DB Migration from sharepoint 2010 to sharepoint 2013

1. Use Farm Admin Account For the Installation

2. Check the Windows 2008 R2 SP1 (using Winver in the RunPrompt) or windows2012 server

3. Run PreUpgradechecker.(Present in the SharePoint 2013 Installation Wizard)

Click on Finish on Prerequisites and it will Restart your computer.

4. Get the 4 KB’s from the following link and Install one-by-one

http://technet.microsoft.com/en-us/library/ee805948.aspx

Install the KB 2554876

Install KB 2708075

Install KB 2759112

Install the KB 2765317

5. 5. Install SharePoint

Run SharePoint set up

Right Click on Prerequisites and click on Run as administrator

Right Click Run As Administrator

6.Configure SharePoint Farm Using PowerShell

http://habaneroconsulting.com/insights/Automating-the-SharePoint-2013-installation-and-creating-a-farm-with-PowerShell

############################################################

# Configure-SPFarm.ps1

# Configures a SharePoint 2013 farm with:

# Configuration Database

# Central Administration web application and site

############################################################

# Service accounts

$DOMAIN = "Domain"

$accounts = @{}

$accounts.Add("SPFarm", @{"username" = "user account"; "password" = "pwd"})

$accounts.Add("SPWebApp", @{"username" = "user account"; "password" = "pwd"})

$accounts.Add("SPSvcApp", @{"username" = "user account"; "password" = "pwd"})

Foreach ($account in $accounts.keys) {

$accounts.$account.Add(`

"credential", `

(New-Object System.Management.Automation.PSCredential ($DOMAIN + "\" + $accounts.$account.username), `

(ConvertTo-SecureString -String $accounts.$account.password -AsPlainText -Force)))

}

# SQL Server client alias

#This is the name of SQL Alias

$AliasName = "SPFarmAlias"

#This is the name of your SQL server (the actual name!)

# In this case we're using the current computer name as we are assuming #SharePoint and SQL are on the same server

# Change this if this isn't the case in your environment!

$ServerName = $env:devshpt31

#These are the two Registry locations for the SQL Alias locations

$x86 = "HKLM:\Software\Microsoft\MSSQLServer\Client\ConnectTo"

$x64 = "HKLM:\Software\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo"

#We're going to see if the ConnectTo key already exists, and create it if it doesn't.

if ((test-path -path $x86) -ne $True)

{

write-host "$x86 doesn't exist"

New-Item $x86

}

if ((test-path -path $x64) -ne $True)

{

write-host "$x64 doesn't exist"

New-Item $x64

}

#Adding the extra "fluff" to tell the machine what type of alias it is

$TCPAlias = ("DBMSSOCN," + $ServerName)

#Creating our TCP/IP Aliases

New-ItemProperty -Path $x86 -Name $AliasName -PropertyType String -Value $TCPAlias

New-ItemProperty -Path $x64 -Name $AliasName -PropertyType String -Value $TCPAlias

# Open cliconfig to verify the aliases

Start-Process C:\Windows\System32\cliconfg.exe

Start-Process C:\Windows\SysWOW64\cliconfg.exe

# Farm configuration

$configPassphrase = "SharePoint 2013 Intranet!"

$s_configPassphrase = (ConvertTo-SecureString -String $configPassphrase -AsPlainText -force)

$serverDB = $AliasName

$dbConfig = "SP2013_Configuration"

$dbCentralAdmin = "SP2013_Content_CentralAdministration"

$caPort = 55555

$caAuthProvider = "NTLM"

########################################

# Create the farm

Add-PSSnapin Microsoft.SharePoint.PowerShell

Write-Output "Creating the configuration database $dbConfig"

New-SPConfigurationDatabase `

-DatabaseName $dbConfig `

-DatabaseServer $serverDB `

-AdministrationContentDatabaseName $dbCentralAdmin `

-Passphrase $s_configPassphrase `

-FarmCredentials $accounts.SPFarm.credential

# Check to make sure the farm exists and is running. if not, end the script

$farm = Get-SPFarm

if (!$farm -or $farm.Status -ne "Online") {

Write-Output "Farm was not created or is not running"

exit

}

Write-Output "Create the Central Administration site on port $caPort"

New-SPCentralAdministration `

-Port $caPort `

-WindowsAuthProvider $caAuthProvider

# Perform the config wizard tasks

Write-Output "Install Help Collections"

Install-SPHelpCollection -All

Write-Output "Initialize security"

Initialize-SPResourceSecurity

Write-Output "Install services"

Install-SPService

Write-Output "Register features"

Install-SPFeature -AllExistingFeatures

Write-Output "Install Application Content"

Install-SPApplicationContent

# Add managed accounts

Write-Output "Creating managed accounts ..."

New-SPManagedAccount -credential $accounts.SPWebApp.credential

New-SPManagedAccount -credential $accounts.SPSvcApp.credential

New-SPManagedAccount -credential $accounts.SPCrawl.credential

#Start Central Administration

Write-Output "Starting Central Administration"

& 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN\psconfigui.exe' -cmd showcentraladmin

Write-Output "Farm build complete."

7.Service Applications Configuration using the Powershell

http://technet.microsoft.com/en-us/library/jj839719.aspx

Start the service instances

The following procedures start the service instances.

To start service application instances from Central Administration

I. Start SharePoint 2013 Central Administration.

o For Windows Server 2008 R2:

§ Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.

o For Windows Server 2012:

§ On the Start screen, click SharePoint 2013 Central Administration.

If SharePoint 2013 Central Administration is not on the Start screen:

§ Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.

For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.

II. In SharePoint 2013 Central Administration, on the Application Management page, in the Service Applications section, click Manage Services on Server.

III. Next to the Business Data Connectivity service, click Start.

IV. Next to the Managed Metadata Web Service, click Start.

V. Next to the PerformancePoint Services service, click Start.

VI. Next to the Secure Store Service, click Start.

VII. Next to the User Profile Service, click Start.

8. The Search service instance must be started by using Windows PowerShell because you cannot start it from Central Administration unless a Search Service application already exists.
To start the Search service instance by using Windows PowerShell

Add-PSSnapin Microsoft.SharePoint.Powershell

$SearchInst = Get-SPEnterpriseSearchServiceInstance

# Stores the identity for the Search service instance on this server as a variable

Start-SPServiceInstance $SearchInst

9. start the service instances using power shell commands follow the below commands

# Starts the service instance

Add-PSSnapin Microsoft.SharePoint.Powershell

#Upgrade Secure Store Service

$applicationPool = Get-SPServiceApplicationPool -Identity "SharePoint Web Services System"

$sss = New-SPSecureStoreServiceApplication -Name 'Secure Store Service' -ApplicationPool $applicationPool -DatabaseName 'Secure_Store_Service_DB' –AuditingEnabled

$sssp = New-SPSecureStoreServiceApplicationProxy -Name SPSecureStoreProxy -ServiceApplication $sss –DefaultProxyGroup

Update-SPSecureStoreMasterKey -Passphrase "Republ1c1" -ServiceApplicationProxy $sssp

Start-Sleep 5

Update-SPSecureStoreApplicationServerKey -Passphrase "Republ1c1" -ServiceApplicationProxy $sssp

Start-Sleep 5

#Upgrade BDS Service