Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When you run the lmvutil command with the --initialize, --uninitialize, --join, or --unjoin option, the command does not complete.You see the error: This server encountered a problem unitializing or leaving a Pod Federation. You are unable to retry a lmvutil operation.
Note: This KB outlines steps for recovering a Cloud Pod Architecture pod. For other recovery scenarios please see Recovery scenarios for Horizon 7 environment (70906) .Important: These steps results in the loss of all global data on the affected pod. If there are other pods in the pod federation, you can rejoin the affected pod to the pod federation to restore the global data after performing these steps. Note: Service names and LDAP Distinguished Names (DNs) between pod-local and global configuration items are similar. To avoid unintended damage, match strings exactly. For more information about connecting to the View ADAM database, see Connecting to the View ADAM Database (2012377) . To resolve this issue, remove the global configuration from the affected pod manually.To remove the global configuration from the affected pod manually: Identify and mark the affected servers as not enabled. On one of the servers in the pod, use ADSI Edit to connect to localhost:389 with DN dc=vdi,dc=vmware,dc=int. Note: To connect Cloud Pod ADAM DB use dc=vdiglobal,dc=vmware,dc=intCheck the pae-LinkedModeEnabled attribute on these RDNs: cn=common,ou=global,ou=lmv,ou=properties cn=<each-connection-server>,ou=server,ou=lmv,ou=properties For each RDN, if the attribute value is 0 or -1, do not modify the value. If the value is 1, change it to -1.Note each server that originally had a value that was not 0. Remove the global configuration from each server. For each server that you noted in Step #1, check whether AD LDS Instance VMwareVDMDSG is installed. Important: The trailing G in VDMDSG is important. Do not modify the existing non-global instance. If AD LDS Instance VMwareVDMDSG is installed, perform these steps to remove it: Open a command prompt.Run sc qc wsbroker 8192 and check its dependencies.If dependencies include both ADAM_VMwareVDMS and ADAM_VMwareVDMDSG, remove the second dependency by running sc config wsbroker depend= ADAM_VMwareVDMDS. Important: The space after depend= in the above command is intentional and must be specified. Verify that the dependency is removed by running sc qc wsbroker 8192.Uninstall AD LDS Instance VMwareVDMDSG. Correct server replication entries on other pods. You must perform this step only if there are other pods in the federation. Perform this step on only one of the other pods. On one of the servers in a functional pod, use ADSI Edit to connect to localhost:22389 and select the configuration partition. Note: To select the configuration partition, Configuration in the field below Select a well known Naming Context. Browse to CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,CN={GUID} .Remove any entries for the servers that you corrected. Entries are identified by <NETBIOS-name>$VMwareVDMDSG. Mark the pod as explicity not enabled. On one of the servers in the pod, use ADSI Edit to connect to localhost:389 with DN dc=vdi,dc=vmware,dc=int.Check the pae-LinkedModeEnabled attribute on these RDNs: cn=common,ou=global,ou=lmv,ou=properties cn=<each-connection-server>,ou=server,ou=lmv,ou=properties For each RDN, ensure that the value has been explicitly set to 0. Run the join or initialize operation, if necessary. For more information, see the Administering View Cloud Pod Architecture Guide.