Skip to main content

CPU Temperature Monitoring

Purpose

The goal of this solution is to monitor the CPU temperature of physical Windows machines using the Libre Hardware Monitor.

Associated Content

Script

ContentTypeFunction
EPM - Sensors - Script - CPU Temperature Monitor - CreateScriptCreate and configure the remote monitor on the end machine.
EPM - Sensors - Script - CPU Temperature Monitor - ManageClient ScriptManages and maintains the remote monitors created on the end machines.

Monitor

ContentTypeFunction
EPM - Sensors - Internal Monitor - Execute Script - CPU Temperature Monitor - CreateInternal MonitorExecutes the above script against the concerned physical Windows machines.
EPM - Sensors - Remote Monitor - CPU Temperature Monitoring ProcessRemote MonitorPerforms the monitoring.

Alert Template

ContentTypeFunction
△ CUSTOM - Execute Script - CPU Temperature Monitor - CreateAlert TemplateExecutes the above script against the machines detected by the internal monitor.

Implementation

  1. Place the CPUTempMon.exe file in the LTShare (or Webdav for hosted partners) as outlined in the Script's documentation.

  2. Import the CPU Temperature Monitor - Create script from the ProSync plugin.

    Import the CPU Temperature Monitor - Manage script from the ProSync plugin.

  3. Import the Execute Script - CPU Temperature Monitor - Create internal monitor from the ProSync plugin.

  4. Import the alert template named △ CUSTOM - Execute Script - CPU Temperature Monitor - Create from the ProSync plugin.

  5. Execute the CPU Temperature Monitor - Create script on any online Windows computer. Make sure to set the ‘Set_Environment’ parameter to 1. This will create the EDFs and system properties.
    Image

  6. Reload the system cache and verify the existence of the EDFs and the system property as detailed in the script documentation.
    Image

  7. Adjust the values in the system properties (or the EDFs) as needed.

  8. Run the CPU Temperature Monitor - Create script on a physical Windows machine. Check the configuration and operation of the remote monitor created by the script.

  9. Configure the solution as follows:

FAQ

Q: Is it accurate to state that tickets generated by the remote monitor are automatically closed upon the resolution of the identified issue?
A: Affirmative, tickets are configured to be automatically closed subsequent to the resolution of the associated issue. However, it’s important to note that if there are any modifications to the monitor set’s configuration during the interval between the generation of the ticket and the resolution of the issue, the auto-closure of tickets will not be executed.