10174AD ENU LabManual

O F F I C I A L
M I C R O S O F T
L E A R N I N G
P R O D U C T
10174A
Lab Instructions and Lab Answer Key:
Configuring and Administering Microsoft
SharePoint 2010
Information in this document, including URL and other Internet Web site references, is subject to change without notice.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people,
places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain
name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright
laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,
mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft
Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject
matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this
document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no
representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the
products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of
Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of
Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any
changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from
any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply
endorsement of Microsoft of the site or the products contained therein.
2010 Microsoft Corporation. All rights reserved.
Microsoft, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
All other trademarks are property of their respective owners.
Product Number: 10174A

Part Number: X17-41871
Released: 09/2010
Lab Instructions: Introducing SharePoint 2010
Module 1
Contents:
Exercise 1: Creating Active Directory Accounts for SharePoint
Exercise 2: Installing SharePoint Server Prerequisites
Exercise 3: Installing SharePoint Server
Exercise 4: Configuring the SharePoint Installation
Exercise 5: Configuring the Farm with the Farm Configuration Wizard
10
Exercise 6 (Optional): Install a Language Pack
11
Lab Instructions: Introduucing SharePoint 2010
Lab: Insttalling SharePo

oint 201
10
Sccenario
Yo
ou have been asked to deplo
oy a SharePoin
nt farm to support Contosos strategic inittiatives related to
en
nterprise collaboration. This single-server farm
f
will act as a prototype, and executive
es, developers,, and
en
nd users will use it to evaluate the new fea
atures of Share
ePoint Server 2010.
2
f Sttart the virtu

ual machine
es
1..
Start 10174
4A-CONTOSO
O-DC-A.
2..
After CONT
TOSO-DC-A ha
as completed startup, start 10174A-SP20
1
10-WFE1-A.

Although you are creating a prototype environment, you must adhere to security best practices, including
least privilege. In this exercise, you create accounts for SharePoint administration, services, and access to
SQL Server.
The main tasks for this exercise are as follows:
1.
Create Active Directory accounts.
1.
2.
Create a SQL login for the SharePoint administrator.

Delegate administration of the SharePoint server.
f Task 1: Create Active Directory accounts

1.
Log on to SP2010-WFE1 as CONTOSO\Administrator with the password Pa$$w0rd.
2.
3.
Open Active Directory Users and Computers.

Expand the contoso.com domain and then in the SharePoint OU, create the following user
accounts. For each account, set the password to Pa$$w0rd, clear the User must change password
at next logon check box, and select the Password never expires check box.
User Logon
Name
Description
E-mail
SharePoint
Administrator
SP_Admin
SharePoint Administrator and

Setup User
SP_Admin @contoso.com
SharePoint Farm
Service
SP_Farm
SharePoint Farm Service
SP_Farm@contoso.com
SharePoint
Service
Applications
SP_ServiceApps SharePoint Service Applications
Full Name
4.
SP_ServiceApps@contoso.com
Close Active Directory Users and Computers.
f Task 2: Create a SQL Server login for the SharePoint administrator

1.
Open SQL Server Management Studio and connect to SP2010-WFE1 as CONTOSO\SQL_Admin with
the password of Pa$$w0rd.
2.
3.
4.
Create a login for CONTOSO\SP_Admin.

Assign the login the dbcreator and securityadmin server roles.
Close the Microsoft SQL Server Management Studio.
f Task 3: Delegate administration of the SharePoint server

1.
Add CONTOSO\SP_Admin to the local Administrators group of SP2010-WFE1.
2.
Log off of SP2010-WFE1.

Results: After this exercise, you should have accounts for SharePoint administration, services, and
database access, each of which has been delegated the least privilege permissions required to install
and configure SharePoint.

Scenario
You must install certain software components and perform specific configuration prior to installing
SharePoint 2010. You use the Prerequisites Installer to ensure that the required elements are in place.
1.
Attempt to install SharePoint Server prerequisites.
2.
3.
4.
Identify prerequisite installation errors.

Copy SharePoint prerequisite installation files
Script the installation of SharePoint Server prerequisites.
f Task 1: Attempt to install SharePoint Server prerequisites

1.
Log on to SP2010-WFE1 as CONTOSO\SP_Admin with the password Pa$$w0rd.
2.
3.
4.
Run D:\Software\SharePointServer2010\default.hta.
Click Install software prerequisites.
Step through the Microsoft SharePoint 2010 Products Preparation Tool.
The prerequisite installer prepares the server.
The Microsoft SharePoint 2010 Products Preparation Tool displays the message, There was an error
during installation. A summary of prerequisite installation status is also displayed.
f Task 2: Identify prerequisite installation errors

1.
Click Review the log file.
2.
Find the first instance of the text 976462. Observe the lines in the log file that indicate that the
prerequisite installer checked for the existence of Hotfix for Microsoft Windows (KB976462).
Find the next instance of the text 976462. Observe the lines in the log file that indicate that the
prerequisite installer attempted to download Hotfix for Microsoft Windows (KB976462) from
microsoft.com. Observe the URL that was used.
3.
You can use this URL to download the prerequisite manually. Click Cancel and then close the log file.
4.
Close the Microsoft SharePoint 2010 Products Preparation Tool and the SharePoint Server 2010 Start
page.
f Task 3: Copy SharePoint prerequisite installation files

Copy and paste all of the files from D:\Software\SharePoint Prerequisites to
D:\Software\SharePointServer2010\PrerequisiteInstallerFiles.
f Task 4: Script the installation of SharePoint Server prerequisites

1.
Open Notepad. Type the following, on one line, with spaces between each switch:
/SQLNCli:PrerequisiteInstallerFiles\sqlncli.msi
/ChartControl:PrerequisiteInstallerFiles\MSChart.exe
/KB976462:PrerequisiteInstallerFiles\Windows6.1-KB976462-v2-x64.msu
/IDFXR2:PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu
/Sync:PrerequisiteInstallerFiles\Synchronization.msi
/FilterPack:PrerequisiteInstallerFiles\FilterPack.msi
/ADOMD:PrerequisiteInstallerFiles\SQLSERVER2008_ASADOMD10.msi
/ReportingServices:PrerequisiteInstallerFiles\rsSharePoint.msi
/Speech:PrerequisiteInstallerFiles\SpeechPlatformRuntime.msi
/SpeechLPK:PrerequisiteInstallerFiles\MSSpeech_SR_en-US_TELE.msi
Alternately, you can copy the contents of the file D:\Labfiles\Lab01

\PrerequisiteInstaller.Arguments.txt and paste it into your Notepad document.
2.
3.
4.
5.
Save the file as D:\Software\SharePointServer2010

\PrerequisiteInstaller.Arguments.txt.
Close Notepad.
Start the Command Prompt using the Run as administrator option.
Type the following commands, each followed by ENTER:
D:
CD Software\SharePointServer2010
PrerequisiteInstaller.exe
The Microsoft SharePoint 2010 Products Preparation Tool appears.

In a production environment, you would also add the /unattended switch to the
PrerequisiteInstaller.Arguments.txt file to specify a silent, unattended installation of SharePoint
prerequisites. An unattended installation skips the Welcome page and the license agreement.
For this lab, however, you did not use the /unattended switch so that you may observe the progress of
the prerequisite installer and ensure that there are no errors in your script.
6.
Step through the Microsoft SharePoint 2010 Products Preparation Tool. When installation has
completed successfully, click Finish to close the tool.
Results: After this exercise, you should have installed and configured all SharePoint Server 2010
prerequisites.

Scenario
You are ready to install SharePoint Server 2010. In this exercise, you install the SharePoint binaries. In the
next exercise, you finish the initial configuration of the SharePoint installation.
You may choose to perform installation manually or to script the installation of SharePoint Server.
1A.
Install SharePoint Server.

or
1B.
Script the installation of SharePoint Server.
f Task 1A: Install SharePoint Server

1.
In the SharePointServer2010 folder, double-click default.hta. On the SharePoint Server installation

splash screen, click Install SharePoint Server.
2.
Complete the installation wizard using the following configuration information:

For the Product Key, type 36BY2-DVVJY-6426X-PXWVQ-BM342.
On the Permissions page, select the I accept the terms of this agreement check box, and then
click Continue.
On the Choose the installation you want page, click Server Farm.
On the Server Type page, select the Complete option, and then click Install Now.
Installation proceeds for approximately 710 minutes.
3.
4.
When installation completes, clear the Run the SharePoint Products Configuration Wizard now
check box, and then click Close.
On the SharePoint installation splash screen, click Exit, and then close the Windows Explorer window
that displays the contents of the SharePointServer2010 folder.
f Task 1B: Script the installation of SharePoint Server

1.
Edit D:\Software\SharePointServer2010\Files\SetupFarmSilent \config.xml.
2.
Replace line 11 with the following line:

<PIDKEY Value="36BY2-DVVJY-6426X-PXWVQ-BM342" />
Remove the comment tags, .

3.
Replace the Display element with the following:

<Display AcceptEULA="yes"
Level="basic"
CompletionNotice="yes" />
Alternately, copy D:\Labfiles\Lab01\config.xml to the D:\Software

\SharePointServer2010\Files\SetupFarmSilent folder, overwriting the existing file.
4.
5.
6.
Save the file and close Notepad.

Start Command Prompt using the Run as administrator option.
Type the following command on one line, and then press ENTER:
"D:\Software\SharePointServer2010\setup.exe" /config
"D:\Software\SharePointServer2010\Files\SetupFarmSilent\
config.xml"
Installation takes approximately 710 minutes.

7.
You can monitor the progress of the SharePoint installation using any of these methods:
Click Start, type %temp%, and then press ENTER. Open the log named SharePoint Server
Setup*.log.
Open Task Manager, and then monitor processes including Msiexec.exe, Setup.exe,
Mscorsvw.exe, and Psconfigui.exe.
8.
Clear the Run the SharePoint Products Configuration Wizard now check box and then close the
Run Configuration Wizard page.
Results: After this exercise, you should have installed SharePoint Server 2010.

Scenario
You are ready to complete the configuration of the SharePoint installation. In this exercise, you use the
SharePoint Products Configuration Wizard to configure the server and the farm.
You may choose to perform configuration manually or to script the configuration of SharePoint Server
and of the new farm.
1A.
or
1B.
Run the SharePoint Products Configuration Wizard.

Perform a scripted configuration of SharePoint Server.
f Task 1A: Run the SharePoint Products Configuration Wizard

1.
Open the SharePoint 2010 Products Configuration Wizard.
2.
Complete the wizard using the following configuration information:
Connect to a server farm: Create a new server farm

Database server: SP2010-WFE1
Database access username: CONTOSO\SP_Farm
Database access password: Pa$$w0rd
Farm passphrase: 10174_SharePoint_2010
Central Administration port number: 9999
The Configuring SharePoint Products page indicates the progress of configuration, which takes
approximately five minutes.
3.
When configuration has completed successfully, click Finish.

Windows Internet Explorer appears and opens the Help Make SharePoint Better page. This is the
Customer Experience Improvement survey page of the SharePoint 2010 Central Administration Web
site.
4.
5.
Select Yes, I am willing to participate (Recommended), and then click OK.

Close Internet Explorer.
You configure SharePoint in a later lab.
f Task 1B: Perform a scripted configuration of SharePoint Server

1.
Start Windows PowerShell 2.0 using the Run as administrator option.
2.
Type the following command, and then press ENTER:

D:\Labfiles\Lab01\ConfigureSharePoint.ps1
The Windows PowerShell Credential Request dialog box appears.

3.
In the Password box, type Pa$$w0rd, and then press ENTER.

A prompt appears to enter the farm passphrase.
4.
Type 10174_SharePoint_2010, and then press ENTER.

Configuration proceeds for 710 minutes.
5.
When the prompt Press Enter to exit appears, press ENTER.
Results: After this exercise, you should have configured SharePoint Server 2010 as a single-server
farm with the Central Administration application on port 9999.
10

In this exercise, you use the Farm Setup Wizard to configure the SharePoint farm and service applications
with default settings.
1.
Run the Farm Configuration Wizard.
f Task 1: Run the Farm Configuration Wizard

1.
Open SharePoint 2010 Central Administration and start the Farm Configuration Wizard. For the
service account, create a new managed account using the SP_ServiceApps account with the user
name CONTOSO\SP_ServiceApps, and the password Pa$$w0rd.
2.
Observe the list of service applications that will be created by the Farm Configuration Wizard. Clear
the check box next to User Profile Service Application and then proceed with the wizard by clicking
Next.
Farm service applications are created and started. This takes several minutes. Optionally, you can
open SQL Server Management Studio to follow the progress of the service application database
creation.
When the configuration is complete, the Create Site Collection page opens.
3.
Click Skip.
You create an intranet in the following exercises.
4.
On the Initial Farm Configuration Wizard page, click Finish.
Results: After this exercise, you should have a SharePoint farm and service applications configured with
default settings.
11

In this exercise, you install the French language pack.
1.
Install the French language pack.
2.
3.
Complete the configuration of the language pack.

Validate the installation of the language pack.
f Task 1: Install the French language pack

1.
Run D:\Software\SharePointLanguagePackFR \ServerLanguagePack.exe.
2.
3.
Select the Jaccepte les termes de ce contrat check box.

Click Continuer.
The language pack installs.
4.
5.
On the Excuter lAssistant Configuration page, clear the Excuter lAssistant Configuration des
produits SharePoint check box.
Click Fermer.
f Task 2: Complete the configuration of the language pack
Run the SharePoint 2010 Products Configuration Wizard.

After configuration is complete, SharePoint 2010 Central Administration opens.
f Task 3: Validate the installation of the language pack

1.
In SharePoint 2010 Central Administration, in the Quick Launch, click System Settings.
2.
3.
In the Servers section, click Manage servers in this farm.

Confirm that SP2010-WFE1 has the Language Pack for SharePoint, Project Server, and Office Web
Apps 2010 - French/Franais installed.
f To prepare for the next module

When you finish the lab, revert the virtual machines back to their initial state. To do this, complete the
following steps:
1. On the host computer, start Microsoft Hyper-V Manager.
2.
Right-click the virtual machine name in the Virtual Machines list, and then click Revert.
3.
In the Revert Virtual Machine dialog box, click Revert.
Lab Instructions: Creating a SharePoint 2010 Intranet
Module 2
Contents:
Exercise 1: Creating a Web Application
Exercise 2: Creating a Site Collection
Exercise 3: Creating a Site Collection in a New Content Database
Lab: Cre
eating a Sh
harePoint 2010 Intra
anet
Sccenario
Yo
ou have been asked to build
d an intranet to
o support com
mmunication and collaboratio
on requiremen
nts at
Co
ontoso, Ltd. Yo
ou have recently completed the installatio
on of SharePoint 2010. You must
m
now conffigure
th
he farm using the
t Farm Conffiguration Wizard, and create the logical to
opology to support the initial
bu
usiness require
ements. You are tasked with establishing a SharePoint 2010 intranet site so that bussiness
ussers can review
w the new feattures of the pu
ublishing site definition.
d
Add
ditionally, you have been askked to
co
onfigure sites to
t meet the co
ollaboration re
equirements off several divisio
ons within the
e organization.. You
w begin by cre
will
eating a site fo
or the Informa
ation Technolo
ogy (IT) department.
f Sttart the virtu

ual machine
es
1..
2..
Start 10174
4A-CONTOSO
O-DC-B.
After CONT
TOSO-DC has completed sta
artup, start 101
174A-SP2010
0-WFE1-B.

Scenario
In this exercise, you will create a new SharePoint Web application for the intranet.
1.
Create a new Web Application.
f Task 1: Create a new Web application

1.
2.
3.
Log on to SP2010-WFE1 as CONTOSO\SP_Admin with the password, Pa$$w0rd.

In SharePoint 2010 Central Administration, navigate to the Web Applications Management
page.
Create a new Web application with the following configuration:
Authentication: Classic Mode Authentication
Port: 80
Host header: intranet.contoso.com
Application pool name: SharePoint Web Applications
Application pool identity: CONTOSO\SP_ServiceApps
Database name: WSS_Content_Intranet
Results: After this exercise, you should have created a new Web application, intranet.contoso.com.

Scenario
In this exercise, you will create a site collection for the Intranet, and you will solve problems accessing the
new Web application.
1.
2.
3.
4.
5.
6.
Create a New Site Collection.

Attempt to Open the New Site.
Add a DNS Host Record for the New Web Application.
Open the New Site.
Create a Publishing Site Page.
Configure Permissions.
f Task 1: Create a new site collection
In SharePoint 2010 Central Administration, create a new site collection with the following
configuration:
Web application: http://intranet.contoso.com
Title: Contoso Intranet
Web site address: http://intranet.contoso.com/
Site definition: Publishing Portal
Primary site collection administrator: CONTOSO\SP_Admin
f Task 2: Attempt to open the new site
In Microsoft Internet Explorer, in the address bar, type http://intranet.contoso.com, and then
press ENTER.
An Internet Explorer cannot display the webpage error page is displayed.
Question: What is the cause of this error?
f Task 3: Add a DNS host record for the new Web application
Start DNS Manager using the Run as different user option. Enter the user name,
CONTOSO\Administrator, and the password, Pa$$w0rd.
Connect to the DNS server running on CONTOSO-DC.
Create a new host record in the contoso.com zone with the name, intranet, and the IP address,
10.0.0.21.
Close DNS Manager.
f Task 4: Open the new site

1.
In Internet Explorer, in the address bar, type http://intranet.contoso.com, and then press ENTER.
An Internet Explorer cannot display the webpage error is displayed. If this error does not appear on
your system, continue to the next task.
2.
3.
Open Command Prompt, and then execute the command, ipconfig /flushdns. Then close
Command Prompt.
The Web site begins to load. Because this is the first time that the site has been requested from the
server, it must be compiled. This takes several seconds.
The intranet Web application opens.
f Task 5: Create a publishing site page
Create a new page on the site with the name, Important Phone Numbers and with the following
page content:
In case of emergency, call 911
f Task 6: Configure permissions
Add the CONTOSO\Domain Users group to the Contoso Intranet Visitors group.
Results: Upon completing this exercise, you should have been able to successfully create a Contoso
intranet Web site.

Scenario
In this exercise, you will create a Web site for the Information Technology (IT) department on the Contoso
intranet. To support backup and restore operations according to Contosos SharePoint governance plan,
you will create the IT intranet Web site in its own content database. This will allow you to back up or
restore the Web site independently of the corporate intranet Web site you created in the previous
exercise.
1.
2.
3.
Create a Content Database.

Create a Site Collection in a Specific Content Database.
Examine the Information Technology Web site
f Task 1: Create a content database
In SharePoint 2010 Central Administration, create a new content database with the following
configuration in the Web application, http://intranet.contoso.com:
Database name: WSS_Content_Intranet_IT
f Task 2: Create a site collection in a specific content database
In SharePoint 2010 Central Administration, create a new site collection with the following
configuration:
Web application: http://intranet.contoso.com
Title: Information Technology
Web site address: http://intranet.contoso.com/sites/IT
Site definition: Team Site
f Task 3: Examine the information technology Web site
Navigate to http://intranet.contoso.com/sites/IT. Spend some time reviewing and experimenting

with the new site. You can make changes to the site, but those changes will not persist after this Lab.
Results: After this exercise, you should have created the intranet Web site for Contosos Information
Technology department.

following steps:
On the host computer, start Microsoft Hyper-V Manager.
Lab Instructions: Administering and Automating SharePoint
Module 3
Contents:
Lab A: Automating SharePoint with Windows PowerShell
Exercise 1: Adding SharePoint Functionality to Windows PowerShell
Exercise 2: Delegating the Ability to Use Windows PowerShell to

Manage SharePoint
Exercise 3: Reporting Web and Site Collection Properties
Exercise 4: Creating Site Collections Using Windows PowerShell
Exercise 5: Creating and Updating Items
Lab B: Administering SharePoint with Stsadm

Exercise 1: Executing Stsadm Commands
10
Lab Instructions: Administering and Automatting SharePoint
Lab A:
A Automating
g ShareP
Point with Win
ndows
Powe
erShell
Yo
ou are responssible for ensurring that the Sh
harePoint farm
m can be built consistently in
n both lab and
d
prroduction environments, and
d that the farm
m can be rebuilt in the eventt of a catastrop
phic failure.
Additionally, yo
ou are required
d to produce weekly
w
reports showing the webs
w
and stora
age utilization of each
sitte collection in
n the production farm. To meet
m
these goals, you must build
b
Windows PowerShell sccripts
th
hat can automate SharePointt management tasks.
f Sttart the virtu

ual machine
es
1..
Start 10174
4A-CONTOSO
O-DC-C.
2..
After CONT
artup, start 101
174A-SP2010
0-WFE1-C.

Scenario
To automate SharePoint management, you must use Windows PowerShell. But Windows PowerShell does
not load SharePoint .dll files or snap-ins by default. In this exercise, you learn several ways to add
SharePoint management functionality to Windows PowerShell.
1.
2.
3.
Load SharePoint .dll files using .NET reflection.

Add the SharePoint snap-in using the Add-PSSnapin cmdlet.
Open the SharePoint 2010 Management Shell.
f Task 1: Load SharePoint .dll files using .NET reflection

In the Windows Quick Launch, click Windows PowerShell.
To identify the assemblies that are currently loaded, type the following command and then press
ENTER:
[AppDomain]::CurrentDomain.GetAssemblies() | ForEach-Object { Split-Path $_.Location Leaf } | Sort
Microsoft.SharePoint.dll is not in the list. To use the SharePoint object model, you must load the
SharePoint .dll files.
Type the following command and then press ENTER:
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
The output displays GAC, version, and location information for the assembly.
Repeat step 3 to display the loaded assemblies.
Tip: You can press the UP key to scroll through previously executed commands.
The listing includes the Microsoft.SharePoint.dll.
f Task 2: Add the SharePoint snap-in using the Add-PSSnapin cmdlet

Get-PSSnapin
The output lists the snap-ins that have been added to the current session. The SharePoint snap-in is
not listed.
Get-PSSnapin Registered
The output lists the snap-ins that are registered on the system, except for those that are installed with
Windows PowerShell.
Add-PSSnapin Microsoft.SharePoint.PowerShell

Get-PSSnapin
now added.
ENTER:
The listing includes numerous SharePoint assemblies.

Rather than loading each assembly one by one, use the Add-PSSnapin cmdlet to load them all at
once.
Close Windows PowerShell.
f Task 3: Open SharePoint 2010 Management Shell

Click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint
2010 Management Shell.
Type the following command and press ENTER:
Get-PSSnapin
already added to the session.
To identify the assemblies that are currently loaded, type the following command and press ENTER:
The listing demonstrates that SharePoint 2010 Management Shell preloads the SharePoint .dll files.
Results: After this exercise, you will have learned how to run Windows PowerShell with the ability to
administer SharePoint.
Exercise 2: Delegating the Ability to Use Windows PowerShell to Manage

SharePoint
You have been asked to report the storage utilization of SharePoint site collections. In this exercise, you
discover that, without a delegation, you cannot use Windows PowerShell to manage SharePoint. You
perform the appropriate delegation, and then, in the next exercise, you continue with the task of
producing reports of SharePoint storage utilization.
1.
Attempt to use Windows PowerShell to enumerate webs.
2.
Configure least privilege rights to manage SharePoint with Windows PowerShell.
f Task 1: Attempt to use Windows PowerShell to enumerate webs

In SharePoint 2010 Management Shell, type the following command and then press ENTER:
$spsite = Get-SPSite "http://intranet.contoso.com"
To enumerate all of the webs in the site collection, type the following command and press ENTER:
$spsite | Get-SPWeb
An error appears indicating that login failed. The SP_Admin user account does not have the
permissions required to access the information about the intranet site collection with Windows
PowerShell.
f Task 2: Configure least privilege rights to manage SharePoint with Windows PowerShell
Start SharePoint 2010 Management Shell using the Run as different user option. Enter the user name,
Type the following commands each followed by ENTER:
$spcdb = Get-SPContentDatabase WSS_Content_Intranet
Add-SPShellAdmin -UserName CONTOSO\SP_Admin -Database $spcdb
Close Administrator SharePoint 2010 Management Shell.

Results: After this exercise, you will have delegated SP_Admin the ability to manage SharePoint with
Windows PowerShell.

You have been asked to produce a weekly report of the webs and storage utilization of SharePoint site
collections. In this exercise, you use Windows PowerShell to list all the webs in a site collection and to
produce reports of site collection properties.
1.
2.
3.
4.
Use Windows PowerShell to report web properties.

Attempt to use the grid-view to report site collection properties.
Install the Windows PowerShell Integrated Scripting Environment.
Use the grid-view to report site collection properties.
f Task 1: Use Windows PowerShell to report Web properties

Switch to SharePoint 2010 Management Shell.
List all of the sites in the site collection, http://intranet.contoso.com. Include the LastItemModifiedDate,
URL, and Created properties, and sort the results by Created.
Tip: You need to use the Get-SPSite, Get-SPWeb, and Select cmdlets.
f Task 2: Attempt to use the Grid-View to report site collection properties

To enumerate all of the site collections in the farm, except Central Administration, type the following
command and then press ENTER:
Get-SPSite

Get-SPSite | Select URL, @{Name="Storage"; Expression={"{0:N2} MB" -f
($_.Usage.Storage/1000000)}}, @{Name="Quota"; Expression={"{0:N2} MB" -f
($_.Quota.StorageMaximumLevel/1000000)} }
The listing displays various properties of each site collection.

($_.Quota.StorageMaximumLevel/1000000)} } | Out-GridView -Title "Sites with Usage"
An error indicates that the Windows PowerShell Integrated Scripting Environment feature is not
installed.
f Task 3: Install the Windows PowerShell Integrated Scripting Environment

Type the following two commands each followed by ENTER:
Import-Module ServerManager
Add-WindowsFeature PowerShell-ISE
An error indicates that you must run the command with elevated permissions.
Start Windows PowerShell using the Run as administrator option.
Close Administrator: Windows PowerShell.
f Task 4: Use the Grid-View to report site collection properties

In SharePoint 2010 Management Shell, press the UP arrow several times until you see the command
you typed in Task 2, and then press ENTER to rerun the command.
installed. This occurs because you must close and reopen SharePoint 2010 Management Shell to load
the component.
Close SharePoint 2010 Management Shell.
Open SharePoint 2010 Management Shell.
Type the following command and then press ENTER, which is the same as the command you executed
in the beginning of this task:
A Grid-View window appears displaying the output of the command.

Close the Sites With Usage window.
Results: After this exercise, you will have used Windows PowerShell to produce reports of your
SharePoint environment.

You have been asked to create sites on the intranet for Sales, Marketing, and HR. To create the site
collections and webs consistently in both the lab and production environments, you must create Windows
PowerShell scripts to create the new sites.
1.
Create a single site collection using Windows PowerShell.
2.
Create multiple site collections using Windows PowerShell.
f Task 1: Create a single site collection using Windows PowerShell

In SharePoint 2010 Management Shell, type the following commands:
New-SPContentDatabase -Name WSS_Content_Intranet_Sales -WebApplication
http://intranet.contoso.com
$spsite = New-SPSite -Url "http://intranet.contoso.com/sites/Sales" -ContentDatabase
WSS_Content_Intranet_Sales -OwnerAlias CONTOSO\SP_Admin -Template "STS#0"
A site collection and top-level web for the Sales department is created using the Team Site site
definition.
Open the Sales site with Windows Internet Explorer.
f Task 2: Create multiple site collections using Windows PowerShell

In SharePoint 2010 Management Shell, create a script with a loop that creates two new sites called HR
and Marketing.
Tip: Refer to the commands from the previous task and the following example of a loop.
$i = ("A", "B")
foreach($s in $i)
{
Write-Host $s
}
Get-SPSite
The output lists the new site collections.

Results: After this exercise, you will have used Windows PowerShell cmdlets and scripts to create new
content databases, site collections, and sites.

You want to modify the default announcement that is created on a new team site when you provision a
new site with your Windows PowerShell scripts.
The main task for this exercise is as follows:
1.
Modify a list item using Windows PowerShell.
f Task 1: Modify a list item using Windows PowerShell

Open your newly created Sales site.
Open the Announcements list, and then observe the title of the only item in the list.
$gc = Start-SPAssignment
$spsite = $gc | Get-SPSite "http://intranet.contoso.com/sites/Sales"
$splist = $spsite.rootweb.lists["Announcements"]
$splistitem = $splist.items[0]
$splistitem["Title"] = "Our SharePoint 2010 Sales site is now live!"
$splistitem.update()
$gc | Stop-SPAssignment
The list item will be updated. Notice that you did not use a cmdlet to update a list item. There are
things that will require direct access to the object model and, as such, you need to be careful to
dispose of objects you create.
Switch to Internet Explorer and then refresh the Announcements list, and then observe that the title
of the list item has been updated.
Close all Internet Explorer and Windows PowerShell windows.
Results: After this exercise, you will have updated a list item using a Windows PowerShell script.
f Do not shut down the virtual machines

Leave the virtual machines running. You will use them for Lab B.
10
Labb Instructions: Administering

n
and Automaating SharePoint
L B: Administ
Lab
A
tering SharePo
S
oint with Stsadm
Co
ontosos policies encourage and in some cases
c
mandate
e the automatiion of commo
on tasks. As succh, your
M
Microsoft
Office
e SharePoint Server
S
2007 environment had
d several Stsad
dm scripts thatt were used to create
sitte collections and
a webs.

C
s
Yo
ou have just finished setting up the new SharePoint Servver 2010 farm and you have
e been tasked with
w
te
esting some off the scripts to determine wh
hether changes have been made
m
to Stsadm
m that might break
b
th
he scripts.
Th
he main tasks for this exercisse are as follow
ws:
1..
2..
3..
4..
5..
Display Stsa
adm Help documentation.
Enumerate site collection
ns in a Web ap
pplication using
g Stsadm.
Create an Operations
O
site
e collection usiing Stsadm.
Create an Operations
O
Ma
aintenance site
e using Stsadm
m.
Configure the
t site collecttion administra
ator using Stsa
adm.
f Task 1: Displaay Stsadm Help

H
docume
entation
Start SharePoint 2010 Man
nagement She
ell using the Ru
un as adminisstrator option
n.
and and then press ENTER:
Type the following comma
stsadm
e output of the
e command, which
w
includes a list of the nu
umerous opera
ations supported by
Examine the
Stsadm. Also
o notice the exxamples displayed at the end
d of the Help documentation
d
n.
H
documenttation for the enumsites
e
ope
eration, type th
he following co
ommand and then
To display Help
press ENTER
R:
stsadm hel
lp enumsites
11
f Task 2: Enumerate site collections in a Web application using Stsadm

Use the enumsites operation of Stsadm to list the site collections in the Web application,
http://intranet.contoso.com.
Observe the amount of time that the operation takes to complete.
Review the XML response that you get from the command, and note that this can be used in a
Windows PowerShell script to iterate through all your site collections.
Type the following command, and observe the amount of time it takes for the command to execute:
Get-SPSite "http://intranet.contoso.com" | Get-SPWeb
Repeat steps 1 and 2, and observe the amount of time it takes for each command to execute.
f Task 3: Create an Operations site collection using Stsadm

Use the createsite operation of Stsadm to create a site collection and top-level web for the Operations
department, with the URL http://intranet.contoso.com/sites/Operations. Assign
CONTOSO\SP_Admin as the site administrator with the e-mail address sharepoint@contoso.com.
In Internet Explorer, browse to http://intranet.contoso.com/sites/Operations. Select the Team Site
template and accept the default group configuration.
f Task 4: Create an Operations Maintenance site using Stsadm

Use the createweb operation of Stsadm to create a web for the Maintenance department with the URL
http://intranet.contoso.com/sites/Operations/Maintenance.
In Internet Explorer, browse to the new site and select the Team Site template.
f Task 5: Configure the site collection administrator using Stsadm

Attempt to sign in to the Maintenance site as CONTOSO\Administrator with the password
Pa$$w0rd.
Access is denied.
Use the siteowner operation of Stsadm to assign CONTOSO\Administrator as the site administrator
of the Operations site collection.
Confirm that you can open the Maintenance web as CONTOSO\Administrator.
Results: After this exercise, you will have executed several Stsadm commands to create a new
Operations site collection and web with a specific site collection administrator.

following steps:
Lab Instructions: Configuring Content Management
Module 4
Contents:
Lab A: Configuring List Throttling and Remote BLOB Storage
Exercise 1: Configuring List Throttling
Exercise 2: Enabling FILESTREAM and Provisioning the RBS Data Store
Exercise 3: Installing RBS on All SharePoint Web and Application Servers
Exercise 4: Configuring the BLOB Size Threshold for RBS
Lab B: Configuring Managed Metadata

Exercise 1: Configuring and Implementing Managed Metadata
Lab A: Configuring List Throttling and Remote BLOB

Storage
Scenario
You have just installed a new SharePoint 2010 server farm at Contoso, Ltd. Your previous SharePoint 2007
environment included some very large lists that performed poorly for end users and large document
libraries that increased the size of content databases and therefore the time required to perform backup
and restore operations. Your revised governance policy for SharePoint 2010 requires that large lists have
controls to manage performance and that the size of content databases be more carefully managed. To
support these requirements, you have been tasked with implementing list throttling and Remote BLOB
Storage.
f Log on to the virtual machine for this lab

1.
Start 10174A-CONTOSO-DC-D.
1.
After CONTOSO-DC has completed startup, start 10174A-SP2010-WFE1-D.

In this exercise, you experience latency problems when performing operations on very large lists. You
apply list throttling to ensure that such operations do not cause excessive stress on the SharePoint farm.
1.
Create a computer inventory list.
2.
Configure least privilege rights to manage SharePoint using Windows PowerShell.
3.
Create a large list using Windows PowerShell.
4.
Observe the list view threshold.
5.
Add items to exceed the list threshold.
6.
Experience list throttling.
7.
Configure list throttling.
f Task 1: Create a computer inventory list
Log on to SP2010-WFE1 as CONTOSO\SP_Admin using the password Pa$$w0rd.
Open Internet Explorer, and then browse to http://intranet.contoso.com

/sites/IT.
Create a custom list named ComputerInventory. After creating the list, change its name and
description to Computer Inventory (with a space).
Create two single-line text columns named Computer Name and Serial Number.
f Task 2: Configure least privilege rights to manage SharePoint using Windows PowerShell
Start SharePoint 2010 Management Shell using the Run as different user option. Enter the user
name CONTOSO\Administrator and the password Pa$$w0rd.

Add-SPShellAdmin -UserName CONTOSO\SP_Admin -Database (Get-SPContentDatabase
"WSS_Content_Intranet_IT" )
Close the Windows PowerShell window.
f Task 3: Create a large list using Windows PowerShell
In SharePoint 2010 Management Shell, create 4,000 items in the new list by typing the following
commands:
$site = Get-SPSite "http://intranet.contoso.com/sites/IT"
$web = $site.rootweb
$list = $web.Lists["Computer Inventory"]
$i = 1
do {
#add item
$newitem = $list.items.Add()
$newitem["Title"] = "Client-" + $i.ToString().PadLeft(4, "0");
$newitem["Computer Name"] = "Client-" + $i.ToString().PadLeft(4, "0");
$newitem["Serial Number"] = $i.ToString().PadLeft(8,"0");
$newitem.Update()
$i++
}
while ($i -le 4000)
$web.dispose()
$site.dispose()
You can watch the progress of the script by refreshing the Computer Inventory list page in the IT
Web.
f Task 4: Observe the list view threshold
Open the List Settings of the Computer Inventory list, and then verify that the List view threshold
message indicates that the list contains 4,000 items.
f Task 5: Add items to exceed the list threshold
In SharePoint 2010 Management Shell, create 5,000 additional items in the Computer Inventory list
by typing the following commands:
$i = 4001
do {
#add item
$newitem.Update()
$i++
}
while ($i -le 9000)
$web.dispose()
$site.dispose()
Web.
f Task 6: Experience list throttling
Switch to Internet Explorer and refresh the view of the Computer Inventory list.
Open the List Settings of the Computer Inventory list, and then verify that the List view threshold
message indicates that the list contains 9,000 items.
Attempt to delete the list.

An Error page appears that indicates the operation is prohibited because it exceeds the list view
threshold.
Return to the Computer Inventory list, point at the Title column header, and then click the dropdown arrow that appears.
A message appears: Cannot show the value of the filter. The field may not be filterable, or the number
of items returned exceeds the list view threshold enforced by the administrator.
f Task 7: Configure list throttling
Open SharePoint 2010 Central Administration. In Central Administration, change the resource
throttling settings for the SharePoint intranet.contoso.com80 Web application. Configure the List
View Threshold to 10000.
Switch back to the Computer Inventory list. In the Computer Inventory list, point at the Title
column header, and then click the drop-down arrow that appears. Verify that the Show Filter
Choices command is now available.
In Central Administration, change the resource throttling settings for the SharePoint
intranet.contoso.com80 Web application. Configure the List View Threshold to 7000, with a daily
time window for large queries from 11pm to 4am.
Open the List Settings of the Computer Inventory list, and then observe the List view threshold.
Verify that the new list threshold of 7,000 items has been applied.
Results: After this exercise, you should have modified list throttling settings for a site collection.

In this exercise, you enable FILESTREAM and configure RBS on the computer that is running SQL Server
2008.
1.
Enable FILESTREAM on the computer running SQL Server.
2.
Provision a BLOB store.
f Task 1: Enable FILESTREAM on the computer running SQL Server
Start SQL Server Configuration Manager using the Run as a different user option. Enter the user
Click SQL Server Services, and then open the properties of SQL Server (MSSQLServer). In the
FILESTREAM tab, select all three check boxes, and then close SQL Server Configuration Manager.
Start SQL Server Management Studio using the Run as a different user option. Enter the user
Open the properties of SP2010-WFE1, and then configure Filestream Access Level so that full
access is enabled. Then, restart SQL Server services.
f Task 2: Provision a BLOB store
In SQL Server Management Studio, select the WSS_Content_Intranet_IT content database. Set the
database master key by executing the following query:
use [WSS_Content_Intranet_IT]
if not exists (select * from sys.symmetric_keys where name =
N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Master Key
Pa$$w0rd'
Add a filegroup for the RBS provider by executing the following query:
if not exists (select groupname from sysfilegroups where
groupname=N'RBSFilestreamProvider')alter database [WSS_Content_Intranet_IT]
add filegroup RBSFilestreamProvider contains filestream
Add a file system mapping for the RBS provider by executing the following query:
alter database [WSS_Content_Intranet_IT] add file (name = RBSFilestreamFile, filename
= 'c:\Blobstore') to filegroup RBSFilestreamProvider
Results: After this exercise, you should have enabled FILESTREAM and configured RBS on the
computer running SQL Server.

In this exercise, you install RBS on all Web and application servers in the SharePoint farm.
1.
Install RBS on the first Web server.
2.
Confirm the installation of RBS.
3.
Enable RBS for a content database.
4.
Test the RBS provider.
f Task 1: Install RBS on the first Web server
Start Command Prompt using the Run as administrator option. Change to the D:\Labfiles\Lab04
folder, type the following command, and then wait one minute for the operation to complete:
msiexec /qn /lvx* rbs_install_log1.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true
FILEGROUP=PRIMARY DBNAME="WSS_Content_Intranet_IT" DBINSTANCE="SP2010-WFE1"
FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
f Task 2: Confirm the installation of RBS
Open D:\Labfiles\Lab04\rbs_install_Log1.txt, and then confirm that you see the following line
within the last 20 lines of the end of the file:
Product: SQL Server 2008 R2 Remote Blob Store -- Installation completed successfully.
In SQL Server Management Studio, refresh the view of the Object Explorer tree, and then verify that
several tables exist in the WSS_Content_Intranet_IT database that have names that begin with the
letters mssqlrbs.
f Task 3: Enable RBS for a content database
In SharePoint 2010 Management Shell, enable RBS for the WSS_Content_Intranet_IT database by
typing the following commands:
$cdb = Get-SPContentDatabase "WSS_Content_Intranet_IT"
$rbss = $cdb.RemoteBlobStorageSettings
$rbss.Installed()
$rbss.Enable()
$rbss.SetActiveProviderName($rbss.GetProviderNames()[0])
$rbss
f Task 4: Test the RBS provider
Open the C:\Blobstore folder, and then observe the number of items in the folder.

/sites/IT. Navigate to the Shared Documents document library, and then upload the file
D:\LabFiles\Lab04\rbs_install_log1.
Switch to Windows Explorer and verify that the file has been added to the Blobstore folder.
Results: After this exercise, you should have configured RBS on the SharePoint farm and tested its
functionality.

You have discovered that, by default, RBS stores all BLOBs in the Blobstore folder. After testing in your lab,
you determined that optimal performance is achieved on your infrastructure when BLOBs of less than 1
Megabyte (MB) are stored in the content database, and BLOBs greater than 1 MB are stored in the file
system. In this exercise, you configure RBS so that only files greater than 1 MB are stored in the file
system.
1.
Configure the minimum blob storage size.
2.
Validate the behavior of minimum blob storage size.
f Task 1: Configure the minimum BLOB storage size
In SharePoint 2010 Management Shell, configure the MinimumBlobStorageSize property to 1 MB

by typing the following commands:
$rbss.MinimumBlobStorageSize = 1048576
$cdb.update()
f Task 2: Validate the behavior of minimum BLOB storage size
Switch to Internet Explorer, and then upload the

D:\LabFiles\Lab04\SharePoint_2010_Walkthrough_Guide.pdf to the IT document library.
Upload the D:\LabFiles\Lab04\SharePoint_2010_Datasheet.pdf to the IT document library.
Switch to Windows Explorer, open the C:\Blobstore folder, and, by examining file sizes and
timestamps, verify that SharePoint_2010_Walkthrough_Guide.pdf was moved to Blobstore
whereas SharePoint_2010_Datasheet.pdf was not moved to Blobstore.
Results: After this exercise, you should have modified the RBS configuration to store files larger than
1 Mbyte in the file system.
Leave the virtual machines running. You use them for Lab B.
Scenario
The knowledge management team at Contoso is excited about the ability of SharePoint 2010 to support
an enterprise taxonomy. They have asked you to prototype the functionality of the managed metadata
service and of terms.

In this exercise, you create a term set of departments at Contoso. You use the term set as metadata in a
list that helps you keep track of help desk support requests.
1.
Assign Term Set Administrators.
1.
Create a group, a term set, and terms.
2.
Add a managed metadata column to a list.
3.
Add items with managed metadata.
4.
Configure metadata navigation.
f Task 1: Assign Term Store Administrators
In Central Administration, assign CONTOSO\SP_Admin as a Term Store Administrator.
f Task 2: Create a group, a term set, and terms
In Term Store Management, create a new group named Organization.
Create a new term set named Department. Configure the term set with a closed submission policy.
Add terms for the following departments: Marketing, Finance, IT, and Sales.
10
f Task 3: Add a managed metadata column to a list
Open Internet Explorer, and then browse to http://intranet.contoso.com/sites/IT.
Create a new custom list named SupportRequests.
Create a single-line text column named User Name.
Create a managed metadata column named Department using the Department term set.
Create a managed metadata column named Request Type using a custom term set. Configure the
custom term with an open submission policy.
f Task 4: Add items with managed metadata
Add the following items to the Support Requests list:

Title
User Name
Department
Request Type
Create a new account for Andy Ruth
AndyR
Finance
New User
Reset password for Christa Geller
ChristaG
IT
Password Reset
Problem starting computer
FrankM
Marketing
Desktop Support
Create a new account for Sean Chai
SeanC
Sales
New User
Reset password for Lola Jacobsen
LolaJ
Sales
Password Reset
Tip: To add a new term you must add it to the term store by clicking the Browse For A Valid Choice
icon, and then clicking the Add New Item link.
Tip: Use the Suggestions list to enter departments without having to type the entire department
name.
f Task 5: Configure metadata navigation
Configure the metadata navigation settings of the SupportRequest list so that Department and
Request Type are the selected hierarchy fields.
Observe the tree view below the Quick Launch. Click the terms in the Department and Request
Type term sets to filter the list.
Results: After this exercise, you should have created term sets and a SupportRequest list with
managed metadata columns, and you should have configured metadata navigation to filter the list.

following steps:
In the Revert Virtual Machine dialog, click Revert.
Lab Instructions: Configuring Authentication
Module 5
Contents:
Lab A: Configuring Custom Authentication
Exercise 1: Creating and Configuring an ASP.NET Membership Database
Exercise 2: Creating a Web Application That Uses

Claims-Based Authentication
Lab B: Configuring Secure Store

Exercise 1: Creating User Accounts for Access to External Data
Exercise 2: Configuring Secure Store Services
Exercise 3: Configuring Secure Store Unattended Accounts
11
Scenario
The Client Services department at Contoso, Ltd. has asked you to establish a SharePoint site with which
employees and clients can collaborate. Your organizational IT Policy states that only employees shall have
an Active Directory account. Therefore, you must configure a custom authentication mechanism using
forms based authentication, so that user accounts for clients can be maintained in a separate database.
f Start the virtual machines

1.
2.

In this exercise, you will create a membership and role database using the schema and tools provided with
ASP.NET. You will configure the .NET framework and SharePoint Central Administration to connect to the
database, and then you will create user accounts in the database.
1.
Create an ASP.NET membership database.
2.
Configure the connection to the database.
3.
Create users.
4.
Enable the Secure Token Service to use forms-based authentication.
f Task 1: Create an ASP.NET membership database
Start Command Prompt with the Run as administrator option.
Type the following commands:

cd c:\windows\microsoft.net\framework\v2.0.50727
aspnet_regsql.exe
Accept all of the defaults in the ASP.NET SQL Server Setup Wizard.
f Task 2: Configure the connection to the database
With Notepad, open c:\windows\microsoft.net\framework

\v2.0.50727\config\machine.config. Modify the connectionStrings element of the XML file to
match the following, and then save and close the file.
<connectionStrings>
<clear/>
<add name="LocalSQLServer"
connectionString="Server=.;Database=aspnetdb;uid=sa;pwd=Pa$$w0rd;"
providerName="System.Data.SqlClient"/>
</connectionStrings>
Repeat the previous step for the file, c:\windows\microsoft.net

\framework64\v2.0.50727\config\machine.config.
f Task 3: Create users
Start SharePoint 2010 Management Shell with the Run as administrator option, and then type the
following commands:
$member = New-Object System.Web.Security.SQLMembershipProvider
$vals=New-Object System.Collections.Specialized.NameValueCollection
$vals.Add("name", "sql")
$vals.Add("connectionStringName", "LocalSQLServer")
$vals.Add("applicationName", "/")
$member.Initialize("sql", $vals);
$status = New-Object System.Web.Security.MembershipCreateStatus
$member.CreateUser('SiteAdministrator', 'Pa$$w0rd', 'SharePoint@contoso.com', 'first
person kissed', 'mom', $true, $id, [ref] $status)
Ignore the error message that indicates the membership provider name specified is invalid.
Type the following command:

$status
Verify that the last message you see is Success.

$member.CreateUser('JamesF', 'Pa$$w0rd', 'JamesF@tailspintoys.com', 'favorite pet',
'Spot', $true, $id, [ref] $status)

$status
f Task 4: Enable the secure token service to use forms-based authentication
With Notepad, open the file, c:\program files\common files\microsoft shared\web server
extensions\14\webservices\root\web.config.
Remove the <clear> statements within system.web\membership\providers and

roleManager\providers xpath elements. Then save and close the file.
Results: After completing this exercise, you should have a new custom database to support formsbased authentication for SharePoint, and you should have two user accounts in the database.
Exercise 2: Creating a Web Application That Uses Claims-Based

Authentication
In this exercise, you will create a Web application to support collaboration with external clients. You will
provide Windows authentication for employees and forms-based authentication for clients.
1.
Create a Web Application that uses both Windows and forms-based authentication.
2.
Add a DNS host record for the new Web application.
3.
Test claims-based authentication.
f Task 1: Create a Web application that uses both Windows and forms-based
authentication
In Central Administration, click the Manage web applications link and create a new Web
application with the following settings:
Authentication: Claims Based Authentication
Port: 80
Host Header: clients.contoso.com
Claims Authentication Types: Integrated Windows Authentication (NTLM) and Forms Based
Authentication
ASP.NET Membership provider name: AspNetSqlMembershipProvider
ASP.NET Role manager name: AspNetSqlRoleProvider
Application Pool: SharePoint 80 (CONTOSO\SP_ServiceApps)
Database name: WSS_Content_Clients
Create a site collection in the new Web application with the following settings:
Title: CONTOSO Client Portal
Template Selection: Publishing Portal
Primary Site Collection Administrator: CONTOSO\SP_Admin
Secondary Site Collection Administrator: SiteAdministrator
Start DNS Manager using the Run as different user option. Enter the user name,
In the contoso.com forward lookup zone, create a new host record named clients with the address
10.0.0.21.
Close DNS Manager.
f Task 3: Test claims-based authentication
Open Internet Explorer, and then browse to http://clients.contoso.com.
Sign in using Forms Authentication with the user name SiteAdministrator and the password,
Pa$$w0rd.
Click Sign in as Different User and then sign in with Windows Authentication as SP_Admin with
the password, Pa$$w0rd.
Results: After completing this exercise, you should have created a Web application that is accessible
both by employees, using Windows authentication, and by clients, using forms-based authentication.
Lab B: Configure Secure Store
Scenario
Information workers at Contoso, Ltd. have started using the new intranet portal site and would like to start
using SharePoint Designer 2010 to add Business Connectivity Services applications to pages.
Organizational IT policy states that under no circumstances shall credentials be stored in an unencrypted
manner in applications. Because of this policy, users will not be allowed to embed credentials in the
ASP.NET pages. You have been tasked with configuring Secure Store Service to facilitate the
authentication for these information workers.

Scenario
In this exercise, you will establish user accounts in Active Directory that will be assigned to target
applications in the Secure Store in the next exercise.
1.
Create Active Directory accounts.
On SP2010-WFE1, start Active Directory Users and Computers using the Run as different user
option. Enter the user name, CONTOSO\Administrator, and the password, Pa$$w0rd.
In the Users container, create the user accounts listed in the table below. For each account, set the
password to Pa$$w0rd, clear the User must change password at next logon check box, and select
the Password never expires check boxes.
Full name
User logon name
Excel Unattended Service Account
SP_Excel_USA
PerformancePoint Unattended Service Account
SP_PerfPoint_USA
Visio Graphics Unattended Service Account
SP_Visio_USA

In this exercise, you will configure Secure Store Services to store credentials that can be used by service
applications to access data.
1.
Initialize an instance of a Secure Store Service application.
2.
Create a target application for Excel Services.
3.
Configure the Secure Store credentials for Excel Services.
4.
Create a target application for Visio Graphics.
5.
Configure the Secure Store credentials for Visio Graphics
f Task 1: Initialize an instance of a Secure Store Service application
In Central Administration, navigate to the Manage Service Applications page, and then click the
Secure Store Service link on the Secure Store Service Application row.
Generate a new key with the pass phrase, 10174_SSS_2010.
f Task 2: Create a target application for Excel Services
Create a target application with the following configuration:
Target Application ID: ExcelUnattendedSA
Display Name: Excel Unattended Service Account
Contact E-mail: sharepoint@contoso.com
Target Application Type: Group
Target Application Page URL: None
Target Application Administrators: CONTOSO\SP_Admin
Members: Domain Users
f Task 3: Configure the Secure Store credentials for Excel Services
Set the credentials of the ExcelUnattendedSA application.
Enter the user name, CONTOSO\SP_Excel_USA, and the password, Pa$$w0rd.
f Task 4: Create a target application for Visio Graphics
Create a target application with the following configuration:
Target Application ID: VisioUnattendedSA
Display Name: Visio Unattended Service Account
Contact E-mail: sharepoint@contoso.com
Target Application Type: Group
Target Application Page URL: None
Target Application Administrators: CONTOSO\SP_Admin
Members: Domain Users
f Task 5: Configure the Secure Store credentials for Visio Graphics
Set the credentials of the VisioUnattendedSA application.
10
Enter the user name, CONTOSO\SP_Visio_USA, and the password, Pa$$w0rd.

Results: After completing this exercise, you should have fully configured the Secure Store Service and
created two target applications.
11

In this exercise, you will configure three service applications to use credentials in the Secure Store.
1.
Configure Excel Services Secure Store account.
2.
Configure Performance Point Secure Store account.
3.
Configure Visio Graphics Secure Store account.
f Task 1: Configure Excel Services Secure Store account
Configure the Excel Services Application global settings to use the Application ID,
ExcelUnattendedSA, to access external data.
Excel Services can now use the credentials in Secure Store to render spreadsheets and connect to
external data connections.
f Task 2: Configure Performance Point Secure Store account
Configure the Performance Point Service Application settings so that the Secure Store and
unattended service account is the user name, CONTOSO\SP_PerfPoint_USA, and the password,
Pa$$w0rd.
f Task 3: Configuring Visio Graphics Secure Store account
Configure the Visio Graphics Service global settings to use the application ID, VisioUnattendedSA,
to access external data.
Visio can now execute diagrams, and data connection refreshes using the unattended account.
Results: After completing this exercise, you should have configured Excel Services, PerformancePoint
and Visio to have an Unattended Secure Store account.

When you finish the lab, reset the virtual machines back to their initial state. To do this, complete the
following steps:
Lab Instructions: Securing Content
Module 6
Contents:
Exercise 1: Managing SharePoint Groups
Exercise 2: Creating Custom Permission Levels
Exercise 3: Managing Permissions and Inheritance
Exercise 4: Creating a Web Application Policy
Lab: Configuring Security for SharePoint Content
Scenario
You have created an intranet on a new SharePoint 2010 farm at Contoso, Ltd. You have been tasked with
helping set up users, groups, and permissions on the intranet until governance and training are in place,
at which point permission management will be delegated to site collection administrators. Additionally,
you must configure SharePoint to support the business requirement that the internal security and
compliance audit team has the ability to access all information stored on the intranet.

1.
2.

The IT site collection must be secured so that users in the IT department can make changes and users
from other departments can view but not modify content. Additionally, you have been asked to add a
group to each team site that assigns the Design permission level to its members.
1.
2.
3.
4.
5.
Add a user to a sites Members group.

Verify that the member can sign in.
Add a user to a sites Visitors group.
Verify that the visitor can sign in.
Create a new group and assign it the Design permission level.
f Task 1: Add a user to a sites Members group
Open Windows Internet Explorer, and then browse to http://intranet.contoso.com/sites/IT.
Add the user CONTOSO\SanjayS to the site, assigning him to the Information Technology
Members [Contribute] group.
You have now added Sanjay Shah, the Contoso chief technology officer (CTO), as a contributor to the
IT intranet Web, which gives him Read and Write permissions.
f Task 2: Verify that the member can sign in
Browse to http://intranet.contoso.com/sites/IT. Sign in to the site as CONTOSO\SanjayS with the

password Pa$$w0rd. Add a new task to the Tasks list titled Select SharePoint Governance Team.
f Task 3: Add a user to a sites Visitors group
Sign in to the site as CONTOSO\SP_Admin with the password Pa$$w0rd.
Observe the membership of the Information Technology Dept Visitors group, and then add the
user CONTOSO\JeffL to the group.
You have now added Jeff Low, the Contoso vice president of finance, as a visitor to the IT intranet
Web, which gives him Read permission.
f Task 4: Verify that the visitor can sign in
Browse to http://intranet.contoso.com/sites/IT. Sign in to the site as CONTOSO\JeffL with the

password Pa$$w0rd. Verify that you do not see the Add new item link in the Tasks list.
f Task 5: Create a new group and assign it the Design permission level
Sign in to the site as CONTOSO\SP_Admin with the password Pa$$w0rd.
Create a new group named Information Technology Dept Designers, and give it the Design
permission level. Configure the groups description to read as follows: Use this group to grant
people Design permissions to the SharePoint site: Information Technology Dept.
Results: After this exercise, you should have added users to the Members and Visitors groups and
created a new SharePoint group.

Lola Jacobsen has been tasked with monitoring the usage of the IT Web and all other intranet Webs. You
must configure the least privilege permissions required for her to access the out of the box Web Analytics
reports. You want to implement best practice, role-based management, so you will create a group with
which to assign her the required permissions.
1.
Create a custom permission level to allow viewing Web analytics reports.
2.
Attempt to view Web analytics reports.
3.
Add a permission to the custom permission level.
4.
Validate the functionality of the custom permission level.
f Task 1: Create a custom permission level to allow viewing Web analytics reports
Create a custom permission level named View Usage with the description Can see only usage data
about this site. Assign the View Web Analytics Data permission. Additional permissions will be
selected automatically.
Create a group named Usage Monitors with the description Use this group to grant people
permission to view Web Analytics data for the SharePoint site: Information Technology Dept.
Assign the group the View Usage permission level.
Add the user, CONTOSO\LolaJ to the group.
f Task 2: Attempt to view Web analytics reports
Browse to http://intranet.contoso.com/sites/IT, and then sign in as CONTOSO\LolaJ with the

password Pa$$w0rd. You will be denied access. Browse to the usage reports page
http://intranet.contoso.com/sites/it/_layouts/usageDetails.aspx. Again, you will be denied access
because, although you have permission to access Web analytics data, you do not yet have permission
to view the default application pages that present that data.
f Task 3: Add a permission to the custom permission level
Sign into the IT site as CONTOSO\SP_Admin with the password Pa$$w0rd. Edit the View Usage
permission level, adding the View Application Pages permission.
f Task 4: Validate the functionality of the custom permission level
Browse to http://intranet.contoso.com/sites/IT, and then sign in as CONTOSO\LolaJ with the

password, Pa$$w0rd. You will be denied access. Browse to the site settings page,
http://intranet.contoso.com/sites/it/_layouts/settings.aspx. Examine the Site Web Analytics
reports and the Site Collection Web Analytics reports.
Results: After this exercise, you should have created a new custom permission level assigned to a
custom group that gives users the ability to view Web Analytics reports.

You want to create a folder in which Lola Jacobsen can save usage reports she generates. Because Lola is
not in the IT department itself, she should not have Contribute permission to the entire IT Web. In this
exercise, you manage permissions and experience the behavior of the security-trimmed SharePoint
interface.
1.
Add a document and a folder to a library.
2.
Assign permissions to a folder.
3.
Verify the behavior of SharePoint permissions.
f Task 1: Add a document and a folder to a library
Browse to http://intranet.contoso.com/sites/IT. Sign in to the site as CONTOSO\SP_Admin with

the password Pa$$w0rd.
Open the Shared Documents document library. Upload the document D:\Labfiles\LAB06\ IT
Policies and Procedures for SharePoint 2010.
Create a new folder in the document library named Usage Reports.
f Task 2: Assign permissions to a folder
Configure permissions on the Usage Reports folder so that the only permission on the folder is one
that gives CONTOSO\LolaJ the Full Control permission level.
f Task 3: Verify the behavior of SharePoint permissions
Browse to http://intranet.contoso.com/sites/IT. Sign in to the site as CONTOSO\LolaJ with the

password Pa$$w0rd. You will be denied access because LolaJ does not have permission to the home
page. Browse to the URL of the Shared Documents document library. You are able to see the Usage
Reports folder but not the policies document.
Close all open Internet Explorer windows.

Results: After this exercise, you should have configured a list and list item with custom permissions.

The SharePoint governance plan at Contoso specifies that a group of internal auditors will have the ability
to view all content to ensure compliance with information security and information management policies.
This group will have Read access to content. Additionally, a group must have the ability to access all
content with Full Control permission in the event that noncompliant content must be removed, but the
group with this level of access will not include any user accounts unless and until action must be taken.
Finally, the environment must support the ability to deny one or more users access to SharePoint, in the
event of a security incident.
1.
Add a user to a group.
2.
Create groups.
3.
Create a Read Web application policy.
4.
Create a Full Control Web application policy.
5.
Create a deny Web application policy.
6.
Verify the behavior of SharePoint Web application policies.
f Task 1: Add a user to a group
On SP2010-WFE1, start Active Directory Users and Computers with the Run as different user
option. Enter the user name CONTOSO\Administrator and the password Pa$$w0rd.
Open the Users container. Create a new group named SharePoint Content Auditors. Add
CONTOSO\JimD to the SharePoint Content Auditors group.
f Task 2: Create groups
Create a group named SharePoint Full Control Policy.
Create a group named SharePoint Deny Policy, and then close Active Directory Users and
Computers.
f Task 3: Create a Read Web application policy
Open Central Administration.
In the User Policy for the intranet Web application, add a user policy that gives
CONTOSO\SharePoint Content Auditors the ability to read all content from all zones.
f Task 4: Create a Full Control Web application policy
Add a user policy that gives CONTOSO\SharePoint Full Control Policy full control of all content
from all zones.
f Task 5: Create a Deny Web application policy
Add a user policy that denies CONTOSO\SharePoint Deny Policy any access from all zones.
f Task 6: Verify the behavior of SharePoint Web application policies
Browse to http://intranet.contoso.com/sites/IT. Sign in to the site as CONTOSO\JimD with the

password Pa$$w0rd. Verify that you do not see the Add new item link in the Tasks list.

following steps:
Lab Instructions: Managing SharePoint Customizations
Module 7
Contents:
Lab A: Administering Features and Solutions
Exercise 1: Administering Features
Exercise 2: Administering Solutions
Lab B: Administering Sandboxed Solutions

Exercise 1: Administering Sandboxed Solutions
Exercise 2: Modifying Sandboxed Solutions Timer Jobs
Exercise 3: Configuring Sandbox Points
Lab C: Administering the Developer Dashboard

Exercise 1: Configuring the Developer Dashboard
11
Scenario
You have just installed a new SharePoint 2010 farm at Contoso, Ltd. Several developers would like to test
the functionality of features and solutions they created for SharePoint 2007. Corporate IT policy states
that only administrators may modify the production environments, so it is your job to install these
features and solutions.

The CEO has asked you to add a calendar to the intranet site. Although you have given her permissions to
create lists on the intranet, she mentions that there is no option to create a calendar. Additionally, you
have been asked to add a custom feature to the intranets Site Actions menu. In this exercise, you will
install, activate, deactivate, and uninstall SharePoint features.
1.
Activate a built-in feature.
2.
Install a custom feature.
3.
Activate and test a custom feature.
4.
Deactivate a feature.
f Task 1: Activate a built-in feature
Open Microsoft Internet Explorer, and then browse to http://intranet.contoso.com.
From the Site Actions menu, attempt to create a calendar list.
Observe that you cannot create a calendar, task, or contact list.
Activate the Team Collaboration Lists feature.
Re-attempt to create a calendar list.

Observe that you can now create a calendar, task, or contact list.
f Task 2: Install a custom feature
Open Windows Explorer and copy the folder, D:\LabFiles\Lab07\CustomAction, to the folder,
C:\Program Files\Common Files\Microsoft Shared\web server extensions
\14\Template\Features.
Each folder in the features folder represents a feature on the SharePoint server.
Close all open Windows Explorer windows.
Open the SharePoint 2010 management shell and use the installfeature operation of Stsadm.exe to
install the feature.
Tip: The installfeature operation is focused, by default, on the features folder. The path to the feature
can be entered as a path that is relative to the Features folder.
This will install a new feature into SharePoint that enables a simple custom action in the Site Actions
menu.
f Task 3: Activate and test a custom feature
On the intranet site, activate the feature JavaScript Dropdown Item.
Click the Site Actions menu, and then click the new item on the menu, A Custom Action.
A Message from webpage window appears with the message, Hello World.
Click OK.
f Task 4: Deactivate a feature
Deactivate the JavaScript Dropdown Item feature.
Confirm that the item, A Custom Action, no longer appears on the Site Actions menu.

Results: After completing this exercise, you should have installed, activated and deactivated
SharePoint features.

You want to track bugs and issues with the new SharePoint farm, and you have decided to use the
SharePoint bug database application template to do so. In this exercise, you will install and deploy the
solutions that enable the bug database application.
1.
Install a solution.
2.
Deploy a solution.
3.
Confirm the deployment of a solution.
f Task 1: Install a solution
Use the addsolution operation of Stsadm.exe to add the following two solutions to the farm:
D:\Labfiles\Lab07\ApplicationTemplateCore.wsp
D:\Labfiles\Lab07\BugDatabase.wsp
Open SharePoint 2010 Central Administration, and then from System Settings open the Manage
farm solutions page.
Observe that the two solutions are installed, but are not deployed.
f Task 2: Deploy a solution
Deploy the two solutions, applicationtemplatecore.wsp and bugdatabase.wsp.
f Task 3: Confirm the deployment of a solution
Create a new Web site named Bug Tracking, with the URL
http://intranet.contoso.com/sites/IT/Bugs and with the Bug Database site definition.
Open the new bug tracking Web site. Then close all open Internet Explorer windows.
Results: After completing this exercise, you should have installed and deployed SharePoint solutions
to your farm.
Scenario
Developers have started testing their solutions on your SharePoint farm, and some users have complained
that the new solutions seem to be causing performance problems. Your manager has tasked you with
examining the resource usage of the solutions and with changing the resource point settings of
sandboxed solutions for the time being to prevent database queries made by custom solutions from
causing problems.

In this exercise, you will upload and test a custom solution, and examine the resource usage of that
solution.
1.
Ensure that the code service is running.
2.
Upload a sandboxed solution.
3.
Test a sandboxed solution.
f Task 1: Ensure that the code service is running
In the Services console, confirm that the SharePoint 2010 User Code Host service is not started, and
that it is disabled.
In SharePoint 2010 Central Administration, start the Microsoft SharePoint Foundation Sandboxed
Code Service.
In the Services console, confirm that the SharePoint 2010 User Code Host service is started, and is
set to start automatically.
f Task 2: Upload a sandboxed solution
Browse to the IT intranet site, http://intranet.contoso.com/sites/IT. Upload the solution,

D:\Labfiles\Lab07\BadReceiver.wsp, and then activate the solution.
Activate the site feature, BadReceiver Feature1.
f Task 3: Test a sandboxed solution
From the All Site Content page, create a new announcement in the Announcements list, with the
title My Announcement.
An error message appears.
In the Webs Solutions Gallery, observe that the BadReceiver solution shows no resource usage. That
is because the timer job has not yet calculated resource usage for the solution.
Results: After completing this exercise, you should have deployed and tested the BadReceiver
solution.

In this exercise, you will launch the timer jobs that calculate resource usage.
1.
Run sandboxed solution timer jobs.
2.
Monitor resource usage.
f Task 1: Run sandboxed solution timer jobs
In SharePoint 2010 Central Administration, locate the timer job, Solution Resource Usage Update,
for SharePoint intranet.contoso.com80. Run the job now.
Note: Be sure to run the Solution Resource Usage Update and not the Solution Daily Resource
Usage Update timer job. Running the latter will cause resource usage points to be reset.
Run the timer job, Solution Resource Usage Log Processing, for the site SharePoint
intranet.contoso.com80.
f Task 2: Monitor resource usage
Browse to the Solutions Gallery for the IT Web, and then refresh the page.
The resource usage for the solution should now be updated. If you do not see the updated resource
usage, then you may need to wait for up to 5 minutes for the timer jobs to execute.
Results: After completing this exercise, you should have updated and executed one of the sandboxed
solutions timer jobs.

In this exercise, you will report the default resource point settings for sandboxed solutions, and then you
will modify the points assigned to database queries.
1.
Review default resource measures.
2.
Change default resource measure points.
3.
Test modified sandboxed resource measures.
4.
Deactivate the bad solution.
f Task 1: Review default resource measures
Run SharePoint 2010 Management Shell as Administrator.
To export a list of default point values, type the following command:

$spusercodeservice = [Microsoft.SharePoint.Administration.SPUserCodeService]::Local
$spusercodeservice.ResourceMeasures > c:\ResourceMeasures.txt
Open the file C:\ResourceMeasures.txt.

This file contains a listing of the resource measures that are monitored for sandboxed solutions.
Find the section for SharePointDatabaseQueryCount, and then record the current values of
ResourcesPerPoint and AbsoluteLimit. Close the file.
f Task 2: Change default resource measure points
In Administrator: SharePoint 2010 Management Shell, type the following commands:

$obj = $spusercodeservice.ResourceMeasures["SharePointDatabaseQueryCount"]
$obj.ResourcesPerPoint = 1
$obj.Update()
$obj | Select-Object Name,ResourcesPerPoint
This script sets the ResourcesPerPoint property for SharePointDatabaseQueryCount to 1 and will
cause SharePoint database queries to increase the resource usage point count very quickly.

iisreset
IIS restarts and enables the new resource settings.
Close Administrator: SharePoint 2010 Management Shell.
f Task 3: Test modified sandboxed resource measures
Switch to the instance of Internet Explorer that displays the IT intranet Web.
It will take a few seconds to load the Web, because you recently reset IIS.
From the All Site Content page, create a new announcement in the Announcements list, with the
title My Next Announcement.
10
In the Webs Solutions Gallery, observe that the BadReceiver solution shows no resource usage. That
is because the timer job has not yet calculated resource usage for the solution.
If you see resource usage of 2.00, then you were lucky! The timer jobs executed just in time. Skip to
Step 6.
Repeat Task 1 of Exercise 2 to run the sandboxed solutions timer jobs.
Refresh the view of the IT intranet Web Solutions Gallery.
Observe that the resource usage of the solution is increasing more rapidly.
If you do not see the updated resource usage, then you may need to wait for up to 5 minutes for the
timer jobs to execute.
f Task 4: Deactivate the bad solution
In the Solutions Gallery, deactivate the BadReceiver solution.

Results: After completing this exercise, you should have updated the default sandboxed solution
resource measures.
Leave the virtual machines running. You will use them for Lab C.
Question: What was the value of ResourcesPerPoint for SharePointDatabaseQueryCount? Explain the
relationship between this number and one resource usage point.
11
Scenario
You have installed a new SharePoint 2010 farm for your developers. Recently the development manager
fielded several performance issues from end users and has mandated that applications are designed with
performance as top priority. One of the developers has asked you to enable the Developer Dashboard for
debugging and instrumentation purposes to support this new initiative.

In this exercise, enable and disable the Developer Dashboard.
1.
Enable the Developer Dashboard.
2.
Review the Developer Dashboard.
3.
Disable the Developer Dashboard.
f Task 1: Enable the Developer Dashboard
In the SharePoint 2010 Management Shell, type the following commands:

$svc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService
$ddsetting=$svc.DeveloperDashboardSettings
$ddsetting.DisplayLevel=[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel
]::OnDemand
$ddsetting.Update()
This script enables the Developer Dashboard in OnDemand mode.
f Task 2: Review the Developer Dashboard
Click the small icon in the top right next to SharePoint Administrator.
12
This will enable the Developer Dashboard for the page.
Observe the information that is available on the page:
Http Handler Events for Http Request
Web Server stats
Asserts and Critical events
Database Queries
Service Calls
SPRequest Allocations
WebPart Events Offsets
f Task 3: Disable the Developer Dashboard
In the SharePoint 2010 Management Shell, type the following commands:

]::Off
$ddsetting.Update()
This script disables the Developer Dashboard.

Results: After completing the exercise, you should have enabled and disabled the Developer
Dashboard on the IT intranet Web.

following steps:
Lab Instructions: Configuring and Securing SharePoint Services and Service Applications
Module 8
Lab Instructions: Configuring and Securing SharePoint
Services and Service Applications
Contents:
Lab A: Administering SharePoint Services
Exercise 1: Administering SharePoint services
Exercise 2: Administering SharePoint Windows Services
Lab B: Configuring Application Security

Exercise 1: Configuring Web Application and Application Pool Security
Exercise 2: Configuring Secure Sockets Layer Security
8
10
Lab C: Configuring Service Applications

Exercise 1: Creating a Service Application
13
Scenario
The Communications team at Contoso wants to publish content to the intranet by using Microsoft Word.
The teams manager discovered that SharePoint includes a feature that can convert Word documents to
Web pages and is complaining that the intranet site does not expose the document conversion command.
Additionally, developers are experiencing errors that suggest some SharePoint services may not be
running correctly. You have been asked to troubleshoot the problems and to ensure that SharePoint and
Windows Services that are required to support the SharePoint farm are running correctly.

Scenario
In this exercise, you enable the document conversion service on the intranet Web, and you ensure that the
SharePoint Services requested by your developers are started.
1.
Create a document in a document library.
2.
Attempt to convert a document.
3.
Attempt to enable document conversion.
4.
Configure and start document conversion services.
5.
Enable document conversion.
6.
Test document conversion.
7.
Configure and start SharePoint Services.
f Task 1: Create a document in a document library
Open Windows Internet Explorer, and then browse to http://intranet.contoso.com.
Use the View All Site Content link to navigate to the Documents document library. From the library,
create a new document. In the new document, type this text: SharePoint IT Policies and
Procedures. If prompted for a user name, use Contoso\SP_Admin and the password Pa$$w0rd.
Save the document to the document library http://intranet.contoso.com/Documents with the

name SharePoint IT Policies and Procedures.
Close Microsoft Word, and then click Yes and OK to check in the document.
Switch to Internet Explorer, and then refresh the page to confirm that the document was saved in
the document library.
f Task 2: Attempt to convert a document
Point at the row containing the new document SharePoint IT Policies and Procedures, and then
click the drop-down arrow that appears next to the file name.
Observe that there are no options to convert the document.

You must enable document conversion for each Web application and several services must be
running.
Minimize, but do not close, Internet Explorer.
f Task 3: Attempt to enable document conversion
Open SharePoint 2010 Central Administration.
In the Quick Launch, click General Application Settings, and then, in the External Connections
section, click Configure document conversions.
The Configure Document Conversions page appears.
Click the Web Application list, and then click Change Web Application.
The Select Web Application dialog appears.
Click SharePoint - intranet.contoso.com80.
In the Enable Document Conversions section, click Yes, and then click OK.
At the top of the page, a message appears that indicates you must choose a document conversion
server.
Click the Load Balancer server drop-down arrow. Observe that you have no options. Click Cancel.
You must enable the SharePoint service on front-end Web servers before you can enable document
conversions.
f Task 4: Configure and start document conversion services
Under System Settings, click Manage services on server, and then browse to the Services On
Server page.
Start the Document Conversions Load Balancer Service and Document Conversions Launcher
Service. For the Document Conversion Launcher Service, select SP2010-WFE1 as the server and the
load balancer server.
f Task 5: Enable document conversion
From the General Application Settings page, browse to the Configure Document Conversions
page.
Enable document conversions for the Web application http://intranet.contoso.com using SP2010WFE1 as the load balancer server.
f Task 6: Test document conversion
Switch to the instance of Internet Explorer that displays the document library. Refresh the page.
Open the Edit menu for the document SharePoint IT Policies and Procedures. Observe the new
menu item, Convert Document. Convert the document to a Web page named SharePoint Policies
and Procedures with the URL name SharePointPoliciesAndProcedures.
f Task 7: Configure and start SharePoint Services
Switch to SharePoint 2010 Central Administration, click System Settings, and then browse to the
Services On Server page.
Start Claims to Windows Token Service and Microsoft SharePoint Foundation Subscription
Settings Service.
Start SharePoint Foundation Search using CONTOSO\SP_ServiceApps as the service account.

Configure the content access account as CONTOSO\SP_ServiceApps with the password Pa$$w0rd.
Close all instances of Internet Explorer.
Results: After this exercise, you should have enabled document conversions on the intranet Web and
configured and started several SharePoint farm services.

Scenario
The SharePoint Timer service is responsible for performing a number of important maintenance and
administration activities on the SharePoint farm. Some of the error messages experienced by developers
suggest that the Timer service is not running. In this exercise, you experience one of the symptoms of a
stopped Timer service, and then you start the service.
1.
Stop the Timer service.
2.
Attempt to create a service application.
3.
Start the Timer service.
4.
Observe the effects of the Timer service.
f Task 1: Stop the Timer service
Run Command Prompt as administrator, type the following command, and then close Administrator:
Command Prompt:
net stop sptimerv4
f Task 2: Attempt to create a service application
Open SharePoint 2010 Central Administration, and then browse to the Manage Service
Applications page.
Attempt to create a new Managed Metadata Service application with the following specifications:
Name: Managed Metadata Human Resources
Database name: HRMetadata
Application pool name: HRMetadataPool
Application pool identity: CONTOSO\SP_ServiceApps
When you attempt to create this application, Central Administration will pause indefinitely. Wait two
minutes, and then click Cancel.
Refresh the page, and then observe that the Managed Metadata Human Resources service
application is listed as Stopped, and that there is no Managed Metadata Service Connection created
for the service application.
The Timer service must be running to process the jobs related to the creation of a service application.
f Task 3: Start the Timer service
Open the Services console, and then start the SharePoint 2010 Timer service. Close the Services
console.
f Task 4: Observe the effects of the Timer service
Switch to SharePoint 2010 Central Administration, and then refresh the page. Observe the
Managed Metadata Human Resources service application. If the application is listed as Stopped or
if there is no Managed Metadata Service Connection for the application, wait a few moments, and
then repeat this step.
Results: After this exercise, you should have experienced an effect of a stopped SharePoint 2010
Timer service and started the service.
Scenario
You recently inherited a SharePoint farm that was not set up using best practices. Your manager is a
Certified Information Systems Security Professional (CISSP) and advocates security best practices. He
would like you to explore the service account permissions and SSL settings of the SharePoint server and
possibly change these settings to use specific service accounts. He would also like you to install SSL to
secure the metadata that is traveling between the clients and servers.

Scenario
In this exercise, you must use SharePoint security best practices and have an in-depth understanding of
various governance issues to configure and use SharePoint. What may seem like a simple setting could
present information security holes and expose sensitive data to unauthorized individuals.
1.
Review farm account settings.
2.
Add a managed account.
3.
Change the SharePoint farm account.
4.
Configure password change settings.
5.
Change a managed account password.
f Task 1: Review farm account settings
Open the Services console, and then observe the identity that is used by the SharePoint 2010 Timer
service.
Open Internet Information Services (IIS) Manager, and then observe the identity of the
SharePoint Central Administration v4 application pool.
f Task 2: Add a managed account
In Central Administration, click the Security link, and then navigate to the Managed Accounts page.
Register a managed account using the user name CONTOSO\SP_Admin and the password
Pa$$w0rd.
f Task 3: Change the SharePoint farm account
In Central Administration, click the Security link, and then navigate to the Service Accounts page.
Change the Farm Account to use the managed account CONTOSO\SP_Admin.
Open the Services console, and then confirm that the SharePoint 2010 Timer service is now using
the account SP_ Admin.
Switch to Internet Information Services (IIS) Manager, and then confirm that the SharePoint
Central Administration v4 application pool is now using the account, SP_Farm.
Repeat the first step to reset the farm account to SP_Farm.
f Task 4: Configure password change settings
Switch to SharePoint 2010 Central Administration, and then browse to the Password
Management Settings page.
In the Notification E-Mail Address box, type sharepoint@contoso.com.
f Task 5: Change a managed account password
In Central Administration, navigate to the Managed Accounts page.
Change the password of CONTOSO\SP_Farm to Pa$$w0rd1. Enable automatic password change

and notification by email.
Wait for the Security page to open.
Confirm that the Last password change column of the CONTOSO\SP_Farm row indicates that the
password was changed.
Results: After completing this exercise, you should have changed the farm account, reset its
password, and configured the password change policy.
10

Scenario
Contosos SharePoint governance policy requires that passwords and other security-sensitive information
must be encrypted when transmitted over the network. You have observed that Central Administration is
not using encryption, and you must bring Central Administration into compliance with the policy.
1.
Review the encryption of Central Administration.
2.
Install Active Directory Certificate Services.
3.
Create and install an SSL certificate.
4.
Configure SSL for Central Administration.
5.
Test SSL for Central Administration.
f Task 1: Review the encryption of Central Administration
In Central Administration, navigate to the Managed Accounts page.
In the CONTOSO\SP_Farm row, click the Edit icon. Observe the warning that appears at the top of
the page that reminds you that Central Administration is not using encryption.
f Task 2: Install Active Directory Certificate Services
Start Server Manager using the Run as different user option. Enter the user name
CONTOSO\Administrator and the password Pa$$w0rd.
Add the Active Directory Certificate Services role, including the role services Certification
Authority and Certification Authority Web Enrollment. Accept all other defaults as you configure
the role with the Add Role Wizard.
f Task 3: Create and install an SSL certificate
In Server Manager, expand Roles, expand Web Server (IIS), and then click Internet Information
Services (IIS) Manager.
In the Connections panel, select SP2010-WFE1, and in the IIS section, double-click Server
Certificates.
In the Actions panel, click Create Domain Certificate. Create a domain certificate with the following
specifications:
Common name: Contoso
Organization: Contoso
Organizational unit: SharePoint
City/locality: Redmond
State/province: WA
Country/region: US
Certificate authority: Contoso-SP2010-WFE1-CA
Friendly name: Contoso
f Task 4: Configure SSL for Central Administration
Create a binding for the SharePoint Central Administration v4 site with the following
specifications:
Type: https
Port: 10000
SSL certificate: Contoso
Close Server Manager.
f Task 5: Test SSL for Central Administration
Open Internet Explorer, and then browse to https://sp2010-wfe1:10000.

A message indicates the following: There is a problem with this websites security certificate.
This message appears because the certificate is issued by the server itself, and not from a trusted
certificate authority. In a production environment in which you had established your certificate
authority using a certificate from a trusted certificate root, this message would not appear.
Click Continue to this website (not recommended).

The Central Administration site will open in secure mode.
Click the Security link, and then browse to the Managed Accounts page.
In the CONTOSO\SP_Farm row, click the Edit icon.
Observe that the warning message you observed in Task 1 no longer appears.
Close all open applications and windows.

Results: After this exercise, you should have configured Central Administration to use SSL.
f Do not turn off the virtual machines
Leave the virtual machines running. You use them in Lab C.
11
12
Scenario
Your company Contoso has adopted SharePoint 2010 for many reasons. One is its new, more optimized
service application environment and another is its ability to manage metadata. You want to allow sites in
the client-facing Web application to use managed metadata and keywords, but you do not want
managed metadata and keyword columns in the client Web application to have visibility into terms used
internally. Therefore, you must configure a separate Managed Metadata Service for the client Web
application.

Scenario
In this exercise, you configure Business Connectivity Services to address the business intelligence
requirements of Contoso, Ltd.
1.
Create a service application.
2.
Configure the default application proxy group.
3.
Configure a custom application proxy group.
4.
Publish a service application.
f Task 1: Create a service application
Open SharePoint 2010 Central Administration, click Application Management, and then browse
to the Manage Service Applications page.
Create a new Managed Metadata Service application with the following specifications:
Service application name: Managed Metadata Clients
Database name: Managed_Metadata_Clients
Application pool name: SharePoint Web Services Default
Add this service application to the farms default list: Clear this option
f Task 2: Configure the default application proxy group
Click the Application Management link, browse to the Service Application Associations page.
Edit the default application proxy group. Verify that the Managed Metadata Clients application
connection is removed from the proxy group.
f Task 3: Configure a custom application proxy group
Browse to the Service Application Associations page.
Create a custom application proxy group for the SharePoint intranet.contoso.com80 Web
application with the following service applications:
Managed Metadata Clients
Search Service Application
Usage and Health data collection
Web Analytics Service Application
Observe that there is an application proxy group labeled custom assigned to the intranet Web
application.
f Task 4: Publish a service application
Click the Application Management link, and then browse to the Manage Service Applications
page.
Publish the Managed Metadata Clients service application. Select the Publish the Service
Application to other farms option.
Because this lab contains only one farm, you cannot configure a trust relationship.
13
14
Results: After this exercise, you should have configured a new managed metadata service
application, modified the default proxy group, and created a custom application proxy group.

following steps:
Lab Instructions: User Profiles and Social Networking
Module 9
Contents:
Lab: A: Configuring User Profiles
Exercise 1: Creating a User Profile Service Application
Exercise 2: Configuring User Profiles
Exercise 3: Configuring Profile Import from External Data Sources
Lab: B: Administering My Sites

Exercise 1: Configuring My Sites
10
Exercise 2: Creating Your My Site and Profile
12
Exercise 3: Configuring Social Networking Features
14
Lab A: Configuring User Profiles
Scenario
Your corporation has never had an employee directory despite the multiple requests of the Human
Resources department. Since implementing SharePoint 2010, the Human Resources department has again
requested the directory be implemented using SharePoint user profiles. Previous IT policies prevented
making changes to Active Directory and forced the creation of a separate Human Resources database of
user information. You have been tasked to set up user profiles in the new farm using Active Directory as
the primary data source and integration with profile properties that come from the secondary HR data
source.

1.
2.

1.
Start the Web Service Application Pool.
2.
Create a user profile service application.
3.
Start required SharePoint services.
4.
Verify successful service startup.
5.
Reset IIS.
6.
Validate the service application.
f Task 1: Start the Web Service Application Pool
Log on to SP2010-WFE1 as CONTOSO\SP_Admin with password, Pa$$w0rd.
In IIS Manager, ensure that the SharePoint Web Services Root application pool is started. Then
close IIS Manager.
This step is necessary because memory limitations in the lab environment may prevent the
application pool from starting automatically. This problem would manifest itself as a WCF error later
in this lab.
f Task 2: Create a user profile service application
In Central Administration, click the Application Management link and then navigate to the Manage
Service Applications page.
Create a new User Profile Service Application with the following configuration:
Name: User Profile Service Application
Application pool name: UserProfilePool
Application pool account: CONTOSO\SP_Farm
f Task 3: Start required SharePoint services
In Central Administration, click System Settings and then navigate to the Services on Server page.
Start the user profile service. Then start the user profile synchronization service. When prompted
to select the user profile application, select user profile service application, and enter the password,
Pa$$w0rd.
Observe the Status of the user profile synchronization service.

A timer job is created that will configure user profile settings in the farm. When it has completed the
status of the service will change from Starting to Started.
Click Monitoring and then navigate to the Timer Job Status page. Click Running Jobs and then
monitor the page. Press F5 to refresh the page. Repeat this step until the
ProfileSynchronizationSetupJob appears.
Note: It can take up to 5 minutes for the ProfileSynchronizationSetupJob to appear on the Running
Jobs list. If you dont see the job start, re-start the timer service, but be sure you DO NOT restart it if
this job is running.
Monitor the page. Press F5 to refresh the page. Repeat this step until the
ProfileSynchronizationSetupJob disappears.
Note: It can take up to 15 minutes for the ProfileSynchronizationSetupJob to complete.
Navigate to the Job History page. Confirm that the Status of ProfileSynchronizationSetupJob is
Succeeded.
Click the System Settings link and then navigate to the Services on Server page. Confirm that the
Status of the user profile synchronization service is Started. Close SharePoint 2010 Central
Administration.
f Task 4: Verify successful service startup
Open the Services console. Confirm that the following services are started:
Forefront Identity Manager Service
Forefront Identity Manager Synchronization Service
If a service is not started, then press F5 to refresh the view. Repeat this step until the services have
started.
Note: This can take several minutes.
Close the Services console.
Open the folder C:\Program Files\Microsoft Office Servers\14.0

\Synchronization Service\MaData. Confirm that the ILMMA folder exists. Confirm that a folder
named MOSS-GUID exists with todays date.
If they do not exist, wait until the timer job has completed fully, at which point the folders will appear.
Close the Windows Explorer window that is showing the MaData folder.
f Task 5: Reset IIS
Start Command Prompt using the Run as administrator option. Type iisreset, and then press
ENTER. After the command has completed, close Command Prompt.
f Task 6: Validate the service application
In Central Administration, click Application Management and then navigate to the Manage Service
Applications page. Open the Manage Profile Service page for user profile service application.
If an error is displayed, it is probably because the Web services have not completed startup following
the IISRESET operation. Press F5 to refresh the page until the error disappears.
Confirm that there are numbers on the right side of the page, which indicates that the service
application is running. Then close Central Administration.
Results: After completing this exercise, you should have created a new User Profile Service
Application and started all services related to user profile synchronization.

1.
Delegate Active Directory permissions to enable user profiles synchronization.
2.
Create a user profile connection to Active Directory.
3.
Add a custom user property.
4.
Import user profiles from Active Directory.
5.
Validate the profile import.
6.
Configure a profile property in Active Directory.
7.
Run an incremental profile synchronization.
8.
Validate the profile import.
f Task 1: Delegate Active Directory permissions to enable user profiles synchronization
Start Active Directory Users and Computers using the Run as a different user option. Enter the
user name, CONTOSO\Administrator, and the password, Pa$$w0rd.
Use the Delegation of Control Wizard to delegate the user account, CONTOSO\SP_Farm, permission
for Replicating Directory Changes for the contoso.com domain. Then close Active Directory Users
and Computers.
f Task 2: Create a user profile connection to Active Directory
In Central Administration, click Application Management, click Manage service applications, and
then open the Manage Profile Service page for user profile service application. Create a new
synchronization connection with the following configuration:
Connection name: Contoso Active Directory
Forest name: contoso.com
Account name: CONTOSO\SP_Farm
Password: Pa$$w0rd
Containers to synchronize: the People, SharePoint, and Users organizational units (OUs)
f Task 3: Add a custom user property
In Central Administration, open the Manage Profile Service page for user profile service
application. Add a new user property with the following configuration:
Name: City
Display name: City
Default privacy setting: Everyone
Replicable: Yes
Display the property in the profile properties section of the users profile page, on the Edit Details
page, and in the newsfeed
Property imported from the Contoso Active Directory connection, l attribute
Tip: l (lowercase L) is the Lightweight Directory Access Protocol (LDAP) name for the locale, or city
attribute.
f Task 4: Import user profiles from Active Directory
application. Start a full synchronization of user profiles.
Monitor the progress of synchronization. The synchronization job will take a few moments to start,
and then will take 10-15 minutes to complete. When the job is complete, confirm that the Number
of user profiles is 53, and confirm that Profile Synchronization Status displays Idle.
f Task 5: Validate the profile import
Find the profile for SP_Admin. Confirm that the City attribute has no value.
f Task 6: Configure a profile property in Active Directory
Start Active Directory Users and Computers using the Run as different user option. Enter the user
name, CONTOSO\Administrator, and the password, Pa$$w0rd.
Open the properties of the SharePoint Administrator account, in the SharePoint OU. Change the
City property to Seattle.
f Task 7: Run an incremental profile synchronization
application. Start an incremental synchronization of user profiles.
and then will take a few minutes to complete. When the job is complete, the Profile
Synchronization Status displays Idle.
Find the profile for SP_Admin. Confirm that the City attribute is Seattle.
Results: After completing this exercise, you should have configured and performed user profile
synchronization.

1.
Create a new profile property.
2.
Set up data source permissions.
3.
Create an external data source.
4.
Set permissions on an external data source.
5.
Create a synchronization connection to an external data source.
6.
Add a profile property from an external data source.
7.
Edit a user profile.
8.
Import profile data from the external data source.
9.
Validate the user profile import.
f Task 1: Create a new profile property
In Central Administration, click Application Management, click Manage service applications, and
then open the Manage Profile Service page for user profile service application.
Add a new user property with the following configuration. Type the text exactly as shownbe careful
about the inclusion and exclusion of spaces.
Name: EmployeeID
Display name: Employee ID
Type: integer
Replicable: Yes
Allow users to edit values for this property: Yes
Display the property in the profile properties section of the users profile page, and on the Edit
Details page.
f Task 2: Set up data source permissions
Start the Microsoft SQL Server 2008 R2 SQL Server Management Studio using the Run as different
user option. Enter the user name, CONTOSO\Administrator, and the password, Pa$$w0rd.
Click Connect.
Add a login for the AdventureWorks database for CONTOSO\SP_Admin. Assign the login the
db_owner database role. Repeat the step for CONTOSO\SP_Farm.
Close SQL Server Management Studio.
f Task 3: Create an external data source
Start Microsoft SharePoint Designer 2010, and then open the site,
http://intranet.contoso.com/sites/IT. Wait for the site to open. When prompted for credentials, use
Contoso\SP_Admin with the password of Pa$$w0rd.
Create a new external content type named AdventureWorks. Connect to the SQL Server, SP2010WFE1, and to the database, AdventureWorks. Select the Employee table and Create All
Operations. Save the external content type, and then close SharePoint Designer.
f Task 4: Set permissions on an external data source
In Central Administration, navigate to the Manage Service Applications page, and then click
Business Data Connectivity Service.
Set permissions on the AdventureWorks content type so that All Authenticated Users have all
available permissions.
f Task 5: Create a synchronization connection to an external data source
In Central Administration, open the Manage Profile Service page for User Profile Service
Application.
Create a new synchronization connection with the following configuration:
Connection name: Adventure Works
Type: Business Data Connectivity
Business data connectivity entity: AdventureWorks
Connect as a 1-to-1 mapping with the EmployeeID profile property
f Task 6: Add a profile property from an external data source
Application.
Create a new user profile property with the following configuration:
Name: Gender
Display name: Gender
Policy setting: Optional
Replicable: Yes
Display the property in the profile properties section of the users profile page, and on the Edit
Details page
Source data connection: AdventureWorks
Attribute: Gender
f Task 7: Edit a user profile
Find the profile for CONTOSO\SP_Admin. Change Employee ID to 1, and confirm that Gender is
blank.
f Task 8: Import profile data from the external data source
Application. Start a full synchronization of user profiles.
and then will take 10-15 minutes to complete. When the job is complete, confirm that the Number
of user profiles is 34, and confirm that Profile Synchronization Status displays Idle.
f Task 9: Validate the user profile import
Find the profile for SP_Admin. Confirm that the Gender attribute is M.
Question: What group does the farm account have to be in in order for user profile synchronization to
work?
Results: After completing this exercise, you should have configured and performed profile attribute
synchronization from an external source.
10
Lab B: Administering My Sites

1.
Create My Site Web application.
2.
Create a search center.
3.
Configure permissions for the search center.
4.
Configure a managed path for MySites.
5.
Enable self-service site creation.
6.
Configure My Sites.
7.
Configure permissions for the intranet
f Task 1: Create My Site Web application
In Central Administration, create a new Web application with the following configuration:
Port: 80
Host header: mysites.contoso.com
Application pool identity: CONTOSO\SP_Farm
Database name: WSS_Content_MySites
Create a new site collection in the Web application with the following configuration:
Title: My Site Host
Template: My Site Host
f Task 2: Create a search center
Create a new site collection in the My Site Host Web application with the following configuration:
Title: Search Center
URL: http://mysites.contoso.com/sites/Search
Template: Enterprise Search Center
f Task 3: Configure permissions for the search center
Open a new tab in Windows Internet Explorer, and then browse to

http://mysites.contoso.com/sites/Search. Add the Domain Users group to the Search Center
Visitors group.
f Task 4: Configure a managed path for MySites
In Central Administration, navigate to the Web Applications Management page.
Add a wildcard inclusion managed path named personal to the SharePoint mysites.contoso.com80 Web application.
f Task 5: Enable self-service site creation
Enable self-service site creation for the SharePoint - mysites.contoso.com80 Web application.
f Task 6: Configure my sites
Application. Set up My Sites using the following configuration:
Preferred search center: http://mysites.contoso.com/sites/Search/Pages
My Site Host location: http://mysites.contoso.com
Location: personal
f Task 7: Configure permissions for the intranet
Open a new tab in Internet Explorer, and then browse to http://intranet.contoso.com. Add the
Domain Users group to the Contoso Intranet Visitors group.
Log off SP2010-WFE1.

Results: After completing this exercise, you should have configured My Sites.
11
12

1.
Create your My Site.
2.
Update your status.
3.
Edit your profile.
f Task 1: Create your My Site
Log on to SP2010-WFE1 as CONTOSO\DanJ with password, Pa$$w0rd.
Open Internet Explorer, and then browse to http://intranet.contoso.com. Click the logon menu,
Dan Jump, and then click My Profile.
Note: If My Profile is not visible, click My Settings, and then click My Profile.
Click My Content. A My Site is created. The Processing screen may display for 1 to 2 minutes.
Click My Profile. Review the tabs on the My Site.
f Task 2: Update your status
Update your status to Loving SharePoint!
f Task 3: Edit your profile
Edit your profile using the values in the following table.

Profile Property
Value
About me
I enjoy helping my team succeed
Mobile phone
206-555-1234
Home phone
725-555-1234
Office Location
New Tower
Time Zone
(UTC-8:00) Pacific Time (US and Canada)
Past projects
SharePoint 2007
Skills
Public Speaking
Schools
University of SharePoint
Birthday
January 1
Employee ID
Configure your birthday to display to My Colleagues. Save your changes.
On the profile page, click More information. Observe that the newly populated profile properties are
now visible.
Results: After completing this exercise, you should have created a My Site for Dan Jump, and
modified his user profile.
13
14

1.
Add colleagues.
2.
Track colleagues.
3.
Configure membership.
4.
Start profile synchronization jobs.
5.
Explore In Common with You.
6.
Wait for search and synchronization jobs to complete.
7.
View previous updates
f Task 1: Add colleagues
Click the Colleagues tab and then add Contoso\LolaJ as a colleague. Do not add any additional
suggested colleagues.
f Task 2: Track colleagues
Click the Jump, Dan link and then sign in as a different user. Sign in as Contoso\LolaJ with the
password of Pa$$w0rd.
Click My Profile and then edit the profile as follows:
About Me: On the Contoso team for 15 years
Employee ID: 3
Whats happening?: Working on our marketing strategy
f Task 3: Configure membership
In the address bar, type http://intranet.contoso.com/Sites/IT. The Error: Access Denied page
opens.
Sign in as Contoso\SP_Admin with the password of Pa$$w0rd.
Click Site Actions, and then click Site Permissions. Grant Contoso\Danj permissions to the site by
adding him to the Information Technology Members [Contribute] group.
Open the Information Technology Members page, and then make this group the default group for
the site.
f Task 4: Start profile synchronization jobs
Open SharePoint 2010 Central Administration. When prompted for credentials, provide
Contoso\SP_Admin with the password of Pa$$w0rd.
In Central Administration, click the Monitoring link and then under Timer Jobs, click Review job
definitions. Enable and run the following jobs:
User Profile Service Application Activity Feed Job
User Profile Service Application User Profile to SharePoint Full Synchronization
User Profile Service Application User Profile to SharePoint Quick Synchronization
f Task 5: Explore In Common with You
Open Internet Explorer and browse to http://intranet.contoso.com/Sites/IT.
Browse to Dan Jumps My Profile page.
Under My Organization Chart, review Toni Poes profile information.
Click Organization Browser and view Dan Jumps organization structure and profile.
f Task 6: View previous updates
Switch to Dan Jumps My Site page.
Click the following links and view the changes:
My Newsfeed
My Profile
Memberships
Information Technology
Results: After this exercise, you should have configured various social networking features.

following steps:
1.
2.
3.
15
Lab Instructions: Administering and Configuring SharePoint Search
Module 10
Lab Instructions: Administering and Configuring SharePoint
Search
Contents:
Lab A: Configuring Search
Exercise 1: Creating Content for Search
Exercise 2: Creating an Enterprise Search Center Site
Exercise 3: Creating and Configuring a Content Source
Exercise 4: Configuring File Types
Exercise 5: Configuring Search Settings
Exercise 6: Configuring Managed Properties
10
Exercise 7: Creating and Configuring a Search Scope
12
Lab B: Tuning SharePoint Search

Exercise 1: Creating Keywords and Best Bets
14
Exercise 2: Configuring a Thesaurus
16
Exercise 3: Configuring Noise Words
18
Lab Instructions: Administering and Configurring SharePoint Searcch
Lab A: Config
guring Search
Sccenario
Yo
ou have installled a new SharePoint 2010 farm
f
to addresss the needs off employees att Contoso, Ltd., to
se
earch for information across both intranet sites and sharred folders. You have been asked
a
to prototype a
Sh
harePoint searrch capability on
o the Informa
ation Technolo
ogy Department Web site an
nd, based on your
y
exxperience with
h the prototype
e, to configure
e SharePoint to
o support searrch requiremen
nts.
f Log on to
o the virtual machine fo
or this lab
Start 10174A-CONT
TOSO-DC-E.
After CONTOSO-DC
has completed startup, startt 10174A-SP20
C
010-WFE1-E.

In this exercise, you identify and add content to SharePoint and to shared folders on servers that run the
Windows operating system. This content will serve to test the out of box search functionality of
SharePoint.
1.
2.
3.
Explore SharePoint content.

Create a shared folder.
Add files to the shared folder.
f Task 1: Explore SharePoint content

On the home page, click the Shared Documents document library, which includes the documents IT
Policies and Procedures for SharePoint 2010 and SharePoint Governance Plan.
Click the All Site Content link, and then open the Announcements list. Observe the two
announcements, WSS stands for Windows SharePoint Services, and Mud is dirty.
Return to the Information Technology home page.
f Task 2: Create a shared folder

Create a folder named Data on the C drive.
Share the folder with the share name Data. Grant the Everyone group the Full Control share
permission.
Inside the Data folder, create a folder named Temporary Drafts.
Close any open Windows Explorer windows.
f Task 3: Add files to the shared folder

Open Notepad and create a file named C:\Data\SharePoint Search.txt with the following text:
SharePoint is able to index files in a shared folder.
Create a file named C:\Data\Temporary Drafts\Crawl Rules.txt with the following text:
SharePoint crawl rules allow you to manage the content that is included and excluded.
Copy D:\LabFiles\Lab10\SharePoint Governance Checklist.pdf to C:\Data.

Results: After this exercise, you should have created text files in a shared folder.

In this exercise, you build the prototype SharePoint Enterprise Search site in the Information Technology
Department site collection. Then, you test the SharePoint out of box search functionality.
1.
2.
3.
4.
Attempt to create a search center.

Enable SharePoint Search features.
Create a Search Center.
Test the Search Center.
f Task 1: Attempt to create a Search Center
In the Information Technology Department Web, attempt to create a new site with the following
settings:
Site definition: Enterprise Search Center
URL: Search
The SharePoint Server Publishing Infrastructure feature must be active to create a Web using the
Enterprise Search Center site definition. You can create a Web using the Basic Search Center site
definition without activating the SharePoint Server Publishing Infrastructure feature.
The SharePoint Server Standard Site Collection Features feature must also be active before you can
create a Web with either site definition.
Close the error message.
f Task 2: Enable SharePoint Search features
Enable the SharePoint Server Publishing Infrastructure feature for the Information Technology site
collection.
f Task 3: Create a Search Center
In the Information Technology Web, create a new site with the following settings:
Site definition: Enterprise Search Center
URL: Search
f Task 4: Test the Search Center
In the Search Center, perform a search for the keyword procedures.

The file IT Policies and Procedures is returned in the list of results.
In the Search Center, perform a search for the keyword index.

No results are returned.
In the Search Center, perform a search for the keyword excluded.

Results: After this exercise, you should have created a Search Center and tested the default behavior
of SharePoint Search.

In the previous exercise, you built a prototype Search Center and confirmed that, by default, SharePoint
indexes content on SharePoint sites but does not index content in shared folders. In this exercise, you add
the shared folder Data as a content source so that SharePoint can crawl and index the folder. You also
exclude files that are considered temporary drafts.
1.
2.
3.
4.
5.
6.
Create a content source.

Test the content source.
Create a crawl schedule.
Create a crawl rule.
Crawl a content source.
Test the crawl rule.
f Task 1: Create a content source
In SharePoint 2010 Central Administration, open the Search Service Application and create a
content source with the following settings:
Name: Shared Folder - Data
Content source type: File Shares
Start address: \\sp2010-wfe1.contoso.com\Data
Start full crawl of this content source: Selected
Monitor the crawl status of the Shared Folder - Data content source until the full crawl is complete.
Tip: The full crawl takes two to four minutes.
f Task 2: Test the content source

The file SharePoint Search.txt is returned as a result.
Perform a search for the keyword excluded.

The file Crawl Rules.txt is returned as a result.
f Task 3: Create a crawl schedule
In SharePoint 2010 Central Administration, edit the Shared Folder - Data content source. Create a
schedule for full crawls that runs every hour.
f Task 4: Create a crawl rule
Create a crawl rule that excludes the path \\sp2010-wfe1.contoso.com\Data

\Temporary Drafts\*.
f Task 5: Crawl a content source
Start a full crawl of the content source Shared Folder - Data. Monitor the crawl status until the crawl
is complete.
f Task 6: Test the crawl rule

Perform a search for the keyword excluded.

Results: After this exercise, you should have created a content source for the shared folder Data, a
crawl schedule, and a crawl rule that excludes files from the Temporary Drafts folder.

One of the requirements for Search at Contoso is that commonly used file types can be searched.
However, a user of the IT Search Center reports that she cannot search for a PDF document that she
knows is in the shared folder. In this exercise, you add a file type for PDFs so that SharePoint can index
PDFs.
1.
2.
3.
4.
Search for an existing PDF file.

Add a file type for PDFs.
Test the file type.
f Task 1: Search for an existing PDF file
In the Search Center, perform a search for the keyword governance.

You should not see the file sharepoint governance checklist.pdf in the results even though it is in the
shared folder Data.
f Task 2: Add a file type for PDFs
In SharePoint 2010 Central Administration, add a file type for files with the extension pdf.
is complete.
Task 4: Test the file type

The file sharepoint governance checklist.pdf is returned as a result.
Observe its URL.

Perform a search for the keyword Deployment.
Note: Deployment is a term in the PDF file. You must install a 64-bit iFilter for PDFs on all servers that
perform indexing to index the contents of PDF documents successfully.
Results: After this exercise, you should have created a file type for PDFs.

In this exercise, you configure search settings to address search requirements at Contoso, which include
use of a dedicated account to crawl content and minimization of the impact of crawling.
1.
2.
3.
4.
5.
6.
7.
Explore query crawl logs.

Configure the default content access account.
Add a server name mapping.
Test server name mappings.
Explore host distribution rules.
Configure crawler impact rules.
f Task 1: Explore query crawl logs
In SharePoint 2010 Central Administration, open the crawl log of the Shared Folder - Data content
source. Examine the crawl history of the content source. Examine the list of URLs that have been
indexed in the content source.
Locate the URL for the file SharePoint Governance checklist.pdf. If the file does not appear on the
list of indexed URLs, wait a few moments, and then click the Search button.
f Task 2: Configure the default content access account
Configure the default content access account as CONTOSO\SP_Crawl with the password Pa$$w0rd.
f Task 3: Add a server name mapping
Create a server name mapping that presents content indexed in the content source \\sp2010wfe1.contoso.com with the URL \\localhost.
is complete.
f Task 5: Test server name mappings

Observe that the URL is displayed as localhost instead of

sp2010-wfe1.contoso.com.
f Task 6: Explore host distribution rules
In SharePoint 2010 Central Administration, browse to the Host Distribution Rules page.
SharePoint notifies you that host distribution rules cannot be applied to a farm with only one crawl
database.
f Task 7: Configure crawler impact rules
In SharePoint 2010 Central Administration, create a crawler impact rule for the site SP2010-WFE1
that requests one document at a time and waits 30 minutes between requests.
Results: After this exercise, you should have configured a variety of search settings.
10

Contoso wants users to be able to search for documents based on a custom document description
attribute. In this exercise, you address this requirement by configuring a managed property.
1.
2.
3.
4.
5.
6.
Add a column to a document library.

Configure a managed property.
Modify a Search Center to support the managed property.
Test the managed property and modified Search Center.
f Task 1: Add a column to a document library
Switch to Internet Explorer and browse to http://intranet.contoso.com/sites/IT.

Click the Shared Documents link, and then in the Shared Documents document library, add a column
named Summary.
Edit the properties of the document IT Policies and Procedures for SharePoint 2010 so that its
Summary property is Contoso IT Policies and Procedures for SharePoint 2010.
Start a full crawl of the content source Local SharePoint sites. Monitor the crawl status until the
crawl is complete.
Tip: The full crawl takes four to six minutes.
f Task 3: Configure a managed property
In SharePoint 2010 Central Administration, add a new managed property named ContosoSummary
mapped to the crawled property ows_Summary(Text). Select the Allow this property to be used in
scopes option.
Tip: When adding the mapping to the crawled property ows_Summary(Text), select SharePoint
from the category list.
Start a full crawl of the content source Local SharePoint sites.

Note: Continue to the next task while the crawl proceeds.
f Task 5: Modify a Search Center to support the managed property
Browse to the Search Center http://intranet.contoso.com/sites/IT/Search, and then click

Advanced,
Edit the Advanced Search Box Web Part. In the properties panel, click the builder button next to the
Properties box.
11
Add the following element inside the <PropertyDefs> element:

<PropertyDef Name="ContosoSummary" DataType="text" DisplayName="Summary"/>
Add the following element as the last element in the
<ResultType DisplayName="All Results" Name="Default"> element:
<PropertyRef Name="ContosoSummary"/>
After making your changes, click Save & Close.
f Task 6: Test the managed property and modified Search Center
In SharePoint 2010 Central Administration, monitor the crawl status of the Local SharePoint sites
content source until the crawl status is Idle.
In the Search Center, click Advanced to open the Advanced Search page. Perform a search with the
property Summary containing the text Contoso.
The file IT Policies and Procedures for SharePoint 2010 is listed as the result.
Results: After this exercise, you should have created a new managed property and customized the
advanced Search Center to expose a capability to search with the new property.
12

Some teams at Contoso have not moved their files from shared folders to SharePoint document libraries.
These teams need to search for their documents in shared folders only so that results from SharePoint
sites are filtered out. In this exercise, you create and configure a search scope that narrows a search query
to a specific content source.
1.
2.
3.
4.
Create a search scope.

Configure a search scope rule.
Add the custom search scope to a site.
Test the custom search scope.
f Task 1: Create a search scope
In SharePoint 2010 Central Administration, click the Scopes link, and then create a search scope
named Shared Files.
f Task 2: Configure a search scope rule
Add a scope rule for the Shared Files scope that defines the scope as content from the Shared
Folder Data content source.
On the Search Administration page, launch a scope update.
On the scopes list, monitor the Update Status of the Shared Files scope until the scope is Ready.
f Task 3: Add the custom search scope to a site
Modify the search settings for the Information Technology Department site collection to enable
custom scopes by connecting the site to the Search Center at
http://intranet.contoso.com/sites/IT/Search/Pages. Configure the site collection to show the
Scopes drop-down.
Configure the site collection search scopes to include the Shared Files scope in the Search
Dropdown display group.
f Task 4: Test the custom search scope
Browse to the Information Technology home page.

Use the search box to search for the keyword sharepoint.
Many results are listed, including both documents in the shared folder and items from SharePoint
sites.
Return to the Information Technology Department Web home page and perform the search
again, limiting the scope to Shared Files.
The files sharepoint search.txt and sharepoint governance checklist.pdf are listed as the only results.
Results: After this exercise, you should have created a new search scope and added the scope to the
Information Technology Department Web.

You will use the same virtual machines in the next lab.
Lab Insstructions: Administeering and Configuringg SharePoint Search
13
Lab B:
B Tuning Share
ePoint Search
Sccenario
During the testiing of the prottotype Search Center on the
e Information Technology
T
De
epartment We
eb
Se
earch Center, users
u
complain
ned that the re
elevance of ressults was not accounting
a
forr the fact that the
t
m
most
importantt files are, at th
his point, the fiiles stored in shared
s
folders. Users also pointed out thatt
se
earches with sp
pecific keyworrds should yield
d predefined results
r
that are
e likely to be most
m
useful, an
nd that
ce
ertain keyword
ds should be trreated as syno
onyms. Finally, the governancce committee added a requirement
th
hat you preven
nt searches using keywords that
t
are frowned on by Conttosos employe
ee ethics policies. You
arre tasked with refining Share
ePoint Search to
t meet these expectations.
14

In this exercise, you modify query behavior so that, for specific query keywords, suggested results appear
at the top of the results list.
1.
2.
3.
4.
Create a Best Bet.

Test Best Bets.
Customize the presentation of Best Bets.
Test the customized presentation of Best Bets.
f Task 1: Create a Best Bet
Add a search keyword to the Information Technology Department site collection with the following
settings:
Keyword Phrase: SharePoint
Best Bet URL: http://sharepoint.microsoft.com
Best Bet Title: Microsoft SharePoint Server Home Page
Keyword Definition: Microsoft SharePoint Server is the business collaboration platform for
the enterprise and the Internet
f Task 2: Test Best Bets
Browse to the Information Technology home page.

Use the search box on the home page to search for the keyword sharepoint.
Confirm that the Best Bet that you configured in Task 1 precedes the query-based search results.
f Task 3: Customize the presentation of Best Bets
On the search results page, edit the Search Best Bets Web Part, and in its properties panel, click XSL
Editor.
The Search Best Bets Web Part properties panel is displayed on the right.
Tip: You might need to scroll to the right, and to the top, to see the properties panel.
Replace the All_Results/BestBetResults/Result element with the following:

<xsl:template match="All_Results/BestBetResults/Result">
<xsl:if test="$DisplayBB = 'True'" >
<xsl:if test="position() <= $BBLimit" >
<xsl:variable name="url" select="url"/>
<xsl:variable name="id" select="id" />
These are the results that the Contoso Search Team recommends, based on your
query. 
<xsl:if test="$DisplayTitle = 'True'" >

<img src="/_layouts/images/star.gif" alt="" />


<a href="{$url}" id="{concat('BBR_',$id)}">
<xsl:value-of select="title"/>
</a>
 

</xsl:if>
<xsl:if test="$DisplayDescription = 'True' and description[. != '']" >
<div class="srch-BB-Description">
<xsl:value-of select="description"/>
 
</div>
</xsl:if>
<xsl:if test="$DisplayUrl = 'True'" >

<a href="{$url}" id="{concat('BBR_U_',$id)}" dir="ltr">
<xsl:value-of select="$url"/>
</a>

 
 
</xsl:if>
</xsl:if>
</xsl:if>
</xsl:template>
After making your changes to the Web Part, click Save & Close.
f Task 4: Test the customized presentation of Best Bets
Perform a search for the keyword sharepoint.

The new text appears in the Best Bet Web Part: These are the results that the Contoso Search Team
recommends, based on your query.
Results: After this exercise, you should have created keyword Best Bets and customized the
presentation of Best Bets.
15
16

In this exercise, you configure the SharePoint thesaurus file to improve the efficiency of Search by refining
the search thesaurus. Keywords are automatically replaced with more accurate synonyms, and keywords
are expanded with similar words and phrases.
1.
2.
3.
4.
Perform searches with the default thesaurus.

Edit a thesaurus file.
Restart the Search service.
Test Search with the modified thesaurus.
f Task 1: Perform searches with the default thesaurus
In the Search Center, perform searches with the following keywords. Write down the exact number of
results that are returned:
SharePoint
MOSS
WSS
SharePoint Foundation
Tip: If the number of results is reported as an approximate number, page through the results so that
you can identify the exact number of results that were returned.
f Task 2: Edit a thesaurus file
Open the file C:\Program Files\Microsoft Office Servers\14.0\Data

\Office Server\Applications\GUID-query-0\Config\tsenu.xml in Notepad. Replace the contents
with the following text, and then save your changes and close Notepad:
<XML ID="Microsoft Search Thesaurus">
<thesaurus xmlns="x-schema:tsSchema.xml">
<diacritics_sensitive>0</diacritics_sensitive>
<replacement>
<pat>MOSS</pat>
SharePoint
</replacement>
<expansion>
WSS
SharePoint Foundation
</expansion>
</thesaurus>
</XML>
f Task 3: Restart the Search service
Run Command Prompt as administrator. Type the following commands:

net stop osearch14
net start osearch14
f Task 4: Test Search with the modified thesaurus
In the Search Center, perform a search for the keyword sharepoint. Record the number of results.
Perform a search for the keyword MOSS. Verify that the number of results is equal to the number of
results returned when you searched for sharepoint.
Search results appear because searching for MOSS now produces search results for SharePoint
through replacement.
Perform a search for the keyword WSS. Write down the number of results.
More results appear than in Task 1 because searching for WSS also returns results for the term
SharePoint Foundation because of expansion.
Results: After this exercise, you should have modified the English thesaurus file.
17
18

In this exercise, you address the concerns of Contosos governance committee regarding searches for
keywords that are considered inappropriate in the workplace based on Contosos employee ethics
policies.
1.
2.
3.
4.
Perform a search.
Update a noise words file.
Restart the Search service.
Test the noise word.
f Task 1: Perform a search
Perform a search for the keyword dirty.

The announcement Mud is dirty is returned as a result.
f Task 2: Update a noise words file
Open the file C:\Program Files\Microsoft Office Servers\14.0\Data

\Office Server\Applications\GUID-query-0\Config\noiseenu.xml in Notepad. Add the word dirty
to the end of the file on its own line. Save your changes, and then close Notepad.
Run Command Prompt as administrator. Type the following commands:

net stop osearch14
net start osearch14
f Task 4: Test the noise word
Perform a search for the keyword dirty.

Note: In a production environment, you should consider reindexing all content after modifying the
noise word file so that the words are removed from the index itself.
Results: After this exercise, you should have added new noise words and validated the behavior of
noise words.

following steps:

Lab Instructions: Implementing Office Web Apps
Module 11
Contents:
Exercise 1: Installing and Configuring Office Web Apps
Exercise 2: Configuring and Testing the Office Web Apps in

a Document Library
Lab Instructions: Implem

menting Office Web Apps
Lab: Implementing Office Web

W Ap
pps
Sccenario
Co
ontosos strate
egic objectivess for the year set
s a target forr improved em
mployee produ
uctivity. ShareP
Point
20
010s collabora
ation features are a pivotal component
c
to achieving thiss objective. On
ne initiative rellated to
th
his project is to
o provide Micrrosoft Office cllient applicatio
on functionalitty to users in a variety of sce
enarios,
in
ncluding remotte users on pe
ersonal computters that may not have Microsoft Office in
nstalled. You ha
ave
be
een tasked witth installing, co
onfiguring, and testing Officce Web Apps to
t improve end
d user producttivity.
f Sttart the virtu

ual machine
es
1..
2..
Start 10174
4A-CONTOSO
O-DC-D.
After CONT
artup, start 101
174A-SP2010
0-WFE1-D.

In this exercise, you will install and configure Office Web Apps to support end user productivity objectives.
1.
2.
3.
Install Office Web Apps.

Configure Office Web Apps Service Applications.
Assign Office Web Apps Service Application Connections.
f Task 1: Install Microsoft Office Web Apps

Open Windows Explorer, and then browse to and double-click D:\Labfiles\Lab11\Setup.exe.
Install Office Web Apps.
For the product key, type BFGMH-8RM8J-JWMCQ-P784Q-F7R2Y.
After Office Web Apps have installed, run the SharePoint Products Configuration Wizard.
When the wizard is complete, SharePoint 2010 Central Administration opens.
f Task 2: Configure Office Web Apps service applications
In Central Administration, complete the Configure your SharePoint Farm wizard.

Accept all default settings, except skip the creation of a site collection.
Click the System Settings link, and then open the Services on Server page.
Confirm that the following services are started, and then close Central Administration.
PowerPoint Service
Excel Calculation Services
Word Viewing Service
f Task 3: Assign Office Web Apps service application connections
Click Application Management, and then on the Service Application Associations page, ensure that
both PowerPoint Service Application and Word Viewing Service service application connections
are included in the default application proxy group.
Results: After completing this exercise, you should have installed and configured Office Web Apps.
Exercise 2: Configuring and Testing the Office Web Apps in a Document

Library
In this exercise, you will test the functionality of Office Web Apps. You will configure a document library to
open documents in the browser. You will upload a PowerPoint presentation and a Word document to a
document library, and then test the viewing and editing experience of the Office Web Apps.
1.
2.
3.
4.
Configure documents to open in a browser.

Create and upload a PowerPoint presentation.
Create and save a Word document.
Test Office Web Apps.
f Task 1: Configure documents to open in a browser
In Internet Explorer, browse to http://intranet.contoso.com/sites/IT.

Activate the Office Web Apps site collection feature.
Configure the Shared Documents document library settings to open documents in the browser.
f Task 2: Create and upload a PowerPoint presentation
Open Microsoft PowerPoint 2010.

Create the following slides:
Title slide layout with the title, Marketing Strategy
Title and Content slide layout with the title, Product
Title and Content slide layout with the title, Pricing
Title and Content slide layout with the title, Packaging
Title and Content slide layout with the title, Positioning
Save the presentation with the name Marketing Strategy.
In Internet Explorer, open the Shared Documents document library, and upload the Marketing
Strategy presentation.
f Task 3: Create and save a Word document
Open Microsoft Word 2010.

Type SharePoint Governance Plan and apply the style Heading 1 to the paragraph.
Click File, and then use the Save & Send command to save the document to the Information
Technology Web sites Shared Documents document library with the name, SharePoint
Governance Plan.
Tip: You may experience one or more delays of up to one minute during this step. If you are
prompted for credentials, enter the user name, CONTOSO\SP_Admin, and the password, Pa$$w0rd.
In Internet Explorer, refresh the view of the Shared Documents document library, and then verify
that SharePoint Governance Plan appears
f Task 4: Test the functionality of Office Web Apps
Open SharePoint Governance Plan.

The document opens in the browser in view mode
Click Edit in Browser.
The document opens in edit mode
Save and close the document.
Open Marketing Strategy.

The presentation opens in the browser in view mode.
The presentation opens in edit mode.
Add a new slide after the existing title slide.
Apply the Title and Content layout.
Add the title, Market Demographics, to the slide.
View the slide show.
Close the presentation.
Results: After completing this exercise, you should have tested the functionality of Office Web Apps.

following steps:
1.
2.
3.

Lab Instructions: Installing and Upgrading to SharePoint 2010
Module 12
Lab Instructions: Installing and Upgrading to SharePoint
2010
Contents:
Lab A: Preparing SharePoint 2007 for Upgrade to SharePoint 2010
Exercise 1: Performing SQL Server Database Maintenance
Exercise 2: Moving a Site Collection Between Content Databases
Exercise 3: Preparing SQL Server Databases for Upgrade
Exercise 4: Preparing SharePoint 2007 for Upgrade
Lab B: Upgrading SharePoint 2007 to SharePoint 2010

Exercise 1: Upgrading SharePoint 2007 to SharePoint 2010
11
Exercise 2: Upgrading Content Databases
12
Exercise 3: Implementing a Visual Upgrade
14
Lab Instructions: Installinng and Upgrading too SharePoint 2010
Lab A:
A Prepa
aring Sh
harePo
oint 200
07 for Upgrade
e to
Share
ePoint 2010
2
f Lo
og on to the
e virtual machine for this lab
1..
2..
Start 10174
4A-CONTOSO
O-DC-F.
After CONT
artup, start 101
174A-SP2007
7-WFE1-F.

f Task 1: Clean up databases
1.
2.
Click Start, click All Programs, click Microsoft SQL Server 2008 R2, and then click SQL Server
Management Studio.
Click Connect.
Click File, click Open, and then click File.
Select D:\Labfiles\Lab12\DefragIndexes.sql, and then click Open.
In the Available Databases list on the toolbar, select WSS_Content_Intranet.
Click Execute. When the query is complete, the status below the Results panel indicates Query
executed successfully. You may have to expand the results window to see the results.
Repeat steps 6 and 7 for the following databases:
3.
4.
5.
6.
7.
8.
9.
WSS_Content_Intranet_IT
WSS_Content_MySites
SharePoint_AdminContent_GUID
SharePoint_Config
Close SQL Server Management Studio.
f Task 2: Confirm sufficient free disk space

1.
2.
Open Windows Explorer and confirm that there is at least 20 gigabytes of free disk space on C drive.
Close Windows Explorer.

1.
2.
Click Start, click All Programs, click Microsoft Office Server, and then click SharePoint 3.0 Central
Administration. If prompted for credentials, provide Contoso\Administrator as the user name and
Pa$$w0rd as the password.
Click the Application Management tab, and then create a new site collection with the following
settings:
Web Application: http://intranet.contoso.com/
Title: Sales
URL: Sales
Primary Site Collection Administrator: Contoso\SP_Admin
f Task 2: Create a new content database

1.
2.
In the Quick Launch, click Application Management.

In the SharePoint Web Application Management section, create a new Content database named
WSS_Content_Intranet_Sales.
f Task 3: Move a site collection between content databases

1.
2.
Open Command Prompt.

To export an Extensible Markup Language (XML) listing of sites in the intranet Web application, type
the following command and press ENTER:
"C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\12\Bin\stsadm.exe" -o enumsites -url http://intranet.contoso.com >
C:\SiteList.xml
3.
To open the site listing in Notepad, type the following command and press ENTER:
notepad C:\SiteList.xml
4.
Delete the following two elements (the entire line of XML):

Site Url="http://intranet.contoso.com"
Site Url="http://intranet.contoso.com/sites/IT"
5.
6.
7.
8.
Confirm that the only remaining Site element is for the Sales site collection.
Click File, and then click Save.
Close Notepad.
Switch to Administrator: Command Prompt.
To move the Sales site collection from the WSS_Content_Intranet content database to the
WSS_Content_Sales content database, type the following command, and then press ENTER:
Extensions\12\Bin\stsadm.exe" -o mergecontentdbs -url http://intranet.contoso.com sourcedatabasename WSS_Content_Intranet -destinationdatabasename
WSS_Content_Intranet_Sales -operation 3 -filename C:\SiteList.xml
9.
To restart IIS, type the following command:

iisreset
f Task 4: Verify and report the move of the site collection

1.
2.
3.
4.
Switch to Internet Explorer. Press F5 to refresh the page. If the Windows Security dialog opens,
type CONTOSO\Administrator in the User name box, type Pa$$w0rd in the Password box, and
then click OK.
Observe that the WSS_Content_Sales content database now contains one site.
To export an XML listing of sites in the intranet Web application, type the following command:
C:\SiteList.xml
5.
To open the site listing in Notepad, type the following command:

6.
7.
8.
9.
Click Format, and then click Word Wrap.

Observe the information that is reported for each site collection, including the owner (primary site
collection administrator), content database, and storage utilization.
Close Notepad.
Close Administrator: Command Prompt.

f Task 1: Back up SharePoint databases using SQL Server
1.
2.
3.
4.
5.
6.
7.
Open Windows Explorer and browse to C drive.

On the toolbar, click New folder.
Type Backups, and then press ENTER.
Management Studio.
Click Connect.
Click New Query.
Type the following query into the query editor panel:
use WSS_Content_Intranet
dbcc shrinkfile ('WSS_Content_Intranet')
dbcc shrinkfile ('WSS_Content_Intranet_log')
go
backup database WSS_Content_Intranet to disk = 'C:\Backups\WSS_Content_Intranet.bak'
go
backup log WSS_Content_Intranet to disk = 'C:\Backups\WSS_Content_Intranet_log.bak'
go
go
8. Click the Execute button.

9. Confirm that at the bottom of the Results panel, the status indicates Query executed successfully.
10. Repeat steps 69 to back up and truncate the WSS_Content_Intranet_IT database. Use the following
query:
use WSS_Content_Intranet_IT
dbcc shrinkfile ('WSS_Content_Intranet_IT')
dbcc shrinkfile ('WSS_Content_Intranet_IT_log')
go
backup database WSS_Content_Intranet_IT to disk =
'C:\Backups\WSS_Content_Intranet_IT.bak'
go
backup log WSS_Content_Intranet_IT to disk =
'C:\Backups\WSS_Content_Intranet_IT_log.bak'
go
go
11. Repeat steps 69 to back up and truncate the WSS_Content_Intranet_Sales database. Use the
following query:
use WSS_Content_Intranet_Sales
dbcc shrinkfile ('WSS_Content_Intranet_Sales')
dbcc shrinkfile ('WSS_Content_Intranet_Sales_log')
go
backup database WSS_Content_Intranet_Sales to disk =
'C:\Backups\WSS_Content_Intranet_Sales.bak'
go
backup log WSS_Content_Intranet_Sales to disk =
'C:\Backups\WSS_Content_Intranet_Sales_log.bak'
go
go
12. Repeat steps 69 to back up and truncate the WSS_Content_MySites database. Use the following
query:
use WSS_Content_MySites
dbcc shrinkfile ('WSS_Content_MySites')
dbcc shrinkfile ('WSS_Content_MySites_log')
go
backup database WSS_Content_MySites to disk = 'C:\Backups\WSS_Content_MySites.bak'
go
backup log WSS_Content_MySites to disk = 'C:\Backups\WSS_Content_MySites_log.bak'
go
go
13.
14.
15.
16.
Open the C:\Backups folder.

Confirm that the database and log backup files were created.
Close the C:\Backups folder.
Close SQL Server Management Studio. When prompted to save your changes, click No.
f Task 2: Back Up a SharePoint 2007 farm using Central Administration

1.
Switch to SharePoint 3.0 Central Administration. Click the Operations link, and then from the
Backup and Restore section perform a backup.
2.
3.
4.
5.
Select the check box next to Farm.

Click Continue to Backup Options.
In the Backup location box, type C:\Backups.
Do not perform a backup at this time. Click Cancel.
f Task 3: Detach content databases

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

In the SharePoint Web Application Management section, click Web application list.
In the SharePoint Web Application Management section, click Content databases.
Click the database name of the first-listed content database.
Select the Remove content database option. A confirmation message appears. Click OK.
Click OK. The content database is removed.
Repeat steps 57 for each content database.
Repeat steps 18 for the Web application SharePoint - mysites.contoso.com80.
Close SharePoint 3.0 Central Administration.

f Task 1: Perform a preupgrade check
1.
2.

Type the following command, and then press ENTER. A report opens in Windows Internet Explorer:
Extensions\12\Bin\stsadm.exe" -o preupgradecheck
3.
4.
5.
6.
7.
Switch to Command Prompt.

Review the output of the command.
Switch to Internet Explorer.
Review the report.
Close all open windows and applications.
f To prepare for the next lab

1.
2.
Turn off 10174A-SP2007-WFE1-F. Leave 10174A-CONTOSO-DC-F running.

Start and connect to 10174A-SP2007-WFE1-G.
10
Labb Instructions: Installing and Upgrading to SharePoint 2010
L B: Upgrading
Lab
U
SharrePoint 2007 to
o Share
ePoint 2
2010
f Lo
og on to the
1..
2..
Start 10174
4A-CONTOSO
O-DC-F.
After CONT
artup, start 101
174A-SP2007
7-WFE1-G.
11

f Task 1: Run the SharePoint Products Configuration Wizard
Note: To save time the actual installation of SharePoint 2010 has already been completed on
10174A-SP2007-WFE1-G. You use this virtual machine for the remainder of the lab.
1.
2.

Click Start, point to All Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint
2010 Products Configuration Wizard.
3. On the Welcome to SharePoint Products page, click Next. A message appears to inform you that
services may have to be started or reset.
4. Click Yes.
5. On the Specify Farm Security Settings page, type 10174_SharePoint_2010 in the Passphrase and
Confirm passphrase boxes.
6. Click Next.
7. On the Visual Upgrade page, review the message and options.
8. Click Preserve the look and feel of existing SharePoint Sites, and allow end users to update
their sites user experience.
9. Click Next.
10. On the Completing the SharePoint Products Configuration Wizard page, click Next. A SharePoint
Products Configuration Wizard message opens. The message reminds you to install the binaries on all
servers in the farm before you run the wizard. Click OK.
11. On the Configuration Successful, Upgrade In Progress page, read the message, and then click
Finish. SharePoint 2010 Central Administration opens.
f Task 2: Validate the upgrade

1.
2.
3.
4.
5.
In SharePoint 2010 Central Administration, on the Upgrade Status page, confirm that Status is
Succeeded. You might need to wait a few minutes before the upgrade completes. Press F5 to refresh
the page, and then return to step 1.
Observe the number of Errors and Warnings. There should be no errors. However, warnings are
expected.
Identify the Log File that contains a record of events during the upgrade.
Open the log file in Notepad.
Press CTRL+F, and then type [Warning].
Tip: Include the brackets.
6.
7.
8.
Read the first warning message.

Press F3 to locate the next warning message, and then read the message. Repeat this step for all
warning messages.
Close Notepad.
12

f Task 1: Attempt to attach a content database
1.
2.
3.
4.
5.
6.
7.

In the Databases section, click Manage content databases.
Click Add a content database.
In the Database Server box, type SP2007-WFE1.
In the Database Name box, type WSS_Content_Intranet.
Click OK. An error page opens that explains that you must use the addcontentdb operation of
Stsadm.exe or the Mount-SPContentDatabase cmdlet of Windows PowerShell to attach and
upgrade a content database.
Click Go back to site.
f Task 2: Attach content databases using Windows PowerShell

1.
2.

Mount-SPContentDatabase "WSS_Content_Intranet" -DatabaseServer SP2007-WFE1 WebApplication http://intranet.contoso.com
Mount-SPContentDatabase "WSS_Content_Intranet_IT" -DatabaseServer SP2007-WFE1 WebApplication http://intranet.contoso.com
Mount-SPContentDatabase "WSS_Content_Intranet_Sales" -DatabaseServer SP2007-WFE1 WebApplication http://intranet.contoso.com
f Task 3: Verify the database upgrade

1.
2.
3.
4.
5.
6.
Switch to SharePoint 2010 Central Administration.

In the Quick Launch, click Upgrade and Migration.
In the Upgrade and Patch Management section, click Check upgrade status.
Click the first item in the Upgrade sessions list.
Identify the Starting object for the upgrade session.
Observe the number of errors and warnings.
Note: There should be no errors, but warnings are expected.
7.
Repeat steps 46 for each upgrade session.
f Task 4: Verify the database attach

1.
2.
3.
4.
5.
6.
7.

Confirm that three databases are attached to the intranet Web application.
Click WSS_Content_Intranet.
In the Database Versioning section, confirm that the
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version is
14.0.4762.1000.
f Task 5: Verify database upgrade status

1.
2.
3.
4.
5.
6.

In the Upgrade and Patch Management section, click Check product and patch installation
status.
Confirm that all products are listed as Installed with a version of 14.0.4763.1000.
In the Upgrade and Patch Management section, click Review database status.
Confirm that the Status for all databases is No action required.

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
In the Quick Launch, click Configuration Wizards.

In the Farm Configuration section, click Launch the Farm Configuration Wizard.
Click Yes, I am willing to participate (Recommended). Click OK.
Click Start the Wizard.
In the Service Account section, click Create new managed account.
In the User name box, type CONTOSO\SP_ServiceApps.
In the Password box, type Pa$$w0rd.
Click Next.
Click Skip.
Click Finish.
Close SharePoint 2010 Central Administration.
13
14

f Task 1: Validate the SharePoint 2007 user interface
1.
2.
3.
4.
5.

/sites/IT. If you receive an error message, click Go back to site.
Click Welcome Contoso\Administrator, and then click Sign in as Different User.
Log on as Contoso\SP_Admin with the password Pa$$w0rd.
In the Quick Launch, click Calendar.
Observe the SharePoint 2007 user interface.
f Task 2: Preview the SharePoint 2010 user interface

1.
2.
3.
Click Site Actions, and then click Visual Upgrade.

Select the Preview the updated user interface option, and then click OK.
Observe the new SharePoint 2010 user interface.
f Task 3: Revert to the SharePoint 2007 user interface

1.
2.
3.
4.
5.
On the information bar, click View or modify this sites Visual Upgrade settings.
Click Use the previous user interface, and then click OK.
Click the Home tab.
f Task 4: Upgrade to the SharePoint 2010 user interface

1.
2.
3.

Click Update the user interface, and then click OK.
Click Site Actions, and then observe that the Visual Upgrade command no longer appears.

following steps:
1. On the host computer, start Microsoft Hyper-V Manager.
2. Right-click the virtual machine name in the Virtual Machines list, and then click Revert.
3. In the Revert Virtual Machine dialog, click Revert.
Lab Instructions: Implementing Business Continuity
Module 13
Contents:
Lab A: Implementing a Backup Strategy
Exercise 1: Backing Up SharePoint Using Central Administration
Exercise 2: Investigating SharePoint Backup Logs and Files
Exercise 3: Automating SharePoint Backup Using Windows PowerShell
Lab B: Implementing a Restore Strategy

Exercise 1: Restoring a Web Application Using Central Administration
10
Exercise 2: Investigating SharePoint Restore Logs and Files
11
Exercise 3: Performing a Partial Restore
13
Lab Instructions: Implem

menting Business Conntinuity
Lab A: Imple
ementin
ng a Ba
ackup Strategy
y
Sccenario
Co
ontosos Share
ePoint governa
ance plan requ
uires that sites be backed up
p regularly. You have been asked to
de
emonstrate the out of box backup
b
functio
onality of Share
ePoint Server 2010,
2
and to create
c
an autom
mated,
niightly backup of the SharePo
oint farm.
Sttart the virtu

ual machine
es
1..
2..
Start 10174
4A-CONTOSO
O-DC-E.
After CONT
artup, start 101
174A-SP2010
0-WFE1-E.

In this exercise, you will use the out of box backup operation in Central Administration to back up the
intranet Web application.
1.
2.
Create a backup share.

Back up a Web application with Central Administration.
f Task 1: Create a backup share
Create a new folder, C:\SharePointBackup. Assign NTFS permissions that allow the Users group Full
Control. Share the folder with the share name, SharePointBackup, and with share permissions that
allow the Everyone group Full Control.
Note: In a production environment, you should configure NTFS permissions that ensure the least
privilege access to the folder. The service account that performs the backup operation should be
given Full Control permission to the backup share.
f Task 2: Back up a Web application with Central Administration
Open SharePoint 2010 Central Administration, click the Backup and Restore link, and then
browse to the Perform a Backup page. Observe the components that can be backed up:
Farm
Various solutions and services
Microsoft Office InfoPath Forms Services
SharePoint Server State Service
Microsoft SharePoint Foundation Web Application(s)
WSS_Administration
SharePoint Server State Service Proxy
SPUserCodeV4
Global Search Settings
Application Registry Service
Shared Services
Perform a full backup of the Web application,

SharePoint intranet.contoso.com80, to the backup share,
\\SP2010-WFE1.contoso.com\SharePointBackup.
The Backup and Restore Job Status page opens. The page refreshes every few seconds. You can click
Refresh to refresh the page manually.
Wait until Phase shows as Completed.

Note: The backup operation may complete with warnings. This is expected in this lab. You may
continue to the next step.
Results: After this exercise, you should have backed up the intranet Web application using Central
Administration.

When you backed up the intranet Web application, you noticed that a warning was generated. In this
exercise, you will investigate the files and logs in the backup share to identify the cause of the warning.
1.
2.
Examine the backup folder.

Identify backup warnings and errors in the backup log.
Task 1: Examine the backup folder
Switch to Microsoft Windows Explorer and browse to C:\SharePointBackup, and then open the
file, spbrtoc.xml, in Microsoft Notepad. Examine the file, which is similar to the following:
<?xml version="1.0" encoding="utf-8"?>
<SPBackupRestoreHistory>
<SPHistoryObject>
<SPId>GUID of operation/SPId>
<SPRequestedBy>CONTOSO\SP_Admin</SPRequestedBy>
<SPBackupMethod>Full</SPBackupMethod>
<SPRestoreMethod>None</SPRestoreMethod>
<SPStartTime>Start Date and time</SPStartTime>
<SPFinishTime>End Date and time</SPFinishTime>
<SPIsBackup>True</SPIsBackup>
<SPConfigurationOnly>False</SPConfigurationOnly>
<SPBackupDirectory>\\SP2010-WFE1.contoso.com\
SharePointBackup\
spbr0000\</SPBackupDirectory>
<SPDirectoryName>spbr0000</SPDirectoryName>
<SPDirectoryNumber>0</SPDirectoryNumber>
<SPTopComponent>Farm\Microsoft SharePoint Foundation
Web Application\SharePoint
intranet.contoso.com80</SPTopComponent>
<SPTopComponentId>GUID of top component</SPTopComponentId>
<SPWarningCount>1</SPWarningCount>
<SPErrorCount>0</SPErrorCount>
</SPHistoryObject>
</SPBackupRestoreHistory>
Locate the SPHistoryObject element.

This element describes the backup operation, and is used during a restore operation.
Locate the SPBackupDirectory element.

This element is a reference to the folder in which the backup files are stored.
Locate the SPWarningCount and SPErrorCount elements.

These elements report warnings and errors.
Close Notepad.
Open the spbr0000 folder, and then observe the backup (*.bak) files in the folder.
Open the file, Spbackup.xml, in Notepad. Examine the file.

This file contains attributes related to the backup operation and to each of the components. It is used
during a restore operation. You should not modify, delete, or rename the Spbackup.xml file.
Close Notepad.
f Task 2: Identify backup warnings and errors in the backup log
Open the file, Spbackup.log, in Notepad.
Examine the log. Observe that each of the backup operations is listed, including the T-SQL commands
that were sent to SQL Server.
Observe the last lines of the log, which indicate that the backup completed and summarize the
number of warnings and errors.
Navigate to the top of the log, and then use the Find command to find the text, Warning:.
Tip: Include the colon.
Write down the warning message.
Navigate to the top of the log, and then use the Find command to find the text, BACKUP
DATABASE. Observe the command that was sent to SQL Server to back up one of the SharePoint
databases.
Answer the following questions:
Which SharePoint database was backed up?
Which database backup (.bak) file in the backup folder contains that SharePoint database?
Repeat step 5 to identify the database backup file that contains the backup of the WSS_Content_IT
database.
Close Notepad.
Results: After this exercise, you should have investigated the files and logs in the SharePoint backup
share. You should also have identified the database that is a backup of the SQL database,
WSS_Content_IT.

In this exercise, you will use Windows PowerShell and the Windows Task Scheduler to automate the
nightly backup of your SharePoint farm.
1.
2.
3.
4.
Create a backup script.

Schedule the backup script.
Test the scheduled backup task.
Monitor the backup operation.
f Task 1: Create a backup script
Create a new folder, C:\Scripts.
Create a script named C:\Scripts\Backup.ps1, with the following text:

Backup-SPFarm -directory \\SP2010-WFE1.contoso.com\SharePointBackup -backupmethod
Full
f Task 2: Schedule the backup script
Create a scheduled task using the following specifications:
Task name: Backup SharePoint FULL
Description: Back up the SharePoint farm
Schedule: Daily at 1:00 a.m.
Action: Start the program PowerShell.exe with the argument C:\Scripts\backup.ps1.
Run the script as Contoso\SP_Farm and choose the option to Run whether user is logged on
or not.
Run with highest privileges.
Provide Pa$$w0rd as the password.
f Task 3: Test the scheduled backup task
Run the task, Backup SharePoint FULL.
Open the C:\SharePointBackup folder.

You should see another set of backups get loaded into the file share.
Note: The operation to perform a full backup of the entire farm takes several minutes to complete.
Tip: You may continue to the next task.
f Task 4: Monitor the backup operation
Switch to SharePoint 2010 Central Administration, and then browse to the Backup and Restore
Job Status page.
Refresh the page and examine the information that is presented on the page.
Browse to the Backup and Restore History, and then examine the information that is presented.
Return to the Backup and Restore Job Status page, and then wait for the Phase to be Completed
before continuing to the next lab.

Results: After this exercise, you should have created a backup script using Windows PowerShell and
scheduled the script to run nightly.
Allow the backup operation to continue until it has completed. You will use the same virtual machines
in the next lab to perform restore operations.
Lab Instructtions: Implementing Business Continuity
L B: Im
Lab
mpleme
enting a Restorre Strategy
Sccenario
Yo
ou have recently configured
d an automated
d, nightly backkup of your Sh
harePoint farm
m. The SharePoint
go
overnance pollicy requires yo
ou to test yourr backups everry 60 days. You
u have been ta
asked with testting the
m
most
recent bacckup by restorring it to a stag
ging environm
ment. You mustt also verify that you can perrform a
pa
artial restore of
o a site collecttion, site, and list.
10

In this exercise, you will test the integrity of the most recent backup by restoring a Web application using
Central Administration.
1.
2.
3.
4.
Delete a Web application.

Test the deleted Web application.
Restore a Web application using Central Administration.
Verify the restored Web application.
f Task 1: Delete a Web application
Open SharePoint 2010 Central Administration, click Application Management, and then browse
to the Web Applications Management page.
Delete the Web application, SharePoint - intranet.contoso.com80, including its content databases
and IIS Web sites.
f Task 2: Test the deleted Web application
Open Microsoft Internet Explorer, and then browse to http://intranet.contoso.com/sites.
An error page opens.
f Task 3: Restore a Web application using Central Administration
Switch to SharePoint 2010 Central Administration, and then browse to the Restore from Backup
page.
Select the most recent Farm backup, and then click Next.
Select the SharePoint - intranet.contoso.com80 Web application to restore, and then click Next.
Select the Same configuration restore option, and configure the login password for the
CONTOSO\SP_ServiceApp account as Pa$$w0rd.
Start the restore operation. Monitor its status until the Phase shows as Completed.
f Task 4: Verify the restored Web application
Switch to Internet Explorer, and then browse to http://intranet.contoso.com. Verify that the
intranet site opens.
Results: After this exercise, you should have deleted and then restored a SharePoint Web application.

When you performed the restore of the intranet Web application, you noticed that warnings were
reported. In this exercise, you will investigate the restore logs to identify the cause of these warnings.
1.
2.
Examine the backup folder.

Identify restore warnings and errors in the restore log.
f Task 1: Examine the backup folder
Open the SharePoint backup folder, and then open the file, Spbrtoc.xml, in Notepad. Examine the
file to discover the following:
Identify the SPHistoryObject element that describes the restore operation.
Locate the SPRestoreMethod element.

This element describes the type of restore operation that was performed.

Locate the SPTopComponent element.

This element describes the top level component of the farm that was restored.

These elements report warnings and errors. The same count was shown on the timer job status
page in the previous task.
Close Notepad.
Open the spbr0001 folder.
Open the file, Sprestore.xml, in Notepad. Examine the file.

This file contains attributes related to the restore operation and to each of the components. You
should not modify, delete, or rename the Sprestore.xml file.
Close Notepad.
f Task 2: Identify restore warnings and errors in the restore log
Open the file, Sprestore.log, in Notepad.
Observe the last lines of the log, which indicate that the backup completed and summarizes the
Navigate to the top of the log, and then use the Find command to find the text, Progress: Starting
Restore.
This step locates the beginning of the restore operation.
Navigate to the top of the log, and then use the Find command to find the text, Warning:.
11
12
Navigate to the top of the log, and then use the Find command to find the text, RESTORE
DATABASE. Observe the command that was sent to SQL Server to back up one of the SharePoint
databases.
Close Notepad.
Results: After this exercise, you should have investigated the restore logs in the SharePoint backup
share.
13

In this exercise, you will perform and validate partial restore operations on SharePoint lists and libraries.
1.
2.
3.
4.
5.
6.
7.
8.
9.
Restore a content database.

Delete a document library.
Export a document library from an unattached content database.
Restore a deleted document library.
Validate the restored document library.
Delete a list.
Export a list from an unattached content database.
Restore a deleted document library.
Validate the restored list.
f Task 1: Restore a content database
Open SQL Server Management Studio as Contoso\Administrator with the password of Pa$$w0rd.
Right-click Databases, and then click Restore Database.
In the To Database box, type WSS_Content_Intranet_IT_Backup.
Click From device, and then select C:\SharePointBackup

\spbr0000\000000xx.bak, where 000000xx.bak is the backup of the WSS_Content_Intranet_IT
database that you identified in Lab A, Exercise 2, Task 2.
In the Select the backup sets to restore box, select the check box next to
WSS_Content_Intranet_IT.
Tip: If you do not see WSS_Content_Intranet_IT listed, it is because you did not restore the correct
database. Return to Lab A, Exercise 2, Task 2 to identify the database that contains
WSS_Content_Intranet_IT. Then repeat Task 1 of this exercise.
Perform the restore operation.
f Task 2: Delete a document library
Switch to the instance of Internet Explorer that displays the intranet site.
Browse to http://intranet.contoso.com/sites/IT, and then delete the Shared Documents

document library.
f Task 3: Export a document library from an unattached content database
Switch to SharePoint 2010 Central Administration, click the Backup and Restore link, and then
browse to the Unattached Content Database Recovery page.
Perform an export with the following specifications:
Database name: WSS_Content_Intranet_IT_Backup
Object: /sites/it/Shared Documents
Export to filename: \\SP2010-WFE1.contoso.com\SharePointBackup

\ITSharedDocuments.cmp
Export full security
After you start the export, monitor the Granular Backup Job Status page until the job is complete.
14
f Task 4: Restore a deleted document library
Open SharePoint 2010 Management Shell as Contoso\SP_Farm with the password of Pa$$w0rd.
To do this, hold down the SHIFT key, right-click SharePoint 2010 Management Shell and then click
Run as different user.
To import the document library, type the following command:

Import-SPWeb -identity http://intranet.contoso.com/Sites/IT -path
c:\SharePointBackup\ITSharedDocuments.cmp
f Task 5: Validate the restored document library
Switch to the instance of Internet Explorer that displays the Information Technology Dept Web.
Confirm that the Shared Documents document library is restored.
f Task 6: Delete a list
Delete the Announcements list.
f Task 7: Export a list from an unattached content database
Switch to SharePoint 2010 Central Administration, and then browse to the Unattached Content
Database Recovery page.
Perform an export with the following specifications:
Database name: WSS_Content_IT_Backup
Object: /sites/it/Announcements
Export to filename: \\SP2010-WFE1.contoso.com\SharePointBackup

\ITAnnouncements.cmp
Export full security
After you start the export, monitor the Granular Backup Job Status page until the job is complete.
f Task 8: Restore a deleted list
To import the list, type the following command:

c:\SharePointBackup\ITAnnouncements.cmp
f Task 9: Validate the restored list
Switch to the instance of Internet Explorer that displays the Information Technology Dept Web.
Confirm that the Announcements list is restored.
Results: After this exercise, you should have restored a deleted SharePoint document library and list.

following steps:
Lab Instructions: Monitoring and Optimizing SharePoint Performance
Module 14
Lab Instructions: Monitoring and Optimizing SharePoint
Performance
Contents:
Lab A: Configuring SharePoint Monitoring
Exercise 1: Configuring SharePoint Diagnostic Logging
Lab B: Analyzing SharePoint Health

Exercise 1: Configuring Health Analyzer Rules
Exercise 2: Reviewing and Repairing Health Analyzer Problems
Lab C: Reporting SharePoint Usage

Exercise 1: Configuring SharePoint Usage Data Collection
Exercise 2: Creating Reports from the Logging Database
10
Lab Instructions: Monitoring and Optimizing SharePoint Performaance
Lab A: Confiiguring
g ShareP
Point Monitor
M
ring
Sccenario
Co
ontosos Share
ePoint governa
ance plan speccifies levels of monitoring fo
or the development and prod
duction
en
nvironments th
hat differ from
m the out of bo
ox settings. You have been ta
asked with con
nfiguring mon
nitoring
an
nd with demonstrating how developers ca
an use monitorring to trouble
eshoot errors generated
g
by their
t
co
ode.
f Lo
og on to the
1..
2..
Start 10174
4A-CONTOSO
O-DC-D.
After CONT
artup, start 101
174A-SP2010
0-WFE1-D.

Scenario
The development team plans to deploy several new solutions to the development environment. The
governance plan dictates a higher level of monitoring during periods of solutions deployment and testing
so that developers can view errors generated by their code. However, you must also ensure that the size
of log files does not grow out of control.
1.
2.
Configure diagnostic logging.

Review a log file.
f Task 1: Configure diagnostic logging

1.
2.
3.

Open SharePoint 2010 Central Administration, click the Monitoring link, and then browse to the
Diagnostic Logging page.
Configure all categories of events to use verbose logging to both the event log and the trace log.
Enable event log flood protection and ensure that trace logs do not grow larger than 10 gigabytes
(GB).
Note: It is not recommended to configure a verbose-level trace log in a production environment.
f Task 2: Review a log file
Open Windows Explorer and browse to the C:\Program Files

\Common Files\Microsoft Shared\Web Server Extensions\14\Logs folder. Open the most
recently modified log (*.log) file. Examine the log. Observe the number of events that are logged in
just a few seconds. Close the log and the Windows Explorer window that displays the Logs folder.
Results: After this exercise, you should have configured verbose diagnostic logging for your
SharePoint farm.
Leave the virtual machines running. You will use them in the next lab.
L B: Analyzin
Lab
A
ng Share
ePoint Health
H
Sccenario
Yo
ou have just in
nstalled a SharePoint 2010 fa
arm. When you
u open Centra
al Administratio
on, an error message
m
ap
ppears at the top
t of the pag
ge that indicate
es an error in configuration.
c
The SharePoin
nt governance
e plan
m
mandates
that SharePoint
S
farms at Contoso
o should be de
eployed using Microsoft-reco
ommended be
est
prractices. You have
h
been taskked with determ
mining the cau
use of the erro
or message and correcting th
he
co
onfiguration of
o the farm.

In this exercise, you explore the default Health Analyzer rules.
1.
2.
3.
Review Health Analyzer problems.

Configure Health Analyzer rule definitions.
Run a Health Analyzer rule.
f Task 1: Review Health Analyzer problems
Open SharePoint 2010 Central Administration, click the Monitoring link, and browse to the
Review problems and solutions page. Observe the list of reported problems.
f Task 2: Configure Health Analyzer rule definitions

1.
Click the Monitoring link, and then browse to the Health Analyzer Rule Definitions page. Observe
the four categories of rules:
Security4 rules
Performance17 rules
Configuration30 rules
Availability13 rules
Tip: The list of rules is paged. Click the Next Page button, displayed as a right-pointing arrow below
the list, to see additional rules.
2.
Open the Some content databases are growing too large rule. Observe that you can change the
following attributes of the rule, but do not make any changes at this time:
Title
Scope
Schedule
Enabled
Repair Automatically
Version
Note: You cannot change the actions that the rule uses to perform its health analysis task. The rules
actions are determined by the code used to develop the rule.
3.
Edit the rule and change the Schedule to Daily.
f Task 3: Run a Health Analyzer rule
Run the following two rules:
Availability category: Some content databases are growing too large
Configuration category: One or more categories are configured with Verbose trace logging
Results: After this exercise, you should have configured rule definitions and run two rules.

In this exercise, you review and repair problems identified by the Health Analyzer.
1.
2.
3.
Review Health Analyzer problems.

Repair Health Analyzer problems.
Validate the Health Analyzer solution.

1.
2.
3.
4.
Open SharePoint 2010 Central Administration, click the Monitoring link, and browse to the
Review problems and solutions page.
Observe the list of reported problems. In the Configuration section, observe that a new problem is
reported: One or more categories are configured with Verbose trace logging.
Click the problem, and then examine the information that is presented on the problem details page.
Click Reanalyze Now to reanalyze the problem.
On the Review problems and solutions page, refresh the page until the Modified column for the
problem indicates that the rule was analyzed.
f Task 2: Repair Health Analyzer problems

1.
2.
Click the One or more categories are configured with Verbose trace logging problem.
Click Repair automatically. On the Health Analyzer Reports list, refresh the page until the problem
report disappears.
f Task 3: Validate the Health Analyzer solution

1.
2.
3.
4.
5.
6.
Click the Monitoring link, and then browse to the Diagnostic Logging page.
Observe that the two lists, Least critical event to report to the event log and Least critical event
to report to the trace log, are reset. They no longer are set to Verbose.
For All Categories, set event log reporting level to Error and trace log reporting level to
Unexpected.
Browse to the Health Analyzer Rule Definitions page. Run the rule One or more categories are
configured with Verbose trace logging.
Browse to the Review problems and solutions page and confirm that the rule One or more
categories are configured with Verbose trace logging is not shown on the report.
Results: After this exercise, you should have configured Health Analyzer rules, reviewed Health
Analyzer reports, and repaired Health Analyzer problems.
You use the same virtual machines in the next lab.
L C: Reportin
Lab
R
ng Share
ePoint Usage
U
Sccenario
Co
ontoso recently implemente
ed a systems management
m
re
eport center. You
Y are require
ed to submit reports
r
re
elated to perfo
ormance and usage.
u
You havve been tasked
d with creating
g a SharePoint performance and
ussage report that uses the SharePoint loggiing database as
a its data sourrce.

In this exercise, you configure SharePoint usage data collection and trigger the jobs that collect data.
1.
2.
Perform usage data collection.

Create reports from the logging database.
f Task 1: Perform usage data collection

1.
2.
3.
4.
Open SharePoint 2010 Central Administration. Click the Monitoring link, and then browse to the
Configure web analytics and health data collection page. Click Health Logging Schedule.
Observe the set of Health Analysis jobs. Then, run the Health Analysis Job (Daily, Microsoft
SharePoint Foundation Timer, All Servers) job.
Click the Monitoring link, and then browse to the Configure web analytics and health data
collection page. Click Log Collection Schedule. Run the following jobs: Microsoft SharePoint
Foundation Usage Data Import and Microsoft SharePoint Foundation Usage Data Processing.
Results: After this exercise, you should have executed the logging timer jobs that populate the
logging database.
10

In this exercise, you create reports in Microsoft Excel using the logging database as the data source.
1.
2.
Explore logging database tables.

Create a logging report using Microsoft Excel.
f Task 1: Explore logging database tables

1.
2.
3.

Open SQL Server Management Studio and expand the tables in the WSS_Logging database. You
should see several tables with different partition names.
Execute the following query, and record the ConfigValue value that is returned in the Results panel:
Use WSS_Logging
Select * from configuration where configname = 'max partition id - TimerJobUsage'
f Task 2: Create a logging report using Microsoft Excel

1.
2.
3.
4.
5.
Open Microsoft Excel 2010.

If the Microsoft Office Activation Wizard appears, click Cancel.
Save the new workbook with the name SharePoint Timer Job Duration Report.
Create a data connection with the following configuration:
SQL Server: SP2010-WFE1
Database: WSS_Logging
Table: TimerJobUsage_PartitionXX table, where XX is the ConfigValue value you obtained in

Task1.
Create a PivotTable report. In the PivotTable Field List panel, in the Choose fields to add to report
list, select the following options:
MachineName
WebApplicationName
JobTitle
Drag the Duration field from the field list to the Values box.
You now have a report of timer job durations presented by server, by webapplication, and by
timerjob.
Results: After this exercise, you should have created a usage report based on data from the
SharePoint logging database.
To revert the virtual machines

following steps:
1.
2.
3.

In the Revert Virtual Machine dialog, click Rev
Lab Answer Key: Introducing SharePoint 2010
Module 1
Contents:
10
11
Lab: Installing SharePoint 2010

1.
2.
Start 10174A-CONTOSO-DC-A.
After CONTOSO-DC-A has completed startup, start 10174A-SP2010-WFE1-A.

1.
2.
3.
4.

On SP2010-WFE1, click Start, point to Administrative Tools, and then click Active Directory Users
and Computers.
Expand contoso.com, and then click SharePoint.
Right-click SharePoint, point to New, and then click User.
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
5.
6.
7.
In the Full name box, type SharePoint Administrator.

In the User logon name box, type SP_Admin.
Click Next.
In the Password and Confirm password boxes, type Pa$$w0rd.
Clear the User must change password at next logon check box.
Select the Password never expires check box.
Click Next.
Click Finish.
Right-click SharePoint Administrator, and then click Properties.
In the Description box, type SharePoint Administrator and Setup User.
In the E-mail box, type SP_Admin@contoso.com.
Click OK.
Repeat steps a-l to create an account with the following configuration:
Full name: SharePoint Farm Service
User logon name: SP_Farm
Description: SharePoint Farm Service
E-mail: SP_Farm@contoso.com
Repeat steps a-l to create an account with the following configuration:
Full name: SharePoint Service Applications
User logon name: SP_ServiceApps
Description: SharePoint Service Applications
E-mail: SP_ServiceApps@contoso.com
Close Active Directory Users And Computers.
f Task 2: Create a SQL Server login for the SharePoint administrator

1.
Click Start, click All Programs, click Microsoft SQL Server 2008 R2, hold the SHIFT key and rightclick SQL Server Management Studio, and then click Run as different user.
The Windows Security dialog box appears.
2.
In the User name box, type CONTOSO\SQL_Admin.
3.
4.

Click OK.
Microsoft SQL Server Management Studio opens.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Click Connect.
Expand Security.
Right-click Logins, and then click New Login.
In the Login name box, type CONTOSO\SP_Admin.
In the Select a page panel, click Server Roles.
Select the dbcreator check box.
Select the securityadmin check box.
Click OK.
Close Microsoft SQL Server Management Studio.
f Task 3: Delegate administration of the SharePoint server

1.
2.
3.
4.
5.
6.
7.
8.
In the taskbar, click Server Manager.

Expand Configuration, expand Local Users and Groups, and then click Groups.
In the details pane, double-click Administrators.
Click Add.
In the Enter the object names to select box, type CONTOSO\SP_Admin, and then click OK.
Click OK.

f Task 1: Attempt to install SharePoint Server prerequisites
1.
2.
3.

Open D:\Software\SharePointServer2010.
Double-click default.hta.
The SharePoint Server 2010 Start page opens.
4.
Click Install software prerequisites.

The User Account Control dialog box appears.
5.
Click Yes.
6.
7.
8.
Click Next.
Select the I accept the terms of the License Agreement(s) check box.
Click Next.
The prerequisite installer prepares the server.
The Microsoft SharePoint 2010 Products Preparation Tool displays the message, There was an error
during installation. A summary of prerequisite installation status is also displayed.
f Task 2: Identify prerequisite installation errors

1.
Click Review the log file.

The PrerequisiteInstaller log file opens.
2.
Press CTRL+F.
The Find dialog box appears.
3.
4.
5.
6.
Type 976462, and then click Find Next.

Observe the lines in the log file that indicate that the prerequisite installer checked for the existence
of Hotfix for Microsoft Windows (KB976462).
Click Find Next.
Observe the lines in the log file that indicate that the prerequisite installer attempted to download
Hotfix for Microsoft Windows (KB976462) from microsoft.com. Observe the URL that was used.
You can use this URL to manually download the prerequisite.
7.
8.
9.
Click Cancel and then close the log file.

Click Finish in the Microsoft SharePoint 2010 Products Preparation Tool.
Click Exit on the SharePoint Server 2010 Start page.
f Task 3: Copy SharePoint prerequisite installation files

1.
2.
3.
4.
5.
Open D:\Software\SharePoint Prerequisites.

To select all files in the folder, press CTRL+A.
To copy all files, press CTRL+C.
Open D:\Software\SharePointServer2010\PrerequisiteInstallerFiles.
To paste all files, press CTRL+V.
f Task 4: Script the installation of SharePoint Server prerequisites

1.
2.
Open Notepad.
Type the following, on one line, with spaces between each switch:
/SQLNCli:PrerequisiteInstallerFiles\sqlncli.msi
/ChartControl:PrerequisiteInstallerFiles\MSChart.exe
/KB976462:PrerequisiteInstallerFiles\Windows6.1-KB976462-v2-x64.msu
/IDFXR2:PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu
/Sync:PrerequisiteInstallerFiles\Synchronization.msi
/FilterPack:PrerequisiteInstallerFiles\FilterPack.msi
/ADOMD:PrerequisiteInstallerFiles\SQLSERVER2008_ASADOMD10.msi
/ReportingServices:PrerequisiteInstallerFiles\rsSharePoint.msi
/Speech:PrerequisiteInstallerFiles\SpeechPlatformRuntime.msi
/SpeechLPK:PrerequisiteInstallerFiles\MSSpeech_SR_en-US_TELE.msi
Alternately, you can copy the contents of the file,

D:\Labfiles\Lab01\PrerequisiteInstaller.Arguments.txt and paste it into your Notepad document.
3.

The Save As dialog box appears.
4.
Type D:\Software\SharePointServer2010, and then press ENTER.

The SharePointServer2010 folder opens.
5.
6.
7.
Type PrerequisiteInstaller.Arguments.txt, and then press ENTER.

Close Notepad.
Start the Command Prompt using the Run as administrator option.
8.
9.
Click Yes.
Type the following commands, each followed by ENTER:
D:
CD Software\SharePointServer2010
PrerequisiteInstaller.exe

In a production environment, you would also add the /unattended switch to the
PrerequisiteInstaller.Arguments.txt file to specify a silent, unattended installation of SharePoint
prerequisites. An unattended installation will skip the Welcome page and the license agreement.
For this lab, however, you did not use the /unattended switch, so that you may observe the progress
of the prerequisite installer and ensure that there are no errors in your script.
10. Click Next.
11. Click I accept the terms of the License Agreement(s).
12. Click Next.
SharePoint prerequisites are installed.
13. On the Installation Complete page, confirm that installation completed successfully.
14. Click Finish.

f Task 1A: Install SharePoint Server
1.
In the SharePointServer2010 folder, double-click default.hta.

The SharePoint Server 2010 Start page opens.
2.
On the SharePoint Server installation page, click Install SharePoint Server.

3.
4.
5.
6.
7.
8.
Click Yes.
Type 36BY2-DVVJY-6426X-PXWVQ-BM342, and then click Continue.
Select the I accept the terms of this agreement check box.
Click Continue.
Click Server Farm.
On the Server Type page, click Complete, and then click Install Now.
Installation proceeds for approximately 7-10 minutes.
9.
On the Run Configuration Wizard page, clear the Run the SharePoint Products Configuration
Wizard now check box.
10. Click Close.
11. On the SharePoint installation page, click Exit.
12. Close the Windows Explorer window that is displaying the contents of the SharePointServer2010
folder.
f Task 1B: Script the installation of SharePoint Server

As an alternate to this procedure, you can copy D:\Labfiles\Lab01\config.xml to the
D:\Software\SharePointServer2010\Files\SetupFarmSilent folder, overwriting the existing file.
1.
2.
3.
Open D:\Software\SharePointServer2010\Files\SetupFarmSilent.
Right-click config.xml, and then click Edit.
Perform one of the following two tasks:
1.
Replace line 11the PID elementwith the following line:

<PIDKEY Value="36BY2-DVVJY-6426X-PXWVQ-BM342" />
Remove the comment tags, <!- and -->.

2.
Replace the Display element with the following:

<Display AcceptEULA="yes"
Level="basic"
CompletionNotice="yes" />
In a production environment, you would leave the Display element with its default values
(Level=none and CompletionNotice=no) for a completely unattended installation.
In this lab, you change the values of the Display element so that installation can be monitored.
4.
5.
6.

Click File, and then click Exit.
Start Command Prompt using the Run as administrator option.
7.
8.
Click Yes.
Type the following command on one line, and then press ENTER:
"D:\Software\SharePointServer2010\setup.exe" /config
"D:\Software\SharePointServer2010\Files\SetupFarmSilent\
config.xml"
Installation takes approximately 7-10 minutes. A progress bar is displayed.

In a production environment in which you have configured the DisplayLevel value to none, you can
monitor the progress of the SharePoint installation using any of these methods:
9.
Click Start, then type %temp% and then press ENTER. Open the log named SharePoint Server
Setup*.log.
Open Task Manager, and then monitor processes including msiexec.exe, setup.exe,
mscorsvw.exe, and psconfigui.exe.
On the Run Configuration Wizard page, clear the Run the SharePoint Products Configuration
Wizard now check box.
10. Click Close.

f Task 1A: Run the SharePoint Products Configuration Wizard
1.
Click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then click
SharePoint 2010 Products Configuration Wizard.
2.
Click Yes.
After a few minutes, the SharePoint Products Configuration Wizard appears.
3.
On the Welcome to SharePoint Products page, click Next.

A message appears to inform you that services may have to be started or reset.
4.
5.
6.
7.
8.
9.
10.
Click Yes.
On the Connect to a server farm page, click Create a new server farm, and then click Next.
In the Database server box, type SP2010-WFE1.
In the Username box, type CONTOSO\SP_Farm.
Click Next.
On the Specify Farm Security Settings page, type 10174_SharePoint_2010 in the Passphrase and
Confirm passphrase boxes, and then click Next.
11. On the Configure SharePoint Central Administration Web Application page, select the Specify
port number check box.
12. In the Specify port number box, type 9999, and then click Next.
13. On the Completing the SharePoint Products Configuration Wizard page, click Next.
The Configuring SharePoint Products page indicates the progress of configuration, which takes
approximately five minutes.
14. On the Configuration Successful page, click Finish.
Windows Internet Explorer appears and opens the Help Make SharePoint Better page. This is the
Customer Experience Improvement survey page of the SharePoint 2010 Central Administration
website.
15. Click Yes, I am willing to participate (Recommended).
16. Click OK.
17. Close Internet Explorer.
You configure SharePoint in the next exercise.
f Task 1B: Perform a scripted configuration of SharePoint Server

1.
In the task bar, hold the SHIFT key and right-click Windows PowerShell, and then click Run as
administrator.
2.
3.
Click Yes.
D:\Labfiles\Lab01\ConfigureSharePoint.ps1
The Windows PowerShell Credential Request dialog box appears to prompt you for the credentials of
the CONTOSO\SP_Farm account.
4.

A prompt appears to enter the farm passphrase.
5.
Type 10174_SharePoint_2010, and then press ENTER.

After a few moments, configuration status will be displayed. Configuration proceeds for 7-10 minutes.
The following warning is expected during the configuration of SharePoint:
The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.
The local farm does not yet exist. It will be created by the configuration script.
You can monitor the progress of the SharePoint installation by performing these steps:
a.
b.
6.
7.
Open Task Manager, click the Processes tab, and then select the Show processes from all
users check box.
Monitor processes including powershell.exe, sqlservr.exe, and owstimer.exe.
When prompted Press Enter to exit, press ENTER.

You will configure SharePoint in a later lab.
10

1.
Start SharePoint 2010 Central Administration:

a.
SharePoint 2010 Central Administration.
A User Account Control message appears.

2.
Click Yes.
After a few moments, Central Administration opens.
3.
4.
5.
6.
7.
8.
9.
In the Central Administration Quick Launch, click Configuration Wizards.

On the Configure your SharePoint farm page, click Start the Wizard.
In the Services section, observe the list of service applications that will be created by the Farm
Configuration Wizard.
10. Clear the User Profile Service Application check box.
11. Click Next.
Farm service applications are created and started. This takes several minutes. Optionally, you can
open SQL Server Management Studio and refresh the view of the Databases node to monitor the
creation of service application databases.
When the configuration is complete, the Create Site Collection page opens.
12. On the Create Site Collection page, click Skip.
You will create an intranet in the following exercises.
13. On the Initial Farm Configuration Wizard page, click Finish.
11
Exercise 6 (Optional): Installing a Language Pack

f Task 1: Install the French language pack
1.
Double-click D:\Software\SharePointLanguagePackFR\ServerLanguagePack.exe.
2.
3.
4.
Click Yes.
Select the Jaccepte les termes de ce contrat check box.
Click Continuer.
The language pack installs.
5.
6.
On the Excuter lAssistant Configuration page, clear the Excuter lAssistant Configuration des
produits SharePoint check box.
Click Fermer.
f Task 2: Complete the configuration of the language pack

1.
Click Start, then click All Programs, then click Microsoft SharePoint 2010 Products, and then click
2.
Click Yes.
After a few minutes, the SharePoint 2010 Products Configuration Wizard appears.
3.

4.
Click Yes.
The farm is configured.
5.
On the Configuration Successful page, click Finish.

SharePoint 2010 Central Administration opens.
f Task 3: Validate the Installation of the language pack

1.
2.
In SharePoint 2010 Central Administration, in the Quick Launch, click System Settings.
In the Servers section, click Manage servers in this farm.
The Servers in Farm page appears.
3.
Confirm that SP2010-WFE1 has the Language Pack for SharePoint, Project Server, and Office
Web Apps 2010 - French/Franais installed.

following steps:
1.
2.
3.

Lab Answer Key: Creating a SharePoint 2010 Intranet
Module 2
Contents:
Lab: Creating a SharePoint 2010 Intranet

1.
2.
Start 10174A-CONTOSO-DC-B.
After CONTOSO-DC has completed startup, start 10174A-SP2010-WFE1-B.

f Task 1: Create a new Web application
1.
2.

3.
4.
5.
6.
Click Yes.
In the Central Administration Quick Launch, click Application Management.
In the Web Applications section, click Manage web applications.
On the Web Applications tab of the ribbon, click New.
The Create New Web Application page opens.
7.
In the Authentication section, select Classic Mode Authentication.

Microsoft SharePoint can now use Claims Based Authentication, which is discussed in Module 5.
8.
9.
10.
11.
12.
In the IIS Web Site section, in the Port box, type 80.
In the Host Header box, type intranet.contoso.com.
Make no changes to the Security Configuration and Public URL sections.
In the Application Pool section, ensure that Create new application pool is selected.
In the Application pool name box, type SharePoint Web Applications.
You should use a meaningful, descriptive name for each application pool that you create.
13. In the Application Pool section, under Select a security account for this application pool, in the
Configurable list, select CONTOSO\SP_ServiceApps.
14. In the Database Name and Authentication section, in the Database Name box, type
WSS_Content_Intranet.
You should always use a meaningful name for your content databases.
15. Click OK.
The Web application and content database will be created. When it is complete, the Application
Created page opens.
16. Click OK.
The new Web application is displayed on the Web Applications Management page.

1.
2.
3.

In the Site Collections section, click Create site collections.
In the Web Application section, confirm that http://intranet.contoso.com is selected.
If not, click the button, then click Change Web Application, and then click SharePoint
4.
5.
6.
7.
8.
In the Title box, type Contoso Intranet.

In the Web Site Address section, confirm that the address is http://intranet.contoso.com/.
In the Template Selection section, click the Publishing tab, and then click Publishing Portal.
In the Primary Site Collection Administrator section, in the User name box, type
CONTOSO\SP_Admin.
Click OK.
The site collection is created, and the Top-Level Site Collection page opens.
9.
Click OK.
f Task 2: Attempt to open the new site
In Windows Internet Explorer, in the address bar, type http://intranet.contoso.com and then press
ENTER.
An Internet Explorer cannot display the webpage error page is displayed.

Answer: The browser cannot resolve the name intranet.contoso.com. There is no DNS record for
intranet.contoso.com.
1.
Click Start, then point to Administrative Tools, then hold the SHIFT key and right-click DNS and
then click Run as different user.
2.
3.
4.
5.
In the User name box, type CONTOSO\Administrator.

Expand CONTOSO-DC, then expand Forward Lookup Zones, and then click contoso.com.
Right-click contoso.com and then click New Host (A or AAAA).
The New Host dialog box appears.
6.
7.
8.
9.
10.
11.
In the Name box, type intranet.

In the IP address box, type 10.0.0.21.
Click Add Host.
Click OK.
Click Done.
Close DNS Manager.
f Task 4: Open the new site

1.
In Internet Explorer, in the address bar, type http://intranet.contoso.com and then press ENTER.
An Internet Explorer cannot display the webpage error is displayed. If this error does not appear on
your system, continue to the next task.
Answer: The DNS client has cached the negative resolution of intranet.contoso.com.
2.
3.
4.
5.
Click Start, and then click Command Prompt.

Type ipconfig /flushdns, and then press ENTER.
Close Command Prompt.
The Web site begins to load. Because this is the first time that the site has been requested from the
server, it must be compiled. This takes several seconds.
The intranet Web application opens.
f Task 5: Create a publishing site page

1.
On the Contoso intranet site, click Site Actions, and then click New Page.
The New Page page opens.
2.
3.
4.
5.
In the New page name box, type Important Phone Numbers.

Click Create.
In the Page Content area, type In case of emergency, call 911.
In the ribbon, click Save & Close.
The page is displayed.
f Task 6: Configure permissions

1.
2.
3.
4.
Click Site Actions, and then click Site Permissions.

In the Groups list, click the Contoso Intranet Visitors link.
Click the New arrow, and then click Add Users.
In the Users/Groups box, type CONTOSO\Domain Users and then click OK.
All users with Active Directory accounts in the CONTOSO domain can now access the intranet site.

f Task 1: Create a content database
1.
2.
3.
4.

5.
6.

In the Database Name box, type WSS_Content_Intranet_IT, and then click OK.
f Task 2: Create a site collection in a specific content database

1.
2.
3.

In the Site Collections section, click Create site collections.
4.
5.
In the Title box, type Information Technology.

In the Web Site Address section, ensure that sites is selected in the Site Prefix list, and then type IT
in the Site Name text box.
The result will be the URL for the site collection: http://intranet.contoso.com
/sites/IT.
6.
7.
8.
In the Template Selection section, ensure that the Team Site site definition is selected.
CONTOSO\SP_Admin.
Click OK.
The Top-Level Site Successfully Created page appears.
9.
Click OK.
f Task 3: Examine the information technology Web site

1.
Open a new tab of the browser, and then type http://intranet.contoso.com

/sites/IT in the address bar. Press ENTER.
The Information Technology site opens.
2.
Spend some time reviewing and experimenting with the new site. You can make changes to the site,
but those changes will not persist after this lab.

following steps:
1.
2.
3.

Lab Answer Key: Administering and Automating SharePoint
Module 3
Contents:
Lab A: Automating SharePoint with Windows PowerShell
Exercise 2: Delegating the Ability to Use Windows PowerShell to

Manage SharePoint

Lab A: Automating SharePoint with Windows

PowerShell
1.
2.
Start 10174A-CONTOSO-DC-C
After CONTOSO-DC has completed startup, start 10174A-SP2010-WFE1-C.

f Task 1: Load SharePoint .dll files using .NET reflection
1.
2.

In the Windows Quick Launch, click Windows PowerShell.
Windows PowerShell opens.
3.
ENTER:
Microsoft.SharePoint.dll is not in the list. To use the Microsoft SharePoint object model, you must
load the SharePoint .dll files.
4.

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
The output displays global assembly cache (GAC), version, and location information for the assembly.
5.
Repeat step 3 to display the loaded assemblies.
Tip: You can press the UP ARROW to scroll through previously executed commands.
The listing includes the Microsoft.SharePoint.dll.
f Task 2: Add the SharePoint snap-in using the Add-PSSnapin cmdlet

1.

Get-PSSnapin
not listed.
2.

Get-PSSnapin Registered
The output lists the snap-ins that are registered on the system, except for those that are installed with
Windows PowerShell.
3.
4.

Get-PSSnapin
now added.
5.
ENTER:
The listing includes numerous SharePoint assemblies.

Rather than loading each assembly one by one, the Add-PSSnapin cmdlet loads them all at once.
6.
f Task 3: Open SharePoint 2010 Management Shell

1.
2.
SharePoint 2010 Management Shell.
Get-PSSnapin
already added to the session.
3.
ENTER:
The listing demonstrates that SharePoint 2010 Management Shell preloads the SharePoint .dll files.
Exercise 2: Delegating the Ability to Use Windows PowerShell to Manage

SharePoint
f Task 1: Attempt to use Windows PowerShell to enumerate webs
1.
In SharePoint 2010 Management Shell, type the following command and the press ENTER:
2.
To enumerate all of the webs in the site collection, type the following command and then press
ENTER:
$spsite | Get-SPWeb
An error appears, indicating that login failed. The SP_Admin user account does not have the
permissions required to access the information about the intranet site collection with Windows
PowerShell.
f Task 2: Configure least privilege rights to manage SharePoint with Windows PowerShell
1.
Click Start, click All Programs, click Microsoft SharePoint 2010 Products, hold down the SHIFT key
and right-click SharePoint 2010 Management Shell, and then click Run as different user.
2.
3.
4.
5.

Click OK.
Type the following commands each followed by ENTER:
$spcdb = Get-SPContentDatabase WSS_Content_Intranet
Add-SPShellAdmin -UserName CONTOSO\SP_Admin -Database $spcdb
6.
Close the Administrator SharePoint Management Shell.

f Task 1: Use Windows PowerShell to report Web properties
1.
2.

3.
To enumerate all of the webs in the site collection, type the following command and then press
ENTER:
$spsite | Get-SPWeb
4.
To enumerate all of the webs in the site collection using the AllWebs collection, type the following
$spsite.AllWebs
5.
To list specific properties of the webs, type the following command and then press ENTER:
$spsite.AllWebs | Select LastItemModifiedDate, Url, Created | Sort Created
f Task 2: Attempt to use the Grid-View to report site collection properties

1.
Get-SPSite
2.

($_.Quota.StorageMaximumLevel/1000000)} }
The listing displays various properties of each site collection.

3.

installed.
f Task 3: Install the Windows PowerShell Integrated Scripting Environment

1.

An error indicates that you must run the command with elevated rights.
2.
Right-click the Windows PowerShell icon in the Windows taskbar, and then click Run as
Administrator.
A User Account Control message appears.
3.
4.
Click Yes.
5.
Close Administrator: Windows PowerShell.
f Task 4: Use the Grid-View to report site collection properties

1.
In SharePoint 2010 Management Shell, press the UP ARROW several times until you see the
command you typed in Task 2, and then press ENTER to rerun the command:
installed. This occurs because you must close and reopen SharePoint 2010 Management Shell to load
the component.
2.
3.
4.

Type the following command and then press ENTER, which is the same as the command you
executed in step 1:
A Grid-View window appears displaying the output of the command.

5.
Close the Sites With Usage window.

f Task 1: Create a single site collection using Windows PowerShell
1.

New-SPContentDatabase -Name WSS_Content_Intranet_Sales -WebApplication
$spsite = New-SPSite -Url "http://intranet.contoso.com/sites/Sales" -ContentDatabase
WSS_Content_Intranet_Sales -OwnerAlias CONTOSO\SP_Admin -Template "STS#0"
A site collection and top-level web for the Sales department is created using the Team Site site
definition.
2.
3.
Open Windows Internet Explorer.

In the address bar, type http://intranet.contoso.com/sites/Sales, and then press ENTER.
The Sales site opens.
4.
Minimize Internet Explorer.
f Task 2: Create multiple site collections using Windows PowerShell

1.
In SharePoint 2010 Management Shell, type the following script. On the last line, press ENTER to
create a blank line. This causes the script to execute.
$i = ("HR", "Marketing")
ForEach($url in $i)
{
New-SPContentDatabase -Name WSS_Content_Intranet_$url -WebApplication
New-SPSite -Url http://intranet.contoso.com/sites/$url -ContentDatabase
WSS_Content_Intranet_$url -OwnerAlias CONTOSO\SP_Admin -Template "STS#0"
}
Two new content databases, site collections, and top-level webs are created.
2.
Get-SPSite
The output lists the new site collections.

f Task 1: Modify a list item using Windows PowerShell
1.
2.
3.
4.

In the Sales site Quick Launch, click All Site Content, and then click Announcements.
Observe the title of the only item in the list.
Switch to SharePoint 2010 Management Shell, and then type the following commands:
$gc = Start-SPAssignment
$spsite = $gc | Get-SPSite "http://intranet.contoso.com/sites/Sales"
$splist = $spsite.rootweb.lists["Announcements"]
$splistitem = $splist.items[0]
$splistitem["Title"] = "Our SharePoint 2010 Sales site is now live!"
$splistitem.update()
$gc | Stop-SPAssignment
The list item will be updated. Notice that you did not use a cmdlet to update a list item. There are
things that will require direct access to the object model and, as such, you need to be careful to
dispose of objects you create.
5.
6.
7.
Switch to Internet Explorer, and then press F5 to refresh the view of the Announcements list.
Observe the updated title of the announcement.

f Task 1: Display Stsadm Help documentation
1.
Click Start, click All Programs, click Microsoft SharePoint 2010 Products, right-click SharePoint
2010 Management Shell, and then click Run as administrator.
2.
3.
Click Yes.
stsadm
Examine the output of the command, which includes a list of the numerous operations supported by
Stsadm. Also notice the examples displayed at the end of the Help documentation.
4.
To display Help documentation for the enumsites operation, type the following command and then
press ENTER:
stsadm help enumsites
f Task 2: Enumerate site collections in a Web application using Stsadm

1.
stsadm -o enumsites -url "http://intranet.contoso.com"
Review the Extensible Markup Language (XML) response that you get from the command, and note
that this can be used in a Windows PowerShell script to iterate through all your site collections.
2.
Get-SPSite "http://intranet.contoso.com" | Get-SPWeb
3.
Repeat steps 1 and 2, and observe the amount of time it takes for each command to execute.
f Task 3: Create an Operations site collection using Stsadm

1.

stsadm -o createsite -url "http://intranet.contoso.com/sites/Operations" -ownerlogin
CONTOSO\SP_Admin -owneremail sharepoint@contoso.com
A new Operations site collection is created.

2.
3.
Open Internet Explorer.

In the address bar, type http://intranet.contoso.com/sites/Operations, and then press ENTER.
The Template Selection page appears.
4.
5.
Select the Team Site template.

Click OK.
The site is created using the Team Site site definition.
10
6.
On the Set Up Groups for this Site page, click OK.
f Task 4: Create an Operations Maintenance site using Stsadm

1.
Switch to SharePoint Management Shell, and then type the following command:
stsadm -o createweb -url "http://intranet.contoso.com/sites/Operations/Maintenance"
A new web called Maintenance is created in the Operations site collection.

2.
3.

In the address bar, type http://intranet.contoso.com/sites/Operations
/Maintenance, and then press ENTER.
The Template Selection page appears.
4.
Select the Team Site template, and then click OK.
f Task 5: Configure the site collection administrator using Stsadm

1.
Click the SharePoint Administrator menu in the upper-right corner of the page, and then click Sign
in as Different User.
2.
3.

In the Password box, type Pa$$w0rd, and then click OK.
An Error: Access Denied page appears.
4.
Switch to SharePoint2010 Management Shell, and then type the following command:
stsadm -o siteowner -url "http://intranet.contoso.com/sites/Operations" -ownerlogin
CONTOSO\Administrator
5.
Switch to Internet Explorer, type http://intranet.contoso.com/sites

/Operations/Maintenance in the address bar, and then press ENTER.
You can now access that site collection as CONTOSO\Administrator.
6.

following steps:
1.
2.
3.

Lab Answer Key: Configuring Content Management
Module 4
Contents:
Lab A: Configuring List Throttling and Remote BLOB Storage

10
Lab A: Configuring List Throttling and Remote

BLOB Storage
1.
2.

f Task 1: Create a computer inventory list
1.
2.
3.

Start Windows Internet Explorer.
In the address bar, type http://intranet.contoso.com/sites/IT, and then press ENTER.
The Information Technology site opens.
4.
5.
6.
7.
8.
Click Site Actions, and then click More Options.

In the Filter By panel, click Blank & Custom.
Click Custom List.
In the Name box, type ComputerInventory.
Click Create.
The list is created with the URL http://intranet.contoso.com/sites/IT/Lists/ComputerInventory.
9.
Click the List tab, and then click List Settings.

The List Settings page opens.
10.
11.
12.
13.
14.
Click Title, description and navigation.

In the Name box, type Computer Inventory, with a space.
Click Save.
In the navigation breadcrumb, click Computer Inventory.
Click the List tab, and then click Create Column.
The Create Column page opens.
15. In the Column name box, type Computer Name, and then click OK.
16. Click the List tab, and then click Create Column.
The Create Column page opens.
17. In the Column name box, type Serial Number, and then click OK.
f Task 2: Configure least privilege rights to manage SharePoint using Windows

PowerShell
1.
2.
3.
Click Start, click All Programs, click Microsoft SharePoint 2010 Products, hold down the SHIFT key
and right-click SharePoint 2010 Management Shell, and then click Run as different user.
Enter the user name CONTOSO\Administrator and the password Pa$$w0rd, and then click OK.
Type the following command, and then press ENTER.
Add-SPShellAdmin -UserName CONTOSO\SP_Admin -Database (Get-SPContentDatabase
"WSS_Content_Intranet_IT" )
4.
Close the Windows PowerShell window.
f Task 3: Create a large list using Windows PowerShell

1.
2.

To create 4,000 items in the new list, type the following commands:
$i = 1
do {
#add item
$newitem.Update()
$i++
}
while ($i -le 4000)
$web.dispose()
$site.dispose()
Web.
f Task 4: Observe the list view threshold

1.
2.
3.
4.

Verify that the List view threshold message indicates that the list contains 4,000 items.
In the navigation breadcrumb, click Computer Inventory.
f Task 5: Add items to exceed the list threshold

1.
2.

To create 5,000 additional items in the Computer Inventory list, type the following commands:
$i = 4001
do {
#add item
$newitem.Update()
$i++
}
while ($i -le 9000)
$web.dispose()
$site.dispose()
Web.
f Task 6: Experience list throttling

1.
2.
3.
4.
5.

Press F5 to refresh the Computer Inventory list.
Verify that the List view threshold message indicates that the list contains 9.000 items.
In the Permissions and Management section, click Delete this list.
A confirmation dialog appears.
6.
Click OK.
An Error page appears that indicates the operation is prohibited because it exceeds the list view
threshold.
7.
8.
9.

In the Quick Launch, click Computer Inventory.
Point at the Title column header, and then click the drop-down arrow that appears.
A message appears: Cannot show the value of the filter. The field may not be filterable, or the number
of items returned exceeds the list view threshold enforced by the administrator.
10. Click OK.
f Task 7: Configure list throttling

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.

The User Account Control dialog appears.
Click Yes.
In the Application Management section, click Manage web applications.
The Web Applications Management page opens.
Click SharePoint intranet.contoso.com80.
On the ribbon, click the General Settings drop-down arrow, and then click Resource Throttling.
The Resource Throttling page opens.
In the List View Threshold box, type 10000, and then click OK.
Switch to the instance of Internet Explorer that displays the Computer Inventory list.
Press F5 to refresh the page.
Point at the Title column header, and then click the drop-down arrow that appears.
Verify that the Show Filter Choices command is now available.
Switch to Central Administration.
On the ribbon, click the General Settings drop-down arrow, and then click Resource Throttling.
In the List View Threshold box, type 7000.
Select the Enable a daily time window for large queries check box.
In the Start time list, select 11pm.
In the Duration list, select 5 hours, and then click OK.
Switch to the instance of Internet Explorer that displays the Computer Inventory list.
Verify that the List view threshold is 7000.

f Task 1: Enable FILESTREAM on the computer running SQL Server
1.
Click Start, click All Programs, click Microsoft SQL Server 2008 R2, click Configuration Tools, hold
down the SHIFT key and right-click SQL Server Configuration Manager, and then click Run as
different user.
The Windows Security dialog appears.
2.
In the User name box, type CONTOSO\Administrator. In the Password box, type Pa$$w0rd. Then,
click OK.
3. SQL Server Services.
4. Right-click SQL Server (MSSQLServer), and then click Properties.
5. Click the FILESTREAM tab.
6. Select the Enable FILESTREAM for Transact-SQL access check box.
7. Select the Enable FILESTREAM for file I/O streaming access check box.
8. Select the Allow remote clients to have streaming access to FILESTREAM data check box, and
then click OK.
9. Close SQL Server Configuration Manager.
10. Click Start, click All Programs, click Microsoft SQL Server 2008 R2, hold down the SHIFT key and
right-click SQL Server Management Studio, and then click Run as different user.
11. In the User name box, type CONTOSO\Administrator. In the Password box, type Pa$$w0rd. Then,
click OK.
12. Confirm that the Server name is SP2010-WFE1, and then click Connect.
13. In Object Explorer, right-click SP2010-WFE1, and then click Properties.
14. In the Select a page section, click Advanced.
15. Click Filestream Access Level, click the drop-down arrow, and then click Full access enabled. Click
OK.
A message appears indicating that you must restart Microsoft SQL Server. Click OK.
16. In Object Explorer, right-click SP2010-WFE1, and then click Restart.
A confirmation dialog appears.
17. Click Yes.
f Task 2: Provision a BLOB store

1.
2.
In Microsoft SQL Server Management Studio, expand Databases, and then click
Click the New Query button on the toolbar.
The Query Editor opens a new query in the details pane.
3.
To set the database master key, type the following query into the Query Editor:
use [WSS_Content_Intranet_IT]
if not exists (select * from sys.symmetric_keys where name =
N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Master Key
Pa$$w0rd'
4.
Click the Execute button on the toolbar.
5.

6.
To enable a new filegroup for your Remote BLOB Storage (RBS) provider, type the following query
into the Query Editor:
if not exists (select groupname from sysfilegroups where
groupname=N'RBSFilestreamProvider')alter database [WSS_Content_Intranet_IT]
add filegroup RBSFilestreamProvider contains filestream
7.
8.
Click the Execute button on the toolbar.

9.
To add a file system mapping for your RBS provider, type the following query into the Query Editor:
alter database [WSS_Content_Intranet_IT] add file (name = RBSFilestreamFile, filename
= 'c:\Blobstore') to filegroup RBSFilestreamProvider
10. Click the Execute button on the toolbar.

f Task 1: Install RBS on the first Web server
1.
Click Start, right-click Command Prompt, and then click Run as administrator.
2.
3.
Click Yes.
Type the following commands, and then press ENTER.
cd d:\labfiles\lab04
d:
4.

msiexec /qn /lvx* rbs_install_log1.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true
FILEGROUP=PRIMARY DBNAME="WSS_Content_Intranet_IT" DBINSTANCE="SP2010-WFE1"
FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
5.
Wait one minute for the operation to complete.
f Task 2: Confirm the installation of RBS

1.
2.
Open the D:\Labfiles\Lab04\rbs_install_Log1.txt file.

Confirm that you see the following line within the last 20 lines of the end of the file:
Product: SQL Server 2008 R2 Remote Blob Store -- Installation completed successfully.
3.
4.
5.
6.
7.
8.
Close rbs_install_log1.
Switch to Microsoft SQL Server Management Studio.
In Object Explorer, right-click the root node SP2010-WFE1, and then click Refresh.
Expand Databases, expand WSS_Content_Intranet_IT, and then expand Tables.
Verify that several tables exist with names that begin with the letters mssqlrbs.
Close SQL Server Management Studio. When prompted to save changes, click No.
f Task 3: Enable RBS for a content database

1.
2.

To enable RBS in a specific content database, type the following commands:
$rbss.Installed()
$rbss.Enable()
$rbss.SetActiveProviderName($rbss.GetProviderNames()[0])
$rbss
f Task 4: Test the RBS provider

1.
Open the C:\BlobStore folder.

A message appears indicating that you need permission to access the folder.
2.
Click Continue.
The Blobstore folder opens.
3.
Observe the number of items in the folder.
4.
5.
6.
7.
8.
9.
10.
11.
12.

In the Quick Launch, click Shared Documents.
Click Add document.
Click Browse.
Navigate to the D:\LabFiles\Lab04 folder, select rbs_install_log1, and then click Open. Click OK.
Switch to the Windows Explorer window showing the Blobstore folder.
Observe that a new folder has been added to the Blobstore folder.
Open the folder with the most recent modified date, open the folder inside, and then open the file
with the most recent modified date.
13. Examine the contents of the file to verify that this is the rbs_install_log1 file.
14. Close Notepad.

f Task 1: Configure the minimum BLOB storage size
1.
2.

To configure the MinimumBlobStorageSize property to 1 Megabyte (Mbyte), type the following
commands:
$rbss.MinimumBlobStorageSize = 1048576
$cdb.update()
f Task 2: Validate the behavior of minimum BLOB storage size

1.
2.
3.
4.

Click Add document.
Click Browse.
Navigate to the D:\LabFiles\Lab04 folder, select SharePoint_2010_Walkthrough_Guide.pdf, and
then click Open. Click OK.
5. Click Add document.
6. Click Browse.
7. Navigate to the D: \LabFiles\Lab04 folder, select SharePoint_2010_Datasheet.pdf, and then click
Open. Click OK.
8. Switch to the Windows Explorer window showing the Blobstore folder.
9. Verify that a new file representing SharePoint_2010_Walkthrough_Guide.pdf has appeared, and
observe its Date modified.
10. Verify that there is not a file representing SharePoint_2010_Datasheet.pdf with a Date modified
after the date of SharePoint_2010_Walkthrough_Guide.pdf.
11. Close all open applications and windows.
10

f Task 1: Assign Term Store Administrators
1.
2.
3.
4.
5.
6.

Click OK.
In the Application Management section, click Manage service applications.
Click the Managed Metadata Service link.
The Term Store Management Tool opens.
In the Term Store Administrators box, type CONTOSO\SP_Admin.
Click Save.
f Task 2: Create a group, a term set, and terms

1.
2.
3.
4.
5.
6.
7.
8.
9.
Under Taxonomy Term Store, point at Managed Metadata Service, click the drop-down arrow
that appears, and then click New Group.
Type Organization, and then press ENTER.
Point at Organization, click the drop-down arrow, and then click New Term Set.
Type Department, and then press ENTER.
Point at Department, click the drop-down arrow, and then click Create Term.
Type Marketing, and then press ENTER.
Type Finance, and then press ENTER.
Type IT, and then press ENTER.
Type Sales, and then press ENTER.
f Task 3: Add a managed metadata column to a list

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Open a new tab in Internet Explorer.

In the Quick Launch, click All Site Content.
Click Create.
Click Custom List.
In the Name box, type SupportRequests.
Click Create.
In the Column name box, type User Name, and then click OK.
In the Column name box, type Department.
In the list of column types, click Managed Metadata.
In the Term Set Settings section, expand Managed Metadata Service, expand Organization, and
then click Department. Click OK.
In the Column name box, type Request Type.
In the list of column types, click Managed Metadata.
In the Term Set Settings section, click Customize your term set.
Click Edit Using Term Set Manager.
A message box appears.
19. Click OK.
The Term Store Management Tool opens in a new window.

20. Confirm that Submission Policy is configured as Open.
21. Close Term Store Management Tool.
f Task 4: Add items with managed metadata

1.
2.
3.
4.
Click the Items tab, and then click New Item.

In the Title box, type Create a new account for Andy Ruth.
In the User Name box, type AndyR.
In the Department box, type Fin.
The Suggestions list appears and displays Finance.
5.
6.
Press ENTER to accept the suggestion.

In the Request Type box, type New User, and then press ENTER.
New User is displayed with a red, dashed underline. This indicates that the term does not exist.
7.
8.
9.
10.
11.
12.
Click the Browse for a valid choice button next to the Request Type box.
Click Add New Item.
Type New User, and then press ENTER.
Click Select, and then click OK.
Click Save.
Repeat the steps in this task to create the following support requests:
Title
User Name
Department Request Type
Reset password for Christa Geller
ChristaG
IT
Password Reset
Problem starting computer
FrankM
Marketing
Desktop Support
Create a new account for Sean Chai
SeanC
Sales
New User
Reset password for Lola Jacobsen
LolaJ
Sales
Password Reset
f Task 5: Configure metadata navigation

1.
2.
3.
4.
5.
6.
7.
8.

In the General Settings section, click Metadata navigation settings.
In the Available Hierarchy Fields list, click Department, and then click Add.
In the Available Hierarchy Fields list, click Request Type, and then click Add.
In the Selected Hierarchy Fields list, click Folders, and then click Remove. Click OK.
In the Quick Launch, click SupportRequests.
Observe the tree view below the Quick Launch.
Click the terms in the Department and Request Type term sets to filter the list.

following steps:
1.
2.
3.

11
Lab Answer Key: Configuring Authentication
Module 5
Contents:
Exercise 2: Creating a Web Application That Uses Claims-Based

Authentication

10

1.
2.

f Task 1: Create an ASP.NET membership database
1.
2.

Click Start, then right-click Command Prompt, and then click Run as administrator.
3.
4.
Click Yes.
cd c:\windows\microsoft.net\framework\v2.0.50727
aspnet_regsql.exe
The ASP.NET SQL Server Setup Wizard appears.

5.
6.
7.
8.
9.
On the Welcome page, click Next.

On the Select a Setup Option page, click Next.
On the Select the Server and Database page, click Next.
On the Confirm Your Settings page, click Next.
On the The database has been created or modified page, click Finish.
f Task 2: Configure the connection to the database

1.

cd c:\windows\microsoft.net\framework\v2.0.50727\config
notepad machine.config
2.
Modify the connectionStrings element of the XML file to match the following:
<connectionStrings>
<clear/>
<add name="LocalSQLServer"
connectionString="Server=.;Database=aspnetdb;uid=sa;pwd=Pa$$w0rd;"
providerName="System.Data.SqlClient"/>
</connectionStrings>
3.
4.
5.

Close Notepad.
In Administrator: Command Prompt, type the following commands:
cd c:\windows\microsoft.net\framework64\v2.0.50727\config
notepad machine.config
6.
Repeat steps 2-4.
f Task 3: Create users

1.
Click Start, click All Programs, click Microsoft SharePoint 2010 Products, right-click SharePoint
2010 Management Shell, and then click Run as administrator.
2.
3.
Click Yes.
Execute the following commands:
$member.CreateUser('SiteAdministrator', 'Pa$$w0rd', 'SharePoint@contoso.com', 'first
person kissed', 'mom', $true, $id, [ref] $status)
4.

$status
5.
6.
Verify that the result is Success.

$member.CreateUser('JamesF', 'Pa$$w0rd', 'JamesF@tailspintoys.com', 'favorite pet',
'Spot', $true, $id, [ref] $status)
7.

$status
8.
9.

f Task 4: Enable the secure token service to use forms-based authentication

1.
In Administrator: Command Prompt, type the following commands:

cd "c:\program files\common files\microsoft shared\web server
extensions\14\webservices\root"
notepad web.config
2.
3.
4.
5.
6.
7.
8.
Locate the <system.web> element, then locate the <membership> element, and then locate the
<providers> element.
Remove the <clear/> directive inside the <providers> element.
Locate the <roleManager> element, and then locate the <providers> element.
Remove the <clear/> directive inside the <providers> element.
Close Notepad.
Exercise 2: Creating a Web Application that Uses Claims-Based Authentication

f Task 1: Create a Web application that uses both Windows and forms-based
authentication
1.

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Click Yes.
In the Application Management section, click Manage web applications.
On the ribbon, click New.
In the Authentication section, click Claims Based Authentication.
In the Port box, type 80.
In the Host Header box, type clients.contoso.com.
In the Claims Authentication Types section, select the Enable Windows Authentication and
Integrated Windows Authentication check boxes, and then select NTLM from the drop-down list.
Select Enable Forms Based Authentication (FBA).
In the ASP.NET Membership provider name box, type AspNetSqlMembershipProvider.
In the ASP.NET Role manager name box, type AspNetSqlRoleProvider.
In the Application Pool section, click Use existing application pool, and then select SharePoint
80 (CONTOSO\SP_ServiceApps) from the drop-down list.
For the database name, type WSS_Content_Clients.
Click OK.
Central Administration provisions the new Web application.
15.
16.
17.
18.
On the Application Created page, click the Create Site Collection link.
In the Title box, type CONTOSO Client Portal.
In the Template Selection section, click the Publishing tab, and then click Publishing Portal.
In the Primary Site Collection Administrator section, in the User name text box, type
CONTOSO\SP_Admin.
19. In the Secondary Site Collection Administrator section, type SiteAdministrator.
20. Click OK.
The Top-Level Site Successfully Created dialog box appears.
21. Click OK.
1.
Click Start, then click to Administrative Tools, then hold SHIFT and right-click DNS, and then select
2.
3.
4.
5.

Expand CONTOSO-DC, then expand Forward Lookup Zones, and then click contoso.com.
Right-click contoso.com, and then click New Host (A or AAAA).
The New Host dialog box appears.
6.
7.
8.
In the Name box, type clients.

In the IP address box, type 10.0.0.21.
Click Add Host.
9. Click OK.
10. Click Done.
11. Close DNS Manager.
f Task 3: Test claims-based authentication

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

In the address bar, type http://clients.contoso.com, and then press ENTER.
On the Sign In page, select Forms Authentication from the drop-down list.
In the User name box, type SiteAdministrator.
Click Sign In.
Verify that you are authenticated as SiteAdministrator.
Click SiteAdministrator in the upper-right corner of the page.
Click Sign in as Different User.
On the Sign In page, select Windows Authentication from the drop-down list.
11.
12.
13.
14.
15.
In the User name box, type CONTOSO\SP_Admin.

Click OK.
Verify that you are authenticated as SharePoint Administrator.
Lab Review
Question: Why must you remove the <clear/> elements from the Web.config file?
Answer: The <clear/> elements prevent the SharePoint Secure Token service from finding users in the
forms-based authentication database. The service cannot build claims for the users, and authentication
would fail.
Question: If you are familiar with the configuration of forms-based authentication on Microsoft Office
SharePoint Server 2007, what is different about the number and type of Web applications required to
support forms-based authentication in Microsoft SharePoint Server 2010 in the client extranet scenario
presented in this lab?
Answer: Microsoft Office SharePoint Server 2007 required a separate, extended Web application to
support forms-based authentication. In SharePoint Server 2010, claims-based authentication accepts
claims from multiple authentication mechanisms, including both Windows and forms-based
authentication. Therefore, only one Web application is required to support this scenario.

1.
On SP2010-WFE1, click Start, then click Administrative Tools, then hold the SHIFT key and rightclick Active Directory Users and Computers, and then select Run as different user.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

Click OK.
Expand contoso.com, and then click Users.
Right-click Users, then point to New, and then click User.
In the Full name box, type Excel Unattended Service Account.
In the User logon name box, type SP_Excel_USA.
Click Next.
In the Password and Confirm password boxes, type Pa$$w0rd.
Clear the User must change password at next logon check box.
Select the Password never expires check box.
Click Next.
Click Finish.
Repeat steps 6-14 to create the following accounts:
Full name: Performance Point Unattended Service Account, User logon name:
SP_PerfPoint_USA.
Full name: Visio Graphics Unattended Service Account, User logon name: SP_Visio_USA.
16. Close Active Directory Users and Computers.

f Task 1: Initialize an instance of a Secure Store Service application
1.
2.
3.
4.
5.
6.
7.
Open SharePoint 2010 Central Administration. At the User Account Control dialog box, click Yes.
In the Service Applications section, click Manage service applications.
Click the Secure Store Service link on the Secure Store Service Application row.
On the ribbon, click Generate New Key.
In the Pass Phrase and Confirm Pass Phrase boxes, type 10174_SSS_2010.
Click OK.
f Task 2: Create a target application for Excel Services

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

In the Target Application ID box, type ExcelUnattendedSA.
In the Display Name box, type Excel Unattended Service Account.
In the Contact E-mail box, type sharepoint@contoso.com.
In the Target Application Type list, select Group.
In the Target Application Page URL section, click None.
Click Next.
On the Add Field page, click Next.
In the Target Application Administrators box, type CONTOSO\SP_Admin.
In the Members list, type Domain Users.
Click OK.
f Task 3: Configure the Secure Store credentials for Excel Services

1.
2.
3.
4.
5.
Select the ExcelUnattendedSA check box.

In the Credentials group of the ribbon, click Set.
In the Windows User Name box, type CONTOSO\SP_Excel_USA.
In the Windows Password and Confirm Windows Password boxes, type Pa$$w0rd.
Click OK.
f Task 4: Create a target application for Visio Graphics

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

In the Target Application ID box, type VisioUnattendedSA.
In the Display Name box, type Visio Unattended Service Account.
In the Contact E-mail box, type sharepoint@contoso.com.
In the Target Application Type list, select Group.
In the Target Application Page URL section, click None.
Click Next.
On the Add Field page, click Next.
In the Target Application Administrators box, type CONTOSO\SP_Admin.
In the Members list, type Domain Users.
Click OK.
f Task 5: Configure the Secure Store credentials for Visio Graphics

1.
2.
3.
4.
Select the VisioUnattendedSA application check box.

In the Credentials group on the ribbon, click Set.
In the Windows User Name box, type CONTOSO\SP_Visio_USA.
In the Windows Password and Confirm Windows Password boxes, type Pa$$w0rd.
5.
Click OK.
10

f Task 1: Configure Excel Services Secure Store account
1.
2.
3.
4.
5.
Click Application Management.

Click Excel Services Application on the line of Excel Services Application Web Service Application.
Click Global Settings.
In the External Data section, in the Application ID box, type ExcelUnattendedSA, and then click
OK.
Excel Services can now use the credentials in Secure Store to render spreadsheets and connect to
external data connections.
f Task 2: Configure PerformancePoint Secure Store account

1.
2.
3.
4.
5.
6.
7.

In the Service Applications section, click Manage services applications.
Click PerformancePoint Service Application.
Click PerformancePoint Service Application Settings.
In the Secure Store and Unattended Service Account section, in the User Name box, type
CONTOSO\SP_PerfPoint_USA.
In the password box, type Pa$$w0rd.
Click OK.
PerformancePoint will create its own Secure Store account based on the information you entered.
f Task 3: Configure Visio Graphics Secure Store account

1.
2.
3.
4.
5.

Click Visio Graphics Service.
Click Global Settings.
On the External Data section, in the Application ID box, type VisioUnattendedSA, and then click
OK.
Visio can now execute diagrams and data connection refreshes using the unattended account

When you finish the lab, set the virtual machines back to their initial state. To do this, complete the
following steps:
1.
2.
3.

Lab Answer Key: Securing Content
Module 6
Contents:
Lab: Configuring Security for SharePoint

Content
Scenario
You have created an intranet on a new Microsoft SharePoint 2010 farm at Contoso, Ltd. You have been tasked
with helping set up users, groups, and permissions on the intranet until governance and training are in place, at
which point permission management will be delegated to site collection administrators. Additionally, you must
configure SharePoint to support the business requirement that the internal security and compliance audit team
has the ability to access all information stored on the intranet.

1.
2.

f Task 1: Add a user to a sites Members group
1.
2.
3.
4.
5.
6.
7.

On the ribbon, click Grant Permissions.
In Users/Groups box, type CONTOSO\SanjayS.
In the drop-down list, select Information Technology Members [Contribute], and then click OK.
You have now added Sanjay Shah, the Contoso chief technology officer (CTO), as a contributor to the
IT intranet Web, which gives him Read and Write permissions.
f Task 2: Verify that the member can sign in

1.
2.
In the address bar of Windows Internet Explorer, type http://intranet.contoso.com/sites/IT,

and then press ENTER.
In the upper-right corner of the page, click SharePoint Administrator, and then click Sign in as
Different User.
3.
4.
5.
6.
7.
8.
In the User name box, type CONTOSO\SanjayS.

In the Quick Launch, click Tasks.
Click Add new item.
In the Title box, type Select SharePoint Governance Team.
Click Save.
f Task 3: Add a user to a sites Visitors group

1.
In the upper-right corner of the page, click Shah, Sanjay, and then click Sign in as Different User.
2.
3.
Click Use another account.

4.
5.
6.
7.
8.

In the groups list, click Information Technology Visitors.
Click the drop-down arrow next to the New button, and then click Add Users.
In the Users/Groups box, type CONTOSO\JeffL, and then click OK.
You have now added Jeff Low, the Contoso vice president of finance, as a visitor to the IT intranet
Web, which gives him Read permission.
f Task 4: Verify that the visitor can sign in

1.
2.
In the tab navigation, click Information Technology.

Different User.
3.
4.
5.
6.
7.

In the User name box, type CONTOSO\JeffL.
Verify that you do not see the Add new item command.
f Task 5: Create a new group and assign it the Design permission level
1.
In the upper-right corner of the page, click Low, Jeff, and then click Sign in as Different User.
2.
3.
4.
5.
6.
7.
8.

On the ribbon, click Create Group.
In the Name box, type Information Technology Designers.
In the About Me box, type Use this group to grant people Design permissions to the SharePoint
site: Information Technology.
9. In the Give Group Permissions to this Site section, select the Design permission level check box.
10. Click Create.

f Task 1: Create a custom permission level to allow viewing Web analytics reports
1.
2.
3.
4.
5.
6.

On the ribbon, click Permission Levels.
Click Add a Permission Level.
In the Name box, type View Usage.
In the description box, type Can see only usage data about this site.
Select the View Web Analytics Data check box.
Note: Additional permissions check boxes are selected automatically.

7.
8.
9.
10.
11.
12.
13.
14.
15.
Click Create.
On the ribbon, click Create Group.
In the Name box, type Usage Monitors.
In the About Me box, type Use this group to grant people permission to view Web Analytics
data for the SharePoint site: Information Technology Dept.
In the Give Group Permission to this Site section, select the View Usage check box.
Click Create.
Click the drop-down arrow next to the New button, and then click Add Users.
In the Users/Groups box, type CONTOSO\LolaJ, and then click OK.
f Task 2: Attempt to view Web analytics reports

1.
2.
In the address bar of Internet Explorer, type http://intranet.contoso.com/sites/IT, and then press
ENTER.
Different User.
3.
4.
5.

In the User name box, type CONTOSO\LolaJ.
An Access Denied error appears.
6.
To open the usage page, click in the address bar, type

http://intranet.contoso.com/sites/it/_layouts/usageDetails.aspx, and then press ENTER.
An Access Denied error appears. This is because although you have permission to access Web
analytics data, you do not yet have permission to view the default application pages that present that
data.
f Task 3: Add a permission to the custom permission level

1.
Click Sign in as Different User.

2.
3.
4.

5.
6.
7.
8.
9.

On the ribbon, click Permission Levels.
Click View Usage.
Select the View Application Pages check box.
Click Submit.
f Task 4: Validate the functionality of the custom permission level

1.
2.
ENTER.
Different User.
3.
4.
5.

6.
In the address bar, type http://intranet.contoso.com/sites/it/_layouts/settings.aspx, and then

press ENTER.
7. Click Site Web Analytics reports.
8. Examine the report, and then click the browsers Back button.
9. Click Site Collection Web Analytics reports.
10. Examine the report, and then click the browsers Back button.
11. Close Internet Explorer.

f Task 1: Add a document and a folder to a library
1.
2.

3.
4.
5.
6.
7.
8.

Click Add document.
Click Browse.
Select the file D:\Labfiles\LAB06\IT Policies and Procedures for SharePoint 2010, click Open, and
then click OK.
9. On the ribbon, click the Documents tab.
10. Click New Folder.
11. In the Name box, type Usage Reports.
12. Click Save.
f Task 2: Assign permissions to a folder

1.
Click the Usage Reports row to select it.

Do not click the Usage Reports link because it will open the folder.
2.
3.
On the ribbon, click Document Permissions.

On the ribbon, click Stop Inheriting Permissions.
A Message from webpage dialog appears.
4.
5.
6.
Click OK.
To select all permissions, click the check box in the column heading row, next to Name.
On the ribbon, click Remove User Permissions.
A Message from webpage dialog appears.
7.
8.
9.
10.
Click OK.
In the Users/Groups box, type CONTOSO\LolaJ.
In the Grant Permissions box, select the Full Control check box, and then click OK.
f Task 3: Verify the behavior of SharePoint permissions

1.
2.
ENTER.
Different User.
3.
4.
5.

6.
In the address bar, type http://intranet.contoso.com/sites/IT/Shared Documents.

The document library opens. You are able to see the Usage Reports folder but not the policies
document.
7.

f Task 1: Add a user to a group
1.
2.
3.
4.
5.
6.
7.
8.
9.
On SP2010-WFE1, click Start, click Administrative Tools, hold down the SHIFT key and right-click
Active Directory Users and Computers, and then select Run as different user.
Enter the user name CONTOSO\Administrator and the password Pa$$w0rd, and then click OK.
Expand the contoso.com domain, and then click the Users container.
Right-click the Users container, point to New, and then click Group.
In the Name box, type SharePoint Content Auditors, and then click OK.
In the details pane, double-click SharePoint Content Auditors.
Click the Members tab.
Click Add.
Type CONTOSO\JimD, click OK, and then click OK again.
f Task 2: Create groups

1.
2.
3.
4.
5.
In the Name box, type SharePoint Full Control Policy, and then click OK.
In the Name box, type SharePoint Deny Policy, and click OK.
f Task 3: Create a Read Web application policy

1.

2. Click Yes.
3. In the Application Management section, click Manage web applications.
4. Click SharePoint - intranet.contoso.com80.
5. On the ribbon, click User Policy.
6. Click Add Users.
7. In the Zones list, select (All Zones).
8. Click Next.
9. In the Users box, type CONTOSO\SharePoint Content Auditors.
10. In the Choose Permissions section, select the Full Read check box.
11. Click Finish.
f Task 4: Create a Full Control Web application policy

1.
2.
3.
4.
5.
6.
Click Add Users.

In the Zones list, select (All Zones).
Click Next.
In the Users box, type CONTOSO\SharePoint Full Control Policy.
In the Choose Permissions section, select the Full Control check box.
Click Finish.
f Task 5: Create a Deny Web application policy

1.
2.
3.
4.
5.
Click Add Users.

In the Zones list, select (All Zones).
Click Next.
In the Users box, type CONTOSO\SharePoint Deny Policy.
In the Choose Permissions section, select the Deny All check box.
6.
Click Finish, and then click OK.
f Task 6: Verify the behavior of SharePoint Web application policies

1.
2.
ENTER.
Different User.
3.
4.
5.
6.
7.

In the User name box, type CONTOSO\JimD.
Verify that you do not see the Add new item command.
Results: After this exercise, you should have created a new Web application policy granting full Read
permission to the intranet for audit purposes.

following steps:
1.
2.
3.

Lab Answer Key: Managing SharePoint Customizations
Module 7
Contents:


11

1.
2.

f Task 1: Activate a built-in feature
1.
2.
3.
4.
5.

In the address bar, type http://intranet.contoso.com, and then press ENTER.
Click Site Actions, and then click View All Site Content.
Click Create.
The Create page appears.
6.
7.
8.
9.
10.
11.
12.
Observe that a calendar or contact list are not shown as available options.
Close the Create page.
Click Site Actions, and then click Site Settings.
In the Site Actions section, click Manage site features.
In the Team Collaboration Lists row, click Activate.
Click Create.
The Create page appears.
13. Observe that you can now create a calendar or contact list.
14. Close the Create page.
f Task 2: Install a custom feature

1.
2.
3.
Open Windows Explorer and browse to the folder, D:\Labfiles\Lab07.

Right-click the CustomAction folder, and then click Copy.
In Windows Explorer, browse to C:\Program Files\Common Files
\Microsoft Shared\web server extensions\14\Template\Features.
Each folder in the Features folder represents a feature on the Microsoft SharePoint server.
4.
5.
6.
Press CTRL+V to paste the CustomAction folder into the Features folder.
Close the Features folder window.
Click Start, then click All Programs, then click Microsoft SharePoint 2010 Products, then rightclick SharePoint 2010 Management Shell, and then click Run as administrator.
7.
8.
Click Yes.
stsadm -o installfeature -filename CustomAction\feature.xml
This will install a new feature into SharePoint that enables a simple custom action in the Site Actions
menu.
f Task 3: Activate and test a custom feature

1.
2.
3.
4.
5.

In the JavaScript Dropdown Item row, click Activate.
Click Site Actions, and then click A Custom Action.
A Message from webpage window appears with the message, Hello World.
6.
Click OK.
f Task 4: Deactivate a feature

1.
2.
3.

In the JavaScript Dropdown Item row, click Deactivate.
A warning page appears.
4.
5.
6.
Click Deactivate this feature.

Click Site Actions, then observe that A Custom Action no longer appears, and then press ESC to
close the menu.

f Task 1: Install a solution
1.
2.

stsadm -o addsolution -filename "d:\Labfiles\Lab07\ApplicationTemplateCore.wsp"
stsadm -o addsolution -filename "d:\Labfiles\Lab07\BugDatabase.wsp"
3.
4.

5.
6.
7.
8.
Click Yes.
In the Quick Launch, click System Settings.
In the Farm Management section, click Manage farm solutions.
Observe that the two solutions are installed, but are not deployed.
f Task 2: Deploy a solution

1.
2.
3.
4.
5.
6.
Click applicationtemplatecore.wsp.
Click Deploy Solution.
Review the settings, and then click OK.
Click bugdatabase.wsp.
Click Deploy Solution.
Review the settings, and then click OK.
f Task 3: Confirm the deployment of a solution

1.
2.
3.
4.
5.
6.

Click Site Actions, and then click New Site.
In the left navigation, click the Application Templates tab, and then click Bug Database.
In the Title box, type Bug Tracking.
In the URL name box, type Bugs.
Click Create.
A new bug database Web is created in the IT site collection.
7.
8.
In the address bar, type http://intranet.contoso.com/sites/IT/Bugs, and then press ENTER.

Results: After completing this exercise, you should have installed and deployed SharePoint solutions to
your farm.
Lab Review
Question: What is a disadvantage of deploying a feature, in contrast to a solution, to a farm with more
than one server?
Answer: The Features folder must be the same on all servers in the farm, so you must copy the feature to
all servers and keep the Features folder in sync. When you deploy a feature with a solution, SharePoint
updates the Features folder on each server in the farm.
Question: Why is it important in some cases, such as the solutions deployed in this lab, to deploy
solutions in a specific order?
Answer: Solutions can have dependencies upon other solutions. The Bug Database solution has
dependencies on the Application Template Core solution.

f Task 1: Ensure that the code service is running
1.
2.
3.
4.
5.
Click Start, then click Administrative Tools, and then click Services.
Right-click SharePoint 2010 User Code Host, and then click Properties.
Verify that the service is not started, and that the Startup type is Disabled.
Click OK.
6.
7.
8.
9.
Click Yes.
Click Manage services on server.
In the Microsoft SharePoint Foundation Sandboxed Code Service row, click Start.
The service status changes to Started.
10.
11.
12.
13.
14.
Switch to the Services console.

Right-click SharePoint 2010 User Code Host, and then click Properties.
Verify that the service is started, and that the Startup type is Automatic.
Click OK.
f Task 2: Upload a sandboxed solution

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

In the Galleries section, click Solutions.
On the ribbon, click the Solutions tab, and then click Upload Solution.
Click Browse.
Select D:\Labfiles\Lab07\BadReceiver.wsp.
Click Open.
Click OK.
On the ribbon, click Activate.
The BadReceiver solution is displayed with a status of Activated.
11. Click Site Actions, and then click Site Settings.

12. In the Site Actions section, click Manage site features.
13. In the BadReceiver Feature1 row, click Activate.
f Task 3: Test a sandboxed solution

1.
2.
3.
4.
5.
6.

Click Announcements.
On the ribbon, click the Items tab.
Click New Item.
In the Title box, type My Announcement.
Click Save.

7.
8.
9.

Observe that the BadReceiver solution shows no resource usage. That is because the timer job has not
yet calculated the resource usage for the solution.
If you happened to see resource usage, then you were lucky! The timer jobs executed just in time.
Results: After completing this exercise, you should have deployed and tested the BadReceiver solution.

f Task 1: Run sandboxed solution timer jobs
1.

2.
3.
4.
5.
Click Yes.
In the Quick Launch, click Monitoring.
In the Timer Jobs section, click Review job definitions.
Locate the Solution Resource Usage Update timer job for SharePoint intranet.contoso.com80.
Tip: You must click the arrow at the bottom of the page.
6.
Click Solution Resource Usage Update in the SharePoint intranet.contoso.com80 row.
Note: Be sure to click Solution Resource Usage Update and not Solution Daily Resource Usage
Update. Clicking the latter will cause resource usage points to be reset.
7.
8.
9.
Click Run Now.

Click Solution Resource Usage Log Processing in the SharePoint intranet.contoso.com80 row.
Click Run Now.
f Task 2: Monitor resource usage

1.
2.
Switch to the instance of Internet Explorer that is displaying the Solutions Gallery
The resource usage for the solution should now be updated. If you do not see the updated resource
usage, then you may need to wait for up to 5 minutes for the timer jobs to execute.

f Task 1: Review default resource measures
1.
Run SharePoint 2010 Management Shell as administrator.

2.
3.
Click Yes.
To export a list of default point values, type the following command and then press ENTER:
$spusercodeservice.ResourceMeasures > c:\ResourceMeasures.txt
4.
Open the file C:\ResourceMeasures.txt.

This file contains a listing of the resource measures that are monitored for sandboxed solutions.
5.
6.
7.
To find the section for database queries, press CTRL+F, then type SharePointDatabaseQueryCount,
and then press ENTER.
Record the current values of ResourcesPerPoint and AbsoluteLimit.
Close the file.
f Task 2: Change default resource measure points

1.
2.
Switch to Administrator: SharePoint 2010 Management Shell.

$obj = $spusercodeservice.ResourceMeasures["SharePointDatabaseQueryCount"]
$obj.ResourcesPerPoint = 1
$obj.Update()
$obj | Select-Object Name,ResourcesPerPoint
This script sets the ResourcesPerPoint property for SharePointDatabaseQueryCount to 1 and will
cause SharePoint database queries to increase the resource usage point count very quickly.
3.

iisreset
IIS restarts and enables the new resource settings.

4.
Close Administrator: SharePoint 2010 Management Shell.
f Task 3: Test modified sandboxed resource measures

1.
Switch to the instance of Internet Explorer that displays the IT intranet Web.
It will take a few seconds to load the Web, because you recently reset IIS.
2.
3.
4.
5.
6.

Click Announcements.
On the ribbon, click Items.
Click New Item.
In the Title box, type My Next Announcement.
10
7.
Click Save.
8. Click Go back to site.

10. In the Galleries section, click Solutions.
Observe that the BadReceiver solution shows no resource usage. That is because the timer job has not
yet calculated resource usage for the solution.
If you saw resource usage, then you were lucky! The timer jobs executed just in time. Skip to step 13.
11. Repeat Task 1 of Exercise 2 to run the sandboxed solutions timer jobs.
12. Switch to the instance of Internet Explorer that displays the Solutions gallery for the IT intranet
Web.
13. Press F5 to refresh the page.
14. Observe that the resource usage of the solution is increasing more rapidly.
If you do not see the updated resource usage, then you may need to wait for up to 5 minutes for the
timer jobs to execute.
f Task 4: Deactivate the bad solution

1.
2.
3.
4.

Click the Bad Receiver row.
On the ribbon, click Deactivate.
The Solution Gallery - Deactivate Solution page opens.
5.
On the ribbon, click Deactivate.
Leave the virtual machines running. You will use them for Lab C.
Lab Review
Question: What was the value of ResourcesPerPoint for SharePointDatabaseQueryCount? Explain the
relationship between this number and one resource usage point.
Answer: 400. Each database query accrues 1/400 of a resource usage point.

Scenario
You have installed a new SharePoint 2010 farm for your developers. Recently the development manager fielded
several performance issues from end users and has mandated that applications are designed with performance as
top priority. One of the developers has asked you to enable the Developer Dashboard for debugging and
instrumentation purposes to support this new initiative.

f Task 1: Enable the Developer Dashboard
1.
2.

]::OnDemand
$ddsetting.Update()
This script enables the Developer Dashboard in OnDemand mode.
f Task 2: Review the Developer Dashboard

1.
2.
3.

Click the small icon in the top right next to SharePoint Administrator.
This will enable the Developer Dashboard for the page.
4.
Observe the information that is available on the page:
Http Handler Events for Http Request

Web Server stats
Asserts and Critical events
Database Queries
Service Calls
SPRequest Allocations
WebPart Events Offsets
f Task 3: Disable the Developer Dashboard

1.
2.

]::Off
$ddsetting.Update()
11
12
This script disables the Developer Dashboard.

Results: After completing the exercise, you should have enabled and disabled the Developer
Dashboard on the IT intranet Web.

following steps:
1.
2.
3.

Lab Review
Question: Describe the role of the Developer Dashboard.
Answer: The Developer Dashboard exposes performance and debugging information that can be used to
monitor and improve the performance of pages and solutions.
Lab Answer Key: Configuring and Securing SharePoint Services and Service Applications
Module 8
Lab Answer Key: Configuring and Securing SharePoint
Services and Service Applications
Contents:


11

1.
2.
Exercise 1: Administering SharePoint Services

f Task 1: Create a document in a document library
1.
2.
3.

After a few moments, the Contoso intranet Web appears.
4.
5.
6.
7.
Click Documents.
On the ribbon, click Documents.
Click New Document.
The Open Document dialog appears.
8.
Click OK.
After a few moments, the new document opens in Microsoft Office Word. If prompted for a user
name, click OK.
If the Windows Security dialog appears, perform the following steps:
a.
b.

9. In the document, type SharePoint IT Policies and Procedures.

10. On the ribbon, click File, and then click Save.
After a few moments, the Save As dialog displays the Documents library.
11. Click Save.
12. Observe the status bar at the bottom of the Word window. Wait until Word has finished saving the
document.
13. Close Word and click Yes and OK to check in the document.
14. Switch to Internet Explorer.
15. To confirm that the document was saved in the document library, press F5 to refresh the page, and
then click Retry.
f Task 2: Attempt to convert a document

1.
2.
Observe that there are no options to convert the document.
You must enable document conversion for each Web application and it requires several services to be
running.
3.
Minimize, but do not close, Internet Explorer.
f Task 3: Attempt to enable document conversion

1.

2.
3.
4.
Click Yes.
In the Quick Launch, click General Application Settings.
In the External Service Connections section, click Configure document conversions.
The Configure Document Conversions page appears.
5.
The Select Web Application dialog appears.
6.
7.

In the Enable Document Conversions section, click Yes, and then click OK.
At the top of the page, a message appears that indicates you must choose a document conversion
server.
8.
9.
Click the Load Balancer server drop-down arrow.

Observe that you have no options.
You must enable the SharePoint service on front-end Web servers before you can enable document
conversions.
10. Click Cancel.
f Task 4: Configure and start document conversion services

1.
2.

In the Servers section, click Manage services on server.
The Services On Server page opens. A list of all registered SharePoint Services is displayed.
3.
In the Document Conversions Load Balancer Service row, click Start.

The service starts.
4.
In the Document Conversions Launcher Service row, click Start.

The Launcher Service Settings page opens.
5.
6.
On the Launcher Service Settings page, in the Select Server section, verify that SP2010-WFE1 is
selected.
In the Load Balancer list, select SP2010-WFE1, and then click OK.
The service starts.
f Task 5: Enable document conversion

1.
2.
3.
4.
5.
In the Quick Launch, click General Application Settings.

In the External Service Connections section, click Configure document conversions.
Confirm that the selected Web application in the Web Application list is
http://intranet.contoso.com.
In the Enable Document Conversions section, click Yes.
In the Load Balancer Server list, select SP2010-WFE1, and then click OK.
f Task 6: Test document conversion

1.
2.
3.
4.
5.
Switch to the instance of Windows Internet Explorer that displays the document library.
To refresh the page, press F5, and then click Retry.
Observe the new menu item, Convert Document.
Click Convert Document, and then click From Word Document to Web Page.
The Create Page From Document page opens.
6.
7.
8.
In the Title box, type SharePoint Policies and Procedures.

In the URL Name box, type SharePointPoliciesAndProcedures.
Click Create. If the AutoComplete dialog opens, click No.
The SharePoint Policies And Procedures page opens.
f Task 7: Configure and start SharePoint Services

1.
2.
3.

The Services On Server page opens. A list of all registered SharePoint Services is displayed.
4.
In the Claims to Windows Token Service row, click Start.

The service starts.
5.
In the Microsoft SharePoint Foundation Subscription Settings Service row, click Start.
The service starts.
6.
In the SharePoint Foundation Search row, click Start.

The configuration page opens.
7.
8.
9.
10.
11.
In the Service Account list, select CONTOSO\SP_ServiceApps.

In the Content Access Account section, in the User name box, type CONTOSO\SP_ServiceApps.
Click Start.
Close all instances of Internet Explorer.

f Task 1: Stop the Timer service
1.
2.
3.
Click Yes.
net stop sptimerv4
This will stop the SharePoint 2010 Timer service. When this Windows Service has stopped, your
SharePoint farm loses much of its functionality.
4.
f Task 2: Attempt to create a service application

1.
2.
Open SharePoint 2010 Central Administration, and then in the Quick Launch, click Application
Management.
In the Service Applications section, click Manage Service Applications.
The Manage Service Applications page opens.
3.
On the ribbon, click New, and then click Managed Metadata Service.
The Create New Managed Metadata Service dialog appears.
4.
5.
6.
7.
In the Name box, type Managed Metadata Human Resources.

In the Database Name box, type HRMetadata.
In the Application Pool section, in the Application pool name box, type HRMetadataPool.
In the Configurable list, select CONTOSO\SP_ServiceApps, and then click OK.
The page will pause indefinitely.
8. Wait two minutes, and then click Cancel.

10. Observe that the Managed Metadata Human Resources service application is listed as Stopped,
and that there is no Managed Metadata Service connection created for the service application.
The Timer service must be running to process the jobs related to the creation of a service application.
f Task 3: Start the Timer service

1.
Click Start, click Administrative Tools, and then click Services.

The Services console opens.
2.
3.
Right-click the SharePoint 2010 Timer service, and then click Start.
f Task 4: Observe the effects of the Timer service

1.
2.
3.
4.

Observe the Managed Metadata Human Resources service application.
If the application is listed as Stopped, or if there is not a Managed Metadata Service connection for
the application, wait a few moments, and then return to step 2.
Leave the virtual machines running. You use them in Lab B.

f Task 1: Review farm account settings
1.

The Services console opens.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Right-click SharePoint 2010 Timer, and then click Properties.

Click the Log On tab.
Observe the account that is assigned to the SharePoint 2010 Timer service.
Click Cancel.
Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
Expand SP2010-WFE1.
Click Application Pools.
Right-click SharePoint Central Administration v4, and then click Advanced Settings.
In the Process Model section, observe the Identity property of the application pool.
Click Cancel.
f Task 2: Add a managed account

1.
2.
3.

In the Quick Launch, click Security.
In the General Security section, click Configure managed accounts.
The Managed Accounts page appears.
4.
5.
6.
Click Register Managed Account.

f Task 3: Change the SharePoint farm account

1.
2.
3.

In the General Security section, click Configure service accounts.
The Service Accounts page appears.
4.
5.
In the drop-down list, select Farm Account.

In the Select an account for this component list, select CONTOSO\SP_Admin, and then click OK.
SharePoint will reconfigure services that use the farm account to now use the SP_Admin account.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Wait for the Security page to appear.

Open the Services console.
Right-click SharePoint 2010 Timer, and then click Properties.
Click the Log On tab.
Confirm that the account assigned to the SharePoint 2010 Timer service is SP_Admin.
Click Cancel.
Switch to Internet Information Services (IIS) Manager.
Right-click SharePoint Central Administration v4, and then click Advanced Settings.
In the Process Model section, confirm that the Identity property of the application pool is
SP_Admin.
15. Click Cancel.

16. Repeat steps 16 to reset the farm account to SP_Farm.
f Task 4: Configure password change settings

1.
2.
3.

In the General Security section, click Configure password change settings.
The Password Management Settings page appears.
4.
In the Notification E-Mail Address box, type sharepoint@contoso.com, and then click OK.
f Task 5: Change a managed account password

1.
2.
In SharePoint 2010 Central Administration Quick Launch, click Security.

The Managed Accounts page opens.
3.
4.
5.
6.
7.

Select the Change password now option.
In the Set account password to new value and Confirm password boxes, type Pa$$w0rd1, and
then click OK.
Wait for the Security page to open.
Confirm that the Last password change column of the CONTOSO\SP_Farm row indicates that the
password was changed.

f Task 1: Review the encryption of Central Administration
1.
2.

3.
4.

Observe the warning that appears at the top of the page that reminds you that Central
Administration is not using encryption.
f Task 2: Install Active Directory Certificate Services

1.
Hold down the SHIFT key and right-click Server Manager, and then click Run as different user.
2.
3.
4.
Enter the user name CONTOSO\Administrator and the password Pa$$w0rd.

In the console tree, click Roles.
In the Roles Summary section, click Add Roles.
The Add Roles Wizard appears.
5.
6.
7.
8.
9.
10.
11.
12.
On the Before You Begin page, click Next.

On the Select Server Roles page, select the Active Directory Certificate Services option.
Click Next.
On the Introduction to Active Directory Certificate Services page, click Next.
On the Select Role Services page, ensure that Certification Authority is selected.
Select the Certification Authority Web Enrollment option.
Click Next.
On the Specify Setup Type page, ensure that Enterprise is selected, and then click Next.
Note: If you cannot select Enterprise, ensure that you are logged in as CONTOSO\Administrator.
13.
14.
15.
16.
17.
18.
19.
20.
On the Specify CA Type page, ensure that Root CA is selected, and then click Next.
On the Set Up Private Key page, click Next.
On the Configure Cryptography for CA page, click Next.
On the Configure CA Name page, click Next.
On the Set Validity Period page, click Next.
On the Configure Certificate Database page, click Next.
On the Confirm Installation Selections page, click Install.
On the Installation Results page, click Close.
f Task 3: Create and install an SSL certificate

1.
2.
3.
4.
5.
6.
In the console tree, expand Roles, expand Web Server (IIS), and then click Internet Information
Services (IIS) Manager.
In the Connections panel, expand SP2010-WFE1, and then click SP2010-WFE1.
In the IIS section of the SP2010-WFE1 Home pane, double-click Server Certificates.
In the Actions panel, click the Create Domain Certificate.
In the Common name box, type Contoso.
In the Organization box, type Contoso.
10
7.
8.
9.
10.
11.
12.
13.
14.
15.
In the Organizational unit box, type SharePoint.

In the City/locality box, type Redmond.
In the State/province box, type WA.
In the Country/region list, select US.
Click Next.
Click Select.
Click contoso-SP2010-WFE1-CA, and then click OK.
In the Friendly name box, type Contoso.
Click Finish.
f Task 4: Configure SSL for Central Administration

1.
2.
3.
4.
5.
6.
7.
8.
In the Connections panel, expand Sites, and then click Sites.

Right-click SharePoint Central Administration v4, and then click Bindings.
Click Add.
In the Type list, select https.
In the Port list, type 10000.
In the SSL certificate list, select Contoso, and then click OK.
Click Close.
f Task 5: Test SSL for Central Administration

1.
2.

In the address bar, type https://sp2010-wfe1:10000. Press ENTER.
A message indicates the following: There is a problem with this websites security certificate.
This message appears because the certificate is issued by the server itself, not a trusted certificate
authority. In a production environment in which you had established your certificate authority using a
certificate from a trusted certificate root, this message would not appear.
3.
Click Continue to this website (not recommended).

The Central Administration site opens in secure mode.
4.
5.

6.
7.
8.

Observe that the warning message you observed in Task 1 no longer appears.
Leave the virtual machines running. You use them in Lab C.

f Task 1: Create a service application
1.

2.
3.
4.
Click Yes.
5.
6.
7.
8.
9.
Click New, and then click Managed Metadata Service.

In the Service Application Name box, type Managed Metadata Clients.
In the Database Name box, type Managed_Metadata_Clients.
In the Application pool section, click Use existing application pool, and then select SharePoint
Web Services Default.
Clear the Add this service application to the farms default list option, and then click OK.
The service application is created.
10. Click OK.
f Task 2: Configure the default application proxy group

1.
2.

In the Service Applications section, click Configure service application associations.
The Service Application Associations page opens.
3.
4.
In the Application Proxy Group column, click default.

Verify that the Managed Metadata Clients option is clear, and then click OK.
f Task 3: Configure a custom application proxy group

1.
2.

The Service Application Associations page opens.
3.
4.
5.

In the Edit the following group of connections list, select [custom].
Select the following service application check boxes:
6.
7.
Managed Metadata Clients

Search Service Application
Usage and Health data collection
Web Analytics Service Application
Click OK.
Observe that there is an application proxy group labeled custom assigned to the intranet Web
application.
11
12
f Task 4: Publish a service application

1.
2.

3.
Select the Managed Metadata Clients service application row.
Tip: Do not click the Managed Metadata Clients link. The link opens the management page for the
service application. Instead, click any part of the row other than the link.
4.
5.
On the ribbon, click Publish.

Select the Publish the Service Application to other farms option.
Because this lab contains only one farm, you cannot configure a trust relationship.
6.
Click OK.

When you finish the lab, revert the virtual machines to their initial state. To do this, complete the
following steps:
1.
2.
3.

Lab Answer Key: User Profiles and Social Networking
Module 9
Contents:
Lab: A: Configuring User Profiles
Lab: B: Administering My Sites

14
17
19
Lab A: Configuring User Profiles

1.
2.

f Task 1: Start the Web Service Application Pool
1.
2.
3.
4.
5.

Click Start, then click Administrative Tools, and then click Internet Information Services (IIS)
Manager.
Expand SP2010-WFE1.
Click Application Pools.
If Microsoft SharePoint Web Services Root is not started, then right-click SharePoint Web
Services Root, and then click Start.
This step is necessary because memory limitations in the lab environment may prevent the
application pool from starting automatically. This problem would manifest itself as a WCF error later
in this lab.
6.
Close Internet Information Services (IIS) Manager.
f Task 2: Create a user profile service application

1.
2.
3.

4.
Click New, and then click User Profile Service Application.

The Create New User Profile Service Application page opens.
5.
6.
7.
8.
9.
In the Name box, type User Profile Service Application.

In the Application pool name box, type UserProfilePool.
In the Configurable list, select CONTOSO\SP_Farm.
Review, but skip the remaining sections.
Click Create.
The service application is created.
10. Click OK.
f Task 3: Start required SharePoint services

1.
2.

The Services on Server page opens.
3.
4.
In the User Profile Service row, click Start.

In the User Profile Synchronization Service row, click Start.
The User Profile Synchronization Service page opens.
5.
6.
7.
8.
In the Select the User Profile Application list, select User Profile Service Application.
In the Password and Confirm Password boxes, type Pa$$w0rd.
Click OK.
Observe the Status of the User Profile Synchronization Service.
A timer job is created that will configure user profile settings in the farm. When it has completed, the
status of the service will change from Starting to Started.
9.
10.
11.
12.
13.
14.

In the Timer Jobs section, click Check job status.
In the Timer Links section of the Quick Launch, click Running Jobs.
Monitor the page.
Repeat this step until the ProfileSynchronizationSetupJob appears.
Note: It can take up to 5 minutes for the ProfileSynchronizationSetupJob to appear on the Running
Jobs list. If you dont see the job start, re-start the Timer Service, but be sure you DO NOT restart it if
this job is running.
15. Monitor the page. Press F5 to refresh the page. Repeat this step until the
ProfileSynchronizationSetupJob disappears.
Note: It can take up to 15 minutes for the ProfileSynchronizationSetupJob to complete.
16.
17.
18.
19.
In the Timer Links section of the Quick Launch, click Job History.
Confirm that the Status of ProfileSynchronizationSetupJob is Succeeded.
20. Confirm that the Status of the user profile synchronization service is Started.
21. Close SharePoint 2010 Central Administration.
f Task 4: Verify successful service startup

1.
2.

Confirm that the following services are started:
Microsoft Forefront Identity Manager Service

Forefront Identity Manager Synchronization Service
If a service is not started, then press F5 to refresh the view. Repeat this step until the services have
started.
Note: This can take several minutes.
3.
4.

Open the folder C:\Program Files\Microsoft Office Servers\14.0
\Synchronization Service\MaData.
5.
Confirm that the ILMMA folder exists. Confirm that a folder named
MOSS-GUID exists with todays date.
If the folders do not exist, wait until the timer job has completed fully, at which point the folders will
appear.
6.
Close the Windows Explorer window that is showing the MaData folder.
f Task 5: Reset IIS

1.
2.
3.
4.
Click Yes.
Type IISRESET, and then press ENTER.
After the command has completed, close Administrator: Command Prompt.
f Task 6: Validate the service application

1.
2.
3.
Open Microsoft SharePoint 2010 Central Administration.

4.
Click User Profile Service Application.

The management page for the service application opens.
If an error is displayed, it is probably because the Web services have not completed startup following
the IISRESET operation. Press F5 to refresh the page until the error disappears.
5.
6.
Confirm that there are numbers on the right side of the page, which indicates that the service
application is running.

f Task 1: Delegate Active Directory permissions to enable user profiles synchronization
1.
Click Start, click Administrative Tools, hold the SHIFT key and right-click Active Directory Users
and Computers, and then click Run as different user.
2.
3.
4.
Enter the user name, CONTOSO\Administrator, and the password, Pa$$w0rd, and then click OK.
In the console tree, expand contoso.com.
Right-click contoso.com, and then click Delegate Control.
The Delegation of Control Wizard appears.
5.
6.
7.
8.
9.
10.
11.
12.
13.
On the Welcome to the Delegation of Control Wizard page, click Next.

On the Users or Groups page, click Add.
Type CONTOSO\SP_Farm.
Click OK.
Click Next.
On the Tasks to Delegate page, click Create a custom task to delegate.
Click Next.
On the Active Directory Object Type page, click Next.
On the Permissions page, in the Permissions list, select the Replicating Directory Changes check
box.
14. Click Next.
15. On the Completing the Delegation of Control Wizard page, click Finish.
16. Close Active Directory Users and Computers.
f Task 2: Create a user profile connection to Active Directory

1.
2.
3.
Open the SharePoint 2010 Central Administration.

4.

The Manage Profile Service page opens.
5.
In the Synchronization section, click Configure Synchronization Connections.

The Synchronization Connections page opens.
6.
Click Create New Connection.

The Add new synchronization connection page opens.
7.
8.
9.
In the Connection Name box, type Contoso Active Directory.

In the Forest name box, type contoso.com.
In the Account name box, type CONTOSO\SP_Farm.
Note: This is the account used by the User Profile Synchronization Service in the Beta virtual machine.
10. In the Password and Confirm password boxes, type Pa$$w0rd.
11. Click Populate Containers.

12. In the Containers section, expand CONTOSO, and then select the People, SharePoint, and Users
check boxes.
13. Click OK.
A new synchronization connection is created.
f Task 3: Add a custom user property

1.
2.
3.
4.

In the People section, click Manage User Properties.
The Manage User Properties page opens.
5.
6.
7.
8.
9.
Click New Property.

In the Name box, type City.
In the Display Name box, type City.
In the Policy Settings section, in the Default Privacy Setting list, select Everyone.
Select the Replicable check box.
A message box appears indicating that replicated data will not be deleted.
10. Click OK.

11. In the Display Settings section, select the Show in the profile properties section of the users
profile page check box.
12. Select the Show on the Edit Details page check box.
13. Select the Show updates to the property in newsfeed check box.
14. In the Add New Mapping section, in the Source Data Connection box, select Contoso Active
Directory.
15. In the Attribute list, select l.
Tip: l (lowercase L) is the Lightweight Directory Access Protocol (LDAP) name for the locale, or city
attribute.
16. In the Direction list, select Import.
17. Click Add.
18. Observe that the new attribute mapping appears in the Property Mapping for Synchronization
section.
19. Click OK.
f Task 4: Import user profiles from Active Directory

1.
2.
3.
4.
5.
6.
7.

In the Synchronization section, click Start Profile Synchronization.
Click Start Full Synchronization.
Click OK.
Wait one minute.
The synchronization does not start immediately.

9. Observe the Profile Synchronization Status in the Profile Synchronization Settings section.
10. Return to step 8 until the Profile Synchronization Status displays Idle.
Note: This may take 10-15 minutes.
11. In the Profiles section, confirm that the Number of user profiles is 53 and confirm that Profile
Synchronization Status displays Idle.

1.
In the People section, click Manage User Profiles.

The Manage User Profiles page appears.
2.
3.
4.
5.
6.
In the Find profiles box, type SP_Admin.

Click Find.
Click CONTOSO\SP_Admin, and then click Edit My Profile.
Browse to City, notice it has nothing in it.
Click Cancel and Go Back.
f Task 6: Configure a profile property in Active Directory

1.
Click Start, click Administrative Tools, hold the SHIFT key and right-click Active Directory Users
and Computers, and then click Run as different user.
2.
3.
4.
5.
6.
7.
8.
9.
Enter the user name, CONTOSO\Administrator, and the password, Pa$$w0rd.

In the console tree, expand contoso.com.
Click SharePoint.
Right-click SharePoint Administrator, and then click Properties.
Click the Address tab.
In the City box, type Seattle.
Click OK.
f Task 7: Run an incremental profile synchronization

1.
2.
3.
Switch to Central Administration.

4.
5.

The Start Profile Synchronization page opens.
6.
Click Start Incremental Synchronization.
7.
8.
Click OK.
Wait 30 seconds.

Note: This may take several minutes.

1.

2.
3.
4.
5.
6.

Click Find.
Confirm that City is Seattle.
Click Cancel and Go Back.

f Task 1: Create a new profile property
1.
2.

3.
4.

5.
6.
Click New Property.

In the Name box, type EmployeeID.
Note: You must type the text exactly as shown, with no space.
7.
In the Display Name box, type Employee ID.
Note: You must type the text exactly as shown, with a space.
8. In the Type list, select integer.
9. In the Policy Settings section, in the Default Privacy Setting list, select Everyone.
10. Select the Replicable check box.
A message appears indicating that replicated data will not be deleted.
11. Click OK.
12. Click the Allow users to edit values for this property radio button.
15. Click OK.
f Task 2: Set up data source permissions

1.
Click Start, click All Programs, then click Microsoft SQL Server 2008 R2, hold SHIFT and right-click
SQL Server Management Studio, and then click Run as different user.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Enter the user name, CONTOSO\Administrator, the password, Pa$$w0rd, and then click OK.
On the Connect to Server dialog box, click the Connect button.
Expand Databases.
Expand AdventureWorks.
Expand Security.
Right-click Users, select New User.
In the Login name box, type CONTOSO\SP_Admin.
In the Database role membership list, select the db_owner check box.
Click OK.
10
12. Repeat steps 6-10 for CONTOSO\SP_Farm.

13. Close Microsoft SQL Server Management Studio.
f Task 3: Create an external data source

1.
2.
3.
Click Start, click All Programs, click SharePoint, and then click Microsoft SharePoint Designer
2010.
Click Open Site.
Type http://intranet.contoso.com/sites/IT, and then click Open.
Wait for the site to open.
4. When prompted for credentials, use Contoso\SP_Admin with the password Pa$$w0rd.
5. In the Site Objects panel, click External Content Types.
Wait for SharePoint to retrieve external content types.
6.
7.
On the ribbon, click External Content Type.

In the External Content Type Information section, next to Name, click New external content
type.
8. Type AdventureWorks.
9. Click Click here to discover external data sources.
10. Click Add Connection.
The External Data Source Type Selection dialog box appears.
11. In the Data Source Type list, select SQL Server.
12. Click OK.
The SQL Server Connection dialog box appears.
13.
14.
15.
16.
17.
18.

In the Database Name box, type AdventureWorks.
Click OK.
In the Data Source Explorer box, expand AdventureWorks.
Expand Tables.
Right-click Employee, and then click Create All Operations.
The All Operations dialog box appears.
19.
20.
21.
22.
Click Next.
Click Finish.
To save the external content type, press CTRL+S.
Close SharePoint Designer.
f Task 4: Set permissions on an external data source

1.
2.
3.

4.
Click Business Data Connectivity Service.

The View External Content Types page appears.
5.
6.
Click AdventureWorks.
On the ribbon, click Set Object Permissions.
7.
8.
9.
10.
11
Type All Authenticated Users.

Click Add.
In the Permissions for All Authenticated Users list, select each of the four check boxes.
Click OK.
f Task 5: Create a synchronization connection to an external data source

1.
2.

3.

The Manage Profile Service page opens.
4.
Click Configure Synchronization Connections.

The Synchronization Connections page opens.
5.
Click Create New Connection.

The Add new synchronization connection page opens.
6.
7.
8.
In the Connection Name box, type AdventureWorks.

In the Type box, select Business Data Connectivity.
Next to the Business Data Connectivity Entity box, click the Select External Content Type button.
Tip: The Select External Content Type button is the right-most button.
The External Content Type Picker dialog box appears.
9.
10.
11.
12.
13.
Click AdventureWorks.
Click OK.
Click Connect User Profile Store to Business Data Connectivity Entity as a 1:1 mapping.
In the Return items identified by this profile property list, select EmployeeID.
Click OK.
Task 6: Add a profile property from an external data source

1.
2.

3.
4.

5.
6.
7.
8.
9.
10.
Click New Property.

In the Name box, type Gender.
In the Display Name box, type Gender.
In the Policy Settings section, in the Policy Setting list, select Optional.
In the Default Privacy Setting list, select Everyone.
Select the Replicable check box.
A message appears indicating that replicated data will not be deleted.
12
11. Click OK.

14. In the Source Data Connection list, select AdventureWorks.
15. In the Attribute list, select Gender.
16. Click Add.
17. Click OK.
f Task 7: Edit a user profile

1.
2.

3.
4.

5.
6.
7.
8.
9.
10.

Click Find.
In the Employee ID box, type 1.
Confirm that Gender is blank.
Click Save and Close.
f Task 8: Import profile data from the external data source

1.
2.
3.
In the Quick Launch, click Central Administration.

4.
5.

The Start Profile Synchronization page opens.
6.
7.
8.
Click Start Full Synchronization.

Click OK.
Wait 30 seconds.

Note: This may take 10-15 minutes.
f Task 9: Validate the user profile import

1.
2.

3.
4.

5.
6.
7.
8.
9.

Click Find.
Confirm that Gender is M.
Question: What group does the farm account have to be in in order for user profile synchronization to
work?
Answer: The farm account must be a local administrator. This requirement is enforced by the set up of
Forefront Identity Manager in the synchronization process.
13
14
Lab B: Administering My Sites

f Task 1: Create My Site Web application
1.
2.
3.

In the Web Applications section, click Manage Web applications.
4.

The Create New Web Application page opens.
5.
6.
In the IIS Web Site section, in the Port box, type 80.
In the Host Header box, type mysites.contoso.com.
Note: A DNS host record for mysites.contoso.com has already been created in the domain's DNS zone.
7.
8.
9.
In the Application Pool section, in the Configurable list, select CONTOSO\SP_Farm.

In the Database Name and Authentication section, in the Database Name box, type
WSS_Content_MySites.
Click OK.
The Application Created page opens.
10.
11.
12.
13.
14.
Click Create Site Collection.

In the Title box, type My Site Host.
In the Template Selection section, click the Enterprise tab.
Select My Site Host.
In the Primary Site Collection Administrator section, in the User Name box, type
CONTOSO\SP_Admin.
15. Click OK.
The Top-Level Site Successfully Created page opens.
16. Click OK.
f Task 2: Create a search center

1.
2.

In the Site Collections section, click Create Site Collections.
The Create Site Collection page opens.
3.
4.
5.
6.
7.
8.
In the Title box, type Search Center.

In the Web Site Address section, select sites, and then type Search.
In the Template Selection section, click the Enterprise tab.
Click Enterprise Search Center.
CONTOSO\SP_Admin.
Click OK.
f Task 3: Configure permissions for the search center

1.
2.
3.
4.
5.
6.
7.
Open a new tab in Windows Internet Explorer.

In the address bar, type http://mysites.contoso.com/sites/Search and then press ENTER.
In the Users/Groups box, type Domain Users.
In the Add users to a SharePoint group list, select Search Center Visitors.
Click OK.
f Task 4: Configure a managed path for MySites

1.
2.
3.

4.
5.
6.
7.
8.
Click SharePoint - mysites.contoso.com80.

On the ribbon, click Managed Paths.
In the Path box, type Personal.
Click Add Path.
Click OK.
The managed path is added.
f Task 5: Enable self-service site creation

1.
2.
Click SharePoint - mysites.contoso.com80.

On the ribbon, click Self-Service Site Creation.
The Self-Service Site Collection Management page opens.
3.
4.
Click On.
Click OK.
f Task 6: Configure my sites

1.
2.

3.
4.
5.

In the My Site Settings section, click Setup My Sites.
In the Preferred Search Center box, type http://mysites.contoso.com/sites
/Search/Pages.
15
16
6.
7.
8.
In the My Site Host location box, type http://mysites.contoso.com.

In the Location box, type personal.
Click OK.
f Task 7: Configure permissions for the intranet

1.
2.
3.
4.
5.
6.
7.
8.
9.
Open a new tab in Internet Explorer.

In the address bar, type http://intranet.contoso.com.
In the Users/Groups box, type Domain Users.
In the Add users to a SharePoint group (recommended) list, select Contoso Intranet Visitors
[Read].
Click OK.
Log off SP2010-WFE1.

f Task 1: Create your My Site
1.
2.
3.
4.
Log on to SP2010-WFE1 as CONTOSO\DanJ with password, Pa$$w0rd.

Click the logon menu, Dan Jump, and then click My Profile.
Note: If My Profile is not visible, click My Settings, and then click My Profile.
The profile page for Dan Jump, CEO, opens.
5.
In the top link bar, click My Content.

A My Site is created. The Processing screen may display for 1 to 2 minutes.
6.
In the top link bar, click My Profile.

The profile page opens.
7.
Review the tabs on the My Site.
f Task 2: Update your status

1.
2.
Click in the Whats happening? box.

Type Loving SharePoint! and then press ENTER.
Your status is updated.
f Task 3: Edit your profile

1.
2.
3.
Click Edit My Profile.

For the following profile properties, type the corresponding value.
Profile Property
Value
About me
I enjoy helping my team succeed
Mobile phone
206-555-1234
Home phone
725-555-1234
Office Location
New Tower
Time Zone
(UTC-8:00) Pacific Time (US and Canada)
Past projects
SharePoint 2007
Skills
Public Speaking
Schools
University of SharePoint
Birthday
January 1
Employee ID
In the Birthday section, in the Show To list, select My Colleagues.
17
18
4.
5.
6.

Click More information.
Observe that the newly populated profile properties are now visible.
19

f Task 1: Add colleagues
1.
Click the Colleagues tab.

A listing of your colleagues is displayed. Anyone that is specified as a direct report in Active Directory
is automatically listed as a colleague.
2.
Click Add Colleagues.

The Add Colleagues page opens.
3.
4.
5.
In the Colleagues box, type CONTOSO\LolaJ, and then click the Check Names button.
In the Add to My Team section, click Yes.
Click OK.
Lola Jacobson is added as your colleague.
The Suggested Colleagues page opens.
6.
Click Skip.
f Task 2: Track colleagues

1.
Click the Dan Jump logon menu, and then click Sign in as a Different User.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

Click OK.
In the top link bar, click My Profile.
Click Edit My Profile.
In the About Me box, type On the Contoso team for 15 years!
In the Employee ID box, type 3.
Click in the What's happening? status box.
Type Working on our marketing strategy, and then press ENTER.
f Task 3: Configure membership

1.
In the address bar, type http://intranet.contoso.com/Sites/IT.

The Error: Access Denied page opens.
2.
3.
4.
5.
6.
Click Sign in as different user.

Click OK.
The Permissions page opens.
7.

The Grant Permissions page opens.
20
8.
9.
10.
11.
12.
13.
14.
In the Users/Groups box, type CONTOSO\DanJ.

In the Add users to a SharePoint group (recommended) list, select Information Technology
Members [Contribute].
Click OK.
Click Information Technology Members.
On the Information Technology Members page, click Settings, and then click Make Default
Group.
Click OK.
f Task 4: Start profile synchronization jobs

1.

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

Click OK.
Click Review job definitions.
Click the next page buttonthe right-pointing arrowat the bottom of the page.
Click User Profile Service Application Activity Feed Job.
Click Enable.
Click Run Now.
Press F5 to refresh the page. Repeat this step until the Last run time indicates that the job has
completed.
14. Click OK.
15. Repeat the above steps and run the following jobs:
User Profile Service Application User Profile to SharePoint Full Synchronization
User Profile Service Application User Profile to SharePoint Quick Synchronization
f Task 5: Explore In Common with You

1.
2.
3.
4.

In the address bar, type http://intranet.contoso.com/Sites/IT.
Click the Sign In control that displays Dan Jump, and then click My Profile.
In the My Organization Chart section, click Toni Poe.
Toni Poes profile opens.
5.
6.
7.
Review the contents of the In Common with You section.

Click Organization Browser.
Click Dan Jump.
Dan Jumps section of the organization browser expands.
8.
Click Dan Jumps name.

Dan Jumps profile page appears.
f Task 6: View previous updates

1.
2.
Switch to the instance of Internet Explorer that displays the My Site for Dan Jump.
Click My Newsfeed.
You should see the various changes you have made.
3.
Click My Profile, and then click Memberships.

You should see the new Information Technology site you are a member of.
4.
5.
Click Information Technology.

Click the browser's Back button.

following steps:
1.
2.
3.

21
Lab Answer Key: Administering and Configuring SharePoint Search
Module 10
Lab Answer Key: Administering and Configuring SharePoint
Search
Contents:
11
14

16
18
20

1.
2.
Start 10174A-CONTOSO-DC-E.
After CONTOSO-DC has completed startup, start 10174A-SP2010-WFE1-E.

f Task 1: Explore SharePoint content
1.
2.
3.
4.
5.
6.
7.
8.

Observe that the library includes the documents IT Policies and Procedures for SharePoint 2010
and SharePoint Governance Plan.
In the Quick Launch, click All Site Content, and then click Announcements.
Observe the two announcements, WSS stands for Windows SharePoint Services and Mud is dirty.
In the global navigation, click the Home tab.
f Task 2: Create a shared folder

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Open the C drive.

In the toolbar, click New folder.
Type Data, and then press ENTER.
Right-click Data, and then click Properties.
Click the Sharing tab.
Click Advanced Sharing.
Select the Share this folder option.
Click Permissions.
Click the Allow option next to Full Control.
To close all dialogs, click OK, click OK again, and then click Close.
Double-click Data.
Type Temporary Drafts, and then press ENTER.
Close the Windows Explorer window Data.
f Task 3: Add files to the shared folder

1.
2.
Click Start, and then click Notepad.

Type the following:
SharePoint is able to index files in a shared folder.
3.
4.
5.
6.

In the File name box, type C:\Data\SharePoint Search, and then press ENTER.
Click File, and then click New.
Type the following:
SharePoint crawl rules allow you to manage the content that is included and excluded.
7.
8. In the File name box, type C:\Data\Temporary Drafts\Crawl Rules, and then press ENTER.
9. Close Notepad.
10. Copy D:\LabFiles\Lab10\SharePoint Governance Checklist.pdf to C:\Data.

f Task 1: Attempt to create a Search Center
1.
2.
Switch to the instance of Windows Internet Explorer that displays the Information Technology Web.
The Create page opens.
3.
4.
5.
6.
7.
In the Filter By panel, click Search.

In the URL name box, type Search.
Click Create.
Note: The Microsoft SharePoint Server Publishing Infrastructure feature must be active to create a
Web using the Enterprise Search Center site definition. You can create a Web using the Basic Search
Center site definition without activating the SharePoint Server Publishing Infrastructure feature.
The SharePoint Server Standard Site Collection Features feature must also be active before you can
create a Web with either site definition.
8.
Close the error message, and then close the Create page.
f Task 2: Enable SharePoint Search features

1.
2.
3.
4.

In the Site Collection Administration section, click Site collection features.
In the SharePoint Server Publishing Infrastructure row, click Activate.
Wait for the page to refresh, and then confirm that the features status is Active.
f Task 3: Create a Search Center

1.

The Create page opens.
2.
3.
4.
5.
6.
In the Filter By panel, click Search.

In the URL name box, type Search.
Click Create.
A Search site is created.
f Task 4: Test the Search Center

1.
In the search box, type procedures, and then press ENTER.

The file IT Policies and Procedures for SharePoint is returned in the list of results.
2.
In the search box, type index, and then press ENTER.

3.
In the search box, type excluded, and then press ENTER.

f Task 1: Create a content source
1.

2.
3.
4.
5.
Click Yes.
Click Search Service Application.
The Search Administration page opens.
6.
7.
8.
9.
10.
11.
In the Quick Launch, in the Crawling section, click Content Sources.

Click New Content Source.
In the Name box, type Shared Folder - Data.
In the Content Source Type section, click File Shares.
In the Start Addresses box, type \\sp2010-wfe1.contoso.com\Data.
Scroll to the Start Full Crawl section, select the Start full crawl of this content source option, and
then click OK.
A new content source is created and a full crawl is started.
12. Click Refresh above the list of content sources. Repeat this step to refresh the page until the Status
column of the Shared Folder - Data row displays Idle.
f Task 2: Test the content source

1.
2.
Switch to the instance of Internet Explorer that displays the Search Center.
3.

The file Crawl Rules.txt is returned as a result.
f Task 3: Create a crawl schedule

1.
2.
3.

Point at Shared Folder - Data, click the drop-down arrow, and then click Edit.
In the Crawl Schedules section, under Full Crawl, click the Create schedule.
The Manage Schedules page opens.
4.
5.
In the Settings section, select the Repeat within the day option.
In the Every box, type 60, click OK, and then click OK again.
f Task 4: Create a crawl rule

1.
2.
In the Quick Launch, in the Crawling section, click Crawl Rules.

Click New Crawl Rule.
3.
4.
In the Path box, type \\sp2010-wfe1.contoso.com\Data

\Temporary Drafts\*.
Examine, but do not change, the other settings on the page, and then click OK.

1.
2.
3.

Point at Shared Folder - Data, click the drop-down arrow, and then click Start Full Crawl.
Click Refresh above the list of content sources. Repeat this step to refresh the page until the Status
f Task 6: Test the crawl rule

1.
2.
3.


f Task 1: Search for an existing PDF file
In the search box, type governance, and then press ENTER.

You should not see the file sharepoint governance checklist.pdf in the results even though it is in the
shared folder Data.
f Task 2: Add a file type for PDFs

1.
2.

In the Quick Launch, in the Crawling section, click File Types.
The Manage File Types page opens.
3.
4.
Click New File Type.

In the File extension box, type pdf, and then click OK.

1.
2.
3.

f Task 4: Test the file type

1.
2.
3.
4.
Observe the URL of the file sharepoint governance checklist.pdf.

In the search box, type Deployment, and then press ENTER.
Note: Deployment is a term in the PDF file. You must install a 64-bit iFilter for PDFs on all servers that perform
indexing to index the contents of PDF documents successfully.

f Task 1: Explore query crawl logs
1.
2.
3.
4.
5.
6.
7.

In the Quick Launch, in the Crawling section, click Crawl Log.
Click Shared Folder - Data.
Examine the crawl history of the Shared Folder - Data content source.
Above the list, click URL.
Examine the crawl history for each URL that has been indexed.
Examine the list to locate the URL for the file sharepoint governance checklist.pdf. If the URL does
not appear, wait a few moments, and then click the Search button.
f Task 2: Configure the default content access account

1. In the Quick Launch, click Search Administration.
2. In the Default content access account row, click CONTOSO\SP_ServiceApps.
3. In the Account box, type CONTOSO\SP_Crawl.
4. In the Password and Confirm Password boxes, type Pa$$w0rd, and then click OK.
f Task 3: Add a server name mapping

1.
2.
3.
4.
In Quick Launch, in the Crawling section, click Server Name Mappings.

Click New Mapping.
In the Addresses in index box, type \\sp2010-wfe1.contoso.com.
In the Address in search results box, type \\localhost, and then click OK.

1.
2.
3.

f Task 5: Test server name mappings

1.
2.
The file sharepoint governance checklist.pdf is returned in the list of results.
3.
Observe that the URL of the file sharepoint governance checklist.pdf is displayed as localhost
instead of sp2010-wfe1.contoso.com.
f Task 6: Explore host distribution rules

1.
2.

In the Quick Launch, in the Crawling section, click Host Distribution Rules.
SharePoint notifies you that host distribution rules cannot be applied to a farm with only one crawl
database.
10
f Task 7: Configure crawler impact rules

1.
2.
3.
4.
5.
In the Quick Launch, in the Crawling section, click Crawler Impact Rules.
Click Add Rule.
In the Site box, type SP2010-WFE1.
Click Request one document at a time and wait the specified time between requests.
In the Time to wait box, type 30, and then click OK.

f Task 1: Add a column to a document library
1.
2.
3.
4.
5.
6.
7.
On the ribbon, click Library.
Click Create Column.
In the Column name box, type Summary, and then click OK.
Point at IT Policies and Procedures for SharePoint 2010, click the drop-down arrow that appears,
and then click Edit Properties.
The properties page for the document opens.
8.
9.
In the Summary box, type Contoso IT Policies and Procedures for SharePoint 2010.
Click Save.

1.
2.
3.
4.
5.
6.
7.

Point at Local SharePoint sites, click the drop-down arrow, and then click Start Full Crawl.
column of the Local SharePoint sites row displays Idle.
f Task 3: Configure a managed property

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

In the Quick Launch, in the Queries and Results section, click Metadata Properties.
Click New Managed Property.
In the Property name box, type ContosoSummary.
In the Mappings to crawled properties section, click Add Mapping.
In the Select a category list, select SharePoint.
Below the Select a crawled property list, click Next, which is represented by a right-pointing arrow
below the list.
11. In the Select a crawled property list, click ows_Summary(Text).
Note: If you do not see ows_Summary(Text) in the list, you must reindex your content source and wait
for it to show up on this page.
12. Click OK.
13. Select the Allow this property to be used in scopes option, and then click OK.
11
12

1.
2.

Point at Local SharePoint sites, click the drop-down arrow, and then click Start Full Crawl.

Note: Continue to the next task while the crawl proceeds.
f Task 5: Modify a Search Center to support the managed property

1.
2.
3.
4.
5.
Switch to the instance of Internet Explorer that displays the Shared Documents document library.
In the address bar, type http://intranet.contoso.com/sites/IT/Search, and then press ENTER.
Next to the search box, click Advanced.
Click Site Actions, and then select Edit Page.
In the Advanced Search Box Web Part, point at Advanced Search Box Web part Menu, click the
drop-down arrow, and then click Edit Web Part.
The Advanced Search Box Web Part properties panel appears.
6.
7.
8.
Expand the Properties section.

Click in the Properties box, and then click the Click to use builder button, which is displayed as a
button with an ellipsis ().
Locate the <PropertyDefs> tag.
Tip: It is near the middle of the file.

9.
After the <PropertyDefs> tag, before the first <PropertyDef> element, add the following text:
<PropertyDef Name="ContosoSummary" DataType="text" DisplayName="Summary"/>
10. Locate the <ResultTypes> tag, locate the <ResultType> element <ResultType DisplayName="All
Results" Name="Default">, and then locate the end of that element, which is the next
</ResultType> tag.
11. Before the </ResultType> tag you located in the previous step, add the following text:
<PropertyRef Name="ContosoSummary"/>
12. In the Text Editor dialog, click OK.

13. In the Advanced Search Box properties panel, click OK.
14. On the ribbon, click Save & Close.
f Task 6: Test the managed property and modified Search Center

1.
2.
3.

column of the Local SharePoint sites row displays Idle.
4.
5.
6.
13
In the address bar, type http://intranet.contoso.com/sites/IT/Search, and then press ENTER.

On the Advanced Search page, in the Add property restrictions section, in the (Pick Property) list,
select Summary, and then type Contoso in the text box.
Click Search.
The file IT Policies and Procedures for SharePoint 2010 is listed as the result.
14

f Task 1: Create a search scope
1.
2.
3.
4.

In the Quick Launch, in the Queries and Results section, click Scopes.
Click New Scope.
In the Title box, type Shared Files, and then click OK.
f Task 2: Configure a search scope rule

1.
2.
3.
4.
5.
6.
7.
8.
On the Shared Files row, click Add rules.

In the Scope Rule Type section, click Content Source.
In the Content Source list, select Shared Folder Data, and then click OK.
Observe that the Shared Files row indicates that the scope will be ready after the next update.
In the Quick Launch, in the Administration section, click Search Administration.
In the Scopes needing update row, click Start update now.
In the Quick Launch, in the Query and Results section, click Scopes.
Above the list, click Refresh. Repeat this step until the Update Status column of the Shared Files
row indicates that the scope is Ready.
Wait until the scope is updated before continuing to the next task.
f Task 3: Add the custom search scope to a site

1.
2.
3.
4.
5.
6.
7.
In the Site Collection Administration section, click Search settings.
In the Site Collection Search Center section, click Enable custom scopes.
In the text box, type http://intranet.contoso.com/sites/IT/Search/Pages.
In the Site Collection Search Dropdown Mode section, select Show scopes dropdown, and then
click OK.
8. In the Site Collection Administration section, click Search Scopes.
9. Click Display Groups.
10. Click Search Dropdown.
11. Select the Shared Files option, and then click OK.
f Task 4: Test the custom search scope

1.
2.
In the global navigation, click the Information Technology tab.

In the Search box, type sharepoint, and then press ENTER.
Many results are listed, including both documents in the shared folder and items from SharePoint
sites.
3.
4.
Click the Back button on the browser to return to the Information Technology Web home page.
In the Search Scope list, which displays All Sites by default, select Shared Files.
Note: If you do not see Shared Files, you need to wait for the scope to be updated.
5.
In the Search box, type sharepoint, and then press ENTER.

The files sharepoint search.txt and sharepoint governance checklist.pdf are listed as the only results.
15
Do not turn off the virtual machines. You use the same virtual machines in the next lab.
Lab Review
Question: In what scenarios would you create a crawl rule?
Answer: Answers may vary. A common scenario is a requirement to use an account other than the default
crawl account to index content. Another common scenario is a requirement to exclude a subset of data in a
content source from indexing.
Question: You have added documents from a popular application to a SharePoint document library, but they
are not being indexed. What must be done to ensure that a file is indexed both for its attributes and content?
Answer: A file type must be added, and an iFilter must be installed.
Question: You have extended a Web application and now search results are listed twice with different URLs.
How can you prevent this duplication of results?
Answer: Create a server mapping that replaces the URL of results from the extended Web application with the
URL of the original Web application, effectively hiding the duplicate results.
Question: Users want to be able to search list items based on a custom column in the list. How can you
accomplish this and make it easy for users to perform the queries in the user interface without typing
property:value search syntax?
Answer: Create a managed property for the custom column. Then, customize the Search Center to support
queries based on the new property.
Question: Users are complaining that too many results are being returned. How can you provide users a way
to narrow down their search results?
Answer: Implement search scopes that target specific sets of data.
16

f Task 1: Create a Best Bet
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
In the Site Collection Administration section, click Go to top level site settings.
In the Site Collection Administration section, click Search keywords.
Click Add Keyword.
In the Keyword Information section, in the Keyword Phrase box, type SharePoint.
In the Best Bets section, click Add Best Bet.
In the URL box, type http://sharepoint.microsoft.com.
In the Title box, type Microsoft SharePoint Server Home Page, and then click OK.
In the Keyword Definition box, type Microsoft SharePoint Server is the business collaboration
platform for the enterprise and the Internet, and then click OK.
f Task 2: Test Best Bets

1.
2.
3.
In the global navigation, click the Information Technology tab.

In the search box, type sharepoint, and then press ENTER.
Confirm that the Best Bet you configured in Task 1 precedes the query-based search results.
f Task 3: Customize the presentation of Best Bets

1.
2.
On the search results page, click Site Actions, and then click Edit Page.
In the Search Best Bets Web Part, click the drop-down arrow, Search Best Bets Web Part Menu,
and then click Edit Web Part.
The Search Best Bets Web Part properties panel appears.
Tip: You might need to scroll to the right, and to the top, to see the properties panel.
3.
4.
In the properties panel, click XSL Editor.

Locate the line that matches the following:
5.
Update the Extensible Stylesheet Language (XSL) template starting with that line and ending with the
line </xsl:template> to the following:
<xsl:if test="$DisplayBB = 'True'" >
<xsl:if test="position() <= $BBLimit" >
<xsl:variable name="url" select="url"/>
<xsl:variable name="id" select="id" />
These are the results that the Contoso Search Team recommends, based on your
query. 
<xsl:if test="$DisplayTitle = 'True'" >

<img src="/_layouts/images/star.gif" alt="" />


<a href="{$url}" id="{concat('BBR_',$id)}">
<xsl:value-of select="title"/>
</a>
 

</xsl:if>
<xsl:if test="$DisplayDescription = 'True' and description[. != '']" >
<div class="srch-BB-Description">
<xsl:value-of select="description"/>
 
</div>
</xsl:if>
<xsl:if test="$DisplayUrl = 'True'" >

<a href="{$url}" id="{concat('BBR_U_',$id)}" dir="ltr">
<xsl:value-of select="$url"/>
</a>

 
 
</xsl:if>
</xsl:if>
</xsl:if>
</xsl:template>
6.
7.
8.
Click Save.
In the Search Best Bets Web Part properties panel, click OK.
On the ribbon, click Save & Close.
f Task 4: Test the customized presentation of Best Bets

The new text appears in the Best Bet Web Part: These are the results that the Contoso Search Team
recommends, based on your query.
17
18

f Task 1: Perform searches with the default thesaurus
1.
2.
Search results appear.
3.
Write down the number of results that appear.
4.
In the search box, type MOSS, and then press ENTER.

No search results are found.
5.
6.
7.
8.
In the search box, type WSS, and then press ENTER.

In the search box, type SharePoint Foundation, and then press ENTER.
f Task 2: Edit a thesaurus file

1.
Open the folder C:\Program Files\Microsoft Office Servers\14.0\Data

\Office Server\Applications\GUID-query-0\Config.
Tip: You need to expand the Name column in Windows Explorer to see the full name of the folders.
2.
3.
Right-click tsenu.xml, and then click Edit.

Replace the contents of the file with the following:
<XML ID="Microsoft Search Thesaurus">
<thesaurus xmlns="x-schema:tsSchema.xml">
<diacritics_sensitive>0</diacritics_sensitive>
<replacement>
<pat>MOSS</pat>
SharePoint
</replacement>
<expansion>
WSS
SharePoint Foundation
</expansion>
</thesaurus>
</XML>
4.
5.

Close Notepad.

1.
Run Command Prompt as administrator.

2.
3.
Click Yes.
net stop osearch14
net start osearch14
f Task 4: Test Search with the modified thesaurus

1.
2.
Search results appear.
3.
Write down the number of results.
4.
5.
In the search box, type MOSS, and then press ENTER.

Verify that the number of results is equal to the number of results returned when you searched for
sharepoint.
Search results appear because searching for MOSS now produces search results for SharePoint
through replacement.
6.
7.
In the search box, type WSS, and then press ENTER.

Write down the number of results.
More results appear than in Task 1 because searching for WSS also returns results for the term
SharePoint Foundation as a result of expansion.
19
20

f Task 1: Perform a search
In the search box, type dirty, and then press ENTER.

The announcement Mud is dirty is returned as a result.
f Task 2: Update a noise words file

1.
2.
3.
Switch to the instance of Windows Explorer that displays the Config folder.
Right-click noiseenu.txt, and then click Edit.
Add the following line to the end of the file:
dirty
4.
5.

Close Notepad.

1.
2.

net stop osearch14
net start osearch14
f Task 4: Test the noise word

1.
2.
In the search box, type dirty, and then press ENTER.
Note: In a production environment, you should consider reindexing all content after modifying the
noise word file so that the words are removed from the index itself.

following steps:
1.
2.
3.

Lab Review
Question: Describe the two functions of synonyms in a thesaurus file.
Answer: A query keyword can be replaced with another keyword to yield a more accurate result set. A
query keyword can be used along with its synonyms to yield an expanded result set.
Lab Answer Key: Implementing Office Web Apps
Module 11
Contents:
Exercise 2: Configuring and Testing the Office Web Apps in

a Document Library
Lab: Implementing Office Web Apps

1.
2.

f Task 1: Install Microsoft Office Web Apps
1.
2.

Open Windows Explorer, and then browse to and double-click D:\Labfiles\Lab11\Setup.exe.
3.
4.
5.
6.
7.
8.
Click Yes.
On the Enter your Product Key page, type BFGMH-8RM8J-JWMCQ-P784Q-F7R2Y.
Click Continue.
Select the I accept the terms of this agreement check box.
Click Continue.
Click Install Now.
The Microsoft Office Web Apps are installed.
9.
On the Run Configuration Wizard page, leave the check box selected, and then click Close.
The Microsoft SharePoint Products Configuration Wizard appears.
10. On the Welcome page, click Next.

A message appears informing you that services will be restarted.
11. Click Yes.
SharePoint is configured to support the Microsoft Office Web Apps.
13. On the Configuration Successful page, click Finish.
14. Close the Windows Explorer window that is showing the Lab11 folder.
f Task 2: Configure Office Web Apps service applications

1.
2.
On the Initial Farm Configuration Wizard page, click Start the Wizard.
Click Next.
Service applications for Office Web Apps are created and configured.
3.
4.
5.
6.
On the Create Site Collection page, click Skip.

Click Finish.
7.
Confirm that the following services are started, and if they are not, then start them by clicking Start:
Microsoft Office PowerPoint Service
Microsoft Office Excel Calculation Services

Microsoft Office Word Viewing Service
f Task 3: Assign Office Web Apps service application connections

1.
2.
3.
4.
5.

On the Service Application Associations page, click default.
Ensure that both PowerPoint Service Application and Word Viewing Service check boxes are
selected.
Click OK.
Exercise 2: Configuring and Testing the Office Web Apps in a Document Library
f Task 1: Configure documents to open in a browser
1.
In the Microsoft Internet Explorer address bar, type http://intranet.contoso.com/sites/IT, and

then press ENTER.
2. If you get an error, it is memory related; just click Go back to Site.
4. In the Site Collection Administration section, click Site collection features.
5. In the Office Web Apps row, click Activate.
6. In the Quick Launch, click Shared Documents.
7. On the ribbon, click the Library tab.
8. Click Library Settings.
9. Click Advanced Settings.
10. In the Opening Documents in the Browser section, click Open in the browser.
11. Click OK.
f Task 2: Create and upload a PowerPoint presentation

1.
Click Start, click All Programs, click Microsoft Office, and then click Microsoft PowerPoint 2010.
Microsoft PowerPoint opens.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
On the title slide, click the title placeholder, and then type Marketing Strategy.
Press CTRL+M to create a new slide, and then type Product.
Press CTRL+M to create a new slide, and then type Pricing.
Press CTRL+M to create a new slide, and then type Packaging.
Press CTRL+M to create a new slide, and then type Positioning.
In the Save As dialog box, click Save.
Minimize, but do not close PowerPoint.
Click Add document.
Click Browse.
In the navigation pane, click Documents and then click Marketing Strategy, and then click Open.
Click OK.
The document is uploaded to the shared documents library.
The shared documents library page refreshes and the presentation, Marketing Strategy, appears.
f Task 3: Create and save a Word document

1.
Click Start, click All Programs, click Microsoft Office, and then click Microsoft Word 2010.
Microsoft Word opens.
2.
3.
4.
5.
In the Styles gallery, click Heading 1.

Type SharePoint Governance Plan, and then press ENTER.
Click File, and then click Save & Send.
Click Save to SharePoint, and then click Save As. In the File name box, type
http://intranet.contoso.com/sites/IT/Shared Documents, and then click Save.
Wait for the Windows Security dialog box to appear. This takes approximately one minute.
6.
7.
8.

Click OK.
If necessary, click Shared Documents to open the Information Technology Shared Documents
document library.
9.
10.
11.
12.
13.
Click Save.
On the ribbon, click File, and then click Close.
Close Microsoft Word.
In the Quick Launch, click Shared Documents to refresh the view of the document library.
The document, SharePoint Governance Plan, appears in the Shared Documents library.
f Task 4: Test the functionality of Office Web Apps

1.
Click SharePoint Governance Plan.

After a few moments, the document opens in the browser in view mode. If you get an error, try again.
2.

The document opens in edit mode.
3.
4.
5.

Click File, and then click Close.
Click Marketing Strategy.
The presentation opens in the browser in view mode.
6.

The presentation opens in edit mode.
7.
8.
9.
10.
11.
12.
13.
14.
15.
On the ribbon, click New Slide.

In the New Slide dialog box, click Title and Content, and then click Add Slide.
Click Click to add title.
Type Market Demographics.
On the ribbon, click the View tab.
Click Slide Show.
Click each slide to advance to the following slide.
Click the black slide at the end of the presentation to exit.
Click File, and then click Close.
Results: After completing this exercise, you should have tested the functionality of Office Web Apps.

following steps:
1.
2.
3.

Lab Review
Question: Describe the business scenarios for which Office Web Apps are useful.
Answer: Answers will vary, but may include responses from users on non-Windows platforms who require
the ability to view and edit Word, PowerPoint, and Excel documents; scenarios in which multiple users
need to collaborate and make concurrent edits to documents; users who do not have the Microsoft Office
client applications installed; and remote users working from computers without Office client applications.
Lab Answer Key: Installing and Upgrading to SharePoint 2010
Module 12
Lab Answer Key: Installing and Upgrading to SharePoint
2010
Contents:
Lab A: Preparing SharePoint 2007 for Upgrade to SharePoint 2010
Lab B: Upgrading SharePoint 2007 to SharePoint 2010

11
13
Lab A: Preparing SharePoint 2007 for Upgrade

to SharePoint 2010
1.
2.
Start 10174A-CONTOSO-DC-F.
After CONTOSO-DC has completed startup, start 10174A-SP2007-WFE1-F.

f Task 1: Clean up databases
1.
2.
3.
4.
5.
6.
7.

Management Studio.
Click Connect.
Click File, click Open, and then click File.
Select D:\Labfiles\Lab12\DefragIndexes.sql, and then click Open.
In the Available Databases list on the toolbar, select WSS_Content_Intranet.
Click Execute.
When the query is complete, the status below the Results panel indicates Query executed successfully.
You may have to expand the results window to see the results.
8.
Repeat steps 67 for the following databases. When you are finished, close the SQL Server
Management Studio.
WSS_Content_MySites.
SharePoint_AdminContent_GUID.
SharePoint_Config.
f Task 2: Confirm sufficient free disk space

1.
2.
3.
Click Start, and then click Computer.

Confirm that there is at least 20 gigabytes of free disk space on C drive.
Close the Windows Explorer window that displays the Computer folder.

1.
2.
3.
4.
5.
6.
7.
Click Start, click All Programs, click Microsoft Office Server, and then click SharePoint 3.0 Central
Administration. If prompted for credentials, provide Contoso\Administrator and the password
Pa$$w0rd.
Click the Application Management tab.
In the SharePoint Site Management section, click Create site collection.
In the Web Application section, ensure that http://intranet.contoso.com/ is selected.
In the Title box, type Sales.
In the URL box, type Sales.
CONTOSO\SP_Admin, and then click OK.
f Task 2: Create a new content database

1.
2.
3.
4.

In the Database Name box, type WSS_Content_Intranet_Sales, and then click OK.
f Task 3: Move a site collection between content databases

1.
2.

To export an Extensible Markup Language (XML) listing of sites in the intranet Web application, type
the following command and press ENTER:
C:\SiteList.xml
3.
To open the site listing in Notepad, type the following command and press ENTER:
4.
Delete the following two elements (the entire line of XML):
Site Url="http://intranet.contoso.com"
Site Url="http://intranet.contoso.com/sites/IT"
Confirm that the only remaining Site element is for the Sales site collection.
5.
6.
7.
8.

Close Notepad.
To move the Sales site collection from the WSS_Content_Intranet content database to the
WSS_Content_Intranet_Sales content database, type the following command and then press ENTER:
Extensions\12\Bin\stsadm.exe" -o mergecontentdbs -url http://intranet.contoso.com sourcedatabasename WSS_Content_Intranet -destinationdatabasename
WSS_Content_Intranet_Sales -operation 3 -filename C:\SiteList.xml
9.
To restart Internet Information Services (IIS), type the following command:
iisreset
f Task 4: Verify and report the move of the site collection

1.
Switch to Internet Explorer. Press F5 to refresh the page.

If the Windows Security dialog opens, type CONTOSO\Administrator in the User name box, type
Pa$$w0rd in the Password box, and then click OK.
2.
3.
4.
Observe that the WSS_Content_Intranet_Sales content database now contains one site.
To export an XML listing of sites in the intranet Web application, type the following command:
C:\SiteList.xml
5.
To open the site listing in Notepad, type the following command:

6.
7.
8.
9.
Click Format, and then click Word Wrap.

Observe the information that is reported for each site collection, including the owner (primary site
collection administrator), content database, and storage utilization.
Close Notepad.
Close the command prompt.

f Task 1: Back up SharePoint databases using SQL Server
1.
2.
3.
4.
5.
6.
Open Windows Explorer and browse to C drive.

Type Backups, and then press ENTER.
Management Studio.
Click Connect, and then click New Query.
Type the following query into the query editor panel:
use WSS_Content_Intranet
go
backup database WSS_Content_Intranet to disk = 'C:\Backups\WSS_Content_Intranet.bak'
go
backup log WSS_Content_Intranet to disk = 'C:\Backups\WSS_Content_Intranet_log.bak'
go
go
7.
8.
9.
Click the Execute button.

Confirm that at the bottom of the Results panel, the status indicates Query executed successfully.
Repeat the preceding steps to back up and truncate the WSS_Content_Intranet_IT database. Use the
following query:
use WSS_Content_Intranet_IT
go
backup database WSS_Content_Intranet_IT to disk =
'C:\Backups\WSS_Content_Intranet_IT.bak'
go
backup log WSS_Content_Intranet_IT to disk =
'C:\Backups\WSS_Content_Intranet_IT_log.bak'
go

go
10. Repeat the preceding steps to back up and truncate the WSS_Content_Intranet_Sales database. Use
the following query:
use WSS_Content_Intranet_Sales
go
backup database WSS_Content_Intranet_Sales to disk =
'C:\Backups\WSS_Content_Intranet_Sales.bak'
go
backup log WSS_Content_Intranet_Sales to disk =
'C:\Backups\WSS_Content_Intranet_Sales_log.bak'
go
go
11. Repeat the preceding steps to back up and truncate the WSS_Content_MySites database. Use the
following query:
use WSS_Content_MySites
go
backup database WSS_Content_MySites to disk = 'C:\Backups\WSS_Content_MySites.bak'
go
backup log WSS_Content_MySites to disk = 'C:\Backups\WSS_Content_MySites_log.bak'
go
go
12. Open the C:\Backups folder.
13. Confirm that the database and log backup files were created.
14. Close the C:\Backups folder.
15. Close SQL Server Management Studio. When prompted to save your changes, click No.
f Task 2: Back up a SharePoint 2007 farm using Central Administration

1.
2.
3.
4.
5.
6.
7.
Switch to SharePoint 3.0 Central Administration.

In the Quick Launch, click Operations.
In the Backup and Restore section, click Perform a backup.
Select the check box next to Farm.
Click Continue to Backup Options.
In the Backup location box, type C:\Backups.
Do not perform a backup at this time. Click Cancel.
f Task 3: Detach content databases

1.
2.
3.
4.
5.
6.

In the SharePoint Web Application Management section, click Web application list.
Click the database name of the first-listed content database.
Select the Remove content database option.
A confirmation message appears.
7.
8.
Click OK.
Click OK.
The content database is removed.
9. Repeat steps 58 for each content database.

10. Repeat steps 19 for the Web application SharePoint - mysites.contoso.com80.
11. Close SharePoint 3.0 Central Administration.

f Task 1: Perform a preupgrade check
1.
2.

Extensions\12\Bin\stsadm.exe" -o preupgradecheck
A report opens in Windows Internet Explorer.

3.
4.
5.
6.
7.

Review the output of the command.
Review the report.
f To prepare for the next lab

1.
2.
Turn off 10174A-SP2007-WFE1-F. Leave 10174A-CONTOSO-DC-F running.

Start and connect to 10174A-SP2007-WFE1-G.
Lab Review
Question: Why did you defragment the database indexes before the upgrade?
Answer: A fragmented database means the upgrade will take longer. By reducing the database
fragmentation, you speed up the movement from one database schema to another.
Lab B: Upgrading SharePoint 2007 to

SharePoint 2010
1.
2.
Start 10174A-CONTOSO-DC-F.
After CONTOSO-DC has completed startup, start 10174A-SP2007-WFE1-G.

f Task 1: Run the SharePoint Products Configuration Wizard
Note: To save time the actual installation of Microsoft SharePoint 2010 has already been completed
on 10174A-SP2007-WFE1-G. You use this virtual machine for the remainder of the lab.
1.
2.
3.

Click Start, point to All Programs, click Microsoft SharePoint 2010 Products, and then click
4.
5.
Click Yes.
On the Specify Farm Security Settings page, type 10174_SharePoint_2010 in the Passphrase and
Confirm passphrase boxes.
6. Click Next.
7. On the Visual Upgrade page, review the message and options.
8. Click Preserve the look and feel of existing SharePoint Sites, and allow end users to update
their sites user experience.
9. Click Next.
A SharePoint Products Configuration Wizard message opens.
The message reminds you to install the binaries on all servers in the farm before you run the wizard.
11. Click OK.
SharePoint 2010 is configured.
12. On the Configuration Successful, Upgrade In Progress page, read the message, and then click
Finish.
f Task 2: Validate the upgrade

1.
In SharePoint 2010 Central Administration, on the Upgrade Status page, confirm that Status is
Succeeded.
Note: You might need to wait a few minutes before the upgrade completes. Press F5 to refresh the
page, and then return to step 1.
10
2.
Observe the number of Errors and Warnings.

There should be no errors. However, warnings are expected.
3.
4.
5.
Identify the Log File that contains a record of events during the upgrade.
Open the log file in Notepad.
Press CTRL+F, and then type [Warning].
Tip: Include the brackets.

6.
7.
8.
Read the first warning message.

Press F3 to locate the next warning message, and then read the message. Repeat this step for all
warning messages.
Close Notepad.

f Task 1: Attempt to attach a content database
1.
2.
3.
4.
5.

In the Database Name box, type WSS_Content_Intranet, and then click OK.
An error page opens that explains you must use the addcontentdb operation of Stsadm.exe or the
Mount-SPContentDatabase cmdlet of Windows PowerShell to attach and upgrade a content
database.
6.
f Task 2: Attach content databases using Windows PowerShell

1.
2.

Mount-SPContentDatabase "WSS_Content_Intranet" -DatabaseServer SP2007-WFE1 WebApplication http://intranet.contoso.com
Mount-SPContentDatabase "WSS_Content_Intranet_IT" -DatabaseServer SP2007-WFE1 WebApplication http://intranet.contoso.com
Mount-SPContentDatabase "WSS_Content_Intranet_Sales" -DatabaseServer SP2007-WFE1 WebApplication http://intranet.contoso.com
f Task 3: Verify the database upgrade

1.
2.
3.

In the Upgrade and Patch Management section, click Check upgrade status.
The Upgrade Status page appears.
4.
5.
6.
Click the first item in the Upgrade sessions list.

Identify the Starting object for the upgrade session.
Observe the number of errors and warnings.
Note: There should be no errors, but warnings are expected.

7.
Repeat steps 46 for each upgrade session.
f Task 4: Verify the database attach

1.
2.

The Manage Content Databases page opens.
3.
4.
5.
Confirm that three databases are attached to the intranet Web application.
11
12
6.
7.
Click WSS_Content_Intranet.
In the Database Versioning section, confirm that the
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version is
14.0.4762.1000.
f Task 5: Verify database upgrade status

1.
2.
3.
4.
5.

In the Upgrade and Patch Management section, click Check product and patch installation
status.
Confirm that all products are listed as Installed with a version of 14.0.4763.1000.
In the Upgrade and Patch Management section, click Review database status.
The Manage Databases Upgrade Status page opens.
6.
Confirm that the Status for all databases is No action required.

If they are not yet upgraded, your upgrade process is still running.

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
In the Quick Launch, click Configuration Wizards.

Click Yes, I am willing to participate (Recommended), and then click OK.
Click Start the Wizard.
Click Next.
Click Skip.
Click Finish.
13

f Task 1: Validate the SharePoint 2007 user interface
1.
2.
3.
4.
5.
6.

In the address bar, type http://intranet.contoso.com/sites/IT, and then press ENTER. If you
receive an error, click Go back to site.
Click Welcome Contoso\Administrator, and then click Sign in as Different User.
Log on as Contoso\SP_Admin with the password Pa$$w0rd.
f Task 2: Preview the SharePoint 2010 user interface

1.
2.
3.

Click the Preview the updated user interface option, and then click OK.
Observe the new SharePoint 2010 user interface.
f Task 3: Revert to the SharePoint 2007 user interface

1.
2.
3.
4.
5.
In the information bar, click View or modify this sites Visual Upgrade settings.
Click Use the previous user interface, and click OK.
Click the Home tab.
f Task 4: Upgrade to the SharePoint 2010 user interface

1.
2.

Click Update the user interface, and then click OK.
The site is updated to the new SharePoint 2010 look and feel.
3.
Click Site Actions, and then observe that the Visual Upgrade command no longer appears.

following steps:
1.
2.
3.

Lab Review
Question: Why did you detach the content databases before the upgrade?
Answer: Although the content databases in this lab are small, the ones you may have in production could
be very large. Rather than upgrade in place, you can use the database attach approach to migrate the
content one database, or many, at a time.
Question: Why would you want to choose the visual upgrade approach?
Answer: Some customization may not work properly with the new master pages of SharePoint 2010. By
doing a visual upgrade, you can keep the old look and test the new look and feel for any incompatibilities.
Lab Answer Key: Implementing Business Continuity
Module 13
Contents:

10
12

1.
2.
Start 10174A-CONTOSO-DC-E.
After CONTOSO-DC has completed startup, start 10174A-SP2010-WFE1-E.

f Task 1: Create a backup share
1.
2.
3.
4.
5.
6.
7.
8.
9.

Open Windows Explorer and then browse to the C: drive.
Type SharePointBackup, and then press ENTER.
Right-click SharePointBackup, and then click Properties.
Click the Security tab.
Click Edit.
In the Group or user names list, select Users.
Select the Allow check box next to Full control.
Note: In a production environment, you should configure NTFS permissions that ensure the least
privilege access to the folder. The service account that performs the backup operation should be given
Full Control permission to the backup share.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Click OK.
Click the Sharing tab.
Click Advanced Sharing.
Select the Share this folder check box.
Click Permissions.
Select Allow check box next to Full Control.
Click OK.
Click OK.
Click Close.
f Task 2: Back up a Web application with Central Administration

1.

2.
3.
4.
Click Yes.
In the Quick Launch, click Backup and Restore.
In the Farm Backup and Restore section, click Perform a Backup.
The Perform a Backup Step 1 of 2: Select Component to Back Up page opens.
5.
Observe the components that can be backed up:
Farm
Various solutions and services
Microsoft Office InfoPath Forms Services
SharePoint Server State Service
6.
7.
Microsoft SharePoint Foundation Web Application(s)

WSS_Administration
SharePoint Server State Service Proxy
SPUserCodeV4
Global Search Settings
Application Registry Service
Shared Services
Select the SharePoint intranet.contoso.com80 check box.

Click Next.
The Perform a Backup Step 2 of 2: Select Backup Options page opens.
8.
9.
In the Backup Type section, click Full.

In the Backup location box, type \\SP2010-WFE1.contoso.com
\SharePointBackup.
10. Click Start Backup.
A timer job is created to perform the backup of the selected item(s).
11. Wait until Phase shows as Completed.
Note: The backup operation may complete with warnings. This is expected in this lab. You may
continue to the next step.

1.
2.
3.
Switch to Windows Explorer, and then open the C:\SharePointBackup folder.

Right-click Spbrtoc.xml, and then click Edit.
Examine the file, which is similar to the following:
<?xml version="1.0" encoding="utf-8"?>
<SPBackupRestoreHistory>
<SPHistoryObject>
<SPId>GUID of operation/SPId>
<SPRequestedBy>CONTOSO\SP_Admin</SPRequestedBy>
<SPBackupMethod>Full</SPBackupMethod>
<SPRestoreMethod>None</SPRestoreMethod>
<SPStartTime>Start Date and time</SPStartTime>
<SPFinishTime>End Date and time</SPFinishTime>
<SPIsBackup>True</SPIsBackup>
<SPConfigurationOnly>False</SPConfigurationOnly>
<SPBackupDirectory>\\SP2010-WFE1.contoso.com\
SharePointBackup\
spbr0000\</SPBackupDirectory>
<SPDirectoryName>spbr0000</SPDirectoryName>
<SPDirectoryNumber>0</SPDirectoryNumber>
<SPTopComponent>Farm\Microsoft SharePoint Foundation
Web Application\SharePoint
intranet.contoso.com80</SPTopComponent>
<SPTopComponentId>GUID of top component</SPTopComponentId>
<SPWarningCount>1</SPWarningCount>
<SPErrorCount>0</SPErrorCount>
</SPHistoryObject>
</SPBackupRestoreHistory>
4.
Locate the SPHistoryObject element.

This element describes the backup operation, and is used during a restore operation.
5.

6.

These elements report warnings and errors.
7.
8.
9.
10.
11.
Close Microsoft Notepad.

In Windows Explorer, open the spbr0000 folder.
Observe the backup (*.bak) files in the folder.
Right-click Spbackup.xml, and then click Edit.
Examine the Spbackup.xml file.
This file contains attributes related to the backup operation and to each of the components. It is used
during a restore operation. You should not modify, delete, or rename the Spbackup.xml file.
12. Close Notepad.
f Task 2: Identify backup warnings and errors in the backup log

1.
2.
Double-click spbackup.log.
Examine the log. Observe that each of the backup operations is listed, including the T-SQL commands
that were sent to Microsoft SQL Server.
3.
4.
5.
6.
Press CTRL+END to navigate to the end of the log.

Press CTRL+HOME to navigate to the top of the log.
Press CTRL+F, type Warning:, and then press ENTER.

7.
8.
9.
10.

Press CTRL+F, then type BACKUP DATABASE, and then press ENTER.
Observe the command that was sent to SQL Server to back up one of the SharePoint databases.

11. Press F3 to find the next instance of the text, BACKUP DATABASE. Repeat this step as necessary to
locate the backup command that was used to back up the WSS_Content_Intranet_IT database.
Answer the following question:
Which database backup (.bak) file in the backup folder contains that SharePoint database? Write
down the file name. You will need it in Lab 13B.
12. Close Notepad.

f Task 1: Create a backup script
1.
2.
3.
4.
5.
Open Windows Explorer and then browse to the C: drive.

Type Scripts, and then press ENTER.
Open Notepad.
Type the following text:
Backup-SPFarm -directory \\SP2010-WFE1.contoso.com\SharePointBackup -backupmethod Full
6.
7.
8.

In the File name box, type c:\scripts\backup.ps1, and then press ENTER.
Minimize, but do not close, Notepad.
f Task 2: Schedule the backup script

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
Click Start, point to Administrative Tools, and then click Task Scheduler.
In the Actions panel, click Create Basic Task.
On the Create Basic Task page, in the Name box, type
Backup SharePoint - FULL.
In the Description box, type Back up the SharePoint farm.
Click Next.
On the Trigger page, click Daily.
Click Next.
On the Daily page, configure the Start time to 1:00 AM.
Click Next.
On the Action page, click Start a program.
Click Next.
On the Start a Program page, in the Program/script box, type PowerShell.exe.
In the Add arguments (optional) box, type C:\Scripts\backup.ps1.
Click Next.
On the Summary page, select the Open the Properties dialog for this task when I click Finish
check box.
Click Finish.
Click Change User or Group.
Type CONTOSO\SP_Farm and then click OK.
On the General tab, in the Security options section, click Run whether user is logged on or not.
Select the Run with highest privileges check box.
Click OK.
The Task Scheduler dialog box appears.
22. In the Password box, type Pa$$word.

23. Click OK.
f Task 3: Test the scheduled backup task

1.
2.
3.
In the console tree, click Task Scheduler Library.

Right-click Backup SharePoint FULL, and then click Run.
Open the C:\SharePointBackup folder.
4.
Observe that a new backup folder, spbr0001, is created.
Tip: It may take up to 60 seconds for the script to call the backup APIs, and for the new backup folder
to appear.
The operation to perform a full backup of the entire farm can take up to 30 minutes to complete.
Tip: You may continue to the next task.
f Task 4: Monitor the backup operation

1.
2.
3.

Click Check backup and restore job status.
The Backup and Restore Job Status page opens.
4.
5.
6.
7.
8.
9.
Examine the information that is presented on the Backup and Restore Job Status page.
Click View History.
Examine the information that is presented on the Backup and Restore History page.
Click Backup and Restore Job Status to return to the status page.
Wait for the Phase to be Completed before continuing to the next lab.
Do not turn off the virtual machines. Allow the backup operation to continue until it has completed.
You will use the same virtual machines in the next lab to perform restore operations.
Lab Review
Question: Does SharePoint automatically clean your Spbrtoc.xml file when you delete a corresponding
backup directory?
Answer: No, you are responsible for cleaning out any backup entries from this file. This can be done using
Windows PowerShell.

f Task 1: Delete a Web application
1.
2.
3.
4.
5.
6.
7.
8.
9.

Select the row, SharePoint - intranet.contoso.com80.
On the ribbon, click Delete.
The Delete Web Application page opens.
In the Delete content databases section, click Yes.
In the Delete IIS Web sites section, click Yes.
Click Delete.
10. Click OK.

The Web application is deleted.
f Task 2: Test the deleted Web application

1.
2.

An error page opens.
f Task 3: Restore a Web application using Central Administration

1.
2.
3.

In the Farm Backup and Restore section, click Restore from a backup.
The Restore from Backup Step 1 of 3 page opens.
4.
5.
Select the radio button next to Farm in the first (oldest) backup.
Click Next.
6.
7.
Select the check box next to SharePoint - intranet.contoso.com80.

Click Next.
8.
In the Restore Options box, click Same configuration.

9. Click OK.
10. In the Login Names and Passwords section, in the Password box, type Pa$$w0rd.
11. Click Start Restore.
A timer job is created to perform the restore of the selected item(s).
12. Wait until Phase shows as Completed.
f Task 4: Verify the restored Web application

1.
2.
Switch to the instance of Internet Explorer that displays the error page from Task 2.
After a few moments, the intranet site opens.
10

3.
4.
5.
6.
Open the c:\SharePointBackup folder.

Right-click Spbrtoc.xml, and then click Edit.
Examine the file, and identify the SPHistoryObject element that describes the restore operation.
Locate the SPRestoreMethod element.
This element describes the type of restore operation that was performed.
7.

8.
Locate the SPTopComponent element.

This element describes the top level component of the farm that was restored.
9.

These elements report warnings and errors. The same count was shown on the timer job status page
in the previous task.
10.
11.
12.
13.
Close Notepad.
In Windows Explorer, open the spbr0001 folder.
Right-click Sprestore.xml, and then click Edit.
Examine the Sprestore.xml file.
This file contains attributes related to the restore operation and to each of the components. You
should not modify, delete, or rename the sprestore.xml file.
14. Close Notepad.
f Task 2: Identify restore warnings and errors in the restore log

1.
2.
3.
4.
5.
Double-click Sprestore.log.
Press CTRL+END to navigate to the end of the log.
Press CTRL+F, then type Progress: Starting Restore, and then press ENTER.
This step locates the beginning of the restore operation.
6.
In the Find dialog box, in the Find what box, type Warning: and then press ENTER.

7.
8.
9.
10.

Press CTRL+F, then type RESTORE DATABASE, and then press ENTER.
Observe the command that was sent to SQL Server to restore one of the SharePoint databases.
11. Close Notepad.
11
12

f Task 1: Restore a content database
1.
Click Start, click All Programs, click Microsoft SQL Server 2008 R2, hold the SHIFT key and rightclick SQL Server Management Studio, and then click Run as different user.
2.
Enter the user name, CONTOSO\Administrator, and the password, Pa$$w0rd, and then click OK.
The Connect to Server dialog box appears.
3.
4.
5.
6.
7.
8.
Click Connect.
Expand Databases.
Right-click Databases, and then click Restore Database.
In the To Database box, type WSS_Content_Intranet_IT_Backup.
Click From device.
Click the browse button, which is displayed with ellipses ().
The Specify Backup dialog box appears.
9. Click Add.
10. Select C:\SharePointBackup\spbr0000\00000xxx.bak, where 00000xxx.bak is the backup of the
WSS_Content_Intranet_IT database that you identified in Lab A, Exercise 2, Task 2.
11. Click OK.
12. Click OK.
13. In the Select the backup sets to restore box, select the check box next to
Tip: If you do not see WSS_Content_Intranet_IT listed, it is because you did not restore the correct
database. Return to Lab A, Exercise 2, Task 2 to identify the database that contains
WSS_Content_Intranet_IT. Then repeat Task 1 of this exercise.
14. Click OK.
A message appears indicating that the restore operation was successful.
15. Click OK.
f Task 2: Delete a document library

1.
2.
3.
4.
5.
6.
Switch to the instance of Internet Explorer that displays the intranet site.
On the ribbon, click the Library tab.
Click Library Settings.
In the Permissions and Management section, click Delete this document library.
7.
Click OK.
f Task 3: Export a document library from an unattached content database

1.
2.
3.

In the Granular Backup section, click Recover data from an unattached content database.
The Unattached Content Database Recovery page opens.
4.
5.
6.
In the Database Name box, type WSS_Content_Intranet_IT_Backup.

In the Operation to Perform section, click Browse content.
Click Next.
The Browse content page opens.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
Click the Site Collection list, and then click Change Site Collection.
Click /sites/IT.
Click OK.
Click the Site list, and then click Change Site.
Click /sites/IT.
Click OK.
Click the List down list, and then click Change List.
Click the next page button, which is displayed as a right-pointing arrow in the upper-right corner of
the page.
Click Shared Documents.
Click OK.
Click Export site or list.
Click Next.
In the Filename box, type \\SP2010-WFE1.contoso.com\SharePointBackup
\ITSharedDocuments.cmp.
Select the Export full security check box.
Click Start Export.
The Granular Backup Job Status page appears
22. Press F5 to refresh the page. Monitor the Current Job section. Wait until Status is No operation in
progress.
23. Confirm that in the Previous Job section, Status is Succeeded. Repeat steps 22 and 23 until the
Status of the Previous Job is Succeeded.
f Task 4: Restore a deleted document library

1.
2.
Open SharePoint 2010 Management Shell as Contoso\SP_Farm with the password of Pa$$w0rd.
To do this, hold down the shift key, right click SharePoint 2010 Management Shell and then click
To import the document library, type the following command:
c:\SharePointBackup\ITSharedDocuments.cmp
13
14
f Task 5: Validate the restored document library

1.
2.
3.
Switch to the instance of Internet Explorer that displays the All Site Content page of the
Information Technology Web.
Confirm that the Shared Documents document library is restored.
f Task 6: Delete a list

1.
2.
3.
4.
In the Quick Launch, click Announcements.

On the ribbon, click the List tab.
Click List Settings.
In the Permissions and Management section, click Delete this list.
5.
Click OK.
f Task 7: Export a list from an unattached content database

1.
2.
3.

In the Granular Backup section, click Recover data from an unattached content database.
The Unattached Content Database Recovery page opens.
4.
5.
6.
In the Database Name box, type WSS_Content_Intranet_IT_Backup.

In the Operations to Perform section, click Browse content.
Click Next.
The Browse content page opens.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Click the Site Collection list, and then click Change Site Collection.
Click /sites/IT.
Click OK.
Click the Site list, and then click Change Site.
Click /sites/IT.
Click OK.
Click the List down list, and then click Change List.
Select Announcements.
Click OK.
Click Export Site or list.
Click Next.
In the Filename box, type \\SP2010-WFE1.contoso.com\SharePointBackup
\ITAnnouncements.cmp.
19. Select the Export full security check box.
20. Click Start Export.
The Granular Backup Job Status page appears
21. Press F5 to refresh the page. Monitor the Current Job section. Wait until Status is No operation in
progress.
22. Confirm that in the Previous Job section, Status is Succeeded. Confirm that the Completed time is
current, indicating that the job is the export job that you just performed. Repeat steps 21 and 22 until
the Status of the Previous Job is Succeeded, and the Completed time is current.
15
f Task 8: Restore a deleted list

1.
2.

To import the list, type the following command:
c:\SharePointBackup\ITAnnouncements.cmp
f Task 9: Validate the restored list

1.
2.
3.
Switch to the instance of Internet Explorer that displays the All Site Content page of the
Information Technology Web.
Confirm that the Announcements list is restored.

following steps:
1.
2.
3.

Lab Review
Question: Can you use Central Administration to restore a list to a site?
Answer: No, the out of the box Central Administration site does not have this functionality; you must use
the PowerShell cmdlet Import-SPWeb to restore the exported list.
Question: Can you restore a single document using Central Administration?
Answer: No, you cannot restore a single document. You would need to restore the library to a temporary
location and then download the item you are looking for.
Lab Answer Key: Monitoring and Optimizing SharePoint Performance
Module 14
Lab Answer Key: Monitoring and Optimizing SharePoint
Performance
Contents:



1.
2.

f Task 1: Configure diagnostic logging
1.
2.

Click Start, click All Programs, click Microsoft SharePoint 2010 Products, then click SharePoint
2010 Central Administration.
3.
4.
5.
Click Yes.
In the Reporting section, click Configure diagnostic logging.
The Diagnostic Logging page opens.
6.
In the Event Throttling section, observe the Category list.

This is the list of event categories, each of which can be configured independently for a desired level
of detail.
7.
8.
9.
Select the All Categories option.

In the Least critical event to report to the event log, select Verbose.
In the Least critical event to report to the trace log, select Verbose.
Note: It is not recommended you configure a trace log level of Verbose in a production environment.
10. In the Event Log Flood Protection section, select the Enable Event Log Flood Protection option.
Event log flood protection is a new setting that prevents the repetitive logging of redundant events.
11. In the Trace Log section, select the Restrict Trace Log disk space usage option.
12. In the Maximum storage space for Trace Logs (GB) box, type 10, and then click OK.
f Task 2: Review a log file

1.
2.
3.
4.
5.
6.
Open Windows Explorer and browse to the C:\Program Files\Common Files\Microsoft

Shared\Web Server Extensions\14\Logs folder.
Click the Date modified column to sort the files so that the newest files are listed first.
Open the most recently modified log (*.log) file.
Examine the log. Observe the number of events that are logged in just a few seconds.
Close the log.
Close the Windows Explorer window that displays the Logs folder.

1.

2.
3.
4.
Click Yes.
In the Health Analyzer section, click Review problems and solutions.
The Review Problems And Solutions page opens.
5.
Observe the list of reported problems.
f Task 2: Configure Health Analyzer rule definitions

1.
2.

In the Health Analyzer section, click Review rule definitions.
The Health Analyzer Rule Definitions page opens.
3.
Observe the four categories of rules:
Security4 rules
Performance17 rules
Configuration30 rules
Availability13 rules
Tip: The list of rules is paged. Click the Next Page button, displayed as a right-pointing arrow below
the list, to see additional rules.
4.
In the Availability section, click Some content databases are growing too large.
5.
6.
Click Edit Item.

Observe that you can change the following attributes of the rule, but do not make any changes at
this time:
Title
Scope
Schedule
Enabled
Repair Automatically
Version
Note: You cannot change the actions that the rule uses to perform its health analysis task. The rules
actions are determined by the code used to develop the rule.
7.
8.
Change the Schedule to Daily.

Click Save.
f Task 3: Run a Health Analyzer rule

1.
2.
3.
4.
5.
6.
7.
In the Availability section, click Some content databases are growing too large.
Click Run Now.
Click Close.
At the bottom of the list of rules, click the previous page link, which is displayed as a left-pointing
arrow.
In the Configuration section, click One or more categories are configured with Verbose trace
logging.
Click Run Now.
Click Close.

1.
2.

In the Health Analyzer section, click Review problems and solutions.
3.
4.
In the Configuration section, observe that a new problem is reported: One or more categories are
configured with Verbose trace logging.
Click One or more categories are configured with Verbose trace logging.
The problem details page opens.
5.
6.
7.
8.
Examine the information on the problem details page.

Click Reanalyze Now.
Click Close.
Press F5 to refresh the view of the page. Observe the Modified column for the problem. Repeat this
step until the Modified column indicates that the rule was analyzed.
f Task 2: Repair Health Analyzer problems

1.
2.
3.
4.
Click One or more categories are configured with Verbose trace logging.
Click Repair automatically.
Click Close.
Press F5 to refresh the view of the page. Repeat this step until the problem report disappears.
f Task 3: Validate the Health Analyzer solution

1.
2.

In the Reporting section, click Configure diagnostic logging.
The Diagnostic Logging page opens.
3.
4.
5.
6.
7.
Select the All Categories option.

Observe that the two lists, Least critical event to report to the event log and Least critical event
to report to the trace log, are reset. They no longer are set to Verbose.
In the Least critical event to report to the event log list, select Error.
In the Least critical event to report to the trace log list, select Unexpected, and then click OK.
In the Health Analyzer section, click Review rule definitions.
8.
In the Configuration section, click One or more categories are configured with Verbose trace
logging.
9. Click Run Now.
10. Click Close.
11. In the Quick Launch, click Monitoring.
12. In the Health Analyzer section, click Review problems and solutions.
13. Confirm that the report does not include the problem One or more categories are configured with
Verbose trace logging.
14. Close all open applications and windows.
Do not turn off the virtual machines. You use the same virtual machines in the next lab.
Lab Review
Question: How often do Health Analyzer rules run, and when might you want to run them manually?
Answer: Each rule has its own schedule. You can run a rule manually when you suspect a problem that is
evaluated by a rule. If the rule finds a problem, you can in some cases click the Repair Automatically
button to fix the problem.

f Task 1: Perform usage data collection
1.
2.
3.

In the Reporting section, click Configure usage and health data collection.
The Configure Web Analytics And Health Data Collection page opens.
4.
In the Health Data Collection section, click Health Logging Schedule.

The Job Definitions page opens.
5.
6.
Observe the set of Health Analysis jobs.

Click Health Analysis Job (Daily, Microsoft SharePoint Foundation Timer, All Servers).
The Edit Timer Job page opens.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Click Run Now.

In the Reporting section, click Configure usage and health data collection.
In the Log Collection Schedule section, click Log Collection Schedule.
Click Microsoft SharePoint Foundation Usage Data Import.
Click Run Now.
Click Microsoft SharePoint Foundation Usage Data Processing.
Click Run Now.
Results: After this exercise, you should have executed the logging timer jobs to populate the logging
database.

f Task 1: Explore logging database tables
1.
2.
3.
4.
5.
6.
7.

Management Studio.
In the Authentication list, select Windows Authentication.
Click Connect.
Expand Databases.
Expand WSS_Logging.
Expand Tables.
You should see several tables with different partition names.
8.
9.
On the toolbar, click New Query.

In the new query window, type the following query:
Use WSS_Logging
Select * from configuration where configname = 'max partition id - TimerJobUsage'
10. On the toolbar, click Execute.

11. Record the ConfigValue value that is displayed in the Results panel.
f Task 2: Create a logging report using Microsoft Excel

1.
Click Start, click All Programs, click Microsoft Office, and then click Microsoft Excel 2010.
Microsoft Office Excel opens.
2.
3.
4.
5.
On the ribbon, click File, and then click Save As.

In the File name box, type SharePoint Timer Job Duration Report, and then press ENTER.
On the ribbon, click Data.
Click From Other Sources, and then click From SQL Server.
The Data Connection Wizard appears.
6.
7.
8.
On the Connect To Database Server page, in the Server name box, type SP2010-WFE1.
Click Next.
On the Select Database And Table page, in the Select the database that contains the data you
want list, select WSS_Logging.
9. In the list of tables, select TimerJobUsage_PartitionXX table, where XX is the ConfigValue value
you obtained in Task 1.
10. Click Next.
11. On the Save Data Connection File And Finish page, click Finish.
The Import Data dialog box appears.
12. Click PivotTable Report, and then click OK.
13. In the PivotTable Field List panel, in the Choose fields to add to report list, select the following
options in the order listed:
MachineName
WebApplicationName
JobTitle
14. Drag the Duration field from the field list to the Values box.
You now have a report of timer job durations presented by server, by webapplication, and by
timerjob.
f To revert the virtual machines

following steps:
1.
2.
3.

Lab Review
Question: Why is it important that you run queries against the logging database rather than the
Microsoft SharePoint content databases?
Answer: The logging database is configured to support any SELECT query, whereas the content database
must have special locking hints specified when doing queries. Third-party queries and applications could
cause locking and latency of the Web front ends, and therefore it is not recommended or supported to
run queries directly against SharePoint databases.

10174AD ENU LabManual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10174AD ENU LabManual

Uploaded by

Copyright:

Available Formats

O F F I C I A L

Product Number: 10174A

Lab Instructions: Introducing SharePoint 2010

Exercise 2: Installing SharePoint Server Prerequisites

Exercise 3: Installing SharePoint Server

Exercise 4: Configuring the SharePoint Installation

Exercise 5: Configuring the Farm with the Farm Configuration Wizard

Exercise 6 (Optional): Install a Language Pack

Lab Instructions: Introduucing SharePoint 2010

Lab: Insttalling SharePo

f Sttart the virtu

Lab Instructions: Introducing SharePoint 2010

Exercise 1: Creating Active Directory Accounts for SharePoint

Create Active Directory accounts.

Create a SQL login for the SharePoint administrator.

f Task 1: Create Active Directory accounts

Log on to SP2010-WFE1 as CONTOSO\Administrator with the password Pa$$w0rd.

Open Active Directory Users and Computers.

SharePoint Administrator and

SharePoint Farm Service

SP_ServiceApps SharePoint Service Applications

Close Active Directory Users and Computers.

f Task 2: Create a SQL Server login for the SharePoint administrator

Create a login for CONTOSO\SP_Admin.

f Task 3: Delegate administration of the SharePoint server

Add CONTOSO\SP_Admin to the local Administrators group of SP2010-WFE1.

Log off of SP2010-WFE1.

Lab Instructions: Introducing SharePoint 2010

Exercise 2: Installing SharePoint Server Prerequisites

Attempt to install SharePoint Server prerequisites.

Identify prerequisite installation errors.

f Task 1: Attempt to install SharePoint Server prerequisites

Log on to SP2010-WFE1 as CONTOSO\SP_Admin with the password Pa$$w0rd.

f Task 2: Identify prerequisite installation errors

Click Review the log file.

f Task 3: Copy SharePoint prerequisite installation files

f Task 4: Script the installation of SharePoint Server prerequisites

Lab Instructions: Introducing SharePoint 2010

Alternately, you can copy the contents of the file D:\Labfiles\Lab01

Save the file as D:\Software\SharePointServer2010

The Microsoft SharePoint 2010 Products Preparation Tool appears.

Lab Instructions: Introducing SharePoint 2010

Exercise 3: Installing SharePoint Server

Install SharePoint Server.

Script the installation of SharePoint Server.

f Task 1A: Install SharePoint Server

In the SharePointServer2010 folder, double-click default.hta. On the SharePoint Server installation

Complete the installation wizard using the following configuration information:

f Task 1B: Script the installation of SharePoint Server

Edit D:\Software\SharePointServer2010\Files\SetupFarmSilent \config.xml.

Replace line 11 with the following line:

Remove the comment tags, .

Replace the Display element with the following:

Alternately, copy D:\Labfiles\Lab01\config.xml to the D:\Software

Save the file and close Notepad.

Lab Instructions: Introducing SharePoint 2010

Installation takes approximately 710 minutes.

Lab Instructions: Introducing SharePoint 2010

Exercise 4: Configuring the SharePoint Installation

Run the SharePoint Products Configuration Wizard.

f Task 1A: Run the SharePoint Products Configuration Wizard

Open the SharePoint 2010 Products Configuration Wizard.