This is a known issue in VMware vCenter Server 5.1.0a and 5.1.0b.
To work around this issue when you do not want to upgrade, update the sts URL in the vpxd.cfg file.
Note: The vpxd.cfg file is located at C:\ProgramData\VMware\VMware VirtualCenter.
To update the sts URL in the vpxd.cfg file:
- Open the SsoData/ssoLocations.txt file using a text editor.
- This file may be located in the temporary ( %tmp%) folder, if it is not use the lookup service to get the URL:
- Open a command prompt as administrator, change the directory to:
C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ssoregtool
Note: Adjust the commands depending on where you have installed vCenter Server.
- Run the commands:
SET JAVA_HOME=C:\Program Files\VMware\Infrastructure\jre
regtool.cmd storeSsoData -d https://SSO_Server_FQDN:7444/lookupservice/sdk -f output_path
- Open the location you specified in step 2.b in the regtool command and find the sts URL in the ssoLocations.txt file.
- Locate the sts URL within the SsoData/ssoLocations.txt file.
For example:
groupcheck = https://<lookup service-ip>:7444/sso-adminserver/sdk
admin = https://<lookup service-ip>:7444/sso-adminserver/sdk
sts = https://<lookup service-ip>:7444/sso-adminserver/sdk
-
Copy the sts URL from the ssoLocations.txt file and update the sts URL in the vpxd.cfg, for example:
<sts>
<uri>https://<lookup service-ip>:7444/sso-adminserver/sdk</uri>
</sts>
Note: Run the vCenter Server installer to install Profile-Driven Service.