Monday 23 July 2012

SBS 2003 to SBS 2011 Migration Guide – v1.4.0

It is important to note that this Migration Guide is closely tied into our SBS 2011 Setup Guide which can be found here:

The official Microsoft migration document can be found here:

Microsoft now has an official migration Web site for SBS!


If installing SBS 2011 into a VM setup then keeping that VM’s time accurate is important.

SBS 2003 to SBS 2011 Migration Steps
These preparatory steps still apply:

A couple of very important things to note:

  • Have a backup of the SBS 2003 box and System State BEFORE beginning the migration process!
  • You will need the SBS install disk 2 with the Exchange65 folder for the Exchange uninstall step!

We use both NTBackup to create a system state backup as well as ShadowProtect to create a full server image before initiating any changes on the production network.

In the case of ShadowProtect, we will have it on the SBS 2003 box at least a couple of days before the migration process starts to get a base full backup and set an incremental schedule as well. Then, when it comes time to begin the migration we can run incremental backups during the process which are very short in duration.

Preparation for Migration

It is important to be prepared for the coming migration. One of the steps we need to be prepared is to have all of the up to date drivers and firmware downloaded before running the migration process. It is important to make sure that the server hardware’s firmware is up to date before putting the server into production.

  • Server Hardware
    • RAID Controller firmware.
    • Server Board firmware.
    • RAID and server board drivers.
    • Hardware management software.
  • Server OS and Server Apps
    • Download the most recent service packs for OS, Exchange, SharePoint, etc.
  • Printers and Copiers
    • X86 (32-bit) and x64 (64-bit) Printer Drivers
      • WHQL certified drivers are preferred if possible.
      • Used to deliver the printers to the workstations via Group Policy.
      • If XP is still around have the PushPrinterConnections.exe utility handy.
  • LoB Applications
    • Updates for the LoBs and their MySQL, SQL, or other database backend are good to run at this time.
    • Have Simply or QuickBooks downloaded as they are large.

Itemize the DHCP reservations on the source server if they are not already documented somewhere. If the reservations are going to be restructured then make sure to have the MAC addresses on hand for each device.

  • Device MAC: ____________________ Description: ____________________
  • Device MAC: ____________________ Description: ____________________
  • Device MAC: ____________________ Description: ____________________
  • Device MAC: ____________________ Description: ____________________

Run a full export of the third party trusted certificate (SSL) that is being used and password protect it. Have it handy to import into the destination server when the time comes.

