Collaboration Services 3.8 - Deployment Guide

About this document About Collaboration Services Architecture and functionality Before you begin Platform considerations Pre-Installation planning Prepare for use Collaboration Services upgrade Installation checklists Re-Installing Collaboration Services Troubleshooting

Conflicting email addresses

When Collaboration Services creates a stub object, it verifies that no other object with the same address exists in the forest by querying the nearest Global Catalog. If the object already exists, Collaboration Services can take any of the following actions:

When configuring the matching, you can choose the attribute synchronization direction on a per-attribute basis, so some or all attributes are synchronized from the published object to the object you are matching into. Attribute synchronization is useful if the user account is updated by the provisioning system in one of the forests and these changes need to be propagated to the same user’s accounts in other forests.

If you have active user accounts of the same user in multiple forests but do not want to use matching for some reason, you can do one of the following:

Other conflicts

There can be other conflicts that are not detected and resolved by Collaboration Services automatically because the conflicting objects do not cause technical issues, but can confuse the end users. Examples include:

Step 3: Plan Collaboration Services configuration

After you decide how conflicts will be resolved in each forest, you can plan the Collaboration Services configuration. The main decision will be which forest should serve as the headquarters (HQ) for Collaboration Services synchronization. Only one HQ forest can be set up in a Collaboration Services environment.

Consider the following criteria when selecting the HQ forest:

To increase synchronization performance and reduce network traffic and HQ server load, choose the forest containing the most data to be synchronized.

The HQ forest processes all synchronized data from all synchronization partners. Therefore, there is a higher data processing load on the HQ Collaboration Services server, which means higher hardware requirements.

The HQ forest administrator will be a key person to help other partners in tuning performance and troubleshooting problems for the whole Collaboration Services structure.

You must also consider how you will form object collections. This decision may require additional environment preparation. Collaboration Services allows both explicit and dynamic object selection.

Dynamic object selection may be based on the following:

Decide if you need mappers to customize Collaboration Services synchronization. For example, consider using mappers if:

Choose the HQ forest

After you decide how conflicts will be resolved in each forest, you can plan the Collaboration Services configuration. The main decision will be which forest should serve as the headquarters (HQ) for Collaboration Services synchronization. Only one HQ forest can be set up in a Collaboration Services environment.

Consider the following criteria when selecting the HQ forest:

To increase synchronization performance and reduce network traffic and HQ server load, choose the forest containing the most data to be synchronized.

The HQ forest processes all synchronized data from all synchronization partners. Therefore, there is a higher data processing load on the HQ Collaboration Services server, which means higher hardware requirements.

The HQ forest administrator will be a key person to help other partners in tuning performance and troubleshooting problems for the whole Collaboration Services structure.

You must also consider how you will form object collections. This decision may require additional environment preparation. Collaboration Services allows both explicit and dynamic object selection.

Dynamic object selection may be based on the following:

Decide if you need mappers to customize Collaboration Services synchronization. For example, consider using mappers if:

Documentos relacionados