Migrating domain

[drewdown]

Scneario: migrating to new separate domain. DC/DNS/DHCP x2 , 1 of each for both domains.

When moving users to new domain how do you control old vs new DNS and old vs new DHCP?

IE: IF a user is part of the new domain he should get specific DHCP server and DHCP options. No real way to control that is there other than static IP addy's until the old domain is gone?

 

[kmcferrin]

You don't want to run two DHCP servers on the same network. That will cause problems. Besides, DHCP is probably the last thing that you will want to migrate (and then only so all of your resources are members of the new domain).

As far as the DNS servers go, you can set up referrals or a stub zone (I prefer a stub zone) for the opposite DNS namespace. So the old domain gets a stub zone for the new domain's namespace that points at DNS servers in the new domain, and vice versa. If you set up your stub zones or referrals correctly then any node in either domain can resolve nodes in the other domain and you'll be set. Just keep in mind that you will likely have to use FQDNs instead of short names. If you don't want to use FQDNs then you can of course set up WINS and replicate between the two environments, but you can easily end up with duplicates in this case (i.e., SERVER1.OLDDOMAIN.COM and SERVER1.NEWDOMAIN.COM look the same to WINS).

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator

 

[58sniper]

Also, you REALLY should have more than one DC in each domain. REALLY.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[drewdown]

I have 5 in the new domain and 2 in the old. I just gave you the short version.

 

[cyberspace]

You could do it if you have the two domains in separate broadcast domains (so new and old DHCP won't clash)

You could use port based VLANs or even a new/spare switch not connected to the old one with New DC's and PC's attached, and move PC's over.

All down to the scale of the task I suspect! I suspect with 5 DCs we aren't talking about a small office so could be a real nightmare..

'When all else fails.......read the manual'

 

[drewdown]

Its a branch office so this part is small. I am just trying to figure out the best way to do this. I moving to a new domain and off MS DNS/DHCP onto a separate 3rd party DNS/DHCP appliance.

So its tricky to say the least.

 

[kmcferrin]

Yes, especially with only half of the information.

If you plan on continuing to use Active Directory (and it seems that you do) then you're going to have to work out how to use AD with non-MS DNS servers. I know that this was possible on older versions (Windows 2003 with BIND, for example) but I never bothered to keep up with it since it seemed like a major unnecessary headache.

Likewise, I know that DNS Stub Zones are supported on MS DNS servers and certain versions of BIND, but it's entirely possible that the devices that you are referring to do not support them.



________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator