1 / 80

The Path through Upgrade and Beyond

The Path through Upgrade and Beyond. Brian Caauwe – Senior SharePoint Consultant. September 28th, 2013. Session Agenda. Upgrade Planning Upgrade Overview Upgrade Cycle. Who am I?. Brian Caauwe SharePoint Consultant & Speaker Email: bcaauwe@avtex.com Twitter: @ bcaauwe

vienna
Télécharger la présentation

The Path through Upgrade and Beyond

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. The Path through Upgrade and Beyond Brian Caauwe – Senior SharePoint Consultant September 28th, 2013

  2. Session Agenda • Upgrade Planning • Upgrade Overview • Upgrade Cycle

  3. Who am I? • Brian Caauwe • SharePoint Consultant & Speaker • Email: bcaauwe@avtex.com • Twitter: @bcaauwe • Blog: http://blog.avtex.com/author/bcaauwe • Technical Editor • Professional SharePoint 2013 Administration • Certifications • MCM: SharePoint Server 2010

  4. Thank You! For Sponsoring the IT Pro/Admin Track

  5. Quick Poll • SharePoint Version • 2007 – WSS, MOSS • 2010 – SPF, Server, FAST • 2013 • Work Roles • SharePoint Administrator • SharePoint Developer • Business User • Other

  6. Upgrade Planning

  7. Upgrade Planning General Definitions Upgrade • “to improve or replace especially software or a device for increased usefulness” Migration • “to move from one country, place, or locality to another” Source http://www.Merriam-Webster.com

  8. Upgrade Planning SharePoint Definitions Upgrade • Enhancing the core system to enable new functionality • Version to Version • 2010 to 2013 (and beyond) • Build to Build • Cumulative Updates • Service Packs Migration • Moving content from between SharePoint objects or between environments • Making an SPWeb an SPSite • Moving a document library to another location • Moving a file between libraries

  9. Upgrade Planning Upgrade Level Set • ALL upgrade enhancements have been made with one customer in mind

  10. Upgrade Planning Managing a complex process • Customer Communication • Farm / Customization Surveys • Upgrade / Customization Testing • Environment Cleanup • Environment Build-out • Customizations Deployment • Operations Scheduling • Rollback Plan • Post-Upgrade Activities • Ongoing Support Calls

  11. Upgrade Overview

  12. Upgrade Overview Typical Issues • Customizations • Available Disk Space • Customizations • Resource Constraints (I/O, Memory, Time) • Customizations • Testing (or lack thereof) • Customizations • Knowledge • Customizations

  13. Upgrade Overview OOB Upgrade Scenarios Supported • MOSS 2007 / WSS 3.0 SP2  SharePoint 2010 RTM  SharePoint 2013 • Need to force site version from 12 to 14 • SharePoint 2010 RTM+  SharePoint 2013 • Database Attach Upgrade • Service Applications (some) • Content Databases • Swing Upgrade • AAM Redirection (DO NOT USE) Unsupported • In Place • SharePoint 2007 (or previous)  SharePoint 2013

  14. Upgrade Overview What’s Different – Changed • Claims authentication • DEFAULT authentication method • Classic isn’t gone, only use with REAL business requirement • Converting to Claims • Microsoft guidance == migrate to claims in 2010 first 2010 $webApp = Get-SPWebApplicationhttps://portal.company.com $webApp.UseClaimsAuthentication = $true $webApp.Update() $webApp.MigrateUsers($true) 2013 $webApp = Get-SPWebApplicationhttps://portal.company.com Convert-SPWebApplication $webApp -To Claims -RetainPermissions • TechNet Reference: http://technet.microsoft.com/en-us/library/jj219696.aspx

  15. Upgrade Overview What’s Different – Changed • Test-SPContentDatabase • Use -ServerInstance parameter to connect to specific SQL instance • CAN target connected 2010 content databases • Use -ShowLocation parameter to show site collection ID references for reported issues • Does NOT tell the whole story • User Experience • CSS, Master Pages, Page Layouts • Themes are different again (new SPColor) • References to /_layouts/ and /_controltemplates/ need to change to /_layouts/15/ and /_controltemplates/15/ (2013 mode) • Office Web Application URLs (separate product == new URLs) • When upgrading Site Collection, masterpage gets set to seattle.master

  16. Upgrade Overview What’s Different – Changed • Site Collection / Web Upgrade • Webs can only be in the same compatibility level as Site Collection • Cannot swap between UIVersions for “preview” • Evaluation sites will ALWAYS have a shelf life • Upgrade Ownership • Farm Administrators make site collection upgrade “available” • Site Collection Administrators initiate / evaluate upgrade • Site Collection Administrators NOTIFIED of upgrade process

  17. Upgrade Overview What’s Different – Changed • Web Application / Content Database Upgrade Throttling • Storage limit (in MB) beyond which the site should be moved to queue • $webApp.SiteUpgradeThrottleSettings.UsageStorageLimit (10 Default) • Subweb limit beyond which the site should be moved to queue • $webApp.SiteUpgradeThrottleSettings.SubwebCountLimit (10 Default) • Max concurrent upgrade sessions per application pool • $webApp.SiteUpgradeThrottleSettings.AppPoolConcurrentUpgradeSessionLimit (5 Default) • Max concurrent upgrade sessions per content database • $contentDB.ConcurrentSiteUpgradeSessionLimit (10 Default) • MSDN Reference: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spsiteupgradethrottlesettings_properties.aspx

  18. Upgrade Overview What’s Different – Improved • Upgrade Logging • Server: Individual consolidated Upgrade-[DATE]-[TIME]-[ID]-error.log files • Site collection maintenance logs available through UI • Formatted like ULS logs • Placed in folder in a special gallery • ~site/_catalogs/MaintenanceLogs/[DATE]-[TIME]-[ID].txt • Service Application Upgrade • 2010 environment CAN consume 2013 service applications • Will not utilize new features until web applications are in 2013 mode

  19. Upgrade Overview What’s Different – Improved • Service Application Upgrade (continued…) • Secure Store • New-SPSecureStoreApplication (Upgrades SSS) • Update-SPSecureStoreApplicationServerKey (Requires Passphrase from 2010) • Business Connectivity Services • New-SPBusinessDataCatalogServiceApplication (Upgrades BCS) • Managed Metadata • New-SPMetadataServiceApplication (Upgrades MMS) • Search • Restore-SPEnterpriseSearchServiceApplication (Upgrades Search Admin DB) • Does NOT retain index • Auto-generates other search database names … GUIDS

  20. Upgrade Overview What’s Different – Improved • Service Application Upgrade (finally…) • User Profile • New-SPProfileServiceApplication (Upgrades Profile, Social and / or Sync DB) • Can upgrade ALL or SOME User Profile Databases • User Profile • Social • Sync (requires additional FIM certificate “fun”) • PerformancePoint • New-SPPerformancePointServiceApplication (Upgrades PerformancePoint) • Project • New-SPProjectServiceApplication (Creates Project Service App) • Mount-SPProjectDatabase (Mounts singled merged project DB OR merges four prior DB’s into one)

  21. Service Application Upgrade Demo

  22. Upgrade Overview What’s Different – Removed • Methods • In Place Upgrade • AAM Redirection • OK it’s still there… but DO NOT USE • stsadm -o preupgradecheck • Manual / OM methods • Test-SPContentDatabase can help a good amount • SPWeb.UIVersion & SPWeb.UIVersionConfigurationEnabled • Evaluation Sites are the “replacement” • Content Databases no longer flip to SIMPLE recovery during upgrade

  23. Upgrade Overview What’s New – Compatibility Ranges / Compatibility Levels • CompatibilityRange • Determines what VERSION of site collections can be created in Central Administration AND impacts Self-Service upgrade options • Configurable on Web Application • $webApp.CompatibilityRange • Features / Solutions now deployed based on CompatibilityRange (14, 15, All) • Install-SPSolution uses parameter name -CompatibilityLevel • TechNet Reference: http://technet.microsoft.com/en-us/library/ff607534.aspx • CompatibilityLevel • Site Collection Determines user experience • Replacement for UIVersion • Located on the Site Collection object NOT Web object • Cannot be directly set • Set as part of the Upgrade-SPSite process ONLY • $site.CompatibilityLevel

  24. Upgrade Overview What’s New – Evaluation Site Collection PowerShell • Submit Request • $site = Get-SPSite https://portal.company.com/sites/sitecollectionurl • Request-SPUpgradeEvaluationSite $site [-Email] [-NoUpgrade] • TechNet Reference: http://technet.microsoft.com/EN-US/library/fp161282.aspx

  25. Upgrade Overview What’s New – Evaluation Site Collection • Timer Job managed • Create Upgrade Evaluation Site Collections • Creates evaluation site collections • Default Configuration: Runs daily between 01:00:00 and 01:30:00 • Internal Name: job-create-upgrade-eval-sites • Delete Upgrade Evaluation Site Collections • Deletes evaluation site collections AND sends notifications near expiry date • Default Configuration: Runs daily between 01:00:00 and 01:30:00 • Internal Name: job-delete-upgrade-eval-sites

  26. Upgrade Overview What’s New – Evaluation Site Collection • Web Application Properties • Allows Site Collection Administrators Self-Service Evaluation • $webApp = Get-SPWebApplicationhttps://portal.company.com • $webApp.AllowSelfServiceUpgradeEvaluation = $true (Default) • Can postpone upgrade available notification for site collection administrators • $webApp.UpgradeReminderDelay = 30 (Default) • E-mail notifications • $webApp.SendSiteUpgradeEmails = $true (Default) • Max Size for Evaluation Sites • $webApp.MaxSizeForSelfServiceEvalSiteCreationMB = 102400 (Default – in MB) • Evaluation site retention • $webApp.UpgradeEvalSitesRetentionDays = 30 (Default – in days)

  27. Upgrade Overview What’s New – Evaluation Site Collection • Site Collection Properties • Self-Service properties • $site = Get-SPSitehttps://portal.company.com • $site.AllowSelfServiceUpgrade = $true (Default) • $site.AllowSelfServiceUpgradeEvaluation = $true (Default) • Also contains “inherit” properties on Site Collection to reset values from Web Application • $site.InheritAllowSelfServiceUpgradeSetting = $true (Default) • $site.InheritAllowSelfServiceUpgradeEvaluationSetting = $true (Default)

  28. Evaluation Site Collection Demo

  29. Upgrade Overview What’s New – Site Collection Upgrade PowerShell • Start Site Upgrade • $site = Get-SPSite https://portal.company.com/sites/sitecollectionurl • Upgrade-SPSite $site [-VersionUpgrade] [-Email] [-QueueOnly] [-Unthrottled] • TechNet Reference: http://technet.microsoft.com/EN-US/library/fp161257.aspx • Monitor Upgrade Queue • $db = Get-SPContentDatabaseWSS_Content • Get-SPUpgradeSessionInfo -ContentDatabase $db [-HideWaiting] [-ShowFailed] [-ShowInProgress] • $site = Get-SPSite https://portal.company.com/sites/sitecollectionurl • Get-SPUpgradeSessionInfo -Site $site • TechNet Reference: http://technet.microsoft.com/EN-US/library/fp161278.aspx

  30. Upgrade Overview What’s New – Site Collection Upgrade • Deferred Site Collection Upgrade • Allows site collection administrators to determine WHEN they go to 2013 • Timer Job managed • Upgrade Site Collections job • Default Configuration: Runs every 1 minute • Internal Name: job-create-sites

  31. Site Collection Upgrade Demo

  32. Upgrade Overview What’s New – Site Collection Health Checks PowerShell • Test-SPSite$site • TechNet Reference: http://technet.microsoft.com/EN-US/library/fp161259.aspx • Repair-SPSite $site • TechNet Reference: http://technet.microsoft.com/EN-US/library/fp161269.aspx

  33. Upgrade Overview What’s New – Site Collection Health Checks • Health Checks are forcibly run before any site collection upgrade • Rule based • Conflicting Content Types • Customized Files • Missing Galleries • Missing Parent Content Types • Missing Site Templates • Unsupported Language Pack References • Unsupported MUI References • WILL prevent upgrade if upgrade blocking errors occur • Can be run manually through UI or PowerShell • Can / should be used OUTSIDE of the upgrade process to identify issues • TechNet Reference: http://technet.microsoft.com/en-us/library/jj219720.aspx

  34. Upgrade Overview What’s New – System Notifications / Email Templates • Status message bar is NOT customizable • Additional “Maintenance Link” property to direct users to pre-determined pages • $webApp.ReadOnlyMaintenanceLink • $webApp.UpgradeMaintenanceLink • Email Templates provided by Web Application feature • Feature Name: EmailTemplates • Only deployed to 14 Hive

  35. Upgrade Cycle

  36. Upgrade Cycle

  37. Upgrade Cycle Learn About YOUR environment • Customizations (Solutions / Features / Cowboy) • Your code • Branding • 3rd party • Authentication Provider • Classic vs. Claims • FBA • Custom STS • Hardware Requirements (YOU NEED MORE) • Disk Requirements (include backup and restore sizing) • Resource Requirements • TechNet Reference: http://technet.microsoft.com/en-us/library/cc262485.aspx Upgrade Methods • Services Application (FIRST) • Point in time migration • Swing migration • Content Database • Read-only outage acceptable to reduce “downtime”

  38. Upgrade Cycle Learn Web Browser Requirements • IE 8+ • Google Chrome (latest version) • Mozilla Firefox (latest version) • Apple Safari (latest version) • What about mobile? Office Requirements • 2010 or 2013 • SharePoint Designer “Deprecated” Features • Sandbox Solutions • code == bad • XML == OK • SharePoint Designer – Design View (Removed) • PowerPoint Broadcast site collection (Removed) • Meeting Workspaces • Web Analytics  Moved to Search Service Application • Office Web Applications  Separate application

  39. Upgrade Cycle Prepare Reconnect with users • Ask your users how they are using your solutions • Determine dead sites • Remove data clutter • Prioritize items that are fixed in 2013 • Re-visit information architecture • Build internal buzz • Start communication early!!

  40. Upgrade Cycle Prepare Upgrade Strategy • Different Roles, Different Upgrade Schedules • SQL (MDOP) • Office Web Applications • Azure Workflow • SharePoint • Upgrade Operations • Roles on call, required, optional • Downtime / Disruption limits • URL adjustments (AVOID IF POSSIBLE)

  41. Upgrade Cycle Prepare SharePoint 2010 Environment • Validate / Complete Visual Upgrade • Cleanup sites, webs, versions • Isolate customized site collections into separate databases • Isolate ROOT (/) site collections into separate databases • Prepare site and list “templates” for migration • Service Applications • Swing Upgrade: Prepare Farm for Service Application consumption

  42. Upgrade Cycle Prepare – Upgrade Prep Tools Farm Insight • Manual • File / Folder comparison • 14 hive • web.config • GAC • IIS Bindings • Host Headers • SSL Certificates • Service Application / Web Application settings • Secure Store Passphrase • User Profile Import Connection(s) • Blobcache • BrowserFileHandling • Maximum Upload Size • Tools • WinDiff / BeyondCompare • PowerShell • XCopy

  43. Upgrade Cycle Prepare – Upgrade Prep Tools Farm Insight (Continued) • PowerShell • Get-SPServer • Get-SPWebApplication / Get-SPSite / Get-SPWeb • Get-SPFeature • Get-SPWebTemplates • Test-SPContentDatabase • Get-SPContentDatabase | %{$_.Repair([bool])} • $true = fix issues • $false = list issues • MANY, MANY MORE… • STSADM • stsadm -o enumsites • stsadm -o enumallwebs • stsadm -o databaserepair

  44. Upgrade Cycle Prepare – Upgrade Prep Tools Moving Content • PowerShell • Move-SPSite • Export-SPWeb / Import-SPWeb • STSADM • stsadm -o mergecontentdbs • stsadm -o export / import • 3rd Party Tools • MANY out there Customization Gathering • PowerShell • Get-SPSolution • Export-SPInfoPathAdministrationFiles • STSADM • stsadm -o enumsolutions • stsadm -o ExportIPFSAdminObjects

  45. Upgrade Cycle Test SharePoint 2013 Environment • Build / Prepare SQL environment • Ensure Max Degree of Parallelism • Build Associated Services • Office Web Applications • Azure Workflow Manager • Build SharePoint environment • Use YOUR real data • Use similar hardware as production • Know what you are trying to test • Web Applications • Set CompatibilityRange • Create Managed Paths • Manual web.config changes • Service Applications • Build out new service applications NOT being migrated • Swing Upgrade: Prepare Farm for Service Application publishing (2013) / consumption (2010) • Apps configuration

  46. Upgrade Cycle Test Service Applications • Test service applications to upgrade • User Profile: Create Import Connections • Search: Perform crawl to populate index • Swing Upgrade: Publish service applications and consume for validation Content • Run Test-SPContentDatabase prior to Mount-SPContentDatabase • Run Test-SPSite and Repair-SPSite before site upgrades

  47. Upgrade Cycle Test Perform MULTIPLE test upgrades • Create a checklist • Document your process AND procedures • Create scripts for repeatable process • Take user error out of the equation as much as possible • Identifies YOUR time requirements End user Testing • Real accounts • Customization Testing • They know their sites better than you • Performance / Load Testing

  48. Upgrade Cycle Implement Service Application Upgrade Order • Secure Store • Business Connectivity Services (might require SSS) • Managed Metadata • User Profile (requires BCS and MMS) • Search (crawl account needs to have access to UPA) • PerformancePoint • Project • Make sure associated services are also running Content Database Upgrade Order • Root level site collections • Easy (less customization) • Hard (most customization) • ALWAYS Test-SPContentDatabase before Mount-SPContentDatabase

  49. Upgrade Cycle Implement Upgrade Order for Social Experience • Upgrade MySite Host to 2013 • Upgrade Personal sites to 2013 • PowerShell initiated • User Initiated • Users cannot use new social features until their personal site is in 2013 mode

  50. Upgrade Cycle Validate Logs • Server logs • Event Logs • ULS Logs • Upgrade Logs • Site Collection Maintenance Logs • Do NOT ignore “warnings” Issue Resolution Order • Authentication • Customizations • Content Data Integrity • Orphans / DB issues • Missing Data

More Related