The following permissions are required while deploying Collaboration Services for Exchange:
- Exchange View Only Administrator role:
If your Organization contains only Exchange 2003 server:
- Open Exchange System Manager
- Right click your Organization name and select Delegate Control
- Click Next
- Click Add
- Click Browse and enter the name of the service account
- Click OK
- Select Exchange View Only Administrator and click OK
- Click Next
- Click Finish
If your Organization contains Exchange 2007 or Exchange 2007 and 2010 servers:
- Add the service account to the Active Directory Exchange View-Only Administrators group
If your Organization contains only Exchange 2010 server View-Only rights are not sufficient. Organization Management rights are required:
- Add the service account to the Active Directory Organization Management group
- Local Administrator permissions on the computer where Collaboration Services is installed:
- Add the service account to the local Administrators group
- Full mailbox access permission for the service mailbox
- Full Control permission for Collaboration Services container:
- Open Active Directory Users and Computers (ADUC)
- Click View and check Advanced Features
- Right click the OU created for Collaboration Services and select Properties
- Select the Security tab
- Click Add
- Enter the name of the service account and click OK
- Select Full Control under Permissions and click OK
The deployment of Collaboration Services itself is very straightforward and does not require much knowledge of Active Directory and Exchange. In the test lab, where you can use Enterprise Admins group member accounts to deploy and start Collaboration Services, setting special permissions is not required. However, if you deploy Collaboration Services in the production environment, it makes sense to use accounts with minimal required privileges.
Below is outline of permissions required for the QCS service account (also referred to as general account in the product documentation):
- Read Access to Active Directory
- Replicate Directory Changes right for all domains in the forest from which objects will be published:
- Open ADUC
- Click View and check Advanced Features
- Right click the domain name and select Properties
- Select the Security tab
- Select the name of the service account or click Add to enter it
- Select Replicating Directory Changes under Permissions and click OK
- Manage Replication Topology right for all domains in the forest from which objects will be published:
- Open ADUC
- Click View and check Advanced Features
- Right click the domain name and select Properties
- Select the Security tab
- Select the name of the service account or click Add to enter it
- Select Manage Replication Topology under Permissions and click OK
- Write, create, and delete objects rights for the Collaboration Services container and child container:
- Open ADUC
- Click View and check Advanced Features
- Right click the Collaboration Services container and select Properties
- Select the Security tab
- Select the name of the service account or click Add to enter it
- Select Read, Write, Create all child objects and Delete all child objects under Permissions and click OK
- Note: These rights are granted if you give the service account Full Control to the Collaboration Services container and allow the permission to be inherited by the child objects
- Delete objects right for all containers with objects that are subject to conflict resolution via deletion:
- Open ADUC
- Click View and check Advanced Features
- Right click the container that contains objects subject to conflict resolution via deletion and select Properties
- Select the Security tab
- Select the name of the service account or click Add to enter it
- Select Delete all child objects under Permissions and click OK
- Repeat steps c - f for each container that contains objects subject to conflict resolution via deletion
- Write permission for all objects that are subject to matching:
- Open ADUC
- Click View and check Advanced Features
- Right click a container that contains objects subject to matching and select Properties
- Select the Security tab
- Select the name of the service account or click Add to enter it
- Select Write under Permissions and click OK
- Repeat steps c - f for each container that contains objects subject to matching
- Modify group membership right for all groups whose members can be affected by conflict resolution via deletion or matching:
- Open ADUC
- Click View and check Advanced Features
- Right click a container that contains groups whose members can be affected by conflict resolution via deletion or matching and select Delegate Control
- Click Add
- Enter the name of the service account and click OK
- Click Next
- Select Create, delete and manage groups
- Click Next
- Click Finish
- Modify permission for all stores in the Configuration container where Collaboration Services Calendar stub objects are stored (this requirement was added starting since QCS 3.0 when calendar data synchronization became possible):
Exchange 2003:
- Open ADSI Edit
- Expand Configuration | Services | Microsoft Exchange | Your Organization Name | Administrative Groups | The relevant Administrative Group | Server | The relevant Server name | InformationStores
- Click the relevant Storage Group Name
- In the right hand pane right click the name of a store and select Properties
- Select the Security tab
- Click Advanced
- Select the name of the service account or click Add to enter it
- Click Edit if the name was already in the list
- Select Modify Permissions and click OK
- Repeat for each store where Calendar stub objects are stored
Exchange 2007/2010/2013
- Open ADSI Edit
- Expand Configuration | Services | Microsoft Exchange | Your Organization Name | Administrative Groups | The relevant Administrative Group | Databases
- Right click the name of a Database and select Properties
- Select the Security tab
- Click Advanced
- Select the name of the service account or click Add to enter it
- Click Edit if the name was already in the list
- Select Modify Permissions and click OK
- Repeat for each Database where Calendar stub objects are stored