Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

  • Gender

Recent Profile Visitors

8,509 profile views
  1. SmartDeploySupport

    Insert Disk 1?

    Tom, Does that work 100% of the time? I ask, because if it's the same exact image, it's most likely randomly working at times when importing into Install Images and creating the res.rwm.
  2. SmartDeploySupport

    Insert Disk 1?

    Jason, I wish we could help. We are looking into workarounds but ultimately it's something Microsoft needs to fix.
  3. SmartDeploySupport

    Insert Disk 1?

    Hello, This is a known issue. It occurs if the Windows 10 image is 1803 or greater. There is a chance that it won't import correctly into WDS on Server that isn't 2016. But, not all images have the issue, so you may have luck recreating the image. The older version of Wingapi.dll isn't handling some of the new file properties in 1803. Unfortunately this is something we cannot fix and it even happens when importing a .WIM that isn't create by SmartDeploy but even dism.exe.
  4. SmartDeploySupport

    remote agent

    Hi Nathan, Please refer to our cloud broker KB: https://support.smartdeploy.com/kb/article/34-performing-a-cloud-push-deployment/
  5. SmartDeploySupport

    Insert Disk 1?

    We have seen other customers experience this as well. Thanks for attaching our logs. We will reach out soon as we are trying to reproduce this issue on our end.
  6. SmartDeploySupport

    WIN 10 OS Digital Signature error

    Hello, We are based in Seattle Washington. We open at 8am PST, which was about 15 minutes ago. A tech will reach out shortly. Sorry for any inconvenience.
  7. SmartDeploySupport

    WIN 10 OS Digital Signature error

    Support will reach out to you shortly in response to #SDE00003674.
  8. SmartDeploySupport

    WIN 10 OS Digital Signature error

    Please boot to SmartDeploy media on the affected device (ideally with USB boot media with no answer file, to avoid starting another deployment and wiping the previous logs), click the Collect logs option, save the resulting zip file to an external location. Submit it via the Support form, which includes a file upload option.
  9. SmartDeploySupport

    WIN 10 OS Digital Signature error

    Hello, When do you receive this error message? After applying the image or when you boot to the SmartDeploy boot environment. If you could provide a bit more detail we can investigate further. Thanks, SmartDeploy Support
  10. Hi WixonStaff, Thank you for sharing your experience! What you've described is definitely a good method for troubleshooting - by default, SmartDeploy will use the administrative share path (e.g. \\computername\c$\SmartDeploy) of whatever location you browse to in the Answer File Wizard, rather than the name of any network share that you may have manually created. And it's true that this may or may not be reachable from a target device depending on what set of credentials you use, your network environment, etc. If you're ever uncertain which path to use from a target device, you can always open a command prompt in WindowsPE (by clicking the link at the bottom of the SmartDeploy splash screen) and try mapping a network drive to the share manually: net use * \\computername\SmartDeploy net use * \\computername\c$\SmartDeploy Once you've confirmed which path and credentials work most reliably from the target device, you can update your answer file to make sure that this is reflected, then recreate your media using the updated answer file, and you should be all set. Thanks again, and please feel free to reach out to support if we can assist you with anything. Glenn SmartDeploy Support
  11. SmartDeploySupport

    Windows 10 1809 - Sysprep Fail

    Hi Lee, Unfortunately, Justin is correct - we no longer recommend upgrading your reference VM from one major Windows 10 version (e.g. 1803) to a later Windows 10 version (e.g. 1809). The in-place upgrade process from Microsoft (which includes a Sysprep run, and retaining an entire previous set of Windows.old files on the VM, adding several GB to the image size) leaves the VM in a less reliable state for capture, Sysprep, and deployment. Our best recommendation if you wish to deploy a new major Windows 10 version is to build a new, blank VM and install that Windows version using OS media from Microsoft that includes that version. Then run all available Windows Updates (for that version only - no major version upgrades), gracefully shutdown the VM (shutdown /s /t 0), capture, and deploy. Once you've confirmed the VM has produced a good image, back up a copy of the VM in its known-good state, and then you can begin installing software and configuring as needed. This way, you'll always have a good copy of the VM to fall back on if any software installation or configuration change results in an unusable image. In order to deploy a Windows 10 Version 1809 image, you will need to have SmartDeploy version 2.0.3025 or later installed, and be sure to recreate your SmartDeploy media after installing the new version. Please feel free to reach out to support if you have any questions or issues - you can reach us at support@smartdeploy.com. Glenn SmartDeploy Support
  12. SmartDeploySupport

    Windows 10 1809 - Sysprep Fail

    If you still experience sysprep issues with 1809, please submit a support ticket and we will take a look. Thanks, SmartDeploy Support
  13. SmartDeploySupport

    Boot media Creation taking long time

    Hi Chris, We'll need to see your Media Wizard log - C:\SmartDeploy\Logs\Media.log. Go ahead and email it to support@smartdeploy.com, and we can assist further. Glenn SmartDeploy Support
  14. SmartDeploySupport

    Remote Cloud deployment

    Hi Tim, We'll reach out to you via email for further troubleshooting. Regards, Glenn SmartDeploy Support
  15. SmartDeploySupport

    Windows 10 Activation

    Tony, Thanks for clarifying. Yes, that is compliant.