Explore Microsoft SharePoint 2013

Microsoft Corporation
Published: October 2012
Author: Microsoft Ofce System and Servers eam !itspdocs"microsoft#com$
Abstract
his boo% provides information about &hat's ne& in SharePoint 201(# he
audiences for this boo% include application specialists) line*of*business application
specialists) and + administrators &ho &ant to %no& more about SharePoint 201(#
he content in this boo% is a copy of selected content in the SharePoint 2013 technical
library as of the publication date# ,or the most current content) see the technical
library on the &eb#


This document is provided as-is. Information and views expressed in this document, including URL
and other Internet wesite references, ma! change without notice. "ou ear the ris# of using it.
$ome examples depicted herein are provided for illustration onl! and are fictitious. %o real association
or connection is intended or should e inferred.
This document does not provide !ou with an! legal rights to an! intellectual propert! in an! &icrosoft
product. "ou ma! cop! and use this document for !our internal, reference purposes.
' ()*+ &icrosoft ,orporation. -ll rights reserved.
&icrosoft, -ccess, -ctive .irector!, /ac#stage, /ing, 0xcel, 1roove, 2otmail, 2!per-3, Info4ath,
Internet 0xplorer, 5ffice 678, 5ne%ote, 5utloo#, 4erformance4oint, 4ower4oint, $hare4oint,
$ilverlight, 5ne.rive, 3isio, 3isio $tudio, 9indows, 9indows Live, 9indows &oile,
9indows 4ower$hell, 9indows $erver, and 9indows 3ista are either registered trademar#s or
trademar#s of &icrosoft ,orporation in the United $tates and:or other countries.
The information contained in this document represents the current view of &icrosoft ,orporation on the
issues discussed as of the date of pulication. /ecause &icrosoft must respond to changing mar#et
conditions, it should not e interpreted to e a commitment on the part of &icrosoft, and &icrosoft
cannot guarantee the accurac! of an! information presented after the date of pulication.

ii
Contents
-ettin. help########################################################################################################## viii
+ Professional /evie&er's -uide for SharePoint Server 201(##################################1
See Also############################################################################################################## 1
0hat's ne& in authentication for SharePoint 201(##################################################2
1ser authentication and authori2ation in SharePoint 201(###################################2
+mprovements in claims infrastructure##################################################################(
Server*to*server authentication############################################################################ (
App authentication################################################################################################ 3
See Also############################################################################################################## 3
0hat's ne& for 4usiness Connectivity Services in SharePoint 201(########################5
O6ata support####################################################################################################### 7
Automatic .eneration of 46C models for O6ata data sources##############################7
8vent listener######################################################################################################## 9
Subscriptions enable event receivers on e:ternal lists#######################################9
Support for apps for SharePoint############################################################################ 9
About SharePoint app*scoped e:ternal content types and connections#############9
8:ternal list enhancements################################################################################### ;
Performance improvements in e:ternal lists######################################################;
<imitin. records returned by the e:ternal system##############################################;
6ata source =lterin.########################################################################################### >
Sortin. e:ternal lists########################################################################################### >
8:port e:ternal lists to 8:cel############################################################################## >
4usiness Connectivity Services in SharePoint Online enhancements####################>
/8S !CSOM$ ob?ect model for Microsoft 4usiness Connectivity Services for &eb
and mobile app developers############################################################################## 10
4usiness Connectivity Services Client /untime supports side*by*side Ofce 2010
and Ofce 201( installations############################################################################10
O6ata 0indo&s Po&erShell cmdlets###################################################################10
Additional resources############################################################################################ 10
See Also############################################################################################################ 10
0hat's ne& in e6iscovery in SharePoint Server 201(############################################11
SharePoint e6iscovery Center############################################################################# 11
SharePoint in*place holds#################################################################################### 12
SharePoint e6iscovery e:port############################################################################# 12
8nterprise*&ide e6iscovery################################################################################# 1(
See Also############################################################################################################ 1(
iii
0hat's ne& for mobile devices in SharePoint 201(###############################################13
Optimi2ed mobile bro&ser e:perience################################################################13
6evice channels################################################################################################## 15
Push noti=cations################################################################################################ 15
<ocation############################################################################################################## 15
4usiness intelli.ence content############################################################################## 15
Ofce 0eb Apps################################################################################################## 17
See Also############################################################################################################ 17
0hat's ne& in records mana.ement and compliance in SharePoint Server 201(##19
Site*based retention############################################################################################ 19
See Also############################################################################################################ 19
0hat's ne& in business intelli.ence in SharePoint Server 201(############################1;
8:cel 4+############################################################################################################### 1;
8:cel Services##################################################################################################### 1;
PerformancePoint Services################################################################################## 1>
@isio Services###################################################################################################### 20
0hat's ne& in social computin. in SharePoint Server 201(##################################21
Communities####################################################################################################### 21
My Sites############################################################################################################## 22
My Site document libraries###############################################################################2(
Savin. and synchroni2in. content####################################################################2(
Sharin. content################################################################################################ 2(
Microblo..in. and feeds################################################################################## 23
6eployment and con=.uration#########################################################################23
1p.rade considerations#################################################################################### 23
Central Administration chan.es#######################################################################25
Con=.ure permissions for personal and social features###################################25
Con=.ure microblo..in. and follo&in. settin.s###############################################25
Con=.ure policies for privacy and people#########################################################25
See Also############################################################################################################ 27
0hat's ne& in &eb content mana.ement for SharePoint 201( publishin. sites####2;
Content authorin. improvements#######################################################################2;
@ariations for multilin.ual sites###########################################################################(0
Cross*site publishin.########################################################################################### (0
Catalo.*enabled libraries and lists######################################################################(1
Mana.ed navi.ation############################################################################################ (2
Cate.ory pa.es################################################################################################### ((
,riendly 1/<s###################################################################################################### ((
Content Search 0eb Part#################################################################################### ((
/e=ners and faceted navi.ation##########################################################################(3
Analytics and recommendations######################################################################### (3
iv
4randin.############################################################################################################## (5
6evice*speci=c tar.etin.##################################################################################### (5
0hat's ne& in &or%Ao& in SharePoint Server 201(###############################################(7
&o SharePoint &or%Ao& platforms#####################################################################(7
SharePoint 6esi.ner enhancements###################################################################(9
0or%Ao& Mana.er capabilities############################################################################ (;
0indo&s Po&erShell cmdlets that mana.e &or%Ao&##########################################(>
See Also############################################################################################################ (>
0hat's ne& in search in SharePoint Server 201(###################################################30
Search user interface improvements##################################################################30
/elevance improvements#################################################################################### 31
Be& ran%in. models######################################################################################### 31
Analysis of content and user interaction##########################################################31
Cuery rules####################################################################################################### 31
/esult sources################################################################################################## 32
Chan.es in cra&lin.############################################################################################ 32
Continuous cra&l############################################################################################## 3(
Dost distribution rules removed#######################################################################3(
/emovin. items from the search inde:############################################################3(
6iscoverin. structure and entities in unstructured content################################3(
More Ae:ible search schema############################################################################### 3(
Search health reports########################################################################################## 33
Be& search architecture##################################################################################### 33
Chan.es from SharePoint 2010 to SharePoint 201(##############################################35
,eatures deprecated in SharePoint 201(#############################################################35
@isual up.rade################################################################################################## 35
6ocument 0or%space site template#################################################################37
Personali2ation Site site template####################################################################37
Meetin. 0or%space site templates###################################################################39
-roup 0or% site template and -roup 0or% solution#########################################39
@isio Process /epository site template#############################################################39
1n.hostin. and customi2in. CSS =les##############################################################3;
+ma.in. 0eb service######################################################################################## 3;
8:cel Services E Can't edit &or%boo%s in the bro&ser that have e:ternal data
connections################################################################################################### 3;
0eb Analytics in SharePoint Server 2010#########################################################3>
8:cel Services E Can't edit &or%boo%s in the bro&ser that have e:ternal data
connections###################################################################################################### 50
Or.ani2ation Pro=les########################################################################################### 50
SharePoint ,oundation 2010 deprecated search features###################################50
Search capabilities########################################################################################### 50
SharePoint Server 2010 deprecated search features##########################################51
v
Modifyin. the search topolo.y usin. a &eb*based interface############################51
6iacritic sensitivity element in the thesaurus##################################################51
/eplacement mode &ithin the thesaurus#########################################################51
Search Cuery &eb service################################################################################52
Search /SS and search from 0indo&s#############################################################52
Custom &ord brea%er dictionaries####################################################################52
Con=.uration of stemmin. in the re.istry########################################################5(
SharePoint Search SC< synta:##########################################################################5(
Shallo& search re=ners#################################################################################### 5(
,AS Search Server 2010 for SharePoint deprecated features############################53
,AS Search database connector#####################################################################53
,AS Search <otus Botes connector#################################################################53
,AS Search &eb cra&ler################################################################################## 53
,ind similar results############################################################################################ 57
,AS Cuery <an.ua.e !,C<$ deprecated features############################################57
1/< Cuery synta:############################################################################################# 59
Speci=c search scope =lters#############################################################################5;
Anti*phrasin.#################################################################################################### 5>
OFensive content =lterin.################################################################################5>
Substrin. search############################################################################################### 5>
Person names and location e:tractions############################################################70
Bumber of custom entity e:tractors#################################################################70
Supported document formats###########################################################################70
Content processin. e:tensibility######################################################################71
Custom GM< item processin.########################################################################### 71
Addin. a test item to the inde:########################################################################71
See Also############################################################################################################ 72
Overvie& of identity mana.ement in SharePoint 201(##########################################7(
8lements of an identity mana.ement system#####################################################7(
8ntities############################################################################################################# 7(
Stores for accounts and attributes###################################################################73
Methods of authentication################################################################################73
Claims*based identity and authentication########################################################73
Methods of authori2ation################################################################################## 75
Methods to store) synchroni2e) and display entity attributes###########################77
See Also############################################################################################################ 77
est lab .uides for SharePoint Server 201(###########################################################79
echBet articles about <-s for SharePoint Server 201(####################################79
Additional resources about <-s######################################################################### 7;
est <ab -uide: Con=.ure SharePoint Server 201( in a hree*ier ,arm################7>
6o&nload the test lab .uide###############################################################################7>
See Also############################################################################################################ 7>
vi
est <ab -uide: 6emonstrate +ntranet Collaboration for SharePoint Server 201(##90
6o&nload the test lab .uide###############################################################################90
See Also############################################################################################################ 90
est <ab -uide: 6emonstrate Social ,eatures for SharePoint Server 201(############91
6o&nload the test lab .uide###############################################################################91
See Also############################################################################################################ 91
est <ab -uide: 6emonstrate SAM<*based Claims Authentication &ith SharePoint
Server 201(######################################################################################################## 92
6o&nload the test lab .uide###############################################################################92
See Also############################################################################################################ 92
est <ab -uide: 6emonstrate forms*based claims authentication for SharePoint
Server 201(######################################################################################################## 9(
6o&nload the test lab .uide###############################################################################9(
See Also############################################################################################################ 9(
vii
Getting help
Every effort has been made to ensure the accuracy of this book. This content is also available online in
the Office System TechNet ibrary! so if you run into "roblems you can check for u"dates at#
http;::technet.microsoft.com:office
$f you do not find your ans%er in our online content! you can send an email messa&e to the 'icrosoft
Office System and Servers content team at#
itspdocs<microsoft.com
$f your (uestion is about 'icrosoft Office "roducts! and not about the content of this book! "lease
search the 'icrosoft )el" and Su""ort *enter or the 'icrosoft +no%led&e ,ase at#
http;::support.microsoft.com

viii
IT Professional Reie!er"s G#i$e for SharePoint
Serer 2013
P#blishe$% Septe&ber '( 2012
S#&&ar)% earn ho% ne% ca"abilities in SharePoint Server 2013 can hel" $T "ros better mana&e cost!
risk! and time.
This &uide describes ho% SharePoint Server 2013 builds on the investments of "revious SharePoint
releases to hel" you do the follo%in&#
o%er $T costs %ith a fle-ible and scalable collaboration "latform.
,etter mana&e risk by safe&uardin& your business %ith secure and reliable ca"abilities.
$ncrease "roductivity throu&h cost.effective and efficient mana&ement.
/o%nload this &uide as a P/0 document.
SharePoint Server 2013 Previe% $T Professional 1evie%er2s 3uide 4htt"#55&o.microsoft.com5f%link5"56
ink$d7283991:
See Also
SharePoint 2013 for $T "ros

*hat"s ne! in a#thentication for SharePoint
2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% SharePoint 2013 includes im"rovements in claims infrastructure and authentication features
that enable ne% server.to.server and a"" authentication scenarios.
-pplies to; $hare4oint $erver ()*6 0nterprise = $hare4oint $erver ()*6 $tandard = $hare4oint
>oundation ()*6
;uthentication enhancements in SharePoint 2013 make the use of claims.based authentication easier
and enable ne% scenarios and functionality for E-chan&e Server 2013! ync Server 2013! and a""s in
the SharePoint Store or ;"" *atalo&. SharePoint 2013 introduces su""ort for server.to.server
authentication and a"" authentication by utili<in& and e-tendin& the O"en ;uthori<ation 2.0 4O;uth 2.0:
%eb authori<ation "rotocol. O;uth is an industry standard "rotocol that "rovides tem"orary! redirection.
based authori<ation. ; user or a %eb a""lication that acts on behalf of a user can re(uest authori<ation
to tem"orarily access s"ecified net%ork resources from a resource o%ner. 0or more information! see
O;uth 2.0.
Su""ort for O;uth in SharePoint 2013 allo%s users to &rant a""s in the SharePoint Store and ;""
*atalo& access to s"ecified! "rotected user resources and data 4includin& contact lists! documents!
"hoto&ra"hs! and videos: %ithout re(uirin& the a"" to obtain! store! or submit the user=s credentials.
O;uth allo%s a"" and services to act on behalf of users for limited access to SharePoint resources. 0or
e-am"le! a user mi&ht a""rove "ermissions to an a"" to &rant access to a s"ecific folder of a document
library. This enables an a""! such as a third."arty "hoto "rintin& a""! to access and co"y the files in the
s"ecific folder u"on user re(uest! %ithout havin& to use or verify the user=s account credentials.
-ser a#thentication an$ a#thori.ation in SharePoint
2013
>ser authentication in SharePoint 2013 is the "rocess that verifies the identity of a user %ho re(uests
access to a SharePoint %eb a""lication. ;n authentication "rovider issues the authenticated user a
security token that enca"sulates a set of claims.based assertions about the user and is used to verify a
set of "ermissions that are assi&ned to the user. >ser authori<ation in SharePoint 2013 is the "rocess
that determines the users %ho can "erform defined o"erations on a s"ecified resource %ithin a
SharePoint %eb a""lication. SharePoint 2013 su""orts user authentication based on the follo%in&
methods#
?indo%s claims
Security ;ssertion 'arku" an&ua&e 4S;':.based claims
0orms.based authentication claims
These claims.based authentication methods are no% the recommended authentication methods for
SharePoint 2013.
2
The a"" authentication and server.to.server authentication features of SharePoint 2013 re(uire claims.
based authentication. ,ecause of this! claims.based authentication is the default for ne% %eb
a""lications in SharePoint 2013. ?hen you create a %eb a""lication in *entral ;dministration! you can
only s"ecify authentication methods for claims.based authentication. ;lthou&h ?indo%s *lassic mode
authentication is still available in SharePoint 2013 and can be confi&ured throu&h ?indo%s Po%erShell!
%e recommend that you use claims.based authentication. ?indo%s *lassic mode authentication is
de"recated in SharePoint 2013.
I&proe&ents in clai&s infrastr#ct#re
SharePoint 2013 also includes the follo%in& im"rovements in claims authentication infrastructure#
Easier mi&ration from classic mode to ?indo%s.based claims mode %ith the ne% Conert/
SP*ebApplication ?indo%s Po%erShell cmdlet
'i&ration can be run a&ainst each content database and each %eb a""lication. This is in contrast to
SharePoint 2010 Products! in %hich the mi&ration %as run a&ainst each %eb a""lication. 0or more
information! see 'i&rate from classic.mode to claims.based authentication.
o&in tokens are no% cached in the ne% /istributed *ache Service
SharePoint 2013 uses a ne% /istributed *ache Service to cache lo&in tokens. $n SharePoint 2010
Products! the lo&in token is stored in the memory of each %eb front.end server. Each time a user
accesses a s"ecific %eb front.end server! it needs to authenticate. $f you use net%ork load
balancers in front of your %eb front.ends! users need to authenticate for each %eb front.end server
that is accessed behind the load balancer! causin& "ossible multi"le re.authentications. To avoid re.
authentication and its delay! it is recommended to enable and confi&ure load balancer affinity 4also
kno%n as sticky sessions:. ,y storin& the lo&in tokens in the /istributed *ache Service in
SharePoint 2013! the confi&uration of affinity in your load balancin& solution is no lon&er re(uired.
There are also scale.out benefits and less memory utili<ation in the %eb front.ends because of a
dedicated cache service.
'ore lo&&in& makes the troubleshootin& of authentication issues easier
SharePoint 2013 has much more lo&&in& to hel" you troubleshoot authentication issues. E-am"les
of enhanced lo&&in& su""ort are the follo%in&#
Se"arate cate&ori<ed.claims related lo&s for each authentication mode
$nformation about addin& and removin& 0ed;uth cookies from the /istributed *ache Service
$nformation about the reason %hy a 0ed;uth cookie could not be used! such as a cookie
e-"iration or a failure to decry"t
$nformation about %here authentication re(uests are redirected
$nformation about the failures of user mi&ration in a s"ecific site collection
Serer/to/serer a#thentication
SharePoint 2013 e-tends O;uth to im"lement a server.to.server authentication "rotocol that can be
used by services such as SharePoint 2013 to authenticate other services such as E-chan&e Server
3
2013 or ync Server 2013 or services that are com"liant %ith the server.to.server authentication
"rotocol.
SharePoint 2013 has a dedicated local server.to.server security token service 4STS: that "rovides
server.to.server security tokens that contain user identity claims to enable cross.server authenticated
access. These user identity claims are used by the other service to looku" the user a&ainst its o%n
identity "rovider. ; trust established bet%een the local STS 4the SharePoint 2013 server.to.server STS:
and other server.to.server com"liant services 4the E-chan&e Server 2013 or ync Server 2013 server.
to.server STS: is the key functionality that makes server.to.server "ossible. 0or on."remises
de"loyments! you confi&ure the @avaScri"t ObAect Notation 4@SON: metadata end"oint of the other
server.to.server com"liant service to establish this trust relationshi". 0or online services! an instance of
the ?indo%s ;<ure ;ccess *ontrol Service 4;*S: acts as a trust broker to enable cross.server
communications amon& the three ty"es of servers.
The ne% server.to.server STS in SharePoint 2013 issues access tokens for server.to.server
authentication. $n SharePoint 2013 4and also in SharePoint 2010 Products:! trusted identity "roviders
that are com"liant %ith the ?S.0ederation "rotocol are su""orted. )o%ever! the ne% server.to.server
STS in SharePoint 2013 "erforms only the functionality that enables tem"orary access tokens to
access other services such as E-chan&e Server 2013 and ync Server 2013. The server.to.server STS
is not used for user authentication and is not listed on the user si&n.in "a&e! the ;uthentication Provider
>$ in *entral ;dministration! or in the Peo"le Picker in SharePoint 2013 Products.
App a#thentication
SharePoint 2013 uses O;uth 2.0 to authori<e re(uests by a""s in the SharePoint Store and ;""
*atalo& to access SharePoint resources on behalf of a user. The user &rants "ermission to a""s in the
SharePoint Store and ;"" *atalo& to access SharePoint resources on the user2s behalf %hen they are
installed. 0or e-am"le! a user installs an a"" from the SharePoint Store. ; SharePoint site contains an
embedded )T' inline frame 4$01;'E: that the a"" renders and that re(uires the a"" to access a
user list. ?hen a ?eb bro%ser dis"lays the site! the a"" then calls back to the server runnin&
SharePoint 2013 to access the list on behalf of the user. ;fter the a"" obtains the data from the list! it
dis"lays the contents of the $01;'E.
The a"" authentication "rocess in SharePoint 2013 uses O;uth to verify a claim that an a"" makes
and assert that the a"" can act on behalf of an authenticated user. $n SharePoint 2013! an instance of
the ?indo%s ;<ure ;*S acts as the a"" identity "rovider. Bou can also use a"" authentication %ithout
;*S. The authori<ation "rocess verifies that an authenticated a"" has "ermission to "erform a defined
o"eration or to access a s"ecified resource.
See Also
E-"lore SharePoint 2013
;uthentication
*onfi&ure authentication infrastructure

9
*hat"s ne! for 0#siness Connectiit) Serices
in SharePoint 2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% earn about the ne% features and ca"abilities of ,usiness *onnectivity Services 4,*S: in
SharePoint 2013! includin& O/ata! ,/* models! and a""s for SharePoint.
-pplies to; $hare4oint >oundation ()*6 = $hare4oint $erver ()*6
The SharePoint 2013 and the Office 2013 suites include 'icrosoft ,usiness *onnectivity Services. ?ith
,usiness *onnectivity Services! you can use SharePoint 2013 and Office 2013 clients as an interface
into data that doesn=t live in SharePoint 2013 itself. $t does this by makin& a connection to the data
source! runnin& a (uery! and returnin& the results. ,usiness *onnectivity Services returns the results to
the user throu&h an e-ternal list! or a"" for SharePoint! or Office 2013 %here you can "erform different
o"erations a&ainst them! such as *reate! 1ead! >"date! /elete! and Cuery 4*1>/C:. ,usiness
*onnectivity Services can access e-ternal data sources throu&h O"en /ata 4O/ata:! ?indo%s
*ommunication 0oundation 4?*0: end"oints! %eb services! cloud.based services! and .NET
assemblies! or throu&h custom connectors.
This article lists the ne% and enhanced ca"abilities of ,usiness *onnectivity Services in SharePoint
2013. $f you are ne% to ,usiness *onnectivity Services! see ,usiness *onnectivity Services Overvie%
4SharePoint 2013:. To learn more about chan&es and ne% features for develo"ers that have been
added to ,usiness *onnectivity Services 4,*S: for SharePoint 2013! see ?hat2s ne% in ,usiness
*onnectivity Services in SharePoint 2013 in the 'S/N ibrary
$n this article#
O/ata su""ort
;utomatic &eneration of ,/* models for O/ata data sources
Event listener
Su""ort for a""s for SharePoint
E-ternal list enhancements
,usiness *onnectivity Services in SharePoint Online enhancements
1EST 4*SO': obAect model for 'icrosoft ,usiness *onnectivity Services for %eb and mobile a""
develo"ers
,usiness *onnectivity Services *lient 1untime su""orts side.by.side Office 2010 and Office 2013
installations
O/ata ?indo%s Po%erShell cmdlets
;dditional resources
D
12ata s#pport
SharePoint 2013 introduces su""ort for O/ata ,usiness /ata *onnectivity 4,/*: connections. This is
in addition to data connections for ?*0! SC Server! and .NET assemblies. The O"en /ata Protocol
4O/ata: is a %eb "rotocol that is used to (uery and u"date data. O/ata a""lies %eb technolo&ies such
as )TTP! ;tom Publishin& Protocol 4;tomPub:! and @avaScri"t ObAect Notation 4@SON: to "rovide
access to information from a variety of a""lications! services! and stores. 0or more information about
O/ata! see $ntroducin& O/ata# /ata ;ccess for the ?eb! the cloud! mobile devices! and more in the
'S/N ibrary. 0or years! SharePoint has been an O/ata "rovider! %hich means a SharePoint list can
be consumed by usin& O/ata. $n SharePoint 2013! you can no% connect to an e-ternal data source by
usin& O/ata. 0or e-am"les of O/ata "roviders and for more information about O/ata su""ort! see
E*onnectin& to O"en /ata 4O/ata: /ata SourcesF in ?hat=s ne% in ,usiness *onnectivity Services for
develo"ers in the 'S/N ibrary. 0or more information on usin& O/ata in ,*S in SharePoint 2013! see
>sin& O/ata sources %ith ,usiness *onnectivity Services in SharePoint 2013 in the 'S/N ibrary.
,usiness *onnectivity Services su""orts ;nonymous! ,asic! ?indo%s! and *ustom authentication to
O/ata services %hen it is used %ith the Secure Store Service. $f you %ant to a""ly "ermissions at more
discrete levels! use O/ata connections. O/ata connections "rovide an easier %ay to create ,/*
models that %ork for both SharePoint 2013 and Office 2013 client a""lications. $n SharePoint 2013! you
can connect e-ternal lists that are surfaced throu&h O/ata to Office 2013 clients and you can %ork %ith
the data %hen you are offline. ?hen the Office 2013 client reconnects! it "erforms bidirectional
synchroni<ation %ith the O/ata source.
A#to&atic generation of 02C &o$els for 12ata $ata
so#rces
,efore SharePoint 2013 or SharePoint Online can be used as an interface to e-ternal data! they must
understand %hat kind of data source it is! ho% to talk to it! and %hat kind of authentication the e-ternal
system e-"ects. These items G and also %hich tables to read! %hich items from those tables are of
interest! and %hich o"erations to "erform on them G are all described to ,usiness *onnectivity
Services in a ,/* model. $n SharePoint 2013! you must use Hisual Studio 2010 to create ,/* models
for O/ata data sources. To make the ,/* model creation "rocess smoother! Hisual Studio 2010 %ill be
able to connect to the O/ata end"oint throu&h ,usiness *onnectivity Services and read the O/ata
source. Hisual Studio 2010 %ill then automatically &enerate the ,/* model based on the available
metadata. The ,/* model can then be either im"orted into the ,usiness /ata *atalo& as a farm.
sco"ed e-ternal content ty"e! or be included in an a"" for SharePoint. 0arm.sco"ed e-ternal content
ty"es can be used in e-ternal data lists! business data ?eb Parts! or business data in lists any%here
across the SharePoint farm.
The ,/* model %ill not contain any filters because it is not "ossible to kno% %hat these %ould be
beforehand. ,y default! Hisual Studio 2010 %ill &enerate all the ,usiness *onnectivity Services
o"erations for all the O/ata o"erations 43et! Put! Post! and /elete:.
8
Eent listener
SharePoint 2013 "rovides an event listener. The event listener includes an event subscriber on the
SharePoint 2013 side. The subscriber receives notifications from the event "ublisher 4on the e-ternal
system side: on chan&es to the data and then initiates "redefined actions %hen chan&es occur. This
enables SharePoint users and custom code to receive notifications of events that occur in the e-ternal
system. The users and custom code need to e-"licitly subscribe to events on entities for %hich they
%ant to receive a notification. The e-ternal system can use any of the su""orted connections 4O/ata!
SC! or ?*0: for transactions %ith the e-ternal system. )o%ever! to su""ort eventin&! the e-ternal
system must im"lement interfaces that allo% users to subscribe to events and it must send the
notifications back as ;TO' feeds or @SON obAects to the SharePoint 2013 end"oint.
S#bscriptions enable eent receiers on external lists
SharePoint 2013 su""orts a "ull model for &ettin& data from an e-ternal system and it introduces a
subscri"tion model. $n this version! develo"ers can create ,/* models that subscribe to "ublished
events from an event "ublisher in the e-ternal system. The develo"ers can tar&et a "articular entity in
the e-ternal system! such as the *ustomer entity! and receive notifications about events that are
"ublished on that entity. This enables develo"ers to %rite custom code for e-ternal lists that tri&&er
SharePoint events %hen data is chan&ed. SharePoint users can also subscribe to alerts on e-ternal
lists that are associated %ith a ,/* model in %hich a develo"er has defined a subscri"tion. 0or
e-am"le! you can create a custom event on an e-ternal list that sends an email messa&e to an
em"loyee %hen a customer account is assi&ned to that em"loyee in the e-ternal system. Bou can do
this by subscribin& to a "articular event 4or alert: on a "articular vie% of an e-ternal list. Note that users
can subscribe to an event the same %ay that they did in SharePoint Server 2010. 0or information about
ho% to subscribe to an alert! see *reate an alert or subscribe to an 1SS 0eed on Office.com. 0or more
information! see E1eceivin& Events from E-ternal SystemsF in ?hat=s ne% in ,usiness *onnectivity
Services for develo"ers in the 'S/N ibrary.
S#pport for apps for SharePoint
SharePoint 2013 introduces a""s for SharePoint. ,y usin& a""s for SharePoint! you can add
functionality to a SharePoint site by usin& the self.contained a"" for SharePoint. ?hen installed! a""s
for SharePoint do not make any chan&es to the underlyin& code on the com"uter that is runnin&
SharePoint Server. Therefore! each a"" for SharePoint is isolated from the rest of the system. ,ecause
a""s for SharePoint contain all the resources that they need to function! they are very safe to use and
also can be uninstalled cleanly. This article focuses on ,usiness *onnectivity Services su""ort for a""s
for SharePoint. ,usiness *onnectivity Services su""orts a""s for SharePoint in t%o %ays. 0irst! ,/*
models can be sco"ed to a""s for SharePoint. Second! connection information is defined and stored
se"arately from the a"".sco"ed ,/* model in ,/* connections.
Abo#t SharePoint app/scope$ external content t)pes an$
connections
$n SharePoint 2013! develo"ers of a""s for SharePoint can "acka&e ,/* models in an a"" for
SharePoint. The ,usiness *onnectivity Services runtime then creates e-ternal content ty"es that are
I
sco"ed to the a"" for SharePoint. This limits use of the e-ternal content ty"e to the a"" for SharePoint.
*onnection "ro"erties can be s"ecified in t%o %ays! either in the ,/* model that is contained in the
a"" for SharePoint or in a ,usiness *onnectivity Services connection settin&s obAect that is created and
stored in the Secure Store. Other%ise! if you connect to a data source that re(uires authentication! the
connection must be defined se"arately in the ,usiness *onnectivity Services layer by a develo"er.
;lso! an O/ata connection must be used to connect the a"" for SharePoint to the e-ternal data source.
,y definin& the connections se"arately from the ,/* models that are "acka&ed %ithin the a"" for
SharePoint! administrators can more easily mana&e connections to e-ternal systems. ; ,usiness
*onnectivity Services connection settin&s obAect is a combination of the follo%in&#
; name for the connection.
The end"oint >1 of the data source.
; declaration of the credential ty"e and authentication method that %ill be used to authenticate %ith
the end"oint >1 of the data source. Bou must use a credential ty"e and authentication method
that is su""orted by the e-ternal data source. 0or e-am"le! you can declare that the connection %ill
use the credentials of the user that is lo&&ed in or a different set. *ertificate details can be included
also.
?hen an administrator installs an a"" for SharePoint that needs to access a data feed throu&h
,usiness *onnectivity Services! the a"" for SharePoint must use a ,/* connection. /urin&
installation! the administrator must &rant "ermission to the a"" for SharePoint to use the a""ro"riate
,/* connection. Note that e-ternal content ty"es created from an a"".sco"ed ,/* model are sco"ed
to only the a"" for SharePoint that contains the model. )o%ever! multi"le a""s for SharePoint G each
of %hich contains an a"".sco"ed ,/* model G can all "oint to the same ,usiness *onnectivity
Services connection settin&s obAect. $n this %ay! connection settin&s can be reused across different
a""s for SharePoint. 0or more information about %hat=s ne% for develo"ers fora"".sco"ed e-ternal
content ty"es and ho% to create a connection! see E;"".Sco"ed E-ternal *ontent Ty"esF in ?hat=s ne%
in ,usiness *onnectivity Services for develo"ers in the 'S/N ibrary. 0or a develo"er overvie% of
a""s for SharePoint! see ;"".sco"ed e-ternal content ty"es in SharePoint 2013
External list enhance&ents
SharePoint 2013 includes enhancements to e-ternal lists that brin& them to functional "arity %ith other
SharePoint lists.
Perfor&ance i&proe&ents in external lists
SharePoint 2013 introduces a number of im"rovements for e-ternal lists. These im"rovements reduce
the load on the database servers in the SharePoint farm and increase the s"eed of list renderin&.
Performance is enhanced by havin& the e-ternal system do "a&in&! filterin&! and sortin& of the e-ternal
list data before it is sent to SharePoint.
3i&iting recor$s ret#rne$ b) the external s)ste&
?hen a limit filter is defined for a ,/* model! users can s"ecify the number of records in the list that
they %ant dis"layed "er "a&e.
J
2ata so#rce filtering
>sers can use a dro".do%n list on a column in an e-ternal list to filter (ueries. /evelo"ers can "re"are
*ollaborative ;""lication 'arku" an&ua&e 4*;': (ueries or calls to the SPist obAect model to filter
a list. $n SharePoint 2013! if a data source filter is defined in the ,/* model! the filterin& occurs on the
e-ternal system before it is "assed to SharePoint.
Sorting external lists
$n SharePoint 2013! the user=s re(uest to sort an e-ternal list is sent to the e-ternal system. The
e-ternal system sorts the data! and then sends it to the e-ternal list. To do this! the solution develo"er
adds a sort filter to the ,/* model for each column in the e-ternal list that the develo"er %ants users to
be able to sort. Sortin& is a""lied on the entire dataset in the e-ternal system! instead of Aust the first set
of data retrieved. The result is an accurately sorted list that is dis"layed to the user. 0or more
information about "a&in&! filterin&! and sortin& e-ternal lists! see EEnhanced 0ilterin&! Sortin& and
"a&in& for e-ternal listsF in ?hat=s ne% in ,usiness *onnectivity Services for develo"ers in the 'S/N
ibrary.
Export external lists to Excel
$n SharePoint 2013! you can e-"ort an e-ternal list to E-cel 2010 or to E-cel 2013. This %orks much
like e-"ortin& SharePoint native lists to E-cel in SharePoint Server 2010. )o%ever! there are some
differences in ho% you control %hat &ets e-"orted and ho% you %ork %ith the e-"orted data. ,y default!
e-"ortin& e-ternal lists is enabled. )o%ever! an administrator can disable this.
?hen you e-"ort an e-ternal list to E-cel! you basically &et the list as it is dis"layed in the bro%ser. Bou
&et only the data that is "resent in the selected vie% and the ro%s and columns in E-cel %ill have the
same sortin& and filterin& a""lied as the e-ternal list. The column names in the e-"orted data %ill have
the same lan&ua&e settin&s as the e-ternal list and the e-"orted data is subAect to any filters that are on
the e-ternal system.
The "rocess of e-"ortin& data creates a one.%ay 4e-ternal list to E-cel: link bet%een the e-ternal list
and the E-cel version of the list. The E-cel version can be refreshed at any time to reflect the current
state of the source e-ternal list. This means that any chan&es users mi&ht have made to the E-cel
version are over%ritten. *han&es that are made in the E-cel version are never "ushed back u" to the
source e-ternal list.
0#siness Connectiit) Serices in SharePoint 1nline
enhance&ents
;ll Office 38D for enter"rises subscri"tions include SharePoint Online. This version of SharePoint
Online introduces ,usiness *onnectivity Services to the Office 38D users. ,y usin& this version! you %ill
be able to brin& e-ternal data into SharePoint Online from cloud.based data sources and from data
sources that are behind your com"any=s fire%all in a hybrid scenario. 'icrosoft ,usiness *onnectivity
Services can consume data sources that are e-"osed as ?*0 services! SC ;<ure data services!
O/ata end"oints! and %eb services.
K
REST 4CS1M5 ob6ect &o$el for Microsoft 0#siness
Connectiit) Serices for !eb an$ &obile app
$eelopers
$n SharePoint 2013! ,usiness *onnectivity Services e-"oses the 1e"resentational State Transfer
41EST: ;P$s for %eb and mobile a"" develo"ers to use. These ;P$s "rovide a standard interface to the
develo"ers.
0#siness Connectiit) Serices Client R#nti&e
s#pports si$e/b)/si$e 1ffice 2010 an$ 1ffice 2013
installations
,usiness *onnectivity Services *lient 1untime no% su""orts side.by.side installation of Office 2010
and Office 2013 on the same client com"uter. 0or e-am"le! if Outlook 2010 and ync 2013 are installed
on the same client com"uter! by default both versions of ,usiness *onnectivity Services *lient 1untime
are also installed. This ne% feature enables Office 2010 and Office 2013 to continue to %ork %ithout
causin& conflicts or failures %hen 'icrosoft ,usiness *onnectivity Services *lient 1untime is used.
12ata *in$o!s Po!erShell c&$lets
SharePoint 2013 includes the follo%in& si- ne% ?indo%s Po%erShell cmdlets s"ecifically for O/ata.
Get/SP12ataConnectionSetting 1eads a ,usiness *onnectivity Services connection of a ,/*
service a""lication and returns the ,usiness *onnectivity Services connection obAect.
Get/SP12ataConnectionSettingMeta$ata 1eturns ,usiness *onnectivity Services connection
metadata "ro"erties.
7e!/SP12ataConnectionSetting *reates a ne% ,usiness /ata *onnectivity connection.
Re&oe/SP12ataConnectionSetting /eletes the ,usiness *onnectivity Services connection
obAect to&ether %ith its metadata obAect.
Set/SP12ataConnectionSetting *an be used to edit the "ro"erties of an e-istin& ,usiness
*onnectivity Services connection.
Set/SP12ataConnectionSettingMeta$ata *an be used to edit metadata "ro"erties of an
e-istin& ,usiness *onnectivity Services connection.
A$$itional reso#rces
0or develo"er.focused information about %hat=s ne% in ,usiness *onnectivity Services! see ?hat=s
ne% in ,usiness *onnectivity Services for develo"ers in the 'S/N ibrary.
10
See Also
,usiness *onnectivity Services Overvie% 4SharePoint 2013:
11
*hat"s ne! in e2iscoer) in SharePoint Serer
2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% 3et a (uick introduction to e/iscovery and in."lace hold ca"abilities in SharePoint Server
2013.
-pplies to; $hare4oint $erver ()*6
The e/iscovery functionality in SharePoint Server 2013 "rovides im"roved %ays to hel" you "rotect
your business. SharePoint Server 2013 includes the follo%in&#
; site collection from %hich you can "erform e/iscovery (ueries across multi"le SharePoint farms
and E-chan&e servers and "reserve the items that are discovered.
$n."lace "reservation of E-chan&e mailbo-es and SharePoint sites G includin& SharePoint list
items and SharePoint "a&es G %hile still allo%in& users to %ork %ith site content.
Su""ort for searchin& and e-"ortin& content from file shares.
The ability to e-"ort discovered content from E-chan&e Server 2013 and SharePoint Server 2013.
The follo%in& sections describe the ne% functionality#
SharePoint e/iscovery *enter
SharePoint in."lace holds
SharePoint e/iscovery e-"ort
Enter"rise.%ide e/iscovery
SharePoint e2iscoer) Center
SharePoint Server 2013 introduces a ne% site for mana&in& discovery cases and holds. The
e.iscover! ,enter site tem"late creates a "ortal throu&h %hich you can access discovery cases to
conduct searches! "lace content on hold! and e-"ort content. 0or each case! you create a ne% site that
uses the e.iscover! ,ase site tem"late. Each case is a collaboration site that includes a document
library %hich you can use to store documents related to the mana&ement of the case. $n addition! you
can associate the follo%in& thin&s %ith each case#
So#rces% E-chan&e mailbo-es! SharePoint sites! or file shares from %hich content can be
discovered.
e2iscoer) sets% *ombinations of sources! filters! and %hether to "reserve content. e/iscovery
sets are used to identify and "reserve content.
8#eries% The search criteria! such as author! date ran&e! and free.te-t terms! and the sco"e of the
search. Cueries are used to identify content to e-"ort.
Exports% ; list of all of the e-"orts that %ere "roduced that relate to the case.
12
?hen there is a ne% need for discovery G for e-am"le! a le&al case or an audit G a user %ho has
a""ro"riate "ermissions can create a ne% case! create e/iscovery sets to identify the s"ecific material
to be located! and then "reserve the sites and mailbo-es in %hich content %as discovered. The user
can then create (ueries to further refine the content that is relevant! "revie% the content! and e-"ort the
content. ?hen the case is closed! all of the holds associated %ith the case are released.
SharePoint in/place hol$s
$n SharePoint Server 2013! content that is "ut on hold is "reserved! but users can still chan&e it. The
state of the content at the time of "reservation is recorded. $f a user chan&es the content or even
deletes it! the ori&inal! "reserved version is still available. 1e&ular users see the current version of the
contentL com"liance officers %ho have "ermissions to use the e/iscovery features of SharePoint
Server 2013 can access the ori&inal! "reserved version.
$n."lace holds in SharePoint Server 2013 offer im"rovements to the hold functionality in earlier versions
of SharePoint Server. $m"rovements include the follo%in&#
/ocuments! list items! "a&es! and E-chan&e Server 2013 mailbo-es can be "reserved.
Preservation is done at the level of a site. Preservin& a site "reserves the contents of the site.
>sers can continue to %ork %ith content that is "reserved. The content remains in the same
location! and users can edit! delete! and add ne% content.
; user %ho has "ermissions to "erform e/iscovery can access the ori&inal version of "reserved
content.
Bou do not have to "reserve a %hole site or mailbo-. Bou can s"ecify a (uery filter to define the
sco"e of "reservation! and "reserve only the content that matches the (uery filter.
SharePoint e2iscoer) export
$n SharePoint Server 2013! you can e-"ort the results of an e/iscovery search for later im"ort into a
revie% tool. Bou can e-"ort all of the content that is associated %ith an e/iscovery case. This includes
the follo%in&#
2oc#&ents% /ocuments are e-"orted from file shares. /ocuments and their versions are e-"orted
from SharePoint Server 2013.
3ists% $f a list item %as included in the e/iscovery (uery results! the com"lete list is e-"orted as a
comma.se"arated values 4.csv: file.
Pages% SharePoint "a&es! such as %iki "a&es or blo&s! are e-"orted as '$'E )T' 4.mht: files.
Exchange ob6ects% $tems in an E-chan&e Server 2013 mailbo-! such as tasks! calendar entries!
contacts! email messa&es! and attachments! are e-"orted as a ."st file.
;n M' manifest that com"lies %ith the Electronic /iscovery 1eference 'odel 4E/1': s"ecification
"rovides an overvie% of the e-"orted information.
13
Enterprise/!i$e e2iscoer)
$n SharePoint Server 2013! you can centrally mana&e e/iscovery across multi"le SharePoint farms!
E-chan&e servers! and file shares. 0rom one e/iscovery *enter! you can do the follo%in&#
*reate a case! define a (uery! and then search SharePoint Server 2013! E-chan&e Server 2013!
and file shares throu&hout the enter"rise for content that matches the (uery.
E-"ort all of the content that %as identified.
Preserve items in "lace in SharePoint Server 2013 or E-chan&e Server 2013.
Track statistics related to the case.
To im"lement e/iscovery across the enter"rise! you confi&ure SharePoint Server 2013 Search to cra%l
all file shares and %ebsites that contain discoverable content! and confi&ure the central Search service
a""lication to include results from E-chan&e Server 2013. ;ny content from SharePoint Server 2013!
E-chan&e Server 2013! or a file share or %ebsite that is inde-ed by Search or by E-chan&e Server
2013 can be discovered from the e/iscovery *enter.
See Also
Overvie% of e/iscovery and $n.Place )olds 4SharePoint 2013:
Plan for e/iscovery

19
*hat"s ne! for &obile $eices in SharePoint
2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% earn about the ne% mobile features available in SharePoint 2013! includin& the mobile
bro%ser e-"erience! device channels! and location.
-pplies to; $hare4oint >oundation ()*6 = $hare4oint $erver ()*6
SharePoint Server 2013 offers ne%! o"timi<ed vie%in& e-"eriences across different mobile "latforms.
;dditionally! several ne% features %ere added to hel" im"rove both %orker "roductivity and usability on
the device. This functionality includes the follo%in&#
O"timi<ed mobile bro%ser e-"erience 0or smart"hone mobile devices SharePoint Server 2013
"rovides a li&ht%ei&ht! contem"orary vie% bro%sin& e-"erience for users to navi&ate and access
document libraries! lists! %ikis! and ?eb Parts.
/evice channels Bou can render a sin&le "ublished SharePoint site in multi"le desi&ns to
accommodate different device tar&ets.
Push notifications ; "ush notification service on a SharePoint site can be enabled to send device
u"dates such as a tile or toast notification to a ?indo%s Phone device.
ocation SharePoint Server 2013 su""orts a ne% &eolocation field ty"e that can be used for
mobile a""lication develo"ment.
,usiness intelli&ence content *ertain devices are no% able to vie% business intelli&ence content
such as PerformancePoint ?eb Parts! E-cel Services re"orts! and SC 1e"ortin& Services re"orts.
Office ?eb ;""s Bou can vie% ?ord! E-cel! and Po%erPoint documents in mobile bro%sers %ith
additional functionality in SharePoint Server 2013.
1pti&i.e$ &obile bro!ser experience
SharePoint Server 2013 offers im"rovements to the mobile bro%ser e-"erience %ith the introduction of
a ne% contem"orary vie%. /e"endin& on the mobile bro%ser! users have one of the follo%in& bro%sin&
o"tions#
Conte&porar) ie! This vie% offers an o"timi<ed mobile bro%ser e-"erience to users and
renders in )T'D. This vie% is available to 'obile $nternet E-"lorer version K.0 or later versions for
?indo%s Phone I.D! Safari version 9.0 or later versions for iPhone iOS D.0! and the ;ndroid
bro%ser for ;ndroid 9.0 or later versions.
Classic ie! This vie% renders in )T' format! or similar marku" lan&ua&es 4*)T'! ?'! and
so on:! and "rovides back%ard com"atibility for mobile bro%sers that cannot render in the ne%
contem"orary vie%. The classic e-"erience in SharePoint 2013 is identical to the mobile bro%ser
e-"erience of SharePoint Server 2010.
1D
9#ll screen -I There is also the ability to have a full deskto" vie% of a SharePoint site on a
smart"hone device.
7ote%
The classic and contem"orary vie%s are only rendered for smart"hone mobile bro%sers. 0or
more information about these bro%sin& e-"eriences! see 'obile /evices Overvie% 4SharePoint
2013:.
2eice channels
,ro%sin& the %eb on a mobile device is no% so common that it is essential that a SharePoint site
should be o"timi<ed for readability and ease of use on smart"hones and other mobile devices such as
tablets.
Previous versions of SharePoint Server included a sin&le default mobile vie% that %as auto.&enerated
based on the e-istin& site! and that default mobile vie% %as not easily customi<able. No%! %ith mobile
channels in SharePoint Server 2013! you can render a sin&le "ublishin& site in multi"le %ays by usin&
different desi&ns that tar&et different devices. Bou create a sin&le site and author the content in it a
sin&le time. Then! that site and content can be ma""ed to use different master "a&es! "a&e layouts!
and style sheets for a s"ecific device or &rou" of devices.
P#sh notifications
SharePoint Server 2013 su""orts a""lications on mobile devices 4such as smart"hones! tablets! and so
on: that should receive notifications from a SharePoint site. Notifications can include events that occur
in the site! such as %hen a user adds an item to a list or u"dates an item. 0or mobile devices to receive
these notifications! device a""lications must re&ister %ith a SharePoint site. Once the device is
re&istered! you can %rite event handler code to interact %ith 'icrosoft Push Notification Service or
notification services of other mobile device "latforms. Notifications are sent from the server %here the
a""lication is hosted to the re&istered mobile device a""lication.
3ocation
SharePoint Server 2013 introduces a ne% &eolocation field ty"e that can be used in a list. 0or e-am"le!
you can no% make lists Elocation.a%areF and dis"lay latitude and lon&itude coordinates throu&h ,in&
'a"s. ;n entry is ty"ically seen as a "ush"in on the ma" vie%. ;lthou&h there are several %ays to use
this &eolocation field! one key scenario is for mobile a""lication develo"ment. >sers can track or lo&
location.s"ecific data %hile they %ork remotely from the cor"orate office. ;lternatively! the a""lication
can hel" them locate "oints of interest %hen it "erforms offsite functions.
0#siness intelligence content
SharePoint Server 2013 enables a user to vie% certain kinds of dashboard content. This includes
PerformancePoint re"orts and scorecards! and E-cel Services re"orts in iOS D.0 Safari bro%sers on
iPad devices.
18
1ffice *eb Apps
$n SharePoint Server 2010! Office ?eb ;""s Server "rovides bro%ser.based com"anions for ?ord!
E-cel! and Po%erPoint. ?hen Office ?eb ;""s Server is installed on SharePoint Server 2010! Office
'obile ?eb ;""s is also installed on the server. Office 'obile ?eb ;""s enables users to o"en
documents in the mobile %eb a""lication by usin& a mobile bro%ser. ?ith SharePoint Server 2013!
Office ?eb ;""s Server is no lon&er a com"anion "roduct installed on a com"uter that is runnin&
SharePoint Server. $nstead! Office ?eb ;""s Server is a ne% stand.alone server "roduct that still
"rovides mobile bro%ser.based vie%ers for these a""lications. These vie%ers called ?ord 'obile
Hie%er! E-cel 'obile Hie%er! and Po%erPoint 'obile Hie%er are o"timi<ed to render documents for
"hones. ?hen inte&rated %ith SharePoint Server 2013! a user can enAoy enhanced vie%in&
e-"eriences %hen interactin& %ith documents on the "hone.
See Also
'obile /evices Overvie% 4SharePoint 2013:

1I
*hat"s ne! in recor$s &anage&ent an$
co&pliance in SharePoint Serer 2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% earn about the ne% site.based retention feature in SharePoint Server 2013.
-pplies to; $hare4oint $erver ()*6
The records mana&ement and com"liance features in SharePoint Server 2013 "rovide im"roved %ays
to hel" you "rotect your business. The records archive and in."lace record retention from earlier
versions of SharePoint Server are still su""orted. SharePoint Server 2013 adds retention "olicies that
are a""lied at the level of a site.
Site/base$ retention
*om"liance features of SharePoint Server 2013 have been e-tended to sites. Bou can create and
mana&e retention "olicies in SharePoint Server 2013! and the "olicies %ill a""ly to SharePoint sites and
any E-chan&e Server 2013 team mailbo-es that are associated %ith the sites.
*om"liance officers create "olicies! %hich define the follo%in&#
The retention "olicy for the %hole site and the team mailbo-! if one is associated %ith the site.
?hat causes a "roAect to be closed.
?hen a "roAect should e-"ire.
?hen a "roAect be&ins! the "roAect o%ner creates a SharePoint site and an E-chan&e Server 2013
team mailbo-. The "roAect o%ner selects the a""ro"riate "olicy tem"late and invites team members to
Aoin the "roAect. ;s the team adds documents to the site! sends email messa&es! and creates other
artifacts such as lists! these items automatically receive the correct retention "olicies. ?hen the %ork is
com"leted! the "roAect o%ner closes the "roAect! %hich removes the "roAect2s folders from the team
members2 user interface in Outlook 2013. ;fter a certain time! as s"ecified by the "olicy! the "roAect
e-"ires! and the artifacts associated %ith the "roAect are deleted.
See Also
Site "olicy overvie% 4SharePoint 2013:

1J
*hat"s ne! in b#siness intelligence in
SharePoint Serer 2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% 'icrosoft "rovides com"rehensive ,$ tools that inte&rate across Office a""lications and
other 'icrosoft technolo&ies. These tools enable analysis! re"ortin&! dashboards! and visuali<ations.
-pplies to; $hare4oint $erver ()*6 0nterprise
,usiness intelli&ence 4,$: in SharePoint 2013 "rovides com"rehensive ,$ tools that inte&rate across
'icrosoft Office a""lications and other 'icrosoft technolo&ies. These ,$ tools are# E-cel 2013! E-cel
Services in SharePoint 2013! PerformancePoint Services in SharePoint Server 2013! Hisio Services in
SharePoint! SharePoint 2013! and 'icrosoft SC Server.
Excel 0I
E-cel ,$ "rovides the ca"abilities to analy<e and visually e-"lore data of any si<e! and to inte&rate and
sho% interactive solutions. $n SharePoint Server 2013! E-cel ,$ offers certain ne% features to su""ort
business intelli&ence a""lications.
These include the follo%in&#
In/Me&or) 0I Engine 4IM0I5% The $n 'emory multidimensional data analysis en&ine 4$',$:! also
kno%n as the Herti"a( en&ine! allo%s for almost instant analysis of millions of ro%s and is a fully
inte&rated feature in the E-cel client.
Po!er :ie! A$$/in for Excel% Po%er Hie% 4N*rescentN: enables users to visuali<e and interact
%ith modeled data by usin& hi&hly interactive visuali<ations! animations and smart (ueryin&.. >sers
can "resent and share insi&hts %ith others throu&h rich storyboard "resentation ca"abilities.
Po%erHie% is "o%ered by the ,$ Semantic 'odel and the HertiPa( en&ine.
2eco#ple$ PiotChart an$ PiotTable reports% >sers can no% create Pivot*hart re"orts %ithout
havin& to include a PivotTable re"ort on the same "a&e.
Excel Serices
E-cel Services enables "eo"le to vie% and interact %ith E-cel %orkbooks that have been "ublished to
SharePoint sites. >sers are able to e-"lore data and conduct analysis in a bro%ser %indo% Aust as they
%ould by usin& the E-cel client. 0or more information about E-cel Services in 'icrosoft SharePoint
Server 2010! see E-cel Services overvie% 4SharePoint Server 2010: on 'icrosoft TechNet.$n
SharePoint Server 2013! E-cel Services offers certain ne% features to su""ort business intelli&ence
a""lications. These include the follo%in&#
/ata e-"loration im"rovements# Peo"le can more easily e-"lore data and conduct analysis in E-cel
Services re"orts that use SC Server ;nalysis Services data or Po%erPivot data models. 0or
1K
e-am"le! users can "oint to a value in a Pivot*hart or PivotTable re"ort and see su&&ested %ays to
vie% additional information. >sers can also use commands such as /rill /o%n To to conduct
analysis. >sers can also a""ly the /rill /o%n command by usin& a sin&le mouse click.
0ield list and field %ell su""ort# E-cel Services enables "eo"le to easily vie% and chan&e %hich
items are dis"layed in ro%s! columns! values! and filters in Pivot*hart re"orts and PivotTable
re"orts that have been "ublished to E-cel Services.
*alculated measures and members# E-cel Services su""orts calculated measures and calculated
members that are created in E-cel.
Enhanced timeline controls# E-cel Services su""orts timeline controls that render and behave as
they do in the E-cel client.
;""lication ,$ Servers# ;dministrators can s"ecify SC Server ;nalysis Services servers to su""ort
more advanced analytic ca"abilities in E-cel Services.
,usiness $ntelli&ence *enter u"date# The ,usiness $ntelli&ence *enter site tem"late has been
streamlined. $t not only has a ne% look! it is easier to use.
Perfor&ancePoint Serices
PerformancePoint Services enables users to create interactive dashboards that dis"lay key
"erformance indicators 4+P$s: and data visuali<ations in the form of scorecards! re"orts! and filters. 0or
more information about PerformancePoint Services in SharePoint Server 2010! see PerformancePoint
Services overvie% 4SharePoint Server 2010: on 'icrosoft TechNet.$n SharePoint Server 2013!
PerformancePoint Services offers certain ne% features to su""ort business intelli&ence a""lications.
These include the follo%in&#
2ashboar$ Migration% >sers %ill be able to co"y entire dashboards and de"endencies! includin&
the .as"- file! to other users! servers! or site collections. This feature also allo%s the ability to
mi&rate sin&le items to other environments and mi&rate content by usin& ?indo%s Po%erShell
commands.
9ilter Enhance&ents ; 9ilter Search% The >$ has been enhanced to allo% users to easily vie%
and mana&e filters includin& &ivin& users the ability to search for items %ithin filters %ithout havin&
to navi&ate throu&h the tree.
0I Center -p$ate% The ne% ,$ *enter is cleaner! and easier to use %ith folders and libraries
confi&ured for easy use.
S#pport for Anal)sis Serices Effectie -ser% This ne% feature eliminates the need for +erberos
dele&ation %hen "er.user authentication is used for ;nalysis Services data sources. ,y su""ortin&
;nalysis Services Effective >ser feature! authori<ation checks %ill be based on the user s"ecified
by the Effective>serName "ro"erty instead of usin& the currently authenticated user.
Perfor&ancePoint S#pport on iPa$% PerformancePoint dashboards can no% be vie%ed and
interacted %ith on iPad devices usin& the Safari %eb bro%ser.
20
:isio Serices
Hisio Services is a service a""lication that lets users share and vie% 'icrosoft Hisio /ra%in& 4O.vsd-:
and Hisio 2010 ?eb dra%in& 4O.vd%: files. The service also enables data.connected Hisio /ra%in&
4O.vsd-: and Hisio 2010 ?eb dra%in& 4O.vd%: files.to be refreshed and u"dated from various data
sources.
Maxi&#& Cache Si.e% ; ne% service "arameter! it is located on the *entral ;dmininstration Hisio
3ra"hics Service ;""lication 3lobal Settin&s "a&e. The default value is D120 ',.
<ealth Anal).er r#les% Ne% corres"ondin& )ealth ;naly<er rules have been added to reflect the
ne% 'a-imum *ache Si<e "arameter.
-p$ate$ *in$o!s Po!erShell c&$lets( Set/SP:isioPerfor&ance% This cmdlet has been
u"dated to include the ne% 'a-imum *ache Si<e "arameter.
Co&&enting on $ra!ings s#pporte$% >sers can add meanin&ful comments to a Hisio /ra%in&
4O.vsd-: collaboratively on the %eb via Hisio Services in full "a&e renderin& mode.

21
*hat"s ne! in social co&p#ting in SharePoint
Serer 2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% earn about ne% features and functionality for social com"utin&! such as 'y Sites! feeds!
*ommunity Sites! and *ommunity Portals.
-pplies to; $hare4oint $erver ()*6
The social com"utin& and collaboration features in SharePoint Server 2013 offer an im"roved
administration and user e-"erience! in addition to ne% functionality for enter"rise users to share and
collaborate %ith others in their or&ani<ation.
The introduction of *ommunity Sites offers a forum e-"erience to cate&ori<e discussions around
subAect areas! and connect users %ho have kno%led&e or seek kno%led&e about subAect areas.
$m"rovements to 'y Sites offer a more intuitive %orkflo% for users to develo" their "ersonal "rofiles!
store content! and kee" u".to.date %ith activities of interest.
:i$eo% Social co&p#ting oerie! !ith 0ill 0aer
4htt"#55%%%.microsoft.com5resources5technet5en.us5office5media5video5video.html6
cid7stcPfrom7mscomST*PHideo$/70K9dcDb0.8902.93aa.KK2I.1JII03DIabDd:

$n this article#
*ommunities
'y Sites
Co&&#nities
$n SharePoint Server 2010 and SharePoint 0oundation 2010! you could add a /iscussion list to sites to
facilitate discussions amon& members of the site. SharePoint Server 2013 and SharePoint 0oundation
2013 continue to "rovide this /iscussion list! but also e-"and on the discussion conce"t by introducin&
t%o ne% site tem"lates named ,ommunit! $ite and ,ommunit! 4ortal.
*ommunity Sites offer a forum e-"erience to cate&ori<e and cultivate discussions %ith a broad &rou" of
"eo"le across or&ani<ations in a com"any. *ommunity Sites "romote o"en communication and
information e-chan&e by fosterin& discussions amon& users %ho share their e-"ertise and use
e-"ertise of others %ho have kno%led&e in s"ecific areas of interest.
?ith *ommunity Sites! you or&ani<e discussions in cate&ories. Hisitors can vie% the discussions and
become members if they %ant to contribute to those discussions. 'oderators mana&e the community
22
by settin& rules! revie%in& and addressin& ina""ro"riate "osts! markin& interestin& content as featured
discussions! and so on. 'oderators can also assi&n &ifted bad&es to s"ecific members to visually
indicate that the member is reco&ni<ed as a s"ecific kind of contributor in the *ommunity Site! such as
an e-"ert or a moderator. Each *ommunity Site contains information about member and content
re"utation! %hich members earn %hen they actively "ost in discussions! and %hen their content is liked!
re"lied to! or marked as a best ans%er.
Bou can de"loy *ommunity Sites or use community features in the follo%in& %ays#
0) $eplo)ing a stan$/alone co&&#nit) ?ith a stand.alone community! you can create the
*ommunity Site at either a site collection or a site level. 0or e-am"le! you mi&ht create a
community in a divisional "ortal if you %ant to facilitate discussions amon& members of the division
and use the community cate&ories to kee" thin&s or&ani<ed.
0) actiating co&&#nit) feat#res Bou can activate community features on any site! %hich
"rovides the core *ommunity Site "a&es! moderation! membershi"! and re"utation functionality
%ithin the e-istin& site %ithout creatin& a se"arate *ommunity Site. This o"tion is useful %hen you
already have a site! such as a team site! %here you %ant to include community functionality! such
as earnin& re"utations! %ithout havin& to direct users to a se"arate site.
;dditionally! %hen you have multi"le *ommunity Sites that you %ant to dis"lay to users in your
enter"rise! you can de"loy the *ommunity Portal. The *ommunity Portal is a search.driven "a&e that
surfaces SharePoint site collections and sites in the SharePoint farm that use the *ommunity Site
tem"late. >sers can visit the *ommunity Portal to discover "o"ular communities and to search for
communities that they mi&ht %ant to Aoin. The *ommunity Portal relies on enter"rise search for security
trimmin&! and dis"lays only *ommunity Sites for %hich a user has at least read "ermissions.
0or more information about communities! see *ommunities overvie% 4SharePoint 2013:! Plan for
*ommunities 4SharePoint 2013:! and Setu" and confi&ure *ommunities 4SharePoint 2013:.
M) Sites
$n SharePoint Server 2010! 'y Sites "rovided a central "lace for users to store "ersonal and shared
documents! in addition to "romotin& their user information and e-"ertise! ta&&in& content! and
communicatin& %ith others by usin& the Note ,oard. Throu&h "eo"le search! users %ere able to
connect %ith one another and benefit from e-"ertise of others in their or&ani<ation.
$n SharePoint Server 2013! 'y Sites continue to "rovide the benefits from the "revious release.
)o%ever! the user interface is com"letely redesi&ned and moderni<ed to &ive users an invitin& and
intuitive e-"erience. ; key chan&e to the user interface includes a sim"lified and unified navi&ation
e-"erience for your o%n and others= 'y Sites. ;dditionally! 'y Sites contain the ne% 'icroblo& and
Ne%sfeeds features. These features allo% users to en&a&e in short! "ublic conversations! and kee" u".
to.date on activities from content and "eo"le in %hich they are interested.
This section discusses im"rovements and ne% functionality to the follo%in& areas of 'y Sites#
'y Site document libraries
'icroblo&&in& and feeds
/e"loyment and confi&uration
23
*entral ;dministration chan&es
M) Site $oc#&ent libraries
$n SharePoint Server 2010! each 'y Site contained t%o document libraries# "ersonal and shared. $tems
stored in the "ersonal document library %ere restricted to the 'y Site o%ner! and items in the shared
document library %ere shared %ith everyone.
$n SharePoint Server 2013! 'y Sites include several im"rovements to savin&! synchroni<ation! sharin&!
and movin& of content. These im"rovements make 'y Sites a more robust solution for users to store
and %ork %ith files in the SharePoint environment.
Saing an$ s)nchroni.ing content
?hen de"loyed! a user=s 'y Site document library is the default save location for files saved from
Office 2013 client a""lications. ; discovery service identifies the user=s 'y Site >1 and offers it as the
default location in addition to other locations available for savin& files. This "romotes the %orkflo% of
storin& files in the user=s 'y Site document library %here items can be mana&ed! &overned! shared!
and moved. This hel"s reduce the amount of content that is stored in other systems! such as in email or
on "ersonal drives.
7ote%
$n test environments %here users have more than one 'y Site! the discovery service is unable
to determine the default 'y Site location to use for savin& files.
>sers have the o"tion to synchroni<e their 'y Site document library content %ith a local drive to enable
offline access to documents. This o"tion encoura&es the use of the 'y Site document library for
stora&e instead of the users= local drives because it offers fle-ibility for users to %ork %ith documents in
both online and offline scenarios.
Sharing content
SharePoint Server 2013 introduces the conce"t of sharin& for all document libraries. This conce"t is
levera&ed by the 'y Site document library to ease the "rocess of collaboratin& %ith other users on
content. Sharin& is based on the same "ermissions infrastructure as SharePoint Server 2010! but
sim"lifies and im"roves the user e-"erience. ,y usin& this sim"lified e-"erience! users can s"ecify
"ermissions for a s"ecific document %ithout havin& to understand the inheritance model.
,y default! all content that is stored in a user=s 'y Site document library is restricted to the user! and
other users cannot see content unless it is shared %ith them. $f the user %ants others to collaborate on
a "iece of content in that library! the user can share the content %ith s"ecific users or &rou"s! and
select the "ermission those users or &rou"s have to the content.
Even thou&h the sharin& "rocess is available to all document libraries in SharePoint Server 2013! 'y
Sites include a sharin& hint! %hich dis"lays all the users and the "ermissions for a s"ecific "iece of
content. This makes it easier for users to see at a &lance %hat they are sharin& and %ith %hom.
29
Microblogging an$ fee$s
$n SharePoint Server 2013! the Ne%sfeed "a&e in the 'y Site continues to "rovide an a&&re&ated vie%
of activities from content and "eo"le the user is follo%in&. )o%ever! the feed is im"roved %ith ne%
microblo&&in& functionality that enables users to do the follo%in&#
Partici"ate in conversations by "ostin& comments and re"lies.
Post "ictures and links.
>se ta&s 4startin& %ith the Q symbol: to define key%ords that users can follo% and search for.
>se mentions 4startin& %ith the R symbol: to ta& users in "osts and re"lies.
$ndicate a&reement %ith comments and re"lies by clickin& ike.
0ollo% "eo"le! documents! sites! and ta&s to customi<e their feed.
$n SharePoint Server 2013! a ne% in.memory cache kno%n as the /istributed *ache 4%hich uses
;""0abric for ?indo%s Server: maintains the Ne%sfeed. ;""0abric is installed and confi&ured as "art
of the SharePoint Server 2013 "rere(uisites. 0or more information about SharePoint Server 2013
"rere(uisites! see Pre"are for installation 4SharePoint 2013:.
This feeds infrastructure better su""orts the read and %rite o"erations &enerated by users= activities
and "artici"ation in microblo&&in&. The feeds ;P$ is e-tensible! %hich enables scenarios %here
activities can be added to the ne%sfeed or consumed by other a""lications "ro&rammatically. 0or
e-am"le! you mi&ht develo" a ne% a""lication for users to check in to locations! such as a buildin&! and
broadcast their check.ins to their feed by usin& the feeds ;P$.
$n SharePoint Server 2013! each 'y Site re(uires a document library for microblo&&in& and feeds. This
document library contains a microblo&&in& list that maintains all of a user=s "osts instead of maintainin&
them in the 'y Site )ost site collection as in SharePoint Server 2010. This means that activities are
"ersisted indefinitely and no lon&er limited to 19 days as in SharePoint Server 2010. The Ne%sfeed
"a&e dis"lays the a&&re&ated vie% of recent activities that are maintained in the cache! %hereas the
user=s "rofile "a&e dis"lays all activities maintained in the user=s microblo&&in& list.
2eplo)&ent an$ config#ration
The "lannin&! de"loyment! and confi&uration ste"s for 'y Sites are much the same as in SharePoint
Server 2010. 0or more information! see Plan for social com"utin& and collaboration 4SharePoint 2013:
and >ser Profile Service administration 4SharePoint 2013:.
This section describes the considerations for u"&radin& 'y Sites from SharePoint Server 2010! and
ne% and u"dated settin&s for 'y Sites in SharePoint Server 2013.
-pgra$e consi$erations
$f you u"&rade from SharePoint Server 2010 to SharePoint Server 2013! there are s"ecial
considerations for 'y Sites. 'ake sure that you u"&rade the 'y Site )ost site collection before you
allo% users to u"&rade their individual 'y Sites in SharePoint Server 2013. This ensures that the server
soft%are and database chan&es are com"lete so that users can start the u"&rade of their individual 'y
Sites successfully. >"&rade of a s"ecific 'y Site occurs the first time that a user o"ens an individual 'y
Site. ;n u"&rade re(uest is (ueued until the 'y Site u"&rade is com"leted. ?hile the u"&rade re(uest
2D
is in the (ueue! users can continue to use their 'y Sites thou&h the sites %ill a""ear as they did in
SharePoint Server 2010 until the u"&rade is com"leted. 0ollo%in& u"&rade! users see the ne% user
interface the ne-t time that they visit their 'y Site.
Central A$&inistration changes
SharePoint Server 2013 includes several chan&es to the >ser Profile service a""lication settin&s in
*entral ;dministration to su""ort ne% 'y Sites functionality.
Config#re per&issions for personal an$ social feat#res
The 'ana&e >ser Permissions "a&e contains ne% and u"dated settin&s for the >ser Profile service
a""lication. Bou can select one or more of the follo%in& "ermissions for users and &rou"s that you %ant
to &rant "ermission to "ersonal and social features#
Create Personal Site 4re=#ire$ for personal storage( ne!sfee$( an$ follo!e$ content5 This
"ermission enables users to create "ersonal sites to store their documents! ne%sfeed! and follo%ed
content.
9ollo! People an$ E$it Profile This "ermission enables users to follo% "eo"le from their 'y Site
and to edit their "ersonal "rofile.
-se Tags an$ 7otes This "ermission enables users to use the Ta&s and Notes feature from
SharePoint Server 2010. The Ta&s and Notes feature is "rovided "rimarily for u"&rade "ur"oses so
that users can continue to access the ta&s and notes they created in the "revious version of
SharePoint Server. )o%ever! you mi&ht also use this "ermission to enable users to leave notes on
documents in SharePoint Server 2013.
Config#re &icroblogging an$ follo!ing settings
*entral ;dministration contains ne% settin&s for >ser Profile service a""lication administrators to
confi&ure microblo&&in& and follo%in& activities#
Enable &icroblogging e/&ail notifications On the Set#p M) Sites "a&e! under E/&ail
7otifications! select Enable ne!sfee$ e&ail notifications if you %ant users to receive email
notifications that relate to their microblo&&in& activities.
Manage 9ollo!ing page On the >ser Profile service a""lication administration "a&e! under M)
Site Settings! click Manage 9ollo!ing. 0rom the Manage 9ollo!ing "a&e! you can confi&ure
limits for the number of "eo"le! documents! and sites that users can follo% from their 'y Site.
Config#re policies for priac) an$ people
*entral ;dministration contains ne% "olicy settin&s for the >ser Profile service a""lication and 'y
Sites. These settin&s a""ear on the 'ana&e Policies "a&e of the >ser Profile service a""lication. There
are t%o ne% sections that dis"lay "rivacy and "eo"le settin&s. Bou can select a s"ecific "olicy to
chan&e %hether the "olicy is enabled! the default "rivacy settin& for users! and %hether users can
override the settin& from their o%n "rofiles. $n SharePoint Server 2013! the /efault Privacy Settin& for
28
"olicies contains only t%o settin&s# 1nl) Me and Eer)one. The additional settin&s from SharePoint
Server 2010 of M) Manager! M) Tea&! and M) Colleag#es are removed. Settin& a "olicy to 1nl) Me
sets the default behavior for feed events to off! %hereas settin& it to Eer)one turns it on. $f you allo%
users to override the settin&! they can choose %hether to chan&e the default behavior on their individual
"rofiles.
The follo%in& are ne% settin&s under Privacy Settin&s#
0ollo%in& a /ocument or Site on 'y Site
Ta&&in& an $tem on 'y Site
?ork"lace anniversary on 'y Site
0ollo%in& a Ta& on 'y Site
>"datin& E;sk 'e ;boutF on 'y Site
1atin& an $tem on 'y Site
0ollo%in& a Person on 'y Site
Postin& on a Note ,oard on 'y Site
@ob Title *han&e on 'y Site
Postin& a ne% blo& "ost on 'y Site
,irthday *elebration on 'y Site
The follo%in& are u"dated settin&s under Peo"le Settin&s#
Peo"le on 'y Site
;uto.follo% "eo"le from team
Peo"le 1ecommendations
7ote%
These Peo"le Settin&s e-isted in SharePoint Server 2010 under the 'y *ollea&ues section!
but they are renamed in SharePoint Server 2013 because the conce"t of collea&ues is no%
chan&ed to "eo"le. ;dditionally! the People on M) Site settin& no% defines the default "rivacy
settin& for all "eo"le a user follo%s! instead of individual "rivacy settin&s. This means that %hen
you set the "rivacy settin& to Eer)one! everyone %ho accesses a user=s "rofile can see the
"eo"le %hom that user follo%s.
7ote%
'y Sites are "rivate by default. There is a "rivacy settin& named Ma>e M) Sites P#blic that an
administrator can use to make all users2 'y Sites "ublic by default. The Ma>e M) Sites P#blic
settin& is located in the >ser Profile service a""lication under Set#p M) Sites. Even if an
administrator confi&ures any of these "olicy settin&s! these "olicy settin&s are overridden if the
Ma>e M) Sites P#blic settin& is selected.
See Also
*ommunities overvie% 4SharePoint 2013:
Plan for *ommunities 4SharePoint 2013:
2I
Setu" and confi&ure *ommunities 4SharePoint 2013:
Plan for 'y Sites 4SharePoint 2013:
Set u" 'y Sites 4SharePoint 2013:
'icroblo&&in& overvie% 4SharePoint 2013:
Plan for feeds and the /istributed *ache service 4SharePoint 2013:

2J
*hat"s ne! in !eb content &anage&ent for
SharePoint 2013 p#blishing sites
P#blishe$% +#l) 1,( 2012
S#&&ar)% earn about %eb content mana&ement features for buildin& $nternet! intranet! and e-tranet
SharePoint "ublishin& sites.
-pplies to; $hare4oint $erver ()*6
SharePoint Server 2013 includes ne% and im"roved features for %eb content mana&ement that sim"lify
ho% you desi&n "ublishin& sites and enhance the authorin& and "ublishin& "rocesses of your
or&ani<ation. SharePoint Server 2013 also has ne% features that use the "o%er of search to surface
dynamic %eb content on "ublishin& sites.
Content a#thoring i&proe&ents
*ontent authors have a better e-"erience in SharePoint Server 2013. *ontent authors can no% co"y
content from ?ord! "aste it directly into a 1ich Te-t Editor ?eb Part! *ontent Editor ?eb Part! or an
)T' field control on a "a&e! and have the resultin& semantically correct )T' marku" dis"lay in the
styles that %ere defined by the site desi&ner. Site o%ners and desi&ners can no% customi<e the &lobal
and current navi&ation menus by dra&&in& and dro""in& menu items directly on the "a&e.
SharePoint Server 2013 adds many ne% features for videos and usin& videos on "a&es. ; ne% video
content ty"e is added! and the video u"load "rocess is im"roved for content authors. Thumbnail
"revie% ima&es are created automatically %hen a video is u"loaded to an asset library! and content
authors can choose a frame from the video and use that as the thumbnail "revie% ima&e. 0or automatic
thumbnail creation to %ork! the /eskto" E-"erience feature must be installed on the front.end %eb
server that hosts SharePoint Server 2013. 0or information about the /eskto" E-"erience feature! see
/eskto" E-"erience Overvie%.
$n SharePoint Server 2013! content authors can insert an iframe element into an )T' field on a "a&e.
This lets content authors embed dynamic content from other sites! such as videos or ma" directions. ,y
default! certain trusted e-ternal domains are already a""roved for use in iframes. Site collection
administrators can customi<e the field security settin&s by chan&in& the default trusted e-ternal
domains. They can also allo% content authors to insert iframes for any e-ternal domain! or "revent
them from insertin& iframes on any "a&e. To chan&e the field security settin&s for a site collection! click
<TM3 9iel$ Sec#rit) on the Site Settin&s "a&e.
0inally! SharePoint Server 2013 su""orts image renditions. $ma&e renditions let you dis"lay different
si<ed versions of an ima&e on different "a&es. ?hen you create an ima&e rendition! you s"ecify the
%idth and hei&ht for all ima&es that use that ima&e rendition. 0or e-am"le! if the site has a ne%s article
"a&e layout that contains an ima&e field! you can create an ima&e rendition named ;rticleSima&e to
dis"lay the full.si<ed ima&e in the article "a&e. ; second ima&e rendition named ThumbnailSsmall can
be used to dis"lay a smaller version of the ima&e associated %ith a "articular article %hen the ima&e is
dis"layed in a ?eb Part that lists all recent ne%s articles on the site home "a&e. To use ima&e
2K
renditions! you first define the ima&e rendition si<es. Ne-t! you &enerate the default ima&e "revie% by
u"loadin& an ima&e! %hich you can adAust if it is necessary. 0inally! you add the ima&e to a "a&e and
s"ecify %hich ima&e rendition to use on that "a&e.
,y default! the ima&e "revie% that is dis"layed for an ima&e rendition is &enerated from the center of
the ima&e. Bou can adAust the ima&e "revie% for individual ima&es by selectin& and resi<in& the "ortion
of the ima&e that you %ant to use as the ima&e "revie%. 0or e-am"le! if a "hoto contains a "erson=s
face but the default ima&e "revie% does not sho% the %hole face! you can chan&e the selected ima&e
area so that the %hole face is dis"layed.
$ma&e renditions let you have lar&e source ima&es on the site and also have "laces on the site %here
"a&es only use smaller versions. This reduces the si<e of the file that is do%nloaded to the client! %hich
im"roves site "erformance. $ma&e renditions also let you have multi"le versions of the same ima&e that
are cro""ed differently %ithout havin& to u"load multi"le ima&es. This reduces the stora&e s"ace that is
re(uired for ima&es. 0inally! ima&e renditions are useful in mobile scenarios! %here different versions of
ima&es can be dis"layed based on the device that is used.
I&portant%
,efore you can use ima&e renditions! you must enable the ,O, cache. 0or information about
ho% to enable the ,O, cache! see N*onfi&urin& ,O, cache settin&sN in *onfi&ure cache
settin&s for a ?eb a""lication 4SharePoint Server 2010:.
To use ima&e renditions! click I&age Ren$itions on the Site Settin&s "a&e. Bou define an ima&e
rendition by s"ecifyin& a name! such as ThumbnailSsmall! and the %idth and hei&ht in "i-els for that
ima&e rendition. Bou can create as many ima&e renditions as you %ant for your site desi&n. To use an
ima&e rendition for a s"ecific ima&e on a "a&e! you add an ima&e to a "a&e as you ty"ically %ould.
?hen you add an ima&e to a "a&e! the Edit $ma&e Pro"erties "a&e dis"lays a list of ima&e renditions
that you can a""ly. The ima&e is then dis"layed on the "a&e usin& the dimensions s"ecified in the
selected ima&e rendition.
Bou can also use ima&e renditions on a "a&e by s"ecifyin& a value in the Ren$itionI2 "ro"erty for an
ima&e field control on a "a&e layout! or by usin& a >1 that has the Ren$itionI2 "arameter to "oint
directly to the version of the ima&e that you %ant to use. The rendition $/ is dis"layed on the $ma&e
1enditions settin&s "a&e for a site collection or site. ;fter you create an ima&e rendition! you can
"rovide a list of available rendition $/s to content authors so they al%ays kno% %hat value to use for the
Ren$itionI2 in field controls or as a "arameter in a >1. 0or e-am"le! if the ima&e rendition named
ThumbnailSsmall has Ren$itionI2 2! you can &ive that information to content authors so that they
al%ays use Ren$itionI2 2 any%here they %ant to insert a small thumbnail of an ima&e.
Bou can also use the follo%in& alternative methods to s"ecify the Ren$itionI2#
To s"ecify the Ren$itionI2 "ro"erty in the ima&e field control! enter the numeric $/ that
corres"onds to the rendition that you %ant to use %hen an ima&e is inserted into that field control
durin& "a&e editin&.
To s"ecify the Ren$itionI2 "arameter in the >1! add N61endition$d7nN to the ima&e >1! %here n
is the 1endition$/. 0or e-am"le! the >1 htt"#55contoso.com5$ma&es5myima&e.A"&61endition$d72
%ill load the ima&e rendition %ith $/ 2 for the ima&e file myima&e.A"&.
30
:ariations for &#ltiling#al sites
$n SharePoint Server 2013! the variations feature is used e-clusively for multilin&ual sites. The
variations feature makes content available to s"ecific audiences on different sites by co"yin& content
from a source variation site to one or more tar&et variation sites! and trackin& relationshi"s bet%een
source and tar&et content. >sers %ho visit the site are redirected to the a""ro"riate variation site based
on the lan&ua&e settin& of their %eb bro%ser.
SharePoint Server 2013 no% has an inte&rated translation service that lets content authors select
content for e-"ort for human translation or s"ecify content for machine translation. Translated content
can also be used across multi"le site collections by usin& cross.site "ublishin&. 0or information about
cross.site "ublishin&! see *ross.site "ublishin& later in this article.
,y usin& SharePoint Server 2013! content authors can nominate lists on source variation sites to be
"ro"a&ated to tar&et variation sites. ist items such as documents! ima&es! or announcements
"ro"a&ate inde"endently from "a&es. 0or e-am"le! if you have a "a&e that links to a document! and
you chan&e only the document! the document %ill be "ro"a&ated to the tar&et variation site %ithout the
user havin& to re"ublish the "a&e that references the document.
$n SharePoint Server 2013! additional chan&es %ere made to the variations feature to im"rove
"erformance! such as enablin& bulk e-"ort of "a&es. o&&in& functionality is u"dated to im"rove the
usefulness of error messa&es! and lo&s can no% be e-"orted to E-cel.
7ote%
$n SharePoint Server 2010! you could use variations to make content available to audiences
based on lan&ua&e! country and re&ion! mobile device! or cor"orate brandin& needs. $n
SharePoint Server 2013! you use cross.site "ublishin& to make content available to users in a
sin&le lan&ua&e! or if you %ant to brand the same content %ith different cor"orate brandin&
re(uirements. $f you %ant to make content available to users on multi"le mobile devices! use
mobile channels and device.s"ecific tar&etin&. 0or information about cross.site "ublishin&! see
*ross.site "ublishin& later in this article. 0or information about ho% to desi&n mobile channels!
see ?hat=s ne% %ith brandin& sites in SharePoint Server 2013
4htt"#55&o.microsoft.com5f%link5"56ink$d72DD0D8:.
Cross/site p#blishing
*ross.site "ublishin& lets you store and maintain content in one or more authorin& site collections! and
dis"lay this content in one or more "ublishin& site collections. ?hen you chan&e the content in an
authorin& site collection! those chan&es are dis"layed on all site collections that are reusin& this
content.
*ross.site "ublishin& uses search technolo&y to retrieve content. On a site collection %here the *ross.
Site *ollection Publishin& feature is enabled! libraries and lists have to be enabled as catalo&s before
the content can be reused in other site collections. 0or more information! see *atalo&.enabled libraries
and lists. The content of the library or list catalo&s must be cra%led and added to the search inde-. The
content can then be dis"layed in a "ublishin& site collection by usin& one or more *ontent Search ?eb
Parts. 0or more information! see *ontent Search ?eb Part. The follo%in& illustration sho%s ho%
31
content is stored in libraries and lists in an authorin& site collection! and then reused across three
se"arate "ublishin& site collections by usin& *ontent Search ?eb Parts.

Catalog/enable$ libraries an$ lists
SharePoint Server 2013 has added the ability to desi&nate any library or list as a catalo&. ;fter the
*ross.Site *ollection Publishin& feature is enabled for a site collection! you can desi&nate any library or
list %ithin that site collection as a catalo& so that content can be reused on "ublishin& site collections.
Bou can use catalo&.enabled libraries or lists for scenarios such as an article library! kno%led&e base
library! or "roduct catalo&. 0or e-am"le! in an $nternet business scenario %here a com"any is sellin&
32
electronic "roducts such as THs and radios! the com"any can use one or more lists that are enabled as
catalo&s to share "roduct information such as brand! color! and si<e as it a""lies to each "roduct. ,y
usin& cross.site "ublishin&! this information can then be dis"layed in one or more "ublishin& site
collections.
;nother e-am"le is an intranet scenario! %here all kno%led&e base articles created in an or&ani<ation
can be %ritten and stored in one or more libraries that are enabled as catalo&s in a content site
collection. ,y usin& cross.site "ublishin&! different combinations of these kno%led&e base articles can
be dis"layed on one or more "ublishin& site collections G for e-am"le! based on ho% relevant the
articles are for the different de"artments in the or&ani<ation.
SharePoint Server 2013 includes a ne% "ublishin& site collection tem"late! the Product *atalo& Site
*ollection! desi&ned to author! store and maintain data that is used in a catalo& scenario. ,y default!
the *ross.Site *ollection Publishin& feature is automatically enabled in the Product *atalo& Site
*ollection. )o%ever! you must still confi&ure the catalo& settin&s to share content %ith other site
collections! Aust as you %ould %ith any other library or list.
?hen you connect a library or list that is enabled as a catalo& to a "ublishin& site collection! a result
source is automatically created for this library or list. ; result source narro%s the sco"e from %hich the
search results can be retrieved. That is! the result source created for a library or list is limited to content
%ithin this library or list. 0or e-am"le! you can use the automatically &enerated result source to limit a
(uery in a *ontent Search ?eb Part. Bou can also co"y a result source or chan&e it to s"ecify an even
narro%er search result sco"e.
Manage$ naigation
'ana&ed navi&ation lets you define and maintain the navi&ation on a site by usin& term sets. 'ana&ed
navi&ation su""lements the e-istin& SharePoint navi&ation that is based on site structure. Bou create
the mana&ed navi&ation structure by addin& terms to term sets in the Term Store 'ana&ement tool. Bou
can co"y the navi&ation term set and translate it into the same lan&ua&es that are used for variations
labels. 0or more information about terms and term sets! see 'ana&ed metadata overvie% 4SharePoint
Server 2010:.
Bou can combine "ortions of term sets from different site collections to create the navi&ation of a
%ebsite. This can be valuable in an $nternet business scenario in %hich you have a catalo& of "roducts.
This is because you can use one term set for the navi&ation %ithin "roduct "a&es! and another term set
for the navi&ation %ithin non."roduct "a&es. To&ether! these term sets form the navi&ation for the %hole
site. 0or e-am"le#
$n an authorin& site collection! you create a term set for the navi&ation of the "roduct "a&es. ; term
%ithin this term set ty"ically re"resents a "roduct cate&ory G for e-am"le! ;udio! *ameras! or
*om"uters.
$n the "ublishin& site collection! you create a term set for the navi&ation of the non."roduct catalo&
"a&es. ; term %ithin this term set usually re"resents "a&es G for e-am"le! )ome! ;bout! or
*areers.
,y usin& cross.site "ublishin& to dis"lay content from the authorin& site collection in the "ublishin&
site collection! you can combine the terms from the t%o site collections to create the com"lete
%ebsite navi&ation G in this e-am"le! )ome! ;udio! *ameras! *om"uters! ;bout! and *areers.
33
Categor) pages
,ategor! pages are "a&e layouts that are used for dis"layin& structured content such as catalo& data.
Bou can use cate&ory "a&es %hen you %ant to a&&re&ate content that meets certain criteria or
"arameters. 0or e-am"le! in an intranet scenario! all com"any events are maintained in a list that is
shared as a catalo&. Bou %ant the information about each event to a""ear in the same manner G for
e-am"le! %ith a title in bold! follo%ed by information about %hen and %here the event occurs. To avoid
havin& to create one "a&e for each event! you can create some cate&ory "a&es that can be used to
dis"lay all events in the same manner.
*ate&ory "a&es are closely tied to mana&ed navi&ation. This is because you can associate a cate&ory
"a&e %ith a s"ecific term %ithin the term set that is used for mana&ed navi&ation. 0or e-am"le! in the
com"any events scenario that %as described earlier! you can have a term set in %hich the different
de"artments are used for mana&ed navi&ation. Bou can use t%o se"arate cate&ory "a&e tem"lates to
dis"lay the different events. *ate&ory "a&e 1 can be used to dis"lay all events related to the 'arketin&
de"artment! and *ate&ory "a&e 2 can be used to dis"lay all events related to the )uman 1esources
de"artment.
9rien$l) -R3s
,y usin& mana&ed navi&ation and cate&ory "a&es! the >1s of cate&ory "a&es can be built from the
terms that you have s"ecified in the term set! such as *om"uters or 'arketin&. 0or individual catalo&
items! you can s"ecify that the >1 consists of additional "ro"erties from the library or list that is shared
as a catalo&. This lets you create more meanin&ful! user.friendly >1s! instead of havin& >1s that
consist of strin&s that do not make sense to users. $n SharePoint Server 2010! the >1s for "ublishin&
sites included the name of the Pa&es library G for e-am"le!
htt"#55%%%.contoso.com5Pa&es5*om"uters.as"-Q5$/79D3PSource7htt"T3;T201010101. $n
SharePoint Server 2013! you can create >1s that are more user.friendly G for e-am"le
htt"#55%%%.contoso.com5*om"uters5model101.
Content Search *eb Part
SharePoint Server 2013 has added a ne% *ontent Search ?eb Part that dis"lays content that %as
cra%led and added to the search inde-. To dis"lay content in the *ontent Search ?eb Part! you s"ecify
a (uery in the ?eb Part. This (uery is automatically issued! and it returns results from the search inde-
%hen users bro%se to a "a&e that contains the *ontent Search ?eb Part. The *ontent Search ?eb
Part is es"ecially "o%erful %hen it is used in combination %ith mana&ed navi&ation and cate&ory "a&es.
0or e-am"le! in an $nternet business scenario %here a "roduct catalo& is dis"layed! a term %ithin the
term set s"ecified for mana&ed navi&ation is associated %ith a s"ecific cate&ory "a&e! as described
earlier in *ate&ory "a&es. Bou can s"ecify that a (uery in a *ontent Search ?eb Part on a cate&ory
"a&e use the current navi&ation cate&ory as "art of the (uery. 0or e-am"le! %hen users bro%se to a
cate&ory! such as *om"uters! a (uery is issued from the *ontent Search ?eb Part to return all items
from the search inde- that are s"ecified as *om"uters. Similarly! %hen users bro%se to the cate&ory
;udio! the same *ontent Search ?eb Part on the same cate&ory "a&e %ill dis"lay items in the search
inde- that are s"ecified as ;udio.
39
Refiners an$ facete$ naigation
1efiners are based on mana&ed "ro"erties from the search inde-. 'ana&ed "ro"erties re"resent the
s"ecifications of the items in the catalo&.enabled library or list G for e-am"le! ;uthor! /ate! *olor! or
Product *ate&ory. $n a catalo& scenario! you can add a 1efinement Panel ?eb Part to a cate&ory "a&e
so that users can narro% the content as they bro%se throu&h different "a&es. 0or e-am"le! in an
$nternet business scenario in %hich a catalo& of mobile tele"hones is dis"layed! the mana&ed "ro"erty
*olor is set as a refiner. ?hen a user vie%s all mobile tele"hones in the catalo&! all available colors are
dis"layed in the 1efinement Panel ?eb Part. ?hen a user clicks a s"ecific color! such as 3ray! only
mobile tele"hones %ith the color 3ray are dis"layed. Similarly! in the scenario in %hich com"any events
are dis"layed! the mana&ed "ro"erty /ate is set as a refiner. $n the 1efinement Panel ?eb Part! users
can see for %hich dates events are scheduled. ?hen they click a "articular date! they refine the results
so that only events scheduled to occur on that date a""ear.
,y usin& faceted navigation! you can confi&ure different refiners for different terms in a term set. 0or
e-am"le! in an $nternet business scenario in %hich a "roduct catalo& is dis"layed! you can set the
mana&ed "ro"erty Screen si<e as refiner for the term *om"uter! and the mana&ed "ro"erty 'e&a"i-els
as refiner for the term *ameras. The faceted navi&ation &uides users to content that is relevant for each
s"ecific cate&ory! and makes it easier and faster to bro%se throu&h catalo& content.
Anal)tics an$ reco&&en$ations
The ne% ;nalytics Processin& *om"onent in SharePoint Server 2013 runs different analytics Aobs to
analy<e content in the search inde- and user actions that %ere "erformed on a site to identify items that
users "erceive as more relevant than others.
The ne% functionality for dis"layin& content recommendations based on usa&e "atterns uses the
information from the analyses. ,y includin& recommendations on a "a&e! you can &uide users to other
content that may be relevant for them. 0or e-am"le! you can &uide users to "o"ular items in a cate&ory
or let them kno% that users %ho vie%ed this item also vie%ed another item.
The search recommendations frame%ork %orks in the follo%in& %ay#
-ser actions pro$#ce #sage eents? ?hen users interact %ith a SharePoint Server 2013
%ebsite G for e-am"le! %hen they click a link! "ress a button! or vie% a document G their actions
are stored as usa&e events.
-sage eents are co#nte$ an$ anal).e$? The recommendations al&orithm in the ;nalytics
Processin& *om"onent counts and analy<es the usa&e events.
Infor&ation is a$$e$ to the in$ex?
;fter "rocessin& in the ;nalytics Processin& *om"onent! the information is added to the search
inde- and the 1e"ortin& database.
Bou can use search recommendations to do the follo%in&#
A$$ Reco&&en$e$ Ite&s an$ Pop#lar Ite&s *eb Parts to a site? $n SharePoint Server 2013!
you can dis"lay recommendations on a site by addin& one or more 1ecommended $tems ?eb
Parts. Bou can confi&ure the ?eb Part to dis"lay recommendations for the document or item that a
3D
user is vie%in&. 0or e-am"le! these recommendations can be dis"layed under the headin& Users
who viewed this document also viewed.
Bou can use the Po"ular $tems ?eb Part to dis"lay the most "o"ular items that satisfy a set of
criteria. 0or e-am"le! these recommendations can be dis"layed under the headin& &ost popular
items in this categor!.
Get insights thro#gh reports? $nformation about usa&e events is dis"layed in E-cel re"orts. Bou
can use the re"orts to vie% user statistics to understand the traffic "attern on a %ebsite.
Act on insights? ,ased on the information in the re"orts! you can make decisions about ho% to
fine.tune the %ebsite.
Monitor changes? The re"orts are u"dated based on the chan&es that are made! and you can
monitor the effect of the chan&es.
0ran$ing
Ne% features for "ublishin& sites in SharePoint Server 2013 minimi<e the s"ecial SharePoint
kno%led&e that is re(uired to successfully desi&n and brand a SharePoint site. To brand a SharePoint
site! desi&ners Aust create a site desi&n as they ty"ically %ould! by im"lementin& )T'! *SS! and
@avaScri"t. /esi&ners can create these files by usin& their desi&n tool of choice! %hether that is ;dobe
/ream%eaver! 'icrosoft E-"ression ?eb! or some other )T' editor. Bou don2t have to use
SharePoint /esi&ner or Hisual Studio 2013 to brand a SharePoint site. 0or information about ho% to
brand sites in SharePoint Server 2013! see ?hat2s ne% %ith SharePoint 2013 site develo"ment
4htt"#55&o.microsoft.com5f%link5"56ink$d72DD0D8:.
2eice/specific targeting
SharePoint Server 2013 su""orts tar&etin& different devices such as smart"hones! tablets! and set.to"
bo-es. /esi&ners can create channels that allo% a sin&le "ublishin& site to be rendered in multi"le
%ays by usin& different desi&ns that tar&et different devices. 0or information about ho% to desi&n
channels! see ?hat2s ne% %ith SharePoint 2013 site develo"ment 4htt"#55&o.microsoft.com5f%link5"56
ink$d72DD0D8:. 0or information about additional o"timi<ations for mobile su""ort in SharePoint Server
2013! see ?hat2s ne% for mobile devices in SharePoint 2013.

38
*hat"s ne! in !or>flo! in SharePoint Serer
2013
P#blishe$% +#l) 1,( 2012
S#&&ar)% earn about the ne% com"onents and conce"ts in SharePoint Server 2013 %orkflo%.
-pplies to; $hare4oint $erver ()*6
SharePoint Server 2013 brin&s a maAor advancement to %orkflo%# enter"rise features such as fully
declarative authorin&! 1EST and Service ,us messa&in&! elastic scalability! and mana&ed service
reliability.
SharePoint Server 2013 can use a ne% %orkflo% service built on the ?indo%s ?orkflo% 0oundation
com"onents of the .NET 0rame%ork 9.D. This ne% service is called ?orkflo% 'ana&er and it is
desi&ned to "lay a central role in the enter"rise. Processes are central to any or&ani<ation and %orkflo%
is the orchestrator of "rocesses.
$n this article#
T%o SharePoint %orkflo% "latforms
SharePoint /esi&ner enhancements
?orkflo% 'ana&er ca"abilities
?indo%s Po%erShell cmdlets that mana&e %orkflo%
T!o SharePoint !or>flo! platfor&s
The SharePoint 2010 ?orkflo% "latform has been carried for%ard to SharePoint Server 2013. ;ll of
your %orkflo%s that %ere built by usin& SharePoint Server 2010 %ill continue to %ork in SharePoint
Server 2013.
$n SharePoint Server 2010 the %orkflo% en&ine installed automatically %ith the "roduct. This continues
to be the case %ith the SharePoint 2010 ?orkflo% "latform in SharePoint Server 2013. $f you sim"ly
install SharePoint Server 2013 and do not install and confi&ure ?orkflo% 'ana&er then you %ill have a
nearly identical e-"erience %ith buildin& %orkflo%s as you did in SharePoint Server 2010.
The SharePoint 2013 ?orkflo% "latform only becomes available to you! and your tools! after you
do%nload and install the ne% ?orkflo% 'ana&er service and confi&ure it to communicate %ith your
SharePoint Server 2013 farm. 0or a detailed &uide on this "rocess! see )o% to# Set u" and confi&ure
SharePoint 2013 %orkflo%s.
3I
The fi&ure illustrates the conce"t.
9ig#re% Architect#ral changes in SharePoint *or>flo!

SharePoint 2esigner enhance&ents
SharePoint /esi&ner 2013 includes ne% functionality desi&ned s"ecifically for ?orkflo% 'ana&er. $n
SharePoint /esi&ner 2013 this ne% "latform is kno%n as the SharePoint 2013 ?orkflo% "latform.
These ne% features include#
; visual %orkflo% develo"ment e-"erience that uses a Hisio 2013 add.in
3J
; ne% action that enables no.code %eb service calls from %ithin a %orkflo%
Ne% actions for creatin& a task and startin& a task "rocess
Ne% coordination actions that let you start a %orkflo% built on the SharePoint 2010 ?orkflo%
"latform from a %orkflo% built on the SharePoint 2013 ?orkflo% "latform
; ne% /ictionary ty"e
Ne% %orkflo% buildin& blocks such as Sta&e! oo"! and ;"" Ste"
?hen you create a %orkflo% in SharePoint /esi&ner 2013! you have the o"tion of choosin& the "latform
on %hich you %ish to build a %orkflo% in the %orkflo% creation dialo& as sho%n in the fi&ure.

*or>flo! Manager capabilities
?orkflo% 'ana&er brin&s a ne% class of %orkflo% to SharePoint Server 2013. ?orkflo%s built by usin&
?orkflo% 'ana&er can take advanta&e of several ne% ca"abilities. These include enter"rise features
such as#
)i&h /ensity and 'ulti.Tenancy
Elastic Scale
;ctivity 5 ?orkflo% ;rtifact 'ana&ement
Trackin& and 'onitorin&
$nstance 'ana&ement
0ully /eclarative ;uthorin&
1EST and Service ,us 'essa&in&
'ana&ed Service 1eliability
3K
To learn more about ?orkflo% 'ana&er! see ?orkflo% 'ana&er on 'S/N.
*in$o!s Po!erShell c&$lets that &anage !or>flo!
;s a SharePoint Server 2013 %orkflo% administrator you should be familiar %ith ?indo%s Po%erShell.
;fter you have installed the ?orkflo% 'ana&er service you %ill need to confi&ure it to communicate %ith
your SharePoint Server 2013 farm. This "airin& is accom"lished by usin& ?indo%s Po%erShell
cmdlets. ?indo%s Po%erShell is used e-clusively %hen you mana&e and monitor ?orkflo% 'ana&er.
See Also
3ettin& started %ith SharePoint Server 2013 %orkflo%
?orkflo% develo"ment in SharePoint /esi&ner 2013 and Hisio 2013
?orkflo% 'ana&er

90
*hat"s ne! in search in SharePoint Serer 2013
P#blishe$% Septe&ber 2@( 2012
S#&&ar)% earn about ne% search ca"abilities in SharePoint Server 2013! includin& %ays to confi&ure
and monitor the system and im"rove search results.
-pplies to; $hare4oint $erver ()*6
$n this article#
Search user interface im"rovements
1elevance im"rovements
*han&es in cra%lin&
/iscoverin& structure and entities in unstructured content
'ore fle-ible search schema
Search health re"orts
Ne% search architecture
Search #ser interface i&proe&ents
?ithout havin& to o"en each search result! users can (uickly identify useful results in %ays such as the
follo%in&#
>sers can rest the "ointer over a search result to "revie% the document content in the hover panel
to the ri&ht of the result.
>sers can (uickly distin&uish search results based on their ty"e. 0or e-am"le! 'icrosoft Office
documents dis"lay the a""lication icon in front of the title of the search result. Ne%sfeed
conversation results dis"lay the number of re"lies and the number of likes to the ri&ht. Site results
list the to" links that users often click on the site. Peo"le in results sho% the "icture and the ync
availability status to the left.
,y default! certain ty"es of related results are dis"layed in &rou"s called result loc#s. ; result
block contains a small subset of results that are related in a "articular %ay. 0or e-am"le! results
that are Po%erPoint documents a""ear in a result block %hen the %ord N"resentationN is one of the
search terms. ;dministrators and site o%ners can also create result blocks to &rou" other results.
ike individual search results! you can "romote result blocks or rank them %ith other results.
Search hel"s users (uickly return to im"ortant sites and documents by rememberin& %hat they have
"reviously searched and clicked. The results of "reviously searched and clicked items are dis"layed as
(uery su&&estions at the to" of the results "a&e.
$n addition to the default manner in %hich search results are differentiated! site collection administrators
and site o%ners can create and use result t!pes to customi<e ho% results are dis"layed for im"ortant
documents. ; result ty"e is a rule that identifies a ty"e of result and a %ay to dis"lay it.
91
Site collection administrators and site o%ners can use dis"lay tem"lates to customi<e the a""earance
of search results by usin& an )T' editor! and they can customi<e the behavior of search results by
usin& @avaScri"t. They can s"ecify dis"lay tem"lates that determine ho% result ty"es a""ear.
Releance i&proe&ents
; search result! su&&estion! or recommendation is more relevant %hen it better satisfies the intent of
the "erson %ho issues the (uery. SharePoint Server 2013 im"roves relevance in areas such as
freshness of search results! lin&uistics! and document "arsin&. $t also im"roves relevance in the
follo%in& areas#
Ne% rankin& models
;nalysis of content and user interaction
Cuery rules
1esult sources
7e! ran>ing &o$els
SharePoint Server 2013 "rovides ne% rankin& models for "eo"le search! intranet sites! and $nternet
sites. ; rankin& model determines recall 4%hich items are dis"layed in the search results: and rank 4the
order in %hich search results are dis"layed:.
Anal)sis of content an$ #ser interaction
The search system determines the relevance of search results in "art by ho% content is connected!
ho% often an item a""ears in search results! and %hich search results "eo"le click. The search system
also determines %hich items users most commonly click in SharePoint. The ne% analytics com"onent
in SharePoint Server 2013 tracks and analy<es this information and uses it to continuously im"rove
relevance.
,ased on analytics information! site collection administrators and site o%ners can customi<e the user
e-"erience by addin& ?eb Parts to dis"lay recommendations and "o"ular items! or to dis"lay deep
lin#s! %hich link directly to sub.sections of a main "a&e that are fre(uently visited.
The search service also uses analytics to com"ute data for search usa&e re"orts. ;dministrators can
&et these re"orts in a timely manner! even on lar&e de"loyments.
8#er) r#les
?ithout any custom code! Search service administrators! site collection administrators! and site o%ners
can hel" searches res"ond to the intent of users by creatin& ?uer! rules. $n a (uery rule! you s"ecify
conditions and correlated actions. ?hen a (uery meets the conditions in a (uery rule! the search
system "erforms the s"ecified actions to im"rove the relevance of the search results. 0or e-am"le! you
mi&ht s"ecify a condition that checks %hether the (uery matches a term in a SharePoint term set! or
another condition that checks %hether the (uery is fre(uently "erformed on a "articular search vertical
in your search system! such as Hideos.
92
; (uery rule can s"ecify the follo%in& ty"es of actions#
;dd 4romoted Results 4formerly called ,est ,ets: that a""ear above ranked results. 0or e-am"le!
for the (uery Nsick leave!N a (uery rule could s"ecify a "articular Promoted 1esult! such as a link to
a site that has a statement of com"any "olicy re&ardin& time off %ork. These items %ere "reviously
referred to as ,est ,ets in SharePoint 2010.
;dd one or more result blocks. 0or e-am"le! for a (uery that contains N0abrikam sales re"ort!N a
(uery rule mi&ht use a ta-onomy dictionary to reco&ni<e 0abrikam as a customer! and then dis"lay
a result block %ith "ertinent results about 0abrikam from a customer relationshi" mana&ement
4*1': system.
*han&e ranked results! such as by modifyin& their relevance. 0or e-am"le! for a (uery that
contains Ndo%nload toolbo-!N a (uery rule could reco&ni<e the %ord Ndo%nloadN as an action ter&
and boost results from a "articular do%nload site on your intranet.
Res#lt so#rces
$n SharePoint Server 2010! sco"es and federated locations "rovided %ays to limit searches to a certain
set of content or subset of search results. $n SharePoint Server 2013! result sources re"lace sco"es
and federated locations.
Bou create and use a result source to s"ecify a location from %hich to &et search results and to s"ecify
a "rotocol for &ettin& those results. $n SharePoint Server 2010! you s"ecified a location and a "rotocol
by creatin& a federated location. $n SharePoint Server 2010! you could s"ecify the "rotocol as local
SharePoint inde-! 0;ST Search Server 2010 for SharePoint inde-! or O"enSearch. $n SharePoint
Server 2013! you can s"ecify the $ource T!pe as local SharePoint inde-! remote SharePoint inde-!
O"enSearch! or 'icrosoft E-chan&e Server inde-. $f you s"ecify remote SharePoint inde- as the
Source Ty"e! you do not have to su""ly any custom code to handle authentication! unlike in SharePoint
Server 2010.
$n a result source! you can also restrict (ueries to a subset of content by usin& a ?uer! transform. 0or
e-am"le! the "re.defined Nocal Hideo 1esultsN result source uses a (uery transform to return only
video results from the local SharePoint inde-. $n SharePoint Server 2010! you confi&ured this kind of
(uery restriction by usin& search sco"es.
On a search results "a&e! you can e-"ose results for (ueries on a "articular result source in several
%ays! such as in a result block or in a dedicated ?eb Part.
$n SharePoint Server 2010! only a Search service a""lication administrator %as able to create and
confi&ure federated locations. $n SharePoint Server 2013! site collection administrators! site o%ners!
and site desi&ners can also create and confi&ure result sources to meet their s"ecific re(uirements.
Changes in cra!ling
SharePoint Server 2013 includes many chan&es and im"rovements related to cra%lin& content.
93
Contin#o#s cra!l
$n SharePoint Server 2013! you can confi&ure cra%l schedules for SharePoint content sources so that
cra%ls are "erformed continuously. Settin& this o"tion eliminates the need to schedule incremental
cra%ls and automatically starts cra%ls as necessary to kee" the search inde- fresh. ;dministrators
should still confi&ure full cra%ls as necessary. 0or more information! see 'ana&e continuous cra%ls in
SharePoint 2013.
<ost $istrib#tion r#les re&oe$
$n SharePoint Server 2010! host distribution rules are used to associate a host %ith a s"ecific cra%l
database. ,ecause of chan&es in the search system architecture! SharePoint Server 2013 does not
use host distribution rules. $nstead! Search service a""lication administrators can determine %hether
the cra%l database should be rebalanced by monitorin& the 2atabases vie% in the cra%l lo&.
Re&oing ite&s fro& the search in$ex
$n SharePoint Server 2010! Search service a""lication administrators could remove items from the
search inde- by usin& Search Res#lt Re&oal. $n SharePoint Server 2013! you can remove items
from the search inde- only by usin& the cra%l lo&s.
2iscoering str#ct#re an$ entities in #nstr#ct#re$
content
Bou can confi&ure the cra%ler to look for NentitiesN in unstructured content! such as in the body te-t or
the title of a document. These entities can be %ords or "hrases! such as "roduct names. To s"ecify
%hich entities to look for in the content! you can create and de"loy your o%n dictionaries. 0or
com"anies! you can use the "re."o"ulated com"any e-traction dictionary that SharePoint Server 2013
"rovides.
Bou can store these entities in your search inde- as se"arate mana&ed "ro"erties and use those
"ro"erties later G for e-am"le! in search refiners.
To im"rove search relevance! the document "arsin& functionality in the content "rocessin& com"onent
analy<es both the structure and content of documents. /ocument "arsers e-tract useful metadata and
remove redundant information. 0or e-am"le! "arsers e-tract headin&s and subheadin&s from ?ord
documents! and titles! dates! and authors from slides in Po%erPoint "resentations. 0or )T' content!
redundant &eneric information such as menus! headers! and footers are classified as such and
removed from document summaries in the search results.
More flexible search sche&a
,y definin& cra%led "ro"erties! mana&ed "ro"erties! and the ma""in&s bet%een them! the search
schema determines ho% the "ro"erties of cra%led content are saved to the search inde-. *ra%led
"ro"erties and ho% these are ma""ed to mana&ed "ro"erties define ho% to transform cra%led content
99
into mana&ed "ro"erties. The search inde- stores the contents of the mana&ed "ro"erties. The
attributes of the mana&ed "ro"erties determine the search inde- structure.
SharePoint Server 2013 introduces ne% attributes that you can a""ly to mana&ed "ro"erties! such as
sortable and refinable. The sortable attribute reduces the time that is re(uired to return lar&e search
result sets by sortin& results before they are returned. The refinable attribute enables you to create a
refiner based on a "articular mana&ed "ro"erty.
$n SharePoint Server 2013! you can have multi"le search schemas. The main search schema is
defined at the Search service a""lication level. Site collection administrators can create customi<ed
search schemas for different site collections.
0or more information! see 'ana&e the search schema in SharePoint 2013.
Search health reports
SharePoint Server 2013 "rovides many (uery health re"orts and cra%l health re"orts. $n SharePoint
Server 2010 and 0;ST Search Server 2010 for SharePoint! similar re"orts %ere called Search
;dministration 1e"orts. 0or more information! see Hie% search dia&nostics in SharePoint Server 2013.
7e! search architect#re
SharePoint Server 2013 introduces a ne% search architecture that includes si&nificant chan&es and
additions to the search com"onents and databases. 0or e-am"les and more information! see the
Search technical dia&rams in Technical dia&rams for SharePoint 2013.

9D
Changes fro& SharePoint 2010 to SharePoint
2013
-p$ate$% 1ctober 1,( 2012
S#&&ar)% earn about the features and functionality that are de"recated in SharePoint 2013.
-pplies to; $hare4oint >oundation ()*6 = $hare4oint $erver ()*6
This article describes the features in SharePoint 2010 Products that have been de"recated or removed
from SharePoint 2013. /e"recated features are included in SharePoint 2013 for com"atibility %ith
"revious "roduct versions. These features %ill be removed in the ne-t maAor release of SharePoint
Products.
I&portant%
The information in this article a""lies to both SharePoint 0oundation 2013 and SharePoint
Server 2013.
$n this article#
0eatures de"recated in SharePoint 2013
SharePoint 0oundation 2010 de"recated search features
SharePoint Server 2010 de"recated search features
0;ST Search Server 2010 for SharePoint de"recated features
9eat#res $eprecate$ in SharePoint 2013
The follo%in& features and functionality have been de"recated or chan&ed in SharePoint 2013.
:is#al #pgra$e
2escription% The visual u"&rade feature in SharePoint Server 2010 is not available in SharePoint
2013. 0or the u"&rade from Office SharePoint Server 200I to SharePoint Server 2010! you could
choose to use the visual u"&rade feature to &ive site collection o%ners and site o%ners the o""ortunity
to "reserve the "revious user interface tem"orarily %hile still u"&radin& the infrastructure and
databases! site collections! and features to the latest version. This allo%ed site collection o%ners and
site o%ners to u"date customi<ations to %ork in the ne% user interface. Once the database and site
collection u"&rade %as com"lete! the user had the o"tion to u"&rade the user interface on a more
&ranular level of the %ebsite 4SP?eb obAect:.
Reason for change% The visual u"&rade feature is re"laced %ith deferred site collection u"&rade. The
site collection u"&rade "rocess is not reversible. The deferred site collection u"&rade is a more
com"rehensive u"&rade "rocess than visual u"&rade.
98
Hisual u"&rade "reserved only the old master "a&es! *SS files! and )T' files. /eferred site collection
u"&rade "reserves much more! includin& SP0eature functionality. To achieve the deferred site
collection u"&rade! maAor chan&es in the architecture %ere re(uired! includin& the removal of visual
u"&rade.
?ith deferred site collection u"&rade! you can continue to use the >$ from the "revious version
4SharePoint Server 2010: more seamlessly than is "ossible %ith visual u"&rade. The master "a&e!
*SS! @Scri"t! and SP0eatures %ill remain in SharePoint Server 2010 mode. One key difference is that
the &ranularity of u"&radin& the user interface is "er site collection 4SPSite: instead of site 4SP?eb:.
>sers can still "revie% their site in the ne% SharePoint 2013 user interface before committin&. )o%ever!
this is accom"lished by creatin& and u"&radin& a tem"orary co"y of their site collection instead of a
"revie% in the e-istin& instance of the site collection. The reason for "revie%in& a co"y of the site
collection is because of the com"le-ity of %hat occurs durin& site collection u"&rade. Once a site
collection is u"&raded! it cannot be rolled back. Therefore! "erformin& a "revie% %ould not be "ossible
e-ce"t in a co"y of the site collection.
Migration path% Site collection administrators %ho are usin& visual u"&rade to continue to use
SharePoint Server 200I must move to the SharePoint Server 2010 user interface before u"&radin& to
SharePoint 2013. ;fter the content database is u"&raded! users can use deferred site collection
u"&rade to continue to use the SharePoint Server 2010 e-"erience for their site collections. Site
collection administrators can be notified by their farm administrator %hen a site collection is ready for
u"&rade and the site collection administrators can then choose to either "erform the u"&rade of their
site collection or o"tionally first "revie% the ne% functionality in a tem"orary co"y of their site collection.
;ny SharePoint user interface mi&ht have de"endencies on visual u"&rade. The main de"endency %as
&ettin& the user interface version and then out"uttin& the correct user interface 4ne% or le&acy:. The
visual u"&rade ;P$ feature is u"dated so that the user interface version is rema""ed to the ne% site
collection co&patibilit) leel "ro"erty. This returns the same information about %hich version the site
uses as before. Therefore! de"endent code does not need to chan&e.
2oc#&ent *or>space site te&plate
2escription% ?hen you create a site in SharePoint 2013! the /ocument ?orks"ace site tem"late is not
available.
Reason for change% The scenario of collaboratin& on a document is no% "rovided by the Team Site
site tem"late. The /ocument ?orks"ace site tem"late %as removed from SharePoint 2013 to sim"lify
the list of tem"lates that are available %hen a user creates a ne% site collection.
Migration path% E-istin& sites that %ere created by usin& the /ocument ?orks"ace site tem"late %ill
continue to o"erate in SharePoint 2013. The /ocument ?orks"ace site tem"late %ill be removed
com"letely from the ne-t maAor release of SharePoint and sites that %ere created by usin& the
/ocument ?orks"ace site tem"late %ill not be su""orted.
Personali.ation Site site te&plate
2escription% ?hen you create a site in SharePoint 2013! the Personali<ation Site site tem"late is not
available.
9I
Reason for change% The Personali<ation Site site tem"late %as not a %idely used site tem"late. The
Personali<ation Site site tem"late %as removed from SharePoint 2013 to sim"lify the list of tem"lates
that are available %hen a user creates a ne% site collection.
Migration path% E-istin& sites that %ere created by usin& the Personali<ation Site site tem"late %ill
continue to o"erate in SharePoint 2013. The Personali<ation Site site tem"late %ill be removed
com"letely from the ne-t maAor release of SharePoint and sites that %ere created by usin& the
Personali<ation Site site tem"late %ill not be su""orted.
Meeting *or>space site te&plates
2escription% ?hen you create a site in SharePoint 2013! all five of the 'eetin& ?orks"ace site
tem"lates are not available. This includes the ,asic 'eetin& ?orks"ace! ,lank 'eetin& ?orks"ace!
/ecision 'eetin& ?orks"ace! Social 'eetin& ?orks"ace! and 'ulti"a&e 'eetin& ?orks"ace.
Reason for change% SharePoint 2013 and Office 2013 "rovide other features that su""ort meetin&s
and collaboration. 0or e-am"le! you can use ync to conduct live meetin&s! OneNote to take notes
durin& meetin&s! and a SharePoint team site or 'y Site to store shared meetin& notes.
Migration path% E-istin& sites that %ere created by usin& the 'eetin& ?orks"ace site tem"lates %ill
continue to o"erate in SharePoint 2013. The 'eetin& ?orks"ace site tem"lates %ill be removed
com"letely from the ne-t maAor release of SharePoint and sites that %ere created by usin& the 'eetin&
?orks"ace site tem"lates %ill not be su""orted.
Gro#p *or> site te&plate an$ Gro#p *or> sol#tion
2escription% ?hen you create a site in SharePoint 2013! the 3rou" ?ork site tem"late is not available.
This 3rou" ?ork site tem"late "rovides a &rou"%are solution that teams can use to create! or&ani<e!
and share information. The 3rou" ?ork site tem"late includes the 3rou" *alendar! *irculation! Phone.
*all 'emo! document library! and other basic lists. The 3rou" ?ork site tem"late and the 3rou" ?ork
solution are discontinued and not available in SharePoint 2013.
Reason for change% The 3rou" ?ork site tem"late %as not a %idely used site tem"late. The 3rou"
?ork site tem"late %as removed from SharePoint 2013 to sim"lify the list of tem"lates that are
available %hen a user creates a ne% site collection.
Migration path% E-istin& sites that %ere created by usin& the 3rou" ?ork site tem"late %ill continue to
o"erate in SharePoint 2013. The 3rou" ?ork site tem"late %ill be removed com"letely from the ne-t
maAor release of SharePoint and sites that %ere created by usin& the 3rou" ?ork site tem"late %ill not
be su""orted.
:isio Process Repositor) site te&plate
2escription% ?hen you create a site in SharePoint 2013! the Hisio Process 1e"ository site tem"late
%ill continue to be available. )o%ever! the Hisio Process 1e"ository site tem"late %ill be removed in the
ne-t maAor release of SharePoint.
9J
Reason for change% The Hisio Process 1e"ository site tem"late is not a %idely used site tem"late. The
Hisio Process 1e"ository site tem"late %as removed from SharePoint 2013 to sim"lify the list of
tem"lates that are available %hen a user creates a ne% site collection.
Migration path% Not re(uired. The Hisio Process 1e"ository site tem"late is available in SharePoint
2013.
-nghosting an$ c#sto&i.ing CSS files
2escription% The follo%in& methods are included in SharePoint 2013! but %ill be removed from the
ne-t maAor release of SharePoint#
Microsoft?SharePoint?SoapSerer?*ebs?C#sto&i.eCss
Microsoft?SharePoint?SoapSerer?*ebs?ReertCss
The *ebs?C#sto&i.eCss method a""lies style sheet customi<ation to a "articular file.
The *ebs?ReertCss method reverts style sheet customi<ation of a file to the default style sheet.
These t%o methods are stored in ?ebs.asm-.cs and are defined in ?ebs%sdl.as"s.
Reason for change% The methods are outdated and are no lon&er needed.
Migration path% None.
I&aging *eb serice
2escription% The $ma&in& ?eb service "rovides functionality for creatin& and mana&in& "icture
libraries. The $ma&in& ?eb service %ill be removed from the ne-t maAor release of SharePoint. The
$ma&in& ?eb service is included and su""orted in SharePoint 2013.
Reason for change% The $ma&in& ?eb service is not %idely used. The only client a""lication for the
$ma&in& ?eb service! Office Picture 'ana&er! is no lon&er included %ith SharePoint 2013. The $ma&in&
?eb service is bein& removed to reduce security vulnerabilities and to sim"lify the number of %ays to
connect to SharePoint 2013.
Migration path% ;ll the functionality of the $ma&in& ?eb service is available throu&h the client.side
obAect model 4*SO':. The *SO' "rovides client.side a""lications %ith access to a subset of the
SharePoint 0oundation server obAect model! includin& core obAects such as site collections! sites! lists!
and list items. ;lso! ?eb /istributed ;uthorin& and Hersionin& 4?eb/;H: "rovides clients %ith key
functionality of the $ma&in& ?eb service 4for e-am"le! u"load! do%nload! and rename:.
Excel Serices A Can"t e$it !or>boo>s in the bro!ser that hae
external $ata connections
2escription% ?orkbooks %ith e-ternal data connections that use ?indo%s authentication cannot be
refreshed in the bro%ser. $nstead! you are "rom"ted to o"en the %orkbook in the E-cel client "ro&ram.
?orkbooks that have database or ?indo%s credentials stored either in the Secure Store Service or in
the connection strin& can still be edited in the bro%ser. This chan&e a""lies only %hen E-cel ?eb ;""
9K
in Office ?eb ;""s Server is used to vie% %orkbooks! not %hen E-cel Services in SharePoint Server
2013 is used.
Reason for change% This is a desi&n limitation in SharePoint 2013.
Migration path% Bou can still refresh these %orkbooks in the E-cel client "ro&ram. ;dditionally! a
service a""lication administrator can confi&ure that %orkbooks are vie%ed in SharePoint 2013 instead
of Office ?eb ;""s Server.
*eb Anal)tics in SharePoint Serer 2010
2escription% ?eb ;nalytics in SharePoint Server 2010 has been discontinued and is not available in
SharePoint 2013. ;nalytics "rocessin& for SharePoint 2013 is no% a com"onent of the Search service.
Reason for change% ; ne% analytics system %as re(uired for SharePoint 2013 that included
im"rovements in scalability and "erformance! and that had an infrastructure that encom"asses
SharePoint Online. The ;nalytics Processin& *om"onent in SharePoint 2013 runs analytics Aobs to
analy<e content in the search inde- and user actions that are "erformed on SharePoint sites.
SharePoint 2013 still lo&s every click in SharePoint sites and still "rovides a count of hits for every
document. >ser data is made anonymous early in the lo&&in& "rocess and the ;nalytics Processin&
*om"onent is scalable to the service.
This analytics data is used in SharePoint 2013 to "rovide ne% item.to.item recommendation features! to
sho% vie% counts that are embedded in SharePoint 2013 and Search Server user interface! to "rovide
a re"ort of the to" items in a site and list! and to influence the relevancy al&orithm of search.
*hat happens to *eb Anal)tics after #pgra$e% The ?eb ;nalytics Service is not u"&raded to the
;nalytics Processin& *om"onent in SharePoint 2013. ?hen you u"&rade to SharePoint 2013! the
databases that contain the data from ?eb ;nalytics in SharePoint Server 2010 are not removed. These
databases are not used by or maintained by the ;nalytics Processin& *om"onent in SharePoint 2013.
This means that documents on sites in SharePoint Server 2010 that are u"&raded %ill sho% a hit count
of 0.
?hen you u"&rade to SharePoint 2013! do not attach and u"&rade the databases that contain the data
from ?eb ;nalytics in SharePoint Server 2010. ?e recommend that you turn off ?eb ;nalytics in the
SharePoint Server 2010 environment before you co"y the content databases that you %ant to u"&rade
to SharePoint 2013.
1e"orts from ?eb ;nalytics for the to" items in a site are carried for%ard. 1e"orts that sho% bro%ser
traffic! to" users of a site! and referrin& >1 are not carried for%ard and are not used by the ;nalytics
Processin& *om"onent in SharePoint 2013.
;dministrative re"orts for the (uota usa&e of site collections in the farm are not available in SharePoint
2013.
SharePoint 2013 does not su""ort the ?eb ;nalytics ?eb Part. ;fter a farm is u"&raded to SharePoint
2013! all instances of a ?eb ;nalytics ?eb Part %ill not function. The "a&e that includes the ;nalytics
?eb Part %ill render and a messa&e a""ears that informs the user that the ?eb Part is no lon&er
su""orted.
D0
Migration path% None. /ata collection for ;nalytics Processin& in SharePoint 2013 starts immediately
for sites! includin& SharePoint Server 2010 sites.
Excel Serices A Can"t e$it !or>boo>s in the
bro!ser that hae external $ata connections
2escription% ?orkbooks %ith e-ternal data connections that use ?indo%s authentication cannot be
refreshed in the bro%ser. $nstead! you are "rom"ted to o"en the %orkbook in the E-cel client "ro&ram.
?orkbooks that have database or ?indo%s credentials stored either in the Secure Store Service or in
the connection strin& can still be edited in the bro%ser. This chan&e a""lies only %hen E-cel ?eb ;""
in Office ?eb ;""s Server is used to vie% %orkbooks! not %hen E-cel Services in SharePoint Server
2013 is used.
Reason for change% This is a desi&n limitation in SharePoint 2013.
Migration path% Bou can still refresh these %orkbooks in the E-cel client "ro&ram. ;dditionally! a
service a""lication administrator can confi&ure that %orkbooks are vie%ed in SharePoint 2013 instead
of Office ?eb ;""s Server.
1rgani.ation Profiles
2escription% The Or&ani<ation Profiles feature is de"recated in SharePoint Server 2013. Or&ani<ation
Profiles contain detailed information about an or&ani<ation such as teams! divisions! and other
information that describes the or&ani<ation=s hierarchy.
Reason for change% SharePoint features related to identities continue to evolve around the core
conce"ts of users and &rou"s! and SharePoint %ill not be investin& further in Or&$/.
Migration path% E-istin& solutions based on Or&ani<ation Profiles %ill continue to o"erate in
SharePoint 2013. The Or&ani<ation Profiles feature %ill be removed com"letely from the ne-t maAor
release of SharePoint! and solutions created by usin& Or&ani<ation Profiles %ill not be su""orted.
SharePoint 9o#n$ation 2010 $eprecate$ search
feat#res
The follo%in& functionality has chan&ed in SharePoint 0oundation search.
Search capabilities
2escription# The search ca"abilities of SharePoint 0oundation 2013 have chan&ed! and are no%
based on the same search im"lementation as SharePoint Server. This "rovides many im"rovements!
but also means that the search confi&uration is very different.
Reason for change# ;li&nment of basic ca"abilities bet%een SharePoint Server and SharePoint
0oundation.
D1
Migration path# No mi&ration of search settin&s is su""orted.
SharePoint Serer 2010 $eprecate$ search feat#res
The follo%in& section "rovides details about the de"recated search features in SharePoint Server.
Mo$if)ing the search topolog) #sing a !eb/base$ interface
2escription# SharePoint 2013 uses the %eb.based interface to sho% the current status of the to"olo&y.
Bou chan&e the to"olo&y by usin& ?indo%s Po%erShell. SharePoint Server 2010 also included a %eb.
based o"tion for chan&in& the to"olo&y.
Reason for change# The core search architecture of SharePoint 2013 has a more com"le- and fle-ible
to"olo&y that can be chan&ed more efficiently by usin& ?indo%s Po%erShell.
Migration path# >se ?indo%s Po%erShell to modify the search to"olo&y.
2iacritic sensitiit) ele&ent in the thesa#r#s
2escription# $n SharePoint Server 2010! thesaurus files contain a HdiacriticsIsensitiveJ element. This
element determines %hether diacritical marks such as accents should be i&nored or a""lied by the
search system %hen e-"andin& a (uery %ith terms from the thesaurus. ,y default! the
HdiacriticsIsensitiveJ element is set to <ero to i&nore diacritical marks.
$n SharePoint 2013! the HdiacriticsIsensitiveJ element is not available. $nstead! diacritical marks are
al%ays res"ected %hen matchin& (uery terms %ith terms in the thesaurus.
/iacritic variants are not automatically matched %ith (uery terms. Therefore! fe%er (uery terms mi&ht
be e-"anded by synonyms. 0or e-am"le! the thesaurus entry HmunchenJ is not matched %ith the
(uery term HmKnchenJ.
Reason for change# The feature has limited usa&e. The same behavior as in SharePoint Server 2010
can be achieved by addin& diacritic variants in the thesaurus.
Migration path# >"date the thesaurus dictionaries that are ta&&ed as diacritic insensitive. To u"date
thesaurus dictionaries! add diacritic variations of the relevant terms.
Replace&ent &o$e !ithin the thesa#r#s
2escription# The thesaurus re"lacement mode is de"recated in SharePoint 2013.
$n SharePoint Server 2010! you can classify entries in the thesaurus as e-"ansions that are added to
the (uery in addition to the ori&inal term. ike%ise! you can classify entries as re"lacements of the
ori&inal term in a (uery.
$n SharePoint 2013! thesaurus re"lacements are no lon&er su""orted. ;ll entries in the thesaurus are
e-"ansions! and the ori&inal term is not removed from the (uery. The ori&inal (uery term is al%ays
evaluated %hen you search the inde-. Bou cannot remove synonyms or %ords from the inde-.
D2
Reason for change# The feature has limited usa&e! and may also have un%anted side.effects for
relevance.
Migration path# No e(uivalent feature.
Search 8#er) !eb serice
2escription# The Search Cuery %eb service is de"recated in SharePoint 2013.
$n SharePoint Server 2010! the Search Cuery %eb service e-"oses the SharePoint Enter"rise Search
ca"abilities to client a""lications. This enables you to access search results from client and %eb
a""lications outside the conte-t of a SharePoint site.
Reason for change# The Search Cuery %eb service is de"recated because the client obAect model
4*SO': and a ne% 1EST.based %eb service are available for develo"in& Office.%ide e-tensibility
scenarios. The *SO' e-"oses the same functionality as the Search Cuery %eb service! and a lar&er
set of functionality for stand.alone client a""lications.
Migration path# *han&e custom search solutions to use the *SO' or 1EST.based %eb service
instead of usin& the Search Cuery %eb service.
Search RSS an$ search fro& *in$o!s
2escription# The search 1SS feature is de"recated in SharePoint 2013. The functionality for
"erformin& enter"rise searches from ?indo%s I de"ends on search 1SS and this element has also
been de"recated in SharePoint 2013.
The 1SS link no lon&er a""ears on the results "a&e. This link is re"laced by the Search ;lerts link.
,efore u"&radin& site collections to SharePoint 2013! you can continue to use 1SS in the SharePoint
2010 version of the Search *enter. )o%ever! after you u"&rade the Search *enter to SharePoint 2013!
the 1SS is no lon&er available. $n SharePoint 2013! you can create custom 1SS feeds that use the
client obAect model 4*SO':! %hich tar&ets the needs of your "articular a""lication and the 1SS
readers.
Reason for change# 'ost 1SS readers that are available do not su""ort claims authentication. $n
SharePoint 2013! claims authentication is the default authentication model. ,y usin& claims
authentication! 1SS readers %ork %hile the authentication cookie is cached. )o%ever! after the cookie
e-"ires! 1SS readers cannot refresh their authentication! and so they sto" %orkin&.
Migration path# ;fter mi&ratin& a site to SharePoint 2013! you can create search.based alerts to be
notified of chan&es to search results. Bou can also create a custom 1SS feed in SharePoint document
libraries! by usin& the >M e-tensibility "latform.
C#sto& !or$ brea>er $ictionaries
2escription# The format of the custom %ord breaker dictionaries has chan&ed in SharePoint 2013. $n
SharePoint 2013! you can only create one lan&ua&e.inde"endent dictionary. $n SharePoint Server
2010! you can create lan&ua&e.s"ecific custom dictionaries 4one dictionary for each lan&ua&e: to edit
D3
the %ord breaker behavior of enter"rise search. The %ord breaker behavior for East ;sian 4*@+:
lan&ua&es has not chan&ed in SharePoint 2013.
$n SharePoint 2013! custom %ord breaker dictionaries from earlier versions of SharePoint Server are
not su""orted.
Reason for change# The search "rocessin& frame%ork for SharePoint 2013 is ne%! and the %ay the
%ord breakers o"erate has chan&ed.
Migration path# Bou must combine e-istin& custom dictionaries into one lan&ua&e.inde"endent
dictionary.
Config#ration of ste&&ing in the registr)
2escription# The confi&uration of stemmin& in the re&istry is no lon&er su""orted in SharePoint 2013.
'odifyin& stemmin& entries in the re&istry has no effect durin& search. $n SharePoint Server 2010! you
can turn stemmin& on or off! or you can re"lace it %ith a third."arty stemmer by chan&in& the re&istry. $n
SharePoint 2013! you cannot use a third."arty stemmer.
Reason for change# This feature has limited feature usa&e.
Migration path# There is no mi&ration "ath available for custom stemmers. Bou can enable or disable
stemmin& in the Search 1esult ?eb Part.
SharePoint Search S83 s)ntax
2escription# $n SharePoint Server 2010! you could construct com"le- search (ueries by usin& SC
synta-.
Search in SharePoint 2013 su""orts 0;ST Cuery an&ua&e 40C: synta- and +ey%ord Cuery
an&ua&e 4+C: synta- for custom search solutions. Bou cannot use SC synta- in custom search
solutions.
*ustom search solutions that use SC synta- %ith the Cuery obAect model and the Cuery %eb service
that %ere created in earlier versions of SharePoint Serverdo not %ork %hen you u"&rade them to
SharePoint 2013. $f you submit (ueries by usin& these a""lications! you %ill receive an error.
Reason for change# The core search architecture has chan&ed in SharePoint 2013! and the SC
synta- is no lon&er su""orted.
Migration path# *han&e current search solutions to use either the +C synta- or 0C synta- for
(ueries.
Shallo! search refiners
2escription# SharePoint Server Search in Office 2010 su""orted shallo% search refiners. 0;ST Search
Server 2010 for SharePoint su""orts shallo% refiners and dee" refiners. $nSharePoint 2013! only dee"
search refiners are su""orted.
D9
?e recommend that you use dee" search refiners to refine searches. $n SharePoint 2013! dee"
refiners are an im"rovement to the e-istin& 0;ST Search Server 2010 for SharePoint functionality. 0or
e-am"le! the resource usa&e for each refiner is im"roved in SharePoint 2013.
$n SharePoint 2013! you can vie% refiners as you did in the earlier version of the "roduct. )o%ever! the
refiners are no% com"uted differently. They are created based on inde- structures that are a&&re&ated
across the full result set.
Reason for change# The shallo% search refiners are re"laced %ith an im"roved im"lementation of
dee" search refiners.
Migration path# No s"ecific mi&ration ste"s are necessary.
9AST Search Serer 2010 for SharePoint $eprecate$
feat#res
The follo%in& section "rovides details about the de"recated features in 0;ST Search Server 2010 for
SharePoint.
9AST Search $atabase connector
2escription# The 0;ST Search database connector is not su""orted in SharePoint 2013.
Reason for change# The connector frame%ork for SharePoint 2013 is combined %ith the ,*S
frame%ork and the ,usiness /ata *atalo& connectors.
Migration path# 1e"lace the 0;ST Search database connector %ith the ,usiness /ata *atalo&.based
inde-in& connectors in the ,*S frame%ork.
9AST Search 3ot#s 7otes connector
2escription# The 0;ST Search otus Notes connector is not su""orted in SharePoint 2013.
The otus Notes inde-in& connector 4,*S frame%ork: "rovides similar functionality as the 0;ST
Search otus Notes connector. The 0;ST Search otus Notes connector su""orts the otus Notes
security model. This includes otus Notes roles! and lets you cra%l otus Notes databases as
attachments.
Reason for change# The connector frame%ork for SharePoint 2013 is combined %ith the ,*S
frame%ork and the ,usiness /ata *atalo& connectors.
Migration path# 1e"lace the 0;ST Search otus Notes connector %ith the otus Notes inde-in&
connector! or %ith a third."arty connector.
9AST Search !eb cra!ler
2escription# The 0;ST Search %eb cra%ler is not su""orted in SharePoint 2013.
DD
The SharePoint 2013 cra%ler "rovides similar functionality to the 0;ST Search %eb cra%ler.
Reason for change# The cra%ler ca"abilities are mer&ed into one cra%ler im"lementation for
consistency and ease of use.
Migration path# >se the standard SharePoint 2013 cra%ler. The follo%in& table e-"lains the differences
bet%een the 0;ST Search %eb cra%ler and the SharePoint 2013 Previe% cra%ler! and "rovides details
about mi&ration.

9eat#re 9AST Search !eb cra!ler SharePoint 2013 cra!ler Migration path
1efeed documents Bou can refeed documents
that you have "reviously
do%nloaded to the inde-
%ithout havin& to recra%l
them.
Bou can "erform a full
recra%l %ith similar
functionality! but %ith
sli&htly decreased
"erformance of feeds.
None.
E-tract dynamically
&enerated links and
content from @ava
Bou can e-tract
dynamically &enerated
links and content from
@avaScri"t.
No lon&er su""orted. None.
an&ua&e.focused
cra%ls
Bou can e-tract
dynamically &enerated
links and content from
@avaScri"t. Bou can
"erform cra%ls focused on
lan&ua&e.
Bou can focus a cra%l on
a certain lan&ua&e! by
only follo%in& links from
and storin& content for
documents that match
s"ecific lan&ua&es.
This feature is intended for
lar&e scale cra%ls that
tar&et s"ecific lan&ua&es
but that do not limit the
cra%l to a to" level
domain.
No lon&er su""orted. None.
'odify >1$s Bou can modify the >1$s
before cra%lin& them.
Such a modification of the
>1$ enables you to
remove certain features of
the >1$! such as dynamic
Bou can a""ly "refi-.ty"e
>1$ re%ritin& %ith the
NServer name rema""in&N
feature in Search ;dmin.
This allo%s you to "erform
the most relevant
None.
D8
9eat#re 9AST Search !eb cra!ler SharePoint 2013 cra!ler Migration path
com"onents! and to
rename host names.
modifications of the >1$.

9in$ si&ilar res#lts
2escription# The 0ind similar results feature is not available in SharePoint 2013. The 0ind similar
results feature is su""orted in 0;ST Search Server 2010 for SharePoint to search for results that
resemble results that you have already retrieved.
Reason for change# The 0ind similar results feature is available only %ithin the (uery inte&ration
interfaces! and it does not consistently "rovide &ood results in many scenarios.
Migration path# There is no mi&ration "ath available.
9AST 8#er) 3ang#age 49835 $eprecate$ feat#res
2escription# The 0C features are ali&ned %ith the features of the SharePoint +ey%ord Cuery
an&ua&e 4+C: synta-
The follo%in& table describes the 0;ST Cuery an&ua&e 40C: features that are de"recated in
SharePoint 2013.

983 operator or feat#re Change$ behaior in SharePoint 2013
ABL o"erator This o"erator has the same effect as the O/ o"erator.
/ABM o"erator This o"erator is acce"ted but does not affect result rankin&.
G/ABM o"erator This o"erator has a ne% and more fle-ible synta-.
The old synta- is de"recated.
The boost "arameter is ma""ed to the ne% cb "arameter. The boostall
"arameter is i&nored.
S/+B- o"erator The B "arameter is acce"ted but i&nored.
The M+B8GPABS+OBNMAG8GPABS+OB "arameters are not su""orted.
The ABBOA+OBIC<ASS "arameter is not su""orted.
0or the MO68 "arameter! the follo%in& ar&uments are de"recated! and have
the follo%in& behavior#
ABL# E(ual to the O/ mode.
DI
983 operator or feat#re Change$ behaior in SharePoint 2013
B8A/NOB8A/# E(ual to the AB6 mode.
S+MP<8A<<NS+MP<8ABL# The (uery strin& ar&ument is evaluated
accordin& to the +C (uery synta-.
$m"licit ty"in& of numeric
data ty"es
The 0C "arser is not search schema.a%are! and some im"licit numeric
data ty"in& is no lon&er su""orted.

Reason for change# To sim"lify the (uery synta-! some redundant synta- features %ere removed from
SharePoint 2013.
Migration path# The follo%in& table describes %hat to re"lace the de"recated 0C o"erators or
features %ith.

Replace this 983 operator or
feat#re
*ith
ABL o"erator 0O/6S o"erator
/ABM o"erator G/ABM o"erator
G/ABM o"erator Ne% synta-
S/+B- o"erator 0or "ro-imity o"erations! use the B8A/NOB8A/ o"erators. 0or
ma""in& of end.user (uery te-t! use the +C mode.
Numeric data ty"es Ty"e numeric data e-"licitly. >se either the intNAoatNdecimal
o"erators! or consistently use decimalNAoat synta- 4%ith decimals
al%ays included: in the (uery.

-R3 8#er) s)ntax
2escription# $n 0;ST Search Server 2010 for SharePoint! the >1.related mana&ed "ro"erties 4such
as site! or "ath: are tokeni<ed as a te-t strin&! and you can (uery any sub"art of the >1. This includes
SA/S*0+D! 8B6S*0+D! PD/AS8 and "ro-imity (ueries on >1 "ro"erties. S"ecial characters such
as ENF! EIF and E*Fare handled as %ord delimiters.
$n SharePoint 2013! the entire >1 is tokeni<ed as one %ord. This includes s"ecial characters such as
ENF! EIF and E*F. Bou can (uery these mana&ed "ro"erties by#
Searchin& for the full strin& for the site or "ath.
Searchin& for the leadin& "art of the site or "ath.
Omittin& the "rotocol "art 4htt"! htt"s:! and omittin& the leadin& "art of the domain address in the
(uery e-"ression! for the site mana&ed "ro"erty.
DJ
Reason for change# The im"lementation in SharePoint 2013 is ali&ned %ith SharePoint Server 2010
search. The 0;ST Search Server 2010 for SharePoint im"lementation has a very hi&h (uery
"erformance cost! es"ecially %hen you search for the full >1 or a leadin& subset of the >1.
Migration path# The follo%in& table "rovides details on ho% to chan&e 0;ST Search Server 2010 for
SharePoint (uery e-"ressions to match the SharePoint 2013 >1 (uery synta-.

To &atch Then
The com"lete >1 strin& Search for the e-act strin&. S"ecial characters in the
>1 must match. /o not use the PD/AS8 o"erator.
The leadin& "art of the >1 /o not use the %ildcard character.
;ny "art of the >1
'a" the relevant cra%led "ro"erty to an additional
mana&ed "ro"erty of ty"e te-t.
>se this mana&ed "ro"erty as a "ro"erty filter in
your (uery.

Specific search scope filters
2escription# $n SharePoint 2013! search sco"es are automatically converted to result sources.
$n 0;ST Search Server 2010 for SharePoint! you can s"ecify additional filterin& conditions for search
sco"es! as described in the follo%in& table#

9ilter4s5 2escription
0C sco"e These filters may contain 0C synta-. $n SharePoint
2013! you can use mi&rated 0;ST Search sco"e
filters! but you cannot chan&e them.
;lternative full.te-t inde- for the (uery This filter "rovides a non.default full.te-t inde- for
the full.te-t "art of the (ueries.
$n SharePoint 2013! you can use mi&rated 0;ST
Search sco"e filters that contain an alternative full.
te-t inde-. )o%ever! you cannot chan&e or convert
these filters to result sources.

Reason for change# The search sco"e functionality %as re"laced by a more "o%erful functionality for
result sources.
DK
Migration path# Bou must convert 0C sco"e filters to corres"ondin& result sources. Bou can use an
alternative full.te-t inde- in the (uery synta-.
Anti/phrasing
2escription# The search anti."hrasin& feature in 0;ST Search Server 2010 for SharePoint is not
su""orted in SharePoint 2013.
;nti."hrasin& removes "hrases that do not have to be inde-ed from (ueries! such as E%ho isF! E%hat isF!
or Eho% do $F. These anti."hrases are listed in a static dictionary that the user cannot edit.
$n SharePoint 2013! such "hrases are not removed from the (uery. $nstead! all (uery terms are
evaluated %hen you search the inde-.
Reason for change# The 0;ST Search Server 2010 for SharePoint feature has limited usa&e due to
the limited number of customi<ation o"tions.
Migration path# None.
1ffensie content filtering
2escription# The filterin& of offensive content in search is de"recated in SharePoint 2013.
$n 0;ST Search Server 2010 for SharePoint! you can choose to filter offensive content. Offensive
content filterin& is not enabled by default.
$n SharePoint 2013! you can no lon&er block documents that contain "otentially offensive content from
bein& inde-ed.
Reason for change# The feature has limited usa&e.
Migration path# None.
S#bstring search
2escription# The substrin& search feature %as removed in SharePoint 2013.
$n 0;ST Search Server 2010 for SharePoint! substrin& search 4N.&ram inde-in&: can be used in
addition to the statistical tokeni<er in East ;sian lan&ua&es. Substrin& search can be useful for cases in
%hich the normal tokeni<ation is ambi&uous! such as for "roduct names and other conce"ts that are not
"art of the statistical tokeni<er.
Reason for change# The feature has limited usa&e! and has very e-tensive hard disk re(uirements for
the inde-.
Migration path# None.
80
Person na&es an$ location extractions
2escription# $n SharePoint 2013! you cannot e-tract "erson names and locations from documents by
usin& "redefined e-tractors.
$n SharePoint 2013! you can create custom e-tractors to e-tract "erson names and locations. The
difference bet%een the "redefined e-tractors in 0;ST Search Server2010 for SharePoint! and custom
e-tractors in SharePoint 2013! is that custom e-tractors are only based on dictionary entries! %hereas
the "redefined e-tractors also use e-traction rules.
Reason for change# This feature has limited usa&e and usually re(uires e-tensive customi<ation. $n
most cases! %e recommend that you use customer.s"ecific dictionaries.
Migration path# >se custom e-tractors for "erson names and locations.
7#&ber of c#sto& entit) extractors
2escription# $n SharePoint 2013! the number of custom entity e-tractors that you can define is limited
to 12.
$n 0;ST Search Server 2010 for SharePoint Service Pack 1 4SP1:! you can define an unlimited number
of custom e-tractors. Bou can use custom entity e-tractors to "o"ulate refiners on the search result
"a&e.
There are 12 "redefined custom entity e-tractors in SharePoint 2013#
0ive %hole.%ord case.insensitive e-tractors
0ive %ord."art case.insensitive e-tractors
One %hole.%ord case.sensitive e-tractor
One %ord."art case.sensitive e-tractor
Reason for change# ,y usin& a "redefined set of custom entity e-tractors! the content "rocessin&
architecture is more sim"le and easier to use.
Migration path# >se the "redefined set of custom entity e-tractors.
S#pporte$ $oc#&ent for&ats
2escription# SharePoint 2013 no lon&er su""orts rarely used and older document formats that are
su""orted in 0;ST Search Server 2010 for SharePoint by enablin& the ;dvanced 0ilter Pack. ,oth the
>S lo&s and the cra%l lo& indicate the items that %ere not cra%led.
$n SharePoint 2013! the set of su""orted formats that are enabled by default is e-tended! and the
(uality of document "arsin& for these formats has im"roved.
Reason for change# The file formats for inde-in& are older formats and are no lon&er su""orted.
Migration path# Bou can %ork %ith "artners to create $0ilter.based versions of the file formats that can
no lon&er be inde-ed.
81
Content processing extensibilit)
2escription# The 0;ST Search Server 2010 for SharePoint content "rocessin& e-tensibility feature has
chan&ed in SharePoint 2013. *ontent "rocessin& "re"ares an item from a content source for inde-in&
and searchin&. The 0;ST Search Server 2010 for SharePoint content "rocessin& e-tensibility feature
uses a sandbo- %here your custom code runs. See htt"#55msdn.microsoft.com5library5ffIKDJ01.as"- on
'S/N! 0;ST Search! for more information.
SharePoint 2013 "rovides a ne% %eb service interface for content "rocessin& e-tensibility.
The ne% im"lementation of this feature has the follo%in& im"rovements#
The %eb service callout "rovides more fle-ibility about %here the custom code runs than it does
%ith the sandbo- callout.
Bou can define tri&&ers for the %eb service callout to o"timi<e "erformance.
*ontent "rocessin& is "erformed on mana&ed "ro"erties instead of on cra%led "ro"erties. This
makes it sim"ler to mana&e the items that are chan&ed.
Reason for change# The content "rocessin& architecture of search has chan&ed to im"rove
"erformance and fle-ibility.
Migration path# To inte&rate %ith the ne% SharePoint content "rocessin& com"onent! you must chan&e
the code. The custom content "rocessin& code must be "acka&ed as a %eb service.
C#sto& BM3 ite& processing
2escription# 0;ST Search Server 2010 for SharePoint includes a custom M' item "rocessin& feature
as "art of the content "rocessin& "i"eline. *ustom M' item "rocessin& is not su""orted in SharePoint
2013.
Reason for change# $n SharePoint 2013! the content "rocessin& architecture has chan&ed. *ustom
M' item "rocessin& %as removed and %e recommend that you im"lement a ma""in& functionality
outside SharePoint.
Migration path# *ustom M' item "rocessin& can be "erformed outside the content "rocessin&
"i"eline! for e-am"le by ma""in& M' content to a SharePoint list! or to a database table.
A$$ing a test ite& to the in$ex
2escription# /ocPush is a test and dia&nostic command.line tool that submits test documents to the
0;ST Search Server 2010 for SharePoint inde-. ; similar command.line tool is not available in
SharePoint 2013.
Reason for change# The administration and dia&nostics of feedin& and cra%lin& has chan&ed in
SharePoint 2013.
Migration path# None. Bou can create test documents or test lists in SharePoint to test cra%lin& and
feedin&. To remove items from the search inde- or to verify that there are any errors on an item! you
can use the cra%l lo&. See Hie% search dia&nostics in SharePoint Server 2013 for more information.
82
To remove items from the search results! use the Search 1esult 1emoval feature in Cueries and
1esults. See /elete items from the search inde- or from search results in SharePoint 2013.
See Also
E-"lore SharePoint 2013 Previe%

83
1erie! of i$entit) &anage&ent in SharePoint
2013
P#blishe$% 1ctober 1,( 2012
S#&&ar)% earn ho% SharePoint 2013 su""orts authentication! authori<ation! and the stora&e!
synchroni<ation! and dis"lay of entities and their attributes.
-pplies to; $hare4oint $erver ()*6 0nterprise = $hare4oint $erver ()*6 $tandard = $hare4oint
>oundation ()*6
$dentity mana&ement in SharePoint 2013 is the combination of the follo%in& "arts#
The set of identifiers for entities! their stora&e location! the creation of trust relationshi"s amon&
identity stores! and the dis"lay of identifier information.
>sers! com"uters! or services are e-am"les of entities.
The methods! ty"ically "rovided by a form of credential e-chan&e that is "rotected %ith
cry"to&ra"hy! that use identifiers to authenticate access to a resource.
The methods! ty"ically s"ecified by a set of "ermissions that are assi&ned to identifiers! that s"ecify
and enforce the authori<ation of access to a resource.
Ele&ents of an i$entit) &anage&ent s)ste&
; ty"ical identity mana&ement system consists of the follo%in& elements#
Entities
Stores for accounts and attributes
;uthentication methods
;uthori<ation methods
Stora&e! synchroni<ation! and dis"lay of entity attributes
The follo%in& sections describe these elements and ho% SharePoint 2013 su""orts them.
Entities
?ithin an identity mana&ement system! an entity re"resents a "hysical or lo&ical obAect that re(uires
access to a resource. Entities on a net%ork that uses ;ctive /irectory /omain Services 4;/ /S:
include users! com"uters! and services. Each entity has an identity that can corres"ond to an account
in a directory! such as ;/ /S. ;ccounts can consist of a set of attributes that describe the entity! such
as name! &rou" membershi"! email address! and so on.
0or identity mana&ement in SharePoint 2013! entities are users! &rou"s! services! com"uters! and
a""s.
89
Stores for acco#nts an$ attrib#tes
; store that contains accounts and attributes "rovides a location for entity accounts and their attributes.
Net%orks that use ;/ /S store accounts and attributes in ;/ /S. The store that contains accounts and
attributes can do the follo%in&#
Halidate account credentials durin& authentication.
Provide account attributes to the entity that re(uests authentication so that those attributes can be
used for authori<ation.
SharePoint 2013 can use the forms.based or Security ;ssertion 'arku" an&ua&e 4S;': user
authentication methods for ;/ /S or additional stores. SharePoint 2013 does not include a store for
accounts and attributes.
$dentity federation is the "rocess that links multi"le stores of accounts and attributes throu&h trust
relationshi"s so that authentication and authori<ation for access to resources can occur seamlessly
across those stores. 0orefront $dentity 'ana&er 2010 12 enables you to mana&e identity life cycle and
role mana&ement across hetero&eneous identity "latforms.
Metho$s of a#thentication
;n authentication method is a s"ecific set of messa&es that com"uters send to each other to "erform
authentication. ; messa&e validates an identity of an entity. The result of the authentication "rocess is a
security token! %hich ty"ically contains cry"to&ra"hic "roof that a store of accounts and attributes has
validated the identity. The security token can also contain entity attributes! such as the list of security
&rou"s to %hich the entity belon&s.
0or ;/ /S! the authentication method is ty"ically either NT' or the +erberos "rotocol. 0or e-am"le!
%hen a user lo&s on to a domain.Aoined com"uter! it collects the security credentials from the user and
uses the +erberos "rotocol to validate those credentials %ith an ;/ /S domain controller. The user=s
com"uter receives a +erberos ticket to use %hen the user accesses resources. The +erberos ticket
contains cry"to&ra"hic "roof that ;/ /S has validated the credentials and a list of &rou"s to %hich the
user belon&s.
Clai&s/base$ i$entit) an$ a#thentication
;lthou&h +erberos and NT' %ork %ell for ;/ /S.based net%orks! they do not e-tend easily to
multi"le stores of accounts and attributes from third."arty vendors or to identity mana&ement systems
in the cloud.
0or claims.based identity! a user obtains a security token that a trusted security token service 4STS:
has di&itally si&ned and that contains a set of claims. Each claim re"resents a s"ecific item of data
about the user such as his or her name! &rou" membershi"s! and role on the net%ork. *laims.based
identity enables a""lications to rely on the security token for "roof of authentication and the set of
claims for authori<ation or other "rocessin&. *laims.based identity ty"ically enables a user to "erform
an authentication to obtain the security token and submit that token to a""lications. The claims.a%are
a""lication verifies the di&ital si&nature of the security token and uses the claims to im"lement
authori<ation and other a""lication.s"ecific functions.
8D
*laims.based identity and authentication in ?indo%s is built on ?indo%s $dentity 0oundation 4?$0:!
%hich is a set of .NET 0rame%ork classes that is used to im"lement claims.based identity. *laims.
based authentication relies on standards such as ?S.0ederation! ?S.Trust! and "rotocols such as
S;'.
; sim"lified claims.based identity im"lementation contains the follo%in& com"onents#
A clai&s/a!are client application ;n a""lication that can obtain a security token from an STS
and submit security tokens for authentication and authori<ation. ;n e-am"le of a claims.a%are
client a""lication is a %eb bro%ser! such as $nternet E-"lorer.
An STS ; server or service that creates security tokens for claims.a%are client a""lications. The
STS that is in SharePoint 2013 "rovides its o%n security tokens to re(uestin& claims.a%are client
a""lications! and it can also use ;ctive /irectory 0ederation Services 4;/ 0S: 2.0 as an e-ternal
STS.
A rel)ing part) ; com"uter or a""lication that relies on an STS for tokens. The relyin& "arty
redirects claims.a%are client a""lications to the STS to obtain a suitable security token. SharePoint
2013 can act as a relyin& "arty to an e-ternal STS. ;n e-am"le is a SharePoint %eb a""lication
that is confi&ured to use ;/ 0S as its STS.
A clai&s/a!are serer application ;n a""lication that re(uires a security token for authentication
and authori<ation. ;n e-am"le is a SharePoint 2013 %eb a""lication that uses claims.based
authentication 4the default:.
SharePoint 2013 su""orts claims.based identity and authentication for the follo%in& entities#
-sers The validation of a user2s identity a&ainst a store of accounts and attributes that contains the
user=s credentials and can verify that the user submitted them correctly. >ser authentication occurs
%hen a user attem"ts to access a SharePoint resource. 0or more information! see Plan for user
authentication methods in SharePoint 2013.
Apps The validation of the identity a remote a"" for SharePoint and the authori<ation of the a""
and an associated user to re(uest a secured SharePoint resource. ;"" authentication occurs %hen
an e-ternal com"onent of a SharePoint Store a"" or an ;"" *atalo& a""! such as a %eb server
that is located on the intranet or the $nternet! attem"ts to access a secured SharePoint resource.
0or more information! see Plan for a"" authentication in SharePoint 2013.
Serers The validation of a server2s re(uest for resources that is based on a trust bet%een the
STS of the server that runs SharePoint 2013 and the STS of another server that su""orts the
O;uth server.to.server "rotocol. ,ased on this trust relationshi"! a re(uestin& server can access
secured resources on the server that is runnin& SharePoint 2013 on behalf of a s"ecified user
account! subAect to server and user "ermissions. 0or more information! see Plan for server.to.
server authentication in SharePoint 2013.
Metho$s of a#thori.ation
;fter authentication succeeds! an a""lication must determine %hether the entity is authori<ed to access
the re(uested resource. To "erform this analysis! the a""lication com"ares the identity information
about the entityGsuch as the user name and the &rou"s for %hich it is a memberGin the security token
4for claims.based identity: or +erberos ticket to the list of default or confi&ured "ermissions for the
resource bein& accessed.
88
Permissions are settin&s that s"ecify an entity 4such as a user or &rou" name: and %hat that entity is
allo%ed or not allo%ed to do 4such as read! edit! or delete files in a shared folder:. To obtain access to
the resources! the confi&ured "ermissions must "ermit the ty"e of access that the entity re(uests.
SharePoint 2013 "rovides "ermissions for users to access %eb a""lications and their resources! server
"ermissions for server.to.server resource re(uests! and a"" "ermissions for a"" resource re(uests.
0or more information about ho% to "lan for "ermissions in SharePoint 2013! see Permissions "lannin&
for sites and content and Plan a"" "ermissions mana&ement.
Metho$s to store( s)nchroni.e( an$ $ispla) entit) attrib#tes
To confi&ure "ermissions! the identity mana&ement system must obtain the list of entities from a
stora&e location and dis"lay them for you. $f that stora&e location is not the ori&inal store of accounts
and attributes! the entity information must be synchroni<ed %ith that store and re"licated to other
com"uters.
$n SharePoint 2013! the facility that dis"lays entity information for "ermissions confi&uration is Peo"le
Picker and the service that collects! synchroni<es! and re"licates local entity information is the >ser
Profile a""lication service.
0or more information! see Peo"le Picker and claims "roviders overvie% and >ser Profile service
a""lication overvie%.
See Also
Plan for user authentication methods in SharePoint 2013
Plan for a"" authentication in SharePoint 2013
Plan for server.to.server authentication in SharePoint 2013
Permissions "lannin& for sites and content
Plan a"" "ermissions mana&ement
Peo"le Picker and claims "roviders overvie%
>ser Profile service a""lication overvie%

8I
Test lab g#i$es for SharePoint Serer 2013
-p$ate$% 1ctober 2( 2012
S#&&ar)% 0ind the set of Test ab 3uides 4T3s: for SharePoint Server 2013 to &ain valuable hands.
on e-"erience before "lannin& and de"loyment.
-pplies to; $hare4oint $erver ()*6
The follo%in& articles on TechNet and related resources "rovide information about T3s for SharePoint
Server 2013.
Tech7et articles abo#t T3Gs for SharePoint Serer
2013
The follo%in& articles about the set of T3s for SharePoint Server 2013 are available to vie% online.
?riters u"date articles on a continuin& basis as ne% information becomes available and as users
"rovide feedback.

Content 2escription

Test ab 3uide# *onfi&ure
SharePoint Server 2013 in a
Three.Tier 0arm
/escribes the ste"s to confi&ure
a 3.tier farm 4%eb front.end!
a""lication! and database tiers:
usin& SharePoint Server 2013.
Test ab 3uide# /emonstrate
$ntranet *ollaboration for
SharePoint Server 2013
/escribes the ste"s to confi&ure
and demonstrate intranet
collaboration features in the
SharePoint Server 2013 3.tier
farm test lab.
Test ab 3uide# /emonstrate
Social 0eatures for SharePoint
Server 2013
/escribes the ste"s to confi&ure
and demonstrate the ne% social
features in SharePoint Server
2013 4'y Sites! Ne%sfeeds!
*ommunity Sites! and Team Site
feeds: in the SharePoint Server
2013 3.tier farm test lab.
Test ab 3uide# /emonstrate
S;'.based *laims
;uthentication %ith SharePoint
Server 2013
/escribes the ste"s to confi&ure
and demonstrate Security
;ssertion 'arku" an&ua&e
4S;':.based claims usin&
;ctive /irectory 0ederation
8J
Content 2escription
Services 4;/ 0S: 2.0 in the
SharePoint Server 2013 3.tier
farm test lab.
Test ab 3uide# /emonstrate
forms.based claims
authentication for SharePoint
Server 2013
/escribes the ste"s to confi&ure
and demonstrate forms.based
authentication in the SharePoint
Server 2013 3.tier farm test lab.

A$$itional reso#rces abo#t T3Gs
The follo%in& resources about T3s are available.

Content 2escription

Test ab 3uides
4htt"#55microsoft.com5testlab&ui
des:
SharePoint Server 2013 Test
ab
$nstallation and de"loyment for
SharePoint 2013 $T "ros
1esource *enter
Hisit the central Test ab
3uides "ortal in the TechNet
?iki for a descri"tion of T3
content and links to all the
"ublished T3s.
Hisit this "ortal "a&e in the
TechNet ?iki for all of the
T3 content for SharePoint
Server 2013.
Hisit the 1esource *enter to
access videos! community
sites! documentation! and
more.
0logs

'icrosoft Test lab 3uides
Hisit this blo& for the latest
information about T3 content
"ublished across 'icrosoft.


8K
Test 3ab G#i$e% Config#re SharePoint Serer
2013 in a Three/Tier 9ar&
-p$ate$% 1ctober 2( 2012
S#&&ar)% earn ho% to install and confi&ure SharePoint Server 2013 on multi"le servers %ith
'icrosoft SC Server 2012 usin& the com"uters in the ,ase *onfi&uration test lab.
-pplies to; $hare4oint $erver ()*6
This document is the Test ab 3uide version of the "rocedures that are described in 'ulti"le servers for
a three.tier farm.
This document contains instructions for the follo%in&#
1. *onfi&urin& the ,ase *onfi&uration test lab.
2. $nstallin& and confi&urin& a ne% server named SC1.
3. $nstallin& SC Server 2012 on the SC1 server.
9. $nstallin& SharePoint Server 2013 on the ;PP1 server.
D. $nstallin& and confi&urin& a ne% server named ?0E1.
8. $nstallin& SharePoint Server 2013 on ?0E1.
I. /emonstratin& the facilities of the default *ontoso team site on ?0E1.
2o!nloa$ the test lab g#i$e
Test ab 3uide# *onfi&ure SharePoint Server 2013 Previe% in a Three.Tier 0arm
See Also
'ulti"le servers for a three.tier farm
Test ab 3uides

I0
Test 3ab G#i$e% 2e&onstrate Intranet
Collaboration for SharePoint Serer 2013
-p$ate$% 1ctober 2( 2012
S#&&ar)% earn ho% to confi&ure and demonstrate the intranet collaboration features of SharePoint
Server 2013 based on the Test ab 3uide# *onfi&ure SharePoint Server 2013 in a Three.Tier 0arm.
-pplies to; $hare4oint $erver ()*6
This document is the Test ab 3uide version of the confi&uration described in the Corporate Portal
!ith <ost/7a&e$ Sites desi&n sam"le! %hich can be found in Technical dia&rams.
This document contains instructions for the follo%in&#
1. Settin& u" the SharePoint Server 2013 three.tier farm test lab.
2. *onfi&urin& the intranet collaboration features on ;PP1.
3. /emonstratin& the intranet collaboration features on ;PP1.
2o!nloa$ the test lab g#i$e
Test ab 3uide# /emonstrate $ntranet *ollaboration %ith SharePoint Server 2013 Previe%
See Also
Technical dia&rams
Test ab 3uides

I1
Test 3ab G#i$e% 2e&onstrate Social 9eat#res
for SharePoint Serer 2013
P#blishe$% Septe&ber 1C( 2012
S#&&ar)% earn ho% to confi&ure and demonstrate the ne% social features of SharePoint Server 2013
based on the Test ab 3uide# *onfi&ure SharePoint Server 2013 in a Three.Tier 0arm.
-pplies to; $hare4oint $erver ()*6
This document is the Test ab 3uide version of the "rocedures described in *onfi&ure social com"utin&
features.
This document contains instructions for the follo%in&#
1. Settin& u" the SharePoint Server 2013 three.tier farm test lab.
2. *reate a 'y Site site collection and confi&ure settin&s.
3. *onfi&ure 0ollo%in& settin&s.
9. *onfi&ure community sites.
D. *onfi&ure site feeds.
8. /emonstrate social features.
2o!nloa$ the test lab g#i$e
Test ab 3uide# /emonstrate Social 0eatures for SharePoint Server 2013 Previe%
See Also
*onfi&ure social com"utin& features
Test ab 3uides

I2
Test 3ab G#i$e% 2e&onstrate SAM3/base$
Clai&s A#thentication !ith SharePoint Serer
2013
-p$ate$% 1ctober 2( 2012
S#&&ar)% earn ho% to confi&ure and demonstrate Security ;ssertion 'arku" an&ua&e 4S;':.
based claims authentication %ith ;ctive /irectory 0ederation Services 4;/ 0S: 2.0 and SharePoint
Server 2013 based on the Test ab 3uide# *onfi&ure SharePoint Server 2013 in a Three.Tier 0arm.
-pplies to; $hare4oint $erver ()*6
This document is the Test ab 3uide version of the confi&uration described in *onfi&ure S;'.based
claims authentication %ith ;/ 0S.
This document contains instructions for the follo%in&#
1. Settin& u" the SharePoint Server 2013 three.tier farm test lab.
2. *onfi&urin& ;/ 0S 2.0.
3. *onfi&urin& S;'.based claims authentication.
9. /emonstratin& S;'.based claims authentication.
2o!nloa$ the test lab g#i$e
Test ab 3uide# /emonstrate S;'.based *laims ;uthentication %ith SharePoint Server 2013 Previe%
See Also
*onfi&ure S;'.based claims authentication %ith ;/ 0S
Test ab 3uides

I3
Test 3ab G#i$e% 2e&onstrate for&s/base$
clai&s a#thentication for SharePoint Serer
2013
P#blishe$% Septe&ber 1C( 2012
S#&&ar)% earn ho% to confi&ure and demonstrate form.based authentication for SharePoint Server
2013 based on the Test ab 3uide# *onfi&ure SharePoint Server 2013 in a Three.Tier 0arm.
-pplies to; $hare4oint $erver ()*6
This document is the Test ab 3uide version of the confi&uration described in *onfi&ure forms.based
authentication for a claims.based %eb a""lication.
This document contains instructions for the follo%in&#
1. Settin& u" the SharePoint Server 2013 three.tier farm test lab.
2. *onfi&urin& forms.based authentication.
3. /emonstratin& forms.based authentication.
2o!nloa$ the test lab g#i$e
Test ab 3uide# /emonstrate 0orms.based ;uthentication %ith SharePoint Server 2013
See Also
*onfi&ure forms.based authentication for a claims.based %eb a""lication
Test ab 3uides

I9