Access Exchange 2013

amscottnyc
amscottnyc used Ask the Experts™
on
I had setup self signed SSL certificates in IIS on Windows 2012 which enabled me to access Exchange 2013 owa and ecp. Then I went to install a store bought SSL cert. I deleted what I thought were just the self singed certs and installed the new SSL cert in IIS Manager. Now Exchange doesn't respond to anything. When I try to access OWA I get a message saying the certificate is bad, I tell it to connect anyway, I get the login screen but then I just get a blank white screen. When I try to go into ecp (https://server/ecp) I get the login screen but when I click sign it goes right back to the login screen, with no messages at all including no message about the password being bad. I assume I deleted a certificate I shouldn't have. Can someone tell me what certs I should have, if not certs, what the problem may be.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Whats names does the new certificate include.
Check webapps URLs and make sure they are set to your webmail.
Also create an internal host name for webmail.domain.com in your DNS pointing to your exchange server.
Then try  using https://webmail.domain.com/ecp
Most Valuable Expert 2014
Commented:
Can you start Exchange Management Shell?
If so, run new-exchangecertificate.
That will create a self signed certificate, which should let you back in to Exchange. You can then enable the purchased certificate.
It could be that your purchased certificate is corrupt.

Exchange will need to have some self signed certificates on it for internal purposes, they can be left alone.

Simon.
amscottnycConsultant

Author

Commented:
Hi Sembee,
I was unable to run exchange management shell. I got an error message "The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid...". A google search on the error message lead me to a webpage that said the SSL Certificate was no longer bound to the Exchange Back End website. The page,  http://exchangeserverpro.com/the-winrm-shell-client-cannot-process-the-request/, told how to fix that and I have been able to get to exp and owa. Thanks for the answer.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial