SmartDeploySupport

-1054801659 means there is no WDS multicast transmission associated with your Install image, or it needs to be recreated. You will need to right click on your install image and select Create Multicast Transmission, or delete the current one associated to your install image and recreate with the same steps. If you still encounter the same error, we have seen this if the .RWM is corrupted or associated to the wrong image somehow. - Delete your ImageGroup via the WDS interface - Create a new ImageGroup via the WDS interface - Import your Install image into the Imagegroup - Right click on your image and select "Create multi-cast transmission" - Attempt to re-deploy and say "Yes" when asked if it's a multicast transmission Let us know your results. SmartDeploy Support

Hi esardinha, This may be possible, depending on the specific model. Intel's driver support for their NUC series of MiniPCs has been fairly robust, and from my initial browsing of their download center, it looks like they may have a similar level of driver support for the Compute Stick, which looks to be structurally similar in a smaller package. I can't say with certainty whether we can create a Platform Pack for this device without having its hardware information and model number in hand, but if you'd like us to look into it, go ahead and fill out our Platform Pack Request Form with the hardware info (wmi.txt) from the device, and be sure to indicate which operating system(s) you're interested in deploying. https://www.smartdeploy.com/support/platform-pack-request/ I see from our records that you're a current support customer with us, so we'll be in touch after you fill out the form to let you know if it will be possible to create a pack, and if any fee would apply to do so. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Martijn, Do you have any anti-virus on your virtual reference machine by chance? If so, uninstall it and try capturing again. If you still have issues, try capturing while the machine is powered on. Boot the virtual reference machine to the C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SmartDeploy_x64.iso. Select the capture option and capture the image to a network share, which can also be the local host. This process is documented in the User Guide on page 49. Then deploy that image and let us know your results. Thanks, SmartDeploy Support

It can be fully updated (which we recommend) including those two updates. If you update your Windows 7 VM with all updates you will get the above updates as well. Thanks, SmartDeploy Support

Hi Javier, Usually, it means that the computer account already exists in a different OU than what was specified. You should be able to join without specifying an OU, or if you want the machine account in a different OU, then that account would have to first be deleted or moved. Thanks, SmartDeploy Support

Hi Martin, Unfortunately, PowerShell commands are not supported in the SmartDeploy PE environment, as the PowerShell environment is not a part of Windows PE. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Stuart, If you use the "wipe and reload" option, the contents of a single folder on C: can be preserved on the target device. This has to be a folder in the root of C: (by default, it would be C:\Backup). Using a folder in C:\Users would not be a practical option. This folder is created by Windows (so it would be wiped out upon reimaging). There are further reasons why this would be unworkable as well - user accounts have unique identifiers and permissions that would not match on the reimaged device even if you created a new account with the same name as the old one. If your goal is to preserve files through reimaging, you'll want to copy these files to the C:\Backup folder (or another folder that you designate in the Deploy Wizard advanced options), and select the Wipe and Load Drives option. If you're testing different backup methods, we would recommend backing up any data externally until you're certain the deployment is configured as desired, in order to avoid data loss. Feel free to reach out if you have any questions - you can reach us at support (at) smartdeploy.com SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Oh wow, sorry to hear that. What probably happened was your boot media was created successfully, then the host computer restarted for whatever reason (Perhaps Windows Updates?) and it booted to the unattended USB stick which imaged the host computer. It used the Windows in box drivers to image. SmartDeploy Support

Hi Rich, We just sent you an e-mail for some more information. Thanks, SmartDeploy Support

Hi Anthony, Thanks for reaching out. SmartDeploy images are created and maintained in a virtual environment in order to be hardware-independent. So - to address your two key scenarios: Installed a new security patch (Windows Updates): Yes, you would need to gracefully shut down the VM and recapture. Then you would use this new WIM to deploy to your devices. Downloaded a new Platform Pack/Wish to deploy to another device: You do not need to recapture your image in this case. As long as you have the correct Platform Pack that matches the target device and the OS of the image you're trying to deploy (e.g. HPEliteBookFolio1040G2-Windows7.ppk), then you should be able to deploy your image to that device. The only thing you might need to do when you download a Platform Pack is re-run Media Wizard to include any additional Windows PE drivers that may have come with the new pack. This will ensure that the SmartDeploy PE environment has all of the drivers it needs for your specific devices in Windows PE, whether that's Ethernet, SATA, or anything else needed before the OS and the full driver set are installed. If you have any questions or issues, feel free to shoot us an email at support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

