So, at screen saver startup, a Lock event will be registered in UserLock although the session may be not locked yet (the user can prevent from locking during the 5 seconds grace period). If you do not make that, the change is not effective. This option allows you to get a more efficient result when generating reports using the 'Sub session' option and when setting actions to perform on idle sessions.Īfter that, restart the "UserLock Agent Service" ("ULAgentService") service on target computers (restart it if the OS is Windows XP or Windows Server 2003). When this option is selected and the screen saver is password protected, UserLock will consider the session as locked at screen saver start-up.
0 Comments
Leave a Reply. |