Sort of. Enter-PSSession is backed by http or https [1] and is not as good as ssh. You can interact with PowerShell, but you can't interact with command-line programs launched from PS.

[1] Grep for "http" on this page: http://ss64.com/ps/enter-pssession.html

Most stuff I use have PS cmdlets so its not really an issue with me.

Yes, but only if both PCs are in the same domain. Getting PowerShell remoting to work in other environments requires a lot of configuration.

That's not true. I had it working over the internet, separate domains with public/private certs fairly easily.

I'd be interested in how you set it up, can you maybe share it somewhere?

Guides like https://wprogramming.wordpress.com/2011/07/11/remote-pssessi... don't seem "fairly easy" to me (that's why I said it requires a lot more configuration compared to Enter-PSSession when both parties are in the same domain).

There's a lot of waffle in that. If you actually look at the commands his asking you to enter, it isn't that much.

It's essentially, Enable-PSRemoting

And commands 1 to 3 in the following guide after Enable-PSRemoting. Try to ignore the waffle. You probably do want to to disable HTTP though.

http://www.sirchristian.net/blog/2013/03/11/using-powershell...

Trying to get SSH to work with certs can involve just as much or more stuff than that.

Maybe i'll write a super simple guide, just listing the bare commands, since the documentation/tutorials for powershell seem non-existent despite being pretty powerful..

If only that was cross platform like SSH is.