Windows 7 Domain Issues
OK I have a laptop joined to the domain running Windows 7 RC. It joined fine but takes a long time to show the desktop. It can take 5-10 mins while its logging in I just get a black screen. I'm not sure if this is because the logon scripts we use are causing issues. I'm guessing this is because of our printer logon script that uses vbscript. Anyone have any idea what could cause this? Thanks!
June 2nd, 2009 10:56pm

May be caused by some changes after log on with domain account. If the printer is deployed by script, the driver is downloaded from the server. The driver may be not compatible, and causes this issue. I suggest that you remove the printer deploy command from the script and check the result again. If the issue persists, please let us know the other changes that is done by the script.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2009 11:50am

This can be caused if you have the wrong DNS server set. Make sure that the only DNS servers in the TCP/IP properties are Domain DNS servers. Post the results of ipconfig /all if you are not sure.Kerry Brown MS-MVP - Windows Desktop Experience
June 4th, 2009 4:55pm

Try creating a test OU that blocks inheritence and write a basic logon script, something that applies group policy and adds a drive or something.Then go from there.Once you identify what works and what doesnt, you can modify the domain logon script to apply proper settings to Windows 7 machines and integrate them into your main environment.hope that helps
Free Windows Admin Tool Kit Click here and download it now
June 6th, 2009 12:08am

I had the same problem is solved by removing the user account on the server and re-create it, they win. 7 requests the username and password to save. Thank you
June 8th, 2009 6:49am

I changed the logon scripts. It turned out there were a couple different issues. The print scripts were partly to blame and have since gone to deploy them through a GPO instead and it works much better. The other problem was one of the network shares was using samba and I had to change the local security policy to allow NTLM V2 and also to allow NTLM SSOP non-encrypted connections and then everything was happy. Thanks!
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2009 4:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics