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

Step 4: Dedicate a server

Collaboration Services can be installed on any computer in a forest. For performance reasons, it is highly recommended to install it on a dedicated server not holding any other roles such as file server, print server, Exchange server, or domain controller.

Ensure the server meets hardware and software requirements listed in the System requirements .

Step 5: Verify Free/Busy accessibility

Synchronized free/busy information is stored on the Exchange server keeping the free/busy public folder for the administrative group that contains Exchange server where the service mailbox resides.

If your Exchange deployment contains multiple administrative groups, free/busy information access between various groups must be obtained using either public folder referrals or free/busy folder replication. In fully functional production environments, one of these methods is usually already implemented and no further action is needed. Nevertheless, many customers have problems with access to free/busy information, so you should ensure that users from each domain are able to access the free/busy information located on the server that Collaboration Services will use.

Please see the appropriate Microsoft Exchange server documentation for more information on configuring free/busy information access between administrative groups.

Phase III: Deploying Quest Collaboration Services

This section provides a sample scenario for installing and testing Collaboration Services, including the recommendations for the following procedures:

Step 1: Install Collaboration Services

Install Collaboration Services on dedicated servers in each forest at least a week before the planned synchronization start date. This will give you time to exchange the public key files, troubleshoot any installation problems, configure Collaboration Services instances, and synchronize a test collection of users between forests.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating