What's New in PowerShell 7.2?

Hey everyone, it's time to get stuck into PowerShell 7.2. PowerShell 7.2 is an important release in the lifecycle of PowerShell as it replaces 7.0 as the next Long Term Support (LTS) release. That means it will have support from Microsoft next 3 years.

How can I Install PowerShell 7.2?

You can grab the 7.2 release here:  https://aka.ms/PowerShell-Release?tag=v7.2.0

On Windows desktop operating systems, you can install PowerShell from either the Microsoft Store, or from an MSI. On Windows Servers, you're limited to The MSI. The installation on Linux has also been improved for this release, with one universal package that targets most major flavours of Linux.

Enabling update via Microsoft Update

You can enable Microsoft Update when installing using the MSI:

 Micrsoft Update PowerShell 7.2

There are command line options too, but the default is to enable Microsoft Update.

Changing the Look and Feel of PowerShell 

Microsoft has introduced a new built-in variable, $PSStyle. You can use that to change the look and feel of PowerShell.

One of the favorite items to change is the table headings, you can do this by setting the $PSStyle.Formatting.TableHeader value, shown below:

Writing PowerShell Faster with Predictive Intellisense

 PSReadLine 2.1 ships with PowerShell 7.2, but you need to enable it first. You can enable it using the below command:

Set-PSReadLineOption -PredictionSource History

You also might want to change the colour of the predictions, by default it's a bit hard to see the predictions, see below, it's almost invisible on my monitor:

Here is an example of the prediction with a more readable colour:


 If you're using Azure, you can also install a plug-in module that allows you to get Azure specific predictions, install it:

Install-module -name Az.Tools.Predictor -MinimumVersion 0.5.0

 Then you can enable it:

Enable-AzPredictor -AllSession


Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
Read more

gPLink and gPOptions

gPLink is a property for sites, domains and organisational units that contains a prioritised list of GPOs linked to the node. gPOptions is a property that contains all Block Policy Inheritance settings for the node. To manage GPO links on a node, you must have read and write access to the gPLink and gPOptions properties.
Read more

PSLoggedOn Getting Started on Windows Server 2008 R2

Image
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se
Read more