![]() I am having this issue within my domain (2012r2 + win10pro 20h2). Hope this isn’t too long winded, I hope this helps anyone This will set the local policy back to “Not Configures” This is to delete the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System If the police is set locally, only way I found to disable As these were redundant, I did not set the " Inactivity limit or User policy - Screen Saver timeout. Out at the lowest number between the two policies: Computer policy – Machine If the Machine inactivity limit is set, the screen will lock > Personalization, set for it to function. Policies > Inactive Logon: Machine inactivity limit. Windows settings > Security settings > Local Policies > Security ![]() Troubleshooting note: When testing (playing) with the policies in: Computer Config > Example:ĥ minute Policy has the (5 minutes AD Universal Security Group) and (Domain computer) added to security Universal Security Group and Domain Computers the corresponding policy. Added users to those groups who need that particular timeout. Universal Security Groups in AD, for 5, 30 and 60 Policies, otherwise the policy will not get applied. Screen saver is not set by the user, or the screen saver if the user hadįor the GP Manager to apply Admins Templates Policies to any machines the userĪnd the AD groups/User must be in the Security Filtering for the Group A value of 60 = 1 minute.Īfter X seconds the screen will lock and either just show the logon screen if a Screen Saver Timeout – This policy is the timer for the User to re-enter their password to unlock the screen after the Screen Saver Timeout is reached. Password protected screen saver – This policy requires the It is only a prerequisite for the following policies. It does not force or change a screen saver if a userĪlready has one set. ![]() User Configuration > Admin Template > Control panelĮnable Screen saver – This policy enables the following Default being 5 minutes and instructorsĬan have a longer time if necessary for presentations. Here is what I’ve done to resolve this on our domain.īackground: We wanted to set up 3 policies to have the screen If you can add any more detail, such as if the other per-user screen lock settings are the ones found under HKCU\Software\Policies\Microsoft\Windows\Control Panel\Desktop or HKCU\Control Panel\Desktop, it would be appreciated.Īfter working on this exact same issues for 3 days straight, It appears you are saying this could be a bug peculiar to windor 1709+ where the machine inactivity limit by itself doesn't work properly unless other per-user screen lock settings are in place which should not be necessary. In one case at least, the behavior changed when we removed the old legacy policy leaving it with no user screenlock (as seen under "personalization->screen lock" in Windows) only the new PGO for machine inactivity limit. So I'm testing out a GPO with the "Interactive Logon: Machine inactivity limit" on 2 users that are not locking reliably. But it fails randomly for some PCs (unknown, probably 1%). I have a GPO for the whole company that uses the "legacy" screen saver setting per user (start scrnsve.scr after 900s inactive) which is set to 15 min which seems to work for most people. I'm having what sounds like the same issue as you, spicehead-jn80, on some of my Windsystems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |