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

简介: 域控上的日志不断报错,源于美国一台我到公司之前的CA非法撤消, 事隔多年,于我,只好手工清除。 ~~~~ 参考文档: http://retrohack.com/cleaning-up-after-a-failed-2008-certificate-authority/ inding m...

域控上的日志不断报错,源于美国一台我到公司之前的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.

 

目录
相关文章
|
存储 Java 数据库
windows server2016搭建AD域服务器
windows server2016搭建AD域服务器
1278 72
|
安全 BI 数据安全/隐私保护
AD域、Windows AD域管理功能大全
Windows AD域管理功能大全,再也不用东拼西凑了!
1252 1
|
人工智能 JavaScript 网络安全
ToB项目身份认证AD集成(三完):利用ldap.js实现与windows AD对接实现用户搜索、认证、密码修改等功能 - 以及针对中文转义问题的补丁方法
本文详细介绍了如何使用 `ldapjs` 库在 Node.js 中实现与 Windows AD 的交互,包括用户搜索、身份验证、密码修改和重置等功能。通过创建 `LdapService` 类,提供了与 AD 服务器通信的完整解决方案,同时解决了中文字段在 LDAP 操作中被转义的问题。
678 1
|
存储 监控 安全
深入调查研究挖掘Windows AD
【11月更文挑战第18天】
344 0
|
弹性计算 网络协议 文件存储
将Windows系统机器加入AD域
一台Windows服务器需要加入到Active Directory域后才能通过AD域服务来管理。本文介绍了如何将一台Windows服务器加入已有的AD域。
5517 0
将Windows系统机器加入AD域
|
存储 安全 网络协议
Windows安全加固-AD建立与加入
Windows安全加固-AD建立与加入
396 0
|
文件存储 数据安全/隐私保护 Windows
从Windows以AD域用户身份挂载使用阿里云SMB协议文件系统
在完成AD域接入之后,用户即可开始以AD域用户身份挂载使用阿里云SMB协议文件系统了。本文介绍了几种SMB文件系统的挂在方式以及简单的ACL特性使用方法的演示。
6692 0
从Windows以AD域用户身份挂载使用阿里云SMB协议文件系统
|
缓存 负载均衡 网络协议
windows之DNS7种资源记录和flushdns命令清除DNS缓存以及nslookup解析域名和ipconfig/all命令查看网络配置使用总结
windows之DNS7种资源记录和flushdns命令清除DNS缓存以及nslookup解析域名和ipconfig/all命令查看网络配置使用总结
1129 0
windows之DNS7种资源记录和flushdns命令清除DNS缓存以及nslookup解析域名和ipconfig/all命令查看网络配置使用总结
|
缓存 数据安全/隐私保护 Windows
windows 技巧篇-清除共享地址访问缓存信息,共享路径临时访问用户切换方法
windows 技巧篇-清除共享地址访问缓存信息,共享路径临时访问用户切换方法
1008 0
windows 技巧篇-清除共享地址访问缓存信息,共享路径临时访问用户切换方法
|
网络协议 文件存储 数据安全/隐私保护
通过安装和配置AD域解决Windows Server 2016的IIS无法加载SMB文件卷文件的问题
通过客户反馈我们发现Windows Server 2016的IIS无法加载SMB文件卷的文件,显示的错误是:未能加载文件或程序集。经过我们不断研究和实验,发现在安装和配置好AD域之后,2016上IIS加载文件卷文件发生错误的问题可以得到解决。
5229 0
通过安装和配置AD域解决Windows Server 2016的IIS无法加载SMB文件卷文件的问题