These issues are resolved in vCenter Server 5.5.0b, available at
VMware Download Center. For more information about this version, see the
vCenter Server 5.5.0b Release Notes.
To resolve this issue when you are unable to upgrade to vCenter Server 5.5.0b, replace the
ds.jar file that the vCenter Server Inventory Service utilizes. This resolves
Issue A,
Issue B.
- Log in to the vCenter Server as an Administrator.
- Navigate to the
C:\Program Files\VMware\Infrastructure\Inventory Service\lib
folder. - Locate the
ds.jar
file. - Create a backup copy of the
ds.jar
file. - Download the
ds.zip
file attached to this KB article. - Replace the existing ds.jar file with the new file.
Note: If you are using vCenter Server Heartbeat 6.x, repeat these steps on both Heartbeat nodes.
- Restart the VMware Inventory Service and the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Note: To work around this issue for Issue A and Issue B, create a Local OS identity source in vCenter Server Single Sign-On using the vSphere Web Client. You can perform this workaround on any virtual machine that is part of vCenter Server Linked Mode.
To add the Local OS identity source:
- Log in to the vSphere Web Client as [email protected] or as another user with SSO administrator privileges.
Note: The default vSphere Web Client URL is https://client-hostname:9443/vsphere-client
- Navigate to Administration > Single Sign-On > Configuration.
- Click the Identity Sources tab then click the Add Identity Source icon (
). - Select Local OS.
- In the Name field, type the short name of the vCenter Server.
- Click OK.
- Log out of the vSphere Web Client and log back in.