Skip to main content

Migration and Up Gradation Approach for SharePoint 2010 Portal to 2013 or 2016




Migration Options

·        Database Attach (Recommended)
o   Improved over SP2010 database attach
o   2010 –> 2013
·        In-Place no longer supported
·        Third Party Tool
o   Any version -> Any version

Database Attach upgrade approach is very standard and recommended for migration from SharePoint 2010 to SharePoint 2013. We follow this approach though out this article.
                                                                                                                                                                  

Database attach upgrade approach



 


Prepare for the Up gradation
Ø Investigate existing farm and Gather Information
·         Gather Settings
§  Alternate Access Mapping           
·         (intranet.heartwareinc.com)
§  Authentication Providers and Authentication Mode
§  Incoming and Outgoing e-mail settings
·         From central administration
§  Customization
·         All WSPs [Web parts, workflows, user controls, Master pages, CSS and other deployable]
[Note: Based on the custom solutions it may require to upgrade the codebase compatible to SharePoint 2013.]
·         3rd party tools used
§  Certificates
·         Any SSL or other certificate from central administration site
·         Gather Environment Information
§  Number of Sites
§  Number of Databases
·         Web application database
·         SharePoint Service application database
·         LOB application database
§  Number of Users
·         Clean up
§  Check and repair all database consistency error
§  Turn Off Web analytics Service application


Ø Prepare SharePoint 2013 Farm
·         Install the Software
·         Configure Service Applications
·         Configure Farm settings

Upgrade Databases
Following database types can be upgraded to SharePoint 2013 Products.
ü  Content Databases
o   Content Databases including My Sites (WSS_Content_ID)
ü  Service Application Databases
o   Business data connectivity
o   Manage Metadata Service
o   Performance Point Service
o   Secure Store Service
o   Search Service Application
o   User Profile Service Application


Ø Copy or Backup Content Databases
Ø Upgrade Service application database

Use Windows PowerShell cmdlets to create new service applications and upgrade the service application databases. You must also create proxies for the upgraded service applications and add the new service application proxies to the default proxy group.

Ø Create Web applications and Deploy the customization
·         Create and configure web application
§  It is not required to create site collection in it because upgrade approach will automatically add new site collections in it.
·         Deploy Customization
§  Solution packages
§  Custom site definitions
§  Web parts
§  Web services
§  Workflow
§  Solutions
§  Web.config settings
§  And others

Note: This may require code upgrade to support SharePoint 2013.

Ø Upgrade Content Databases
·         Use the Mount-SPContentDatabase cmdlet in Windows PowerShell to upgrade the databases.

Upgrade Sites
Ø Run site collection health checks
Before upgrading, site collection administrators can use the site collection health checker to identify and address potential issues in their site collections. Health checks are also run automatically before upgrade.
Ø Create an upgrade evaluation site collection

Site collection administrators can also request an upgrade evaluation site collection – a separate copy of the site collection upgraded to the new user interface. This site is used to preview the new user interface so that the administrator can address issues before upgrading the site collection.

Ø Upgrade a site collection
            After verifying that the site is ready, site collection administrators can upgrade their site collection to the new user interface.


Note: For My Sites, when you are ready to upgrade them, upgrade the My Site host site collection before allowing user access to their My Sites. When users browse to their My Sites after the My Site host is upgraded, their site collections are upgraded automatically.

Comments

Post a Comment

Popular posts from this blog

How to deal with SharePoint 2010 exception "An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error"

Scenario: You receive the below exception when you try to logon to a site that has been configured to use Claims Based Authentication with a custom membership provider using FBA credentials: Event ID from Event Log  - 8306 An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.. Explanation: This error started to appear in our QA environment which does not have Visual Studio installed. I have tried starting the service "Claims to Windows Token Service" but that did not help either. I have made sure that all config...
Post a Comment
Read more

Custom Form Base Login Web Part With Sharepoint 2010

In my  Last Post , I talked about creating a Form based authentication web application with Active Directory LDAP. After implementing that you have surely noticed that, when you try to sign in after creating a site collection from FBA web application, you get the following sign in page: Surely, it does not look pretty at all. So, you might want to change this default login page. In order to do this, first let us create an empty SharePoint project in Visual Studio 2010. After that, add an application page by right click-selecting “Add New Item” and you will get like the following window in Solution Explorer: Notice that, when you add any application page to your project, Visual Studio automatically creates a Layouts  folder. To keep things simple enough for your understanding, you may keep your application page under a folder where you might name it as same as your project like the figure above. Now, add a reference for  Microsoft.SharePoint.IdentityModel...
2 comments
Read more

Migrating from Skype for Business to Microsoft Teams: A Step-by-Step Guide

Do you still use Skype for Business to meet the communication and collaboration needs of your business? If so, now is the perfect time to think about switching to Microsoft Teams, a cutting-edge platform with cutting-edge capabilities and seamless connectivity with other Microsoft services. But if you're unfamiliar with the procedure, switching to a new platform can seem like a difficult task. I'll walk you through the process of switching from Skype for Business to Microsoft Teams in this article. Plan the migration in Step 1 You must make a plan before you start the relocation procedure. Set a deadline, make a list of all the Skype for Business capabilities you presently use, and choose whether to migrate gradually or all at once. Step 2: Set up your surroundings. Make sure your network and infrastructure fulfil Microsoft Teams' standards. Upgrades to your hardware, software, and licences might be necessary. Additionally, confirm that you have the right permissions to ca...
Post a Comment
Read more