Delta CRL publication can be stabilized by moving the CA database and log files off the system drive, and by updating the CA’s CRL/CDP configuration so published CRLs use consistent locations.
- Back up first
- Export the CA configuration registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration - This is important before changing CA settings.
- Export the CA configuration registry key:
- Move the CA database and log files to a dedicated volume
- Warning: this requires registry changes. Incorrect registry edits can cause serious problems.
- Stop the Certificate Services service.
- Copy the database and log files from the default location:
%SystemRoot%\System32\CertLogto the new dedicated volume. - Update these registry values to the new path:
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration\DBDirectory -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration\DBLogDirectory -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration\DBSystemDirectory -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration\DBTempDirectory
-
- Start the Certificate Services service.
- Check the Application event log for CertSvc event 26 to confirm the service started successfully.
- If startup fails, verify the registry path syntax.
- Ensure NTFS permissions on the new folder allow System full control. By default, System, Administrators, and Enterprise Administrators have full control on the CertLog folder.
- Standardize CRL distribution point configuration
- Review the current CRL Distribution Point configuration with
pkiviewand export the configuration. - Configure the new CA or updated CA settings so the CRL Distribution Point settings match the required publication paths.
- For CDP/AIA design, configure these before issuing certificates where possible, because changes to CRL distribution point URLs affect only newly issued certificates. Previously issued certificates continue to reference the original locations.
- Review the current CRL Distribution Point configuration with
- Use stable and accessible CRL locations
- Adjust the default
LDAP://andhttp://URL locations on the CA Extensions tab according to operational needs. - Publish a CRL on an HTTP Internet or extranet location so clients outside the organization can perform certificate validation.
- HTTP CDP locations are also recommended for non-Windows clients.
- Windows clients retrieve CRL URLs sequentially until a valid CRL is found.
- Adjust the default
- Important impact for existing certificates
- If CRL paths change, certificates already issued continue to point to the old CRL location.
- To avoid revocation checking failures, the CA must continue publishing CRLs to the old paths as well as the new paths until all old certificates are retired.
This addresses the disk-space issue on the system drive and helps standardize CRL publication so delta CRLs and certificate validation remain available.
References: