You can use the vdmadmin command with the -X option to detect and resolve LDAP entry collisions and LDAP schema collisions on replicated Omnissa Horizon Connection Server instances in a group. You can also use this option to detect and resolve LDAP schema collisions in a Cloud Pod Architecture environment.
Syntax
vdmadmin -X [-b authentication_arguments] -collisions [-resolve]
vdmadmin -X [-b authentication_arguments] -schemacollisions [-resolve] [-global]
vdmadmin -X [-b authentication_arguments] -seizeSchemaMaster
vdmadmin -X [-b authentication_arguments] -seizeSchemaMaster [-global]
Usage Notes
Duplicate LDAP entries on two or more Horizon Connection Server instances can cause problems with the integrity of LDAP data in Omnissa Horizon. This condition can occur during an upgrade, while LDAP replication is inoperative. Although Omnissa Horizon checks for this error condition at regular intervals, you can run the vdmadmin command on one of the Horizon 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 Omnissa Horizon 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.
| Option | Description |
|---|---|
| -collisions | Specifies an operation for detecting LDAP entry collisions in a Horizon 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.
| Option | Description |
|---|---|
| -schemacollisions | Specifies an operation for detecting LDAP schema collisions in a Horizon 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. |
The following table shows the options that you can specify to resolve LDAP schema master issues.
| Option | Description |
|---|---|
| -seizeSchemaMaster | Makes the current node the schema master node on the cluster. |
| -global | The schema role is seized on the global Horizon LDAP instance in a Cloud Pod Architecture environment. If you do not specify this option, the schema role is seized on the local Horizon LDAP instance. |
Examples
Detect LDAP entry collisions in a Horizon Connection Server group.
vdmadmin -X -collisions
Detect and resolve LDAP entry collisions in the local LDAP instance.
vdmadmin -X -collisions -resolve
Detect and resolve LDAP schema collisions in the global LDAP instance.
vdmadmin -X -schemacollisions -resolve -global
Make the current node the schema master node on the cluster for a local LDAP instance.
vdmadmin -X -seizeSchemaMaster
Make the current node the schema master node on the cluster for a global LDAP instance in a Cloud Pod Architecture environment.
vdmadmin -X -seizeSchemaMaster -global
Cette page vous a-t-elle été utile ?