DEP340Moving to Windows SharePoint Services and Microsoft Office SharePoint Portal Server 2003 from Previous SharePoint Releases

Veli-Matti VanamoHewlett-Packard Company

Agenda

Upgrading SharePoint Team Services to Windows SharePoint Services

Upgrading SharePoint Portal Server 2001 to SharePoint Portal Server 2003

Migrating from web storage system to SQL based document libraries

Migrating Web Parts

Case Study – Hewlett-Packard

SharePoint InvestmentsSmart Connected Workspaces

Consistent rich experience – users, developers, and IT

Smart connections – people, teams, topics, divisions, etc.

Flexible deployment – bottoms-up, centralized, hybrid on large scale farms

IndividualIndividual

EnterprisEnterprisee

DivisionDivision

TeamTeam

SharePoint Investments

Team Collaboration Solution well beyond file server

Scalable Workspace Platform

SharePoint Services Collaboration Document

Collaboration Flexible Lists Web Part Pages Personalization Life Cycle

Management Scale-Up/Out

Foundation

Enterprise Portal Solution built on top of Windows SharePoint Services

Hub and Aggregator for SharePoint personal, team and portal sites

SharePoint Portal Server

News and Links Site Directory and

Connections Personal Sites Audience Targeting Index, Search and

Alerts Single Sign-On BizTalk Integration

ASP.NETASP.NET

SharePoint Services

Significant enhancements in collaboration, flexible lists, personalization

Much more scalable and highly available

Web Parts

Built on Windows Server 2003, SQL Server 2000 and ASP.NET

Moving from SharePoint Team Services

Utility for moving sites – smigrate.exe

Available from SharePoint Services CD, and download

Migrates all site content, security, etc…

Customizations must be reapplied

Can also be used to migrate sites between SharePoint Services servers

Upgrading from SharePoint Team Services - Export

Set the original site(s) to read only (optional)

Increase page file size to at least 1 GB

Increase IIS timeout to maximum

Run smigrate.exe

smigrate.exe –w <URL> -f <FILE>

Upgrading from SharePoint Team Services - Import

Increase IIS timeout to maximumTurn on anonymous access (optional)Ensure quota limit is large enoughTurn off blocked file typesIncrease max file sizeSet max number of alerts to be unlimitedRun smigrate.exe

smigrate.exe –r –w <URL> -f <FILE>

Moving from SharePoint Team Services Sites to Windows SharePoint Services

demodemo

SharePoint Portal Server 2003

Increased scalability, more flexible deploymentsPersonal sites, personalization, people as a discoverable resourceImproved search relevance and scalabilityEnterprise application integration and single sign onBuilt on SQL Server 2000, Windows Server 2003, and ASP.NET, and Windows SharePoint ServicesBackwards compatible support for web store based document libraries

Upgrading from SharePoint Portal Server 2001

In place upgradeRequires OS upgradeDocuments remain in web store, accessible from new portal

Maintain document versions, document profilesMaintain most PKMCDO applications

Categories and content sources migrated to new portalDigital dashboards no longer supported

Code migration required

Upgrading from SharePoint Portal Server 2001 - Process

Backup SharePoint Portal Server 2001Run upgrade.exe

Export categories, content sources and keywords

Upgrade OS to Windows Server 2003Install ASP.NET

Run upgrade.exeInstall SharePoint Portal Server 2003, upgrade web storage system

Import categories, keywords, content sources

SharePoint Portal Server upgraded experience

demodemo

Migrating between document libraries

Migration utility available at launch

Plan for functional differences between document libraries

Versioning

Approval

Security

Metadata

Prototype Import/Export toolDeveloped by HP and Microsoft

2 part process with Intermediate XML

Prototype Export Tools

Export Tool for SharePoint Portal Server 2001

Export TaxonomyExport Document ProfilesFolder Hierarchy, Security and Versions preservedContent Expert and System Administrator driven

Other Export Tools in development LiveLink 9.1Lotus QuickplaceExchange Public Folders

Prototype Import Tool

SharePoint Portal Server 2003 Import WizardUses Managed Object Model

Upfront configuration and customizationModify List Columns

Create Custom Views

Migrates Topic StructureApplies Security

Creates Custom List Templates

Creates Lists

Creates List Items

Uploads documents

Versions

System Administrator driven

SharePoint Portal Server upgraded experience

demodemo

Web Parts – Then and Now

