Group Policy Slows Down Logons

[Ryan Tremblay]

We recently just tested out 4 labs with domain group policy here at our
college. Two of the labs work fine. The other two we are having major
problems with. One lab is located in another building which is connected
via T1 (half voice half data). Anyway at one of the labs here it is taking
5-15 minutes for the machines to log on and the one at the other building it
can take 15-45 minutes to logon.

All labs also use mandatory roaming profiles. I think the problem is we are
using group policy to set some file permissions instead of doing it on the
local machines. I thought when group policy is applied it is cached on the
local computer and it won't reapply all settings unless the GPO has changed.
Is there a way we can speed up these settings? We don't want to lose any
security settings and don't won't to do anything on the local machines. Is
there a way we can cache them so it will let the users logon quicker? Or
should I do away with the mandatory roaming profile and use group policy to
apply other settings? Any help would be appreciated. We use the roaming
profiles so when the user logs off and logs back on any settings (desktop,
screensaver, and anything they put on the desktop and my documents is gone).

 

[Florian Frommherz]

Howdy Ryan!

problems with. One lab is located in another building which is connected
via T1 (half voice half data). Anyway at one of the labs here it is taking
5-15 minutes for the machines to log on and the one at the other building it
can take 15-45 minutes to logon.

Up to 45 minutes? But the configuration of the clients and the servers
are alright? You don't have DNS issues, do you?

All labs also use mandatory roaming profiles. I think the problem is we are
using group policy to set some file permissions instead of doing it on the
local machines. I thought when group policy is applied it is cached on the
local computer and it won't reapply all settings unless the GPO has changed.

This is right for many GPs. I think your point has something got to do
with the mandatory profiles. How large are your mandatory profiles? How
fast is the connection when logging on? Do you have any logon scripts
that could hang and let the system wait for a timeout?

Did you check the eventlogs on the clients?

cheers,

Florian