Archive for the 'Notes Migrator' Category

Configure Quest Notes Migrator for Exchange to Only Create PST files

Nov. 14th 2013

 

The 4.8 version of the Notes Migrator for Exchange has a slight “bug” in the Exchange options.

 

First a little back story of this Notes Migration

I was assisting a client that wanted to use NME to only extract data form their Legacy notes environment and create a single PST for each user/resource mailbox.

 

Sure no problem, we went through the process of installing a new NME standalone server with a local SQL Express (2005) instance installed.

While working through the initial configuration wizard of NME we “accidentally” selected one of the Exchange versions on the Exchange options tab. Once an Exchange version is selected it seemed the tool would not allow us to continue without populating the configuration, example: CAS server name, admin account name, admin account password etc.

(Older versions of the tool allowed you to select the check box “No Exchange option”.  This option was and is NOT on the Exchange options tab.  So… (scratch head and get another cup o java).

 

Let’s think about what happened, if the option is not present to skip the Exchange tab then maybe we just skip that portion of the initial configuration all together.  <wink>

 

So I dropped the NME (SQL) DB from the local SQL Express server.

 

Navigate to the “Application working Directory” and rename OR delete the addresstranslation.bin and the addresstranslation.tsv files.

 

Launched the NME and setup a new SQL database, populated the notes server information and SKIPPED the Exchange tab all together.

 

NOTE:  For an NME to PST migration some OR all of the following setting need to be added to the Global.ini file: Under the EDIT pull down menu in the NME tool.

 

In the [General] section add the following:

PABDest=PST

ServerMailDest=PST

Type=PST

PublicDelegates=0

 

(Make sure to save the changes)

 

 

Once we exported the Directory (Notes) and created an collection we were ready to migrate some data to PST.

 

Using the migrate user – select your collection and during the process of creating the PST files you will

see that NME will pop-up a window for the Exchange information:  On this screen you will see our MISSING check box:  Please select the check box “NO Exchange” and continue on.

 

Author Chris Pearson LeadThem Consulting Architect

 

 

 ———————————————————————————————————————————————————————————————-

 

 

Posted by LeadThem Consulting | in Notes Migrator | Comments Off on Configure Quest Notes Migrator for Exchange to Only Create PST files

The Most Important Aspect of a Notes Migration

Aug. 21st 2013

 

There are some aspects of a Lotus Notes Migration to Exchange that are more important than others, but they probably aren’t what you would expect.

Over the past five years of doing these mail migrations I’ve found that the most successful migrations come down to three common factors:
1) Good Analysis
2) Extensive Planning
3) Appropriate Expectations

That may seem like a given but sadly it’s far from it.

Good Analysis gives you a true understanding of what your source data is. This lets you plan how long your migrations will take, how many migration machines you need to setup and what kinds of data your actually migrating. In the end, understanding what you have will better prepare you for supporting what you migrate.

Planning seems like it should be easy enough from the start of a migration project. You only need some servers, and the software right? We all wish it were that easy. The reality is that yes, you need the servers and software, but you need to plan for:
• Migration space and expansion for growth on your Exchange server.
• You need to plan for when you need to be done with your migration and how many people per day you need to migrate.
• You need to know how much data you need to migrate per person.
• What kind of data you need to migrate. Do you need only calendar, mail, both?
• How are users going to connect to their new Exchange mailbox? OWA? Outlook Clients?
• How are you going to support your users after they are migrated? What kind of call volume can your support desk handle?
• Can you migrate during the day or will that impact your production servers too much? This is a limiting factor on how quickly you can migrate.
• Do you need coexistence?

These are just some examples of the common things to put a plan in place for. These are just the tip of the questions you need to ask and investigate before you start your migration. A rich plan will make your migration go much more smoothly.

And finally, setting appropriate expectations is probably the most important of all. Migrations are a translation from one system to another not a copy and paste. Knowing the limitations of a migration will help to control the support calls after the migration.

Starting with those three basic migration concepts will get you far in the start of your migration.

Author: Dave Cook, LeadThem Consulting  Notes Architect

 

 ———————————————————————————————————————————————————————————————-

 

 

Posted by LeadThem Consulting | in Notes Migrator, Uncategorized | Comments Off on The Most Important Aspect of a Notes Migration
logos

LeadThem Consulting
20418 SE Hwy 212
Damascus, OR 97089