SmartDeploySupport

That is probably due to a mismatch between UEFI and Legacy. The way the machine is configured, and the boot option need to match. I.e. if the machine is in UEFI mode, then you need to ensure you are selecting a UEFI boot menu option. If the machine is in Legacy mode, then you have to select a Legacy option. Ensure that once booted to SmartDeploy, the lower right hand corner shows the correct setting UEFI or BIOS. Looks like you we're booting the machine in BIOS, but it was configured UEFI. It looks like by default on these devices the "Enable UEFI Network Stack" isn't checked. So, in order to UEFI PXE boot this machine, you'll need to go into the BIOS, System Configuration, Integrated NIC, and check the Enable UEFI Network Stack" option. Also, put the machine back into it's default settings, if you changed it to Legacy... General, Advanced Boot Options, Enable Legacy Option ROMs = unchecked Secure Boot, Secure Boot Enable, Secure Boot Enable = checked

It looks like the Deploy Wizard could see the disk... DeviceID:\\.\PHYSICALDRIVE0 Caption:SK hynix SC311 SATA 256GB So, what was the exact error you we're receiving? It actually looks like from the logs that the deployment was successful. Is it just that the machine is auto rebooting to the USB drive? If so, you'll need to remove it and reboot the machine. Or, Deploy Wizard, Advanced Options, and choose shutdown instead of reboot so that you'll know when the deployment is finished and to remove the USB stick. Unfortunately, some UEFI devices write a firmware boot entry for the USB drive, and will try to boot to it on reboot, even if we clear out the firmware boot entries before rebooting.

Are you using the beta release by chance? Can you check Add/Remove programs and verify that SmartDeplloy Enterprise is 2.0.3000.8154? If it's not, then uninstall that version and download the current version from our website, and re-create your boot media. If it is, then boot your 7490 to SmartDeploy and on the splash screen click Collect Logs. Save the resulting .zip to USB or Network and email it to us at support @ smartdeploy .com Thanks!

If you are using SmartDeploy 2.0.2097, then you need to ensure you've built your boot media with the platform pack for this device selected. Otherwise, if you are using SmartDeploy 2.0.3000, then it should work out of the box.

Hi Eric, Please email us at support (at) smartdeploy.com (referencing this thread) and we will provide further instructions. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Try cleaning the existing drive. Boot to your boot media Click the link to open a command prompt in the SmartDeploy splash screen Perform the following commands: Diskpart Select Disk 0 Clean (this will wipe the selected disk) Create partition primary (this will create a partition to apply the image to) Format FS=NTFS Quick Assign letter C Active Exit Restart the machine and attempt to deploy again and let us know your results.

