Home > Blogs > VMware PowerCLI Blog

New Release: VMware PowerCLI 6.5.4

It feels just like yesterday that we released PowerCLI 6.5.3. Shockingly, it was less than a month ago when we released the brand-new module to help manage and automate your NSX-T environments. Yet, we’re back with another brand-new module to manage VMware Cloud on AWS environments as well as a bunch of new and updated storage cmdlets too!

PowerCLI 6.5.4 features the following:

  • New module for VMware Cloud on AWS functionality
  • 14 new cmdlets added to the Storage module
  • Several cmdlets have also been improved in the Storage module

Let’s take a closer look at each of these.

New VMware Cloud on AWS Module

VMware Cloud on AWS (VMC) initial availability was announced earlier this year at VMworld US. PowerCLI already works with the vSphere infrastructure out of the box. How about managing the VMC service itself? Doing tasks such as creating SDDCs, adding or removing ESXi hosts, and so forth. PowerCLI 6.5.4 makes all of that possible!

This module is being released as a low-level, API access only, module and will feature the following cmdlets:

  • Connect-VMC
  • Disconnect-VMC
  • Get-VmcService

Note: The VMC API is currently available as a “Technical Preview” and therefore the namespace and functionality provided by the module may change in the future.

When we get started with the VMC module, we’ll notice immediately that it has a little different authentication process than the other connection cmdlets. This module requires you first acquire the OAuth Refresh Token from the VMware Cloud Console:
VMware Cloud Console OAuth Refresh Token

Copy the refresh token, open a new PowerShell session (after having updated to PowerCLI 6.5.4), and connect to the VMC service with the following command:

Now that we are connected, we can then display some information about the current Organization with the following commands:

Example Output:
Example: Connecting and Listing Current Org

One other thing you probably want to do is retrieve information about the Org’s SDDC. That information can be found with the following commands:

Example Output:
Example: Retrieving an Org's SDDC Information

New Storage Module Cmdlets

The Storage module has added a ton of functionality around vSAN encryption. PowerCLI can now manage Key Management Servers (KMS), configure KMS clusters, manage certificates, and even start the vSAN encryption process on a cluster! There are also a couple of other cmdlets available to repair vSAN objects, obtain evacuation plan information, and manage vSAN rebalance cluster actions.

Here’s a list of all the new cmdlets available:

  • Add-KeyManagementServer
  • Get-KeyManagementServer
  • Set-KeyManagementServer
  • Remove-KeyManagementServer
  • Get-KmsCluster
  • Set-KmsCluster
  • New-KmipClientCertificate
  • Get-KmipClientCertificate
  • Start-VsanEncryptionConfiguration
  • Get-VsanEvacuationPlan
  • Repair-VsanObject
  • Start-VsanClusterRebalance
  • Stop-VsanClusterRebalance
  • Get-VsanRuntimeInfo

Taking a look at some of these new cmdlets in action:

Improved Storage Module Cmdlets

Last, but not least, there are some cmdlets that have received updates for additional functionality. Here’s a list of the improved cmdlets:

Cmdlet Added Functionality
Get-VsanTest Displays vnic and pnic vSAN Stats
Start-VsanClusterDiskUpdate Parameter: EraseDisksBeforeUse
Reformats the vSAN disk with encryption settings
Get-VsanClusterConfiguration Displays the Silent Health Check Statuses and Resync Throttling Configuration of a vSAN Cluster
Set-VsanClusterConfiguration Parameter: AddSilentHealthCheck & RemoveSilentHealthCheck
Allows for Management of vSAN Health Check Silencing Actions
Parameter: ResyncThrottlingMbps
Configures Throttling of vSAN Resync Traffic
Parameter: WitnessHost
Replaces the Witness Host in a Stretched Cluster
Test-VsanClusterHealth Additionally Displays Encryption Health Results


PowerCLI 6.5.4 brings some fantastic updates to your PowerShell console and only a month after the last update! This release allows you to manage your VMware Cloud on AWS Org, SDDC, and more directly from PowerCLI. There are also a lot of storage improvements to make automating vSAN clusters a breeze and more secure with 14 new cmdlets and several other having been improved upon.

