Most Exchange admins know that you can setup Exchange in hybrid configuration to integrate your Exchange on-premises infrastructure with Exchange Online; this is done using the Hybrid Configuration Wizard (HCW) which is available for download and provide a wide range of configuration options (from lightweight to complete/classic configuration).
Microsoft has released this new version, which is a major version update, the build begins with 17.x vs 16.x. The build number can be found in the top right corner once you download and open the HCW.
Because of the web-based distribution nature HCW uses and this version is a brand new package, you will get all this goodness simply by installing the new HCW from here. The current builds of HCW (16.x) will not automatically update to 17.x build, in fact – you could run the two side-by-side. Once you are on 17.x build – the HCW will then auto-update as usual.
As part of the improvements:
- HCW will no longer enable Federation Trust by default for all installations. Instead, it will only enable Federation Trust if there are Exchange 2010 servers on premises. HCW will call Get-ExchangeServer and if no Exchange 2010 servers are reported, the workflow to enable Federation Trust and subsequently require domain proof will not execute. Note that organization relationships are still created
- FIXED – When uninstalling the hybrid agent and switching to Classic in the HCW, this action would sometimes fail with a “null reference” error.
- IMPROVED LOG – HCW 8064 error – unable to configure OAuth, and subsequently had no idea why OAuth failed to configure? In this release, OAuth configuration has been completely changed: instead of enabling OAuth at the service layer, it is now enabled via a Graph API under the context of the Tenant Admin. This in turn removes the error obfuscation we had with the service layer enablement and allows us to include a detailed error entry in the HCW log. So while you still see the HCW 8064 error in the HCW UI, you can now review the log for the specific error detail which will make it easier to troubleshoot and resolve.
- When verifying DNS, a fallback mechanism what present that would reach out to an external site to verify domains. It has been removed and now only use the endpoint “mshybridservice.trafficmanager.net”, which is listed in our endpoints documentation.