Notes Migrator for Exchange

Notes Primer

May 2014

2014, Cognizant
Notes Fundamentals

Notes / Domino and MS Exchange are very different

solutions both in terms of architecture and functionality
Exchange relies on AD for its members (Global
Catalog) whereas Domino uses its own directory
Exchange uses central mail Information Stores
(shared) whereas Notes uses individual files per
User for their personal data
Means Domino typically uses NO single instancing for mail
storage
But there are options for Shared Mail (uncommon) and Domino DAOS with later
versions of Domino

Notes permits the making of data-file replicas,

both locally and on the Domino Server
Local replicas are updated automatically and widely used
Similarities With Exchange
Notes Object
Domino (Server)
Notes (Client)
iNotes / Domino Web Access
(Web Client)
Local Replica
Personal Address Book (PAB)
Domino Directory (NAB)
Document Link
Mail-in Databases
Resource Reservation Database
Archive NSF File
Exchange Equivalent
MS Exchange (Server)
Outlook (Client)
OWA (Web Client)
Outlook PST/OST File
Contacts
Global Address List (GAL)
Hyperlink
Shared Mailboxes
Resource Mailboxes
Archive PST File
Differences From Exchange
Notes Objects Function
NSF File Notes Storage File that is the format for all Notes Databases
NTF File Notes Template File is what NSF files inherit their design
elements from. These can be customized.
Name & Address Domino Directory equivalent to AD where all User, Group
Book (NAB) and Server information is stored. File called Names.nsf
Names.nsf Default name for the NAB and the Personal Address Book
(PAB)
Groups Three types:
Mail DLs
Access Used to grant access to applications
Multi-Purpose can server as Mail or Access Control
groups
Resources Conference rooms, projectors and like resources are stored
in the Resource Reservations database
User ID Used by Notes for authentication. Created by the
Administrator and copied to the User workstation
Personal Address This is typically stored on the End User workstation and
Book (PAB) holds personal addresses and distribution groups. File also
called Names.nsf
NSFs and NTFs

Everything in Notes is a database

Many of them, all individual files
Examples are Domino Directory, Personal Address Book, Mailboxes,
Archives
A .NSF file denotes a Notes database file
Contains the application data
Comprised of forms, fields, folders, views
Also has a navigator and a database icon that allows
for personalization of the data presentation
A .NTF denotes a Notes template file
Contains the database structure; forms, folders, and
views
Does not contain documents
Used to create .nsf databases
Standard NTFs come from the install; Mail, PABs
These can be easily customized and often are!
Domino Directory

The Domino Directory is a Notes Database and the center

of the Notes universe
Stores information about every server, user, local mail
recipient, group, certifier, and resource in the local
Domino domain
Stores information about how servers route mail and
replicate databases
Every Domino Server hosts a primary Domino Directory
with the filename names.nsf
This defines the membership of the local
Notes Domain
Document Types

Domain Documents these are key different types of Domain

documents for migration

Domain Document Type Function

Global Domain Document Document used for Internet Addressing in the
Domino Directory
Foreign Domain Document Defines the path between the Domino Domain
and the external mail system such as Exchange
Foreign SMTP Domain Provides Domino Servers with information on
Document where to route a specific SMTP address to a
specific Host (equivalent to a Send Connector in
Exchange)
Person Document
Domain Document: Foreign Domain Document
Domain Document: Foreign SMTP Document
Internet Addressing

Global Domain Document identifies what Internet

Domains Domino is responsible for routing
Determines how Domino will form the
Internet Address if this is not specified in the
Person Record and this is possible!
Many objects such as resources, groups and
mail-in databases do not have assigned
internet addresses
Domino does not have to have an exact match for the
SMTP address like Exchange
It pattern-matches on the alias portion of the
address so it can even ignore the Internet
Domain and still make a match
Global Domain Document

Authoritativ
e

Authoritativ
e
Internet Addressing

Example

User name is Bob Smith / Internet address specified in the

Person Document is B.Smith@winemakers.com

Notes is able to route email to Bob Smith using any one of

these addresses: Bob.Smith@winemakers.com,
Bob@winemakers.com, Bob_Smith@winemakers.com
Internet Addressing

Domino Users often use these alias addresses

They become business critical but its also
difficult to determine who is using them

NME will discover all the Internet Domains that

Domino is responsible for routing and then
generate aliases for them so they can be present in
Exchange
Addresses

Domino uses proprietary addresses internally

that must be converted during migration to
preserve reply-ability
CN=First Last/OU=Org
Unit/O=Org@NotesDomain will be converted
to first.last@xyzcorp.com (on migration)
When messages leave the Domino environment
they are converted to normal SMTP address
Bob.Smith@xyzcorp.com
Rooms and Resources

