Jeff Harris

You'd first want to make sure you're able to sun the installation via command line on a test client, which a successful silent installation. Then try making a new pack, filling out all the informational fields and saving it before you add files. Then add the installation files and the set up the executable path, save, and try again. At deployment; .spk files are copied to the C:\Windows\SysWOW64\SmartDeploy\Sources folder, and extracted to the C:\Windows\Temp\SmartDeploy\Scratch folder where the installation is then run on the target machine. Also, it's always worth a test to deploy one of the application packs we provide for download to make sure that App Deployment is working correctly.

The first thing you should do if you haven't, is test an Application Package available for download from the console. This will make sure that the service is working as intended, then you can dig into why your custom pack isn't working. The next step is to try your App Pack deployment, watching the C:\Windows\Temp\SmartDeploy\Scratch folder on the target. Your App Pack contents will be extracted here. (It's removed after the install, or after a failure.) If you see the folder appear here, then you know your app pack is being copied and extracted successfully. This means that there's a problem with your syntax, or something else is blocking the installation. At this point, you can contact Support and send in your App Pack for us to test and we can see if it's related to your target, or the App Pack itself.

In the Application Manager window you have in your screenshot, right-click the Files node on the left, and click Add File to add your MSI file. Then, to the right of the executable location click Select, and select the msi file. This should automatically change your executable location in that field. Then edit it so that it looks like this; msiexec.exe /i "[ApplicationsFolder]\Zoom Video Conferencing\Files\ZoomInstallerFull.msi" You can leave your arguments as-in in the arguments field, and then you should see a successful deployment of the application.

You'd need an XML file, with the instructions for excluding files. I've attached a sample. Then you'd edit your SmartDeploy Answer File, the migration section specifically, to add additional scanState arguments, as below: Exclude-Sample.xml

In the Answer File Wizard, you'd move the WMI query to the top of the list, and set the query to SELECT SerialNumber FROM Win32_SystemEnclosure

When deploying in UEFI mode, you'll want Secure boot to be enabled. Sorry, we do not have a BIOS settings matrix, no.

When investigating why USMT is failing, you'd want to look at the ScanState log file, which would go in C:\Wndows\Temp on the target computer. If you're initiating the capture from the console, make sure that you've checked the box for "ignore access errors."

Hey Dale - When you capture your image, you have an opportunity to specify the Windows product key. If you do, the Answer File Wizard will detect this, and won't ask you for it again. You'll need to re-capture the image, to a new WIM file. If you prefer, you can skip the key in the Capture Wizard, and instead put it in the Answer File, where it will be easier to change going forward should you need too.

I believe this should be resolved in the next release.

Yes, it will skip them automatically do you do not need to edit any packs or create your own. (Unless you want too)

I may have spoke too quickly there. A restart may be required it the driver installation requires it. But Windows should prompt whichever user that a restart is required, and prompt to do it or defer. Things like BIOS updates and certain other things included in driver packs require a script to install. Anything like that in a driver isn't going to be applied when updating drivers via the console.

SmartDeploy won't restart a client following a driver update. There's not a real-time update, but you can look at the dism.txt file in C:\Platform where the drivers are copied. That file can tell you which drivers were installed, and if there were any that failed to install. As far as bandwidth management; that would need to be managed outside of the console, as we do not have that build into the product. Any remote actions like image/app/driver deployments have to be initiated from the console.

We have a video where I demonstrate how to customize the Start Menu and Task Bar here: https://support.smartdeploy.com/kb/article/3-customizing-the-start-menu-and-task-bar/ This should persist through deployments, as it's the method we use on our employee workstations as well.

That is interesting. Are there any errors or warnings in the Application Event log?

Do you have any anti-virus or other security software running on the Probook? That would be the first thing I'd look to disable and re-try.

Then please open a ticket and it will be sent to you that way.

Please download, rename to .vbs, and run the attached script on one of the affected systems, and then email the file that's created to support@smartdeploy.com, detailing this issue. We'll need to dig into this beyond forum replies to investigate this. SmartDeploy_Support.txt

Alright well we can't re-produce that error ourselves. I'd file a ticket with Support. Hopefully it doesn't require shipping us a unit. I don't see an HP ProDesk 600 G4 platform pack, only a G3, as what's in your screenshot above. You deployed to a 600 G4, with the client install option? Or just installed the client? Can you share version information on the wireless adapter driver?

I assume this is only happening on the HP ProDesk 600 G3 devices?

I notice you're on version 2.0.3030. Would you mind updating your console, and watching to see if the issue persists after the clients update themselves to 2.0.3040?

It appeared that the mps and the mps.xml file weren't in the Updates folder of the package they send. I confirmed that if they are, the /adminfile argument shouldn't be needed. I also discovered that I could not add the .mps.xml as an individual file to the Updates folder, getting an error about the path. I had to place the files into the Update folder, and then re-add the entire Visio installation folder back into the spk. (I have alerted the dev team to investigate this problem)

Do you see that same error message when you deploy one of the other packs? We'll probably need you to send logs into support@smartdeploy.com to investigate.

You receive this error, but files are still copied to the client? Are you able to deploy one of the apps that we have available for download successfully?

Aaron; how are you disabling the wireless adapters on these systems? We're not able to reproduce this error when disabling via command prompt, or the Control Panel.

Ok thanks Aaron. The greyed out text means the last heartbeat check didn't work. Good to see that some clients are still black, which means the client isn't failing. I've shared this thread with some members of the team here to see if we can determine what's going on.