Forum Discussion
tonyguadagno
Aug 07, 2023Copper Contributor
upgrading from exchange 2013 to 2019, new install of 2019..cannot login to ecp or owa
hi, thanks in advance for your help. i have an existing small environment. it consists of a pair of 2022 domain controllers, the domain/forest level is set to 2016. I have an existing 2012 (not r2) ...
- Sep 01, 2023
ok, after spending $500, 3 weeks and 4 engineers, I finally have this fixed...i hope this will help you.
the moral of the story is pay attention to the warning messages. In mine, you will see it referencing a cert thumbprint. this thumbprint is the Microsoft Auth Certificate on my Exchange 2019 server. I had found this article but it talks about your auth cert being expired...my auth cert was not expired so I dismissed it...and so did the Microsoft tech until they could not think of anything else to do....so they recommended we recreate the auth cert any...and this fixed my issue.
if you have this warning message, the issue is almost certainly the cert it references!
good luck
TAE_YOUN_ANN
Aug 08, 2023MVP
In the IIS Management Console, click the Binding Settings section of the Site->Exchange Back End item and verify that Microsoft Exchange Certificate is selected for port 444.
- tonyguadagnoAug 08, 2023Copper Contributor
TAE_YOUN_ANN hi, thanks, my SAN cert was bound to port 444 so i changed it back to the "Microsoft exchange" cert that setup created and i did an iisreset....that did not help.