I know this is a little long-winded – hopefully it’s clear.
I’m having trouble running PsExec commands through BatchPatch as a domain admin user. For my test, I’m launching a saved deployment that runs a PowerShell script that performs a simple query on the host and returns the result.
If I log into Windows using the actual Administrator account everything works fine.
If I log into Windows using my personal domain admin account, launch BatchPatch using Run as administrator and attempt the same deployment, BatchPatch waits forever with the message Deployment: Executing. If I go to the host machine (currently my local machine, but it’s the same with a remote machine) and kill the PsExec process, the correct result is returned to BatchPatch in the Deployment Output Log column, but the returned message is Deployment Error. It complains that the process cannot access BatchPatchdeploymenttemp because it’s in use by another process. This isn’t surprising to me since I had to kill it, I figure anything I get after that is questionable. It does kind of surprise me that the query result comes back.
I’ve tried setting the Remote Execution settings to rename the PsExec service with the same result.
I’ve copied the Command to execute from the saved deployment and tried running just the script portion without PsExec in a command prompt window and it works fine.
I then tried running the entire command including the PsExec part in a command prompt window, and it also works fine.
I know it must be some kind of permission thing, since everything works fine as Administrator, but I can’t figure out why my commands work as a domain admin from the command prompt, but not from BatchPatch.
Any help would be appreciated.
Thanks,
Sue