Collaboration Services 3.8 - 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 1: Notify branch forest administrators

Notify all branch forest administrators about the upcoming upgrade. To ensure a successful upgrade, have each Branch administrator:

Step 2: Distribute upgrades

Ensure that each Branch has the same build version Collaboration Services that the HQ is being upgraded to.

Step 3: Upgrade the HQ and branches

Have each site administrator run the setup of the new version of Collaboration Services. Once the setup completes, the Collaboration Service computer may need to be re-started to complete upgrade. Once the site comes back online it will try to communicate with the HQ. Once communication has been re-established, the upgrade is complete.

The manual upgrade should be done using the Microsoft Windows Installer Tool, msiexec.exe, as this will allow the upgrade process to produce a log which can be used for troubleshooting if the upgrade does not work correctly. In the location of the new version of Collaboration Service (by default the msi file is located in Collaboration Service folder), run the msiexec.exe with these options.

Preparing for an automatic upgrade

The Upgrade page of the Collaboration Services Properties dialog box allows each forest administrator to specify whether the Collaboration Services server should be restarted automatically after the upgrade is complete.

1
Select the Enable automatic upgrade check box.
2
To automatically restart the computer on completion of the upgrade, select the Send notification and restart computer after upgrade check box and specify a delay before the restart.
Documentos relacionados