This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECH%3C/text%3E%3C/svg%3E)
Running Exchange Server 2013 (latest CU, latest updates) in Classic Hybrid mode - have considered the pros and cons of switching and trying to follow the steps here:
If you have weighed the pros and cons of switching from Classic to Modern, you proceed by deleting your existing migration batches and migration endpoint and re-running the Hybrid Configuration wizard and selecting Modern Hybrid.
However when I run the latest version of the Hybrid Configuration Wizard (17.0.8347.0, from http://aka.ms/hybridwizard), I log in to on-premises and Exchange Online, select the appropriate Hybrid Features, Hybrid Domains etc but never get the 'Hybrid Topology' screen:
The wizard does not give me the option to switch.
Have checked the following:
Any ideas?
@ChrisHill-9515
Could you provide screenshots about HCW step by step in your organization? It could help us narrow down this issue. (Remember to delete private information before posting)
I also want to confirm with you, do you choose “Full Hybrid Configuration” during Hybrid Features?
Toggling MRSProxy shouldn't matter, as they need to be on for both for moving mailboxes across.
As indicated, you may need to remove existing migration batches, remove existing migration endpoint and HCW should start show the section.
To confirm/check, just after Gathering Configuration Information, press F12 and open the HCW log. It should show what HCW retrieved at the end,
and verify it is not picking up current HCW configuration which caused it to skip the topology section.
@Michel de Rooij Aha! Looking through the logs made me realise there are two places where I needed to check for migration batches and endpoints - both the on-premises and the in-cloud Exchange Management Console. The wording about removing the 'existing... migration endpoint' (singular) confused me.
I removed the migration endpoint from Exchange Online and it all works now :)
Many thanks!
@KyleXu-MSFT Yes, we're choosing 'Full Hybrid Configuration'.
Here you go:
As you can see the option is never presented.
It looks weird, let's take the following steps to further troubleshoot:
Hi @KyleXu-MSFT ,
Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $false
Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $true
Anything else?
@KyleXu-MSFT Oh and in my original post I said I was running .NET Framework 4.6.2 - sorry that should have been at least 4.6.2 - actually running 4.8 (per the CU23 requirements)
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Just to say that @Michel de Rooij 's response helped the most. Looking through the logs made me realise there are two places where I needed to check for migration batches and endpoints - both the on-premises and the in-cloud Exchange Management Console. The wording about removing the 'existing... migration endpoint' (singular) confused me.
I had not removed the Migration Endpoint from Exchange Online. When I did this, the option reappeared.
Thankfully Microsoft have recently updated the documentation to make this clearer:
If you have weighed the pros and cons of switching from Classic to Modern, you proceed by deleting your existing migration batches and migration endpoint in Exchange Online and re-running the Hybrid Configuration wizard and selecting Modern Hybrid.