Administer Window Server LU2
Administer Window Server LU2
Administer Window Server LU2
The Active Directory service is a distributed database that stores and manages information
about network resources, as well as application-specific data from directory-enabled
applications. Active Directory allows administrators to organize objects of a network (such as
users, computers, and devices) into a hierarchical collection of containers known as the logical
structure. The top-level logical container in this hierarchy is the forest. Within a forest are
domain containers, and within domains are organizational units.
Active Directory (AD) is a distributed database that stores objects in a hierarchical, structured,
and secure format. AD's objects typically represent users, computers, peripheral devices, and
network services. Each object is uniquely identified by its name and attributes. The domain,
the forest, and the tree represent logical divisions of an AD infrastructure.
Active directory is a technology that has information about all the objects in an organization’s
network.
It is a software to arrange, store information, provides access and permission based on those
information.
Active directory information is used to authenticate, authorize the users, computers, resources
which are part of a network.
In Windows 2000 Server and Windows Server 2003, the directory service is named Active
Directory. InWindows Server 2008 and Windows Server 2008 R2, the directory service is
An object is physical entities of a network. Like users, computers, resources like printers,
shared folders and files etc.
ADS object can be described by a subset of attributes. Object are explained by their attributes
like Name, location, Department etc.
Highly secure: using an active Directory it is possible to have layered security this means to
have policies and permission for security at different levels.
Easy to deploy: objects can be located anywhere physically yet can securely access domain
and network’s resources
Effective and efficient: easy and efficient search mechanism to locate an object. With a
centralized storage for user information this makes process of backup and restore a lot more
efficient.
Scalable: millions of users can be added to a single domain this make ADS highly scalable
and readily extensible.
Flexible: Ability to create trust relationships with external networks running previous versions
of Active Directory and even UNIX.
Active Directory is the central repository in which all objects in an enterprise and their
respective attributes are stored. It's a hierarchical, multi-master enabled database that can store
millions of objects. Changes to the database can be processed at any given domain controller
(DC) in the enterprise, regardless of whether the DC is connected or disconnected from the
network.
Active directory provide a flexibility to allow change in Domain controller in the organization
.but this may create problem when there is a data replication. Windows provide a conflict
resolution called algorithm handle by checking the last change or written last which is the last
writer wins and all the change is discarded.
There is a possibility that this methods can’t work properly. That is why they have introduced
single- master model
For certain types of changes, Windows incorporates methods to prevent conflicting Active
Directory updates from occurring.
Single-master model
To prevent conflicting updates in Windows, the Active Directory performs updates to certain
objects in a single-master fashion. In a single-master model, only one DC in the entire directory
is allowed to process updates. It's similar to the role given to a primary domain controller (PDC)
in earlier versions of Windows, such as Microsoft Windows NT 3.51 and 4.0. In earlier versions
of Windows, the PDC is responsible for processing all updates in a given domain.
Active Directory extends the single-master model found in earlier versions of Windows to
include multiple roles, and the ability to transfer roles to any DC in the enterprise. Because an
Active Directory role isn't bound to a single DC, it's referred to as a Flexible Single Master O
operation role (FSMO). Currently in Windows there are five FSMO roles:
The schema master FSMO role holder is the DC responsible for performing updates to the
directory schema, that is, the schema naming context or
LDAP://cn=schema,cn=configuration,dc=<domain>. This DC is the only one that can process
updates to the directory schema. Once the Schema update is complete, it's replicated from the
schema master to all other DCs in the directory. There's only one schema master per forest.
This FSMO role holder is only active when the role owner has inbound replicated the
schema NC successfully since the Directory Service started.
DCs and members of the forest only contact the FSMO role when they update the schema.
Domain Naming Master: The Domain Naming Master makes sure that you don’t create a
second domain in the same forest with the same name as another. It is the master of your domain
names. Creating new domains isn’t something that happens often, so of all the roles, this one
is most likely to live on the same DC with another role.
The domain naming master FSMO role holder is the DC responsible for making changes
to the forest-wide domain name space of the directory, that is, the
Partitions\Configuration naming context or LDAP://CN=Partitions, CN=Configuration,
DC=<domain>. This DC is the only one that can add or remove a domain from the
directory. It can also add or remove cross references to domains in external directories.
This FSMO role holder is only active when the role owner has inbound replicated the
configuration NC successfully since the Directory Service started.
Domain members of the forest only contact the FSMO role holder when they update the
cross-references. DCs contact the FSMO role holder when:
RID Master: The Relative ID Master assigns blocks of Security Identifiers (SID) to different
DCs they can use for newly created objects. Each object in AD has an SID, and the last few
digits of the SID are the Relative portion. In order to keep multiple objects from having the
same SID, the RID Master grants each DC the privilege of assigning certain SIDs.
The RID master FSMO role holder is the single DC responsible for processing RID Pool
requests from all DCs within a given domain. It's also responsible for removing an object from
its domain and putting it in another domain during an object move.
When a DC creates a security principal object, such as a user or group, it attaches a unique
Security ID (SID) to the object. This SID consists of:
A domain SID that's the same for all SIDs created in a domain.
A relative ID (RID) that's unique for each security principal SID created in a domain.
Each Windows DC in a domain is allocated a pool of RIDs that it's allowed to assign to the
security principals it creates. When a DC's allocated RID pool falls below a threshold, that DC
issues a request for additional RIDs to the domain's RID master. The domain RID master
responds to the request by retrieving RIDs from the domain's unallocated RID pool, and assigns
them to the pool of the requesting DC. There's one RID master per domain in a directory.
This FSMO role holder is active only when the role owner has inbound replicated the
domain NC successfully since the Directory Service started.
DCs contact the FSMO role holder when they retrieve a new RID pool. The new RID
pool is delivered to DCs through AD replication.
PDC (primary domain Controller) emulator FSMO role The PDC emulator is necessary to
synchronize time in an enterprise. Windows includes the W32Time (Windows Time) time
service that is required by the Kerberos authentication protocol. All Windows-based computers
within an enterprise use a common time. The purpose of the time service is to ensure that the
The PDC emulator of a domain is authoritative for the domain. The PDC emulator at the root
of the forest becomes authoritative for the enterprise, and should be configured to gather the
time from an external source. All PDC FSMO role holders follow the hierarchy of domains in
the selection of their in-bound time partner.
In a Windows domain, the PDC emulator role holder retains the following functions:
Password changes done by other DCs in the domain are replicated preferentially to the
PDC emulator. When authentication failures occur at a given DC because of an incorrect
password, the failures are forwarded to the PDC emulator before a bad password failure
message is reported to the user.
The PDC emulator performs all of the functionality that a Windows NT 4.0 Server-based
PDC or earlier PDC performs for Windows NT 4.0-based or earlier clients.
This part of the PDC emulator role becomes unnecessary under the following situation:
All workstations, member servers, and domain controllers (DCs) that are running Windows NT
4.0 or earlier are all upgraded to Windows 2000.
The PDC emulator still does the other functions as described in a Windows 2000 environment.
This FSMO role holder is always active when the PDC emulator finds the
fSMORoleOwner attribute of the domain NC head points to itself. There is no inbound
replication requirement.
DCs contact the FSMO role holder when they have a new password, or the local password
verification fails. No error occurs when the PDC emulator can't be reached or the
AvoidPdcOnWan registry value is set to 1.
When the Recycle Bin optional feature is not enabled, the Infrastructure FSMO role owner is
the DC responsible for updating a cross-domain object reference in the event that the referenced
object is moved, renamed, or deleted. In this case, the Infrastructure Master role must be held
by a domain controller that is not a GC server. If the Infrastructure Master runs on a GC server,
it will not update object information, because it does not contain any references to objects that
it does not hold. This is because a GC server holds a partial replica of every object in the forest.
When the Recycle Bin optional feature is enabled, every DC is responsible for updating its
cross-domain object references in the event that the referenced object is moved, renamed, or
deleted. In this case, there are no tasks associated with the Infrastructure FSMO role, and it is
not important which domain controller owns the Infrastructure Master role.
When an object in one domain is referenced by another object in another domain, it represents
the reference by:
• The GUID
• The SID (for references to security principals)
• The DN of the object being referenced
The infrastructure FSMO role holder is the DC responsible for updating an object's SID and
distinguished name in a cross-domain object reference.
If all the domain controllers in a domain also host the GC, then all the domain controllers have
the current data, and it is not important which domain controller owns the Infrastructure Master
(IM) role.
Active Directory stores copies of partitions on multiple domain controllers and updates
them through directory replication.
✓ A schema is the set of definitions of the object types and attributes that you use to
define the objects created in AD DS.
✓ A domain is a logical administrative container for objects such as users and computers.
A domain maps to a specific partition and you can organize the domain with parent-
child relationships to other domains. There is no limit of number of object that can be
contained in a domain.it is no necessary for an object to be in a same physical location.
Domain controller is the domain supreme authority; domain controller is responsible
for all the authentication, authorization, additions, deletions, edits, modification inside
a domain.
Physical component:
Physical components in AD DS are those objects that are tangible, or that described
tangible components in the real world.
Other components
✓ User component
Contains information about users like their first, middle and last names, login
credentials etc. For example say Aroma, Paul and Alex are employees of an
organization, then a user object can be created for each one of them, This object will
store various properties of the user like their name, the manager they report to, their
sub-ordinates etc.
✓ Contact component
Contains contact info about any person associated with the organization like a
supplier’s telephone number, mail address etc. For example an organization might want
to store details of people who are not directly associated with the organization such as
people who help in network maintenance or suppliers etc. These people usually do not
need to be given access to AD; only their details need to be stored which in this case is
their name and contact information, this can be done using a contact object.
✓ Group component: is a collection of Active Directory objects. The group can include
users, computers, other groups and other AD objects. Administrators can manage the
group as a single object that helps to simplify network maintenance and administration
What Are Domains and Forests? Define AD DS forests and domains - Learn | Microsoft
Docs
To learn more about domains and forests, you must first understand the logical and
physical structures of ActiveDirectory. This section describes how those structures
differ, and defines domains and forests in terms of the logical structure.
Active Directory stores network object information and implements the services that
make this information available and usable to users. Active Directory presents this
information through a standardized, logical structure that helps you establish and
understand the organization of domains and domain resources in a useful way. This
presentation of object information is referred to as the logical structure because it is
independent of the physical aspects of the Active Directory infrastructure, such as
the domain controllers required for each domain in the network.
Benefits of the Logical Structure
The logical structure provides a number of benefits for deploying, managing, and
• Low total cost of ownership. The reduced administration costs for network
management and the reducedload on network resources that can be achieved
with the Active Directory logical structure can significantly lower the total
cost of ownership.
An efficient Active Directory logical structure also facilitates the system integration
of features such as Group Policy, enabling desktop lockdown, software distribution,
and administration of users, groups, workstations, and servers. In addition, the
logical structure can facilitate the integration of services such as Exchange 2000,
public key infrastructure (PKI), and domain-based distributed file system (DFS).
Components of the Logical Structure
The logical structure consists of leaf object and container object components that
must conform to the hierarchical structure of an Active Directory forest. Leaf
objects are objects that have no child objects, and arethe most basic component of
the logical structure. Container objects store other objects and occupy a specific
level within the forest hierarchy.
The relationships among the components of the logical structure control access to
stored data and determine howthat data is managed across one or more domains
The logical structure of your organization is represented by the following Active Directory
components:
1. Organizational units
2. Domains
3. Trees
4. Forests
5. Objects
Component Description
Organization Organizational units are container objects. You use these container objects to arran
alUnits objects in a manner that supports your administrative purposes. By arranging o
organizational units, you make it easier to locate and manage them. You can also
the authority to manage an organizational unit. Organizational units can be nested
organizational units.
You can arrange objects that have similar administrative and security requirem
organizational units. Organizational units provide multiple levels of administrative a
so that you can apply Group Policy settings and delegate administrative control.
Domains Domains are container objects. Domains are a collection of administratively defined objects
that share a common directory database, security policies, and trust relationships with other
domains. In this way, each domain is an administrative boundary for objects. A single domain
can span multiple physical locations or sites and can contain millions of objects.
A domain is a collection of computers & servers that are part of the same centralized
database.
Many domains are available like: Single Domain, Parent Domain, Child Domain, Domain
tree, and Forest domain.
Current forest
Forests A forest is a complete instance of Active Directory. Each forest acts as a top-level container
in that it houses all domain containers for that particular Active Directory instance. A forest
can contain one or more domain container objects, all of which share a common logical
structure, global catalog, directory schema, and directory configuration, as well as automatic
two-way transitive trust relationships. The first domain in the forest is called the forest root
domain. The name of that domain refers to the forest, such as Nwtraders.msft.
By default, information in Active Directory is shared only within the forest. In this way, the
forest is a security boundary for the information that is contained in that instance of Active
Directory.
Site Objects Sites are leaf and container objects. The sites container is the topmost object in the hierarchy
of objects that are used to manage and implement Active Directory replication. The sites
container stores the hierarchy of objects that are used by the Knowledge Consistency Checker
(KCC) to effect the replication topology. Some of the objects locatedin the sites container
include NTDS Site Settings objects, subnet objects, connection objects, server objects, and
site objects (one site object for each site in the forest). The hierarchy is displayed as the
contents of the Sites container, which is a child of the Configuration container
Note
• You can view and manage components of the logical structure by using the
Active Directory Users and Computers, Active Directory Domains and Trusts,
and Active Directory Schema Microsoft ManagementConsole (MMC) snap-ins,
and other tools.
2.2.1. Proper installation of active directory Domain Service based on windows server
version.
2.2.1.1.2. Installing Active Directory Domain Services and promoting the server to a domain
controller
Note: Before installing Active directory first change name server and configure static IP address.
Run command prompt (cmd) as an administrator. If you are on Server Core this is likely already
open. If it is not, hold Ctrl+Alt+Del and select Task Manager. Then choose File -> Run new
task, type cmd, select Run with administrative privileges and click OK or hit Enter.
Step2. Enter PowerShell: Type the word PowerShell and hit Enter
Step3. Type y and hit Enter (assuming the server can be rebooted at this time)
Then type Get-AdDomain and hit Enter .This will show you information about your new
Domain
Step 6 .You can also open Active Directory Users and Computers and you will see your new
domain listed.
Prerequisites
Before installing, there are a few prerequisites that our server must meet:
Have a DNS server installed on your network (or, while setting up your AD Forest, the setup
wizard will ask you to add the role to the same server where you are installing ADDS)
d) Press “Next”
g) Press “Next”.
Choose “Add a new forest” and choose your “Root domain name”.
Press “Next”. You can safely ignore the DNS server message.
After the installation completed, you can now logon as the Domain Admin of the newly created
AD Forest.
In the left pane of ADUC, expand the folder containing the user account to be enabled/disabled.
Right click the user account and click Enable or Disable to enable/disable the user account.
In the left pane of ADUC, expand the folder containing the user account whose password is to be
reset.
Type and confirm the password in the appropriate fields. Select other password related options if
needed.
In the left pane of ADUC, right click the folder where the group account is to be created.
Type in a suitable name for the group. For group scope, select one among domain local, global,
and universal. For group type, select either security or distribution.
In the left pane of ADUC, right click the folder containing the group account to which you want
to add a member.
Type in the name of the objects you want to add to the group.
Click OK.
In the left pane of ADUC, right click the folder containing the group whose type or scope is to be
modified.
In the left pane of ADUC, right click the folder where the computer account is to be created.
In the left pane of ADUC, right click the folder where the computer account is to be created.
In the left pane of ADUC, right click the folder where the object is located.
4. On the Account tab, click Logon Hours, and then set the permitted or denied logon
hours for the user.
Additional considerations
To perform this procedure, you must be a member of the Account Operators group, Domain
Admins group, or Enterprise Admins group in Active Directory Domain Services (AD DS), or you
must have been delegated the appropriate authority. As a security best practice, consider using Run
as to perform this procedure.
Another way to open Active Directory Users and Computers is to click Start, click Run, and then
type dsa.msc.
To modify the logon hours for multiple users, press and hold down CTRL, and then click each
user. Right-click the selected users, and then click Properties. On the Account tab, click Logon
Hours, and then set the permitted or denied logon hours for the user.
By default, domain users are required to change their passwords every 42 days, as defined by
domain password policy.
If you find those password expiry notices annoying, you can set password to never expire for
domain accounts in Windows Server 2016, 2012, 2008, 2003.
Before getting started, you can check when your domain account password is going to expire.
Just open the Command Prompt as administrator, type the following command and press Enter.
This will display your account information, including when you last changed your password, and
when it expires.
In the Properties dialog, click the Account tab and check “Password never expires” under the
Account options section.
Method 2: Set Domain Account Password to Never Expire via PowerShell. Click Start, click
Administrative Tools, and then click Active Directory Module for Windows PowerShell. After
Replace pcunlocker with the name of your domain account. Set-LocalUser -Name "pcunlocker"
-PasswordNeverExpires 1
The Store password using reversible encryption policy setting provides support for applications
that use protocols that require the user's password for authentication. Storing encrypted passwords
in a way that is reversible means that the encrypted passwords can be decrypted. A knowledgeable
attacker who is able to break this encryption can then log on to network resources by using the
compromised account. For this reason, never enable Store password using reversible encryption
for all users in the domain unless application requirements outweigh the need to protect password
information
Best practices
Set the value for Store password using reversible encryption to Disabled. If you use CHAP
through remote access or IAS, or Digest Authentication in IIS, you must set this value to Enabled.
This presents a security risk when you apply the setting by using Group Policy on a user-by-user
basis because it requires opening the appropriate user account object in Active Directory Users
and Computers.