How to go past the ‘Adding Federated Domain’ status in the hybrid configuration wizard, while running from an Exchange 2016 CU7 server?
More…
I have come across this issue a couple of times now and mostly while the server from which I am running the hybrid configuration wizard is Exchange 2016 CU7. This is not to say that it won’t happen on another CU level.
The issue is that HCW gets ‘stuck’ while trying to verify the domain’s TXT record (to prove the ownership) and adding the domain. The wizard verifies the existence of the TXT record, but doesn’t go past the window below even after letting it do it’s thing for hours!
A quick google confirms that there are number of other customers who have the same issue and number of workaround and solutions have been suggested.
The one solution that has worked for me all the time is to have an ini file in the ‘Config’ folder of the Exchange 2016 server. Follow the exact steps below.
- check
- check
- check
- check
- check
- check
Have you used any other workarounds for the same issue? Let me know in the comments below.
That worked like a charm! I love you man will you marry me?
Glad it worked for you Sean.
Save it as .ini or as .txt?
Save it as .ini Ayyappan.
No luck for me
Did yo get it resolved Renier? Waiting for a bit before trying again might help.
Worked in my Case. Thanks!
Glad that the article helped you Jan
I had multiple domains. I checked then off one at a time, proceeded to next and then went back and did that for all of them until they were all able to get through the next step, then went back and selected all and was able to proceed.
Glad that the article helped you Pete
Same her
Only one Domain is not working.
Did you setup the .ini file?
Restart the server and run the HCW again.
i applied this but not success.
This has worked time and time again for me.
After adding the file, restart the machine and run the HCW again Sabbir.
Any suggestions for exchange 2010? Thanks
Is it the same issue Lee?
Whats the path for Exchange2010?
Hi Aji,
The default installation path for Exchange 2010 is C:/Program Files/Microsoft/Exchange Server/V14
It is, but there is no Config folder.
This didnt seem to work for me, but I ended up needing to add in the following reg keys for .net TLS issues and it worked.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727]
“SystemDefaultTlsVersions”=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727]
“SystemDefaultTlsVersions”=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]
“SystemDefaultTlsVersions”=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319]
“SystemDefaultTlsVersions”=dword:00000001
Thank you Brad for the update. I am sure it is going to help someone.