1 / 28

Upgrading to SharePoint 2010

Upgrading to SharePoint 2010. Don Pistulka Microsoft Technical Specialist CDW . Don Pistulka. Microsoft Technical Specialist, CDW SharePoint Migrations Lead Member of Microsoft's Upgrade IT Kitchen for 2010 Contact/Follow Me @ DonPistulka Don.pistulka@cdw.com

eithne
Télécharger la présentation

Upgrading to SharePoint 2010

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. Upgrading to SharePoint 2010 Don Pistulka Microsoft Technical Specialist CDW

  2. Don Pistulka • Microsoft Technical Specialist, CDW • SharePoint Migrations Lead • Member of Microsoft's Upgrade IT Kitchen for 2010 • Contact/Follow Me • @DonPistulka • Don.pistulka@cdw.com • Donpistulka.spaces.live.com

  3. Agenda • Overview of What’s New/Changed • Upgrade Methodology • Get Prepared Today • Requirements for Upgrade to 2010 • Supported Upgrade Methods • Unsupported Upgrade Methods • Visual Upgrade • Pre-Upgrade Checker • 3rd Party Tools – When to us them

  4. 2010 Upgrade Overview • New and Improved • Upgrade Status Reporting • Improved – Upgrade status page • New – Upgrade status history • New – Command line progress indication • Upgrade Logging • New – One upgrade log per sessions • New – Upgrade errors only log • New – Fixed upgrade log schema • Read-only DB Support • Farm Insight • Pre-Upgrade Checker • stsadm –o EnumAllWebs (Now includes the features that are installed in a Web) • SPDiagV2 • Customizations gathering • stsadm –o ExportIPFSAdminObjects

  5. What’s New for Upgrade • Parallel Upgrades • Visual Upgrade • V2V and B2B Support • Pre-Upgrade Checker • Resume-able Upgrade • STSADM (SP2) • stsadm-o enumallwebs (Shows orphaned sites) • stsadm-o enumallwebs -databasenamesharepoint_site_content_db • stsadm-o variationsfixuptool • stsadm–o deletesite (With force allows you to delete orphaned sites) • Test-SPContentDatabase

  6. Upgrade Methodology • Learn • Prepare • Test Read upgrade documentation – Resources • Implement • Validate Run Pre Upgrade Checker Beta bits are out – Test lab • Upgrade to 2007 SP2 October CU • Meet Requirements Find issues in test labs and beta

  7. Preparing for 2010 Today • Prepare Your Environment • Clean up unused sites (Archive or delete) • Limit Databases to 100GB’s • Move sites/ site collections • Optimize large lists and views • Remove unused features/add missing features • Test, Test, Test • Make a virtual copy of your environment in Hyper V • Run pre-upgrade checker • Use Visual Upgrade (More on this later) • Mock upgrade – Beta now Available • Do it again • Get Hardware in Place as Needed • Understand SharePoint 2010 requirements

  8. Requirements for 2010 • 64 Bit Hardware and Software • Windows Server 2008 and R2 64 bit • SQL 2005 or 2008 64 bit • 8GB RAM Minimum for WFE’s • IE7, IE8, Safari and FireFox3x – No support for IE6 • Software Prerequisites

  9. Software Prerequisites • Microsoft SQL Server 2008 SP1 (http://go.microsoft.com/fwlink/?LinkId=166490) • Microsoft SQL Server 2005 SP3 (http://go.microsoft.com/fwlink/?LinkId=166496) • Microsoft Windows Server 2008 Standard SP2 (http://go.microsoft.com/fwlink/?LinkId=166500) • Microsoft .NET Framework 3.5 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=131037) • Microsoft SQL Server 2008 Express Edition Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=166503) • Microsoft "Geneva" Framework (http://go.microsoft.com/fwlink/?LinkID=165752) • Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/?LinkID=141237&clcid=0x409) • Microsoft Filter Pack 2.0 (http://go.microsoft.com/fwlink/?LinkId=166504) • Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://go.microsoft.com/fwlink/?LinkID=141512) • Windows PowerShell 2.0 CTP3 (http://go.microsoft.com/fwlink/?LinkId=165758) • Microsoft SQL Server 2008 Native Client (http://go.microsoft.com/fwlink/?LinkId=166505) • Microsoft SQL Server 2008 Analysis Services ADOMD.NET (http://go.microsoft.com/fwlink/?LinkId=130651) • Microsoft Silverlight 3.0 (http://go.microsoft.com/fwlink/?LinkId=166506) • ADO.NET Data Services v1.5 CTP2 (http://go.microsoft.com/fwlink/?LinkId=158354) for Windows Server 2008 SP2 • ADO.NET Data Services v1.5 CTP2 (http://go.microsoft.com/fwlink/?LinkId=159780) for Windows Server 2008 R2

  10. Upgrade Methods • Database Attach • Still the most common • Parallel Upgrades • Command line (STSADM) and PowerShell Cmdlets • In Place Upgrade • Need hardware • Only preferred for smaller farms • Testing still required • Single Click Install - SQL Migration • Windows Internal Database (WID)

  11. 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

  12. Visual Upgrade • Stay in 2007 UI (default) or move to 2010 UI • UI Preview capability • Farm admin or site admin controlled • Web level setting and OM • Some items not 2007 UI compatible: • My site host • PWA site collection • Report Server web parts

  13. Visual Upgrade

  14. Visual Upgrade

  15. Preview

  16. Apply Visuals

  17. PreUpgradeCheck • STSADM.exe –o preupgradecheck • Makes no changes to environment or data • Not Required • A list of all servers and components in the farm, and whether the servers meet the following requirements for upgrading: 64-bit hardware and the Windows Server 2008 operating system. • The alternate access mapping URLs that are being used in the farm. • A list of all site definitions, site templates, features, and language packs that are installed in the farm. • Whether there are customizations in the farm that are not supported (such as database schema modifications). • Whether there are any database or site orphans in the farm. • Whether there are missing or invalid configuration settings in the farm (such as a missing Web.config file, invalid host names, or invalid service accounts). • Missing features or site definitions • Whether the databases meet the requirements for upgrade — for example, databases are set to read/write, and any databases and site collections that are stored in Windows Internal Database are not larger than 4 GB.

  18. No Failures

  19. With Failures

  20. PowerShell 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 • O12 SSO data to Secure Store database V2V upgrade

  21. Database Attach Process using STSADM • stsadm -o addcontentdb -url<URL> -databasename<database name>

  22. 3rd Party Tools • Quest Software • Metalogix • Scenarios for 3rd Party Tools • POC or Pilot of one site/department • Move to different templates (Publishing) • Re-factor. Move sites to new, smaller databases • Limit the data being migrated • Move a site to new site collection • Promote a site to a site collection • Direct Migration from 2003

  23. Resources • http://msdn.microsoft.com/en-us/sharepoint/ee514557.aspx • Roadmap for Upgrade - http://technet.microsoft.com/en-us/library/ee731988(office.14).aspx • Upgrade Search Service - http://technet.microsoft.com/en-us/library/cc263403(office.14).aspx • SharePoint Team blog - http://blogs.msdn.com/sharepoint/archive/2009/05/07/announcing-sharepoint-server-2010-preliminary-system-requirements.aspx

More Related