<

Migrate Small Business Server 2003 to Small Business Server 2011

Published on
91,294 Points
38,794 Views
25 Endorsements
Last Modified:
Awarded
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Small Business Server 2011.

NOTE: This guide has been written using the preview version of SBS2011 therefore some of the screens may look slightly different on the final release. 

For this migration to work you will need the following software:
Windows Small Business Server 2003 (SBS 2003)
Windows Small Business Server 2011
Microsoft Baseline Configuration Analyzer which can be downloaded from:  http://www.microsoft.com/downloads/en/details.aspx?familyid=1B6E9026-F505-403E-84C3-A5DEA704EC67&displaylang=en
Steps required:
1.   Health Checks on Small Business Server 2003
2.   Configure SBS2003 for single NIC
3.   Run Migration Preparation tool on SBS2003 & Create Answerfile
4.   Administrative User Creation
5.   Setting data locations
6.   Configure the Network
7.   Configure the Internet Address
8.   Migrate Exchange Mailboxes and Settings
9.   Remove Legacy Group Policies and Logon Settings
10.  Migrate users' Shared Data
11.  Migrate Fax Data
12.  Migrate Users and Groups
13.  Uninstall Exchange 2003 from Small Business Server 2003
14.  Check Transfer of the 5 FSMO roles to SBS2011
15.  DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network


Step 1.   Health Checks on Small Business Server 2003


The absolute first thing you need to do is take a SYSTEM STATE backup of your Small Business Server as well as a full system backup.  There is little chance of the data getting lost but the SYSTEM STATE backup backs up Active Directory so that if it all goes wrong we can recover it if needed.

To do this from using your preferred backup product ensure that System Stare is selected from the selection list then run a backup.

What you then need to do on the SBS 2003 server is to make sure you have all the latest available updates.  This means you should at a minimum have:

Windows 2003 Service Pack 2 - verify this by right clicking on My Computer and select properties.  It should tell you here the Windows Service Pack
Windows Small Business Server Service Pack 1 - verify this by checking the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\ServicePackNumber you are looking for a value of 1 in the bracket.
Microsoft Exchange 2003 Service Pack 2 - verify this using the Exchange System Manager.  Navigate to first administrative > Servers.  With the Servers folder highlighted on the right hand side you will see the SBS2003 servername with the service pack version listed.

Once you have installed all of the above, run Windows Update and make sure you select the option in the blue banner bar across the top for Microsoft Update.  Microsoft Update will then allow you to update all Microsoft products installed on the server providing a more comprehensive update solution.  Keep running the check and installing all updates until there are no more available.  Further details on this process can be found in my article here: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_7/A_3236-Get-more-from-Windows-Updates.html

Check the health of your Active Directory by running DCDIAG, if there is anything reported as an error fix it before moving on.

A common problem that can cause this migration to fail is that the SBS 2003 server does not have its own IP address listed for DNS in the network properties under TCP/IP.  If this is the case, update it so that it does (do not use the loopback 127.0.0.1 address).

Step 2 - Configure SBS2003 for single NIC


Before you can migrate from SBS2003 it needs to be configured in a single NIC configuration and ISA server (if in use) needs to be removed.

To do this uninstall the ISA components from Add/Remove programmes.

You may also need an additional internet router appropriate for the type of connection you use.  This should support NAT and needs to be configured with an IP address to match the internal NIC on your server.

Once you have done this, disable the second NIC and then run the Connect to the Internet Wizard to ensure SBS2003 is configured correctly.

I would then suggest a reboot to ensure that all these changes are taken in to effect.

Step 3.   Run Migration Preparation tool on SBS2003 & Create Answerfile


As part of the Migration Preparation tool it will run the best practice analyzer to identify any issues with the current setup.  Before you run the tool you will need to download and install from Microsoft Baseline Configuration Analyzer which can be downloaded from:  http://www.microsoft.com/downloads/en/details.aspx?familyid=1B6E9026-F505-403E-84C3-A5DEA704EC67&displaylang=en

We can then run the wizard by inserting the SBS2011 DVD in to the SBS2003 server drive.  Allow it to autoplay and you should see the following screen.  If you don't have a DVD drive in the SBS2003 server then there are a few options.  Either use a USB DVD Drive, share the drive out from another workstation that does have a DVD drive, or copy the contents of the SBS2011 DVD to the SBS2003 server hard drive.  The folders you require specifically are TOOLS and SOURCES.  If you copy these 2 folders then instead of seeing the link below you will need to run the SourceTool installer from the TOOLS folder.
 sbs2003-Preparation-Tool.jpgFrom here we need to select the option for Install the Migration Preparation Tool.  The first screen we will see asks about getting and installing installation updates.  My recommendation here would be to not install updates unless you are encountering an issue that has been identified by the SBS team and you are following specific advice regarding this. (screen below)
 sbs2003-Preparation-Tool-01.jpgOnce you have made your choice, the following screen will ask you to confirm that you have an adequate backup of the SBS system.  Obviously the data needs to be backed up.  But the important thing that needs to be backed up that is often missed is the System State Backup.  This includes Active Directory and will be needed to recover with should the migration fail.  (screen below)
 sbs2003-Preparation-Tool-02.jpgOnce you check the box to say you have a backup and click next you will see the screen below.  This is preparing Exchange and Active Directory for the introduction of your new SBS2011 server.  We are looking for 4 green ticks here.
 sbs2003-Preparation-Tool-03.jpgOnce this has completed click next.  The next stage is the Migration Wizard will use the baseline analyzer tools you installed earlier to check the organisation for any misconfigurations that should cause the migration to fail (screen below)
 sbs2003-Preparation-Tool-04.jpgThis could take a few minutes but what we are hoping to see is the screen below that says we have no errors.  This means we are ready to proceed with the introduction of the new server.
 sbs2003-Preparation-Tool-05.jpgClicking Next to move on will tell us the source server has been successfully (image below) prepared and give us the option to view the migration guide.  At time of writing this article there was no migration content on the link provided.
 sbs2003-Preparation-Tool-06.jpg 
