"Diane Alsing" wrote:

> After reading the question I posted below - I was even confused - so this is
> really what I want to get at.
>
> I have Windows Server 2000 deployed with AD.  I have added a Windows Server
> 2003 to the network in hopes of one day promoting it to be the primary domain
> controller.  My question is, should I install the AD on the 2003 Server also,
> and if I do, will it duplicate the info from the 2000 Server?  I believe I
> understood that if I did this, the 2003 Server would be the secondary
> controller & would promote itself should the primary server go down.
>
> Thank you.

"Desmond Lee" wrote:

> W2k3 Server can be a normal member server in the W2k AD environment. It can
> also be made a DC but new features will not be available until all W2k DCs
> have been upgraded (to W2k3 - W2k3 "functional" forest / domain level).
>
> Moving to a complete W2k3 based AD infrastructure requires several
> preparatory tasks (/forestprep, /domainprep) that belong to good planning and
> design.
>
> Hope this helps to clarify matters. Do let us know. Thanks.
>
>
> "Diane Alsing" wrote:
>
> > After reading the question I posted below - I was even confused - so this is
> > really what I want to get at.
> >
> > I have Windows Server 2000 deployed with AD.  I have added a Windows Server
> > 2003 to the network in hopes of one day promoting it to be the primary domain
> > controller.  My question is, should I install the AD on the 2003 Server also,
> > and if I do, will it duplicate the info from the 2000 Server?  I believe I
> > understood that if I did this, the 2003 Server would be the secondary
> > controller & would promote itself should the primary server go down.
> >
> > Thank you.

"Diane Alsing" wrote:

> I currently only have 1 DC Windows Server 2000 with other 2000 Servers on the
> network.
>
> I just want to verify - Can I ad the new 2003 server as a DC (in addition to
> the 2000) without upgrading the 2000 DC Server?  I think I understand that I
> can by doing the following (if you could just verify for me ;-)
>
> 1 - disconnect Windows Server 2000 from network
> 2 - run adprep/forestprep
> 3- if no errors, I should be able to add Windows Server 2003 as additional DC
>
> This will not have all features of 2003 until the 2000 server is upgraded.
>
> Will this replicate the 2000 Server?
>
> Then, to upgrade the 2000 to 2003, all I should now have to do is back-up
> the 2000 DC Server & install the software?
>
> "Desmond Lee" wrote:
>
> > W2k3 Server can be a normal member server in the W2k AD environment. It can
> > also be made a DC but new features will not be available until all W2k DCs
> > have been upgraded (to W2k3 - W2k3 "functional" forest / domain level).
> >
> > Moving to a complete W2k3 based AD infrastructure requires several
> > preparatory tasks (/forestprep, /domainprep) that belong to good planning and
> > design.
> >
> > Hope this helps to clarify matters. Do let us know. Thanks.
> >
> >
> > "Diane Alsing" wrote:
> >
> > > After reading the question I posted below - I was even confused - so this is
> > > really what I want to get at.
> > >
> > > I have Windows Server 2000 deployed with AD.  I have added a Windows Server
> > > 2003 to the network in hopes of one day promoting it to be the primary domain
> > > controller.  My question is, should I install the AD on the 2003 Server also,
> > > and if I do, will it duplicate the info from the 2000 Server?  I believe I
> > > understood that if I did this, the 2003 Server would be the secondary
> > > controller & would promote itself should the primary server go down.
> > >
> > > Thank you.

"Allen Firouz" wrote:

> Diane,
>
> First off, a clarification:  In AD, there are no BDC's.  All DC's are on the
> same level!
> Now, based on your environment, you can install Win2003 server in your 2000
> AD, then DCpromo it and make it a DC on your existing 2000 AD.  This would
> make your AD "2003 Mixed Mode".  When you introduce the 2003 DC, AD will
> automatically replicate the directory and Sysvol to the new server.  You
> should NOT disjoin the 2003 and Dcpromo it, because then you will have 2
> separate AD environments and you have to migrate everything from one to the
> other.  Add the member server and Dcpromo to make it an "additional DC in an
> existing Forest".
> Now, to upgrade fully, you move the FSMO roles to the 2003 DC and upgrade
> the remaining DC's to 2003 as well.  Once all your DC's (not member servers)
> are 2003, flip the bit and make it a 2003 Native Mode (ADS&S > Domain right
> click and elevate domain mode).
> This link willl help a lot:
> http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2ktows03-2.mspx
> and this for additional iinfo: http://support.microsoft.com/kb/325379
>
> -Allen Firouz
>
>
> "Diane Alsing" wrote:
>
> > I currently only have 1 DC Windows Server 2000 with other 2000 Servers on the
> > network.
> >
> > I just want to verify - Can I ad the new 2003 server as a DC (in addition to
> > the 2000) without upgrading the 2000 DC Server?  I think I understand that I
> > can by doing the following (if you could just verify for me ;-)
> >
> > 1 - disconnect Windows Server 2000 from network
> > 2 - run adprep/forestprep
> > 3- if no errors, I should be able to add Windows Server 2003 as additional DC
> >
> > This will not have all features of 2003 until the 2000 server is upgraded.
> >
> > Will this replicate the 2000 Server?
> >
> > Then, to upgrade the 2000 to 2003, all I should now have to do is back-up
> > the 2000 DC Server & install the software?
> >
> > "Desmond Lee" wrote:
> >
> > > W2k3 Server can be a normal member server in the W2k AD environment. It can
> > > also be made a DC but new features will not be available until all W2k DCs
> > > have been upgraded (to W2k3 - W2k3 "functional" forest / domain level).
> > >
> > > Moving to a complete W2k3 based AD infrastructure requires several
> > > preparatory tasks (/forestprep, /domainprep) that belong to good planning and
> > > design.
> > >
> > > Hope this helps to clarify matters. Do let us know. Thanks.
> > >
> > >
> > > "Diane Alsing" wrote:
> > >
> > > > After reading the question I posted below - I was even confused - so this is
> > > > really what I want to get at.
> > > >
> > > > I have Windows Server 2000 deployed with AD.  I have added a Windows Server
> > > > 2003 to the network in hopes of one day promoting it to be the primary domain
> > > > controller.  My question is, should I install the AD on the 2003 Server also,
> > > > and if I do, will it duplicate the info from the 2000 Server?  I believe I
> > > > understood that if I did this, the 2003 Server would be the secondary
> > > > controller & would promote itself should the primary server go down.
> > > >
> > > > Thank you.

