PowerMAN Deployment Tips and Scenarios
As you move from using PowerMAN to monitor PC usage to control power management the following hints may help with project planning:
- Think about your users and their usage pattern. Are your user-computer relationships persistent/exclusive? Will the same user use the PC next time? If the same user will be the next person to use the PC then using hibernate / sleep whilst the user is logged on may be fine.
- If the users change frequently then hibernate / sleep may result in the computer being locked for the next user. In this case, a forced logout after an idle period may be a reasonable approach. When the user has been logged out, you can then implement your chosen power management strategy using a "No User" policy.
- PowerMAN offers several different policy management policies. Most organisations implement a standard "Default User" policy. If appropriate, you may also wish to implement a distinct "No User" policy for when nobody is logged on. This is a good opportunity to use full power-off (shutdown) for maximum energy saving.
- Idle (timeout) strategies generally save more energy because they allow each computer to respond independently to its environment. This works well in some environments but may be unacceptable in others with a more rigid operating schedule (for instance school classrooms).
- Alternatively you may like to use a scheduled strategy as your primary management mechanism to enable power saving at specific times. Depending upon your environment, this may be a cruder approach but have the advantage of being consistent on every PC and therefore more suitable for your users.
- Some organisations use a mixture of the idle and scheduled approaches. For instance, you could use an idle approach for a 'light' daytime sleep and then a night-time scheduled shutdown to clean-up and maximize savings overnight and at weekends.
Whatever approach you use, please remember that PowerMAN will work most consistently if you:
- Baseline the environment before implementing actual power management– This will allow the power saving to be quantifiably measured.
- Always define a "Default User" policy - even if it is configured to do nothing. This applies at all times unless another more specific policy applies.
- Always define a "Global policy" for hardware buttons etc - even if the configuration is trivial this will ensure consistency. This step is particularly useful where pre-existing power management configuration may sometimes cause a conflict.
- Remember to enable hibernate if you plan to use this power saving mode.
- Enable "Policy Enforcement" to ensure consistent application on PCs suffering from PC Insomnia.
This last feature is explained in our FAQs here:
What is computer insomnia?
What is the policy enforcement feature? How does it work?