The second option is to create an answer file.  This is essential for the successful migration to SBS2011 so click this option and complete with the detail as illustrated below.  The reason I select these options is that it then asks you to confirm some information at the installation stage.  Almost like a second check before proceeding.  One of the key options is not to perform any updates.  This can be done after the migration, and with my experience from SBS2008 migrations these updates have been known to make changes which cause the migration to fail.
Answer-File-01.jpgNow we need to save the answer file using the save option.  Once done, copy it to a USB drive and place this in your new server along with the SBS2011 DVD and post up.

The first screen we see is the language and keyboard selection screen (image below)
 sbs2011-install.jpgMake the appropriate selections and click next.

We then see the screen below.  Click Install Now
 sbs2011-install-02.jpgWe are then presented with the usual License Agreement screen (below).  Put a check in the check box and click Next.  Obviously only if you agree to the licensing terms as set out by Microsoft.
 sbs2011-install-03.jpgThe following screen (below) provides any storage that has already been configured on your new hardware.  If you don't see anything here you will need to load 3rd party drivers from your vendor using the Load Driver option.  If you still don't see anything listed then you may need to configure your RAID Controller so that there is a volume, most will do this by default on first boot if you don't select to configure yourself, but some might not.
 sbs2011-install-05.jpgOnce you have made the appropriate selections click next and we will see the usual Windows 2008 R2 component configuration and file copy screen as below.
 sbs2011-install-06.jpgOnce this has finished the server will reboot and display the screen below.  As this is a migration we will be selecting Server Migration and then click next.

The screen below is the time zone and date/time selection screen.  It is absolutely essential that this matches the source server otherwise connection to the domain and promotion to a domain controller will fail.
 sbs2011-install-07.jpgVerify the time zone and date/time then click Next.
 sbs2011-install-09.jpgThe screen below asks you to verify the source server IP address, the IP address you wish to assign the new server and the gateway address.  Confirm the details and then click next.
  sbs2011-install-10.jpgThe next screen is more confirmation.  This time it is the source server name and internal domain name along with the administrative user details and the source server name.
sbs2011-install-11.jpgConfirm the details, and even retype the password just to be sure.  Then click Next.
 
We then see the update screen below.  Again, my recommendation here would be to not install udates. And then click next.
 sbs2011-install-12.jpgThe screen below is your company details, this will be used on Companyweb/Remote Web Workplace.  Fill in the form an click next.
 sbs2011-install-13.jpgWe then see the screen below which is the start of the SBS2011 component installation, this could take around 30-45 minutes and you can expect the server to reboot at least once during this phase.
 sbs2011-install-14.jpgOnce this has finished you should be presented with the SBS2011 desktop and the screen below.  This means that the installation phase of the migration has been completed.
 sbs2011-install-15.jpgIf there were any problems with the migration you would see a troubleshooting assistant informing you of what has failed and how to correct it.

Step 4.   Administrative User Creation

Now that SBS2011 has been successfully installed and you have logged in for the first time we will see SBS console.  Those of you familiar with SBS2008 will notice that not much has changed.
SBS2011-PostInstall-01.jpgAs with SBS2008 most of the tasks we need to complete need to be performed with an Administrative user other than the built in Administrator account.  This was not the case with SBS2003 and you probably do not have another Administrative user.  If this is not completed we will receive the error below when trying to launch the Migration Wizard
SBS2011-PostInstall-02.jpgSo the first step is to create this user.

Using the SBS Console select the Users and Groups option across the top of the console.  You will then see the screen as illustrated below.
 SBS2011-PostInstall-03.jpgThere will be no users listed here, don't panic, this is perfectly normal.  You will not see the existing users in the SBS Console until the migration is complete.

Click on the Add a new user account on the right hand side.  This will launch the new user wizard. Admin-User-01.jpgEnter the details for your user.  The important part is that you select Network Administrator as the User Role.  Once you are done click next.

The following screen we are asked to enter a password for the user, enter a password and click Add User Account.
 Admin-User-02.jpgWe then see the following screen, this can take a few minutes to complete but what we are looking for is 5 green ticks.  If for any reason any of the stages fail the final screen will tell you what failed and why.
 Admin-User-03.jpgThe following screen allows us to associate computers with this user or add an additional computer.  There is no need to do this for the new Administrative User.  Click finish to exit the wizard.  From the SBS Console select the Home section and click Migrate to Windows SBS to start the migration tasks.
 Admin-User-04.jpg

Step 5.   Setting data locations

When launching the migration wizard there is a list of tasks to complete.  These should be done in the order they are presented. As illustrated below.
Migration-Wizard-01.jpgThe first task is to set the data locations for Exchange, Sharepoint, Shared Folders, Redirected My Documents and Windows Software Update Services.  The wizards are the same for each so this guide will only run through one of them.

NOTE: If you don't have a second volume configured there is no need to run this part.  If you try to you will receive the following error.
 Migration-Wizard-Error.jpgIf you do not have a second volume and don't intend to have one, then on the first screen of the wizard put a check in the Task Complete radio and click next. 
Migration-Wizard-02.jpgTo run the wizards click the hyperlinks on the above screen one by one.  The first screen (below) is simply the summary of what you will be doing, click next when ready.
 Migration-Wizard-03.jpgThe next screen runs a check of the configuration, one of the tasks this is completing is checking for available volumes and disk space for the files to be moved to.
 Migration-Wizard-04.jpgOnce this is complete we are given the options of locations to select from.  At this stage because we have not configured a backup you will see an error that this has not been done.  Click OK to continue.
 Migration-Wizard-06.jpgMake the drive selection and then click Move.  What we want to see is the screen below indicating that the move has been successful.  Click finish and then move on to the next hyperlink to continue setting the data locations.
 Migration-Wizard-07.jpg

Step 6.   Configure the Network

The next task the wizards want us to complete is the Configure the Network wizard.  This is the Connect to the Internet Wizard.

When launched, the first screen we see is the one below.  From here we need to select the Start the Connect to the Internet Wizard hyper link.
 Migration-Wizard-08.jpgThe following screen will give you a summary of some information that will be required to allow the wizard to be completed.
 Migration-Wizard-09.jpgMake sure you have this information to hand and click Next.

The next screen does a check of the network configuration and will attempt to discover among other things your router.  Part of these checks will also detect if there are any other DHCP services running on the network.
 Migration-Wizard-10.jpgThe wizard will not continue if another DHCP service is detected (see image below).  Therefore if you plan to use another device for DHCP then this must be temporarily disabled to allow you to complete this task.  I would however recommend that you do use SBS2011 for DHCP rather than another device.
 Migration-Wizard-11.jpgOnce you have disabled any DHCP services the wizard will move on and display what it has detected from your network configuration.
 Migration-Wizard-12.jpgCheck the information is correct and if so click Next.  If not make any appropriate changes before clicking next.

Once done, we are looking for the big green tick as illustrated below that says our network has been configured.
 Migration-Wizard-13.jpg

Step 7.   Configure the Internet Address

The 3rd task in the migration wizard is to Configure the Internet Address this wizard is for configuring the external domain you intend to use with the SBS2011 server.

The first screen we see is a summary screen explaining what the wizard will do.
 Migration-Wizard-14.jpgClick the hyperlink for Start the Internet Address Wizard and then read the guidance on the screen below.
 Migration-Wizard-15.jpgAs this is a migration you will probably already have an external domain name and it will already be configured.  The rest of this guide will assume you have a domain name registered and that you will use the control panel from your ISP to manage your External DNS.  Click Next to start the configuration.

On the following screen, select the I already have a domain name that I want to use and click Next.
 Migration-Wizard-16.jpgOn this screen select the I want to manage the domain name myself and click Next.
 Migration-Wizard-17.jpgThe following screen we need to enter the external domain name we will be using, this will be the domain name used in the hyperlink for Remote Web Workplace, Outlook Web App, ActiveSync and will be used to create your email address.
 Migration-Wizard-18.jpgClicking the Advanced Settings link will allow us to reconfigure the name that appears in the self-signed SSL certificate from remote.domainname.com to something else.  If you have mail.domainname.com or owa.domainname.com setup currently then this is where you would enter this information.

Once done click the configure button and the wizard will make the necessary changes.  Once completed we want to see the summary screen as below.  We are looking for 3 green ticks to say it has been successful.
 Migration-Wizard-20.jpg

Step 8.   Migrate Exchange Mailboxes and Settings

The next step of the Migration process is to migrate the Exchange Mailboxes and Public Folders.  When we launch the wizard for this task we see the following screen.
 Migrate-Exchange-Mailboxes-And-Settings-01.jpg Clicking the hyperlink (at time of writing) takes you to the technet article for Migrating Mailboxes.  To do this, we need to delve in to the Exchange Management Console.  Click Start > All Programs > Microsoft Exchange Server 2010 and select Exchange Management Console.

