demote to BDC

[Guest]

Dear all,

The question as below:
- NT 4 server as PDC (running WIN)
- 2 x Win2K server as BDC (running DNS)
I want to one of Win2K server promote to PDC, and NT 4 server demote to BDC.
How to do it ?

Thanks you for your attention

Chris

 

[Danny Sanders]

- 2 x Win2K server as BDC (running DNS)

I want to one of Win2K server promote to PDC, and NT 4 server demote to
BDC.
How to do it ?

Win 2k can not be a BDC. There is no such thing as a BDC in Win 2k.You have
2 x Win 2k member servers in a NT 4.0 domain.

I want to one of Win2K server promote to PDC,

To make a Win 2k member server a DC you run dcpromo. You should be aware
that this will create a new domain on the Win 2k server that has nothing to
do with the NT 4.0 domain.

On an NT 4.0 domain the ONLY DC that holds a writeable copy of the SAM is
the PDC. In order to carry that SAM into the Win 2k domain you MUST upgrade
the PDC first. Upgrading any other server before the PDC will create a new
SAM. New SAM = new domain as far as your clients are concerned.

Consider setting up a "box" (a PC will do for the "box") and installing NT
4.0 on it as a BDC while connected to your existing network, promote to PDC,
then upgrade to Win 2k and AD. Then promote one of your existing Win 2k
member servers to a DC, then transfer the FSMO roles to the new Win 2k DC.
Then you would run dcpromo on the "box" to make it a member server and
remove it from the domain.

You will be left with one of your existing Win 2k member servers as a Win 2k
DC, your existing PDC will be demoted to a BDC and your Win 2k domain will
be in mixed mode which supports NT 4.0 BDCs.

You should research Upgrading a NT 4.0 PDC to Win 2k, see:
How to Upgrade Windows NT Server Version 4.0 to Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;298107



You should research transferring the FSMO roles, see:

How To View and transfer FSMO Roles in the Graphical User Interface

http://support.microsoft.com/default.aspx?scid=kb;en-us;255690



Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
http://support.microsoft.com/default.aspx?scid=kb;en-us;255504



For you to have any chance of doing this you need to know AD's DNS needs
see:

Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

How to configure DNS for Internet access in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202



hth

DDS W 2k MVP MCSE

 

[Guest]

Thanks you for help. I will try it.

Win 2k can not be a BDC. There is no such thing as a BDC in Win 2k.You have
2 x Win 2k member servers in a NT 4.0 domain.


To make a Win 2k member server a DC you run dcpromo. You should be aware
that this will create a new domain on the Win 2k server that has nothing to
do with the NT 4.0 domain.

On an NT 4.0 domain the ONLY DC that holds a writeable copy of the SAM is
the PDC. In order to carry that SAM into the Win 2k domain you MUST upgrade
the PDC first. Upgrading any other server before the PDC will create a new
SAM. New SAM = new domain as far as your clients are concerned.

Consider setting up a "box" (a PC will do for the "box") and installing NT
4.0 on it as a BDC while connected to your existing network, promote to PDC,
then upgrade to Win 2k and AD. Then promote one of your existing Win 2k
member servers to a DC, then transfer the FSMO roles to the new Win 2k DC.
Then you would run dcpromo on the "box" to make it a member server and
remove it from the domain.

You will be left with one of your existing Win 2k member servers as a Win 2k
DC, your existing PDC will be demoted to a BDC and your Win 2k domain will
be in mixed mode which supports NT 4.0 BDCs.

You should research Upgrading a NT 4.0 PDC to Win 2k, see:
How to Upgrade Windows NT Server Version 4.0 to Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;298107



You should research transferring the FSMO roles, see:

How To View and transfer FSMO Roles in the Graphical User Interface

http://support.microsoft.com/default.aspx?scid=kb;en-us;255690



Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
http://support.microsoft.com/default.aspx?scid=kb;en-us;255504



For you to have any chance of doing this you need to know AD's DNS needs
see:

Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

How to configure DNS for Internet access in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202



hth

DDS W 2k MVP MCSE