Transition from Small Business Server to Standard Windows Server

 

Transition from Small Business Server to Standard Windows Server

These steps are applicable for transition from all the versions of Small Business Server to Windows Server 2008/ 2008 R2/ 2012.

Note: The Transition Pack which was used previously for same is no more available.

Transition Process:

1. To ensure a seamless Transition we need to start by performing Health Check of AD and Exchange using tools like dcdiag, BPA for SBS 2003, 2008 and 2011 and BPA for Exchange: http://blogs.technet.com/b/ptsblog/archive/2011/11/14/performing-an-active-directory-health-check-before-upgrading.aspx

2. Microsoft Windows Small Business Server 2003 Best Practices Analyzer: http://www.microsoft.com/en-us/download/details.aspx?id=5334

3. We always need to ensure that we take a complete backup along with System State Backup of the SBS Server.

http://technet.microsoft.com/en-us/library/cc787254(v=ws.10)

Description of the Windows NT Backup Restore Utility for Windows 7 and for Windows Server 2008 R2

http://support.microsoft.com/kb/974674

4. Install the new Standard Windows Server OS (2008 R2) on the new hardware and join it to the existing SBS domain.

5. Upgrade the Schema on SBS Server 2003/ 2008 to support Windows 2008 R2

a. Insert the media for Windows Server 2008 R2 into the Small Business Server 2003/2008 server.

b. Browse to the following folder:
<DVD drive >:\Sources\Adprep> Adprep /forestprep

c. Press C, and then press ENTER. Wait for the process to complete.

d. Type the following command:
<DVD drive >:\Sources\Adprep>Adprep /domainprep

when this step completes, you should receive a message: “Adprep successfully update the domain-wide Information”

6. Promote the new Windows 2008 R2 to be a Domain Controller and DNS Server.

 

7. Make 2008 R2 as Global Catalog

8. Migrate the DHCP database http://blogs.technet.com/b/networking/archive/2008/06/27/steps-to-move-a-dhcp-database-from-a-windows-server-2003-or-2008-to-another-windows-server-2008-machine.aspx

Application Movement:

All the applications, services and data that are installed or configured on SBS machine (Exchange, SharePoint, File Server Terminal Server License etc.) we need to transfer them on to 2008 R2 DC or member server’s depending on the nature of the application.

1. Exchange Migration: http://technet.microsoft.com/en-us/library/dd638130.aspx http://technet.microsoft.com/en-us/library/bb124350.aspx

2. Before moving FSMO roles install the below hotfix, applicable only in case of SBS 2003

This software update extends the allowable grace period for the supported scenarios from 7 days to 21 days. http://www.microsoft.com/downloads/details.aspx?FamilyId=64903D3C-3264-418D-9199-2963A599E268

3. Transfer FSMO roles to WS08R2: http://support.microsoft.com/default.aspx?scid=kb;EN-US;255504

After you move the FSMO roles you have 21 days grace period to keep the SBS box running.

Note: After the completion of 21st day, the SBS box reboots itself few time during the day, services become inconsistent, so it’s recommended to perform the steps before this period end.

After proper testing in production uninstall Exchange from SBS. After making sure users are able to access and authenticate from the domain.

Demote SBS Server and unjoin it from the domain, reformat and use the hardware for any other purpose.

And you are done. Monitor the environment for a few more days for errors in the event log and make sure that all of them are rectified if any.

Cheers!

- A-Team

