SharePoint Installation and UpgradeUntangling Your Options

Dan HolmeMVP, SharePoint ServerMicrosoft Technologies Analyst & EvangelistIntelliem

CONSULTANTMVP

Dan Holme

INTELLIEM AUTHORMAUI, HAWAIIAvePoint

danholme http://tiny.cc/danholmepresentationsdan.holme@intelliem.com

About This SessionTechnical guidanceHow do I upgrade or migrate?What do I need to know to successfully upgrade?

Roadmap to 2013What is SharePoint 2010? What is new at Microsoft? What is SharePoint 2013?When should I upgrade? On-premise or Office 365?

Insight, clarity & balanceWhat are enterprises planning and doing?

Answer questions

Upgrade is dead

What is upgrade?Version-to-version (V2V)SharePoint 2010 to SharePoint 2013

Build-to-build (B2B)Patches, updates, cumulative updates, service packs, etc.

What options are available?In-placeB2B onlyNot available V2V

Database attachV2VB2BConsider the benefits of using DB attach for B2B

Upgrade: A High Level View

Copy databases to new farm

2

Upgrade Databases

3

Server Farm Administrators 4 Site Collection Admins

Create SharePoint 2013

Production farm

1

Upgrade site collections to 2013 mode

5

Site collections remain in 2010 mode

4

2010 mode available

2010 workflow engine2010 customization

models (Full Trust, Sandbox)

Upgrade is “dead”No more in-place upgradeNew Farm + Database AttachBackward compatibility: 2010 & 2013 “modes”2013 includes 2010 root folder (“14 hive”), features, templates etc.And the 2013 root folder, features, templates, etc.New sites can be created in 2010 or 2013 mode (configurable: SPWebApp/SPSite.SiteCreationMode)

Support for 2010 and 2013 approaches2010 workflows and 2013 workflows2010 customization models (full trust & sandbox) and 2013 App models

Old workloads and customizations continue to work** To be confirmed with real-world customer experience. Always plan & test upgrade.Compatibility problems reduced

Upgrade planningDefinitionCurrent state & future state

WhyWhat must be rebuilt, migrated, or upgradedServers and settingsServices & contentCustomizations

Governance of upgradeTimeline, roles, responsibilities, policies and procedures, cost/benefit, risk and reward

ImpactPerformance, disruption, downtime

Upgrade

Learn

Prepare

TestImplement

Validate

Upgrade

Learn

Prepare

TestImplement

Validate

Upgrade improvementsFasterDeferred site collection upgrade

SaferNo in-place upgradeUpgrade evaluation site collectionsSite collection and health checks

ManageableCan be delegated to site collection administratorsSite collection upgrade throttlingSystem event notifications systemLogging changes

FlexibleFederated services compatibility across versions

Upgrade

Learn

Prepare

TestImplement

Validate

ImplementBuild serversDeploy customizationsUpgrade servicesMigrate to claimsUpgrade content databasesUpgrade site collectionsAlong the wayBackup everything firstMinimize downtimeMonitor progress

Build server(s)Scripted deploymentSQLPrerequisitesSharePoint binariesConfigurationCheck out my Deployment Wizard session from the SPC, on video at http://www.mssharepointconference.com/Pages/default.aspx

Cannot upgrade the configuration database

Upgrade service applications1. Document settings for service in source farm2. Back up service application database(s) in

source farm3. Restore database to target farm4. Create service application app pool5. Create service application

Attach or upgrade service database when creating the service applicationSome service applications require special attention: Project, Search, Secure Store

6. Create service application proxy7. Start service instances only

After service is created with upgraded databases

Upgrade service applicationsProjectMerge four databases into one before upgrading

Secure StoreSet service passphrase to the same value as before upgrade

SearchV2V admin database onlyIndex cannot be upgraded, V2VRecommend: Start anew

