Categories Menu

Migrating SharePoint Foundation 2010 (part of SBS 2011) to a full blown SharePoint 2010 on Windows 2012 R2


GOAL :  To migrate SharePoint Foundation to a full blown SharePoint 2010 server running on a Windows 2012 R2 server.  This is useful if you have a SBS 2011 but reaching out its user license limit and you need to move to a full size Windows domain and retire your SBS 2011 server.

  1. On the old Sharepoint (SBS 2011 server), using SQL Management Studio, backup the SharePoint CompanyWeb database. By default, the database name used by CompanyWeb is ShareWebDB.
  2. On the new server, install the OS. On my end, I used Windows 2012 R2.  Set a Static IP address if possible.
  3. Set group policy so when you add .NET 3.5 in as an add-on feature, it will not error out. Modify Computer Configuration -> Administrative Templates -> System and look for the entry for “Specify settings for optional component installation and component repair.  Set it to ENABLED and check “Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS).  This step only applies to Windows 2012 and Windows 2012 R2.
  4. Run gpupdate /force on a command window. Or better yet, just reboot the server.
  5. Add the IIS (web server) and .NET 3.5 on Roles and Features in windows.
  6. Install SQL 2008 standard. I heard that SQL 2008 Express will work too but I have some doubts so I just installed the full version.  I didn’t attempt to use SQL 2012 or SQL 2014 since my goal is to mimic the whole SQL setup of the old server.
  7. Run all the windows updates an SQL 2008 Service Packs.
  8. In SQL Management Studio of the new SharePoint server, create a new database called ShareWebDb.
  9. Assuming that you have created service accounts were created for the previous SharePoint system, you will need to provide the same permissions of all those accounts in your new SharePoint server. On my end, I had service accounts of the following names – spfarm and spwebapp.  Along with the domain administrator account, I made these 2 accounts sysadmin of the SQL 2008 R2 component of the new SharePoint server.
  10. Copy the backup file on step 1 to a folder in the new SharePoint server that is accessible to SQL Management Studio. On my end, I saved it at C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup.
  11. Restore the backup file onto the new SharePoint server.
  12. Although the permissions from the backup file would propagate over to the newly restored database, check if they did by checking the user mapping to the ShareWebDb database and they should be set at db_owner.
  13. Start the SharePoint Installation. But before you start the actual SharePoint 2010 installation, you will need to run the PrerequisiteInstaller program first.  This will correct and install all the necessary programs required in order for SharePoint to complete the installation.
  14. Install SharePoint
    1. Choose a Server Farm Setup. Remember, in SBS2011, the SharePoint is in a Server Farm Environment.
    2. On the server type, choose Stand Alone (all the components will be housed in the same server. Click on Install Now.
  15. After the installation, proceed in running the configuration wizard.
  16. At the prompt where it asks to run the following services – IIS, SharePoint Admin Service, SharePoint Time Server, choose YES.
  17. Now comes to the critical part which is the recreation of the CompanyWeb site. Once you get to the site creation screen, choose Team Site.
  18. On the Groups for this site, just keep the default. Home Visitors for Visitors to this site, Home Members for Members of this site and Home Owners for Owners of this site.  Click OK.  Once you see the Welcome page, close the browser or the site.
  19. Run SharePoint 2010 Central Administration.
  20. On the main Central Administrator screen, under Application Management, choose Manage web applications.
  21. On Web Application page, choose New to create a new Web Application.
  22. On the Create a New Web Application page, user the following:
  • Authentication – Classic Mode
  • IIS Web Site – On my end, I used the existing IIS Default Web Site since no web application is using it. In the event that this web server is being shared with another Web App, you may choose to create a new website to differentiate SharePoint from it.
  • Port – this should be the same as the port that your old CompanyWeb used. On my end it was 987.
  • Host Header – you can practically put anything. But to be consistent, I had mine as NewCompanyWeb
  • Path – Leave it as default (C:\inetpub\wwwroot)
  • Authentication Provider – I set mine to NTLM since my server is part of the domain. No for Anonymous since I don’t want non-authenticated users to see our company website, and SSL to NO since I’m not incorporating any SSL security for this site.  You may choose to set it to Yes if you have an existing SSL resource (i.e. SSL certificate)
  • URL – This should be accordingly adjusted based from the values in the Port and Host Header fields.
  • Application Pool – Unless you already have an existing Application Pool that you can use, you may have to just create a new one. On my end, I named it “SharePoint – <Abbreviation of my Company Name>.  You may prefer to use any name that you can think of.
  • Security Account – set it to configurable and click on the “Register New managed Account” link. Use one of the service accounts that you had created in AD and specify its password.  Make sure you append the domain name onto the account (i.e., mydomain\spwebapp)

You may or may not choose the Automatic Password Change and the period of expiration and notification.  On my end, for security purposes, I had to set it.

  • Database Server – From the previous steps during the creation and restoration of the ShareWebDb database, depending on which instance you restored it to, use that in the Database Server Field. On my end, since I restored it to the default instance, I had the value of Database Server set to just the server name (i.e., SPSERVER1\)
  • Database Name – Leave whatever is in there for now. We will map to the correct database later on.  Just to be on the safe side, although not really necessary since we won’t be using this database, nonetheless, set a sa password for this database.  So choose SQL authentication, put sa in the account and enter your preferred password.
  • Failover Database Server – Leave this blank.
  1. Hit OK. Wait until the message saying the Web Application creation has been completed.  You will also see the Company Web app being added to the list.
  2. On the left pane, click on Application Management. You may also go back to the Central Administration windows and choose Application Management.
  3. Choose Configure alternate access mappings.
  4. Click on Add Internal URLs.
  5. Click the “Alternate Access Mapping Collection” drop down selection. A new window with the list of collections will appear.  Choose the one pertaining to your CompanyWeb site.
  6. In the URL protocol, host and port field, enter http://newcompanyweb/. For the Zone, choose INTRANET.  Click SAVE
  7. On the left pane, click on Application Management. You may also go back to the Central Administration windows and choose Application Management.
  8. On the Databases section, choose Manage Content Database.
  9. Click on the Database that we defined in previous step.
  10. Scroll down to the bottom of the Database Information page and hit the check box to remove the Content Database. Then Click OK and OK.
  11. Now, click on Add a content Database.
  12. In the Add a Content Database page, do the following:
  • Web Application – click on the pull down selection and pick the application that you just created for your CompanyWeb (i.e. http://mynewcompanyweb:987/
  • Database Server – Specify the database instance. Since we restored the ShareWebDb database in the default SQL instance, only the server name needs to be specified. (i.e., MYSQLSERVER1\
  • Database Name – ShareWebDb
  • Authentication – Choose SQL authentication and specify the sa account and its password.
  1. Open IIS manager and make sure that no other site has a binding to port 80 except the CompanyWeb site. Since we used the Default Website for this example, make sure that only the Default Website has a binding to port 80.  And in the Default Web Site, remove all its bindings to any port other than port 80.
  2. Restart the SharePoint and IIS services in the Windows Services window. Or better yet, just restart the whole server.
  3. Modify your internal DNS. Add an A record to map the IP address of the new SharePoint server to the SharePoint name (i.e. newcompanyweb      168.100.250).  Reload DNS.  You may also do this to your external DNS if your SharePoint is internet facing.
  4. On the workstation that you will use to test access to the new SharePoint server, make sure the DNS records are flushed.
  5. Then on a browser enter http://newcompanyweb.
  6. Wallah!! Your CompanyWeb site should now be migrated!!

Take me back to the Tech Tips list..

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.