VDT output shows an orphaned SSO registration

Products

• VMware vCenter Server

Issue/Introduction

The output of the VDT (vCenter Diagnostic Tool) shows one or more orphaned SSO service registrations such as the example below:

   SSO CHECKS

        VC Lookup Service Check

            • SSO Site: default-first-site

                • [PASS]    ########.###.### (VC Server or CGW)

                • [PASS]    ########.###.### (VC Server or CGW)

                • [FAIL]    ##NO_HOSTNAME##
                    [FAIL]    3rd party/Orphaned service registrations.  Additional investigation needed:
                                Type: com.dell.plugin.OpenManager_HWSupportManager, ID: #########-####-####-#####-

Environment

VMware vCenter Server 8.x

Cause

This is a result of left over service registrations from one or more third party services that integrate with vCenter Server, when those services are improperly removed.

Resolution

The stale SSO service registration will not impact operation of vCenter Server if left there untouched.

However, if the requirement is that it must be removed, then the first step is to perform powered off snapshot of your vCenter Server. Additionally, please make sure you have successful backups of vCenter Server in the event something unexpected occurs.

Subsequently, you can either use the MOB (Managed Object Browser) of vCenter Server to remove any orphaned service registrations. However, be careful only to remove the one that was indicated by the VDT script.

The general process to remove an extension from the vCenter MOB is as follows:

• Navigate to the vCenter Server MOB at https://<vCenter_IP_or_FQDN>/mob.

• Log in with your vSphere Administrator credentials (e.g., [e-mail]).

• Click on Content.

• Click on ExtensionManager (listed under the extensionManager property).

• Under the Properties list, expand extensionList to verify the exact string of the stale extension key you wish to remove.

• Scroll down to the Methods section and click UnregisterExtension.

• A new pop-up window will appear. Paste the exact extension key (e.g., com.vmware.vcDr) into the Value string field.

• Click Invoke Method.

• If successful, the result will display void. You can refresh the ExtensionManager page to confirm the key is no longer listed.

NOTE: As a precautionary step, make sure you have atleast two different methods of rollback available before you proceed - for example a cold clone of vCenter Server, a powered-off snapshot of vCenter Server, a vCenter Database backup.

 

Additional Information

Similar KB articles for MOB-based removal of other service registrations:

Cleaning up decommissioned SRM registration from vCenter Server

Clean up the vCenter Server Extension Manager