O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

SharePoint 2010 Upgrade Best Practices Teched Brazil by Joel Oleson

5.661 visualizações

Publicada em

SharePoint 2010 Upgrade Best Practices Teched Brazil by Joel Oleson. Includes strategy for upgrade including details on the common upgrade methods including additional best practices, a decision tree, and solutions.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

SharePoint 2010 Upgrade Best Practices Teched Brazil by Joel Oleson

  1. 1. SETEMBRO, 2010 | SÃO PAULO<br />
  2. 2. CÓDIGO DA SESSÃO:OSP302<br />SharePoint 2010 Upgrade Best Practices<br />Joel Oleson<br />Sr. SharePoint Architect<br />Quest Software<br />
  3. 3. Who is SharePoint Joel?<br />10 Years of SharePoint<br />SharePoint Product Architect, Evangelist & Strategy @ Quest<br />Twitter: @joeloleson<br />Email: joel.oleson@quest.com<br />
  4. 4. SharePointJoel.com<br />
  5. 5. Upgrade<br />Before<br />During & After<br />
  6. 6. Pre Upgrade<br />
  7. 7. SharePoint 2010 Requirements<br />SharePoint 2007 SP2 Update (Recent CU or at least October highly recommended)<br />64 bit operating system for application servers<br />Windows Server 2008 or 2008 R2 + SP & Hotfixes included in PreReq Installer<br />64 bit SQL Server<br />2008 R2+, 2008 SP1 CU5 or later, 2005 SP3 CU5 or later***<br />Virtualization is supported and very common<br />*** Upgrade or Installation will fail w/o proper CU<br />
  8. 8. Running PreUpgradeCheck (in SP2007 Sp2)<br />
  9. 9. PreUpgradeCheck Failed Report (snippets)<br />Selections from PreUpgradeCheck<br />
  10. 10. Test-SPContentDatabase<br />
  11. 11. Upgrade<br />
  12. 12. Insight on Upgrade<br />Binary Upgrade<br />In Place - New Timeout, Resume on failures<br />Database Attach - New Parallel, Progress Indicator<br />Visual Upgrade<br />Separate process<br />Delegation by default<br />
  13. 13. In-Place Upgrade<br />All-at-once upgrade<br />Must upgrade the whole farm at one time<br />No SP 2007 and SP2010 in same farm<br />Schedule downtime<br />Simplest approach, but *most risky*!<br />No going back<br />Resume Upgrade if problems occur<br />Recommendations<br />Run Test-SPContentDatabase from SP 2010 farm against databases<br />Do a full farm backup before you start!<br />
  14. 14. Pre Requisite Installer<br />
  15. 15. In Place Upgrade - Install<br />
  16. 16. In Place - Binary Approach to Upgrade<br />Caution: Not recommended for most deployments…<br />
  17. 17. Why I don’t recommend In-Place Alone<br />
  18. 18. Database Attach Upgrade<br />Safer, Requires more planning (A good thing)<br />Upgrade is done on a separate 2010 farm<br />Done database-by-database <br />Can be used with 2nd step visual upgrade<br />Use Test-SPContentDatabase (PowerShellcmdlet) to test database first<br />To attach<br />Mount-SPContentDatabase (PowerShell)<br />STSADM –o Addcontentdb operation<br />Parallel database upgrades are possible<br />
  19. 19. DEMO<br />Test-SpContentDatabase<br />Mount-SpContentDatabase<br />Upgrade Status<br />
  20. 20. Attaching Database to SP2010 Farm<br />
  21. 21. Central Admin Upgrade Status<br />
  22. 22. No Brainer - Read-Only Database Strategy<br />
  23. 23. DB Attach- Binary Approach to Upgrade <br />Recommended for most deployments…<br />
  24. 24. Visual Upgrade<br />Stay in 2007 (default) or move to 2010 UI<br />2010 ships 2007 Master pages and CSS<br />UI Preview capability<br />Farm admin or site admin controlled<br />Web level setting<br />Some items not 2007 UI compatible<br />My site host<br />PWA site collection<br />Report Server web parts<br />
  25. 25. Demo<br />Read-Only<br />Visual Upgrade<br />
  26. 26. Post Binary Upgraded Site: Preview Visuals<br />
  27. 27. Visual Upgrade Options<br />
  28. 28.
  29. 29. What about the Fabulous 40 Application Templates?<br />What do you want to do?<br />I want to continue using them<br />Install Upgraded Templates - Fab 40 on Destination farm<br />Convert Templates - .STP to .WSP<br />I want to remove them<br />Remove the .stp (Remove the template)<br />Export lists or use third party tools to move into OOB Site Defs<br />http://bit.ly/dhQUjd<br />
  30. 30. Upgrade Strategies<br />
  31. 31. PowerShell Upgrade Cmdlets<br />Test-SPContentDatabase<br />Discover and Document issues 2007/2010<br />Mount-SPContentDatabase<br />Initiate Content database B2B/V2V upgrade<br />Upgrade-SPContentDatabase<br />Resume Content database B2B/V2V upgrade<br />Upgrade-SPEnterpriseSearchServiceApplication<br />Search Service Application Instance<br />Upgrade-SPSingleSignOnDatabase<br />O12 SSO data to Secure Store database<br />
  32. 32. Hybrid Upgrade Considerations<br />Best of In Place<br />Configuration database<br />Site Definitions may be upgraded<br />Easier SSP -> Service App Upgrade<br />Best of Database Attach<br />Fast with multi database parallel upgrade<br />
  33. 33. Consider a Hybrid Upgrade<br />
  34. 34. Decisions???<br />Customized?<br />Uptime?<br />New HardwareExtra?<br />Hardware Ready?<br />Virtual/Rollback?<br />MSDE/SQL Express?<br />
  35. 35. SSP to Service App<br />Each SSP upgrades into:<br />A Search service app<br />A User Profiles service app<br />An Excel service app<br />An App Registry back-compat service app<br />New Services can be activated/added<br />
  36. 36. Visual Upgrade Strategies<br />Upgrade the UI at the same time<br />psconfig.exe –cmd upgrade –preserveolduserexperiencefalse<br />Updateuserexperience parameter of the Mount-SPContentDatabase or STSADM<br />Stager Upgrade (Hide UI)<br />Post Upgrade: Site Settings | Site Collection Administration| Supported User Experiences<br />Delegate UI Upgrade (Default)<br />psconfig.exe –cmd upgrade –preserveolduserexperiencetrue<br />
  37. 37. In Place Upgrade - Visual Upgrade Decisions…<br />
  38. 38. Troubleshooting/Common Issues<br />Missing server-side files or customizations, such as features or Web Parts<br />Configuration issues in the server farm, Web application, or services, such as managed paths or services that are not started<br />Additional issues in sites discovered on a site-by-site basis, starting with high-impact, high-profile sites<br />Disk Space or CPU/Memory Constraints<br />Don’t forget Forms to Claims<br />Profile Import & FIM (CU has fixes, security requirement)<br />
  39. 39. Released to the Web<br />SharePoint 2010: Best Practices for Upgrading and Migrating<br />Get Prescriptive guidance on Upgrade Methods<br />Drill deep into assessment tools<br />Compare Migration tools<br />Save yourself time<br />
  40. 40. Why Consider third party tools?<br />Getting out of customizations…<br />Quest Migration Manager<br />2003 to 2010 with post Migration Sync<br />2007 to 2010 in beta<br />Notes to SharePoint Migrations<br />www.quest.com<br />
  41. 41. Obrigado!<br />
  42. 42. Por favor preencha a avaliação<br />
  43. 43. Learn More about SharePoint 2010<br />Information forIT Prosat TechNet<br />http://MSSharePointITPro.com<br />Information forDevelopersat MSDN<br />http://MSSharePointDeveloper.com<br />Information forEveryone<br />http://SharePoint.Microsoft.com<br />
  44. 44. © 2008 Microsoft Corporation.Todos os direitos reservados.Microsoft, Windows, Windows Vista e outros nomes de produtos são ou podem ser marcas registradas e/ou marcas comerciais nos EUA e/ou outros países.<br />Este documento é meramente informativo e representa a visão atual da Microsoft Corporation a partir da data desta apresentação.Como a Microsoft deve atender a condições de mercado em constante alteração, este documento não deve ser interpretado como um compromisso por parte da Microsoft, e a Microsoft não pode garantir a precisão de qualquer informação fornecida após a data desta apresentação.A MICROSOFT NÃO DÁ QUALQUER GARANTIA, SEJA ELA EXPRESSA, IMPLÍCITA OU ESTATUTÁRIA, REFERENTE ÀS INFORMAÇÕES DESTA APRESENTAÇÃO.<br />