Error 1621: Please make sure that PSEXEC.exe is in your system Path

[Marco Reichartz]

Hi,

we have a problem with BatchPatch Version 20.3.10.17.47 managing Windows Server in another domain and Windows Server not joined to any domain.

Although we provide remote credentials and place PSEXEC.EXE in C:\Windows we get “Error 1621: Invalid Directory. Please make sure that PSEXEC.exe is in your system PATH.

I´ve made a rollback to BatchPatch version 2024.7.16.15.21 (which we used till lately) and all works fine.

Any idea how to get around the error in the current version?

[doug]

I would start by going to Tools > Settings > Remote Execution > Use psexec.exe custom filepath. Configure the ‘Use psexec.exe custom filepath’ setting to point to the PsExec.exe on your system.

[Marco Reichartz]

Hi Doug,

I´ve already tried this without success.
Tried to set a local directory path containing the psexec.exe.

Whenever I try to execute tasks on a system in a remote domain (same AD tree) or workgroup (with supplied remote credetials) I get error 1621.

Systems within my user´s domain react as expected.

[doug]

When you say “remote domain” what exactly do you mean? If it’s working for a local domain but not a remote domain, there is your problem. Presumably there is some type of communication that is not permitted to the remote domain from your local domain. I would suggest very carefully going through the troubleshooting guide, step by step, until you find where exactly the issue is.

[Marco Reichartz]

Let me try to clarify:

We have one AD tree with a nearly empty root domain and a productive sub-domain. I start BatchPatch with Domain-Admin credentials (my user is actually member of the Domain-Admins group) of the sub-domain.
When I patch the domain-controllers of the root domain, I used to add them to BatchPatch and specify root domain adminuser credentials by the means of “specify alternate login credentials”.
We also have two servers (facility management) that are not domain-joined. So we added those two to BatchPatch and specified the local admin credentials by “specify alternate login credentials”.
Besides this we have about 250 sub-domain-joined servers, that we also patch by BatchPatch.

This worked well until we made the update to the last BatchPatch Version.

With the current version of BatchPatch I’m still able to patch the servers within the subdomain (remember: i am domain-admin). BatchPatch starts PSEXEC and everything works fine.

I`m unable to patch the servers in the root domain and the two “workgroup server”.
The WMI connection is successfull (see Troubelshooting guide) but BatchPatch does not start the local PSEXEC.EXE. Error 1621.

I followed the troubleshooting guide and end up with WMI fine, PSEXEC for servers ins the same domain fine, server with “alternate credentials specified” PSEXEC is not found.

Switching back to the older BatchPatch.Eexe everything works like a charm.

[doug]

I sent you an email to you to see if we can work on this directly so that I can see screenshots and more details.

[doug]

For anyone else who comes across this thread, it turned out he was running the batchpatch.exe from a network location. Resolution was to move batchpatch.exe to the local computer.

[Author]

Posts