Jump to content

Jeff Harris

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About Jeff Harris

  • Rank
    Support Team

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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."
  2. 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.
  3. I believe this should be resolved in the next release.
  4. Yes, it will skip them automatically do you do not need to edit any packs or create your own. (Unless you want too)
  5. 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.
  6. 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.
  7. 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.
  8. That is interesting. Are there any errors or warnings in the Application Event log?
  9. 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.
  10. Then please open a ticket and it will be sent to you that way.
  11. 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
  12. 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?
  13. I assume this is only happening on the HP ProDesk 600 G3 devices?
  14. 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?
  15. 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)
  • Create New...