Jure_SGS 0 Posted March 10 Share Posted March 10 Hi. My plan is to automate locking of idle devices via command that can be run as a client task. I've created a dynamic group for idle devices and would run the task via that group. I'd like to know when/how is the device considered Idle so that command doesn't run too soon for an example. Quote Link to comment Share on other sites More sharing options...
Jure_SGS 0 Posted March 16 Author Share Posted March 16 Hi. Maybe I wasn't clear enough? Feel free to ask if there any dilemmas. Thank you. Quote Link to comment Share on other sites More sharing options...
Most Valued Members Nightowl 183 Posted March 16 Most Valued Members Share Posted March 16 (edited) I am not sure about it since I don't work for ESET,but I believe ESET Protect will see the computer as idle , once the screensaver kicks in. Just from my thoughts , I could be totally wrong. Try to set that policy for one computer and leave that computer and see when it kicked in , and check in the same time the screensaver setting for that computer And also if you have Domain Controllers , you can use Group Policy to modify when the PC will be idle/locked. Edited March 16 by Nightowl Quote Link to comment Share on other sites More sharing options...
Jure_SGS 0 Posted March 16 Author Share Posted March 16 (edited) Hi. Thanks for the reply and the policy idea. Will try to create a new one with the dynamic group involve. GP is not an option. Thanks again! Edited March 16 by Jure_SGS Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.