Study guide
14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
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
14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
Key Takeaways Explain This Topic AI
iSCSI Target Server is a role service under File and Storage Services that turns a Windows Server into IP-based block storage backed by VHDX files.
An iSCSI Qualified Name follows the form iqn.yyyy-mm.reversed-domain:unique-name and is how a target identifies which initiators may connect.
The iSCSI protocol listens on TCP port 3260, and initiators discover targets either by target portal address or through an iSNS server.
The Microsoft iSCSI Initiator requires a CHAP secret of 12 to 16 characters; mutual CHAP additionally authenticates the target to the initiator using a second, different secret.
MPIO with the Microsoft Device Specific Module aggregates multiple network paths into one logical disk, with Failover Only, Round Robin and Least Queue Depth policies.
Last updated: August 2026
iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
Storage Replica and Storage Spaces both assume the server already has block storage. iSCSI Target Server is how Windows Server provides it: a role service that presents virtual disks as SCSI logical unit numbers (LUNs) over a standard TCP/IP network, so any initiator — a Hyper-V host building a guest cluster, a Linux database server, a diskless workstation — can attach remote storage as though it were locally connected.
1. Architecture: Targets, Initiators and Portals
The iSCSI Target Server role in Windows Server transforms a standard Windows Server into an IP-based block storage SAN appliance, serving virtual disks over standard Ethernet fabrics. +-----------------------------------------------------------------------------------+
- | iSCSI SAN ARCHITECTURE & MPIO |
- | |
- | [iSCSI INITIATOR (CLIENT)] [iSCSI TARGET SERVER] |
- | - Windows Server / Hyper-V - Windows Server Role |
- | - IQN: iqn.1991-05.com.microsoft:... - Port: TCP 3260 |
- | +--------------------------+ +------------------------+ |
- | | NIC 1 (192.168.20.10) | ===(Path 1: TCP 3260)==>| Portal 1 (192.168.20.1)| |
- | | | [MPIO Load Balancing]| - Target: Target-VMs | |
- | | NIC 2 (192.168.21.10) | ===(Path 2: TCP 3260)==>| Portal 2 (192.168.21.1)| |
- | +--------------------------+ +------------------------+ |
- | | | |
- | [MPIO: Round Robin / Failover] [iSCSI Virtual Disks] |
- | Presents single Disk to OS (LUN 0: Data.vhdx) |
- +-----------------------------------------------------------------------------------+
- Core iSCSI Concepts
iSCSI Target: A logical entity created on the target server that manages connections and exposes one or more iSCSI Virtual Disks ( .vhdx files) as LUNs to authorized initiators.
iSCSI Initiator: The client system (Hyper-V host, database server) that mounts the remote LUNs. Each initiator is uniquely identified by its iSCSI Qualified Name (IQN) (e.g., iqn.1991-05.com.microsoft:srv-app01.corp.contoso.com ).
Target Portals: The IP addresses and port ( TCP port 3260 ) on which the iSCSI Target listens for incoming discovery and login requests.
Authentication: One-Way CHAP vs. Mutual CHAP
Unauthenticated / IQN Only: Access is restricted solely by matching the client's IQN or IP address.
One-Way CHAP (Challenge Handshake Authentication Protocol): The Target challenges the Initiator. The Initiator must supply a valid shared secret (password) to log in.
Mutual (Reverse) CHAP: The Target authenticates the Initiator, and the Initiator simultaneously authenticates the Target using two distinct secrets. This prevents rogue target spoofing and man-in-the-middle attacks on the storage fabric.
High Availability: Multipath I/O (MPIO)
To eliminate network interface and switch single points of failure, administrators configure Multipath I/O (MPIO) on iSCSI initiators.
Microsoft DSM (Device Specific Module): Aggregates multiple network paths to the same iSCSI LUN into a single logical disk presented to the operating system.
MPIO Load Balancing Policies:
Failover Only: Active/Passive configuration; traffic flows across a primary path, switching to standby only upon path failure.
Round Robin: Active/Active configuration; rotates I/O requests sequentially across all healthy network paths for aggregated throughput.
Least Queue Depth: Routes I/O to the path currently processing the fewest active requests. # Install iSCSI Target Server Role and MPIO Feature
Install-WindowsFeature -Name FS-iSCSITarget-Server, Multipath-IO -IncludeManagementTools
- # Create an iSCSI Virtual Disk (.vhdx)
- New-IscsiVirtualDisk -Path 'D:\iSCSIVirtualDisks\LUN-SQL01.vhdx' -SizeBytes 500GB
- # Create an iSCSI Target and assign the Initiator IQN
- New-IscsiServerTarget `
- TargetName 'Target-SQL01' `
- InitiatorIds @('IQN:iqn.1991-05.com.microsoft:srv-sql-01.corp.contoso.com')
- # Assign the Virtual Disk to the Target
- Add-IscsiVirtualDiskTargetMapping -TargetName 'Target-SQL01' -Path 'D:\iSCSIVirtualDisks\LUN-SQL01.vhdx'
- 2. Installation, Backing Storage and Where iSCSI Fits
iSCSI Target Server is a role service of the File and Storage Services role, found under File and iSCSI Services — not a standalone Windows feature. The client side needs nothing installed at all: the Microsoft iSCSI Initiator ships in every Windows Server and Windows client, exposed through iscsicpl.exe and the MSiSCSI service, which is set to Manual by default and must be started and set to Automatic.
Backing storage is a VHDX file on an NTFS or ReFS volume, which brings three practical consequences:
Virtual disks can be fixed , dynamically expanding or differencing , and the target server can be backed by anything Windows can mount — Storage Spaces, a hardware RAID set, a SAN LUN or plain direct-attached disks.
Because a LUN is a file, it can be snapshotted, backed up and moved with ordinary file tooling while the target is offline.
Differencing disks are what make large-scale diskless network boot economical. Microsoft's own testing deployed 256 computers in 34 minutes , and differencing VHDs can save up to 90 percent of the storage otherwise consumed by identical operating system images.
Because iSCSI Target Server supports non-Microsoft initiators , it is also the common answer for presenting Windows-backed block storage to Linux or appliance workloads that cannot speak SMB.
Important
For high availability, iSCSI Target Server itself is installed as a failover cluster role , which requires shared storage behind the cluster — Fibre Channel or a shared SAS array. Installing the role on two standalone servers and pointing initiators at both does not produce a highly available target; it produces two unrelated targets and a corrupted file system if both are written.
3. Access Control: IQNs, CHAP and Mutual CHAP
Access control has two independent layers, and the exam expects you to know that the first one is weak on its own.
Layer 1 — initiator identification. A target lists the initiators permitted to connect, identified by IQN , by IP address, by MAC address, or by DNS name. The iSCSI Qualified Name takes the form: iqn.yyyy-mm.<reversed-domain>:<unique-name>
- | | |
- | | +-- host-specific identifier
- | +-- naming authority that owned the domain at that date
- +-- year and month the naming authority was registered
Example: iqn.1991-05.com.microsoft:srv-sql-01.corp.contoso.com
An IQN is a name, not a credential — it is configured locally on the initiator and can be changed by anyone with administrative rights on that machine. IQN-only access control is therefore appropriate for an isolated storage VLAN, never for a shared network.
Layer 2 — CHAP. The Challenge Handshake Authentication Protocol proves possession of a shared secret without sending it over the wire:
- Mode Who proves what Secrets
- None Nothing; IQN or IP filtering only —
- One-way CHAP The target challenges the initiator One shared secret
Mutual (reverse) CHAP Each side challenges the other Two different secrets — reusing the same secret on both sides is rejected
Mutual CHAP is what defends against a rogue target : without it, an attacker who can answer at the target IP address can present a fake LUN to your initiator. Two constraints cause most configuration failures:
The Microsoft iSCSI Initiator requires the CHAP secret to be 12 to 16 characters. A shorter or longer secret is rejected at the initiator with a CHAP secret error, even though the target may have accepted it.
Mutual CHAP must be configured on both ends; the reverse secret is entered in the initiator's Configuration tab, not in the connection dialog, and omitting it produces an authentication failure that looks like a wrong password. # Target side: require one-way CHAP, then add a distinct reverse secret for mutual CHAP
- Set-IscsiServerTarget -TargetName 'Target-SQL01' `
- EnableChap $true -Chap (Get-Credential 'iscsi-chap-user') `
- EnableReverseChap $true -ReverseChap (Get-Credential 'iscsi-revchap-user')
- # Initiator side: start the service, register the portal, and connect with MPIO enabled
- Set-Service -Name MSiSCSI -StartupType Automatic; Start-Service MSiSCSI
- New-IscsiTargetPortal -TargetPortalAddress '192.168.20.1'
- Connect-IscsiTarget -NodeAddress 'iqn.1991-05.com.microsoft:tgt-sql01-target-sql01' `
- IsPersistent $true -IsMultipathEnabled $true `
- AuthenticationType MUTUALCHAP -ChapUsername 'iscsi-chap-user' -ChapSecret '<12-16 chars>'
- 4. Discovery, MPIO and Operational Checks
Initiators find targets in one of two ways. Target portal discovery requires each initiator to be told the target server's IP address and port explicitly — simple, and fine for a handful of hosts. The Internet Storage Name Service (iSNS) is a Windows Server feature that acts as a central registry: targets register themselves, initiators query the iSNS server, and adding a new target requires no change on any initiator. In a fleet of dozens of hosts, iSNS is the answer to "how do we avoid touching every initiator".
MPIO is not optional in production. A single NIC, cable or switch between an initiator and its LUN is a single point of failure for a disk , which is far more damaging than losing a network path. The Microsoft Device Specific Module presents multiple paths as one logical disk; the load-balancing policy determines how I/O is distributed:
Policy Behaviour Typical use
Failover Only One active path, the rest standby Paths of unequal speed, or an array that prefers a single controller
Round Robin Rotates I/O across all healthy paths Symmetric paths of equal speed — the common default
Least Queue Depth Sends I/O to the path with the fewest outstanding requests Mixed or bursty workloads where queue depth varies # Enable MPIO for iSCSI devices (a restart is required) and set the default policy
- Enable-MSDSMAutomaticClaim -BusType iSCSI
- Set-MSDSMGlobalDefaultLoadBalancePolicy -Policy RR
- # Verify what the initiator actually sees
- Get-IscsiSession | Format-Table InitiatorNodeAddress,TargetNodeAddress,IsPersistent,IsConnected
- Get-IscsiConnection| Format-Table ConnectionIdentifier,InitiatorAddress,TargetAddress
- Get-Disk | Where-Object BusType -eq 'iSCSI' | Format-Table Number,FriendlyName,OperationalStatus,Size
Tip
Two symptoms and their causes: the same LUN appears twice in Disk Management means MPIO is not claiming iSCSI devices, so run Enable-MSDSMAutomaticClaim -BusType iSCSI and restart. The disk disappears after a reboot means the connection was made without -IsPersistent $true , so it was never added to the favorite targets list.