Chatta subito con l'assistenza
Chat con il supporto

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

Recipient Update Service

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.

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.

Exchange 2007 only

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

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione