Chat now with support
Chat with Support

Quick Connect for Cloud Services 3.3 - Release Notes

Release Notes

Quest One Quick Connect for Cloud Services

Version 3.3.0

Release Notes

December 4, 2012

 


Contents

Welcome to Quest One Quick Connect for Cloud Services

New in This Release

Resolved Issues and Enhancements

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information

 


Welcome to Quest One Quick Connect for Cloud Services

Quest One Quick Connect for Cloud Services is an option of Quick Connect Sync Engine that provides connectors allowing you to connect Quick Connect Sync Engine to the following data systems:

  • Google Apps
  • Google Postini Services
  • Microsoft Office 365
  • Salesforce

After installing Quick Connect for Cloud Services, you can connect Quick Connect Sync Engine to the above-listed data systems and start synchronizing identity information between them and/or any other data systems managed by Quick Connect Sync Engine. Quick Connect for Cloud Services also simplifies password management tasks by automatically synchronizing user passwords from an Active Directory domain to the data systems supported by Quick Connect for Cloud Services.

For detailed information on what data you can read and write in each of the data systems supported by Quick Connect for Cloud Services, see the Quick Start Guide supplied with this release.

 


New in This Release

  • Extended Support for Groups in Office 365. The Office 365 Connector now supports security groups, distribution groups, and dynamic distribution groups in Office 365. To work with these types of groups, you can use new objects in the connector schema named SecurityGroup, DistributionGroup, and DynamicDistributionGroup appropriately. For more information on what data you can read and write in Office 365 by using these objects, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.
  • Support for Mailboxes in Office 365. The Office 365 Connector now supports mailboxes in Office 365. To read and write the properties of mailboxes hosted in Office 365, you can use the Mailbox object provided in the connector schema. For more information on what data you can read and write in Office 365 by using the Mailbox object, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.
  • Support for Mail Users in Office 365. The Office 365 Connector now supports mail users in Office 365. To read and write the properties of Office 365 mail users, you can use the MailUser object provided in the connector schema. For more information on what data you can read and write in Office 365 by using this object, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.
  • Support for More Properties of Users and Contacts in Office 365. The Office 365 Connector now can work with more properties of users and contacts in Office 365.
    To work with users in Office 365, you can use the User object in the Office 365 Connector schema. The User object now provides 50+ attributes that allow you to read and write the properties of  users in Office 365.
    To work with contacts in Office 365, you can use the Contact object in the Office 365 Connector schema. The Contact object now provides 80+ attributes for reading and writing the properties of contacts in Office 365.
    For more information on what data you can read and write in Office 365 by using the User and Contact objects, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.

 


Resolved Issues and Enhancements

The following is a list of issues resolved and enhancements implemented in this release, as compared to Quick Connect for Cloud Services version 3.2.0.

TF00183776
Fixed: A provisioning step that is configured to provision objects to Microsoft Office 365 and specify their membership may fail with the following error: "The requested operation is not defined for the 'Member' attribute of the 'Group' class."

TF00184095
Fixed: After you change the Microsoft Online Services ID and/or the related password in the properties of an existing Microsoft Office 365 connection, you may encounter the following error in the Quick Connect Administration Console when running a workflow using that connection: "Unable to connect to Office 365 service. Please check credentials."
When you use the "Test Connection" button to verify the connection settings, the test operation completes successfully and does not reveal any problems with the connection.

TF00185091
Fixed: An updating step configured to update the initials of an external contact in Microsoft Office 365 may fail to update the initials, returning the following error message: "A positional parameter cannot be found that accepts argument 'Initials'." As a result, the initials of the external contact are not updated.

TF00185094
Fixed: An updating step configured to update the first and last name of an external contact in Office 365 may not make any changes to the first and last name of the contact. This issue occurs when you attempt to update the first and last name by using the FirstName and LastName attributes provided by the Microsoft Office 365 Connector.
 


Known Issues

The following is a list of issues known to exist at the time of this Quick Connect for Cloud Services release.

TF00134124
Unexpected result of a synchronization operation performed on a group in Google Apps: The account that is the group owner may lose its ownership and become a member of that group. This problem occurs when your synchronization workflow first synchronizes the Owners attribute, and then synchronizes the Members attribute.
WORKAROUND
Reconfigure your synchronization workflow so that it synchronizes the Members attribute prior to synchronizing the Owners attribute.

