Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Secondary DC management

Status
Not open for further replies.

irevuelto

IS-IT--Management
Dec 19, 2006
2
ES
I have a main domain controller for my network. I've created a secondary domain controller. I just want to have this secondary DC in case of failure of the main one.

Last time I added a new computer to the domain, I realised it appeared only in the secondary domain manager instead of in the main one.

As I want to manage the whole domain from the main domain controller, this is an annoying situation.
The secondary DC should only has the same information than the main DC. I don't want it to work as a main DC too.

How can I avoid it?

Thank you very much
 
There is a slight delay between when things show up one domain controller vs. another due to replication. If you wait long enough, the data should be the same on each DC.

There really is no "main" DC, as each has write access to AD. The whole purpose to having more than one DC is redundancy, and load balancing. It's by design.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
If you added a second DC it should have the same data as DC1. You can connect to DC to make changes ADD DELETE accounts etc. I assume DC1 holds your FSMO roles? I guess that can be considered your "main DC".

sniper is right redundancy and load balancing is why you have a second DC.

If things are not syncing up properly. run dcdiag Is your DC active directory intergrated?
 
I've followed your advices and I've checked my DC configuration.

My Dc is active directory integrated. Of course, it holds all the FSMO roles. So it works as PDC.

The problem is that "the slight delay" sometimes is a few hours.

I don't know if it's a sync problem or if it's the normal operation...

Windows can't recognize the command "dcdiag". I don't know if it can solve this issue.

Thank you very much for your collaboration
 
No such thing as a PDC. If you run dcdiag and netdiag, those might point to the problems with slow replication. Do a search on the DC for the dcdiag command and see if it's just not in your path.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
Dont forget to make your 2nd DC an additional Global Catalog server, you will need/want that in the event the 1st DC goes down.

RoadKi11
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top