SmartDeploySupport

Hi Barak, Please contact SmartDeploy at support (at) smartdeploy.com and we can assist further on this. Glenn SmartDeploy Support

Restart the machine that back into the SmartDeploy boot environment. Click Collect Logs and save the resulting zip to a USB or network share and send it to us and we can investigate. You can attach the zip here, or send it to us at support @ smartdeploy .com and reference this thread. Thanks, SmartDeploy Support

Please try closing the SmartDeploy console, open an Administrator command prompt, and run these commands: regsvr32 "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\Resources\SmartCOM.dll" regsvr32 "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\SDK\Bin\64bit\SmartCOM.dll" Then retry downloading the PPK. Thanks, SmartDeploy Support

Does this particular VM that causes that error have snapshots? Thanks, SmartDeploy Support

Hi Jeff, It sounds like the storage controller is failing to initialize in PE, likely due to a missing driver. We recently added a Windows PE 10.0 storage driver to this pack - make sure you have the latest version of the pack, then re-run Media Wizard to recreate your media (making sure to include this pack, and packs for any other devices you plan to deploy to), then retry deployment. If you have any issues, go ahead and email your Media Wizard log to us at support (at) smartdeploy.com. It is located in C:\SmartDeploy\Logs\Media.log. Glenn SmartDeploy Support

Send the log to support @ smartdeploy .com and we can take a look. Thanks, SmartDeploy Support

Please attach your C:\SmartDeploy\Logs\Console.log from the SmartDeploy host and we can take a look. Thanks, SmartDeploy Support

Yes, by default these new machines ship with SecureBoot on, UEFI only. But, the PXE boot settings don't have the UEFI network stack enabled by default. So, when you PXE boot out of the box it is a Legacy/BIOS boot option and that won't work. The way the machine is configured and the boot option have to match. If you want to PXE boot these machines, have to enable the UEFI network stack first. If USB boot, then you simply select the UEFI USB boot option.

Hello, For this issue, we'll want to see a complete log set. 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 submit it via the Support form, which includes a file upload option. Glenn SmartDeploy Support

Hi Stephen, I'm not sure that all of these currently exist in any single location - there are definitely some in the User's Guide when discussing the specific section involved. Is there a particular one you were curious about? Glenn SmartDeploy Support

Did you create a Windows 10 VM from a 1803 ISO? Attach your C:\Windows\Debug\Deploy.log from the deployed machine and we can take a look. Thanks, SmartDeploy Support

We resolved this issue with the latest version of SmartDeploy (2.0.3005). Download it here: https://www.smartdeploy.com/download/smartdeploy/ Then recreate your boot media via the Media Wizard and redeploy your image and you should have no more broken apps. Thanks, SmartDeploy Support

Try recreating your boot media and selecting JUST the Lenovo Tablet X1 Generation 3 platform pack during the process. This should inject the Ethernet adapter drivers so you receive an IP address in PE. Thanks, SmartDeploy Support

The preimage tasks run as basically the first thing when you click finish on the Deploy Wizard, so yes, any WMI collection has already happened.

Hello, Unfortunately, this is a Microsoft bug - there's not really a workaround we can implement here. SmartDeploy is making use of the AutoLogon feature in Windows, and the known bug is that whatever AutoLogon count you specify in the registry key will be increased by 1. See here for details: https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-shell-setup-autologon-logoncount#logoncount-known-issue SmartDeploy is passing through whatever AutoLogon integer that you specify, and knowing this, if you wanted to automatically log into Windows some number of times greater than 1, you could simply decrement that number by 1, and it would achieve your desired number. But unfortunately, it's not possible to specify 0 - Windows simply will not accept it. So if your desired outcome is just 1 AutoLogon, that is not currently possible. As for the Task, I don't see why that wouldn't work... The command is executed using the current user context. But FirstLogon tasks are only executed on the very first logon, so any subsequent ones would not reboot as a means of escaping/consuming the extraneous AutoLogon (which - if I understand you correctly - is your objective with that Task?). Glenn SmartDeploy Support

