In our previous blog post we covered an overview of what migration endpoints are, how to find them and what makes them tick. In this post, we will cover related troubleshooting. Note that this post h...
Updated Mar 30, 2020
Version 5.0
Blog Post
Hi Mirela_Buru ,
Thanks for the reply. I can confirm the HCW was v17.0.4544.0, and I was indeed selecting the classic topology. Another support tech had previously selected modern topology, but was instructed by MS support to change that as a result of a different error message we were getting. It is therefore true that we did previously use modern topology, then changed to classic, as you describe in the article. At that time we were also instructed to run Remove-HybridConfiguration on the on-prem server, and we did not select modern topology again since doing that.
The server in question is a client production system so I'm not keen to make changes for the sake of it, and if I do need to make changes then I need to plan a server maintenance window for a weekend. If you would like to see the results of the process recorder then I can plan to run the HCW in a couple of weeks time, and come back to you. Otherwise, I'm happy to let it lie (until it causes a problem). I did take a screenshot of the final screen, see below.
Another observation is the HCW reports Exchange 2016 CU11 when we are actually running CU16
Kevin