What you need to know
Use Move-ADDirectoryServer to review this narrow operational decision without extending the source beyond its stated scope.
Potentially affected
Teams, systems, services, or facilities within the stated scope of Move-ADDirectoryServer
DSE recommendation
Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.
Keep this document to one review outcome: Move-ADDirectoryServer: move addirectory server with bounded evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.
Source fact:
The official Move-ADDirectoryServer from Microsoft supports the following bounded statements:
- At SYNOPSIS, Microsoft states: “Moves a directory server in Active Directory to a new site.” The research record locates this support at SYNOPSIS.
- At DESCRIPTION, Microsoft states: “The Move-ADDirectoryServer cmdlet moves a directory server in Active Directory to a new site within the same domain.” The research record locates this support at DESCRIPTION.
The source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.
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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.
Applicability questions
- For source statement 1 at SYNOPSIS, which observable configuration, record, or test can confirm applicability here?
- For source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?
- What inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?
- Which condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials 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 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 SYNOPSIS; DESCRIPTION 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-195 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.
Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.
Official references
- Move-ADDirectoryServer — Microsoft
Review the official source
Move-ADDirectoryServer · Verified August 27, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE