Gary VirkIT support / infrastructure
← All work

01 IT support · PowerShell · Windows 11

Windows endpoint readiness

A read-only support utility that separates DNS-only faults from broader network-path failures and leaves an escalation-ready evidence bundle.

Validated result

Two controlled Windows faults were reproduced, classified, corrected, retested, and rolled back in fresh disposable sessions.
  • Windows 11 Pro ARM64
  • PowerShell 7
  • Pester
  • UTM
47/47Pester tests
02Native fault scenarios
24Published artifacts

What needed to be known?

A user can report “the network is down” when the adapter, route, DNS resolver, or one service is actually at fault. The project needed to narrow that ticket without changing the endpoint.

A controlled path from fault to retest.

  1. 01

    Collected adapter, address, route, DNS, ICMP, and TCP evidence through a bounded PowerShell module.

  2. 02

    Classified incomplete evidence as unknown instead of treating missing data as proof.

  3. 03

    Injected a DNS-only failure and a wrong-static-network failure outside the read-only collector.

  4. 04

    Repeated the same checks after correction and again after fresh-session rollback.

CheckFailure evidencePost-change
Adapter / IPPassPass
Direct TCPPassPass
DNS nameFailPass
AssessmentDNSOnlyHealthy
Selected evidence summary · full claims remain bounded below

Evidence tied to the claim.

01

DNS-only fault

IP and TCP remained available while name resolution failed; the collector returned Fail / DNSOnly.

02

Wrong static network

Address and route evidence changed together; the collector returned Fail / NetworkPath.

03

Release gate

The public payload was rebuilt byte-for-byte, checksum-bound, sanitized, and independently reviewed.