Inspirirani ljudima. Ugasite mobitele. Hvala.

Dražen Pavković Premier Field Engineer Microsoft Migracija na SharePoint 2013.

Inspirirani ljudima. Overview

Migration options Database attach Version-to-version (2010 to 2013) upgrade Upgrade of some service applications Build-to-Build (patch) upgrade In-place Only for B2B

Overview

Databases eligible for database attach Content Databases Search Administration User Profile Managed Metadata Secure Store PerformancePoint BCS SSRS Project All four databases merged into one

Upgrade Site collection upgrade Separated from content database upgrade Significant schema changes Sparse columns Shredded storage for documents and other binary objects

Authentication changes Windows authentication (Windows Classic) is deprecated Can be set only via PowerShell Claims is the recommended SharePoint Authentication method Windows, Forms, and Third-Party Identity Providers all provide Claims Identities Test-SPContentDatabase in SharePoint 2013 detects mismatched authentication modes from source to destination Options for Claims Migration: Recommended option is prior to database migration

Site collection upgrade Site Collection Upgrade Multiple version site collection compatibility modes Self-service upgrade Managed queue of pending upgrades Site Collection health checks Upgrade Evaluation Site Collections Notification System

Site collection upgrade 2010 site collections continue to render unchanged in 2013 No SharePoint 2010 installation required 2013 has all required SharePoint 2010 files included Replaces Visual Upgrade Allows deep backwards compatibility Most 2010 features remain available Existing customizations continue to work as is All sites remain in 2010 mode after database attach Cannot be forced automatically on database upgrade

Site collection upgrade Site collections can be upgraded to 2013 mode By farm admins By site collection admins (if allowed by farm admins) Web Application settings determine available versions for new site collections Existing site collections remain in 2010 mode when database is attached New site collections can be created in 2010 or 2013 mode Unless admin changes settings

Site collection upgrade Preview existing site in 2013 mode Creates side by side copy of existing site collection Occurs in scheduled Timer Job process Can be an expensive operation Notification sent when evaluation site is available To requester and all site collection administrators is optional if request occurs via PowerShell

Site collection upgrade Upgrade from queue is executed immediately in current process if not effected by throttling If throttled, upgrade will be deferred and picked up by timer job Application Pool throttles – effect upgrades started from Web pages Content Database throttles – effect upgrades started from Web pages or PowerShell Prevents overload from self service site collection upgrade

Service farms 2010 farms can consume 2013 Service Applications Search Profile Secure Store Managed Metadata BCS Allows parallel service farms 2010 farms can consume 2010 and 2013 Services 2013 farms can consume only 2013 Services Upgrade Services farms first

Inspirirani ljudima. Process

Document configuration Farm Settings Server Settings Domain and Network Settings Service and Service Application Settings Databases Content Databases Service Application Databases Web Applications External Services Multi- and Cross-Farm Configuration

Downtime mitigation Read-Only Databases and Site Collections Set-SPSite –LockState ( ReadOnly | NoAccess | Unlock ) Set SQL databases to read only (SharePoint is aware) Migrate content databases individually Migration of content instead of upgrade of databases Set Service Application databases to read-only

Identify stakeholders SharePoint Administrators Server Administrators Network Administrators Security Administrators Database Administrators Client Administrators Helpdesk Site Collection Owners and Administrators Site Designers and Developers Site Users Partners Executive sponsors and stakeholders

Change notifications Changes following upgrade URL changes Functionality changes Upgrade window Date and time Planned duration Availability during upgrade window Read-Only or not at all Site collection upgrade Will you allow evaluation site collections? Will you allow self-service site upgrade? Will you enforce site upgrade? When?

Testing Ensure test environments cannot impact production environment Do external data connections effect production external systems? Shared resources (e.g. SQL, disk or network) Minimize differences in test environment Server and DNS names Load balancing arrangements Same hardware Use real data

Test-SPContentDatabase Checks for dependencies between content database and environment Warnings to console; Reports to ULS Detects and Reports on: Missing Site Definitions Missing Features Site Collection Orphans (SiteMap Sites) Missing files for ghosted pages Missing Web Parts Missing Event Receiver assemblies Table Row Counts

Deploy Create managed paths before attaching content databases Use same as existing environment If existing managed paths do not exist, SharePoint creates default paths Two explicit inclusions at the same path will cause the path to be turned into a wildcard inclusion Paths applied to databases attached later may not match

Content database upgrade Ensure Managed Paths exist Ensure Service Application Proxy Group contains all previous service application proxies Ensure AAMs are configured correctly Run Mount-SPContentDatabase Automatic snapshotting during Upgrade

Content database upgrade: Monitor Percentage Update in Console Page in CentralAdmin ULS Logs Get-SPPendingUpgradeAction

