Quick Connect for Cloud Services 3.7 - Release Notes

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.

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 technical support for more information on this issue.

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.

Unexpected result when you use One Identity 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.

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.

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).

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.

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 Administrator Guide supplied with this release.

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.

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.

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.

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.

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 Administrator Guide supplied with this release.

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.

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.

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 One Identity Quick Connect for Cloud Services Administrator Guide supplied with this release.

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.

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 one of the following values:

- "Managers of the group"

- "Owner of the group"

- "All organization members"

- "Managers of the group" and "All organization members"

- "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.

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.

The mapping you created for Office 365 Contact objects may stop working after you upgrade Quick Connect for Cloud Services. 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.

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.

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.

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 Administrator Guide supplied with this release.

When you use the Automated Password Synchronization feature to synchronize a user's password from an Active Directory domain to Microsoft Office 365, the user’s passwords in these systems do not stay in sync because Microsoft Office 365 forces the user to change the password at next logon.

This issue occurs because of the default Microsoft Office 365 behavior.

WORKAROUND

Create a password sync rule to modify the user's ForceChangePassword attribute value to False in Microsoft Office 365.

For more information, see "Managing Password Sync Rules" in the Quick Connect Sync Engine Administrator Guide.

Your attempt to disable Lync Online for a Microsoft Office 365 user by setting the value of user's "Enabled for Lync Server" attribute to FALSE may fail with the error "Cannot perform the requested operation, because an Office 365 cmdlet has returned the following error: Cannot process command because of one or more missing mandatory parameters: Identity."

WORKAROUND

You cannot use the "Enabled for Lync Server" attribute to disable Lync Online for a Microsoft Office 365 user.

To disable Lync Online for a user, assign to that user a Microsoft Office 365 license plan that excludes Lync Online.

Processor

Memory

Hard disk space

Operating system

One Identity Quick Connect Sync Engine

Internet connection

Microsoft Office 365 Connector