Jeff Harris

BB IT; Let's continue in the ticket you opened. 

Can you first check the properties of SDESetup.exe and look to see if there's a button or checkbox for 'Unblock'? If so, please click that, click OK, re-install SmartDeploy and see if that corrects the issue. 

Sorry, but no; SmartDeploy doesn't support the capturing of images from physical hosts, or virtual disks created from a physical-to-virtual conversions. 

Are you able to capture the image if you perform a warm capture? Mount the ISO file below to your Ref VM, boot to it and start the capture wizard. 

C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SmartDeploy_x64.iso

I would start with adding exceptions/exclusions for the Console, CaptureWizard, BuildWizard, and MediaWizard EXE files which are found in C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\Resources.

You'll create a boot image and import that into your WDS host, and you'll also import your Windows image. You can check out the process end to end in the WDS Integration guide here: https://www.smartdeploy.com/wp-content/uploads/SmartDeploy_WDS.pdf

I've attached a key for those icons. We're working on the documentation update for these now. 

SmartDeploy - Icon Definitions_v2a.pdf

Sorry for the delayed response. You do want to open a command prompt as administrator, and then run the the script there. 

One thing I would do, is make sure that the zip file containing the script and accompanying files isn't blocked, by viewing the Properties of the zip file and making sure there's not an Unblock button or checkbox. If so, unzip it again and try again. 

If you collect logs and contact support, they can help narrow down the issue. It could be related to the clipsvc service issue with Sysprep. This was addressed in v2.0.3005, but it was found that certain models required additional tweaking, which will be addressed in the soon to be released 2.0.3006 build. 

I would also recommend creating a new VM and installing Win 10 v1803 directly if your current Ref VM was in-place upgraded from 1709 to 1803. 

You changed your SmartDeploy folder away from the H: drive? Do you have new Ref VMs in the new folder location?

It's also worth testing with a warm capture to see if you get the same message. 

C:\Program Files (x86)\ would have been the default location and would have been used unless manually changed by whomever installed. If you find that it was installed there and those DLLS are missing, please re-install SmartDeploy after checking the Properties of the SDEsetup.exe file to make sure that there isn't an 'Unblock' prompt on the General tab of the Properties menu. 

Hi Brad, 

Do you have anti-virus or other security software installed on the Reference VM? If so, you may need to uninstall it. A/V in images often breaks the capture/deployment in unpredictable and unusual ways. If you have it installed on your SmartDeploy host, you may also need to temporarily disable it as it sometimes incorrectly flags some of the activities that SmartDeploy as malicious. 

If neither is the case; then the next thing I would try is a warm capture. You can mount the C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SmartDeploy_x64.iso to your virtual machine, and boot to it to get to the SmartDeploy boot environment, and start the Capture wizard. 

/Jeff

Unfortunately, SmartDeploy is not able to do that. It will always wipe the contents of the drive, and apply the image that you captured from your reference VM. That being said, you can use the User State Migration Toolkit (USMT) option in the Answer File which will copy the user files and some settingsback onto the device after the image is applied. 

Here's a link to some Microsoft documentation on USMT.  This is the tool that SmartDeploy uses when you enable it in the Answer File. 

One other user was stuck in this state, and we were able to get it going by re-registering some DLLs. Can you Open a command prompt and try the following commands? After that, please restart your system, remove the erroneous packs and try the download again. 

regsvr32 "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\Resources\SmartCOM.dll"

regsvr32 "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SDK\Bin\64bit\SmartCOM.dll”

Following deployment, if you create a new profile are the apps still broken/missing?

Have you successfully deployed this image before? 

The things to check would be that no in-place upgrades have been done on the VM, that there's no anti-virus software on the reference VM, there are no pending updates, and that it was shutdown with the shutdown -s -t 0 command. 

Ah I see. I misunderstood that you were running sysprep generalize, shutting down and capturing the image. I've attached our instructions for using copy profile, just in case. 

CopyProfile.zip

Hey guy.

First, you never want to sysprep/generalize your Reference VM before you capture your image to use with SmartDeploy. We do that for you at deployment. 

And in short; The settings you enter into the Answer File wizard are in turn applied by SmartDeploy to the answer file that's used by sysprep. 

4 minutes ago, jaykeblakk said:

So in other words, if I have a VM that has 15+ individually installed programs on it and I want to deploy a new version of Windows 10, I will have to just build the VM brand new and re-install all of those programs?

Yes, this is our recommendation, as well as Microsoft. However we are working on a version of SmartDeploy that will hopefully address some of the issues that arise from sysprepping Windows that was upgraded from 1709 to 1803. 

You do not want to do in-place upgrades on your VMs in between major versions of Windows 10. If you wish to deploy v1803, you will want to create a new VM and use the v1803 ISO to install that version of Windows directly. 

If you're able to, boot that system back into the SmartDeploy boot environment and Click Collect Logs, and send them into Support. 

Usually the only real catch is to avoid opening any Office apps after installation. You mentioned the user guide, but just want to make sure you caught that.

Here's the link to Microsoft's guide for installing O365 on a reference system for deployment. It's got a little bit more information; https://docs.microsoft.com/en-us/deployoffice/deploy-office-365-proplus-as-part-of-an-operating-system-image

45 minutes ago, allenturnage said:

I'm currently having this same problem. I don't understand the fix here.

Are you able to enter the system settings and enable Secure Boot?