Conference rooms, projectors and like resources are stored

in the Resource Reservations database
This database is where users schedule and manage meeting
resources
Users can select a particular resource and reserve a time for
it, or they can choose a time and let the Resource
Reservations database display resources available during
that time.
All management of Resources are performed through this
database
Creating and removing new conference rooms
Restrictions on the capacity and hours it can be booked
Restrictions on who can book the room
Rooms and Resources
Notes Fundamentals: Security

Database security is managed by the Access Control List

(ACL) on the individual database
The ACL contains a list of all the Users, Domino Servers,
and Groups that have access to the database and what
level of access they have
In order to modify the Domino Directory you must have
sufficient rights on the names.nsf.
It is possible to have rights on the Domino
directory and NOT the Mail File as each
databases has its own unique ACL
Notes Fundamentals: Security - Mail File ACL
Notes Fundamentals: Security

When a new User is created, the Notes Admin

creates
A Person Document
A User ID File
Mail File
These files identify the User to Domino and are
required to access the Server and Local databases.
The Administrator will use the Certifier ID File to
create the User ID file
This will creates an electronic stamp that
indicates a trust relationship
All Domino security is driven off of the Certifier
Notes Fundamentals: Location of Notes Data

Mail Stores are located on Domino server in an .nsf file

Can also be replicated to an End Users
machine so he can work from a local copy
Personal Address Books (PAB) can be located on an End
Users machine, a Domino Server, or a File Server
iNotes installations can synchronize the
personal address book into the mail file
Archives can be located on the Domino server, on an End
Users machine OR on a File Server and it can be in all
three locations
Notes Fundamentals: Notes Applications

Anybody with a Notes client can develop an application

Notes supports
Standard template-based applications that
can be customized
Team Rooms
Document Libraries
Discussions
Custom Applications
Expenses
HR
Order Processing
 Notes Migrator for Exchange

May 2014

2014, Cognizant
Notes Migrator for Exchange Terminology
Archive
Files that contain Users personal mail and
calendar data, stored in an NSF file. Most users
store archives on their local workstations to help
stay within the limits of Server quotas
Coexistence
The state of two independent mail or directory
platforms when both are serving the same
organization at the same time. This is a common
temporary condition during the transition period
of a migration
Collection
A defined group of Users or Groups based on
Domino Directory. All migration tasks are all
applied to collections
Notes Migrator for Exchange Terminology
Data Migration Wizard
Performs the bulk of migrations activities such as
mailbox enable, forwarding, data migration
Directory Export
Exports Domino directory information into the SQL
database
Label
A device for classifying and sorting collections, by
alpha-numeric strings, that can be assigned to
collections in the Collection Wizard that creates them
Mail-Enabled Object
A security object that can receive messages at an
external e-mail address only. They cannot send or
store messages on Exchange
Notes Migrator for Exchange Terminology
Mailbox-Enabled Object
A security object that has a mailbox that can
send, receive, and store messages on their
Exchange Server
MX Record
Short for Mail eXchange record, an entry in a
domain name database that identifies the mail
server responsible for handling emails for that
domain name
Object Merge
Consolidates Contacts with User Accounts to
create a Mail-Enabled object
PAB Replicator
Sends a special email that allows users to
replicate their Personal Address Book to a
Domino server to be migrated
Notes Migrator for Exchange Terminology
Provisioning
Populating a directory such as Active Directory,
with objects such as Users and Groups
PST File
The files in Microsoft Outlook that contain Users
personal storage data typically the form to
which Notes archives are migrated
Self Service Desktop Migrator (SSDM)
End user driven migration component that can
migration mail, PABs, and archives
Synchronization
Process of updating the contents of one directory
to match the contents of another directory
Notes Migrator for Exchange Terminology

TSV File
Unicode text data files, stored in a structured
tab-separated-values (tsv) format that uses
tab characters as field delimiters for data
tables
Product Architecture
Core Component Review

Quest Notes Migrator for Exchange is comprised

of five core components
Console (Notes Migration Manager)
SQL Database
Self-Service Desktop Migrator
Notes Migration Scheduling Application
Log File Viewer
Console (Notes Migration Manager)

Central console from which all migration

activities can be coordinated, launched and
reviewed
Allows Project Consultants to
Program default and Server access credentials
Identify the location of Notes/Domino source data
Export data from the Domino directory
View ongoing migration statistics
Track migration project status
Create Mailboxes and manage Mail forwarding
Migrate Data
Notes Migrator For Exchange Console
SQL Database

NME requires a SQL database to store project

