Windows 2000 pdc to windows2003 pdc

G

Guest

Guest
Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

I want to upgrade a win2k pdc file server to a new file server running
win2003. Can I simply join the new file server to the existing domain,
promote the new file server, and then transfer the roles to the win2003
server, move the data over to the new file server, demote the old server and
be done.
--
sbrantl
 
Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

sbrantl typed this:

> I want to upgrade a win2k pdc file server to a new file server running
> win2003. Can I simply join the new file server to the existing domain,
> promote the new file server, and then transfer the roles to the win2003
> server, move the data over to the new file server, demote the old server and
> be done.


I'm no expert, but the idea of PDC and BDC (I believe) went away with
NT. If you 'have' a server running Windows 2000 Standard Srv you should
be able to UPGRADE it to Windows 2003 Standard server by installing the
Win2K3 NOS - that 'should' maintain all that server's settings, etc...
as you are not changing names, so forth... or are you saying that you
'have' a Win2K that will be going *bye-bye* once your NEW server
(Win2K3) is up and running? - Then I think you can do what you are
asking. Bring the Win2K3 into the domain, make it an AD integrated DC
and let it synchronize and propagate and then check with DCDIAG and
make sure all is fine... 'demote', using DCPromo, the Win2K and then
bring it out of the domain and gone. That's what I believe can be done.
 
Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

Your plan will work fine. You will be prompted to run a few prerequisite
tools before it will allow you to dcpromo the new Win2k3 box but it will
guide you as to what to do. If I remember correctly it will adprep and then
the AD is ready for a Win2k3 DC.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows Server Networking

"sbrantl" <sbrantl@kansas.net> wrote in message
news:00B8D47F-A06E-4944-8CE9-3A550EF2F160@microsoft.com...
>I want to upgrade a win2k pdc file server to a new file server running
> win2003. Can I simply join the new file server to the existing domain,
> promote the new file server, and then transfer the roles to the win2003
> server, move the data over to the new file server, demote the old server
> and
> be done.
> --
> sbrantl
 
Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

Thank you very much for your input.
--
sbrantl


"Scott Harding" wrote:

> Your plan will work fine. You will be prompted to run a few prerequisite
> tools before it will allow you to dcpromo the new Win2k3 box but it will
> guide you as to what to do. If I remember correctly it will adprep and then
> the AD is ready for a Win2k3 DC.
>
> --
> Scott Harding
> MCSE, MCSA, A+, Network+
> Microsoft MVP - Windows Server Networking
>
> "sbrantl" <sbrantl@kansas.net> wrote in message
> news:00B8D47F-A06E-4944-8CE9-3A550EF2F160@microsoft.com...
> >I want to upgrade a win2k pdc file server to a new file server running
> > win2003. Can I simply join the new file server to the existing domain,
> > promote the new file server, and then transfer the roles to the win2003
> > server, move the data over to the new file server, demote the old server
> > and
> > be done.
> > --
> > sbrantl
>
>
>
 
Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

Thank you very much for your input
--
sbrantl


"Doc" wrote:

> sbrantl typed this:
>
> > I want to upgrade a win2k pdc file server to a new file server running
> > win2003. Can I simply join the new file server to the existing domain,
> > promote the new file server, and then transfer the roles to the win2003
> > server, move the data over to the new file server, demote the old server and
> > be done.
>
>
> I'm no expert, but the idea of PDC and BDC (I believe) went away with
> NT. If you 'have' a server running Windows 2000 Standard Srv you should
> be able to UPGRADE it to Windows 2003 Standard server by installing the
> Win2K3 NOS - that 'should' maintain all that server's settings, etc...
> as you are not changing names, so forth... or are you saying that you
> 'have' a Win2K that will be going *bye-bye* once your NEW server
> (Win2K3) is up and running? - Then I think you can do what you are
> asking. Bring the Win2K3 into the domain, make it an AD integrated DC
> and let it synchronize and propagate and then check with DCDIAG and
> make sure all is fine... 'demote', using DCPromo, the Win2K and then
> bring it out of the domain and gone. That's what I believe can be done.
>