When right clicking on an endpoint in the 9.1+ console, there is now an option for “Send Client Alert Request”. What does this do exactly?
When this is used, it results in a “WakeFromDeepSleep command received” in the client logs.
Is this a subset, superset, or completely different than the “Send Refresh” / “notify client ForceRefresh” / “ForceRefresh command received.” ?
Is there a way to achieve a similar effect of “Send Client Alert Request” through ActionScript or through the REST API or through the command line while on the client itself?
How does this relate to the following client setting? :
There is a sleep mode of the client where the client will sleep for periods of time but it will IGNORE UDP messages from the infrastructure (queue them actually) except for one - which is the one you are seeing.
The setting to enable is:
_BESClient_Resource_PowerSaveDeepSleepEnable
Type: Boolean
Version: 8.0
Platform: All
Default: 0
Requires Client Restart: NO
Description: set to 1 to activate the deep sleep mode.
What this allows is our client to go through all the content and stop doing anything which lets the processor enter very very low power states. A mode similar to this but still reacting to the regular UDP messages is:
_BESClient_Resource_PowerSaveEnable
Type: Boolean
Version: 8.0
Platform: All
Default: 0
Requires Client Restart: NO
Description: set to 1 to activate the simple sleep mode.
In this mode we still keep up the processor checks etc and pay attention to the UDP messages. This is good for laptops/tablets.
This setting can be set on new endpoint installations to run at “normal” Work/Idle settings until it gets through a complete pass of all the content. This is a way of a new client being able to subscribe to sites etc and complete a full first pass quickly.
The deep sleep functionality trumps everything. The client shuts down on a timed event with two triggers, shutdown and the WakeDeepSleep UDP message. When the times expire (there are 6 settings that control those depending on power level and network connectivity) the client wakes up and performs a full cycle before going back to sleep again only if nothing changed.
Good question. The internal one I maintain has it but I am not sure where these are documented. They were heavily used in the Android agent (with different defaults however) even though the Windows agent predated their use.
What document do you use that describes Client Settings?
For completeness then here are the remaining 6 settings mentioned.
_BESClient_Resource_PowerSaveTimeout0
Type: Numeric
Version: 8.0
Platform: Windows
MinNumeric:
MaxNumeric:
Default: 10
Requires Client Restart: NO
Description: Minutes to sleep when the network is present at high power. Min: 0, Max: 2147483647
_BESClient_Resource_PowerSaveTimeout1
Type: Numeric
Version: 8.0
Platform: Windows
MinNumeric:
MaxNumeric:
Default: 20
Requires Client Restart: NO
Description: Minutes to sleep when the network is present at medium power. Min: 0, Max: 2147483647
_BESClient_Resource_PowerSaveTimeout2
Type: Numeric
Version: 8.0
Platform: Windows
MinNumeric:
MaxNumeric:
Default: 60
Requires Client Restart: NO
Description: Minutes to sleep when the network is present at low power. Min: 0, Max: 2147483647
_BESClient_Resource_PowerSaveTimeout3
Type: Numeric
Version: 8.0
Platform: Windows
MinNumeric:
MaxNumeric:
Default: 720
Requires Client Restart: NO
Description: Minutes to sleep when the network is NOT present at high power. Min: 0, Max: 2147483647
_BESClient_Resource_PowerSaveTimeout4
Type: Numeric
Version: 8.0
Platform: Windows
MinNumeric:
MaxNumeric:
Default: 1440
Requires Client Restart: NO
Description: Minutes to sleep when the network is NOT present at medium power. Min: 0, Max: 2147483647
_BESClient_Resource_PowerSaveTimeout5
Type: Numeric
Version: 8.0
Platform: Windows
MinNumeric:
MaxNumeric:
Default: 2880
Requires Client Restart: NO
Description: Minutes to sleep when the network is NOT present at low power. Min: 0, Max: 2147483647
but I am not sure where these are documented. They were heavily used in the Android agent (with different defaults however) even though the Windows agent predated their use.