Discussion Locked

BDC promoted to PDC reverts back to BDC

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We recently installed new server hardware. The new hardware was introduced to the Domain as a BDC then all the data including an Exchange DB was migrated to the new server. The PDC was taken offline and the BDC promoted to a PDC (probably the 1st mistake). The new computer's name was then changed to the old PDC name so client drive mappings and the Exchange DB site would be correct. The new server (promoted to PDC) reverts back to a BDC about 1/2 hour after a reboot (the first BDC name is removed after the reboot. When the Server Manager is opened the message "Cannot find the Primary DC for DOMAIN. You may adminsiter this domain, but certain domain-wide operations will be disabled."
Is there an easy way to fix this or should we introduce another BDC and then straigthen out the naming and relationships?

11 replies

by wbuching

First it seems that the original PDC still thinks that it is. First I would change the new servers' name back to its original name. I have seen problems with names before. Second I would then bring both servers online and if they both come up as a PDC one will lose and it's netlogon service will be stopped. At this point through server manager you can choose which server will be the PDC. If the old server comes up as the PDC and the new one is the BDC, try the promotion again. I think you just need to undo some of your changes and try again.

by 93961

First of all, all the domain controllers (PDC & all BDCs) should be online while promoting any BDC to a PDC. This way the old PDC will be automatically demoted to BDC. Then you should rename the servers. First rename the old PDC (now BDC) tp any other non-existing name in your network then rename the new PDC to the name of the old PDC. You can now rename the old PDC to any name if you want.

by bill cassada

I was doing some Knowledge Base research today and came across article Q250263
which sounds like it may be your problem...not sure if it applies, but you can take a look and see.

by shepherr

The second answer sounds like the closest, with one exception. Between each change, you need to use the servermanager for domains to synch the domains. Otherwise, the PDC may have changes which the BDCs won't know about when you make the second and third changes. One thing to note, It is very important to keep the original PDC online during this whole thing because all the BDCs know that it is the PDC until you demote it (as the first step, then promote the BDC you want as PDC (this is the only step I'd take without synching betweem the previous and current step)). Another note to know, if you are running IP, also change the IP addresses of the servers. When you are finished, the second server should be in the exact position (networkwise) of the original PDC. Good luck.

by 93961

The answer is in the discussion itself. Please read all the posts of the discussion, specifically the 4th post from the top.

This discussion is closed to new replies.