SharePoint 2001

Script (VBScript, JScript)

Code exposed

Portable, code and all

Allow rogue code

Only worked in SPS, not STS

Code not signed

1 copy of code for each time web part deployed

SharePoint “v2.0”

.NET compiled assemblies

Code hidden

Portable, settings only

Only “Safe” controls allowed

Same parts run on both SPS and STS

Code must be signed

1 copy of code, central on server

Migrating Web Parts

Survey pre-built “v2.0” web partsGet to know the features/capabilities of them

Look for 3rd party part providers and Microsoft add-on parts

Survey the web parts you need to migrate

Can you simply replicate functionality from a 1.0 part to “v2.0”?

If no existing part exists, then port functionality from 1.0 web parts to 2.0 (Microsoft whitepaper with helpful tips)

Crib sheet for Web Part migration

If ContentType is HTML or XMLUse a similar function “v2” pre-built web part

If ContentType is VBScript or JscriptWrite a new “v2” web part class

Init() PreRender()

getContent() RenderWebPart()

XSL and XSLLink Try using the XML Web Part

Migrating Web Parts

demodemo

SharePoint at Hewlett Packard

Migration from SharePoint Team Services

Upgrade and migration from SharePoint Portal Server 2001

Benefits of the new environment

HP ServicesStrategy for Communities and Collaboration

HP Services has 65,000 IT professionals in 160 countries around the world

Three tier knowledge architectureTier 1 – Corporate

Tier 2 – Communities of Practice

Tier 3 – Project teams

SharePoint Products and Technologies as backbone

Cost effective solution

Customizable and extendable

Exploit existing Office and Windows Infrastructure deployment

HP Version 1 Implementation

Deployed 5 regional sites with 11 servers and 30,000 active users

SharePoint Team ServicesHP Branding

Self Service Creation

Over 3500 active sites

SharePoint Portal Server 2001HP Branding

Custom Web Parts and Applications

UBBThreads Discussions integration

Manufacturing ISO9000 certification

35 Communities in production

Requirements for Migration

SharePoint Team Services is now mission critical

Minimal downtime due to migrationMaintain Similar functionalityMaintain Similar look and feelLittle or no training required to use the new version

SharePoint Portal Server is critical part of the HP Services KM implementation

Minimal downtime due to migrationUse phased approach with early adoptersSupport Restructuring during migration processSupport Collapsing Workspaces into TopicsAllow standardised approach to communities with common metadata and templates

SharePoint Team Services Migration Approach

Check for Team Site URL collisionsRename STS spaces where necessary

Disable outbound networkExport with smigrate

20 - 100GB to move over WAN for collapsed regional serversSet Team Sites to Read OnlyEnable outbound network

Import with smigrateForward old Team Sites to new URL

Enumerate Team Sites and create Portal listings

SharePoint Portal Server 2001 Migration Approach

Assess current workspaces and web partsPlan for functional differences

Code new web parts

Design V2 Community TemplatesSimplify

Use new features

Export to Intermediate XML

Clean up list templates, fields

Import to SharePoint Portal Server 2003

Benefits of the New Environment

High availabilityGuaranteed SLA to business

Operational Cost SavingsData Centre Consolidation

Simplified ManagementSame Interface for My Site, Teams and Portals

Scale-out for further expansionSecure environmentEnd-user benefits

Personal SitesTemplatesOffice IntegrationMeeting WorkspacesDocument ManagementWeb PartsGranular Security

Conclusions

Upgrading to Windows SharePoint ServicesUtility for moving sites

Upgrading to SharePoint Portal Server 2003In place upgrade, documents remain in original document libraries

Migrating to SQL based Libraries requires planning due to functional differences

Assess and Plan Web Part MigrationsMicrosoft whitepaper available

Significantly more flexibility for deployments

Ask The ExpertsGet Your Questions Answered

10:30 – 14:00

Community Resources

Evaluate Windows SharePoint Services and SharePoint Portal Server 2003 Betas http://www.microsoft.com/sharepoint

Download technical documentation and Software Development Kits from our Developer Center http://msdn.microsoft.com

Find and contribute Web Parts and templates to the Web Component Directory  http://www.microsoft.com/sharepoint/webparts

Visit our community websites http://www.microsoft.com/sharepoint/community/

evaluationsevaluations

© 2003 Microsoft Corporation. All rights reserved.© 2003 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.