Systems / Featured build / Windows Server

BEN.LOCAL

An organization built from the network up. A documented Windows Server lab spanning identity, access, storage, networking, resilience, and deployment.

The brief

Start with an empty virtual network. Build the services, permissions, and endpoints needed to operate a multi-department environment.

Hyper-V · Windows Server 2019/2016 · Windows 10

6Organizational units
9Virtual machines
2Virtual networks
106Pages in supplied build deck
01 / Architecture

One domain.
Many moving parts.

The architecture below is reconstructed from the project summary's machine and IP inventory. It is a logical overview, not a physical wiring diagram.

Internal LAN · 192.168.100.0/24

Domain & services

DC1 · .1AD DS · DNS · DHCP · WDS · FSRM · files
DC2 · .2Additional DC · RID master · iSCSI initiator
IS1 / IS2 · .3 / .4IIS servers · NLB virtual IP .10
CL1 · DHCPWindows 10 · domain client
↳ Print1 / Print2 · .50 / .51 · GPO deployment
WAN · 192.168.200.0/24

Remote access & imaging

RAS · .200.1VPN gateway · LAN interface .100.254 · iSCSI target
PC1 · .200.10Remote Windows 10 VPN client
Master · DHCPWindows reference image
NEW · DHCPPXE deployment target
↔ RAS links WAN and LAN in the lab
02 / Scope

Beyond a domain
controller.

The work is organized around services that depend on each other—not a disconnected list of tools.

01 / Identity

Directory & access

AD DS forest, six OUs, scripted user creation, delegated password resets, password policies and HelpDesk permissions.

02 / Policy

Endpoint governance

GPO-based folder redirection, drive mapping, removable storage restrictions, application restrictions and software deployment.

03 / Data

File services

NTFS permissions, shared reports, FSRM quotas and file screens, shadow copies and iSCSI storage.

04 / Network

Connectivity

DHCP, DNS, routing and remote access, VPN lab configuration and a second domain controller.

05 / Availability

Service continuity

Two IIS servers, Network Load Balancing, network printer deployment and replication-related administration.

06 / Deployment

Windows imaging

WDS, PXE, Sysprep and DISM procedures documented as a repeatable deployment workflow.

03 / Selected evidence

Not just a claim.
A build record.

Screenshots reproduced from the original presentation. Select any image to inspect it at a larger size.

04 / Troubleshooting

When the lab
pushed back.

A technical portfolio is more useful when it includes what failed, not only what was configured.

The project records a conflict between File Server Resource Manager file screening and Group Policy editing on Windows Server 2019.

Documented workaround: temporarily unload the datascrn filter using fltmc unload datascrn, complete GPO editing, then restore it with fltmc load datascrn. This is a lab-specific troubleshooting record, not a recommended general production procedure.
05 / Primary materials

Read the work.

Both original PowerPoint files are preserved. PDF versions are included for convenient browser viewing.

Executive orientation

Project summary

11 slides covering architecture, scope, skill areas, slide index and a machine-by-machine build map.

Detailed technical record

Complete build

106 pages in the supplied PowerPoint, including lab screenshots, step-by-step instructions and deployment documentation.

Preview the project summary

If your browser does not support embedded PDFs, use the Read PDF link above.

Evidence boundary: The project summary identifies the later Windows image-deployment section as documented commands and Microsoft Learn procedures without corresponding lab screenshots. It is presented here as documentation, not independently verified completed deployment.
Next in Systems
Explore Systems projects↗All projects↗