Solved

Migrating SharePoint ("Companyweb") site from SBS2011 to stand-alone server

Posted on 2016-11-21
2
176 Views
Last Modified: 2017-01-31
We are planning to decommission an old SBS2011 server.  The SharePoint site is to be migrated to a new dedicated Server 2012 R2 virtual machine (presumably running SharePoint Foundation 2013).

What steps must we take in order to successfully migrate the site?

Both servers are fully patched with Windows updates. Thanks!
0
Comment
Question by:David Haycox
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 13

Accepted Solution

by:
Ajit (Kevin k) earned 500 total points
ID: 41897246
Before proceeding, back up your Source Server before you begin the migration process. Making a backup helps protect your data from accidental loss if an unrecoverable error occurs during migration.

This is probably the best documentation to follow for Migrate from Previous Versions to Windows Server 2012 R2 Essentials or Windows Server Essentials Experience: https://technet.microsoft.com/en-gb/library/dn408633.aspx

Regarding your request, maybe you could refer to the following article. It’s for SBS 2011, but the steps are similar with Windows Server 2012 Essentials. Move All SharePoint Foundation 2010 Databases for Windows SBS 2011 Standard to Another Server: http://technet.microsoft.com/en-us/library/gg616007.aspx

However, to upgrade from SharePoint 2010 Products to SharePoint 2013, you use the database-attach method to upgrade. In the database-attach method, you first create and configure a SharePoint 2013 farm. Then you copy the content and service application databases from the SharePoint 2010 Products farm, and then attach and upgrade the databases. This upgrades the data to the new version. Site owners can then upgrade individual site collections. For detailed steps: Step by Step guide to Migrate from SharePoint 2010 to SharePoint 2013

Also check this link: https://technet.microsoft.com/en-us/library/gg563792(v=ws.11).aspx

Before decommissioning your source server you need to run a gpupdate on all machines connecting to the domain.

Hope this helps!
1
 
LVL 2

Author Comment

by:David Haycox
ID: 41897587
Was able to work it out with that info, thanks!  Here are the steps I took, for the record:

1.      Install SharePoint Foundation and SQL Server Management Studio on new server
2.      Windows updates and PSCONFIG, check event logs for errors
3.      Detach / backup databases and copy to new server (https://technet.microsoft.com/en-us/library/gg616007.aspx)
4.      Check settings on 2013 with “Get-SPWebApplication | fl” from SharePoint 2013 Management Shell
5.      Delete default web application and content database on 2013
6.      Create classic-mode web application in 2013 (need to use CLI as it is deprecated in the GUI): https://technet.microsoft.com/en-us/library/gg251985.aspx (“To create a classic-mode Web application in SharePoint 2013”)
a.      New-SPWebApplication -Name “SharePoint - 80” -ApplicationPool “SharePoint - 80” -AuthenticationMethod Kerberos –ApplicationPoolAccount NetworkService -Port 80 -URL http://servername
7.      Delete the content database just created (in SharePoint Central Admin and in SQL Management Studio)
8.      Attach / restore the content database from 2010 using SQL Management Studio
9.      Test the database with the following command: Test-SPContentDatabase –Name ShareWebDB –WebApplication http://servername
10.      Rectify or ignore any errors listed, as appropriate
11.      Attach the database with: Mount-SPContentDatabase –Name ShareWebDB –WebApplication http://servername
12.      Test website
13.      Add alternate site mapping (http://companyweb)
14.      Upgrade the site collection to the 2013 look (follow link at top of page)
15.      Apply new look
16.      Update internal DNS entry to point companyweb to the IP of new server

Here are some more resources I found useful:

http://en.share-gate.com/blog/step-by-step-upgrade-sharepoint-2010-database-to-sharepoint-2013
http://www.sharepointdiary.com/2013/09/migrate-from-sharepoint-2010-to-2013-step-by-step.html
https://technet.microsoft.com/en-us/library/gg251985.aspx
https://technet.microsoft.com/en-us/library/cc303436.aspx
http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=124
1

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

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

Pimping Sharepoint 2007 without Server-Side Code Part 1 One of my biggest frustrations with Sharepoint 2007 in the corporate world is that while good-intentioned managers lock down the more interesting capabilities of Sharepoint programming in…
I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question