Chat now with support
Chat mit 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:

1
Install Collaboration Service
2
Initial configuration
3
Publication of test collections
4
Publication of all Users objects

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.

To install Collaboration Services
1
Download and install Outlook, or the latest version of Microsoft Exchange Server MAPI Client and Collaboration Data Objects.
2
Install the Collaboration Services instance in the HQ forest. During the setup, the HQ public key file will be generated.
* 
NOTE: For Windows Server 2012 and later versions, if you are not logged in as "Administrator", run the Collaboration Services setup file with the option "Run as administrator".
3
Securely transfer the HQ public key file to the branch forest administrators. Installation of branch forests is not possible without the HQ public key file.
4
Install Collaboration Services in each of the branch forests.
5
Log on to each branch forest’s administrative interface and export its branch public key file.
6
Securely transfer the public key files for all branches to the HQ forest administrator.
7
Log on to the HQ forest administrative interface and register all branches in the collaboration structure.
* 
TIP: Do not install both Outlook and MAPI CDO on the same machine that Collaboration Services is installed. Install either Outlook or MAPI CDO.
* 
TIP: Exclude the installation folder %Program Files%\Quest Software\Collaboration Services and all sub folders from the virus scan software.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen