手工清除WINDOWS AD域内的CA( Certificate Authority)

域控上的日志不断报错,源于美国一台我到公司之前的CA非法撤消,

事隔多年,于我,只好手工清除。

~~~~

参考文档:

http://retrohack.com/cleaning-up-after-a-failed-2008-certificate-authority/

inding myself with a 2008 AD integrated certificate authority gone bork, I wanted to get it completely out of AD. The server was long since dead, so gracefully uninstalling Certificate Services was not an option. It’s presence wasn’t hurting anything, but if you know me at all, you know I like a clean AD.

The main steps below were taken from http://support.microsoft.com/kb/889250, but I have changed them to match up with what I did for Windows 2008. The biggest difference was that I had to go into ADSIEDIT to do most of this, instead of AD Sites & Services.

 

 

Determine the CACommonName of the CA.

If you do not remember this, create an msc, add the Certificates snap-in for your local computer, and browse down the tree to Trusted Root Certification Authorities. Expand the Certificates, and the browse through until you find the name of the failed CA.

Then follow these steps, being careful NOT to delete other PKI objects such as those from TMG or other CAs in your environment.

  1. Click Start, Run, then type adsiedit.msc and click OK.
  2. Right-click ADSI Edit, select connect to, and choose Configuration from the drop down menu for "Select a well known naming context."
  3. Expand Services, expand Public Key Services, and then click the AIA folder.
  4. In the right pane, right-click the CertificationAuthority object for your CA, click Delete, and then click Yes.
  5. In the left pane, click the CDPfolder.
  6. In the right pane, locate the container object for the server where Certificate Services is installed. Right-click the container, click Delete, and then click Yes two times.
  7. In the left pane, click the Certification Authorities node.
  8. In the right pane, right-click the CertificationAuthority object for your CA, click Delete, and then click Yes.
  9. In the left pane, click the Enrollment Services node.
  10. In the right pane, verify that the pKIEnrollmentService object for your CA was removed when Certificate Services was uninstalled. If the object is not deleted, right-click the object, click Delete, and then click Yes.
  11. At the root of CN=Public Key Services, find the object CN=NTAuthCertificates and access its properties. There is a multi-valued string cACertificate. Remove the entry that corresponds to your dead CA. Hopefully, you will only have one, as this is encoded. If you see multiple, you can try to figure out which is the correct one by picking it out chronologically, or by converting the encoding to ASCII characters, or perhaps you could consult the Tarot, or I Ching. Sorry, I don’t have much better advise to give on this one.

Then log on to a domain controller, open an administrative cmd prompt and run this command.    certutil -dcinfo deleteBad [enter]

Certutil.exe tries to validate all the DC certificates that are issued to the domain controllers. Certificates that do not validate are removed.

Finally, go into your default domain GPO, Computer Configuration, Policies, Windows Settings, Security Settings, Public Key Policies and remove the root certificate from the list of Trusted Root Certificate Authorities. Give your clients time to refresh group policy, and you’re all set.

But since you really ought to wait for group policy to propagate before you make any other changes, you should take a few moments to yourself and resist the temptation to make more changes. Trust me, this is for your own good. Tell your boss I said so. As I was finishing this up, I overheard the word "Willoughby" and was reminded of one of my favourite episodes of The Twilight Zone. The time it takes you to enjoy the show below should be just enough time to wait for GPO propagation to complete before you do anything else.

 

时间: 2024-09-19 20:33:29

手工清除WINDOWS AD域内的CA( Certificate Authority)的相关文章

如何手工转移WINDOWS AD域内 Inter-Site Topology Generator (ISTG)

升级和迁移AD域控,总免不了这些琐碎手工之事. 还好,网络大把资源可以使用. http://www.expta.com/2011/03/how-to-manually-move-istg-role-to.html The Knowledge Consistency Checker (KCC) is an Active Directory component that is responsible for the generation of the replication topology bet

ASA8.42的Windows AD域LDAP认证

1.拓扑图: 参考:http://bbs.51cto.com/thread-728599-1-1.html 2.ASA配置步骤: A.添加LDAP认证类型的aaa-server aaa-server yuntian.com protocol ldap max-failed-attempts 2 aaa-server yuntian.com (inside) host 100.1.1.100 ldap-base-dn cn=users,dc=yuntian,dc=com ldap-group-ba

