Michael Yorke
Comments
-
Hi Jake, Yes, I'm deploying from an admin image for both 2016 and 2017. I usually check the logs within the subfolder of wherever the admin image is installed, for example \\CAD\Solidworks\Installs...
-
Odd. When I add the codes that Jake suggested, it works on my Solidworks 2017 SP5 administrative image deployment, but not on Solidworks 2016 SP5 administrative image. This is despite the 2016 depl...
-
Thanks. Very helpful. Although this does get Solidworks installed on the target computer, the PDQ task fails with "command script returned no error code". Is there a success code other than "0"?
-
Boom. Thanks Shane. This worked exactly as described - I had the option ticked in my OCT config, so unticked that, saved the changes and tested deployment again. All working good now.
-
+1 here. An app-store style interface would be great. If that's too much of a stretch, then just a web interface would be useful - when I get requests for software installs whilst out the office, I...
-
just to answer my own question. After further troubleshooting I had issues with the NetLogon service on my PC. This was down to a known bug in the version of Webroot I was using. Uninstalling Webro...
-
Hi, I too am getting this on PDQ Inventory. I have just downloaded the trial today as we have been a PDQ Deploy site for a while now. I'm running Inventory version 15.1.0.0 I have installed PDQ I...