Sync Levels and Trim DN

Levels and Trim DN are located on the Destination tab.

Note: When changing Levels, be sure to run Discovery and SIMULATION to review results before running a SYNC. For previously synced contacts, you can expect to see a Move/Mod for all objects.

Sync Levels: How many OUs of Source structure do you want replicated from the Source to the Destination directory?

By default, Levels is blank (or zero). On the Destination, all synced objects are placed in a single ‘flat’ directory as specified by Struct Name and/or Placement DN.

To replicate source OU structure, creating the same structure on the Destination, you may elect to set Levels to a value greater than zero. Or, use ‘ALL’ instead of a number.

The Levels setting replicates the structure as it appears under the root of the Source tab’s Source Context.

Note: This requires permission on the destination Sync OU allowing the destination login permission to create an OU.

Example:

Source tab, Source Context is OU=AllContacts,dc=domain,dc=com

This OU contains sub OUs
ou=Sales,ou=AllContacts,dc=domain,dc=com
ou=Support,AllContacts,dc=domain,dc=com

When levels is set to 1, the structure under ou=All Contacts are created under your Sync OU.

Destination tab, Placement DN (sync OU) ou=External Contacts,dc=alpha,dc=com

The following OUs would be created on the destination: ou=Sales,ou=External Contacts,dc=alpha,dc=com ou=Support,ou=External Contacts,dc=alpha,dc=com

If the Source context’s Sub OUs contain OUs, you can use Levels = ALL to replicate the entire structure.

Trim DN:

Sometimes, depending on your Source OU, the replicated structure may not be quite right.

Trim DN is not a commonly used feature. Trim DN is available when Levels > 0. This option allows you to redefine the levels (container structure) that are replicated to the Destination. The actual components available for trimming as well as the actual Trim results will vary depending on your environment and connection configuration. The best way determine if Trim DN is useful in your connection is to run Discovery and Simulation, then review the log file to review the container structure of each object as it is added. Depending on the type of object being created, there may be additional configurations required. More information on Trim DN is available in our knowledge base.

Trim DN attribute is found on the Destination tab and is generally used in conjunction with levels greater than zero.

Positive Trim DN Values

Positive Trim will remove DN components from the left, omitting the component from the Destination structure when the new object is created. This feature may also be used to add components that might not otherwise be included in the default structure replication. Only Source domain components included in the ‘Source Context’ may be trimmed using this feature.

IMPORTANT NOTE: The actual components available for trimming as well as the actual Trim results will vary depending on your environment and connection configuration. The best way determine if Trim DN is useful in your connection is to run Discovery and Simulation. Then review the log file to review the container structure of each object as it is added.

Any number of level trimming is supported, 1, 2, 3, etc. Any level above the number of Source Context structures will be ignored as Source container structure is never trimmed.

Positive Trim DN Examples

The following examples assume the following:

• Source IP is a domain controller (but not a global catalog). If the Source IP points to a domain controller, then Source Context may be simply dc=com and therefore only dc=com is available for trimming.

• Source DN: In format of cn=user,ou=sub2,ou=sub1,ou=contacts,dc=domainA,dc=com

• Struct Name: Your sync container/ou name; example SyncContainer

• Source Context: In format of dc=domainA,dc=com

• Selection DN is not specified.

• Levels: All

Examples

In this example, only 2 levels are available for trimming. So any higher trim will simply return the same results as Trim=2.

Trim DN=0

Destination DN: cn=user,ou=sub2,ou=sub1,ou=contacts,ou=domainA,ou=com,ou=SyncContainer,dc=DestDomain,dc=com

Trim DN = 1

Destination DN: cn=user,ou=sub2,ou=sub1,ou=contacts,ou=domainA,ou=SyncContainer,dc=DestDomain,dc=com

Trim DN = 2 (default / blank) Destination DN: cn=user,ou=sub2,ou=sub1,ou=contacts,ou=SyncContainer,dc=DestDomain,dc=com

Trim DN = 3 and up Destination DN: cn=user,ou=sub2,ou=sub1,ou=contacts,ou=SyncContainer,dc=DestDomain,dc=com

Negative Trim DN values

Negative Trim values may be used when a container or domain is specified in the Source Tab’s Selection DN parameter. Negative Trim values always add DN components that are not part of the replicated structure by default.

Like Positive Trim, Negative Trim function only Adds structure based on the Source Context specified. In this case, the Source Context is equal to the Selection DN.

Negative Trim DN Examples

The following examples assume the following:

• Source DN: In format of cn=user,ou=sub2,ou=sub1,ou=contacts,dc=domainA,dc=com

• Struct Name: Your sync container/ou name; example SyncContainer

• Source Context: In format of dc=domainA,dc=com

• Selection DN is ou=sub1,ou=contacts,dc=domainA,dc=com

• Levels: All

In this case we are pointing directly to ou=sub1 using Selection DN. Normally, this level and any above it would not be replicated to the Destination. Negative Trim allows you to opt for these levels to be added back in from left to right.

Trim DN = blank (default) Destination DN: cn=user,ou=sub2,ou=SyncContainer,dc=DestDomain,dc=com

Trim DN = -1 Destination DN: cn=user,ou=sub2,ou=sub1,ou=SyncContainer,dc=DestDomain,dc=com

Trim DN = -2 Destination DN: cn=user,ou=sub2,ou=sub1,ou=contacts,ou=SyncContainer,dc=DestDomain,dc=com

Trim DN = -3 Destination DN: cn=user,ou=sub2,ou=sub1,ou=contacts,ou=domainA,ou=SyncContainer,dc=DestDomain,dc= com

If you have any questions regarding Trim DN and its uses. please contact Technical Support.