Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, November 13, 2019 8:44 AM
Hi,
I wanted to ask something, regarding Exchange Server 2016 - OnPremises.
My Server is running on Windows Server 2016.
I installed Exchange Server 2016 OnPremises, but it's only an offline server. I don't have Public IP yet to update my DNS records in my domain, but I already tried installing the Certificate I bought in GoDaddy.
After I install the certificate and restarted the server, I cannot access ECP/OWA anymore, even in localhost.
Can someone Help me?
PS: Planning to reinstall the exchange, but I don't know how.
Thanks in advance.
All replies (6)
Wednesday, November 13, 2019 8:59 AM ✅Answered
Hi
Login to IIS and check your bindings for the default and backend sites and make sure your new SSL cert is selected.
Do an IISreset afterwards
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Thursday, November 14, 2019 9:01 AM ✅Answered | 2 votes
Hi jbnavarro,
The cause of your problem may be the bindings on Default Web Site and Exchange Back End don’t have the correct certificate assigned. I have met the same issue, hope the solutions will help you:
- Open IIS Manager, find Sites-Default Web Site, click bindings and double-click https (with a * in IP address), select the certificate you bought in SSL certificate.
- Select Exchange Back End, click bindings and double-click https (with a * in IP address), select the certificate you bought in SSL certificate.
- Run Windows Power Shell as administrator and type in iisreset /start.
Regards,
Eric Yin
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, November 13, 2019 9:06 AM
Hello,
Did you install the certificate through EAC or bind it manually in IIS? The former is the correct procedure.
Generally with Exchange, although it relies on IIS it arranges all the necessary bindings automatically and you should not do any manual configs on IIS. You should always use exchange admin tools for certificate configuration.
What error do you receive when you browse to owa?
Thanks
Wednesday, November 13, 2019 10:07 AM
Check IIS for SSL bindings,
https://support.microsoft.com/en-gb/help/2971270/blank-page-after-login-exchange-eac-owa-ecp
Checked assigned services to certificate,
https://practical365.com/exchange-server/exchange-2013-assign-ssl-certificate-to-services/
/en-us/exchange/architecture/client-access/assign-certificates-to-services?view=exchserver-2019
Tuesday, November 19, 2019 9:18 AM
Hi,
I am writing here to confirm with you how the thing going now?
If you need further help, please provide more detailed information, so that we can give more appropriate suggestions.
Just checking in to see if above information was helpful. Please let us know if you would like further assistance.
Regards,
Eric Yin
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, December 3, 2019 9:20 AM
Hi, I'm here to confirm with you if your issue has been resolved. If the problem is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Regards,
Eric Yin
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].