OFC333 Windows SharePoint Services and Microsoft Office SharePoint Portal Server: Upgrade and Migration Bill English MVP Mindsharp

OFC333OFC333Windows SharePoint Windows SharePoint Services and Microsoft Services and Microsoft Office SharePoint Portal Office SharePoint Portal Server: Upgrade and Server: Upgrade and MigrationMigration

OFC333OFC333Windows SharePoint Windows SharePoint Services and Microsoft Services and Microsoft Office SharePoint Portal Office SharePoint Portal Server: Upgrade and Server: Upgrade and MigrationMigrationBill EnglishBill EnglishMVPMVPMindsharpMindsharp

Session ObjectivesSession Objectives

Explain the upgrade alternatives Explain the upgrade alternatives Understand the options & advantages Understand the options & advantages

Understand options for handling customizationsUnderstand options for handling customizations

Impact of special configurationsImpact of special configurations

Show what’s needed to plan an upgrade Show what’s needed to plan an upgrade Pre-upgrade tasksPre-upgrade tasks

Executing the upgradeExecuting the upgrade

Design goalsDesign goals

Before upgradeBefore upgrade

Upgrade approachesUpgrade approaches

Additional considerationsAdditional considerations

Summary of alternatives and trade-offsSummary of alternatives and trade-offs

TopicsTopics

In-place upgradeIn-place upgradeGradual upgradeGradual upgradeContent DB migrationContent DB migration

Microsoft Office SharePoint Portal Server 2007Microsoft Office SharePoint Portal Server 2007Shared servicesShared servicesPost upgradePost upgrade

Microsoft Microsoft Windows Windows

SharePoint SharePoint Services v2Services v2

SharePoint PortalSharePoint PortalServer 2003Server 2003

ContentContentManagementManagementServer 2002Server 2002

CMS/SPS/WSS RoadmapCMS/SPS/WSS Roadmap

Microsoft Office Microsoft Office 20072007

SharePoint ServersSharePoint Servers

Microsoft Microsoft Windows Windows

SharePointSharePointServices ‘v3’Services ‘v3’

Design GoalsDesign Goals

Provide clean Microsoft Office SharePoint Portal Server 2003 Provide clean Microsoft Office SharePoint Portal Server 2003 (SPS) to Microsoft Office SharePoint Server 2007 (MOSS) (SPS) to Microsoft Office SharePoint Server 2007 (MOSS) upgradeupgrade

No upgrade plans for SharePoint 2001 – MOSS releaseNo upgrade plans for SharePoint 2001 – MOSS release

Minimize user impactMinimize user impactReduce outage duration Reduce outage duration

Limit number of users impacted for any outageLimit number of users impacted for any outage

Support customizations to SPSSupport customizations to SPSCustom site definitions & web partsCustom site definitions & web parts

Pages customized using Microsoft Office FrontPagePages customized using Microsoft Office FrontPage

Provide resource use choices to adminsProvide resource use choices to adminsEnable upgrading existing farmEnable upgrading existing farm

Support migrating to new farmSupport migrating to new farm

Provide single clear set of UI optionsProvide single clear set of UI optionsBoth GUI and command lineBoth GUI and command line

Consistent approach for both productsConsistent approach for both products






TopicsTopics



Understand Upgrade OptionsUnderstand Upgrade Options

In-place upgrade In-place upgrade Updates existing databases and servers Updates existing databases and servers

Easiest approach, environment offline while it runsEasiest approach, environment offline while it runs

Gradual upgrade: upgrade site collectionsGradual upgrade: upgrade site collectionsGranular control: one to many site collections at a timeGranular control: one to many site collections at a time

Run old and new versions side-by-side; rollback to SPS Run old and new versions side-by-side; rollback to SPS supportedsupported

More complex and resource intensiveMore complex and resource intensive

Content DB migration: upgrade into Content DB migration: upgrade into separate farmseparate farm

Attach SPS content database to MOSS farm and upgrade Attach SPS content database to MOSS farm and upgrade runsruns

