Chat now with support
Chat with Support

Collaboration Services 3.9.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

Service account rights and permissions

The account used as the service account should be used to install and configure for Collaboration Services. Ensure that the account has the following rights:

•
Member of the Built-In Administrator group in all domains where Collaboration Services is installed
•
Exchange Full Admin rights
•
Member of the Local Administrators group on the computer where Collaboration Services is to be installed
* 
NOTE: The full administrative rights for Exchange are different for each version. Refer to the Quest Support site (https://support.quest.com/collaboration-services/kb/4253978/what-permissions-are-necessary-for-deploying-collaboration-services) for the latest information on the required rights.

SMTP connectivity

Collaboration Services instances communicate with each other using SMTP. It is recommended to establish SMTP connectors between the HQ and branch forests to optimize mail flow between synchronization partners. Please see the Microsoft Exchange Server documentation for details.

If you use DNS to route mail, DNS servers in all forests must have Mail Exchanger (MX) records to correctly route mail between collaboration partners. For more information, please refer to the appropriate DNS documentation.

* 
TIP: You can also set up the mail flow using the Exchange smart host feature. This is useful if you install Collaboration Services in a test environment and do not want to set up and configure a DNS server. For more information, please refer to the appropriate Microsoft Exchange Server documentation.

Service mailbox

The Collaboration Services service requires a service mailbox, which will be used to exchange synchronization data with other synchronization partners. A service mailbox should be created in each forest participating in the collaboration.

* 
TIP: Check the mail flow between all forests before deploying Collaboration Services by sending test e-mails between the HQ and branch service mailboxes in both directions. By doing this test, you can be sure all forests will be able to communicate with each other using the specified mailboxes. The test can be easily performed using, for example, Outlook Web Access (OWA).
* 
NOTE: Ensure anti-spam filters are configured appropriately in all forests. In the HQ forest, be sure to add all branches’ service mailboxes addresses to the safe senders list. In each branch forest, add the HQ forest service mailbox address to the safe senders list.

 

Platform considerations

Recipient Update Service

In most cases, the Exchange Server's built-in Recipient Update Service should be used to stamp mail attributes such as the Legacy Exchange DN. After installation, this should be enabled in the RUS Options section of the Collaboration Services properties dialog box. If not selected, published objects will not appear in the Global Address List.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating