Let me start by saying there is no Upgrade option for SharePoint 2010 to 2013. No matter what people say, one cannot upgrade SharePoint 2010 to 2013. The option to do an in-place upgrade was removed since SharePoint 2010. Anytime you need to create a new farm, detach content database and move them to a new farm that process is called a migration, because one is migrating the data from one location to another, regardless of leveraging a tool or out of the box methods. I am sure that you will agree on how to Migrate SharePoint 2010 to 2013 once you have read the article.

Great now that we have gotten that terminology out of the way lets focus on Migrating SharePoint 2010 to 2013.

Read and action our SharePoint Migration guide.

This SharePoint Migration page has all the content you need to complete a successful migration. Compare features of different versions of SharePoint. Plan and strategies the correct approach to ensure a successful migration. Use PowerShell scripts to clean your data. Listen to a webinar about what to do and what not to do. Get a checklist in place to follow a detailed plan. Send out an infographic on SharePoint migration to all involved so that everyone knows what to expect.

Now the practical how to steps

Perform a fill site audit

Utilising either PowerShell, Central Admin or a tool – Get a full overview of the SharePoint 2010 environment. All web applications, site collections, permissions, services, topologies etc. This should all be in your checklist. The reason for doing this is to ensure your new SharePoint 2013 environment is ready and capable to host your previous SharePoint 2010 content.

Build the new environment

Installation

Prerequisite installation
Manual installations .netfx 3.5

Windows Server 2012 R2 ISO image mounted followed by running the following command through command prompt using elevated rights.

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs

Add the Windows Features Offline:

Completed through PowerShell using elevated rights.

Import-Module ServerManager

Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer –Source D:\sources\sxs

Offline SharePoint Prerequisites installation:

Completed through PowerShell using elevated rights.

$SharePoint2013Path = “C:\Installs\SPInstall”

 Start-Process “$SharePoint2013Path\PrerequisiteInstaller.exe” –ArgumentList “/SQLNCli:$SharePoint2013Path\PrerequisiteInstallerFiles\sqlncli.msi /IDFX:$SharePoint2013Path\PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu /IDFX11:$SharePoint2013Path\PrerequisiteInstallerFiles\MicrosoftIdentityExtensions-64.msi /Sync:$SharePoint2013Path\PrerequisiteInstallerFiles\Synchronization.msi /AppFabric:$SharePoint2013Path\PrerequisiteInstallerFiles\WindowsServerAppFabricSetup_x64.exe /KB2671763:$SharePoint2013Path\PrerequisiteInstallerFiles\AppFabric1.1-RTM-KB2671763-x64-ENU.exe /MSIPCClient:$SharePoint2013Path\PrerequisiteInstallerFiles\setup_msipc_x64.msi /WCFDataServices:$SharePoint2013Path\PrerequisiteInstallerFiles\WcfDataServices.exe”

Issues experienced during Prerequisite installation and Resolutions applied

Issue 1:

The tool was unable to install Application Server Role, Web Server (IIS) Role.

“C:\Windows\system32\ServerManagerCmd.exe”

In the Windows\System32 directory ServerManagerCMD.exe doesn’t exist

ServerManager.exe, copied it, renamed it to ServerManagerCMD.exe and copied to Windows\System32

Reran Configuration which allowed to continue

Issue 2:

Appfabric installation failed because installer MSI returned with error code:1603

Append the following path to PSModulePath entry in the environment variables

%SYSTEMROOT%\System32\WindowsPowerShell\v1.0

  • My Computer, Properties
  • System page, Advanced System Settings
  • Advanced tab, Environment Variables
  • Remove the PSModulePath entry from the ‘Environment Variables’ and re-run the installer. completed Prerequisite installation successfully,

SharePoint Installation

SQL Alias Configuration:

 Performed on the Web Front End and Application Server

– Open CLICONFIG.exe from C:\Windows\System32\cliconfg.exe (64 bit version of cliconfig.exe)

– Enable TCP/IP under general tab

Content Databases SharePoint 2013

– Click on Alias Tab

– Type Current SQL Server Name in the Alias Name field

– Type Current SQL Server Name in the Server field (see screenshot below. In your case SQL Alias and SQL Server name is the same)

Edit Network Library Configuration

Create a DNS entry to point to the Database SQL Alias

Installation Wizard Walkthrough – First Server

Microsoft SharePoint 2013 Product Key

Microsoft SharePoint Server 2013 Terms and Conditions

Microsoft SharePoint Server 2013 Server Type

Select Complete installation

Microsoft SharePoint Server 2013 File Location Setup

Change the file location to an alternative location other than the system drive.

Microsoft SharePoint Server 2013 Installation Progress