PHASE 1: SBS 2003 Preparation Steps

  1. SBS 2003 with 2 NICS and/or ISA.
    • Uninstall ISA and run CEICW
    • Install firewall appliance or gateway.
    • Set NIC1 Gateway to the new device.
      • IP:
      • Subnet:
      • Gateway: (gateway device)
      • DNS1: (self)
      • DNS2: Blank
    • Disable NIC2 and run CEICW.
    • Verify that the DNS Server service is working as expected. A reboot may be required.
  2. If SBS 2011 will be using an existing RWW URL that is protected by a third party certificate, make sure to export that certificate from SBS 2003 with the key and import it using the wizard on SBS 2011 at the appropriate time.
    • OPTION: Have the certificate issuer’s site logon information on hand to use for a rekey of the certificate using the SBS 2011 Third Party Trusted Certificate wizard.
  3. Make sure that the up to date Windows Server 2003 Resource Kit Tools (download) and Service Pack 2 Support Tools (download) are installed on SBS 2003.
  4. Verify Active Directory Forest and Domain levels are set to Windows Server 2003 native.
  5. Reset the Active Directory Restore Mode password (MS KB322672).
    • image
  6. Verify that Exchange 2003 is running in Native Mode (Step 17 on the SBS 2003 Setup Checklist).
    • Also make sure the Exchange Management Console is showing the routing groups in step 16 of the above list.
  7. Verify that Exchange 2003 has Service Pack 2 installed and functioning as expected.
  8. Verify that the default SBS SMTP Connector is installed.
    • Also check for any additional connectors installed as they will interfere with the replication of Public Folders.
  9. Remove any SmallBusiness SMTP Connector Forwarding.
    • image
  10. Verify and record any custom Send As setups for Exchange users. They will need to be manually set up on the new SBS 2011 server.
  11. Verify Windows Server 2003 Service Pack 2 is installed.
    • The SBS 2003 BPA will help with the post SP2 fixes if any were missed.
  12. Verify that SBS 2003 has Small Business Server 2003 Service Pack 1.
    • image
    • HKLM\Software\Microsoft\SmallBusinessServer\ServicePackNumber
  13. The following are run from the command prompt to test Active Directory health:
    1. DCDiag
      • DCDiag [Enter]
      • DCDiag /test:DNS
      • DCDiag /? (List of switches)
    1. NetDiag
    2. RepAdmin
      • RepAdmin /viewlist *
      • RepAdmin /SyncAll
      • RepAdmin /KCC
    1. NetDom /query FSMO
  14. Verify that the SBS 2003 CA is clean before starting.
    1. Microsoft KB 889250: How to decommission a Windows enterprise certification authority and how to remove all related objects from Windows Server 2003 and from Windows Server 2000
      1. Step 6 (We had to empty all folders before our last migration ran successfully on 2012-0723).
      2. Bad on left (our source) good on right (client product SBS 2003):
      3. image
      4. All folders on the right were actually empty. This is a server we set up about three years ago. The server on the right was a contract job.
  15. The following can be done to test the health of the Exchange databases at the command prompt and with the stores dismounted (remember to backup):
  16. Exchange mailbox prep.
    1. Possible Error: SBS Migration Error- Exchange – The token supplied to the function is invalid 80090308
      • image
    2. Have everyone empty their Deleted Items folder.
    3. Get everyone to run an Archive process in their Outlook to remove older and not necessarily needed content.
    4. Verify the Replication Message Priority setting for all Public Folders: Urgent 
      • image
    5. Verify the Replication interval setting for the root Public Folder Store: Always run
      • image
  17. Download and run the Microsoft IT Environment Health Scanner (download page).
  18. Run the server time setup step.
    1. w32tm /config /syncfromflags:domhier /reliable:no /update [Enter]
    2. net stop w32time && net start w32time [Enter]
      • Standalone Hyper-V or VMware: Configure the host to poll and allow the guests to poll the host through the firewall for time.
  19. Verify that the default Administrator (500 Account) has the Primary Group set to Domain Users.
  20. Run the SBS 2003 Best Practices Analyzer and follow its recommended steps.
  21. Backup SBS 2003 completely.
    • TIME:________
  22. Backup the SBS 2003 system state with NTBackup.
    • TIME:________
    • image
    • Note that the System State backup in the above image was run from within NTBackup on the source server.
  23. Run the VPN Wizard to disable VPN PPTP services on the source server.
  24. Download and install the Microsoft Baseline Configuration Analyzer 2.0
  25. Run the Source Prep Tool
    • Insert the SBS 2011 DVD and run SourceTool.exe from the Tools folder.
    • A copy of this folder can be placed on the source server if using a USB flash drive to install the SBS 2011 OS.
    • Note that a reboot is required.
    • TIME:________
  26. Disable the Update Services (WSUS) on SBS 2003 before installing SBS 2011 in Migration Mode.

