SharePoint 2010 70-667 Study Guide

Topic	Link	Reviewed
AAM	http://blogs.msdn.com/b/enterprisesearch/archive/2010/05/28/server-name-mapping-and-alternate-access-mapping-aam.aspx http://technet.microsoft.com/en-us/sharepoint/ff679917.aspx	20110409
Add Server to Farm	http://technet.microsoft.com/en-us/library/cc261752.aspx	20110407
Admin Reports	http://technet.microsoft.com/en-us/library/ee663489.aspx
Authentication Methods	http://technet.microsoft.com/en-us/library/cc262350.aspx
Backup	http://technet.microsoft.com/en-us/library/ee428320.aspx
BLOB Storage	http://technet.microsoft.com/en-us/library/ee748649.aspx
Cache Settings for Web App	http://technet.microsoft.com/en-us/library/cc770229.aspx
Caching	http://technet.microsoft.com/en-us/library/ee424404.aspx http://technet.microsoft.com/en-us/library/cc770229.aspx	20110411
Claims Windows Token Service	http://msdn.microsoft.com/en-us/library/ee517278.aspx http://technet.microsoft.com/en-us/library/ee806890.aspx
Correlation ID	http://blogs.technet.com/b/wbaer/archive/2010/05/01/correlation-ids-in-sharepoint-2010.aspx
Custom Permissions	http://technet.microsoft.com/en-us/library/cc263239.aspx
Database Management	http://technet.microsoft.com/en-us/library/cc825329.aspx
Deploy Solutions	http://technet.microsoft.com/en-us/library/ee906539.aspx
Deployment Scenarios	http://technet.microsoft.com/en-us/library/cc303424.aspx
Designer	http://office.microsoft.com/en-us/sharepoint-designer-help/managing-sharepoint-designer-2010-HA101838275.aspx
Diagnostic Logging	http://technet.microsoft.com/en-us/library/ff463595.aspx http://technet.microsoft.com/en-us/library/ee748656.aspx
Extend Web App	http://technet.microsoft.com/en-us/library/cc288162.aspx
External Anonymous Access	http://technet.microsoft.com/en-us/library/cc263468(office.12).aspx
Fast Search	http://technet.microsoft.com/en-us/library/ff678242.aspx
Filestream	http://technet.microsoft.com/en-us/library/ee748649.aspx
HTTP Monitoring and Throttling	http://blogs.technet.com/b/wbaer/archive/2010/04/22/http-request-monitoring-and-throttling.aspx
Install using PowerShell	http://technet.microsoft.com/en-us/library/cc303424.aspx http://technet.microsoft.com/en-us/library/cc262839.aspx
Kerberos	http://technet.microsoft.com/en-us/library/cc303424.aspx http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1a794fb5-77d0-475c-8738-ea04d3de1147&displaylang=en
Manage PerformacePoint Services Site	http://technet.microsoft.com/en-us/library/ee836143.aspx
Manage Search Scope	http://technet.microsoft.com/en-us/library/ee792872.aspx
Manage Service Accounts	http://technet.microsoft.com/en-us/library/ff724280.aspx http://technet.microsoft.com/en-us/library/ee428296.aspx
Merge Content DB	http://technet.microsoft.com/en-us/library/cc262923%28office.12%29.aspx
Monitoring	http://technet.microsoft.com/en-us/library/ee748636.aspx
Move Site Collection - Content DB	http://technet.microsoft.com/en-us/library/cc825328.aspx
PerformancePoint Services Admin	http://technet.microsoft.com/en-us/library/ee681490.aspx
PowerShell for SharePoint 2010	http://technet.microsoft.com/en-us/sharepoint/ee518673.aspx
PowerTools cmdlets	http://technet.microsoft.com/en-us/library/ee906539.aspx
psconfig	http://technet.microsoft.com/en-us/library/cc263093.aspx
Publishing Features	http://technet.microsoft.com/en-us/library/ff628963.aspx
Quota Template	http://technet.microsoft.com/en-us/library/cc263223.aspx
Restore a Service Application	http://technet.microsoft.com/en-us/library/ee428305.aspx
Sandbox Solution	http://technet.microsoft.com/en-us/library/ff603636.aspx http://technet.microsoft.com/en-us/library/ee721992.aspx
Secure Store Service	http://technet.microsoft.com/en-us/library/ee806889.aspx
Service Applications Permissions	http://technet.microsoft.com/en-us/library/ff603636.aspx
Setup.exe Reference	http://technet.microsoft.com/en-us/library/cc262897.aspx
Site Permissions	http://technet.microsoft.com/en-us/library/cc262778.aspx
Storage Limit Site Collection	http://technet.microsoft.com/en-us/library/cc263480.aspx
Timer Job	http://technet.microsoft.com/en-us/library/ee748593.aspx http://technet.microsoft.com/en-us/library/ee748599.aspx http://technet.microsoft.com/en-us/library/cc678870.aspx
Upgrade	http://technet.microsoft.com/en-us/library/ee617150.aspx
Usage and Health Reports	http://technet.microsoft.com/en-us/library/ee663480.aspx
User Profile service	http://technet.microsoft.com/en-us/library/ee662538.aspx http://technet.microsoft.com/en-us/library/ee721065.aspx
Verify Upgrades	http://technet.microsoft.com/en-us/library/cc424954.aspx
Visual Upgrade	http://technet.microsoft.com/en-us/library/ff607998.aspx
Web Analytics	http://technet.microsoft.com/en-us/library/ee663487.aspx
Web Application Settings	http://technet.microsoft.com/en-us/library/cc262107.aspx http://technet.microsoft.com/en-us/library/cc287691.aspx
Workflow by External Users	http://technet.microsoft.com/en-us/library/ee662521.aspx

