Quick question about battery reporting. I’m trying to get ahead of hardware replacements before batteries start swelling or dying on my users mid-shift.
The standard MDM telemetry usually just shows me the current charge percentage (like 85%), which doesn’t really tell me if the battery is actually dying long-term. Is there a way to use Hexnode to pull the real “State of Health” (SoH)—like the exact cycle count and maximum retainable capacity—for both our Macs and Windows machines?
15 Views
Hi @skylar-a,
This is a fantastic proactive approach. You are absolutely correct that standard charge percentages are too volatile for hardware lifecycle planning. To truly forecast a hardware refresh, you need to look at State of Health (SoH) metrics like Design Capacity vs. Full Charge Capacity, Cycle Counts, and Thermal History.
Because deep chemical health metrics are often sandboxed by the OS, the best way to extract this in Hexnode is by utilizing the Execute Custom Script action. This allows you to query the system at a forensic level.
Here are the scripts you can deploy right now:
For macOS (Bash/Zsh): You can audit Macs using the native IOKit and system_profiler commands.
|
1 2 3 4 |
#!/bin/zsh # Extracts Cycle Count and Maximum Capacity percentage echo "--- macOS Battery Health Audit ---" system_profiler SPPowerDataType | grep -E "Cycle Count|Condition|Maximum Capacity" |
For Windows (PowerShell): Windows devices can be queried using powercfg to generate diagnostics, or WMI/CIM for immediate telemetry.
|
1 2 3 4 5 6 7 8 9 10 |
# Generates a local battery report and extracts key health stats $ReportPath = "C:\Windows\Temp\battery_report.html" powercfg /batteryreport /output $ReportPath # Optional: Extract immediate live capacity state via CIM instance $Battery = Get-CimInstance -ClassName Win32_Battery Write-Output "--- Windows Battery Health Audit ---" Write-Output "Estimated Charge Remaining: $($Battery.EstimatedChargeRemaining)%" Write-Output "Status: $($Battery.Status)" Write-Output "Full Diagnostic Report Generated at: $ReportPath" |
How to view the data: Once you push these scripts to your targeted devices, the results are piped directly into the Hexnode portal. Just navigate to the Action History tab for the device and click Show Output to view the parsed telemetry.
Let us know if you need help scheduling these scripts!
Thanks for this @kylian-parker!
Don't have an account? Sign up