Upgrade commandlets Upgrade-SPFarm Upgrades all objects in farm recursively, including all databases and sites (build-to-build only) Upgrade-SPContentDatabase Upgrades content databases sites (build-to-build only) Upgrade-SPSite Only upgrades sites

Site upgrade Via UI: User clicks “Start Now” or Site Collection Upgrade page Site Health Check must pass first If passes constraints, runs in process Otherwise, queued for timer job Via PowerShell: Upgrade-SPSite Still must pass site health check Defaults to build-to-build upgrade If not queued, upgraded immediately

Site upgrade logs {SiteUrl}/_catalogs/MaintenanceLogs {DateTime}.txt {DateTime}-error.txt SharePoint Log Directory (default: 15\LOGS) SiteUpgrade-{DateTime}.txt SiteUpgrade-{DateTime}-error.txt DEBUG and VERBOSE messages only logged to file system log MEDIUM and higher messages to document library

Site upgrade evaluation Via UI or Request-SPUpgradeEvaluationSite Evaluation Site Creation Queue: PreviewSiteRequests table Initial preview site expiration governed by: SPWebApplication.UpgradeEvalSitesRetentionDays (default == 31) job-create-upgrade-eval-sites Daily between 1:00am and 1:30am (default) Uses snapshots if available job-delete-upgrade-eval-sites Sends s within two days of expiration Deletes after expiration Daily between 1:00am and 1:30am (default)

Personal sites Personal Sites Upgrade Upgrade MySiteHost User sites are automatically upgraded on first access

Migration - PowerShell New-SPWebApplication -Name "Upgrade" -ApplicationPool "SharePoint Web Applications" -Url -Port 80 - AuthenticationProvider (New-SPAuthenticationProvider -DisableKerberos –UseWindowsIntegratedAuthentication) Test-SPContentDatabase -Name WSSContent_ContosoUpgrade_Restored - WebApplication -ServerInstance SPSQL01 Mount-SPContentDatabase -Name WSSContent_ContosoUpgrade_Restored - WebApplication Upgrade-SPSite -Identity -VersionUpgrade

Test (1) Check authentication providers Can you access home page and _layouts pages? Confirm PeoplePicker works Pick certain sites in advance and check if they work At least one from each site definition Test MySites Start service instances only after service application are created

Test (2) Search Crawl content sources, check scopes and best bets Profile Check profile sync works BCS Check connections to external data Secure store Check access

Test (3) Validate external data connections InfoPath connections, BCS connections, Excel services, Search crawl external targets Confirm connections work for all users Administrators and end users Connection strings may need to be edited Services may be incorrectly set up Network and firewall filters

Inspirirani ljudima. Customizations

Types of customizations Visual – Likely Issues Master Pages Themes Web Pages Web Parts Content Structure - Migrate to 2013 and test Content Types List Templates Web Templates Site Definitions Platform - Evaluate Web Service Windows Service HTTP Handlers and Modules

Content types and list schemas High level of dependency during upgrade and migration If schema is not available for list, it will not render Modifications require planning Iterate over every instance to update Require independent validation and testing Beware of conflicts Column Names Paths Upgrade Definition Files can help

Install customizations Install previous customizations Use existing solutions when available Run installers Script file deployment and config file changes Install new customizations Use solutions as much as possible Can defer installation of 15 solutions if using 2010 mode sites web.config changes to consider SafeControls Forms Authentication Providers BlobCache

Deploying customizations Solutions Default deployment of existing solutions will deploy to 2010 directories Use Install-SPSolution –CompatibilityLevel to force cross-version install Files Master pages, JavaScript, CSS, othe XML Deploy to 14 and 15 hives if necessary

Inspirirani ljudima. Troubleshooting

Troubleshooting - Site rendering Site doesn’t render? Class reference missing from SafeControls list Assembly or referenced items not installed Site renders wrong? Rendering issues due to expecting earlier version artifacts  such as old JavaScript and CSS Exceptions due to missing artifacts or deprecated API calls

Troubleshooting - Access denied Access denied errors Ensure account has access to databases Ensure account is site collection admin Ensure account is local administrator

Troubleshooting - Diagnostics session Start/Stop-SPDiagnosticsSession -CorrelationId -Dashboard -TraceLevel

Troubleshooting vs 2013 Existing 2010 visuals should work without changes in 2010 mode Issues can occur when upgrading site collections to 2013 mode Common causes are: References to 2010 or earlier version of files  Has explicit references to _layouts (defaults to 14)  Relies on 2010 JavaScript and/or CSS while in 2013 mode Pages that have been modified using 2010 or earlier visuals  Customized (unghosted) pages  Custom ASPX pages

Troubleshooting - other Look in upgrade log for problems with customizations Plan to address problems as soon as possible to narrow potential problems For WSP solutions ensure you have installed to correct target -CompatibilityLevel parameter required For 3rd party components/services Install 2013 versions May also need previous versions for 2010-mode sites

Inspirirani ljudima. Pitanja i odgovori.