1 / 12

MOSS Migrations brown bag discussion March 5, 2012

MOSS Migrations brown bag discussion March 5, 2012. Feisal Abedeen MCITP , MCPD SharePoint Architect/Developer PRESENTATION. Migration Key Points. Must be MOSS 2007 SP2 Always Test in DEV Pre-Upgrade Check on MOSS 2007 Test Individual Components Isolate Failure Points

ross
Download Presentation

MOSS Migrations brown bag discussion March 5, 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MOSS Migrationsbrown bag discussionMarch 5, 2012 Feisal AbedeenMCITP, MCPD SharePoint Architect/Developer PRESENTATION

  2. Migration Key Points • Must be MOSS 2007 SP2 • Always Test in DEV • Pre-Upgrade Check on MOSS 2007 • Test Individual Components • Isolate Failure Points • Script when Possible • Disaster Recovery Plan • Update Resume First -

  3. Migration Types - 1 • In-Place Upgrade • Hardware Must be Compatible • Farm Offline • Create Read-Only Farm • Farm will be offline – downtime • One Server at a Time • Works for Small Farms • Maintains Customizations* • Maintains Security • Missed Chance to Improve

  4. Migration Types - 2 • Database Attach Upgrade • Detach  Update • Simultaneous DB Upgrades • Complete Control over Process • Allows For Improvements • Requires Parallel Farms • Requires URL Management • Works for Medium - Large Farms • Minimal Downtimes – MOSS Read-Only • Customizations Must be Addressed • Requires Database Management

  5. Migration Types - 3 • Hybrid Upgrade • Detach* In-Place Update • Hardware Must be Compatible • Simultaneous DB Upgrades* • Minimal Downtime* - MOSS Read-Only • Works for Medium – Large Farms • Maintains Customizations* • Maintains Security • Reduced Chance for Improvements*

  6. Migration Types - 4 • Extended Upgrade • Detach  Redirect*  Update • Used in Special Circumstances: • Content DBs Too Large • Too Many Customizations • Limited Hardware Available • Phased Migration Required • Not All Links Work • Allows For Improvements • Problems Fixed in Stages • Phased Over Days or Weeks • Eliminates Downtime – Both Online • Requires Communication & Planning

  7. Migration Phases 1 - 3 • Phase 1 - Design • Plan New Architecture • Plan Improvements • Build Unit Test Cases • Build Migration Team • Phase 2 – Optimization • Fix Current Issues • Review Logs • Upgrade Customizations • Remove Inactive Sites • Phase 3 – Testing • Create QA (Staging) Environment • Plan Beta Phase • Expose Selected End-Users to UI

  8. Migration Phases 4 - 5 • Phase 4 – Implementation • Create Implementation Team • Written Implementation Plan • Manage Downtime • Update Governance • Phase 5 – Remediation • Review Logs • Fix End-User Issues • Clean Up SA’s • Train Help Desk Staff

  9. Migration Phases 6 - 7 • Phase 6 - Monitoring • Test Server Performance • Monitor Processes • Monitor Web Analytics • Phase 7 – Training • End-User Training • Create Central Site • Online Help – Create How-To’s

  10. Common Gotchas - 1 • Unhandled Customizations • Site Definitions • Un-ghosted Objects • Redeploy Solutions • Poorly Written UI • JavaScript Errors • HTML Looks Different • Throttling Issues • Large Lists • Failed Sites • Fix Manually

  11. Common Gotchas - 2 • SA’sNot Optimized • Few DBs Upgrade, Configure Others • Test Prior to User Access • Inadequate Communication • Users Cannot “Find” Objects • Users Poorly Trained • Inadequate Planning • Downtime More Than Expected • Failure on First Attempt • Group Feedback…..

  12. In Summary • MOSS Upgrade Only Successful with Proper Planning and Implementation • New SharePoint 2010 Farm Should be Designed to Remove Past Issues • Know Limitations • Have Realistic Expectations • Take Advantage of New Functionality to Improve ROI • Have Fun With Your Upgrade -

More Related