20332B ENU TrainerHandbook

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

O F F I C I A L M I C R O S O F T L E A R N I N G P R O D U C T
20332B
Advanced Solutions of Microsoft
SharePoint Server 2013

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
ii Advanced Solutions of Microsoft SharePoint Server 2013
Information in this document, including URL and other Internet Web site references, is subject to change
without notice. Unless otherwise noted, the example companies, organizations, products, domain names,
e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with
any real company, organization, product, domain name, e-mail address, logo, person, place or event is
intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the
user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in
or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property
rights covering subject matter in this document. Except as expressly provided in any written license
agreement from Microsoft, the furnishing of this document does not give you any license to these
patents, trademarks, copyrights, or other intellectual property.
The names of manufacturers, products, or URLs are provided for informational purposes only and
Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding
these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a
manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links
may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not
responsible for the contents of any linked site or any link contained in a linked site, or any changes or
updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission
received from any linked site. Microsoft is providing these links to you only as a convenience, and the
inclusion of any link does not imply endorsement of Microsoft of the site or the products contained
therein.
2013 Microsoft Corporation. All rights reserved.
Microsoft and the trademarks listed at
http://www.microsoft.com/about/legal/en/us/IntellectualProperty/Trademarks/EN-US.aspx are trademarks of
the Microsoft group of companies. All other trademarks are property of their respective owners

Product Number: 20332B
Part Number (if applicable): X18-76964
Released: 06/2013

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

MICROSOFT LICENSE TERMS
MICROSOFT INSTRUCTOR-LED COURSEWARE

These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its
affiliates) and you. Please read them. They apply to your use of the content accompanying this agreement which
includes the media on which you received it, if any. These license terms also apply to Trainer Content and any
updates and supplements for the Licensed Content unless other terms accompany those items. If so, those terms
apply.

BY ACCESSING, DOWNLOADING OR USING THE LICENSED CONTENT, YOU ACCEPT THESE TERMS.
IF YOU DO NOT ACCEPT THEM, DO NOT ACCESS, DOWNLOAD OR USE THE LICENSED CONTENT.

If you comply with these license terms, you have the rights below for each license you acquire.

1. DEFINITIONS.

a. Authorized Learning Center means a Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, or such other entity as Microsoft may designate from time to time.

b. Authorized Training Session means the instructor-led training class using Microsoft Instructor-Led
Courseware conducted by a Trainer at or through an Authorized Learning Center.

c. Classroom Device means one (1) dedicated, secure computer that an Authorized Learning Center owns
or controls that is located at an Authorized Learning Centers training facilities that meets or exceeds the
hardware level specified for the particular Microsoft Instructor-Led Courseware.

d. End User means an individual who is (i) duly enrolled in and attending an Authorized Training Session
or Private Training Session, (ii) an employee of a MPN Member, or (iii) a Microsoft full-time employee.

e. Licensed Content means the content accompanying this agreement which may include the Microsoft
Instructor-Led Courseware or Trainer Content.

f. Microsoft Certified Trainer or MCT means an individual who is (i) engaged to teach a training session
to End Users on behalf of an Authorized Learning Center or MPN Member, and (ii) currently certified as a
Microsoft Certified Trainer under the Microsoft Certification Program.

g. Microsoft Instructor-Led Courseware means the Microsoft-branded instructor-led training course that
educates IT professionals and developers on Microsoft technologies. A Microsoft Instructor-Led
Courseware title may be branded as MOC, Microsoft Dynamics or Microsoft Business Group courseware.

h. Microsoft IT Academy Program Member means an active member of the Microsoft IT Academy
Program.

i. Microsoft Learning Competency Member means an active member of the Microsoft Partner Network
program in good standing that currently holds the Learning Competency status.

j. MOC means the Official Microsoft Learning Product instructor-led courseware known as Microsoft
Official Course that educates IT professionals and developers on Microsoft technologies.

k. MPN Member means an active silver or gold-level Microsoft Partner Network program member in good
standing.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

l. Personal Device means one (1) personal computer, device, workstation or other digital electronic device
that you personally own or control that meets or exceeds the hardware level specified for the particular
Microsoft Instructor-Led Courseware.

m. Private Training Session means the instructor-led training classes provided by MPN Members for
corporate customers to teach a predefined learning objective using Microsoft Instructor-Led Courseware.
These classes are not advertised or promoted to the general public and class attendance is restricted to
individuals employed by or contracted by the corporate customer.

n. Trainer means (i) an academically accredited educator engaged by a Microsoft IT Academy Program
Member to teach an Authorized Training Session, and/or (ii) a MCT.

o. Trainer Content means the trainer version of the Microsoft Instructor-Led Courseware and additional
supplemental content designated solely for Trainers use to teach a training session using the Microsoft
Instructor-Led Courseware. Trainer Content may include Microsoft PowerPoint presentations, trainer
preparation guide, train the trainer materials, Microsoft One Note packs, classroom setup guide and Pre-
release course feedback form. To clarify, Trainer Content does not include any software, virtual hard
disks or virtual machines.

2. USE RIGHTS. The Licensed Content is licensed not sold. The Licensed Content is licensed on a one copy
per user basis, such that you must acquire a license for each individual that accesses or uses the Licensed
Content.

2.1 Below are five separate sets of use rights. Only one set of rights apply to you.

a. If you are a Microsoft IT Academy Program Member:
i. Each license acquired on behalf of yourself may only be used to review one (1) copy of the Microsoft
Instructor-Led Courseware in the form provided to you. If the Microsoft Instructor-Led Courseware is
in digital format, you may install one (1) copy on up to three (3) Personal Devices. You may not
install the Microsoft Instructor-Led Courseware on a device you do not own or control.
ii. For each license you acquire on behalf of an End User or Trainer, you may either:
1. distribute one (1) hard copy version of the Microsoft Instructor-Led Courseware to one (1) End
User who is enrolled in the Authorized Training Session, and only immediately prior to the
commencement of the Authorized Training Session that is the subject matter of the Microsoft
Instructor-Led Courseware being provided, or
2. provide one (1) End User with the unique redemption code and instructions on how they can
access one (1) digital version of the Microsoft Instructor-Led Courseware, or
3. provide one (1) Trainer with the unique redemption code and instructions on how they can
access one (1) Trainer Content,
provided you comply with the following:
iii. you will only provide access to the Licensed Content to those individuals who have acquired a valid
license to the Licensed Content,
iv. you will ensure each End User attending an Authorized Training Session has their own valid licensed
copy of the Microsoft Instructor-Led Courseware that is the subject of the Authorized Training
Session,
v. you will ensure that each End User provided with the hard-copy version of the Microsoft Instructor-
Led Courseware will be presented with a copy of this agreement and each End User will agree that
their use of the Microsoft Instructor-Led Courseware will be subject to the terms in this agreement
prior to providing them with the Microsoft Instructor-Led Courseware. Each individual will be required
to denote their acceptance of this agreement in a manner that is enforceable under local law prior to
their accessing the Microsoft Instructor-Led Courseware,
vi. you will ensure that each Trainer teaching an Authorized Training Session has their own valid
licensed copy of the Trainer Content that is the subject of the Authorized Training Session,
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

vii. you will only use qualified Trainers who have in-depth knowledge of and experience with the
Microsoft technology that is the subject of the Microsoft Instructor-Led Courseware being taught for
all your Authorized Training Sessions,
viii. you will only deliver a maximum of 15 hours of training per week for each Authorized Training
Session that uses a MOC title, and
ix. you acknowledge that Trainers that are not MCTs will not have access to all of the trainer resources
for the Microsoft Instructor-Led Courseware.

b. If you are a Microsoft Learning Competency Member:
User attending the Authorized Training Session and only immediately prior to the
commencement of the Authorized Training Session that is the subject matter of the Microsoft
Instructor-Led Courseware provided, or
2. provide one (1) End User attending the Authorized Training Session with the unique redemption
code and instructions on how they can access one (1) digital version of the Microsoft Instructor-
Led Courseware, or
3. you will provide one (1) Trainer with the unique redemption code and instructions on how they
can access one (1) Trainer Content,
iv. you will ensure that each End User attending an Authorized Training Session has their own valid
licensed copy of the Microsoft Instructor-Led Courseware that is the subject of the Authorized
Training Session,
v. you will ensure that each End User provided with a hard-copy version of the Microsoft Instructor-Led
Courseware will be presented with a copy of this agreement and each End User will agree that their
use of the Microsoft Instructor-Led Courseware will be subject to the terms in this agreement prior to
providing them with the Microsoft Instructor-Led Courseware. Each individual will be required to
denote their acceptance of this agreement in a manner that is enforceable under local law prior to
vi. you will ensure that each Trainer teaching an Authorized Training Session has their own valid
licensed copy of the Trainer Content that is the subject of the Authorized Training Session,
vii. you will only use qualified Trainers who hold the applicable Microsoft Certification credential that is
the subject of the Microsoft Instructor-Led Courseware being taught for your Authorized Training
Sessions,
viii. you will only use qualified MCTs who also hold the applicable Microsoft Certification credential that is
the subject of the MOC title being taught for all your Authorized Training Sessions using MOC,
ix. you will only provide access to the Microsoft Instructor-Led Courseware to End Users, and
x. you will only provide access to the Trainer Content to Trainers.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

c. If you are a MPN Member:
User attending the Private Training Session, and only immediately prior to the commencement
of the Private Training Session that is the subject matter of the Microsoft Instructor-Led
Courseware being provided, or
2. provide one (1) End User who is attending the Private Training Session with the unique
redemption code and instructions on how they can access one (1) digital version of the
Microsoft Instructor-Led Courseware, or
3. you will provide one (1) Trainer who is teaching the Private Training Session with the unique
redemption code and instructions on how they can access one (1) Trainer Content,
iv. you will ensure that each End User attending an Private Training Session has their own valid licensed
copy of the Microsoft Instructor-Led Courseware that is the subject of the Private Training Session,
v. you will ensure that each End User provided with a hard copy version of the Microsoft Instructor-Led
Courseware will be presented with a copy of this agreement and each End User will agree that their
use of the Microsoft Instructor-Led Courseware will be subject to the terms in this agreement prior to
providing them with the Microsoft Instructor-Led Courseware. Each individual will be required to
denote their acceptance of this agreement in a manner that is enforceable under local law prior to
vi. you will ensure that each Trainer teaching an Private Training Session has their own valid licensed
copy of the Trainer Content that is the subject of the Private Training Session,
vii. you will only use qualified Trainers who hold the applicable Microsoft Certification credential that is
the subject of the Microsoft Instructor-Led Courseware being taught for all your Private Training
Sessions,
viii. you will only use qualified MCTs who hold the applicable Microsoft Certification credential that is the
subject of the MOC title being taught for all your Private Training Sessions using MOC,
ix. you will only provide access to the Microsoft Instructor-Led Courseware to End Users, and
x. you will only provide access to the Trainer Content to Trainers.

d. If you are an End User:
For each license you acquire, you may use the Microsoft Instructor-Led Courseware solely for your
personal training use. If the Microsoft Instructor-Led Courseware is in digital format, you may access the
Microsoft Instructor-Led Courseware online using the unique redemption code provided to you by the
training provider and install and use one (1) copy of the Microsoft Instructor-Led Courseware on up to
three (3) Personal Devices. You may also print one (1) copy of the Microsoft Instructor-Led Courseware.
You may not install the Microsoft Instructor-Led Courseware on a device you do not own or control.

e. If you are a Trainer.
i. For each license you acquire, you may install and use one (1) copy of the Trainer Content in the
form provided to you on one (1) Personal Device solely to prepare and deliver an Authorized
Training Session or Private Training Session, and install one (1) additional copy on another Personal
Device as a backup copy, which may be used only to reinstall the Trainer Content. You may not
install or use a copy of the Trainer Content on a device you do not own or control. You may also
print one (1) copy of the Trainer Content solely to prepare for and deliver an Authorized Training
Session or Private Training Session.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

ii. You may customize the written portions of the Trainer Content that are logically associated with
instruction of a training session in accordance with the most recent version of the MCT agreement.
If you elect to exercise the foregoing rights, you agree to comply with the following: (i)
customizations may only be used for teaching Authorized Training Sessions and Private Training
Sessions, and (ii) all customizations will comply with this agreement. For clarity, any use of
customize refers only to changing the order of slides and content, and/or not using all the slides or
content, it does not mean changing or modifying any slide or content.

2.2 Separation of Components. The Licensed Content is licensed as a single unit and you may not
separate their components and install them on different devices.

2.3 Redistribution of Licensed Content. Except as expressly provided in the use rights above, you may
not distribute any Licensed Content or any portion thereof (including any permitted modifications) to any
third parties without the express written permission of Microsoft.

2.4 Third Party Programs and Services. The Licensed Content may contain third party programs or
services. These license terms will apply to your use of those third party programs or services, unless other
terms accompany those programs and services.

2.5 Additional Terms. Some Licensed Content may contain components with additional terms,
conditions, and licenses regarding its use. Any non-conflicting terms in those conditions and licenses also
apply to your use of that respective component and supplements the terms described in this agreement.

3. LICENSED CONTENT BASED ON PRE-RELEASE TECHNOLOGY. If the Licensed Contents subject
matter is based on a pre-release version of Microsoft technology (Pre-release), then in addition to the
other provisions in this agreement, these terms also apply:

a. Pre-Release Licensed Content. This Licensed Content subject matter is on the Pre-release version of
the Microsoft technology. The technology may not work the way a final version of the technology will
and we may change the technology for the final version. We also may not release a final version.
Licensed Content based on the final version of the technology may not contain the same information as
the Licensed Content based on the Pre-release version. Microsoft is under no obligation to provide you
with any further content, including any Licensed Content based on the final version of the technology.

b. Feedback. If you agree to give feedback about the Licensed Content to Microsoft, either directly or
through its third party designee, you give to Microsoft without charge, the right to use, share and
commercialize your feedback in any way and for any purpose. You also give to third parties, without
charge, any patent rights needed for their products, technologies and services to use or interface with
any specific parts of a Microsoft software, Microsoft product, or service that includes the feedback. You
will not give feedback that is subject to a license that requires Microsoft to license its software,
technologies, or products to third parties because we include your feedback in them. These rights
survive this agreement.

c. Pre-release Term. If you are an Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, MPN Member or Trainer, you will cease using all copies of the Licensed Content on
the Pre-release technology upon (i) the date which Microsoft informs you is the end date for using the
Licensed Content on the Pre-release technology, or (ii) sixty (60) days after the commercial release of the
technology that is the subject of the Licensed Content, whichever is earliest (Pre-release term).
Upon expiration or termination of the Pre-release term, you will irretrievably delete and destroy all copies
of the Licensed Content in your possession or under your control.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

4. SCOPE OF LICENSE. The Licensed Content is licensed, not sold. This agreement only gives you some
rights to use the Licensed Content. Microsoft reserves all other rights. Unless applicable law gives you more
rights despite this limitation, you may use the Licensed Content only as expressly permitted in this
agreement. In doing so, you must comply with any technical limitations in the Licensed Content that only
allows you to use it in certain ways. Except as expressly permitted in this agreement, you may not:
access or allow any individual to access the Licensed Content if they have not acquired a valid license
for the Licensed Content,
alter, remove or obscure any copyright or other protective notices (including watermarks), branding
or identifications contained in the Licensed Content,
modify or create a derivative work of any Licensed Content,
publicly display, or make the Licensed Content available for others to access or use,
copy, print, install, sell, publish, transmit, lend, adapt, reuse, link to or post, make available or
distribute the Licensed Content to any third party,
work around any technical limitations in the Licensed Content, or
reverse engineer, decompile, remove or otherwise thwart any protections or disassemble the
Licensed Content except and only to the extent that applicable law expressly permits, despite this
limitation.

5. RESERVATION OF RIGHTS AND OWNERSHIP. Microsoft reserves all rights not expressly granted to
you in this agreement. The Licensed Content is protected by copyright and other intellectual property laws
and treaties. Microsoft or its suppliers own the title, copyright, and other intellectual property rights in the
Licensed Content.

6. EXPORT RESTRICTIONS. The Licensed Content is subject to United States export laws and regulations.
You must comply with all domestic and international export laws and regulations that apply to the Licensed
Content. These laws include restrictions on destinations, end users and end use. For additional information,
see www.microsoft.com/exporting.

7. SUPPORT SERVICES. Because the Licensed Content is as is, we may not provide support services for it.

8. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this agreement if you fail
to comply with the terms and conditions of this agreement. Upon termination of this agreement for any
reason, you will immediately stop all use of and delete and destroy all copies of the Licensed Content in
your possession or under your control.

9. LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of the Licensed
Content. The third party sites are not under the control of Microsoft, and Microsoft is not responsible for
the contents of any third party sites, any links contained in third party sites, or any changes or updates to
third party sites. Microsoft is not responsible for webcasting or any other form of transmission received
from any third party sites. Microsoft is providing these links to third party sites to you only as a
convenience, and the inclusion of any link does not imply an endorsement by Microsoft of the third party
site.

10. ENTIRE AGREEMENT. This agreement, and any additional terms for the Trainer Content, updates and
supplements are the entire agreement for the Licensed Content, updates and supplements.

11. APPLICABLE LAW.
a. United States. If you acquired the Licensed Content in the United States, Washington state law governs
the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws
principles. The laws of the state where you live govern all other claims, including claims under state
consumer protection laws, unfair competition laws, and in tort.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

b. Outside the United States. If you acquired the Licensed Content in any other country, the laws of that
country apply.

12. LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws
of your country. You may also have rights with respect to the party from whom you acquired the Licensed
Content. This agreement does not change your rights under the laws of your country if the laws of your
country do not permit it to do so.

13. DISCLAIMER OF WARRANTY. THE LICENSED CONTENT IS LICENSED "AS-IS" AND "AS
AVAILABLE." YOU BEAR THE RISK OF USING IT. MICROSOFT AND ITS RESPECTIVE
AFFILIATES GIVES NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS. YOU MAY
HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT
CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT AND
ITS RESPECTIVE AFFILIATES EXCLUDES ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

14. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM
MICROSOFT, ITS RESPECTIVE AFFILIATES AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP
TO US$5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL,
LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.

This limitation applies to
o anything related to the Licensed Content, services, content (including code) on third party Internet
sites or third-party programs; and
o claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence,
or other tort to the extent permitted by applicable law.

It also applies even if Microsoft knew or should have known about the possibility of the damages. The
above limitation or exclusion may not apply to you because your country may not allow the exclusion or
limitation of incidental, consequential or other damages.

Please note: As this Licensed Content is distributed in Quebec, Canada, some of the clauses in this
agreement are provided below in French.

Remarque : Ce le contenu sous licence tant distribu au Qubec, Canada, certaines des clauses
dans ce contrat sont fournies ci-dessous en franais.

EXONRATION DE GARANTIE. Le contenu sous licence vis par une licence est offert tel quel . Toute
utilisation de ce contenu sous licence est votre seule risque et pril. Microsoft naccorde aucune autre garantie
expresse. Vous pouvez bnficier de droits additionnels en vertu du droit local sur la protection dues
consommateurs, que ce contrat ne peut modifier. La ou elles sont permises par le droit locale, les garanties
implicites de qualit marchande, dadquation un usage particulier et dabsence de contrefaon sont exclues.

LIMITATION DES DOMMAGES-INTRTS ET EXCLUSION DE RESPONSABILIT POUR LES
DOMMAGES. Vous pouvez obtenir de Microsoft et de ses fournisseurs une indemnisation en cas de dommages
directs uniquement hauteur de 5,00 $ US. Vous ne pouvez prtendre aucune indemnisation pour les autres
dommages, y compris les dommages spciaux, indirects ou accessoires et pertes de bnfices.
Cette limitation concerne:
tout ce qui est reli au le contenu sous licence, aux services ou au contenu (y compris le code)
figurant sur des sites Internet tiers ou dans des programmes tiers; et.
les rclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilit
stricte, de ngligence ou dune autre faute dans la limite autorise par la loi en vigueur.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

Elle sapplique galement, mme si Microsoft connaissait ou devrait connatre lventualit dun tel dommage. Si
votre pays nautorise pas lexclusion ou la limitation de responsabilit pour les dommages indirects, accessoires
ou de quelque nature que ce soit, il se peut que la limitation ou lexclusion ci-dessus ne sappliquera pas votre
gard.

EFFET JURIDIQUE. Le prsent contrat dcrit certains droits juridiques. Vous pourriez avoir dautres droits
prvus par les lois de votre pays. Le prsent contrat ne modifie pas les droits que vous confrent les lois de votre
pays si celles-ci ne le permettent pas.

Revised September 2012
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
x Advanced Solutions of Microsoft SharePoint Server 2013

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Advanced Solutions of Microsoft SharePoint Server 2013 xi
Acknowledgments
Microsoft Learning wants to acknowledge and thank the following for their contribution toward
developing this title. Their effort at various stages in the development has ensured that you have a good
classroom experience.
Jason Lee Content Developer
Jason Lee is a principal technologist with Content Master where he has been working with Microsoft
products and technologies for several years, specializing in SharePoint architecture and development.
Jason holds a PhD in computing and is currently MCPD and MCTS certified. You can read Jason's technical
blog at www.jrjlee.com.
James Hamilton-Adams Content Developer
James has been a trainer and consultant on Microsoft Technologies for over 10 years, and is an associate
technologist with CM Group. James specializes in SharePoint Server and Exchange Server, for which he
holds MCITP and MCSE certifications, in addition to working with other platforms, such as Project Server
and Lync. James has been working with SharePoint since the first release in 2001, and regularly works with
organizations to integrate SharePoint with their business processes.
John Devaney Content Developer
John Devaney is a principal technologist with Content Master and has worked with SharePoint products
and technologies since SharePoint Portal Server 2003. He worked on both Microsoft Office SharePoint
Server 2007 and SharePoint Server 2010 MOC curriculum for IT Pros. He is a SharePoint Server 2010
MCITP and has worked as an MCT.
Mike Sumsion Content Developer
Mike Sumsion is a senior technologist with Content Master, where he has worked with a range of
Microsoft technologies. Mike has worked with SharePoint products since Microsoft Office SharePoint
Server 2007, and has produced a variety of courseware, hands-on-labs, and other documentation. Michael
has an honors degree in Computer Science, and is currently MCTS certified. You can read Mike's blog at
www.mikesumsion.com.
Stephen Ryan Content Developer
Steve Ryan is a senior technologist in the Content Master IT Pro team with over 12 years experience in
training and technical authoring. He specializes in Windows Server operating systems and SharePoint, for
which he has MCITP, MCSE, and MCTS certifications.
Scott Jamison Technical Reviewer
Scott Jamison is Chief Architect and CEO at Jornata and SharePoint subject matter expert. Scott is a
recognized thought leader and published author with several books, hundreds of magazine articles, and
regular speaking engagements at events around the globe. Scott was one of the first professionals to hold
the Microsoft Certified Master for SharePoint certification and is currently both a SharePoint MVP and
Microsoft Certified Architect for SharePoint. You can follow Scott on Twitter via @sjam and at
www.scottjamison.com.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
xii Advanced Solutions of Microsoft SharePoint Server 2013
Contents
Module 1: Understanding the SharePoint 2013 Architecture
Lesson 1: Core Components of the SharePoint 2013 Architecture page 2
Lesson 2: New Features in SharePoint Server 2013 page 10
Lesson 3: SharePoint Server 2013 and SharePoint Online Editions page 17
Lab: Reviewing Core SharePoint Concepts page 21
Module 2: Designing Business Continuity Management Strategies.
Lesson 1: Designing Database Topologies for High Availability and
Disaster Recovery page 2
Lesson 2: Designing SharePoint Infrastructure for High Availability page 12
Lesson 3: Planning for Disaster Recovery page 17
Lab: Planning and Performing Backups and Restores page 28
Module 3: Planning and Implementing a Service Application Architecture
Lesson 1: Planning Service Applications page 2
Lesson 2: Designing and Configuring a Service Application Topology page 8
Lab A: Planning a Service Application Architecture page 17
Lesson 3: Configuring Service Application Federation page 18
Lab B: Federating Service Applications between SharePoint Server
Farms page 29
Module 4: Configuring and Managing Business Connectivity Services
Lesson 1: Planning and Configuring Business Connectivity Services page 2
Lesson 2: Configuring the Secure Store Service page 7
Lab A: Configuring BCS and the Secure Store Service page 12
Lesson 3: Managing Business Data Connectivity Models page 16
Lab B: Managing Business Data Connectivity Models page 19
Module 5: Connecting People
Lesson 1: Managing User Profiles page 2
Lesson 2: Enabling Social Interaction page 16
Lab A: Configuring Profile Synchronization and My Sites page 28
Lesson 3: Building Communities page 35
Lab B: Configuring Community Sites page 43
Module 6: Enabling Productivity and Collaboration
Lesson 1: Aggregating Tasks page 2
Lesson 2: Planning and Configuring Collaboration Features page 8
Lab A: Configuring Project Sites page 15
Lesson 3: Planning and Configuring Composite Solutions page 20
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Advanced Solutions of Microsoft SharePoint Server 2013 xiii
Lab B: Configuring Workflow page 26
Module 7: Planning and Configuring Business Intelligence
Lesson 1: Planning for Business Intelligence page 2
Lesson 2: Planning, Deploying and Managing Business Intelligence
Services page 10
Lab A: Configuring Excel Services page 22
Lesson 3: Planning and Configuring Advanced Analysis Tools page 26
Lab B: Configuring PowerPivot and Power View for SharePoint page 33
Module 8: Planning and Configuring Enterprise Search
Lesson 1: Configuring Search for an Enterprise Environment page 2
Lab A: Planning an Enterprise Search Deployment page 12
Lesson 2: Configuring the Search Experience page 14
Lesson 3: Optimizing Search page 23
Lab B: Managing Search Relevance in SharePoint Server 2013 page 31
Module 9: Planning and Configuring Enterprise Content Management
Lesson 1: Planning Content Management page 2
Lesson 2: Planning and Configuring eDiscovery page 8
Lab A: Configuring eDiscovery in SharePoint Server 2013 page 14
Lesson 3: Planning Records Management page 19
Lab B: Configuring Records Management in SharePoint Server 2013 page 24
Module 10: Planning and Configuring Web Content Management
Lesson 1: Planning and Implementing a Web Content Management
Infrastructure page 2
Lesson 2: Configuring Managed Navigation and Catalog Sites page 6
Lab A: Configuring Managed Navigation and Catalog Sites page 13
Lesson 3: Supporting Multiple Languages and Locales page 18
Lesson 4: Enabling Design and Customization page 23
Lesson 5: Supporting Mobile Users page 27
Lab B: Configuring Device Channels page 31
Module 11: Managing Solutions in SharePoint Server 2013
Lesson 1: Understanding the SharePoint Solution Architecture page 2
Lesson 2: Managing Sandbox Solutions page 8
Lab: Managing Solutions page 13
Module 12: Managing Apps for SharePoint Server 2013
Lesson 1: Understanding the SharePoint App Architecture page 2
Lesson 2: Provisioning and Managing Apps and App Catalogs page 5
Lab: Configuring and Managing SharePoint Apps page 11
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
xiv Advanced Solutions of Microsoft SharePoint Server 2013
Module 13: Developing a Plan for Governance
Lesson 1: Overview of Governance page 2
Lesson 2: Key Elements of a Governance Plan page 6
Lesson 3: Planning for Governance in SharePoint Server 2013 page 13
Lab A: Developing a Plan for Governance page 18
Lesson 4: Implementing Governance in SharePoint 2013 page 20
Lab B: Managing Site Creation and Deletion page 26
Module 14: Upgrading and Migrating to SharePoint Server 2013
Lesson 1: Preparing Upgrade or Migration Environment page 2
Lesson 2: Performing the Upgrade Process page 13
Lab A: Performing a Database-Attach Upgrade page 23
Lesson 3: Managing Site Collection Upgrade page 28
Lab B: Managing Site Collection Upgrades page 36
Lab Answer Keys
Module 1 Lab: Reviewing Core SharePoint Concepts page 1
Module 2 Lab: Planning and Performing Backups and Restores page 1
Module 3 Lab A: Planning a Service Application Architecture page 1
Module 3 Lab B: Federating Service Applications between SharePoint
Server Farms page 2
Module 4 Lab A: Configuring BCS and the Secure Store Service page 1
Module 4 Lab B: Managing Business Data Connectivity Models page 5
Module 5 Lab A: Configuring Profile Synchronization and My Sites page 1
Module 5 Lab B: Configuring Community Sites page 8
Module 6 Lab A: Configuring Project Sites page 1
Module 6 Lab B: Configuring Workflow page 6
Module 7 Lab A: Configuring Excel Services page 1
Module 7 Lab B: Configuring PowerPivot and Power View for
SharePoint page 6
Module 8 Lab A: Planning an Enterprise Search Deployment page 1
Module 8 Lab B: Managing Search Relevance in SharePoint Server
2013 page 2
Module 9 Lab A: Configuring eDiscovery in SharePoint Server 2013 page 1
Module 9 Lab B: Configuring Records Management in SharePoint
Server 2013 page 7
Module 10 Lab A: Configuring Managed Navigation and Catalog
Sites page 1
Module 10 Lab B: Configuring Device Channels page 7
Module 11 Lab: Managing Solutions page 1
Module 12 Lab: Configuring and Managing SharePoint Apps page 1
Module 13 Lab A: Developing a Plan for Governance page 1
Module 13 Lab B: Managing Site Creation and Deletion page 2
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Advanced Solutions of Microsoft SharePoint Server 2013 xv
Module 14 Lab A: Performing a Database-Attach Upgrade page 1
Module 14 Lab B: Managing Site Collection Upgrades page 6
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
About This Course i
About This Course
This section provides a brief description of the course, audience, suggested prerequisites, and course
objectives.
Course Description
Note: This release (B) MOC version of course 20332B has been developed on RTM software.
This course describes how to plan and configure advanced features in SharePoint Server 2013. The course
includes broad architectural and design-based content, including disaster recovery and high availability,
which underpins much of the knowledge required to manage a SharePoint deployment. The course
covers the various SharePoint 2013 workloads, for example, collaboration, productivity, and social
computing. The course then covers how to manage extensions and customizations. Finally, this course
covers planning and implementing governance, and upgrading SharePoint.
Audience
The course is targeted at experienced IT Professionals interested in learning how to install, configure,
deploy and manage SharePoint Server 2013 installations in either the data center or the cloud.
Students typically have more than four years of hands-on experience* planning and maintaining
SharePoint and other core technologies upon which SharePoint depends, including Windows Server 2008
R2 or later, Internet Information Services (IIS), SQL Server 2008 R2 or later, Active Directory, and
networking infrastructure services.
Students should have completed Course 20331: Core Solutions of Microsoft SharePoint Server 2013, or
have gained equivalent knowledge and experience, before taking this course.
The minimally qualified candidate typically:
Is an IT professional who plans, implements, and maintains a multi-server deployment of
SharePoint Server 2013.
Has a working knowledge of, and preferably hands-on experience, with SharePoint Online.
Has broad familiarity with SharePoint workloads.
Has experience with business continuity management, including data backup, restoration, and
high availability.
Has experience with authentication and security technologies.
Has experience with Windows PowerShell.
* Hands-on experience or job experience is considered a solutions-based role where the candidate works
within the solutions space covered by SharePoint, working on multiple solutions in the SharePoint space
that includes document management, content management, and search.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
ii About This Course
Student Prerequisites
An ideal student will have at least one year of experience with deploying and administering multiple
SharePoint 2010 farms across a large enterprise. Because many customers skipped upgrading from
SharePoint 2007, a student can also have at least 2 years of experience with SharePoint 2007 and
knowledge of the differences between 2007 and 2010, particularly the Service Application model. A
student can demonstrate the following skills:
Completion of Course 20331: Core Solutions of Microsoft SharePoint Server 2013, successful
completion of Exam 70-331: Core Solutions of Microsoft SharePoint 2013, or equivalent skills.
At least one years experience of mapping business requirements to logical and physical technical
design.
Working knowledge of network design, including network security.
Software management in a Windows 2008 R2 enterprise server or Windows Server 2012
environment.
Deploying and managing applications natively, virtually and in the cloud.
Administering Internet Information Services (IIS).
Configuring Active Directory for use in authentication, authorization and as a user store.
Managing an application remotely using Windows PowerShell 2.0.
Connecting applications to Microsoft SQL Server.
Implementing Claims-based security.
Course Objectives
After completing this course, students will be able to:
Describe the core features of SharePoint 2013.
Plan and design a SharePoint 2013 environment to meet the requirements for high availability and
disaster recovery.
Plan and implement a service application architecture for a SharePoint 2013 deployment.
Configure and manage Business Connectivity Services features in a SharePoint 2013 deployment.
Plan and configure social computing features.
Plan and configure productivity and collaboration platforms and features.
Plan and configure Business Intelligence solutions.
Optimize the search experience for an enterprise environment.
Plan and configure enterprise content management in a SharePoint 2013 deployment.
Plan and configure a web content management infrastructure to meet business requirements.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
About This Course iii
Manage solutions in a SharePoint 2013 deployment.
Configure and manage apps in a SharePoint Server 2013 environment.
Develop and implement a governance plan for SharePoint Server 2013.
Perform an upgrade or migration to SharePoint Server 2013.

Course Outline
The course outline is as follows:
Module 1, Understanding the SharePoint 2013 Architecture"
Module 2, Designing Business Continuity Management Strategies"
Module 3, Planning and Implementing a Service Application Architecture"
Module 4, Configuring and Managing Business Connectivity Services"
Module 5, Connecting People"
Module 6, Enabling Productivity and Collaboration"
Module 7, Planning and Configuring Business Intelligence"
Module 8, Planning and Configuring Enterprise Search"
Module 9, Planning and Configuring Enterprise Content Management"
Module 10, Planning and Configuring Web Content Management"
Module11, Managing Solutions in SharePoint Server 2013"
Module 12, Managing Apps for SharePoint Server 2013"
Module 13, Developing a Plan for Governance"
Module 14, Upgrading and Migrating to SharePoint Server 2013"

Course Materials
The following materials are included with your kit:
Course Handbook: a succinct classroom learning guide that provides the critical technical
information in a crisp, tightly-focused format, which is essential for an effective in-class learning
experience.
Lessons: guide you through the learning objectives and provide the key points that are critical to
the success of the in-class learning experience.
Labs: provide a real-world, hands-on platform for you to apply the knowledge and skills learned
in the module.
Module Reviews and Takeaways: provide on-the-job reference material to boost knowledge
and skills retention.
Lab Answer Keys: provide step-by-step lab solution guidance.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
iv About This Course
Course Companion Content: searchable, easy-to-browse digital content with integrated premium
online resources that supplement the Course Handbook.
Modules: include companion content, such as questions and answers, detailed demo steps and
additional reading links, for each lesson. Additionally, they include Lab Review questions and
answers and Module Reviews and Takeaways sections, which contain the review questions and
answers, best practices, common issues and troubleshooting tips with answers, and real-world
issues and scenarios with answers.
Resources: include well-categorized additional resources that give you immediate access to the
most current premium content on TechNet, MSDN, or Microsoft Press.
Student Course files: includes the Allfiles.exe, a self-extracting executable file that contains all
required files for the labs and demonstrations.
Course evaluation: at the end of the course, you will have the opportunity to complete an online
evaluation to provide feedback on the course, training facility, and instructor.
To provide additional comments or feedback on the course, send an email to
support@mscourseware.com. To inquire about the Microsoft Certification Program, send an
email to mcphelp@microsoft.com.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
About This Course v
Virtual Machine Environment
This section provides the information for setting up the classroom environment to support the business
scenario of the course.
Virtual Machine Configuration
In this course, you will use Microsoft Hyper-V to perform the labs.
The following table shows the role of each virtual machine that is used in this course:
Virtual machine Role
NYC-CL1 Windows 8 client computer for running Microsoft
Office applications.
NYC-DC1 Windows Server 2012 server acting as the domain
controller for the contoso.com domain.
NYC-DB1 Windows Server 2012 server running Microsoft
SQL Server 2012, a member of the contoso.com
domain.
NYC-SP1 Windows Server 2012 server running Microsoft
SharePoint Server 2013, a member of the
contoso.com domain.
NYC-FARM2 Windows Server 2012 server running Microsoft
SharePoint Server 2013 as an additional
SharePoint farm, a member of the contoso.com
domain.
Software Configuration
The following software is installed on each VM:
Microsoft Windows 8 Enterprise
Microsoft Office 2013
Microsoft Visio Professional 2013
Microsoft Windows Server 2012
Microsoft SharePoint Server 2013
Microsoft Office Web Apps
Microsoft SQL Server
Microsoft SQL Server Reporting Services
Microsoft SQL Server Analysis Services
Microsoft Project Server
Microsoft Project Professional
Microsoft Workflow Manager
Microsoft SharePoint Designer
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
vi About This Course
Course Files
The files associated with the labs in this course are located in the E:\ModXX\ folder on the student
computers.
Classroom Setup
Each classroom computer will have the same virtual machine configured in the same way.
Course Hardware Level
To ensure a satisfactory student experience, Microsoft Learning requires a minimum equipment
configuration for trainer and student computers in all Microsoft Certified Partner for Learning Solutions
(CPLS) classrooms in which Official Microsoft Learning Product courseware is taught.
Hardware Level 7
64 bit Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) processor (2.8 Ghz
dual core or better recommended)
Dual 500 GB hard disks 7200 RPM SATA or faster (striped).
16GB RAM.
DVD drive (dual layer recommended)
Network adapter with Internet connectivity
Dual SVGA monitors 17 or larger supporting 1440X900 minimum resolution
Video adapter that supports 1440 x 900 resolution
Microsoft Mouse or compatible pointing device
Sound card with amplified speakers
In addition, the instructor computer must be connected to a projection display device that supports SVGA
1024 x 768 pixels, 16 bit colors.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
1-1
Module 1
Understanding the SharePoint Server 2013 Architecture
Contents:
Module Overview 1-1
Lesson 1: Core Components of the SharePoint 2013 Architecture 1-2
Lesson 2: New Features in SharePoint Server 2013 1-10
Lesson 3: SharePoint Server 2013 and SharePoint Online Editions 1-17
Lab: Reviewing Core SharePoint Concepts 1-21
Module Review and Takeaways 1-28

Module Overview
The architectural components of SharePoint continue to evolve to meet the changing needs and
environments with each new version of the product.
This module introduces the architectural features that underpin Microsoft SharePoint Server 2013, both
for on-premise and online deployments. This includes an examination of the features that are new in this
version, as well as those that have been removed. This module reviews the basic structural elements of a
farm deployment, and the different deployment options that are available in SharePoint 2013.
Objectives
After completing this module, you will be able to:
Describe the architectural features of SharePoint Server 2013.
Identify new and deprecated features in SharePoint 2013.
Describe the editions for SharePoint Server 2013 on-premises and SharePoint Online.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
1-2 Understanding the SharePoint Server 2013 Architecture
Lesson 1
Core Components of the SharePoint 2013 Architecture
SharePoint 2013 is broadly built on the systems architecture developed with SharePoint Server 2010.
There have been enhancements in all areas, and radical redesign in some. Irrespective of the changes in
SharePoint 2013, it is essential that you have a good understanding of the core SharePoint 2013
architectural components in order to successfully plan and design a SharePoint deployment. These
components include:
Information architecture.
Logical architecture.
Service applications.
Search.
Physical architecture.
Lesson Objectives
After completing this lesson, you will be able to:
Describe the role of information architecture in a SharePoint 2013 design.
Describe the SharePoint 2013 logical architecture and the components that affect farm design.
Describe the service application architecture and the new services available in SharePoint 2013.
Describe the revised search architecture.
Explain the physical architecture requirements in SharePoint 2013.
Information Architectures
An information architecture (IA) defines the means
by which information in an organization is
cataloged. The most widely used information
architecture in the world is the Dewey Decimal
Classification system, which is used to structure
books in libraries. The goals of an information
architecture are to ensure information:
Usability. This balances the twin needs of
storing content by contributors and ensuring
its discoverability by consumers.
Maintainability. New content types, such as
new products, services, or functionality, must
be easy to integrate into an information architecture. For all organizations, change is a constant. If
your information architecture is too rigid, it may make it difficult to accommodate changes to
content.
Extensibility. Although your information architecture is platform-independent, you must ensure that it
conforms to the software, security, and management boundaries of SharePoint Server 2013. There is
no point in creating an IA solution that cannot fit into your organizations chosen platform.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Advanced Solutions of Microsoft SharePoint Server 2013 1-3
When planning your information architecture, it is important to understand the SharePoint Server 2013
container hierarchy. The term container refers to the logical structures that make up SharePoint Server
2013. The container hierarchy, from top to bottom, is as follows:
Farm
Web applications
Site collections
Sites
List and libraries
The features of SharePoint Server 2013 that are most closely associated with information architecture
include:
The Managed Metadata Service. This stores and publishes common metadata items for use by an
entire organization or divisions of the organization. With SharePoint Server 2013, you can publish this
information globally or for specific groups by deploying multiple instances of the Managed Metadata
Service.
Site columns. You can create custom columns to hold information such as metadata or item data.
Using custom columns, you can choose the data type for the column and specify the information that
the column stores.
Content types. These are a powerful method for creating content of a certain type and associating
columns, metadata, document templates, information management policies, or workflows with that
type of item.
Term sets. These provide the ability to tag information to improve usage clarity by means of both
managed and unmanaged lists of terms. Managed lists are provisioned and maintained by a central
function; unmanaged lists provide flexibility for users to add personal comments. The term sets use
the Managed Metadata column to add metadata information that is surfaced as part of a documents
properties.
Information management policies. These enable you to specify settings for document or item behavior
regarding retention, auditing, barcoding, and labeling.
Your information architecture can also be used to drive navigation. Metadata navigation presents users
with navigation options that are based on tags applied by contributors to their content. This delivers
results that are filtered, or refined by the taxonomy delivered by Managed Metadata columns.
Logical Architecture
Logical architecture is closely associated with
information architecture. The logical architecture
documents the nonphysical structure of a solution,
designed to fulfill business requirements.
The logical architecture does not specify any
server-related functionality, such as the amount or
size of server hardware. Rather, it reflects how you
structure the information architecture within the
non-physical components of SharePoint 2013.
Some may feel that logical architecture is platform
agnostic, but as a matter of practicality, you must
develop your logical architecture based on the
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
platform structures.
The SharePoint Server 2013 logical architecture has the following core components that will influence
your design:
Server farms. A server farm is a collection of servers acting as a single top-level logical unit. These
represent the top-level element of a design. The number of farms needed to fulfill your logical
requirements are affected by elements such as:
o Separate operational divisions of responsibility.
o Dedicated funding sources.
o Separate data center locations.
o Regulatory requirements for physical isolation between sites.
Service applications. These provide resources that can be shared across sites in a farm or across
multiple farms.
Application pools. These are groups of one or more URLs that a worker process or a set of worker
processes serves.
Web applications. A web application is an IIS website that SharePoint Server 2013 creates and uses.
You can extend a web application up to four times to create additional zones in SharePoint Server
2013, which results in up to five IIS websites that are associated with a single web application. Each IIS
website is associated with a different zone, and you can assign a unique domain name to each.
Zones. These represent different logical paths (URLs) to gain access to the same web application.
Content databases. All content for a web application is stored in one or more content databases. You
can separate content into multiple content databases at the site collection level. A content database
can include one or more site collections.
Site collections. This is perhaps the most important SharePoint logical design element. Site collections
are a logical set of SharePoint sites that share the same top-level site and certain administrative
settings. Site collections are the highest level of logical containment within SharePoint.
Sites. A site is a logical unit of containment that contains lists and libraries, permission levels, and
configuration settings.
Lists and libraries. A list (or library) is a logical container that holds a collection of similar items such as
contacts, appointments, and documents.
Items. An item is the most granular logical element in SharePoint, and represents a singular unit of
content.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Service Application Architecture
The service application architecture, which
replaced the Shared Service Provider (SSP) model
of Microsoft Office SharePoint Server (MOSS)
2007, remains in SharePoint Server 2013. This has
been extended with new service applications to
enhance the capabilities of the platform.
Service applications, as defined earlier, provide
services to SharePoint Server 2013 users and other
applications. These include access to application
functionality with Microsoft Excel 2013, Microsoft
Visio 2013, or underlying services such as the
Managed Metadata Service (MMS) or the Business
Connectivity Services (BCS). The framework of the service application architecture in SharePoint 2013 is
designed to enable architects to select only the services that are required to deliver a business solution.
From a basic management viewpoint, a service application has the following components:
An administrative interface, through which you can manage the associated service application.
An application pool.
A service database or databases, dependent on the requirements of the service.
One or more physical instancesthe service process running on a physical server.
SharePoint 2013 includes three new services:
App Management Service. SharePoint Server 2013 has embraced the app model, which has become
so familiar to mobile device users over the last few years. SharePoint Server 2013 provides a platform
for in-house or third-party apps to be used across an organization, with the service application
managing permissions and access to individual apps.
Machine Translation Service. The growth of SharePoint as a global platform is enhanced with the new
Machine Translation Service application. This provides automatic language translation of document
and site pages. This does not mean that SharePoint Server 2013 itself provides a translation engine.
When the Machine Translation Service application processes a translation request, the request is
forwarded to a cloud-based host that performs the actual translation. This is designed to integrate
with the existing Variations functionality.
Work Management Service. For business users, this service is designed to provide an integrated view
of their work. The tasks that users need to undertake are aggregated on the users My Site. These
tasks may be from the SharePoint server, or they may be from external systems, such as Microsoft
Exchange or Microsoft Project Server. The architecture of the Work Management Service is such that
it will be able to aggregated tasks from other environments in the future.
Services that have been deprecated or changed in SharePoint 2013 include:
Web Analytics Service. Rather than have this as a self-contained service application, the Web Analytics
functionality has been incorporated into the Search service.
Office Web Apps Service. Office Web Apps is now a separate server product.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Search Architecture
The Search service has been re-architected in
SharePoint 2013. The architecture changes have
been made to help ensure that Search offers a
higher level of redundancy for single and multiple
farm environments. One of the most obvious
changes in the new architecture is the inclusion of
the FAST technologies into the Search service. This
enhances search functionality, and also makes it
easier for solution architects to design and deploy
a full feature search solution in their organizations.
Search combines a range of elements on
application servers, which include:
Crawl Component
Content Processing Component
Analytics Processing Component
Indexing Component
Query Processing Component
Search Administration Component
These components interact to build the search index and respond to queries. To ingest data, the Crawl
Component interrogates the content sources that you have configured, either on the SharePoint farm or
on external sources, such as Microsoft Exchange or Lotus Notes. The crawled items are processed by the
Content Processing Component to format them appropriately to be stored on the index. Information from
the Analytics Processing Component is used in this process to identify useful associated item information,
such as previous user interaction. The data, or artifacts, are written to the index, which is a series of files
and folders that are stored on disk and referred to, collectively, as the index file. The Query Processing
Component receives queries from the Web Front End (WFE) server, it processes the query, and then it
sends it to the Indexing Component, which returns results sets. The Query Processing Component
performs additional processing to aggregate and clean the results and then sends the result sets back to
the WFE to be rendered for the user. Several temporary and permanent storage databases used
throughout the process.
In addition to the architectural changes, managing an enterprise search environment has been extended
in SharePoint 2013. In previous versions, the focus of search management has been at the service
application level by search administrators. Although this is still available, search management is now
available more widely for site collection administrators and site owners. This means that the search
management overhead for SharePoint 2013 farm and service application administrators is reduced, and
also that users can expect a more flexible response to change requests as core feature management is
delegated to administrative users.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Physical Architecture and Topologies
The physical architecture of SharePoint 2013 is
broadly consistent with that of SharePoint 2010,
although there are some revised
recommendations on sizing and capacity.
Server systems hardware
The server system specification recommends a 64-
bit, 4 cores processor with a minimum 12 GB of
memory (RAM), and a system drive of 80 GB. This
is for a general purpose Web Front End (WFE)
server and application server. For database servers,
you may need to adjust the specification for small,
medium, or large farm deployments. Clearly, you
must monitor your systems to ensure that they perform well.
Software
The software requirements are detailed on TechNet, but you should aim to implement SharePoint 2013
on Windows Server 2012 (Standard or Datacenter) with databases on the 64-bit edition of Microsoft SQL
Server 2012. You can still use Windows Server 2008 R2 Standard, Enterprise, or Datacenter with Service
Pack 1 and the 64-bit edition of SQL Server 2008 R2 Service Pack 1.
Additional Reading: For more information about hardware and software requirements for
SharePoint, see Hardware and software requirements for SharePoint 2013 at
http://go.microsoft.com/fwlink/?Linkid=299525
Storage
The capacity of SharePoint 2013 as a content storage and management platform means that you need to
thoroughly review your storage and data access requirements. The following storage architectures are
suitable for SharePoint 2013:
Direct attached storage (DAS), where hard disks are attached directly to the computer running SQL
Server.
Storage area network (SAN), which uses a network infrastructure to connect the computer running
SQL Server to the separate disk storage volumes.
Network attached storage (NAS) devices may be suitable, under certain circumstances, such as for
remote binary large object (BLOB) storage. However, this support is subject to precise NAS
specifications.
New to SharePoint 2013 is Shredded Storage. This new file save algorithm enhances performance by
minimizing the size or disk writes on a file save operation. Shredded Storage enables incremental file
updates, rather than always writing an entire file when saving, by breakingor shreddinga file into
pieces.
Single farm topologies
The topology of your SharePoint 2013 farm is important to designing and deploying an effective solution.
The general guidance for farm sizing is as follows:
Small farms. These farms typically have between two and approximately five servers, and they can
have two or three tiers. In a small, two-tier farm, the WFE server(s) also run service application
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
components such as search query and search crawl. A small farm can serve between 10,000 to 20,000
users depending on usage and service requirements.
Medium farms. These farms have between approximately five and 10 servers, separated into three
tiers. In medium farms, service applications are often spread out across a number of application
servers, with dedicated search servers. A medium farm can manage up to 40 million items. You can
extend a medium farm by having more than one database server, with the search databases
separated from other SharePoint databases.
Large farms. These farms typically start at approximately 10 servers and scale out. The
recommendation for scaling out a large farm is to group services or databases with similar
performance characteristics onto dedicated servers and then scale out the servers as a group.
Multiple farm topologies and cross-farm services
In SharePoint 2013, you can share some service applications among different farms in the same
organization. This enables you to unify or standardize certain service applicationrelated elements.
Cross-farm services are applications that can be shared independently with other farms. For example, an
organization may have two farms that both use the Managed Metadata Service to define metadata. Farm
A can use the local Managed Metadata Service and consume the Managed Metadata Service of Farm B,
which makes both sets of metadata available. You can repeat this configuration on Farm B so that both
farms can share metadata definitions.
SharePoint online deployment
SharePoint 2013 builds upon the improved options for hosting providers added in SharePoint 2010.
Improvements in logical architecture enable you to implement farm deployments that use a multi-
tenancy model. Multi-tenancy means that different companies can share a single farm environment.
Multi-tenancy makes use of the following features:
Using multiple web applications or host-header site collections to accommodate many disjoint
namespaces.
Using site subscriptions to enable grouping and administration of site collections by tenant. Site
subscriptions also help with service application connections.
Using service application partitioning to store service application data separately for different tenants.
SharePoint hybrid deployment
A hybrid SharePoint environment is one where an on-premises deployment integrates with a SharePoint
Online (Microsoft Office 365) platform to provide an integrated business environment. The level of
integration is determined by your organizations business requirements, but hybrid solutions most often
provide:
Federated search. You can provision access for users to business data from both cloud and on-
premises environments.
Business Connectivity Services. You can provision access to line-of-business data from applications in
SharePoint and external lists in SharePoint Online.
Single sign-on. You can enable a single authentication login for both environments to streamline user
access.
Directory synchronization. You can automatically synchronize user accounts in the on-premises Active
Directory Domain Services (AD DS) domain automatically with Office 365.
One-way or two-way server-to-server trust. You can configure trust relationships between the on-
premises and online environments to provision data connections.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Discussion: How Does SharePoint Server 2013 Architecture Affect Your
Organization?
How do you think the changes to SharePoint 2013
architectures may affect your organizations
environment?
Do you have a documented information
architecture and logical architecture?
Are you planning to implement the Apps
Management Service application? What will
this provide?
Do you provide search at present? Do you
think the additional delegated administration
will be used in your organization?
What SharePoint topology do you have at the moment or plan to have? Will you implement multiple
farms?
Does your organization use or plan to use SharePoint Online? What do you see as the advantages
and disadvantages of SharePoint in the cloud for your organization?

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
New Features in SharePoint Server 2013
SharePoint Server 2013 extends the functionality delivered by SharePoint Server 2010. Although there is a
lot that SharePoint administrators will recognize, SharePoint Server 2013 has new features for:
Business intelligence (BI).
Search.
Content management.
Mobile users.
Social computing.
SharePoint apps.
This lesson introduces many of the new features of SharePoint 2013 for administrators and end users, and
identifies which features have been deprecated.
Lesson Objectives
List some of the key new BI features in SharePoint 2013.
Describe the new Search features that build on the architecture changes in SharePoint 2013.
Describe new content management features added to SharePoint 2013.
Explain the new features that target mobile users in SharePoint 2013.
Describe the new community and My Sites features in SharePoint 2013.re in SharePoint 2013.
Explain the new SharePoint Apps architecture.
List the main features deprecated in SharePoint 2013.
Business Intelligence
SharePoint products and technologies have always
offered business intelligence (BI) functionality to
developers and users. Excel Services,
PerformancePoint Services, and Visio Services are
three of the key BI services. These continue to
provide the ability to surface both SharePoint
Server 2013 and line-of-business BI, but they are
improved in a number of ways. These are
complemented by extensions, such as Power View
for SharePoint and PowerPivot for SharePoint.
Excel Services
Improvements have been made to the Excel
Services web parts in the areas of PivotTables and PivotCharts, with an improved interface and enhanced
support for SQL Server Analysis Services (SSAS) or PowerPivot data models.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The Excel client application also supports new Excel Services functions, such as calculated measures and
calculated members functions using SSAS data, and the ability to support timeline controls for data
filtering by time.
PerformancePoint services
PerformancePoint dashboards now support themes and styles, and dashboards can be exported to other
sites or servers. Dashboards also now support the use of the Safari browser on iPads.
In addition, PerformancePoint now supports the EffectiveUserName property in SSAS, which means that
Kerberos authentication is no longer required to avoid the double-hop authentication issue.
Visio Services
Visio Services now provides the facility for users to add comments to full-page rendered drawings. This
ability enhances collaboration. The comments themselves are embedded in the Visio files, so they are also
available to the client application. The integration of Visio Services with external data connectivity has also
been enhanced to streamline authoring and security. To improve performance, Visio Services can now use
the MaxCacheSize parameter to better manage the use of system resources. Visio Services has also been
optimized, along with other SharePoint Server 2013 service applications, for use with touch-based device
interfaces, commonly found on smartphone and tablet devices.
Search
In addition to the overhaul of the Search service
architecture, SharePoint 2013 introduces
improvements to the user experience and search
operation.
The immediate, visual changes for users include:
Hover panel. This feature, familiar to FAST
users, lets users hover their mouse pointer
over a search result items and preview the
document content.
Result types. Results are displayed based on
their result type. For example, Microsoft Office
documents display the application icon in front of the result item title, while people in results show
the picture and their Lync availability status, if Lync functionality is available.
Result blocks. This renders a subset of results that are related, so PowerPoint documents returned in a
result set appear in a result block when the word "presentation" is one of the search terms. There are
a number of system-delivered result blocks, but administrators can add their own.
SharePoint 2013 delivers improved search result relevance in the following areas:
Ranking models. There are new ranking models for people search, intranet sites, and Internet sites,
which improve relevance.
Content analysis. SharePoint analyzes the relationships between pieces of content, their frequency in
result sets, and how often users click a search result item to improve result set relevance.
Administrators, both at the Search Service and site collection levels can provide suggestions and
popular sites.
Query rules. Query rules replace Best Bets to promote result items in a search, provide a mechanism
for adding result blocks to return against a query, and enable administrators to change result ranking.
These can be run at service, site application and site levels by administrators or site owners.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Result sources. In SharePoint 2013, result sources replace scopes and federated locations, which were
available in SharePoint Server 2010. There are a large number of supported result sources delivered
with SharePoint 2013.
For administrators, SharePoint 2013 introduces:
Continuous crawling. SharePoint 2013 introduces continuous crawling, a new option for managing
content source crawls. This is an additional option over the existing incremental and full crawls, so
you can still configure this as you would in SharePoint Server 2010. When you select the option to
crawl continuously, the content source is crawled every 15 minutes.
Display templates. Returned result types can be rendered in a specific display template, which defines
the appearance on screen, or visual layout, of the result type. The template itself is just HTML. This
means that your web designers can use any HTML editorSharePoint Designer, Dreamweaver, or
even Notepadto create the template. This change makes it easier for organizations with a big
investment in non-SharePoint web design to quickly create display templates for result types without
the need to train designers in SharePoint development tools.
Enhanced administration delegation. Far more of the search administration can be delegated to site
collectionand sometimes sitelevels, such as Search Schema management, Query Rule
development, and result type management.
Content Management
Management of business content is integral to the
success of any SharePoint implementation.
SharePoint 2013 continues to deliver Enterprise
Content Management (ECM) and Web Content
Management (WCM) improvements for all sizes of
enterprise deployments.
Enterprise Content Management
Records and document management has always
be a central feature of SharePoint products and
technologies. SharePoint Server 2013 provides
new and extended ECM facilities, including:
Site-level retention policies. This means that organizational compliance can be extended to sites. The
policies include a retention policy for sites and team mailboxes associated with a site, and the options
to define project closure and expiration policies. This means that you can now define when a site is
deleted or the workflows associated with the closure of a site, which may archive the site.
Discovery Center. This is designed for managing discovery cases and holds. It establishes a portal
through which you can access discovery cases to conduct searches, place content on hold, and export
content.
eDiscovery. This functionality has been extended, such that you can export discovered content from
Microsoft Exchange and SharePoint Server 2013 to file shares, where it can also be searched. This is
particularly useful if you need to provide information outside Exchange or SharePoint for legal
inspection.
Team Folders. SharePoint Server 2013 provides seamless integration of Microsoft Exchange and
SharePoint. This means you can create a team folder that gets an e-mail address and can receive mail,
which is then available to the entire team.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Web Content Management
WCM is a core function of SharePoint products and technologies. WCM is often regarded as a function of
Internet-facing sites. In fact, the majority of WCM users are focused on intranet, corporate information
sites. This means that WCM should be a default feature of just about all SharePoint Server 2013
implementations.
In SharePoint Server 2013, there is a greater emphasis on making interface development more accessible
to all developers. Rather than needing to have an in-depth knowledge of SharePoint architecture, the
interface designer can now concentrate on the HTML or CSS to build attractive sites that provide a better
user experience. This means that a larger number of common web development tools can be used to
develop SharePoint sites.
One of the most important features of WCM is the ability to detect user devicessmartphone, tablet,
laptop, and so forthand then render and optimize the same content into an appropriate screen format.
This is termed device channels in SharePoint 2013. Device channels use user agent strings to indicate the
device type of a browser that is attaching to a web server. The server can interpret the string and render
an appropriately formatted page to return to the device. You can configure the user agent string settings
in Device Settings on the Site Settings page.
SharePoint Server 2013 also provides:
Variations and content translation. SharePoint Server 2013 provides support for automated or manual
translation in variations and also in terms, by using the XLIFF file format. The translation content may
include documents, lists, pages, and navigation.
Search Engine Optimization (SEO). SEO is a critical component of Internet-facing website design.
SharePoint 2013 has refined a number of design and development issues, such as provision of:
o Clean URLs
o Country code top-level domains
o XML site maps
o SEO properties
Cross-site publishing. You can now define content to be available across site collections. This may
include documents rather than just defined lists. The content, which is available across site collections,
may be aggregated by using the Content by Search Web Part. You can also use catalog-enabled sites
for scenarios such as a content repositories, knowledge bases, or product catalogs.
Mobile Users
SharePoint Server 2013 offers new, optimized
viewing experiences across different mobile
platforms. Additionally, several new features were
added to help improve both worker productivity
and usability on the device. This functionality
includes the following:
Improved mobile browser experience.
SharePoint 2013 provides three options for
mobile browser users:
o Contemporary view. Renders in HTML5.
o Classic view. Renders in HTML or similar
markup language formats, to provide SharePoint 2010 backwards compatibility.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Full screen user interface. Renders a full desktop on a smartphone device.
Device channel identification and optimization. This provides the ability to have a single authored site
and its content mapped to master pages, page layouts, and cascading style sheets for multiple mobile
browsers.
Push notification. This facility enables you to develop event handler code to integrate with notification
services, such as the Microsoft Push Notification Service, to push information to registered devices.
Location. SharePoint Server 2013 supports a geolocation field type. This enables developers to create
location-aware applications for mobile users.
Business intelligence (BI). iPad users can render BI content such as PerformancePoint Web Parts and
Excel Services reports using the Safari web browser.
Office Web Apps. Although Office Web Apps is now a separate server productunlike the service
application that was available with SharePoint Server 2010the close integration with SharePoint
2013 means that users can have viewers called Word Mobile Viewer, Excel Mobile Viewer, and
PowerPoint Mobile Viewer to render documents for smartphones.
Additional Reading: For more information about new features for mobile device users, see
Overview of mobile devices and SharePoint Server 2013 at

Social Computing
SharePoint Server 2010 made great strides in
developing an enterprise solution for social
computing. This evolution continues in SharePoint
2013, with particular improvements in the
development of communities and My Sites.
Communities
Communities are new in SharePoint 2013. There
are two new site templates available to create
communities: Community Site and Community
Portal. The goal of these is to create environments
where people communicate naturally, and where
an enterprise can capture and provision
information in the most flexible manner. Much in the way that public communities thrive, the SharePoint
2013 Community Site enables user groups to establish moderated communities of common interests and
recognize expertise, though peer recognition, such as like or best answer tags. In addition to using a
Community Site template, you can enable community features on an existing site.
You can use the Community Portal to deploy multiple community sites for your organization. The portal is
a search-driven page that enables user to search for communities. The portal used all the functionality of
the new Search architecture to ensure speed and security for your users.
Additional Reading: For more information about configuring communities, see Create and
configure communities in SharePoint Server 2013 at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
My Sites
My Sites have existed in SharePoint Products and Technologies for more than a decade. In SharePoint
2013 My Sites have been enhanced with:
My Site document libraries. A users My Site is now the default location for saving content from Office
2013 applications. The goal is to make sure that content is available to be shared, rather than held on
a local disk, creating silos of business content. To work offline, a user can use SkyDrive Pro to
synchronize their My Site document library with their local disk. To enhance user adoption, the
security and data access model for My Site document libraries has been streamlined, so non-technical
users should find it much easier to provision access to documents in their document library.
Microblogging. SharePoint 2013 My Sites also provide a platform for microblogging so that people
can:
o Quickly post comment s and replies.
o Post images.
o Use hash tags (#) to define keywords that can be followed or searched.
o Use the @ symbol mentions to tag other users.
o Like comments or posts.
o Follow people, documents, sites, and tags.
Additional Reading: For more information about configuring My Sites, see Configure My
Sites in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302037
SharePoint Apps
In recent years, the concept of apps has created a
thriving new sector for the IT industry.
Independent developers can create relatively small
applications that provide solutions to user
requirements. SharePoint Server 2013 has
embraced this development with the new App
Management service application. This is, arguably,
the most radical change in the SharePoint Server
2013 architecture model. Apps do not replace
solutionspackaged (.wsp) files that provide
customizations or enhancements to SharePoint
sitesbut their ease of use will make them more
popular, especially with end users. It is probable that SharePoint development will follow the same path
that is seen in smartphone and slate devices, with apps providing the majority of end user applications.
Note: For a list of available SharePoint Apps, see the Apps for Office and SharePoint page
of the Office Store at http://go.microsoft.com/fwlink/?Linkid=302038
Microsoft is encouraging developers to develop SharePoint Apps, which they can then submit to
Microsoft for validation and then distribute through the app store, Apps for SharePoint. Apps are not
allowed to execute server-side code, which ensures that a new app cannot damage your SharePoint
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
environment; all code executes in the client browser or in a separate remote environment, such as
Windows Azure.
For an enterprise environment, the App Management service application controls access and licensing of
apps by users. The SharePoint farm provides an internal app store, called the App Catalog. You can deploy
internally-developed apps and approved apps bought or licensed through the Microsoft App Store to
your organization's internal App Catalog. This is hosted on SharePoint 2013 or SharePoint Online and
controls the visibility of apps to users in your organization.
When you start planning to deploy apps on your SharePoint farm, it is important that you review your
governance and compliance policies to include app access and usage. You also need to manage the
deployment environment. You need to set up a Domain Name Services (DNS) domain name to provide a
host name for the installed apps. This means that apps for SharePoint are separated from SharePoint sites
and enhances security by ensuring that there is no unauthorized access to user data and reducing the
surface for cross-site scripted attacks. This provides discrete URLs for SharePoint apps and sites, which is
called app isolation. Remember that you will need a DNS record to ensure domain name resolution.
Deprecated Features in SharePoint 2013
As is always the case with version upgrades, there
are some features and functions that are
deprecated in SharePoint Server 2013. Some of
these are concerned with changes to the Search
service, which has already been reviewed. Other
key deprecations include:
Visual upgrade. This has been replaced with
the deferred site collection upgrade, which
offers extended usability, such as the
preservation of SPFeature functionality.
Document Workspace site template. This
functionality is now delivered in the Team Site
template.
Meeting Workspace site templates. This functionality is broadly delivered by other SharePoint Server
2013 and Office 2013 features.
Unghosting and customizing CSS files. This is old technology and no longer widely used.
Web Analytics service application. This functionality is now delivered by the Search service.
Office Web Apps service application. This is now a separate server product.
Additional Reading: For a full list of features that have been deprecated in SharePoint
2013, see Changes from SharePoint 2010 to SharePoint 2013 at

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
SharePoint Server 2013 and SharePoint Online Editions
There are a number of versions of SharePoint 2013 and SharePoint Online available from Microsoft. It is
important that you and your organization understand the functionality offered by each to ensure that you
select the correct edition to fit your business needs.
In addition to on-premises and online implementations, you can deploy hybrid solutions that integrate
your on-premises and cloud-based business. The decision to stay in-house or go to the cloud is one that
many organizations are already discussing and all will face in the next few years. This lesson examines
these options, along with their benefits and disadvantages.
Lesson Objectives
List the SharePoint 2013 on-premises editions.
List the SharePoint Online editions.
Describe some of the options for hybrid deployment integration.
SharePoint On-Premises Editions
For on-premises deployments there are several
different editions of SharePoint 2013 that
organizations can choose from.
SharePoint Foundation 2013. This offers an
entry-level or small office SharePoint solution
with minimal costs. SharePoint Foundation
includes document management and
collaboration features, search capabilities, and
a scalable architecture. SharePoint Foundation
licensing is included with Windows Server
licensing and Windows Client Access Licenses
(CALs) allowing many organizations to
leverage the benefits of SharePoint collaboration.
SharePoint Server 2013 Standard edition. Standard edition offers Enterprise Content Management
(ECM), Web Content Management (WCM), Managed Metadata, user profile synchronization, My Sites,
audience targeting, Secure Store Service, and social networking.
SharePoint Server 2013 Enterprise edition. Enterprise edition offers PerformancePoint, Visio Services,
Access Services, Excel Services, and InfoPath Forms Services.
Additional Reading: For a comparison list of the features of SharePoint 2013 on-premises
solutions, see the section SharePoint feature availability across on-premises solutions of the
SharePoint Online Service Description page at http://go.microsoft.com/fwlink/?Linkid=302040
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
SharePoint Online
SharePoint Online provides organizations an
additional option for how they choose to deploy
SharePoint. SharePoint Online is part of Microsoft
Office 365, but you can license only the SharePoint
Online component if desired.
The current subscription plans for Office 365
include:
Office 365 Small Business
Office 365 Small Business Premium
Office 365 Midsize Business
Office 365 Enterprise E1, Office 365 Government G1
Office 365 Enterprise E2, Office 365 Education A2, Office 365 Government G2
Office 365 Enterprise K1, Office 365 Government K1, Office 365 Enterprise K2, Office 365 Government
K2
In addition to these Office 365 plans, an organization can purchase SharePoint Online Plan 1 and
SharePoint Online Plan 2 on a standalone basis or as part of an Office 365 subscription. SharePoint Online
Plan 1 offers standard SharePoint capabilities plus the ability to view Office documents in the browser
interface. SharePoint Online Plan 2 adds Enterprise features with full Office Web App capabilities.
Additional Reading: To review a complete list of SharePoint Online features per edition,
see the section SharePoint feature availability across on-premises solutions of the SharePoint
Online Service Description page at http://go.microsoft.com/fwlink/?Linkid=302042
SharePoint Online Benefits
One of the primary advantages of a SharePoint Online deployment is that management of the
infrastructure and a service level agreement (SLA) are provided as part of the subscription, so
administrators can get on with managing other SharePoint elements, such as site structure, permissions,
and managed metadata. SharePoint Online also provides organizations with a rich extranet capability that
is easy to provision and prevents external partners from having access to the internal corporate network.
Site customization is supported in SharePoint Online with SharePoint Designer. It provides the ability to
connect to and edit sites and workflow in the SharePoint Online environment; however, Full Trust Coded
solutions, also known as farm level solutions, are not supported in SharePoint Online, although sandboxed
code solutions are supported, and the new SharePoint App model will soon be supported.
SharePoint Online also offers Active Directory integration through the use of Active Directory Federation
Services (AD FS) so that users can log in to the SharePoint Online environment using the same user name
and password that they use to access their desktop environment.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
SharePoint 2013 Hybrid Deployments
With SharePoint 2013, it is possible to mix an on-
premises and a SharePoint Online Deployment in
such a way that certain features and functionality
can be shared between the two environments. This
approach is called a hybrid deployment.
A hybrid deployment can provide one-way or
two-way integration. This describes the sharing of
content or functionality, with one-way commonly
enabling the on-premises deployment to consume
cloud-based resources, whereas two-way
integration provides pathways in both direction
between SharePoint 2013 and SharePoint Online.
Hybrid deployments may be able to offer some organizations the best of both options, with some content
being made available from an on-premises farm, and some content being held in SharePoint Online.
Hybrid deployments can use single sign-on, so that users only need to authenticate once using an Active
Directory domain user account to gain access to both on-premises SharePoint farms and SharePoint
Online. Hybrid deployments can use federated search to provide search results that encompass both on-
premises and SharePoint Online content for users of both environments, if desired.
You can also use Business Connectivity Service (BCS) functionality to directly publish certain on-premises
data to the SharePoint Online environment. This is called a SharePoint BCS Hybrid solution. SharePoint
BCS Hybrid solutions can only publish line-of-business (LOB) data from on-premises environments to
SharePoint Online; it cannot publish data from SharePoint Online to on-premises. Data is published
securely, by using the on-premises BCS services to handle data connectivity and then using a reverse
proxy to publish the BCS connection to SharePoint Online.
Reader Aid: For more information about SharePoint 2013 hybrid deployments, see Hybrid
for SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=302043
Discussion: What Is the Role of SharePoint Online in Business
Organizations?
What do you think is the role of SharePoint Online
in an organization like yours?
Do you:
Currently use SharePoint Online?
Plan to evaluate SharePoint Online?
Plan to deploy SharePoint Online?
Have no plans to evaluate or use SharePoint
Online?
Does your organization use any cloud-based
solutions?
What do you see as the advantages and disadvantages of cloud-based SharePoint?
What benefits can you see in a hybrid SharePoint deployment?
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab: Reviewing Core SharePoint Concepts
Scenario
The IT team at Contoso has created a server farm for an initial deployment of SharePoint Server 2013. The
server farm consists of three servers: a domain controller, a SQL Server 2012 server, and a SharePoint 2013
server. Your team has installed SQL Server 2012, and SharePoint Server 2013. Your IT team has already
completed the core planning and design tasks for the SharePoint deployment, but you now need to
implement some of the more advanced enterprise functionality.
Rather than work on the production environment, your team would like to set up a lab environment and
have asked you to complete the SharePoint 2013 core configuration tasks. You have been tasked with
configuring the SharePoint farm, and creating and configuring web applications and site collections for
the farm.
Objectives
After completing this lab, you will be able to:
Configure a SharePoint Server 2013 farm.
Create and configure a site collection.
Estimated Time: 40 minutes
Virtual Machine: 20332B-NYC-DC-01, 20332B-NYC-DB-01, 20332B-NYC-SP-01
User Name: administrator@contoso.com
Password: Pa$$w0rd
Exercise 1: Configuring SharePoint server 2013 Farms
Scenario
In this exercise, you will configure a SharePoint server farm. You will run the SharePoint 2013 Products
Configuration Wizard to complete the installation.
In addition to running the wizard, you will also complete supplementary tasks necessary to make the
SharePoint server function correctly. This will include creating necessary service accounts, configuring
DNS.
Finally, you will create new web applications by using a host header, and ensure that SharePoint sites can
be browsed from the SharePoint server by selectively disabling loopback checking.
The main tasks for this exercise are as follows:
1. Create a Server Farm Account in Active Directory
2. Create service accounts for the web applications
3. Configure DNS for the sharepoint.contoso.com and finance.contoso.com domains
4. Enable TCP/IP Connectivity in SQL Server
5. Create a SQL Server Alias on the SharePoint 2013 Server
6. Run the SharePoint Products Configuration Wizard
7. Register the web application service accounts as SharePoint managed accounts
8. Create the sharepoint.contoso.com and finance.contoso.com web applications
9. Disable loopback checking for the sharepoint.contoso.com and finance.contoso.com domains
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 1: Create a Server Farm Account in Active Directory
Start the 20332B-NYC-DC-01 virtual machine. Wait for the virtual machine to display the logon
screen, and then wait a further five minutes before you proceed to the next step.
Start the 20332B-NYC-DB-01 virtual machine. Wait for the virtual machine to display the logon
screen before you continue.
Start the 20332B-NYC-SP-01 virtual machine. Wait for the virtual machine to display the logon screen
before you continue.
Log on to the 20332B-NYC-DC-01 machine as administrator@contoso.com with the password
Pa$$w0rd.
Start Active Directory Administrative Center.
Create a new user with the following details:
Property Setting
Full
name
SharePoint Farm
UPN SPFarm@contoso.com
UPN
logon
SPFarm@contoso.com
SAM Account Name logon Contoso\SPFarm
Password Pa$$w0rd
Password never expires Selected
User cannot change password Selected
Task 2: Create service accounts for the web applications
Property Setting
Full name sharepoint.contoso.com Service Account
UPN logon SPContosoCom@contoso.com
SAM Account Name logon Contoso\SPContosocom
Password Pa$$w0rd
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
Full name finance.contoso.com Service Account
UPN logon SPFinanceWebApp@contoso.com
SAM Account Name logon contoso\SPFinanceWebApp
Password Pa$$w0rd
Property Setting
Full name sales.contoso.com Service Account
UPN logon SPSalesWebApp@contoso.com
SAM Account Name logon contoso\SPSalesWebApp
Password Pa$$w0rd
Task 3: Configure DNS for the sharepoint.contoso.com and finance.contoso.com
domains
Open DNS Manager.
Add a new host record to the contoso.com forward lookup zone with the following properties:
Property Setting
Name sharepoint
IP address 172.16.1.21

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Add a new host record to the contoso.com forward lookup zone with the following properties:
Property Setting
Name Finance
Create a new forward lookup zone named finance.
Add a new host record to the finance forward lookup zone with the following properties:
Property Setting
Name
Task 4: Enable TCP/IP Connectivity in SQL Server
Log on to the 20332B-NYC-DB-01 virtual machine as CONTOSO\Administrator with the password
Pa$$w0rd.
Open SQL Server Configuration Manager.
Enable TCP/IP for the MSSQLSERVER server instance.
Restart the MSSQLSERVER server instance.
Task 5: Create a SQL Server Alias on the SharePoint 2013 Server
Log on to the 20332B-NYC-SP-01 machine as administrator@contoso.com with the password
Pa$$w0rd.
Open the cliconfg.exe application from the C:\Windows\System32 folder.
Add a new server alias named ContosoDB, which uses the TCP/IP network library and connects to
the NYC-DB1 server.
Close SQL Server Client Network Utility.
Open the cliconfg.exe application from the C:\Windows\SysWOW64 folder.
Add a new server alias named ContosoDB, which uses the TCP/IP network library and connects to
the NYC-DB1 server.
Close SQL Server Client Network Utility.
Task 6: Run the SharePoint Products Configuration Wizard
On the 20332B-NYC-SP-01 server, run the SharePoint Products Configuration Wizard and specify the
following configuration settings:
Property Setting
Server farm New server farm
Database server ContosoDB
Database Name SharePoint_Config
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
Database access account user name CONTOSO\SPFarm
Database access account password Pa$$w0rd
Farm passphrase Pa$$w0rd
Central Administration web application port
number
50000
Central Administration web application
authentication provider
NTLM
Verify that you can access the Central Administration website, but do not complete the Farm
Configuration Wizard.
Task 7: Register the web application service accounts as SharePoint managed
accounts
Use the Central Administration website to register the contoso\SPSalesWebApp account you
created in the previous tasks as a managed account.
Register the contoso\SPFinanceWebApp account you created in the previous tasks as a managed
account.
Task 8: Create the sharepoint.contoso.com and finance.contoso.com web
applications
Use the Central Administration website to create a new web application with the following properties:
Property Setting
Port 80
Port header sharepoint.contoso.com
Application pool name SharePoint - 80
Application pool security account CONTOSO\SPContosoCom
Use the Central Administration website to create a new web application with the following properties:
Property Setting
Port 80
Port header finance.contoso.com
Application pool name SharePointFinance - 80
Application pool security account CONTOSO\SPFinanceWebAPP
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In IIS add a binding to the SharePoint - finance.contoso.com website that binds it to the
172.16.1.21 IP address on port 80 with the host name finance.
Task 9: Disable loopback checking for the sharepoint.contoso.com and
finance.contoso.com domains
In the registry, disable loopback checking for the sharepoint.contoso.com domain to enable you to
visit the site on the SharePoint server.
Disable loopback checking for the finance.contoso.com domain.
Disable loopback checking for the finance domain.
Restart Internet Information Services (IIS).

Results: After completing this exercise, you should have completed initial SharePoint configuration,
including provisioning the SharePoint Central Administration website, and created a new web application
for the sharepoint.contoso.com domain
Exercise 2: Creating and Configuring Site Collections and Sites
Scenario
In this exercise, you will create top-level site collections in the sharepoint.contoso.com and
finance.contoso.com web applications. You will create two top-level site collections by using the Central
Administration website, and you will create a host named site collection by using PowerShell.
You will also create a subsite for the IT department in the sharepoint.contoso.com site collection.
1. Create a top-level site collection for the sharepoint.contoso.com web application
2. Create a site in the sharepoint.contoso.com site collection
3. Create a top-level site for the finance.contoso.com web application
4. Use PowerShell to create a host named site collection in the finance.contoso.com web application
Task 1: Create a top-level site collection for the sharepoint.contoso.com web
application
Use the Central Administration website to create a new top-level site collection in the
sharepoint.contoso.com web application with the following properties:
Property Setting
Title SharePoint
URL http://sharepoint.contoso.com
Template Team Site
Primary site collection administrator CONTOSO\Administrator
Navigate to the sharepoint.contoso.com site collection to verify it is configured correctly.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 2: Create a site in the sharepoint.contoso.com site collection
Add a new site named IT with the URL http://sharepoint.contoso.com/IT.
Verify that the IT site displays correctly.
Close Internet Explorer.
Task 3: Create a top-level site for the finance.contoso.com web application
finance.contoso.com web application with the following properties:
Property Setting
Title Finance Extranet
URL http://finance.contoso.com
Template Team site
Navigate to the finance.contoso.com site collection to verify it is configured correctly.
Task 4: Use PowerShell to create a host named site collection in the
finance.contoso.com web application
Use the New-SPSite cmdlets in PowerShell to create a new host named site collection in the
finance.contoso.com web application with the following properties:
Property Setting
Title Finance Intranet
URL http://finance
Template Team Site (STS#0)
Navigate to the finance site collection to verify it is configured correctly.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Module Review and Takeaways
In this module, you reviewed the architectural changes in SharePoint 2013, new and enhanced features,
and the editions that are available for on-premises and online deployments.
Review Question(s)
Test Your Knowledge
Question
Which of the following Service Applications is no longer available with SharePoint
Server 2013Enterprise Edition?

Select the correct answer.
Search
Office Web Apps
Translation Service
Work Management Service
App Management Service
Verify the correctness of the statement by placing a mark in the column to the right.
Statement Answer
Solutions have been superseded by SharePoint Apps.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
2-1
Module 2
Designing Business Continuity Management Strategies
Contents:
Module Overview 2-1
Lesson 1: Designing Database Topologies for High Availability and Disaster
Recovery 2-2
Lesson 2: Designing SharePoint Infrastructure for High Availability 2-12
Lesson 3: Planning for Disaster Recovery 2-17
Lab: Planning and Performing Backups and Restores 2-28

Module Overview
High availability describes the steps you take to make your server farm resilient to hardware failures. In
other words, high availability means that users can continue to access SharePoint if a single component in
the farm fails. By contrast, disaster recovery refers to the processes you put in place to avoid loss of data
when a hardware or software failure occurs.
When designing high availability and disaster recovery strategies for a SharePoint farm, it is important to
understand the different approaches required by each logical tier in the farm. High availability for the
database tier requires understanding how SQL Server provides high availability and the associated
requirements.
High availability for the application tier can be straightforward for some service applications, whereas
other applications, such as Search, require additional planning and configuration for high availability. The
Web Front End (WFE) tier will also require additional planning and configuration for high availability, and
architects should consider the new SharePoint 2013 request management feature.
SharePoint farm disaster recovery has always required considerable planning and understanding of the
necessary components and backup tools available. In this regard, SharePoint 2013 is no different, and
farm administrators should create a disaster recovery plan that states how content and configurations are
backed up, how data can be restored, and what backup schedules are required.
Objectives
Select an appropriate database server configuration to meet availability requirements.
Design a physical architecture and infrastructure to meet availability requirements.
Develop and implement a backup and restore strategy.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
2-2 Designing Business Continuity Management Strategies
Lesson 1
Designing Database Topologies for High Availability and
Disaster Recovery
When designing high availability for databases in a SharePoint farm, you should be familiar with the
different high availability options present in SQL Server 2008 R2 and SQL Server 2012. Understanding
these options will give you the ability to choose the appropriate option for your farm deployment, based
on factors such as user requirements, cost, and available resources.
Lesson Objectives
Determine the components affecting high availability.
Describe how SQL mirroring provides database high availability.
Describe how SQL failover clustering provides SQL instance high availability.
Describe how AlwaysOn Availability Groups provide database high availability.
Describe how SQL log shipping provides database high availability.
Identify which SharePoint databases support which SQL high availability approaches.
Identify storage options for SQL high availability.
Designing for High Availability
Typically, high availability involves using
additional, redundant components to avoid
outages and ensure continuation of operations
when primary components fail. Outages occur
under normal circumstances when failures occur
or when planned maintenance is required. By
implementing an appropriate high availability
strategy, you can ensure that there is a
significantly greater degree of service uptime.
Uptime is typically measured as a percentage; for
example, 99.99% uptime, sometimes referred to as
four nines uptime, represents only 0.01%
downtime, which is equivalent to 52 minutes downtime per year.
When designing a solution to meet high availability requirements, it is important to include
considerations for supporting the entire solution. There is no point in making the database servers highly
available if there is only one Web Front End (WFE) server, because the WFE server becomes a single point
of failure for the farm. Additionally, supporting components, such as the network infrastructure, must be
considered and planned for as part of a highly available solution to avoid other single points of failure,
including cables, switches, and power supplies.
When designing a highly available SharePoint solution, you should consider the following components:
Hardware. Protecting servers against hardware failure involves duplicating components, such as
power supplies, network cards, and implementing RAID storage for the operating system volume and
any other critical data storage, such as databases. You can go further to protect against the loss of
entire servers in the farm by duplicating server workloads or creating server clusters.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
WFE servers. You can protect against the loss of a WFE server by creating and joining additional WFE
servers to the farm. In order to allow for seamless failover between multiple WFE servers, you can
configure Network Load Balancing (NLB).
Application servers. You can protect against the loss of application servers by creating and joining
additional application servers to the farm. Some service applications may require additional
configuration to support the use of additional servers.
Database servers. You can protect against the loss of database servers by adding more servers
running SQL server. You can configure multiple SQL servers to provide high availability for databases
by using SQL mirroring, SQL server failover clustering, or AlwaysOn Availability Groups.
Server virtualization. You may consider using your virtualization platform to provide a small or large
part of your high availability strategy for SharePoint 2013. When planning to utilize high availability
within your virtualization platform, it is important to understand how the virtualization platform
assists availability, and to plan your virtualization deployment accordingly.
Additional Reading: For more information about high availability and downtime, see High
availability and disaster recovery concepts in SharePoint 2013 at
Using SQL Mirroring for High Availability
SQL database mirroring is an option for making
databases highly available in SQL Server 2008 R2
(in SQL Server 2012, high availability is handled
through AlwaysOn Availability Groups, which are
discussed later in this lesson). Database mirroring
provides a redundant copy of a database, called a
mirror, on an alternate SQL server; this mirrored
database is automatically kept up to date with
changes occurring in the principal copy of the
database. The mirrored database server is also
known as the failover database server. Mirroring
sends transaction log information from the server
holding the principal copy of the database to the server holding the mirror, where the logs are
continuously replayed, so that the mirror copy reflects the latest changes.
With SQL mirroring, only the principal SQL server can write changes to the database at any given time.
SQL mirroring supports only one mirror to provide two copies of the database in total.
SQL Mirroring supports three availability modes:
High availability mode. This mode uses synchronous mirroring so that transactions on the principal
database are only committed after the same transactions have been successfully copied to the mirror.
This mode requires the use of an additional SQL server as a witness server, which monitors both the
principal server and the mirror server, if you want to provide optional automatic failover capabilities.
High safety mode. This mode also uses synchronous mirroring, but it does not require the use of a
witness server. This mode guarantees the data on the mirror, but cannot provide automatic failover
and should be considered a warm standby option. This means that the solution cannot automatically
take over in the event of a failure at the primary server, and some reconfiguration work is required to
bring the solution online.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
High performance mode. This mode uses asynchronous mirroring, which allows the principal to
commit transactions as soon as possible, without waiting to confirm that the mirror has received
copies of the transactions. This means that the mirror may not be fully up to date with the principal,
so some data may be lost at failover. However, this mode allows for a higher throughput of
transactions on the principal. This mode does not require a witness server because failover is a
manual process.
Note: SQL mirroring is only supported when the database recovery model is set to full
recovery mode, which saves all transaction logs as part of the backup process.
Failover database server
SharePoint supports automatic failover with SQL Server mirroring by using the failover database server
option provided when you create new web applications, new content databases, or new service
applications. If you specify a failover database server and SharePoint is unable to contact the principal SQL
Server after a number of retry operations, SharePoint will automatically attempt to connect to the same
database on the failover database server, which would be the mirror.
SQL synchronous mirroring can be configured on SQL Server Standard edition and has no special
requirements for Windows Server. You can only configure SQL asynchronous mirroring by using SQL
Server Enterprise or Datacenter editions.
Note: Database mirroring is available in SQL Server 2012, but the feature has been
deprecated, and the use of database mirroring in SQL 2012 is not recommended for new
deployments. In SQL Server 2012, you should consider AlwaysOn Availability Groups as a
replacement for SQL mirroring.
Using Failover Clustering for SQL High Availability
SQL Server failover clustering is based on Windows
Server Failover Clustering (WSFC). Clustering
protects against the failure of the actual database
server hardware, whereas mirroring protects
against the failure of the data itself. Using WSFC
and a shared storage platform, such as iSCSI or
fiber channel-based storage, enables you to create
a high availability instance of SQL Server. A high
availability instance of SQL Server includes
elements such as the instance network name and
IP addresses, in addition to the databases running
on that instance. This means that applications,
such as SharePoint, that are running on the databases do not need configuration of a failover server
setting. If a server in the cluster fails, the entire SQL instance, including storage access, network name, IP
address, and supporting Windows services, fail over to another node in the cluster, and the application is
able to access the databases without reconfiguration.
Note: In SQL Server 2012, SQL failover clusters are called AlwaysOn Failover Clusters.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Because of the requirement for the WSFC feature, SQL failover clustering requires that SQL Server be
installed on Windows Server Enterprise or Datacenter editions. You can use SQL Server Standard edition to
create a two-node failover cluster. You can use SQL Server Enterprise edition to create a failover cluster
using the maximum number of nodes supported by the operating system. Windows Server 2008 R2
supports clusters up to 16 nodes; Windows Server 2012 supports clusters up to 64 nodes.
Using AlwaysOn Availability Groups for High Availability
SQL Server 2012 offers a new high availability
mechanism called AlwaysOn Availability Groups.
AlwaysOn Availability Groups provide high
availability protection for databases by managing
multiple copies of a database in a manner similar
to database mirroring, but significantly enhanced.
When you create an AlwaysOn Availability Group,
you configure an instance of SQL Server 2012 as
the primary replica for that group. The primary
replica hosts the read/write copies of the
databases that you want to keep highly available.
You can then configure between one and four SQL
Server 2012 instances as secondary replicas. Each secondary replica hosts a copy of each of the databases
from the primary replica that are included in the availability group. If the primary replica becomes
unavailable, you can manually or automatically pass the role of primary replica to one of the secondary
replicas in a process called failover.
The databases that you want to make highly available in the availability group must use the full recovery
model. The primary replica keeps secondary replicas up-to-date by copying transactions across to
secondary copies.
AlwaysOn Availability Groups support two availability modes:
Synchronous-commit mode. In synchronous-commit mode, when a client updates a database, the
primary replica writes the change to its local log and copies the change to its secondary replicas. The
primary replica then waits for the secondary replicas to confirm that they have written the transaction
to their logs before committing the transaction and sending an acknowledgement to the client.
Synchronous-commit mode ensures that the databases that are part of the availability group on the
primary and secondary replicas are synchronized at all times to ensure no data loss in the event of a
failover. However, this process results in reduced performance while the primary replica waits for
confirmation.
Asynchronous-commit mode. In asynchronous-commit mode, when a database receives an update,
the primary replica writes the change to its log and sends the updates to its secondary replicas. This
mode does not wait for confirmation from the secondary replicas, which results in improved
performance. However, if a failover occurs, the secondary replicas may not have all the transactions
from the primary and some data may be lost.
Clients connect to the databases in an availability group by using an availability group listener, which
consists of a DNS name, a TCP port number, and one or more IP addresses. Using a listener removes the
need to reconfigure clients to connect to a new primary replica in the event of a failover.
AlwaysOn Availability Groups support different types of failover, which can be automatic or planned, and
may or may not guarantee zero data loss depending on whether the availability databases are running in
synchronous-commit mode or asynchronous-commit mode. Automatic failover is only available in
synchronous-commit mode.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
SQL Server 2012 AlwaysOn Availability Groups require SQL Server 2012 Enterprise edition running on
Windows Server 2008 R2 Enterprise or Datacenter editions or Windows Server 2012 Datacenter edition.
Additional Reading: For more information, see Overview of AlwaysOn Availability Groups
(SQL Server) at http://go.microsoft.com/fwlink/?Linkid=302045
Discussion: Mirroring versus Clustering
In this discussion you will consider the relative
advantages or disadvantages of database
mirroring and failover clustering.

Using Log Shipping for High
Availability
In SQL Server, log shipping provides a simple way
to implement a warm standby solution to aid high
availability and disaster recovery scenarios. Warm
standby means that the solution cannot
automatically take over in the event of a failure at
the primary server, and some reconfiguration work
is required to bring the solution online. However, a
warm standby solution is much quicker to
implement than restoring databases from backup,
and it is typically cheaper to implement than a hot
standby solution, such as mirroring, which can
automatically fail over.
Log shipping consists of periodically backing up the transaction log and copying the backup to a
secondary server, which also holds a copy of the database. The secondary server restores the log backup
so that the logs are ready to process when you want to start the secondary copy. This backup, copy,
restore, process is automated by a series of SQL Server Agent jobs.
You can specify how frequently log backups are performed and transferred to secondary servers to
determine how far behind the secondary copy is. However, it is important to note that with log shipping,
there is always a risk of data loss, because there is no way to guarantee transactional consistency between
the primary and secondary copies. Log shipping is useful because there is not the same requirement for
transactional consistency and no clustering requirements, so log shipping can be used across different
subnets and often between SQL servers in different physical locations, such as a disaster recovery site.
You can also configure secondary copies to have a load delay, which prevents the secondary database
from including changes within a recent time window, such as eight hours. This means that the secondary
copy will always be eight hours behind the primary copy. This configuration can be useful where you want
to protect the database against user error or logical corruption. In such a case, the administrator can
choose to switch to the secondary copy, which has not yet processed the action you want to avoid.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Log shipping requires that you use the full or bulk-logged recovery models on the database. You can use
log shipping with SQL Server Standard and Enterprise editions running on Windows Server Standard
edition. There is no specific requirement for Windows Server Enterprise edition to configure log shipping.
Additional Reading: For more information about log shipping, see Log Shipping Overview,
at http://go.microsoft.com/fwlink/?Linkid=302046
High Availability Support for SharePoint Databases
Although SQL Server supports several different
high availability technologies, not all of these
technologies are suitable for SharePoint databases.
Before planning your high availability and disaster
recovery strategy for SharePoint, it is important to
understand which high availability technologies
are suitable for use with your farm.

The following table shows which types of SharePoint database support which SQL Server high availability
technologies:
Database (DB) Type
SQL
Synchronous
Mirroring
Supported
SQL 2012
AlwaysOn
Availability
Groups with
Synchronous
Commit
Supported
SQL 2008 R2
Asynchronous
Mirroring or Log
Shipping
Supported
SQL Server 2012
AlwaysOn
Availability
Groups with
Asynchronous
Commit
Supported
Farm Configuration
DB
Yes Yes No No
Central Admin DB Yes Yes Yes No
Content DBs Yes Yes Yes Yes
App Management DB Yes Yes Yes To be determined
(TBD). Not
currently
supported
Search Admin DB Yes Yes No TBD. Not currently
supported
Analytics Reporting
(Search)
Yes Yes Yes TBD. Not currently
supported
Search Crawl DB Yes Yes No TBD. Not currently
supported
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Database (DB) Type
SQL
Synchronous
Mirroring
Supported
SQL 2012
AlwaysOn
Availability
Groups with
Synchronous
Commit
Supported
SQL 2008 R2
Asynchronous
Mirroring or Log
Shipping
Supported
SQL Server 2012
AlwaysOn
Availability
Groups with
Asynchronous
Commit
Supported
Search Link DB Yes Yes No TBD. Not currently
supported
Secure Store DB Yes Yes Yes TBD. Not currently
supported
Usage and Health
Data Collection
Yes, not
recommende
d
Yes, not
recommended
Yes, not
recommended
TBD. Not currently
supported
Word Conversion DB Yes Yes No No
Subscription Settings
DB
supported
UPS Profile DB Yes Yes Yes TBD. Not currently
supported
UPS Sync DB Yes Yes No TBD. Not currently
supported
UPS Social Tagging
DB
supported
Word Automation
Services DB
Yes Yes No TBD. Not currently
supported
Managed Metadata
Service DB
supported
Taxonomy DB Yes Yes Yes TBD. Not currently
supported
Translation Services
DB
supported
BDC service DB Yes Yes Yes TBD. Not currently
supported
PerformancePoint Yes Yes Yes TBD. Not currently
supported
State Service DB Yes Yes No No
All SharePoint databases support failover clustering of SQL Server instances.
Note: With any high availability implementation that only protects the database content,
such as mirroring, AlwaysOn Availability Groups, and log shipping, SQL Server settings from the
primary server will not be copied automatically to secondary servers. Any settings you require to
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
be duplicated at secondary servers, such as SQL login and role configuration, will need to be
configured manually or scripted.
Additional Reading: For more information about database high availability support, see
Supported high availability and disaster recovery options for SharePoint databases (SharePoint
2013) at http://go.microsoft.com/fwlink/linked=302047
Designing Storage for High Availability Requirements
When you plan for content storage on SharePoint
2013, you must choose a suitable storage
architecture. SharePoint content storage has a
significant dependency on the underlying
database; therefore, database and SQL Server
requirements will drive your storage choices.
Storage Architecture
The following storage architectures are suitable for
SharePoint 2013:
Direct attached storage (DAS), where hard
disks are attached directly to the computer
running SQL Server.
Storage area network (SAN), which uses a network infrastructure to connect the computer running
SQL Server to the separate disk storage volumes.
Network attached storage (NAS) devices may be suitable, under certain circumstances, such as for
remote binary large object (BLOB) storage. However, this support is subject to precise NAS
specifications.
Note: Content databases with remote BLOB storage are the only configuration in which
SharePoint 2013 supports NAS storage. Any network storage architecture must respond to a ping
within one millisecond and must return the first byte of data within 20 milliseconds.
DAS is typically a significantly cheaper option than SAN storage. However, DAS usually offers fewer
management capabilities and fewer options for high-availability configurations. SAN storage can support
failover clustering in SQL Server and may provide additional disaster recovery options, such as SAN
mirroring.
Note: In general, you should choose a DAS architecture if a shared storage platform cannot
guarantee a response time of 20 milliseconds or less and sufficient capacity for average and peak
I/O operations per second (IOps).

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
RAID
SharePoint 2013 works well with redundant array of independent disk (RAID)-based storage, which offers
improved performance, additional fault tolerance, or both, depending on the RAID option that you
choose. The following table describes the most common RAID types.
RAID configuration Description
RAID 0 Offers improved performance by striping data across disks in
the array. Not fault tolerant.
RAID 1 Duplicates (mirrors) data onto a second disk in the array.
Fault tolerant, but no significant performance improvement.
RAID 5 Uses three or more disks to provide fault-tolerant storage
with less wasted space than RAID 1. RAID 5 typically offers
good read I/O characteristics; however, disk write
performance is typically slower than normal, due to the fault-
tolerance requirement.
RAID 10 Uses a combination of RAID 1 to provide fault tolerance and
RAID 0 to provide a performance improvement. More
expensive than RAID 1 or RAID 5, but ensures optimum write
performance.
Disk Types
Different storage architectures use a range of disk types, including:
Serial Advanced Technology Attachment (SATA).
Small Computer System Interface (SCSI).
Serial Attached SCSI (SAS).
Solid State Drive (SSD) or Flash Disk.
These disk types have varying performance, capacity, and cost characteristics that you must take into
consideration when you design your SQL Server storage architecture.
Storage planning for high availability
In addition to considering the disk type and RAID profile, you should also plan for the impact high
availability technologies may have on your storage platform, as follows:
Choosing failover clustering for SQL Server requires a shared storage platform, such as a SAN, which
may incur additional cost. However, only one copy of the data exists on the SAN.
Choosing mirroring, AlwaysOn Availability Groups, or log shipping results in duplicating databases,
which creates a greater overhead on storage requirements. In particular, duplicating databases on
SAN storage can significantly increase the storage cost.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Discussion: High Availability Planning
In this discussion, you will review the role of the
SharePoint 2013 administrator in overall high
availability planning.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Designing SharePoint Infrastructure for High Availability
After ensuring that the database tier is highly available, it is important to consider how you can help
ensure that both Web Front End (WFE) services and service applications within a SharePoint farm can be
made highly available. In SharePoint 2013, there is a new Request Management feature that can help to
direct certain types of request to specific sets of servers. The choice of server is made in part by
determining server health scores to determine which server can best service the request. You should also
consider components such as Central Administration, SQL Server access, and server placement for impact
on farm availability.
Lesson Objectives
Determine a requirement for network load balancing.
Describe Request Management.
Describe how to implement high availability for SharePoint service applications.
Describe how to implement high availability for Central Administration.
Describe best practices for highly available farm deployments.
Implementing Network Load Balancing
Network Load Balancing (NLB) provides high
availability and scalability for TCP/IP-based
services, including web servers, File Transfer
Protocol (FTP) servers, as well as other mission-
critical servers and services. In an NLB
configuration, multiple servers run independently,
and do not share any resources. This group of
servers is referred to as an NLB cluster. Client
requests are serviced by one of the servers in the
cluster, depending on the cluster configuration. In
the event of a server failure, client requests are
handled by another server in the cluster. In this
way, NLB allows you to increase network service performance and availability.
In terms of a SharePoint implementation, NLB is effective for client requests to Web Front End (WFE)
servers. By using multiple WFE servers in the farm and configuring NLB, you can increase the availability of
the WFE tier.
You can implement NLB in two ways:
Configuring Windows Network Load Balancing on each WFE server.
Using a third-party load balancing solution, such as a dedicated hardware load balancer.
Conceptually, both approaches share some common configuration requirements. Consider a SharePoint
farm with three WFE servers. Each WFE server has a single network adapter with a unique IP address. You
create a web application called intranet.contoso.com in Central Administration and use a host header. This
automatically creates the IIS website and virtual directories on all three WFE servers. You configure NLB
with an additional unique IP address and create a DNS A record, or host record, for intranet.contoso.com
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
to point to the NLB address. When a client navigates to intranet.contoso.com in a web browser, the
TCP/IP packets first reach the NLB component before NLB decides which server should handle the
request. If a WFE server fails, NLB stops passing requests to that host and all requests are spread between
the two remaining hosts until the failed server is brought online.
Note: NLB is only effective for the WFE role; you should not configure NLB for the
application servers or database servers.
Additional Reading: For more information about Windows Network Load Balancing, see
Network Load Balancing Overview at http://go.microsoft.com/fwlink/?Linkid=302049
What Is Request Management?
In a SharePoint farm with multiple WFE servers,
you may want to perform more tasks than simple
load balancing. In particular, Windows NLB does
not provide any smart traffic management, so
that request routing is always evenly divided
across the farm. You can implement host
weighting to adjust the way requests are split, but
this is a fairly static mechanism. Many
organizations may want to prioritize certain types
of request, or to reroute web requests when
individual servers become overloaded.
In SharePoint 2013, you can use Request
Management to perform dynamic, rule-based request routing to different WFE servers in your farm. The
following behavior can be configured with Request Management:
Route requests to web servers with a better health score, thus avoiding overloading servers.
Prioritize important requests, such as end user requests over low priority requests, such as crawl
requests.
Route requests to specific servers based on host name, client IP address, or browser type. This could
be a permanent configuration or to assist troubleshooting.
Route traffic to servers based on request type, such as search or client applications.
Identify and block harmful requests.
Note: Request Management is typically configured in addition to NLB, because Request
Management cannot provide failover capabilities in the event of a server failure.
Request Management can operate in two modes:
Integrated mode. This mode runs the Request Management service on every server configured with
the WFE server role, which is every server running the Microsoft SharePoint Foundation Web
Application service. In integrated mode, requests arrive at a WFE server in the farm, but they may be
redirected to another WFE server according to rule configuration.
Dedicated mode. This mode runs the Request Management service on a set of dedicated servers,
separate from the WFE servers in the farm. Requests arrive at the Request Management servers before
being directed to a WFE server. Dedicated mode is typically used only for very large server farms.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Request Management has the following components:
Routing rules. Routing rules route requests to an associated machine pool based on matching criteria.
Machine pools. Machine pools are collections of one or more servers, typically dedicated to handling
certain types of requests, such as end user requests, crawler requests, and mobile device requests.
Server weights. Server weights are used by routing rules to determine which servers will provide the
best response for a request. Weights can be static or health based. Static weights can be assigned by
an administrator by using Windows PowerShell, whereas health weights are controlled by the system,
based on information such as current load.
Execution group. An Execution group holds one or more routing rules. There are three possible
execution groups, numbered 0, 1, and 2, which are processed in sequence. Once a rule is matched in
an execution group, no other execution groups are processed for that request. For example, if a
request matches a rule in execution group 0, no rules in execution groups 1 or 2 are processed for
that request.
Throttling rules. Throttling rules are used to refuse requests based on matching criteria. Throttling
rules are not associated with a machine pool or execution group, they can have an expiry time, and
they are always evaluated first.
Request Management is configured on a per-web application basis by using PowerShell. There is no GUI
for managing Request Management components or settings. You must also start the Request
Management service instance on each WFE server in the farm.
High Availability for SharePoint Service Applications and Services
The approach to making service applications and
services highly available in a SharePoint farm is
typically simpler than ensuring the Web Front End
or database tiers are highly available.
In most cases, for a service application or service
to be highly available, you must start the service
instance on more than one server. SharePoint will
then utilize multiple servers running the service
automatically. You can start service instances by
using the Service on Server page in Central
Administration or by using the Start-
SPServiceInstance PowerShell cmdlet.
There are some service applications or services that cannot run multiple instances or require more
advanced configuration to achieve high availability. These service include:
Search service. In order to make the search service application highly available, you must configure
the service application topology using PowerShell. Search is comprised of crawl and query functions
and you must determine whether you require high availability for both functions.
User Profile Synchronization service. You cannot run multiple instances of the User Profile
Synchronization service in one farm concurrently. If you require the User Profile Synchronization
service in your farm, you should consider a warm standby approach as best availability for this service.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
High Availability for Central Administration
An important consideration for making a
SharePoint farm highly available is what to do with
Central Administration. By default, Central
Administration runs on the first server in the farm.
Although you can move Central Administration to
a new server, even if the previous server running
Central Administration is unavailable, some
additional, manual intervention will be required.
During this time, no other administration tasks can
be performed with Central Administration if it is
unavailable.
You can install Central Administration on more
than one server in the farm in order to alleviate this issue. The easiest way to achieve this is to run the
SharePoint Products and Technologies Wizard and in the advanced options for Host Central
Administration Web Application, select the option to Use this machine to host the web site.
Optionally, you can also implement NLB for the Central Administration web application, if you require
load balancing or automatic failover for Central Administration.
Best Practices to Support High Availability and Disaster Recovery
In addition to the service specific configurations
required to ensure your SharePoint farm is highly
available, the following best practices can assist
your farm deployments.
Server placement
For best availability, place all servers in the farm on
the same LAN. It is not recommended to create a
stretch farm where servers in the same farm are
located in different data centers. If you have
multiple data centers, it is recommended to
configure multiple farms, such as a production
farm and a warm standby farm, and use
technologies such as backup and restore, SQL log shipping, or SAN replication.
SQL aliases
When initially configuring a farm deployment with the Products and Technologies Wizard and when
creating new web applications and new service applications, you will be asked for the name of the SQL
Server that will store the SharePoint databases. The name of the SQL Server is then written to the farm
configuration database. In the event of a SQL server failure, you can:
Use an alternate server to restore the SharePoint databases to.
Use SQL log shipping.
Move the databases to a faster server.
In these cases, it can be difficult to update all the entries of the SQL Server name that are held in the farm
configuration database, particularly because these changes must be performed through SharePoint. It is
not supported to update the database tables directly.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To ease updating the SQL Server references held in SharePoint, you can use SQL Server aliases when
configuring your SharePoint servers. For example, use the SQL Configuration Manager utility on each
SharePoint server to add a SQL alias of SPSQL pointing to SQL1. When creating the farm, use SPSQL as the
SQL Server name to hold the farm configuration database. If you need to replace server SQL1 with server
SQL2, you can simply update the SQL alias on each server and point SPSQL to SQL2.
Network redundancy
In addition to considering technologies such as Network Load Balancing, you should also consider the
availability of the network infrastructure itself as part of your solution. If users cannot access SharePoint
content due to the failure of a network switch, the goal of avoiding a single point of failure has not been
met. As part of a highly available solution, you should consider redundant switching, routing, and cabling
in order to prevent the network becoming a single point of failure. In addition, you should consider
whether backup Internet connectivity or WAN routing is required for your solution.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Planning for Disaster Recovery
In addition to considering high availability, it is essential that every production farm environment is
correctly backed up in line with clearly established recovery objectives and any agreed service level
agreements. A SharePoint farm represents a complex distributed application with many services and user-
edited content stores, so it is important to understand what built-in backup tools are available and how
the tools can be used in order to protect the farm against data loss of any kind. After the options are
understood and a disaster recovery plan created, it is important to periodically test the plan by
performing test restores of content, service applications, and the farm, and using each test to refine the
disaster recovery plan itself and the procedural documentation that should accompany the plan.
Lesson Objectives
Identify the components of a backup plan.
Plan farm backups.
Plan farm component backups.
Describe required permissions for backup and restore.
Plan content restore procedures.
Plan component restore procedures.
Plan farm restore procedures.
Planning SharePoint Backups
SharePoint includes built-in tools for backing up
the entire farm, service applications, or content.
When planning backups of your SharePoint
environment, it is important to ensure that all
necessary configuration settings and content are
protected in case of a disaster and that you are
able to restore items at the necessary level.
When protecting against disaster in your
SharePoint farm, you should consider the
following types of loss:
Catastrophic loss of farm
Loss of individual server
Loss or error in service application
Loss or error in web application
Loss or error in content database
Loss or error in site collection
Loss or error at or within individual sites (including lists, libraries, and items)
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: SharePoint has additional protection mechanisms available for site collections, sites,
lists, libraries, and items, such as the various levels of recycle bin. However, you must still plan for
how to retrieve content after a longer period of time when the deleted content is no longer
present in the recycle bin.
Backup tools
There are several different ways to back up SharePoint data, including:
Backup options in Central Administration.
Backup using SharePoint PowerShell cmdlets.
Backup using SQL Server backups.
Backup using System Center Data Protection Manager (DPM).
Backup using third-party SharePoint backup tools.
Note: Backup options in Central Administration cannot be scheduled, so to schedule
regular farm or content backups using SharePoint tools, it is recommended that you create a
PowerShell script to perform the necessary backup operations and schedule the script by using
the Windows Task Scheduler.
Virtualization
If you have virtualized some or all of your SharePoint servers, you should consider a virtual machine
backup solution as part of your disaster recovery planning. Being able to restore a farm by restoring the
virtual machines can make farm restoration very simple in the event of a catastrophe. However, do not
assume that virtual machine backups are all you require, even if the entire farm is virtualized. You must
still consider the following issues:
How to retrieve old content that was deleted, but is no longer in the recycle bin.
Restoring service applications or web applications in the event of a misconfiguration.
SQL Server log truncation.
Note: In addition to planning the use of backup tools and the type of backups you will use,
you should fully document you SharePoint farm environment. Good documentation can be
invaluable when attempting to fully or partially restore a farm. For practical information about
documenting your farm environment, see Document farm configuration settings in SharePoint
2013 at http://go.microsoft.com/fwlink/?Linkid=302050
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Protecting a Farm with Backups
It is recommended for your backup plan that you
consider backing up the complete farm by
including both the configuration and content.
Regular backups of the farm will greatly reduce
the possibility of data loss that is possible due to
hardware failures, power outages, or other
elements that may impact your environment.
Performing a backup does not affect the state of
the farm. It does require resources and has the
potential to affect farm performance when the
backup process is taking place.
Considerations
Consider the following:
To avoid performance issues, run backups of the farm during off hours.
Backing up the farm backs up the configuration and Central Administration content databases.
However, these cannot be restored using Microsoft SharePoint Server 2013 tools in anything beyond
a single server deployment.
If you are using Remote Binary Large Object (BLOB) Storage (RBS), consider the following:
o If you are using the SQL FILESTREAM provider for RBS, this RBS provider must be installed on the
database server being backed up and the database server to which the databases will be
restored.
o If you are using a third-party RBS provider, you must manually back up the remote BLOB stores,
or use a third-party backup solution that will include the RBS content.
The farm backup process does not back up any certificates that you used to form trust relationships
for cross-farm service application publishing. Ensure that you have copies of those certificates before
you back up the farm. You must re-establish these trust relationships after restoring the farm.
If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your
environment by using SharePoint tools or SQL Server tools, the TDE encryption key is not
automatically backed up or restored. You must back up the key manually. When restoring, you must
manually restore the key before restoring the data.
If you are using SQL Server Enterprise edition, it is recommended to use backup compression.
When you restore a farm or web application that is configured to use claims-based authentication
(which is the default for new web applications created in SharePoint 2013), duplicate or additional
providers may appear to be enabled. If duplicates appear, you must manually save each web
application zone to remove them.
When restoring a farm or web application that uses forms-based authentication, you must manually
register the membership and role providers again in the Web.config file, and deploy the providers
again.
You should also note the following limitations of farm backups:
Farm backups cannot be restored to other product versions.
Downgrade and upgrade topologies with farm backup and restore are not possible.
The destination farm must have the same topology as the original farm.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
You can perform a full farm backup by using Central Administration or by using the Backup-SPFarm
PowerShell cmdlet.
Note: Performing a farm backup using SharePoint backup tools triggers a backup
operation in SQL Server, which is logged against the SQL Server database. However, any
databases using the FULL recovery model will not truncate the database log files until a LOG
BACKUP operation is run. You must run this operation in SQL Server in order to prevent
transaction log files from filling the associated volume, or consider switching the database
recovery model to SIMPLE.
Some supporting settings for SharePoint are not included in any of the different SharePoint backup
options. You must configure additional backups, such as system state or file system backups, to protect
these items, or consider creating a redeployment script that can reconfigure the necessary settings. These
settings include:
Application pool account passwords.
HTTP compression settings.
Time-out settings.
Changes to the Web.config file that were not performed through Central Administration or the object
model, such as BLOB cache settings or forms-based authentication providers.
Custom Internet Server Application Programming Interface (ISAPI) filters.
Computer domain membership.
Internet Protocol security (IPSec) settings.
Secure Sockets Layer (SSL) certificates.
NLB settings.
Network adapter settings, including IP address configuration.
Additional Reading: For more information, see Overview of backup and recovery in
SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=302053
Backing Up Individual Components of a SharePoint Farm
Performing full farm backups is an important task
that should be performed regularly; however,
some farm data, such as configuration databases,
will not change frequently, so it will not require
frequent backups. Other data, such as content
databases, will change frequently and should be
backed up at a much higher frequency.
You can use the backup options in Central
Administration or PowerShell cmdlets to back up
specific components. You can also use SQL Server
backup to back up specific databases.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Backing up a SharePoint farm configuration
You can perform a configuration-only backup of a farm by using Central Administration or the Backup-
SPConfigurationDatabase cmdlet. A configuration-only backup is useful for development or test
environments, or where you are using a different method, such as SQL Server backup, to back up
SharePoint content. You cannot back up the farm configuration using SQL Server backup tools or System
Center Data Protection Manager.
Backing up service applications
You can use Central Administration or the Backup-SPFarm Item <Service Application Name> cmdlet
to back up specific service applications. Performing a SQL Server backup of the databases associated with
the service application does not back up the entire service application itself; however you can re-provision
the service application using the restored SQL databases.
Note: Using Central Administration or the Backup-SPFarm cmdlet are the only supported
ways to back up the search service application, because these methods keep the search
application databases and the search index files in sync.
Backing up web applications
You can use Central Administration or the Backup-SPFarm Item <Web Application Name> cmdlet to
back up specific web applications and all attached content databases. Performing a SQL Server backup of
the databases associated with the web application does not back up the entire web application itself;
however, you can recreate the web application using the restored SQL databases.
Backing up content databases
You can use Central Administration, the Backup-SPFarm Item <Web Application Name> cmdlet, or
SQL Server backup to back up specific content databases. Backing up a content database backs up all site
collections and contained content in that database, but does not back up the associated web application.
Note: Backing up and restoring content databases can also be used to put useful
information into a test or development environment. This could be automated in SQL Server or
scripted by using PowerShell.
Backing up site collections
You can use the granular backup option in Central Administration or the Backup-SPSite cmdlet to back
up an individual site collection, including all sites and content within that site collection. Site collection
backups can be useful as part of a roll-back plan prior to making significant changes, or where it is
important to be able to restore individual site collections independently, instead of restoring an entire
database.
Note: It is not recommended to back up individual site collections larger than 85 GB in this
way. Site collections larger than 85 GB should be backed up as part of a content database
backup.
Exporting content
You can export a site, list, or library by using the granular backup option in Central Administration or by
using the Export-SPWeb cmdlet. However, unlike backing up, exporting is not considered full-fidelity and
some items will not be included. For example, when exporting a site, workflows will be omitted from the
export.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Additional Reading: For more information about backing up different farm components,
see Plan for backup and recovery in SharePoint 2013 at
For more information about backing up service applications, see Back up service applications in
For more information about configuration-only backups, see Back up farm configurations in
Configure Permissions for Backup and Restore
When planning how you will configure and
schedule backups, it is important to consider the
permissions required for backing up SharePoint
farm components. You must ensure that the
SharePoint timer service account, the SQL Server
service account, and any users who will perform
backup operations have the necessary permissions
and are members of the required Windows
security groups.
Using Central Administration for Backup
When using Central Administration to perform
backup tasks, the Windows SharePoint Services
Timer V4 (SPTimerV4) and the SQL Server service account in SharePoint 2013 run the backup tasks. These
accounts require Full Control permissions on the backup folder locations.
You must ensure that any user account using Central Administration to perform a backup or restore task
is a member of the groups stated in the following table.
Farm component to back up
Must be a member of
local Administrators
group on server
Must be a member of
Farm Administrators
group
Farm Yes No
Service application Yes No
Content database Yes No
Site collection No Yes
Site, list, library, or item No Yes
Using PowerShell for backup
In order to use PowerShell for backing up SharePoint farm components, you must ensure that any user
account running the backup cmdlets in PowerShell, including the account configured to run the script
when scheduling PowerShell based backup operations, are added to the SharePoint_Shell_Access role for
the databases to back up. These accounts must also be members of the required groups that are specified
in the following table.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Farm component
Must be a
member of local
Administrators
group on server
Must be a
member of Farm
Administrators
group
Must have Full
control
permissions on
backup folder
Farm Yes No Yes
Service application Yes No Yes
Content database Yes No Yes
Site collection No Yes Yes
Site, list, library, or item Yes No Yes
You should use the Add-SPShellAdmin cmdlet to add a user account to the SharePoint_Shell_Access role
on the necessary databases.
Note: By default, no user accounts are granted the SharePoint_Shell_Admin role
membership on any content databases. If you are planning to use PowerShell scripts to schedule
SharePoint backups, you must configure at least one user account with this role membership.
Additional Reading: For more information about permissions required for backup or
restore, see Configure backup and restore permissions in SharePoint 2013 at
Restoring Content to SharePoint
Before you restore content in SharePoint 2013,
you must understand the different options for
restoring content databases and site collections.
The type of restore operation that you perform to
recover content will depend of the nature of the
disaster and the type of backup that you have
available.
Scenario 1 Content database is
corrupt, damaged, or lost
In a case where the entire database needs to be
restored from a good backup in order to resume
normal operations, you can choose to restore a database by using one of three methods:
Restore the database by using Central Administration. You can use Central Administration to restore
the database if the database backup was made by using SharePoint tools, such as Central
Administration or PowerShell, and you have the necessary permissions.
Restore the database by using PowerShell. You can use PowerShell to restore the database if the
database backup was made by using SharePoint tools, such as Central Administration or PowerShell,
and you have the necessary permissions.
Restore the database by using SQL Server backup/restore tools. You can restore a content database by
using SQL Server tools if the backup was created by using SQL Server backup. In this case, you should
stop the Windows SharePoint Services Timer Service before restoring the databases in SQL Server, and
then start the timer service after the restore is complete.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Scenario 2 Content has been deleted and is no longer in the recycle bin
In this scenario, you would use the same restore method regardless of the level of object or content you
need to restore; that is, whether you need to restore a site collection, site, list, library, or item.
There are two approaches to restoring content that is no longer in the recycle bin:
Restore content from an unattached database. You can restore the database from backup to an
alternate name or alternate SQL Server to avoid overwriting the current, live version of the
database. After restoring the database, you can use PowerShell to connect the database to
SharePoint, and use PowerShell cmdlets to retrieve content from the restored database. Alternatively,
you can connect to the database by using Central Administration and browse the content, use the
backup site collection option, or use the export option to retrieve the required content.
Restore a read-only copy of the database and attach the database to a web application. You may have
a read-only copy of the database as part of a disaster recovery or maintenance scenario, which may
or may not use log shipping or mirroring from the main production farm. You can use PowerShell to
attach a read-only database to a web application. After attaching, the database will automatically
change to allow read/write access.
Note: SharePoint 2013 restores remote BLOB stores only if you are using the SQL
FILESTREAM provider. If you are using a different RBS provider, you must restore the remote
BLOB stores manually or by using a third-party tool.
Additional Reading: For more information about recovering content databases, see
Restore content databases in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=302060
For more information about recovering content from unattached databases, see Restore content
from unattached content databases in SharePoint 2013 at
http://go.microsoft.com/fwlink/?Linkid=302065 .
For more information about recovering content from a read-only database, see Attach and
restore a read-only content database in SharePoint 2013 at
Restoring Farm Components
Just as you can back up service applications and
web applications, you can also restore these farm
components individually. Restoring components,
such as the Managed Metadata Service or the
Business Data Connectivity (BDC) service, can be
useful if the databases for that service application
become damaged or corrupt, or if a
misconfiguration has been made to the service.
Service applications
You can restore service applications through
Central Administration or by using PowerShell. If
you only have SQL Server based-backups, you will
not be able to restore the entire service application, but you will be able to re-provision the service
application and use the restored databases.
In order to restore a service application with PowerShell, use the Restore-SPFarm Item
<ServiceApplicationName> cmdlet. You should also have the following security roles and
memberships:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
securityadmin role on the SQL Server instance
db_owner role on any database to be updated
Administrators group membership on the server on which you are running PowerShell
You can use the Restore-SPFarm Item Farm\Shared Service Applications cmdlet to restore all
service applications.
Note: If you created a backup of the Search service application by using SQL Server tools,
this will not include the Search index files and you will not be able to restore the index from such
a backup. Instead, you should restore the Search databases, re-provision the Search service
application, and then perform a full crawl of all searchable content. Ensure you plan time for a
full crawl within your recovery objectives.
Web applications
You can restore web applications through Central Administration or by using PowerShell. If you only have
SQL Server based-backups, you will not be able to restore the entire web application, but you will be able
to re-provision the web application and use the restored databases.
In order to restore a web application with PowerShell, use the Restore-SPFarm Item
<WebApplicationName> cmdlet. You should also have the following security roles and memberships:
If the web application you restore uses claims-based authentication (which is the default in SharePoint
2013), you may see duplicate or additional claims providers (this may be visible through a login page). If
duplicates appear, you should manually save each web application zone (you do not need to make
changes) in order to remove the duplicate.
If the web application you restore uses forms-based authentication, you must re-register the membership
and role providers in the Web.config file and redeploy the providers.
Farm configuration
You can also choose to restore only the farm configuration information. This is useful when a disaster has
affected the farm configuration database, but no other farm databases. You can restore the farm
configuration by using Central Administration or PowerShell. In order to use PowerShell to restore the
farm configuration, you must have the following security roles and memberships:
You can use the Restore-SPFarm ConfigurationOnly cmdlet to restore only the farm configuration.
Additional Reading: For more information about restoring service applications, see
Restore service applications in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=302068
For more information about restoring web applications, see Restore web applications in
For more information about restoring only the farm configuration, see Restore farm
configurations in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=302070
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Restoring a SharePoint Farm
Farm-level recovery is typically performed as a last
resort, after a catastrophic failure that includes or
affects the whole farm and where partial recovery
is not possible. You may also use a farm backup
and restore to move a SharePoint deployment
from one farm to another.
You can restore a SharePoint farm by using
Central Administration, PowerShell, or SQL Server
tools. Use the following procedure to restore a
farm:
1. Reinstall SQL Server.
2. Reinstall SharePoint.
3. Run the SharePoint Products Configuration Wizard (PSConfig) to create a new farm.
4. Restore the farm backup over the newly created farm.
5. Start the required SharePoint Services on servers in the farm.
Be aware of the following considerations when restoring a farm in SharePoint 2013:
You cannot restore a multiple-server farm to a stand-alone farm or restore a stand-alone farm to a
multiple-server farm.
You cannot back up from one version of SharePoint 2013 and restore to different version of
SharePoint 2013.
When you restore the farm, the restore process will not automatically start all of the service instances.
Do not use the farm configuration wizard to start the services because this will re-provision the
service applications and the associated proxies.
If you are sharing service applications across farms, be aware that the trust certificates that were
exchanged are not included in farm backups. When you restore a farm that shares a service
application, you must import and redeploy the certificates, and then re-establish any inter-farm trusts.
After a web application using claims-based authentication is restored, there may be duplicate or
additional claims providers (this may be visible through a login page). If duplicates appear, you
should manually save each web application zone (you do not need to make changes) in order to
remove the duplicate.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Discussion: Backup Strategies
In this discussion, you will review experiences of
backing up and restoring SharePoint components.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab: Planning and Performing Backups and Restores
Scenario
Considering the business continuity requirements for Contoso Ltd. and the physical architecture design,
your team must create a business continuity plan for the SharePoint farm.
The information that your team requires is detailed in the supplied documents. Use these documents to
produce your business continuity plan. When the plan is complete, you will need to test key elements,
such as backing up and restoring SharePoint 2013 components and business data.
Objectives
Create backup and restore plan.
Prepare and test backup and restore on a SharePoint server.
Estimated Time: 30 Minutes
Virtual Machine: 20332B-NYC-CL
o User name: admin
o Password: Pa$$w0rd
Virtual Machine: 20332B-NYC-DC-02, 20332B-NYC-DB-02 and 20332-NYC-SP-02
o User name: administrator@contoso.com
Exercise 1: Create a Backup and Restore Plan
Scenario
Business groups have been asked to review their data on SharePoint and to identify the service levels that
they require for backup and restore of information. You will need to interpret their requirements and
develop a backup and recovery plan that will ensure compliance with this request. This will become the
basis for the IT departments service level agreement on SharePoint 2013 availability. You will need to
include the options for backup and restore that you feel will best service the needs.
1. Read the supporting information
2. Complete the Backup and Restore Planning worksheet
Task 1: Read the supporting information
Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen.
Log on to the NYC-CL1 machine as admin with the password Pa$$w0rd.
Read the lab scenario.
In the E:\Mod02\Starter folder, read the information in the Contoso Business Continuity
Requirements.docx file.
Task 2: Complete the Backup and Restore Planning worksheet
In the E:\Mod02\Starter folder, open and complete the worksheet in the SharePoint 2013 Backup
and Restore Planning Worksheet.xlsx file, based on the information you have reviewed in Task 1.
Shut down the 20332B-NYC-CL virtual machine.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

Results: A completed SharePoint Backup Plan
Exercise 2: Test the Backup and Restore Process
Scenario
In this exercise, you will test the backup and restore process.
You will test the process by backing up a service application, and then you will delete the service
application to simulate a failure. After you remove the service application, you will restore it from the
backup and verify that it restores correctly.
In this exercise, you will store the backup on the database server for convenience. In a production
environment, you should store data backups separately from the data protected by the backup.
1. Prepare the backup storage for backing up a SharePoint server
2. Perform a backup of SharePoint components
3. Remove SharePoint components to simulate a failure
4. Restore failed SharePoint components from a backup
Task 1: Prepare the backup storage for backing up a SharePoint server
screen and then wait a further five minutes before you proceed to the next step.
Log on to the 20332B-NYC-DB-02 machine as administrator@contoso.com with the password
Pa$$w0rd.
Create a new folder C:\Backups.
Share the C:\Backups folder. You should grant read/write access to the SQL Server service account
(MSSQLSERVER), and the SharePoint farm service account (CONTOSO\SPFarm).
Task 2: Perform a backup of SharePoint components
Pa$$w0rd.
Open the Central Administration website.
Browse to the Backup and restore page.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Configure the farm default backup settings by specifying the following properties:
Property Setting
Number of backup threads 3
Number of restore threads 3
Backup location \\NYC-DB1\Backups
Perform a backup of all shared services (include shared service applications and shared service
proxies.) Wait for the backup to finish before continuing.
Task 3: Remove SharePoint components to simulate a failure
In the Central Administration website, browse to the Manage Service Applications page.
Delete the Contoso UPSA service application instance.
On the Manage Service Applications page verify that the Contoso UPSA service application
instance and the service application proxy have been removed.
Task 4: Restore failed SharePoint components from a backup
On the Central Administration website, browse to the Backup and Restore page.
Restore the Contoso UPSA service application by using the backup you created in this exercise. Use
the same configuration as the original deployment, with the password Pa$$w0rd. Wait for the
recovery to complete before continuing. You may need to refresh the status page to verify the
progress.
Restore the Contoso UPSA service application proxy by using the backup you created in this exercise.
Wait for the recovery to complete before continuing.
Browse to the Manage Service Applications page and verify that the Contoso UPSA service
application instance and the Contoso UPSA service application proxy have been restored and are
included in the list of service applications.

Results: After completing this exercise, you should have tested the backup and restore process for a
SharePoint 2013 service application.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you learned about high availability and disaster recovery options for SharePoint 2013.
With SharePoint 2013, you plan high availability approaches separately for WFE servers, application
servers, and database servers. Making the database tier highly available relies on SQL Server high
availability technologies, such as mirroring, failover clustering, or AlwaysOn Availability Groups. Making
WFE servers highly available requires Network Load Balancing and may also involve request management
configuration. Making service applications highly available typically involves running more instances of
the associated service, on additional servers.
This module also described the methods available for backing up and restoring SharePoint content, farm
components, and entire farms using built-in tools.
Review Question(s)
Test Your Knowledge
Question
Which database recovery feature is replaced by AlwaysOn availability groups in SQL
Server 2012?

Failover Clustering
Database Mirroring
Log Shipping
Network Load Balancing
Request Management
Test Your Knowledge
Question
Which of the following statements about performing backups from Central
Administration is true?

You cannot schedule backups from Central Administration.
You cannot back up site collections from Central Administration.
You cannot back up individual farm components from Central Administration.
You cannot perform differential backups from Central Administration.
You cannot back up content databases from Central Administration.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Statement Answer
True or false: Request management always
requires additional servers.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
3-1
Module 3
Planning and Implementing a Service Application
Architecture
Contents:
Module Overview 3-1
Lesson 1: Planning Service Applications 3-2
Lesson 2: Designing and Configuring a Service Application Topology 3-8
Lab A: Planning a Service Application Architecture 3-17
Lesson 3: Configuring Service Application Federation 3-18
Lab B: Federating Service Applications between SharePoint Server Farms 3-29

Module Overview
Service applications were introduced in SharePoint 2010, replacing the Shared Service Provider
architecture of Microsoft Office SharePoint Server 2007. Service applications provide a flexible design for
delivering services, such as managed metadata or PerformancePoint to users who need them. There are
several deployment topologies available to you when you plan your service application implementation.
These range from a simple, single-farm, single-instance service application model to more complex, cross-
farm, multiple-instance designs. What remains most important is that you create a design that matches
the needs of your organization's users in terms of performance, functionality, and security.
This module reviews the service application architecture, how to map business requirements to design,
and the options for enterprise scale, federated service application architectures.
Objectives
Explain the service application architecture.
Describe the fundamental options of service application design.
Describe how to configure a federated service application deployment.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
3-2 Planning and Implementing a Service Application Architecture
Lesson 1
Planning Service Applications
The service application architecture was introduced in Microsoft SharePoint Server 2010, replacing the
Shared Service Provider (SSP) model of Microsoft Office SharePoint Server 2007. The architecture remains
consistent in SharePoint 2013, with the addition of new service applications. More than 20 services ship
with SharePoint Server 2013, some of which are new to this version, whereas others are enhanced.
The service application architecture is consistent across all of the SharePoint 2013 on-premises and online
stock-keeping units (SKUs).
In this lesson, you will see how service applications are structured and the functionality that they offer to a
SharePoint 2013 designer.
Lesson Objectives
Describe the service application architecture.
List some of the core service applications and their functions.
List the service applications that are available to SharePoint Online users.
Overview of Service Application Architecture
Service applications provide specific functionality
to users in SharePoint 2013. This includes access to
application functionality with Microsoft Excel 2013,
Microsoft Visio 2013, and supporting services such
as the Managed Metadata Service or the Business
Connectivity Services. In addition, there are
underlying service applications that provide
functionality across SharePoint 2013, such as the
Application Discovery and Load Balancer Service
Application and the State Service. These are not
configurable from the service application listing on
the Manage Service Applications page. The
framework of the service application architecture in SharePoint 2013 is designed to enable architects to
select only the services that are required to deliver a business solution.
A service application has the following components:
An administrative interface, through which you can manage the associated service application
An application pool
A service application proxy group
A service database or databases, dependent on the requirements of the service
One or more physical instancesthe service process running on a physical server
For a service application to talk to a specific web application, it must use a service application connection.
When you deploy a service application, you create a service application connection, which is more
commonly known as a proxy. The proxy manages the connection information so that the service
application can communicate with service requests from service consumers, such as Web Parts. You can
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
link and manage service applications against individual web applications. This means that you have the
flexibility to deploy multiple service application instances, which you can isolate to match performance or
security requirements. You should remember that by default, service applications are associated with all of
the web applications on a farm, so you have to specifically associate service applications to web
applications if you dont want the default settings. A service application proxy is created automatically
when you create a new service application.
You can group multiple proxies together, which is then referred to as a service application connection
group, or proxy group. By default, SharePoint creates a single proxy group called default. You can create
additional proxy groups to re-associate service applications to web applications if needed.
The majority of service applications have one or more associated databases. The system-generated names
for these databases are not easy to relate to the service application. For easier management and
recognition, you should define your own database names for your service application databases. You
should be aware of the potential size to which these databases can grow.
The service application architecture runs across the SharePoint 2013 and SharePoint Online SKUs,
although not all SKUs offer all of the SharePoint services. The service application architecture is also
extensible, so third-party vendors can develop service applications that you can deploy in your solution.
The flexibility of the service application architecturewhere you can deploy multiple instances of the
same serviceprovides a range of design options for SharePoint 2013 architects. You can implement
multiple instances of a service application for resilience, performance, or security.
Service application workflow
Service applications deliver service functionality to users. When a user triggers a service request from a
browser, the requestsuch as a keyword searchis sent through the Web Front-End (WFE) server, which
may be preceded by a hardware network load balancer.
The WFE server sends a request through to the application server that serves the service application. The
service application architecture in SharePoint 2013 enables multiple servers to deliver instances of the
same service application, so there is a software load balancer that routes requests to the appropriate
server.
All communication uses WCF, so there is no direct access to the service application databases. By default,
communication between web servers and service applications in a farm takes place by using HTTP (port
32843), but you can select either HTTP (port 32843) or HTTPS (port 32844). Third-party companies that
develop service applications can also implement NetTcpBinding (port 32845) to provide high-
performance communications with WCF clients. NetTcpBinding is generally the best option for services
operating inside a firewall, such as on an intranet site. Administrators can use the Service Applications
page to change the protocol and port binding for each service application.
Communication between service applications and Microsoft SQL Server takes place over the standard SQL
Server ports or the ports that you configure for SQL Server communication.
For the following service applications, information is cached to improve performance:
Access Services
Excel Services
PerformancePoint Services
Word Automation Services
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Overview of Individual Service Applications and their Dependencies
There are over 20 service applications shipped
with SharePoint 2013 Enterprise Edition. The
following section highlights some of the most
commonly configured service applications for
enterprise deployments and reviews those that are
new to SharePoint 2013.
Note: For a full list and description of the
SharePoint 2013 service applications, see Technical
diagrams for SharePoint 2013 at
Commonly configured enterprise service applications
There are some service applications that just about every SharePoint 2013 administrator will configure at
least once. This may be due to their popularity, or because other services applications are dependent on
functionality they offer. Those applications that tend to be popular with users include:
Excel Services. This service application enables you to publish Excel 2013 workbooks on a SharePoint
2013 server. It comprises Excel Calculation Services, the Excel Web Access Web Part, and Excel Web
Services for programmatic access.
Search Service. This service application provides enterprise search functionality across your
environment. Search has been reengineered to include FAST functionality.
PerformancePoint Services. This service application provides tools to develop UI options, such as
dashboards, scorecards, and key performance indicators, to help monitor and analyze business
performance.
Visio Services. This enables users to render Visio diagram in a web browser. The content can also be
refreshed and recalculated for diagrams hosted on a SharePoint site.
Services that offer supporting functionality on which other service applications often depend include:
Business Connectivity Service. Business Connectivity Services (BCS) provides the access to external
systems data so that it can be used in SharePoint 2013 applications. Several service applications are
closely associated with BCS, such as User Profile Services, because it provides access to user
information held on external systems.
Managed Metadata Service. The Managed Metadata Service (MMS) enables you to use metadata
features, such as managed metadata, term sets, and content types across web applications and site
collections.
Secure Store Service. This service provides a database that is used to store authentication credentials.
It is used by some other service applications to provide external data access, including Excel Services
and PerformancePoint Services.
State Service. This service provides temporary storage for user session data for SharePoint Server
applications. It is a dependency for a number of other services applications, including Visio Graphics
Services and PerformancePoint Services. The State Service can only be configured through Windows
PowerShell.
User Profile Service. This service provides the ability to create and administer user profiles that can be
accessed from multiple sites and farms.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
New service applications
There are three new service applications in SharePoint 2013:
App Management Service. This service application enables administrators to manage the new
SharePoint Apps, which are available with SharePoint 2013. SharePoint Apps can be purchased from
an external vendor or developed internally within an organization. The App Management Service
checks user access permissions and licensing for Apps usage.
Translation Service. This service application provides automatic language translation, so that content
from one site can be automatically translated into another language. This is closely linked to the
variations functionality offered in SharePoint 2013, which enables administrators to deliver duplicate
site environments for use in different languages.
Work Management Service. This service application enables users to synchronize tasks between a
range of Microsoft environments, including Exchange and Project Server.
Deprecated or merged service applications
For administrators familiar with SharePoint 2013, there are a number of service applications that have
changed. These include:
Web Analytics Service. The functionality of the Web Analytics Service has been incorporated into the
Search Service.
Office Web Apps Service. This is now a separate product, rather than a SharePoint service application.
Service Applications in SharePoint Online 2013
SharePoint Online is available in various editions.
The service applications available to you will
depend on which edition you purchased.
Note: The full list of SharePoint Online
versions is detailed in Module 1 of this course.

The following tables list the facilities offered in SharePoint Online (Plans 1 and 2) and in Office 365.
Features
SharePoint Online
Plan 1
SharePoint Online
Plan 2
Access Services Yes Yes
App Management Services Yes Yes
BCS: Secure Store Service No Yes
InfoPath Forms Services No Yes
Service Application Platform Yes Yes
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Features
SharePoint Online
Plan 1
SharePoint Online
Plan 2
State Service N/A N/A
Managed Metadata Service Yes Yes
PowerPoint Automation
Services
No No
SharePoint Translation
Services
Yes Yes
Word Automation Services No No
Excel Services No Yes
PerformancePoint Services No No
SQL Server Reporting Services
(SSRS) Integrated Mode
No Yes
Visio Services No Yes
Work Management Service Yes Yes

Features
Office
365
Small
Business
Office
365
Small
Business
Premium
Office
365
Midsize
Business
Office
365
Enterprise
E1
Office
365
Enterprise
E2
Office
365
Enterprise
E3
Office
365
Enterprise
E4
Access Services Yes Yes Yes Yes Yes Yes Yes
App
Management
Services
Yes Yes Yes Yes Yes Yes Yes
Secure Store
Service
No No No No No Yes Yes
State Service N/A N/A N/A N/A N/A N/A N/A
PowerPoint
Automation
Services
No No No No No No No
SharePoint
Translation
Services
Word
Automation
Services
Excel Services No No No No No Yes Yes
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Features
Office
365
Small
Business
Office
365
Small
Business
Premium
Office
365
Midsize
Business
Office
365
Enterprise
E1
Office
365
Enterprise
E2
Office
365
Enterprise
E3
Office
365
Enterprise
E4
PerformancePoint
Services
PerformancePoint
Services (PPS)
Dashboard
Migration
SQL Server
Reporting
Services (SSRS)
Integrated Mode
Visio Services No No No No No Yes Yes
Work
Management
Service

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Designing and Configuring a Service Application
Topology
When you design your service application topology, it is essential that you understand the available
topologies and the reasons why you would choose one over another. Like any design, the options should
be selected based on the business requirements of your organization.
Service applications provision functionality to web applications, either specific functionality such as
PerformancePoint and Search, or underlying functionality such as Managed Metadata Services and Secure
Store Service. You can use this architecture to contain service application use, so that only web
applications, site collections, and sites that need the service application function have access to it. This
means that you can make best use of logical and physical resources in your farm.
You can also create federated services, so that your enterprise environment can deploy cross-farm
services, where a web application on Farm A can consume service applications that are provisioned from
Farm B. This design option makes it possible to develop service application-based topologies.
Whatever your final design, you must base it on the business requirements and maintain documentation
to support your environment.
Lesson Objectives
Describe the basic design choices of a service application topology.
Explain the options for a single farm service application topology.
Describe the rationale and requirements for cross-farm federation.
Describe how service applications provision access to external data.
Explain how to map business requirements to service application design.
Explain how to document your service application design.
Service Application Topologies
Service applications can have a major impact on
the topology of your overall solution because
users want functions and service applications that
offer a wide range of functionality. The breadth of
these service offerings means that you can choose
from a wide range of implementation topologies.
The flexibility of the service application
architecture enables you to create many
alternative designs. It is important that you ensure
that your design is functional rather than
unnecessarily complex. Key elements to remember
when you select your topology design include:
Granularity of topologies. Most important is that you use the granularity of the service application
architecture to ensure that you can deliver the business requirements across the organization without
wasting resources, such as administrative time or hardware budget.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Extensibility of topologies. Remember that you can now extend your service architecture. In addition
to adding service applications or extending them across farms or domains, you can also increase
performance or capacity by adding service instances to deal with growth. This may also be an option
for managing spikes in demand or unexpected changes in usage.
Delivery of service-driven topologies. There is also the option for developing a service application
driven topology. This may sound unlikely, but search is a service application and it is common for
organizations to set up search-specific farms. You may choose to extend this beyond a specific service
and include a range of services. The key point is the service application flexibility, which should
encourage you to design a solution that will fit your business.
For service-driven topologies, SharePoint 2013 provides six service applications that can be shared across
farms, so that a large enterprise organization can offer a consistent, centralized service to all farms. The
design options and benefits of federated service applications are covered in this lesson, whereas the
practicalities of configuring service federation are covered in Lesson 3, Configuring Service Application
Federation.
Irrespective of whether you choose to implement a single farm or a multiple farm environment, your
design must be based on the delivery of the best possible services to users who need them, while
minimizing resource utilizationboth human and computeracross your organization.
Single Farm Service Application Architecture
There are a range of options for deploying service
applications on a single farm. Although these are
covered in some detail in Course 20331B, Core
Solutions of Microsoft SharePoint Server 2013, it is
worth reviewing these options, with a specific
focus on design.
When working on a single farm, you must use the
flexibility and security offered by the SharePoint
2013 logical and physical architectures to develop
the best solution for your organization. This
flexibility means that there may be many options
to suit your business needs, but the design choices
fall into three main topologies.
Single farm with a single service application proxy group
In this topology, all of the service applications are in a single default service application proxy group. All
sites have access to all of the farm service applications. This may seem like a simple approach, but
simplicity is often the most elegant solution. This option is easy to deploy and manage because much of
the configuration capitalizes on the default settings. The design offers centralized maintenance with
minimal effort, and it is unlikely that users will have issues when they access service applications.
If there is an issue regarding this topology, it is scalability. There is no separation of services dependent on
the requirements of unique areas of the business. There is also no option for individual departments to
manage their own service applications. Therefore, if the volume of business increases, the load on the
central IT team may also increase.
This is almost certainly the most common deployment topology for service applications, although part of
that may be to do to the fact that it works for the majority of new installations. If this is the solution that
you choose, you should review it as part of your ongoing review process to determine whether your
organization may gain benefits from other deployment options for service applications.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Single farm with multiple service application proxy groups in multiple application
pools
This solution provides greater isolation by putting services that are dedicated to the custom group in a
separate application pool. It is important to note that you can share service applications across both
default and custom groups. You can also share them among web applications.
In this topology, simplicity is sacrificed for greater granularity. This inevitably makes management more
complex, but this should not be an issue if you maintain documentation of your solution.
There is greater isolation of services, which provides some data security. It may be that one of the service
applications in a custom group is a second instance of a service application that is available in the default
group. Deployment of another instance will consume additional farm resources, but this may be justified
by the increased granularity of service.
Single farm with multiple service application proxy groups in a single application
pool
This is basically an extension of the practices that the previous examples used. You can create a farm that
has more than one custom group. This may be a requirement because several divisions require a single
service to be isolated. For example, each may use an instance of Excel Services that they want to keep
separate, perhaps maintaining different databases to increase separation.
You can also use this type of topology to provide unique service applications to individual web
applications, which use a delegated model to reduce pressure on central IT resources. Topologies that
provide custom service application proxy groups are most useful for organizations that have divisions or
teams that require a degree of separation from the rest of the business. The custom group may also be
useful for specialist sites where separation is essential, such as sites that provide access to external partners
or customers.
Cross-Farm or Federated Topologies
Enterprise organizations are not always more
complex than other environments. However, they
are usually much larger, so there is greater scope
for more unique requirements and pressing
solution boundaries. Remember that if you work
for a large enterprise, it does not mean that you
must design a complex solution.
In the scenario on the slide, there are a number of
different approaches to service application
deployment.
Enterprise Services Farm
You can use an Enterprise Services Farm to share service applications. This enables the central IT
department to provision all shareable services across the organization, such as corporate taxonomies
through the Managed Metadata Service. This topology is also attractive for pan-organization Search
Service implementations.
Farms with no local service applications
In the diagram on the slide, Farm A has no local service applications, but it consumes all of its services
from the Enterprise Services Farm. This limits the range of possible services to the User Profile Service, the
Managed Metadata Service, the Business Connectivity Services, the Search Service, the Secure Store
Service, and the Web Analytics Service.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
This means that the farm is probably not one where users would consume service applications that cannot
be published across farms, such as Excel Services or Visio Services. This design is probably best suited to
publishing environments.
The benefits of this design include:
Centralization of resources on the Enterprise Services Farm.
Reduced administrative overheads on Farm A.
Provision of pan-organization services, such as the User Profile Service and the Managed Metadata
Service.
Collaborative farms
Farm B has a range of local services, which makes it more useful for collaborative working because these
may include Excel Services and Access Services. These service applications must be provided on the local
farm because they cannot be consumed across farms. This taxonomy still benefits from the organization-
wide User Profile Service and Managed Metadata Service. Note that there is a divisional Managed
Metadata Service on Farm C, which indicates that there is a subgroup taxonomy that is applicable to both
Farm B and Farm C.
Access to centralized service application resources.
Local administrative capability.
Integration with other farms.
Specialized farms
Farm C is a smaller environment, with only one web application that uses primarily local services. This may
indicate that this is a specialist department that has specific requirements. In this instance, the Excel
Services and Business Connectivity Services applications are isolated from other farms.
This farm also has its own Managed Metadata Service so that it can manage a taxonomy that is distinct
from the organizations taxonomy. Note that in this example, this farm has access to two MMS service
applications, and could use either one.
Service isolation.
Metadata autonomy.
Access to centralized services, such as the User Profile Service and the Managed Metadata Service.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Accessing External Data from Service Applications
There are a number of SharePoint 2013 service
applications that can provide access to external
data. The definition of external data in SharePoint
2013 needs to be flexible to support the different
options offered different service applications.
For Business Connectivity Services (BCS), external
data can mean Web Services, external line-of-
business applications, or external databases. The
key emphasis here is that all of these are offered
outside the SharePoint 2013 environment. For
other service applications, such as the Visio
Graphics Service, external data can exist on an
external data source, but it often means an Excel workbook that is hosted in a SharePoint 2013 library.
This is still external to the Visio Graphics service application, but is not stored on a non-SharePoint
environment. This topic will focus on as the core external data access service.
Note: For more information about working with Business Intelligence-focused service
applications, see Module 7, Planning and Configuring Business Intelligence.
Accessing external data with BCS
BCS provides centralized services that enable you to integrate external data sources with SharePoint
business solutions. The most common means of displaying external data in SharePoint 2013 by using BCS
is to create external lists, but you can include external data by including external data columns in
SharePoint 2013 lists or libraries.
BCS provides functionality to perform a range of actions on external data, such as:
Create.
Read.
Update.
Delete.
Query.
This is often referred to as CRUDQ. You can limit these functions depending on the permissions that you
set on the external data source.
Advantages of BCS integration
BCS offers the following advantages over other integration solutions:
Centralization. BCS uses External Content Types to wrap the data that is presented to SharePoint
applications. These content types are stored centrally in SharePoint so they can be made available to
any number of SharePoint solutions, streamlining the integration process and minimizing the need to
develop multiple unique data source access methods. Provisioning is administered once and
maintained centrally, so new requirements from business development staff do not need continual
recreation of data access connections.
Managed Security. BCS manages all secure transactions with external data systems. Credentials are
managed centrally through the Secure Store Service, which means that users and developer do not
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
need to concern themselves with providing a user ID and password or developing a unique security
mechanism.
Search Integration. You can extend Search Service functionality thought BCS, bringing external and
SharePoint data into a common, secure, enterprise search environment.
Like all service applications, BCS deployment is a function of business requirements. BCS can enable you
to create fully integrated solutions, drawing information from diverse sources and surfacing that
information in a PerformancePoint dashboard or enhancing social computing by adding external user
information from external Human Resources databases. The key point is that you need to identify what
users need and then reconcile the availability of line-of-business applications to satisfy those
requirements. You can then use BCS to create and manage the necessary data connections.
Note: For detailed information about configuring Business Connectivity Services, see
Deploy a Business Connectivity Services on-premises solution in SharePoint 2013 at
Identifying Business Requirements for Service Applications
Mapping business requirements to the available
service applications demands that you have a
thorough understanding of what service
applications offer and what your business users
want to achieve. It should not be your goal to use
as many service applications as possible, but to use
the right ones. For example, just because
information workers use the Microsoft Office client
applications does not mean that you should
deploy all of the service applications that are
related to Microsoft Office; these are necessary
only if you want to use their functionality.
Required applications
Identifying service applications that the organization requires is dependent on the information that you
gather as part of your analysis of business requirements. It is rare for a user requirements document to
specify any need for the User Profile Service, so you must interpret which services are necessary to deliver
business functionality. For example, if the business requirements specify that the business wants to use
more social computing functions, such as tagging and My Sites sites, you should be able to rationalize
that to a need for the User Profile Service.
Security through service isolation
When you have identified all of the required services, you should then identify whether some divisions or
departments have a requirement for isolated instances of these services. This is not a function of
preference, but rather a result of real business need. For example, a department may have a taxonomy
that they want to use for Search. If this is unique to this department, you should consider deploying a
separate service instance that enables departmental users to manage their own taxonomy. These users will
not be separated from the corporate Managed Metadata Service, but they will have an additional
taxonomy that they can use. You may also need to identify the level of isolation that is necessary for
service applications so that you can decide whether to provide separate service application databases.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Availability through multiple instances
You should identify which, if any, services are critical to your business and a level of performance that is
acceptable to the users. When you have this information, you may choose to include multiple instances of
important service applications for improved performance or increased security. If you do require multiple
instances for resilience, ensure that you host these instances on separate servers. For example, you could
implement two instances of Excel Services in the same application pool to ensure increased availability for
users of Excel Services. By having two instances on separate servers within the farm, you can ensure that
the service continues, even if an application server fails.
Performance through separation
All service applications place resource demands on servers. If you have a series of resource-intensive
service applications, such as Excel Services or the Visio Graphics Service, you should ensure that you
implement these on separate platforms if performance becomes an issue.
Multiple farms
From a performance and management perspective, your goal should be to deliver a single farm solution
for your organization. Often, architects regard farm separation as the first, or even only, option to isolate
users. However, web applications and site collections are the first options that an architect should select.
You can only share six of the SharePoint 2013 service applications across farms:
Business Data Connectivity
Machine Translation
Managed Metadata
User Profile
Search
Secure Store
If you must deploy multiple farms, you should identify and group common requirements so that you can
design for easy management and better performance.
Centralized services
If you have a compelling reason for establishing two or more farms for your deployment, you should
identify which of the available service applications you can share. This will minimize administrative
overhead and create a corporate unity for business components such as social computing.
Discussion: Identifying Business Requirements in Your Organization
You should consider the following questions when
identifying business requirements in your
organization:
What service applications does your
organization require?
Do any teams require isolated service
applications?
Do you need to provide multiple instances of
any service applications?
How can you deliver acceptable performance?
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
How many farms does your organization require and what opportunities do you have to share
services across farms?
Do the needs of your organization warrant a centralized services farm?
Mapping Instances by Using the Service Applications Planning Worksheet
You must document the service applications that
you plan to implement and the core information
about them. You should always maintain
documentation about the service applications that
you deploy. This will help you maintain the
environment, and it will enable you to ensure that
you have configured dependent service
applications. Microsoft publishes a planning
worksheet for service applications that can help
you to identify and record your service application
requirements.
Note: To download a planning worksheet,
see Planning worksheets for SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=302072
Planning worksheet
The planning worksheet is specific to the logical design that you have created for your organization
because it reflects the web applications with which services are connected. The columns in the worksheet
include:
Service application. This column lists all of the service applications. You can add service applications
based on your SharePoint 2013 SKU and any third-party service applications that you use.
Description. This column gives a brief description of the service functionality. Although this may not
be necessary for an experienced architect, it makes it easier to map services against business
requirements. You may add dependencies here to assist less experienced IT staff.
Farm. The name of the farm on which the instance or instances should be deployed.
Federation. If federation is required, list the farm or farms with which this instance is to be federated.
Service application instances. This column enumerates the number of instances for each service
application. Make sure that you have all of the instances that are necessary for isolation and
performance.
Web application proxy groups. This column lists the web application proxy groups. For each web
application that uses a service application, you should identify the name of the proxy group. For most
proxy groups, this should be the Default option. However, you can also specify the custom groups
with their associated web application. There may be a series of these columns.
Proposed database names. This column lists the names of the service application databases that you
intend to create. For each service application that you create, you should name the associated
database or databases. Remember that multiple instances can share a common database set, so if you
want to isolate service applications at the database level, you must provide names for each service
instance. You may need to consult with your database administrator (DBA) to ensure that you select
names that fit with any existing standard.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Service Application Name. The name by which the service application will be known.
Proxy. The name of the application proxy.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Planning a Service Application Architecture
Scenario
The logical design for the Contoso Ltd. environment has been signed off, so you now need to define the
service applications that are necessary to service the business requirements. Your team must review the
options for fulfilling the business requirements that have been agreed by the executive board.
Objectives
Create a service application plan for SharePoint 2013 at Contoso.
Virtual Machine: 20332B-NYC-CL
o User name: admin
o Passw0rd: Pa$$w0rd
Exercise 1: Planning a Service Application Topology
Scenario
You have received the executive requirements for the Contoso SharePoint 2013 implementation. You
must identify the service applications and configuration that you should deploy to service the business.
2. Complete the Service Applications Planning worksheet
Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen
In the E:\Mod03\Starter folder, read the information in the Contoso Services
BusinessRequirements.docx file.
Task 2: Complete the Service Applications Planning worksheet
In the E:\Mod03\Starter folder, open and complete the worksheet in the SharePoint 2013 Service
Applications Planning Worksheet.xlsx file, based on the information you have reviewed in Task 1.
Shut down the NYC-CL1 virtual machine.

Results: A completed Service Application Planning worksheet.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Configuring Service Application Federation
For enterprise or complex SharePoint environments, you can federate service applications between farms.
The implementation of cross-farm service applications requires that you complete a series of
configuration steps on both the publishing and consuming SharePoint Farms.
In this lesson, you will see what service application federation offers and how to complete the federation
process.
Lesson Objectives
Describe service application federation.
Describe how to plan federation.
Describe the reason and steps to exchange certificates between farms.
Describe how to manage inter-farm trust relationships.
Explain how to publish services.
Describe how to set service application permissions.
Describe the steps to start consuming published service applications.
Understanding Service Application Federation
SharePoint 2013 provides the ability for one farm
to use service applications that are available on
another farm, referred to as federated or cross-
farm services. This facility makes it possible to
maximize resource productivity and to create
service hubs, where one farm is implemented
essentially to provide services to other farms.
Not all service application can be shared in this
way. Remember that you can only share the
following service applications between farms:
Machine Translation
Managed Metadata
User Profile
Search
Secure Store
In a federated environment, the farm that shares one or more services is referred to as the publishing
farm, while a farm that uses service applications shared by a publishing farm is referred to as a consuming
farm.
So why bother federating services between farms? The answer to this is the same answer that can be
given to the question, why use service applications rather than stick with the Microsoft Office SharePoint
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Server 2007 model of a single Shared Service Provider (SSP)? The answer to both questions is resource
provision and management. The old SSP structure gave all web applications access to the services
available on a farm. This was a waste of resources and meant that services could not be isolated from web
applications that had no reason to deliver the service to its users. The SharePoint 2010 service application
architecture provided greater granularity and meant that only the web application user who needed
access to a service would get it.
The extension of this is to enable a farm to provide services to other farms, which saves duplication of
resources across different farms; there is no need to have servers on different farms providing Search
services when it can be managed centrally on one farm.
Federated services enable a new form of service application-based topology. In this design, you can create
one or more farms whose function is to provision federated services, such as Managed Metadata Services,
across an entire enterprise implementation.

Mixed SharePoint 2010 and SharePoint 2013 environments
Service application federation was introduced in SharePoint Server 2010. In a situation where you are
migrating from a SharePoint 2010 to a SharePoint 2013 infrastructure, your SharePoint 2010 farms can
continue to consume services from a farm that has been upgraded to SharePoint 2013. The exception to
this is the Machine Translation Service, which was only introduced in SharePoint 2013.
Planning Service Federation
There are two elements to consider when
designing a federated service deployment:
Which services you need to federate, if any.
What steps necessary to deploy a federated
service application.
What services do you need to federate?
When you develop a service application
architecture against your logical and physical
architecture designs, you need to identify whether
you will need to create a federated service
environment. Clearly, there is no needand
indeed, no optionto federate services if you design a single farm implementation. For most designs, the
key drivers are the need to:
Rationalize use of resources. If you have a limited number of users who require a service application
that can be federated, you can provision the necessary functionality on a single farm and make it
available to others. This limits unnecessary resource use on multiple servers. It also means that your
administration is focused on a single farm, rather than multiple farms.
Provision an enterprise-wide service. For several of the service applications that can be federated, it is
probable that you would like to provision their functionality across your entire organization. For
example, most multi-farm enterprises will have a single set of Managed Metadata, such as taxonomy
or terms sets. It is logical that you should manage these from a single location. Should you have a
sub-division on a separate farm that requires additional Managed Metadata Services, you can have a
local farm MMS instance which may have metadata that is sub-division specific. In this case, you may
place the local MMS instance in an alternative group, custom rather than default, for web
applications that need that MMS content.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Deploy an enterprise-wide service-driven topology. This offers a number of advantages, such as
centralized administration and resource management. A federated service application topology is
most commonly associated with large enterprise deployment. The service application most commonly
deployed in this topology is the search service, because it is usually required across the entire
organization and because it can have large resource and capacity requirements. By federating search
it is possible to optimize other farms for the services that run on them, rather than having to optimize
all farms for search.
It is worth noting that in wide area networking (WAN) environments, it is not always advisable to federate
all services. This is usually due to request latency, which can cause performance issues across a WAN. As a
general rule, you can federate Search, managed metadata, and Machine Translation Services across a
WAN infrastructure. The Business Data Connectivity service can prove more problematic, depending on
where the line-of-business data source is located on a WAN environment.
It is strongly recommended that neither User Profile Services nor the Secure Store Service should be used
over a WAN connection. The User Profile service application requires a direct database access.
What steps are necessary to federate a service application?
The steps necessary to successfully federate a service application are:
Exchange trust certificates between the farms.
Publish the service application on the publishing farm.
Set permissions on the service application on the consuming farm.
Connect to the published service application on the consuming farm.
Add the shared service application to a web application proxy group on the consuming farm.
These steps are covered in the following topics.
Certificate Exchange
To implement cross-farm service application
sharing, you must establish a trust relationship
between the two farms by exchanging trust
certificates. This exchange must be a two-way
trust; both farms must exchange certificates. In this
configuration, one farm is the publishing farm,
whereas the other is the consuming farm.
Publishing. The publishing environment makes
one or more service applications that are
running on the farm available to one or more
external farm (consuming farm).
Consuming. The consuming farm uses one or
more service applications that are running on the publishing farm. These service applications are
made available to the consuming farms web applications.
Exporting and copying trust certificates
The exchange of certificates between farms is a two-part operation, which involves:
1. The consuming farm providing two certificates to the publishing farm:
o Root certificate
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Security Token Service (STS) certificate
2. The publishing farm providing one certificate to the consuming farm:
o Root certificate
You must use Windows PowerShell cmdlets to complete these processes; they cannot be achieved
through the Central Administration UI. You need to be sure that the logged-on user has appropriate
access to the Windows PowerShell cmdlets.
Note: For more information about using Windows PowerShell to administer SharePoint
2013 and the necessary memberships, see Use Windows PowerShell to administer SharePoint
Exporting certificates from the consuming and publishing farms
On the consuming farm, use the following procedures and cmdlets to export the required certificates
from the consuming farm.
Exporting the root certificate (from consuming farm)
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2013 Products.
3. Click SharePoint 2013 Management Shell.
4. At the Windows PowerShell command prompt, type the following command:
$rootCert = (Get-SPCertificateAuthority).RootCertificate
$rootCert.Export("Cert") | Set-Content <C:\<PATH>\<PATH>\ConFarmRoot.cer> -Encoding
byte
(c:\<path>\<path>\ConFarmRoot.cer is the path to which you export the root certificate.)
Exporting the STS certificate(from consuming farm)
On the consuming farm, use the same process to launch Windows PowerShell as described in Exporting
the root certificate (from consuming farm) and then run the following cmdlets:
$stsCert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate
$stsCert.Export("Cert") | Set-Content <C:\<PATH>\<PATH>\ConFarmSTS.cer> -Encoding
byte
(c:\<path>\<path>\ConFarmSTS.cer is the path to which you export the root certificate.)
Exporting the root certificate (publishing farm)
On the publishing farm, use the same process to launch Windows PowerShell as described in Exporting the
root certificate (from consuming farm) and then run the following cmdlets:
$rootCert = (Get-SPCertificateAuthority).RootCertificate
$rootCert.Export("Cert") | Set-Content <C:\<PATH>\PubFarmRoot.cer> -Encoding byte
(c:\<path>\PubFarmRoot.cer is the path to which you export the root certificate.)
Copy certificates to the publishing and consuming farms
After you consume and publish farm certificates, copy them between the two farms in preparation to
establish the trust relationships. There is no special procedure to copy the files; simply copy the two root
and Security Token Service (STS) certificates from their destinations (c:\<path>\ConFarmRoot.cer and
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
c:\<path>\ConFarmSTS.cer for the consuming farm and c:\<path>\PubFarmRoot.cer for the publishing
farm in the examples above) to the other farm server.
Managing Trusts
After you copy the required certificates between
farm servers, you can then create the necessary
trust relationships, either by continuing to use
Windows PowerShell or through the Central
Administration UI. This topic explains the steps
that you need to complete to establish trust
between the two farms.
Importing certificates and creating trust
relationships with Windows PowerShell
After the certificate files are copied between the
farms, you must then import the certificates and
establish trust relationships on each farm.
Importing certificates and creating a trust relationship on the consuming farm
As noted in the procedures in the topic Certificate ExchangeExporting the root certificate (from
consuming farm), log on as a user with appropriate memberships on the consuming farm server, and then
run the following cmdlets:
$trustCert = Get-PfxCertificate <C:\<PATH>\PubFarmRoot.cer>
New-SPTrustedRootAuthority <PubFarm> -Certificate $trustCert
(c:\<path>\PubFarmRoot.cer is the location and name of the root certificate file copied from the
publishing farm and <PubFarm> is the unique name of the publishing farm.)
Importing certificates and creating a trust relationship on the publishing farm
On the publishing farm, you must import the consuming farms root certificate and STS certificate, and
then create a trusted service token issuer. When you create a trusted service token issuer, you are
registering the consuming farm with the SharePoint security token service as a trusted consumer of
service applications.
Importing the root certificate
On the publishing farm, use the same process to launch Windows PowerShell as described in the topic
Certificate ExchangeExporting the root certificate (from consuming farm) and then run the following
cmdlets:
$trustCert = Get-PfxCertificate <C:\<PATH>\ConFarmRoot.cer>
New-SPTrustedRootAuthority <ConFarm> -Certificate $trustCert
(c:\<path>\ConFarmRoot.cer is the location and name of the root certificate file copied from the
publishing farm and <ConFarm> is the unique name of the publishing farm.)
Importing the STS certificate and creating a trusted service token issuer
On the publishing farm, use the same process to launch Windows PowerShell as described in Certificate
ExchangeExporting the root certificate (from consuming farm) and then run the following cmdlets:
$stsCert = Get-PfxCertificate
<c:\<path>\ConFarmSTS.cer>
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
New-SPTrustedServiceTokenIssuer <ConFarm> -Certificate $stsCert
(c:\<path>\ConFarmSTS.cer is the location and name of the STS certificate file copied from the publishing
farm and <ConFarm> is the unique name of the publishing farm.)
Importing certificates and creating trust relationships with Central Administration
Completing the import of certificates and creation of trust relationships by using Central Administration
requires that procedures are run on both farms, as they do when using Windows PowerShell. To complete
the procedure on the two farms, you must log on as a user who is a member of the Farm Administrators
SharePoint group.
Importing certificates and creating a trust relationship on the consuming farm
To import the publishing farm root certificate on the consuming farm, complete the following steps:
1. On the SharePoint Central Administration website, click Security.
2. On the Security page, in the General Security section, click Manage trust.
3. On the Trust Relationship page, on the ribbon, click New.
4. On the Establish Trust Relationship page type a name that describes the purpose of the trust
relationship.
5. Browse to and select the Root Authority Certificate for the trust relationship (in the example, this is
PubFarmRoot.cer).
6. Click OK.
Importing certificates and creating a trust relationship on the publishing farm
To import the consuming farm root and STS certificates on the publishing farm and to create a trusted
service token issuer, complete the following steps:
1. On the SharePoint Central Administration website, click Security.
2. On the Security page, in the General Security section, click Manage trust.
3. On the Trust Relationship page, on the ribbon, click New.
4. On the Establish Trust Relationship page type a name that describes the purpose of the trust
relationship.
5. Browse to and select the Root Authority Certificate for the trust relationship (in the example, this is
ConFarmRoot.cer).
6. Select the check box for Provide Trust Relationship and type a name for the token issuer.
7. Browse to and select the STS certificate that was copied from the consuming farm (in the example,
this is ConFarmSTS.cer).
8. Click OK.
After you complete these procedures, you will have established a trust relationship between the farms.
This will enable you to consume service applications on the consuming farm that have been shared on the
publishing farm.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Publishing Federated Services
The service application that you want to share is
implemented on the publishing farm. Just because
it has been published for consumption on an
external farm does not mean that it is any
different than a local service application. You can
continue to allocate the service application to web
applications on the local farm.
The publishing process requires that the logged-
on user be a member of the Farm Administrators
SharePoint group for the publishing farm. You can
complete the configuration both through the
Central Administration UI and Windows
PowerShell. If you intend to use PowerShell, you must ensure that the logged-on user has the appropriate
memberships.
2013 at http://go.microsoft.com/fwlink/?Linkid=302073 .
Publishing a service application by using the Central Administration UI
You must, of course, have one of the shareable service application configured on your publishing farm.
This procedure was covered in detail in course 20331B, Core Solutions of Microsoft SharePoint Server 2013.
When you have a service application installed, the procedure for publishing your service application
through the Central Administration UI is as follows:
1. On the SharePoint Central Administration website, click Application Management, and then click
Manage service applications.
2. Click the row that contains the service application that you want to publish.
3. On the ribbon, click Publish.
4. In the Publish Service Application dialog box:
o Select the Connection Type that you want from the drop-down list.
o In this instance, you want to publish the service application so you select the check box for
Publish this Service Application to other farms.
5. Copy the Published URL into a text editor and save it for use later in the federation process.
Note: For detailed steps for configuring a range of service applications, see Configure
services and service applications in SharePoint 2013 at
http://go.microsoft.com/fwlink/?Linkid=302074 . You will need this URL to configure the
consuming farms connection to the federated service application. This procedure is covered in
this lesson in topic Consuming Federated Services.
6. You can provide descriptive text and a link to a Web page that will be visible to administrators of
remote farms. This is optional, but it is recommended, particularly if you are not responsible for the
remote farm administration.
7. To publish the service application, click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Publishing a service application by using Windows PowerShell
The procedure for starting Windows PowerShell is dependent on your server platform, Windows Server
2008 R2 or Windows Server 2012. Follow the correct procedure for your platform to launch Windows
PowerShell and then run the following cmdlet:
Publish-SPServiceApplication -Identity <ServiceApplicationGUID>
Note: If you do not know the ServiceGUID, you can present a list of all the services GUIDs
by running the PowerShell cmdlet Get-SPServiceInstance.
Service Application Permissions
You have now completed the first two steps in
federating a service application by establishing a
trust relationship between the two farms and
publishing a service application. The next phase is
to provide access permissions to the published
service application from the consuming farm.
There are two stages to this process, even if you
are only federating one service application. This is
because you must provide access on the
publishing farms Application Discovery and Load
Balancing Service Application to the consuming
farm. Without this, the consuming farm will not be
able to discover the federated service applications. Once permissions to this service are in place, you must
set permissions for all of the other service applications that you wish to federate between the publishing
and consuming farms.
You can use either the Central Administration UI or Windows PowerShell to configure access permissions
to a published service application, but for both you will need the farm ID for the consuming farm. This can
only be achieved by running the following Windows PowerShell command on the consuming farm:
Get-SPFarm | Select Id
To run this command, you must have the appropriate memberships.
2013 at http://go.microsoft.com/fwlink/?Linkid=302073 .
When you have the consuming farm ID, you can perform the following procedures to complete the
process by using either the Central Administration UI or Windows PowerShell.
Setting access permissions by using the Central Administration UI
The permissions provision configuration can be completed from the Central Administration UI, but you
must first get the ID of the consuming farm. In this procedure, you must be logged on as a user who is a
member of the Farm Administrators SharePoint group. The initial task is to set access permissions on the
Application Discovery and Load Balancing Service Application.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
1. On the publishing farm, on the SharePoint Central Administration website, click Application
Management, and then click Manage service applications.
2. Click the row that contains Application Discovery and Load Balancing Service Application.
3. On the ribbon, click Permissions.
4. In the Connection Permissions dialog box, complete the following steps:
a. Manually paste the ID of the consuming farm that you found by running the Get-SPFarm
cmdlet.
b. Click Add.
c. Select the consuming farm ID, then select the Full Control check box, and then click OK.
To provision access permissions for other service applications that you want to federate, repeat the steps
for each service application on the publishing farms Central Administration interface.
Setting access permissions by using Windows PowerShell
If you want to grant permissions by using Windows PowerShell, you must run the following commands on
the publishing farm. The logged on user must have the appropriate memberships to run Windows
PowerShell cmdlets.
$security=Get-SPTopologyServiceApplication | Get-SPServiceApplicationSecurity
$claimprovider=(Get-SPClaimProvider System).ClaimProvider
$principal=New-SPClaimsPrincipal -ClaimType
"http://schemas.microsoft.com/sharepoint/2009/08/claims/farmid" -ClaimProvider
$claimprovider -ClaimValue <confarmid>
(<confarmid> is the farm ID of the consuming farm that you found by running the Get-SPFarm cmdlet.)
Grant-SPObjectSecurity -Identity $security -Principal $principal -Rights "Full
Control"
Get-SPTopologyServiceApplication | Set-SPServiceApplicationSecurity -ObjectSecurity
$security
With these procedures completed, you can start using the federated service application on the consuming
farm.
Consuming Federated Services
The final steps in the federation process are to
connect to the published service application from
the consuming farm and to add a service
application connection from a web application.
You can create a service application connection by
using either the Central Administration UI or with
Windows PowerShell. For the former, you must be
a member of the Farm Administrators SharePoint
group; and for the latter, you must have the
appropriate memberships, as outlined earlier in
this lesson.
Creating a service application connection
Your first step to using a federated service application is to create a service application connection.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Central Administration
This section details the procedure for creating a service application connection for a published service
application. This assumes that you have completed all of the steps discussed earlier in this lesson.
1. On the consuming farm Central Administration website, click Application Management, and then
click Manage service applications.
2. On the ribbon, click Connect.
3. On the Connect drop-down menu, click the kind of service application to which you want to connect.
4. On the Connect to a Remote Service Application page, type the appropriate URL in the Farm or
Service Application address text box, and then click OK.
Note: This is the URL that the publishing farm administrator generated when he or she
published the service application. You can also insert the URL of the remote farms topology
service application (Discovery and Load Balancer Service Application).
5. The new Connect to a Remote Service Application dialog box displays the service applications that
match your URL. Click the row that contains the name of the service application, and then select the
check box to add the service application connection to the farms default list of service application
connections (that is, the default proxy group).
6. Click OK.
7. Type a new name into the Connection Name text box or leave the default name, and then click OK.
8. To complete the procedure, click OK.
Windows PowerShell
Again, this procedure assumes that you have completed all of the stages discussed previously in this
lesson.
At the Windows PowerShell command prompt, type the following cmdlets:
Receive-SPServiceApplicationConnectionInfo -FarmUrl <PubFarmTopologyURL>
In this sample <PubFarmTopologyURL> is the information that is retrieved by running the Get-
SPTopologyServiceApplication cmdlet on the publishing farm.
New-SPServiceApplicationProxy -Name " <ServiceApplicationProxyName>" Url
"<PubFarmTopologyURL>"
In this sample, <ServiceApplicationProxyName> is a unique name for a service application connection on
the consuming farm, and <PubFarmTopologyURL> is the service application topology URL that was also
used in the first cmdlet.
Add a service application connection to a web application
After you create your connection for the federated service application, you need to start using the service
application on one of the web applications on the consuming farm.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Central Administration
1. On the Central Administration website, click Application Management.
2. On the Application Management page, in the Service Applications section, click Configure service
application associations.
3. On the Service Application Associations page, select Web Applications from the View drop-down
menu.
4. In the list of web applications, in the Application Proxy Group column, click the name of the service
application connection group that you want to change.
5. Select the check box that is next to the service application that you want to add to the connection
group.
6. Click OK.
Windows PowerShell
At the Windows PowerShell command prompt, type the following cmdlet:
Add-SPServiceApplicationProxyGroupMember -Identity <service application proxy group>
-Member <members to add to the service application proxy group>

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Federating Service Applications between
SharePoint Server Farms
Scenario
Now that you have finished planning a service application topology, your next task is to use Contoso's test
environment to verify the process for sharing services between SharePoint 2013 server farms. First, you
must configure a trust relationship between two server farms by exchanging certificates, creating trusted
root certification authorities on each farm, and creating a trusted service token issuer on the farm that will
provide services. Next, you will publish a service application and configure the second server farm to
consume published services from the provider farm.
Objectives
Create service application instances.
Establish trust relationships between SharePoint server farms.
Publish and consume service applications between SharePoint server farms.
Virtual Machine: 20332B-NYC-DC-03, 20332B-NYC-DB-03, 20332B-NYC-SP-03, 20332B-NYC-FARM2-03
User name: administrator@contoso.com
Password: Pa$$w0rd
Exercise 1: Creating a Service Application Instance
Scenario
In this exercise, you will create a Managed Metadata Service application instance that you can use to test
service application federation. First, you will create a domain account to run the service application, and
you will register the domain account as a managed account in SharePoint. You will then start the
Managed Metadata Web Service and provision a Managed Metadata Service application instance. Finally,
you will create and populate two term sets to use for testing.
1. Create a service account to run the Managed Metadata Service
2. Register the service account as a SharePoint managed account
3. Start the Managed Metadata Web Service service
4. Create a new Managed Metadata Service application instance
5. Create sample term sets
Task 1: Create a service account to run the Managed Metadata Service
screen, and then wait a further five minutes before starting the next step.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Start the 20332B-NYC-FARM2-03 virtual machine. Wait for the virtual machine to display the logon
Pa$$w0rd.
Property Setting
Full name SharePoint General MMS
UPN logon ContosoMMS@contoso.com
SAM Account Name logon CONTOSO\ContosoMMS
Password Pa$$w0rd
Task 2: Register the service account as a SharePoint managed account
Pa$$w0rd.
Open the Central Administration web site.
Navigate to the Managed Accounts page.
Register the CONTOSO\ContosoMMS account you created in the previous tasks as a managed
account.
Task 3: Start the Managed Metadata Web Service service
Navigate to the Services on Server page on the Central Administration website.
Start the Managed Metadata Web Service service.
Task 4: Create a new Managed Metadata Service application instance
Navigate to the Manage Service Applications page on the Central Administration website.
Create a new Managed Metadata Service with the following settings:
Property Setting
Name Contoso Managed Metadata Service
Database name ContosoMMS
Application pool name ContosoMMSAppPool
Application pool security account CONTOSO\ContosoMMS
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
Content type hub http://sharepoint.contoso.com
Task 5: Create sample term sets
In the Contoso Managed Metadata Service term store, create a new term set group named
Organization.
In the Organization group, create a new term set named Department.
Add the following terms to the Department term set:
o Marketing
o Finance
o IT
o Sales
In the Organization group, create a new term set named Supplier.
Add the following terms to the Supplier term set:
o Litware, Inc.
o Proseware, Inc.
o Northwind Traders
o Trey Research
o Wide World Importers

Results: After completing this exercise, you should have provisioned a Managed Metadata Service
application instance.
Exercise 2: Establishing Trust Relationships between SharePoint Farms
Scenario
In this exercise, you will establish a trust relationship between two SharePoint farms. To do this, you will
perform the following high-level tasks:
On the farm that will provide services (the provider farm), you will export the SharePoint certification
authority root certificate. You will copy the certificate to the farm that will consume services (the
consumer farm) and use it to register a trusted root authority.
On the consumer farm, you will export the SharePoint certification authority root certificate and the
SharePoint STS token-signing certificate. You will copy these certificates to the provider farm and use
them to register a trusted root authority and a trusted token issuer.
1. Export certificates from the consumer farm
2. Export the root certificate from the provider farm
3. Create a trusted root authority on the consumer farm
4. Create a trusted root authority on the provider farm
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
5. Create a trusted token issuer on the provider farm
Task 1: Export certificates from the consumer farm
Log on to the 20332B-NYC-FARM2-03 virtual machine as CONTOSO\Administrator with password
Pa$$w0rd.
In PowerShell, get a reference to the root certificate of the SharePoint certificate authority.
Export the root certificate to the E drive with the filename ConsumerFarmRoot.cer.
Get a reference to the token-signing certificate for the local login provider of the SharePoint STS.
Export the token-signing certificate to the E drive with the filename ConsumerFarmSTS.cer.
Copy the certificates to the network file share at \\NYC-SP1\Share.
Task 2: Export the root certificate from the provider farm
Switch to the 20332B-NYC-SP-03 virtual machine.
In PowerShell, get a reference to the root certificate of the SharePoint certificate authority.
Export the root certificate to the E drive with the filename ProviderFarmRoot.cer.
Copy the certificate to the network file share at \\NYC-FARM2\Share.
Task 3: Create a trusted root authority on the consumer farm
Switch to the 20332B-NYC-FARM2-03 virtual machine. If you are not already logged on, log on as
CONTOSO\Administrator with password Pa$$w0rd.
In PowerShell, get a reference to the provider farm root certificate as a PfxCertificate object.
Use the provider farm root certificate to create a new SharePoint trusted root authority named
Contoso Provider Farm.
Task 4: Create a trusted root authority on the provider farm
Switch to the 20332B-NYC-SP-03 virtual machine. If you are not already logged on, log on as
In PowerShell, get a reference to the consumer farm root certificate as a PfxCertificate object.
Use the provider farm root certificate to create a new SharePoint trusted root authority named
Contoso Consumer Farm.
Task 5: Create a trusted token issuer on the provider farm
In PowerShell, get a reference to the consumer farm token-signing certificate as a PfxCertificate
object.
Use the consumer farm token-signing certificate to register a new SharePoint trusted service token
issuer named Contoso Consumer Farm.
Open the Central Administration website and locate the list of trust relationships.
Verify that Contoso Consumer Farm is listed with a type of Trusted Service Provider.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

Note: The term Trusted Service Provider on this page can be confusing, as in this case you want to
use Contoso Consumer Farm to consume services. In this context, the term Trusted Service Provider
means that the local farm includes a trust relationship that enables it to provide services to Contoso
Consumer Farm.

Results: After completing this exercise, you should have configured a trust relationship between two
SharePoint farms.
Exercise 3: Publishing and Consuming Service Applications
Scenario
In this exercise, you will publish the Managed Metadata Service application instance on the provider farm
and then connect to the service application instance from the consumer farm. First, you will grant the
consumer farm permissions to both the Application Discovery and Load Balancing Service Application
instance and the Managed Metadata Service application instance. You will then publish the Managed
Metadata Service application instance on the provider farm, connect to it from the consumer farm, and
verify that you can browse term sets.
1. Get the ID of the consumer farm
2. Grant the consumer farm permissions on the provider farm Application Discovery and Load Balancing
Service Application
3. Grant the consumer farm permissions on the provider farm Managed Metadata Service application
4. Publish the Managed Metadata Service application on the provider farm
5. Connect to the Managed Metadata Service application from the consumer farm
Task 1: Get the ID of the consumer farm
In PowerShell, get the ID of the consumer farm. You can either write down the farm ID, or copy it to a
text file and add it to the Share folder on the provider farm.
Task 2: Grant the consumer farm permissions on the provider farm Application
Discovery and Load Balancing Service Application
In PowerShell, use the consumer farm ID that you recorded in the previous task to create a new
SharePoint claims principal.
Grant the new claims principal Full Control permissions on the local Application Discovery and Load
Balancing service application instance.
Task 3: Grant the consumer farm permissions on the provider farm Managed
Metadata Service application
On the Central Administration website, grant the consumer farm the Full Access to Term Store
permission set on the Contoso Managed Metadata Service application.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 4: Publish the Managed Metadata Service application on the provider farm
Publish the Contoso Managed Metadata Service application.
Configure the published service application to use a connection type of http.
Record the published URL for the service application. You can either write it down, or add it to a text
file and copy it to the Share folder on the consumer farm.
Task 5: Connect to the Managed Metadata Service application from the consumer
farm
On the Central Administration website, connect to the Contoso Managed Metadata Service
application using the URL you recorded in the previous task.
Verify that you can browse the Organization and Department term sets from the remote farm.

Results: After completing this exercise, you should have published a service application on one
SharePoint farm and connected to the service application from another SharePoint farm.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you learned how to:
Explain the service application architecture.
Describe the fundamental options of service application design.
Describe how to configure a federated service application deployment.
Review Question(s)
Test Your Knowledge
Question
In all service application communication, which of the following communications
formats is used?

HTTP
HTTPS
OData
TCP
WCF
Test Your Knowledge
Question
Which of the following statements is only true of a federated or cross-farm service
application environment?

You can deploy multiple instances of a service application.
You can deploy all service applications in a service application-driven design.
You can isolate service applications from one another.
You can deploy a single instance of the Managed Metadata Service to be
consumed from multiple farms in an enterprise.
You can delegate service administration.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Test Your Knowledge
Question
Which of the following steps in the configuration of a federated service application
environment can only be completed by using Windows PowerShell?

Generating certificates.
Managing trust relationships.
Publishing a federated service.
Setting federated service application permissions.
Creating a proxy for a federated service application.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4-1
Module 4
Configuring and Managing Business Connectivity Services
Contents:
Module Overview 4-1
Lesson 1: Planning and Configuring Business Connectivity Services 4-2
Lesson 2: Configuring the Secure Store Service 4-7
Lab A: Configuring BCS and the Secure Store Service 4-12
Lesson 3: Managing Business Data Connectivity Models 4-16
Lab B: Managing Business Data Connectivity Models 4-19

Module Overview
Most organizations store information in a variety of disparate systems. In many cases, these organizations
want to be able to view, interact with, and update information from these disparate systems from a single
interface. This reduces the need for information workers to constantly switch between systems and creates
opportunities for power users or analysts to aggregate data from multiple sources.
In Microsoft SharePoint Server 2013, Business Connectivity Services (BCS) is a collection of technologies
that enable you to query, view, and update data from external systems. In this module, you will learn how
to plan and configure various components of BCS.
Objectives
Plan and configure the Business Data Connectivity Service application.
Plan and configure the Secure Store Service application.
Manage Business Data Connectivity models.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4-2 Configuring and Managing Business Connectivity Services
Lesson 1
Planning and Configuring Business Connectivity Services
In SharePoint 2013, BCS relies on interactions between a variety of components. To manage a BCS
deployment effectively, you must have a solid understanding of the roles performed by each of these
components and how they work together to provide access to external data. In this lesson, you will learn
about the core components of BCS and how to provision and manage a Business Data Connectivity (BDC)
service application instance.
Lesson Objectives
Describe the purpose and capabilities of BCS.
Describe the high-level architecture of BCS.
Explain the key components of a Business Data Connectivity (BDC) model.
Provision a BDC service application instance.
Manage permissions for a BDC service application instance.
What is Business Connectivity Services?
In SharePoint 2013, Business Connectivity Services
(BCS) is a set of components that enable you to
work with data that resides outside of SharePoint.
The BCS enables you to support the full range of
create, retrieve, update, delete, and query
(CRUDQ) data operations on external data sources
from SharePoint and from Office client
applications.
When you connect to external data sources
through the BCS, you can work with the data in a
variety of ways. For example:
You can use the built-in Business Data Web
Parts to display, query, and interact with the data.
You can create external lists, which enables you to interact with external data in a similar way to
standard SharePoint list data.
You can use the Search service to index and query the data.
You can use the data to augment user profiles.
You can use the data to drive SharePoint workflows.
You can interact with the data from Office client applications.
You can create custom-coded SharePoint solutions that use the BCS object model to support more
esoteric scenarios.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Business Data Connectivity models
The BCS uses Business Data Connectivity (BDC) models to represent data entities within an external
system. The BDC model is a self-contained, XML-based file that provides SharePoint with all the
information it needs to connect to and interact with external data. This information includes:
Details of how to connect to and authenticate to the external system.
Definitions for each data entity of interest on the external system.
Definitions for each CRUDQ data access method you want to perform against data entities.
A BDC model is portable. You can export it and import it. You can create BDC models for the following
types of data sources:
SQL Server databases
Windows Communication Foundation (WCF) web services
Open Data Protocol (OData) web services
Other types of data source, by using a .NET connectivity assembly.
You can create BDC models interactively in SharePoint Designer for SQL Server databases and WCF web
services. For OData web services and other types of data source, you can use Visual Studio templates to
create and develop the model.
Note: OData is a standards-based web protocol for querying and updating data.
BCS service applications
SharePoint includes two service applications that underpin the functionality of BCS:
The BDC service application. This service application stores and manages BDC models.
The Secure Store service application. This service application enables you to map SharePoint users to
external system credentials. For example, you could map a group of SharePoint users to a set of SQL
Server credentials that provide access to a specific database.
Reference Links: For more information about BCS capabilities in SharePoint 2013, see
Overview of Business Connectivity Services in SharePoint 2013 at
Discussion: Using Business Connectivity Services
In this discussion, you will compare experiences of
BCS in SharePoint 2010, and consider how the new
BCS features in SharePoint 2013 might meet the
requirements of your organization.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Business Connectivity Services Architecture
SharePoint 2013 BCS includes various server-side
components. Understanding the role of these
components, and how they work together, can be
beneficial when you need to configure and
manage BCS.
BCS components
SharePoint 2013 BCS includes the following key
components:
The BDC service application. This is responsible
for storing and managing BDC models. Within
the BDC service application, BDC models are
stored in the BDC Metadata Store, which is a SQL Server database. When an administrator imports or
modifies a BDC model, the BDC service application adds the model definition to the BDC Metadata
Store. When a user submits a request that involves external data, the BDC Runtime retrieves the
model definition from the BDC Metadata Store and uses the information in the model to connect to
the external data source.
The Secure Store service application. This is responsible for storing any credentials required to access
an external system. Within the Secure Store service application, credentials are mapped to SharePoint
users in secure store target applications. Each target application is associated with an external system
in the BDC service application. You can map external credentials to individual SharePoint users or
groups of SharePoint users. The Secure Store Service and secure store target applications are covered
in the next lesson.
The BDC Runtime. This service runs on each Web Front End (WFE) server in the SharePoint server
farm, and is responsible for handling and executing requests for external data. When a request is
received, the BDC Runtime retrieves details of the required BDC model from the BDC Metadata Store.
If the model specifies that Secure Store Service credentials are required, the BDC Runtime retrieves
these credentials from the Secure Store Service application. The BDC Runtime then uses a connector
to execute the requested operation on the external data source, and returns the results to the client.
The Connector Framework. This consists of a set of connectors that enable the BDC Runtime to
communicate with each of the supported external systems. The Connector Framework includes
connectors for SQL Server databases, WCF web services, OData web services, and .NET connectivity
assemblies.
The request process
A typical BCS request follows this high-level process:
1. A client, such as a Business Data Web Part or an external list, requests a CRUDQ operation on an
external data source. The WFE server routes the request to the BDC Runtime.
2. The BDC Runtime retrieves the BDC model metadata required to fulfill the request from the BDC
Metadata Store. This information will include connection information, authentication information, and
method definitions for any supported data operations.
3. If the BDC model specifies that Secure Store Service credentials are required, the BDC Runtime will
contact the Secure Store Service to request the external credentials that are mapped to the current
SharePoint user for the specified target application.
4. The BDC Runtime uses the BDC model metadata, the Secure Store Service credentials if required, and
an appropriate connector to perform the data operation on the external data source.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
5. The BDC Runtime returns the result of the data operation to the client that submitted the request.
Understanding Business Data Connectivity Models
A BDC model contains all the information required
to connect to an external source and perform data
operations. A BDC model consists of the following
components:
External system. Each BDC model can contain
one or more external systems, which are
represented by LobSystem elements in the
BDC model file. An external system is a
general representation of an external data
source, such as a SQL Server database with
specific tables.
System instance. Each external system can
include one or more system instances, which are represented by LobSystemInstance elements in the
BDC model file. As the name suggests, a system instance represents a specific instance of an external
systemfor example, an instance of your SQL Server database hosted on a specific server with
specific security settings. The system instance includes connection details, such as the web service
endpoint or the SQL Server connection string, and details of how to authenticate to the external
system instance.
Entities. Each external system can include one or more entities, which are represented as external
content types (ECTs).
External content types
An ECT is essentially a model of a data entity. ECTs are central to how end users work with external data in
SharePoint and in Office client applications. For example, when you create an external list, you associate it
with an ECT. When you create Business Data Web Parts, you select an ECT. Each ECT defines the following
components:
One or more identifiers that uniquely identify instances of the external data entity.
One or more methods that define CRUDQ operations on the external data entity, together with any
sorting and filtering criteria.
Provisioning a Business Data Connectivity Service Application
Provisioning a BDC service application instance is
much the same as provisioning any other service
application instance. At a high level, you must
complete the following tasks:
1. Create a new domain account if you want to
run the BDC service application in a new
application pool.
2. Register the domain account with SharePoint
as a managed account.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
3. Start the Business Data Connectivity service on the SharePoint server on which you want to run the
BDC service application.
4. Provision a BDC service application using the Central Administration website or Windows PowerShell.
5. Create a service application proxy, if it was not created automatically.
If you want to use Windows PowerShell, you can use the New-
SPBusinessDataCatalogServiceApplication cmdlet to create the service application and the New-
SPBusinessDataCatalogServiceApplicationProxy cmdlet to create the service application proxy.
Note: The BDC service application supports SQL Server database mirroring. When you
provision the service application, you can specify a failover database server to use if the primary
database server becomes unavailable.
Managing Business Data Connectivity Permissions
The BDC service application allows you to set
unique permissions on the following objects in the
BDC hierarchy:
The BDC Metadata Store
Individual BDC models
Individual external systems
Individual ECTs
The following permissions are available for each
object:
Edit. This permission allows a user to edit
items at the specified scope and to create new child items. For example, if you grant the Edit
permission at the BDC Metadata Store scope, the user can create new BDC models and define new
external systems. If you grant the Edit permission at the external system scope, the user can create
new ECTs.
Execute. This permission allows a user to execute the data operations defined in an ECT. Users require
this permission to use any components that rely on external data, such as external lists and Business
Data Web Parts. This permission only has an effect at the ECT scope.
Selectable in Clients. This permission enables users to create external lists and to view and select
external content types in the external item picker. This permission only has an effect at the ECT scope.
Set Permissions. This permission allows a user to grant permissions to other users, within the scope on
which the permission is granted. If this permission is granted at the BDC Metadata Store level, the
user can grant permissions on any object within the BDC hierarchy.
When you assign permissions at the BDC Metadata Store scope, you can choose whether to propagate
permissions to all BDC models, external systems, and external content types within the BDC Metadata
Store. You should use this option with caution because it will overwrite unique existing permissions on
items within the metadata store.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Configuring the Secure Store Service
In many organizations, users maintain several sets of credentials for access to different systems and
applications. If you want to provide a consolidated view of data across these systems and applications,
you need to provide a single sign-on experience. In SharePoint 2013, the Secure Store Service maintains a
secure credential store that maps SharePoint user identities to external system credentials. This allows the
BDC Runtime to authenticate to various external systems on behalf of a user without prompting the user
for credentials.
In this lesson, you will learn how to configure the Secure Store Service. You will also learn how to use the
Secure Store Service in conjunction with the BDC service application to provide a single sign-on
experience to BCS users.
Lesson Objectives
Explain the purpose of the Secure Store Service.
Describe the components of a secure store target application.
Configure the Secure Store Service application.
Create secure store target applications.
Understanding the Secure Store Service
Many organizations rely on proprietary or third-
party legacy systems for a variety of functions.
These systems may include customer relationship
management (CRM) systems, inventory
management systems, enterprise resource
planning (ERP) tools, and other line-of-business
(LOB) applications. In many cases, these systems
will maintain their own credential stores. This
presents a challenge when you want to surface
external data in SharePoint. How can you present
an integrated view of data from disparate data
sources, if the user has to enter a separate set of
credentials for each data source?
The answer is provided by the Secure Store Service application. The Secure Store Service enables you to
map SharePoint user identities to external credentials. The external credentials and the credential
mappings are stored in an encrypted database. You can map individual SharePoint users or groups of
SharePoint users to an individual set of external credentials.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Understanding Secure Store Target Applications
If you want to use the Secure Store Service to
manage credentials, you must first create a target
application. A target application is the unit of
management in the Secure Store Service, and
defines one or more credential mappings for a
specific external system or application.
Each target application is uniquely identified by a
target application ID. There is a one-to-one
mapping between BDC models and secure store
target applications. If you want to use secure store
credentials with a BDC model, the BDC model
settings must specify a target application ID. In
this way, the BDC Runtime knows which set of external credentials it should use to access the external
system associated with the BDC model.
What does a target application contain?
A target application includes the following information:
Target application ID. This uniquely identifies the target application.
Display name and contact email. The name and contact email address for the target application.
Target application type. The options include Individual, in which each SharePoint user is mapped to
an individual set of external credentials, and Group, in which multiple SharePoint users are mapped
to a single set of external credentials.
Field names and types. These represent the credentials that are required by the external system. You
can specify a variety of credential types, including generic user names and passwords, Windows user
names and passwords, PINs, keys, and certificates.
Target application administrators. This is the list of users who can edit the target application settings.
In addition to these settings, each target application includes credential mappings. In the case of target
applications based on the Group type, the target application contains a single credential mapping that
maps a group of SharePoint users to a single set of external credentials. In the case of target applications
based on the Individual type, the target application contains credential mappings for each SharePoint
user that accesses the external system.
Configuring the Secure Store Service
Provisioning a Secure Store Service application
instance is much the same as provisioning any
other service application instance. At a high level,
you must complete the following tasks:
1. If you want to run the Secure Store Service
application in a new application pool, create a
new domain account.
2. Register the domain account with SharePoint
as a managed account.
3. Start the Secure Store Service on the
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
SharePoint server on which you want to run the BDC Service application.
4. Provision a Secure Store Service application using the Central Administration website or Windows
PowerShell.
5. Create a service application proxy, if it was not created automatically.
If you want to use Windows PowerShell, you can use the New-SPSecureStoreServiceApplication cmdlet
to create the service application and the New-SPSecureStoreServiceApplicationProxy cmdlet to create
the service application proxy.
Generating a Secure Store master key
The Secure Store Service uses an encrypted database to store external credentials. Before you can use the
Secure Store Service, you must generate a master key to encrypt the database. You can do this from the
Secure Store Service management page in Central Administration, or by using the Update-
SPSecureStoreMasterKey cmdlet in Windows PowerShell.
To generate a secure store master key, you must provide a pass phrase. You will need this pass phrase if
you want to add more servers running the Secure Store Service or if you want to restore a backed-up
Secure Store database. SharePoint will not store the pass phrase, and you will be unable to recover the
data in the Secure Store database if you forget the pass phrase. As such, you should record the pass
phrase and keep it somewhere safe for future reference.
Creating Secure Store Target Applications
You can create a secure store target application
from the Central Administration website or by
using Windows PowerShell.
To create a new target application from the
Central Administration website, browse to the
management page for the Secure Store Service
application. On the ribbon, in the Manage Target
Applications group, click New. You will be
presented with a series of pages that collect the
required information. Alternatively, you can use
the New-SPSecureStoreTargetApplication
cmdlet in Windows PowerShell.
Specifying the target application type
When you create a target application, you can choose from six different target application types.
Essentially, there are three variations of the Individual type and three variation of the Group type. The
following table provides more information on the available target application types.
Target Application Type Description
Individual Maps individual SharePoint users to individual sets of external
credentials.
Individual Ticket Maps individual SharePoint users to individual sets of external
credentials. Also issues a ticket that allows other accounts to
retrieve the set of external credentials for a limited period of
time.
Individual Restricted Maps individual SharePoint users to individual sets of external
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Target Application Type Description
credentials. Access to the external credentials is limited to
fully-trusted code.
Group Maps a group of SharePoint users to a single set of external
credentials.
Group Ticket Maps a group of SharePoint users to a single set of external
credentials. Also issues a ticket that allows other accounts to
retrieve the set of external credentials for a limited period of
time.
Group Restricted Maps a group of SharePoint users to a single set of external
credentials. Access to the external credentials is limited to
fully-trusted code.
When you create a target application of type Individual Ticket or Group Ticket, you can specify the
duration for which issued tickets are valid. By default, this is set to two minutes. You will also be prompted
to specify a list of Ticket Redeemers. This is the list of user accounts or groups who are authorized to
redeem the tickets issued on behalf of SharePoint users.
Providing credential fields
By default, a target application includes two credential fields: a field of type Windows User Name, and a
field of type Windows Password. However, you can change the type of these fields and add more fields
as required. The Secure Store Service supports a range of field types that are designed to meet the
authentication requirements of almost any external system. The following table provides more
information on the available field types.
Field Type Description
Generic Any text-based information that does not fit any other
category.
User Name A text-based user name.
Password A text-based password.
PIN A personal identification number.
Key The key associated with a cryptographic algorithm or cipher.
Windows User Name A Windows user account.
Windows Password The password for a Windows user account.
Certificate A security certificate.
Certificate Password The password for a certificate.
For each field you add, you can specify whether you want the value to be masked (like a typical password
text box) or unmasked.
Note: You can add fields of type Generic to capture any additional information required
by the external system. For example, if the external system requires you to specify a database
name, you could add a Generic field named Database to capture the information.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Setting credentials
If you create a target application based on the Group type, you specify the target application members.
This is the list of users or groups that are mapped to the single set of external credentials managed by the
target application. You can then specify the external credentials from the management page for the
Secure Store Service application, by selecting the target application and then clicking the Set button in
the Credentials group on the ribbon.
The process for target applications based on the Individual type is slightly different. Although you can
specify credentials for individual users from Central Administration, this is likely to be impractical if you
have a large number of users. Instead, the user is redirected to a target application page that captures the
users credentials when he or she first accesses the external system. When you create a target application,
you can choose to use the default target application page provided by SharePoint or specify the URL for
an alternative target application page.
Reference Links: For more information about configuring target applications and the
Secure Store Service, see Configure the Secure Store Service in SharePoint 2013 at

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Configuring BCS and the Secure Store Service
Scenario
Managers at Contoso are becoming frustrated by having to log on to multiple different systems to gain
an overview of different aspects of the business, such as the sales pipeline and levels of inventory. The
management committee has asked you to investigate ways of providing a consolidated view of
information from other line-of-business solutions on the SharePoint 2013 intranet. Your first task is to
configure Business Connectivity Services and related service applications. You will also configure the
Secure Store Service, so that SharePoint can map end-user credentials to the credentials required by
various line-of-business systems. Later in this module, you will import and configure a BDC model as a
proof-of-concept to demonstrate functionality.
Objectives
Configure the Business Data Connectivity service application.
Configure the Secure Store Service application.
Passw0rd: Pa$$w0rd
Exercise 1: Configuring the Business Data Connectivity Service Application
Scenario
In this exercise, you will configure a Business Data Connectivity Service application instance. First, you will
create a new domain account to run the service, and you will register the new account with SharePoint as
a managed account. Next, you will start the Business Data Connectivity Service on the local SharePoint
server and then provision a new Business Data Connectivity Service application instance. Finally, you will
configure the Business Data Connectivity Service application instance by setting metadata store
permissions and creating a site to host profile pages for external content types.
1. Create a service account to run the BDC service application
2. Register the service account as a managed account
3. Start the Business Data Connectivity Service
4. Create a new Business Data Connectivity service application instance
5. Set metadata store permissions
Task 1: Create a service account to run the BDC service application
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Pa$$w0rd.
Full name SharePoint BDC
UPN logon SP_BDC@contoso.com
SAM Account Name logon CONTOSO\SP_BDC
Password Pa$$w0rd
Task 2: Register the service account as a managed account
Pa$$w0rd.
Register the CONTOSO\SP_BDC account that you created in the previous task as a managed
account.
Note: You can use either the Central Administration website or Windows PowerShell to
register a managed account.
Task 3: Start the Business Data Connectivity Service
On the SharePoint server, start the Business Data Connectivity Service.
Note: You can start services by using Windows PowerShell or from the Central
Administration website.
Task 4: Create a new Business Data Connectivity service application instance
Create a new Business Data Connectivity Service application with the following properties:
Property Value
Service application name Contoso BDC
Database name Contoso_BDC_DB
Application pool name SharePointContosoBDC
Security account for application pool CONTOSO\SP_BDC
Task 5: Set metadata store permissions
Open the metadata store permissions for the Contoso BDC service application.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Grant CONTOSO\Administrator all permissions.
Propagate the permissions to all BDC Models, External Systems, and External Content Types in the
BDC Metadata Store.
Note: To view external lists and interact with ECTs in Office client applications, users require
the Execute and Selectable in Clients permissions. However, you also want the administrator to
be able to edit BDC model components and assign permissions to other users.

Results: After completing this exercise, you should have created and configured a Business Data
Connectivity Service application instance.
Exercise 2: Configuring the Secure Store Service
Scenario
In this exercise, you will configure a Secure Store Service application instance. First, you will create a new
domain account to run the service, and you will register the new account with SharePoint as a managed
account. Next, you will start the Secure Store Service on the local SharePoint server and then provision a
new Secure Store Service application instance. Finally, you will configure the Secure Store Service
application instance by creating a new master key to encrypt the database.
1. Create a service account to run the Secure Store Service application
3. Start the Secure Store Service
4. Create a new Secure Store Service application instance
5. Create a secure store master key
Task 1: Create a service account to run the Secure Store Service application
Switch to the 20332B-NYC-DC-04 machine. If you are not already logged on, log on as
administrator@contoso.com with the password Pa$$w0rd.
Full name SharePoint SSS
UPN logon SP_SSS@contoso.com
SAM Account Name logon CONTOSO\SP_SSS
Password Pa$$w0rd
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Switch to the 20332B-NYC-SP-04 machine. If you are not already logged on, log on as
Register the CONTOSO\SP_SSS account you created in the previous task as a managed account.
Task 3: Start the Secure Store Service
On the SharePoint server, start the Secure Store Service.
Note: You can start services from Windows PowerShell or from the Central Administration
website.
Task 4: Create a new Secure Store Service application instance
Create a new Secure Store Service application with the following properties:
Property Value
Service application name Contoso Secure Store
Database name Contoso_SSS_DB
Application pool name SharePointContosoSSS
Security account for application pool CONTOSO\SP_SSS
Task 5: Create a secure store master key
Open the management settings for the Contoso Secure Store service application.
Generate a new secure store master key with the pass phrase Pa$$w0rd.

Results: After completing this exercise, you should have created and configured a Secure Store Service

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Managing Business Data Connectivity Models
BDC models are central to how BCS components interact with external data. As an architect or an
administrator, you are unlikely to get involved in creating BDC models, which is typically the job of a
developer. However, you will need to know how to import and configure BDC models.
In this lesson, you will learn about how to configure authentication for BDC models. You will also learn
about the difference between farm-scoped and SharePoint App-scoped BDC models. Finally, you will
learn how to import and export BDC models.
Lesson Objectives
Explain the different approaches to BDC model authentication.
Explain the differences between farm-scoped and app-scoped BDC models.
Import and export BDC models from a SharePoint farm.
BDC Model Authentication
The BDC Service application supports two high-
level authentication models:
Trusted subsystem. In this model, the middle
tier (typically the SharePoint WFE server)
authenticates to the external system using a
fixed identity. This could be the identity of the
application pool that runs the BDC service
application, or it could be credentials supplied
by a group-based secure store target
application.
Impersonation and delegation. In this model,
the middle tier impersonates the client and
uses the client identity to authenticate to the external system. Credentials supplied by an individual-
based secure store target application also fall under this model.
The trusted subsystem approach has various advantages. For example, it is less complex, it can reduce
licensing costs on the external system, and it supports connection pooling. However, the impersonation
and delegation approach may be required if the external system requires per-user authorization or
auditing.
Authentication for a specific BDC model is configured in the external system section of the model. You
can edit the authentication settings for a BDC model from the Central Administration website or in
SharePoint Designer. When you browse to the settings for a specific external system, you can choose from
four authentication modes:
User's Identity. In this mode, the BDC Runtime impersonates the Windows identity of the user to
authenticate to the external system. To use this mode, you must have Kerberos delegation configured
in your environment due to the double-hop limitation of NTLM. Within the BDC model, this mode is
referred to as PassThrough.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
BDC Identity. In this mode, the BDC Runtime authenticates to the external system using the identity of
the IIS application pool that runs the BDC service application. Within the BDC model, this mode is
referred to as RevertToSelf.
Impersonate Custom Identity. In this mode, the BDC Runtime uses non-Windows-based secure store
credentials to authenticate to the external system. To use this mode, you must have configured the
Secure Store Service and you must specify a secure store target application ID. Within the BDC model,
this mode is referred to as Credentials.
Impersonate Windows Identity. In this mode, the BDC Runtime uses Windows-based secure store
credentials to authenticate to the external system. To use this mode, you must have configured the
Secure Store Service and you must specify a secure store target application ID. Within the BDC model,
this mode is referred to as WindowsCredentials.
Farm-Scoped and App-Scoped BDC Models
In SharePoint 2010, BDC models were always
scoped to the entire farm. When you created or
imported a BDC model in SharePoint 2010, users
with sufficient permissions could make use of the
ECTs defined within the BDC model anywhere
within the SharePoint farm.
In SharePoint 2013, developers can also include
BDC models in SharePoint apps. In this case, the
BDC model is scoped to the app. You cannot use
ECTs defined within an app anywhere outside of
the app. This enables app developers to include
BDC models as part of the proprietary logic of
their SharePoint apps.
However, this approach presents a challenge when it comes to defining connection details. Suppose an
app developer distributes an app that includes ECTs designed to work with a specific type of CRM system.
The data schema may be the same for every customer that uses that CRM system, but the specific
connection detailsfor example, the service endpoint URLwill vary from customer to customer. As such,
although it makes sense for the app developer to include ECTs in their SharePoint app, it does not make
sense for the developer to include external system details.
For this reason, SharePoint 2013 enables you to define app-scoped ECTs separately from the connection
settings. App developers can include BDC models that contain app-scoped ECTs but no connection
information. Meanwhile, SharePoint administrators can define connection settings objects in the Secure
Store Service application, and then grant SharePoint apps permission to use these connection settings
objects. This approach also enables multiple app-scoped BDC models to share the same connection
settings objects.
Note: For an example of how to work with app-scoped BDC models, see SharePoint 2013:
Create external lists based on app-scoped external content type at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Importing and Exporting BDC Models
You can import and export BDC models as
portable, self-contained XML files. BDC model files
are indicated by the .bdcm file extension.
Importing BDC models
You can import BDC models from the Central
Administration website or by using Windows
PowerShell. You can use the following high-level
process to import a BDC model:
1. On the Central Administration website,
browse to the management page for the BDC
2. On the ribbon, in the BDC Models group, click Import. You will be prompted to locate the .bdcm file
you want to import.
3. Specify whether you want to import the entire model or just specific resources from within the model,
and then click Import.
The import wizard will validate the BDC model and report any errors it encountered. After the model is
imported successfully, you can change model settings as required and set permissions on the model.
Note: For detailed information about the permissions you can assign to BDC models, see
Managing Business Data Connectivity Permissions in the first lesson.
Exporting BDC models
Perform the following steps to export BDC models from your SharePoint farm by using SharePoint
Designer 2013:
1. Open SharePoint Designer 2013, connect to a SharePoint site, and browse to External Content
Types.
2. Select an ECT within the model that you want to export.
3. On the ribbon, click Export BDC Model.
4. SharePoint Designer will package the BDC model and prompt you to save it as a .bdcm file.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Managing Business Data Connectivity Models
Scenario
Now that you have configured the BDC service application and the Secure Store Service application, you
must verify that everything behaves as expected. To help you achieve this, the IT team has provided a
simple BDC model, ContosoDW, which you can use as a proof-of-concept. The ContosoDW BDC model
contains a single ECT named Employees that retrieves data from an Employees table in the
ContosoRetailDW database. To use this model, you will configure a secure store target application that
specifies the Windows credentials to use to connect to the database. Next, you will import the BDC model
and associate the secure store target application with the model. Finally, you will use the Employees ECT
to create an external list and verify that everything works as expected.
Objectives
Create a new secure store target application.
Import and configure a BDC model.
Create an external list.
Passw0rd: Pa$$w0rd
Exercise 1: Configuring a Secure Store Service target application
Scenario
In this exercise, you will configure a new secure store target application. The target application will use the
group model, so that all users are mapped to a single set of credentials that the BDC model can use to
access a database.
1. Create a new target application
2. Set the credentials for the target application
Task 1: Create a new target application
Pa$$w0rd.
On the Central Administration website, browse to the management page for the Contoso Secure
Store service application.
Create a new secure store target application with the following properties:
Property Value
Target Application ID ContosoDW_TA
Display Name ContosoDW database target application
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Value
Contact E-mail administrator@contoso.com
Target Application Type Group
Field Names and Field Types Leave defaults of Windows User Name and
Windows Password unchanged
Target Application Administrators CONTOSO\Administrator
Members CONTOSO\Sales
CONTOSO\Administrator
Task 2: Set the credentials for the target application
Set the following credentials for the ContosoDW_TA target application:
a. User name: CONTOSO\CDW_User
b. Password: Pa$$w0rd

Results: After completing this exercise, you should have created and configured a secure store target
application.
Exercise 2: Importing and Configuring BDC Models
Scenario
In this exercise, you will import and configure a BDC model. First, you will import the model and verify
that the import process completes without errors. Next, you will associate the external system in the BDC
model with the secure store target application that you created in the previous task. Finally, you will use
the ECT in the model to create an external list and verify that you can interact with the model data as
expected.
1. Import the ContosoDW BDC model
2. Associate the external system in the BDC model with a target application
3. Create an external list to review the model data
Task 1: Import the ContosoDW BDC model
On the Central Administration website, browse to the management page for the Contoso BDC
Import the ContosoDW.bdcm BDC model file from the E:\Mod04 folder.
Verify that the import completes successfully.
Task 2: Associate the external system in the BDC model with a target application
Examine the settings for the ContosoDW external system.
Change the secure store target application ID for the external system to ContosoDW_TA.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Create an external list to review the model data
In Internet Explorer, browse to sharepoint.contoso.com. If you are prompted for credentials, log on
as CONTOSO\Administrator with password Pa$$w0rd.
Add a new external list named Employees to the site.
Associate the Employees list with the Employees external content type.
Browse to the Employees list. When the page loads, verify that the page displays a list of employees
from the database.
Switch to the details view for one of the employees in the list.
Verify that the page displays the details of the selected employee.

Results: After completing this exercise, you should have imported and configured a BDC model.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you learned how to plan, configure, and manage the different components of BCS in
SharePoint 2013.
Review Question(s)
Test Your Knowledge
Question
Which component of BCS is responsible for receiving and responding to requests from
clients?

The connector framework
The BDC Metadata Store
The BDC Runtime
The BDC service application
The Secure Store Service application
Test Your Knowledge
Question
After you provision a Secure Store Service application, what is the first thing you must
do before you can start to use the service?

Create an external system.
Create a target application.
Generate a secure store master key.
Import a BDC model.
Set metadata store permissions.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Statement Answer
True or False: If you want the BDC Runtime to access an
external system by impersonating the current SharePoint user,
you must first configure the Secure Store Service application.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
5-1
Module 5
Connecting People
Contents:
Module Overview 5-1
Lesson 1: Managing User Profiles 5-2
Lesson 2: Enabling Social Interaction 5-16
Lab A: Configuring Profile Synchronization and My Sites 5-28
Lesson 3: Building Communities 5-35
Lab B: Configuring Community Sites 5-43

Module Overview
Talking about connecting people in Microsoft SharePoint Server 2013 really means talking about taking
people out of their isolated workspaces and giving them the ability and tools to collaborate with other
people in the organization such as their work colleagues, peers, and executives. It is about finding people
with expertise, and identifying shared interests and about creating networks of people that share common
goals.
In this module, you will learn about the concepts and ways of connecting people in SharePoint 2013. You
will examine user profiles and user profile synchronization, social interaction features and capabilities, and
communities and community sites in SharePoint 2013.
Objectives
Understand and manage user profiles and user profile synchronization in SharePoint 2013.
Enable social interaction in SharePoint 2013.
Understand and build communities and community sites in SharePoint 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
5-2 Connecting People
Lesson 1
Managing User Profiles
User profiles underpin much of the social computing and people search functionality in SharePoint 2013.
To support these features, you need to understand the core concepts of user profiles. You also need to be
able to configure and manage how your user profiles integrate with user directories and other data stores
within your organization.
Lesson Objectives
After completing this lesson you will be able to:
Understand the concept of user profiles in SharePoint 2013.
Understand profile properties and profile synchronization methods in SharePoint 2013.
Configure one-way user profile import in SharePoint 2013.
Configure two-way user profile synchronization in SharePoint 2013.
Manage user profile properties and mappings in SharePoint 2013.
Manage user profile policies in SharePoint 2013.
Manage audiences in SharePoint 2013.
What Are User Profiles?
Each user in SharePoint 2013 has a user profile
that contains data about the user, which is stored
in user profile properties. User profiles can contain
a variety of organizational and personal properties
such as phone numbers, direct manager, job role,
position in the organizational hierarchy, group
memberships, products and projects currently
being worked on, skills, and interests, along with
social media items such as tags. A user profile
must also contain a property that uniquely
identifies the user within the directory, such as a
user principal name (UPN) or an email address.
User profiles in a SharePoint 2013 farm are stored in a profiles database that is associated with a User
Profile service application.
Additional Reading: For more information, see Server-to-server authentication and user
profiles in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302080
How user profiles are used
The information contained in user profiles provides the foundation for enterprise-wide social networking
features in SharePoint 2013. These features include My Sites, People Search, organizational charts, skills
and expertise searches, and community sites for social features such as tagging, following, sharing, and
audiences. In this way, user profiles provide a rich and personalized experience for your organizations
users.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The following image illustrates how the properties of a user profile can be derived from various sources,
including directory services, diverse business systems, and user input.
Image not available in the media folder
In the diagram, a directory service provides organizational information about each user, such as user
name, email address, department and work phone number. Business systems would provide information
about customer accounts, products and sales leads related to users; and the users themselves would
provide additional personal information such as their skill sets and interests.
User profiles are created in either of two instanceswhen a user without an existing user profile first
accesses their My Site, or when users are imported from other systems within your organization by using
profile synchronization.
Understanding Profile Properties and Synchronization
A user profile is made up of a set of user
properties that contain information about a user.
Each user property has a value that can be entered
manually by a user or can be imported from an
LDAP-compliant directory service, such as Active
Directory, Novell eDirectory, Oracle Sun ONE
Directory Server, and IBM Tivoli Directory Server.
You can configure some of the properties of a user
profile to be exported to a directory service in a
two-way synchronization process.
User profile properties can also be provided by a
supported Business Data Connectivity (BDC)
system, such as SQL Server. BDC systems are typically used to augment user profiles and are not often
used as a primary source in the way that directory services are. BDC systems provide an import method
for user profile properties; however, they cannot be used to export data back from a user profile.
SharePoint 2013 user profiles provide their own default user profile properties, and you can also define
your own if required. These default user profile properties are used by the social networking and
personalization features of SharePoint 2013. A subset of these default user profile properties are
automatically mapped to their equivalent directory service attributes after you run profile synchronization.
You can also configure your own mappings to map a profile property to a particular source property.

Additional Reading: For more information, see Default user profile properties in SharePoint
Server 2010 at http://go.microsoft.com/fwlink/?Linkid=302081
Profile synchronization types in SharePoint 2013
User Profile Service administrators in SharePoint 2013 can use profile synchronization to manage and
synchronize the user and group profile data stored in the SharePoint 2013 profile store with profile data
stored in directory services and BDC systems.
There are two distinct forms of profile import and synchronization available in SharePoint 2013:
One-way profile import. This is a new implementation of a simple import process that was first
provided in SharePoint Server 2007. It uses the SharePoint Active Directory Import option to import
user profile data from Active Directory Domain Services (AD DS).
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: One-way profile import only works with Active Directory and does not support other
directory services.
Two-way profile synchronization. This uses the SharePoint Server 2013 profile synchronization method
that was first introduced in SharePoint Server 2010. It uses Microsoft Forefront Identity Manager (FIM)
to synchronize profile data with external directory services and BDC systems.
Note: Important: The term two-way synchronization can be a little misleading. Although
the mapping direction of profile properties can be either an import or export mapping, you
cannot set both types of mapping on an individual property; for each property, it is one or the
other, not both.
Configuring One-Way Profile Import
The one-way profile import method is considered
to be a simpler approach to importing profile data
in SharePoint 2013 compared to the two-way
profile import. It uses the SharePoint Active
Directory Import option to import user profile
properties from Active Directory into SharePoint
2013 user profiles.
Advantages of this import method
One-way profile import is the ideal solution for
environments where a simple import method is
needed with no requirements to write back to the
source. This method is an import-only method and
only supports Active Directory. It is very simple to set up and has minimal requirements to make it work.
Other key benefits of this method include:
The User Profile Synchronization Service does not need to be deployed because one-way profile
import runs under the User Profile Service instance.
It is faster than the FIM-based two-way profile synchronization method.
It runs incremental imports automatically every five minutes.
It is much easier to configure than two-way profile import.
Configuring SharePoint Active Directory Import
There are only a few steps to configuring the Active Directory Import method in SharePoint 2013.
You must begin by selecting the SharePoint Active Directory Import option in Central Administration.
Note that this is a unidirectional process and that any changes you make to user profiles in SharePoint
2013 are not synchronized back to Active Directory.
Perform the following steps to select the SharePoint Active Directory Import option:
1. Log on with a user account that is a member of the Farm Administrators group.
2. In Central Administration, under System Settings, open the Manage services on server page, and
ensure that the User Profile Service is started.
3. In Central Administration, open the Manage service applications page.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4. Click on the name of the User Profile service application.
5. On the Manage Profile Service page, click Configure Synchronization Settings.
6. On the Configure Synchronization Settings page, in the Synchronization Options section, select the
Use SharePoint Active Directory Import option.
Next, you need to create a connection to the directory service. In this step, you create a connection the
relevant directory service. When you do this, you specify the items that you want to synchronize, and the
credentials used to make the connection to the directory service.
Perform the following steps to create a connection to the directory service:
1. On the Manage Profile Service page, in the Synchronization section, click Configure
Synchronization Connections.
2. On the Synchronizations Connections page, click Create New Connection.
3. On the Add new synchronization connection page:
a. Provide a name for the synchronization connection.
b. Select Active Directory Import as the synchronization type.
c. Specify the settings contained in the Connection Settings section. These include the name of
the domain, the authentication method to use, the synchronization account credentials, port
settings and any require import filters.
d. In the Containers section, click Populate Containers.
e. Select the containers from the directory service that you want to synchronize.
Next, you need to map user profile properties. In this step, you define the mappings for SharePoint user
profiles to user attributes retrieved from the directory service.
Perform the following steps to map user profile properties to user attributes:
1. On the Manage Profile Service page, in the People section, click Manage User Properties.
2. On the Manage User Properties page, click the name of the property that you want to map to a
directory service attribute, and then click Edit.
3. To remove an existing mapping:
a. In the Property Mapping for Synchronization section, select the mapping that you want to
remove, and then click Remove.
4. To add a new mapping:
a. In the Add New Mapping section, in the Source Data Connection list, select the data
connection that represents the directory service to which you want to map the user profile
property.
b. Type the name of the directory service attribute to which you want to map the property.
c. Add the import mapping.
d. Repeat this process to map additional user profile properties.
Note: You cannot edit an existing mapping; to change mapping settings for a property,
remove the existing mapping first and then create a new mapping.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Finally, you can either wait for the five minutes to elapse when the scheduled synchronization job will run,
or you can start the profile synchronization process manually. For this step, you need to have configured
at least one synchronization connection to a directory service. If you have configured multiple
connections, you can either choose to synchronize after you create each connection, or you can
synchronize them all at one time after you create all of your connections. If you synchronize each
connection independently, it does take longer to do, but it is makes troubleshooting any issues that occur
much easier.
Perform the following steps to start the profile synchronization process manually:
1. On the Manage Profile Service page, in the Synchronization section, click Start Profile
Synchronization.
2. On the Start Profile Synchronization page, do one of the following:
o Select Start Incremental Synchronization to synchronize only the changes to information that
have occurred since you last synchronized; this include new connections that you added or
existing ones that you modified.
o Select Start Full Synchronization if this is the first time that you are synchronizing, or you want
to reset the user profile data store.
Additional Reading: For more information about using the SharePoint Active Directory
Import method, see Configure profile synchronization by using SharePoint Active Directory Import
in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302082
Configuring Two-Way Profile Synchronization
The two-way profile synchronization method is
considered to be a more complex approach to
synchronizing user profile information with
SharePoint 2013. It relies on Forefront Identity
Manager (FIM) to import and export user profile
property mappings between SharePoint 2013 and
directory services and to import user profile
property data from BDC systems.
Advantages of this synchronization
method
This solution is required in SharePoint 2013
environments where changes made to user
profiles must be written back to the directory services source. For example, if a user updates his or her
email address or phone number in SharePoint 2013, those changes can be synched back to the directory
service. This is possible because you can configure each property mapping to have a direction, which must
be either import or export; it cannot be both.
Two-way profile synchronization offers other additional benefits over a one-way import. For example:
It can be used with directory services other than Active Directory.
It enables you to define exclusion filters for synchronization connections.
It enables you to import user profile data from BDC systems.
The two-way profile synchronization approach will be familiar to SharePoint 2010 administrators, because
the process remains largely unchanged.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Configuring SharePoint profile synchronization
There are several key steps that need to be performed when using the SharePoint profile synchronization
method in SharePoint 2013, and these can be broken into five main phases. You may need to perform all
of the steps in each of these phases, or you may only need to perform some of them, depending on your
particular environment and situation.
Phase one Configure farm prerequisites
This phase involves the following high-level steps:
1. Create a web application to host My Sites.
2. Create a managed path for My Site.
3. Create a My Site Host site collection.
4. Create a User Profile service application.
5. Enable NetBIOS domain names for user profile synchronization by using Windows PowerShell.
Phase two Start the User Profile Service and the User Profile Synchronization Service
1. Start the User Profile Service.
2. Make the SharePoint farm account a member of the local Administrators group on the server that
runs the User Profile Synchronization service.
3. Start the User Profile Synchronization Service.
4. Remove the SharePoint farm account from the local Administrators group.
5. If the User Profile Synchronization Service is running on the same server as the Central Administration
website, reset IIS.
Phase three Configure a connection to the directory service and import data
1. Create a synchronization connection to a directory service.
2. Define exclusion filters for a synchronization connection.
3. Map user profile properties.
4. Start profile synchronization.
Additional Reading: To watch a video demonstration of the tasks in this phase, see
Configure a profile synchronization connection in SharePoint Server 2010 (video) at
Phase four (optional) Configure connections to line-of-business systems and import
data
If you want to augment your user profiles with data from line-of-business (LOB) systems, you can use
SharePoint Business Connectivity Services (BCS) to do this. This phase involves the following high-level
steps:
1. Grant the User Profile service application permission to use the external content type in the BCS.
2. Configure a Business Data Connectivity synchronization connection.
3. Add or edit user profile properties.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4. Import data by selecting full synchronization.
Additional Reading: To watch a video demonstration of the tasks in this phase, see
Configure a synchronization connection to a SQL Server database in SharePoint Server 2010
(video) at http://go.microsoft.com/fwlink/?Linkid=302085
Phase five (optional) Configure connections to export data to a directory service
If you want to export profile data from SharePoint to your directory service, you must perform these high-
level steps:
1. Map user profile properties by using the export mapping direction.
2. Start profile synchronization by selecting incremental synchronization.
The next time that profile synchronization occurs, the user profile properties will either be exported or
imported, depending on the property mapping directions you specified in the synchronization
connection. When configuring the export of user profile data to a directory service, you cannot create
new synchronization connections explicitly for the purpose of exporting the data; you must use the
existing synchronization connections and modify the mapping direction for the relevant properties to
export.
Note: You cannot export user profile data back to business systems using BDC connections.
Additional Reading: For detailed information about all the phases and all the procedural
steps to configure and synchronize user profiles using the SharePoint Profile Synchronization
method, see Synchronize user and group profiles in SharePoint Server 2013 at
Discussion: Selecting the Appropriate Import Method
Under what circumstances would you use full
profile synchronization rather than a simple one-
way import?
Which approach do you think would be most
appropriate for your organization?
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Managing Profile Properties and Mappings
As discussed earlier in the lesson, specific user
profile properties are already mapped to a
corresponding directory service attribute by
default in SharePoint 2013 after you run profile
synchronization, but you can also add your own
mappings to map user profile properties to
specific attributes on a directory service when
required. You can create property mappings for
both Active Directory Domain Services (AD DS)
and non-AD DS directory services, such as Novell
eDirectory.
Additional Reading: For more information
about the default user profile property mappings in SharePoint 2013 for AD DS and other
directory services, see Default user profile property mappings in SharePoint Server 2013 at
Default user profile property mappings
SharePoint 2013 provides many default user profile properties that you can map to directory service
attributes. The following table lists just a few examples of these.
User profile property Display name User profile service data type
SID SID binary
FirstName First name string (single-value)
Manager Manager Person
CellPhone Mobile phone string (single-value)
PersonalSpace Personal site URL
SPS-Interests Interests string (multi-value)
SPS-HireDate Hire date date
Note that some of these properties are single-value and others are multi-value, and that there are a
variety of data types, such as binary, date, Person, string, and URL.
Additional Reading: For a full list of the default user profile properties provided in
SharePoint 2013, see Default user profile property mappings in SharePoint Server 2013 at
Data type compatibility
When you map user profile properties from SharePoint 2013 with attributes in external directory services,
the data types of the property and the attribute that you are mapping must be compatible. The following
table lists some of the data type compatibilities for AD DS.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
User profile service data type AD DS data type
big integer Large Integer, Integer
binary Octet String, SID
date UTC Coded Time
E-mail Unicode String, IA5-String, Case Insensitive String
Person Distinguished Name
When you create an external content type in SharePoint 2013, you need to specify the .NET data type for
each column. When you map user profile properties from SharePoint 2013 with an external content type
by using a BDC connection, their data types need to be compatible. The following table lists some of the
data type compatibilities for .NET.
User profile service data type .NET data type
Boolean System.Boolean
string (multi-value) System.String
date, date time System.DateTime
big integer System.Int64
big integer System.UInt64
Additional Reading: For a full list of the data type compatibilities for AD DS and .NET, see
User profile property data types in SharePoint Server 2013 at
http://go.microsoft.com/fwlink/?Linked=299770
Using managed metadata term sets with user profile properties
In SharePoint 2013, you can use the managed metadata feature to create and define centrally managed
terms that can be used as attributes for SharePoint 2013 items. A set of these managed terms is referred
to as a term set, and you can associate a term set with an editable user profile property, so that you can
control which values are associated with a specific user profile property. This will make it simpler for users
to enter the appropriate values for a property. For example, if you define the job titles for your users in
the organization in a term set and then associate that term set with the job title profile property, you can
encourage regular use of those defined titles in your users user profiles.
Additional Reading: For more information about planning managed metadata, see Plan
managed metadata in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302091
Mapping user profile properties (one-way profile import method)
The steps to map user profile properties when using the SharePoint Active Directory Import method are:
On the Manage Profile Service page, in the People section, click Manage User Properties.
On the Manage User Properties page, click the name of the property that you want to map to a
directory service attribute, and then click Edit.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To remove an existing mapping:
o In the Property Mapping for Synchronization section, select the mapping that you want to
remove, and then click Remove.
To add a new mapping:
o In the Add New Mapping section, in the Source Data Connection list, select the data
connection that represents the directory service to which you want to map the user profile
property.
o Type the name of the directory service attribute to which you want to map the property.
o Add the import mapping.
o Repeat this process to map additional user profile properties.
Mapping user profile properties (two-way profile synchronization method)
The steps to map user profile properties when using the SharePoint Profile Synchronization method are
the same as the preceding steps, except that you have the additional ability to export your mapping
instead. When you set the mapping direction setting to Export, it means that the propertys value in
SharePoint 2013 will be exported to set the value of the specific attribute on the external directory service.
You will also need to edit your user profile property mappings when you have retrieved information from
business systems that need manually mapping to your user profile properties.
Managing User Profile Policies
In SharePoint 2013, you can set policies on the
properties of user profiles to help control how that
piece of data is used.
To manage a policy for a user profile property:
In Central Administration, under Application
Management, click Manage service
applications.
Click the name of the User Profile service
application.
Under People, click Manage Policies.
On the Manage Policies page, scroll down the list to find the section named User Profile Properties.
Click the name of the property, and then click Edit Policy.
In the Policy Settings section, specify the required setting for the property.
You can specify the following policy settings options.
Policy Setting This defines whether the policy is available to be used or not and has the following
setting options:
o Required This specifies that the user profile property must contain data. For example, the
Account name property is set to Required by default.
o Optional This specifies that the user profile property may contain data but is not required to, so
each user can provide a value for this property of leave it empty. For example, the Job Title
property is set to Optional by default.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Disabled This specifies that this user profile property is unavailable to be used in user profiles.
For example, the MemberOf property is set to Disabled by default.
Default Privacy Setting This specifies the visibility of the user profile property and has the following
setting options:
o Everyone This specifies that everyone who has at least view permissions can see this property
information. The majority of user prolife properties are set to Everyone by default.
Note: Only user profile properties that have a privacy setting that is set to Everyone will be
used by SharePoint 2013 search features.
o Only Me This specifies that only the user themselves can see this property information. For
example, the MemberOf, Last Colleague Added, and Outlook Web Access URL properties are
set to Only Me by default.
User can override This specifies whether users are allowed to change the property's Default Privacy
Setting or not. If this option is not selected, only administrators of the User Profile Service can change
the setting. The majority of user profile properties are not overridable, but several are. For example,
the Job Title, Department, Hire date, and Home phone properties can be overridden by a user.
Replicable This specifies whether a user profile property's value will be replicated to user
information lists in other sites when its value changes. In order to replicate a user property, its
Default Privacy Setting must be set to Everyone and the User can override policy setting must not
be selected.
Additional Reading: For more information about managing user profile policies, see Plan
user profiles in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302091
Managing Audiences
Audiences in SharePoint 2013 provide a way to
target your content at the right people based on
the groups in which they are a member, and by
rules that you can configure. Audiences are
groupings of users that you compile to make
content targeting easier.
After you create an audience, you define the
audience rules and then compile the audience.
Compiling an audience identifies the membership
in an audience by searching the most recently
imported information from profile
synchronization. You must compile each audience
before you can begin targeting content to that audience. Audiences are defined and contained in the
User Profile service application, and you create audiences, create audience rules, and compile audiences
by using Central Administration.
Note: You do not use audiences to grant user rights and permissions; you use audiences to
define and manage how content is targeted and distributed, not to implement security.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Creating audiences
You use audiences in SharePoint 2013 when you want to target your website content, such as lists,
libraries, and Web Parts, at particular users in your organization. This can be useful when you need to
provide content that is only relevant to a specific subset of users. For example, you might add a Web Part
that provides sales lead information which you can target only at members of the Sales department.
Perform the following steps to create an audience in Central Administration:
1. In Central Administration, under Application Management, click Manage service applications.
2. On the Service Applications page, click the User Profile service application that you want to configure.
3. On the Manage Profile Service page, under People, click Manage Audiences.
4. Click New Audience.
5. Create a new audience by specifying the following:
o Name.
o Description.
o User name of the user who will own and manage this audience. This owner should be someone
who understands the reasons behind this audience being created, and they should ideally be
someone who will take responsibility for management of this audience. Typically, but not
necessarily, the owner will be the person who created the audience.
o Specify one of the following:
Whether to include users who satisfy all of the rules in order for them to be included in the
audience.
Whether to include users who satisfy any of the rules in order for them to be included in the
audience.
After you finish creating an audience, the Add Audience Rule page automatically opens.
Creating audience rules
Audience rules in SharePoint 2013 are based on the following:
Windows security group and distribution list membership
An organization's reporting hierarchy
User profile properties
When you define audience rules, you must specify the following elements and associated values:
Operand. This identifies the user or property that you want to include in the query for the rule. For
example, in a rule based on Windows security group membership, the value for this would be User.
Operator. This determines whether users who are compared to the value are included in or excluded
from the rule. For the example, the value for this would be Member Of.
Value. This is the point of comparison that is used by the query. For the example, this would be the
value of the group name of which the user is a member, such as Sales.
Note: Audiences must always contain at least one audience rule.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To create an audience rule in Central Administration, perform one of the following steps on the Add
Audience Rule page:
To add a rule based on security group membership:
o For the Operand, select User.
o For the Operator, select Member Of to target content by group or distribution list.
o For the Value, type the name of a Windows security group or distribution list that the user must
belong to in order to be included in this audience.
Note: If you were creating an audience based on who the users manager is, you would
select Reports Under for the Operator, and then enter the managers account name for the
Value.
To add a rule based on a user profile property (for example, all users who are in the Sales
department):
o For the Operand, select Property, and then select the Department property from the list.
o For the Operator, select an operator for the property from the list. The list of operators varies,
depending on the property selected. For this example, the operators for the Department
property are Contains and Not Contains.
o For the Value, type a value to use when evaluating the property against this rule; in this example,
it would be Sales.
Compiling audiences
When you compile an audience, SharePoint 2013 identifies members of the audience by searching
through the most recent user profile data. You can compile an audience manually whenever you want to,
or you can schedule automatic compilations to happen.
Perform the following steps to compile an audience:
2. On the Service Applications page, click the name of the User Profile service application that you want
to configure.
3. On the Manage Profile Service page, under People, click Compile Audiences.
4. Note that the Last Compilation Time will update on the right side of the page once compilation is
complete.
Note: You can also compile an audience by clicking on the Compile audience link on the
View Audience Properties page.
Perform the following steps to schedule audience compilations:
2. On the Service Applications page, click the name of the User Profile service application that you want
to configure.
3. On the Manage Profile Service page, under People, click Schedule Audience Compilation.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4. On the Specify Compilation Schedule page:
o Select the Enable scheduling check box.
o Specify a start time.
o Specify a daily, weekly, or monthly schedule.
Note: It is best practice to compile audiences on a regular basis because user profile
properties and the group memberships from directory services can change frequently.
Discussion: Using Audiences
In what scenarios would you use audiences within
your organization?

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Enabling Social Interaction
In this lesson, you will learn about enabling social interaction and social features in SharePoint 2013.
Specifically, you will learn about the social experience provided by SharePoint 2013, and how to plan and
configure My Sites, configure microblogging and activity feeds, and manage permissions and privacy
settings for SharePoint 2013 social features.
Lesson Objectives
Understand the social experience in SharePoint 2013.
Plan for My Sites in SharePoint 2013.
Configure My Sites in SharePoint 2013.
Configure microblogging and activity feeds in SharePoint 2013.
Manage permissions for social features in SharePoint 2013.
Manage privacy settings for social features in SharePoint 2013.
The Social Experience in SharePoint 2013
There are several features in SharePoint 2013
designed to make enterprise social computing and
collaboration easier, and offer an improved
administration and user experience. New
capabilities also enable enterprise users to share
and collaborate with other people within the
organization. These social features enable your
users to obtain and share the knowledge and skills
required to perform their job. Information sharing
inspires collaboration and targets content to the
most appropriate audience. Based on this
knowledge, you can more easily adjust content to
individual users needs, but you can also set policies on the information to protect peoples privacy when
required.
My Sites
A My Site is a users personal site in an organization. It can be used as a central repository for a users own
documents, as well as documents they share with other people; it is also the default saving location for
the users Office documents. Users also use it to display information about themselves and their areas of
expertise, to tag content, and to communicate with other people using the Note Board. Users within the
organization can use people search to find and connect with other users based on the expertise
information contained in their My Sites.
In SharePoint 2013, the My Site user interface has been totally redesigned to provide a more intuitive user
experience, predominantly by virtue of the simplified and unified navigation. My Sites in SharePoint 2013
has also been enhanced to contain the new microblogging and newsfeeds features. Activities within each
My Site are persisted indefinitely and the newsfeed page provides an aggregated view of recent activities
held in the cache, whereas the users profile page shows all activities held in the users microblogging list.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Microblogging and newsfeeds
The Newsfeed page in a users My Site offers a combined view of activities from people and content that
is being followed by a user. In SharePoint 2013, the feed feature has been enhanced with the addition of
new microblogging features that enable users to participate in conversations by posting comments and
replies, post pictures and links, and use the following social computing capabilities:
Tags. They define keywords that users can search for and follow if they want. Tags take the form
#topic and are also known as hashtags. When a user posts or replies to a threads they can tag words
with hashtags. The managed metadata service provides a list of metadata terms that match the users
input. When a post contains tags, the newsfeed shows any activity related to that tag, and any users
who decide to follow that particular tag will see the activity in their own newsfeed.
Mentions. They tag other users by name in posts and replies. Mentions take the form @name. When
users post or respond to a thread, they can tag other users with a mention. The User Profile Service
provides a list of names that match the users input. When a user is mentioned, they receive an
activity in their own My Site newsfeed that tells them they have been mentioned by someone else.
Likes. They show that a user agrees with a posting or a reply. When users post or respond to a thread,
other users can like the original posting or one or more of the responses. In My Sites, likes are
viewable in the newsfeed. Users can use the Likes view in the newsfeed to view previously liked items.
Ratings. They allow users to rate the content and can be enabled on lists and libraries in SharePoint
2013. You can configure ratings to be rated by either Likes or Star Ratings, both of which will appear
in the newsfeed on users My Sites. This feature encourages participation and feedback from users of
the site and the average ratings for a list of library may help a user decide whether to view the
content or not.
Following
This feature enables a user to show interest in particular items in SharePoint 2013, such as documents,
tags, sites, or even other people. When a user follows one of these items, new activities about that item
are displayed in the user's newsfeed on their My Site.
Community Sites
SharePoint 2013 provides the Discussion list feature in its sites to simplify discussions among users of the
site. SharePoint 2013 has also expanded on the discussion list concept by introducing two new site
templates, Community Site and Community Portal.
Community Sites provide a user forum to classify and encourage discussions within an extensive group of
people in an enterprise. Community Sites provide a location for communication and the sharing of
information about expertise and interests between users who want to share their expertise and also utilize
the expertise of other people in the organization and to find people with common interests.
Community Portals
The Community Portal is useful when you have multiple Community Sites that you want to make available
to your enterprise users. The Community Portal is a search-driven page for site collections and sites in
your SharePoint 2013 farm that use the Community Site template. Users can visit the Community Portal to
determine the most popular communities and to search for other communities that might interest them
and that they might join.
Additional Reading: For more information about new social computing features in
SharePoint 2013, see What's new in social computing in SharePoint Server 2013 at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Discussion: Using Social Computing Features
Which social computing features do you think
would be useful within your own organization?
Which features do you plan to implement?
What do you think the barriers to successful user
adoption might be?

Planning for My Sites
In SharePoint Server 2013, a My Site is a users
personal site in an organization. To the user, a My
Site might appear to be a single isolated site, but
in fact the My Sites architecture in SharePoint
2013 consists of much more than that.
Note: In Office 365, My Sites are now known
as SkyDrive Pro.
Planning the My Sites architecture
The My Sites architecture consists of the following
components:
Web application. This is required to host the My Sites infrastructure. Every user's My Site utilizes two
site collections: the farms My Site host site collection and the user's individual site collection. You
could use an existing web application to host these site collections, but it is better practice to create
and use a dedicated web application for My Sites to enhance performance and ease its management.
When you create the My Site host site collection and users create their own site collections for My Site,
the data is stored in one or more content databases associated with the web application that you create
and configure to host My Sites. If you want to add further storage databases for My Sites, you can simply
add content databases to the My Sites web application in SharePoint 2013.
My Site host site collection. This is a special site collection that displays the profile and newsfeed pages
for all users' My Sites. When creating this site collection, you must use the My Site Host Site template,
which is accessed from the Enterprise tab of the Create Site Collection page. This template can only
be used once per User Profile service application, which is one of the service application
dependencies for My Sites.
A My Site host site collection must exist at the root of the host web application for My Sites to work. It is
recommended to use a dedicated web application for My Sites. You should use the default root path for
the My Site host collection unless there is a very good reason not to do so.
Individual site collections. Each user's My Site is actually a site collection. This site collection is created
the first time they access their My Site. For this automatic site collection provisioning to work, there
are several underlying configuration elements that need to be in place:
o The web application that you use to host My Sites has a wildcard inclusion managed path, such
as /mysites or /personal. This is the path under which the individual site collections will be
created when users access their My Sites for the first time.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o The Setup My Sites settings for the User Profile service application need to be configured to use
the URL of the My Site host site collection and the wildcard inclusion managed path for
individual site collections.
o The host web application needs to have Self-Service Site Creation enabled, which allows the
individual site collections to be created under the specified wildcard inclusion managed path.
o You need to have granted all users the Create Personal Site permission to create a My Site. This
permission is enabled for all authenticated users by default.
Note: Except for the individual site collections, all other parts of the My Site infrastructure
are configured once and shared among all the users who are part of a My Sites deployment.
Planning for My Sites-related service applications and features
There are several My Sites-related service applications you need to plan for when planning your My Sites
infrastructure:
Related SharePoint service applications and databases. There are several service applications and
related databases that My Sites rely on in SharePoint 2013:
o The User Profile service application is required for My Sites and it has three databases: the profile
database, a social database, and a synchronization database.
o The Managed Metadata Service application enables web applications to store and access
keywords from a managed metadata term store. This capability is required by My Sites if you
want to enable users to specify keywords as their areas of expertise in the Ask Me About section,
use hashtags in newsfeed posts, and use the Tags and Notes feature of a My Site. Although it is
not required, the Managed Metadata Service application is highly recommended for use in My
Sites environments to get the full benefit of the feature; you must configure it as the default
keyword term store for the host web application.
o The Search service application, although not required for My Sites, is highly recommended to
enable your users to use people search from their My Site to find people in the organization
based on their names or on their areas of expertise. In addition, if you add a hashtag to a
microblog post, when users click the tag, they are directed to the search results for that tag.
There are several My Sites-related tasks you may need to perform when planning your My Sites
infrastructure:
Planning for profile synchronization. This is an optional but highly recommended step to synchronize
profiles between SharePoint Server 2013 and directory services or business applications.
Additional Reading: For more information about planning for profile synchronization, see
Plan profile synchronization for SharePoint Server 2013 at
Planning policies and privacy. SharePoint Server 2013 provides a set of configurable default policies to
make the appropriate information available to meet the needs of an organization and its users;
however, you can also create and deploy your own custom policies to meet more specific needs.
When planning for My Sites, you need to define which information is needed for what purpose, and
who needs access to it. Some information in an organization might be unsuitable for sharing across
an organization, and some information should be shared only among specifics sets of users.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Additional Reading: For more information about policy planning, see Plan user profiles in
SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302091
Planning users and user permissions. In order for your users to be able to create My Sites, to manage
their own profiles, to follow people and content, and to use tags and notes, you need to determine
and configure user permissions for the User Profile service application used by My Sites.
Planning for jobs and schedules. There are several timer jobs related to My Sites functionality.
Planning for geographically distributed deployments. You must consider the location of the users in
the organization and the number of farms or User Profile service applications that will host My Sites. If
you have more than one farm or User Profile service application, you will likely have to configure
trusted My Site host locations.
Planning for the multilingual user interface. When enabled, users can use the multilingual user
interface feature for their My Sites. This feature is used to display the site in another preferred
language instead of the default, primary language selected when the site was created.
Planning for storage requirements. My Sites users can edit their profiles, generate newsfeed activities,
and upload and download documents, so you need to plan for the storage and capacity needs of
your My Sites infrastructure. Consider the content databases for My Sites and the databases for the
related My Sites service applications.
Planning for file types. You can configure the file types that users are allowed to upload to or
download from the My Sites web application. This helps prevent large files such as video or other
media being uploaded and downloaded, and it protects against users downloading potentially
dangerous executable files to their client computer.
Additional Reading: For more information about these planning tasks, see Plan for My
Sites in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302094
Configuring My Sites
There are several tasks you need to perform to
configure a successful My Sites environment for
SharePoint 2013.
Configure prerequisites for your My
Sites web application
There are several prerequisites you need to
complete before creating your My Sites web
application:
Ensure you have a User Profile service
application instance to use for My Sites.
Configure and run profile synchronization if
you want to synchronize user profile data stored in the SharePoint Server 2013 profile database with
profile information stored in a directory service or business system.
Configure a DNS record for the My Sites web application.
Create a service account for the My Sites web applications application pool.
Register the service account as a managed account.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Create and configure a web application for My Sites
Although you do not need to create a separate dedicated web application for My Sites, it is best practice
to do so for optimal performance and for increased security.
Perform the following steps to create a web application for My Sites:
1. In Application Management, click Manage web applications.
2. On the Web Applications Management page, create a new web application by specifying the
following:
a. A name for the web application (for example MySites 80).
b. A port number to use (for example 80).
c. A host header (for example mysites.litwareinc.com).
d. A name for the My Sites application pool (for example SharePointMySites 80).
e. The name of the application pool account (for example LITWARE\MySitesAppPool).
Create a My Site host site collection
This site collection must be created in the web application that will be hosting My Sites. This site collection
would typically be created at the root path of the web application; however, as long as a site collection
exists at the web application root, you can create it as an explicit inclusion managed path deeper in the
URL structure.
Perform the following steps to create a My Site host site collection:
1. In Application Management, click Create site collections.
2. On the Create Site Collection page:
a. Verify that your My Sites web application is selected.
b. Enter a title for your My Site host site collection, for example; MySite Host.
c. Select the My Site Host template from the Enterprise tab.
d. Provide the name and password for the primary site collection administrator.
Add a wildcard inclusion managed path to the web application
Perform the following steps to add a managed path for the web application:
1. Select the web application in the web applications list, and on the ribbon, click Managed Paths.
2. Add a new managed path, for example; personal.
3. Ensure that you use the Wildcard inclusion type for the managed path.
Connect the web application to service applications
The My Sites web application needs to be connected to service applications in SharePoint 2013, such as
the User Profile service application, and optionally, the Managed Metadata Service application and Search
Perform the following steps to connect the My Sites web application to service applications:
2. On the Web Applications Management page, select the My Sites web application.
3. On the Web Applications tab, in the Manage group, click Service Connections.
4. In the Configure Service Application Associations dialog box, do one of the following:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
a. Select default if the default group contains the service applications that you want to connect to
the web application.
b. Select [custom] and then manually select any service applications to which you want to connect
the web application, such as the User Profile service application, the Managed Metadata Service
application, or the Search service application.
Note: If you have any other SharePoint sites from which you want users to be able to
access their My Site and About Me links from the upper-right corner menu, connect the web
applications of those sites to the User Profile service application by selecting the [custom]
option.
Enable Self-Service Site Creation for the web application
This enables the automatic creation of individual site collections for users when they first access their My
Site. Perform the following steps to enable self-service site creation for the My Sites web application:
2. On the Web Applications Management page, select the My Sites web application.
3. On the Web Applications tab, in the Security group, click Self-Service Site Creation.
4. In the Self-Service Site Creation Management dialog box:
a. Enable users to create their own site collections.
b. Specify whether to allow users to create new Team Sites using the Start a Site link.
c. Specify whether to display the Site Classification setting.
d. Specify whether users need to supply the name of another site administrator.
Note: If you allow your users to create their own Team Sites from their My Sites, you also
need to add a permission policy level to grant those users the Create Subsites permission.
Configure My Site settings for the User Profile service application
You can use these settings to update the My Sites settings in the User Profile service application. The
majority of these settings are configured during initial deployment, and they typically require little
maintenance after that. One setting you will want to specify is the My Site Host location.
Perform the following steps to configure My Site settings for the User Profile service application:
1. In Application Management, click Manage service applications.
2. Click the User Profile service application for the My Sites web application.
3. On the Manage Profile Service page, in the My Site Settings section, click Setup My Sites.
4. In the My Site Host section, in the My Site Host location box, type the URL of the My Site host site
collection, for example; http://mysites.litwareinc.com.
Enable the Activity Feed Job for the User Profile service application for My Sites
When you enable this timer job, users will receive system generated posts in their newsfeeds for events,
such as following a tag, tagging items, changes to job titles, postings on a Note Board, and updates to the
Ask Me About section.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Additional Reading: For more information about enabling the Activity Feed Job for the
User Profile service application, see To enable the User Profile Service Application - Activity Feed
Job in Configure My Sites in SharePoint Server 2013 at
http://go.microsoft.com/fwlink/?LinkId=302095
Understanding Microblogging and Activity Feeds
Microblogging features in SharePoint 2013 enable
users to swiftly and easily post information to a
central location while enabling other users to
create a public dialog by replying with comments
and "likes". In this way, significant information and
news can be rapidly shared between colleagues
while providing context to the conversations.
When users post the information on a microblog,
they can include text, URLs, pictures, and videos.
After it is posted, it is instantly viewable in the
newsfeed on users My Sites, so other users can see
the post and respond to it.
Using microblogging and activity feeds offers various advantages to users and organizations:
It allows users to communicate with other users and specific groups of people over time and distance.
It allows users to keep up to date about recent organizational news and activities.
It maintains the focus on the interaction between people and teams, and not on the discussion topic.
It reduces the need to regularly visit items such as documents, discussions, and lists by collecting and
delivering the update information directly to users.
It gives users a central location to stay up-to-date with all of the content and people they work with.
It enables conversations and discussions to occur quickly.
The microblogging and activity feeds infrastructure
The infrastructure behind microblogging and activity feeds relies on the Distributed Cache Service. This
service is built on Windows Server AppFabric, which implements the AppFabric Caching service. This
caching mechanism is new in SharePoint 2013 and improves the performance of various SharePoint
features, as well as underpinning the social computing functionality. Microblogging features and activity
feeds in SharePoint 2013 rely on the Distributed Cache to store data for rapid retrieval across all entities.
Specifically, microblogs and activity feeds use the following two caches, which are both managed by the
Distributed Cache service:
Feed Cache. This cache stores recent activities and conversations for use by newsfeeds on users My
Sites.
Last Modified Time Cache. This cache uses stored time stamp information to determine the last
modified time for all items in the Feed Cache.
The activity generation process
The following steps are performed when an activity is generated in SharePoint 2013:
1. Some activities are saved to the content databases. For example, if the activity is a user or site activity,
the activity is saved to the My Sites content database; if the activity is a site feed activity, the activity is
saved in the team sites content database. Tags and document activities are not saved to content
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
databases. As such, you will need to allocate storage for My Site content databases if you want to
enable user and site activities, even if you do not want to deploy a personal storage location.
2. Activities are then written to the Distributed Cache.
3. Updates then appear in the relevant feed and users receive visual indicators to alert them of the new
updates to the feed. The updates are displayed when the user refreshes the browser.
The feed construction process
The following steps are performed when constructing feeds, such as the newsfeed, the Likes feed, the
Mentions feed, or the Everyone feed:
1. The feeds query the Last Modified Time Cache to obtain time stamp information and metadata of
recent activities related to that feed.
2. This time stamp information is then used as input to query the Feed Cache to retrieve activity data
related to that feed.
3. The requested feed is then constructed by using the activity data retrieved from the Feed Cache.
For each item, such as users, tags, sites, and documents, the Feed Cache assigns a portion of memory
known as a cache bucket to store recent activity data for that item. However, cache buckets only store
recent activities, and many cache buckets are empty because not all entities will have recent activities. By
default, recent activities are only retained for seven days.
Cache hosts and cache clusters
Servers in a farm that are running the Distributed Cache service are known as cache hosts. A cache cluster
consists of several cache hosts from a SharePoint 2013 farm. When a new application server running the
Distributed Cache service is added to the farm, the cache host joins a cache cluster. When using a cache
cluster, the Distributed Cache extends over all the application servers and creates one cache in the farm.
The total cache size is the sum of the memory allocated to the Distributed Cache service on each of the
cache hosts.
The Last Modified Time Cache only exists on one cache host in a cache cluster, and the Feed Cache stores
recent information about all items. Therefore, from a capacity planning perspective it is important that
you consider these factors when planning which servers to make into cache hosts.
Additional Reading: For more information, see Plan for feeds and the Distributed Cache
service (SharePoint Server 2013) at http://go.microsoft.com/fwlink/?Linkid=302095
Configuring Microblogging and Activity Feeds
In SharePoint 2013, you can manage various
aspects of microblogging and activity feeds from
the Central Administration website. Specifically,
you can:
Enable newsfeed email notifications. This
setting enables you to specify whether you
want your users to receive email notifications
relating to their microblogging activities, such
as replies to conversations they have been
involved in and mentions.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Manage Following. When users follow items, new activities about those items appear in the users
newsfeeds on their My Sites. This setting enables you to put limits on the number of items that a user
can follow.
Perform the following steps to enable newsfeed email notifications for My Sites:
2. In the list of service applications, click the name of the User Profile service application.
3. On the Manage Profile Service page, in the My Site Settings section, click Setup My Sites.
4. On the My Site Settings page, scroll down to the Email Notifications section.
5. Select the Enable newsfeed email notifications check box.
6. Enter a valid email address to be used as the senders email address.
Perform the following steps to configure Following settings for My Sites:
2. In the list of service applications, click the name of the User Profile service application.
3. On the Manage Profile Service page, in the My Site Settings section, click Manage Following.
4. On the Manage Following page, you can specify the following:
a. The maximum number of people that a user can follow from the users My Site. The maximum for
this setting is 1,000.
b. The maximum number of documents that a user can follow from the users My Site. The
maximum for this setting is 500.
c. The maximum number of sites that a user can follow from the users My Site. The maximum for
this setting is 500.
Note: Using lower limits for Following settings can slightly improve performance, and by
using lower limits, users will be more likely to follow higher priority documents, people, or sites.
Managing Permissions for Social Features
In SharePoint 2013, your farm administrators or
User Profile Service administrators can govern
which users can create My Sites and use personal
and social features, such as maintaining their user
profiles, following people and documents, and
using tags and notes. For example, you might
want some of your users to create their own My
Site, so you would need to grant them the
permission to perform that task.
You grant these permissions on the Manage User
Permissions page of the User Profile service
application.
Perform the following steps to enable users or groups to use personal and social features:
1. In Central Administration, in the Application Management section, click Manage service
applications.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
2. In the list of service applications, click the name of the User Profile service application you want to
configure permissions for.
3. On the Manage Profile Service page, under People, click Manage User Permissions.
4. On the permissions page, add the users or groups you want to grant permissions to.
5. In the list of permissions, select the check box for the permission you want the users or groups to be
able to use. The permissions that you can grant include:
a. Create Personal Site. This permission enables users to create a personal site to store their
documents, newsfeed, and followed content.
b. Follow People and Edit Profile. This permission enables users to follow people from their My Site
and to edit their own profile.
c. Use Tags and Notes. This permission enables users to use the Tags and Notes feature from
SharePoint Server 2010. This feature is provided in SharePoint 2013 primarily for backward
compatibility in upgrade scenarios so that users can continue to access the tags and notes they
created in the previous version. However, you can also use this permission to enable users to
leave notes on documents in SharePoint 2013.
Note: By default, all authenticated users are granted all these permissions. You can
configure your own specific permissions based on your organizational and user requirements. For
example, you could allow full-time staff to create My Sites, but not temporary staff.
Note: As a best practice, simplify administration by granting permissions to security groups
instead of specific users.
Managing Privacy Settings for Social Features
In SharePoint 2013, new privacy settings are
provided to support the social features of My Sites.
You can access these new privacy settings on the
Manage Policies page of the User Profile service
application in Central Administration. From this
page, you can control the default visibility of the
following activities:
Following a Document or Site on My Site
Tagging an Item on My Site
Workplace anniversary on My Site
Following a Tag on My Site
Updating Ask Me About on My Site
Liking or rating something
Participation in communities
Following a Person on My Site
Posting on a note board on My Site
Job Title Change on My Site
Posting a new blog post
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Birthday Celebration on My Site
Perform the following steps to manage policies for Privacy Settings:
2. Click the name of the User Profile service application.
3. Under People, click Manage Policies.
4. On the Manage Policies page, locate the section named Privacy Settings.
5. Click the name of one of the privacy settings, and then click Edit Policy.
6. In the Policy Settings section, specify the required setting for this privacy setting.
You can specify the following policy settings options:
Policy Setting. This defines whether the policy is enabled or disabled. All privacy settings are set to
Enabled by default.
Default Privacy Setting. This specifies the visibility of the privacy setting and has the following setting
options:
o Everyone. This specifies that everyone who has at least view permissions can see this information.
o Only Me. This specifies that only the user themselves can see this information. All privacy settings
are set to Only Me by default.
User can override. This specifies whether users are allowed to change the Default Privacy Setting
from their own profile or not. If this option is not selected, only administrators of the User Profile
service can change the setting. By default, all privacy settings can be overridden by a user.
By default all users My Sites are private, which means that each users list of followers and who they are
following is not shared with other users. The same applies to all the social activities such as tagging,
rating, birthdays, and blog posts.
There is another privacy setting named Make My Sites Public, located under Setup My Sites for the
User Profile service application. Service application administrators can use this setting to make all users
My Sites public by default. Therefore, if the user or an administrator configures any of the policies for
privacy settings discussed, these policy settings will be overridden if the Make My Sites Public setting has
been configured.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Configuring Profile Synchronization and My Sites
Scenario
Contoso wants to encourage social computing and collaboration to improve knowledge sharing within
the organization, but recognizes the need to protect the privacy of users. Contoso wants to make user-
adoption easier and faster by pre-populating user profiles with the user data they already possess. You
have been tasked with configuring a My Site infrastructure. To pre-populate users profiles, you will
configure two-way synchronization to import existing data.
Objectives
After completing this lab you will be able to:
Configure profile synchronization.
Configure My Sites.
Virtual Machine: 20332B-NYC-DC-05, 20332B-NYC-SP-05
Password: Pa$$w0rd
Virtual Machine 20332B-NYC-DB-05
User name: jim@contoso.com
Password: Pa$$w0rd
Exercise 1: Configuring Profile Synchronization
Scenario
In this exercise, you will configure two-way profile synchronization. You will create service accounts and
grant the permissions required to replicate the directory. You will then create an instance of the User
Profile Service Application service application and start the required services.
Finally, you will configure the connection to Active Directory and then test the profile synchronization.
1. Create a service account for the service application
2. Grant the SPFarm account the Replicating Directory Changes permission
3. Grant the SPFarm account local administrator permissions on the SharePoint server
5. Create a new User Profile Service Application application instance
6. Configure the User Profile Synchronization Service Application application instance to support NetBIOS
domain names
7. Start the User Profile Synchronization Service service
8. Configure a connection to Active Directory
9. Configure profile synchronization
10. Test profile synchronization
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 1: Create a service account for the service application
Pa$$w0rd.
Property Setting
Full name Profile Service
UPN logon ProfileService@contoso.com
SAM Account Name logon Contoso\ProfileService
Password Pa$$w0rd
Task 2: Grant the SPFarm account the Replicating Directory Changes permission
View the properties for the Contoso domain.
Grant the Replicating Directory Changes permission to the SPFarm user account.
Use ADSI Edit to grant the Replicating Directory Changes permission, on the cn=configuration
container, to the SPFarm account.
Task 3: Grant the SPFarm account local administrator permissions on the SharePoint
server
Pa$$w0rd.
Open the Local Users and Groups Microsoft Management Console (MMC) plugin.
Add the CONTOSO\SPFarm user account to the local Administrators group.
Note: When you start the User Profile Synchronization Service service, the SharePoint Timer
Service Windows service performs several steps to provision the service. To complete these steps,
the service requires various permissions, including permissions to log on locally. These
permissions are granted to local administrators. The SharePoint Timer Service Windows service
runs under the SPFarm account; however, you must restart the service to ensure the process has
the administrative privileges you granted in the previous step.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Open the Services MMC plug-in.
Restart the SharePoint Timer Service Windows service.
Register the CONTOSO\ProfileService account that you created in the previous tasks as a managed
account.
Task 5: Create a new User Profile Service Application application instance
Browse to the Manage Service Applications page.
Create a new instance of the User Profile Service Application service application with the following
properties:
Property Setting
Name Contoso UPSA
Application pool name ContosoUPSAAppPool
Application pool service account CONTOSO\ProfileService
Verify that the service application and a corresponding service application proxy are added to the list
of service applications.
Task 6: Configure the User Profile Synchronization Service Application application
instance to support NetBIOS domain names
Use the Get-SPServiceApplication cmdlet in PowerShell to instantiate a variable named $upsa. Use
a where filter to locate the User Profile Synchronization Service Application application.
Set the NetBiosDomainNamesEnabled property of the $upsa object to true.
Call the Update method on the $upsa object to make the change permanent.
Task 7: Start the User Profile Synchronization Service service
On the Central Administration website, browse to the Services on Server page.
Star the User Profile Service, if it is not already started.
Start the User Profile Synchronization Service service, by specifying the Contoso UPSA user profile
application and the password Pa$$w0rd for the SPFarm user account.
Verify that the service starts successfully. You will need to refresh the page to update the status and
the service may take some time to start.
Note: If the service does not start after 10 minutes then it is likely that you have a
configuration error. You must use PowerShell to stop the service and then correct the error.
You can use the following PowerShell script to stop the User Profile Synchronization Service:
Get-SPServiceInstance | where {$_.DisplayName} like "user*" | Stop-SPServiceInstance
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 8: Configure a connection to Active Directory
Browse to the application management page for the Contoso UPSA service application.
View the synchronization settings, and verify that the service is configured to synchronize users and
groups, and that SharePoint profile synchronization should be used.
Create a new synchronization connection with the following properties:
Property Setting
Connection name Contoso Domain
Type Active Directory
Forest name contoso.com
Domain controller Auto-discover
Account name CONTOSO\SPFarm
Password Pa$$w0rd
Containers to synchronize All
Task 9: Configure profile synchronization
Browse to the application management page for the Contoso UPSA service application.
Enable the synchronization timer job. Accept the default schedule.
Browse to the application management page for the Contoso UPSA service application, and then
start a full profile synchronization. Wait for the synchronization to complete before continuing.
Task 10: Test profile synchronization
Browse to the Manage User Profiles page.
View the user profile for the CONTOSO\Jim user account.
Note: Some fields will display error messages. This is expected because you have not
configured all of the social features in SharePoint 2013 to support these fields.

Results: After completing this exercise, you should have configured two-way profile synchronization.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 2: Configuring My Sites
Scenario
In this exercise, you will configure My Sites. You will create a new web application to host the My Sites.
You will also create a new service account for this web application, which you will register as a SharePoint
managed account, and you will configure DNS.
You will then create a My Site Host site collection in the new web application. After you create the My Site
Host site collection, you will configure the My Site settings in the User Profile Service Application instance
and complete the configuration.
Finally, you will test My Site creation.
1. Configure a DNS record for the My Site web application
2. Create a service account for the My Sites web application application pool
4. Create and configure a new web application to host My Sites
5. Create a My Site host site collection
6. Enable Self-Service Site Creation for the My Site host web application
7. Configure My Site settings for the User Profile Service Application service application instance
8. Enable the User Profile Service Application - Activity Feed Job timer job
9. Test My Site creation by using a non-administrative user account
Task 1: Configure a DNS record for the My Site web application
Switch to the 20332B-NYC-DC-05 virtual machine. If you are not already logged on, log on as
Open DNS Manager.
Add a new host record to the Contoso.com forward lookup zone with the following properties:
Property Setting
Name mysites
Task 2: Create a service account for the My Sites web application application pool
Property Setting
Full name My Sites Application Pool
UPN logon MySitesAppPool@contoso.c
om
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
SAM Account Name logon Contoso\MySitesAppPool
Password Pa$$w0rd
Register the CONTOSO\MySitesAppPool account that you created in the previous task as a
managed account.
Task 4: Create and configure a new web application to host My Sites
Create a new web application with the following properties:
Property Setting
IIS web site name MySites - 80
Port 80
Host header mysites.contoso.com
Application pool name SharePointMySites - 80
Application pool security account CONTOSO\MySitesAppPool
All other settings Accept default setting
Add a managed path named personal to the mysites.contoso.com web application.
Task 5: Create a My Site host site collection
mysites.contoso.com web application with the following properties:
Property Setting
Title MySite Host
URL http://mysites.contoso.com
Template My Site Host
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
Task 6: Enable Self-Service Site Creation for the My Site host web application
On the Central Administration website, browse to the Web Application Management page.
Enable self-service site creation for the MySites - 80 web application with default settings.
Task 7: Configure My Site settings for the User Profile Service Application service
application instance
Browse to the service application management page for the Contoso UPSA service application.
Configure the My Site settings for the Contoso UPSA user profile service application by using the
following properties:
Property Setting
My Site host location http://mysites.contoso.com
All other settings Leave blank or accept the default setting
Task 8: Enable the User Profile Service Application - Activity Feed Job timer job
Browse to the Timer Jobs page.
Enable the Activity Feed Job timer job associated with the Contoso UPSA service application.
Task 9: Test My Site creation by using a non-administrative user account
Switch to the 20332B-NYC-DB-05 virtual machine and log on as jim@contoso.com with the
password Pa$$w0rd.
Open Internet Explorer and navigate to the http://sharepoint.contoso.com site. Log on as
jim@contoso.com with the password Pa$$w0rd.
On the SharePoint site, browse to the users My Site. Log on as jim@contoso.com with the
password Pa$$w0rd.

Results: After completing this exercise, you should have configured My Sites and tested My Site creation
for a non-administrative user.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Building Communities
In this lesson, you will learn about communities and community site features in SharePoint 2013.
Specifically, you will learn about the structure of Community Sites, how to plan for communities, and how
to create and configure Community Sites and Community Portals in SharePoint 2013.
Lesson Objectives
After completing this lesson you will be able to:
Understand communities and Community Site structure in SharePoint 2013.
Plan Community Sites in SharePoint 2013.
Create and configure Community Sites in SharePoint 2013.
Create and configure Community Portals in SharePoint 2013.
Understanding Communities in SharePoint 2013
Community Sites and community features are new
in SharePoint 2013. Essentially, Community Sites
provide a rich and full-featured forum site
experience for communities within an
organization. In this context, communities can be
any group of people with mutual goals who
collaborate to share information, exchange ideas,
and discuss issues. Communities offer a platform
for promoting and encouraging collaboration
between large numbers of people in an enterprise.
Community Sites provide a user forum to classify
and encourage discussions within a group of
people in an enterprise. They provide a central place for communication and the sharing of expertise and
interest information between users who want to share their expertise and find other people in the
organization with specific skills and interests. Through posts and replies, members of the Community Site
can obtain useful information and can evaluate the replies to see which might be most useful to them
based on the number of "likes" it has received and whether it has been marked as a best reply.
This system provides motivation for members of the community to contribute and build themselves a
reputation within the community. Users who have provided the most constructive contributions to the
community will gradually become Top Contributors and earn trust from other members.
Uses and benefits of communities
Communities use categories to establish and group their discussions. A visitor to the community can view
those discussions and, if they are interested in contributing to the discussion, they can become a
community member. Moderators of the community are responsible for managing the community, its
members, and its content. This is done by applying usage rules, reviewing and determining inappropriate
posts, marking content of particular interest as featured discussions, and assigning badges to valued
community contributors. Members of the community can build up content reputation points, which they
earn by participating in discussions, by getting their content liked, or marked as a best reply by other
community members.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
There may appear to be similarities between community discussions and discussions in email distribution
lists; however, communities provide many additional benefits, including:
All users who have access to the community, either through membership or having visitor
permissions, can view discussions. With email distribution lists, only members of that list benefit from
discussions.
Communities persist longer and contain a discussion history of posts and replies, which are
immediately viewable even by recently joined members. This is in contrast to email distribution lists,
where a new user joining the list would only receive emails from the point that they joined the list.
Communities help assemble and categorize intellectual property that is otherwise hard to find. With
email distribution lists, this information would only be available if you part of the distribution list, and
they provide no technique for categorizing email messages. Also, search results of email messages in
a distribution list are only returned within the members own folders.
Communities inspire and incentivize members for participating in the community by building their
reputation points for posting, replying, and receiving likes and best replies.
Communities have their own built-in moderation capability to help keep the community active and
suitable to the needs of the organization.
Community Site template
The new Community Site template in SharePoint 2013 is provided as one of the Collaboration templates,
and it is based on the Team Site template. The Community Site template provides the same fundamental
elements that the Team Site template does, such as lists, libraries, wiki-page editing, and so on, but it also
provides additional features and elements, such as:
New Pages. About, Administration Settings, Categories, Home and Members
New Lists. Badges, Categories, Community Members, and Discussions
New Web Parts. There are also new Web Parts:
o Whats Happening. This is available for both members and visitors, and it displays the number of
members, discussions, and replies in the community.
o Top Contributors. This is available for both members and visitors, and it displays which members
contribute most to the community.
o My Membership. This is available only for members, and it displays information about their
membership activity, such as the number of posts and replies they have made.
o Community Tools. This is available only to site owners and community moderators. It is used to
access community management tasks such as managing discussions, creating categories,
assigning badges to members, reputation settings, and community settings.

Community Portal template
The new Community Portal template in SharePoint 2013 is provided as one of the Enterprise templates.
Essentially, the Community Portal provides a search-driven platform for users to discover community sites
of interest within the SharePoint farm. It also uses a Popular Communities Web Part to display the
communities that generate the most posts, replies, and members. The popularity grading is done by
weighting posts higher than replies and members. As such, even if a community with a small member
count has a lot of posts, it is likely to be graded as more popular than a community with a lot of members
but little posting activity. When a Community Portal template is deployed in a farm with My Sites
configured, users can access the Community Portal from their My Site page through the Sites link.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: There can only be one Community Portal per SharePoint 2013 farm.
Community usage options
In SharePoint 2013, there are several ways that you can use Community Sites and features:
Create a stand-alone community at the site collection or site level. You can create a community in an
organizational portal so that you can expedite discussions among members of the organization and
organize community items by using categories.
Populate a community with email messages from a distribution list. This is a one-way only approach
where email messages populate the discussions in the community, but new posts and replies
originating from the community do not appear in the email distribution list.
Activate community features on existing sites. You can activate the community features on any site.
This will give your site the fundamental Community Site pages, built-in moderation, membership, and
reputation capabilities without having to create a community itself. This would be useful in a scenario
where you want to provide community-type functionality on an existing team site, but you do not
want the overhead of creating and managing a separate community site.
Community membership
The membership of a community is maintained in a list in that Community Site, so membership and
reputation information are specific to that site. You can choose to allow people to join your Community
Site without prior approval, or you can specify that people are required to request access to the
community and provide them the email address of an approver. This requires that you enable outgoing
email in your SharePoint 2013 farm.
Community Site permissions
In SharePoint 2013, Community Sites use the SharePoint permissions infrastructure to secure the
community and provide appropriate access to its contents and allow for participation in the community.
You can either use SharePoints default permission levels, or you can configure your own specific
permissions if you want to limit the discoverability, accessibility, and usability of the Community Site.
The following table lists the SharePoint groups, their default permission levels, and a description of the
permissions granted.
SharePoint
Group
Permission
Level
Permission Description
Members Contribute Members can view, add, update, and delete lists and documents.
Members can only read the Categories and Members list items,
and the site pages.
Moderators Moderate Moderators can view, add, update, delete, and moderate list
items and documents.
Owners Full Control Owners have full control of the site.
When you create a Community Site, you specify a primary
owner, and optionally a secondary owner. These users belong to
the Owners group for the Community Site and have permission
to add users to groups.
Visitors Read Visitors can view pages and list items, and
download documents.
Visitors Read Visitors can view pages and list items, and download documents.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
These default groups and permission levels will be adequate for many organizations; however, you can
create more groups and configure unique permission levels to suit your communitys needs.
Additional Reading: For more information about how to plan for user permissions on
Community Sites, see Plan for communities in SharePoint Server 2013 at
Discussion: Organizing Discussions in a Community Site
If you implemented a community site within your
organization, what categories would you create to
organize discussions?

Planning for Communities
Community planning is most effective when
business users support it by mapping communities
to organizational goals and by working alongside
IT to develop and implement the plan through
technology. When you plan to implement a
Community Portal and Community Sites in
SharePoint 2013, ensure that you have suitable
business leaders and users involved at an early
stage when determining the needs of the
organization. This ensures that the planning effort
has a purpose suitable for a community solution.
The planning effort involved when planning for a
Community Portal and Community Sites can be broken up into four distinct phases.
Phase 1: Identify project stakeholders and responsibilities
The first phase is to determine stakeholders who will be responsible for defining the needs of the
organization, evaluating potential solutions, creating a schedule, and for approving the collaboration
solution plans.
Business leaders and users need to obtain input from IT staff about the technology options available when
promoting collaboration initiatives for the organization. You need to have a balance of people involved as
stakeholders of the project to gain the most benefit from the planning effort. To guarantee successful user
adoption of the solution, you should ensure that some of the stakeholders are very knowledgeable about
the workplace and the workforce; this will help identify their major pain points and challenges, which the
eventual solution can then address.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Phase 2: Determine business needs and evaluate collaboration solutions
The second phase is all about evaluating the potential collaboration solutions provided by SharePoint
2013 and ensuring that they map to, and meet, the determined business needs.
You should start with the goals of the business and then use them to develop the plan for the community
solution. If communities are a new concept for your organization, start with low-risk business needs and
deploy the intended solution to a small group of users who are ready and willing to collaborate. After this
is deemed a success, you can add other communities later, bit by bit.
During this phase of the planning process, you need to consider the following information when
evaluating social computing features and capabilities in SharePoint 2013:
Community Sites. These are best suited to mass collaboration initiatives, where large numbers of users
collaborate by sharing information and expertise from other people across organizational and
hierarchical boundaries. They are a persistent form of information, expertise-gathering, and storage.
Team Sites. These are best suited to distinct user groups who want to collaborate and store
information that is common to the team, such as documents and calendars. They are typically used
within organizational hierarchies, and are generally more permanent than Project Sites.
Project Sites. These are best suited to distinct user groups who collaborate on specific projects,
although these users might span organizational hierarchies. These types of sites usually exist for the
life of the respective project, and they are often archived or simply deleted when the project has
come to an end.
My Sites. These are best suited to individual users in order to promote their profile information, store
and share personal documents, build networks of people, follow content and sites of interest, stay up
to date through newsfeeds, and participate in microblogging activities. Some elements of a My Site
last longer than others, such as stored documents and profiles; however, other elements, such as
newsfeed items, might last for a much shorter time.
Phase 3: Plan the solution
The third phase is where you plan the actual solution architecture. This involves finding the answers to
several key planning questions:
Do you need a new dedicated Community Site, or will a discussion list or community features added
to an existing site fulfill your needs?
How many Community Sites are you going to need?
Will you require a Community Portal to act as a directory of all your Community Sites?
Should your Community Sites be open, closed, or private?
Should you make your Community Sites discoverable by other users in the organization?
How do you want to handle membership approval?
What is the primary language for your Community Sites?
Where does each Community Site logically belong in the current or planned SharePoint
environment?
What services and service applications do you have or need that support community features and
functionality?

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Phase 4: Define site ownership and moderation roles
The final phase is when you need to identify which users you will need to assign as site owners and site
moderators. You need to work closely with these users so that they can understand and apply the
appropriate permissions for the community based on the needs of the business.
Community Site moderators play a very important role in managing and maintaining the community to
keep it active and useful. They must have the permissions and tools to perform the following key tasks in
a Community Site:
Manage categories.
Manage discussions.
Edit and delete posts.
Mark posts as featured items or best replies.
Monitor potentially inappropriate flagged content.
Configure reputation settings and assign badges.
Note: When you change reputation settings after members join and participate in a
community, SharePoint 2013 will not recalculate the existing reputation of members. Therefore,
you should ensure that site owners and moderators configure reasonable reputation settings
before members start to use the community, and encourage them not to change the settings
later unless absolutely necessary.
You should also define the rules for participating in the community and the actions that will be taken if
the rules are broken. Although most communities are relatively self-governing, moderators need to have
clearly defined guidelines on what to do in cases where rules have been broken and how to use
technology to implement the consequences of doing so.
Encourage your site owners and moderators to use the Manage Discussion view to monitor community
activity by exporting the discussion list to Excel. This will be very helpful to them when addressing
community issues relating to discussions and replies. For example, they may need to move discussions to
more appropriate categories, or try to encourage participation where posts are going unanswered.
Additional Reading: For more information about planning for communities, see Plan for
communities in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=302097
Creating and Configuring Community Sites
You can use Central Administration to create a
Community Site to provide a discussion forum and
social interface for your SharePoint 2013
environment. They can be created at the site
collection or site level.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Create a Community Site
Perform the following steps to create a Community Site:
1. In Central Administration, under Application Management, click Create site collections.
a. Ensure that the selected web application is the web application in which you want to create the
Community Site.
b. Provide a title and description for the site collection.
c. Select the URL where you want to create the site collection.
d. In the Template Selection section, on the Collaboration tab, select Community Site.
e. Enter the account name of the Primary Site Collection Administrator, and optionally the
Secondary Site Collection Administrator using the format domain\username.
f. Optionally, select a quota template for the site collection.
g. If you want to verify the site collection has been created successfully, you can click the URL link to
open the new Community Site.
Configure a Community Site
In a Community Site, in the Community Tools section, you can access Community settings to configure
the following:
Established date. This sets the date that the community was established that is displayed on the About
page.
Auto-approval for permission requests. This setting enables you to allow people to join the community
without prior approval from a site administrator. When this setting is not enabled, site administrators
are required to approve every request to join the community.
Reporting of offensive content. This setting enables you to allow community members to report
abusive or inappropriate content. After the content has been reported as offensive, site administrators
and moderators can review the reported content and either remove it or reinstate it as non-offensive.
In the Community Tools section of a Community Site, you can also access Reputation settings to
configure the following settings:
Rating settings. This specifies whether list items can be rated, and whether to use Likes or Star Ratings
as the rating system.
Member achievements point system. This enables and configures the member achievements point
system.
Achievement level points. This specifies the different achievement level values.
Achievement level representation. This specifies whether to display achievement levels as images or
text.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Creating and Configuring Community Portals
A Community Portal provides a Community Sites
directory to help users browse and search for
communities that might be of interest to them in
SharePoint 2013. Community Portals can only be
created at the site collection level, and there is
only one Community Portal per SharePoint 2013
farm. Central Administration is used to create
community portals.
Create a Community Portal
Perform the following steps to create a
Community Portal:
1. In Central Administration, under Application Management, click Create site collections.
a. Ensure that the selected web application is the web application in which you want to create the
Community Portal.
b. Provide a title and description for the site collection.
c. Select the URL where you want to create the site collection.
d. In the Template Selection section, on the Enterprise tab, select Community Portal.
e. Enter the account name of the Primary Site Collection Administrator, and optionally the
Secondary Site Collection Administrator using the format domain\username.
f. Optionally, select a quota template for the site collection.
g. If you want to verify the site collection has been created successfully, you can click the URL link to
open the new Community Portal.
Run a search crawl on the Community Portal
On a Community Portal, no Community Sites appear until after you run a search crawl to populate the
Community Site list. You can configure the incremental crawl schedule so that the Community Portal
displays any newly created Community Sites to make it easier for members of the community to find
them.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring Community Sites
Scenario
Contoso wants to encourage social computing and hopes to increase morale and save money by
providing a simple system for employees to communicate in an informal manner. To support this,
Contoso wants to develop community sites that are easy to locate and easy to join. The management
overhead associated with these sites should be minimal. You have been tasked with creating a community
site architecture. You will create a community portal to make it easy for employees to locate community
sites that are relevant to them. You will then create some community sites and verify that they display on
the community portal. To reduce management overhead, you will configure the site to allow anyone to
join the site. To help ensure the site is not abused, you will ensure that any offensive content can be
reported, and use reputation settings to make it easy for members of the site to identify regular, helpful
users.
Objectives
Create a community site infrastructure.
Configure community site participation.
Password: Pa$$w0rd
Virtual Machine 20332B-NYC-DB-05
User name: jim@contoso.com
Password: Pa$$w0rd
Virtual Machine 20332B-NYC-DC-05
User name: ray@contoso.com
Password: Pa$$w0rd
Exercise 1: Creating a Community Site Infrastructure
Scenario
In this exercise, you will create a community site infrastructure, which will include a community portal to
make it easy to locate community sites, as well as multiple community sites.
You will configure DNS and service accounts for a new web application in which you will create the
community sites. You will create a community portal at the root of the new web application, and then you
will create two community sites, one for the Sales department and the other for the Finance department.
To enable the community portal to list all of the available community sites, you will configure the search
service and perform a search crawl.
Finally, after verifying that the community sites appear correctly on the community portal, you will create
two discussions on the Finance community site.
1. Configure a DNS record for the community site portal
2. Create a service account for the community portal web application application pool
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4. Create and configure a new web application for the community site portal
5. Create a site collection for the community portal
6. Create community sites for the Finance and Sales departments
7. Create service accounts for the search service
8. Register the service accounts as SharePoint managed accounts
9. View the community sites on the community portal
10. Create discussions on the Finance community site
Task 1: Configure a DNS record for the community site portal
Open DNS Manager.
Property Setting
Name community
Task 2: Create a service account for the community portal web application
application pool
Start the Active Directory Administrative Center.
Property Setting
Full name Community Application Pool
UPN logon CommunityAppPool@contoso.com
SAM Account Name logon Contoso\CommunityAppPool
Password Pa$$w0rd
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Register the CONTOSO\CommunityAppPool account that you created in the previous task as a
managed account.
Task 4: Create and configure a new web application for the community site portal
Create a new web application with the following properties:
Property Setting
IIS web site name Community - 80
Port 80
Host header community.contoso.com
Application pool name SharePointCommunity - 80
Application pool security account CONTOSO\CommunityAppPool
All other settings Accept default setting
Add a managed path named forums to the community.contoso.com web application.
Configure outgoing e-mail settings for the community.contoso.com web application with the
Property Setting
Outbound SMTP server mail.contoso.com
From address community@contoso.com
Reply address donotreply@contoso.com
Task 5: Create a site collection for the community portal
community.contoso.com web application with the following properties:
Property Setting
Title Community Portal
URL http://community.contoso.com
Template Community portal
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 6: Create community sites for the Finance and Sales departments
Create a new site collection in the community.contoso.com web application with the following
properties:
Property Setting
Title Finance Forum
URL http://community.contoso.com/forums/Finance
Template Community site
Create another new site collection in the community.contoso.com web application with the
Property Setting
Title Sales Forum
URL http://community.contoso.com/forums/Sales
Template Community site
Task 7: Create service accounts for the search service
Property Setting
Full name Search Service Admin Web Service Application Pool
UPN logon SearchAdminAppPool@contoso.com
SAM Account Name logon Contoso\SearchAdminAppPool
Password Pa$$w0rd

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
Full name Search Service Query Web Service Application Pool
UPN logon SearchQueryAppPool@contoso.com
SAM Account Name logon Contoso\SearchQueryAppPool
Password Pa$$w0rd
Property Setting
Full name Search Service Account
UPN logon SearchService@contoso.com
SAM Account Name logon Contoso\SearchService
Password Pa$$w0rd
Task 8: Register the service accounts as SharePoint managed accounts
On the Central Administration website, navigate to the Managed Accounts page.
Register the CONTOSO\SearchAdminAppPool account that you created in the previous task as a
managed account.
Register the CONTOSO\SearchQueryAppPool account that you created in the previous task as a
managed account.
Register the CONTOSO\SearchService account that you created in the previous task as a managed
account.
Task 9: View the community sites on the community portal
In Internet Explorer, on a new tab, navigate to the http://community.contoso.com site. Log on as
administrator with password Pa$$w0rd when prompted.
Notice that currently the page displays an error. This is because the Community Portal site relies on
the search service which is not currently configured.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Create a new instance of the Search Service Application service application by using the following
properties:
Property Setting
Name Contoso Search
Search service account CONTOSO\SearchService
Admin application pool name SearchAdminAppPool
Admin application pool account CONTOSO\SearchAdminAppPool
Query and site settings application pool name SearchQueryAppPool
Query and site settings application pool account CONTOSO\SearchQueryAppPool
Start a full search crawl of local SharePoint sites. Do not continue until the search crawl finishes.
If the Local SharePoint sites content source does not appear in the list of content sources, you
should periodically refresh the page. It may take several minutes for SharePoint to populate the
content sources list after you create the Search Service Application service application.
Switch to the Community Portal tab, and refresh the page. Verify that the community portal now
lists the finance and sales community sites.
Task 10: Create discussions on the Finance community site
Browse to the Finance community site.
Create a new discussion on the Finance community site with the following properties:
Property Setting
Subject New Site
Body We now have a new forum site to discuss anything related to the Finance
department. Please use this site to ask questions or make suggestions.
Question No
Create a new discussion on the Finance community site with the following properties:
Property Setting
Subject Meal?
Body Are you interested in a departmental meal on Friday?
Question Yes

Results: After completing this exercise, you should have created a community site infrastructure, including
a community portal and multiple community sites.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 2: Configuring Community Site Participation
Scenario
In this exercise, you will enable auto-approval to enable users to easily access a community site. You will
then use auto-approval to gain access to the site by using an alternative user account.
As the site administrator, you will grant badges to members of the site, making them readily identifiable
to other site users. You will also review the reputation settings to ensure they are appropriate for the site.
Finally, you will use a third user account to participate in a discussion by posting inappropriate content.
You will use the second user account to report the inappropriate content, and then you will moderate that
content by using the administrative account.
1. Enable access requests for the Finance community site
2. Attempt to access the Finance community site with a non-administrative user account
3. Approve an access request for a community site
4. Attempt to access the Finance community site with a non-administrative user account
5. Enable auto-approval and reporting of offensive content for the Finance community site
6. Use auto-approval to gain access to the Finance community site with a non-administrative user account
7. Gift badges to community site users
8. Review the default reputation settings
9. Create categories and assign a category to an existing discussion
10. Moderate offensive content on the finance community site
Task 1: Enable access requests for the Finance community site
View the site permissions for the Finance community site.
Enable access requests for the Finance community site. Access requests should be sent to
financesiteadmin@contoso.com.
Task 2: Attempt to access the Finance community site with a non-administrative user
account
Switch to the 20332B-NYC-DB-05 virtual machine. If you are not already logged on, log on as
In Internet Explorer, navigate to the Finance community site at
http://community.contoso.com/forums/finance. Verify that you are denied access, but have an
option to request access to the site.
Request access to the site with the message I would like to participate in departmental discussions.
Task 3: Approve an access request for a community site
Browse to the Site Settings page for the Finance Forum site.
View the access requests for the Finance Forum site.
Approve the pending request from Jim Corbin.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
account
Switch to the 20332B-NYC-DB-05 virtual machine. If you are not already logged on, log on as
http://community.contoso.com/forums/finance. Verify that you now have access.
Join the Finance Forum site.
Task 5: Enable auto-approval and reporting of offensive content for the Finance
community site
Browse to the community settings for the Finance Forum site.
Enable auto-approval and reporting of offensive content for the Finance Forum site.
3. Add Everyone to the Finance Forum Visitors SharePoint security group. Do not send an invitation
email.
Task 6: Use auto-approval to gain access to the Finance community site with a non-
administrative user account
Switch to the 20332B-NYC-DC-05 virtual machine. If you are currently logged on, log off.
Log on as ray@contoso.com with the password Pa$$w0rd.
http://community.contoso.com/forums/finance. Verify that you have visitor access and that you
can view discussions, but that you cannot reply to them.
Join the Finance Forum site. Verify that you now have the option to reply to discussions.
Task 7: Gift badges to community site users
Review the default badges for the Finance Forum website.
Create a new badge named Site Admin.
Grant the Expert badge to the CONTOSO\Jim user.
4. Grant the Site Admin badge to the CONTOSO\Administrator user.
Task 8: Review the default reputation settings
Review the default reputation settings for the Finance Forum website, but do not make any changes.
Task 9: Create categories and assign a category to an existing discussion
Create a new category named Chat, with the description Non-work related discussions.
Assign the Chat category to the Meal? discussion.
Task 10: Moderate offensive content on the finance community site
Switch to the 20332B-NYC-DC-05 virtual machine.
Add the reply I do not care about your meal I came to the last one and it was boring! to the Meal?
discussion.
Switch to the 20332B-NYC-DB-05 virtual machine.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
View the Meal? discussion.
Report the reply left by Ray as offensive, with the message I find this response offensive.
Review reported posts.
Edit the reported post. Change the text of the post to [OFFENSIVE CONTENT REMOVED].
Dismiss the offensive content report to remove it from the list of reported posts.
Refresh the Meal? discussion and verify that the offensive message has been replaced with the
moderators edit.

Results: After completing this exercise, you should have configured community site participation, by
making it easy for users to access a community site, and you should have used community site features to
ensure the site is used properly.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you have learned about the key concepts of user profiles and user profile synchronization
in SharePoint 2013. You have also learned how to enable social interaction and configure social features,
and how to build communities using community sites in SharePoint 2013.
Review Question(s)
Test Your Knowledge
Question
What is the default schedule for profile synchronization jobs?

Every 5 minutes
Every 10 minutes
Every 15 minutes
Every 30 minutes
Test Your Knowledge
Question
Which social microblogging feature is used to tag other users by name in posts and
replies?

Following
Likes
Mentions
Ratings
Tags

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Test Your Knowledge
Question
Which Community Site Web Part displays the number of members, discussions, and
replies in the community?

Community Tools
My Membership
Top Contributors
Whats Happening

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6-1
Module 6
Enabling Productivity and Collaboration
Contents:
Module Overview 6-1
Lesson 1: Aggregating Tasks 6-2
Lesson 2: Planning and Configuring Collaboration Features 6-8
Lab A: Configuring Project Sites 6-15
Lesson 3: Planning and Configuring Composite Solutions 6-20
Lab B: Configuring Workflow 6-26

Module Overview
Microsoft SharePoint Server 2013 extends the ability of users to work collaboratively and increase
productivity through seamless integration with external software platforms, additional SharePoint
collaboration features, and the provision of flexible tools, with which users can develop their own
solutions to business problems.
For most business users, email and project-related tasks take up most of their working day. SharePoint can
now tightly integrate with Microsoft Exchange Server 2013 and Microsoft Project Server 2013. This
integration with external systems means that you can provide users with a consistent set of resources and
fully integrated personal business information.
SharePoint 2013 includes improvements to the collaborative user experience. Central to this is the
extension of the co-authoring functionality that was previously available in SharePoint Server 2010. Co-
authoring has now become more granular and includes richer functionality with a broad set of client
applications and Office Web Apps.
For power users and even less experienced users, SharePoint continues to provide solution development
options. Composites are essentially code-free business solutions that users can create from the functions
available from SharePoint, Microsoft Access 2013, and other Microsoft Office 2013 products. SharePoint
2013 also has an enhanced workflow architecture so that users can benefit from Representational State
Transfer (REST) workflows.
Objectives
Explain how the integration options for Exchange 2013 and Project Server 2013 improve task
aggregation.
Describe how to plan and configure SharePoint collaborative and co-authoring options.
Describe how to plan and use workflows in SharePoint 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6-2 Enabling Productivity and Collaboration
Lesson 1
Aggregating Tasks
Task aggregation in SharePoint focuses on the integration of business productivity infrastructure and the
SharePoint services that support task management. The new Work Management Services service
application provides an underlying architecture that enables users tasks to be aggregated to their My
Site.
To support Work Management Services, SharePoint can integrate with Exchange 2013 to provide a
coherent environment to manage tasks and email. Beyond this, you can also integrate project
management functionality by linking Project Server 2013 to deliver seamless project task aggregation. For
organizations that do not use Project Server 2013, SharePoint can combine the flexibility of a SharePoint
task list with Project Professional 2013 to deliver professional project management with the collaborative
functionality of SharePoint 2013.
Lesson Objectives
Describe Work Management Services.
Explain how to connect your SharePoint 2013 and Exchange 2013 environments.
Describe the functions of trust management.
Explain how to integrate Project Server 2013 and SharePoint 2013.
Describe the different levels of Microsoft Project products and technologies with SharePoint 2013.
Overview of Work Management Services
The challenge for information workers, and the IT
Professionals who support them, is the scattered
nature of their work tasks. These can be stored
across a series of applications or sites, so that it is
difficult to have a comprehensive, centralized view
of working tasks. Even when all tasks are held on
SharePoint, they can be held in a number of
different places.
The Work Management Service, which is only
available in SharePoint 2013 Enterprise Edition, is
designed to provide a single view of their tasks
and start and end times, and deadlines. User tasks
from a range of SharePoint sites or external applications can be aggregated to a single view.
Work management task architecture
The Work Management Service is designed to aggregate tasks on a users personal My Site. With Work
Management Services configured, user tasks on farm sites can be rendered on the My Site to deliver a
holistic view of the tasks that are timetabled for that day or week. Beyond SharePoint 2013 sites, you can
also integrate tasks from a Project Server service application on the same farm, such that they are
displayed on the same My Site. This can also extend to include tasks created in and Outlook client which
can be synchronized with Exchange 2013 and then, in turn, synchronized with SharePoint 2013. The
architecture can be extended to synchronize with other external sources.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: To integrate SharePoint 2013 and Exchange 2013, you must install the Exchange
Web Services Managed API on your Exchange 2013 server. This is available at
When a user accesses their My Site, a synchronous request is made to update the tasks that are held in the
service cache. An asynchronous request to other providers, such as Exchange or Project Server, is also
triggered. These providers send updates to the service cache when their internal update jobs run. In the
case of Exchange, there is a timer job that sends updates to the cache.
Configuration
The Work Management Service application is created automatically when you run the SharePoint Farm
Configuration wizard. If, as is more likely, you manually configure your farm, you can create a Work
Management Service application from the Manage Service Applications page. To do so, you click Add
Service Application from the ribbon, and then click Work Management Service Application.
Additional information is limited to specifying an application pool and a service application proxy.
There is no specific configuration for the Work Management Service through Central Administration or
Windows PowerShell. Its functionality is accessed programmatically through the out-of-the-box features
provisioned by the service. However, there are some service application dependencies that must be
configured to use the Work Management Service. You must have both the Search and User Profile
Management services configured, with the Work Management Service service account given Full Control
permissions on the User Profile Service.
My Sites rendering
The tasks appear on the My Sites pages in a timeline format for users, split into the following categories:
Important and Upcoming Tasks
Active Tasks
Completed Tasks
Connecting to Exchange Server 2013
When you plan your inter-server authentication,
you need to identify the trust relationships that
you need to configure on SharePoint 2013. These
trust relationships between two servers can be
incoming (service requests) and outgoing (sending
requests) to the SharePoint 2013 server. For the
former, the SharePoint 2013 server must trust the
requesting server, whereas for the latter, the
SharePoint 2013 server must be trusted by the
server that services its requests. In your SharePoint
farm, you must identify the relationships on a per-
server basis.
OAuth authentication
You create trust relationshipsserver-to-server authenticationto enable server products, such as
SharePoint 2013, Exchange Server 2013, Lync Server 2013, and Azure Workflow Service, to share and
request resources. This authentication uses the Open Authorization (OAuth) 2.0 protocol. It is unique to
server communication, so it does not appear as an identity provider, unlike authentication protocols for
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
user access. Use of a common protocol streamlines inter-server integration. OAuth uses tokens to provide
the requesting server with access to a resource on the sharing server.
For on-premises implementations of OAuth between SharePoint 2013, Exchange Server 2013, and Lync
Server 2013, the servers issue self-signed tokens that provide access to resources. The sharing server must
trust the token from the requesting server. You establish this trust relationship by configuring a partner
application that includes the requesting servers. After you establish a trust relationship, you need to grant
permissions to the application principal.
Server-to-server authentication configuration (SharePoint 2013 and Exchange Server
2013)
Server-to-server authentication configuration between SharePoint 2013 and Exchange Server 2013 has
three core steps:
1. Configuring the SharePoint 2013 server to trust the Exchange Server 2013 server.
2. Configuring permissions on the SharePoint 2013 server.
3. Configuring the Exchange Server 2013 server to trust the SharePoint 2013 server.
The first step in the process is to configure the SharePoint 2013 server to trust its Exchange Server 2013
counterpart. You complete this task with Windows PowerShell cmdlet New-
SPTrustedSecurityTokenIssuer.
New-SPTrustedSecurityTokenIssuer MetadataEndpoint
"https://<ExchgHostName>/metadata/json/1" IsTrustBroker Name
"<ExchgHostFriendlyName>"
Where:
<ExchgHostName> is the name or address of the Exchange Server 2013 server.
<ExchgHostFriendlyName> is a friendly name for the Exchange Server 2013 server.
The second step is to configure the appropriate permissions on the SharePoint 2013 server. An application
principal is a special type of user that represents an external application, in this case Exchange. You are
granting permissions to this user.
To do this, you use the Windows PowerShell cmdlet Set-SPAppPrincipalPermission in the following
script:
$exchange=Get-SPTrustedSecurityTokenIssuer
$app=Get-SPAppPrincipal -Site http://<SPHostName> -NameIdentifier $exchange.NameId
$site=Get-SPSite http://<SPHostName>
Set-SPAppPrincipalPermission AppPrincipal $app Site $site.RootWeb Scope
sitesubscription Right fullcontrol -EnableAppOnlyPolicy
Where:
<SPHostName> is the name or address of the SharePoint 2013 server.
The final step is to configure the Exchange Server 2013 server to trust the SharePoint 2013 server by
running the following script in the Exchange Management Shell:
cd c:\'Program Files'\Microsoft\'Exchange Server'\V15\Scripts
.\Configure-EnterprisePartnerApplication.ps1 -AuthMetadataUrl
https://<HostName>/_layouts/15/metadata/json/1 -ApplicationType SharePoint
Where:
<HostName> is the name and port of any SSL-enabled web application of the SharePoint farm.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Project Server 2013 Integration
You can configure Project Server 2013 to run as a
service application in SharePoint 2013. This
requires you to have both SharePoint 2013 and
Project Server 2013 installed. You should already
be familiar with the installation of SharePoint
2013, so this section only covers the installation of
Project Server and its deployment as a service
application.
Installing Project Server 2013
To install Project Server 2013, use the following
procedure:
Insert the Project Server 2013 media. This should automatically open the Setup menu. (If this does not
automatically open, navigate to and launch default.hta on the installation media.
1. On the Start page, click Install Project Server.
2. On the Enter your Product Key page, type your product key, and then click Continue.
3. In the End User License Agreement page, select the I accept the terms of this agreement check
box, and then click Continue.
4. On the Choose a file location page, click Install Now.
5. When the installation is complete, clear the Run the SharePoint Products and Technologies
Configuration Wizard now check box and click Close.
You must complete this procedure on each of the application servers on the farm where you want to host
Project Server 2013.
After Project Server 2013 is installed, you can run the SharePoint Products Configuration Wizard to
integrate Project Server with SharePoint Server 2013. Again, this should occur on each application server
that hosts Project Server 2013.
Configuring the Project Server service application
With Project Server 2013 installed, you must start the Project Server application service on at least one of
the servers.
1. On the Central Administration home page, click Manage services on server.
2. On the Services on Server page, select the server where you want to run the Project Application
Service from the drop-down list.
3. On the Service list, next to Project Server Application Service, click Start.
With the Project Server application service started, you now create a Project Server service application.
You will need a registered managed account to complete this configuration. The procedure for creating
the service application uses the following steps:
1. On the Central Administration home page, click Manage service applications.
2. On the Manage Service Applications page, click New on the ribbon, and then click Project Server
Service Application.
3. On the Create Project Web App service application page complete the form specifying the service
application name, the application pool, and the managed account to be used. Then click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Providing Different Levels of Project Integration
There are a range of levels to which users can
experience integration of SharePoint 2013 and
Microsoft Project Professional 2013, most of which
do not include the full integration of Project
Server 2013.
Opening SharePoint 2013 task lists in
Project Professional 2013
Your users can create a task list in a SharePoint
2013 site that they can then open in Project
Professional 2013. This is done by performing the
following steps:
1. Create a site and click the Working on a deadline? option.
2. In the dialog box, click Add Item.
3. Type in the tasks, resources, and timings that you require in the task list.
4. On a client computer that is running Project Professional 2013, open the SharePoint 2013 site, click
Tasks, and then, on the ribbon, click Open with Project. This opens your tasks in Project Professional
2013.
5. Add more tasks in the Project Professional 2013 client, click File, and then click Save.
6. Close Project Professional.
7. On the SharePoint site, refresh the Tasks page to see your changes.
You can use both the SharePoint task list and Project Professional 2013 to update the project.
Enabling the Project Web App site collection features
You can use a Project Web App to provide more features to your Project users. These site collection
features enable you to:
Import SharePoint 2013 task list projects into Project Web App.
Create reports from imported projects.
Implement SharePoint Project Web App security groups.
You use the Windows PowerShell cmdlet New-SPProjectDatabase to create a new Project Web App
database.
New-SPProjectDatabase Name <DatabaseName> -ServiceApplication
<ServiceApplicationName> -DatabaseServer <SQLServerInstance> -Tag <String>
Where the Tag <String> parameter associates a unique string with this database, which is used in later
in the configuration process.
With the Project Web App database available, you next enable the Project Web App site collection
features. Again, you do this by using the Windows PowerShell cmdlet Enable-SPFeature. The script
should conform to this format:
$web=Get-SPWeb SiteCollectionURL
$web.Properties["PWA_TAG"]="String"
$web.Properties.Update()
Enable-SPFeature pwasite -URL SiteCollectionURL
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Where the String parameter is the string that you specified in the New-SPProjectDatabase cmdlet.
To deliver the Project Web App site collection functionality to your users, you can either:
Add a Project Center Web Part to the site collection. This enables users to import SharePoint list
projects into Project Web App. To do this, you edit a page just as you would to add any Web Part; in
other words, you select Project Web App from the Categories list and then select Project Center
from the Parts list. You need to give users permission to view projects in the Project Center Web Part
by adding them to a Project Web App security group on the site collection.
Add a Project Web App site to the site collection. This provides full Project Web App functionality by
providing the Project Web App site, which includes the Project Center Web Part.
Enterprise Project features
For environments that use Project extensively for project management, you can convert a SharePoint task
list into an enterprise project. The most obvious change here is that the project can only be viewed, but
not updated, in the SharePoint task list view. You must use Project Professional 2013 or Project Web App
to edit the tasks.
You can activate the enterprise Project features by using the following procedure:
1. On the site collection Settings menu, click Project Web App Settings.
2. On the Project Server Settings page, click Connected SharePoint Sites.
3. On the Connected SharePoint Sites page, click Activate for the project.
With the enterprise Project features activated, you can create a new Project Web App site to the site
collection, and you can use the functionality available in Project Server 2013 and Project Web App. This is
done on a site collection basis. You can create a Project Web App site in an existing site collection by
adding a site and then running the Windows PowerShell cmdlet Upgrade-SPProjectWebInstance. You
will need to run iisreset after this to make the Project Web App site available.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Planning and Configuring Collaboration Features
Providing a collaborative working environment has always been central to SharePoint products and
technologies. This theme continues in SharePoint 2013, with a big emphasis on co-authoring, both for
traditional PCs and mobile devices. Although Office Web Apps are no longer a SharePoint service
application, their integration with SharePoint 2013 through the new Office Web App Server platform
remains integral to the co-authoring story.
There have been additional changes to include Project Site templates, to streamline project services to
SharePoint users, and changes to the architecture of Word Automation Services to provide near-real time
document conversion.
Lesson Objectives
Describe the function of Project sites.
Explain how to integrate Office Web App Server with SharePoint 2013.
Describe the new functionality and boundaries for Word Automation Services.
Describe how to implement co-authoring in SharePoint 2013.
Unified Task Management with My Sites and Project Sites
In modern business organizations, a user
oftentimes works across different projects. Because
these projects can use different platforms as the
repository of choice for project management, it
can be difficult for users to manage their time and
ensure that they complete their tasks on time and
efficiently. The solution to this problem is to
provide a unified environment where a user can
see all their tasks, irrespective of the project to
which each belongs.
My Sites
Unified task management must be built on the
delivery of personal tasks directly to the user. Preferably tasks should appear in a central location and in a
consistent format, so that each user can better manage their time and stay on schedule. In SharePoint
2013, a users tasks can be aggregated to his or her My Site page. All tasks are available from the left-
hand navigation menu, under Tasks. This link shows all tasks aggregated from all site collections for the
user in a timeline. This is not simply a reporting environment. The user can manage, modify, and create
tasks, which can also be synchronized to an Outlook calendar and with Microsoft Project products and
technologies.
In order to provision unified task management in My Sites, you must configure the following SharePoint
features and services:
Search Service
User Profile Service
A My Site host
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Work Management Service
A project site in one of the site collections
The tasks will appear in the Tasks timeline when a full crawl is completed.
Project sites
SharePoint 2013 provides the Project Site template for project managers to quickly deploy a site. A
project site can be used to manage users and manage basic project tasks within the context of a larger
project. In addition, like any site, this provides a central location where project members can share
documents and communicate.
The Project Site template provides the following components to help manage a project:
Project Summary Web Part (task timeline)
Project task schedule
Document library
OneNote team notebook
Shared calendar
Office Web Apps Integration
Office Web Apps provide browser-based
companion versions of Microsoft Office Word,
Excel, PowerPoint, and OneNote client
applications. Office Web Apps are available with
both SharePoint 2013 and SharePoint Online
(Office 365).
Note: Office Web Apps can also be available
with SkyDrive, Microsoft SharePoint Foundation
2010, and Microsoft SharePoint Server 2010.
In SharePoint Server 2010, Office Web Apps was a service application. This has changed in SharePoint
Server 2013, where Office Web Apps is now a server platform in its own right. That being the case, Office
Web Apps are still closely related to SharePoint 2013, providing browser-based editing solutions across a
range of document types.
New features for Office Web Apps
There are a number of new features in Office Web Apps, including:
Change tracking. Users can open Word files with revision marks in Word Web App.
Comments. Users can work with document comments in the Word and PowerPoint Web Apps.
Co-authoring. Co-authoring is now available for the Word and PowerPoint Web Apps. This is still
available with the Excel and OneNote Web Apps.
Ink support. Users can work with ink inserts in Word and OneNote Web App files.
Licensing. There are two levels of licensing for Office Web Apps working with SharePoint 2013:
o View-only. This is free and provides view-only access to documents through their associated Web
App.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Edit and View. This enables editing as well as viewing of documents in their associated Web App.
This is enabled when implementing the Office Web Apps Server farm.
Quick Preview. This provides a preview of documents for the SharePoint 2013 Search service
application.
Share by link. This enables users to share a human-friendly document link (URL) with colleagues which
can be viewed in the associated Web App.
Office Web Apps also includes the following improvements for mobile users:
PowerPoint attendee view. Users can attend PowerPoint broadcast slide presentations.
Excel Mobile Viewer. Users can sort data in a spreadsheet on a mobile device.
Word Mobile Viewer. Users can view images in documents.
Configuring Office Web Apps for sharing with SharePoint 2013
Office Web App Server 2013 is now a separate product from SharePoint 2013. The guidance for deploying
an Office Web Apps farm can be found at http://go.microsoft.com/fwlink/?Linkid=302104
To configure Office Web Apps availability from SharePoint 2013, there are some preparatory steps that
you must complete:
Authentication. Office Web Apps can only be configured with claims-based authentication. If you
have web applications that use classic-mode authentication, you need to upgrade or migrate these to
claims.
Licensing. If you intend to provide edit capabilities, you must ensure that you have the correct licenses
and have enabled editing on the Office Web App farm.
Request and response communication between the SharePoint 2013 and Office Web App farms can take
place using either HTTP or HTTPS protocols. Configuration for either communication protocol is
completed by using Windows PowerShell.
Note: WOPI is the Web Application Open Platform Interface Protocol. It defines a set of
operations that enables a client to access and change files stored by a server. It enables a client to
render files and provide file editing functionality for files stored on a server. For more information
about WOPI, see [MS-WOPI]: Web Application Open Platform Interface Protocol at
Configuring HTTPS communication
You must first create a binding between SharePoint 2013 and the Office Web Apps Server, by running the
following cmdlet:
New-SPWOPIBinding -ServerName <ServerName>
Where <ServerName> is the fully qualified domain name (FQDN) of the URL that you set for the internal
URL. You can specify an external URL if required.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
This displays a list of bindings. Office Web Apps Server uses zones to identify the URL and protocol to use
to communicate with a host. By default, SharePoint uses the internal-https zone. You can check that the
zone is correctly configured by running the following cmdlet:
Get-SPWOPIZone
Configuring HTTP communication
You must first create a binding between SharePoint 2013 and the Office Web Apps Server by running the
following cmdlet:
New-SPWOPIBinding -ServerName <ServerName> -AllowHTTP
Where <ServerName> is the fully qualified domain name (FQDN) of the URL that you set for the internal
URL. You can specify an external URL if required.
This displays a list of bindings. You can change this to HTTP by running the following cmdlet:
Set-SPWOPIZone zone "internal-http"
You can check that the zone is correctly configured by running the following cmdlet:
Get-SPWOPIZone
Next, you must configure the OAuth authentication. If the SharePoint site is using HTTP, the
AllowOAuthOverHttp setting should be set to True. You can check the setting by running the following
cmdlet:
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
If the cmdlet returns False, you should reset the configuration as follows:
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()
You should test that you can use Office Web Apps when viewing or editing (as licensed) documents from
a SharePoint library.
Word Automation Services
Word Automation Services (WAS) provides a
server-based conversion of documents into
formats that are supported by the Microsoft Word
client application. This service application was
introduced with SharePoint Server 2010. It enables
documents to be converted into Word readable
format from the following file types:
Open XML File Format documents (.docx,
.docm, .dotx, .dotm)
Word 97-2003 documents (.doc, .dot)
Rich Text Format files (.rtf)
Single File webpages (.mht, .mhtml)
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Word 2003 XML documents (.xml)
Word XML document (.xml)
The WAS architecture in SharePoint Server 2010 used the Object Model on a Web Front End (WFE) server
to deliver asynchronous conversion requests to a queue manager on an application server. Conversion
requests were queued to disk in a database file. A timer job would service the queue to send requests to
the Word File Conversion Engine, which would load balance requests across application servers and
perform the conversion.
This had a number of shortcomings for users, including:
Solutions were asynchronous and had to wait until the timer job execution to convert files.
The process could only handle files stored on SharePoint.
The user was not automatically notified when the conversion was complete.
In SharePoint 2013, the architecture has been modified to resolve these issues. The WFE functions have
remained broadly common with SharePoint 2010, but the application server queue can now service
requests immediately and not necessarily from a timer job. This operates on one file at a time per request,
with configuration options from Central Administration for simultaneous request volumes.
WAS now supports streamed input. These streams are now stored in memory, so that there is no increase
in disk storage. Clearly, you must monitor application server memory counters to ensure that this process
does not affect overall performance. Finally, there is now notification on file conversion.
WAS software boundaries
Like all services, there are recommended boundaries and thresholds that you should review for WAS, as
outlined in this table.
Limit Maximum value Limit type Notes
Input file size 512 MB Boundary Maximum file size that
can be processed by
WAS.
Frequency with
which to start
conversions
(minutes)
1 minute
(recommended)
15 minutes (default)
59 minutes (boundary)
Threshold Specifies WAS timer
job execution.
Number of
conversions to
start per
conversion
process
For PDF/XPS output
formats: 30 x M
For all other output
formats: 72 x M Where
M is the value of
Frequency with which
to start conversions
(minutes)
Threshold This setting affects the
throughput of WAS.
Higher values may
cause conversions jobs
to fail.
Conversion job
size
100,000 conversion
items
Supported A conversion job can
include multiple
conversion items,
which is a single file
conversion. These
items are transferred
to the application
server when a
conversion job
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
initiates. Large item
numbers increases
execution time and
transmission volumes.
Total active
conversion
processes
N-1, where N is the
number of cores on
each application server
Threshold A conversion can
consume a single
processing core, so do
not run more
processes than you
have cores available.
Leave a core free for
use by the conversion
timer job and
SharePoint.
WAS database size 2 million conversion
items
Supported WAS maintains a
persistent queue of
conversion items in a
database. Each
conversion request
generates one or more
records.
Co-authoring with SharePoint 2013
Co-authoring enables multiple users to collaborate
on a single document without impacting one
anothers changes or additions. It removes the
problems associated with multiple copies of
documents each being amended and then
merged, as well as the increased volumes of email
that such a process inevitably entails. In SharePoint
2013 and SharePoint Online, you can co-author
documents in Word, PowerPoint, Excel, and
OneNote Web Apps.
Word, PowerPoint, and Excel
Co-authoring is the next step from the check-in
and check-out process that users have become accustomed to with SharePoint over many iterations. For
the user, the experience is functionally seamless. Users can edit documents or presentations in Office 2013
products or Office Web Apps. The exception to this is Excel, where co-authoring is only supported in
Office Web Apps and not in the Office Excel 2013 application.
In Word 2013, PowerPoint 2013, or Word Web App a user is notified of changes made by other users. At
this point, the user can choose to refresh his or her view to see the updates or carry on, refreshing the
document later. PowerPoint Web App and Excel Web App automatically save the document so that views
are refreshed. SharePoint 2013 maintains a version history, so that users can roll back to a previous version
if required.
The Office Excel 2013 client application does not support co-authoring. It uses the Shared Workbook
feature to support non-real-time collaborative workbooks. These are stored on the local machine or a file
servers shared folder.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
OneNote
OneNote 2013 and OneNote Web App automatically synchronize edits, including edits made on the same
OneNote page; this provides near real-time co-authoring. The version management for notebooks is
provided by OneNote.
Co-authoring planning
Co-authoring requires the client applications or Office Web Apps necessary to support your user
population, as outlined earlier. As part of your planning for co-authoring, you must establish the
following:
Permissions. All authors must have edit permissions on co-authored documents.
Versioning. SharePoint provides both major and minor update versioning for all documents, except
for OneNote notebooks. In the case of OneNote, you should disable minor update versioning
because this conflicts with the integral OneNote synchronization and versioning functionality. You
must plan for the attributes of version management:
o Number of versions. Heavy co-authoring, particularly in OneNote environments, can generate a
large number of document versions. You should set a maximum number of versions to ensure
that you do not exceed capacity planning limits. You can establish a working level by monitoring
storage use. You set the number of versions in the Version Settings from the Library Settings
page for a document library.
o Versioning period. You can set the versioning periodhow often a new version is createdto
manage your versions. The shorter the period, the more regularly new versions are created. This
setting does not affect versioning of OneNote notebooks. This uses the
CoauthoringVersionPeriod property with a value set in minutes.
Maximum number of co-authors. You can set a maximum number of co-authors for Word 2010, Word
2013, Word Web App, PowerPoint 2010, PowerPoint 2013 and PowerPoint Web App documents by
using the CoauthoringMaxAuthors parameter. This limits the number of co-authors who can work
on a single document at the same time.
It is worth noting that checking out a document locks the document so that it cannot be co-authored.
This remains a useful feature, but if you want to provide a co-authoring environment you must not enable
the Require Check Out feature on the document library.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Configuring Project Sites
Scenario
In addition to replacing existing systems within Contoso, the companys directors want to use productivity
and collaboration features in SharePoint 2013 to improve project success rates. They hope that by better
engaging teams and by providing better visibility of project status they can engage the right people at
the right time to make projects more successful.
To support this goal, you have been charged with creating and configuring project sites, including the use
of social features to engage teams, and ensuring task aggregation to personal sites. You will investigate
the features available for engaging project teams ready to demonstrate the features to various teams in
the business. When you present the results to the business directors, you will explain that tasks can also be
aggregated to Microsoft Exchange, and therefore appear in Outlook, but that you have not yet
configured Exchange integration as there is a forthcoming global upgrade from Exchange 2010 to
Exchange 2013; tasks will be integrated into Exchange after the global upgrade. For this reason, you will
not include Exchange integration in this lab.
Objectives
Create Project sites.
Configure Project sites.
Configure social features to engage project teams.
Virtual Machine: 20332B-NYC-DC-06 and 20332B-NYC-SP-06
Password: Pa$$w0rd
Virtual Machine: 20332B-NYC-DB-06
User Name: jim@contoso.com
Password: Pa$$w0rd
Exercise 1: Creating Project Sites
Scenario
In this exercise, you will create a project site by using the Central Administration website.
1. Add a new managed path to the sharepoint.contoso.com web application
2. Use Central Administration to create a site collection in the sharepoint.contoso.com web application
Task 1: Add a new managed path to the sharepoint.contoso.com web application
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Pa$$w0rd.
On the Central Administration website, browse to the Web Applications Management page.
Add a managed path named projects to the sharepoint.contoso.com web application.
Task 2: Use Central Administration to create a site collection in the
sharepoint.contoso.com web application
Use the Central Administration website to create a new site collection in the
sharepoint.contoso.com web application with the following properties:
Property Setting
Title Project 1
URL http://sharepoint.contoso.com/project1/p1
Template Project Site
Primary Site Collection Administrator CONTOSO\Administrator

Results: After completing this exercise, you should have created a project site.
Exercise 2: Configuring Project Sites
Scenario
In this exercise, you will review the default project site. You will customize the layout and components on
the home page of the project site. You will also add some initial content to the project site.
1. Review the default project site
2. Add tasks to the project timeline
3. Customize the display of the project site
4. Add items to the project calendar
Task 1: Review the default project site
Open Internet Explorer and browse to http://sharepoint.contoso.com/projects/p1. Login as
Review the default project site. Notice that it includes a project summary, with a project timeline, a
document library, a task list, and a calendar.
Task 2: Add tasks to the project timeline
Add a new task to the task list. The task should be called Product Design. The task should start
today, and end in two weeks. The task should be assigned to Jim Corbin (jim@contoso.com).
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Add a new task to the task list. The task should be called Proof of Concept. The task should start one
week from today, and end in three weeks from today. The task should be assigned to Administrator
(administrator@contoso.com).
View the tasks in the Project Summary on the project site home page.
Add a new task to the task list from the project timeline. The task should be called Kick Off Meeting,
and the tasks should both start and end today. The task should be assigned to all members of the
Project 1 Members group.
Task 3: Customize the display of the project site
Edit the Proof of Concept task to display as a callout.
Remove the Get started with your site Web Part from the page.
Add a Calendar Web Part to the page. You should add the Calendar Web Part under the Project
Summary Web Part. (You may find it easier to minimize the Web Parts before reordering them after
you add the calendar web part).
Stop editing the page layout.
Task 4: Add items to the project calendar
Add a new event to the calendar. The event should be called Kick Off Meeting, it should be an all-
day event, and should be categorized as a Meeting.

Results: After completing this exercise, you should have customized and configured a project site.
Exercise 3: Engaging Project Teams
Scenario
In this exercise, you will use the social integration features to make a project site more engaging for team
members. You will follow sites and documents, and review the impact by using your My Site.
Finally, you will configure SharePoint to support task propagation from project sites to My Sites.
1. Add a document to the project documents library
2. Test the social integration features
3. Configure the SharePoint farm for task propagation
Task 1: Add a document to the project documents library
Upload the Project Outline.docx file from the E:\Mod6 folder to the Documents document library.
Task 2: Test the social integration features
Follow the Project Outline.docx document.
Browse to the Documents document library.
Add a note to the Documents document library note board with the message Added a project
outline document. I will add to this during out kick off meeting.
Follow the Project 1 project site.
Share the Project 1 project site with Jim Corbin (jim@contoso.com), Toni Poe
(toni@contoso.com), and Anat Kerry (anat@contoso.com).
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Use the Central Administration website to run the Contoso UPSA - Activity Feed Job timer job
immediately.
Browse to your My Site (http://mysites.contoso.com).
Verify that the Newsfeed includes messages which indicate you are now following the Project 1 site,
and the Project Outline.docx document.
Note: If the newsfeed displays the message We're still collecting the latest news. You
may see more if you try again a little later. you may need to reset the distributed cache by
running the following cmdlets in a SharePoint Management Shell instance:
Use-CacheCluster
Remove-SPDistributedCacheServiceInstance
Add-SPDistributedCacheServiceInstance
Restart-CacheCluster
After resetting the cache cluster, you may need to wait several minutes before the news feed
display posts correctly.
Add a new message to your newsfeed with the text @[Jim Corbin] I might be late for the
#kickoffmeeting.
Switch to the 20332B-NYC-DB-06 virtual machine. Log on as CONTOSO\Jim with the password
Pa$$w0rd.
Open Internet Explorer, and then browse to your My Site (http://mysites.contoso.com).
Log in with the user name CONTOSO\Jim and the password Pa$$w0rd.
On the Newsfeed page, view posts in which you were mentioned.
Verify that the message from Administrator appears in the list of posts.
Task 3: Configure the SharePoint farm for task propagation
View your task list. Verify that no tasks currently appear in your task list, and that a warning icon
appears next to the text which indicates when the task list was last updated.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Use the Central Administration website to create a new instance of the Work Management Service
Application service application with the following properties:
Property Setting
Name Contoso Work Management
Application Pool ContosoServices
Start the Work Management Service service.
In Internet Explorer, refresh the page. Verify that the Product Design task now appears in the task
list. You may need to wait while SharePoint retrieves your tasks for the first time. If after refreshing the
page SharePoint still indicates that there is a problem retrieving your tasks, wait for a few minutes and
then refresh the page.

Results: After completing this exercise, you should have used the social integration features on a project
site to make the site more engaging for team members.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Planning and Configuring Composite Solutions
A composite solution is a no-code solution developed by end users, using various SharePoint features as
building blocks, to meet a specific business need. Users are often the best designers of business solutions.
However, they may not have the programming skills to follow through the development of business
applications. SharePoint 2013 has enhanced the options for users to develop their own, no-code,
solutions. These solutions may use a variety of SharePoint services, such as Business Connectivity Services
(BCS) and PerformancePoint, and can integrate with Office 2013 applications.
Users can also use workflows, which are now based on Windows Azure functionality, to extend business
activity integration.
Lesson Objectives
Describe the function of composite solutions.
Explain how to integrate business data from external sources by using BCS.
Describe the use of Access Services and Access Apps in developing user solutions.
Describe the architecture of workflows in SharePoint 2013.
What Are Composite Solutions?
A composite solution is a code-free application,
usually created by a power user, which combines
the functionality of two or more existing facilities
to provide a business solution. The key part of this
description is that composites are usually
developed by power users, rather than
professional software developers. With SharePoint
2013, the composite solutions usually combine
business data or documents with the functionality
offered by SharePoint or other Microsoft Office
applications. The types of composites range from
a users webpage that uses Web Parts to a solution
that is used across an organization.
There are a number of benefits that an organization can accrue from using composites, including:
Increased user productivity based on existing applications. Composites do not use additional software
applications; users create them with the tools and data that they already have available to them.
Use of corporate data in personal solutions. Often users inadvertently create silos of information,
which are outside the control of IT services, which are not protected or subject to the necessary
business continuity standards. Composite solutions make it easier for users to consume line-of-
business data directly, rather than maintaining their own information silos.
Rapid solution deployment. Composites usually are not very complex application development
components, and they are made by the people, for the people. Therefore, there is not a development
chain that can take many months to complete. Composites are more like building blocks that users fit
together to build the solution that they need at that time.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Compliance with business governance. The data, and even the application components, are part of the
fabric of your business, so they are always under the control of the IT services department.
Supportability. The majority of composites are easy to support because they do not need coding at
the outset. Their infrastructure dependence also means that a good composite that could be made
even better with a little custom code can easily be extended under the management and support of
professional developers. Composites can be seen as the step between out-of-the-box functions and
coded development.
Composite example
As an example of a composite solution, consider an expenses claims system. A power user creates a
solution that is available to their team members that automatically calculates expenses payments based
on information in a SharePoint list. This is a simple calculation that may be displayed in a Web Part. This is
a quick solution, probably created in a users spare time, but it offers a consistent and managed solution
that is based on business data. It may be extended with an InfoPath form or an Excel spreadsheet to
become a more complex composite.
It uses standard user interfaces offered by SharePoint 2013 or an integrated application, provides a vehicle
for business logic, consumes corporate data, and is based on the organizations existing infrastructure. The
final point should be highlighted, as the common infrastructureSharePoint, security, and networking
means that the composite can readily be shared with other parts of an organization.
Composites components
The SharePoint services and features that are commonly associated with creating composite include:
Page customizations (Web Parts)
Workflows
SharePoint Designer 2013
Service applications
o InfoPath 2013 Services
o Business Connectivity Services
o Access Services
o Excel Services
o Visio Services
o PerformancePoint Services
Basic coding tools for more complex composites include:
JavaScript
Web Services
REST
Integration solutions for composites are often based on Microsoft Office 2013. Beyond the more obvious
Visio diagram integration, you may find simple efficiencies in the use of Document Information Panels
that integrate SharePoint data directly into the metadata for a Word document, or the creation of
dashboards that render corporate data into Excel Services. For more complex environments, you may
deploy solutions such as PowerPivot or Power View for users to design their own analysis solutions.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Using BCS Data in Composites
Business Connectivity Services (BCS) provides
secure access to line-of-business data sources that
are external to SharePoint 2013. This data access
means that users can extend the data functionality
of their composite solutions to include a rich
variety of business information. The read/write
options available within BCS mean that composite
solutions can go beyond simple reporting, to
include updating of data sources. Common
examples of composites that include BCS content
include integration with business applications such
as Microsoft Customer Relationship Manager
(CRM), mail solutions, such as Microsoft Exchange, and third-party applications, such as Enterprise
Resource Planning solutions.
Working with BCS data
There are three phases to incorporating BCS data into composite solutions:
Planning eternal data access. In this phase, you need to identify the data that needs to be surfaced to
satisfy the composites requirements and its security. You will also need to identify the external data
types that you need to define.
Integration with SharePoint. After you identify the external data, you need to surface this in
SharePoint 2013. Therefore, you may need to use any combination of the following SharePoint 2013
facilities, depending on the end-user toolset:
o External lists
o External data columns
o Business Data Web Parts
o Workflows
o Search result sets
o Apps
o Programmed components or solutions
Integration with Office. You may need to identify the non-SharePoint products that users want to
employ to surface data as a composite solution, such as Office Word or Office Excel.
For a SharePoint 2013 administrator, the key tasks are to manage access through the provision of
SharePoint components, such as external data types, and the management of permissions. This will almost
certainly include the configuration of the Secure Store Service to map credentials and streamline
authentication, which manages security issues based on the NTLM double-hop limitation. For on-premises
SharePoint 2013 environments, configuring the Secure Store Service is relatively straight forward, because
you control the entire SharePoint 2013 toolset. However, if you are supporting composite development in
SharePoint Online or hybrid environments, you must remember that you may have a restricted toolset, so
you can only connect to the following data sources:
WCF
Web Services
OData
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
SQL Server Azure
Access Services and Access Apps
Microsoft Access 2013 offers a number of
opportunities for power users to develop their
own business solutions that integrate corporate
data. To some extent, this is the reason for Access
Services; you can put an Access database into
SharePoint 2013. Modification of the database,
such as adding new tables or changing columns,
still takes place in Access 2013, but by publishing
the database through Access Services, you can
make the data available to other SharePoint 2013
users.
SharePoint 2013 creates a unique SQL Server
database for each Access app. This contrasts with the approach used in SharePoint 2010, in which Access
Services data was maintained in a single database. An Access Services app accesses content on a SQL
Server databasenot necessarily a SharePoint content databaseand enables you to render the data in a
SharePoint interface.
Configuring Access Services and Access Apps
To provision Access apps, you must have the following infrastructure in place:
o App Management Service. This enables you to install SharePoint apps from the Office
Marketplace and Corporate Catalog.
o Secure Store Service. This manages authentication and authorization for Access apps.
o Access Services. This allows user to view, edit, and work with Access Services databases in a
browser.
o Access Services 2010. This allows user to view, edit, and work with Access Services 2010 databases
in a browser.
o A dedicated site collection for Access apps. This is because each Access app requires a subsite.
Note: The Microsoft SharePoint Foundation Subscription Settings Service must be running.
Domain Name Services (DNS) domain name to provide a host name for the apps
DNS records:
o SQL Server 2012 instance
o Database Engine Services
o Full-Text and Semantic Extractions for Search
o SQL Management Tools feature (recommended)
o Client Tools Connectivity
o Security Mode = Mixed Mode (SQL Server and Windows authentication)
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Creating an Access app
You create an Access app from one of the available templates on the Access 2013 startup screen. You
must select the option to create a Custom web app and specify the URL for the target site.
The Access Services database is packaged as an app, which has its own site in the Access apps site
collection.
The Access objects that you create are stored as follows in the SQL Server database:
Tables as tables
Queries as views
Parameter queries as table-valued functions
Macros as triggers and stored procedures
Validation rules as check constraints
Views (HTML and JavaScript) as text in system tables
SharePoint 2013 Workflow Architecture
The SharePoint 2013 workflow architecture has
undergone some fundamental changes when
compared to SharePoint Server 2010. The redesign
is based on the need to extend the flexibility and
interoperability of workflows on the platform. The
new architecture is built around Workflow
Manager 1.0, a Windows Azure-based component
that is installed and managed independently from
the SharePoint server farm.
When you configure Workflow Manager, you
create a service application proxythe Workflow
Manager Client Service Application Proxyin
SharePoint. This allows SharePoint 2013 to interact with the Workflow Manager, rather than having the
workflow functionality as part of the SharePoint code, as was the case in SharePoint Server 2010.
Workflow Manager communicates with SharePoint 2013 using common protocols over the Windows
Azure service bus, with authentication provided by OAuth. The Workflow Manager Client is built on
Windows Workflow Foundation 4.0, rather than 3.x, as was previously the case. This makes workflow
available across both on-premise and online services.
The Workflow Manager manages workflow definitions and hosts the workflows execution processes.
SharePoint events that may trigger a workflow action, such the creation or update of an item, route to the
Workflow Manager on the Windows Azure service bus and are returned by way of the SharePoint REST
API. Although this may appear to be an academic change, it has fundamentally altered the functionality of
SharePoint 2013 workflows. Previously, the publisher of a workflow event and its consumer (subscriber)
were coupled. This meant that a workflow publisher had to have some knowledge of the consumer. Now
these are decoupled, so the publisher can simply initiate the trigger and leave it to the Workflow Manager
to manage messaging with the subscriber. Equally, the subscribers can receive messages without any
knowledge of the publisher. All of this lends itself to an always on approach to workflows so that the
infrastructure to direct workflows is assumed and the developer can focus on the workflows business
logic.
The workflow framework is delivered through SharePoint 2013, which maps the business processes for
SharePoint components, such as lists or tasks. It also stores the metadata associated with workflows.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To enable backward compatibility for organizations that have lots of SharePoint 2010 workflows, there is
SharePoint Workflow Interop. This enables SharePoint Server 2010 workflows to continue to execute in a
SharePoint 2013 implementation.
Note: For more information about the development framework of workflow interop for
SharePoint 2013, see Using workflow interop for SharePoint 2013 at
There are two major tools for developing workflows: SharePoint Designer 2013 and Visual Studio 2012.
SharePoint Designer 2013 is mostly regarded as an end-user, or power-user, tool. To streamline workflow
development, it ships with a number of features specifically designed to develop SharePoint workflows.
Visual Studio 2012 is intended for developers to create more complex, custom workflow interactions. You
can also integrate workflows with InfoPath 2013 and Visio 2013.
Installing and configuring Workflow Manager
To install Workflow Manager 1.0, you must run workflowmanager.exe. This opens a runtime window titled
Web Platform Installer 4.5. When you run this executable it either installs a new version of Workflow
Manager 1.0 if it is not already installed on the server, or it updates the installed version.
Note: To download Workflow Manager 1.0 (workflowmanager.exe), see the Workflow
Manager page in the Microsoft Download Center at
The installation process downloads and installs any pre-requisite software, such as .NET Framework, and
then it installs Workflow Manager. Depending on the software that needs to be installed, you may have to
reboot the system multiple times during this process.
The wizard provides three installation options:
Configure Workflow Manager with Default Settings (Recommended)
Configure Workflow Manager with Custom Settings
Join and Existing Workflow Manager Farm
The first two options install the Workflow Manager to predefined or personalized settings and then create
a workflow farm. The third option applies when you are installing on a new server but have an existing
workflow farm configuration. You can only configure one server at a time.
If you install using the default settings, you are prompted for a SQL Server instance to host the databases,
a service account, and a certificate generation key.
The custom installation process requests information regarding the associated SQL Server instances and
database names for the Farm, Instance, and Resource Management databases. You must also configure
the following:
Service account
Certificates, which may be auto-generated
Port, which defaults to 12290
Admin Group
If you join an existing farm, you must provide the SQL Server instance for the Workflow Manager Farm
Management database and the Service Bus Farm Management database.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring Workflow
Scenario
Many of the processes used in Contoso can easily be modeled as workflows. Currently, as each step is
completed in one of these workflows, the project manager will be sent an email message. He or she will
then check what the next step is and send an email message to the relevant person. This is very simple but
also very time consuming, and project managers in Contoso struggle to complete their other work as a
result.
Your job is to investigate how you can implement these workflows in SharePoint, which could reduce the
workload on project managers, enabling them to focus on delivering a successful project rather than
focusing on facilitating common procedures.
Objectives
Configure Windows Azure Workflow and SharePoint Workflow Services.
Create and test a SharePoint 2013 workflow.
Virtual Machine: 20332B-NYC-DC-06, 20332B-DB-06, and 20332B-NYC-SP-06
Password: Pa$$w0rd
Exercise 1: Configuring Windows Azure Workflow and SharePoint
Workflow Services
Scenario
In this exercise, you will configure Windows Azure Workflow. You will make necessary changes to DNS,
create service accounts, and then use the configuration wizard to complete the setup.
Finally, you will use PowerShell to associate the Workflow Services instance with a SharePoint project site.
1. Configure the DNS settings for workflow services
2. Create a service account for workflow services
3. Disable loopback checking for the workflow.contoso.com domain
4. Use the Workflow Configuration Wizard to configure workflow services
5. Use PowerShell to associate the workflow service with the project site
Task 1: Configure the DNS settings for workflow services
Open DNS Manager.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
Name Workflow
Close DNS Manager.
Task 2: Create a service account for workflow services
Property Setting
Full name Workflow Services
UPN logon workflowservices@contoso.com
SAM Account Name logon CONTOSO\workflowservices
Password Pa$$w0rd
Close Active Directory Administrative Center.
Add the Workflow Services account to the IIS_IUSRS local security group on the 20332B-NYC-SP-06
server.
Grant the Workflow Services account read and write permissions on the Windows temporary
directory.
Task 3: Disable loopback checking for the workflow.contoso.com domain
In the registry, disable loopback checking for the workflow.contoso.com domain to enable you to
visit the site on the SharePoint server.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 4: Use the Workflow Configuration Wizard to configure workflow services
Use the Workflow Manager Configuration Wizard to configure Workflow Manager with the following
properties and settings:
Property Setting
SQL Server instance NYC-DB1
User ID for services workflowservices@contoso.com
Allow workflow management over HTTP Allowed
Certificate generation key Pa$$w0rd
Note: When you type the user name, you should use the fully qualified user name.
Close the Workflow Manager Configuration Wizard.
Task 5: Use PowerShell to associate the workflow service with the project site
1. Open a SharePoint 2013 Management Shell.
2. Use the Register-SPWorkflowService cmdlet to register the http://workflow.contoso.com:12291
workflow service instance with the http://sharepoint.contoso.com/projects/p1 project site. You
should specify that OAuth over HTTP is allowed.
3. Close the command window.

Results: After completing this exercise, you should have configured Windows Azure Workflow, and
associated the Workflow Services instance with a SharePoint project site.
Exercise 2: Creating and Testing a Workflow
Scenario
In this exercise, you will use SharePoint Designer to create a SharePoint 2013 workflow. You will then test
that workflow on a project site.
1. Use SharePoint Designer to create a new workflow
2. Test the workflow
Task 1: Use SharePoint Designer to create a new workflow
Open SharePoint Designer.
In SharePoint Designer, open the http://sharepoint.contoso.com/projects/p1 site. Connect to the
site as administrator, with the password Pa$$w0rd.
Add a new workflow named Task Complete to the Tasks list. The workflow should use the
SharePoint 2013 Workflow platform.
Add steps to the workflow to write the message Task complete to the workflow history list when the
Task Status for the current item is Completed.
Configure the workflow to run automatically whenever an item in the list is changed, or whenever an
item is added to the list.
Publish the workflow.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 2: Test the workflow
In Internet Explorer, browse to http://sharepoint.contoso.com/projects.p1. Log on as
administrator, with the password Pa$$w0rd.
Set the % Complete field to 100% for the Kick Off Meeting task.
Open the history list for the Task Complete workflow.
Note: You can use the links in SharePoint Designer to easily locate and open the history list for a
workflow.
Verify that the Workflow History list contains one item, with a Description of Task completed.
Close all open windows.

Results: After completing this exercise, you should have used SharePoint Designer to create a SharePoint
2013 workflow.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Collaboration remains a cornerstone of the success of SharePoint Products and Technologies. SharePoint
2013 builds on the success of previous versions, by extending functionality and embracing integration
opportunities with external services. This is an important feature of collaborative work, because SharePoint
2013 benefits from the development of other platforms to extend its own functionality. This is highlighted
by the development of Office Web Apps as a separate server platform, rather than a service application, as
was the case in SharePoint 2010.
In this module, you have seen how SharePoint 2013 has improved user productivity and collaboration
options through seamless integration with external application platforms, such as Exchange 2013, Project
Server 2013, and Windows Azure Workflow. You have also seen how to configure collaborative options,
such as workflow and Windows Web Apps.
Beyond administrator provisioned functionality, you have also seen how composites and apps can enable
users to develop their own business solutions.
Review Question(s)
Test Your Knowledge
Question
Which protocol does SharePoint 2013 use to request data from Exchange 2013 and
other server products?

OData
OAuth
REST
Kerberos
NTLM

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Test Your Knowledge
Question
Which of the following is a recommendation for using co-authoring with OneNote
notebooks?

Disable co-authoring for all OneNote notebooks.
Disable major and minor versioning on OneNote notebooks.
Disable minor versioning on OneNote notebooks.
Require check out on OneNote notebooks.
Limit the number of concurrent authors to five for OneNote notebooks.
Statement Answer
In SharePoint 2013, each Access app has a unique
SQL Server database on the database server.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
7-1
Module 7
Planning and Configuring Business Intelligence
Contents:
Module Overview 7-1
Lesson 1: Planning for Business Intelligence 7-2
Lesson 2: Planning, Deploying, and Managing Business Intelligence Services 7-10
Lab A: Configuring Excel Services 7-22
Lesson 3: Planning and Configuring Advanced Analysis Tools 7-26
Lab B: Configuring PowerPivot and Power View for SharePoint 7-33

Module Overview
Business intelligence (BI) continues to be an important area for large enterprise organizations. The key to
successful BI is the ability to integrate the components that deliver the right information, to the right
people, at the right time. Microsoft SharePoint Server 2013 Enterprise Edition provides a range of
integrated solutions that enable both users and administrators across an organization to develop BI
solutions to fit their business requirements. These BI tools extend beyond SharePoint to provide consistent
information management from personal data analysis environments, which use Microsoft Excel, through
to departmental or organizational data repositories, which use SQL Server Reporting Services (SSRS) and
SQL Server Analysis Services (SSAS).
In this module, you will see how SharePoint 2013 can deliver BI solutions for your business.
Objectives
Explain the SharePoint BI architecture, its components, and how to identify BI opportunities in your
organization.
Describe how to plan, deploy, and manage the core SharePoint 2013 BI services.
Describe the advanced BI options available with SharePoint 2013 and Microsoft SQL Server 2012.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
7-2 Planning and Configuring Business Intelligence
Lesson 1
Planning for Business Intelligence
BI is concerned with streamlining business decision-making by providing high-quality source information
in easily digestible forms. It is important to understand the scenarios where you can deliver the most
business benefit to users with the components available to you. You also need to understand how your BI
solutions fit with your IT infrastructurehow it will affect environment performance and how it maintains
corporate security.
In this lesson, you will see what BI can offer your organization and how it integrates with your SharePoint
2013 security and service architectures.
Lesson Objectives
Describe the different types of BI that are commonly used in business organizations.
List the SharePoint 2013 BI components.
Describe the SharePoint BI architecture and important optimization components.
Explain how BI fits into the SharePoint security model.
An Overview of Business Intelligence
Business intelligence (BI) is an enabler to business
decision-making; the goal is to get the right
information to the right people, in a timely
manner. You must ensure that you understand the
business requirements for your organization and
can interpret them. In this way, you can effectively
map them against SharePoint 2013 BI solutions.
There are three key types of BI:
Self-service personal BI
BI for a business community
BI for an organization.
Self-service personal BI
The goal of self-service personal BI is to ensure that users can provide their own BI services. Usually, it
involves personal productivity facilities such as Microsoft Office, in addition to back-end data sources such
as SQL Server or other database software. Users, usually information workers, can format and analyze data
to generate business logic models that help them make decisions. This involves little or no ongoing effort
from the IT department.
Business intelligence for the community
The goal of BI for the community is the ability to analyze data in a collaborative environment. The aim is
to create teams who can combine effort and therefore produce more complex or better informed
business models. This requires a more sophisticated approach to business systems, but it has the major
benefit of eradicating silos of business information that are outside the control of the business.
Eradicating such silos is the most common goal of BI implementations. Therefore, a solution architect
must identify opportunities for teams to share common information to make corporate decisions. A good
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
example of how this extends personal BI is exhibited in the difference between Excel 2013 and Excel
Services. Excel 2013 provides personal productivity, whereas Excel Services provides a truly collaborative
environment.
This approach creates a homogeneous data environment where both local information, such as Excel
workbooks, and corporate data are used in a coherent manner across an organization. This usually
involves greater input from IT services through the provision of collaborative tools, but the power of how
to use information remains with information worker teams.
Organizational business intelligence
Organizational BI extends the use of business data beyond individual or team usage and creates a
strategic model for business operation. The company goals are reflected in the use of data, with BI tools
generating pre-analyzed output that aligns with organizational goals. As a superset of the model of BI for
the community, information workers can continue to collaborate on data analysis, but work is placed in
the context of the overarching business strategy. This model commonly uses key performance indicators
(KPIs), dashboards, and scorecards to publish achievements or targets. This model has the added benefit
of enforcing governance across the business at a day-to-day level.
This approach often requires a lot of architectural and developmental effort from the IT department,
which is based on business requirements from BI stakeholders and the organizations management team.
Identifying core BI opportunities
As a BI solution designer, it is essential that you can reconcile business requirements with opportunities
for the use of BI. This does not mean that you must use BI; rather, you must recognize when BI, and
specifically the SharePoint 2013 BI toolset, is appropriate to your design. Here are some examples of
requirements that should trigger a review of SharePoint 2013 BI components:
Delivering user autonomy. If business stakeholders and users identify self-service as a key requirement,
you should investigate their goals and reasons for this. The goal should be to enable users to more
quickly generate business solutions through closer collaboration and accessibility to back-end
corporate data. You should avoid the need to involve the IT department in protracted systems design
projects. One of the key benefits of BI is that it enables information workers to have structured and
managed access to corporate information when they need it. Be careful of the goal of unilateral
independence from the IT department; sometimes users feel that the IT department is a blocker to BI
rather than an enabler.
Sharing Excel workbooks through browsers. The ability to work collaboratively on Excel workbooks has
previously involved saving a workbook on a shared drive so that others can access it. This is still
possible with SharePoint 2013, and it has the obvious advantages of version control and check-in and
check-out from document libraries. The key benefit of SharePoint 2013 Excel Services is that it
enables users to view and interact with Excel workbooks through a browser. This browser
functionality, together with Web Part visualization, means that users can now work collaboratively
wherever they are and without the need to have the client license for Excel 2013.
Deploying dashboards. Business dashboards enable you to deploy BI information to both BI and non-
BI users through an onscreen Web Part. You should review requirements to identify where
stakeholders also need information delivered directly to users, rather than just for their own analysis.
Deploying status indicators and KPIs. Status indicators and KPIs give information workers a current
view of performance. This is only deliverable with a connected system because you must have access
to back-end data sources to ensure that the status reflects current business achievements.
Generating business scorecards. Business scorecards provide an overall view of status indicators. They
are modeled after the business, not the data, to reflect goals. These may be included as part of a
dashboard.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Enabling business process visualization. For environments such as process industries that map complex
processes in Microsoft Visio 2013, you should investigate whether these are required just for Visio
users or for a wider audience. This is especially the case when Visio diagrams are connected to back-
end data systems that monitor or manage business processes.
Creating a central reporting location. Identify whether users want a centralized reporting environment.
Deploying single instances of reports minimizes the effort that is wasted in user generation of
multiple versions of the same information.
Providing central management for external data connections. Assess the need for central management
of connections to back-end business data sources. If your environment has a range of complex data
access requirements, you should review the opportunities to create a managed set of data
connections that are made available to users. This minimizes duplication of effort and makes solution
deployment faster.
Discussion: What Is the Role of Business Intelligence in Your Organization?
BI is often viewed as a large enterprise solution,
but all organizations need current and accurate
data to ensure that staff can make well-informed
decisions, based on the correct information. Every
business, from the smallest to the largest, uses
some BI components, whether that is an Excel
spreadsheet or a SQL Server database.
In this discussion, describe the BI infrastructure in
your organization and how SharePoint products
and technologies affect BI delivery.
SharePoint 2013 Business Intelligence Overview
SharePoint 2013 Enterprise Edition has a number
of key service applications that focus on delivering
BI to users in a wide variety of ways. Whether you
need to share workbooks, develop dashboards
and scorecards, integrate process management, or
report and analyze complex business information,
SharePoint 2013 has a proven range of solutions
to business challenges. These include:
Excel Services. The Excel Services service
application enables users to share and view
Excel workbooks. It also enables data-
connected Excel workbooks and worksheets
to be refreshed and updated from a variety of data sources.
PerformancePoint Services. PerformancePoint Services delivers community or organizational BI
through its ability to visualize performance management, KPIs, and results information.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Visio Graphics Service. The Visio Graphics Service service application enables users to share and view
Visio diagrams created in Visio. The service application also enables data-connected Visio 2013
diagrams to be refreshed and updated from different data sources.
SQL Server Reporting Services for SharePoint (SSRS). SSRS integrates SharePoint 2013 closely with SQL
Server 2012 to provide a range of tools and services to enable you to provide reports for users in an
organization.
PowerPivot for SharePoint. PowerPivot for SharePoint is a collection of services that integrate with
SharePoint 2013 to enable users to browse and interact with PowerPivot workbooks through the
browser window. In an organization that uses PowerPivot for Excel to create workbooks that contain
analytical data, you need to have PowerPivot for SharePoint to access that data in the server
environment.
Power View for SharePoint. Power View is a Silverlight application that is built on SQL Server 2012
Reporting Services and PowerPivot for SharePoint 2013. Power View enables users to interactively
explore data and create reports that have a strong visual impact. Power View is also available as an
add-in for Excel 2013 (client) so users can create Power View charts in workbooks.
Business Intelligence Platform: Architecture and Optimization
The BI service applications for SharePoint 2013 are
only available in the Enterprise Edition of the
product. The SharePoint 2013 BI architecture is
based primarily on service applicationsExcel
Services, PerformancePoint Services, Visio Graphics
Service, and SSRS. There are add-ins options in the
form of PowerPivot and Power View, which
provide additional functionality. When you
implement PowerPivot, it is a service application,
but it is tightly integrated with Excel Services. The
basic architecture for SharePoint 2013 BI reflects
the architecture for provision of enterprise service
applications; however, you should note that none of the BI service application can be federated in a cross-
farm sharing configuration. Like with all SharePoint topology design options, central to an effective BI
solution deployment is the ability to optimize your environment performance.
Your focus in planning and deploying a well-performing BI environment is on the resources available to
the physical server on which a service instancethe bits of a service applicationare installed and the
network bandwidth that these service applications can consume.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Excel Services architecture
Excel Services is a multifaceted service application. This means that there are several components that
integrate to deliver the Excel Services functionality. The components are described in the following table.
Component Description
Excel Calculation Services The service that is responsible for loading
Excel workbooks from trusted file locations,
executing any workbook calculations,
calling any user-defined functions, and
refreshing workbook references to external
data sources.
It also creates, maintains, and closes user
sessions to the service. You can configure it
to cache open Excel workbooks,
calculations, and data query results for
improved performance.
Excel Web Services The developer interface to Excel Services.
You can create applications that call the
service to perform custom tasks on a
workbook.
You can also use Excel Web Services to
incorporate server-based workbook logic
into an application.
Excel Web Access The component of Excel Services that is
visible to information workers. This renders
Excel workbook information into a web
browser.
This division of functionality will affect the physical design of your Excel Services implementation, because
you will need to define the capabilities of both application and web front-end (WFE) servers. Excel
Services provides all of the visualization and computational analysis functionality that you usually expect
to deliver through a personal computer. Your SharePoint 2013 servers deliver these loads, so you must be
sure that you understand the loading effort that is involved. To do this, you must review the number, size,
and complexity of the workbooks that you expect to manage in Excel Services. These are highly subjective
metrics, so it is important that you pilot any environment and assess the performance of Excel Services for
users.
The output from Excel Services render in a browser on a client system, so there is no concern about client
performance.
BI services optimization
All service applications consume server resources, so sizing your environment, piloting your deployment,
and monitoring both the pilot and the final implementation are essential. This is the case for all service
applications, but it may be more important for the BI services because they generally perform a lot of
calculations, on application servers, and rendering, on WFE servers. This means that you need to assess the
number of BI documentsExcel workbooks and Visio diagramsthat you need to store and their
complexity.
The three key performance areas to assess and monitor are:
Processor and memory. Large and complex Excel workbooks are processor-intensive applications, so
you may find it fruitful to dedicate a server that has powerful processing capabilities as a dedicated
Excel Services server. This high processing requirement also makes it preferable to dedicate a server
to Excel Services, rather than share the hardware platform with other service applications. You should
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
also plan for high-performance servers for PowerPivot because of the long-running queries that are
characteristic of PowerPivot processing. The resource loading will be on the SSRS instance, so you
should monitor the physical system that hosts this new instance. The minimum specification should
include a 64-bit, dual-core processor and 16 GB of RAM, but you should review performance metrics
both during the design phase and as a component of you regular farm monitoring schedule.
Storage. All content is stored in SharePoint 2013 databases. Service application metadata is stored in
the instance service application database. Files can become very large, particularly in the case of
PowerPivot. You should review versioning for all large files to ensure capacity availability.
Networking. There is often a good deal of network traffic associated with BI service applications. This
is the case, not only because of the application server to WFE traffic, but also because there is often
connectivity to external line-of-business data sources. This may be eased by the use of caching
options on WFE servers. With PowerPivot queries, for example, data transfer speed can be an issue.
Very large workbooks of 1 GB can take longer than 10 seconds to load over a 100-Mbps network.
This time may be even longer during a save action because SharePoint is optimized for download.
PowerPivot servers use a file-caching methodology to reduce file reloads, but you should specifically
monitor network traffic and query performance.
Planning Business Intelligence Security
When you are designing a BI deployment strategy
for SharePoint 2013, you must ensure that you
look at how your organization manages data, in
addition to matching BI tools to requirements.
Most companies have an overarching BI strategy,
which includes elements such as data compliance
and security. For your design to succeed, you must
fit the SharePoint 2013 solutions into this strategy.
Organizational compliance
The security component requires that you
understand the company-wide standards for
security, such as:
Protocols. Which security protocols (HTTP, HTTPS, and so on) are used in your organization and does
SharePoint 2013 support them?
Authentication. Does your organization want to implement a single sign-on (SSO) approach, with
authentication transferred through a given methodology between different platforms?
Management. How does your environment manage personal credentials?
Security integration
From a systems management perspective, it is important to aggregate the security mechanisms of various
platforms. Each is likely to have its own implementation of data security, so you must understand which
platforms and methodologies can integrate with SharePoint 2013. You can deliver a range of security and
authentication implementations in SharePoint 2013, such as classic or claims. You must plan to implement
the correct security implementation for your web applications.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Seamless user experience
Your users employ various systems, so they almost certainly want to minimize the need for multiple logon
credentials. This is critical for a BI implementation because the goal is to provide a seamless flow of
information and authentication. SharePoint 2013 delivers claims-based security and the Secure Store
Service, which enables you to provide security accreditation across systems without intervention from
users in the form of additional logons.
Central control
In your BI plan, you must also establish the responsibilities of IT and deployed administration control of
security. SharePoint security is, by default, centralized, which offers coordinated security management.
You can also delegate security administration to departmental groups to minimize IT intervention and
maximize effective response to users.
Business Connectivity Services security planning
The security architecture of Business Connectivity Services (BCS) is primarily involved in integrating
authentication with external systems. BCS is designed to integrate with external data sources, which
means that you must ensure that you can pass authentication credentials from the user to the external
platform. The two methods of authentication that are available in BCS are:
Claims-based authentication.
Credentials-based authentication.
Authentication of BCS access with claims
If you are planning for SharePoint 2013 BCS with a claims-aware data source, you may want to enable
your web application for claims-based authentication. For BCS authentication, your solution uses the
SharePoint 2013 Security Token Service (STS). This service is preconfigured on a farm and authenticates
users or functions, such as a web service, to SharePoint. The service is a broker for SharePoint 2013 and
supports multiple authentication providers for applications based on both ASP.NET and Windows
Communication Foundation (WCF).
The process for claims-based authentication is as follows:
1. The user accesses an application that is configured for claims authentication, such as an external list.
The list access triggers an authentication request.
2. The list requests a security token from the STS.
3. The STS issues a token that contains a set of claims based on the user identity, and a target
application identifier, which is returned to the list.
4. The list passes the security token to the Secure Store Service.
5. The Secure Store Service reads the user information and sends credentials to the external data source.
6. The external source reviews the credentials and, if the claims are appropriate, sends the data to
update the list.
Authentication of BCS access with credentials
BCS supports the following credential authentication options:
Windows authentication:
o Windows Challenge/Response (NTLM)
o Microsoft Negotiate
Authentication other than Windows:
o Forms-based
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Digest
o Basic
Authentication modes
You must ensure that application developers are aware of the options for authenticating data access from
the BCS. You must associate each with an authentication mode, which is associated with an external
content type. There are two methods of passing this information to the target data source:
Pass the credentials directly to the target.
Map the credentials to an account in the Secure Store Service.
The authentication modes that are available include:
PassThrough. This passes the credentials of the logged-on user to the external system, which means
that the user credentials must exist on the target system.
RevertToSelf. This maps the user credentials to the BCS application pool account and sends those
credentials to the target system.
WindowsCredentials. This can be used for both external web services and database access. It uses a
Secure Store Service to map the users credentials to a set of Windows credentials on the external
system.
Credentials. This can be used for external web services. It uses the Secure Store Service to map the
users credentials to a set of credentials that a source other than Windows supplies. These must be
known to the target system, which uses a basic or digest authentication.
RdbCredentials. This can be used for external database access. It uses the Secure Store Service to map
the users credentials to a set of credentials that a source other than Windows supplies. These must be
known to the target system, which uses a basic or digest authentication.
You should plan to use the latter two options with Secure Sockets Layer (SSL) or IPSec security protocols.
Permissions
You can associate BCS permissions with an individual account, group account, or claim with one or more
permission levels on an object in a metadata store. When you plan a permissions strategy, you should give
specific permissions to each user or group that needs it, in accordance with the principle of least privilege.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Planning, Deploying, and Managing Business Intelligence
Services
The three core SharePoint 2013 BI service applications are Excel Services, PerformancePoint Services, and
the Visio Graphics Service. Although they are separate service applications, they can integrate to deliver
seamless data provision for business users from a single working environment.
In this lesson, you will review the key elements of planning, deploying, and managing each of these
solutions.
Lesson Objectives
Explain the key components in planning, deploying, and managing Excel Services.
Describe the process for deploying and managing Excel Services.
Describe the key components in planning, deploying, and managing PerformancePoint Services.
Describe the key components in planning, deploying, and managing the Visio Graphics Service.
Planning Excel Services
Excel is arguably the most widely used personal
data analysis tool in the business world, so it is
hardly surprising that Excel Services was the first BI
tool integrated into SharePoint products and
technologies. If you are planning to use Excel
Services as part of your BI strategy, it is important
that you understand what you are getting so that
you can match it to your users requirements.
You can regard Excel Services as the mass
reporting version of Excel 2013. Excel Services
makes it simple to use, share, secure, and manage
Excel 2013 workbooks as interactive reports in a
consistent way throughout the enterprise. One of Excel Services most important features is that it renders
Excel workbooks through a browser, although it does not provide as rich an analysis environment as the
Excel 2013 client. Excel Services is not a multiuser version of Excel 2013; users can interact with workbooks,
but they cannot create new ones in Excel Services. This is an important distinction and may not be obvious
to users. A key advantage is the ability to store a workbook in a central location and make it available to
many users. You can also use Excel Services to create dashboards, which reflect current workbook statistics
or metrics directly to a users webpage.
Users often have complex business logic in Excel 2013 workbooks. In SharePoint 2013, you can access this
business logic programmatically through a web servicebased interface. Users would be unlikely to make
such a request, so you need to identify where key business logic is held. You may find that business
analysts are more attuned to this type of business solution.
Many users, particularly those in financial services, are comfortable with the traditional spreadsheet
reporting layout. You can use Excel Services to generate reports to include BI information, or any other
data that you use in Excel Services.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
New features in Excel Services
There are several enhancements and new features in Excel Services, which include:
Data exploration improvements. You can now configure Excel Services reports to use SQL Server
Analysis Services or PowerPivot data.
Field list and field well support. This enhances the ability to view and change which items are displayed
in rows, columns, values, and filters in PivotChart reports and PivotTable reports.
Calculated measures and members. You can now use calculated measures and calculated members
created in Office Excel.
Enhanced timeline controls. Excel Services now supports timeline controls.
Application BI Servers. You can configure Excel Services access to SSAS servers.
Data connectivity with Excel Services
Excel Services can use embedded and linked connections to external data sources. An embedded
connection is stored in the workbook, whereas link connections are stored in external Office Data
Connection (ODC) files, which are stored in a trusted data connection library on the same farm as the
Excel workbook. It is a good idea to centralize ODC file storage to maintain security and to provide a
central resource pool for other services that also use trusted connections, such as the Visio Graphics
Service. Because the content of an ODC file is plain text, this will also make it easier to manage all content
security.
Additional Reading: For more information about adding and configuring a trusted file
location, see Manage Excel Services trusted file locations (SharePoint Server 2013) at
For more information about managing trusted data connection libraries, see Manage Excel
Services trusted data connection libraries (SharePoint Server 2013) at
There are advantages and disadvantages in both the embedded and links connection approaches, and
you must select the best option for individual cases in your environment. A brief review shows that
embedded connections are neater, because all the information is held on the Excel worksheet and are
relatively easy for users, rather than administrators, to create. However, if all the information is embedded
in individual files, changes have to be made to all affected files when a source changes. Link connections
are more complex to create and may need an administrator to create and configure the components, but
they can be shared across multiple files and users. This means that a single change can be made to a
connection file when a source location changes, so it is easier to plan updates. Generally, enterprise
solutions use linked connections, with embedded connections for small-scale or individual solutions.
Unattended service accounts
To streamline data access, you can configure an unattended service account for Excel Services. This
enables you to map all users to a single set of credentials that have permissions to the target data. For
security purposes, the unattended service account should be a Windows domain account created with
least-privilege. The service impersonates this account to connect to a target data source.
The unattended service account is used when:
An ODC file specifies the use of the unattended service.
An embedded data connection specifies the unattended service account.
Using SQL credentials that are stored in a Secure Store target application.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
If you work in an organization that needs to be highly secure, you may choose not to implement an
unattended service account. Its advantage is that it is quick to set up and requires little maintenance.
Unless you are using Kerberos, you must configure an unattended service account. This is because NT LAN
Manager (NTLM) authentication will fail due to the double-hop limitation.
Additional Reading: For more information about the double-hop limitation in NTLM, see
Configure a SharePoint Server 2010 farm for business intelligence by using NTLM at
Unattended service accounts are used in other SharePoint 2013 BI service applications, including
PerformancePoint Services and Visio Graphics Service.
Planning authentication for data connectivity
For access authentication to external data sources, Excel Services can use any of the following options:
SQL Server Analysis Services (SSAS)
o Windows authentication (integrated security)
Constrained Kerberos Delegation
Secure Store using Unattended Service Account
o EffectiveUserName connection string property
SQL Server
o Windows authentication (integrated security)
Constrained Kerberos Delegation
Secure Store using Unattended Service Account
o SQL Server Authentication
Custom data providers
o Data source specific configuration, typically providing a user-name and password stored in a
connection string.
Note: Note that the connectivity options available in Excel Services are not the same as
those in Excel 2013. For example, you cannot connect to Access databases or text files.
The selection of the most appropriate authentication method depends on the level of security you require
and the amount of administrative effort you want to expend. For example, by using the unattended
service account, you will minimize administrator configuration, but you will not be able to determine who
has access to a data source. Alternatively, Kerberos delegation needs a higher degree of administrator
setup, but it will provide per-access auditing. Note that the new EffectiveUserName option, where the
users domain user name is passed to Analysis Services data sources, is only available for SSAS.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Deploying and Managing Excel Services
There are a number of steps to deploying and
configuring Excel Services. The configuration
elements, such as configuring Global Settings and
trusted data providers, must be based on effective
business requirements gathering. The service must
be installed and started on a server to undertake
any service application configuration.
The key steps are as follows:
1. Configure the Service Application. This step
involves:
a. The registration of the managed user
account.
b. Provision of database access to the managed user account.
c. Starting Excel Calculation Services.
d. Creation of an Excel Services service application.
2. Configure Global Settings. The Excel Services global settings configure service functions, such as:
a. Security.
b. Load Balancing.
c. Memory use.
d. Workbook caching.
3. Configure trusted file locations. These locations specify from where enabled workbooks can be loaded.
4. Configure trusted data providers. These define the data providers from which Excel Services can load
data. They provide:
a. A database type, such as OLE DB, ODBC, and ODBC DSN for Object Linking and Embedding,
Open Database Connectivity, and Open Database Connectivity with Data Source Name,
respectively.
b. An access protocol.
5. Configure trusted data connection libraries. This step specifies the location for the data connections
used by Excel Services, and possibly other BI service applications.
All of these steps can be completed from the Central Administration website of by using Windows
PowerShell cmdlets. There are more than 20 cmdlets available for configuring or managing Excel Services.
For the preceding steps, the cmdlets are:
1. New-SPExcelServiceApplication. Creates a new Excel Service service application instance.
2. Set-SPExcelServiceApplication. Sets global properties for the service application.
3. New-SPExcelFileLocation. Defines trusted file locations.
4. New-SPExcelDataProvider. Defines trusted data providers.
5. New-SPExcelDataConnectionLibrary. Defines the data connection library.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Additional Reading: For more information about Excel Services Windows PowerShell
cmdlets, see Excel Services cmdlets in SharePoint Server 2013 at
Planning PerformancePoint Services
PerformancePoint Services is available with
SharePoint 2013 Enterprise Edition and is designed
for the delivery of community or organizational BI.
The features and tools that are associated with
PerformancePoint Services focus on this sector of
the BI marketplace, rather than on personal
productivity. This should strongly influence your
design for BI.
You must focus on business requirements that
specify the need for performance management,
KPIs, and results alignment. The visualization and
analysis functions of PerformancePoint Services
can meet such requirements.
PerformancePoint Services uses SharePoint Server authorization groups and permissions, so you must plan
access to these groups:
Farm Administrator. To edit dashboard items, this role needs at least contributor permissions on
content lists (or list items) and data source libraries (or library items).
Site Collection Administrator. To edit dashboard items, this role needs at least contributor permissions
on data source libraries (or library items).
Site Administrator or List and Document Library Contributor. To edit dashboard items, this role needs
at least contributor permissions on content lists (or list items) and data source libraries (or library
items).
New and changed features in PerformancePoint Services
Although there have been no changes to the basic PerformancePoint architecture. some new features
have been added and some existing features have been updated. The primary changes include:
Dashboard migration. You can now copy dashboards to other users, servers, or site collections. This
also enables you to migrate single items and content, by using Windows PowerShell cmdlets.
Filter enhancements and filter search. The user experience is enhanced by allowing users to view and
manage filters.
BI Center update. Although the BI Center is not a PerformancePoint Services feature, it has been
updated to improve the user experience.
Support for Analysis Services Effective User. This new feature eliminates the need for Kerberos
delegation when per-user identity authentication is used for Analysis Services data sources. This uses
the EffectiveUserName property rather than the current user.
PerformancePoint support on iPad. PerformancePoint dashboards are available on the iPad browser.
PerformancePoint architecture
PerformancePoint Services is installed on a SharePoint Servercommonly referred to as an application
serverwhere the application service instance is configured to provide service access and access to data
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
sources, which may be either internal or external. A WFE server performs rendering through Web Parts or
other functions, depending on the data source connections. These data sources may exist within the
SharePoint farm, but they may be external data repositories.
If your organization is a heavy user of PerformancePoint Services, you may need to deploy multiple
service application instances or multiple WFE. Complex dashboards, such as those that provision external
data source access, can consume large amounts of processing and memory resources on application
servers, so you should pilot and then monitor your PerformancePoint environment.
There are a number of service application settings that can affect performance of your PerformancePoint
environment. These include:
Cache. You can cache items and specify the time for these to remain in the cache.
Data Sources. You can limit the time period that the service waits for a response to a query before it is
canceled.
Filters. You can set the time period to retain user-selected filter values before these are cleared.
Show Details. You can set a limit on the number of rows returned when a user selects the Show
Details option.
Decomposition Tree. You can set the maximum number of items returned to the decomposition tree
visualization. This is set on a per-level basis.
Additionally, there are software boundaries that you cannot exceed when running PerformancePoint
Services. The following table lists these recommended limits for usage.
Cells 1,000,000 per
query on Excel
Services data
source
Boundary A scorecard can call up to
1,000,000 cells per query from
an Excel Services data source.
Columns and
rows
15 columns by
60,000 rows
Threshold This specifies the number of
columns and rows that can be
rendered by a dashboard that
uses an Excel workbook as a
data source. This may change
based on rows vs. columns.
Query on a
SharePoint list
15 columns by
5,000 rows
Supported This specifies the number of
uses a SharePoint list as a data
source. This may change based
on rows vs. columns.
Query on a SQL
Server data
source
15 columns by
20,000 rows
Supported This specifies the number of
uses a SQL Server table as a
data source. This may change
based on rows vs. columns.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Components
PerformancePoint Services includes:
Dashboard Designer. This provides a UI for users to develop and manage dashboards and their
elements:
o Reports
o Analytic charts
o Scorecards
o Filters
Web Parts. PerformancePoint Web Parts are built-in, server-side controls that run inside the context
of webpages. You should identify Web Parts that fulfill user requirements during the design phase.
Options include:
o Reports Web Part. The Reports Web Part includes analytic charts and grids, SQL Server Reporting
Services reports, Excel Services reports, and the strategy map.
o Status Indicator Web Part. The Status Indicator Web Part report displays contextually relevant
information about KPIs, metrics, rows, columns, and cells within a scorecard.
o Scorecard View Web Part. The Scorecard View Web Part provides view functionality for the
scorecard. Without the Scorecard View Web Part, users cannot render the KPIs in a dashboard.
PerformancePoint site collections. The Dashboard Designer bases queries on the location of the web
service, which is scoped in a SharePoint Server 2013 site collection.
Using PerformancePoint Services
Depending on your user population, you can use PerformancePoint Services as an IT-provisioned solution,
or provide users with the training to use development options, such as the Dashboard Designer.
PerformancePoint Services adds layers of security over SharePoint 2013; the layers of security are used for
items held in lists or document libraries. You can manage the service application security from the
SharePoint Central Administration website.
Authentication
PerformancePoint Services supports three authentication methods for source data access:
Per-user Identity. Access is based on transmission of the user identifier. This method requires you to
include Kerberos delegation in your design.
Unattended user account. Access is managed through a predefined unattended user account. The
Secure Store Service holds this low-privilege account information. You must include permissions to
give this account access to the external data.
Custom data. SQL Server Analysis Services manages access and includes the currently authenticated
user name as a parameter on the custom data field in an Analysis Services connection string. The
custom data option is only used for Analysis Services data sources.
Trusted data locations
You limit PerformancePoint Services features that use trusted locations. This means that PerformancePoint
Services is available in specified sites, lists, or document libraries, but not to a whole site collection. You
can specify the following locations:
PerformancePoint Content List: This stores the elements required to create a dashboard.
PerformancePoint Data Source Library: This holds data-source definitions that identify a source of
business data, such as a cube or Excel workbook.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Trusted Data Sources and Trusted Content Locations: Here you can specify a URL that has a valid site
collection, site, document library, and list. There are a number of options, such as Edit and Delete,
which are enabled when you have configured a valid location.
Deploying and Managing PerformancePoint Services
As with all service applications, there are a number
of steps that you must configure to deploy
PerformancePoint Services. You can accomplish
these by using either the Central Administration
website or by using Windows PowerShell. These
procedures and commands can also be used to
manage an existing PerformancePoint Service
instance. The service must be installed and started
on a server to undertake any service application
configuration.
The steps required to configure your
PerformancePoint Service service application
include:
1. Configure the service application. This step involves:
a. The registration of the managed user account.
c. Starting the PerformancePoint Service.
d. Creation of a PerformancePoint Service service application.
2. Configure global settings. These include options such as cache, filters, and measure control.
3. Configure the unattended service account for data access. This specifies the account used to provide
access to external data sources.
4. Configure data connections. There are several data connections that you may need to define,
dependent on the connections required in your environment. You create these from the Dashboard
Designer. These can include connections to:
a. SSAS.
b. SharePoint lists.
c. SQL Server tables.
d. PowerPivot.
e. Excel workbooks.
f. Excel Services.
5. Configure trusted data sources. You can specify the sites, lists, or document libraries that have access
to PerformancePoint Services functionality.
The Windows PowerShell cmdlets that are available to complete these management tasks for
PerformancePoint Services are:
New-SPPerformancePointServiceApplication. Creates and configures a new service application.
New-SPPerformancePointServiceApplicationProxy. Configures an application proxy.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
New-SPPerformancePointServiceApplicationTrustedLocation. Creates a new trusted location for
a PerformancePoint Services application.
Set-SPPerformancePointServiceApplication. Enables you to define global runtime properties.
Additional Reading: For more information about the PerformancePoint Services Windows
PowerShell cmdlets, see PerformancePoint Services cmdlets in SharePoint Server 2013 at
Planning Visio Graphics Services
Like Excel Services, the Visio Graphics Service
service application is an interactive reporting
solution rather than a shared or multiuser version
of Visio 2013. This service enables users to render
Visio 2010 Professional, Visio 2010 Premium, and
Visio Professional 2013 files onto a web browser in
the Visio Web Access Web Part. This means that
the users, including mobile device users, do not
need Visio 2013 or the Visio Viewer installed to
view Visio diagrams. These drawings must be
created in Visio 2010 or Visio 2013 and then
published to the Visio Graphics Service.
Visio diagrams are stored in a document library, from which they can be rendered by the Visio Graphics
Service. You can secure these diagrams in the same way that you would secure other files in SharePoint
2013.
New features in Visio Services for SharePoint 2013
There are four new Visio Graphics Service features available in SharePoint 2013, which primarily focus on
improving rendering performance:
Maximum Cache Size. This is a new service parameter that is located on the Central Administration
Visio Graphics Service Application Global Settings page. The new parameter increases the
performance of graphics rendering, and has a default value of 5120 MB.
Health Analyzer rules. New Health Analyzer rules have been added to reflect functionality of the new
MaxCacheSize parameter.
Updated Windows PowerShell cmdlets. The Set-SPVisioPerformance cmdlet has been updated to
include the new MaxCacheSize parameter.
Commenting on drawings support. This enables multiple users to add comments to a Visio Drawing
collaboratively on the web through Visio Services.
Planning your Visio Graphics Service deployment
Visio 2013 is a relatively specialist tool, particularly when you compare it to BI solutions such as Excel
2013. You must identify process-driven options in your business that would benefit from visualization. For
wider use, you may consider provisioning workflow diagrams that show current status and visually flag
overdue or failed workflow steps.
Planning a Visio Graphics Service service application deployment is relatively simple. Performance issues
are mostly based on the number, complexity, and size of the diagrams used in your organization and the
peak loading, triggered by usage. The complexity of the diagrams should mostly focus on the frequency
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
of diagram refreshes for data from internal or external data-connections. As with all implementations, you
should pilot your Visio Graphics Service and monitor the resource consumption. When you are confident
that the consumption is within Service Level Agreement requirements, you can deploy the service. As with
all services, you should continue to monitor performance and usage, so that you can make changes to
service deployment as necessary. If you need to have multiple WFE services to support your Visio Graphics
Service, you must ensure that the State Service is running on these servers. This is not provisioned
automatically when you deploy the Visio Graphics Service.
Connected drawings
Visio 2013 can link to SharePoint and external data sources to provide refreshable input to drawing
variables. The Visio Graphics Service maintains this functionality, and uses SharePoint 2013 to manage
security and authentication. SharePoint 2013 treats unconnected drawings in the same way as any other
file that is held in its document library. You can plan security to make these files available to users either
directly in Visio 2013, or through the Visio Graphics Service visualization options.
By using the data-link and publishing technologies in Visio 2013, drawing creators can connect to and
refresh data from the following sources:
SQL Server 7.0
SQL Server 2000
SQL Server 2005 (32-bit and 64-bit)
SQL Server 2008 (32-bit and 64-bit)
SQL Server 2008 R2 (32-bit and 64-bit)
SQL Server 2012
Sheet information that is stored in Excel workbooks (.xlsx files) that are published from Office Excel
2007, Excel 2010, and Excel 2013 which are hosted on the same SharePoint Server 2013 farm
SharePoint Server lists that are hosted on the same farm
External lists exposed in SharePoint Server through Microsoft Business Connectivity Services
OLE DB or Open Database Connectivity (ODBC)
Custom data providers that are implemented as Microsoft .NET Framework assemblies
To control access, you should plan to define the sources in the list of Trusted Data Providers. You can add
new data providers when you create a Visio Graphics Services service application, either through Central
Administration or by using Windows PowerShell. When you define a trusted data provider you must
specify:
Trusted Data Provider ID. This is the name of the driver acting as the data provider and is used to
reference the data provider in any connection string. This driver is installed on each server that runs
the application service.
Trusted Data Provider Type. This is one of six types:
o OLE DB (1)
o SQL (2)
o ODBC (3)
o ODBC with DSN (4)
o SharePoint Lists (5)
o Custom Data Provider (6)
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Trusted Data Provider Type Description. A brief description of the Trusted Data Provider type.
SharePoint lists
A Visio diagram can connect to basic and external lists that are hosted on the SharePoint farm. External
lists are provisioned as an external content type by Business Connectivity Services. A user must have
appropriate access permissions to both the diagram and at least Read access list to render the connected
data.
Excel connections
Users can connect to Excel workbooks as data sources. In a multiple farm deployment, you must ensure
that your design hosts these on the same farm, because you cannot use this service across farms. You
must also provide Read permission to the Excel workbook and authentication configuration.
SQL Server databases
Visio drawings that are published to the Visio Graphics Service can use connections that are stored in SQL
Server databases.
Authentication
The Visio Graphics Service provides three authentication options:
Integrated Windows authentication (NTLM). The Visio Graphics Service uses the identity of the user
who is viewing the drawing to authenticate with the database. You can enhance security with
Kerberos.
Secure Store Service. As with other BI services, this uses impersonation through the Secure Store
Service to map the users credentials to a different credential that has access to the database. You can
only use Secure Store Service authentication for drawings that use an ODC file to specify the
connection, because the ODC file specifies the target application.
Unattended service account. This provides a single account that an administrator can map to all
authorized users in a Secure Store Service target application. This method, which is the default option
for connection to SQL Server databases, does not enable personalized queries against a database and
does not provide auditing of database calls.
For a mixed authentication environment, you should include the following in your planning:
If a user creates a Visio drawing that connects to a SQL Server database, but he or she does not
specify an ODC file, the unattended service account is used by default.
If integrated Windows authentication fails, the Visio Graphics Service will not use the unattended
service account.
Additional Reading: For more information about SharePoint authentication and how it
pertains to the Visio Graphics Service, see Data authentication for Visio Services in SharePoint
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Deploying and Managing Visio Graphics Service
You can manage the Visio Graphics Service both
through the Central Administration website and by
using Windows PowerShell. From Central
Administration, you can perform all of the
common service application tasks, such as creating
and deleting service applications and application
proxies. The service must be installed and started
on a server to undertake any service application
configuration.
The steps required to configure your Visio
Graphics Service service application include:
1. Configure the service application. This step
involves:
a. The registration of the managed user account.
c. Creation of a Visio Graphics Service service application.
2. Configure global settings. These include options such as maximum diagram size, minimum cache age,
and maximum cache age.
3. Configure trusted data providers. You can specify the sites, lists or document libraries that have access
to PerformancePoint Services functionality.
Additional Reading: For detailed information about completing these common Visio
Graphics Service application tasks, see Visio Graphics Service administration in SharePoint Server
You can use the following Windows PowerShell cmdlets to complete these tasks:
New-SPVisioServiceApplication. Create new service applications.
New-SPVisioSafeDataProvider. Create new service application trusted data providers.
Additional Reading: For more information about the syntax for these and other Visio
Graphics Service cmdlets, see Visio Graphics Service cmdlets in SharePoint Server 2013 at

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Configuring Excel Services
Scenario
Analysts at Contoso currently use Excel tools in conjunction with SQL Server Analysis Services OLAP cubes
to analyze sales data and present it to the executive team. The executive team has expressed an interest in
making these analyses available on the Contoso intranet portal, and has asked you to demonstrate how
this functionality might work.
To prepare your demonstration, you have acquired various data resources, including the Adventure Works
Cycles data warehouse, an associated SQL Server Analysis Services OLAP cube, and an Excel workbook
that uses PivotTables and PivotCharts to query the OLAP cube.
Your first task is to provision an Excel Services service application. Next, you must configure Excel Services
to use an unattended service account to access back-end data sources, and grant the unattended service
account permissions on the OLAP cube. Finally, you will configure a workbook to use an external data
connection and verify that Excel Services enables you to interact with the workbook through a browser
window.
Objectives
Provision an Excel Services service application.
Configure external data access for Excel Services.
Manage data connection files and data connection libraries.
Passw0rd: Pa$$w0rd
Exercise 1: Provisioning Excel Services
Scenario
In this exercise, you will provision an Excel Services service application. First, you will register a managed
account to run the server application. Next, you will grant the service account access to the content
database. You will then start the Excel Calculation Services service instance. Finally, you will create an Excel
Services service application.
2. Grant the service account access to content databases
3. Start the Excel Calculation Services service
4. Create a new Excel Services service application instance
Start the 20332B-NYC-DC-07 virtual machine. Wait for the login screen, then wait a further five
minutes before proceeding to the next step.
Start the 20332B-NYC-DB-07 virtual machine and wait for the logon screen before you continue.
Start the 20332B-NYC-SP-07 virtual machine and wait for the logon screen before you continue.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Pa$$w0rd.
Register the CONTOSO\excelsrv account.
Task 2: Grant the service account access to content databases
Use Windows PowerShell to get a reference to the SharePoint web application at
http://sharepoint.contoso.com.
On the web application object, grant access to the process identity CONTOSO\excelsrv.
Task 3: Start the Excel Calculation Services service
On the SharePoint server, start the Excel Calculation Services service.
Note: You can start services from Windows PowerShell or from the Central Administration
website.
Task 4: Create a new Excel Services service application instance
Create a new Excel Services service application with the following properties:
Property Value
Service application name Contoso Excel Services
Application pool name ContosoExcelServices
Security account for application pool CONTOSO\excelsrv

Results: After completing this exercise, you should have provisioned an Excel Services service application.
Exercise 2: Configuring External Data Access
Scenario
In this exercise, you will configure Excel Services to authenticate to back-end data sources by using an
unattended service account. You will also grant the unattended service account read access to the OLAP
cube on the database server.
1. Configure an unattended service account
2. Grant database permissions to the unattended service account
Task 1: Configure an unattended service account
On the Central Administration website, locate the global settings for the Contoso Excel Services
Configure the service application to use the following credentials as an unattended service account:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Username: CONTOSO\DataAccess
Note: The CONTOSO\DataAccess account has already been created for you in Active
Directory.
Browse to the management page for the Contoso Secure Store service application, and notice that
Excel Services has created a Secure Store target application for the unattended service account.
Task 2: Grant database permissions to the unattended service account
Log on to the 20332B-NYC-DB-07 machine as administrator@contoso.com with password
Pa$$w0rd.
Open SQL Server Management Studio and connect to the Analysis Services instance on the local
server (NYC-DB1).
On the AWSalesMD database, create a new role named Consumers.
Grant the Consumers role the following database permissions:
Process database
Read definition
Grant the Consumers role read access to the Sales cube.
Add the CONTOSO\DataAccess account to the Consumers role.

Results: After completing this exercise, you should have configured an unattended service account for
Excel Services.
Exercise 3: Configuring Data Connections
Scenario
In this exercise, you will configure Excel Services so that hosted workbooks can use trusted external ODC
files to access back-end data sources. First, you will create a new data connection library on SharePoint
and configure Excel Services to trust the new library. Next, you will configure and export a connection file
from an Excel workbook. Finally, you will upload the workbook and the connection file and verify that
everything works as expected.
1. Create a data connection library
2. Configure Excel Services to trust the data connection library
3. Configure and export the connection file
4. Test the Excel Services configuration
Task 1: Create a data connection library
Switch to the 20332B-NYC-SP-07 virtual machine. If you are not already logged on, log in as
Open Internet Explorer and browse to sharepoint.contoso.com. If you are prompted for credentials,
log in as CONTOSO\Administrator with password Pa$$w0rd.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Add a new data connection library named DataConnections to the site.
Task 2: Configure Excel Services to trust the data connection library
On the Central Administration website, browse to the management page for the Contoso Excel
Services service application.
Configure the service application to trust the data connection library at
http://sharepoint.contoso.com/dataconnections.
Task 3: Configure and export the connection file
In Excel, open the workbook at E:\Starter\Sales Analysis.xlsx.
Enable any blocked content.
Locate the data connection named AWSalesMD Sales, and view the properties for the connection.
View the Excel Services authentication settings for the connection, and then change the
authentication account to None.
Note: Setting the data connection account to None ensures that Excel Services uses the
unattended service account to connect to the data source.
Export the data connection to E:\Starter\AWSalesMD Sales.odc.
Note: Leave the Excel workbook and the Connection Properties dialog open, as you will
return to it shortly.
Upload the data connection file to the data connection library at
http://sharepoint.contoso.com/DataConnections.
In Excel, modify the Sales Analysis workbook to use the connection file you just uploaded.
Configure the connection properties to always use the connection file.
On the Category and Business Type slicers, click several items and verify that the workbook still
updates correctly. This confirms that the workbook is able to use the exported data connection file to
access the OLAP cube.
Save and close the Sales Analysis.xlsx file.
Task 4: Test the Excel Services configuration
In Internet Explorer, browse to sharepoint.contoso.com.
Upload the E:\Starter\Sales Analysis.xlsx file to the Documents library.
Open the Sales Analysis file from the Documents library, and verify that the browser window renders
the workbook.
Verify that you are able to interact with the slicers, the PivotChart, and the PivotTable. This confirms
that Excel Services is able to communicate with the back-end data source.

Results: After completing this exercise, you should have configured Excel Services to trust a data
connection library and configured a workbook to use an external data connection file.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Planning and Configuring Advanced Analysis Tools
BI in SharePoint 2013 integrates closely with the rich business data analysis function offered by SQL Server
2012. SQL Server 2012 provides rich data mining and analysis functionality through SQL Server Reporting
Services (SSRS) and SQL Server Analysis Services (SSAS) and has long been associated with sophisticated
modeling tools, such as PowerPivot. SharePoint 2013 offers a mid-tier between SQL Server databases and
personal analysis tools.
In this lesson, you will review these advanced BI options for SharePoint 2013.
Lesson Objectives
Explain the key components in planning, deploying, and managing SSRS for SharePoint.
Describe the use of PowerPivot and Power View in a SharePoint 2013 deployment.
Explain the components necessary to configure PowerPivot for SharePoint
Describe the steps necessary to deploy and use Power View for SharePoint.
Planning, Deploying, and Managing SQL Server 2012 Reporting Services
SQL Server 2012 Reporting Services (SSRS)
provides a range of tools and services to enable
you to provide reports for users in your
organization. With SSRS, you can develop
interactive, tabular, graphical, and free-form
reports from a number of data sources. These
reports can render rich graphical content, and can
be published on a schedule or on-demand. SSRS
integration was introduced with Microsoft Office
SharePoint Server 2007 and continues to provide
extended BI functionality through SharePoint
2013. If you currently have SSRS implemented with
SharePoint Server 2013, it is important to note that you can only use the SQL Server 2012 SP1 version of
the Reporting Services add-in for SharePoint.
Planning usage modes
There are two usage modes for SQL Server 2012 Reporting Services:
Connected or Integrated mode. In Connected mode, an instance of SQL Server Reporting Services
provides back-end services for report storage, caching, scheduling, and subscriptions. Additionally,
SharePoint provides a UI through which the reports that are defined in the report server can be
viewed and managed.
Local or Native mode. Local mode provides a more restricted option for SQL Server 2012 Reporting
Services and SharePoint integration. Local mode requires SharePoint 2013 and the SQL Server 2012
Reporting Services add-in. The deployment does not have a back-end server running SQL Server 2012
Reporting Services. SharePoint uses the SQL Server 2012 Reporting Services add-in to render reports.
In SQL Server 2012, the architecture of SSRS in SharePoint Integrated mode has changed to become a
service application in SharePoint. 2013. Of course, Reporting Service in SharePoint Integrated mode
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
requires SQL Server Setup to install Reporting Services in SharePoint Integrated mode on the application
servers; it also requires installing the Reporting Services add-in on the WFE servers. When these are
installed, SharePoint Central Administration can be used to complete the integration with SharePoint
Server. You can also use Windows PowerShell to install and configure SSRS in SharePoint Integrated
mode,
Planning deployment topologies
You can deploy different topologies for SQL Server 2012 Reporting Services for SharePoint based on the
number of users and the complexity of the reports that are required. These design options are based on
Integrated mode deployments:
Single server farm. This topology has SQL Server Reporting Services and SharePoint 2013 on a single
server. This is best suited for a development environment, or for a specialist departmental
requirement.
Two-tier deployment. This topology separates SharePoint 2013 and the SQL Server Reporting Services
add-in from the SQL Server database, which would also have a SharePoint 2013 WFE implementation.
This solution distributes workload and improves performance for complex reports. This topology is
appropriate for a small company or large department.
Multiple-tier deployment. This topology has three base servers to improve performance and
manageability by using optimized database server hardware:
o SharePoint 2013 with the SQL Server 2012 Reporting Services add-in.
o SQL Server 2012 Reporting Services with a minimal installation of SharePoint 2013 to provide
WFE functionality.
o SQL Server database engine.
Additional Reading: For more information about installing SSRS for SharePoint, see Install
Reporting Services SharePoint Mode as a Single Server Farm at
For information about the options for managing performance by scaling out your deployment,
see Add an Additional Report Server to a Farm (SSRS Scale-out) at
SharePoint Integrated mode installation and configuration
To install Reporting Services in SharePoint Integrated mode, you must perform the following steps when
you have your SharePoint farm installed:
Install Reporting Services. Use the SQL Server 2012 installation media to install Reporting Services in
SharePoint Integrated mode on a SharePoint 2013 application server. When installation is complete,
use the SQL Server 2012 installation media to install the Reporting Services add-in for SharePoint
2013 on the WFE servers.
Configure Reporting Services. To complete the configuration of Reporting Services in SharePoint
Integrated mode, use Central Administration in SharePoint to perform the following steps:
1. Register a managed Reporting Services account.
2. Start the Reporting Services service.
3. Create the Reporting Services application pool.
4. Configure service settings.
5. Enable Reporting Services and Power View in SharePoint sites.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Document library content types for SSRS reports
Reporting Services provides the following content types within SharePoint libraries that enable users to
work with Reporting Services:
Report Builder Report
Report Data Source
Report Builder Model
You can add the Microsoft Business Intelligence Semantic Model (BISM) Connection content type to
enable the creation of connections to tabular data models for Power View and Excel.
Overview of PowerPivot for SharePoint and Power View
PowerPivot for SharePoint and Power View for
SharePoint are add-ins that can extend BI
functionality for SharePoint users. These add-ins
integrate with SSRS, SSAS, and Excel 2013 to
deliver visualization of complex data models.
PowerPivot for SharePoint
PowerPivot is an add-in that organizations can use
to perform data analysis and create data models.
PowerPivot for SharePoint provides the
functionality of PowerPivot for Excel on a
centralized SharePoint Server. This service requires
running SQL Server Setup on each application
server on the SharePoint farm, which creates a PowerPivot instance of Analysis Services on which the
PowerPivot data models can be created when using the application. The SQL setup installs a tool named
PowerPivot for SharePoint 2013 Configuration, which deploys solutions and features, provisions the
service applications, and so forth.
Power View for SharePoint
Power View is a Silverlight application that is built on SQL Server 2012 Reporting Services. Installing SQL
Server 2012 Reporting Services in SharePoint Integrated mode installs the Reporting Services add-in for
SharePoint, which contains the content types, data sources, and entry points that enable Power View
functionality. The add-in also contains the Power View Silverlight application itself. Power View reports
use the tabular data models in PowerPivot workbooks or in Analysis Services tabular databases as a data
sources. You can access these tabular data models to create Power View reports by using the PowerPivot
Gallery Web page hosted in PowerPivot for SharePoint 2013. If you want to create a Power View report
from a tabular SSAS source, you need to define a BISM Connection. Power View is designed for use as a
self-service data analysis tool. It complements the functionality of other Microsoft reporting and data
analysis tools, such as Performance Point Services and PowerPivot for Excel, as well as other tools, such as
Report Builder 2.0, Report Builder 3.0, and SQL Server Data Tools.
Power View was available for SharePoint Server 2010. There have been a number of enhancements and
additions, including:
Additional visualization options, including themes with more palettes and increased font support.
Embedded hyperlink support.
Enhanced language support.
Improved printing.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Improved integer support.
Planning and Configuring PowerPivot for SharePoint
When you plan your PowerPivot for SharePoint
deployment, it is almost certain that your users
already use PowerPivot or have requirements that
they have identified as being serviced by
PowerPivot functionality. That being the case, you
need to assess the effect that PowerPivot will have
on your farm and the prerequisite software or
configuration that you will need to support your
environment.
Planning and installing
To install PowerPivot for SharePoint, you must
perform the following tasks:
1. Establish software pre-requisites for PowerPivot.
2. Install PowerPivot for SharePoint.
3. Configure PowerPivot for SharePoint.
PowerPivot for SharePoint prerequisite software
Before you install Power Pivot for SharePoint, you must install and configure the following prerequisites:
SQL Server 2012 SP1. In order to use the new Excel 2013 features on SharePoint 2013, you install SQL
Server 2012 SP1 in SharePoint deployment mode.
Excel Services. You must configure Excel Services before you can configure and use PowerPivot.
SQL Server Analysis Services. You must have a server deployment of this in SharePoint mode, and this
must be registered in the Excel Services configuration.
Secure Store Service. You must configure this to schedule data refreshes of PowerPivot workbooks.
Installing PowerPivot for SharePoint
You can use the SQL Server 2012 installation media to install PowerPivot for SharePoint on an application
server. The installation routine deploys a PowerPivot mode instance of SSAS on the server and provides a
workspace for working with PowerPivot files. After the installation, you can then run spPowerPivot.msi
from the SQL Server 2012 SP1 feature pack on each server in the SharePoint Server farm to install the
following:
Data providers.
PowerPivot configuration tool.
PowerPivot Gallery.
Data refresh components.
You can execute the spPowerPivot.msi from a command as a scripted installation by running the following
command:
Msiexec.exe /i SpPowerPivot.msi
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
You can add command switches to log the installation report, to perform a quiet installation, or to install
preferred components.
Additional Reading: For more information about spPowerPivot.msi installation command
switches, see the Command Line Installation section of Install or Uninstall the PowerPivot for
SharePoint Add-in at http://go.microsoft.com/fwlink/?Linkid=303688
If you are installing PowerPivot for SharePoint on only one SharePoint 2013 server, the SQL Server
installation media provides these components, so you just run the PowerPivot for SharePoint 2013
Configuration tool.
Configuring PowerPivot for SharePoint
To complete the configuration of PowerPivot for SharePoint, run the PowerPivot for SharePoint 2013
Configuration tool on the application servers to perform the following steps:
1. Register a managed account for the PowerPivot for SharePoint application.
2. Create the PowerPivot for SharePoint application.
3. Start the PowerPivot for SharePoint application.
4. Enable PowerPivot integration within a SharePoint site.
Planning and managing data refresh
PowerPivot workbooks usually contain data models based on data from configured data sources.
Although a user can refresh the workbook data content, it is often preferable to automate this by using a
scheduled job, because this gives greater control to workbook owners and administrators. This means that
the refresh, which may be process intensive, can be run at times of low server activity. You should meet
with your business users to establish a schedule that provides the required level of data freshness and
minimizes workloads at peak usage periods.
Planning authentication for data refresh
Automated data refreshes require you to supply the credentials necessary to connect to a data source.
The authentication options include:
Allow users to specify Windows credentials. This approach enables users to specify a Windows user
name and password when configuring data refresh options for a workbook. This has the advantage of
requiring minimal administrative configuration, but it can result in a difficult-to-manage environment
where credentials for data access are defined in multiple places. If you decide that this option does
not fit with your organizations security strategy, you can disable the setting for the PowerPivot
service application in Central Administration.
Use the unattended PowerPivot data refresh account. As with many services, you can configure an
unattended PowerPivot data refresh account, to which you can give appropriate access controls. You
should note that this approach cannot be used for data sources that do not support Windows
authentication. The unattended PowerPivot data refresh account is stored in the secure store service,
so even if you do not plan to use custom credentials, you must associate the secure store service with
any web applications where data refresh will be used to update PowerPivot workbooks
Use custom credentials. You can use the Secure Store Service to manage access credentials.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Installing, Configuring, and Using Power View
Power View is a component of SSRS 2012 when
installed in SharePoint integrated mode. To install
Power View in your environment, you need
SharePoint 2013 Enterprise Edition.
Installing and configuring Power View
To provision Power View in your SharePoint 2013
farm, you must have the following software
installed:
SQL Server 2012 SP1
Analysis Services (to create a report from
PowerPivot)
Server Analysis Services (SSAS) 2012 instance running in tabular mode
Client Tools
SQL Server Data Tools
Reporting Services SharePoint (on a SharePoint server, not the SQL Server 2012 server)
Reporting Services Add-in for SharePoint Products
To install Power View, you must use the SQL Server 2012 SP1 installation media and perform the following
steps:
1. From the Installation Center start page, click New SQL Server stand-alone installation or add features
to an existing installation.
2. Follow the pages until you select Perform a new installation of SQL Server 2012, and then click
Next.
3. Proceed through product key and licensing pages, and then, on the Setup Role page, select SQL
Server Feature Installation, and then click Next.
4. Accept the options on the subsequent pages, and then click Close on the Complete page.
After the installation procedure is complete, you provision a service application and activate the Power
View feature on site collections.
Using Power View
Power View is designed to work against a tabular data model. This model may be:
A PowerPivot workbook deployed to a SharePoint document library.
A database in a SQL Server Analysis Services (SSAS) 2012 instance running in tabular mode.
Power View reports are created in a web browser. A user can launch Power View from a:
SharePoint library, using a PowerPivot workbook as the data source.
Report Data Source (RDS) file.
Business Intelligence Semantic Model (BISM) file, which is a new type of data connection.
The RDS and BISM files must be stored in a SharePoint document library and point to either a PowerPivot
workbook or a tabular mode database.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To save a Power View report, you simply click Save on the File menu. The report is saved as a single file
with a .rdlx extension. A report file can be saved locally, but it must be saved to a SharePoint document
library for others to view it.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring PowerPivot and Power View for
SharePoint
Scenario
The management team at Contoso is pleased with the new Excel Services functionality on the Contoso
intranet portal. However, the data analysts are increasingly using more sophisticated analysis and
reporting tools, such as PowerPivot and Power View, in their work. The management team has now asked
you to configure the portal to support PowerPivot workbooks and PowerPivot reports.
Objectives
Configure SharePoint 2013 to render PowerPivot workbooks.
Configure SharePoint 2013 to create and render Power View reports.
Passw0rd: Pa$$w0rd
Exercise 1: Configuring PowerPivot for SharePoint
Scenario
In this exercise, you will configure PowerPivot for SharePoint. The IT team has already installed SQL Server
2012 PowerPivot for SharePoint on the SharePoint server. This installation process creates a SQL Server
Analysis Services instance and installs the PowerPivot for SharePoint 2013 Configuration tool. The team
has also provisioned a Secure Store Service application on the SharePoint deployment.
Your task is to complete the configuration. First, you must run the PowerPivot for SharePoint 2013
Configuration tool. This installs the solutions and features that SharePoint requires to support PowerPivot
workbooks, and it creates a PowerPivot service application. Next, you will create a new site collection
using the PowerPivot Site template, and you will use this site to test the PowerPivot functionality in
SharePoint. Finally, you will configure a data refresh schedule for a PowerPivot workbook on the
SharePoint site.
1. Run the PowerPivot for SharePoint 2013 Configuration tool
2. Grant database permissions to the unattended data refresh account
3. Create a PowerPivot site collection
4. Test the PowerPivot for SharePoint 2013 configuration
5. Schedule a data refresh
Task 1: Run the PowerPivot for SharePoint 2013 Configuration tool
On the 20332B-NYC-SP-07 virtual machine, run the PowerPivot for SharePoint 2013
Configuration application.
Note: Be sure to launch PowerPivot for SharePoint 2013 Configuration, not PowerPivot
Configuration Tool. The latter is designed for SharePoint 2010.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Specify a default account username of CONTOSO\Administrator with password Pa$$w0rd. The
default account is used to perform a range of tasks such as provisioning service applications and
deploying features.
Set the PowerPivot server to NYC-SP1\PowerPivot.
Change the name of the PowerPivot service application to Contoso PowerPivot Service
Application.
Set the unattended account for data refresh to CONTOSO\DataAccess with password Pa$$w0rd.
Task 2: Grant database permissions to the unattended data refresh account
Switch to the 20332B-NYC-DB-07 machine. If you are not already logged on, log on as
Open SQL Server Management Studio and connect to the NYC-DB1 database engine.
Create a new login for the CONTOSO\DataAccess account.
Grant the CONTOSO\DataAccess account the db_datareader role on the AWDataWarehouse
database.
Task 3: Create a PowerPivot site collection
In Central Administration, create a new site collection in the sharepoint.contoso.com web
application. Specify the following property values:
Property Value
Title PowerPivot Test Site
Description A test site for PowerPivot and Power View.
URL /sites/power
Template PowerPivot Site
Browse to the new site and log on as CONTOSO\Administrator with password Pa$$w0rd.
Task 4: Test the PowerPivot for SharePoint 2013 configuration
On the PowerPivot Test Site, browse to the PowerPivot Gallery.
Upload the PowerPivot workbook at E:\Starter\Marketing Analysis.xlsx.
Reload the page periodically until SharePoint has generated snapshots of the workbook in a gallery
view.
Review the different views available for the gallery, including Carousel and Theater.
Click the workbook preview and verify that the browser window renders the workbook.
Verify that you can interact with the PivotTable and the slicers. This confirms that PowerPivot for
SharePoint is working correctly.
Refresh the data connections, and verify that the operation completes without errors. This confirms
that the unattended data refresh account is able to retrieve data from the source database.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 5: Schedule a data refresh
From the PowerPivot Gallery, open the data refresh settings for the Marketing Analysis workbook.
Enable data refresh for the workbook, and schedule a data refresh to run daily after business hours.
Configure the data refresh to also run as soon as possible, so that you can verify that it works
correctly.
Configure the data refresh to use the data refresh account you configured earlier in this exercise.
Review the status of the data refresh and verify that the operation was successful.

Results: After completing this exercise, you should have configured SharePoint to support PowerPivot
workbooks.
Exercise 2: Configuring Power View for SharePoint
Scenario
In this exercise, you will configure Power View for SharePoint. The IT team has already installed the SQL
Server 2012 Reporting Services - SharePoint and Reporting Services add-in for SharePoint products on the
SharePoint Server.
Your task is to complete the configuration. First, you must install and start the SharePoint Reporting
Services service. Next, you must provision a Reporting Services service application. You will then activate
the Power View integration feature on a site collection and create a demonstration Power View report.
1. Install and start the SharePoint Reporting Services service
2. Register a managed account
3. Create a Reporting Services service application
4. Activate the Power View Integration Feature
5. Create a Power View report
Task 1: Install and start the SharePoint Reporting Services service
Use Windows PowerShell to install the SharePoint Reporting Service.
Use Windows PowerShell to install the SharePoint Reporting Service proxy.
Use either Windows PowerShell or Central Administration to start the SharePoint Reporting Service.
Task 2: Register a managed account
Register a SharePoint managed account for the following credentials:
o Username: CONTOSO\PowerView
Note: The CONTOSO\PowerView account has already been created for you in Active Directory.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Create a Reporting Services service application
Create a new Excel Services service application with the following properties:
Property Value
Service application name Contoso SSRS
Application pool name ContosoSSRS
Security account for application pool CONTOSO\PowerView
Database server NYC-SP1\PowerPivot
Database name ContosoReportingDB
Web application association sharepoint.contoso.com
Task 4: Activate the Power View Integration Feature
In Internet Explorer, browse to the site collection at sharepoint.contoso.com/sites/power. If you are
prompted for credentials, log on as CONTOSO\Administrator with password Pa$$w0rd.
Activate the Power View Integration Feature at the site collection level.
Task 5: Create a Power View report
From the PowerPivot Gallery, create a new Power View report from the Marketing Analysis
workbook.
Set the report title to Sales promotion Analysis, and then hide the filters area to maximize your
working area.
Add the following Power View fields to the report:
o Revenue
o Promotion Type
o Commute Distance
Display the fields as a clustered bar chart that fills the left half of the report. Tile the chart by Year so
that you can click the year headers above the chart to view revenue by promotion type broken down
by commute distance for each year.
In the blank area to the right of the bar chart, add the Revenue and Country fields, and then display
them as a pie chart that fills the top of the right half of the report.
In the blank area under the pie chart, add the Revenue and Cars fields. Display them as a clustered
column chart that fills the bottom of the right half of the report.
Click the Commute Distance legend values to shade all of the charts in the report based on the
selected commute distance.
Save the report and go back to the PowerPivot Gallery. Notice that the gallery displays a preview of
the report.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Results: After completing this exercise, you should have configured SharePoint to create and render
Power View reports.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you learned how to plan, configure, and manage the different components of BI in
SharePoint 2013. You learned how to plan and configure the core BI service applications, including Excel
Services, PerformancePoint Services, and Visio Graphics Service. You also learned how to deploy and
configure advanced BI components, including PowerPivot for SharePoint, SQL Server Reporting Services,
and PowerView.
Review Question(s)
Test Your Knowledge
Question
The Excel Services service application comprises three services. Which of the following
creates, maintains, and closes user sessions to the service?
Excel 2010
Excel 2013
Excel Calculation Services
Excel Web Access
Excel Web Services
Test Your Knowledge
Question
Which of the following authentication modes maps the user credentials to the BCS
application pool account and sends those credentials to the target system?
Credentials
PassThrough
RdbCredentials
RevertToSelf
WindowsCredentials

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
8-1
Module 8
Planning and Configuring Enterprise Search
Contents:
Module Overview 8-1
Lesson 1: Configuring Search for an Enterprise Environment 8-2
Lab A: Planning an Enterprise Search Deployment 8-12
Lesson 2: Configuring the Search Experience 8-14
Lesson 3: Optimizing Search 8-23
Lab B: Managing Search Relevance in SharePoint Server 2013 8-31

Module Overview
The Search service remains a cornerstone of the SharePoint platforms success. In Microsoft SharePoint
Server 2013, there have been major changes to the components that make up the service, to increase
performance and configurability.
The configuration options in SharePoint Search now enable you to provide greater search result
effectiveness by fine-tuning the service in various ways. The introduction of new functionality, such as
result types and the increased move toward search-driven navigation mean that the role of the Search
administrator has become even more important for business success. Search now enables you to delegate
more of this management to site collection administrator and site owner levels, improving Search
flexibility without increasing the administrative burden on a few Search service application administrators.
To help you in your management of a Search environment, SharePoint 2013 now incorporates Search
analytics and reporting into the Search service, rather than in a separate service application, as was the
case in SharePoint Server 2010. The reports available will help you to monitor the service and optimize its
configuration.
Objectives
Describe the Search service architecture and key areas of configuration.
Explain how to configure the Search service to improve the end-user experience.
Describe how to use analytics reports to optimize your Search environment.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
8-2 Planning and Configuring Enterprise Search
Lesson 1
Configuring Search for an Enterprise Environment
SharePoint 2013 has made a number of architectural changes to the Search service application, many of
which are within the components of the service. It is important that you understand how these
components manage content ingestion and query servicing. The new search components enable you to
flexibly scale your environment, whether it is a small or large enterprise, or an internal or Internetfacing
audience.
As search becomes more sophisticated, you have greater control over the nuances of search, such as the
search schema and content relevance. In this lesson, you will see how the architecture has evolved and
how you can manage that architecture to deliver a high-quality service to consumers.
Lesson Objectives
Describe the new Search service architecture components and how they interact.
Explain how to scale search for different scenarios.
Describe how to plan and manage the search schema.
List the options that are available in Search to maximize result set relevance.
Overview of Search Architecture Workflow
The Search service has been rearchitected in
SharePoint 2013 to provide enhanced operation
and a higher level of search component
redundancy. This improves performance and the
resilience and availability of the search service. As
an increasing number of both internal and
Internet-facing sites provide search-driven
navigation, search has become more than just a
useful tool; it is the core of many business
websites. SharePoint 2013 Enterprise Search has
most obviously changed with the integration of
the functionality previously provided by deploying
FAST for SharePoint 2010. For end users, this provides integral context sensitive item preview for
documents and other result set items.
Following its radical rebuild, the Search architecture is now made up of the following components:
Crawl
Content Processing
Analytics Processing
Indexing
Query Processing
Search Administration
There are two core functions of search, content ingestion and content query. Without effective content
ingestion, contributor content will not be effectively indexed. For search users, it is essential to have
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
indexed content available to them quickly and to ensure that search queries surface the most relevant
content in their result sets.
Content ingestion
The process flow for ingesting content into the search index uses the following components:
Crawl. The crawl component can search content across a range of content sourcesboth from
Microsoft platforms and from third-party sources. Access to these is provisioned by connectors. There
are a number of connectors shipped with SharePoint 2013. Crawled content is held in the crawl
database.
Content Processing. The crawl component passes the crawled content to the content processing
component. This component processes the content by performing tasks such as parsing documents,
property mapping, and processing linguistics, all of which create artifacts that can be stored in the
search index. In addition, this component processes URL links, which are stored in the link database.
Analytics Processing. The analytics processing component analyzes the crawled items and how users
interact with search results. The increased granularity of this analysis provides enhanced analysis items
and how users interact with them.
Index. The index component writes artifacts to the index file, which is actually a number of files and
folders. This component also manages the index partitions and replicas, ensuring that indexed
content is valid.
You can deploy multiple instances of these components to scale-out your search architecture.
Content Query
The process for servicing user search queries is as follows:
1. A client interface, such as the Search Center, passes a query through a web front-end (WFE) to the
query processing component.
2. The query processing component performs some linguistic processing to maximize query efficiency
and effectiveness, such as word-stemming and initiation of query rules. The processed query is then
passed to the index component.
3. The index component interrogates the search index and returns a result set to the query processing
component. This component processes these results to remove duplicates and perform any additional
security trimming that is required, and then passes the result set to the WFE to be rendered to the
client application.
The Search Administration Component runs system processes required for search. It is responsible for
search provisioning and managing topology changes, and it coordinates interaction between the other
search componentsContent Processing, Query Processing, Analytics Processing, and Index Component.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Planning and Scaling Your Search Topology
Your search topology is unique to your
organization. You should test the impact of all
deployment options on the physical server and in
the software configuration.
The key to an effective search deployment is
monitoring your search analytics. This is because
search information changes constantly; last weeks
most popular page may not get any hits this week.
You must also ensure an appropriate level of fault
tolerance for your organization. If you run an
Internet-facing site, and particularly if you
provision online transactions, it is essential to
assess the business impact if your website is unavailable. As part of your availability strategy, you need to
guarantee component availability, so you should deploy multiple Crawl, Content Processing, Analytics
Processing, Query Processing, and Search Administration Components. You should also deploy primary
and secondary index replicas to deliver an effective level of fault tolerance for your index.
All search content is stored on database servers. You must work with your database administrator (DBA) to
ensure fault tolerance and performance through the implementation of SQL Server features, such as
Always On.
Note: SQL Server functionality that you should consider as a SharePoint 2013 administrator
is covered in Module 5, Installing and Configuring SharePoint Server 2013, of Course 20331B, Core
Solutions of Microsoft SharePoint Server 2013.
Microsoft testing makes the following recommendation on scaling out components:
Deploy and configure one additional index partition per 10 million items.
Always use two Query Processing Components for redundancy.
When you have more than 80 million items, increase the number of Query Processing Components to
four.
Deploy and configure one additional crawl database per 20 million items.
Deploy and configure one additional link database per 60 million items.
Deploy and configure one additional analytics database for each 500,000 unique items viewed per
day or for each additional 10 million items.
Always deploy two Search Administration Components for redundancy.
You must always test changes to ensure that they have had the effect you anticipated.
When working with enterprise search environments, you must monitor changes in search performance
metrics. You should use the Crawl Health Reports to identify changes in performance and any associated
bottlenecks. To improve crawl time and index freshness, you may add more crawl databases and Content
Processing Components for result freshness. Be sure to identify any system contention on servers.
Although the recommended minimum RAM for dedicated indexing servers (systems running the Indexing
Component) is twice that of systems running other search service components, the amount of RAM
should never be less than 16 GB. To improve query latency and query throughput, you should consider
increasing the number of search index partitions to reduce the number of items on each partition.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
You may also assess the need for a search-specific farm deployment. For an organization that is heavily
dependent on search, it may be advisable to separate searches that can be shared across farms as a
service application, to better manage server and network traffic and performance.
For general design guidance, Microsoft categorizes search implementations as small, medium, and large
enterprise deployments.
Reference Links: For model Visio diagrams for topology design, see Architecture design for
SharePoint 2013 IT pros at http://go.microsoft.com/fwlink/?Linkid=303689
Small enterprise
A small enterprise deployment is defined by Microsoft as one that provisions search functionality for up to
10 million items. As part of your planning, you should estimate the number of search items that you need
to index. You should also ensure that you fully understand the SharePoint site content volume and the
volumes of searchable content that may be included from external data sources, because these may be
considerably larger than you anticipate. These volumes will also be affected by criteria such as crawl
depth.
Medium enterprise
A medium enterprise is defined as one that can manage up to 40 million search items. This usually means
that you scale out by deploying dedicated servers for specific search functions. As the size of the index
grows, you should review the number of servers running the Query Processing Component and storing
the search index. Additional servers can deliver greater throughput processing and, therefore, better
performance for users.
Large enterprise
A large farm is defined as one that provides search services for 100 million items. For a large farm, you
should scale out based on the preceding advisory guidance.
Internet search sites
Search is often integral to an Internet-facing site; for any site that has new customers, it is essential that
they can find what they are looking for. The following elements of the new SharePoint 2013 Search
architecture are important for Internet-facing deployments:
Web servers are incorporated in the topology for Internet sites to serve user requests, which is not
specifically the case for an enterprise Search deployment.
The query processing and index components are installed on web servers. This maximizes
performance by making use of the web server hardware resources. It also makes it easier to scale out
the topology.
In an Internet-facing environment, performance is critical. There is no industry standard required response
time, but the goal in 2009 was to service a page request within 2 seconds (Forrester: eCommerce Web Site
Performance TodayAn Updated Look At Consumer Reaction To A Poor Online Shopping Experience).
Today, the goal is to be even faster. This means that you need to maximize the resources available to web
front-end (WFE) servers. If you are hosting a site where users rely on search to find items or pages, you
should ensure that your WFE servers have sufficient memory to enable caching of queries and result sets.
For each query, there is a cache rate of approximately 50 percent. This means that your top queries are
almost certainly cached, which means that users get a faster response. Microsoft provides tested
recommendations for the physical configuration of servers in an Internet-facing search deployment.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Search Component RAM Disk
Index component 48 GB 500 GB in addition to base requirements
Analytics processing
component
24 GB 300 GB in addition to base requirements
Crawl component 24 GB
Content processing
component
24 GB
Query processing
component
48 GB
Search administration
component
24 GB
In addition to these physical recommendations, you may improve performance of search requests by
ensuring that the content that your users search is stored on SharePoint, rather than on external data
sources. In addition to improved access speed, you can implement continuous crawl for content stored on
SharePoint, which can keep your index fresh. With any performance tuning, you must establish a baseline
and then test individual changes against that benchmark, because configuration changes can make
responses slower as well as faster.
Planning and Configuring the Search Schema
The SharePoint 2013 search schema specifies the
items to be crawled, how these items are indexed,
and how the results are rendered in search sites. It
maps the relationships between crawled and
managed properties, which is important because
in SharePoint 2013, users can only search on
managed properties, not crawled properties.
Mapping these relationships can be one-to-many
for both crawled and managed properties; one
crawled property to many managed properties or
one managed property to many crawled
properties.
During the ingestion process, the crawl component reads content from the SharePoint 2013 content
databases and other external data sources and passes these to the content processing component. This
processes the content, extracting text and so forth, and maps crawled properties to managed properties,
outputting pairs of managed properties and indexing the content.
There is only one search schema when you first install SharePoint 2013, but you can add additional
schemas as your business needs require. The initial schema is accessible at the Search service application
level, so it can only be changed by an administrator with access to Central Administration. Site collections
inherit this schema and the site collection owners can override the schema, if necessary. This initial schema
is useful for company-wide search standards. In SharePoint Online the structure is similar, but each tenant
inherits from the Search service application, which is pre-defined. Site collections, in turn, inherit from
their parent tenant. Site owners can view the search schema, but not change it.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The configuration changes available for crawled properties, managed properties, or mapping at service
application level include:
Add
Remove
Change
Delete
At a site collection level, an administrator can:
Create new managed properties of type String. These cannot be defined as refinable or sortable.
Create new managed properties of type Yes/No.
Override existing mappings to managed properties.
Create aliases for managed properties.
SharePoint Server 2013 also has settings that you can apply to managed properties, including:
Searchable
Advanced Searchable Settings (optional, if Searchable is selected)
Queryable
Retrievable
Allow multiple values
Refinable
Sortable
Alias
Token Normalization
Complete Matching
Additional Reading: These settings are described in detail in Course 20331B, Core
Solutions of Microsoft SharePoint Server 2013.
Managing the search schema
Managing a search schema involves reviewing, adding, deleting, and mapping properties. You can achieve
all of these through the Search service application management interface in Central Administration. To
manage your search schema, you must navigate to the Search service application from the Manage
service applications option in Central Administration. You can view all of the managed properties from
the Search Schema option.
This loads the Managed Properties page, where you can review:
Managed properties.
Settings on these managed properties.
Mappings between crawled properties and managed properties.
Crawled properties.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
You can add new managed properties by clicking New Managed Property and specifying the Type,
Main characteristics. You can add a mapping to a crawled property by clicking Add a mapping. From
this page, you can also edit and delete managed properties.
Planning Search Relevancy
When you configure Search, it is essential that you
maximize the relevance of the items in the result
set that is returned for a users search query. There
are a number of configuration options that you
need to complete to make this happen. It is also
important to understand that configuring search
relevance is not a one-time-only event. The
configuration of search relevance is an on-going
task, because your content will change and so will
the needs of your users.
The core configuration tools for relevance include:
Authoritative pages
Query rules
Query suggestions
Entity extractors
Thesaurus
Query spelling correction
Authoritative pages
Not all web pages are equally useful to searching users. Although it would be a huge task to weight every
page on an enterprise farm, you can configure pages that you feel will be important to searching users;
these are called authoritative pages. For example, the top-level page on a site or the organizations home
page may be considered as authoritative, because users will readily find what they are looking for, or the
path to required information, on these pages.
Alternatively, you can designate a page as being non-authoritative because you do not want it to be
considered highly relevant when returning a results set. This may be because it holds historical or archived
information, which is important but not current.
You can configure authoritative and non-authoritative pages from the Search Administration page, by
clicking Authoritative Pages. This displays the Specify Authoritative Pages page, on which you can type
the URLs of pages that are the most authoritative. Each URL must be listed on a separate line. You can set
three levels of authority, with the most authoritative having the highest ranking, and therefore the most
relevance when returning a result set. There is also a Non-authoritative Sites section, where you can list
the URLs of any sites that you want to be ranked lower than all of the other sites. Again, each URL must be
listed on a separate line. This will also affect any pages that are child pages or sites on the listed URLs.
After you configure your authoritative options, you can select the Refresh now check box to refresh the
ranking analytics based on your new options. If you do not select this option, the refresh will run on a
defined schedule.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Query rules
The purpose of a query rule is to try to construe the intent of a querywhat the user is really trying to
find in order to render the best possible result set. A query rule comprises three components:
Query Conditions. The rules that define the possible matches for the query.
Query Actions. The actions that the search service takes when a match is made.
Publishing Options. A set of criteria to define when the query rule should trigger.
Query rules can be created at Search service application, site collection, and site levels, by administrators
and users with appropriate permissions for these containers. Search service application query rules are
created from the Query Rules option on the Quick Launch menu for the Search service application. Site
collection and site query rules are created from the Site Setting page by clicking Query Rules.
From the Manage Query Rules page, you can set:
Context. In this section, you can apply the rule to all result sources or to specific result sources.
Query Conditions. Here, you can specify conditions for the query rule, such as Query Matches
Keyword Exactly or Query Contains Action Term.
Actions. This specifies the action that should occur when the query rule executes.
Period. Here, you can specify a time period. For example, a rule may become active when a special
promotion runs.
Additional Reading: Query rule settings are described in detail in Course 20331B, Core
Solutions of Microsoft SharePoint Server 2013 and in Manage query rules in SharePoint Server
You can also render a number of search results that are displayed as a group; this is called a result block.
You can configure this in the Actions section of the Manage Query Rules page.
The goal of a query rule is to promote appropriate results by increasing their ranking. The ranking model
calculates a ranking order of search results. You can change this ranking by promoting or demoting items
within the search results. Again, you can configure this option from the Actions section.
If you have a position where there are multiple queries that can trigger, you can add rules to a group and
configure the order in which the rules execute.
Query suggestions
Query suggestions are phrases that other users have previously used in searches. These are listed below
the Search box and appear as a user types a new search phrase. Search creates these suggested phrases
for a query when other users have clicked the results for that query at least six times. A suggestion phrase
is listed if the query that is being typed contains at least one of the query suggestion phrase words. The
Search service generates these automatically each day for each result source and for each site collection.
You can manually add phrases that should always be used as query suggestions, as well as phrases that
should never be used. To do this, you must create a text file of phrases and import them for a Search
service application. You do this by clicking Query Suggestions on the Manage Service Applications
page:
To import a list of phrases you want to use, click the Always suggest phrases section, and then click
Import from text file.
To import a list of phrases that should never be used, click the Never suggest phrases section, and
then click Import from text file.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
You can edit these lists by exporting the current list to a text file, editing the text file, and then
reimporting the edited file. The import action overwrites the current list, so you cannot augment list items
individually. You enable or disable suggestions by selecting the Show search suggestions check box on
the Query Suggestions page.
Entity extractors
You can configure custom entity extractors to provide greater granularity in your content processing. An
entity is just a word or phrase that may be of significance to your organization, such as a product or
division name. To help ensure that content containing this entity is processed for the search index, you
must create and deploy a custom entity extraction dictionary.
There are four extraction options available for identifying entities, as shown in the following table.
Custom entity
extractor /
dictionary
Description
Word Extraction Case-insensitive, maximum five dictionaries.
Example: the entry "tram" would match "tram" and "Tram", but not
"trample".
Word Part
Extraction
Case-insensitive, maximum five dictionaries.
Example: the entry "tram" would match "tram", "Tram" and within
"trample".
Word Exact
Extraction
Case-sensitive, maximum one dictionary.
Example: the entry "tram" would match "tram", but not "Tram" or
"Trample".
Word Part Exact
Extraction
Case-sensitive, maximum one dictionary.
Example: the entry "tram" would match "tram" and within "trample", but
not "Tram".
Custom dictionaries are created as comma-separated value (.csv) files. These must have two columns: Key
and Display Form. In the Key column, you type the terms to include as custom entities. This can be one
or multiple words. This is followed by a comma and then you type a refiner name, which provides a
standardized format for the refiner wording. You must be sure that there are no leading or training spaces
around words in your csv file; spaces between multiple word phrases are allowed. Save the file and then
import it into SharePoint 2013 by using the Windows PowerShell cmdlet:
Import-SPEnterpriseSearchCustomExtractionDictionary SearchApplication $searchApp
Filename <Path> DictionaryName <Dictionary name>
You can link a custom entity extraction dictionary with a managed property. The assumption is that the
managed property contains the entities in the dictionary. To do this, configure the settings under Custom
entity extraction on the Edit Managed Property page. The dictionary name is not arbitrary, but it will be
something like Microsoft.UserDictionaries.EntityExtraction.Custom.Word.2.
Additional Reading: For more information about entity extraction dictionaries, see Create
and deploy custom entity extractors in SharePoint Server 2013 at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Thesaurus
A thesaurus provides synonyms for words that are used across an organization. For example, you may
have different terms for customers in your organization, such as customers or clients. You can create a
thesaurus to indicate that these terms are synonymous when found in a query, so a user can search for
customers or clients and get the same results.
A thesaurus is a comma-separated value (.csv) file with three possible columns: Key, Synonym, and
Language (optional). The Key word of a phrase is separated from the Synonym by a comma. When a
query contains the key words, the query will automatically extend to include the synonym. You can
include the Language option to indicate the Key and Synonym language. This is added in the
international language code format; for example, EN for English. Again, there must be no space around
Key, Synonym, or Language words or phrases.
You deploy a thesaurus by using the following Windows PowerShell cmdlet:
Import-SPEnterpriseSearchThesaurus -SearchApplication $searchApp -Filename <Path>
Query spelling correction
Users have become accustomed to search engines offering them spelling correction options when they
mistype a query keyword. SharePoint 2013 provides this through its query spelling correction function.
You can create spelling inclusion and exclusion lists by opening the Term Store Management Tool. You do
this on the Search Administration Page, by clicking Search Dictionaries. You then click either the Query
Spelling Inclusions or the Query Spelling Exclusions option and the term to include or exclude. When
you click outside the input text box the term is saved. You can also edit terms by double-clicking the term
that you want to edit.
You can use Windows PowerShell to create or review query spelling corrections by using the following
cmdlets:
Set-SPEnterpriseSearchQuerySpellingCorrection
Get-SPEnterpriseSearchQuerySpellingCorrection

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Planning an Enterprise Search Deployment
Scenario
Contoso has decided to take advantage of the SharePoint 2013 search technology and is planning to
replace the existing search solution.
Sources of information include file shares, documents, and other content that is stored within SharePoint;
people; and the Contoso product information, which exists in a SQL Server database. Your team must
design the enterprise search architecture for Contoso. In addition, your team must enable People Search.
The information that your team needs is detailed in the supplied documents. Use these documents to
produce your search design.
Objectives
Create a search plan for SharePoint 2013 at Contoso.
Lab Setup
Virtual Machine: 20332B-NYC-CLI
o User name: admin
o Passw0rd: Pa$$w0rd
In this lab, you will develop a search plan for Contoso as part of your systems documentation.
In the exercise, you will complete the Search Worksheet, based on the business requirements information
that is supplied to you.
Exercise 1: Planning a Search Solution
Scenario
The Contoso executive board has outlined a series of business requirements centered on search. You have
been asked to develop a plan that documents how these requirements can be serviced by the IT Services
Director; your plan should identify the volumes of data and how these will affect the requirements of the
search components and topology.
2. Complete the SharePoint 2013 Search Planning worksheet
Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen
before you proceed to the next step.
In the E:\Mod08\Starter folder, read the information in the Contoso Search Requirements.docx
file.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 2: Complete the SharePoint 2013 Search Planning worksheet
In the E:\Mod08\Starter folder, open and complete the worksheet in the SharePoint 2013 Search
Planning Worksheet.xlsx file, based on the information you have reviewed in Task 1.
Shut down the NYC-CL1 virtual machine.

Results: A completed SharePoint 2013 Search Planning worksheet.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Configuring the Search Experience
SharePoint 2013 has introduced a number of new features and options in Search, such as Result Types,
which enable you to deliver a more effective search experience for users. The user experience, both as a
contributor and a consumer of content, should be central in your search planning.
Search configuration has been enhanced by the increased number of search-related Web Parts, new
functions, and the increased flexibility in rendering search result sets in formats that are more appealing
to both your users and your organization.
In this lesson, you will see the key changes and how these can be applied to deliver search-driven sites.
Lesson Objectives
Describe the function and configuration of result sources.
Explain how to use and manage result types.
List the functionality offered by new search Web Parts.
Describe the core elements for configuring search-driven navigation.
Explain how to configure a Search Center site.
Describe the options available to enhance the end-user experience of SharePoint 2013 search.
Configuring Result Sources
Result sources have functionally replaced search
scopes in SharePoint 2013. Result sources combine
federated search and search scopes. Result sources
specify:
A location from which to retrieve search
results.
A protocol to use to access these results.
In SharePoint Server 2010, you would specify these
by creating a federated location.
When you configure a result source, you can:
Limit queries to a subset of content.
Use query transformations to ensure you return the content you want.
You achieve the latter by using the inbuilt Query Builder option, where you can build and test your query
from within the SharePoint configuration screen.
Configuring a result source
You can create result sources at the service application, site collection, and site levels by search service
administrators, site collection administrators, and site owners, respectively. When you create a result
source at these levels, they are made available to all site collections in a web application that consumes
the service application, all sites in a site collection, and the individual site.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Accessing service application level configuration page
When you are logged in as a search service administrator, you click Manage service application from
Central Administration. You can then use the Quick Launch menu to click Result Sources.
Accessing site collection level configuration page
For this option, you must log on as a site collection administrator and click Site Settings. In the Site
Collection Administration section, you click Search Result Sources.
Accessing site level configuration page
Finally, you can set result sources at a site level by clicking Site Settings and then, in the Search section,
clicking Result Sources.
Initial configuration
After you navigate to the configuration page by using whichever method you choose, you can create a
new result source by clicking New Result Source. You need to supply a name and, optionally, a
description for the new result source. In the Protocol section, you can select from:
Local SharePoint. This is the default option and provides results from the search index for this Search
service application
Remote SharePoint. This provides results from the search index of another SharePoint 2013 farm.
OpenSearch 1.0/1.1. This provides search results from a search engine source that conforms to the
OpenSearch protocol.
Exchange. This provides search results from Microsoft Exchange Server. You must discover the
Exchange server that you want to use as a source or type in the URL for the Exchange web service.
The Exchange Web Services Managed API must be installed on the physical computer on which the
search service instance is installed and running.
In the Type section, you can specify whether to use the entire index as your source or to limit it to People
Search results.
Working with the Query Builder
In the Query Transform section, you can keep the default query transform, type a new query directly into
the field, or use the new Query Builder button to launch the Query Builder utility.
The Query Builder provides an interface in which you can create, or build, a unique query by specifying
filters and sort options. These appear on the BASIC and SORTING tabs at the top of the Query Builder
page. There is also a TEST tab, where you can test your new query.
The filter options include a Keyword filter, which provides a series of predefined filter options, such as
Name of the user who runs the query, from a drop-down list. You can add additional keyword filters as
necessary. The Property filter options enable you to specify property filters, such as CONTAINS, and to set
values for the property filter option.
On the SORTING tab, you can specify sort options by selecting a managed property from the list of
sortable managed properties, specifying the order in which the results display. You can further refine the
result source by selecting a ranking model if you select the Rank option. By selecting the Add dynamic
ordering rule, you can include rules to dynamically reorder content in a result block.
After you complete your query, you can view the query text, the applicable query rules, and the variable
values.
You can manage your result sources on the Manage Result Sources page. The most common option is
to set a result source as the default for the service application, site collection, or site. You do this by
pointing to the result source, clicking the arrow that appears and then clicking the Set as Default option.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Managing Result Types
SharePoint 2013 provides a new model for
presenting search result, which is known as result
types. You can configure result types to render
search results by defining:
Rules. Rules specify when a result type is
applied. The rules reflect a number of
operator options, including:
o Equals or not equals.
o Less than or greater than comparison.
o Logical operators.
Property lists. Property lists use managed properties to define the result type. These are applied from
a drop-down list.
Rendering template. Rendering templates define the screen layout for a result type.
You can create complex result type rules by specifying multiple conditions, in addition to managed
properties.
Working with result types
You can access the Manage Result Types page from either the Site Collection Settings or Site Settings
pages. Here, you can view the service application result types, site collection result types, and the result
types defined for an individual site. These are categorized so that it is easy to see which type is defined at
each level. Depending on your access you can view, copy, edit, or delete a result type. If you copy a result
type, you can specify a new name, make changes, and save the result type at the level you are editing. For
example, if you open the Manage Result Types screen from the Site Setting page, your copied result type
is created at the site level, even if the result type you copied is from the service application category.
You can create a new result type from the Manage Result Types page by clicking New Result Type. On
the Add Result Type page, in the General Information section, you type a new result type name. Then, in
the Conditions section, you specify its result type conditions which include:
Which source should the results match? This provides a drop-down list of result sources. You can
select one or specify All Sources, which is the default option.
What types of content should match? Here, you can pick one or more content types, such as Microsoft
Word, XML, or Text. This list reflects the available result sources. You can level this selection blank to
include all result sources.
You can add more conditions by clicking Show more conditions. This enables you to add property
conditions, such as Property:Author Operator:Contains Value:John. You can add multiple values for each
property and multiple properties for each condition.
Finally, in the Actions section, you can select the display template that you wish to use for this result type.
Result type priority
Each result type in the three categories, are prioritized. When you manage result types at the site level,
you can change the priorities for the result types at that level. These are numbered 1 n, with 1 being the
highest priority. You cannot modify the priorities of other levels.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The hierarchy in result type matching is as follows:
Site
Site collection site
Search service application
This means that the results presented are based on the cumulative rule types and then rendered by
priority.
Working with Search Web Parts
Web Parts have existed in most versions of
SharePoint Products and Technologies to provide
a flexible means of building webpages in a site
that render content based on configuration
settings. SharePoint 2013 has extended the
number and range of these building blocks that
can broadly be described as search Web Parts.
SharePoint Server 2010 had, essentially, four
search Web Parts:
List View Web Part
Content Query Web Part
Search Result Web Part
Custom Web Part
SharePoint 2013 has extended this to include the following Web Parts:
Content Search. Enables you to select a result source. You can add more filters and search terms by
using Keyword Query Language.
Refinement Panel. Enables you to add refiners to a page, including refiners for faceted navigation.
Taxonomy Refinement Panel. Enables you to combine refinement with Managed Navigation to
enhance search-driven navigation experience for catalog content, when used with Managed
Navigation and associated with a Search Web Part. It works with the results from the associated Web
Part to show refiners.
Articles. Displays items of Article Page content type.
Catalog-Item Reuse. Displays detail content of catalog items. You can also use Keyword Query
Language to add more filters and terms to this Web Part query.
Items Matching a Tag. Displays items tagged with a term.
Pictures. Displays items or the Picture or Image content type.
Popular Items. Displays the most popular items that match a defined set of criteria.
Recently Changed Items. Displays recently changed items.
Recommended Items. The Recommended Items Web Part displays content recommendations based
on usage history, usually based on content in the current site, although this can be configured to
display items from a predefined URL.
Videos. Displays items of a video content type.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Web Pages. Displays items derived from the Page content type.
Wiki Pages. Displays items of the Wiki Page content type.
The majority of SharePoint professionals who work with Web Parts may be described as developers who
create custom Web Parts or power users who configure Web Parts. To work with most of these Web Parts,
the user must be a member of the Designers SharePoint group on the publishing site collection. However,
it is important that IT Professionals understand the scope of functionality available.
Additional Reading: For more information about configuring Search Web Parts, see
Configure Search Web Parts in SharePoint Server 2013 at
Discussion: Using Search to Define the User Experience
SharePoint 2013 provides more options for
developing search-driven site experience for users,
through enhanced navigation options and more
flexible search result surfacing options.
In this discussion, describe how you use search to
improve the user experience for your organization.

Search Web Parts and Navigation
Increasingly, search is being used as a driver for
site navigation, both in internal and Internet-
facing deployments. Key to developing a search-
driven navigation for your site is the use of
metadata. Two of the key Web Parts for
developing a search-driven navigation are the
Content Search Web Part and the Refiner Web
Part.
Content Search Web Part
The Content Search Web Part displays the results
of a search query that is associated with it. The
appearance of the results is rendered in a display
template, which defines the appearance and layout. This Web Part is similar to the Content Search Web
Part, but rather than querying content directly from a single site collection, the Web Part queries a search
index, providing a way to gather results from many site collections indirectly. The Content Search Web
Part is not currently available in SharePoint Online.
Configuring the Content Search Web Part
The first step in configuring a Content Search Web Part is to add the Web Part to a page. To do this, you
must be a member of the Designers SharePoint group on the publishing site collection. To do this, click
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Edit Page on the Settings menu, and then click Add a Web Part. The Content Search Web Part is found
in the Content Rollup category, under Parts.
After the Web Part is in place, you configure the query that is associated with it. This can be done in two
ways:
Quick mode. This method enables you to select options from a list of existing result sources. This is
the default option.
Advanced mode. This method enables you to create your own customer query, by using Keyword
Query Language.
Quick mode
In Quick mode, you first select a query, which enables you to select the result source that you want to use.
You can restrict this by selecting the option to only search a specific site, library, list, or URL. The default
action is to restrict results to the current site. With the result source and location restriction in place, you
can now set the term from a term set that you want to use as an additional restriction, if necessary. By
default, there is no restriction. You can limit search results by selecting one of the following options:
Restrict by navigation term of current page. You can use this option if your site uses managed
navigation. It will restrict the search results to items that are tagged with the same term as the current
page.
Restrict by current and child navigation. This works like the previous option but will include content
that is tagged with sub-terms of the current page.
Restrict on this tag. This option prompts you for a tag, which you can type into the configuration
page.
Advanced mode
When using advanced mode, you specify the following options:
Select a query. This selects a result source, which is set to Local SharePoint Results (System) by default.
Keyword filter. Keyword filters are designed to let you add query variables, which are placeholders for
value and can change depending on the page context. By clicking Add keyword filter, you can
select from a list.
Property filter. Property filters query content based on managed properties. The managed properties
must be set as queryable.
Query text. Here you type your query, using Keyword Query Language.
Additional Reading: For more information about Keyword Query Language, see Keyword
Query Language (KQL) syntax reference at http://go.microsoft.com/fwlink/?Linkid=303693
There are several tabs available on the configuration page:
Refiners (Quick and advanced mode). This displays the managed properties that are available as
refiners. These enable you to limit the returned results to the Web Part. This tab also enables you to
group results.
Sorting (Advanced mode only). You can use these options to sort managed properties in ascending or
descending order. You can select Rank to use a schema ranking model to sort by relevance. The sort
list only displays managed properties that have been defined as sortable. You can add dynamic
ordering rules to changed ranking.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Settings. On this tab, you can set options for:
o Query rules
o Loading behavior
o Priority
Test. This tab previews the query. You can see additional information by clicking Show more. This will
provide information on the following settings to be applied to the query:
o Query template
o Refiners
o Groupings
o Query rules
o Query variables
You can test the query by clicking Test query, which previews the results.
Refinement Web Part
You can use the Refinement Web Part to display refiners on a page. These use managed properties that
are configured as refiners. There are two different modes for the Refiner Web Part:
Search results
Faceted navigation
Search results
For search results, the refinersthe navigational elements shown on the left navigationare generated as
deep refiners rather than the shallow refiners which display the complete set of results, rather than top 50
results as was the case with SharePoint 2010. This will be familiar to those who previously used FAST for
SharePoint.
Faceted navigation
Faceted navigation is a method of locating information by applying filters that are based on the attributes
of crawled data. The difference between a faceted navigation and a hierarchical navigation is that the
latter is a pre-defined hierarchy, so there is far less flexibility in how navigational elements appear.
Faceted navigation uses a term set from the term store to filter the rendered data. With each term that
you select, there are managed properties that you define as refiners with that term. To do this, you must
configure the managed property as refinable.
To use this approach, you create refiners for your managed property. For example, if you have a managed
property of Bread, you may add refiners of Sliced and Unsliced, so that these appear as query
navigational refiners when a user clicks on Bread. The user can then select Sliced or Unsliced as their
next facet of the navigation.
Additional Reading: For more information refiners and faceted navigation, see Configure
refiners and faceted navigation in SharePoint Server 2013 at
Configuring a Refinement Web Part
You can add a Refinement Web Part to your page by using the same procedure used to add a Content
Search Web Part, except that you select Refinement rather than Content Search.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To configure the Web Part, you click the Refinement Web Part Menu arrow, and then click Edit Web
Part. From this page, you can configure for either search results, sometimes referred to as stand-alone, or
faceted, navigation.
Search results
Verify that Choose Refiners in this Web Part is selected, and then click Choose Refiners. This displays a
list of available refiners, which you can select and order. You can configure how each refiner appears by
configuring the options for each in the Configuration for section.
Faceted navigation
In the Properties for Search Refinement section, select the option Use the refinement configuration
defined in the Managed Navigation term set.
Configuring Search Center Sites
SharePoint 2013 provides the Search Center
template to enable you to deploy a centralized
search facility for users. A Search Center site is the
top-level site of a site collection to which you must
grant access permissions to your users and user
groups. It can be based on one of two search
center templates:
Basic Search Center template
Enterprise Search Center template
The difference between building a Search Center
based on the Enterprise Search Center template
and the Basic Search Center template is the ability to customize the user experience. In an Enterprise
Search Center, you can author your own site pages; whereas in a Basic Search Center, you can only edit
the search and search result pages delivered in the template.
The Enterprise Search Center template provides:
A default search home page (default.aspx).
A default search results page (results.aspx).
A number of search verticalspreset result categories, such as people or videos pages to display:
o People Search results (peopleresults.aspx)
o Conversation search results (conversationresults.aspx)
o Video search results (videoresults.aspx)
An advanced research page (advanced.aspx) where users can refine their search queries by applying
query text restrictions; for example, by applying an exact phrase match.
These pages contain Web Parts that the search administrator at the service application level, or the site
collection administrator at the site collection level, can configure to deliver an organizational or
departmental search experience.
To create an Enterprise Search Center, you must enable the SharePoint Server Standard Site Collection
and SharePoint Server Standard Publishing infrastructure features.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Enhancing the End-User Experience of Search
SharePoint 2013 has been redesigned to provide a
cleaner, crisper user interface for all areas of the
product. It has also extended its device interface
support to include tablet devices. Search benefits
from all of these advantages, but there are some
search-specific user experience changes that exist
in the product by default and that you can
configure to fit your users requirements.
The core SharePoint 2013 product search
functionality has been extended to include much
of the functionality that was associated with FAST
for SharePoint 2010, such as deep refiners and
document previews, which uses the functionality of Office Web Applications to render documents in a
browser interface. The function uses the Hover Panel to display not only a preview of documents. It
extends this to render the appropriate information based on the result types. Result type rules define what
the hover panel displays, so for a Word document, it displays a document preview and relevant associated
metadata, whereas for a discussion thread item displayed in a search result, it displays thread replies and
so forth.
Display templates
A major extension to the end-user search experience is the use of display templates. Again, these are
based on the functionality offered by result types. SharePoint 2013 lets you specify display templates to
define how result types are rendered on a screen, so that you can define page layouts based on business
or user requirements. These display templates are stored in the Master Pages and Page layouts folder. The
templates themselves are HTML files, which you can edit with any HTML editor, from Notepad through to
Visual Studio, including third-party products, such as Dreamweaver. It is worth noting that with each
HTML file, you will find an associated JavaScript (.js) file of the same name. These are automatically
generated by SharePoint 2013 when you create a new display template.
SharePoint 2013 ships with a number of predefined templates, which you can use to develop new versions
that you can associate with selected result types to create a unique end-user experience. You can manage
display templates at search service application and site collection levels. This means that site
administrators can add new display templates to the Master Pages and Page layouts folder. This enables
you to delegate some of the administrative responsibility and effort across your organization,
streamlining, but maintaining management of change.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Optimizing Search
When you deploy an enterprise search environment, you must understand that your search configuration,
like your content, will be in a state of constant change. SharePoint 2013 has introduced features, such as
continuous crawling, to help you ensure search content freshness, but you need to perform regular
reviews of Search performance to ensure that you deliver the best service to your users.
SharePoint 2013 has incorporated analytical processing of search performance and usage into the Search
service application. There are a number of reports that you can review to assess how well elements of
search, such as crawling and queries, are performing.
This lesson examines some of the key options available to optimize search by analyzing usage and search
reports.
Lesson Objectives
List the key analytics report available for Search.
Describe the analytics processing for search and queries.
Describe how to view and interpret the Query Health Report.
Describe how to view and interpret the Crawl Health Report.
Explain the function and use of the Crawl Log.
Analyzing Usage and Search Reports
Providing an effective search environment is a
journey rather than a destination. As trends
change or new content is promoted, the use and
usefulness of your search environment will change.
You must monitor your search performance to
ensure that your search queries and content
discoverability are effective. The usage and search
analytics reports that are available in search will
help you assess search performance. To use these
reports, they must first be configured for your
farm.
Viewing reports
Usage reports are gathered and can be viewed based on your Search service applications. To access
reports, you must log on as an administrator so that you have access to Central Administration, and then
perform the following steps:
2. On the Service Applications page, click the Search service application.
3. On the Search Administration page, in the Quick Launch, in the Diagnostics section, click Usage
Reports.
4. On the View Usage Reports page, click the usage or search reports view that you want view.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Usage analytics
The core usage report is titled Number of Queries. This displays the number of queries that have been run
so that you can identify trends. Usage analytics analyzes how search content is used by analyzing events,
such as page views logged in the event store. Page view information, for example, is stored on web front-
end (WFE) servers. This information is pushed to an event store where it is stored until it is processed by
the Analytics Processing Component. The results are then returned to the Content Processing Component
to be included in the search index. The usage events that are analyzed include:
Views
Recommendations displayed
Recommendations clicked
There are a number of sub-analyses the happen for usage analytics:
Usage counts. The Usage counts analysis analyzes events, such as views. The analysis checks the
overall number of times that an item is opened by any means, not just from a search result page. You
can set the analysis retention value as any number between one and 14 days (14 days is the default
value). The statistical data is aggregated at the following levels:
o Site level
o Site collection level
o Tenant level (SharePoint Online only)
Usage events are kept on disk for the retention value (the default value is 14 days) before they are
deleted. Every day, the previous full day of Usage counts data is analyzed. The counts are added to the
search index items to improve relevance. The analysis is also stored in the Analytics reporting database,
where this information can be used to display popular site items.
Recommendations. The Recommendations analysis creates recommendations between items based on
user activity patterns. To improve relevance, the analysis calculates inter-item relationships and adds
the information to the search index items. You can use this information to provide recommendations
based on usage by other users. This information is stored in the Analytics reporting database.
Activity ranking. Activity ranking tracks usage events to improve search relevancy. If an item has a
high view usage, it will get a higher activity rank score. The analysis identifies trends, so that older
items, which have just had more time to amass views, do not automatically get a higher ranking than
newer items, which are getting a larger number of recent hits.
Search reports
The Analytics Processing Component generates an Excel report that shows popularity trends and a listing
of the most popular items, by view. These reports include:
Popularity Trends. This records daily and monthly counts per usage event for a site collection, site, or
item in a SharePoint library or list.
Most Popular Items. This displays the ranking for items in a library or list, on a per usage event basis.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Search Analytics
The following Search reports, which are available
from the View Usage Reports page, can assist you
in improving your search experience:
Top Queries by Day. This displays the most
popular queries on a per day basis, to help
identify search trends.
Top Queries by Month. As above, but the
monthly records provide more long-term
analysis so that you do not make tuning
assumptions based on short term trends.
Abandoned Queries by Day. This identifies the
queries that were run but did not result in a click-through. This helps to identify popular queries that
are not delivering the results that users anticipate. Queries associated with these results may need to
be reviewed and re-engineered.
Abandoned Queries by Month. As above, but the monthly records provide more long term analysis so
that you do not make tuning assumptions based on short term trends.
No Result Queries by Day. This records queries that are regularly run but do not return results. This
may indicate issues in content discoverability or the need to redesign the associated query.
No Result Queries by Month. As above, but the monthly records provide more long term analysis so
that you do not make assumptions on tuning based on short term trends.
Query Rule Usage by Day. This displays how often a query rule is triggered. It also tracks how many
dictionary terms the query uses and the number of user click-throughs on promoted results.
Query Rule Usage by Month. As above, but the monthly records provide more long term analysis so
that you do not make tuning assumptions based on short term trends.
Search sub-analyses
SharePoint 2013 uses search analytics information to enhance search relevance, as well as to create search
reports, recommendations, and data links. The analysis of the number of search clicks from a search
results page can help to improve search relevance by analysis of user activities. This search analysis is
stored in the link database and is further analyzed using the following analyses:
Anchor text processing. This process analyzes how indexed content items are interlinked. Based on this
analysis, ranking points are added to interrelated items to increase their relevance to each other.
Click Distance. Click distance analyzes the distance between an indexed item and an authoritative
page. The closer an item is to an authoritative page in the number of required clicks, the more
ranking points it receives, thus improving its relevance.
Search Clicks. Search analysis reviews the popularity of an item based on the number of users who
click the item having run the query. Items that prove most popular are given more ranking points.
Social Tags. Search analysis records the tags added to an item by users. This does not directly increase
the items ranking, but it does show you which items are instigating the most tags, so that you can
use this information in your search design effort.
Social Distance. This process analyzes the relationships between People Search users to increase inter-
relationship relevance. So a search is more likely to return a relevant person who is a co-worker than
someone who has a limited business relationship to the person running the query.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Deep Links. As was previously available in FAST for SharePoint, this uses search results usage clicks to
identify and display popular subpages.
Working with Query Health Reports
SharePoint 2013 can collect a lot of information
on your users query usage, which can help you
develop your search environment. These
monitoring functions are configured in the
Monitoring section in Central Administration.
Perform the following steps to enable query data
collection:
1. On the Monitoring page, in the Reporting
section, click Configure usage and health
data collection.
2. On the Configure usage and health data
collection page, in the Usage Data
Collection section, select the Enable usage data collection check box.
3. In the Event Selection section, select the check boxes of the events that you want to log.
4. In the Usage Data Collection Settings section, type the path of the folder to which you want usage
and health information to be written in the Log file location box. The path that you specify must
exist on each server in the farm.
The query health reports provide report information on:
Query latency trend
Overall query latency
Default SharePoint flow query latency
Federation query latency
Local SharePoint Search flow query latency
People Search flow query latency
Index engine query latency
To view query health reports, perform the following steps:
3. On the Search Administration page, in the Quick Launch, in the Diagnostics section, click Query
Health Reports.
4. On the Search Service Application: Query Latency Trend page, click the query report that you
want to view.
The following query health reports are available:
Trend (Query Latency Trend). This report shows the query latency by percentile. A graph is produced
that shows the query rate during the time period you select. By default, the graph displays data for all
result pages in the Search service application.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Overall (Overall Query Latency). This report shows the number of queries per minute with an overlay
of the query latency. This latency is broken down to show rendering (WFE), object model
(communication latency between WFE and backend servers), and Backend (the time taken to process
the query, interrogate and surface the result set from the index, and return the result set to the object
model). By default, the graph displays data for all result pages in the Search service application.
Main Flow (Default SharePoint Flow Query Latency). This report shows how fast the system processes a
query and returns result sets to a web server.
Federation (Federation Query Latency). This report shows the query latency for all result source types,
such as Local SharePoint Provider, Exchange Search Provider, or OpenSearch Provider. By default, the
graph shows data for all result pages in the Search service application.
SharePoint Search Provider (Local SharePoint Search Flow Query Latency). This report shows the query
latency for all queries that are processed by the local SharePoint search provider. It breaks down the
query processing activities, including keyword parsing, security trimming, and result type processing
People Search Provider (People Search Flow Query Latency). This report shows the query latency for
queries processed by the local people search provider. It breaks down the query processing activity in
the same way as the SharePoint Search Provider.
Index Engine (Index Engine Query Latency). This report shows the query latency for each index server
that you filter on. By default, the graph shows data for all result pages in the Search service
application.
Note: In these query reports, all query latency is shown in milliseconds.
Query logging is enabled by default, and it is usually advisable to maintain query logs. There may be
circumstances in which you wish to disable query logging for a short period.
Perform the following steps to enable or disable query logging:
1. In Central Administration, in the Application Management section, click Manage service
applications.
2. On the Manage Service Applications page, click the Search service application for which you want
to configure query logging.
3. On the Search Administration page, in the System Status section, locate Query logging.
4. The Query logging status displays as OffEnable or OnDisable.
5. By default, query logging is turned On. Click Disable to turn off query logging or click Enable to turn
on query logging.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Working with Crawl Health Reports
Among the most important health reports for
Search administrators is the set of Crawl Health
reports, which enable you to review the
effectiveness of your content crawling. Because
crawl can have a noticeable effect on system and
search performance, it is important that you
rigorously monitor crawl activities.
The crawl reports are located in the Diagnostics
section of the Search Administration page.
Perform the following steps to view the reports:
1. In Central Administration, under Application
Management, click Manage service
applications.
2. On the Service Applications page, click the Search service application whose reports you want to
view.
3. On the Search Administration page, in the Quick Launch, in the Diagnostics section, click Crawl
Health Reports.
4. On the Search Service Application: Crawl Reports page, click the crawl health report that you want
to view.
The following crawl reports present screen graphs. The reports and their use are detailed in this list:
Crawl Rate. The crawl rate report shows the number of items crawled for this Search service
applications in a minute. The report displays totals for:
o Total content items. This provides an overview figure for the service application. The
recommendation is that you deploy one additional crawl database per 20 million items.
o Modified items. These are content items have changed and need to be recrawled. Use this report
to assess possible changes to crawl requirements, such as the implementation of continuous
crawls on content hosted on SharePoint.
o Not modified items. This displays content items that were not changed and were not crawled.
Again, this may prompt you to amend your search schedule. You should review whether the
source is an archive that does not need to be crawled.
o Security items. You should review this report to identify issues with access to content that you
wish to crawl.
o Deleted items. This report displays items that have been deleted and should be deleted from the
index.
o Average number of other crawl actions that were performed per minute. Review the details of
this for retries and errors in crawls.
Crawl Latency. This graph shows the crawl load for the service application and can be filtered by
server. Specific areas that contribute to crawl latency include:
o In Crawler Queue
o Waiting to submit to content processing
o Submitted to content processing
o Waiting to Commit (SQL)
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Increases in these numbers over time will indicate that you should review the number of available crawl
databases.
Crawl Queue. This displays information on two crawl queues:
o Links to process. Shows the number of URLs queued but yet to be crawled.
o Transactions queued. Shows the number of crawled URLs yet to be processed into the link
database.
Increases in these numbers may indicate a need to add an additional link database. This is recommended
per every 60 million items.
Crawl Freshness. This graph shows the freshness of your indexed content. Content is time stamped
and rated against its Last Modified time stamp. Degradation in the crawl freshness metrics may
indicate that you need more crawl databases and Content Processing Components to improve result
freshness.
Content Processing Activity. This shows the amount of time spent processing content by content
source, machine, content processing component, and content processing activities, such as document
parsing or indexing. Again, increases in these statistics may prompt you to review the number of
Content Processing Components deployed in your search environment.
CPU and Memory Load. This indicates the CPU and memory usage by the search filter
(MMSDmn.exe), the Windows Service that hosts the Crawl Component (MSSearch.exe), the process
that hosts the search components (NodeRunne.exe), and the timer job.
Continuous Crawl. This displays the time (in milliseconds) that the processes took with an overlay of
discovery time (in minutes) for:
o Time In Links Table
o Time In Queue Table
o Crawler Time
o PH (Protocol Handler) Time
o Repository Time
o Content Pipeline Time
o SQL Time
The Crawl Log
Successful crawling is essential to a Search service.
To help you manage your crawl effectiveness,
SharePoint 2013 provides the Crawl Log, which
tracks crawl activity. The log assists in determining:
The success of added crawled content to the
index.
The effect of crawl rules.
Errors affecting crawls.
Perform the following steps to view the crawl log:
1. In Central Administration, under Application
Management, click Manage service applications.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
3. On the Search Administration page, in the Quick Launch, in the Diagnostics section, click Crawl
Log.
4. On the Crawl Log Content Source page, click the view that you want.
The crawl log provides the following information, which you can use to diagnose issues:
Content Source. This provides detailed analysis of the content sources that your service application
crawls. The report indicates successful activities, warning, errors, and deleted items. It also indicates
the average time to complete a content crawl for the content source, which helps you to identify
sources which may be becoming too large or may benefit from a continuous crawl schedule.
Host Name. This provides similar information to the Content Source option, but by host machine.
Crawl History. This view, from the Search Administration database, shows the number of crawl
transactions that take place during a crawl. This will be more than the total crawled items, because
there can be multiple transactions per item. The crawl history provides information for full,
incremental, and continuous crawls. This option also shows the crawl rate, as detailed in Working with
Crawl Health Reports, and the repository latency.
Error Breakdown. This displays a summary of errors for content sources and hosts, based on
information from the crawl databases.
Databases. Reports on the crawl databases.
URL View. This uses the Display URL to identify log items. The URL Viewer enables you to search the
log by:
o Content source
o URL
o Host name
This can display a lot of information, so you can filter for specific issues by:
o Status
o Message
o Start Time
o End Time

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Managing Search Relevance in SharePoint Server
2013
Scenario
The management team at Contoso wants to encourage the use of search as a way of improving the
efficiency of information workers. To boost adoption of search, the search experience needs to be as
helpful and as user-friendly as possible. Your task is to implement various features to aid this process.
Objectives
Configure a thesaurus.
Configure custom entity extraction.
Configure query spelling correction.
Configure company name extraction.
Passw0rd: Pa$$w0rd
Exercise 1: Configuring a Thesaurus
Scenario
People often use a range of different terms and phrases to refer to the same thing. This can make search a
frustrating process. For example, you may find that the term "first aid" returns search results, while the
term "emergency treatment" does not. After reviewing the query logs, you have identified various terms
from failed queries that are synonyms for successful query terms. In this exercise, you will implement a
thesaurus to help users find the right results the first time.
1. Test search limitations
2. Create a thesaurus file
3. Import a thesaurus file
4. Test the thesaurus
Task 1: Test search limitations
Log on to the 20332B-NYC-SP-08 virtual machine as Contoso\Administrator with the password
Pa$$w0rd.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In Internet Explorer, browse to sharepoint.contoso.com/search. Log on as
In the Search Center, search for Painkillers. Notice that the search returns no results.
Search for Analgesics, and notice that the search returns a datasheet.
Search for Emergency Aid. Notice that the search returns no results.
Search for First Aid, and notice that the search returns a datasheet.
Search for Indigestion Remedy. Notice that the search returns no results.
Search for Digestive health, and notice that the search returns a datasheet.
Task 2: Create a thesaurus file
Use Notepad to open the thesaurus file at E:\Mod08\Starter\ContosoThesaurus.csv.
Add entries to map the following synonyms:
Map Painkiller to Analgesic.
Map Analgesic to Painkiller.
Map First aid to Emergency care.
Map First aid to Emergency treatment.
Map First aid to Emergency assistance.
Map Emergency care to First aid.
Map Emergency treatment to First aid.
Map Emergency assistance to First aid.
Map Indigestion to Digestive health.
Map Indigestion remedy to Digestive health.
Map Digestive health to Indigestion.
Map Digestive health to Indigestion remedy.
Save and close the thesaurus file.
Note: Thesaurus entries are not case-sensitive.
Task 3: Import a thesaurus file
Use Windows PowerShell to import the thesaurus file.
Note: The Import-SPEnterpriseSearchThesaurus cmdlet requires that you specify the file location
as a UNC path. Use the path \\NYC-SP1\Starter\ContosoThesaurus.csv.
Task 4: Test the thesaurus
In Internet Explorer, browse to the Search Center at sharepoint.contoso.com/search. Log on as
Search for Painkiller. Notice that the search returns a datasheet that matches the term Analgesics.
Search for Emergency assistance. Notice that the search returns a datasheet that matches the term
First aid.
Search for Indigestion remedy. Notice that the search returns a datasheet that matches the term
Digestive health.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

Results: After completing this lab, you should have created and imported a thesaurus.
Exercise 2: Configuring Entity Extractors and Refiners
Scenario
Over the years, Contoso divisions have operated under various trading names, which is reflected in the
content on the companys SharePoint intranet portal. Contoso management wants Search users to be able
to filter search results by the two primary divisions: Contoso Pharmaceuticals and Contoso Research. Your
task is to create a custom entity extraction dictionary that maps each of the naming variations to either
Contoso Pharmaceuticals or Contoso Research. You will then import the custom entity extraction
dictionary and map it to a managed property. Finally, you will create and test a search refiner that enables
users to filter by division.
1. Create a custom entity extraction dictionary
2. Import the custom entity extraction dictionary
3. Map the custom entity extraction dictionary to a managed property
4. Add a refiner for the custom entity extractor
Task 1: Create a custom entity extraction dictionary
Use Notepad to open the thesaurus file at E:\Mod08\Starter\ContosoBrandEntities.csv.
Add entries to map the following keys and display forms:
Map Contoso Pharm to Contoso Pharmaceuticals.
Map Contoso Pharma to Contoso Pharmaceuticals.
Map Contoso Consumer Pharmaceuticals to Contoso Pharmaceuticals.
Map Contoso R&D to Contoso Research.
Map Contoso R & D to Contoso Research.
Map Contoso R and D to Contoso Research.
Map Contoso Laboratories to Contoso Research.
Save and close the file.
Task 2: Import the custom entity extraction dictionary
Use Windows PowerShell to import the thesaurus file.
a. Use the Import-SPEnterpriseSearchCustomExtractionDictionary cmdlet.
b. Set the Filename property to \\NYC-SP1\Starter\ContosoBrandEntities.csv.
c. Set the DictionaryName property to
Microsoft.UserDictionaries.EntityExtraction.Custom.Word.2.
Task 3: Map the custom entity extraction dictionary to a managed property
Using the Central Administration, website, configure the body managed property to extract custom
entities of type Word Extraction Custom2.
Start a full search crawl on the Local SharePoint sites content source. Wait for the search crawl to
complete before you continue.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: The search crawl may take a few minutes to complete.
Task 4: Add a refiner for the custom entity extractor
In Internet Explorer, browse to sharepoint.contoso.com/search.
Run any search query to take you to the search results page.
On the search results page, edit the Refinement Web Part to include the WordCustomRefiner2
managed property.
Note: When SharePoint extracts entities of type Word Extraction Custom2 from the body
managed property, it copies the extracted entities to the WordCustomRefiner2 managed property.
Configure the new refiner to display the name Contoso Division, and ensure that you apply your
changes to the Refinement web part.
Check in and publish the search results page.
Run a search for ContentType:Invoice, and verify that the Contoso Division refiner appears on the
left of the page.
Under Contoso Division, click Contoso Research.
Verify that the search results page displays a filtered list, and then click the title of one of the search
results.
When you are prompted for credentials, log on as CONTOSO\Administrator with password
Pa$$w0rd.
When the document opens, verify that the invoice is addressed to one of the terms you mapped to
Contoso Research in the custom entity extraction dictionary.
Close Word.
On the search results page, under Contoso Division, click All, and then click Contoso
Pharmaceuticals.
Verify that the search results page displays a filtered list, and then click the title of one of the search
results.
When you are prompted for credentials, log on as CONTOSO\Administrator with password
Pa$$w0rd.
When the document opens, verify that the invoice is addressed to one of the terms you mapped to
Contoso Pharmaceuticals in the custom entity extraction dictionary.
Close Word, and then close Internet Explorer.

Results: After completing this exercise, you should have created and imported a custom entity extraction
dictionary and created a search refiner that uses the custom entities to filter search results.
Exercise 3: Configuring Query Spelling Correction
Scenario
After reviewing the search query logs, you have noticed various words that users regularly misspell in
search queries. In particular, people often struggle to spell the names of the pharmaceutical products that
are manufactured by Contoso. In this exercise, you will add these terms to the Query Spelling Inclusions
dictionary. When users search for one of these words by using an incorrect spelling, SharePoint will then
provide a Did You Mean suggestion that enables the user to search again using the correct spelling.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
1. Test spelling correction limitations
2. Populate the Query Spelling Inclusions term set
3. Force SharePoint to update the custom dictionaries immediately
4. Test the spelling dictionary updates
Task 1: Test spelling correction limitations
In the search box, type Analgesacs (a deliberate misspelling of analgesics), and then press Enter.
Verify that the search returns no results.
In the search box, type Acetamophen (a deliberate misspelling of acetaminophen), and then press
Enter. Verify that the search returns no results.
Task 2: Populate the Query Spelling Inclusions term set
On the Central Administration website, browse to the Search Dictionaries group in the Managed
Metadata term store.
Within the Search Dictionaries group, add the following terms to the Query Spelling Inclusions
term set:
o Analgesic
o Acetaminophen
Task 3: Force SharePoint to update the custom dictionaries immediately
Using either the Central Administration website or Windows PowerShell, locate and run the Search
Custom Dictionaries Update timer job.
Task 4: Test the spelling dictionary updates
In the search box, type Analgesacs, (a deliberate misspelling of analgesics), and then press Enter.
Notice that the search results page displays the message Did you mean Analgesic?
Click Analgesic, and verify that the search results page returns a datasheet.
In the search box, type Acetamophen (a deliberate misspelling of acetaminophen), and then press
Enter.
Verify that the search results page displays the message Did you mean Acetaminophen?
Click Acetaminophen, and verify that the search results page returns a datasheet.

Results: After completing this exercise, you should have populated and tested the Query Spelling
Inclusions dictionary.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 4: Configuring Company Name Extraction
Scenario
Much of the content on the SharePoint intranet portal relates to Contoso's five main suppliers: Litware,
Inc., Proseware, Inc., Northwind Traders, Trey Research, and Wide World Importers. Where relevant, Search
users would like to be able to use these company names to filter search results. In this exercise, you will
configure company name extraction to find these company names. You will then configure a search
refiner to enable users to filter by company name.
1. Populate the Company Inclusions term set
2. Force SharePoint to update the custom dictionaries immediately
3. Enable company name extraction on a managed property
4. Add a refiner for company names
Task 1: Populate the Company Inclusions term set
On the Central Administration website, browse to the Search Dictionaries group in the Managed
Metadata term store.
Within the Search Dictionaries group, add the following terms to the Company Inclusions term set:
o Litware, Inc.
o Proseware, Inc.
o Northwind Traders
o Trey Research
Using the Central Administration website, run the Search Custom Dictionaries Update timer job.
Task 3: Enable company name extraction on a managed property
In Central Administration, configure the body managed property to extract company names.
Start a full search crawl on the Local SharePoint sites content source.
Note: The search crawl may take some time to complete. You can continue before the search crawl is
complete, but you may find that the search results in the next exercise are limited.
Task 4: Add a refiner for company names
Run any search query to take you to the search results page.
On the search results page, edit the Refinement Web Part to include the companies managed
property.
Note: When SharePoint extracts company names from the body managed property, it copies the
names to the companies managed property.
Configure the new refiner to display the name Contoso Division, and ensure you apply your changes
to the Refinement web part.
Check in and publish the search results page.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Run a search for ContentType:Invoice, and verify that the Partner Organization refiner appears on
the left of the page.
Under Partner Organization, click Litware, Inc.
Verify that the search results page displays a filtered list.
Click other items under Partner Organization and verify that the search results are updated
accordingly.

Results: After completing this exercise, you should have configured company name extraction and
configured a search refiner to filter search results by company name.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Having completed this module, you should now be able to:
Describe the Search service architecture and key areas of configuration.
Explain how to configure the Search service to improve the end-user experience.
Describe how to use analytics reports to optimize your Search environment.
Review Question(s)
Test Your Knowledge
Question
Which Search architecture component uses connectors to complete its processing?

Analytics Processing Component
Content Processing Component
Crawl Component
Indexing Component
Query Processing Component
Test Your Knowledge
Question
You review your Crawl Report and see that in the Crawl Rate the total content items
number 45 million. You currently have two crawl databases, four index partitions, two
query processing components, one link database, and four analytics databases. What
should you do?

Add a new crawl database to manage the increased number of content items.
Add a new query processing component to process this volume of content?
Add an additional link database.
Add two additional crawl databases to manage the increased number of content
items.
Nothing, based on this information.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Test Your Knowledge
Question
Your developer colleagues want to take advantage of the flexibility offered by Display
templates. Which development tools should they use?

Visual Studio
Any XSLT editor
SharePoint Designer
Any HTML editor
Dreamweaver

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
9-1
Module 9
Planning and Configuring Enterprise Content Management
Contents:
Module Overview 9-1
Lesson 1: Planning Content Management 9-2
Lesson 2: Planning and Configuring eDiscovery 9-8
Lab A: Configuring eDiscovery in SharePoint Server 2013 9-14
Lesson 3: Planning Records Management 9-19
Lab B: Configuring Records Management in SharePoint Server 2013 9-24

Module Overview
Enterprise Content Management (ECM) is a set of technologies and features that administrators use to
provide some control over sites and content. This could include control over how information is stored,
how long information is kept, how information is visible to users while in use, and how information
growth is kept under control.
Planning support for your ECM requirements requires a clear understanding of content requirements and
how that content supports the organization. This means that, as a best practice, many different
organizational roles should have input into the ECM strategy and supporting features.
Objectives
Plan how to manage content and documents.
Plan and configure eDiscovery.
Plan records management and compliance.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
9-2 Planning and Configuring Enterprise Content Management
Lesson 1
Planning Content Management
In order to plan your Enterprise Content Management strategy, it is important to understand the features
and functions that SharePoint includes to help manage content. You must plan to use the appropriate
features to control information growth, aid with compliance requirements, control item retention, provide
email integration, and control database storage.
Lesson Objectives
Describe document and file management capabilities in SharePoint.
Plan information management policies.
Plan large document repositories.
Configure site-based retention.
Add site mailboxes to SharePoint.
Describe shredded storage.
Document and File Management in SharePoint
Document and file management is one of the key
tenets in SharePoint enterprise content
management, along with Web Content
Management (WCM), and records management.
Document and file management
There are a number of features available to help
you manage documents and files within your
SharePoint farm. Administrators choose to
implement features that are required to meet
functionality requirements, support organization
working practices, promote best practice, or
support compliance requirements. The following
document and file management features are present in SharePoint 2013:
Check-out and check-in. Checking out documents promotes sequential working when several
individuals need to collaborate on a single document, but one individual needs to work on the
document at one time, or perhaps perform document editing while offline.
Document co-authoring. SharePoint 2013 enables co-authoring of several Microsoft Office document
types by default, so that two or more authors can make changes to the same document at the same
time. Co-authoring of Excel workbooks requires Office Web Apps.
Document versioning. You can store each version of a document that is uploaded by a contributor.
Document versions can be set to keep major versions only, or both major and minor (or draft)
versions. Versions require additional storage considerations; however, in SharePoint 2013 only the
changes to a document are stored as the new version.
Content approval. The content approval feature allows for a more controlled publishing process. After
an author considers a document ready for wider consumption, approval is required from a user with
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
approval permissions. This prevents authors from publishing content before managers consider it to
be complete, or perhaps free from errors.
Document sets. Document sets provide the ability to manage a piece of work that may contain or
output multiple files as one entity in SharePoint. This includes the ability to apply metadata, apply
retention policies, and use the content organizer. In SharePoint 2013 document sets support
OneNote notebooks and have improved search support.
Content types. Content types are an important part of document management and information
architecture in SharePoint. Content types enable you to define a type of file, such as a budget
statement, with associated metadata and information policies. You can propagate content types
beyond a single site collection by using a content type hub in conjunction with the Managed
Metadata service application.
Document IDs. In SharePoint, a document ID is a kind of unique serial number which can be applied
to every document in a site collection. Document IDs can be useful to help users identify a specific
document without confusion or to help with document tracking and location.
Content organizer. The content organizer is a SharePoint feature that enables routing of submitted
documents to subfolders or different libraries based on document properties, such as metadata.
Planning Information Management Policies
As part of an ECM strategy, it is important to
consider the types of documents, files, and
information that will be stored in SharePoint and
that may have specific compliance and retention
requirements. You can use an Information
Management Policy to apply retention settings,
audit requirements, and labeling settings to items
that are stored within SharePoint.
For example, suppose an organization has to
follow strict government regulations that require it
to demonstrate proper control and management
of its financial statements. The organization may
create several information management policies that audit the actions of staff members who author and
approve documents that are related to financial filings.
The following table describes the information management policy features that are available in
SharePoint:
Policy feature Description
Retention This policy feature helps to retire or process content in a consistent
way that you can track and manage. When a content item expires, you
can specify the rules for its automatic disposal or define a custom
workflow that runs when the retention period occurs.

Auditing This policy feature logs events and operations that are performed on
documents and list items. You can configure Auditing to log events
such as editing, viewing, checking-in, or deleting a document or item.
Barcodes This policy feature enables you to track printed copies of a document
by creating a unique identifier value for the document in SharePoint.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Policy feature Description
The user then inserts a barcode image of that value in the document.
Custom You can also create and deploy custom policy features to meet your
specific organizational needs, but you must implement them by using
the SharePoint 2013 object model or acquire them from a third-party
software vendor.
For example, a manufacturing organization may want to define an
information management policy for all draft specification documents
for product design that prohibits users from printing copies of these
documents on unsecure printers. In this scenario, the organization can
create a Printing Restriction policy feature and add it to the relevant
information management policy for the product design specification
content type.
Applying information management policies
You can apply information management policies to content types, lists, or libraries. By default, if there is a
conflict between two policies, the content type policy will take precedence; however, the Library and
Folder Based Retention site collection feature reverses this behavior if desired.
Planning Large Document Repositories
Some organizations will need to store large
amounts of documents and files in SharePoint.
This storage requirement can be for any number
of reasons, such as the need for versioning large
numbers of documents, having a large number of
files marked as records and needing eDiscovery, or
simply having a large number of documents that
utilize features such as managed metadata. In
these cases, you must determine the best way to
store a large amount of content in SharePoint that
satisfies the needs of your organization and your
users.
When deciding how to store your content, your planning should take into account two effective
thresholds, which create the following categories:
1. Store content in site collections smaller than 200 GB each.
2. Store content in site collections smaller than 4 TB each.
3. Store content in a site collection that will grow beyond 4 TB in size.
Scenario (a) means that you will split up content into a large number of site collections, so that elements
such as site collection URL, navigation links, and Search will provide users with the way to find what they
need. Although this method spreads the content out and may make it harder for users to navigate, the
content databases are easier to back up, restore, and perform maintenance operations on. There are no
special requirements for content databases smaller than 200 GBs to be supported.
Scenario (b) allows you to be free of many constraints that sub-200 GB site collections create. You can
have fewer, larger site collections, with fewer custom navigation requirements. However, content
databases between 200 GB and 4 TB are only supported when the following conditions are met:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Disk sub-system performance of 0.25 IOPs per GB. 2 IOPs per GB is recommended for optimal
performance.
Plans for high availability, disaster recovery, future capacity, and performance testing should be in
place. Note that you should not expect SharePoint native backup tools to meet your backup
requirements for content databases of this size. You should also consider how long it will take to back
up and restore a content database of this size, and what effect this will have on your disaster recovery
plans and any service level agreements which may have been agreed.
Scenario (c) allows you to keep much larger content databases if desired. It is important to understand
that although this is a supported scenario given the correct conditions, it is not a recommended scenario.
Even for large amounts of content, it would be recommended to split the content up across site
collections that are smaller than 4 TB each. In order for a content database larger than 4 TB to be
supported, you must meet the requirements for scenario (b), such as disk subsystem performance and
planning requirements, in addition to the following:
Only the Document Center or Records Center site templates should be used.
An average of less than 5 percent of the content in the content database will be accessed each
month.
An average of less than 1 percent of content will be modified or written each month.
The site should not allow alerts, workflows, link fix-ups, or item level security on any objects, although
receiving documents through a workflow in a different site collection in a different database is
permitted.
Note: If you plan to use remote BLOB storage (RBS) to improve performance and reduce
SQL database file size, you must be aware that the threshold values and guidelines used above
represent the figure after combining the value of the database file size and the sum total of
associated RBS data.
Additional limits
When planning for large document repositories, you should also take account of the following list and
library level limits that exist within SharePoint 2013:
A content database is unsupported if it contains more than 60 million items.
A single library (or list) is unsupported if it contains more than 30 million items.
A view, by default, will not be processed in normal working hours if there are more than 5,000 items.
A single file to be stored in SharePoint cannot be larger than 2 GB.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Configuring Site-Based Retention
In SharePoint 2013, you can create site policies
that control how long a whole site is retained, and
the actions that occur after this predefined period
is reached.
In order to create site policies, you must activate
the Site Policy site collection feature. When the
feature is active, you can create site policies at the
root level of the site collection. After creating a
sub-site, you can choose to apply an existing
policy to the site, although no policy is applied by
default.
Site policies provide the following options:
Never delete the site automatically
Delete the site automatically at a predefined interval after the site is created, or at a predefined
interval after the site is marked as closed
Close the site automatically at a predefined interval after the site is created, and delete the site at a
predefined interval after the site is closed
Closing a site does not delete the content, but it removes the site and content from elements that
perform content aggregation, such as Outlook or Project Server. After a site policy is applied to a site, site
owners can also manually close (and reopen) sites, and manually postpone the closure or deletion date.
Site policies are a method to help prevent site sprawl within a site collection, so that the number of sites
can be kept under some form of control if site owners neglect to delete a site after it has fallen out of use.
Adding Mailboxes to SharePoint
Site mailboxes are a new feature in SharePoint
2013. Their purpose is to provide a more coherent
approach to the way email and documents are
handled by a collaborative team or project when
using SharePoint.
Typically, an organization with SharePoint will
want to use their SharePoint environment for
document collaboration and storage; however, all
the email messages relating to that team or
project will often be sent to a distribution group
that includes the team members or project
participants. In previous versions of SharePoint, it
can be difficult to examine a complete set of email messages that have been sent regarding the project. In
SharePoint 2013, you can configure integration with Exchange Server 2013 so that a SharePoint site can
have an Exchange mailbox allocated, called a site mailbox. The site mailbox enables storage of email in
Exchange 2013, but team members can view the mailbox using Outlook or by using the associated
SharePoint site. This enables a more integrated view of documents and related email messages to the
team.
In order to create site mailboxes, you must configure server-to-server authentication between SharePoint
Server 2013 and Exchange Server 2013 and activate the relevant feature.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: It is possible to automatically set certain site mailbox properties, such as mailbox
quotas, by using the SiteMailboxProvisioningPolicy cmdlets, such as New-
SiteMailboxProvisioningPolicy, in the Exchange Management Shell (EMS).
What Is Shredded Storage?
Shredded storage is a new feature provided with
SharePoint 2013 that affects the way updates are
made to Binary Large Objects (BLOBs) that are
stored in SQL Server.
When a file, such as a Word document or
PowerPoint presentation, is stored in a library in
SharePoint, the file is stored as a BLOB in SQL
Server. Prior to SharePoint 2010, if a user updated
a file in a SharePoint library, the whole file would
be uploaded to SharePoint from the client.
To improve performance, SharePoint 2010,
allowed the client to upload just the changes to
the file as a delta. In SharePoint 2010, the web front end (WFE) server receives this delta, retrieves the
whole of the original copy of the file from SQL, integrates the delta to the original file and writes an entire
new copy of the file back to SQL. Although this method improves the performance between the WFE
server and the client because only changes are uploaded, it places a heavy burden on WFE and SQL
performance as more work needs to be completed by these roles.
In SharePoint 2013, shredded storage takes the delta uploaded by the client and writes the delta directly
back to SQL, without creating a new, complete copy of the file. When a user requests a download of the
updated file, SharePoint retrieves the original copy of the file and whatever deltas have been applied
since, and then reintegrates these into a single file download which is the current copy of the document.
This improves I/O performance for document changes and collaborative working in particular, but it can
reduce performance for some upload and download scenarios. Shredded storage is always enabled in
SharePoint 2013, regardless of whether you are using document versioning, and cannot be disabled.
An additional benefit with shredded storage is realized when using document versioning on libraries.
When you enable document versioning in previous versions of SharePoint, each version of a document is
stored as a full copy of the document, which could significantly increase storage capacity requirements.
With shredded storage in SharePoint 2013, each document version only has the delta stored, which
greatly decreases the storage requirements associated with versioning in previous versions of SharePoint.
Reference Links: For more information about shredded storage, see Introduction to
Shredded Storage in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=303695

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Planning and Configuring eDiscovery
Organizations must often respond to different types of information requests, which may come from other
areas of the organization, be related to an external standards body, or be a legal requirement or case in
progress. These requests are often times satisfied through search requests in SharePoint. You can leverage
the search capabilities in SharePoint by using the eDiscovery functionality provided in SharePoint 2013.
This includes source and case management tools, along with the ability to retrieve mailbox content from
exchange 2013 and the ability to export all discovered content.
Lesson Objectives
Describe the purpose of eDiscovery.
Configure eDiscovery in SharePoint 2013.
Describe the process for managing eDiscovery cases.
Describe the purpose and behavior of in-place holds.
Configure Exchange Server 2013 integration with eDiscovery in SharePoint 2013.
Plan eDiscovery in SharePoint 2013.
What Is eDiscovery?
Electronic discovery, or eDiscovery, is the process
of identifying and displaying information stored in
electronic formats, such as files in SharePoint, that
are needed as evidence.
SharePoint 2013 provides a new site collection
template for eDiscovery, called the eDiscovery
Center. An eDiscovery Center template enables
you to search for content in the parent SharePoint
farm and across file shares, Exchange Server 2013,
and other SharePoint farms. After discovery,
matching content can be placed on hold. Content
on hold cannot be deleted by users or by a
retention policy and, although users can still work with and make updates to the content, a version of the
content is preserved as of the time the hold was initiated.
You can also use the eDiscovery Center to export content that has been discovered into an industry
standard format.
eDiscovery cases
You perform discovery of information in an eDiscovery Center by creating an eDiscovery case. In
SharePoint, an eDiscovery case is a SharePoint site, created as a child site of the eDiscovery Center, which
contains one or more eDiscovery sets and one or more eDiscovery queries.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
eDiscovery sets
Each eDiscovery case can contain one or more eDiscovery sets. Each eDiscovery set has the following:
Sources. Sources define a location that will be searched. Sources can include SharePoint sites,
Exchange Server 2013 mailboxes, and file shares.
Filter. A filter defines the search criteria. Filters can include search terms, keywords, date ranges, and
metadata, such as the author.
Hold. A hold provides the option to preserve the discovered content in its current state and location,
while allowing users to continue working on the content.
eDiscovery queries
You can use eDiscovery queries to find and export content. An eDiscovery query contains the following:
Documents. You can export documents and their versions from SharePoint 2013. You can also export
documents from file shares.
Lists. If a SharePoint list item is included in the query results, the entire list is exported as a comma-
separated values (.csv) file.
Pages. You can export SharePoint pages, such as wiki pages or blogs, as MIME HTML (.mht) files.
Exchange objects. You can export content from an Exchange Server 2013 mailbox, such as tasks,
calendar entries, contacts, email messages and attachments. Mailbox content is exported as a.pst file.
You can also discover and export Lync conversations if the conversations have been archived in
Exchange.
XML manifest. The XML manifest file provides an overview of the exported information. This
information is presented in the electronic discovery reference model (EDRM) format.
Note: EDRM is a standard for eDiscovery that was designed to improve transfer of
electronically stored information (ESI) between different applications involved with eDiscovery.
Configuring eDiscovery in SharePoint 2013
For content to be discoverable, eDiscovery users
must have at least read permissions on the
content.
You must complete the following steps to
configure eDiscovery in SharePoint 2013:
1. Grant permissions for all discoverable content
to eDiscovery users.
There are two key methods for granting an
eDiscovery user access to all necessary
content:
a. Grant read permissions at the web
application level with a user policy.
b. Grant read permissions at each site collection or site level.
2. Configure the SharePoint search service application to crawl all discoverable content.
3. Create a site collection using the eDiscovery center template.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4. Grant the eDiscovery users at least the read and create subsites permission levels on the eDiscovery
center site collection.
5. Configure communication between SharePoint Server 2013 and Exchange Server 2013 to include
mailbox content in eDiscovery. This step is optional.
Managing eDiscovery Cases
Managing eDiscovery cases involves a number of
steps that can only be performed by users with the
required permissions. In order to create an
eDiscovery case, users must have the Create
Subsites permission on the eDiscovery Center site.
By default, only the associated owners group for
the eDiscovery Center site has the Create Subsites
permission.
To create and manage an eDiscovery case,
1. Create a new eDiscovery case. At the
eDiscovery Center site, click the Create new
case button. You must complete the New SharePoint Site page with a Title and URL name, because
each eDiscovery case has a unique SharePoint site. Optionally, you can also add a description, set
unique permissions for the site, and set navigation options for the site.
2. Create eDiscovery sets. You use eDiscovery sets to initially discover content and ensure that the
current version of any discovered items is preserved while the investigation is underway.
a. On the eDiscovery case home page, under eDiscovery Sets, click new item.
b. On the New: eDiscovery Set page, add a name for the eDiscovery set.
c. Click Add & Manage Sources. In the Add & Manage Sources dialog box, you can add
Exchange 2013 mailboxes to search. You can also specify paths for SharePoint locations or file
shares to search. When you enter a SharePoint URL and click OK, the eDiscovery set will match
the URL to a specific site collection or site, but the eDiscovery set can still include content that
matches the path, not just the site collection. For example, if you add the Contoso Intranet home
page URL (http://intranet.contoso.com) to the eDiscovery set, SharePoint will list the source for
the eDiscovery set as Contoso Intranet, but the eDiscovery set will still include content from
http://intranet.contoso.com/sites/sales.
d. Under Filter, you can enter text keywords that you are searching for. You can use the wildcard
character (*) at the end of words in the keyword filter and you can use search operators, such as
AND, OR, NOT, and quotes. You can also apply additional filter criteria, such as a date range, the
author or sender properties, and a specific domain for email. Click the Preview Results button if
you want to see a detailed list of items that match the filter.
e. Choose whether you want to enable in-place hold for the content matching the filter. The default
value for this setting is disabled. After your eDiscovery set is complete, click Save.
3. Create queries. You use queries to identify and export discovered content for presentation and review
outside of the SharePoint environment.
a. On the eDiscovery case home page, under Queries, click new item.
b. On the Query: New Item page, add a name for the query.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
c. Choose which sources will be used for the query. By default, the query is restricted to the existing
eDiscovery sets in this eDiscovery case. However, you can choose to select only specific
eDiscovery sets, or select specific sources that have been defined within the eDiscovery case.
d. In the Query box, you can enter keywords to further refine the results from your eDiscovery sets.
You can also use a date range, or the author or sender fields to find specific results. After you
click Search, the Query Statistics section of the page is updated with the number of items
matching each keyword in the search.
e. You can also further refine your search by selecting certain types of Exchange content, such as
email or meetings, and you can refine SharePoint content by file extension, author, content type,
content class, title, or web template.
f. Click Save to save the query, you can also click Export to export a report of the matches to your
query or to export copies of the content that the query returned.
Note: When you export content by using a query, SharePoint launches the eDiscovery
Download Manager tool to perform the download.
Using In-Place Holds
You can preserve content that may be required as
part of an investigation by using in-place holds
within the eDiscovery Center. You can use an
eDiscovery set within a case to enable an in-place
hold. After enabling the in-place hold, all content
will be preserved as it was at the time the hold was
enabled. Users can continue to work with content
and even update and delete files in the original
locations, but a copy will be available to users of
the eDiscovery Center until the hold is disabled.
At the site level, a special library called a
preservation holds library is created when the in-
place hold is enabled. This library is used to hold content that is on hold if a user attempts to update or
delete the item. For example, if a user edits a document that has an in-place hold applied, SharePoint
determines if this is the first time that content has been changed since the hold was applied. If this is the
first change, SharePoint copies the content to the preservation hold library, and allows the user to
continue with the change.
Note: Only site collection administrators have permission to view the preservation holds
library.
The Information Management Retention Timer job cleans up preservation hold libraries by running
periodically to compare content in the preservation hold library with eDiscovery set filters that place
content on hold. If the content in a library no longer matches a hold, the preserved content is deleted.
This also means that when an investigation is complete and the corresponding eDiscovery case is deleted,
preservation hold library content will also be removed.
An in-place hold only preserves the version of the content at the time the hold is applied. An in-place
hold will not continually add new versions of content to the preserved content. For example, if an in-place
hold is applied to a document currently at version five, this version will be preserved while the hold is
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
continued. However, users may continue to update the content, and another hold is applied at a later
date. This hold applies to version eight of the same document; therefore, assuming no further holds are
applied, only versions five and eight of the document are preserved.
Configuring Exchange Integration for eDiscovery
In SharePoint 2013, eDiscovery can include the
contents of Exchange Server 2013 mailboxes by
utilizing the multi-mailbox search mechanism
provided in Exchange 2013. In order to provide
discovery of Exchange 2013 mailboxes, you must
configure server-to-server authentication between
your SharePoint 2013 farm and your Exchange
2013 environment.
Prerequisites
There are specific prerequisites that are not
required for SharePoint eDiscovery alone, but are
required before you configure server-to-server
authentication for Exchange 2013 and SharePoint 2013. The App Management service application is a
prerequisite for configuring Exchange 2013 integration. You will need to create this service application if it
is not already provisioned in your farm.
You should also configure server-to-server authentication between two endpoints that use HTTPS in order
to protect the security token being exchanged. You should ensure that the certificate being used for the
autodiscovery virtual directory on the Exchange server is trusted by servers in the SharePoint farm. You
should also ensure that the web application and site collections for which you plan to grant access to
Exchange are accessible by HTTPS.
Use the following procedure to configure Exchange Server 2013 integration for SharePoint eDiscovery:
1. Install the Exchange Web Services Managed API on each SharePoint 2013 server in the farm. You
must use the following command to perform the installation in order to correctly register the
necessary components in SharePoint:
msiexec /i EwsManagedApi.msi
addlocal=ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac
2. Ensure that you have the SPShellAdmin role on the following databases:
a. The database used by the App Management service application
b. The content database with the root site for the web application that you will grant the Exchange
service principal access to, which is typically your intranet web application
3. Configure server-to-server authentication for Exchange 2013 on a SharePoint 2013 server:
a. Enable Exchange 2013 as a trusted security token issuer in SharePoint 2013 using the following
command:
$exchange = New-SPTrustedSecurityTokenIssuer Name Exchange MetadataEndpoint
https://<Exchange Server>/autodiscover/metadata/json/1
Where <Exchange Server> is either the NetBIOS name or the External URL Fully Qualified
Domain Name (FQDN) of the Exchange 2013 server, such as mail.contoso.com.
b. Grant the Exchange 2013 service principal full control permissions to SharePoint site subscription
with the following commands:
$app = Get-SPAppPrincipal site https://<URL> NameIdentifier $exchange.NameId
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
$site = Get-SPSite https://<URL>
Set-SPAppPrincipalPermission AppPrincipal $app Site $site.RootWeb Scope sitesubscription
Right fullcontrol EnableAppOnlyPolicy
Where <URL> is the URL of a site collection accessible through HTTPS, such as
sharepointx.contoso.com.
4. Configure server-to-server authentication from Exchange 2013 to SharePoint 2013 by running the
following commands on an Exchange 2013 server:
cd C:\Program files\Microsoft\Exchange Server\V15\Scripts
.\Configure-EnterprisePartnerApplication.ps1 AuthMetadataUrl
https://<URL>/_layouts/15/metadata/json/1 -ApplicationType SharePoint
Where <URL> is the same as used in step 3b.
5. Add the eDiscovery users to the Discovery Management group in Active Directory Directory
Services (AD DS). Members of the Discovery Management group have the ability to search all
mailboxes in Exchange Server 2013. If you want eDiscovery users to be able to search only a subset of
mailboxes in your Exchange environment, such as only team or project mailboxes, you must create a
new role assignment in Exchange Server 2013.
Planning eDiscovery
There are several elements to consider when
planning eDiscovery. Factors such as the number
of search applications, whether any content should
be specifically restricted, and who should be
allowed to perform eDiscovery at what scope will
all affect how you implement eDiscovery features
in your SharePoint farm.
Plan eDiscovery Centers
One of the first considerations to make is how
many eDiscovery Centers you need for users to
discover content. Typically, if you have one search
service application indexing all your content, only
one eDiscovery Center is required. However, if you have more than one search service application, you will
need to create an eDiscovery Center for each search service application that you want to be able to use
for discovering content.
Plan permissions
You must determine how to grant your eDiscovery users access to all the content that they must be able
to discover. Typically, there are two ways to grant these permissions:
Grant read permissions at the web application level.
Grant read permissions on each site collection.
Granting read permissions across web applications is easier for an administrator to perform, but it does
not allow for any special exceptions that you may not want to be discoverable. Also, you cannot set
permissions at the web application level in SharePoint Online.
You should also consider whether it is appropriate to provide eDiscovery users with access to the crawl
log. This is useful if eDiscovery users would like to provide a list of locations that could not be included
when content is exported.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Configuring eDiscovery in SharePoint Server 2013
Scenario
The legal department at Contoso is investigating a contractual dispute with one of your major suppliers,
Trey Research. The legal team needs to be able to discover all content across Contoso that relates to
invoicing and contractual obligations with Trey Research.
To assist the legal team, you must configure eDiscovery functionality on the SharePoint intranet portal.
You will first create and configure an eDiscovery Center. You will then guide the legal team through the
discovery process for their first case.
Objectives
Create and configure an eDiscovery Center.
Create eDiscovery sets and use in-place holds.
Create eDiscovery queries and export discovered content.
Password: Pa$$w0rd
Exercise 1: Creating and Configuring an eDiscovery Center
Scenario
In this exercise, you will create and configure an eDiscovery Center. To make it easier to manage
permissions, you will first create an AD DS security group for the legal team. You will then create a web
application policy that grants the legal team Full Read permissions on all content in the web application.
This will enable the legal team to use eDiscovery tools to query content from all sites in the web
application.
Next, you will provision an eDiscovery Center site collection and add the members of the legal team to
the site. Finally, you will create a new eDiscovery case to help the legal team get started with their
investigations.
1. Create a secure group for the legal team
2. Create a web application policy for the legal team
3. Create an eDiscovery Center site collection
4. Add site members to the eDiscovery Center
5. Create a new case
Task 1: Create a secure group for the legal team
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Log on to the 20332B-NYC-DC-09 machine as administrator@contoso.com with password
Pa$$w0rd.
In Active Directory Administrative Center, create a new security group named Legal.
Add the following users to the Legal group:
Jim Corbin (CONTOSO\Jim)
Anat Kerry (CONTOSO\Anat)
Will Kennedy (CONTOSO\Will)
Ray Chow (CONTOSO\Ray)
Neil Charney (CONTOSO\Neil)
Task 2: Create a web application policy for the legal team
Log on to the 20332B-NYC-SP-09 machine as administrator@contoso.com with password
Pa$$w0rd.
Create a new user policy for the sharepoint.contoso.com web application. The user policy should:
Apply to all zones.
Grant Full Read permissions to the CONTOSO\Legal security group.
Task 3: Create an eDiscovery Center site collection
In the sharepoint.contoso.com web application, create a new site collection with the following
properties:
Property Value
Title Contoso eDiscovery
Description An eDiscovery Center for use by the
Contoso legal team.
URL /sites/discovery
Template eDiscovery Center
Task 4: Add site members to the eDiscovery Center
Grant the following users Contribute permissions on the eDiscovery Center:
Jim Corbin (CONTOSO\Jim)
Anat Kerry (CONTOSO\Anat)
Will Kennedy (CONTOSO\Will)
Ray Chow (CONTOSO\Ray)
Neil Charney (CONTOSO\Neil)
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 5: Create a new case
In the eDiscovery Center, create a new case with the following properties:
Property Value
Title Trey Research Contract Dispute
Description Case ref C0001
URL C0001
Sign out of SharePoint and close all Internet Explorer windows.

Results: After completing this exercise, you should have created and configured an eDiscovery Center site
collection.
Exercise 2: Discovering and Preserving Content
Scenario
In this exercise, you will create an eDiscovery set and use it to locate all content relating to Trey Research.
You will then place the discovered content on hold to prevent users from deleting or modifying relevant
material. Finally, you will delete a document and verify that the in-place hold preserves the deleted
content.
1. Run a full search crawl
2. Create an eDiscovery set
3. Run the eDiscovery In-Place Hold Processing Timer job
4. Test the in-place hold functionality
Task 1: Run a full search crawl
Using the Central Administration website or Windows PowerShell, run a full search crawl on the Local
SharePoint sites content source. Wait for the search crawl to finish before you continue.
Close any open Internet Explorer windows.
Task 2: Create an eDiscovery set
Open Internet Explorer and browse to http://sharepoint.contoso.com/sites/discovery.
Log on as CONTOSO\jim with password Pa$$w0rd.
In the Trey Research Contract Dispute case, add an eDiscovery set named Trey Contractual
Documents.
Within the Trey Contractual Documents set, add the following content sources:
o The Finance team site collection at http://sharepoint.contoso.com/sites/finance.
o The project site collection at http://sharepoint.contoso.com/projects/p1.
Configure the filter for the Trey Contractual Documents set to:
o Search for content added after January 1st, 2012.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Search for content that matches the keywords Trey Research.
Enable in-place hold for the Trey Contractual Documents set.
Preview the results of the Trey Contractual Documents set, and verify that the set includes several
documents.
Save the Trey Contractual Documents set.
Close all Internet Explorer windows.
Task 3: Run the eDiscovery In-Place Hold Processing Timer job
In the Central Administration website, locate the job definition for the eDiscovery In-Place Hold
Processing timer job.
Run the timer job.
Note: By default, the eDiscovery In-Place Hold Processing timer job runs once every hour.
In a production environment, you would not typically need to run the timer job manually. In this
case, you are running the timer job manually to enable you to proceed with the lab without
delay.
Task 4: Test the in-place hold functionality
Open Internet Explorer and browse to http://sharepoint.contoso.com/sites/Finance.
Log on as CONTOSO\Administrator with password Pa$$w0rd.
In the Contracts library, delete the file named Wide World Contract.
Locate the Preservation Hold Library, and verify that the library includes a version of the file you
just deleted.

Results: After completing this exercise, you should have created and configured an eDiscovery set.
Exercise 3: Querying and Exporting Content
Scenario
In this exercise, you will use queries to provide a finely-tuned "live" view of content that matches your
search criteria. First, you will run a full search crawl to ensure that the search results are up-to-date. Next,
you will create a query and view the results. Finally, you will export the content returned by the query as
an Electronic Discovery Reference Model (EDRM)compliant package.
2. Create a new eDiscovery query
3. Export discovered content
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Using the Central Administration website or Windows PowerShell, run a full search crawl on the Local
SharePoint sites content source. Wait for the search crawl to finish before you continue.
Close any open Internet Explorer windows.
Task 2: Create a new eDiscovery query
Open Internet Explorer and browse to http://sharepoint.contoso.com/sites/discovery/C0001.
Log on as CONTOSO\Jim with password Pa$$w0rd.
Create a new eDiscovery query named Trey Invoices.
Ensure the query includes both of the sources you defined in the previous exercise.
Use keyword query syntax to limit the search results to documents with a content type of Invoice.
Review the Advanced Query Options item. Notice that the dialog box displays the full SharePoint
query:
(ContentType:"Invoice") AND (((Trey Research))) AND
(Path:"http://sharepoint.contoso.com/sites/finance" OR
Path:"http://sharepoint.contoso.com/projects/p1")
Note: The dialog box may take several seconds to display the query.

This query is comprised of:
The keyword query you added.
The paths to the sources you defined in the previous exercise.
The filter you defined in the previous exercise.
Review the query results, and then save and close the query.
Task 3: Export discovered content
Create a new eDiscovery export.
When prompted to select a query, select the Trey Invoices query.
Download the results of the query to the desktop.
On the desktop, review the contents of the Trey Invoices folder.
Note: In addition to the exported content, the Trey Invoices folder includes a manifest.xml
file. This is an Electronic Discovery Reference Model (EDRM) compliant XML file that enables users
to use the export with third party EDRM tools.

Results: After completing this exercise, you should have created an eDiscovery query and exported the
content returned by the query.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Planning Records Management
Records management and storage of key information for compliance purposes or to support later
investigations is becoming more important to organizations. This is especially true for organizations that
must comply with external standards bodies, such as financial institutions or manufacturing companies.
Records management in SharePoint gives organizations the ability to preserve key content at a specific
point in time for later retrieval and review. Although some may consider this as archiving, it is important
to understand that, although there are similarities, records management is only interested with specific
types of information produced by the organization to support requirements, such as external audits or
legal action.
Lesson Objectives
Describe records management.
Describe a file plan.
Describe methods for storing records in SharePoint.
Describe methods for declaring records in SharePoint.
What Is Records Management?
Records management is the process by which an
organization performs the following tasks:
Considers which kinds of information it should
declare as records.
Decides how it should handle documents that
will later become records while they are in
use, and decides how it should collect the
information after the documents are declared
as records.
Decides howand for what length of timeit
retains each record type to comply with legal,
business, or regulatory requirements.
Implements technical solutions and business processes to help ensure that the organization complies
with its records management obligations in a cost-effective way without intruding on the normal
running of the business.
Performs routine tasks on its records, such as disposing of expired records or locating and protecting
records that are related to external events such as lawsuits.
A record is a document or other electronic or physical entity in an organization that serves as evidence of
an activity or transaction performed by the organization and that requires retention for some time period.
For example, assume that your organization is a defense contractor that builds trucks for the government.
You start a project for a new truck design to meet new government requirements. You create a
specification document for the new truck design. When your customer (the government) agrees on the
specification document, the specification document becomes a record, and your organization will need to
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
keep it safe for a predetermined period, such as 10 years beyond the project end date, so that it can be
referred to in case of a dispute over the originally agreed specifications.
It is the responsibility of corporate compliance officers, records managers, and lawyers in your
organization to determine which documents are records. These staff members can help you to ensure that
documents are retained for the appropriate period of time by carefully categorizing all enterprise content
in your organization. A well-designed records management system is important for the following reasons:
It helps to legally protect an organization.
It helps the organization to comply with regulatory obligations.
It increases the efficiency of an organization by encouraging the disposition of expired items that are
not records.
Key elements of a records management solution
The key elements of a records management solution include the following:
A content analysis document that categorizes enterprise content that can become records, provides
source locations, and also describes how the content will move to the records management
application.
A file plan that specifies where each kind of record should be retained, the policies that apply to
them, how long they must be retained, how they should be disposed of, and who is responsible for
managing them.
A compliance requirements document that defines the rules that the organization's IT systems must
follow to ensure compliance and the methods used to ensure the participation of enterprise team
members.
The method for collecting inactive records from all record sources, such as collaboration servers, file
servers, and email systems.
The method for auditing active records.
The method for capturing and maintaining metadata and audit histories for records.
The process for putting records on hold when events such as litigations occur.
A monitoring and reporting system for the handling of records to ensure that employees are filing,
accessing, and managing them according to defined policies and procedures.
Creating a File Plan
In order for an organization to perform records
management, the organization should construct a
file plan. A file plan should contain the following
details about the types of information in the
organization:
The types of information and documents or
files that exist
The types of information that should be
treated as records
The triggers for creating records, such as
agreements, approvals, or official sign-offs
The storage location of the records
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The retention period for records
The disposition or disposal process for records
The person responsible for the records
Identifying Records
Identifying which types of document should become records is not the job of the IT manager or the IT
department. Although IT specialists will undoubtedly be required to help implement a records
management solution such as SharePoint, determining which documents and information should be
declared as a record will require input from records managers, lawyers, compliance officers, and content
managers. Along with general business laws, you must evaluate standards body and legal requirements
that are specific to your organization.
Reference Links: For more information about creating a file plan, see Create a file plan to
manage records in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=303696
Storing Records in SharePoint
There are typically two approaches to storing
records in SharePoint. You can use a records
center to hold a copy of all records that you
require, or you can use in-place records
management to keep the record in the original
location it was created or managed.
Using a records center
A records center is a separate site collection,
typically in a separate database, which you use to
store only records. When users mark an item, such
as a project document, as a record, a copy of the
document is sent to the records center along with
any metadata that is attached to the document at the time of declaration. Using a records center has the
following advantages:
Records can easily be restricted to records management staff or compliance officers.
Records are maintained in one place.
Records do not clutter existing collaboration or publishing sites.
Records can be easily organized by type or metadata and moved to the correct location
automatically.
Records can be easily audited.
Records storage can be managed separately from live documents.
Using in-place records management
In-place records management leaves records in their original location, such as a collaboration site, after
they are declared records. When an item is declared a record, a different retention policy and retention
actions are applied to the item. In-place records management has the following advantages:
A separate site collection is not required for records storage.
Users can easily find records.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Later versions of a document can be automatically declared records.
Metadata is maintained in the original view.
In some circumstances, you may want a hybrid approach where some records are stored in a records
center, and some are stored using in-place records management. This approach is fully supported,
although you must ensure all necessary records are being stored in an appropriate location for the
required period.
Reference Links: For more information about the differences between using a records
center and using in-place records management, see Use a SharePoint Server 2013 records archive
or manage records in place at http://go.microsoft.com/fwlink/?Linkid=303697
Creating Records in SharePoint
When planning for records management you must
also consider at what point, under what
circumstances, or what trigger occurs that you
should declare information as a record. Often, this
trigger will be some kind of agreement or
approval, perhaps from senior management or
from a customer. In the earlier example of
specifications for a project, the agreement on
specifications should trigger the record
declaration. This means that you must understand
business processes with respect to record
declaration in order to ensure you are capturing
the correct version of a document at the correct stage to treat the document as a record.
There are typically four ways to declare a record from an existing document or existing information:
Manually declare a record in the SharePoint user interface (UI)
Use a retention policy to automatically declare a record at a specific time interval
Use a workflow to declare a record, perhaps as part of a larger process
Use a custom code solution
Manually declaring records
If a SharePoint administrator has configured a connection to a records center or you are using in-place
records management, users will be able to use the SharePoint interface to declare a document as a record.
Manually declaring records can be useful, because it does not require much special configuration;
however, when considering the importance of records management to your organization, you must
consider whether it is appropriate to rely on users understanding the correct time to declare records and
to remember to perform the action. Also, manual declaration does not always scale well in large
environments.
Using retention policies
You can use retention policies to declare items as records at a predefined interval. The interval will be
calculated from any date field which applies to the item, including custom column date fields. After the
interval is reached, the policy can declare the item a record (in-place) or transfer the item to a location,
such as a records center. SharePoint supports multi-stage retention policies; for example, you can have a
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
policy which declares an in-place record six months after creation, subsequently transfers the item to a
records center after another year, and then deletes the item five years after the last modification date.
Using a workflow to declare records
You can create workflows in SharePoint Designer that use the send item to repository action. This action
can send items to a records center. Adding this kind of records declaration into a workflow is very
powerful because users can use the workflow to assist other processes without realizing that records
management is being performed in the background. For example, you could create a workflow for
document approval that notifies a senior manager when the document is ready for approval, enables the
manager to approve the document, and once the document is approved, sends a copy of the document
to the records center.
Using custom solutions for records declaration
You can also create custom solutions using Visual Studio that leverage the records management
functions, such as records declaration or sending items to a records center. These solutions can use
additional triggers which are not available to no-code workflows, such as dedicated timer jobs.
Disposing of records
In addition to how your organization will create or declare records, you must consider how your
organization will dispose of records. Typically, you will need to keep records for a predetermined period
of time, such as five years; therefore, retention policies in the records center can help to keep records
storage manageable and automatically cleared out. Additionally, retention policies enable you to start a
workflow, such as a disposition workflow, to check with content managers or compliance officers whether
records can be deleted as they expire.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring Records Management in SharePoint
Server 2013
Scenario
To ensure that Contoso complies with legal and regulatory requirements, its audit and compliance team
has produced a file plan that specifies various policies that should be applied to different types of
documents. For example, all contracts must be retained for five years from the final effective date, and all
invoices must be retained for seven years from the payment due date. In addition, the team needs to
audit any changes to invoices. Your task is to configure in-place records management policies to
implement this file plan.
Objectives
Create and apply in-place retention policies.
Create and apply audit policies.
Password: Pa$$w0rd
Exercise 1: Configuring In-Place Records Management
Scenario
In this exercise, you will configure in-place records management for the Finance team site collection. First,
you will configure a retention policy for contracts on the site. You will then configure a retention and
audit policy for invoices.
1. Create an in-place retention policy for contracts
2. Create an in-place retention and auditing policy for invoices
Task 1: Create an in-place retention policy for contracts
Open Internet Explorer and browse to http://sharepoint.contoso.com/sites/Finance.
Log on as CONTOSO\Administrator with password Pa$$w0rd.
In the Contracts document library, configure an information policy for the Contract content type.
The policy should ensure that all contracts are retained for five years from the final effective date.
Task 2: Create an in-place retention and auditing policy for invoices
In the Invoices document library, configure an information policy for the Invoice content type.
Add a retention policy to ensure that all invoices are retained for seven years from the payment due
date.
Add an audit policy to ensure that the following events are audited:
An invoice is edited
An invoice is moved or copied to another location
An invoice is deleted or restored
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

Results: After completing this exercise, you should have configured retention and audit policies for the
Contract and Invoice content types.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you learned about SharePoint features that support Enterprise Content Management
(ECM). This included features to provide administrative control over document storage, information
retention, document and item classification, information growth, and e-mail integration.
In addition, you learned about implementing eDiscovery within SharePoint 2013, including the supporting
components required for eDiscovery, and eDiscovery case management. You also learned about records
management to store and provide subsequent access to official information that supports evidence of the
behavior and actions of an organization.
Review Question(s)
Test Your Knowledge
Question
Which of the following site templates is supported for a large scale repository?

eDiscovery Center
Document Center
Team Site
Publishing Site
Project Site
Test Your Knowledge
Question
How do you use the eDiscovery capabilities to prevent content being deleted during an
investigation?

Create an eDiscovery query
Create an eDiscovery set
Send the content to a records center
Create an in-place hold
Add a user to the discovery management group

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Test Your Knowledge
Question
Which of the following details should not be in your file plan?

Document type
Retention period
Last modification date
Disposal method
Record storage option

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
10-1
Module 10
Planning and Configuring Web Content Management
Contents:
Module Overview 10-1
Lesson 1: Planning and Implementing a Web Content Management
Infrastructure 10-2
Lesson 2: Configuring Managed Navigation and Catalog Sites 10-6
Lab A: Configuring Managed Navigation and Catalog Sites 10-13
Lesson 3: Supporting Multiple Languages and Locales 10-18
Lesson 4: Enabling Design and Customization 10-23
Lesson 5: Supporting Mobile Users 10-27
Lab B: Configuring Device Channels 10-31

Module Overview
The web content management capabilities in Microsoft SharePoint Server 2013 can help an organization
to communicate and integrate more effectively with employees, partners, and customers. SharePoint
Server 2013 provides easy-to-use functionality to create, approve, and publish web content. This enables
you to get information out quickly to intranet, extranet, and Internet sites and give your content a
consistent look and feel. You can use these web content management capabilities to create, publish,
manage, and control a large and dynamic collection of content. As part of Enterprise Content
Management (ECM) in SharePoint Server 2013, web content management can help to streamline your
process for creating and publishing websites.
Objectives
Plan and configure a Web Content Management infrastructure to meet business requirements.
Configure managed navigation and product catalog sites.
Plan and configure support for multilingual sites.
Manage design and customization for publishing sites.
Plan and configure support for mobile users.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
10-2 Planning and Configuring Web Content Management
Lesson 1
Planning and Implementing a Web Content Management
Infrastructure
As part of the planning for web content management features, it is important to understand how certain
features work in order to understand the significance and impact of those features on your SharePoint
deployment. Some web content management features affect many aspects of web content management
and some are designed to enhance only specific functionality or provide a solution only to specific
scenarios. Understanding how each of these features fits into the greater whole of web content
management will help you understand necessary configuration requirements and prerequisites, required
skillsets, and any training requirements that may exist.
Lesson Objectives
Identify SharePoint 2013 web content management features.
Identify planning steps for web content management features.
Determine appropriate content publishing methods.
Web Content Management Features in SharePoint 2013
Web content management (WCM) in SharePoint
Server 2013 consists of features and functionality
that you use to configure, customize, optimize,
and publish site collections, sites, and pages.
Publishing sites are designed to host primarily
webpage content rather than document content,
although publishing sites can contain libraries in
the same way as a non-publishing site.
There are three publishing site collection
templates:
Publishing Portal. The Publishing Portal
template offers libraries for pages, images,
reports, form templates, styles, and reusable content. By default, there are content approval
workflows for pages, the template is designed to support extensive branding, and anonymous
permissions can be granted to only content pages.
Enterprise Wiki. The Enterprise Wiki template is for the collaborative creation of page content, with
page categories, comments, and ratings.
Product Catalog. The Product Catalog template is for managing lists and libraries for cross-site
collection publishing. Typically, list and library content stored and updated in a product catalog site
collection is consumed through category pages or search-driven Web Parts in other site collections.
Publishing site collection and site templates typically enable the SharePoint Server Publishing
Infrastructure feature and the SharePoint Server Publishing feature. These features include the following
functionality:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Special groups and permissions. Site collections with the SharePoint Server Publishing Infrastructure
feature activated have special groups created, including Approvers, Designers, and Hierarchy
Managers, along with matching permission levels.
Navigation. The global navigation menu replaces the top-link bar, and managed navigation is
available.
Master pages, page layouts, and display templates. You can customize the overall appearance of your
site collection or site with master pages, and use page layouts and display templates to customize the
way information is shown on certain pages.
Design Manager and design packages. Design Manager is a SharePoint 2013 feature that you can use
to manage site branding. You can export customizations as a design package, which is a single file
with a .wsp extension, and import these design packages into other sites or site collections. Design
packages include changes made in the Master Page Gallery, Style Library, Theme Gallery, the Device
Channels list, and Page content types.
Device channels. Device channels enable you to specify different designs for different devices, such as
mobile devices, in order to enable better content layout for that type of device.
Site columns and content types. Additional site columns, such as Page Content, Scheduling Start Date,
and Scheduling End Date are created within the Site Column Gallery, and content types such as Page
Layout, Article Page, and Enterprise Wiki Page are added to the Content Type Gallery.
Web parts. Additional content related web parts are added to the Web Part Gallery.
Pages library. A Pages library is created to store webpages for the site.
Approval workflow and scheduling. You can use an approval workflow to route approval tasks to the
appropriate users prior to publishing. Scheduling enables an author to specify a time or date when
the page should be available.
Variations for multilingual sites. Variations enable you to keep the same site structure but have
different language pages for end users. In SharePoint 2013, you can translate pages manually or use
the machine translation service.
Caching. SharePoint can use an object cache to reduce the burden on object retrieval from the
database servers. For example, publishing sites can store retrieved object data in the memory of the
web front-end (WFE) server for short periods of time so that if the same object is requested again, it
can be returned from memory very quickly.
Note: You can activate the SharePoint Server Publishing Infrastructure and SharePoint
Server Publishing features on site collections and sites that do not use the publishing site
templates in order to provide additional functionality to your site collection. However, you should
consider that each feature activation step includes several of the functional components listed
here; for example, you cannot only activate the navigation functionality.
Additional Reading: For more information about WCM in SharePoint 2013, see Overview
of publishing to Internet, intranet, and extranet sites in SharePoint Server 2013 at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Planning for Web Content Management
There are several planning steps that you should
complete to determine the best way to approach
your WCM requirements. These steps involve
determining which features you will require to
support the authoring methods that you choose.
Determine placement and access
requirements
After you determine that you require publishing
sites and features, you should identify which of the
following categories will apply to the sites:
Intranet. An intranet is typically accessed from
the internal network by employees with valid active directory logon accounts.
Extranet. An extranet is accessible to Internet clients in a secure manner. Although the people who
need access to the content are typically not all internal employees, each user will require a logon.
Internet. An Internet-facing website typically has some sites or content that is available to everyone,
regardless of whether that user has logon credentials. Internet-facing sites usually require anonymous
access.
Determine multilingual support
You should also identify whether any of the content you are publishing requires variations for different
languages. Even if there is no requirement now but the possibility exists for needing multilingual support
later, you should consider using SharePoints variations feature at the outset so that your site content can
more easily accommodate the changes when you decide to implement variations. Adding variations later
without these considerations can be more difficult.
Determine the publishing method
Content is typically authored for publishing sites in one of two ways, cross-site collection publishing or in-
place authoring.
Cross-site collection publishing
With cross-site collection publishing, content is created and updated in one or more site collections that
are indexed by the search service application. Content is published to one or more additional site
collections that use the Content Search Web Part and the Catalog-Item Reuse Web Part to display the
authored content. Branding is done on the publishing site collections using master pages, page layouts,
and display templates that affect the information shown by the Web Parts.
You should consider implementing cross-site collection publishing if the answer to any of the following
questions is yes:
Is it acceptable (or required) for the authoring site to have a different look and feel (and possibly a
different structure) from the publishing site?
Do you want or need to keep the authoring site separate from the publishing site?
Do you want to have multiple sites or even different host headers for different brands?
Do you want to combine content from multiple authoring sites to one publishing site, or have
content from one authoring site published to multiple publishing sites?
Do you plan to use variations or translate content for multiple sites with different URLs for different
locale-specific variants of your site?
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In-place authoring
With in-place authoring, authors create content in the same location that it will be read or consumed.
Approval processes and workflows assist reviewers to ensure content is suitable before being published.
Branding is carried out through master pages and page layouts, and is the same for authors and
consumers.
In-place authoring is typically the best option if:
You do not need variations with unique URLs.
You do not need to publish the same content to multiple sites.
You require authoring to be performed in the same site as the content is consumed.
Additional Reading: For more information about planning for WCM, see Plan for Internet,
intranet, and extranet publishing sites in SharePoint Server 2013 at
Discussion: Publishing Methods
Consider the following questions for your own
organization:
Do you currently use in-place authoring for
publishing content?
Which of your sites will use in-place authoring
for publishing content?
Do you have any site content that could fit the
product catalog?
Which of your sites will use cross-site
collection publishing?

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Configuring Managed Navigation and Catalog Sites
SharePoint 2013 introduces new features to improve the flexibility behind publishing sites and the type of
content that can be published as part of a no-code solution with out-of-the-box functionality. This lesson
introduces two new publishing features, managed navigation and catalog sites, and the components that
support these key features.
Lesson Objectives
Describe the purpose of managed navigation.
Describe the purpose of a catalog site.
Describe the process for publishing a catalog site.
Describe the purpose of category and catalog item pages.
Describe how search Web Parts are used to publish content.
Understanding Managed Navigation
Managed navigation enables you to create a
navigation structure for the global navigation area
(typically the top-link bar). This structure is defined
by a term set in the managed metadata service
instead of the logical site structure in the site
collection.
Managed navigation is important to two
publishing scenarios:
Creating a navigation structure for webpages
in a single page library. In previous versions of
SharePoint, the global navigation area was
populated by the site structure within a site
collection, but without developing a custom solution, only subsites would extend the navigation links
for global navigation. This meant that navigation between pages would have to be done by
navigation links in the pages themselves, which could be confusing for users.
In SharePoint 2013, you can create a global navigation structure using a managed metadata term set
where each term links to a specific page. This gives the end user the illusion of a navigation structure even
though all the site pages are in one library.
Publishing a product catalog using category and topic pages. A product catalog typically stores
product information in a flat list or library. In the publishing site collection, you can organize items
from the product list based on metadata for navigation. For example, there may be a category of
items called Cameras in the product catalog, so there can be a global navigation link for cameras that
will take users to a special page for cameras.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Friendly URLs
Managed navigation is also able to provide friendly URLs without using HTTP redirection. Friendly URLs
provide a way to eliminate control characters and identifier strings that often appear in SharePoint URLs
and replace the complex URL with a friendly URL that might look like http://products
.contoso.com/cameras.
Overview of Catalog Sites
A catalog site holds a list or library that is
configured as a product catalog. You can enable
any list or library as a catalog if you have activated
the Cross-Site Collection Publishing feature. When
you configure the list or library that you want to
use as a catalog, you configure at least one
column to use managed metadata. This column
will hold some kind of category or classification,
which drives the navigation element when the
catalog is used by a publishing site.
You can use catalog-enabled lists or libraries in an
online store scenario. For example, Contoso sells IT
products and services, such as desktop computers, servers, storage, and support services. Contoso can put
details about the products they sell into one or more catalog-enabled lists, where the categories would
include computers, servers, storage, and services. In turn, these lists would be published to the public
Internet site using the Cross-Site Collection Publishing feature.
As another example, Litware stores department and office-related information in many documents and
knowledgebase articles. These documents and articles are stored in several different sites, where they are
authored and updated by the appropriate teams. Enabling these libraries as catalogs enables Litware to
create a publishing site for viewing all departmental and office-related documentation and articles.
You can also use the Product Catalog site collection template to create the source location for a catalog.
By default, the Product Catalog template has the following settings:
The Cross-Site Collection Publishing feature is activated.
A site collection term set called Product Hierarchy is created.
A list called Products is created. This list is not enabled as a catalog by default.
Two content types, Product and Product with Image, are associated with the Products list.
A site column called Group Number is created and associated with both content types.
A site column called Item Category is created and associated with both content types. This is a
managed metadata column linked to the Product Hierarchy term set.
You should also specify the location to which the catalog will be published. This creates a result source,
which narrows the scope of queries for Web Parts, such as the Content Search Web Part. The result source
is used to create dynamic, reusable pages based on the catalog contents.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Publishing Catalog-Enabled Lists
Configuring catalog-enabled lists or libraries for
cross-site collection publishing can be a complex
task. The level of complexity will be, in part,
dependent on the nature of the items in the
catalog and dependent on whether the catalog list
already exists or will be created new. The following
procedures provide the steps to follow when
creating a new catalog, or when publishing an
existing catalog.
In order to create a catalog publishing
configuration with new content, you need to
1. Create a site collection using the Product Catalog template. Check that the site collectionspecific
term group is created with the Product Hierarchy term set.
2. Create custom site columns for any item attributes that you require. Item attributes can be used to
filter the display of items in the publishing site, called refinement.
3. Populate the Product Hierarchy term set with the appropriate values for your item categories. Share
the term group with the publishing site.
4. Create custom content types for the types of item in the catalog. You should use the Product and
Product with Image content types as the parent for your custom content types, and add your custom
columns to the content types you create.
5. Populate the catalog. Authors can start creating items in the catalog using the content types you
created in the previous step.
6. Enable the Products list as a catalog. If you have more than one column that uses managed metadata,
including the Item Category column, you must choose the field that drives managed navigation. You
must also choose whether anonymous access is required. Anonymous access is needed to the catalog
if anonymous users will be accessing the publishing site to view products from the catalog.
7. Ensure that a search crawl has run for the content in the catalog site. Content in the publishing site
will only be as up-to-date as the last crawl.
8. Create the publishing site collection. This is where users will browse the content and product items
from the catalog.
9. Connect the catalog to the publishing site. At this point, managed navigation should take effect at
the publishing site.
10. Customize category and item pages at the publishing site if required.
In order to publish information as a catalog from an existing list or library to another site, you should
1. Enable the cross-site collection publishing feature at the site collection that holds the source list or
library to be used as a catalog.
2. Configure a managed metadata term set to use for both categorization and managed navigation.
Ensure this term set is available to the publishing site.
3. Ensure that the managed metadata term set to be used for navigation is assigned to a column that is
applied to items in the source list or library.
4. Ensure each item in the list or library has a value assigned for the column representing the term set.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
5. Run a search crawl, or wait for the next search crawl to complete.
6. Enable the source list or library as a catalog.
7. Go to the publishing site collection or create a new site collection for publishing. Connect the
catalog-enabled list or library to the publishing site.
8. Customize category and item pages at the publishing site if required.
Understanding Category Pages and Catalog Item Pages
Cross-site collection publishing of content is
mainly driven by the Search service application. In
a publishing site, you use pages with Web Parts to
display content from the catalog dynamically.
When you create a catalog connection at the
publishing site, two sample pages are created in
the Pages library for this purpose. These pages use
sample page layouts added to the Page Layout
Gallery.
Category pages
The first of these sample page layouts is the
category page. By default, each category (each
term in the Product Hierarchy term set) has a category page that uses Web Parts to display the relevant
items within that category. Mapping the categories to pages is done within the managed metadata term
store as follows:
For each term (or category), the NAVIGATION tab enables you to configure the term for navigation
using term-driven pages. Using the term-driven pages mechanism is important to reflect the dynamic
re-use of just a few pages acting as templates for all the categories of your catalog.
For each term, the TERM-DRIVEN PAGES tab enables you to configure the friendly URL for the
category and specify which target page is used for term-driven content. You can also specify an
image to be associated with the categorythis image can be displayed in the Term Property Web
Part.
You can use the same category page for all categories in your product hierarchy, but because each
category can have a specific category page, you can create a different page layout based on the category
type or the category level in the term set hierarchy. For example, you could:
Associate a page named category.aspx with the root level of the term set.
Associate a page named subcategory.aspx with the second level of the term set.
Associate a page named topic.aspx with the third level of the term set.
This would give you the ability to have content arranged differently based on the depth the user
navigates to in the hierarchy.
Catalog item pages
Catalog item pages are typically used to display individual item information from the catalog. By default,
the catalog item page layout uses the Catalog-Item Reuse Web Part to display selected details of an item
from the catalog. Additional instances of the Catalog-Item Reuse Web Part are embedded into the page
layout to list the item data of each indexed column in the catalog.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
You control the mapping of items to catalog item pages by using the options on the TERM-DRIVEN
PAGES tab of the parent category in the managed metadata term store. For example, if your product
items are bicycles, the parent category may be called Bikes. In the managed metadata term store, on the
TERM-DRIVEN PAGES tab of the Bikes term, you can choose the page that all child items will use for
display. By default, the CatalogItem-Product-Hierarchy.aspx page is used to display item details.
Note: This means that you can only change the catalog item page for all items in one
category together; you cannot change the catalog item page for an individual item.
Additional Reading: For more information about category pages and catalog item pages,
see Overview of cross-site publishing in SharePoint Server 2013 at
Using Search Web Parts to Publish Content
Catalog pages and catalog item pages are able to
display dynamic content from a catalog-enabled
list or library by using new Web Parts that are
present in SharePoint 2013. These Web Parts are
search-driven and enable you to customize the
data displayed by utilizing multiple Web Parts on
one page.
Content Search Web Part
The Content Search Web Part displays a set of
search results from a result source. A result source
is a predefined set of information, such as a site or
a list, used to limit the breadth of search results.
After selecting the result source to use for the Web Part, you can choose to further filter the items
displayed from the result source by matching against tags or navigation terms. Restrict by current and
child navigation terms is the default behavior for product catalog and managed navigation
configuration. You can also specify a managed property to use as a refiner to be applied to the results. A
refiner specified as part of the query further limits the results by item properties, such as author, date
modified, or content type.
Note: The Content Search Web Part can use result sources from across the entire
SharePoint farm, and is not limited to the current site collection. This enables cross-site collection
publishing in SharePoint 2013, which was not possible in previous versions of SharePoint without
custom code solutions.
Refinement Panel Web Part
You can use the Refinement Panel Web Part to provide users with the ability to perform additional filters
on the items returned in the Content Search Web Part. These refinements can be selectively enabled or
disabled by the user on the page, to provide a more manageable or meaningful result set. For example,
you could add the Refinement Panel Web Part to your Bikes category page, and include the FrameSize
managed property as a refiner. Users will then be able to reduce the list of displayed bikes by selecting a
specific frame size from the Refinement Panel Web Part.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: To use a list or site column as a refiner, the list must have previously been crawled by
the Search service application, and you must have promoted the crawled property to a managed
property, and enabled the managed property for refinement.
Taxonomy Refinement Panel Web Part
You can use the Taxonomy Refinement Panel Web Part to add child categories of the current term-driven
navigation category as refiners to the page. For example, assume that part of your product category term
set is as follows:
Bikes
o Mens
Hybrid
Mountain
Road
Then, if you added the Taxonomy Refinement Panel to the Mens category page, the panel would
automatically add Hybrid, Mountain, and Road to the page as refiners.
Faceted navigation
Faceted navigation is an extension of refinement capabilities in SharePoint 2013. Faceted navigation
enables you to configure specific refiners for specific categories, represented by terms in the term store, so
that the refiners are always relevant to the category you are currently viewing. For example, the product
catalog which includes bikes also includes bike accessories, so an expanded view of the product category
term set is as follows:
Bikes
o Mens
Hybrid
Mountain
Road
o Womens
Hybrid
Mountain
Road
Accessories & Parts
o Saddles
o Handlebars
o Mudguards
o Clothing
Gloves
Cycle Helmets
In a previous example, you could add frame size as a refiner for bikes, but frame size is not applicable to
accessories, such as saddles, and saddles have attributes you might want to use as a refiner, but does not
apply to bikes, such as padding type.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this example, you can enable faceted navigation for the navigation term set and add FrameSize to the
FACETED NAVIGATION tab of the Bikes term in the Product Hierarchy term set from the product catalog
site. Then the specified refiners are available only for the appropriate categories.
Additional Reading: For more information about configuring the search and refinement
Web Parts, see Configure Search Web Parts in SharePoint Server 2013 at
http://go.microsoft.com/fwlink/?Linkid=303701 For more information about configuring the
refinement and faceted navigation, see Configure refiners and faceted navigation in SharePoint

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Configuring Managed Navigation and Catalog Sites
Scenario
Following the successful deployment of SharePoint 2013 throughout the business, the IT team now wants
to investigate using SharePoint as a web publishing platform. One of the requirements for Contosos
public-facing website is a product catalog with details of each product provided by Contoso. The business
would like to categorize each product to make it easy for consumers to locate the product they desire.
Contoso has a hierarchical taxonomy that they use to structure their product offerings, but they do not
currently have a way of making this taxonomy visible to consumers.
Your job is to develop a website by using the web content management features in SharePoint 2013. You
will use managed metadata and a term store to create a hierarchical navigation structure that will be
available both to the business when adding products to the catalog, and to consumers when they access
the public site. You will create this sample site by using the Contoso lab environment, and this website will
act as a proof of concept that is not intended to be accessed by the general public; any security
considerations that might apply to a live deployment will be ignored.
Objectives
Create and configure product catalog sites.
Configure cross-site publishing.
Configure publishing sites.
Passw0rd: Pa$$w0rd
Exercise 1: Configuring Product Catalog Sites
Scenario
In this exercise, you will create, populate, and configure a product catalog site. First, you will create a new
Product Catalog site collection. Next, you will add site columns and a content type to represent Contoso
pharmacy products, and then you will configure a managed metadata term set to categorize your
products. Finally, you will populate the product catalog with some sample data.
1. Create a Product Catalog Site Collection
2. Add product-related site columns
3. Create a product-related content type
4. Add the Pharmacy Products content type to the Products list
5. Configure the Product Hierarchy term set
6. Populate the Product Catalog site
Task 1: Create a Product Catalog Site Collection
Start the 20332B-NYC-DC-10 virtual machine. Wait until the logon screen is displayed and then wait a
further five minutes before you proceed to the next step.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Start the 20332B-NYC-DB-10 virtual machine. Wait until the logon screen is displayed before
continuing.
Start the 20332B-NYC-SP-10 virtual machine.
Pa$$w0rd.
In the sharepoint.contoso.com web application, create a new web site collection with the following
properties:
Property Value
Title Products
Description A product catalog for demonstration purposes.
URL /sites/catalog
Template Product Catalog
After the site is created, browse to the site. Log on as CONTOSO\Administrator with the password
Pa$$w0rd.
Task 2: Add product-related site columns
On the Products site collection, create the following site columns:
Column name Column type Category
Size Single line of text Product Catalog Columns
Quantity Number Product Catalog Columns
Color Single line of text Product Catalog Columns
Task 3: Create a product-related content type
Create a new site content type named Pharmacy Products.
Configure the content type to inherit from the Product with Image content type.
Add the content type to the Product Catalog Content Types group.
Add the Color, Quantity, and Size columns to the content type.
Task 4: Add the Pharmacy Products content type to the Products list
Add the Pharmacy Products content type to the Products list.
Delete the Product with Image list content type from the Products list.
Task 5: Configure the Product Hierarchy term set
On the Products site, open the Term Store Management Tool.
In the site collection term set group, locate the Product Hierarchy term set.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Within the Product Hierarchy term set, create a new term named Pharmacy Products.
Add the following terms as children of the Pharmacy Products term:
o Analgesics
o Digestive Health
o First Aid
Add the following terms as children of the Analgesics term:
o Acetaminophen
o Ibuprofen
Add the following terms as children of the Digestive Health term:
o Antacids
o Prokinetics
Add the following terms as children of the First Aid term:
o Antiseptics
o Bandages
o Plasters
o Scissors
Task 6: Populate the Product Catalog site
Run the E:\Mod10\SetupFiles\Setup.ps1 file by using Windows PowerShell.
Note: The Setup.ps1 file adds some sample items to the Products list.
After the script finishes running, open Internet Explorer and browse to
sharepoint.contoso.com/sites/catalog.
Log on as CONTOSO\Administrator with the password Pa$$w0rd when prompted.
Verify that several products with images have been added to the Products list.
Verify that a term from the Product Hierarchy term set has been assigned to the Item Category
field for each item.

Results: After completing this exercise, you should have created and configured a product catalog site
collection.
Exercise 2: Configuring Cross-Site Publishing
Scenario
In this exercise, you will configure cross-site publishing for your product catalog site. First, you will
configure catalog settings on the Products list so that other site collections can consume it as a catalog.
Next, you will share the Product Hierarchy term set to make it available to other site collections. Finally,
you will run a search crawl to index your catalog content.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
1. Configure catalog settings for the Products list
2. Share the Product Hierarchy term set with the publishing site collection
Task 1: Configure catalog settings for the Products list
In Internet Explorer, browse to sharepoint.contoso.com/sites/catalog.
Open the Products list and browse to the Catalog Settings page.
Enable the Products list as a catalog.
Make the Item Category and Item Number columns available as catalog item URL fields.
Specify Item Category as the column that categorizes items for navigation.
Configure the Products list to be re-indexed at the next search crawl.
Task 2: Share the Product Hierarchy term set with the publishing site collection
In the Term Store Management Tool, locate the term set group for the Products site collection.
Grant access to the term set group for the site collection at
http://sharepoint.contoso.com/sites/staging.
Note: You will create a publishing site collection at
http://sharepoint.contoso.com/sites/staging in the next exercise.
Run a full search crawl on the Local SharePoint sites content source.
Wait for the crawl to complete before continuing with the lab. This may take a few minutes.
Note: You do not need to run a full search crawl every time you configure or update
catalog content. You are running a full search crawl (rather than using continuous or incremental
crawls) in this case because the SharePoint environment has not been crawled before.

Results: After completing this exercise, you should have made the contents of your product catalog site
available to other site collections by using cross-site publishing.
Exercise 3: Configuring Publishing Sites
Scenario
In this exercise, you will configure a publishing site to enable users to browse products. First, you will
create a Publishing Portal site collection. You will then connect the site to the product catalog that you
configured in the previous exercises.
1. Create a Publishing site collection
2. Connect the publishing site to a product catalog
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 1: Create a Publishing site collection
In the sharepoint.contoso.com web application, create a new site collection with the following
properties:
Property Value
Title Staging
Description A staging site to test cross-site publishing.
URL /sites/staging
Template Publishing Portal
After the site is created, browse to the site. Log on as CONTOSO\Administrator with the password
Pa$$w0rd.
Task 2: Connect the publishing site to a product catalog
On the Staging site, browse to the Manage catalog connections page.
Connect the site to the Products Products catalog with the following options:
o Integrate the catalog into the Staging site.
o Use the Item Category column to categorize items for navigation.
o Use Pharmacy Products as the root term for the navigation hierarchy.
Verify that the Quick Launch navigation menu now mirrors the Pharmacy Products term set that you
configured in the first exercise.
After you finish configuring the catalog connection, on the Quick Launch navigation menu, click
Bandages.
Verify that the page displays two items from the Bandages category.
Verify that the page displays a friendly URL that ends with /first-aid/bandages.
Click 5m Crepe Bandage.
Verify that the page displays the details of the 5m Crepe Bandage product.
Note: The default category and item pages (together with the master page) that you see at
this point are designed for testing and demonstration purposes only. In a real environment,
designers would create category and item pages to present your products in a desirable way.

Results: After completing this exercise, you should have configured a publishing site to consume data
from a product catalog site.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Supporting Multiple Languages and Locales
Previous versions of SharePoint supported mechanisms for enabling content of several different
languages to be created, translated, and updated. However, the task of translation was always performed
by a person. The variations mechanism for organizing multilingual content is still the primary method for
publishing content of different languages in SharePoint 2013, but this mechanism has been supplemented
with the Machine Translation Service for automated language translation of content.
Lesson Objectives
After completing the lesson, you will be able to:
Describe how to configure variations to support multilingual content.
Describe how the Machine Translation Service supports automated translation of content.
Describe how to configure managed metadata for multiple languages.
Using Variations for Multilingual Content
In order to support multilingual content, you can
use SharePoints variations feature. The variations
feature enables you to specify a source variation
site and have the content copied to a target
variation site where the content can be translated
into another language before being published.
The variations feature requires the SharePoint
Server Publishing Infrastructure feature.
The variations feature uses the following elements
to provide multiple sites in different languages:
Variation labels. A variation label is an
identifier for a variation site.
Variation sites. There are two types of variation sites:
o Source variation site. The source variation site is where content is authored and published and
viewed by users from the relevant locale. Content is copied from the source variation site to one
or more target variation sites. Only one source variation site can exist in a single site collection.
You cannot change the source variation site collection after it is created.
o Target variation site. Target variation sites receive content copied from the source variation site.
However, the content can be changed, typically translated, after the copy is complete. Any
content created on a target variation site is unique to that site and not automatically copied to
any other site.
Variation root site. The variation root site provides the URL and the landing page for redirection to
the appropriate source and target variation sites. The variation root site does not need to be the root
site in a site collection.
Variation hierarchy. The variation hierarchy represents all variation sites and all variation labels.
Variation pages. Variation pages are publishing pages that are copied from the variation source site
to a variation target site.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Variations site structure
Typically, your variations source site and variations target sites will be subsites of the site collection root.
For example, if the site collection root is http://www.contoso.com, the source variation site in English
might be http://www.contoso.com/en-us, and a target variation site in Spanish could be
http://www.contoso.com/es-es. Because pages are copied from the source to the target sites, the page for
company contact would be created at http://www.contoso.com/en-us/contactus and would be copied to
http://www.contoso.com/es-es/contactus, where it can be translated.
Configuring variations
Use the following process to create a site collection with multilingual variations:
1. Install any additional SharePoint Server 2013 language packs for languages that you need to support.
Each language pack supports a single language. Add only the language packs you require to all
SharePoint servers in the farm. You do not need to install the language pack corresponding to the
SharePoint Server 2013 installation language, because this language pack is already present. You do
not need to install the corresponding Windows language pack onto the SharePoint servers.
2. Create a new site collection or choose an existing site collection where you will add variations.
3. At the site collection root site, use the Variations Labels page to create a new label for the variation
source site. Creating the source label will allow you to specify the Variations Home URL and choose
the URL structure to use.
4. Create additional labels for each additional language you want to support. This will specify the target
variation site URL. You can also select which of the following content to copy from the source to the
target sites:
o Publishing Sites, Lists with Variations, and All Pages.
o Publishing Sites Only.
o Root Site Only.
5. Select whether to allow human translation on the target label and whether to allow machine
translation on the target label. This enables you to select different types of translation for different
supported languages.
6. Specify the behavior for updating existing pages. You can choose to automatically update target site
pages or allow target site contributors to choose when to update existing content from the source
site.
7. Select Create Hierarchies to set the Variations Create Hierarchies Job Definition setting. By
default, this timer job will run within the hour or you can manually run the job from the Job
Definitions page in Central Administration. This will create the site structure based on the label
definitions you created.
Variations logs
Note that most of the site creation and content copying is performed by SharePoint timer jobs. You can
see when content or updates were submitted and the success or error messages generated by viewing the
Variation logs from the site collection settings page.
Additional Reading: For more information about variations and multilingual content, see
Variations overview (SharePoint Server 2010) at http://go.microsoft.com/fwlink/?Linkid=303702
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The Machine Translation Service
You can use the Machine Translation Service in
SharePoint 2013 to translate page and site content
from one language to another.
You can create the Machine Translation Service
using Windows PowerShell or from the Service
Applications page in Central Administration. The
Machine Translation Service has the following
prerequisites:
The App Management service application
must be started in Central Administration.
You must configure server-to-server
authentication and app authentication.
The User Profile Service application must be configured and started.
The server that will run translations must be connected to the Internet.
The Machine Translation Service submits content to an online, cloud-based service to perform the
language translation. When configuring the Machine Translation Service, you can change the following
options:
Select which file types will be enabled for translation. By default, .docx, .doc, .docm, .dotx, .dot, .rtf,
.html, .htm, .aspx, .xhtml, .xhtm, .txt, and .xlf extensions are enabled.
Set the maximum binary file size for submission. Word documents are treated as binary files.
Set the maximum text file size for submission. Plain text, HTML, and XML Localization Interchange File
Format (XLIFF) files are treated as text files.
Specify a proxy server for the required Internet connection.
Specify the number of simultaneous translations to process.
Set translation performance options, such as start frequency, number of translations to start in a
group, number of retries, and queue length.
Additional Reading: For more information about configuring the Machine Translation
Service, see Create and configure Machine Translation services in SharePoint Server 2013 at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Configuring Multilingual Metadata
SharePoint can represent a term in the term store
with different labels. You will most commonly see
different labels for the same term if you
implement synonyms for terms in the term store.
For example, the term human resources may also
have the synonym personnel.
In a similar way, SharePoint can treat different
language versions of a word as being different
labels for the same term. This enables you to
define the term set once, but apply the term set in
as many supported languages as you require,
without needing a separate term set for each
language.
To implement multilingual term sets, you must perform the following actions:
1. Install the SharePoint Server 2013 language pack for each language that you require.
2. Use the Term Store Management Tool to add each language to the list of working languages for the
term store.
3. Select one language to be the default language for the term store.
There are three ways to enter terms in multiple languages:
You can use the Term Store Management Tool to enter multiple labels in each language. For
example, you can enter synonyms of the terms in each language; however, each language must have
a default label.
You can use the Machine Translation Service to translate the entire term set using the TRANSLATION
tab on the term set properties.
You can export the term set to a translation package in XLIFF format for translation and then import
the result when complete. The export and import options are available on the TRANSLATION tab of
the term set properties.
SharePoint will display the term by using the default language and label regardless of the language that
you use to enter the term.
Note: If your SharePoint environment includes multiple term stores, consider updating all
term stores to support the same languages.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Discussion: Translating Content
Consider creating multilingual content for your
SharePoint environment and discuss the following
questions:
Are you planning to use Machine Translation
Services?
Are there any issues with machine translation
for multilingual content?
How do you ensure translated content is
ready for publishing?

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 4
Enabling Design and Customization
There are many ways of customizing the look and feel of SharePoint sites. For example, you can match
corporate colors, provide clarity for navigation or content purposes, or provide a good experience on
devices with smaller form-factors. Traditional customization methods include the use of SharePoint
Designer or Visual Studio, and both of these tools are supported with SharePoint 2013. However, there are
several improvements to the way that sites can be branded and how some of the content can be
downloaded. It is important for farm administrators and SharePoint consultants to be aware of these
improvements, even if someone with a different skillset, such as a web designer, will perform the
customization tasks.
Lesson Objectives
Plan for branding SharePoint sites.
Describe the function and features of Design Manager.
Describe how to configure image renditions.
Planning Branding for SharePoint 2013
Most organizations understand the importance of
branding; it gives a consistent look and feel to
company information or products that is
recognizable to customers or consumers. Branding
is essential for Internet-facing web content in the
same way that it is for advertising or marketing
materials. Even for intranet sites, it is important to
maintain the organization brand and also develop
divisional and departmental brands in a site. These
should provide clarity for navigation, create a
common identity, and encourage consistency of
content.
The publishing templates that are available in SharePoint provide additional branding and navigation
settings beyond those that are available in other site templates. For example, you can use managed
navigation and Design Manager. The reason for this is that publishing has a far greater reliance on look
and feel than other functions such as records management.
Tools for creating a consistent look and feel
The key elements that SharePoint provides for establishing a consistent appearance are master pages,
page layouts, and CSS. You can create your own master pages, page layouts, or CSS files by using an
editor such as SharePoint Designer 2013 or Visual Studio. You can also import files from other web design
tools into Design Manager to create the necessary master pages, page layouts, and CSS.
Master pages and page layouts are held in the Master Page and Page Layouts Gallery document library
usually referred to as the Master Page Galleryin the top-level site of a publishing site collection.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Planning branding in SharePoint 2013
The key considerations when you plan for branding in SharePoint Server 2013 are as follows:
Provide tools and training. You must provide your SharePoint 2013 designers with adequate tools and
training to create the required branding for your site.
Create specifications. You must give your site designers some clear ideas on how you envision the
eventual look and feel of the site.
Prioritize your requirements. You must determine what you must brand on your site. Perhaps a simple
color change is sufficient for your requirements, or maybe you want to rebrand the whole site and
brand items such as Search controls or calendars. However, if you hardly ever use the calendar view of
events, perhaps this is too much branding at this stage in the sites development.
Consider content editors. When you brand your site, you should ensure that it keeps a consistent look
and feel throughout. With web content management in SharePoint Server 2013, you can control the
editing tools and styles that are available. The level of HTML experience that your content editors
have may dictate how you decide to implement your branding plan. For example, a Content Editor
Web Part may be too complex for some of your content editors, so you may need to consider
enabling publishing features to allow users to edit content directly on the page.
Simplify deployment. You should involve your developers in the content deployment phase.
Determine how they want to deploy any customizations, and try to synchronize your deployment
with theirs. In addition, you must ensure that your plan makes it easy to change your branding styles.
If you have to update a theme file or a logo image, you must reset IIS, and you may need to reapply it
to many sites. This will be costly and time-consuming. However, if you plan branding correctly, it will
not be necessary to reset IIS. For example, you can use the Alternate CSS option or an import that
points to another file.
Mobile device access. You should consider what type of mobile device or applications should have
access to SharePoint. Mobile devices may require additional planning for content layouts, selecting
which browsers should be redirected to mobile views, identifying browser user agent strings, and
mobile alerts.
External content embedding. You must consider any requirements for embedding external content
into SharePoint pages. SharePoint 2013 enables content editors to add HTML IFrame tags to embed
content held on external sites, such as skydrive.live.com. A site collection administrator can control
which external URLs are allowed for content by choosing which domain names are listed on the
HTML field security page.
Overview of Design Manager
Design Manager is a new feature for SharePoint
2013 that enables you to upload design assets,
such as images, HTML, and CSS, and use these to
create your master pages and page layouts. You
can launch Design Manager from the site settings
page of a site or from the settings menu.
Design Manager gives your site designers options
that form part of a process. By using Design
Manager, site designers will find all steps for the
process in one place. Not all steps are required,
and Design Manager will allow users to jump to
specific steps and tasks. Design Manager provides
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
the following functionality:
Import an already prepared design package.
Select from pre-installed designs.
Create and manage channels for different types of device.
Upload design files, including a HTML version of a master page, CSS, JavaScript, and image files.
Convert an HTML page to a master page. The HTML page can be authored in any HTML authoring
tool, enabling designers to create designs using tools which they are already familiar with.
Edit master pages.
Edit display templates for search-driven Web Parts.
Edit page layouts.
Publish and assign master pages to channels for different devices.
Create your own design package for importing to other site collections. A design package is saved as
a .wsp file.
Note: In the public-facing website in SharePoint Online, Design Manager also has the
capability to create themes and composed looks. Themes are a set of fonts and colors that you
can apply to a master page. A composed look is an association of a background image, a theme,
and a master page.
Note: Design packages are not available in the public-facing website in SharePoint Online.
Editing master pages
If your designers have uploaded an HTML page and used the option to convert the HTML page into a
master page, any changes to that master page can still be made by editing the HTML page used for the
conversion. This allows designers to continue updating or refining a site design in third-party authoring
tools if desired.
Working with display templates
Search-driven Web Parts use display templates for styling the returned properties using HTML and CSS
and to map the returned properties so the properties are available for JavaScript. Display templates are
made up of an HTML file and a corresponding .js file, but designers should only edit the HTML file; when
the HTML file is saved, SharePoint will update the .js file accordingly.
Working with page layouts
Although you can use Design Manager to create a master page from an HTML file for you, designers must
create page layouts in Design Manager first. After the page layout is created in Design Manager, an .aspx
file and an HTML file are created. This is required to create the necessary page fields that are added to the
page layout files; however, after the layout is created, designers can edit and update the HTML file with
any HTML editor.
Additional Reading: For more information about Design Manager, see Overview of Design
Manager in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=303704
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Using Image Renditions
Image renditions are a new feature in SharePoint
2013 that is designed to optimize the way images
are used in page content throughout SharePoint
site collections.
Previously, when a user uploads an image into
SharePoint with the intention of placing the image
on a page, the image is stored once with whatever
resolution is native to the image. Many page
authors do not realize that when the image is
added to a page and resized, the client browser
must still download the entire image at the native
resolution before resizing it based on the HTML
tags in the page. This can cause slow page loading times and poor site performance simply because the
browser must download much more image data than is necessary.
In SharePoint 2013, you can create image renditions that are differently sized versions of an image based
on one original source image. A content editor or author can upload an image at any resolution, and
SharePoint will automatically create specified renditions of the image and store the renditions in the BLOB
cache. When the image is added to a page, the author chooses the rendition to use.
Image renditions require the following:
The SharePoint publishing feature must be enabled on the site.
BLOB caching must be configured for the web application. The BLOB cache is a disk-based cache
present on web front-end servers.
Custom rendition sizes must be configured if required. Renditions are created at the site level.
Additional Reading: For more information about image renditions, see How to: Manage
image renditions in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=303705

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 5
Supporting Mobile Users
With the rapid increase of different types and format of web-capable devices in the current workplace, it
is important that SharePoint 2013 provide a good experience for users working from a smartphone or
tablet device. SharePoint has several new features for supporting these types of users, including the ability
to automatically provide smartphone views by redirection, provide different layouts of the same content
for tablet users, and the ability to track location data provided by a mobile device.
Lesson Objectives
Describe new features for supporting mobile devices.
Plan mobile device access for site collections and content.
Describe how the device channels feature can support mobile device users.
New Mobile Device Features in SharePoint 2013
There are several new features added to
SharePoint 2013 to provide better support for
mobile devices, such as smartphones and tablet
computers. These new features include:
Contemporary mobile device view. The
contemporary device view is a new mobile
view designed for smartphone devices that
support HTML5.
Mobile alert subscriptions. Users can subscribe
to text message alerts to be sent to a mobile
phone when SharePoint content is updated.
Device channels. Device channels enable designers to create different layouts for different types of
devices, such as a tablet.
Location. There is a geolocation field available to lists in SharePoint 2013. However, the geolocation
field must be inserted programmatically, because there is no user interface option for geolocation.
Push notifications. Push notification enable SharePoint to send notifications to applications built to
use SharePoint data, such as a smartphone application.
Geolocation
The geolocation field is designed to work with the Bing Maps service and may display a map pushpin, or
be used to highlight items of interest in the local area. You must install the SQLSysClrTypes.msi package
on every SharePoint web front-end server in the farm to display geolocation data. You must also register
and perform the following tasks with Bing Maps in order to view geolocation data from the Bing Maps
service:
Create a developer account.
Create an authentication key.
Register the authentication key in SharePoint at the farm, website, or application level.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: For more information about using geolocation, see Use the location field type in
mobile applications for SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=303706
Push notification
Push notifications require a device to register with a SharePoint site; at which time, event handler code
can interact with the Microsoft Push Notification Service. After activation on a site, a subscription store is
created as a hidden list of device subscriptions. The list is limited to 2,000 subscriptions, at which point, no
new subscriptions are accepted until older subscriptions are removed.
Additional Reading: For more information about removing push subscriptions, see Clear
push notification registrations from the subscription store in SharePoint 2013 at
Planning Mobile Device Access
In SharePoint 2013, there are two distinct methods
for supporting the use of mobile devices:
Accessing the SharePoint site directly from the
device, such as a tablet or smartphone.
Being sent SMS updates about content in
SharePoint.
Mobile browser support
SharePoint 2013 supports the use of mobile device
browsers in several different ways:
Classic view. Classic view is only applicable for
smartphone devices and renders content in HTML, CHTML, WML, or similar markup language. Classic
view is intended to provide backward compatibility for smartphone browsers that are unable to use
the new contemporary view. Classic view is available by default in SharePoint 2013.
Contemporary view. Contemporary view is for smartphone devices only and is enabled by default on
several site templates, including the Team Site, Blank Site, and Document Center templates. The
contemporary view renders in HTML5, is optimized for touch, and supports Windows Phone 7.5 and
later, iOS 5 and later on iPhone, and Android 4.0 devices. Although contemporary view is designed
only for smartphones, some slates or tablets may receive this view based on the user agent string. You
can update the browser definition file if your users experience this issue.
Full screen UI. The full screen UI view can be accessed on smartphone and tablet devices using an
option shown in the contemporary view. The full screen UI view offers the same experience as the
desktop browser view.
Device channels. Device channels enable the use of custom master pages for specific browsers or
devices. Device channels are part of the SharePoint Server Publishing Infrastructure feature and are
only available to publishing sites by default.
Additional Reading: For more information about mobile views, see Plan for mobile views
in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=303708
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Providing external access for mobile devices
In order to provide mobile devices, such as smartphones, that are often connected to the Internet and not
the local network, with access to internal SharePoint sites, you must use one of the following options:
Reverse proxy server. A reverse proxy server which supports SSL, such as Microsoft Forefront Unified
Access Gateway, offers the most secure option for publishing internal content to Internet-based
clients. A reverse proxies can offer the following measures to increase security:
o Terminating the secure SSL channel.
o Forwarding requests to internal servers instead of forwarding packets.
o Scanning HTTP requests for malicious traffic or suspicious encoding.
o Authenticating users before allowing access to internal servers.
Mobile proxy server. Mobile proxy servers can help provide mobile device access to a corporate IT
infrastructure. The mobile proxy server must forward the mobile browser HTTP headers to SharePoint.
Direct Internet access. You can place a SharePoint site on your extranet. This method only supports
basic authentication, so you must add a mechanism such as SSL to protect user credentials and
content from being intercepted.
When publishing an intranet site to Internet-based clients, you should also configure cross-firewall access.
Cross-firewall access enables you to specify which web application zone URL will be used when a user
clicks E-mail a link or Alert Me on a site. This ensures that any links sent by SharePoint will be accessible
from the Internet so that it does not matter how the user is connected when they access the link.
Configuring the browser definition file (compat.browser)
You can use the browser definition file to control which mobile device browsers, such as smartphone
browsers, should be automatically redirected to either the contemporary or classic mobile device views.
The browser definition file is the compat.browser file in the App_Browsers subfolder of the web
application path (C:\inetpub\wwwroot\wss\VirtualDirectories\<host header and port> by default). You can
change existing entries capability value to True to enable redirection, or to False to disable redirection.
You can also add new entries to this file if the devices you support are not listed.
Using mobile alerts
You can also allow users to receive text message (SMS) alerts when items change or content is updated in
SharePoint 2013. In order for the farm to send SMS alerts, you must perform the following tasks:
Set up an account with an online SMS messaging service provider.
Ensure the farm has Internet access.
Import the service providers root certificate and create a trusted root authority within the SharePoint
farm.
Configure a mobile account in the SharePoint farm to connect to the service provider.
Additional Reading: For more information about configuring text message alerts, see
Configure mobile accounts in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=303709
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Understanding Device Channels
In order to optimize the SharePoint browsing
experience across a wide range of devices and
screen formats, such as desktop computers,
tablets, and smartphones, you can use device
channels to customize the way information is
displayed for that type of device.
A device channel enables site designers to specify
different master pages, CSS, and different images,
so that the content displayed on the device is the
same basic content, but organized in way that
better fits the device for usability and
performance. Device channels are selected based
on the user agent string provided by the browser.
Creating device channels
You can create device channels from the site collection settings page or by using Device Manager. When
you create a device channel, you should configure the following settings:
Name. This is a friendly name to identify the channel.
Alias. The alias is used when you configure customization for the channel, such as a custom master
page. If you change the channel alias later, you will need to manually update master page mappings,
device channel panels, and any custom code or markup.
Device inclusion rules. Rules are used to specify the user agent substring, which will automatically
provide matching browsers with content formatted by the channel. For example, setting Windows
Phone OS 7.5 as the user agent would match only Windows Phone 7.5 devices, but setting Windows
Phone OS as the user agent would match Windows Phone 7, Windows Phone 7.5, and Windows
Phone 8 devices.
Active. The active setting selects whether automatic redirection for the channel is turned on. Setting
the channel to inactive can be useful for initial configuration and testing before activating the
channel.
Description. This is an optional field to provide a description for the channel.
You can store up to 10 device channels per site in SharePoint 2013. However, device channels are stored
in a ranked list. The ranking is important to the order of evaluation against the rules for user agent string.
For example, if you place the channel with device inclusion rule of Windows Phone OS first in the list and
a channel with a device inclusion rule of Windows Phone OS 7.5 second in the list, the second device
channel can never be used, as all Windows Phone OS agents get directed to the first channel.
Note: Device channels are only available to sites with the SharePoint Server Publishing
Infrastructure feature activated.
You can also create device channel panels that enable specific content to be rendered only on specific
device channels, such as the desktop version of the site. This is done by inserting the IncludedChannels
HTML attribute in the relevant part of the page.
Additional Reading: For more information about configuring device channels, see Plan
device channels in SharePoint Server 2013 at http://go.microsoft.com/fwlink/?Linkid=303710
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring Device Channels
Scenario
You have developed a web publishing site as a proof of concept and the business is pleased with the
outcome. Although various users within the company tested the site, one common item of feedback was
that the site did not look as good when viewed on a mobile device with a significantly smaller screen than
a desktop computer.
Your job is to modify the site to support device channels, returning a different version of the site to
mobile devices.
Objectives
After completing this lab, you will be able to create and configure device channels on SharePoint 2013
publishing sites.
Passw0rd: Pa$$w0rd
Exercise 1: Configuring Device Channels
Scenario
In this exercise, you will create and configure a device channel. First, you will create a network share for
the Master Page Gallery. This will enable developers and designers to update and test master pages and
page layouts quickly and efficiently. Next, you will create a new device channel for Windows Phone OS
devices. You will then modify a master page to include device-specific content, and verify that the device
channel behaves as expected.
Windows Phone devices are not available in the lab environment; therefore, you will use the
DeviceChannel query string to test that the device channel is working properly.
1. Create a network share for the Master Page Gallery
2. Create a new device channel
3. Modify a master page to test the device channel
4. Associate master pages with device channels
5. Test device channels
Task 1: Create a network share for the Master Page Gallery
Open the 20332B-NYC-SP-01 virtual machine. If you are not already logged on, log on as
CONTOSO\Administrator with the password Pa$$w0rd.
Create a new mapped network drive for the folder at
http://sharepoint.contoso.com/sites/staging/_catalogs/masterpage/. Assign the drive letter Z to
this mapped network drive. When you are prompted for credentials, log on as
Verify that you are able to browse the contents of the Master Page Gallery in File Explorer.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 2: Create a new device channel
In Internet Explorer, browse to sharepoint.contoso.com/sites/staging. Log on as
Use Design Manager to create a new device channel with the following properties:
Property Value
Name Windows Phone
Alias WindowsPhoneOS1
Description A device channel for Windows Phone operating systems.
Device Inclusion Rules Windows Phone OS
Make the device channel active.
Task 3: Modify a master page to test the device channel
Use the Design Manager to preview the oslo master page.
Use the snippets tool to generate a Device Channel Panel HTML snippet.
Set the IncludedChannels property of the Device Channel Panel to WindowsPhoneOS1, update
the snippet, and then copy the snippet to the clipboard.
In File Explorer, move to the masterpage share.
Open the oslo.html file by using Notepad, and find the <div id="s4-bodyContainer"> element.
Add the HTML snippet for the device channel panel immediately after the div element that you just
located.
Locate the line that reads You should replace this div with content that renders based on your
Device Channel Panel Properties. (This will be approximately six lines into the content that you just
added.) Delete this text, and in its place type This content is only visible on the Windows Phone
OS device channel.
Save and close the file.
Task 4: Associate master pages with device channels
On the Staging site, in Design Manager, assign the oslo master page to every device channel.
Note: You can assign master pages to device channels from the Publish and Apply Design page in
Design Manager.
Task 5: Test device channels
Browse to the Staging site home page.
In the Internet Explorer address bar, add the following query string to the site URL, and then reload
the page:
?DeviceChannel=WindowsPhoneOS1
When the page reloads, verify that the page includes a highlighted block at the top of the page with
the text This content is only visible on the Windows Phone OS device channel.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: In most cases, developers and site designers would develop custom master pages for each
device channel. In addition, designers can use device channel panels to control how content is rendered
on different devices.

Results: After completing this exercise, you should have created, configured, and tested a device channel.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you learned how to plan for web content management. With SharePoint configuration,
you learned how to configure cross-site collection publishing with product catalogs and search-driven
Web Parts. You also learned how to support multilingual requirements for an organization, both for
content, such as webpages, and for supporting elements, such as metadata. You learned about new
options for branding SharePoint sites, and how SharePoint 2013 supports the use of mobile devices as
clients.
Review Question(s)
Test Your Knowledge
Question
Which of the following is a requirement to enable image renditions?

Storing images in an Image Library.
BLOB caching configured on the web application.
Enabling anonymous access for the web application.
Configuring a search service application.
Using a publishing site template.
Test Your Knowledge
Question
Which of the following is not part of the SharePoint Publishing Infrastructure feature?

Device channels.
Approvers permission level.
Variations.
Site columns.
Output caching.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Test Your Knowledge
Question
Which of the following is a requirement to configure managed navigation?

Machine Translation Service application.
Publishing Site template.
Document Center template.
User Profile Service application.
Managed Metadata Service application.
Test Your Knowledge
Question
When configuring a site collection for multilingual variations, what must you create for
each language that you will use?

A new site.
A new site template.
A new label.
A new term.
A new term set.
Test Your Knowledge
Question
Which of the following is a prerequisite for configuring device channels?

Device Manager.
Publishing Site template.
Managed navigation.
SharePoint Server Publishing Infrastructure feature.
Content Organizer feature.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
11-1
Module 11
Managing Solutions in SharePoint Server 2013
Contents:
Lesson 1: Understanding the SharePoint Solution Architecture 11-2
Lesson 2: Managing Sandbox Solutions 11-8
Lab: Managing Solutions 11-13

Module Overview
As a SharePoint administrator, it is important to understand the features that are available in Microsoft
SharePoint Server 2013. However, there are often specific functional requirements that may be part of
SharePoints feature set but are not included in certain site templates. There may also be sites that require
repeatable customization of lists or libraries, or custom code deployments that are necessary to add
capabilities that are not available out-of-the-box. Developers use features and solutions to add and
control these functionality requirements. Administrators, on the other hand, must understand how
features and solutions are deployed and managed in order to meet user needs in a SharePoint farm.
Objectives
Describe and manage SharePoint features and solutions.
Manage sandboxed solutions in a SharePoint 2013 deployment.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
11-2 Managing Solutions in SharePoint Server 2013
Lesson 1
Understanding the SharePoint Solution Architecture
SharePoint features enable administrators to activate and deactivate specific sets of SharePoint
functionality. However, it is important to understand that different feature scopes affect functionality at
different levels within a SharePoint farm. In addition, administrators can upload new solutions that add
additional features and functionality to certain farm elements, such as new site templates, new timer jobs,
and new workflow behavior.
Lesson Objectives
Describe SharePoint features.
Deploy and activate features.
Describe farm solutions.
Deploy, update, and retract farm solutions.
Overview of SharePoint Features
A SharePoint feature is a set of functionality that
an administrator can enable or disable. Features
can include many types of objects, such as Web
Parts, workflows, and forms. When an
administrator enables a feature, all the
functionality that is part of it is enabled and
becomes available to users.
Note: A feature consists of a set of XML files
on each SharePoint server. There is always one
feature.xml file and one or more manifest files,
which also use XML. Features are declarative and
do not contain additional code. Any components that are deployed by a feature are defined in
XML.
Built-in features
Much of the default SharePoint functionality is encapsulated into features. These features allow you to
enable the functionality that you need and disable the functionality that you consider unnecessary. For
example, in a site collection that uses the Team Site template, you could activate the Document ID feature
to provide all documents with a unique ID code. Different site templates have different site collection and
site features activated by default, but you can activate a feature to provide required functionality after a
site collection or site has been created.
Keep built-in features in mind when troubleshooting SharePoint. If users cannot find a tool or facility in
SharePoint that they know is included in the product, it may be because a built-in feature is disabled; in
which case, you must enable the feature first before its functionality can be accessed by users.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Custom features
Custom functionality that extends SharePoint directly is usually encapsulated in a feature. Therefore, the
features that appear in your SharePoint system depend on the customizations you have installed. Custom
features may be created by any of the following:
Third parties. If you purchase and install a SharePoint customization, it is likely to add one or more
features. These features may appear in different scopes.
Your own developers. Developers in your organization often build their customizations into features.
You must install and activate these features to make the custom functionality available to users.
Feature scope
A SharePoint feature is installed into one of the following scopes, depending on where its functionality is
relevant and who will administer the feature:
Farm Scope. These features include customizations that apply across multiple servers, site collections,
and web applications throughout the SharePoint farm. Farm scope features are enabled and disabled
by farm administrators.
Web Application Scope. These features include customizations to all servers that host a web
application. Web application scope features are enabled and disabled by farm administrators.
Site Collection Scope. These features include customizations to a single site collection and its subsites.
Site collection scope features are enabled and disabled by site collection administrators.
Website Scope. These features include customizations to just a single SharePoint site. Website scope
features are enabled and disabled by site administrators, site collection administrators, and site
owners.
Note: Some features have dependencies and can require another feature at the same
scope or at the parent scope to be activated first. For example, the SharePoint Server Publishing
site feature requires the SharePoint Server Publishing Infrastructure site collection feature to be
activated in the parent site collection.
Possible feature contents
Features can contain many types of objects that can be used to customize SharePoint. For example:
Web Parts and Visual Web Parts. Users can add these to Web Parts pages.
ASP.NET user control or server controls. Users cannot modify these user interface components.
Custom actions. These shortcuts appear on a menu in SharePoint, for example, the Site Actions menu.
List instances. These ensure that when the feature is activated, a new list is created.
List templates. Users can use these templates to create new lists.
Modules. These are files that are automatically added to SharePoint by the feature.
Feature receivers. These contain code that runs when a feature is activated.
Content types. These define new types of items or documents.
Fields. These can be assembled into content types.
Workflows. These model and manage a business process.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Deploying and Activating Features
After a developer creates a SharePoint feature to
encapsulate the customizations they have created,
you must install and activate the feature to make
the custom functionality available to users.
Deploying features
A feature consists of a folder hierarchy. The name
of the top folder is the name of the feature; this
folder contains a file called Feature.xml, along with
other files and folders. Deploying a feature is a
two-step process:
1. You must first copy the folder structure to the
following location:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES
2. You must then install the feature using Windows PowerShell. The following example shows the
PowerShell command that will install the feature that is contained in the folder titled ContosoProjects
(it will look for the ContosoProjects folder in the path mentioned in the prior step):
Install-SPFeature -Path "ContosoProjects"
After you install the feature, it is visible in the list of features at the correct scope. The scope is determined
by the developer when he or she creates the feature.
Note: If you have multiple web front-end servers in your SharePoint farm, you must install
each feature on every web front-end server to ensure its availability. However, if a feature is
incorporated into a solution package, administrators need not deploy the feature to each web
front-end server in the farm. For more information about deploying solution packages, see the
remaining topics in this lesson.
Activating features
After you install your feature, its functionality is not available to users until you activate it. You can do this
in the browser interface. The following example shows the steps to activate a feature that is site-scoped:
1. In the site where you want to use the feature, click the Settings menu, and then click Site settings.
2. Click Site Features.
3. Locate the feature and then click its Activate button.
You can also activate, deactivate, and remove features by using Windows PowerShell. The following
examples show the PowerShell commands that will perform these functions on the feature that is
contained in the folder titled ContosoProjects:
Enable-SPFeature -Identity ContosoProjects
Disable-SPFeature -Identity ContosoProjects
Uninstall-SPFeature -Identity ContosoProjects
Where the identity parameter is either the name of the feature folder (such as ContosoProjects) or the
feature GUID.
After you install and activate a feature, users can begin to employ its custom functionality.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Overview of Farm Solutions
A SharePoint farm solution is a set of functionality
assembled into a package that administrators can
install in a single operation. These are available for
an on-premises deployment, but not for
SharePoint Online. Solution packages make
administration and distribution of SharePoint
customizations significantly easier than with
features alone.
Characteristics and creation
A farm solution package consists of a single file
with a .wsp extension. The .wsp file is a
compressed cabinet file containing all the files and
information needed for the custom functionality. Developers can create .wsp files by using the solution
Package Designer tool in Microsoft Visual Studio or alternate tools such as MAKECAB, when they are
ready to distribute their custom project.
For SharePoint administrators, the advantage with farm solution packages is that after you add the
solution to Central Administration, SharePoint handles distribution of the necessary files to all SharePoint
servers in the farm. Distribution of the solution files will also occur automatically when adding new servers
to the farm. This automated process makes working with farm solutions significantly easier for
administrators than manually adding features.
Package content
A solution package can contain any number of the following:
Features
Site definitions
Assemblies
Files
Updates to web.config files
Notice, for example, that a developer could include two featuresone with site scope and one with web
application scopeinto a single solution package for easy deployment.
Most third-party SharePoint customizations are distributed as solution packages, not individual features.
You do not have to install these features manually because they install with the solution package;
however, you might have to activate these features.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Managing Farm Solutions
SharePoint farm administrators can deploy,
upgrade, and retract farm solutions. You can only
add a solution to a farm using Windows
PowerShell in the SharePoint Management Shell;
however, you can upgrade and retract farm
solutions through either PowerShell cmdlets or
Central Administration.
Deploying farm solutions
Deploying a farm solution typically involves three
steps:
1. Add the solution to the farm solution store.
You cannot use Central Administration to perform this step; instead, you must use the Add-
SPSolution PowerShell cmdlet in the SharePoint Management Shell.
2. Deploy the farm solution to SharePoint servers in the farm. To perform this step in Central
Administration, click System Settings, click Manage farm solutions, and then choose the solution
that you want to deploy. You can also deploy solutions by using the Install-SPSolution PowerShell
cmdlet.
3. Activate the feature where required. Many farm solutions will deploy functionality controlled by one or
more features. In these cases, you must activate the required features to enable the installed
functionality.
Upgrading farm solutions
There are two ways to upgrade a solution that was previously installed and deployed to the farm:
Replacement. To perform a replacement type of upgrade, you retract the old version of the solution
and optionally remove it from the farm solution store. You then add the new version and deploy it to
the farm. It is not necessary that the new solution package (.wsp file) have the same name or GUID as
the old version; however, if the old version is retracted but not removed from the solution store, the
new version must have a different filename and GUID.
Update. To perform an update type of upgrade, you use the Update-SPSolution cmdlet. SharePoint
installs and deploys a new version of the solution package, which has a different file name but the
same GUID as the old version. SharePoint detects that the GUIDs are the same and automatically
retracts the old version before deploying the new version. If the solution contains features, the
features will remain activated, but assemblies and certain other files in the feature are updated with
the versions from the new solution package.
Note: When you successfully upgrade a solution, SharePoint backs up the previous version
of the solution in the configuration store. This backup is used by the solution framework in the
case of an upgrade failure. Only a single backup copy is stored for each solution.
Note: You must use the replacement upgrade method if the new version of the solution
differs from the installed version in any of the following ways:
The new version has different features compared to the old version.
The new version changes the ID or scope of a feature.
The new version has a changed version of a feature receiver.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The new versions elements.xml file and the installed versions elements.xml file are different.
The new version has changes to the Property elements in a feature.xml file.
Retracting farm solutions
There are three steps to removing a farm solution:
1. Deactivate features. Deactivate any features that are part of the solution.
2. Retract the solution. This step can be performed from the Manage farm solutions page in Central
Administration or by using the Uninstall-SPSolution cmdlet. Retracting the solution reverses the
deployment step.
3. Remove the solution. This step deletes the solution itself from the SharePoint farm solution store. You
can perform this step from the Manage farm solutions page in Central Administration, or by using
the Remove-SPSolution cmdlet.
Additional Reading: For more information about deploying solutions, see Installation and
Deployment of a Farm Solution in SharePoint 2010 at
For more information about upgrading solutions, see Upgrading a Farm Solution in SharePoint
For more information about retracting solutions, see Uninstallation and Retraction of a Farm
Solution at http://go.microsoft.com/fwlink/?Linkid=303713

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Managing Sandbox Solutions
In addition to farm solutions, you can deploy solutions in a more limited fashion by using sandbox
solutions. Sandbox solutions limit the scope of the solution to an individual site collection, prevent farm-
wide access to code, and enable site collection administrators to upload solution files. This approach
enables more flexibility without affecting farm stability when adding custom code, and enables custom
code deployment within the SharePoint Online environment. Although the deployment of Sandbox
solutions is still supported, you should remember that the new app model is the preferred approach.
Lesson Objectives
Describe sandbox solutions.
Configure the user code service.
Configure resource quotas for sandbox solutions.
Overview of Sandbox Solutions
The SharePoint sandbox is an isolated, restricted
environment in which to run solution packages
within the context of a single site collection and by
using a dedicated application pool. This way,
solutions in the sandbox cannot affect stability and
administrators can set strict quotas on the
resources they consume.
The sandbox environment
The sandbox places the following restrictions on
the solutions that run within it:
Solutions run in a separate process called
SPUCWorkerProcess.exe. This protects other SharePoint and Windows services and processes.
Solutions run a version of the SharePoint Object Model with some classes removed. These are classes
that may affect security and stability if poorly used.
Solutions run under a strict code access security policy. This increases protection against malicious
code.
Solutions are governed by resource quotas set by administrators. You can use these quotas to ensure
that solutions do not over-consume resources and cause contention and slow responses.
The following capabilities and elements are not supported in sandboxed solutions:
o Access to the Internet to make web service calls.
o Access to a hard disk to read or write files. However, you can read and write to lists and libraries
within SharePoint Online.
o Web application-scoped or farm-scoped features.
o Adding assemblies to the global assembly cache.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
o Running security-related functionality; for example, RunWithElevatedPrivileges or other
SPSecurity methods.
o Custom action groups.
o HideCustomAction element.
Note: Although the sandbox is a restricted environment, solutions within it can still access
most of SharePoints facilities and remain powerful.
Sandboxed solutions are sometimes called user solutions. They are stored in the Solution Gallery in a site
collection, which you can access from the Site Settings page. Site collection administrators can upload
new solutions to the sandbox at any time and enable them without involving farm administrators or
developers. You can also use the Install-SPUserSolution PowerShell cmdlet to add sandbox solutions.
SharePoint composites and the sandbox
SharePoint composites are custom applications created by users in SharePoint sites that are adapted to
the needs of a team or department. The browser interface, SharePoint Designer, and Windows InfoPath
forms can all be used to create custom applications without any code or developer involvement.
SharePoint composites can include:
Custom lists, libraries, and content types.
Custom workflows.
Business Connectivity Services (BCS) connections to external data sources.
Custom InfoPath forms for items and workflows.
When a SharePoint composite is complete, a user can save it as a user solution. This packages the site as a
.wsp file and stores it in the Solution Gallery at the site collection level. You can download the .wsp file
from the gallery and use it to install the composite application in other site collections or SharePoint
farms. This enables users and power users to distribute their custom applications to other parts of your
organization.
Sandbox solutions and SharePoint Online
SharePoint Online, which is part of Microsofts Office 365 platform, also supports the uploading and use
of sandbox solutions. However, SharePoint Online imposes some additional restrictions on sandbox
solutions that are not present with on-premises SharePoint deployments. SharePoint Online performs
additional validation checks when solutions are uploaded to the Solutions Gallery to prevent activation of
solutions using specific elements. The following capabilities and elements are not supported in sandboxed
solutions for SharePoint Online:
Content type binding
Web Part connections
Additional Reading: For more information about customization capabilities in SharePoint
Online, see SharePoint Online: An Overview for Developers at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Configuring the User Code Service
The sandbox relies on the user code service to
provide the restricted environment in which to run
solutions. As an administrator, you must
understand this service application and configure
it in Central Administration.
User code service processes
The following processes are required to support
the sandbox and provide the isolated and
restricted environment:
SPUCHostService.exe. This is the user code
service itself. This process manages worker
processes and enforces quotas. In the services list, this process is labeled SPUserCodeV4.
SPUCWorkerProcess.exe. This is the process in which sandboxed solutions run, isolated from other
SharePoint and Windows services.
SPUCWorkerProcessProxy.exe. This process enables the user code service to partake in the service
application infrastructure.
Note: You can find these processes in Task Manager and the SharePoint 2013 User Code
Host service in the services application. However, you should not start and stop the processes and
services in these tools. Instead, use Central Administration to determine on which servers the user
code service runs.
Configuring the User Code Service in Central Administration
Use the following steps to configure the servers that will run the user code service and support the
sandbox:
1. In Central Administration, under System Settings, click Services on Server.
2. At the top of the service list, choose the SharePoint server that you want to administer.
3. In the list of services, click Microsoft SharePoint Foundation Sandboxed Code Service.
4. Click Start or Stop to enable or disable the service on this server.
Additional Reading: For more information about sandbox solutions and sandbox code
execution, see Sandboxed Solutions at http://go.microsoft.com/fwlink/?Linkid=303715
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Configuring Quotas for Sandbox Solutions
A key feature of the sandbox is the way it restricts
the server resources that each solution can
consume in a day. When a solution runs, an
algorithm calculates points that reflect the
processor time, memory usage, database queries,
and other server resources that it uses. Farm
administrators set a maximum number of points
that each sandboxed solution can consume in a
day. Administrators can also tune the algorithm to
adapt it more closely to the available resources on
their servers.
Setting quotas
It is recommended that you use quota templates to control sandbox resource quotas and storage quotas
for site collections. Quota templates make it easier to apply standard quota values against many site
collections, and you can apply a quota template during site collection creation. Perform the following
steps to set sandbox resource quotas in a quota template:
1. In Central Administration, click Application Management, and then click Specify quota templates.
2. Choose an existing template to copy and edit, or start with a blank template.
3. Under Sandboxed Solutions With Code Limits, specify the maximum resource usage per day in
points.
4. You can also specify a warning level. Administrators receive an e-mail alert when a solution exceeds
this limit.
Perform the following steps if you want to alter sandbox resource usage limits for a site collection
individually without using a template:
1. In Central Administration, click Application Management, and then click Configure quotas and
locks.
2. At the top of the window, select the site collection you want to administer.
3. Under Site Quota Information, you can specify the maximum usage per day in points.
4. You can also specify a warning level. Administrators receive an e-mail alert when a solution exceeds
this limit.
Points calculation
SharePoint uses 14 metrics to calculate points. These include the following values:
CPU cycles. When the processor uses a predefined number of cycles on the sandboxed solution, a
point is logged.
Percentage processor time. When the sandboxed solution uses more than a predefined percentage of
the processing time, a point is logged.
Critical exception count. When a predefined number of exceptions occur in a sandboxed solution, a
point is logged.
Thread count. When the solution exceeds a predefined number of threads in the SPUCWorkerProcess
process, a point is logged.
SharePoint database queries. When a solution initiates more than a predefined number of queries to
the SharePoint content database, a point is logged.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
As you can see, there is a predefined number involved in each metric. The administrator can influence the
algorithm by setting these numbers in PowerShell.
Blocking a sandboxed solution
Farm administrators can also block any sandboxed solution. Usually, an administrator does this when the
solution consumes resources too heavily or poses a security issue. Perform the following steps to block a
solution:
1. Start Central Administration, and then click System Settings.
2. Under Farm Management, click Manage user solutions.
3. In the File box, in the Solution Restrictions section of the Sandboxed Solution Management page,
either type the full path of the file that contains the solution to block or use the Browse button to
browse for the file to block.
4. You can optionally type a message in the Message box. This message will be displayed when a user
tries to use the solution.
5. Click Block, and then click OK.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab: Managing Solutions
Scenario
The IT department has completed the initial rollout of SharePoint to the business, and generally, the
deployment has been successful. However, there have been some complaints from departments that had
previously used SharePoint as a repository. After some investigation into the complaints, your manager
has discovered a common reason for the complaints. All of the departments who are now complaining
had previously deployed custom solutions to their local SharePoint deployments. Currently, the global
SharePoint solution does not support custom code, so these departments are struggling to complete tasks
made easier by their custom solutions.
Most of the custom solutions were developed as sandboxed solutions. Your job is to modify the
SharePoint deployment to permit sandboxed solutions. You must configure SharePoint to permit
deployment, but you must also configure monitoring so that you can ensure no sandboxed solution has a
detrimental effect on the SharePoint deployment. In addition to preparing the SharePoint farm for
sandboxed solutions, you must also deploy a farm solution used by one of the departments. Developers in
the IT department have reviewed the farm solution, and they are happy that it has been developed
correctly; it is very unlikely to have a negative effect on the SharePoint deployment after you deploy it.
Objectives
Configure a SharePoint farm to support sandboxed solutions.
Configure a SharePoint site to support sandboxed solutions.
Deploy farm solutions by using PowerShell.
Virtual Machine: 20332B-NYC-DC-11, 20332B-NYC-SP-11, 20332B-NYC-DB-11
Password: Pa$$w0rd
Exercise 1: Configuring a Sandboxed Solution Management at the Farm
Level
Scenario
In this exercise, you will configure a SharePoint farm to support sandboxed solutions.
You will start necessary services and configure how requests from sandboxed code should be load
managed. You will also create quota templates and apply those templates to site collections, thus
restricting the potential impact of a sandboxed solution that does not manage resources efficiently.
Finally, you will block a solution that you know uses excessive resources to prevent users from loading it
on a SharePoint site.
1. Start the sandboxed code service
2. Create a quota template to control sandboxed resource usage
3. Configure load balancing and block a solution
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 1: Start the sandboxed code service
Pa$$w0rd.
On the Central Administration website, browse to the Services on Server page.
Ensure the Microsoft SharePoint Foundation Sandboxed Code Service. Is running.
Task 2: Create a quota template to control sandboxed resource usage
On the Central Administration website, browse to the Application Management page.
Create a new quota template with the following properties:
Property Setting
Name Standard Template
Storage limit Do not limit storage
Sandboxed solutions maximum usage daily threshold 200 points
Sandboxed solutions warning email daily threshold 100 points
Create a new quota template with the following properties:
Property Setting
Name Enhanced Template
Storage limit Do not limit storage
Sandboxed solutions maximum usage daily threshold 500 points
Sandboxed solutions warning email daily threshold 450 points
Configure the sharepoint.contoso.com site collection to use the Standard Template quota
template.
Configure the admin.contoso.com site collection to use the Enhanced Template quota template.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Configure load balancing and block a solution
On the Central Administration website, browse to the Sandboxed Solution Management page.
Add the BadWebPart.wsp solution as a blocked solution with the message This solution does not
comply with company policies. You will find the BadWebPart.wsp solution in the E:\Mod11 folder
on the virtual machine.
Configure sandboxed code to run on the same server as a request for maximum performance.

Results: After completing this exercise, you should have configured a SharePoint farm to support
sandboxed solutions.
Exercise 2: Configuring Sandboxed Solution Management at the Site
Collection Level
Scenario
In this exercise, you will configure a site collection to support sandboxed solutions.
You will verify the quotas applied at the farm level, and then finally add a sandboxed solution to the site
collection.
1. Verify sandboxed code quotas
2. Add a sandboxed solution
Task 1: Verify sandboxed code quotas
In Internet Explorer, browse to the http://sharepoint.contoso.com site. Log on as
Browse to the solution gallery for the sharepoint.contoso.com site collection.
Verify that the resource quota is 200 server resources.
Browse to the http://admin.contoso.com site. Log on as administrator@contoso.com with the
password Pa$$w0rd.
Browse to the solution gallery for the admin.contoso.com site collection.
Verify that the resource quota is 500 server resources.
Task 2: Add a sandboxed solution
Add the Contoso Pharmaceuticals Brand.wsp solution to the solution gallery. You will find the
Contoso Pharmaceuticals Brand.wsp solution in the E:\Mod11 folder on the virtual machine.
Activate the Contoso Pharmaceuticals Brand.wsp solution.

Results: After completing this exercise, you should have verified the quotas applied to a site collection,
and added a sandboxed solution to the site collection.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 3: Deploying Farm Solutions
Scenario
In this exercise, you will install and deploy a farm solution by using Windows PowerShell. After installing
and deploying the farm solution, you will view and activate the site collection feature added by the farm
solution.
1. Install and deploy a farm solution
2. Enable features added by a farm solution
Task 1: Install and deploy a farm solution
Use the Add-SPSolution PowerShell cmdlet to deploy the Contoso Pharmaceuticals Clinical Trial
Management.wsp farm solution. You will find the farm solution in the E:\Mod11 folder.
Use the Install-SPSolution PowerShell cmdlet to install the Contoso Pharmaceuticals Clinical Trial
Management.wsp farm solution. You should permit global assembly cache deployment.
Task 2: Enable features added by a farm solution
In Internet Explorer, navigate to the http://sharepoint.contoso.com site.
Browse to the Site Settings page for the sharepoint.contoso.com site.
View the list of features installed on the site collection.
Activate the Contoso Pharmaceuticals Clinical Trial Management feature.

Results: After completing this exercise, you should have installed and deployed a farm solution by using
PowerShell, and then activated the features added by that farm solution.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
This module examined how features can be used to control SharePoint functionality at the farm, web
application, site collection, and site levels, and how custom features can be deployed to a SharePoint
farm. This module also reviewed how developers can package features and other functionality into
solutions for easier deployment and management by farm administrators.
You also learned how sandbox solutions can be used to limit custom code access to the SharePoint
environment and to allow site collection administrators to deploy custom functionality.
Review Question(s)
Test Your Knowledge
Question
The second of the three steps required to deploy a farm solution must be completed
using which of the following Windows PowerShell cmdlets?

Add-SPSolution
Install-SPSolution
Deploy-SPSolution
Install-SPUserSolution
Add-SPUserSolution
Test Your Knowledge
Question
Which of the following processes runs the solution code in a sandbox solution?

W3wp.exe
SPUCHostService.exe
SPUCWorkerProcess.exe
SPUCWorkerProcessProxy.exe
Svchost.exe

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
12-1
Module 12
Managing Apps for SharePoint Server 2013
Contents:
Lesson 1: Understanding the SharePoint App Architecture 12-2
Lesson 2: Provisioning and Managing Apps and App Catalogs 12-5
Lab: Configuring and Managing SharePoint Apps 12-11

Module Overview
SharePoint apps are new to Microsoft SharePoint Server 2013 and provide an additional capability to
provide application functionality within the context of SharePoint. SharePoint apps supplement the
capabilities of farm solutions and sandbox solutions, while providing a user experience that offers a
measure of self-service customization capabilities without putting the stability or security of the farm at
risk.
Objectives
Describe SharePoint apps and the supporting SharePoint infrastructure.
Provision and configure SharePoint apps and app catalogs.
Manage how apps are used within a SharePoint 2013 deployment.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
12-2 Managing Apps for SharePoint Server 2013
Lesson 1
Understanding the SharePoint App Architecture
SharePoint apps provide site owners and other authorized users with the ability to add customizations to
sites from a central store. However, the underlying architecture of SharePoint apps requires some
additional components to be configured for the farm before the app catalog or the SharePoint store can
be leveraged.
Lesson Objectives
Describe SharePoint apps.
Describe the requirements to support SharePoint apps.
Describe how the app catalog and SharePoint store enable app deployment.
Overview of SharePoint Apps
SharePoint apps are a new way of providing
application functionality in SharePoint 2013 sites
and site collections. In previous versions of
SharePoint, providing custom functionality
required the deployment of solutions, either at the
farm level or as sandbox solutions at the site
collection level. Although SharePoint 2013
continues to support the deployment of solutions,
SharePoint apps provide an additional and more
flexible way of providing additional functionality
to users.
SharePoint apps are isolated within their own app
domain, which effectively restricts the operation of a SharePoint app to the site level. An app domain
represents a SharePoint site with its own host header that is dedicated to the app; this is sometimes
referred to as an app web. Site collection and farm level features or server-side code cannot be deployed
with a SharePoint app.
SharePoint apps can be run in three different ways:
SharePoint hosted. SharePoint apps can be run in the same farm as the content the user is accessing.
Windows Azure hosted. SharePoint apps can be run on Windows Azure in the cloud. If you are using
SharePoint Online and you install a SharePoint app, the Windows Azure resources can be
automatically provisioned.
Provider hosted. SharePoint apps can be hosted on a dedicated server in your organization, or they
can be hosted on the app developers server.
SharePoint apps can only deploy the following components:
Features (web-scoped only).
Custom actions (including shortcut menu items and ribbon customizations).
Remote event receivers. Remote event receivers are not available to SharePoint hosted apps.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Markup that references existing Web Parts and app parts. Custom Web Parts cannot be deployed
with a SharePoint app.
Custom cascading style sheets (CSS) files.
Custom JavaScript files.
Modules. A module is a set of files.
Pages.
List templates.
List and library instances.
Custom list forms.
Custom list views.
Custom content types.
Fields that use existing field types. Custom field types cannot be deployed by SharePoint apps.
Microsoft Business Connectivity Services (BCS) models scoped to the site level. This can include
external content types based on the model and external lists that use those content types. BCS
models deployed with a SharePoint app are not stored in the Business Data Connectivity (BDC)
service shared service store; instead, they are stored as a file in the app web.
Workflows. Only declarative workflows or workflows that use the new Windows Azure-hosted
workflow runtime are allowed. You cannot include coded workflows that use the SharePoint-hosted
workflow runtime in a SharePoint app.
Property bags. A property bag holds the properties of a feature.
Web templates. You cannot deploy site definitions with SharePoint apps.
Additional Reading: For more information about the SharePoint app model, download
the SharePoint 2013: App Overview for IT Pro from
Farm Infrastructure for SharePoint Apps
In order to deploy SharePoint apps, you need to
configure certain SharePoint components at the
farm level. SharePoint apps require:
DNS configuration. SharePoint apps require a
dedicated domain name.
A Subscription Settings Service application.
SharePoint apps always require this service
application, even though it is usually only
required for multitenant farm configurations.
An App Management Service application. This
service application is needed to run the app
catalog in your farm.
An app catalog. You must create at least one app catalog before you can upload or deploy SharePoint
apps.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: You must also ensure that there is at least one instance of the Microsoft SharePoint
Foundation Subscription Settings Service and the App Management Service running on a server
in the farm.
The App Catalog and the SharePoint Store
A SharePoint user with the Manage Lists
permissions on a site can add SharePoint apps
from two sources:
SharePoint Store. The SharePoint Store is an
Internet-based site, hosted by Microsoft, with
apps made available by third-party vendors
for use within SharePoint 2013 farms.
SharePoint apps can be free, require licenses,
or offer trial periods before licenses are
required.
App Catalog. The app catalog holds a set of
SharePoint apps that have either been directly
uploaded into the app catalog, such as custom developed apps, or have been pre-approved from the
SharePoint Store and added to the catalog. An app catalog applies to one or more web applications
in SharePoint.
Farm administrators can control users access to SharePoint apps in a number of ways:
You can allow or prevent users from downloading SharePoint apps directly from the SharePoint Store.
Users can make requests from the SharePoint store instead of downloading.
Farm administrators and app catalog site owners can add apps from the SharePoint Store to pre-
approve them.
Only users with the Manage Lists permission can add SharePoint apps to a site.
In addition, some apps in the SharePoint store appear greyed-out by default and are not available for
installation. These apps require sites with Internet-facing endpoints, so they will not work with many
internal SharePoint deployments. In order to allow these apps to be installed, you must enable the
Internet-facing endpoints web application feature from Central Administration.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Provisioning and Managing Apps and App Catalogs
Use of SharePoint apps can help you to provide a degree of self-service capability to site owners in your
SharePoint farm environment. However, it is important to understand farm configuration requirements for
supporting SharePoint apps, in addition to recognizing how administrator actions will affect the user
experience for SharePoint app deployment.
Lesson Objectives
Configure DNS to support SharePoint apps.
Create a farm infrastructure to support SharePoint apps.
Deploy apps from an app catalog.
Describe app permissions.
Monitor SharePoint apps.
Configuring DNS for SharePoint Apps
Before configuring the farm for SharePoint app
deployment, you must configure DNS to support
the SharePoint app model.
Each SharePoint app runs on a dedicated site that
is given a specific URL, called the app domain, in
order to provide app isolation for security
purposes. You need to create and register a DNS
domain name that will apply to all SharePoint
apps in your farm, such as ContosoApps.com. In
addition, each instance of an app has a unique
host header in the form http://<Prefix>-
<appHash>.
ContosoApps.com/sites/web1/<appname>, where <prefix> is a prefix that can be specified by a farm
administrator and supports multi-tenancy, <appHash> is a unique ID created by SharePoint for that
instance of the SharePoint app, and <appname> is the name of the app.
Apps for SharePoint cannot use multiple zones with Alternate Access Mappings (AAMs). This means that
you cannot deploy SharePoint apps to sites in web applications that use multiple zones with AAMs.
Instead, consider using host header site collections because these are fully supported with SharePoint
apps.
Note: It is recommended that you do not make the app domain a subdomain of the
domain that holds DNS records for SharePoint; this configuration could leak information held in
cookies or other sites. For example, if your SharePoint farm is at sharepoint.contoso.com, do not
use apps.contoso.com for the SharePoint apps DNS requirements. It is also recommended that
you configure the app domain to be in the Internet or Restricted Sites security zones in Internet
Explorer.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In order to configure DNS to support SharePoint apps, you must perform the following:
Create a new DNS zone for your SharePoint apps, such as yourcompanyapps.com. This domain
should be publicly resolvable if you require Internet access to SharePoint sites that use SharePoint
apps.
Create a wildcard alias (CNAME) DNS record for the app domain that points to the SharePoint farm.
For example, if you app domain is contosoapps.com and your SharePoint farm is
sharepoint.contoso.com, you would create a CNAME record in the contosoapps.com zone where the
alias name is * and the target host is sharepoint.contoso.com.
Note: If you are using SSL for your SharePoint sites, you should also use SSL for your apps.
You should create or purchase a wildcard certificate for your app domain in order to support SSL
with several apps in your SharePoint farm.
Additional Reading: For more information about configuring the farm for SharePoint
apps, see Configure an environment for apps for SharePoint (SharePoint 2013)
Creating the App Catalog
After you configure your SharePoint farm to
support SharePoint apps, you must create an App
Catalog. At least one app catalog is required to
upload custom developed apps, and to allow users
to download or request apps from the SharePoint
store.
Perform the following steps to create an app
catalog:
From the Apps page in Central
Administration, go to the Manage App
Catalog page.
On the Manage App Catalog page, select the web application for which you want to provide an app
catalog.
Choose to create a new app catalog or connect an existing app catalog to the web application.
Creating a new app catalog creates a new site collection with a special template for managing
SharePoint apps. You must provide this site collection with a title, URL, site collection administrators,
and any users or groups that you want to be able to browse the app catalog site directly. Site
collection administrators of the app catalog site will be able to upload custom apps to the catalog
and approve apps from the SharePoint store.
Use the Manage App URLs page to set the app domain name that you have configured with DNS,
such as contosoapps.com, and the host header prefix that will be used for app sites, such as app-
12345ABCD.contosoapps.com. Although the app prefix is used to support multitenant hosting, you
must also set an app prefix for the default tenant in single tenant farms. You only need to configure
the app domain once for the farm.
After the app catalog site is created, you can control permissions settings for the SharePoint store, upload
custom apps to the app catalog, and control app request behavior.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: Each app catalog is associated with one or more web applications in your farm. You
can create one app catalog and use the same app catalog for all web applications, or you can
create more than one app catalog to make different apps available for different sites, but only
where those sites are in different web applications.
Deploying Apps
SharePoint apps can be deployed through the app
catalog in a number of ways:
Users who are granted permission to the app
catalog site can upload custom developed
apps for deployment.
Farm administrators can browse the
SharePoint store and choose to add apps from
the store to the app catalog. This can be
useful if, for security reasons, you do not
provide all site owners the ability to download
any app from the SharePoint store. If a farm
administrator adds the app from the
SharePoint store to the app catalog, the app becomes available to all site owners.
If end users are not allowed to install apps directly from the SharePoint store, they can still browse the
store, but they can only request apps and not add apps directly. Requests are stored in the app
catalog site for an administrator to approve or reject.
Using app requests
If you set the option Should end users be able to get apps from the SharePoint Store? to No in
Central Administration, this will not prevent end users from browsing the SharePoint store. However, end
users will not be able to add apps from the store directly; instead, the add option is replaced with a
request option. So end users can browse the SharePoint store and request apps, and the app request is
added to a list on the app catalog site. An administrator for the app catalog site can then determine what
to do with the request. Note that approving or rejecting the app request is not performed with the
approve/reject list item buttons on the ribbon interface; rather, the administrator must edit the list item
and change the Status field to the appropriate value.
Also note that setting the value to Approved or Closed as Approved does not automatically add the
item to the app catalog. The administrator must manually click the link provided in the View App Details
field and then click Add in order to add the app to the app catalog; otherwise, end users will not be able
to install the app.
Licensing apps
When choosing to add an app from the SharePoint store, you have the option to select the type of license
for the app you are adding. SharePoint store app licenses commonly fall into two categories:
For everyone in the organization. This effectively represents an unlimited use license so site owners
and administrators do not need to keep track of the number of users accessing the site using this app.
For a certain number of users. With this option, you must choose which users have a license for the
app. If you do not need the app for everyone in the organization, specifying a fixed number of users
can reduce the license cost for some apps.
You can use the Manage App Licenses page in Central Administration to view the current licenses for
SharePoint apps, to add or remove licenses, and to add users to a license.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Upgrading apps
Apps in the SharePoint store or custom apps you have added to the app catalog may be upgraded while
they are still in use. Users can deploy app upgrades to sites where the older version of the app is already
running. When a newer version of the app is deployed, the following process occurs:
A new site is created for the new version of the app.
The original app site is marked as read-only.
Content is copied from the original app site to the new version site.
The old version site is deleted.
This process will be seamless to end users.
Additional Reading: For more information about deploying apps, see Manage the App
Catalog in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=303718
Overview of SharePoint App Permissions
When a user with the Manage Lists permission
adds a SharePoint app to a site, the app will
request the permissions and scope that are
necessary for the app to perform its function. For
example, a user could install an app that displays
video from an asset library. In this scenario, the
app would require read-only permission to be able
to view the contents of the library.
There are four types of permission that SharePoint
apps can request:
Read-only. Enables an app to view content,
such as lists, items, files, and pages.
Write. Enables an app to add, update, and delete content in lists and libraries, and update Web Parts.
Write permission also includes read-only permission.
Manage. Enables an app to manage lists and libraries, apply style sheets, apply themes, and customize
pages. Manage permission also includes write permission.
Full Control. Enables an app to have full control at the specified scope.
A SharePoint user adding an app must assign permissions to the app before installation can complete. A
SharePoint user cannot assign a permission level to an app that he or she does not possess. For example, a
user with Designer permission level on a site cannot grant an app full control permission, because the user
does not have full control permission. In this scenario, the app would not install to the site. Apps cannot
have custom permissions; any requests for custom permissions from the app will be ignored by SharePoint
2013 and have no effect.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Scopes
SharePoint app permissions also have a related property called a permission request scope, which controls
where the requested permission is applied. For example, an app might request read-only permission on a
single list or for the entire site. The following permission request scopes are available to SharePoint 2013
apps:
Site collection
Site
List
Tenant
App authorization policies
When an app is run or used, an access check is performed to ensure the necessary rights exist to access or
update items and content. This check ensures access to the data that the app is accessing at the time of
use. This is different from the permissions request discussed earlier, which checks whether the user can
enable the app to install. Developers specify one of the following app authorization policies to evaluate
access to content:
App-only policy. This policy checks if the app has been granted permissions to access content. This is
used if the app is not directly acting on a users behalf.
User-only policy. This policy checks if the current user has been granted permissions to access content.
User and app policy. This policy checks if both the current user and the app have been granted
permissions to access content. This policy is required when a SharePoint Store app that runs outside
SharePoint needs to act on behalf of a user to access user resources.
Additional Reading: For more information about SharePoint app permissions, see App
permissions in SharePoint 2013 at http://go.microsoft.com/fwlink/?Linkid=303719
Monitoring SharePoint Apps
A SharePoint farm administrator can choose to
monitor apps that are deployed in sites
throughout the farm. You can monitor one or
more apps, but you cannot monitor individual
instances of an app separately. For example, if you
add an app called Super Video Viewer that is
installed in five different sites, you cannot monitor
only the instance of Super Video Viewer at
http://app-
3b2eb611126e6f.contosoapps.com/sites/training;
instead, you must monitor all instances of Super
Video Viewer.
Monitoring apps provides you with the following information, which is updated on a 24-hour basis:
Number of licenses purchased
Number of licenses used
Number of failed installs
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Number of failed upgrades
Number of runtime errors
Number of install locations
Number of installs
Number of uninstalls
Number of launches
Note: For app monitoring to collect information, there must be a search service application
to collect analytics data, and the following timer jobs must be active:
ECM analytics timer job name: Usage Analytics timer job for Search Service
Usage DB timer job name: Microsoft SharePoint Foundation Usage Data Import

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab: Configuring and Managing SharePoint Apps
Scenario
Following Contosos successful deployment of SharePoint, various departments have made requests for
specific functionality. In some cases, they are asking for functionality provided by their previous solution;
in others, the requests represent improvements that the departments have wanted for many years, but
that were not possible with their previous system. The IT department wants to ensure that any custom
development work, or apps purchased from the SharePoint app catalog, are visible to the entire business
to ensure every department has the opportunity to benefit from each purchase. Because not all of the
requests can be achieved in the current budget, managers in the IT departments are currently meeting
managers within the business to discuss development priorities.
To ensure maximum visibility for the custom solutions, managers in the IT department want all custom
code developed as SharePoint apps, and wherever possible they want to purchase existing apps from the
SharePoint app catalog. They want to make the apps available through a corporate app catalog. It is your
job to configure SharePoint to support apps and then add a corporate app catalog to the SharePoint
deployment. Finally, you will configure monitoring for an app, and test it by deploying it to a site. None of
the apps required by the business are available yet so you will use a sample app for this lab.
Objectives
Configure SharePoint Server 2013 to support apps.
Create and configure a corporate app catalog
Deploy and monitor apps.
Virtual Machine: 20332B-NYC-DC-12, 20332B-NYC-SP-12, 20332B-NYC-DB-12
Password: Pa$$w0rd
Exercise 1: Configuring a SharePoint Farm to Support Apps
Scenario
In this exercise, you will configure a SharePoint farm to support apps.
You will configure DNS settings to create a new domain to host deployed apps, and you will make
changes to the SharePoint server to route requests for that domain to the appropriate IIS website.
You will then use PowerShell to create shared service applications which are required to support app
deployment on a farm. Finally, you will start the necessary services.
1. Configure DNS settings to support app deployment
2. Create a new service account
3. Add an additional IP address to the SharePoint server and configure IIS to bind to the new IP address
5. Use PowerShell to create new shared service applications
6. Use the Central Administration website to start necessary services
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 1: Configure DNS settings to support app deployment
Pa$$w0rd.
Open DNS Manager.
Add a new forward lookup zone for the contosoapps.com domain.
Add a new host record to the contosoapps.com forward lookup zone with the following properties:
Property Setting
Name *
Task 2: Create a new service account
Property Setting
Full name SharePoint Apps Service App Pools
UPN logon AppsAppPools@contoso.com
SAM Account Name logon contoso\AppsAppPools
Password Pa$$w0rd
Task 3: Add an additional IP address to the SharePoint server and configure IIS to
bind to the new IP address
Open Network Connections to view the network adapters installed on this server.
Add the following additional IP address to the Ethernet network adapter:
o 172.16.1.50
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In IIS add a binding to the SharePoint - sharepoint.contoso.com80 website that binds it to the
172.16.1.50 IP address on port 80. You should not specify a host name.
Note: Loopback checking is disabled on this virtual machine. Microsoft does not recommend
disabling loopback checking; however, you may not be able to access your apps on your SharePoint
server if you do not disable loopback checking. You do not need to disable loopback checking if you do
not want to access your apps on your SharePoint server. For more information about disabling loopback
checking, see You receive error 401.1 when you browse a Web site that uses Integrated Authentication and
is hosted on IIS 5.1 or a later version at http://go.microsoft.com/fwlink/?Linkid=303720
Use the Central Administration website to register the contoso\AppsAppPools account you created
in the previous tasks as a managed account.
Task 5: Use PowerShell to create new shared service applications
Open a SharePoint 2013 Management Shell scripting window.
Use the New-SPServiceApplicationPool cmdlet to create a new application pool for the App
Management Service application with the following properties:
Property Setting
Name AppManagementAppPool
Account AppsAppPools@contoso.com

Note: Throughout this task you will need to reference objects you create in previous steps. Saving a
reference to each object you create in a variable will help you to complete this task.
Use the New-SPAppManagementServiceApplication cmdlet to create a App Management
application instance with the following properties:
Property Setting
Name App Management
Application pool AppManagementAppPool
Use the New-SPAppManagementServiceApplicationProxy cmdlet to create a service application
proxy for the new App Management application instance with the following properties:
Property Setting
Name App Management Proxy
Service application App Management
Verify that the App Management Service and an associated proxy connection now appear on the
Manage Service Applications page on the Central Administration website.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Use the New-SPServiceApplicationPool cmdlet to create a new application pool for the
subscription settings service application with the following properties:
Property Setting
Name SubscriptionSettingsAppPool
Account AppsAppPools@contoso.com
Use the New-SPSubscriptionSettingsServiceApplication cmdlet to create subscription settings
application instance with the following properties:
Property Setting
Name Subscription Settings
Application pool Subscription Settings AppPool
Use the New-SPSubscriptionSettingsServiceApplicationProxy cmdlet to create a service
application proxy for the new Subscription Settings application instance with the following properties:
Property Setting
Service application Subscription Settings
Verify that the Subscription Settings service and an associated proxy connection now appear on the
Manage Service Applications page on the Central Administration website.
Task 6: Use the Central Administration website to start necessary services
Navigate to the Services on Server page on the Central Administration website.
Verify that the App Management Service service is running. If it is not running start the service.
Verify that the Microsoft SharePoint Foundation Subscription Settings Service service is running.
If it is not running start the service.

Results: After completing this exercise, you should have configured a SharePoint farm to support apps,
including starting services, creating shared services, and necessary domain configuration.
Exercise 2: Creating and Configuring a Corporate App Catalog
Scenario
In this exercise, you will configure a corporate catalog for a web application.
You will create a new corporate catalog by using an explicit managed path, and then you will configure
the URL and SharePoint store settings for that corporate catalog.
1. Add a new managed path to the sharepoint.contoso.com web application
2. Create an app catalog
3. Configure app URLs
4. Configure SharePoint store settings
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
On the Central Administration website, browse to the Web Applications Management page.
Add an explicitly included managed path named contosoapps to the sharepoint.contoso.com web
application.
Task 2: Create an app catalog
Browse to the Apps page.
Create a new app catalog in the sharepoint.contoso.com web application with the following
properties:
Property Setting
Title Contoso Apps
URL http://sharepoint.contoso.com/contosoapps
Permitted end users Everyone
Task 3: Configure app URLs
Configure app URLs with the following settings:
Property Setting
App domain contosoapps.com
App prefix contoso
Task 4: Configure SharePoint store settings
Configure the SharePoint Store settings to prevent users from getting apps directly from the
SharePoint store.

Results: After completing this exercise, you should have created and configured a corporate catalog.
Exercise 3: Deploying and Monitoring Apps
Scenario
In this exercise, you will deploy and monitor a sample app.
You will add the sample app to the corporate catalog that you created in the previous exercise. You will
then add the app from the catalog to a SharePoint site.
After deploying the app, you will attempt to monitor the app. To enable monitoring, you will deploy an
instance of the Search service, and perform a full search crawl. After the crawl completes, you will
configure SharePoint to monitor the sample app.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
1. Add a sample app to the app catalog
2. Add the sample app to a SharePoint site
3. Attempt to monitor the sample app
4. Create service accounts for the search service
5. Register the service accounts as SharePoint managed accounts
6. Use the Central Administration website to create a new shared search service application
7. Monitor the sample app
Task 1: Add a sample app to the app catalog
In Internet Explorer, on a new tab, navigate to the corporate app catalog you created in the previous
exercise (http://sharepoint.contoso.com/contosoapps). Log on as administrator@contoso.com
with the password Pa$$w0rd.
Add the ContosoApp.app app to the corporate catalog. Make the ContosoApp.app app a featured
app so that it will appear in the "noteworthy" section. You will find the ContosoApp.app app in the
E:\Mod12 folder on the virtual machine.
Task 2: Add the sample app to a SharePoint site
Navigate to the http://sharepoint.contoso.com site.
Add the ContosoApp app to the http://sharepoint.contoso.com site. Wait until the ContosoApp
app finishes installing before continuing.
Browse to the ContosoApp app instance. Use the user name administrator@contoso.com and the
password Pa$$w0rd.
Task 3: Attempt to monitor the sample app
Switch to the Central Administration website.
Browse to the Monitor Apps page.
Verify that you are not currently able to monitor any apps as the search service is currently disabled.
Property Setting
Full name Search Service Admin Web Service Application Pool
UPN logon SearchAdminAppPool@contoso.com
SAM Account Name logon contoso\SearchAdminAppPool
Password Pa$$w0rd
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Property Setting
Property Setting
Full name Search Service Query Web Service Application Pool
UPN logon SearchQueryAppPool@contoso.com
SAM Account Name logon contoso\SearchQueryAppPool
Password Pa$$w0rd
Property Setting
Full name Search Service Account
UPN logon SearchService@contoso.com
SAM Account Name logon contoso\SearchService
Password Pa$$w0rd
On the Central Administration website, navigate to the Managed Accounts page.
Register the CONTOSO\SearchAdminAppPool account you created in the previous task as a
managed account.
Register the CONTOSO\SearchQueryAppPool account you created in the previous task as a
managed account.
Register the CONTOSO\SearchService account you created in the previous task as a managed
account.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 6: Use the Central Administration website to create a new shared search service
application
Create a new instance of the Search Service Application service application by using the following
properties:
Property Setting
Name Contoso Search
Search service account CONTOSO\SearchService
Admin application pool name SearchAdminAppPool
Admin application pool account CONTOSO\SearchAdminAppPool
Query and site settings application pool name SearchQueryAppPool
Query and site settings application pool account CONTOSO\SearchQueryAppPool
Start a full search crawl of local SharePoint sites. Do not continue until the search crawl completes.
Task 7: Monitor the sample app
Browse to the Monitor Apps page.
Add the ContosoApp app as a monitored app.
Note: The data for each app is updated every 24 hours. As a result, the app may not correctly report
the number of installations.

Results: After completing this exercise, you should have added a sample application to the corporate
catalog, deployed that app to a SharePoint site, configured SharePoint to support monitoring, and
monitored the sample app.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
This module examined the difference between SharePoint apps and SharePoint solutions. It also identified
the configuration requirements to create a working app catalog, and the prerequisites needed for app
deployment and access to the SharePoint store.
Review Question(s)
Test Your Knowledge
Question
You are the administrator for SharePoint at Litware Inc. You currently use
intranet.litwareinc.com and extranet.litwareinc.com as web application host headers
within your SharePoint farm. What would be the best app domain to use for your farm?

Apps.litwareinc.com
Litwareapps.litwareinc.com
Apps.litwareinc.local
Litwareapps.com
Litwareinc.apps
Test Your Knowledge
Question
After creating the app catalog, what must you configure?

You must prevent end users from accessing the SharePoint store.
You must configure the app prefix.
You must set up multitenancy.
You must allow end users to access the SharePoint store.
You must monitor all apps.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
13-1
Module 13
Developing a Governance Plan
Contents:
Lesson 1: Introduction to Governance Planning 13-2
Lesson 2: Key Elements of a Governance Plan 13-6
Lesson 3: Planning for Governance in SharePoint 2013 13-13
Lab A: Developing a Plan for Governance 13-18
Lesson 4: Implementing Governance in SharePoint 2013 13-20
Lab B: Managing Site Creation and Deletion 13-26

Module Overview
Governance as it relates to SharePoint can be described as a way of controlling a SharePoint environment
through the application of people, policies, and processes.
Governance is necessary for all IT systems as a whole, and in particular for SharePoint deployments, which
often introduce significant change in business processes, available functionality, and day-to-day working
practices.
It is important to understand that governance must reflect the needs of the organization and how it
should best use SharePoint. Therefore, the IT department cannot be the only body governing SharePoint;
input must come from corporate sponsorship across the organization. The IT department must still act as
the technical authority for SharePoint; however, this is just a single part of how SharePoint governance
must be brought together from different parts of the organization.
Objectives
Describe the concepts of governance.
Describe the key elements of a governance plan.
Plan for governance in SharePoint Server 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
13-2 Developing a Governance Plan
Lesson 1
Introduction to Governance Planning
It is important to understand the importance of governance in the wider context of a SharePoint
deployment. Without planned governance, many SharePoint deployments fail to deliver key requirements
and functions for the organization; however, with governance, SharePoint deployments can grow and
develop in a controlled, useful fashion, rather than an uncontrolled mess that requires a much higher
administrative overhead.
Lesson Objectives
Describe the need for governance with a SharePoint deployment.
Describe the components of a governance plan.
Overview of Governance Planning
A Microsoft SharePoint Server 2013
implementation is only as good as its underlying
structure and content. Therefore, a sturdy
governance plan is critical to help ensure that your
implementation delivers the right content to your
users in an efficient, timely, and effective manner.
What is governance?
Governance defines the following properties of a
SharePoint deployment:
The deployments architectural elements.
The person(s) who are allowed to make
certain types of changes within those elements.
The key decision maker for request and escalation purposes.
These definitions should be clearly stated in a governance plan, so that all users have a clear
understanding of the use and ownership of various aspects of the SharePoint deployment. This helps
ensure that growth and development of content areas and features are in line with corporate expectations
for the platform, in a way that complements the current state of the environment.
What governance is not
Governance is not just permissions. Permissions should be used to support the governance plan, but a
good governance plan should identify who to escalate a change to if it is beyond the authority of the
current user. Governance is not put in place to prevent growth or change; rather, governance should
accommodate and even embrace growth and change. This should happen in a measured way that
identifies the reason for change and the best approach to encompass that change in the current
environment with an understanding of the effects on the business.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The Importance of Planning Governance
SharePoint Server 2013 is designed to empower its
users, who are generally not IT or content
management specialists. Therefore, it is crucial that
your governance plan not only improve your
deployments usability, but also save your users
time and effort when they create and deploy new
sites.
A governance plan defines the roles, processes,
and technologies that are required to:
Prevent portal, team site, and content sprawl
by defining a content and site review process.
Help ensure that content quality is maintained during its life cycle by implementing quality
management policies for the content.
Provide a consistently high-quality user experience by defining guidelines for site designers, content
designers, and authors, and by ensuring that the governance plan is correctly implemented and
followed.
Establish clear decision-making authority and escalation procedures so that you can handle and
resolve policy violations and conflicts in a timely manner.
Help ensure that the implementation strategy correctly maps to business objectives and requirements
so that it continuously delivers value to the organization.
Help ensure that content is secured and stored to comply with guidelines for records retention.
There are some key reasons as to why planning for governance in SharePoint Server 2013 is so important:
Many SharePoint capabilities, such as document IDs and Content Organizer, are not mandatory for
your users, but they still need guidance about what they can do with these capabilities to gain true
benefit from them.
SharePoint Server 2013 is designed to empower users. Governance helps ensure that they accept their
responsibility for the content that they create and use, and for the actions that they perform on the
site.
The increased emphasis and availability of social computing features such as tagging, bookmarking,
and ratings has increased the types of content to govern.
SharePoint Server 2013 introduces new capabilities for sharing metadata across multiple site
collections and server farms. A successful governance plan provides the required planning and control
to utilize these features.
SharePoint Server 2013 provides new and more user-friendly record management capabilities,
including the ability to declare a record in place. In-place record management enables you to
manage records in the same document repository as active documents. These new record
management features enable you to create and enforce a record management strategy as part of
your overall governance plan for content management.
SharePoint Server 2013 provides users with more customization power over their sites. For example,
users can deploy out-of-the-box themes, they can use Microsoft SharePoint Designer 2013, and they
can create their own sandboxed solutions. Therefore, you must include decisions in your governance
plan that consider how, where, and when to allow configuration using these new capabilities.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: Creating a governance plan is as equally important for Office 365-based SharePoint
deployments as for on-premise deployments.
Key Areas Requiring Governance Planning
Each organization has its own individual
requirements and business goals that influence the
way it handles and applies governance. Large
organizations may take governance to one
extreme by locking down everything; whereas a
small organization may only apply a very small
amount of governance to its users and their
content.
However, in both cases, any successful
implementation of SharePoint Server 2013 must
consider planning for governance of the following
key areas of the business.
Information architecture
The aim of information architecture is to create a solution that enables an organizations users to gather,
store, retrieve, and utilize the information that is needed to meet the organizations business objectives. A
wide-ranging appraisal of your company's information architecture can help you to determine possible
inefficiencies such as:
Inconsistent use of metadata that can make it difficult to search for, and compare, related data or
content.
A poorly designed and managed content storage infrastructure that can result in documents existing
in multiple versions without any method for controlling and identifying authoritative and recent
versions.
A poorly cataloged and managed data storage infrastructure that can result in decision-makers
finding and relying on incorrect data.
A poorly designed portal navigation and presentation infrastructure that can make it difficult for users
to find sites and data that are important to their job.
SharePoint platform architecture features
SharePoint Server 2013 includes architecture features that your governance plan should address,
including:
A service application architecture that enables delegation of control for individual service
applications.
Multi-tenancy capabilities.
Managed accounts that automate password changes.
The ability to use the Windows PowerShell command-line interface and scripting language tool for
SharePoint administration.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
SharePoint Server 2013 farms and servers
Unless you have a governance plan, the fast spread of disparately managed web servers running
SharePoint Server 2013 can have unforeseen consequences, including:
Rogue farms or servers hosting loosely managed site collections that do not have a common search
index, navigation, or security system.
Servers hosting insecure applications, which can compromise the integrity of your content.
Technical support requests for local SharePoint Server 2013 servers that are running without the
support team's knowledge.
Critical activities, such as compliance with regulatory standards being inconsistently administered
across servers.
Day-to-day maintenance tasks, such as data backup and restore operations or product updates,
which may not be properly carried out due to lack of training or inconsistent server configuration.
Changes in site ownership can create confusion about content ownership or lock sites.
As the use of SharePoint increases in your enterprise, you should implement a set of well-governed
hosting services that makes SharePoint available and establishes control over its use and configuration.
Customization policy
SharePoint Server 2013 includes customizable features and capabilities, such as business intelligence,
forms, workflow, and content management. The ability for users to customize look, feel, behavior, and
content brings more risks to the stability, maintenance, and security of your SharePoint environment. To
support these customization capabilities while maintaining control of your overall governance plan, you
should develop a customization policy that addresses the following considerations:
Deciding whether to approve customization tools, such as SharePoint Designer 2013.
Determining which elements of a site can be customized, and who can perform the customization.
Determining whether third-party SharePoint apps can be added to a site, and who can add
SharePoint apps.
Determining methods for managing source code, such as a source control system, and standards for
documenting the code.
Providing standards for site development, such as guidelines for coding best practices.
Providing standards for testing and verification processes.
Providing standards for packaging and installation. You should control the use of sandboxing, which
enables site owners to host custom solutions in a partly trusted environment so that they do not
adversely affect the other parts of your implementation of SharePoint.
Supporting different methods of customization, such as allowing the use of Web Parts to integrate
Microsoft Silverlight 3 applications with SharePoint sites.
Branding
You should include branding in your governance plan if you are designing an information architecture
and a set of sites for use across your enterprise organization. A prescribed set of branding policies helps to
ensure that sites have a consistent look and feel by using enterprise imagery, fonts, themes, and other
design elements. For example, you can import a design package directly into a SharePoint site, which then
automatically applies the branding assets to all of its subsites.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Key Elements of a Governance Plan
In order to create a governance plan, it is important to understand the elements that are required to be
part of the plan. A governance plan for SharePoint should contain a basic statement about what
SharePoint should deliver for the organization, along with the key principles of the plan. This information
should help determine the types of content to include; the areas of the organization that should be the
focus of SharePoint support and development; and the priorities for the platform when faced with
multiple options for change.
In addition, a SharePoint governance plan should outline the roles and responsibilities of those using
SharePoint and the standards that should be followed for adding or updating content, commenting or
rating content, and the look and feel of pages, navigation, and other common elements.
Finally, a SharePoint governance plan must include information about how users will receive training, who
will provide the training, and the methods that will be used for the training. It is not an understatement to
say that introducing SharePoint to people in a workplace brings significant change to the way those
people work with information, so no one should expect people to instantly know how best to use or
implement SharePoint and its myriad features. A carefully planned approach to training can yield
dividends in user adoption and acceleration of the platform functionality.
Lesson Objectives
Describe a vision statement for a governance plan.
Describe the roles and responsibilities that should be included in a governance plan.
Describe the principles that form the fundamental statements of a governance plan.
Describe standards and policies that should be included in a governance plan.
Describe how a training plan supports a governance plan.
Vision Statement for a Governance Plan
Your vision statement should describe what you
want to accomplish by implementing SharePoint
Server 2013, and how the solution delivers value
to the business and its employees. A lucid vision
statement provides critical guidance on the
decision tradeoffs that you will inevitably need to
make when you create your governance plan. You
will typically write the vision statement when you
begin planning the implementation, but you will
probably need to refine it as the project matures.
The following is an example of a vision statement
for SharePoint Server 2013:
SharePoint Server 2013 provides a holistic view of organizational assets that simplifies employee
interaction with our enterprise business systems. It also helps to improve collaboration within the
company and with our suppliers, partners, and customers. In this way, it improves employee productivity
and employee and customer satisfaction.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
After you write your vision statement, the next step is to determine and document the roles and
responsibilities of the people who are involved in your implementation of a SharePoint Server 2013
solution.
Roles and Responsibilities for a Governance Plan
Roles and responsibilities define how each
employee as an individual or as a member of a
team is responsible for ensuring the ultimate
success of a solution. Documenting the roles and
responsibilities of your SharePoint Server 2013
solution is a crucial part of your governance plan.
It defines who has authority to mediate conflicting
requirements and make overall decisions about
branding and policy.
Determining roles and responsibilities should be
based on policy decisions made by the
organization in response to questions such as:
Who will be responsible for the technical management aspects of the environment, for items such as
hardware and software implementation, configuration, and maintenance?
Who will be allowed to install new features, Web Parts, or other code enhancements?
Who will be responsible for setting up new sites?
If this responsibility lies with your IT team, they will probably need to establish some SLAs for site
setup responsiveness with the business stakeholders. However, if you delegate this responsibility to
users, you must also give them adequate training to ensure that they follow agreed and acceptable
principles and standards for allowed content, naming, storage, and so on.
Who will be granted access to each page and site, and who can grant access to others?
How much responsibility for page and site design will be delegated to page owners?
Will users be allowed to modify Web Parts on pages that they own on team sites? Can those users
modify Web Parts on pages that are part of the corporate intranet publishing solution?
Will page owners be allowed to fix some Web Parts on the page, or all content on their pages?
Who will be responsible for the management of metadata?
Who will be allowed to set up or request new content types or site columns, and how much central
control will the farm administrator have over the values in site columns and the properties of content
types?
If the governance plan defines that page and site owners are responsible for their own content
management, will the farm administrator decommission those pages in which no one in the
organization claims ownership or responsibility for the content?
There are several key roles to consider in your governance plan, and in some smaller organizations, an
individual can often fulfill multiple roles.
The following tables list some of the typical roles and responsibilities for the overall solution and for each
site or site collection. You will need to adapt both the responsibilities and the names that you use for each
role to suit your specific organizational environment.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Overall solution role Key responsibilities
Executive sponsor Serves as the executive-level champion for the solution,
whose primary strategic responsibilities are positioning the
solution as a critical mechanism for achieving business
value and helping to communicate the value of the
solution to the management levels of the organization.
Governance committee Serves as a governance body that has ultimate
responsibility for meeting the goals of the solution.
Business owner Manages the overall design and functional integrity of the
solution from a business perspective.
Solution administrator Manages the overall design and functional integrity of the
solution from a technology perspective. Works in
partnership with the business owner.

Site and site collection role Key responsibilities
Site sponsor/owner Serves as the centralized, primary role for ensuring that
content for a particular page or site is properly collected,
reviewed, published, and maintained.
Site steward/contact Manages the site by performing the everyday tasks
required to help ensure that the content on the site or
page is accurate, relevant, and up to date. This person will
also act as the Content Steward for the sites for which they
are responsible.
Site designer Creates and maintains the site or site collection design in
environments where site design is delegated to business
users.
Site user Uses the solution to access and share information. Users
may have different access permissions for different sections
of the solution, sometimes acting as a content contributor,
and at other times acting as a content consumer.
Guiding Principles for a Governance Plan
The guiding principles of a governance plan define
the organizational preferences to support the
vision. These critical statements reflect best
practices that all users and site designers must
understand and internalize to ensure the success
of your SharePoint Server 2013 solution.
You can use the example principles in the
following table as a starting point to help define a
set of guiding principles for your solution. You
should consider creating some supplemental
reference material to help users internalize these
principles, or perhaps add a Principle of the Day
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
to the home page of your solution. Users who have a good understanding of your guiding principles are
more likely to follow your governance guidelines.
Guiding principle of
governance
Implication Key consideration
Example General Principle
Policies are tied to the
scope and intention of the
site. Governance policies
are more flexible for sites
that have limited access
than for sites that are
shared with a broad
audience.
The different audiences for
sites enable you to adapt
the governance model
according to business
needs. You will enforce
some policies across the
entire organization, but
site owners may also apply
their own policies.
One size does not fit all.
There are rules, but you
must identify when it is
appropriate to deviate
from a standard to achieve
a business objective more
effectively.

Example Security Principle
Role-based security
governs access control and
permissions on both
intranet and extranet areas
of the portal.
Users may have different
permissions on different
areas of the portal, which
has an implication for both
governance and training.
Although most users may
not have content
contribution privileges for
tightly governed intranet
pages, all users have Full
Control privileges for their
own My Site.
You may not have the
same permissions on every
page of the portal.
Example Site Design
Principle
You must provide a
consistent user experience.
Users should be able to
find key information on
any collaboration site and
search for the content that
they need.
All sites also follow a
consistent baseline design
template to ensure
consistency and usability
across collaboration sites.
When you design your site,
you must consider what
your users needs are.
Example Content Principle
Site sponsors/owners are
accountable, but everyone
owns the responsibility for
content management.
Site owners are
accountable for content
quality and archiving old
content on a timely basis,
but site users are
responsible for making site
owners aware of content
that needs updating.
Everyone is responsible for
content management.
Note: It is especially important to remember the one size does not fit all guiding
principle when it comes to developing your governance plan.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Policies and Standards for a Governance Plan
Policies define the rules for using SharePoint
Server 2013, whereas standards describe the best
practices for using SharePoint Server 2013. From a
governance perspective, statutory, regulatory, and
organizational requirements typically drive
policies, while standards are developed based on
user experience from working with SharePoint and
web content.
Policies. When you create policies, you expect
your users to follow them as prescribed. If
your organization is subject to regulatory
oversight, you must ensure that you can
enforce your policies so that the organization remains compliant.
Standards. You typically create standards to encourage consistent working practices. You would
expect your users to implement the standards that are relevant to them or their job function.
To ensure that your policies and standards are current and relevant:
Verify that your policies and standards for SharePoint are not at odds with other organization-wide
policies.
Publish policies and standards where your users can easily find and follow them.
Regularly review and amend policies and standards to keep them correctly mapped to your changing
organizational needs.
Example content policies and standards
Consider the following example content policies and standards when developing the governance plan for
your organization:
Posting content to existing pages or sites. Your plan should include a policy or standard to cover the
following:
o Ensuring that only single copies of documents exist
o Only posting content that the user owns
o Maintaining a content posting cycle
o Only editing documents that are in place to avoid breaking links
o Controlling file formats and names
o Keeping links updated
Posting content to the home page. You should consider creating a specific policy for posting content
to the home page of your portal solution, particularly on the intranet home page.
Content auditing and review. You should consider creating a policy to define the frequency and type
of review that you will have on each type of content or site. You must also ensure that the review
cycles that you define conform to any regulatory or statutory requirements.
Records retention. You should ensure that you define clear policies regarding how users retain and
dispose of records. You must also create policies that define the responsibilities of content owners to
identify content as records and associate the appropriate record retention code to a given content
item.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Example design policies and standards
Consider creating policies and standards for each of the following design elements:
Creating new subsites. If end-user site owners have permissions that enable them to create their own
information architectures for sites under their control, you must provide some guidance to help them
understand best practices for creating nodes in an information hierarchy.
Page layout and organization. Anyone who has page design permissions must remember the guiding
principle about focusing on the end user. However, these page designers should also be familiar with
best practices for general design usability.
Content types and metadata. Your governance plan must include standards and policies for the
content types and site columns that you have used in your solution. The plan must also include
policies for how users can request the creation of a new enterprise content type or site column.
Social tags and ratings. Your governance plan should include guidelines for how you want users to
participate in social tagging and ratings, and should provide guidance and examples of meaningful
tags for your organization.
Content-specific guidelines and policies. You should provide some standards and policies for specific
types of SharePoint content such as blogs, wikis, announcements, discussion boards, media libraries,
document libraries, and links.
Security. Your governance plan should clearly define any specific security policies and describe how
they should be applied within your SharePoint sites.
Branding. Your governance plan should take into account whether it is possible to change the
corporate branding in a specific SharePoint Site Collection. Site users will be confused if the branding
scheme changes from site to site. Therefore, when you consider defining branding standards and
policies, you should do so with the site user in mind.
Creating Training Plans
After the governance plan itself, the most
important element in a successful SharePoint
deployment is the human element. Training is
oftentimes one of those forgotten components of
a governance plan, even though it is crucial to the
success of the implementation. A widespread
training plan should demonstrate how to use
SharePoint according to the standards and
practices that your governance plan defines. It
should also explain why those standards and
practices are important. The plan should cover the
type and level of training that is required for
specific roles, and it should prescribe any appropriate training tools.
Training should not just happen once; it should be a continuing activity. Also, training is not just about the
features and functions of SharePoint; it is also about training your user base in the roles and
responsibilities, guiding principles, and policies and standards of governance. By properly educating your
user base, you can affect significant business process change, increase satisfaction with your
implementation of SharePoint, and help to reduce support costs.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Who to train
You should provide adequate and job-relevant training for all staff who are involved in your SharePoint
solution, including:
Site administrators
Site designers
Site developers
Help desk
Content contributors
Workflow approvers
End users
What to train
Your training plan should consider what kind of training to provide to your user base. Some key skills
include:
Site and site collection administration (including with Windows PowerShell).
Document, records, and digital asset management.
Site support.
Site and page design.
How to train
You should consider the methods you will employ for training users. Training does not necessarily imply
taking several people out of a team or department at one time and training those people in a classroom
format. Although the classroom format can work well for some types of training and for certain user
levels, you should also consider the following training delivery methods:
Virtual instructor led training, using web-based delivery sessions
Video-based training
On-the-job coaching
Self-paced learning using book or web-based training materials

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Planning for Governance in SharePoint 2013
When planning governance, it is important to create a team of individuals who will control the way in
which SharePoint is used and grows in the organization. You should also identify those people in the
organization who need to have input to this body, and the level of expertise these people represent.
You must also consider how your governance plan will be assembled and approved before being
published for users to view and implement.
Lesson Objectives
Describe the members in a governance committee.
Assemble a governance plan.
Describe the process for implementing a governance plan.
List best practices and pitfalls for a governance plan.
Building a Governance Committee
A successful implementation of SharePoint Server
2013 requires constant communication and
partnership among business managers, IT
professionals, and information workers. One major
aspect of your governance plan is the creation of
the governance committee. This committee should
include representatives from as many of the
following groups and roles as possible:
Executive stakeholders. Define the overarching
goals of the governance committee. They
should also provide the authority that it
requires, and they should regularly assess the
success of the policies and standards that your governance plan implements.
Financial stakeholders. Ensure that governance policies and processes help increase the return on the
enterprise's investment in SharePoint products and technologies.
IT leaders. Help develop their service offerings and determine how to achieve their IT responsibilities,
such as improving security and maintaining reliability, while still supporting the features that the
business teams require.
Business division leaders. Represent the teams that do the primary enterprise work and drive the
architectural and functional requirements of the implementation of SharePoint Server 2013. They
must work with information architects to determine the enterprise's information architecture and
organizational taxonomy standards. Business leaders must also work with IT leaders to create SLAs
and other support policies.
Information architects or taxonomists. Have extensive experience in planning and designing
information systems and taxonomies. They develop plans that support organizational goals and
define site architecture and navigation based on their analysis of the end users information needs.
Compliance officers. Help ensure that an enterprise meets its regulatory and legal requirements.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Software development leaders. Help determine which customization tools are approved, how to verify
code security, and other code-related best practices.
Information workers. Perform the regular day-to-day working tasks that use SharePoint Server 2013.
Their input to the governance committee helps ensure that the services and information architecture
of SharePoint Server 2013 meet their needs.
Trainers. Provide the instructional expertise. They are responsible for developing a training plan and
conducting all appropriate training and education.
Documenting and Communicating the Governance Plan
Successful governance is an iterative process;
therefore, your governance committee should
conduct regular meetings to perform the
following tasks:
Consider incorporating any new requirements
into the governance plan.
Reevaluate and adjust governance principles
and standards to meet new guidelines or
regulatory requirements.
Resolve conflicts among business divisions for
IT resources.
The committee should update its executive sponsors with regular reports. This will promote accountability
and help enforce compliance across the enterprise.
Document your plan
When you are documenting your governance plan for the first time, you should distribute the research
work among key members of the governance committee. After all of the committees research is
complete, you are ready to perform the following tasks:
Use the vision statement that you established as a foundation for your governance plan to identify
the basic governance principles.
Meet with governance committee members who have the appropriate expertise to draft sections that
address how you want to manage the various aspects of your environment.
Review each major component of your plan with sponsors, stakeholders, and other governance
committee members to ensure that you agree about the major components of the plan: vision, roles
and responsibilities, guiding principles, and key policy decisions.
As you develop your governance plan, think about how users will utilize and internalize its contents. Also,
think about the length of your documentation. These planning documents can easily become lengthy,
and the longer they are, the harder it is for users to absorb them. Try to ensure that your plan is as
succinct as possible because this will make it easier for your users to understand and follow its principles
and standards.
Although you prepare a governance plan before the implementation of your solution, you must not think
of it as being finished at any point. Your governance plan should be a living document. As your
SharePoint environment develops, you should return to your governance plan to adapt to the changing
needs of both the organization and your users.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Communicate your plan
Communicating the body of the governance plan is a central element of planning the implementation
and continuing management of your SharePoint environment. The main audiences for the governance
plan are your key business stakeholders and the end users who create and consume the site content.
However, you should communicate the goals and contents of your governance plan to everyone in the
organization because all users can create some form of content by using SharePoint social computing
features, such as tagging and ratings.
One simple way to communicate the details of your governance plan to everyone in the organization is
through a centralized governance portal off the intranet home page.
On this site, you should include sections on topics such as:
Governance hierarchy
Team roles and responsibilities
Individual roles and responsibilities
Operations policies and procedures
Application usage policies and procedures
How to obtain IT support
Site change requests
User experience feedback
Reference Links: For more information, you can download the SharePoint governance
planning white paper at http://go.microsoft.com/fwlink/?Linkid=303721
Reviewing and Updating the Governance Plan
You must follow a regimented process to create a
successful governance plan. The following steps
provide an example of a process that you can
follow in your organization when you review and
update your governance plan prior to
implementation:
1. Build the governance policies:
a. Explore examples of governance plan
templates and checklists from available
online resources.
b. Use any existing policies as a starting
point.
c. Group the key policy elements of your plan into high-level policy groups such as security, design,
content management, and collaboration.
d. Separate the high-level policy groups into subgroups, which then become your content types.
e. Ensure that you assign metadata to the documents that you add to the subgroups to make them
searchable, such as policy name, policy scope, policy type, review status, and approval data.
2. Hold an initial policy review:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
a. Work closely with the relevant business unit to review the policies.
b. Conduct meetings with each unit to go through each policy and review each one in detail.
During this phase, you might conclude that you must delete, create, or modify some policies.
3. Edit the policies:
a. Make any agreed modifications to the policies after your initial review meetings.
b. Mark each policy as being ready for review by the business unit, and use versioning to maintain
version control of your policy documents.
4. Hold a business unit review:
a. Use policy scope to provide each business unit with a unique view. This way, units will only see
the policies that apply to them.
b. Use online reviews to avoid having to schedule multiple meetings.
c. Ask the business units to review and approve their policies.
5. Make any final modifications and review the policies again:
a. Make further modifications based on the business units online feedback.
b. Mark policies as approved and get ready to publish them.
6. Publish governance information:
a. Create a centralized SharePoint Server 2013 governance site, possibly as part of a central web
support portal. The governance section should contain:
Governance policies grouped by category and made searchable.
Governance training information by user role and topic.
Governance FAQ list.
Governance guidance and best practices.
Considerations for the Governance Plan
There are several things you need to consider
when designing your governance plan, and these
include some common pitfalls and best practices.
Best practices for governance plans
Keep these best practice suggestions in mind
when developing your governance plan:
Use your governance plan to ensure quality
and relevance of content and to ensure that
all users understand their roles and
responsibilities.
Make sure that you have a governance
committee that has a strong supporter in the role of executive sponsor.
Keep your governance model as simple as possible while still maintaining its strength.
Ensure that you do not make the solution more complex than necessary by overdesigning it.
SharePoint may have a great feature, but that does not necessarily mean that you need to deploy it,
or at least not immediately.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Ensure that all users with design or Full Control privileges have internalized your design guiding
principles and that content contributors understand your guiding principles for creating content.
Think about how you will ensure compliance with your governance plan over time, particularly for
highly visible sites. You might want to perform detailed monitoring and reviews of some sites, but
only perform spot-checks on others.
An effective governance plan should not need to restrict every move; it should provide guidance to
users to ensure that the implementation of SharePoint Server 2013 remains effective and dynamic
over time.
Pitfalls of governance plans
You should avoid the following design and implementation pitfalls when developing your governance
plan:
Not defining any policies that control how SharePoint Server 2013 is used throughout the
organization by departments, teams, or users.
Empowering users without providing them with adequate and appropriate training.
Allowing users to manage their own security when they do not have the appropriate knowledge and
experience.
Allowing users to add too many items to a list, causing downgraded server performance.
Not planning for scale and growth.
Not providing SharePoint Server 2013 as the focal point for organizational information and services.
Not testing the backup and recovery processes and the data integrity.
Governing users too much, thereby stifling the dynamic nature of the business and its SharePoint
implementation.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Developing a Plan for Governance
Scenario
The management team at Contoso has requested that you create a governance plan for the new
SharePoint Server 2013 deployment. The management team has supplied you with documentation that
describes their requirements. Your task is to analyze this information and use worksheets to develop a
robust governance plan.
Objectives
Create a governance plan for SharePoint provisioning and customizations.
Lab Setup
Virtual Machine: 20332B-NYC-CLI
o User name: admin
In this lab, you will develop a governance plan for provisioning and customizations in Contoso as part of
your systems documentation.
In the exercise, you will complete the Governance Worksheet, based on the business requirements
information that is supplied to you.
Exercise 1: Creating a Governance Plan
Scenario
You need to create a governance plan for the Contoso, Ltd SharePoint 2013 implementation. Additional
information that your team needs is detailed in the supplied documents. You will use these documents to
produce a planning worksheet to help create your governance plan.
2. Complete the SharePoint 2013 Governance worksheet
Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen,
and then continue.
Log on to the 20332B-NYC-CL machine as admin with the password Pa$$w0rd.
In the E:\Mod13\Starter folder, read the information in the SharePoint 2013 - Contoso
Provisioning and Customization Requirements.docx file.
Task 2: Complete the SharePoint 2013 Governance worksheet
1. In the E:\Mod13\Starter folder, open and complete the worksheet in the SharePoint 2013
Governance Worksheet.xlsx file, based on the information you have reviewed in Task 1.
2. Shut down the NYC-CL1 virtual machine.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Results: A completed Governance worksheet.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 4
Implementing Governance in SharePoint 2013
After planning the areas of your SharePoint 2013 implementation that require governance, the levels of
governance required, and the people that will be involved in governance of your SharePoint environment,
you need to identify how you can use SharePoints features and functionality to aid or assist governance.
Although elements such as permissions should be obvious methods to help control what tasks users can
and cannot perform, elements such as who can approve content, what changes can be made to branding,
and whether solutions or apps can be deployed, must also be governed in the same way.
Lesson Objectives
Identify IT service features that support governance.
Identify information management features that support governance.
Describe how information management policies support governance.
Identify information architecture features that support governance.
Describe the implementation of governance for sandbox solutions.
Describe the implementation of governance for SharePoint apps.
IT Service Features for Implementing Governance
SharePoint includes the following IT service
features that can provide governance of your
SharePoint implementation:
Site templates. Using a site template, you can
encourage consistent branding, site structure,
and layout in the sites that your users create.
You can create customized site templates for
provisioning sites and use them instead of the
templates that are included with SharePoint.
Quotas. A quota dictates a limit on the
amount of storage that a site collection can
use, and prevents users from adding content
when the limit has been reached.
Workflows. Workflows implement business processes for users of a SharePoint site, and are associated
with site items such as documents, forms, or lists.
Features. You can deploy a feature as a part of a site definition or a solution package, and you can
individually activate a feature. You can hide features to prevent site users from manually deactivating
them. You can use a technique called feature stapling to attach a feature to all new instances of sites
that use a given site definition. This enables you to control the features that users of your service can
access.
Self-service site creation. You can enable users to create their own site collections by using the Self-
Service Site Creation feature. A key decision in governing self-service site creation is to determine the
level of service that supports self-service site creation.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Site use confirmation and deletion. You can configure SharePoint to check with site collection
administrators is a site collection is still in use, and if not in use, perform automatic deletion of the site
collection.
SharePoint Designer. You can manage how an organization uses SharePoint Designer at either the
Web application level or the site collection level.
User profiles and My Site policies. You can use user profile policies to control the site content that
users can see and how they can interact with that content. By default, all authenticated users can
create a My Site Web site, and you should use security groups to manage permissions for these sites.
My Site features store and use personally identifiable information, so before you deploy My Site Web
sites, you should either plan how to control the behavior of these features or turn them off
completely to help protect the security of this information.
Reference Links: For more information about planning quotas management, see Plan
quota management (SharePoint Server 2010, at http://go.microsoft.com/fwlink/?LinkID=303722
For more information about workflows, see Getting started with SharePoint Server 2013 workflow
at http://go.microsoft.com/fwlink/?Linkid=303723
For more information about Self-service site creation, see Configuring Self Service Site Creation in
Information Management Features for Implementing Governance
Information management in SharePoint consists of
managing, retrieving, obtaining, and retaining
information. SharePoint includes the following
information management features that an
organization can use to help govern the use of
SharePoint:
Document management. You use document
management to control the life cycle of
documents in your organization. You can use
policies that implement auditing, document
retention, labeling, and barcodes. You can
implement these policies to help your
organization achieve regulatory compliance, such as retaining records for a given time period.
Content approval. You can use content approval to formalize and control the process of making
content available to an audience; for example, by ensuring that content has gone through the correct
legal review and approval process before it is published.
Versioning. You can use versioning to prevent users who have read permissions from viewing drafts of
documents.
Site policies. You can use the site policies feature to control how long sites are kept after creation. This
feature can help control site growth. You can create site policies at a content type hub in order to
publish these policies to other site collections.
Records management. Records management is the process by which an organization determines the
types of information that should be considered records, how to manage records while they are active,
and how long to retain each type of record. SharePoint includes features that can help organizations
to implement integrated records management systems and processes.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Digital asset management. Having a centralized repository for managing your digital assets enables
you to apply firm control over brand-sensitive content, and helps to ensure that only approved assets
are available to the appropriate users.
eDiscovery. You can use an eDiscovery center to track external actions such as litigations,
investigations, or audits that require you to suspend the disposition of documents. If you use
SharePoint to manage any electronic information, you should consider using eDiscovery when you
are developing your SharePoint governance plan.
Reference Links: For more information about content approval and versioning, see Plan
document versioning, content approval, and check-out controls in SharePoint 2013 at
http://go.microsoft.com/fwlink/?LinkID=303725
For more information about records management planning, see Plan records management in
SharePoint Server 2013 at http://go.microsoft.com/fwlink/?LinkID=303726
For more information about planning for eDiscovery, see Plan for eDiscovery in SharePoint Server
Information Management Policies for Implementing Governance
SharePoint includes several information
management policies that an organization can use
to help govern the use of SharePoint content. An
information management policy is a set of rules
for a content type, or for a location where content
is stored. Each rule in a policy is a policy feature.
You can use information management policies to
audit who accesses information, what they do with
it, and how long the information should be
retained for. You can assign a policy to a list,
document library, or content type.
Note: When you configure an information
management policy, it is a recommended best practice to write a policy statement that is
displayed in Microsoft Office client programs to inform document authors about the policies that
are enforced on a document.
SharePoint includes the following information management policies:
Auditing policy. This policy logs events and operations that are performed on documents and list
items. You can configure auditing to log events such as editing documents, viewing them, or
changing a document's permissions level.
Retention policy. This policy helps to dispose of or process content in a consistent way that you can
track and manage. For example, the policy can ensure that a document is retained for a predefined
period of time, send the document to a records center, or define a workflow task to have SharePoint
route the document for permission to destroy it.
Labeling policy. This policy specifies a label to associate with a type of document or list item. Labels
are searchable text areas that SharePoint generates based on metadata properties and formatting
that you specify. Labels can be inserted into an office document.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Barcode policy. This policy enables you to track physical copies of a document. You create a unique
identifier value for a document and then insert a barcode image of that value in the document. By
default, barcodes are compliant with the common Code 39 standard (ANSI/AIM BC1-1995, Code 39),
and you can use the object model of the policies to plug in other barcode providers.
Information management policy reports help you to monitor how consistently your organization uses
policies. If you implement information management policies to help your organization comply with
regulations, you should monitor policy usage frequently to help ensure that your organization is
compliant.
Reference Links: For more general information about planning information management
policies, see Plan for information management policy in SharePoint Server 2013 at
Information Architecture Features for Implementing Governance
SharePoint includes several information
architecture features that an organization can use
to help govern the use of SharePoint. Information
architecture in SharePoint refers to the
organization of enterprise information such as
documents, lists, Web sites, and Web pages. This
organization is designed to take full advantage of
the information's usability and manageability.
You can increase your organizations return on its
portal investment by including information
architecture standards and policies in your
governance plan. A well-governed architecture
makes it easier for your users to find, share, and use your information.
The following information architecture features can provide governance of your SharePoint
implementation:
Content types. You use content types to organize, manage, and handle content in a consistent way.
They define the attributes of a type of list item, document, or folder. Each content type can specify
metadata properties to associate with items of its type, available workflows, templates, and
information management policies. To govern content types, you should consider associating event
receivers and workflows with the forms that are used to modify the content types.
Blocked file types. You can use this feature to restrict files from being uploaded or downloaded to a
server by basing the restriction on the file extension. For example, you can block executable files,
which may contain malicious software, so that users cannot run them on their client computers. By
default, many file types are blocked, and this includes executable files.
Taxonomy and managed metadata. Managed metadata is a hierarchical collection of centrally
managed terms that you can define and then use as attributes for items in SharePoint. Users can see
only global term sets and term sets that are local to the user's site collection. Therefore, if there are
term sets that some users should be unable to view, you should assign these term sets to separate
groups.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
An organizations governance policies can affect how you design managed metadata services and
connections. If every document that is created must have a certain set of attributes, you may want to have
a content type hub in at least one service. You should acquaint yourself with your organizations
governance plan before you determine any managed metadata services and connections.
Reference Links: For more information about content types and workflow planning, see
Plan content types and workflows in SharePoint 2013 at
For a complete list of the default blocked file types, see Manage blocked file types in SharePoint
2013 at http://go.microsoft.com/fwlink/?LinkID=303730
For more information about managed metadata service applications, see Overview of managed
metadata service applications in SharePoint Server 2013 at
Governance of Sandboxed Solutions
A sandbox is a restricted environment that enables
programs to execute code that can access only
specific resources; therefore, issues that occur in
the sandbox do not adversely affect the rest of the
environment. When you deploy a solution in a
sandbox, it is known as a sandboxed solution.
Sandboxed solutions are typically deployed to test
ways in which an organization can improve system
performance and security.
Sandboxed solutions run in an isolated worker
thread, so they cannot use resources that belong
to other solutions. In addition, they have restricted
access to local and network resources, so they cannot gain access to content outside the site collection in
which you have deployed them.
The most common scenarios for using sandboxed solutions include:
Your organization wants to run code on a production SharePoint site, but the code has not been fully
and rigorously tested.
You want to provide hosted environment services and you need to allow the owners of the hosted
SharePoint sites to upload and run custom code.
You want to utilize sandboxed solutions for load-balancing purposes.
Planning governance for sandboxed solutions
When planning governance for your sandboxed solutions, you should consider the following:
When should a farm administrator block or unblock a sandboxed solution? Identifying the
management policy for blocking and unblocking sandboxed solutions will help to reduce confusion if
there is any uncertainty about whether to block a sandboxed solution.
When can you transfer a sandboxed solution to the production environment as a fully trusted solution?
You must define a policy for determining what level of testing is required for a sandboxed solution to
be considered ready for production use in your organization.
Who will you allow to deploy sandboxed solutions? Depending on your organizations security
requirements, you could choose to add people directly to the site collection administrators group.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Alternatively, you could establish a procedure for specifying a restricted number of site collection
administrators to deploy sandboxed solutions on behalf of their users.
Will you dedicate a separate server to running sandboxed solutions? You can increase isolation by
using remote load balancing and by only running the sandboxing service on specific servers.
Note: Only members of the Farm Administrators group can block sandboxed solutions,
configure load balancing, and reset exceeded quotas.
Governance of SharePoint Apps
In the same way that you plan governance for site
customizations and solutions, you should also plan
governance for SharePoint apps.
You should consider the following when planning
governance for SharePoint apps:
Do you plan to deploy or use SharePoint
apps? If you do not plan to use SharePoint
apps, you do not need to configure
connectivity to the SharePoint Store or the
App Catalog, and site owners will not be able
to deploy any apps.
Do you plan to allow site owners to install apps from the SharePoint Store? Should site owners be
able to install any of the apps available in the SharePoint Store or should the SharePoint Store be
restricted?
Do you plan to allow site owners to request apps from the SharePoint Store? If site owners are not
allowed to install apps directly from the SharePoint Store, should they be allowed to request apps
from the SharePoint Store?
Who should be able to add apps to the App Catalog? Who will be allowed to make decisions on what
apps are allowed, who can upload custom apps to the app catalog, and if you are using requests, who
can approve app requests?
Based on the answers to these questions and your planned approach for app governance, you should
configure appropriate access to the SharePoint Store. You can also configure users and permissions for
the App Catalog site for those users who should be able to approve or upload apps.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Managing Site Creation and Deletion
Scenario
Various project teams at Contoso have requested the ability to create their own sites and site collections
for short-term project planning. However, the IT team is concerned that this could lead to a rapid
proliferation in the number of sites and the amount of content on the intranet portal. To mitigate these
concerns, your governance plan includes policies for site quotas and automatic site deletion for use with
self-service site creation. Your next task is to implement these policies on the SharePoint 2013
deployment.
Objectives
Create and publish a site policy.
Enable and manage self-service site creation.
o User Name: administrator@contoso.com
Virtual Machine: 20332B-NYC-DB-13
o User Name: jim@contoso.com
Exercise 1: Creating and Publishing Site Policies
Scenario
In this exercise, you will define a new site policy. You will identify the site collection that is acting as the
content type hub for the instance of the Managed Metadata Service that is provisioned in the server farm,
and then you will enable the site policy feature on that site collection. You will then create a new policy
and publish it for consumption. To ensure your new policy is available to other site collection promptly,
you will manually trigger the timer jobs which propagate content types from the content type hub to the
content type subscribers.
1. Activate the Site Policy feature on the content type hub site collection
2. Create and publish a site policy
Task 1: Activate the Site Policy feature on the content type hub site collection
Pa$$w0rd.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
View the properties of the Contoso MMS service application to identify which site collection acts as
the content type hub for the service. The content type hub should be
http://sharepoint.contoso.com.
In Internet Explorer, in a new tab, navigate to the http://sharepoint.contoso.com site collection.
Verify that the Site Policy site collection feature on the http://sharepoint.contoso.com site
collection is enabled.
Task 2: Create and publish a site policy
Browse to the Site Policies page.
Create a new site policy with the following properties.
Property Setting
Name Short Term Planning
Site closure and deletion
option
Close and delete sites automatically
Closure event Delete 180 days after site creation
Deletion event Delete 60 days after site closure
Warning emails Do not send any warning emails
Deletion postponement Disabled
Closed site state Read only
Publish the Short Term Planning policy.
Note: Content types are propagated by a timer job. To help ensure that the new site policy is
available to other site collections and web applications, you can force the Content Type Hub and Content
Type Subscriber timer jobs. There will be one instance of the Content Type Subscriber timer job for each
subscribing web application in your environment.
Using the SharePoint 2013 Management Shell, run the following commands:
get-SPTimerJob | where {$_.DisplayName -eq "Content Type Hub"} | start-SPTimerJob
get-SPTimerJob | where {$_.DisplayName -eq "Content Type Subscriber"} | start-
SPTimerJob

Results: After completing this exercise, you should have enabled site policies on the content type hub,
created a new site policy, and published that policy for consumption in other site collections.
Exercise 2: Enabling and Managing Self-Service Site Creation
Scenario
In this exercise, you will enable Self-Service Site Creation. You will create a site quota to apply to new sites
created by using the Self-Service Site Creation feature, and then you will enable the feature on the
sharepoint.contoso.com web application.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To ensure that users are able to take advantage of the feature, you will create a new web application
permissions policy that grants the necessary permissions to use Self-Service Site Creation, and then you
will create a user policy to map that permission to a set of users.
You will then configure the Self-Service Site Creation URL for the My Site host web application to enable
users to use Self-Service Site Creation across web applications. Finally, you will test the Self-Service Site
Creation functionality to verify that it is configured correctly.
1. Use the Central Administration website to create a site quota
2. Enable Self-Service Site Creation
3. Test Self-Service Site Creation
Task 1: Use the Central Administration website to create a site quota
On the Central Administration web site, browse to the Application Management page.
Create a new quota with the following properties.
Property Setting
Name Short Term Quota
Maximum site storage 1024MB
Warning email threshold 768MB
Sandboxed code limits 0 points
Task 2: Enable Self-Service Site Creation
On the Central Administration website, browse to the Web Application Management page.
Enable self-service site creation for the SharePoint sharepoint.contoso.com80 web application
with the following properties:
Property Setting
Quota template Short Term Quota
Start a site link Prompt users to create a site collection under any managed path
Site classification Required
Secondary contact required Off

Note: Users create new sites by using the Self-Service Site Creation feature from their My Site. My
Sites are already configured in the lab environment; however, you must configure the Self-Service Site
Creation URL on the My Sites web application to enable users to create sites in the correct web
application.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Ensure Self-Service Site Creation is enabled for the SharePoint mysites.contoso.com80 web
application, and set the Start a Site link to display the custom form at
http://sharepoint.contoso.com/_layouts/15/selfservicecreate.aspx.
Note: The Sites link may not appear immediately. It can take up to five minutes for the Sites link to
appear.
Create a new permission policy for the SharePoint sharepoint.contoso.com80 web application
with the following properties:
Property Setting
Name Self-Service Site Creator
Description Can use the Self-Service Site Creation feature
Granted permissions Use Self-Service Site Creation and View Items
Denied permissions None

Note: The Use Self-Service Site Creation permission is the only permission required to enable
users to create sites. In this lab, you also grant the View Items list permission; this is necessary to enable
the user to view the available site policies when they use the self-service site creation tool. Without the
View Items permissions, users can still create self-service sites; however, they cannot select a policy to
apply to the site.
Create a new user policy with the following properties:
Property Setting
Zone All zones
Users Everyone
Permissions Self-Service Site Creator
Recycle the web application application pools for the mysites.contoso.com and
sharepoint.contoso.com web applications.
Task 3: Test Self-Service Site Creation
Log on to the 20332B-NYC-DB-13 machine as jim@contoso.com with the password Pa$$w0rd.
Open Internet Explorer and navigate to the http://sharepoint.contoso.com site. Logon as
On the SharePoint site, browse to the Sites page.
Note: It can take several minutes for the Sites link to appear.
Create a new site named My Project, which uses the Short Term Planning site policy.
View the site closure and deletion settings for the My Project site, and verify that the site is
scheduled for closure in 180 days.

Results: After completing this exercise, you should have configured Self-Service Site Creation for the
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you learned about the importance of governance to a SharePoint deployment. You also
learned how to go about creating a governance plan for SharePoint, including key statements and
foundations for the governance plan, defining key roles and responsibilities to reflect in the governance
plan, and how important planning training is for users.
You also examined how to assemble a governance plan along with how best to distribute the plan to
those users it affects in order to ensure everyone involved has a clear understanding of how SharePoint
supports day-today working practices.
Review Question(s)
Test Your Knowledge
Question
Which of the following does governance not help with?

Preventing site sprawl
Preventing any users from creating new site collections
Helping ensure structured growth
Helping ensure content quality
Helping ensure standards for navigation structure
Test Your Knowledge
Question
Which solution role holds the primary strategic responsibility to help ensure that the
business gets value from the solution?

Governance committee
Business owner
Executive sponsor
Solution administrator
Site designer

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Test Your Knowledge
Question
Which governance committee members are responsible for defining the architecture
and navigation of sites?

Executive stakeholders
Business division leaders
IT leaders
Information architects
Software development leaders
Test Your Knowledge
Question
Which feature can you use to help control the growth of large numbers of sites within a
site collection?

Self-Service Site Creation
Site use confirmation and deletion
Quota templates
Site policies
Content types

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
14-1
Module 14
Upgrading and Migrating to SharePoint Server 2013
Contents:
Lesson 1: Preparing Upgrade or Migration Environment 14-2
Lesson 2: Performing the Upgrade Process 14-13
Lab A: Performing a Database-Attach Upgrade 14-23
Lesson 3: Managing Site Collection Upgrade 14-28
Lab B: Managing Site Collection Upgrades 14-36

Module Overview
Upgrading your Microsoft SharePoint Server 2010 farm(s) to SharePoint 2013 is a major undertaking, so it
is important that you carefully plan the upgrade activities. You need to ensure that your upgrade path
moving from version to versionis supported, that you have reviewed the business impact of your
upgrade, and that you test your upgrade strategy to ensure business continuity. As with all such activities,
preparation is crucial.
In contrast with earlier version of SharePoint, SharePoint 2013 supports only database-attach upgrades for
content, but it now supports upgrades for some of the databases associated with service applications. You
need to plan for these and ensure that you are prepared for any troubleshooting that may be required.
Another change in SharePoint 2013 is the approach to upgrading site collections. These are upgraded
separately from the data and service applications. You can also delegate the upgrade tasks to site
collection administrators.
Objectives
Describe how to plan and prepare for your upgrade.
Explain the steps involved in data and service application upgrades.
Describe the process for upgrading site collections.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
14-2 Upgrading and Migrating to SharePoint Server 2013
Lesson 1
Preparing Upgrade or Migration Environment
Fail to plan and plan to fail is a well-used axiom. When preparing to upgrade, it is essential that you plan
and prepare thoroughly. SharePoint Products and Technologies provide core business solutions for many
organizations, so you must ensure that you continue to provide a service that meets your service-level
agreement (SLA) standards.
You need to appreciate the overall process and to be sure that your current environment is not only
supported for your target upgrade, but that it is also in good health. If your current farm has issues, you
may well find that your upgrade will have similar problems, if it upgrades at all. You should regard an
upgrade as an opportunity to complete any housekeeping tasks that are necessary to make your
SharePoint Server 2010 deployment work at its optimum level.
With a healthy farm in place, you can prepare the SharePoint 2010 content and then establish your new
SharePoint 2013 environment so that it will deliver the services your business requires.
Lesson Objectives
Describe the upgrade process.
List the planning steps necessary for an upgrade.
List the supported upgrade paths.
Describe good practices in upgrade preparation.
Describe the pre-upgrade tasks that you should complete.
Explain the use of trial upgrade environments.
Describe how to backup you SharePoint 2010 databases.
Describe how to prepare your new SharePoint 2013 environment.
Overview of the Upgrade Process
The upgrade process from SharePoint Server 2010
to SharePoint 2013 has changed from the process
that was available to upgrade from Microsoft
Office SharePoint Server 2007 to SharePoint Server
2010. The changes include:
Elimination of in-place upgrades. You can no
longer perform an in-place upgrade on a
farm. This was supported in SharePoint Server
2010, although it was usually recommended
for small farms or test environments. This
means that only the database-attach method,
where a SharePoint Server 2010 database is
attached to a new SharePoint 2013 farm deployment to migrate the farm data. Database-attach
upgrades provide greater control over the process and minimize upgrade issues that could affect an
entire farm.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Database-attach upgrade for some service application databases. In SharePoint 2013, you can now
upgrade some service application databases by using the database-attach migration. The service
applications that support this process are:
o Business Data Connectivity service
o Managed Metadata Service
o PerformancePoint Services
o Secure Store Service
o User Profile services
o Search administration
Deferred site collection upgrade by site collection administrators. Upgrading site collections can now
be delegated to site collection administrators. This means that a site collection administrator can
upgrade his or her environment when it is appropriate for the business, even if the farm has been
upgraded to SharePoint 2013 by the farm administrator. The site collection upgrade is supported by:
o Notification of upgrade availability to site collection administrators.
o A real SharePoint 2010 environment post farm upgrade and prior to site collection upgrade to
ensure continuity.
o A site collection health checker.
o Evaluation site collections.
o Throttling of the site collection upgrade process to manage upgrade impact.
Log files in Unified Logging System (ULS). Upgrade log files are now readable in ULS to make it easier
to review upgrade logs.
The upgrade process
The upgrade process is split into five stages, with the first four undertaken by a farm administrator and
the fifth performed by a site collection administrator, if required.
1. Create a new SharePoint 2013 farm. Because in-place upgrades are no longer supported, the first job
is to create a new SharePoint 2013 farm. The settings of the new farm should duplicate the
functionality of the existing environment that was identified when planning the upgrade. With a new
farm configured, you should set the SharePoint Server 2010 farm databases to read-only so that you
can create backup copies of the data without further updates occurring. You can perform upgrades
for content databases consecutively and in any order, so you can manage the process one database
at a time, if required.
2. Copy SharePoint 2010 databases to the new farm environment. You can now save the database copies
to the SharePoint 2013 farm and set them to read-write.
3. Upgrade service applications. Configure all required service applications and perform database-attach
upgrades for:
a. Business Data Connectivity service
b. Managed Metadata Service
c. PerformancePoint Services
d. Secure Store Service
e. User Profile service
f. Search administration
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
4. Create web applications to host your content. You should configure host names and DNS settings to
match your SharePoint 2010 environment.
5. Install any server-side customizations required by your content. These customizations can include site
definitions, web services, assemblies, and web.config amendments.
6. Upgrade content databases. Attach the content databases to the new farm and upgrade the content
databases for the web applications you have created.
7. Upgrade site collections. The site collection administrators should receive notification, by email or on
the site home page, that they can begin upgrading to SharePoint 2013.
Planning an Upgrade
Planning an upgrade is more complex than
planning a new deploymentit has all of the
challenges of a fresh deployment and the
additional problems of migrating existing business
environments to the new platform. This means
that in addition to planning to perform all of the
installation tasks, you must also plan a complete
review of your existing environments.
The list of tasks that you should perform when
planning an upgrade includes:
Plan business communications.
Gather business requirements.
Undertake farm surveys.
Execute upgrade tools to gather information about the current environment.
Perform environment cleanup.
Build hardware.
Perform pre-upgrade backups.
Establish a project schedule.
Test the upgrade.
Test rollback and restore options.
Perform post-upgrade activities.
Establish launch and ongoing support management.
Planning business communication
Upgrades may affect users through changes to applications, unavailability of service, or changes to
working practices. You must prepare the users for these events. If you do not, you may find that their
response to the newand hopefully improvedservices may be negative.
This is not solely your responsibility and should be undertaken by the entire project leadership team,
particularly the project sponsor and business stakeholders. These team members are probably closer to
the business than you and should be able to identify key departments and workers who must be engaged
in the project or supported through the changes.
The key elements of your communications planning should include the following:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Announce the upgrade. Do not surprise users with a new deployment, even if everything happens
during business downtime, such as over a weekend. You must prepare users and preferably engage
them in the preparation for the upgrade.
Identify user training requirements. You must ensure that project team stakeholders identify all of the
groups and the changes that may occur to their working environments. You must plan and pre-
deliver any training that is necessary on a test system. This will minimize support desk calls on launch
day. It may also identify potential issues that you can then use as input to your overall upgrade plan.
Identify administration training. You and the upgrade team are almost certainly familiar with
SharePoint 2013, but the site collection administrators and system operators may still be working to
maintain the SharePoint Server 2010 environment. Make sure that these people, who will include
frontline support staff, are fully conversant with both the applications and the administrative
functions that they are likely to use.
Plan launch support. You should plan to have mentors available on launch day to help with any
transition issues. These mentors should be staff from either the IT department or the business, and
they should work with users rather than just offering telephone support. This will reduce support calls
significantly and will engender a team ethic in the company.
Supported Upgrade Paths
As you have seen, the only upgrade option to
SharePoint 2013 is by using the database-attach
method. For organizations that have not upgraded
older versions of SharePoint Products and
Technologies to SharePoint Server 2010, the only
option is to perform a two-step upgrade; first you
upgrade to SharePoint 2010, and then you
upgrade to SharePoint 2013.
The following table shows the supported upgrade
paths for SharePoint 2013 and the paths that are
not supported. It is essential that you follow a
supported path.
Start version
Supported target
version
Unsupported target version
SharePoint Server
2010, Standard
edition
SharePoint Server
2013, Standard
edition
SharePoint Server 2013, Enterprise edition. You
would need to migrate to the Enterprise edition
after the initial upgrade to the Standard Edition.
SharePoint Server
2010, Enterprise
Edition
SharePoint Server
2013, Enterprise
edition
SharePoint Server 2013, Standard edition. You
cannot migrate from Enterprise edition to
Standard edition.
SharePoint Server
2010, Trial edition
SharePoint Server
2013, Trial edition
SharePoint Server 2013, full edition. You can only
convert to the full version after the upgrade.
SharePoint
Foundation 2010
SharePoint
Foundation 2013
or
SharePoint Server
2013

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Start version
Supported target
version
Unsupported target version
Search Server 2010 SharePoint Server
2013 or Search
Server 2013
SharePoint Foundation 2013
Project Server 2010
with SharePoint
Server 2010,
Enterprise Edition
Project Server 2013
with SharePoint
Server 2013,
Enterprise Edition

Recommended Best Practices When Upgrading
There are some obvious best practices that you
should perform whenever you upgrade any
software, and most software products have
additional upgrade recommendations that are
specific to the product. The same is true when
upgrading to SharePoint 2013. The most
important point is to ensure business continuity.
The basics of upgrading are reflected in the
following cycle:
Learn
Ensure that you fully understandand your plan reflectsboth your organizations upgrade
requirements, as well as those of SharePoint 2013. Use the available tools to preempt issues such as
missing dependencies or lack of storage capacity. You should know and evaluate the update options for
your farm or farms. This should include development of a plan for the completion of all of the tasks that
are necessary for a successful upgrade. You must also ensure that your plan reflects business requirements
such as system downtime.
Prepare
Your upgrade plan should reflect what you have learned. It must have an exhaustive breakdown of events
in chronological order, so that the administrators who implement your plan have all of the correct
components in place, including all prerequisites. It should also include information about how to identify
and manage any existing customizations and how to manage individual solutions and items. Always
establish a fallback position for extreme situations. For example, an upgrade failure, such as a hardware or
power problem, may be beyond your control, but you must have a plan for ensuring that your business
users can still work in the morning.
As part of this process, you must ensure that your site conforms to any changes in software boundaries,
software prerequisites, and hardware requirements for SharePoint 2013.
You should ensure that your site collection planning is also thorough. It may be that your site collection
administrators complete the physical upgrading tasks, but you must plan and document what they must
do.
Test
Before you even start testing, make sure that you have a working backup of your farm, such that you can
guarantee business continuity.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
If you are upgrading a business system, you must always pretest your plan. This means that you must first
review the current environment to validate that it is performing as designed. This does not mean that you
undertake development, but that you perform a survey to ensure that you are not upgrading web
applications that are no longer used. An upgrade is a great opportunity to complete housekeeping on
your farm.
If possible, you should build a test environment and test each component of your upgrade. This does, of
course, take time and resources. However, attempting to rebuild a business system after a failed upgrade
will take longer, and it will cause greater problems for your organization. Use copies of production data
and hardware if possible, but you can sample data and virtual machines to do worthwhile upgrade
testing. All testing errors must be resolved before you upgrade the production environment.
Implement
After you complete your tests and are satisfied with your mitigation plan, you should schedule the
upgrade. Although you should have documented how much time the upgrade will take through your test
runs, you should still monitor the progress of your upgrade by viewing the status indicators. This will help
you to assess any time differences between your tests and the upgrade exercises.
Validate
Always validate an upgrade by reviewing logs and testing applications. After a long upgrade, it can be
easy to ignore apparently minor errors, but you must check everything thoroughly. As part of your
upgrade, you should have experienced users who can test the validity of data to reveal any potential
issues. You should also test for user experience (UX) in addition to UI changes. Note that the UX concerns
the overall familiarity of your applications, and not just the visual changes in the UI. Your user acceptance
testing must ensure that users are happy with any changes to working practices enforced by the upgrade.
You must be sure that site collection administrators also complete site collection validation checks.
Completing the Pre-Upgrade Steps
When you start to prepare for your upgrade, there
are three key steps that you should complete:
Create a farm inventory.
Clean up your environment.
Test the upgrade process.
This topic examines the first two steps in this
process. Testing the upgrade is covered in the next
topic.
Create a farm inventory
Documentation is an integral part of any system,
especially when upgrading the environment. Organizations often maintain a good record of physical
infrastructure, but many are less thorough when it comes to managing their software customization
updates. The problem here is often caused by the dislocation between the IT professional and developer
management structures. The IT professionals manage the hardware and application software platforms,
whereas the developers manage software development changes. The confusion that can occur is not due
to any failing in the individual management procedures, but rather in the inability to take a holistic view
of the business solutions.
The upgrading of application platforms, such as SharePoint Products and Technologies, often falls to the
IT Professional. This is especially true in an environment where new or alternative hardware platforms are
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
to be used, as is often the case for a database-attach upgrade. It is essential that you not only have an
inventory of hardware and server software, such as service applications, web applications, site collections,
and so forth, but also the programmatic configuration, additions, and add-ins that have been developed
for your SharePoint Server 2010 deployment.
You need to work with development teams to identify and evaluate the continued requirements and
dependencies for:
Master pages
Themes
Webpages
Web Parts
Custom JavaScript
Custom CSS files
Customized (unghosted) pages
Content types
List types
Web templates
Site definitions
Solution packages
Web services
Windows services
HTTP handlers
HTTP module.
Although not all of these components may cause an upgrade to fail, they can have an adverse effect on
the user experience and the functionality of the upgraded farm.
SharePoint administrators and developers also need to work with the business stakeholders to establish
that customizations are still required. This is part of the inventory development process, but also enables
you to develop a clean-up strategy. For individual customizations you may, together, decide:
A customization is essential and will mean that the site should continue to function in SharePoint
Server 2010 mode.
To redevelop the customization prior to the upgrade.
Do away with the customization, because it is no longer used or has been superseded by a new
feature.
Note: You can use the Upgrade Planning worksheet to record information and settings
about your SharePoint 2010 Products environment. You can download this from
Clean up your environment
As a result of your inventory development or verification exercise, you can undertake some housekeeping
on your farm. Irrespective of how well you manage your SharePoint Server 2010 environment, there will
inevitably be elements that you can discard when it is time to upgrade.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Areas that you should particularly review include:
Unused or unnecessary site collections and sites. This is a general housekeeping function, but it does
give you a chance to check that sites are still in use,
Wide lists (with too many fields). These can cause upgrades to fail, so should be checked with Test-
SPContentDatabase.
Database management. Take this opportunity to ensure that your content databases comply with
software boundaries and performance recommendations.
Unnecessary versions. Review the volume of content that is made up of old versions. Verify whether
these are really required, but be mindful of the need for compliance.
Unused features, templates, and Web Parts. Use the Stsadm -o EnumAllWebs command with the -
includefeatures and -includewebparts operators to identify feature and Web Part customizations in
your farm.
Deprecated features. Review your farm for use of deprecated features, such as FAST for SharePoint
2010 or the Office Web Apps service application.
Testing Your Upgrade in a Trial Environment
For any major infrastructure upgrade involving
your hardware or software platform, you need to
plan and test the upgrade before you run it in
your production environment. There are potential
problems with trialing a complete test, but the
most common two are lack of time and lack of
equipment. With SharePoint 2013, which now only
supports database-attach upgrades, lack of time
should not be a problem. And unless you plan to
take your entire farm configuration off line,
upgrade the SharePoint software, and upgrade
from backups, you will have to work with at least
some new hardware.
You should plan to include trial upgrades so that you can:
Test and improve your upgrade plan.
Test your customizations.
Test your hardware.
Establish a realistic timeline for the final upgrade.
Test procedures for site collection administrators.
Become familiar with the tools and scripts that you need to use.
You can also undertake user acceptance testing, so that your users have time to give feedback on changes
to the user experience and to ensure that business solutions work as required. Part of the user acceptance
testing will be to establish any security issues, such as changes to authentication and permissions.
A test environment should be as identical as is practically possible to the new production environment,
using the same URLs, external data sources, copies of the real content databases, and real database
names. There will be limitations in this if you have to use the production DNS and Active Directory servers.
You must ensure that your testing does not affect the production environment.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Your testing should involve a thorough review of the upgrade log file and the upgrade error log file,
which are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\15\LOGS.
When you find errors or issues, you must retest to ensure that these problems are addressed.
If you intend to have site collections upgraded by your site collection administrators, you must get them
to test the procedures that you prepare for them. Do not assume that because you can make a script
work, that they will also be able to do so.
Backing Up Your SharePoint 2010 Databases
When preparing your SharePoint Server 2010
environment for your upgrade, a key task is to set
the SharePoint databases to read-only. This allows
you to continue providing data read elements of
your business services, while you prepare to make
backups of your SharePoint data. You do not need
to make backups of the configuration or admin
content databases because new versions of these
databases will be created when you install the new
SharePoint 2013 farm.
For service applications, you should make backups
of the following databases:
Managed Metadata
PerformancePoint
Secure Store
User Profile
o Profile database
o Social database
o Sync database
Note: To back up the Search Administration database, you will need to stop the Search
service.
The backup timetable should reflect your experiences in everyday backup processes. You should ensure
that your backup time is factored into your overall upgrade plan.
Backing up SharePoint 2010 databases
You can back up the content and service application databases by using SQL Server tools. When do this,
you will need to be logged in as a member of the db_owner fixed database role for the databases. You
should perform the following steps to create backups of your SharePoint 2010 databases:
1. Make sure that you have an inventory of database names and sufficient disk or offline storage space
to complete your backups.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
2. In SQL Server Management Studio, in Object Explorer, connect to an instance of the Database Engine,
expand the server, and then expand Databases.
3. Right-click the database that you want to back up, point to Tasks, and then click Back Up.
4. In the Back Up Database dialog box, in the Source area, in the Database box, verify the database
name.
5. In the Backup type box, select Full.
6. Under Backup component, select Database.
7. In the Backup set area, in the Name box, either accept the backup set name or type another name
for the backup set.
8. In the Destination area, specify the type of backup destination by selecting Disk or Tape, and then
specify a destination, or create a new destination by clicking Add.
9. Click OK.
You should repeat these steps for the databases that you need to back up.
Preparing for the SharePoint 2013 Environment
After you successfully complete the preparatory
steps for your upgrade, you are ready to deploy
your SharePoint 2013 farm. This will be the target
and new production environment for your
organization.
Configuration settings
As part of your pre-upgrade planning, you should
already have assessed the hardware requirements
for SharePoint 2013. You should also review your
logical and physical architecture designs. It may be
tempting to skip these activities, assuming that
you will just replace the current environment with
new levels of platform software. If you follow this path, you may miss an opportunity to implement new
functionality and architectures. As part of your deployment planning for the SharePoint 2013 farm, you
should review current practices and configuration to assess options for improvement.
Your inventory management exercise focuses primarily on your organizations business content and
customizations. In preparation for creating your new site, you should review the configuration settings for
your farm so that you can match or update these options. You should compile a list of configuration
settings for options such as:
Alternate access mappings
Authentication providers and authentication modes that are being used
Quota templates
Managed paths
Self-service site management settings
Incoming and outgoing email settings
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Security preparation
For SharePoint security components, you may need to ensure that you have the SharePoint 2010 security
files, such as the Secure Store service application pass phrase and the User Profile service application
encryption key.
If you have misplaced your Secure Store service application pass phrase, you can use the Windows
PowerShell cmdlet Set-SPPassPhrase to reset it.
For User Profile services, you must export the Microsoft Identity Integration Server Key (MIIS) encryption
key from your SharePoint Server 2010 farm and import it to the SharePoint Server 2013 farm after you
have upgraded the User Profile service application databases.
Additional Reading: For information about exporting the key, see Create the SharePoint
2013 farm for a database attach upgrade at http://go.microsoft.com/fwlink/?Linkid=303734
Installation
With this information and the security components extracted from your SharePoint Server 2010 farm, you
are now ready to install your new SharePoint 2013 farm. You will also need to configure the required
service applications. Several service application databases can be upgraded, which is covered in detail in
the next lesson.
You will also need to configure farm settings for functions such as:
Incoming and outgoing email settings
All farm-level security and permission settings
Blocked file types
Usage and health data collection
Diagnostic logging
Settings and schedules for timer jobs
Discussion: Preparation for Upgrading
Upgrades happen in all organizations and are
often anticipated with some trepidation. However,
all IT professionals have to upgrade platform or
client software at some point in their careers. In
this discussion, share your experiences with
upgrading in your organization.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 2
Performing the Upgrade Process
You are ready to perform your farm upgrade after you complete your preparation tasks. You will need to
restore the content and service application databases and complete the post-upgrade steps. Although it is
every administrators goal to have an uneventful upgrade, you need to be prepared should any issues
arise during the process.
In this lesson, you will see how to perform the database-attach processes. You will also learn how to track
and interpret problems and common issues.
Lesson Objectives
Describe how to upgrade content databases.
Describe how to upgrade service application databases.
Describe how to upgrade from classic-mode to claims-mode authentication.
List the post-upgrade procedures you should perform.
Describe how to troubleshoot common issues.
Upgrading Content Databases
With a new farm configured to fulfill your business
requirements and backup copies in place of your
content and service databases, you are ready to
upgrade the content databases to your SharePoint
2013 farm. To perform this task, you need to be a
member of the db_owner fixed database role for
the content databases and a member of the Farm
administrators security group to create the
necessary web applications.
Creating web applications
You will need to create web applications to match
those that existed on your cleaned SharePoint
Server 2010 farm. You will need to ensure that these applications use the URL that was used to configure
Alternate Access Mappings (AAMs), if you need to do so. AAMs are deprecated but still supported in
SharePoint 2013, to ensure backward compatibility.
If your organization continues to use Windows classic authentication, you will need to use Windows
PowerShell to create the web applications, because claims-based authentication is now the default
authentication mode. You can alternatively migrate to claims-based authentication, which is covered later
in this lesson. As part of your web application configuration, you should match the SharePoint Server 2010
settings, including:
Paths
Host headers
DNS configuration
Quotas
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Email settings
Self-service site creation
Managed path for the My Sites on the My Sites web application
Policies
When you create a web application, a content database is created for the web application by default. You
can delete the default databases when you attach the SharePoint 2010 database.
Customizations
You must ensure that you reapply the customizations that you identified during the inventory
development process, such as site definitions, Web Parts, web services, features, solutions, and web.config
modifications.
If you decide to maintain some sites running in SharePoint 2010 mode, you must ensure that
customizations are provisioned in both the SharePoint 2013 and SharePoint 2010 directory structures.
These are installed by default at:
Web Server Extensions/14/TEMPLATE/Features
Web Server Extensions/15/TEMPLATE/Features
To have customizations available for both SharePoint 2010 and SharePoint 2013 modes, you must install
them in both structures.
Verifying customizations
You can verify that you have the custom components required for a content database by running the
Test-SPContentDatabase Windows PowerShell cmdlet. To run this command, open the Windows
PowerShell command prompt and type:
Test-SPContentDatabase -Name DatabaseName -WebApplication URL
Where DatabaseName is the name of the database you are testing and URL is the URL of the web
application.
Attaching a database
To attach a database to a web application in your new environment, you must use the Windows
PowerShell cmdlet Mount-SPContentDatabase; the Central Administration interface does not provide an
attach option. Running this cmdlet attaches the database to the web application, but it does not upgrade
site collections, which is now a separate task. For a web application that spans multiple databases, you
must first attach the content database that contains the root site collection. After this is complete, you can
then attach the web applications remaining content databases in any order. With the attach procedure
completed, you then upgrade site collections or create new site collections, if you require them. If you
have a My Sites site collection, you must attach the content database that contains the My Site host
before attaching databases that contain the My Sites.
The Mount-SPContentDatabase cmdlet uses the following syntax:
Mount-SPContentDatabase -Name DatabaseName -DatabaseServer ServerName -WebApplication
URL
The parameters are as follows:
DatabaseName is the name of the database that you want to upgrade.
ServerName is server on which the database is stored.
URL is the URL for the web application that will host the sites.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Upgrading Service Applications
Only six service applications can be upgraded.
These include:
Business Data Connectivity service
Managed Metadata Web Service
PerformancePoint Services service
Secure Store Service
User Profile service
Search service
When you upgrade service applications, you
create a new SharePoint 2013 service application and provide the name of the backup copy of the service
application for SharePoint to use. The process of creating a service application automatically upgrades the
database. To perform upgrades, you must be logged on with an account that has the following
memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all relevant databases.
Administrators group on the server running the Windows PowerShell cmdlets. This is required if you
wish to upgrade any of the services with Windows PowerShell and must be used to upgrade the
Search service.
The steps involved in the procedure are as follows:
1. Start the service instances. You can start most of the service instances from Central Administration or
by using Windows PowerShell. For Search, you must use Windows PowerShell. You can start the
service application instances from Central Administration, on the Application Management page, in
the Service Applications section, by clicking Manage Services on Server. Beside each of the
services you then click Start. To start the Search service with Windows PowerShell, run the following
cmdlet:
Start-SPServiceInstance Identity
Where Identity is the GUID of the Search instance. You can retrieve this with the Get-
SPEnterpriseSearchServiceInstance cmdlet.
2. Create the service applications and upgrade the databases. You can create the service application and
restore the associated databases by using Windows PowerShell.
3. Create proxies for the service applications. After the databases are upgraded, you have to create
service application proxies and add them to the default group. You have to create proxies for all of
the upgradable services except the Business Data Connectivity service application, which
automatically creates a proxy and adds it to the default group.
4. Verify that the proxies are in the default group. You can do this by running the Windows PowerShell
cmdlet Get-SPServiceApplicationProxyGroup for the default proxy group.
Upgrading with Windows PowerShell
To upgrade each of the six service applications, you must run the appropriate Windows PowerShell cmdlet
to create the required service application and specify the backup copy of the service application database
copied from your SharePoint Server 2010 farm.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
The cmdlets that you will need for each service application are listed in the following table. Depending on
your approach to PowerShell scripting, you can use variables to help streamline the process. There are
additional parameters that you can set for these cmdlets.
Note: The names used in this table are examples only; they are not recommended as real
service application or database names.
Service
Application
Cmdlet or command Function
Secure Store
service
New-SPSecureStoreServiceApplication -Name
SecureStore' -ApplicationPool
SecureStoreAppPool -DatabaseName
'BackupSSSDB
Creates a new Secure
Store Service called
SecureStore with an
application pool called
SecureStoreAppPool and
attaches the database
BackupSSSDB.
New-SPSecureStoreServiceApplicationProxy
-Name SSSProxy -ServiceApplication
SecureStore -DefaultProxyGroup
Creates a new proxy for
the Secure Store service
(SecureStore) called
SSSProxy and adds it to
the default group.
Update-SPSecureStoreApplicationServerKey
-Passphrase <SSSPassphrase> -
ServiceApplicationProxy SSSProxy
Updates the pass phrase
(SSSPassphrase) for the
proxy (SSSProxy).
Business Data
Connectivity
service
New-
SPBusinessDataCatalogServiceApplication -
Name 'BDCService' -ApplicationPool
BDCAppPool -DatabaseName ' BackupBDCDB
'
Creates a new Business
Data Connectivity service
called BDCService with
an application pool
called BDCAppPool and
BackupBDCDB.
Managed
Metadata Service
New-SPMetadataServiceApplication -Name
'MMServiceApp' -ApplicationPool
MMSAppPool -DatabaseName 'BackupMMSDB'
Creates a new Managed
Metadata Service called
MMServiceApp with an
MMSAppPool and
BackupMMSDB.
New-SPMetadataServiceApplicationProxy -
Name MMSProxy -ServiceApplication
MMServiceApp -DefaultProxyGroup
the Managed Metadata
Service (MMServiceApp)
called MMSProxy and
adds it to the default
group.
User Profile
service
New-SPProfileServiceApplication -Name
'UPService' -ApplicationPool UPSAppPool
-ProfileDBName 'UPSA_ProfileDB' -
SocialDBName 'UPSA_SocialDB' -
Creates a new User
Profile service called
UPServiceApp with an
UPSAppPool and
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Service
Application
ProfileSyncDBName 'UPSA_SyncDB' attaches the three
databases for profiles,
social and
synchronization:
UPSA_ProfileDB
UPSA_SocialDB
UPSA_SyncDB

New-SPProfileServiceApplicationProxy -
Name UPSProxy -ServiceApplication
UPService -DefaultProxyGroup
the User Profile service
(UPService) called
UPSProxy and adds it to
the default group. Note
that you will have to start
the User Profile
Synchronization service.
At a command line, navigate to %Program
Files%\Microsoft Office
Servers\15.0\Synchronization Service\Bin\ and run
the command:
miiskmu.exe /i {Path and file name for
the key that you want to import}
This command imports
the encryption key for
User Profile service
application.
PerformancePoint
Services service
New-SPPerformancePointServiceApplication
-Name 'PPSServiceApp' -ApplicationPool
PPSAppPool -DatabaseName 'BackupPPSDB'
Creates a new
PerformancePoint
Services service called
PPSServiceApp with an
PPSAppPool and
BackupPPSDB.
New-
SPPerformancePointServiceApplicationProxy
-Name PPSProxy -ServiceApplication
PPSServiceApp -Default
the PerformancePoint
Services service
(PPSServiceApp) called
PPSProxy and adds it to
the default group.
Search service
Restore-
SPEnterpriseSearchServiceApplication -
Name 'SearchSApp' -applicationpool
SearchSAppPool -databasename
'BackupSearchSDB' -databaseserver
<ServerName> -AdminSearchServiceInstance
SearchSInstance
This cmdlet restores the
Search service
application (SearchSApp)
with the application pool
SearchSAppPool and
database
BackupSearchSDB to a
server <serverName>
and a Search
administration instance
SearchSInstance.
New-
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Service
Application
SPEnterpriseSearchServiceApplicationProxy
-Name SearchSProxy -SearchApplication
SearchSApp
the Search service
(SearchSService) called
SearchSProxy.
Add-SPServiceApplicationProxyGroupMember
member SearchSProxy -identity
<IDParameter>"
Adds Search service
proxy (SearchSProxy) to
the default group.
Search
When you upgrade Search, you only upgrade the Search service Administration database, not all of the
other databases associated with search, such as the index and the Link database. These are only recreated
when you run a full crawl. Therefore, after you upgrade your Search service, you must run a full crawl of
the SharePoint 2013 farm. The upgrade does not upgrade the logical components of the Search topology.
You must manually recreate the Search topology on the SharePoint 2013 farm. The upgrade option is
primarily to preserve the setting in the administration database.
Additional Reading: For more information about managing your Search topology, see
Change the default search topology in SharePoint Server 2013 at
Migrating from Classic Mode to Claims Mode Authentication
SharePoint Server 2013 uses claims-based
authentication as its default authentication model,
and it is an essential component to enable the
advanced functionality of SharePoint 2013. Using
claims-based authentication has several
advantages over using Windows classic-mode
authentication:
App authentication and server-to-server
authentication rely on claims-based
authentication. If you use Windows classic-
mode authentication, you will be unable to
use external SharePoint apps. You will also be
unable to use any services that rely on a trust relationship between SharePoint and other server
platforms, such as Office Web Apps Server 2013, Exchange Server 2013, and Lync Server 2013.
SharePoint can delegate claims identities to back-end services, regardless of the sign-in method. For
example, suppose your users are authenticated by NTLM authentication. NTLM suffers from a well-
known "double-hop" limitation, which means that a service such as SharePoint cannot impersonate
the user to access other resources on behalf of the user, such as SQL Server databases or web services.
By contrast, when you use claims-mode authentication, SharePoint can use the claims-based identity
token to access resources on behalf of the user.
When you create a web application in claims-based authentication mode, you can associate multiple
authentication providers with the web application. For example, you can support Windows-based
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
sign in and forms-based sign in without creating additional Microsoft Internet Information Services
(IIS) websites and extending your web application to additional zones.
Claims-based authentication is based on well-known open web standards and is supported by a
broad range of platforms and services.
There are several supported scenarios for migrating or converting from classic mode to claims mode
authentication, supported by a number of Windows PowerShell cmdlets.
Convert web application on SharePoint Server 2010 and then upgrade
This is a two-step process that first converts the web application to claims-based authentication on
SharePoint Server 2010 and then upgrades to SharePoint Server 2013. To complete the first step, you
must use the following Windows PowerShell scripts and commands on the SharePoint 2010 server.
1. Set an account as the administrator for the site.
$WebAppName = "http://<WebAppUrl>"
$wa = get-SPWebApplication $WebAppName
$wa.UseClaimsAuthentication = $true
$wa.Update()
2. Configure the policy to provide the user with full access.
$account = "<Domain\UserName>"
$account = (New-SPClaimsPrincipal -identity $account -identitytype
1).ToEncodedString()
$wa = get-SPWebApplication $WebAppName
$zp = $wa.ZonePolicies("Default")
$p = $zp.Add($account,"PSPolicy")
$fc=$wa.PolicyRoles.GetSpecialRole("FullControl")
$p.PolicyRoleBindings.Add($fc)
$wa.Update()
3. Perform the migration.
$wa.MigrateUsers($true)
4. After the migration, provision claims.
$wa.ProvisionGlobally()
To migrate to SharePoint Server 2013, you must first create an equivalent claims-based web application
on the SharePoint Server 2013 environment and then use database-attach to attach the converted
database to the SharePoint Server 2013 web application.
Convert SharePoint Server 2010 classic-mode web applications to SharePoint Server
2013 claims-mode web applications
You can take a SharePoint Server 2010 classic-mode web application and convert it to a SharePoint 2013
claims-based authentication, by using the Convert-SPWebApplication cmdlet. This procedure creates a
classic-mode web application and then converts it to claims-mode. The process is as follows:
1. Create a new web application that uses classic-mode authentication on the SharePoint Server 2013
environment.
New-SPWebApplication name "<NewWebApp>" Port 100 ApplicationPool
"<NewWebAppPool>" ApplicationPoolAccount (Get-SPManagedAccount
"<Domain\UserName>")
2. Attach the content database from the SharePoint Server 2010 farm.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
3. Convert the web application to claims-mode.
Convert-SPWebApplication Identity <NewWebAppUrl> To Claims
-RetainPermissions [ -Force]
Verifying database upgrades
When a service applications upgrade cmdlet
finishes running, you can view the upgrade status
in Central Administration. To do this, in Central
Administration, click Upgrade and Migration,
and then click Check upgrade status.
You should verify the first content database that
you upgrade, to ensure that you have run the
procedure correctly. If issues arise during the
upgrade, you can review the upgrade log to
identify the problems. If the procedure runs
correctly, you can upgrade the remaining
databases by executing further instances of the
Mount-SPContentDatabase cmdlet. These can be run concurrently, but you should stagger the
commands to avoid locks and contention issues. You must verify each database when the cmdlet
completes.
To view the upgrade status of all farm databases, you can use the following Windows PowerShell cmdlet:
Get-SPContentDatabase | ft Name, NeedsUpgradeIncludeChildren
This will produce a tabular list of content databases on the SharePoint 2013 farm and identify whether
they need to be upgraded.
If you identify an issue, you will need to resolve the problem, and then restart the upgrade. When this is
done, you can restart a database upgrade by using the following Windows PowerShell cmdlet:
Upgrade-SPContentDatabase <DBName>
Here DBName is the name of the database
Alternatively, you can specify the database GUID by using the id parameter.
After the upgrade completes, you must verify the database again.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Troubleshooting Upgrade Issues
If you have a problem with your upgrade, the first
place to look when troubleshooting the issues is in
the upgrade logs. When you locate errors or
warnings, you must resolve these and retry the
upgrade.
Error logs
SharePoint 2013 provides two upgrade logs that
you should review, even if it appears that
everything has upgraded correctly:
Upgrade error log file. This is named Upgrade-
YYYYMMDD-HHMMSS-SSS-error.log. It is a
smaller file that lists only the errors that occurred. This is often the best place to start when
troubleshooting, simply because it goes straight to errors. You may need to view the other log file to
gain greater understanding of the context of any errors that are registered here.
Upgrade log file. This is named Upgrade-YYYYMMDD-HHMMSS-SSS.log and lists all of the events
that occurred during the upgrade.
You can find these two files at %COMMONPROGRAMFILES%\Microsoft Shared\Web server
extensions\15\LOGS. They are compiled in Unified Logging System (ULS) format.
You should also review any notifications or errors that are recorded in the Windows Server 2012 Event
Viewer.
Beyond the upgrade logs
You should ensure that all databases have upgraded successfully by reviewing their upgrade status.
Although this is a step in the post upgrade process, it is not uncommon for administrators to forget this
step in the excitement of an apparently successful upgrade.
Failure to manage customizations is a common reason for upgrade problems. You must check your
inventory of customizations to ensure that they have all been accounted for. It is particularly common for
some features or Web Parts to surface after the upgrade. If you are providing support for both SharePoint
2013 and SharePoint 2010 modes of operation, you must check that you have updated the files in both
directory structures. You may also find that web.config files have not been updated on all the servers to
which changes apply.
If there are no problems with your customizations, you should next look at configuration issues for the
server farm, web application, and service applications. Make sure that all features are correctly configured,
such as incoming and outgoing email, and that all the services have started correctly.
Additional Reading: For information about common upgrade questions and issues, see
Troubleshoot database upgrade issues in SharePoint 2013 at
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Discussion: Upgrading
Undertaking an upgrade is a crucial activity for
your organization. Share your experiences of the
activities you associate with the upgrade process.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab A: Performing a Database-Attach Upgrade
Scenario
The Finance team at Contoso is currently using a SharePoint 2010 environment to host various intranet
sites. As part of a broader infrastructure consolidation, Contoso wants to migrate these sites into the new
SharePoint 2013 deployment. Your task is to perform a proof-of-concept migration by using backed up
SharePoint 2010 service application databases and content databases from the Finance team.
Objectives
Restore database backups.
Upgrade service applications from SharePoint 2010 to SharePoint 2013.
Upgrade content databases from SharePoint 2010 to SharePoint 2013.
Virtual machines: 20332B-NYC-DC-14, 20332B-NYC-DB-14, 20332B-NYC-SP-14
Password: Pa$$w0rd
Exercise 1: Import the SharePoint 2010 Databases
Scenario
In this exercise, you will restore the SharePoint 2010 database backups to the database server in your
SharePoint 2013 server farm.
1. Restore the Managed Metadata Service database
2. Restore the Finance content database
3. Make the databases writeable
Task 1: Restore the Managed Metadata Service database
screen, and then wait a further five minutes before proceeding to the next step.
Log on to the 20332B-NYC-DB-14 virtual machine as Contoso\Administrator with the password
Pa$$w0rd.
Use SQL Server Management Studio to restore the ContosoMMS database from the backup file at
E:\Mod14\ContosoMMS.bak.
Task 2: Restore the Finance content database
Use SQL Server Management Studio to restore the WSS_FinanceContentDB database from the
backup file at E:\Mod14\WSS_FinanceContentDB.bak.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Make the databases writeable
Make the ContosoMMS database writeable.
Make the WSS_FinanceContentDB database writeable.

Results: After completing this exercise, you should have restored a service application database and a
content database from backup files.
Exercise 2: Migrating and Upgrading a Service Application
Scenario
In this exercise, you will upgrade the Managed Metadata Service application from the Finance team's
SharePoint 2010 environment. To do this, you will use Windows PowerShell to create a new Managed
Metadata Service application that uses the database that you restored in the previous exercise. As part of
the service application provisioning process, SharePoint will upgrade the service application database to
SharePoint 2013.
1. Start the Managed Metadata Web Service
2. Register a new managed account
3. Create the Managed Metadata Service application
4. Verify that the service application database was upgraded successfully
Task 1: Start the Managed Metadata Web Service
Pa$$w0rd.
Start the Managed Metadata Web Service service.
Task 2: Register a new managed account
Register a new SharePoint managed account for the following credentials:
o User name: CONTOSO\ContosoMMS
Note: The CONTOSO\ContosoMMS domain user account has already been created in
Active Directory.
Task 3: Create the Managed Metadata Service application
Use Windows PowerShell to create a new application pool named ContosoFinanceMMS. The
application pool should run using the CONTOSO\ContosoMMS identity that you registered in the
previous task.
Create a new Managed Metadata Service application with the following properties:
o Name: Contoso Finance Managed Metadata
o Application pool: ContosoFinanceMMS
o Database: ContosoMMS
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Create a service application proxy for the service application you just created. Ensure the proxy is
added to the default proxy group.
Task 4: Verify that the service application database was upgraded successfully
On the Central Administration website, locate the term store for the Contoso Finance Managed
Metadata service application.
Verify that the term store includes a term set group named Organization.
Verify that the Organization group includes term sets named Department and Supplier.
Verify that the Department term set contains the following terms:
o Finance
o IT
o Marketing
o Sales
Verify that the Supplier term set contains the following terms:
o Litware, Inc.
o Northwind Traders
o Proseware, Inc.
o Trey Research

Results: After completing this exercise, you should have migrated a Managed Metadata Service
application from a SharePoint 2010 environment and upgraded it to SharePoint 2013.
Exercise 3: Migrating and Upgrading a Content Database
Scenario
In this exercise, you will upgrade a SharePoint 2010 content database and attach it to a SharePoint 2013
web application. To ensure a consistent user experience, the host name and port of the new web
application must match the host name and port of the SharePoint 2010 web application. To facilitate this
requirement, you will create a web application with the host name finance.contoso.com, and you will
add an associated record in DNS. You will then use Windows PowerShell to attach the migrated content
database to the web application. As part of this process, SharePoint will upgrade the content database to
SharePoint 2013.
1. Add a DNS record for finance.contoso.com
2. Create a new managed account
3. Create a web application to host the content database
4. Attach the content database to the web application
5. Verify that the migrated site collection is fully functional
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 1: Add a DNS record for finance.contoso.com
Log on to the 20332B-NYC-DC-14 virtual machine as Contoso\Administrator with the password
Pa$$w0rd.
Using DNS Manager, in the Contoso.com forward lookup zone, add a new host record that maps the
hostname finance.contoso.com to the IP address 172.16.1.21.
Task 2: Create a new managed account
Switch back to the 20332B-NYC-SP-14 virtual machine. If you are not already logged on, log on as
Register a new SharePoint managed account for the following credentials:
o User name: CONTOSO\SPFinanceAppPool
Note: The CONTOSO\SPFinanceAppPool domain user account has already been created
in Active Directory.
Task 3: Create a web application to host the content database
Create a new web application with the following configuration:
o Set the port number to 80.
o Set the host header to finance.contoso.com.
Create a new application pool that runs by using the CONTOSO\SPFinanceAppPool identity you
registered in the previous task.
Name the content database WSS_FinanceContentDB_New.
Task 4: Attach the content database to the web application
Use Windows PowerShell to mount the WSS_FinanceContentDB in the finance.contoso.com web
application.
Task 5: Verify that the migrated site collection is fully functional
In Internet Explorer, browse to finance.contoso.com. If you are prompted for credentials, log on as
On the Start screen, type Internet Explorer, and then press Enter.
In the Internet Explorer address bar, type finance.contoso.com.
At the credential prompt, log on as CONTOSO\Administrator with the password Pa$$w0rd.
Verify that the site collection loads successfully.
Note: Notice that the site collection is still in SharePoint 2010 mode. You will perform a site
collection upgrade in the next lab.
Open the ContosoP1AnnualReport from the Shared Documents library. If you are prompted for
credentials, log on as CONTOSO\Administrator with the password Pa$$w0rd.
Verify that the document opens successfully.
Browse to the Invoices library, and edit the properties of one of the documents.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Verify that the Contoso Department column allows you to choose values from the Department term
set.
Note: By editing the properties of an invoice, you have verified that:
Site columns have migrated successfully to the new environment.
Content types have migrated successfully to the new environment.
Managed metadata site columns are able to retrieve values from the restored Managed Metadata
Service application.

Results: After completing this exercise, you should have migrated a content database from a SharePoint
2010 environment and upgraded it to SharePoint 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lesson 3
Managing Site Collection Upgrade
If you delegate some of your SharePoint 2013 site collection upgrades to your site collection
administrators, it is essential that you prepare and plan your upgrades thoroughly, as you would for any
other component upgrade, and also that you prepare your site administrators for their tasks. You must
ensure that they understand the preparation, process, and potential troubleshooting tasks that they
should undertake to complete any upgrades. You must also ensure that you retain overall control of the
upgrade process, so that the actions of individual site collection administrators do not affect the
performance and availability of your farm.
Lesson Objectives
Describe the site collection upgrade process.
List the tasks that must be completed as part of the pre-upgrade health check.
Explain the steps that a farm administrator should take to manage the site collection upgrade
process.
Describe the site collection upgrade process.
Explain the post-upgrade verification steps that a site collection administrator must perform.
Overview of the Site Collection Upgrade Process
Upgrading site collections is a separate exercise
from upgrading content databases or service
applications. This is due to the emphasis in
SharePoint 2013 on delegated or distributed
management, where site collection administrators
and owners can play a far more active role in a
large number of administrative duties. The site
collection administrator can be far more familiar
with the business requirements for their site
collections, which can be a major advantage in
assessing the time and mode of any upgrade. The
delegation can also reduce the farm
administrators workload at a potentially busy time because that they can let site collection administrators
have greater control over business-led activities.
Delegation does not reduce the importance of the farm administrator. If an organization has business
critical sites, sites with major customizations, or very large sites collections, the farm administrator should
be closely involved in their upgrade. Because of their complexity or importance, farm administrators may
not feel comfortable delegating their upgrade to someone who is less expert in SharePoint Products and
Technologies. As a general rule, farm administrators should be involved if site collection upgrades that are
less than straight-forward. If you are to upgrade all of the site collections, you can do this automatically or
use Windows PowerShell.
Preparing site collection administrators
Site collection administrators who perform upgrades must be trained and involved in testing the upgrade
plan. Farm administrators must take them through the upgrade process, as well as the customization
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
process and basic troubleshooting. For organizations with many site collections, farm administrators may
find that this training process saves significant time and effort later on.
Farm administrators must ensure that site collection administrators are comfortable with the options for
SharePoint 2010 and SharePoint 2013 modes, and that they understand the use of upgrade evaluation
sites to test functionality. Farm administrators should be in charge of the overall plan and the timetable
for upgrades.
Site collection modes
You can create sites collections in either 2010 mode or 2013 mode; the former means that the user
interface is configured to resemble SharePoint Server 2010. Site collections remain in 2010 mode until
they are specifically upgraded to 2013 mode. The default setting is 2010 mode for upgraded site
collections. If you have mixed modes, you must be sure that all features and settings are available to both,
as covered earlier in this module.
Evaluation site collections
You can let site collection administrators preview their sites by enabling them to generate an upgrade
evaluation site collection. This creates a new, separate copy of the site, which has its own URL. The site is a
complete copy, but work that is done on the new copy does not affect the original.
The evaluation site is created by a timerCreate Upgrade Evaluation Site Collectionswhich runs once a
day. The evaluation site is available for 30 days, by default, and you must emphasize to your site collection
administrators that this is just for evaluation.
A site collection administrator can request an upgrade evaluation site collection by following these steps:
1. On the site collection Site Settings page, in the Site Collection Administration section, click Site
collection upgrade.
2. On the Step up to SharePoint 2013 page, click Try a demo upgrade.
3. In the Create Upgrade Evaluation Site Collection box, click Create Upgrade Evaluation Site
Collection.
4. Click Close to close the notification window.
The site collection administrator receives notification of the site collections availability in an email
message, which has a URL link to the site collection.
You can control the availability to create evaluation site collections by setting the
SPSite.AllowSelfServiceUpgradeEvaluation property for a site collection.
Running Site Collection Pre-Upgrade Health Check
SharePoint 2013 provides a packaged series of
health checks that your site collection
administrators can run on their sites before they
upgrade. Each check has a Rule ID, shown in
parentheses, which can be used to specify a
specific check when using Windows PowerShell.
The checks test the following features of each site
collection:
Conflicting Content Types. Checks for possible
issues between existing content types and
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
new (SharePoint 2013) content types, such as two types having the same name. (befe203b-a8c0-
48c2-b5f0-27c10f9e1622)
Customized Files. Checks for customized files in the site collection or its subsites. The check can be run
in repair mode. If this is the case, the page is reset to default. (cd839b0d-9707-4950-8fac-
f306cb920f6c)
Missing Galleries. Checks for all default galleries. If the check fails for the site collection or any of its
subsites, the missing galleries are reported. (ee967197-ccbe-4c00-88e4-e6fab81145e1)
Missing Parent Content Types. Checks for missing parent content types. (a9a6769f-7289-4b9f-ae7f-
5db4b997d284)
Missing Site Templates. Checks that the site template is available. Any failure issues are reported.
(5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd)
Unsupported Language Pack References. Checks availability and referencing of language packs.
(99c946f7-5751-417c-89d3-b9c8bb2d1f66)
Unsupported MUI References. Checks availability and referencing of multi-user interface elements.
(6da06aab-c539-4e0d-b111-b1da4408859a)
Running the pre-upgrade health checks through the SharePoint UI
The site collection administrator can complete the health checks by using the following procedure:
collection health checks.
2. On the Run site collection health checks page, click Start checks.
The procedure produces an issues report. If issues occur, these should be resolved and the procedure
rerun completely or, if the issue was minor and quickly resolved, the site administrator can click Try it
again.
Running the pre-upgrade health checks using Windows PowerShell
You can run the health check procedure in either:
Test Mode. Checks the site collection, but makes no changes to it.
Repair Mode. Checks the site collection and makes changes (repairs) that will enable successful
completion of the health checks, if possible.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
To run the procedure in Test mode, use the following syntax:
Test-SPSite -Identity <SiteURL> [-Rule <RuleID>]
<SiteURL> URL for the site collection.
<RuleID> ID for a rule that you wish to run, as listed above.
To run the procedure in Repair mode, use the following syntax:
Repair-SPSite -Identity <SiteURL> [-Rule <RuleID>]
<SiteURL> URL for the site collection.
<RuleID> ID for a rule that you wish to run, as listed above.
Managing Site Collection Upgrades
The farm administrator will configure and upgrade
the SharePoint 2013 farm, content databases, and
service applications before the site collection
administrators can perform site upgrades. As the
farm administrator, you can manage notification,
by email or through a message in the status bar,
that site collection upgrades can be started. This
enables you to control when site collection
administrators start their upgrades, thereby
allowing you to load balance the upgrades to
avoid contention on servers and the technical
support staff.
Site collection upgrade notification
You can control this notification to help ensure that all site collection administrators do not upgrade at
the same time and degrade farm performance. The site collection upgrade notification is set through
Windows PowerShell by using the following properties:

AllowSelfServiceUpgradeEvaluation. This allows site collection administrators to use the UI to request
upgrade evaluation sites.
SendSiteUpgradeEmails. This property enables you to send email to all site collection administrators
when upgrade evaluation site is requested and later created.
You can also provide notification by using the UpgradeReminderDelay property for a web application.
If you want to restrict site collection upgrades to 2010 mode, 2013 mode, or all modes (default), you can
use the SPWebApplication.CompatibilityRange property with a value of OldVersions, NewVersions,
or AllVersions.
The SPWebApplication.UpgradeReminderDelay property can be used to limit the appearance of the
upgrade notification on the status bar. Alternatively, if you want to send additional information to site
collection administrators who are likely to upgrade, you can use the
SPWebApplication.UpgradeMaintenanceLink property. This will add an additional link to the
upgrading now status message so that users can follow it and find out more information. This defaults to
being empty, so no link appears.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Site collection upgrade queuing
You can manage the site collection upgrade throughput for your farm by reviewing the upgrade queue.
All site collection upgrades are queued, even if they are processed immediately. Each upgrade is serviced
by the site collection upgrade timer job. You can manage the activity of the site collections in the queue
with Windows PowerShell.
Review the queue
You can see all the site collections in the upgrade queue for a given content database by running the
cmdlet:
Get-SPSiteUpgradeSessionInfo -ContentDatabase <DatabaseName> -ShowInProgress -
ShowCompleted -ShowFailed |ft
Where <DatabaseName> is name of the database or the database GUID.
Review current upgrades
You can review the site collections that are currently upgrading for a given content database by running
the cmdlet:
Get-SPSiteUpgradeSessionInfo ContentDatabase <DatabaseName> -ShowInProgress
Where <DatabaseName> is name of the database or the database GUID.
Check a specific site
You can check for a specific site collection in a queue by running the cmdlet:
Get-SPSiteUpgradeSessionInfo -Site <http://site>
Where <http://site> is URL for the site collection you want check.
Add a site collection to the queue
You can add a site collection to the upgrade queue by running the following cmdlets:
Upgrade-SPSite <http://site> -VersionUpgrade QueueOnly
Where <http://site> is URL for the site collection to add to the queue.
Remove a site collection from the upgrade queue
You can remove a site collection from the upgrade queue by running the cmdlet:
Remove-SPSiteUpgradeSessionInfo -Identity <URL>
Where <URL> is URL for the site collection you want to remove.
Throttling site collection upgrades
If you have decided to allow site collection administrators to upgrade their sites, you can still control
upgrade queues so that they do not affect the performance of your farm. You can do this by configuring
the following throttling options, which control the upgrade process by queuing upgrade requests at a
number of levels:
Web application. This defaults to five upgrades per web application and is controlled by the property
SPWebApplication.SiteUpgradeThrottleSettings AppPoolConcurrentUpgradeSessionLimit.
Database. This defaults to ten concurrent upgrades per content database and is set by the property
SPContentDatabase.ConcurrentSiteUpgradeSessionLimit.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Site content. This sets the maximum size and maximum number of subsites that can be upgraded in a
self-service procedure, so it should be upgraded by a farm administrator. The default is 10 MB in size
or 10 subsites. This is controlled by the properties SPWebApplication.SiteUpgradeThrottleSettings
UsageStorageLimit and SubwebCountLimit.
Upgrading a Site Collection
You, or your site collection administrators, can
only upgrade site collections after the farm
administrator has upgraded the SharePoint 2010
databases. The site collection upgrade should run
after the site collection health checks have
completed successfully.
Site collection upgrade procedure
A site collection administrator should perform the
following steps to complete the upgrade through
the SharePoint 2013 user interface:
collection upgrade.
2. On the Site Collection Upgrade page, click Upgrade this Site Collection, and click Im ready to
start the actual upgrade in the confirmation window. (The site collection health checks are run
automatically in repair mode before the upgrade starts). The Upgrade status page displays and
updates during the upgrade process, displaying information on:
a. Errors or warnings
b. Upgrade start time
c. Upgrade log file location
3. After the upgrade completes successfully, the Upgrade status page displays with the message
Completed Successfully.
4. Click Lets see the new site to open the site collection home page.
Using Windows PowerShell to upgrade site collections
You can use Windows PowerShell to upgrade a single site collection or all the site collections for a
specified database.
Upgrading a single site collection with Windows PowerShell
To upgrade a specific site collection to SharePoint 2013 with Windows PowerShell, you should use the
following cmdlet:
Upgrade-SPSite <http://site> -VersionUpgrade [-Unthrottled]
Where <http://site> is the URL for the site collection. You can optionally add the option -Unthrottled to
bypass the site collection upgrade queue.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Upgrading all site collections in a database with Windows PowerShell
You can choose to upgrade all site collections in a database to SharePoint 2013 mode, but this will mean
that site collection administrators cannot request an evaluation version for testing. This means that you
must be confident that all site collections in the database will function as required.
To upgrade all site collections in a database, you use the Windows PowerShell cmdlet:
Get-SPSite -ContentDatabase <DBName> -Limit All | Upgrade-SPSite -VersionUpgrade -
QueueOnly
Where <DBName> is the name of the content database for which you want to upgrade all site
collections. The -QueueOnly parameter means that the site collections are added to the upgrade queue
to avoid performance issues.
My Sites
If your organization uses My Sites, you must upgrade the My Site Host site collection before you allow
users to access their My Sites in SharePoint 2013. Because My Sites falls in the category of both large and
important site collections, the farm administrator should complete the My Site upgrade, having first
verified that all necessary farm upgrades are complete. The individual user My Site upgrades when the
user first navigates to their individual My Site.
Verifying Site Collection Upgrades
Site collection administrators must verify that their
site collections and subsites work as expected after
they complete their upgrade, even if they have
previously run an evaluation version of the site.
Upgrade status
The site collection administrators initial task is to
check the upgrade status of the site collection by
reviewing the site collection upgrade status. They
can do this by performing the following
procedure:
collection upgrade.
2. On the Site Collection Upgrade page, click Review Site Collection Upgrade Status.
This will display whether the site collection has successfully upgraded.
You can also use Windows PowerShell to check the upgrade status, by running the following cmdlet:
Get-SPSiteUpgradeSessionInfo -Site <http://site>
Where <http://site> is the site collection URL. This returns the upgrade status for the specified site.
Additional upgrade review checks
The upgrade status is useful, but it is not an exhaustive review of the site collections successful upgrade.
You should encourage site collection administrators to perform some additional upgrade validation
checks, such as:
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Does the site functions as expected? They should particularly review elements such as Web Part and
general screen rendering. They may need to ask users to perform some basic user acceptance testing
on their sites.
Do large lists render as expected? They should check that the required list throttling is configured.
Do cascading style sheets render the page as expected? Make sure that your site collection
administrators can recognize rendering issues such as this.
Are all menus functioning? They should check all JavaScript controls.
Do all user browsers render correctly? This must be checked for all users, including those who use
tablet or smartphone devices that should be supported.
Are all customizations in place? This is particularly important if there are users in both SharePoint
2010 and SharePoint 2013 modes.
All issues should be addressed promptly and escalated to the farm administrator. If the site collection is
upgraded by the farm administrator, each of these checks must be performed.
Logs
The site collection administrator should also review the log for the site collection upgrade, which they can
locate at http://<SiteName>/_catalogs/MaintenanceLogs/YYYYMMDD-HHMMSS-SSS.txt. The file name is
created by concatenating the year, month, day, hour, minute, and second when the log file was created;
the purpose of this naming convention is to simplify identification of the latest version, in case there are
multiple files.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Managing Site Collection Upgrades
Scenario
Some members of the IT team have raised concerns about the impact of site collection upgrades on the
performance of the SharePoint 2013 server farm as a whole. To allay these concerns, you will explore the
site collection upgrade process and review the settings that farm administrators can use to control the site
collection upgrade queue.
Objectives
Prepare site collections for upgrade.
Upgrade site collections by using the site collection user interface or Windows PowerShell.
Virtual machines: 20332B-NYC-DC-14, 20332B-NYC-DB-14, 20332B-NYC-SP-14
Password: Pa$$w0rd
Exercise 1: Preparing Site Collections for Upgrade
Scenario
In this exercise, you will prepare a site collection for upgrade. You will run site collection health checks,
both from the site collection user interface and from Windows PowerShell. You will repair any issues
identified by the health checks and then re-run the checks to verify the site collection is ready to upgrade.
1. Run site collection health checks from the browser
2. Run site collection health checks from Windows PowerShell
3. Repair a site collection
Task 1: Run site collection health checks from the browser
Switch back to the 20332B-NYC-SP-14 virtual machine. If you are not already logged on, log on as
In Internet Explorer, browse to finance.contoso.com. If you are prompted for credentials, log on as
Run site collection health checks from the site collection administration settings.
Verify that the health check detects problems in the following areas:
o Conflicting Content Types
o Customized Files
Task 2: Run site collection health checks from Windows PowerShell
Use Windows PowerShell to run site collection health checks on the site collection at
http://finance.contoso.com.
Verify that the PowerShell cmdlet identifies the same issues as the browser-based health checks.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Note: The Test-SPSite cmdlet and the browser-based health checks perform the same operation.
The browser-based health checks are aimed at site collection administrators, whereas the PowerShell-
based health checks are aimed at farm administrators.
Task 3: Repair a site collection
In Windows PowerShell, use the Repair-SPSite cmdlet to attempt to correct the issues with the
http://finance.contoso.com site collection.
Verify that the Repair-SPSite cmdlet was unable to resolve all the outstanding issues. This is because
the tool will not automatically make changes, such as deleting content types, which may affect
existing functionality.
Switch back to Internet Explorer.
On the finance.contoso.com site, rename the Video content type to Video_SP2010.
Re-run the site collection health checks and verify that the content type conflict is now resolved.
Note: The rule check still displays a warning that some files have been customized from their default.
However, in most cases you should not reset (re-ghost) pages to their original definitions unless they
present specific problems after upgrade. In a live environment, you should make a note of these pages
and verify each of them after the upgrade process.

Results: After completing this exercise, you should have prepared a site collection for upgrade.
Exercise 2: Upgrading Site Collections
Scenario
In this exercise, you will create an upgrade evaluation site collection from the site collection user interface.
You will then perform a site collection upgrade from Windows PowerShell, while reviewing some of the
cmdlets you can use to manage the upgrade process and the upgrade queue. Finally, you will verify that
the upgraded site collection behaves as you expect.
1. Create an upgrade evaluation site collection
2. Perform a site collection upgrade in Windows PowerShell
3. Verify that the upgraded site collection behaves as expected
Task 1: Create an upgrade evaluation site collection
In Internet Explorer on the 20332B-NYC-SP-14 virtual machine, on the site collection at
http://finance.contoso.com, request a demo upgrade from the site collection administration
settings.
On the Central Administration website, locate the Create Upgrade Evaluation Site Collections timer
job for the finance.contoso.com web application, and then run the timer job.
Browse to the list of site collections for the finance.contoso.com web application, and notice that a
new site collection with the relative URL /sites/root-eval has been created.
Browse to the site collection at http://finance.contoso.com/sites/root-eval, and verify that the site
is displayed as a SharePoint 2013 team site. Log on as CONTOSO\Administrator with the password
Pa$$w0rd if you are prompted.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Browse to the site collection at http://finance.contoso.com, and verify that the original Finance site
collection is unchanged.
Task 2: Perform a site collection upgrade in Windows PowerShell
In Windows PowerShell, use the Upgrade-SPSite cmdlet to upgrade the site collection at
http://finance.contoso.com.
Note: Ensure you perform a version-to-version upgrade rather than a build-to-build upgrade.
Use the Get-SPSiteUpgradeSessionInfo cmdlet to review the upgrade queue for the
WSS_FinanceContentDB_New database. If necessary, repeat the command until the status of the
current site collection upgrade shows as completed.
Review the site upgrade throttle settings for the finance.contoso.com web application. Verify that
site collection upgrades are subject to the following limits:
The application pool is limited to five concurrent site collection upgrades.
Site collection administrators are prevented from upgrading site collections with more than 10 MB of
content.
Site collection administrators are prevented from upgrading site collections with more than 10
subsites.
Task 3: Verify that the upgraded site collection behaves as expected
In Internet Explorer, browse to the site collection at http://finance.contoso.com. If you are
prompted for credentials, log on as CONTOSO\Administrator with the password Pa$$w0rd.
Verify that the site is displayed as a SharePoint 2013 team site.
Open the ContosoP1LaunchDeck presentation from the Shared Documents library. If you are
prompted for credentials, log on as CONTOSO\Administrator with the password Pa$$w0rd.
Verify that the document opens successfully, and then close it.
Browse to the Contracts library, and verify that the Contracts page is rendered as a SharePoint 2013
document library.
Browse to the Invoices library, and verify that the Contracts page is rendered as a SharePoint 2013
document library.

Results: After completing this exercise, you should have upgraded a site collection from SharePoint 2010
to SharePoint 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
In this module, you have reviewed the importance of preparing your upgrade and the steps that you
should take in readying your SharePoint 2010 farm and content for upgrade. You have also reviewed the
steps necessary to upgrade data and service applications. Finally, you have seen that site collection
upgrades can be delegated to your site collection administrators.
Review Question(s)
Test Your Knowledge
Question
Which of the following is NOT a supported upgrade path?

SharePoint Server 2010, Standard edition to SharePoint Server 2013, Standard
edition.
SharePoint Server 2010 to SharePoint Foundation 2013.
Search Server 2010 to SharePoint Server 2013.
Project Server 2010 with SharePoint Server 2010, Enterprise Edition to Project
Server 2013 with SharePoint Server 2013, Enterprise Edition.
SharePoint Server 2010, Trial edition to SharePoint Server 2013, Trial edition.
Test Your Knowledge
Question
Which of the following Windows PowerShell cmdlets should you run to review the
customizations in a SharePoint Server 2010 content database?

Get-SPContentDatabase
Mount-SPContentDatabase
Repair-SPSite
Test-SPContentDatabase
Upgrade-SPContentDatabase
Question: What are the key advantages of delegating site collection upgrades to site
collection administrators?

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Course Evaluation
Your evaluation of this course will help Microsoft understand the quality of your learning experience.
Please work with your training provider to access the course evaluation form.
Microsoft will keep your answers to this survey private and confidential and will use your responses to
improve your future learning experience. Your open and honest feedback is valuable and appreciated.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L1-1
Module 1: Understanding the SharePoint Server 2013
Architecture
Lab: Reviewing Core SharePoint Concepts
Exercise 1: Configuring SharePoint server 2013 Farms
Task 1: Create a Server Farm Account in Active Directory
1. Start the 20332B-NYC-DC-01 virtual machine. Wait for the virtual machine to display the logon
2. Start the 20332B-NYC-DB-01 virtual machine. Wait for the virtual machine to display the logon
3. Start the 20332B-NYC-SP-01 virtual machine. Wait for the virtual machine to display the logon screen
4. Log on to the 20332B-NYC-DC-01 machine as administrator@contoso.com with password
Pa$$w0rd.
5. On the Start screen, type Active Directory Administrative Center, and then press Enter.
6. In Active Directory Administrative Center, click Contoso (local).
7. In the Tasks pane, under Builtin, click New, and then click User.
8. In the Create User dialog box, in the Full name box, type SharePoint Farm.
9. In the User UPN logon box, type SPFarm, verify that the User SamAccountName logon boxes have
automatically populated with the corresponding user name.
10. In the Password and Confirm password boxes, type Pa$$w0rd.
11. Click Other password options, select the Password never expires, and User cannot change
password check boxes, and then click OK.
Task 2: Create service accounts for the web applications
2. In the Create User dialog box, in the Full name box, type sharepoint.contoso.com Service
Account.
3. In the User UPN logon box type SPContosoCom, verify that the User SamAccountName logon
boxes have automatically populated with the corresponding user name.
4. In the Password, and Confirm password boxes, type Pa$$w0rd.
7. In the Create User dialog box, in the Full name box, type finance.contoso.com App Service
Account.
8. In the User UPN logon box type SPFinanceWebApp, verify that the User SamAccountName logon
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L1-2 Advanced Solutions of Microsoft SharePoint Server 2013
12. In the Create User dialog box, in the Full name box, type sales.contoso.com App Service Account.
13. In the User UPN logon box type SPSalesWebApp, verify that the User SamAccountName logon
Task 3: Configure DNS for the sharepoint.contoso.com and finance.contoso.com
domains
1. On the Start screen, type DNS, and then press Enter.
2. In DNS Manager, expand NYC-DC1, expand Forward Lookup Zones, and then click Contoso.com.
3. Right-click Contoso.com and then click New Host (A or AAAA).
4. In the New Host dialog box, in the Name box, type sharepoint, in the IP address box, type
172.16.1.21, and then click Add Host.
5. In the DNS dialog box, click OK.
6. In the New Host dialog box, in the Name box, type finance, in the IP address box, type
8. In the New Host dialog box, click Done.
9. Right-click Forward Lookup Zones, and then click New Zone.
10. In the New Zone Wizard dialog box, on the Welcome to the New Zone Wizard page, click Next.
11. On the Zone Type page, click Next.
12. On the Active Directory Zone Replication Scope page, click Next.
13. On the Zone Name page, in the Zone name box, type finance, and then click Next.
14. On the Dynamic Update page, click Next.
15. On the Completing the New Zone Wizard page, click Finish.
16. Click finance, right-click finance, and then click New Host (A or AAAA).
17. In the New Host dialog box, in the IP address box, type 172.16.1.21, and then click Add Host.
20. Close all open windows.
Task 4: Enable TCP/IP Connectivity in SQL Server
1. Log on to the 20332B-NYC-DB-01 virtual machine as CONTOSO\Administrator with the password
Pa$$w0rd.
2. On the Start screen, type SQL Server Configuration Manager, and then press Enter.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L1-3
3. In SQL Server Configuration Manager, expand SQL Server Network Configuration, and then click
Protocols for MSSQLSERVER.
4. Right-click TCP/IP, and then click Enable.
5. In the Warning dialog box, click OK.
6. Click SQL Server Services.
7. Right-click SQL Server (MSSQLSERVER), and then click Restart.
8. Wait for the service to restart, and then close SQL Server Configuration Manager.
Task 5: Create a SQL Server Alias on the SharePoint 2013 Server
1. Log on to the 20332B-NYC-SP-01 machine as administrator@contoso.com with the password
Pa$$w0rd.
2. On the desktop, click File Explorer, browse to C:\Windows\System32, and then double-click
cliconfg.exe.
3. In the SQL Server Client Network Utility dialog box, on the Alias tab, click Add.
4. In Add Network Library Configuration dialog box, in the Server alias box, type ContosoDB, under
Network libraries, click TCP/IP, in the Server name box, type NYC-DB1, and then click OK.
5. In the SQL Server Client Network Utility dialog box, click OK.
6. In File Explorer, browse to C:\Windows\SysWOW64, and then double-click cliconfg.exe.
7. In the SQL Server Client Network Utility dialog box, on the Alias tab, click Add.
8. In Add Network Library Configuration dialog box, in the Server alias box, type ContosoDB, under
Network libraries, click TCP/IP, in the Server name box, type NYC-DB1, and then click OK.
9. In the SQL Server Client Network Utility dialog box, click OK.
Task 6: Run the SharePoint Products Configuration Wizard
1. On the 20332B-NYC-SP-01 machine, on the Start screen, type SharePoint Products Configuration,
and then press Enter.
2. In SharePoint Products Configuration Wizard, on the Welcome to SharePoint Products page, click
Next.
3. In the SharePoint Products Configuration Wizard dialog box which warns you about services being
started or reset, click Yes.
4. On the Connect to a server farm page, click Create a new server farm, and then click Next.
5. On the Specify Configuration Database Settings page, in the Database server box, type
ContosoDB, in the Username box, type CONTOSO\SPFarm, in the Password box, type Pa$$w0rd,
and then click Next.
6. On the Specify Farm Security Settings page, in the Passphrase and Confirm passphrase boxes,
type Pa$$w0rd, and then click Next.
7. On the Configure SharePoint Central Administration Web Application page, select the Specify
port number check box, in the Specify port number box, type 50000, and then click Next.
8. On the Completing the SharePoint Products Configuration Wizard page, verify the settings, and
then click Next.
9. On the Configuration Successful page, click Finish.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
10. In Internet Explorer, if you are prompted to set up Internet Explorer 10, click User recommended
security and compatibility settings, and then click OK.
11. In the Help Make SharePoint Better dialog box, click Yes, I am willing to participate
(Recommended), and then click OK.
12. On the Welcome page, click No, I will configure everything myself.
Task 7: Register the web application service accounts as SharePoint managed
accounts
1. On the Start screen, type Central Administration, and then press Enter.
2. In Central Administration, click Security.
3. On the Security page, under General Security click, Configure managed accounts.
4. On the Managed Accounts page, click Register Managed Account.
5. On the Register Managed Account page, in the User name box, type contoso\SPContosoCom, in
the Password box, type Pa$$w0rd, and then click OK.
7. On the Register Managed Account page, in the User name box, type
contoso\SPFinanceWebApp, in the Password box, type Pa$$w0rd, and then click OK.
Task 8: Create the sharepoint.contoso.com and finance.contoso.com web
applications
1. Click Application Management.
2. On the Application Management page, click Manage web applications.
3. On the Web Applications Management page, on the ribbon, click New.
4. In the Create New Web Application dialog box, under IIS Web Site, in the Port box type 80.
5. In the Host Header box, type sharepoint.contoso.com.
6. Under Application Pool, in the Application pool name box, type SharePoint - 80.
7. In the Configurable list, click CONTOSO\SPContosoCom, and then click OK.
8. In the Application Created dialog box, click OK.
10. On the Create New Web Application dialog box, in the Port box, type 80.
11. In the Host Header box type, finance.contoso.com.
12. Under Application Pool, in the Application pool name box, type SharePointFinance - 80.
13. In the Configurable list, click CONTOSO\SPFinanceWebApp, and then click OK.
15. On the Start screen, type IIS, and then press Enter.
16. In Internet Information Services (IIS) Manager, expand NYC-SP1 (CONTOSO\Administrator).
17. If an Internet Information Services (IIS) Manager dialog box appears, asking you about getting
started with Microsoft Web Platform, click No.
18. Expand Sites, and then click SharePoint - finance.contoso.com80.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L1-5
19. In the Actions pane, click Bindings.
20. In the Site Bindings dialog box, click Add.
21. In the Add Site Binding dialog box, in the IP address list, click 172.16.1.21, in the Host name box
type finance, click OK.
22. In the Site Bindings dialog box, click Close.
23. Close Internet Information Services (IIS) Manager.
Task 9: Disable loopback checking for the sharepoint.contoso.com and
finance.contoso.com domains
1. On the Start screen, type regedit, and then press Enter.
2. In Registry Editor, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet,
expand Control, and then expand Lsa.
3. Under Lsa, right-click MSV1_0, point to New, and then click Multi-String Value.
4. Type BackConnectionHostNames, and then press Enter.
5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Edit Multi-String dialog box, in the Value data box, type sharepoint.contoso.com, and then
press Enter.
7. Type finance.contoso.com, and then press Enter.
8. Type finance, and then click OK.
9. If a Warning dialog box appears, click OK.
10. On the start screen, type Command Prompt, and then press Enter.
11. At the command prompt, run the following command:
iisreset /noforce

Results: After completing this exercise, you should have completed initial SharePoint configuration,
including provisioning the SharePoint Central Administration website, and created a new web application
for the sharepoint.contoso.com domain

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 2: Creating and Configuring Site Collections and Sites
Task 1: Create a top-level site collection for the sharepoint.contoso.com web
application
3. On the Application Management page, click Create site collections.
4. On the Create Site Collection page, under Web Application verify that
http://sharepoint.contoso.com is selected. If it is not currently selected, click the current web
application, click Change Web Application, and then click SharePoint -
sharepoint.contoso.com80.
5. Under Title and Description, in the Title box, type SharePoint.
6. Under Template Selection, verify that Team Site is selected.
7. Under Primary Site Collection Administrator, in the User name box, type
CONTOSO\Administrator, and then click OK.
8. On the Top-Level Site Successfully Created page, click OK.
9. In Internet Explorer, browse to http://sharepoint.contoso.com.
10. In the Windows Security dialog box, in the User name box, type administrator, in the Password
box, type Pa$$w0rd, and then click OK.
Task 2: Create a site in the sharepoint.contoso.com site collection
1. On the SharePoint site, click Settings, and then click Site contents.
2. On the Site Contents page, click new subsite.
3. On the New SharePoint Site page, in the Title box, type IT, in the URL name box, type IT, and then
click Create.
4. Verify that the IT site displays correctly.
5. Close Internet Explorer.
Task 3: Create a top-level site for the finance.contoso.com web application
http://finance.contoso.com is selected. If it is not currently selected, click the current web
application, click Change Web Application, and then click SharePoint - finance.contoso.com80.
5. Under Title and Description, in the Title box, type Finance Extranet.
6. Under Template Selection, verify that Team Site is selected.
9. In Internet Explorer, browse to http://finance.contoso.com.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L1-7
Task 4: Use PowerShell to create a host named site collection in the
finance.contoso.com web application
1. On the Start screen, type SharePoint Management Shell, and then press Enter.
New-SPSite http://finance -HostHeaderWebApplication http://finance.contoso.com -Name
"Finance Intranet" -OwnerAlias CONTOSO\Administrator -Template STS#0
3. In Internet Explorer, browse to http://finance.
4. If the Windows Security dialog box appears, in the User name box, type administrator, in the
Password box, type Pa$$w0rd, and then click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L2-1
Module 2: Designing Business Continuity Management
Strategies
Lab: Planning and Performing Backups and
Restores
Exercise 1: Create a Backup and Restore Plan
1. Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen.
2. Log on to the NYC-CL1 machine as admin with the password Pa$$w0rd.
3. Read the lab scenario.
4. In the E:\Mod02\Starter folder, read the information in the Contoso Business Continuity
Task 2: Complete the Backup and Restore Planning worksheet
1. In the E:\Mod02\Starter folder, open and complete the worksheet in the SharePoint 2013 Backup
and Restore Planning Worksheet.xlsx file, based on the information you have reviewed in Task 1.
2. Shut down the 20332B-NYC-CL virtual machine.

Results: A completed SharePoint Backup Plan

Exercise 2: Test the Backup and Restore Process
Task 1: Prepare the backup storage for backing up a SharePoint server
4. Log on to the 20332B-NYC-DB-02 machine as administrator@contoso.com with the password
Pa$$w0rd.
5. On the Start screen type C:\ and then press Enter.
6. In Windows Explorer, on the ribbon, on the Home tab, click New folder, type Backups and then
press Enter.
7. Right-click the Backups folder, point to Share with and then click Specific people.
8. In the File Sharing dialog box, type MSSQLSERVER, and then click Add.
9. In the MSSQLSERVER row, in the Permission Level column, click the drop-down arrow, and then
click Read/Write.
10. In the text box, type CONTOSO\SPFarm, and then click Add.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
11. In the CONTOSO\SPFarm row, in the Permission Level column, click the drop-down arrow, click
Read/Write, and then click Share.
12. In the File Sharing dialog box, when the message Your folder is shared appears, click Done.
Task 2: Perform a backup of SharePoint components
Pa$$w0rd.
3. On the Central Administration website, click Backup and Restore.
4. On the Backup and Restore page, click Configure backup settings.
5. On the Default Backup and Restore Settings page, in the Backup location box type \\NYC-
DB1\Backups and then click OK.
6. On the Backup and Restore page, click Perform a backup.
7. On the Perform a Backup Step 1 of 2 page, locate the Shared Services top-level component. In
that row, select the check box, and then click Next.
8. On the Perform a Backup Step 2 of 2 page, click Start Backup.
9. On the Backup and Restore Job Status page, click Refresh. Periodically repeat this step until the
backup phase is reported as Completed.
Task 3: Remove SharePoint components to simulate a failure
2. On the Application Management page, under Service Applications, click Manage service
applications.
3. On the Manage Service Applications page, select Contoso UPSA and then, on the ribbon, click
Delete.
4. In the Delete Service Application dialog box, select Delete data associated with the Service
Applications and then click OK.
5. In the Delete Service Application dialog box, when the message The Service Application has been
deleted appears, click OK.
6. In Internet Explorer, refresh the Manage Service Applications page, and then verify that the
Contoso UPSA service application is no longer included in the list of service applications.
Task 4: Restore failed SharePoint components from a backup
1. On the Central Administration website, click Backup and Restore.
2. On the Backup and Restore page, click Restore from a backup.
3. On the Backup and Restore History page, locate the backup with the Top Component of
Farm\Shared Services. In that row, click Select, and then click Next.
4. On the Restore from Backup Step 2 of 3 page, expand Shared Services, expand Shared Services
Applications, and locate the Contoso UPSA service application. In that row select Select, and then
click Next.
5. On the Restore from Backup Step 3 of 3 page, under Restore Options, click Same
configuration.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L2-3
6. In the Message from webpage dialog box, click OK.
7. Under Login Names and Passwords, in the Password box type Pa$$w0rd, and then click Start
Restore.
restore phase is reported as Completed.
9. Click Backup and Restore, and then click Restore from a backup.
10. On the Backup and Restore History page, locate the backup with the Top Component of
Farm\Shared Services. In that row, click Select, and then click Next.
11. On the Restore from Backup Step 2 of 3 page, expand Shared Services Proxies, and locate the
Contoso UPSA application proxy. In that row select Select, and then click Next.
12. On the Restore from Backup Step 3 of 3 page, under Restore Options, select Same
configuration.
14. Click Start Restore.
restore phase is reported as Completed.
applications.
18. On the Manage Service Applications page, verify that the Contoso UPSA service application and
application proxy have been restored.

Results: After completing this exercise, you should have tested the backup and restore process for a
SharePoint 2013 service application.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L3-1
Module 3: Planning and Implementing a Service Application
Architecture
Lab A: Planning a Service Application
Architecture
Exercise 1: Planning a Service Application Topology
1. Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen
4. In the E:\Mod03\Starter folder, read the information in the Contoso Services Business
Task 2: Complete the Service Applications Planning worksheet
1. In the E:\Mod03\Starter folder, open and complete the worksheet in the SharePoint 2013 Service
Applications Planning Worksheet.xlsx file, based on the information you have reviewed in Task 1.

Results: A completed Service Application Planning worksheet.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Federating Service Applications
between SharePoint Server Farms
Exercise 1: Creating a Service Application Instance
Task 1: Create a service account to run the Managed Metadata Service
screen, and then wait a further five minutes before starting the next step.
4. Start the 20332B-NYC-FARM2-03 virtual machine. Wait for the virtual machine to display the logon
Pa$$w0rd.
9. In the Create User dialog box, in the Full name box, type SharePoint General MMS.
10. In the User UPN logon box, type ContosoMMS.
11. Verify that the User SamAccountName logon boxes have automatically populated with the
corresponding user name.
Pa$$w0rd.
6. On the Register Managed Account page, in the User name box, type CONTOSO\ContosoMMS, in
Task 3: Start the Managed Metadata Web Service service
1. Click Central Administration, and then under System Settings, click Manage services on server.
2. Locate the Managed Metadata Web Service service, and then in that row click Start.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L3-3
Task 4: Create a new Managed Metadata Service application instance
1. Click Application Management, and then under Service Applications, click Manage service
applications.
2. On the ribbon, click New, and then click Managed Metadata Service.
3. In the Create New Managed Metadata Service dialog box, in the Name box, type Contoso
Managed Metadata Service.
4. In the Database Name box, type ContosoMMS.
5. In the Application Pool section, click Create new application pool, and then in the Application
pool name box, type ContosoMMSAppPool.
6. In the Configurable list, click CONTOSO\ContosoMMS.
7. In the Content Type hub box, type http://sharepoint.contoso.com, and then click OK.
8. If the Message from webpage dialog box appears, click OK.
Task 5: Create sample term sets
1. On the list of service applications, click the uppermost Contoso Managed Metadata Service row,
and then on the ribbon, click Manage.
2. On the Term Store Management Tool page, in the navigation pane, click Contoso Managed
Metadata Service.
3. On the Contoso Managed Metadata Service drop-down menu, click New Group.
4. Type Organization, and then press Enter.
5. On the Organization drop-down menu, click New Term Set.
6. Type Department, and then press Enter.
7. On the Department drop-down menu, click Create Term.
8. Type Marketing, and then press Enter.
9. Type Finance, and then press Enter.
10. Type IT, and then press Enter.
11. Type Sales, and then press Enter.
12. On the Organization drop-down menu, click New Term Set.
13. Type Supplier, and then press Enter.
14. On the Supplier drop-down menu, click Create Term.
15. Type Litware, Inc., and then press Enter.
16. Type Proseware, Inc., and then press Enter.
17. Type Northwind Traders, and then press Enter.
18. Type Trey Research, and then press Enter.
19. Type Wide World Importers, and then press Enter.

Results: After completing this exercise, you should have provisioned a Managed Metadata Service
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 2: Establishing Trust Relationships between SharePoint Farms
Task 1: Export certificates from the consumer farm
1. Log on to the 20332B-NYC-FARM2-03 virtual machine as CONTOSO\Administrator with password
Pa$$w0rd.
2. On the Start screen, type SharePoint 2013 Management Shell, and then press Enter.
3. At the command prompt, type the following command, and then press Enter:
$rootcert = (Get-SPCertificateAuthority).RootCertificate
$rootcert.Export("Cert") | Set-Content "E:\ConsumerFarmRoot.cer" -Encoding byte
$stscert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate
$stscert.Export("Cert") | Set-Content "E:\ConsumerFarmSTS.cer" -Encoding byte
7. Close the SharePoint 2013 Management Shell.
8. On the Windows taskbar, click File Explorer.
9. In the File Explorer window, expand Computer, and then double-click Allfiles (E:).
10. Select the ConsumerFarmRoot and ConsumerFarmSTS files, right-click the files, and then click
Copy.
11. In the File Explorer address bar, type \\NYC-SP1\Share, and then press Enter.
12. Right-click the content area, and then click Paste.
13. Close the File Explorer window.
Task 2: Export the root certificate from the provider farm
1. Switch to the 20332B-NYC-SP-03 virtual machine.
$rootcert = (Get-SPCertificateAuthority).RootCertificate
$rootcert.Export("Cert") | Set-Content "E:\ProviderFarmRoot.cer" -Encoding byte
7. In the File Explorer window, double-click Allfiles (E:).
8. Right-click the ProviderFarmRoot.cer, and then click Copy.
9. In the File Explorer address bar, type \\NYC-FARM2\Share, and then press Enter.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L3-5
Task 3: Create a trusted root authority on the consumer farm
1. Switch to the 20332B-NYC-FARM2-03 virtual machine. If you are not already logged on, log on as
$trustcert = Get-PfxCertificate "E:\Share\ProviderFarmRoot.cer"
New-SPTrustedRootAuthority "Contoso Provider Farm" -Certificate $trustcert
Task 4: Create a trusted root authority on the provider farm
1. Switch to the 20332B-NYC-SP-03 virtual machine. If you are not already logged on, log on as
$trustcert = Get-PfxCertificate "E:\Share\ConsumerFarmRoot.cer"
New-SPTrustedRootAuthority "Contoso Consumer Farm" -Certificate $trustcert
Task 5: Create a trusted token issuer on the provider farm
$stscert = Get-PfxCertificate "E:\Share\ConsumerFarmSTS.cer"
New-SPTrustedServiceTokenIssuer "Contoso Consumer Farm" -Certificate $stscert
4. On the Start screen, type SharePoint 2013 Central Administration, and then press Enter.
5. On the Quick Launch navigation menu, click Security.
6. Under General Security, click Manage trust.
7. Verify that Contoso Consumer Farm is listed with a type of Trusted Service Provider.
Note: The term Trusted Service Provider on this page can be confusing, as in this case
you want to use Contoso Consumer Farm to consume services. In this context, the term Trusted
Service Provider means that the local farm includes a trust relationship that enables it to provide
services to Contoso Consumer Farm.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Results: After completing this exercise, you should have configured a trust relationship between two
SharePoint farms.

Exercise 3: Publishing and Consuming Service Applications
Task 1: Get the ID of the consumer farm
Get-SPFarm | Select Id | Set-Content "E:\ConsumerFarmID.txt"
6. In the File Explorer window, double-click Allfiles (E:).
7. Right-click the ConsumerFarmID.txt file, and then click Copy.
8. In the File Explorer address bar, type \\NYC-SP1\Share, and then press Enter.
10. Close the File Explorer window
Task 2: Grant the consumer farm permissions on the provider farm Application
Discovery and Load Balancing Service Application
3. In the File Explorer window, browse to E:\Share, and then open the ConsumerFarmID.txt file.
4. In the ConsumerFarmID.txt file, select the GUID, and then on the Edit menu, click Copy.
Note: Only copy the GUID. Do not include the curly brackets or the preceding text.
5. Close the Notepad window and the File Explorer window.
$security = Get-SPTopologyServiceApplication | Get-SPServiceApplicationSecurity
$claimprovider = (Get-SPClaimProvider System).ClaimProvider
9. At the command prompt, type the following command, and then press Enter (replace
<ConsumerFarmID> with the value you copied from the text file):
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L3-7
$principal = New-SPClaimsPrincipal -ClaimType
"http://schemas.microsoft.com/sharepoint/2009/08/claims/farmid" -ClaimProvider
$claimprovider -ClaimValue <ConsumerFarmID>
Grant-SPObjectSecurity -Identity $security -Principal $principal -Rights "Full
Control"
Get-SPTopologyServiceApplication | Set-SPServiceApplicationSecurity -ObjectSecurity
$security
Task 3: Grant the consumer farm permissions on the provider farm Managed
Metadata Service application
2. Under Application Management, click Manage service applications.
3. On the list of service applications, click the uppermost Contoso Managed Metadata Service.
4. On the ribbon, click Permissions.
5. In the Connection Permissions for Contoso Managed Metadata Service dialog box, in the text
box, paste the GUID that you copied from the text file, and then click Add.
6. In the list of permissions, select the Full Access to Term Store check box, and then click OK.
Task 4: Publish the Managed Metadata Service application on the provider farm
1. In the list of service applications, ensure that Contoso Managed Metadata Service is still selected.
3. In the Publish Service Application dialog box, in the Connection Type list, ensure http is selected.
4. Select the Publish this Service Application to other farms check box.
5. Under Published URL, select the URL, right-click the selected text, and then click Copy.
6. In the Description text box, type Managed Metadata Service application from the Contoso
provider farm, and then click OK.
9. In the File Explorer address bar, type \\NYC-FARM2\Share, and then press Enter.
10. Right-click in the content area, point to New, and then click Text Document.
11. Type ContosoManagedMetadataURL, and then press Enter.
12. Open the ContosoManagedMetadataURL.txt file, paste the URL you copied, and then save and
close the file.
Task 5: Connect to the Managed Metadata Service application from the consumer
farm
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
3. Browse to E:\Share, and then double-click ContosoManagedMetadataURL.txt.
4. Select and copy the URL, and then close the file.
8. On the ribbon, on the Connect menu, click Managed Metadata Service Connection.
9. In the Connect to a Remote Service Application dialog box, in the text box, paste the URL you
copied from the text file, and then click OK.
10. When the dialog box displays the Contoso Managed Metadata Service application, click Contoso
Managed Metadata Service, and then click OK.
11. When you are prompted to name the connection, accept the default name and click OK.
12. When the dialog box displays a success message, click OK.
13. On the list of service applications, click Connection to: Contoso Managed Metadata Service.
14. On the ribbon, click Manage.
15. On the Term Store Management Tool page, verify that the Organization term set is displayed from
the remote farm.

Results: After completing this exercise, you should have published a service application on one
SharePoint farm and connected to the service application from another SharePoint farm.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L4-1
Module 4: Configuring and Managing Business Connectivity
Services
Lab A: Configuring BCS and the Secure
Store Service
Exercise 1: Configuring the Business Data Connectivity Service Application
Task 1: Create a service account to run the BDC service application
Pa$$w0rd.
8. In the Create User dialog box, in the Full name text box, type SharePoint BDC.
9. In the User UPN logon text box type SP_BDC.
10. Verify that the User SamAccountName logon box is automatically populated with the
corresponding username.
11. In the Password box type Pa$$w0rd, and then in the Confirm password box, type Pa$$w0rd
12. Click Other password options, select Password never expires, select User cannot change
password, and then click OK.
Pa$$w0rd.
3. In the command prompt window, type the following command, and then press Enter:
New-SPManagedAccount
4. In the Windows PowerShell Credential dialog box, type the user name CONTOSO\SP_BDC and the
password Pa$$w0rd, and then click OK.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Start the Business Data Connectivity Service
2. Under System Settings, click Manage services on server.
3. On the Services on Server page, in the Business Data Connectivity Service row, click Start.
Task 4: Create a new Business Data Connectivity service application instance
1. On the Central Administration website, on the Quick Launch navigation menu, click Application
Management.
applications.
3. On the ribbon, click New, and then click Business Data Connectivity Service.
4. In the Create New Business Data Connectivity Service Application dialog box, in the Service
Application Name text box, type Contoso BDC.
5. In the Database Name text box, delete the existing text, and then type Contoso_BDC_DB.
6. Under Application Pool, in the Application pool name text box, type SharePointContosoBDC.
7. In the Configurable dropdown list, click CONTOSO\SP_BDC, and then click OK.
8. In the dialog box that reports that the service application was created successfully, click OK.
Task 5: Set metadata store permissions
1. In the list of service applications, click Contoso BDC, and then on the ribbon, click Manage.
2. On the ribbon, click Set Metadata Store Permissions.
3. In the Set Metadata Store Permissions dialog box, type CONTOSO\Administrator, and then click
Add.
4. Under Permissions for CONTOSO\Administrator, select all permissions.
5. Select Propagate permissions to all BDC Models, External Systems, and External Content Types
in the BDC Metadata Store, and then click OK.

Results: After completing this exercise, you should have created and configured a Business Data
Connectivity Service application instance.

Exercise 2: Configuring the Secure Store Service
Task 1: Create a service account to run the Secure Store Service application
1. Switch to the 20332B-NYC-DC-04 machine. If you are not already logged on, log on as
administrator@contoso.com with password Pa$$w0rd.
5. In the Create User dialog, in the Full name box, type SharePoint SSS.
6. In the User UPN logon box, type SP_SSS.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L4-3
7. Verify that the User SamAccountName logon box is automatically populated with the
8. In the Password box, type Pa$$w0rd, and then in the Confirm password box, type Pa$$w0rd
1. Switch to the 20332B-NYC-SP-04 machine. If you are not already logged on, log as
3. In the command prompt window, type the following command, and then press Enter:
4. In the Windows Powershell Credential dialog box, type the user name CONTOSO\SP_SSS and the
password Pa$$w0rd, and then click OK.
Task 3: Start the Secure Store Service
2. Under System Settings, click the Manage services on server.
3. On the Services on Server page, in the Secure Store Service row, click Start.
Task 4: Create a new Secure Store Service application instance
Management.
applications.
3. On the ribbon, click New, and then click Secure Store Service.
4. In the Create New Secure Store Service Application dialog box, in the Service Application Name
text box, type Contoso Secure Store.
5. In the Database Name text box, delete the existing text, and then type Contoso_SSS_DB.
6. Under Application Pool, in the Application pool name text box, type SharePointContosoSSS.
7. In the Configurable drop-down list, click CONTOSO\SP_SSS, and then click OK.
8. In the dialog box that reports that the service application was created successfully, click OK.
Task 5: Create a secure store master key
1. In the list of service applications, click Contoso Secure Store, and then on the ribbon, click Manage.
2. On the ribbon, click Generate New Key.
3. In the Generate New Key dialog box, in the Pass Phrase text box, type Pa$$w0rd, in the Confirm
Pass Phrase text box, type Pa$$w0rd, and then click OK.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Results: After completing this exercise, you should have created and configured a Secure Store Service

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L4-5
Lab B: Managing Business Data Connectivity
Models
Exercise 1: Configuring a Secure Store Service target application
Task 1: Create a new target application
Pa$$w0rd if you are not already logged in.
5. On the ribbon, in the Manage Target Applications group, click New.
6. On the Create New Secure Store Target Application page, in the Target Application ID text box,
type ContosoDW_TA.
7. In the Display Name text box, type ContosoDW database target application.
8. In the Contact E-mail text box, type administrator@contoso.com.
9. In the Target Application Type dropdown list, click Group.
10. Click Next.
11. Leave the field names and field types unchanged, and then click Next.
12. In the Target Application Administrators text box, type CONTOSO\Administrator, and then click
Check Names.
13. In the Members text box, type CONTOSO\Sales;CONTOSO\Administrator, click Check Names, and
then click OK.
Task 2: Set the credentials for the target application
1. In the list of target applications, select ContosoDW_TA.
2. On the ribbon, in the Credentials group, click Set.
3. In the Set Credentials for Secure Store Target Application (Group) dialog box, in the Windows
User Name text box, type CONTOSO\CDW_User.
4. In the Windows Password text box, type Pa$$w0rd.
5. In the Confirm Windows Password text box, type Pa$$w0rd, and then click OK.

Results: After completing this exercise, you should have created and configured a secure store target
application.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 2: Importing and Configuring BDC Models
Task 1: Import the ContosoDW BDC model
Management.
2. Under Service Applications, click Manage service applications.
3. In the list of service applications, click Contoso BDC, and then click Manage.
4. On the ribbon, in the BDC Models group, click Import.
5. On the Import BDC Model page, click Browse.
6. In the Choose File to Upload dialog box, browse to E:\Mod04, click ContosoDW.bdcm, and then
click Open.
7. Leave the remaining settings unchanged, and then click Import.
8. When the message confirming that the model was imported successfully appears, click OK.
Task 2: Associate the external system in the BDC model with a target application
1. On the ribbon, in the View group, in the dropdown list, click External Systems
2. Click ContosoDW.
3. Click ContosoDW again.
4. In the Secure Store Target Application Id text box, delete the existing text, and then type
ContosoDW_TA.
5. Click OK.
Task 3: Create an external list to review the model data
1. In the Internet Explorer address bar, type sharepoint.contoso.com, and then press Enter.
2. If you are prompted for credentials, log on as CONTOSO\Administrator with password Pa$$w0rd.
3. On the Settings menu, click Add an app.
4. On the Your Apps page, click External List.
5. In the Adding External List dialog, in the Name text box, type Employees.
6. Click the Select External Content Type icon, click Employees, and then click OK.
7. Click Create.
8. On the Site Contents page, click Employees.
9. The page may take up to two minutes to load due to the constraints of the classroom environment.
10. When the page loads, verify that the page displays a list of employees from the database.
11. Click the ellipsis () in one of the rows, and then click View Item.
12. Verify that the page displays the details of the selected employee.

Results: After completing this exercise, you should have imported and configured a BDC model.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-1
Module 5: Connecting People
Lab A: Configuring Profile Synchronization
and My Sites
Exercise 1: Configuring Profile Synchronization
Task 1: Create a service account for the service application
screen, then wait a further five minutes before you proceed to the next step.
Pa$$w0rd.
8. In the Create User dialog box, in the Full name box, type Profile Service
9. In the User UPN logon box, type ProfileService, and then verify that the User SamAccountName
logon box is automatically populated with the corresponding user name.
10. In the Password box, type Pa$$w0rd, and then in the Confirm password box, type Pa$$w0rd.
Task 2: Grant the SPFarm account the Replicating Directory Changes permission
1. Right click Contoso (local), and then click Properties.
2. In the Contoso dialog box, in the Extensions panel, on the Security tab, click Add.
3. In the Select Users, Computers, Service Accounts, or Groups dialog box, in the Enter the object
names to select box, type SPFarm, and then click OK.
4. Under Permissions for SPFarm, locate the Replicating Directory Changes permission row, select
Allow, and then click OK.
5. On the Start screen, type ADSI Edit, and then press Enter.
6. In the ADSI Edit window, right-click ADSI Edit, and then click Connect to.
7. In the Connection Settings dialog box, in the Select a well known Naming Context list, click
Configuration, and then click OK.
8. Expand Configuration [NYC-DC1.Contoso.com].
9. Right-click CN=Configuration,DC=Contoso,DC=com, and then click Properties.
10. In the CN=Configuration,DC=Contoso,DC=com Properties dialog box, on the Security tab, in the
Group or user names section, click Add.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
12. In the CN=Configuration,DC=Contoso,DC=com Properties dialog box, in the Permissions for
SPFarm section, in the Replicating Directory Changes row, select Allow, and then click OK.
13. Close the ADSI Edit window.
Task 3: Grant the SPFarm account local administrator permissions on the SharePoint
server
Pa$$w0rd.
2. On the Start screen, type Local Users, click Settings, and then click Edit local users and groups.
3. In the lusrmgr [Local Users and Groups (local)] dialog box, click Groups, and then double click
Administrators.
4. In the Administrators Properties dialog box, click Add.
6. In the Administrators Properties dialog box, click OK.
7. On the Start screen, type Services, and then click Services.
8. In the Services dialog box, click Services (Local), click SharePoint Timer Service, and then click
Restart. Wait for the service to restart before continuing.
2. On the Central Administration website, click Security, and then on the Security page, under
General Security, click Configure managed accounts.
4. On the Register Managed Account page, in the User name box, type CONTOSO\ProfileService, in
Task 5: Create a new User Profile Service Application application instance
2. On the Application Management page, click Manage service applications.
3. On the Manage Service Applications page, on the ribbon, click New, and then click User Profile
Service Application.
4. In the Create New User Profile Service Application dialog box, in the Name text box, type
Contoso UPSA.
5. In the Application pool name box, type ContosoUPSAAppPool.
6. In the Configurable list, click CONTOSO\ProfileService, and then click Create.
7. When the Profile Service Application successfully created message appears, click OK.
8. Refresh the Manage Service Applications page and verify that the Contoso UPSA service
application and the Contoso UPSA service application proxy are included in the list of service
applications.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-3
Task 6: Configure the User Profile Synchronization Service Application application
instance to support NetBIOS domain names
2. In the Administrator: SharePoint 2013 Management Shell command window, run the following
command:
$upsa = Get-SPServiceApplication | where {$_.DisplayName -eq "Contoso UPSA"}
3. In the command window, run the following command:
$upsa.NetBiosDomainNamesEnabled = $true
$upsa.Update()
Task 7: Start the User Profile Synchronization Service service
1. Return to Internet Explorer displaying the Central Administration website.
2. Click System Settings.
3. On the System Settings page, click Manage services on server.
4. Locate the User Profile Service service, and then in that row click Start.
5. Locate the User Profile Synchronization Service service, and then in that row click Start.
6. On the User Profile Synchronization Service page, in the Select the User Profile Application list,
verify that Contoso UPSA is selected, in the Password box type Pa$$w0rd, in the Confirm
password box type Pa$$w0rd, and then click OK.
7. Refresh the Services on Server page, and then check the status of the User Profile Synchronization
Service service. Periodically repeat this step until the status changes to Started. Do not continue until
the service status changes to Started. This may take up to ten minutes.
Task 8: Configure a connection to Active Directory
3. On the Manage Service Applications page, click Contoso UPSA (you must click the name in the
User Profile Service Application row, not the User Profile Service Application Proxy row).
4. On the Manage Profile Service page, under Synchronization, click Configure Synchronization
Settings.
5. On the Configure Synchronization Settings page, under Synchronization Entities, verify that
Users and Groups is selected.
6. Under Synchronization Options, verify that Use SharePoint Profile Synchronization is selected,
and then click OK.
Connections.
8. On the Synchronization Connections page, click Create New Connection.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
9. On the Add new synchronization connection page, in the Connection Name text box, type
Contoso Domain.
10. Under Connection Settings, in the Forest name text box, type contoso.com.
11. In the Account name text box, type CONTOSO\SPFarm.
12. In the Password text box, type Pa$$w0rd. In the Confirm password text box, type Pa$$w0rd.
13. Under Containers, click Populate Containers. Wait for the containers to load before you proceed to
the next step.
14. Click Select All, and then click OK.
Task 9: Configure profile synchronization
Timer Job.
5. On the Edit Timer Job page, click Enable.
9. On the Manage Profile Service page, under Synchronization, click Start Profile Synchronization.
10. On the Start Profile Synchronization page, click Start Full Synchronization, and then click OK.
11. On the Manage Profile Service page, under Profile Synchronization Settings, verify that the
Profile Synchronization Status is Synchronizing. You may need to refresh the page. Periodically
refresh the page and do not continue until the status returns to Idle.
Task 10: Test profile synchronization
1. On the Manage Profile Service page, click Manage User Profiles.
2. On the Manage User Profiles page, in the Find profiles box, type Jim, and then click Find.
3. Under Account name, click CONTOSO\Jim, and then click Edit My Profile.

Results: After completing this exercise, you should have configured two-way profile synchronization.

Exercise 2: Configuring My Sites
Task 1: Configure a DNS record for the My Site web application
1. Switch to the 20332B-NYC-DC-05 virtual machine. If you are not already logged on, log on as
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-5
3. In DNS Manager, expand Forward Lookup Zones, right-click Contoso.com, and then click New
Host (A or AAAA).
4. In the New Host dialog box, in the Name box, type mysites, in the IP address box, type
5. In the confirmation message box, click OK, and then click Done.
Task 2: Create a service account for the My Sites web application application pool
4. In the Create User dialog box, in the Full name box, type My Sites Application Pool.
5. In the User UPN logon box, type MySitesAppPool. Verify that the User SamAccountName logon
box is automatically populated with the corresponding user name.
3. In Central Administration, click Security, and then on the Security page, under General Security,
click Configure managed accounts.
5. On the Register Managed Account page, in the User name text box, type
CONTOSO\MySitesAppPool, in the Password text box, type Pa$$w0rd, and then click OK.
Task 4: Create and configure a new web application to host My Sites
4. In the Create New Web Application dialog box, under IIS Web Site, in the Name text box, type
MySites - 80.
5. In the Port box, type 80.
6. In the Host Header text box, type mysites.contoso.com.
7. Under Application Pool, in the Application pool name text box, type SharePointMySites - 80.
8. In the Configurable list, click CONTOSO\MySitesAppPool, and then click OK.
10. Click MySites - 80, and then on the ribbon, click Managed Paths.
11. In the Define Managed Paths dialog box, under Add a New Path, in the Path text box, type
personal.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
12. Ensure Wildcard inclusion is selected in the Type list, click Add Path, and then click OK.
Task 5: Create a My Site host site collection
http://mysites.contoso.com is selected. If it is not currently selected, click the current web
application, click Change Web Application, and then click MySites 80.
4. Under Title and Description, in the Title text box, type MySite Host.
5. In the URL list, click /.
6. Under Template Selection on the Enterprise tab, click My Site Host.
Task 6: Enable Self-Service Site Creation for the My Site host web application
2. Click Manage web applications.
3. On the Web Applications Management page, click MySites 80, and the on the ribbon, click Self-
Service Site Creation.
4. In the Self-Service Site Creation Management dialog box, under Site Collections, click On.
5. Under Start a Site, under The Start a Site link should, select Be hidden from users, and then click
OK.
Task 7: Configure My Site settings for the User Profile Service Application service
application instance
4. On the Manage Profile Service page, under My Site Settings, click Setup My Sites.
5. On the My Site Settings page, in the My Site Host Location box, type
http://mysites.contoso.com, and then click OK.
Task 8: Enable the User Profile Service Application - Activity Feed Job timer job
1. Click Monitoring.
2. On the Monitoring page, under Timer Jobs, click Review job definitions.
3. On the Job Definitions page, click Contoso UPSA Activity Feed Job.
4. On the Edit Timer Job page, if the timer job is disabled, click Enable (if the timer job is already
enabled the page will contain a Disable button instead of an Enable button).
5. Click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-7
Task 9: Test My Site creation by using a non-administrative user account
1. Switch to the 20332B-NYC-DB-05 virtual machine and log on as jim@contoso.com with the
password Pa$$w0rd.
2. On the Start screen, click Internet Explorer.
3. In Internet Explorer, browse to http://sharepoint.contoso.com, in the Windows Security dialog
box, in the User name box, type jim, in the Password box, type Pa$$w0rd, and then click OK.
4. On the SharePoint site, click Sites. In the Windows Security dialog box, in the User name box, type
jim, in the Password box, type Pa$$w0rd, and then click OK.
5. In the Get the most out of SharePoint dialog box, click OK.

Results: After completing this exercise, you should have configured My Sites and tested My Site creation
for a non-administrative user.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring Community Sites
Exercise 1: Creating a Community Site Infrastructure
Task 1: Configure a DNS record for the community site portal
3. In DNS Manager, expand Forward Lookup Zones, right-click Contoso.com, and then click New
Host (A or AAAA).
4. In the New Host dialog box, in the Name text box, type community, in the IP address box, type
5. In the confirmation message box, click OK, and then click Done.
Task 2: Create a service account for the community portal web application
application pool
4. In the Create User dialog box, in the Full name box, type Community Application Pool.
5. In the User UPN logon box, type CommunityAppPool. Verify that the User SamAccountName
3. In Central Administration, click Security, and then on the Security page, under General Security,
click Configure managed accounts.
5. On the Register Managed Account page in the User name box, type
CONTOSO\CommunityAppPool, in the Password box, type Pa$$w0rd, and then click OK.
Task 4: Create and configure a new web application for the community site portal
4. On the Create New Web Application dialog box, under IIS Web Site, in the Name text box, type
Community - 80.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-9
5. In the Port text, box type 80.
6. In the Host Header text box, type community.contoso.com.
7. Under Application Pool, in the Application pool name text box, type SharePointCommunity - 80.
8. In the Configurable list, click CONTOSO\CommunityAppPool, and then click OK.
10. Click Community - 80, and then on the ribbon, click Managed Paths.
11. In the Define Managed Paths dialog box, under Add a New Path, in the Path text box, type
forums.
12. Ensure Wildcard inclusion is selected in the Type list, click Add Path, and then click OK.
13. Click Community - 80, and then on the ribbon, in the General Settings list, click Outgoing E-mail.
14. In the Web Application Outgoing E-Mail Settings dialog box, in the Outbound SMTP server text
box, type mail.contoso.com.
15. In the From address text box, type community@contoso.com.
16. In the Reply-to address text box, type donotreply@contoso.com, and then click OK.
Task 5: Create a site collection for the community portal
http://community.contoso.com is selected. If it is not currently selected, click the current web
application, click Change Web Application, and then click Community - 80.
4. Under Title and Description, in the Title text box, type Community Portal.
5. In the URL list, click /.
6. Under Template Selection on the Enterprise tab, click Community Portal.
7. Under Primary Site Collection Administrator, in the User name text box, type
Task 6: Create community sites for the Finance and Sales departments
2. On the Create Site Collection page, under Web Application, verify that
3. Under Title and Description, in the Title text box, type Finance Forum.
4. Under URL, in the list, click /forums/, and then in the text box, type Finance.
5. Under Template Selection, on the Collaboration tab, click Community Site.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
10. Under Title and Description, in the Title box, type Sales Forum.
11. Under URL, in the list, click /forums/, and then in the text box, type Sales.
12. Under Template Selection, on the Collaboration tab, click the Community Site template.
5. In the Create User dialog box, in the Full name text box, type Search Service Admin Web Service
Application Pool.
6. In the User UPN logon text box, type SearchAdminAppPool. Verify that the User
SamAccountName logon box is automatically populated with the corresponding user name.
10. In the Create User dialog box, in the Full name text box, type Search Service Query Web Service
Application Pool.
11. In the User UPN logon box, type SearchQueryAppPool. Verify that the User SamAccountName
12. In the Password text box, type Pa$$w0rd, and then in the Confirm password box, type Pa$$w0rd.
15. In the Create User dialog box, in the Full name box, type Search Service Account.
16. In the User UPN logon text box, type SearchService. Verify that the User SamAccountName logon
box is automatically populated with the corresponding user name.
17. In the Password text box, type Pa$$w0rd, and then in the Confirm password text box, type
Pa$$w0rd.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-11
2. On the Central Administration page, click Security, and then on the Security page, under General
Security, click Configure managed accounts.
CONTOSO\SearchAdminAppPool, in the Password text box, type Pa$$w0rd, and then click OK.
CONTOSO\SearchQueryAppPool, in the Password text box, type Pa$$w0rd, and then click OK.
CONTOSO\SearchService, in the Password text box, type Pa$$w0rd, and then click OK.
Task 9: View the community sites on the community portal
1. In Internet Explorer, click the New Tab tab, in the address bar, type
http://community.contoso.com, and then press Enter.
2. In the Windows Security dialog box, in the User name text box, type administrator, in the
Password box type Pa$$w0rd, and then click OK.
3. On the Community Portal page verify that the page indicates that something went wrong.
4. Click the Managed Accounts tab to return to the Central Administration website.
7. On the Manage Service Applications page, on the ribbon, click New, and then click Search Service
Application.
8. In the Create New Search Service Application dialog box, in the Name text box, type Contoso
Search.
9. In the Search Service Account list, click CONTOSO\SearchService.
10. Under Application Pool for Search Admin Web Service, in the Application pool name text box,
type SearchAdminAppPool.
11. In the Configurable list, click CONTOSO\SearchAdminAppPool.
12. Under Application Pool for Search Query and Site Settings Web Service, in the Application pool
name text box, type SearchQueryAppPool.
13. In the Configurable list, click CONTOSO\SearchQueryAppPool, and then click OK.
14. In the Manage Search Topology dialog box, click OK.
15. Refresh the Manage Service Applications page, and then click Contoso Search (you must click the
name in the Search Service Application row, not the Search Service Application Proxy row).
16. On the Contoso Search: Search Administration page, click Content Sources.
17. On the Contoso Search: Manage Content Sources page, on the Local SharePoint sites list, click
Start Full Crawl, and then click OK. If the Local SharePoint sites content source does not appear in
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
the list of content sources, you should periodically refresh the page. It may take several minutes for
SharePoint to populate the content sources list after you create the Search Service Application
18. Verify that the status of the Local SharePoint sites content source has changed to Starting.
19. Periodically refresh the page and view the status. Do not continue until the status returns to Idle.
20. Click the Community Portal tab, and then refresh the page. Verify that the page now lists the
Finance Forum and Sales Forum community sites.
Task 10: Create discussions on the Finance community site
1. On the Community Portal site, click Finance Forum.
2. On the Finance Forum page, click new discussion.
3. On the new item page, in the Subject text box, type New Site.
4. In the Body text box, type We now have a new forum site to discuss anything related to the
finance department. Please use this site to ask questions or make suggestions., and then click
Save.
5. On the Finance Forum page, click new discussion.
6. On the new item form, in the Subject box type Meal?.
7. In the Body text box, type Are you interested in a departmental meal on Friday?, select the
Question check box, and then click Save.

Results: After completing this exercise, you should have created a community site infrastructure, including
a community portal and multiple community sites.

Exercise 2: Configuring Community Site Participation
Task 1: Enable access requests for the Finance community site
2. On the Finance Forum site, click Settings, and then click Site settings.
3. On the Site Settings page, under Users and Permissions, click Site permissions.
4. On the Permissions: Finance Forum page, on the ribbon, click Access Request Settings.
5. In the Access Requests Settings dialog box, ensure Allow access requests is selected, in the text
box type financesiteadmin@contoso.com, and then click OK.
account
1. Switch to the 20332B-NYC-DB-05 virtual machine. If you are not already logged on, log on as
3. In Internet Explorer, browse to http://community.contoso.com/forums/finance.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-13
4. In the Windows Security dialog box, in the User name text box, type jim, in the Password text box,
type Pa$$w0rd, and then click OK. Verify that you are denied access, but have an option to request
access to the site.
5. In the text box, type I would like to participate in departmental discussions, and then click Send
request.
Task 3: Approve an access request for a community site
2. On the Finance Forum site, click Settings, and then click Site settings.
3. On the Site Settings page, click Access requests and invitations.
4. On the Access Requests page, next to the request from Jim Corbin, click the ellipsis (), and then
click APPROVE.
account
1. Switch to the 20332B-NYC-DB-05 virtual machine. If you are not already logged on, log on as
4. In the Windows Security dialog box, in the User name text box, type jim, in the Password text box
type Pa$$w0rd, and then click OK. Verify that you now have access to the site.
5. On the Finance Forum site, click Join this community.
Task 5: Enable auto-approval and reporting of offensive content for the Finance
community site
2. On the Finance Forum site, click Home.
3. On the Finance Forum home page, under Community tools, click Community settings.
4. On the Community Settings page, select Enable auto-approval, select Enable reporting of
offensive content, and then click OK.
5. Click Settings, and then click Site settings.
6. On the Site Settings page, click People and groups.
7. On the People and Groups page, click Finance Forum Visitors.
8. On the Finance Forum Visitors page, click New.
9. In the Share 'Finance Forum' dialog box, in the Enter names, email addresses, or 'Everyone'. text
box, type Everyone.
10. Click SHOW OPTIONS, clear Send an email invitation, and then click Share.
Task 6: Use auto-approval to gain access to the Finance community site with a non-
administrative user account
1. Switch to the 20332B-NYC-DC-05 virtual machine. If you are currently logged on, log off.
2. Log on as ray@contoso.com with the password Pa$$w0rd.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
5. In the Windows Security dialog box, in the User name text box, type ray, in the Password text box,
type Pa$$w0rd, and then click OK. Verify that you have access to the site.
6. On the Finance Forum site, click Meal?.
7. On the topic page, verify that you have the option to Like the post, but that you do not have the
option to Reply.
8. Click Home.
9. On the Finance Forum home page, click Join this community.
10. On the Finance Forum site, click Meal?.
11. On the topic page, verify that you now have both the option to Like the post, and the option to
Reply to the post.
Task 7: Gift badges to community site users
2. Click Home.
3. On the Finance Forum home page, click Create badges.
4. On the Badges page, click new item.
5. On the new item page, in the Badge Name text box, type Site Admin, and then click Save.
6. Click Home.
7. On the Finance Forum home page, click Assign badges to members.
8. On the Community Members page, select the row for Jim.
9. On the ribbon, on the MODERATION tab, click Give Badge.
10. In the Gifted Badge list, click Expert, and then click Save.
11. On the Community Members page, select the row for the Administrator, and then on the ribbon,
on the MODERATION tab, click Give Badge.
12. In the Gifted Badge list, click Site Admin, and then click Save.
Task 8: Review the default reputation settings
1. Click Home.
2. On the Finance Forum home page, click Reputation settings.
3. On the Community Reputation Settings page, review the default reputation settings and then click
Cancel.
Task 9: Create categories and assign a category to an existing discussion
1. Click Home.
2. On the Finance Forum home page, click Create categories.
3. On the Categories page, click new item.
4. On the new item form, in the Category Name box, type Chat.
5. In the Description box, type Non-work related discussions, and then click Save.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L5-15
6. Click Home.
7. On the Finance Forum home page, click Manage discussions.
8. On the Discussions List page, locate the discussions with the Title Meal? In that row, click the ellipsis
(), and then click Edit Item.
9. On the edit item page, in the Category list, click Chat, and then click Save.
Task 10: Moderate offensive content on the finance community site
1. Switch to the 20332B-NYC-DC-05 virtual machine.
2. In the Add a reply box, type I do not care about your meal I came to the last one and it was
boring!, and then click Reply.
3. Close all open windows on this virtual machine.
4. Switch to the 20332B-NYC-DB-05 virtual machine.
5. Click the Meal? discussion.
6. Locate the reply left by Ray, and next to that reply, click the ellipsis (), and then click Report to
moderator.
7. In the Report offensive content dialog box, in the text box, type I find this response offensive,
and then click Report.
9. Click Home.
10. On the Finance Forum home page, click Review reported posts.
11. On the Reported Posts page, select the post.
12. On The Community Moderation View page, on the ribbon, click Edit Post.
13. On the Community Moderation Edit page, replace the text in the Body text box with [OFFENSIVE
CONTENT REMOVED], and then click Save.
14. On the Finance Forum home page, click Review reported posts.
15. On the Reported Posts page, select the post.
16. On the ribbon, click Dismiss Report.
20. Refresh the Meal? page, and then verify that the offensive message has been replaced with the
edited message.

Results: After completing this exercise, you should have configured community site participation, by
making it easy for users to access a community site, and you should have used community site features to
ensure the site is used properly.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L6-1
Module 6: Enabling Productivity and Collaboration
Lab A: Configuring Project Sites
Exercise 1: Creating Project Sites
1. Start the 20332B-NYC-DC-06 virtual machine. Wait for the virtual machine to display the logon, and
then wait a further five minutes before you proceed to the next step.
Pa$$w0rd.
6. On the Central Administration web site, under Application Management, click Manage web
applications.
7. Click SharePoint - sharepoint.contoso.com:80, and then on the ribbon, click Managed Paths.
8. In the Define Managed Paths dialog box, under Add a New Path, in the Path box, type projects.
9. In the Type list, ensure Wildcard inclusion is selected, click Add Path, and then click OK.
Task 2: Use Central Administration to create a site collection in the
sharepoint.contoso.com web application
2. On the Application Management page, under Site Collections, click Create site collections.
http://sharepoint.contoso.com is selected. If it is not currently selected, click the current web
application, click Change Web Application, and then click SharePoint -
sharepoint.contoso.com80.
4. Under Title and Description, in the Title box, type Project 1.
5. Under Web Site Address, in the URL drop-down list, click /projects/, and then in the text box, type
p1.
6. Under Template Selection, click Project Site.

Results: After completing this exercise, you should have created a project site.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 2: Configuring Project Sites
Task 1: Review the default project site
2. In Internet Explorer, browse to http://sharepoint.contoso.com/projects/p1.
4. Review the default project site. Notice that it includes a project summary, with a project timeline, a
document library, a task list, and a calendar.
Task 2: Add tasks to the project timeline
1. Under Project Summary, click Edit.
2. In the Task Name box, type Product Design.
3. Click the Due Date box, click the calendar, and then click the date two weeks from the current date.
4. In the Assigned To box, type jim@contoso.com.
5. On a new line, click the Task Name box.
6. In the The first one is on us dialog box, click Close.
7. In the task list, next to Product Design, click the ellipsis ().
8. In the Product Design dialog box, click the ellipsis (), and then click Edit Item.
9. On the Tasks - Product Design page, click the Start Date box, click the calendar, click the current
date, and then click Save.
11. In the Task Name box, type Proof of Concept.
12. In the Proof of Concept row, click the Due Date box, click the calendar, and then click the date
three weeks from the current date.
13. In the Assigned To box, type administrator@contoso.com.
15. In the task list, next to Proof of Concept, click the ellipsis ().
16. In the Proof of Concept dialog box, click ADD TO TIMELINE.
17. In the task list, next to Proof of Concept, click the ellipsis ().
18. In the Proof of Concept dialog box, click the ellipsis (), and then click Edit Item.
19. On the Tasks - Proof of Concept page, click the Start Date box, click the calendar, click the date
one week from the current date, and then click Save.
20. On the Tasks page, click Stop, and then click Home.
21. On the Home page, verify that the Product Design and Proof of Concept tasks appear on the
project timeline.
22. On the Project Summary Web Part, click ADD TASK.
23. On the Tasks - New Item page, in the Task Name box, type Kick Off Meeting.
24. Next to Start Date, click the calendar, and then click the current date.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L6-3
25. Next to Due Date, click the calendar, and then click the current date.
26. In the Assigned To box, type Project 1 Members, and then click Save.
Task 3: Customize the display of the project site
1. On the Project Summary Web Part, click the Proof of Concept task.
2. On the ribbon, on the TIMELINE tab, click Display as Callout.
3. Click Settings, and then click Edit page.
4. Point to the Get started with your site Web Part, click the Get started with your site Web Part
menu drop-down arrow, and then click Delete.
6. In the Top panel, click Add a Web Part.
7. In the Categories pane, ensure Apps is highlighted.
8. In the Parts pane, ensure Calendar is highlighted, and then click Add.
9. Point to the Calendar Web Part, click the Calendar Web Part Menu drop down arrow, and then
click Minimize.
10. In the Top pane, drag the Calendar Web Part under the Project Summary Web Part.
11. Point to the Calendar Web Part, click the Calendar Web Part menu drop-down arrow, and then click
Restore.
12. On the ribbon, on the PAGE menu, click Stop Editing.
Task 4: Add items to the project calendar
1. In the Calendar Web Part, click the current date, and then click Add.
2. In the Calendar - New Item dialog box, in the Title box, type Kick Off Meeting.
3. In the Category list, click Meeting.
4. Select the All Day Event check box, and then click Save.

Results: After completing this exercise, you should have customized and configured a project site.

Exercise 3: Engaging Project Teams
Task 1: Add a document to the project documents library
1. On the Documents Web Part, click new document.
2. In the Add a document dialog box, click Browse.
3. In the Choose File to Upload dialog box, browse to E:\Mod6, click Project Outline.docx, and then
click Open.
4. In the Add a document dialog box, click OK.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 2: Test the social integration features
1. On the Documents Web Part, next to Project Outline, click the ellipsis ().
2. In the Project Outline.docx dialog box, click FOLLOW.
3. In the Quick Launch, click Documents.
4. On the ribbon, on the LIBRARY tab, click Tags & Notes.
5. In the Documents - All Documents dialog box, on the Note Board tab, in the box, type Added a
project outline document. I will add to this during our kick off meeting., and then click Post.
6. Close the Documents - All Documents dialog box.
7. On the ribbon, click FOLLOW.
8. On the ribbon, click SHARE.
9. In the SHARE 'Project 1' dialog box, in the Enter names, email addresses, or 'Everyone' box, type
jim@contoso.com; toni@contoso.com; anat@contoso.com;, and then click Share.
12. On the Central Administration web site, click Monitoring.
14. On the Job Definitions page, click Contoso UPSA - Activity Feed Job.
15. On the Edit Timer Job page, click Run Now.
16. In Internet Explorer, browse to http://mysites.contoso.com.
18. Verify that the Newsfeed includes messages which indicate you are now following the Project 1 site,
and the Project Outline.docx document.
Note: If the newsfeed displays the message We're still collecting the latest news. You
may see more if you try again a little later. on the Start screen, type SharePoint Management
Shell, and then press Enter. In the command window, run the following commands:
Use-CacheCluster
Remove-SPDistributedCacheServiceInstance
Add-SPDistributedCacheServiceInstance
Restart-CacheCluster
Refresh the newsfeed page. You may need to wait several minutes before the page correctly
displays the newsfeed.
19. In the Start a conversation box, type @[Jim Corbin] I might be late for the #kickoffmeeting, and
then click Post.
20. Switch to the 20332B-NYC-DB-06 virtual machine. Log on as CONTOSO\Jim with the password
Pa$$w0rd.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L6-5
22. In Internet Explorer, browse to http://mysites.contoso.com.
23. In the Windows Security dialog box, in the User name box, type Jim, in the Password box, type
Pa$$w0rd, and then click OK.
24. On the Newsfeed page, click Mentions.
25. Verify that the message from Administrator appears in the list of posts.
Task 3: Configure the SharePoint farm for task propagation
1. Click Tasks.
2. On the My Tasks page, verify that no tasks currently appear in your task list, and that a warning icon
appears next to the text which indicates when the task list was last updated.
5. On the Central Administration website, under Application Management, click Manage service
applications.
6. On the Manage Service Applications page, click New, and then click Work Management Service
Application.
7. In the Create New Work Management Service dialog box, in the Name box, type Contoso Work
Management.
8. Under Application Pool, click Use existing application pool, in the Use existing application pool
list, click ContosoServices, and then click OK.
9. Under Central Administration, click System Settings.
10. On the System Settings page, under Servers, click Manage services on server.
11. On the Services on Server page, in the Work Management Service row, click Start.
13. In Internet Explorer, refresh the page. Verify that the Product Design task now appears in the task
list. You may need to wait while SharePoint retrieves your tasks for the first time. If after refreshing the
page SharePoint still indicates that there is a problem retrieving your tasks, wait for a few minutes and
then refresh the page.

Results: After completing this exercise, you should have used the social integration features on a project
site to make the site more engaging for team members.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring Workflow
Exercise 1: Configuring Windows Azure Workflow and SharePoint
Workflow Services
Task 1: Configure the DNS settings for workflow services
3. In DNS Manager, expand Forward Lookup Zones, click Contoso.com, right-click Contoso.com, and
then click New Host (A or AAAA).
4. In the New Host dialog box, in the Name box, type workflow, in the IP address box, type
7. Close DNS Manager.
Task 2: Create a service account for workflow services
4. In the Create User dialog box, in the Full name box, type Workflow Services.
5. In the User UPN logon box, type workflowservices.
6. Verify that the User SamAccountName logon boxes have automatically populated with the
8. Click Other password options, select the Password never expires and User cannot change
9. Close Active Directory Administrative Center.
11. On the Start screen, type Local Users, click Settings, and then press Enter.
12. In lusrmgr - [Local Users and Groups (Local)], click Groups, and then double-click IIS_IUSRS.
13. In the IIS_IUSRS Properties dialog box, click Add.
names to select box, type workflowservices, then click OK.
15. In the IIS_IUSRS Properties dialog box, click OK.
16. Close lusrmgr - [Local Users and Groups (Local)].
17. On the Start screen, type %TEMP%, and then press Enter.
18. In the Temp folder, next to the address bar, click Up to "Local".
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L6-7
19. In the Local folder, right-click Temp, and then click Properties.
20. In the Temp Properties dialog box, on the Security tab, click Edit.
21. In the Permissions for Temp dialog box, click Add.
names to select box, type workflowservices, and then click OK.
23. In the Permissions for Temp dialog box, click OK.
24. In the Temp Properties dialog box, click OK.
25. Close File Explorer.
Task 3: Disable loopback checking for the workflow.contoso.com domain
1. On the Start screen, type regedit, and then press Enter.
2. In Registry Editor, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand CurrentControlSet,
expand Control, and then expand Lsa.
3. Under Lsa, click MSV1_0, and then double-click BackConnectionHostNames.
4. In the Edit Multi-String dialog box, in the Value data box, on a new line, type
workflow.contoso.com, and then click OK.
5. If a Warning dialog box appears, click OK.
6. On the Start screen, type Command Prompt, and then press Enter.
iisreset /noforce
Task 4: Use the Workflow Configuration Wizard to configure workflow services
1. On the Start screen, type Workflow Manager Configuration, and then press Enter.
2. In Workflow Manager Configuration Wizard, on the Welcome page, click Configure Workflow
Manager with Default Settings (Recommended).
3. On the New Farm Configuration page, in the SQL SERVER INSTANCE box, type NYC-DB1.
4. In the USER ID box, type workflowservices@contoso.com.
5. In the PASSWORD box, type Pa$$w0rd.
6. Select the Allow Workflow management over HTTP on this computer check box.
7. In the Certificate Generation Key and CONFIRM CERTIFICATE GENERATION KEY boxes, type
Pa$$w0rd, and then click Next.
8. On the Summary page, click Apply.
9. On the Configuration progress page, when the configuration is complete, click Close.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 5: Use PowerShell to associate the workflow service with the project site
2. At the command prompt, type Register-SPWorkflowService -SPSite
http://sharepoint.contoso.com/projects/p1 -WorkflowHostUri
http://workflow.contoso.com:12291 -AllowOAuthHttp, and then press Enter.

Results: After completing this exercise, you should have configured Windows Azure Workflow, and
associated the Workflow Services instance with a SharePoint project site.

Exercise 2: Creating and Testing a Workflow
Task 1: Use SharePoint Designer to create a new workflow
1. On the Start screen, type SharePoint Designer, and then press Enter.
2. In SharePoint Designer, click Open Site.
3. In the Open Site dialog box, in the Site name box, type
http://sharepoint.contoso.com/projects/p1, and then click Open.
5. Under Navigation, click Workflows.
6. On the WORKFLOWS tab, click List Workflow, and then click Tasks.
7. In the Create List Workflow - Tasks dialog box, in the Name box, type Task Complete, in the
Platform Type list, click SharePoint 2013 Workflow, and then click OK.
8. On the WORKFLOW tab, click Condition, and then click If any value equals value.
9. In the workflow designer, in the text If value equals value, click the first instance of value.
10. Click the Define workflow lookup button.
11. In the Define Workflow Lookup dialog box, in the Field from source list, click Task Status, and
then click OK.
12. Click value, and then click Completed.
13. Click the box under the If statement.
14. On the ribbon, click Action, and then click Log to History List.
15. Click message, type Task completed, and then press Enter.
16. Right-click (Insert go-to actions with conditions for transitioning to the stage), and then click Go
to a stage.
17. Click a stage, and then click End of Workflow.
18. On the ribbon, click Workflow Settings.
19. Under Start Options, select the Start workflow automatically when an item is created, and Start
workflow automatically when an item is changed check boxes.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L6-9
Task 2: Test the workflow
1. In Internet Explorer, browse to http://sharepoint.contoso.com/projects/p1.
3. On the Project 1 site, click Tasks.
4. On the Tasks page, next to Kick Off Meeting, click the ellipsis ().
5. In the Kick Off Meeting dialog box, click the ellipsis (), and then click Edit Item.
6. On the Tasks - Kick Off Meeting page, in the % Complete box, type 100, and then click Save.
7. In SharePoint Designer, in the Navigation pane, click Workflows, and then double-click Task
Complete.
8. On the Task Complete page, under Customization, click Open history list.
9. Under List Information, click the Web Address.
11. Verify that the Workflow History list contains one item, with a Description of Task completed.

Results: After completing this exercise, you should have used SharePoint Designer to create a SharePoint
2013 workflow.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L7-1
Module 7: Planning and Configuring Business Intelligence
Lab A: Configuring Excel Services
Exercise 1: Provisioning Excel Services
1. Start the 20332B-NYC-DC-07 virtual machine. Wait for the logon screen, then wait a further five
minutes before proceeding to the next step.
2. Start the 20332B-NYC-DB-07 virtual machine and wait for the logon screen before you continue.
3. Start the 20332B-NYC-SP-07 virtual machine and wait for the logon screen before you continue.
Pa$$w0rd.
7. In the Windows PowerShell Credential dialog box, in the User name box, type
CONTOSO\ExcelSrv, in the Password box, type Pa$$w0rd, and then click OK.
Task 2: Grant the service account access to content databases
1. In the SharePoint 2013 Management Shell, at the command prompt, type the following command,
and then press Enter:
$webapp = Get-SPWebApplication -Identity http://sharepoint.contoso.com
$webapp.GrantAccessToProcessIdentity("CONTOSO\ExcelSrv")
Task 3: Start the Excel Calculation Services service
3. On the Services on Server page, in the Excel Calculation Services row, click Start.
Task 4: Create a new Excel Services service application instance
Management.
applications.
3. On the ribbon, on the New menu, click Excel Services Application.
4. In the Create New Excel Services Application dialog box, in the Name box, type Contoso Excel
Services.
5. Under Application Pool, ensure Create new application pool is selected.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6. In the Application pool name box, type ContosoExcelServices.
7. In the Configurable list, click CONTOSO\ExcelSrv, and then click OK.
8. Close all Internet Explorer windows.

Results: After completing this exercise, you should have provisioned an Excel Services service application.

Exercise 2: Configuring External Data Access
Task 1: Configure an unattended service account
3. In the list of service applications, click Contoso Excel Services, and then on the ribbon, click
Manage.
4. On the Manage Excel Services Application page, click Global Settings.
5. On the Excel Services Application Settings page, under Unattended Service Account, ensure
Create a new Unattended Service Account is selected.
6. In the User Name: (Domain\UserName) box, type CONTOSO\DataAccess.
7. In the Password, and Confirm Password boxes, type Pa$$w0rd, and then click OK.
8. On the Quick Launch navigation menu, click Application Management.
9. Under Service Applications, click Manage service applications.
11. Notice that Excel Services has created a Secure Store target application for the unattended service
account.
Task 2: Grant database permissions to the unattended service account
1. Log on to the 20332B-NYC-DB-07 machine as administrator@contoso.com with password
Pa$$w0rd.
2. On the Start screen, type SQL Server Management Studio, and then press Enter.
3. In the Connect to Server dialog box, in the Server type list, click Analysis Services.
4. In the Server name box, type NYC-DB1, and then click Connect.
5. In the Object Explorer pane, expand Databases, and then expand AWSalesMD.
6. Right-click Roles, and then click New Role.
7. In the Create Role dialog box, in the Role name box, type Consumers.
8. Under Set the database permissions for this role, select the Process database and Read
definition check boxes.
9. In the Select a page pane, click Membership, and then click Add.
10. In the Select Users or Groups dialog box, click Locations.
11. In the Locations dialog box, expand Entire Directory, click Contoso.com, and then click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L7-3
12. In the Select Users, Service Accounts, or Groups dialog box, in the Enter the object names to
select box, type CONTOSO\DataAccess, and then click OK.
13. In the Select a page pane, click Cubes.
14. In the Access column, click None, and then in the drop-down list, click Read.
15. On the Create Role dialog box, click OK.
16. Close SQL Server Management Studio.

Results: After completing this exercise, you should have configured an unattended service account for
Excel Services.

Exercise 3: Configuring Data Connections
Task 1: Create a data connection library
1. Switch to the 20332B-NYC-SP-07 virtual machine. If you are not already logged on, log in as
2. On the Start screen, type Internet Explorer, and then press Enter.
4. If the Windows Security dialog box appears, in the User name box, type CONTOSO\Administrator,
in the Password box, type Pa$$w0rd, and then click OK.
5. On the Settings menu, click Add an app.
6. On the Your Apps page, in the Find an app box, type Data Connection, and then press Enter.
7. Click Data Connection Library.
8. On the Adding Data Connection Library page, in the Name box, type DataConnections, and then
click Create.
Task 2: Configure Excel Services to trust the data connection library
3. In the list of service applications, click Contoso Excel Services, and then on the ribbon, click
Manage.
4. On the Manage Excel Services Application page, click Trusted Data Connection Libraries.
5. On the Excel Services Application Trusted Data Connection Libraries page, click Add Trusted
Data Connection Library.
6. In the Address box, type http://sharepoint.contoso.com/dataconnections.
7. In the Description box, type Data connection files for the Contoso intranet portal, and then click
OK.
8. Leave Internet Explorer open for the next task.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Configure and export the connection file
2. In File Explorer, browse to E:\Starter, and then double-click Sales Analysis.xlsx.
3. If the SECURITY WARNING banner appears, click Enable Content.
4. On the DATA tab, click Connections.
5. In the Workbook Connections dialog box, click AWSalesMD Sales, and then click Properties.
6. In the Connection Properties dialog box, on the Definition tab, click Authentication Settings.
7. In the Excel Services Authentication Settings dialog box, click None, and then click OK.
Note: Setting the data connection account to None ensures that Excel Services uses the unattended
service account to connect to the data source.
8. In the Connection Properties dialog box, on the Definition tab, click Export Connection File.
9. In the File Save dialog box, browse to E:\Starter, and then click Save.
10. Switch back to Internet Explorer.
11. In the address bar, type http://sharepoint.contoso.com/DataConnections, and then press Enter.
12. In the Windows Security dialog box, in the User name box, type CONTOSO\Administrator, in the
13. On the DataConnections page, click new item.
15. In the Choose File to Upload dialog box, browse to E:\Starter, click AWSalesMD Sales.odc, and
then click Open.
17. In the DataConnections - AWSalesMD Sales.odc dialog box, click Save.
18. Switch back to Excel.
19. In the Connection Properties dialog box, on the Definition tab, click Browse.
20. In the Select Data Source dialog box, in the File name box, type
http://sharepoint.contoso.com/DataConnections/AWSalesMD%20Sales.odc, and then click
Open.
22. In the Connection Properties dialog box, on the Definition tab, select the Always use connection
file check box, and then click OK.
23. In the Workbook Connections dialog box, click Close.
24. On the Category and Business Type slicers, click several items and verify that the workbook still
updates correctly.
25. Save and close the Sales Analysis.xlsx file.
Task 4: Test the Excel Services configuration
2. On the Contoso Intranet Portal home page, under Documents, click new document.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L7-5
4. In the Choose File to Upload dialog box, browse to E:\Starter, click Sales Analysis.xlsx, and then
click Open.
6. Under Documents, click Sales Analysis.
7. Verify that the browser window renders the workbook.
8. On the Category slicer, click Bikes.
9. In the Query and Refresh Data dialog box, click Yes.
10. Verify that the PivotChart and the PivotTable display updated values.
Note: The first update operation may take a few seconds to complete.
11. Click other items on the Category and Business Type slicers, and verify that the PivotChart and
PivotTable are updated accordingly.

Results: After completing this exercise, you should have configured Excel Services to trust a data
connection library and configured a workbook to use an external data connection file.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Configuring PowerPivot and Power
View for SharePoint
Exercise 1: Configuring PowerPivot for SharePoint
Task 1: Run the PowerPivot for SharePoint 2013 Configuration tool
1. On the 20332B-NYC-SP-07 virtual machine, on the Start screen, type PowerPivot for SharePoint
2013 Configuration, and then press Enter.
2. In the PowerPivot Configuration Tool dialog box, ensure Configure or Repair PowerPivot for
SharePoint is selected, and then click OK.
3. On the Configure or Repair PowerPivot for SharePoint page, in the Default Account Username
box, leave CONTOSO\Administrator unchanged. The default account is used to perform a range of
tasks such as provisioning service applications and deploying features.
4. In the Default Account Password box, type Pa$$w0rd.
5. In the PowerPivot Server for Excel Services box, type NYC-SP1\PowerPivot, and then click
Validate.
6. In the Task Validation dialog box, click OK.
7. In the navigation pane, click Create PowerPivot Service Application, in the Service Application
Name box, type Contoso PowerPivot Service Application.
8. In the Database Name box, type ContosoPowerPivotDB, and then click Validate.
10. In the navigation pane, click Create Unattended Account for DataRefresh, in the Unattended
Account User Name box, type CONTOSO\DataAccess.
11. In the Unattended Account Password box, type Pa$$w0rd, and then click Validate.
13. Click Run.
14. In the Warning dialog box, click Yes.
Note: The PowerPivot for SharePoint configuration process may take a few minutes to complete.
15. In the Task Configuration dialog box, click OK.
16. In the PowerPivot Configuration Tool window, click Exit.
Task 2: Grant database permissions to the unattended data refresh account
1. Switch to the 20332B-NYC-DB-07 machine. If you are not already logged on, log on as
3. In the Connect to Server dialog box, in the Server type list, click Database Engine.
5. In the Object Explorer pane, expand Security, right-click Logins, and then click New Login.
6. In the Login - New dialog box, in the Login name box, type CONTOSO\DataAccess.
7. In the Select a page pane, click User Mapping.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L7-7
8. Under Users mapped to this login, select the AWDataWarehouse check box.
9. Under Database role membership for: AWDataWarehouse, select the db_datareader check box,
and then click OK.
Task 3: Create a PowerPivot site collection
3. Under Application Management, click Create site collections.
4. On the Create Site Collection page, under Web Application, ensure
http://sharepoint.contoso.com/ is selected.
5. In the Title box, type PowerPivot Test Site.
6. In the Description box, type A test site for PowerPivot and Power View..
7. Under Web Site Address, under URL, in the text box, type power.
8. Under Template Selection, on the Collaboration tab, click PowerPivot Site.
10. On the Top-Level Site Successfully Created page, click
http://sharepoint.contoso.com/sites/power.
Task 4: Test the PowerPivot for SharePoint 2013 configuration
1. On the PowerPivot Test Site home page, on the Quick Launch navigation menu, click PowerPivot
Gallery.
2. On the ribbon, on the FILES tab, click Upload Document.
4. In the Choose File to Upload dialog box, browse to E:\Starter, click Marketing Analysis.xlsx, and
then click Open.
6. Reload the page periodically until SharePoint has generated snapshots of the workbook in a gallery
view.
7. On the ribbon, on the LIBRARY tab, in the Current View list, click Carousel.
8. Notice that SharePoint displays a snapshot of each worksheet in a carousel view.
9. On the ribbon, on the LIBRARY tab, in the Current View list, click Theater.
10. Notice that SharePoint displays a snapshot of each worksheet in a theater (or slideshow-style) view.
11. In the scrollbar at the bottom of the page, click the leftmost (Sheet1) icon, and then click the large
preview image above the scrollbar.
12. Verify that the browser window renders the workbook.
13. Click various items on the Marital Status, Gender, and Order Date slicers, and verify that the
PivotTable is updated. This confirms that PowerPivot for SharePoint is working correctly.
14. On the DATA menu, click Refresh All Connections.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
15. In the Query and Refresh Data dialog box, click Yes.
16. Verify that the data refresh completes without errors. This confirms that the unattended data refresh
account is able to retrieve data from the database server.
17. Click the browser back button to return to the PowerPivot Gallery page.
Task 5: Schedule a data refresh
1. In the gallery view, ensure that Sheet1 is selected, and then click Manage Data Refresh.
Note: The Manage Data Refresh button is displayed as a calendar icon in the top right corner of
the gallery view.
2. On the Manage Data Refresh: Marketing Analysis page, under Data Refresh, select the Enable
check box.
3. Notice that by default the data refresh is scheduled to run daily after business hours.
4. Under Schedule Details, select the Also refresh as soon as possible check box.
5. Under Credentials, ensure that Use the data refresh account configured by the administrator is
selected, and then click OK.
6. On the gallery view, click Manage Data Refresh.
7. Reload the page periodically until the Current Status shows Succeeded.

Results: After completing this exercise, you should have configured SharePoint to support PowerPivot
workbooks.

Exercise 2: Configuring Power View for SharePoint
Task 1: Install and start the SharePoint Reporting Services service
Install-SPRSService
Install-SPRSServiceProxy
Get-SPServiceInstance -all | where {$_.TypeName -like "SQL Server Reporting*"} |
Start-SPServiceInstance
Task 2: Register a managed account
CONTOSO\PowerView, in the Password box, type Pa$$w0rd, and then click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L7-9
Task 3: Create a Reporting Services service application
3. On the ribbon, on the New menu, click SQL Server Reporting Services Service Application.
4. In the Create SQL Server Reporting Services Service Application dialog box, in the Name box,
type Contoso SSRS.
5. Under Application Pool, ensure Create new application pool is selected.
6. In the Application pool name box, type ContosoSSRS.
7. In the Configurable list, click CONTOSO\PowerView.
8. In the Database server box, type NYC-SP1\PowerPivot.
9. In the Database name box, delete the existing text, and then type ContosoReportingDB.
10. Under Web Application Association, select the SharePoint - sharepoint.contoso.com80
(http://sharepoint.contoso.com/) check box, and then click OK.
11. When the service application has been successfully created, click OK.
Task 4: Activate the Power View Integration Feature
1. In the Internet Explorer address bar, type sharepoint.contoso.com/sites/power, and then press
Enter.
2. If you are prompted for credentials, log on as CONTOSO\Administrator with password Pa$$w0rd.
3. On the Settings menu, click Site settings.
4. On the Site Settings page, under Site Collection Administration, click Site collection features.
5. On the Site Collection Features page, in the Power View Integration Feature row, if the feature is
not already Active, click Activate.
Task 5: Create a Power View report
1. On the Quick Launch navigation menu, click PowerPivot Gallery.
2. On the gallery view, ensure that Sheet1 is selected, and then click Create Power View Report.
Note: The Create Power View Report button is displayed as a chart icon in the top right corner of
the gallery view. The Report Designer may take a few minutes to load.
3. In the Power View report, click Click here to add a title, and then type Sales Promotion Analysis.
4. On the ribbon, in the Show group, click Filters to hide the filters area.
5. In the Field List pane, expand Internet Sales, and then select the Revenue check box.
6. Expand Promotion, expand Sales_Promotion, and then select the Promotion_Type check box.
7. Expand Customer, and then select the Commute Distance check box.
8. On the ribbon, on the Visualizations drop-down list, click Clustered Bar. Resize the chart so it fills
the left half of the report.
9. Ensure that the clustered bar chart you just added is selected in the designer, and then in the Field
List pane, expand Date, expand Calendar_Date, and then drag the Year field to the TILE BY area.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Click each of the year headers in the report to view revenue by promotion type broken down by
commute distance for each year.
10. Click the blank area of the report on the right, and in the Field List pane, under Internet Sales, select
the Revenue check box.
11. Under Customer, expand Customers_By_Geography, and then select the Country check box.
12. On the ribbon, on the Visualizations drop-down list, click Pie. Resize the chart so it fills the top of
the right half of the report.
13. Click the blank area of the report on the right under the pie chart, and in the Field List pane, under
Internet Sales, select the Revenue check box.
14. Under Customer, select the Cars check box.
15. In the Fields area, on the Cars drop-down menu, click Do Not Summarize.
16. On the ribbon, on the Visualizations drop-down list, click Column. Resize the chart so it fills the
bottom of the right half of the report.
17. In the Commute Distance legend, click the colored square for the 0-1 Miles category, and note that
all of the charts are shaded to reflect the selected value.
18. Click each of the other Commute Distance legend values and note the shading in all charts.
19. Click the currently selected Commute Distance legend value again to remove the shading.
20. On the ribbon, on the File tab, click Save.
21. In the Save As dialog box, in the File name box, type MarketingView, and then click Save.
22. Click the browser back button. Notice that a thumbnail for the MarketingView report has been added
to the PowerPivot gallery.

Results: After completing this exercise, you should have configured SharePoint to create and render
Power View reports.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L8-1
Module 8: Planning and Configuring Enterprise Search
Lab A: Planning an Enterprise Search
Deployment
Exercise 1: Planning a Search Solution
1. Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen
before you proceed to the next step.
4. In the E:\Mod08\Starter folder, read the information in the Contoso Search Requirements.docx
file.
Task 2: Complete the SharePoint 2013 Search Planning worksheet
1. In the E:\Mod08\Starter folder, open and complete the worksheet in the SharePoint 2013 Search
Planning Worksheet.xlsx file, based on the information you have reviewed in Task 1.

Results: A completed SharePoint 2013 Search Planning worksheet.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Managing Search Relevance in
Exercise 1: Configuring a Thesaurus
Task 1: Test search limitations
4. Log on to the 20332B-NYC-SP-08 virtual machine as Contoso\Administrator with the password
Pa$$w0rd.
6. In the Internet Explorer address bar, type sharepoint.contoso.com/search, and then press Enter.
7. In the Windows Security dialog box, in the User name text box, type CONTOSO\Administrator, in
the Password text box, type Pa$$w0rd, and then click OK.
8. In the search text box, type Painkillers, and then press Enter. Notice that the search returns no
results.
9. In the search box, type Analgesics, and then press Enter. Notice that the search returns a datasheet.
10. In the search box, type Emergency aid, and then press Enter. Notice that the search returns no
results.
11. In the search box, type First aid, and then press Enter. Notice that the search returns a datasheet.
12. In the search box, type Indigestion remedy, and then press Enter. Notice that the search returns no
results.
13. In the search box, type Digestive health, and then press Enter. Notice that the search returns a
datasheet.
Task 2: Create a thesaurus file
1. On the desktop, click File Explorer.
2. In the File Explorer window, browse to E:\Mod08\Starter, right-click ContosoThesaurus.csv, point
to Open with, and then click Notepad.
3. Immediately after the line that reads Key,Synonym,Language, on a new line, add the following text:
Painkiller,Analgesic

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L8-3
4. Add the following text, using a new line for each comma-separated pair of values:
Analgesic,Painkiller
First aid,Emergency care
First aid,Emergency treatment
First aid,Emergency assistance
Emergency care,First aid
Emergency treatment,First aid
Emergency assistance,First aid
Indigestion,digestive health
Digestive health,indigestion
Indigestion remedy,Digestive health
Digestive health,Indigestion remedy
5. Save the file and close Notepad.
Task 3: Import a thesaurus file
$search = Get-SPEnterpriseSearchServiceApplication
Import-SPEnterpriseSearchThesaurus -SearchApplication $search -Filename \\NYC-
SP1\Starter\ContosoThesaurus.csv
Task 4: Test the thesaurus
3. In the Windows Security dialog box, in the User name text box type CONTOSO\Administrator, in
the Password text box type Pa$$w0rd, and then click OK.
4. In the search box, type Painkiller, and then press Enter. Notice that the search returns a datasheet
that matches the term Analgesic.
5. In the search box, type Emergency assistance, and then press Enter. Notice that the search returns a
datasheet that matches the term First aid.
6. In the search box, type Indigestion remedy, and then press Enter. Notice that the search returns a
datasheet that matches the term Digestive health.

Results: After completing this lab, you should have created and imported a thesaurus.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 2: Configuring Entity Extractors and Refiners
Task 1: Create a custom entity extraction dictionary
2. In the File Explorer window, browse to E:\Mod08\Starter, right-click ContosoBrandEntities.csv,
point to Open with, and then click Notepad.
3. Immediately after the line that reads Key,Display form, on a new line, add the following text:
Contoso Pharm,Contoso Pharmaceuticals
4. Add the following text, using a new line for each comma-separated pair of values:
Contoso Pharma,Contoso Pharmaceuticals
ContosoPharm,Contoso Pharmaceuticals
Contoso Consumer Pharmaceuticals,Contoso Pharmaceuticals
Contoso R&D,Contoso Research
Contoso R & D,Contoso Research
Contoso R and D,Contoso Research
Contoso Laboratories,Contoso Research
5. Save the file and close Notepad.
Task 2: Import the custom entity extraction dictionary
$search = Get-SPEnterpriseSearchServiceApplication
Import-SPEnterpriseSearchCustomExtractionDictionary -SearchApplication $search -
Filename \\NYC-SP1\Starter\ContosoBrandEntities.csv -DictionaryName
Microsoft.UserDictionaries.EntityExtraction.Custom.Word.2
Task 3: Map the custom entity extraction dictionary to a managed property
3. On the list of service applications, select Contoso Search, and then on the ribbon, click Manage.
4. On the Quick Launch navigation menu, under Queries and Results, click Search Schema.
5. In the Filter box, type body, and then press Enter.
6. In the list of managed properties, click body.
7. On the Contoso Search: Edit Managed Property body page, under Custom entity extraction,
select Word Extraction Custom2, and then click OK.
8. On the Quick Launch navigation menu, under Crawling, click Content Sources.
9. On the Local SharePoint sites drop-down menu, click Start Full Crawl.
11. Click Refresh periodically until the Status column shows Idle.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L8-5
Note: The search crawl may take a few minutes to complete.
Task 4: Add a refiner for the custom entity extractor
3. In the search box, type any text, and then press Enter.
Note: It does not matter what search text you type, this step is intended solely to take you
to the search results page.
4. On the results page, on the Settings menu, click Edit page.
5. On the Refinement web part drop-down menu, click Edit Web Part.
6. In the Properties for Search Refinement pane, click Choose Refiners.
7. In the Available refiners list box, click WordCustomRefiner2, and then click Add.
8. In the Selected refiners list box, click WordCustomRefiner2.
9. In the Configuration for: WordCustomRefiner2 pane, in the Display name text box, type Contoso
Division, and then click OK.
10. In the Properties for Search Refinement pane, click Apply.
11. On the ribbon, click Check In.
12. In the Check In dialog box, type a comment, and then click Continue.
13. On the Recent draft not published banner, click Publish this draft.
14. In the search box, type ContentType:Invoice, and then press Enter.
15. Verify that the Contoso Division refiner appears on the left of the page.
16. Under Contoso Division, click Contoso Research.
17. Verify that the search results page displays a filtered list, and then click the title of one of the search
results.
18. In the Microsoft Office dialog box, when asked if you want to open the file, click Yes.
20. When the document opens, verify that the invoice is addressed to one of the terms that you mapped
to Contoso Research in the custom entity extraction dictionary.
21. Close Word.
22. On the search results page, under Contoso Division, click All, and then click Contoso
Pharmaceuticals.
23. Verify that the search results page displays a filtered list, and then click the title of one of the search
results.
24. In the Microsoft Office dialog box, when asked if you want to open the file, click Yes.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
26. When the document opens, verify that the invoice is addressed to one of the terms you mapped to
Contoso Pharmaceuticals in the custom entity extraction dictionary.
27. Close Word, and then close Internet Explorer.

Results: After completing this exercise, you should have created and imported a custom entity extraction
dictionary and created a search refiner that uses the custom entities to filter search results.

Exercise 3: Configuring Query Spelling Correction
Task 1: Test spelling correction limitations
4. In the search box, type Analgesacs (a deliberate misspelling of analgesics), and then press Enter.
Verify that the search returns no results.
5. In the search box, type Acetamophen (a deliberate misspelling of acetaminophen), and then press
Enter. Verify that the search returns no results.
Task 2: Populate the Query Spelling Inclusions term set
3. In the list of service applications, click Contoso Search, and then on the ribbon, click Manage.
4. On the Quick Launch navigation menu, under Queries and Results, click Search Dictionaries.
5. On the Term Store Management Tool page, in the navigation pane, expand Search Dictionaries.
6. On the Query Spelling Inclusions drop-down menu, click Create Term.
7. Type Analgesic, and then press Enter.
8. Type Acetaminophen, and then press Enter.
9. Click the site logo to return to the Central Administration home page.
1. On the Central Administration home page, click Monitoring.
2. Under Timer Jobs, click Review job definitions.
3. On the Job Definitions page, click Search Custom Dictionaries Update.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L8-7
Task 4: Test the spelling dictionary updates
3. In the search box, type Analgesacs (a deliberate misspelling of analgesics), and then press Enter.
4. Verify that the search results page displays the message Did you mean Analgesic?
5. Click Analgesic, and verify that the search results page returns a datasheet.
6. In the search box, type Acetamophen (a deliberate misspelling of acetaminophen), and then press
Enter.
7. Verify that the search results page displays the message Did you mean Acetaminophen?
8. Click Acetaminophen, and verify that the search results page returns a datasheet.

Results: After completing this exercise, you should have populated and tested the Query Spelling
Inclusions dictionary.

Exercise 4: Configuring Company Name Extraction
Task 1: Populate the Company Inclusions term set
3. On the list of service applications, click Contoso Search, and then on the ribbon, click Manage.
4. On the Quick Launch navigation menu, under Queries and Results, click Search Dictionaries.
5. On the Term Store Management Tool page, in the navigation pane, expand Search Dictionaries.
6. On the Company Inclusions drop-down menu, click Create Term.
7. Type Litware, Inc., and then press Enter.
8. Type Proseware, Inc., and then press Enter.
9. Type Northwind Traders, and then press Enter.
10. Type Trey Research, and then press Enter.
11. Type Wide World Importers, and then press Enter.
1. On the Central Administration home page, click Monitoring.
2. Under Timer Jobs, click Review job definitions.
3. On the list of timer jobs, click Search Custom Dictionaries Update.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Enable company name extraction on a managed property
1. On the Central Administration home page, under Application Management, click Manage service
applications.
2. On the list of service applications, click Contoso Search, and then on the ribbon, click Manage.
3. On the Quick Launch navigation menu, under Queries and Results, click Search Schema.
4. In the Filter box, type body, and then press Enter.
5. In the list of managed properties, click body.
6. On the Contoso Search: Edit Managed Property body page, under Company name extraction,
select Company Extraction, and then click OK.
8. On the Local SharePoint sites drop-down menu, click Start Full Crawl.
10. Click Refresh periodically until the Status column shows Idle.
Note: The search crawl may take some time to complete. You can continue before the
search crawl is complete, but you may find that the search results in the next exercise are limited.
Task 4: Add a refiner for company names
3. In the search box, type any text, and then press Enter.
Note: It does not matter what search text you type, this step is designed solely to take you to the
search results page.
4. On the results page, on the Settings menu, click Edit page.
5. On the Refinement Web Part drop-down menu, click Edit Web Part.
6. In the Properties for Search Refinement pane, click Choose Refiners.
7. In the Available refiners list box, click companies, and then click Add.
8. In the Configuration for: companies (Companies) pane, in the Display name box, type Partner
Organization, and then click OK.
9. In the Properties for Search Refinement pane, click Apply.
10. On the ribbon, click Check In.
11. In the Check In dialog box, type a comment, and then click Continue.
12. On the Recent draft not published banner, click Publish this draft.
13. In the search box, type ContentType:Invoice, and then press Enter.
14. Verify that the Partner Organization refiner appears on the left of the page.
15. Under Partner Organization, click Litware, Inc.
16. Verify that the search results page displays a filtered list.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L8-9
17. Click other items under Partner Organization and verify that the search results are updated
accordingly.

Results: After completing this exercise, you should have configured company name extraction and
configured a search refiner to filter search results by company name.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L9-1
Module 9: Planning and Configuring Enterprise Content
Management
Lab A: Configuring eDiscovery in SharePoint
Server 2013
Exercise 1: Creating and Configuring an eDiscovery Center
Task 1: Create a secure group for the legal team
screen before you continue, and then wait a further five minutes before you proceed to the next step.
Pa$$w0rd.
7. In the center pane, click Users.
8. In the Tasks pane, click New, and then click Group.
9. In the Create Group dialog box, in the Group name box, type Legal.
10. In the navigation pane, click Members.
11. In the Members pane, click Add.
12. In the Select Users, Contacts, Computers, Service Accounts, or Groups dialog box, type
jim@contoso.com; anat@contoso.com; will@contoso.com; ray@contoso.com;
neil@contoso.com;, click Check Names, and then click OK.
13. In the Create Group: Legal dialog box, click OK.
Task 2: Create a web application policy for the legal team
1. Log on to the 20332B-NYC-SP-09 machine as administrator@contoso.com with password
Pa$$w0rd.
3. Under Application Management, click Manage web applications.
4. On the Web Applications Management page, click SharePoint - sharepoint.contoso.com80.
5. On the ribbon, in the Policy group, click User Policy.
6. In the Policy for Web Application dialog box, click Add Users.
7. In the Add Users dialog box, in the Zones list, ensure (All zones) is selected, and then click Next.
8. In the Users box, type CONTOSO\Legal, and then click Check Names.
9. Under Permissions, click Full Read - Has full read-only access, and then click Finish.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
10. In the Policy for Web Application dialog box, click OK.
Task 3: Create an eDiscovery Center site collection
2. Under Site Collections, click Create site collections.
3. On the Create Site Collection page, under Web Application, ensure
4. In the Title box, type Contoso eDiscovery.
5. In the Description box, type An eDiscovery Center for use by the Contoso legal team.
6. In the URL text box, type discovery.
7. Under Template Selection, on the Enterprise tab, click eDiscovery Center.
http://sharepoint.contoso.com/sites/discovery.
10. If the Windows Security dialog box appears, in the User name box, type CONTOSO\Administrator,
in the Password box, type Pa$$w0rd, and then click OK.
Task 4: Add site members to the eDiscovery Center
2. On the Site Settings page, under Users and Permissions, click People and groups.
3. On the New menu, click Add Users.
4. In the Share 'Contoso eDiscovery' dialog box, type
jim@contoso.com; anat@contoso.com; will@contoso.com; ray@contoso.com;
neil@contoso.com;, and then click Share.
Task 5: Create a new case
1. On the Quick Launch navigation menu, click Cases.
2. On the Cases page, click create.
3. On the New SharePoint Site page, in the Title box, type Trey Research Contract Dispute.
4. In the Description box, type Case ref C0001.
5. In the URL name box, type C0001, and then click Create.
6. On the CONTOSO\administrator drop-down menu, click Sign Out.
7. In the Windows Internet Explorer dialog box, click Yes.

Results: After completing this exercise, you should have created and configured an eDiscovery Center site
collection.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L9-3
Exercise 2: Discovering and Preserving Content
3. On the Manage Service Applications page, in the list of service applications, click Contoso Search,
and then on the ribbon, click Manage.
4. On the Contoso Search: Search Administration page, under Crawling, click Content Sources.
5. On the Contoso Search: Manage Content Sources page, on the Local SharePoint sites drop-down
menu, click Start Full Crawl.
7. Periodically click Refresh until the Status column displays Idle. This may take three to four minutes.
Task 2: Create an eDiscovery set
2. In the Internet Explorer address bar, type http://sharepoint.contoso.com/sites/discovery, and then
press Enter.
3. In the Windows Security dialog box, in the User name box, type CONTOSO\Jim, in the Password
4. On the Quick Launch navigation menu, click Cases.
5. On the Cases page, click Trey Research Contract Dispute.
6. On the Trey Research Contract Dispute page, on the Quick Launch navigation menu, click
eDiscovery Sets.
7. On the eDiscovery Sets page, click new item.
8. On the New: eDiscovery Set page, in the eDiscovery Set Name box, type Trey Contractual
Documents.
9. Click Add & Manage Sources.
10. In the Add & Manage Sources dialog box, under Locations, add the following items on separate
lines:
http://sharepoint.contoso.com/sites/finance
http://sharepoint.contoso.com/projects/p1
11. To the right of each item, click the Check Location icon, and then click OK.
12. On the New: eDiscovery Set page, in the Filter box, type Trey Research.
13. In the Start Date date picker, click January 1st 2012, and then click Apply Filter.
14. Click Enable In-Place Hold, and then click Preview Results.
15. In the Preview Results dialog box, verify that the SharePoint tab includes several items, and then
click Close.
16. On the New: eDiscovery Set page, click Save.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Run the eDiscovery In-Place Hold Processing Timer job
2. On the Quick Launch navigation menu, click Monitoring.
4. On the Job Definitions page, click eDiscovery In-Place Hold Processing.
Note: By default, the eDiscovery In-Place Hold Processing timer job runs once every hour.
In a production environment, you would not typically need to run the timer job manually. In this
case, you are running the timer job manually to enable you to proceed with the lab without
delay.
Task 4: Test the in-place hold functionality
2. In the Internet Explorer address bar, type http://sharepoint.contoso.com/sites/Finance, and then
press Enter.
4. On the Quick Launch navigation menu, click Contracts.
5. On the Contracts page, select Wide World Contract by clicking in the leftmost column.
6. On the ribbon, on the FILES tab, click Delete Document.
8. On the Quick Launch navigation menu, click Site Contents.
9. On the Site Contents page, click Preservation Hold Library.
10. Notice that the Preservation Hold Library includes a preserved version of the file you just deleted.

Results: After completing this exercise, you should have created and configured an eDiscovery set.

Exercise 3: Querying and Exporting Content
3. In the list of service applications, click Contoso Search, and then on the ribbon, click Manage.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L9-5
5. On the Contoso Search: Manage Content Sources page, on the Local SharePoint sites drop-down
menu, click Start Full Crawl.
7. Periodically click Refresh until the Status column displays Idle. This may take three to four minutes.
Task 2: Create a new eDiscovery query
2. In the Internet Explorer address bar, type http://sharepoint.contoso.com/sites/discovery/C0001,
3. In the Windows Security dialog box, in the User name box, type CONTOSO\Jim, in the Password
4. On the Quick Launch navigation menu, click Queries.
5. On the Queries page, click new item.
6. On the Query: New Item page, in the Name box, type Trey Invoices.
7. In the Query box, type ContentType:"Invoice", and then click Search.
8. Click Advanced Query Options.
9. In the Advanced Query Options dialog box, notice it displays the full SharePoint query:
(ContentType:"Invoice") AND (((Trey Research))) AND
(Path:"http://sharepoint.contoso.com/sites/finance" OR
Path:"http://sharepoint.contoso.com/projects/p1")
Note: The dialog box may take several seconds to display the query.
This query is comprised of:
The keyword query you added.
The paths to the sources you defined in the previous exercise.
The filter you defined in the previous exercise.
10. In the Advanced Query Options dialog box, click OK.
11. At the bottom of the page, on the SharePoint tab, notice that the query has identified four
documents that match the search criteria.
12. Under Specify Property, notice that you have the option to further refine your search results.
13. Notice that you have the option to export content at this point.
14. Click Save, and then click Close.
Task 3: Export discovered content
1. On the Quick Launch navigation menu, click Exports.
2. On the Exports page, click new item.
3. Under Select Queries, select Trey Invoices by clicking in the leftmost column, and then click Next.
4. On the Export: New Item page, review the options, and then click OK.
5. On the Export: Download page, click Download Results.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6. In the Application Run - Security Warning dialog box, click Run.
7. In the eDiscovery Download Manager dialog box, click Browse.
8. In the Browse For Folder dialog box, click Desktop, and then click OK.
9. In the eDiscovery Download Manager dialog box, click OK.
10. When the download is complete, click Close.
12. On the desktop, review the contents of the Trey Invoices folder.
Note: In addition to the exported content, the Trey Invoices folder includes a manifest.xml
file. This is an Electronic Discovery Reference Model (EDRM)compliant XML file that enables
users to use the export with third-party EDRM tools.
13. Close the Trey Invoices folder window.

Results: After completing this exercise, you should have created an eDiscovery query and exported the
content returned by the query.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L9-7
Lab B: Configuring Records Management in
Exercise 1: Configuring In-Place Records Management
Task 1: Create an in-place retention policy for contracts
2. In the Internet Explorer address bar, type http://sharepoint.contoso.com/sites/Finance, and then
press Enter.
5. On the ribbon, on the LIBRARY tab, click Library Settings.
6. On the Settings page, under Permissions and Management, click Information management
policy settings.
7. On the Information Management Policy Settings page, under Content Type Policies, click
Contract.
8. On the Edit Policy page, in the Administrative Description box, type Retention and expiration
policy for contracts.
9. In the Policy Statement box, type Contracts are automatically retained for five years from the
final effective date.
10. Select the Enable Retention check box, and then click Add a retention stage.
11. In the Stage properties dialog box, under This stage is based off a date property on the item, in
the leftmost dropdown list, click Final Effective Date.
12. In the central text box, type 5.
13. Under Action, in the When this stage is triggered, perform the following action list, click
Permanently Delete, and then click OK.
14. On the Edit Policy page, click OK.
Task 2: Create an in-place retention and auditing policy for invoices
1. On the Information Management Policy Settings page, at the top of the page, click Finance.
2. On the Quick Launch navigation menu, click Invoices.
3. On the ribbon, on the LIBRARY tab, click Library Settings.
4. On the Settings page, under Permissions and Management, click Information management
policy settings.
5. On the Information Management Policy Settings page, under Content Type Policies, click
Invoice.
6. On the Edit Policy page, in the Administrative Description box, type Retention and expiration
policy for invoices.
7. In the Policy Statement box, type Invoices are automatically retained for seven years from the
due date.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
8. Select the Enable Retention check box, and then click Add a retention stage.
9. In the Stage properties dialog box, under This stage is based off a date property on the item, in
the leftmost drop-down list, click Payment Due Date.
10. In the central text box, type 7.
11. Under Action, in the When this stage is triggered, perform the following action list, click
Permanently Delete, and then click OK.
12. On the Edit Policy page, select the Enable Auditing check box.
13. Select the following items check boxes, and then click OK:
Editing items
Moving or copying items to another location in the site
Deleting or restoring items

Results: After completing this exercise, you should have configured retention and audit policies for the
Contract and Invoice content types.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L10-1
Module 10: Planning and Configuring Web Content
Management
Lab A: Configuring Managed Navigation
and Catalog Sites
Exercise 1: Configuring Product Catalog Sites
Task 1: Create a Product Catalog Site Collection
1. Start the 20332B-NYC-DC-10 virtual machine. Wait until the logon screen is displayed and then wait a
further five minutes before you proceed to the next step.
2. Start the 20332B-NYC-DB-10 virtual machine. Wait until the logon screen is displayed before
continuing.
3. Start the 20332B-NYC-SP-10 virtual machine.
Pa$$w0rd.
6. Under Application Management, click Create site collections.
7. On the Create Site Collection page, under Web Application, ensure that
8. In the Title box, type Products.
9. In the Description box, type A product catalog for demonstration purposes.
10. Under URL, in the text box, type catalog.
11. Under Template Selection, on the Publishing tab, click Product Catalog.
http://sharepoint.contoso.com/sites/catalog.
14. In the Windows Security dialog box, log in as CONTOSO\Administrator with the password
Pa$$w0rd.
Task 2: Add product-related site columns
1. On the Products home page, click Create site columns.
2. On the Site Columns page, in the Show Group list, click Product Catalog Columns.
3. On the Site Columns page, click Create.
4. In the Column name text box, type Size.
5. Under Group, in the Existing group list, click Product Catalog Columns.
6. Click OK.
8. In the Column name text box, type Quantity.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
9. Under The type of information in this column is, click Number (1, 1.0, 100).
11. Click OK.
13. In the Column name text box, type Color.
15. Click OK.
Task 3: Create a product-related content type
1. On the Settings menu, click Site Settings.
2. On the Site Settings page, under Web Designer Galleries, click Site content types.
3. On the Site Content Types page, click Create.
4. On the New Site Content Type page, in the Name box, type Pharmacy Products.
5. Under Parent Content Type, in the Select parent content type from list, click Product Catalog
Content Types.
6. In the Parent Content Type list, click Product with Image.
7. Under Group, in the Existing group list, click Product Catalog Content Types, and then click OK.
8. On the Site Content Type page, under Columns, click Add from existing site columns.
9. On the Add Columns page, in the Select columns from list, click Product Catalog Columns.
10. In the Available columns list box, click Color, press Ctrl and click Quantity, press Ctrl and click Size,
and then click Add.
11. Click OK.
12. Click the site logo to return to the Products home page.
Task 4: Add the Pharmacy Products content type to the Products list
1. On the Products home page, under Add catalog items, click Products list.
2. On the ribbon, on the LIST tab, click List Settings.
3. On the Settings page, under Content Types, click Add from existing site content types.
4. On the Add Content Types page, in the Select site content types from list, click Product Catalog
Content Types.
5. In the Available Site Content Types list box, click Pharmacy Product, and then click Add.
6. Click OK.
7. On the Settings page, under Content Types, click Product with Image.
8. On the List Content Type page, under Settings, click Delete this content type.
10. On the Settings page, under Views, click All Items.
11. Under Columns, select Color, Quantity, and Size, and then click OK.
12. Click the site logo to return to the Products home page.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L10-3
Task 5: Configure the Product Hierarchy term set
1. On the Products home page, click Manage item hierarchy in Term Store.
2. On the Term Store Management Tool page, in the navigation pane, expand the Site Collection
sharepoint.contoso.com-sites-catalog node.
3. Click Product Hierarchy, and then in the Product Hierarchy drop-down menu, click Create Term.
4. Type Pharmacy Products, and then press Enter.
5. Click Pharmacy Products, and then in the Pharmacy Products drop-down menu, click Create
Term.
6. Type Analgesics, and then press Enter.
7. Click Analgesics, and then in the Analgesics drop-down menu, click Create Term.
8. Type Acetaminophen, and then press Enter.
9. Type Ibuprofen, and then press Enter.
Term.
11. Type Digestive Health, and then press Enter.
12. Click Digestive Health, and then in the Digestive Health drop-down menu, click Create Term.
13. Type Antacids, and then press Enter.
14. Type Prokinetics, and then press Enter.
Term.
16. Type First Aid, and then press Enter.
17. Click First Aid, and then in the First Aid drop-down menu, click Create Term.
18. Type Antiseptics, and then press Enter.
19. Type Bandages, and then press Enter.
20. Type Plasters, and then press Enter.
21. Type Scissors, and then press Enter.
Task 6: Populate the Product Catalog site
2. In the File Explorer window, browse to E:\Mod10\SetupFiles.
3. Right-click Setup.ps1, and then click Run with PowerShell.
Note: The Setup.ps1 file adds some sample items to the Products list.
4. In the Administrator: Windows PowerShell window, at the Execution Policy Change prompt,
press Enter.
5. After the script finishes running, on the Start screen, type Internet Explorer, and then press Enter.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6. In the Internet Explorer address bar, type sharepoint.contoso.com/sites/catalog, and then press
Enter.
7. In the Windows Security dialog box, log on as CONTOSO\Administrator with the password
Pa$$w0rd.
8. On the site home page, under Products, verify that several products with images have been added to
the Products list.
9. Verify that a term from the Product Hierarchy term set has been assigned to the Item Category
field for each item.

Results: After completing this exercise, you should have created and configured a product catalog site
collection.

Exercise 2: Configuring Cross-Site Publishing
Task 1: Configure catalog settings for the Products list
1. In the Internet Explorer address bar, type sharepoint.contoso.com/sites/catalog, and then press
Enter.
2. On the Quick Launch navigation menu, click Products.
3. On the ribbon, on the LIST tab, click List Settings.
4. On the Settings page, under General Settings, click Catalog Settings.
5. On the Catalog Settings page, under Catalog Sharing, select Enable this library as a catalog.
6. Under Catalog Item URL Fields, in the Available Fields list box, click Item Category, press Ctrl and
click Item Number, and then click Add.
7. Under Navigation Hierarchy, in the Select the column that categorizes items for navigation list,
click Item Category.
8. Click OK.
9. On the Settings page, under General Settings, click Advanced settings.
10. On the Advanced Settings page, click Reindex List.
11. In the Reindex List dialog box, click Reindex List.
12. On the Advanced Settings page, click OK.
Task 2: Share the Product Hierarchy term set with the publishing site collection
1. Click Home.
2. On the site home page, click Manage item hierarchy in Term Store.
3. On the Term Store Management Tool page, in the navigation pane, click Site Collection
sharepoint.contoso.com-sites-catalog.
4. In the Site Collection Access text box, type http://sharepoint.contoso.com/sites/staging, and
then click Save.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L10-5
3. On the list of service applications, click the Contoso Search row, and then on the ribbon, click
Manage.
5. In the Local SharePoint sites drop-down menu, click Start Full Crawl.
7. Click Refresh periodically until the Status column displays the text Idle.
Note: The search crawl may take several minutes to complete.

Results: After completing this exercise, you should have made the contents of your product catalog site
available to other site collections by using cross-site publishing.

Exercise 3: Configuring Publishing Sites
Task 1: Create a Publishing site collection
1. On the SharePoint 2013 Central Administration website, click Central Administration, and then
under Application Management, click Create site collections.
2. On the Create Site Collection page, in the Title box, type Staging.
3. In the Description box, type A staging site to test cross-site publishing.
4. Under Web Site Address, in the URL text box, type staging.
5. Under Template Selection, on the Publishing tab, click Publishing Portal.
http://sharepoint.contoso.com/sites/staging.
Pa$$w0rd.
Task 2: Connect the publishing site to a product catalog
2. On the Site Settings page, under Site Administration, click Manage catalog connections.
3. On the Manage catalog connections page, click Connect to a catalog.
4. On the Connect to catalog page, in the Products Products row, click Connect.
5. On the Catalog Source Settings page, under Connection Integration, ensure that Integrate the
catalog into my site is selected.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6. Under Navigation Hierarchy, in the Select the column that categorizes items for navigation list,
ensure Item Category is selected.
7. In the Root term of hierarchy box, click Browse for a valid choice.
Note: The Browse for a valid choice item is represented by an icon consisting of two tags.
8. In the Select: Add Terms dialog box, click Pharmacy Products, click Select, and then click OK.
9. Review the remaining options on the page without changing them, and then click OK.
10. Verify that the Quick Launch navigation menu now mirrors the Pharmacy Products term set that you
configured in the first exercise.
11. On the Quick Launch navigation menu, click Bandages.
12. Verify that the page displays two items from the Bandages category.
13. Verify that the page displays a friendly URL that ends with /first-aid/bandages.
14. Click 5m Crepe Bandage.
15. Verify that the page displays the details of the 5m Crepe Bandage product.
Note: The default category and item pages (together with the master page) that you see at
this point are designed for testing and demonstration purposes only. In a real environment,
designers would create category and item pages to present your products in a desirable way.

Results: After completing this exercise, you should have configured a publishing site to consume data
from a product catalog site.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L10-7
Lab B: Configuring Device Channels
Exercise 1: Configuring Device Channels
Task 1: Create a network share for the Master Page Gallery
1. Open the 20332B-NYC-SP-01 virtual machine. If you are not already logged on, log on as
2. On the Start screen, click Computer.
3. In the Computer window, on the Computer tab, click Map network drive.
4. In the Map Network Drive dialog box, on the Drive menu, click Z:.
5. In the Folder box, type http://sharepoint.contoso.com/sites/staging/_catalogs/masterpage/,
and then click Finish.
Pa$$w0rd.
7. Verify that the File Explorer window displays the contents of the Master Page Gallery.
Task 2: Create a new device channel
2. In the Internet Explorer address bar, type sharepoint.contoso.com/sites/staging, and then press
Enter.
Pa$$w0rd.
4. On the Settings menu, click Design Manager.
5. On the Design Manager: Welcome page, click Manage Device Channels.
6. On the Design Manager: Manage Device Channels page, click Create a channel.
7. On the Device Channels New Item dialog, in the Name box, type Windows Phone.
8. In the Alias box, type WindowsPhoneOS1.
9. In the Description box, type A device channel for Windows Phone operating systems.
10. In the Device Inclusion Rules box, type Windows Phone OS.
11. Select Active, and then click Save.
Task 3: Modify a master page to test the device channel
1. On the Design Manager: Manage Device Channels page, click Edit Master Pages.
2. On the Design Manager: Edit Master Pages page, click oslo.
3. On the banner at the top of the page, click Snippets.
4. On the ribbon, click Device Channel Panel.
5. Under Customization Device Channel Panel, in the IncludedChannels box, type
WindowsPhoneOS1, and then click Update.
6. Verify that the page generates an HTML snippet for the device channel panel.
7. Under HTML Snippet, click Copy to Clipboard.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
8. In the Internet Explorer dialog box, click Allow access.
9. Without closing any Internet Explorer tabs, on the taskbar, click File Explorer.
10. In the File Explorer window, click Computer, and then double-click masterpage.
11. Right-click oslo.html, point to Open with, click More options, and then click Notepad.
12. In Notepad, on the Edit menu, click Find.
13. In the Find dialog, in the Find what box, type <div id="s4-bodyContainer">, and then click Find
Next.
14. Add a blank line immediately below the element that you just located, place the cursor in this line,
and then on the Edit menu, click Paste.
15. Locate the line that reads You should replace this div with content that renders based on your Device
Channel Panel Properties. (This will be approximately six lines into the content that you just added.)
Delete this text, and in its place type This content is only visible on the Windows Phone OS
device channel.
16. On the File menu, click Save, and then close Notepad.
Task 4: Associate master pages with device channels
1. In Internet Explorer, on the Preview: oslo.html tab, click the browser back button.
2. On the Design Manager: Edit Master Pages page, click Publish and Apply Design.
3. On the Design Manager: Publish and Apply Design page, click Assign master pages to your site
based on device channel.
4. On the Site Master Page Settings page, under Site Master Page, in the Windows Phone menu,
click oslo.
5. In the Default menu, click oslo.
6. Under System Master Page, in the All Channels menu, click oslo.
7. Click OK.
Task 5: Test device channels
1. Click the site logo to return to the Staging home page.
2. In the Internet Explorer address bar, append the following text to the site URL and then press Enter:
?DeviceChannel=WindowsPhoneOS1
3. When the page reloads, verify that the page includes a highlighted block at the top of the page with
the text This content is only visible on the Windows Phone OS device channel.

Results: After completing this exercise, you should have created, configured, and tested a device channel.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L11-1
Module 11: Managing Solutions in SharePoint Server 2013
Lab: Managing Solutions
Exercise 1: Configuring a Sandboxed Solution Management at the Farm
Level
Task 1: Start the sandboxed code service
Pa$$w0rd.
6. On the Central Administration website, under System Settings, click Manage services on server.
7. On the Services on Server page, locate the Microsoft SharePoint Foundation Sandboxed Code
Service service, and then in that row, if the service is not already started, click Start.
Task 2: Create a quota template to control sandboxed resource usage
2. On the Application Management page, under Site Collections, click Specify quota templates.
3. On the Quota Templates page, under Template Name, click Create a new quota template, and
then in the New template name box, type Standard Template.
4. Ensure the Limit site storage to a maximum of check box is not selected.
5. Ensure the Send warning E-mail when Site Collection storage reaches check box is not selected.
6. In the Limit maximum usage per day to box, type 200.
7. Select the Send warning e-mail when usage per day reaches check box, in the text box type 100,
and then click OK.
9. On the Quota Templates page, under Template Name, click Create a new quota template, and
then in the New template name box, type Enhanced Template.
10. Ensure the Limit site storage to a maximum of check box is not selected.
11. Ensure the Send warning E-mail when Site Collection storage reaches check box is not selected.
12. In the Limit maximum usage per day to box, type 500.
13. Ensure the Send warning e-mail when usage per day reaches check box is selected, in the text box
type 450, and then click OK.
14. On the Application Management page, under Site Collections, click Configure quotas and locks.
15. On the Site Collection Quotas and Locks page, click the current site collection, and then click
Change Site Collection.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
16. In the Select Site Collection dialog box, click the current web application, and then click Change
Web Application.
17. In the Select Web Application dialog box, click SharePoint - sharepoint.contoso.com80.
18. In the Select Site Collection dialog box, click OK.
19. On the Site Collection Quotas and Locks page, in the Current quota template list, click Standard
Template, and then click OK.
20. On the Application Management page, under Site Collections, click Configure quotas and locks.
21. On the Site Collection Quotas and Locks page, click the current site collection, and then click
Change Site Collection.
22. In the Select Site Collection dialog box, click the current web application, and then click Change
Web Application.
23. In the Select Web Application dialog box, click AdminContosoCom 80.
24. In the Select Site Collection dialog box, click OK.
25. On the Site Collection Quotas and Locks page, in the Current quota template list, click Enhanced
Template, and then click OK.
Task 3: Configure load balancing and block a solution
1. Under Central Administration, click System Settings.
2. On the System Settings page, under Farm Management, click Manage user solutions.
3. On the Sandboxed Solution Management page, under Solution Restrictions, click Browse.
4. In the Choose File to Upload dialog box, browse to the E:\Mod11 folder, click BadWebPart.wsp,
and then click Open.
5. In the Message box, type This solution does not comply with company policies., and then click
Block.
6. Under Load Balancing, click All sandboxed code runs on the same machine as a request, and
then click OK.

Results: After completing this exercise, you should have configured a SharePoint farm to support
sandboxed solutions.

Exercise 2: Configuring Sandboxed Solution Management at the Site
Collection Level
Task 1: Verify sandboxed code quotas
4. Click Settings and then click Site settings.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L11-3
5. On the Site Settings page, under Web Designer Galleries, click Solutions.
6. Verify that the resource quota is 200 server resources.
7. In Internet Explorer, browse to http://admin.contoso.com.
10. On the Site Settings page, under Web Designer Galleries, click Solutions.
11. Verify that the resource quota is 500 server resources.
Task 2: Add a sandboxed solution
1. On the Solution Gallery page, on the ribbon, click Upload Solution.
3. In the Choose File to Upload dialog box, browse to the E:\Mod11 folder, click Contoso
Pharmaceuticals Brand.wsp, and then click Open.
5. In the Solution Gallery - Activate Solution dialog box, on the ribbon, click Activate, and then click
Close.

Results: After completing this exercise, you should have verified the quotas applied to a site collection,
and added a sandboxed solution to the site collection.

Exercise 3: Deploying Farm Solutions
Task 1: Install and deploy a farm solution
Add-SPSolution "E:\Mod11\Contoso Pharmaceuticals Clinical Trial Management.wsp"
Install-SPSolution -Identity "Contoso Pharmaceuticals Clinical Trial Management.wsp"
-GACDeployment
Task 2: Enable features added by a farm solution
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6. On the Site Collection Features page, locate the Contoso Pharmaceuticals Clinical Trial
Management feature, and then in that row click Activate. Verify that the status of the feature
changes to Active.

Results: After completing this exercise, you should have installed and deployed a farm solution by using
PowerShell, and then activated the features added by that farm solution.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L12-1
Module 12: Managing Apps for SharePoint Server 2013
Lab: Configuring and Managing SharePoint
Apps
Exercise 1: Configuring a SharePoint Farm to Support Apps
Task 1: Configure DNS settings to support app deployment
4. Log on to the 20332B-NYC-DC-12 machine as administrator@contoso.com with the password
Pa$$w0rd.
6. In DNS Manager, right-click Forward Lookup Zones, and then click New Zone.
7. In the New Zone Wizard dialog box, on the Welcome to the New Zone Wizard page, click Next.
8. On the Zone Type page, click Next.
9. On the Active Directory Zone Replication Scope page, click Next.
10. On the Zone Name page, in the Zone name box, type contosoapps.com, and then click Next.
11. On the Dynamic Update page, click Next.
12. On the Completing the new Zone Wizard page, click Finish.
13. Expand Forward Lookup Zones, click contosoapps.com, right-click contosoapps.com, and then
click New Host (A or AAAA).
14. In the New Host dialog box, in the Name box, type *, in the IP address box, type 172.16.1.50, and
then click Add Host.
Task 2: Create a new service account
4. In the Create User dialog box, in the Full name box, type SharePoint Apps Service App Pools.
5. In the User UPN logon box, type AppsAppPools, verify that the User SamAccountName logon
boxes have automatically populated with the corresponding username.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 3: Add an additional IP address to the SharePoint server and configure IIS to
bind to the new IP address
2. On the Start screen, type Network Connections, click Settings, and then click View network
connections.
3. Right-click the network adapter, and then click Properties.
4. In the properties dialog box, click Internet Protocol Version 4 (TCP/IPv4), and then click
Properties.
5. In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click Advanced.
6. In the Advanced TCP/IP Settings dialog box, on the IP Settings tab, under IP addresses click Add.
7. In the TCP/IP Address dialog box, in the IP address box, type 172.16.1.50, and then click Add.
8. In the Advanced TCP/IP Settings dialog box, click OK.
9. In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click OK.
10. In the properties dialog box, click Close.
11. On the Start screen, type IIS, and then press Enter.
12. In Internet Information Services (IIS) Manager, expand NYC-SP1 (CONTOSO\Administrator).
13. If an Internet Information Services (IIS) Manager dialog box appears asking you about getting
started with Microsoft Web Platform, click No.
14. Expand Sites, and then click SharePoint - sharepoint.contoso.com80.
15. In the Actions pane, click Bindings.
16. In the Site Bindings dialog box, click Add.
17. In the Add Site Binding dialog box, in the IP address list click 172.16.1.50, click OK.
18. In the Site Bindings dialog box, click Close.
5. On the Register Managed Account page in the User name box, type contoso\AppsAppPools, in

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L12-3
Task 5: Use PowerShell to create new shared service applications
$AppPool = New-SPServiceApplicationPool -Name AppManagementAppPool -Account
AppsAppPools@contoso.com
$AppManagement = New-SPAppManagementServiceApplication -Name "App Management" -
ApplicationPool $AppPool
$AppManagementProxy = New-SPAppManagementServiceApplicationProxy -Name "App
Management Proxy" -ServiceApplication $AppManagement
5. Switch to Internet Explorer to view the Central Administration website.
applications.
8. Verify that the App Management service appears in the list (it should also have a corresponding
proxy).
9. Switch to the Administrator: SharePoint 2013 Management Shell command window, and then run
the following command:
$AppPool = New-SPServiceApplicationPool -Name SubscriptionSettingsAppPool -Account
AppsAppPools@contoso.com
$SubscriptionSettings = New-SPSubscriptionSettingsServiceApplication -Name
"Subscription Settings" -ApplicationPool $AppPool
$SubscriptionSettingsProxy = New-SPSubscriptionSettingsServiceApplicationProxy -
ServiceApplication $SubscriptionSettings
12. Switch to Internet Explorer to view the Central Administration website.
13. Refresh the Manage Service Applications page, and verify that the Subscription Settings service
appears in the list (it should also have a corresponding proxy).
Task 6: Use the Central Administration website to start necessary services
1. Click Central Administration, and then under System Settings, click Manage services on server.
2. Locate the App Management Service service, if the service is currently Stopped, in that row click
Start.
3. Locate the Microsoft SharePoint Foundation Subscription Settings Service service, if the service is
currently Stopped, in that row click Start.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Results: After completing this exercise, you should have configured a SharePoint farm to support apps,
including starting services, creating shared services, and necessary domain configuration.

Exercise 2: Creating and Configuring a Corporate App Catalog
3. Click SharePoint - sharepoint.contoso.com:80, and then on the ribbon, click Managed Paths.
4. On the Define Managed Paths dialog box, under Add a New Path, in the Path box, type
contosoapps.
5. In the Type list, click Explicit inclusion, click Add Path, and then click OK.
Task 2: Create an app catalog
1. Click Apps.
2. On the Apps page, under App Management, click Manage App Catalog.
3. On the Manage App Catalog page, ensure Create a new app catalog site is selected.
4. Ensure the Web Application is http://sharepoint.contoso.com. If it is not, click the current web
application, click Change Web Application, and then in the Select Web Application dialog box,
click SharePoint - sharepoint.contoso.com80.
5. On the Manage App Catalog page, click OK.
6. On the Create App Catalog page, in the Title box, type Contoso Apps.
7. Under Web Site Address, in the URL list, click /contosoapps.
CONTOSO\Administrator.
9. Under End Users, in the Users/Groups box, type Everyone, and then click OK.
Task 3: Configure app URLs
1. Click Apps.
2. On the Apps page, under App Management, click Configure App URLs.
3. On the Configure App URLs page, in the App domain box, type contosoapps.com.
4. In the App prefix box, type contoso, and then click OK.
Task 4: Configure SharePoint store settings
1. On the Apps page, under SharePoint and Office Store, click Configure Store Settings.
2. On the SharePoint Store Settings page, under App Purchases, click No, and then click OK.

Results: After completing this exercise, you should have created and configured a corporate catalog.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L12-5
Exercise 3: Deploying and Monitoring Apps
Task 1: Add a sample app to the app catalog
1. In Internet Explorer, click the New Tab tab.
2. In the address bar, type http://sharepoint.contoso.com/contosoapps, and then press Enter.
3. In the Windows Security dialog box, in the User name box, type administrator@contoso.com, in
4. On the Contoso Apps page, click Distribute apps for SharePoint.
5. On the Apps for SharePoint page, click new app.
7. In the Choose File to Upload dialog box, browse to E:\Mod12, click ContosoApp.app, and then
click Open.
9. In the Apps for SharePoint - ContosoApp.app dialog box, select the Featured check box, and then
click Save.
Task 2: Add the sample app to a SharePoint site
1. In Internet Explorer, navigate to http://sharepoint.contoso.com.
2. Click Settings, and then click Add an app.
3. On the Your Apps page, click From Your Organization.
4. Under Noteworthy, click ContosoApp.
5. In the Do you trust ContosoApp? dialog box, click Trust It.
6. Wait until the ContosoApp app finishes installing (when the app finishes installing you are no longer
able to cancel the installation) before continuing.
7. On the Site Contents page, click ContosoApp.
8. In the Windows Security dialog box, in the User name box, type administrator@contoso.com, in
Task 3: Attempt to monitor the sample app
1. Switch to the Central Administration website.
2. Click the Apps tab.
3. On the Apps page, click Monitor Apps.
4. On the Monitored Apps page verify that an error indicates that the search service is currently
disabled.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
5. In the Create User dialog box, in the Full name box, type Search Service Admin Web Service
Application Pool.
6. In the User UPN logon box, type SearchAdminAppPool, verify that the User SamAccountName
logon boxes have automatically populated with the corresponding user name.
7. In the Password, and Confirm password boxes type Pa$$w0rd.
10. In the Create User dialog box, in the Full name box, type Search Service Query Web Service
Application Pool.
11. In the User UPN logon box, type SearchQueryAppPool, verify that the User SamAccountName
logon boxes have automatically populated with the corresponding user name.
15. In the Create User dialog box, in the Full name box, type Search Service Account.
16. In the User UPN logon box, type SearchService, verify that the User SamAccountName logon
2. Under Central Administration, click Security.
CONTOSO\SearchAdminAppPool, in the Password box, type Pa$$w0rd, and then click OK.
CONTOSO\SearchQueryAppPool, in the Password box, type Pa$$w0rd, and then click OK.
9. On the Register Managed Account page, in the User name box, type CONTOSO\SearchService, in
Task 6: Use the Central Administration website to create a new shared search service
application
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L12-7
3. On the Manage Service Applications page, on the ribbon, click New and then click Search Service
Application.
4. In the Create New Search Service Application dialog box, in the Service Application name box,
type Contoso Search.
5. In the Search Service Account list, click CONTOSO\SearchService.
6. Under Application Pool for Search Admin Web Service, in the Application pool name box, type
SearchAdminAppPool.
7. In the Configurable list, click CONTOSO\SearchAdminAppPool.
8. Under Application Pool for Search Query and Site Settings Web Service, in the Application pool
name box, type SearchQueryAppPool.
9. In the Configurable list, click CONTOSO\SearchQueryAppPool, and then click OK.
10. In the Manage Search Topology dialog box, click OK.
11. Refresh the Manage Service Applications page, and then click Contoso Search (you must click the
name in the Search Service Application row, not the Search Service Application Proxy row).
13. On the Contoso Search: Manage Content Sources page, point to Local SharePoint sites, click the
drop-down arrow and then click Start Full Crawl. If the Local SharePoint sites content source does
not appear in this list of content sources, periodically refresh the page. It may take several minutes for
SharePoint to populate the content source list after you create the Search Service Application
shared service application.
15. Verify that the status of the Local SharePoint sites content source has changed to Starting.
Periodically refresh the page and view the status. Do not continue until the status returns to Idle.
Task 7: Monitor the sample app
1. On the Contoso Search page, click Central Administration.
2. On the Central Administration page, click Apps.
3. On the Apps page, click Monitor Apps.
4. On the Monitor Apps page, on the ribbon, click Add App.
5. In the Add an app to monitor dialog box, select the ContosoApp check box, and then click Add.

Results: After completing this exercise, you should have added a sample application to the corporate
catalog, deployed that app to a SharePoint site, configured SharePoint to support monitoring, and
monitored the sample app.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L13-1
Module 13: Developing a Governance Plan
Lab A: Developing a Plan for Governance
Exercise 1: Creating a Governance Plan
1. Start the 20332B-NYC-CL virtual machine. Wait for the virtual machine to display the logon screen,
and then continue.
2. Log on to the 20332B-NYC-CL machine as admin with the password Pa$$w0rd.
4. In the E:\Mod13\Starter folder, read the information in the SharePoint 2013 - Contoso
Provisioning and Customization Requirements.docx file.
Task 2: Complete the SharePoint 2013 Governance worksheet
1. In the E:\Mod13\Starter folder, open and complete the worksheet in the SharePoint 2013
Governance Worksheet.xlsx file, based on the information you have reviewed in Task 1.

Results: A completed Governance worksheet.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Managing Site Creation and Deletion
Exercise 1: Creating and Publishing Site Policies
Task 1: Activate the Site Policy feature on the content type hub site collection
Pa$$w0rd.
6. On the Central Administration website, under Application Management, click Manage service
applications.
7. Click the row (not the name) for the Contoso MMS Managed Metadata Service, and then on the
ribbon, click Properties.
8. In the Create New Managed Metadata Service dialog box, ensure the Content Type hub is
http://sharepoint.contoso.com, and then click Cancel.
9. In Internet Explorer, click the New Tab tab, in the address bar, type http://sharepoint.contoso.com,
box type Pa$$w0rd, and then click OK.
11. On the SharePoint page, click Settings, and then click Site settings.
13. On the Site Collection Features page, locate the Site Policy feature, and then verify that it is Active.
Task 2: Create and publish a site policy
1. Click Site Settings.
2. On the Site Settings page, under Site Collection Administration, click Site Policies.
3. On the Site Policies page, click Create.
4. On the New Site Policy page, in the Name box, type Short Term Planning.
5. Under Site Closure and Deletion, click Close and delete sites automatically.
6. Under Close Event, in the Site created date + box, type 180, and in the list, click days.
7. Under Deletion Event, in the Site closed date +box, type 60, and in the list, click days.
8. Clear the Send an email notification to site owners this far in advance of deletion check box.
9. Clear the Owners can postpone imminent deletion for check box.
10. Select the The site collection will be read only when it is closed check box, and then click OK.
11. On the Site Policies page, in the Short Term Planning row, click Manage publishing for this
policy.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L13-3
12. On the Content Type Publishing page, ensure that Publish is selected, and then click OK.
14. In the Administrator: SharePoint 2013 Management Shell window, type get-SPTimerJob | where
{$_.DisplayName -eq "Content Type Hub"} | start-SPTimerJob, and then press Enter. Verify that
the command runs without reporting any errors.
15. In the Administrator: SharePoint 2013 Management Shell window, type get-SPTimerJob | where
{$_.DisplayName -eq "Content Type Subscriber"} | start-SPTimerJob, and then press Enter. Verify
that the command runs without reporting any errors.
16. Close the Administrator: SharePoint 2013 Management Shell window.

Results: After completing this exercise, you should have enabled site policies on the content type hub,
created a new site policy, and published that policy for consumption in other site collections.

Exercise 2: Enabling and Managing Self-Service Site Creation
Task 1: Use the Central Administration website to create a site quota
1. In Internet Explorer, click the Manage Service Applications browser tab.
4. On the Quota Templates page, click Create a new quota template.
5. In the New template name text box, type Short Term Quota.
6. In the Limit site storage to a maximum of box, type 1024.
7. In the Send warning E-mail when Site Collection storage reaches box, type 768, and then click
OK.
Task 2: Enable Self-Service Site Creation
1. Under Web Applications, click Manage web applications.
2. On the Web Applications Management page, click the row for SharePoint -
sharepoint.contoso.com80, and then on the ribbon, click Self-Service Site Creation.
4. In the Quota template to apply list, click Short Term Quota.
5. Under Start a Site, under The Start a Site link should, click Prompt users to create a site
collection under any managed path.
6. Under Site Classification Settings, click A required choice, and then click OK.
mysites.contoso.com80, and then on the ribbon, click Self-Service Site Creation.
9. Under Start a Site, under The Start a Site link should, click Display the custom form at, in the text
box, type http://sharepoint.contoso.com/_layouts/15/selfservicecreate.aspx, and then click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
sharepoint.contoso.com80, and then on the ribbon, click Permission Policy.
11. In the Manage Permission Policy Levels dialog box, click Add Permission Policy Level.
12. In the Add Permission Policy Level dialog box, in the Name box, type Self-Service Site Creator.
13. In the Description box, type Can use the self-service site creation feature.
14. Under List Permissions, locate the View Items permission, and then in that row, select the Grant
check box.
15. Under Site Permissions, locate the Use Self-Service Site Creation permission, in that row, select the
Grant check box, and then click Save.
16. In the Manage Permission Policy Levels dialog box, click OK.
17. On the ribbon, click User Policy.
18. In the Policy for Web Application dialog box, click Add Users.
19. In the Add Users dialog box, click Next.
20. In the Users box, type Everyone, under Permissions, select Self-Service Site Creator, and then click
Finish.
21. In the Policy for Web Application dialog box, click OK.
23. On the Start screen type Command Prompt, and then press Enter.
24. In the command prompt window, type iisreset /noforce, and then press Enter.
25. Close the command prompt window.
Task 3: Test Self-Service Site Creation
1. Log on to the 20332B-NYC-DB-13 machine as jim@contoso.com with the password Pa$$w0rd.
3. In the address bar, type http://sharepoint.contoso.com and press Enter.
4. In the Windows Security dialog box, in the User name box, type jim, in the Password box, type
5. On the SharePoint site, click Sites.
6. In the Windows Security dialog box, in the User name box, type jim, in the Password box, type
7. In the Get the most out of SharePoint dialog box, click No Thanks.
8. If the Were almost ready page appears, periodically click Sites, until the Sites page appears, this
may take several minutes.
9. On the Sites page, click new site.
10. On the Start a new site dialog box, in the Give it a name box, type My Project, in the Pick the
most appropriate policy list click Short Term Planning, and then click Create.
11. On the My Project site, click Settings, and then click Site settings.
12. On the Site Settings page, under Site Administration click Site Closure and Deletion.
13. On the Site Closure and Deletion page, verify that the site is scheduled for closure in 180 days.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L13-5

Results: After completing this exercise, you should have configured Self-Service Site Creation for the
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L14-1
Module 14: Upgrading and Migrating to SharePoint Server
2013
Lab A: Performing a Database-Attach
Upgrade
Exercise 1: Import the SharePoint 2010 Databases
Task 1: Restore the Managed Metadata Service database
1. Start the 20332B-NYC-DC-14 virtual machine. Wait for the virtual machine to display the logon, and
then wait a further five minutes before proceeding to the next step.
4. Log on to the 20332B-NYC-DB-14 virtual machine as Contoso\Administrator with the password
Pa$$w0rd.
6. In the Connect to Server dialog box, in the Server type drop-down menu, select Database Engine.
8. In the Object Explorer pane, right-click Databases, and then click Restore Database.
9. In the Restore Database dialog box, under Source, click Device, and then click the ellipsis ()
button.
10. In the Select backup devices dialog box, click Add.
11. In the Locate Backup File NYC-DB1 dialog box, browse to E:\Mod14, select ContosoMMS.bak,
and then click OK.
12. In the Select backup devices dialog box, click OK.
13. In the Restore Database dialog box, under Destination, in the Database drop-down list, verify that
ContosoMMS is selected.
14. Under Backup sets to restore, verify that ContosoMMS-Full Database Backup is selected, and then
click OK.
15. When the restore operation completes successfully, in the Microsoft SQL Server Management
Studio dialog box, click OK.
Task 2: Restore the Finance content database
1. In the Object Explorer pane, right-click Databases, and then click Restore Database.
2. In the Restore Database dialog box, under Source, click Device, and then click the ellipsis ()
button.
3. In the Select backup devices dialog box, click Add.
4. In the Locate Backup File NYC-DB1 dialog box, browse to E:\Mod14, select
WSS_FinanceContentDB.bak, and then click OK.
5. In the Select backup devices dialog box, click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
6. In the Restore Database dialog box, under Destination, in the Database drop-down list, verify that
WSS_FinanceContentDB is selected.
7. Under Backup sets to restore, verify that WSS_FinanceContentDB-Full Database Backup is
selected, and then click OK.
8. After the restore operation completes successfully, if the Microsoft SQL Server Management Studio
dialog box appears, click OK.
Task 3: Make the databases writeable
1. In the Object Explorer pane, expand Databases.
2. Right-click ContosoMMS (Read-Only), and then click Properties.
3. In the Database Properties ContosoMMS dialog box, in the Select a page list, click Options.
4. Under State, in the Database Read-Only row, click False, and then click OK.
5. In the Open Connections dialog box, click Yes.
6. Right-click WSS_FinanceContentDB (Read-Only), and then click Properties.
7. In the Database Properties WSS_FinanceContentDB dialog box, in the Select a page list, click
Options.
8. Under State, in the Database Read-Only row, click False, and then click OK.
9. In the Open Connections dialog box, click Yes.
10. Close SQL Server Management Studio.

Results: After completing this exercise, you should have restored a service application database and a
content database from backup files.

Exercise 2: Migrating and Upgrading a Service Application
Task 1: Start the Managed Metadata Web Service
Pa$$w0rd.
4. On the Services on Server page, in the Managed Metadata Web Service row, click Start.
Task 2: Register a new managed account
3. At the credential prompt, in the User name box, type CONTOSO\ContosoMMS.
4. In the Password box, type Pa$$w0rd, and then click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L14-3
Task 3: Create the Managed Metadata Service application
1. In the SharePoint 2013 Management Shell, at the command prompt, type the following command,
and then press Enter:
$AppPool = New-SPServiceApplicationPool -Name ContosoFinanceMMS -Account
CONTOSO\ContosoMMS
$mms = New-SPMetadataServiceApplication -Name "Contoso Finance Managed Metadata" -
ApplicationPool $AppPool -
DatabaseName ContosoMMS
New-SPMetadataServiceApplicationProxy -Name "Contoso Finance Managed Metadata" -
ServiceApplication $mms -DefaultProxyGroup
4. After the command completes successfully, close the SharePoint 2013 Management Shell.
Task 4: Verify that the service application database was upgraded successfully
3. In the list of service applications, click Contoso Finance Managed Metadata, and then click
Manage.
4. On the Term Store Management Tool page, under Contoso Finance Managed Metadata, expand
Organization.
5. Expand Department, and verify that the term set contains the following terms:
o Finance
o IT
o Marketing
o Sales
6. Expand Supplier, and verify that the term set contains the following terms:
o Litware, Inc.
o Northwind Traders
o Proseware, Inc.
o Trey Research

Results: After completing this exercise, you should have migrated a Managed Metadata Service
application from a SharePoint 2010 environment and upgraded it to SharePoint 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Exercise 3: Migrating and Upgrading a Content Database
Task 1: Add a DNS record for finance.contoso.com
1. Log on to the 20332B-NYC-DC-14 virtual machine as Contoso\Administrator with the password
Pa$$w0rd.
3. In the DNS Manager window, in the navigation pane, expand Forward Lookup Zones.
4. In the navigation pane, right-click Contoso.com, and then click New Host (A or AAAA).
5. In the New Host dialog box, in the Name text box, type finance.
6. In the IP address text box, type 172.16.1.21, and then click Add Host.
7. In the DNS message box, click OK.
Task 2: Create a new managed account
1. Switch back to the 20332B-NYC-SP-14 virtual machine. If you are not already logged on, log on as
CONTOSO\SPFinanceAppPool.
5. In the Password text box, type Pa$$w0rd, and then click OK.
Task 3: Create a web application to host the content database
2. Under Application Management, click Manage web applications.
3. On the ribbon, click New.
4. In the Create New Web Application dialog box, in the Port text box, type 80.
5. In the Host Header text box, type finance.contoso.com.
6. Under Application Pool, ensure Create new application pool is selected, and then in the
Configurable drop-down list, click CONTOSO\SPFinanceAppPool.
7. Under Database Name and Authentication, in the Database Name text box, type
WSS_FinanceContentDB_New.
8. Click OK.
9. When the new web application has been successfully created, in the Application Created dialog box,
click OK.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L14-5
Task 4: Attach the content database to the web application
Mount-SPContentDatabase -Name WSS_FinanceContentDB -DatabaseServer ContosoDB -
WebApplication http://finance.contoso.com
3. After the command finishes, close the SharePoint 2013 Management Shell.
Task 5: Verify that the migrated site collection is fully functional
2. In the Internet Explorer address bar, type finance.contoso.com.
4. Verify that the site collection loads successfully.
5. On the Finance home page, under Shared Documents, click ContosoP1AnnualReport.
6. In the Open Document dialog box, click OK.
8. Verify that the document opens successfully.
9. Close Word 2013.
11. In the list of documents, click the row containing Litware1.
12. On the ribbon, on the Documents tab, in the Manage group, click Edit Properties.
13. In the Invoices Litware1.docx dialog box, in the Contoso Department row, click Browse for a
valid choice.
Note: The Browse for a valid choice command is represented by an icon containing a pair
of tags.
14. In the Select: Contoso Department dialog box, click Marketing, click Select, and then click OK.
15. In the Invoices Litware1.docx dialog box, click Save.

Results: After completing this exercise, you should have migrated a content database from a SharePoint
2010 environment and upgraded it to SharePoint 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Lab B: Managing Site Collection Upgrades
Exercise 1: Preparing Site Collections for Upgrade
Task 1: Run site collection health checks from the browser
1. Switch back to the 20332B-NYC-SP-14 virtual machine. If you are not already logged on, log on as
5. On the Site Actions menu, click Site Settings.
6. Under Site Collection Administration, click Site collection health checks.
8. Verify that the health check detects problems in the following areas:
o Conflicting Content Types
o Customized Files
Task 2: Run site collection health checks from Windows PowerShell
Test-SPSite -Identity http://finance.contoso.com
3. Verify that the Test-SPSite cmdlet identifies the same issues as the browser-based health checks.
Task 3: Repair a site collection
Repair-SPSite -Identity http://finance.contoso.com
2. Verify that the Repair-SPSite cmdlet was unable to resolve all the outstanding issues.
3. Close the SharePoint 2013 Management Shell and switch back to Internet Explorer.
5. Under Galleries, click Site content types.
6. Under Digital Asset Content Types, click Video.
7. On the Video page, under Settings, click Name, description and group.
8. In the Name text box, delete the existing text, type Video_SP2010, and then click OK.
10. Under Site Collection Administration, click Site collection health checks.
12. On the Site Collection Health Check Results page, verify that the Conflicting Content Types check
ran successfully.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L14-7

Results: After completing this exercise, you should have prepared a site collection for upgrade.

Exercise 2: Upgrading Site Collections
Task 1: Create an upgrade evaluation site collection
1. In Internet Explorer on the 20332B-NYC-SP-14 virtual machine, on the Site Actions menu, click Site
Settings.
2. Under Site Collection Administration, click Site collection upgrade.
3. On the Site Collection Upgrade page, click TRY A DEMO UPGRADE.
4. In the Create Upgrade Evaluation Site Collection dialog box, click Create Upgrade Evaluation
Site Collection.
5. In the We've received your demo site request dialog box, click Close.
8. Click Monitoring, and then under Timer Jobs, click Review job definitions.
9. In the list of timer jobs, click Create Upgrade Evaluation Site Collections job. If the list shows more
than one instance of this timer job, click the one in which the Web Application column displays the
value SharePoint finance.contoso.com80.
11. On the Quick Launch navigation menu, click Application Management.
12. Under Site Collections, click View all site collections.
13. On the Site Collection List page, in the Web Application drop-down list, ensure that
http://finance.contoso.com is selected.
14. Notice that a site collection with the relative URL /sites/root-eval has been created.
Note: If the /sites/root-eval site collection is not listed, the timer job may not have finished
running. In this case, refresh the page periodically until the site collection is added to the list.
15. In the Internet Explorer address bar, type finance.contoso.com/sites/root-eval, and then press
Enter.
16. If the Windows Security dialog box appears, in the User name text box, type
CONTOSO\Administrator, in the Password text box, type Pa$$w0rd, and then click OK.
17. Verify that the site is displayed as a SharePoint 2013 team site.
18. In the Internet Explorer address bar, type finance.contoso.com, and then press Enter.
19. Verify that the original Finance site collection is unchanged.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
Task 2: Perform a site collection upgrade in Windows PowerShell
Upgrade-SPSite http://finance.contoso.com/ -VersionUpgrade -QueueOnly
Get-SPSiteUpgradeSessionInfo -ContentDatabase WSS_FinanceContentDB_New -ShowCompleted
-ShowInProgress -ShowFailed | select SiteId, Status, UpgradeType | Format-List
4. Verify that the status of the site upgrade shows as Completed.
Note: If the site upgrade status shows In Progress, periodically re-run the Get-
SPSiteUpgradeSessionInfo command until the status shows Completed.
$webapp = Get-SPWebApplication http://finance.contoso.com
$webapp.SiteUpgradeThrottleSettings
7. Verify that site collection upgrades are subject to the following limits:
The application pool is limited to five concurrent site collection upgrades.
Site collection administrators are prevented from upgrading site collections with more than 10MB of
content.
Site collection administrators are prevented from upgrading site collections with more than 10
subsites.
Task 3: Verify that the upgraded site collection behaves as expected
4. Verify that the site is displayed as a SharePoint 2013 team site.
5. On the Finance home page, under Shared Documents, click ContosoP1LaunchDeck.
6. In the Microsoft Office dialog box, click Yes.
8. Verify that the document opens successfully.
9. Close PowerPoint 2013.
11. Verify that the Contracts page is rendered as a SharePoint 2013 document library.
M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D
L14-9
13. Verify that the Invoices page is rendered as a SharePoint 2013 document library.

Results: After completing this exercise, you should have upgraded a site collection from SharePoint 2010
to SharePoint 2013.

M
C
T

U
S
E

O
N
L
Y
.

S
T
U
D
E
N
T

U
S
E

P
R
O
H
I
B
I
T
E
D

20332B ENU TrainerHandbook

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

20332B ENU TrainerHandbook

Încărcat de

Drepturi de autor:

Formate disponibile

M

S-ar putea să vă placă și