지금 지원 담당자와 채팅

라이브 도움말 보기
등록 완료

로그인

가격 산정 요청

영업 담당자에게 문의

무료 트라이얼

Collaboration Services 3.10.1 - Deployment Guide

콘텐츠 탐색

About this document About Collaboration Services

Intended use in real-time environments Unified messaging environment for all users Transparency for end users Secure solution

Architecture and functionality

Collaboration Services structure Data synchronization

Collections

The synchronization process

Two way synchronization Publication and subscription Automatic synchronization of changes Synchronized groups

Communication among forests Security Mail forwarding Administrative interface

Before you begin

System requirements

Exchange server Collaboration Services server

Platform Memory Hard disk space Operating system Additional software

Service account rights and permissions SMTP connectivity Service mailbox

Platform considerations

Recipient Update Service Choosing between Free/Busy and Calendar synchronization Public folders Exchange 2007 only Exchange 2010 only Exchange 2013, 2016 and 2019

Pre-installation planning

Phase I: Planning

Step 1: Gather directory information

Objects to be synchronized Conflict resolution information

Step 2: Plan conflict resolution

Conflicting email addresses Other conflicts

Step 3: Plan Collaboration Services configuration

Choose the HQ forest

Phase II: Preparing forests

Step 1: Resolve conflicts Step 2: Restructure the OU hierarchy Step 3: Create service account Step 4: Dedicate a server Step 5: Verify Free/Busy accessibility

Phase III: Deploying Quest Collaboration Services

Step 1: Install Collaboration Services

HQ forest installation Branch forest installation Using the ACS Users and ACS Administrators groups Test local access

Step 2: Configure Collaboration Services

Set up conflict resolution rules Check namespace settings

Step 3: Publish test collections

Synchronization settings Object selection Monitoring Testing

Step 4: Publish all required users

Settings Object selection Monitoring

Prepare for use Collaboration Services upgrade

Preparing for a manual upgrade Performing the manual upgrade

Step 1: Notify branch forest administrators Step 2: Distribute upgrades Step 3: Upgrade the HQ and branches

Preparing for an automatic upgrade Performing the automatic upgrade

Step 1: Notify branch forest administrators Step 2: Distribute upgrades Step 3: Upgrade the HQ forest

Monitoring the upgrade

Installation checklists

Pre-Installation checklist Installation checklist Prepare for use checklist

Re-installing Collaboration Services Troubleshooting

Service account minimum rights and permissions

Step 1: Notify branch forest administrators

Step 1: Notify branch forest administrators

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

•

Ensure the Enable automatic upgrade check box is no selected (not selected by default).

•

Ensure the Send notification and restart computer after upgrade check box is not selected.

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

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.

1

Stop all QCS services.

2

Run command: msiexec /i "QCS.3.9.0.msi" /lv*! install.log ACSCOPYFILES="YES"


	NOTE: Inter-forest synchronization activities will be suspended until the upgrade completes.

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.


	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: All inter-forest synchronization activities will be suspended until the upgrade completes for all branches. NOTE: The HQ forest will be updated last.

To select the upgrade options

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.

3

Restart the computer to complete the upgrade.


	NOTE: The best practice is to allow Collaboration Services to restart the computer. This will ensure the upgrade is completed.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택