After you verify that the test collection is synchronizing properly for several days, you can start synchronization for all users. You can either create new collections, or edit the test collection settings to include all users.
NOTE: If you have multiple large collections, it is recommended to publish them one by one to improve overall synchronization speed. That is, publish the first collection and wait until the initial synchronization is over for all subscribing forests, and then publish the next collection. This can be achieved by first creating all collections in a disabled state and then enabling them one by one as necessary.
You may want to fine-tune the interaction between Active Directory, Exchange, and Collaboration Services instances using the synchronization settings. The default settings are good for most environments; however, you may want to optimize them for your own environment. For example, if your Active Directory data is updated rarely, you can increase the Query AD for changes value. Or you may want to restrict Active Directory and Exchange server access during the busiest production hours by using scheduling.
When creating a collection, either proceed with the All attribute preset (it is selected by default), or individually select the attributes to be published for each object class, depending on your requirements.
When publishing all users to be synchronized, it is not recommended to specify any user accounts explicitly or through group membership for performance reasons. Collaboration Services provides dynamic object selection so you can use the OU structure and LDAP filters to select the objects to be published.
By default, group members are not synchronized when you publish a group. You can change the group’s settings to make the group members be synchronized; however, this is not recommended for large groups due to performance reasons. If you want to publish large groups, publish them separately from their members. For large deployments, it is also recommended to place users and groups in separate collections and synchronize these collections in the following order: first the user collection, and then the group collection.
Verify that the stub user accounts are created in the proper location and that users are published in the Exchange GAL. The stub objects for each collaboration partner are created in the dedicated OUs (within the OU specified during the setup).
The initial synchronization may take considerable time. This time depends on numerous conditions, including Collaboration Services settings (such as bandwidth quotas and timeouts), the total number of published objects, and network and server load.
NOTE: When you re-publish (or request re-publication of) a collection, you start initial synchronization of all objects in that collection. Because initial synchronizations can take considerable time, be sure to perform them only when it is required. It is recommended to re-publish only one collection at a time.
© 2019 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad