Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Content Count

    641
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Seattle Washington
  • Interests
    Deploying Windows with SmartDeploy

Recent Profile Visitors

8,833 profile views
  1. Hi vlee14, If I understand correctly, you're looking for a real-time status indicator on the console? This is a bit tricky to engineer, since the USMT Scanstate and Loadstate processes are essentially just copying files per-user profile, but they don't output any sort of overall percentage that we could capture and provide as feedback within the UI. We can detect when it starts, and detect when it completes - and that information is reflected via that icon in the console. That said, if you have any feedback about this aspect of the UI, please feel free to submit it - we're always looking to improve the usability of the product, and we appreciate all user feedback. You can send this to feedback (at) smartdeploy.com. Glenn SmartDeploy Support
  2. Hi Chaynie, For this request, please go ahead and submit this to support@smartdeploy.com. Thanks, Chris SmartDeploy Support
  3. Hello, Yes, our plan is to update them periodically or by customer request. Thanks, Devon SmartDeploy Support
  4. Hi Nagaraj, This is a difficult scenario, since using SmartDeploy requires local administrator privileges, which would generally also grant these users access to both the WDS console and any virtualization platform that you're using. If this is a major security concern, I would recommend installing SmartDeploy on a different server. If you have any questions, feel free to reach out to support@smartdeploy.com. Glenn SmartDeploy Support
  5. Hello Joedarkness, Thanks for reaching out to us. Smartdeploy is definitely a great fit for you in this scenario. We will contact you soon via email and get you started with a trial.
  6. Hi MNATC, The easiest way to do this would be with two separate boot images - each with an unattended answer file that points to each image. Add both boot images to WDS with friendly names that indicate which OS image they point to, e.g. Win 10 Base Image (Unattended) and Win 10 Engineering Image (Unattended). You can even do additional Attended versions of these answer files and boot images if you find that useful. Then your technician PXE boots the device, and simply selects the appropriate boot image from the WDS boot menu, and the deployment will proceed. Feel free to reach out if you have any questions or issues. Glenn SmartDeploy Support support@smartdeploy.com
  7. Shane, Please send us your C:\SmartDeploy\Logs\Console.log from the SmartDeploy host here and refer to this post and I'll take a look. Thanks, Devon SmartDeploy Support
  8. Hi Ted, Just to clarify something on differencing images, a differencing image (.dwm file) is mostly intended for a use case of having to support branch offices with limited connectivity, as it allows you to save a smaller .dwm file that only contains the changes that were made to the VM since a previous .wim was captured. This would allow you to not have to upload a large, multi-GB .wim file to another office every time you update your image. You can certainly use differencing .wims each time you update instead, but there’s not much of an advantage over just capturing a new .wim file for the use case you described below, unless you need to transfer the image to another location. If you are using differencing wims, you will want the original .WIM in the same locations as the .dwm and then point to the .dwm when creating your answer file. Also, SmartDeploy technically does not support 1903 yet, so if you run into issues we would have to say recreate your VM with a 1809 ISO. We should have full support of 1903 soon. Thanks, SmartDeploy Support Devon
  9. Howard, Sorry to hear you're still having issues. Yes, please submit a ticket here. Reference this thread and we will get this resolved. Thanks, Devon SmartDeploy Support
  10. According to the log the Media Wizard is crashing while reading your image. C:\SmartDeploy\Images\Win7AdminNVMe.wim Have you used this image before?
  11. Hi there, Sure thing - reaching out via email now. Glenn SmartDeploy Support
  12. Hi vlee14, Please refer to this: https://docs.microsoft.com/en-us/surface/ethernet-adapters-and-surface-device-deployment Based on this, your dock and dongle should work. You won't need to disable SecureBoot.
  13. Hi vlee13, I found that with using PXE boot, you still need to enable the "Enable boot from USB devices" option in the boot options list. Did you by chance do that?
  14. Aaron, Glad it works in your case. This issue doesn't occur with all imported WDS images, but we have seen it come up quite a bit.
  15. Hi Ted, That return value doesn't look like a success - just to confirm, is the client installing properly now? Glenn SmartDeploy Support
×
×
  • Create New...