Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Collaboration Services 3.10.1 - 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

Step 2: Configure Collaboration Services

Once a Collaboration Services instance is installed in each forest, you need to configure each instance to fit your environment.

Use the synchronization settings to fine-tune the interaction between Active Directory, Exchange, and Collaboration Services instances, and the connectivity between the synchronization partners. To open the Collaboration Services Properties dialog box, select the Collaboration Services node in the management tree and Properties from its shortcut menu.

Set up conflict resolution rules

You can choose either automatic or manual conflict resolution:

•
In most cases, you can configure the service to resolve the conflicts automatically. To do that, select and configure the desired conflict resolution method.
•
Alternatively, you can choose to resolve conflicts manually, which is quite convenient during product testing. Just wait for a conflicting object to appear in the Non-Applied Objects queue, and then either approve the conflict resolution actions suggested by Collaboration Services or choose a custom conflict resolution action.

Check namespace settings

Carefully check the namespace settings after deployment. During the setup, Collaboration Services automatically populates namespaces with values from the Exchange organization’s recipient policies. Using the wrong namespaces may result in incorrect mail forwarding or an inability to create the stub objects at all. Refer to the Quest Collaboration Services User Guide for more information on using namespaces.

Step 3: Publish test collections

Once the Collaboration Services instances are configured in each of the forests, you can publish a test collection from each forest. The test collections should be published a week before publishing all users objects.

When creating the test collections, you should specify the same synchronization type you are planning to use with regular collections. Depending on your license type, you can create collections of mixed type, Active Directory-only collections, and calendar or free/busy-only collections. For descriptions of these types, see Collections .

* 
NOTE: A Collaboration Services administrator in each branch and in the HQ forest must subscribe to the test collections manually in order for the collection objects to be applied to their forests.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation