Earlier this year VMware released PowerCLI 10! Wait a minute, 10??? What happened to 7, 8, and 9?? I’ll get to that in a minute…
Along side PowerCLI 10, Microsoft PowerShell 6.0 has also been released. This is big, really, really big. If you haven’t been following PowerShell with their 6.0 release they are adding support for other Operating Systems. Yes that’s right, you can now run PowerShell ,and PowerCLI, on MacOS as well as various flavors of Linux.
Also note worthy in PowerCLI 10 is the way PowerCLI handles certificates. If the vCenter or ESXi server you’re connecting to is using an invalid certificate, such as a self-signed cert, when you connect to it using Connect-VIServer you get a certificate error. Now, you can set the default action for handling these invalid certificates using Set-PowerCLIConfiguration.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore
Now, what about that version number? In the VMware PowerCLI Blog article, by Kyle Ruddy, Kyle states that the version number has seen some jumps over the years. Initially PowerCLI was used to manage vSphere. But, VMware added functionality that allowed to manage more of VMware’s portfolio. The version number has been lock step with vCenter and ESXi for a while now. However, the latest version adds so many additional features that it was time to break it away as something that can stand on it’s own. The PowerCLI team felt it appropriate to jump to 10 as PowerCLI is in it’s 10th year! Crazy!
For more information on this release of PowerCLI checkout the full announcement from the VMware PowerCLI blog, here.
Keep a look out for a future article on setting up PowerShell 6.0 and PowerCLI 10 on MacOS!
No Blinky Blinky 