Have you actually tried to use Powershell remoting? When you try to do remote automation on Windows machines you land in this Bizarro world where some things work with psexec, some with remoting, and some not at all.
A working, secure protocol where things actually execute on the remote machine will be very welcome, and when we think SSH that's what we're excited about.
(The hit-and-miss nonsense I'm talking about was a script that reached out to a collection of machines, shut down a Win service, set it to "manual", deleted its log file, then set it back to auto, then started the service. It was a hodge-podge of psexec, remotable commandlets, and Powershell remoting. There may have been whiffs of WinRM in there too, but I'm trying to forget it.)
The only hassle I've had is trying to use external resources while already in a session. e.g. enter-pssession "someserver"; copy-item "\\netshare" .
In thins case you need to further enable CredSSP on your domain to allow passing on your auth credentials through the session to the third machine.
Any cmdlet I've seen that doesn't take a session (wmi or cim) I've just wrapped up into invoke-expression -computername "commands..."
Ps remoting lets me do great things like import module from servers to clients that I don't have remote tools installed on. e.eg. $session = new-cimInstance "domainController"; import-module activedirectory -sessions $session
A working, secure protocol where things actually execute on the remote machine will be very welcome, and when we think SSH that's what we're excited about.
(The hit-and-miss nonsense I'm talking about was a script that reached out to a collection of machines, shut down a Win service, set it to "manual", deleted its log file, then set it back to auto, then started the service. It was a hodge-podge of psexec, remotable commandlets, and Powershell remoting. There may have been whiffs of WinRM in there too, but I'm trying to forget it.)