We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Certificate Authority Has Too Many Root Certificates

Medium Priority
1,587 Views
Last Modified: 2012-05-07
This problem started because our enterprise root ca certificate expired. We tried to renew the certificate and now there are three root certificates in the CA. The results of the certutil -cainfo are below. The problem is that because of this we cannot renew or issue any certificates. Please help!

Exit module count: 1
CA name: moorpark
Sanitized CA short name (DS name): moorpark
CA type: 0 -- Enterprise Root CA
    ENUM_ENTERPRISE_ROOTCA -- 0
CA cert count: 3
KRA cert count: 0
KRA cert used count: 0
CA cert[0]: 4 -- Expired
CA cert[1]: 3 -- Valid
CA cert[2]: 3 -- Valid
CA cert version[0]: 0 -- V0.0
CA cert version[1]: 1 -- V1.0
CA cert version[2]: 0x20002 (131074) -- V2.2
CA cert verify status[0]: 0x800b0101 (-2146762495)
CA cert verify status[1]: 0
CA cert verify status[2]: 0
CRL[0]: 3 -- Valid
CRL[1]: 1 -- Error: No CRL for this Cert
CRL[2]: 3 -- Valid
DNS Name: curry5.samintl.com
Advanced Server: 1
CertUtil: -CAInfo command completed successfully.
Comment
Watch Question

ParanormasticCryptographic Engineer
CERTIFIED EXPERT

Commented:
I think your understanding if this issue is incorrect.  The output so far looks fine, there are probably just some followup tasks you need to do as I am imagining when you renewed the CA cert that you did so using a new keyset.

Your existing certs should be fine as the CRL from the original is still valid.  Looks like you never issued a CRL from the first renewal, but have from this instance.  That CRL needs to be pushed to your CDP locations.

You need to take a copy of this new root CA cert and deploy that to your clients via GPO or whatever methods you have used previously.  Do not remove the old root certificate from GPO, etc. - it is fine (and until you renew all the old certs important) to leave it there.

Since your environment presumably does not trust the new CA cert then that can get in the way of issuance.

Also, check your AIA locations and copy the CA cert to those locations as well.  The new CRLs may have a (2) at the end of the filename, for example RootCA(2).crl for the base crl, RootCA(2)+.crl for the delta if you have one.  If you have a script to copy the CRLs out, if they were specifying the exact file name you may need to adjust that - it may be easiest to just copy *.crl form the certenroll directory.
ParanormasticCryptographic Engineer
CERTIFIED EXPERT

Commented:
After that, you can wait for AD to replicate and if it is 2003/vista/2008 (or xp with 2003 adminpak installed to have access to certutil) then you can issue 'gpupdate /force' (or reboot) to push the new cert down, then 'certutil -pulse' to pulse autoenrollment events.  For xp without the adminpak then you can just do the gpupdate and reboot or wait.  For LDAP servers (usually just your DC's) if they need to renew then you will need to reboot after the new cert is applied to have it used instead of the old cached one.

If you are still having problems, run pkiview.msc and check that.  If still having problems after that, post back and let me know what exactly isn't working and if there are any unique considerations (works for these but not these, etc.)
ParanormasticCryptographic Engineer
CERTIFIED EXPERT

Commented:
The CA Cert Count just reflects that you had 1 cert originally and that it has been renewed 2 times.  Even though there are 2 that are valid that's perfectly fine.  Normally you should be renewing before the old one expires, so this is not abnormaly behavior.
Cryptographic Engineer
CERTIFIED EXPERT
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
rewarding points for detail of answer. we actually, though, just ended up uninstalling the root ca and installing on another server which seems to have worked fine for us.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.