Exchange 2010 and later permit the differentiation of resources into three types: Room, Equipment and Online Meeting. The Directory Export Wizard copies the resource type designations from Domino into the object records in the SQL database, and the Provisioning Wizard then provisions the objects into Active Directory with the type designations intact.
Note: If a resource appears in a collection, but no corresponding security object or contact yet resides in AD, the Provisioning Wizard can be configured to overlook the missing entities. This feature is enabled or disabled by a checkbox on the wizard’s Choose the Container for User Objects screen:
Mark the checkbox if you want the wizard to create a new mail-enabled object in AD when none is found by the wizard to correspond with a user (resource) in the collection. Leave the checkbox unmarked to disable that feature. Any such new objects will be created in the container specified by the User Container text box (on the wizard’s Choose the Container for User Objects screen).
NOTE: Use this Create new objects feature only if no corresponding contact or resource object already exists in AD. If an AD resource object exists without a corresponding contact, the wizard will simply mail-enable the existing object. |
Notes-to-Exchange resource booking is typically accomplished by one of two methods:
• |
To support free/busy inquiries with N-to-E resource booking: Delete the Domino resource and use CMN's Directory Connector to create a forwarding contact to replace it—to route resource requests to the corresponding resource object in Active Directory. |
• |
If free/busy is not required: N-to-E resource booking can be achieved by mail forwarding, where the resource in Domino is configured to forward its mail (resource requests) to the corresponding resource object in AD. (Migrator for Notes to Exchange can automatically configure this mail-routing when it migrates the resource.) |
By default, the Data Migration Wizard and Self-Service Desktop Migrator both preserve ACL information, including calendar and task folder ACLs, as they migrate Notes source data to Exchange. To disable this feature, you can set ACLs=0 in the [General] section of Task Parameters or Global Defaults (for the Data Migration Wizard), or in the notesdtapp.ini file (for the Desktop Migrator).
IMPORTANT: For delegates and ACLs to migrate properly:
|
A few other notes to keep in mind about migrating ACLs and Delegation Rights:
• |
Migrator for Notes to Exchange maps Notes Delegate permissions to Exchange so that, if no permission level in Exchange corresponds exactly to the Notes Delegate permission level, Exchange will assign the next lower level. This prevents any case where a non-exact match yields a higher level of permissions in Exchange than was allowed in the Notes source. For example, if a Notes Delegate with access level Editor is authorized to Delete owned document but not to Delete any document, Exchange will assign the Delegate to the Author level in Exchange. |
• |
For the Data Migration wizard, when targeting Office 365, only well-known folder ACLs are migrated. However, if [Exchange MigrateWellKnownFolderAclOnly is set to 0, the ACLs of all folders involved in the migration are migrated. |
• |
Exchange does not assign the non-specific Custom access level, but instead assigns the defined, more specific access level that is closest to the original Notes level without exceeding any Notes permissions. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center