SBS2003 with major issues - best practise for reloading sought ple

Discussion in 'Windows Small Business Server' started by Grant Ovenden, Jan 10, 2008.

  1. Hehe, this is what everyone wants when they come back from holiday;

    One of our clients SBS2003 Std servers THINKS it has SP2 installed, but it
    doesn't, in fact it doesn't even seem to have SP1 installed.

    So, I'm thinking the best course of action is a reload and restore of the
    Exchange etc.

    I've only done SBS2000 to SBS2003's but I guess it's pretty much the same?

    Or does anyone have an 'EASY' way of re-loading said SBS2003 and restoring

    Thanks heaps!
    Grant Ovenden, Jan 10, 2008
    1. Advertisements

  2. Sorry, further to this...

    Every single Windows Server 2003 Hotfix and Windows SBS 2003 SP2 is showing
    under Add/Remove Programs as all being 29.27Mb in size...

    Also the server (under ABOUT WINDOWS) shows;
    Microsoft (R) Windows
    Version 5.2 (Build 3790.srv03_gdr.050225-1827)

    Who knows what's causing every single hotfix to show as the same file size?
    Really odd eh!

    They have AV and I've run scans and it's fine, I've even run X-Soft over it
    and it's reporting fine.

    Grant Ovenden, Jan 10, 2008
    1. Advertisements

  3. Grant Ovenden

    Pedro CR Guest

    If it's SBS 2003 R1 (not R2) I would start by installing
    - SBS 2003 Service Pack 1 (please note it's SBS Service pack NOT Windows
    Server Service Pack 1)
    - Next Update the drivers for all the network cards
    - Next Install WINDOWS Server 2003 Sp2 (this time it's Windows Server
    Service Pack)
    - Finally install ALL post-sp2 fixes. If you fail to do so you may have
    problems with clients being unable to connect to the server.

    As a final step run SBS Best Practices Analyser. If SBS BPA reports all is
    fine and the event viewer does not show severe errors I think you can be
    confident the server is ok.
    The issues you are seing do not seem very serious. It's normal that
    sometimes Add/remove programs gets confused with the installation size of

    As a last comment let me say that redoing the domain may be a lot more of a
    headache than you are anticipating. First of all if you reinstall the whole
    domain, user accounts need to be recreated and each user will get a new SID.
    This means that yyou will have to re-join each and every workstation to the
    domain and migrate all the user docs/settings. Also reocnfigure all
    Finally moving back the data to exchange is the simplest task. BEFORE you
    re-install the server use a utility called EXMERGE and export ALL user
    mailboxes. Once you have reinstalle dthe server, run EXMERGE again to import
    the data back into exchange.

    Both EXMERGE and Exchange Best praticies analyser are free downloads from

    Again I would stronglly advise you not to re-install SBS 2003. Before doing
    it try to install all appropriate SP's and I am confident you will get the
    server running OK.
    Pedro CR, Jan 10, 2008
  4. Thanks Pedro, I'll start to try to re-install as you've suggested...
    Grant Ovenden, Jan 10, 2008
  5. It's pretty screwed up, have tried almost everything, everytime I run the SP1
    (or just about anything patch-related) I get "system cannot find file" and it
    bombs out.

    Reload time.

    Has anyone ever seen a system with all the Hotfix's etc. locked in at
    29.27Mb file size?
    Grant Ovenden, Jan 10, 2008
  6. Grant Ovenden

    Quilnux Guest

    I have. It's not a problem. Don't lose any sleep over it. I can't say it's
    "normal" but it causes no problems. Sometimes Add/Remove programs creates the
    same identifiers for applications and patches being installed. when this
    occurs it makes everything that shares the identifier the same size even when
    it's not.

    I just checked my environment and I have 18 out of 27 hotfixs showing up at
    8.29MB. they aren't. Just a glitch in the add/remove reporting system.

    For your companyweb. Have you tried rerunning CEICW? If, not try it. Does it
    fail? If it fails can you post the log file? (C:\Program Files\Microsoft
    Windows Small Business Server\Support\icwlog.txt). If it succeeds try
    accessing companyweb. If it does not fail and you still cannot access
    companyweb check the host header record for Default Site in IIS. (In server
    management > Expand Advanced Management > Expand Internet Information
    Services > Expand Web Sites > Right-click Default Web Site and choose
    Properties > In Properties window, under the Web Site tab, click the advanced
    button next to IP Address > In the top box [not the one with SSL] is there an
    entry that includes companyweb under "Host Header Value"?) If not, you can
    click add > type TCP port 80 and type companyweb in host header value)
    restart IIS and see if that works.
    Quilnux, Jan 10, 2008
  7. Hi, okay the major problem is it that no new patches/hotfixes will install.

    They all just fail.

    And the fact the system shows it's basic a bland SBS2003 Std with no SP1 and
    no SP2 is a concern to us.

    Turns out it's more of a nightmare anyway, so I'm going to take it offline
    and just reload/restore and go from there.

    I AM STILL keen to hear from anyone with a good idea on how to effectively
    reload a SBS box and cleanly restore AD and Exchange back into it...


    Thanks for all the posts though people, always much appreciated!
    Grant Ovenden, Jan 10, 2008
  8. Grant Ovenden

    Quilnux Guest

    AD will be a problem I think. You won't be able to reload username and
    password data from AD. At best you would get back custom AD data you may use
    for your applications. If I'm wrong I sure someone will say so.

    Exchange shouldn't be too hard. I would just run a windows backup to include
    exchange and once your reload is finished just use that backup to restore.
    However, I've never had to do this before so I'm not sure how acurate this is.
    Quilnux, Jan 10, 2008
  9. Grant Ovenden

    kj [SBS MVP] Guest

    Well you could add a second DC and go through the Install SBS into existing
    domain route. It's a fair amount of work, but if you have a bunch of users
    and don't want to mess with workstations and profiles it might be your best
    non third party solution.

    If you keep things the same (Domain & server name) you can forklift the
    exchange DB or you could export to PSTs and exmerge the data back in.

    'reload' and 'restore' are a bit exclusive.
    kj [SBS MVP], Jan 10, 2008
  10. Let me potentially save you a lot of headache

    I ran into a similar issue last year and it took months to figure out. In
    my scenario I tried to install 2003 SP2 on the SBS server. It got part of
    the way through and quit. Then it listed SP2 in the Add/Remove programs, but
    listed SP1 elsewhere. Any subsequent updates would fail.

    I finally found an MS KB that stated that SBS 2003 had a limit to the number
    of updates that could be installed. SP2 fixes this, but of course it
    couldn't be installed because the limit had been reached. There was a
    workaround on the KB which worked and I was able to install it and SBS
    Service Pack 1.

    I would strongly recommend that you resort to reloading only after you have
    exhausted all other avenues.
    Jonathan Barrie, Jan 11, 2008
  11. Grant Ovenden

    Pedro CR Guest

    here is the link to the fix proposed by Jonathan:

    After installing windows 2003 sp2 you may also want to check this out:

    again, I would strongly advise you not go the route of a re-install. If you
    are getting that file not found error, check the installation log. I'm sure
    there would be a command line switch or some kind of log being produced by
    the update packages. Check it out a post the errors here.

    Maybe it's just a matter of permissions or TEMP folders.

    Try disabling the AV while installing the updates (unplug from the Internet
    prior to disabling the AV).
    Also try to empty the TEMP folder and make sure there is enough space on the
    hard drive.

    One more recomendation would be to run chdsk against all the harddrives on
    the server before attempting a re install.
    Pedro CR, Jan 11, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.