Run Configuration Wizard To complete configuration of your server, you must run the SharePoint Products Configuration Wizard.

SharePoint Products Configuration Wizard

SharePoint Products Configuration Wizard Connect to an existing serverfarm

Create a new server farm

SharePoint Config Wizard Specify Config Database

Add the SharePoint Farm account.

SharePoint Products Configuration Wizard port selection

Specify a port number that is not being used by something else. Random port numbers are for n00bs

Completing the SharePoint Products configuration wizard

SharePoint Products Configuration Wizard

Moment of truth, if anything fails here we missed a step along the way

SharePoint Products Configuration Wizard Successful

Success! If you don’t see this screen, read the log file and find the issues to fix.

Disableloopbackcheck

Completed through Registry

HKLM\System\CurrentControlSet\Control\Lsa

Add new DWORD DisableLoopBackCheck and set value of 1

Disableloopbackcheck registry

Services running on the Web Front End and Application Server:

SharePoint Central Administration servers

Installation Wizard Walkthrough – Additional Servers

SharePoint Products Configuration Wizard Additional servers

SharePoint Products Configuration Wizard reset during config prompt

SharePoint Products Configuration Wizard connect to existing farm

SharePoint Products Configuration Wizard database settings

Specify the new SQL database server and the new SharePoint 2013 SharePoint Config DB to join the newly created SharePoint 2013 environment.

SharePoint Products Configuration Wizard security settings

SharePoint Products Configuration Wizard advanced settings


SharePoint Products Configuration Wizard Configuration Successful

 Disableloopbackcheck Repeated on additional servers

Additional Servers disableloopbackcheck

SharePoint Service Pack 1 “KB2880552” Installation

SharePoint Service Pack 1 “KB2880552” Installation

SharePoint Service Pack 1 “KB2880552” Installation

Run Configuration Wizard on both servers to apply settings to configuration database

SharePoint Configuration Wizard complete

SharePoint Configuration Wizard complete

SharePoint Configuration Wizard complete

Register Service Accounts

Register SharePoint 2013 Service Accounts

Service Application Installation & Configuration

App Management Service

New App Management Service SharePoint 2013

New App Management Service SharePoint 2013

Business Data Connectivity Service

New Business data connectivity Service SharePoint 2013

New Business data connectivity Service SharePoint 2013

Machine Translation Service Application

New Machine Translation Service Service SharePoint 2013

New Machine Translation Service Service SharePoint 2013

Managed Metadata Service

New Managed Metadata Service Service SharePoint 2013

New Managed Metadata Service Service SharePoint 2013

Search Service Application

New Search Service Service SharePoint 2013

New Search Service Service SharePoint 2013

New Search Service Service SharePoint 2013

New Search Service Service SharePoint 2013

Secure Store Service Application

New Secure Store Service SharePoint 2013

New Secure Store Service SharePoint 2013

User Profile Service Application

New User Profile Service SharePoint 2013

New User Profile Service SharePoint 2013

New User Profile Service SharePoint 2013

New User Profile Service SharePoint 2013

New User Profile Service SharePoint 2013

New User Profile Service SharePoint 2013

Don’t user yammer …. It really shouldn’t be recommended and we recommend rather not.

Word Automation Service Application

New Word Automation Service SharePoint 2013

New Word Automation Service SharePoint 2013

Work Management Service Application

New Work Management Service SharePoint 2013

Service Application Summary

Service Application Summary SharePoint 2013

UPS Service

Create MySite Host Site Collection

UPS Service SharePoint 2013

New permission Policy Created for Mysite Web Application

UPS Service SharePoint 2013

Permission set for MySite policy

UPS Service SharePoint 2013

Users Assigned to MySite Policy

UPS Service SharePoint 2013

Self-Site Creation Configuration

Self Site Creation SharePoint 2013

Migrate the content

These steps are based off a content detach attach method for migrating SharePoint 2010 to 2013, which is really more a content backup and restore method. These steps are thoroughly covered in the following Microsoft article and this great Code Project article.

First things first, we need to test the content databases to see if they have issues. To do this perform the following actions on the SharePoint 2013 Farm.

  1. Create a backup of the 2010 SharePoint content database
  2. Create a new web application in SharePoint 2013 to house the content database. In this example we use http://migtest
  3. Restore the backup to the 2013 SharePoint Farm via the SQL instance
  4. Test the content database

Test-SPContentDatabase –name “SP2013_MigTest” -ServerInstance “ServerName” -WebApplication http://migtest

Troubleshoot database upgrade issues here

  1. Mount-SPContentDatabase “SP2013_MigTest” -DatabaseServer “ServerName” -WebApplication http://migtest

Content Database Settings

Leave a Reply

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

*