PowerCLI 6.0 R1 Is Now Generally Available


I am pleased to announce that vSphere PowerCLI 6.0 Release 1 is now Generally Available to the public. With this comes many great new features and functionality.

One of the great things that I love about PowerCLI is that although we are product-feature driven, we are also very much customer driven. Each new release tends to have several features or enhancements that have been asked for by YOU, our customers. These new features come to us by way of interaction at events like VMworld, Partner Exchange, VMUG Conferences, Twitter, Email, and customer visits. What better way to show our customers that we listen then by adding in features they ask for? This release does not disappoint! Thank you to all who provide feedback and help us continue to improve this great tool.

In this release PowerCLI meets VSANvCloud AirModules, and More! If that isn’t enough to spark interest in reading further, I don’t know what will! Without further ado:

What’s New in This Release

  • vCloud Air Integration – Easily connect to, and work with vCloud Air from PowerCLI
    • You can now connect and disconnect from vCloud Air with simple Connect-PIServer/Disconnect-PIServer cmdlets
    • Choose your vCloud Air datacenter with the new Get-PIDatacenter cmdlet
  • Storage – Continuing to enhance PowerCLI capabilities with our latest product offerings
    • PowerCLI cmdlets added for IO Filters
    • Integrated the VSAN cmdlets from the VSAN Cmdlet fling into the PowerCLI release
    • Enhancements to enable the management of VSAN in their respective areas:
      • New-Cluster and Set-Cluster Cmdlets now have a –VSANEnabled Parameter and a –VSANDiskClaimMode parameter
      • New-VMHostNetworkAdapter and Set-VMHostNetworkAdapter cmdlets now have a –VsanTrafficEnabled parameter
  • Modules – Say what?? No Way! We’re getting modules!
    • You’ve been asking, we’ve been listening. Modules are here!
    • There are a few remaining PSSnapins that will be converted to modules. We wanted to get you in on the goodness as quickly as possible. Next blog post will discuss this release’s ‘hybrid’ deployment and have more details on what we’ve done with these modules.
  • DRM Information – Export DRM log information without needing to SSH
    • New ability to export DRM information for each cluster with the new Get-DrmInfo cmdlet
  • Other Enhancements
    • New-VM and Set-VM have been updated for vSphere 6 and Hardware version 11
    • Other bug fixes and performance enhancements that make your life that much better
    • Connect to and manage the new vCloud Suite SDK with the Connect-CISServer and Get-CISService cmdlets.
    • Single download file for all PowerCLI cmdlets: PowerCLI for Tenants has been removed and is available within the PowerCLI installer located in the ‘vCloud Air/vCD PowerCLI’ feature option.
  • Updated Requirements
    • PowerCLI now requires .Net Framework 4.5 or newer, allowing for enhanced features and capabilities in future releases of PowerCLI
  • Deprecated cmdlets – Still exist, but work towards removing from scripts
    • Guest customization cmdlets, -VMGuestNetworkInterface and -VMGuestRoute, have been marked as deprecated and will be removed in a future version of PowerCLI:
      • Get/Set-VMGuestNetworkInterface
      • Get/New/Remove-VMGuestRoute

A very big thank you to the hard work of all who were involved in making this release come to fruition. A special thanks to a great Product Line Manager, Alan Renouf, as well as our PowerCLI team in Sofia. Fantastic work!

The above is a high level list of the updates made to vSphere PowerCLI, in-depth blog articles on each of these features will follow. For more information on changes made in vSphere PowerCLI 6.0 Release 1, including improvements, security enhancements, and deprecated features, see the vSphere PowerCLI Change Log. For more information on specific product features, see the VMware vSphere PowerCLI 6.0 Release 1 User’s Guide (for PDF version click HERE). For more information on specific cmdlets, see the VMware vSphere PowerCLI 6.0 Release 1 Cmdlet Reference.

Please take a moment to look through the Release Notes HERE for important information about some of the changes in this version.

Download PowerCLI 6.0 now! 


15 comments have been added so far

  1. After installing 6.0, both the 32 and 64 bit PowerCLI consoles throw an error:

    Get-PowerCLIVersion : The term ‘Get-PowerCLIVersion’ is not recognized as the
    name of a cmdlet, function, script file, or operable program. Check the
    spelling of the name, or if a path was included, verify that the path is
    correct and try again.
    At C:\Program Files (x86)\VMware\Infrastructure\vSphere
    PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:81 char:12
    + $version = Get-PowerCLIVersion
    + ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-PowerCLIVersion:String) [],
    + FullyQualifiedErrorId : CommandNotFoundException

    1. I just uninstalled PowerCLI, downloaded PowerCLI 6.0 from the link in this post, Installed it, and its up and running fine. Try uninstalling and reinstalling.

      1. That didn’t fix it, but I did find the problem.
        The issue is that the installer adds the PowerCLI modules path to the PSModulePath of the installing user rather than the system wide PSModulePath.
        Since my logged in user account wasn’t the user that installed PowerCLI (I don’t run as a local admin) the PowerCLI modules folder wasn’t in PSModulePath.

        Once I added that directory to the system PSModulePath variable it all worked properly.

        1. Had the same problem. Here’s a bit of powershell code to quickly ‘patch’ the issue (substitute Program Files (x86)) with just “Program Files” if running on 32-bit OS.

          $PowerCLIModulePath = “C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Modules”
          if (($env:PSModulePath).tostring() -notmatch “PowerCLI”) {
          Write-Host “[Adding PowerCLI Module directory to Machine PSModulePath]” -ForegroundColor Green
          $env:PSModulePath += “;$PowerCLIModulePath”
          } else {
          Write-Host “[PowerCLI Module directory already in PSModulePath. No action taken]” -ForegroundColor Cyan

  2. I was wondering if there are any improvements to Invoke-Vmscript? Like passing variables or just general usability?

  3. Any idea which snapin or module holds the Get-VASAProvider cmdlet? I don’t understand why the cmdlet reference for each cmdlet doesn’t show which module contains it. Every time I find a cmdlet I want to use, I have to hunt and peck through blogs to figure out which module to load. Any help would be greatly appreciated.

    1. Hi John,
      Your request is quite simple actually. Try this:

      Get-Command Get-VasaProvider | Select ModuleName

      Does that work for you?


Leave a Reply

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