Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1843
  • Last Modified:

SBS 2011 - Stuck on Welcome

We had to move a clients server into the new building, this server is a newer Dell T310 with SBS 2011, serving a very small office (6 Computers).  

We tried to log into the server to shut it down but it wasn't responding and froze on the welcome screen after we typed in the credentials.  The staff was able to work on files at this point.  We force shut down the server and moved to new building.  On boot up it is gets to the login screen, and I can type the credentials but then gets stuck on the Welcome page with the spinning ball.  I can get into Safe Mode, I do not see any errors that pop up in event viewer.  During when it is stuck in the Welcome screen the hard drive lights are blinking away.  If I try to log in and it stays on the Welcome screen it seems like it then hangs 5-10 minutes after.  

Any ideas?  I do not want to do a domain rebuild.  I haven;t been to this site in a while, the last updates were 2/29 and one was the Rollup 6 for Exchange and Rollup 1 for SBS.  

I can't uninstall them in Safe Mode so not sure.
0
Fluid_Imagery
Asked:
Fluid_Imagery
  • 5
  • 3
  • 3
1 Solution
 
rtayIT DirectorCommented:
Try booting to last known good configuration.
0
 
rtayIT DirectorCommented:
You may also want to try a clean boot.  then disable any antivirus/firewall on the system and check for any ms updates, drivers that may have installed automatically.  

Here are clean boot instructions.  

http://support.microsoft.com/kb/929135
0
 
Cliff GaliherCommented:
My first guess is that you have a misfiring group policy and some of those timeouts are quite long (a few are 60 minutes.)

I'd attempt your login and then be *VERY* patient. Unless you allow the login to succeed (after whatever is hanging finally fails) then no events will be written and therefore even viewing the event log remotely will provide no information. In these types of problems, you really have to let the process complete. I'd at least see if the server *eventually* comes up given an hour or two before I did anything drastic.

-Cliff
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
rtayIT DirectorCommented:
You may want to check for hardware issue, such as a disk problem just to make sure the hardware is ok.  at least run a chkdsk
0
 
Fluid_ImageryAuthor Commented:
After disabling some startup items, and rebooting it went through login and was on a GPO Printer Policy.  I didn't want to check so I restarted back into safe mode and DNS was pointing to itself (192.168.10.10) but I changed to 127.0.0.1

Restarting again and waiting.
0
 
Cliff GaliherCommented:
Printer policies are ones that will take 60 minutes to time out if a driver install issue arises. The system will not finish logging in until the driver installer fails, and that is a strange UAC issue that causes the system to hang (temporarily.) Forcing a shutdown/reboot runs a high risk of both exchange and AD corruption so, as I mentioned, I'd wait it out. Once you get in, you can use GPMC to temporarily disable the GPO causing the issue and then add security or WMI filters to prevent it causing problems again in the future.

-Cliff
0
 
Fluid_ImageryAuthor Commented:
What is odd is when I enable all the existing startup items (msconfig) when I reboot all I see is a spinning circle on the Welcome Page.

When I disable the startup items, it atleast gets up to the GPO Printer.

Do I restart, disable the items and then wait it out, or just leave it on the welcome page?
0
 
Cliff GaliherCommented:
I'd leave it on the welcome page. There are built-in timeouts for MOST login processes (although some are quite long) so you really should eventually see movement. Not gracefully shutting down a server is bad (so is a desktop, but a desktop is usually less critical) and a server that requires consistency in its databases (the AD database and Exchange databases) are even worse. I know waiting is frustrating, but the alternatives are even moreso...especially if, as you said, a domain rebuild is not an option. Booting up a server, getting the "no login servers are available" and seeing AD errors in your event logs is one of the worst experiences an SBS admin can have.
0
 
Fluid_ImageryAuthor Commented:
What is the GPO Printer one for?  Workstations or server?
0
 
Fluid_ImageryAuthor Commented:
Ended up having to wipe server.
0
 
Fluid_ImageryAuthor Commented:
fixed it ourself
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 5
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now