- This topic has 4 replies, 2 voices, and was last updated 6 years, 3 months ago by .
-
Posts
-
Hello,
Attempting to use BatchPatch and it seems anything that relies on PsExec is not working. PsExec is installed in C:Windows and I even attempted to move the PsExec.exe into the same directory as BatchPatch. I can run PsExec fine on its own and even connect to the target computer fine and run actions on it.
In BatchPatch I can pull information fine and when attempting to check for updates I can even see that the agent was copied correctly to the target computer in C:progamfilesbatchpatch
When actions run that need PsExec they simply sit on “Queued…”
Looking at the processes on the target computer nothing seems to start when attempting to run actions on it remotely using BatchPatch.
System Info:
BatchPatch computer (evaluation mode): Windows 10 .Net 4.7
Remote Computer: Windows 2008 R2
Thanks for any help!
It sounds like something is preventing psexec.exe from running. There are a couple/few possibilities.
1. Make sure that there isn’t a hidden ‘Open File – Security warning’ popping up and waiting for a response. Since psexec.exe was downloaded from the web, Windows can sometimes prevent it from running by popping a dialog that you have to click on. However, if this dialog pops up in the background, you might not know it’s waiting for input. If the dialog is the cause, there is a checkbox on the dialog that can be modified so that the dialog does not continue to pop up every time psexec.exe is executed.
2. If you are running the BatchPatch.exe as a different logon account than the account that you are logged on to the computer with (so like if you use right-click run-as to launch BatchPatch), make sure that you have logged on to the computer one time as the run-as account. And also when logged on with that run-as logon account, launch BatchPatch.exe and attempt an action that uses psexec. Once things are working properly in this account, then you can switch to the other account where you may use run-as to run the batchpatch.exe successfully as the run-as account.
3. Another thing to consider is anti-virus or other similar security software. This could be an issue. Aside from disabling or removing the AV software on both the BP computer and the target computer, one option that sometimes can work to bypass the AV issue is to provide a custom name for the psexec service. This is done under ‘Tools > Settings > Remote Execution > Use psexec -r switch…’
I can’t think of any other possible causes for the problem you are experiencing.
-Doug
I’m glad you got it worked out. FYI there’s no reason you shouldn’t be able to use run-as from your other account. We have many customers who do this, and we do it here all the time. If it’s not working like that, I’m not quite sure why, but it’s gotta be something about your environment. I’m sure it could be made to work.
-Doug
- You must be logged in to reply to this topic.