Meeting # 105 Welcome to the Minnesota SharePoint User Group September 11 th, 2013 SharePoint...

Meeting # 105http://sharepointmn.com

Welcome to the Minnesota SharePoint

User Group

September 11th, 2013

SharePoint Upgrade: What you need to know

Brian Caauwe

Donald Donais


Agenda

• Upgrade Planning• Upgrade OverviewBreak• Upgrade Cycle• Demo• Post Upgrade• Resources


User Group Goal / Objectives

Develop and support a local community focused on Microsoft SharePoint Technologies

• Educate user group members about SharePoint Technologies• Transfer knowledge within the community• Communicate best practices• Introduce new products / solutions


MNSPUG Sponsors

Wrox Press (www.wrox.com)

O’Reilly (www.oreilly.com)

Dedicated Sponsors

Avtex (www.avtex.com)

Microsoft (www.microsoft.com)

Annual SponsorBenchmark Learning (www.benchmarklearning.com)

SharePoint User Group Support

softwareOne(www.softwareone.com)

http://www.wrox.com/

http://www.oreilly.com/

http://www.avtex.com/

http://www.microsoft.com/

http://www.benchmarklearning.com/

http://www.benchmarklearning.com/

http://www.softwareone.com/EN-US/Pages/Default.aspx


MNSPUG Sponsorship

• Two Opportunities to Sponsor• Annual Sponsorship ($2500 annually)

Money Will Help Fund MNSPUG Events Annual Sponsorship will be Reviewed Yearly Cannot be in Direct Competition with Another Annual Sponsor Looking for:

• Microsoft SharePoint ISV• Microsoft Learning Provider• Microsoft Licensing Account Reseller

• Lunch Sponsorship


MNSPUG Sponsorship Continued

• Lunch Sponsorship ($500 for a lunch) Sponsor a Lunch Event Following MNSPUG Event This can be geared toward your specific SharePoint product or

capabilities


MN SharePoint Users Group Website

• SharePoint Resource Documents• SharePoint Resource links• RSS Feeds • Meeting Schedule• Past User Group Presentations• Past User Group Recordings• Sponsorship Information

• http://sharepointmn.com• Email: [email protected]

mailto:[email protected]



Social Networking

• Linked In group – The most interactive… includes job postings… Post Job Posting on the Jobs Discussion page

http://www.linkedin.com/groups?gid=1878792

• Twitter tags - @MNSPUG and #MNSPUG

http://www.linkedin.com/groups?gid=1878792


Upcoming Schedule

• Next Meeting October 9th 9:00 AM to 11:30 AM SharePoint and Social Vendor Sponsored Lunch - NewsGator Microsoft Technology Center Check www.SharePointMN.com for updates!

• Ongoing Schedule 2nd Wednesday of every month 9:00 to 11:30 am Microsoft Technical Center - Edina

http://www.sharepointmn.com/


Local and Online EventsMicrosoft Webcast Calendar of Eventshttp://www.microsoft.com/events/webcasts/calendar/monthview.aspx#filter

SharePoint ShopTalk (Online) – Every Thursday @ 11:30 AMhttp://sharepointshoptalk.com/

SharePoint Legal Users Group – 3rd Thursday @ 12:00 to 1:00 p.m.http://sharepointmnlegal.com

SharePoSH – Online Virtual Eventhttp://www.shareposh.com/Pages/default.aspx

SharePoint Saturday Omaha – September 28th, 2013 University of Nebraska, Omahahttp://spsevents.org/city/Omaha/Pages/Information.aspx

SharePoint Saturday Twin Cities – October 12th, 2013 Normandale Community College, Bloomingtonhttp://www.spstc.com/

SharePoint Saturday Chicago – November 2nd, 2013 Hard Rock Hotel, Chicago, ILhttp://www.sharepointsaturdaychicago.com/

SharePoint Conference 2014 – March 3-6th 2014 , The Venetian, Las Vegas, Nevadahttp://sharepointconference.com/

Anything Else?

http://www.microsoft.com/events/webcasts/calendar/monthview.aspx

