Organizational Units

[Bill Hand]

I want to setup an OU structure like this:

Locations (OU)
|
|-NY (OU)
| |- ADMIN (OU)
| |- IT (OU)
|
|-NC

Is it bad to go three OU's deep? Should I just lump all the NY Users in the NY OU?

Thanks.

 

[Laura E. Hunter \(MVP\)]

The largest "gotcha" with nested OUs is in the area of Group Policy
processing: if you have a GPO linked to Locations, two GPOs linked to NY,
and another GPO linked to IT, it can create substantial logon times for a
user in the IT OU. This is something that warrants testing in your specific
environment, since network bandwidth between client and server will make a
difference in how quickly GPOs get copied from the server.

 

[Chriss3 [MVP]]

Design the directory as you want to administrate it, and after requirement
of policies. it's not too deep design.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup