Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 89
  • Last Modified:

Exchange 2013 ECP SSL error

Hi all,

I've run into a bit of trouble with an Exchange 2013 installation. The server had issues with OWA which I thought where connected with certificates that might not be correctly configured. To fix this I used ECP to register a new, self-signed certificate from scratch. I somehow connected this to IIS (for ECP and OWA) and set it up to need SSL. Now I've run into the problem that whenever I try and open ECP I get an 403.4 error because the http-url forwards or is looking for the https version.

I didnt setup or install the environment so what I basically am looking for is a direction to reset certificates in Exchange back to defaults, so I can use ECP to try and fix everything again. Any suggestions are welcome :D.

Greetings
Martijn
0
Martijn Snel
Asked:
Martijn Snel
Advertise Here
  • 2
1 Solution
 
Todd NelsonSystems EngineerCommented:
Do you get an error when you open EMS?  Is there a certificate bound to the Default Web Site in IIS?
0
 
Martijn SnelICT AdvisorAuthor Commented:
Hi. Yes.. i get the same type of error (either its a 403.4 > when I go to ECP or a blanc page when I go to OWA or any other subpage). There is a binding in IIS to a certificate on the default website (Exchange Back End), I'm thinking that something went wrong (or I screwed up) and the wrong type of setting for SSL. I'm basically look for a way to bypass SSL / settings, or reset them completly so I can at least access ECP.
0
 
Simon Butler (Sembee)ConsultantCommented:
Use EMS and the command enable-exchangecertificate.
That will allow you to assign the correct certificate to the IIS role.

You can do everything through EMS, so lack of accept to ECP shouldn't be a problem to get the server fixed.
0
 
Martijn SnelICT AdvisorAuthor Commented:
Hi, Finally seems that I have fixed the issue; I have reset all certifcates (made a new self-signed certificate) and to get IIS working correctly again used the EMS with Remove-OwaVirtualDirectory and Remove-ECPVirtualDirectory commands to repair everything.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Learn More
  • 2
Advertise Here
Tackle projects and never again get stuck behind a technical roadblock.
Join Now