How to exclude user objects which are not mailbox-enabled but have the mail attribute populated from the Coexistence Manager for GroupWise (CMG) Directory Sync?
In certain scenarios, user objects have a value populated into the mail attribute field but are not mailbox-enabled and it is not desired to have them within the synchronisation scope of the CMG directory connector.
By default, all objects from the selected organizational unit (OU) which have a value within the mail attribute are synchronized from AD to GroupWise.
The following steps need to be performed in order to change the source definition files so that the attribute msExchMailboxGuid is extracted from the AD objects upon directory connector runtime.
As next step, a modification to the exclusion list needs to be done as all objects that do not have the msExchMailboxGuid attribute populated (hence are not mailbox-enabled) should be excluded.
Now the connector can be run and all objects without a value populated into the msExchMailboxGuid attribute will be excluded from the synchronization.
The logfile (located in ‘…\Quest Software\Quest Coexistence Manager for GroupWise\Directory Connector\log4net’) should include entries like this for all objects that are not mailbox-enabled:
Discovered DN | CN=Firstname Lastname,OU=OrgUnit,DC=domain,DC=tld
Excluded | Rule: msexchmailboxguid=NULL
Please note that the exclude.txt file will be overwritten again when the connector settings are changed through the console and the connector is run. A prompt will pop up asking to save the configuration which triggers the overwriting. Please have a copy of the modified file available so that you can replace it after changing the connector config through the console.