Re: Win2K Server to Win SBS 2003 migration

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: 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)
  • Re: Win2K Server to Win SBS 2003 migration
    ... The swing is great if you want to end up with all the shared data on the SBS ... Because the Win2K server ... to simply x-fer all the AD data from the Win2K server to the SBS 2003 box, ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2K Server to Win SBS 2003 migration
    ... a new machine was acquired with a copy of SBS 2003 ... Assuming his AD and DNS are in good shape, the only reason for a swing ... Adding an SBS server to an existing 2000 or 2003 non-SBS domain is easy ... Then, once the first transfer is finished, take the Win2K Server offline, ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2K Server to Win SBS 2003 migration
    ... The swing is great if you want to end up with all the shared data on the SBS ... Because the Win2K server ... to simply x-fer all the AD data from the Win2K server to the SBS 2003 box, ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2K Server to Win SBS 2003 migration
    ... Setup a new domain on the SBS 2003 box and use the ADMT to ... Then, once the first transfer is finished, take the Win2K Server offline, ... that was on the old Win2K server) and perform another ADMT transfer from ... domain info. ...
    (microsoft.public.windows.server.sbs)
Loading