VMware PowerCLI 12.7.0 Release Notes
Released 14 July 2022
VMware PowerCLI 12.7.0. Build 20091289
Check frequently for additions and updates to these release notes.
VMware PowerCLI 12.7.0 Release Notes
This document contains the following information:
About VMware PowerCLI
VMware PowerCLI is a suite of PowerShell modules to manage VMware products and services. VMware PowerCLI includes over 800 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 12.7.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.Vmc: Provides cmdlets for managing VMware Cloud on AWS features.
VMware.VimAutomation.Vds: Provides cmdlets for managing vSphere distributed switches and distributed port groups.
VMware.VimAutomation.HorizonView: Provides cmdlets for automating VMware Horizon features.
VMware.VimAutomation.Srm: Provides cmdlets for managing VMware Site Recovery Manager features.
VMware.VimAutomation.Storage: Provides cmdlets for managing vSphere policy-based storage.
VMware.VimAutomation.Hcx: Provides cmdlets for managing VMware HCX features.
VMware.Sdk.Nsx.Policy: Provides auto-generated cmdlets for accessing the NSX Policy API.
For a list of VMware PowerCLI 12.7.0 supported operating systems and PowerShell versions, see Compatibility Matrixes for VMware PowerCLI 12.7.0.
For a list of VMware products with which VMware PowerCLI 12.7.0 is compatible, see VMware Product Interoperability Matrixes.
What's New in This Release
VMware PowerCLI 12.7.0 introduces the following new features, changes, and improvements:
VMware.VumAutomation module has been ported to work on macOS and Linux.
VMware.Sdk.Nsx.Policy module has been updated to include the following improvements:
UseRemoteAuthentication parameter has been added to the
Connect-NsxServer cmdlet to enable remote authentication.
Get-NsxOperation cmdlet has been modified to return only exact matches of the
Path parameter and to accept target paths in various formats.
VMware.Sdk.Nsx.Policy module has been updated with the latest NSX Policy API features.
- A new cmdlet has been added to the
New cmdlet to specify a vSAN health check threshold.
VMware.VimAutomation.Storage module has been updated to include the following improvements:
CapacityThreshold parameter has been added to the
Set-VsanClusterConfiguration cmdlet to enable the setting of a vSAN health check threshold.
CapacityThreshold property has been added to the
VsanClusterConfiguration object to indicate a vSAN health check threshold.
VMware.VimAutomation.HorizonView module has been updated to support the API features of Horizon 8.4.
For more information on changes made in VMware PowerCLI 12.7.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 12.7.0 Home Page.
The following issues have been resolved in VMware PowerCLI 12.7.0:
Export-VDSwitch and Export-VDPortGroup
The behavior of the parameters
EndDate is swapped.
Connect-SrmServer fails on PowerShell 7.2.2 and later.
Connect-SrmServer performance on Linux is slow.
Export-VDPortGroup fail with an error message of type
Could not load file or assembly ICSharpCode.SharpZipLib or one of its dependencies. The system cannot find the file specified.
Get-VsanClusterConfiguration does not return the full vSAN cluster configuration when remote datastores are mounted in a vSAN HCI Mesh architecture.
Set-VsanClusterConfiguration fails if there is a disk group present when configuring shared witness node.
New-HCXMigration requires target data center as a mandatory value for PCLI OSAM migrations.
There is a delay in getting response from
Multiple VMC cmdlets
Multiple VMC cmdlets use
CisServer instead of
VmcServer as input for the
VMware PowerCLI 12.7.0 is known to have the following issues:
Username parameter of the
Get-HCXMigration cmdlet is case-sensitive.
Workaround: Use the username format supported by API. For example, use
If you try to import
VMware.PowerCLI module on PowerShell Core, you receive an error message and the import process fails.
Workaround: Import each module separately.
When you run
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.
When you run
Set-VsanClusterConfiguration on vSAN 6.5 or vSAN 6.6, the
RemoveSilentHealthCheck parameters do not update any values.
Workaround: Update to vSAN 6.7.
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 throws an exception instead of a warning. This might mislead you that running
Start-HCXMigration is not possible.
- Get-CustomCertificates, Add-CustomCertificate and Remove-CustomCertificates
Remove-CustomCertificates fail with a message of type
Unsupported version URI.
- 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.