Questions

Windows Server 2003 - very long boot time (+3 hours)

+
0 Votes
Locked

Windows Server 2003 - very long boot time (+3 hours)

mr.sweetchuck
Hi,
I appear to be having some problems with my Windows SBS 2003 server.

When I boot up the server it, takes several hours to get to the log-in screen. Furthermore, when I log in, the server continues to display the 'Applying Computer Settings' messages box ofr +1 hour, (during this time the server is responsive to cursor movements and pings from other machines.)

One final note, the MS Exchange System Attendant services stalls when i manually attempt to start it.

Does anyone have any suggestions re how to resolve this?

Thanks,
chuck.
  • +
    0 Votes
    Dumphrey

    BootVis, or something similar, it may be able to show you the offending processes. There are to many possibilities off the top of my head to narrow it down any further.

    Does Exchange run properly? Any errors in application or system logs? Failed Raid drive?

    +
    0 Votes
    Jacky Howe

    Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS


    http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382

    < Typo >

    +
    0 Votes
    CG IT

    to a time when it didn't take 3 hours to load...if it's always taken 3 hours...you have a major problem... if sys attendant won't start it probably would be best is you reinstalled the Exchange component from the DVD and then reinstall SP 2&3.

    if SBS takes 5 minutes to get to the logon screen, and you aren't running SQL it's to long....

    +
    0 Votes

    DNS

    cj_mcnix

    I had a similar problem when MS had me reboot both of my servers during a service call. Problem was that each server was pointing to the other for primary DNS and itself for secondary. Took a few hours before they came back up and I was able to change the primary DNS to themselves. Part of my problem was also a top level domain name issue that messed with DNS as well. (domainname instead of domainname.com or domainname.local). I needed a special MS VB script to fix that one....

    +
    0 Votes
    khoffenkamp

    Hey Chuck,
    Had the same prob on Win2k3 SBS. Exchange Services was the cause. The server had Exchange installed but it was not functioning as an Exchange server. Since it was not configured properly it would not start. I assume you have the same situation, since Exchange will not work without the Attendant service. If this is the case, just disable all your Exchange services. I had to do some through the registry since the services were partially started. Mine went from 2.5 hours down to 5-7 minutes.

    +
    0 Votes
    J.C.Alexandres

    Try upgrading the BIOS and firmware for RAID controllers, along with updated disk drivers

    +
    0 Votes
    k_magz

    We had the same issue. Finally found
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

    had grown HUGE do to some automated drive mapping we were doing. If that's your case remove that hive and re-add an emtpy value(back up yrou registry first if you can -- ours was so large we could not back it up.)

    Good Luck

    - Ken

    +
    0 Votes
    davidt

    Problem was, I installed a service pack that was intended for 2003 standard, not SBS (and it ALLOWED it, thank you very much MS). I was on the phone with India for hours.....

    +
    0 Votes
    mr.sweetchuck

    As one of the guys above pointed out, this was an Exchange problem.

    History:
    Server was build with an aim of adding to the domain before replacing the current DC.

    Unfortunately, I made a mistake in the build and built is as a DC for its own domain. To resolve this, I used dcpromo to downgrade the new server to a stand alone server. I was then able to add the server to the domain and promote it again, (using dcpromo.) During this time Exchange was uninstalled.

    Resolution: The resolution was to reinstall Exchange.

    Thanks everyone for your help and suggestions,

    Much appreciated,
    chuck

    +
    0 Votes
    cbhildre

    I have had the same issue with my SBS box since day 1. It was installed in a brand new network so Mr. Sweetchuck's solution won't work for me. If anyone else has any ideas that would be great.

    Thanks

  • +
    0 Votes
    Dumphrey

    BootVis, or something similar, it may be able to show you the offending processes. There are to many possibilities off the top of my head to narrow it down any further.

    Does Exchange run properly? Any errors in application or system logs? Failed Raid drive?

    +
    0 Votes
    Jacky Howe

    Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS


    http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382

    < Typo >

    +
    0 Votes
    CG IT

    to a time when it didn't take 3 hours to load...if it's always taken 3 hours...you have a major problem... if sys attendant won't start it probably would be best is you reinstalled the Exchange component from the DVD and then reinstall SP 2&3.

    if SBS takes 5 minutes to get to the logon screen, and you aren't running SQL it's to long....

    +
    0 Votes

    DNS

    cj_mcnix

    I had a similar problem when MS had me reboot both of my servers during a service call. Problem was that each server was pointing to the other for primary DNS and itself for secondary. Took a few hours before they came back up and I was able to change the primary DNS to themselves. Part of my problem was also a top level domain name issue that messed with DNS as well. (domainname instead of domainname.com or domainname.local). I needed a special MS VB script to fix that one....

    +
    0 Votes
    khoffenkamp

    Hey Chuck,
    Had the same prob on Win2k3 SBS. Exchange Services was the cause. The server had Exchange installed but it was not functioning as an Exchange server. Since it was not configured properly it would not start. I assume you have the same situation, since Exchange will not work without the Attendant service. If this is the case, just disable all your Exchange services. I had to do some through the registry since the services were partially started. Mine went from 2.5 hours down to 5-7 minutes.

    +
    0 Votes
    J.C.Alexandres

    Try upgrading the BIOS and firmware for RAID controllers, along with updated disk drivers

    +
    0 Votes
    k_magz

    We had the same issue. Finally found
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

    had grown HUGE do to some automated drive mapping we were doing. If that's your case remove that hive and re-add an emtpy value(back up yrou registry first if you can -- ours was so large we could not back it up.)

    Good Luck

    - Ken

    +
    0 Votes
    davidt

    Problem was, I installed a service pack that was intended for 2003 standard, not SBS (and it ALLOWED it, thank you very much MS). I was on the phone with India for hours.....

    +
    0 Votes
    mr.sweetchuck

    As one of the guys above pointed out, this was an Exchange problem.

    History:
    Server was build with an aim of adding to the domain before replacing the current DC.

    Unfortunately, I made a mistake in the build and built is as a DC for its own domain. To resolve this, I used dcpromo to downgrade the new server to a stand alone server. I was then able to add the server to the domain and promote it again, (using dcpromo.) During this time Exchange was uninstalled.

    Resolution: The resolution was to reinstall Exchange.

    Thanks everyone for your help and suggestions,

    Much appreciated,
    chuck

    +
    0 Votes
    cbhildre

    I have had the same issue with my SBS box since day 1. It was installed in a brand new network so Mr. Sweetchuck's solution won't work for me. If anyone else has any ideas that would be great.

    Thanks