CHGLOG PowerShell 7 vs 5.1: Check for Cmdlet Parameter Support

Windows PowerShellAssuming that you have already run Update-Help -force -UICulture “en-us” on your local machine, you can check if a set of cmdlets support a particular parameter.

Staying on the *-Service cmdlets, execute the following to check which cmdlet supports the –ComputerName parameter in your target PowerShell version:

$s = Get-Help *-service
$ | % { $Psitem; Get-Help $PSItem -Parameter ComputerName }



CHGLOG PowerShell 7 vs 5.1: Get-Service & Set-Service -ComputerName Parameter is Gone

Windows PowerShellThe –ComputerName parameter in Get-Service and Set-Service permits targeting a remote machine without relying on Windows PowerShell remoting in 5.1.x. This parameter no longer exists in the new PowerShell 7.0.0.

Next to this change, the following parameters of the Get-Service cmdlet now accept wildcard characters by default:

– DisplayName
– Exclude
– Include
– Name
– RequiredServices

PowerShell 7 RTM / GA!

Windows PowerShellDespite unexpected hiccups which resulted in the more than one month+ delay, it was announced earlier today by the PowerShell Team blog on Wed 4 Mar 2020 that the latest open-source, cross-platform* PowerShell 7.0.0 (based on .NET Core 3.1) has finally gone RTM and is now generally available for download on GitHub.

Read all about it from the official source or from independent sources (here and in German here), including important end-of-life (EOL) information concerning the previous version of .NET Core 3.0 over here.

See also What’s New in PowerShell 7.0.

* Windows, Linux, macOS (x64 and ARM platforms)