Question : Login GPO timeout Event ID 1217

I've just comleted the migration of two domains (1 x NT4 - 1 x Win 2k3) in to a 3rd existing domain (Win 2k3).  During the process, the NT4 server was wiped and upgraded to Win 2k3, so all domain controllers in the new domain are now Win 2k3.  All clients are Win XP SP 2.

A number of PCs are now experiencing extremely slow log in times, only completing the log in process when GPO processing times out.  This occurs in clients from both of the original 2 domains.  No roaming profiles are in use.  Cold reboots hold no consequence.  ALL clients receive DNS and WINS via DHCP.  All clients are in the same OU.  The problem occurs with both restricted and administrative domain accounts.  Affected and non affected clients appear to resolve the domain to the same DC, so it would not appear to be a server side problem.

Group Policies applied are absolutely minimal, but as stated above, do not appear to be relevant as the same GPOs are applied across the board.  The same clients experience the problem every time a user attempts to log in.  Those that do not have the problem, always function correctly.

Any ideas?  We're a bit stumped.  I'll try to post any additional info that maybe need as and when its requested.

Cheers

Answer : Login GPO timeout Event ID 1217

Hi, for info the issue appears to have been related to the image installed on the one client model.  For some reason, the clients were retaining group policy settings from the old domain, specifically to wait for the network to be available before logging on.  It was almost as though the clients were looking specifically for a domain controller on the old domain.  Very strange.  As the available time to resolve the issue was limited, we took the decision to flatten the clients with a rehash of a working client image rather than digging around the Registry / Group Policies and potentially still not resolving the issue.  The machines are used in classrooms where lessons are 50 minutes.  Waiting 20+ minutes to log in was not an option, so the accepted solution, however grotesque, was the safe option.
Random Solutions  
 
programming4us programming4us