- This topic has 6 replies, 3 voices, and was last updated 9 years, 5 months ago by .
-
Posts
-
I responded directly to the email you sent me. Let’s figure out the issue over email, and then I’ll post the resolution here afterward, once we’ve figured out what’s going on.
Thanks,
Doug
We eventually discovered that McAfee software was causing the problem. Disabling it on the target host (or adding an exclusion for BatchPatchRemoteAgent.exe and PSEXECSVC.exe) solved the problem.
-Doug
We have isolated the issue that’s causing the 2250 error, and the fix for it was published in the build released on January 1, 2014.
If you need to work around this issue for some reason, follow the steps below:
The workaround that we are recommending for the time being is to stop using alternate credentials within BatchPatch. Instead, launch BatchPatch with the credentials of the other user, as described below.
1. Place BatchPatch.exe in a public directory, such as C:Program FilesBatchPatchBatchPatch.exe. For this workaround to be successful it is NOT sufficient to run BatchPatch from a user profile directory such as the desktop.
2. Launch BatchPatch from the public directory by shift-right-clicking on it and choosing “run as different user.” And then use the credentials of a user that has local administrative permissions on target computers.
3. Once BatchPatch is running as the different user, you can start patching target systems without using alternate credentials. Just use integrated security and everything will work.
4. Launch one separate instance of BatchPatch for each set of credentials that you desire to use for patching target systems.
hi,
can you please write in ful the path for the batchpatchagent.exe i can’t seem to locate it 🙁
thanks
giles.
found it C:Program FilesBatchPatchBatchPatchRemoteAgent.exe
was tricky cos it keeps on disappearing 🙁
It keeps disappearing because it is only temporarily deployed by BatchPatch and then removed when BatchPatch is done working.
-Doug
- You must be logged in to reply to this topic.