<div>
Hi Cliff, <br />
<br />
A lot of the background behind all of my unreasonably stupid sounding questions are my way of disproving to certain people in my environment that the path that they've chosen to take was incorrect. &nbsp;The only way to have them believe that best practice is correct is to disprove their theories.<br />
<br />
Although I am familiar and understand best practice, hearing from professionals like yourself, full of knowledge and who are always willing to help shed light on mythical creatures such as AD CS, is the best way to combat the theories and methods that people have chosen to take in small environments such as a start up.<br />
<br />
Your patience and help through this process has been extremely helpful.
</div>


Hi Cliff,

A lot of the background behind all of my unreasonably stupid sounding questions are my way of disproving to certain people in my environment that the path that they've chosen to take was incorrect.  The only way to have them believe that best practice is correct is to disprove their theories.

Although I am familiar and understand best practice, hearing from professionals like yourself, full of knowledge and who are always willing to help shed light on mythical creatures such as AD CS, is the best way to combat the theories and methods that people have chosen to take in small environments such as a start up.

Your patience and help through this process has been extremely helpful.

<div>
Hey. I don't judge. Glad to help.
</div>


<div>
Thanks Cliff, as always, you're the best!
</div>


Thanks Cliff, as always, you're the best!

<div>
<div class="content wysiwyg-content">
I am in the process of preparing for the decommissioning of an Enterprise Root CA. &nbsp;I will be using this microsoft page: &nbsp;<a href="https://support.microsoft.com/en-us/help/889250/how-to-decommission-a-windows-enterprise-certification-authority-and-remove-all-related-objects" rel="ugc">https://support.microsoft.com/en-us/help/889250/how-to-decommission-a-windows-enterprise-certification-authority-and-remove-all-related-objects</a><br />
<br />
Anything to watch out for during this process would be great.
</div>
</div>


I am in the process of preparing for the decommissioning of an Enterprise Root CA.  I will be using this microsoft page:  https://support.microsoft.com/en-us/help/889250/how-to-decommission-a-windows-enterprise-certification-authority-and-remove-all-related-objects

Anything to watch out for during this process would be great.

Is there anything to watch out for when decommissioning an Enterprise Root CA?

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.