Hi there, Network-based deployment packages can only be used for console-initiated deployments, which can only be performed for target devices that have a functional OS and the SmartDeploy client installed. For new computers - which may have no OS installed, or may have an OEM image installed - we would recommend using some other method to boot these devices. PXE boot is indeed an option, but it requires integrating SmartDeploy with Windows Deployment Services - see our white paper here (direct link to PDF) for details. You can also boot the target devices using USB boot media, or offline deployment media (see P. 34 of the User's Guide for detail on the various media types available). Feel free to shoot us an email at support (at) smartdeploy.com if you have any questions or issues. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Hi Don, OEM licenses do not include reimaging rights from Microsoft. We have had some customers report success with such licenses, but it is inconsistent and unreliable (by design), as the license is only intended to be used to revert the device back to its original factory image. SmartDeploy has no interaction with this process, so we have no control over whether or not Microsoft allows the device to activate if you do not provide a license key for us to pass through at deployment time. Our recommendation is to look into getting a volume license. We are not a volume license reseller, but we can put you in touch with one - go ahead and email us and we can send you their info. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Hi Don, Activating Windows on the reference VM has no bearing on whether it will activate on the target PC. The Sysprep\Generalize process which runs on every image at deployment time strips out any existing license info from the image. SmartDeploy provides two opportunities to enter a Windows product key - either in Capture Wizard (in which case it is hashed and written into the metadata of the image to be used at deployment time), or in Deploy Wizard (in which case it is written into the Sysprep Unattend.xml to be used at deployment time). If you do not provide a Windows product key at one of these times, then we cannot guarantee that the target device will activate. If you have any questions, feel free to email us at support (at) smartdeploy.com Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

On a workstation that's connected to the network, run the following command: (You may need to verify your interface name) netsh wlan export profile name="NameOfWirelessNetwork" folder=c:\temp interface="Wireless Network Connection" Then copy the NameOfWirelessNetwork.xml file to a place on your reference VM like C:\Temp\ Then you'd add a 'At First Logon' task to your Answer File, using the Tasks tab in the Advanced settings of the Answer File wizard with the following command: cmd /c netsh wlan add profile filename="C:\Temp\NameOfWirelessNetwork.xml" Alternatively, you could keep the xml on a network share, and use GPO to import the wlan profile. You may also need to do some tweaking to the xml file dpending on which security method you use. You an find examples on TechNet for this.

Glad to hear it - please let us know if we can assist with anything else. Regards, SmartDeploy Support

Can we please see your C:\Windows\Debug\Deploy.log from the deployed machine where the task did not work? Thanks, SmartDeploy Support

When you said it originally worked, did you also use wipe and load?

Have you tried doing a full format on the USB stick? If not, try performing a full format on the USB, then rerun the Media Wizard and recreate your boot media. Let us know your results. Thanks, SmartDeploy Support

Usually we see this if anti-virus is installed on the image. Is that the case in this scenario? Thanks, SmartDeploy Support

Hi there, Yes, you can download this pack from within the console. The official model name (as listed by Dell) is Latitude 14 Rugged 5414 - a search for '5414' should allow you to find it. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Restart the machine back into the SmartDeploy boot environment and click Collect Logs. Save the resulting zip to a usb or network share and send it to us and we can see what the issue is. Please submit the logs here and refer to this thread https://www.smartdeploy.com/support/support-request/ Thanks, SmartDeploy Support

To customize copy the wallpaper to default users, I have included the needed files and instructions for setting up Default Profile (Copy Profile) in the CopyProfile.ren attachment, please rename to CopyProfile.zip before opening. That being said, with the Windows 10 1709 release it does seem as it may not work sometimes due to the build in appx packages. This is sadly out of our control, but you can still try it. Sysprep may be resetting the applications settings, what specific application settings are you trying to set? Thanks, SmartDeploy Support CopyProfile.ren

Hello, Please send the following information to us at support (at) smartdeploy.com: -Whether there is any antivirus software running on the computer where SmartDeploy is installed -Whether there is any a/v installed on the VM you're capturing -Whether you have successfully captured a VM on this computer previously Also, please send your Capture Wizard log: C:\SmartDeploy\Logs\Capture.log Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Hi Lee, We really need to see a log set in order to answer this question. Please go ahead and submit one via the Support Form link above. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

If the Windows version in the reference machine library is showing as 1607, then that is how the VM appears to SmartDeploy externally. You'll want to go ahead and power on the VM and run that winver command to confirm which version is installed. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

If you mean within the VM, you can confirm this by running the command winver. Determining this from the captured image (.wim) is also possible, but we'll need to have a look at the log set referenced above. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

Hi Lee, There's really no plausible mechanism for this other than capturing the VM in the wrong state/snapshot (which you've ruled out above), or accidentally deploying an old image. Have you updated your answer file to point to the new image, recreated your WDS boot media, and replaced it on your WDS server? If you've omitted any of these steps, it's possible you're still deploying the old image. If you're not sure which image you deployed, you can retrieve a log set from the deployed device and we can take a look. 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, and email to us at support (at) smartdeploy.com. Note that some organizations restrict sending zip files over email, so you may want to check with your IT department to make sure the email made it out with the attachment. Alternately, you can fill out our Support form, which includes a file upload option. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks

This is a new feature in Windows 10 1709. Would need to be disabled via Group Policy, if that's possible.

Hi Michael, Glad to hear it's going well otherwise! Per our message, we'll continue troubleshooting this one with the log that you sent via email. For anyone else reading, if you have experienced any errors with Media Wizard, feel free to contact us at support (at) smartdeploy.com, and send your Media Wizard log, which is located in the SmartDeploy directory (default location: C:\SmartDeploy\Logs\Media.log). Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks