SharePoint 2010 Upgrade Strategies and Best Practices - MS Days Bulgaria - Joel Oleson

  • 2,437 views
Uploaded on

In place upgrade has been a rough experience. Many think it’s the worst thing you could ever do. There are better ways of getting SharePoint 2007 to SharePoint 2010, but the hybrid methods can be the …

In place upgrade has been a rough experience. Many think it’s the worst thing you could ever do. There are better ways of getting SharePoint 2007 to SharePoint 2010, but the hybrid methods can be the best approach depending on what is happening in your environment. It’s important to understand the customizations, the service application, and various add-ons. In this session we’ll drill into these issues and talk about what has changed and how best to take advantage of it. For those already on SharePoint 2010 we’ll dig into the service packs, and cumulative updates. We’ll discuss a real world SharePoint 2010 upgrade and talk about the lessons learned and best practices. Key Take Aways: - Upgrade Best Practices - Upgrade Strategies - Migration Considerations - How to roll back - How to have minimal impact - Patching, and Cumulative update strategies

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,437
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
47
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SharePoint 2010 Upgrade & PatchingStrategiesJoel OlesonSolutions Managerhttp://www.sharepointjoel.com@joeloleson
  • 2. Who is SharePoint Joel? 11+ Year SharePoint Veteran Twitter: @joeloleson Find me on Facebook, LinkedIn Blog: SharePointJoel.com
  • 3. Upgrade Cycle: Overview Learn • Requirements/prerequisites • Upgrade methods • Downtime mitigation • Common issues Validate Prepare • Upgrade event failures • Document environment • UI/UX issues • Manage customizations • Data issues • Plan upgrade strategy • Make items upgradable Implement Test • Build/upgrade farms • Build test farms • Deploy customizations • Use real data • Minimize downtime • Evaluate techniques • Monitor progress • Find issues early
  • 4. Learning from PreUpgradeCheck
  • 5. PreUpgradeCheck Failed Report
  • 6. SharePoint PreUpgradeCheck Report Important Information & Configuration Issues and Dependencies• Content Sources & • Site Definition Start addresses (referenced & missing)• Farm & Search • Installed Language Topology Pack• Servers • Features (referenced &• Upgrade Supported missing) based on Farm Type • Custom List Views &• AAMs, Large Lists & Custom Field Types, Libraries Web.Config entries
  • 7. Test-SPContentDatabase
  • 8. Getting All Your DependenciesEnumallWebs has some added enhancements. These are very applicable for gathering what you need out of your farm.stsadm.exe -o enumallwebs [ -databasename <database name>] [ -databaseserver <database server name>] [ -includefeatures ] [ -includesetupfiles ] [ -includewebparts ] [ -includeeventreceivers ] [ -includecustomlistview ]stsadm -o enumallwebs -includefeatures -includesetupfiles -includewebparts - includeeventreceivers -includecustomlistview > enumallwebs.xml
  • 9. Output enumallwebs -includefeatures
  • 10. Insight on UpgradeBinary Upgrade –In Place - New Timeout, Resume on failures –Not recommended for most deployments –Database Attach - New Parallel, Progress Indicator VisualVisual Upgrade Upgrade –Separate process Binary Upgrade –Delegation by default
  • 11. In-Place UpgradeAll-at-once upgrade – Must upgrade the whole farm at one time – No SP 2007 and SP2010 in same farm – Schedule downtimeSimplest approach, but *most risky*! – No going backResume Upgrade if problems occurRecommendations – Run Test-SPContentDatabase from SP 2010 farm against databases – Do a full farm backup before you start!
  • 12. Database Attach UpgradeSafer, Requires more planning (A good thing)Upgrade is done on a separate 2010 farm – Done database-by-database – Can be used with 2nd step visual upgradeUse Test-SPContentDatabase (PowerShell cmdlet) to test database firstTo attach – Mount-SPContentDatabase (PowerShell) – STSADM –o Addcontentdb operationParallel database upgrades are possible
  • 13. Read-Only Databases
  • 14. Visual Upgrade Stay in 2007 (default) or force move to 2010 UI –2010 ships 2007 Master pages and CSS –UI Preview capability Farm admin or site admin controlled –Web level setting Some items not 2007 UI compatible –My site host –PWA site collection –Report Server web parts
  • 15. Attaching Database to SP2010 Farm
  • 16. Central Admin Upgrade Status
  • 17. Binary Upgraded Site:Site Preview
  • 18. Visual Upgrade Options
  • 19. Real World Visual Upgrade Issues…• Parent/Child Freakiness• How long should you keep them around?• What happens if they stay in preview mode or stay in 2007 UI?• Usage Stops working• Can I roll back?• Schema issues
  • 20. Common Upgrade Failure Issues & Recovery 1. Determine cause of failure – Status Page & Upgrade Logs: – Error log – Full upgrade log – Customizations Management Commands: – Test-SPContentDatabase – stsadm -o EnumAllWebs 2. Fix issue(s) – Install missing or updated customizations – Activate missing services; farm, web app settings 3. Resume upgrade – Farm upgrade command – Content database specific upgrade command – Service specific upgrade commands
  • 21. Upgrading SharePoint Service AppsEach SSP upgrades into: –A Search service app –A User Profiles service app –An Excel service app –An App Registry back-compat service appNew Services can be activated/added
  • 22. Why Should Users care about upgrade? • Cross browser and client OS compatibility Duxs iPad and Mac writeup. Microsofts Browser maxtrix for support. Firefox, Safari, Chrome • Client Side Application Development • Scalable lists How about 50 million items in a list! Theres an updated SharePoint 2010 software capacity limits • Office Integration, Office Web Apps, and Office Mobile apps – multi authoring capabilities in Word 2010, cell locking and multi user editing in Excel and One Note. walk through on co-authoring in Word. • More control: SharePoint Designer • Improved List correlation and list relationships - You can get more data from SharePoint 2010 List Relationships. • Social tagging, and other social features – My Network, Social Distance Relevancy, tagging, Enterprise wikis • Content Management features –Lists can now include content types for audio and video including silverlight webpart
  • 23. What’s new in SP1? • Site Recycle bin • Security enhancements • Reliability enhancements • Storage Reporting for end users – StorMan the interface users had in 2007 to view storage is back and better! • Chrome Support for SharePoint & Office Web Apps – Nice! More details on SharePoint 2010 SP1 browser support on TechNet • RBS (Remote Blob Storage) - Remote storage support for shadow copies ensuring better reliability and recoverability. • New Powershell cmdlet (Move-spsite) for moving Site Collections between databases without moving content back in the db (when using RBS) • Project Professional now synchronizes scheduled tasks with SharePoint task lists • Improved backup / restore functionality for SharePoint Server • Includes all previous monthly cumulative updates • Database sizing restrictions loosened • 10 Reasons SharePoint 2010 SP1 Will Rock Your World!
  • 24. Fab 40Feature or Template Error Message Found a missing feature Id = 75a0fea7-KB Provisioning Feature 84d9-447d-b9ec-bc49570874db Assembly KnowledgeBaseEventHandler,Knowledge Base Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c WebTemplate ID 75801 (lcid: 1033),Bug Database provisioned in ContentDatabase WSS_ldsteams47_Content, is missing.
  • 25. Fab 40 lessons learned Some features don’t deactivate despite the –force command. If you experience this problem (they will still show up during the upgrade and the DB will fail), Ive found this tool to be helpful: http://featureadmin.codeplex.com/ Installing the 2007 Appcore and Applicable 2007 Fab 40 templates on the 2010 box removes the errors. Khalil’s 2010 fab 40 will not remove the errors, they are to support the functionality 3rd party migration software to clean these things up. Doing that also gives you the flexibility to split up site collections, combine site collections, populate metadata We decided we didn’t want to support Fab 40 going forward, but we needed the code, so we decided to hide the Features
  • 26. Don’t forget to submityour feedback and win agreat Nokia smartphoneand Kindle e-reader!