Migrating W2K domain to SBS 2003

Hi
we've got a Windows 2000 domain with a single DC and we'd like to move towards SBS 2003 (and keeping the current DC and domain name). What is the best way to do that
I thought of adding the new server as a Windows 2000 DC, trasfer the FSMO roles to this server and then upgrade it to SBS 2003. The original DC will be preserved and will act a secondary DC. Could be this the best way

Thanks in advance.

Ric
Tue Dec 23 10:30:05 CST 2003

That sounds like a fair way - but bear in mind that you will have an
upgraded box as opposed to a clean install which I would prefer. You could
achieve this by installing 2k as a DC on a spare box and transfer the FSMO
roles as you said. Then upgrade this spare box to 2003. You will now have
a 2k3 domain to which you can add the new server as a DC and transfer the
FSMO roles again. Voilla! You now have a fully clean install of 2k3 but
you keep your existing domain and SIDs.

I like this version slightly better than yours as there won't be any
remnants of a 2000 install hanging around on your box.

"Mickey" <anonymous@discussions.microsoft.com> wrote in message
news:788538A2-629B-474B-8122-ED3C6239D9DA@microsoft.com...
> Hi,
> we've got a Windows 2000 domain with a single DC and we'd like to move
towards SBS 2003 (and keeping the current DC and domain name). What is the
best way to do that?
> I thought of adding the new server as a Windows 2000 DC, trasfer the FSMO
roles to this server and then upgrade it to SBS 2003. The original DC will
be preserved and will act a secondary DC. Could be this the best way?
>
> Thanks in advance.

anonymous
Tue Dec 23 10:46:15 CST 2003

Thank you Ric. From what I can understand, the third server will be installed as a Windows 2003 DC and then upgraded to SBS 2003. Is this correct?

Mickey

Ric
Tue Dec 23 10:56:21 CST 2003

Sorry, yes that's right. As I said - your way will work just fine but this
way you will have a cleaner install.

"Mickey" <anonymous@discussions.microsoft.com> wrote in message
news:258FA2A6-A683-411A-9B6A-9C406830A5E2@microsoft.com...
> Thank you Ric. From what I can understand, the third server will be
installed as a Windows 2003 DC and then upgraded to SBS 2003. Is this
correct?
>
> Mickey

SuperGumby
Tue Dec 23 12:11:35 CST 2003

but it's unnecessary.

use the SBS 2003 media to do a clean install on the new hardware but only do
the W2K3 part. Use adprep, from the SBS2K3 CD, to extend your current 2000
AD to accomodate W2K3 DC's ('adprep /forestprep' & 'adprep /domainprep').
Join W2K3 to the domain and dcpromo it into a DC role, move the FSMO roles,
make it a GC, continue with SBS setup.

Did it this afternoon.

"Ric" <ric@somewhere.com> wrote in message
news:eB0lHVXyDHA.2340@TK2MSFTNGP12.phx.gbl...
> Sorry, yes that's right. As I said - your way will work just fine but
this
> way you will have a cleaner install.
>
> "Mickey" <anonymous@discussions.microsoft.com> wrote in message
> news:258FA2A6-A683-411A-9B6A-9C406830A5E2@microsoft.com...
> > Thank you Ric. From what I can understand, the third server will be
> installed as a Windows 2003 DC and then upgraded to SBS 2003. Is this
> correct?
> >
> > Mickey
>
>

anonymous
Tue Dec 23 12:41:05 CST 2003

Okay, that is gonna be my scenario. I want the SBS machine to hold the FSMO roles and keep the original Windows 2000 DC as an additional DC in the new SBS environment. What you did is just like the installation of a normal W2K3 DC in an existing W2K structure, the SBS part can be performed afterwards and it's pretty straightforward, is this correct?

On the Microsoft website I found also a whitepaper about this issue (http://www.microsoft.com/WindowsServer2003/sbs/upgrade/default.mspx) . It is recommended to use another DNS name, another domain name and use ADMT for migration. This is nonsense.

Thanks again.

SuperGumby
Tue Dec 23 13:07:00 CST 2003

really, it doesn't matter what you want, SBS _must_ have the FSMO roles.

Yes, once you have the 2K3 machine as DC and holding the FSMO roles it's
pretty well 'follow the bouncing ball'.

The upgrade document you refer to has info about two procedures 'upgrade' or
'migrate', the new server name, new domain name, and ADMT is only required
for 'migrate'.

"Mickey" <anonymous@discussions.microsoft.com> wrote in message
news:731B9893-2D7B-4037-8C28-1B65B67238AB@microsoft.com...
> Okay, that is gonna be my scenario. I want the SBS machine to hold the
FSMO roles and keep the original Windows 2000 DC as an additional DC in the
new SBS environment. What you did is just like the installation of a normal
W2K3 DC in an existing W2K structure, the SBS part can be performed
afterwards and it's pretty straightforward, is this correct?
>
> On the Microsoft website I found also a whitepaper about this issue
(http://www.microsoft.com/WindowsServer2003/sbs/upgrade/default.mspx) . It
is recommended to use another DNS name, another domain name and use ADMT for
migration. This is nonsense.
>
> Thanks again.

anonymous
Sat Feb 28 23:26:07 CST 2004

Hi

I would like to know how did your installation go did you have many problems or was it straight forward. Only other question I like to ask is about Exchange Server 5.5 migration from w2k server to SBS 2003 server into Excahange 2003

our Scenario is thi

We have W2K Server with one DC and running exchange 5.5
We have purchased a new server on which we would like to run SBS 2003 with exchange 200
We would like to keep the same domain name and make sbs 2003 as the main DC and make the old w2k server as additional DC

Thanks in advance