PowerShell remoting in PowerShell 7 should use PowerShell.7 endpoint by default

[alexandair]

At the moment, PowerShell remoting in PowerShell 7 is using Windows PowerShell's microsoft.powershell endpoint as the default one. That endpoint is not even visible/discoverable when you run Get-PSSessionConfiguration.

By default, targets should be PS7 endpoints and you could specify -ConfigurationName microsoft.powershell, if you really want to execute in the context of Windows PowerShell.

[SteveL-MSFT]

This makes sense particularly as compatibility with WinPS in PS7 has improved significantly compared to PSCore6

[iSazonov]

In future (after we will have many PS7 installations) we could have PS7 endpoint first and fallback to WinPS one.

[alexandair]

I would like to hear a reason why should PS7 fallback to WinPS endpoint.

[iSazonov]

We keep backward compatibility and modern management tools may work with old endpoints.

[ThomasNieto]

This might need to go into its own issue report but Install-PowerShellRemoting.ps1 and Enable-PSRemoting create different endpoint names and might not work correctly with this feature if implemented.

[Jaykul]

There are many reason why WinRM should always default to "microsoft.powershell" regardless of the version of the PowerShell client:

• This endpoint is installed and enabled by default on Windows Server -- including in Azure.
• The default endpoint should always be the unversioned endpoint. Otherwise you'd have to know what was available on each each remote!
• The version of PowerShell a client is running should not affect which endpoint you connect to,

You know, the other problem is that there's no other endpoint you can connect to:

• New versions of PowerShell do not register endpoints by default. There's no point defaulting to connect to an endpoint that won't exist by default.
• Organizations that do switch to new versions of PowerShell are required to install it during initialization, and must configure the endpoints themselves, so they can configure whatever endpoints they want to use by default.

Frankly, at this point, that doesn't seem that likely, based on the conversations I've had. It's more likely that devs and admins are installing new client versions on their personal development and administration machines, but to do their jobs, they still connect to whatever comes pre-configured on their servers.

Because of that, I think that if we are ready to say a new version of PowerShell should be the default, we should update the default endpoint to point to it. Register the versioned endpoints for use by software that requires a particular version (and add a PowerShell.5) but update the default to point at the latest version of PowerShell, and turn on remoting by default (on servers). Or rather, check the remoting box it by default if remoting is already enabled on the OS, and add another checkbox (also checked) to take over the default endpoint.

[doctordns]

Should PowerShell 7 always create a remoting endpoint during installation?
Or should that be the task of a specific command (Install-PowerShell7Remoting)?

[Jaykul]

Thomas Lee (@doctordns) I would say it could depend on whether WinRM is already enabled or not.

That is, if you're installing where WinRM remoting is already enabled ...

• I would argue for adding "powershell.7"
• I would argue if "microsoft.powershell" points at PowerShell 5, add a "powershell.5" if it's not there already
• I would not argue against updating "microsoft.powershell" to point at 7 ...

Otherwise... regardless of whether it's Windows, Mac, or Linux ... I think that if WinRM is not already enabled, you shouldn't enable it by default, and there's no point setting up endpoints if it's not, right?

[doctordns]

I believe installing PowerShell 7 should create meaningful endpoints. That way, everything works if WINRM is enabled and can work if you do enable WInRM. If you are arguing NOT to create the endpoint I'd agree but only if enabling WInRM then creates the required endpoint.

IIRC, you have the PowerShell 5 endpoint whether or not you have WinRM enabled. I'd like that same behaviour when I install PowerShell 7.

Also, I would like a PowerShell.5 and a PowerShell.7 endpoints created explicitly. For backwards compatibility reasons the Microsoft.PowerShell should remain as is.

[SteveL-MSFT]

A less breaking change would be for PS7 client to use PowerShell.7 remoting endpoint by default instead of Microsoft.PowerShell which (currently) always points to the inbox Windows PowerShell

[iSazonov]

A less breaking change would be for PS7 client to use PowerShell.7 remoting endpoint by default instead of Microsoft.PowerShell

And fallback to Microsoft.PowerShell endpoint.