VDT reports "Machine ID Check" or "Solution User Cert Parity Checks" FAIL due to Likewise registry mismatch

search cancel

book

calendar_today

VMware vCenter Server VMware vCenter Server 8.0

Running the VCF Diagnostic Tool for vSphere (VDT) 2.2.9 or later returns a [FAIL] for Machine ID Check or Solution User Cert Parity Checks.
vCenter Server functions (SSO, certificates, login) appear to be working normally.
VDT reports a "Current MID" that does not exist in /etc/vmware/install-defaults/sca.hostid
Running /usr/lib/vmware-vmafd/bin/vmafd-cli get-machine-id --server-name localhost returns the "Correct MID" identified by VDT, but the failure persists.
Manual inspection of the Likewise registry shows an incorrect UUID: /opt/likewise/bin/lwregshell list_values '[HKEY_THIS_MACHINE\Services\vmdir]' "MachineGuid"

VMware vCenter Server 8.x

The Likewise registry MachineGuid shows an incorrect UUID compared to the VMAFD Machine ID and the sca.hostid file.

Update the Likewise registry to match the authoritative VMAFD Machine ID.

Take an offline (powered off) snapshot of the vCenter Server. If the vCenter is part of an Enhanced Linked Mode (ELM) domain, offline snapshots of all replication partners are required.

Refer: Snapshot Best practices for vCenter Server Virtual Machines
Run the following command and note the UUID returned.

/usr/lib/vmware-vmafd/bin/vmafd-cli get-machine-id --server-name localhost
Use lwregshell to set the MachineGuid to the value obtained in Step 2.

/opt/likewise/bin/lwregshell set_value '[HKEY_THIS_MACHINE\Services\vmdir]' 'MachineGuid' '<UUID_FROM_STEP_2>'
Apply the change by restarting all vCenter services:

service-control --stop --all && service-control --start --all
Re-run the VDT tool to confirm the checks now pass.

thumb_up Yes

thumb_down No