SmartDeploySupport

Is this Windows 7 Professional VL by chance? You may just have to force the key and activation with tasks. Deploy Wizard, Advanced, Tasks… FIRSTBOOT cscript.exe c:\windows\system32\slmgr.vbs –ipk XXXXX- XXXXX- XXXXX- XXXXX- XXXXX cscript.exe c:\windows\system32\slmrg.vbs –ato

This should still work just the same. Might want to verify that Win32_BIOS SerialNumber contains a valid computer name on the machine in question. I.e. "wmic bios get serialnumber" If it doesn't meet the criteria for a valid Windows computer name, then it wouldn't get used. If this is happening on machines where this is populated with a valid value, then might want to create a new answer file just to be sure. Also ensure this answer file is getting used... I.e. click on Advanced, Identification tab, and are these selections specified?

This error is usually because the installation of Windows has been upgraded. Sysprep will not run on an upgraded installation. With Windows 10, the Threshold 2 (1511) update is being run as an in-place upgrade. If you want to create an image with this update, you must create the VM from slipstreamed 1511 media. I.e. download the updated .iso from MS VL.

Hello, Send us your C:\Windows\Debug\Netsetup.log to support@smartdeploy.com and we can take a look. Thanks, SmartDeploy Support

Hi Alan, The version of the Windows ADK that is supported (and required) for the current version of SmartDeploy (2.0.1030, as of this writing) is: Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 Update https://www.microsoft.com/en-us/download/details.aspx?id=39982 SmartDeploy does support deploying Windows 10 with this version. Feel free to reach out if you have any issues installing or using the ADK with SmartDeploy - you can reach us at support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Yes, you could have another boot image with it's own answer file and load it to WDS as well. When you import the boot image you will have the option to name it. You could name the boot images like the following for example and would be able choose which one you desire upon PXE boot of the target machine. This is what most users do. Windows 7 - Standard Image Windows 8.1 - Sales image etc Or you could have one boot image, and have everything automated in the answer file except the Select Image screen where you could select which image you would like to choose. We can provide you with those steps if you would like. Thanks, SmartDeploy Support

Hello, You could send the the .WIM and packs to the remote site, then have them deploy that .WIM via the network if that's what you're asking. Thanks, SmartDeploy Support

Update (2014-04-11): You can access your license usage at http://www.smartdeploy.com/licensing – if you need to decommission any machines due to end-of-life, you can send those on a spreadsheet to licensing@smartdeploy.com. ___________________________________________________________________________ Hello, You can check your licensing usage here and decommission a machine. https://www.smartdeploy.com/register/licensing/ Then deploy to the new machine. The machines are counted by the deployment not the machine name or MAC address using an agent. Thanks, SmartDeploy Support

Hi there, That does sound frustrating! Sorry you've been experiencing these issues, and we'll do whatever we can to help troubleshoot them. Regarding Tech-Win7x64, which is failing with the "Windows could not parse or process" issue: The most common cause of this issue is a mistyped Windows product key. From the details that you provided, it sounds like you've heard this suggestion from us before, so I'm glad we can rule that out! To diagnose the cause of this issue, we'll need you to retrieve the Windows Setup logs from a device that has failed in this manner. Since you've retried a number of different times, I'd like you to go ahead and perform another test deployment, and when you see this error, simply press and hold the Power button to power off the device. Once you've done so, email us at support (at) smartdeploy.com, and be sure to include a link to this DeployCentral thread for reference. We will provide instructions for how to retrieve the logs. Regarding the All-Win7x64 image: If this image was indeed created with the SmartDeploy Capture Wizard, and is known-good on other devices, this may be a bug we'll need to zero in on. I'd like to have a look at the WIM metadata for this particular image. Please complete the following steps: On your SmartDeploy IT Workstation, click Start, and type SmartDeploy Enterprise Command Prompt. Right-click the prompt in the search results, and click Run as administrator. In the command prompt, browse to the folder that contains your captured image, and execute this command: SMARTWIM /info "[yourimagename.wim]" >wiminfo.txt Here’s an example of this command being executed on a wim stored on my system: cd C:\Demo\Images SMARTWIM /info "Windows 7.wim" >wiminfo.txt This will create an output file that includes the wim information, in the same folder as the wim itself. Please send this file with your reply. Note: If this command fails, try it again without the >wiminfo.txt included. This will output the result of the command in the window, where you can select the text and copy it into an email instead. Using either method, go ahead and send us the output of this command to support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Allen, Be sure you have SilverLight 5 installed. You can download it here: http://www.microsoft.com/silverlight/ If you still have issues, contact support@smartdeploy.com Thanks, SmartDeploy Support

