PowerCLI 6.5.4 is dead, welcome PowerCLI 10.0.0 🙂 VMware released few days ago the latest version, marked with a huge jump in numbering, moving straight from 6 to 10. This version marks also the promote of the former Fling PowerCLI Core into the main PowerCLI product. Now we have same product running multiplatform: Windows, Linux, and MacOS. This makes things simpler. How do you install PowerCLI on Windows? That’s “Install-Module -Name VMware.PowerCLI”. How about Linux? “That’s “Install-Module -Name VMware.PowerCLI”. MacOS? You got this, it’s the same.
PowerCLI 10.0.0 consists of the following modules:
- VMware.DeployAutomation
- VMware.ImageBuilder
- VMware.PowerCLI
- VMware.VimAutomation.Cis.Core
- VMware.VimAutomation.Cloud
- VMware.VimAutomation.Common
- VMware.VimAutomation.Core
- VMware.VimAutomation.HA
- VMware.VimAutomation.HorizonView
- VMware.VimAutomation.License
- VMware.VimAutomation.Nsxt
- VMware.VimAutomation.PCloud
- VMware.VimAutomation.Sdk
- VMware.VimAutomation.Srm
- VMware.VimAutomation.Storage
- VMware.VimAutomation.StorageUtility
- VMware.VimAutomation.Vds
- VMware.VimAutomation.Vmc
- VMware.VimAutomation.vROps
- VMware.VumAutomation
Not all these modules are supported on PowerShell Core, generating an error when trying to launch on Linux, but I will detail this in a future article. [Update 05 March 2018: The article is here: PowerCLI 10.0.0 Linux Error in VMware.VimAutomation.Srm Module. The mentioned error: “Import-Module : VMware.VimAutomation.Srm module is not currently supported on the Core edition of PowerShell”.]
PowerCLI 10.0.0 Changes
Following cmdlets were removed from VMware.VimAutomation.Core module: Get-VMGuestNetworkInterface, Set-VMGuestNetworkInterface, Get-VMGuestRoute, New-VMGuestRoute, and Remove-VMGuestRoute.
Default value of the Scope parameter of the Set-PowerCLIConfiguration cmdlet is now User instead of AllUsers.
Default value of the InvalidCertificateAction parameter of the Set-PowerCLIConfiguration cmdlet is now Fail instead of Prompt.
There are also plenty of bugfixes in the current version, but these caught my attention:
- (Get-Datacenter | Get-Cluster) fails when there is more than one datacenter.
- Get-OMResource stops running when you query for a virtual machine with a # in the name.
- Get-TagAssignment does not return Tag Catagory in the Tag output when running against vCenter Server 6.5.
- When you want to migrate a virtual machine with snapshots from VMFS 5 datastore to VMFS 6 datastore, the operation fails and you receive an error message of type “The specified delta disk format ‘redoLogFormat’ is not supported”.
- New-NetworkAdapter and Set-NetworkAdapter only accept manual MAC addresses in the valid 00:50:56 range.
- When you have multiple connections to the same vCenter Server system in different PowerShell runspaces, a memory leak issue occurs.
Update to PowerCLI 10.0.0
I wrote earlier about the install procedure on Windows, Linux and Mac, but how easy it is to update a previous installation? Let’s just say, this is as easy as the install procedure.
I started with my previous installation of PowerCLI 6.5.4:
And then I ran the famous update command:
Update-Module -Name VMware.PowerCLI
I accepted to install the modules from the untrusted repository, then I waited for around 1 minute for installation to complete.
I then imported VMware.PowerCLI module and confirmed the version:
Import-Module VMware.PowerCLI
Get-Module -Name VMware.PowerCLI | Select-Object -Property Name,Version
Happy scripting!
