See all of the top support solutions for our most common issues here
Carol has been busy today, now with another post on how the Configuration Manager Product Team has updated their blog post for publishing the CRL on a separate Web server because the instructions were missing the variable <DeltaCRLAllowed> in the paths, which is needed for delta CRLs. According to Carol:
As a rule, I'm not fond of adding variables in documentation instructions when they are not needed for basic functionality, but this one is needed for delta CRLs. I also added <CAName> so that you can publish CRLs from different CAs into the same location (for example, when you have a tiered CA hierarchy you must publish CRLs from each CA in the chain up to and including the root), and <CRLNameSuffix> according to best practices (http://technet.microsoft.com/en-us/library/dd379469(WS.10).aspx).
For more information see http://blogs.technet.com/configmgrteam/archive/2009/08/13/updated-blog-post-for-how-to-publish-the-crl-on-a-separate-web-server-for-delta-crls.aspx.
J.C. Hornbeck | Manageability Knowledge Engineer