SharePoint 2013 Admin Manual

SharePoint 2013 Administrator Training Course
SharePoint Innovations, LLC

14631 SW Millikan Way
Beaverton, OR 97006
1-800-935-4245
training@sharepointinnovations.com
www.sharepointinnovations.com
Module 1 SharePoint 2013 Deployment Overview
Module 2 SharePoint 2013 Installation and Configuration
5
5
10
22
25
27
34
41
49
52
55
56
58
59
62
68
70
74
2.1 Task 1: Checking the Prerequisites to Install

2.2 Task 2: Server Farm Installation
2.3 Task 3: Configuring Service Applications using the Configuration Wizard
2.4 Task 4: Web Application and Site Collection Configuration
2.5 Task 5: Create MySite Web Application and Site Collection
2.6 Task 6: Creating a Front-end Portal
2.7 Task 7: Configuration of User Profile Service
2.8 Task 8: Configure Search Service Application
2.9 Task 9: How to Create a Content Source.
2.10 Task 10: Configure People Search
2.11 Task 11: Create a Crawl Rule
2.12 Task 12: Remove the Profile Store URL from the Default Content Source.
2.13 Task 13: Specify How to Crawl the Profile Store
2.14 Task 14: Install Workflow Manager
2.15 Task 15: Configure Workflow Manager using HTTP
2.16 Task 16: App Domain Setup and App Catalog Configuration
2.17 Task 17: Create an Isolated App Domain Using the GUI
Module 3 SharePoint 2013 Email Configuration
83
3.1 Task 1: Configure outgoing email

3.2 Task 2: Configure Incoming Email
83
85
Module 4 SharePoint 2013 Deployment Best Practices
89
Module 5 SharePoint 2013 Unified Search
90
5.1 Task 1:
5.2 Task 2:
5.3 Task 3:
5.4 Task 4:
Configure Result Sources

Create Search Center
Add Result Source to Search Center
How to Create Search Refiners
90
98
101
103
Module 6 SharePoint 2013 Enterprise Metadata Management
111
6.1 Task 1: Setup Managed Metadata Service

6.2 Task 2: Managing Metadata and Metadata Navigation Exercise
6.2 Task 2: Metadata Refinement Panel
6.3 Task 3: Content Search Web Part and Cross Site Collection Publishing
6.4 Task 4: Populate Product Hierarchy Term Set
6.5 Task 5: Setup an Asset Library
6.6 Task 6: Add Products to Catalog Site
6.7 Task 7: Share the Product list as catalog.
6.8 Task 8: Perform a Full Crawl
6.9 Task 9: Creating a Publishing Site Collection.
6.10 Task 10: Connect a Publishing Site Collection to a Product Catalog
6.11 Task 11: Adding a Content Search Web Part
112
114
122
132
134
139
142
146
148
150
151
154
Module 7 SharePoint 2013 PowerShell Introduction
159
7.1 Task 1: Cmdlets

7.2 Task 2: Objects
160
161
Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245
SharePoint 2013 Administrator Course Manual
7.3 Task 3: SharePoint Structure

7.4 Task 4: Create an Intranet Using PowerShell
163
165
Module 8 SharePoint 2013 Site Administration
168
8.1 Task 1:
8.2 Task 2:
8.3 Task 3:
8.3 Task 3:
8.4 Task 4:
8.5 Task 5:
8.6 Task 6:
8.7 Task 7:
Customize User Permissions

Create New Permission Level
Create Security Group
Add Users to a Group
Remove Users from a Group
Create a New Group with Permissions
Delete a Group
Break Permission Inheritance
168
170
172
173
175
177
180
181
Module 9 SharePoint 2013 Office Web Apps
183
9.1 Task 1 - Install prerequisite software for Office Web Apps Server
9.2 Task 2 Install Office Web Apps Server
9.3 Task 3 Creating the Office Web Apps Server Farm
9.4 Task 4 Configure Office Web Apps for SharePoint 2013
184
185
186
188
Module 10 SharePoint 2013 Business Connectivity Services
190
10.1 Task 1: Create a Business Connectivity Service Application

10.2 Task 2: Give Permissions
190
202
Module 11 SharePoint 2013 SQL Reporting Services
205
11.1 Task 1: Install Reporting Services Add-in *Discussion Only as it is already setup on our server
11.2 Task 2: Register and Start the Reporting Services SharePoint Service
11.3 Task 3: Create a Reporting Services Service Application
11.4 Task 4: Creating Reports
206
207
208
211
Module 13 SharePoint 2013 Backup and Restore
219
Backup Architecture in SharePoint 2013

Recovery processes in SharePoint 2013
13.1 Task 1: Backup and Restore a Site Collection using PowerShell.
220
223
224
Module 14 SharePoint 2013 Governance
225
SharePoint Governance
14.1 Project and Operational Management
14.2 Development and Configuration
14.3 Infrastructure
14.4 Operational Concerns
14.5 Education and Training
14.6 Navigation, Taxonomy, and Search
225
226
229
231
232
233
234
Module 15 SharePoint 2007 to SharePoint 2010 Migration
236
In-place upgrade Key Points

Database Attach Upgrade Key Points
Migration Key Points
Migration Steps
In-Place Upgrade Steps
Database Attach Steps
236
238
239
241
241
242
Module 16 SharePoint 2010 to SharePoint 2013 Migration
243
16.1 Task 1: Upgrade to SharePoint 2013
252
MODULE 1 SHAREPOINT 2013 DEPLOYMENT OVERVIEW

This module is a PowerPoint presentation by the instructor.
It will cover the following functional areas:
SharePoint 2013 Enterprise Product Architecture
SharePoint 2013 Best Practice Software, Hardware and Virtualization Requirements
SharePoint 2013 6 Major Enterprise Functional Areas
SharePoint 2013 Farm and Service Application Architecture
SharePoint 2013 Editions and Licensing Overview
MODULE 2 SHAREPOINT 2013 INSTALLATION AND CONFIGURATION

2.1 Task 1: Checking the Prerequisites to Install
Installing SharePoint 2013 on your virtual machine.
The installation of SharePoint 2013 is basically a three-part process:
Install prerequisites files from media (DVD) onto your hard drive.
Configure installed applications, Central Administration Module and create
a SharePoint web site.
Customize SharePoint to your unique environment.
After you have completed setup and the SharePoint Products Configuration
Wizard, you will have installed binaries, configured security permissions,
configured registry settings, configured the configuration database, configured the
content database, and installed the SharePoint Central Administration web site.
Next, you can choose to run the Farm Configuration Wizard to configure the
farm, select the services that you want to use in the farm, and create the first site
collection, or you can manually perform the farm configuration at your own pace.
During this class we will use a server built on remote physical servers called
virtual machines to learn how to install and administer SharePoint 2013.
Installation of SharePoint 2013 on your own server follows this method, with
exceptions being that you will use your own file names and passwords.
SharePoint 2013 includes a prerequisites installer application, which ensures that
SharePoint has all the necessary software components to operate.
Note: When executing any of the installation applications for SharePoint 2013, be sure to
run as an elevated privilege administrator if you have Windows User Account Control
enabled. See the following link on Windows UAC:
http://windows.microsoft.com/en-US/windows-vista/What-is-User-Account-Control
Log into your server with the credentials provided by the instructor.
1. Open Remote Desktop.
2. Enter the IP address provided.
3. Enter the user name: Administrator and Password: trainingdan49$.
The prerequisites installer is available on the desktop in the SharePoint Setup
folder and is named PrerequisiteInstaller.exe. Executing this application with no
command-line argument parameters will present you with the dialog shown
below:
1. Click Next.
The prerequisites installer does not require all the packages to be available on the
server before installing them and will attempt to download any package before
installing. Of course, in certain scenarios, automatic download of software may
violate company policy in a secure environment, so the prerequisites installer
allows the administrator to choose which packages to install using the command
line, by providing the path to previously downloaded packages.
For the purposes of this class, the Prerequisites have already been installed to
save time and bandwidth.
1. 2.1.1 Best Practice Service Accounts
During this course we will use the following service accounts to install and
configure our SharePoint 2013 platform.
Service Account Name
Purpose
SQL Server Service

Account
The domain user account for running SQL Server and SQL
Server Agent.
Example: TPILEARN\sp_sql
In the class to save time, we will be using
TPILEARN\Administrator
Setup User Account
The domain user account for installing SharePoint 2013 on

each server and running the Configuration Wizard; this
account should have local administrator privileges on the
server and have access to the SQL Server as part of the
securityadmin and dbcreator roles.
In the class to save time, we will be using
TPILEARN\Administrator
Server Farm Account
The domain user account nominated as the database

account during execution of the Configuration Wizard;
you do not need to apply specific permissions to this
account, as the Configuration Wizard will take care of
granting this account access to the SQL Server databases
and configuring the SharePoint Timer Service, Code Host
Service, and Central Administration site application pool.
After configuration, the farm account is a member of the
following security groups on the local server:
IIS_IUSRS
WSS_ADMIN_WPG
WSS_WPG
WSS_RESTRICTED_WPG
Performance Log Users
Performance Monitor Users
The farm account also has the following local

security policy rights:
Adjust memory quotas for a process
Logon as a service
Replace a process-level token
Example: TPILEARN\spfarmadmin
Application Pool
Account
The domain user to run all SharePoint web site applications

in the farm; do not grant any explicit privileges you may
have several managed accounts (one for each web
application) in the farm, but only need one domain user
account.
Example: TPILEARN\sp_services
Search Crawl Account
The domain user account with no explicit privileges to crawl

content for content
User Profile
Synchronization
Account
This account must have domain replication rights for UPS

to operate correctly:
Example: TPILEARN\spups
Business Intelligence
Account
The domain user account and trusted account for

Reporting Services and Performance Point when not using
Kerberos; grant database access as appropriate to access
external content. (optional):
Example: TPILEARN\sp_bi
Cache Super Reader
The object cache stores properties about items in

SharePoint Server 2013. Items in this cache are used by the
publishing feature when it renders web pages.
Example: TPILEARN\SP_CacheSuperReader
Cache super User
The object cache stores properties about items in

SharePoint Server 2013. Items in this cache are used by the
publishing feature when it renders web pages.
Example: TPILEARN\SP_CacheSuperUser
You can find these service accounts in your Active Directory as shown below:
2.2 Task 2: Server Farm Installation

Using the Products Installation Wizard:
1. Click the Server Farm Installation option in the dialog box. After choosing
the Server Farm Installation option, the setup application begins installation.
2. Enter the Product Key and click Continue.
10
3. Accept the Software License Terms and click Continue.
11
4. Under Server Type select Complete .

Note: In your production environment you can install SharePoint on a different drive.
12
The installation of SharePoint begins.
13
5. Leave the Run the SharePoint Products Configuration Wizard box check
box checked.
6. Click Close to configure your new SharePoint farm or join this server to an
existing farm.
If you uncheck the option to run the Configuration Wizard now (if you are
installing binaries on multiple WFE servers first), you can execute the
Configuration Wizard from the SharePoint Products group in Windows Start
menu.
14
7. The configuration process begins. Click Next.
8. Click Yes.
15
9. Check Create a new server farm and then Next.
10. Type tpserver for Database server and type TPILEARN\Administrator as the
setup farm account Username. This account will have the most access to the
SQL server.
16
The dialog box that follows asks for the passphrase for the installation.
SharePoint requires the passphrase later when adding additional servers to
the farm or removing existing servers from the farm, so be sure to keep the
passphrase safe. You may change the passphrase later with PowerShell, but
retrieving the passphrase is impossibleyou may only reset it.
11. Enter the passphrase: trainingdan49$
17
You will now be asked for the port number and authentication type for the
Central Administration Web Application. It will create the Central
Administration on its own. Like any other website running on SharePoint,
Central Administration is a special website running its own web application
within IIS (Internet Information Server). The Configuration Wizard will
suggest a port for the Central Administration web site, based on a random
available port on the server.
Its recommended to override the chosen port with 11111 as an easy to
remember port number. The Configuration Wizard creates a new IIS Web
Application on the server at the following location:
C:\InetPub\wwwroot\wss\VirtualDirectories\{PortNumber}.
12. Enter 11111 under Specify port number:
18
Options for security include NTLM or Kerberos. NTLM (Windows ChallengeResponse Authentication) is the typical choice in most installations as this is
the default Windows authentication type for most applications. However, if you
are familiar with Kerberos and have this authentication mechanism configured
in your infrastructure, then feel free to use it here.
Before proceeding with the configuration, the Configuration Wizard provides
a summary of the configuration you entered; changing them later potentially
involves removing the server from the farm and going through the
Configuration Wizard steps again
13. Double-check these values and click Next.
19
Once the Configuration Wizard starts the provisioning process, you should
not interrupt it, unless you need to cancel the operation and start again. A
failed provision process leaves stale databases and configurations in SQL
Server, which you should remove before attempting another run at
configuration. The Configuration Wizard completes several steps
(approximately ten) in the process, which include creating databases, creating
new IIS web applications, etc.
The provisioning process in operation.
20
Once complete, the Configuration Wizard should show a dialog box like that
below. If, on the other hand, the wizard encounters a problem, it will show an
error message and a link to the log file, so you may troubleshoot what caused
the error.
21
2.3 Task 3: Configuring Service Applications using the Configuration Wizard

For this class, we will be installing only the necessary services account to get
central administration to work properly. We will then configure the rest of the
services manually.
The purpose of this section is to install basic services needed to run SharePoint
2013 and Central Administration, using the configuration wizard. The
configuration wizard has the ability to install and configure all SharePoint services
automatically.
Typical services that need to be provisioned first are:
App Management
Secure Store Service
State Service
Usage and Health data collection
Application Search Service
Application Discovery and Load Balancer Service (created by wizard)
Secure Toke Service (created by wizard)
22
1. Click Start the Wizard.
2. Click on Create new managed account to begin the process.

3. Type User name TPILEARN\sp_services and Password trainingdan49$
23
4. Make sure all you only select the services checked in the images.
App Management
Secure Store Service
State Service
Usage and Health data collection
5. Once you have them all checked, click OK.
SharePoint 2013 will then configure these web applications automatically and
associate the services to it.
24
2.4 Task 4: Web Application and Site Collection Configuration

Once the wizard is done creating service applications, you will be prompted to
create a Site Collection. This will be the default site collection for the default web
application.
1. In the Title box, type HOME.
2. Under Select Template, choose Team Site under the Collaboration tab.
3. Click OK.
25
Once the site collection is created, you should see this screen. This indicates
that the configuration process is complete.
26
2.5 Task 5: Create MySite Web Application and Site Collection

In order to continue to configure the service applications, we need to create a
MySite web application and its pertinent site collection. The particular service
application that requires this is the User Profile Service.
Lets look into Central Administration. Click Application Management on the
far left.
1. Click Manage Web Applications.
2. Click New in the Ribbon to create a new web application.
27
SharePoint will show a dialog with a form for you to enter details about the new
web application.
1. Enter a name under Create New Web Application: Mysites-80.
2. Enter the Port number for the new mysites web app: 80
3. Enter the Host Header as mysites. The Host Header is the URL or address
that will identify the web application in the web browser.
28
You can either create a new web application pool for this web app or you can use
an existing one. We will use an existing one.
4. Select SharePoint 80 from the existing application pool.
5. Under Database Server, enter the name of the SharePoint database server:
tpserver
6. Under Database Name, remove the long GUID and replace it with mysites at
the end. The Database Name should be wss_content_mysites.
29
7. Click OK to create your new web application.
The web application list page should now show your new mysite web
application we just created called Mysites-80.
30
We are now ready to create the mysite site collection, which is needed to create
the User Profile Synchronization service.
10. In Central Administration, click on Application Management on the left.
11. In Application Management click on Create site collections.
31
The Create New Site Collection menu will be displayed.

