## 1) Tool Purpose
`DebugInfoCollectorTool.ps1` is a Windows diagnostic collection script for Intel AMT/CSME troubleshooting.  
It gathers host, driver, event log, network, power, WLAN, Intel ME, and AMT WS-MAN data, then packages the results into a single ZIP report.

Main flow:
1. Validates Administrator privileges.
2. Collects multiple diagnostics into a `Logs` folder.
3. Writes a transcript and a simple status CSV.
4. Creates a ZIP report (`<HostName>_CSME_Report-<timestamp>.zip`).
5. Deletes temporary files from the `Logs` folder after ZIP creation.

## 2) What the Script Collects (high level)
- OS version + timezone + selected LMS registry values
- SetupAPI log, LMS log, LMS application/system event logs
- Intel MEI/Wi-Fi/Network adapter driver details
- WLAN report + Wi-Fi ETL/WiMan ETL + stored WLAN profiles
- `powercfg -a` and Sleep Study report
- MEInfo output (`-fwsts`, `-verbose`) by detected firmware major version
- FWUpdate backup (`FWUpdLcl64.exe`) and partition version info
- RPC AMT info
- AMT WS-MAN class dump (via helper script)
- MPS connection quality test
- System info and screen resolution details

## 3) How to Use
### Prerequisites
- Run in **elevated PowerShell** (Run as Administrator).
- Execution policy must allow script execution (for example `RemoteSigned`).
- Script folder should contain required helper tools in `Tools` (for example MEInfo, FWU, `rpc.exe`, and `Get_AMT_wsman.ps1`).
- Intel ME/AMT-related data collection requires Intel components/drivers/services to be present on the system.

### Basic run
1. Open PowerShell as Administrator.
2. Go to the script directory.
3. Run:
   - `./DebugInfoCollectorTool.ps1`

The script enables ZIP packaging by default and produces a timestamped report ZIP in the script base directory.

## 4) Output
- Working folder: `Logs` (under script folder).
- Main outputs:
  - Transcript log: `ScriptOutput-<timestamp>_<host>.log`
  - Final package: `<host>_CSME_Report-<timestamp>.zip`

## 5) Supported Operating Systems
**Supported:** Windows only.

Reason: the script depends on Windows-specific APIs and commands, including:
- Windows Registry paths (`HKLM:\...`)
- `Get-WmiObject`, `Get-CimInstance`, `Get-PnpDevice`
- `netsh`, `wevtutil`, `powercfg`, `logman`, `Test-NetConnection`
- Windows file paths such as `C:\Windows\...`

Practical target OS versions:
- Windows 10 / Windows 11 (recommended)
- Windows Server versions with equivalent PowerShell/cmdlet support may work, but are not the primary target.