Study guide

1.1 Deploying & Managing Domain Controllers On-Premises

Administering Windows Server Hybrid Core Infrastructure AZ-800

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About Exam AZ-800: Format, Scoring & the September 2026 Retirement

2 Chapter 1: Active Directory Domain Services Architecture & Deployment

1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships

3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join

2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale

4 Chapter 3: Hybrid Identity & Microsoft Entra Integration

3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

5 Chapter 4: Group Policy in AD DS and Hybrid Environments

4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

6 Chapter 5: Remote Server Management in Hybrid Environments

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion

7 Chapter 6: Hybrid Management with Azure Arc and Azure Services

6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration

7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization

9 Chapter 8: Hyper-V High Availability, Security & Containers

8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry

10 Chapter 9: Azure IaaS Virtual Machine Administration

9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity

11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution

10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC

12 Chapter 11: IP Addressing, DHCP & IPAM Management

11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments

13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access

12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections

14 Chapter 13: File Services, DFS, SMB & Azure File Sync

13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync

15 Chapter 14: Windows Server Storage Infrastructure & High Availability

14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O

1.1 Deploying & Managing Domain Controllers On-Premises

Key Takeaways Explain This Topic AI

Install-ADDSForest provisions a new forest root and Install-ADDSDomainController adds a replica DC; both accept -DatabasePath, -LogPath, and -SysvolPath to relocate NTDS.dit, edb.log, and SYSVOL onto dedicated volumes.

Forest and Domain Functional Levels (FFL/DFL) gate which Active Directory features are available; they are raised with Set-ADForestMode and Set-ADDomainMode and cannot be lowered below the Windows Server 2008 R2 baseline.

Server Core is the recommended domain controller installation option because it removes the GUI shell, Internet Explorer, and most binaries, shrinking the patch surface and reboot count relative to Desktop Experience.

Graceful decommissioning uses Uninstall-ADDSDomainController, which demotes the role and removes the DC's metadata automatically.

A domain controller that has failed unrecoverably must be removed with manual metadata cleanup in Active Directory Users and Computers, Sites and Services, and DNS, because the object cannot demote itself.

Last updated: August 2026

Deploying & Managing Domain Controllers On-Premises

Active Directory Domain Services (AD DS) forms the identity and authentication backbone of hybrid enterprise infrastructures. This section covers the on-premises half of that job: promoting and demoting domain controllers on physical hardware and on-premises hypervisors, choosing forest and domain functional levels, automating deployment with the ADDSDeployment module, and deciding between Server Core and Desktop Experience. Domain controllers hosted on Azure IaaS virtual machines — including the disk-caching rules, static addressing requirements, and virtualized domain controller cloning — are covered separately in section 1.2.

1. AD DS Architecture & Deployment Prerequisites

Before promoting a Windows Server instance to a domain controller, specific infrastructure prerequisites must be satisfied to ensure directory stability and replication integrity. +-----------------------------------------------------------------------------+

  • | AD DS PROMOTION PREREQUISITE CHECKLIST |
  • | |
  • | [1. IDENTITY & CREDENTIALS] ---> Enterprise Admins / Schema Admins for |
  • | Forest Root; Domain Admins for child/new |
  • | replica domain controllers |
  • | | |
  • | v |
  • | [2. NETWORK & DNS] ---> Static IP allocation, correct DNS client |
  • | pointing to existing DC/DNS servers |
  • | | |
  • | v |
  • | [3. TIME SYNCHRONIZATION] ---> Windows Time (W32Time) accuracy within |
  • | 5 minutes (Kerberos max clock skew) |
  • | | |
  • | v |
  • | [4. BINARIES & ROLES] ---> AD-Domain-Services role and RSAT tools |
  • | installed via Install-WindowsFeature |
  • +-----------------------------------------------------------------------------+
  • Core Prerequisite Dimensions

Administrative Privilege Delegation: Promoting the first domain controller in a new forest requires membership in the local server's Administrators group. Adding a new domain to an existing forest requires membership in Enterprise Admins . Modifying schema during preparation requires Schema Admins . Adding a replica DC to an existing domain requires Domain Admins in that target domain.

Domain Name System (DNS) Architecture: AD DS depends fundamentally on DNS Service Location ( SRV ) resource records (e.g., _ldap._tcp.dc._msdcs.<DomainName> ) to locate directory services. Before promoting a replica DC, its network adapter DNS client settings must point to an existing active AD DS DNS server—never to loopback ( 127.0.0.1 ) as the primary DNS during promotion.

Time Synchronization (Kerberos v5): The Kerberos authentication protocol tolerates a default maximum clock skew of 5 minutes (300 seconds). If system clocks between domain controllers or authenticating clients drift beyond this threshold, ticket granting and directory replication fail catastrophically.

2. Forest and Domain Functional Levels (FFL & DFL)

