Exchange 2010

Lotus Domino -> Exchange 2010 in Lab (Part 2)


Published: 2010-11-19
Updated: –
Version: 1.0
Part: 2 (of 2)

Configure Notes Migrator for Exchange (NME)


NME will need at least SQL Express 2005 or SQL Server 2005 and newer.
In my Lab environment I’m using SQL Express 2005 and the Management Studio for it.
This should be installed before doing the NME installation.

The installation of NME is pretty much a straightforward process and the first time it starts up, it will ask for a
license, provide it with the license and go further.

We will be asked to provide the SQL Server settings and authentication for it.

I’ve done it like the picture below shows

The next setting we need to configure is the “Shared Directories”, I’ve shared some folders on my migration
server and using them for logs, *ssdm and *ssdmlogs.
*Self-Service Desktop Migrator

Do NOT use verbose logging, it will SPAM you, instead use normal logging and if necessary check the logs
and change afterwards.

Anyway, my settings looks like below

“Notes Server” is the next setting, just like it looks like, the id file, domino name and password should be entered here.

Next screen shows the Exchange Server settings; in here I gave it the account that has the “Receive As” permission.
Also specify the Exchange version.

Active Directory settings, in this window I’m typing in the account that has Domain Administrator and
Exchange Org Admin rights. Also specifying OUs for distribution groups and external members
of distribution groups.

That was it for the configuration of NME.

It’s now time for finding the Domino directory and locates all information from the Domino environment.
Go to Find NABs and run the wizard, it should look like below

Next step is to search for the available domains inside Domino, that’s done through the “Find Domains” wizard.
It will look something like this when the wizard is done.
If you want to add more domains manually that could be done in the NME GUI with the “Add domain” button.

To see what users, mail-in databases, groups etc. there are in Domino it’s time to Export the directory, this will
export the information to the GUI and save it inside the SQL database.

Migration of user mailbox contents


In my lab I’ll do the migration based on matching SMTP addresses, so it’s important that a matching mailbox with the same
SMTP address as in Domino.

The creation of users and mailboxes could be achieved in different ways, either like in my lab; created manually.
Or by using scripts, or using a provisioning solution like MIIS/ILM/FIM, very often used at large companies.
This post is not about how to create a mailbox so it’s created in the background here.

Now it’s time for the migration, in my scenario here I already have the mailbox created, so it’s the configuration of mail
routing and the mail data that I want to move.

This is done by selecting Migrate User Data and selects the user collection and pressing the Migrate button

I will not move the trash to recycle bin, that’s the only exclusion I’ve done.
And not moving the Archive either.

Doclinks should be taken care of by the Notes client.

The migration is done through the Domino server.

The contents should be placed into the mailbox (on the server).

The mail routing settings, new mails should be sent to Exchange using SMTP protocol.

Mail system=Other Internet Mail and the calendar domain in my case is set to “Exchange”.

Select the “Remove free/busy forwarding attributes from Exchange public free busy folder”.

Here we select to migrate all contents.

Selecting the default settings and press Next.

Selecting the default settings and press Next.

Migration is in progress.

Migration is done.

Checking the person document in Domino, the information has been changed; Mail system and Internet address.

Calendar domain has been changed to “Exchange”.

Let’s check the mailbox in Outlook and verify that the contents look OK.
And it does J

I want to mention that this is not any best practice in any way, this is done in lab environment!

Ps. This tool should be setup and configured by a PSO consultant (Quest).