SharePoint Upgrade, reel life experience, best practices

1. SharePoint Upgrade, reel life experience, best practices #SPSBE02 Knut Relbe-Moe April 26th, 2014

2. Thanks to our sponsors! Gold Silver

3. Knut Relbe-Moe Senior Solution Architect Technical Lead SharePoint Steria AS Oslo Norway 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. • 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 25.000 users. • Worked with automating the installation and configuration of SharePoint. Contact @sharePTkarm Email: knutrelbemoe@outlook.com Blog: www.sharepointblog.no Skype: shareptkarm Mobile: 0047-98224609

4. I’mproud to work for:

5. About this session Technet guide What can be upgraded? What about upgrade from 2007? Upgrade process – different options Step by step process on upgrading to SharePoint 2013 How to upgrade your custom solutions from 2010 to 2013. How to upgrade from 2013 to 2013 SP1

6. Upgrade? • 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 Somefacts: Or Migrate?

7. Technet

8. So whatabouttechnet? 01.06.2013

9. Onlyone problem Technetdoesn’t tell youwhat to do when it doesn’tgo like planed…

10. What can be upgraded?

11. 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)

12. What about upgrade from 2007?

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

14. Upgrade path MOSS 2007 SharePoint 2010 SharePoint 2013

15. Anotheroption • If youdon’twant to gotrough SharePoint 2010, it’s plenty migrationtoolsthat support migration from all theway back to 2003/2007. • Under i Have linkedsomeoptions (it’smany more), youneed to look at thedifferences, and choosetheonewhich is right for you. This canchange from project to projectand thetaskyou have in front ofyou.

16. Upgrade process – different options

17. Upgrade process – farm solutions Analyze todays environment Setup 2013 farm Attach database to SQL Test database on SP 2013 Deploy 2010 solutions Copy databases from SP 2010 Clean up the 2010 environment Deployupgraded 2013 solutions Upgrade Site Collections to 2013 Uninstall 2010 solutions Miscconfig scripts Mount database on SP 2013 Migrate to claimsif not already done

18. Upgrade process – moving to the cloud – best practice Couldyour 2010 code be replaced by standard functionality Great, use standard functionality Yes No Rewritethecode to appmodel Canyou do it withtheappmodel Yes No Rewritethecode to 2013 solution Think howyoucanmove it to theappmodelanyways

19. 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 @adrianfiechterhttp://tinyurl.com/oq87nnd

20. Iterative upgrade process You can also take a look at Tobias Zimmergrens iterative upgrade process wheel. For more info about this go to his site: http://t.co/LMdhQh4wnD Tobias Zimmergren Entrepreneur / Microsoft MVP / Technology Evangelist @zimmergren www.zimmergren.net

21. Step by step process on upgrading to SharePoint 2013

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

23. Step by step process on upgrading to SharePoint 2013 Add and deploy any required O14 custom solutions in your SharePoint 2013 farm

24. Step by step process on upgrading to SharePoint 2013 Backup and restore the SharePoint 2010 content database to your SQL Server hosting SharePoint 2013 farm.

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

26. Step by step process on upgrading to SharePoint 2013 Attach the content database to the desired web application using Mount-SPContentDatabasecmdlet.

27. Step by step process on upgrading to SharePoint 2013 After successfully mounting the content database to web application, the site should be accessible in 14 mode.

28. Step by step process on upgrading to SharePoint 2013 Run Get-SPSite -contentdatabase SP2010_24_Test_Content_Portal -Limit All | Upgrade-SPSite -VersionUpgrade. To perform visual upgrade.

29. Step by stepprocessonupgrading to SharePoint 2013 Migrate to claims if you didn’t do it in the 2010 environment

30. Step by stepprocessonupgrading to SharePoint 2013 Upgrade SP2010 code to SP2013 Deploy of SP2013 WSP-Files

31. Step by stepprocessonupgradingto SharePoint 2013 Your site collection should now be accessible in the 15 mode along with all new capabilities enabled in the farm and for the hosting web application such as Social and Office Web Apps.

32. Upgrade your Custom Solutions

33. Getthe latest versionofvisual studio developertoolswith Web Platform Installer

34. Open yourprojects in Visual Studio You’ll get a dialog saying “Do you want to upgrade <project name> to a SharePoint 2013 solution? Klick Yes. Once the upgrade is complete, the solution can’t be deployed to SharePoint 2010. Do you want to continue?”

35. The migration report tellsyouhowtheupgradewent. Hopefully there will be no Errors, only warnings and Messages

36. Checkouttheassemblyreferences in yourprojectthatarepointing to any SharePoint assemblies Note thattheassemblies have automaticallybeenupdated to thecorrectversionofthe SharePoint 2013 assembly.

37. Othercodeupdates • //images folder Replace all the paths in your project Path to the images folder Path to the layouts folder Path to the controltemplate folder • //layouts folder • //controltemplates folder

38. Demo time: Content upgrade and code upgrade

39. Demo – summary • Createweb application in 2013 farm • Set Source DB-To Read Only (in 2010 farm) • Backupexistingcontent DB. (in 2010 farm) • Restorecontent db to new SQL Server • Test upgradeprocessusing:Test-SPContentDatabase -nameContentDBName -webapplication http:/mydemo > c:\autid.txt • Review log files for errors/upgradeblockers • RunMount-SPContentDatabasecommand to upgrade DB (DB is updated but not site collections) • To upgradethevisualexperience to 2013 on all sitecollections run thefollowingcommand: • Get-SPSite -contentdatabaseContentDBName -Limit All | Upgrade-SPSite –VersionUpgrade • I have nowshownyouhow to upgradeyourcustomsolutions to 2013. • But for eachsolutionyou have to consider, shall I just convertthecode, or shall I rewritethecodecompletely so it wouldalsoworkwiththenew SharePoint App Model

40. Typicalerrors • LegacyUIDetected • MissingFeature • MissingSetupFile • MissingAssembly • Configuration • Look for UpgradeBlocking: False • Great!

41. Upgrading SharePoint 2013 To: SharePoint 2013 SP1

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

43. Upgrade to 2013 Service Pack 1 1. Patch SharePoint 2013 Farm to SP1 –Microsoft just republished the SP1 Patch. Until then you have to reinstall the server 2. Install SharePoint 2013 service-pack 1 on all servers if not already done. Without SP1 we can’t run Windows 2012 R2 with SharePoint 2013 (and be supported at least). 3. Next, complete the upgrade with psconfig/config-wizard to complete the upgrade process. If a server hasn’t been fully patched done yet you’ll see a warning about software version mismatches.

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

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

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 • The compatibility check will point out the Hyper-V device drivers might not work after the upgrade. We don’t mind. If you need to restart for any reason, setup will insist you do that 1st too here. • If your server has 4 million apps installed, these may cause problems with the upgrade. As this is my “production” environment, there is just SharePoint + prerequisites so this is what I see:

48. Running Setup & Upgrading Windows 2012 to R2 • Once passed the compatibility checks, Windows setup should basically keep itself busy for the rest of the process without any interruption needed 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 fixit! • STS is likely broken and the cache-cluster probably needs a reboot to get it working again. • Fix the cache cluster by removing and then re-adding each cache server in turn • For STS errors, a simple psconfig upgrade command per failing server (psconfig -cmd upgrade -inplace b2b) should fix that problem up. • If not run the following commands to rebuild your environment psconfig -cmd services install psconfig -cmdinstallfeatures psconfig -cmdsecureresources