When I login to our vCenter 6 Update 1 Appliance (embedded PSC) via the Web Client with an Active Directory Integrated ID, select "System Configuration", then select the vCenter node, the summary screen does not display any IP or Hostname information. Additionally, uptime and workload status for storage/memory/swap/workload all display "Unknown." See attached picture for reference.
Any values under Manage -> Settings are also blank.
When I login with administrator@vsphere.local, all the above mentioned values are displayed and I can modify the settings for the vCenter Appliance as expected. This made me suspect a permission issue exists, but I'm unable to figure out which SSO group to add our AD accounts under to enable management/monitoring of the vCenter appliance to make this work as expected.
Already tried adding our accounts to the following groups in SSO under the vsphere.local domain:
DCAdmins
SystemConfiguration.Administrators
ComponentManager.Administrators
Administrators
This information on each group's purpose unfortunately did not help me understand which one(s) might be applicable:
Groups in the vsphere.local Domain
Thank you very much for the help!
I just did some digging on this myself (we have 6.0 U2 deployed now) after I tried the same things (adding AD users into the SSO domain groups, etc. etc.) with no success.
What I finally found is that this is just plain a KNOWN ISSUE with 6.0 U2 and perhaps they'll fix it with 6.0 U3 whenever that comes out (later this Summer)? Maybe it'll be 6.5 by then, with an announcement at VMworld 2016 or something---who knows.
The workaround is a joke --- suggesting deploying via only the default SSO domain. Well, that's never going to happen of course, so what they should have said as a workaround is, if you really need to get in and view the status, etc. from within the web client, just log on with your administrator@vsphere.local account that was created at original time of installation.
VMware vCenter Server 6.0 Update 2 Release Notes
*****
Attempts to configure and view information about the vCenter Server Appliance by using the System Configuration page in the vSphere Web Client fail with errors
Log in to the vCenter Server instance in the vCenter Server Appliance with a user who is in a custom-named (different from the default vsphere.local) Single Sign-On domain by using the vSphere Web Client. On the vSphere Web Client Home page, click System Configuration and under System Configurationselect Nodes. If you attempt to edit the settings, restart or power off a node of the vCenter Server Appliance, the operation fails with one of the following errors:An internal error has occurred - Error # 1009
and Not authorized to use this API
. If you click the Summary, Monitor, or Manage tabs, some information about the appliance might not be displayed.
Workaround: Deploy the vCenter Server Appliance only by using the default Single Sign-On domain: vsphere.local.
Hi,
Did you ever find a solution to this? I have the exact issue.
Thanks
I just did some digging on this myself (we have 6.0 U2 deployed now) after I tried the same things (adding AD users into the SSO domain groups, etc. etc.) with no success.
What I finally found is that this is just plain a KNOWN ISSUE with 6.0 U2 and perhaps they'll fix it with 6.0 U3 whenever that comes out (later this Summer)? Maybe it'll be 6.5 by then, with an announcement at VMworld 2016 or something---who knows.
The workaround is a joke --- suggesting deploying via only the default SSO domain. Well, that's never going to happen of course, so what they should have said as a workaround is, if you really need to get in and view the status, etc. from within the web client, just log on with your administrator@vsphere.local account that was created at original time of installation.
VMware vCenter Server 6.0 Update 2 Release Notes
*****
Attempts to configure and view information about the vCenter Server Appliance by using the System Configuration page in the vSphere Web Client fail with errors
Log in to the vCenter Server instance in the vCenter Server Appliance with a user who is in a custom-named (different from the default vsphere.local) Single Sign-On domain by using the vSphere Web Client. On the vSphere Web Client Home page, click System Configuration and under System Configurationselect Nodes. If you attempt to edit the settings, restart or power off a node of the vCenter Server Appliance, the operation fails with one of the following errors:An internal error has occurred - Error # 1009
and Not authorized to use this API
. If you click the Summary, Monitor, or Manage tabs, some information about the appliance might not be displayed.
Workaround: Deploy the vCenter Server Appliance only by using the default Single Sign-On domain: vsphere.local.
Wow this is unfortunate for the workaround, but greatly appreciate the link to the release notes where the issues is documented as a known problem! If nothing else, it at least puts the issue to rest with trying to resolve it. We work-around the problem by logging in with the administrator@vsphere.local account when we need to see this information under System Configuration, which is a pain but better than nothing. Thanks!