Converse agora com nosso suporte
Chat com o suporte

Binary Tree Migrator Express for Exchange 20.10 - Release Notes

What’s New in Version 20.10.0

Binary Tree is now part of Quest. All product names and brand elements have been updated for Binary Tree Migrator Express for Exchange 20.10.0 to reflect this change.

 

Release Notes 20.10.0

  • Product names and brand elements have been updated.

Previous Updates

3.0.0.8

  • An issue where the Migrator Express for Exchange Agent was not compatible with Microsoft Office Click-to-Run has been resolved. (66680)

  • An issue where the Migrator Express for Exchange Agent did not create a profile for the target mailbox in a Windows 7 64-bit client machine has been resolved. (67266)

3.0.0.7

  • An issue with mailbox migration when the mailbox is hidden in the GAL has been resolved. (44088)

3.0.0.6

  • Migrator Express for Exchange now preempts connection timeouts while migrating mailboxes with large numbers of folders from on-premises Exchange to Office 365. Periodically pinging the target now keeps the connection active due to an apparent shortening of the Office 365 connection inactivity threshold. (36849)

  • This release introduces an updated End User License Agreement (EULA). The installer will prompt you to review and accept the new agreement. (38341)

3.0.0.5

  • A message with an empty Subject field no longer generates an Unexpected error – Item: - Source Folder: Inbox (NullReferenceException) migration error. (33872)

3.0.0.4

  • The Migrator Express for Exchange Agent now supports HTTP proxy for connections to Exchange, for environments that require a proxy config and routing via the proxy. (32169)

3.0.0.3

  • Migrator Express for Exchange now correctly migrates a forwarded email message whose original Subject field was empty (so that the Subject in the forwarded message reads only "FW:"). (28990)

3.0.0.2

  • The Migrator Express for Exchange migration engine now provides improved handling of MapiMigrate process errors, suppressing an error dialog box (that previously would pause the migration process until the user dismissed it), and adding log details to help troubleshoot the problem. An application crash caused by the MapiMigrate process was resolved with upgraded DLLs of the migration engine being used to copy data from the source to the target mailbox.  (26152)

  • Migrator Express for Exchange now correctly sets folder permissions when migrating mailboxes from Office 365 to an on-premises Exchange 2013. This was resolved with upgraded DLLs of the migration engine being used to copy data from the source to the target mailbox. (26180)

  • Migrator Express for Exchange now counts a mailbox migration job as Failed only when a configurable number of migration errors are encountered for individual items within the mailbox. The threshold is zero by default (so that a migration job status is Failed if any single item fails) but can be set to a higher value by a new FailThreshold key in the MAPIMigrate.exe config file located in C:\Program Files\Binary Tree\E2E Express\bin. For example, a migration job is marked Completed if FailThreshold=20 and the job completes with only 19 (or fewer) item errors. (26644)

3.0.0.1

  • Two new checkboxes have been added to the Settings tab for "Enable migrated message" and "Enable Welcome message".  These are checked by default, but if unchecked, these notification messages will be disabled. (22818)

3.0

  • An Migrator Express for Exchange Agent to install on user workstations has been added. The Migrator Express for Exchange Agent allows for the Migrator Express for Exchange Mailbox Cutover process. The agent switches the user’s personal profile to point to their target mailbox after mailbox migration is complete. The Cutover process is managed on Migrator Express for Exchange's new Cutover screen. (2702)

  • Migrated mail can now be replied to without running a separate utility or script. Recipient objects are now changed to SMTP objects after migration. (2772)

  • The ability to migrate online archives has been added (2793)

  • The ability to migrate mailboxes and archives to PST files has been added. (2794)

  • A code change has been made to ensure installing Migrator Pro for Exchange and Migrator Express for Exchange on the same machine will not share a database and cause compatibility issues. (13137)

  • Migrator Express for Exchange now supports SQL Server 2014. (13201)

  • Migrator Express for Exchange will now automatically disable Cached Exchange Mode for Outlook profiles. If Cached Exchange Mode cannot be automatically disabled, the user can manually disable this mode. (13205)

  • An issue where an empty message was being copied to target when the network connection between Migrator Express for Exchange and the Source Exchange Server was interrupted has been resolved. (13274)

  • An issue where when using MAPI with a target server of Exchange 2013 or greater, the incorrect target server information was displayed in the logs has been resolved.  The server name is no longer logged if the server is Exchange 2013 or greater. (14252)

  • Migrator Express for Exchange supports migration to and from Exchange 2016. (14296)

  • A code change was made to speed up the determination of folder items counts during mailbox migrations. (14444)

  • An issue where migrated messages could not be replied to in Outlook Web App (OWA) has been resolved. (14527)

  • The MAPI/CDO prerequisite has been removed from the Migrator Express for Exchange installer. (14528)

  • An issue where the UI would be disabled if a migration profile was saved without defining a range end date has been resolved. (14576)

  • When adding a new profile, the Add button will now blank out the existing profiles name. (15005)

  • The selectable logging level now includes Error, Warning, Verbose, Info (default), and Off logging levels. (15062)

  • There was an issue where Public Folders were not created in the proper folder tree location during rationalization if the public folder name contained characters from the Polish alphabet. This issue has been resolved. (52842)

  • An issue where the auto-licensing to O365 was not being applied to mailboxes during migration based on available SKU has been resolved. (53447)

  • O365 Forest Rationalization has been modified to process O365 mailboxes in batches which speeds up rationalization in large environments. (53476)

  • An issue where Public Folder rationalization missed public folders with names containing characters from the Polish alphabet has been resolved. (53884)

Product Licensing

A valid license is required for Binary Tree Migrator Express for Exchange.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

To apply a license file:

  1. Click the Settings icon.

  2. Click Apply License.

 

 

 

 

Ferramentas de autoatendimento
Base de conhecimento
Notificações e alertas
Suporte a produtos
Downloads de software
Documentação técnica
Fóruns de usuário
Tutorial em vídeo
Feed RSS
Fale conosco
Obtenha assistência de licenciamento
Suporte técnico
Visualizar tudo
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação