1. SPTechCon
The SharePoint
Technology Conference
SharePoint 2013
Upgrade Planning For The End User:
What You Need To Know
Presented By: Richard Harbridge
#SPTechCon @RHarbridge
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
2. SPTechCon
The SharePoint
Technology Conference
Who am I?
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
3. SPTechCon
The SharePoint
Technology Conference
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
4. SPTechCon
The SharePoint
Technology Conference
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
5. SPTechCon
The SharePoint
Technology Conference
Our Goal Today…
From Here To Here
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
6. SPTechCon
The SharePoint
Technology Conference
What Will We Cover Today?
• Why Do We Need Upgrade Planning For the End User?
• What Is The End User Responsible For?
• Motivating Users To Learn SharePoint 2013
• Examples Of New Features & Impact On End Users
• What Is IT Responsible For That Impacts End Users?
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
7. SPTechCon
The SharePoint
Technology Conference
Why Do We Need
Upgrade Planning
For The End User?
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
8. Upgrading Almost Always Involves
Restructuring Content
Costs Associated
With Restructuring
Technology Upgrade Costs
#SPTechCon @RHarbridge
9. Many Times Upgrading Actually
Means “Migrating”
Migration Process
For Office 365 Migrations
Assessment
Analyze Existing
Identify Source Determine
Determine Content Assess Office 365
Content To Be Ownership Of
Migration Priority (Location, Quantity, Environment
Migrated Content
Solutions)
Preparation
Clean Up Content/ Define Migration Prepare Office 365 Create New Site(s)
Define Content Map
Content Refresh Schedule Environment In Office 365
Migration
Migrate Content
Based On Map/ Resolve Issues
Schedule
Validation
Testing/
Validate Content Owner Review Of
Based On Content Content (Training
Map/Schedule Opportunity)
Approved
Post Migration
Delete Source
Launch New Site Set Source Content
Plan Launch Efforts Review Feedback Content That Has
#SPTechCon @RHarbridge (w/ Training) To Read Only
Been Migrated
10. Upgrade Planning Must
Include Notification Planning
Prepared User
Unprepared User
#SPTechCon @RHarbridge
11. 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?
Prepared User
That sucks, but you gave
me some acceptable
workarounds, training, and
support… and I know it’s
not IT’s fault.”
#SPTechCon @RHarbridge
12. 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 Unprepared User
upgrade any of the sites we
work with either! Rawrrrr!”
#SPTechCon @RHarbridge
13. Quick Sample List Of End User
Impacts On An Upgrade
1. 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)
#SPTechCon @RHarbridge
14. No In-Place Upgrade
More likely that the user will have (for a transition period)
some sites in 2010 and some sites in 2013.
#SPTechCon @RHarbridge
20. 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
#SPTechCon @RHarbridge
complete.
25. 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…
#SPTechCon @RHarbridge
26. What Do Users Need
To Know From IT?
• 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…
#SPTechCon @RHarbridge
27. 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?
#SPTechCon @RHarbridge
28. SPTechCon
The SharePoint
Technology Conference
What Is The End User
Responsible For?
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
29. 1. Delete Unused/Evaluate Underused
Site Collections & Sub Sites
Not every ‘unused’ site collection or
‘old’ site collection should be deleted.
Example: Emergency Preparedness Site
#SPTechCon @RHarbridge
30. 2. Delete Unnecessary Versions
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.
#SPTechCon @RHarbridge
Before Digital File Shares SharePoint
31. 3. Identify Unused Templates,
Features & Web Parts
#SPTechCon @RHarbridge
32. 4. Finish Visual Upgrades In 2010
Environment w/ IT
#SPTechCon @RHarbridge
33. 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…
#SPTechCon @RHarbridge
35. SPTechCon
The SharePoint
Technology Conference
Motivating End Users
To Learn
SharePoint 2013
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
36. What Are The Business Benefits Of
Upgrading To SharePoint 2013?
1. End User Improvements That Lead To Increased
Productivity & Adoption
2. Social Improvements Can Be A Significant Driver
3. The New Search Experience & Engine Can Transform
Your Organizations View On Search
4. Technical Benefits
(Storage, Site Collection Level Control, Etc)
5. Solution Benefits
(eDiscovery, Language, Doc Sets, WCM+, Etc)
#SPTechCon @RHarbridge Article: http://www.rharbridge.com/?p=875
38. Previews are Awesome
Office 2013 and the
Office 2013 web apps
can encourage users to
migrate/upgrade faster.
Consider tying the
2013 and Windows
8 upgrades to
SharePoint.
#SPTechCon @RHarbridge
39. Focus On Content
Are your pages ready for
wider displays when users
choose to ‘focus’ on
content and hide the
quick launch?
Is this a feature you
already plan on using for
those wide lists/pages?
#SPTechCon @RHarbridge
40. 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
#SPTechCon @RHarbridge
41. Themes Can Add (Simple) Sex Appeal
#SPTechCon @RHarbridge
45. SPTechCon
The SharePoint
Technology Conference
Examples Of New
Features & User Impact
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
46. iFrames & External Content
What is it?
• In SharePoint 2013 content authors can insert an
iframe element into an HTML field on a page.
Why does it matter?
• This lets content authors embed dynamic content from other
sites, such as videos or map directions.
What does a user have to do on upgrade?
• By default, certain trusted external domains are already approved for
use in iframes. Site collection administrators can customize the field
security settings by changing the default trusted external domains.
They can also allow content authors to insert iframes for any external
domain, or prevent them from inserting iframes on any page. (HTML
#SPTechCon @RHarbridge
Field Security Settings)
47. Content Search Web Part
What is it?
• A new web part that allows a user to roll up aggregated content across
sites, site collections or the entire farm (unrestricted).
Why does it matter?
• Rolling up content across sites and site collections removes barriers
and helps improve productivity when working across many locations.
What does a user have to do on upgrade?
• If the organization doesn’t have an alternative component for cross site
collection roll up then this is the perfect opportunity to begin using
this.
• If the organization does have an alternative component for cross site
#SPTechCon @RHarbridge it may be worth evaluating replacing it with this web
collection roll up,
part where appropriate.
48. Image Renditions
What is it?
• Image renditions let you display different sized versions of an image on
different pages.Users can select the image rendition they want when
modifying page content under the ‘Pick Rendition’ option.
Why does it matter?
• Not only does the image often look better when set to a smaller size
(using renditions) but it also can be an extremely small fraction of the
image size.
What does a user have to do on upgrade?
• By default, the image preview that is displayed for an image rendition is
generated from the center of the image. Unfortunately this also means
many need to be adjusted throughout your publishing sites (if you
#SPTechCon @RHarbridge
intend to use this feature).
49. SPTechCon
The SharePoint
Technology Conference
What Is IT Responsible For
That Impacts Users?
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
52. 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.
#SPTechCon @RHarbridge
53. Spring Cleaning For A Healthy Farm
• Delete stale SPSites help
and SPWebs (w/ User • Finish Visual Upgrades
Approval) to 14
• Remove extraneous • Repair data issues
document versions – stsadm -o
– Primarily user DatabaseRepair [-
driven, code or tools deletecorruption]
help – stsadm -o
• Cleanup ForceDeleteList
templates, features, & – stsadm -o
web parts VariationsFixupTool
– Primarily user – Etc…
driven, code or tools
#SPTechCon @RHarbridge
54. 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…
#SPTechCon @RHarbridge
55. Address Wide Lists?
What are wide lists (lists with too many Column Type Number Of
columns)? Columns
Wide lists are lists with more columns than fit (Table Row)
in a single rowspan in the content database. Single Line Of Text 64
During upgrade, the database is changed to a Choice 32
sparse table structure, and a very wide list can
cause upgrade to fail. Use the Test- Date & Time 8
SPContentDatabase command in Windows Yes/No 16
PowerShell to look for wide lists in the content
Number/Currency 12
databases and then remove extra columns
before you upgrade. Calculated 8
Integer, Lookup, People & 16
http://technet.microsoft.com/en- Group, Managed Metadata
us/library/ff382641%28v=office.15%29
Unique ID 1
#SPTechCon @RHarbridge
56. 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.
#SPTechCon @RHarbridge Microsoft ‘suggests you consider it’.
Richard says you should do it (at a minimum).
58. Remove PowerPoint Broadcast Sites
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.
Get-SPSite | Where-Object{$_.RootWeb.Template -eq "PowerPointBroadcast#0"} | Remove-SPSite
#SPTechCon @RHarbridge
59. 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
#SPTechCon @RHarbridge
60. SPTechCon
The SharePoint
Technology Conference
Thank You
Organizers, Sponsors and You for Making this Possible.
Questions? Ideas? Feedback? Contact me:
Twitter: @RHarbridge
Blog: http://www.RHarbridge.com
Email: Richard@RHarbridge.com
Resources:
90+ SharePoint Presentations at.. SlideShare.net/RHarbridge
130+ SharePoint Standards at.. SPStandards.com
15 Pages of Important Questions at.. SharePointDiagnostics.com
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
61. SPTechCon
The SharePoint
Technology Conference
Content Description
SharePoint 2013 Products Preview - Upgrade Describes the steps in the process for a database-attach upgrade.
Process model
SharePoint 2013 Products Preview - Test Your See a visual display of information about how to test the upgrade process.
Upgrade Process model
SharePoint 2013 Products Preview Upgrade Use this worksheet to record information about your environment while you test upgrade.
Worksheet
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 Find resources about how to test and troubleshoot an upgrade from SharePoint 2010
SharePoint 2013 Products to SharePoint 2013.
Upgrade databases from SharePoint 2010 to Find resources to help you perform the steps to upgrade databases from SharePoint 2010
SharePoint 2013 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 Visit the Resource Center to find additional information about upgrades to SharePoint 2013.
SharePoint 2013 Products
Capabilities and features in SharePoint 2013 Visit the Resource Center to learn about what’s new in SharePoint 2013.
Resource Center
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
62. SPTechCon
The SharePoint
Technology Conference
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 Get a visual overview of the steps involved in performing an upgrade.
2013
Services upgrade overview for SharePoint SharePoint 2010 Products included several service applications, some of which have
Server 2013 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 In SharePoint Server 2010, it was possible to configure parent farms and child farms to share
child farms) to SharePoint 2013 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 Understand the requirements for upgrade. And if you are planning to change SKUs or
upgrading to SharePoint 2013 products during upgrade, understand which upgrade paths are supported.
SPTechCon
The SharePoint
#SPTechCon @RHarbridge
Technology Conference
Notes de l'éditeur
Surprises are good for birthdays, not for business planning.
An email should be sent out to Site Collection admin when the temporary site is provisioned.
When and what to communicate to the upgrade teamIn general, the server administrators and service application administrators set the timeline for upgrade, and site owners are notified only when the process is about to begin. However, because team members have their own tasks to perform at particular points in the overall upgrade process, it is very important that you have a solid plan to communicate the progress of the upgrade to all team members so that everyone knows when it is time to perform their particular tasks. The whole upgrade team must work together to determine the dates and times to perform the upgrade. We recommend that you choose an upgrade window to occur when site usage is lowest. For small single-server deployments, upgrade may be completed in less than a day. Larger deployments can take more time, up to a weekend. There is no way to determine the precise length of time that will be required to upgrade any particular site collection. Because of this, it is very important to communicate with other team members involved in the upgrade process in addition to users. The day or days that you choose for upgrading should be far enough in the future that the upgrade team has enough time to complete all of the preliminary steps. When you plan the timeline, make sure that you schedule time to validate the upgraded sites and time to implement any changes or do any work to re-brand sites.It is important to communicate with site owners, designers, and developers at the following points during the upgrade process:Before the trial upgrade so that they know the general timeline and their roles in the process.After you perform a trial upgrade to find issues. For example, issues such as customized site templates or custom Web Parts should be reported to the appropriate site owner, designer, or developer before you schedule the upgrade, to give them time to investigate the issues and take preliminary steps. Or a developer might decide that it would be prudent to rebuild a Web Part before the upgrade occurs. And site owners might want to note any customizations that were done to their sites, such as site templates and changes to core Active Server Page Extension (ASPX) files. After the environment is upgraded so that they can review the sites and make any changes that are needed.When you are ready for them to upgrade their site collections.When and what to communicate to site usersIt is equally important to communicate with the users of the sites to tell them about the following issues: When the environment will be upgraded In particular, you must also inform them if their sites will be unavailable during the upgrade.When their sites will upgraded Site collection owners should communicate to their site users about the timeline for upgrading the site collection. If you, as a server farm administrator, are upgrading a site, you should communicate when that will occur.How the upgrade might affect them and what they should know about the new environment For example, the site will look different and function slightly differently in the new user interface. You can also point them to available content, such as What's New articles or training materials, to learn about the new version. For more information about feature changes, see What's new in SharePoint Server 15 Beta.How to obtain help If they find an issue with their site after upgrade, how can they obtain help in addressing it?You can use the new system status bar in the site collections to notify users of these items.
During an upgrade from the server products in the Office 2007 release to SharePoint 2010 Products, you could allow site owners to use Visual Upgrade to keep sites in the old experience on the upgraded environment. When you upgrade to SharePoint 2013 Preview, all sites that are still in the old experience in SharePoint 2010 Products are automatically upgraded to the 2010 experience. If you want the opportunity to address any issues and review the sites before they are switched to the new experience, upgrade them to the new experience in your SharePoint 2010 Products environment and review them before you upgrade them to SharePoint 2013 Preview. We recommend that you finish visual upgrades before you upgrade to SharePoint 2013 Preview. Finishing visual upgrades before you upgrade provides the following benefits:You can address issues while you still have the server products in the Office 2007 release components available.You can have users be involved in reviewing and fixing issues in their sites.You can roll back to the old experience temporarily if it is necessary. You cannot roll back when you are in the SharePoint 2013 Preview experience.You avoid adding potential errors to the upgrade process. The fewer operations occurring during upgrade, the better. Trying to troubleshoot errors is more difficult when you have more processes involved. And users might think that upgrade has caused an issue when it's really the experience changing to the new version. If you have an issue with how the site interface is displaying, how will you know whether it is an old issue from the site that was forced through visual upgrade, a problem with the 2010 mode in SharePoint 2013 Preview, or a problem with a new CSS file?To check for sites in the old experience, on the SharePoint 2010 Products environment, you can use the Get-SPSite Windows PowerShell command.To check for and upgrade sites still in the old experience in the SharePoint 2010 Products environment by using Windows PowerShellVerify that you have the following memberships:securityadmin fixed server role on the SQL Server instance.db_owner fixed database role on all databases that are to be updated.Administrators group on the server on which you are running the Windows PowerShell cmdlets.An administrator can use the Add-SPShellAdmincmdlet to grant permissions to use SharePoint 2013 Preview cmdlets.Note: If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin.On the Start menu, click All Programs.Click Microsoft SharePoint 2010 Products.Click SharePoint 2010 Management Shell.At the Windows PowerShell command prompt, type the following command to return all site collections that are in or have subwebs in the old experience:Get-SPSite | ForEach-Object{$_.GetVisualReport()} At the Windows PowerShell command prompt, type the following command to upgrade those sites to the new experience:Get-SPSite | ForEach-Object{$_.VisualUpgradeWebs()} For more information, see Get-SPSite and Manage visual upgrade (SharePoint Server 2010).
MicrobloggingShare content, links, and mediaFollow people, sites, content, and conversationsActivity FeedsProvides a view into recent activity related to content, links, media, and peopleCommunitiesCommunity sites with self-service administration and moderationModern community features such as achievements and reputationDiscussionsModern discussion boardsBlogsClient application integrationCategories, comments, and moderation
New Search architecture with one unified searchPersonalized search results based on search historyRich contextual previews
Technical Details:Requires: Blob Caching to be enabled for the web application. (To minimize performance impact due to dynamic generation of images.)Adding Your Own: Additional renditions can be configured for the site collection under Site Settings > Look and Feel > Image Renditions.Stored: In the site collection /_catalogs/masterpage/PublishingImageRenditions.xml file.Supported Image Types: gif, jpg, jpeg, jpe, jfif, bmp, dib, png, tif, tiff, ico, wdp, hdp. Supported Video Types:wmv, wma, avi, mpg, mp3, mp4, asf, ogg, ogv, oga, webm.Changing Image Rendition Dimensions: Since image renditions are versioned after you change the dimensions you have to re-edit all images to crop the image according to the new dimensions.
A lot of this can seem daunting and I know one of the hardest things is figuring out how to do some of the things I have shown today. If you are interested in further training or assistance please let me know. Based on the number of people who are interested and the areas of interest we can schedule further training sessions to help everyone better use the SharePoint portal.It's our commitment to you that we will continue to hear your feedback and identify the issues. I encourage you to give us feedback during the coming months, and we will continue to deliver more and more functionality, more and more guidance to help you be successful with your application of SharePoint.Thank You for Reading/Listening
