Home > IT Answers > Microsoft Windows > Black Screen after Windows Vista Login to Dom...
BSchlinker
15 pts.
0
Q:
Black Screen after Windows Vista Login to Domain Controller
Domain Controller, Login scripts, Vista, Vista Errors
Currently experiencing problems when basic domain users login to their desktops. I have three desktops running Windows Vista Business experiencing the same problem.

Here is the problem:
- User will login to their account as they normally do -- no problems occur before the login process.
- Windows Vista will display the "Welcome" dialog along with spinning orb thing.
- After a few moments, the entire screen will go black. Pressing CTRL+ALT+DEL will not result in a security dialog. There is no way to start explorer or task manager. The system will never unfreeze (as far as I know). I believe I have been able to move around the mouse on the screen, but I do not remember at this time.

Notes:
- An administrative user logging into the system (with Domain Admin privileges) will not experience these problems. This user does not need to be given local admin rights (although I believe Domain Admin's already have them already).
- Enabling / disabling UAC does not affect this problem.
- The system event log does not show any relevant information to this problem. It appears that no information is ever written to it.
- This problem only began recently -- and occurred within a few days on each of the systems. Around that time, IE8 was installed automatically along with other updates via WSUS and Windows Updates.
- System Restore does not appear to help this problem -- despite how it does attempt to undo the most recent Windows Updates.

Temporary solution:
- I disabled three login scripts which are based on the kix32 platform. I disabled these scripts by simply moving the files to another location from their previous location in NETLOGON.
- Systems will work after I have moved these login scripts.
- If I run these login scripts interactively from the users desktop via a command prompt, I experience no problems.
- Guessing that there was a permissions problem, I checked permissions on these scripts and granted access to 'Everyone'. This did not help solve the problem -- I had to disable them again.
- There have been no other major changes made to these systems. There is no reason why these simple login scripts should simply stop working.

Whats wrong with these scripts?

--- Example of one of the script files ---
 If InGroup("QuickBooks Users")
         Use q: /delete /persistent
         Use q: "\\twinserve\quickbooks"
 EndIf
ASKED: May 29 2009  9:56 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
BSchlinker
15 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
Last Answered: May 29 2009  9:56 AM GMT by BSchlinker   15 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

JennyMack   3205 pts.  |   May 29 2009  1:41PM GMT

Hi BSchlinker,

Welcome to IT Knowledge Exchange, and thanks for the great question — plenty of detail, well-tagged — well done! This should really help your peers answer your question. Feel free to drop us a line if you have any questions or suggestions about the site.

Jenny
Community Manager

 

Carlosdl   29340 pts.  |   May 29 2009  2:20PM GMT

Have you tried moving one logon script at a time to identify which is the one that is causing the problem ?

 

BSchlinker   15 pts.  |   May 29 2009  5:15PM GMT

Carlos,

I did try all three of the login scripts one at a time. No matter which login script I try, I experience these problems.

Since all three are basically the same thing, I wouldn’t expect a major difference depending on which one is active. Also, all three will run correctly when interactively executed within windows.

 

Mshen   23525 pts.  |   Jun 4 2009  6:27AM GMT

Microsoft operating systems allow you to login before they are fully connected to the network which will cause login scripts that map network drives to fail. Try turning this off in a group policy: Computer Configuration -> Administrative Template -> System -> Login -> Enable Always wait for the network at computer startup and logon.

It is also possible that this is a kix issue.

 

Carlosdl   29340 pts.  |   Jun 4 2009  1:40PM GMT

Mshen might be right.

That would explain why when the scripts are run interactively they don’t fail.

 
0