PHASE 2: SBS 2011 Migration Mode OS Install

  1. Multi-NIC servers: Disable all NICs in the BIOS except #1.
  2. We set up an 8GB or 16GB USB flash drive to be bootable using the NTFS file system (previous blog post).
    • The SBS OS image file is well over 6GB in size.
    • We also drop the necessary drivers and server management tools in a folder called Drivers on the flash drive.
  3. Set up the Answer File in Migration Mode with the requisite information.
    • SBSAfg.exe is in its own folder under the TOOLS folder on the SBS 2011 DVD.
    • We make two copies of the XML file:
      • 11-06-17-ClientName-SBSAnswerFile.XML
      • SBSAnswerFile.XML (goes on the flash drive)
    • We also create a PDF from within the Answer File Generator.
    • The SBSAnswerFile.XML can be saved to a small VHD if running the migration virtually for a lab test or going into a virtual production environment.
  4. Begin the SBS 2011 install in Migration Mode (SBS 2011 Setup Guide).
    • Note that the migration project will jump in and out of the SBS 2011 Guide’s various setup steps.
    • Setup the SBS 2011 RAID 10 array and configure the OS partition.
      • Five or more 15K spindle option: RAID 5 on hardware RAID plus battery backup.
      • A small 5 or so seat firm with low I/O requirements will run fine on RAID 5 with four 15K SAS spindles.
    • Plug the USB flash drive into the server.
    • Note that on some Tier 1 servers the USB flash drive will need to be plugged in once past the SBS 2011 EULA stage.
    • Use the Load Driver dialogue to verify that the server hardware is reading the USB Flash drive with the Answer File.
    • Depending on the hardware manufacturer, make sure to have the latest RAID controller on hand to install. We put it into a folder on the Answer File USB flash drive to keep things simple.
  5. Verify the time during the SBS 2011 OS setup process especially if installing in a VM (previous blog post).
  6. SBS 2011 Migration Mode status will show on SBS 2003:
    1. ADUC: SBS 2011 will show up in the Domain Controllers OU.
    2. DNS:
      • SBS 2011 will show up in _msdcs.SBSDomain.local with its new GUID.
      • SBS 2011 will show up as a Name Server in SBSDomain.local and Subnet (whatever subnet being used).
    3. DSSite.msc: SBS 2011 will show up after the above DCPromo reboot.
      • Note that the replication links can take anywhere up to 15-20 minutes to show up in DSSite.msc.
  7. SBS 2011 should eventually come up with the Green Check of a successful install.



Before clicking the Migrate to Windows SBS link in the Getting Started Tasks we need to work on our SBS 2011 server to bring its configuration up to production quality. Things like finishing off the disk configuration, driver installs, and more are covered in our SBS 2011 Setup Guide.image

PHASE 3: Preliminary SBS 2011 OS And Services Checks

  1. Verify that the Exchange services are up and running (an ongoing thing).
  2. Set up the SBS Backup and take a backup of the freshly installed SBS 2011 OS.
    • Make sure to have all disks for the backup rotation handy so that they can be done at the same time due to a bug in the destination wizard.
  3. Work through the SBS 2011 Setup Guide up to the Getting Started Tasks – Out of Order.
    • Set any DHCP Reservations in place once the SBS Native Tools Console has been configured.
    • Keep taking backups on both servers after each portion of the migration is completed.
  4. Back up both servers.
    • SBS 2003 Time: _____
    • SBS 2011 Time: _____

