VMware PowerCLI 13.2 Release Notes

VMware PowerCLI 13.2 Release Notes

This document contains the following information:

• About VMware PowerCLI
• What's New in This Release
• Resolved Issues
• Known Issues

About VMware PowerCLI

VMware PowerCLI is a suite of PowerShell modules to manage VMware products and services. VMware PowerCLI includes over 7000 cmdlets to easily manage your infrastructure on a global scale.

Installation, Upgrade, and Removal of VMware PowerCLI

Management of the PowerCLI modules is provided by the PowerShell Gallery and by using the PowerShell default cmdlets for working with modules in the PowerShell Gallery. For detailed information on how to install, upgrade, or remove PowerCLI, refer to the VMware PowerCLI User's Guide.

VMware PowerCLI Components

In VMware PowerCLI 13.2.1, the following modules have been updated:

• VMware.PowerCLI: Provides a root module which other modules are dependent on. This ensures the PowerCLI product can be installed, upgraded, and removed as a complete package if needed.
• VMware.Sdk.Vr: Provides auto-generated cmdlets for managing the vSphere Replication API.
• VMware.Sdk.Srm: Provides auto-generated cmdlets for managing the Site Recovery Manager (SRM) API.

In VMware PowerCLI 13.2.0, the following modules have been updated:

• VMware.PowerCLI: Provides a root module which other modules are dependent on. This ensures the PowerCLI product can be installed, upgraded, and removed as a complete package if needed.
• VMware.VimAutomation.Core: Provides cmdlets for automated administration of the vSphere environment.
• VMware.VimAutomation.Common: Provides functionality that is common to all PowerCLI modules. This module has no cmdlets, but is required for other modules to function correctly.
• VMware.VimAutomation.Sdk: Provides SDK functionality that is needed by all PowerCLI modules. This module has no cmdlets, but is required for other modules to function correctly.
• VMware.VimAutomation.Cis.Core: Provides cmdlets for managing vSphere Automation SDK servers.
• VMware.Vim: Provides vSphere low-level binding libraries. This module has no cmdlets.
• VMware.VimAutomation.HorizonView: Provides cmdlets for automating VMware Horizon features.
• VMware.VimAutomation.Vmc: Provides cmdlets for managing VMware Cloud on AWS features.
• VMware.VimAutomation.Storage: Provides cmdlets for managing vSphere policy-based storage.
• VMware.ImageBuilder: Provides cmdlets for managing depots, image profiles, and VIBs.
• VMware.DeployAutomation: Provides cmdlets that provide an interface to VMware Auto Deploy for provisioning physical hosts with ESXi software.
• VMware.CloudServices: Provides cmdlets for managing VMware Cloud Services.
• VMware.Sdk.Nsx.Policy: Provides auto-generated cmdlets for accessing the NSX Policy API.
• VMware.Sdk.Vr: Provides auto-generated cmdlets for managing the vSphere Replication API.
• VMware.Sdk.Srm: Provides auto-generated cmdlets for managing the Site Recovery Manager (SRM) API.
• VMware.Sdk.vSphere.*: Provides auto-generated cmdlets for accessing the vSphere Automation (REST) API.

Supported Platforms

For a list of VMware PowerCLI 13.2.0 supported operating systems and PowerShell versions, see Compatibility Matrixes for VMware PowerCLI 13.2.0.

For a list of VMware products with which VMware PowerCLI 13.2.0 is compatible, see VMware Product Interoperability Matrixes.

What's New in This Release

New Features

VMware PowerCLI 13.2.1 introduces the following new features, changes, and improvements:

• For the vSphere Replication and Site Recovery Manager SDK cmdlets, the type of the object Id properties and Id parameters has been changed from guid to string.

VMware PowerCLI 13.2.0 introduces the following new features, changes, and improvements:

• The VMware.Sdk.Vcf.CloudBuilder and VMware.Sdk.Vcf.SddcManager modules have been added to provide functionality for managing the VMware Cloud Foundation REST API with VMware PowerCLI.
• The VMware.Sdk.Srm module has been updated to support the API features of VMware Site Recovery Manager 8.8.
• The VMware.Sdk.Vr module has been updated to support the API features of vSphere Replication 8.8.
• The VMware.Sdk.Nsx.Policy module has been updated to support the API features of NSX 4.1.2.
• The VMware.VimAutomation.HorizonView module has been updated to support the API features of VMware Horizon 8 2306.
• The VMware.Vim and VMware.Sdk.vSphere.* modules have been updated to support the API features of VMware vSphere 8.0 Update 2.
• The VMware.VimAutomation.Vmc module has been updated to include the following improvements:
• The New-VmcSddc and New-VmcSddcCluster cmdlets have been extended to support a new host type - I4I.
  
