I had no problem configuring SSH Remoting. Automation is only good when you keep the humans out of the loop. No?Īppreciate any feedback, and especially appreciate any alternative approaches that make use of PWSH's SSH Remoting capabilities without having to fetch a password from the user before using an Invoke-Command to execute commands on a remote computer. Maybe I am missing something here but, is there a good reason for not mirroring how PWSH's WinRM sessions are handled, in terms of available parameters? Not an expert by any stretch but, I would think that this would be a good feature, if not a necessity, to keep around in a cross-platform environment. Just a quick reach out to the PSS Community to see if anyone has a good answer for why Powershell 7.2/3 (aka., PWSH) SSH Remoting does not appear to support non-interactive SSH Remoting sessions in Cmdlets like Invoke-Command, Enter-PSSession, New-PSSession, etc.)? Basically, you can only pass half the user credentials (username only) in the Cmdlet and no support for passing the corresponding user password as a secure string.

OS: Windows 10 Pro for Workstations (64 Bit)

Powershell 7 ssh