Active Directory Administration
Active Directory administration is the day-to-day management of Microsoft's directory service for Windows networks. It covers creating and organizing user accounts, groups, and computer objects, delegating permissions, applying Group Policy settings, and maintaining domain controllers so that authentication and authorization work reliably across the organization.
itWindows and Microsoft infrastructure | OpenSkills.info
Intro
Active Directory Administration
Active Directory Domain Services (AD DS) is Microsoft's directory service for Windows networks. It stores information about the objects on a network — user accounts, computer accounts, groups, printers, and shared resources — in a structured, hierarchical database, and it makes that information available to authorized users and administrators. When you sign in to a Windows domain computer, check group membership before opening a file share, or push a security setting to every machine in a department, AD DS is the system answering "who is this, and what are they allowed to do."
The useful mental model is a shared address book with a rulebook attached. The address book holds every user, computer, and group in the organization; the rulebook (security permissions and Group Policy) decides who can read or change each entry and what configuration gets pushed to which machines. Every domain controller holds a full copy of that address book for its domain and keeps it synchronized with every other domain controller, so a change made in one office is visible everywhere else within minutes.
Why AD DS exists
Before directory services, each Windows server kept its own local list of users and passwords. Ten servers meant ten separate accounts to create, update, and disable for every employee — and ten places for a former employee's access to linger. AD DS solves this by centralizing identity: create a user once, and that identity works across every computer, server, and application that trusts the domain. This is why AD DS underpins most on-premises Windows environments and remains the identity backbone that hybrid cloud setups (via Microsoft Entra Connect) synchronize into the cloud.
AD DS combines several pieces into one service:
- A structured data store — the directory itself — organized hierarchically so information is easy to find.
- The schema, a set of rules defining what classes of objects (users, computers, groups, and more) can exist in the directory, what attributes each object type can have, and the format of their names.
- A global catalog, a searchable index containing a subset of every object's attributes across the entire forest, so a query for "find this user" doesn't need to know which domain holds the answer.
- A query and index mechanism, so applications and users can search the directory efficiently.
- A replication service that copies directory changes to every domain controller in a domain, so any domain controller can answer requests with current data.
- Integrated security: a single username and password authenticates a user across the network, and access to directory objects is controlled the same way access to files is controlled — with permissions.
Who administers AD DS, and what they do
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview
Supports
- What AD DS is and what it stores (users, computers, groups, shared resources)
- AD DS core components: schema, global catalog, query/index mechanism, replication service, integrated security
- Definition of the schema as the rules for object classes/attributes
- Definition of the global catalog as a forest-wide search index
- https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/understanding-the-active-directory-logical-model
Supports
- Logical hierarchy of forest, domain tree, domain, organizational unit (OU)
- Forest definition (shared schema, configuration, global catalog) and automatic two-way transitive trusts between domains in one forest
- Domain definition as a directory partition and core administrative/authentication/replication boundary
- OU definition as a container for delegated administration and Group Policy application
- https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-fsmo-roles
Supports
- Definition and scope (forest-wide vs domain-wide) of all five FSMO roles
- Schema Master and Domain Naming Master as one-per-forest roles
- RID Master, PDC Emulator, and Infrastructure Master as one-per-domain roles
- PDC Emulator as authoritative for password changes, account lockouts, and forest time source
- Infrastructure Master's role update behavior and its interaction with global catalog placement
- Rationale for FSMO roles existing despite multimaster replication
- https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/replication/active-directory-replication-concepts
Supports
- Multimaster replication model
- Site, site link, and bridgehead server definitions
- Intra-site vs inter-site replication behavior (frequent/fast vs scheduled)
- Global catalog server definition (full replica of its own domain, partial replica of every other domain)
- Knowledge Consistency Checker (KCC) role in building replication topology
- https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-policy/group-policy-overview
Supports
- GPO definition and its two components (Group Policy container in the domain partition, Group Policy template in SYSVOL)
- GPOs link to sites, domains, and OUs
- Group Policy inheritance/cumulative application down the OU hierarchy
- Group Policy applied at computer startup and user sign-in, with periodic background refresh
- Client-side extension (CSE) role in applying policy settings
- OU as the lowest-level container to which Group Policy is assigned, and typical linking practice
- https://learn.microsoft.com/en-us/windows-server/security/kerberos/kerberos-authentication-overview
Supports
- Kerberos Key Distribution Center (KDC) running on domain controllers, using the AD DS database as its account store
- Single sign-on benefit of Kerberos within a domain/forest
- Mutual authentication as a Kerberos property NTLM lacks
- Delegation (a service acting on behalf of a client to another service)
- Renewable session tickets reducing the need for per-request domain controller contact, versus NTLM pass-through authentication
- https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-security-groups
Supports
- Security groups vs distribution groups
- Group scope table: domain local, global, universal — membership and permission-granting rules
- Assigning rights/permissions to groups rather than individual accounts
- Default groups location (Builtin/Users containers) and the AdminSDHolder protection mechanism
- https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/active-directory-integrated-dns-zones
Supports
- Active Directory-integrated DNS zones replicate via AD DS replication (multimaster) instead of classic zone transfers
- Secure dynamic updates
- ForestDnsZones and DomainDnsZones application directory partitions
- https://learn.microsoft.com/en-us/entra/identity/domain-services/concepts-forest-trust
Supports
- Trust direction (one-way/two-way) and transitivity (transitive/non-transitive) definitions
- All on-premises AD DS domain trusts within one forest are two-way and transitive by default
- Forest trusts connect exactly two forest root domains and are not implicitly extended to a third forest
- Trusted Domain Object (TDO) storage and the 30-day trust password rotation driven by the trusting domain's PDC Emulator
- Kerberos and NTLM referral processing across trust paths
- https://learn.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/remote-server-administration-tools
Supports
- RSAT's AD DS/AD LDS toolset: Active Directory Administrative Center, Active Directory Domains and Trusts, Active Directory Sites and Services, Active Directory Users and Computers, and the Active Directory module for Windows PowerShell
- https://learn.microsoft.com/en-us/powershell/module/activedirectory/
Supports
- Existence and purpose of the ActiveDirectory PowerShell module
- Cmdlet names referenced in this course (Get-ADUser, Get-ADGroupMember, Get-ADDomainController, New-ADUser)
