2013-08-23, 10:51 #1
- Join Date
- Dec 2001
- Atlanta, Georgia, USA
- Thanked 0 Times in 0 Posts
2003 domain & 2012 domain in same subnet?
Hi all. I have a friend who has an old SBS 2003 server that runs Exchange 2003. He's looking at replacing that system with a new server running Server 2012 Standard and Exchange 2013. I know there's no migration path from 2003 to 2013, but what I'm wondering is if there'd be an issue having Exchange 2013 up and running and functional in the current environment with SBS 2003?
His domain is also a .local internally and because of the issue beginning in 2015 with SSL certs and internal domain names I'm going to use this new server as an opportunity to completely replace his existing internal domain, Active Directory, etc. So adding this new 2012 server to the existing domain, making it a DC w/DNS, etc. to more easily migrate over to using the new server isn't an option.
Knowing all of this I'm wondering something. What would be the implications if I connected the new server to network, gave it a static IP, created a new domain in the same IP subnet as the existing domain, installed Exchange 2013, etc.? I believe I should do this on a separate subnet but am just wondering if it would really cause any issues? All the PC's are members of domain.local and I'd be creating domain.com.
What do you all think? What issues do you see that would/could occur in this scenario?
Subscribe to our Windows Secrets Newsletter - It's Free!
Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!
+ Get this BONUS — free!
Get the most of Excel! Learn about new features, basics of creating a new spreadsheet and using the infamous Ribbon in the first chapter of Excel 2013: The Missing Manual - Subscribe and download Chapter 1 for free!
2013-08-25, 01:47 #2
- Join Date
- Dec 2009
- Thanked 225 Times in 213 Posts
The IP subnet is not relevant to the domain, except that Sites and Services lists known IP ranges so login requests can be directed to a relevant DC and route traffic as required. I suspect you only have one server so only serving login requests is an issue. Login requests are domain specific so I don't see a problem.
Personally I'd add the new domain as a trusted domain, then you can migrate users and email easily (relatively easily, no inter domain transfer is easy).
If you do encounter problems with the servers on a the same subnet, simple router's are cheap.
p.s. This isn't really an issue so you don't need to rename the domain, except that you are introducing a new server without an upgrade path - good old MS. See this discussion and references.