PHASE 4: SBS 2003 to SBS 2011 Migration Wizard Steps

  1. On the source server edit the SBS 2003 Folder Redirection Policy to point to the destination server.
    • \\NewSBS\RedirectedFolders
      • image
      • SBS 2003 while a DC will maintain the 21 day period before SBCore starts shutting the server down.
      • SBS 2003 DCPromod to a domain member server will only have 7 days to complete the redirected data move.
      • Folder redirection caveat and settings suggestion: SBS 2003 to SBS 2008 Migrations – Folder Redirection Caveat (previous blog post)
  2. Log onto SBS 2011 with the existing 500 Admin account and create the new SBS 2011 account using the SBS 2011 Console.

    • We like famous or not so famous generals for the necessary admin accounts created on our SBS domains.
    • Note the absence of the UAC while logged in with the old 500 Admin account.
    • What happens when the SBS Migration Wizard is opened while logged on with the original SBS 2003 domain admin account:
    • image
  3. Log off SBS 2011 and log back on with the new SBS 2011 Domain Admin account.
  4. Note that the GUI customization steps in our SBS 2011 Setup Guide will need to be run for this new account. 
  5. Make sure to change the DHCP service’s credentials to the new Domain Admin account and password.
  6. Update the Serial Number for the Domain.Local SOA in the DNS Forward Lookup Zone.
    • image
    • We use the full year plus month: 2011050000 (May 2011) to tell us when DNS was modified in any way. Note that the serial has already been bumped up a number of times since this particular DNS SOA was changed.
  7. Export the Public Folders to PST via an Outlook client connected to the existing SBS 2003 as a precautionary measure.

  8. Run the Migration Wizard from the SBS Console.

    1. Move the Data folders.
      1. SharePoint Foundation Data.
      2. Users’ Shared Folders.
      3. Users’ Redirected Folders Data.
      4. WSUS Update Repository Data.
        • Enable Access-based Enumeration on the Users Shared Folders and Users Redirected Folders after moving them.
    2. Connect to the Internet.
      • Check off the appropriate step in the Getting Started Tasks section in the SBS 2011 Setup Checklist.
    3. Configure the Internet Address.
      • Check off the appropriate step in the Getting Started Tasks section in the SBS 2011 Setup Checklist.
    4. Migrate Network Settings
      1. Migrate DNS Forwarders.
      2. Migrate the Mobile Users Group.
      3. Using the SBS Native Tools Management Console import the SSL certificate PFX exported from the source server earlier in this guide.
    5. Migrate Exchange mailboxes and settings
      1. Remove the SmallBusiness SMTP Connector
        • If the SBS Console was open during the SBS 2011 Migration Mode install the ESM node may not show the new Connectors. Click on DOMAIN (Exchange) then click the Refresh button to bring up all of the new settings.
          • image
        • SmallBusiness SMTP Connector on the Source Server.
          • image
      2. POP3 Connectors
        • This is a manual process. A screenshot of the existing list can be used as a checklist.
        • Account removal is done now on the source SBS 2003 server.
        • Adding the mail accounts to the SBS 2011 POP3 Connector is indicated later in this guide.
      3. Migrate the Exchange Server public folders (TechNet).
        • Right click on Public Folder Store (Source-SBS) and Move All Replicas.
          • image
        • On the Destination Server in an elevated Exchange PowerShell:
          • Get-PublicFolderStatistics –Server DestinationSBS [Enter]
        • If the Public Folder Store is quite large, change the limits on the destination server.
        • Note that this process may take some time and caution should be taken so as to not move on before the folders have replicated.
        • Run the above PS command a few times and the number of items on each PF should increase.
        • On the Source server: Public Folder Instances in ESM will eventually be empty.
      4. OPTION: Public Folder Migration Extra Steps
        1. If replication happens but then looks to be stuck:
          1. Right click on the Public Folder Store (Source) and Resend Changes…
            • image
          2. Change the logging level for Public Folders:
            • image
      5. Move the Offline Address Book.
        1. Move OAB to SBS 2011.
          1. On Destination: ESM –> Org Config –> Mailbox –> OAB Tab.
          2. Click Move near the bottom of he Actions list.
            • image
          3. Select the destination server under the Browse button and click Move.
        2. Enable Web-based Distribution in Exchange 2010.
          • image
        3. Set the Offline Address Book for the Mailbox Database
          1. Destination: ESM –> Org Config –> Mailbox –> Database Management.
          2. Right click the Mailbox Database and Properties.
            • image
      6. Move the mailboxes to SBS 2011.
          • Done from the Exchange 2010 Console on SBS 2011.
          • NOTE: Verify the largest mailbox size on SBS 2003 and set Standard User Role mailbox size and defaults in Exchange 2010 accordingly!
          • LARGEST MAILBOX: ______________
        1. ESM –> Recip Config –> Mailbox –> Click Recipient Type Details header to sort.
          • image
        2. SHFT + Click to highlight all Legacy Mailboxes.
        3. Click New Local Move Request under Actions.
          • image
          • We use 10 messages as the default setting for corrupt messages.
        4. MOVE STATUS: ESM –> Recip Config –> Move Request.
        5. Post Move: ESM –> Recip Config –> Move Request.
        6. ESM –> Recip Config –> Move Request.
        7. Highlight all Completed moves and right click and Clear Move Request.
          • image
        8. OPTION: Enable Circular Logging on the destination server.
          • Have a look at the mailboxes on the Source SBS 2003 server. The new SBS 2011 created domain admin account starts logging into each one. The move progresses from there.
          • It can take a long time before anything seemingly happens. Please be patient.
    6. Some important considerations for this point in the migration:
      1. Port forwarding can be changed for SMTP to the new SBS server once the mailboxes are moved.
      2. Obtaining a third party trusted certificate before this stage would be a good idea so that remote users do not deal with the need to import the self-issued SBS 2011 certificate. Use the SBS 2011 wizard to generate the CSR if required, or to import the certificate exported from the source server previously.
      3. Official SBS Blog: How to Configure SBS 2011 Standard to Accept E-mail for Multiple Authoritative Domains.
        • We will try and publish a blog post covering our own methodology for this process.
    7. Remove legacy Group Policy objects and logon settings.
      1. Remove old logon scripts including the SBS_Login_Script.bat file.
        • %windir%\sysvol\sysvol\SBSDomain.local\Scripts
      2. Remove the batch file from all users in ADUC.
        1. Select all domain Users and right click on any highlighted user account and click on Properties.
          • image
        2. Profile Tab
        3. Check Logon Script and leave blank.
        4. Apply and OK. All users will no longer have the batch file associated with them.
      3. Remove old GPOs from SBS 2003:
        • Click the Details tab to see the Created/Modified date for the GPOs before deleting.
          • image
          • Delete can be done in bulk by CTRL+Click on the following GPOs listed under the Contents tab in the Group Policy Objects folder.
        • Small Business Server – Windows Vista Policy (RipCurl Policy)
        • Small Business Server Auditing Policy
        • Small Business Server Client Computer
        • Small Business Server Domain Password Policy ***
        • Small Business Server Internet Connection Firewall
        • Small Business Server Lockout Policy
        • Small Business Server Remote Assistance Policy
        • Small Business Server Update Services Client Computer Policy
        • Small Business Server Update Services Common Settings Policy
        • Small Business Server Update Services Server Computer Policy
        • Small Business Server Windows Firewall
      4. NOTE: Password Policies are set in the SBS Console later on in our SBS 2011 Setup Guide. When set, _all_ user accounts will receive a request to change their password.
      5. Remove the SBS 2003 WMI Filters:
        • PostSP2
        • PreSP2
        • Vista (RipCurl Filter)
    8. Migrate users’ shared data
      • We use the Company shared folder created in the SBS 2011 Setup Guide to store all user data. Access-based Enumeration is set up to maintain control over which users can see what folders in that share.
      • We use BeyondCompare for our data migration purposes. RoboCopy is another option.
    9. Migrate the Companyweb internal Web site.
      1. Option 1 (Microsoft method):
        • Run the Prescan tool.
        • Migrate the entire Companyweb site by detaching the databases on SBS 2003 and reattaching them on SBS 2011 .
        • This method is pretty straightforward in that it preserves all of the existing data structures.
        • Create a DNS CNAME for OldCompanyweb that points to SBS 2011 FQDN.
        • Update the existing Companyweb CNAME to point to the new SBS 2011 .
        • Remember to edit the DNS CNAME record for Companyweb to point to SBS 2011 .
      2. Option 2 (direct data copy):
        • SharePoint list data that is Outlook integrated can be moved into new SharePoint libraries.
        • If versioning is not required, then opening the existing document libraries in Explorer View enables us to copy the data straight across.
    10. Migrate fax data.
    11. Migrate users and groups.
      1. Migrate Security Groups and Distribution Lists.
        • C:\Program Files\Windows Small Business Server\bin\GroupConverter.exe
        • image
      2. Run the Change User Role Wizard.
        • Map to Standard User.
        • Note: To view the user accounts that were migrated from the Source Server, in the Users list view, click the Display all the user accounts in the Active Directory check box.
      3. Delete the following legacy AD accounts:
        • STS Worker
        • SBSBackup
        • IUSR_SBS
        • IWAM_SBS
      4. Map appropriate RWW RDP user permissions to domain workstations.
      5. OPTION: POP3 Connector setup the user account’s POP3 e-mail to their mailbox.
    12. Enable Folder Redirection and Quotas in the SBS 2011 Console.
      • Select all users for the policy.
      • We redirect Documents and Desktop by default.
      • We will disable exclusivity for the user and set it to move back to the local system. This causes FR to appear off in the SBS Console though.
      • GPUpdate /force on both source and destination.
      • Verify GPO settings on source before DCPromoing the source server. Manually initiating AD replication would be a good idea too.
    13. Migrate SQL Server Data.
    14. Migrate Terminal Services Licensing.
    15. Finish the Migration.
      1. Update the Recipient Update Services on SBS 2003.
        1. Recipient Update Service (SBSDOMAIN)
          1. Click the Browse button, put SBS 2011’s name for the Exchange field and click the Check Names button before clicking OK.
        2. Recipient Update Service (Enterprise Configuration)
          1. Exchange: SBS 2011
      2. Delete the Routing Group Connectors
        1. Delete: SBSNew-SBSOLD
        2. Delete: SBSOld-SBSNew
          • image
      3. Uninstall Exchange 2003 (previous blog post) from the source server.
        • Add/Remove Programs –> Small Business Server –> Change/Remove.
        • Remove: Exchange Server
        • SBS CD 2 will be required for this uninstall.
      4. Manually Remove Exchange if the above blows up. (Previous blog post)
    16. Use ADSI Edit to clean up the CN=Servers container.
      1. Official SBS Blog: Empty ‘CN=Servers’ Container Causing Issues with Public Folders on Small Business Server 2011
    17. Change the edge device’s publishing rules:
      1. SMTP to destination.
      2. HTTPS to destination.
      3. Create and publish HTTPS port 987 and point it to the destination server.
      4. PPTP 1723 is an option for VPN if needed.
      5. Delete inbound RDP proxy port 4125 and SharePoint 444.
    18. DCPromo SBS 2003 to remove the DC role.
      • REMINDER: SBS 2003 will start to reboot 7 days from the introduction of the SBS 2011 box when a domain member server only!
      • If Certificate Services has been installed on the source SBS 2003 box previously it will need to be uninstalled before the DCPromo process will run.
      • NOTE: If the DCPromo fails due to NETLOGON time-out, BACK UP in the wizard and start it again. It will run successfully the second time.
      • A reboot will be required.
    19. Run a final image of the source SBS 2003 box.
    20. Disjoin SBS 2003 from the SBS 2011 domain.
      • The generic WORKGROUP works here.
    21. Delete the original SBS 2003 Folder Redirection Policy.
      • If it is seemingly missing, click on Refresh in the GPMC to bring it up.
      • For comparison (in our case since we enabled both above):
        • Old policy will refer only to the Documents folder.
        • New policy will refer to Documents and Desktop.
        • We can check the time stamp for each GPO for clarification as well.
    22. Give the built-in Administrator group the right to logon as batch.
      • image
    23. Clean up any references to the old SBS 2003 server on the SBS 2011 server:
      • ADUC: Delete from SBSComputers OU.
        • Yes to the “…other objects” message.
      • DNS: Remove ALL references to SBSOld NS and DNS A in all zones.
      • DNS: Remove ALL references to SBSOld’s IP Addresses in all zones.
      • Active Directory Sites and Services: Remove the old SBS 2003 server reference.
      • Remove SBSOld from All Computers in WSUS Console.
      • Remove SBSOld from the Security Filtering under the Scope tab of the Update Services Server Computers Policy GPO.
        • image
    24. Download, install, and run the Windows Small Business Server 2011 Best Practices Analyzer.
    25. Verify user quotas for the Standard User Role.
      • Exchange Mailbox
      • Redirected Folders
      • NOTE: Any changes made to the Standard User Role will affect any user that has that role.

