Hi everyone, I was using Exchange Server 2007 and i am using Third party CA with the following SAN names
mail.mydomain.com, mydomain.com, www.mydomain.com, legacy.mydomain.com, autodiscover.mydomain.com.
I did the transition to Exchange Server 2013 and i did import the certificate successfully and i have never used this
certificate for my company website.
When i open owa i can see the san names under certificates, and when i export this certificate from exchange server and import it in my webserver i am facing issues in IIS. Now i needed to generate a new CSR should i generate the csr
from my exchange server or from the webserver. I am confused here.(Please do refer the attachment for the error i am facing in IIS on webserver when i import the cert)
What do you mean you're "facing some issues"?
When you exported the certificate, did you export the private key? How did you originally create the CSR? If you used the Exchange 2010 or 2013 certificate wizards to create the CSR, the private key should be exportable. If you use some other method to request the certificate, that's an option you must specify.
We can help more if you tell us precisely and completely what you've done, exactly what happens, and what you're trying to do.
Using DigiCert Utility www.digicert.com/util
Should i try the below article, i did not try this
https://www.sslshopper.com/move-or-copy-an-ssl-certificate-from-a-windows-server-to-another-windows-server.html
Hi Rising,
Thank you for your question.
If we have import certificate into Exchange server, then we need not to import it into IIS in terms of Exchange service(Eg: OWA). Because you have enabled certificate on Exchange server, so you have generate a new CSR for other services in IIS, we could generate a CSR by the following link:
https://technet.microsoft.com/en-us/library/cc732230(v=ws.10).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
This topic is archived. No further replies will be accepted.
Other recent topics
