fiza Posted September 17, 2013 Posted September 17, 2013 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.
AJWhite1970 Posted September 17, 2013 Posted September 17, 2013 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 Andrew 1
fiza Posted September 17, 2013 Author Posted September 17, 2013 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 Andrew Thanks Andrew but the description of the symptoms is different. We get past the welcoem screen and there is no blue swirl. With us the black screen eventually allows login and doesnt require a reboot.
peterp Posted September 17, 2013 Posted September 17, 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
fiza Posted September 18, 2013 Author Posted September 18, 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 Checked and it doesnt look like GPO processing is in synchronous mode. As I said it is intermittent.
Duke5A Posted September 18, 2013 Posted September 18, 2013 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).
fiza Posted September 18, 2013 Author Posted September 18, 2013 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). That was my next step - to update the display driver. Currently using the one win 7 came with. machines are student machines so no dual displays involved.
TechSupp Posted November 4, 2013 Posted November 4, 2013 Was a solution found, have similar issues here.
fiza Posted November 5, 2013 Author Posted November 5, 2013 Was a solution found, have similar issues here. I think I traced mine to an old DC. I was meant to replace a DC with a new one. Introduced the new one but then other events took over and I forgot to decommission the old one. This DC was really on its last legs and it seems to be slowing down logins for any clients it authorised. Once I decommissioned the server the issue has gone away (at least I havent had any reports of it occurring).
unixman_again Posted November 5, 2013 Posted November 5, 2013 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.
fiza Posted November 5, 2013 Author Posted November 5, 2013 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. We were doing the same. Either wait for 5-7 minutes and it eventually logs in or reboot. Since taking out the DC no more complaints but this could be due to the fact that users have just accepted that this is what happens and we dont get any reports of it.
TechSupp Posted November 5, 2013 Posted November 5, 2013 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.
TechSupp Posted November 11, 2013 Posted November 11, 2013 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?
fiza Posted January 20, 2014 Author Posted January 20, 2014 We were doing the same. Either wait for 5-7 minutes and it eventually logs in or reboot. Since taking out the DC no more complaints but this could be due to the fact that users have just accepted that this is what happens and we dont get any reports of it. Looks like our issue is still there. Anyone know a way around this?
Watty08 Posted January 20, 2014 Posted January 20, 2014 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.
fiza Posted January 20, 2014 Author Posted January 20, 2014 (edited) I may have worked out why we were getting it. Seems we have a login script which maps drives and was trying to map a drive from a server that was taking an age to respond. The server is due for decommissioning and the drive isn't used anymore but it was still there in the script. I took out the reference to the mapped drive and so far the few tests I have done seem to indicate that the black screen is gone. I have asked the IT Teachers to monitor student logins over the next few days to be sure. I think the black screen was waiting for the drive to map but as it as the server wasn't responding it took ages. Edited January 20, 2014 by fiza
TechSupp Posted January 21, 2014 Posted January 21, 2014 Yes, I had a similar solution, it turned out to be the printers loading but only affected the netbooks, PC's were fine so took the decision to just not have printers on netbooks which all agree is fine so long as the kids can save work to their folders which they can.
Darylrese Posted January 26, 2014 Posted January 26, 2014 I was just about to say mapped drives causes this. I once mapped all staff users to a NAS and it caused a hang, black screen with white cursor for about 5 - 10mins. As soon as I took it off, it was lightening quick again. Check your mapped drives are correct and the location of the mapped drive is adequately spec'd
lukeacourt2 Posted March 14, 2019 Posted March 14, 2019 The machine could be not activated as windows does changes it to black when logging on. by activating you will make it geniune then once you selected the theme it will stay the same.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now