PHASE 5: Continue the SBS 2011 Setup.

    1. Complete setup from the Getting Started Tasks – Out of Order – Backup Now step and up from the SBS 2011 Setup Guide.


Some of the various problems we can run into running a migration from SBS 2003 to SBS 2011.

Philip Elder
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer


Paul said...

Hi Philip, great migration guide!!! We're planning our first one here so this will be a real help!

Had an idea and was wondering if you could think about it and suggest why this would NOT work.

Take a shadow copy of the client's server, restore it in our office to different HW\Virtual. Run through the migration in our office with the new HW. Once we're happy with it, take it back to the client's site, turn off their old SBS and insert the new one. Copy the data/mailbox PSTs to the new server and hey presto, migration should be complete. This seems too simple, why would it not work? Would the Windows clients freak out? Thanks, Paul.

Philip Elder Cluster MVP said...


The biggest catch in this is in the time between the snapshot and when the new box goes live.

What kind of change process mitigation will be in place to catch all that happens on the old box?

We do virtualize the crustier boxes and run the migration virtually as a test but we run the migration live on live systems when it comes time to do the deed.

IMNSHO, there are just too many variables that can be missed in the method you describe.


Philip Elder Cluster MVP said...

On the other hand, Jeff Middleton's Swing Method would work for you and kind of comes close to the methodology described.