information
Multiple consoles can connect to the same
SQL database and share the same project
information
User information from the Domino directory is
imported into database
Provides Domino information to the Quest
Provisioning, Object-Merging, and various
Migration Wizards
No mail data is stored in the SQL database so it
stays relatively small
Self-Service Desktop Migrator
Standalone application that allows End Users to
migrate their own data
Executable launched from within a share or using
a link
Is launched from the End User workstation that
has Outlook and Notes installed and configured
An Administrator can also launch it on behalf of
the User using his/her credentials
Mail can be from a Server or a Replica
Many will use this in conjunction with a central
migration
An easy way to capture PABs, Archives, and encrypted items
Encrypted mail requires the User ID file to
decrypt so encrypted mail is best handled by the
SSDM
Notes Migrator Scheduling Application

Command-line application that executes

scheduled tasks such as Directory Export and
Data Migration Wizard
The program checks the SQL database to see
whether any tasks have been scheduled to
run since the last check
If yes, it executes them
If no, it runs another check in the time interval specified
Also known as QSched or QSched.exe
Runs as a Windows Task
Log File Viewer

Simplifies the viewing and interpretation of the

program log files
Log files are generated by most NME Wizards
Document process errors and warnings
You must set the default location for log storage
once the product is installed
Can be done through the GUI
Shared Directories line item on the left

Will tell you about what Notes-specific Objects /

Features that were skipped
Log File Viewer
Additional Wizards

In addition to the five core components, NME

also contains 10 built-in Wizards
Launched from within the Console
Used for numerous functions:
Help discover location of Notes NABs, Data, and Internet
Domains
Create User and Group collections
Provision Groups
Replicate PABs
Merging objects in Active Directory
Additional Wizards

Collection Wizard Data Migration Wizard

Directory Export Wizard Send PAB Replicator Wizard

NABs Discovery Wizard AD Groups Provisioning Wizard

AD Object Merging Wizard Internet Domains Discovery Wizard

Notes Data Locator Wizard Self-Service Desktop Migration

Statistics Collection Wizard
Rights & Permissions

Most Common Method

Will use three administrative accounts
One for Notes
Requires Manager Access to the Domino Directory and the Mailboxes to be
migrated
One for AD
Needs to be in the Exchange Org Admin group and Builtin\Administrators
(Domain)
One for Exchange
Domain User with a mailbox that has a minimum of Receive As rights on
every mailbox Store
Migration Planning

Having the right migration plan is critical to delivering a

successful migration project
Before you are ready to deploy NME into the
environment your migration design should factor in
Customer Drivers and Requirements
Location and volume of data, bandwidth restrictions
Coexistence Scenarios
Migration Planning

Customer Drivers and Requirements

Understand the customers resource commitment
Who are the Help Desk, Network/Exchange/Notes Admins
working on this project from the customer side?
Inventory the Notes environment
Is there a provisioning tool in place populating the AD /
Exchange target environment and if yes, what?
How will Outlook be deployed?
Is an archiving solution in place and if yes, which one?
Design the E2.x environment
What version of Exchange are they migrating to?
Is the customer attempting to centralize their mail
environment?
Do the target Exchange mailboxes reside in a hosted
environment?
Migration Planning

Customer Drivers and Requirements

Build out lab and test process
Do there a test lab?
Does it mirror the production environment?
Perform several production pilots to fully validate
process
Is the Help Desk be included in the pilot?
Who validates migration session success?
What is the prescribed rollback procedure?
Who is responsible for key nightly backups?
Who will validate the pilot was successful from the customer?
Execute migration in production
Who will liaise with the Help Desk as migrations begin?
Does the customer require status reports?
Whats the plan for Day 1 support?
Discovery of the Customer Environment
Require a comprehensive, current inventory of the
Notes environment
Location of Notes data
Volume of Notes data
Location of archives
Quotas
Inactive mailboxes
Groups
Resources
Mail-in Databases and Shared Mailboxes
Version of the Notes Clients
Lotus Notes Report Pack will provide you with these
details
Add-on report pack to Quest MessageStats
Domino Admins can also help
Migration Considerations

Is Exchange ready for migration?

Is there sufficient disk space on the target?
Be conscious of the amount of data to be migrated and what this will cause
in terms of size of Exchange transaction logs
Will backup schedules need to be adjusted?
Sometimes backup schedules need to be adjusted to keep pace clearing the
logs with the amount of migrated data added to Exchange
Should you consider a freeze on changes to the environment for a
period of time to validate the stability of the environment?
The number of directory changes can potentially force offline
Address Book re-generations in certain versions of Exchange
Migration Considerations

Use the questions below to help determine the best