"Diane Alsing" wrote:

> I just want to clarify that you are suggesting going to the Windows Server
> 2000, choosing Active Directory Sites & Services, and adding the new 2003
> server name there
> Then I should promote it to a domain controller  (not sure how to do this -
> ??)
> Then go to the 2003  server & add AD
>
> (sorry - i'm very new to this)
>
> "Allen Firouz" wrote:
>
> > Diane,
> >
> > First off, a clarification:  In AD, there are no BDC's.  All DC's are on the
> > same level!
> > Now, based on your environment, you can install Win2003 server in your 2000
> > AD, then DCpromo it and make it a DC on your existing 2000 AD.  This would
> > make your AD "2003 Mixed Mode".  When you introduce the 2003 DC, AD will
> > automatically replicate the directory and Sysvol to the new server.  You
> > should NOT disjoin the 2003 and Dcpromo it, because then you will have 2
> > separate AD environments and you have to migrate everything from one to the
> > other.  Add the member server and Dcpromo to make it an "additional DC in an
> > existing Forest".
> > Now, to upgrade fully, you move the FSMO roles to the 2003 DC and upgrade
> > the remaining DC's to 2003 as well.  Once all your DC's (not member servers)
> > are 2003, flip the bit and make it a 2003 Native Mode (ADS&S > Domain right
> > click and elevate domain mode).
> > This link willl help a lot:
> > http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2ktows03-2.mspx
> > and this for additional iinfo: http://support.microsoft.com/kb/325379
> >
> > -Allen Firouz
> >
> >
> > "Diane Alsing" wrote:
> >
> > > I currently only have 1 DC Windows Server 2000 with other 2000 Servers on the
> > > network.
> > >
> > > I just want to verify - Can I ad the new 2003 server as a DC (in addition to
> > > the 2000) without upgrading the 2000 DC Server?  I think I understand that I
> > > can by doing the following (if you could just verify for me ;-)
> > >
> > > 1 - disconnect Windows Server 2000 from network
> > > 2 - run adprep/forestprep
> > > 3- if no errors, I should be able to add Windows Server 2003 as additional DC
> > >
> > > This will not have all features of 2003 until the 2000 server is upgraded.
> > >
> > > Will this replicate the 2000 Server?
> > >
> > > Then, to upgrade the 2000 to 2003, all I should now have to do is back-up
> > > the 2000 DC Server & install the software?
> > >
> > > "Desmond Lee" wrote:
> > >
> > > > W2k3 Server can be a normal member server in the W2k AD environment. It can
> > > > also be made a DC but new features will not be available until all W2k DCs
> > > > have been upgraded (to W2k3 - W2k3 "functional" forest / domain level).
> > > >
> > > > Moving to a complete W2k3 based AD infrastructure requires several
> > > > preparatory tasks (/forestprep, /domainprep) that belong to good planning and
> > > > design.
> > > >
> > > > Hope this helps to clarify matters. Do let us know. Thanks.
> > > >
> > > >
> > > > "Diane Alsing" wrote:
> > > >
> > > > > After reading the question I posted below - I was even confused - so this is
> > > > > really what I want to get at.
> > > > >
> > > > > I have Windows Server 2000 deployed with AD.  I have added a Windows Server
> > > > > 2003 to the network in hopes of one day promoting it to be the primary domain
> > > > > controller.  My question is, should I install the AD on the 2003 Server also,
> > > > > and if I do, will it duplicate the info from the 2000 Server?  I believe I
> > > > > understood that if I did this, the 2003 Server would be the secondary
> > > > > controller & would promote itself should the primary server go down.
> > > > >
> > > > > Thank you.