SharePoint Study Guide - Install Using PowerShell

http://technet.microsoft.com/en-us/library/cc262839.aspx


This article discusses how to do a clean installation of Microsoft SharePoint Server 2010 on a stand-alone server or on a server farm by using Windows PowerShell.
Installation process overview:

• Farm server requirements
  
• Prepare SPModule
  
• Install Microsoft SharePoint Server 2010 by running Install-SharePoint
  
• Configure the farm by using New-SharePointFarm
  
• Create a Web Application using Windows PowerShell
  
• Deploy services using the SharePoint 2010 Farm Configuration Wizard
  
• Create a site collection by using Windows PowerShell
  
• Perform additional configuration tasks
  
• Add servers to the farm using Join-SharePointFarm
  
• Configure the trace log
  

You can streamline deployment by using Windows PowerShell to install Microsoft SharePoint Server 2010 in combination with other administrator tools to automate unattended installations and configure the farm.

SharePoint 2010 Study Guide - Deployment Scenarios

http://technet.microsoft.com/en-us/library/cc303424.aspx


Deploy a single server with SQL Server (SharePoint Server 2010)

This article describes how to install SharePoint Server 2010 on a single server. This deployment uses Microsoft SQL Server and can easily be scaled out to create two- and three-tier farm topologies.

Deploy a single server with a built-in database (SharePoint Server 2010)

This article describes how to install SharePoint Server 2010 on a single server. This deployment uses SQL Server Express and is typically used for evaluating SharePoint Server 2010.

Multiple servers for a three-tier farm (SharePoint Server 2010)

This article describes how to install SharePoint Server 2010 on multiple servers. This deployment uses Microsoft SQL Server and the resulting three-tier topology provides the foundation for implementing any solution.

Quick start: Deploy single server in an isolated Hyper-V environment (SharePoint Server 2010)

This article describes how to use Windows PowerShell to install SharePoint Server 2010 on a single server that uses either SQL Server Express or Microsoft SQL Server. Use the included Windows PowerShell code to quickly install SharePoint Server 2010 in an isolated Hyper-V environment that you can use for to evaluate SharePoint Server 2010.

Deploy by using DBA-created databases (SharePoint Server 2010)

This article describes how to deploy Microsoft SharePoint Server 2010 in a farm environment that uses DBA-created databases.

Deploy in a virtual environment (SharePoint Server 2010)

This article describes guidance for deploying a virtual environment.

Install SharePoint Server 2010 by using Windows PowerShell

This article explains how to use a scripted module to deploy SharePoint Server 2010.

SharePoint 2010 70-667 Study Guide - Secure Store Service

Secure Store Service
http://technet.microsoft.com/en-us/library/ee806889.aspx

In Microsoft SharePoint Server 2010, the Secure Store Service replaces the single sign-on (SSO) feature. The Secure Store Service is a claims-aware authorization service that includes a secure database for storing credentials that are associated with application IDs. These application IDs can be used to authorize access to external data sources.
In this article:

• About the Secure Store Service
  
• Secure store service preparation
  
• Application IDs
  
• Secure store service mappings
  
• Secure store service and claims authentication
  

About the Secure Store Service

The Secure Store Service is an authorization service that runs on an application server. The Secure Store Service provides a database that is used to store credentials (consisting of a user identity and password) for application IDs that can be used by applications to authorize access to shared resources. For example, SharePoint Server 2010 can use the secure store database to store and retrieve credentials for access to external data sources. The Secure Store Service provides support for storing the credentials of multiple back-end systems using multiple application IDs.

Secure store service preparation

When you prepare to deploy the Secure Store Service, be aware of the following important guidelines:

• Run the Secure Store Service in a separate application pool that is not used for any other service.
  
• Run the Secure Store Service on a separate application server that is not used for any other service.
  
• Create the secure store database on a separate application server running SQL Server. Do not use the same SQL Server installation that contains content databases.
  
• Before you generate a new encryption key, back up the secure store database. You should also back up the secure store database after it is initially created, and again each time credentials are reencrypted. When a new key is generated, the credentials can be re-encrypted with the new key. If the key refresh fails, or the passphrase is forgotten, the credentials will not be useable.
  
• Back up the encryption key after initially setting up the Secure Store Service, and back up the key again each time it is regenerated.
  
• Do not store the backup media for the encryption key in the same location as the backup media for the secure store database. If a user obtains a copy of both the database and the key, the credentials stored in the database could be compromised.
  

Application IDs

Each Secure Store Service entry contains an application ID that is used to retrieve a set of credentials from the secure store database. Each application ID can have permissions applied so that only specific users or groups can access the credentials that are stored for the application ID. Applications use application IDs to retrieve credentials from the secure store database on behalf of a user. The application can then use the retrieved credentials to access a data source.
Application IDs are used to map users to credential sets. Mappings are available for groups or individuals. In a group mapping, every user who is a member of a specific domain group is mapped to the same set of credentials. In an individual mapping, each individual user is mapped to a unique set of credentials.

Secure store service mappings

The Secure Store Service supports individual mappings and group mappings. The Secure Store Service maintains a set of credentials for the application IDs of resources that are stored in the secure store database. Individual credentials for an application are retrieved based on the application ID. Individual mappings are useful if you need logging information about individual user access to shared resources. For group mappings, a security layer checks group credentials for multiple domain users against a single set of credentials for a resource identified by an application ID that is stored in the secure store database. Group mappings are easier to maintain than individual mappings, and can provide improved performance.

Secure store service and claims authentication

The Secure Store Service is a claims-aware service. It can accept security tokens and decrypt them to get the application ID, and then perform a lookup.. When a SharePoint Server 2010 Security Token Service (STS) issues a security token in response to an authentication request, the Secure Store Service decrypts the token and reads the application ID value. The Secure Store Service uses the application ID to retrieve credentials from the secure store database. The credentials are then used to authorize access to resources.

See Also

Concepts

Configure the Secure Store Service (SharePoint Server 2010)

SharePoint 2010 - Excel Service Data Provider

http://technet.microsoft.com/en-us/library/ee662517.aspx

SharePoint 2010 - Sandbox

http://technet.microsoft.com/en-us/library/ff603636.aspx

SharePoint 2010 - Search

blue Placeholder Certification

SharePoint 2010 - Backup

Placeholder for Backup