ad域-windows server 2008 做AD域 和 ldap同步用户

问题描述 windows server 2008 做AD域 和 ldap同步用户 windows AD域 我已经搭建好了,这个google上面很多方法搭建,可是就是很少做到 和LDAP同步用户访问.出现问题,要如何配置slapd.conf 求非常详细的帮助文档,或者指点.急 这里我之前用samba来同步AD域 是可以访问的,可以要做到LDAP用户也可以. 解决方法 ,想了好几天 最近一直在研究利用openldap代理windows AD的问题,初次接触ldap,希望大侠能给点意见. 环境: 一台

VPN用户在外网通过ISA (CA证书)访问域内VPN服务器

一般情况下VPN用户在连接VPN服务器是是要输入密码的,如果这样的话,那么在一些公共场合输入密码的时候很有可能造成密码的泄露,从而造成不必要的损失.口令验证协议虽然硬件上的要求没有质询握手协议那么高,但是,在安全性上面,其跟质询握手协议还是有一段距离.具体要采用哪一种身份验证协议,用户要根据自己的安全级别进行判断.今天我做的这个实验是:VPN用户在外网连接VPN服务器来访问域内的资源时,不需要输入密码,而是通过CA服务器验证VPN用户的身份. 实验环境:beijing内网的域控制器.DNS服务器

保护内网安全之提高Windows AD安全性(三)

本文讲的是保护内网安全之提高Windows AD安全性(三),Active Directory的安全始于能确保安全地配置域控制器(DC). 在今年夏天的BlackHat USA大会上,我非常专业的提到了AD的安全,并提供了关于如何能够最好程度上保护Active Directory安全的一些提示. 这篇文章主要关注域控制器的安全性和一些跨越Active Directory的安全性.毕竟我的博客被称为"ADSecurity" - 本文将会涵盖一些通过保护域控制器(简称"域控&qu

保护内网安全之提高Windows AD安全性 (二)

本文讲的是保护内网安全之提高Windows AD安全性 (二),Active Directory的安全始于能确保安全地配置域控制器(DC). 在今年夏天的BlackHat USA大会上,我非常专业的提到了AD的安全,并提供了关于如何能够最好程度上保护Active Directory安全的一些提示. 这篇文章主要关注域控制器的安全性和一些跨越Active Directory的安全性.毕竟我的博客被称为"ADSecurity" - 本文将会涵盖一些通过保护域控制器(简称"域控&q

保护内网安全之提高Windows AD安全性 Part.1

本文讲的是保护内网安全之提高Windows AD安全性 Part.1,Active Directory的安全始于能确保安全地配置域控制器(DC).在今年夏天的BlackHat USA大会上,我非常专业的提到了AD的安全,并提供了关于如何能够最好程度上保护Active Directory安全的一些提示.这篇文章主要关注域控制器的安全性和一些跨越Active Directory的安全性.毕竟我的博客被称为"ADSecurity" - 本文将会涵盖一些通过保护域控制器(简称"域控&

在 Windows下管理Samba4 AD域管制器DNS和组策略

这篇文章中我们将学习如何使用微软 DNS 管理器远程管理我们的 Samba AD 域控制器的 DNS 服务器,如何创建 DNS 记录,如何创建反向查找区域以及如何通过组策略管理工具来创建域策略. 第 1 步:管理 Samba DNS 服务器 Samba4 AD DC 使用内部的 DNS 解析器模块,该模块在初始化域提供的过程中创建(如果 BIND9 DLZ 模块未指定使用的情况下). Samba4 内部的 DNS 模块支持 AD 域控制器所必须的基本功能.有两种方式来管理域 DNS 服务器,直接

Samba 系列(四):在 Windows 下管理 Samba4 AD 域管制器 DNS 和组策略

要求 1. 在 Ubuntu 16.04 系统上使用 Samba4 软件来创建活动目录架构(一) 2. 在 Linux 命令行下管理 Samba4 AD 架构(二) 3. 使用 Windows 10 的 RSAT 工具来管理 Samba4 活动目录架构 (三) 第 1 步:管理 Samba DNS 服务器 Samba4 AD DC 使用内部的 DNS 解析器模块,该模块在初始化域提供的过程中创建(如果 BIND9 DLZ 模块未指定使用的情况下). Samba4 内部的 DNS 模块支持 AD