Are the notebooks connecting remotely or is it just that they are notebooks? I have seen weird driver issues in the past cause slowness in policy processing but those are hard to track down. How long is user processing taking, according to gptime? Darren -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of prankmonkey Sent: Tuesday, April 01, 2008 5:40 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Policy processing time and slow login/boot Hi all, I'm trying to diagnose whether group policy is causing an issue with slow boot and login. I've enabled userenv debugging nad nothing in the log strikes me as out of the ordinary. Using the gptime tool seems to indicate a computer policy processing time straight after boot (on a core2duo machine 2gb memory) of about 9 seconds which to me is totally reasonable. Notebooks seem to be the biggest culprit and besides a specific policy (registry policy which I know can be slow to apply) to enable them to change timezones, the policies that apply to the desktop are the same that apply to notebooks. Notebooks will always be slower due to FDE and the slower HDDs + SAV is known to slow down machines but I'm just wondering if the list can give me some pointers on tracking down areas of slowness. Is there certain policies settings that should be avoided specifically for notebooks? *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************