Home > Blogs > VMware PowerCLI Blog


New Release: PowerCLI 11.0.0

PowerCLI has been moving at quite the rapid pace over the last 2 years. In 2018, we’ve been releasing roughly every other month to make sure we get the latest features, performance improvements, and updates available as quickly as possible. Well, it’s been two months and we’re not going to break this trend. Today, we are releasing PowerCLI 11.0.0!

PowerCLI 11.0.0 comes with the following updates:

  • Added a new Security module
  • Added new cmdlets for Host Profiles
  • Added a new cmdlet to interact with NSX-T in VMware Cloud on AWS
  • Support for vSphere 6.7 Update 1
  • Support for NSX-T 2.3
  • Support for Horizon View 7.6
  • Support for vCloud Director 9.5
  • Multiplatform support for the Cloud module
  • Updated the Get-ErrorReport cmdlet
  • Removed the PCloud module
  • Removed the HA module

Let’s take a more in-depth look at some of these updates.

New Security Module

There has been a tremendous amount of improvements around security for vSphere lately. The new VMware.VimAutomation.Security module ensures you have the ability to automate these new features.

The Security module includes the following cmdlets:

  • Get-SecurityInfo
  • Get-VTpm
  • Get-VTpmCertificate
  • Get-VTpmCSR
  • New-VTpm
  • Remove-VTpm
  • Set-VTpm
  • Unlock-VM

Also, thanks to the Security module (with a little help from the Storage module), several other cmdlets are receiving enhancements as well:
New-VM has added the following parameters:

  • KmsCluster
  • StoragePolicy
  • SkipHardDisks
  • StoragePolicy
  • ReplicationGroup
  • StoragePolicyTarget

Set-VM has added the following parameters:

  • DisableEncryption
  • KmsCluster
  • SkipHardDisks
  • StoragePolicy

Set-VMHost has added the following parameter:

  • KmsCluster

Set-HardDisk has added the following parameters:

  • DisableEncryption
  • KmsCluster
  • StoragePolicy

New-HardDisk has added the following parameters:

  • KmsCluster
  • StoragePolicy

Host Profile Updates

There have been a lot of requests coming in for updates to the set of cmdlets available to manage Host Profiles. The VMware.VimAutomation.Core module has some updates you’ll want to check out!

The following cmdlets have been added to help manage Host Profiles:

  • Get-VMHostProfileUserConfiguration
  • Set-VMHostProfileUserConfiguration
  • Get-VMHostProfileStorageDeviceConfiguration
  • Set-VMHostProfileStorageDeviceConfiguration
  • Get-VMHostProfileImageCacheConfiguration
  • Set-VMHostProfileImageCacheConfiguration
  • Get-VMHostProfileVmPortGroupConfiguration
  • Set-VMHostProfileVmPortGroupConfiguration

Storage Module Updates

The VMware.VimAutomation.Storage module has grown by leaps and bounds in the last couple releases. This release adds two new cmdlets and quite a few updates to existing cmdlets. Some of the improvements include an update to support predefined time ranges when using Get-VsanStat. Get-VsanDisk has some additional properties which are returned, such as: capacity, used percentage, and reserved percentage. Also receiving an update is the Get/Import/Export-SpbmStoragePolicy cmdlets, as they now support storage policy components.

The following cmdlets have been added to help automate vSAN:

  • Get-VsanObject
  • Get-VsanComponent

More details on these updates for vSAN can be found on the Virtual Blocks blog, by Jase McCarty: More vSAN Cmdlets in PowerCLI 11!

vCloud Director Updates

This update is another direct result from feedback. There has been an impressive amount of people requesting updates to the VMware.VimAutomation.Cloud module. With this release, we are updating the module to support vCloud Director 9.5. There are also a couple of new cmdlets being added.

The following cmdlets have been added to help automate vCloud Director networking:

  • Get-EdgeGateway
  • New-OrgVdcNetwork
  • Remove-OrgVdcNetwork
  • Set-OrgVdcNetwork

Other Improvements and Updates

There are also a handful of updates which are all due to community feedback! There has been an update to the output when using New-VM combined with the ‘Confirm’ parameter so that the output matches that of the created VM. An update to Get-View has been added to help resolve a Vim error being received when the ‘Property’ parameter was specified. Another fix was when Get-VM would result in an error of ‘Value cannot be null’. The last big issue, there has been an update to the way Get-NetworkAdapter outputs a NSX-T logical network backed portgroup.

Summary

PowerCLI 11.0.0 has been released and there are a ton of fantastic new additions. Over 20 new cmdlets have been added to help automate vCloud Director networking, virtual TPM settings, Host Profile configurations, and VMware Cloud on AWS networking. More than 10 cmdlets have been enhanced to add newly released features. Plus, a handful of updates to improve the overall quality and reliability.

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

Remember, updating your PowerCLI modules is now as easy as ‘Update-Module VMware.PowerCLI’.

Update-Module VMware.PowerCLI

Let us know in the comments what you’re most excited about!

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

