SharePoint 2010 Virtualization - SharePoint Saturday East Bay 2010
Planning for SharePoint 2013 in our 2010 project
-
Upload
pearcealex -
Category
Technology
-
view
663 -
download
1
description
Transcript of Planning for SharePoint 2013 in our 2010 project
planning for 2013 in our 2010 project
alex pearce
meDirector: BFC Networks
SharePoint MVP since 2008
Twitter: @alex_pearce
Personal Interests in SharePoint
• Office 365
• Integration
• Doing as much as you can with OOTB features
agenda• Why bother about 2013 when we are working so hard on 2010?
• Terminology
• Features
• Branding
• Upgrade consideration
whywhy bother about this?
why bother about 2013 now?• New features that might be better than 2010
• Help make the upgrade process from 2010 to 2013 easier, both from a technical point of view and the end users
• Prepare for future visions and releases of your platform and when you decide to go with 2013
• Training
• Don’t lose adoption rate between versions
terminologynew words, old words, changed words
terminology• Help with training for 2010 and 2013
• Terminology that is there for 2010 but not 2013
• Terminology that has changed or new to 2013
• The end of lists and libraries (to the end user)
lists and libraries
terminology - appwhat does app mean to different people
featuresnew feature such as communities, improved social, higher
integration with exchange and windows
demo – communities
site templates
demo – site templatedifferences between the 2010 team template and the
2013 team template
demo – skydriveoffline sync to the desktop with skydrive
brandingnew masterpage, new design, new ‘metro’ clean cut look
and change of layout
branding• Changes to the general look and feel of 2013
• Additional top navigation
• Terminology changes
• Changes to the standard buttons such as Site Actions
You can brand SharePoint 2010 or 2013 anyway you want. If you want 2010 to look like 2013, than why not, it would help end users transition between versions.
Sam Dolan
upgrade considerations• SharePoint Social: 2010 or 2013
• You cannot run cross service applications between a 2010 and 2013 farm
• Only install the service applications you need in 2010 so you don’t have to upgrade them to 2013 (install them when you actually need to implement them)
• Start in 2010 and move very quickly to 2013 but stay in 2010 mode
what to take away• Re-evaluate requirements from each phrase
• Understand the features you want in 2010 and what they do in 2013
• Understand what the features can do in 2013 that they can’t do in 2010
• User the changes to your advantage (we listened to you and we added this feature) ;-)
• Brand your site to what you want it to look like with 2013
• There are going to be differences so try and minimise them as much as possible
so when do you upgrade?
so when do you upgrade?it depends!