Enabling the TLSv1.1 and TLSv1.2 protocols for PowerCLI
search cancel

Enabling the TLSv1.1 and TLSv1.2 protocols for PowerCLI

book

Article ID: 333523

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

PowerCLI communication with vCenter Server might fail when the vCenter Server system is configured to use the TLSv1.1 and TLSv1.2 protocols. Communication between PowerCLI and vCenter Server is determined by the client OS and .NET version.

Resolution

To enable communication between PowerCLI and vCenter Server systems that use the TLSv1.1 or TLSv1.2 protocols, you must edit the Windows registry.
Note: You must use PowerCLI 6.0 R1 or later. Earlier versions of PowerCLI work with versions of the .NET Framework that cannot use the TLSv1.1 and TLSv1.2 protocols by editing the registry.

  • For 32-bit processes, change the following registry key value to 1.

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\[.NET_version]
    Value: SchUseStrongCrypto (DWORD)

  • For 64-bit processes, in addition to the above registry key, change the following registry key value to 1.

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\[.NET_version]
    Value: SchUseStrongCrypto (DWORD)

Powered by Wolken Software