telecomguy9 Posted November 19, 2013 Share Posted November 19, 2013 I have an associate who has a SBS 2003 server / network running Exchange 2003. He's purchased a new HP server with Windows Server 2012 (Standard). He was intending to use this to completely replace his SBS box. Because of an issue with one application running on his SBS box he needs to keep it running for around a year before it can be decommissioned. The 2012 server has already been completely setup with Exchange Server 2013 and as an Active Directory / DNS server for his external domain (company.com). His SBS box is currently setup for all of this, too, but with his internal domain (company.local). I've come to the conclusion that we're going to setup split DNS so he can use both boxes now and take advantage of the new hardware, new OS, and new version of Exchange. What I'm wondering is if it's best practice to just demote/remove Active Directory / DNS from the new box, leaving Exchange 2013 on there, then joining it to his existing 2003 domain... - or - should we blow away the new box and start over from scratch? I'm mostly concerned about the Exchange 2013 installation and if demoting/removing all of the Active Directory and DNS stuff and then joining it to a completely different domain will completely throw it off and break it. Thoughts? Quote Link to comment Share on other sites More sharing options...
telecomguy9 Posted November 20, 2013 Author Share Posted November 20, 2013 There are no PC's currently joined to the 2012 domain. I think I'll rebuild the 2012 box entirely, join it to the 2003 domain, and then install Exchange 2013 as you suggest. There will be no migration from Exchange 2003 to 2013. There are 7 mailboxes to take care of so my plan was to backup those mailboxes to PST files and leave it at that. No biggie. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.