Comments

  • Anonymous
    January 01, 2003
    How do you find out how many days are remaining before the source server shuts down? I'm moving from SBS 2008 to 2012 Essentials but the dashboard is completely different from SBS 2011. There's a great blog article for SBS 2011 on how to find this information but I have yet to find one for 2012 Essentials.
  • Anonymous
    January 01, 2003
    The authentic xplorer² installer is digitally signed and guaranteed to be free of viruses and malware. Please be careful if you download xplorer² from untrusted sources, always prefer the official download location (this page).


  • Anonymous
    January 01, 2003
    Hi Luke, This kind of transition is supported. There are two possibilities:
  1. Break fix errors that occurs on windows server will be handled by the Windows support team.
  2. Application failure errors (Exchange, sharepoint) will be taken care by respective teams. Hope this helps. Regards, Bonoshri
  • Anonymous
    January 01, 2003
    Interesting, a great article. Very useful Regards,

  • Anonymous
    January 01, 2003
    thanks

  • Anonymous
    January 01, 2003
    I am surprised at you for even suggesting to run the Exchange BPA for 2007. It requires .Net 1.1 which breaks SharePoint and IIS. Why would you suggest such a thing?

  • Anonymous
    January 01, 2003
    Great article and more in depth than any other article relating to this topic. We have go from SBS 2011 to Server 2008 R2 eventually sometime this year because of number of users. Do you know if any of the SBS Licenses carry over to Server 2008 R2? I know I probably have to get Exchange CALs, but I was hoping 75 SBS CALs would turn to Windows CALs and are not just a waste. thanks,

  • Anonymous
    January 01, 2003
    xplorer = explorer

  • Anonymous
    September 08, 2012
    Very interesting...  So, this begs the question...  is this supported?  I see nothing on the SBS Team blog that refers to anything like this.  Further documentation from the SBS side to explain that this transition is supported would be greatly appreciated.  Thanks!

  • Anonymous
    September 11, 2012
    Sounds good.  Thanks!

  • Anonymous
    September 15, 2013
    For those migrating from SBS 2003 to Windows 2012, you no longer need to upgrade the Schema on step 5. Once you promote Windows 2012, it will update the Schema for you. Also, there is no 32 bit Adprep on Windows 2012 DVD.

  • Anonymous
    February 04, 2014
    Is it possible to migrate without Exchange Server SBS 2003? Our Server is corrupt and the customer does not Need it anymore.,.

  • Anonymous
    February 22, 2014
    everything worked fine until all the FSMO roles were moved. Once that happened sysvol and netlogon shares were not working correctly.

  • Anonymous
    March 21, 2014
    how to migrate the small business server 2003 along with sql 2005 to windows 2008 r2 server

  • Anonymous
    March 21, 2014
    how to migrate the small business server 2003 domain along with sql 2005 to windows 2008 r2 server

  • Anonymous
    August 22, 2014
    Can anyone address the best way to address redirected folders and the migration process? Specifically from SBS 2008 to Server Standard 2012.

  • Anonymous
    August 29, 2014
    Greg: You should be able to update the Group Policy or create a new Folder Redirection GPO to point to the new server. If you configure the GPO correctly, I believe you can force the workstations to move the files to the new location so that there is no manual intervention. However, if you do this, you may find performing a robocopy of the redirected folders to the new location is beneficial as the workstations will only have to update files instead of copying them all over to the new server again.

  • Anonymous
    September 16, 2014
    Do you have procedure for uninstalling Exchange from the SBS2003 server ? Is there a MS technote ? Thanks.

  • Anonymous
    September 17, 2014
    how about the 75 user limit will it be removed after migration.

  • Anonymous
    October 10, 2014
    On my W2K8R2 DVD the adprep tool is not found in D:SourcesAdprep, but in D:SupportAdprep. And because SBS2003 is 32-bit I needed to run the adprep32.exe instead. Otherwise it worked.

  • Anonymous
    December 17, 2014
    We are installing Windows Server 2012 R2 we have Windows Small Business Edition 2011 could we join it to Windows Servetransition-from-small-business-server-to-standard-windows-server.aspxr 2012 R2 as a member server

  • Anonymous
    January 07, 2015

  1. @ Rajesh - If you migrate to Windows Server Standard the 75 user limit in SBS will go away. However, if you use the Essentials Experience role in Windows Server 2012 R2 it has its own limits.

    2. @Brian - If you install WS 2012 R2 as a domain controller you can't join a SBS 2011 server to the domain as a member server - the SBS 2011 server must be the domain controller set up during SBS setup. The way to go is to join the WS 2012 R2 server to the SBS 2011 domain - where it can be either a member server or a second domain controller. If you don't want the SBS 2011 domain for some reason (for example, you want to be rid of its limitations) you can't use the SBS licence any more. You will also need Windows Server 2012 CALs becaus the SBS CALs are for Windows Server 2008 only.
  • Anonymous
    February 01, 2015
    Hey Greg,
    Before you demote anything or move FSMO roles, there is a tool inside SBS server manager (not Server Manager, but SBS Server Manager, they are both exist) - to move redirected folders anywhere to any UNC or drive within the domain (I know it works on drives, I suspect UNC) - use that and the data gets moved and the GPO gets edited automatically.

    After you demote the SBS, you will have to manually do an extra step when you add new users to domain to also get them to redirect desktops.
  • Anonymous
    March 05, 2015
    Hey Ben/Greg, What is the manual step that you need to do when to add a new computer/user to the domain - apart from simply joining to the domain?
  • Anonymous
    March 23, 2015
    The DVD path is wrong. It should read "Support" instead of "Sources"

    :SupportAdprep> Adprep /forestprep
  • Anonymous
    August 16, 2015
    The comment has been removed
  • Anonymous
    September 05, 2015
    Can I use this method to migrate from SBS 2011 to Windows 2012 R2 Standard? I'm planning to migrate Exchange to Office 365
  • Anonymous
    September 05, 2015
    Hey Ben/Greg, What is the manual step that you need to do when to add a new computer/user to the domain - apart from simply joining to the domain?
  • Anonymous
    September 19, 2015
    Sarish, thanks good article. One question left after all this is, "what to do with the old SBS Group Policies?". I found this article applying to SBS 2003 (https://technet.microsoft.com/en-us/library/gg563794.aspx) (although intended for SBS to SBS). I also found this article pertaining to SBS 2008 (https://technet.microsoft.com/en-us/library/cc527585%28v=ws.10%29.aspx).
  • Anonymous
    September 19, 2015
    Nice article thanks for sharing this useful information.

    http://www.happydiwali2015cards.com