1 / 37

Welcome To Upgrading to SharePoint 2013 Speaker: Shane Young Rackspace

Welcome To Upgrading to SharePoint 2013 Speaker: Shane Young Rackspace. Thanks to our Conference Hosts. #SPcincy2014 on Twitter @ sharepointcincy. Please express your thanks to our sponsors today for their supporting this event!. Who Am I?. Shane Young – Cincinnati, Ohio

nen
Download Presentation

Welcome To Upgrading to SharePoint 2013 Speaker: Shane Young Rackspace

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Welcome To Upgrading to SharePoint 2013 Speaker: Shane Young Rackspace

  2. Thanks to our Conference Hosts #SPcincy2014 on Twitter @sharepointcincy

  3. Please express your thanks to our sponsors today for their supporting this event!

  4. #SPcincy2014 on Twitter @sharepointcincy

  5. Who Am I? • Shane Young – Cincinnati, Ohio • SharePoint@Rackspace • SharePoint Server MVP longer than Todd • Consultant, Trainer, Writer, & Speaker • Shane.Young@Rackspace.com • Blog • http://msmvps.com/shane • SharePoint Consulting • http://sharepoint.Rackspace.com • Twitter @ShanesCows

  6. Agenda • Upgrade Methods • Upgrade Nuggets • Upgrade How to • Upgrade Demo

  7. Upgrade Survivor SharePoint 2007 Gradual Upgrade Database Attach Upgrade In-Place Upgrade

  8. Upgrade Survivor SharePoint 2010 Gradual Upgrade Database Attach Upgrade In-Place Upgrade

  9. Upgrade Survivor SharePoint 2013 Gradual Upgrade Database Attach Upgrade In-Place Upgrade

  10. Secret method? Buy a 3rd party tool 

  11. Supported Databases • All content databases • BCS • Managed Metadata • PerformancePoint • Secure store (need to know passphrase) • User Profile databases • Search administration (no index or property dbs)

  12. SharePoint 2010 and 2013 • They cannot exist on the same server • SharePoint 2010 databases must be RTM or later (no service pack required) • You probably need more hardware

  13. Quick notes • Add managed paths manually before attaching databases • Always upgrade database with root site collection first • Try to use same URLs • 14 = SharePoint 2010 • 15 = SharePoint 2013

  14. 2013 lets you create 2010 site collections • This is very important to note for your early testing • You can create it in 2010 and then upgrade it to 2013 • No database fuss • Lets you work out the basics in a very difficult environment to break

  15. Go deep on Office Web Apps • They are awesome and you need to use them in 2013 • Hardware is key – They must be on their own server with nothing else • Office Web Apps require you to be using Claims authentication to work • Read only is free – Edit requires a specific Office License (volume license)

  16. Authentication • Claims is dominant • Classic is left for the golden oldies station • Recommended to upgrade to 2013 and then convert to claims • 2 major changes

  17. Create and convert a Classic Web App • New-SPWebApplication -Name Upgrade -ApplicationPool "SharePoint App Pool" -AuthenticationMethod NTLM -Port 80 -URL http://upgrade.contoso.com • Get-SPWebApplication | Select URL, useclaimsauthentication • Convert-SPWebApplication -Identity "http://upgrade.contoso.com" -To Claims –RetainPermissions [-Force]

  18. No more preupgradecheck • Boo! • Instead from management shell you can use: • test-spcontentdatabase –name <YourDBName> -webapplication <http://YourWebApp> • Works the same in 2010 or 2013

  19. Features and Solutions • 2010 stuff mostly just works • Hopefully you were a good boy or girl and did everything as WSPs • Shane’s old 2010 blog post will help you get all of the WSPs out of 2010. Commands are the same or similar in 2013 to get the stuff in. • http://msmvps.com/blogs/shane/archive/2011/05/05/using-powershell-to-export-all-solutions-from-your-sharepoint-2010-farm-and-other-fun.aspx

  20. Upgrade a database • Test-SPContentDatabase –Name WSS_Content_Upgrade –WebApplication http://upgrade.contoso.com • Mount-SPContentDatabase –Name WSS_Content_Upgrade –WebApplication http://upgrade.contoso.com

  21. Things that are the same • The commands we just ran • One upgrade log file per upgrade • One upgrade error log file per upgrade • ..\15\logs • Still mount multiple databases at same time • Look and feel not upgraded automatically

  22. Things that are new • Upgrade just affects the database schema not the site collections • No option to force site collection to upgrade when upgrading the database • No more visual upgrade • 2010 vs. 2013 site collections • Everything is in the hands of site collection admins • Test upgrade – creates a new site collection to test • Upgrade health rules • Upgrade process • SPSite.AllowSelfServiceUpgradeEvaluation • Upgrade logs are ULS format, include Correlation IDs • Lots more

  23. Testing evaluation site collections • You can request an evaluation site collection • Site Settings > Site collection upgrade > Try a demo upgrade • Puts it in queue to be created • Creates you a new site collection at http://webapp/sites/yoursite-eval • Expensive operation only done by a timer job at 1 am by default • The source site collection is read only for the duration of the creation process • Sends email to requestor and all site collection administrators • For TESTING (like your play VM) you can manually run the timer job

  24. Forcing evaluation site collections • Remember this is done at 1 AM for a reason so don’t arbitrarily do this • Your SOURCE site collection will be read only while this runs • Unless you have SQL Server Enterprise then a snapshot is used • Central Admin > Monitoring > Review job definitions • Job name = Create Upgrade Evaluation Site Collections job • One per web application • Run it now • When job finishes you will have new site collection but it will be 2010 • About a minute later the Job “Upgrade site collections job” will kick in and upgrade to 2013 • Job scheduled for every minute so no need to run now

  25. Upgrade the site collection • Done by the site collection administrator • Can be done with PowerShell also • Upgrade-SPSite • Has 7 health rules that run to make sure upgrade can happen • Can be manually ran • Site settings > Site collection health checks • Test-spsite http://URL • When upgrade finished logs available • Site collection level • 15\logs – “SiteUpgrade – date/time” • Small site collections processed by app pool, larger by timer job • 10 MB or more than 10 subwebs

  26. Throttling • Upgrade is expensive so there are default limits • App pool 5 simultaneous site collections per web app • SPWebApplication.SiteUpgradeThrottleSettings - AppPoolConcurrentUpgradeSessionLimit • Site collections with less than 10 MB and less than 10 webs process by app pool, all others done by timer job • SPWebApplication.SiteUpgradeThrottleSettings - UsageStorageLimit and SubwebCountLimit • Content databases only allow 10 simultaneous site collections to be upgraded • SPContentDatabase.ConcurrentSiteUpgradeSessionLimit • $pig = Get-SPWebApplication http://upgrade.contoso.com • $pig.SiteUpgradeThrottleSettings.AppPoolConcurrentUpgradeSessionLimit • $pig.SiteUpgradeThrottleSettings.UsageStorageLimit • $pig.SiteUpgradeThrottleSettings.SubwebCountLimit

  27. Upgrade cmdlets you care about • Test-SPContentDatabase • Mount-SPContentDatabase • Request-SPUpgradeEvalutionSite • Upgrade-SPSite • Others • Get-Command *upgrade* • Have fun.

  28. Use the notification system • $pig = Get-SPWebApplication http://upgrade.contoso.com • $pig.UpgradeEvalSitesRetentionDays • $pig.UpgradeMaintenanceLink • $pig.UpgradeReminderDelay • $pig.ReadOnlyMaintenanceLink (I cannot make this work)

  29. What if you have a services farm in 2010 • A 2010 content farm can connect to a 2013 services farm • So upgrade it first 

  30. Random PowerShell for manipulating upgrade properties • Lock a site collection from PowerShell (2013 only) • $cow = get-spsite portal.contoso.com • $cow.readonly = $true • If you set a SQL database to read only in SQL it will lock all site collections for you • SPWebApplication.CompatibilityRange • You control min and max version (14 = 2010, 15 = 2015)

  31. Upgrade from 2007 to 2013 • No shortcuts • Upgrade 2007 (SP2 or later) to 2010 • Upgrade 2010 to 2013 • Or buy a 3rd party tool 

  32. Rackspace war stories • Mike’s adventure with wide list 10,000 items with 259 ROWS • 259 ROWS!!!!! • Actually upgrade blocking • Fix: He deleted the list • Scott’s story 2010 features still presenting themselves in 2013 • Fix: developers fixed their shoddy code • Sidenote: 8 TB in 260 Content DBs took 6 months • Gary grinded his team with not enough resources • Fix: bought more ram

  33. Twitter Tips • Give Search more resources @MrIsaac • Make sure there are no sites that are using 2007 UI on the 2010 environment. Do visual upgrades on 2010 first! @shankarajay1 • Many get stuck in the need to upgrade/migrate when it's easier to start from a new. Consider all options. @1wisegeek • A whole blog post http://www.collabshow.com/2014/02/27/10-strategy-considerations-for-sharepoint-2013-upgrade-youre-likely-to-miss/ @joeloleson

  34. More Resources • One link to rule them all • http://SharePoint.Rackspace.com/SPC • Shane giving a similar talk on upgrade • http://www.youtube.com/watch?v=yATAB2h8RDU&feature=youtu.be • Microsoft Ignite training, recordings and PPTs • http://technet.microsoft.com/en-US/sharepoint/fp123606 • TechNet looking good • http://technet.microsoft.com/en-us/library/cc303420(v=office.15) • 2010 claims migration (white paper) • http://technet.microsoft.com/en-us/library/hh487289.aspx

  35. Please express your thanks to our sponsors today for their supporting this event!

More Related