320 likes | 407 Views
SharePoint 2010 Installation & Upgrade. Randy Williams , MVP SharePoint Server rwilliams@synergyonline.com. Who is Synergy?. SharePoint Consulting Implementation Development Branding SharePoint Training Administration Design Development Upgrade. www.synergyonline.com.
E N D
SharePoint 2010 Installation & Upgrade Randy Williams, MVP SharePoint Server rwilliams@synergyonline.com
Who is Synergy? • SharePoint Consulting • Implementation • Development • Branding • SharePoint Training • Administration • Design • Development • Upgrade www.synergyonline.com In the business of making your business better.
Agenda • SharePoint 2010 System Requirements • SharePoint 2010 Installation • Upgrade Methods • Upgrade Preparation • Upgrade Overview
SharePoint 2010 Requirements • 64 bit operating system for application servers • Windows Server 2008 or 2008 R2 • 64 bit SQL Server • SQL 2005/2008/2008 R2 • For Development environments • 64-bit Vista SP1 and Windows 7 • Virtualization is definitely an option • Hyper-V • VMware
Client Desktop Considerations • A standards-based browser is needed to author content • IE 7, IE 8, Firefox 3.x • Better support for Safari • No support for IE 6 • Desktop version of Office • With a possible desktop refresh, it is a great time to consider an Office update • Office 2010 will provide the best integration
Installation Overview 1. Install software prerequisites 2. Install SharePoint 3. Create or Join Farm 4. Create Service applications
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 • Service Databases
Upgrade Preparation - Overview • Upgrade farm to at least SP2 • Run Pre-Upgrade Checker • Clean up and optimize • Document farm customizations and configuration changes • Build a test farm
Farm Investigation Tools • STSADM Operations • PreUpgradeCheck (SP2) • EnumAllWebs (SP2) • EnumSites • SPDiag V2 - http://technet.microsoft.com/en-us/library/dd745013.aspx • SPDocGen - http://spdocgen.codeplex.com/ • WinDiff / WinMerge
Pre-Upgrade Checker Commandstsadm -o preupgradecheck [-localonly] Details Rules Files (Partial List) Informational Farm Servers, Databases AAM Configuration Lists Site Definitions, Features, Web Parts, Event Receivers Installed Language packs CAML views/CAML content types Issues Missing Site Definitions, Features, Assemblies Data orphans Modified content databases • Reports farm and server data • Identifies useful farm information • Identifies current or potential issues • Modes • Local server + farm databases (default) • Local server only • Makes no changes to environment or data • Introduced in SP2; improved in October 2009 CU
UI Upgrade • Migrating to SharePoint 2010 • All content will migrate over • Most branding will not be unaffected • SharePoint 2007 / 3.0 style UI is retained • Existing master pages & page layouts are used • Manually migrate to SharePoint 2010 UI • Ribbon, Improved Site Settings, AJAX • Visual Upgrade
Visual Upgrade • Stay in 2007/v3 (default) or move to 2010 UI • 2010 ships 2007/v3 Master pages and CSS • UI Preview capability • Farm admin or site admin controlled • Web level setting • Some items not 2007/v3 UI compatible • My site host • PWA site collection • Report Server web parts
In-Place Upgrade • All-at-once upgrade • Must upgrade the whole farm at one time • Cannot intermingle SP 2007 and SP2010 in same farm • Schedule downtime • Simplest approach, but most risky • No going back • Upgrade resume if problems occur • Recommendations • Test content databases on SP 2010 farm • Do a full farm backup before you start!
Database Attach Upgrade • Safer, but more complex than in-place • Upgrade is done on a separate 2010 farm • Done database-by-database • Can be used as a gradual upgrade • Use Test-SPContentDatabase (PowerShellcmdlet) to test database first • To attach • Upgrade-SPContentDatabase (PowerShell) • Addcontentdb operation (STSADM) • Parallel database upgrades are possible
Upgrading your SSPs • When using in place upgrade • Each SSP gets upgraded into a new service app • Web application associations are preserved • A proxy is created for each service app • New databases are created as needed • When using database attach • Personalization (user profile, My Sites) is upgraded • Must manually reconfigure • Search, InfoPath, BDC, Excel Services
What can I do today to prepare? • Work towards 64-bit server environments • Upgrade to Service Pack 2 (SP2) • Run PreUpgradeCheck • Review and identify your customisations • Cleanup as much as possible • Organise your WSP Solutions • Optimiselarge lists & content databases • Build a test farm • Verify custom solutions work and deploy in 2010
Additional Resources • http://msdn.microsoft.com/en-us/sharepoint/ee514557.aspx • http://technet.microsoft.com/en-us/sharepoint/ee517214.aspx • http://www.slideshare.net/joeloleson/preparing-for-upgrade-to-sharepoint-2010-with-joel-oleson-quest-software-webcast • http://MSSharePointITPro.com
Questions? • rwilliams@synergyonline.com • Blog: http://www.synergyonline.com/randy