Jeff Harris

USB is probably the best way to go, if you're unboxing new laptops. Unless you have a WDS host that you can upload your SmartDeploy boot image to, and PXE boot your new systems. 

The 3rd method for deploying with SmartDeploy involves pushing the deployment from the console to clients, which would require you to unbox the new systems, step through OOBE, then install the client, and get them connected to your host. 

I would first configure my Answer File to use the BIOS Asset Tag field for the computer name, if I hadn't done that already. Then I'd unbox a few laptops at a time, boot into BIOS and set the name Windows needs to use, and then boot into SmartDeploy and let the unattended deployment do it's thing. While those work, I'd get to unboxing the next round. 

You can also configure your Answer File to shut down after the initial deployment. This will allow you to grind through the first stage a bit faster. Then, as you need to deliver laptops to any person, or lab, the next time you turn them on, they'll complete the sysprep portion of the deployment. 

If you're talking about clients on the same local network as your console host, then it should be within about 3-5 minutes after the service starts. (It is on a delayed start, so give it extra time if the client has just booted.) If it's not connecting, then check that the service started successfully, and look for errors in the Application log in Event Viewer. 

If you're talking about off-site clients and connecting through the cloud, you want to make sure that you used the non-fqdn name of your console host, and not an IP. Additionally, you want to make sure that your console hostname isn't externally accessible from the internet. 

Lastly, you may need to block access to your console host via VPN if you want to use the remote/cloud deployments. (You can create a CNAME alias for you to use as an administrator if you need to RDP to the host yourself.) This is because the clients need to fail to reach the console host to switch to the cloud. If they can reach the host, it can get stuck in a semi-functional state, and fail to appear in the console. 

I've seen instances where the prefix and serial number comes to 16 or more characters, which is rejected by Windows. When this happens, it will move to the next naming convention in line. Less frequently, the serial number field is blank. 

It looks like TeamViewer has some extra steps to jump through for what you're trying to do. This link below has instructions to visit; Design & Deploy page to set up your customization within the TeamViewer Management Console. 

You'll likely need to start there. 

https://community.teamviewer.com/t5/Knowledge-Base/Mass-deployment-improvements/ta-p/39639

Here's another link for the customized "Full Client" installation.
https://community.teamviewer.com/t5/Knowledge-Base/Create-a-Custom-Full-Client/ta-p/73157

Lastly; I think you'll want to the using PsExec to test running this command line installation as System, as it will be installed by SmartDeploy. You will be able to test your install parameters and package a lot faster. Then once you get it, you can put it in an Application Pack. This process is detailed in this article: (At the bottom) https://support.smartdeploy.com/support/solutions/articles/48001062096-troubleshooting-application-pack-deployments

I've also seen this error, related to the specific file I was trying to save in the Files folder of the Answer File. Confirm this by creating the pack first without any files, and save it. Then try adding the MSI and trying again. 

Please reach out to support either via email, (support@smartdeploy.com) or the ticket for to request this script; https://support.smartdeploy.com/support/tickets/new

You want to download the O365 source files ahead of time, and include them in the Application Pack. Then you would be running the command "setup.exe /configure configuration.xml" in the app pack, with your custom XML. 

We'd have to see some logs, but when the Deploy wizard prompts for an image, it's because the credentials saved in the Answer File are no longer valid, the deployment media was made without the updated Answer File, or there's a networking issue in SmartPE. 

On 4/18/2020 at 2:18 PM, JayM said:

I'm having the same issue... But after imaging with a stick, my server couldn't remote deploy the image to the client anymore. It can report heartbeat though.

Are you saying that you deployed with USB media, and following that the machine appeared in Computer Management, but you're not able to deploy an image then? We'd need to know more about this scenario. Is the client local or cloud, not connected via VPN, etc. Would be best to reach out to support via email or the form for investigating. 

I would first check that all traffic to *.smartdeploy.com is allowed, and that the traffic there is exempt from SSL Inspection. 

In cases like this, if you're going to place any scripts or files to run as tasks, it's best to put them in a folder such as C:\Temp\. 

That is correct; we are working on how to better address a previously failed Application Pack deployment. The presence of the !sdspk folder in C:\Windows\Temp\ is a good indication that an installation is stuck, along with any files in the C:\Windows\syswow64\SmartDeploy\sources folder. 

We do check for those when we're troubleshooting any deployments. 

First I’d check the Application log in Event Viewer for any errors related to SmartDeploy. You may need to reach out to Support depending on what you see.

Additionally, check this URL for port information and some powershell commands to test them.

https://support.smartdeploy.com/support/solutions/articles/48000968329-which-ports-are-required-by-smartdeploy-

First, I would check C:\Platform on the target system to make sure the Platform Pack was copied there. Then check the System log in Event Viewer so see if drivers are being injected. 

This is likely due to a problem with the certificates created by SmartDeploy. Unfortunately you'll need to clear them out and re-install SmartDeploy to repair this issue.  

Please email support with your company email, and we can assist in helping you. 

Your additional users should be able to provide the email address that you currently use to log into SmartDeploy. You'll receive an email to approve the addition of their accounts. 

Our Platform Pack download endpoints are hosted in Azure, and thus we don't have much in the way of investigating bandwidth. Are any other packs downloading as slow?

Keep in mind that SmartDeploy won't upgrade Windows 7 to 10. It will wipe the disk and apply your image as configured in your Reference VM. 

You can migrate the user data in 1 of 2 ways; configure it in the Answer File as you mentioned, or install the SmartDeploy client on the Windows 7 client, and use the Computer Management workspace to capture the user state before deploying your image, and then restoring it the same way. 

SmartDeploy uses Microsoft's User State Migration Tool for this process. 

Hi Sean, 

There isn't a way to track the process of a deployment aside from going and looking directly on the machine. 4 hours is certainly to long. I'd be interested to know what's on-screen on the device, and would want to see logs collected by booting back into SmartDeploy and clicking Collect Logs on the main menu. 

You'll probably want to reach out to support for more guidance. 

You can create Application Packs for running PowerShell scripts, and push those to your SmartDeploy clients. Here's our KB article for creating custom Application Packs; 
https://support.smartdeploy.com/support/solutions/articles/48000960633-create-your-own-custom-application-pack

You'll need to add PowerShell.exe -NoProfile -NonInteractive -ExecutionPolicy bypass -File to the start of the executable path after selecting your script,, per the documentaiton. 

Hi Bryan, 

We'll need you to email support, detailing how it's breaking, along with logs from a failed deployment so that we can investigate what's happening. 

Please email support for more help with his issue. 

Did you receive an error when you mapped a network drive to the share where your image is kept?

If you have a valid IP, you should be able to click the Network button and specify a \\HostName\ShareName to map a network drive, then browse back through "This PC" to see the drive and pull the image off the network. 

I was wrong; that Platform Pack doesn't include a WinPE node, which means it wasn't expected to need additional drivers when booted into WinPE. 

All you should need to do is boot the VM to the ISO, and the default network settings should allow the VM to reach your network. Is there no IP address listed in the bottom right corner?

We do have a VMware Workstation 12 Platform Pack. I would download that, and make sure it's included when you re-create your SmartDeploy ISO to re-try the deployment. 

Typically it's not required, however I don't have v12 to install and test.