Applies to: Windows Server 2019, Windows Server 2022, and Windows Server 2025.
Certificate autoenrollment issues and renews approved user or computer certificates through Active Directory policy.
Prerequisites
- Administrative access to the affected servers.
- A verified backup and approved maintenance window.
- A pilot system for testing before production rollout.
Step-by-step procedure
- Publish a controlled certificate template.
- Grant Enroll and Autoenroll only to the target group.
- Enable autoenrollment in a scoped GPO.
- Refresh policy on one pilot computer.
Commands
gpupdate /force
certutil -pulse
Get-ChildItem Cert:\LocalMachine\My | Select Subject,NotAfter,Thumbprint
gpresult /h C:\Temp\autoenrollment.htmlVerification
The pilot receives the expected certificate and autoenrollment events show a successful request.
Rollback
Disable the GPO setting and remove template permissions; revoke mistakenly issued certificates if required.
Security and operations
- Use least privilege and document all production changes.
- Replace example addresses and names with approved values.
- Review relevant Windows event logs after implementation.
Join the template, policy and trust requirements
Autoenrollment succeeds only when the certificate template, enrollment permissions, CA publication and client policy agree. A policy refresh alone cannot make a template available to an account that lacks Enroll or Autoenroll permissions. Check those permissions for the intended user or computer group instead of granting broad access to work around a failed request.
Keep computer and user enrollment distinct. The LocalMachine certificate store is appropriate for many machine services, while a user certificate may belong to CurrentUser. Test as a representative member of the target group and inspect the relevant certificate-enrollment event log when a request does not appear.
Review the issued certificate’s subject, alternative names, intended purposes, validity and chain. A certificate existing in a store does not establish that IIS or another application is using it. Binding or selecting it for a service can be a separate step.
For renewal, check the template’s renewal behaviour and whether the application automatically adopts a replacement certificate. Preserve the old working certificate and binding until the new one is verified. Restrict who can change subject names or request authentication-capable certificates; template design is part of the domain security boundary.
Related resources
Canadian Windows VPS and RDS hosting is available from managed Windows VPS hosting. Also review the official Microsoft Windows Server documentation.