12. Under Web Application make sure Mysites is selected.
13. Under Title and Description give the site collection a title: Portal. Enter portal
for the URL, too
14. IMPORTANT- Under Template Selection please make sure you select My
Site Host which is located under the Enterprise tab.
32
15. Under Primary Site Collection Administrator type in
TPILEARN\administrator in the User name box.

16. Under Secondary Site Collection Administrator type in spfarmadmin in the
User name box.

17. Click OK to create your new site collection.
You have now created the Mysite web application and site collection. The next
section will go into more detail on how to create a web application. Click OK.
33
2.6 Task 6: Creating a Front-end Portal

The purpose of this exercise is to create a SharePoint 2013 front-end web
application and site collection for team collaboration under a host header and port
number 80.
Host Header/Name: intranet.contoso.com
Port Number: 80
1. From Central Administration, click on the Manage Web Applications link.
The next page shows a list of already configured web applications, which
includes Central Administration and possibly the My Sites host application.
2. Click the New icon in the Ribbon to create a new web application.
34
3. Complete the details for IIS, the Name of the web application Port number,
and Host Header as shown below.
35
4. If you have preconfigured a SSL certificate for your web application and
domain name, you may select to use SSL, otherwise leave this option set to
No.
5. If you plan to allow public access to your site, or parts of your site, click Yes to
Allow Anonymous Access (you will need to allow this in the site collection
also).
6. SharePoint 2013 now insists on Claims-Based-Authentication for web
applications, and no longer supports Classic Mode. Enable Windows
Authentication and configure any ASP.NET membership providers and/or
third-party trusted claims providers.
36
It is recommended to use the default sign-in page and change this to a custom
page later, once the application is up and running.
7. Leave the Public URL and Zone as default.
8. Select an existing Application Pool. Use SharePoint
80(TPILEARN\SP_Services)
9. Provide the name of a new Content Database (INTRANET) and database
authentication as Windows.
37
10. Leave Failover database empty (unless you have a failover in place).
11. Choose your service application group (or default if you have none defined).
12. Choose whether to enroll in the Customer Experience Improvement
Program.
13. Click OK and wait a few seconds while SharePoint creates your new web
application.
38
We are now ready to create the intranet site collection

14. In Central Administration, click on Application Management on the left.
15. In Application Management click on Create site collections.
The Create New Site Collection menu will be displayed.

12. Under Web Application make sure intranet.contoso.com is selected.
13. Under Title and Description give the site collection a title: Home. Enter portal
for the URL, too
14. Under Template Selection select Team Site which is located under the
Collaboration tab.
39
15. Under Primary Site Collection Administrator type in

TPILEARN\administrator in the User name box.
16. Under Secondary Site Collection Administrator type in spfarmadmin in the
User name box.
17. Click OK to create your new site collection.
You have now created the intranet.contoso.com web application and site
collection. Click OK.
18. Go to C:\Windows\System32\Drivers\ETC\ and edit the host file using
Notepad.
19. Add the local address 127.0.0.1 intranet.contoso.com of the new web
application you just created.
40
2.7 Task 7: Configuration of User Profile Service

Now we will create a User Profile Service to synchronize user information from
the Active Directory to SharePoint.
1. Go to the Central Administration home page and click on Manage service
applications under Application Management.
2. In the Ribbon click New and select User Profile Service Application.
41
3. Select Use existing application pool. Make sure the Database Server
name is correct and scroll down.
42
4. Type in your Profile Database Server name tpserver, Type the Database
Name UserProfile_DB and scroll down.
5. Verify your Synchronization Database Server name tpserver, Type the
Database Name UserProfileSync_DB and scroll down.
6. Verify your Social Tagging Database Server name tpserver, Type the
Database Name UserProfileSocial_DB and scroll down.
7. Select the server you wish to run the Synchronization Service on, which is
tpserver, and enter your My Site Host address, which is http://mysites/
43
8. Enter the Managed Path and site naming format. It is recommended to leave
all of these in default.
9. Select Default Proxy Group.

10. Click Create.
44
11. In order to start the services, go back to the Central Administration Home
Page and select Manage services on server under System Settings.
12. Start the User Profile Service by clicking on the Start link on the right as
shown in the screenshot below.
Here is the awesome part! You dont have to worry about the User Profile
Synchronization Service. You just need to reset IIS, go back to the Service
Application screen and click on the Service Application. You dont have to
worry about it, and that is mostly true as long as you are using Active
Directory
13. In order to configure the User Profile Synchronization, go to Manage
Service Applications and click on User Profile Synchronization, and then
click on Configure Synchronization Settings.
45
14. Select Use SharePoint Active Directory Import and click OK.
15. Click Configure Synchronizations Settings.
16. Next, click on Configure Synchronization Connections.
17. Click Create New Connection. Fill in the Connection Name TPILEARN.
18. Enter the Fully Qualified Domain Name for your domain: tpilearn.com.
19. Select your Authentication Provider Type, enter your Account Name and
Password.
20. Click Populate Containers.
46
21. In the pop-up box, select the Users, and click OK.
47
22. Click the Start User Profile Synchronization link on the User Profile
Service page.
23. Select Start Full Synchronization.
24. Click OK.
You should see Synchronizing next to Profile Synchronization Status after

a minute or so and then the following reports:
48
2.8 Task 8: Configure Search Service Application

1. Open Central Administration.
2. Click Manage service applications under the Application Management
heading.
49
3. In the Ribbon, click the pull-down arrow under New and choose Search
Service Application.
4. Under Search Service Account, click Register new managed account then
type: TPILEARN\sp_searchadmin and Password trainingdan49$, then click
OK
5. Enter Service Application Name of Search Service Application
50
6. In the Application Pool for Search Admin Web Service, Select Use
existing application pool and choose SharePoint Web Services Default.
7. In the Application Pool for Search Query Web Service, Select Use existing
application pool and choose SharePoint Web Services Default.
8. Click OK to proceed.
Now you should see Search Service Application 1.
9. Click on the row for Search Service Application 1.
10. In the Ribbon, click Manage.
Note the items on the Quick Launch are now search related.
51
2.9 Task 9: How to Create a Content Source.

1. Click on Content Sources in Search Administration.
2. Click the pull-down arrow and then click Edit.
3. Here we need to tell SharePoint what to crawl. Type in the following URL to
allow search to crawl the mysites web app: sps3://mysites/. * sps3 is a protocol
52
handler for searching user profiles. If the site used a SSL you should use
sps3s.
My Sites
4. Click Create Schedule and set how often you would like the sites to be
crawled. The settings should be set based on company needs or
requirements. The question that you should be asking is. How soon after a
document is uploaded to SharePoint will you need to search for that document?
5. Click OK at the bottom of the window.
6. On the Quick Launch, click Crawl Rules.
7. Click the link New Crawl Rule.
53
8. Fill in the form as seen below.
9. Click OK at the bottom of the form.
54
2.10 Task 10: Configure People Search

Now we will grant access to a user account to crawl the profile store.
1. Verify that the user account that is performing this procedure is an
administrator for the Search service application.
2. From the Start screen, click SharePoint 2013 Central Administration.
3. In Central Administration, from the Application Management section,
click Manage service applications.
4. On the Manage service applications page, click the row that contains the
User Profile service application.
5. Click to the right of the link to select the row, and then in the Ribbon,
click Administrators.
6. In the Administrators for User Profile Service Application dialog box, in

the To add an account box, type a user account in the
form TPILEARN\Sp_searchadmin.
7. Click Add.
55
8. In the Permissions list, select the Retrieve People Data for Search
Crawlers check box.
9. Click OK.
After you give the user account access to crawl the profile store, you must
create a crawl rule to specify that you want to use that account when you crawl
the profile store.
2.11 Task 11: Create a Crawl Rule