• A new cmdlet has been added to the VMware.VimAutomation.Core module.
  • New cmdlet to export the desired state of a vSphere Lifecycle Manager host.
    Export-LcmVMHostDesiredState
    
• A new cmdlet has been added to the VMware.VimAutomation.Storage module.
  • New cmdlet to retrieve a list of the most impactful vSAN performance contributors.
    Get-VsanPerformanceContributor
    
• The VMware.VimAutomation.Storage module has been updated to include the following improvements:
• The Get-VsanSpaceUsage cmdlet has been modified to include an EsaObjectOverheadGB value in the returned object.
  
• The VMware.VimAutomation.Storage module has been updated to support the API features of VMware vSAN 8.0 Update 2.
• A new cmdlet has been added to the VMware.ImageBuilder module.
  • New cmdlet to create a vLCM-compliant offline bundle based on input depots and a software specification.
    New-OfflineBundle
    

  For more information on changes made in VMware PowerCLI 13.2.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 User's Guide. For more information on specific cmdlets, see the VMware PowerCLI Cmdlet Reference. For the full list of PowerCLI documentation, visit the VMware PowerCLI 13.2.0 Home Page.

Resolved Issues

The following issues have been resolved in VMware PowerCLI 13.2.1:

• vSphere Replication and Site Recovery Manager SDK cmdlets
  On some vCenter Server systems, cmdlets from the VMware.Sdk.Vr and VMware.Sdk.Srm modules fail because the Guid property is provided in upper-case letters.

The following issues have been resolved in VMware PowerCLI 13.2.0:

• Tagging and content library cmdlets
  Certain cmdlets that use tagging or content library functionality (Get-TagAssignments, Get-SpbmStoragePolicy, and so on) stop working and the vCenter has to be rebooted.
• Remove-AlarmAction
  Remove-AlarmAction does not remove all triggers for SNMP actions.
• Set-VMHostNetworkAdapter
  When you run Set-VMHostNetworkAdapter -AutomaticIPv6 $false, a statically configured IPv6 address is also removed.
• Connect-VIServer
  Reconnecting to an ESXi host after reboot with Connect-VIServer in the same PowerShell session fails with an error message of type Object reference not set to an instance of an object.
• Get-vSANStat
  Get-vSANStat fails with an error message stating that a vSAN ESA feature is not available.
• All ImageBuilder Cmdlets
  If you have installed on your machine the public distribution of pyVmomi through pip, all VMware.ImageBuilder cmdlets do not work.
• New-IsoImage, New-PxeImage, and Export-EsxImageProfile
  An image generated through the VMware.ImageBuilder module when using Python version 3.8 or later fails to boot even if no issues were encountered during image creation.
• Remove-EsxSoftwarePackage
  Remove-EsxSoftwarePackage doesn't throw a warning when removing an invalid software package from the image profile.

Known Issues

VMware PowerCLI 13.2.0 and VMware PowerCLI 13.2.1 are known to have the following issues:

• Get-HCXMigration
  Тhe Username parameter of the Get-HCXMigration cmdlet is case-sensitive.
  Workaround: Use the username format supported by API. For example, use Administrator@VSPHERE.LOCAL.
• Get-Tag and Get-TagAssignment
  On vCenter Server version 6.5 and 7.0, the Name parameter is case-sensitive.
  Workaround: Use wildcard characters in your parameter value. For example, use Get-Tag -Name "[T]agName".
• New-HCXServiceMesh
  When you run New-HCXServiceMesh, the Service Mesh object accepts destination as an input at the organization virtual datacenter level, but the Service Mesh object is created at an organization level.
• Set-WMCluster
  The default value of the DefaultImageRegistryHostPort parameter is 443, but this is not implemented.
  Workaround: Always define the DefaultImageRegistryHostPort parameter when the DefaultImageRegistryHostname parameter is specified.
• Test-HCXMigration
  Test-HCXMigration throws an exception instead of a warning. This might mislead you that running Start-HCXMigration is not possible.
• Other
  
  • For Windows PowerShell 5.1, when you run a cmdlet and the operation fails on the server side, you might receive a There is an error in the XML document. error message. This is not a valid server error and it is returned when PowerShell is unable to read the actual server-side error.
    Workaround: Update to PowerShell 7 or use the vSphere Web Client to check the actual server-side error.
  • On MacOS, downloading the PowerCLI ZIP file through Chrome fails with an error message of type "VibSign.so" cannot be opened because the developer cannot be verified.
    Workaround: Use Safari or the Mac Terminal to download the PowerCLI ZIP file.