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”.]
Read More
Show your support, share this article:
Recent Comments