Skip to content

Add 51 Windows RunCommand diagnostic scripts + triage map#126

Open
ScottAzure wants to merge 3 commits into
Azure:masterfrom
ScottAzure:feature/windows-triage-map
Open

Add 51 Windows RunCommand diagnostic scripts + triage map#126
ScottAzure wants to merge 3 commits into
Azure:masterfrom
ScottAzure:feature/windows-triage-map

Conversation

@ScottAzure
Copy link
Copy Markdown
Collaborator

Summary

Adds a complete Windows VM diagnostic toolkit via Azure Run Command:

  • 51 Tier-2 diagnostic scripts covering RDP, networking, boot, services, identity/domain, security, storage, performance, monitoring, Azure agent/extensions, updates, and reliability
  • Customer-facing triage map (TRIAGE-MAP.md) that routes symptoms to ordered script sequences — includes per-extension troubleshooting chains for CustomScript, ADE, MMA/AMA, Patch, DSC, BGInfo, VMAccess, and Dependency Agent

What's in each script folder

  • .ps1\ script (PowerShell 5.1 only, no Az module, read-only, <4KB output)
  • \README.md\ with Interpretation Guide (FAIL/WARN → cause → fix → Learn link)
  • \mock_config_sample.json\ for offline testing (-MockConfig\ + -MockProfile)

Quality

  • All scripts pass quality gate (50/50 Tier-2 with probes)
  • Consistent output format: OK/FAIL/WARN rows + Decision block
  • 48 folder references in triage map validated — zero broken links
  • Customer-friendly language throughout (no internal jargon)

How to use

Customers: open TRIAGE-MAP.md → find your symptom → run scripts in order via Azure portal Run Command.
Engineers: same flow, or use -MockConfig\ for offline testing.

… routing index

- 15 symptom categories: RDP, boot, services, agent, 9 per-extension, network, perf, BSOD, disk, domain, security, update, backup, monitoring
- Shared extension baseline + per-extension chains (CSE, ADE, MMA/AMA, Patch, DSC, BGInfo, VMAccess, DependencyAgent, catch-all)
- 48 script folder references, all validated
- Customer-friendly language (no internal jargon)
- Fallback section for unclear symptoms
- How to run (portal + CLI) and how to read output
Complete diagnostic toolkit for Windows Azure VMs:
- 51 scripts across RDP, networking, boot, services, identity, security, storage, performance, monitoring, extensions, updates, and reliability
- Each script includes: .ps1 (PowerShell 5.1), README.md with Interpretation Guide, mock_config_sample.json
- All scripts pass quality gate (50/50 on Tier-2 scripts with probes)
- Consistent output format: OK/FAIL/WARN with Decision block
- Mock testing support: -MockConfig + -MockProfile for offline validation
- Customer-facing TRIAGE-MAP.md (committed separately) routes symptoms to script sequences
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant