Issue with location of PSExec when running .bps file

[doug]

Thanks for the information. We’ll update this to work as expected in a future build. However, in either case, the immediate solution and the recommended way to avoid any issues, in general, is to put PsExec in your Windows PATH. So, for example you can just drop PsExec.exe in the C:Windows or C:WindowsSystem32 folder, and then you’ll never have an issue again. Or simply set the PATH to wherever you have the PsExec.exe – https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/path.mspx?mfr=true

We have heard of a few cases where a user has put psexec.exe in the PATH but for some reason has still had trouble, but then after moving psexec to the same location as the BatchPatch.exe, the problem disappeared. It’s not exactly clear why for some users the behavior is different. However, in either case we will address this in a future build so that it’s possible to hardcode into BatchPatch the location of psexec.

[Xenophane]

Don’t remember if this was ever fixed, just stumbled upon it again today…

If it was fixed at some point, it has been reintroduced 🙂

[doug]

One user determined that the firewall software in place at his organization was the cause of the issue. He was able to add a new exclusion rule to resolve it.

[Author]

Posts