Once the console has launched, navigate to Recipient Configuration > Mailbox.  Here we should see all our mailboxes listed.  All the mailboxes that appear as Legacy Mailbox are currently located on the SBS2003 servers mailstore.
 Migrate-Exchange-Mailboxes-And-Settings-02.jpg You can either batch select the mailboxes using SHIFT or CTRL or do each mailbox one by one.  Once you have selected the mailboxes to move, from the Action Pane on the right hand side select New Local Move Request.  This will start the move mailbox wizard.
 Migrate-Exchange-Mailboxes-And-Settings-03.jpg From the first screen click the browse button to select the Mailbox Store on the new SBS2011 Server.  Once you have done this click Next.
 Migrate-Exchange-Mailboxes-And-Settings-04.jpg For this screen, leave it at defaults for the first run.  If you find that mailboxes fail to move due to corrupt items you may have to increase the value here to allow those corrupt items to be skipped and for the mailbox to move successfully.
 Migrate-Exchange-Mailboxes-And-Settings-05.jpg The screen above is simply a summary of what task you will be performing, clicking the New button will start the mailbox moves.

Once complete, we are looking for the following screen, all green ticks.
 Migrate-Exchange-Mailboxes-And-Settings-06.jpg If you are moving the mailboxes in batches then repeat this task until all mailboxes have been moved to the SBS2011 server.
The next stage is to migrate the Public Folders. To do this, complete the following steps on the SBS 2003 Server:

Click Start > All Programs > Microsoft Exchange Server > System Manager
Navigate to Administrative Groups > First Administrative Group > Servers > Servername > First Storage Group
Right click on the Public Folder Store and select Move All Replicas.  The only option that should appear in the list is your Exchange 2010 server.  Click OK.

Now that we have moved the data to the SBS2011 server it’s best to leave the Exchange Settings as is for a day or so to a) make sure all the data is moved before we perform any other Exchange related tasks. b) allow all the outlook clients to update automatically with the new server settings.  We can now continue with the rest of the migration.

Step 9.   Remove Legacy Group Policies and Logon Settings

The next step is to remove any Legacy Group Policies and Logon Configurations that are incompatible with SBS2011.  The recommendation here is that any logon scripts in use should be migrated to Group Policies and/or Group Policy preferences.  However in my experience it doesn't cause any problems if this is not done.

Further information on these processes can be found here:

Remove old logon scripts for Windows SBS migration: http://technet.microsoft.com/en-us/library/cc527605(WS.10).aspx
Remove old Active Directory Group Policy objects for Windows SBS 2008 migration: http://technet.microsoft.com/en-us/library/cc527585(WS.10).aspx

Step 10.   Migrate users' Shared Data

This is another task where you need to perform the configuration manually.  The steps required can be found here: http://technet.microsoft.com/en-us/library/cc527517(WS.10).aspx

Once you have the shares configured a simple backup of the SBS2003 server and restore to the 2011 server will restore all data with associated permissions.

Alternatively you could use robocopy which is part of the Windows 2003 Resource Kit which can be downloaded from: http://www.microsoft.com/downloads/en/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

There is also command line reference for robocopy here: http://technet.microsoft.com/en-us/library/cc733145(WS.10).aspx

Step 11.   Migrate Fax Data


Launching the wizard will display the following screen.
 Migrate-Fax-01.jpgClicking the hyperlink Click to start Migrating your fax data this will move the data to the new server.  At this stage if there is no fax services installed/configured on the SBS2003 server you will receive the error displayed below.
 Migrate-Fax-02.jpgYou will receive this error if you haven't installed the Fax role on to Windows Server.  This is an optional step and should only be installed if you will be using fax services.

Step 12.   Migrate Users and Groups

As part of joining the SBS2011 server to the domain which contains SBS2003 and making it a Domain Controller it has already got a copy of the Active Directory and all the users and groups.

However, they will not appear in the SBS Console, this is normal and can be resolved following the instructions here.

To allow the users to be seen a new role needs to be applied.  To do this on the first screen the wizard shows a hyperlink to Run the change user role wizard as illustrated below.
 Migrate-Users-01.jpgClick this link, to start the wizard.  From the list displayed select the role you wish to assign to these users.
 Migrate-Users-02.jpgOn the following screen put a check in the box for Display all user accounts in the Active Directory as illustrated below.  This will display all of the users.  Highlight your existing user then click the Add button to move them to the right hand side.
 Migrate-Users-03.jpgClick the change user role button.  We are looking for a screen similar to the one below with lots of green ticks to confirm the roles have changed.
 Migrate-Users-05.jpg

Step 13 - Uninstall Exchange 2003 from Small Business Server 2003

Hopefully you are arriving at this step a day or two after you have migrated all the mailboxes, if not then I would recommend you leave it for a day or two just to allow all client computers to automatically update the Exchange server setting in outlook.  If you uninstall Exchange 2003 from the Small Business Server and this hasn’t happened then the clients will have to be changed manually.

To perform this task we will need Small Business Server 2003 CD 2, which will be asked for during the uninstallation.  Before we can do this though, there are a few steps we need to perform otherwise we will not be able to uninstall it.

If you use Recipient Policies that are Manage Mailbox policies, then these will need to be removed.  Likewise, if you have Recipient Policies that are used for both e-mail address definition and mailbox management, the settings defined under Mailbox Manager Settings will need to be removed.  You DO NOT need to remove your e-mail address policies.

The Recipient Update Service is not used in Exchange 2010 and is therefore not required, so it can be removed.  To do this you will need to use ADSI Edit.  This can be done by using the following procedure:
click Start > Run > MMC > Click OK
Select File then Add/Remove Snap-in
Click Add and select ADSI Edit and click Add, then close and OK
Right click on the ADSI Edit and select 'Connect to'.  From the drop down under 'Select a well known Naming Context', select Configuration and click OK
Expand Configuration > Services > Microsoft Exchange > Organisation Name > Address List Container > Recipient Update Services
Right click on Recipient Update Service (Enterprise Configuration) and select Delete.  There may also be a Recipient Update Service (ORGNAME) this also needs to be deleted
Only delete the Recipient Update Service entries under the container; DO NOT delete the container itself or any other entries

The final step in preparation for uninstalling Exchange Server 2003 is to delete the routing group connectors that would have been created as part of the installation.  I have highlighted them in the image below.  Simply right click on each connector and select delete.
 Uninstall-Exchange-01.jpg 
We are now ready to uninstall Exchange 2003.  To do this, navigate to Start > Control Panel > Add or Remove Programs.  From the list of installed applications, highlight Windows Small Business Server 2003 and click Change/Remove.

Click next on the Welcome screen, and next on the screen that follows.  Once the component screen opens pull down the drop down next to Exchange Server and select remove, as shown below. Then click next and next again.
Uninstall-Exchange-02.jpg

Step 14.   Check Transfer of the 5 FSMO roles to SBS2011


All of the 5 FSMO roles should already have been transferred to the SBS2011 as part of the installation process but it's always worth a check.  The steps below will give instructions on how to do this if required.

Caution needs to be taken when performing this next step.  I would advise that ALL of the previous steps need to be completed before this is done as Small Business Server MUST hold all 5 FSMO roles.

Once you are ready, the roles can be transferred as follows.  Working on the Windows 2008 server do the following:
Click Start > Administrative Tools > Active Directory Users and Computers
Right click on the domain name and select Operations Masters.  You will see the screen below.
On each tab (RID, PDC & Infrastructure) click the change button.
Accept the confirmation that you want each role to be transferred.
 
That is 3 of the 5 roles transferred.  To do the next one, which is the Domain Naming Master we need to do the following:
Click Start > Administrative Tools > Active Directory Domains and Trusts.
Right click where it says Active Directory Domains and Trusts and select Operations Master.
Once again click the Change button and say yes to the notification dialog.
4 down with 1 to go.  To move the Schema Master role we need to do the following:
Click Start > Run and type regsvr32 schmmgmt.dll
Click OK to the confirmation
Click Start > Run and type MMC and click OK
Select File > Add/Remove Snap-in from the console
From the list select Active Directory Schema, click Add
Click Close and OK.
Right click on Active Directory Schema and select Change Active Directory Domain Controller
Choose the Windows 2008 Server from the list and click OK
Click OK on the warning Dialog box.
Right click on Active Directory Schema and select Operations Master
Click the Change button and say yes to the notification dialog
That’s all the FSMO roles transferred from the Small Business 2003 Server.  The next and final step is to demote the server from being a Domain Controller.

Step 15.   DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network

This is the final step of the migration process.  If you have made it this far, well done!  This is the easy bit!

At this point it is worth double checking that both the SBS2003 and SBS2011 server are both configured to use the SBS2011 server for DNS in the TCP/IP properties of the NIC.  The only DNS entry should be the IP address of the SBS2011 server.

The first thing we need to do is make sure the SBS2003 is no longer a Global Catalog Server.  Click on Start > Administrative Tools > Active Directory Sites and Services.  Locate the Small Business Server as shown in the screen shot below.
 
Right click on NTDS settings located under the Small Business Server and select properties.  Remove the check from the Global Catalog check box and click OK.  Close Active Directory Sites and Services snap-in.

The final step is to run DCPROMO.  To do this, do the following:
Click Start > Run and type DCPROMO and click OK
Click next on the Welcome screen
DO NOT check the box that says “This server is the last domain controller in the domain” and Click next
Enter a new administrator password for the local administrator user and click next
The server will then remove Active Directory Services from the SBS2003 server and it will no longer be a Domain Controller.

Once this has finished, allow the server to restart, login and then shut it down.  You have now completed the migration.

The only additional step would be the Trusted Certificate Wizard.  This is not a requirement to make everything work it just makes the annoying certificate messages go away on external clients and mobile phones.  You can get a certificate that will satisfy this requirement from http://www.exchangecertificates.com

If you are still with me, well done!  There are a few sections of additional reading below if you would like to know some more detail about some of the processes we have just completed.  There is an excellent article from EE Expert tigermatt around the purpose of the FSMO roles which you will find under the further reading section.

Further Reading

