As an important administrative component in your Active Directory Domain O YOuth enable you to partition
air and organize domain objects into a hierarchical structure.
O use can help you to delegate rights to administrative groups enabling them to administer certain objects
or attributes of objects below that or you.
It helps you to apply group policies to users and computer objects below that of you and it helps you
to create a hierarchy that enables you to administer the objects in the domain quickly.
There are several strategies for design and O use structures.
Let's take a look at the O you design strategies that are the most common location based strategy.
This strategy uses locations for reached top level or you in the root of the domain.
These location based o use are the main organizational element of the O use structure.
For example a datum corporation might use a location based strategy to create a use for reach of its
physical locations in London Toronto and Sydney and then create additional or use for their branch distribution
centers.
Each aided yes a resource such as user groups and computers is located in the O U that corresponds to
the location where the resource resides.
The location based strategy is common when each location operates relatively independently or when many
tasks are delegated to centralized administrators.
For example the administrative staff in London can perform the main administrative duties.
Administrators in Sydney or Toronto have some delegated rights like accessing their users groups and
computers quickly.
It is advantages for the local staff to fulfil some administrative duties across different types of
objects in the same branch.
In addition you do not have to move objects frequently between the top level or use unless the objects
move to another physical location.
Moving objects to another physical location likely requires moving home folders or Microsoft Exchange
Server mail boxes.
The location based gratitude also works well for organisations that expect to expand into new locations
because you can add new locations easily to the O use structure.
The next strategies resource based strategy.
This strategy relates to the functions of resources that are in the O use structure.
Typically use separate resources by function or objects by type and you create or use to represent these
functions.
For example some common top level or use are servers workstations groups and to users the resource base
strategy is common in smaller organisations in organisations that administrative staff maintain sir
centrally and their administrative delegation is based on the object type rather than on their location
or department.
Examples of this administrative groups include helpdesk clients support virtual administration and application
specific support in large organisations.
It is likely that those top level 0 use are more defined in the next subordinate level.
For example the sorrow or so you might contain child or use named after their applications such as Microsoft
Exchange Sara or Microsoft sequel server.
The next strategy is organisation based strategy.
This strategy reflects the structure of the organisation's business logic top level or use represent
departments within the organisation such as sales research or finance.
This strategy works well if resources move frequently or if they are not affiliated with a physical
location and if there are few employees changes between departments.
You should consider this strategy when administrative tasks are delegated on a per department basis
rather than a publication base.
For example an organisation with Neverland sales teams and other units that are not location bound would
benefit from an organization based strategy.
However this strategy is not a good choice for organizations that frequently rely on their business
model or that encourage employees to shift between roles.
The next strategies multiple tenancy based strategy.
This strategy is suitable for organizations that required the active directory infrastructure the service
to other organizations.
This might be a group of affiliated organizations that share the same domain a hostage environment and
outsourced environment or remain a private or public cloud provider.
This strategy is appropriate when one organization maintains the Active Directory infrastructure while
another organization manages certain Active Directory objects or if the first organization relies completely
on the administrations of the host in the organization.
For example a datum might maintain 80 days for tree research and control so tree research might want
to administer their users groups and computers or use independently but might not want to manage Active
Directory replication and DNS control also relies full the I.T. staff from a datum for all these tasks.
In this scenario a region would create a top level or you for I.T. services where they maintain all
administrative accounts and group sound top level or use named a datum control store and trade with
storage for reach of the managed organizations under lease or use regular user group workstations and
perhaps server accounts are represented as deeper level the I.T. staff of the trade research would maintain
their own account set design in their multiple tenancy based strategy.
It is possible to allow different tenants to work together or to create privacy settings so that each
organization sees its own resources.
In this strategy include and or a separate a new organizations can be straight forward process and the
last in our list is hybrid strategy.
This strategy uses a combination of all use based on location organization and resources.
The multi tenancy based strategy is also a hybrid strategy.
Are other hybrid strategies might decide the locations at the top level and separate objects types on
the next level.
The structure of the hybrid strategy depends on the organizational requirements.
For example the server so you could contain or use for file servers IRS Sequel Server Exchange server
and other application servers the user or so you might contend location or department or use the workstation
so you might distinguish between desktop and laptops and the group so you could incorporate department
location project or application specific groups regardless of which strategy you use to design your
or your structure.
Always remember that the main purpose is to enable the implementation of an Active Directory administrative
tasks modal a second priority might be group policy.
It is also recommended separated administrative accounts and groups from regular user accounts and groups
that delegated administrators might administer.