Back up the root CA before renewing its certificate

Keep this document to one review outcome: Back up the root CA before renewing its certificate. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Renew root CA certificate in Windows Server from Microsoft supports the following bounded statements:

• A root CA self-signs at the top of the PKI hierarchy, so its renewal preserves continued trust. The research record locates this support at Opening overview.
• Microsoft documents renewal with an existing or new key pair and makes root-CA backup the first procedure step. The research record locates this support at Sections: renewal options; Step 1 – Back up the root CA.

Keep the evidence boundary at these traced claims. They support a review of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

Plan chain rollover, publication, relying-party compatibility, and old-key retention before renewal. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections: renewal options; Step 1 – Back up the root CA, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles are in and out of scope?
• Which condition in Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, observed and expected states, owner, and reason for deviation.

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities before and after the test, and store only sanitized operational evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Opening overview; Sections: renewal options; Step 1 – Back up the root CA through CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks. Record what was collected, where, when, by whom, and which system or role it represents.

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

Official references

• Renew root CA certificate in Windows Server — Microsoft