Windows 2000 PDC and BDC migration to Windows 2003 BDC

[Guest Sam Wishka]

Hi,

 

My current configuration is Windows 2K PDC and Windows 2K BDC.

I installed a new Windows 2003 meber server. i want them to Upgrade from

Windows 2000 Server Dc to Windows Server 2003 DC.

How dO I upgrade windows 2000 DC on my windows 2003 meber server?

 

thanks,

Sam

[Guest Meinolf Weber]

Re: Windows 2000 PDC and BDC migration to Windows 2003 BDC

 

Hello Sam,

 

 

!!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

 

One question first:

Is one of the old servers also Exchange server and will it be taken out of

the domain

forever, when the new server is running?

 

- On the old server open DNS management console and check that you are running

Active directory integrated zone (easier for replication, if you have more

then one DNS server)

 

- run replmon, dcdiag and netdiag on the old machine to check for errors,

if you have some post the complete output from the command here or solve

them first

 

- run adprep /forestprep and adprep /domainprep from the 2003 installation

disk against the 2000 server, with an account that is member of the Schema

admins, to upgrade the schema to the new version

 

- Install the new machine as a member server in your existing domain

 

- configure a fixed ip and set the preferred DNS server to the old DNS server

only

 

- run dcpromo and follow the wizard to add the 2003 server to an existing

domain

 

- if you are prompted for DNS configuration choose Yes (also possible that

no DNS preparation occur), then install DNS after the reboot

 

- for DNS give the server time for replication, at least 15 minutes. Because

you use Active directory integrated zones it will automatically replicate

the zones to the new server. Open DNS management console to check that they

appear

 

- if the new machine is domain controller and DNS server run again replmon,

dcdiag and netdiag on both domain controllers

 

- if you have no errors, make the new server Global catalog server, open

Active directory Sites and Services and then double-click sitename, double-click

Servers, click your domain controller, right-click NTDS Settings, and then

click Properties, on the General tab, click to select the Global catalog

check box (http://support.microsoft.com/?id=313994)

 

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

 

- you can see in the event viewer (Directory service) that the roles are

transferred, also give it some time

 

- reconfigure the DNS configuration on your NIC of the 2003 server, preferred

DNS itself, secondary the old one

 

- if you use DHCP do not forget to reconfigure the scope settings to point

to the new installed DNS server

 

- export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473

 

 

Demoting if needed

 

- reconfigure your clients/servers that they not longer point to the old

DC/DNS server on the NIC

 

- to be sure that everything runs fine, disconnect the old DC from the network

and check with clients and servers the connectivity, logon and also with

one client a restart to see that everything is ok

 

- then run dcpromo to demote the old DC, if it works fine the machine will

move from the DC's OU to the computers container, where you can delete it

by hand. Can be that you got an error during demoting at the beginning, then

uncheck the Global catalog on that DC and try again

 

- check the DNS management console, that all entries from the machine are

disappeared or delete them by hand if the machine is off the network for ever

 

 

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> Hi,

>

> My current configuration is Windows 2K PDC and Windows 2K BDC.

> I installed a new Windows 2003 meber server. i want them to Upgrade

> from

> Windows 2000 Server Dc to Windows Server 2003 DC.

> How dO I upgrade windows 2000 DC on my windows 2003 meber server?

> thanks,

> Sam

[Guest Sam Wishka]

RE: Windows 2000 PDC and BDC migration to Windows 2003 BDC

 

Hi Meinolf,

 

Thank you for response.

Sam

 

"Sam Wishka" wrote:

> Hi,

>

> My current configuration is Windows 2K PDC and Windows 2K BDC.

> I installed a new Windows 2003 meber server. i want them to Upgrade from

> Windows 2000 Server Dc to Windows Server 2003 DC.

> How dO I upgrade windows 2000 DC on my windows 2003 meber server?

>

> thanks,

> Sam

[Guest Edwin vMierlo [MVP]]

Re: Windows 2000 PDC and BDC migration to Windows 2003 BDC

 

>

> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

>

 

Change that to:

 

Never start before having created AND TESTED a backup of your data/machine

[Guest Meinolf Weber]

Re: Windows 2000 PDC and BDC migration to Windows 2003 BDC

 

Hello Edwin vMierlo [MVP],

 

You are right, i will change it directly.:-)

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

>> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

>>

> Change that to:

>

> Never start before having created AND TESTED a backup of your

> data/machine

>

[Guest Sam Wishka]

Re: Windows 2000 PDC and BDC migration to Windows 2003 BDC

 

 

Hi Meinolf,

 

I am ruining C:\I386>adprep /forestPre on a member server windows 2003 .

Trouble is that adprep/forestprep says that:

Adprep cannot run on this platform because it is not a domain controller

[status/Consequence]

Adprep stopped without making any changes.

[user Action]

Run Adprep on a domain controller.

 

Thanks,

 

Sam

 

 

"Meinolf Weber" wrote:

> Hello Sam,

>

>

> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

>

> One question first:

> Is one of the old servers also Exchange server and will it be taken out of

> the domain

> forever, when the new server is running?

>

> - On the old server open DNS management console and check that you are running

> Active directory integrated zone (easier for replication, if you have more

> then one DNS server)

>

> - run replmon, dcdiag and netdiag on the old machine to check for errors,

> if you have some post the complete output from the command here or solve

> them first

>

> - run adprep /forestprep and adprep /domainprep from the 2003 installation

> disk against the 2000 server, with an account that is member of the Schema

> admins, to upgrade the schema to the new version

>

> - Install the new machine as a member server in your existing domain

>

> - configure a fixed ip and set the preferred DNS server to the old DNS server

> only

>

> - run dcpromo and follow the wizard to add the 2003 server to an existing

> domain

>

> - if you are prompted for DNS configuration choose Yes (also possible that

> no DNS preparation occur), then install DNS after the reboot

>

> - for DNS give the server time for replication, at least 15 minutes. Because

> you use Active directory integrated zones it will automatically replicate

> the zones to the new server. Open DNS management console to check that they

> appear

>

> - if the new machine is domain controller and DNS server run again replmon,

> dcdiag and netdiag on both domain controllers

>

> - if you have no errors, make the new server Global catalog server, open

> Active directory Sites and Services and then double-click sitename, double-click

> Servers, click your domain controller, right-click NTDS Settings, and then

> click Properties, on the General tab, click to select the Global catalog