Move/Migrate Sharepoint Services: http://technet.microsoft.com/en-us/library/cc288664.aspx
Move last legacy Exchange Server: http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
Demystifying the Active Directory FSMO Roles by tigermatt: http://www.experts-exchange.com/articles/Software/Server_Software/File_Servers/Active_Directory/Demystifying-the-Active-Directory-FSMO-Roles.html
25
Comment
Author:Glen Knight
43 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
Brilliant article - I can see this one being referenced numerous times.

Yes vote from me.

Alan
0
 
LVL 9

Expert Comment

by:Alex Appleton
Great work, fantastic resource!
0
 
LVL 3

Expert Comment

by:mrwolf
Just what i needed. This is a great article. Very well done!
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.

 

Expert Comment

by:Stefan Müri
well done i was following your guide and it worked super!!!
0
 

Expert Comment

by:sergio3986
fantastic article!!! I will be performing a migration in the upcoming weeks.

Curious...what is the estimated amount of time required to complete a standard migration? Estimate?

It is my first time performing one.
0
 

Expert Comment

by:Stefan Müri
hi sergio hi did it during 3 day's mostly in the evening, typical IT time... lets say 3x 5 hours
0
 
LVL 74

Author Comment

by:Glen Knight
Well, it's actually pretty hard to say.  The installation of SBS2001 and then associated Windows updates I would say 2-3 hours depending on how many updates are available at time of migration.

Then you have the mailbox migration, exchange will just get on with this in the background if you bulk move.  So it depends on mailbox numbers and sizes.

Then there is the data migration.  Again it depends on thwacking of data and the method you use to migrate the data.

Is Companyweb being migrated?  Personally I like to start a migration on Thursday, do the things that can be done without interrupting service, Friday evening start the mailboxes moving and the shared data copying.

Users come in on Monday open outlook, it updates to the new server, users are accessing data on the new server.  Confirm availability and stability.  Tuesday remove Exchange from source server then dcpromo and turn off.  

Wednesday spent on-site with clients ironing out any problems.

May seem long winded but I believe in making sure my installs are stable and meet the customers expectation.  I don't want to spend 3-4 weeks resolving problems and the customer doesn't want me doing this either.  A bit of hand holding makes them feel comfortable and saves you a lot of time in the future.  Plus, they remember how smooth this migration was when the next version cones out.

And more importantly, when they are at their executive breakfast meetings boasting about their new SBS2012 they will tell their friends what a good job you did!
0
 

Expert Comment

by:sergio3986
Thanks for the update and breakdown. I'm basically trying to calculate my time and time slots during the day when is best and when would have the least impact to business....I now have something to work with and can plan accordingly...Huuuuuge thanks!!!

No company web migration for my project, very small deployemnt right now. Exchange with maybe 8 mailboxes, default GPO's nothing fancy, oh and pop connector...that's it. They are just hosting a acces database on it.

Thanks again, and I will document and provide results, pains & gains, from a migration newbie :)
0
 

Expert Comment

by:chrisp666
I don't like to seem ungrateful, and am probably going to seem dim, but am I right in thinking the migration means a new name for the new server?
0
 
LVL 4

Expert Comment

by:Tekyguy
Yes, the new server will have a new name.  Unfortunately there is no way to 'upgrade' to SBS 2011, you have to do a swing migration.
0
 

Expert Comment

by:BlenGroup
Great arcticle.  I've done this now for 2 different clients and encountered a seemingly unsolvable issue both times.  When attempting to run the SBS 2011 Migration Preparation Tool on the SBS 2003 server, I get a warning that I "must be a member of all of the following security groups; Enterprise Admins, Domain Admins, and Schema Admins", which of course I am.  The solution was that I had to make my primary group something other than those three groups.  Once I changed that, it ran without issue.

I search the internet for over an hour without finding this fix, so I thought I'd post it and see if it helps anyone.
0
 

Expert Comment

by:chrisp666
BlenGroup, that was a kind and thoughtful post. Thank you.
0
 

Expert Comment

by:reliantcorp


Isn't it necesary to change the redirected folders GPO to point to the new server ? or is there a new feature that autoatically moves that data to the new server ?

I remember that was one of the first things on the 2003-2008 SBS migration docs.

Thanks !!
0
 

Expert Comment

by:chrisp666
Speaking as a rank amateur, I think it is. I've just completed a migration, and pointers to redirected folders on the old server have been the bane of my life.
0
 
LVL 13

Expert Comment

by:ktaczala
I'm planning on doing a customers migration (SBS 2003 to SBS 2011 (25 Users)) this comming weekend(Friday, Saturday, Sunday).  During the pre-install preparation it wants me to upgrade MSDE 2000 to sp4.  That part is failing.  The customer does not use sharepoint nor companyweb.  Although it's there.  Can I ignore this error? And continue with the migration?
0
 

Expert Comment

by:reliantcorp

chrisp666:

Do you mean the redirected folders moved by theirselves ? before activating folder redirection on the new target server ? or did you have to change the original GPO first to get them moved ?
0
 

Expert Comment