migration strategy for your customer
How many users will be migrated?
Do these users require free/ busy?
How long will it take to complete the migration?
How are you planning for a consistent directory between
the Source and Target environments?
i.e. Directory Synchronization
How much data will be migrated?
Are there any quotas in place on either environment?
If yes, can they be temporarily removed?
Do you have Domino Archives?
If yes, are they to be migrated and where?
Migration Considerations

Use the questions below to help determine the best

migration strategy for your customer
What are you planning for Exchange archives?
PST, O365 Personal Archive, or 3rd party solutions
Are you planning to migrate resources?
If yes, when will the migration occur?
How will administration be done during the coexistence period?
Are you planning to migrate Notes Groups?
If yes, when will the migration occur?
How will administration be done?
Has Active Directory been populated?
If yes, how were these account created?
What is the provisioning process for new users in the
organization?
Migration Considerations

Use the questions below to help determine the best

migration strategy for your customer (cont)
Where does the MX record point to?
Is there a Smart Host involved that can do LDAP
lookups?
Do you know how many encrypted mail messages and
private folders are in use and where they are at?
Are there any special character languages in the
environment?
What language packs need to be installed?
Is coexistence needed?
For what period of time?
Does the customer need to retain Notes rich text content?
 Migration Scenarios

| 2014,
Migration Scenarios
The migration approach you choose will be based
on the level of coexistence needed by your
customer
Three options
No coexistence / Offline
Simple
Complex
Migration Scenarios No Coexistence

Option 1
When there IS connectivity between Source and
Target
Also known as a big bang migration all users are
migrated at once and Domino will be decommissioned post
migration
Option 2
Where there is NO connectivity between Source and
Target
Will include offline migrations
No Coexistence: Option 1 Big Bang

No coexistence - Big Bang

No directory / no SMTP mail flow coexistence
There is connectivity between the Source and Target
Fairly small number of users and a small amount of data
to be moved
Well-connected network
Can be completed over the weekend
Few expectations about retaining a consistent directory
There can be user impact
Fairly uncommon scenario because Notes usually stays
as an application platform
Typically seen in divestitures where there are a small number
of users/data in play
What It Looks Like Big Bang
No Coexistence: Option 2 Offline

No coexistence - Offline
No directory / no SMTP mail flow coexistence
There is NO connectivity between the Source and
Target
Or extremely limited connectivity which makes offline the
preferred migration method
May work well in certain situations
Two methods
PST
Requires additional step of merging migrated PST data into
Exchange or distributed to the users
NSF
Requires additional step of copying of the Domino NSFs to disk
Data needs to be physically transported to target
site
Memory stick, external hard drive, etc
No Coexistence: Option 2 Offline

No coexistence Offline
Large number of mailboxes in the environment can
make this process cumbersome
Does not use the full functionality of Quest Notes
Migrator for Exchange for managing migration (e.g.
manage mail forwarding, direct migration, etc)
There can be end user impact
Can be used in together with a online migration
model for some poorly connected customer sites
Example, youve got a Domino Server in Kazakhstan with
very restricted bandwidth to the site
What It Looks Like Offline Data Migration

SMTP
Message Delivery

PST
External HD
Source Domino Quest Migration Console Target Exchange
Quest Notes Migrator converts mail and
Environment personal address book data into PST. Environment
PSTs are taken to site and moved into the
target by Microsoft ExMerge.

NSF
Migration Scenarios Simple Coexistence

Assumes the target Exchange environment has already been

pre-populated with Users that can be mail-enabled or
mailbox-enabled
Assumes there is direct connectivity between the Source and
Target environments
Popular approach, will work well in many customer situations
Easier to implement as there are no Coexistence tools
It provides no level of Coexistence between the
environments other than SMTP-based mail routing
No free/busy lookups
No automated directory synchronization
However these can be achieved using alternative means
FIM, in-house provisioning applications, scripting, etc.
Migration Scenarios Simple Coexistence

Simple coexistence
It leverages the full functionality of Quest Notes
Migrator for Exchange to manage the migration
Manage mail forwarding, mailbox enable, data migration
What It Looks Like Simple Coexistence

SMTP
Message Delivery

Source Domino Quest Migration Console Target Exchange

Environment Environment
Migration Scenario Complex Coexistence

Coexistence between the Source and Target environment is

provided using
Coexistence Manager for Notes (CMN)
Microsoft Transporter Suite
Does add a layer of complexity as a result
Assumes there is direct connectivity between the Source and
Target environments
Both solutions listed above provide Free / Busy lookups,
Directory Sync and mail routing
NME picks up coexistence tools leave off
Manage mail forwarding, object merge, mailbox-enable,
data migration
Complex Coexistence CMN

Quest Coexistence Model

SMTP Mail via CMN Mail

Connector

Source Domino Target Exchange 2007/2010

Free/Busy & Directory
Environment Connector
Environment
CMN Server and Domino
Server Pair

Quest Data Migration Model

Source Domino Quest Migration Console Target Exchange 2007/2010

Environment Environment
What Comes First?

Migration of email generally occurs first

Discuss migration plan with Notes Admins and
Developers
Notes Applications usually have mail built into the
workflow
Important the Developers understood what
migration plan is because some changes can impact
the application functionality
Pre-Migration Activities
For Notes Readiness
Tidy the environment by asking Users to delete
unwanted mail
Remove quotas on the Domino Server for the
duration of the migration
Reading the NSFs causes them to grow and can result in
quota-related errors
Identify resources and shared mailboxes that
functional groups use
Best practice is to migrate these together
Decrypt mail before central migration if not using
SSDM
This allows mail to be migrated through the central console
Pre-Deployment Activities

Ensure you have the NME software and correct license

key
Need to ensure all required machines are in place
SQL Server, Console Machine, etc
Verify rights and permission requirements are met
Verify recommended system requirements are met
This will help maximize performance
Understand how users will be groups together for migration
Deployment Models
Deployment Type Variables Configuration Guidance
Phased migration over a Single Console
Single Console prolonged period of time. All product components are
installed on this machine. SQL
Typically less than 50 DB can be on an existing SQL
mailboxes @ 350 MB each Server or this server.
per day
Phased migration with a Designate one console as
Multiple larger number of mailboxes Primary
Consoles to migrate per day (longer All product components are
than a weekend scenario) installed on this machine. SQL
DB can be on an existing SQL
OR Server or this server.

A big bang migration Additional consoles will

where high throughput connect to same SQL DB and
numbers are needed used same Shared Directories.
Product Installation

Things to know
Migration Console machine is a member of the same AD as
Exchange Server.
Ensure the appropriate language packs and code pages are
installed on the Console
Install using a Local Admin account.
Install the Outlook client and configure the profile before
the NME install
Lotus Notes must be installed in single-user mode and
configured with ID file before the NME install
Product Installation

Installing NME is a simple process:

Consists of four core steps
Launch the installation executable
Choose the destination location for the software
Choose to install the SQL native client
Copy the files
Once the product is installed you can
Install the license
Connect to the SQL Server
Set the location for the Log Files
And more
Product Installation: Step 1
Product Installation: Step 2
Product Installation: Step 3
Product Installation: Step 4
Product Installation: Step 5
Product Installation: Step 6
Configuring Notes Migrator For Exchange

License Installation
SQL Server
The path for the bulk import directory
Ideally should be on the SQL Server
Log files directory
A common tools directories
Self Service Desktop Migrator which include address
translation files
Self Service Desktop Logs
SQL Server Configuration Screen
Configuring Notes Migrator For Exchange

Location of the Bulk Import Directory.

Location of the Self Service Desktop Migrator
log settings
This is where the logs and statistics for SSDM will be placed
Notes Server information
Domino Server name
ID File for Notes
Password for the ID File
Exchange account to be used for the
migration
The Exchange Server version
(2007/2010/Hosted/Office 365)
Outlook Anywhere, (RPC over HTTP)
Configuring Notes Migrator For Exchange

Specify AD Account that will be used to

delete contacts, provision groups & other
operations.
Optional OU Destinations for :
Groups
External Contacts for Users in Distribution
Groups
AD Provisioned User Accounts
Resource forest migration AD Credentials if
necessary.
Shared Directories
Notes Server Configuration
Exchange Server Configuration
Active Directory Configuration
Final Steps..

Name and Address Book Discovery Wizard

Contacts the Notes Server specified during configuration
Exports the names of available Address Books enabling you
to choose which one to run the Directory Exporter Wizard
against

Internet Domain Discovery Wizard

Queries the Notes Global Domain Document for all Internet
Domains that Notes is responsible for routing
Uses this information to generate aliases that will be stamped during the
mailbox enabling action so addresses remain consistent when the mailbox is
migrated
The more addresses that are on the list, the longer the Directory Export will
take
Name and Address Book Discovery
Internet Domain Discovery
Notes Migration Workflow

1 Run Directory Exporter

2 Create User Collections

3 Merge Contacts / Provision Users in AD

4 Create Exchange Mailbox

5 Send PAB Replicator (optional)

6 Migrate Users / Data Sources

7 Create Group Collections

