2022-05-31

"Interactive logon: Machine inactivity limit" policy gets triggered by disabled screensaver's timeout

This is just a quick post about how Microsoft managed to keep me busy for a couple hours on what should have been a simple 5-minute job.

After months and years I have finally managed to get the higher-ups to agree on implementing the "Interactive logon: Machine inactivity limit" local security policy after I proved to them that we have a number of users who do not lock their machines even over night or even the weekend.

Previously all we did was enable the power saving option for the monitor but let the user disable that if they had any kind of issue with it or "simply do not like it".

Anyway, I finally got the green light and enabled the policy with a 1200 seconds timeout on inactivity. And that is were most of my workday suddenly got a lot busier than I had it expected to be.