1. Best practices on upgrading SharePoint from 2007/2010 to
2013
#SPSDXB
Knut Relbe-Moe
May 17th, 2014

2. Thanks to our sponsors!

3. Knut Relbe-Moe
Senior Solution Architect
Technical Lead SharePoint
Steria AS
Oslo, Norway
Microsoft Certified Trainer
Contact
@sharePTkarm
Email: knutrelbemoe@outlook.com
Blog: www.sharepointblog.no
Skype: shareptkarm
Mobile: 0047-98224609
My Experience:
 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 2013.
 Works as a Lead Architect and advisor creating SharePoint Farm
architecture/infrastructure on many projects. With up to 25.000
users.
 Worked with automating the installation and configuration of
SharePoint.

4. I’m proud to work for:

5. About this session

6.  SharePoint doesn’t support upgrading
straight from MOSS 2007 to SharePoint
2013. You first have to go trough
SharePoint 2010.
 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

7. What can be upgraded?

8. What can be upgraded?

9. What about upgrade from
2007?

10. I have SharePoint 2007… Should I skip
2010?
 You can’t skip 2010, because SharePoint doesn’t support upgrading
straight from MOSS 2007 to SharePoint 2010

11. Upgrade path

12. Another option

13. Upgrade process – different
options

14. Upgrade process – farm solutions
Analyze todays environment

15. Upgrade process – moving to the cloud
– best practice
Rewrite the code
to 2013 solution

16. Color Description
Blue Supporting 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 Fiechter
@adrianfiechter
http://tinyurl.com/oq87nnd

17. Iterative upgrade process
Tobias Zimmergren
Entrepreneur / Microsoft
MVP / Technology
Evangelist
@zimmergren
www.zimmergren.net
http://t.co/LMdhQh4wnD

18. Don’t forget the impact a
database upgrade can have
on your environment

19.  If you run on a old version of SQL server you should consider upgrading to a new one at the same time
as you upgrade the SharePoint environment
 If your database is not set up correct you can get great effect on your environment by reinstalling or
upgrading the database.
 Always use SQL Alias when you install SharePoint, then it will be easy to move or upgrade your
environment.
 Process is very simple:
Don’t forget the value of upgrading your SQL server

20. Databases require upgrade or
not supported.
Severity 1 - Error
Category Configuration
Explanation The following
databases require upgrade
because their versions are older
than the backwards compatible
range:

21. Step by step process on upgrading
to SharePoint 2013

22.  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 http://server/sitecollection
 Deploy of SP2013 WSP-Files
Step by step process on upgrading to SharePoint 2013

23. Step by step process on upgrading to SharePoint 2013

24. Step by step process on upgrading to SharePoint 2013

25.  Run Test-
SPContentDatabase cmdlet to
identify missing components along
with potential errors and related
warnings.
 Check the upgrade log and deploy
any missing components and re run
the cmdlet until no errors returned
Step by step process on upgrading to SharePoint 2013

26. Step by step process on upgrading to SharePoint 2013

27. Step by step process on upgrading to SharePoint 2013

28. Step by step process on upgrading to SharePoint 2013

29.  Migrate to claims if you didn’t
do it in the 2010 environment
Step by step process on upgrading to SharePoint 2013

30. Step by step process on upgrading to SharePoint 2013

31. Step by step process on upgrading to SharePoint 2013

32. Upgrade your Custom
Solutions

35.  The migration report tells you how the
upgrade went.

36. 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.

37.  Path to the images folder
 Path to the layouts folder
 Path to the controltemplate folder
Other code updates //images folder
//layouts folder
//controltemplates folder

38. Demo time: Content upgrade
and code upgrade

39. Demo – summary
 Create web application in 2013 farm
 Set Source DB-To Read Only (in 2010 farm)
 Backup existing content DB. (in 2010 farm)
 Restore content db to new SQL Server
 Test upgrade process using:
Test-SPContentDatabase -name ContentDBName -webapplication http:/mydemo > c:autid.txt
 Review log files for errors/upgrade blockers
 Run Mount-SPContentDatabase command to upgrade DB (DB is updated but not site
collections)
 To upgrade the visual experience to 2013 on all site collections run the following command:
 Get-SPSite -contentdatabase ContentDBName -Limit All | Upgrade-SPSite –
VersionUpgrade
 I have now shown you how to upgrade your custom solutions to 2013.
 But for each solution you have to consider, shall I just convert the code, or shall I rewrite the
code completely so it would also work with the new SharePoint App Model

40. Typical errors
False
Great!

41. Upgrading SharePoint 2013
To: SharePoint 2013 SP1

42. 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:

43. Upgrade to 2013 Service Pack 1

44. 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.
Prepare Windows 2012 R2 ISO
44

45. Run setup, accept the UAC elevation and begin the
install. Get the updates
45

46. 46
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.

47. Windows Upgrade Compatibility Check
47

48. Running Setup & Upgrading Windows 2012 to R2
48
Setup will restart
a couple of times.

49. Verify SharePoint Functionality & Fixing Errors
 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:

50. How to fix it!
psconfig -cmd services install
psconfig -cmd installfeatures
psconfig -cmd secureresources

51. 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

53. Upgrade to 2013 Service Pack 1 update

54. Link to the download of SP1 update
KB Download
KB Download
KB Download
KB Download

56. Scripted install of cumulative updates/Service Pack 1
To save a lot of time during installation of cumulative updates / service pack, take a look
at Russ Maxwell powershell script to script the installation. This will save you a lot of time.
http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-
cumulative-update-takes-5-hours-to-install.aspx
This script reduces the patch time from 5 hours to approximately 30 minutes
Another note – Best practice on install

57. About the script
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

58. Drop the SharePoint cumulative/sp1 update in the same folder as the script.
For instance C:scripts
How to run the script
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!

59. How to succeed upgrading
SharePoint

60. How to succeed upgrading SharePoint

61. How to succeed upgrading SharePoint

62. Another option:

63. Different migration tools

65. Summary

66. Thanks to

67. My contact details:
Twitter: @sharePTkarm
Email: knutrelbemoe@outlook.com /
kirm@steria.no
Blogg: http://www.sharepointblog.no
Skype shareptkarm
Mobile: 0047-98224609
Linkedin: http://no.linkedin.com/pub/k
nut-relbe-moe/2/70b/6a/

68. Thank you!