Workaround:Add the vCenter VPXD solution user directly to the Administrators group.
There is an script to take care of such :
-----BEGIN SCRIPT-----
#!/bin/sh
HOST=localhost
ADMIN=cn=Administrator,cn=Users,dc=vsphere,dc=local
/opt/likewise/bin/ldapmodify -h "$HOST" -D "$ADMIN" -W <<EOM
dn: cn=Administrators,cn=Builtin,dc=vsphere,dc=local
changetype: modify
add: member
member: CN=vpxd-42a9751e-4839-427b-####-###########,CN=ServicePrincipals,dc=vsphere,dc=local
EOM
-----END SCRIPT-----
NOTES: You would just have to find the particular VPXD solution user name for this vCenter instance and replace that in the script above (i.e. replace 'vpxd-42a9###-####-...' with the real VPXD solution user name).
This solution user can be found by running the following on VC
/usr/lib/vmware-vmafd/bin/dir-cli group list --name SolutionUsers Also keep in mind that your Domain may not be [
vsphere.local] as example could be [
###.vi]
Example of steps to run the WA :
#0- I ran the following from the VC with the aim of finding the VPXD solution ID but I see 3 possible VPXD solution IDS
root@vcenter-wl1 [ ~ ]#
/usr/lib/vmware-vmafd/bin/dir-cli group list --name SolutionUsersEnter password for administrator@###.vi:
CN=machine-6f562e3d-ad1e-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=vsphere-webclient-6f562e3d-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=vpxd-6f562e3d-ad1e-42f0-####-####################,CN=ServicePrincipals,DC=###,DC=vi ###1####CN=vpxd-extension-6f562e3d-ad1e-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=hvc-6f562e3d-ad1e-42f0-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=wcp-6f562e3d-ad1e-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=workload_storage_management-6f562e3d-ad1e-####-#####################,cn=ServicePrincipals,dc=###,dc=vi
CN=hvc-a5f26514-f634-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=wcp-a5f26514-f634-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=workload_storage_management-a5f26514-f634-####-#####################,cn=ServicePrincipals,dc=###,dc=vi
CN=machine-f04b80a3-b97b-4ebb-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=vsphere-webclient-f04b80a3-b97b-4ebb-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=vpxd-f04b80a3-b97b-4ebb-####-####################,CN=ServicePrincipals,DC=###,DC=vi ###2###CN=vpxd-extension-f04b80a3-b97b-4ebb-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=hvc-f04b80a3-b97b-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=wcp-f04b80a3-b97b-4ebb-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=workload_storage_management-f04b80a3-b97b-4ebb-####-#####################,cn=ServicePrincipals,dc=###,dc=vi
CN=machine-4bd6131a-c5cf-4cdf-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=vsphere-webclient-4bd6131a-c5cf-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=vpxd-4bd6131a-c5cf-4cdf-####-####################,CN=ServicePrincipals,DC=###,DC=vi ###3###CN=vpxd-extension-4bd6131a-c5cf-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=hvc-4bd6131a-c5cf-4cdf-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=wcp-4bd6131a-c5cf-4cdf-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=workload_storage_management-4bd6131a-####-#####################,cn=ServicePrincipals,dc=###,dc=vi
CN=nsxt_834ac160-40cb-####-#####################,cn=ServicePrincipals,dc=###,dc=vi
CN=VMware_CWP_SOLUTION_d6aa2a05-4201-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=VMware_CWP_SOLUTION_9f744faf-82bc-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=VMware_CWP_SOLUTION_6cb5cc54-fe4f-4208-####-#####################,CN=ServicePrincipals,DC=###,DC=vi
CN=nsxt_698d01e8-5a20-4d84-####-#####################,cn=ServicePrincipals,dc=###,dc=vi
root@vcenter-wl1 [ ~ ]#
From the output above we took the 3 possible VPXD solution IDS
CN=vpxd-6f562e3d-ad1e-####-#####################,CN=ServicePrincipals,DC=###,DC=vi ####1####
CN=vpxd-f04b80a3-b97b-####-#####################,CN=ServicePrincipals,DC=###,DC=vi ####2####
CN=vpxd-4bd6131a-c5cf-####-#####################,CN=ServicePrincipals,DC=###,DC=vi ####3####
#1- SSH into VC
#2- Create 3 separated scripts
vim user1solution.sh
#!/bin/sh
HOST=localhost
ADMIN=cn=Administrator,cn=Users,dc=###,dc=vi
/opt/likewise/bin/ldapmodify -h "$HOST" -D "$ADMIN" -W <<EOM
dn: cn=Administrators,cn=Builtin,dc=###,dc=vi
changetype: modify
add: member
member: CN=vpxd-6f562e3d-ad1e-42f0-####-#####################,CN=ServicePrincipals,dc=###,dc=vi
EOM
vim user2solution.sh
#!/bin/sh
HOST=localhost
ADMIN=cn=Administrator,cn=Users,dc=###,dc=vi
/opt/likewise/bin/ldapmodify -h "$HOST" -D "$ADMIN" -W <<EOM
dn: cn=Administrators,cn=Builtin,dc=###,dc=vi
changetype: modify
add: member
member: CN=vpxd-f04b80a3-b97b-####-#####################,CN=ServicePrincipals,dc=###,dc=vi
EOM
vim user3solution.sh
#!/bin/sh
HOST=localhost
ADMIN=cn=Administrator,cn=Users,dc=###,dc=vi
/opt/likewise/bin/ldapmodify -h "$HOST" -D "$ADMIN" -W <<EOM
dn: cn=Administrators,cn=Builtin,dc=###,dc=vi
changetype: modify
add: member
member: CN=vpxd-4bd6131a-c5cf-####-#####################,CN=ServicePrincipals,dc=###,dc=vi
EOM
#3-- Give execute rights to all 3 files
chmod a+x user1solution.sh
chmod a+x user2solution.sh
chmod a+x user3solution.sh
# --Run the Scripts
./user1solution.sh
./user2solution.sh
./user3solution.sh
#4-- Go back to the failed Compute Manager registration and you should click on error on Registration status and resolve the error.