Raise the RID pool after rollback to prevent identifier reuse

Keep this document to one review outcome: Raise the RID pool after rollback to prevent identifier reuse. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official AD Forest Recovery – Raising RID pools from Microsoft supports the following bounded statements:

• Raising available RID pools prevents a restored domain from reallocating a RID used after the backup point. The research record locates this support at Opening overview.
• The domain-wide RID space is maintained in the RID Manager object’s rIDAvailablePool attribute. The research record locates this support at Section: Active Directory RID Pools and rIDAvailablePool.

The source support ends with the statements listed above. Use them to examine forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps in the applicable environment, not to imply a wider guarantee.

What the source does not establish

Perform RID arithmetic exactly as documented and record the pre- and post-change values. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel and the environment’s recorded constraints.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section: Active Directory RID Pools and rIDAvailablePool, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps are in and out of scope?
• Which condition in offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps, observed and expected states, owner, and reason for deviation.

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets.

Verification and evidence

Tie each conclusion back to Opening overview; Section: Active Directory RID Pools and rIDAvailablePool and to observable material such as backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.

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

• AD Forest Recovery – Raising RID pools — Microsoft