Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2009-04-06
6
Medium Priority
?
582 Views
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.
0
Comment
Question by:WDecatur
  • 3
  • 3
6 Comments
 
LVL 65

Expert Comment

by:Mestha
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.

Simon.
0
 

Author Comment

by:WDecatur
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?
0
 
LVL 65

Expert Comment

by:Mestha
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.

Simon.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 

Author Comment

by:WDecatur
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?
0
 
LVL 65

Accepted Solution

by:
Mestha earned 2000 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.

Simon.
0
 

Author Closing Comment

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

Featured Post

Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

Question has a verified solution.

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

This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

916 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