This presentation reviews the differences between SharePoint 2010 Enterprise Search, FAST Search, and SharePoint 2013 Search. It then presents three approaches for using SharePoint 2013 to search SharePoint 2010 as part of a "Search First" migration.

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

2. 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
http://blogs.msdn.com/BobGerman
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 Chicago.
@Bob1German

3. 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
#spfestchi @Bob1German

4. SharePoint 2010
Enterprise Search vs.
FAST Search for SharePoint
#spfestchi @Bob1German

5. Comparing the Search Engines
2010 Ent. Search 2010 FAST Search 2013 Search
Refiners X X X
Deep Refiners X X
High degree of relevancy X X
Multitenant X X
Soundex People Search X X
Best Bets (good) X
Visual Best Bets (better) X
Promoted Results (best) X
Entity Extraction X X
#spfestchi @Bob1German

6. 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 19.00
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

7. 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 Good The Bad and The Ugly
#spfestchi @Bob1German

8. FAST for SharePoint 2010 Architecture
FAST Query SSA
Query Processing
FAST Content SSA
SharePoint Sites
Web Sites
File Shares
Databases
Business Apps
Query Matching
FAST Search Authorization
Search Index
Item Processing
Indexing
FAST Specific Connectors
Web Analyzer
Administration
Logical Architecture
Physical Architecture
SharePoint Server 2010
(Medium Farm)
FAST Search for SharePoint
FAST Search for SharePoint
(Small Deployment)
SharePoint Server 2010 Search Request
WFE WFE
APP
SQL
Administration
Document Processing
SQL
Search Administration Database
Crawl Database
Backup Indexer
Content Distributor
Indexing Dispatcher
Document Processing
Web Analyzer
Query Server
SQLSQL
Primary Indexer
Content Distributor
Indexing Dispatcher
Document Processing
Web Analyzer
Query Server
#spfestchi @Bob1German

9. SharePoint 2013 Search Architecture
Content UX
API
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
#spfestchi @Bob1German

10. Scaling SharePoint 2013 Search
• 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
Index Index
Index
Index
Content Processing
Index Index
IndexIndexIndex
Index
Index

11. 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 http://bit.ly/Search1Scripts
Migrating Shared Services Services that Support Upgrade

12. Three Approaches
Content Search Engine Search Center
Approach 1 SharePoint
2010
SharePoint
2013
SharePoint
2010
Approach 2 SharePoint
2010
SharePoint
2013
SharePoint
2013
Approach 3 Anything SharePoint
2013
SharePoint
2010
Federation
#spfestchi @Bob1German

13. SharePoint
2010
Content
Web App
Approach 1: 2010 Search Center consumes 2013
SharePoint
2013
DC
SSA
SA
Proxy
Search
Center
Consume
Service
User
Profile
Service
#spfestchi @Bob1German

14. Approach 1: 2010 Search Center consumes 2013
 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
Pro Con
#spfestchi @Bob1German

15. Approach 1:
SharePoint 2010 Search Center
Consumes 2013 SSA
demo

16. Approach 1: 2010 Search Center consumes 2013
 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
2013
2. 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
Products Shown Setup Steps #spfestchi @Bob1German

17. SharePoint
2010
Content
Web App
Approach 2: Redirect to 2013 Search Center
SharePoint
2013
DC
SSA
Search Center
Web App
Search
Center
User
Profile
Service
#spfestchi @Bob1German

18. 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
Pro Con
#spfestchi @Bob1German

19. Approach 2:
Redirect to SP2013 Search Center
demo
#spfestchi @Bob1German

20. 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
2013
2. Crawl the 2010 farm from the new
SSA
 Configure managed properties and other
settings
3. Set up a search center on
SP2013
4. (optional) For Office previews:
 Set up an OWA 2013 server
 Modify SP2013 display templates as
explained here: http://bit.ly/Search1Previews/
5. On SP2010, set results page to
point to SP2013 search center
Products Shown Setup Steps #spfestchi @Bob1German

21. SharePoint
2010
Content
Web App
Approach 3: Federate with 2013 Search
SharePoint
2013
DC
SSA
Search
Center
SSA
User
Profile
Service
External
Content
#spfestchi @Bob1German

22. 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
Pro Con
#spfestchi @Bob1German

23. Approach 3:
Federate with SP2013 Search
Center
demo
#spfestchi @Bob1German

24. 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
2013
2. Crawl the external content from
the new SSA
 Configure managed properties and other
settings
3. Set up a search center in SP2013
4. 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 Shown Setup Steps #spfestchi @Bob1German

25. 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 Scenario FAST Capabilities with
minimal disruption
Full 2013 User
Experience
Specialized content
sources
Global Deployment Low latency between
2010 and 2013 farms
Medium latency
between 2010 and 2013
farms
High latency / low
bandwidth OK between
2010 and 2013 farms
Branding Preserve current look
and feel
Jump into SP2013 look
and feel
Preserve current look
and feel
Security Read access to all
content
Read access to all
content
Provide secured search
service without access
to all content
#spfestchi @Bob1German

26. 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
http://bit.ly/Search1New
http://bit.ly/Search1PromotedResults
http://bit.ly/Search1Editions
http://bit.ly/Search1Farms
http://bit.ly/Search1CrossFarm
http://bit.ly/Search1Previews
http://bit.ly/Search1Scripts
#spfestchi @Bob1German

27. Thank you!
#spfestchi @Bob1German