New domain controller different subnet
Hi,
I will be building a new 2012 R2 domain controller and joining it to the current domain which has a 2003 domain controller. The new server will have a new subnet of say 10.10.10.0/24 with VLAN 10. The existing subnet is 192.168.10.0/24 no VLANs.
- What is the best method to join this DC to the domain and ensure they are able to replicate correctly
- I will need to make the 2012 R2 server the primary DC and demote the 2003 DC once replicated
- I will need to update how DHCP will work with multiple subnets and ensure that the existing and new can run side-by-side until i stop the existing subnet and allow the new subnet to be pushed out to workstations
Someone mentioned that i need to do some configuration on sites and services to get it to work correctly?
Thanks.
I will be building a new 2012 R2 domain controller and joining it to the current domain which has a 2003 domain controller. The new server will have a new subnet of say 10.10.10.0/24 with VLAN 10. The existing subnet is 192.168.10.0/24 no VLANs.
- What is the best method to join this DC to the domain and ensure they are able to replicate correctly
- I will need to make the 2012 R2 server the primary DC and demote the 2003 DC once replicated
- I will need to update how DHCP will work with multiple subnets and ensure that the existing and new can run side-by-side until i stop the existing subnet and allow the new subnet to be pushed out to workstations
Someone mentioned that i need to do some configuration on sites and services to get it to work correctly?
Thanks.
Cliff Galiher
The onlymrhing you need to do is make sure the designers can communicate with each other and that traafficia not blocked. Any router and most layer-3 switches can route between subnets.
Yes, You need to create a new subnet under sites and services for new subnet 10.10.10.0/24. Once new server is installed and promoted as an Domain controller, you can do the migration from 2003 to 2012 R2.
https://blogs.technet.microsoft.com/canitpro/2014/04/01/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012-r2/
https://blogs.technet.microsoft.com/canitpro/2014/04/01/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012-r2/
A new site really isn't necessary. It is recommended when communicating over a WAN so clients find the closest domain controller and don't vuen WAN traffic m. But two subnets on high speed local link's wouldn't have that issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Reread the Ops post. He is migrating subnets. In that scenario there wouldn't be site linked GPOs, DFS for file servers, preference filtering, or anything like that. No errors would be logged.
This isn't even abnormal. Campus area networks do this *all the time.* You meed sites when you actually want to manage which DCs are considered "closest" to an endpoint, or similar functionality. That isn't the case here. Creating a site is superfluous.
This isn't even abnormal. Campus area networks do this *all the time.* You meed sites when you actually want to manage which DCs are considered "closest" to an endpoint, or similar functionality. That isn't the case here. Creating a site is superfluous.
Missing site/subnet is required, best practice and flagged in an AD Rap, so is a single Default site.
(I am referring to a strictly BP, such as using LOG to calculate site-link costs but agree to fast-link statement from a functional perspective)
(I am referring to a strictly BP, such as using LOG to calculate site-link costs but agree to fast-link statement from a functional perspective)
I don't recall anyone saying that the default site is missing. I just said creating a new one is not required in the given scenario. Neither from a best practices nor from a functional scenario.
Read my comment... A single site is flagged by AD Rap
I read it. But ADRAP was never meant to be a standalone BPA (server manager has one of those that doesn't flag a single site last I checked.) It was a PSS tool and meant to be customized for the environment by the TAM. But...not really worth arguing about.
There is a massive difference between server manager BPA and AD Rap as a service (not AD Rap) and the fact that server manager BPA doesn't flag it is irrelevant.
I am not saying create sites for every DC, I am saying if you have a reason for a second go for it. Subnets are always required
Export from AD Rap as a service
I am not saying create sites for every DC, I am saying if you have a reason for a second go for it. Subnets are always required
Export from AD Rap as a service
ASKER
Thanks everyone.
What i would like to do is run them side by side for a few days before removing the 2003 R2 DC. Configuring the new DC server during business hours shouldn't cause any issues should it? Event with a different subnet address
What i would like to do is run them side by side for a few days before removing the 2003 R2 DC. Configuring the new DC server during business hours shouldn't cause any issues should it? Event with a different subnet address
Any feedback?