PsExec Throws Error Messages, but works without any problems

Question

So we are using PsExec a lot in our automations to install virtual machines, as we can\'t use ps remote sessions with our windows 2003 machines. Everything works great and t

Answer 1

redirect stderr to null worked best for me. see below link

Error when calling 3rd party executable from Powershell when using an IDE

Here's the relevant section from that link:

To avoid this you can redirect stderr to null e.g.:

du 2> $null Essentially the console host and ISE (as well as remoting) treat the stderr stream differently. On the console host it was important for PowerShell to support applications like edit.com to work along with other applications that write colored output and errors to the screen. If the I/O stream is not redirected on console host, PowerShell gives the native EXE a console handle to write to directly. This bypasses PowerShell so PowerShell can't see that there are errors written so it can't report the error via $error or by writing to PowerShell's stderr stream. ISE and remoting don't need to support this scenario so they do see the errors on stderr and subsequently write the error and update $error.

.\PsExec.exe \$hostname -u $script:userName -p $script:password /accepteula -h cmd /c $powerShellArgs 2> $null