Updating to PowerCLI 6.5.4 is just as easy as:

For more information on changes made in VMware PowerCLI 6.5.4, including improvements, security enhancements, and deprecated features, see the VMware PowerCLI Change Log. For more information on specific product features, see the VMware PowerCLI 6.5.4 User’s Guide. For more information on specific cmdlets, see the VMware PowerCLI 6.5.4 Cmdlet Reference.

This entry was posted in General and tagged on by .
Kyle Ruddy

About Kyle Ruddy

Kyle Ruddy is a Senior Technical Marketing Architect working for VMware R&D in the Cloud Platform Business Unit. Kyle currently focuses on vSphere and VMware Cloud on AWS automation and the associated automation frameworks including all things API, CLI, and SDK. Kyle is also a Microsoft MVP and long-term vExpert whom can be found blogging on VMware blogs, http://blogs.vmware.com/vSphere and http://blogs.vmware.com/PowerCLI, and his personal blog, https://www.kmruddy.com. His Twitter: @kmruddy

9 thoughts on “New Release: VMware PowerCLI 6.5.4

  1. Pingback: Using PowerCLI to manage VMware Cloud on AWS - Virtu-Al.Net

  2. Vandrey Trindade

    Hi, I’m getting this error to update:

    PS C:\> Get-PowerCLIVersion
    AVISO: The cmdlet “Get-PowerCLIVersion” is deprecated. Please use the ‘Get-Module’ cmdlet instead.

    PowerCLI Version
    VMware PowerCLI 6.5.1 build 5377412
    Component Versions
    VMware Cis Core PowerCLI Component 6.5 build 6983166
    VMware VimAutomation Core PowerCLI Component 6.5 build 6234650

    PS C:\> update-module VMware.PowerCLI -Force
    AVISO: The version ‘’ of module ‘VMware.VimAutomation.Sdk’ is currently in use. Retry the operation after
    closing the applications.
    AVISO: The version ‘’ of module ‘VMware.VimAutomation.Common’ is currently in use. Retry the operation
    after closing the applications.
    AVISO: The version ‘’ of module ‘VMware.VimAutomation.Cis.Core’ is currently in use. Retry the operation
    after closing the applications.
    AVISO: The version ‘’ of module ‘VMware.VimAutomation.Core’ is currently in use. Retry the operation after
    closing the applications.

    1. Kyle RuddyKyle Ruddy Post author

      Looks like there are a couple PowerCLI modules active in a PowerShell session. It also looks like you’re up to date, PowerCLI wise. You can verify what version of PowerCLI you’re using with:
      Get-Module VMware.PowerCLI -ListAvailable | Sort-Object Version -Descending | Select-Object -First 1

      More information on that deprecation notice can be found on this blog post: https://blogs.vmware.com/PowerCLI/2017/08/finding-powercli-version.html

      If you still want to do the update, try the following: (Note: This will unregister any active PowerCLI modules from your current PowerShell session and not remove the modules from the local system)
      Get-Module VMware.* | Remove-Module -Force
      Update-Module VMware.PowerCLI

      1. Vandrey Trindade

        Kyle Ruddy,

        Thanks for your fast reply!
        I’ve tried to remove the modules that it said were active and didn’t work.
        As my module is updated, I’ll leave it that way.

        Major Minor Build Revision
        —– —– —– ——–
        6 5 4 7155375


  3. Ola

    Why is there no prepackage PowerCLI installation package?
    Admin machines should not have Internet access, for obvious reasons.
    So how do I update without Internet access?

  4. free robux generator

    hey friends if you love to play roblox then try roblox its amazing

  5. István

    How to istall it to a computer which is not connected to the Internet?

  6. Pingback: Using PowerCLI & vSAN Management API to list VMs w/Thick VM swap

  7. look at this site

    Hi! I like this website because i have a lot of options to choose and good info.thanks alot god blessed.


Leave a Reply

Your email address will not be published. Required fields are marked *