SmartDeploySupport

Hello andrew.holt With these PC's in computer management from the console, you can simply delete them from there and the clients (these machines) will receive the message to uninstall themselves.

Hi Kamsobe, We'll reach out via email to assist further. Glenn SmartDeploy Support

Hi Allen, We have a script that can assist with this - you won't be able to push it out with the new console, obviously, but if you have some other means of pushing it out to each endpoint, it would have the effect of pointing that endpoint toward whatever hostname or IP address you specify. I've opened a support ticket for you - please expect an email shortly. Glenn SmartDeploy Support

Hi Kamsobe, If you reimage a computer with SmartDeploy, that machine is counted against your license count. With Per Machine licenses, you can reimage the same computer as many times as you wish without ever consuming more than 1 license per machine. A SmartDeploy license remains attached to that computer until you decommission it, which can be done via the SmartDeploy customer portal. This should only be done for computers that are leaving your environment permanently and will never again be reimaged with SmartDeploy. If you have any further licensing questions, please feel free to reach out to licensing@smartdeploy.com. Glenn SmartDeploy Support

Hi Benjamin, They're one and the same - a search for Latitude 3189 only yields one result from Dell: https://www.dell.com/support/home/us/en/04/product-support/product/latitude-11-3189-2-in-1-laptop/overview When we're naming a pack, we tend to respect whatever model identifier is listed in the system firmware, which in this case is simply Latitude 3189. Dell is generally pretty good about making their online listings match what's in the system firmware, but there are exceptions, and this is one of them. Go ahead and download the pack and let us know if you have any issues - support@smartdeploy.com. Glenn SmartDeploy Support

Hi the_ringleader, Given the specificity of the issue, we're prepping a VM to test it on our end right now. We can't be sure if we'll be able to find a resolution for this if it's a bad update breaking Sysprep (until Microsoft releases an update of their own to fix it), but we'll see what we can do in the meantime. Stay tuned - we'll post any updates here. Glenn SmartDeploy Support

Hello, We would need to see the full deployment logs, which would include the sysprep logs. Restart the machine back into the SmartDeploy boot environment and click Collect Logs. Save the resulting zip and submit a support request here and we can investigate further. Be sure to reference this thread in the ticket. Thanks, Devon SmartDeploy Support

Thanks for confirming Tom! Devon SmartDeploy Support

Oh, probably TPM related... it's asking for a StartupKey or Password because it can't use the TPM. Can you verify the TPM is functional in tpm.msc?

Looks like you're using Windows 10 1607? Perhaps the command is different in that old version?... manage-bde /on /? Is the option -RecoveryPassword or -Password ? In newer versions of Windows 10, it's -RecoveryPassword

Sounds good! Appreciate the update. Thanks, Devon SmartDeploy Support

Hello, This likely indicates a systemic communications issue between your console and your clients. We can help troubleshoot this, but we'll need you to go ahead and reach out to support@smartdeploy.com for next steps. Please mention my name and include a link to this thread. Glenn SmartDeploy Support

Hi Tom, Can you email your latest C:\SmartDeploy\Logs\Media.log from the SmartDeploy host? We may have to add dism to your trusted rules as well. You can reference this forum post. https://support.smartdeploy.com/new Thanks, Devon SmartDeploy Support

Hi Gordie, I assume this error occurs when you're migrating data? Are you doing it from the console or deployment? Please submit a ticket here and we can gather more details and corresponding logs. Please reference this thread. Thanks, SmartDeploy Support Devon

Hi Blargh, This is supported. Any SmartDeploy user with a current support contract can open up a Platform Pack using Platform Manager (the program that opens when you right-click | Edit a Platform Pack from the console, or double-click on one in Windows Explorer). You can then right-click any folder and Extract. If you expand the make | model | OS notes on the left pane, and click on SystemUpdate, you can see the current task that is being executed (and during which phase of deployment). Take note of this before you make any changes. We install SystemUpdate using a Setup.vbs script, so you'll want to make the changes by editing that script, then re-add the folder and re-add the Task as written (likely wscript.exe [PlatformFolder]\SystemUpdate\Setup.vbs in the Specialize phase). Out of curiosity, what change were you planning to make to installing Lenovo SystemUpdate? We've generally just done a silent install of the utility. Glenn SmartDeploy Support

Hi Billy, If you'd like some assistance troubleshooting this, please go ahead and reach out to us at support@smartdeploy.com, and be sure to reference this DeployCentral thread. Glenn SmartDeploy Support

Added a note of clarification above, for everyone's info. Glenn SmartDeploy Support

Hi Dustin, We'll follow up with you via email about this - we'll need a bit more info about your environment to determine how best to proceed. Expect an email shortly. Glenn SmartDeploy Support

Hi C, The default answer file mode is unattended - and to be clear, if an answer file is unattended, the "skip=#" values will be ignored, and the entirety of Deploy Wizard will be hidden. This is how this option behaved previously, and this has not changed. What's new is - if you click into the Answer File Wizard | Advanced options, and change the answer file from unattended to attended, then the checkboxes to skip each Deploy Wizard page will appear, and will be respected by any attended media that uses the new answer file. Edit: Please note, console-initiated deployments are always unattended, and skip values are not supported for this method. But they can be used for USB/DVD media, or WDS/PXE boot media. Please feel free to reach out if you have any questions or issues. Glenn SmartDeploy Support

Hi Amanda, The 'warm capture' is typically VM specific. There could be something about your host environment that is interfering with the functionality of Capture Wizard - domain security policy and antivirus software (this isn't the case in your scenario) are common culprits. It is for this reason that we provide two different methods for capture, and I can assure you that the resulting .wim file is identical whether it is captured using either method (it is literally the same Capture Wizard running in either context - the only difference is the OS environment that it is being executed in). Were currently in the process of making the Capture wizards performance better but the warm capture method isn't intended to be an alternative, per se - just another tool in the toolbox. We have many customers whose secure environments render it impractical to run Capture Wizard directly, and they've decided as a practical matter that it's easiest to just run warm capture every time they need to capture a new image. If you have any further questions, please feel free to reach out to us at support@smartdeploy.com

Hello Tfallert, You can use your skip feature which is illustrated on page 118 in our user guide here You'll be able to skip certain pages in the deploy wizard so that it will prompt you for the computer name.

Hi Jason, That's great news, thanks for sharing it. Hopefully this issue is finally over. Glenn SmartDeploy Support

Hi DeJeon, No, by design, computers with the SmartDeploy client installed can only be managed by a single specific console, identified by the hostname or IP that you specified when you created the installer package. Glenn SmartDeploy Support

Hi DeJeon, You've hit upon the fundamental issue here, which is that USB passthrough from a host to a VM is unreliable. Many of them rely on virtual machine additions that simply don't offer the same level of functionality that would be present on a physical host. Because SmartDeploy is licensed per deployed endpoint, there is no licensing restriction that would prevent you from installing the SmartDeploy console on multiple computers. Rather than struggle with trying to make passthrough work reliably, our recommendation is to simply install SmartDeploy on a secondary physical workstation (such as any standard business laptop or desktop) for the purpose of creating USB media. You can temporarily copy down any images or Platform Packs that you plan to use, and then create the media without issue. Please feel free to reach out if you have any questions or issues - support@smartdeploy.com. Glenn SmartDeploy Support

Hi Ajainin, We'll need to see a complete logset from this deployment - we'll send a reply to your email with further instructions. Glenn SmartDeploy Support