How does the LANDesk Management Suite Power Management Saving report work to generate the savings numbers and how is the defaultusagetable.xml generated?

Version 4

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.x


    This document provides information on how the LANDesk Management Suite Power Management Savings report works to generate the savings numbers as well as how the defaultusagetable.xml is generated.


    LDMS 9.5 and beyond


    The defaultusagetable.xml is based upon computer data gathered by power management tools on the clients.  An example would be something like this after removing the XML tags:

    DayOfWeek name="Monday"

    "Inactivity" at="0001" duration="6091"

    DayOfWeek name="Tuesday"

    DayOfWeek name="Wednesday"

    DayOfWeek name="Thursday"

    DayOfWeek name="Friday"

    "Inactivity" at="0535" duration="1437"


    Due to the machines in be above example being inactive for most of the week, the inactive timer was started on Monday at 001 (24 hours) and carried through for 6091 or all the way through Friday sometime and then became inactive again at 0535. There was no need for any other entries in the file because there was no further activity and the machine stayed inactive for the remainder of the time. There is a warning often that pops up stating there is no data for entire days of the week when attempting to create the defaultusagetable.xml.  It means that the computer started idle at the beginning of the usage period and remained idle for a long period during the sample time. The data is accurate, there is just not a lot there. If a user wants to generate their own data driven xml, they must rename it to defaultusagetable.xml in order for it to be used in report calculation.


    The defaultusagetable.xml is also editable by hand. Inactivity is determined by the screensaver, mouse and keyboard movement and input responses received from the machine via power management tools at the workstation level.