You are prompted for the Administrator's password twice, once for the source vCenter Server and once for the destination vCenter Server. Note: I recently wrote an article entitled Change a VMware vCenter Server Appliance (VCSA) system name (FQDN). Where my destination domain name is "vsphere.local" and my destination VCSA fully qualified domain name (FQDN) is "." In my case, the command looks like this: cmsso-util domain-repoint -m pre-check -src-emb-admin Administrator -replication-partner-fqdn -replication-partner-admin Administrator -dest-domain-name vsphere.local The syntax: cmsso-util domain-repoint -m pre-check -src-emb-admin Administrator -replication-partner-fqdn FQDN_of_destination_node -replication-partner-admin PSC_Admin_of_destination_node -dest-domain-name destination_PSC_domain The default resolution mode for Tags and Authorization conflicts is Copy, so even if you don't verify whether there are conflicts, you might end up with some doubles at the destination. In this case, you don't need to perform the precheck since you don't expect any conflicts. Note: You might also need to merge two domains to create a third (new) SSO domain, rather than migrating anything to an existing domain. This can cause problems if your host time and DC time are different. After the precheck, we can use the "execute" option, which will, as its name suggests, execute the actual operations. The only real issue I've seen as a result of joining the VCSA to the domain is that it adds an additional mechanism for time-sync on the guest. We will be migrating this vCenter Server into an existing SSO domain, so we need to do a "precheck" operation and review any conflicts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |