What AD CS does on its own
Active Directory Certificate Services (AD CS) issues certificates from your own internal CA. Domain-joined Windows computers and users can get and renew certificates without anyone acting, through autoenrollment:
- A certificate template allows autoenrollment, and the computers or groups that should receive it have the Read, Enroll and Autoenroll permissions on it.
- A Group Policy setting, Certificate Services Client - Auto-Enrollment, is enabled with renewal of expired certificates and updating of pending certificates turned on.
- The Windows certificate client checks every eight hours and enrols or renews as needed.
When renewal happens
Two template settings control renewal: the validity period and the renewal period. Microsoft explains in approval required for certificate renewals with autoenrollment that a certificate is renewed once 80 percent of its validity has passed or it is inside the renewal period. For normal renewal the renewal period should be more than eight hours and less than 20 percent of the validity period. Outside those limits, Windows sends a new enrolment request instead of a renewal, which may need CA manager approval.
You can read a template’s values with certutil -dstemplate <TemplateName>.
Where autoenrollment stops
- Non-Windows systems. Linux servers, appliances, load balancers and Kubernetes cannot autoenroll. Their internal certificates are often requested once by hand and then forgotten.
- Getting the certificate into use. Autoenrollment renews the certificate in the store. IIS moves its bindings only if Certificate Rebind is enabled, and other services such as SQL Server or RDP may need their own configuration.
- Visibility. Each computer renews on its own, and the CA database is not a simple list of what is deployed where, a gap we describe in why certificate tracking spreadsheets fail.
How clm.mt handles AD CS
clm.mt requests certificates from AD CS through a domain-joined Windows agent with certreq, using a template the agent’s computer account may enrol for. It renews them with a new key, deploys them to targets such as IIS, checks the served certificate and can undo a failed rollout. Requests generated on appliances are not supported.
clm.mt status
Supported for Microsoft AD CS. Enterprise CA lab tested issuance, renewal, IIS deployment and recovery. Requires a domain-joined Windows agent; test your CA and template first. See the integrations board for every tested scope, and the documentation to plan a pilot.
Other platform guides
- AWS load balancer certificate renewal with ACM
- Azure Key Vault certificate auto renewal, and when it does not happen
- F5 BIG-IP SSL certificate renewal automation
- FortiGate ACME certificates and automatic renewal
- IIS SSL certificate auto renewal on Windows Server
- Kubernetes certificate management and TLS Secret renewal
- NetScaler ADC SSL certificate renewal and update
- NGINX SSL certificate auto renewal with ACME
- Palo Alto firewall certificate renewal automation