AD CS CRL Publication Failure Due to Large CRL Size

Adin Mohhamed 20 Reputation points
2026-09-09T02:55:20.83+00:00

Hi team,

Our issuing CA is unable to publish the CRL after the file grew beyond 100 MB, resulting in LDAP directory synchronisation failures. What is the recommended way to reduce the CRL size by adjusting the CRL and delta CRL publication intervals, and can partitioned CRLs be used to avoid this issue?

Appreciate your suggestion!

Adin.

Windows for business | Windows 365 Business
0 comments No comments

2 answers

Sort by: Most helpful
  1. Marcin Policht 106.8K Reputation points MVP Volunteer Moderator
    2026-09-09T03:14:21.0766667+00:00

    Yep - implementing partitioned CRLs is the recommended long-term solution when the issuing CA's CRL has exceeded 100 MB and is causing LDAP directory replication or synchronization failures. Partitioning prevents the CA from having to publish one continuously growing CRL file and keeps each individual CRL within a manageable size.

    For the publication intervals, delta CRLs should be published relatively frequently, such as every 1 to 2 days, so that newly revoked certificates are distributed promptly. The base CRL can have a much longer validity and publication interval, such as several weeks or months, which reduces how frequently the large base CRL has to be regenerated and replicated. Note that changing the intervals alone is not a permanent solution because the base CRL will continue to grow as additional certificates are revoked.

    Partitioned CRLs address the underlying size problem by splitting the revocation information into smaller CRLs based on certificate characteristics, such as certificate templates or key usage, rather than simply separating certificates by revocation reason. In an AD CS environment, this can be configured through the CA properties in certsrv.msc on the Extensions tab by defining additional CRL Distribution Points and associating the appropriate CDPs with specific certificate templates. Clients then retrieve the CRL partition applicable to their certificate type rather than one enormous CRL containing all revoked certificates.

    More at http://learn.microsoft.com/en-au/answers/questions/5983547/crl-publication-optimization-and-partition-setup


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments No comments

  2. moonis ellahi 0 Reputation points
    2026-09-09T03:13:05.9133333+00:00

    This issue is usually caused by the CRL becoming too large to publish through LDAP. Check the CRL size and consider reducing stale certificates, reviewing CRL settings, or using HTTP-based CRL distribution.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.