Exchange Migration: Problems with the Outlook connection

This short article is intended to list the most common causes of problems with the Outlook connection to Exchange during migration. Connection problems often occur after a mailbox has been moved to a newer Exchange version. Outlook then often displays one of the following messages: The Microsoft Exchange administrator has made a change that requires Outlook to be restarted. ... Read more

HowTo: Migration from Exchange 2016 to Exchange 2019 (Part 4)

In the last part of the article series "Migration from Exchange 2016 to Exchange 2019", the uninstallation of Exchange 2016 is prepared and the migration completed. The small Troubleshooting section is dedicated to the most common cause of failed or stopped MoveRequests. During migrations, problems can always occur that could not be ruled out beforehand. The causes can be ... Read more

HowTo: Migration from Exchange 2016 to Exchange 2019 (Part 3)

In part 3 of the article series "Migration from Exchange 2016 to Exchange 2019", it is now time to migrate the data. Specifically, it is about moving the various mailboxes and public folders from Exchange 2016 to Exchange 2019. I am moving the various mailbox types individually here, if no public folders or shared mailboxes (shares) are used, you can ... Read more

HowTo: Migration from Exchange 2016 to Exchange 2019 (Part 2)

Part 1 of the article series "Migration from Exchange 2016 to Exchange 2019" only described the test environment and the installation of Exchange 2019. Now the more interesting steps follow. This part is about the configuration of Exchange 2019 for co-existence with Exchange 2016. The aim of this article is to create a functional Exchange 2019 server and ... Read more

HowTo: Migration from Exchange 2016 to Exchange 2019 (Part 1)

Now that Exchange 2019 and Windows Server 2019 are available, there is nothing standing in the way of migrating from Exchange 2016 to Exchange 2019. Only the change in licensing could be problematic for some: Exchange 2019 is only available in the volume licensing program. This is the first part of the article series "Migration from Exchange 2016 to Exchange 2019" ... Read more

Exchange 2019: Migration from Exchange 2010 possible?

I have received various questions in the comments and by email about the migration options for Exchange 2019. Judging by the messages, many people are wondering whether it will be possible to migrate from Exchange 2010 to Exchange 2019. The question is quite justified if you take a look at the version numbers: Exchange 2010: 14.0 Exchange 2013: 15.0 ... Read more

Exchange 2019: Test migration from Exchange 2016 to the Technical Preview

Exchange 2019 is currently only available as a Technical Preview, so I cannot publish detailed instructions on how to migrate from Exchange 2016 to Exchange 2019 at this point. Nevertheless, I was interested to know whether migration is already possible. At the moment, of course, this is only recommended for testing in test environments, as the Technical Preview ... Read more

Exchange Migration: Problems with Autodiscover (HTTP 400) and Kerberos

When migrating from Exchange 2010 / 2013 to Exchange 2016, there may be problems with Autodiscover in connection with Kerberos. The problems range from permanent queries of the login information in Outlook to a complete crash of Outlook when a mailbox is moved to an Exchange 2016 server. When can the problem occur? The problem ... Read more

Exchange 2016: Error when moving mailboxes (A version mismatch was detected)

During the migration from Exchange 2013 to Exchange 2016, the following error (version mismatch) may occur when moving user mailboxes from Exchange 2013 to Exchange 2016: A version mismatch was detected (Actual:6, Expected:5) The following message can then be seen in the Exchange 2013 server log: 2017-04-23T20:37:21.432Z,6,Default,Error,",", "RegisterMigrationBatch failed, exception at Microsoft.Exchange.Migration.MigrationServiceHelper.SafeInvokeImplMethod(Action method, MigrationServiceRpcMethodCode methodCode) at Microsoft.Exchange.Migration.MigrationNotificationRpcSkeleton.RegisterMigrationBatch(IMigrationNotification ... Read more