I like to think I know a lot about Group Policy, but every now and then I come across something cool that I never knew existed. If you haven't heard about it, I'll introduce you to Group Policy Loopback processing.
First, some history. We set our screen saver timeout in a GPO applied to an OU above all our user accounts and, for the most part, everyone is happy with the setting. The trouble is, we have PCs in our conference rooms that are used for demonstrations and it would be nice to have a longer timeout value on those PCs. A request was made to increase the timeout value, and another admin changed the value - a USER setting - on the GPO linked to the conference room PC OU. Unfortunately that didn't change anything and the users complained again. The other admin came to me for an explanation and I said that since the user accounts are not in the Conference Room OU, they won't get that setting (which is mostly true). I implemented a workaround - using Server 2008 Group Policy Preferences - where I edited the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon and added the value ScreenSaverGracePeriod which I set to 15 (which I picked up from the
Windows Registry Guide). This gives the users 15 seconds to move the mouse before the screen saver locks and they have to put in a password. The users accepted this compromise and we moved on.
This weekend I was reading a few chapters out of the
Server 2008 Terminal Services Resource Kit while reviewing for my upcoming 70-649 exam and there is an in-depth explanation on Group Policy Loopback processing mode. It turns out that you can apply User settings even if the user is not in the linked OU by enabling User Group Policy loopback processing mode in Computer\admin templates\system\Group Policy. I just finished reading the
Server 2008 Group Policy Resource Kit and I didn't remember loopback processing being mentioned at all. I checked, and it's only mentioned in the troubleshooting section as an event log entry, but there is never a mention as to what it actually does.
I came in this morning, changed a test GPO to enable loopback processing in merge mode (so that it will only change the screensaver entry and not delete all the other user settings) and adjusted the screensaver timeout. I logged in with a regular account to a test PC and the screensaver timeout reflected the computer OU GPO setting instead of the user's normal setting, and there was much rejoicing.
Why haven't I heard about this setting before? The GP Management Editor says it requires at least Windows 2000, so it has been around since the dawn of GPOs. Why isn't it mentioned in the Group Policy Resource Kit? I can understand why it is in the Terminal Services Resource Kit becasue this setting can be really handy in a TS environment. Is anyone else using different loopback processing modes?