Hayden said...

One of the best migration guides I've seen. Good work. Thanks for the effort.

艾瑞克 said...

Hi Philip,

I follow your guide to migrated the SBS2003 to SBS2011. Everything work fine beside the new sever keep pointing at the old server as DC and Global Catelog. as soon as I uncheck Global Catelog on the 2003 server, My exchang stop working. Do you have any idea ?

Oran Emuse said...

wow. amazingly highly detailed transfer. i am amazed. i work for an IT consult company in Israel, and we just now got an SBS2003 to SBS2011 migration job, and this article just made me so much more relaxed. very well written. you rock! thanks !

boma23 said...

excellent Migration Guide - I worked between this and DeMazter one on Expert's Exchange and his blog. Yours helped pricularly with somethings he left to be "assumed" :)

Far better than the MS guide, and happy o have complete my 1st SBS2003 - 2001 migration!

Philip Elder Cluster MVP said...

Glad to see that our guide is helpful.

Exchange 2010 does weird things during and sometimes after the migration process.

Make sure that Exchange 2003 is uninstalled cleanly, or removed properly, before moving on to DCPromoing the SBS 03 out.

We DCPromo SBS 2003 once we are ready to finish up. Messing with the DC attributes/settings before demoting is something we would not do.



George said...

I am getting ready to do a SBS 2003 to SBS 2011 move and one of my major concerns is the IP address of the destination (new) server. Can it be the same as the old server? I would like to keep everything the same so that I don't have to make other changes to the network. Any information would be helpful.


