VMware released a new PowerCLI version, version 10.1.0. I will cover in this article the improvements brought by PowerCLI 10.1.0, the installation process on Windows and the update procedure on both Windows and Linux.
PowerCLI 10.1.0 Changes
- New module: VMware.Vim provides vSphere API bindings, allowing access to the latest features available in the VMware Cloud on AWS.
- New cmdlets: Set-ScriptBundleAssociation and Remove-ScriptBundle added to the VMware.DeployAutomation module. They provide the ability to work with script bundles modification.
- NSX-T module has been updated to support the new API features in VMware NSX-T 2.1.
- VMware PowerCLI has been updated to support the new API features in VMware vSphere 6.7.
- Instead of producing a warning when connecting to resources using invalid or self-signed certificates, PowerCLI now produces an error.
- The Import-VApp cmdlet has been updated to support SHA-256 and SHA-512 hash algorithms.
- The Version parameter of the New-VM and Set-VM cmdlets has been deprecated and replaced by the HardwareVersion parameter that accepts string input.
- The Version property of the VirtualMachine object has been deprecated and replaced by the HardwareVersion property.
- When using Get-TagAssignment, you cannot query tags on datastore clusters.
- When running Get-VDPortgroup, names that contain a “/” character are returned with a “%2f” string from the API.
- When you try to migrate a virtual machine to VMware Cloud on AWS by using Cross vCenter Server vMotion, the operation might fail.
- When you run Set-PowerCLIConfiguration and the value of the InvalidCertificateAction parameter is set to Unset or Warn, valid certificates might appear as invalid.
- VMware.VimAutomation.Vds cmdlet formatting does not work.
For full instructions, check the official documentation: VMware PowerCLI User’s Guide.
Install PowerCLI 10.1.0
Moving to the easy part now, let’s install PowerCLI 10.1.0 in a new Windows box. Make sure you have at least PowerShell 5.0 installed, open a console and run the install command:
Install-Module -Name VMware.PowerCLI
After a short wait, installation completes. You can now import PowerCLI module and check the version:
Get-Module -Name VMware.PowerCLI | Select-Object -Property Name,Version
Update to PowerCLI 10.1.0
Let’s see now how to update a previous installation. In my case I will first update a PowerCLI 10.0.0 environment running on Windows.
Update-Module -Name VMware.PowerCLI
Moving on Linux, I will update now an environment running 10.0.0 on Ubuntu 16.04 / PowerShell Core 6.1.0. I will use same command as on above.
No surprise, after the update to PowerCLI 10.1.0 I am not able to import the module.
Import-Module : VMware.VimAutomation.Srm module is not currently supported on the Core edition of PowerShell.
For the unsupported way of making it run, you can check one of my previous articles: PowerCLI 10.0.0 Linux Error in VMware.VimAutomation.Srm Module.
Happy scripting 🙂