TF00143733
You may encounter the following problem when running a workflow that provisions a user object to Google Postini Services: If you have specified two or more rules to generate a name for the user object being provisioned, only the first rule from the list is used and the other rules are ignored.
WORKAROUND
Contact Quest Support for more information on this issue.

TF00171533
Unexpected behavior when you are using the Quick Connect Administration Console to view information about the members of a Google Apps group: the Administration Console may not show suspended Google Apps users as members of the group, although these users actually are the group members.
WORKAROUND
This behavior is by design. To view a complete list of group members (including suspended users), use the Google Apps user interface.

TF00171758
Unexpected result when you use Quick Connect to rename or move an organization unit (OU) in Google Apps: Mapped child OUs in the renamed or moved OU may be unexpectedly unmapped from their counterparts in other connected systems.
WORKAROUND
Manually remap the child OUs in the renamed or moved OU.

TF00184222
Unexpected behavior: A synchronization step configured to update the description of a distribution group in Microsoft Office 365 may not make any changes to the group description. Instead, the step unexpectedly writes the specified group description value to the MailTip option in Office 365.
This issue occurs when you try to update the group description by using the Notes attribute provided by the Microsoft Office 365 Connector for the DistributionGroup object.
WORKAROUND
Manually update the group description in Office 365.

TF00226518
You may encounter any of the following issues when using attributes provided by the Office 365 Connector for DynamicDistributionGroup object:
ISSUE 1
Unexpected behavior when you use the ManagedBy attribute to read data in Office 365: The ManagedBy attribute always returns canonical name, although Office 365 stores the value in a different format. This issue only occurs when you use the ManagedBy attribute as a string attribute.
ISSUE 2
Unexpected behavior when you use the RecipientFilter attribute to write data to Office 365: The value written to Office 365 may be different from the one you specified in the RecipientFilter attribute.
WORKAROUND FOR ISSUE 1
To avoid this behavior, use the ManagedBy attribute as a reference attribute.
WORKAROUND FOR ISSUE 2
Use other attributes to specify recipients (for example, you can use the IncludeRecipients attribute).

TF00226734
Unexpected behavior when you use a rule in an update synchronization step to generate an empty value for the attribute Members of a security group in Office 365: The step does not clean up the value of the Members attribute.
WORKAROUND
Configure an attribute to attribute updating rule in order to write the empty value from the source attribute to the target attribute.

TF00233551
Your attempt to create or update a Mailbox object in Office 365 by using the SecondaryDialPlan,
LitigationHoldEnabled, RetentionComment, and/or LitigationHoldDate attributes may fail with the following error message: "A positional parameter cannot be found that accepts argument <AttributeName>."
This issue shows up when your Office 365 environment does not have the fields to which these attributes correspond (for example, when your license plan does not provide for such fields).
WORKAROUND
Exclude these attributes from the synchronization step.
For more information about the SecondaryDialPlan, LitigationHoldEnabled, RetentionComment, and LitigationHoldDate attributes of a Mailbox object, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.

TF00235832
Your attempt to change the IsRegular attribute value to TRUE for a Mailbox object in Microsoft Office 365 may result in the following error message: "Error code <Number> occurred with message The user and the mailbox are in different Active Directory sites."
WORKAROUND
Disregard the error message: in the described situation, the new value of the IsRegular attribute is successfully written to Microsoft Office 365.

TF00235928
Unexpected result when you use the MailTip attribute of the MailUser object to write data to Office 365: The value written to Office 365 may include HTML tags (such as <html> or <body>), although the value you specified in the MailTip attribute does not include any HTML tags.
WORKAROUND
Do not use the MailTip attribute to write data to Office 365.

TF00235939
You may encounter the following error when writing values to Office 365:
"A positional parameter cannot be found that accepts argument '<AttributeName>."
This issue shows up when you attempt to write data by using attributes provided for the following object types: Contact, Mailbox, MailUser, DistributionGroup, DynamicDistributionGroup.
In fact, this error message may indicate that your current Office 365 license plan does not allow you to update the field values you want.
WORKAROUND
Make sure your license plan in Office 365 allows you to update the fields you want.

TF00236554
Unexpected result when you use the MailTipTranslations attribute of the MailUser object to write data to Office 365: The value written to Office 365 may include HTML tags (such as <html> or <body>), whereas the value you specified in the MailTipTranslations attribute does not include any HTML tags.
WORKAROUND
Do not use the MailTipTranslations attribute to write data to Office 365.

