SBS2008 console session stuck on "Please wait for the Local Session Manager".

We have an otherwise apparently fully functional SBS2008 machine which on start-up follows the usual sequence ("Applying computer settings..." and so forth") but then before getting to Ctrl-Alt-Del (so I don't think it's a user profile issue) it just stops on "Please wait for the Local Session Manager...".  In the background the server continues to start up normally, and can be connected to using Remote Desktop.  All services appear to run normally, it's just not possible to log on locally from the console because the Session Manager message sticks there  indefinitely.

 Thanks in advance for any ideas!
LVL 2
David HaycoxConsultant EngineerAsked:
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.

Daniel HelgenbergerCommented:
See this post on EE.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_27843972.html

The user disabled the NIC and windows started again normally.
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
David HaycoxConsultant EngineerAuthor Commented:
Thanks for that - I disabled the NIC then rebooted into normal mode.  Straight to CTRL-ALT-DEL.  Enabled the NIC and rebooted, still ok!  Logged on and checked everything out (all looking normal), then rebooted once more.  Agh!  The problem's back again.

The weird thing is that unlike in the post you linked to, everything is actually working fine; it's just the console login that's blocked by this stuck message.

It looks like it's NIC-related though, so I shall uninstall the NIC (and any other old or hidden ones) and clean out the registry of NIC-based settings and try again.

There are also some updates ready to install so I'll get those done as well and see what happens.
0
Daniel HelgenbergerCommented:
Glad this helped.

I suspect the problem in the the other user reported did not relate to his original problem of the crash but was random.

Anyway, reinstalling the network drivers may be a good precaution. Other then that I advise against any other action, esp. cleaning up registry since the system is working again. Only take action if this happens again.
0
David HaycoxConsultant EngineerAuthor Commented:
Sorry, I think you misunderstood - disabling the NIC worked for one reboot only, the next time it was back to the old problem.  I have cleaned up old NIC entries and installed a couple of hotfixes that looked like they might be relevant, and am rebooting again now.  If everything else really is okay then I might just leave it alone as we can easily administer the server via RDP.
0
David HaycoxConsultant EngineerAuthor Commented:
This problem appears to be tied to SBS2008 - we have another customer whose server started to exhibit the same problem after no changes other than just Windows Updates.  You can still log on fine by RDP, just not from the console.
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
SBS

From novice to tech pro — start learning today.