Running winrs from Team Build Hangs

Question

I have a step in my TFS build workflow that tries to invoke a command on a remote machine using winrs. I use the call process task and pass powershell to it, and then pass it to a script that contains something like

winrs -r:remote.server.com ipconfig

The team works very well, and I can see the output in the build logs, but it all seems to stop at this point. I can go into the remote box and confirm that ipconfig is not running, so the process has finished, but it looks like winrs is not returning. Is there some kind of trick I'm missing, maybe

-justBloodyWork

flag?

Answer 1

: https://serverfault.com/questions/135070/why-does-my-powershell-script-hang-when-called-in-psexec-via-a-batch-cmd-file

POSH. , stdin . : winrs -r: remote.server.com ipconfig < NUL

Answer 2

Try -nop. , .

Answer 3

The Bamboo build server is working with the same problem. <NUL works for bat files, but <broke in powershell. To provide standard input in powershell, the pipe is in $ null: $null | winrs -r:remote.server.com ipconfig