Provide a potential workaround in situations where severe environment latency is present between the vCenter Server and domain controllers.

Symptoms:
lw-measure tool shows latency to Active Directory nodes is high.

Note: lw-measure tool and instructions listed in Using the lw_measure tool to detect latency between vCenter Server and Active Directory domain controllers

If either of the last two numbers are around 300000000 usec (300 seconds), it indicates severe latency in the communication between the vCenter and domain controller.

VMware vCenter Server Appliance 6.7.x
VMware vCenter Server Appliance 6.5.x

SSO uses likewise to contact Active directory environments. The default timeout is set to 5 minutes. In environments where high latency exists between vCenter and Active Directory, reducing the timeout will allow likewise to try other available DCs where less latency exists.

To resolve this issue a new value must be added to the registry to control the connection timeout:

1. Connect to the vCenter Server Appliance with an SSH session and root credentials.
2. Run this command to switch to the bash shell

3. Run this command to add the registry entry:

4. Run this command to change the EchoInterval to 30 (Minimum supported value):

5. Restart the vCenter Server Appliance services by running:

To revert the workaround:

1. Connect to the vCenter Server Appliance with an SSH session and root credentials.
2. Run this command to switch to the bash shell

3. Run this command to remove the registry entry:

4. Run this command to change the EchoInterval to 300 (default value):

5. Restart the vCenter Server Appliance services by running: