2003 domain & 2012 domain in same subnet?

[telecomguy9]

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?

[Guest LilBambi]

I remember reading them! Very helpful Temmu.

[V.T. Eric Layton]

wonder what happened to the original poster, telecomguy9?

 

He went to work for a cable company and became cableguy9.

[V.T. Eric Layton]

Oh, wow! I apologize to telecomguy9 and you Temmu. I didn't realize this was a current thread. I thought it was just an old thread you were reviving as you sometimes have been known to do.

 

So... nevermind.

[crp]

thanks, lilbambi for liking my notes

 

here's my advice on adding a server 2008 r2 dc to a server 2003 domain

http://forums.scotsn...l=+2003 +domain

How about getting NT and 2008r2 to co-exist and trust each other?

[telecomguy9]

Hi all. I'm still here. Sorry for the delayed response. I appreciate the thoughts, ideas, and knowledge you've shared.

 

We're sticking with just creating a new 2012 AD domain running side by side, but not interacting with, the existing 2003 SBS domain. He only has 10 users and 10 mailboxes so it's not a huge over haul by any means. I don't see the need to migrate to 2008 R2 and Exchange 2010 in order to move to 2012 and Exchange 2013. That's just too much work for such a tiny network setup.

[telecomguy9]

Thanks Temmu. We're planning on exporting the contents of all mailboxes, individually, to PST files from each user's Outlook client itself. I know it'll take longer than using exmerge, perhaps, but it should be cleaner from what I've heard.

 

Regarding unjoining the PC's from the SBS domain and joining them to the new domain, thanks for the idea about adding the PC's to AD beforehand. Also, regarding the fact that doing this will create new accounts on the PC's and their data and other such things local to the PC will be in their old user account folders, I was thinking of using something like this - http://iwrconsultancy.co.uk/reprofiler - to help out with that.

 

You're correct, it's gonna be an interesting few days for sure!