First a little background..
Migrator for Notes to Exchange (MNE) uses Outlook (MAPI) profiles to connect to Office 365 and migrate data. On the migration server, MNE automatically generates a unique Outlook (MAPI) profile for each user being migrated simultaneously, or put another way, 1 Outlook profile for each migration thread.
By default, MNE will use the Office 365 migration administrator account that is entered on the Exchange Server settings screen, as seen below:
Herein lies the problem…
In Office 365, each user is limited, or throttled, to 500MB of maximum throughput per hour when using Outlook (MAPI) profiles. This means that by default, even if you have configured MNE to run 8 migration threads, the cumulative migration throughput for all threads together will max out at 500MB per hour.
A clever solution!
This is where MNE’s admin account pool feature gets its place in the spotlight. The idea is that you create a pool of “admin workers” to take the load off of the main Office 365 migration administrator account. Each migration “admin worker” account in the pool will be able to achieve 500MB per hour migration throughput. For the best results, you would want to create an admin pool account for each migration thread you plan on running simultaneously across all MNE migration servers.
Here is an example..
Let’s say you have 6 MNE migration servers:
1 will be the Admin server, which will host the MNE40DB SQL database and will be available for reviewing logs, creating user collections and other management tasks.
The other 5 MNE migration servers will be doing the heavy lifting, each running 8 migration threads. As an aside, we typically find that the sweet spot for migration throughput is running 8-12 threads on each MNE migration server.
In this example, you would need to create 40 admin pool accounts (5 migration servers x 8 threads on each server) to reach your full migration performance potential.
A step by step…
In order to enable the MNE admin account pool feature, there are two prerequisites:
Microsoft’s MSOL Sign-in Assistant x64 edition (available at this Microsoft link).
Microsoft's Azure AD Module for Windows PowerShell x64 edition (available at this Microsoft link).
After installing the two prerequisites above, you are ready to continue with enabling the admin account pool feature in MNE:
- Open the MNE Migration Manager
- Click on the Exchange Server settings screen
- Locate the “Use admin account pool” option and click Manage…
- Wait a couple of minutes as the Office 365 modules are loaded and the connection to Office 365 is made
- Assign a password for these admin pool “worker” accounts. They will all use the same password, which will be subject to your normal Office 365 tenant password expiration policies.
- Check the box to “License Admin Pool Accounts”. These admin pool “worker” accounts need an Exchange Online license. You can remove these licenses from your Office 365 subscription once your migration project is complete.
- Set the “New pool size” to the number of migration threads you plan on running across all MNE migration servers simultaneously (“40” for our example above). As your migration volume changes, you can come back here an add or remove accounts from the pool as needed.
- Click Apply.
- Wait for a few minutes while each admin account pool worker is created
- Click Close
- Check the “User admin account pool” box
- Check the “Always use these values” box
- Click Apply
You are now ready to fasten your seat belt and migrate from Notes to Office 365 at ludicrous speed!
In a future post, I will discuss ways to proactively grant “Full Access” migration permissions to the admin account pool “workers”, to reduce Office 365 permissions propagation delays.
Be sure to check out the Migrator for Notes to Exchange Product Support page to find solution articles, tips and tricks, tutorials, documentation, notifications, life cycle tables, training, and a product user forum.
For customers that are interested in evaluating Migrator for Notes to Exchange, you can sign up for a trial here.
We love to hear any and all feedback. Tell us what you like, don't like, and if you have any ideas for future enhancements, please let us know on the discussion forums!