How do I migrate resources?
How do I migrate resources?
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 (AD) with the type designations intact. When the Data Migration Wizard mailbox-enables those objects, the mailboxes are created with the correct resource type.
In a typical scenario, AD security objects have been created for all users and resources, and a dirsync creates mail-enabled AD contacts that correspond to existing security objects. The Provisioning Wizard merges the contact information (including resource types) into the existing security objects, and deletes the contacts, leaving a single mail-enabled security object in AD per user or resource. After the merge process creates the mail-enabled security objects, the Data Migration Wizard can mailbox-enable the objects.
Note: If a resource appears in a collection but no corresponding security object or contact resides in AD, the Provisioning Wizard can be configured to overlook the missing entities. This feature is enabled or disabled by a check box on the Choose the Container for User Objects screen:
[ ] Create new objects for recipients that do not already exist in Active Directory
Select the check box if you want to create a new mail-enabled object in AD when none is found to correspond with a user (resource) in the collection. Leave the check box clear to disable that feature. Any such new objects are created in the container specified by the User Container text box (on the Choose the Container for User Objects screen).
|
|
NOTE: Use this Createnewobjects... feature only if no corresponding contact or user object already exists in AD. If an AD user object exists without a corresponding contact, the wizard will mail-enable the existing object. |
How do I migrate mail-in databases?
How do I migrate mail-in databases?
Migrator for Notes to Exchange migrates Notes mail-in databases, such as Resources, to Exchange as Shared mailboxes. The Directory Export Wizard recognizes mail-in databases as distinct from other (user) mailboxes and identifies them as Mail-in Databases in Notes Migration Manager in the Object Type column of the Objects found table.
When migrating a mail-in database, verify that the source address in the TSV file matches the name associated with the mail-in database folder to be migrated. You can verify the name in the Notes administrator account under the Mail-In Database section. The mail-in database is matched up using either of:
The application does not perform a lookup in the names.nsf file but instead looks for the matching address in the mail-in-database NSF file.
|
|
NOTE: The Data Migration Wizard sets forwarding on a mail-in database if it is told to do so by setting the MailAddress attribute in Notes Document Properties for the mail-in database. |
How do I save and restore all Migrator for Notes to Exchange-defined collections from TSV files?
How do I save and restore all Migrator for Notes to Exchange-defined collections from TSV files?
It is rare but possible that data corruption or incongruities in the SQL database can make it easier to delete the database contents and re-export data from the Notes/Domino source, although it would be tedious in most environments to manually recreate collections one at a time.
The Manage User Collections and Manage Group Collections screens in Notes Migration Manager allow you export all Migrator for Notes to Exchange-defined collections (all at once) to a TSV file, and later restore them to the SQL database (also all at once), to spare you the time and trouble of having to manually recreate collections in the event the SQL database is deleted and reloaded.
See Group Collections: Manage Groups and User Collections: Manage Users in chapter 1 for the export and import procedures.
