helpdesk
Comments
-
Bingo! This worked perfectly. My mistake for not spotting a CMD variable wouldn't be compatible with Powershell. Many thanks!
-
dannybethell Did you find a solution to this? I see the official blog article has been updated to remove the powershell script. TIA
-
+1 for this.
-
Colby Bouma, thanks again. That worked! I'll post my findings here for anyone else who is looking to do this... I re-deployed the LAPS client using msiexec.exe /i "LAPS.x64.msi" ALLUSERS=1 /qn /no...
-
I'm trying to follow your suggestion and create a tool. https://help.pdq.com/hc/en-us/community/posts/4411254123931/comments/4411284728347 The tool is set to Local, which I understood to mean it wo...
-
Colby Bouma, thanks! As an alternative, I guess I could push out the powershell module when deploying the LAPS client to the endpoints, then execute the command locally on the endpoints, correct?
-
Colby Bouma, perfect! I have run all these and they are working as expected. I'll keep an eye out for any issues. Many thanks!
-
I came here looking for this. I have the same request as nfelbinger - I have a custom exit code (a critical application was running at the time of the deployment) and need to send the machine in th...
-
Amazing! Thanks Colby. This works perfectly when testing on its own. It doesn't work in PRTG - so I need to take it up with them and see what's happening and try to get the logs. I'll post back her...
-
Hi Shaun, Just remember that the script is just handling whether the users wants to run the upgrade now or later, then the PDQ deploy schedule handles running the script on machines which don't hav...