When plan an Active Directory functionality you should consider the following high level aspects of
all you design.
The first aspect is administrative purpose.
The O use structure should rely on primarily to administrative purposes such as your Active Directory
tasks delegation modal and your GP.
Avoid mimicking your organizational chart unless it benefits the administrative modal organization charts
change frequently and it's not practical to change your or your structure that often.
If you have requests for department specific GP O's it might be preferable to reflect those departments
in a lower level of the O use structure.
However it is also likely that you have a security and distribution group to reflect the users in this
department and you can instead use security filtering for that purpose.
Users and managers usually do not see the O use structure so there is no benefit in list and corporate
hierarchies there.
If you want to enable users to browse the organizational structure ensure that you fill in the manager
attribute of the user object.
This enables users to use current and previous versions of Microsoft Outlook in combination with the
Exchange server message an infrastructure Microsoft Office 365 and Microsoft Exchange sort of SharePoint
Server to navigate through the organizational structure.
The O U is for administrative purposes only.
Another aspect is inheritance.
Inheritance is an important aspect of all new functionality both for delegation of control and GPO application.
You should design their or use structure to include objects that require the same administrative control
or group policy settings within the same you structure.
This way you can assign the delegation of control or the GPO was set in only once at a higher level.
In the all you structure rather than individually at each child level.
Remember that you can block inheritance for a certain child or use if you do not want the US to apply
the sentence for a higher or you level to a certain child or use.
And lastly the change aspect design your own use structure to accommodate change after you implement
an all you structure.
It can be difficult to change especially if you also change design strategies such as changing from
an organization based strategy to a resource based strategy.
Ensure that your or use structure leaves room for organizational growth and a reasonable level of structural
change.