by:chrisp666
No, they didn't move by themselves. To be honest, the setup we had was a bit non-standard, but after the migration, the My Documents folders on workstations still pointed to the old server. That was when I discovered the GPO object which set that...as I said, I am not an expert.

On the whole, it all went pretty smoothly, but I did have problems with redirections - in the end, in desperation, I set them manually - also, not all permissions were correctly moved. Oh, and we had enormous mailboxes and quite a few of them were corrupt, this took ages to resolve.

No flames please - I admit I know nothing!!
0
 

Expert Comment

by:the_chuckster
Well done. Now how about one to take SBS2008 to SBS2011 ???   :)
0
 

Expert Comment

by:ChristianWirth
Really great guide!

We had a move with this as a master guildeline and succeeded so far. A few problem here and there but everything went well.

A couple of points are still unclear.

Microsoft states that a couple of GPOs have to be removed from the old server. These GPOs are listed here:
http://technet.microsoft.com/en-us/library/gg563794.aspx

Does this really need to be done?

One of the last things to do for the migration in your guide was to uninstall the Microsoft Exchange 2003 server.
This wasn't written in the Microsoft Migration Guide and does run into a error on our installation.
The deinstallation can not be completed therfore.
The error reads:

 SBS 2003 Uninstall Error
[08:04:50] Leaving CBaseComponent::ScPostSetup
[08:04:50] Objekt wird bei /dc=local/dc=DOMAIN/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=DOMAIN/cn=Administrative Groups/cn=erste administrative gruppe/cn=Servers/cn=SERVEROLD geändert.
[08:04:50] msExchMonitoringMode is set to 0
[08:04:50] Leaving CBaseExchangeComponent::ScPostSetup
[08:05:32]  CComBOIFacesFactory::QueryInterface (f:\titanium\admin\src\udog\bo\bofactory.cxx:54)
           Error code 0X80004002 (16386): Keine Schnittstelle.

This looks to be related to DNS issues or to NNTP, IIS, SMTP not running as well as all Exchange services being started not as local service. All checked and fixed as described in this articles:

http://support.microsoft.com/kb/822583/en-us
http://support.microsoft.com/kb/295623/en-us

Will it be sufficient to just demote the old server without uninstalling Exchange Server 2003 (SP2) (slightly different path on the CD) ?

Won't spent to much time on getting rid of the old environment.

Thank you!


regards,

Christian Wirth.

0
 
LVL 74

Author Comment

by:Glen Knight
>>Microsoft states that a couple of GPOs have to be removed from the old server.

As the technet article you linked to states, these are optional tasks.

>>Will it be sufficient to just demote the old server without uninstalling Exchange Server 2003 (SP2) (slightly different path on the CD) ?

if you do you will have to manually remove Exchange from Active Directory.

Unfortunately I don't know what the message translates to in English.  I advise you to raise a question in the SBS zone with a translation.  Wherever possible I would favor proper removal of Exchange before demotion.
0
 
LVL 7

Expert Comment

by:jesaja
Hi demazter
this article is just great but do you have any recommendations to migrate from a normal Windows 2003 Server and Exchange 2003 to SBS 2011.

I really appreciate your help
0
 
LVL 7

Expert Comment

by:jesaja
Thanks demazter sounds promising, except public folder migration :)
But is it worth to migrate 5 users only or start from scratch?
0
 

Expert Comment

by:dolphinituk
Just saved my bacon when got confused with parts of microsofts article. Thanks
0
 
LVL 38

Expert Comment

by:younghv
@demazter,
This is an amazing document and thank you for putting it together.

I've noticed several people posting specific "My Migration" types of questions here.
Would it be better for us to post a question over in the SBS Zone and then link to it in a comment here?

Thanks again - big "Yes" vote above.
0
 

Expert Comment

by:oneobserver
First off, thank you for an excellently documented procedure. I have used it for two migrations now and have only one issue. In Step 13, you say to remove the Recipient Update Policy _before_ you remove the old Exchange 2003. if you do this you will always get the dreaded "Prerequisites not found" error. Wait until after you have removed Exchange 2003 to remove that policy and the process is more likely to complete sucessfully, or at least tell you what is really wrong. If you have followed the process as outlined then you need to do the following:

-      Opened ADSIEDIT.MSC and at the following location.
-      Configuration / Services / Microsoft Exchange / <organization name> / Address Lists Container
-      The RUS Container was empty.
-      So right clicked on the Addres Lists Container ===> Select new object-msexchangeserverRecipient - The value should be Recipient Update Services. then finish.

Once Exchange 2003 has been removed, go back and remove this object.

This procedure was supplied by Microsoft Tech Samesh Panicker who helped me identify this problem on the second migration.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
@oneobserver - I have done three migrations following the guide to the letter and haven't had the issue you did, so there isn't any need to change the steps as they work 100%.

You might not have followed one properly, or had a peculiar problem with two of your migrations, but I haven;t had any issues with my migrations.

Alan
0
 
LVL 74

Author Comment

by:Glen Knight
oneobserver,

From your post above it would appear the instructions in my guide were not followed and you actually deleted the Recipient Update Services container and not the object under it.

