Search First Migration: Using SharePoint 2013 Search with SharePoint 2010 (and earlier) Bob German – SharePoint Principal Architect BlueMetal Architects

About the Speaker Bob German Principal Architect at BlueMetal Architects Developer and architect on the SharePoint platform since it was called “Site Server 3.0” Co-author of SharePoint 2010 Development with Silverlight for Addison-Wesley BlueMetal Architects  We are experts at building solutions that exactly meet the needs of our customers by apply the right people, processes and platforms.  Our focus is on modernizing applications through expertise in Creative, Social, Development and Data.  We have offices in Boston, New York, and

A Tale of Two Search Engines ESP for SharePoint Licensing deal for FAST and SharePoint 2007 Used FAST’s original SharePoint integration FAST Search for SharePoint Common crawl and query components FAST and SharePoint farms tightly integrated SharePoint 2013 Search One search engine One farm Simple, easy, powerful

SharePoint 2010 Enterprise Search vs. FAST Search for SharePoint

Comparing the Search Engines 2010 Ent. Search2010 FAST Search2013 Search RefinersXXX Deep RefinersXX High degree of relevancyXX MultitenantXX Soundex People SearchXX Best Bets (good)X Visual Best Bets (better)X Promoted Results (best)X Entity ExtractionXX

Entity Extraction and Content Enrichment Built-in Company Name Extraction (add inclusions and exclusions) Add Custom Entity Extractors Dictionary Based Full or Partial word matches Case sensitive or insensitive Content Enrichment Web service is called with each crawled item Web service can Extract Entities Classify and Tag content Cleanse content Processing & refinement … REDMOND, Wash., and OSLO, Norway — Jan. 8, 2008 Microsoft Corp. (Nasdaq “MSFT”) today announced that it will make an offer to acquire Fast Search & Transfer ASA (OSE: “FAST”), a leading provider of enterprise search solutions, through a cash tender offer for Norwegian kroner (NOK) per share. This offer represents a 42 percent premium to the closing share price on Jan. 4, 2008 (the last trading day prior to this announcement), and values the fully diluted equity of FAST at 6.6 billion NOK (or approximately $1.2 billion U.S. ). FAST’s board of directors has unanimously recommended that its shareholders accept the offer. Location Company Company Company Location

FAST – The Good, The Bad, and The Ugly  “Deep” Refiners (refiners take whole result set into account)  Entity Extraction  Exact hit counts  Content previews (with Office Web Applications)  Visual Best Bets  Complex configuration  Single purpose – no multi- tenancy  Difficult to manage  Can’t be managed by site collection administrator  Additional hardware investment The GoodThe Bad and The Ugly

FAST for SharePoint 2010 Architecture

SharePoint 2013 Search Architecture Search Admin Content UX Crawl Content Processing Index Query ProcessingWFE API Analytics Processing FAST Search Index Content Enrichment Web Service Public API Unit of scale/role boundary Extensibility Points HTTP File shares SharePoint User profiles Lotus Notes Documentum Exchange folders Custom - BCS SharePoint SP Apps Devices Non-SP UX

Scaling SharePoint 2013 Search Partitions and replicas n Partitions 1 primary replica ≥ 0 secondary replica Add Partitions to scale content Add Replicas to scale queries and add availability All nodes perform indexing Journal shipping from primary to replicas Index Content Processing Index

Search First Migration 1.Set up SharePoint 2013 Farm 2.Set up (or migrate) Shared Service  In this case, we’ll crawl the SP2010 farm from a new SP2013 SSA 3.Consume the SP2013 service from SharePoint 2010 Notes:  Works because Service Application architecture is the same for 2010 and 2013  Users and content stay in SharePoint 2010 – no user impact  Business Data Connectivity  Managed Metadata  PerformancePoint Services  Search  Secure Store  User Profile  Search Upgrade Options: 1.Manually re-create 2.DB Attach (Admin DB only) 3.Migration scripts (from FAST 2010 only) see Migrating Shared ServicesServices that Support Upgrade

Three Approaches ContentSearch EngineSearch Center Approach 1SharePoint 2010 SharePoint 2013 SharePoint 2010 Approach 2SharePoint 2010 SharePoint 2013 Approach 3AnythingSharePoint 2013 SharePoint 2010 Federation

SharePoint 2010 Content Web App Approach 1: 2010 Search Center consumes 2013 SSA SharePoint 2013 DC SSA SA Proxy Search Center Consume Service Crawl User Profile Service

