What are the files associated with LANDesk Power Management?

Version 1

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6

    Question:  What are the files on the client and core that are associated with LANDesk Power Management and what function do they perform?


    Answer:  The answer is written in the bulleted list below:



    • ClientSideEnableWOL.vbs:  Enables the WOL functionality of the client system if it can be enabled.
    • GetInputInfo.exe:  Obtains the input information from the system.
    • ldiscn32.exe:  Collects the current power scheme, deployed power policy information, and time zone data with the inventory scan.
    • LocalWakeUp.exe:  Wake the system up from sleep mode when enabled.
    • poweroff.exe:  Shutdown or reboot the system
    • PWMCfg.exe:  Setting the power of the system.
    • PWMCfg64.exe:  Setting some values of power in a 64 bit system.
    • PWMClientUsageAnalyzer.exe:  Collects and uploads the usage of the client to the core server.
    • PWMProcScipt.ini:  Process list for process-sensitive triggers
    • PWMReservedList.ini:  The ignored process list when sending the insomnia alert.
    • PWMScript.ini:  The power policy that is deployed to the client.
    • PWMWakeUpScript.ini:  The local wake up schedule file.
    • ProcTriggerSvc.exe:  Monitors the CPU, network, and input information to keep the system alive, or terminate processes and send insomnia alerts.
    • tracksvc.exe:  Records the usage and power state of workstation.


    • PowerManagement.asmx:  Web Service that loads under core.anonymous and allows for reporting of all client usage data.

    Database Tables:

    • Computer:  List of all LANDesk Managed Nodes.
    • ConsoleUser:  Users who are allowed to login and perform operations within the LANDesk consoles.
    • CompSystem:  One to One relationship with the computer table.  System information for each computer stored here.
    • PWM_POLICY_DEF:  Policy information is stored in this table.
    • PWM_SCHEME_DEF:  Scheme information is stored in this table.
    • PWM_POLICY_SCHEME_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_SCHEME_DEF
    • PWM_CUSTOM_WATTAGE_DEF:  User defined definition of wattage usage contained with a computer.
    • PWM_BASE_SCHEME_DEF:  Unique entry for each computer.  First information for power state of computer including monitor, disk, system standby, and hibernate.  Stored via inventory scan.  This information is used as base line for each system when generating the savings report.
    • PWM_PROCESS_DEF:  Lists all processes that will be used by a process sensative trigger.
    • PWM_POLICY_PROCESS_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_PROCESS_DEF.
    • PWM_END_PROCESS:  Lists all process that will be ended when there is insomnia.
    • PWM_POLICY_END_PRO_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_END_PROCESS.
    • PWM_CLIENT_INFO:  Client information of Power Management. Inventory Information seen in the tree of the console.
    • PWM_WEEKLY_USAGE:  Keeps the user usage data (active or idle) from each computer, each day.
    • PWM_WEEKLY_HISTORY:  Keeps the time of every power state from each computer, each day.
    • PWM_GROUP_INFO:  Keeps the cost of every group.
    • PWM_IGNORE_PROCESS:  Lists all processes that will be ignored by the insomnia alert viewer.
    • PWM_DETECTABLE_PROCESS:  Lists all processes from received insomnia alerts.
    • PWM_USER_RECORD:  Keeps the last policy and current user operating
    • PWM_RECORD_GROUP_REL:  Relationship between user records and group records.


    If Power Management is failing to report data accurately or is not showing a process list, the first step to take is verify the correct executables are installed and operational on the client.  Checking the appropriate tables within the database can ensure that the data is being received by the core server.  By default, the local scheduler on each client is setup to run the process for sending up Power Management data once a day when the Power Management client is installed and usage data is collected.  The Power Management web service runs anonymously so there is no need for authentication when the clients report data up.  If user authentication is denied in the web service logs, then there is a security issue or a web site configuration issue that must be addressed to fix the problem.