Platform: Windows Server 2019, 2022 and 2025, with the version and hosting restrictions described below.
Decide whether an online root is the right trust anchor
An enterprise root CA is not simply another application service. Its signing key anchors trust for certificates issued under it, and its AD integration supports template-driven issuance. Keeping that root online can simplify a small PKI, but exposes the root key to the operational environment. A two-tier design with an offline standalone root and an enterprise issuing CA offers a different security and maintenance model.
Netcloud24 can prepare the agreed PKI as part of a managed environment, but the organisation must still own its trust, issuance and recovery policies. This article describes the authorised administrator’s deployment of a deliberately selected new enterprise root. It is not a repair for an existing CA, a migration shortcut or a reason to generate a replacement root whenever enrollment fails.
Write the long-lived decisions before generating a key
Choose a stable CA common name, key algorithm and protection method, certificate validity, publication names and renewal strategy. The CA name is separate from the computer name. Recreating a friendly name does not recreate a signing key or the trust of an old certificate. Finalise the server identity before installation and avoid later casual renaming.
Determine who may administer the CA, manage certificates, change templates and recover keys. Keep the CA on a dedicated member server rather than a domain controller or public application host. Select HSM protection where the security requirements call for it and validate that provider’s availability and recovery process before installation.
Plan CRL and AIA retrieval from every relying network. A stable publication hostname can outlive the CA computer. Clients may need revocation data before a VPN connects or outside the domain. Changing URLs after issuance does not alter the URLs inside older certificates, so publication choices belong before the first production request.
Check directory and host readiness
Use a supported, patched domain member with healthy DNS, time and directory access. Enterprise CA configuration requires appropriate AD/forest authority as well as local administration. Use the approved installation identity and then separate routine operating roles rather than retaining broad privilege as the everyday process.
Get-ComputerInfo | Select-Object CsName,CsDomain,WindowsProductName,OsBuildNumber
Get-WindowsFeature ADCS-Cert-Authority
Get-Volume | Select-Object DriveLetter,FileSystemLabel,SizeRemaining,Size
Resolve-DnsName 'corp.example'Verify the data location for the CA database and logs and its protection. If CAPolicy.inf forms part of the design, put the reviewed file in the Windows directory before CA configuration. Do not copy a file intended for a different hierarchy without understanding its policies and extensions. Preserve a recoverable host baseline, while recognising that later CA recovery also needs its key and database identity.
Install only the certification-authority components
Install the CA role service and management tools. Web Enrollment, online responders and enrollment web services are additional functions with their own exposure and authentication implications; none should be added merely because the wizard offers it.
Install-WindowsFeature ADCS-Cert-Authority -IncludeManagementTools
$rootSettings = @{
CAType = 'EnterpriseRootCA'
CACommonName = 'Example Organisation Trust CA'
CryptoProviderName = 'RSA#Microsoft Software Key Storage Provider'
KeyLength = 4096
HashAlgorithmName = 'SHA256'
ValidityPeriod = 'Years'
ValidityPeriodUnits = 12
DatabaseDirectory = 'E:\PKI\Database'
LogDirectory = 'E:\PKI\Logs'
}
Install-AdcsCertificationAuthority @rootSettingsRSA 4096, SHA-256 and twelve years are illustrative design values, not universal policy. Confirm interoperability and lifecycle requirements first. Review the installation confirmation rather than suppressing it by default. An existing key, database or directory-object conflict is a reason to stop and investigate, not to enable overwrite switches that could destroy a prior CA identity.
Complete publication and issuance policy before onboarding users
Review CA properties and the CDP/AIA extensions, including which entries are publication paths and which are embedded retrieval locations. Configure the agreed endpoints, publish the root certificate and current CRL, and verify the files served from each retrieval location. Creating a local CRL does not prove a web endpoint received it.
Get-Service CertSvc
certutil -getreg CA\CRLPublicationURLs
certutil -getreg CA\CACertPublicationURLs
certutil -CRL
# Use an existing protected evidence directory:
certutil -ca.cert 'C:\PKI-Evidence\RootCertificate.cer'Review the CA’s enabled templates and their enrollment permissions before production issuance. Limit publication to approved purposes and groups. Broad authentication templates combined with requester-supplied identities can create powerful unintended credentials. Issuance policy should be an explicit security decision, not whatever template list happened to appear after installation.
Validate trust, issuance and revocation as separate outcomes
Confirm the CA responds, inspect its root certificate and verify trust distribution on intended clients. Domain integration is not permission to install a private root on arbitrary unmanaged devices. Non-domain clients need an approved distribution and ownership process.
certutil -config 'PKI01.corp.example\Example Organisation Trust CA' -ping
certutil -dump 'C:\PKI-Evidence\RootCertificate.cer'
# On a representative client, for an approved issued pilot certificate:
# certutil -urlfetch -verify 'C:\Pilot\service.cer'Issue a disposable pilot through the intended template, then inspect identity, purposes, chain, private-key location and embedded publication URLs. Test its revocation using the actual retrieval path. Enrollment success proves the CA issued something; client verification proves a different set of trust and distribution dependencies. Record both results without implying that an unperformed recovery exercise passed.
Protect the CA identity and its operating evidence
Back up the database, CA certificates and private keys, registry configuration, CAPolicy.inf and enabled-template inventory through the supported procedure. Keep backup secrets separately protected. If an HSM owns a non-exportable key, use its documented recovery method. A server image alone is not a substitute for known signing-key recovery.
Monitor service health, capacity, certificate renewal, CRL publication and security events. Establish approval for template changes and separate administrative responsibilities where required. Authentication-certificate issuance also needs to account for current strong AD account-mapping requirements. Plan root renewal, key rollover and eventual retirement well before expiry makes them urgent.
Recognise the limits of undoing a trust deployment
Before issuance or trust distribution, a failed new deployment may be removed through controlled cleanup of its own objects. After certificates exist, uninstalling AD CS does not revoke them, remove every trust record or keep required revocation endpoints available. Decommissioning is a PKI lifecycle operation, not a feature-removal checkbox.
For enrollment faults, inspect request disposition, template publication and permissions. For validation faults, inspect trust, time, purposes and actual revocation retrieval. Preserve the exact setup or service error rather than recreating the CA. A managed PKI is ready when its team can explain who may issue, how clients validate and how the original CA identity can be recovered safely.
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…
Designing an AD CS template with a narrow enrollment boundary
Design a restricted AD CS template as an issuance policy, separate AD creation from CA enablement, validate subject and key controls, and…
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…