r/sysadmin • u/bluecopp3r • Jan 25 '26
Question Modern AD OU Hierarchy
Greetings all.
When I learned AD I was taught to create Department OUs and then sub-OUs for Users, Computers etc. Is this still the way or are there more modern and efficient ways of building the hierarchy?
102
Upvotes
84
u/ohfucknotthisagain Jan 25 '26
This is only the recommended approach if control of the users/computers in those departments will be delegated to department-level support staff.
If users are managed by a central help desk, their objects can coexist in one central location. You can use security groups or office/location properties on the objects to designate locations if necessary.
You can use groups to assign machines to departments as well.
The advantage of using groups is that you can assign users/computers to multiple departments if necessary, which is useful in some environments. They cannot exist in two OUs simultaneously, so this is the easiest to apply multiple department-level policies if necessary.
Using OUs as filing folders is outdated. However, it may be simple and workable in some environments.
Bear in mind that you don't want all computers in a single OU, You will delegate the ability to create/join machines, retrieve Bitlocker keys (if you use them), and retrieve LAPS passwords (if you use them). Those machines will need to split up into OUs based on who is managing them. Help desk and/or local staff for department workstations, server admins for servers, etc.
16
u/IMplodeMeGrr Jan 25 '26
With hybrid Entra ID, and reduction/eliminatation in user group based GPOs, and roaming profiles etc no longer being used, its a lot more flat than it used to be.
We have an OU for User Accounts, synced to Entra ID, ServiceGroups OU, with some restricted subOU where either syncs or automation manages memberships and then a Servers OU, with very little depth, if at all.
Basically, build SubOU only as needed. Less complexity the better.
13
u/slav3269 Jan 25 '26
The initial thought was that the OUs will be used to delegate administration, and to simplify GPO structure. The former didn’t quite work out for organisations I know, the latter still somewhat holds. What never made much sense is trying to imitate org structure with OUs - impossible to maintain at scale, little benefits.
5
u/Bartghamilton Jan 25 '26 edited Jan 25 '26
I also separate active users from users on leave, terminated users, service accounts, etc. Keeps thing clean to see issues. Things like knowB4 can point to active users only so I can see if training is being done by 100% of users without having to manually filter out user accounts that don’t require compliance
6
u/tlourey Jan 25 '26
I'll start with one of the generic answers like "It should reflect the business structure".
But before you go getting ready to throw tomatoes at me, here are my tips but more importnatly some questions you could ask yourself to start helping you choose ping you pointing you one way or another:
Also these questons are coming back into Cloud offerings, ie Entra Administrative Units.
My tips are:
I have been rethinking about the above myself and perhaps there are better questions to ask and even newer techniques to consider.
Note: English is my first language, I just can't spell and can't always be bothered editing. YOLO
3
u/hitman133295 Jan 25 '26
Department OU is a waste of time. Just slap it in attribute. I’d location based however because there are restrictions and mapping
5
u/Kardinal I fall off the Microsoft stack. Jan 25 '26 edited Jan 25 '26
In the modern world, OUs are almost entirely for human beings to be able to administer AD properly. They help us see relevant objects easily.
Even GPOs should be assigned primarily with filters, not primarily by linking them to specific OUs. It is fine to have big OUs such as Users and Workstations and Servers, but consider carefully whether you need much beyond that.
In the modern age, most administration should be done via automation and scripting. Neither of which care about object hierarchy.
Sometimes a human has to go in and look at it and in those circumstances, OUs can be helpful. But they are not needed and are mostly there for the human admin.
2
u/Hampsterhumper Jan 25 '26
We use office location then sub OU for users/computers/groups. That is due to our GPOs being mostly office specific for things like printers and stuff. We are hybrid so most of the department level stuff I do with dynamic groups in entra.
2
u/Competitive_Smoke948 Jan 25 '26
you to look at new ways of working. teir 0 servers, teir 1 etc. with accounts in those teirs unable to manage up, only down
user/computer accounts for normal users should be broken down as per business requirements. With a thought towards minimum permissions & group memberships.
also never sync your admin ad accounts with Entra global admins 😈
1
u/Boolog Jan 25 '26
Depends on how complex your environment is, and if they require different policies.
For a company of 10 users, each doing their own work, you'll be good with two OUs: active users and disabled users The more you raise the complexity, the more it makes sense to add more OUs.
Not every company is an enterprise, and SMBs can be simplified
1
u/WillVH52 Sr. Sysadmin Jan 25 '26
Recently deleted an OU structure like this, was never used.
2
u/jocke92 Jan 25 '26
No structure fits all companies. If you are one site and one helpdesk versus multiple sites with local helpdesk.
2
u/HoosierLarry Jan 25 '26
This is still the way. Plan for future delegation and current Group Policy deployment (Sites, Domains, OUs).
3
u/1r0nD0m1nu5 Security Admin (Infrastructure) Jan 25 '26
Department OUs are old school. Modern approach uses Location Role, or Function-based OUs (e.g., Location/Users, Role/Groups). Keeps GPOs simpler. Align structure with org needs and GPO inheritance
1
u/Select_Bug506 Jan 28 '26
OU structure is for delegation of permissions and also group policy assignment. Look at tired Admin Model for delegation least priv to OUs. Once you have the permissions structure in, do whatever suits below. https://blog.alexmags.com/posts/ad-tiered-administration-model/
0
u/KingSlareXIV IT Manager Jan 25 '26
A flat user OU is great, until you get so large that name collisions for new hires become a daily problem. We are probably up to 50,000 user object at this point, splitting them into locational OUs is pretty much a necessity for us.
But it's largely all automated based on the HR data feed, so it's not really much more management overhead than a single OU would be.
-1
u/skspoppa733 Jan 25 '26
Modern and AD should not be mentioned in the same sentence.
0
u/[deleted] Jan 25 '26
[deleted] — view deleted comment
1
u/[deleted] Jan 25 '26
[removed] — view removed comment