Domain Controller in Unusable State
Posted on 2008-10-21
About 2 months ago we utitlzed VMware to performa P2V of one of our Domain Controllers. Last week we were trying to make some Group Policy changes and we noticed lots of errors on our DC's. We have Mission Critical support on the Dell servers that are running ESX which also allows us to obtain support on all applications running on these servers. We called them to get assistance resolving some of these errors and they were able to get one of the replication errors cleared up. There are still numerous errors though and the technician told us that it is never good to perform a P2V on a DC, contrary to what our consultants said. He said it would be simpler to correct these issues by doing the following:
1. Transfer the FSMO roles off of the DC with issues to our other DC.
2. Demote the DC with issues and then disjoin it from the Domain.
3. Bring up a new virtual server, promote it to a DC, and the transfer the FSMO roles back.
After looking into this, I noticed there are some additional factors that are coming into play. I thought before spending the time to open a support call with Microsoft, I would reach out to the EE community first for guidance which might save me a lot of phone time and money. Below are my concerns:
1. The DC that is having problems is only performing the FSMO roles of "Schema Owner" and "Domain Role Owner". We only have 1 other DC in our environment. Is there an issue have all FSMO roles on the 1 DC for a short period of time? What other issues might I experience moving the FSMO roles over to the good DC?
2. The DC that is having issues is also the Global Catalog server? What exactly does this mean and what is the process of making the other DC the global catalog server?
3. The DC that is having problems also serves as our secondary DNS server. What is the proces for shutting down the DNS function on it properly and then making the new virtual server the secondary DNS server?
4. Once we have all the roles and functions moved off the server with issue, what is the proper procedure to demote it and clean it up from our Domain?
5. After bring the new virtual server up, what are the tricks to migrating all the roles the old one was previously taking to this new server?
6. We would like to give the new virtual server DC the same IP Addresses as the old DC because all of our servers have it hard-coded as their secondary DNS server. Will we experience any issues giving the new DC the same IP as the old one? Does it need to have the same name as the old one or can it have a different name?
I know this question should probably be worth 1,000,000 points but I will greatly appreciate any feedback I get.
John David Lambert