This may have something to do with your Windows 10 image. You'll want to download the latest Windows 10 .iso that includes the 1511 update from Microsoft Volume Licensing and create a brand new VM from that .iso. Once it's at the desktop, perform a full shutdown with "shutdown /s /t 0" then capture that VM and retest your deployment. Thanks, SmartDeploy Support

Hi Zach, Hmmm... That's an odd error message to see if there don't seem to be any driver problems afterward. Can you pull the following logs and email them to us at support (at) smartdeploy.com? C:\Windows\Debug\Deploy.log C:\Platform\Dism.txt C:\Windows\Inf\Setupapi.dev.log Be sure to reference this DeployCentral thread in your email. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

In order to deploy Windows 7 to modern hardware, you need to ensure these 2 KB's are installed in your VM before it's captured. https://support.microsoft.com/en-us/kb/2685811 https://support.microsoft.com/en-us/kb/2685813

What version of Windows is this? If it's Windows 7, you'll need to ensure KB2685811 and KB2685813, the Kernel-Mode and User-Mode framework updates are installed in the VM before capturing it. These are required to deploy Windows 7 to modern hardware. This might explain why your 64-bit image works and your 32-bit doesn't. If that doesn't resolve it, contact us directly at support @ smartdeploy.com and we'll troubleshoot further.

Please contact us directly at support @ smartdeploy.com and we can have you gather some logs to investigate further.

Yes, you can manually just copy additional packs onto the USB media. By default with offline media, the Deploy Wizard will look in the Z folder. Thanks.

Hello, The way drivers loaded is the same. Send us the following logs from the deployed machine and we can take a look what may be going on: C:\Windows\Debug\Deploy.log C:\Platform\dism.txt (May not exist if the drivers aren't loading) Send to support @ smartdeploy.com and refer to this thread. Thanks, SmartDeploy Support

Hello, We stopped creating multiple OS packs and now just list the OS the pack supports. For the D620 the multiple OS pack contains Windows 7 support both x86 and x64 and Windows XP (Which we no longer support). A Windows 10 pack cannot be created for the D620 as Dell does not support Windows 10 on that device. We build our platform packs based on the manufacturer drivers. You could deploy without a platform pack and use the Windows 10 in box drivers, but if you run into any issues it would be unsupported by Dell and SmartDeploy. Thanks, SmartDeploy Support

Hello, In order to skip all pages except the computer identification, when you export your answer file, export it as attended, not unattended. Once exported, open your exported XML and simply add a skip value of 1 for every page you want to skip. For example, if you don’t want to skip the network identification page you would leave that value as 0. All other pages you would have a value of 1. This way, when you select “Deploy an Image” from the SmartPE splash screen it should skip all the pages except for the network identification and page. Thanks, SmartDeploy Support

Send us the above log as well and we can take a look. Thanks, SmartDeploy Support

Hello, Run two deployments at the same time. When the second deployment freezes, can you close out of the Deploy Wizard and return to the splash screen? If so, click the link to open a command prompt and browse to X:\Windows\Temp\Deploy.log. Save deploy.log to a network share/usb and then send it to support@smartdeploy.com and we can take a look. Reference this thread as well. If the Deploy Wizard completely freezes and you can't move/close it, try opening the command prompt first, then start the deployment. When the Deploy Wizard freezes you should still be able to access the CMD prompt. We'll take a look what may be going on. Thanks, SmartDeploy Support

Hi daizer, The Media Wizard log is a text file called Media.log, located in C:\SmartDeploy\Logs (by default, unless you've selected a different location for the SmartDeploy folder structure). Go ahead and send us the log at support (at) smartdeploy.com, and we'll be happy to assist further. Be sure to reference this DeployCentral thread in your email. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Maarten, This happens when the WIM's meta data is not complete. Try capturing while the machine is powered on. To do so, boot your virtual reference machine to C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SmartDeploy_x64.iso. Then opening a command prompt by clicking the link on the splash screen and entering the above command again. You will have to save the .WIM to a network share, which can also be the local host. Thanks, SmartDeploy Support

Hello, You can use the same USB as many times as you need. SmartDeploy does not mark the USB unable once it has been deployed from. Thanks, SmartDeploy Support

The Deploy Wizard is part of SmartDeploy.