Publishing certificates in the Active Directory


Deploying certificates and CRL in a domain or a forest in an automated fashion can done using GPO like many other settings.

However a less well-known possibility is to use the certutil -dspublish command. Let’s review how it works.

When using that option, certificates are stored in one of the “PKI Container”s of the forest, and every time GPO are refresh they are copied into the registry of the computer.

The PKI Settings of a forest are stored under the “Configuration” naming context of the forest.

![ADSI Edit PKI tree](
Configuration container in AD

Under that container, “Certification Authorities” will contain one entry for each Certification Authority Root you want the computers in your forest to trust.

To add a certificate use the following command:
<pre class="EnlighterJSRAW" data-enlighter-group="" data-enlighter-highlight="" data-enlighter-language="generic" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-theme="" data-enlighter-title="">certutil -dspublish -f CACertificate.cer RootCA

The CACertificate.cer is a file containing the certificate public key to publish in one of the standard X509 formats.

Once you’ve done that, you may want to wait for the Active Directory replication to happen in case the computer you’re testing receives GPOs from another Domain Controller as the one you targeted.

Then wait for the Group Policy refresh to occur (90 minutes more or less in a standard AD environment) or use gpupdate /force.

Your certificate authority will be then trusted, as it is now stored in the registry under HKLM\Software\Microsoft\SystemCertificates\Root\Certificates.

You’ll find a key with the thumbprint of the certificate and a blob entry containing the certificate.

The full list of registry locations that can be targeted with dspublish are now documented by Microsoft.