Hi

We have deployed the wake proxy agent to all (~1400) machines, I was under the impression that only a handful per subnet (we have around 24 subnets) would be kept online as Guardians, but it appears all machines are staying awake, when previously they would have slept due to inactivity.

Is this expected? If so, is there an easy way to deploy the wake proxy agent to just a selection of machines? What is the best practice when deploying the proxy agent? I have read through the documentation and it isn't made clear.

The computer activity report shows most machines staying awake through the night.

Hello,

Is ICMP protocol allowed in firewall rules? Computer send ping command to the others in order to determine if they are awake. So if no response received, they became Guardians I think. Check this, also notice the prerequisites:

Planning How to Wake Up Clients

Configure Wake on LAN

Have you read this?

Have you determined exactly which process is keeping them awake?

Hi - no, logging a ticket with MS now

We allow pings through the firewall, so it should be working. This issue only started happening after we rolled out the SCCM client, along with the WOL proxy agent enabled. Before then, machines would sleep if a user had left the machine at CTRL-ALT-DEL. Now, they do not transition to sleep and if they are shutdown, they are powered on almost immediately.

I am guessing at either a broadcast sent across the VLANs is being captured by the WOL guardians, which powers machines on immediately, or a design flaw in the agent which will mean we install it on a subset of our machines, rather than all of them.

I have run the insomnia reports which seem to verify the sleep agent as being the cause.