Jeff Harris

The first thing I'd recommend is check to make sure that you're on the latest version of SmartDeploy; v2.0.2097. There were some known bugs regarding locale in previous versions. Also, confirm that the desired locale is set in the Regional Settings portion in the Answer File wizard. Whatever is set there will override what was in the reference VM.

Remember; you need to recreate boot media after you update, and also make sure the setup file isn't 'blocked' in the file properties menu.

Laura; that is something that will require a closer look by the Support Team. Restart the device into the SmartDeploy boot environment, click Collect Logs, and send the zip file thats created along with a run-down of what you're doing and when the error occurs to support@smartdeploy.com.

In the mean time, make sure that you're using the latest version of SmartDeploy; 2.0.2097. If you're not, log into smartdeploy.com to download it and install it,and re-try your deployment. (Make sure that you view the properties of the installer file to make sure it wasn't blocked upon downloading, and also remember to recreate your boot media after updating.)

Typically; installing the newer version right over whichever version is currently installed works just fine. A couple tips; always right-click the newly downloaded SDESetup.exe file and click Properties to see if the file has been blocked by Windows, and remember that you do need to re-create any boot media that you're using for deployments. 

Uninstalling before installing a new version is something we recommend when troubleshooting problems related to the SmartDeploy console. 

Yes, that's what I needed. I took a look and it appears that the Setup.bat called by the pack was left out on accident. I've replaced that file, and updated the pack to version 1.1.0.1. Please re-download the pack and give your deployment another try. 

Thanks for letting us know!

So I can identify the exact pack you're using; which version of Windows are you deploying? 

Seeing as the original posts in this thread are from over a year ago, I'd encourage you to check out the latest version of SmartDeploy which has USMT features built into it, and to also review the User Guide which covers those features. 

Stephen; is it any platform packs in particular or any one that you try to download? We've seen this issue before and it's often related to something on a particular system, or related to an internet proxy or other content filtering on the network. 

Please try installing SmartDeploy on a different system to rule out your workstation. (Remember that you may need to right-click the installer package, click Properties, and click Unblock before installing.) Alternatively, if you're on laptop and can enable a mobile hot spot on your phone you can eliminate your network as the culprit. 

Hey Tim,

Unfortunately I don't have a quick solution as this isn't a common issue. We'd need to have you email your deploy.log to support@smartdeploy.com so we could look at the version of SmartDeploy you're on and get more details of what's happening in the background.

If you've received the error "Unable to inject the necessary drivers. Code 50" when creating boot media, certain privileges may not be enabled for the account in use. Open a Command Prompt as Administrator and run the whoami /priv command to confirm that the following permissions are enabled:

SeManageVolumePrivilege 
SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege 
SeBackupPrivilege
SeRestorePrivilege
SeChangeNotifyPrivilege
SeImpersonatePrivilege
SeCreateGlobalPrivilege

Here is a TechNet article that covers configuring Security Policy settings.

Thanks for helping identifying this bug CTEK. It seems we've identified the bug and will address it in our upcoming release. 

If anyone following this thread is having the same issue; please contact SmartDeploy support for assistance between now and the release of or next version. 

Are you using CopyProfile for a customized default profile in your deployments?

I'm not able to re-produce this in my test environment. I've never seen or heard of a bug where the console downloads the incorrect path. I'm going to submit this for investigation, and will PM you with a direct link. 

In the mean time, can you please try another pack at random and post the same screenshot as above? 

Are the 2 VMware platform packs the only one's that you've tried to download since installing? Were there any ppk files in the platform packs folder before you installed SD? I've just tested downloading them and the packs appear to be fine as far as their details. This could be mix-up in how the folder is being scanned for ppk files. 

Try this; Copy the  VMware platform packs out of the folder, (or any packs that appear to have mix-matched details), then remove them from the console, and then use the console to import them back in.

When you're creating a new virtual machine for your reference machine, you'll want pay special attention to this specific setting, depending on the platform you're using. 

• When creating a new VM in Hyper-V; choose Generation 1. 
• When creating a new VM in VMware, check the settings and confirm that 'Use EFI instead of BIOS' is not checked. (VMware will not ask you to choose one or the other when you create the VM.)

The reason for this is because SmartDeploy is not able to capture GPT virtual disks. You can't change this after you install Windows! 

That being said; you can still capture a Generation 1 or BIOS configured virtual machines and deploy them to UEFI based machines. 

Problem: When attempting to capture an image, you receive the error message: "Capturing guid partition table virtual disks is not currently supported."

Resolution: This error indicates that the virtual machine is configured to boot with EFI instead of BIOS, or that it is a 'Generation 2' Hyper-V virtual machine. You will need to create a new virtual machine with that setting disabled in VMware, or as a 'Generation 1' virtual machine in Hyper-V, and re-install Windows.