Custom requests (and IIS manager) are designed to be used to request 3rd party certs.
Configure your (custom) CA enrollment security groups and set the security on your templates.
Configure your templates to set the defaults and required info
for each template.
Then use the Certificates mmc to enroll the certs using the CA
templates.
Even better, use GPO to autoenroll many of the certificates for users and computers.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2BjGzLEoc47O59WbuiNCRzP0air2z-v3Eh0%2BhKCi-6X1qw%40mail.gmail.com.
Custom requests (and IIS manager) are designed to be used to request 3rd party certs.
Configure your (custom) CA enrollment security groups and set the security on your templates.
Configure your templates to set the defaults and required info for each template.
Then use the Certificates mmc to enroll the certs using the CA templates.
Even better, use GPO to autoenroll many of the certificates for users and computers.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/a4be5550-a507-60c9-8d67-d8be06a76f45%40doomsdaypig.com.
This is going to be mostly off the top of my head, so there might be some errors. Also keep in mind your environment may need different settings that what I chose:
Now go to your web server and use the Certificates MMC for the local machine to request a new cert using AD Enrollment Policy. Since the computer account now has permission to enroll a certificate, you should see that template as available. The list of available templates will be a combination of what is available to the user and the computer accounts.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2BjcOXLXKn%2Bd%3DfDVgC%3DeO14OBALJCSU8xxxX9SAewME%3DHw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/23152859-7433-7b63-26dd-cc246033ad57%40doomsdaypig.com.
This is going to be mostly off the top of my head, so there might be some errors. Also keep in mind your environment may need different settings that what I chose:
- Create an AD group, such as "CA-WebServers" and add the computer objects of all of your web servers
- In the "Certificate Templates" mmc, duplicate the "Web Server" template and name it according to your naming standard.
- I use a company abbreviation prefix to identify all of our templates
- On the "General" tab, I like to check "Publish to Active Directory" and "Do not automatically reenroll". This will add the cert to the AD object.
- Click "Enroll". There may be a screen or two after this, read them and click through.
- You should now have a certificate signed by the CA and installed on the computer.
- Click "Enroll". There may be a screen or two after this, read them and click through.
It is possible that you may want to grant "Autoenrollment" for the Web Server AD group on your certificate template.
I believe Enroll will allow you to request that certificate type, while autoenroll will automatically approve it. I tend to not use autoenrollment on very many templates because I use GPO's to enable autoenrollment and I don't want those certs on all servers or I need to customize the cert.
Since the Web Server template requires additional information, I don't believe the server would autoenroll based on the GPO, but just to be sure. . .
Bear in mind that the Certificate Manager mmc just manages the various certificate stores. You will still need to assign the certificate in IIS, but it should now be visible as an available option.
Back in the dark ages, IIS manager would show just the subject
name of a certificate, so if you had several re-issued certs, you
would not be able to tell one from the other as they all had the
same subject name. Then I discovered that if the "Friendly Name"
were added to the certificate, IIS would display that in place of
the subject. That's why I like to always add a friendly name with
a date. I think more modern IIS mangers provide additional
details when selecting certs, but old habits die hard.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2BgUyWgxQeajXMPPUzo8juNoNZ%2BBByn56%3DSg8yXo9%3Db_Bw%40mail.gmail.com.
It is possible that you may want to grant "Autoenrollment" for the Web Server AD group on your certificate template.
I believe Enroll will allow you to request that certificate type, while autoenroll will automatically approve it. I tend to not use autoenrollment on very many templates because I use GPO's to enable autoenrollment and I don't want those certs on all servers or I need to customize the cert.
Since the Web Server template requires additional information, I don't believe the server would autoenroll based on the GPO, but just to be sure. . .
Bear in mind that the Certificate Manager mmc just manages the various certificate stores. You will still need to assign the certificate in IIS, but it should now be visible as an available option.
It has been a while, but I seem to remember there was an option like "complete certificate request" that would go and pick up the approved cert and install it in the Personal certificate store.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2BgGoTjhhx8XK0ux8s0wsEf4d-Si3iNakGdTz-LhoCrV3A%40mail.gmail.com.
It has been a while, but I seem to remember there was an option like "complete certificate request" that would go and pick up the approved cert and install it in the Personal certificate store.
As long as the machine/user has permissions, you can retrieve the certificate form the Sub CA via command line using certreq:
certreq –retrieve <Request ID> <Output Path>
Example: certreq –retrieve 21 C:\CertName.cer
If you want to import the certificate
certreq –accept <Cert Path>
Example: certreq –accept C:\CertName.cer
Be wary of the above commands if Outlook modified the hyphens.
From: ntsys...@googlegroups.com <ntsys...@googlegroups.com>
On Behalf Of Michael Leone
Sent: Wednesday, March 4, 2020 2:19 PM
To: NTSysAdmin <ntsys...@googlegroups.com>
Subject: Re: [ntsysadmin] Re: MS CA and Subject Alternate Names
|
ATTENTION: This email came from an external sender. If you don't recognize the source and it has unexpected or suspicious links or attachments, click the "Report Email" button (above) or send to: cyberalert @ chomp.org. |
On Wed, Mar 4, 2020 at 4:57 PM Dennis Pinckard <ntsys...@doomsdaypig.com> wrote:
It has been a while, but I seem to remember there was an option like "complete certificate request" that would go and pick up the approved cert and install it in the Personal certificate store.
Don't recall seeing that, but I'll look again tomorrow.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2Bh7uMsnxOVBNMrx0Qa6CZsR4pGLp8OkBaEktimhpbftTQ%40mail.gmail.com.
As long as the machine/user has permissions, you can retrieve the certificate form the Sub CA via command line using certreq:
certreq –retrieve <Request ID> <Output Path>
Example: certreq –retrieve 21 C:\CertName.cer
If you want to import the certificate
certreq –accept <Cert Path>
Example: certreq –accept C:\CertName.cer