win2000 server on nt4 network

[trustee]

Looking for information/links on promoting a win 2000 server
to be the pdc. right now i have a nt4 pdc. i have the win2000 server connected to the network.

 

[CoolClark]

I don't think there is a way to create a DC in an existing NT 4.0 Domain. What you have to do is install w2k on the PDC (BE SURE YOU HAVE A BDC OFFLINE) and then DCPROMO the server to create the first w2k DC of your network. Hope this helps.

 

[greg013]

You either have to update the PDC, or create a new network, and trust relationships between the two.

The best way to update is to have a fully replicated BDC, and take it off line. Then, upgrade the PDC to Win2k. If you have any problems, remove the PDC, reconnect the BDC, and promote it to PDC.

Good luck.

 

[trustee]

well the win 2000 server is a brand new server, the old nt4 pdc is not worth putting win 2000 on..

 

[greg013]

Then, it sounds like you'll be creating a brand new domain for W2k, and creating a trust relationship to the NT4 domain.

 

[trustee]

well i dont really want to create 2 domains . this is a small network, I have 2 bdc's but theres really not much going on. i only have like 50 users connecting, can i drop the bdc's from the domain, pull the pdc out of the picture. bring the win2k online then have the old bdcs join the win2ks domain? one of the bdc's is my exchange server .

 

[greg013]

It sounds like you need to go the upgrade path, in order to maintain your applications and data. First, upgrade the PDC to Win2k. Then, you can upgrade the remaining BDCs (or not, as you choose). When you upgrade the PDC, you're creating Win2k domain in mixed mode, and maintaining all data and permissions.

Win2k does not have PDC/BDC. All domain controllers are created equally. Once you've upgraded the PDC, join the new Win2k machine to this domain. Then, you can remove the original PDC, if you so desire.

 

[AlexIT]

If you don't want to mess with the existing server, install NT4.0 onto the NEW server, making it a BDC for your network. Now upgrade the NEW server to PDC, automatically demoting the old one to BDC. Take the old server offline (for safety) and then upgrade the new server from NT4.0 PDC to Win2K and you will have this set up in mixed-mode. Now reconnect the old server and you just have an extra BDC...

Alex

 

[mcconmw]

In my opinion, it would be easier to load to NT 4.0 on the new server and make it a BDC. Then demote the old PDC and promote the new server to PDC. From there you follow the normal upgrade path.

As far as all DCs being created equal, that is not entirely true. You still have operation masters that functionally force you into a PDC/BDC situation. This is barely noticeable if at all in a small environment, but it becomes painfully obvious in an enterprise environment. Particularly, when you start dealing with replication.