DEP340 Moving to Windows SharePoint Services and Microsoft Office SharePoint Portal Server 2003 from Previous SharePoint Releases Veli-Matti Vanamo Hewlett-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 Investments Smart 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 Individual Enterprise Division Team

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.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 -f

Upgrading from SharePoint Team Services - Import Increase IIS timeout to maximum Turn on anonymous access (optional) Ensure quota limit is large enough Turn off blocked file types Increase max file size Set max number of alerts to be unlimited Run smigrate.exe smigrate.exe –r –w -f

Moving from SharePoint Team Services Sites to Windows SharePoint Services demo demo

SharePoint Portal Server 2003 Increased scalability, more flexible deployments Personal sites, personalization, people as a discoverable resource Improved search relevance and scalability Enterprise application integration and single sign on Built on SQL Server 2000, Windows Server 2003, and ASP.NET, and Windows SharePoint Services Backwards compatible support for web store based document libraries

Upgrading from SharePoint Portal Server 2001 In place upgrade Requires OS upgrade Documents remain in web store, accessible from new portal Maintain document versions, document profiles Maintain most PKMCDO applications Categories and content sources migrated to new portal Digital dashboards no longer supported Code migration required

Upgrading from SharePoint Portal Server Process Backup SharePoint Portal Server 2001 Run upgrade.exe Export categories, content sources and keywords Upgrade OS to Windows Server 2003 Install ASP.NET Run upgrade.exe Install SharePoint Portal Server 2003, upgrade web storage system Import categories, keywords, content sources

SharePoint Portal Server upgraded experience demo demo

Migrating between document libraries Migration utility available at launch Plan for functional differences between document libraries Versioning Approval Security Metadata Prototype Import/Export tool Developed by HP and Microsoft 2 part process with Intermediate XML

Prototype Export Tools Export Tool for SharePoint Portal Server 2001 Export Taxonomy Export Document Profiles Folder Hierarchy, Security and Versions preserved Content Expert and System Administrator driven Other Export Tools in development LiveLink 9.1 Lotus Quickplace Exchange Public Folders

Prototype Import Tool SharePoint Portal Server 2003 Import Wizard Uses Managed Object Model Upfront configuration and customization Modify List Columns Create Custom Views Migrates Topic Structure Applies Security Creates Custom List Templates Creates Lists Creates List Items Uploads documents Versions System Administrator driven

SharePoint Portal Server upgraded experience demo demo

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 parts Get 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 XML Use a similar function “v2” pre-built web part If ContentType is VBScript or Jscript Write a new “v2” web part class Init()  PreRender() getContent()  RenderWebPart() XSL and XSLLink  Try using the XML Web Part

Migrating Web Parts demo demo

SharePoint at Hewlett Packard Migration from SharePoint Team Services Upgrade and migration from SharePoint Portal Server 2001 Benefits of the new environment

HP Services Strategy for Communities and Collaboration HP Services has 65,000 IT professionals in 160 countries around the world Three tier knowledge architecture Tier 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 Services HP Branding Self Service Creation Over 3500 active sites SharePoint Portal Server 2001 HP 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 migration Maintain Similar functionality Maintain Similar look and feel Little 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 migration Use phased approach with early adopters Support Restructuring during migration process Support Collapsing Workspaces into Topics Allow standardised approach to communities with common metadata and templates

SharePoint Team Services Migration Approach Check for Team Site URL collisions Rename STS spaces where necessary Disable outbound network Export with smigrate GB to move over WAN for collapsed regional servers Set Team Sites to Read Only Enable outbound network Import with smigrate Forward old Team Sites to new URL Enumerate Team Sites and create Portal listings

SharePoint Portal Server 2001 Migration Approach Assess current workspaces and web parts Plan for functional differences Code new web parts Design V2 Community Templates Simplify Use new features Export to Intermediate XML Clean up list templates, fields Import to SharePoint Portal Server 2003

Benefits of the New Environment High availability Guaranteed SLA to business Operational Cost Savings Data Centre Consolidation Simplified Management Same Interface for My Site, Teams and Portals Scale-out for further expansion Secure environment End-user benefits Personal Sites Templates Office Integration Meeting Workspaces Document Management Web Parts Granular Security

Conclusions Upgrading to Windows SharePoint Services Utility for moving sites Upgrading to SharePoint Portal Server 2003 In place upgrade, documents remain in original document libraries Migrating to SQL based Libraries requires planning due to functional differences Assess and Plan Web Part Migrations Microsoft whitepaper available Significantly more flexibility for deployments

Ask The Experts Get Your Questions Answered 10:30 – 14:00

Community Resources Evaluate Windows SharePoint Services and SharePoint Portal Server 2003 Betas Download technical documentation and Software Development Kits from our Developer Center Find and contribute Web Parts and templates to the Web Component Directory Visit our community websites

evaluations evaluations

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