@Troye-Johnson Your script with the creds works perfect with the Server/Client setup of PDQ Deploy. Thanks again for the help!

@x23piracy I actually am not sure. They provided a link to me via email for the update, so my assumption is that it is not. You can always reach out to them and get it. Their support is excellent.

@Troye-Johnson I should have checked a littler harder. I found the snapin pack option when creating a snapin. It pays to know how to read.

@Troye-Johnson Just had a chance to dig into your script. Very new to fog, so forgive my ignorance. How are you getting the password file and key to the tmp fog service directory on the client? I don’t see a way to copy supporting files in the snapin manager in FOG?

@Troye-Johnson Excellent. I will let you know what I find out! Thanks again.

@Bob-Henderson Interesting. Probably a good thing each of our techs are licensed for PDQ Deploy then! Good work though.

@Troye-Johnson Thanks for this. PDQ actually provided me with an update that fixes this issue on v13. No need for the registry setting change. The update put us on v13.2.0.0.

@Troye-Johnson I forgot to ask, which I am sure I will find out anyway through testing, but is your FOG Service running as the default SYSTEM account on the client using this script? Since you are specifying creds in the script, this doesn’t matter now, I assume.

@Troye-Johnson Thank you very much for this. I will report back if this works for server mode of PDQ Deploy.

@Troye-Johnson Did you ever get an answer to your question? I am running into the exact same problem. Since the service runs as SYSTEM, it doesn’t have permissions to even remote powershell to our PDQ server.