Bestpractices on upgrading SharePoint from 2007/2010 to 2013 Knut Relbe-Moe Norway, – April 16 th /17 th, 2014

Senior Solution Architect Technical Lead SharePoint Steria AS Oslo Norway / Skype: knutik.net | mobile:

About me  SharePoint evangelist, mentor, speaker  Old developer, turned Architect / ITPro  Have worked with SharePoint since the 2003 version.  Worked with several clients upgrading their solution from 2007/2010 to  Worked with several clients upgrading from 2013 to 2013 SP1  Works as a Lead Architect and advisor creating SharePoint Farm architecture/infrastructure on many projects. With up to users.  Worked with automating the installation and configuration of SharePoint. My Experience

Vlad Catrinescu Matthias​ Einig Jasjit Chopra​ Jon​ Manderville (England) Paul Gallagher Stefan Bauer Raphael Londner

 SharePoint doesn’t support upgrading straight from MOSS 2007 to SharePoint You first have to go trough SharePoint  SharePoint 2013 doesn’t support «In-Place upgrade». Which is a good thing!  SharePoint 2013 supports «database attach» which arrived with SharePoint 2010  SharePoint 2013 supports upgrade of some of the Service Applications

What can be upgraded?

 SharePoint Web applications/content  Custom Code  Service Applications  Search administration  Business Data Connectivity  Managed Metadata  PerformancePoint  Secure Store  User Profile (Profile, Social, and Sync databases)

What about upgrade from 2007?

 You can’t skip 2010, because SharePoint doesn’t support upgrading straight from MOSS 2007 to SharePoint 2010

 Prepare and gather info  Clean up the 2010 environment (Remove faulty features, solutions that should not be used anymore)  Build servers / install 2013 SharePoint  Backup and upgrade of service application database  Upgrade your SP 2010 code to SP 2013  Backup and upgrade of content databases  Deploy 2010 WSP files to the 14 – hive in SP 2013  Test-SPContentDatabase – Correct any mistakes that occurs  Mount-SPContentDatabase – Probably fails  Migrate to claims  Upgrade site collection – Upgrade SPSite  Deploy of SP2013 WSP-Files

Step by step process on upgrading to SharePoint 2013

Analyze todays environment

Rewrite the code to 2013 solution

ColorDescription BlueSupporting items for your decision Orange Solution is not cloud ready and can't be used with Office 365. So it has to be farm solution. Yellow Yellow: Can't be used with Office 365 multitenant. Could work with Office 365 dedicated (please verify it with Microsoft before starting to build it). Green Solution is cloud ready and can be used with Office 365 The decision chart is based on the idea, that you separate each use case and you do an evaluation for each of them. It could be that your solution is a mix of apps, sandbox solutions and a client application used to deploy and configure it. Adrian

Tobias Zimmergren Entrepreneur / Microsoft MVP / Technology

Upgrade your Custom Solutions

 Check out the assembly references in your project that are pointing to any SharePoint assemblies  Note that the assemblies have automatically been updated to the correct version of the SharePoint 2013 assembly.

Other code updates //images folder //layouts folder //controltemplates folder

Demo time: Content upgrade and code upgrade

1. Install SharePoint 2013 service-pack 1 on all servers. 2. Install SharePoint 2013 Language pack service pack 1 on all servers 3. Complete the upgrade with psconfig/config-wizard to complete on all servers 4. Install Windows 2012 R2 on all servers Alternative 1:

Windows 2012 is perfectly capable of mounting local ISO files as a virtual disc. Click the ISO, then run setup when the ISO is mounted. 43

44

45 Make sure you install the GUI Windows only. SharePoint doesn’t support server core. Make sure you select “upgrade” as it’s pretty much the entire point of this article/process.

46

47 Setup will restart a couple of times.

 As mentioned earlier, the upgrade to Windows 2012 R2 can leave SharePoint rather broken by default.  Specifically the Security Token Service can break because of a problem with then SharePoint farm certificate.  Click on “view these issues” and you might see something like this:

49 psconfig -cmd services install psconfig -cmd installfeatures psconfig -cmd secureresources

1.Reinstall the Servers. 2.Install Windows 2012 R2 on all servers 3.Install SharePoint 2013 service-pack 1 on all servers. 4.Install SharePoint 2013 Language pack service pack 1 on all servers 5.Join the SP1 servers to the farm 6.Complete the upgrade with psconfig/config-wizard to complete on all servers 7.Remove the old 2013 servers from the farm

1. Disable the IISAdmin and SPTimerV4 service 2. Shut down IIS Admin and Timer Services if they are running 3. Give you the option to Pause the Search Service Application (see search notes below) 4. Stop Search Services (see search notes below) 5. Install the patch in passive mode (No user interaction required but will witness the patch install in the UI) Note: Power Shell should remain open in the background while patch is running 6. Upon completion of the patch, the Power Shell script, services in step 1 are set to Automatic 7. Starts up IIS Admin and Timer Services 8. Starts up Search services 9. Resume the Search Service Application if it was paused 10. Finally, the script will display the Start Time and End Time for patch install

Drop the SharePoint cumulative/sp1 update in the same folder as the script. For instance C:\scripts Important: Only one update should be placed here and the file extension should be.exe. Finally, run the script from c:\scripts using SharePoint Management Shell. Example Screenshot during patching it looks like: Example Screenshot – Patching is complete!

/ Blogg: Skypeknutik.net Mobile: Linkedin: moe/2/70b/6a/