Re: Migrate to new Hardware and/or SBS2003

There's more than one way to do a migration, and a lot of things add into
the mix --- like how many users you have on youre server, any specific
applications, etc.

If it were me, given your scenario, I would SKIP any thoughts of upgrading
to SBS2003 first on your current server, before migrating. Since your
current server is working fine, and you have new equipment, I might suggest
taking a look at Jeff Middleton's SwingMigration approach at
www.sbsmigration.com .

Here's why:
1. Your current server remains up and running thorughout the process, until
the very end. That means minimal impact to your users
2. You install SBS2003 fresh on your new server. Shoot, install it 2 or 3
times to get a feel for it, test out your recovery process, etc.
3. Then once you are ready, you do a final swing, move over your Exchange
database, and all user data files, etc.
4. The advantage is that there's virtually no impact to your users, or to
their workstations. Literally you turn the workstations on, and sign in like
you did before. Users won't know anything has happened!

Now, the "gotcha" for all of this is two simple things:
1. You need another computer to act as an interim server. I simply used a
spare laptop with 768mb of memory, for this process.
2. You've got to plow through all of Jeff's manuals, documentations and
notes. Not that the process is hard, buyt Jeff goes into a lot of detail so
you are not only aware of what's going on at each step of th emigration, but
also -- if you run into any problems, he's already addressed them!

My first swing migration was an SBS server with 20 users, and except for one
printer and one shared folder I forgot to restore, it was painless to the
end users.



--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"Jan Pasterkamp" <vullis@xxxxxxxxxxxxxx> wrote in message
news:42b094c2$0$27926$dbd49001@xxxxxxxxxxxxxxxxxx
> Our SBS2000 Server is getting a little slow. I also read the line about
> Migrating to new Hardware. Do you axpect any problems on the new Hardware
> and should we Upgrade to SBS2003 to avoid strange problems.
> If SBS2003 is better should we Upgrade first and then migrate to new
> Hardware or Migrate to new Hardware and then Upgrade.
> NB: The HP NetServer is running perfectly and the new Hardware is Dell
> with
> Raid-5 (5xharddisk).
>
>


.

Relevant Pages

  • Re: Upgrading from NT4 to SBS2003 Premium
    ... > install SBS 2003 on a new hardware; refer to the following white paper to ... > do a migration of the user and computer accounts. ... Migrating from Small Business Server 4.5 or Windows NT ... > an In-Place upgrade. ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading from NT4 to SBS2003 Premium
    ... perform an in-place upgrade to w2k3 Standard Server from the NT4. ... This newsgroup only focuses on SBS technical issues. ... possible to do an In-Place upgrade to w2k3 Standard and then an In-Place ... |> do a migration of the user and computer accounts. ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading to SBS 2003
    ... My idea was to upgrade the hardware and install a proper server OS. ... SBS is a server O/S, ...
    (microsoft.public.windows.server.sbs)
  • Re: P4 Xeon compatibility with 5.0.5
    ... > I am looking to upgrade our current Pentium II 300 Mhz. server. ... Maybe you can find an old P3 desktop and transfer the special hardware ... what's mostly going bad on the old box are the hard drives and the ...
    (comp.unix.sco.misc)
  • Re: Upgrading from sbs2k to 2003 Premium R2 - questions
    ... Where you buy should be decided based on the type of upgrade you plan ... Will this be an in-place upgrade (same hardware) or a migration ... Dell ships with SBS R2 Premium Edition for only $500 ...
    (microsoft.public.windows.server.sbs)