When you say check Network flow, are you referring to network connectivity?
Yes
Please don't forget to mark this reply as answer if it help to fix your issue
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am very confused by the process of publishing Root and Intermediate certificates to AD and how they deploy to servers across an enterprise. When I publish the Root and Intermediate CA certs to the AIA and Certification Authorities Containers in AD, some servers will pull the new certificates into their trust stores and others will not.
When looking for any documentation around this process, I cannot find much. Does anyone out there know the process from beginning to end? Also, does anyone have an idea of why some would pull the certs from AD and others would not?
Thank you to anyone who can shed light on these dark times.
When you say check Network flow, are you referring to network connectivity?
Yes
Please don't forget to mark this reply as answer if it help to fix your issue
These are live production servers. No network issues, regular restarts, but ___domain rejoins are out of the question. Any other ideas?
In this case you case you can export the root certificate from another server and installer it in all impacted servers manually in the right store.
Please don't forget to mark this reply as answer if it help to fix your issue
Let me ask this, is there a way to prevent a server from pulling these certificates from AD through configurations? What could one do to stop the autoenrollment process from downloading roots and intermediates from the AIA and Certificate Authorities containers in AD?
the download of the root certificate is not related of the auto-enrollment process.
It is not the same process. the root certificate can be detected via the certutil -pulse command or by restarting the server if the network connectivity is ok.
On the other hand, we can speak of auto-enrollment when you create a certificate template, then you allow the servers in question the to auto-enroll on this template and finally activate auto-enrollment through GPO.
Ahh now we are getting to the meat and potatoes. My understanding was the same, but this is where my confusion resides. To quote Brian Komar in "Windows Server 2008 PKI and Certificate Security" under the section on Publishing Certificates and CRLs into AD DS (pg. 133), it states "The next time Group Policy is applied to a computer that is a member of the forest, certificates will be automatically added to the trusted root or intermediate CA store of the local machine through the autoenrollment mechanism."
This was the original intent of this post was to get clarity on this exact issue. Are the references to autoenrollment different for these certs vs. what is used for say autoenrollment of a device authentication cert, or does it leverage the same process?