Computers Randomly Hanging at Boot Up and Log in

Hello Experts,

I am hopeful you all can help me pick my brain, I have a very random problem that keeps happening and it may cost me my job if I can't figure out the cause and it's effecting various systems and very random.

Here is the senerio:


- The problem is at any given time, a few systems will take forever to boot up and get stuck on "applying deployed printer policies."
- At the same time, when a student logs in, it is set to install the printer from the lab they are in, and it will get stuck.

- We have a total of 439 systems
- We have had the same group policies that have been fully tested running successfully since September.
- We had the setting "wait for network before boot up" enabled on the default domain, which I have disabled but we had it happen to several today.
- I have taken systems and put them in a blocked ou and removed all policies and added them back one by one and have had inconsistent results.  They both became locked up at different policies with different messages.  No printer policies ever applied.
- No errors in policies in the event log or any services
- The same two systems mentioned above are not working fine with no issues.
- It's no the same systems every time, it happens very random.
- The machines are pingable when this happens but I am unable to browse to them to manage them using any windows tools.
- the only process I have been able to see when this is happening is the process "system" is running high.

We are on a 2003 forest with all windows 7 systems.

Any suggestions on what I can do to hunt this down?   I really have to get this resolved and it's so random and not consistent.

Thank you,

Karen
-
klsphotosAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brett DanneyIT ArchitectCommented:
Tricky one. I have had similar issues. You can try the following:
1. If you are not using IPv6 I recommend running this patch to disable IPv6 on the machines - MicrosoftFixit50409 (Google it, you will get a download link)
2. Next you will want to install Windows6.1-KB2537556-x64 or Windows6.1-KB2537556-x86 (64bit or 32bit depending on the OS)

The patch in two solved my issues, which were very similar to yours.
0
klsphotosAuthor Commented:
Thank you SagiEDoc, Ip is already disabled on the whole domain through the default domain policy.
0
klsphotosAuthor Commented:
I believe this has been resolved.

I believe this is related to UAC.  UAC is disabled on the ghost image that all the systems have, however I believe it was still prompting behind the log in for the students who logged in, you just couldn't see it.  I have temporarily disabled policies I believe may have contributed and will have to test to narrow it down but for now, everyone is logging in.

Thank you for your help.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
klsphotosAuthor Commented:
I believe I have found the additional and main cause for this issue and am hoping to get some advice from someone else who had experience with this.

The problem started when the log ins for our students were randomly being slow.  This was not isolated to a single place, but many of the labs.

Besides UAC, which is now resolved, and some performance issues on 2 of the domain controllers, and also on our print server, I discovered this:

Slow link detection in the Default Domain Policy is set to 0.  

According to this article:
http://blogs.technet.com/b/musings_of_a_technical_tam/archive/2012/02/27/gpos-and-slow-link-detection.aspx

if it is set to 0:
NOTE: If you want to turn off slow link detection, you can set the Connection speed to 0.  This will cause all of the settings in your policy to be processed without the advantage of testing for a slow link.  While it may sound like a good idea, the downside is that you may have clients complaining about slow processing of policies due to network conditions.

As I said, the original complaint was that we had slow logins, which made my boss furious because the students were losing class time.  In this process of tearing apart policy to find the cause, I disabled all policies except their vital policies, including the default domain, temporarily. I also did this on our laptop cart that is used by teachers.  They use a wireless connection.  Guess what happened?  The laptops are now coming up with "no logon servers available" or were stuck on "please wait."  Makes sense, it's not loading our wireless policy because it detects too slow of a connection...the same slow connection that is processing the forced slow logins?  At my desk when I was testing this, I had 3 systems.  A virtual connected to our ESX host, my desktop hardwired and a old laptop that was connected to the wireless.  I lost most of my bars during my testing on the wireless and was able to duplicate the "no logon servers" message.  My deployed printer also loaded after I was logged on, currently it wait's for the logon to finish to load the printer.

My boss is insistent that there is nothing wrong with the network because the systems can be pinged......(?) and that the issue lies on the windows side.  These settings were configured prior to my arrival but am I wrong to come to the conclusion that either we have random slow log ins or students won't get their redirected drives or possibly printers and other needed resources OR  we do something to speed up the network?

Is there anything else I can do?
0
klsphotosAuthor Commented:
Again, this is hard to troubleshoot, especially for those who do not have access to the resources needed to work on it, but I believe I have located the cause as explained in my explanation.

Thank you,

Karen
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.