finance_teacher
asked on
2nd domain inside existing domain -- Windows 2012 ?
I currently have all of my devices on the 192.168.50.x network, including my current "company.root.tld" DOMAIN on 192.168.50.10
Can I create a new "newCompany.newRoot.tld" DOMAIN on a 2nd Windows 2012 HyperV using the available 192.168.50.20, with DHCP disabled and slowly move the 10 PCs I have over to the new domain one-at-a-time, with the machines still getting DHCP IPs from the old 192.168.50.10 until I have everyone moved over, then enable DHCP on 192.168.50.20 ?
If not, what do you recommend since I just want to get everyone to a BRAND-NEW domain, recreating AD Groups and individual FileServer folder group permissions ?
Can I create a new "newCompany.newRoot.tld" DOMAIN on a 2nd Windows 2012 HyperV using the available 192.168.50.20, with DHCP disabled and slowly move the 10 PCs I have over to the new domain one-at-a-time, with the machines still getting DHCP IPs from the old 192.168.50.10 until I have everyone moved over, then enable DHCP on 192.168.50.20 ?
If not, what do you recommend since I just want to get everyone to a BRAND-NEW domain, recreating AD Groups and individual FileServer folder group permissions ?
ASKER
I am almost 100% sure I did this before, just making all the machines on the "newCompany.newRoot.tld" have a STATIC "DNS" server that was the "newCompany.newRoot.tld" server, still allowing all machines on both domains to get DHCP issued from the old "company.root.tld" DHCP server until I sunset it
Could that be possible ?
Could that be possible ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Which matters because, no, you cannot do what you want the way you describe. Clients need to be able to find a domain controller to work on a domain. If the DHCP server has data out DNS entries for the old domain, new machines getting addresses via DHCP won't work. If you configure DHCP to give out new DC addresses for DNS, machines still OK the old domain and on DHCP won't work.
And you can't have two different DHCP settings for old and new. At least not easily.
You can manually configure IP settings and not use DHCP during the transition. Or you can split your network so they aren't on the same broadcast domain (as in layer 2 OSI model terms, not to be confused with active directory domains) as separate LANs or VLANs. But regardless it'll be a different and not seamless approach.