SPS stays available and untouched by upgradeSPS stays available and untouched by upgrade

Content only, requires new farm, has many manual stepsContent only, requires new farm, has many manual steps

Before Upgrade to MOSS Before Upgrade to MOSS

Upgrade farm to Office SharePoint SP2 – Upgrade farm to Office SharePoint SP2 – requiredrequired

Install pre-requisitesInstall pre-requisitesWindows Workflow Foundation latest versionWindows Workflow Foundation latest version

ASP.Net 2.0 ASP.Net 2.0

TIP: Test custom web parts with ASP.Net 2.0 in TIP: Test custom web parts with ASP.Net 2.0 in WSS SP2WSS SP2

Before Upgrade (cont’d)Before Upgrade (cont’d)

Run & test a full backupRun & test a full backup

Run the Pre-upgrade scan toolRun the Pre-upgrade scan toolReports common issues you must addressReports common issues you must address

Lists all site definitions in useLists all site definitions in use

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

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

Before Upgrade: Before Upgrade: Handling FrontPage customizationsHandling FrontPage customizations

Important consideration: keep Important consideration: keep customizations or move to MOSScustomizations or move to MOSS

Custom pages kept by default during upgradeCustom pages kept by default during upgradeSPS themes are not preservedSPS themes are not preserved

Be aware: customized pages do not match rest Be aware: customized pages do not match rest of siteof site

““Reset to Site Definition” Reset to Site Definition” Returns page to layout in site definition Returns page to layout in site definition

Option exists to reset all pages during upgrade Option exists to reset all pages during upgrade Gets users to clean MOSS environment soonerGets users to clean MOSS environment sooner

Available in site settings or within SharePoint Available in site settings or within SharePoint DesignerDesigner

Works for any page edited in SharePoint Designer or Works for any page edited in SharePoint Designer or FrontPageFrontPage

Maintaining Customizations Maintaining Customizations ExampleExample

Pre-upgradePre-upgrade

UpgradedUpgraded

Does not match rest of Does not match rest of sitesite

Lacks new features: Lacks new features: NavigationNavigationSite actions menuSite actions menuSecurity trimmed Security trimmed UIUIRecycle binRecycle binEtc…Etc…

Maintaining Customizations Maintaining Customizations ExampleExample

Before Upgrade: Before Upgrade: Custom site definitionsCustom site definitions

Existing sites based on custom SPS site Existing sites based on custom SPS site definitions should work in MOSSdefinitions should work in MOSS

MOSS site definition needed to create new MOSS site definition needed to create new sites sites

Upgrade your custom site definitionsUpgrade your custom site definitionsCreate new MOSS site definitionCreate new MOSS site definition

Craft upgrade mapping – SPS to MOSS site Craft upgrade mapping – SPS to MOSS site definitiondefinition

Deploy mapping file & MOSS site definition Deploy mapping file & MOSS site definition to MOSS install directory, and run upgradeto MOSS install directory, and run upgrade

Can be done post-upgrade using command line Can be done post-upgrade using command line

Before Upgrade:Before Upgrade:Custom Web PartsCustom Web Parts

Most will work post-upgradeMost will work post-upgrade

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

Must re-deploy web parts if:Must re-deploy web parts if:Moving to a new server farm (content DB Moving to a new server farm (content DB migration)migration)

Web part in the Bin & not upgrading in-placeWeb part in the Bin & not upgrading in-place

Before Upgrade: Before Upgrade: Shared services overviewShared services overview

Choose an upgrade strategyChoose an upgrade strategyUpgrade master, then each child – Upgrade master, then each child – Recommended; offers most flexibilityRecommended; offers most flexibility

Build temporary master, upgrade children – Build temporary master, upgrade children – Useful where customers want to upgrade Useful where customers want to upgrade smaller sites firstsmaller sites first

Choose an upgrade methodChoose an upgrade methodIn-place – Upgrade all components at onceIn-place – Upgrade all components at once

