Running Troubleshooting Packs Remotely
You can run a troubleshooting pack across the network on a remote computer, which can allow you to diagnose common problems quickly and possibly solve them without walking the user through the troubleshooting process. The following Windows PowerShell commands, when run on a Windows 7 computer (either locally or remotely using Invoke-Command or the *-PSession cmdlets), will run the built-in Windows Aero troubleshooting pack, automatically attempt to resolve any problems, and store the results to the C:\DiagResult folder.
Import-Module TroubleshootingPack $aero = Get-TroubleshootingPack $env:SystemRoot\Diagnostics\System\Aero Invoke-TroubleshootingPack -Pack $aero -Result C:\DiagResult -unattend
You could also use this technique in a script to run a troubleshooting pack on multiple computers across the network; in combination with a custom troubleshooting pack, you could quickly determine which computers suffered from a specific problem or misconfiguration. Because troubleshooting packs can make configuration changes to solve problems, you could use this approach to detect and resolve a common problem without contacting users or manually connecting to computers.
In this tutorial:
- Troubleshooting Hardware, Driver, and Disk Issues
- Windows 7 Improvements for Hardware and Driver Troubleshooting
- Windows Troubleshooting Platform
- Built-in Troubleshooting Packs
- Windows Troubleshooting Platform Components
- Creating Custom Troubleshooting Packs
- Running Troubleshooting Packs Remotely
- Windows 7 Reliability Monitor
- Windows 7 Resource Monitor
- Windows Memory Diagnostics
- Disk Failure Diagnostics
- Self-Healing NTFS
- Improved Driver Reliability
- Improved Error Reporting
- The Process of Troubleshooting Hardware Issues
- How to Troubleshoot Problems That Prevent Windows from Starting
- How to Troubleshoot Problems Installing New Hardware
- How to Troubleshoot Problems with Existing Hardware
- How to Troubleshoot Unpredictable Symptoms
- How to Diagnose Hardware Problems
- How to Use Device Manager to Identify Failed Devices
- How to Check the Physical Setup of Your Computer
- How to Check the Configuration of Your Hardware
- How to Verify That System Firmware and Peripheral Firmware Are Up to Date
- How to Test Your Hardware by Running Diagnostic Tools
- How to Simplify Your Hardware Configuration
- How to Diagnose Disk-Related Problems
- How to Use Built-In Diagnostics
- How to Use Reliability Monitor
- How to Use Event Viewer
- How to Use Data Collector Sets
- How to Use Windows Memory Diagnostics
- Memory Failures
- How Windows Automatically Detects Memory Problems
- How to Schedule Windows Memory Diagnostics
- How to Start Windows Memory Diagnostics When Windows Is Installed
- How to Start Windows Memory Diagnostics from the Windows DVD
- How to Configure Windows Memory Diagnostics
- How to Troubleshoot Disk Problems
- How to Prepare for Disk Failures
- How to Use ChkDsk
- ChkDsk Examples
- ChkDsk Syntax
- How to Use the Graphical ChkDsk Interface
- How to Determine Whether ChkDsk Is Scheduled to Run
- ChkDsk Process on NTFS Volumes
- How to Use the Disk Cleanup Wizard
- How to Disable Nonvolatile Caching
- How to Troubleshoot Driver Problems
- How to Find Updated Drivers
- How to Roll Back Drivers in Windows 7
- How to Use Driver Verifier
- How to Use the File Signature Verification
- How to Use Device Manager to View and Change Resource Usage
- How to Use Windows 7 System Restore
- How to Troubleshoot USB Problems
- How to Solve USB Driver and Hardware Problems
- Understanding USB Limitations
- How to Identify USB Problems Using Performance Monitor
- How to Examine USB Hubs
- How to Troubleshoot Bluetooth Problems
- Troubleshooting Tools
- DiskView
- Handle
- Process Monitor