winrm-troubleshooting
Diagnoses WinRM failures on Windows servers and AutomatedLab VMs: service startup, listeners, HTTP.sys/IIS, authentication, HTTPS, firewall, TrustedHosts, limits, double hop, and fallback channels. USE FOR: WinRM error, HTTP 500, quickconfig failure, StopPending, service won't start, listener missing, connection refused/denied/timeout, Enter-PSSession failure, Invoke-Command failure, WSManFault, 0x80338170, 0x80070005, 0x80090322, firewall, HTTPS, CredSSP, TrustedHosts, Kerberos, double hop, PowerShell Direct, MaxEnvelopeSize, port 5985/5986, Test-WSMan, ping works but WinRM is closed after reboot. DO NOT USE FOR: AutomatedLab Proxmox lifecycle ordering (use automatedlab-proxmox), monitoring a running remote job (use long-running-job-monitor), SSH remoting, Azure Automation DSC, general networking.
- Compatibility
- Requires Windows or Windows Server targets, PowerShell 5.1+ with the WSMan provider, and administrative access to the target.
Pinned to revision 7a186c5dfcf8, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/winrm-troubleshooting/SKILL.md
- skills/winrm-troubleshooting/notes-evals.md
- skills/winrm-troubleshooting/references/advanced-diagnostics.md
- skills/winrm-troubleshooting/references/post-restart-readiness.md
Every link opens the file at its source, pinned to the revision this page describes.