Gradual/Content DB MigrationGradual/Content DB MigrationSPS master continues to provide services to SPS sitesSPS master continues to provide services to SPS sites

SPS sites retain user experienceSPS sites retain user experience

User profile, audience data pushed from MOSS->SPS by scheduled User profile, audience data pushed from MOSS->SPS by scheduled jobjobTwo search crawls active (SPS, MOSS)Two search crawls active (SPS, MOSS)Maximize efficiency by removing SPS sites from SPS crawl after they are Maximize efficiency by removing SPS sites from SPS crawl after they are upgradedupgraded






TopicsTopics

In-Place upgradeIn-Place upgradeGradual upgradeGradual upgradeContent DB migrationContent DB migration


Available Upgrade MethodsAvailable Upgrade Methods

In-place upgrade In-place upgrade Updates existing databases and servers Updates existing databases and servers

Easiest approach, environment offline while it runsEasiest approach, environment offline while it runs

Best for small or single-server environmentsBest for small or single-server environments

Gradual upgrade: Upgrade site collections

Granular control: one to many site collections at a time

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

More complex & resource intensive

Best where there are many sites, & must limit downtime

Content DB migration: Upgrade into separate farm

Attach SPS content db to MOSS farm & upgrade runs

SPS stays available and untouched by upgrade

Content only, requires new farm, has many manual steps

Best if moving to new hardware

Run setup, choose Run setup, choose upgrade in-placeupgrade in-place

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

SPS no longer available SPS no longer available after upgradeafter upgrade

In-Place UpgradeIn-Place Upgrade

SPS ConfigDB

MOSS Config DBs

Web ServerWeb Server

SPS Web AppSPS Web App


Web ServerMOSS Web App

MOSS Web App

SPS Search + User Profiles

MOSS SSPDBs

SPS Content DB(s)

MOSSContent DB(s)

Search + User

Profiles

Search + User

Profiles

All items upgradedAll items upgraded

IIS sitesIIS sites

Local dataLocal data

Config & content databasesConfig & content databases

In-Place Upgrade Steps In-Place Upgrade Steps

Follow pre-upgrade stepsFollow pre-upgrade stepsRun setup and choose upgradeRun setup and choose upgrade

Install language packs if neededInstall language packs if needed

Upgrade one web serverUpgrade one web serverReview log files & resolve any issuesReview log files & resolve any issues

Issues should be rare, upgrade docs will have Issues should be rare, upgrade docs will have recommended workarounds for common issuesrecommended workarounds for common issues

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

After completion on first server, repeat After completion on first server, repeat setup & upgrade on each server in the setup & upgrade on each server in the farmfarmReview resultsReview resultsReset pages to (MOSS) site definition Reset pages to (MOSS) site definition versionsversions


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 collectionsGradual upgrade: upgrade site collectionsGranular control: one to many site collections at a timeGranular control: one to many site collections at a timeRun old & new versions side-by-side; can roll back to SPSRun old & new versions side-by-side; can roll back to SPSMore complex than in-placeMore complex than in-placeRequires extra SQL storage, has perf impact on SPSRequires extra SQL storage, has perf impact on SPSBest where there are many sites, & must limit downtimeBest where there are many sites, & must limit downtime

Content DB migration: upgrade into separate farmAttach SPS content db to MOSS farm & upgrade runsSPS stays available and untouched by upgradeContent only, requires new farm, has many manual stepsBest if moving to new hardware

SPS ConfigDB

SPS Content DB(s)

MOSS ConfigDBs

MOSS Content DB(s)

Web Web Server(s)Server(s)SPS Web AppSPS Web App MOSS Web MOSS Web

AppApp Portal sitePortal site Team Team sitessites MySitesMySites

Portal sitePortal site Team Team sitessites MySitesMySites

SPS Search/User Profile

DB(s)MOSS SSP

DB(s)

Gradual UpgradeGradual UpgradeBuild MOSS farm on current HWBuild MOSS farm on current HWCheck disk, memory availability – Check disk, memory availability – this is resource intensivethis is resource intensiveRun Setup, choose Gradual Upgrade Run Setup, choose Gradual Upgrade on each web serveron each web serverFor SPS, run setup & upgrade For SPS, run setup & upgrade on Job then Search server(s)on Job then Search server(s)

Create temporary URL domainsCreate temporary URL domains

For each Web ApplicationFor each Web Application

Creates matching content db Creates matching content db for each SPS content dbfor each SPS content db

Create new MOSS web appCreate new MOSS web app

Existing v-server moved to new Existing v-server moved to new domain, domain, & site redirects created& site redirects createdManually re-deploy Web parts in BinManually re-deploy Web parts in Bin

Upgrade batches of site Upgrade batches of site collectionscollections

Must upgrade root site firstMust upgrade root site first

Upgrade 1 to N sites thereafterUpgrade 1 to N sites thereafter

Command line availableCommand line available

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

Gradual UpgradeGradual UpgradeURL redirectsURL redirects

After upgradeAfter upgrade

MOSS at //domainMOSS at //domain

Redirects not Redirects not needed once needed once upgrade upgrade completes & completes & results are results are validatedvalidated

Upgrade moves SPS virtual server to new URL domainUpgrade moves SPS virtual server to new URL domain

Redirect is created for all sites to new SPS locationRedirect is created for all sites to new SPS location

As site is upgraded, redirect is droppedAs site is upgraded, redirect is dropped

Browse access to original URL always worksBrowse access to original URL always works

New URL domain is needed until upgrade is completeNew URL domain is needed until upgrade is complete

During upgradeDuring upgrade

SPS at SPS at //domain_old//domain_oldMOSS at //domainMOSS at //domainRequests for Requests for //domain/sites/WS//domain/sites/WSSSredirected to redirected to //domain_old/sites/wss //domain_old/sites/wss until it is upgradeduntil it is upgraded

Pre-upgradePre-upgrade

SPS at //domainSPS at //domain

Create //domain_old Create //domain_old URLURL

Key site at Key site at //domain/sites/WS//domain/sites/WSSS

Gradual Upgrade Steps:Gradual Upgrade Steps:Create MOSS InfrastructureCreate MOSS Infrastructure

On existing hardwareOn existing hardware

Run standard pre-upgrade stepsRun standard pre-upgrade steps

Prepare secondary domain for each web Prepare secondary domain for each web appapp

Run setup, choose Gradual Upgrade on 1 Run setup, choose Gradual Upgrade on 1 Web ServerWeb Server

Creates MOSS Central Admin site, Config DB Creates MOSS Central Admin site, Config DB

Performs local-server upgrade actionsPerforms local-server upgrade actions

Run setup & gradual on all other farm Run setup & gradual on all other farm serversservers

Upgrades all sever-local dataUpgrades all sever-local data

Review log filesReview log files

Gradual Upgrade Steps:Gradual Upgrade Steps:Upgrade SPS “virtual server”Upgrade SPS “virtual server”

Provide domain SPS will use during Provide domain SPS will use during upgradeupgrade

Recommendation: automatically create Recommendation: automatically create databasesdatabases

May be manually configured if necessaryMay be manually configured if necessary

Need one MOSS content db for each SPS content db, plus Need one MOSS content db for each SPS content db, plus one temporary db per SQL serverone temporary db per SQL server

Need extra 30-50% additional SQL disk spaceNeed extra 30-50% additional SQL disk space

Redirect created for all sites at this timeRedirect created for all sites at this timeSPS IIS site reconfigured to use new domain or portSPS IIS site reconfigured to use new domain or port

MOSS web application created using the original domainMOSS web application created using the original domain

Choose SSP for web applicationChoose SSP for web application

Re-deploy any web parts located in the SPS Re-deploy any web parts located in the SPS binbin

Gradual Upgrade Steps:Gradual Upgrade Steps:Upgrade contentUpgrade content

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

2.2. Select first group of sites to upgradeSelect first group of sites to upgradeMust include the root site of the domain in first groupMust include the root site of the domain in first group

Note storage (number of MB) to be upgradedNote storage (number of MB) to be upgraded

3.3. During upgrade, redirect to WSS v2 URL is During upgrade, redirect to WSS v2 URL is removed removed

WSS v3 site is now live WSS v3 site is now live

Automatic - no admin action neededAutomatic - no admin action needed

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

5.5. Repeat steps 1-3 for all sitesRepeat steps 1-3 for all sites

6.6. Command line available to automateCommand line available to automate

Gradual Upgrade Steps: Gradual Upgrade Steps: Revert to SPSRevert to SPS

When upgrade result is undesirable, “revert” When upgrade result is undesirable, “revert” deletes MOSS and resets redirect to SPSdeletes MOSS and resets redirect to SPSConfirm SPS site still exists before reverting to itConfirm SPS site still exists before reverting to it

Make copy of MOSS using stsadm Export / Make copy of MOSS using stsadm Export / Import commandsImport commands

Revert to SPS via UI or command lineRevert to SPS via UI or command lineUI: Select Sites for Upgrade > Revert SiteUI: Select Sites for Upgrade > Revert Site

Command line: stsadm –o upgrade -revertCommand line: stsadm –o upgrade -revert

Fix copy of MOSS using SharePoint DesignerFix copy of MOSS using SharePoint DesignerOnce complete, re-upgrade originalOnce complete, re-upgrade original

Use SharePoint Designer to merge changes from Use SharePoint Designer to merge changes from “fixed” & re-upgraded versions“fixed” & re-upgraded versions

Gradual Upgrade Steps:Gradual Upgrade Steps:Shared ServicesShared Services

Shared Services configurationShared Services configurationFor each master portalFor each master portal

Configure search in MOSSConfigure search in MOSS

Configure profile/audience sync in MOSSConfigure profile/audience sync in MOSS

Review Managed Properties of user profiles in MOSSReview Managed Properties of user profiles in MOSS

For each child portalFor each child portalModify start addresses in SPS master portal to prevent Modify start addresses in SPS master portal to prevent

double-crawlingdouble-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 collections

Granular control: one to many site collections at a time

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

More complex & resource intensive

Best where there are many sites, & must limit downtime

Content DB migration: upgrade into separate farmContent DB migration: upgrade into separate farmAttach SPS content db to MOSS farm & upgrade runsAttach SPS content db to MOSS farm & upgrade runs

SPS stays available and untouched by upgradeSPS stays available and untouched by upgrade

Content only, requires new farm, has many manual stepsContent only, requires new farm, has many manual steps

Best if moving to new hardwareBest if moving to new hardware

Create new MOSS farmCreate new MOSS farm

Initialize MOSS web Initialize MOSS web applicationsapplications

MOSSConfig DBs

Web ServerWeb Server



Web ServerMOSS Web App

MOSS Web App

MOSS SSPDBs

MOSSContent DB(s)

Search + User

Profiles

Search + User

Profiles

Manually copy Manually copy customizationscustomizations

Custom templatesCustom templates

All custom web parts All custom web parts (BIN & GAC)(BIN & GAC)

Content Database MigrationContent Database Migration

Content DB Migration Content DB Migration Shared ServicesShared Services

SPS not affectedSPS not affectedMaster continues to provide services to SPS Master continues to provide services to SPS sitessites

Child sites retain user experienceChild sites retain user experience

User profile, audience data NOT pushed User profile, audience data NOT pushed from MOSS to SPS by scheduled job from MOSS to SPS by scheduled job

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

Content DB Migration Steps Content DB Migration Steps

Perform standard pre-upgrade steps Perform standard pre-upgrade steps

Create new MOSS farm on clean hardwareCreate new MOSS farm on clean hardwareConfigure SSPConfigure SSP

Create a new web application for each SPS Create a new web application for each SPS virtual servervirtual server

Manually re-apply configuration settingsManually re-apply configuration settingsEnsure all inclusions re-created in MOSS Ensure all inclusions re-created in MOSS (required)(required)

Deploy all custom site definitionsDeploy all custom site definitions

Deploy custom web parts to GAC or BINDeploy custom web parts to GAC or BIN

Set e-mail server, special permissionsSet e-mail server, special permissions

Re-create quota templatesRe-create quota templates

Content DB Migration Steps Content DB Migration Steps (cont’d)(cont’d)

Back up SPS content database using SQLBack up SPS content database using SQL

Restore backup to copy in MOSS farmRestore backup to copy in MOSS farm

Add content db to web application via GUI or Add content db to web application via GUI or command linecommand line

Ensure root site is included in first databaseEnsure root site is included in first database

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

Command line is stsadm –o addcontentdbCommand line is stsadm –o addcontentdb

Upgrade triggers automatically, runs until it Upgrade triggers automatically, runs until it completescompletes

For large databases, command line preferableFor large databases, command line preferable

Review log files for any issuesReview log files for any issues

Repeat for all content and search/user profile Repeat for all content and search/user profile databasesdatabases

Content DB Migration Steps Content DB Migration Steps Other considerationsOther considerations

Set SPS content DBs to read-onlySet SPS content DBs to read-onlyAvoids manual merging of updates post-upgradeAvoids manual merging of updates post-upgrade

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

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

Work-intensive – redirects all added manuallyWork-intensive – redirects all added manually

Re-applying inclusions, custom web parts Re-applying inclusions, custom web parts & custom site definitions are critical& custom site definitions are critical

Entirely manual process for moving themEntirely manual process for moving them

Whitepaper planned to detail the processWhitepaper planned to detail the process

Inclusions (e.g. /teams, /mysites) commonly missedInclusions (e.g. /teams, /mysites) commonly missed






TopicsTopics



Additional SPS Considerations:Additional SPS Considerations:Site structureSite structure

AreasAreasAreas are upgraded to regular sub-sitesAreas are upgraded to regular sub-sites

All areas under a given portal must be All areas under a given portal must be upgraded upgraded at once at once

URLsURLsPortal URLs change after upgradePortal URLs change after upgrade

In MOSS URLs follow the logical navigation structure – In MOSS URLs follow the logical navigation structure – navigation changes are now reflected in the URLnavigation changes are now reflected in the URL

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

Redirects: links through Internet Explorer will be Redirects: links through Internet Explorer will be redirected; Office Client apps will notredirected; Office Client apps will not

Additional SPS Considerations:Additional SPS Considerations:Site contentSite content

ListingsListingsListings in SPS: “Portal Listings” list + Listings Listings in SPS: “Portal Listings” list + Listings web partweb part

Listings in MOSS: “Links” list items + Content Listings in MOSS: “Links” list items + Content By Query web partBy Query web part

Consider creating MOSS summary links from Consider creating MOSS summary links from upgraded listings to leverage new page upgraded listings to leverage new page featuresfeatures

Create new summary link control/web partCreate new summary link control/web part

Manually copy over listing content and orderManually copy over listing content and order

PagesPagesArea homepages (e.g. default.aspx) are Area homepages (e.g. default.aspx) are upgraded to the new page template modelupgraded to the new page template model

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

Additional SPS Considerations: Additional SPS Considerations: Site applicationsSite applications

NewsNewsNews listings are upgraded to Links list items and pagesNews listings are upgraded to Links list items and pages

List items/pages are rolled up Content by Query Web PartList items/pages are rolled up Content by Query Web Part

Site directorySite directorySite is upgraded to new UI Site is upgraded to new UI

Sites List schema changes Sites List schema changes New columns added to Sites List for categoriesNew columns added to Sites List for categories

Single sign-on (SSO)Single sign-on (SSO)No schema changes for MOSSNo schema changes for MOSS

Gradual: configure MOSS to point to SPS SSO dbGradual: configure MOSS to point to SPS SSO db

Content DB Migration: backup, restore SPS SSO db to Content DB Migration: backup, restore SPS SSO db to MOSS farmMOSS farm

Additional Considerations for Additional Considerations for SPS Search and AlertsSPS Search and Alerts

SearchSearchIndexes not upgraded – full crawl of all content Indexes not upgraded – full crawl of all content required after upgraderequired after upgrade

All content sources default to a single index All content sources default to a single index (MOSS has one index per SSP)(MOSS has one index per SSP)

Duplicate start addresses in content sources will be Duplicate start addresses in content sources will be ignoredignored

Conflicting crawl rules between SPS indexes will Conflicting crawl rules between SPS indexes will be ignored (if item included in any index, it will be ignored (if item included in any index, it will be preserved)be preserved)

Search scopes, scope groups not upgradedSearch scopes, scope groups not upgraded

SPS AlertsSPS AlertsSPS alerts preserved but not automatically SPS alerts preserved but not automatically upgradedupgraded

Additional Considerations Additional Considerations for MySitesfor MySites

All upgrade approachesAll upgrade approachesMy Sites are upgraded to MOSS look and feel, My Sites are upgraded to MOSS look and feel, new features (Colleagues, Memberships, Blogs)new features (Colleagues, Memberships, Blogs)

Consider moving My Site to its own web Consider moving My Site to its own web application which uses the application which uses the MySiteMySite host host templatetemplate

Gradual Upgrade-specificGradual Upgrade-specificUntil user’s personal site is upgraded, entire Until user’s personal site is upgraded, entire MySite experience remains SPSMySite experience remains SPS

Once SPS Shared Services are upgraded, Once SPS Shared Services are upgraded, changes to SPS profile will not be copied to changes to SPS profile will not be copied to upgraded MOSS SSPupgraded MOSS SSP

Additional Considerations for Additional Considerations for SPS with Shared ServicesSPS with Shared Services

SearchSearchTwo crawls runningTwo crawls running

Recommend manually modifying SPS/O12 start addresses to Recommend manually modifying SPS/O12 start addresses to prevent double-crawlingprevent double-crawling

Keywords, site-level scopes only available for upgraded Keywords, site-level scopes only available for upgraded MOSS sitesMOSS sites

User profiles/AudiencesUser profiles/AudiencesGradual upgrade: Changes in MOSS pushed down to SPS Gradual upgrade: Changes in MOSS pushed down to SPS - does not include new properties and audience rules- does not include new properties and audience rules

Review Managed Properties list for people search scopeReview Managed Properties list for people search scope

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

Post-Upgrade ConsiderationsPost-Upgrade Considerations

Delete un-needed SPS sites Delete un-needed SPS sites Needed for Gradual Upgrade & Content DB Needed for Gradual Upgrade & Content DB MigrationMigration

Finalize upgrade Finalize upgrade Required stepRequired step

Removes temporary data maintained about SPS Removes temporary data maintained about SPS environmentenvironment

Post-upgrade data migrationPost-upgrade data migration

Un-install SPSUn-install SPS

Common Upgrade ChallengesCommon Upgrade Challenges

Pre-scan cannot update locked or over-Pre-scan cannot update locked or over-quota sites or database orphansquota sites or database orphans

Impact of redirectsImpact of redirectsFull URLsFull URLs

Office client applicationsOffice client applications

Gradual upgrade hardware & disk Gradual upgrade hardware & disk requirementsrequirements

Database sizesDatabase sizes

Application pools & accountsApplication pools & accountsSPS and MOSS central admin account should be the sameSPS and MOSS central admin account should be the same

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

Avoiding content updates during upgradeAvoiding content updates during upgrade

Common SPS CustomizationsCommon SPS Customizations

CSS filesCSS files_layouts files_layouts filesGraphicsGraphicsSite definitions Site definitions Themes (SPS site def’n won’t render Themes (SPS site def’n won’t render without it)without it)Web parts (bin and GAC)Web parts (bin and GAC)Web.config and safe controls listWeb.config and safe controls listNon-SharePoint ElementsNon-SharePoint Elements

NT ServicesNT ServicesWeb servicesWeb servicesIIS VserversIIS VserversCustom DLLsCustom DLLs






