upgrade and migration from windows sharepoint services v2 and sharepoint portal server 2003 allan...

Upgrade And Migration From Upgrade And Migration From Windows Sharepoint Services V2 Windows Sharepoint Services V2 And Sharepoint Portal Server And Sharepoint Portal Server 20032003

Allan SchweighardtSr. Technology SpecialistMicrosoft Corporation

Session ObjectivesSession Objectives

Explain the upgrade alternatives Understand the options & advantages Understand options for handling customizationsImpact of special configurations

Show what’s needed to plan an upgrade

Pre-upgrade tasksExecuting the upgrade

TopicsTopics

Design goalsBefore Upgrade Upgrade Approaches

In-Place Upgrade

Gradual Upgrade

Content DB Migration

Additional Considerations:SharePoint Portal Server

Shared Services

Post Upgrade

Summary of Alternatives and Trade-offs

CMS/SPS/WSS RoadmapCMS/SPS/WSS Roadmap

Content ManagementServer 2002

Office SharePoint Server 2007

Windows SharePointServices “v3’

SharePoint PortalServer 2003

Windows SharePointServices v2

Design GoalsDesign GoalsProvide clean v2/2003 to v3/2007 upgrade

No upgrade plans for v1 – v3/2007 release

Minimize user impactReduce outage duration Limit number of users impacted for any outage

Support customizations to v2/2003Custom site definitions & web partsPages customized using FrontPage

Provide resource use choices to adminsEnable upgrading existing farmSupport migrating to new farm

Provide single clear set of UI optionsBoth GUI and command lineConsistent approach for both products

TopicsTopics


In-Place Upgrade

Gradual Upgrade



Shared Services

Post Upgrade


Understand Upgrade Understand Upgrade OptionsOptions

In-Place Upgrade Updates existing databases and servers

Easiest approach, environment offline while it runs

Gradual Upgrade: Upgrade Site CollectionsGranular control: one to many site collections at a time

Run old & new versions side-by-side; rollback to v2/2003 supported

More complex & resource intensive

Content DB Migration: Upgrade Into Separate Farm

Attach v2/2003 content db to v3/2007 farm & upgrade runs

V2/2003 stays available and untouched by upgrade

Content only, requires new farm, has many manual steps

Before Upgrade To V3/ Before Upgrade To V3/ 20072007

Upgrade farm to SharePoint SP2 – required

Install pre-requisitesWindows Workflow Foundation(dotnetfx3.exe)ASP.Net 2.0 TIP: Test custom web parts with ASP.Net 2.0 in WSS SP2

Before UpgradeBefore Upgrade

Run & test a full backupRun the Pre-Upgrade Scan Tool

Reports common issues you must address

Lists all site definitions in use

Updates WSS lists so they can be upgradedPre-requisite for upgrade, requires SP2

Scan tool is installed with product, and will be available as a download

Coordinate with your customers Tip: Review WSS 2.0 to WSS 3.0 or SPS v2 to Office 2007 upgrade documentation

Before UpgradeBefore UpgradeHandling FrontPage CustomizationsHandling FrontPage Customizations

Important consideration: keep customizations or move to v3/2007

Custom pages kept by default during upgradev2/2003 Themes are not preserved

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 upgrade Gets users to clean v3/2007 environment sooner

Available in site settings or within SharePoint Designer

Works for any page edited in SharePoint Designer / FP

Maintaining Customizations Maintaining Customizations ExampleExample

UpgradedUpgraded

Pre-upgradePre-upgrade

Maintaining Customizations Maintaining Customizations ExampleExample

Does not match rest of Does not match rest of sitesiteLacks new features: Lacks new features:

NavigationNavigationSite actions menuSite actions menuSecurity trimmed UISecurity trimmed UIRecycle binRecycle binEtc…Etc…

Before UpgradeBefore Upgrade Custom Site DefinitionsCustom Site Definitions

