Infrastructure is a dependency chain
Active Directory depends on DNS. Applications depend on services, networking, and name resolution. Hybrid identity depends on healthy on-premises infrastructure and clear cloud boundaries. This hub organizes those relationships so technicians can investigate the system behind the symptom.
Begin with a focused published guide: inspect local network configuration, test one DNS question, investigate DHCP capacity or server storage, or follow the domain-health path when multiple Windows dependencies overlap.
Published investigation guide · Windows Server
Confirm the affected volume, measure capacity and growth, and correlate Windows, application, database, virtualization, backup, and role evidence before planning a change.
Open the storage guidePublished investigation guide · DHCP
Compare scope statistics with lease states, reservations, exclusions, failover, and client impact before planning a capacity change.
Open the DHCP capacity guidePublished investigation guide · Active Directory
Follow an evidence-first sequence from client scope through locator records, domain-controller checks, replication, time, services, and logs.
Open the domain-health guidePublished tutorial · DNS
Download, verify, review, and run the DNS-only tool, then interpret its normalized results without overstating what one query proves.
Open the Test-KTDNS tutorialPublished tutorial · Local network configuration
Verify and run Get-KTNetworkConfig, interpret its eight-property objects, preserve the evidence limits, and choose the next targeted check.
Open the Get-KTNetworkConfig tutorialVersioned download
Download the release with its source, README, tests, license, and checksum manifest from one versioned location.
Open DownloadsLearning method
Use the MSP University sequence to understand dependencies, collect evidence, isolate the cause, and verify the result.
Review the learning pathThe published DNS and local network-configuration tools are linked directly. Other lanes establish where future reviewed learning will belong without inventing tutorials or cases.
Published investigation guide
Investigate client configuration, domain discovery, member secure channels, controller advertising, services, replication, time, and logs.
Investigate domain healthPublished tool available
Name resolution, record types, resolver selection, response evidence, and the DNS dependencies that affect domains, services, and applications.
Use the read-only DNS toolPublished investigation guide
Scopes, leases, options, reservations, relay paths, and the client configuration that connects addressing to DNS and routing.
Investigate scope capacityPublished storage investigation guide
Begin with evidence-first low-disk-space investigation. Broader roles, features, update, scheduled-work, and administration guidance remains in development.
Investigate server storagePublished investigation guide
Review replication, SYSVOL and NETLOGON evidence, time, domain-controller reachability, and signals that distinguish local from domain-wide failures.
Use the evidence-first guideContent in development
Service state, dependencies, startup behavior, recovery, accounts, and the difference between a stopped service and an underlying failure.
Content in development
Time-bounded evidence, provider context, event correlation, useful filters, and ways to avoid treating isolated warnings as root cause.
Content in development
Addressing, routes, ports, firewall boundaries, name resolution, path testing, and the evidence that separates reachability from application health.
Content in development
On-premises identity health, synchronization boundaries, DNS, time, authentication, and the dependencies that surface in Microsoft cloud services.
Two public tools
Read-only discovery and stable output now include Test-KTDNS and Get-KTNetworkConfig. Other Windows, server, and Active Directory tools remain private or in development.
Explore the PowerShell LibraryFive published guides now cover local network configuration, focused DNS testing, DHCP scope capacity, broader Active Directory health, and evidence-first Windows Server storage investigation. Additional Windows and hybrid procedures remain in development.
Published tutorial · DNS
Verify the release, query a selected resolver and record type, read the stable output, and use the result as one piece of troubleshooting evidence.
Use the Test-KTDNS procedurePublished tutorial · Windows networking
Collect active adapter, address, gateway, DNS-server, and profile evidence without treating configuration as proof of connectivity.
Use the Get-KTNetworkConfig procedurePublished investigation guide · DHCP
Compare percentage and absolute free capacity with lease states, reservations, exclusions, failover, and current client impact.
Open the DHCP capacity investigationPublished investigation guide · Active Directory
Determine which dependency is associated with the symptom before planning an environment-specific repair.
Open the domain-health investigationPublished investigation guide · Windows Server
Measure the affected volume and identify credible growth evidence without deleting data, clearing logs, changing retention, or resizing storage.
Open the low-disk-space investigationCurrent tutorial catalog
The tutorial catalog now includes this Windows/DNS procedure alongside the published Microsoft 365 and Exchange Online guidance.
View all current tutorialsContent in development
Future procedures will cover other Windows Server, service, event-log, networking, and hybrid scenarios only after technical review.
Two public releases provide narrow, read-only DNS and local network-configuration evidence with source, tests, documentation, and checksums.
PowerShell · v1.0.0
Review supported record types, requirements, stable output, terminating errors, checksum verification, and the Authenticode limitation.
Review release detailsPowerShell · v1.0.0
Review the zero-parameter local discovery boundary, eight-property output contract, privacy guidance, checksums, and Authenticode limitation.
Review release detailsPackage integrity
Get the ZIP and checksum manifest from the Downloads page before reviewing or running the script.
Open the download packageFuture tools
Additional Active Directory, server, service, event-log, networking, and hybrid tools will appear only after review, testing, documentation, and packaging.
No Windows or hybrid case is published yet. This lane is reserved for sanitized investigations that preserve useful infrastructure reasoning.
Windows & Hybrid cases
Future cases may cover directory health, DNS, services, event evidence, connectivity, replication, and hybrid dependencies after privacy and technical review.
Current case catalog
The current case library contains two anonymized Microsoft 365 investigations and does not claim a Windows case.
Browse current casesCase method
Published cases separate confirmed findings, hypotheses, remediation, and verification instead of presenting a symptom as a root cause.
Review the case flow