Platform: Windows Server 2019, 2022 and 2025, with the version and hosting restrictions described below.
Treat the template as an issuance policy
A certificate template determines more than a display name. It controls who can request a certificate, which identities and purposes appear, how keys are generated and whether approval or automatic enrollment is permitted. A weak template can issue credentials far more powerful than the administrator intended. Start with the application requirement and its trust consequences before duplicating anything.
In a managed Netcloud24 PKI, template preparation is handled by authorised operators under the organisation’s issuance policy. Application owners supply required names, purposes and renewal expectations; they should not have to edit forest-wide template objects themselves. This guide follows a restricted pilot template through design, AD replication, CA publication and verification.
Separate the three meanings of publication
The template object lives in Active Directory. Adding it to a CA’s enabled list allows that CA to issue from it. Publishing an issued certificate into an AD object is yet another setting. Creating the first object does not automatically complete either of the other operations. Keep those states distinct when a requester cannot see a new template.
Record both display name and template short name. Commands and request attributes often use the short name, which can differ from the friendly text shown in the console. Give a custom template a distinct, stable purpose rather than reusing an ambiguous historical name.
Changes can affect a forest-wide issuance policy, not just one server. Review permissions to modify the template as well as permissions to enroll from it. A group that can rewrite authentication-template settings can potentially alter the credential boundary even if it rarely requests a certificate itself.
Choose a starting point and compatible cryptography
Open Certificate Templates through the CA console or the template-management snap-in and duplicate the built-in or approved custom template closest to the real purpose. Configure the new object before accepting the dialog. Do not edit a shared production template just to run an isolated pilot.
Set compatibility to the oldest CA and recipient types that must use it. The latest labels available in the template compatibility interface can remain Windows Server 2016 and Windows 10/Server 2016 even when the host runs Windows Server 2025; do not invent a missing 2025 option. Compatibility is a feature constraint, not a reason to choose unnecessarily old cryptography.
Select provider, key algorithm, size and hash supported by the application and key-protection policy. Decide whether the private key may be exported. Exportability, enrollment-agent purposes, code signing and authentication warrant extra review because compromise has consequences beyond an ordinary TLS endpoint. Keep key usage and application policies limited to the documented use case.
Control identity and approval explicitly
Prefer building user or computer identity from AD where the scenario permits it. Supply in the request is necessary for some web-service names, but it lets the requester provide identity information. Do not combine unrestricted requester-supplied subjects with broad authentication enrollment. Narrow the requesting group and use the approval or validation process appropriate to the service.
Define validity and renewal periods in relation to the issuing CA’s remaining lifetime and operational renewal window. Decide whether a fresh key is required at renewal, and whether manager approval or authorised signatures are needed. These choices can make a template unsuitable for unattended auto-enrollment; do not enable Autoenroll without checking the whole issuance path.
For AD authentication certificates, account for current strong certificate mapping and the intended SID or approved explicit mapping mechanism. A certificate with a familiar UPN is not automatically sufficient under current enforcement. Align the template with the actual authentication design rather than relying on legacy weak-name behaviour.
Set Read, Enroll and Autoenroll separately
On Security, give the small pilot group Read and Enroll. Grant Autoenroll only when the pilot is specifically intended to run automatically. Remove unnecessary enrollment rights after reviewing inherited or broad groups. Template administration rights should remain with its approved owners.
If Authenticated Users is removed from the template ACL, ensure each issuing CA computer account retains Read through another applicable entry. The CA must be able to read the AD template to use it. Removing broad read without adding the correct CA readers can make a seemingly secure template unavailable for issuance.
Do not resolve discovery failure by granting Domain Users broad enrollment. Check the requester’s actual account, group token, template read access, CA read access and AD replication first. A correct ACL change may require a fresh sign-in or time for directory convergence before a client sees it.
Enable the pilot on the intended issuing CA
After saving the template and allowing directory replication, add its short name to the correct CA’s issuance list. The example uses ServiceDeskTLS as an illustrative name. Inspect the list first and avoid publishing the template to every CA without a reason.
Get-CATemplate
Add-CATemplate -Name 'ServiceDeskTLS'
Get-CATemplate | Where-Object Name -eq 'ServiceDeskTLS'The Certification Authority console provides the equivalent Certificate Templates, New, Certificate Template to Issue workflow. This publication does not issue a certificate immediately and does not grant a requester missing template permissions. Keep the pilot narrow while testing, and retain the previous CA-template list for recovery evidence.
Inspect the issued result and a denied request
Request a disposable certificate from an authorised pilot context using the intended enrollment method. Inspect the actual subject, SAN, purposes, key provider, validity, chain and private-key location. Verify the application can use it and the embedded AIA/CDP locations work. A template name appearing in a list is not proof of correct issued extensions.
Also confirm that an unauthorised identity cannot enroll. Where approval is required, verify the request remains pending rather than silently issuing. Record request identifiers and CA disposition evidence. Test renewal and supersedence behaviour separately if those features form part of the rollout; replacing a template does not instantly revoke certificates already issued from its predecessor.
Retire without confusing issuance control and revocation
Removing a template from one CA’s issuance list stops future use there but leaves the AD template object and existing certificates. Use the specific name when previewing removal; do not use an all-templates operation to undo one pilot.
Remove-CATemplate -Name 'ServiceDeskTLS' -WhatIf
# After reviewing the single-template removal:
# Remove-CATemplate -Name 'ServiceDeskTLS'Deleting the AD object has wider consequences and should follow inventory and retirement planning. Existing certificates remain valid until expiry or a separate revocation decision. Keep the template owner, enrollment groups, CA list, purpose and renewal policy documented. A managed PKI stays understandable when each template has a narrow boundary and a verifiable issued result.
Establishing an AD-integrated root certification authority deliberately
Establish an enterprise root CA only after deciding trust, keys, publication and ownership, then validate separate issuance and revocation…
Separating an offline root from day-to-day certificate issuance
Separate offline root signing from enterprise issuance, prepare the standalone trust anchor, review the subordinate request, validate…
Rolling out certificate auto-enrollment with a measurable pilot
Roll out certificate auto-enrollment through a narrow user or computer pilot, align template and GPO eligibility, inspect issued keys and…
Enrolling an enterprise certificate for the actual web-service name
Enroll a machine-held enterprise TLS certificate for the real service DNS names, respect template approval and key policy, inspect the…
Making a certificate revocation reach the relying application
Carry one approved certificate revocation from issuer and serial verification through reason selection, CRL publication, endpoint delivery…