Existing sites based on custom v2/2003 site definitions should work in v3/2007V3/2007 site definition needed to create new sites Upgrade your custom site definitions

Create new v3/2007 site definitionCraft upgrade mapping – v2/2003 to v3/2007 site definition

Deploy mapping file & v3/2007 site definition to v3/2007 install directory, and run upgrade

Can be done post-upgrade using command line

Before UpgradeBefore UpgradeCustom Web PartsCustom Web Parts

Most will work post-upgrade

Must re-build custom parts if you used ASP.Net 1.1 “obfuscation” tools

Must re-deploy web parts ifMoving to a new server farm (content DB migration)Web part in the Bin & not upgrading in-place

Before Upgrade Before Upgrade Shared Services OverviewShared Services Overview

Choose an upgrade strategyUpgrade master, then each child

Recommended; offers most flexibility

Build temporary master, upgrade childrenUseful where customers want to upgrade smaller sites first

Choose an upgrade methodIn-place

Upgrade all components at once

Gradual/Content DB MigrationV2/2003 master continues to provide services to v2 sitesV2 sites retain user experienceUser profile, audience data pushed from v3->v2 by scheduled jobTwo search crawls active (v2, v3)

Maximize efficiency by removing v2 sites from v2 crawl after they are upgraded

TopicsTopics


In-Place Upgrade

Gradual Upgrade



Shared Services

Post Upgrade


Available Upgrade Available Upgrade MethodsMethods

In-Place Upgrade Updates existing databases and servers Easiest approach, environment offline while it runsBest for small or single-server environments

Gradual Upgrade: Upgrade Site CollectionsGranular control: one to many site collections at a timeRun old & new versions side-by-side; rollback to v2 supportedMore complex & resource intensiveBest where there are many sites, & must limit downtime


Attach v2 content db to v3 farm & upgrade runsV2 stays available and untouched by upgradeContent only, requires new farm, has many manual stepsBest if moving to new hardware

In-Place UpgradeIn-Place Upgrade

V2 ConfigDB

V2 Content DB(s)

Run Setup, Choose Run Setup, Choose Upgrade In-PlaceUpgrade In-Place

All items upgraded: All items upgraded:

IIS sites, IIS sites,

local data, local data,

config & content config & content databasesdatabases

V3 ConfigDBs

V3 Content DB(s)

Repeat Setup & upgrade Repeat Setup & upgrade on each server in farmon each server in farm

V2 no longer available V2 no longer available after upgradeafter upgrade

Web Server

V2 Web App

V2 Web App

Web Server

V3 Web App

V3 Web App

Search + User Profiles

Search + User Profiles

V2 Search + User Profiles

V3 SSPDBs

In-Place Upgrade Steps In-Place Upgrade Steps

Follow pre-upgrade steps

Run setup and choose upgradeInstall language packs if needed

Upgrade one web server

Review log files & resolve any issuesIssues should be rare, upgrade docs will have recommended workarounds for common issues

Logs in: program files\common files\microsoft shared\web server extensions\12\logs

After completion on first server, repeat setup & upgrade on each server in the farm

Review results

Reset pages to (v3/2007) site definition versions


In-Place Upgrade Updates existing databases and servers Easiest approach, environment offline while it runsBest for small or single-server environments

Gradual Upgrade: Upgrade Site CollectionsGranular control: one to many site collections at a timeRun old & new versions side-by-side; can roll back to v2/2003More complex than in-placeRequires extra SQL storage, has perf impact on v2/2003Best where there are many sites, & must limit downtime

Content DB Migration: Upgrade Into Separate FarmAttach v2 content db to v3 farm & upgrade runsV2 stays available and untouched by upgradeContent only, requires new farm, has many manual stepsBest if moving to new hardware

Gradual UpgradeGradual UpgradeBuild v3/2007 farm on

current HWCheck disk, memory availability – this is resource intensive Run Setup, choose Gradual Upgrade on each web serverFor SPS, run setup & upgrade on Job then Search server(s)Create temporary URL domains

