1 / 25

Upgrade from SharePoint 2007 to 2010 – the theory

Upgrade from SharePoint 2007 to 2010 – the theory. Michael O’Donovan michodon@microsoft.com. Resources. Microsoft SharePoint Upgrade Resource Center http:// msdn.microsoft.com/sharepoint/ee514557.aspx. Agenda. Upgrade types Before you upgrade Potential issues Validate upgrade.

mirari
Télécharger la présentation

Upgrade from SharePoint 2007 to 2010 – the theory

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. Upgrade from SharePoint 2007 to 2010 – the theory Michael O’Donovan michodon@microsoft.com

  2. Resources • Microsoft SharePoint Upgrade Resource Center • http://msdn.microsoft.com/sharepoint/ee514557.aspx

  3. Agenda • Upgrade types • Before you upgrade • Potential issues • Validate upgrade

  4. Upgrade Types

  5. Upgrade Types • Un-supported • Upgrade from earlier than WSS v3 SP2/MOSS 2007 SP2 • Direct upgrade from WSS v2/SPS 2003 or earlier • Supported • In Place • Database Attach • Hybrid • Visual Upgrade • Option to keep 2007 UI for all supported scenarios

  6. Database Attach Steps • Set up and configure the new farm. Transfer customizations to the new farm and test the environment. • Detach the content database from the old farm and set the Content DB on old farm read-only. • Attach the content databases to the new farm and upgrade the content. • Start serving requests on the new farm at the “new” URL. • Try and keep same URL • Otherwise Outlook, favourites, etc etc break

  7. Attach DB • Attach DB • STSADM = addcontentdb • PowerShell = Mount-SPContentDatabase • Works on content db and ssp-userprofile db

  8. Hybrid Upgrade Steps • Build a new 2007 farm, with 2007 content db’s • Detach the content dbs. in this new farm • Upgrade in place (this will do all config too) • Do database attach (2007 database into 2010)

  9. Hybrid Upgrade Disadvantages • Farm settings and search index will be migrated in 2007 topology style • How to test Config DB, Central Admin DB, Search DB,…?

  10. Before you upgrade

  11. SharePoint Tools • Run Pre-upgrade checker tool on 2007 environment • Tools comes with from SharePoint 2007 / WSS 3.0 SP2 • Rules for tool found in CONFIG\PreUpgradeCheck\WssPreUpgradeCheck.xml • Errors explained - http://support.microsoft.com/kb/960577 • Run Test-SPContentDatabase using 2007 database in 2010 environment • Answers the question of “will the DB “work” in the 2010 farm?”

  12. PreUpgradeCheck • Stsadm –o preupgradecheck • Return 3 Files • Report as .htm file: • Operation runs successful and we get a .htm file • Logfile of PreUpgradeCheck -> Quality of the report • SSP2 didn‘t had a index assigned -> How the upgade process can react on this? SSP2 is not accessible? • XML

  13. Test-SPContentDatabase

  14. Know what you have • How many Content DBs? • Size of each DB? • How many site collection per Content DB? • Size of each site collection? • SPWebs & templates used • Webs that use custom site definitions / templates • Web that don’t have a template assigned • Orphaned webs • Customisations • Features, list definitions, web parts, event handlers • Admin level customisations, timer jobs, central admin customisations • 3rd party add-ins • Integration with other systems

  15. SPWeb Overview in SQL

  16. WebTemplates from MS

  17. Get SPWeb Overview in STSADM • Stsadm –o enumallwebs –dn <dbname> • Note: • enumAllWebs has some RuleChecks on SPWeb level against broken webs

  18. Pre-Validation Techniques • MS tools discussed previously • WinDiff over 12-Hive Folder • Compared with a OOB installation of MOSS • Find all custom files / customization • wssAnalyzeFeatures – from Stefan Gossner • Show if feature files are on the file system • SharePoint Farm Solution Extractor • Check all solutions in SP2010 • SQL Queries against Content DB • Export and Import Content • using STSADM –o export, and then re-import to see if errors are shown

  19. Other Potential Issues

  20. Collaboration Issues • Browser support change • ContentType template change: • .xls -> .xlsx • .doc ->.docx • .ppt -> .pptx • -> Office 2003 functions limited • Workaround: Office Compability Pack or change document templates

  21. List and Site Templates (stp files) • Find & check all ListTemplates & WebTemplates • .Stp inside site and list galleries dont migrate, so you need to manually solve this, also 2010 requires WSPs not stps

  22. List Items reference Features no longer around • This is an issue, even for items in recycle bin • On this note; a blog article from Jason Dicker • http://jasondicker.wordpress.com/2010/10/13/my-sharepoint-2010-upgrade-experiences/

  23. Custom Branding • Keep as 2007 UX or Visual Upgrade to 2010 UX • Themes • Will need to re-create for 2010 UX • Master Pages • Will need to re-create for 2010 UX

  24. How do we know it worked? How do you validate?

  25. Ideas? • Upgrade.log • Users check sites

More Related