windows server 2012

I purchased SSL SAN Certificate needed to secure Internet traffic to  2 websites
The IIS is not configured yet –
Otherwise do you have a recommended procedure to follow on Windows 2012 to create a certificate request for a SAN certificate for those two DNS names please?
 
Each website will use a separate IP address
 
We have added DNS A records to external DNS zone for this website
how should I install on windows 2012 server
pramod1Asked:
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.

btanExec ConsultantCommented:
Actually you can create from Win2012 an CSR to get the request to submit to CA (of your choice to get the needed SAN certificate. https://technet.microsoft.com/en-us/library/ff625722(v=ws.10).aspx
Since you already has that purchase, I assumed you have submitted the CSR as stated as the cert will then complete the CSR as per shared in https://www.digicert.com/ssl-certificate-installation-microsoft-iis-8.htm
Specifically, will need SNI e.g. <IPaddress><port> to bind to each different domain using the same cert. This is also included in the prev link. Note SNI is available only on IIS 8. Also note this
3 types of SSL bindings:
IP:Port – Legacy SSL binding.
Hostname:Port – SSL binding using SNI. (new in IIS 8)
Central Certificate Store – SSL binding using Central Certificate Store. I will discuss this in detail in my next blog. (new in IIS 8)

There is a small problem that the administrators have to take care of while configuring SSL bindings to use SNI. If a non-SNI compliant browser connects to a site on which SNI is enforced, as I mentioned earlier the SSL handshake would fail.
 
To tackle this there is a fall-back mechanism in IIS where the it would try to determine a binding with the combination of IP:Port, if this is not present, then the SSL handshake fails. For this the IIS admin has to configure a binding which neither uses SNI nor CCS.
On SNI - http://blogs.msdn.com/b/kaushal/archive/2012/09/04/server-name-indication-sni-in-iis-8-windows-server-2012.aspx

Do make sure the CA and Intermediate CA are stored respective certstore e.g. Trusted Root cert store  for CA cert, and likewise for Intermediate CA into its Intermediate certstore.

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
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
SSL / HTTPS

From novice to tech pro — start learning today.