TF00236770
Your attempt to create or update a Contact object in Office 365 by using the SecondaryDialPlan, LitigationHoldEnabled, RetentionComment, and/or LitigationHoldDate attributes may fail with the following error message: "A positional parameter cannot be found that accepts argument <AttributeName>."
This issue shows up when your Office 365 environment does not have the fields to which these attributes correspond (for example, when your license plan does not provide for such fields).
WORKAROUND
Exclude these attributes from the synchronization step.
For more information about the SecondaryDialPlan, LitigationHoldEnabled, RetentionComment, and LitigationHoldDate attributes of a Contact object, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.

TF00236783
Unexpected behavior when you use the Manager attribute of a Contact object to read data in Office 365: The Manager attribute always returns canonical name, although Office 365 stores the value in a different format.
This issue only occurs when you use the Manager attribute as a string attribute.
WORKAROUND
To avoid this behavior, use the Manager attribute as a reference attribute.

TF00237712
When a synchronization step generates an invalid value for an attribute, you may encounter the following misleading error message that fails to correctly describe the issue: "Unable to complete this action. Try again later."
WORKAROUND
Make sure the synchronization step generates valid values for all attributes.

TF00237905
Your attempt to create or update a User object in Office 365 by using the AllowUMCallsFromNonUsers attribute may fail with the following error message: "A positional parameter cannot be found that accepts argument <AttributeName>."
This issue may show up when your Office 365 environment does not have the field to which the AllowUMCallsFromNonUsers attribute corresponds (for example, when your license plan does not provide for such a field).
WORKAROUND
Ensure that your Office 365 environment includes the field to which the AllowUMCallsFromNonUsers attribute corresponds. If no such field exists, exclude the AllowUMCallsFromNonUsers attribute from the synchronization step.
For more information about the AllowUMCallsFromNonUsers attribute of a User object, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.

TF00238904
Unexpected behavior when you use a rule in an update synchronization step to generate an empty value for the attribute Members of a distribution group in Office 365: The step does not clean up the value of the Members attribute.
WORKAROUND
Configure an attribute to attribute updating rule in order to write the empty value from the source attribute to the target attribute.

TF00240316
When you use the EmailPermission attribute to perform a Read operation on a Group object in Google Apps, the attribute may unexpectedly return "Not Set" or an empty value in a situation where some email permissions are actually set on the Group object.
This issue may occur in the next scenarios.
SCENARIO 1
In most cases, this issue affects the Google Apps groups for which the Post option on the "Posting permissions" tab is set to the following values:
- "Managers of the group"
OR
- "Owner of the group"
OR
- "All organization members"
OR
- "Managers of the group" and "All organization members"
OR
- "Owner of the group" and "All organization members"
SCENARIO 2
In some cases, this issue affects groups regardless of the values set for them in the Post option on the "Posting permissions" tab.
WORKAROUND FOR SCENARIO 1
1. In Google Apps, open the "Posting permissions" tab for the group, and then in the Post option select one or more other values in addition to the already selected values.
2. Retry the read operation on the group.
WORKAROUND FOR SCENARIO 2
1. Recreate the affected group in Google Apps.
2. Retry the read operation on the group.

TF00240517
Your attempt to create (provision) a user object on Google Apps may fail with the following error message: "Entity doesn't exist". This issue only occurs when you attempt to create a user object that has been recently deleted from Google Apps.
WORKAROUND

Wait for 10-15 minutes, and then retry the create (provision) operation.

TF00243179
The mapping you created for Office 365 Contact objects may stop working after you upgrade to Quick Connect for Cloud Services 3.3. This happens because the ObjectId attribute provided by the Microsoft Office 365 Connector for Contact objects now uses object GUID rather than the ExternalDirectoryObjectId attribute value to uniquely identify objects in Office 365.
WORKAROUND
1. Create new mapping rules for the Office 365 Contact objects.
2. Run the map operation on these Office 365 Contact objects.

TF00243524
Your attempt to update an Office 365 mail user by using the attributes ModeratedBy and ModerationEnabled may fail with the error "You need to add at least one moderator when message approval is turned on. Property Name: ModeratedBy"
This issue only occurs when you use these two attributes in one synchronization step.
WORKAROUND
Use a separate synchronization step to set a value for each of these attributes.

