Share PowerPoint. Anywhere!

Unisys Migrating to MOSS

Uploaded from authorPOINT Lite
Download as Download Not Available PPT
Presentation Description

No description available

Like authorSTREAM?


You can vote once a day till December
10th, Vote Now!
Views: 74
Like it  ( Likes) Dislike it  ( Dislikes)
Added: February 20, 2008 This presentation is Public
Presentation Category :Education
Presentation StatisticsNew!
Views on authorSTREAM: 72 | Views from Embeds: 2
Presentation Transcript

MOSS 2007 Migration : 20/02/2008 Page 1 MOSS Upgrade MOSS 2007 Migration Terry Yarnall Manager, Desktop Solutions, Global Infrastructure BETT


Agenda : 20/02/2008 Page 2 MOSS Upgrade Agenda


Unisys – Company Profile : Unisys – Company Profile 20/02/2008 MOSS Upgrade Page 3 Headquarters: Blue Bell, PA Employees: ~30,000 Partners: Cisco, Dell, EMC, IBM, Intel, Microsoft, NEC, Oracle and SAP We combine expertise in Consulting Systems integration Outsourcing Infrastructure Server technology We serve five primary vertical markets worldwide Financial services Public Sector Communications Transportation Commercial


SharePoint History : SharePoint History 20/02/2008 MOSS Upgrade Page 4


SharePoint History : SharePoint History 20/02/2008 MOSS Upgrade Page 5 2001: Evaluated SharePoint v1 and SharePoint Team Services No integration between the two products SPSv1 was not scalable SPSv1 used the web storage system (EDB) 2002: Beta evaluation of Office 2003 including SharePoint v2 and WSS 2003: Developed production architecture and Knowledge Network design 2004: Went live on SharePoint 2003 in January 2006: Office 2007 TAP program. MOSS Project kickoff 2007: Early Search implementation. Gradual migration underway


SharePoint 2003 : SharePoint 2003 20/02/2008 MOSS Upgrade Page 6 Centrally Managed Environment 14 portals Parent portal with Shared Services enabled (Unet) One large general purpose portal with communities (Knet) Business Unit portals Design goal: minimize the number of managed portals ~9,500 MySites 1.2 TB of data


Architecture : Architecture Web Front-Ends 4x Dual Core HT 2.8Ghz processors 16GB Memory Windows Server 2003 Enterprise, SP1 Load balanced through a Cisco Content Switch Indexing Servers V2 – 4x 2Ghz processors 3.5 GB Memory used for Excel Services after migration V3 – 4x Dual Core HT 2.8Ghz, 16GB memory Windows Server 2003 Enterprise, SP1 Database Back-End SQL 2005 Cluster (Active/Active) 16-Way 1.5Ghz , 16GB Memory each node Windows 2003 DCE, SP1 Clariion SAN Storage 20/02/2008 Page 7 MOSS Upgrade


Slide8 : Docs/tasks/calendars, blogs, wikis, e-mail integration, project management “lite”, Outlook integration, offline docs/lists Enterprise Portal template, Site Directory, My Sites, social networking, privacy control Enterprise scalability, contextual relevance, rich people and business data search Rich and Web forms based front-ends, LOB actions, pluggable SSO Server-based Excel spreadsheets and data visualization, Report Center, BI Web Parts, KPIs/Dashboards Integrated document management, records management, and Web content management with policies and workflow Business Forms Search Content Management Platform Services Workspaces, Mgmt, Security, Storage, Topology, Site Model SharePoint Feature Areas 20/02/2008 Page 8 MOSS Upgrade


Migration Strategy : Migration Strategy 20/02/2008 MOSS Upgrade Page 9


Scope of Migration Project : Scope of Migration Project 20/02/2008 Page 10 MOSS Upgrade


