[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 840
  • Last Modified:

SBS 2003 to Server 2008r2 and changing domain name

Long time reader, second time asking a question.  Any tips or advice on this upcoming project is much appreciated.

I have an old SBS 2003 w/Exchange 2003 server that needs to be replaced.  We have also recently changed the firm name so during this transition I'd like to change the domain name.  I have about 28 users all on new Win7 machines.  

In anticipation of server 2012, and having to move away from the SBS environment, i'm upgrading to 2008r2 Standard w/SA and i'll wait for SP1 to be ready before thinking of putting that into production.  

I'm also upgrading from Exch 2003 to 2010, again with SA and down the road will upgrade to Exch 15 when the time is right.  

I do not need to worry about RWW or the SQL on the SBS box, as i have a second 2003 standard server with SQL 2005 running apps that will stay in place for now.

The new Standard 2008r2 server will be my only domain controller, host AD & Exchange and maybe some printer sharing.  The server will be installed as VM using VMware.

I've read some articles on moving from SBS 2003 to 2008 Standard, but nothing involving a domain name change.  

Any tips or advice and or great links and articles to follow up on is much appreciated.  FYI, i've been in the IT field for several years, but this will be my first migration of both SBS and Exchange.
2 Solutions
Cliff GaliherCommented:
You simply won't be able to do what you want. Renaming a domain out from under exchange will break a lot of things.

You do have options. You can build up a temp DC and temp exchange server, decommission SBS, then stand up your new final DC with the new AD domain and establish a domain trust to move accounts over  (SBS does not allow or support trusts which is why it must be retired before doing this,)

Or you can build up your new network and jump through a lot of ADMT and exchange hoops to export and import the data.

Regardless, all workstations and member servers will also need to be touched.

I'd look into SBSmigration.com and get a support kit. Talk to them ahead of time because your plan will be an edge case. I know they'll support such a migration, but it isn't one of their standard kits so you'll want to let them k ow what you want and let them assist you on building a plan tailored to your needs. That'd be my recommendation.

Rob WilliamsCommented:
The only documentation for doing a domain name change during the migration that I am aware of is by buying a migration kit, specifically for your scenario, from http://www.swingmigration.com
They provide customized instructions, tools, and 90 days support for the migration for $395.
LB2015Author Commented:
Thanks for the quick feedback.  I was already assuming it would be a PITA, but just wanted some reassurance that I was right.  Maybe i can talk the partners out of changing the local domain.

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now