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. 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.
  2. Then please open a ticket and it will be sent to you that way.
  3. 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
  4. 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?
  5. I assume this is only happening on the HP ProDesk 600 G3 devices?
  6. 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?
  7. 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)
  8. 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.
  9. 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?
  10. 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.
  11. 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.
  12. In the Computer Management console; are the clients generating this error appearing in bold/regular text?
  13. Interesting. Do these errors stop if you enable the wireless adapter?
  14. On a second look, this blog post has instructions for creating an MSP file which would automatically be applied when setup is run. It mentions MDT, however if you can create the MSP file and configure it per this blog, then you should be able to add the Visio install folder to an App Pack, in which setup would be run, detect this MSP file and install as configured. https://web.sas.upenn.edu/jasonrw/2015/11/03/automate-the-install-of-microsoft-office-2016-with-an-msp-file/
  15. I do believe that you'd want to put your XML in the same older as setup.exe, then add that folder to the App Pack. Then you'd add the arguments: /configure installconfig.xml
  • Create New...