Chatta subito con l'assistenza
Chat con il supporto

Collaboration Services 3.9.1 - User Guide

Getting started with Collaboration Services Organizing objects for synchronization Resolving synchronization conflicts Managing the synchronization process Transport management Fine-tuning and maintenance Backup, restore, and troubleshooting

Deletion

Use this option to make Collaboration Services automatically delete conflicting objects in the selected OUs before creating the stub objects.

Figure 2. Deleting conflicting objects
* 
NOTE: This configuration should be implemented with care, since the objects will be deleted from the selected OUs automatically without further confirmations.
* 
NOTE: Ensure that the Collaboration Services service account has full access to any containers which are selected. If not, the conflict resolution will not be completed and errors will be generated.
To configure the deletion
1
Select the Allow deletion of conflicting objects from the following containers: check box.
2
Click Add, and then Load the list of containers from Active Directory; select the containers from which conflicting objects will be deleted.
You can also import a list of containers from a text file. Click the Import button and choose the file containing the list of containers. The file should list the distinguished names (DNs) of the containers, one DN per line.
3
For each container, specify how the attributes of deleted objects should be handled. To configure attribute handling:
a
Select the container and click Settings.
b
Select the attribute synchronization rule for each attribute.
You can choose from among the following rules:
•
Leave—Preserve the attribute of the deleted object.
•
Replace—Overwrite the attribute with the published object’s attribute (you can click Replace All if this rule should be applied to all selected attributes).
•
Merge—Merge the attributes of the deleted and published objects (this option is available for multi-valued attributes only).
* 
NOTE: A stub object created after deletion of the conflicting object will inherit the following attributes from the conflicting object: LegacyExchangeDN, X500 addresses. Preserving these attributes prevents users from getting non-delivery receipts (NDRs) when replying to older email from a deleted object.
c
You can also do the following:
•
Save the configuration for future use by clicking Save Preset.
•
Load a preset.
•
Restore default settings.
d
Click OK to apply your changes.
* 
NOTE: With the default settings, a stub object created by matching into the conflicting object will replace the targetAddress attribute value of the target object with the redirector address. If you choose to leave the targetAddress attribute of the target object intact, mail redirection might not function properly.
4
To delete the conflicting objects not only in the selected OUs but in the sub-containers as well, select the Apply to all sub-containers check box. In that case, parent OU settings will be propagated to child OUs settings.

Matching

Use this method to make Collaboration Services automatically match published objects into conflicting objects in the selected OUs, thus resolving the conflict.

Figure 3. Matching objects
To configure matching
1
Select the Allow matching to objects from the following containers: check box. Follow the procedure for configuring object attributes found within the section Deletion .
You can select containers and specify how the attributes of objects you match into are handled as described in Deletion section, and the same rules are available for the attributes of target objects.
* 
NOTE: Passwords cannot be synchronized across forests due to the secure nature of Collaboration Services. Therefore, passwords need to be managed separately in each forest.
NOTE: With the default settings, a stub object created by matching into the conflicting object will replace the targetAddress attribute value of the target object with the redirector address. If you choose to leave targetAddress attribute of the target object intact, mail redirection might not function properly.
2
Select the Apply to all sub-containers check box to specify that the conflicting objects should be deleted not only in the selected OUs, but in the sub-containers also. In that case, parent OU settings will be propagated to child OUs settings.

Pre-Matching

On the Pre-matching page you can configure Collaboration Services to match published objects into specified objects automatically in the selected OUs. To match published objects into existing ones, pre-matching rules are used. A rule includes:

•
Email address of the published object
•
Distinguished names (DNs) of the object to match into

Whenever an object with a specified email is synchronized, it will be matched into the object whose DN is stated in the rule.

* 
NOTE: Ensure that the Collaboration Services service account has full access to any containers which are selected. If not, the conflict resolution will not be completed and errors will be generated.
NOTE: The incoming object and the object you are matching into must be of the same object class; in most cases, they are user objects.

 

To configure pre-matching
•
Select the Use custom matching for the following objects: check box to enable the option.

Creating a New Rule and the Pre-Matching Wizard

To create a new rule
1
Click the Add button and follow the steps of the Pre-Matching Wizard.
2
On the Welcome page, click Next.
3
On the Email Address page, click Browse to specify the email address of published object using the Select recipient dialog box and click OK.
4
On the Select Object page, specify the object you want to match into and click Next.
5
On the Attribute Synchronization page, choose how to handle the attributes of objects you match into. Select the Replace, Leave, or Merge (for multi-valued attributes only) attribute synchronization rule for each attribute of the object to match into and click Next.
6
In the message box that appears, click Yes if you want to proceed with creating the new pre-matching rule.
7
View the Summary and click Finish.

For each pre-matching rule you add, you can perform the following actions:

•
Click Remove to delete the rule from the list.
•
Click Settings to change how to handle matching object attributes.
•
Click Import to import a list of pre-matching rules from a text file. The file should contain a list of pairs, one pair per line. Each pair must include the email address of the published object and the distinguished name (DN) of the object to match into, separated by a space.
•
Click Detect to scan Active Directory and update the list of rules if any changes were made to Active Directory (for example, objects were moved).
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione