Decomissioning 2003 CA


I decomissioned old 2003 CA using the following KB article:

All the steps completed without any problems with the exception of step 7. The following commands responded with "Access Denied" messages:

certutil -viewdelstore ldap:///CN=NtAuthCertificates,CN=Public Key

certutil -viewdelstore ldap:///CN=NtAuthCertificates,CN=Public Key

I used "certutil -viewdelstore" instead and removed the certificates manualy so that should be OK.

Finaly, I installed a new certification authority on Windows Server 2008 R2. Everything seems to be configured correctly but it seems like some references to the old CA are still left somewhere in AD. When I try to enroll for a certificate using MMC console, I get the up-to-date list of available certificate templates but when I actually enroll, I get "RPC Server Unavailable". I have confirmed that all the services are up and that firewall are in tact.

If I use web enrollment page, the whole process goes smoothly. I even get the message that the certificate was issued to me and that it was installed. BUT, no signs of that certificate exist on CA server nor on my client computer.

Thank you for your time,
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.

Jason WatkinsIT Project LeaderCommented:
it may just be that the new CA needs to propagate it's hooks into A.D.

Even though step 7 was a pain, were you able to complete the remaining steps successfully?

The verbose, unabridged, gory details for a migration like yours;

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

I would use ldifde to dump the AD database and search to see where the old CA server name exists.
I have used ldifde and/or ldp to delete items before like workstations that will not delete from AD because they had RRAS service installed, etc. - not a preferred method but it works.  Just like a failed registry tweak you run your own risks.

replace the dc=domain,dc=com with your real AD dns namespace.
ldifde -d dc=domain,dc=com -f ldap-out.txt
ldifde -d cn=configuration,dc=domain,dc=com -f ldap-configuration-out.txt
ldifde -d cn=schema,cn=configuration,dc=domain,dc=com -f ldap-schema-out.txt

Those dumps can be 100 meg or so don't try notepad use Scite , Notepad++ or one of the other text editors for the searching.

Hope that helps,
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
OS Security

From novice to tech pro — start learning today.