upgrade from 2003 STD to server 2003 SBS Std

Discussion in 'Windows Small Business Server' started by Bernard Si-Tech, Dec 10, 2007.

  1. As soon as I start the upgrade, I get "unable to access active directory",
    if I demote the directory service I loose the users and their settings.
    I am trying to upgrade as I only have 1 server (HP proliant server )
    if I remove the directory and users the upgrade process tells me that my Os
    is newer than the CD I am using.
    This is a new CD just purchased
    Bernard Si-Tech, Dec 10, 2007
    1. Advertisements

  2. Bernard

    FWIW, I have never been able to get the upgrade to work this way. Your
    best bet is a Swing migration. If you have 2nd box that you can use to
    stage things, you can move your active directory intact to that box.
    Then setup your Proliant using the Windows on the SBS install disk.
    Pull over the AD from your staging box and then complete the SBS

    For more information, check out

    J. M. De Moor, Dec 10, 2007
    1. Advertisements

  3. Thanks for the info about Swing. I had seen this previously but was not sure
    if it was worth purchasing.
    I was trying to do an upgrade as it was a recommendation from Microsoft
    here, they since deny this
    I try to do an upgrade so I dont loose the programs installed on the server
    as it took me over 1 day to install and setup these.

    Is there any simple way to export the users & settings to a backup medium?
    Bernard Si-Tech, Dec 10, 2007
  4. Thanks for the responce.
    Microsoft recomend the upgrade to SBS from 2003 STD
    Here is the link

    Anny other info would be hlepful on how I can migrate / backup system
    settings to same server

    Bernard Si-Tech, Dec 10, 2007
  5. Is this swingit a Product (software) or documentation.

    Bernard Parrett, Dec 10, 2007
  6. Swing It! is documentation of a process.

    The basics.
    You install a DC that takes a copy of the AD, this is your 'swing' server.
    You then disconnect this from the original AD and install the new box into
    this 'offline copy' using the name of the original server. To do so the AD
    needs to have references to the original server removed. This is done
    primarily to lessen work at the workstations, you recreate your UNC paths
    from the old box on the new, Exchange ends up having the same name as the
    original Exchange, etc... At changeover time you shut down the old server,
    disconnect it from the network, plug in the new and fire it up. As the AD
    (ie. the domain SID) and server name have been preserved the workstations
    sortta don't recognise the server as having been changed.

    The process is a compendium of MS KB articles and 'normal' AD procedures so
    the end product is fully supportable as a 'normal' system.

    Many suggest Jeff's support of the project, which comes as part of the kit,
    alone justifies the cost.

    HOWEVER, I've just quickly skimmed your original and other posts to the
    thread. Swing may not be necessary in your case. I'm guessing the origin
    server has Windows Server SP2, and possibly Windows Server R2 components,
    installed and AFAIK the SBS media you are attempting to use for 'inplace
    upgrade' is SP1, you might try removing SP2 (and R2, and any post-SP1
    hotfixes) then attempt your upgrade. Also consider that though there is an
    'R2' in SBS we only get some parts of it.

    CAUTION: I _would_ Swing the AD, it's a much cleaner way of doing what you
    want. I offer the suggestion only because it is a viable option, or at least
    worth trying. You would also be performing a 'swing to same hardware' which
    in best manner requires formatting the OS partition, and therefore
    reinstallation of your apps that you indicate took substantial time. I
    cannot guess as to what the apps are and probably couldn't comment on the
    effect 'inplace upgrade' is going to have even if you named them.
    SuperGumby [SBS MVP], Dec 10, 2007
  7. Thanks for the great input.
    Clarifies things a lot.
    I had not heard of Swing process unbtil today so it was new to me.
    this seems the better option.
    I was trying to not have to install the allpications on the server but this
    gives an opportunity to install the newer versions of Maximizer and mail
    system we intend to use.
    Thanks again for the input.

    Bernard Si-Tech, Dec 10, 2007
  8. Sorry, you just set off an alarm by saying 'and mail system we intend to
    use.'. Exchange Server is highly integrated into SBS which uses Exchange
    facilities for such things as FAX to email and Performance/Monitoring
    reports. Now, AFAIK any transfers from the SBS components are via SMTP
    rather than MAPI so _theory_ suggests any properly configured mail system
    should be OK but you are really treading where angels fear by replacing

    Due to the nature of SBS I suggest SBS implementers who do not intend to use
    Exchange still install it on SBS with a minimum of the 'Administrator'
    mailbox, running their alternate mail system on another box.

    What mail system do you intend to use, and WHY? Exchange integrates to
    Maximizer, or vice versa.
    SuperGumby [SBS MVP], Dec 10, 2007
  9. Just want to say thanks to everyone for the great input.
    I migrated the server to same system using Swing It
    was so easy, only slight problems as the original server would not allow
    other server to access the sysvol, but after fix that it was smoothe sailing
    finished in 2 days..
    Bernard Si-Tech, Dec 17, 2007
    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.