Annex — Certificate Export and NTAuth Store Procedures
Get the certificate chain
The following procedure describes how to manually inspect and export the full certificate chain. The certificate must be trusted by the computer.
- Press Windows + R and type
certmgr.mscto open the user certificate store. - Locate and double-click the certificate you want to inspect.
- Go to the Certification Path tab.
- The Certificate status field should read "This certificate is valid". If it does not, root or intermediate certificates may be missing.
- Click each certificate in the chain and use View Certificate to open intermediate certificates for export.
Export a certificate
- On the Details tab of the certificate, click Copy to File.
- If exporting the end-entity certificate, you may be asked whether to export the private key. Do not export the private key.
- Select the CER format — either DER-encoded binary or Base-64 encoded.
Adding a certificate to the NTAuth store
The NTAuth store holds the CA certificates trusted for smart card logon. If a root or intermediate CA certificate is missing, authentication fails with a "certificate not trusted" error.
First, export the CA certificate to a .cer file (see above). Then use one of the methods below.
Method 1 — PKI Health Tool
- Install the Windows Server 2003 Resource Kit Tools.
- Open
mmc.exeand add the Enterprise PKI snap-in:- Go to Console → Add/Remove Snap-in → Standalone → Add.
- Select Enterprise PKI, click Add, then Close, then OK.
- Right-click Enterprise PKI and choose Manage AD Containers.
- Click the NTAuthCertificates tab, then click Add.
- Go to File → Open, locate the
.cerfile, and click OK.
Method 2 — Certutil
certutil -dspublish -f filename.cer NTAuthCA
Note — Propagation delay: Changes to the NTAuth store can take up to 8 hours to propagate. Force immediate propagation on both the domain controller and the client with:
gpupdate /force