I inherited an interesting domain controller challenge.
When I came to this Job there were two windows 2003 AD domain Controllers in the domain that were upgraded from two windows 2000 domain controllers. Before they were upgraded to 2003, they were load balanced as domain controllers. So now, I have two windows 2003 domain controllers running active directory with NLBS assigned to the nic properties. Why anyone would load balance two domain controllers is beyond me.
To make matters worse, I have an exchange 2003 server with active directory installed. So, the network also sees our exchange server as a domain controller, but nothing on our network has it in the DNS settings.
The operations master is always the same since it will not change when one of the servers goes down. So, esentially we have three domain controllers, of which only two are assigned as domain controllers. And of these two, only one of them function as a true domain controller even though the global catalog resides on both. Another problem is that we have a website with the same name as our domain name minus the .com. This creates a problem as well. We have Ourname.com as a website and ourname as the name of the domain when it should actually be ourname.net. There are so many things to correct I don't know where to begin. And there are so many aspects of our domain configured incorrectly that if I attempt to clean things up, there is no telling what will fail. What I would like to do is rebuild both domain controllers correctly, but they are both in production. It seems like the most logical route would be to build another server as a domain controller and migrate the Active Directory information to that server and then start collapsing the old DC 's one by one. But once again, who knows what will happen.
Anyone ever seen this kind of a catch 22 scenario in a domain setup?