Scope RODC replicates passwords of all users incorrectly in Windows Server in observed AD/DNS state

Use this document to resolve one bounded operational decision: Scope RODC replicates passwords of all users incorrectly in Windows Server in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RODC replicates passwords of all users incorrectly in Windows Server from Microsoft supports the following bounded statements:

• At Introduction below H1, Microsoft states: “This article addresses an issue in which RODC replicates passwords when it’s granted incorrect permissions in Windows Server.” The research record locates this support at Introduction below H1.
• At Symptom, Microsoft states: “Normally, Read Only Domain Controllers (RODCs) only replicate user passwords for user accounts that are a member of the Allowed RODC Password Replication Group or are listed in the RODC account’s msDS-RevealOnDemandGroup attribute.” The research record locates this support at Symptom.

Only the traced statements above are asserted as source facts. Apply the review to Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services after confirming that the source and deployed context match.

What the source does not establish

The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Symptom, which observable configuration, record, or test can confirm applicability here?
• Which owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?
• What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?
• Which success, stop, and escalation criteria are written before testing begins?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

Tie each conclusion back to Introduction below H1; Symptom and to observable material such as sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Label this evidence set DSE-20260827-381 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• RODC replicates passwords of all users incorrectly in Windows Server — Microsoft