Home AZ-802 Server Prep
Windows Server Administrator Associate

The AZ-802 Windows Server guide

AZ-802 replaced AZ-800 and AZ-801 on September 30, 2026. It's one exam covering the whole Windows Server job, on-prem and hybrid: Active Directory, Hyper-V, DNS and DHCP, file services and storage, hardening, and troubleshooting, plus the Azure services that manage servers anywhere (Arc, Update Manager, Azure Files). Expect detailed "which feature, which setting" questions more than design questions.

01 · Format

What you're walking into

700passing score out of 1000 (scaled, not a %)
40–60questions, typically about 50
~100 minfor questions; plan on ~2 hours total
1 examearns Windows Server Administrator Associate
  • Question types: single choice, multi-select, drag-and-drop ordering (for example, the steps to restore a deleted object), hot-area (pick the PowerShell cmdlet or parameter), Yes/No series, and case studies.
  • Command recognition matters. You won't type commands, but you'll often pick the right cmdlet or tool from a list. The "Commands to recognize" section below covers the common ones.
  • Yes/No series: each proposed solution is judged on its own, and you can't go back.
  • Microsoft Learn is available during the exam (open book). Use it only to check a specific limit or parameter.
  • Most questions cover features that are generally available. Windows Server 2025 features (dMSA, OSConfig, SMB over QUIC in Standard and Datacenter, hotpatching) are fair game.
02 · Weighting

Domain map

Weights are from Microsoft's official AZ-802 study guide. The "if you passed AZ-104" column estimates how much is new for someone coming from Azure administration.

DomainWeightIf you passed AZ-104Focus
Deploy and manage AD DS20–25%HighFSMO, RODC, trusts, sites and replication, service accounts, Group Policy processing.
Manage storage and file services15–20%MediumAzure File Sync, FSRM, DFS, SMB over QUIC, Storage Spaces / S2D, Storage Replica, BitLocker.
Monitor and troubleshoot15–20%HighPerfmon, event forwarding, AD Recycle Bin, DSRM, SYSVOL, replication, Kerberos, secure channel.
Manage Windows Server in a hybrid environment10–15%MediumWindows Admin Center, PowerShell double-hop and JEA, Azure Arc, Update Manager, runbooks.
Manage VMs10–15%MediumHyper-V features (nested, PowerShell Direct, GPU, checkpoints, Replica, SET) and Azure VM basics.
On-prem and hybrid networking10–15%MediumDNS zones, forwarding, policies, DNSSEC, hybrid name resolution, DHCP scopes and failover.
Secure Windows Server10–15%HighCredential Guard, App Control, LAPS, OSConfig, fine-grained passwords, Protected Users, DC hardening.
03 · Schedule

A two-week study plan

Day 1

Baseline

Take the full practice exam timed, before studying. Use the domain bars on the results page to rank your weak areas.

Days 2–5

AD DS and troubleshooting

Together these are about 40% of the exam, and many troubleshooting questions are about AD. Read both cheat sheets, then practice both domains to 80%.

Days 6–9

Storage, VMs, networking

Work through the remaining cheat sheets. If you have a lab, build a two-node Hyper-V setup and try Replica, checkpoints, and a file server with FSRM.

Days 10–13

Full exams

A full timed exam every other day, with review of every miss. Drill flashcards daily, especially the commands.

Day 14

Light review

Commands, numbers, and traps only. Then rest.

04 · AD DS · 20–25%

Active Directory cheat sheet

FSMO roleScopeWhat breaks when it's down
Schema masterForestSchema extensions (for example, installing Exchange or a new DC version)
Domain naming masterForestAdding or removing domains
RID masterDomainDCs eventually can't create new users, groups, or computers once their RID pool runs out
PDC emulatorDomainTime sync source, password change priority, account lockout processing, GPO editing default
Infrastructure masterDomainCross-domain object references (irrelevant if every DC is a global catalog)