Philip Elder Cluster MVP said...


No, the destination server must have its own IP address that is unique to itself.


Tismon said...

I realize that the pop3 connector is not very desirable, but for the moment, it is the best option for us as we transition.

However, the sbs 2011 version doesn't seem to have the ability to leave messages on the server. Do you know of any way to do that without going to a 3rd party software?

And if another program is needed, it looks like Shell Tool's POPConnector might be the cheapest that supports exchange2010/sbs2011. Do you know anything about it or possibly a better option for cheap?

Thank you.

Lorenzo said...

Hi Philip, I was wondering if SharePoint Foundation, that is included with SBS 2011 will support external collaboration, ie. cleints and vendors. We're a small company and we outsource most of our IT 'stuff'. I just don't think our company will be able to take advantage of all the benefits that SharePoint Server offers. Thanks!

Anonymous said...

How long does this take?? is it possible to have up and running over a weekend

Anonymous said...

Dear Philip,

I just finished a migration from sbs 2003 to 2011. I mostly used your guide which was absolutely great. It's simple, it's understandable and the pictures are very helpful. Thank you very much for your work to do this.

Dávid from Hungary

Michael Kistenmacher said...

Wow! this is work, that MS should have done officially - hope, they have sent you a gift... Thank you very much!

Anonymous said...

Wow indeed, Many thanks Philip for providing such a detailed guide.

Best Regards

nietsze said...

When having problems with dcpromo when removing the old sbs, the following ntdsutil does magic for you: