What’s New in VMware PowerCLI 10.0?
At 10th PowerCLI’s birthday, VMware announced new release of PowerCLI with new name and new features.
vSphere PowerCLI name has been changed to VMware PowerCLI because after 10 years of evolution, PowerCLI is automation tools for many of VMware’s products.
Also PowerCLI version number has been jumped to 10 because of celebrating 10th birthday.
Let’s review some of the new features and improvements.
Installing PowerCLI via PowerShell
PowerCLI is an executable file that you can download it form VMware and install it on your client or server.
It was the before! Now, you can install PowerCLI from PowerShell easily.
Run the below command to install PowerCLI’s modules on your clients:
Install-Module -Name VMware.PowerCLI -Scope CurrentUser
If you want to replace installed version with last release, run the below instead of the above command:
Install-Module -Name VMware.PowerCLI -Force -Scope CurrentUser
Maybe, you have to install some extra components, if the client has no module installed. NuGet is required to download and install other modules.
After the installation is completed, you can verify the installation by the below command:
Get-Module VMware.PowerCLI -ListAvailable
The output should be like this:
Multi Platform Support
PowerCLI 10.0.0 adds support for Mac OS and Linux! The only pre-requisite is to have PowerShell Core 6.0 installed. The installation process is same on all supported OSes.
Default Certificate Handling
This version changes the way certificates are handled when connecting to a vCenter server or ESXi host with the Connect-VIServer cmdlet. If your connection endpoint is using an invalid certificate (self-signed or otherwise), PowerCLI would previously return back a warning. The handling has been updated to be more secure and now return back an error.
If you are using an invalid certificate, you can correct the error with the ‘Set-PowerCLIConfiguration’ cmdlet. The parameter needing to be configured is ‘InvalidCertificateAction’ and the available settings are Fail, Warn, Ignore, Prompt, and Unset.
The following code will configure the ‘InvalidCertificateAction’ parameter to be Ignore:
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore
Deprecated Cmdlets and Property
The below cmdlets removed from VMware.VimAutomation.Core module:
These cmdlets are replaced with the use of the Invoke-VMScript cmdlet.
Please read this post to find good sample of using Invoke-VMScript cmdlet:
[How To]: Change Linux IP Address via PowerCLI
The below problem has been resolved in this release:
- Piping the Get-Datacenter cmdlet output to Get-Cluster now works when more than one datacenter is present
- Configuring manual MAC addresses with the New/Set-NetworkAdapter cmdlet now accepts all addresses, not just MAC addresses in the 00:50:56 range
- VMs with snapshots can be Storage vMotioned to VMFS6 datastores without hitting a ‘redoLogFormat’ error
- Lots of updates to the Get-TagAssignment cmdlet, including when connected to two vCenter Servers and also displays the Tag Category as expected
More On Teimouri.Net
1,660 total views, 2 views today
Davoud Teimouri is as a professional blogger, vExpert 2015/2016/2017/2018, VCA, MCITP. This blog is started with simple posts and now, it has large following readers.