Re: Win2K Server to Win SBS 2003 migration

Thanks for the response. (and to everyone else who's responded) I'll speak
with the liason and find out the various options, and let you know what's
decided.

After reading the post, I agree that leaving anything on the old machine
could be seen as odd, though the old machine has a nice 10-bay, hot swapable
SCSI drive setup with RAID 5 and a nice DLT 7000 drive, where the new one
currently has just 2 internal SATA drives with RAID 1.

Most likely it will probably be a swing migration, and just use the old
Win2K for data backup, or additional storage.

Thanks once again for your time, help and advice, and I shall let you know
about the final progress once completed.

Regards,
-James-



"Gregg Hill" wrote:

If all you want to do is ADD an SBS 2003 system, and you DO NOT care if it
has a different server name (since you will leave your shares on the 2000),
then all you need is
http://support.microsoft.com/default.aspx?scid=kb;EN-US;884453 as noted by
Jim Martin.

The swing is great if you want to end up with all the shared data on the SBS
box and you do not want to go to each workstation to re-create the shares
and printer mapping (although most of that can be one with a login script, I
presume).

One question I have is why would you want to keep all your data on a box
that is nearly ten years old? That is just asking for trouble.

Gregg Hill




"James G" <JamesG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:11C964EE-0855-4A19-8758-78B3D20E4DE3@xxxxxxxxxxxxxxxx
Hi Greg,

Thanks for your confirmation about a the Swing Migration. I was looking
at
the site, and received an email back from Jeff at SBSMigration.com
confirming
that it would work im my scenario. Actually this copy of SBS 2003 is the
R2
Standard edition - Retail Box. (long, and funny, story about the previous
SBS 2003 version that came with the machine)

In thinking, and speaking with the liason at the business, I had an Idea
that -if possible - might be all that is needed. Because the Win2K server
right now is working OK right where it is, I am wondering if it is
possible
to simply x-fer all the AD data from the Win2K server to the SBS 2003 box,
demote the Win2K as the previous DC, and simply leave it in place as a
secondary file server, as there is a significant amount of backup data
that
has been placed on it over a period of (nearly) 9-10 years or so.

Is that a viable possibility where the SBS 2003 machine will be the DC and
manage the AD for the business, and the Win2K server will have the DC
demoted, add it in the 'Manage Servers' section on the SBS 2003 machine,
and
leave it in place as secondary file server? Or is this just creating more
hastle than using a Swing migration and transfer ALL over to the new SBS
2003
machine?

I appreciate your time, help and advise invested thus far.

Regards,
-James-


"Gregg Hill" wrote:

If you want to replace your 2000 DC with the SBS 2003 system, keeping all
AD
info, share paths, printer paths, server name and IP, etc, then you
definitely want to use a swing. The kit is WELL WORTH its price. Read up
the
docs before you buy it to see if it will work with OEM software. I assume
your new purchase of SBS was an OEM.

www.sbsmigration.com

BTW, it works for SBS and non-SBS migrations.

When you are done and have verified that the new system works perfectly
(give it a week or two), then you can format the old box and reinstall
2000,
then join the domain as a member server and make it your terminal server.

Gregg Hill


"James G" <JamesG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E555024E-962A-478D-AA0D-403DCF2D5BF9@xxxxxxxxxxxxxxxx
Thanks for all your posts so far. Tomorrow, and most of this weekend,
I
will
be spending time on this project and should have time to test all the
suggestions.

Greg-
Yes. From you assessment, I believe that is what my desired end result
would be. There is currently a Win2K machine that is running on an old
(but
great) machine. Recently, a new machine was acquired with a copy of
SBS
2003
R2. Because all the machines are already pointing to the previous DC
utilizing the original Domain, and the fact that the original machine
has
an
AD (with all the users, computers, permissions, etc...) that is
working,
several DNS & DHCP settings that are being referenced as well as the
fact
that the current computer name and IP address of the original server
are
being accessed, the ideal solution would be whatever is closest to
swaping
the original machine out for the new one with all the original settings
and
parameters.

If this method closely resembles the swing method, than I would imagine
that
this is the way to go.

Please let me know if any part of my message is unclear, and I greatly
appreciate everyone's help and advice thus far.

Regards,
-James-

"Gregg Hill" wrote:

He already has an intact AD, so a swing is not necessary, but may be
desired, depending upon his desired end result.

Assuming his AD and DNS are in good shape, the only reason for a swing
migration would be if he wants to keep the name of his current DC as
the
name for the new SBS 2003. If he just wants to add the SBS 2003 box to
the
domain with a different name than the current DC, then a swing is not
needed. He can do that using
http://support.microsoft.com/default.aspx?scid=kb;EN-US;884453 as
previously
noted.

Adding an SBS server to an existing 2000 or 2003 non-SBS domain is
easy
using 884453. However, he did not state if he intended to keep more
the
just
the domain name. If the intention is to keep the same domain name,
same
server name an IP, same file and printer shares on that DC, and remove
that
DC from service after the upgrade, then a swing is the way to go.

Another benefit of just doing the 884453 method is that he will have
the
old
box that he can dcpromo to a member and use as a terminal server.

Gregg Hill









"Frank F" <ffarero@xxxxxxxxxx> wrote in message
news:45dd8387$0$24698$4c368faf@xxxxxxxxxxxxxxxxx
www.sbsmigration.com
"James G" <James G@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F3EDDEEE-A45E-4192-8C00-D71EBA0D2C3B@xxxxxxxxxxxxxxxx
Hi everyone,

I just wanted to see if I can firm what I believe is the correct
process
to
migrate from Win2K Server on one box to Win SBS 2003 on another box
trying to
keep the same domain.

Setup a new (temporary) domain on the SBS 2003 box and use the ADMT
to
transfer all the AD info regarding permissions, users, etc... to
the
new
SBS
2003 box.

Then, once the first transfer is finished, take the Win2K Server
offline,
create a new DC on the SBS 2003 box (using the previous domain
information
that was on the old Win2K server) and perform another ADMT transfer
from
the
temporary created DC and transfer it to the DC that contains the
original
domain info.

Am I correct in my brief outline of steps above? From the
documents
I've
been printing off and reading, as well as the searches I've
performed,
it
seems like this is the logical path to follow. Since it's not a
rushed
support ticket, I have plenty of time to perform this task, but I
wanted
to
confirm with the community so that it's done correctly.

I appreciate any and all comments, and thank you all in advance for
your
assistance.

Regards,
-James-











.

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: 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: 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: 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)
  • Re: Win2K Server to Win SBS 2003 migration
    ... Thanks for your confirmation about a the Swing Migration. ... Actually this copy of SBS 2003 is the R2 ... to simply x-fer all the AD data from the Win2K server to the SBS 2003 box, ... manage the AD for the business, and the Win2K server will have the DC ...
    (microsoft.public.windows.server.sbs)