BatchPatch Forums Home › Forums › Re: Strange psexec workgroup behavior
This is not a psexec issue. BatchPatch uses multiple methods for authentication beyond just psexec, due to some special requirements it has. And so when you test psexec directly at the command line it works fine, but when you use BatchPatch in this scenario, access is denied. When you’re using BatchPatch in a WORKGROUP (NOT in a domain) environment, there are special considerations to pay attention to. Please see below.
Special Considerations for BatchPatch Authentication in a WORKGROUP:
1. The built-in local administrator account on all computers in the WORKGROUP must be set with the exact same password. Note that I’m referring to THE account named “administrator.” It is not sufficient to use an account with a different name, even if that different account is a member of the local administrators group)
2. The computer that you use to run BatchPatch must be logged on with this built-in local administrator account.
3. BatchPatch must be set to use Integrated Security. Do NOT use alternate credentials within BatchPatch when you’re working under these circumstances.
If the 3 above steps are followed, BatchPatch will work in a WORKGROUP environment. This was tested on 5/31/2013, running BatchPatch on a Win 7 machine with a Win 2008 target, and then also running BatchPatch on a Win 2003 machine with a Win 2008 target.
-Doug