Prevent Old CA Certificate from being distributed to Domain Clients


I run a Server 2012 R2 Domain.

I had an issue that my original CA certificate that expires in 2021 did not have the crl url in it so I created a new CA certificate created CA certificate that expires in 2026.

in the Certificate Authority General tab I can see both certificates.

I need to stop the original certificate from being distributed to the Domain Clients as its causing errors on my S4B servers.

I have tried going into the MMC certificates snap in (where you can see both the Old and New CA certificate) and deleting the old CA certificate on a client computer - but it just gets re-added.

any help would be appreciated

many thanks

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Okay... what I know.
There are two mechanisms thru which your trusted CA certificate is getting pushed to clients:
  1. Would be via Group Policy -- so you'd want to look thru the policies applied to your clients to make certain that isn't happening.
  2. Via certutil -dspubilsh.  In that case, I believe your certificate will be visible via ADSIEdit in Configuration,Services,Public Key Services, Certification Authorities.  Now, I fear -- that is the edge of my knowledge.  I suspect certutil -delstore is the best way to remove the old CA... but I don't know what impact manually deleting the CA Certificate might have.

In either case, fixing those will only prevent the client from receiving the CA on the local machine AGAIN after you remove them... it won't remove them.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Original request was to stop the certificate from propagating to the client machines.  There are two ways the root certificate would be distributed to clients, and this answer addresses each.
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Adding additional information: This is the procedure to remove an Enterprise CA from an environment.  Steps 6 & 7 are of particular interest if your CA is being distributed from AD (rather than by group policy.)
OWASP: Avoiding Hacker Tricks

Learn to build secure applications from the mindset of the hacker and avoid being exploited.

jackbensonDirectorAuthor Commented:
I do not need to remove the Certificate Authority

I originally created the  Certificate Authority in 2011 and it created a CA Certificate.

that original CA Certificate did not have a crl so I created a new CA Certificate in 2016.

every time I delete the old CA Certificate from a domain client - it gets replaced.

its not group policy that is causing it.

I need to stop the client computers getting the 2011 CA Certificate


Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
I believe I understand.  If the certificate isn't propagated by a Group policy, then there are objects in AD which still exist from the Certificate Authority created in 2011.  Because an Enterprise Certificate authority writes objects into the Active Directory, I believe you need to run thru the Certificate Authority decommissioning steps for that certificate authority.  I believe the specific object that needs to be removed is the certificationAuthority object specifies as the third object in step 6 -- but I'd advocate you run thru all of steps 5 and 6 to clean up the old installation.
jackbensonDirectorAuthor Commented:

can I check that you understand that I have not installed a new Certificate Authority - just a new certificate for the authority created in 2011


Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Apologies.  Just step six then... there are two certificateAuthority objects which contain the old certificate.  It's the object in "CN=Certification Authorities,CN=Public Key Services,CN=Services,CN=Configuration,DC=ForestRoot,DC=com. " which is causing that certificate to repopulate to your client machines... but be sure to only remove the 2011 certificate.

(And hopefully your new CA certificate isn't signed using the SHA1 algorithm.  Early next years, a fair amount of software will stop honoring certificates signed by CAs using SHA1.  Less of an issue for an internal CA, but could cause some software which checks to fail without a message.)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.