SBS 2003 migration to 'Full Product' - Same Domain

Posted on 2011-04-25
Medium Priority
Last Modified: 2012-05-11
Hi Guys,

Demazter's article goes someway to answering my questions;


We are migrating from SBS2003 SP2 to 'Full Product', this was our option from MS after the SBS-EBS migration was a spectacular failure.

SBS2003 and production servers are all in VM and we have already migrated MOSS, Exchange (2003->2007) and SQL to standalone Server2008, what we need to do now is retire/remove the SBS2003 server.

To this end I have S2008x64 build in VM to use as the new DC and also want a BDC, Q1; can we use any of the current S2008 boxes as BDC? (I believe the Exchange box is not a good idea for either role and do have several others).

Q2; Can I follow Demazter's excellent migration article (link above) and just ignore the parts appertaining to Exchange? (obviously not using the Exchange box as the DC in my case).


Bill - London
Question by:wlewis123
LVL 35

Accepted Solution

Cris Hanna earned 1000 total points
ID: 35468419
You will need to updated the schema on the SBS 2003 box first to allow for Server 2008 domain controllers

You are correct, you don't want to use the one with Exchange on it...wouldn't use one with SQL on it either.

Once you've upgraded schema on SBS 2003, and assuming there are no OLDER DC's , you would also need to raise the forest and domain levels of the SBS 2003 server to Server 2003 native.

Then add the DC role to your selected server, and replicate.
Add the DNS role to the selected server and replicate
Add the Global catalog role to the new server
Add DHCP (but don't turn on yet) to the new server
When all replication is complete...all data is removed from the SBS Server is moved, Exchange has been removed from the SBS 2003 server, if not already done, etc (you no longer need the SBS server AT ALL), transfer the FSMO roles from the SBS 2003 server to your new server, then immediately DC PROMO the SBS server out and remove it from the domain.

Author Comment

ID: 35495593
Thank You CrisHanna,

I followed Demazter's guide ignoring the obvious bits (Exchange/Sharepoint migrations), my old SBS2003 system fought tooth and nail throwing exceptions out at every step which took a full 8hrs to resolve and finally I could put it in a VM folder called 'Got the little bugger!".

My new DC/Domain need a little bit of tidying up to correct DNS/DHCP settings (DHCP is handled by a Sonicwall), but that was nothing compared to demoting the old SBS box.

Bill - London.

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Question has a verified solution.

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

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
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.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

862 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