Chat now with support
Chat with Support

Migration Manager for Email Archives 9.6 - Release Notes

Release Notes

These release notes provide information about the Quest® Migration Manager for Email Archives 9.6 release.


About this release

Migration Manager for Email Archives 9.6 is a major release with enhanced features and functionality. See New features and Enhancements for details. These notes can also be found on the Quest Support Portal at


The following is a list of enhancements implemented in Migration Manager for Email Archives 9.6:

When using Journal Explosion, it’s now possible to manually map to single target mailbox.


The user interface and SQL were adjusted to support a new source that will be introduced in a future release.


When using Journal Explosion, the Time to expire inactive items setting can now be disabled by entering 0.


During Journal Explosion, if a user’s primarySMTPaddress was changed during (or before) ingestion, they’re now handled successfully. On the JE Users Management page, they’re marked as having an invalid address. Then, a new Fix Invalid SMTP Addresses button can be used to resolve the issue.


PST files are now verified upon completion, before they’re moved to the PST file target location. A PST file is considered “verified” when they can be opened (showing they’re not corrupt) and the count of ingested items in the target PST is as expected.


The Native Format Import (NFI) module now ingests items in processes, rather than threads.


A new module and commands were created to support a new source that will be introduced in a future release.


Adjustments were made to Migration Manager for Email Archives Core to support a new source that will be introduced in a future release.


PST as a source is no longer supported for Journal Explosion.


For Journal Explosion to PST migrations, mapping ownerless users to an original smtp address is now supported.


Two new PowerShell commands are available to support finalization of JE leavers.


Modules that use EWS now support OAuth/modern authentication.


Microsoft EWS API version 2.2 is now used and Exchange import module trace entry text was enhanced.



The database upgrade process was enhanced for better selection of upgrade scripts for execution.


Several development components were updated. For example, LLBLGen was updated to version 5.5.3 (DB) and DevExpress was updated to version 19.1.4 (UI).

NOTE: Please note, requirements have changed for modules. Check your .net compatibility before installing Migration Manager for Email Archives 9.6. Special considerations might be necessary when upgrading large item databases. For upgrade instructions and in case of any doubts contact Quest Support at

Performance and handling of queuing of Journal Explosion items for ingest was improved. It is disabled by default.


On the Journal Explosion Leavers Management page, performance was improved of the Enable for Import, Merge Leavers, and Merge Leavers by Preview actions.


The triggering and execution of the Retry Failed Items action from the Failed Items report was enhanced.


Release history

The items below were added to Migration Manager for Email Archives 9.5

The enhancements below were implemented in Migration Manager for Email Archives 9.5:

Enterprise Vault 12.4 is now supported as a source and target.


Collection and migration of archives from Quest Archive Manager (QAM) is now supported.


When using Journal Explosion, mailbox quota information now displays on a new JEMailboxQuota page. The mailbox quota threshold can be configured on the Journal Explosion Settings page. For more information contact Quest Support at


When using Journal Explosion, you can now convert a shared mailbox exceeding quota to a regular mailbox so ingestion can continue.


The Default Stage 1 view now includes Journal Explosion mappings..


When PST is a Journal Explosion target, items for a certain user can be re-exported.


Exploded email addresses filtering has been implemented to limit UI to users in scope for Journal Explosions.


Office 365 Mailboxes with no association to synchronized Active Directory users can now be synchronized and used in mappings.


Proxy addresses for existing Journal Explosion users are now supported.


Global management of leavers was enhanced via 2 new PowerShell commands covering mailbox storage quotas in Journal Explosion.


Now, when you perform an action against an Office 365 link, only modules associated with that link are used in the execution of the applicable command.


Enterprise Vault journal archives without a P1 header (not regular Exchange Envelope journaled messages) are supported in Journal Explosion migrations.


It’s now possible to run Core Windows services on multiple machines.


Windows Server 2019 is now supported.


The Journal Explosion ItemRouting batch size is now configurable.


FTP settings (URL, username, password) are no longer hardcoded for the ExportFailedItemsToFTP command and use the settings from System Configuration.


You can now opt to include Journal Explosion sub-mappings (detail grids) in the exported report.


The option to set In-Place holds for Office 365 leavers has been removed in preparation for Microsoft feature deprecation.


The Progress & Performance and Performance pages can now be configured to display compressed sizes.


SQL was optimized, and temporary tables have replaced in statements containing a lot of parameters.


Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating