One way:

1. Open Certificates Snap-in from Remote Management computer.
2. Connect to remote computers Machine store (Core-IIS).
3. Right click the Personal Store object (folder) -> All tasks -> Advanced Operations -> Create Custom Request…
4. Pick Enrollment Policy (Custom Request for 3rd Party CAs) I have internal CA, So I picked AD Enrollment Policy.
5. Template – Web Server | PKCS #10
6. Click Details to expand the AD EP – Web Server template properties (Make sure you enter a common name of the host name of the server, and SAN names for any sites you plan to use this certificate for)
7. Save the Request file.
8. A) Navigate to your CA sign the certificate. (In my case I have web enrollment, so I simply navigated to my CA web page and picked custom request, then opened the request file in notepad and copied the request contents into the text box of the web request, after issued, saved a copy in Base64 format)
   OR
   B) Open the CA snap-in, Right click the CA -> All tasks -> Submit a new Request, Save the issued cert file.
9. Right click the Personal store on the remote Certificates Snap-in again, select All Tasks -> Import.
10. Your Certificate is ready for use on the Website binding section of IIS.

Second way:

1. Creating an INF file to set the certificate properties
   

   [Version] 
   Signature="$Windows NT$"
   
   [NewRequest] 
   Subject = "CN=SERVER.CONTOSO.COM"   ; For a wildcard use "CN=*.CONTOSO.COM" for example 
   ; For an empty subject use the following line instead or remove the Subject line entierely 
   ; Subject = 
   Exportable = FALSE                  ; Private key is not exportable 
   KeyLength = 2048                    ; Common key sizes: 512, 1024, 2048, 4096, 8192, 16384 
   KeySpec = 1                         ; AT_KEYEXCHANGE 
   KeyUsage = 0xA0                     ; Digital Signature, Key Encipherment 
   MachineKeySet = True                ; The key belongs to the local computer account 
   ProviderName = "Microsoft RSA SChannel Cryptographic Provider" 
   ProviderType = 12 
   SMIME = FALSE 
   RequestType = CMC
   
   ; At least certreq.exe shipping with Windows Vista/Server 2008 is required to interpret the [Strings] and [Extensions] sections below
   
   [Strings] 
   szOID_SUBJECT_ALT_NAME2 = "2.5.29.17" 
   szOID_ENHANCED_KEY_USAGE = "2.5.29.37" 
   szOID_PKIX_KP_SERVER_AUTH = "1.3.6.1.5.5.7.3.1" 
   szOID_PKIX_KP_CLIENT_AUTH = "1.3.6.1.5.5.7.3.2"
   
   [Extensions] 
   %szOID_SUBJECT_ALT_NAME2% = "{text}dns=computer1.contoso.com&dns=computer2.contoso.com" 
   %szOID_ENHANCED_KEY_USAGE% = "{text}%szOID_PKIX_KP_SERVER_AUTH%,%szOID_PKIX_KP_CLIENT_AUTH%"
   
   [RequestAttributes] 
   CertificateTemplate= WebServer

2. Compiling the INF file into a REQ fileThe following command-line command will generate key material and turn the INF file into a certificate request.

   certreq –new ssl.inf ssl.req

   Once the certificate request was created you can verify the request with the following command:

   certutil ssl.req

3. Submitting the REQ file to the CA: if the CA is reachable via RPC over the network, use the following command to submit the certificate request to the CA:

   certreq –submit ssl.req

   You will get a selection dialog to select the CA from. If the CA is configured to issue certificates based on the template settings, the CA may issue the certificate immediately.If RPC traffic is not allowed between the computer where the certificate request was created and the CA, transfer the certificate request to the CA and perform the above command locally at the CA.

   If the certificate template name was not specified in the certificate request above, you can specify it as part of the submission command:

   certreq -attrib "CertificateTemplate:webserver" –submit ssl.req

4. Installing the certificate at the IIS or ISA computer: Once the certificate was issued and is available as a file on the target computer, use the following command to install it.

   certreq –accept ssl.cer

   The installation actually puts the certificate into the computer’s personal store, links it with the key material created in step #1 and builds the certificate property. The certificate property stores information such as the friendly name which is not part of a certificate.After performing steps 1 to 4 the certificate will show up in the IIS or ISA management interface and can be bound to a web site or a SSL listener.

*UPDATE* Powershell – I love PowerShell. If you’d like some more automated scripts to help with such a task. Please see this Blog Post by Adam Bertram in which he provides a link to his gitHub page with the required scripts.

Thanks Adam for this fine work. I might just make a pull request to make some changes/tweaks to the scripts. Amazing the neat little tricks I learn from reading other peoples code. 🙂