I would start with this hotfix, it cured something very similar for me last year
The logon process stops responding in Windows Server 2008 R2 or in Windows 7
Used MDT/WDS to deploy machines over the summer. Randomly, after user enters crednetials, machines will display a black screen with a cursor. Machine will stay like this for anywhere between 1 and 7 minutes and then eventually display the desktop. It doesnt happen every login.
Any ideas? Various things on Google but none which seem to apply. Could it be a graphics driver issue? The machines concerned are Dell Optiplex 755, Dell 760 and 780 machines.
fiza (17th September 2013)
Sounds like GPO processing is in synchronous mode, rather than asynchronous.
The computer is delaying the login till all GPO's are processed.
Group Policy and Logon Impact - Group Policy Team Blog - Site Home - TechNet Blogs
Dropping to a black screen with a cursor would make me think display drivers. Running the actual chip maker's driver instead of the MS one? Is there more than one display hooked up to these systems? I've also seen machines do this when detecting and setting up multiple displays (although it usually takes just a split second).
Was a solution found, have similar issues here.
We get this but it is totally random. If it happens, I just switch the PC off at the wall, reboot it, and it us OK, although it will take a bit longer to boot than normal.
I have a feeling it may be linked to issue we were/are having with our old server that acts as a print server. Its not a DC anymore due to issues as you found, poor logons etc. Have done fresh install of print server before half term so waiting to see if error returns however we still have some print availability issues for some reason.
I have tried the hotfix on a pc and no joy, delay of 600 seconds, iszue with gpclient in event logs, does this need to be run on the server as well? Does the gpclient message mean its a gpo issue and would the error message tell me which gpo is causing the dely? Will be changing the asynchronus processing setting later to see if that helps. Incidentally if I distributed the hotfix its an msu do I do it via a logon script and does it check if its already been applied previously or does that have to be scripted?
Could you take a machine out of action that has had the problem, add it to a new OU and try adding gps independantly. Might need a few different test users with different permisions and different level of GP's assigned to them.
There are currently 1 users browsing this thread. (0 members and 1 guests)