Domain controllers

  • Transfer a FSMO role when the holder is online. Seize only when it's permanently gone (Move-ADDirectoryServerOperationMasterRole -Force or ntdsutil). A server whose role was seized must never come back online.
  • DCs in Azure: static private IP, NTDS database and SYSVOL on a data disk with host caching set to None, an AD site and subnet for the VNet, and VNet DNS servers pointed at the DCs.
  • Install from media (IFM, ntdsutil ifm) to avoid replicating a large database over a slow link.

Read-only DCs

  • For branch sites with weak physical security. No writable copy of AD, and by default no cached passwords.
  • Password Replication Policy: add users and computers to Allowed RODC Password Replication Group (or the RODC's allow list). The Denied group always wins.
  • Staged install: a Domain Admin pre-creates the RODC account and delegates installation to a local branch admin, who doesn't need Domain Admin rights.
  • Administrator role separation: a delegated local admin can manage the RODC without any domain rights.
  • If an RODC is stolen: delete its computer account and choose to reset the passwords of all cached accounts.

Trusts

  • Forest trust: between two forest roots. Transitive across all domains in both forests. Kerberos.
  • External trust: domain to domain, non-transitive. Used for old NT-style or single-domain needs.
  • Shortcut trust: inside one forest, between two deep child domains, to speed up authentication.
  • Realm trust: to a non-Windows Kerberos v5 realm.
  • Selective authentication: users from the trusted side need the Allowed to Authenticate permission on each computer they use. SID filtering (quarantine) is on by default for external and forest trusts.

Sites & replication

  • Sites map to IP subnets so clients find the nearest DC. Site links have a cost (lower is preferred) and a replication interval (default 180 min, minimum 15).
  • Intrasite replication uses change notification (about 15 seconds). Intersite follows the site link schedule.
  • The KCC builds the topology automatically. The ISTG picks bridgehead servers for each site.
  • A site without a global catalog: turn on universal group membership caching so logons don't depend on the WAN.
  • Account lockouts and RID changes replicate urgently (immediately), even between sites.

Security principals

  • Group scopes: global (members from own domain), domain local (permissions in own domain, members from anywhere), universal (forest-wide, stored in the GC). Pattern: AGDLP.
  • gMSA: password managed by AD and rotated automatically (every 30 days), usable on many servers. Requires a KDS root key (Add-KdsRootKey, usable after 10 hours).
  • sMSA: same idea but for a single server.
  • dMSA (Windows Server 2025): migrates an existing legacy service account to a managed account, binding it to specific machines.
  • Install on the server with Install-ADServiceAccount, then test with Test-ADServiceAccount.

Group Policy

  • Processing order: Local → Site → Domain → OU (LSDOU). The last applied wins.
  • Enforced on a link beats Block Inheritance on a child OU.
  • Security filtering (default Authenticated Users, which needs Read) and WMI filtering narrow which users or computers apply a GPO.
  • Loopback processing: user settings come from the GPOs linked to the computer's OU (Merge or Replace mode). Used for kiosks and RDS hosts.
  • Preferences (drive maps, printers, registry, local groups) aren't enforced: users can change them. Item-level targeting filters each item.
  • Central store: copy ADMX files to SYSVOL\…\Policies\PolicyDefinitions so all admins use the same templates.
  • Refresh: every 90 minutes ± 30 on members, 5 minutes on DCs. gpupdate /force, gpresult /r.
05 · Hybrid management · 10–15%

Hybrid management cheat sheet

Remote management

  • Windows Admin Center: browser-based server management. Install it as a gateway on-prem, or use it in the Azure portal for Azure VMs and Arc-enabled servers.
  • PowerShell remoting uses WinRM (HTTP 5985 / HTTPS 5986).
  • Double-hop problem: a remote session can't pass your credentials to a third server. Fix it with resource-based Kerberos constrained delegation (preferred). CredSSP works but exposes credentials. JEA endpoints with a gMSA are another option.
  • OpenSSH Server is included in Windows Server 2025 but not enabled by default. Enable the sshd service.
  • RDP: restrict with Network Level Authentication, and prefer Remote Credential Guard or Restricted Admin mode for admin sessions.

Just Enough Administration

  • Lets users run only specific cmdlets and parameters as an admin, without being an admin.
  • Role capability file (.psrc): which cmdlets, functions, and parameters are visible.
  • Session configuration file (.pssc): maps groups to roles and sets RunAsVirtualAccount or a gMSA.
  • Register with Register-PSSessionConfiguration. Users connect with Enter-PSSession -ConfigurationName.
  • Transcripts record everything users do.

Azure Arc

  • Install the Connected Machine agent (azcmagent). It needs outbound HTTPS 443 only, with no inbound ports, optionally through a proxy or Private Link scope.
  • Onboard at scale with a service principal and a generated script, or through Group Policy or Configuration Manager.
  • Once onboarded, the server is an Azure resource: RBAC, tags, Azure Policy, machine configuration (guest configuration), and Defender for Servers.
  • VM extensions on Arc servers: Azure Monitor Agent, Custom Script, Defender, Key Vault, Hybrid Runbook Worker.
  • azcmagent show and azcmagent check troubleshoot connectivity.

Updates & automation

  • Azure Update Manager: assess and patch Azure VMs and Arc servers. Periodic assessment checks every 24 hours. Maintenance configurations schedule installs.
  • Hotpatching installs security updates without a reboot (Azure Edition, or Arc-enabled Windows Server 2025 with a subscription).
  • Azure Automation runbooks (PowerShell or Python), authenticated with a managed identity. To run against on-prem resources, use a Hybrid Runbook Worker (extension-based).
06 · Virtual machines · 10–15%

Hyper-V and Azure VM cheat sheet

Guest access

  • Enhanced Session Mode: VMConnect over RDP internally, giving clipboard, drive, and USB redirection. Enable it on the host and in VMConnect.
  • PowerShell Direct: Enter-PSSession -VMName from the host to a Windows guest over the VMBus. No network needed. You need guest credentials.
  • SSH Direct (hvc): the same idea for Linux guests.
  • Integration services: heartbeat, shutdown, time sync, KVP exchange, VSS (backup), and Guest services (Copy-VMFile, off by default).

Memory, CPU & devices

  • Dynamic Memory: startup, minimum, maximum, buffer, and weight. Runtime memory resize changes static memory while the VM runs.
  • Nested virtualization: VM off, Set-VMProcessor -ExposeVirtualizationExtensions $true, turn off Dynamic Memory, and enable MAC address spoofing (or use NAT) so nested VMs get network access.
  • Discrete Device Assignment: passes a whole PCIe device (GPU, NVMe) to one VM.
  • GPU partitioning (GPU-P): shares one physical GPU among several VMs. Windows Server 2025 supports live migration with GPU-P.

Disks & checkpoints

  • VHDX: up to 64 TB, 4K sectors, resilient to power loss. VHD: 2 TB. Types: fixed, dynamically expanding, differencing.
  • Shared VHDX / VHD Set (.vhds) gives shared storage for guest failover clusters.
  • Production checkpoints (default) use VSS inside the guest, so they're application-consistent. Standard checkpoints also save memory state.
  • Checkpoints aren't backups. Delete them so the AVHDX merges back into the parent disk.
  • Generation 2: UEFI, Secure Boot, boot from SCSI, virtual TPM. Generation can't be changed after creation.

Networking

  • Virtual switch types: External (physical network), Internal (host and VMs), Private (VMs only).
  • Switch Embedded Teaming (SET) is the host teaming method for Hyper-V switches and works with RDMA. LBFO teaming isn't supported on new Hyper-V switches.
  • Guest NIC teaming: two vNICs, each with "Allow this network adapter to be part of a team in the guest OS" enabled.
  • NAT network: Internal switch plus New-NetNat.

High availability

  • Failover cluster with Cluster Shared Volumes: live migration with no downtime, automatic restart on another node after a host failure.
  • Shared-nothing live migration moves a running VM and its storage between non-clustered hosts.
  • Hyper-V Replica: asynchronous replication to another host every 30 seconds, 5 minutes, or 15 minutes. Up to 24 additional recovery points. Extended replication adds a third site. Use the Hyper-V Replica Broker role on clusters.
  • Replica failover types: test (isolated copy), planned (no data loss, source shut down first), unplanned (source down).
  • Cluster-Aware Updating patches nodes one at a time, draining roles first.

Windows Server VMs in Azure

  • Resizing may need the VM deallocated if the new size isn't available on the current hardware cluster.
  • Availability sets (99.95%) vs zones (99.99%). VM Scale Sets to scale out.
  • Just-in-time VM access (Defender for Servers Plan 2) opens RDP/SSH in the NSG only on request, for a limited time.
  • Azure Bastion: RDP/SSH in the browser with no public IP on the VM.
  • Static private IPs are set on the NIC in Azure, never inside the guest OS.
07 · Networking · 10–15%

DNS & DHCP cheat sheet

DNS zone or settingUse
AD-integrated primaryStored in AD, multi-master, secure dynamic updates. Replication scope: all DNS servers in the forest, the domain, or a custom partition.
SecondaryRead-only copy using zone transfers. Works with non-AD DNS servers.
Stub zoneHolds only NS, SOA, and glue records, so it updates automatically when the other zone's name servers change.
Conditional forwarderSends queries for one specific domain to specific servers. Static, so you update it by hand.
ForwardersSend all queries the server can't answer to upstream servers.

DNS features

  • DNS policies: answer differently by client subnet, time of day, or interface. Uses client subnets and zone scopes. Used for geo-location routing and split-brain DNS.
  • DNSSEC: sign the zone (KSK and ZSK). Resolvers validate with trust anchors. Clients require validation through the NRPT (via Group Policy).
  • Scavenging removes stale dynamic records: no-refresh 7 days plus refresh 7 days by default. Enable it on the zone and on at least one server.
  • Record types: A/AAAA, CNAME, MX, SRV (how clients find DCs), PTR (reverse), NS, SOA, TXT.

Hybrid name resolution

  • Azure VMs joined to AD: set the VNet's custom DNS servers to the DCs.
  • DCs in Azure that need Azure private DNS zones: forward to 168.63.129.16 (Azure's resolver).
  • On-prem servers resolving Azure private zones (private endpoints): conditional forwarder to an Azure DNS Private Resolver inbound endpoint.
  • Azure resources resolving on-prem names without custom DNS on VMs: Private Resolver outbound endpoint plus a forwarding ruleset.

DHCP

  • A domain-joined DHCP server must be authorized in AD before it hands out leases.
  • Options precedence (most specific wins): reservation → scope → server. Common options: 003 router, 006 DNS servers, 015 DNS domain name.
  • Exclusions keep addresses inside a scope from being leased. Reservations tie an IP to a MAC address.
  • Superscope: groups scopes for multiple logical subnets on one physical segment.
  • DHCP relay agent (or the router's IP helper) forwards broadcasts to a DHCP server in another subnet.
  • A client with a 169.254.x.x address (APIPA) didn't reach any DHCP server.
  • You can't run your own DHCP server for VMs inside an Azure VNet. Azure assigns IPs.

DHCP failover

  • Two servers share lease information for a scope (IPv4 only).
  • Load balance mode: both servers answer, 50/50 by default.
  • Hot standby mode: the partner only answers when the primary is down. It keeps 5% of addresses by default. Good for a branch backed up by a central server.
  • MCLT (maximum client lead time, default 1 hour) controls how long a partner waits before taking over the whole scope.
  • Older split-scope (80/20) designs are replaced by failover.
08 · Storage & file services · 15–20%

Storage & file services cheat sheet

Storage Spaces resiliencyMinimum disksSurvives
Simple1No failures
Two-way mirror21 disk
Three-way mirror52 disks
Single parity31 disk
Dual parity72 disks

Azure Files & File Sync

  • Storage Sync Service → sync group → one cloud endpoint (an Azure file share) plus server endpoints. A server registers with only one Storage Sync Service.
  • Cloud tiering: keeps hot files local and leaves cold files as pointers. Set by volume free space and an optional date policy. Can't be used on the system volume.
  • Permissions: share-level RBAC (SMB Share Reader, Contributor, Elevated Contributor) plus NTFS ACLs. Identity source: on-prem AD DS (join the account with AzFilesHybrid), Entra Kerberos, or Entra Domain Services.
  • Replacing DFS-R: sync each DFS-R member to one sync group, then retire DFS-R. File Sync handles multi-site sync through the cloud.
  • Migrating a file server to a new Windows Server or Azure: Storage Migration Service (inventory, transfer, cut over the identity).
  • Monitor File Sync with Azure Monitor metrics, the sync group health in the portal, and the server's Telemetry event log.

File server features

  • FSRM quotas: hard (blocks writes) or soft (alerts only). Quota templates and auto-apply quotas for new subfolders.
  • File screens: active (block file types, such as .mp3) or passive (monitor only). File screen exceptions allow a subfolder.
  • Classification and file management tasks (for example, expire old files).
  • DFS Namespaces: one path (\\contoso.com\files) over many servers. Domain-based namespaces are highly available. Access-based enumeration hides folders users can't open.
  • DFS Replication: multi-master, block-level (RDC). Read-only replicated folders for branches. Choose a primary member for initial sync.

SMB

  • SMB over QUIC: SMB inside TLS 1.3 over UDP 443, for remote users without a VPN. Needs a certificate on the server. Available in Windows Server 2025 Standard and Datacenter. Client access control limits which clients can connect.
  • Windows Server 2025 requires SMB signing by default. SMB encryption can be required per share or per server. SMB1 is off and should stay off.
  • SMB Direct: SMB over RDMA NICs (iWARP, RoCE, InfiniBand) for low CPU use and high throughput. Works with SET, not LBFO teaming.
  • SMB Multichannel uses multiple NICs automatically.

Disks, volumes & file systems

  • ReFS: integrity streams, block cloning, fast VHDX operations. Use for Hyper-V and S2D. Can't boot, and no EFS or disk quotas.
  • NTFS: boot volume, EFS, quotas, compression.
  • Data Deduplication: NTFS or ReFS data volumes, not the system volume. Usage types: general file server, VDI, backup.
  • iSCSI Target Server: targets with IQNs. Use MPIO on initiators for redundant paths.
  • Storage QoS policies (in a cluster) set minimum and maximum IOPS per VHDX. Dedicated policies apply per disk, aggregated policies share the limit.

Storage Spaces Direct & Storage Replica

  • S2D: pools local disks across 2–16 cluster nodes. Fastest drives become cache. Two-node clusters need a witness (cloud or file share) and can use nested resiliency.
  • Storage Replica: block-level volume replication. Synchronous (no data loss, needs low latency, about 5 ms round trip or less) or asynchronous (longer distance, possible data loss).
  • Storage Replica modes: server-to-server, cluster-to-cluster, stretch cluster. Each side needs a log volume, and source and destination volumes must be the same size.
  • Standard edition limits Storage Replica to one partnership with one volume up to 2 TB. Datacenter is unlimited.
  • Test the configuration first with Test-SRTopology.

BitLocker

  • Protectors: TPM, TPM + PIN, startup key, recovery password, Network Unlock (auto-unlock on the corporate network using WDS).
  • Back up recovery passwords to AD DS with Group Policy (or Entra for Entra-joined devices). Find them in AD Users and Computers on the computer object's BitLocker Recovery tab.
  • Recovery: enter the 48-digit recovery password, or use manage-bde -unlock or repair-bde for damaged volumes.
  • Clusters can encrypt Cluster Shared Volumes. The cluster name object (CNO) is added as a protector.
09 · Security · 10–15%

Security cheat sheet

Server hardening

  • Credential Guard: isolates LSA secrets (NTLM hashes, Kerberos TGTs) with virtualization-based security. Blocks pass-the-hash. On by default on qualifying domain-joined Windows Server 2025 machines. Not supported on domain controllers.
  • App Control for Business (formerly WDAC): allow lists for code that can run. Start in audit mode. AppLocker is the older, per-user option.
  • Exploit protection: system and per-app mitigations (DEP, ASLR, CFG). Export and deploy as XML.
  • OSConfig (Windows Server 2025): apply Microsoft security baselines with PowerShell, with drift control that reapplies settings that change.
  • Windows LAPS: unique, rotating local admin passwords, backed up to AD DS or Entra ID, optionally encrypted. On DCs, it can manage the DSRM password.
  • Defender for Servers: Plan 1 includes Defender for Endpoint. Plan 2 adds JIT VM access, file integrity monitoring, and vulnerability assessment.

Windows Firewall

  • Profiles: Domain, Private, Public. The domain profile applies when the server can authenticate to a DC.
  • Rules filter by program, port, protocol, and scope (remote IPs).
  • Connection security rules use IPsec to require authentication or encryption between hosts (for example, server isolation).
  • Manage centrally with Group Policy or New-NetFirewallRule.

Passwords & accounts

  • The domain password policy comes from a GPO linked at the domain. Only one per domain.
  • Fine-grained password policies (PSOs): different policies for users or global security groups (not OUs). The lowest precedence number wins. Create them in ADAC or with New-ADFineGrainedPasswordPolicy.
  • Entra Password Protection for AD DS: a proxy service plus a DC agent on every DC. Blocks the global banned list and your custom banned words. Start in audit mode.
  • Protected Users group: no NTLM, no DES/RC4 Kerberos, no delegation, no cached credentials, 4-hour TGT. Don't add service or computer accounts.
  • Mark admin accounts "Account is sensitive and cannot be delegated".

Securing AD DS

  • Tiered admin model: Tier 0 (DCs, AD) admins never sign in to lower tiers. Use privileged access workstations.
  • Authentication policies and silos restrict where privileged accounts can sign in.
  • AdminSDHolder: SDProp resets permissions on protected admin groups and their members every 60 minutes. Edit AdminSDHolder, not the accounts, to change them.
  • Delegation of Control Wizard: give help desk staff specific rights on an OU (for example, reset passwords) without adding them to admin groups.
  • Harden DCs: Server Core, no internet browsing, restrict logon rights, keep DCs patched, and limit physical and console access.
  • Kerberos: enforce AES and disable RC4. Audit then restrict NTLM. Kerberos armoring (FAST) protects pre-authentication.
10 · Monitor & troubleshoot · 15–20%

Monitor & troubleshoot cheat sheet

Monitoring tools

  • Performance Monitor: live counters. Data collector sets record counters, traces, and configuration on a schedule, and can trigger alerts.
  • System Insights: local predictive analytics that forecast CPU, network, and storage capacity use.
  • Event subscriptions: a collector gathers events from sources into Forwarded Events. Collector-initiated (collector pulls, small fixed set) or source-initiated (sources push, configured by GPO, scales better). Needs WinRM.
  • Azure: Azure Monitor Agent plus data collection rules for event logs and counters (works on Arc servers too). VM Insights for performance maps. Alert rules with action groups.

Active Directory recovery

  • AD Recycle Bin: needs forest functional level 2008 R2 or higher and can't be turned off. Restore with Get-ADObject -IncludeDeletedObjects | Restore-ADObject or AD Administrative Center. Keeps attributes and group memberships.
  • Without the Recycle Bin: restore from backup in DSRM, then an authoritative restore of the object with ntdsutil so it isn't overwritten by replication.
  • Non-authoritative restore: rebuild a failed DC from backup and let replication bring it up to date.
  • Reset the DSRM password: ntdsutil "set dsrm password".
  • SYSVOL (DFS-R) recovery: non-authoritative (sync from a partner) or authoritative (set msDFSR-Options=1 on the good DC and disable the others, then re-enable).
  • Deleted objects stay recoverable for the deleted object lifetime (default 180 days).

AD and authentication problems

  • Replication: repadmin /replsummary, /showrepl, /syncall. Health: dcdiag.
  • A DC that's been offline longer than the tombstone lifetime (180 days) must not be reconnected. Lingering objects follow. Demote it and rebuild.
  • Kerberos fails with more than 5 minutes of clock skew. Check time with w32tm /query /status. Members sync from DCs, and DCs from the forest root PDC emulator, which syncs from an external NTP source.
  • Duplicate SPNs break Kerberos: setspn -X. Clear tickets with klist purge.
  • "The trust relationship between this workstation and the primary domain failed": repair the secure channel with Test-ComputerSecureChannel -Repair or Reset-ComputerMachinePassword. No rejoin needed.

Server problems

  • Connectivity: Test-NetConnection -Port, tracert, pathping. Name resolution: Resolve-DnsName, nslookup, ipconfig /flushdns, Clear-DnsServerCache.
  • Windows Update: Get-WindowsUpdateLog, then check the Windows Update service, disk space, and the SoftwareDistribution folder.
  • Disk encryption: check the recovery key escrow and TPM state (manage-bde -status).
  • Azure VM won't boot: boot diagnostics screenshot, serial console, or attach the OS disk to a repair VM. Use Run Command to run scripts without network access.
  • Extensions: check the extension status in the portal and the logs under C:\WindowsAzure\Logs (Azure VMs) or azcmagent logs (Arc).
11 · Recognition

Commands to recognize

TaskCommand
Transfer or seize a FSMO roleMove-ADDirectoryServerOperationMasterRole (-Force to seize)
Find FSMO holdersnetdom query fsmo
Create the KDS root key for gMSAsAdd-KdsRootKey
Create / install a gMSANew-ADServiceAccount / Install-ADServiceAccount
Restore a deleted AD objectRestore-ADObject
Authoritative restore, IFM, DSRM passwordntdsutil
Replication statusrepadmin /replsummary
DC healthdcdiag
Repair a broken computer trustTest-ComputerSecureChannel -Repair
Applied GPOsgpresult /r (/h for HTML)
Enable nested virtualizationSet-VMProcessor -ExposeVirtualizationExtensions $true
PowerShell Direct into a VMEnter-PSSession -VMName
Register a JEA endpointRegister-PSSessionConfiguration
Validate a Storage Replica setupTest-SRTopology
Time sync statusw32tm /query /status
Arc agent statusazcmagent show
12 · Recall

Numbers to memorize

ItemValue
Default site link replication interval / minimum180 / 15 min
Kerberos maximum clock skew5 min
Tombstone and deleted object lifetime (default)180 days
Group Policy refresh: members / DCs90 ± 30 min / 5 min
gMSA password change / KDS key usable after30 days / 10 hours
AdminSDHolder (SDProp) interval60 min
Protected Users TGT lifetime4 hours
Hyper-V Replica frequency30 s / 5 min / 15 min
Hyper-V Replica additional recovery pointsup to 24
VHDX / VHD max size64 TB / 2 TB
S2D cluster size2–16 nodes
Storage Replica in Standard edition1 volume, up to 2 TB
DHCP failover hot-standby reserve / MCLT5% / 1 hour
DNS scavenging no-refresh + refresh7 + 7 days
SMB over QUIC portUDP 443
WinRM HTTP / HTTPS5985 / 5986
13 · Traps

Classic traps

Fine-grained password policies apply to users and global groups, not OUs. Linking a password GPO to an OU does nothing for domain accounts.
Seizing a FSMO role is permanent. Transfer if the holder is reachable. Never bring a seized-from DC back online.
Enforced beats Block Inheritance. And the last GPO applied (OU) wins over domain and site.
Security filtering needs Read too. If you remove Authenticated Users, the computer accounts still need Read on the GPO.
The double-hop fix is resource-based Kerberos constrained delegation, not CredSSP, when the question mentions security.
PowerShell Direct works with no network, but only from the Hyper-V host and only with guest credentials.
Nested virtualization needs the VM off, Dynamic Memory off, and MAC spoofing (or NAT) for guest networking.
Checkpoints aren't backups. And production checkpoints don't save memory state.
Stub zones update themselves; conditional forwarders don't.
DHCP servers must be authorized in AD, and you can't run one for VMs inside an Azure VNet.
Deduplication isn't supported on the system volume, and cloud tiering can't run on it either.
Storage Replica synchronous mode needs low latency. Long distances mean asynchronous and possible data loss.
Credential Guard isn't supported on domain controllers.
A broken trust relationship doesn't need a domain rejoin. Repair the secure channel.
The AD Recycle Bin can't be disabled and doesn't recover objects deleted before it was enabled.