SharePoint 2013 Visual Upgrade and Version Upgrade after Migration using PowerShell

Here we look how to perform visual upgrade of Site Collections after upgrade to SharePoint 2013. Visual upgrade is necessary after migration process to get new visual look of SharePoint 2013. Version upgrade is necessary to change it to 15 Hive, means compatibility level to current version SP 2013.
Note: Deploy custom Master Pages, Custom Solution etc before you attach content database. No error will show while opening site.
First, attach your existing content DB to new web application by using cmdlet-
Mount-SPContentDatabase “DBName” -DatabaseServer “ServerName” -WebApplication http://sitename
To check current compatibility level of content-db which you have attached. 
Run  Get-spsite cmdlet
Latest upgraded site listed as compatibility level 14 hive.

Second, Test your Site by using Test-SPSite.
Test-SPSite http://server/sitecollection
you can avoid warnings, it will be good if you remove errors before upgrade process.
At last run upgrade cmdlet for Visual upgrade and also pass version upgrade parameter for current version compatibility level- 15 hive.

Upgrade-SPSite http://server/sitecollection –VersionUpgrade

Once 100% completed, you will have the SharePoint 2013 visuals throughout your site collection.

Note: We determine here that already converted classic based authentication to Claim Based Authentication.

• The Upgrade-SPSite cmdlet activates the upgrade process for the specified SPSite object. You can also use this cmdlet to resume failed upgrades. When you use this cmdlet to initiate upgrade on an SPSite object, the object can be either a build-to-build or version-to-version upgrade. By default, the Upgrade-SPSite cmdlet operates as a build-to-build upgrade. 
• -VersionUpgrade parameter, specifies to perform a version-to-version upgrade on the SPSite object. When this parameter is set, it internally triggers all available build-to-build actions that are associated with the current site collection operating mode. Version-to-version actions follow to bring site collections to the next site collection operating mode inclusive of all new build-to-build actions that are associated with the new site collection operating mode. When this parameter is not set, it triggers only available build-to-build upgrade actions that are associated with the current site collection operating mode. Reference https://technet.microsoft.com/  

On next post see how to upgrade Sharepoint site collection from  Site Settings page of site collection.

SharePoint 2013 Visual Upgrade and Version Upgrade after Migration using PowerShell

Here we look how to perform visual upgrade of Site Collections after upgrade to SharePoint 2013. Visual upgrade is necessary after migration process to get new visual look of SharePoint 2013. Version upgrade is necessary to change it to 15 Hive, means compatibility level to current version SP 2013.
Note: Deploy custom Master Pages, Custom Solution etc before you attach content database. No error will show while opening site.
First, attach your existing content DB to new web application by using cmdlet-
Mount-SPContentDatabase “DBName” -DatabaseServer “ServerName” -WebApplication http://sitename
To check current compatibility level of content-db which you have attached. 
Run  Get-spsite cmdlet
Latest upgraded site listed as compatibility level 14 hive.

Second, Test your Site by using Test-SPSite.
Test-SPSite http://server/sitecollection
you can avoid warnings, it will be good if you remove errors before upgrade process.
At last run upgrade cmdlet for Visual upgrade and also pass version upgrade parameter for current version compatibility level- 15 hive.

Upgrade-SPSite http://server/sitecollection –VersionUpgrade

Once 100% completed, you will have the SharePoint 2013 visuals throughout your site collection.

Note: We determine here that already converted classic based authentication to Claim Based Authentication.
The Upgrade-SPSite cmdlet activates the upgrade process for the specified SPSite object. You can also use this cmdlet to resume failed upgrades. When you use this cmdlet to initiate upgrade on an SPSite object, the object can be either a build-to-build or version-to-version upgrade. By default, the Upgrade-SPSite cmdlet operates as a build-to-build upgrade. 
-VersionUpgrade parameter

Specifies to perform a version-to-version upgrade on the SPSite object. When this parameter is set, it internally triggers all available build-to-build actions that are associated with the current site collection operating mode. Version-to-version actions follow to bring site collections to the next site collection operating mode inclusive of all new build-to-build actions that are associated with the new site collection operating mode. When this parameter is not set, it triggers only available build-to-build upgrade actions that are associated with the current site collection operating mode.
reference https://technet.microsoft.com/  

On next post see how to upgrade Sharepoint site collection from  Site Settings page of site collection.

Migrate SharePoint 2010 classic-mode web applications to SharePoint 2013 classic-mode web applications

In my last org task - Upgrade of SharePoint Server to SharePoint 2013 from SharePoint 2007 version, I found that  SharePoint 2013 default authentication method for web application is Claim based authentication and Windows Classic authentication method is deprecated in SharePoint 2013 release.

In SharePoint 2013, complete the following procedure to create a classic-mode web application, then migrate an existing SharePoint 2010 classic-mode Web application to SharePoint 2013 and at last convert an existing SharePoint 2010 classic-mode web application to a SharePoint 2013 web application that uses claims-based authentication.

First we will create a web application using PowerShell command because we cannot create web application having classic based authentication using central administration.

New-SPWebApplication -name "MySiteClassicAuthApp" -Port 100 

-ApplicationPool "MySiteClassicAuthAppPool"

-ApplicationPoolAccount(Get-SPManagedAccount "Domain\account")

Attach an existing content database of SharePoint 2010 version to our new 2013 web application, which we have already added in SQL Server before that we have to Test Content Database using “Test contentDB” powershell command for successful mount of content database.

     Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" 

       -WebApplication http://SiteName

 

Now detach a content database which was created while creating site.

Dismount-SPContentDatabase "<ContentdBName>"

Convert your SharePoint 2013 classic-mode web application to claims-based authentication - 

  Convert-SPWebApplication -Identity <yourWebAppUrl> 

         -To Claims

         -RetainPermissions [ -Force]

Retain permission property used to retain exiting permissions.

Note:

• If you not used -AuthenticationMethod parameter while creating New classic based auth web application then also by default classic based auth web app will be created.
• Account which your using have sufficient permission to perform activity in SQL and SharePoint.
• Convert-SPWebApplication converts the web application to claims-based authentication. You have to verify that the users can access the web application after you have converted it.
• You must use the content database GUID in this command instead of using the content database name, in case of multiple content databases that have the same name.
• To retrieve the GUID of the content database, run the Get-SPContentDatabase PowerShell cmdlet with no arguments.
• The Dismount-SPContentDatabase  detaches the content database from the web application, but it does not delete the content database from SQL Server. After detached, you cannot delete it by using Windows PowerShell 3.0. You can only remove it by using SQL Server tools. If you want to delete the content database from SQL Server while you detach it, use the Remove-SPContentDatabase instead.

Reference: http://technet.microsoft.com