8 Provision Groups
Directory Export Wizard
The Directory Export Wizard exports all of the
Domino Directory which includes all Person
Records, Resources, Groups into the SQL Database
Every migration tasks use the Directory
Information stored in SQL
Best practice is run this at least once a week so
new employees, renames are updated into the
database
Larger customers may need to run it multiple times per day if
there are many changes in the Domino Directory
Large Domino Directories will take a longer time to complete
(several hours)
You can manipulate the values stored in SQL by
a tsv import/export
Process will complete faster if fewer internet
domains specified
Directory Export Wizard
Step 2 Create A User Collection

You can create a User Collection using several

methods
Select objects from the SQL Server database by
name or other value
Import the contents of a .TSV file
Use filtering based on a custom attribute in the
Domino Directory
Filter on existing values like Department or Location values

Custom attribute filtering is easy

You can choose a filter using existing values in
the Directory or create a new one
Migration date is a very common value to use
Any value used needs time to replicate before performing a
Directory Export prior to migration
Step 2 Create A User Collection

Collections can be created, modified and

recycled
They cannot be deleted by design
Users can exist in multiple Collections
Existing Collections can be edited to
add/remove members
All Migration Tasks will begin by selecting a
Collection
User collections can include Resources and Mail-
in Databases / Shared Databases
Step 2 Create A User Collection
Step 2 Create A User Collection
Step 2 Create A User Collection
Step 2 Create A User Collection
Step 3 Provision Users In Active Directory

Possible Provisioning Scenarios

1. No users exist in Target
Common for BPOS/Office 365 migrations

2. Contacts only exist in Target

MS Transporter or CMN may have been used

3. User objects only exist in Target

4. Mail-enabled or mailbox-enabled user
objects exist in Target
Step 3: Provision Users In Active Directory

Provisioning Scenarios And Approaches

Scenario Recommended Approach Comments

No users in Target Can use NME or
another method to
provision user account
Contacts only exist in Use NME or another Data Migration Wizard can
Target method to provision be used with
user account MboxFromContact
Parameter
Users objects only Use NME to mail enable Merge Contacts Wizard can
exist in Target mail enable and ensures
required re-direction
addresses are applied.
Mail-enabled user Use NME to mailbox Data Migration Wizard can
objects exist enable mailbox enable and ensures
required re-direction
addresses are applied.
Provision AD Users Workflow: Detailed Steps

Handled by the Merge Contacts Wizard

Specify OU Where Users Will Be Created
Launch Merge Contact Wizard
Find AD Objects
Review Configuration Summary
Run The Contact Merge Wizard
Review Completion Screen
Step 3 Merge Contacts

AD Object Merging Wizard used to merge Contacts

and User Objects into a mail-enabled object
Intermediate step before mailbox enabling the
object
Preserves all of the Contact attributes
Several steps must be completed prior to running the
wizard
Export the User Collection to a TSV file
Populate the Search Key column with the Users
SamAccountName
Save the file as a TSV
Run the Import Objects From TSV
Run the Object Merge Wizard
Step 3 Merge Contacts

Other values can be used for matching between

Domino and AD
If Employee ID is present in both Directory then
you can automatically match this by selecting the
attribute on the Wizard
Timing can be flexible!
Object merging and mailbox-enabling should be
performed at the beginning of the migration or
right before the data is migrated
For those customers using the Transporter and CMN
for Free/Busy Coexistence, it will continue to
function until the they are Mailbox enabled
Step 3 Merge Contacts

Step Step Step

1 2 3

Contact with Contact with Notes Mail Enabled User Object

Notes Addressing Addressing is deleted Email Attributes Merged from
Contact but no Mailbox present

User Object Mail Enabled User Object MailBOX Enabled User Object
No Email Attributes Email Attributes Merged from Email Attributes Merged from
Contact but no Mailbox present Contact and Mailbox present
Step 3 Merge Contacts
Step 4: Create Exchange Mailbox
Data Migration Wizard has multiple uses throughout
the migration process
Used to mailbox-enable accounts
Set and/or manage mail forwarding
At this point the Data Migration Wizard will be used
to mailbox-enable accounts
Launch the Data Migration Wizard
Select the User Collection
Enable the first two options to mailbox-enable
the accounts and the manage mail routing
As soon as you mailbox-enable a User you either
have to switch them over to Exchange OR set a
forward back to Notes
Best practice is to forward back to Notes until you are ready to
cut over (otherwise mail will land in both mailboxes!)
Step 4: Create Exchange Mailbox

Dont forget about the delegation

