Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My CA server crashed. It was used to deploy certs to messenger clients for live communication. I am no longer using live communication. I removed the server object from AD but my clients and servers envent logs have a lot of the following entries

  1. Automatic certificate enrollment for local system failed to enroll for one Domain Controller certificate (0x800706ba). The RPC server is unavailable.

  2. DCOM was unable to communicate with the computer msgsvr01.mycompany.local using any of the configured protocols

What else do I need to remove form AD when removing a CA?


share|improve this question
up vote 2 down vote accepted

Have a look here:

I removed an Enterprise CA from an AD domain (Windows 2003) that I "inhertied" and started w/ a new Enterprise CA with no ill effects by following the directions in that article, then put in a fresh deployment that worked fine following. All-in-all, I felt it went very smoothly.

share|improve this answer
The crtutil key wouldn't be able to run on the DC because I never installed the cert services on that machine. It was only installed on the machine which was crashed. – Saif Khan Jun 25 '09 at 16:42
You can extract certutil.exe from the Windows setup files if you want to use it on any of the later steps. The big thing that gets done w/ it is deleting the old machine's private key. The private key is already gone if that machine was lost. You can do all the other steps safely. You're going to have to guess on the common name of the old CA, but you probably know it. – Evan Anderson Jun 26 '09 at 1:27
The info was excellent. I was able to remove all the entries and no event popped up in my logs for the last 12 hours. – Saif Khan Jun 26 '09 at 15:37
Glad I could help. – Evan Anderson Jun 26 '09 at 17:06

I would check your GPOs to make sure they arn't pushing an auto enrolment policy

User Settings -> Windows Settings -> Security -> Public Key Policies/AutoEnrollment policies

share|improve this answer
That's all well and good, but he needs to go thru the proper retirement procedure if he wants to fix this right and wants to be able to deploy a working Windows PKI later on. – Evan Anderson Jun 25 '09 at 14:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.