Approach 1: 2010 Search Center consumes 2013 SSA  Recommended by Microsoft as part of “Search First” migration  Enable FAST features with minimal disruption  Deep Refiners  Previews work out of the box  2013 farm hardware requirements similar to FAST farm  Invest in hardware once  No way to take advantage of new SharePoint 2013 Search UI features  Result Types  Display Templates ProCon

Approach 1: SharePoint 2010 Search Center Consumes 2013 SSA

Approach 1: 2010 Search Center consumes 2013 SSA  SharePoint 2010 Server Enterprise Edition (for FAST Search Center)  SharePoint 2013  Standard works fine  Enterprise adds:  Custom Entity Extraction  Extensible Content Processing  (other features which aren’t visible from SP2010) 1.Set up Search SA on SharePoint Crawl the 2010 farm from the new SSA  Configure managed properties and other settings 3.Exchange trust certificates between farms 4.Publish the SharePoint 2013 SSA 5.Grant the SP2010 farm access to the following SP2013 SA’s:  Application Discovery and Load Balancing  Search 6.Connect the SP2010 to the 2013 SSA 7.Associate the 2013 SSA proxy with the 2010 Web Application 8.Use the FAST Search Center on 2010 Products ShownSetup Steps

SharePoint 2010 Content Web App Approach 2: Redirect to 2013 Search Center SharePoint 2013 DC SSA Search Center Web App Search Center Crawl Redirect User Profile Service

Approach 2: Redirect to 2013 Search Center  Enjoy full SP2013 search experience  Deep Refiners  Result Types  Display Templates  Query Rules  2013 farm hardware requirements similar to FAST farm  Invest in hardware once  Extra work required to get Office previews to work  Users may find transition to the SP2013 UI to be jarring ProCon

Approach 2: Redirect to SP2013 Search Center

Approach 2: Redirect to 2013 Search Center  SharePoint 2010 Server (Standard or Enterprise)  SharePoint 2013  Standard works fine  Enterprise adds:  Custom Entity Extraction  Extensible Content Processing  Advanced actions on Query Rules  Video Search 1.Set up Search SA on SharePoint Crawl the 2010 farm from the new SSA  Configure managed properties and other settings 3.Set up a search center on SP (optional) For Office previews:  Set up an OWA 2013 server  Modify SP2013 display templates as explained here: 5.On SP2010, set results page to point to SP2013 search center Products ShownSetup Steps

SharePoint 2010 Content Web App Approach 3: Federate with 2013 Search SharePoint 2013 DC SSA Search Center SSA Crawl Federation User Profile Service External Content

Approach 3: Federate with 2013 Search  Most useful with external content  Not disruptive – users see familiar SP2010 UI  2013 farm hardware requirements similar to FAST farm  Federation works well over slow WAN connections  Results appear side by side, not reflected in refiners, no previews  No distinct advantage over Approach 1 for SharePoint content ProCon

Approach 3: Federate with SP2013 Search Center

Approach 3: Federate with 2013 Search  SharePoint 2010 Server (Standard or Enterprise)  SharePoint 2013  Standard works fine  Enterprise adds:  Custom Entity Extraction  Extensible Content Processing  (other features which aren’t visible from SP2010) 1.Set up Search SA on SharePoint Crawl the external content from the new SSA  Configure managed properties and other settings 3.Set up a search center in SP Ensure Kerberos is in place if you want security trimming 5.On SP2010, add a federated location for the SP2013 search center 6.Configure the Federated Results web part on SP2010 Products ShownSetup Steps

Choosing an Approach Approach 1: 2010 Search Center Consume 2013 Service Approach 2: 2013 Search Center Native 2013 Service Approach 3: 2010 Search Center Federate to 2013 Key ScenarioFAST Capabilities with minimal disruption Full 2013 User Experience Specialized content sources Global DeploymentLow latency between 2010 and 2013 farms Medium latency between 2010 and 2013 farms High latency / low bandwidth OK between 2010 and 2013 farms BrandingPreserve current look and feel Jump into SP2013 look and feel Preserve current look and feel SecurityRead access to all content Provide secured search service without access to all content

Summary  If you haven’t moved to FAST, there are several good reasons to move directly to SP2013 Search:  Easier to set up and maintain  First step in migrating to SP2013  Able to phase in new SP2013 user experience  Better documentation  Brighter future  Similar hardware footprint and cost (software licenses will vary depending on your agreement with Microsoft)  Choose an approach that best meets your needs Note bit.ly links are case sensitive!

Thank you!