TopicsTopics



Upgrade Upgrade ApproacApproac

hhIn-Place:In-Place: GradualGradual DB MigrationDB Migration

PROsPROs SimpleSimple

Upgrade smaller Upgrade smaller sets of data at a sets of data at a time time

SPS & MOSS stay SPS & MOSS stay livelive

Can revert to Can revert to original original

Uses existing HWUses existing HW

Upgrade & move Upgrade & move to new farm to new farm

SPS is a separate SPS is a separate farm, not affectedfarm, not affected

CONsCONs

Entire farm Entire farm offline during offline during upgradeupgrade

No revert No revert abilityability

Hardware Hardware intensive: memory intensive: memory & SQL storage& SQL storage

Redirects for SPS Redirects for SPS URLs during URLs during upgradeupgrade

Many complex Many complex manual steps manual steps required, higher required, higher risk of errorrisk of error

Requires new Requires new farm, double the farm, double the SQL storageSQL storage

Summary and Trade-offsSummary and Trade-offs

URLs, Farms and Admin EffortURLs, Farms and Admin Effort

In PlaceIn Place

GradualGradual

DB MigrationDB Migration

Same FarmSame Farm

Least Admin EffortLeast Admin Effort

Same FarmSame Farm

Moderate Admin EffortModerate Admin Effort

New FarmNew Farm

Extensive Admin EffortExtensive Admin Effort

Same URLSame URL

New URL’sNew URL’s

New URL’sNew URL’s

Try upgradeTry upgrade

Avoid known issuesAvoid known issues

When you send feedbackWhen you send feedback

Call to ActionCall to Action

Gradual, in-place, db attachGradual, in-place, db attach

Avoid upgrading on DCsAvoid upgrading on DCs

Look for ‘upgrade’ in READMELook for ‘upgrade’ in README

SPS gradual upgrade, multi-server farmSPS gradual upgrade, multi-server farm

Need log files from <WSS install dir>\logsNeed log files from <WSS install dir>\logs

Screen images of errorsScreen images of errors

Portal Server UpgradePortal Server UpgradePortal Server UpgradePortal Server Upgrade

ResourcesResourcesTechnical Chats and Webcastshttp://www.microsoft.com/communities/chats/default.mspx http://www.microsoft.com/usa/webcasts/default.asp

Microsoft Learning and Certificationhttp://www.microsoft.com/learning/default.mspx

MSDN & TechNet http://microsoft.com/msdnhttp://microsoft.com/technet

Virtual Labshttp://www.microsoft.com/technet/traincert/virtuallab/rms.mspx

Newsgroupshttp://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx

Technical Community Siteshttp://www.microsoft.com/communities/default.mspx

User Groupshttp://www.microsoft.com/communities/usergroups/default.mspx

http://www.microsoft.com/communities/chats/default.mspx

http://www.microsoft.com/communities/chats/default.mspx

http://www.microsoft.com/usa/webcasts/default.asp

http://www.microsoft.com/usa/webcasts/default.asp

http://www.microsoft.com/learning/default.mspx

http://www.microsoft.com/learning/default.mspx

http://microsoft.com/msdn

http://microsoft.com/msdn

http://microsoft.com/technet

http://microsoft.com/technet

http://www.microsoft.com/technet/traincert/virtuallab/rms.mspx

http://www.microsoft.com/technet/traincert/virtuallab/rms.mspx

http://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx



http://www.microsoft.com/communities/default.mspx

http://www.microsoft.com/communities/default.mspx

http://www.microsoft.com/communities/usergroups/default.mspx

http://www.microsoft.com/communities/usergroups/default.mspx

Fill out a session Fill out a session evaluation on evaluation on CommNet for CommNet for

a chance toa chance toWin an XBOX Win an XBOX

360!360!

© 2006 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.

Documents

OFC333 Windows SharePoint Services and Microsoft Office SharePoint Portal Server: Upgrade and Migration Bill English MVP Mindsharp