(imported topic written by MattBoyd)
If a BES client is in the process of running an action (or downloading content for an action), will the client be prevented from going into standby when it has power settings applied? We want to make sure that the machine does not go into standby while actions are being run, such as software installs.
Also, is there an easy way to check if a client is in the process of running any actions from the client, without parsing the logs?
(imported comment written by BenKus)
Hey Boyd,
The agent will not specifically tell the computer not to go into standby… but by default Windows has all sorts of heuristics to figure out when not to go into standby (like if the CPU/disk activity is high)…
Where would you want to see if an agent is running actions? On the local computer or in the console?
Ben
(imported comment written by MattBoyd)
Ben,
Ideally, I would like to be able to use relevance that returns whether or not there are actions running on the client. However, we would also like a separate process/application running on the local computer to be able to check to see if there are any running actions (via registry key, file, etc). So if either of these scenarios are feasible, it would be a lot of help.
Thanks
Matt
(imported comment written by jessewk)
You maybe able to use the relevance ‘exists active action’ to see if an action is running from the console. This may not work and if it does you’ll probably only ever see it say true for long running actions.
Externally, I believe you can query the client using the same relevance through the client compliance API to see if it’s running an action. Again, I’m not sure if that inspector will work outside of the currently running action’s context. You may need to contact or professional services department to figure out how to accomplish this itegration.
Jesse