AIDS includes both logical and physical components.
You need to understand how AIDS components work together so that you can manage your infrastructure
efficiently.
In addition, you can use aid options to perform actions such as installing, configuring and updating
applications, managing the security infrastructure, enabling remote access service and direct access,
and issuing and managing digital certificates.
One of the most used AIDS features is group policy, which allows you to configure centralized policies
for managing most objects in AIDS.
Understanding the various AIDS components is important for use group policy successfully.
We'll talk about implementing group policies a bit later in more detail.
But for now, let's take a closer look at logical components of AIDS.
It is so logical components are structures that you use to implement Active Directory design that is
appropriate for an organisation.
As you can see, they have logical components and physical components.
Let's see what logical components are.
Partition a partition or name context is a portion of the Active Directory database.
By the way, I advise you to remember all these names because they are very crucial for understanding
how Active Directory works.
So back to partition.
Although the database is one file named and its date, different partitions contain different data.
For example, the schema partition contains a copy of Active Directory schema.
The configuration partition contains the configuration objects for the forest and the domain partition
contains the user's computers, groups and other objects specific to the domain.
Copies of a partition can be stored on multiple domain controllers and updated through directory replication.
Let's move on and take a look at schema.
Schema is the set of definitions of the object types and attributes that you use to define the objects
created in Active Directory.
Next on is domain.
A domain is a logical administrative container for objects such as users and computers.
A domain maps to a specific partition and can be organized with parent child relationships to other
domains.
Next up, we have domain three.
A domain three is a hierarchical collection of domains that share a common root domain and a contiguous
domain name system or DNS namespace.
Next up is Forest.
And Forest is a collection of domains that share a common address, root and schema, which have a two
way trust relationship.
Then we have a site.
A site is a container for added objects such as computers and services that are specific to their physical
location.
This is in comparison to the main, which represents the logical structure of objects such as users
and groups in addition to computers.
Next, we have a subnet.
A subnet is a portion of the network IP addresses of an organization assigned to computers.
In a site, a site can have more than one subnet, so a site is computers in physical location and subnet
is IP addresses assigned to this computers and a site hand can have more than one subnet.
Next up, we have Oyu and OYU is a container object for users, groups and computers that provides a
framework for delegating administrative rights and administration by by linking group policy objects
or GPOs.
So all use are created to make administrator.
Life easier instead of administration users or computers or groups, one by one you organize them together
in or use, which is a container.
And the last one is container.
A container is an object that provides an organizational framework for use in aid.
As some containers are created by default, you can create custom containers.
Containers cannot have GPOs linked to them.
So thing is in this way you can manipulate and do some actions with or use and you cannot do anything
with container like applying any policies on it.
Now besides logical components, we've got physical components.
We've got a domain controller.
It contains a copy of its database.
For most operations, each domain controller can process changes and replicate the changes to all the
other domain controllers.
In domain, we've got data stored.
A copy of the data store exists on each domain controller.
The Active Directory database uses Microsoft Jet database and stores the directory information in the
anti.
This dot did file and associated log files.
The default folder for these files is c drive colon backslash windows folder backslash ntds folder.
So if you want, you can go right now and find this folder where all the files are kept in case you've
got to run an domain controller at your hand and let's move on.
We've got also global catalog server as a physical component.
A global catalog server is a domain controller that hosts the global catalog, which is a partial read
only copy of all the objects in a multiple domain forest.
A global catalog speeds up searches for objects that might be stored on domain controllers in different
domain in the forest.
And the last component is read Only domain controller or raw DC and Row DC is a special readable installation
of add s row.
This is our common and branch offices where physical security is not optional.
IT support is less advanced than in the main corporate centers or line of business.
Applications need to run on a domain controller.