Objects that aren??™t containers can be considered
files that can be moved around into different folders depending on where you want
them. How does this play out in real life? Depending on your organization, you may
decide to create an OU for each major department in the organization, such as IT, HR,
Sales, Engineering, and Finance. Each of these OUs can then contain all the users, workstations,
and even security and distribution groups associated with that department.
You can even create sub-OUs??”for example, you can have separate containers for user
accounts and for computer accounts.
The key factor here is that you decide. Many best practices around Active Directory
are published on the Microsoft TechCenter Web site. No one can tell you that it has to be
done a certain way. No one will know your organization better than you, so you need to
take that into consideration when designing an OU structure. At the end of the day, many
factors come into play when planning an OU structure: Some of them might have to do
with your political boundaries, while others may be directly related to the group policies
you would like to implement. For example, you could tie a restrictive set of policies for
the Sales OU so that sales staff can perform only certain actions on their workstations,
while providing a more lax policy on the IT OU so that the IT staff can perform necessary
administrative functions without being locked down.
Pages:
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143