Don't upgrade to SharePoint 2013

4,226 views

Published on

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.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
4,226
On SlideShare
0
From Embeds
0
Number of Embeds
2,106
Actions
Shares
0
Downloads
41
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Out of 100 IT administrators interviewed, just over 30% still have 2007. Upgrading is not always necessary.
  • So you’ve decided to upgrade, its going to happen. But when?
  • Want to upgrade real bad, just need to justify it.
  • So is the requirement here to justify upgrading?
  • 2010 is the XP of SP
  • One more reason, its expired
  • Is the 2007 -> 2010 -> 2013 process true?
  • Is the 2007 -> 2010 -> 2013 process true?
  • Is the 2007 -> 2010 -> 2013 process true?
  • Is the 2007 -> 2010 -> 2013 process true?
  • Many organizations, 75%, already use this multi-farm model.
  • Revisiting the versions used, if you notice the total of versions, it’s way over 100%, that’s because people are running multiple farms, with differing versions.
  • Walk through each step
  • SearchUser ProfileMetadataBusiness Data
  • Optionally, use your SP2013 services farm as a hub, purely to serve up enterprise wide services to multiple farms
  • Can O365 consume an onprem services farm? Visa-versa? Or would O365 be completely stand alone?
  • Don't upgrade to SharePoint 2013

    1. 1. Who am I? SharePoint Architect with Slalom Consulting Mail: david.lozzi@slalom.com Twit: @DavidLozzi Blog: www.davidlozzi.com
    2. 2. SHAREPOINT 2013 WHAT’S ALL THE EXCITEMENT FOR?
    3. 3. 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/
    4. 4. 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
    5. 5. Doesn’t everyone just upgrade anyway? Current installed SharePoint versions. Source: Metalogix Survey from SPC 2012
    6. 6. WHEN IS THE RIGHT TIME TO UPGRADE?
    7. 7. 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?)
    8. 8. Self-Justification The Joneses Happier users Stay current Why that’s bad Not the right fit Doesn’t benefit the overall business goals
    9. 9. 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
    10. 10. 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
    11. 11. 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
    12. 12. 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
    13. 13. What’s the cost? Upgrading from 2007, requires upgrading to 2010 first, then upgrade to 2013 3rd party solutions available Upgrading from 2003, good luck SP2007 SP2010
    14. 14. 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
    15. 15. What’s the cost? Training Developers: new APIs, Apps model, etc. Users and power users IT administration and maintenance User Adoption
    16. 16. Will you upgrade?
    17. 17. YES I WANT TO UPGRADE!
    18. 18. Upgrade from 2010 Create a new SP2013 Farm Detach/attach databases Apply customizations Upgrade site collections SP2010
    19. 19. GOING
    20. 20. 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
    21. 21. Hybrid Number of farms at an organization Source Metalogix Survey from SPC 2012
    22. 22. Hybrid Source: Metalogix Survey from SPC 2012
    23. 23. Keep your SharePoint 2010 farm SP2010
    24. 24. Create a SharePoint 2013 farm
    25. 25. Upgrade Service Applications Business Data Connectivity Managed Metadata Performance Point SP2010 Secure Store Search User Profile
    26. 26. Configure and publish 2013 services
    27. 27. Consume services on 2010 SP2010
    28. 28. Migrate site collections to SP2013 SP2010
    29. 29. Additional SP2013 farms SP2010
    30. 30. Go to SP2010
    31. 31. Should I Upgrade? Or Shouldn’t I?
    32. 32. 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

    ×