Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 38 ยท Projects and Practice

Project: Design an OU Structure and Delegation Model

Design a practical Active Directory OU structure for a mid-sized company, plan delegation and GPO placement, and validate the design with a runnable Python checker.

In this project you design the OU tree for a fictional company, decide who administers what, and place Group Policy where it belongs. The result is a plan you could hand to a real team. You will also build a checker that catches design mistakes automatically, which is how large environments keep a design from drifting.

You cannot create a real domain on this site, so the commands you would run are listed as read-only text and the checker is a Python stand-in working on a data structure. Everything uses ideas from earlier lessons: GPO links and precedence, filtering, tiering and password policies.

The scenario

Northwind Trading has 1,200 employees in Berlin, Tokyo and a small Paris office. IT is centralised in Berlin, but each office has a local helper who resets passwords and moves computers. Finance and HR handle sensitive data. The company has Windows laptops, a few hundred servers, and a handful of Linux servers joined to the domain. Domain: northwind.example.

Requirements:

  1. Help desk staff can reset passwords and unlock accounts for ordinary users in their own office only.
  2. Server admins manage member servers but never see workstations or domain controllers.
  3. Finance computers get a stricter security baseline. Laptops get a power and encryption GPO.
  4. Domain controllers, admin accounts and the PKI form Tier 0 and are isolated.
  5. New users and computers land in a holding OU instead of the default Users and Computers containers, so they never receive anything by accident.

Design principles

  • Structure for administration and policy, not for the org chart. An OU should exist because someone different administers it or a GPO differs for it. Departments that need no different treatment do not need an OU.
  • Shallow trees. Aim for three or four levels; deep trees slow policy evaluation and confuse people.
  • Separate object types. Users, computers, groups and service accounts in different OUs make delegation and GPO scoping easy (computer settings on computer OUs, user settings on user OUs).
  • Keep Tier 0 on its own branch outside the delegated tree.
  • Protect OUs from accidental deletion.
  • Redirect defaults. redircmp and redirusr make new computers and users land in your holding OUs.

A proposed tree

flowchart TD
  D["northwind.example"] --> T0["Tier0 (admins, PAW, PKI)"]
  D --> Co["Northwind"]
  D --> DC["Domain Controllers"]
  Co --> Us["Users"]
  Co --> Cm["Computers"]
  Co --> Sv["Servers"]
  Co --> Gr["Groups"]
  Co --> Sa["ServiceAccounts"]
  Co --> Hold["_Staging"]
  Us --> UB["Berlin"]
  Us --> UT["Tokyo"]
  Us --> UP["Paris"]
  Cm --> WB["Workstations"]
  Cm --> LP["Laptops"]
  Cm --> FN["Finance"]

Offices appear only under Users and Computers, where local delegation applies. The same office names are not repeated under Servers or Groups.

Delegation matrix

Delegation uses the Delegation of Control Wizard or direct ACL edits on the OU, always granting to a group (such as DLG-HelpDesk-Berlin), never to individuals. Typical custom tasks:

Group Scope (OU) Rights
DLG-HelpDesk-Berlin Users/Berlin Reset password, unlock account, read and write lockoutTime, pwdLastSet (user must change password at next logon)
DLG-HelpDesk-Tokyo Users/Tokyo Same, Tokyo OU
DLG-Join-Computers _Staging Create computer objects (used by deployment tools and realm join)
DLG-ServerAdmins Servers Full control on computer objects; local admin through GPO Restricted Groups
DLG-GroupManagers Groups Create/delete groups, modify membership

Delegation grants rights; GPOs decide settings. Combine them with security groups rather than direct user ACEs, document each ACE, and review them yearly.

GPO plan

GPO Linked at Filtering Contents
SEC - Baseline Computers Northwind/Computers (Enforced) none Firewall, SMB signing, audit policy, Defender
SEC - Finance Hardening Computers/Finance none Stricter user rights, USB blocked
HW - Laptop Power and BitLocker Computers/Laptops none Power plan, drive encryption
USR - Desktop Experience Northwind/Users none Wallpaper, drive maps through preferences
USR - Finance Drives Northwind/Users Group Finance-Staff (plus Read for computers) Finance share maps
SEC - Server Baseline Northwind/Servers none Server hardening, RDP limits
SEC - Tier0 Tier0 and Domain Controllers none Logon restrictions, enhanced audit

The domain-level Default Domain Policy keeps only the password and Kerberos policy; fine-grained PSOs handle admins and service accounts.

Build the checker

The checker below models the tree as nested dictionaries and applies rules that mirror the principles: depth limit, OUs named consistently, no empty-purpose OUs, no user objects in a computer OU, and GPO links on existing OUs only. Run it, then edit the design to see violations appear.

Python OU design validator (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The tree has one bad name, and one link to an OU that does not exist. Fix the data so the list is empty, then add your own rule (for example "every OU needs a purpose").

Delegation checker

Delegation sprawl is the second thing that drifts. This stand-in compares who has which rights where, and flags the dangerous ones: any right granted to an individual user, anything broader than the OU's purpose, and high-impact rights such as Full Control on the domain.

Python Delegation review (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Commands you would run

POWERSHELL
redircmp "OU=_Staging,OU=Northwind,DC=northwind,DC=example"
redirusr "OU=_Staging,OU=Northwind,DC=northwind,DC=example"
New-ADOrganizationalUnit -Name Northwind -Path "DC=northwind,DC=example" -ProtectedFromAccidentalDeletion $true
New-ADOrganizationalUnit -Name Users -Path "OU=Northwind,DC=northwind,DC=example"
New-GPO -Name "SEC - Baseline Computers" | New-GPLink -Target "OU=Computers,OU=Northwind,DC=northwind,DC=example" -Enforced Yes

These are listed for reference only; run them in a lab first (see PowerShell safety habits).

Extension tasks

  1. Add an OU for the Paris office computers and decide whether it deserves its own GPO or none.
  2. Write a rule for the checker that every OU linked to a user GPO contains users, not computers.
  3. Sketch Tier 0 isolation: authentication policy, separate admin accounts, Protected Users and the groups in the Tier0 OU.
  4. Add a fine-grained password policy for ServiceAccounts and Domain Admins.
  5. Decide where the Linux servers belong and which delegation group joins them.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the best reason to create an OU?

    OUs exist for delegation and Group Policy scoping, not to copy the org chart.
  2. 2. Why redirect the default Users and Computers containers?

    Containers cannot have GPOs linked, so redirecting new objects into OUs lets policy apply from the start.
  3. 3. Delegation should be granted to:

    Groups make delegation manageable and auditable.
  4. 4. Which GPO placement is best for a baseline that applies to all computers and must not be overridden?

    A single enforced link at the top applies everywhere and cannot be blocked below.

Summary

  • Design OUs for delegation and policy; keep the tree shallow, separate object types and isolate Tier 0.
  • Delegate to groups per office and role; document every ACE.
  • Link GPOs high, narrow them with filters, and enforce only true baselines.
  • Automate checks of names, depth, links and delegation to keep the design from drifting.

Next: Project: Build an LDAP Filter Engine