Project Approach : Project Approach Establish baseline familiarity with the product – IT Lab Determine, recommend, and build architecture Use QA as primary proving ground for Production Implement and deploy 2007 search early to replace SPS 2003 search Test and hone “gradual upgrade” process through repeated trials Migrate portals to MOSS using gradual upgrade process, running 2003 and 2007 in parallel Decommission 2003 Migrate Extranet environment 20/02/2008 MOSS Upgrade Page 11


Key Challenges : Key Challenges Early search deployment Use redirected MOSS 2007 search in SPS 2003 Effective and efficient migration processes SPS broken links; unghosted pages; minimize redesign Many customized Areas and Sites Minimize portal/site collection unavailability User education 20/02/2008 Page 12 MOSS Upgrade


Key Challenges : Key Challenges Mapping customizations is very time consuming Early on there was a lack of good documentation – getting better! Availability of knowledgeable resources at MS to answer questions Also getting better!! Requires a lot of testing and practice runs 20/02/2008 Page 13 MOSS Upgrade


Slide14 : 20/02/2008 MOSS Upgrade Page 14


Work Streams : Work Streams 20/02/2008 MOSS Upgrade Page 15


Slide16 : 20/02/2008 Page 16 MOSS Upgrade


Initial Pre-scan Results : Initial Pre-scan Results 20/02/2008 Page 17 MOSS Upgrade Prescan takes 2.5 hours to run


Early Search Implementation : Early Search Implementation 20/02/2008 MOSS Upgrade Page 18


Slide19 : New Search Options Web – MOSS Desktop - Windows Desktop Search Vista & XP Intranet Search – MOSS Internet point of presence search - MOSS Search in the Enterprise Solutions 20/02/2008 Page 19 MOSS Upgrade


Why implement Search early? : Why implement Search early? 20/02/2008 MOSS Upgrade Page 20


Slide21 : Key new features make the crawls faster (fresher content) Continuous propagation Crawl log viewer Item level details – view by host name, content source, dates, and messages Ability to pre-test crawl rules Change log crawl / Security-only crawl Ability to remove single item from index Maximum scale is 10’s of Millions of documents per indexer New Features For Managing Crawls 20/02/2008 Page 21 MOSS Upgrade


Things to consider : Things to consider 20/02/2008 MOSS Upgrade Page 22


Slide23 : Search as a Shared Service 20/02/2008 Page 23 MOSS Upgrade


Slide24 : Content Sources 20/02/2008 Page 24 MOSS Upgrade


Slide25 : Relevancy Improvements 20/02/2008 Page 25 MOSS Upgrade


Slide26 : Know your environment Use dedicated web front ends for crawling large farms/sites Define Crawler Impact Rules to avoid site overload Schedule for off-hours crawling where appropriate Consider using single content access account per region SharePoint 2007 requires full read permissions Non-Farm admin account otherwise the crawl may include not published documents Pause indexes if you need to temporarily halt crawling – stopping an index starts a full update Configuration Best Practices 20/02/2008 Page 26 MOSS Upgrade


Slide27 : Query Reporting 20/02/2008 Page 27 MOSS Upgrade


Thesaurus : Thesaurus 20/02/2008 MOSS Upgrade Page 28


Preparing for Migration : Preparing for Migration 20/02/2008 MOSS Upgrade Page 29


Clean-up Campaign : Clean-up Campaign 20/02/2008 MOSS Upgrade Page 30 Before each portal is migrated Remove old sites Verify site owner Remove users no longer with the company Clean-up document libraries If versioning is enabled, limit the number of Saved versions Remove web parts that are hidden and not being used Review subsites - remove any that are not being used Clean-up old alerts. Alerts are not migrated; however, v2 indexer still generates alerts. Can use Outlook 2007 to manage alerts


Selecting a Migration Option : Selecting a Migration Option 20/02/2008 MOSS Upgrade Page 31


In-Place Migration : In-Place Migration 20/02/2008 MOSS Upgrade Page 32 New SSP is created. Parent becomes the SSP MySite collection is created under the parent Converts existing databases The new SSP becomes the default and is set as the parent


