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

Data synchronization

Even though all data sent between forests is encrypted, Collaboration Services does not store or transmit to other forests any security-related user data, such as account SIDs or passwords. Only data required to provide inter-forest user collaboration is transmitted, such as object names and other attributes, email addresses, and group membership.

Collaboration Services is capable of synchronizing the following mail or mailbox-enabled objects and information:

Each forest administrator decides which objects (and which of their attributes) should be published and added to the GAL in other forests after subscription, and whether the calendar or free/busy information of the published objects should be available for users in other forests.

Collections

To provide flexibility, the objects to be synchronized are grouped into collections—sets of objects and their attributes. You can either define the objects to be synchronized on per-container or per-group basis; or add groups, users, and contacts to collections explicitly.

Depending on your license type, you can create collections of mixed type, Active Directory-only collections, Calendar-only collections, and Free/Busy-only collections:

The synchronization process

Two way synchronization is not possible in Collaboration Services. Two way synchronization would allow the subscribing side to change attributes to a publishing partner’s data and this would violate the security of Active Directory and Exchange. The administrator of the publication primarily controls the data and who can access it in the publication. Without this capability, synchronization security cannot be guaranteed. The same applies to subscriptions where the receiving partner decides which subscriptions to subscribe to.

Two way synchronization

Two way synchronization is not possible in Collaboration Services. Two way synchronization would allow the subscribing side to change attributes to a publishing partner’s data and this would violate the security of Active Directory and Exchange. The administrator of the publication primarily controls the data and who can access it in the publication. Without this capability, synchronization security cannot be guaranteed. The same applies to subscriptions where the receiving partner decides which subscriptions to subscribe to.

Documentos relacionados