Forum Discussion
Enzo Faranda
Nov 01, 2020Copper Contributor
Exchange Hybrid Issues
Hello, I'm hoping that you'd be able to help me on an issue that I've found myself working on. I'm working on an Exchange Hybrid (Exchange 2010 with Microsoft 365). The Hybrid has been runni...
JeremyTBradshaw
Nov 01, 2020Iron Contributor
Hi Enzo Faranda,
Sounds like it could be a cert issue. You mentioned the TLS 1.2 thing, maybe that fix was the catalyst for this new issue?
I would browse to the autodiscover URL you found from Get-ClientAccessServer and login using valid user/password. It should let you in and show you some XML. The browser should see the certificate as valid. If both of those checks pass, it is likely something else like DNS or maybe load balancer.
If you updated/replaced the certificate that Exchange had been using (for your TLS1.2 fix), it might not have been gracefully enabled for the Exchange services (e.g. IIS).
Let us know.
Sounds like it could be a cert issue. You mentioned the TLS 1.2 thing, maybe that fix was the catalyst for this new issue?
I would browse to the autodiscover URL you found from Get-ClientAccessServer and login using valid user/password. It should let you in and show you some XML. The browser should see the certificate as valid. If both of those checks pass, it is likely something else like DNS or maybe load balancer.
If you updated/replaced the certificate that Exchange had been using (for your TLS1.2 fix), it might not have been gracefully enabled for the Exchange services (e.g. IIS).
Let us know.
Enzo Faranda
Nov 01, 2020Copper Contributor
JeremyTBradshawThanks Jeremy,
I had only looked into the TLS 1.2 upgrade as a potential fix, the issues I had mentioned were present before the TLS upgrade.
I did also check the cert and this is still valid, nothing cert wise has changed since the issues had been reported.