1 / 59

SharePoint 2010 Upgrade

SharePoint 2010 Upgrade. Martin Y. Leveille Sharepoint Deployment Technical Lead RJB Technical Consulting, Inc . martin.leveille@rjbtech.com twitter : @ martinyleveille www.rjbtech.com. Upgrade Overview. Preparing For Upgrade What you can do to get ready. Learn. Prerequisites.

adelio
Télécharger la présentation

SharePoint 2010 Upgrade

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. SharePoint 2010 Upgrade Martin Y. Leveille Sharepoint Deployment Technical Lead RJB Technical Consulting, Inc. martin.leveille@rjbtech.com twitter: @martinyleveille www.rjbtech.com

  2. Upgrade Overview

  3. Preparing For UpgradeWhat you can do to get ready

  4. Learn

  5. Prerequisites Common issues • 64 bit only • Operating System • SQL server • Missing dependencies • UI changes • Lack of space • Forms Authentication Providers Upgrade methods Downtime mitigation • In-Place • Database Attach • Content • Profile • Project • Read-only content databases • Parallel upgrades: • Multiple temporary farms • Parallel database attach • AAM redirection

  6. New • Upgrade Preparation Tools • Windows PowerShell Upgrade Cmdlets • Feature Upgrade • Visual Upgrade • Downtime Mitigation Processes: • Parallel Upgrade Pipelines • Content DB Upgrade with AAM Redirection Changed • Upgrade Methods • Improved • Upgrade Status Reporting • Upgrade Logging • Read-only DB Support Removed • Gradual Upgrade • Side By Side Installation Upgrade Overview

  7. SharePoint 2010 UpgradeOption 1 – In-place upgrade • All-or-nothing upgrade requires prep work • Hardware / Software environment needs to be appropriate • 64bit Windows Server 2008 SP2 OR 64bit Windows Server R2 • 64bit SQL 2008 SP1+CU OR 64bit SQL 2005 SP3+CU • Consider this a minimum • Source WSSv3/MOSS 2007 environment needs to have SP2 • Standard in-place caution recommended

  8. In-Place Upgrade and your farm • Each SSP upgrades into: • A Search service app • A User Profiles service app • An Excel service app • An Application Registry backward-compatible service app • A new managed metadata service app • Web application associations are preserved • A proxy is created for each service application • New databases are created as needed

  9. Visual Upgrade Capability • Stay in MOSS 2007 UI (default) or move to Sharepoint 2010 UI • Sharepoint 2010 ships MOSS 2007 Master pages and CSS • UI Preview capability • Farm admin or site admin controlled • Web level setting • Some items not MOSS 2007 UI compatible: • My site host • Report Server web parts

  10. SharePoint 2010 UpgradeOption 2 – Central Admin DB Attach • Central Admin - DB Attach • Content DB and Profile DB are all supported • Supports both build-to-build (b2b) and version-to-version (v2v) scenarios* • Scoped at the content database level – one at a time • Includes visual upgrade *v2v is MOSS 2007 to SP 2010, it does not support WSSv2 or SPS 2003

  11. SharePoint 2010 UpgradeOption 3 – Powershell DB attach • PowerShellCmdlets – DB Upgrade • Upgrade-SPContentDatabase • Supports both build-to-build (b2b) and version-to-version (v2v) scenarios* • Similar to the Central Admin option • Scoped at the database level • Supports parallel db upgrades • Upgrade many DBs simultaneously *v2v is MOSS 2007 to SP 2010, it does not support WSSv2 or SPS 2003

  12. Windows PowerShell Upgrade Cmdlets • Upgrade-SPContentDatabase • Content database B2B/V2V upgrade • Common Scenarios: • Initiate/resume content database B2B upgrades • Resume failed content database V2V upgrades • Upgrade-SPEnterpriseSearchServiceApplication • Search Service Application Instance B2B upgrade • Upgrade-SPSingleSignOnDatabase • MOSS 2007 SSO data to Secure Store database V2V upgrade

  13. Upgrade Logging/Status Reporting • Upgrade Logging • New – One upgrade log per session • New – Upgrade errors only log • New – Fixed upgrade log schema • Upgrade Status Reporting • Improved – Upgrade status page • New – Upgrade status history • New – Command line progress indication

  14. SharePoint 2010Unsupported scenarios for upgrade • No support for direct WSSv2 or SPS 2003 upgrades • No support for side-by-side installs of WSSv3/MOSS 2007 and WSSv4/SharePoint 2010 • No gradual upgrade • No support for 32bit environments (e.g. Virtual Server) • Limited support for co-existence • No support for migration to SharePoint 2010 Online

  15. Default Services Access Services Application Registry Service Business Data Catalog Excel Services Lotus Notes Connector • Enables users to view, edit, and interact with Access databases in a Web browser • Enables users to search and collaborate around business data • Enables structured data from line-of-business applications, such as SAP and Siebel systems, to be integrated into SharePoint Server 2010 • Enables users to view and interact with Microsoft® Office Excel® spreadsheets in a Web browser • Enables users to search data on a Lotus Notes server

  16. Default Services Managed Metadata Service People Search Service Application Secure Store Service State Service • Enables teams or departments to manage their own taxonomy, hierarchies, keywords, and social tagging infrastructure (for example, so that taxonomies and content types can be shared across the organization) • Enables users to search for people within their organization (for example, to find skills, memberships within enterprise communities, and shared interests) • Enables users to index content, gather information, and perform search queries • Enables users to store data securely and associate it to a specific identity or group of identities • Enables users to temporarily store user session data for SharePoint Server 2010 components

  17. Default Services Usage and Health data collection Visio Graphics Service Web Analytics Web Service Word Conversion Service Application • Collects data about how users access pages in a deployment of SharePoint Server, such as the search engine used and keywords that the end user types to find a site • Enables users to perform automated bulk document conversions • Collects farm-wide usage and health data so users can view usage and health reports • Enables users to view and refresh published Visio diagrams

  18. Prepare

  19. Prepare

  20. Accounts Needed for Setup Setup user account • Domain user account • Member of the Administrators group on each server on which Setup is run • SQL Server login on the computer that runs SQL Server • Member of the following SQL Server security roles • Securityadmin fixed server role • Dbcreator fixed server role Server farm account • Domain user account • Dbcreator fixed server role • Securityadmin fixed server role • Db_owner fixed database role for all databases in the server farm

  21. Environment CleanupSpring cleaning for a healthy farm • Delete Stale Sites and Webs (Backup First) • stsadm -o DeleteSite [-force] [-gradualdelete] • stsadm -o DeleteWeb [-force] • Remove Extraneous Document Versions • Primarily user driven, OM operations or tools help • Cleanup Templates, Features, & Web Parts • Primarily user driven, OM operations or tools help • Repair Data Issues • stsadm -o DatabaseRepair [-deletecorruption] • stsadm -o ForceDeleteList • stsadm -o VariationsFixupTool

  22. Operations Scheduling • Note: • Planned 36 hours outage. • Up to 54 hours emergency outage if rollback is required. • Downtime mitigation processes such as read-only databases can be used to reduce outage time.

  23. Upgrade Methods Supported Scenarios Unsupported Scenarios Upgrade from earlier than WSS v3 SP2/MOSS 2007 SP2 Direct upgrade from WSS v2/SPS 2003 or earlier Side by side installation Gradual upgrade • In-Place Upgrade • Database Attach Upgrade: • Content Database • Profile Service Database

  24. Upgrade Preparation Tools WSS v3/MOSS 2007 SP2 SharePoint 2010 Farm review stsadm -o EnumAllWebs SPDiag 2010 (TBD) Content database review Test-SPContentDatabase • Farm review • Pre-Upgrade Checker • stsadm -o EnumAllWebs • SPDiag V2 • Customizations gathering • stsadm -o ExportIPFSAdminObjects

  25. Test-SPContentDatabase • Content database review from Sharepoint 2010 • Complements pre-upgrade checker report • Reports data from server/database pairing • Compares against a specific web application • Identifies current or potential issues: • Data orphans • Missing site definitions • Missing features • Missing assemblies • Can show table sizing metrics • Scans MOSS 2007 and Sharepoint 2010 content databases • Makes no changes to the database

  26. Test

  27. Test

  28. Demo Pre-Upgrade Checker

  29. Implement

  30. Implement

  31. Wizards • Microsoft SharePoint Products and Technologies 14 Preparation Tool • Setup Wizard • SharePoint Product and Technologies Configuration Wizard • Server Farm Configuration Wizard

  32. Microsoft SharePoint Products and Technologies Preparation Tool • A.K.A. prerequisite installer • Installs files from \PrerequisiteInstallerFiles • Confirms/installs: • IIS 7.0 • Microsoft® SQL Server® Client • Microsoft Filter Pack 14 • PowerShell 2.0 (download) • Windows Installer 4.5 (download) • Microsoft® .NET Framework 3.5 SP1 (download) • Microsoft Sync Framework Runtime 1.0 • Microsoft “Geneva” Framework (download) • Microsoft Server Speech Language Pack (English-U.S.) version 6.0 • Microsoft Chart Controls for Microsoft .NET Framework 3.5 • Microsoft Unified Communications Managed API 2.0 Speech Implement

  33. Setup Wizard Much like the WSS 3.0 and MOSS 2007 setup • Prerequisite checks • Server type • Complete • Standalone • WFE only (scripted only) • Binary installation (14 hive) • Registry changes

  34. SharePoint Product and Technologies Configuration Wizard • Post-setup configuration wizard (PSCONFIG.EXE) • New farm • Database server and database name • Database access account and password • Port for Central Administration • Authentication provider (Kerberos or NTLM) Much like the WSS 3.0 & MOSS 2007 experience

  35. Specify Farm Security Settings

  36. Demo In-Place Upgrade

  37. Access Services • Application Registry Service • Business Data Catalog • Excel® Services • Lotus Notes Connector • Managed Metadata Service • People • Search Service application • Secure Store Service • State Service • Usage and Health data collection • Visio® Graphics Service • Web Analytics Web Service • Word Conversion Service application Farm Configuration Wizard Services

  38. Configure farm-wide search dashboard/settings • Search timeout • Ignore SSL warnings • Default content access account • Specify the contact e-mail address • Proxy server • Add crawl rules • Install third party iFilters and configure file types • Create additional content sources • Create crawl schedules • Add priority • Crawl rules • Promote crawled properties to managed properties • Create scopes • Search Center • Add user permission • More – federation, server name mappings, result removal, host distribution rules, etc. Configure Search Service Application

  39. Configure Search Service Application • Enable search reporting • Enable people search • Add user profiles to the People service application • Configure My Site settings • Crawl the profile store

  40. Backup/Restore Databases • Set content databases as read-only • Backup databases • Content databases • SSP database • Restore backups to new SQL Server or as new database names to same SQL Server

  41. Verify Databases • Use test-spcontentdatabasecmdlet • Missing customization • Before navigating to the site, check permissions

  42. Customizations • Copy new site definitions into site templates • Install upgrade definition file • Copy CSS and images • Web parts • Web services • Install features • Install solutions (hopefully you have these) • Web.config changes (for example, security)

  43. Add the Content Databases to the Web Applications • Create Web application(s) • Remove content database • Begin attaching content databases • Root site for Web application must be included in the first content database • stsadm -o addcontentdb -url <URL> -databasename <database name> • Repeat for each content database • Multiple databases at once with multiple instances • Pay close attention to Microsoft® SQL Server® performance

  44. Database Attach Process • Two log files created per database attached • Header in *.log file provides content database name • Progress is reported • Use tail.exe or similar tool to watch progress

  45. More Configuration • Web.config settings – application settings • AAMs • Trusted paths • Managed paths • Farm level permissions • BDC setup

  46. SSP Upgrade • Pre-work (used to be SSP) • Create a new, blank Web application • Start People service and the Managed Metadata service • Create a new Metadata service • Create a new application pool • New People service • Proxy needed • Associate the new proxy with the default proxy group

  47. My Sites • Database attach into empty Web application • People service you want to associate with the My Sites • Setup My Sites • My Site host is in your content database • Check or set inclusions

  48. Find and Fix Issues • Missing Templates • Deprecated Templates • SSP Admin Site • Great Plains (STSPKPL) • Missing Features • Deprecated Features • PortalLayouts • Missing Assemblies • Web parts (STSPKPL) • Forms Based Authentication • Modify config files • Fix-up user identifiers • User Experience • Unghosted pages • Non-reghostable pages • Incompatible HTML • Content Issues • Large/wide lists Post-Upgrade Activities

  49. Validate

  50. Validate

More Related