More than Just Lines on a Map: Best Practices for U.S Bike Routes
Upgrade SharePoint 2003/2007 to SharePoint 2010
1. SharePoint 2003/2007 to SharePoint 2010 Upgrade Leonard Mwangi MCDBA, MCTS eTek Global Inc. We make IT work for You | Microsoft Solutions
2. Quick survey Microsoft Office? 2003? 2007? 2010? SharePoint version 2003 2007 2010 How often do you use SharePoint in a daily basis? Often Really Never
4. Things you should know (best practice) Requirements Hardware – x64 Operating System – Windows 2008 or Windows 2008 R2 Database Server – SQL 2005, SQL 2008 or SQL 2008 R2 No direct upgrade path from SPS 2003 to SPS 2010
5. Things you should know (best practice) Pre-upgrade requirements Service Pack 2 (MOSS & WSS) Pre-upgrade checker process Upgrade process decision (in-place, database attachment, hybrid process) Customizations Restructuring Databases sizes Database back-ups
6. Upgrade preparation Understand your environment Prepare for the upgrade Test, Test, Test Implementation Validate the process Review ULS
7.
8. user profiles in SSP are upgraded and moved to user taxonomy & profiles database.
14. Downtime mitigation Hybrid approach In-place upgrade Pros:- Farm settings are preserved. Customizations are still available after upgrade. Take advantage of multiple content db’s upgrade. Cons:- Network glut Direct access to SQL Server
15. Downtime mitigation Hybrid approach – read only Pros:- Existing farm still accepting user requests Take advantage of multiple content db’s upgrade. Hardware & Software upgrades Cons:- Customizations are not upgraded. Services & farm settings not upgraded Network glut Direct access to SQL Server
Pre-upgrade check – no of servers, Alternate Access mappings, Site definition, customizations, orphaned sites, invalid config, db requirementsRestructuring – multiple farms into one farm – April 2009 Cummulative update allows AAM settings in each content db allowing web apps to exist in the same farm without merging the URL’sGet-SPDatabase | Sort-Object disksizerequired -desc | Format-Table Name, @{Label ="Size in MB"; Expression = {$_.disksizerequired/1024/1024}}
Pre-upgrade check – no of servers, Alternate Access mappings, Site definition, customizations, orphaned sites, invalid config, db requirementsRestructuring – multiple farms into one farm – April 2009 Cumulative update allows AAM settings in each content db allowing web apps to exist in the same farm without merging the URL’sGet-SPDatabase | Sort-Object disksizerequired -desc | Format-Table Name, @{Label ="Size in MB"; Expression = {$_.disksizerequired/1024/1024}}
