SharePoint 2010 Upgrade
- 1. SharePoint 2010 Upgrade Veenus Maximiuk SharePoint Managing Architect ICC July 1, 2011
- 2. Agenda Upgrade Cycle Learn Prepare Test Implement Demo Validate Lessons Learned 2
- 3. Upgrade Cycle: Overview Learn • Requirements/ prerequisites • Upgrade methods • Downtime mitigation • Common Issues Validate Prepare • Upgrade event failures • Document environment • UI/UX issues • Manage customizations • Data issues • Plan upgrade strategy Implement Test • Build/upgrade farms • Build test farms • Deploy customizations • Use real data • Minimize downtime • Evaluate techniques • Monitor progress • Find issues early 3
- 4. Upgrade Cycle: Learn Learn • Requirements/prerequisites • Upgrade methods • Downtime mitigation • Common Issues 4
- 5. Learn Minimum Hardware Requirements • 64-bit Processor • Quad processor for WFE and Applications Servers • 2.5 GHz minimum per core • 4 GB for developer or evaluation use Memory • 8 GB for single server and multiple server farm Storage • 80 GB for installation 5
- 6. Learn Minimum Software Requirements SQL Server/Server OS/Client Browser • x64 Edition SQL Server 2005 • Service Pack 3 and Cumulative Update 3 • x64 Edition SQL Server 2008 • Standard • SP1 and Cumulative Update 2 • x64 Windows Server 2008 SP2 Standard Operating System • x64 Windows Server 2008 R2 Standard • Internet Explorer 7, 8, and 9 Client Browser • Firefox 3.6 • Safari 4.04 6
- 7. Learn Prerequisites SharePoint Server • SQL 2008 Native Client • Windows Identity Foundation • Sync Framework Runtime v1.0 (x64) • Chart Controls for .NET Framework 3.5 • Filter Pack 2.0 • SQL Server 2008 Analysis Services ADOMD.NET • Speech Platform Runtime • Speech Recognition Language • Windows PowerShell 2.0 • Web Server Role • Application Server Role • Microsoft .NET Framework 3.5 SP1 Windows Server 2008 • KB976394 Windows Communication Foundation (WCF) Fix Windows Server 2008 R2 • KB976462 Windows Communication Foundation (WCF) Fix 7
- 8. Learn Supported Upgrade Methods • Preserve farm wide settings, customizations, and URLs In-place • Farm is offline during the upgrade process • Incur most downtime • Potential out of disk space risk Database • Upgrade multiple content DBs at the same time • Must transfer settings from old farm to new farm Attach • Must apply customizations manually • Preserve farm wide settings, customizations, and URLs • Upgrade multiple content DBs at the same time Hybrid • Farm is offline during the administrative databases upgrade process • Potential out of disk space risk 8
- 9. Learn Visual Upgrade An upgrade method that allows for independent upgrade of infrastructure and site rendering 9
- 10. Learn Supported In-place Upgrade Paths MOSS 2007 MOSS 2007 SharePoint SP2 x86 SP2 x64 Server 2010 WSS 3.0 SP2 MOSS 2007 MOSS 2007 SharePoint x86 SP2 x86 SP2 x64 Server 2010 SharePoint WSS 3.0 SP2 WSS 3.0 SP2 Foundation x86 x64 2010 10
- 11. Learn Unsupported Upgrade Methods 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. Learn Common Upgrade Failure Issues & Recovery Determine cause of failure Status Page & Upgrade Logs: Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14Logs Error log Full upgrade log Customizations Management Commands: Test-SPContentDatabase stsadm -o EnumAllWebs Fix issue(s) Install missing or updated customizations Activate missing services; farm, web app settings Resume upgrade Farm upgrade command Content database specific upgrade command Service specific upgrade commands
- 13. Upgrade Cycle: Prepare Prepare • Document environment • Manage customizations • Plan upgrade strategy 13
- 14. Prepare Plan & Prepare Checklist Prepare Server, Client Desktop/Laptops Document environment Revisit Farm and network structure Review hardware end of life Identify customizations Plan for upgrade capacity disk space, memory, processor Plan upgrade strategy Farm/Topology/Services upgrade order/plan Order of Operations Downtime limits / mitigation plan Rollback process Schedule Communication Plan 14
- 15. Prepare PreUpgradeCheck Command stsadm command shipped with SP2 -o preupgradecheck Checks for prerequisites and known issues Rules based Informational Errors Makes no changes Additional/updated rules is included in October Cumulative Update stsadm –o EnumAllWebs –IncludeWebParts improvements to find other customizations at SPWeb level 15
- 16. Prepare PreUpgradeCheck Report • Content Sources & Start address • Farm & Search Topology Information & • Servers Configuration • Upgrade Types • AAMs, Large Lists & Libraries • Site Definition (referenced & missing) Important Issues • Installed Language Pack and • Features (referenced & missing) Dependencies • Custom List Views & Custom Fields Types, Web.config entries 16
- 17. Prepare PreUpgradeCheck Report Sample – Passed 17
- 18. PreUpgradeCheck Report Sample Prepare Requires Attention 18
- 19. PreUpgradeCheck Report Sample Prepare 19
- 20. Prepare Test-SPContentDatabase Checks database compatibility before attaching 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 Works with 2007 and 2010 content databases Makes no changes to the database 20
- 22. Prepare Tools to Identify Customizations & Cleanup Identify Customizations Cleanup • Windiff • Remove excessive document versions • Beyond Compare • Remove unused features, templates, web • Web.config parts • SafeControls elements • Repair Data Issues • SPDiag (SharePoint Admin ToolKit) • stsadm –o DatabaseRepair • PreUpgradeCheck • stsadm –o ForceDeleteList • Stsadm –o PreUpgradeCheck (in SP2) • stsadm -o VariationsFixupTool • Test-SPContentDatabase (PS Script 2010) • Delete Orphans • stsadm –o DeleteSite –force –id GUID • stsadm –o DeleteWeb –force –id GUID 22
- 23. Prepare Pre-Upgrade Considerations/Strategy Amount of Data and Customization • Upgrade performance is directly proportional to the amount of data being upgraded • Upgrade complexity is directly proportional to the amount of customization Dependent Applications • Consider upgrading from SQL Server 2005 to SQL Server 2008 before upgrading SharePoint • Web parts • Third party applications • Applications dependencies on v3 and may not work with v4 Downtime • Service Level Agreement (SLA) • In-Place vs. DB Attach vs. Hybrid URL Changes • DB Attach/Hybrid - URL may remain or change 23
- 24. Upgrade Cycle: Test Test • Build test farms • Use real data • Evaluate techniques • Find issues early 24
- 25. Test Build Test Farms Use real data (copies of production databases) To identify trouble areas To determine upgrade performance Measure sequences and actions Use similar hardware if possible Use similar network/firewall configuration if possible 25
- 26. Test Evaluate Techniques Upgrade method Comparison of In-Place vs. DB Attach vs. Hybrid Downtime mitigation This will provide an estimated downtime for production upgrade Troubleshooting/validation Fix errors Apply missing customizations Apply missing settings Web parts Third-party applications 26
- 27. Test Search Run crawls and review logs Run search queries View query reports Web application level Site collection level Search people and profile Search customizations 27
- 28. Test Customizations Large list query throttling STP files for sites are deprecated Save site as template now generates .WSP Master pages and CSS Toolbar actions properly moved to ribbon Workflows must be redeployed 28
- 29. Test Customizations Considerations Customization Common Choice Recommendation Site template Recreate in v4 Recreate in v4 using WSP model Custom site definition Create v4 site definition Migrate sites to OOTB site definition, Create User-defined function upgrade then apply features with (UDF) solution deployment Un-ghosted page Revert to site definition Review options: retain customizations or revert and possibly re-ghost Add-ons workflow, server Determine per solution Determine per solution controls Contact vendor Contact vendor Custom web parts Works most of the time Test it out on a test server Event handler Works most of the time Rewrite and redeploy as a feature Code or pages in /_layouts Ignore and re-evaluate Analyze and create solution deployments for requirements Themes Recreate in v4 Use Visual Upgrade Recreate theme in v4 29
- 30. Upgrade Cycle: Implement Implement • Build/upgrade farms • Deploy customizations • Minimize downtime • Monitor progress 30
- 31. Implement Required Accounts • Domain user account • Member of the Administrators group on each SharePoint server • SQL Server login on the computer that runs SQL Setup User Account Server • Member of the following SQL Server security roles • Securityadmin fixed server role • Dbcreator fixed server role • Domain user account • Dbcreator fixed server role Server Farm • Securityadmin fixed server role Account • Db_owner fixed database role for all databases in the server farm 31
- 32. Implement Hybrid Upgrade Process Run the pre-upgrade checker Disconnect users Run Microsoft SharePoint 2010 Products Preparation Tool Detach content and SSP databases Run setup An opportunity to back out Run SharePoint Product and Technologies Configuration Wizard Convert forms-based authentication to claims based authentication Only if Web application was configured to use forms-based authentication 32
- 33. Implement Hybrid Upgrade Process (cont’d) Attach content and SSP databases Wait… Configure new services Managed Metadata service Upgrade profile properties to managed metadata and User Profile service applications Move-SPProfileManagedMetadataProperty Update-SPProfilePhotoStore Wait again Start a full crawl 33
- 35. Implement In-place/Hybrid Upgrade Previous Version 35
- 36. Implement Specify Farm Security Settings This is a password that is used to encrypt all communications across the farm. The farm passphrase is required to be input anytime you wish to remove a server from the SharePoint farm or add a server to the farm. The password should be recorded and kept in a safe place and can be changed through Windows PowerShell by the administrator. 36
- 38. Implement SharePoint Services Access Services Secure Store Service Application Registry Service State Service Business Data Catalog Usage and Health Data Collection Excel Services User Profile Service Application Lotus Notes Connector Visio Graphics Service Managed Metadata Service Web Analytics Web Service PerformancePoint Service Word Conversion Service Application Application Search Service Application 38
- 39. Implement In-place/Hybrid Upgrade - SSP 39
- 40. Implement Installation Process – Database Attach Run Microsoft SharePoint 2010 Products Preparation Tool Run setup wizard Run PowerShell to create SharePoint configuration and Central Administration Content databases Run SharePoint Product and Technologies Configuration Wizard Register Managed Accounts Run Server Farm Configuration Wizard to provision Service Applications POC or Development Run PowerShell to Create Service Applications Staging and Production environments 40
- 41. Implement Customizations Install upgrade definition file Copy CSS and images Web parts Web services Install features Install solutions Web.config changes 41
- 42. Implement Upgrade Tasks for DB Attach Set database to be read-only Backup and restore content database Create Web Application Test Database Test-SPContentDatabase -Name Content_DB -WebApplication http://MyPortal Look for UpgradeBlocking: False/True Upgrade SSP Start User Profile and Managed Metadata services Run New-SPProfileServiceApplication Run New-SPProfileServiceApplicationProxy 42
- 43. Implement Upgrade Tasks for DB Attach (cont’d) Upgrade My Site Host and Personal Site Collections Run Test-SPContentDatabase Install missing DLLs and features Run Test-SPContentDatabase again Mount-SPContentDatabase Set up My Sites Run iisreset Upgrade Content Databases Mount-SPContentDatabase -Name Content_DB –WebApplication http://MyPortal Validate Site 43
- 44. Database Attach Upgrade Walkthrough Demo 44
- 45. Upgrade Performance Implement Why prediction is difficult Database Shape Centric Hardware Centric • # Site Collections • SQL Disk I/O per second • # Webs • SQL Database to disk layout • # Lists • SQL Temp DB optimizations • # Document Versions • SQL CPU & Memory • Document Versions Size • WFE CPU & Memory • # Documents • Network Bandwidth & latency • # Links • Overall DB Size 45
- 46. Upgrade Cycle: Overview Validate • Upgrade event failures • UI/UX issues • Data issues 46
- 47. Validate Validate Discussion Verify High Impact/High Profile sites Create a new site collection/libraries and verify basic functionality Review application event log and upgrade log for failures Review UI/UX issues (XHTML/SXLT/MasterPages) External Data Sources Security requires special attention post-upgrade Migrate to Claims Based Authentication 47
- 48. Validate Post Upgrade Checklist Add Administrators to Web Application Set Default Quota Template Filter People Picker to Active Directory Forests stsadm -o setproperty -pn peoplepicker-searchadforests -pv "forest:demo.vm.local;domain:icc.ohio.com,DOMAINAccountName,"Password" -url http://WebApplication AAMs IIS bindings Add Trusted paths Import Administrator-approved form templates and data connection files Configure Caching Scheduling the Warm-up Script on SharePoint Servers 48
- 49. Issues Encountered E-mail alerts not sent to ‘Assigned To’ person Disable and re-enable People search error 'Property doesn't exist or is used in a manner inconsistent with schema settings.’ Check the Use Location Visualization check box – under People Search Core Results Excel services Add https under Trusted File Location Large list throttling Indexing Disable list throttling 51
- 50. Lessons Learned Customizations Solutions Training Features Install Productivity Hub Look in 12 hive TemplatesFeatures Custom Site Definitions Themes Sites may need to be re-ghosted Look in 12 hive TemplatesThemes Web.config Compare with OOTB web.config FAB 40 12 hive Cannot create a new version Compare with a clean environment Clean up data before upgrade Look for a different date than other folders Watch out for Workflow History Limit SharePoint Designer use 52
- 51. Automatic Installation Resources Remote Install with SPModule http://sharepoint.microsoft.com/blogs/zach/lists/posts/post.aspx?ID=55 Allows for remote install of SharePoint 2010 farm using Windows PowerShell Automatic SharePoint Installer http://autospinstaller.codeplex.com/ Scripted installs make for consistent environments and ideal for DR documentation 53
- 52. Customizations Upgrade Resources Upgrading a Custom Site Definition http://msdn.microsoft.com/en-us/library/aa543837.aspx Upgrading Master Page http://www.andrewconnell.com/blog/archive/2010/08/09/upgrading-a-sharepoint- 2007-wcm-site-to-sharepoint-2010-wcm.aspx http://www.andrewconnell.com/blog/archive/2010/08/09/upgrading-a-site- collection-from-sharepoint-server-2007-wcm-to.aspx Upgrade Resource Center – SharePoint 2010 http://msdn.microsoft.com/en-us/sharepoint/ee514557 54
- 53. References Migration and Upgrade Information for SharePoint Developers http://msdn2.microsoft.com/en-us/office/aa905505.aspx Migration and Upgrade Information for SharePoint Server (IT Pros) http://technet.microsoft.com/en-us/sharepoint/ee517214 Upgrade Documentation http://technet.microsoft.com/en-us/library/cc303420.aspx Troubleshooting Upgrade Issues http://technet.microsoft.com/en-us/library/cc288476.aspx Microsoft SharePoint 2010 Administration Toolkit http://www.microsoft.com/download/en/details.aspx?id=20022 Upgrade in WSS SDK http://msdn.microsoft.com/en-us/library/ms460185.aspx 55
- 54. Q&A 56
- 55. Thank You Veenus Maximiuk www.iccblogs.com/blogs/vmaximiuk vmaximiuk@iccohio.com Joe Hartsel jhartsel@iccohio.com 57