Forcing Computer Refresh Through API

The clients don’t use deep sleep by default unless they are Android. You could configure Deep Sleep if you wanted, but that would probably only make sense for laptops. The right click to send a client alert brings the client out of deep sleep on demand, but it should only work if the client gets the UDP packet from the system or if it polls for commands.

If you have computers that are not reporting for a long time, it is likely that they are not receiving the UDP packets that the system sends to notify them of work to be done. In this case you should enable command polling.

Sending a ForceRefresh does nothing to cause the client to respond right away. It still must either get the UDP packet or do a poll for commands to see that it should refresh itself.

I would recommend all clients poll for commands at least once every 12 hours. Clients that are off network or mobile and unlikely to receive the UDP packets, they should poll for commands at once an hour, give or take. It is not a good idea to enable command polling that is too aggressive. Command polling primarily impacts the relays.