Forum Discussion
EAC Issue After Exchange 2019 CU14 Install
We upgraded our Exchange 2019 server from CU13 to CU14 successfully. This is a hybrid setup and we only use this server as a SMTP relay to Office 365. There are no mailboxes on-prem. Mail flow is wo...
I have the same exact issue with EAC is keep asking username/password and PowerShell session is not connecting to Exchange 2019 CU14 servers.
I am glad I am not the only one. I have not found a solution yet. I am almost to the point where I will open a support ticket with Microsoft. If you find a fix, please post it here.
- After I talked Microsoft support, I found the port 443/SSL certificate binding on Default Website and Exchange Backend sites in IIS manager changed somehow on Exchange servers after CU14 (Or the binding used to work before CU14).
Default Website 443 binding should be set to public certificate and IP address set to "All Unassigned".
Exchange Backed site binding should be set with self-signed Exchange certificate and also set to "All unassigned".
After I made changes, I have refreshed the Application pools (or do a IISReset). It worked for me.- Did you have two bindings for 443 on the default website? I have one for 127.0.0.1 and one for "all assigned". They are both using my public cert. Do I just need to remove the one for 127.0.0.1?
- Keep the 127.0.0.1 as it is.
The other 443 binding needs the IP address set to "All assigned" /*.