Windows 7 Domain Logon takes 6 minutes

[sharpharp]

Can anyone help, this is turning out to be a nightmare.

Got an image ready and use sysprep to add the PC to the domain and use the copy profile set to YES to make all users use the default profile...

The profile is around 100MB which isn't so bad judging by the amount of software we have on there.

But when logging in as any domain user, the windows 7 screen displays the Welcome screen for well over 6 minutes....

I've checked the Event Log on the Windows 7 PC and it says the following in the Application Log.... "The winlogon notification subscriber <gpclient> is taking long time to handle the notification event (logon)"

Event ID 6005
Locale ID 2057

Any ideas?????

Thanks in advance
Sharpy

 

[richc46]

Try in safe mode
If that works, use a clean boot
http://support.microsoft.com/kb/929135

 

[chev65]

Can anyone help, this is turning out to be a nightmare.

Got an image ready and use sysprep to add the PC to the domain and use the copy profile set to YES to make all users use the default profile...

The profile is around 100MB which isn't so bad judging by the amount of software we have on there.

But when logging in as any domain user, the windows 7 screen displays the Welcome screen for well over 6 minutes....

I've checked the Event Log on the Windows 7 PC and it says the following in the Application Log.... "The winlogon notification subscriber <gpclient> is taking long time to handle the notification event (logon)"

Event ID 6005
Locale ID 2057

Any ideas?????

Thanks in advance
Sharpy

I'm not sure if this is the same problem but Msoft has a hotfix.
Stuck On Windows 7 Login Welcome Screen? [Quick Fix] | EMDMA

 

[sharpharp]

We use a Jpeg as background, not a solid colour as mentioned in the MS article...

Tried the drivers, no joy. Still get that message in event log and still upto 5 mins to logon as a fresh domain user...

 

[Barman58]

Do you have any persistent network shares mapped and are they all available to the test system during test.

have seen a delay at this point whilst the system repeatedly attempts to connect, this is especially prevalent on test lab systems which are running on a small test network that does not exactly copy the intended network