> check box (http://support.microsoft.com/?id=313994)

>

> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

>

> - you can see in the event viewer (Directory service) that the roles are

> transferred, also give it some time

>

> - reconfigure the DNS configuration on your NIC of the 2003 server, preferred

> DNS itself, secondary the old one

>

> - if you use DHCP do not forget to reconfigure the scope settings to point

> to the new installed DNS server

>

> - export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473

>

>

> Demoting if needed

>

> - reconfigure your clients/servers that they not longer point to the old

> DC/DNS server on the NIC

>

> - to be sure that everything runs fine, disconnect the old DC from the network

> and check with clients and servers the connectivity, logon and also with

> one client a restart to see that everything is ok

>

> - then run dcpromo to demote the old DC, if it works fine the machine will

> move from the DC's OU to the computers container, where you can delete it

> by hand. Can be that you got an error during demoting at the beginning, then

> uncheck the Global catalog on that DC and try again

>

> - check the DNS management console, that all entries from the machine are

> disappeared or delete them by hand if the machine is off the network for ever

>

>

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > Hi,

> >

> > My current configuration is Windows 2K PDC and Windows 2K BDC.

> > I installed a new Windows 2003 meber server. i want them to Upgrade

> > from

> > Windows 2000 Server Dc to Windows Server 2003 DC.

> > How dO I upgrade windows 2000 DC on my windows 2003 meber server?

> > thanks,

> > Sam

>

>

>

[Guest Meinolf Weber]

Re: Windows 2000 PDC and BDC migration to Windows 2003 BDC

 

Hello Sam,

 

You have ti run adprep on the schema master of the domain with an account

that is member of the schema admins, not on a member server. To find out

your schema master run on a DC "netdom query fsmo" without the quotes on

a command prompt.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> Hi Meinolf,

>

> I am ruining C:\I386>adprep /forestPre on a member server windows 2003

> .

> Trouble is that adprep/forestprep says that:

> Adprep cannot run on this platform because it is not a domain

> controller

> [status/Consequence]

> Adprep stopped without making any changes.

> [user Action]

> Run Adprep on a domain controller.

> Thanks,

>

> Sam

>

> "Meinolf Weber" wrote:

>

>> Hello Sam,

>>

>> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

>>

>> One question first:

>> Is one of the old servers also Exchange server and will it be taken

>> out of

>> the domain

>> forever, when the new server is running?

>> - On the old server open DNS management console and check that you

>> are running Active directory integrated zone (easier for replication,

>> if you have more then one DNS server)

>>

>> - run replmon, dcdiag and netdiag on the old machine to check for

>> errors, if you have some post the complete output from the command

>> here or solve them first

>>

>> - run adprep /forestprep and adprep /domainprep from the 2003

>> installation disk against the 2000 server, with an account that is

>> member of the Schema admins, to upgrade the schema to the new version

>>

>> - Install the new machine as a member server in your existing domain

>>

>> - configure a fixed ip and set the preferred DNS server to the old

>> DNS server only

>>

>> - run dcpromo and follow the wizard to add the 2003 server to an

>> existing domain

>>

>> - if you are prompted for DNS configuration choose Yes (also possible

>> that no DNS preparation occur), then install DNS after the reboot

>>

>> - for DNS give the server time for replication, at least 15 minutes.

>> Because you use Active directory integrated zones it will

>> automatically replicate the zones to the new server. Open DNS

>> management console to check that they appear

>>

>> - if the new machine is domain controller and DNS server run again

>> replmon, dcdiag and netdiag on both domain controllers

>>

>> - if you have no errors, make the new server Global catalog server,

>> open Active directory Sites and Services and then double-click

>> sitename, double-click Servers, click your domain controller,

>> right-click NTDS Settings, and then click Properties, on the General

>> tab, click to select the Global catalog check box

>> (http://support.microsoft.com/?id=313994)

>>

>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller

>> (http://support.microsoft.com/kb/324801)

>>

>> - you can see in the event viewer (Directory service) that the roles

>> are transferred, also give it some time

>>

>> - reconfigure the DNS configuration on your NIC of the 2003 server,

>> preferred DNS itself, secondary the old one

>>

>> - if you use DHCP do not forget to reconfigure the scope settings to

>> point to the new installed DNS server

>>

>> - export and import of DHCP database (if needed)

>> http://support.microsoft.com/kb/325473

>>

>> Demoting if needed

>>

>> - reconfigure your clients/servers that they not longer point to the

>> old DC/DNS server on the NIC

>>

>> - to be sure that everything runs fine, disconnect the old DC from

>> the network and check with clients and servers the connectivity,

>> logon and also with one client a restart to see that everything is ok

>>

>> - then run dcpromo to demote the old DC, if it works fine the machine

>> will move from the DC's OU to the computers container, where you can

>> delete it by hand. Can be that you got an error during demoting at

>> the beginning, then uncheck the Global catalog on that DC and try

>> again

>>

>> - check the DNS management console, that all entries from the machine

>> are disappeared or delete them by hand if the machine is off the

>> network for ever

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> Hi,

>>>

>>> My current configuration is Windows 2K PDC and Windows 2K BDC.

>>> I installed a new Windows 2003 meber server. i want them to

>>> Upgrade

>>> from

>>> Windows 2000 Server Dc to Windows Server 2003 DC.

>>> How dO I upgrade windows 2000 DC on my windows 2003 meber server?

>>> thanks,

>>> Sam