Windows Forum

Ask something
Discussion Locked

Keep NT Server Add W2KAdv Server As DC

0 helpful
9 replies

by lindawilbourne

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I now run NT4 SP5 on one 3 1/2 year old server (the only one in the 14-workstation network at the small non-profit organization where I work) where Exchange 5.5 also resides and runs without any problems. I'm adding a new server to the domain and will install Win2K Advanced Server on it. Because it's running without problems, I don't want to upgrade the old NT Server now, since I know nothing about administering Exchange and don't want to have to deal with problems.(For the same reason, I haven't even installed SP6. I do back up the old NT server every night to a tape drive.) I just plan to transfer most applications and data files, except Exchange, to the new server. What problems and issues might I have when I add this new server tothe domain as an additional domain controller? I put 500 points on this question, not because I think it's hard--I'm sure it will be easy for people who really know what they're doing and have lots of experience--but because I really need a good answer from someone who has experienced this situation and can tell me how to navigate through it. Thanks!!

9 replies

by joseph moore

First off, you CANNOT add a Win2K Server as a Domain Controller on a NT4 domain. It does not work that way.
What you can do, instead, is add the Win2K Server as a MEMBER of your existing NT4 domain. That is ok. It can be a member just like your workstations. But you cannot promote it to be a Domain Controller.
NT4 PDCs and Win2K DCs cannot co-exist in the same domain!
This is a common mistake people make.
Now, you CAN have a Win2K Server Domain Controller (running Active Directory) and NT4 BDCs for the same domain. That is ok.
But, since you are not upgrading your existing NT4 PDC to Win2K, then you can't make the new Win2K Server a DC.
So, add the new Win2K Server into your existing NT domain, and don't try to promote it.
The process is very simple. Install the Win2K Server. During the install process, when you ask if you want to make it a member of a Workgroup or a Domain member, select the Domain member option, and put in the name of your NT4 domain in the box. You will geta username and password challenge to add the Win2K server to your NT4 domain, just like when you add a workstation. Type in your Administrator user name and password. Click OK, and after a few moments, it will say the Win2K machine has been added tothe XXXXX domain.
Easy!

hope this helps

by trackhappy

Hmmmmm. Rusty on the NT4 stuff now, but as I recall you can't demote a PDC, and W2K can't be a BDC. My suggestion would be to add tne new server as a NT4 BDC, then promote it to PDC, then upgrade it to Win2K. A little more work, but clean and safe. I wouldn't be concerned about upgrading the old one though. W2K upgrades over NT4 just fine on an Exchange machine ( Exch. SP 3 minimum). Get Norton Ghost and ghost the server first if you have any concerns, works a treat. Email me if you want more help. trackhappy@hotmail.com and I'll give you my work email from there.

by ronnonf

Install NT and Sp6a to the new server. Bring the box up as a BDC and promote it to PDC. This will demote the other system to a BDC.
Upgrade the system to Win 2k with AD and fret not b/c Exchange should still work.
Though I would suggest tested this before putting it into production.

by @lberto

Ok, let's keep it simple.
Are you planning to replace your old server?
choices;

.- NO: Then you don't have to make it PDC (Well on Windows 2000 Advanced Server is call DC), you can just add it to your domain and keep the old Windows NT server as PDC, it will be in a mixed network. Windows 2000 is able to work that way. Just join the domain and that's it, it will work, you'll be able to login in any of the servers.
.- YES: then you can choose any of the previous answers the other IT guys gave you already.

If I can help further please let me know.

@lberto
alberto@wirelesscuracao.com

This discussion is closed to new replies.