Author: bladeraptor
Subject: psexec runs if started manually but not by process
Posted: 21 July 2013 at 5:08pm
Hi
I have a batch to do a software installation that uses xcopy and psexec among other tools to move files about and execute other batches.
This batch is populated with variables from a powershell script and then executed from that script.
The problem is that some of the elements of the batch such as xcopy run fine when called from the powershell (running under a service account with admin creds on all local and remote servers), but not the psexec commands. They seem not to even start - its almost like the batch process skips the psexec commands and moves further down the batch executing other elements
If I open a cmd dialogue window and call the batch manually psexec works every time - has anyone else seen this behavior or know what might be causing it?
Many thanks
Subject: psexec runs if started manually but not by process
Posted: 21 July 2013 at 5:08pm
Hi
I have a batch to do a software installation that uses xcopy and psexec among other tools to move files about and execute other batches.
This batch is populated with variables from a powershell script and then executed from that script.
The problem is that some of the elements of the batch such as xcopy run fine when called from the powershell (running under a service account with admin creds on all local and remote servers), but not the psexec commands. They seem not to even start - its almost like the batch process skips the psexec commands and moves further down the batch executing other elements
If I open a cmd dialogue window and call the batch manually psexec works every time - has anyone else seen this behavior or know what might be causing it?
Many thanks