Avatar of Nativtexan
Nativtexan
 asked on

AD Sites and Services issue when creating new site

We have a 2003 domain and currently everything is in the Default-First-Site-Name site.
This includes the local domain controllers as well as the ones located miles away connected by WAN. The default first site contains not only my DC's but other child domain DC's as well. Due to bandwidth it is time to start breaking things up. At the moment there are no subnets defined and everything works. I attempted to create a site first for a remote location (created the site, the subnet and moved that locations DC into it) and right after I get this message on my local DC's- None of the IP addresses (x.x.x.x) of this Domain Controller map to the configured site 'Default-First-Site-Name' It seemed once I defined a subnet for the remote site, the servers in the default-first-site lost their minds. I moved the DC back to Default first site, deleted the remote site and subnet I had created and everything went back to normal. If I associate a subnet for a new site, do i then have to create a subnet for everything still in default first site? I thought that by creating a unique site and associating a subnet for it that it would only affect clients in that subnet and make them use that local DC. I have read many "how to's" to do this and it seemed straight forward but I was not expecting this to happen.
Active DirectoryWindows Server 2003

Avatar of undefined
Last Comment
Nativtexan

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Adam Brown

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Mike Kline

I believe that is only a warning in the event logs not an error (correct me if I'm wrong there)

If you want it to go away then define the subnets for both sites.   You will also need to create a site link between the two sites.

If you want it is also safe to rename the default first site (something like HQ....more descriptive)

Thanks

Mike
Nativtexan

ASKER
I cannot assign a single subnet to the default-first-site-name site as there are currently 17 DC's in there and that covers over 12 different subnets (due to WAN) so if I created a subnet for the ones in my location it would apply to the ones that are in a different subnet so things would still "go batty" wouldn't they?
SOLUTION
Adam Brown

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
arifkayaca

Check, your Domain Function Level, it must be set to Server 2003 Mode.

In New Site you must create subnet,because this subnet determine an identify that used by Active Directory Replication. (so this is uses by DCs)
Your help has saved me hundreds of hours of internet surfing.
fblack61
Nativtexan

ASKER
 Please review my steps below, I do not want any interruption or things "going batty" during this reorganization. Sorry if I am oversimplifying but I want to ensure I have the steps correctly.
1) First create all subnets needed and assign them to Default-First-Site-Name (where all DC's currently reside)
2) Create a site for a remote area
3) Assign an already created subnet to it. Subnet would apply to both sites at the moment.
4) Move the DC that should service that remote site from default first name site to the newly created site.
5) Remove subnet association from default first site and leave just on new site. Clients in new site will now go only to DC I just moved in there.
6) Repeat above steps for each needed site

  Now a question I have is- When I start creating all my subnets, it's gonna take a few minutes to do all of them so won't things start "going batty" untl they are all in place?
Mike Kline

No things won't go batty, but you can also do it after hours to ease your mind and to make sure no users are on the network.

You will also need to create a site link between the current site and the new remote site.

Thanks


Mike
Nativtexan

ASKER
 We are 24/7 shop and network is always busy, hence the precautions. I thought a site link is just needed to better streamline replication traffic, which we will do but if we can simply get folks to authenticate against their local DC versus one across town that would help the bandwidth right there. Won't all sites use the same initial link until you add more to better refine the routes to take and wish to modify replication shcedules?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Nativtexan

ASKER
So are my steps above accurate?