立即与支持人员聊天
与支持团队交流

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

The service account mailbox

Instances of Collaboration Services installed in the HQ and branch forests communicate with each other using the Simple Mail Transfer Protocol (SMTP), which is a native protocol for Exchange. All communications between partners are performed through administrative mailboxes, one mailbox per forest. The data packets are compressed, grouped in regular email messages, and sent to other service account mailboxes.

* 
TIP: The service account mailbox should be created before installing Collaboration Services. It is defined during the install procedure of Collaboration Services and should not be modified after unless necessary.
To view the service account mailbox information
1
Right-click the Collaboration Services node in the tree, select Properties, select General.
The name of Exchange server where the service mailbox resides is in Exchange server: field.
The mailbox name used by the service account is in the Mailbox: field.
2
Click Test to find out whether the specified mailbox exists on the Exchange server and whether it can be accessed by Collaboration Services.
* 
NOTE: If you change the service mailbox, you must generate a new public key file and distribute it to the other forests so they can update your forest’s key using the Configure Branches or Configure HQ wizard. Until then, communication with other synchronization partners will not be possible.

Recipient Update Service (RUS)

With Collaboration Services version 3.6 and later, the RUS is enabled by default if Exchange 2007 or higher is detected in the Exchange environment. If not selected, published objects will not appear in the Global Address List.

Configure Active Directory access

To configure Active Directory access settings
1
Right-click the Collaboration Services node in the tree, select Properties, select General, and AD Options.
The General account is used to read and update Active Directory data. By default, the service account is used as the general account, but you can use a different account if you want.
* 
NOTE: The permissions required for that account are described in the Rights and Permissions section of the Quest Collaboration Services Deployment Guide.
You can also find more information under Service Account Minimum Rights and Permissions in the Quest Collaboration Services Deployment Guide.
2
Use the Test button to test whether the newly specified account has sufficient permissions.

By default, Collaboration Services uses any available domain controller (DC) to read or update Active Directory data. To optimize the traffic and reduce the load on mission-critical DCs, you can configure the service to connect only to a particular domain controller (for example, you can choose to set up a dedicated DC for Collaboration Services to use).

For connection with a specific domain controller
1
Select the Use preferred domain controllers check box.
2
Select the domain, then click Load.
3
In the list of DCs loaded, select the check box next to the DC the service should use.
* 
NOTE: If the selected DC is down, Collaboration Services will not be able to access the Active Directory data. A corresponding event will be logged to the event log in this case.

Set up logging

Collaboration Services service logs its activity to its own log, ACSAlerts.log, which is located in the ACSLOGS subfolder of the service installation directory, and (optionally) to the Windows System log.

To write events to the System log
1
In the management console, right-click Collaboration Services and select Properties.
2
Click Logging | General, and select whether to write events to the System log.
3
Adjust the level of events to be logged.
* 
NOTE: By default, all events are logged. It is recommended not to lower this setting soon after installation of Collaboration Services because log files are extremely helpful for troubleshooting. You can reduce the logging level after you are confident that the synchronization between partners is established correctly.
To clear the ACSAlerts.log
•
Right-click Collaboration Services node in the tree, and use the corresponding shortcut menu command.

For Collaboration Services events details, see Appendix B: Collaboration Services events .

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级