Promoting a Win2k server to PDC in an NT4 network

[rdurant]

I have network that contains an NT4 server which currently acts as the PDC for that domain. I recently added a Win2k server to that domain and I want this server to take over the PDC role in this domain. Is this possible? and if so, how is it done?

I realise that one cannot promote the server to a PDC from Server Manager, neither can I promote it using 'dcpromo'...

I choose 'Additional domain controller for an existing domain' and it tells me that the domain is not an AD domain, or an AD domain controller for that domain could not be found.

Thanks,
Ryan

 

[zmann]

rdurant,

You can not make a W2K server a PDC. You can only make it a Domain Controller which requires either a currently running Active Directory or you could create a new AD. W2K servers can be used as other roles on a NT4 domain. ie, member server, file&print, Web, Database, Exchange, etc. Sorry, you either need another copy of NT4 server or upgrade your infrastructure to AD.

Hope this helps,

Z

 

[i601254]

Set up the Win2k server initially in mixed mode. Use the migration tool to move all user accounts over from the NT 4.0 PDC. Once you've done that demote the PDC to member server using UPromote (you can find it on the web).

 

[jtb]

Actually, "in the future", you may want to consider following Microsoft's advice on the subject...

My Advice may not be as valuable; but it's based on my "one man show" (no Sugar Daddy/Sugar Momma clients) approach to IT...

In order of my preference:

Scenario 1: hopefully, you have more than the NT4 PDC, ie, at least 1 BDC. If so, upgrade (yes, I know how painful) the BDC to W2K. Promote the W2K BDC to PDC. Add the new server as a DC. Takeover PDC Operations Master role.

Scenario 2: if not, make a full backup, format the drives as FAT (Not Fat32, not W2K NTFS) and install nt4 on the new server as a BDC. Upgrade the BDC to W2K. Promote the W2K BDC to PDC.

Scenario 3: Aelita or similarly expensive migration tools

Any of 'em will take half a day on "normal" hardware... a bit longer if the stuff is really old...

YMMV, feel free to kick me if I'm wrong...

JTB
Senior Infrastructure Specialist
MCSE-NT4, MCP+I, MCP-W2K, CCNA, CCDA,
CTE, MCIWD, i-Net+, Network+
(MCSE-W2K in progress)

 

[rmb1905]

In my oppinion there only 2 options:

1 You keep your network a NT4 network. Then you have to install NT4 Server on the new machine. Set it up as BDC, add it to the domain, demote the PDC to BDC and promote the new BDC to PDC

2 You switch to a w2k network with active directory. In this case you can choose 2 things:

- Do the lot from scratch and set up the new server as first domaincontroller. This probably is no option because you will have to set up all policies and groups in the new domain. There might be tools to give a hand but this is just not a funny job.

- Install the new server with NT4 server as BDC. Do the Demote/promote trick with both servers (because you want the new server as fisrt domain controller in the forrest)
The new server now being PDC, upgrade to W2k domaincontroller keeping all policies users and groups.

@JTB: promoting a _W2K_ server to BDC to PDC?.... you need to explain this one further. I think you want to say something else than you have written. W2K don't have pdc or bdc, NT4 does. (but you know that i'm sure... ;-) )

 

[jtb]

you have an nt4 domain. so yes, you can have w2k bdc or pdc... in mixed mode, the 1st w2k dc has the pdc emulator role... but I was probably wrong about the order...

nt4 bdc -> nt4 pdc -> w2k dc/pdc preserves the user accounts and domain permissions... there are load more details in w2k resource kit... i just haven't done it for so long i forgot what we did...

ie, rmb1905's item 1 plus the upgrade...

JTB
Senior Infrastructure Specialist
MCSE-NT4, MCP+I, MCP-W2K, CCNA, CCDA,
CTE, MCIWD, i-Net+, Network+
(MCSE-W2K in progress)