Project context
The customer operated offices in Hangzhou and Jinhua. Site connectivity already existed through the current firewall environment, so the delivery boundary was intentionally kept above the network layer: rebuild identity and policy at both sites, establish inter-domain trust, introduce a new file server, and define controlled cross-site access for users and data.
Objectives
- Rebuild two maintainable AD environments without changing the existing site-to-site network design.
- Use DNS, domain trust and security groups to create controlled cross-site identity and file access.
- Deploy a new file share with read/write or read-only access limited to explicit groups and folders.
Scope baseline
Review AD, DNS, GPO and client logon at both Hangzhou and Jinhua sites.
Rebuild AD, align DNS resolution and time, and configure inter-domain trust.
Deploy new file shares, folder structure, security groups and cross-domain permissions.
Validate representative-user logon, GPO, cross-domain file access and endpoint baseline policy.
Implementation and control
- 01
Freeze lower-layer connectivity changes and confirm the current site link is stable enough for required networks, keeping network and identity workstreams separate.
- 02
Build a clean AD/DNS baseline at each site and verify local logon, name resolution and GPO before introducing trust.
- 03
Configure the DNS relationship and only the communications required for domain trust; validate first with test accounts.
- 04
Create the new file share and assign cross-domain read/write or read-only access through security groups rather than direct broad grants.
- 05
Complete representative-user, GPO and file-access tests, then hand over architecture, trust, permission and support records.
Risk and change control
The underlying link already works; changing it during the identity project would widen scope and make troubleshooting ambiguous.
Domain trust depends on DNS, time and required communications, so failures are isolated by layer rather than treated as a generic authentication issue.
Cross-domain file access is not opened to all users; security groups and explicit folders define the boundary.
Acceptance and handover
- Users at both sites can sign in to their local domains and receive baseline GPOs.
- Inter-domain DNS, trust and representative-account authentication are verified.
- The new file share enforces the agreed group-based read/write or read-only model.
- Two-site architecture, trust relationship, file permissions and client-test records are handed over.

