We will be undergoing scheduled maintenance on May 20th, 2013 at 02:00 GMT.
Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
Organizational units, OUs are new to Windows 2000 and carried over to Windows Server 2003. An Organizational unit can best be thought of as containers and this chapter will discuss what Organizational units are and they are used in our Active Directory. In particular we are going to discuss the purpose of OU, modifying OU permissions, delegating administrative authority and distribution of group policy. So, let us talk about the purpose of OUs first. The main purpose is of OUs are 2 things. Number 1 to delegate administrative control rather than having to put in administrator in charge of entire domain we can simply allow them to manage a certain part of our domain. We do not have to create a new domain in order to give them some administrative authority over a section of our domain. It is sort like of you if you have ever taught Sunday school if you have not this analogy will not make sense. If you teach Sunday school and you look down the hall, And you see all of these doors and all of these doors are going to classrooms and in each one of these classrooms, there is supposed to be an instructor but let us say that somebody does not show up then they would take the students that were supposed to be in that classroom, where the instructor did not show up and they would put those students into another classroom with another instructor. So my question is before they move the students did they change anything about the students? The answer is, no they did not. Did they change anything about the instructor before they put new student into the instructor's class? The answer is, no they did not. But when they put the new students in and they shut the door are those students under the responsibility of the instructor. And yes they are instructor's responsibility because now they are in his classroom as well. Same thing is h organizational unit. If I put you in charge of an organizational unit and only has a certain number of objects in it and then I add additional objects to it, you are responsible for those as well just because I put them I your container. We will talk about how we delegate administrative control to OUs. We can also use OUs to distribute group policy. Group policies are not policy for groups. Lot of people get there confused because of the term group policy. But it has got nothing to do with the kind if group we have been talking about. It doesn't have anything to do with global groups or domain local groups or universal groups. Group policies are groups of policies that are used to manage sites, domains and OUs. Rarely sites, every now and then domains but most of the time OUs. So group policies are used to set standards or set security settings or roll out software to groups of individuals based on the OUs that they are in. Groups of users, groups of computers or both and therefore OUs are used to distribute those group policies. So those are the two main reasons for OUs. OUs do not have their own security context. We can assign permissions to someone to manage an OU. But the OU itself is not a security context like a domain in another words you don not logon to an OU but OUs are containers that we use for 2 reasons. Number 1, to delegate administrative control and 2, to distribute group policies. So in our next section we are going to focus more on the first reason to have OUs. Delegation of administration control; that is next.
| Course: | Microsoft Windows Server 2003 (70-290) |
| Author: | Bill Ferguson/Certified Instructor |
| SKU: | 33497 |
| ISBN: | 1932072918 |
| Release Date: | 2004-06-03 |
| Duration: | 8.5 hrs / 107 lessons |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |