Troubleshooting

•Power Management Processor Is Not Running

•Pressing Power Button Does Not Wake Computer

Power Management Processor Is Not Running

The power management processor serves many critical functions. This topic lists symptoms that can mean that it has stopped running.

The power management processor runs as a Windows service, and it should be configured to start automatically. If it does not, or if it is running and something stops the processor, any of these symptoms can occur:

•Device check-ins are not processed.

The Device Status column in the Administrator console is not correctly updated. For example, you might see inactive devices marked as active or the reverse. If the Last Connected column appears, it is not updated for active devices.

•Wake jobs are not processed.

In the WakeJob table in the database, you would see your wake job with a LastWakeJobServiceUpdateTimeUtc value showing the time you submitted the job. When the background processor is running, this field is updated roughly every minute.

•Policy changes are not delivered to all affected clients.

•New Wake on WAN proxies are not elected if an existing one shuts down.

•Wake on LAN power state changes that are scheduled in policies do not run as scheduled.

•New devices that connect are not allocated a license.

•Operational Hours report data is missing or truncated after a particular time.

If you see any of these symptoms, open the Windows Services console to check that the service is running: Windows Start menu / Run / services.msc.

In the Services console, look for the Enterprise Power Management Processor. If it has stopped, you can restart it manually.

If you experience any of these issues, and the power management processor is running properly, further troubleshooting depends on the specific issue. For assistance, contact Cisco Technical Support.

Pressing Power Button Does Not Wake Computer

If a computer does not wake when you press the power button, an outdated driver or other hardware conflict might be preventing the power-state change.

•Detecting the Hardware Issue

•Updating the Hardware Does Not Resolve the Issue

Detecting the Hardware Issue

When you press the power button on a computer in standby, the power button light can show the issue that is preventing the computer from waking.

Table 10-1 shows the hardware signals, indications, and the resolutions.

Table 10-1 Hardware Issues and Resolutions 

Signal
Meaning
Resolution

Power light changes from blinking blue or green to blinking red or orange

A piece of hardware is preventing the system from waking, for example, the video card.

Update the hardware or video card, or try a different video driver.

Power light changes to blue or green, and the CPU engages, but the monitor does not.

Conflict with the video card or driver.

Contact the video card manufacturer to get the most recent version.

Multiple monitors do not wake properly or consistently, screens display incorrect resolution on wake, and so on.

Conflict with the video card.

Contact the video card manufacturer to get the most recent version.


Video driver issues are more common in computers that were built in 2006 and earlier, but they could also be present in new systems. Obtaining the latest driver version usually resolves the wake issue.

Tip To ensure that you get the latest version of the video driver, contact the video card manufacturer rather than the computer manufacturer.

Updating the Hardware Does Not Resolve the Issue

If updating to the latest video driver does not resolve the wake issue, apply a policy to the computer that turns the computer off at night instead of changing it to standby and that does not change the computer to standby after idle time.

Tip If you use Wake on WAN, set this computer as a preferred proxy. Proxy computers are always on. For information, see the "Setting a Device As a Preferred Wake on WAN Proxy" section on page 6-8.