If you read my instructions it quite clearly says "Only delete the Recipient Update Service entries under the container; DO NOT delete the container itself or any other entries"

If you delete the container then you will indeed get the error that you are seeing.

Thanks
demazter

@youngv, thank you for your comment, much appreciated.  You are absolutely right, this is an article and should not be used for troubleshooting, if experiencing problems when following this guide then questions should be raised in the SBS zone where there are a number of experts who are more than capable of assisting.

@alanhardisty, thanks for your comment, very pleased you have had success with the article :)
0
 

Expert Comment

by:oneobserver
I had the same problem with both migrations at that step and that was what the MS techs had to do in both cases to get past it. At least this way it's documented if anybody else has the same issues I had. Overall it's a great document and you did a tremendous job on it. I used it as my "bible", for these two clients with just that one hiccup. I have at least 3 more to do and will continue to use it for those.
0
 

Expert Comment

by:oneobserver
You are correct. That is where I got confused. It wasn't clear what you meant by that line, as the instructions say to right click on the thing that is the container and delete it, then the line below says not to delete the container. The steps above give a work around for anybody who misread it the way I did.
0
 
LVL 74

Author Comment

by:Glen Knight
OK, not sure on your last comment.

The article says:

click Start > Run > MMC > Click OK
Select File then Add/Remove Snap-in
Click Add and select ADSI Edit and click Add, then close and OK
Right click on the ADSI Edit and select 'Connect to'.  From the drop down under 'Select a well known Naming Context', select Configuration and click OK
Expand Configuration > Services > Microsoft Exchange > Organisation Name > Address List Container > Recipient Update Services
Right click on Recipient Update Service (Enterprise Configuration) and select Delete.  There may also be a Recipient Update Service (ORGNAME) this also needs to be deleted

0
 

Expert Comment

by:oneobserver
Time to chock it up to long hours bleary eyed syndrome since I don't have another system in a state where I can compare at the moment. Your procedure is correct. I was wrong. If somebody else goes wrong the same way. The steps to correct are in my first post. It's obviously possible or the warning wouldn't be there...
0
 

Expert Comment

by:planetiware
Hi does anyone know if its ok to create the answer file on a xp machine ? haivng issues loading this due to .NET issue

thanks
0
 

Expert Comment

by:one8solutions
Got this from Best Practices Analyzer:
The ISAPI Filter for Companyweb web site is not at its default value of SHRPTFLT and stsfltr. To reconfigure the ISAPI Filters for companyweb, click Start, point to Administrative Tools, click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, right-click Companyweb, and then click ISAPI Filters. Add filters SHRPTFLT and stsfltr.

Is this something to be really concerned about? The source server's companyweb is blank also
0
 
LVL 7

Expert Comment

by:karllangston
When running the BPA do I need to address all the warnings as well or just the errors?
0
 
LVL 21

Expert Comment

by:Jason Yousef, MS
Great article...god bless...
0
 

Expert Comment

by:ditobot
I would like to change our internal domain name on the SBS 2011 server.  The original name is really long so I wanted to shorten it.  Is it possible to do this at the page "Source and Destination Server networking information"?

If not is it possible to change this after the migration?  Or is it possible to change this before on the SBS 2003 server?

Thanks
0
 
LVL 76

Expert Comment

by:Alan Hardisty
You can rename the SBS 2003 domain pre migration - don't do it mid-migration, or post-migration.

A guide on how to:

http://www.msexchange.org/tutorials/domain-rename.html
0
 

Expert Comment

by:clesin
If I am migrating from Server 2003 Standard with Exchange 2003 to SBS 2011with Exchange 2010. Are these instructions still accurate, or would there be different steps to take?
0
 

Expert Comment

by:clesin
Dematzer,

I started to follow this article from Migrating to SBS 2011 which - per your comment on this EE article you said it was identical to migrating to SBS 2008:


The issue I have is: When running the 'source tool' it does not say anything about 'Preparing Exchange' as your screenshot would suggest. Is that something that I should be concerned about??
0
 
LVL 34

Expert Comment

by:Shreedhar Ette
Hello Dematzer,

Does the procedure is same for SBS 2003 t0 SBS 2011 Essentials?
0
 
LVL 25

Expert Comment

by:Tony Giangreco
Great article!!!

Do you have guides for the following?

Migrating from SBS2003 32 bit to Server 2008 R2 standard (not SBS) where exchange is not being used on the sbs2003 box and not planned for Server 2008 R2?

Migrating from SBS2003 32 bit to Server 2012 R2 Essentials where exchange is not being used on the sbs2003 box and not planned for Server 2008 R2?

Migrating from SBS2003 32 bit to Server 2012 R2 Foundation where exchange is not being used on the sbs2003 box and not planned for Server 2008 R2?
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Join & Write a Comment

This Micro Tutorial will teach you how to add a cinematic look to any film or video out there. There are very few simple steps that you will follow to do so. This will be demonstrated using Adobe Premiere Pro CS6.
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
Suggested Courses
Course of the Month17 days, 13 hours left to enroll

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month