Most companies have Notes mailbox
delegation in place and want to retain it
A mailbox must exist in the Exchange target
for the user or else delegation on the Source
mailbox will be dropped
No mailbox, no delegation
Step 4: Create Exchange Mailbox
Step 4: Create Exchange Mailbox
Step 4: Create Exchange Mailbox
Step 4: Create Exchange Mailbox
Step 4: Create Exchange Mailbox
Step 5: Send PAB Replicator
Migrating the Personal Address Book (PAB) can be a
challenging aspect of Notes migrations because
PABs are separate from the mailbox
Stored on the hard drive of the user workstation
Referred to as a PAB (Personal Address Book)
Actual file name is Names.NSF, the same as the
Server Directory
The Send PAB Replicator Wizard simplifies the task
Copies PABs to a Domino Server allowing for
rapid, central migration
NME sends an email to each End User that contains a button that
replicates the User PAB to a Domino Server of the migration
administrators choice
Activated when the End User clicks on the button
Tracks what Domino Server the PABs will be replicated to
Step 5: Send PAB Replicator

PAB Replicator button

Is a small .NSF file bundled in with NME
Can be edited (i.e. change the look and feel
of the button) provided the functionality
remains unchanged
Step 5: Send PAB Replicator

Alternate means of migrating the PAB

Use the Locate Notes Data Stores Wizard
Only works if all the PABs have been replicated to a Domino
Server or File Server
Use Self Service Desktop Migrator tool to
perform this task
Can insert link into welcome message when they are
migrated directing them to use NME
Simple interface for users to use
Can be run by local user or project team members
Step 5: Send PAB Replicator
Step 6: Migrating Users
Data Migration Wizard

Manage mail routing

Migrate users
Perform Notes administrative functions
Many other features are
A welcome note can be automatically sent to
users
You can specify the data that will be migrated
(Mail, PABs, Archives)
You can specify where this data migrates to
(Server, PST, Archive)
You can apply filters based date and attachment
size
You can strip attachments from mail
Step 6: Migrating Users

Launch the Data Migration Wizard

Ensure the options to manage mail routing
and migrate users are selected
Mail forwarding option will be set prior to data migration so
new mail will arrive in the Exchange mailbox immediately
Ensure option to perform Notes
Administrative Functions is not selected
Step 6: Migrating Users
Configure welcome message contents if you want to use one
Very useful way of communicating to the End User about their migration
status
Next you specify what to migrate
Mail data
Archives
PABs
Specify where the Wizard will find the content to be migrated
Domino Server or other location
Specify where the content will be migrated to including PST,
Exchange Mailbox, or Exchange 2010 Personal Archive
Step 6: Migrating Users

Mail Routing Options

Configure the options
If Coexistence is in use additional
configuration will be required
MS Transporter or Coexistence Manager for Notes will have
different mail routing and coexistence settings that will be
required.
Once select a coexistence option you will be forced to enter
the required settings before proceeding this ensures all of
the correct fields are populated for coexistence.

Additional configuration parameters will need

to be set on the formatting of the forwarding
address
Step 6: Migrating Users

Data Migration Wizard also allows migration of

Mail-in Databases
Resources
Archives
Shared Mailboxes

Always migrate these types of data with their

respective Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 6: Migrating Users
Step 7: Creating a Group Collection

You create and use Group Collections the same

way as User Collections
Easiest to select objects from the SQL
database or use a .TSV file
Group Collections also can be created, modified
and reused
They cannot be deleted
All Group actions are driven from a Collection
Step 8: Provision Groups

AD Groups Provisioning Wizard performs this

action
Provisioning is the act of migrating groups
Can be done incrementally or all at once
Incremental approach is normally performed when an entire
business group is provisioned.
Provisioning all groups at once at the end of the migration is
most common and preferred
There is NO two-way sync between Notes
and Exchange by design
Step 8: Provision Groups

Within the Provisioning Wizard there is an ability

to synchronize
Does not perform a two-way sync
Will only add members who appear from the next Directory
Export run
Need to continue to run this Group Collection in order for this
to work
Best practice is to provision Groups at the
end
Provisioning does NOT use a license
Step 8: Provision Groups
Locate Notes Data Stores

Archives and PABs can be in locations other than

a Domino Server
Domino Replica Server
File system (home drive, network share)
External drive or media
Are these files required for migration?
How can they be located?
How can they be associated with the owner?
Locate Notes Data Stores

Locate Notes Data Store Wizard helps locate the

data for future migration
Wizard will scan a specified location looking for databases
Determine if it is an archive, PAB or mailbox based on the
template type specified in Manage Design Classes in the NME
Console
Determines the owner by reading the ACL or Profile Owner
document in the database (Archive, PAB or mailbox)
Migrating Data Offline

Offline Data Migrations maybe preferable when

