Search the VMware Knowledge Base (KB)
View by Article ID

After upgrading to VMware vCenter Server Appliance 6.0 users are unable to view the inventory in the vSphere Web Client (2125628)

  • 8 Ratings


  • After upgrading the vCenter Server Appliance to 6.0, Active Directory user accounts show an empty inventory when logging into the vSphere Web Client.
  • This issue is not seen in the vSphere Client.
  • Accounts that are part of the vsphere.local identity source do not have this issue.
  • Attempting to remove the user account(s) permissions does not resolve the issue.


This issue occurs when permissions for Active Directory user accounts were added in vCenter Server 5.x based on the NetBIOS alias of the domain. As of vSphere 6, permissions are now added based on the domain specified in the user's User Principal Name (UPN) and any users added prior to vSphere 6.0 will retain the NetBIOS alias.


This issue is resolved in VMware vCenter Server Appliance 6.0 Update 2, available at VMware Downloads.

To work around the issue without upgrading, correct the permission entries in the vCenter Server Appliance database to have the full domain name.
  1. Open a console to the vCenter Server Appliance.
  2. Stop the vCenter Server services. For more information, see Stopping, starting, or restarting VMware vCenter Server Appliance 6.0 services (2109887).
  3. Take a backup the vCenter Server Appliance database. For more informaiton, see Back up and restore vCenter Server Appliance/vCenter Server vPostgres database (2091961).
  4. Run this command to access the vCenter Server Appliance database:

    /opt/vmware/vpostgres/current/bin # ./psql -d VCDB -U postgres

  5. Run these commands to update the domain entries:

    update CIS_KV_KEYVALUE set KV_KEY = replace(kv_key,'DOMAIN%5C','DOMAIN.COM%5C');

    update CIS_KV_KEYVALUE set KV_VALUE = replace(kv_value,'DOMAIN\','DOMAIN.COM\');

    Note: Where DOMAIN is the original domain alias and DOMAIN.COM with the full domain name.

  6. Use the \q command to exit the database.
  7. Reboot the vCenter Server appliance.

See Also

Update History

03/15/2016 - Added the details of the vCenter Server Appliance 6.0 Update 2 release, which resolves this issue.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 8 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 8 Ratings