Discussion Locked

w2k dns, gcs and dc

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

we have a testlab runing two w2k servers as domain controller for domain name "testdom".
Initially we setup active directory on one of the machine using dcpromo. Everythign went well. Then, we configure the other one as member server and later useddcprome.exe to promote it to secondary dc.
Q. If the dc1 goes down, why can't we run everything smoothly on dc2? for example, group policy gives us error message:
"Domain controller not found for testdom.net.
The domain controller for Group Policy Operations is not available. You many cancel this operation for this sesison or retry using one of the following domain controller choise.

The one with the Operations Master token for the PDC emulator.
The one used by the Active Directory Snap-ins.
Use any available Domain Controller.

What is going on?

1 reply

by rkelly

The error message you are getting is expected in your scenario. When you use the Group Policy snap-in it always focuses on the PDC Emulator in the domain, in your case this will be the first domain controller that you brought on line. The idea of always focussing in one location is the stop replication conflicts in GPOs due to multi master replication.

When you want to modify a GPO when your PDC Emulator is offline just choose the other domain controller and everything will be OK. You could always try making your second DC the PDC emulator for your domain! Use AD Users and Computers to do this.

This discussion is closed to new replies.