Need assistance in completing the cert enrollment.

I am creating a SAN certificate CSR using the option "Certificate Enrollment wizard with a standalone CA" in this link -

When completing the certificate enrollmet, I use the cert from my 3rd party CA and the file will be mycert.CRT.  May someone give me some example of using the CERTREQ.EXE in the link?

In the name, it says "Servername\CAName".  In my case, it is a  "CertificaeRequest.req" which I assume it is my certificate request file?  But I usually use the extension .txt.  The "CertificateResponse.cer", again, my 3rd party CA they always give me a final cert with a  .zip files which composes of both the .CRT and another intermediate file.7b.  And the "RequestID" - dont know where to get it.

I do not know how to put the above together.  How do I do this in MMC?

Many thanks.
Who is Participating?
MAS (MVE)Connect With a Mentor Technical Department HeadCommented:
.req you can open in notepad and paste in Godaddy portal.
If you open file received from Godaddy (zip file) you can see .cer an .p7b files.  
You have to install in your IIS8 (in windows 2012 server).
Here is the guide from Godaddy.
nav2567Author Commented:

Just want to clarify, so, I can use the below to request a SAN CSR.  Once I have got the zip file from my 3rd party CA, use your want to complete the rest in IIS?  

When I go to the personal store and export the PKF cert, it should contain all the host names of other computers I could use to protect, right?

use the Certificate Enrollment wizard with a standalone CA

In the Certificates snap-in, right-click the Personal folder, point to All Tasks, point to Advanced Operations, and then click Create Custom Request.
This will start the Certificate Enrollment wizard.
Click Next.
Click Proceed without enrollment policy, and then click Next.
In the Template list, click either (No template) CNG key or (No template) Legacy key. (No template) CNG key will ensure that the private key will be generated by the new Cryptography Next Generation key storage provider (KSP) and may not be usable by all applications. To ensure interoperability, click (No template) Legacy key, which will use the CAPI2 cryptographic service provider (CSP).
For Request format, click either PKCS #10 or CMC. PKCS #10 is generally accepted by all CAs. If you will not submit the custom request to a Microsoft standalone CA, check with your CA vendor to determine if the CMC format is supported.
Click Next.
Click the Details arrow, and then click Properties. You will need to configure all the certificate request options so that the issued certificate will be suitable for TLS/SSL.
On the Subject tab:
Because SSL/TLS does not require a Subject name when a SAN extension is included, the Subject name can be empty. If you are using another protocol, verify the certificate requirements. To use an empty Subject name, skip steps 8a and 8b.
In the Subject name area under Type, click Common Name.

In the Subject name area under Value, enter the fully qualified domain name of the server, and then click Add.

In the Alternative name area under Type, click DNS.

In the Alternative name area under Value, enter the fully qualified domain name of the server, and then click Add.

Repeat steps c and d above for each SAN you want to specify.

On the Extensions tab:
Click the Key usage arrow. In the Available options list, click Digital signature, and then click Add. Click Key encipherment, and then click Add.

Click the Extended Key Usage (application policies) arrow. In the Available options list, click Server Authentication and Client Authentication, and then click Add.

On the Private Key tab:
Click the Cryptographic Service Provider arrow, and verify the following:

If you selected CNG key in step 4 above, the RSA, Microsoft Software Key Storage Provider is enabled.

If you select Legacy key in step 4 above, the Microsoft RSA SChannel Cryptographic Provider is enabled.

Click the Key options arrow. In the Key size list, select a key size. If desired, select the Make private key exportable check box. Do not select either the Allow private key to be archived or Strong private key protection check box.

Click the Select Hash Algorithm arrow. In the Hash Algorithm list, select the desired hash algorithm.

The specified hash algorithm is used in the request. You must specify a hash algorithm that is compatible with your client computer and CA.
Click the Key permissions arrow. If the application or service runs as Network Service, grant the Network Service account Read permission. If the application or service that will use this certificate runs as Local System, no permissions changes are required.

Click OK.
Click Next.
Enter a path and file name indicating where the request file will be saved.
Select the Base 64 format.
Click Finish.
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.

All Courses

From novice to tech pro — start learning today.