don't upgrade to sharepoint 2013

37
Don’t upgrade to SharePoint 2013! - David Lozzi, Slalom Consulting

Post on 19-Oct-2014

3.139 views

Category:

Technology


1 download

DESCRIPTION

My presentation from the Boston SharePoint User Group. We discussed upgrading, and weighing the costs around infrastructure, customizations and training. We also walk through 2 methods of upgrading from SharePoint 2010.

TRANSCRIPT

Page 1: Don't upgrade to SharePoint 2013

Don’t upgrade to SharePoint 2013!

- David Lozzi, Slalom Consulting

Page 2: Don't upgrade to SharePoint 2013

Who am I?

SharePoint Architect with Slalom Consulting

Mail: [email protected]

Twit: @DavidLozzi

Blog: www.davidlozzi.com

Page 3: Don't upgrade to SharePoint 2013

SHAREPOINT 2013WHAT’S ALL THE EXCITEMENT FOR?

Page 4: Don't upgrade to SharePoint 2013

Maybe before we rush to adopt SharePoint 2013 we

should stop to consider the consequences of

blithely giving this technology such a central

position in our lives…credit: http://xkcd.com/1215/

Page 5: Don't upgrade to SharePoint 2013
Page 6: Don't upgrade to SharePoint 2013

What’s all the excitement for?

Search is robust and the core of most of what you see.

Social computing

New site templates, communities

Apps & Marketplace

Mobile device support

Supports browsers other than IE

Branding, design, look and feel

SkyDrive Pro

Task List Aggregation

Cross-Site Publishing

Web content management

Shredded storage

Page 7: Don't upgrade to SharePoint 2013

Doesn’t everyone just upgrade anyway?

Current installed SharePoint versions. Source: Metalogix Survey from SPC 2012

Page 8: Don't upgrade to SharePoint 2013

WHEN IS THE RIGHT TIME TO UPGRADE?

Page 9: Don't upgrade to SharePoint 2013

Now!

Just do it.

If it’s newer, it’s better.

It’s shiny.

Why that’s bad

If it’s not broke, don’t fix it

Guinea pig

Windows ME, Vista, (8?)

Page 10: Don't upgrade to SharePoint 2013

Self-Justification

The Joneses

Happier users

Stay current

Why that’s bad

Not the right fit

Doesn’t benefit the overall business goals

Page 11: Don't upgrade to SharePoint 2013

See a need, fill a need

Does it make sense

Fit into your requirements

Features vs cost

Why that’s bad

Um, it isn’t

Page 12: Don't upgrade to SharePoint 2013

What’s all the excitement for?

Search is robust and the core of most of what you see.

Social computing

New site templates, communities

Apps & Marketplace

Mobile device support

Supports browsers other than IE

Branding, design, look and feel

SkyDrive Pro

Task List Aggregation

Cross-Site Publishing

Web content management

Shredded storage

Page 13: Don't upgrade to SharePoint 2013
Page 14: Don't upgrade to SharePoint 2013

End of Life

Source: http://support.microsoft.com/lifecycle/search/default.aspx

Mainstream: MS’s normal support options

Extended: No free incident support, warranty claims, design changes/requests, but you still get security updates, paid support, and web based support (KB).

Version Mainstream Extended

SharePoint 2013 4/10/2018 4/11/2023

SharePoint 2010 10/13/2015 10/13/2020

SharePoint 2007 10/9/2012 10/10/2017

SharePoint 2003 4/14/2009 4/8/2014

Page 15: Don't upgrade to SharePoint 2013

What’s the cost to upgrade?

Page 16: Don't upgrade to SharePoint 2013

What’s the cost?

Increased hardware requirements

New servers, licenses, CALs

No In-Place upgrade option, use detach/attach method

It’s a migration process, to a new farm

SP2010

Page 17: Don't upgrade to SharePoint 2013

What’s the cost?

Upgrading from 2007, requires upgrading to 2010 first, then upgrade to 20133rd party solutions available

Upgrading from 2003, good luck

SP2007 SP2010

Page 18: Don't upgrade to SharePoint 2013

What’s the cost?

Upgrade custom solutions

Move to 2013 Apps?Farm solutions

Sandbox solutions

Visual Studio 2012 for developers

Development environments

Rebuild branding to fit 2013 styling

Implement the enterprise application store

Page 19: Don't upgrade to SharePoint 2013

What’s the cost?

TrainingDevelopers: new APIs, Apps model, etc.

Users and power users

IT administration and maintenance

User Adoption

Page 20: Don't upgrade to SharePoint 2013

Will you upgrade?

Page 21: Don't upgrade to SharePoint 2013

YES I WANT TO UPGRADE!

Page 22: Don't upgrade to SharePoint 2013

Upgrade from 2010

Create a new SP2013 Farm

Detach/attach databases

Apply customizations

Upgrade site collections

SP2010

Page 23: Don't upgrade to SharePoint 2013

GOING

Page 24: Don't upgrade to SharePoint 2013

Hybrid

It’s all the craze, energy savings, save gas, it’s cool…

Running multiple farms/environments in multiple versions to leverage the best features to fit your needs

Allows for a stepped approach to upgrading

Page 25: Don't upgrade to SharePoint 2013

HybridNumber of farms at an organization

Source Metalogix Survey from SPC 2012

Page 26: Don't upgrade to SharePoint 2013

Hybrid

Source: Metalogix Survey from SPC 2012

Page 27: Don't upgrade to SharePoint 2013

Keep your SharePoint 2010 farm

SP2010

Page 28: Don't upgrade to SharePoint 2013

Create a SharePoint 2013 farm

Page 29: Don't upgrade to SharePoint 2013

Upgrade Service Applications

Business Data Connectivity

Managed Metadata

Performance Point

SP2010

Secure Store

Search

User Profile

Page 30: Don't upgrade to SharePoint 2013

Configure and publish 2013 services

Page 31: Don't upgrade to SharePoint 2013

Consume services on 2010

SP2010

Page 32: Don't upgrade to SharePoint 2013

Migrate site collections to SP2013SP2010

Page 33: Don't upgrade to SharePoint 2013

Additional SP2013 farms

SP2010

Page 34: Don't upgrade to SharePoint 2013

Go to

SP2010

Page 35: Don't upgrade to SharePoint 2013

Bringing it home

Page 36: Don't upgrade to SharePoint 2013

Should I Upgrade?

Or Shouldn’t I?

Page 37: Don't upgrade to SharePoint 2013

Should I Upgrade?Search is robust and the core of most of what you see.

Social computing

New site templates, communities

Apps & Marketplace

Mobile device support

Supports browsers other than IE

Branding, design, look and feel

SkyDrive Pro

Task List Aggregation

Cross-Site Publishing

Web content management

Shredded storage

Increased hardware requirements

New servers, licenses, CALs

No In-Place upgrade option, use detach/attach method

It’s a migration process, to a new farm

Upgrading from 2007, requires upgrading to 2010 first, then upgrade to 2013

Upgrading from 2003, good luck

Upgrade custom solutions

Move to 2013 Apps

Visual Studio 2012 for developers

Development environments

Rebuild branding to fit 2013 styling

Implement the enterprise application store

Training

User Adoption

vs