I want to add a second domain controller (global catalog) Beta 10.2.0.0 /16 on a different subnet for fail over

I have domain controller Alpha (global catalog) on 10.1.0.0 /16

I want to add a second domain controller (global catalog) Beta 10.2.0.0 /16 on a different subnet for fail over  

I want all users to connect to Alpha, and only connect to Beta if Alpha is missing, or hard down.

I have switching on the network, so Alpha and ping Beta and vice versa

I have DCPROMO Beta

i'm just not sure about Sites and Services.  Do I create two sites, do I make a site link.
I need some help with this part of the setup



13yearsAsked:
Who is Participating?
 
Mike KlineCommented:
i'm just not sure about Sites and Services.  Do I create two sites, do I make a site link.
I need some help with this part of the setup


you have it right


Take a look at the steps in my comment about halfway down here

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_24109142.html

You associate 10.1.0.0 /16 with alpha and 10.2.0.0 /16 with beta

Also make beta a DNS server if you are running AD Integrated DNS.

Really in your situation I'd just put them both in the same site (just have one site), no problem having both DCs authenticating users.  

Thanks

Mike
0
 
13yearsAuthor Commented:
I'm reading, post back in a second.  

Neither Alpha or Beta is running DNS.   That is on a seperate server.  

 I guess guy I work for just wants this as a "Back up" of the AD.  In case something happens to Alpha, Beta can be used.  
0
 
Mike KlineCommented:
ok then don't worry about DNS

So if you put them in the same site the same scenario happens.  If A goes down then B will still service clients.

The benefit of putting them in the same site is that you get much faster replication using intrasite replication versus intersite replication.

Are you 13 years old?  If that is the case AWESOME!!  If you are 13 are you also on twitter...you would be the second young person I've encountered working with AD in the community over the last week. (wondering if it is the same person)

Thanks

Mike
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
13yearsAuthor Commented:
Good info.  So I create two subnets and associate 10.1 .0.0 to Alpha  and 10.2.0.0 to Beta

Under Inter-Site Transpports IP
I deleted the default site link and created a new one.  I added both servers to the list

Do I need to do anything with the prefered transport for a bridge head server?
When I go under server and select NTDS Settings, I have a Transport choice.  IP?

Is there a way to make ALL users whatever subnet always connect to Alpha, and only Beta if things are FUBAR?
0
 
13yearsAuthor Commented:
I stole it from most of the user aggreements that say "you must be exactly 13years of age" or older to post here.
0
 
13yearsAuthor Commented:
Ok, same site, and then I would not need subnets.   That make sense.

I assume there some sort of cost check that tells an AD account which DC to use.  
0
 
Mike KlineCommented:
Well still associate the subnets but just all to that one site.   You can weight the DCs if want one DC to handle more of the load

http://technet.microsoft.com/en-us/library/cc816793(WS.10).aspx

I wouldn't worry about that in your situation.
0
 
13yearsAuthor Commented:
hmm AD is replicating.   Maybe I am wayyyy over thinking this.    

Gosh darn thank you for a solid answer.  
0
 
13yearsAuthor Commented:
AewsomeO
0
 
Mike KlineCommented:
No problem, glad to help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.