|
|
 |
|
|
Pages: 1
Windows 2000 domain controllers
(Click here to view the original thread with full colors/images)
Posted by: llyr
I seem to have forgotten where one chooses primary and secondary domain controlers in a "Native" install of Windows 2000 servers.
Would someone please help me on this?
I am removing our Primary domain controler from the network, and have already migrated the AD roles from it to the secondary domain controler (I know it is the secondary DC as I have it listed in the "bible", I just can't remember for the life of me where to change them, and I know I have seen it, and even performed the promotion before.
Any help is apriciated, all net serches and reffrences in MS help have proved fruitless.
Sincerely
Allyn Llyr
Posted by: slugo3
I dont think you need to make any changes. The second DC has a full copy of AD, you can just go ahead and remove the first one because really there is no PDC like NT 4.
Posted by: llyr
I am replacing the Primary though with a secondary, and I am worried about fail over in the long term.
You are right about their being no immediate impact though.
Sincerely
Allyn
Posted by: slugo3
yeah just put in another DC and you have the failover
Posted by: EvilCable
There is not a primary domain per se, however, you will need to remove references in WINS (if you have it running), TCP and active directory to the domain controller that you are removing. If you don't your going to have some wierd issues floating about. Since you are in a shared domain structure (win2k ldap native mode) you don't need (and won't be able to) set any domain controller as the primary.
I do reccomend, depending on how big your domain is, to run a 2nd domain controller, just to house, at the very least, the active directory stuff. Possiably having DNS and WINS (if you use it) on that machine also as secondary, you never know when your gonna need it.
Posted by: slugo3
 Quote:
Originally posted by EvilCable
There is not a primary domain per se, however, you will need to remove references in WINS (if you have it running), TCP and active directory to the domain controller that you are removing. If you don't your going to have some wierd issues floating about.
|
I've experienced some of these issuse, usually nothing serious that will criple your domain. things like replication error messages and the removed server showing up in DC lists in various places.
went to a 2k3 training and learned there is a new tool in 2003 that will go out and remove the wins enties and all the other stuff supposedly.
dcpromo /force or /forceremove, dcpromo /? should show it on a 2k3 server
|
|
|
|
|
