Hi, One of the guys in our team has been looking to further optimise login speeds for our project before the pilot begins. The environment we're in is W2k3 throughout and MPS4. During his investigation he noticed that the logon process was delayed by a couple of seconds while the 'Resultant Set of Policies' was enumerated. By default this policy is on in AD it appears. During logon we got this in the userenv log :- USERENV(11c8.12c4) 10:00:21:437 AllocAdmFileInfo: Adding File name <\\our.domain\sysvol\our.domain\Policies\{46C145B9-B38F-4FD0-A87F-3C1382ED27 E7}\Adm\wuau.adm> to the Adm list. USERENV(11c8.12c4) 10:00:26:171 LogRegistry RsopData: Successfully logged registry Rsop data Granted this is a dev environment hes working on but. That's a considerable wait for the logging to complete. He tracked this down to a default policy setting Computer->Admin Templates->System->Group Policy->Turn off resultant Set of Policy Logging According to the explanation in the policy: 'RSoP logs information on Group Policy settings that have been applied to the client. This information includes details such as which Group Policy objects (GPO) were applied, where they came from, and the client-side extension settings that were included. If you enable this setting, RSoP logging is turned off. If you disable or do not configure this setting, RSoP logging is turned on. By default, RSoP logging is always on.' So he turned it on, which turned the setting off (thanks Microsoft) and got this in the log: USERENV(1158.11bc) 10:09:19:062 LeaveCriticalPolicySection: Critical section 0x430 has been released. USERENV(1158.11bc) 10:09:19:062 ProcessGPOList: Extension Registry status was not updated because there was no changes and no transition or rsop wasn't enabled And the result - much quicker logon times. So, anyone come across this before ? Anyone else tuning this value? tia ---------------------------------- Andrew Wood Sunderland United Kingdom