Chat now with support
Chat with Support

Collaboration Services 3.9 - Release Notes

Quest® Collaboration Services 3.9

Quest® Collaboration Services 3.9
These release notes provide information about the Quest® Collaboration Services release.
Topics:
•
About this release
•
New features
•
Resolved issues
•
Known issues
•
System requirements
•
Product licensing
•
Installation instructions
•
More resources
•
Globalization
•
About us

About this release

Quest Collaboration Services allows companies to establish secure collaboration between users in different forests; being used on a continuous basis, it allows you to reduce the costs and complexities associated with managing a decentralized, multi-forest network. Quest Collaboration Services provides a consolidated view of all collaboration processes and gives easy access to object management functionality. It assists corporate IT administrators in synchronizing data between separated forests, while taking into account organizational and business demands.

Quest Collaboration Services can be deployed in a single company (for example, between divisions and subsidiaries) as well as between separate companies (such as partners, consultants, and vendors). Quest Collaboration Services allows for granular and selective data synchronization, including global address list (GAL), free/busy information and calendar details information.

Collaboration Services 3.9 is a minor release, with new features and functionality. See New features.

New features

New features in Collaboration Services 3.9:
•
Added support for synchronizing SIP address in the Active Directory attribute proxyAddresses.
•
Added support for MAPI over HTTP: Outlook 2016 or later versions is required.
•
New platforms supported:
•
Windows Server 2019
•
Exchange 2019
•
New Outlook clients supported:
•
Outlook for Office 365
•
Outlook 2019
•
Outlook 2016

Resolved issues

The following is a list of issues addressed in this release.
 
Table 1. General resolved issues
Resolved issue
Issue ID

The service mailbox test does not work when a user’s displayName and sAMAccountName are not the same.

176438

The sync service might crash.

168901

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating