6.0.3

b For each domain controller, verify forward and reverse resolution by running the following
command:
# dig my-controller.my-ad.com
The relevant addresses are in the answer section, as in the following example:
;; ANSWER SECTION:
my-controller.my-ad.com (...) IN A controller IP address
...
# dig -x <controller IP address>
The relevant addresses are in the answer section, as in the following example:
;; ANSWER SECTION:
IP-in-reverse.in-addr.arpa. (...) IN PTR my-controller.my-ad.com
...
3 If that does not resolve the problem, remove the vCenter Server Appliance from the Active Directory
domain and then rejoin the domain. See the vCenter Server Appliance Conguration documentation.
4 Close all browser sessions connected to the vCenter Server Appliance and restart all services.
/bin/service-control --restart --all
vCenter Server Login Fails Because the User Account is Locked
When you log in to vCenter Server from the vSphere Web Client login page, an error indicates that the
account is locked.
Problem
After several failed aempts, you cannot log in to the vSphere Web Client using vCenter Single Sign-On.
You see the message that your account is locked.
Cause
You exceeded the maximum number of failed login aempts.
Solution
n
If you log in as a user from the system domain (vsphere.local), ask your vCenter Single Sign-On
administrator to unlock your account. As an alternative, you can wait until your account is unlocked, if
the lock is set to expire in the password policy. vCenter Single Sign-On administrators can use CLI
commands to unlock your account.
n
If you log in as a user from an Active Directory or LDAP domain, ask your Active Directory or LDAP
administrator to unlock your account.
VMware Directory Service Replication Can Take a Long Time
If your environment includes multiple Platform Services Controller instances, and if one of the
Platform Services Controller instances becomes unavailable, your environment continues to function. When
the Platform Services Controller becomes available again, user data and other information are usually
replicated within 60 seconds. In certain special circumstances, however, replication might take a long time.
Problem
In certain situations, for example, when your environment includes multiple Platform Services Controller
instances in dierent locations, and you make signicant changes while one Platform Services Controller is
unavailable, you do not see replication across VMware Directory Service instances right away. For example,
you do not see a new user that was added to the available Platform Services Controller instance in the other
instance until replication is complete.
vSphere Security
62 VMware, Inc.