Repository navigation
Missing psexec.exe in the Deployment folder? #2
Description
Hi Charles, noted you were looking in to another issue with the Update Compliance Configuration Script, so hoping you're the guy.
Found that the current download doesn't have the psexec.exe file in the Deployment folder, so I'm getting a '..\Psexec.exe is not recognised as an internal or external command..' type error when you run the RunConfig.bat.
That file got missed out accidently?
Activity
cinglis-msft commentedon Jun 12, 2020
Yes, looks like it. We're working on fixing a few things with the script. Thank you for bringing this to our attention
SteveBurkettNZ commentedon Jun 15, 2020
No probs. BTW, because it's using PSExec.exe, the Attack Surface Reduction rule for Block process creations originating from PSExec and WMI commands triggers. So any customers with locked down Windows 10 configs or running MDATP will likely have issues with the Update Compliance script as it stands. It's a little unusual to see PSExec being used like this.
braddonegan commentedon Oct 26, 2020
Hello,
We ended up taking out the psexec line in the Deployment script and changing it to this:
%PowershellHome%\powershell.exe -ExecutionPolicy Bypass -noexit -Command %powershellCommand%Didn't see a reason to have it run on all the clients for broad deployment.
Thanks!
cinglis-msft commentedon Oct 26, 2020
Thanks for the update, we'll keep this in mind as we work on the next version. There are some changing requirements, hence the delay in the next version.