← Back to projects
PROJECT

Port operator in Foshan | Windows Server 2022 dual-DC AD rollout

A two-domain-controller Windows Server 2022 environment was planned and deployed with emphasis on replication, DNS, time, FSMO roles and client behavior. The second DC was considered complete only after it was proven able to participate in real authentication and policy services.

Foshan, GuangdongPort operationsWindows Server 2022 / dual DC / DNS
01

Project context

The organization needed two Windows Server 2022 domain controllers so authentication and DNS would not depend on a single server. The design treated Active Directory as a multi-master service—not a traditional active/standby pair—and explicitly covered replication, DNS, FSMO roles, time synchronization and client DNS behavior.

02

Objectives

  • Deploy two Windows Server 2022 domain controllers with integrated DNS.
  • Make AD replication, name resolution, time synchronization and client authentication verifiable.
  • Document role placement and health checks for ongoing domain-controller maintenance.
03

Scope baseline

01

Confirm naming, addressing, DNS and time prerequisites before promotion.

02

Validate the first DC before adding the second domain controller.

03

Check directory/DNS replication, SYSVOL/NETLOGON and key event logs.

04

Test client sign-in, name resolution and Group Policy with both DNS servers.

04

Delivery and controls

  1. 01

    Confirm naming, addressing, DNS and time prerequisites before promotion.

  2. 02

    Validate the first DC before adding the second domain controller.

  3. 03

    Check directory/DNS replication, SYSVOL/NETLOGON and key event logs.

  4. 04

    Test client sign-in, name resolution and Group Policy with both DNS servers.

  5. 05

    Document FSMO placement, DNS configuration, replication health and the routine checks required for both domain controllers.

05

Risk and change control

R01

FSMO roles, DNS and replication were designed as AD dependencies rather than as a simple primary/backup server pair.

R02

Time synchronization and client DNS settings were validated to avoid authentication faults that can look like replication failures.

R03

Critical event logs and replication state were reviewed before the second DC was considered ready.

06

Acceptance and handover

  • Directory and DNS replication between the two domain controllers matched the intended design.
  • Clients could sign in, resolve names and process policy using the planned DNS configuration.
  • No unresolved critical replication or directory-service errors remained in the relevant event logs.
  • Role, DNS, replication and health-check baselines were handed over.

Key deliverables

AD/DNS architecture recordFSMO and time baselineReplication validationDC operations checklist

Planning a similar project?

Share the current environment, business impact and target outcome. We will confirm scope, dependencies and delivery boundaries first.

Discuss a similar project →