Upgrade the My Site Host2010 mode or 2013 modeAfter My Site Host is upgraded to 2013 modeSharePoint 2013 social features become availableNew personal sites will be created in 2013 mode

Personal site upgradeAs users visit My Site Host, their sites are added to upgrade queueUpgraded by timer job

Failed personal site upgradeIf upgrade of personal site fails, it will be reattempted after a delayCan force upgrade attempt

Site collection admin: From personal site UIFarm administrator: PowerShell if farm admin

Authentication considerationsWindows Classic (legacy)SP2013 limited support

Windows ClaimsDefault in SP2013Required for Apps and some other features

Migrate to claims before upgradeRecommended

Authentication mode mismatchesDatabase attach detects mismatched authentication modes

Forms AuthenticationNo changes from SP2010Install and configure provider in SP2013 with same name before attaching database

Migrating to claims authenticationPerform as a separate stepClarify faults to reduce troubleshooting

Migrate to claims before upgradeRecommended best practice

Use Test-SPContentDatabase before attachIdentify & remediate authentication problemsPartial migration within content databaseMisconfigured web application

Verify after upgradeContent securityFunctionalityExternal data sourcesWeb services

Upgrade content databases1. Document settings

From source farm

2. Configure web appApplication pool and managed accountManaged pathsAAM zones, URLs, IIS bindings

3. Install solutions and other customizationsInstall SP2010 customizationsInstall SP2013 customizationsMake web.config changes

4. Ensure service apps are connected to web app

5. Attach content database

Deferred Site Collection UpgradeSharePoint 2013 deep backwards compatibilitySharePoint 2010 mode and SharePoint 2013 mode

Attach content database2010 mode2010 mode is default. SP2013 mode is an additional step: not automatic on database upgrade.

Upgrade availabilityAvailable to farm administratorsAvailable to site collection administrators (configurable: SPSite.AllowUpgrade)System status bar notification

Upgrade evaluation site collectionCopy of site collection to evaluate upgraded functionality

PerformanceEnvironmentSQL server: CPU, memory, disk IOPS, database-to-disk layout (fragmentation), temp DB optimizationsSharePoint server: CPU, memoryNetwork bandwidth & latencySimultaneous upgrades

PerformanceDatabase upgradeRows: Site collections, webs, lists, documents, items, linksDatabase sizeRBS

Site collection upgradeRows: Webs, lists, activated upgrading features, documents, items, links

Upgrade throttlingConcurrent upgrades: per web application or per content databaseSite collection content: storage or subweb count (set in web application)If upgrade request is throttled, it is placed in upgrade queue

Disruption and DowntimeDisruptionChange client softwareRetrain usersRefactor or replace customizationsMitigation: Deferred site collection upgrade

DowntimeTemporary disruptionNo such thing as “zero downtime”: data loss vs. downtime reductionMitigation

Add granularity to multi-site content DBs over 100GB: Move site collection to new DB, then upgradeRead-only databases: Content, Services (except Access)Parallel upgradesUpgrade offline, sync, redirect: requires third party tools

Upgrade

Learn

Prepare

TestImplement

Validate

Document environmentSettingsPowerShellWinDiff: web server extensions, IIS site (web.config), GAC, 14 & 15 root folders

CustomizationsFull-trust solutions, admin-deployed InfoPath formsMSI, XCopy deployments

Performance characteristicsHardwareSQLNetwork

Clean upClean up SP2010 environmentDelete stale contentSite collections and web sites

Remove extraneous document versionsRationalize templates, features & web partsComplete visual upgrades to SP2010

Manage customizationsCategory Examples Likely Impact

Visual Master PagesThemesWeb PagesWeb Parts

2010 mode: function2013 mode: fail

Data Content TypesList TypesWeb TemplatesSite Definitions

If working: no impactIf missing: blockerUpgrade required: expensive—iteration

Internals Web ServicesWindows ServicesHTTP HandlerHTTP Module

Incompatible

