sharepoint 2013 upgrade planning for the business: what you need to know
TRANSCRIPT
#SPSBoston @RHarbridge
Presented By: Richard Harbridge
Upgrade Planning For The Business:What You Need To Know
My Name Is Richard Harbridge…
What Will We Cover Today?• Why Do We Need Upgrade Planning For the Business?
• What Is The Business Responsible For?
• Motivating The Business To Learn SharePoint 2013
• What Is IT Responsible For That Impacts The Business?
#SPSBoston @RHarbridge
Presented By: Richard Harbridge
#SPSBoston @RHarbridge
Upgrading Almost Always
Involves Restructuring
ContentCosts Associated With Restructuring
Technology Upgrade Costs
#SPSBoston @RHarbridge
Migration Process
Pre
par
atio
nA
sses
smen
tM
igra
tio
nTe
stin
g/V
alid
atio
nP
ost
Mig
rati
on
For Office 365 Migrations
Analyze Existing Content
(Location, Quantity, Solutions)
Determine Migration Priority
Create New Site(s) In Office 365
Validate Content Based On Content
Map/Schedule
Launch New Site (w/ Training)
Assess Office 365 Environment
Identify Source Content To Be
Migrated
Determine Ownership Of
Content
Clean Up Content/Content Refresh
Prepare Office 365 Environment
Define Content Map
Owner Review Of Content (Training
Opportunity)
Migrate Content Based On Map/
Schedule
Define Migration Schedule
Approved
Delete Source Content That Has
Been Migrated
Set Source Content To Read Only
Review Feedback
Resolve Issues
Plan Launch Efforts
Many Times Upgrading Actually
Means “Migrating”
#SPSBoston @RHarbridge
Prepared User
Unprepared User
Upgrade Planning Must
Include Notification Planning
#SPSBoston @RHarbridge
Prepared User
What Happened To My
SharePoint Designer “Design”
View? “Design view is gone? It’s really difficult to update my existing customizations, data view web parts, and solutions?
That sucks, but you gave me some acceptableworkarounds, training, and support… and I know it’s not IT’s fault.”
#SPSBoston @RHarbridge
Unprepared User
What Happened To My
SharePoint Designer “Design”
View?“Design view is gone?! *Censored ranting+…
There is no way in [Censored] I am letting you upgrade my sites.
Everything is business critical. I don’t want you to upgrade any of the sites we work with either! Rawrrrr!”
#SPSBoston @RHarbridge
Quick Sample List Of End User
Impacts On An Upgrade1. No Design View in SharePoint Designer 2013 2. No Breadcrumb (By Default) 3. Create Sub Site Has Moved 4. No Sign In As a Different User 5. App Naming & Organization (For Those Who Are Used To
Previous Methods For Creating New Lists/Libraries The App Naming Can Be Confusing)
6. Share Instead Of Manage Permissions (Better Than Previous Model, But Requires Explanation)
#SPSBoston @RHarbridge
No In-Place Upgrade
More likely that the user will have (for a transition period) some sites in 2010 and some sites in 2013.
#SPSBoston @RHarbridge
Users Can Try A Demo Upgrade
Sends an email to the Site Collection Admin when queue and eval site creation is complete.
• The “Upgrade Evaluation Site Collection” must be clearly communicated as NOT FOR REAL USE as it expires in 30 days – noted in a bar at the top.
• It also creates a copy of the site collection, so depending on search settings, and storage this can have significant ramifications (beyond just the performance implications).
• Depending on SQL (non enterprise) this may set the site to ‘read only’ until creation is complete.
#SPSBoston @RHarbridge
What Is The Business Responsible For?
34
1. Coordinate 2. Delete 3. Delete
4. Identify5. Re-Create6. Finish The
Upgrade
7. Learn SharePoint
2013
8. Adopt SharePoint
2013
#SPSBoston @RHarbridge
• Identify & Help Engage Content Owners• Identify Business Solutions• Support Prioritization Of Content Being Upgraded• Support Testing & Validation Of Upgrade Success
1. Coordinate With IT
#SPSBoston @RHarbridge
2. Delete Unused/Evaluate Underused Site Collections & Sub Sites
Not every ‘unused’ site collection or ‘old’ site collection should be deleted. Example: Emergency Preparedness Site
#SPSBoston @RHarbridge
3. Delete Unnecessary Versions
Before Digital File Shares SharePoint
Hopefully you already limit the number of versions whenever versioning is enabled…
If you don’t – the upgrade provides a reminder (and benefit) to adjusting and evaluating versioning and previous stored versions of documents.
#SPSBoston @RHarbridge
5. Re-Create Site Templates
From 2010 Only A Few…• Document Workspace• Meeting Workspace• Group Work Site• Personalization Site• Visio Process Repository (Not Removed, But Will Be)
From 2007 All Site Templates…
#SPSBoston @RHarbridge
8. Adopt SharePoint 2013
Adoption Activities Listing
#SPSBoston @RHarbridge
1. End User Improvements That Lead To Increased Productivity & Adoption
2. Social Improvements Can Be A Significant Driver3. The New Search Experience & Engine Can
Transform Your Organizations View On Search4. Technical Benefits
(Storage, Site Collection Level Control, Etc)5. Solution Benefits
(eDiscovery, Language, Doc Sets, WCM+, Etc)
What Are The Business Benefits Of Upgrading To SharePoint 2013?
Article: http://www.rharbridge.com/?p=875
#SPSBoston @RHarbridge
Sharing Is Easier
Sharing in SharePoint 2013 is designed to mitigate common problems from previous versions:
• Granting access to a site can be a bit convoluted• Users don’t understand what permission level to grant to
other users• Users generally don't know who all has permissions on a
site• Users can’t see the invitations that have been sent out to
external users.• Users don’t understand what rights they are giving people
when they add them to a SharePoint group
#SPSBoston @RHarbridge
Understand The Differences
Article http://www.rharbridge.com/?page_id=966
#SPSBoston @RHarbridge
IT Control Of Upgrade Rollout
Some of the key questions…• When to unlock creating new 2013
Site Collections…• When to allow upgrade of existing Site
Collections…• Whether to give Site Collection
Admins control or not…
#SPSBoston @RHarbridge
Controlling The Site Collection Upgrade Rollout
• Defer upgrade for site collections until you can get updated customizations to support 2013 mode.
• If you wait until the customizations are available, you can complete the initial upgrade of database and services without significantly affecting use of the existing sites in 2010 mode.
#SPSBoston @RHarbridge
• Information on what will happen during transition…• Communication on when their 2013 ‘infrastructure’
upgrade will occur…• Provided directions if using self-service upgrade…• Notifications and reminders for when upgrade must be
completed by…• Self-service upgrade still means getting people to do it
eventually by a specific time
• Notification when the ‘infrastructure’ upgrade is finished…
• What IT support, training, and help will be available…
What Do Users Need
To Know From IT?
#SPSBoston @RHarbridge
What Do Users Need To Know From IT?
• In migration tool driven upgrade scenarios users will need to know what their level of involvement will be.
• They may need training on the migration tools, or the migration process.
• What will change after migration/upgrade?• How will IT be charging or managing the cost for the
migration?• What new services IT will be providing that they can
leverage using SharePoint 2013?
#SPSBoston @RHarbridge
IT Driven Clean Up Activities
• Delete stale SPSites and SPWebs (w/ User Approval)
• Remove extraneous document versions
• Primarily user driven, code or tools help
• Cleanup templates, features, & web parts
• Primarily user
driven, code or tools help
• Finish Visual Upgrades to 14
• Repair data issues• stsadm -o
DatabaseRepair [-deletecorruption]
• stsadm -o ForceDeleteList
• stsadm -o VariationsFixupTool
• Etc…
#SPSBoston @RHarbridge
2007 Only – Address Large Lists
Wait a second… I have SharePoint 2007 (or 2003)!
• Large list views and lists with many lookup columns have performance challenges.
• If you are upgrading to SharePoint 2010 this is also important to understand as the default throttling limits may impact user experience.
• SQL Scripts (Read Only) and API calls can help identify what lists you do have over the default throttle settings, and which have a larger lookup count.
• Preventative Measures: Selectively indexing large list columns can help (up to 10 columns), building smarter more efficient views (1st filter), CAML/Search alternatives…
#SPSBoston @RHarbridge
Address Wide Lists?
What are wide lists (lists with too many columns)?Wide lists are lists with more columns than fit in a single rowspan in the content database. During upgrade, the database is changed to a sparse table structure, and a very wide list can cause upgrade to fail. Use the Test-SPContentDatabase command in Windows PowerShell to look for wide lists in the content databases and then remove extra columns before you upgrade.
http://technet.microsoft.com/en-us/library/ff382641%28v=office.15%29
Column Type Number Of Columns (Table Row)
Single Line Of Text 64
Choice 32
Date & Time 8
Yes/No 16
Number/Currency 12
Calculated 8
Integer, Lookup, People & Group, Managed Metadata
16
Unique ID 1
#SPSBoston @RHarbridge
Number Of Site Collections Per DB
Too many site collections in a content database?If you have 5,000 or more site collections in a database you should break them out into multiple databases.
Why is this necessary?In SharePoint 2010 Products, there was a default warning at 9,000 site collections and a hard limit at 15,000 site collections. In SharePoint 2013 Preview, these values change to 2,000 site collections for the warning and 5,000 site collections for the limit.
Microsoft ‘suggests you consider it’. Richard says you should do it (at a minimum).
#SPSBoston @RHarbridge
PowerPivot Rebuilds
http://www.chrismcnulty.net/blog/Lists/Posts/Post.aspx?ID=51
#SPSBoston @RHarbridge
Remove PowerPoint Broadcast Sites
Get-SPSite | Where-Object{$_.RootWeb.Template -eq "PowerPointBroadcast#0"} | Remove-SPSite
They have to go. Notify users and work with them to migrate key content, but they must be removed or left in a 2010 farm.
#SPSBoston @RHarbridge
Plan New Site Retention Policy
• Site-level retention policies– Compliance levels extended to
sites
– Policies include:
• Retention policy for sites and Team Mailbox associated with site
• Project closure and expiration policy
What Did We Cover Today?• Why Do We Need Upgrade Planning For the Business?
• What Is The Business Responsible For?
• Motivating The Business To Learn SharePoint 2013
• What Is IT Responsible For That Impacts The Business?
• Achieve Greater Success & Meeting Expectations
• Coordination, Validating Readiness, & Cleaning Content
• Use Scenarios & Focus On Meaningful & Immediate Value
• UnderstandingDifferences, Communicating, & Technology
Twitter: @RHarbridge Blog: http://www.RHarbridge.com Email: [email protected] Resources:
50+ User Adoption Activities Adoption Activities130+ SharePoint Standards SPStandards.com35+ Governance Documents Governance Documents80+ Downloadable Presentations SlideShare.com/RHarbridge
Thank You Organizers, Sponsors and You for Making this Possible.
Content Description
SharePoint 2013 Products Preview - Upgrade
Process model
Describes the steps in the process for a database-attach upgrade.
SharePoint 2013 Products Preview - Test Your
Upgrade Process model
See a visual display of information about how to test the upgrade process.
SharePoint 2013 Products Preview Upgrade
Worksheet
Use this worksheet to record information about your environment while you test upgrade.
Get started with upgrades to SharePoint 2013 Find resources to help you understand how to upgrade databases and site collections from
SharePoint 2010 Products to SharePoint 2013.
Plan for upgrade to SharePoint 2013 Find resources about how to plan to upgrade from SharePoint 2010 Products to SharePoint
2013.
Test and troubleshoot an upgrade to SharePoint
2013
Find resources about how to test and troubleshoot an upgrade from SharePoint 2010 Products
to SharePoint 2013.
Upgrade databases from SharePoint 2010 to
SharePoint 2013
Find resources to help you perform the steps to upgrade databases from SharePoint 2010
Products to SharePoint 2013.
Upgrade site collections to SharePoint 2013 Find out how to upgrade a site collection to SharePoint 2013.
Upgrade and Migration Resource Center for
SharePoint 2013 Products
Visit the Resource Center to find additional information about upgrades to SharePoint 2013.
Capabilities and features in SharePoint 2013
Resource Center
Visit the Resource Center to learn about what’s new in SharePoint 2013.
Content Description
What's new in SharePoint 2013 upgrade Find out about new requirements, approaches, and features that are available for upgrading to
SharePoint 2013.
Overview of the upgrade process to SharePoint
2013
Get a visual overview of the steps involved in performing an upgrade.
Services upgrade overview for SharePoint Server
2013
SharePoint 2010 Products included several service applications, some of which have databases
that can be upgraded when you upgrade to SharePoint 2013. Find out which service application
databases can be upgraded and what steps that you must take before, during, and after
upgrade for your service applications.
Upgrade farms that share services (parent and
child farms) to SharePoint 2013
In SharePoint Server 2010, it was possible to configure parent farms and child farms to share
services. In such an environment, the parent farm hosts one or more service applications from
which one or more child farms consume services. Learn how to approach upgrading these
environments to SharePoint Server 2013.
Best practices for upgrading to SharePoint 2013 Get off to the right start - review these best practices for testing and performing an upgrade to
SharePoint 2013.
Review supported editions and products for
upgrading to SharePoint 2013
Understand the requirements for upgrade. And if you are planning to change SKUs or products
during upgrade, understand which upgrade paths are supported.