Study guide
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites
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
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites
Key Takeaways Explain This Topic AI
Hyper-V is a Type 1 microkernelized hypervisor: the root partition owns the physical device drivers and every guest runs in a child partition with no direct hardware access.
Virtualization Service Providers in the root partition pair with Virtualization Service Clients in each guest and exchange I/O over the VMBus, which is why integration services must be current for good performance.
The host CPU must support and have enabled hardware-assisted virtualization (Intel VT-x or AMD-V), Second Level Address Translation (EPT or NPT), and hardware Data Execution Prevention.
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart installs the role on Windows Server; the reboot is mandatory because the hypervisor must load beneath the existing OS.
Nested virtualization is what allows a Hyper-V host to itself run inside a VM, and it is required for Hyper-V-isolated containers and WSL 2 inside a guest server.
Last updated: August 2026
Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites
Microsoft Hyper-V is an enterprise-grade, bare-metal virtualization platform built directly into Windows Server. This section establishes the foundation: the Type 1 bare-metal partition model, what the hypervisor actually owns versus what the parent partition owns, and the hardware prerequisites and installation paths the exam expects you to recognize. Virtual machine generations, Secure Boot, virtual TPM, Enhanced Session Mode, and the direct guest-access channels build on this model and are covered in section 7.2.
1. Hyper-V Type 1 Bare-Metal Hypervisor Architecture
Hyper-V uses a Type 1 (native/bare-metal) microkernelized hypervisor architecture. The hypervisor layer ( hvix64.sys or hvax64.sys ) loads directly on the physical processor before any operating system boots. It creates and manages isolated execution domains called partitions . +-----------------------------------------------------------------------------------------+
- | HYPER-V TYPE 1 HYPERVISOR ARCHITECTURE |
- | |
- | +-----------------------------+ +--------------------------------------+ |
- | | ROOT PARTITION | | CHILD PARTITION (GUEST VM) | |
- | | (Parent / Host OS) | | | |
- | | - Windows Server 2022/2025 | | - Windows Server / Client / Linux | |
- | | - Management Stack (WMI) | | - Virtual Applications & Services | |
- | | - Virtual Machine Worker | | | |
- | | Processes (vmwp.exe) | | +--------------------------------+ | |
- | | +-----------------------+ | | | Virtualization Service Clients | | |
- | | | Virtualization Service| | | | (VSCs: StorVSC, NetVSC, etc.) | | |
- | | | Providers (VSPs) | | | +--------------------------------+ | |
- | | +-----------+-----------+ | +------------------+-------------------+ |
- | +--------------|--------------+ | |
- | | ================================== | |
- | +====== | VMBus (Shared Memory) | ==+ |
- | ================================== |
- | | |
- | +---------------------------------------------------------------------------------+ |
- | | HYPER-V HYPERVISOR LAYER | |
- | | - Partitions Isolation, vCPU Scheduling, SLAT/EPT Memory Virtualization | |
- | +---------------------------------------------------------------------------------+ |
- | | |
- | +---------------------------------------------------------------------------------+ |
- | | PHYSICAL HARDWARE (x64 CPU, RAM, NIC, PCIe) | |
- | +---------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
- Core Architectural Components
Hypervisor Layer:
A thin layer of code that has direct, unmediated control over physical CPU scheduling, physical memory partitioning, and interrupt routing.
Enforces strict memory and compute isolation between partitions using hardware virtualization extensions (Intel VT-x / AMD-V) and Second Level Address Translation (SLAT).
Root Partition (Parent Partition):
The primary management partition created automatically when Windows Server boots with the Hyper-V role.
Runs the management operating system (Windows Server 2022/2025 Standard or Datacenter).
Controls physical hardware device drivers (storage controllers, physical network adapters, graphics adapters).
Hosts the Virtual Machine Management Service ( vmms.exe ) and spawns an isolated Virtual Machine Worker Process ( vmwp.exe ) for each running child VM.
Contains Virtualization Service Providers (VSPs) that service I/O requests from child partitions.
Child Partitions (Guest VMs):
Virtual execution environments instantiated by the root partition via the hypercall API.
Do not have direct access to physical hardware devices or the ability to manage other partitions.
Run guest operating systems (Windows Server, Windows Client, Linux distributions) containing Virtualization Service Clients (VSCs) (e.g., NetVSC for networking, StorVSC for synthetic storage).
VMBus (Virtual Machine Bus):
A high-speed, point-to-point, in-memory communications channel that interconnects child partitions directly to the root partition.
Avoids the substantial CPU overhead and latency of traditional hardware emulation by transferring requests and data buffers over partitioned shared memory.
2. Hyper-V Installation & Hardware Prerequisites
Before deploying Hyper-V in production, the physical server hardware must meet strict architectural criteria.
Hardware Prerequisites
Hardware Requirement Minimum Specification Verification / Technical Role
Processor Architecture 64-bit processor with x64 support Mandatory; 32-bit physical host processors are unsupported.
Hardware-Assisted Virtualization Intel VT-x or AMD-V Enabled in physical UEFI/BIOS; virtualizes CPU control registers.
Second Level Address Translation (SLAT) Intel Extended Page Tables (EPT) or AMD Nested Page Tables (NPT / RVI) Reduces hypervisor memory virtualization overhead by handling guest physical-to-host physical address mappings in hardware.
Hardware Data Execution Prevention (DEP) Intel Execute Disable (XD) bit or AMD No-Execute (NX) bit Enabled in UEFI/BIOS; mitigates buffer overflow exploits by preventing code execution in memory data pages.
VM Monitor Mode Extensions Hardware support for nested hypervisor instruction sets Required for nested virtualization and virtualization-based security (VBS).
- Validating Hardware Prerequisites # Validate Hyper-V hardware prerequisites via systeminfo
- systeminfo.exe
# Look for the 'Hyper-V Requirements' section at the end of the output:
- # VM Monitor Mode Extensions: Yes
- # Virtualization Enabled In Firmware: Yes
- # Second Level Address Translation: Yes
- # Data Execution Prevention Available: Yes
- # Alternative PowerShell query for firmware virtualization support
- Get-ComputerInfo -Property HyperVisorPresent, CsHypervisorPresent, DeviceGuard*
- Installing the Hyper-V Role via PowerShell
To install the Hyper-V role along with the PowerShell management module and Hyper-V Manager GUI console: # Install Hyper-V role with all management tools and initiate an automatic restart
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart
- # Verify successful installation post-reboot
- Get-WindowsFeature -Name *Hyper-V*
Note
On Server Core installations, -IncludeManagementTools installs the Hyper-V PowerShell module. The GUI Hyper-V Manager console ( virtmgmt.msc ) is excluded automatically since Server Core does not support desktop shell components.
Loading diagram... Hyper-V Type 1 Architecture, VMBus & VM Generation Stack
Operational Validation After Installation
Treat systeminfo.exe differently before and after the role is active. On a prospective host, its Hyper-V Requirements list must report Yes for VM Monitor Mode extensions, firmware virtualization, Second Level Address Translation, and Data Execution Prevention. On a running Hyper-V host, the tool instead reports that a hypervisor has been detected and does not display the individual requirements; that message confirms the hypervisor is already loaded rather than indicating a failed prerequisite.
Installing only remote management tools does not require SLAT because that workstation is not loading the virtualization components or running guests. Installing the server role does require the hardware features and a restart. During that restart, the hypervisor loads first and the Windows installation that used to run directly on the hardware becomes the root partition. The root partition then supplies device drivers and the management stack, while the hypervisor continues to enforce CPU scheduling and memory isolation.
A final deployment check is software compatibility. VMware Workstation, VirtualBox, and similar products that expect exclusive control of the same processor virtualization extensions can fail to start guests or run unreliably while the Hyper-V hypervisor is active. Diagnose that symptom as hypervisor contention, not as a missing virtual switch or damaged guest disk.