Powershell Script # A few days ago, an application team reported intermittent connectivity issues and poor application performance. Their initial conclusion was that the Windows Server OS was responsible for the outages. Rather than relying on assumptions, I decided to investigate with data. To make troubleshooting faster and more consistent—not just for this incident but for future ones as well—I developed a comprehensive PowerShell-based Windows Server & Application Health Check Toolkit (Powershell Script) and save the output in txt file for analysis. The toolkit automatically performs checks such as: * CPU, Memory, Disk & Page File utilization * Installed Windows updates and reboot history * Critical Windows and application services * Network connectivity and port communication * Application, System, DNS, Netlogon & Domain Controller event logs * Application crashes and service failures * Top recurring errors * Network adapter health and secure channel verification After reviewing the generated report and correlating it with Windows Event Logs, it became clear that the operating system was healthy. There were no resource bottlenecks, service failures, or OS-related events that could explain the reported behavior. The collected evidence helped demonstrate that the issue was application-specific, allowing the application team to redirect their investigation and resolve the actual root cause more efficiently. This experience reinforced an important lesson: Evidence-driven troubleshooting is far more effective than assumption-driven troubleshooting. Automation not only saves time but also provides consistent, repeatable, and objective health assessments that improve collaboration between infrastructure and application teams. PowerShell-based Windows Server & Application Health Check Toolkit (Powershell Script) download from below link.

https://dvirus.in//assets/uploads/posts/Appshealth-OShealthCheck.zip