8.0

Table 5-1. Conflict Types (continued)
Conflict
Properties used to
compare Category
Objects Conflict Types
Conflicting
Properties Conflict Resolution Options
in a vCenter
Server.
n cardinality:
Cardinality of
Category, either
Single or Multiple.
n
associableEntityTy
pe: List of vCenter
Server object that
can be associated
with a tag from this
category. A value of
All indicates all
vCenter Server
objects.
conflict. This conflict
indicates that a
category with the
same name exists in
the target vCenter
Server but with
different properties
(cardinality or
associableEntityT
ype).
can be at least
one of two
types:
Cardinality or
AssociableTypes
.
name. The new category
is created with the same
property name as in the
source vCenter Server. All
the tags that were present
under this category is
imported under the newly
created CategoryCopy.
Note
The default resolution
option to resolve
CategoryName conflicts is
COPY.
n MERGE. Conflicting
properties are merged
with the category that is
already present in the SSO.
Properties are merged as
follows:
a
Description. The
description that is
already present is used.
b
Cardinality.
Cardinality cannot
shrink. If there is a
cardinality conflict, the
cardinality is set to
multiple. It cannot be
reduced to single.
c
AssociableTypes.If
either the
associableEntityType
values are null, it is
set to null. Otherwise,
Objects types are
merged.
n
SKIP. Do nothing. All tags
are imported under the
category that exists.
Tags Conflict: A
tag object
always belongs
to a
category
Object. A tag
Name must be
unique only
n name
n description
Only one type of
conflict can be seen
while importing
tags: TagName
conflict. This conflict
indicates that a
Tag with the same
Properties that
can be
conflicting for a
conflict of type:
TagName can be
Description.
n COPY. A copy of the
conflicting tag is created in
the target vCenter Server,
with –-copy appended to
the tag name. Take the
vCenter Server Installation and Setup
VMware, Inc. 84