http://sharepointshoptalk.com/

http://sharepointshoptalk.com/

http://sharepointmnlegal.com/

http://www.shareposh.com/Pages/default.aspx

http://spsevents.org/city/Omaha/Pages/Information.aspx

http://www.spstc.com/

http://www.sharepointsaturdaychicago.com/

http://sharepointconference.com/


Evaluations & Giveaways!

Ira Fuchs


In Remembrance


Presenter


Brian Caauwe• SharePoint Consultant• Sports Enthusiast• @bcaauwe• http://blog.avtex.com/author/bcaauwe

Introductions

http://blog.avtex.com/author/bcaauwe


Upgrade Planning


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

Upgrade PlanningGeneral Definitions

http://www.merriam-webster.com/


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

Upgrade PlanningSharePoint Definitions


Poll

• What target customer(s) was SharePoint 2013 upgrade developed for?


• ALL upgrade enhancements have been made with one customer in mind

Upgrade PlanningUpgrade Level Set


• 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

Upgrade PlanningManaging a complex process


• Create a communication plan TechNet: http://technet.microsoft.com/en-us/library/cc263345.aspx

• Upgrade Group / Committee Stakeholders Server Admins Database Admins SharePoint Admins Site Admins Security Team Designers Developers Site Users

• Customer Survey’s

• COMMUNICATE!!! Upgrade Reasons Upgrade Plan Upgrade Status More, more, more…

Upgrade PlanningCustomer Communications

http://technet.microsoft.com/en-us/library/cc263345.aspx



• Gather Information

• Determine Impact

• Collect customizations Manual Scripted

• Sample Worksheet http://www.microsoft.com/en-us/download/details.aspx?id=30370

Upgrade PlanningFarm / Customization Surveys

http://www.microsoft.com/en-us/download/details.aspx?id=30370



• Upgrade Issues Wide lists Authentication Mismatch Modified Databases Customizations

• Recommendations Complete Customer & Farm Survey’s BEFORE testing Set Testing Goals Test customizations Use REAL data Evaluate branding requirements Use Evaluation sites

• TEST YOUR Upgrade Process http://www.microsoft.com/en-us/download/details.aspx?id=30366

Upgrade PlanningUpgrade Testing / Customization Testing




• Remove unneeded sites Office Web Application “cache” PowerPoint Broadcast

• Remove Stale Content / Unneeded Versions• Review Quotas / Locks• Cleanup Templates, Solutions, Features, Web Parts, etc

User Driven, OM / PowerShell can help• Repair Data issues

User Driven, OM / PowerShell can help• Verify “Healthy” Environment (e.g. Health Analyzer, Event Logs, SP Logs)• Balance / Organize Content Databases

Root sites “Issue Sites” in their own DBs

Upgrade PlanningEnvironment Cleanup


• Virtualization• Use Snapshots between steps

OS Install SP Install Farm Configuration Etc.

• Storage & I/O• Farm Build

Scripted Process• Service Accounts

New or Old• Identify new service / service application requirements

Upgrade PlanningEnvironment Build-out


• Solutions• Features• Site Definitions• web.config modifications• Custom Files / Images

• What did your Farm Survey say?

• Use the Upgrade Worksheet http://www.microsoft.com/en-us/download/details.aspx?id=30370

Upgrade PlanningCustomizations Deployment



Microsoft Benchmark Operations Schedule

Note: • Planned 36 hours outage• Up to 54 hours emergency outage if rollback is required• Downtime mitigation process can reduce outage time

Upgrade PlanningOperations Scheduling

Schedule Operation

Friday 2200hrs Start backups

Saturday 0000hrs Start upgrade of content farm/databases

Sunday 1200hrs

Upgrade must be effectively complete, or rollback of environment must begin

Monday 0600hrs

Environment must be completely working, either as original version or new version


• DNS, Load Balancer, Service Applications, SQL Locks• Draw a line in the sand

How long does it take to implement? How long does it take to rollback?

• Test, Test and Re-Test processes AND procedures• Prepare communication

Upgrade PlanningRollback Plan


Later Today• Post-Upgrade Activities• Ongoing Support Calls

Upgrade PlanningAfter Upgrade


Upgrade Overview


Poll

• What are your “largest”, “time consuming”, “hardest to overcome” issues with SharePoint Upgrades?


• Customizations• Available Disk Space• Customizations• Resource Constraints (I/O, Memory, Time)• Customizations• Testing (or lack thereof)• Customizations• Knowledge

• Customizations

Upgrade OverviewTypical Issues


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

Upgrade OverviewOOB Upgrade Scenarios


• Compatibility Levels / Compatibility Ranges• Self-Service Site Collection Upgrade• Evaluation Site Collection• Site Collection Health Checks• System Notifications / Email templates

Upgrade OverviewWhat’s New


• 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

Upgrade OverviewWhat’s New – Compatibility Ranges / Compatibility Levels

http://technet.microsoft.com/en-us/library/ff607534.aspx



• 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

Upgrade OverviewWhat’s New – Self-Service Site Collection Upgrade


• Web Application Properties Allows Site Collection Administrators Self-Service Evaluation

• $webApp = Get-SPWebApplication https://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)


https://portal.company.com/


• Site Collection Properties Self-Service properties

• $site = Get-SPSite https://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)




Upgrade OverviewUpgrade Site Collection – End User Service-Service User Experience


• 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-SPContentDatabase WSS_Content Get-SPUpgradeSessionInfo -ContentDatabase $db [-HideWaiting] [-ShowFailed] [-

ShowInProgress]

$site = Get-SPSite https://portal.company.com/sites/sitecollectionurl Get-SPUpgradeSessionInfo -Site $site


Upgrade OverviewUpgrade Site Collection – PowerShell

http://technet.microsoft.com/EN-US/library/fp161257.aspx





• 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

Upgrade OverviewWhat’s New – Evaluation Site Collection


Upgrade OverviewRequest Evaluation Site – End User Service-Service User Experience


• Submit Request $site = Get-SPSite

https://portal.company.com/sites/sitecollectionurl Request-SPUpgradeEvaluationSite $site [-Email] [-NoUpgrade]


Upgrade OverviewRequest Evaluation Site – PowerShell



• 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

Upgrade OverviewWhat’s New – Site Collection Health Checks

http://technet.microsoft.com/en-us/library/jj219720.aspx



Upgrade OverviewSite Collection Health Checks – End User Service-Service User Experience


• 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

Upgrade OverviewSite Collection Health Checks – PowerShell






• 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

Upgrade OverviewWhat’s New – System Notifications / Email Templates


• 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 first2010

$webApp = Get-SPWebApplication https://portal.company.com$webApp.UseClaimsAuthentication = $true$webApp.Update()$webApp.MigrateUsers($true)

2013$webApp = Get-SPWebApplication https://portal.company.comConvert-SPWebApplication $webApp -To Claims -RetainPermissions

TechNet Reference: http://technet.microsoft.com/en-us/library/jj219696.aspx

Upgrade OverviewWhat’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


http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spsiteupgradethrottlesettings_properties.aspx




• 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



• 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



• Service Application Upgrade 2010 environment CAN consume 2013 service applications Will not utilize new features until web applications are in 2013 mode

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)

Upgrade OverviewWhat’s Different – Improved


• Service Application Upgrade (continued…) Search

• Restore-SPEnterpriseSearchServiceApplication (Upgrades Search Admin DB)– Does NOT retain index– Auto-generates other search database names … GUIDS

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”)



• Service Application Upgrade (finally…) 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)



• PowerShell Cmdlets

• 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



• 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

Upgrade OverviewWhat’s Different – Removed


Break


Upgrade Cycle


Upgrade CycleLearn

• Upgrade methods• New capabilities• Downtime mitigation

Prepare• Document

environment• Manage

customizations• Plan upgrade strategy• Make items

upgradable

Test• Build test farms• Use real data• Evaluate techniques• Find issues early

Implement• Build/upgrade farms• Deploy

customizations• Minimize downtime• Monitor progress

Validate• Troubleshooting• Upgrade event

failures• UI/UX issues• Data issues


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”

Upgrade CycleLearn




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

Upgrade CycleLearn


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!!

Upgrade CyclePrepare


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)



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



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

Upgrade CyclePrepare – 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



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



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

Upgrade CycleTest


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

Upgrade CycleTest


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

Upgrade CycleTest


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

Upgrade CycleImplement


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

Upgrade CycleImplement


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

Upgrade CycleValidate


Site Sampling• Choose all high impact / visibility sites• Choose some simple sites

Get at least one of each site definition• Choose most high customized sites

• Ensure what you are validating WORKED before upgrade

Verify Services• New Service Application functionality• Upgraded Service Application functionality

Customizations• 2010 AND 2013 mode• Might need to deploy to -CompatibilityLevel All

User Experience• Master Pages, Page Layouts• CSS and Themes

Upgrade CycleValidate


Demo

• Service Application Upgrade• Evaluation Site Collection• Site Collection Upgrade


Post Upgrade


• You WILL miss something

• Solutions / Features

• Templates / Definitions Remove PowerPoint Broadcast Remove Office Web Application Cache Fab 40 … don’t go there

• Large Lists / Wide Lists

• User Experience Use Site Collection Health Checks to help

• Unghosted pages• Non-reghostable pages

Incompatible HTML

Post UpgradeFixing Issues


• If not already, at least be on March 2013 PU It’s the NEW RTM

SharePoint Foundation 2013: http://support.microsoft.com/kb/2768000 SharePoint Server 2013: http://support.microsoft.com/kb/2767999

• For Cumulative Updates and Service Packs (B2B), same cycle applies Learn Prepare Test Implement Validate

Post UpgradePatching

http://support.microsoft.com/kb/2768000





• Support calls WILL happen “something changed” “what is this new button”

• Who will receive support calls? Can they solve the problems Do they have permissions to do so What is the escalation process

• Proactive vs. Reactive Support

Post UpgradeSupport


Resources


Communication Plan• http://technet.microsoft.com/en-us/library/cc263345.aspx

Upgrade Worksheet• http://www.microsoft.com/en-us/download/details.aspx?id=30370

How to Test Upgrade• http://www.microsoft.com/en-us/download/details.aspx?id=30366

Run site collection health checks in SharePoint 2013• http://technet.microsoft.com/en-us/library/jj219720.aspx

Hardware and software requirements for SharePoint 2013• http://technet.microsoft.com/en-us/library/cc262485.aspx

SharePoint 2013 training for IT pros• http://technet.microsoft.com/en-US/sharepoint/fp123606

References











http://technet.microsoft.com/en-US/sharepoint/fp123606




Test-SPSite• http://technet.microsoft.com/EN-US/library/fp161259.aspx

Repair-SPSite• http://technet.microsoft.com/EN-US/library/fp161269.aspx

Upgrade-SPSite• http://technet.microsoft.com/EN-US/library/fp161257.aspx

Get-SPSiteUpgradeSessionInfo• http://technet.microsoft.com/EN-US/library/fp161278.aspx

Request-SPupgradeEvaluationSite• http://technet.microsoft.com/EN-US/library/fp161282.aspx

Convert-SPWebApplication• http://technet.microsoft.com/en-us/library/jj219696.aspx

Install-SPSolution• http://technet.microsoft.com/en-us/library/ff607534.aspx

SPWebApplication.SPSiteUpgradeThrottleSettings• http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spsiteupgradethrottlesettings_properties.aspx

Technical References

















Last But Not Least

• Please Fill Out Evaluations• Drawings for Giveaways• Today’s Presenter:

Brian Caauwe Email: [email protected] Twitter: @bcaauwe Blog:


Thanks for coming!




Meeting # 105 Welcome to the Minnesota SharePoint User Group September 11 th, 2013 SharePoint...

Documents

Transcript of Meeting # 105 Welcome to the Minnesota SharePoint User Group September 11 th, 2013 SharePoint...