1 / 76

Overview of Upgrade to WSS 3.0 and SharePoint Server 2007

annelise
Download Presentation

Overview of Upgrade to WSS 3.0 and SharePoint Server 2007

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. Overview of Upgrade to WSS 3.0 and SharePoint Server 2007 Joel Oleson Sr. Technical Product Manager Microsoft Corporation

    2. Agenda Upgrade Preparation Prescan and * Disk considerations Upgrade Methods and Options In-Place, Gradual and Content DB Migration Post Upgrade Considerations Customizations, Content Partner Upgrade Tools Summary Q & A

    3. Upgrade/Migration Path

    4. Preparing for Upgrade Scope and Plan your upgrade Review Hardware End of Life, plan for upgrade capacity; disk space, memory, processor Test your upgrade & estimate your upgrade duration Review customizations Keep or Decommission customizations Cleanup Remove Orphans, increase close quotas, remove locks, Service Offering Redesign, Training, Communication plan

    5. What will Prescan find? Sites based on customized site templates - site template upgrade kit Sites based on custom site definitions Unghosted pages Orphaned objects Custom Web Parts Sites than need language packs

    6. Prescan Example of good PreScan results: 07/19/2006 17:17:01 Scan finished without failure. 07/19/2006 17:17:01 Number of sites skipped (already scanned): 0 07/19/2006 17:17:01 Number of sites scanned: 1 07/19/2006 17:17:01 Number of broken sites: 0 07/19/2006 17:17:01 Number of webs scanned: 13 07/19/2006 17:17:01 Number of broken webs: 0 07/19/2006 17:17:01 Number of webs using custom template: 0 07/19/2006 17:17:01 Number of pages scanned: 0 07/19/2006 17:17:01 Number of unghosted pages: 63

    7. Upgrade Options In-Place Upgrade For small non production environments, offline while it runs (Not recommended for most environments) Gradual Upgrade: Side by Side Upgrade Granular control, one to many site collections at a time Side-by-side; rollback to 2003 supported More complex & resource intensive Content DB Migration: Upgrade Into Separate Farm Attach 2003 content db to 2007 farm & upgrade runs 2003 farm stays available and untouched Content only, requires new farm, has many manual steps

    8. In Place Upgrade Pros: Simple and fast upgrade Best for smaller or non production environments Cons: Environment offline during upgrade Riskier in large environments Upgrade Fails if it encounters errors -fix then rerun. Not Recommended for Most Deployments

    9. Database Mapping

    10. In-Place Upgrade Steps On existing hardware, install prerequisites Run setup and choose “In-Place Upgrade” Install language packs if needed Deploy Upgrade Definition, Site Definition and Feature Files Run Configuration Wizard and Upgrade one web server Review log files and resolve any issues Review upgraded content Reset pages (or site) to Site Definitions

    11. Gradual Upgrade Pros: Old and new SharePoint versions run in parallel Allows upgrade with minimal downtime Can roll-back upgrades per site collection Cons: Redirector will cause user confusion Additional impact from two SharePoint versions

    12. Gradual Upgrade Process

    13. On existing hardware, install prerequisites Prepare URL Redirect Domain Install Binaries and Choose Gradual Upgrade Option Run Configuration Wizard to setup a new farm Install Language Packs Deploy Upgrade Definition, Site Definition and Feature Files Deploy Custom Web Part Packages and any other custom code (only if in Bin directory)

    14. Gradual Upgrade Upgrade Steps Review log files & resolve any issues Repeat setup & upgrade on each server in the farm Start content upgrade thru UI or stsadm Review your upgraded content If customized sites, reset pages to 2007 site definition versions Fix issues and reapply customizations using SharePoint Designer If upgrade result is undesirable, revert to 2003 site

    15. Gradual Upgrade Content Upgrade

    16. Gradual Upgrade Revert to 2003 When upgrade result is undesirable, “revert” deletes 2007 & resets redirect to 2003 Confirm 2003 site still exists before reverting to it Revert to 2003 via UI or command line UI: Select Sites for Upgrade > Revert Site Command line: stsadm –o upgrade –revert Once complete, re-upgrade original Use SharePoint designer to merge changes from “fixed” & re-upgraded versions

    17. Gradual Upgrade Scenarios Works best for Staging Environment Environments with Heavy Customizations Recommended for Large Databases and Site Collections Upgrade a subset of Site Collections only Environments requiring minimal migration window

    18. Content DB Attach Upgrade Pros: Fast upgrade method Cons: More complex than in-place upgrade Note: This does still require Prescan. Don’t forget assemblies

    19. Content DB Migration

    20. Create new 2007 farm on clean hardware Install prerequisites Configure farm-level settings Create a new web application for each 2007 virtual server Manually re-apply configuration settings Ensure all inclusions re-created in 2007 (required) Deploy Upgrade Definition, Site Definition and Feature Files Deploy custom web parts to GAC or BIN Content DB Migration Steps

    21. Back up 2003 content database using SQL Restore backup to copy in 2007 farm Add content db to web application via command line Ensure root site included in first database stsadm –o addcontentdb Upgrade triggers automatically, runs until it completes For large databases, command line preferable Review log files for any issues Repeat for all additional content and search/user profile databases stsadm –o restoressp Content DB Migration Steps continued

    22. Set 2003 content DBs to read-only Avoids manual merging of updates post-upgrade Note: Users will see warnings when DB is read-only Re-mapping URLs Use ISA Server to remap URLs to 2007 farm Use IIS Redirect Use DNS Re-applying inclusions, custom web parts & custom site definitions are critical Entirely manual process for moving them Content DB Migration Additional Considerations

    23. Moving to new hardware or a new architecture Customers who need to maximize upgrade throughput. Required for Scalable Hosting Mode or Active Directory Account Creation Mode. Recommended for Large Farms

    24. Database Attach on Steroids

    25. 2003 Customizations Templates Custom Site Definitions Custom Site Templates Page Templates Custom Code Web Parts Event Handlers Client-side Scripts ASP.NET apps in _layout Branding and Layout Customizations Style sheets and Themes FrontPage Customizations Non-SharePoint Elements NT Services Web services Custom DLLs

    26. Customization Considerations

    27. Resetting to Site Definition

    28. Page ReGhosting (Reverting) Unghosting of pages occurs easily Upgrade may not affect unghosted status Page re-ghosting in Site Settings or Designer Re-ghosting pages during upgrade: Your choice Can be performed by Server Administrator or Site Collection Admin

    29. Upgrade Effects on Ghosting

    30. Upgrading Site Definitions Three things required to upgrade site definitions: Prescan configuration file Upgrade configuration file Upgraded site definition Upgrade file changes site structure: <List FromTemplateId="104” ToFeatureId="00BFEA71-D1CE-42de-9C63-A44004CE0104" /> <File FromPath="{LocaleId}\STS\default.aspx” ToPath= "SiteTemplates\STS\default.aspx" />

    31. Upgrade Considerations Best Practices Reduce Dependency on Site Definitions (Use Soln Deployments) Consolidate Web Applications and farms Information Architecture Restructure Content/structure change – Workflow & Forced Checkout URL/path change - Global Nav & Breadcrumbs WSS upgrade to MOSS

    32. Finalize Upgrade Business/Customer approval Removes gradual upgrade redirector Can remove SharePoint 2003 afterwards Can still upgrade using database attach method

    33. Lessons Learned Communicate upgrade schedule Determine plan or policies: Ghosting during upgrade Upgrade priorities – exceptions process Upgrade roll-backs – exceptions process Determine whether to offer site previews Choose gradual upgrade redirection URL wisely Review and Retain upgrade logs after each upgrade

    34. Troubleshooting Tips Prescan logs %temp% Prescan.log Prescan Report and Summary Log files Upgrade and Server logs Logs are in: \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs Event Viewer Psconfig command-line utility

    35. Partner: CorasWorks Migrator Reghost multiple sites at once Migrate Customizations and web parts to sites post upgrade Helps you add layouts, master pages, web parts, en masse

    36. Partner: Echo Helps you quickly roll out customizations and settings and permissions across your farm with no site collection boundaries

    37. Partner: AvePoint DocAve Used to connect to 2003 and move content to 2007 without dependencies on customizations. Quickly and Easily move your lists and libraries into a clean slate (out of box site definitions).

    38. Summary Use In-Place for Development Environments Use Gradual for Staging your Customizations Use Content DB Migration to move to a new architecture and hardware Prepare, plan and test your customizations!! Learn how to troubleshoot prescan and upgrade logs

    39. References Upgrade Documentation http://technet2.microsoft.com/Office/en-us/library/396c85d9-4b86-484e-9cc5-f6c4d725c5781033.mspx?mfr=true Migration and Upgrade Information for SharePoint Developers http://msdn2.microsoft.com/en-us/office/aa905505.aspx Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide http://www.microsoft.com/technet/solutionaccelerators/collaboration/default.mspx Upgrade on WSS SDK http://msdn2.microsoft.com/en-us/library/ms460185.aspx IT Pro Content http://www.microsoft.com/technet/prodtechnol/office/sharepoint/default.mspx SharePoint Technical Library on TechNet http://technet2.microsoft.com/Office/en-us/library/3e3b8737-c6a3-4e2c-a35f-f0095d952b781033.mspx Conferences (SharePoint Conference 2006, TechEd 2006) Models, Scenarios and Flowchart http://officebeta.iponet.net/en-us/help/HA101639821033.aspx?pid=CL100605171033 HotFixes Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services http://support.microsoft.com/kb/918744 Description of a new command-line operation that is available for the Spsadm.exe command line tool that you can use to clean up orphaned items in the configuration database in SharePoint Portal Server 2003 http://support.microsoft.com/kb/918742/

    40. References Supportability 2003 Best Practices to ensure upgradeability http://msdn2.microsoft.com/en-us/library/ms916859.aspx KB Article on Site Defn supportability in 2003 http://support.microsoft.com/Default.aspx?id=898631 Supported and unsupported scenarios for working with custom site definitions and custom area definitions in Windows SharePoint Services and in SharePoint Portal Server 2003 http://support.microsoft.com/kb/898631/en-us Community Tools SharePoint Configuration Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyID=918f8c18-89dc-4b47-82ca-34b393ea70e1&DisplayLang=en SharePoint Utility http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724 SPReport http://workspaces.gotdotnet.com/spreports Managing SharePoint Products and Technologies Performance at Microsoft http://www.microsoft.com/technet/itshowcase/content/spsperfnote.mspx#ETKAE Microsoft SQL Server Report Pack for Microsoft Office SharePoint Portal Server 2003 http://www.microsoft.com/downloads/details.aspx?FamilyID=49159368-544b-4b09-8eed-4844b4e33d3d&DisplayLang=en Blogs Resources and Recommendations for Upgrading Site Definitions and Site Templates http://blogs.msdn.com/joelo/archive/2007/01/03/resources-and-recommendations-for-upgrading-site-definitions-and-site-templates.aspx Upgrade Content IT Pros may not have seen http://blogs.msdn.com/joelo/archive/2006/12/06/upgrade-content-it-pros-may-not-have-seen.aspx Other Upgrade Topics from Joel’s Blog http://blogs.msdn.com/joelo/archive/tags/Upgrade/default.aspx

    41. Custom Site Definitions 2007 custom site definition is required or sites in “Compatibility mode” Upgrade your custom site definitions and page templates Create and test new site definition and “features” Create upgrade definition to map 2003 to 2007 Deploy mapping file & 2007 site definition Can be done post-upgrade using command line

    43. Upgrade Definitions Upgrade files deployed to \12\config\upgrade WSSUpgrade.xml SPSUpgradePremium.xml Upgrade Definition File Schema Config   WebTemplate   Lists   List   Source   Files   File   AppliedSiteFeatures   Feature   AppliedWebFeatures   Feature

    44. Upgrading Site Definitions Not heavily customized site definition Example: Add custom list, modified Default.aspx Create new v3 site definition and re-apply customizations Recommended approach Heavily customized site definition Modify v2 site definitions to work in v3 ASPX Pages must contain Web Part Manager or use Master Pages <WebPartPages:SPWebPartManager id="m" runat="Server" /> Onet.xml contains $Resources Remove base types, standard lists, deprecated list templates Map document templates to v3 document templates Replace List Templates with Feature references Replace Form and View Pages with “\pages\form.aspx” and "pages\viewpage.aspx“ SPTool from SharePoint Toolkit, http://spplatform/toolkit

    45. Custom Site Templates Locate .stp file Determine which site definition it is based on Determine whether it is customize/unghosted Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide Steps In 2003, create a site using the site template (.stp) Install 2007 and upgrade site In 2007, revert to site definition and reapply changes Package the site into site template Test by creating new sites using 2007 site template

    46. Custom Web Parts Most will work post-upgrade Test in WSS 2003 SP2 with ASP.NET 2.0 Must re-build custom parts if you used ASP.Net 1.1 “obfuscation” tools Must re-deploy web parts if Moving to a new server farm (Content DB Migration) Web part in the \bin (Gradual Upgrade) Deploying web parts stsadm –o addwppack

    47. FrontPage Customizations Important consideration: keep customizations or move to 2007 Custom pages kept by default during upgrade Be aware: customized pages do not match rest of site “Reset to Site Definition” Returns page to layout in site definition Option exists to reset all pages during Gradual upgrade Available in site settings or within SharePoint Designer

    48. Preparing for Upgrade Investigate and Prepare your content Large site collection and database sizes Tools for analyzing your environment SharePoint Utility, SharePoint Configuration Analyzer, SPReport Backup, backup, backup… Run Pre-Scan tool is required Comes with the product in \bin , available as download Reports common issues that needs to be addressed Updates WSS lists so they can be upgraded Lists all custom site definitions used

    49. Running Prescan.exe prescan.exe /c preupgradescanconfig.xml /all PreScan Log and Summary created in \%temp%\

    52. Pre-Scan Common Issues Site/List not scanned error at the end of the log Solution: Post SP2 Hotfix UpdateListSchemaInAllWebs() Method not found Solution: Install SP2 Various WSS OM method failure from SPRequest object with File not found error Solution: Install custom site definitions Virtual server is not in a ready state Solution: Run it against v2 Virtual server

    53. Orphaned Objects WSS Content DB Orphans Post SP2 Hotfix, KB 918743 and KB 918744 stsadm -o databaserepair -url http://WSSSite -databasename DatabaseName stsadm -o databaserepair -url http://WSSSite -databasename DatabaseName –deletecorruption SPS Config DB orphans Post SP2 Hotfix, KB 918742 spsadm –o repairorphans http://PortalSite WSS Config DB orphans Remove and then reattach the content databases on the virtual server

    54. For ITPros: (RTM Exam) 70-631 - Windows SharePoint Services 3.0 - Configuring 70-630 - Office SharePoint Server 2007 - Configuring For Developers: (Beta Exam) 70-541 - Microsoft Windows SharePoint Services 3.0 - Application Development 70-542 - Microsoft Office SharePoint Server 2007 - Application Development All 4 exams are available TODAY in the Learning Testing Center on the First Floor of the WSCC DON'T DELAY – TAKE 'EM TODAY!!! Be one of the first to pass the NEW MCTS Exams!!!

    55. Appendix

    57. Post-Upgrade Delete un-needed 2003 sites Needed for Gradual Upgrade & DB Attach Finalize Upgrade Required for Gradual & In-Place Upgrade Removes temporary data maintained about 2003 environment Post-upgrade data migration Un-install 2003 environment

    58. Effect of Upgrades: Low Customization Site (Original)

    59. Effect of Upgrades: Low Customization Site (Upgraded)

    60. Effect of Upgrades: Low Customization Site (Re-Ghosted)

    61. Effect of Upgrades: High Customization Site (Original)

    62. Effect of Upgrades: High Customization Site (Upgraded)

    63. Effect of Upgrades: High Customization Site (Re-Ghosted)

    64. Effect of Upgrades: Themed Site (Original)

    65. Effect of Upgrades: Themed Site (Upgraded)

    66. Reasons for Upgrade Consolidation of Services and Infrastructure Less number of Databases and Servers Shared Services Operational Needs Full fidelity Data Protection and Recovery Site ownership management Built-in ability to remove site customizations Platform Upgrade 64 bit SQL Server 2005 ASP.NET 2.0/3.0

    67. Reasons for Upgrade New Business Scenarios/Requirements Content Management Business Intelligence Business Data Integration Improved Experience Security-trimmed UI Search Workflow Improved Extensibility

    68. Planning for Upgrade Review your environment and business scenarios Profile your usage scenarios Review customizations; requirements and design documentations Determine how to handle them Determine upgrade approach Understand upgrade process Prototype different options with subset of your data

    69. Choose if resetting files to template version Can change selection with each group of sites upgraded Select first group of sites to upgrade Must include the root site of the domain in first group Note storage (number of MB) to be upgraded During upgrade, redirect to 2003 URL is removed 2007 site is now live Automatic - no admin action needed Review log files after each upgrade group Tip: Upgrade duration is in logs. Number of MB / duration is good approximation for subsequent upgrade durations Repeat steps 1-3 for all sites Command line available to automate Gradual Upgrade Content Upgrade

    70. Shared Services configuration For each master portal Configure search in 2007/O12 Configure profile/audience sync in 2007/O12 Review Managed Properties of user profiles in 2007/O12 For each child portal Modify start addresses in 2003/O11 master portal to prevent double-crawling Gradual Upgrade Shared Services Considerations

    71. Gradual Upgrade Shared Services Considerations Search Services Two crawls running at the same time Keywords, site-level scopes only available for upgraded 2007 sites User Profiles/Audiences Changes in 2007 pushed down to 2003 – does not include new properties and audience rules Review Managed Properties list for people search scope Review upgraded audiences – consider deleting those built on DLs/SGs as those groups can be used directly

    72. Content Database Migration

    73. Content DB Migration Shared Services V2/O11 not affected Parent continues to provide services to v2 sites Child sites retain user experience User profile/audience data not synced between v2, v3 Two profiles, two MySites, etc may confuse Applications Most search data not upgraded Re-create search settings other than custom search properties

    74. Search Services Configure on the 2007 Parent farm Avoid double-crawl as configuring your content sources User Profiles/Audiences Data not synchronized between 2003 and 2007 Review Managed Properties list for people search scope Review upgraded audiences – consider deleting those built on DLs/SGs as those groups can be used directly My Sites – Two of them…

    75. Additional Considerations Search Upgrade In-Place and Gradual: some settings are not upgraded Index files, Scopes, Search alerts, Any filters, word breakers and thesaurus files DBAttach: none of the search settings are upgraded since search settings are on the registry Configure search settings on the new farm Site Directory (area, list, sites) 2003: Area with Directory List, Site collections 2007: Subsite with Directory List, Site collections, Subsites under /SiteDirectory

    76. Summary and Tradeoffs

More Related