Ad Structure
To get a basic understanding of what I believe an Active Directory Structure should look like, I imagined it as somewhat like and organizational chart. The organization or in this case the Active Directory structure consist of many parts. Like any other organization all the parts must have an established relationship and must all be able to communicate within the structure for a common goal or purpose. I will attempt to lay out in this paper, my understanding of those relationships and their functions in Active Directory.
Like any good organization, in the planning phase, there needs to be a good outline of what we want the organization to look like, what role we want each part of the organization to perform and a name for each separate part.
To begin, we need to know a grasp a basic understanding of what Active Directory is and how it relates to Schema. Then the paper will attempt to give a basic description of how all the parts of the structure work together.
The Schema defines definition of all object classes, and attributes that make up those object classes, that can be stored in the directory. The schema itself is stored in the directory in the schema partition in the directory and is replicated among all the domain controllers in the forest. This way, any change that is made to the schema is replicated to every domain controller in the forest.
An Active Directory structure is hierarchical in nature and its objects fall within the categories of resources, services and users and stores information and settings in a central database. Active Directory can also be used to assign policies, deploy software, and apply critical updates to an organization or enterprise level.
Now that Schema and Active Directory have been put into simple terms, our organization can move on to a basic understanding of Forrest, Domains and Operational Units. A Forrest is a collection of Domains and a domain is a collection of Operational...
View Full Essay