Computing.Net > Forums > Windows Server 2003 > Clustering Primary Domain Controlle

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Clustering Primary Domain Controlle

Reply to Message Icon

Name: JGALT
Date: November 26, 2006 at 07:43:00 Pacific
OS: Windows Server 2003
CPU/Ram: Intel XEON/1GB
Product: DELL
Comment:

Hi Everyone.

Is there a way to create a 2-node or more cluser for the primary domain controller. This is so I can have a backup PDC when the primary PDC node goes down....so my users would not feel the loss of 1 PDC cluster node...since the other one take over.....

JGALT



Sponsored Link
Ads by Google

Response Number 1
Name: heropsycho2177
Date: November 26, 2006 at 08:58:06 Pacific
Reply:

In Active Directory, there is a PDC emulator FSMO role holder, but there's no PDC in the sense there was in NT4. The immediate impact of the PDC emulator going down is loss of backward compatibility with NT4 legacy apps and clients.

Therefore, you do not need to cluster domain controllers in Active Directory. If you need to ensure you don't want to lose the compatibility mentioned above, you can create NT4 BDC's.

For high availability for Active Directory, have multiple DC's with multiple Global Catologs, along with multiple DNS servers.

"How many squirrels had to die to make you look fly?!"


0

Response Number 2
Name: heropsycho2177
Date: November 26, 2006 at 08:59:21 Pacific
Reply:

P.S. Who is John Galt?

"How many squirrels had to die to make you look fly?!"


0

Response Number 3
Name: bilbus
Date: November 26, 2006 at 18:44:33 Pacific
Reply:

clustering does not work that way.

AD is a cluster, install 2 AD controlers, add each of them to the clients ip settings and your good.


0

Response Number 4
Name: heropsycho2177
Date: November 26, 2006 at 23:18:08 Pacific
Reply:

"install 2 AD controlers, add each of them to the clients ip settings and your good."

It's not that simple. For authentication to AD to take place, clients must be able to query a DNS server they are configured to use to find the resource records for domain controllers for the domain along with global catalog servers.

As I stated earlier, you must have multiple DNS servers for high availability. Installing two domain controllers doesn't cover this because, by default, the second DC would not be a DNS server. Also, incidentally, you don't configure clients within their IP settings to use domain controllers; you configure them to use DNS servers, which can and often are the domain controllers in a domain. Still, this is for DNS services, NOT active directory services. The client subsequently queries DNS for the domain controllers and global catalog servers for its domain/site. DNS servers do not have to be on domain controllers!

You must have multiple Global Catalogs for high availability. By default, only the first DC would be a GC, while the second DC installed would not be a GC by default, so again, simply installing two domain controllers wouldn't provide high availability as you are stating.

Please help survivors of Hurricane Katrina!

www.redcross.org


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More


Hidden share in Win 2003 ... Logon Script - Group Poli...



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Clustering Primary Domain Controlle

Primary Domain Controller (PDC) www.computing.net/answers/windows-2003/primary-domain-controller-pdc/6142.html

Promote Domain controller www.computing.net/answers/windows-2003/promote-domain-controller/6218.html

Backup Domain Controller www.computing.net/answers/windows-2003/backup-domain-controller/6778.html