8.0

Table 5-1. Conflict Types
Conflict
Properties used to
compare Category
Objects Conflict Types
Conflicting
Properties Conflict Resolution Options
Role conflict n name: Name of the
category.
n
privilegeId
: List of
privileges for the
role.
RoleName conflict
occurs while
importing roles and
a role with the
same name exists in
the target
vCenter
Server but with
different privileges.
Properties that
can be
conflicting for
RoleName conflict
type can be
Privileges.
n COPY. A copy of the
conflicting role is created in
the target vCenter Server,
with –-copy appended to
the role name. The new
role is created with a new
role ID with the same set
of privilege IDs. The new
role ID is updated in the
VPX_ACCESS table. The new
role ID is applicable for
both role name conflict and
role ID conflict.
Note
The default resolution
option to resolve Role
conflicts is COPY.
n MERGE.The MERGE option is
resolved in the following
sequence:
a If the source vCenter
Server has a role with
the same name and
privilege list as a role
in the target vCenter
Server, but the role
IDs are different, the
role ID from the target
vCenter Server is used
and updated in the
VPX_ACCESS table.
b If the source vCenter
Server has a role
with the same name
as a role in the
target vCenter Server,
but with a different
privilege list, then the
privilege lists for both
roles are merged.
n SKIP. Do nothing. The
specific role is skipped.
Tag Category
conflict: A
category name
must be unique
n name: Name of the
category.
Only one type of
conflict can be seen
while importing Tag
Categories,
CategoryName
Properties that
can be
conflicting for
conflict type
CategoryName
n COPY. A copy of the
conflicting category is
created in the target
vCenter Server, with –-copy
appended to the category
vCenter Server Installation and Setup
VMware, Inc. 83