Well, you can either get my GP logging ADM (www.gpoguy.com/gpolog.htm) or check out this: http://support.microsoft.com/default.aspx?scid=kb;en-us;221833 Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Snell Sent: Tuesday, March 11, 2008 2:09 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Login Time Issues How do I set that option? From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: 11 March 2008 16:55 To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Login Time Issues Try enabling verbose userenv logging. That will show you where time is spent during the GP processing cycle. It may not actually be GP at all, but some other process contending with GP. Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Snell Sent: Tuesday, March 11, 2008 9:48 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Login Time Issues That doesn't show what GPO is taking 10 minutes to load though. From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Tom Strader Sent: 11 March 2008 16:30 To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: Login Time Issues RSOP!! _____ From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Snell Sent: Tuesday, March 11, 2008 12:25 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Login Time Issues I have a couple of users that have to wait 10-15 minutes when they login while GPOs are being deployed. If I move their laptops to a Test OU the problem disappears. If I block inheritance on the existing OU the problem disappears. I have therefore made the assumption that the problem is being caused by one of the GPOs that is being inherited from an OU above. When logging on their screen stays on Applying Computer Settings for the majority of the time it takes to login. I have assigned all the GPOs that they usually run to a test OU and have been disabling them one at a time to try to find the offending GPO. Is there a quicker way of finding out which GPO is causing the problem? Paul