TF00243700
Your attempt to update a distribution group in Office 365 by using the ManagedBy attribute may fail with the error "Cannot perform the requested operation, because an Office 365 cmdlet has returned the following error: You don't have sufficient permissions. This operation can only be performed by a manager of the group."
This issue only occurs when all of the following is true:
- The distribution group you attempt to update has no owners (managers).
- You use the ManagedBy attribute as a reference attribute.
WORKAROUND
Use the ManagedBy attribute as a string attribute to add at least one owner (manager) for the distribution group. After you do so, you can use the ManagedBy attribute as a reference attribute to add other owners (managers) for the group.

TF00243717
Your attempt to update a dynamic distribution group in Office 365 by setting the IncludedRecipient attribute value to None may fail with the following error message: "Error: Cannot perform the requested operation, because an Office 365 cmdlet has returned the following error: The object must not have empty recipient filter, "". Property Name: RecipientFilter".
WORKAROUND
Do not set the value of the IncludedRecipient attribute to None.
To set the group scope you want, use the RecipientFilter attribute provided for the DynamicDistributionGroup object. For more information about this attribute, see the Quick Connect for Cloud Services Quick Start Guide supplied with this release.
 


Upgrade and Compatibility

You can upgrade to Quick Connect for Cloud Services version 3.3.0 from Quick Connect for Cloud Services version 3.2.0 or later.

To upgrade, install Quick Connect for Cloud Services 3.3.0 on the computer where an earlier version of the product is installed. During upgrading, setup transfers the product configuration to the new installation of Quick Connect for Cloud Services.

 


System Requirements

This section provides system requirements for installing and using Quick Connect for Cloud Services.

Processor 1 GHz or faster, x86 and x64 architecture is supported.
Memory 512 MB of RAM; 1 GB or more recommended.
Hard Disk Space 250 MB or more of free disk space. The amount of required hard disk space depends on the number of objects being synchronized.
Operating System Your computer must run one of the following operating systems (32- or 64-bit edition):
- Microsoft Windows Server 2012 without any Service Pack
- Microsoft Windows Server 2008 R2, Standard or Enterprise
- Microsoft Windows Server 2008, Standard or Enterprise, with or without any Service Pack
- Microsoft Windows Server 2003 R2, with or without any Service Pack
- Microsoft Windows Server 2003, with or without any Service Pack
Quick Connect Sync Engine Quick Connect Sync Engine version 5.1 or 5.2
Internet Connection Internet access to the data system you want to participate in the data synchronization operation (that is, Google Apps, Google Postini Services, Microsoft Office 365, and/or Salesforce).
Microsoft Office 365 Connector The following software must be installed on the Quick Connect for Cloud Services computer in order you could create a connection to Microsoft Office 365:
- Microsoft Online Services Sign-in Assistant version 7.0
- Microsoft Online Services Module for Windows PowerShell version 1.0

Note: The Microsoft Office 365 Connector uses some Windows PowerShell scripts. In order these scripts could work, you need to set the Windows PowerShell execution policy on the computer on which the connector is installed to RemoteSigned.

 


Global Operations

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. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

 


Getting Started

In this section:

Contents of the Release Package

Installation Instructions

 

Contents of the Release Package

The release package contains the following items:

  1. Quest One Quick Connect for Cloud Services version 3.3.0 (x86 and x64 installation files)
  2. Quest One Quick Connect for Cloud Services Release Notes (this document)
     

Installation Instructions

Before installing Quick Connect for Cloud Services, make sure that the System Requirements are met.

For installation instructions, see the Quick Start Guide supplied with this release.

 


For More Information

Contacting Quest Software:

Email info@quest.com
Mail 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.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at www.quest.com/support.

From our Support Portal, you can do the following:

  • Retrieve thousands of solutions from our Knowledgebase
  • Download the latest releases and service packs
  • Create, update and review Support cases

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures.
The guide is available at www.quest.com/support.

 


© 2012 Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This document contains proprietary information protected by copyright. The software described in this document 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.

 

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.

 

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
email: legal@quest.com

Refer to our Web Site www.quest.com for regional and international office information.

 

Trademarks

Quest, Quest Software, the Quest Software logo are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software's trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.

 

Third Party Contributions

This product contains some third party components (listed below). Copies of their licenses may be found at http://www.quest.com/legal/third-party-licenses.aspx. Source code for components marked with an asterisk (*) is available at http://rc.quest.com.

  • .NET Logging Library 2.0: BSD-style license
  • Google Data API SDK (2.1.0.0) Setup 2.1.0.0: Apache 2.0

 

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