Collaboration Services 3.9.1 - Deployment Guide

On the Choose File page, click Browse to specify the branch forest public key file name and location and provide the password for this file to the HQ administrator. Click Next.

In the warning message box that appears, click Yes if you want to proceed with exporting the public key file.

View the Summary details, and click Finish.

To register the branch forest

On the HQ forest computer where Collaboration Services is installed, click Start | Programs | Quest Software | Collaboration Services to open Collaboration Services web interface.

The Configure Branches Wizard starts automatically when you first open the web interface.

On the Welcome page, click Next.

On the Specify Branches step, you can perform the following actions:

Click Add to specify a public key file (.AKF) to add a new branch forest. Supply the authentication password and click OK.

To temporarily exclude a branch forest from collaboration, clear the Enable check box next to its name in the Registered branch forests list. All statistics and configuration information related to this branch will be preserved until the branch is enabled again. To re-enable the branch forest, select the Enable check box.

Specify whether the upgrade packets should be sent to each branch forest by selecting or deselecting the Send Upgrades check box.

Click Remove to remove the selected branch from the list.

Click Next.

In the warning message box that appears, click Yes if you want to apply your changes.

View the Summary details and click Finish.

Collaboration Services upgrade

Collaboration Services allows you to seamlessly upgrade from version 3.5, 3.6, 3.6.1, 3.7 and 3.8 to version 3.9.1. You must use the Collaboration Services Service Account to run the upgrade. Collaboration Services can either be manually or automatically upgraded. The default and recommended mode is Manual.


	NOTE: All inter-forest synchronization activities will be suspended until the upgrade completes for all branches. NOTE: The HQ forest will be updated last.

•

Manual updates are performed by the administrator of each Collaboration Services node. Once the manual update has been completed, the communication between nodes is re-established.

•

Automatic updates involve Collaboration Services sending packets to the nodes that contain the new software. This can take considerable time to complete depending on the update size, email traffic, and network quality. As each packet is sent using SMTP, a hand shaking protocol is used to ensure the update reaches each node correctly. If a packet is missing, then the packet is resent. This results in the automatic update not appearing to be done or taking longer than expected. The update is not performed until all of the update software is received in the node.


	NOTE: An automatic upgrade is not recommended. The upgrade process can take considerable time, as the upgrade package is sent to the Branch computers through email. Please allow up to 24 hours to pass when performing the upgrade before conducting any fault-finding. Interruption of the upgrade process may cause issues with Collaboration Services. NOTE: Automatic upgrades can be performed if required, once all nodes have been manually upgraded and communication between nodes is working correctly (with syncs being re-established). For example, on nodes that do not have an administrator to perform a manual update or sites that can be done over time without impacting Collaboration Service operations.