Quest® Collaboration Services
Version 3.1
Release Notes
November 20, 2009
Welcome to Quest Collaboration Services
Resolved Issues and Enhancements
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 (partners, consultants, vendors, etc.). Quest Collaboration Services allows for granular and selective data synchronization, including global address list (GAL), free/busy information and calendar details information.
The following is a list of issues addressed and enhancements implemented in this release of Quest Collaboration Services.
|
Feature |
Resolved Issue |
Change Request |
| General | When deleting published collections from the publisher side, the following error may be displayed: Failed to send collection packet.Unknown collection ID. |
ST#63229 |
| When deleting members from the inactive collection, Collaboration Services fails to send Free/Busy data for all collections with the following error displayed: Failed to collect Free/Busy: Code : 0x 490,Description : Element not found. | ST#63107 | Synchronization | If any of published Calendar collections is disabled, other collections will be considered disabled as well, so synchronization process fails. | ST#63226 |
| Active Directory Synchronization process may use 100% CPU resources. | ST#62569 | |
| Processing of the recurrence messages is improved. | ST#63224 | |
| If source objects have SMTP addresses with the same namespaces specified, then Primary SMTP will be specified in the Target Address property of the created stub objects. | N/A | |
| During Calendar collections synchronization some calendar appointments might be missed in stub objects. | ST#63227 |
The following is a list of issues known to exist at the time of Quest Collaboration Services release.
|
Feature |
Known Issue |
Change Request |
|
Installation and Upgrade
|
When the upgrade package is deployed automatically to the branch forest (silent upgrade), the following error message is displayed: ”Following feature(s) require valid license: - Quest Collaboration Services – Collaboration Services 3.x License”. Click OK to ignore the message and proceed with the upgrade automatically. | CR49755 |
| As Quest Collaboration Services web management console is installed automatically to qcs folder on the default IIS site, a conflict may occur if another application (e.g., a SharePoint site) had been already installed to that location (default port 80). This prevents users from accessing the web management console. To avoid the problem, when you are prompted for Collaboration Services web console installation pack download, make sure that no sites were installed to the port 80 on the default IIS site. | CR49877 | |
| You need to manually uninstall the previous version of the Collaboration Services remote web interface before or after an upgrade using Add/Remove Programs. Once that is completed, the new version of the web interface package will be downloaded automatically when you first connect to Collaboration Services server remotely. | CR52101 | |
| When upgrading the license to one for a different amount of synchronized objects, it is required to perform a re-publication of all published collections. | CR52100 | |
| Synchronization | If you want to use "Group to Contact" mapper for a source group from Exchange 2007 organization, open that distribution group’s properties in the Exchange 2007 Management Console, go to the Mail Flow Settings tab, select Mail Delivery Restrictions Properties, and in the dialog displayed, clear the Require that all senders are authenticated check box. (Otherwise, message delivery to the target contact will fail). | CR50674 |
| Indexing service, antivirus on-access scanners, and any other software which interacts directly with the file system may lock Collaboration Services databases and cause synchronization failures. You must exclude the Storage subfolder in the Collaboration Services installation folder from the scope of such tools. | CR52047 | |
| When free/busy information is published to public folders, current month is determined in GMT. This behavior is only applicable to Calendar synchronization. | CR52296 | |
| Collection statistics may show incorrect information. This does not mean there are any errors in the synchronization. Please refer to Collaboration Services events for tracking synchronization issues. | CR52099 | |
| General | The user interface may appear to hang for significant time when retrieving large quantities of data when the Collaboration Services server CPU usage is high. This happens because the user interface has the lowest priority and always yields to all other Collaboration Services processes. | CR52098 |
| QCS Namespaces list may contain duplicate namespaces after installation. You can remove duplicate values manually. | CR52102 |
Seamless, automatic upgrade is supported for Collaboration Services 2.x. Please refer to Quest Collaboration Services 3.1 - Installation Guide for the upgrade procedure.
Before installing Quest Collaboration Services, ensure your system meets the following minimum hardware and software requirements:
| Platform |
Intel x86-based computer Pentium III or higher Multi-processor configurations are recommended for the HQ forest server in large deployments. Note: Using faster processors and multi-processor configurations generally improves synchronization performance. |
| Memory |
Depends on the total number of synchronized objects. Less than 100K – 256 MB RAM 100K to 300K – 512 MB RAM More than 300K – 1 GB RAM |
| Hard Disk Space |
5 GB of free disk space minimum Additional disk space: 1MB per every 1K of synchronized AD objects 1MB per every 1K of synchronized Free/Busy objects or Calendar objects Note: It is highly recommended to install Quest Collaboration Services on an NTFS volume. |
| Operating System |
Microsoft Windows 2000 Server (SP4 or later) Microsoft Windows Server 2003 (SP2 or later) |
| Additional Software | Microsoft Internet Explorer 5.0 or later
MAPI Client: Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 Microsoft Windows Installer 2.0 or later Microsoft Internet Information Server (IIS) 5.0 or later Note: IIS is required only if you want to enable remote access to the Collaboration services. If you plan to connect to the Collaboration Services interface only locally (or remotely using Terminal Services), IIS is not required. |
| Exchange Server |
Microsoft Exchange Server 2000 (SP3 or later) Microsoft Exchange Server 2003 (SP2 or later) Microsoft Exchange Server 2007 (SP1 or later) Note: Exchange 2000/2003/2007 organizations in mixed mode (with legacy Exchange 5.5 servers) are supported. |
The remote computer from which you are connecting to the Collaboration Services by means of the web interface should have the following software installed:
| Operating System |
Microsoft Windows NT4 (SP6a or later) Microsoft Windows 2000 Professional Microsoft Windows 2000 Server Microsoft Windows XP Professional Microsoft Windows Server 2003 |
| Additional Software | Microsoft Internet Explorer 5.01 or later |
The accounts used when installing and using Collaboration Services must have the following permissions:
| Account | Used To | Required Permissions | Notes |
| Setup account | Run the Collaboration Services setup and deploy the service |
Exchange View Only Administrator role Local Administrator permissions on the computer where Collaboration Services is installed. Full Control permission for Collaboration Services container |
Be sure to log on to the server with this account before launching setup. When installing the service you will be offered to use the setup account as a service account. You can change it to another account if you need to. |
| Service account | Start the synchronization service on the Collaboration Services server | Local Administrator privileges on the computer where Collaboration Services instance is installed | After Collaboration Services is installed, the service account will be used as a general account. You can change it to another account any time later. |
| General account | Read and update AD data |
Read access to Active Directory Replicate Directory Changes right for all domains in the forest from which objects will be published Manage Replication Topology right for all domains in the forest from which objects will be published Write, create, and delete objects rights for the Collaboration Services container and child containers Delete objects right for all containers with objects that are subject to conflict resolution via deletion Write permission for all objects that are subject to matching Modify group membership right for all groups whose members can be affected by conflict resolution via deletion or matching Modify permissions for all stores in the Configuration container where Collaboration Services' Calendar stub objects are stored |
As long as objects that are subject to conflict resolution via deletion or matching can be scattered all over the forest, be sure to give this account sufficient privileges so it can update/delete objects located in different domains and containers and change membership of different groups throughout the forest. |
This section contains information about installing and operating this product
in non-English configurations, such as those needed by customers outside of
North America. This section does not replace the materials about supported
platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release,
all product components should be configured to use the same or compatible
character encodings and should be installed to use the same locale and regional
options. This release is targeted to support operations in the following
regions: North America, Central and Eastern Europe, Japan.
The Quest Collaboration Services release package contains the following products:
How to install the product from this CD:
Before you start the installation, it is recommended that you close all the previously open applications.
Note: Collaboration Services setup requires Windows Installer 2.0 to be installed. Earlier versions of Windows Installer are automatically upgraded during installation, so you may have to reboot your computer after the installation is finished.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web | http://www.quest.com |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.
This guide is available in English only.
© [2009] Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
| legal@quest.com | |
| Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 |
|
| Web | http://www.quest.com |
Refer to our Web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Aelita, Akonix, Akonix L7 Enterprise, Akonix L7 Enforcer, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vANALYZER, vAUTOMATOR, vCONTROL, vCONVERTER, vEssentials, vFOGLIGHT, vOPTIMIZER, vRANTER PRO, vReplicator, Vintela, Virtual DBA, VizionCore, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.