Hi John, Glad to hear it was resolved. Please let us know if we can assist with anything else. Glenn SmartDeploy Support

Hello, This should refer to the number of times logging on that you wish it to occur automatically. If you just need a single autologon, then you would set this value to 1. Apologies for the documentation issue - we had to release this build on a faster than normal schedule in response to some issues with Windows 10 Version 1803. The User's Guide will be updated in due course to reflect all of the new features. Glenn SmartDeploy Support

Hello, Yep, definitely on the right track. If you plan to store the USMT data on the local hard drive of the target device, then you are correct that you'll need to use the Wipe and load disk option - and it will be selected for you automatically. This will wipe all data from the target device except for a protected backup folder (C:\Backup by default), but leave the disk structure (existing partitions and volumes) intact. To create the media type you're referring to, you'll want to run Media Wizard, and select Offline deployment media. This will copy over the image (and split it, if needed), as well as all Platform Packs that you select. Only the correct PPK will ever be used at deployment time, so there's no harm in including packs for all of the models you intend to deploy to. If this is your first time testing USMT, we would definitely recommend backing up any data manually first, until you've confirmed that the deployment process works as intended with your image and media. If you have any questions or issues, feel free to reach out at support (at) smartdeploy.com. Glenn SmartDeploy Support

Hi John, We don't generally keep old versions of Platform Packs, so there is no method available for this. But you should certainly contact Support - if the current version of the Platform Pack is not working for you, we'll want to get that fixed for you. The first step would be to retrieve a logset from the device that experienced this issue. 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 it to 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. Glenn SmartDeploy Support

Hello, Sounds like you're on the right track with this script - you'll just need to make sure your command line is pointing to the correct drive letter in WindowsPE. The SmartDeploy WindowsPE environment uses the drive letters S:\ and T:\ for the system reserve and OS partitions on the target hard drive, respectively. So the drive letter that will become C:\ (as soon as the device reboots into Windows Setup) would be T:\, and that's the one you'll want to use. If the script was present on your reference VM prior to capture (e.g. in a C:\Scripts folder), then here is an example command line: wscript.exe T:\Scripts\Autoadmin.vbs If you continue to have issues, go ahead and email us at support (at) smartdeploy.com. Glenn SmartDeploy Support

Refer to this thread and send the capture.log to support @ smartdeploy .com Thanks, SmartDeploy Support

Please attach your C:\SmartDeploy\Logs\Capture.log from your SmartDeploy host and we can take a look. Thanks, SmartDeploy Support

Hello, The Recreate Drives option will wipe all data and disk structure (partitions and volumes) and recreate whatever was present in your image, so it is not suitable for any attempt to preserve data on the target device. The Wipe and load drives option will wipe all data only (leaving the disk structure intact), but it will not delete any files that are inside of a protected backup folder (C:\Backup by default). So while it is not supported to preserve a single partition on Disk 0, you should be able to accomplish the same result by putting the data you wish to preserve into the C:\Backup folder, and using the Wipe and Load drives option. This should work as long as there's adequate space on the drive after accounting for these files. If you have any questions, please feel free to reach out to support (at) smartdeploy.com Glenn SmartDeploy Support

Hi Horacio, At this time, WIndows 10 Version 1803 is not officially supported, but we're actively testing it right now - stay tuned. It's not always necessary for us to update the product to support a new Windows 10 version (although it was for the last version, 1709). In the meantime, you're welcome to go ahead and try deployment - we would just recommend starting with a fresh VM built with Windows 10 1803 media, and only testing on a non-production device, as we can't guarantee success just yet. Feel free to reach out to support (at) smartdeploy.com if you have any questions or issues. Glenn SmartDeploy Support

Hi there, We'll need to see a complete logset in order to troubleshoot this issue further. 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 it 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 submit it via the Support form, which includes a file upload option. Regards, Glenn