Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Migrating SBS 2k3 to Server 2k8 and Exchange 2k7

Posted on 2009-04-06
Last Modified: 2012-05-06
Hello Experts,
I have gone through many of the current questions out there on this topic, and can't seem to find a solution that fits exactly what we're trying to do.  I think I'm on the right track, but I wanted to get a quick sanity check.

We currenty have a SBS 2k3 server running our AD, Exchange 2k3, and Sharepoint TS.  Our goal is to migrate the DC role to a 2k8 server, migrate exchange 2003 to exchange 2007 on it's own 2k8 server, and then eventually blow away the SBS server and instal sharepoint portal.  I'm not concerned with the sharepoint part as it's barely used right now and anything we currently have on there I can have someone migrate manually.  My question is related to the part about splitting off the DC role to a 2k8 server and then migrating exchange.  

So, here's the part where I need a sanity check.  Please correct me if I'm wrong.
1)  Use transition pack to move from SBS to server 2k3 domain
2)  Add 2k8 DC, replicate AD
3)  Add 2k8 x64 + Exchange 2k7, Migrate mailboxes
4)  dcpromo old SBS server

First, will doing it this way "break" exchange?

I know that I'm being quite general here, but that's the basic outline.  If I'm crazy, or if anyone has come across any issues doing it this way, or if anyone has a better solution, please let me know.
Question by:WDecatur
  • 3
  • 3
LVL 65

Expert Comment

ID: 24080353
A transition pack in this scenario is a waste. You are moving to Windows 2008 and Exchange 2007 - a transition pack would only be of use if you were going to use the same versions.

As long as you follow the guides to move from Exchange 2003 to Exchange 2007 carefully, ensuring that all settings are moved across etc (look for removing legacy server Technet articles) then Exchange will continue to work correctly. You are going to full product so you can do a standard swing migration.


Author Comment

ID: 24081016
I guess I should have been a bit more specific in my original question.  I think I can handle moving from exchange 2k3 to exchange 2k7, but I'm more concerned with what the best way to move from SBS 2k3 to a standard windows domain running on server 2k8 would be.  I figured I would probably move SBS to a standard domain, add the 2k8 server as a DC, then remove the SBS server after I had moved the mailboxes to the 2k7 server.  Per article http://support.microsoft.com/default.aspx/kb/555073, I need to purchase a transition pack to migrate from a SBS domain to a standard domain in order to keep the same domain name/settings.  Is this not the case?
LVL 65

Expert Comment

ID: 24083106
The article you have referred to is regarding a Windows 2003 domain, not a Windows 2008 domain and if I am honest it isn't a great article.
If you are intending to remove the SBS Server then a transition pack is not required.

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.


Author Comment

ID: 24083155
Ok, that being said, what is the best way to go about migrating to 2k8 from SBS 2k3?  Should I just add the 2k8 server to the domain, DC promo, migrate exchange to 2k7, and blow away the SBS box?  Will there be residual SBS-specific security left inside of AD on 2k8?
LVL 65

Accepted Solution

Mestha earned 500 total points
ID: 24086847
There is nothing SBS specific - SBS acts in the same way as the full product. The only difference is that SBS has some additional applications, the main one being that it detects if the FSMO roles have been moved to another server. That and the fact that you cannot trust another domain are the only operational restrictions on SBS. You can add additional domain controllers, Exchange servers etc as you wish.

So as I said above, do a straight migration. Build the replacement machines, you might want to start with Exchange first, migrate the data. Build the replacement DC, DCPROMO it in, make it a global catalog. Then once everything has been moved, DCPROMO the SBS Server out (which will move the FSMO roles) and then drop the machine in to a workgroup and shut it down.


Author Closing Comment

ID: 31567071
Thank you.  THAT is what I was looking for. :)

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question