I'm so angry that it is possible to get into this situation, but here goes.
I had a perfectly operational exchange 2013 server which I was about to commission into production. Before doing so I was investigating a minor issue with RPC over HTTP and changed the authentication methods for the ECP and OWA from forms to Basic and Windows. Here it all went wrong.
Unable to login, unable to access PS. The whole thing fell apart.
There have been so many steps, I'll recite the ones I can remember.
- Had to reassign the SSL cert in IIS to gain PS access again
- Attempted to correct the ECP and OWA authentication methods for the back end and default website via PS
- Removed and recreated the ECP and OWA virtual directories via PS
I can now access the (ECP) login form, however when I use my previously working credentials (I have several) to log into the ECP I'm informed my credentials are incorrect. (They are now, I can RDP to the server with them and before all this started they were fine)
I must have messed up the authentication communication somehow. I did in my panic after changing the authentication methods in the ECP (when I had access) attempt to fix them in IIS, so I suspect I've really messed something up.
What do I need to do to get Exchange to communicate with the domain and authenticate again? (the exchange server is also a domain controller, one of two)