Chat now with support
Chat mit Support

Migrator for Notes to Exchange 4.16.3 - Pre-Migration Planning Guide

About the Migrator for Notes to Exchange documentation Introduction Critical considerations Other strategic planning issues Appendix A: Known limitations of the migration process

Domino Server Running on AS400, AIX, Unix, or Solaris

If a source Domino server is running on an AS400, AIX, Unix, or Solaris server, the wizards can directly access NSF files only if:

If any Domino source in your network is running on a non-Windows server, and you want the wizards to address NSF files directly, your Migration Plan should specify your method of access to the source data.

Migrating personal address books

The Notes user PABs (personal address books) typically are stored locally (per user) but can also reside with the mailfile, or on a server. MNE includes a PAB Replicator Wizard that can send an email form to users to automate the task of copying their PABs to a centralized Notes server directory where the Data Migration Wizard can find and migrate them.

The Data Migration Wizard can migrate PABs by any of the four methods listed in the preceding section of this chapter, Location of Notes user data.

Migrating resources

Notes/Domino resource management is different than comparable features in Exchange, but MNE can map these features in a way that mimics the settings and behaviors in Notes. After migration, an Exchange administrator can use the capabilities of Exchange to refine the resource restrictions that were set in Notes.

Each Notes resource is configured with an Owner Restrictions setting that defines who is authorized to request a resource, accept or reject a request, book a request, and approve (confirm) a booking. The five Owner Restrictions settings are listed in the following table with descriptions of how the settings affect resource access in Notes and in Exchange after migration (if you choose to migrate this information).

In Exchange, access to a resource is determined by a longer list of specific conditions, each of which is permitted or denied independently as part of the resource configuration. Also, what Notes calls a resource owner corresponds to what Exchange calls a delegate, and MNE migrates Notes resource owners and behaviors on that basis.

Notes Owner Restrictions set to:


No owner is assigned to the resource, and anyone can reserve it.

The calendar attendant and resource booking attendant are enabled on the mailbox. Anyone can book the resource. Parameter set to
[Exchange] SetResourceToAuto­Accept=1


Owner Only

Any user can request the resource but all requests are forwarded to a designated resource owner who must approve resource requests.

Make the Notes owner a delegate. Only the delegate can book the resource and approve booking requests from other users. Delegates can also be assigned full-access permissions to the resource mailbox Optional parameter set to
[Exchange] GrantResourceOwnerFullAccess=1



A list identifies users who are authorized to access the resource. Only specified users can request and book resources.

Add specific people to BookInPolicy list and disable booking for others. Only people in the designated list can book the resource.



A resource request is AutoAccepted if the request comes from a designated owner, or from someone on a list of users authorized to access the resource. Other users can also request the resource but only an owner can approve the bookings.

Same as Owner Only, plus a list of users approved to book in policy. Only people in designated list can book the resource via autoprocessing; all others require a delegate approval.



The resource accepts and books requests from anyone, but allows conflicts.

Same as None, but the resource allows conflicts (effectively no booking policy). Anyone can book the resource at any time; conflicting bookings are allowed.


The Directory Export Wizard captures the owners and the authorized-access users of Notes resources and the Notes Owner Restrictions settings. The Data Migration Wizard can migrate this information when it migrates the resources. The directory export always captures the information but its migration to Exchange is an option that is enabled or disabled by a boolean program parameter in the [Exchange] section of the MNE Task Parameters and Global Defaults:

This feature is off by default (MigrateResourceDelegation=0). To migrate the resource owners and authorized-access users and the associated resource-access permissions, set MigrateResourceDelegation=1.

A related MNE boolean parameter (also in the [Exchange] section) lets you optionally add resource-owner permissions to migrated resource delegates in Exchange:

This feature also is off by default (MigrateResourceDelegation=0). To add resource-owner permissions to migrating resource delegates, set:

Resource types

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 provisions the objects into Active Directory with the type designations intact.

In a common scenario, Active Directory security objects are already 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 has created mail-enabled security objects, the Data Migration Wizard can mailbox-enable the objects.

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. You enable or disable this feature is using a check box on the Choose the Container for User Objects screen:

Select the check box 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 the feature. Any 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 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 mail-enable the existing object.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen