> Additional tools > Power Management > Application behavior > Managing applications that conflict with power policies

Managing applications that conflict with power policies

Applications running on managed devices can conflict with the power management policies you create. Some applications must be allowed to continue running even if the policy has a shut-down command for the device. Other applications should not interfere with the policy and need to be terminated as part of the shutdown process.

The power management alert log helps you identify which processes running on managed devices can conflict with power policies. These conflicts are logged with the device name, time, and process name. Review these log entries to determine which applications are causing conflicts.

The Application management button ( ) on the power management toolbar includes three options that let you manage potential conflicts with applications:

  • Identify process-sensitive triggers: The processes that you include in this list will be allowed to run even if the power policy has a shutdown command. The power policy will wait until the processes have terminated and will then continue to enforce the policy.
  • Identify processes to terminate at shutdown: The processes that you include in this list may interfere with the power policy, causing a state of "insomnia" (inability for the device to shut down or standby). If these processes are running, the power policy will terminate them so it can continue.
  • Identify processes to ignore: The processes that you include in this list do not need attention from the power policy and don't need to be included in alert logs.

Instructions for using these options are found in the following topics:

Configure applications that should not be shut down

Configure applications that should be shut down

Configure applications to ignore in alert logs

 


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other