Notes Migrator for Exchange (NME) Version 4.12 released

Notes Migrator for Exchange Version 4.12 released

Dell published the Version 4.12 of the Notes Migrator for Exchange. The new features are:

  • Configurable Subject field for migrated meetings in resource calendars – Set the Subject field as the actual meeting Subject or the organizer of the meeting to mimic native Outlook behavior
  • Custom, string-based migration filters for Mail/Calendar items and address books – Limit the data pulled from the migrating NSFs using the Data Migration Wizard
  • Expanded time counters – The elapsed and remaining time counters have been expanded to correctly report migration runs longer than 24 hours
  • Configurable locale for target folder names — Specify which locale section (in its Task Parameters) to use when assigning folder names to Outlook folders

Since there has also been a lot of bugfixing in the new version, we recommend to update installations.

Notes Migrator for Exchange (NME) – New Release 4.7 – BlackBerry migration support

Notes Migrator for Exchange Version 4.7 introduces a lot of new features and product enhancements

Dell published the Version of the Notes Migrator for Exchange. One of the new features  is the BlackBerry migration support:

NME now supports migration of BlackBerry accounts and devices as part of a migration from Notes to Exchange. Specifically, NME supports migration from Domino BES 4.1 to Exchange BES 5.0

(Source: Quest Notes Migrator for Exchange Release Notes, last revised 5/14/2013)

Exchange Migration to Office 365 can change behind the scenes – wave 15 rolls in

In these days Microsoft is moving from wave 14 to wave 15 for Office 365 cloud installations. This means a service transition from Exchange 2010 Server backend to Exchange 2013 Server backend, Lync 2010 to Lync 2013 and other cool updates.

However, if you have travelled a long way to get a smooth migration setup (with all the back and forth of finding the right strategy and technical conditions) Microsoft can make you a big surprise by changing your Exchange target infrastructure. You started your migration project with Exchange 2010 in the cloud as target system and you end up with Exchange 2013.

This is “by design” when moving services to the cloud – as MVP Sean McNeill stated in his post []:
This is an important questions because with a move to the cloud, the company give up some control on when, and even if, you will go through an upgrade of the service. The company now relies on the Service Provider, Microsoft in this case, to handle the upgrade and the cadence of the upgrades. This needs to be fully understood and accepted by a company moving to the Cloud.”

To mitigate the risk of forcing the customers to update in times where it is just neither “comfortable” nor “amusable” – as it might be in the middle of an Exchange migration project – Microsoft offers to postpone the update one time. The Office 365 admins receive a notification e-mail which announces the update schedule. From that information the customer has 3 weeks to decide that he better postpone or let Microsoft execute. When he decides to postpone, Microsoft will not start the update for the next 2 months. The timespan to complete the wave 15 upgrade is end of 2013 latest, which means your upgrade cannot be later than this deadline.

For more information check the Office 365 Upgrade Center:

Dell/Quest Software seems to recognize first problems in running migration projects and recommends to postpone the Office 365 tenant upgrade by contacting Microsoft.

Dell Quest Migration Tools: Readiness for Windows Server 2012 and Exchange 2013

Actually we can see a good market response to the new Microsoft Server flagships, Windows Server 2012 and Exchange 2013.
Migration projects are still ahead and probably will not die in 2013.

The following table shows the readiness of the Quest migration tool suite  and answers the question whether the tool can be installed on a Windows Server 2012, whether it can migrate Active Directory to Windows 2012 and mail systems to Exchange 2013.

Microsoft did not release a new version of ADMT yet (the most actual version is still 3.2), that is fully compliant with Windows 2012 functional mode domains, nor can you install ADMT 3.2 on a Windows Server 2012 member server. Actually, a migration from a Windows 2008 R2 domain to a Windows 2012 domain with 2012 functional level can neither be achieved by using the native tool (ADMT) nor Quest Migration Manager for Active Directory.

Active Directory Product Version Tool installation on Windows Server 2012? Can backup/restore AD data on Windows Server 2012 DCs? OR Can migrate data to Windows 2012 DCs?
Recovery Manager for Active Directory Forest Edition 8.2.1 yes yes
Recovery Manager for Active Directory 8.2.1 yes yes
Migration Manager for Active Directory 8.9 No no
Migration Product Version Tool installation on Windows Server 2012? Can migrate data to Exchange 2013? Office 365?
Migration Manager for Exchange 8.9 no no/yes
Migration Manager for Exchange IntraOrg Edition 1.0.1 no yes
Notes Migrator for Exchange 4.6.1 no (no Windows 8 admin workstation) yes/yes
Coexistence Manager for Notes 3.4 no yes/yes
Groupwise Migrator for Exchange 4.2 no (no Windows 8 admin workstation) yes/yes


Notes Migrator for Exchange – New Release 4.6.1

Recently Quest Software® (now a part of Dell) announced a new release of the frequently used software package Notes Migrator for Exchange. The new release comes as Notes Migrator for Exchange 4.6.1 and supports most actual Notes 7.0.4 as source E-Mail System and Exchange up to Versions 2010 SP3 and 2013 as target. Multiple archives can now be migrated into a single pst file by using the SSDM Utility. Furthermore, a couple of improvements have been implemented when migrating from Notes to Microsoft Office 365® Exchange Online mailboxes.
NOTE: Notes Migrator 4.4 is shifted to “Limited Support” by now.
You can download Notes Migrator 4.6.1 here: