1 / 57

MOSS 2007 Migration

MOSS 2007 Migration. Terry Yarnall Manager, Desktop Solutions, Global Infrastructure BETT. Agenda. Unisys Profile SharePoint History Migration Strategy Early Search Implementation Preparing for Migration Problems Encountered Final Thoughts Q&A. Unisys – Company Profile.

Faraday
Télécharger la présentation

MOSS 2007 Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MOSS 2007 Migration Terry Yarnall Manager, Desktop Solutions, Global Infrastructure BETT MOSS Upgrade

  2. Agenda • Unisys Profile • SharePoint History • Migration Strategy • Early Search Implementation • Preparing for Migration • Problems Encountered • Final Thoughts • Q&A MOSS Upgrade

  3. Unisys – Company Profile • 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 MOSS Upgrade

  4. SharePoint History MOSS Upgrade

  5. SharePoint History • 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 MOSS Upgrade

  6. SharePoint 2003 • 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 MOSS Upgrade

  7. Architecture Web Front-Ends 4x Dual Core HT 2.8Ghz processors16GB MemoryWindows Server 2003 Enterprise, SP1Load balanced through a Cisco Content SwitchIndexing Servers V2 – 4x 2Ghz processors 3.5 GB Memory used for Excel Services after migrationV3 – 4x Dual Core HT 2.8Ghz, 16GB memoryWindows 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 MOSS Upgrade

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

  9. Migration Strategy MOSS Upgrade

  10. Scope of Migration Project MOSS Upgrade

  11. 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 MOSS Upgrade

  12. 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 MOSS Upgrade

  13. 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 MOSS Upgrade

  14. Project Organization MOSS Upgrade

  15. Work Streams MOSS Upgrade

  16. PIP Process Plan the Project Requirements and Approach Definition Design and Approach Validation Platform construction & validation Early Search Configured Early Search Deployment … 2003 Platform Decommissioning MOSS Upgrade

  17. Initial Pre-scan Results Prescan takes 2.5 hours to run MOSS Upgrade

  18. Early Search Implementation MOSS Upgrade

  19. Search in the Enterprise Solutions • New Search Options • Web – MOSS • Desktop - Windows Desktop Search Vista & XP • Intranet Search – MOSS • Internet point of presence search - MOSS MOSS Upgrade

  20. Why implement Search early? • Consistent Search Experience • Improved Relevance *** • Hit highlighting • Duplicate and near-duplicate collapsing • Improved Best Bets • Automatic generation of “Do you mean…” • Enhanced query syntax • Ability to subscribe to a search query • Reusable Search web parts • Improved Index management MOSS Upgrade

  21. New Features For Managing Crawls • 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 MOSS Upgrade

  22. Things to consider • One Index server may not be enough • Still need to use the v2 indexer to receive alerts • Need to redirect SPS2003 search to use MOSS search • Need updated ifilters for MOSS • Scheduling crawls is more challenging – double indexing • May create other migration challenges MOSS Upgrade

  23. Search as a Shared Service • A Shared Service Provider (SSP) is a grouping of shared services and related shared resources. • An SSP is created and configured to host shared services by a farm administrator so the services are available to multiple portal sites within a farm. • The farm administrator then assigns an SSP to a portal site. • A farm can contain multiple SSP’s, but a portal site can only be associated with one SSP. • An SSP can only have one instance of a particular shared service. MOSS Upgrade

  24. Content Sources • A content source is a collection of start addresses representing content that should be crawled by the search index component. • Enterprise Search provides several types of content sources by default: • SharePoint content • Web content • File share content • Exchange folder content • Business data content • Lotus Notes - Lotus Notes protocol handler is not installed by default MOSS Upgrade

  25. Relevancy Improvements • Dramatically improved relevance is the top goal of this release • New ingredients added, including • Click Distance • Anchor Text • URL Depth • Missing Metadata Creation • Result is noticeably improved relevant search results • 100% better on all queries • 500% better on common queries MOSS Upgrade

  26. Configuration Best Practices • 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 MOSS Upgrade

  27. Query Reporting MOSS Upgrade

  28. Thesaurus • Unisys did not use the thesaurus in v2 • Search results improve by using: synonyms, replacements, weighting • Once you understand the rules the thesaurus is straightforward • Thesaurus XML files will error in your browser (when the comments are removed) • The Rules: • Never touch the tsschema.xml file !! • Update the U.S. English file (tsenu.xml) and the neutral file (tsneu.xml) • Be sure to save the XML files with the encoding type of UNICODE. Use Notepad • Syntax is critical in XML • Watch out for special characters especially “hyphens” • Create batch files to copy the thesaurus files to their destination • The files reside in a number of directories in the 12 hive. Update them all!! • Cycle the “Office SharePoint Server Search” service after updating the files • Check the application log for errors MOSS Upgrade

  29. Preparing for Migration MOSS Upgrade

  30. Clean-up Campaign • 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 MOSS Upgrade

  31. Selecting a Migration Option • Migration Options • In-Place Upgrade (small environments) • Small farm • Farm is offline during upgrade • Simple process • Use existing hardware • Gradual Upgrade • MOSS installed on same servers • Granular control over the migration • Can revert back to SPS 2003 • Content Database Migration • Most complex – many manual steps • Requires a new farm MOSS Upgrade

  32. In-Place Migration • 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 MOSS Upgrade

  33. In-Place Migration Uses the existing IIS sites Converts SPS 2003 databases MOSS Upgrade

  34. Gradual Upgrade • 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 MOSS Upgrade

  35. Gradual Upgrade • Only one SSP is required • Need to remove SSP1 • Remove MySite and SSP1 sites • _Pair site and database are for MOSS MOSS Upgrade

  36. What happens when you upgrade • 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. MOSS Upgrade

  37. What happens when you upgrade • Run Prescan before migration • If you add new sites – must run prescan • Refresh site the list to show new sites • Three stages to the migration • Stage 1 : 135 steps, Stage 2 : 17 steps, Stage 3 : 6 steps • Temp database is used to copy the content that is being migrated. The database is removed during the upgrade process • 2-3 times more disk space is required for migration • Revert back if results are poor or to practice the migration • It is possible to get back to the pre-staged configuration to run Begin Upgrade again while you’re in test mode • Delete the MOSS site and database associated with the 2003 site MOSS Upgrade

  38. Problems Encountered MOSS Upgrade

  39. Configuration Considerations • Run Windows SharePoint Services Search on one WFE • Windows SharePoint Services Help Search  It’s the same service! • Search & Query on the WFE’s • V3 Indexer is used as a dedicated WFE for crawls • Takes the load off of the WFE’s serving content • Consider running Central Admin on more than one WFE • If the WFE running Central Admin goes down you will need to run the Configuration Wizard to generate a new admin site on another WFE • Only a few links point back to original Central Admin • Use Alternate Access Mappings in Operations if the original Central Admin site is down to fix the link MOSS Upgrade

  40. Windows SharePoint Services Search • Same service • Only need one per farm • Searches MOSS help files MOSS Upgrade

  41. Problems you may encounter • Deprecated Web Parts • Office Web Components (replaced by Excel Services) • MSNBC Web parts (replaced by RSS) • My Links Summary on MySites • Embedded links that point to areas • Documents with embedded links • Content Editor web part with links in the content • Web parts with links as parameters • InfoPath forms • Bug: In one case the “Manage Search Service” page displayed HTML code on the page when reporting remaining disk space MOSS Upgrade

  42. Problems you may encounter • Alerts from MOSS 2007 sent to Office 2007 cannot be opened • Problem with header. Hotfix for Exchange server available • Office 2007 Bugs • Content Editor Web part – cannot edit content in v2 • Cannot open Address Book to add users to a site in v2 • Recurring Meetings cannot display text in the body when using “Open this Occurrence”. Works OK with “Open Series” • SQL Server 2005 • Minimum memory size set to 128 MB • Verify Recover Model for databases – some are set to Full others are Simple MOSS Upgrade

  43. Problems you may encounter • We created an SSP for the early Search implementation • We expected a second SSP to be created when we upgraded the parent portal which we would then collapse to a single SSP before migrating the remaining portals. The SSP did not get created as expected!!! • Microsoft recommends a separate web application for MySites • In a clean MOSS environment with no migrations that makes sense. • Inconsistent with gradual upgrade and In-place migration • The parent portal is migrated first then the child portals. • It may take several months to migrate all portals. • Child portals have a MySite link that maps to a MySite collection in MOSS MOSS Upgrade

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

  45. Gradual Upgrade – MySite Problems • 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 MOSS Upgrade

  46. Creating a new MySite Collection stsadm –o createweb – url http://spstest1/mysite -sitetemplate SPSMSITEHOST -title “MySite” • Create a new MySite Host at the root of the parent site • MySite links on SPS 2003 portals that have not migrated point to: http://<portal site name>/mysite • Users are automatically redirected to mysites in MOSS MOSS Upgrade

  47. Profile Import in SSP • Schedule full AD import weekly • Filter out junk profiles that are not used • To update the User Filter • Select View Import Connections • Click Edit on one of the connections • Update the User Filter Example: (&(objectCategory=Person)(objectClass=User)(!(userAccountControl:1.2.840.113556.1.4.803:=2)) (!(displayname=~*))(!(displayname=#*))(!(displayname=+*))(mail=*)) Filters out – inactive accounts, accounts with blank email addresses, and email accounts prefixed with ~, #, + MOSS Upgrade

  48. Problems you may encounter • Customized web part errors may stop sites from being deployed to WFE’s • Mapping customizations is very time consuming • Areas • Site definitions • Need to recompile custom web parts MOSS Upgrade

  49. Office Web Components • Web Capture web part breaks in SPS 2003 after MOSS is installed • The Web.config file in the wpresources directory is altered and needs to be restored to it’s original state until the migration is finished C:\Program Files\Common Files\Microsoft Shared\web server extensions\wpresources • Install the Web Capture web parts in each MOSS WFE so the migrated web capture part functions in MOSS. Run the following command in MOSS for each cab file: stsadm.exe –o addwppack –filename c:\temp\microsoft.office.dataparts.cab –globalinstall • microsoft.sharepoint.solutions.greatplains.cab • microsoft.sharepoint.webparts.quickquote.cab MOSS Upgrade

  50. Other Problems • Fixing Orphaned MySites • Run SPSADM with repairorphans option • You must stop IIS & SharePoint services to remove the orphans • Be careful with application pools • The version of ASP.NET is based on the web site that is currently running in the App pool • Don’t mix MOSS 2007 (ver 2.0) and SPS 2003 (ver 1.1) MOSS Upgrade

More Related