Link to home
Start Free TrialLog in
Avatar of Garry Shape
Garry ShapeFlag for United States of America

asked on

AD Sites and Services - DEFAULTIPSITELINK?

I'm trying to sort out my domain controllers in Sits and Services. I'd discovered recently that a subnet has been tied to our HQ site when the subnet network is actually at an offiste location where those servers/VM's are as well. So I don't think that has been optimal over time.

My concern/question is, should the Domain Controllers I move from the HQ site to the other site cause a problem, and changing the changing the site association for the subnet to that proper site, affect logging in?

I created a "Site Link" between these two sites. But there is also a "DEFAULTIPSITELINK" that contains ALL OF the sites, which I'm not sure is needed, optimal, or can be deleted.

This would be mostly server 2008 R2 environment, with a couple 2012 R2 DC's.
SOLUTION
Avatar of Sushil Sonawane
Sushil Sonawane
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Garry Shape

ASKER

There is one site that is remote and contains domain controllers in it. Problem is subnet for that actual site is tied to our headquarter site, and so that remote site's always being connected to via logins, ad, exchange, etc.
Do you mean two or more sites? or more than two?
can you upload your generic diagram of your site and service.

If your problem is subnet then map your subnet to remote site or your HQ site also you can map because single token can authenticate your services like ad exchange.
If you read my earlier comment, it clearly says that "More than TWO sites"

If you have only TWO sites, you don't have to create new site link and defaultitsitelink suffice your purpose
Ok well I do still want to make sure that DC's in both sites are not being defaulted to for users logging in at one site (don't want users at Site A logging in and their LogonServer being a DC from Site B). Nor do want Exchange using DC's from Site B.
As long as I have the DC's in Site B moved actually placed in the Servers folder of that Site B (in AD Sites & Services), and the Subnet for those DC's is associated to Site B, I should be good?
Have you looked at the HowTo that i have created? I would highly recommend that you reference that to get a full understanding on how to configure your sites correctly.

Will.
If your site to subnet mapping is correct and if subnet CIDR notation is correct, you should not face any issues
Offcource DC should be present in that site.
Thanks very much, things seem to be working fine now. No replication errors.
I've been testing with "nltest /dsgetsite" on servers to verify site, and echo %logonserver%on clients to verify they're logging on via local site DC's.