Simon, You can capture the virtual reference machine when it’s powered on. To do so, boot the virtual reference machine to the C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SmartDeploy_x86.iso. Select the capture option and capture the image to a network share, which can also be the local host. Let us know your results. This process is documented in the User Guide on page 49. Thanks, SmartDeploy Support

This is still the supported way. Thanks, SmartDeploy Support

Hi Eric, Thanks for the detailed error info. We've actually just released a new version of SmartDeploy v2 (2.0.1020) that's intended to bugfix several issues - go ahead and download and install the latest version from SmartDeploy.com, and feel free to email us at support (at) smartdeploy.com if the issues persist. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello, It is purely optional to use the new C:\SmartDeploy folder structure, as well as the console libraries that they correspond to. All of the wizards will continue functioning exactly as they did previously, even if you have your VMs, images, platform packs, etc. stored on a secondary drive – you would simply need to browse to that location from the wizard as you did before. Based on customer feedback, we are planning to add the ability to select a different location for use in the console libraries in a future release. Thanks, SmartDeploy Support

Hello, Are you using version 2.0.1010 of SmartDeploy? If not, you will need to upgrade and recapture as this was fixed in 2.0.1010. Thanks, SmartDeploy Support

Hello, We do want to add the ability to change the install folder in a future release, but in the current release drive c: is it. You don’t necessarily have to store your large files in the C:\SmartDeploy folder. Can just have them wherever and browse to them with the Wizards. Thanks, SmartDeploy Support

Did you use the latest version of SmartDeploy to capture and deploy this image? Only version 2.0.1010 supports Windows 10. https://www.smartdeploy.com/download/ Also, if using VMware to create your image, be sure to perform a full shutdown (shutdown /s /t 0) before capturing that VM.

Thanks, we are taking a look now. We will respond to your mail as well as update this thread once we know more. SmartDeploy Support

Hi all, Can you run the following command from the command prompt and e-mail the C:\SmartDeploy.log to support@smartdeploy.com SDESetup.exe /V" /lv C:\SmartDeploy.log" Also, if you're on a domain, dis-join and see your results as well as it may be related to a group policy of some sort. Thanks, SmartDeploy Support

Hello, If you have any anti-virus on your SmartDeploy host, disable it and run the installer again. Let us know your results. Thanks, SmartDeploy Support

Hi Adam, We replied to your e-mail that you sent to support. We'll need your C:\Windows\Debug\Deploy.log from one of the deployed machines to investigate further. Thanks, SmartDeploy Support

Interesting.. What is the task command you're using? Be sure the files that the task is calling are there as you will get this error if a task is incorrect as well. Thanks, SmartDeploy Support

After reviewing the platform pack it looks to be in working order. Ensure your product key is good. If it's baked into the image, try recapturing with a good key. If you still have issues, shoot us an e-mail at support@smartdeploy.com and we can gather some logs from you to investigate further. Thanks, SmartDeploy Support

You can actually install SmartDeploy on as many workstations as you want. Licenses are only required for the target devices you deploy with SmartDeploy. You can find our licensing FAQ here. Thanks, SmartDeploy Support

Hi Javier, Unfortunately, you cannot have two instances of SmartDeploy on the same computer. As soon as you install 2.0.1010 it would automatically upgrade 1.1.3010 to 2.0.1010. Thanks, SmartDeploy Support