In-Place Migration : In-Place Migration 20/02/2008 MOSS Upgrade Page 33 Uses the existing IIS sites Converts SPS 2003 databases


Gradual Upgrade : Gradual Upgrade 20/02/2008 MOSS Upgrade Page 34 New SSP is created. Parent becomes the SSP MySite collection is created under the parent Creates two new Side-by-Side databases The new SSP becomes the default and is set as the parent


Gradual Upgrade : Gradual Upgrade 20/02/2008 MOSS Upgrade Page 35 Only one SSP is required Need to remove SSP1 Remove MySite and SSP1 sites _Pair site and database are for MOSS


What happens when you upgrade : What happens when you upgrade 20/02/2008 MOSS Upgrade Page 36 When you select “Begin upgrade” a new MOSS site and database are created with a _Pair extension After selecting “Continue Upgrade” you must select the site collections to migrate. You can also select whether to “reset the template pages” during the upgrade to remove customizations. Content in MOSS uses the original URL. Requests for content that has not been migrated is redirected to the SPS 2003 portal automatically After the upgrade you also have the option to Revert back to the original content.


What happens when you upgrade : What happens when you upgrade 20/02/2008 MOSS Upgrade Page 37


Problems Encountered : Problems Encountered 20/02/2008 MOSS Upgrade Page 38


Configuration Considerations : Configuration Considerations 20/02/2008 MOSS Upgrade Page 39


Windows SharePoint Services Search : Windows SharePoint Services Search 20/02/2008 MOSS Upgrade Page 40 Same service Only need one per farm Searches MOSS help files


Problems you may encounter : Problems you may encounter 20/02/2008 MOSS Upgrade Page 41


Problems you may encounter : Problems you may encounter 20/02/2008 MOSS Upgrade Page 42


Problems you may encounter : Problems you may encounter 20/02/2008 MOSS Upgrade Page 43


Creating a new MySite Collection : Creating a new MySite Collection 20/02/2008 MOSS Upgrade Page 44 Select the My Site Host template Problem: it has to be at the root so the Mysite references in SPS 2003 work properly


Gradual Upgrade – MySite Problems : Gradual Upgrade – MySite Problems 20/02/2008 MOSS Upgrade Page 45 Workaround Plan since the SSP was not created Use the existing SSP Create a MySite collection in the parent web app Remove the existing MySites web app Import the AD profiles Migrate the personal sites


Creating a new MySite Collection : Creating a new MySite Collection 20/02/2008 MOSS Upgrade Page 46


Profile Import in SSP : Profile Import in SSP 20/02/2008 MOSS Upgrade Page 47


Problems you may encounter : Problems you may encounter 20/02/2008 MOSS Upgrade Page 48


Office Web Components : Office Web Components 20/02/2008 MOSS Upgrade Page 49


Other Problems : Other Problems 20/02/2008 MOSS Upgrade Page 50


Final Thoughts : Final Thoughts 20/02/2008 MOSS Upgrade Page 51


Finalize Upgrade : Finalize Upgrade 20/02/2008 MOSS Upgrade Page 52 Very dangerous command For a long migration you may want to consider renaming or replacing FinalizeUpgrade.aspx Path => C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\ADMIN


SharePoint Licensing – Standard CAL : SharePoint Licensing – Standard CAL 20/02/2008 MOSS Upgrade Page 53 SharePoint 2003 is equivalent to MOSS Standard


SharePoint Licensing – Enterprise CAL : SharePoint Licensing – Enterprise CAL 20/02/2008 MOSS Upgrade Page 54 To get Enterprise features you must purchase Enterprise CAL’s


Released Hotfixes May 17 – May 21 : Released Hotfixes May 17 – May 21 20/02/2008 MOSS Upgrade Page 55


Released Hotfixes May 17 – May 21 : Released Hotfixes May 17 – May 21 20/02/2008 MOSS Upgrade Page 56


Q&A : 20/02/2008 Page 57 MOSS Upgrade Q&A