Access Exchange 2013

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.
amscottnycAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Malli BoppeCommented:
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
0
Simon Butler (Sembee)ConsultantCommented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
amscottnycAuthor 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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.