Determining Initial Power State Settings from User and System Activity

Overview

This article describes how to view a user and system activity report, which you use to determine how to optimize power use through power management policies.

Complete this task after you run devices using the Baseline Data Collection policy for a minimum of two weeks of normal operation. View hourly activity over a few days to see trends in user activity that you can build policies around.

Process

  1. In the Administrator console, click Analytics on the Verdiem menu icon.PNG.
  2. Select the Activity: Computer Power States report.
  3. For Range, select Last Full Month.
  4. For Granularity, select Daily.
    Note: Typically the baseline data collection period involves all Windows and Mac clients in the system. But if you are using only a subset, use the Groups or Policies filters to run the report only on the relevant computers.
  5. Specify the filter parameters for Locations or Groups to refine the set of devices you want to view in the report results.
  6. Click Run.
    The graph should present a trend of higher user activity during working hours, tapering off toward the end of the workday.
  7. If the graph illustrates inconsistent use, find a different date range within the baseline period that shows consistent and predictable use before you view only one day.
  8. If the graph illustrates consistent use over the weekdays, drill down to just one day (such as a Tuesday or Wednesday), by clicking that day's data in the graph.
  9. Note the times when user activity picks up and tapers off for the day.
  10. Use this data to create your initial power management policies.

Capture.PNG

The graph here illustrates most of the user activity occurring between 6:00 AM and 6:00 PM, so it might make sense to configure power schemes to match this activity level. In a weekday policy based on this data, you might include the following (with corresponding areas in the image indicated in the image below):

  1. A background scheme that transitions computers to standby after a short time of inactivity. For example, after 10 minutes of idle time.
  2. A scheduled power-state change that wakes computers at 6:00 AM.
  3. A daytime scheme that lengthens the amount of idle time before computers transition to standby.
  4. A scheduled power-state change at 7:00 PM that transitions computers to sleep. This step is optional, because if no scheme is scheduled, the background scheme will take effect, and the computers will transition to sleep when idle for the amount of time you specified.

Capture1.PNG

After you create your initial policies, you assign them to devices. You can then refine them to include assignment rules and other settings.

Comments

0 comments

Article is closed for comments.