Inform UsersActionWhat is needed: requirements, information gathering, content classification & taggingWhen it will happen: events, schedule

ExpectationsWhat will happenWhat happens next, if it worksWhat happens next, if it fails

InstructionsHow to upgrade site collectionsWhen to upgrade site collectionsHow to validate upgrade

SupportHow to communicate with upgrade team

Upgrade

Learn

Prepare

TestImplement

Validate

Build test farm(s)Maximize realism of simulationUse similar hardwareUse real data, not samplesDeploy all required customizationsMinimize URL changesMinimize name changes (SQL Alias)

Minimize impact on production environmentLive databasesExternal data connectionsSQL server performanceActive Directory profile data

Evaluate techniquesMethods & processesConfirmScript

Downtime mitigationPerformanceSQL Server responsivenessSharePoint responsiveness

ValidationTroubleshooting

Test & RepairTest-SPContentDatabaseConfiguration gapsOrphaned sites: site collections in content database but not in config database site mapMissing/unregistered customizations: features, site definitions, templates, web partsRow sizing for predicting comparative upgrade speeds: Add –ShowRowCounts switchAuthentication mis-match

Repair-SPContentDatabaseOrphaned websOrphaned listsOrphaned items

Test-SPSite and Repair-SPSite

Staging MigrationUse a staging farmOfflinePerformance matters only in relation to upgrade, not day-to-day utilization

Validate and remediateIn a non-production environment

Particularly if migrating to the cloudInsufficient access and tools to remediate problems after content is in Office 365

Upgrade

Learn

Prepare

TestImplement

Validate

Upgrade

Learn

Prepare

TestImplement

Validate

ValidateReview events and logsTroubleshoot failuresRemediate UI/UX issuesRemediate data issues

Logging ChangesUpgrade logs changed to ULS formatTSV format allows improved parsingCan be imported into ExcelIncludes Correlation ID

Site collection upgrade logs Available to Site Collection adminsUses separate logging level control than rest of upgrade

ValidateReview events and logsUpgrade error logFull upgrade logULSStart at top of log, work downwards (address dependencies)

Troubleshoot failuresProcess/assembly loadAuthentication (login, access)Missing servicesMissing files or customizationsContent

Remediate UI/UX issuesRemediate data issues

Validation ChecklistExisting sitesHigh-prioritySample of each site definition & featureAll sites

Provisioning of new sitesSite collections and subsitesActivate features, create lists & libraries, create pages, add web partsAs new 2010 mode As new 2013 modeAs new 2010 mode upgraded to 2013 mode

Validate against new 2010 mode

Validation ChecklistAuthenticationVisual customizationsExternal data connectionsOther functionality

Site Collection Health ChecksRule based health checksLooks for common issuesUpgrade-blocking issues

Missing SP2013 templatesPost-upgrade issues

Un-ghosted files

Site collection level scoped toolUI for Site Collection AdminsPowerShell cmdlet for Farm Admins

Runs automatically before Site Collection V2V upgradePrevents upgrade if blocking issues detectedDoes not run automatically before B2B upgrades

Life after upgrade

What doesn’t work?2010 Web Analytics2010 Office Web Applications2013 Office Web Applications used for sites whether in 2010 mode or 2013 mode

Project Web Access (PWA) templatesMust upgrade to 2013 modeProject Sites (PWS) supported in both 2010 and 2013 modes

Specific functionalityUser defined functions in Excel ServicesPowerPoint Broadcast sitesExternal BLOB Storage (EBS)

Align upgrade with business

Multi-farm scenarios1. Build SP2013 service and content farms2. Pre-index content3. Upgrade federated services to SP2013

Profile, Search, Social, Metadata, BCS, Secure StoreSet SP2010 service databases to read-only at SQL to prevent data loss

4. Consume federated SP2013 services in 2010 farm5. Upgrade services and content databases

