Windows Server

Bill · Guest

Migrating SBS 2000 to SBS 2003. 15 users. 60GB data. No server apps except
SBS suite. Ho much time should I allow for a first-time migration?
Cheers, Bill

Frank McCallister SBS MVP · Guest

Hi Bill

Too many variables to give a precise time. It depends on your experience in
SBS installs and the health of your SBS 2000 system and the hardware you
will be using. The Time will be broken up into several phases.

1. Planning and Preparation - Most important phase!!! Read Jeff's Document
completely through taking notes on your situation. Even after doing several
of these Migrations I don't skip this step although it is more Planning than
study now. Decide on hardware for Migration DC, I use my Laptop for
convenience with VPC (Virtual PC) to load the Migration SBS.

2. Perform the Domain Audit of your SBS 2000 using Jeff's Domain Audit Guide
to be sure it meets ALL the requirements of the Migration before you start.

3. Prepare and replicate the 2000 Box to the Migration DC. This is the
critical step and once you have insured that replication is complete and the
Migration DC is disconnected your Production box continues while you work
separately until you are ready to transfer data and connect your
Workstations.

4. Installation of Production box and transfer of AD and data.

Depending on your skills, speed of hardware, health of system, the Time
could run from a minimum of 15 hours to 25 hours. System down time is
amount of time it takes to move the server into position and connect. I have
done that in less than an hour.

--
Frank McCallister SBS MVP
COMPUMAC
"Bill" <billyg1943@hotmail.com> wrote in message
news:%23nDXdQR5FHA.3592@TK2MSFTNGP12.phx.gbl...

David Elders · Guest

And the real beauty is that as Stage 4 is done offline, you can spread this
out over whatever timeframe you like before you do the connect and bring
your live data and Exchange over during the system downtime...

Regards,

David

"Frank McCallister SBS MVP" <anonymous> wrote in message
news:ut1I$PT5FHA.2364@TK2MSFTNGP12.phx.gbl...

Bill · Guest

Thanks Frank & David. I was hoping to make a wild guess so I could tell my
client at least ballpark numbers. Cheers, Bill.
"David Elders" <david_elders@hotmail.com.nospam> wrote in message
news:unGnZ9U5FHA.2484@TK2MSFTNGP09.phx.gbl...

Bill · Guest

Hi Frank, So the migration server can be almost any PC? I'd better get the
kit and make a start! 15-25 hours doesn't sound too horrendous. Better to
spend this time in non-production environment than to risk an unknown amount
of time with a non-functioning server, especially if things go pear shaped,
eh? Cheers, Bill.
"Frank McCallister SBS MVP" <anonymous> wrote in message
news:ut1I$PT5FHA.2364@TK2MSFTNGP12.phx.gbl...

Eddie McGlone · Guest

Can I chip in as I've just done my first. SBS 2000 - 2003, 45 users, about
80Gb data.

I had to start again as I had ignored a file replication error on the old
server which prevented the SYVOL folder from being created on the new temp
DC. Didn't notice till I was trying to transfer AD onto the new server! Also
make sure you allow enough time for the AD transfers - the second time I did
it I left it overnight but probably a couple of hours would be enough.

I used my desktop pc with spare drive to build the temp DC. If I needed to
work on something else, I just disconnected that drive and reconnected the
normal one.

Our old server had two mirrored drives. when the time came to transfer the
data across to the new server, I took one of the drives out of the old
server and connected it in the new one. I then used Arcserve (our backup
software) to copy the data over with all ntfs permissions intact to the
correct locations on the new server. Set it off on the friday at about 5
0'clock and it was all done and ready for me on the Saturday morning.
Mounted the exchange stores, checked connectivity etc. and was done within 3
hours on the Saturday morning. Monday, everyone logged in as usual - no
issues - it's a miracle!!

During all this time up to close of business on the Friday, the old server
was still up and running and we could roll back onto it at any point if
disaster had struck during the weekend. In fact if we need something like an
old mailbox that we have cleaned out of the new exchange store, we can still
fire it up and log onto it now!

A couple of thing have caught us out - an old Group Policy from the 2000
domain broke our Connect Internet and email and Remote Access wizards - I
have posted the solutions in a previous thread and I forgot to add a little
used domain into the new exchange server's recipient policy so we were
rejecting emails for that one until it was drawn to our attention.

All in all from the users' point of view it was seamless and from my point
of view it was far less work than normal and stress levels were down!

Hope it goes well for you too.

Ed
"Bill" <billyg1943@hotmail.com> wrote in message
news:ON34C3p5FHA.444@TK2MSFTNGP11.phx.gbl...

Bill · Guest

Thanks, Eddie, for your encouraging post. Even when I know this is a great
migration methodology, it is still pretty scary if you haven't done one
before. No matter what, I just keep telling myself any alternative method
would be infinitely scarier! I will file this post away with other
"gotchas" and hopefully avoid most of them. If anyone here has any more of
these to contribute I'm sure everyone in this forum would be eternally
grateful. Hope some of you are around on the day(s) in case I need any
handholding! Cheers, Bill

"Eddie McGlone" <ed.mcglone@strathclydehomes.com> wrote in message
news:11n92j24b9ahv2d@corp.supernews.com...

	Windows Server Forum Index -> Small Business Server 2003	All times are GMT
Page 1 of 1