Use the following procedure to create a crawl rule:
administrator for the Search service application.
2. In Central Administration, in the Application Management section,
3. On the Manage Service Applications page, click the Search service
application for which you want to create a crawl rule.
4. On the Search Administration page, in the Quick Launch, in
the Crawling section, click Crawl Rules.
5. On the Manage Crawl Rules page, click New Crawl Rule.
6. In the Path section, in the Path box, type http://mysites/*
56
7. Click Use regular expression syntax for matching this rule if you want to use
regular expression syntax in the path.
8. In the Crawl Configuration section, select Include all items in this path.
9. In the Specify Authentication section, select Specify a different content
access account. It should be TPILEARN\sp_searchadmin.
10. Click OK.
57
2.12 Task 12: Remove the Profile Store URL from the Default Content Source.
SharePoint by default adds MySite URL to its crawl rules along with the front-end
websites. We are removing it and adding it as a separate crawl to separate
content sources for crawl scheduling and result source definitions.
administrator for the Search Service application.
3. On the Manage Service Applications page, click Search Service
Application.
the Crawling section, click Content Sources.
5. On the Manage Content Sources page, click the link to the default content
source (Local SharePoint sites).
6. In the Start Addresses section, remove the URL for the profile store
(http://mysites).
7. Click OK.
8. Click Content Source and create a new content source.
58
2.13 Task 13: Specify How to Crawl the Profile Store

Use the following procedure to create a content source that specifies how to crawl
the profile store. Verify that the user account that is performing this procedure is
an administrator for the Search service application.
2. On the Manage Service Applications page, click Search Service
Application.
the Crawling section, click Content Sources.
59
4. On the Manage Content Sources page, click New Content Source.
5. On the Add Content Source page, in the Name section, type a name for this
content source.
6. In the Content Source Type section, ensure that SharePoint Sites is

selected.
7. In the Start Addresses section, type the start address in the
form sps3://mysites and http://mysites.
8. In the Crawl Settings section, leave the default value of Crawl everything
under the host name for each start address.
9. In the Crawl Schedules section, do the following:
10. Select Enable Incremental Crawls.
NOTE-Continuous crawl automatically provides maximum freshness for the content source
without an incremental crawl schedule, but does take a lot of resources.
60
11. Create a schedule for full crawls.

12. Click OK.
61
2.14 Task 14: Install Workflow Manager

Workflows are another key area in SharePoint 2013 where Microsoft has made
great investments. In fact, workflow platform is completely new in that it allows
creation, usage and deployment of .NET Framework 4.5 workflows in a
SharePoint 2013 farm.
Microsoft has completely redesigned the workflow platform for SharePoint 2013
by creating the Windows Azure Workflow Server (WAS) that enables us to
completely separate the SharePoint side from the workflow one. Indeed, workflow
infrastructure in SharePoint 2013 is completely independent from the SharePoint
point of view that consumes and uses workflows through a web services faade.
Workflow infrastructure in SharePoint 2013 is not set up as part of the installation
process of the platform. You can install WAS in an independent server or in a
web frontend server after you have installed SharePoint 2013. There are two
options to install Workflow infrastructure for SharePoint 2013:
Use the Web Platform Installer available
at: http://www.microsoft.com/web/downloads/platform.aspx
Download and install the workflow individual components
from http://www.microsoft.com/en-us/download/details.aspx?id=35375
For this course, we will be using the first option above.
62
1. Install Workflow Manager by clicking install on the Web Platform Installer

package installer.
2. In the Searchboxof the Web Platform Installer search for workflow.
3. In the search results, click the Add button for the Workflow Manager 1.0 row.
4. Then, click the Install button.
The installation process will install Workflow Manager 1.0 and configure all the
necessary dependencies:
Execute ASP.NET IIS Registration Tool.
IIS Management Service.
Service Bus 1.0.
Microsoft Windows Fabric.
63
5. In order to start the installation process, click I Accept.
6. Once the installation process ends, you can start with the configuration as its
described in the Configure step tab of the wizard. Click the Continue button
so the wizard shows a summary window with all the components installed and
configured.
64
7. Once you have installed Workflow Manager 1.0, a configuration window wizard
is started. As you can see, there are three possibilities for configuring the
Workflow Manager. Just click the first one, the Default Settings configuration.
65
8. Click Test Connection to SQL server.

9. Connection should be successful. If it is not, please check your settings.
10. The configuration service account must be in Domain\username form. In our

case we are using the following credentials:
User ID= TPILEARN\administrator, password = trainingdan49$
11. Click Allow Workflow management over http. SSL is available but the user
of SSL certificates adds a layer of complexity here.
12. The certificate generation password we are going to use is: trainingdan49$
66
Wait for configuration process to run.
Configuration process should be successful.
67
Once Workflow Manager has been installed, we have to then register the
SharePoint 2013 farm to the new workflow manager process.
2.15 Task 15: Configure Workflow Manager using HTTP

1. Log on to the server in the SharePoint Server 2013 farm where Workflow
Manager was installed.
2. Open the SharePoint Management Shell as an administrator. This is
accomplished by right-clicking the SharePoint 2013 Management Shell and
choosing Run as administrator.
3. Run the Register-SPWorkflowService cmdlet.
NOTE: You may need to open Internet Information Services Manager to see
what port number was used when creating the Workflow Management Site.
4. If you have a multi server farm, log on to each Web Front End (WFE) server in
the SharePoint Server 2013 farm.
Each WFE server in the SharePoint Server 2013 farm must have the Workflow
Manager Client installed.
5. Install the Workflow Manager Client on each WFE server in the SharePoint
farm.
Note: When you install Workflow Manager on a WFE it automatically installs the Workflow
Manager Client on that WFE. You will still need to install the Workflow Manager Client on any
additional WFE servers. For example, if you have a farm that contains 5 WFE servers and
you install Workflow Manager on one of those WFE servers you will still need to install the
Workflow Manager Client on the 4 additional servers.
68
6. Once the service has registered you can check to see if it worked by opening
SharePoint Designer 2013:
Note: IF WORKFLOW IS INSTALLED ON A SEPARATE SERVER, WHICH IS NOT PART

OF THE SHAREPOINT FARM, YOU NEED TO DOWNLOAD AND INSTALL THE
WINDOWS AZURE WORKFLOW MANAGER CLIENT ON THE SHAREPOINT SERVER
WHICH YOU ARE CONFIGURING TO USE WORKFLOW
If registering the spworkflow service fails, one thing to try is to delete the
following folders:
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SharePoint.Workfl
owServices.Activities
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SharePoint.Workfl
owServices.Activities.Design
Re-run the register-spworkflow command again and it should work.
If you uninstalled and reinstalled SharePoint on the same server, those GAC
entries will never get removed by the installer process. You must manually
remove them to allow the service to register.
69
2.16 Task 16: App Domain Setup and App Catalog Configuration
In this subchapter, we will setup and configure an app domain and app catalog.
App domain is setup first, then app catalog.
The apps for SharePoint provides a new method to deliver specific information or
functionality to a SharePoint site. An app for SharePoint is a small, easy-to-use,
stand-alone productivity app that solves a specific end-user need.
Before you allow site owners to install apps in a SharePoint environment, you
must plan how you want to support them.
You have to determine your organization's policy around apps for SharePoint,
plan your configuration settings, and determine how to manage and monitor the
apps.
Create an isolated app domain using PowerShell
Ensure that the spadmin and sptimer services are running by opening a
command prompt, type in PowerShell to open PowerShell and typing the
following commands in PowerShell.
net start spadminv4
net start sptimerv4
Create your isolated app domain by running the SharePoint Management Shell as
an administrator and typing the following command.
PowerShell
Set-SPAppDomain "tpiapps.com"
Ensure that the SPSubscriptionSettingsService and
AppManagementServiceInstance services are running by typing the following
command in the SharePoint Management.
70
Verify that the SPSubscriptionSettingsService and

AppManagementServiceInstance services are running by typing the following
command in the SharePoint Management Shell. The output will indicate whether
each service is online.
PowerShell
Get-SPServiceInstance | where{$_.GetType().Name -eq
"AppManagementServiceInstance" -or $_.GetType().Name -eq
"SPSubscriptionSettingsServiceInstance"}
You must specify an account under which the SPSubscriptionService and
AppManagementServiceInstance service instances will run. This account must be
a SPManagedAccount. You can create a SPManagedAccount by typing the
following command in the SharePoint Management Shell. (Youll be prompted for
the account domain\user and password.)
PowerShell
$account = New-SPManagedAccount
Specify an account, application pool, and database settings for the
SPSubscriptionService and AppManagementServiceInstance services by typing
71
the following code in the SharePoint Management Shell. If you created a

SPManagedAccount in the preceding step, use that account name here.
PowerShell
$account = Get-SPManagedAccount "tpilearn\administrator"
$appPoolSubSvc = New-SPServiceApplicationPool -Name
SettingsServiceAppPool -Account $account
$appPoolAppSvc = New-SPServiceApplicationPool -Name AppServiceAppPool Account $account
$appSubSvc = New-SPSubscriptionSettingsServiceApplication ApplicationPool
$appPoolSubSvc Name SettingsServiceApp DatabaseName
SettingsServiceDB
$proxySubSvc = New-SPSubscriptionSettingsServiceApplicationProxy
ServiceApplication $appSubSvc
$appAppSvc = New-SPAppManagementServiceApplication -ApplicationPool
$appPoolAppSvc -Name AppServiceApp -DatabaseName AppServiceDB
$proxyAppSvc = New-SPAppManagementServiceApplicationProxy ServiceApplication $appAppSvc
Specify your tenant name by typing the following code in the SharePoint
Management Shell.
PowerShell
Set-SPAppSiteSubscriptionName -Name "app" -Confirm:$false
After you create your isolated app domain, perform the steps in the following
procedure to add that domain to your bypass list in Internet Explorer. This
ensures that you can navigate to this domain after you deploy a SharePoint-
72
hosted app. You can skip this procedure if your environment does not use a
proxy server.
1. Add your isolated app domain to your bypass list in Internet Explorer
2. In Internet Explorer, go to Tools.
3. Choose Internet options.
4. On the Connections tab, choose the LAN Settings button.
5. Clear the Automatically detect settings check box.
6. Select the Use a proxy server for your LAN check box.
7. Choose the Advanced button, and then add *.YourAppDomain.com to
the Exceptions list.
8. Choose the OK button.
9. Choose the OK button to close the Local Area Network (LAN)
Settings dialog box.
10. Choose the OK button to close the Internet Options dialog box.
73
2.17 Task 17: Create an Isolated App Domain Using the GUI
Now we will create a Forward Lookup zone for your App domain.
1. Go to Start.
2. Click on Programs then Administrative Tools.
3. Select DNS.
74
4. Right click Forward Lookup Zones and select New Zone
5. Click Next.
75
6. Keep the default and click Next again.
7. In most cases, especially if your development server is in its own domain you
can use the default on the next tab again and can just click Next.
76
8. You now have to specify a zone name. Its up to you what you choose here.
My domain name is tpilearn.com and for my app domain I will use
tpiapps.com.
9. Click Next.
10. Click Next.

11. Click Finish.
77
12. Right click on your new zone and select New Alias (CNAME)
13. Fill in a * for Alias name (uses parent domain if left blank)
14. Click Browse.
15. Double click on your server name.
16. Double click Forward Lookup Zones.
17. Double click the domain of your SharePoint environment. In my case this is
tpilearn.com.
18. Select (Same as parent folder) and click OK.
19. Click OK.
Note: Selecting the FQDN of the domain in here will only work in single server scenarios. If
you are using more than one server you should be pointing to the DNS record of the web
server in here. This is either the DNS record for the web server, or the DNS record of the
primary cluster address for NLB environments.
78
You are now done setting up your DNS and it should look like this:
20. Open Central Administration and click on Apps link.

21. Next, click on Configure App URLs:
79
3. 2.17.1 Create an App Catalog Site Collection for a Web Application
1. In Central Administration, on the Apps page, in the App Management

section, click Manage App Catalog.
If no App Catalog exists for the farm, the Web Application page opens, so
you can select a web application.
2. On the Web Application page, select the web application for which you want
to create a catalog.
3. In the App Catalog Site section, select Create a new app catalog site, and
then click OK.
4. On the Create App Catalog page, in the Title box, type a title for the App
Catalog site.
80
5. In the Description box, type the description for the site.

6. In the URL box, fill in the URL to use for the site.
7. In the Primary Site Collection Administrator section, in the User Name box,
type the user who will manage the catalog.
Only one user name can be entered. Security groups are not allowed.
8. In the End Users section, in the Users/Groups box, type the names of the
users or groups that you want to be able to browse the catalog.
Added users or groups have read access to the App Catalog site. You can
add multiple user names and security groups. Users must be added as End
Users to be able to browse the App Catalog from their site collections.
9. In the Select quota template list box, select the quota template to use for the
site.
10. Click OK.
Note: You are now ready to deploy your apps. Because of all this extra domain stuff though
there are a few things you should know about your web applications and site collections.
If you are using a host header for your web application apps wont just work for that web
application. Because of how the redirect for the app domain works IIS will try to resolve the
app URL by using the default IIS web site, which of course doesnt work. If you want to use
host headers for your web applications you have to create an extra web application that is
listening on port 80 (or 443 if you are using https) and that doesnt have a host header.
This means that you have to create a web application like you normally would. You have to
make sure that you select port 80 (or 443 if you are using https) and you should not fill in a
host header. Note that you have to stop the Default Web Site in IIS in order to be able to do
this. The web application will use the server name as its URL. The web application can be
empty except for a root site collection.
Another option is to use web applications without host headers and to create Host Header
Site Collections. Be aware that Host Header Site Collections cannot be created via the user
interface, they can only be created by using PowerShell.
Additional Considerations:
There are of course a number of key additional considerations that you should be aware of
when it comes to SharePoint Apps:
Note: A few of these additional considerations are extrapolated from Steve Peschkas post
here: Planning the Infrastructure Required for the new App Model in SharePoint2013 and
simplified for the sake of this post, go take a look if you need more context and detail.
81
Apps do not support Kerberos since each App runs in its own isolated domain, for
Kerberos to work we would need to configure SPNs for every App which is not
feasible! Therefore even with Kerberos enabled for your Web Applications, SharePoint Apps
rely on being able to fall back to NTLM.
SharePoint-hosted Apps do not support SAML auth currently SharePoint-hosted Apps will
not be redirected to correctly when using SAML auth. This is because most identity
providers (ADFS 2.0 included), do not support wildcards for return URLs which would be
needed due to the isolated domain model implemented for SharePoint-hosted Apps. In
addition, SharePoint does not currently support wildcards in the realm registration
process. However, Azure hosted, or provider-hosted Apps will work when SharePoint is
configured to use SAML auth but there is some configuration required, which Steve
Peschka covers off in quite some detail here: Using SharePoint Apps with SAML and FBA
Sites in SharePoint2013.
Apps do not support multiple zones all requests will only ever be served out of the default
zone. If you need multiple URLs for SharePoint, you should consider using host header site
collections with multiples URLs a new feature in SharePoint2013 rather than multiple
zones and Alternate Access Mappings (AAMs). Check out the Set-SPSiteUrl cmdlet for
more detail.
82
MODULE 3 SHAREPOINT 2013 EMAIL CONFIGURATION

3.1 Task 1: Configure outgoing email
You must first identify the SMTP server that you would like to use. You can
achieve this through the Exchange Server or a local SMTP service.
To configure outgoing email for a farm by using Central Administration
1. In Central Administration, click System Settings.
2. On the System Settings page, in the E-Mail and Text Messages (SMS) section, click
Configure outgoing e-mail settings.
3. Type tpserver in the Outbound SMTP server box.

4. In the From address box, type Info@contoso.com
5. In the Reply-to address box, type Info@contoso.com.
6. Click OK.
83
You can also configure outgoing email for a specific web application
1. Click Application Management, then click Manage web applications.
2. Select the Intranet-80 row from the list of web applications.

3. Select General Settings drop down group on the ribbon, then click Outgoing E-mail.
The name of the Outbound SMTP server, from address, Reply-to address and Character set
should be set to the previously entered settings.
4. In the From address box, change it to intranet@contoso.com.
5. In the Reply-to address box, change it to intranet@contoso.com.
6. Click OK.
84
3.2 Task 2: Configure Incoming Email

Verify that the user account that is performing this procedure is a member of the Administrators
group on the server that is running the SharePoint Central Administration website.
The first thing that we need to do is setup a SMTP server if one is not already setup.
SMTP Setup
1. Click the Server Manager button on the bottom of the Windows task bar.
2. Click Manage, then click Add Roles and Features.
85
3. Click Next.
4. Continue to click Next until you get to Features.

5. Scroll down and check SMTP.
86
6. Click Add Features.
7. Click Next.
8. After installation is complete, click Close.
Configure Incoming E-mail Settings
1. Click System Settings.
2. Click the Configure incoming e-mail settings link.
87
3. In the Enable Incoming E-Mail section, click Yes.

4. Select the Automatic settings mode.
5. In the Incoming E-Mail Server Display Address section, in the E-mail server display
address box, verify that tpserver.tpilearn.com is listed.
6. Use the default settings for all other sections, and then click OK.
88
MODULE 4 SHAREPOINT 2013 DEPLOYMENT BEST PRACTICES

This module is a PowerPoint presentation by the instructor.
It will cover the following functional areas:
SharePoint 2013 Information Architecture
SharePoint 2013 Service Application Best Practices
SharePoint 2013 Security Best Practices
SharePoint 2013 Web Applications, Site Collections, Quotas and Content Database
Best Practices
89
MODULE 5 SHAREPOINT 2013 UNIFIED SEARCH

This module includes a PowerPoint presentation by the instructor.
The FAST search technology, acquired by Microsoft in 2008, is at the heart of
SharePoint 2013. Technologies and ideas from Bing and elsewhere have been
added to the mix to provide a comprehensive set of enterprise search capabilities,
with plenty of room for customizations. It includes a rules-based query parsing
framework.
SharePoint 2013 has done away with Search Scopes and replaced them with
Result Sources. Search Scopes used to allow us to refine search results returned
from an index so that we could scope the results for a particular scenario. For
example, a search scope might restrict search results of a particular sub-site and
below in a site collection, so that users who use this scope in their search only
see results for a narrow set of content. Result Sources provide a similar function
to Search Scopes, only with greater control over the filtering.
Result Sources effectively combine Search Scopes and Federated Locations,
which existed in SharePoint 2010. Open Search is interesting in that we can
request Result Source from other search engines that support the 1.0/1.1
protocol.
The Result Source type applies to either SharePoint Search Results or People
Search Results. SharePoint treats these types of searches as distinctly different
and applies different Result Sources to each accordingly.
5.1 Task 1: Configure Result Sources

We will configure a Result Source to show Managed Metadata in the refiner
panel, specifically to filter PDFs.
1. Go back to Central Administration.
2. Click on Manage Service Application.
90
3. Scroll down and click on the Search Service Application to get to the Search
Administration Page.
4. Clicking on the Result Sources link in the left navigation shows a page like
the one below. SharePoint provides a number of result sources, based on
what users typically search. To call out a few, looking down the list we see
Pages, Documents, Pictures, Local People Results, etc.
91
To understand how a Result Source works, we shall now explore one of them
by clicking the name and selecting the view option in the popup menu.
5. Click on the Local People Results entry.
6. Click the New Result Source link.
92
7. Enter the Name as PDF Results.

8. Choose Local SharePoint to scope results from SharePoint content in the
Search Service Application local index. Leave all options default.
93
9. Click the Launch Query Builder button to configure the Query Transform.
The Build Your Query template opens.
The Query Builder understands both Keyword Query Language (KQL) and
FAST Query Language (FQL), which we use to define our Result Source
criteria. KQL and FQL provide superior query syntax to that of CAML
94
(Collaborative Application Markup Language), used in earlier versions of

SharePoint.
SharePoint 2013 inherits FQL from that of the FAST ESP, which Microsoft
included in the SharePoint 2013 platform.
The syntax available for KQL and FQL is vast, so here is a reference:
http://msdn.microsoft.com/enus/library/sharepoint/jj163973%28v=office.15%29
The keyword filter provides filter capabilities of the entered keywords of a
given search. For example, we can easily create a Result Source that lists
95
recent documents edited by the user performing the search, or include a

parameter from the query string in the search criteria.
10. In our example, we only need the Query from the search box selected from
the Keyword filter dropdown.
11. Once selected, click the button to Add keyword filter.
The Property filter allows you to apply additional filter properties to the search
query, such as the Content Type, Author, or one or many managed properties.
12. Add a Property filter called FileType and set Manual value to our content
source: pdf.
96
13. Click OK to return to the Result Source page.

14. Click Save to save the Result Source.
At this stage, you might be wondering how to use the Result Source in your search
results. Similar to how SharePoint 2010 allowed you to use scopes in Search Result
web parts, SharePoint also allows you to apply Result Sources to search result web
parts.
The ResultScriptWebPart now replaces the CoreResultsWebPart and provides
greater functionality. One of the more obvious improvements is previous
display, which SharePoint 2010 only provided with FAST. The
ResultScriptWebPart understands Result Sources like the
97
CoreResultsWebPart understood scopes. Lets demonstrate this behavior in

the following steps.
As a good practice, you should create a Search Center to centralize search for
various site collections this provides the added benefit of a single place to
apply search result branding.
5.2 Task 2: Create Search Center

1. Navigate to http://intranet.contoso.com Team Site.
2. Enable the Publishing Feature at the Site Collection level by clicking on the
Gear icon > Site Settings > Site Collection Features.
3. Activate the SharePoint Server Publishing Infrastructure feature.
98
4. Again, navigate to http://intranet.contoso.com and click on Site Contents.
5. At the bottom of the page, click + new subsite.
99
6. Give the new site a Title, Search.

7. The URL name extension should be search as well.
8. Under Select a template, choose Enterprise Search Center.
100
9. Make sure that Search is visible in the navigation bar by selecting Yes to the
question Use the top link bar from the parent site?
10. Click Create.
5.3 Task 3: Add Result Source to Search Center

1. From the main landing page of the Search Center, execute a search to
navigate to the results page.
To edit the page, we need to select the Search Results web part and then
edit the web part properties.
2. Click the Change query button.
101
You should see a Query Builder dialog appear (similar to that when creating a
Result Source).
Since you have a query builder in front of you, you can create some on the fly
query filtering.
3. Select the pdf results Result Source from the dropdown menu.
4. Click OK.
5. Click OK on the web part properties box and then Save the page.
6. Execute a search via the Search Center and the results returned are those
filtered by our Result Source.
102
5.4 Task 4: How to Create Search Refiners

When you open a SharePoint 2013 Search Center, you find a page like this:
The results shown on the left are Refiners. Basically, refiners are metadata
keywords by which you can filter your results.
When a catalog is crawled, SharePoint Server 2013 automatically creates
managed properties for all site columns that contain values. These automatically
created managed properties use the Text data type.
The Refinement Panel is a web part and it was available in SharePoint 2010.
However, creating and modifying search refiners was tedious. SharePoint 2013
improved the process by adding a graphical menu to add these refiners via
display templates.
Display templates control which managed properties are shown in the search
results, and how they appear in the Web Part. Each display template is made of
two files: an HTML version of the display template that you can edit in your HTML
editor, and a .js file that SharePoint uses.
103
In this exercise, we are going to create a new custom refiner that shows the item
count for all search results.
1. Navigate to http://intranet.contoso.com/search
2. Type * (asterix) in the search box to find all results.
This will take you to the result page show up below.
3. Edit this page by going to the Gear icon and putting the page in Edit mode.
104
The refinement panel is a webpart. To get to its settings we will have to edit
that webpart.
4. Click the small black arrow and select Edit Web Part.
5. Click on Choose Refiners...
105
Once you click on it, the refinement wizard will be displayed.
On the left side there's the list of available refiners (managed properties), on
the right side you can see your current selections. Of course, you can add and
remove as well as re-order the refiners here.
When you select a refiner in the list above, you'll see its configuration in the
bottom half of the screen. Things you can configure here:
Display name
Display template (see below)
Sort by
Sort direction (ASC / DESC)
Max number of refiner values
In order to create a refiner we will have to copy and create a new display
template based on the Filter_Default built in template. All display templates
are located in the Master Page Gallery section of your SharePoint site.
106
Create a new display template.

6. Go to Site Settings > Master Pages and Page Layouts.
7. Click on Display Templates.
8. Click on Filters.
9. Click on the dropdown menu for Filter_Default.HTML and download a copy to

you desktop.
10. Rename the file on your desktop to refinementwithcounts.html.

107
11. Open the file with Visual Studio 2012 or SharePoint Designer 2013.
12. Click on CTRL F and search for ShowCounts. The default is false.
13. Change ShowCounts to true.
14. Look for <title> and change the text to Refiner with Counts and save the file to
your desktop.
108
15. From Display Templates Filter page, click on the Ribbon and click Upload
Document from your desktop.
SharePoint will automatically create the corresponding .js file.

That's it. If you go back to the Refiner Panel's properties and open the
Display Template dropdown, you'll see the option Refiner Item with Count.
16. Select this for each refiner value for which you would like to see counts.
109
17. Run a search for * and see the results with item counts below.
110
MODULE 6 SHAREPOINT 2013 ENTERPRISE METADATA MANAGEMENT

Managed metadata is a hierarchical collection of centrally managed terms that
you can define, and then use as attributes for items in SharePoint Server 2013.
Basically, metadata is data about data.
Managed metadata makes it easier to use terms and enterprise keywords more
consistently. You can pre-define terms, and allow only authorized users to add
new terms. You can also prevent users from adding their own enterprise
keywords to items, and require them to use existing enterprise keywords.
Managed metadata also provides greater accuracy by presenting only a list of
correct terms from which users can select values. Because enterprise keywords
are also a type of managed metadata, even the enterprise keywords that users
apply to items can be more consistent.
SharePoint 2013 allows the use of Managed Metadata Navigation, a feature that
allows for SEO-friendly URLs and easy management of navigation via the term
111
set management tools. Say goodbye to /Lists/Posts/Post.aspx?ID=568 style

URLs!
6.1 Task 1: Setup Managed Metadata Service

Before we can use all the features of Managed Metadata we need to configure
the service application
1. Go to Central Administration
2. Click Manage service applications.
3. On the Ribbon click New, then click Managed Metadata Service.
112
4. Enter Managed Metadata Service into the Name field.

5. Database Server should be tpserver.
6. Enter Metadata_DB for the Database Name.
7. For the Application Pool, select Use existing and choose SharePoint Web
Services Default.
8. Click OK.
Now we need to start the Managed Metadata Web Service
113
9. Click Application Management, then click Manage Services on server.
10. On the Managed Metadata Web Service line click Start
11. The status should change to Started.
6.2 Task 2: Managing Metadata and Metadata Navigation Exercise

In this exercise we are going to covert the URL:
http://intranet.contoso.com/sitepages/it.asp to http://intranet.contoso.com/it
This change will allow our site to be more easily discovered by search engines.
1. Click on Site Settings.
114
2. Next, click on Navigation under Look and Feel.

NOTE: The SharePoint Server Publishing Infrastructure needs to be enabled for Navigation to be
displayed under Look and Feel.
You will find yourself in the Global and Current Navigation Settings menu.
The Global Navigation is the menu at the top and the Current Navigation is
the one on the left.
For each of these you can choose to use Managed Navigation or Structural
Navigation.
115
3. The one we are looking at today is Managed.
What we need to do next is create our Navigation items in the Term Store.
Lower in the page you will find an option to open the Term Store
Management Tool.
Note: If you get the error Failed to create term set: A default managed metadata service connection
hasn't been specified you may need to go to Central Admin, and the properties of the Managed
Metadata Service Connection and check This service application is the default storage location for
column specific term sets.
116
4. Click on Create Term Set and SharePoint will automatically create a Portal
Navigation Term Set.
5. Click on Open Term Store to edit the new Portal Navigation Term Set.
6. Create a navigation hierarchy by clicking Create Term under Portal

Navigation.
117
7. Type IT, HR and Engineering as sample navigation terms.
8. Click on a term (IT). The Term Properties page comes up.

9. Click on NAVIGATION.
You can choose between two Navigation Node Types:

Simple Link or Header
Term-Driven Page with Friendly URL
The Simple Link or Header is the more traditional hyperlink to an item or
create a heading to group links.
118
10. The Term-Driven Page with Friendly URL is a little more powerful as it
allows for friendly URLs. We will set the Friendly URL by moving to the next
tab for the term, Term-Driven Pages. There you will find options to change
119
the friendly URL as well as setting the target page for the hyperlink. (Can even
set SEO properties)
11. When the customize button is selected you can change the name of the URL
to whatever you want.
You can also change the target page of the term itself. This is useful for
creating custom navigation menus across your site collection without having to
create all the site first.
12. Click on Save when you are done.
13. Time to see the results, notice the new SEO friendly URL. Dont forget that we
are using the Managed Metadata Service (Term Store) which means you can
have more than one level in the navigation.
120
121
6.2 Task 2: Metadata Refinement Panel

1. Navigate to http://intranet.contoso.com/search
2. Type * (asterix) to do a wildcard search in the Search box and click Enter.
We will want to edit the results page to get the managed metadata refiner to
show.
3. From the Gear icon, select Edit page to put the search result page in edit
mode.
122
Once the page is in edit mode, we want to select the refinement web part at
the far left.
4. Click the dropdown icon and select Edit Web Part.
The Refinement panel menu opens at the right hand side of the screen.
123
5. Select Choose Refiners
124
In the Refinement Configuration menu we see all the built-in refiners.
125
6. Scroll down the Available refiners and look for owsmetadatafacetinfo and
Add it to the Selected refiners.
NOTE - If you want the managed metadata field to show up first, you can select it and click on Move
UP to the top of the list.
126
7. In the configuration for owsmetadatafacetinfo, type Managed Metadata next

to Display name.
8. Click OK to save.
127
9. Click Apply then OK in the refinement menu.
128
Once the web part menu closes you must save the changes to your page.
10. Click on Save in the ribbon.
Because we enabled publishing, this page is checked out and needs to be

checked in and published to be visible.
11. Click on the Check it in link in the yellow ribbon.
129
12. You can add version comments if you like, then click Continue.
13. Once it is checked in you can click on Publish this draft link to publish it to
the site and make it viewable to all readers without the yellow bar.
130
14. You can now do a search and the Managed Metadata refiner will show up on
the left above result type.
131
6.3 Task 3: Content Search Web Part and Cross Site Collection Publishing
Lets begin by creating an authoring site collection using the Product Catalog site
collection template.
1. Go to Central Administration.
2. Click on Create site collections.
3. Under Web Application, select http://intranet.contoso.com.

4. Name the site collection Product. The web site address should be prod.
132
5. Make the Primary Site Collection Admin Administrator and the Secondary
Site Collection spfarmadmin and click OK.
By choosing Product Catalog template, SharePoint will create the following
artifacts for the site collection automatically:
Cross Site Publishing feature
Product List associated with content type Product with Image
Two content types, Product and Product with Image
Site Columns
o Group Number
o Item Category [Managed Meta data column linked to Product
Hierarchy term set
o Item Number
o Language Tag
Site Collection Term Set Product Hierarchy
133
6.4 Task 4: Populate Product Hierarchy Term Set

This term set will be used for tagging terms for our catalog items.
1. To populate the term, click on the Gear icon and navigate to site settings in:
http://intranet.contoso.com/sites/prod
2. Under Site Administration, click on Term Store Management.
134
The Term Store Management Tool should be visible:
3. Expand Site Collection intranet.contoso.com-sites-prod and highlight Product

Hierarchy.
Managed Metadata is a taxonomy of terms, so to speak. We are going to

create our own taxonomy of products.
135
4. Click the small arrow mark next to Product Hierarchy.
5. Select Create Term from the dropdown menu to create the Parent Term:
6. Under the Products Term Set create the following Sub Terms by clicking
Create Term:
Computers
Laptops
Cameras
Phones
136
7. Once you have created the terms, click on the first term Computers and
create the following child terms by clicking Create Term:
Sony
HP
Toshiba
Apple
Acer
8. Click on Laptops and create the following Child terms by clicking Create Term.
Sony
HP
Toshiba
Dell
9. Click on Cameras and create the following Child terms by clicking Create
Term.
Cannon
Nikon
Sony
Samsung
10. Last, click on Phones and create the following Child Terms by clicking Create
Term.
Microsoft
Apple
Samsung
Sony
137
At this point your term store should look like this:
138
6.5 Task 5: Setup an Asset Library

This can exist anywhere as a container to store site blobs (Pictures, videos, pdfs,
etc.). In this case, the Asset library exists under authoring web application with
URL http://intranet.contoso.com/sites/prod.
1. To create an asset library click on Site Contents.
2. Then click add an app.
3. Select Asset Library from the choices.
139
4. Name the library Assets.
5. Upload all the images that are in your course materials files to this document
library by clicking on Upload Document in the Ribbon and then Upload Files
using Windows Explorer instead.
140
6. To conveniently access resources from our asset library, configure it as

Suggested Content Browser Location under Site Settings.
7. Navigate to http://intranet.contoso.com/sites/prod/Assets/ where the display

name should be Product Assets.
8. Click Save.
141
6.6 Task 6: Add Products to Catalog Site

After you have uploaded all the images to the asset library, we want to populate
the Products list that is created with the Catalog site.
1. Navigate to Products Site: http://intranet.contoso.com/sites/prod.
2. Click on + new item.
3. The new Item form should open.
142
4. Fill out the Item based on the screen shot below:

5. When you get to Rollup Image, select Click here to insert a picture from
SharePoint.
6. That will bring up a second form. In this form, browse for the image and select
the Assets Library we created.
7. Select the Windows-7-PC-For-sale.jpg from the asset library. Click Save.
8. Fill out another item based on the screenshot below and follow the same steps
as for the first item.
143
9. Finally, repeat one more time using the screen shot below as reference:
By now you should have 3 different Item Categories:

Computer Group number 1
Laptop Group number 2
Phones Group number 3
Optional: you can create more items with the rest of the images. Make sure
you distinguish your label each item category with the correct Group Number.
144
After you have imported your items into the list, you must also approve them.
10. To approve the items, select the item by clicking on the check box and in the
office ribbon under Items tab, click Approve/Reject.
11. In the Approve/Reject form, click Approve. Click OK.
Your Items are now approved.
145
6.7 Task 7: Share the Product list as catalog.

1. To share a list/library as a catalog, go to List Settings in the ribbon and click
on Catalog Settings.
2. In Catalog Settings configure the following:

Item Catalog is NOT enabled for Anonymous access
Item Number is a Primary Key
Navigation will be based on Item Category Managed Metadata Column
146
3. Click OK to share this list as a catalog.
Note: When a List/Library is selected as catalog an indexable property

[IndexedRootFolderPropertyKeys : {PublishingCatalogSettings, IsPublishingCatalog} namevalue pair is added to List's Property Bag. When a full crawl is completed this property is
added and crawl property and also added as Managed Property "IsPublishingCatalog".
147
6.8 Task 8: Perform a Full Crawl

1. To perform a full crawl, open Central Admin > Manage Service Applications
> Search Service.
2. Click on Content Sources.
148
3. Select Local SharePoint Sites and in the dropdown select Start Full Crawl.
Once Full Crawl is completed successfully, our catalog is ready to share with
publishing site collections.
149
6.9 Task 9: Creating a Publishing Site Collection.

1. To create a publishing site collection open Central Admin > Application
Management > Create Site Collection.
2. Give the site collection a name, Publishing.

3. The URL should be pub.
4. The Template should be Publishing > Publishing Portal.
150
6.10 Task 10: Connect a Publishing Site Collection to a Product Catalog

1. To connect to a published catalog go to Publishing Site Settings and under
Site Administration click on Manage Catalog Connections.
2. Select http://intranet.contoso.com/sites/prod/Lists/Products and click Connect.
151
3. Clicking on Connect will open the Catalog Source Settings page.

4. Change Navigation Hierarchy and select Root term of hierarchy, in this
case choose Products as this is our root term.
5. Click OK.
Note: A few points to note here, the Catalog Item URL Format, is using the Primary key
columns in URL Format and the interface is also creating a Category Page and Item Page.
152
At this point we are almost done with the setup of Managed Navigation.
6. Click on any category on the navigation link and it will show all products that
belong to the selected category.
153
6.11 Task 11: Adding a Content Search Web Part

Content search web parts are more powerful and flexible than content query
webparts. Besides being able to pull information from anywhere that is crawled,
you can also use refiners and multi-level sorting. Content search webparts use
154
display templates which are easier to customize than the XSLT format that
content query uses.
1. Browse to the page where you want to add the Content Search Web Part.
This can be Intranet.contoso.com.
2. Click the Settings menu, then click Edit Page.
3. Put your cursor in the area you want to add the Web Part.
4. From the Ribbon, select Insert.
5. In the Categories list, click Content Rollup.

6. In the Parts list, click Content Search, and then click Add.
155
7. In the Web Part, click the Web Part Menu, and then click Edit Web Part.
8. In the Web Part tool pane, click Change query. This will open a dialog box.
156
9. From the Select a query list, select your catalog result source. In our
scenario, it is Items Matching a Tag.
10. From the Restrict by app section, select Specify URL.
11. Add the URL: http://intranet.contoso.com/sites/prod
157
12. In the Restrict by tag section, select Restrict by current and child
navigation terms.
13. Click OK and Save the page.

The Content Search Web Part should now display products from the Prod
Site Collection.
The Content Search Web Part doesnt just display images, it can display any
kind of SharePoint object that has been indexed by Search. For example,
documents, list items, etc.
The queries that build these documents can be very simple (e.g. searching for
a particular word), or very complex (e.g. a query searching for documents of a
particular type, with particular properties, featuring certain keywords, filtered
based on the user profile of the person viewing the page), or somewhere in
between.
There are many pre-configured versions available, each with a specific type of
content. The more metadata your items have, the more options you will have
for using the Content Search Web Part.
158
MODULE 7 SHAREPOINT 2013 POWERSHELL INTRODUCTION

PowerShell is a task based command line shell and scripting language that will
help with administering and automating SharePoint. PowerShell will give you the
ability to complete tasks that would require multiple clicks in Central
Administration with a single command line and it will also make it easier to
perform repetitive tasks.
PowerShell uses cmdlets to command and manipulate objects. SharePoint has
over 500 cmdlets so it is important to know how to discover the cmdlets when you
159
need them or get help on the cmdlets that you know. You will in turn start to
memorize more and more cmdlets as you work with PowerShell.
7.1 Task 1: Cmdlets

Cmdlets follow the format of Verb-Noun and is also referred to as the ActionObject format.
1. Click Start
2. Next, Click Programs and hover over Microsoft SharePoint 2013 Products
3. Right click SharePoint 2013 Management Shell and click Run as
Administrator
4. In the SharePoint 2013 Management Shell, Type Get-Command, Hit Enter

on the keyboard
This will give you a list of commands available in PowerShell. Now lets display
only SharePoint cmdlets.
5. Type Get-Command noun SP* | more, Hit Enter on the keyboard
If you need help with a command you can use the following command line.
160
6. Type Get-Help Get-Command, Hit Enter on the keyboard
7.2 Task 2: Objects

Windows PowerShell returns objects and these object can have properties and
methods. Properties also called attributes represent data maintained by the
source. You can Get a property to retrieve data and Set a property to write data to
the source. Methods are actions that you can perform on objects. For example
the service object has the method of start and stop.
1. In the SharePoint Management Shell, type Get-Service, Hit Enter on the
keyboard.
PS C:\Users\Administrator> Get-Service
That will return all objects representing services on the computer.

2. Hit the arrow key up on you keyboard and add Name Sp* to the end of the
command, Hit Enter on the keyboard. That command will return all the
SharePoint related services.
PS C:\Users\Administrator> Get-Service Name SP*
At this point we have just displayed objects but have not done anything with
them. We will now us a method to start and stop one of the displayed
services.
161
3. In the SharePoint Management Shell, Type Get-Service SPTimerV4 | StopService and hit Enter. That will stop the Timer Service.
PS C:\Users\Administrator> Get-Service SPTimerV4 | Stop-Service
4. Type Get-Service Name Sp* and hit Enter to show that the service has been
stopped.
PS C:\Users\Administrator> get-service -name sp*
5. Type Get-Service SPTimerV4 | Start-Service and hit Enter.

PS C:\Users\Administrator> Get-Service SPTimerV4 | Start-Service
6. Type Get-Service Name Sp* and hit Enter to show that the service has been
started again.
PS C:\Users\Administrator> get-service -name sp*
162
7.3 Task 3: SharePoint Structure

Now we are going to explore the SharePoint logical structure with PowerShell.
SharePoint consists of the Farm, Web Applications, Site Collections, Sites, lists
and documents.
Farm
Get-SPFarm
Web Application
Get-SPWebApplication
Site Collection
Get-SPSite
Site or Subsite
Get-SPWeb
1. In the SharePoint Management Shell, type Get-SPSite

http://intranet.contoso.com | Get-spweb limit ALL and hit Enter on the
keyboard. This will display all sites in the intranet site collection.
PS C:\Users\Administrator> Get-SPSite http://intranet.contoso.com |
Get-spweb limit ALL
2. Type Get-SPWebApplication | Get-SPSite limit All | Get-spweb limit All and

hit Enter on the keyboard. This will display all sites and subsites from all Web
Applications
PS C:\Users\Administrator>
Get-SPWebApplication | Get-SPSite
limit All | Get-spweb limit All
163
Let look at how we can control how the list of site are displayed with selecting
the data that we want to display along with sorting and filtering the data.
3. Hit the Up arrow key on the key board, this will display the last command.
4. Next enter | Select-Object URL,WebTemplate and hit Enter. This will display
the same list but create two columns one for the URL and one for the Web
Template.
limit All | Get-spweb limit All | Select-Object URL,WebTemplate
5. Hit the Up arrow key on the keyboard, this will display the last command.
6. Next enter | Sort Webtemplate and hit Enter. This will display the same list but
sort the Web Template.
limit All | Get-spweb limit All | Select-Object URL,WebTemplate |
Sort Webtemplate
8. Next enter | Where-Object WebTemplate eq sts and hit Enter. This will
display just the STS (Team Site) WebTemplates.
Sort Webtemplate | Where-Object Webtemplate eq sts
You can also change the format and/or output of the data.
164
Operators
Less Than
-lt
Less than or equal
-le
Greater than
-gt
Greater than or equal -ge

Equal
-eq
Not equal
-ne
Like
-like
And
-and
Or
-or
10. Next enter | Format-List at the end of the command and hit Enter. This will
display the data in a list format rather than the default Table format.
Sort Webtemplate | Where-Object Webtemplate eq sts | Format-List
12. Delete | Format-List and type | Out-GridView and hit Enter. This will display
the data in an external dialog box for easy viewing and filtering.
Sort Webtemplate | Where-Object Webtemplate eq sts | Out-GridView
7.4 Task 4: Create an Intranet Using PowerShell

In this task we will be creating the structure for an intranet site including web
application, site collection, and sites. We will start by creating the Site Collection.
1. In the SharePoint Management Shell, type get-help new-spwebapplication
and hit Enter on the keyboard. This will display the syntax required and a
description of what cmdlet will do.
165
2. Type $ap=NewSPAuthenticationProvider
UseWindowsIntegratedAuthentication -DisableKerberos. This will define the
variable $ap as the new Authentication provided that we will reference in the
next command.
$ap=New-SPAuthenticationProvider UseWindowsIntegratedAuthentication -DisableKerberos
3. Type $ap=New-SPAuthenticationProvider UseWindowsIntegratedAuthentication -DisableKerberos

PS C:\Users\Administrator> New-SPWebApplication -Name "Contoso
Extranet" -Port 80 -HostHeader "extranet.contoso.com" -Url
"http://extranet.contoso.com:80" -ApplicationPool "SharePoint Web
Applications" -ApplicationPoolAccount (Get-SPManagedAccount
"TPILEARN\SP_Services") -DatabaseName "Content_Extranet" AuthenticationMethod NTLM AuthenticationProvider $ap
New Lets create a Site Collection for the Web Application that we just created
and then create multiple subsites.
1. In the SharePoint Management Shell, type New-SPSite
http://extranet.contoso.com Name Home Template STS#0 OwnerAlias
TPILEARN\Administrator and hit Enter on the keyboard.
PS C:\Users\Administrator> New-SPSite http://extranet.contoso.com
Name Home Template STS#0 OwnerAlias TPILEARN\Administrator
Next we can check to see if we can access the Site Collection. To do that we
must first add the site to the Host file since we do not have DNS setup for the
site at this time.
2. Navigate to C:\Windows\System32\drivers\etc and open the hosts file in
notepad and add 127.0.0.1
extranet.contoso.com
3. Open Internet Explorer and type http://extranet.contoso.com in the address
bar and enter the Administrator credentials.
166
Now that the site is up we will look at creating a loop so we can create multiple
sites at once.
4. Type, $departments = (HR, Marketing, Sales, Finance), hit Enter.
PS C:\Users\Administrator> $departments = (HR, Marketing,
Sales, Finance)
5. Type, ForEach($dept in $departments) {New-SPWeb URL

http://extranet.contoso.com/$dept Name $dept Template STS#0} , hit
Enter.
PS C:\Users\Administrator> $departments = (HR, Marketing,
Sales, Finance)
PS C:\Users\Administrator> ForEach($dept in $departments) {NewSPWeb URL http://extranet.contoso.com/$dept Name $dept Template
STS#0}
6. Open Internet Explorer and type http://extranet.contoso.com and hit Enter.

7. Go to Site Settings, and see the sites created under the Home page.
167
MODULE 8 SHAREPOINT 2013 SITE ADMINISTRATION

This module focuses on the configuration of User Groups and Permission levels to
control access to information stored in SharePoint.
8.1 Task 1: Customize User Permissions
In this lab we will modify an existing permission status by not allowing users to
delete items they have created or delete other items in a list or library.
Go to http://spinet.sharepointinnovations.com/sites/student< # >
User name: SPI\student<#>
Password: trainingdan49$
1. Go to Site Settings and select Site permissions, then select the Permission
Check icon and enter your login name to view your Permission Levels.
2. Verify that your permission level is Full Control.

3. Go to Site Settings and select Site Collection Administrators, and verify
that you are a Site Collection Administrator.
168
4. On the Site Settings page, under Users and Permissions, click Site
permissions.
5. In the Permissions section of the ribbon, click Permission Levels.
169
6. In the list of Permission Levels, click Contribute.
7. Under Edit Permission Levels, select or clear Delete Items.
8. Click Submit.
8.2 Task 2: Create New Permission Level

Verify that you have one of the following administrative credentials:
You are a member of the Administrators group for the site collection.
You are a member of the Owners group for the site.
You have the Manage Permissions permission.
170
1. Click the link for the permission level you want to copyin this case, the
Contribute permission level. SharePoint will show you a page of the
permissions contained in the selected permission level.
2. Scroll to the bottom of the page and click the Copy Permission Level button.
171
3. In this case, find the Delete Items permission and clear the check box.
4. Give this new Permission Level a Name.

5. Scroll to the bottom of the page and click Create.
SharePoint will navigate you back to the site Permission Levels page with the
new permission level shown along with the default permission levels.
8.3 Task 3: Create Security Group

SharePoint security groups are groups of users, defined within a site collection,
and assigned permissions to secured objects. Security groups work to make
administration of security easier by collecting users into groups according to their
access role. For example, the default Visitors, Members, and Owners groups of a
site collection establish separation of users that have permissions to view secured
objects (visitors), write and change secured objects (members), and enjoy full
access to secured objects (owners).
Follow these steps to view the current groups in the site collection:
1. Click the Gear icon (from the top right of the home page of the site collection).
2. Click Site Settings from the menu.
172
3. Under the Users and Permissions heading, click the People and Groups
link.
By default, SharePoint will open a page of the Portal Members group.
From the Quick Launch left navigation, you can click on any Groups heading
you want to add or remove users to.
8.3 Task 3: Add Users to a Group

173

link.

4. From the sub-menu (New, Actions, and Settings), click the arrow next to
New select Add Users.
5. Add users to the dialog by typing in their usernames, names, or e-mail

addresses.
6. Click Share to save.
174
8.4 Task 4: Remove Users from a Group

Note: Removing a user from a SharePoint security group does not remove the
user from the site collection.
link.

4. Check the check box next to each user you wish to remove from the group.
175
5. From the sub-menu (New, Actions, and Settings), click Actions, and then
click Remove Users from Group.
6. Click OK in the warning dialog that appears.
176
8.5 Task 5: Create a New Group with Permissions

Site collection administrators may create new custom security groups, and then
apply permission levels to these groups within the context of a secured object
(site, list, or page). For example, your organization may decide that the default
Members, Visitors, and Owners roles are not sufficient and want to create a
specialized group of users, called Steering Committee Members. This group
might have contributor access to a site in the collection but not delete rights.
Look back at the section Permissions and Permission Levels for creating a
custom permission level that allows Contribute without Delete.
link.
177
4. Click the Groups heading in the left navigation.
5. Click New from the sub-menu.
6. Give the group a Name and Description.
178
7. Configure the group settings and assign the Portal Contrib- custom
permissions we created earlier.
NOTE: You do not have to assign default permission levels at this stage; you
can do so later when applying permissions to a secured object for users
contained in this group.
8. Click Create to create the group.
The new group should be visible on the left nav.
179
8.6 Task 6: Delete a Group

3. Under the Users and Permissions heading, click the People and Groups link
4. Click the Groups heading in the left navigation.
180
5. Click the Edit icon next to Portal Members Limited.
SharePoint shows the settings page for the group.

6. At the bottom of the page, click the Delete.
7. Click OK on the dialog box that appears.
8.7 Task 7: Break Permission Inheritance

As a general rule of thumb, it is a good practice to assign permissions at the site
collection level that reflect the general population and then break inheritance for
specific circumstances.
1. Navigate to the Documents > Document library where you wish to assign
unique permissions, that is, to break inheritance.
181
2. In the Ribbon, click Library Settings.
3. Click the link for Permissions for this Document Library.
4. Under the Permissions tab, click Stop Inheriting Permissions.
SharePoint now copies all the permissions of the parents and assigns them as
copies to the current library.
182
MODULE 9 SHAREPOINT 2013 OFFICE WEB APPS

This lesson is a discussion and will not be setup in the class
About Office Web Apps Server
Office Web Apps Server is an Office server product that provides browser-based
file viewing and editing services for Office files. Office Web Apps Server works
with products and services that support WOPI, the Web app Open Platform
Interface protocol. These products, known as hosts, include SharePoint 2013,
Lync Server 2013, and Exchange Server 2013. An Office Web Apps Server farm
can provide Office services to multiple on-premises hosts, and you can scale out
the farm from one server to multiple servers as your organizations needs grow.
Although Office Web Apps Server requires dedicated servers that run no other
server applications, you can install Office Web Apps Server on virtual machine
instances instead.
It is easier to deploy and manage Office Web Apps within your organization now
that it is a stand-alone product. If you deploy SharePoint 2013, for example, you
no longer have to optimize the SharePoint infrastructure to support Office Web
Apps, which in earlier versions was tightly integrated with SharePoint Server
2010. You can also apply updates to the Office Web Apps Server farm separately
and at a different frequency than you update SharePoint, Exchange, or Lync
Server. Having a stand-alone Office Web Apps Server farm also means that
users can view or edit Office files that are stored outside SharePoint Server, such
as those in shared folders or other websites. This functionality is provided by a
feature known as Online Viewers.
The following illustration shows the differences between the previous deployment
model for Office Web Apps and the new stand-alone deployment model for Office
Web Apps.
Office Web Apps licensing offers two options:
View-only. By default, Office Web Apps is view-only. View-only functionality is
provided for free.
Edit and view. Youll need to purchase an editing license to use the editing
features of Office Web Apps with SharePoint 2013. You enable editing when
you create the Office Web Apps Server farm.
183
9.1 Task 1 - Install prerequisite software for Office Web Apps Server
Access your Web Apps Server. The Web Apps Server must be a standalone
server separate from SharePoint server.
1. Click Start.
2. Type PowerShell in the search box, and Right Click on PowerShell.exe and
click Run as Administrator
3. In the Windows PowerShell window type the following command

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,WebWebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,WebPerformance,Web-Stat-Compression,Web-Dyn-Compression,WebSecurity,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-NetExt45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,WebIncludes,InkandHandwritingServices,NET-Framework-Features,NETFramework-Core
184
4. Click Enter on the keyboard

5. You may need to restart the server if prompted
9.2 Task 2 Install Office Web Apps Server

1. Download Office Web Apps Server from the Microsoft Download Center.
2. Open the .img file directly and run Setup.exe.

3. For servers older than Server 2012 you may need to use a program that can
mount or extract .img files, then run Setup.exe.
4. On the Read the Microsoft Software License Terms page, select I accept
the terms of this agreement and click Continue.
5. Select the folder where you want the Office Web Apps Server files to be
installed (for example, C:\Program Files\Microsoft Office Web Apps) and select
Install Now. If the folder you specified doesnt exist, Setup creates it for you.
6. When Setup finishes installing Office Web Apps Server, choose Close.
185
9.3 Task 3 Creating the Office Web Apps Server Farm

1. Click Start.
2. Type PowerShell in the search box, and Right Click on PowerShell.exe and
click Run as Administrator
3. In the Windows PowerShell window type the following command

New-OfficeWebAppsFarm InternalURL "http://servername" -AllowHttp EditingEnabled
4. Click Enter on the keyboard

5. Now to test that the farm was created successfully, Open your browser.
6. In the address bar Type http://servername/hosting/discovery.
7. You should see a page with the following XML.
<?xml version="1.0" encoding="utf-8" ?>
- <wopi-discovery>
- <net-zone name="internal-http">
186
- <app name="Excel"
favIconUrl="http://servername/x/_layouts/images/FavIcon_Excel.ico"
checkLicense="true">
<action name="view" ext="ods" default="true"
urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&
>" />
<action name="view" ext="xls" default="true"
>" />
<action name="view" ext="xlsb" default="true"
>" />
<action name="view" ext="xlsm" default="true"
>" />
187
9.4 Task 4 Configure Office Web Apps for SharePoint 2013

1. Click Start.
2. Click Programs.
3. Click Microsoft SharePoint 2013 Products and then Right Click on
SharePoint 2013 Management Shell.
4. Then Click on Run as administrator.
5. In The windows PowerShell window, Type New-SPWOPIBinding -ServerName

<Web App Server Name> and hit Enter.
New-SPWOPIBinding -ServerName <WacServerName>
188
Office Web Apps Server uses zones to determine while URL and protocol to
use when it communicates with SharePoint 2013. By default SharePoint uses
internal-https zone.
6. In the SharePoint Management Shell window, Type Get-SPWOPIZone to
see what one is being used.
7. To change the zone. In the SharePoint Management Shell window, Type
Set-SPWOPIZone zone External-https
8. Now open a document from SharePoint and it should open in the Browser
using Office Web Apps
189
MODULE 10 SHAREPOINT 2013 BUSINESS CONNECTIVITY SERVICES

BCS provides mechanisms to enable experienced users, developers, and
business unit IT professionals to do the following much more easily:
Reveal external data from enterprise applications, web services, and OData
services in SharePoint Server 2013 and in rich-client Office applications.
Provide Office-type behaviors (such as Contacts, Tasks, and
Appointments) and capabilities to external data and services.
Provide complete interaction with the data, including write-back capabilities
from Office applications and SharePoint Server to the underlying external
system data and business objects.
Enable offline use of external data and processes.
Bridge the unstructured world of documents and people and the
appropriate structured data that is locked in external systems.
10.1 Task 1: Create a Business Connectivity Service Application

To create the Business Connectivity Service open Central Administration.
1. Go to Manage Service Applications.
190
2. Click New and select Business Data Connectivity Service.
191
3. Fill in the Service Application Name as BCS.

4. Delete the long GUID in the Database Name and insert the word PROD. This
simply makes it easier to navigate, it doesnt affect the application function.
5. Create a new application pool and name it bcsapppool.
192
6. Select TPILEARN\SP_Services as the account that runs the application pool

and click OK to create.
7. Open SQL Server Management Studio. Make sure it is on Database.

8. Click Connect.
9. Expand Database, then AdventureWorks, then expand the Tables.
10. Right-click the Human Resources Employee Table.
11. Select Top 1000.
12. Open SharePoint Designer.
13. Open http://intranet.contoso.com
193
14. Click External Content Types on left pane.
15. Click the External Content Type button.
194
16. Click on New external content type. Give it a Name AWSemployee
17. Click in Display field, it will populate.

18. Click the Click here to discover external data sources and define
operations link at bottom of page.
195
19. Click Add Connection button.
20. Choose SQL Server in the External Data Source Type Selection drop down
list, click OK.
A dialogue box will pop up asking for information.
196
21. Name the Database Server as tpserver

22. Name the Database Name as AdventureWorks2012
23. Click OK.
24. Expand AdventureWorks.
25. Expand Tables.
26. Right-click on Employee table.
197
27. Select Create All Operations.
Now in the Operations Properties window we can see that our users can
perform such operations as Create, Read, etc.
28. Click Next.

29. Click BusinessEntityID.
198
30. Under Properties on right, check Show in Picker.
31. Click Finish.

This is not saved to SharePoint yet!
199
32. Right-click the AWSemployee tab and click Save.
33. Click External Content Types. Notice our new content type AWSemployee.
This item is an Entity, now we need to create an Instance.

34. Switch to SPD, then click External List in the Ribbon.
35. Select AWSemployees and click OK.
200
36. In the dialog box give it a Name as AWSemployees

37. Click OK.
38. On the left hand navigation, click on External Lists.

Notice at the bottom External Lists now has AWSemployees.
You have now successfully created an External List with data from a different
database.
201
10.2 Task 2: Give Permissions

Now we have to give users permissions to interact with the data. In order to do
that we must manage the BCS connection.
1. Open Central Admin > Application Management > Manage Service
Applications.
2. Click Business Connectivity Service bar.
3. Click Manage.
4. Check the box for AWSemployee.
5. Click Set Object Permissions button in Ribbon.
6. Enter TPILEARN\Administrator, click Checker.

7. Click Add button.
8. Check each of the Permission boxes.
202
9. Make sure Propagate permissions box is checked at bottom.
203
10. Click OK.

11. Repeat steps for any users you want to grant permissions.
12. Make sure Propagate permissions box is checked at bottom.
13. Click OK.
You can now navigate to http://intranet.contoso.com and access the employee
list we just created.
Even though the data does not live in SharePoint, because of the permissions
we just gave the connection, we can effectively make changes to the list in
SharePoint and consequently it changes them on the database.
If error occurs see below:

SharePoint 2013 Business Connectivity Services Login failed for user
NTAUTHORITY IUSR
If you have created an external content type and are trying to access it in a list
and get Access Denied that is because you have not given permissions to the
logged-in user to use that external content type. You can easily give
permissions to that user or to all users in your site by going to Central
Administration site and configuring business connectivity service. For exact
steps on how to do it, read this blog:
SharePoint 2013 Business Connectivity Service Access Denied Error:

http://blog.walisystemsinc.com/2012/11/sharepoint-2013-businessconnectivity.html
204
MODULE 11 SHAREPOINT 2013 SQL REPORTING SERVICES

Reporting services within SharePoint will allow you to use the collaboration and
centralized document management features of SharePoint for reports and
reporting content types. When you integrate the report server with SharePoint
items and properties are stored in the content database. With the reports and
properties stored in the content database it will allow you to manage permissions,
check in and our reports, manage alerts, and allow you to use the report viewer
web part to view or customize reports.
When you access a report from SharePoint it contacts the report server and
creates a session, retrieves necessary data, merges data into the report layout
and then displays it in the Report Viewer Web part. Once the report is open you
will be able to drill into the underlying numbers or can click through to a related
reports. You will also be able to export your reports to other application for further
manipulation or viewing. Report interaction and exporting is all processed by the
report server.
205
11.1 Task 1: Install Reporting Services Add-in *Discussion Only as it is already setup on our server
1. Run the SQL Server Installation Wizard. Navigate to C:\installs and Right
Click on
en_sql_server_2013_enterprise_edition_with_sp1_x64_dvd_1227976.iso
and click Mount.
2. Double click on setup.exe.
3. Click Installation in the left side of the wizard and then click New SQL Server
stand-alone installation or add features to an existing installation.
4. Click OK on the Setup Support Rules page, assuming all rules passed.
5. Click Install on the Setup Support Files page. Depending on what is already
installed on your computer you might see the following message: One or more
affected files have operations pending. You must restart your computer after
the setup process is completed.
6. Click Ok.
7. Click Next after the support files have completed installing and the Support
Rules pages show a status of Passed. Review any warnings or blocking
issues.
8. On the Installation Type page, click Add features to an existing instance of
SQL Server 2012. Select MSSQLSERVER in the drop-down list and click
Next.
9. Check both Reporting Services SharePoint and Reporting Services addin for SharePoint Products.
10. Click Next on the Installation Rules page.
11. Review the Disk Space Requirements page and click Next.
12. If you see the Server Configuration page type appropriate credentials. If you
want to use the Reporting Services data alerting or subscription features, you
need to change the Startup Type for SQL Server Agent to Automatic. You may
not see the Server Configuration page, depending on what is already installed
on the computer.
13. Click Next.
14. If you selected the Database Engine services, you will see the Database
Engine Configuration page, add appropriate accounts to the list of SQL
Administrators and click Next.
15. Review any warnings and then click Next on the Installation Configuration
Rules page.
206
16. Click Next On the Ready to Install page

17. Then Click Install.
The installation will take several minutes. You will see the complete page with
the features listed and the status of each feature. You may see an information
dialog indicating the computer needs to be restarted.
11.2 Task 2: Register and Start the Reporting Services SharePoint Service
1. Click the Start button, and then click Programs to Microsoft SharePoint 2013
Products.
2. Then right click on SharePoint 2013 Management Shell and click on Run as
administrator.
3. Run the following PowerShell command to install the SharePoint service.
PS c:\Users\Administrator> Install-SPRSService
4. Now run the following PowerShell command to install the service proxy
PS c:\Users\Administrator>
Install-SPRSServiceProxy
5. Next run the following PowerShell command to start the service or you can
start it from Central Administration
PS c:\Users\Administrator>
get-spserviceinstance -all |where
{$_.TypeName -like "SQL Server Reporting*"} | StartSPServiceInstance
*To Start from Central Administration

6. Go to Central Administration home page and click on Manage Services on Server
7. Click Start in the SQL Server Reporting Services line
8. Status should change to Started.
207
11.3 Task 3: Create a Reporting Services Service Application

The next step is to create a service application is SharePoint.
1. In SharePoint Central Administration, click Manage Service Applications.
2. In the SharePoint ribbon, click the New button.

3. In the New menu, click SQL Server Reporting Services Service
Application.
208
4. Enter Reporting Services for the Name

5. Choose Use existing application pool, and click the dropdown and Select
SharePoint Web Services Default.
6. Verity that the server name is tpserver.
7. Change the Database Name to ReportingService_DB.

8. In the Web Application Association, check Intranet-80.
9. Click OK.
209
The process could take a bit to complete but when finished you see a
confirmation message.
210
11.4 Task 4: Creating Reports

1. Go to http://intranet.contoso.com.
2. We are going to create a document library to keep our reports in. Click the
Gear in the top right corner and click, Add an app.
3. Next Click Document Library.
4. Type, Reports.
5. Click Create.
6. Click on the Reports document library to open it.
211
7. We are going to add report specific content types to the library so click the
Library tab on the Ribbon.
8. Click Library Settings.
9. Click Advanced Settings.
10. Select Allow management of content types, then Click OK.

11. Next, Click on Add from existing site content types in the Content Types
section.
12. From the Select Content Types dropdown, Choose SQL Server Reporting
Services Content Types.
13. Select Report Builder Model and Click Add. Repeat the steps for Report
Builder Report and Report Data Source.
212
14. Click OK.
15. Click Reports in the breadcrumb navigation to go to the document library home
page.
16. Click the Files tab on the Ribbon.

17. Click the New Document dropdown, then Click Report Data Source.
18. In the Data Source Type dropdown click Microsoft SQL Server.
213
19. Type data source="(local)";initial catalog=AdventureWorks2012 in the

Connection string textbox
20. Select Stored credentials and type TPILEARN\administrator for the User
Name and trainingdan49$ for the Password.
21. Click the Test Connection button and you should get a Connection created
successfully message so you know that everything is set correctly.
22. Click OK.
23. Click the Files tab on the Ribbon.

24. Click the New Document dropdown, then Click Report Builder Report.
25. This will install the SQL Server Report Builder, Click Run.
214
26. Click Blank Report.
27. On the Ribbon click the Insert tab.

28. Next click Table and then Table Wizard.
29. With Create a dataset selected, Click Next.
215
30. Click Browse.

31. Navigate to the Reports library and click on the AdventureWorks data
connection.
32. Click Open.
33. Type in the administrator password trainingdan49$

34. Expand Production.
35. Expand Views.
216
36. Check vProductModelCatelogDescription and Click Next.
37. Click and Drag the specific fields to match the image below.
38. Click Next.
217
39. Uncheck Show subtotals and grand totals and click Next.
40. Leave the style and click Finish.
41. In the Ribbon for the Report Builder, click Run
42. Expand the Product Line groups
43. Click Design on the Ribbon and investigate the changes that you can make to
the form. Page width and column width are a couple of the things that you
may want to change on this report.
44. Click Save and save the report in the Reports library with the name of
Products.
45. Click Save.
46. Open up the http://intranet.contoso.com site and navigate to the Reports
library.
47. Click on the Products report for it to open in the browser.
218
MODULE 13 SHAREPOINT 2013 BACKUP AND RESTORE

The SharePoint 2013 backup architecture and recovery processes include farm
backup and recovery, granular backup and recovery, and recovery from an
unattached content database. You can complete backup and recovery operations
by using the SharePoint Central Administration website or Windows PowerShell
cmdlets. Note that some built-in backup and recovery tools may not meet all the
requirements of your organization.
Backing up and recovering data supports many business scenarios, including the
following:
Recovering unintentionally deleted content that is not protected by the
recycle bin or versioning.
Moving data between installations as part of a hardware or software
upgrade.
Recovering from an unexpected failure.
219
Backup Architecture in SharePoint 2013

SharePoint 2013 provides two backup systems: farm and granular.
Farm Backup Architecture

The farm backup architecture in SharePoint 2013 starts a SQL Server backup of
content and service application databases, writes configuration content to files,
and also backs up the Search index files and synchronizes them with the Search
database backups.
The following illustration shows the farm backup system.
220
The architecture supports both full and differential backups. Full backups create
a new backup of the complete system. Differential backups create a backup of all
changes that are stored in databases since the last full backup.
The farm backup system is organized hierarchically. The components in a farm
that you can select for backup include the following Web, Web Applications,
Service Applications, Service application proxies and Shared Services.
Some settings in the SharePoint 2013 environment are not included in a farm
backup. They include the following settings that are stored on web servers:
Application pool account passwords
HTTP compression settings
Time-out settings
Custom Internet Server Application Programming Interface (ISAPI) filters
Computer domain membership
Internet Protocol security (IPsec) settings
Network Load Balancing settings
Secure Sockets Layer (SSL) certificates
Dedicated IP address settings
221
The granular backup and export architecture

The granular backup and export architecture uses Transact-SQL queries and
export calls. Granular backup and export is a more read-intensive and
processing-intensive operation than farm backup.
From the granular backup system, you can back up a site collection or export a
site or list. Please note that Workflows are not included in exports of sites or lists.
We do not recommend that you use SharePoint 2013 site collection backup for
site collections larger than 85 GB.
The following illustration shows the granular backup and export system.
222
Recovery processes in SharePoint 2013

SharePoint 2013 supports the following primary, built-in recovery options:
Restore from a farm backup that was created by using built-in tools.
Restore from the backup of a component taken by using the farm backup
system.
Restore from a site collection backup.
Connect to a content database by using the unattached content database
feature, back up or export data from it, and then restore or import the data.
By default, SharePoint 2013 recovery restores all objects as new instances of the
object (such as a new farm vs. overwrite an existing farm), instead of overwriting
existing instances with the same name.
SharePoint 2013 can connect to and back up from an unattached database. An
unattached content database is a database that is attached to an instance of SQL
Server but is not associated with a web application.
223
13.1 Task 1: Backup and Restore a Site Collection using PowerShell.

1. Open PowerShell As Administrator
2. Run the following Command:
Backup-SPSite -Identity http://intranet.contoso.com -Path C:\contoso.bak Verbose
3. Make changes to the site http://intranet.contoso.com by uploading a document
to the document library
4. Restore the site collection using the following command:
Restore-SPSite -Identity http://intranet.contoso.com -Path C:\contoso.bak
Verbose Force
5. You should be able to see the old site collection is restored and the document
uploaded in Step 3 is no longer there.
In this exercise you have learned how to backup and restore a SharePoint
2013 site collection.
224
MODULE 14 SHAREPOINT 2013 GOVERNANCE

SharePoint Governance
Microsoft SharePoint technologies offer an immense amount of power for an
organization, and harnessing this power is the goal of every business that installs
SharePoint.
But adoption of the SharePoint technologies can get out of control without proper
governance. You'll learn what governance is and learn about some of items that
you should consider for a SharePoint technologies governance plan.
Before delving into the details of the specifics of SharePoint governance, it's
important to clarify meaning and to understand an overall approach to
governance that works well for organizations of all sizes.
Governance is defined as "a method or system of government of management"
(Dictionary.com). It is also defined in part on Wikipedia.org as " focused on
information technology systems and their performance and risk management."
Governance is managing the deployment of information technologies. Managing,
like project management, is concerned with the risks, the costs, and the
usefulness of the solution once it has been created. Thus when we define
governance we are attempting to manage risk, cost, and adoption.
A Governance Plan describes how your SharePoint environment will be
managed. It describes the roles, responsibilities, and rules that are applied to both
the back end (hardware, farm, application, database configuration and
maintenance) and the front end (information architecture, taxonomy, user
experience). Effective governance planning is critical for the ongoing success of
your SharePoint solution. A good Governance Plan is necessary but not
sufficient to ensure success, so be advised: a Governance Plan alone will not
guarantee the success of your solution. You still have to ensure that the
Governance Plan is applied. However, not having a Governance Plan or having a
plan that is either impractical or unrealistic is a clear recipe for disaster.
We must strike a balance between these goals, seeking to find a manageable
path which is neither overly loose nor overly tight. We cannot exercise no
225
governance and have broad adoption without manageability nor can we exercise
heavy governance which eliminates adoption.
Now that we understand the purpose of governance it's time to review categories
that may be important in your SharePoint governance. They are:
Project and Operational Management

Development and Configuration
Infrastructure
Operational Concerns
Education and Training
Navigation, Taxonomy, and Search
The following sections drill into the details of each area and describe the specific
items that you may want to include in your governance plan. Each section
contains a table which indicates a name of a general grouping for the activities
and decisions, the specific actions ("What to do") and the reasoning behind the
actions ("Why to do it"). The objective here is to provide you with both a practical
guide for creating your governance plan as well as to enlighten you on the
background for the items so that you can identify additional, organizationally
unique, items that should be a part of your governance plan.
14.1 Project and Operational Management

Project and operational management encompasses traditional project
management concerns as well as those concerns which may be more formally
described as operational management - as they refer to the ongoing management
of the platform and not to the project management associated with the initial
construction. In this section we are concerned with the initial construction and
those operational items which need early decisions to promote consistency.
226
Project and Operational Management

Item
What To Do
Why To Do It
Communication
Establish a communications
plan that includes: 1. Who will
do the communications 2.
When the communications will
occur 3. What each
communication will contain 4.
How each communication will
come (i.e. email, hard copy
document, newsletter, etc.)
Establishing an expectation as
to what communications will
happen will help users
understand how to contact the
project team and what they can
expect the communications
pattern to be. This improves the
perceived openness of the
process and facilitates adoption
Create central points of

contact for those who are not
directly involved in the
governance.
Deployment
Process
Define a process which will be

used for in-house developed
and third party software to be
deployed to SharePoint
platform or platforms.
Defining the deployment

process creates a clear
understanding for development
teams on what to expect if their
software is to be installed on the
platform. This eliminates last
minute problems during
deployment and reduces the
number of variations thus
reducing management costs.
Change
Management
Process
Define how changes will be

tracked, cataloged, and
approved
Maintaining a high availability is

essential to adoption. Solid
change (configuration)
management processes create
better availability. Consistency in
approach, approvers, and
responsibilities encourage
ownership and better stability.
Decide what repositories will

hold older versions of
configuration, code, and
compiled components of the
solution
227
Cost Allocation
Decide whether you will be

allocating costs back to
business units or not
If not - Consider where the
costs should be centered, often
this is with costs associated
with email.
If so - Consider what metrics
you'll use for the charge back:
users: number of sites, amount
of storage, amount of activity,
etc.
Sponsorship
Establish a SharePoint
Governance board to review
adoption and controls.
Solicit executive champions
to create the right management
attention to the value of the
initiative.
Encourage business
evangelists to share the power
of SharePoint with other
business leaders.
Roles and Teams
Define clear roles and

responsibilities for the initiation
of the SharePoint technologies
platforms as well as its
operation.
Define strategic teams to
address strategy issues.
Establish cross-functional
problem resolution teams to
address complex issues which
arise.
SharePoint governance in
general, and SharePoint
technology platforms in
particular cost money.
Governance in most cases
implies a centralized platform.
Finding the funding to pay for
the centralized platform is an
essential and sometimes difficult
task.
SharePoint technologies have

the potential to radically redefine
the way software is developed
and projects are run - for the
better. However, if the
management team doesn't
understand this and the users
don't feel excited about the
possibilities that SharePoint
brings then the prospects for
success are not bright.
Clearly defining roles and

establishing formal teams to
address both the specific tasks
which arise and to evaluate
cross functional problems
creates the structure necessary
to complete the initial
development of the central
platform and to resolve issues
that arise quickly.
228
Site and Platform

Classification
Create a classification by
number of users and longevity:
enterprise, departmental, team,
project, and personal.
Create a classification by
type of use: portal for
communications, application for
tactical results, and
collaboration to facilitate team
operations.
Service Level
Agreements
Create a common
understanding for the types of
SharePoint solutions the
organization knows how to do
well and a vocabulary for
speaking with parts of the
business about what is needed.
Create a service level

agreement around the length of
time and approvals necessary
to create a site.
Establishing service level

agreements drives the
understanding of the
organization as to what to
expect. Service level
agreements are a commitment
Establish service level
upon the part of the core team
agreements for problem
resolution through the help desk that the systems will be
available which can in turn drive
adoption.
Negotiate performance
service level agreements for the
first load of a site, subsequent
loads of a site, and
performance at remote
locations
14.2 Development and Configuration

SharePoint technologies significantly blur the line between what is development
and what is configuration. This section covers the items which are either software
development or are configuration. These are essential parts of the governance
plan so that the solutions implemented on the platform are consistent.
Development and Configuration

Item
Branding
What To Do
Establish templates for what
the SharePoint sites will look
like
Determine which types of
sites may be modified and
which may not
Define which parts of the
Why To Do It
Establishing a core brand will
not only make the site seem to
belong to the organization but
will promote better navigation
and organization. Defining which
areas can and cannot be
changed creates the flexibility
229
template may be changed by

site owners, and which may
not.
Define what customization
tools will be allowed?
Communicate what actions
will be allowed and not allowed
in the tool. (i.e. unghosting)
Customization
Tools
Site Definitions
and Templates
Source Code and

Build Control
On-going Source
Code Support
Development
Standards
necessary for adoption.
Nearly every business unit

within the organization will want
to place their stamp on their site.
The challenge is controlling this
so that their need for
individuality doesn't hinder
maintainability.
Establish guidelines for the
Site definitions and site
development of site definitions
templates have their own unique
and mechanisms for
challenges with regard to how to
coordinating ID usage.
manage them in a large
Communicate policies for site environment. Clear
template deployment such as
communication and decisions
the requirements for a globally
up front can improve the ability
installed template.
to manage input from multiple
groups.
Determine if a central
Source code is the essence of
repository will be required for
your organizations
all code installed
enhancements to SharePoint.
Establish standards for
Establishing a common set of
building components either on
expectations and rules around
a centralized server or as
the development of code will
guidelines for building software. make the maintenance process
Communicate expectations
easier and will lead to a more
as to reference documentation stable system.
(compiler generated) and
warnings (whether they are
allowed)
Describe the responsibilities
Defects will be found in code,
of business unit for ongoing
sometimes long after its initial
code support.
deployment - understanding
who will address those defects
is essential to the long term
survivability of the platform.
Establish guidelines for
The security of the site is
which assemblies may be
determined by what code is
installed to the Global
allowed to run and with what
Assembly Cache and which
permissions. .NET's code
may not.
access security and the
Establish rules about the use implications of GAC deployment
of the
are important to maintaining a
AllowPartiallyTrustedCallers
secure system.
attribute.
230
14.3 Infrastructure
While most infrastructure items can honestly be considered implementation
details there are a few which will have a significant impact on how you implement
SharePoint and what the features will be available. The infrastructure items
outlined here are important for inclusion in your governance plan because their
impact on the way the solution will be used.
Infrastructure
Item
Firewalls
What To Do
Establish and communicate
rules for outbound connections
from the web servers for use by
the Content editor web part and
RSS Viewer web part
Load Balancing
Decide upon and

communicate the load
balancing settings related to
session stickiness.
Environments
Define the environments,

which will be used to develop
and test solutions in
SharePoint.
Describe the actions, which
are expected, and those that
are prohibited in each
environment Communicate
policies for site template
deployment such as the
requirements for a globally
installed template.
Why To Do It
Best practice is to not allow
servers to access the web
directly. Further including
content from a third party site
through a content editor web
part or through the RSS reader
web part creates exposure for
cross site scripting attacks.
Controlling what sites can be
linked to from these tools is a
security and operational
concern.
Developers must know if they
are expected to handle
situations where a single
session is transferred between
servers.
Defining the environments helps
business users and developers
know what resources they have
available to test changes without
impacting production.
231
14.4 Operational Concerns

Operating a SharePoint environment, like any large scale web environment, has
many components. The items listed here are an important part of your SharePoint
governance plan because they help to ensure that the system will remain
operational and because they set proper expectations with the business about the
availability of SharePoint technologies.
Operational Concerns
Item
Monitoring
What To Do
Establish monitoring at the
server, site, and SharePoint
level
Define responses to each
type of failure that may occur
Uptime and
Downtime
Define Scheduled downtime

periods
Communicate the procedure
to report unscheduled
downtime or specific
performance issues
Define response procedures
to unscheduled downtime
Disaster Recovery
Plan for single file recovery
(perhaps using version control
and the recycle bin)
Plan for single or multiple
site recovery
Plan for server recovery
Plan for geo-disaster
recovery
Data and
Codify corporate records
Documentation
management requirements into
Recovery
SharePoint.
Define rules for archival of
sites including warnings and
approvals
Quotas
Establish storage quotas by

site type
Establish a process for
Why To Do It
Systems which are not available
cannot be used by users. Taking
a layered approach to
monitoring the system
encourages better awareness of
issues with the platform.
Establishing the periods of time
which the system will not be
available is critical to allow for
patches to be applied.
Communicating the process for
unscheduled downtime will calm
users when unscheduled
downtime does occur.
Disasters will happen. It's not a
question of if but of when and
how. Planning for them further
reinforces the commitment to
the platform and the instance
that it will remain available.
SharePoint technologies can

help with the records
management issues associated
with maintaining too much - or
too little information. Defining
how SharePoint will work aligns
it with the corporate
governance.
Storage management is the
responsibility of everyone within
the organization the
232
requesting a larger quota
Reporting
Define required auditing

reports
Establish storage usage
reports
Develop activity based
reporting for administrators and
business users
establishment of technology
supported guidelines can help to
provide reasonable control
around disk space consumption.
Reporting upon what has been
done is essential for various
compliance needs. Developing
user reporting to report on
activity and storage create a
necessary feedback loop for the
organization to understand the
value that is being derived from
the SharePoint technologies
platform.
14.5 Education and Training

As adoption is an important measure of SharePoint governance success,
education and training are important proactive tools. Education and training not
only explains the features that SharePoint technologies expose but it also helps
users understand real world solutions that they can create.
Education and Training

Item
Initial Training
Community
Development
What To Do
Acquire end user training
and resources
Acquire help desk training
and resources
Acquire administrator
training and resources
Develop administrator policy
guides which describe
organization specific policies
Acquire developer training
and resources
Develop developer policy
guides which describe
organization specific
development policies
Create online forums where
users can support each other
and ask questions.
Create opportunities for faceto-face learning in unstructured
or semi structured
environments such as lunch
Why To Do It
Training both in the facilities and
capabilities of SharePoint as
well as the policies that have
been defined by the
organization is the most
important proactive step to
ensuring the consistency and
manageability of the SharePoint
technologies platform.
Some kinds of information dont

communicate well through
structured training. The context
necessary for users to
understand how to apply it in
their environment is sometimes
best created through users
233
and learns or after hours

discussions.
Renewal Training
talking with each other about the

kinds of solutions they've
implemented.
Plan for renewal training
Formally defining your intention
which gathers the learning from to review progress from a user
multiple groups and exposes it adoption standpoint can
to other groups.
encourage the health review of
Perform periodic audits of the the solution and what additional
platform to discover what
training is required.
features are not being utilized
and which features are not
being utilized correctly.
14.6 Navigation, Taxonomy, and Search

The final set of considerations for your governance plan is those related to finding
information - those related to navigation, taxonomy, and search. They are
important for the long term adoption of SharePoint because they are the
framework by which users find the information that they are looking for when they
don't know where it's located.
Navigation, Taxonomy, and Search

Item
Site Directories
Content Types
Search Locations
What To Do
Define the structure of the
site directories including the
major groupings and
associations.
Develop a linking strategy
between different types of sites
such as enterprise, divisional,
departmental, team, etc.
Define core content types in
the organization
Define key fields to link
documents and operational
systems
Establish content sources to
the file based repositories in
the organization.
Use the Business Data
Catalog to allow searching of
business data
Why To Do It
Defining a structure for how
sites will be organized is an
essential part of helping users
find the information they need.
Developing a linking strategy is
necessary when a single
directory becomes too unwieldy
to manage as a one entity.
Consistency, which leads to a
greater ability to locate
information, can be encouraged
through the use of standardized
fields through standard content
types.
Search is an immensely
powerful tool which can be
essential in being able to find
information throughout the
enterprise. The more content
SharePoint search can index,
the easier it will be for users to
find the information they're
234
Search Relevancy
Define who will be

responsible for core relevancy
settings
Implement organizational
enhancements of the noise
words file, thesaurus file, and
keyword best bets
looking for.
Although search relevancy has
dramatically improved in the
SharePoint platform, additional
efficiencies can be gained by
fine tuning search for the
organization.
Defining Success
SharePoint technologies governance is a broad need with guidance needed in
many different areas. By developing a minimally sufficient governance plan that
emphasizes expectation setting and communication, you can have a successful
adoption of SharePoint technologies while maintaining an appropriate amount of
control.
235
MODULE 15 SHAREPOINT 2007 TO SHAREPOINT 2010 MIGRATION

If you have a SharePoint Server 2007 farm, you have several upgrade options. The
tree upgrade options that you have are in-place, database attach and migration.
The in-place upgrade will allow you to take your existing farm and upgrade it with
the same servers and environment. Your servers have to be compatible with the
SharePoint 2010 requirements. The database attach upgrade will allow you to build
a new farm and upgrade the content database to SharePoint 2010. The last option
is migration and for the migration method and copy the existing data and
configuration to the new farm.
In-place upgrade Key Points

There are a few things that you need to think about before you select any of the
upgrade methods. Here are some things to think about for the in-place upgrade.
Version of the previous farm
System requirements
What is being upgraded
Down time
Rollback
Testing
Version of the Previous Farm
The in-place upgrade will only work if the farm that you are migrating from is
SharePoint 2007. If you have an older version of SharePoint you have to take extra
steps to get to SharePoint 2007 first before going to SharePoint 2010.
System Requirements
SharePoint 2010 has different requirements than SharePoint 2007 so you need to
make sure that your servers will meet the requirements of SharePoint 2010.
SharePoint 2010 needs to be Windows Server 2008 SP2 or Windows Server 2008
R2 with 64-bit. SQL also has minimum requirements for the SharePoint 2010
upgrade. SQL needs to have one of the following versions of SQL: Microsoft SQL
236
Server 2008 R2, SQL Server 2008 with Service Pack 1 and Cumulative Update 2, or
SQL Server 2005 with SP3 and Cumulative Update 3.
With the in-place upgrade everything is upgraded and that includes the content
database, services, configuration and customizations. The customizations may not
function as desired after the upgrade.
Down Time
With the in-place upgrade, the farm will not be available during the migration. The
upgrade process is continuous so plan your upgrade accordingly.
Rollback
An in-place upgrade does not allow you to rollback easily. If you run into issues in
the upgrade process, you will have to uninstall SharePoint 2010 and reinstall
SharePoint 2007
Testing
Because the rollback process is tedious for the in-place upgrade, testing is very
important. Unfortunately, testing is most difficult with an in-place upgrade. The best
237
way to this is to conduct a database attach upgrade to see if anything is broken

during the process.
Database Attach Upgrade Key Points

Here are some things to think about for the database attach upgrade.
Version of the previous farm
System requirements
Down time
Rollback
Flexibility
Database access
Testing
Services
Version of the Previous Farm

The database attach upgrade will also only work with SharePoint 2007. If you have
an older version of SharePoint, you have to take extra steps to get to SharePoint
2007 first before going to SharePoint 2010.
System Requirements
SharePoint 2010 has different requirements than SharePoint 2007, so you need to
make sure that your servers will meet the requirements of SharePoint 2010.
SharePoint 2010 needs to have Windows Server 2008 SP2 or Windows Server
2008 R2 with 64-bit. SQL also has minimum requirements for the SharePoint 2010
upgrade. SQL needs to have one of the following versions of SQL: Microsoft SQL
Server 2008 R2, SQL Server 2008 with Service Pack 1 and Cumulative Update 2, or
SQL Server 2005 with SP3 and Cumulative Update 3.
What is Being Upgraded
With the database attach method you are only upgrading the content database. This
means that you are going to need to configure the central administration. This is a
238
good way to reconfigure your farm with new accounts or settings. This also means
that you are potentially going to have to upgrade other service databases.
Down Time
You mitigate down time with this method because both your old farm and the new
farm can co-exist. When you are going through the database attach process, set
your old farm to read only. When you are ready, change DNS to start sending users
to your new farm.
Rollback
Rollback is easy for the database attach method because we do not change any
settings on the old SharePoint farm. You may just need to change DNS to point
back to the old server, or potentially just set the database back to read/write.
Flexibility
The database attach method will allow you to upgrade the databases in any order
and it will also let you combine data from multiple farms into one.
Database Access
With the database attach method you will need to have direct access to the
database server and have the appropriate permissions to perform certain tasks on
the databases.
Testing
With the database attach method it will be easy to test your farm as it is on separate
servers than your exiting SharePoint. With the ability to run two SharePoint
environments at the same time, you can be testing your new environment at the
while your old environment is still running. Even if it takes you weeks or months to
test, you would just need to bring the content databases over to the new
environment when you are ready to go live.
Services
With the database attach method, you have to remember that all services will need
to be configured.
Migration Key Points

The migration method would require you to setup a new farm and instead of upgrading any
databases, you would be manually moving content. There are multiple ways to migrate your
data, but the most detailed way would be to use a third party migration tool. These tools
239
range in price and functionality but for the most part will allow you to move, restructure and
rearrange without removing permissions, metadata or versions of a document.
Here are some things to think about for the database upgrade.
Cost
Databases
Document Information
Rollback
Flexibility
Cost
Cost could be one of biggest things to think about when considering the migration method.
Cost is only an issue if youre using a third party program to help with migrating your data.
There are other ways to migrate without a third party program, but it would take you
considerably longer to move the data. Also, you can capture information about documents
with the tools provided by the third party program, which you would otherwise not have
access to.
Document Information
Again, I am going to talk about using a third party program to help with migration. If you
move a document from one farm to another, it is similar to a copy and paste action, the
document would move, but not the associated permissions, metadata or other versions of
the document. With a third party, you would be able to capture all of that information with
the move.
Rollback
No need for a rollback, as with a migration, we are just coping the data from one
environment to the other. Because of this, you will have access to both servers and can
decide when you want to start sending users to the new environment.
Flexibility
If you use the migration method for setting up your new farm, you would be able to
restructure your documents, sites and permissions, just to name a few.
240
Migration Steps
The first step before any migration is to run the STSADM pre-upgrade to check on
your existing farm. This is available on SharePoint 2007, SP2 and the October
2009 or later cumulative update. The command is as follows:
%CommonProgramFiles\Microsoft Shared\web server extensions\12\bin\STSADM.exe
-o preupgradecheck
This pre-upgrade check will give you information about your existing farm giving you more
information about how your existing farm is setup, and potentially what upgrade methods
are available and what ones are not. The check will tell you the following:
The current alternate access maps
Site definitions
Site templates
Features
Customizations
Orphaned databases
Server stats and if they meet the new requirements
If you can perform an in-place upgrade or if it must be a database attach
In-Place Upgrade Steps

The following steps would be performed on your existing farm.
1. Run the pre-upgrade check
2. On your current server, that is running the Central Administration, run the
setup for SharePoint 2010. The set up will see that you have a previous
241
version of SharePoint installed and know that you are doing an in-place
upgrade.
3. If you have other SharePoint servers in your farm, run the setup on these
servers as well.
4. Run the configuration wizard on the Central Administration server and at that
time, all databases and services will be upgraded.
5. If you have other SharePoint servers, run the configuration wizard on those
also.
6. The upgrade should be complete at that time.
Database Attach Steps

This process will be done once there is a new farm with all servers meeting or
exceeding the minimum requirements.
1. Install SharePoint 2010 on the new farm.
2. Install any customizations that were installed in the 2007 environment.
3. Setup any necessary services on the new SharePoint server.
4. In your existing farm set the content database to read only. You can do that in
SQL management studio.
5. Also in SQL management studio, back-up the content database and restore
the back-up to the new farm.
6. Attach the restored content database to the new farm and that will trigger the
database to be upgraded to 2010.
242
MODULE 16 SHAREPOINT 2010 TO SHAREPOINT 2013 MIGRATION

This module consists of a PowerPoint presentation by the instructor about the
upgrade process and a hands-on-lab using an existing SharePoint 2010 team site
content database.
We will cover the following topics but not limited to:
Upgrade Concepts and Terminology
Deprecated Upgrade Techniques from SharePoint 2010
Database Detach Preparation
Content Migration
SharePoint 2010 UI Mode Vs. SharePoint 2013 UI mode
Overview of the Upgrade Process
To upgrade from SharePoint 2010 Products to SharePoint 2013, you use the
database-attach method to upgrade. In the database-attach method, you first
create and configure a SharePoint 2013 farm. Then you copy the content and
service application databases from the SharePoint 2010 Products farm, and then
attach and upgrade the databases. This upgrades the data to the new version.
Site owners can then upgrade individual site collections.
243
Stage 1: Create the SharePoint 2013 farm

The first stage in the upgrade process creates the new SharePoint 2013 farm.
A server farm administrator installs SharePoint 2013 to a new farm. The
administrator configures farm settings and tests the environment.
A server farm administrator sets the SharePoint 2010 Products farm to read-only
so that users can continue to access the old farm while upgrade is in progress on
the new farm.
244
Stage 2: Copy the SharePoint 2010 Products databases

The second stage in the upgrade process copies the databases to the new
environment. You use SQL Server Management Studio for these tasks.
With the farm and databases in read-only mode, a server farm administrator
backs up the content and service application databases from the SQL Server
instance on the SharePoint 2010 Products farm.
The server farm administrator restores a copy of the databases to the SQL Server
instance on the SharePoint 2013 farm and sets the databases to read-write on
the new farm.
245
Stage 3: Upgrade SharePoint 2010 Products databases and service applications

The third stage in the upgrade process upgrades the databases and service
applications. A server farm administrator configures the service applications for
246
the new farm. The following service applications have databases that you can
upgrade during this process:
SharePoint Server 2010 and SharePoint Foundation 2010
Business Data Connectivity service application
SharePoint Server 2010 only
Managed Metadata service application
PerformancePoint Services service application
Search service application
Secure Store Service application
User Profile service application
A server farm administrator creates a web application on the SharePoint 2013
farm for each web application on the SharePoint 2010 Products farm.
A server farm administrator installs all server-side customizations.
247
A server farm administrator then attaches the content databases to the new farm
and upgrades the content databases for those web applications.
248
Stage 4: Upgrade SharePoint 2010 Products site collections

The final stage in the upgrade process is to upgrade the site collections. In
SharePoint 2013, site owners are in charge of upgrading their sites. The
upgrade process for My Sites is slightly different from for other types of site
collections.
Upgrade My Sites
A server farm administrator upgrades the My Site host and then individual users
can upgrade their My Sites or the farm administrator can upgrade them by using
249
Windows PowerShell. The following illustration shows four stages for the My Site
host and My Sites during the upgrade process.
Upgrade other SharePoint 2010 Products site collections

Owners of all other site collections can start to upgrade their sites as soon as they
see a notification on their site's home page that the new version is available. The
250
following illustration shows four stages for a site collection during the upgrade
process.
The site owner runs the site collection health checks to determine readiness for
upgrade. The site owner addresses issues before they continue with the next
step.
Optionally, the site owner requests an upgrade evaluation site collection. A timer
job runs to create the site collection and the site owner receives an email
message when the evaluation site collection is ready. The site owner previews
the new user interface. After several days or weeks, the evaluation site collection
251
expires and is deleted by a timer job. A server farm administrator can determine
the length of time before expiration.
When the site owner is ready, the site owner starts the upgrade process. The site
collection health checks are run again automatically. The site owner must address
issues before upgrading. If health checks return no issues, the upgrade starts.
When upgrade is complete, the site owner sees the Upgrade Status page that
contains the status and a link to the upgrade logs. The site owner reviews the site
to make sure that everything works correctly.
16.1 Task 1: Upgrade to SharePoint 2013

Step 1: Create the new SharePoint 2013 farm and web application.
You have done this already on the first day of the class. You have a web
application with the URL http://intranet.contoso.com
Step 2: Copy the databases to the new environment.

Please use SQL Server Management Studio to restore the sp2013-upgradecdb.bak file from your servers file system, e.g. c:\users\administrator\desktop.
1. Open SQL Management Studio.
252
2. Right click on Databases and select Restore Database
3. Select Device: in the menu and click on the ellipses () at the far right.
253
4. Under Backup media type, select File and click Add.
5. Navigate to the location of .bak file and select it.
254
6. Click OK to start Restore.
255
7. Navigate back to Databases and expand the tree. You should see your newly
restored database there.
256
Step 3: Upgrade the database using Windows PowerShell

1. Open SharePoint PowerShell and run the following command:
Mount-SPContentDatabase -Name WSS_Content_UpgradeTest WebApplication http://intranet.contoso.com
Notice the progress as a percentage completed:
257
The mount process is complete.
Step 4: Change the site collection administrators

1. Open Central Administration and navigate to Application Management >
View All Site Collections.
2. Verify that the sp2013upgrade site collection is there.
3. Click on Application Management > Change Site Collections

Administrators.
258
4. Select /sites/sp2013upgrade and click OK.
5. Notice that the site collection administrators from the old farm are present.
Make sure you change them to administrator and spfarmadmin respectively.
6. Click OK.
259
Step 5: View upgrade notification

1. Open http://intranet.contoso.com/sites/sp2013upgrade using your web
browser. You will see SharePoint 2013 user interface with a notification to
upgrade.
260
Step 6: Upgrade the site collection using PowerShell

You can use the UI on the home page to perform the upgrade but we are going to
use PowerShell to save time and to watch the real-time progress indicator from
PowerShell.
1. Open SharePoint PowerShell and run the following command:
Upgrade-SPSite http://intranet.contoso.com/sites/sp2013upgrade
VersionUpgrade
261
Step 7: View the new site

You should see the new SharePoint 2013 look & feel by visiting the URL:
http://intranet.contoso.com/sites/sp2013upgrade
In this exercise we learned how to upgrade a SharePoint 2010 content

database to SharePoint 2013 using PowerShell.
262

SharePoint 2013 Admin Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SharePoint 2013 Admin Manual

Hochgeladen von

Copyright:

Verfügbare Formate

SharePoint 2013 Administrator Training Course

SharePoint Innovations, LLC

Module 1 SharePoint 2013 Deployment Overview

Module 2 SharePoint 2013 Installation and Configuration

2.1 Task 1: Checking the Prerequisites to Install

Module 3 SharePoint 2013 Email Configuration

3.1 Task 1: Configure outgoing email

Module 4 SharePoint 2013 Deployment Best Practices

Module 5 SharePoint 2013 Unified Search

Configure Result Sources

Module 6 SharePoint 2013 Enterprise Metadata Management

6.1 Task 1: Setup Managed Metadata Service

Module 7 SharePoint 2013 PowerShell Introduction

7.1 Task 1: Cmdlets

Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245

SharePoint 2013 Administrator Course Manual

7.3 Task 3: SharePoint Structure

Module 8 SharePoint 2013 Site Administration

Customize User Permissions

Module 9 SharePoint 2013 Office Web Apps

Module 10 SharePoint 2013 Business Connectivity Services

10.1 Task 1: Create a Business Connectivity Service Application

Module 11 SharePoint 2013 SQL Reporting Services

Module 13 SharePoint 2013 Backup and Restore

Backup Architecture in SharePoint 2013

Module 14 SharePoint 2013 Governance

Module 15 SharePoint 2007 to SharePoint 2010 Migration

In-place upgrade Key Points

Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245

SharePoint 2013 Administrator Course Manual

Module 16 SharePoint 2010 to SharePoint 2013 Migration

16.1 Task 1: Upgrade to SharePoint 2013

Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245

SharePoint 2013 Administrator Course Manual

MODULE 1 SHAREPOINT 2013 DEPLOYMENT OVERVIEW

Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245

SharePoint 2013 Administrator Course Manual

MODULE 2 SHAREPOINT 2013 INSTALLATION AND CONFIGURATION

Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245

SharePoint 2013 Administrator Course Manual

Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245

SharePoint 2013 Administrator Course Manual

1. 2.1.1 Best Practice Service Accounts

SQL Server Service

Setup User Account

The domain user account for installing SharePoint 2013 on

Server Farm Account

The domain user account nominated as the database

Copyright SharePoint Innovations | sales@sharepointinnovations.com | 1-800-935-4245

SharePoint 2013 Administrator Course Manual

Performance Log Users

Performance Monitor Users

The farm account also has the following local

Adjust memory quotas for a process

Replace a process-level token

The domain user to run all SharePoint web site applications

Search Crawl Account

The domain user account with no explicit privileges to crawl

This account must have domain replication rights for UPS

The domain user account and trusted account for

Cache Super Reader

The object cache stores properties about items in

Cache super User

The object cache stores properties about items in