Administration

Table Of Contents
Usage Notes
Duplicate LDAP entries on two or more Connection Server instances can cause problems with
the integrity of LDAP data in Horizon 7. This condition can occur during an upgrade, while LDAP
replication is inoperative. Although Horizon 7 checks for this error condition at regular intervals,
you can run the vdmadmin command on one of the Connection Server instances in the group to
detect and resolve LDAP entry collisions manually.
LDAP schema collisions can also occur during an upgrade, while LDAP replication is inoperative.
Because Horizon 7 does not check for this error condition, you must run the vdmadmin command
to detect and resolve LDAP schema collisions manually.
Options
The following table shows the options that you can specify to detect and resolve LDAP entry
collisions.
Table 12-19. Options for Detecting and Resolving LDAP Entry Collisions
Option Description
-collisions Specifies an operation for detecting LDAP entry collisions
in a Connection Server group.
-resolve Resolves all LDAP collisions in the LDAP instance. If you
do not specify this option, the command only lists the
problems that it finds.
The following table shows the options that you can specify to detect and resolve LDAP schema
collisions.
Table 12-20. Options for Detecting and Resolving LDAP Schema Collisions
Option Description
-schemacollisions Specifies an operation for detecting LDAP schema
collisions in a Connection Server group or Cloud Pod
Architecture environment.
-resolve Resolves all LDAP schema collisions in the LDAP instance.
If you do not specify this option, the command only lists
the problems that it finds.
-global Applies the checks and fixes to the global LDAP instance
in a Cloud Pod Architecture environment. If you do not
specify this option, the checks are run against the local
LDAP instance.
Examples
Detect LDAP entry collisions in a Connection Server group.
vdmadmin -X -collisions
Horizon 7 Administration
VMware, Inc. 293