microsoft/CSS-Exchange

[Work Item] Improve power plan detection in HealthChecker

Open

#1,909 建立於 2023年12月14日

在 GitHub 查看
 (2 留言) (0 反應) (1 負責人)PowerShell (985 star) (234 fork)batch import
Health CheckerWork Itemgood first issue

描述

Describe the work Today, HealthChecker is able to properly detect if one of the default high performance power plans is set on the OS:

Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance)
Power Scheme GUID: db310065-829b-4671-9647-2261c00e86ef  (High performance ConfigMgr)

However, if customers create a custom power plan, Windows generates a new GUID, which breaks our logic that we use in Get-PowerPlanSetting.ps1. This may result in false positives, because if the custom power plan is configured as we expect it to be, we are not able to properly detect the power settings (since we just check for the GUID and not for the settings of the power plan).

The same situation would happen in case that the default high performance power plan was adjusted and is no longer a "real" high performance power plan (because some of the new settings throttle system performance). We would show this configuration as good, since the GUID doesn't change in that case.

貢獻者指南

技術棧
shell
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PowerShell scriptingWindows power management
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
The issue is in Get PowerPlanSetting.ps1, which currently checks for specific GUIDs. To improve detection, you'll need to modify the script to query the actual power plan settings (e.g., using powercfg /query or Get CimInstance) instead of relying solely on the GUID. Look for the function that performs the GUID check and consider how to compare settings against expected high performance values. The comments may contain additional context about custom plans.