Should a BDC take over automatically when a PDC goes down?

I have 2 domain controllers running Windows 2003, one is set as the PDC and the other is a BDC.  The PDC went down and I expected the BDC to take over domain responsibilities automatically but it appeared not to as users could not logon.

Can someone guide me to what configuration options I should check to ensure the DCs are setup correctly?
LVL 2
prodriveitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
First, there is no such thing as a BDC and a PDC in Windows Server 2003.  

You have 5 FSMO master roles that could be put on any DC at any time (manually).  You also need a global catalog server (GC) running.  which is likely your problem - make sure the other DC is a global catalog server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Toni UranjekConsultant/TrainerCommented:
There is no BDC in Windows 2000 or Windows 2003 domain. All DC are "equal" because Active Driectory uses multi-master replication model. First DC is usually FSMO holder and GC. When First DC goes down, there are some limitations how your Active Directory works, but users should be able to log on if your DNS is correctly configured. You should use AD integrated zones to replicate DNS data between DC and configure your clients to query multiple DNS servers. In your case configure all clients to have "PDC" as preferred DNS server and "BDC" as alternate DNS server. If you have single domain in your forest, all DC should be configured as GC. If you need more information let me know...

HTH

Toni
0
NJComputerNetworksCommented:
You also need to make sure that DNS is running on both DC's...  This is needed so that your clients can "talk" to the domain properly.  If you are using DHCP, you will also want to add the DHCP server on the second DC...but don't overlap the scope range... (split them instead)
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Brian PiercePhotographerCommented:
Firstly let me repeat what had been said about PDCs and BDCs. These went out with NT4.

If you want two DCs for redundancy purposes then:-
Make sure that the second DC is configured as a Global Catalogue Server and Also has DNS and (if it is being used) DHCP installed. If DHCP is set up them you must make sure both DHCP Servers are set up with appropriate scopes and not giving duplicate addresses.

You also need to make sure that clients have the address of one DC as the Preferred DNS Server and the other as the Alternate DNS Server then they will query the second DNS Server automatically if the first one is off-line.

Once you have done this is the first server goes down then you will need to move the FSMO roles as the first DC to be created holds all of these by default. While the domain can continue to function short-term without these roles, you will need to move them for all put very temporary outages.

If you are planning a shutdown of the first DC then you should transfer the FSMO roles to the other DC before shutdown. The transfer is a clean option to move the roles.

If the first DC goes down unexpectedly should you seize the roles as this is an 'unclean' process which may result in some data loss.

see http://support.microsoft.com/kb/324801 and http://support.microsoft.com/kb/255504
0
Brian PiercePhotographerCommented:
Sorry my penultimate paragraph should have said
If the first DC goes down unexpectedly you should seize the roles as this is an 'unclean' process which may result in some data loss.
0
Toni UranjekConsultant/TrainerCommented:
To KCTS:
Schema master and RID master should not be seized if there is any chance of old FSMO coming back online in reasonable period of time. Infrastructure master and Domain Naming master don't perform any functions in single domain forest, so I wouldn't seize them. In this case only PDC emulator should be seized. You should rather wait for FDC to come back online, than seize other roles. FSMO roles have nothing to do with users having trouble to log on. Asker is probably having problems with incorrect DNS configuration.
0
prodriveitAuthor Commented:
Thanks guys you have given me lots of think about and some direction.  I'll have a look at the DNS and report back.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.