V2 Config

DB

V2 Content DB(s)

V3 Config

DBs

V3 Content DB(s)

Search & Job Server(s)Search & Job Server(s)

Web Server(s)Web Server(s)

V2 Web AppV2 Web App V3 Web AppV3 Web App

For each Web ApplicationCreate new v3/2007 web appCreates matching content db for each v2/2003 content dbExisting v-server moved to new domain, & site redirects created Manually re-deploy Web parts in Bin

Portal sitePortal site Team sitesTeam sites MySitesMySites

Portal sitePortal site Team sitesTeam sites MySitesMySites

Upgrade batches of site collectionsMust upgrade root site firstUpgrade 1 to N sites thereafterCommand line available

V2 Search/User

Profile DB(s)

V3 SSP DB(s)

Gradual UpgradeGradual UpgradeURL RedirectsURL Redirects

Upgrade moves V2/2003 virtual server to new URL domain v3/2007 takes over original URL domain

Redirect is created for all sites to new v2/2003 locationAs site is upgraded, redirect is droppedBrowse access to original URL always worksNew URL domain is needed until upgrade is complete

Pre-upgrade During upgrade After upgradeV2 at //domainCreate //domain_old URL domainKey site at //domain/sites/WSS

V2 at //domain_oldV3 at //domain

Requests for //domain/sites/WSSredirected to //domain_old/sites/wss until it is upgraded

V3 at //domain

Redirects not needed once upgrade completes and results are validated

Gradual Upgrade StepsGradual Upgrade StepsCreate v3/2007 InfrastructureCreate v3/2007 Infrastructure

On existing hardwareRun standard pre-upgrade stepsPrepare secondary domain for each web appRun setup, choose Gradual Upgrade on 1 Web Server

Creates v3 Central Admin site, Config DB

Performs local-server upgrade actions

Run setup & gradual on all other farm servers

Upgrades all sever-local data

Review log files

Gradual Upgrade StepsGradual Upgrade StepsUpgrade v2/2003 “virtual server”Upgrade v2/2003 “virtual server”

Provide domain v2/2003 will use during upgrade

Recommendation: Automatically create databases

May be manually configured if necessary

Need one v3/2007 content db for each v2/2003 content db, plus one temporary db per SQL server.

Need extra 30-50% additional SQL disk space

Redirect created for all sites at this timeV2/2003 IIS site reconfigured to use new domain or port

V3/2007 web application created using the original domain

Choose SSP for web application

Re-deploy any web parts located in the v2/2003 bin

Gradual Upgrade StepsGradual Upgrade StepsUpgrade ContentUpgrade Content

1. Choose if resetting files to template versionCan change selection with each group of sites upgraded

2. Select first group of sites to upgradeMust include the root site of the domain in first groupNote storage (number of MB) to be upgraded

3. During upgrade, redirect to v2/2003 URL is removed

V3/O2 site is now live Automatic - no admin action needed

4. Review log files after each upgrade groupTip: Upgrade duration is in logs. Number of MB / duration is good approximation for subsequent upgrade durations

5. Repeat steps 1-3 for all sites6. Command line available to automate

Gradual Upgrade StepsGradual Upgrade StepsRevert to v2Revert to v2

When upgrade result is undesirable, “revert” deletes v3& resets redirect to v2Confirm v2 site still exists before reverting to itMake copy of v3 using stsadm Export / Import commandsRevert to v2 via UI or command line

UI: Select Sites for Upgrade > Revert SiteCommand line: stsadm –o upgrade –revertAdditional considerations for Portal/MySites

Fix copy of v3 using SharePoint DesignerOnce complete, re-upgrade originalUse SharePoint designer to merge changes from “fixed”& re-upgraded versions

Gradual Upgrade StepsGradual Upgrade StepsShared ServicesShared Services

Shared Services configurationFor each master portal

Configure search in v3/2007

Configure profile/audience sync in v3/2007

