← Back to projects
PROJECT

Trading company in Shanghai | Windows Server 2003 AD rebuild and policy recovery

A legacy Windows Server 2003 domain had accumulated years of identity, DNS, permission and policy dependencies. The work started with read-only evidence collection, then rebuilt and restored the required relationships in stages rather than making repeated changes directly on an unknown legacy state.

ShanghaiTradingWindows Server 2003 AD / rebuild / permissions / GPO
01

Project context

The company was still dependent on an aging Windows Server 2003 Active Directory environment whose DNS, accounts, permissions and policies had changed over many years. Rather than making repeated changes in an undocumented directory, the project established a read-only baseline first and then rebuilt the identity, DNS, permission and policy foundation in a controlled sequence.

02

Objectives

  • Restore a maintainable Active Directory, DNS, access and Group Policy foundation.
  • Identify legacy dependencies and risk before rebuilding or changing the old environment.
  • Retain evidence for key accounts, permissions and policies so later modernization has a reliable baseline.
03

Scope baseline

01

Assess domain health, DNS, objects, permissions and client dependencies first.

02

Create a restore list for required users, groups, shares and policies.

03

Rebuild in stages with verification gates between authentication, DNS and policy changes.

04

Validate client sign-in, name resolution, share access and GPO application end to end.

04

Delivery and controls

  1. 01

    Assess domain health, DNS, objects, permissions and client dependencies first.

  2. 02

    Create a restore list for required users, groups, shares and policies.

  3. 03

    Rebuild in stages with verification gates between authentication, DNS and policy changes.

  4. 04

    Validate client sign-in, name resolution, share access and GPO application end to end.

  5. 05

    Document the recovered identity, DNS, permission and policy baseline, plus any legacy dependency that still requires a later upgrade or migration.

05

Risk and change control

R01

Changes were not made to the legacy directory until DNS, authentication, policy and business dependencies had been recorded.

R02

Legacy applications and clients were checked for domain, DNS or credential dependencies before identity changes.

R03

Permission and Group Policy changes were validated with representative users so working access was not lost during cleanup.

06

Acceptance and handover

  • Core directory services, DNS and client authentication paths were restored to a stable state.
  • Key users, groups and file-access relationships were verified against the agreed inventory.
  • Required Group Policies applied to the intended targets and their results were checked.
  • Recovery records, access/policy baselines and follow-up modernization recommendations were handed over.

Key deliverables

Directory and DNS baselineAccount and access inventoryGPO validation recordRecovery and modernization notes

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 →