Session Code: PRC20
Title of Presentation
Shane Young
President
SharePoint911
2
Todd Klindt
Consultant
Solanite
Session Objectives and Agenda
3
Upgrade/Migration Path
Content Management
Server 2002
Microsoft Office
SharePoint Server 2007
SharePoint Portal
Server 2003
Windows SharePoint
Services 2.0
4
Windows SharePoint
Services 3.0
Preparing for Upgrade
Scope and plan your upgrade
Review Hardware End of Life, plan for upgrade capacity disk
space, memory, processor
Test your upgrade and estimate your upgrade duration
Review customizations
Keep or decommission customizations
Cleanup
Remove orphans, increase close quotas, remove locks
Service offering
Redesign, training, communication plan
5
Prerequisites
Do a backup
Make sure you know how to recover from backup
Get all SharePoint servers to Service Pack 2 or
later
Run prescan.exe early and repeat as necessary
6
Running Prescan.exe
SharePoint Server: prescan.exe /c preupgradescanconfig.xml
/all
Windows SharePoint Services: prescan.exe /all
Prescan Log and Summary created in \%temp%\
7
What Will Prescan find?
Sites based on site templates: Site
Template Upgrade Kit
http://www.microsoft.com/downloads/details.aspx?FamilyID=
a70bd8f8-a0f0-4d00-9010-8e40b7c98f68&displaylang=en
Sites based on custom site definitions
Un-ghosted pages
Orphaned objects
Custom Web Parts
Sites that need language packs
8
9
Prescan
Example of good Prescan results
07/19/2006 17:17:01 Scan finished without failure
07/19/2006 17:17:01 Number of sites skipped (already
scanned): 0
07/19/2006 17:17:01 Number of sites scanned: 1
07/19/2006 17:17:01 Number of broken sites: 0
07/19/2006 17:17:01 Number of webs scanned: 13
07/19/2006 17:17:01 Number of broken webs: 0
07/19/2006 17:17:01 Number of webs using custom
template: 0
07/19/2006 17:17:01 Number of pages scanned: 0
07/19/2006 17:17:01 Number of unghosted pages: 63
10
Issues Found with Prescan?
Site/List not scanned error at the end of the log
Solution: Post-SP2 Hotfix
UpdateListSchemaInAllWebs() Method not
found
Solution: Install SP2
Virtual server is not in a ready state
Solution: Run it against v2 Virtual server
Great resource for errors and resolutions
http://blogs.technet.com/wbaer/archive/2006/12/22/
prescan-errors-what-they-mean.aspx
11
Core Upgrade Methods
In-Place Upgrade
Gradual Upgrade: Side by Side Upgrade
Content DB Migration: Upgrade
Into Separate Farm
12
In Place Upgrade
Pros
Simple and fast upgrade
Best for smaller or non-production environments
Cons
Environment offline during upgrade
Riskier in large environments
Upgrade fails if it encounters errors; -fix then rerun
Not recommended for most deployments
Even for customers whose production environment is perfect
for this scenario, I still recommend gradual method. Why?
Lack of flexibility and recoverability
13
Database Mapping
14
V2 Config DB
V3 Config DB
V2 Search and User
Profiles DBs
SSP DB
Search DB
V2 Content DBs
V3 Content DBs
Gradual Upgrade
Pros
Old and new SharePoint versions run in parallel
Allows upgrade with minimal downtime
Only the site collection you are upgrading is unavailable
Can roll back upgrades per site collection
Cons
Redirector could cause user confusion
Uses URL redirects which aren’t compatible with
Microsoft Office and most other applications
Additional impact from two SharePoint versions
Requires lots of extra SQL storage space
15
Gradual Upgrade Process
http://WSS
http://WSSold
http://WSS
WSS 2003
Web App
WSS 2007
Web App
WSS Farm
Config
SQL Instance
16
Content
Temp
Content
Config
Gradual Upgrade URL Redirection
Current URL: http://portal.company.com
During upgrade, define temporary URL
http://portal.company.com:8080 or
http://temp-portal.company.com
All v2 content moved to temporary URL
v3 automatically redirects requests to temp
URL using 302 redirects
As each site collection is upgraded v3 content
is placed at current URL
v2 content still available at temp URL
17
Upgrade steps
On existing hardware, install SP2, .NET Framework 3.0,
then run Prescan
Prepare URL Redirect Domain
Install Binaries and Choose
Gradual Upgrade option
Run Configuration Wizard to setup a new farm
Install Language Packs
Deploy Upgrade Definition, Site Definition
and Feature Files
Deploy Custom Web Part Packages and
any other custom code (only if in Bin directory)
Upgrade steps
Review log files and resolve any issues
Repeat setup and upgrade on each
server in the farm
Start content upgrade thru UI or stsadm
Review your upgraded content
If customized sites, reset pages to 2007
site definition versions
Fix issues and reapply customizations
using SharePoint Designer
If upgrade result is undesirable, revert to 2003 site
Revert to 2003
When upgrade result is undesirable,
“revert” deletes 2007
and resets redirect to 2003
Confirm 2003 site still exists before reverting to it
Revert to 2003 via UI or command line
UI: Select Sites for Upgrade > Revert Site
Command line: stsadm –o upgrade –revert
Once complete, re-upgrade original
Use SharePoint Designer to merge
changes from “fixed”
and re-upgraded versions
Finalize Upgrade
Business/Customer approval
Removes gradual upgrade redirector
You can remove SharePoint 2003 afterwards
You can still upgrade using
database attach method
Scenarios
Works best for staging environment
Environments with heavy customizations
Recommended for large databases
and site collections
Upgrade a subset of site collections only
Environments requiring minimal migration window
Content DB Attach Upgrade
Pros
Fast upgrade method
Best option if you have 1000s of site collections
Cons
You must redeploy custom configuration
Install Web Parts
Define inclusion rules
Setup search and related components
Note: This does still require Prescan.
Method Required for scalable hosting mode/account creation
mode, and host header mode deployments
23
Content DB Migration
– SQL CPU
– SQL Disk I/O
SQL Server
2003
Config
2007
Config
2003
Content
2007
Content
2003 Farm
24
2007 Farm
Content DB Migration Steps
Create new 2007 farm on clean hardware
Install prerequisites
Configure farm-level settings
Create a new Web application for each
2007 virtual server
Manually re-apply configuration settings
Ensure all inclusions re-created in 2007 (required)
Deploy Upgrade Definition, Site Definition
and Feature Files
Deploy custom Web Parts to GAC or BIN
25
Continued
Run Prescan on farm or Web application
and correct any issues
Back up 2003 content database using SQL
Restore backup to copy in 2007 farm
Add content DB to Web application
via command line
Ensure root site included in first database
stsadm –o addcontentdb
Upgrade triggers automatically, runs
until it completes
For large databases, command line preferable
Review log files for any issues
Repeat for all additional content and search/user profile databases
stsadm –o restoressp
Scenarios
Moving to new hardware or a new architecture
Customers who need to maximize
upgrade throughput
Required for Scalable Hosting Mode or
Active Directory Account Creation Mode
Recommended for large farms
Methods in a Nutshell
In-Place
Simple
Pros
Cons
Scenarios
Uses existing
hardware
Gradual
Provides granularity
Provides revert back option
Reduces user impact
Uses existing hardware
Entire farm offline
during upgrade
Hardware-intensive, memory and
storage
No revert back
option
URL Redirects during upgrade
Failure will stop
upgrade
WSS Scalable Hosting mode not
supported
Dev/Test
platforms
Performance impact on 2003 farm
Medium, large farms
Customized environments
Large databases and site collections
DB Attach
Upgrade to new farm
Existing, 2003, farm not
affected
Complex, many manual
steps
Requires new farm an up
to double storage
New hardware and
topology
WSS Scalable Hosting
modes
Large databases
28
Need more methods?
Content Migration Upgrade
Multi Threaded Database Attach
Virtual In Place Upgrade
Migrate Then Upgrade
http://blogs.msdn.com/joelo/archive/2007/05/22/3-methods-to-upgradelet-me-give-you-4-more.aspx
29
Multithreaded DB Attach
2007 Farm
2007 Farm
2007 Farm
2003
SQL Instance
.
.
2007 Farm
2007 Farm
Customization Considerations
Customization
31
Common Choice
Recommendation
Site Template
Revert to Site Definition
Use Site Template Upgrade Toolkit
Custom Web Part
Works most of the time (Gradual)
Test it out on a sample server with .NET
2.0 (DB Attach)
Event Handler
Works most of the time (Gradual)
Rewrite and Redeploy as a Feature
Un-ghosted Page
Revert to site definition
Review options: Retain customizations
or revert
Themes and Stylesheets
Reapply Theme
Create Masterpage or stylesheet to
apply standardization
Custom Site Definition
Create v3 Site Definition
Create Upgrade Mapping and
Prescan Mapping
Migrate sites to out of box site
Definition, upgrade then apply features
with Solution Deployment
Code or pages in /_Layouts
Ignore and re-evaluate (gradual)
Analyze and create solution
deployments for requirements
Inclusions/Exclusions
Ignore with Gradual
Recreate Inclusions (DB attach)
Exclusions are assumed
Add-ons Workflow, Web Parts,
Server Controls
Determine per solution
Contact vendor
Determine per solution
Contact vendor
Changes to SharePoint Search
Unchanged
Custom content sources
Crawl rules
Upgraded but should be checked for conflicts
Custom crawl file types
Changed
32
Scopes are lost, must recreate
Only 1 index now, default in SharePoint Server
Docicon.xml modifications must be redone
Thesaurus/noise file modifications must be redone
Search schedule lost, must recreate
If using gradual upgrade both v2 and v3
index will be running Disable v2 indexer
ASAP to reduce strain on hardware
Other SharePoint Server-specific Issues
33
Portal alerts are lost during upgrade
(site alerts are retained)
Link listing: upgraded to a special links
list called listings
Content listing: upgraded to news article page
Buckets (“c12”) are moved to real URL
If conflict, number appended starting with zero
http://portal/c12/finance becomes http://portal/finance
(retains structure)
Areas are upgraded to publishing sites
After upgrade you can only create publishing sites
as subsite can be changed
http://msmvps.com/blogs/shane/archive/2007/02/08/mossafter-an-upgrade-you-can-only-create-publishing-subsites.aspx
Common Issues
Local administrator on server no longer has full
access to SharePoint
Can be re-granted
http://msmvps.com/blogs/shane/archive/2007/01/
21/become-administrator-of-the-entire-webapplication.aspx
New blocked file types
ASMX, REM, RESX, SOAP, ASHX
E-mail enabled document libraries don’t work.
Look at new feature “Incoming e-mail”
34
More Common Issues
Office Web Components not available in 2007
Discussion lists are changed
Multithreaded discussion upgraded to single thread
Site Directory now creates sites (sub-sites)
35
FrontPage Customizations
Important consideration: keep customizations
or move to 2007
Custom pages kept by default during upgrade
Be aware: customized pages do not match rest of
site
“Reset to Site Definition”
Returns page to layout in site definition
Option exists to reset all pages during Gradual
upgrade
Available in site settings or within SharePoint
Designer
36
Upgrade Effects on Ghosting
60\Template
12\Template
12\TEMPLATE\
SiteTemplates\STS\
default.aspx
2003
2007 Farm
Config
SQL Instance
37
60\TEMPLATE\1033\
STS\default.aspx
Content
Custom Web Parts
Most will work post-upgrade
Test in Windows SharePoint Services 2003
SP2 with ASP.NET 2.0
Must re-build custom parts if you used ASP.NET
1.1 “obfuscation” tools
Must re-deploy Web Parts if
Moving to a new server farm (Content DB
Migration)
Web Part in the \bin (Gradual Upgrade)
Deploying Web Parts
38
stsadm –o addwppack
Troubleshooting Tips
Prescan logs
%temp%
Prescan.log
Prescan Report and Summary
Log files
Upgrade and Server logs
Logs are in
\Program Files\Common Files\Microsoft Shared\
Web Server Extensions\12\Logs
Watch the Event Viewer
39
Partners Helping You Upgrade
CorasWorks Migrator
Re-ghost multiple sites at once
Migrate customizations and Web Parts
to sites post upgrade
Helps you add layouts, master pages,
Web Parts en masse
Metalogix
Has tools for migrating from SPS 2003, Traditional web sites, and file shares
AvePoint DocAve
Used to connect to 2003 and move content to 2007 without
dependencies on customizations. Quickly and easily move your lists and
libraries into a clean slate (out-of-box site definitions)
CodePlex SPMigration
http://www.codeplex.com/SPMigration/
40
Takeaways
Prepare, plan and test your customizations!
Become familiar with Prescan and upgrade
Consider customization policies in the new
platform, using features over site definitions
41
Orphaned Objects
Windows SharePoint Services
Content DB orphans
Post-SP2 Hotfix, KB 918743 and KB 918744
stsadm -o databaserepair -url http://WSSSite -databasename
DatabaseName
stsadm -o databaserepair -url http://WSSSite -databasename
DatabaseName –deletecorruption
SharePoint Server Config DB orphans
Post SP2 Hotfix, KB 918742
spsadm –o repairorphans http://PortalSite
Windows SharePoint Services Config DB orphans
Remove and then reattach the content
databases on the virtual server
42
Appendix
43
Effect of Upgrades:
Low Customization Site (Original)
44
Effect of Upgrades:
Low Customization Site (Upgraded)
45
Effect of Upgrades:
Low Customization Site (ReGhosted)
46
Effect of Upgrades:
High Customization Site (Original)
47
Effect of Upgrades:
High Customization Site (Upgraded)
48
Effect of Upgrades:
High Customization Site (ReGhosted)
49
Effect of Upgrades:
Themed Site (Original)
50
Effect of Upgrades:
Themed Site (Upgraded)
51
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/sharepointserver/bb421259.aspx
Upgrade Documentation
http://technet2.microsoft.com/Office/en-us/library/396c85d9-4b86-484e-9cc5-f6c4d725c5781033.mspx?mfr=true
Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide
http://www.microsoft.com/technet/solutionaccelerators/collaboration/default.mspx
Upgrade in WSS SDK
http://msdn2.microsoft.com/en-us/library/ms460185.aspx
Fix your Orphans HotFixes
repair content databases in Windows SharePoint Services http://support.microsoft.com/kb/918744
Spsadm.exe command line tool that you can use to clean up orphaned items in the configuration database in SharePoint
Portal Server 2003 http://support.microsoft.com/kb/918742
52
/
References
Supportability
2003 Best Practices to ensure upgradeability http://msdn2.microsoft.com/en-us/library/ms916859.aspx
KB Article on Site Definition Supportability in 2003 http://support.microsoft.com/Default.aspx?id=898631
Supported and unsupported scenarios for working with custom site definitions and custom area definitions in Windows
SharePoint Services and in SharePoint Portal Server 2003 http://support.microsoft.com/kb/898631/en-us
Community Tools
SharePoint Configuration Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyID=918f8c18-89dc4b47-82ca-34b393ea70e1&DisplayLang=en
SharePoint Utility http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724
SPReport http://workspaces.gotdotnet.com/spreports
Managing SharePoint Products and Technologies Performance at Microsoft
http://www.microsoft.com/technet/itshowcase/content/spsperfnote.mspx#ETKAE
Microsoft SQL Server Report Pack for Microsoft Office SharePoint Portal Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=49159368-544b-4b09-8eed-4844b4e33d3d&DisplayLang=en
Blogs
Resources and Recommendations for Upgrading Site Definitions and Site Templates
http://blogs.msdn.com/joelo/archive/2007/01/03/resources-and-recommendationsfor-upgrading-site-definitions-and-site-templates.aspx
Upgrade Content IT Pros may not have seen http://blogs.msdn.com/joelo/archive/2006/12/06/upgrade-content-it-prosmay-not-have-seen.aspx
Other Upgrade Topics from Joel’s Blog http://blogs.msdn.com/joelo/archive/tags/Upgrade/default.aspx
53
Reference
New Upgrade Paper for customizations
https://msmvps.com/blogs/shane/archive/2007/11
/11/a-new-upgrade-paper.aspx
54
Resources for IT Professionals
www.microsoft.com/teched
Tech·Talks
Live Simulcasts
Tech·Ed Bloggers
Virtual Labs
http://microsoft.com/technet
Evaluation licenses, pre-released
products, and MORE!
1 Year
Subscription!
Complete an
evaluation on
CommNet and
enter to win!
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should
not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
57