Jume - My Virtualization Blog

My personal and professional virtualization blog. Everything about VMware, PowerCLI, Powershell, Agile, Scrum, VSAN and Cloud related.

PowerShell 7.0 GA

​Some great news came overnight. Microsoft has announced the release of PowerShell 7.0.0. After a couple of release candidates we now have 7.0.0! Awesome! But does PowerCLI work? Let's check that out!!! Something to note (from the original article):

Which Microsoft products already support PowerShell 7? 

Any module that is already supported by PowerShell Core 6.x is also supported in PowerShell 7, including:

On Windows, we've also added a -UseWindowsPowerShell switch to Import-Module to ease the transition to PowerShell 7 for those using still incompatible modules. This switch creates a proxy module in PowerShell 7 that uses a local Windows PowerShell process to implicitly run any cmdlets contained in that module. For more information on this functionality, check out the Import-Module documentation.

Installation 

Installation is a breeze (on my Windows machine) and downloading almost takes longer than the installation... Grab the binaries from here: https://github.com/PowerShell/PowerShell/releases

I love the 'Add 'Open here' context menus to Explorer' option.

After a few minutes...

Let's check if the modules are available (I've got PowerCLI 11.5 installed already).

​I do get an error message: "Exception: VMware.VimAutomation.License module is not currently supported on the Core edition of PowerShell." - but this is the 'only' module not compatible. As long as you don't use the cmdlets in there, you should be fine. You're going to miss:

Get-LicensingCommand
Get-LicenseDataManager

So be aware of that!

I've tried to load the module with the  -UseWindowsPowerShell switch, but that fails:

Connection works fine (everything is double, hahaha). But VMware.VimAutomation.License is still not working.

Message: "Import-Module: Failed to generate proxies for remote module 'VMware.VimAutomation.License'. Running the Get-FormatData command in a remote session reported the following error: Unable to cast object of type 'Microsoft.PowerShell.Commands.Internal.Format.ControlReference' to type 'Microsoft.PowerShell.Commands.Internal.Format.ComplexControlBody'.."

So it's really a NO-GO for these cmdlets. Oh well - VMware's code team will soon figure that one out and present us an update (11.5 is already 4 months old now).

​I guess this concludes this post. I'm very excited and will be testing PowerShell 7.0.0 in combination with PowerCLI 11.5.0. If I find any strange behavior, I'll report it here!

Access VM console in a secured environment - part ...
6502 computer on a breadboard

Related Posts

 

Comments

No comments made yet. Be the first to submit a comment
Guest
Tuesday, 29 September 2020