立即与支持人员聊天

获得即时帮助
完成注册

登录

请求定价

联系销售人员

Collaboration Services 3.9.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

Recipient Update Service

Platform considerations

In most cases, the Exchange Server's built-in Recipient Update Service should be used to stamp mail attributes such as the Legacy Exchange DN. After installation, this should be enabled in the RUS Options section of the Collaboration Services properties dialog box. If not selected, published objects will not appear in the Global Address List.

Choosing between Free/Busy and Calendar synchronization

Review the table below to determine what synchronization type best suits your environment.


	NOTE: Free/Busy synchronization is typically faster than Calendar synchronization, but it requires that Public Folder storage be available and some configuration work in the Exchange 2007/2010 environment. Free/Busy synchronization is not available or supported in Exchange 2013 and later versions.

Table 1. Synchronization type
	Outlook 2003	Outlook 2007	Outlook 2010	Outlook 2013	Outlook 2016	Outlook 2019	Outlook for Office 365
CALENDAR SYNCHRONIZATION
EXCHANGE 2007	[1]	Yes	Yes	NR	No	No	No
EXCHANGE 2010	[1]	Yes	Yes	Yes	Yes	No	No
EXCHANGE 2013	NR	NR	NR	Yes	Yes	NR	NR
EXCHANGE 2016	NR	NR	NR	Yes	Yes	Yes	Yes
EXCHANGE 2019	NR	NR	NR	Yes	Yes	Yes	Yes
FREE/BUSY SYNCHRONIZATION
EXCHANGE 2007	[1]	[1][3]	[1][3]	NR	No	No	No
EXCHANGE 2010	[1]	[1][3]	[1][3]	NR	No	No	No

[1] - Public folder store is mounted in the organization

[2] - UseLegacyFB registry key is set for each Mailbox

[3] - Configuration of the Availability Service to set the Address Space (https://support.quest.com/Search/SolutionDetail.aspx?id=SOL42144)

NR - Not Recommended

Public folders

Collaboration Services uses public folders to access free/busy information on the Exchange Server. Many organizations have these enabled, especially when there are legacy clients in use. However, on Exchange 2007/2010 a public folder database is not created by default. If you plan to synchronize free/busy data, and you have not already done so, you will need to perform the following steps in order to complete your Collaboration Services installation.


	NOTE: If you merge your organizations and are no longer using Collaboration Services, and you do not require public folders for any other purpose, you may remove them.

To enable public folders

1

Create the public folder database.

2

Run the following command at the Exchange console to enable publishing of free-busy data to the public folders: Add-AvailabilityAddressSpace -AccessMethod PublicFolder -ForestName <Source-Domain>

Exchange 2007 only

If you have not installed a trusted certificate on IIS, you must disable SSL encryption on the public folders virtual directory.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级

© ALL RIGHTS RESERVED. Feedback 使用条款隐私 Cookie Preference Center