How can I sync Groups as Groups (List Processing)?Created: 2012-04-20 08:09:59
Modified: 2019-07-19 11:20:48
Tags: DNHASHGEN Features Group as Group Sync UnitySync
UnitySync will sync the email address (Contact object) of a Source group by default. It can also, however, sync groups as Group objects.
(Default) Syncing Groups as Email Addresses (Mail Enabled Contact)
The default option for syncing your Source Groups/Lists is sync as email address. This means that only the email address of the list is synced to a Contact object, but no group membership information is retained on the Destination. Syncing Groups as Email Addresses is the most common way of handling Group sync, and its all that is needed the majority of the time.
(List Processing) Syncing Groups as Groups
Depending on your Destination directory type, you may also have the option of syncing Groups as Groups. This means a Group object will be created on the Destination and membership information will be synced. This is referred to as List Processing.
To configure your List Processing option, go to the Destination tab of your connection. The List Processing menu box at the bottom of the tab allows you to select from available options for your Destination directory type.
Further, depending on the Destination directory type, different types of groups may be created.
When syncing to an Active Directory (AD) Destination, you may sync to create any one of the following types of AD Groups:
- Global Distribution Group
- Global Security Group
- Global Distribution Group (Mail Enabled)*
- Global Security Group (Mail Enabled)*
Mail Enabled Groups are only valid if your Destination Active Directory has the Exchange 20xx schema loaded.
Important Notes regarding syncing Groups as Groups
Generally, the default Syncing Groups as Email Addresses meets the needs of most Group sync requirements. Before implementing Group as Group sync, please evaluate if it is really needed.
By default a connection that syncs Groups as Groups will only maintain members whose User/Contact record is also synced by that same connection. If a Group member is not synced, that member will be left out of the synced Group. This is because each connection can only resolve Membership DNs of the objects it syncs. This may leave your Membership list a little short if some of the member contacts were synced in via UnitySync and then added to Groups on the Destination server. If those Groups are synced back to the originating server, they will be missing those members because the contacts are excluded from the reverse sync.
There is an alternate connection configuration, utilizing multiple connections including a DNHASHGEN connection, that may be used to allow Memberships to be maintained in cases where Source members (Users or Contacts) are not actually synced in the same connection that the Groups are synced.
Manually created Source User or Contact objects (those not created by any UnitySync connection) that reside in containers that are EXCLUDED from the sync will always be dropped when syncing Groups as Groups. This is because UnitySync has no way of knowing if there is a valid contact for that member on the Destination or what its DN might be.
When a Group is initially synced, the member list may be incomplete. A subsequent sync will get the new Group objects membership list up-to-date.This occurs because the Groups member list can only contain objects that are included in this connections sync. Sometimes, during the sync process, the Group object will sync over before its member objects. When this happens, those members who have not yet synced will not be included in the Group. The next sync will bring the membership up-to-date.
The display name of Groups are synced over exactly as they appear on the source; the Reformat Display Name option on the Display Name tab does not apply to Groups. You have the option of specifying a label to be appended to the Display Name of your Group object. This label may be specified in the Display Name tab, in the Display Name Label sections Group parameter.