Set SP2010 content databases to read onlyValidate database upgradesImmediately upgrade databases required to be 2013 mode (e.g. PWA)

6. Redirect requests to SP2013 farm7. Upgrade sites

Restructure physical or logical architectureNew features in SharePoint 2010Content type hubDocument information policiesManaged metadata

New features in SharePoint 2013Search: Continuous crawl, Content By SearchCross-site publishing (XSP)Managed navigation

Lessons learnedInformation management: security, compliance, information lifecycle managementService management: performance, storage, SLAs, content recovery, high availability, disaster recovery

Information assessmentAssess all contentBusiness needs changeInformation management & service management requirements change

Archive, Rebuild, Migrate, Delete (ARMD)Determine migration priority & actionCreate a migration request queue

Site source URLSite target URLAction (archive, rebuild, remove, migrate, delete)PriorityRoles & responsibilitiesInformation gatheringProcesses and workflowMigration date

Information (re)architectureInformation architectureContent types, metadata, search, site map, navigationClassification (“tagging”) processes and tools

Plan for IA migrationMap source IA to target IA

Perform IA migrationThird party toolsStaging farmConsider and manage URL changes

Utilize IA to facilitate and govern migrationPrioritize and filter sites and content to migrate

Governance, security & complianceUpgrade (improve) or establish governanceHarden securityImprove user and group managementRationalize and re-map security boundaries and controls

Cleanse and validate contentIn source farmIn staging farmIn target farm

Not recommended (on-premise)Not easy or even possible (Office 365)

Migrate, don’t upgradeWhyBig bang migrations are complex and riskyDowntime is not tolerableGarbage in – garbage out

Bad decisionsDatabase modificationsUnsupported site definitions

Information architecture changesRestructureMetadataRules-based migration: filter, tag, process

Migration of third-party components, e.g. workflowsMigration from 2007 (or other platforms) to SharePoint 2013 or Office 365

HowThird-party tools

Upgrade and migration guidanceTreat it as a real projectClean up the source environment firstUpgrade more than just contentImprove and restructure information architectureArchitect governance, security, and compliance into the migration process and end stateUpgrade related infrastructure and services, especially authentication (ADFS)

Utilize test and staging farmsParticularly important to test and stage on-premise before migrating to cloud

Be granularSplit large content DBs into multiple CDBs with fewer sites prior to upgradeUse migration tools to migrate subsets of content

Other Considerations

Evaluate third-party tools: MigrationPreparePre-scanning

ImproveRe-architect farmRestructure information architectureAutomatically classify contentRationalize security managementEnforce and audit content & compliance

Align with business processAlign with business process: granularity, metadata-driven rules and filtersGovern: workflows, approvals, controls

Perform migrationAutomateMinimize down time: performance, offline, and other optionsMigrate other components, e.g. workflows

Support (!!!)Migration is a one-time or rare activity for youIt’s the raison-d’etre for migration tool ISVsExtensive knowledge and experienceServices to support your migration

Evaluate third-party toolsManagement of cloud, on-prem, and hybrid environmentsExpose and integrate legacy and non-SharePoint contentMaintain a healthy service for the next changeInformation architecture: content, metadata, tagging, navigationInformation management: security, compliance, information lifecycleService management: performance, storage optimization, recovery, HA, DRCustomization management: application and customization lifecycle managementService portfolio management

Shout OutsRandy WilliamsJeremy ThakeGary LapointeChris GivensAndrew ConnellSpence HarbarJason HimmelsteinTodd BaginskiScot Hillier

Matt McDermottEric ShuppsPaul SwiderShane YoungTodd KlindtWictor WilénAsif RehmaniRob BogueAgnes Molnar

MAHALO! (thank you!)http://tiny.cc/danholmepresentationshttp://bit.ly/danholmearticleshttp://bit.ly/danholmebooks

A HUI HO! (‘til next time!)dan.holme@intelliem.com@danholme