Let’s stroll you thru verify the PowerShell model and replace it on a Home windows Server.
Instantly extra of a developer or Sysadmin factor, PowerShell was by no means made for the common Home windows consumer as they’ve the Widespread Immediate to play with (ouch 🤐).
Principally, PowerShell runs cmdlets along with Command Immediate instructions.
Nevertheless, we aren’t right here to distinguish PowerShell from Command Immediate. As a substitute, we’ll have a look at a Microsoft-recommended solution to see the PowerShell model.
And whereas there are different strategies of doing this over the Web, they will not all the time work in all conditions.
Test the PowerShell model
The primary is to open PowerShell from the Home windows search.
Then sort $PSVersionTableand press enter.
This returns essential info together with the present PowerShell model, version, suitable variations, and so forth.
Now I come to different instructions that ‘don’t’ work precisely. These embody get-host, $host, $host-versionand so forth.
Particularly, they offer the model of the host PowerShell is put in on and never the model of the PowerShell engine we’re in search of.
Nevertheless, use get-host if in case you have PowerShell model 1.0 since $PSVersionTable was launched from model 2.0. So this $PSVersionTable returns no outcomes when used on PowerShell 1.0.
Replace PowerShell on Home windows Server
You may replace PowerShell on the Home windows server by way of command-line scripts or by downloading and putting in particular PowerShell variations.
The best methodology is to get the newest file from the Microsoft web site or GitHub repository and proceed with the set up.
A geeky approach to do that from throughout the PowerShell itself is to run iex "& { $(irm https://aka.ms/install-powershell.ps1)} -usemsi".
A connection is made to the MS GitHub repository. Then reply to the next prompts and the set up shall be accomplished shortly.
Particularly, this is not going to replace the outdated PowerShell within the system. As a substitute, the up to date model shall be put in alongside it.
Sum up
This completes checking the PowerShell model and updating it.
Cmdlets make PowerShell a robust automation device. Nonetheless, it will assist as a developer to think about just a few extra scripting languages.