Re: Redeploy SBS 2003 to a new Server Why wouldn't these steps wor

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Frank -
For what it's worth, I used Swing on my two user SBS and thought it was well worth it. And I no longer recommend anything else in my book. My basic comment about the official microsoft method is don't do it. I describe it, and then say "if that sounds like a bad idea to you, well it does to us too." And then describe the basic steps in a Swing Migration.

--
Charlie.
http://msmvps.com/xperts64


"Frank Ricciardi" <FrankRicciardi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:16A29B7E-71D7-4C0B-96FC-347B79A706D9@xxxxxxxxxxxxxxxx
Thank you both for your replies.

I was reading up on the swing migration on the web site and it seems like
the whole community agrees it's the way to go.

It just seems like enough people face this challenge of wanting to move SBS
to new hardware that I thought microsoft might post reasonable steps to do it
that don't cost $200.

My domain is VERY small (only two users) and I'm wondering if swing might
not be overkill, versus just starting over with a new SBS installation and
migrating my data


I'm also thinking that some kind of automated tool might be a good idea for
a future release.





"Steve" wrote:

Yes I second Lanwench's recommendation to do this via a swing migration:
www.sbsmigration.com

Your steps are a start (with holes in them as she says), but with the swing
kit it is completely documented and support is provided in case of problems
so its well worth the small fee that is charged.

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u0nefAt7GHA.4996@xxxxxxxxxxxxxxxxxxxxxxx
> In news:B11EE74B-2AEE-4153-B58F-FC378710AAE6@xxxxxxxxxxxxx,
> Frank Ricciardi <FrankRicciardi@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
>> previous had a typo on last few lines (corrected steps below)
>>
>> thanks for any help!
>>
>>
>>
>> "Frank Ricciardi" wrote:
>>
>>> Can anyone (especially from Microsoft) shoot holes in this plan?
>
> You should check out www.sbsmigration.com
>>>
>>>
>>> 1) Exmerge all mailboxes to PST's and export all public folders to
>>> PST's
>
> I'm not recommending you do this (as there are holes in your plan to > begin
> with), but in general, for anything like this portion I suggest you > look
> into Recovery Manager for Exchange (www.quest.com) - much better - esp > if
> you have users with mailboxes exceeding about 1.7GB. But as they said > in
> Airplane!, "that's not important now."
>
>> 2) install Windows 2K3 on new hardware (stopping prior to
>>> integrated SBS Installation)
>>> 3) Uninstall SBS from old server (leaving just windows server as PDC)
>
> You can't uininstall SBS and leave the server as a DC. You can't run > SBS
> as anything but a DC. You can't demote it & run it. And you'd blow up a
> boatload of things if you tried.
>
> NB: No such thing as a PDC/BDC in AD - they're all just DCs.
>
>>> 4) Install DNS on New server
>>> 5) Join new server to domain and promote to DC
>
> There's no domain left, in your scenario, unless you had additional DCs > in
> your SBS domain already.
>
>>> 6) Make new DC global catalog server
>>> 7) Transfer the FSMO roles to the SBS 2003 computer
>
> You'd have nothing to transfer *from* in your scenario, even if it > worked
> (which it won't) - you would have to seize the FSMO roles.
>
>>> 8) Transfer the Infrastructure Master role
>>> 9) Transfer the Schema Master role
>>> 10) Move the site licensing server to the SBS 2003 computer
>>> 11) Finish the SBS 2K3 integrated setup on new box
>>> 12) import PST's to new exchange store
>
> Nope. You're on the right track, overall, though - check out the link I
> posted above.
>
>
>




.

Relevant Pages

  • Re: Server Migration SBS 2000 to New Server Box
    ... It's not my goal to talk you or anyone else into purchasing a Swing It!! ... Kit, not at all, not if it doesn't make sense to both of us. ... I also owe a lot of favors to a bunch of SBS ... You will run in to SFN breaks on the new server as soon as you do the ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SP1 finished successfully... or did it?
    ... Regarding the SP updates to an SBS 2003 Server: ... - If you have SP1 slipstreamed media, ... does without a Swing involved. ...
    (microsoft.public.windows.server.sbs)
  • Re: From NT4 to SBS 2003 - 6 users
    ... Server media to use. ... Not specifically in just the SBS ... I think that Swing Migration makes far more sense than any other ... You could decide that an upgrade of a domain would be ...
    (microsoft.public.windows.server.sbs)
  • Re: Install new hardware for SBS 2003
    ... A fresh install and configuration is good experience, but is more downtime overall because of the migration process. ... A swing migration, because of how it works and its offline nature, means almost *no* downtime, regardless of the "learning curve" because you can break the upgrade many times and the original SBS box is still running in production. ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs migration gurus
    ... know any other IT PROs who know SBS here. ... I could really only take the current production server offline late ... You mentioned that 80%+ of the swing ... migration involves installing SBS fresh on the new server? ...
    (microsoft.public.windows.server.sbs)