Hope this helps anyone who gets themselves stuck in the same situation. Have now installed my go daddy certificate (again) and changed the "outlook Anywhere" settings in ECP to point to the path of my new certificate and all is well! what a way to start friday morning! Loaded up the Webpage and Yes! page loaded! fantastic, but then i got "Something Went Wrong" when logging in! typical! but after removing the HTTPS binding which had ip 127.0.0.1 (then iisreset in CMD) page loaded and logged me in! saved the day! Very worried i had a quick google around and changed the IIS bindings on the exchange server "Default Web Site" - "Bindings" and changed the https: port 443 IP * to select "Microsoft Exchange" as my SSL certificate (then iisreset in CMD) to reset the bindings. "domain".org.uk while in the HTTPS was "server"."domain".local) hense the proxy trust issue for clients.īefore i made this change i compleatly removed the Go Daddy Certificate and removed the CA from trusted (followed the steps i took in the install procedure but just removed them) and rebooted, only to find when i needed to get onto the ECP i just got a blank webpage. I have realised now that i needed to change the "Outlook Anywhere" settings to match my new SAN in the certficate (everything in the certificate was. I had this exact issue, I had recently installed a new Go Daddy CA onto Exchange 2013, the OWA was secure but had an issue with the proxy settings, all users could not connect. It was only then that I discovered the issue, so it's possible it could have occurred before I started to mess with certificates.Įmail is flowing. In the end we decided to purchase a SAN certificate and I undid the steps I went through. We had a standard SSL certificate so to try and resolve autodiscover issues I followed some of the steps at http:/ Opens a new window / articles-tutorials/ exchange-server-2010/ management-administration/ exchange-autodiscover-part2.html. If the problem continues, contact your helpdesk." Sorry, can't get that information right now. When I access ECP via FQDN or localhost, I am initially presented with the normal OWA login screen but when I enter administrative credentials I get the error message: It was up and running, but after playing about with certificates, ECP now seems to be broken. Having some difficulties with Exchange 2013.
0 kommentar(er)