there is
No/Poor connectivity between sites
Security concerns
Archive requirements
Domino Server failure scenario -
Need a unencrypted copy of the Domino Directory and Mail
databases which could be converted into PSTs & migrated.

Very fast and reliable as its reading from a local source versus the
network

Can be used in together with live migration

Notes Data Locator Wizard
Notes Data Locator Wizard
Notes Data Locator Wizard
Using The Self Service Desktop Migrator

SSDM is the self service utility that can be used

by End Users
There is no installation required on the End
User machine as it runs from a File Server
Requires a pre-configured Notes Client, pre-configured
Outlook Client

Converts Mail, Archives, and PAB data for the

End User
Not every customers want to use an End User
driven solution
Using The Self-Service Desktop Migrator

Used primarily to migrate the Archives and PAB

but
It is highly flexible and can be used to perform all aspects (of the
Notes migration except for managing the directories
User is using his own rights to perform the migration so they
will not have rights to manage directories
e.g. Cannot be used for forwarding or mailbox enabling
Encrypted messages are migrated securely
Have the option to write into a PST or into Exchange
If Exchange, an a mailbox must already exist
If migrating into pst files, it will automatically add them to
the Users Outlook profile
Using The Self-Service Desktop Migrator

SSDM can be easily customized to hide screens so user only

has to click a series of next buttons
Customizations are done through editing an INI file in the
SSDM directory
Locate the SSDM directory by checking the Shared Directories
To add customizations edit the NotesDTApp.ini
Check the NME Parameters Guide for a full listing of customizations
Examples of what can be customized through the INI
Data destinations PST or Server
Date Filters
Data Selections Archive, PAB, or Mail
Self Service Desktop Migrator
Self-Service Desktop Migrator
Self-Service Desktop Migrator
Log File Viewer

Every migration action performed against a collection

creates a log
Logs can be located and reviewed again after the
migration action has completed
Stored on the NME Console youve designed as the Log
Directory under the Shared Directories settings
Set this location during the NME configuration
Always use Normal logging level unless
troubleshooting a small number of mailboxes
Verbose logs can be very large for a large collection (1-2GB in size)
Log Directory
View Summaries

Statistics
View Summary section is available in the
Console
There are a number of reports contained in
this area which will provide you with such
details as the source size of data, errors,
migration statistics
Exportable into Excel
View Summaries
Migration Throughput

The Data Migration Wizard uses multi-threading

Multiple mailboxes can be migrated simultaneously
Average rates of data transfer is about 500 MB / hour if
source and target data are local

Projects can be accelerated by running

migrations from multiple migration consoles
Essential for larger migration projects
Easy to add additional consoles since they share
the same project information from the shared
SQL database
Scheduled Operations

All NME tasks can be scheduled which helps

automates aspects of the migration, allows out
of hours migrations.

Manage Scheduled Operations screen in the

Console
Manage the scheduling of the tasks
Schedules then saved in the SQL Server database
Executed by the Notes Migration Scheduling Application
(qsched.exe) process which is setup as a Windows Task
Uses the time & date information on the Migration Console.
Scheduled Operations

The Qsched program checks the SQL Server database

to see whether any tasks have been scheduled to run
since the last check
If it finds anything scheduled it will executes them
The Qsched program is an independent application
It can be executed from the command link or scripted.
It can be configured using Windows Scheduled Task Wizard
Notes Migrator for Exchange: Licensing

Licenses used are based on Domino User Name

Directory Exporter downloads the Domino
Directory information and places details of items
such as Person Records, Resources, and Groups
into the SQL database
Each of these Domino directory object has a
unique name
A license is used when an activity is performed
against one of these unique Domino names
This can include mailbox enablement, object merge, mail migration, use of the
self service tool, etc
Groups are NOT counted
If a user has more than one mail file (i.e. archives) these additional mail files are
NOT counted
Notes Migrator for Exchange: Licensing

Hard Stops
There is NO undo - once a license is used,
its gone
You can exceed the number of licenses
purchased by a very small amount before the
tool stops working on new users
Best practice is to check the Project View within the Console
to track the number of licenses used and ensure additional
licenses are purchased at least 7-10 days prior to needing
them
SSDM Users write logs to a central share and
they should be Audited through the Gather
Desktop Statistics in the Console
Once these logs are collected by the Wizard they will display in the Console
statistics and count against the license
Migration Cleanup

Occurs after the last Notes User has been

migrated to Exchange.
Verify that the Domino Server is no longer
processing any mail traffic
Delete the temporary migrate.domain.com
Decommission the Domino Server
Delete the single administrative accounts
created for the migration project
Shutdown the Quest Console
 Thank you

2014, Cognizant