22 thoughts on “New Release: PowerCLI 11.0.0

  1. Pingback: New Release: PowerCLI 11.0.0 – VMPRO.AT – all about virtualization

  2. Pingback: VMware PowerCLI 11.0.0 Relaesed | Virtual Allan

  3. Anton Paloka

    Great news.
    Trying to update, I get the following:

    VERBOSE: Found the catalog file ‘VMware.VimAutomation.Sdk.cat’ in the module ‘VMware.VimAutomation.Sdk’ contents.
    VERBOSE: Valid authenticode signature found in the catalog file ‘VMware.VimAutomation.Sdk.cat’ for the module ‘VMware.VimAutomation.Sdk’.
    VERBOSE: Validating the ‘VMware.VimAutomation.Sdk’ module files for catalog signing using the catalog file ‘VMware.VimAutomation.Sdk.cat’.
    PackageManagement\Install-Package : Unable to read file C:\Users\paloka\AppData\Local\Temp\1352191934\VMware.VimAutomation.Sdk\net45\VMware.VimAutomation.Sdk.ps1 to calculate its hash.
    At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:2052 char:20
    + … $sid = PackageManagement\Install-Package @PSBoundParameters
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (Microsoft.Power….InstallPackage:InstallPackage) [Install-Package], Exception
    + FullyQualifiedErrorId : UnableToReadFileToHash,Microsoft.PowerShell.Commands.TestFileCatalogCommand,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

    Reply
  4. Kyle RuddyKyle Ruddy Post author

    Are you able to check your antivirus software to see if anything is being blocked?

    Another option, you’re more than welcome to open a VMware support request as well.

    Reply
  5. Mike Morgan

    Sadly, still no commands for vSphere Replication. 🙁

    Reply
  6. Pingback: Новые команды для vSAN в PowerCLI 11 | IT-пилот

  7. Pingback: New Release: PowerCLI 11.0.0 - Everyday Virtualization

  8. Phil

    When importing this module in PSCore 6.1.0 (win7-x64) I receive the following error:
    Import-Module : VMware.VimAutomation.Srm module is not currently supported on the Core edition of PowerShell.
    At line:1 char:1
    + Import-Module vmware.vimautomation.srm
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OperationStopped: (VMware.VimAutom… of PowerShell.:String) [Import-Module], RuntimeException
    + FullyQualifiedErrorId : VMware.VimAutomation.Srm module is not currently supported on the Core edition of PowerShell.,Microsoft.PowerShell.Commands.ImportModuleCommand

    Even if I try to ignore the error, it prevents VMware.PowerCLI from loading any more sub modules.

    Reply
    1. Luke

      It seems like PowerShell 6 is currently not natively supported.
      The Find-Module cmdlet doesn’t even list the vmware.powercli module when run from a PowerShell 6 console.

      Reply
        1. Adis

          But not on Windows Platform. From the page you linked:
          OS Type .NET Version PowerShell Version
          Windows .NET Framework 4.5, 4.5.x, 4.6, 4.6.x or 4.7.x Windows PowerShell 3.0, 4.0, 5.0, or 5.1

          Reply
  9. Pingback: All vSphere 6.7 Update 1 release notes & download links

  10. Vijayabhaskaran

    Any inclusions for vSCSI PowerCLI commands, to know their IOPs/TP/Latency – per vSAN VM wise.

    Reply
  11. AaronK

    There seems to be a ‘bug’ somewhere when i try to install an ‘older’ version of PowerCLI, it installs, but some of the requisite modules actually install the 11.0 version..

    e.g.
    Install-Module VMware.PowerCLI -RequiredVersion 6.5.2.6268016

    When you look at the versions of say vmware.vimautomation.core, it’s actually the 11.0.0.10336080 version..

    So it seems ‘impossible’ to actually do an older version..

    Reply
  12. Axel

    Hello,
    Is there any known issue about using Connect-VIServer with a proxy ?
    PS > Connect-VIServer -Server -Protocol https
    It first connects to the proxy, asks for credentials but then it try to directly connect to the vSphere IP:443 and fails with a timeout error

    Axel

    Reply
  13. Pingback: vToolBelt - October 2018 - Cybersylum

  14. Phil

    Thanks for the release.
    When installing on a new machine I am still getting the log4net error. Could you please fix this for the next release?

    Import-Module : Could not load file or assembly ‘log4net, Version=1.2.10.0, Culture=neutral,
    PublicKeyToken=692fbea5521e1304’ or one of its dependencies. The system cannot find the file specified.
    At line:1 char:1
    + Import-Module vmware.powercli -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.PowerShell.Commands.ImportModuleCommand

    Name Value
    —- —–
    PSVersion 5.1.16299.666
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
    BuildVersion 10.0.16299.666
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

    Reply
    1. Kyle RuddyKyle Ruddy Post author

      Normally that message is seen when the antivirus is quarantining the log4net dll. I would start by checking your antivirus. If that’s not the culprit, please feel free to open a support request and we’ll help you troubleshoot the installation process.

      Reply
  15. Alicia Alvarado

    I found your post by searching in google, and I have enjoyed reading it ….

    Reply
  16. PXCSW

    The Move-VM CMDlet seems to be broken with 11.0 when there are more than 1 Datacenter on the Server.

    Getting:

    Move-VM : 12/2/2018 12:58:02 PM Move-VM The operation for the entity “Computername” failed with the following
    message: “The input arguments had entities that did not belong to the same datacenter.”

    When running Move-VM Computername -inventorylocation Maintenance

    Version 10.2.0 and below still work.
    Running Version 6.7.0 Update 1 on Server

    Reply
  17. Yondaime_Minato

    Hi Kyle,
    is it normal or not a concern when i did the upgrade and did the get-module command it showed, not just 11.0 module but also previous module.
    It listed 3 modules of PowerCLI along with the latest 11.0 version just upgraded

    Reply

Leave a Reply

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

*