Solved

Access Exchange 2013

Posted on 2014-02-27
3
409 Views
Last Modified: 2014-02-28
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.
0
Comment
Question by:amscottnyc
3 Comments
 
LVL 23

Expert Comment

by:Malli Boppe
ID: 39893606
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
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39895644
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
 

Author Comment

by:amscottnyc
ID: 39895980
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

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now