6.7

Argument Description
-dvr, --dest-vc-rhttps (Optional) The HTTPS port for the vCenter Server pointing to the
destination Platform Services Controller. If not set, the default
443 is used.
--ignore-snapshot
(Optional) Ignore snapshot warnings.
--no-check-certs
(Optional) Ignore certification validations.
--debug
(Optional) Retrieves command execution detail.
-h, --help (Optional) Displays the help message for the cmsso-util
domain repoint command.
Understanding Tagging and Authorization Conflicts
When you run the domain repoint command in pre-check mode, data from the
Platform Services Controller is exported, examined, and conflicts are written to a file.
The following data is exported to the /storage/domain-data/ or
ProgramData/VMWare/vCenterServerdata/domain-data folder:
n
All_Privileges.json
n
All_Roles.json
n
All_TagCategories.json
n
All_Tags.json
These files contain the all the data (Authorization and Tagging) from the vCenter Server on which this
command was run.
If a secondary vCenter Server is provided using the -dvf or --dest-vc-fqdn option, any conflicts are
also exported to the same folder:
n
Conflicts_Roles.json
n
Conflicts_TagCategories.json
n
Conflicts_Tags.json
The following is a sample conflicts file:
<---- Sample Conflict file code block --->
{
"global" : {
"resolution" : "MERGE|SKIP|COPY",
"description" : "Default resolution option used to resolve Role Conflicts is COPY. The
conflicts list describes the differences between Role entities on source and target PSC. If
the source information represents an empty JSON array, it simply means that all the entity
attributes from source and target are identical. If the source lists few entries, it means
that only these entity attributes are missing from the target. If the target lists few entries,
it means that only these entity attributes are missing from the source. Though a global resolution
can be set, it can also be overridden at each conflict level by providing individual resolution
mode."
vCenter Server Installation and Setup
VMware, Inc. 150