For a lab/teaching environment, we need to set up a Windows 2012R2 machine as a domain controller, with LDAPS enabled on 636. As we also need ADCS installed, we have just let ADCS auto generate the cert on the LDAPS service.
This is one of the advantages of an Active Directory domain with an Enterprise CA; you can deploy certificates automatically using a process known as autoenrollment. This greatly reduces the amount of administrative overhead required to deploy certificates to your clients; and all you need for this is a GPO linked to your domain or an OU configured with the autoenroll policy. Mar 15, 2016 Microsoft Active Directory Certificate Services AD CS provides a platform for issuing and managing public key infrastructure PKI certificates.On top of securing application and HTTP traffic the certificates that AD CS provides can be used for authentication of computer, user, or device accounts on a.
However, the cert expires in one year. Is there a mechanism where the cert auto renews somehow when a year is up?
I can't seem to find an answer to this.
Or should I manually set up a cert like this with a more distant expire time?
In Active Directory Certificate Services it is possible to configure certificates to autorenew prior to certificate expiration. This functionality (which is shipped with every Windows box) is called certificate autoenrollment.
Whether you're searching for a custom lightsaber blade to call your own or a Star Wars FX Lightsaber replica conversion, UltraSabers is ready to bring you the most 'elegant weapon, for a civilized age.' CUSTOM LIGHTSABERS FROM ULTRA SABERS: THE GALAXY'S GREATEST LIGHTSABER ARSENALConstruct a Lightsaber from millions of combinations to find your true calling as a Jedi Master!Ultra Sabers is known throughout the galaxy for our high-end Lightsabers.
Here is the link that describes how to enable autoenrollment functionality (which is disabled by default): https://technet.microsoft.com/en-us/library/cc770546.aspx
in your case, it is sufficient to use a certificate based on Kerberos Authentication certificate template (which is compatible with LDAPS) and enable autoenrollment GPO. Certificate template already contains Autoenroll permissions for Enterprise Domain Controllers global group. If GPO is configured properly, domain controllers will renew their LDAPS certificates after 80% of existing certificate's lifespan.
and here is a link that describes what is autoenrollment and how it works in details (for reference): https://technet.microsoft.com/en-us/library/cc778954(v=ws.10).aspx
Crypt32Crypt32I have this AD domain where a Windows Server 2003 SP2 Enterprise Root Certification Authority is operational, and certificate autoenrollment is enabled both for users and computers; all fine and good, every domain-joined computer automatically gets a Computer certificate issued. There are also two Windows Server 2003 SP2 domain controllers, which instead received a Domain Controller certificate; all fine and good, again.
Then I got a Windows Server 2008 R2 SP1 member server, which had already automatically enrolled a Computer certificate, and promoted it to domain controller. It didn't get any new one after the promotion, and no errors are logged anywhere: it looks like it simply decided that, having already a working certificate, it didn't need a new one.
What I want to know is:
I tried revoking the existing certificate and rebooting the new DC; nothing happened.Then I removed the existing certificate from the DC's local store and rebooted it again; nothing heppened this time, too.
I turned on autoenrollment logging, and I found there actually are some errors.. when the new DC tries to enroll a certificate, it logs a bunch of errors:
Try certutil -pulse
- this should check for templates the system has permission in, and enroll them. It should have no problem grabbing the certificate, as long as there's nothing crazy going on in the permissions settings on the template.
You'll definitely want to have your DCs have a Domain Controller-style certificate (Domain Controller
is the old one; Domain Controller Authentication
then Kerberos Authentication
supersede it; if your CA is running enterprise edition, then consider switching to the newer Kerberos template) - while a lot of the functions that it satisfies will be handled by a Computer certificate, some of the DC-specific stuff like smart card authentication, the LDAP/SSL listener (I believe?), and with the newer Kerberos certificate, strong KDC validation, need the special certificate.
Did you try removing the certificate from the server itself, instead of simply publishing the revocation to the revocation list on the CA? Then have the server enroll (request a certificate) again?
Here's some info on the certificates:http://technet.microsoft.com/en-us/library/cc787009(WS.10).aspx
mbrownnyc