Review Managed Properties of user profiles in v3/2007

For each child portalModify start addresses in v2/2003 master portal to prevent double-crawling


In-Place Upgrade Updates existing databases and servers

Easiest approach, environment offline while it runs

Best for small or single-server environments

Gradual Upgrade: Upgrade Site CollectionsGranular control: one to many site collections at a time

Run old & new versions side-by-side; rollback to v2 supported

More complex & resource intensive

Best where there are many sites, & must limit downtime


Attach v2 content db to v3 farm & upgrade runs

V2 stays available and untouched by upgrade

Content only, requires new farm, has many manual steps

Best if moving to new hardware

Content Database Content Database MigrationMigration

Create new V3 farm

Initialize v3 web applications

Manually copy customizations

Attach databases

Web ServerWeb Server

V2 Web AppV2 Web App


Web ServerWeb Server



Search + Job Search + Job Server(s)Server(s)

Application Application Server(s)Server(s)

V2 Config

DB

V2 Content DB(s)

V3 Config

DBs

V3 Content DB(s)

V2 Search + User Profiles

V3 SSPDBs

Content DB Migration Content DB Migration Shared ServicesShared Services

V2/2003 not affectedMaster continues to provide services to v2 sitesChild sites retain user experienceUser profile/audience data not synced between v2, v3Two profiles, two MySites, etc may confuse Applications

Most search data not upgradedRe-create search settings other than custom search properties

Content DB Migration Content DB Migration Steps Steps

Perform standard pre-upgrade steps Create new v3/2007 farm on clean hardware

Configure farm-level settings

Create a new web application for each v2/2003 virtual server

Manually re-apply customizationsDeploy all custom site definitions

Deploy custom web parts to GAC or BIN

Content DB Migration Content DB Migration StepsSteps

Back up v2/2003 content database using SQL

Restore backup to copy in v3 farm

Add content db to web application via GUI or command line

Ensure root site is included in first database

UI: Application Management > Manage Content Databases > Add Content Database

Command line is 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 content and search/user profile databases

Content DB Migration Content DB Migration Steps Steps Other ConsiderationsOther Considerations

Set v2/2003 content DBs to read-onlyAvoids manual merging of updates post-upgrade

Note: Users will see warnings when DB is read-only

Internally used ISA Server to re-map URLsAs content db upgraded, remapped URLs to v3 farm

Work-intensive – redirects all added manually

TopicsTopics

Design goals

Before Upgrade

Upgrade ApproachesIn-Place Upgrade

Gradual Upgrade


Additional ConsiderationsSharePoint Portal Server

Shared Services

Post Upgrade

Known Issues


Additional Considerations Additional Considerations For SPS Site StructureFor SPS Site Structure

AreasAreas are upgraded to regular sub-sites

All areas under a given portal must be upgradedat once

Portal URLs change after upgradeIn V3/2007 URLs follow the logical navigation structure – navigation changes are now reflected in the URL

E.g. http://sample_site/c16/marketing changes to http://sample_site/teams/marketing

Redirects: links through IE will be redirected; Office Client apps will not

Additional Considerations Additional Considerations For SPS Site ContentFor SPS Site Content

ListingsListings in v2: “Portal Listings” list + Listings web part

Listings in v3: “Links” list items + Content Query web part

Recommend creating v3 summary links from upgraded listingsto leverage new page features

Create new Summary Link control/web partManually copy over listing content and order

PagesArea homepages (e.g. default.aspx) are upgraded to the newpage template model

By default, all pages will use the installed page template after upgrade

Additional Considerations Additional Considerations For SPS Site Applications For SPS Site Applications And SSOAnd SSO

News“Link” listings become Redirect Pages

“Content” listings become Pages

Both are rolled up by Content Query Web Part

Site DirectorySites List schema changes

New columns added to Sites List for categories

Single Sign-On (SSO)No schema changes for v3

Gradual: configure v3 to point to v2 SSO db

Content DB Migration: copy, restore v2 SSO db to v3 farm

Additional Considerations Additional Considerations For SPS Search And AlertsFor SPS Search And Alerts

SearchIndexes not upgraded – full crawl of all content required after upgradeAll content sources default to a single index (v3/2007 has one index per SSP)

Duplicate start addresses in content sources will be ignored

Conflicting crawl rules between v2/2003 indexes willbe ignored (if item included in any index, it will be preserved)Search scopes, scope groups not upgraded

SPS AlertsV2 alerts preserved but not automatically upgraded

Additional Considerations For Additional Considerations For MySitesMySites

All Upgrade ApproachesMy Sites are upgraded to v3/2007 look and feel,new features (Colleagues, Memberships, Blogs)

Consider moving My Site to its own web application which uses the MySite host template

URL simplicity; one place for my personal data (http://my)

B/R, performance; dedicated content DBs

Gradual Upgrade-specificUntil user’s personal site is upgraded, entire MySite experience remains v2

Once v2 Shared Services are upgraded, changesto v2 profile will not be copied to upgraded v3 SSP

Additional Considerations Additional Considerations For SPS With Shared For SPS With Shared ServicesServices

Recommend Gradual Upgrade or Content DB Migration

SearchTwo crawls running

Recommend manually modifying v2/2007 start addresses to prevent double-crawling

Keywords, site-level scopes only available for upgraded v3/2007 sites

User Profiles/AudiencesGradual upgrade: Changes in v3/2007 pushed down to v2/2003 – does not include new properties and audience rules

Review Managed Properties list for people search scope

Review upgraded audiences – consider deleting those builton DLs/SGs as those groups can be used directly

Post-Upgrade Post-Upgrade ConsiderationsConsiderations

Delete un-needed v2/2003 sites Needed for Gradual Upgrade & Content DB Migration

Finalize Upgrade Required step for Gradual, In-PlaceRemoves temporary data maintained about v2/2003 environment

Post-upgrade data migration

Un-install v2/2003

Common Upgrade Common Upgrade ChallengesChallenges

Pre-scan cannot update locked or over-quota sites or database orphansImpact of redirects

Office client applications

Gradual upgrade hardware & disk requirementsDatabase sizesApplication pools & accounts

V2 and v3 central admin account should be the same

Create new v3 app pools: ASP.Net 1.1 & 2.0 conflict

Avoiding content updates during upgrade

Common v2 Common v2 CustomizationsCustomizations

Look for these elements when considering content db migration approach

CSS files_layouts filesGraphicsSite definitions Themes (required for custom v2 site definitions)Web parts (bin and GAC)Web.config and safe controls listNon-Sharepoint Elements

NT ServicesWeb servicesIIS VserversCustom DLLs

TopicsTopics


In-Place Upgrade

Gradual Upgrade



Shared Services

Post Upgrade


Summary And TradeoffsSummary And Tradeoffs

Upgrade Approach In-Place Gradual DB Migration

PROs Simple Upgrade smaller batches of dataV2 and V3 stay liveCan revert to original Uses existing HW

Upgrade and move to new farm V2/2003 is a separate farm, not affected

CONs Entire farm offline during upgradeNo revert ability

Hardware intensive: memory and SQL storageRedirects for v2/2003 URLs during upgrade

Many complex manual steps required, higher risk of errorRequires new farm, double the SQL storage

Call To ActionCall To Action

Try upgrade Gradual, in-place, db attachAvoid upgrading on DCs

Avoid known issuesLook for ‘upgrade’ in READMESPS gradual upgrade, multi-server farm

When you send feedbackNeed log files from <WSS install dir>\logsScreen images of errors

upgrade and migration from windows sharepoint services v2 and sharepoint portal server 2003 allan...

Documents

upgrade upgrade approaches

upgrade farm

upgrade alternatives

upgrade options

upgrade preupgrade tasks

upgrade plans

preupgrade slide

v32007 farm upgrade