Functional levels determine the available capabilities of an Active Directory forest or domain, as well as the minimum Windows Server operating system version that can host a domain controller. +-----------------------------------------------------------------------------+

  • | FUNCTIONAL LEVEL PROGRESSION & FEATURES |
  • | |
  • | Windows Server 2012 R2 FFL/DFL |
  • | - Kerberos Armoring (FAST) & Protected Users Security Group |
  • | - Authentication Policies & Silos |
  • | | |
  • | v |
  • | Windows Server 2016 FFL/DFL |
  • | - Privileged Access Management (PAM) with Expiring Group Memberships |
  • | - NTLM fallback disabling across trust boundaries |
  • | | |
  • | v |
  • | Windows Server 2025 FFL/DFL |
  • | - 32k Page Database Engine (Extensible Storage Engine optimization) |
  • | - NUMA-Aware Active Directory scalability |
  • | - Channel Binding & LDAP signature enforcement by default |
  • +-----------------------------------------------------------------------------+

Key Functional Level Mechanics:

Elevation Invariance: Forest and Domain Functional Levels can be raised using PowerShell cmdlets ( Set-ADForestMode and Set-ADDomainMode ), but they cannot be lowered below Windows Server 2008 R2. If raised to Windows Server 2016, all older domain controllers (e.g., Windows Server 2012 R2) must have been demoted prior to level elevation.

Dependency Hierarchy: The Forest Functional Level can never be higher than the lowest Domain Functional Level in any domain across the forest. Conversely, a domain's DFL can be equal to or higher than the FFL.

Privileged Access Management (PAM) Expiring Links: Introduced in Windows Server 2016 FFL, this feature enables time-to-live (TTL) memberships in administrative groups, allowing Just-In-Time (JIT) access without manual group pruning.

3. PowerShell Deployment Automation ( ADDSDeployment Module)

Deploying domain controllers via GUI (Server Manager) has been superseded in enterprise environments by declarative, repeatable PowerShell automation using the ADDSDeployment module.

Primary Deployment Cmdlets

Deployment Target Cmdlet Primary Parameters

New Forest Root Install-ADDSForest -DomainName , -DomainNetbiosName , -ForestMode , -DomainMode , -InstallDns , -DatabasePath , -LogPath , -SysvolPath

New Child Domain Install-ADDSDomain -NewDomainName , -ParentDomainName , -DomainType ChildDomain , -Credential , -InstallDns

New Tree Domain Install-ADDSDomain -NewDomainName , -NewDomainNetbiosName , -DomainType TreeDomain , -ForestName , -Credential

Replica DC in Existing Domain Install-ADDSDomainController -DomainName , -Credential , -SiteName , -InstallDns , -NoGlobalCatalog , -ReplicationSourceDC

  • Automated Forest Root Promotion Script # Install the AD DS role and management tools
  • Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools
  • # Configure SafeMode Administrator Password (DSRM)
  • $SecureDSRMPassword = ConvertTo-SecureString 'P@ssw0rd2026!Secure' -AsPlainText -Force
  • # Promote server to the Forest Root Domain Controller
  • Install-ADDSForest `
  • DomainName 'corp.contoso.com' `
  • DomainNetbiosName 'CORP' `
  • ForestMode 'WinThreshold' `
  • DomainMode 'WinThreshold' `
  • InstallDns:$true `
  • DatabasePath 'F:\NTDS' `
  • LogPath 'F:\NTDS' `
  • SysvolPath 'F:\SYSVOL' `
  • SafeModeAdministratorPassword $SecureDSRMPassword `
  • NoRebootOnCompletion:$false `
  • Force:$true

Tip

Parameter Deep Dive: WinThreshold : In PowerShell cmdlets such as Install-ADDSForest and Set-ADForestMode , the string value 'WinThreshold' or 'Windows2016Forest' specifies the Windows Server 2016 functional level. Windows Server 2019 and Windows Server 2022 operate at the Windows Server 2016 functional level baseline.

4. Server Core vs Desktop Experience for Domain Controllers

Microsoft strongly recommends deploying domain controllers using the Server Core installation option rather than Server with Desktop Experience. +-----------------------------------------------------------------------------+

  • | SERVER CORE VS DESKTOP EXPERIENCE FOR DCs |
  • | |
  • | DIMENSION SERVER CORE DESKTOP EXPERIENCE |
  • | --------------------+----------------------------+------------------------|
  • | Attack Surface | Minimal (No Shell, No IE, | Large (GUI components, |
  • | | GDI32 restricted) | explorer.exe, themes) |
  • | Patch Reboots | ~60% fewer reboots required| Frequent patch cycles |
  • | Memory Footprint | ~512 MB - 1 GB RAM idle | ~2 GB - 3 GB RAM idle |
  • | Disk Consumption | ~10 GB OS footprint | ~28 GB OS footprint |
  • | Management Model | Remote: WAC, RSAT, SSH, | Local console or RDP |
  • | | PowerShell Remoting | Desktop sessions |
  • +-----------------------------------------------------------------------------+

Important

Headless DC Management Principle: Running Server Core eliminates local interactive desktop logons by administrators, enforcing the principle of tier-0 administrative isolation. All day-to-day administration must be conducted through remote management tools, including Windows Admin Center (WAC) , Remote Server Administration Tools (RSAT) , and PowerShell Remoting over WinRM/HTTPS .