You are on page 1of 419

OFFICIAL

MICROSOFT

LEARNING

PRODUCT

10231A
Designing a Microsoft® SharePoint® 2010 Infrastructure

Be sure to access the extended learning content on your Course Companion CD enclosed on the back cover of the book.

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 the trademarks listed at http://www.microsoft.com/about/legal/en/us/IntellectualProperty/Trademarks/EN-US.aspx are trademarks of the Microsoft group of companies. All other marks are property of their respective owners.

Microsoft Confidential. © 2010 Microsoft Corporation. All rights reserved. These materials are confidential to and maintained as a trade secret by Microsoft Corporation. Information in these materials is restricted to Microsoft authorized recipients only. These materials support a preliminary release of a product that may be changed substantially prior to final commercial release. These materials may contain preliminary information or inaccuracies, and may not correctly represent any associated Microsoft product as commercially released. All materials are provided entirely "AS IS." These materials are provided for informational purposes only and Microsoft makes no warranties, either express or implied, in these materials and assumes no liability to you for any damages of any type in connection with these materials or any intellectual property in them. The entire risk of the use or the results from the use of these materials remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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 these materials 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. By providing any feedback on these materials to Microsoft, you agree that Microsoft shall be free to use, disclose, reproduce, license, or otherwise distribute, and exploit the feedback provided to it as it sees fit, without obligation or restriction of any kind on account of intellectual property rights or otherwise.

Product Number: 10231A Part Number: 06623 Released: 09/2010

Planning Enterprise Content Management

10-1

Module 10
Planning Enterprise Content Management
Contents:
Lesson 1: Overview of Enterprise Content Management Lesson 2: Planning Tasks for Content Management Lesson 3: Planning Features and Policies for Content Management Lesson 4: Planning Web Content Management Lab: Planning Enterprise Content Management 10-4 10-14 10-26 10-46 10-59

10-2

Designing a Microsoft® SharePoint® 2010 Infrastructure

Module Overview

The term enterprise content management (ECM) in Microsoft® SharePoint® Server 2010 refers to the technologies, strategies, policies, and tools that you use to manage, store, and serve documents and other organizational content to users. This module describes the core ECM functionality that SharePoint Server 2010 provides and describes the major high-level steps that you must take to design a successful ECM plan for SharePoint Server 2010. It also discusses the considerations for planning features and policies for content management in SharePoint Server 2010. All of these steps for planning ECM constitute a vital part of the design of your SharePoint Server 2010 infrastructure.

Objectives
After completing this module, you will be able to: • • Describe the core functionality of ECM in SharePoint Server 2010 that influences your design. Describe the major steps that you should take when you plan a content management solution in SharePoint Server 2010.

Planning Enterprise Content Management

10-3

• •

Describe the considerations for planning features and policies for content management for SharePoint Server 2010. Describe how to plan for Web content management in SharePoint Server 2010.

10-4

Designing a Microsoft® SharePoint® 2010 Infrastructure

Lesson 1

Overview of Enterprise Content Management

Enterprise content management in SharePoint Server 2010 includes the management of documents, records, Web content, and digital assets. You must understand these main concepts before you can plan your enterprise content management strategy and policies.

Objectives
After completing this lesson, you will be able to: • • • • Describe document management in an ECM solution. Describe records management in an ECM solution. Describe Web content management in an ECM solution. Describe digital asset management in an ECM solution.

Planning Enterprise Content Management

10-5

Document Management

Key Points
SharePoint Server 2010 includes document management features that you can use to control a document’s life cycle in your organization. The document’s life cycle includes how you create, review, publish, and retire or retain it. For your document management system to be effective, it should reflect your organization’s culture. Your document management tools must be adaptable. You must be able to hold tight control of a document's life cycle if that suits your organization's culture and goals; however, you must also be able to implement a less stringent and structured system if necessary.

Key Elements of a Document Management Solution
The key elements of a document management solution specify the following: • • • • The types of documents and other content that your organization can create. The template to use for each document type. The metadata for each document type. The document storage location for each stage of a document’s life cycle.

The policies to apply to documents to ensure that document-related actions are audited. review. publication. The principles that must be followed for all documents that are corporate records. and disposition processes. approval.10-6 Designing a Microsoft® SharePoint® 2010 Infrastructure • • The document access method for each stage of a document’s life cycle. The method for moving documents around the organization as team members contribute as part of a document’s creation. and important content is protected. The document format conversions that are required as a document moves through the various phases of its life cycle. documents are retained or disposed of properly. including retention rules to comply with legal requirements and corporate documentation guidelines. • • • .

Decides how—and for what length of time—it retains each record type to comply with legal. Records must be retained for a given period of time. • • . Decides how it should handle documents that will later become records while they are in use. business.Planning Enterprise Content Management 10-7 Records Management Key Points In SharePoint Server 2010. a record is a document or other electronic entity in an organization that can provide evidence of an action or transaction that the organization performs. Implements technical solutions and business processes to help ensure that the organization complies with its records management obligations in a costeffective way without intruding on the normal running of the business. and decides how it should collect the information after the documents are declared as records. Records management is the process by which an organization performs the following tasks: • • Considers which kinds of information it should declare as records. or regulatory requirements.

A well-designed records management system is important for the following reasons: • • • It helps to legally protect an organization. file servers. A monitoring and reporting system for the handling of records to ensure that employees are filing. A file plan that specifies where each kind of record should be retained. These staff members can help you to ensure that documents are retained for the appropriate period of time. such as disposing of expired records or locating and protecting records that are related to external events such as lawsuits. how they should be disposed of. and also describes how the content will move to the records management application. The method for auditing active records. The method for collecting inactive records from all record sources.10-8 Designing a Microsoft® SharePoint® 2010 Infrastructure • Performs routine tasks on its records. A compliance requirements document that defines the rules that the organization's IT systems must follow to ensure compliance and the methods used to ensure the participation of enterprise team members. It helps the organization to comply with regulatory obligations. • • • • • • • . and who is responsible for managing them. the policies that apply to them. The method for capturing and maintaining metadata and audit histories for records. and managing them according to defined policies and procedures. and e-mail systems. by carefully categorizing all enterprise content in your organization. records managers. It increases the efficiency of an organization by encouraging the disposition of expired items that are not records. The process for putting records on hold when events such as litigations occur. and lawyers in your organization to determine which documents are records. Key Elements of a Records Management Solution The key elements of a records management solution include the following: • A content analysis document that categorizes enterprise content that can become records. how long they must be retained. such as collaboration servers. accessing. provides source locations. It is the responsibility of corporate compliance officers.

Key Elements of a Web Content Management Solution The key elements of a Web content management solution include: • • • • • • Publishing features. You use these solutions to create and manage Web content such as HTML. pictures. content control. Version control. Search capabilities. XML. .Planning Enterprise Content Management 10-9 Web Content Management Key Points A Web content management solution is a content management system that you implement as a Web application. Document and workflow tools. Web content management enables content creation. and rich media such as video. and content editing functions. Caching capabilities. Branding and personalization.

10-10 Designing a Microsoft® SharePoint® 2010 Infrastructure • • • Content variation capabilities. Analytics. . Social media capabilities.

This means that users do not have to search through multiple network locations to look for assets or create them from scratch if they cannot find them. and disposes of its digital assets. The digital asset management feature in SharePoint Server 2010 can save an organization time and other resources by providing a specialized repository for storing and managing digital assets. audio. SharePoint Server 2010 provides content types that are designed specifically for audio and video assets and that support the storage and playback of these assets in Web Parts and Web Part pages. distributes. A digital asset is an image. organizes. an organization also gains tighter control over brand-sensitive content and can ensure that only approved assets for products are made available to the relevant users. Functionality for digital asset management in .Planning Enterprise Content Management 10-11 Digital Asset Management Key Points Digital asset management is the process by which an organization creates. stores. manages. or video file or other reusable rich content fragment that an organization uses in applications across the enterprise. By using a centralized storage location for digital asset management.

and disposition processes. The performance issues to consider when you serve assets to your users. As part of your planning for digital asset management. and video files for a department or team to use. The storage space that you require for the assets. The storage location for each stage of an asset’s life cycle. organize. you may restrict the task of organizing and managing assets to a small subset of staff members in the Sales department. As a centralized repository for digital assets for the organization. you must determine the asset library that best fits the requirements of your organization. you use content approval and workflow for all assets that are added to the centralized library. This can be as simple as a place to store image. Alternatively. audio. you use many of the same methods to plan a digital asset management solution as you use to plan a document management solution. The policies to apply to assets to ensure that asset-related actions are audited. which is a type of document library. Overview of Asset Libraries Asset libraries are collections of media files—such as image. audio. The asset library is nothing more than a SharePoint Server 2010 library with specialized content types for digital assets. approval. and you give people different roles and make them responsible for separate stages of the approval process.10-12 Designing a Microsoft® SharePoint® 2010 Infrastructure SharePoint Server 2010 is centered on an asset library. The access method for each stage of an asset’s life cycle. assets are retained or disposed of correctly. You can use an asset library in two ways: • As a general document library for digital assets at the team level. and important assets are protected. review. • Key Elements of a Digital Asset Management Solution The key elements of a digital asset management solution specify the following: • • • • • • The metadata to provide for each asset type. • . you may decide to give everyone in the Sales department permissions to upload. therefore. and video files— on SharePoint Server 2010 that you share with other site users. In this scenario. publication. For example. and manage sales-related assets. The method for moving assets around the organization as team members contribute as part of an asset’s creation.

and how you must retain them to comply with legal requirements and corporate documentation guidelines.Planning Enterprise Content Management 10-13 • The way that assets are treated as corporate records. Question: What are the two main levels at which you would use an asset library? .

10-14 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 2 Planning Tasks for Content Management There are several sets of tasks for each part of the planning process for content management in SharePoint Server 2010. asset library management. List the planning tasks for records management. you will be able to: • • • • • List the planning tasks for document management. List the planning tasks for asset libraries. Objectives After completing this lesson. List the planning tasks for Web content management. and digital asset management in SharePoint Server 2010 before you can design a content management plan. Web content management. List the planning tasks for digital asset management. You must be familiar with these major content management planning tasks for document management. . records management.

from specialized sites such as a records repository to loosely structured document libraries for quick document creation and collaboration. • • . such as Document Sets. SharePoint Server 2010 enables you to organize documents in site collections. to help organize and store documents. You can further organize the content in libraries into folders and subfolders. Analyze document usage. You must also ensure that you have the right implementation team in place and you are aware of the people who contribute to the document management processes. It also offers a range of features. You must ensure that your plans include any feedback from key stakeholders in your organization. Plan the organization of documents.Planning Enterprise Content Management 10-15 Key Planning Tasks for Document Management Key Points Planning for document management includes the following major tasks: • Identify document management roles. sites. and libraries. After you have determined which users work on documents. you should determine the types of documents that they work on and how they are likely to use them.

For example. you can plan to require check-in and check-out. SharePoint Server 2010 includes policies that implement auditing. SharePoint Server 2010 includes workflows for common team-based tasks such as reviewing and approving content. For example. this will happen if your publishing process includes moving a document from a staging site to a production site on the Internet. There are occasions where you may need to move or copy a document from a library or site to another library or site during its life cycle. Plan workflows. labeling. and use Information Rights Management to protect documents from unauthorized distribution. such as document templates. Plan policies. a document might start out as a request for proposal (RFP). For each content type. For example. for a document library. become a final contract. metadata. workflow processes. and finally become a legal document that you must treat as a record. document retention. and barcodes. • • • • . You use content types to organize information about types of documents. This planning step may also include the planning of content that changes its state over its life cycle. Plan content control. and document management policies. and retained according to your organization's corporate and legal requirements.10-16 Designing a Microsoft® SharePoint® 2010 Infrastructure • Plan how content moves between locations. Plan content types. When you plan your organization’s workflows. labeled. You can plan control levels for your content that are based on content type or storage location. you should plan information management policies to ensure that documents are properly audited. SharePoint Server 2010 also enables you to create your own custom workflows. you can control and track how documents move from one person in the workflow to another as each person collaborates during a document's life cycle.

These managers are responsible for locating organizational information and ensuring that teams follow records management practices. These roles include the following: • Records managers and compliance officers. These managers and officers are responsible for categorizing the organization’s records and running the process for records management. Content managers. These personnel are responsible for implementing the IT systems that provide efficient support for records management. . You must identify specialized roles to have a successful plan for records management. Your records managers and content managers should analyze the organization’s document usage to determine which documents can be declared as records before they create a file plan.Planning Enterprise Content Management 10-17 Key Planning Tasks for Records Management Key Points Planning for records management includes the following major tasks: • Identify records management roles. IT personnel. • • • Analyze organizational content.

you can use the Declare As Record option on a document to manually declare it as a record. Plan e-mail integration. and how you should dispose of it. If you use social media sites such as blogs. wikis. in SharePoint Server 2010. For each type of record in your organization. you must determine whether you will manage e-mail records in SharePoint Server 2010 or in the e-mail application itself. Plan how content items become records. indicate their storage location. you must determine how the content items in these sites will become records. how long you should retain it after you classify it as inactive. you must determine when it is inactive. define their retention periods. you can then fill in the rest of the file plan. You should document your plans and processes for records management to verify that your organization is performing its required records management practices and to communicate these practices to others in the organization. When you have analyzed the organizational content and determined retention schedules. Design the records management solution. manage records in place. Plan compliance for social content. Plan compliance reporting and documentation. Develop retention schedules. You must determine whether to create a records archive. and define who is responsible for managing them. As part of your plan. you can create custom workflows to move documents to a records archive. or use a combination of the two approaches. implementation plans. • • • • • • Question: Which records management role is responsible for locating organizational information and ensuring that teams follow records management practices? . For document and records management in SharePoint Server 2010. or My Site Web sites in your enterprise. and effectiveness metrics. You can also use either SharePoint Server 2010 or an external document management system to plan and develop interface components.10-18 Designing a Microsoft® SharePoint® 2010 Infrastructure • Develop a file plan. File plans generally describe the types of items that the organization considers to be records. These components can move content to the records archive or declare a document to be a record without moving it. For example. There may be occasions when you must quickly and easily produce these records management guidelines. Use your file plan to design the record archive or determine how to use existing sites to contain records.

An effective plan for Web pages helps you to ensure that each type of content that your organization publishes has been designed correctly and has been made available to achieve your publishing goals. Plan Web page authoring. and control the authoring features that authors are allowed to use. The term publishing refers to the authoring and deployment of branded content. SharePoint Server 2010 supports browser-based authoring. and the SharePoint Server Publishing feature provides publishing functionality at the site level. When you plan Web page publishing in SharePoint Server 2010. When you plan for browser-based authoring. and configuration files across a SharePoint Server 2010 farm. Plan Web pages. The SharePoint Server Publishing Infrastructure feature provides publishing functionality at the site collection level. you design the appearance of your published content. you must plan which • • . determine where authors are allowed to add content on pages.Planning Enterprise Content Management 10-19 Key Planning Tasks for Web Content Management Key Points Planning for Web content management includes the following major tasks: • Plan publishing features. custom assemblies.

Plan content deployment. This impacts the load. videos. planning the configuration of import and export servers. page layouts. The planning process for content deployment starts with determining whether to use content deployment with your SharePoint Server 2010 solution. or the ability to start a workflow after they submit content. an Internet Information Services (IIS) 7. simple moderation. and identifying the special consideration requirements for large jobs. response time. • . The maximum upload file size setting specifies the maximum size of a file that a user can upload to the server. you must decide how much control you want users to have over the approval and scheduling of site content. Bit Rate Throttling. For example. A Pages library is a document library that contains all of the content pages for a publishing site. The other steps that you must take to plan content deployment include deciding how many server farms you require. Every user who uploads a file to a library uses a connection to the server and increases the amount of data in the database. • Plan content approval and scheduling. and commands to hide from or show to authors. As you plan your SharePoint Server 2010 publishing sites. Maximum upload size. images. Plan caching and performance. You can give users no control. If your site has a Pages library that stores thousands or tens of thousands of pages.10-20 Designing a Microsoft® SharePoint® 2010 Infrastructure resources. planning content deployment paths and jobs. SharePoint Server 2010 provides a disk-based BLOB cache that reduces database load and increases browser performance for users. and data capacity for a server. You must also plan the editing experience in the field controls in which you will allow authors to create content. you may want to impose restrictions on how much control authors have over approving content that they have created themselves.0 extension that improves video performance for users when you serve videos as part of digital asset management. SharePoint Server 2010 also provides Bit Rate Throttling. you must consider a unique set of issues that relate to managing these pages and providing navigation between them in a site. You must consider the following three key caching and performance aspects of SharePoint Server 2010: • Disk-based binary large object (BLOB) caching. The default setting is 50 MB. • • • • Plan large Pages libraries. which can negatively impact your server performance if you have not configured your server to handle large file volumes.

and deciding how to schedule timer jobs for variations. you should start by considering the interaction between variations and other SharePoint Server 2010 features. site navigation. content deployment. Question: What is the default setting for maximum upload size? . Web Parts. These features include content approval. deciding how sites and pages will be created on the target sites. specifying the source variation site and the target variation sites.Planning Enterprise Content Management 10-21 • Plan variations. Other planning steps for using variations with SharePoint Server 2010 include determining the type of variations that you will require. and multilingual sites. When you plan for variations.

you must consider which permissions to grant to users and groups in your organization and whether you must define custom permission levels and groups. Users have all permissions. Contribute. When you plan for permissions and security in an asset library. Users can add or modify items on pages and in lists and libraries. An asset library is a specialized kind of document library. Design. Read. list items. therefore. Users can change the layout of site pages. determining storage requirements for digital assets is the . Full Control. or documents. document libraries. Plan storage and performance. Users can view specific lists. folders.10-22 Designing a Microsoft® SharePoint® 2010 Infrastructure Key Planning Tasks for Digital Asset Management Key Points Planning for digital asset management includes the following major tasks: • Plan permissions and security. The standard available permission levels are as follows: • • • • • • Limited Access. Users can view items on pages.

This makes it much easier to find assets in an asset library. SharePoint Server 2010 has many Web Parts and field controls to take advantage of the new content types that are included as part of an asset library. Some metadata. You add metadata to help describe the type and content of a digital asset.microsoft. rich media files are not automatically searchable because they do not contain text that a search engine can index. or keywords. Plan client support. • Plan metadata and search. but these assets are often much larger. you should enable the disk-based BLOB cache and Bit Rate Throttling options to provide better performance. These include deciding whether all users require access to the asset library and deciding whether the organization requires a managed deployment of the Silverlight client to desktops or users can install it themselves on an as-needed basis. such as the size and dimensions of an image. consider which fields you want to expose to users in Web pages and Web Parts to help users find the assets that they require. . You must add other metadata manually—such as a text description. see http://go. Plan Web Parts and Web pages. • • Additional Reading For more information about ECM planning in SharePoint Server 2010. The main difference is that asset libraries contain fewer assets than document libraries. If you plan to use the asset library to store and serve audio and video files to users. When you design Web pages for sites. You must install the latest version of Microsoft Silverlight® on all client computers that will access your Web sites if you want enterprise users to be able to take advantage of the rich media experience that SharePoint Server 2010 provides. copyright information. This means that there are several things that you must consider about how and when you install Silverlight.Planning Enterprise Content Management 10-23 same as determining storage requirements for documents. is entered automatically when you upload the asset to the asset library.com/fwlink/?LinkID=200900&clcid=0x409.

This information includes how to structure the asset libraries. how many libraries you require. the kinds of assets that they create. After you determine who works with your digital assets. and which information management policies you should apply to the asset libraries. you must determine the kinds of assets that they work on and how they use these assets. the first step is to determine the participants and stakeholders for your solution. This will help you to determine who creates digital assets in your organization. When you plan a digital asset library. • . You must also plan for storage capacity. and who maintains the asset storage servers. You can then use this analysis to help you to determine other important information. because most digital assets are larger than standard document files. Analyze asset usage.10-24 Designing a Microsoft® SharePoint® 2010 Infrastructure Key Planning Tasks for Asset Libraries Key Points Planning asset libraries for your digital asset management solution includes the following major tasks: • Identify digital asset management roles. which content types to use for the assets. who manages the assets.

or you may require users to check assets in and out before they work on assets. For example. You use workflows to perform management tasks on assets in the asset library. The content types that asset libraries include are image. how users must use them. These decisions include where to create them.Planning Enterprise Content Management 10-25 • Plan organization of asset libraries. You may also define an approval process so that assets must be approved before they can be made available to an audience. Plan information management policies. You can either use these content types or create your own custom content types that you derive from the included content types. who has responsibility for managing the expiration of assets. As you plan the asset libraries. you must decide whether assets have to be reviewed and approved before asset consumers can use them. You must plan the information management policies for each content type that you will use in your asset library. and whether you should retain or delete assets after they expire. Plan content types. audio. You must plan the appropriate level of control that is required for each content type and storage location for digital assets. Plan workflows. retain. • • • • . and label assets. how many you require. and video. These policies will then dictate how you audit. and how to organize them. For example. you must make some decisions about them. you may use versioning to store successive iterations of assets in the library. Plan content governance for digital assets. This means that you must consider and decide on several planning-related workflow issues.

you will be able to: • • • Plan for versioning control.10-26 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 3 Planning Features and Policies for Content Management There are several features and policies available in SharePoint Server 2010 that enable you to host an efficient and successful content management solution. You must be familiar with all of the planning steps that are required to implement these features and policies in your SharePoint Server 2010 content management solution before you can design a content management plan. content approval. Objectives After completing this lesson. Plan for content types. and each of these requires planning before you implement them. . Plan for information management policies. and check-in and check-out.

Plan for metadata-based routing and storage. . Plan for workflows. Plan for document IDs.Planning Enterprise Content Management 10-27 • • • • Plan for document sets.

Content approval Check-in and check-out . Content Approval.10-28 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Versioning Control. and Check-In and Check-Out Key Points SharePoint Server 2010 provides features to help you control documents in your document libraries. The methods by which users can better control when a new version of a document is created and also comment on changes that they have made when they check in a document. The method by which site members with Approver permissions control the publication of content. The following table describes these features. Feature Versioning control Description The method by which successive iterations of a document are numbered and saved.

2. 2. you can also specify how many previous major and minor versions to keep. SharePoint Server 2010 has three versioning options: • No versioning. To control the effect on storage space. you must consider how you will use versioning control. 2. you can also specify how many previous versions to keep. This option specifies that numbered versions of documents are retained by using a more complex major and minor versioning scheme such as 1.Planning Enterprise Content Management 10-29 When you plan content management policies. This option specifies that no previous versions of documents are saved.0. A document library . 1. it is important to consider the effect that retaining multiple versions of the same document can have on storage space. Create major versions. You can also configure different versioning control settings for different document libraries to suit the specific requirements of that document type.1. When an approver reviews the document and approves the content. You typically use this option for document libraries that contain content of low importance or content that never changes. This option specifies that numbered versions of documents are retained by using a simple versioning scheme such as 1. To control the effect on storage space. it becomes available for viewing by site users with Read permissions. 3. content approval. Planning Content Approval Use content approval to control the process of making content available to an audience. A document draft that is awaiting content approval is in the Pending state. You can also schedule content publishing depending on the document state. Create major and minor (draft) versions. You typically use major and minor versioning when you want to differentiate between draft content that is not yet ready for publication and published content that is ready for viewing by an audience.1. You typically use this option when you do not want to differentiate between draft versions of documents and published versions. 1. and so on. and check-out and check-in features in SharePoint Server 2010 to control the versions of a document throughout its life cycle. Planning Versioning Control The default versioning control setting for a document library depends on the site collection template on which it is based.0. • • Note: Regardless of the versioning control that you choose.2.

The way in which documents are submitted for approval varies depending on the versioning settings in the document library. as previously mentioned. To share these settings across libraries in your solution. Tip: You configure settings for the content control features that are discussed in this topic in document libraries. This is because an author can write comments that describe the changes that he or she has made to the document when he or she checks it in.10-30 Designing a Microsoft® SharePoint® 2010 Infrastructure owner can enable content approval for a document library and optionally can associate a workflow with the library to run the approval process. but did not need to differentiate between draft versions of documents and published versions? . The key benefits of requiring check-in and checkout include gaining better control of when document versions are created and better capture of metadata. Planning Check-In and Check-Out You can specify that users must check documents out from a document library before they edit the documents. Question: Which versioning option would you use if you wanted to keep previous versions. you can create document library templates that include your content control settings to ensure that newly created libraries reflect your content control decisions.

when performing the authoring and approval process for all documents that are related to financial filings. This organization may create several information management policies that audit the actions of staff members. what users can do with it. An information management policy can help you to enforce compliance with legal and governmental regulations or with your own internal business processes. An information management policy establishes a set of rules for a specific type of content. suppose an organization has to follow strict government regulations that require it to demonstrate proper control and management of its financial statements. For example. you must determine how you should plan and integrate information management policies with your SharePoint Server 2010 content management solution. .Planning Enterprise Content Management 10-31 Planning for Information Management Policies Key Points When you plan content management policies. Information management policies enable you to control who can access your organization’s information. and how long to retain it.

For example. The user then inserts a barcode image of that value in the document. You can also create and deploy custom policy features to meet your specific organizational needs. You can configure Auditing to log events such as editing. but you must implement them by using the SharePoint Server 2010 object model or acquire them from a third-party software vendor. This policy feature specifies a label to associate with a type of document or list item. the organization can Auditing Barcodes Labels Custom . When a content item expires. Policy feature Retention Description This policy feature helps to retire or process content in a consistent way that you can track and manage. Labels are particularly useful in printed versions of documents as a way to display document properties in printed copy.10-32 Designing a Microsoft® SharePoint® 2010 Infrastructure Information Management Policy Features The following table describes the information management policy features that are available in SharePoint Server 2010. In this scenario. a manufacturing organization may want to define an information management policy for all draft specification documents for product design that prohibits users from printing copies of these documents on unsecure printers. checking-in. This policy feature logs events and operations that are performed on documents and list items. or deleting a document or item. This policy feature enables you to track physical copies of a document by creating a unique identifier value for a document. viewing. you can specify that it is disposed of or that a custom workflow is run. Labels are searchable text areas that SharePoint Server 2010 generates based on properties and formatting that you specify.

When you plan the policies for your solution. This may require you to plan custom policy features. You should then distribute these policies for inclusion in the site collection policy galleries of all relevant site collections. you should first determine organization-wide policy requirements and then design site collection policies to meet these requirements.Planning Enterprise Content Management 10-33 Policy feature Description create a Printing Restriction policy feature and add it to the relevant information management policy for the product design specification content type. . Note: If your policy requires custom policy features and resources. you must install and enable these features and resources on all server farms that use your solution.

A content type is a group of reusable settings that describe the shared attributes and behaviors for a specific kind of content. The attributes that you can specify for each content type are as follows: • The metadata that you want to assign to items of this type. . including documents. and folders. you must determine how you should plan and integrate content types with your SharePoint Server 2010 content management solution. You can define content types for any item type in SharePoint Server 2010. Overview of Content Types Content types enable you to organize. and handle content in a consistent way across your SharePoint Server 2010 sites.10-34 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Content Types Key Points When you plan content management policies. By defining content types for specific kinds of documents or information products. media files. you can ensure that you manage each group of content in a consistent way. list items. manage.

If a core content type— such as the Document content type—is sufficient. plan new document content types by using the following steps: • • • • • • • Enter the document type from the document usage worksheet. The custom solutions or features that are associated with items of this type. They also make it possible for a single list or library to contain multiple item types or document types. The document conversions that are available for this type (documents only).Planning Enterprise Content Management 10-35 • • • • • The workflows that are available for items of this type. After you review your list of document types to determine which ones can use core content types. The information management policies that are associated with items of this type. and they can select the type that corresponds to the kind of document that they want to create. Determine the template. The first stage in planning document content types is to review each document type that is listed in your document usage worksheet to determine whether an existing content type will work for that type of document. lists. Planning Document Content Types To plan document content types for your solution. If a library has been set up to support multiple content types. and libraries. use a document usage worksheet and a content type worksheet. Determine the parent content type. . Determine the policy settings. Determine any required document conversions. which records your decisions about each new content type. Determine the workflows. Enter the site URL at which the new content type will be defined. the New Document menu will present users with a list of the available content types. enter the content type name in the document usage worksheet. The document templates for new items of this type (documents only). Fill in a separate content type worksheet for each content type that you plan. Content types provide organizations with a way to manage and organize content consistently across sites.

. Determine the parent content type. Determine the workflows. along with workflows that can run on items of that List content type. You should fill in a separate content type worksheet for each List content type that you plan. Plan new List content types by using the following steps: • • • • Enter List as the document type. You use a List content type to define a type of list item that is unique to your solution.10-36 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning List Content Types The elements of a List content type include the columns of metadata that are associated with the content type. Enter the site URL at which the new content type will be defined.

Planning Enterprise Content Management 10-37 Planning for Document Sets Key Points When you plan content management policies. You can then create additional customized Document Set content types from the parent content type. It also provides a user interface (UI). A document set is a special kind of folder that combines unique Document Set attributes and the attributes and behavior of folders and documents. and object model elements to help manage all aspects of the work product. The Document Set content type is a folder-based content type that organizes multiple related documents into a single view where you can work on them and manage them as a single entity. each inherits properties and settings from the parent . metadata. Overview of Document Sets SharePoint Server 2010 provides support for the creation and management of multiple-document work products with the new Document Set content type. you must determine how you should plan and integrate document sets with your SharePoint Server 2010 content management solution.

However. Considerations for Planning Document Sets Document sets in SharePoint Server 2010 have similar attributes and properties to folders. There is no limit on the number of document sets that can exist in a document library. When you add a Document Set content type to a library. In addition. users can create new instances of the document set by clicking New Document on the ribbon in a library. which runs daily by default. there are some important considerations that you should be aware of when you plan a document set solution: • There is no limit on the number of documents that can exist in a document set. Therefore. • • • • . However. but the number of document sets that can appear in lists is limited by the list view threshold. document sets that are sent to the Content Organizer will remain in the drop off library and will be moved to the appropriate location by the Content Organizer processing timer job.10-38 Designing a Microsoft® SharePoint® 2010 Infrastructure Document Set content type. If you use shared metadata and there are more than 10 items in a document set. you cannot use folders or metadata navigation with document sets. if you use the Send To feature with a document set. you must enable the Document Sets feature for that site collection. the sum for all documents in a document set can be no larger than 50 MB. a timer job will run metadata updates every 15 minutes. If you use document sets in a site collection. When you use document set routing.000 items by default—and to consider your navigation design when you determine how many items should exist in a document set. it is important to consider the likelihood of exceeding the list view threshold—which is set to 5.

. For example. the SharePoint Document Center and Records Center have Document ID search capabilities. the Document ID feature attaches unique identifiers to documents that make it easier to retrieve them independent of their current location. In addition. and they are attached to a document throughout its life cycle. The Document ID service that supports it generates and assigns document IDs. The key benefit of this feature is that you can always reference and find a document by using this unique identifier.Planning Enterprise Content Management 10-39 Planning for Document IDs Key Points When you plan content management policies. you must determine how you should plan and integrate document IDs with your SharePoint Server 2010 content management solution. Search administrators can configure the Search Service to look up document IDs by adding the ID column as a managed search column and optionally creating a new search scope that is used to look up document IDs. regardless of where this document is located. Overview of Document IDs In SharePoint Server 2010.

SharePoint Server 2010 creates a default alphanumeric prefix for you. Therefore. Note: If you do not specify your own prefix. If you decide to activate this feature. Although it can be very useful. if your organization does not require it. there is no reason to activate and configure it. depending on the document retrieval requirements for specific site collections. When you configure your own prefix. Question: At what level do you activate the Document ID feature? . Also bear in mind that you activate the Document ID feature at the site collection level. and it is only enabled after you have activated the Document ID feature. You configure the document ID prefix in the Document ID Settings option under Site Collection Administration. You can specify a prefix of between four and 12 characters. you may want to activate it on one site collection.10-40 Designing a Microsoft® SharePoint® 2010 Infrastructure Key Tasks for Planning Document IDs The first thing to decide is whether you must activate the Document ID feature. but not on another. typical examples of prefixes are department names—such as Sales or Marketing—or the company name if all of your documents are in one central site collection. you must decide what prefix to use for all of your unique document identifiers for the site collection. you can also specify that all existing document IDs should be reset to begin with the same prefix.

In terms of document management. forms. lists. or managing the disposal of documents. SharePoint Server 2010 includes the following workflows for lists. you must determine how you should plan and integrate workflows with your SharePoint Server 2010 content management solution. and content types: . and list items in SharePoint Server 2010. In addition. Web pages. you can use custom workflows to move documents from one site or library to another. or content types. you use workflows to route documents from one person to another so that each person can complete his or her document management tasks. approving document publication. Overview of Workflows Workflows implement business processes on documents. This typically includes reviewing documents. You can associate them with libraries. when a document is scheduled to be archived.Planning Enterprise Content Management 10-41 Planning for Workflows Key Points When you plan content management policies. document libraries. for example.

. Identify the business processes that must be available to run on content of that type. or request changes to the document before they publish it. Collect Signatures. Reviewers can provide feedback. • • • • Key Tasks for Planning Workflows To plan workflows for your document management solution. Identify the workflows that you must make available for that content. Approvers can approve or reject the document. Associate a workflow with a specific content type to make the workflow available whenever that content type is used. reassign the approval task. You use this workflow to route a document for review. Collect Feedback. You use this workflow to route a document for approval. perform the following tasks: • • • • Analyze each document content type that you plan to implement. You use this workflow to track the status of a list item through three phases. Three-state.10-42 Designing a Microsoft® SharePoint® 2010 Infrastructure • Disposition Approval. which is compiled and sent to the document owner when the workflow has completed. You use this workflow to manage document expiration and retention by enabling participants to decide whether to retain or delete expired documents. You use this workflow to gather signatures that are required to complete a Microsoft Office document. Approval.

you must determine how you can use the metadata-based routing and storage in the Content Organizer. your users . as part of your SharePoint Server 2010 content management solution. you configure the settings and rules. route. and store content by using rules that are based on metadata.Planning Enterprise Content Management 10-43 Planning for Metadata-Based Routing and Storage Key Points When you plan content management policies.000 items. You can also use it for day-to-day administrative tasks such as making sure that no folder in a document library contains more than 5. This feature enables you to automatically route documents to different libraries and to folders in these libraries. After you activate the Content Organizer feature. Overview of Content Organizer The new Content Organizer feature in SharePoint Server 2010 is a new metadatabased rules and routing feature that extends and enhances the routing engine that was used in the Records Center site template in Microsoft Office SharePoint 2007. Administrators and users can use the Content Organizer site-level feature to classify. Instead of directly uploading a document to a library or folder.

Sending to Another Site. Using an e-mail drop off zone. Folder Partitioning. and apply rules to a document by using one of the following methods: • • • • • • Uploading a document to a drop off library. You should also test various configurations before you implement your solution live on your production site. route. You can use the following Content Organizer settings in your site to help plan an effective solution for metadata-based content routing and storage: • • • • • • • Redirect Users to the Drop Off Library. The conditions in the rules that you create determine whether a rule should be applied to an item. Planning Content Organizer Settings You must carefully plan how the Content Organizer settings for your site will affect your overall metadata-based routing and storage strategy. Preserve Context.10-44 Designing a Microsoft® SharePoint® 2010 Infrastructure can save. There are several important considerations when you plan Content Organizer rules: . Submission Points. if all of your rule conditions have been met. Submitting to a Record Center site. Using Save as from Microsoft Office Word. Using the Web service object model. and Microsoft Office PowerPoint®. Microsoft Office Excel®. Rules Managers. Planning Content Organizer Rules Content Organizer rules are at the center of your strategy for routing and storing content based on metadata. the target location that you specify determines where the items are sent to. Duplicate Submissions. Using Send To from other SharePoint sites.

you must verify what those items are and try to determine why no rules are being applied to them.Planning Enterprise Content Management 10-45 • • It can sometimes be better to create a set of common rules that send to a unique folder for every unique value of a particular metadata column. There are several important considerations when you plan Content Organizer target locations: • If you choose to create a new folder for each unique property. • Question: Which three object types can you choose when defining a target location for Content Organizer rules? . When you specify another library. library. it is important to consider how many items may populate each new folder. that library must include the content type that is specified in your rule. This may mean creating one simple rule that applies to a particular content type. • Planning Target Locations Each Content Organizer rule that you create must contain a target location setting that specifies where the items that match the rule should be sent. This target location can be another site. You may need to consider creating folders based on a unique property when such a grouping of items exists. If you choose to create a new folder for each unique property and there are hundreds or even thousands of unique properties. If a drop off library contains several items that do not match any of the rules. or folder. A rule can also specify that a new folder is created in the target location for each unique value of a particular property. or it may mean creating several rules that apply to different content types in a number of complex ways. you may create a confusing and unnecessary number of folders that may be difficult to navigate in standard list views. You should create rules that can apply to all possible submissions.

You must be familiar with all of the planning steps that are required to implement the Web content management component of your SharePoint Server 2010 content management solution before you can design a content management plan. and customers. Web content management can help to streamline your process for creating and publishing Web sites. collaborate. You can use these Web content management capabilities to create. SharePoint Server 2010 provides easy-to-use functionality to create. This enables you to get information out quickly to intranet.10-46 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 4 Planning Web Content Management The Web content management capabilities in SharePoint Server 2010 can help an organization to communicate. approve. and integrate more effectively with employees. manage. publish. extranet. As part of ECM in SharePoint Server 2010. partners. and control a large and dynamic collection of content. and publish Web content. . and Internet sites and give your content a consistent look and feel.

. Plan for Web content branding. Plan for Web content approval and scheduling. you will be able to: • • • • Plan for Web content authoring.Planning Enterprise Content Management 10-47 Objectives After completing this lesson. Plan for Web content deployment.

and commands to hide from or show to authors. Planning the Ribbon Authoring Experience The ribbon contains UI elements such as menu items and buttons that provide access to commands.10-48 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Authoring Key Points Web page authoring is the process by which authors add content to a publishing site such as a public-facing Internet site. planning dictionary customizations. publishing and workflow commands. page layouts. Your browser-based authoring plan should include planning which resources. Planning Web Page Authoring SharePoint Server 2010 supports browser-based authoring. and most other commands in SharePoint . It should also include planning the editing experience in the field controls that authors use to create content. planning for reusable content. These commands include page editing commands. and planning additional resources that page authors require. supporting content such as images and videos.

The top-level site in a publishing site collection includes a Reusable Content list that is available to every site below it in the site hierarchy—as long as you have activated the SharePoint Server Publishing feature. you may want to create branded items that must be the same across your site collection. To give your users additional functionality. you can customize the ribbon to add new commands and buttons to provide new functionality to authors. The ribbon is available to all users who have at least Contribute permissions. SharePoint Server 2010 provides this capability by using the Reusable Content list. You can add items to the Reusable Content list and create categories and folders in the list to help you organize these items. page authors can add these items to page content by using the Reusable Content Picker. consider whether you want to add or remove commands from the ribbon or the Quick Access toolbar. When you create page layouts that authors use to create new Web pages. . Also consider the level of access to editing features that you want content authors to have and what kinds of styles that you want to make available. You can also restrict them from gaining access to certain editing features if required. you can add field controls such as text boxes and drop-down lists. For example.Planning Enterprise Content Management 10-49 Server 2010. it is useful to be able to reuse content. you should consider the following questions: • • • • • Do you want to add managed metadata to your page layouts for page authors to use? How will users use the metadata? Which terms and term sets does your organization require? Who owns the term sets? How will you manage term sets? Planning Reusable Content In a publishing environment. or you may want to create templates as starting points for page authors. When you plan your managed metadata. These controls can either contain a predetermined value or can restrict the information that authors are allowed to enter on a page. Planning Managed Metadata You must consider how managed metadata can help to organize and display content pages and other data on your Web site. When you add items to the Reusable Content list. When you plan for Web page authoring.

you can add a custom dictionary to your publishing site. documents. You can also specify whether it can be automatically updated. When you plan for Web page authoring. you should consider the type of additional resources that page authors may require. Additional resources might include master pages and layouts. you can specify that it is shown in the menu during page editing. you must make a list of what these remote resources are and where they are located so that you can add them to the Suggested Content Browser Locations list. and images. custom cascading style sheets (CSS). Planning Dictionary Customizations To prevent words that are unique to your content from being reported as spelling errors. A good example of this is the use of commonly occurring product names and acronyms. . You must consider who will create the resources and where you want to store them. SharePoint Server 2010 creates libraries to store additional resources for your content authors to use.10-50 Designing a Microsoft® SharePoint® 2010 Infrastructure When you create a reusable content item in the Reusable Content list. If some resources are located in other sites. Planning Additional Resources When you create a publishing site.

When you plan for content approval. The Publishing feature in SharePoint Server 2010 provides the ability to approve and schedule content for publishing. Content scheduling is the process by which content is published and made available to readers according to a specified schedule. In SharePoint Server 2010. SharePoint Server 2010 provides a Content Approval workflow that you can use to meet this requirement. you must decide how you want content approval to work for your site and who can approve content for publishing. the control of content can be at one of the following levels: . The scope of your Web content management plan must cover the management and review of content that your users create. You enable content approval in the versioning settings part of the library or list settings for the document library or list that contains the content that you want to publish. Planning Content Approval Users who have Approver permissions control the publication of content by using the content approval process.Planning Enterprise Content Management 10-51 Planning for Content Approval and Scheduling Key Points Content approval is the process by which authored content is approved or rejected for publication.

In addition. you can take advantage of the built-in workflow features. unpublished. Approval workflow. the approval process is more automated. You can schedule your content to be published. You can use a workflow to run the approval process. Simple moderation. and enabling authors to track the status of the approval process. it goes live immediately. A member of the Approver group must manually approve content after an author submits it for publishing. You can change the frequency with which each job runs by using the Review Job Definitions option on the Monitoring page of the Central Administration Web site.10-52 Designing a Microsoft® SharePoint® 2010 Infrastructure • • None. These tasks are initiated by timer jobs that continually check for pages and items in the document or image library that are ready for publishing or expiry. If you enable the Content Approval option for a document library. If content approval is not required for items in a document library. Users can also modify the Approval workflow template or develop their own custom approval workflow by using application tools such as Microsoft SharePoint Designer 2010 or Microsoft Visual Studio® 2010. These features include automatically sending e-mail to approvers. The content is not visible to users with Read permissions until it has been approved. If you use a workflow. . • Planning Content Scheduling Content scheduling is the process by which users with at least Contributor permissions can specify a schedule to publish content to the site. adding approval tasks to approvers’ task lists. after an author submits content for publishing. or expired at specified dates and times. content must also be approved before the schedule publishes it.

If you use content deployment together with content approval and content scheduling for your SharePoint Server 2010 solution. staging.Planning Enterprise Content Management 10-53 Planning for Content Deployment Key Points You use the content deployment feature of SharePoint Server 2010 to copy content from a source site collection to a destination site collection. and publishing farms exist. you must identify all of the considerations that are outlined in this topic for each authoring farm in your environment. all approval processes occur on the source server where the content is authored. Content deployment deploys only changed pages and related assets. . the publishing schedule that is associated with each piece of content is also deployed. If you are implementing a multiple-farm topology for your organization. The content deployment feature is designed for sites that use a multiple-farm topology. When content is deployed to the target server. You can either deploy the complete source site collection or a subset of sites. where separate authoring. and it is incremental by default.

it is not always a requirement for every situation. Planning Export and Import Servers As part of your content deployment plan. . you must decide which site collections you will deploy and also define the source and destination for each of these paths. The servers require specific performance tuning to optimize performance. and determining special considerations for large jobs. To plan the content deployment paths that you require for your solution. Although content deployment can be useful for copying content from one site collection to another. You can associate a content deployment path with only one site collection. a server for staging and quality assurance. You can use content deployment to copy content between two separate site collections in the same server farm. You should start your content deployment planning by determining whether to use the content deployment feature in your SharePoint Server 2010 solution. You have security concerns about the content that you want to deploy to the target farm.10-54 Designing a Microsoft® SharePoint® 2010 Infrastructure Note: The source and destination site collections can be in the same farm or in different farms. but you must install the Central Administration Web site on them. or you can use a three-tier server farm that contains a server for authoring. Other steps that you must take to plan content deployment include deciding how many server farms you require. and a server for production. Planning Content Deployment Paths Content deployment paths define source site collections from which content deployment can start and destination site collections to which content is deployed. planning the export and import servers. Planning Server Farm Requirements A typical content deployment scenario includes two separate server farms: one farm that contains the source server that you use for authoring and one farm that contains the destination server that you use for production. They do not have to be the same as the source or destination servers. You may want to use content deployment for your solution in the following situations: • • • The farm topologies are entirely different. you must decide which servers will perform the roles of export and import servers. planning the content deployment paths and jobs.

You also define the frequency with which your content deployment jobs run and whether they should include all content or only new. Therefore. or deleted content. If your plan specifies that you will use content deployment jobs for specific sites. you must schedule the jobs so that sites that are higher in the site hierarchy are deployed before sites that are lower in the site hierarchy. you must ensure that the temporary storage locations for these files on both the source server farms and the destination server farms have the required space to store the files. When you configure content deployment jobs. and these can be larger than 10 MB. such as video files. In this scenario. will be larger than 10 MB. you must think about the order in which the jobs will run. if the site collection that you are deploying contains some large files. There will be occasions when individual files. each file will be packaged into its own . You must also decide when to run each job. The .cab file.cab files with a default size of 10 MB.cab files are then uploaded to a temporary location on the destination server where they are extracted and imported. As you plan the scope of your content deployment jobs. .Planning Enterprise Content Management 10-55 Planning Job Scheduling After you define your content deployment paths. and then it packages these groups of files into . which should generally mean running the jobs during low activity periods on the source server. you must plan the specific jobs that will deploy the content. you specify whether you will deploy a whole site collection or only specific sites of a site collection for a specific content deployment path. changed. Planning for Large Jobs A content deployment job exports all content to the file system on the source server as XML and binary files.

Tools for Creating a Consistent Look and Feel The key elements that SharePoint Server 2010 provides for establishing a consistent appearance are master pages. it gives a consistent look and feel to company information or products that is recognizable to customers or consumers. page layouts. it is important to maintain the organization brand and also develop divisional and departmental brands in a site. These create a common identity and encourage consistency of content. Branding is essential for Internet-facing Web content in the same way that it is for advertising or marketing materials.10-56 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Branding Key Points Most organizations understand the importance of branding. The reason for this is that publishing has a far greater reliance on look and feel than other functions such as records management. For example. The publishing templates that are available in SharePoint Server 2010 provide additional branding and navigation settings beyond those that are available in other site templates. and CSS. You create your . Even for intranet sites. you can use tree view and content by query controls to provide alternate navigation.

Determine how they want to deploy any customizations. You can even use third-party custom style sheets with SharePoint Designer 2010 as long as they are developed by using Microsoft supported guidelines. Perhaps a simple color change is sufficient for your requirements.Planning Enterprise Content Management 10-57 own master pages. For example. if you hardly ever use the calendar view of events. Create specifications. In addition. You must determine what you must brand on your site. if you plan branding correctly. Prioritize your requirements. if you have to update a theme file or a logo image. The level of HTML experience that your content editors have may dictate how you decide to implement your branding plan. you must reset IIS. For example. However. Consider content editors. You must provide your SharePoint 2010 designers with the adequate tools and training to create the required branding for your site. you must ensure that your plan makes it easy to change your branding styles. With Web content management in SharePoint Server 2010. you should ensure that it keeps a consistent look and feel throughout. Master pages and page layouts are held in the Master Page and Page Layouts Gallery document library—usually referred to as the Master Page Gallery—in the top-level site of a publishing site collection. so you may need to consider enabling publishing features to allow users to edit content directly on the page. page layouts. This will be costly and timeconsuming. However. a Content Editor Web Part may be too complex for some of your content editors. or CSS files by using an editor such as SharePoint Designer 2010 or Visual Studio 2010. and try to synchronize your deployment with theirs. perhaps this is too much branding at this stage in the site’s development. Simplify deployment. You must give your site designers some clear ideas of what you want the eventual look and feel of the site to be like. it will not be necessary to • • • • . Planning Branding in SharePoint 2010 The key considerations when you plan for branding in SharePoint Server 2010 are as follows: • Provide tools and training. You should involve your developers in the content deployment phase. you can control the editing tools and styles that are available. or maybe you want to rebrand the whole site and brand items such as Search controls or calendars. and you may need to reapply it to many sites. When you brand your site.

10-58 Designing a Microsoft® SharePoint® 2010 Infrastructure reset IIS. you can use the Alternate CSS option or an import that points to another file. For example. .

The main tasks for this exercise are as follows: 1. Complete the SharePoint 2010 ECM Planning worksheet. 2. . You need to use the additional information detailed in the supplied documents to complete a planning worksheet for your organization’s ECM design for SharePoint 2010. Read the lab scenario. Task 1: Read the supporting information 1. Ltd has specific requirements for its content management design.Planning Enterprise Content Management 10-59 Lab: Planning Enterprise Content Management Exercise 1: Developing a Content Management Plan Scenario Contoso. Read the supporting information.

2. In the E:\Labfiles\Lab10\Starter folder. complete the worksheet in the SharePoint 2010 ECM Planning Worksheet. Configure all document IDs to use the CONTOSO prefix. Exercise 2: Enabling and Configuring Document IDs and Content Organizer Scenario Before implementing your content management plan in your production environment. .xlsx file. Task 2: Complete the SharePoint 2010 ECM Planning worksheet • In the E:\Labfiles\Lab10\Starter folder. Task 1: Activate document IDs and reset all document IDs to use the same prefix 1. Activate document IDs and reset all document IDs to use the same prefix. 3. Create a new Content Organizer rule. 4.com/sites/docs site. The main tasks for this exercise are as follows: 1. In the intranet.10-60 Designing a Microsoft® SharePoint® 2010 Infrastructure 2. Log on to 10231A-NYC-DC1-10 as CONTOSO\Ed with the password Pa$$w0rd. Create a new Send To connection. Test the new Content Organizer rule. activate the Document ID Service feature. you need to configure and test some parts of the ECM design by using the information in the ECM Business Requirements document and the SharePoint 2010 ECM Planning worksheet. 3. Activate and configure the Content Organizer feature. 5.contoso. read the information in the ECM Business Requirements. 2.docx file.

3. in Content Organizer Settings.) Option Display name Send To URL Task 4: Create a new Content Organizer rule • In the intranet.contoso. In the intranet. 4. create a new Send To connection by using the information in the following table. and ensure that subfolders are created if a target location has too many items in it.com/sites/hrdocs site. create a new Content Organizer rule by using the information in the following table.contoso.contoso.Type Property-based conditions Property Contoso Document Contoso Department . Value Move Contoso Document items to HR Docs Contoso Content Type Option Name Content type Group Content .com/sites/docs site. Copy the Submission Points Web service URL to the clipboard. enable Folder Partitioning. In the intranet. activate the Content Organizer feature. Task 3: Create a new Send To connection • In SharePoint 2010 Central Administration.com/sites/hrdocs/_vti_bin/OfficialFile. Value HR Docs Content Organizer http://intranet.com/sites/hrdocs site.Planning Enterprise Content Management 10-61 Task 2: Activate and configure the Content Organizer feature 1. In the intranet.contoso.com/sites/docs site. asmx (You can paste this from the Clipboard.contoso. 2. activate the Content Organizer feature.

10-62

Designing a Microsoft® SharePoint® 2010 Infrastructure

Option Property-based conditions Operator Property-based conditions Value Target Location

Value Is equal to

HR

HR Docs Content Organizer

Task 5: Test the new Content Organizer rule
1. Create two text documents on the desktop called HR Doc and Non-HR Doc. Ensure that you add some basic text to these two documents because the upload process will not work otherwise. Navigate to the Docs Drop Off Library, and then submit the HR Doc document, specifying HR as the Contoso Department. Navigate to the Docs Drop Off Library, and then submit the Non-HR Doc document, specifying Marketing as the Contoso Department. Verify that the Content Organizer rule moves the HR Doc document to the HR Docs drop off library and leaves the Non-HR Doc document in the Docs drop off library.

2. 3. 4.

Exercise 3: Configuring Retention Policies and Records Management
Scenario
Before implementing your content management plan in your production environment, you need to configure and test some parts of the ECM design by using the information in the ECM Business Requirements document and the SharePoint 2010 ECM Planning worksheet. The main tasks for this exercise are as follows: 1. 2. Configure information management policy settings for document retention on a content type. Activate and configure the In Place Records Management feature.

Planning Enterprise Content Management

10-63

Task 1: Configure information management policy settings for document retention on a content type
• In the intranet.contoso.com/sites/docs site, configure the information management policy settings for document retention for the Contoso Document content type by using the information that the SharePoint 2010 ECM Planning Worksheet – Solution.xlsx file provides.

Task 2: Activate and configure the In Place Records Management feature
1. 2. 3. In the intranet.contoso.com/sites/docs site, activate the In Place Records Management feature. Configure the record declaration settings to allow record declaration in all locations. Change the Non-HR Doc document to a record.

10-64

Designing a Microsoft® SharePoint® 2010 Infrastructure

Module Review and Takeaways

Review Questions
1. What are the main differences between SharePoint documents and records, and how they should be managed in your enterprise content management plan? What are the three key caching and performance aspects of SharePoint Server 2010 that must be considered as part of your planning for Web content management? When planning for using document sets, what are the limits for the number and size of documents in a set that you must consider in your plan? When you are planning for branded items, which must be the same across your site collection, which SharePoint Server 2010 feature should you consider?

2.

3. 4.

Planning Enterprise Content Management

10-65

Best Practices Related to Enterprise Content Management
Supplement or modify the following best practices for your own work situations: • If you plan to use the asset library to store and serve audio and video files to users, you should enable the disk-based BLOB cache and Bit Rate Throttling options to provide better performance. Use the Document ID feature to attach unique identifiers to your users’ documents so that they can find them more easily irrespective of the documents’ current location. If the site collection that you are deploying contains large files, ensure that the temporary storage locations for these files on both the source server farms and the destination server farms have enough space to store the files. Use the new Content Organizer feature to create metadata-based rules to automatically route documents to different libraries and folders.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy

11-1

Module 11
Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy
Contents:
Lesson 1: Overview of Business Intelligence Principles Lesson 2: Planning Data Access by Using BCS Lesson 3: Planning SharePoint 2010 Business Intelligence Solutions Lesson 4: Planning for Reporting and Presentation Lab: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-51 11-4 11-14 11-26 11-44

11-2

Designing a Microsoft® SharePoint® 2010 Infrastructure

Module Overview

This module reviews the role of Microsoft® SharePoint® 2010 business intelligence (BI) solutions as components of a wider organizational BI implementation. SharePoint 2010 extends the BI features of Microsoft Office SharePoint Server 2007 by including PerformancePoint Services and the Visio Graphics Service, in addition to updates to Excel Services. A solution architect must also assess the role of Microsoft SQL Server® Reporting Services for SharePoint 2010 as a significant component of an overall BI strategy. Critical in the development of a BI environment is the role of Business Connectivity Services (BCS) in the visualization of line-of-business (LOB) data from back-office systems. Although BCS is not a true BI tool in the mould of Excel Services, it is intrinsic to BI solutions for users.

Objectives
After completing this module, you will be able to: • • Describe the principles of BI. Describe how to plan for data access by using BCS.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy

11-3

• •

Describe data and security planning concerns for key BI tools. Describe the roles of SQL Server Reporting Services and the BI Center in reporting and presenting BI components.

the goal is to get the right information to the right people in a timely manner. . You must ensure that you understand the business requirements for your organization and can interpret them. BI is an enabler to business decision-making. you will be able to: • • Describe the goals of BI. Objectives After completing this lesson.11-4 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 1 Overview of Business Intelligence Principles SharePoint 2010 delivers a greatly enhanced range of BI solutions. As part of your solution design. you can effectively map them against SharePoint 2010 BI solutions. you must review the options that are available to you for BI deployment. Explain the business opportunities that are appropriate for SharePoint 2010 BI solutions. In this way.

.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-5 • • Explain the data management and access issues that are relevant to BI design. Plan how to implement BI in SharePoint 2010.

so it is probably more useful to assess the goals of BI instead. Business intelligence for the community. in addition to access to back-end data sources such as SQL Server or other database software.11-6 Designing a Microsoft® SharePoint® 2010 Infrastructure Goals of Business Intelligence Key Points There are a range of definitions of BI. usually information workers. can format and . Users. you can more fully understand what you should achieve through your solution design. Self-Service and Personal BI The goal of self-service and personal BI is to ensure that users can provide their own BI services. There are three key goals: • • • Self-service and personal business intelligence. it involves personal productivity facilities such as Microsoft Office. Organizational business intelligence. Usually. In this way.

dashboards. This usually involves greater input from IT services through the provision of collaborative tools. This model commonly uses key performance indicators (KPIs). . Eradicating such silos is the most common goal of BI implementations. a solution architect must identify opportunities for teams to share common information to make corporate decisions. This model has the added benefit of enforcing governance across the business at a day-to-day level. Business Intelligence for the Community The goal of BI for the community is the ability to analyze data in a collaborative environment. but has the major benefit of eradicating silos of business information that are outside the control of the business. and corporate data are used in a coherent manner across an organization. This requires a more sophisticated approach to business systems. whereas Excel Services provides a truly collaborative environment. such as Excel workbooks. This approach creates a homogeneous data environment where both local information. but work is placed in the context of the overarching business strategy. This involves little or no ongoing effort from the IT department. with BI tools generating preanalyzed output that aligns with organizational goals.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-7 analyze data to generate business logic models that help them make decisions. but the power of how to use information remains with information worker teams. As a superset of the model of BI for the community. Therefore. based on business requirements from BI stakeholders and the organization’s management team. This approach often requires a lot of architectural and developmental effort from the IT department. A good example of how this extends personal BI is exhibited by the difference between Microsoft Excel® 2010 and Excel Services. The company goals are reflected in the use of data. Excel 2010 provides personal productivity. The aim is to create teams who can combine effort and therefore produce more complex or better informed business models. and scorecards to publish achievements or targets. Organizational Business Intelligence Organizational BI extends the use of business data beyond individual or team usage and creates a strategic model for business operation. information workers can continue to collaborate on data analysis.

Be careful of the goal of unilateral independence from the IT department. You should avoid the need to involve the IT department in protracted systems design projects. . If business stakeholders and users identify self-service as a key requirement. One of the key benefits of BI is that it enables information workers to have structured and managed access to corporate information when they need it. Here are some examples of requirements that should trigger a review of SharePoint 2010 BI components: • Deliver user autonomy. it is essential that you can reconcile business requirements with opportunities for the use of BI. The goal should be to enable users to more quickly generate business solutions through closer collaboration and accessibility to back-end corporate data. you must recognize when BI. This does not mean that you must use BI. rather than an enabler. and specifically the SharePoint 2010 BI toolset. you should investigate their goals and reasons for this. Rather. sometimes users feel that the IT department is a blocker to BI.11-8 Designing a Microsoft® SharePoint® 2010 Infrastructure Identifying Business Intelligence Opportunities Key Points As a solution architect. is appropriate to your design.

This minimizes duplication of effort and makes solution deployment faster. Deploy status indicators and KPIs. This is especially the case when Visio diagrams are connected to back-end data systems that monitor or manage business processes. not the data. You should review requirements to identify where stakeholders need information delivered directly to users. too. SharePoint 2010 Excel Services enables users to view and interact with Excel 2010 workbooks through a browser. you should investigate whether these are required just for Visio users or for a wider audience. you should review the opportunities to create a managed set of data connections that are made available to users. Business scorecards provide overall view of status indicators. The ability to work collaboratively on Excel workbooks has previously involved saving a workbook on a shared drive so that others can access it. Provide central management for external data connections. They are modeled after the business. together with Web Part visualization. which is the key benefit. This is still possible with SharePoint 2010. to reflect goals. Business dashboards enable you to deploy BI information to both BI and non-BI users through an onscreen Web Part. Create a central reporting location. Identify whether users want a centralized reporting environment. means that users can now work collaboratively wherever they are and without the need to have the client license for Excel 2010. For environments such as process industries that map complex processes in Microsoft Visio® 2010. Deploy dashboards. Enable business process visualization. rather than just for their own analysis. These may be included as part of a dashboard. Deploying single instances of reports minimizes the effort that is wasted in user generation of multiple versions of the same information. and has the obvious advantages of version control and check-in and check-out from document libraries. • • • • • • . If your environment has a range of complex data access requirements. Assess the need for central management of connections to back-end business data sources. This browser functionality. This is only deliverable with a connected system because you must have access to back-end data sources to ensure that the status reflects current business achievements. Status indicators and KPIs give the information worker a current view of performance. Generate business scorecards.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-9 • Share Excel workbooks through browsers.

Most companies have an overarching BI strategy.11-10 Designing a Microsoft® SharePoint® 2010 Infrastructure Data Security Management in Corporate Business Intelligence Key Points When you are designing a BI deployment strategy for SharePoint 2010. For your design to succeed. HTTPS. in addition to matching BI tools to requirements. Which security protocols (HTTP. such as: • Protocols. Organizational Compliance The security component requires that you understand the company-wide standards for security. and so on) are used in your organization and does SharePoint 2010 support them? . you must fit the SharePoint 2010 solutions into this strategy. which includes elements such as data compliance and security. you must ensure that you look at how your organization manages data.

which offers coordinated security management. How does your environment manage personal credentials? • Security Integration From a systems management perspective. which enables you to provide security accreditation across systems without intervention from users in the form of additional logons.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-11 • Authentication. with authentication transferred through a given methodology between different platforms? Management. This is critical for a BI implementation because the goal is to provide a seamless flow of information and authentication. You can also delegate security administration to departmental groups to minimize IT intervention and maximize effective response to users. SharePoint security is. so they almost certainly want to minimize the need for multiple logon credentials. it is important to aggregate the security mechanisms of various platforms. You can deliver a range of security and authentication implementations in SharePoint 2010. Each is likely to have its own implementation of data security. . by default. Does your organization want to implement a single sign-on (SSO) approach. Central Control In your BI plan. so you must understand which platforms and methodologies can integrate with SharePoint 2010. Seamless User Experience Your users employ various systems. centralized. You must plan to implement the correct security implementation for your Web applications. SharePoint 2010 delivers claims-based security and the Secure Store Service. you must also establish the responsibilities of IT and deployed administration control of security. such as classic or claims.

which remains the most popular BI user tool. When you create a design. you must map BI solutions to your business requirements. New options include PerformancePoint Services. such as Excel 2010. and enhancements to existing options include Excel Services. some BI solutions are available that are not directly SharePoint 2010 solutions. Organizational business intelligence. use the essentially personal tools such as Excel 2010 (optionally with PowerPivot) and Visio 2010. These can draw . In addition. These should relate to the three principal goals: • • • Self-service and personal business intelligence. Self-Service and Personal Business Intelligence In the area of personal business productivity. Business intelligence for the community.11-12 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning the Implementation of BI in SharePoint Key Points SharePoint 2010 improved BI options over those that were previously available in Office SharePoint Server 2007.

It is possible to share output from these and. SQL Server Reporting Services is a SQL Server function. These can implement business standards through workflows and the document information panel. You may deploy PerformancePoint Services for a group or individuals to use to create BI solutions. a possible solution is using Excel Services rather than Excel 2010. in the case of Excel 2010. You may also implement report standardization by provisioning Report Builder. provide input to BI components such as Status Indicator Web Parts. These are collaborative tools that provide information to the wider user population through a browser-based user interface (UI). It enables you to design and deploy centralized BI solutions.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-13 information from external systems. PerformancePoint Services straddles the divide between community and organizational productivity. discusses this more fully. but you can deploy it through SharePoint 2010. but do not necessarily provide collaborative environments. If you need to make workbooks available for multiuser updates. . Planning for Reporting and Presentation. such as dashboards and KPIs. For these types of files. across the user environment. but only one worker at a time can use them. such as dashboards or workflows. you can make the function and business logic in Visio drawings available to all users of the SharePoint 2010 environment. you may need to deploy centralized metadata tagging in SharePoint 2010 through custom content types and columns. which are useful for personal or team productivity. use the SharePoint BI tools such as Excel Services and the Visio Graphics Service. Business Intelligence for the Community In the collaborative sector. Lesson 4. Using the Visio Graphics Service. Organizational Business Intelligence PerformancePoint Services is an essential tool for organizational BI.

. which provides data access to users and SharePoint applications beyond the traditional BI solutions of Excel Services. For a SharePoint 2010 BI environment. You should review such integration in the widest terms. because BCS is also used in search and social computing solutions. Objectives After completing this lesson. If back-end data integration is a key business requirement for your users. it is essential to plan your data access strategy because issues over failed access or overly complex authentication configuration have often impacted BI implementations. SharePoint 2010 provides BCS. it is an integral component for integrating LOB data with SharePoint applications. you will be able to: • Describe the key components and functions of BCS. it is almost certain that you will need to implement BCS.11-14 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 2 Planning Data Access by Using BCS Although BCS is not usually included in the core BI tools in SharePoint 2010.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-15 • • • Describe the design options for BCS security. Describe how to prevent the double-hop issue. Explain planning options for authentication when using the Secure Store Service. .

Business Data Connectivity (BDC). . The terminology for BCS is potentially confusing for those who have experience of the Office SharePoint Server 2007 Business Data Catalog (BDC). BCS is described by using the following terms and acronyms: • • • • Business Connectivity Services. A SharePoint 2010 list that is specifically designed to deliver data from external systems. External Content Type (ECT). The runtime that enables connectivity to external data sources. It is one of the few service applications that are embedded in Microsoft SharePoint Foundation 2010.11-16 Designing a Microsoft® SharePoint® 2010 Infrastructure Overview of Business Connectivity Services Key Points BCS is a foundation component for data integration in SharePoint 2010. An entity that is consumed through BCS. External List. The overall name for the service.

BCS provides external data access to Microsoft Office tools such as Excel 2010. you should treat them as BI solutions. but if the solutions are designed to help information workers to become more productive.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-17 BCS Overview BCS is a set of features that enable you to connect through SharePoint 2010 to a range of external data sources. In a broader BI context. integrated. with its SharePoint 2010 add-ins. and executed in supported Office client applications and on the Web server. For more sophisticated development. You can render this external content into SharePoint visualizations such as external lists or Web Parts. These enable you to restrict resources that any application that runs in your SharePoint 2010 environment uses. . You can connect to data sources that include. but are not limited to: • • • • • SQL Server databases SAP applications Web services (including Windows® Communication Foundation (WCF) Web services) Custom applications SharePoint Web sites BCS uses a standard set of interfaces that makes it possible for both users and developers to create business applications in SharePoint 2010. you should ensure that you include the use of sandboxed solutions in your development standards. These may not be defined as BI solutions. SharePoint Designer 2010 is a powerful tool that you can deploy to users who need to develop and deploy business solutions. It does this through a runtime environment in which solutions that include external data are loaded. A key tool for users is Microsoft SharePoint Designer 2010. Note: If your design includes provision of self-service development through SharePoint Designer 2010. there is Microsoft Visual Studio® 2010. which enables them to develop solutions without the need to write programming code.

com/fwlink/?LinkID=201241&clcid=0x409. . see http://go.microsoft.microsoft. For more information about sandboxed solutions.com/fwlink/?LinkID=200901&clcid=0x409.11-18 Designing a Microsoft® SharePoint® 2010 Infrastructure Additional Reading For more information about using SharePoint Designer 2010 with BCS. see http://go.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-19 Planning BCS Security Key Points The security architecture of BCS is primarily involved in integrating authentication with external systems. you may want to enable your Web application for claims-based authentication. The two methods of authentication that are available in BCS are: • • Claims-based authentication Credentials-based authentication Authentication of BCS Access with Claims If you are planning for SharePoint 2010 BCS with a claims-aware data source. Authentication BCS is designed to integrate with external data sources. For BCS authentication. which means that you must ensure that you can pass authentication credentials from the user to the external platform. . This service is preconfigured on a farm and authenticates users or functions. your solution uses the SharePoint 2010 Security Token Service (STS).

You must associate each with an authentication mode. The list requests a security token from the STS. 3. sends the data to update the list. . The service is a broker for SharePoint 2010 and supports multiple authentication providers for applications based on both ASP. The list access triggers an authentication request. The user accesses an application that is configured for claims authentication. such as an external list. Authentication of BCS Access with Credentials BCS supports the following credential authentication options: • Windows authentication: • • • • • • Windows Challenge/Response (NTLM) Microsoft Negotiate Authentication other than Windows: Forms-based Digest Basic Authentication Modes You must ensure that application developers are aware of the options for authenticating data access from the BCS. to SharePoint. The process for claims-based authentication is as follows: 1. if the claims are appropriate.11-20 Designing a Microsoft® SharePoint® 2010 Infrastructure such as a Web service. The external source reviews the credentials and. 2. 5. and a target application identifier. which is returned to the list. 4. which is associated with an external content type. The Secure Store Service reads the user information and sends credentials to the external data source. There are two methods of passing this information to the target data source: • Pass the credentials directly to the target. The list passes the security token to the Secure Store Service. 6.NET and WCF. The STS issues a token that contains a set of claims based on the user identity.

Credentials. group account. Can be used for external database access. • • You should plan to use the latter two options with Secure Sockets Layer (SSL) or IPSec security protocols. you should give specific permissions to each user or group that needs it. It uses a Secure Store Service to map the user’s credentials to a set of Windows credentials on the external system. It uses the Secure Store Service to map the user’s credentials to a set of credentials that a source other than Windows supplies. RdbCredentials. Maps the user credentials to the BCS application pool account and sends those credentials to the target system. Passes the credentials of the logged-on user to the external system. These must be known to the target system. which means that the user credentials must exist on the target system. Can be used for external Web services. When you plan a permissions strategy. Permissions You can associate BCS permissions with an individual account. which uses a basic or digest authentication. WindowsCredentials.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-21 • Map the credentials to an account in the Secure Store Service. It uses the Secure Store Service to map the user’s credentials to a set of credentials that a source other than Windows supplies. or claim with one or more permission levels on an object in a metadata store. RevertToSelf. in accordance with the principle of least privilege. . which uses a basic or digest authentication. The modes that are available include: • • • PassThrough. These must be known to the target system. Can be used for both external Web services and database access.

11-22

Designing a Microsoft® SharePoint® 2010 Infrastructure

Planning Data Access Security by Using the Secure Store Service

Key Points
The Secure Store Service is a service application that enables access to external data sources. It provides a store of credentials through which an active user can gain access to an external data source through impersonation. This impersonation functionality maps BI service applications, users, and credentials through use of a target application. This is a set of metadata that lists the users who have access to the credentials that a BI application uses to access external data. The metadata and credentials are stored in an encrypted Secure Store Service database in SharePoint 2010. The stored settings include: • Administrators. This lists the target application administrators. These can be administrators or users to whom you delegate administrative rights to the Secure Store Service target application.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy

11-23

Note: PerformancePoint Services automatically configures administrators for target applications that are configured through it.

Members. This lists users or Active Directory® directory service groups for whom the Business Intelligence Service Application impersonates credentials.

Note: For target applications that are configured through PerformancePoint Services, PerformancePoint Services specifies the service account that the PerformancePoint Services application pool uses as a member.

Credentials. This lists the target application credentials, which consist of an Active Directory account with direct access to data sources. You must grant this account access to the data source outside SharePoint 2010, in line with the principle of least privilege. This account is impersonated to provide data access to users.

Farm administrators can configure all of these through the Secure Store Service for Excel Services and the Visio Graphics Service. However, PerformancePoint Services is configured through the PerformancePoint Service Application Settings.

Excel Services and the Visio Graphics Service
You can design two methods for use of the Secure Store Service for Excel Services and the Visio Graphics Service: • Specified target application. The workbook or drawing specifies the target application. The Secure Store Service uses the associated credentials when a user requests data access. No specified target application (unattended service account). Again, the workbook or drawing specifies this. However, with this option, the Secure Store Service uses the unattended service account credentials that are specified in the Global Settings for the service application.

PerformancePoint Services
PerformancePoint Services cannot specify a specific Secure Store Service target application. It only uses the Secure Store Service by specifying the unattended service account.

11-24

Designing a Microsoft® SharePoint® 2010 Infrastructure

Data Connection Files
Excel, Visio, and PerformancePoint Services all use data connection files to specify authentication information. For Excel Services and the Visio Graphics Service, this is an Office Data Connection (ODC) file. For PerformancePoint Services, it is a PerformancePoint Services Data Connection (PPSDC) file.

Excel Services Connections
For Excel Services, you must plan and specify the ODC connection before you load the workbook. The settings include: • • • Integrated Windows authentication. Integrated Windows authentication with Kerberos delegation to authenticate each user. Secure Store Service Identifier (SSS ID). The specific Secure Store Service target application that is used for data access. None. The credentials that are specified in the connection string or the unattended service account.

Note: You can only edit these settings by opening the worksheet or ODC file in Excel 2010.

Visio Graphics Service Connections
For the Visio Graphics Service, you can use either embedded connection information or connection information in an ODC file: • Embedded connection. This requires you to specify that users connect to an external data source when they create Visio drawings, which stores the connection directly in the file. When a user accesses the drawing, the Secure Store Service uses the unattended service account. ODC connection. This uses an existing ODC file that is specified in the drawing. When you publish the drawing, the Visio Graphics Service maintains the link to the ODC file and uses the connection information.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy

11-25

Preventing the Double-Hop Issue

Key Points
The double-hop issue is one that is a particular problem for BI implementations. It occurs when users successfully present their credentials to SharePoint 2010, but find that Internet Information Services (IIS) does not pass these credentials to the BCS, so the call to the external data source fails. NT LAN Manager (NTLM) authenticates only the client and not the server, so end users would not know whether their credentials were passed to a valid service. To avoid this scenario, you should plan to use the Secure Store Service to access external data.

11-26

Designing a Microsoft® SharePoint® 2010 Infrastructure

Lesson 3

Planning SharePoint 2010 Business Intelligence Solutions

The three core BI services for SharePoint 2010 are Excel Services, PerformancePoint Services, and the Visio Graphics Service. As part of your design for BI, you must understand how and when you should use each of these. You must also understand the security architecture of each, so that you can maintain security governance over business-critical information.

Objectives
After completing this lesson, you will be able to: • • • • Describe the key planning options for Excel Services. Describe how to plan Excel Services security. Explain the function and use of PowerPivot for SharePoint. Describe the key planning options for PerformancePoint Services.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy

11-27

• •

Describe how to plan PerformancePoint Services security. Describe the key planning options for the Visio Graphics Service.

11-28

Designing a Microsoft® SharePoint® 2010 Infrastructure

Planning for Excel Services

Key Points
Excel Services is a multifaceted service application. This means that there are several components that integrate to deliver the Excel Services functionality. The components are described in the following table.

Component Excel Calculation Services

Description The service that is responsible for loading Excel workbooks from trusted file locations, executing any workbook calculations, calling any user-defined functions, and refreshing workbook references to external data sources. It also creates, maintains, and closes user sessions to the service. You can configure it to cache open Excel workbooks, calculations, and data query results for improved performance.

Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy

11-29

Component Excel Web Services

Description The developer interface to Excel Services. You can create applications that call the service to perform custom tasks on a workbook. You can also use Excel Web Services to incorporate server-based workbook logic into an application.

Excel Web Access

The component of Excel Services that is visible to information workers. This renders Excel workbook information into a Web browser.

This division of functionality will affect the physical design of your Excel Services implementation, because you will need to define the capabilities of both application and Web Front End (WFE) servers. Excel Services provides all of the visualization and computational analysis functionality that you usually expect to deliver through a personal computer. Your SharePoint 2010 servers deliver these loads, so you must be sure that you understand the loading effort that is involved. To do this, you must review the number, size, and complexity of the workbooks that you expect to manage in Excel Services. These are highly subjective metrics, so it is important that you pilot any environment and assess the performance of Excel Services for users. Large and complex Excel workbooks are processor-intensive applications, so you may find it fruitful to dedicate a server that has powerful processing capabilities as a dedicated Excel Services server. This high processing requirement also makes it preferable to dedicate a server to Excel Services, rather than share the hardware platform with other service applications.

Identifying the Need for Excel Services
You must identify the reasons for including Excel Services in your design, and you must base these reasons on business requirements. You can regard Excel Services as the mass reporting version of Excel 2010. Excel Services makes it simple to use, share, secure, and manage Excel 2010 workbooks as interactive reports in a consistent way throughout the enterprise. Excel Services is not a multiuser version of Excel 2010; users can interact with workbooks, but they cannot create new ones in Excel Services. This is an important distinction and may not be obvious to users. A key advantage is the ability to store a workbook in a central location and make it available to many users. You can also use Excel Services to create dashboards, which reflect current workbook statistics or metrics directly to a user Web page.

You may find that business analysts are more attuned to this type of business solution. Users would be unlikely to make such a request. particularly those in financial services. You can use Excel Services to generate reports to include BI information.11-30 Designing a Microsoft® SharePoint® 2010 Infrastructure Users often have complex business logic in Excel 2010 workbooks. are comfortable with the traditional spreadsheet reporting layout. Many users. . so you need to identify where key business logic is held. you can access this business logic programmatically through a Web service– based interface. In SharePoint 2010. or any other data that you use in Excel Services.

These locations must be explicitly trusted before Excel Services can access them.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-31 Planning Excel Services Security Key Points Excel Services enables you to centrally manage not only workbooks. The service application will only process data connections to a trusted data provider. • Trusted data providers. Trusted file locations may be: • • • SharePoint document libraries. . HTTP Web sites. Access Components The access components include: • Trusted file locations. because it can only open workbooks in trusted file locations. but also the resources and connections to corporate data that a workbook may contain. Trusted data providers are external databases that you define as trusted in Excel Services. Universal Naming Convention (UNC) paths.

you should also use Kerberos for added security and as an option to circumnavigate the double-hop issue. You must store the ODC files in a data connection library. You can plan to centrally store these files. If the connection string contains a user name and password. None (unattended service account). or NTLM. is now used exclusively for IIS Authentication Settings in SharePoint Server 2010. The connection strings are passed to the database provider. . but it is more common to use group mapping. Excel Services can use claims-based authentication for all deployment scenarios. You may use individual credentials for usage monitoring. If you choose to use NTLM. and if the database authorizes access. This supports individual or group credentials mapping. However.11-32 Designing a Microsoft® SharePoint® 2010 Infrastructure • Trusted data connection libraries. whether they occur in a single server or multiple server farm. because all Excel Services scenarios use claims. Integrated Windows authentication. Authentication Excel Services supports three authentication methods: • Integrated Windows authentication. Excel Services tries to use inbound connection strings to connect to the database that is specified in the string. you are more likely to use claims-based authentication. Trusted data connection libraries are SharePoint document libraries that contain ODC files. which you may also use for Visio Graphics Service. which must then be trusted by Excel Services. • • Server Communications You should make every effort to use claims-based authentication because it improves security and authentication when you deploy farms. and SharePoint services in different environments. Secure Store Service authentication. Office Business Applications (OBAs). the connection is established by using the security context of the authorized user account.

This service runs on a WFE server. This service routes requests for workbooks in PowerPivot Excel to PowerPivot application servers. These services manage the data in PowerPivot Excel workbooks and handle data queries. • • . The services run on an application server. This is a SharePoint 2010 service application. PowerPivot Web Service.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-33 Planning for PowerPivot Key Points PowerPivot for SharePoint adds analysis services to SharePoint so that it can host and process workbooks that you create by using the PowerPivot for Excel add-in. the following components are installed: • PowerPivot System Service and SQL Server Analysis Services service. Architecture Components When you install the PowerPivot for SharePoint add-in in a SharePoint farm. PowerPivot service application. which defines an endpoint for the PowerPivot System Service and enables centralized security for all instances of the PowerPivot System Service.

This includes the PowerPivot gallery. but you should pilot the service against your existing PowerPivot Excel workbooks to monitor and assess loading on server processor and memory. . PowerPivot servers use a filecaching methodology to reduce file reloads. PowerPivot content and libraries. you may decide to localize resources. If you have requirements for this sort of fast analysis. The three key areas are: • • Storage. However. You can install PowerPivot for SharePoint on any application server. A resource as important as this should be widely available for use across an organization. Processor and memory. if you have few users. which stores PowerPivot metadata. Very large workbooks of 1 GB can take over 10 seconds to load over a 100-Mbps network. You should plan for high-performance services for PowerPivot because of the long-running queries that are characteristic of PowerPivot processing. Environment Planning Your environment planning should reflect pilot and test deployments for PowerPivot for SharePoint. which provides previews of workbooks in PowerPivot and reports in SQL Server Reporting Services. you should consider the centralization of business resources with PowerPivot for SharePoint. All PowerPivot content is stored in SharePoint 2010 databases. Networking. you should investigate the options of working with PowerPivot.11-34 Designing a Microsoft® SharePoint® 2010 Infrastructure • • PowerPivot application database. • Using PowerPivot for SharePoint PowerPivot is a powerful BI extension for Excel 2010 and Excel Services. This is the service application database. Data transfer speed can be an issue for PowerPivot query processing. PowerPivot provides extensive analysis services. The minimum specification should include a 64-bit. This time may be even longer during a save action because SharePoint is optimized for download. dual-core processor and 8 GB of RAM. Service application metadata is stored in the instance service application database. PowerPivot can be a heavy user of both resources because it offers in-memory server-side processing of workbooks. If you have strong business requirements for Excel analysis.

rather than deploying multiple high-performance workstations.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-35 The server-side processing that is available with PowerPoint for SharePoint enables you to specify high-performance servers that can share resources across several users. . so it has minimal performance impact on the client. This is possible because PowerPivot for Excel provides browser-based delivery.

and results alignment. The features and tools that are associated with PerformancePoint Services focus on this sector of the BI marketplace. This should strongly influence your design for BI. rather than on personal productivity. This provides a UI for users to develop and manage dashboards and their elements: • • Reports Analytic charts .11-36 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for PerformancePoint Services Key Points PerformancePoint Services is designed for the delivery of community or organizational BI. The visualization and analysis functions of PerformancePoint Services can meet such requirements. KPIs. Components PerformancePoint Services includes: • Dashboard Designer. You must focus on business requirements that specify the need for performance management.

Without the Scorecard View Web Part. You should identify Web Parts that fulfill user requirements during the design phase: • Reports Web Part. users cannot render the KPIs in a dashboard. The Filter Web Part enables synchronization of Web Part content through connections between different Web Parts. and the strategy map. you can use PerformancePoint Services as an IT-provisioned solution. Excel Services reports. PerformancePoint Web Parts are built-in. rows. Status Indicator Web Part. Filter Web Part. • • • • PerformancePoint Site collections. or provide users with the training to use development options such as the Dashboard Designer.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-37 • • • Scorecards Filters Web Parts. Scorecard View Web Part. Using PerformancePoint Services Depending on your user population. columns. The Reports Web Part includes analytic charts and grids. SQL Server Reporting Services reports. server-side controls that run inside the context of Web pages. and cells within a scorecard. The Dashboard Designer bases queries on the location of the Web service. metrics. which is scoped in a SharePoint Server 2010 site collection. . The Status Indicator Web Part report displays contextually relevant information about KPIs. The Scorecard View Web Part provides view functionality for the scorecard.

Authentication PerformancePoint Services supports three authentication methods for source data access: • • Per-user identity.11-38 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning PerformancePoint Services Security Key Points PerformancePoint Services adds layers of security over SharePoint 2010. Unattended user account. SQL Server Analysis Services manages access and includes the currently authenticated user name as a parameter on the custom data field in • . Custom data. Access is based on transmission of the user identifier. This method requires you to include Kerberos delegation in your design. Access is managed through a predefined unattended user account. You can manage the service application security from the SharePoint Central Administration Web site. You must include provision to give this account access to the external data. The Secure Store Service holds this low-privilege account information. which are used for items held in lists or document libraries.

PerformancePoint Services uses SharePoint Server authorization groups and permissions. data source connections are stored in document libraries and data content is stored in document lists. You can set all locations on the farm as trusted. Trusted data connection libraries. for minimal security. You can design increased PerformancePoint Services security by using trusted file locations. These contain the content—reports. KPIs. so you must plan access to these groups: • Farm Administrator. Therefore. or you can specify centrally managed secure locations. • • . and filters— that is used for dashboards.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-39 an Analysis Services connection string. • • Roles and Permissions PerformancePoint metadata content is stored in SharePoint lists and document libraries. much of the security that you design is based on SharePoint 2010 security options for these file stores. this role needs at least contributor permissions on content lists (or list items) and data source libraries (or library items). Site Collection Administrator. The custom data option is only used for Analysis Services data sources. These contain the PPSDC files. this role needs at least contributor permissions on content lists (or list items) and data source libraries (or library items). To edit dashboard items. Access Components The access components include: • Trusted file locations. scorecards. this role needs at least contributor permissions on data source libraries (or library items). Site Administrator or List and Document Library Contributor. To edit dashboard items. In PerformancePoint Services. Trusted lists. To edit dashboard items.

Connected Drawings Visio 2010 can link to external data sources to provide refreshable input to drawing variables. This service enables users to render Visio 2010 *. For process industries. this can provide visual indicators of performance metrics as part of an integrated management Web page to users who are not using Visio 2010.vdw files onto a Web browser in the Visio Web Access Web Part. the Visio Graphics Service is an interactive reporting solution rather than a shared or multiuser version of Visio 2010.11-40 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for the Visio Graphics Service Key Points Like Excel Services. The key advantage of the Visio Graphics Service is the ability to refresh the connected data and visuals of a Visio Web drawing. and uses SharePoint 2010 to manage security and authentication. SharePoint treats unconnected drawings in the same way as any other file that is held in its . It is also possible to visualize SharePoint 2010 workflows to deliver more visual management options. The Visio Graphics Service maintains this functionality. These drawings are created in Visio 2010 and then published to the Visio Graphics Service.

SQL Server 2008 R2 (32-bit and 64-bit). SQL Server 2008 (32-bit and 64-bit). you should plan to define the sources in the list of trusted data providers. SQL Server 2000. OLE DB or Open Database Connectivity (ODBC). You can plan security to make these files available to users either directly in Visio 2010. . You can enhance security with Kerberos. or through the Visio Graphics Service visualization options.0. SharePoint Server lists that are hosted on the same farm. drawing creators can connect to and refresh data from the following sources: • • • • • • SQL Server 7. Using Microsoft Office Visio 2007 or Visio 2010 data-link technology and publishing by using Visio 2010 publishing functionality. but you can create them in Excel 2010. in a multiple farm deployment. • • • To control access. Sheet information that is stored in Excel workbooks (.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-41 document library. You must ensure that your design hosts these on the same farm.NET Framework assemblies. Visio 2010 does not have an option to create ODC files.xlsx files) that are published from Microsoft Office Excel 2007 or Excel 2010 and hosted on the same SharePoint Server 2010 farm. Authentication The Visio Graphics Service provides three authentication options: • Integrated Windows authentication (NTLM). Custom data providers that are implemented as Microsoft . SQL Server Databases Visio drawings that are published to the Visio Graphics Service can use connections that are stored in ODC files. You must also provide appropriate permissions and authentication configuration. SQL Server 2005 (32-bit and 64-bit). Excel Connections Users can connect to Excel workbooks as data sources. The Visio Graphics Service uses the identity of the user who is viewing the drawing to authenticate with the database.

• Unattended service account. As with other BI services. because the ODC file specifies the target application. the Visio Graphics Service will not use the unattended service account. Peak loads for rendering drawing and external data access. these factors include: • • • • • Size. does not enable personalized queries against a database and does not provide auditing of database calls. you . you should include the following in your planning: • • If users create a Visio drawing that connects to a SQL Server database. You should test and then pilot your implementation so that you can establish a baseline for performance and capacity. Complexity.11-42 Designing a Microsoft® SharePoint® 2010 Infrastructure • Secure Store Service. When you have created a baseline. Note: You can use NTLM with the Secure Store Service for files that require personal credentials. but do not specify an ODC file. the unattended service account is used by default. which is the default option for connection to SQL Server databases. For Web drawings in the Visio Graphics Service. You can only use Secure Store Service authentication for drawings that use an ODC file to specify the connection. Number. This method. as you would for any BI function. this uses impersonation through the Secure Store Service to map the user’s credentials to a different credential that has access to the database. If integrated Windows authentication fails. This provides a single account that an administrator can map to all authorized users in a Secure Store Service target application. Data refresh frequency (for connected drawings). Performance When you plan your Visio Graphics Service deployment. you must review performance factors. For a mixed authentication environment.

If you identify changes in the Visio Graphics Service loading. you may consider provisioning workflow diagrams that show current status and visually flag overdue or failed workflow steps. You must identify process-driven options in your business that would benefit from visualization. Using the Visio Graphics Service Visio 2010 is a relatively specialist tool. you can: • • • Load balance the service by deploying additional instances. For wider use. . particularly when you compare it to BI solutions such as Excel 2010. Increase the minimum cache age for Visio Web drawings.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-43 should then monitor performance to establish functional trends. Scale up server configurations.

This provides a central site from which administrators can manage reporting and data presentation. SharePoint 2010 not only uses SQL Server as a data source. You also need to manage the breadth of BI functionality that is available in SharePoint 2010. it can integrate with the data source by using SQL Server Reporting Services. This is an important enabler for your integration of SharePoint 2010 into a corporate BI strategy. but you can streamline overall BI management by using the BI Center.11-44 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 4 Planning for Reporting and Presentation SharePoint 2010 is designed as an integration platform. particularly if users are already capitalizing on the reporting options of SQL Server Reporting Services. Those who are familiar with the BI capabilities of Office SharePoint Server 2007 may be relatively comfortable with many of the BI options. .

you will be able to: • • Plan the integration. Describe the options and value of the SharePoint 2010 BI Center.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-45 Objectives After completing this lesson. . and deployment aspect of SQL Server Reporting Services for SharePoint 2010. authentication.

You can include report information in SharePoint Web pages to streamline management information. . the sophistication of SQL Server Reporting Services provides business advantages to SharePoint 2010 users who need to review report output for decision-making. Clearly. Incorporating report output in Web Parts. You can visualize these reports by: • • • Publishing reports on SharePoint 2010. Providing managed reports in document libraries. This delivers programmatic options for report generation and the ability to generate reports based on SharePoint 2010 lists.11-46 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning SQL Server Reporting Services Key Points You can plan SQL Server Reporting Services to extend into your SharePoint 2010 deployment.

and subscriptions. This topology has SQL Server Reporting Services and SharePoint 2010 on a single server. Planning Deployment Topologies You can plan a range of deployment topologies for SQL Server Reporting Services for SharePoint. SQL Server Reporting Services with a minimal installation of SharePoint Server to provide WFE functionality.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-47 Planning Usage Modes There are two usage modes for SQL Server Reporting Services: Connected or Integrated Mode and Local or Native Mode. Local Mode provides a more restricted option for SQL Server Reporting Services and SharePoint integration. This topology is appropriate for a small company or large department. You must establish the number of users and the complexity of the reports to identify the most appropriate topology for your farm design. • • . Two-tier deployment. These design options are based on Connected Mode deployments: • Stand-alone server. This solution distributes workload and improves performance for complex reports. scheduling. SQL Server database engine. or for a specialist departmental requirement. These reports are formatted in Report Definition Language (RDL) on SharePoint 2010 sites. The deployment does not have a back-end server running SQL Server Reporting Services. and SharePoint provides a UI through which the reports that are defined in the report server can be viewed and managed. caching. Local Mode requires SharePoint 2010 and the SQL Server Reporting Services add-in. Three-tier deployment. which would also have a SharePoint 2010 WFE implementation. This topology has three base servers to improve performance and manageability by using optimized database server hardware: • • • SharePoint 2010 with the SQL Server Reporting Services add-in. SharePoint uses the SQL Server Reporting Services add-in to render reports. This is best suited for a development environment. This topology separates SharePoint 2010 and the SQL Server Reporting Services add-in from the SQL Server database. an instance of SQL Server Reporting Services provides backend services for report storage. In Connected Mode.

11-48 Designing a Microsoft® SharePoint® 2010 Infrastructure SQL Server Reporting Services Authentication You can plan your design to use Windows authentication with Kerberos or a trusted account to access the report server. which use claims-based identity and must enforce constrained delegation in the same domain. PerformancePoint Services. For more information about configuring authentication for SQL Server Reporting Services in SharePoint Integrated Mode. Unlike Excel Services. you can use SQL Server Reporting Services reports in an external domain when you design them to use delegated Windows authentication. . and the Visio Graphics Service. see Security Overview for Reporting Services in SharePoint Integrated Mode in SQL Server 2008 R2 Books Online.

What Does the Business Intelligence Center Offer to Users? Information panels provide examples of BI tools such as status indicators. and status indicators. The help panes provide links to information about how to: • • Monitor key performance metrics by using PerformancePoint Services tools such as status lists and scorecards. data connections. Build and share reports by using Excel Services and PerformancePoint Services. status lists. . and dashboards. analytic tools and spreadsheets.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-49 Managing BI Components by Using the Business Intelligence Center Key Points The Business Intelligence Center is a site template that is designed to help you manage BI components such as scorecards. This is a good starting point for planning BI management for an environment that has little experience of BI in SharePoint 2010. dashboards.

and the Visio Graphics Services data links. • • • . Documents library. Data connections library.11-50 Designing a Microsoft® SharePoint® 2010 Infrastructure • Create dashboards by using PerformancePoint Services tools such as Dashboard Designer 2010. New dashboards that you create in PerformancePoint Dashboard Designer 2010 are automatically added to the library. The BI Center also provides direct navigation to: • The dashboard library. This is a link to the document library that stores ODC files that are created for Excel. This is a link to the PerformancePoint Services scorecard and report elements that were created in PerformancePoint Dashboard Designer 2010. This is a link to the central documents library. This Web Part page provides a collection of dashboard BI components. PerformancePoint content list. PerformancePoint.

Use the template provided to plan your BI implementation. 2. Ltd has an existing BI strategy and you must implement the SharePoint 2010 BI functions that you identify in the user requirements documentation. Ltd and Research. Read the supporting information. . There are a range of requirements and your design topology must cater for isolation of some application services between Contoso. The main tasks for this exercise are as follows: 1. Complete the Business Intelligence Planning worksheet.Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-51 Lab: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy Exercise 1: Planning the SharePoint Business Intelligence Implementation Scenario Contoso.

you are asked to deploy some of the BI components for user acceptance testing. Log on to 10231A-NYC-DC1-11 as CONTOSO\Ed with the password Pa$$w0rd. 2. Task 2: Complete the Business Intelligence Planning worksheet • In the E:\Labfiles\Lab11\Starter folder.xlsx file.docx file. Name: Excel Services 10231A Application Pool: ExcelServicesAppPool Start the new Excel Calculation Services service. Use the Application Management page to create an Excel Services service by using the following configuration parameters: • • 2. Task 1: Create an Excel Services application and start the Excel Calculation Services service 1. 2. . Create an Excel Services application and start the Excel Calculation Services service. In the E:\Labfiles\Lab11\Starter folder. The main tasks for this exercise are as follows: 1.11-52 Designing a Microsoft® SharePoint® 2010 Infrastructure Task 1: Read the supporting information 1. Create a new BI Center site collection and test the Excel Services application. 3. Read the lab scenario. read the Contoso Business Requirements. Exercise 2: Creating a BI Center and Enabling Excel Services Scenario To assess part of your design. complete the Business Intelligence Planning Worksheet.

com/sites/BICenter Type: BICenter Enterprise template: Business Intelligence Center Site collection administrator: Ed Open the new site collection and from the Documents link. Use the Application Management page to create a new site collection by using the following inputs: • • • • • 2. .Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 11-53 Task 2: Create a new BI Center site collection and test the Excel Services application 1. test that you can load the Excel Services Sample Workbook workbook in a browser.contoso. Title: BI Center URL: http://intranet.

3.11-54 Designing a Microsoft® SharePoint® 2010 Infrastructure Module Review and Takeaways Review Questions 1. . Model your BI components to assess volumes and complexity of documents. What are the three key business goals for BI? What authentication options are available for Excel Services? What is the BI Center? Best Practices Related to BI Planning Supplement or modify the following best practices for your own work situations: • • • Ensure that users understand the different capabilities of Excel Services and Excel 2010. Plan your authentication options for each BI component that you deploy. 2.

Developing a Plan for Governance 12-1 Module 12 Developing a Plan for Governance Contents: Lesson 1: Overview of Governance Lesson 2: Key Elements of a Governance Plan Lesson 3: Planning for Governance in SharePoint Server 2010 Lesson 4: Governance Implementation Features and Policies in SharePoint Server 2010 Lab: Developing a Plan for Governance 12-38 12-51 12-4 12-13 12-27 .

Helping to protect your enterprise from both security threats and noncompliance liability. can have on your plan. You must learn how to create an effective governance plan and understand the impact that key changes. . A comprehensive and successfully designed governance plan can benefit your organization by: • • • Streamlining the deployment of products and technologies such as Microsoft® SharePoint® Server 2010. responsibilities. and processes that direct and control how an organization's IT teams cooperate with their business departments to realize the organization’s business goals. such as enabling social features and solution development changes. Helping to ensure the best return on your investment in SharePoint Server 2010. policies.12-2 Designing a Microsoft® SharePoint® 2010 Infrastructure Module Overview The term governance refers to the group of roles.

and describes how best to implement your governance plan. Objectives After completing this module. Describe the key elements of a governance plan. Plan for governance in SharePoint Server 2010.Developing a Plan for Governance 12-3 This module introduces governance as a crucial element of a deployment of SharePoint Server 2010. explains what the essential components of your governance plan should be. Describe the governance implementation features and policies in SharePoint Server 2010. you will be able to: • • • • Describe the concept of governance. .

even the best intentioned deployment of SharePoint can misfire. Effective governance planning is crucial to the continued success of your implementation of SharePoint Server 2010. . Objectives After completing this lesson. Describe the key components of a governance plan. Identify what a governance plan needs to govern.12-4 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 1 Overview of Governance Governance is an essential element of a successful deployment of SharePoint Server 2010. you will be able to: • • • Describe the importance of planning governance. Without the correct governance plan in place. and introduces the key components of a governance plan. This lesson emphasizes the need for governance of deployments of SharePoint Server 2010.

Therefore. and technologies that are required to: • • Prevent portal. . a sturdy governance plan is critical to ensure that your implementation delivers the right and timely content to your users in an efficient and effective manner. who are not generally IT or content management specialists. it is crucial that your governance plan does not just improve its usability. processes.Developing a Plan for Governance 12-5 The Importance of Planning Governance Key Points An implementation of the SharePoint Server 2010 portal is only as good as its underlying structure and content. Therefore. A governance plan defines the roles. Ensure that content quality is maintained during its life cycle by implementing quality management policies for the content. In addition. but also saves your users time and effort when they create and deploy new sites. SharePoint Server 2010 is designed to empower its users. and content sprawl by defining a content and site review process. team site.

Establish clear decision-making authority and escalation procedures so that you can handle and resolve policy violations and conflicts in a timely manner. you must include decisions in your governance plan that consider how. SharePoint Server 2010 introduces new capabilities for sharing metadata across multiple site collections and server farms. • • • • • . and authors and by ensuring that the governance plan is correctly implemented and followed. The increased emphasis and availability of social computing features such as tagging. Inplace records management means that you can manage records in the same document repository as active documents. and for the actions that they perform on the site. Microsoft SharePoint Designer 2010. which require a lot of planning and control to utilize. and ratings means that there are more types of content to govern. A successfully implemented governance plan will provide this required control. Therefore. bookmarking. Governance helps ensure that they accept their responsibility for the content that they create and use. such as document IDs and Content Organizer. Ensure that the implementation strategy correctly maps to business objectives and requirements so that it continuously delivers value to the organization. users are given a lot of power and responsibility. but they need guidance about what they can do with these capabilities if they are to get the true benefit from them. • • • There are some key reasons as to why planning for governance in SharePoint Server 2010 is so important: • Many SharePoint capabilities are not mandatory for your users. SharePoint Server 2010 gives its users more customization power over their sites. By design. content designers. For example. and when to allow configuration using these new capabilities. and create their own sandboxed solutions. SharePoint Server 2010 provides new and more user-friendly records management capabilities. These new records management capabilities enable you to create and enforce your records management strategy as part of your overall governance plan for content management. where. in SharePoint Server 2010. including the ability to declare a record in place. users can use out-of-the-box themes. Ensure that content is secured and stored to comply with guidelines for records retention.12-6 Designing a Microsoft® SharePoint® 2010 Infrastructure • Provide a consistently high-quality user experience by defining guidelines for site designers.

whereas a small organization might only apply a very small amount of governance of users and their content.Developing a Plan for Governance 12-7 Identifying What Needs to Be Governed Key Points Each organization has its own individual requirements and business goals that will influence the way that they handle and apply governance. . in both cases. Large organizations may take governance to one extreme of the spectrum and have everything locked down. store. and compare. and utilize the information that is needed to meet the organization’s business objectives. The aim of information architecture is to create a solution that enables an organization’s users to gather. related data or content. any successful implementation of SharePoint Server 2010 must consider planning for governance of the following key areas of the business: • Information architecture. A wide-ranging appraisal of your company's information architecture can help you to determine possible inefficiencies such as: • Inconsistent use of metadata that can make it difficult to search for. However. retrieve.

• SharePoint Server 2010 Web servers. • . Technical support requests for local SharePoint Server 2010 servers that are running without the support team's knowledge. A poorly catalogued and managed data storage infrastructure that can result in decision-makers finding and relying on incorrect data. Servers hosting insecure applications. Improvements to backup and restore capabilities. The ability to use the Windows PowerShell™ command-line interface and scripting language tool for SharePoint administration.12-8 Designing a Microsoft® SharePoint® 2010 Infrastructure • A poorly designed and managed content storage infrastructure that can result in documents existing in multiple versions without any method for controlling and identifying authoritative and recent versions. SharePoint Server 2010 provides several new features that your governance plan must address. the fast spread of disparately managed Web servers running SharePoint Server 2010 can have unforeseen consequences. Day-to-day maintenance tasks. Critical activities. Managed accounts that automate password changes. Changes in site ownership can create confusion about content ownership or lock sites. or security system. including: • • • • • Rogue servers hosting loosely managed site collections that do not have a common search index. Multi-tenancy capabilities. that may not be properly carried out because of lack of training or inconsistent server configuration. including: • • • • • A new service application architecture that replaces the Shared Services Provider (SSP) model. which can compromise the integrity of your content. Unless you have a governance plan. A poorly designed portal navigation and presentation infrastructure that can make it difficult for users to find sites and data that are important to their job. navigation. • • • IT service hosting SharePoint Server. such as compliance with regulatory standards being inconsistently administered across servers. such as data backup and restore operations or product updates.

you must develop a customization policy that addresses the following considerations: • • • • • • Deciding whether to approve customization tools. fonts. To support these new customization capabilities while maintaining control. . and content management. such as guidelines for coding best practices. Providing standards for site development. • Customization policy. You should control the use of sandboxing. Providing standards for packaging and installation. forms. Providing standards for testing and verification processes. workflow. such as allowing the use of Web parts to integrate Microsoft Silverlight® 3 applications with SharePoint Server 2010 sites. in SharePoint Server 2010. This enhanced ability to customize brings more risks to the stability. you must implement a set of well-governed hosting services that makes SharePoint Server 2010 available and establishes control over its use and configuration. Determining methods for managing source code. which enables site owners to host custom solutions in a partly trusted environment so that they do not adversely affect the other parts of your implementation of SharePoint Server 2010. such as SharePoint Designer 2010. and who can perform the customization. Supporting different methods of customization. If you are designing an information architecture and a set of sites for use across your enterprise organization. themes. and security of your SharePoint Server 2010 environment. such as a source control system. For example.Developing a Plan for Governance 12-9 As the use of SharePoint Server 2010 increases in your enterprise. such as business intelligence. as part of your overall governance plan. and other design elements. A prescribed set of branding policies helps to ensure that sites have a consistent look and feel by using enterprise imagery. you can import a Microsoft PowerPoint® 2010 theme directly into a SharePoint site. you should include branding in your governance plan. SharePoint Server 2010 includes customizable features and capabilities. • • Branding. Determining which elements of a site can be customized. which then automatically applies the theme to all of its subsites. maintenance. and standards for documenting the code.

see http://go.com/fwlink/?linkid=92311. .microsoft.12-10 Designing a Microsoft® SharePoint® 2010 Infrastructure Additional Reading For more information about processes for managing customizations in SharePoint products and technologies.

Define procedures for common tasks such as creating a new site. Process. infrastructure maintenance. such as best practices and formal policies. Define a clear vision for the solution and articulate the roles and responsibilities. Articulate design and usage principles. service-level agreements (SLAs). or requesting a new site template. The intention of a governance . and your overall measurement plan.Developing a Plan for Governance 12-11 Key Components of a Governance Plan Key Points The key components of an effective plan for governance are: • • • • People. Technology. requesting a new shared content type or attribute. Define policies for service levels and appropriate use. You should publish these procedures in a central portal location so that site owners can easily find and follow them. information architecture. An effective governance plan provides a framework for design standards. Policy.

As your SharePoint Server 2010 environment develops. Your governance plan should include the following critical elements. The next lesson discusses each element in more detail: • • • • • Vision statement Roles and responsibilities Guiding principles Policies and standards Training . which will impact your governance of SharePoint Server 2010. you will need new IT policies to control these new features and capabilities. content confidentiality. Your governance plan should refer to all of your existing IT policies for items such as the appropriate use of technology resources. you must make your governance plan flexible enough to add references to these new policies as they arise. Therefore.12-12 Designing a Microsoft® SharePoint® 2010 Infrastructure plan is to summarize and bind the documents that describe these activities in greater detail. and records retention.

Developing a Plan for Governance 12-13 Lesson 2 Key Elements of a Governance Plan A successful governance plan contains several critical elements. Describe the roles and responsibilities for a governance plan. Describe the role of training for a successful SharePoint Server 2010 implementation. This lesson describes the key elements of a governance plan. Objectives After completing this lesson. you will be able to: • • • • • Describe the vision statement for your SharePoint Server 2010 implementation. You must carefully consider all of these elements when you develop your governance plan. . Describe the guiding principles for a governance plan. Describe the policies and standards included in a governance plan.

partners. Here is an example of a vision statement for SharePoint Server 2010: “SharePoint Server 2010 provides a holistic view of organizational assets that simplifies employee interaction with our enterprise business systems. It also helps to improve collaboration within the company and with our suppliers. . the next step is to determine and document the roles and responsibilities of the people who are involved in your implementation of a SharePoint Server 2010 solution. In this way. and customers. You will typically write the vision statement when the project to create the solution starts. it improves employee productivity and employee and customer satisfaction. A lucid vision statement provides critical guidance on the decision tradeoffs that you will inevitably need to make when you create your governance plan.12-14 Designing a Microsoft® SharePoint® 2010 Infrastructure Vision Statement Key Points Your vision statement should describe what you want to accomplish by using SharePoint Server 2010. but you will probably need to refine it as the project matures. It should describe how the solution delivers value to the business and to its employees.” After you have written your vision statement.

and maintenance.Developing a Plan for Governance 12-15 Roles and Responsibilities for a Governance Plan Key Points Roles and responsibilities define how each employee as an individual or as a member of a team is responsible for ensuring the ultimate success of a solution. configuration. or other code enhancements. • • . Some of the policy decisions that will create the outline for your governance plan and therefore form the foundation of your definitions of the roles and responsibilities include deciding: • Who you will make responsible for the technical management aspects of the environment. It defines who has authority to mediate conflicting requirements and make overall decisions about branding and policy. Documenting the roles and responsibilities of your SharePoint Server 2010 solution is a crucial part of your governance plan. Web Parts. Who you will make responsible for setting up new sites. for items such as hardware and software implementation. Who you will allow to install new features.

Can those users modify Web Parts on pages that are part of the corporate intranet publishing solution? Whether to fix some Web Parts on the page. storage. you must also give them adequate training to ensure that they follow agreed and acceptable principles and standards for allowed content. How much responsibility for page and site design you will delegate to page owners. • • • • There are several key roles to consider in your governance plan. naming. and so on. • • • Who you will grant access to each page and site. Who you will make responsible for the management of metadata. and how much central control you want to have over the values in site columns and the properties of content types. whose primary strategic responsibilities are positioning the solution as a critical mechanism for achieving business value and helping to communicate the value of the solution . they will probably need to establish some SLAs for site setup responsiveness with the business stakeholders. whether you will decommission pages where no one in the organization claims page ownership and therefore responsibility for the content.12-16 Designing a Microsoft® SharePoint® 2010 Infrastructure If this responsibility lies with your IT team. and in some smaller organizations. The following tables list some of the typical roles and responsibilities for the overall solution and for each site or site collection in a successful solution. an individual can often fulfill multiple roles. Overall solution role Executive sponsor Key responsibilities Serves as the executive-level champion for the solution. However. you will need to adapt both the responsibilities and the names that you use for each role to suit your specific organizational environment. if you delegate this responsibility to users. Who you will allow to set up or request new content types or site columns. Whether you will allow users to modify Web Parts on pages that they own in team sites. If your governance plan defines that page and site owners should be responsible for their own content management. or allow page owners to customize all of the content on their pages. and who you will enable to grant access to others. However.

primary role for ensuring that content for a particular page or site is properly collected. Manages the overall design and functional integrity of the solution from a technology perspective. Manages the site by performing the everyday tasks required to ensure that the content on the site or page is accurate. and maintained. Governance committee Serves as a governance body that has ultimate responsibility for meeting the goals of the solution. This person will also act as the Content Steward for the sites for which they are responsible. relevant. reviewed. sometimes acting as a content contributor. Site steward/contact Site designer Site user Question: Which solution role holds the primary strategic responsibility to ensure that the business gets value from the solution? . Users may have different access permissions for different sections of the solution. Uses the solution to access and share information. Works in partnership with the business owner. and at other times acting as a content consumer. Manages the overall design and functional integrity of the solution from a business perspective. published. Business owner Solution administrator Site and site collection role Site sponsor/owner Key responsibilities Serves as the centralized. and up to date. Creates and maintains the site or site collection design in environments where site design is delegated to business users.Developing a Plan for Governance 12-17 Overall solution role Key responsibilities to the management levels of the organization.

. You might also want to consider creating some supplemental reference material to help users internalize these principles. You can use the example principles in the following table as a starting point to help define a set of guiding principles for your solution.12-18 Designing a Microsoft® SharePoint® 2010 Infrastructure Guiding Principles for a Governance Plan Key Points The guiding principles of a governance plan define the organizational preferences to support the vision. If your users have a good understanding of your guiding principles. These critical statements reflect best practices that all users and site designers must understand and internalize to ensure the success of your SharePoint Server 2010 solution. or perhaps consider adding a principle of the day to the home page of your solution. you are more likely to get them to follow your governance guidelines.

There are rules. . you must consider what your users’ needs are. Key consideration One size does not fit all. Although most users may not have content contribution privileges for tightly governed intranet pages. Users may have different permissions on different areas of the portal. Example Site Design Principle You must provide a consistent user experience. Implication The different audiences for sites enable you to adapt the governance model according to business needs. You will enforce some policies across the entire organization. When you design your site. Users should be able to find key information on any collaboration site and search for the content that they need. but site owners may also apply their own policies.Developing a Plan for Governance 12-19 Guiding principle of governance Example General Principle Policies are tied to the scope and intention of the site. all users have Full Control privileges for their own My Site. All sites also follow a consistent baseline design template to ensure consistency and usability across collaboration sites. Example Security Principle Role-based security governs access control and permissions on both intranet and extranet areas of the portal. Governance policies are more flexible for sites that have limited access than for sites that are shared with a broad audience. You may not have the same permissions on every page of the portal. which has an implication for both governance and training. but you must identify when it is appropriate to deviate from a standard to achieve a business objective more effectively.

Implication Site owners are accountable for content quality and archiving old content on a timely basis.12-20 Designing a Microsoft® SharePoint® 2010 Infrastructure Guiding principle of governance Example Content Principle Site sponsors/owners are accountable. but site users are responsible for making site owners aware of content that needs updating. . but everyone owns the responsibility for content management. It is especially important to remember the “one size does not fit all” guiding principle when it comes to developing your governance plan. Key consideration Everyone is responsible for content management.

experience of working with SharePoint. you must ensure that you can enforce your policies because failing to do so may mean that the organization has become noncompliant. However. but equally you would not expect them to implement others that are not relevant to them or their job function.Developing a Plan for Governance 12-21 Policies and Standards for a Governance Plan Key Points Policies define the rules for using SharePoint Server 2010 whereas standards describe the best practices for using SharePoint Server 2010. you expect your users to follow them to the letter. and Web users typically drives standards. When you create policies. Web content. You typically create standards to encourage consistent working practices. statutory. You would expect your users to implement some aspects of the standards you define. From a governance perspective. regulatory. . If your organization is subject to regulatory oversight. or organizational requirements typically drive policies.

You should consider creating a specific policy for posting content to the home page of your portal solution. Content auditing and review. Publish policies and standards where your users can easily find and follow them. Records retention. You should ensure that you define clear policies regarding how users retain and dispose of records. Controlling file formats and names. You should consider creating a policy to define the frequency and type of review that you will have on each type of content or site. particularly on the intranet home page. You must also create policies that define the responsibilities of content owners to identify content as records and associate the appropriate record retention code to a given content item. Only editing documents that are in place to avoid breaking links. • • . Maintaining a content posting cycle. Keeping links updated. The next section describes some specific examples of policies and standards that you might want to consider using in the governance plan for your organization. Example Content Policies and Standards Consider the following example content policies and standards: • Posting content to existing pages or sites. Posting content to the home page. Only posting content that the user owns. You must also ensure that the review cycles that you define conform to any regulatory or statutory requirements.12-22 Designing a Microsoft® SharePoint® 2010 Infrastructure To ensure that your policies and standards are current and relevant: • • • Verify that your policies and standards for SharePoint Server 2010 are not at odds with other organization-wide policies. Your plan should include a policy or standard to cover the following: • • • • • • • Ensuring that only single copies of documents exist. Regularly review and amend policies and standards to keep them correctly mapped to your changing organizational needs.

Social tags and ratings. document libraries. wikis. Page layout and organization. If end-user site owners have permissions that enable them to create their own information architectures for sites under their control. when you consider defining branding standards and policies. Content-specific guidelines and policies. Your governance plan must include standards and policies for the content types and site columns that you have used in your solution.Developing a Plan for Governance 12-23 Example Design Policies and Standards Consider creating policies and standards for each of the following design elements: • Creating new subsites. and links. Your governance plan should include guidelines for how you want users to participate in social tagging and ratings. Your governance plan should clearly define any specific security policies and describe how they should be applied within your SharePoint Server 2010 sites. announcements. Content types and metadata. Security. these page designers should also be familiar with best practices for general design usability. you should do so with the site user in mind. and should provide guidance and examples of meaningful tags for your organization. discussion boards. Therefore. However. You should provide some standards and policies for specific types of SharePoint Server 2010 content such as blogs. Site users will be confused if the branding scheme changes from site to site. Branding. you must provide some guidance to help them understand best practices for creating nodes in an information hierarchy. media libraries. Your governance plan should take into account whether it is possible to change the corporate branding in a specific SharePoint Site Collection. The plan must also include policies for how users can request the creation of a new enterprise content type or site column. • • • • • • Question: What sort of policy should you create to ensure the quality and standard of content posted on your site? . Anyone who has page design permissions must remember the guiding principle about focusing on the end user.

you can increase satisfaction with your implementation of SharePoint Server 2010 and help to reduce support costs. A widespread training plan should demonstrate how to use SharePoint Server 2010 according to the standards and practices that your governance plan defines.12-24 Designing a Microsoft® SharePoint® 2010 Infrastructure Implementing Training for a Governance Plan Key Points After the governance plan itself. Training is one of those often forgotten components of a governance plan. It should also explain why those standards and practices are important. but it is crucial. training is not just about the features and functions of SharePoint Server 2010. it should be a continuing theme. . The plan should cover the type and level of training that is required for specific roles. Training should not just happen once. Also. and policies and standards of governance. guiding principles. By properly educating your user base. the most important element in a successful SharePoint Server 2010 deployment is the human element. it is also about training your user base in the roles and responsibilities. and it should prescribe any appropriate training tools.

Training Resources There are several online resources that you can use to help educate your users such as: • The SharePoint Training Kit. and interactive tutorials that are designed to walk users through various aspects of the SharePoint platform. You can download it at http://go. and digital asset management.com/fwlink/?LinkID=200903&clcid=0x409. Document. Site and site collection administration (including with Windows PowerShell). Office SharePoint Server 2007 Training Standalone Edition is a single installation edition that enables end users to install the content directly on • . videos. Site support. Some key skills include: • • • • Site and page design. This is a set of articles. It comes in the following two editions: • Office SharePoint Server 2007 Training is a portal-based edition that is designed for server administrators to install the training content on a Microsoft Office SharePoint Server site to help end users learn about Office SharePoint Server by using SharePoint itself.Developing a Plan for Governance 12-25 Who to Train You should provide adequate and job-relevant training for all staff who are involved in your SharePoint Server 2010 solution including: • • • • • • • Site administrators Site designers Site developers Help desk Content contributors Workflow approvers End users What to Train Your training plan should consider what kind of training to provide to your user base.microsoft. records.

and includes training content in the form of documents.microsoft.microsoft. It provides a central place for your training efforts. such as blogs and discussion groups. You can download it at http://go.12-26 Designing a Microsoft® SharePoint® 2010 Infrastructure their computers to learn how to use the features of Office SharePoint Server. It uses the social networking capabilities of SharePoint Server.com/fwlink/?LinkID=201242&clcid=0x409. and podcasts that teach Microsoft’s core products including SharePoint Server. Note: The SharePoint Training Kit resource is due to be updated to SharePoint Server 2010 in the near future. • The Productivity Hub. . This is a SharePoint Server 2010 site collection that offers training materials for end users and serves as a fully customizable learning community. videos. You can download it at http://go.com/fwlink/?LinkID=201243&clcid=0x409.

. This lesson describes how to build. you will be able to: • • Describe how to build a governance committee. You must be aware of several considerations when you implement a governance plan. Describe how to document and communicate your governance plan. Objectives After completing this lesson.Developing a Plan for Governance 12-27 Lesson 3 Planning for Governance in SharePoint Server 2010 There are several stages in building and implementing a successful governance plan in SharePoint Server 2010. and communicate your plan for governance. document. and provides high-level descriptions of the key processes and considerations for implementing your governance plan in SharePoint Server 2010.

12-28 Designing a Microsoft® SharePoint® 2010 Infrastructure • • Describe the process of implementing a governance plan. Describe the considerations for your governance plan. .

This committee should include representatives from as many of the following groups and roles as possible: • Executive stakeholders define the overarching goals of the governance committee. • • . IT leaders help develop their service offerings and determine how to achieve their IT responsibilities. One major aspect of your governance plan is the creation of the governance committee. Financial stakeholders ensure that governance policies and processes help increase the return on the enterprise's investment in SharePoint products and technologies. such as improving security and maintaining reliability. and information workers. while still supporting the features that the business teams require. They should also provide the authority that it requires. IT professionals.Developing a Plan for Governance 12-29 Building a Governance Committee Key Points A successful implementation of SharePoint Server 2010 requires constant communication and partnership among business managers. and they should regularly assess the success of the policies and standards that your governance plan implements.

Their input to the governance committee helps ensure that the services and information architecture of SharePoint Server 2010 meet their needs.12-30 Designing a Microsoft® SharePoint® 2010 Infrastructure • Business division leaders represent the teams that do the primary enterprise work and drive the architectural and functional requirements of the implementation of SharePoint Server 2010. how to verify code security. Information workers perform the regular day-to-day working tasks that use SharePoint Server 2010. Business leaders must also work with IT leaders to create SLAs and other support policies. They are responsible for developing a training plan and conducting all appropriate training and education. Software development leaders help determine which customization tools are approved. • • • • • Note: Your organization may not have exactly the same roles. and other code-related best practices. Compliance officers ensure that an enterprise meets its regulatory and legal requirements. They develop plans that support organizational goals and define site architecture and navigation based on their analysis of the end user’s information needs. Trainers provide the instructional expertise. Question: Which committee members are responsible for defining the architecture and navigation of the site? . They must work with information architects to determine the enterprise's information architecture and organizational taxonomy standards. or may use a different title. Information architects or taxonomists have extensive experience in planning and designing information systems and taxonomies.

Reevaluate and adjust governance principles and standards to meet new guidelines or regulatory requirements. This will promote accountability and help enforce compliance across the enterprise. Then. The committee should update its executive sponsors with regular reports. Documenting Your Plan If you are documenting your governance plan for the first time.Developing a Plan for Governance 12-31 Documenting and Communicating the Governance Plan Key Points Successful governance is an iterative process. Resolve conflicts among business divisions for IT resources. you will find it valuable to distribute the work that is required to document the details of your governance plan among key members of the governance committee. so your governance committee should conduct regular meetings to: • • • Consider incorporating any new requirements into the governance plan. do the following: .

However. the harder it is for users to absorb them. Communicating Your Plan Communicating the body of the governance plan is a central element of planning the implementation and continuing management of your SharePoint Server 2010 environment. and key policy decisions. These planning documents can easily become lengthy. and the longer they are. flexible. Although you prepare a governance plan before the implementation of your solution. Your governance plan should be an ongoing. think about the length of your documentation. Team roles and responsibilities. roles and responsibilities. One simple way to communicate the details of your governance plan to everyone in the organization is through a centralized governance portal off the intranet home page. Review each major component of your plan with sponsors. you should communicate the goals and contents of your governance plan to everyone in the organization because all users can create some form of content by using the SharePoint Server 2010 social computing features such as tagging and ratings. . live document. guiding principles. you must not think of it as being finished at any point. Also. The main audiences for the governance plan are your key business stakeholders and the end users who create and consume the site content. On this site. you should return to your governance plan to adapt to the changing needs of both the organization and your users. and other governance committee members to ensure that you agree about the major components of the plan: vision. use the vision statement that you established as a foundation for your governance plan to identify the basic governance principles. • • As you develop your governance plan. you should include sections on topics such as: • • Governance hierarchy. Meet with governance committee members who have the appropriate expertise to draft sections that address how you want to manage the various aspects of your environment. As your SharePoint Server 2010 environment develops. stakeholders.12-32 Designing a Microsoft® SharePoint® 2010 Infrastructure • Before you begin to draft the actual governance plan. Try to ensure that your plan is as succinct as possible because this will make it easier for your users to understand and follow its principles and standards. think about how users will utilize and internalize the contents of your plan.

microsoft. Site change requests.Developing a Plan for Governance 12-33 • • • • • • Individual roles and responsibilities.com/fwlink/?LinkID=201244&clcid=0x409. and http://go.microsoft. . see http://go. Additional Reading For sample governance plans for SharePoint products and technologies. How to obtain IT support. Operations policies and procedures. Application usage policies and procedures.microsoft.com/fwlink/?LinkID=200904&clcid=0x409.com/fwlink/?LinkID=201245&clcid=0x409. User experience feedback. http://go.

Separate the high-level policy groups into subgroups. The following steps provide an example of a process that you can follow in your organization when you implement your governance plan: • Build the governance policies: • • • • • Explore examples of governance plan templates and checklists from available online resources. content management. which then become your content types. such as policy name. Group the key policy elements of your plan into high-level policy groups such as security. design. and approval data. you must follow a regimented process. and collaboration. Use any existing policies as a starting point. .12-34 Designing a Microsoft® SharePoint® 2010 Infrastructure Process of Implementing a Governance Plan Key Points To implement a successful plan for governance. policy scope. policy type. Ensure that you assign metadata to the documents that you add to the subgroups to make them searchable. review status.

Ask the business units to review and approve their policies. Governance FAQ list.Developing a Plan for Governance 12-35 • Hold an initial policy review: • • Work closely with the relevant business unit to review the policies. or modify some policies. units will only see the policies that apply to them. Mark each policy as being ready for review by the business unit. possibly as part of a central Web support portal. Question: Why is it a good idea to hold business unit reviews online? . Use online reviews to avoid having to schedule multiple meetings. • Edit the policies: • • Make any agreed modifications to the policies after your initial review meetings. Governance guidance and best practices. Governance training information by user role and topic. • Publish governance information. you might conclude that you must delete. Conduct meetings with each unit to go through each policy and review each one in detail. and use versioning to maintain version control of your policy documents. • Hold a business unit review: • • • Use policy scope to provide each business unit with a unique view. The governance section should contain: • • • • Governance policies grouped by category and made searchable. This way. During this phase. create. • Make any final modifications and review the policies again: • • Make further modifications based on the business unit’s online feedback. Mark policies as approved and get ready to publish them. Create a centralized SharePoint Server 2010 governance site.

and these include some common pitfalls and best practices. Allowing your users to manage their own security when they do not have the appropriate knowledge and experience. Allowing your users to add too many items to a list. causing downgraded server performance. such as: • • • • • Not defining any policies on what you will allow users to use SharePoint Server 2010 for. Empowering your users without providing them with adequate and appropriate training.12-36 Designing a Microsoft® SharePoint® 2010 Infrastructure Considerations for the Governance Plan Key Points There are several things you need to consider when designing your governance plan. Pitfalls of Governance Plans There are several key design and implementation pitfalls that you must avoid when you develop your governance plan. Not planning for scale and growth. .

Keep your governance model as simple as possible while still maintaining its strength. Best Practices for Governance Plans Keep these best practice suggestions in mind when developing your governance plan: • • • • Use your governance plan to ensure quality and relevance of content and to ensure that all users understand their roles and responsibilities. Ensure that all users with design or Full Control privileges have internalized your design guiding principles and that content contributors understand your guiding principles for creating content. particularly for highly visible sites. Ensure that you do not make the solution more complex than necessary by overdesigning it. or at least not immediately. Make sure that you have a governance committee that has a strong supporter in the role of executive sponsor. it should provide guidance to users to ensure that the implementation of SharePoint Server 2010 remains effective and dynamic over time. but that does not necessarily mean that you need to deploy it. An effective governance plan should not need to restrict every move. Think about how you will ensure compliance with your governance plan over time. Not testing the backup and recovery processes and the data integrity.Developing a Plan for Governance 12-37 • • • Not providing SharePoint Server 2010 as the focal point for organizational information and services. Governing your users too much and therefore stifling the dynamic nature of the business and its SharePoint implementation. but only perform spot-checks on others. • • • . SharePoint may have a great feature. You might want to perform detailed monitoring and reviews of some sites.

This lesson describes the key IT service. and built-in policies that an organization can use to help govern an implementation of SharePoint Server 2010. capabilities.12-38 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 4 Governance Implementation Features and Policies in SharePoint Server 2010 SharePoint Server 2010 includes several features. . It also describes the governance of sandboxed solutions. and information architecture features and policies that you can use to implement your SharePoint Server 2010 governance plan. information management.

Describe the governance of sandboxed solutions in SharePoint Server 2010. you will be able to: • • • • • Describe the key IT service features for implementing governance in SharePoint Server 2010. Describe the key information management features for implementing governance in SharePoint Server 2010. Describe the key information architecture features for implementing governance in SharePoint Server 2010. Describe the key information management policies for implementing governance in SharePoint Server 2010.Developing a Plan for Governance 12-39 Objectives After completing this lesson. .

a single SharePoint deployment is unaware of other SharePoint deployments that might exist in the same enterprise. To help control and prevent unauthorized SharePoint deployments. administrators need to know how many unauthorized deployments might exist in the enterprise. you create and configure the following Group Policy object to disable SharePoint installations: . In Active Directory® directory service. Blocking SharePoint Installations in an Enterprise You manage SharePoint deployments at the farm level.12-40 Designing a Microsoft® SharePoint® 2010 Infrastructure IT Service Features for Implementing Governance Key Points A SharePoint service is an IT service that offers hosted sites and portals based on SharePoint Server 2010. For example. SharePoint Server 2010 enables you to block users from installing SharePoint Server 2010 and related products in your enterprise. SharePoint Server 2010 provides several IT service features that an organization can use to help govern the use of SharePoint Server 2010. Administrators need this information to manage and control all SharePoint deployments in the enterprise. therefore.

A quota dictates a limit on the amount of storage that a site collection can use. By default. or lists. Self-service site creation. You can deploy a feature as a part of a site definition or a solution package. forms. Workflows. and you should use security groups to manage permissions for these sites. and layout in the sites that your users create. you should either plan how to control the behavior of these features or turn them off completely to help protect the security of this information. You can create customized site templates for provisioning sites and use them instead of the templates that are included with SharePoint Server 2010. you can encourage consistent branding. SharePoint Designer. You can use a technique called feature stapling to attach a feature to all new instances of sites that use a given site definition. Quotas. and are associated with site items such as documents. site structure. Features. You can enable users to create their own site collections by using the Self-Service Site Creation feature. My Site features store and use personally identifiable information. User profiles and My Site policies. • • • • • • .Developing a Plan for Governance 12-41 HKLM\Software\Policies\Microsoft\Shared Tools\Web Server Extensions \14. and prevents users from adding content when the limit has been reached. set DWORD DisableInstall=00000001. You can use user profile policies to control the site content that users can see and how they can interact with that content. By default. all authenticated users can create a My Site Web site. this permission is enabled in SharePoint Server 2010 for all authenticated users. Workflows implement business processes for users of a SharePoint site. You can hide features to prevent site users from manually deactivating them. so before you deploy My Site Web sites. Using a site template. You can manage how an organization uses SharePoint Designer 2010 at either the Web application level or the site collection level. IT Service Features These are some of the IT service features in SharePoint Server 2010 that you can use to provide governance of your SharePoint Server 2010 implementation: • Site templates. A key decision in governing selfservice site creation is to determine the level of service that supports selfservice site creation.0\ SharePoint\DWORD DisableInstall To block installation. This enables you to control the features that users of your service can access. and you can individually activate a feature.

For more information about planning workflows. For more information about planning quotas management. see http://go.microsoft.com/fwlink/?LinkID=201246&clcid=0x409.microsoft.com/fwlink/?LinkID=201247&clcid=0x409.com/fwlink/?LinkID=184756. For more information about turning self-service site creation on or off. see http://go. For more information about working with site templates. see http://go. . see http://go.microsoft.12-42 Designing a Microsoft® SharePoint® 2010 Infrastructure Question: At which levels can you control the use of SharePoint Designer? Additional Reading For more information about setting the Group Policy object and for tracking SharePoint installations by using the Active Directory Domain Services marker.microsoft. see http://go. For more information about using features.com/fwlink/?LinkID=201248&clcid=0x409. see http://go.com/fwlink/?LinkID=200905&clcid=0x409.microsoft.com/fwlink/?LinkID=201249&clcid=0x409.microsoft.

Content approval. and barcodes. SharePoint Server 2010 includes several information management features that an organization can use to help govern the use of SharePoint Server 2010. These are some of the information management features in SharePoint Server 2010 that you can use to provide governance of your implementation of SharePoint Server 2010: • Document management. You can use policies that implement auditing. and retaining information. document retention. for example. You can implement these policies to help your organization achieve regulatory compliance.Developing a Plan for Governance 12-43 Information Management Features for Implementing Governance Key Points Information management in SharePoint Server 2010 consists of managing. obtaining. You can use content approval to formalize and control the process of making content available to an audience. retrieving. to ensure that • . You use document management to control the life cycle of documents in your organization. such as retaining records for a given time period. labeling.

SharePoint Server 2010 includes features that can help organizations to implement integrated records management systems and processes. You can use this site-level feature to track external actions such as litigations. see http://go.microsoft. Records management. you should consider using Hold and eDiscovery when you are developing your SharePoint Server 2010 governance plan.com/fwlink/?LinkID=200906&clcid=0x409. For more information about records management planning. • • Versioning. see http://go. Having a centralized repository for managing your digital assets enables you to apply firm control over brand-sensitive content. • • Additional Reading For more information about planning document management policy.com/fwlink/?LinkID=201250&clcid=0x409.microsoft.12-44 Designing a Microsoft® SharePoint® 2010 Infrastructure content has gone through the correct legal review and approval process before it is published.microsoft. Records management is the process by which an organization determines the types of information that should be considered records. or audits that require you to suspend the disposition of documents. You can use versioning to prevent users who have read permissions from viewing drafts of documents.microsoft. see http://go.com/fwlink/?LinkID=201252&clcid=0x409. and helps to ensure that only approved assets are available to the appropriate users.com/fwlink/?LinkID=201251&clcid=0x409. investigations. see http://go. how to manage records while they are active. For more information about planning for eDiscovery. Hold and eDiscovery. If you use SharePoint Server 2010 to manage any electronic information. and how long to retain each type of record. . Digital asset management. For more information about content approval and versioning.

and how long the information should be retained for. You can use information management policies to control who can access organizational information.Developing a Plan for Governance 12-45 Information Management Policies for Implementing Governance Key Points SharePoint Server 2010 includes several information management policies that an organization can use to help govern the use of SharePoint Server 2010. document library. Each rule in a policy is a policy feature. You can assign a policy to a list. it is a recommended best practice to write a policy statement that is displayed in Microsoft Office 2010 client programs to inform document authors about the policies that are enforced on a document. or content type. . or for a location where content is stored. An information management policy is a set of rules for a type of content. Note: When you configure an information management policy. what they can do with it.

the policy can delete a document or define a workflow task to have SharePoint Server route the document for permission to destroy it. see http://go. you should monitor policy usage frequently to help ensure that your organization is compliant. If you implement information management policies to help your organization comply with regulations. and you can use the object model of the policies to plug in other barcode providers. By default.12-46 Designing a Microsoft® SharePoint® 2010 Infrastructure SharePoint Server 2010 includes the following information management policies: • The Auditing policy.microsoft. This policy logs events and operations that are performed on documents and list items. You can configure Auditing to log events such as editing documents. You create a unique identifier value for a document and then insert a barcode image of that value in the document. • • • Information management policy reports help you to monitor how consistently your organization uses policies. For example. or changing a document's permissions level. Labels are searchable text areas that SharePoint Server generates based on metadata properties and formatting that you specify. Additional Reading For more general information about planning information management policies.com/fwlink/?LinkID=200906&clcid=0x409. The Retention policy. barcodes are compliant with the common Code 39 standard (ANSI/AIM BC1-1995. viewing them. This policy helps to dispose of or process content in a consistent way that you can track and manage. This policy enables you to track physical copies of a document. The Labeling policy. Code 39). The Barcode policy. . This policy specifies a label to associate with a type of document or list item.

Web sites. A wellgoverned architecture makes it easier for your users to find. and handle content in a consistent way. You use content types to organize. These are some of the information architecture features in SharePoint Server 2010 that you can use to provide governance of your SharePoint Server 2010 implementation: • Content types. and use your information. Information architecture in SharePoint Server 2010 refers to the organization of enterprise information such as documents. share. lists. . They define the attributes of a type of list item.Developing a Plan for Governance 12-47 Information Architecture Features for Implementing Governance Key Points SharePoint Server 2010 includes several information architecture features that an organization can use to help govern the use of SharePoint Server 2010. and Web pages to take full advantage of the information's usability and manageability. manage. You can increase your organization’s return on its portal investment by including information architecture standards and policies in your governance plan. document.

see http://go. so that users cannot run them on their client computers. if there are term sets that some users should be unable to view. • Question: Which managed metadata term sets can a user view? Additional Reading For more information about content types and workflow planning. see http://go. see http://go.com/fwlink/?LinkID=200908&clcid=0x409. An organization’s governance policies can affect how you design managed metadata services and connections.microsoft. templates. Each content type can specify metadata properties to associate with items of its type.com/fwlink/?LinkID=201253&clcid=0x409. By default. You can use this feature to restrict files from being uploaded or downloaded to a server by basing the restriction on the file extension. you may want to have a content type hub in at least one service. Taxonomy and managed metadata. To govern content types. If every document that is created must have a certain set of attributes. you can block executable files. You should acquaint yourself with your organization’s governance plan before you determine any managed metadata services and connections. you should consider associating event receivers and workflows with the forms that are used to modify the content types. For more information about managed metadata service applications. available workflows.12-48 Designing a Microsoft® SharePoint® 2010 Infrastructure or folder. and information management policies. many file types are blocked. For a complete list of the default blocked file types. Managed metadata is a hierarchical collection of centrally managed terms that you can define and then use as attributes for items in SharePoint Server 2010. and this includes executable files.microsoft.microsoft.com/fwlink/?LinkID=201254&clcid=0x409. • Blocked file types. Therefore. For example. which may contain malicious software. Users can see only global term sets and term sets that are local to the user's site collection. you should assign these term sets to separate groups. .

and you have not fully and rigorously tested the code. it is known as a sandboxed solution. Sandboxed solutions run in an isolated worker thread. so they cannot gain access to content outside the site collection in which you have deployed them. • .Developing a Plan for Governance 12-49 Governance of Sandboxed Solutions Key Points A sandbox is a restricted environment that enables programs to execute code that can access only specific resources. so they cannot use resources that belong to other solutions. they have restricted access to local and network resources. You want to utilize sandboxed solutions for load-balancing purposes. In addition. You want to provide hosted environment services and you need to allow the owners of the hosted SharePoint Server 2010 sites to upload and run custom code. which means that any issues that happen in the sandbox do not adversely affect the rest of the environment. When you deploy a solution in a sandbox. The most common scenarios for using sandboxed solutions are when: • • Your organization wants to run code on a production SharePoint Server 2010 site.

• • • Note: Only members of the Farm Administrators group can block sandboxed solutions. see http://go. If you decide that you need to use them. Additional Reading For more information about planning sandboxed solutions. you could choose to add people directly to the site collection administrators group. Planning Governance for Sandboxed Solutions When planning governance for your sandboxed solutions.microsoft. When can you transfer a sandboxed solution to the production environment as a fully trusted solution? You must define a policy for determining what level of testing is required for a sandboxed solution to be considered ready for production use in your organization. Will you dedicate a separate server to running sandboxed solutions? You can increase isolation by using remote load balancing and by only running the sandboxing service on specific servers. you must first determine whether you need to use them at all. and reset exceeded quotas. you must decide whether your main reason for wanting to deploy them is to achieve greater performance or greater security.12-50 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Sandboxed Solutions When you plan for sandboxed solutions. you should consider the following: • When should a farm administrator block or unblock a sandboxed solution? Identifying the management policy for blocking and unblocking sandboxed solutions will help to reduce confusion if there is any uncertainty about whether to block a sandboxed solution. configure load balancing. Alternatively. . you could establish a procedure for specifying a restricted number of site collection administrators to deploy sandboxed solutions on behalf of their users.com/fwlink/?LinkID=200909&clcid=0x409. Who will you allow to deploy sandboxed solutions? Depending on your organization’s security requirements.

Ltd SharePoint Server 2010 implementation. Complete the SharePoint 2010 Governance worksheet. . Read the lab scenario. Additional information that your team needs is detailed in the supplied documents. 2. Read the supporting information.Developing a Plan for Governance 12-51 Lab: Developing a Plan for Governance Exercise 1: Creating a Governance Plan Scenario You need to create a governance plan for the Contoso. You will use these documents to produce a planning worksheet to help create your governance plan. The main tasks for this exercise are as follows: 1. Task 1: Read the supporting information 1.

The main tasks for this exercise are as follows: 1. Start the Microsoft SharePoint Foundation Sandboxed Code service.contoso.com. Configure the site storage individual quota limit for the SharePoint Team site. . read the information in the Contoso Provisioning and Customization Requirements. Log on to 10231A-NYC-DC1-12 as CONTOSO\Ed with the password Pa$$w0rd. 2. complete the worksheet in the SharePoint 2010 Governance Worksheet. Configure load balancing for sandboxed solutions in the farm. Exercise 2: Implementing the Governance Plan Scenario You will now implement some of the settings in the planning worksheet for your governance plan for the team. Task 1: Enable self-service site creation on the SharePoint Team Web application • For the SharePoint Team Web application. 5. Enable self-service site creation on the SharePoint Team Web application. 3.contoso. 4. enable the Self-Service Site Creation setting.docx file. 3.xlsx file. Task 2: Complete the SharePoint 2010 Governance worksheet • In the E:\Labfiles\Lab12\Starter folder. You will do this by using the information outlined in the Contoso Provisioning and Customization Requirements document and the SharePoint 2010 Governance worksheet. Verify that users can upload sandboxed solutions in team.12-52 Designing a Microsoft® SharePoint® 2010 Infrastructure 2. In the E:\Labfiles\Lab12\Starter folder. Disable SharePoint Designer for the SharePoint Team Web application. 6.com site.

Developing a Plan for Governance 12-53 Task 2: Disable SharePoint Designer for the SharePoint Team Web application • For the SharePoint Team Web application. disable SharePoint Designer.com • In team. they are routed by using solution affinity load balancing. verify that users can upload sandboxed solutions. Task 5: Configure the site storage individual quota limit for the SharePoint Team site • Configure the site storage individual quota limit to be 1 GB. Task 3: Start the Microsoft SharePoint Foundation Sandboxed Code service • Start the Microsoft SharePoint Foundation Sandboxed Code service on the server. Task 4: Configure load balancing for sandboxed solutions in the farm • Verify that when users want to run sandboxed solutions in the farm.contoso.com. Task 6: Verify that users can upload sandboxed solutions in team.contoso. .

4.12-54 Designing a Microsoft® SharePoint® 2010 Infrastructure Module Review and Takeaways Review Questions 1. relevant. and up to date? What is a simple way of communicating the details of your governance plan to everyone in the organization? Which IT service feature enables you to stop users adding more content to the site after the site collection reaches a specific threshold? 3. What are the five key elements of a SharePoint Server 2010 governance plan? Whose role is it to perform the day-to-day management tasks required to ensure that the content on the site or page is accurate. 2. .

Ensure that all users with design or Full Control privileges have internalized your design guiding principles and that content contributors understand your guiding principles for creating content. Ensure that you do not make the solution more complex than necessary by overdesigning it. SharePoint may have a great feature. or at least not immediately. • • . it should provide guidance to users to ensure that the implementation of SharePoint Server 2010 remains effective and dynamic over time.Developing a Plan for Governance 12-55 Best Practices Related to Developing a Governance Plan Supplement or modify the following best practices for your own work situations: • • • Make sure that you have a governance committee that has a strong supporter in the role of executive sponsor. Keep your governance model as simple as possible while still maintaining its strength. An effective governance plan should not need to restrict every move. but that does not necessarily mean that you need to deploy it.

.

Designing a Maintenance and Monitoring Plan 13-1 Module 13 Designing a Maintenance and Monitoring Plan Contents: Lesson 1: Principles of Maintenance and Monitoring Lesson 2: Creating a Maintenance Plan for SharePoint 2010 Lesson 3: Creating a Monitoring Plan for SharePoint 2010 Lesson 4: Considerations for the Maintenance and Monitoring of Associated Technologies Lab: Designing a Maintenance and Monitoring Plan 13-35 13-46 13-3 13-11 13-23 .

Objectives After completing this module. Describe the considerations for developing a maintenance and monitoring plan that incorporates technologies that support SharePoint 2010. Create a maintenance plan for SharePoint 2010. To do this. . you will be able to: • • • • Describe the essential principles of a maintenance and monitoring plan.13-2 Designing a Microsoft® SharePoint® 2010 Infrastructure Module Overview You must ensure that your Microsoft® SharePoint® 2010 infrastructure can operate at maximum efficiency. This plan will help you to ensure that the most vulnerable aspects of the infrastructure are in the best possible state. given the constraints of your particular environment. you require a maintenance and monitoring plan. Create a monitoring plan for SharePoint 2010.

you should be mindful of the end requirements. It will also help you to meet service-level agreements (SLAs) and manage the change process. Describe how to incorporate change management policies into the maintenance and monitoring plan. . Objectives After completing this lesson. Explain how to meet the requirements of quality assurance (QA) planning. You must understand the goals of maintenance and monitoring in your organization. This will help you to plan for all of the necessary aspects of maintaining and monitoring your SharePoint 2010 infrastructure. you will be able to: • • • Describe the goals of maintenance and monitoring planning.Designing a Maintenance and Monitoring Plan 13-3 Lesson 1 Principles of Maintenance and Monitoring When you develop a maintenance and monitoring plan.

Service-Level Agreements Many organizations issue one or more service standards that specify required uptime. The goal of this plan is to enable you to keep SharePoint 2010 running at optimum performance and perform proactive maintenance tasks. customers. and partners. and recovery times.13-4 Designing a Microsoft® SharePoint® 2010 Infrastructure Goals of Planning for Maintenance and Monitoring Key Points To meet the business requirements of your organization. A well-designed maintenance and monitoring plan enables you to meet the SLAs that affect the SharePoint 2010 environment. you should design and document a maintenance and monitoring plan. Organizations also often use SLAs to detail a required level of service between the organization and its suppliers. performance levels. These service standards or SLAs may exist between departments in the organization to detail the expectations that one department has of another. .

It is also easy to review and update the details of your maintenance and monitoring plan if you document it. Who should update and maintain the necessary documentation. .com/fwlink/?LinkID=200910&clcid=0x409. such as the teams that are responsible for the following services: • • • Active Directory® directory service Internet Information Services (IIS) Microsoft SQL Server® SharePoint 2010 relies on all of these services. How often to perform each task. Additional Reading For a sample SLA. You can provide the plan document to the SharePoint 2010 administrators who are responsible for maintenance.microsoft. When you design your maintenance and monitoring plan. Your plan should include: • • • • • Which tasks to perform. you should liaise with other IT teams. Documenting the plan is especially important in large hierarchies where there can be many SharePoint 2010 administrators and other IT teams all working to meet SLAs for the IT infrastructure.Designing a Maintenance and Monitoring Plan 13-5 Documentation Detailed documentation simplifies monitoring and maintenance throughout the hierarchy. so you must ensure that your maintenance and monitoring plan incorporates any tasks that are necessary to maintain and monitor them. It ensures that the maintenance and monitoring processes that you define are repeatable. see Appendix B: Sample SLA at http://go. Who should perform each task. How to perform each task.

13-6 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Quality Assurance Key Points QA refers to a program for the systematic monitoring and evaluation of the various aspects of a service to ensure that you meet agreed standards of quality. QA programs vary. . ITIL gives detailed descriptions of a number of important IT practices and provides comprehensive checklists. tasks. management. and provision of IT services. Many service management methodologies incorporate QA processes. ITIL The IT Infrastructure Library (ITIL) is a set of concepts and practices for the development. but they focus on improving and stabilizing the service that you provide and minimizing issues that lead to interruptions in service. The following sections describe some examples. and procedures that any IT organization can tailor to its requirements.

risk. delivering. You should define the following: • SLAs. Governance. MOF covers the entire IT life cycle by integrating: • • • • Community-generated processes for planning. Your maintenance and monitoring plan should include a defined schedule for backup.Designing a Maintenance and Monitoring Plan 13-7 MOF Microsoft Operations Framework (MOF) 4. You should verify that the backup and restore process will work by testing a selection of backups on a regular basis. Sample QA Program As an example. Microsoft Solutions Framework (MSF) best practices. You should formalize expectations as to which data you can recover and how long it will take you to recover it. you should incorporate QA processes for your supplier. Again. does the offsite storage vendor have the appropriate certification to hold your data securely? • • • . It helps you to establish and implement reliable. This may vary from site to site in your SharePoint 2010 infrastructure. cost-effective IT services. Your maintenance and monitoring plan should include processes for verifying your backups. If you plan to use offsite storage. and compliance activities. Backup schedule. operating. You should define what you will back up—such as content and metadata—along with schedules for backup. and managing IT. This information should be part of the SLA documentation.0 delivers practical guidance for everyday IT practices and activities. consider the QA processes that you require for the backup and recovery of your SharePoint 2010 infrastructure. Restore verification procedure. Management reviews. For example. Many organizations use offsite storage as an added level of protection for their data. Offsite storage. the backup schedule will vary depending on the data that you must back up.

com/fwlink/?LinkID=201255&clcid=0x409.microsoft.13-8 Designing a Microsoft® SharePoint® 2010 Infrastructure Additional Reading For more information about MOF 4. see http://go.0. .

Well-defined change management also helps you to maintain the balance between the need for change and the potential impact of changes. You should also include standardized procedures for the rollback of any changes. . Externally imposed requirements. you will be able to handle all changes in an efficient and prompt manner if you implement change management by using standardized methods and procedures. whether in IT or any other part of the business. Alternatively. Whatever the cause. such as compliance with legal regulations. may lead to changes in your SharePoint 2010 infrastructure. the impetus for change may come from the need to improve efficiency and effectiveness or enable new business initiatives. The objective of change management is to ensure that people who make changes use standardized methods and procedures for all changes to the IT infrastructure. The use of standardized methods and procedures minimizes the number and impact of any unexpected results of the change. Change management provides a way for you to track changes that are made in your organization.Designing a Maintenance and Monitoring Plan 13-9 Change Management Key Points Change management is a key process in service management.

Submit changes for approval. predictable manner. Impose controls on changes. Record maintenance tasks and changes. Create an emergency change process for errors and other issues that significantly impair system function and business operations or increase the system’s vulnerability. Assess and document the effect of the requested change. Separate responsibility for creation. Create a formal process for requesting changes and recording these change requests. Change Management Policies When you develop your maintenance and monitoring plan. or moving content. changing user permissions. You should make the following features part of your change management policy: • • • • • Document and control change management procedures. and application by assigning them to different personnel to avoid changes that you do not want. you should incorporate change management policies. Monitor changes to assess the efficacy of change management policies.13-10 Designing a Microsoft® SharePoint® 2010 Infrastructure Monitoring and maintaining your SharePoint 2010 infrastructure will include making changes such as applying service packs. Change management policies define the standardized methods and procedures for changes to the environment. • • • • • • . approval. Update change documentation when necessary. For example. Apply controls to new SharePoint 2010 solutions. Change management helps you to make changes in a controlled. your change management policies can mandate that you test custom SharePoint 2010 solutions in a staging farm before you move them to the production farm. You can use your SharePoint 2010 staging environment or sandboxing to ensure that new solutions do not behave in a detrimental manner.

You should also include maintenance policies for the different SharePoint 2010 environments in your organization.Designing a Maintenance and Monitoring Plan 13-11 Lesson 2 Creating a Maintenance Plan for SharePoint 2010 Creating a maintenance plan will help you to manage the most at-risk elements of SharePoint 2010. you can ensure that regular tasks are performed as scheduled. By automating maintenance tasks. you will be able to: • • Describe considerations for automating maintenance tasks in SharePoint 2010. . Your maintenance plan should also include a plan for deploying software updates that meets the requirements of the organization’s change management policies. Objectives After completing this lesson. List guidelines for managing diagnostic log files in SharePoint 2010. because the staging and development environments will have different maintenance requirements from the production environment.

Describe policies for staging and development environments. .13-12 Designing a Microsoft® SharePoint® 2010 Infrastructure • • • Develop a plan for deploying software updates. Discuss guidelines for developing a maintenance plan.

rather than the deprecated Stsadm command-line tool. Windows PowerShell Windows PowerShell is a command-line shell and scripting language that helps IT professionals to achieve greater control and productivity. The . lists. you can use Windows PowerShell to create scheduled tasks for site collection backups. It also enables you to manage regular tasks proactively. You should use Windows PowerShell when you perform command-line administrative tasks. sites. and almost any aspect of SharePoint 2010 administration. Windows PowerShell is excellent for automating maintenance tasks. You can use a number of tools to help you to automate your regular maintenance tasks. site collections. The following sections will discuss the use of Windows PowerShell™ and timer jobs. For example. You can use Windows PowerShell to manipulate Web applications.Designing a Maintenance and Monitoring Plan 13-13 Considerations for Automating Maintenance Responses Key Points You can automate maintenance tasks to improve your ability to respond to maintenance requirements in a timely fashion.

You can view the status of timer jobs that have been run by using the Central Administration Web site or Windows PowerShell.13-14 Designing a Microsoft® SharePoint® 2010 Infrastructure Stsadm command-line tool is included in SharePoint 2010 to support compatibility with previous product versions. Web Analysis reports. . The system writes usage and health data to the logging folder and to the logging database.microsoft. For more information about SharePoint 2010 timer jobs. This health and usage data may consist of performance counter data. see http://go.com/fwlink/?LinkID=201256&clcid=0x409. It contains a definition of the service to run and specifies how frequently the service should start. search usage data. Additional Reading For more information about SharePoint 2010 products administration by using Windows PowerShell. event log data. or various performance aspects of the Web servers.microsoft. The system uses this data to create health reports. see http://go. Some services rely on timer jobs to run according to a schedule. The monitoring features in SharePoint 2010 use specific timer jobs to perform monitoring tasks and collect monitoring data. Timer Jobs A timer job is a trigger to start to run a specific Windows® operating system service for Microsoft Office SharePoint. and administrative reports.com/fwlink/?LinkID=200912&clcid=0x409.

Use the following guidelines as best practices: • Change the drive that logging writes to. you may want to customize the settings depending upon the business requirements and the life cycle of the farm. You can also change it to a lower level to reduce the size of the log and the resources that you require to log the data. You can change it to a more verbose level to capture as much data as possible about the state of the system during the changes. you can change the logging level. diagnostic logging is configured to write logs to the drive and partition where SharePoint 2010 is . By default. However. This will limit the types and amount of information that will be written to each log. The default settings are sufficient for most situations.Designing a Maintenance and Monitoring Plan 13-15 Guidelines for Configuring Diagnostic Logging Key Points SharePoint 2010 collects data in the diagnostic log that can be useful for troubleshooting. Best Practices The SharePoint 2010 environment may require configuration of the diagnostic logging settings after initial deployment and throughout the system’s life cycle. You can set the level of diagnostic logging for the event log and for the trace log. If you are deploying a new feature or making large-scale changes to the environment.

or if you keep logs for only a few days. Enable event log flooding protection. SharePoint 2010 does not limit the amount of disk space that diagnostic logging can use. You can use verbose-level logging to record a greater level of detail when you are making critical changes and then reconfigure logging to record only higher-level events after you make the change. Regularly back up logs. The diagnostic logs contain important data. the repeating events are detected and suppressed until conditions return to a typical state. so you should make the ULS Viewer available to those who must read the log. You enable this setting to configure the system to detect repeating events in the Windows event log. if verbose-level logging is configured. and append logs to help to locate data that is relevant . When the space that is available to the log file is used. many entries are written to the log. back them up regularly to make sure that this data is preserved. sort. Consequently. you should configure logging to write to a different physical drive. In SharePoint 2010. the oldest logs are deleted first.13-16 Designing a Microsoft® SharePoint® 2010 Infrastructure installed. When you plan file permissions for farm administrators. especially if you configure logging to write verbose-level events. You can filter. When the threshold is met. Verbose logging logs every action that SharePoint 2010 takes. a slow connection may result in poor log performance. The ULS Viewer enables users who have access to ULS log files to view the logs by using a user-friendly interface. You should also consider the connection speed of the drive. The ULS log can be difficult to interpret in text form. SharePoint automatically deletes when you restrict log drive space usage. • Restrict log disk space usage. Diagnostic logging can use large amounts of drive space. When the same event is logged repeatedly. • • • Unified Logging Service Office SharePoint uses the Unified Logging Service (ULS) to write content to log files. Use the Verbose setting sparingly. highlight. and writing to the logs can affect drive performance. therefore. the oldest logs are removed and new logging data information is recorded. you should consider allowing access to this folder so that the farm administrator can read the log directly. Verbose-level logging can quickly use drive space and affect drive and server performance. You should limit the disk space that logging uses to make sure that it does not fill the disk. the ULS log is located at C:\Program Files \Common Files\Microsoft Shared\Web Server Extensions\14\LOGS. Therefore. by default.

see http://go. For more information about the ULS Viewer. You can use this information to diagnose problems with machines running ULS services or to monitor machines and the events that they create.Designing a Maintenance and Monitoring Plan 13-17 to the issue that you are attempting to resolve.com/fwlink/?LinkID=201257&clcid=0x409. SharePoint 2010 uses correlation IDs.com/fwlink/?LinkID=200913&clcid=0x409. you can identify the request that caused the error and resolve the issue. Additional Reading For more information about how to configure diagnostic logging for SharePoint Server 2010. see http://go. . which are identifiers that are internally associated with every request and are displayed with error messages. By searching the ULS log for the correlation ID.microsoft.microsoft.

In this step. The second step in the update phase is the deployment step. reducing the requirement to restart the server. You must update all servers that are running SharePoint 2010. The first step is the patching step. Services that use files that have to be replaced are temporarily stopped. but you should begin with the Central Administration server to ensure that Central Administration reports the most upto-date information. SharePoint 2010 copies new binary files to the Central Administration server. Update Phase The update phase has two steps: the patching step and the deployment step. The process of deploying software updates has two distinct phases: updating and upgrading.13-18 Designing a Microsoft® SharePoint® 2010 Infrastructure Considerations for Deploying Software Updates Key Points SharePoint 2010 has improved installation and management features that provide a better end-to-end administrative experience when you install a software update. there are some instances when you must restart the server. During the patching step. However. the installer copies support files to the appropriate directories on the server that is .

The next step is to upgrade the databases. However.Designing a Maintenance and Monitoring Plan 13-19 running SharePoint 2010. The first step is to upgrade all of the SharePoint 2010 processes that are running. The upgrade process can run on a single server.com/fwlink/?LinkID=200914&clcid=0x409. You can postpone the upgrade phase. inconsistent farm behavior may result from postponing the upgrade for more than several days. Planning Considerations When you plan the deployment of software updates and service packs. The update phase is complete after the deployment step. If you postpone for a longer period. You can use a staging environment to ensure that the software update will function correctly in your SharePoint 2010 environment. . The upgrade phase is task-intensive and therefore takes the most time to finish. There is full support for automatic updates that use Windows Server Update Services (WSUS). you must complete the installation by starting the upgrade phase. and Microsoft Update. see http://go. so other servers in the farm can continue to service requests. This step ensures that all of the Web applications are running the correct binary files and will function correctly after the software update. Windows Update. This enables you to install the update binary files and postpone update completion to a later time. you increase the risk that farm behavior issues will occur. Administrators can monitor the status of the update by using the Central Administration Web site or Windows PowerShell. but you must complete the software update by running the upgrade on the servers. An automatic update will install the binary files on the farm servers. you should consider the following features: • SharePoint 2010 supports backward compatibility between update versions on different servers. • • • Additional Reading For more information about software updates in SharePoint Server 2010. The next and final phase to deploy software updates is the upgrade phase. Upgrade Phase After you finish the update phase.microsoft.

staging. Each environment has a different role to play in the maintenance of the SharePoint 2010 infrastructure as a whole.13-20 Designing a Microsoft® SharePoint® 2010 Infrastructure Considerations for Maintaining Staging and Development Environments Key Points When you develop a maintenance plan for SharePoint 2010. Large organizations may have a number of SharePoint 2010 environments. A staging environment should therefore mimic at least the key features and configuration of the production environment to provide a useful testing platform. Many organizations implement various environments to meet their business goals. you will need to ensure that they are managed in an appropriate manner. and development. including production. . Depending on the environments that your company implements. Staging Environment Staging environments provide a safe environment for testing changes to your SharePoint 2010 infrastructure before you deploy them in the production environment. you should consider the different environments in your organization.

You should use development environments to provide a platform for the development of SharePoint 2010 solutions. Deployment of software updates. Service packs. . Custom components. and other development features. The development environment is not usually identical to the live production environment. Consider using a development environment for: • • • The distribution and management of development virtual machines (VMs). Source control. Add-ons and integrations. and event handlers.Designing a Maintenance and Monitoring Plan 13-21 You should use staging environments to perform final tests on the solutions and content before they are published to content consumers and end users. Web Parts. Consider using a staging environment to test: • • • • • Incremental updates of data. Development Environment Development environments are used by developers who create custom components such as Windows Workflow assemblies. and Microsoft Visual Studio Team Foundation Server. custom code. License management. because it typically includes developer tools such as Microsoft Visual Studio® 2005.

What categories would you use to organize your maintenance tasks? Question: What is the next step in developing a maintenance plan? Question: Give examples of tasks and activities for each category that you have defined. .13-22 Designing a Microsoft® SharePoint® 2010 Infrastructure Discussion: Developing a Maintenance Plan Key Points Question: You must develop a wide-ranging maintenance plan for your SharePoint 2010 infrastructure.

List guidelines for using Performance Monitor to monitor SharePoint 2010. Monitoring tools such as SharePoint Health Analyzer and Performance Monitor help you to analyze and resolve problems. Discuss how to develop a monitoring plan. Describe considerations for logging usage and health data in SharePoint 2010. Objectives After completing this lesson. List guidelines for monitoring search. and view metrics for the sites. you will be able to: • • • • • Describe considerations for using SharePoint Health Analyzer.Designing a Maintenance and Monitoring Plan 13-23 Lesson 3 Creating a Monitoring Plan for SharePoint 2010 The monitoring features in SharePoint 2010 help you to check how the SharePoint 2010 system is running. .

Performance. SharePoint Health Analyzer runs predefined health rules against servers in the farm. Each health rule falls into one of the following categories: Security. the status is written to the Health Reports list in Microsoft SharePoint Server 2010 and the Windows event log. subscribe to the RSS feed for the list.13-24 Designing a Microsoft® SharePoint® 2010 Infrastructure Considerations for Using SharePoint Health Analyzer Key Points SharePoint 2010 includes SharePoint Health Analyzer. and usage problems. SharePoint Health Analyzer also creates an alert in the Health Analyzer Reports list on the Review problems and solutions page in Central Administration. export the list items into Microsoft Office Excel®. performance. and perform many other tasks. or Availability. which is a new analysis tool that enables you to check for potential configuration. If any rule fails. Configuration. You can edit Health Analyzer Report list items. . You can also open the rule that raised the alert and change its settings. create custom views. A health rule runs a test and returns a status that tells you the outcome of the test. You can click an alert to view more information about the problem and see steps to resolve the problem.

SharePoint 2010 ships with more than 50 predefined health rules to help to ensure that the SharePoint 2010 environment is properly configured and healthy right from the start. All health rules are available through Central Administration. on the Monitoring page. for either immediate or scheduled execution.Designing a Maintenance and Monitoring Plan 13-25 Health Rules You can configure a health rule to run on a defined schedule or on an impromptu basis. Receive e-mail alerts when problems are found. Configure rules to run on a predefined schedule. You can configure specific health rules to perform the following tasks: • • • • • Enable or disable rules. Define the scope where the rules run. The status of the Health Analyzer rules for a SharePoint farm are displayed in the Review Problems and Solutions link in the Monitoring section of Central Administration. Run rules on an impromptu basis. The rules are also available in the SharePoint 2010 management pack for Microsoft System Center Operations Manager. .

. SharePoint 2010 writes usage and health data to the logging folder and the logging database. Configuring Usage and Health Data Collection You can use the Central Administration interface to configure logging settings for usage data collection. and administrative reports. search usage data. and various performance aspects of the Web servers. metrics for site collections and sites. timer service data. The Usage and Health Data Collection Service application performs the logging and is enabled during the initial farm setup. You can specify which events to log and a location and maximum size for the log file. The default logging database is WSS_Logging.13-26 Designing a Microsoft® SharePoint® 2010 Infrastructure Considerations for Logging Usage and Health Data Key Points SharePoint 2010 can log usage information such as feature usage and performance data to the new usage logging database and log files. Health and usage data consists of event log data. You can also configure health data collection. SharePoint 2010 uses this data to create health reports. Web Analysis reports. performance counter data. including scheduling collection times.

. such as setting longer retention periods for page request events. and the events logged are: • • • • • • • • Content import usage Content export usage Page requests Feature use Search query usage Site inventory usage Timer jobs Rating usage Configuring Usage Data Collection for a Specific Event You can also configure some aspects of Usage and Health Data Collection by using the SharePoint 2010 Management Shell. for example. You can use Windows PowerShell cmdlets to configure settings for logging. You can also configure settings for single events.Designing a Maintenance and Monitoring Plan 13-27 Usage data collection is enabled by default. you can specify a new logging database.

Users can configure search alerts on the search query page when a search query is completed and results are displayed. Search Alerts Search alerts enable end users to receive e-mail and Short Message Service (SMS) text message notification when specified search query results are changed or updated. SharePoint 2010 uses this information to improve the relevancy of search results and improve query suggestions. You should enable search alerts when you want to allow end users to create alerts for search queries. Each user can only configure and view search alerts that he or she has created.13-28 Designing a Microsoft® SharePoint® 2010 Infrastructure Guidelines for Monitoring Search Key Points Search is a key service in SharePoint 2010. and you must monitor it closely to ensure optimal performance. . Query Logging SharePoint 2010 search logs information about user search queries and search results that users select on their computers. SharePoint 2010 includes several tools that you can use to help you to monitor search services.

Designing a Maintenance and Monitoring Plan

13-29

Members of the Farm Administrators group or an administrator of the Search Service application can also create reports that are based on this information.

Search Administration Reports
You can use search administration reports to help you to determine the health of Search Service applications on a SharePoint farm. There are three types of search administration reports: • Basic search administration reports. These reports are enabled by default. They show high-level monitoring data aggregated from all components for the selected Search Service application. Advanced search administration reports. These reports are enabled by default. They show more in-depth monitoring data aggregated from all components for the selected Search Service application. Verbose search administration reports. After you enable verbose query monitoring for search, this trend report uses per-query data to derive query latency percentiles.

Guidelines for Crawl
The crawl log tracks information about the status of crawled content. You can use this log to determine whether crawled content was successfully added to the index, whether it was excluded because of a crawl rule, or whether indexing failed because of an error. The crawl log also contains more information about crawled content, including the time of the last successful crawl, the content sources, and whether any crawl rules were applied. You can use the crawl log to diagnose problems with the search experience.

13-30

Designing a Microsoft® SharePoint® 2010 Infrastructure

Guidelines for Using Performance Monitor

Key Points
Performance Monitor is a simple yet powerful visualization tool for viewing performance data, both in real time and from log files. Using Performance Monitor, you can examine performance data in a graph, histogram, or report. You can also configure Performance Monitor to alert you if a counter passes a specified threshold. This enables you to manage the system proactively. SharePoint 2010 automatically installs new performance counters that you can use to monitor the performance of various aspects of the SharePoint 2010 infrastructure. The following table lists some useful counters to monitor that are related to SharePoint 2010.

Designing a Maintenance and Monitoring Plan

13-31

Counter Search - Query rate

Description The number of queries that are posted to the server per second. The number of queries that produce successful searches.

Threshold 10 per second.

Search - Succeeded queries

You should mostly use this counter for troubleshooting search problems. Microsoft has tested up to 5 million documents per content index. This indicates the catalogs that users search most frequently.

Search catalogs Number of documents

The total number of documents in the catalog.

Search catalogs - Queries rate_(index names or all instances)

The number of queries that are posted to indices per second.

You should also monitor hardware-related performance counters for your servers. The following table lists some useful hardware-related counters to monitor.
Counter Processor - % Processor Time Memory - Available Mbytes Physical Disk - Current Disk Queue Length Description The percentage of processor time that is used. The amount of memory that is available, in MB. The number of read or write requests that are waiting to execute to the disk. For a single disk, it should idle at two to three or lower. The number of packets in the queue that are waiting to be sent. A sustained average of more than two packets in a queue indicates a bottleneck that you must resolve. Required value Low

High

Low

Network Interface Output Queue Length

Low

13-32

Designing a Microsoft® SharePoint® 2010 Infrastructure

You should also monitor Web service performance counters for your servers, because SharePoint 2010 implements Web applications. The following table lists some useful counters to monitor that are related to Web services.

Counter Request - Avg Req/Sec

Description The average number of requests per second. Includes failed and passed requests, but not cached requests. The average of passed requests. This information also helps to determine the average number of failed requests per second. The average of the total time that is taken to load a page with all of its HTTP elements. The maximum user load that is provided during a test run. The average number of errors that occur per second. Includes all types of errors.

Required value High

Request - Avg Req Passed/Sec

High

Page - Avg Page Time (Sec)

Low

Scenario - User Load

High

Errors - Errors/Sec

Low

Designing a Maintenance and Monitoring Plan

13-33

Finally, you should monitor SQL Server performance counters for your servers, because SharePoint 2010 uses SQL Server databases. The following table lists some useful database-related counters to monitor.

Counter SQL Server: Buffer Manager - Buffer cache hit ratio SQL Server: Cache Manager - Cache hit ratio

Description The percentage of pages that are found in memory.

Required value High

The ratio between cache hits and misses. This counter is a good indicator of the caching mechanism in SQL Server. The number of times that the log files have been extended. If there is a lot of activity in this counter, allocate static space large enough for log files. The number of users who are currently connected to the computer running SQL Server.

High

SQL Server: Databases Log growths

Low

SQL Server: General Statistics - User Connections

N/A

13-34

Designing a Microsoft® SharePoint® 2010 Infrastructure

Discussion: Developing a Monitoring Plan

Key Points
Question: You must develop a monitoring plan for your SharePoint 2010 infrastructure. What categories would you use to organize your monitoring tasks? Question: What is the next step in developing a monitoring plan? Question: Give examples of tasks and activities for each category that you have defined.

Designing a Maintenance and Monitoring Plan

13-35

Lesson 4

Considerations for the Maintenance and Monitoring of Associated Technologies

SharePoint 2010 relies on SQL Server to provide database hosting and IIS to provide Web services. You must include these associated technologies in your maintenance and monitoring plan. If any issues arise in any of these applications, they may cause a catastrophic failure of your SharePoint 2010 infrastructure.

Objectives
After completing this lesson, you will be able to: • • Describe aspects of database management that you should perform to maintain SharePoint 2010. Describe aspects of IIS management that you should perform to maintain SharePoint 2010.

13-36

Designing a Microsoft® SharePoint® 2010 Infrastructure

• •

Describe how System Center Operations Manager can support SharePoint 2010. Discuss maintaining and monitoring the technologies that are associated with SharePoint 2010.

Instead. and are checked for anomalies. and time-consuming. In recognition of these issues. SharePoint 2010 administrators may not perform database management tasks themselves. Moreover. it is recommended that SharePoint 2010 administrators conduct routine maintenance on each database. In large organizations. These routine database maintenance tasks are often overlooked because they are redundant. they must liaise with the database administrator (DBA) team to ensure that appropriate maintenance and monitoring is performed for the SharePoint 2010 databases. The maintenance plan conducts scheduled SQL Server maintenance tasks to ensure that databases are performing optimally. SharePoint 2010 administrators are overwhelmed with many other tasks throughout the day. Microsoft has provided a way to automate these daily tasks with a SQL Server maintenance plan. A SQL Server maintenance plan performs a comprehensive set of SQL Server jobs that run at scheduled intervals. tedious. are regularly backed up.Designing a Maintenance and Monitoring Plan 13-37 Database Management Key Points For SQL Server databases to perform at optimal levels. You can use the Maintenance .

Rebuilding indices. the wizard can configure database and transaction log backups.13-38 Designing a Microsoft® SharePoint® 2010 Infrastructure Plan Wizard to create and schedule these daily tasks automatically. Cleaning up database job history. A comprehensive maintenance plan includes these primary administrative tasks: • • • • • • Checking database integrity. Updating database statistics. In addition. . Updating index statistics. Performing internal consistency checks and backups.

application domains. specified by elapsed time or error response codes. you can configure IIS 7 to automatically capture full trace logs for any request. IIS version 7 logs real-time state information about application pools. including the following: • • • Use Performance Monitor to monitor counters and configure alerts. To help you with IIS-specific troubleshooting.Designing a Maintenance and Monitoring Plan 13-39 IIS Management Key Points SharePoint 2010 relies on IIS to host the Web applications that contain SharePoint site collections and sites. . IIS 7 also provides detailed trace events that track a request throughout the complete request-and-response process. To enable the collection of these trace events. sites. There are many ways to monitor IIS. so that you are aware of any potential issues with the hosting environment. Use SharePoint Health Analyzer. Examine the IIS log files. worker processes. You should ensure that your maintenance and monitoring plan includes this. and running requests.

When users access your Web Front End (WFE) server that is running IIS 7. and requests. In addition. application domains. you can configure IIS to log site visits. Failed Request Tracing Rules Failed request tracing rules enable you to capture an XML-formatted log of a problem when it occurs. you enable or disable tracing and configure log file settings. you can configure log file rollover options to control the length of time that log file data is stored on the server. Tracing for failed requests is configured at two levels: • • At the site level. You should disable logging for a site when you no longer want IIS to log requests to a site selectively. application pools. You should enable logging for a server when you want IIS to log only certain requests to a server based on configured criteria.13-40 Designing a Microsoft® SharePoint® 2010 Infrastructure Logs In addition to the Windows Server® 2008 system log and security log. The logs provide valuable information that you can use to identify any unauthorized attempts to compromise your Web server. Worker Processes The worker processes feature enables you to monitor sites. . IIS logs the information. Finally. server worker processes. You can define failure conditions for applications and configure which trace events to log for each URL. At the application level. You can configure per-server logging options when you want logging settings to apply to all sites on your server by default. As soon as you enable server logging. This means that you do not necessarily have to reproduce the problem before you start troubleshooting. You can also then view the log file to see which requests are failing and which requests are succeeding. You can enable or disable logging at the server level or the site level. you specify the failure conditions for capturing the trace events and also configure which trace events should be captured in the log file entries. you can configure logging options at the site level if you want to set logging settings for a site that differ from those that you have set at the server level. you can enable logging for any site on the server.

see http://go.com/fwlink/?LinkID=200915&clcid=0x409. .microsoft.Designing a Maintenance and Monitoring Plan 13-41 Additional Reading For more information about how to monitor activity on a Web server that is running IIS 7.

You can also use views that show state. By using System Center Operations Manager.13-42 Designing a Microsoft® SharePoint® 2010 Infrastructure Systems Management Key Points You can use System Center Operations Manager to alert you to issues with certain preconfigured availability. This enables operations and IT . you can gain rapid insight into the state of the IT environment and the IT services that are running across different systems and workloads. you can improve your availability and performance metrics through enhanced service-level monitoring. performance. and performance information. helping organizations to increase efficiency and maintain greater control of the IT environment. or security situations. System Center Operations Manager provides endto-end service management that is easy to customize and extend for improved service levels across your IT environment. health. By using System Center Operations Manager. End-to-End Service Management System Center Operations Manager works seamlessly with Microsoft software and applications. You will have improved access to the key functionality that you require to maintain and enhance the service that you deliver to the organization. configuration.

client. Notifications can be either: • Components that are displayed in red to indicate an unhealthy status in the System Center Operations Manager diagram view. End-to-end service management is not restricted to Microsoft-based environments. . and partner solutions enables you to include systems and hardware from vendors other than Microsoft in your service monitoring. The management pack informs operators when incidents occur that may endanger the health of the SharePoint farm. and application teams. redundant tasks and provides intelligent reporting and monitoring to help you to increase efficiency and maintain greater control of your IT environment. ranging from the Windows operating system to applications such as Office SharePoint and IIS. and deploy in complex environments. Simple Network Management Protocol (SNMP). providing you with knowledge and capabilities to drive greater efficiency. performance counters. Microsoft currently has more than 50 management packs for various Microsoft products. and new infrastructure elements make it easier to monitor.Designing a Maintenance and Monitoring Plan 13-43 management teams to identify and resolve issues that affect the health of distributed IT services. Best for Windows System Center Operations Manager 2007 includes expertise from the Microsoft server. Active Directory integration. Increased Efficiency and Control System Center Operations Manager 2007 automates routine. Role-based security. and SharePoint Health Analyzer rules that are found in SharePoint 2010 products. configure. Improvements in management packs for Microsoft products have increased knowledge and reports based on the best practices of Microsoft IT and Product Support Services. System Center Management Pack The System Center management pack for SharePoint 2010 products includes monitoring for: • • • SharePoint Server 2010 Microsoft Project Server 2010 Microsoft Search Server 2010 The management pack monitors important events. Support for WS-Management. Support for high-availability features such as clustering and failover ensure that the IT environment is always monitored. services.

see http://go.microsoft. .com/fwlink/?LinkID=202091&clcid=0x409. For more information about the System Center Operations Manager knowledge articles (SharePoint Server 2010). Additional Reading For more information about System Center Operations Manager.13-44 Designing a Microsoft® SharePoint® 2010 Infrastructure • Alerts that are sent directly to the operator (this notification happens only for critical incidents). see http://go.microsoft.com/fwlink/?LinkID=200916&clcid=0x409.

Designing a Maintenance and Monitoring Plan 13-45 Discussion: Planning for Associated Technologies Key Points Question: You must incorporate associated technologies into your maintenance and monitoring plan for SharePoint 2010. What categories would you use to organize these technologies? Question: What is the next step in developing a maintenance and monitoring plan? Question: Give examples of tasks and activities for each category that you have defined. .

Resolve the error. 4. You want to provide verified procedures for the team. . The main tasks for this exercise are as follows: 1.13-46 Designing a Microsoft® SharePoint® 2010 Infrastructure Lab: Designing a Maintenance and Monitoring Plan Exercise 1: Resolving an Error in SharePoint 2010 Scenario You have identified two common maintenance tasks that the support team will perform. 2. Document the steps for resolving an error in SharePoint 2010. Read the supporting information. The first task is resolving an error that users have encountered in the Business Intelligence Center (BI Center) when they attempt to open a spreadsheet in Microsoft Excel 2010 in the browser. 3. Identify an error in SharePoint 2010.

Task 4: Resolve the error 1. In the ULS Viewer. Task 2: Document the steps for resolving an error in SharePoint 2010 • Define your steps for resolving an error in SharePoint 2010 by using a correlation ID. Switch back to SharePoint 2010 Central Administration. 6. In SharePoint 2010 Central Administration. In SharePoint 2010 Central Administration. Log on to 10231A-NYC-DC1-13 as CONTOSO\Ed with the password Pa$$w0rd. Read the lab scenario. 2. open the ULS Viewer. Error Resolution Operational Procedures. 2. browse to the User Profile Service application. Record the steps in the E:\Labfiles\Lab13\Starter \Contoso Ltd. 2. In the ULS Viewer. start the User Profile Service. 3. On the desktop. open the ULS log file. . and then attempt to open it. 4. filter the ULS log file to display only the entries for that correlation ID. Task 3: Identify an error in SharePoint 2010 1. run iisreset. and then copy the first eight characters of the correlation ID. verify that the User Profile Service has started.Designing a Maintenance and Monitoring Plan 13-47 Task 1: Read the supporting information 1. From an administrator command prompt. Read the message to determine the problem. 3. In SharePoint 2010 Central Administration. Identify the correct error message. 5.docx file.

contoso. In SharePoint 2010 Central Administration. Document the steps for splitting a content database. Run the SharePoint 2010 Management Shell as an administrator. 5. Content Database Operational Procedures. In SharePoint 2010 Central Administration. Record the steps in the E:\Labfiles\Lab13\Starter \Contoso Ltd. . Task 1: Document the steps for splitting a content database • Document your steps for splitting a content database with multiple site collections into multiple content databases.docx file. From an administrator command prompt. The main tasks for this exercise are as follows: 1. Use the command in the following code example to move the database. Split the content database. view the content databases for /sites/hrdocs and verify that the Database Name is now Content_Docs2. run iisreset. Content_Docs1 1.13-48 Designing a Microsoft® SharePoint® 2010 Infrastructure Exercise 2: Splitting a Content Database Scenario The second error for which you want to provide a verified procedure is resolving an issue with a content database. view the content databases for /sites/hrdocs and verify that the Database Name is Content_Docs1. Move–SPSite –Identity http://intranet. This database has exceeded your predefined threshold and must be split by moving the HRDocs site collection to a new content database. 2. 3. Content_Docs2. Task 2: Split the content database.com/sites/hrdocs DestinationDatabase content_docs2 4. Content_Docs1. 2.

Designing a Maintenance and Monitoring Plan 13-49 Module Review and Takeaways Review Questions 1. What are the key elements of SharePoint 2010 that you must monitor? What tools are available to help you to monitor and maintain your SharePoint 2010 infrastructure? Will the SharePoint 2010 administrators perform all necessary maintenance and monitoring tasks? . 3. 2.

Identify tasks that are important to the overall health and security of the system. .13-50 Designing a Microsoft® SharePoint® 2010 Infrastructure Best Practices Related to Maintenance and Monitoring for SharePoint 2010 Supplement or modify the following best practices for your own work situations: • • • Maintain the network environment’s systems to avoid any inefficiency. Thoroughly test and evaluate service packs and updates in a staging environment before you install them on production servers and client machines.

Planning Business Continuity 14-1 Module 14 Planning Business Continuity Contents: Lesson 1: Overview of Business Continuity Management Lesson 2: Developing a Business Continuity Plan for SharePoint Server 2010 Lesson 3: Creating a Backup and Restore Plan for SharePoint Server 2010 Lab: Planning Business Continuity 14-34 14-47 14-15 14-4 .

and explains how to plan for backup and restore in your SharePoint Server 2010 environment. . but also events that affect your local geographical region. processes.14-2 Designing a Microsoft® SharePoint® 2010 Infrastructure Module Overview Business continuity management consists of the business decisions. such as loss of power to your building. and tools that you implement to handle any catastrophic events that might occur. These include events that might affect only your organization. This module introduces the concept of business continuity. such as an earthquake or flood. It also describes how to develop a plan for business continuity in Microsoft® SharePoint® Server 2010.

Describe how to create a backup and restore plan for SharePoint Server 2010. . you will be able to: • • • Describe business continuity management.Planning Business Continuity 14-3 Objectives After completing this module. Describe how to develop a business continuity plan for SharePoint Server 2010.

This lesson provides an overview of business continuity management in the context of an implementation of SharePoint Server 2010. Objectives After completing this lesson. you will be able to: • • Describe the concept of business continuity in SharePoint Server 2010. you must consider business continuity management in your implementation of SharePoint Server 2010. . Explain the difference between availability and disaster recovery.14-4 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 1 Overview of Business Continuity Management To keep your SharePoint Server 2010 infrastructure running smoothly and to keep your services fully operational and available to your users.

recovery point objectives (RPOs). recovery time objectives (RTOs). Explain the concepts of service-level agreements (SLAs). . and recovery level objectives (RLOs).Planning Business Continuity 14-5 • • Describe the business continuity management features that are available for SharePoint Server 2010.

14-6 Designing a Microsoft® SharePoint® 2010 Infrastructure What Is Business Continuity? Key Points The term business continuity refers to the actions that an organization performs to guarantee that vital business functions and services are available to everyone who needs access to them. and support operations. change management. Ensures a certain fixed level of operational continuity in the event that one or more components fail. by providing some form of redundancy for your services. Ensures a certain fixed level of operational continuity in the event that all systems fail. . including customers and suppliers. The various daily tasks that an organization might perform include data and operating system backups. Business continuity management is a combination of high availability and disaster recovery: • • High availability. Disaster recovery.

your overall plan should be much more wide-ranging and should include the following elements: • • • • • Clearly documented procedures. Offsite recovery mechanisms. Ongoing staff training.Planning Business Continuity 14-7 Although the key elements of business continuity are high availability and disaster recovery. The business continuity features in SharePoint Server 2010 should definitely be a part of your business continuity management plan. . Clearly designated roles that should responsible in the event of a disaster. including practices and drills. Any business continuity plan that you create is the manifestation of the procedures that you expect all of the users in your organization to follow on a daily basis to guarantee continuing standard operations. Business continuity planning is the process by which you determine how to provide business continuity. Offsite storage of key business records. backup and restore processes are often considered to be subsets of disaster recovery. However.

you should implement timely and effective action to rectify them. and when they do occur. which is the percentage of time that a given system is active and working. This means that incidents that affect your services should rarely occur. the term downtime is typically applied. . A system with an uptime of 99. This percentage is expressed as a number of nines.14-8 Designing a Microsoft® SharePoint® 2010 Infrastructure Comparing Availability and Disaster Recovery Key Points There can be some confusion and some gray areas when discussing the terms availability and disaster recovery. An available system should also be a resilient system. Availability Availability is the degree to which users of a SharePoint Server 2010 environment consider it to be available and fully operational during a given time period. If a system is unavailable. One of the most common gauges of availability is the percentage of uptime.999 percent is referred to as having five nines of availability.

A second data center that can provide availability within minutes or hours. You must synchronize the disaster recovery strategy that you use for SharePoint Server 2010 with the disaster recovery strategy for the remainder of your infrastructure. or cold standby. Cold standby. You must work alongside the administrators of the infrastructure that it is based on to design a successful disaster recovery plan. which are defined as follows: • • • Hot standby. A second data center that can provide availability within seconds or minutes. The time and effort that is required to get another farm up and running in a different location is often referred to as a hot. Warm standby.Planning Business Continuity 14-9 Disaster Recovery Disaster recovery is the ability to recover from a situation in which a computer running SharePoint Server 2010 becomes unavailable. warm. . A second data center that can provide availability within hours or days.

list items. to recover items that users have deleted from the first-stage Recycle Bin. users can keep multiple versions of the same document in a document library. • . If you enable the first-stage Recycle Bin. Users who have the appropriate permissions can use the first-stage Recycle Bin to recover documents. SharePoint Server 2010 includes a two-stage Recycle Bin. which is also called the Site Collection Recycle Bin. Site collection administrators can use the second-stage Recycle Bin.14-10 Designing a Microsoft® SharePoint® 2010 Infrastructure Overview of Business Continuity Management Features in SharePoint Server 2010 Key Points SharePoint Server 2010 includes several capabilities and features that you can use to manage business continuity. users can recover their data themselves. Using versioning. and document libraries that they or someone else has deleted from a site. Users can lose data by overwriting a document. User-Controlled Business Continuity Capabilities SharePoint Server 2010 includes the following user-controlled capabilities that support business continuity management: • Recycle Bin. Versioning. lists.

Administrator-Controlled Business Continuity Capabilities SharePoint Server 2010 includes the following administrator-controlled capabilities that support business continuity management: • Availability. users can recover their data themselves. No single feature or capability provides availability in a SharePoint Server 2010 environment. • Records Center.Planning Business Continuity 14-11 In the event of an unwanted change. including: • • • Offsite storage of backups. . which are discussed later in this course.microsoft. and site collections. but serving data only through one. Web applications. Disaster recovery. or business reasons. Additional Reading For more information about how to protect content by using Recycle Bins and versioning. the user can easily restore the previous version. You can use Windows PowerShell™ cmdlets or the SharePoint Central Administration Web site to back up and recover SharePoint Server 2010 farms. No single feature or capability provides disaster recovery in a SharePoint Server 2010 environment. When you enable versioning. You can choose from many approaches to improve availability. both within and outside your region. Mirroring of databases.com/fwlink/?LinkID=200917&clcid=0x409. Shipping images of servers to offsite locations. including: • • • • Fault tolerance of components and the network. Running multiple data centers. such as an overwritten document or document corruption. see http://go. Records Center sites support managing records storage for legal. Redundancy of server roles and servers in a farm.microsoft. see http://go. • Backup and restore.com/fwlink/?LinkID=201269&clcid=0x409. regulatory. databases. There are also many other tools that you can use to back up and recover data. You can choose among many approaches to improve availability when a data center goes offline. For more information about records management planning. keeping the others available on standby.

and days. RPOs. It is typically used to refer to the expected performance or delivery time of that service. minutes. An SLA is a formal or informal contract between two parties that defines an agreed level of service. and represent the minimum regularity with which you must create backups. and recovery level objectives. These terms can be defined as follows: • SLAs. Therefore. These define the amount of data loss that has been deemed acceptable over a given time period. RTOs. The two parties concerned might be a supplier and a customer or they might be different departments within the same organization. • . hours. they also define a point in time that your organization has determined that you must be able to recover data to in the event of a disaster. RPOs are set in seconds. recovery point objectives. you must think in terms of service-level agreements. RPOs. and RLOs Key Points When you are creating your business continuity plan for SharePoint Server 2010. recovery time objectives.14-12 Designing a Microsoft® SharePoint® 2010 Infrastructure Overview of SLAs.

and fix the problem. This value corresponds to the measurable uptime of an SLA expressed as percentages such as 99. minutes.999 percent. • Recycle Bins: • • • • Whether the two-stage Recycle Bin feature is offered. Business Continuity Management SLAs for SharePoint Server 2010 Business continuity management is a key area where your IT team may offer SLAs to set expectations within your customer groups. and are set in terms of seconds. site. This time measurement also includes the time that it takes the support team to analyze. RLOs. they also define the maximum acceptable downtime of the service. These define the amount of time that it takes to make a service available again after a disaster has occurred. The amount of space that is allocated for the first-stage Recycle Bin and second-stage Recycle Bin. The following list describes some common features of business continuity management SLAs in SharePoint Server 2010: • Availability: • The service availability as a percentage of uptime. and days. These define the granularity with which you must be able to recover data. Therefore. this might be whether you must be able to recover the entire farm. just a Web application. The length of time for which items are held before they are permanently deleted in each Recycle Bin. Any additional charges for recovering items that have been permanently deleted from the second-stage Recycle Bin. • Versioning: • Whether the versioning feature is offered. In the case of SharePoint Server 2010. . RTOs are usually calculated and based on lost revenue or productivity periods. site collection. You use them in conjunction to make the foundation on which you should develop your business continuity plan. list. or even a single list item.99 percent or 99. hours. This is usually expressed as a number of nines that classify the percentage of time that a given service is active and working. • RPOs and RTOs form two of the most explicit and significant elements of an SLA. library.Planning Business Continuity 14-13 • RTOs. test.

Disaster recovery: The RPOs and RTOs. • Backup and recovery: • • • The objects and services that you can back up and recover. a local emergency versus a regional emergency.14-14 Designing a Microsoft® SharePoint® 2010 Infrastructure • • • The amount of space allocated for versioning. Different RTOs are often set for different circumstances. . and RLO for each object or service. for example. The RPO. The available backup window for each object or service. RTO.

. Describe the strategies for database availability in SharePoint Server 2010. Objectives After completing this lesson. technologies.Planning Business Continuity 14-15 Lesson 2 Developing a Business Continuity Plan for SharePoint Server 2010 There are several strategies. and aspects to consider when you develop a plan for business continuity in SharePoint Server 2010. you will be able to: • • • Plan for availability in SharePoint Server 2010. This lesson describes the key processes and strategies that are available to provide high availability and disaster recovery for your SharePoint Server 2010 environment. Describe the difference between failover clustering and high-availability mirroring.

14-16 Designing a Microsoft® SharePoint® 2010 Infrastructure • • • • Plan user-controlled business continuity features. Plan for disaster recovery in SharePoint Server 2010. Use log shipping for disaster recovery in SharePoint Server 2010. Identify considerations for high-level business continuity planning. .

you must be aware that the greater the degree of availability and the more systems that you decide to protect. Be mindful also that not all of the scenarios in your organization are necessarily going to require equal levels of availability. which can increase the complexity of interactions among software applications and settings. When you plan your investment in an availability solution.Planning Business Continuity 14-17 Planning for Availability in SharePoint Server 2010 Key Points You must make several key decisions when you plan your availability strategy for an implementation of SharePoint Server 2010. different application services. you must consider the following costs: • Additional hardware and software. the more complex and expensive your availability solution is liable to be. Evaluating Costs As you plan your availability requirements. or different farms. You might decide to provide different degrees of availability for different sites. .

but the most typical approaches are to: • Improve the fault tolerance of your server hardware components. you may decide to add more servers to increase overall availability. After you have met your base capacity requirements. or farm becomes unavailable. or farm becomes unavailable. service. You should evaluate the costs of improving availability in conjunction with your business needs. you must ask yourself the following questions: • • If the site. or farm. including redundant array of independent disks (RAID) arrays. service. you must: • Be aware that complete redundancy of every component in a server may be impossible or impractical. • • • Increase the redundancy of server roles within your farm. will employees be unable to perform their expected job responsibilities? If the site. service. Fault tolerance of hardware components is the redundancy of hardware components and infrastructure systems such as power supplies at the server level. you should invest in an availability solution. Obtain fault-tolerant hardware from your hardware vendors that is appropriate for the system. Ensure that servers have multiple power supplies connected to different power sources for maximum redundancy. SharePoint Server 2010 supports running server roles on redundant computers within a farm to increase capacity and provide basic availability. Use additional servers for additional redundancy. When you are planning for fault tolerance of hardware components. Choosing an Availability Strategy and Level There are several approaches to increase the availability of your SharePoint Server 2010 environment. . The capacity that you require determines both the number of servers and the size of the servers in a farm. leading to a loss of business and customers? If you answer yes to either of these questions. Do all of your services require the same level of availability? To gauge your organization's tolerance for downtime for a site.14-18 Designing a Microsoft® SharePoint® 2010 Infrastructure • Additional operational complexity. will business and customer transactions stop.

. you can use Microsoft SQL Server® failover clustering or SQL Server high-availability database mirroring.Planning Business Continuity 14-19 Choosing Database Availability Strategies To support the availability of databases in your SharePoint Server 2010 environment.

A failover cluster is a combination of one or more nodes or servers. A failover cluster instance appears as a single computer. failover is automatic and seamless from the perspective of SharePoint Server 2010. SharePoint Server 2010 can run on any combination of active and passive nodes in a cluster that SQL Server supports and that interprets the failover cluster as a whole entity. SQL Server Failover Clustering You can use SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2 failover clustering to provide availability in a SharePoint Server 2010 farm. . you can use SQL Server failover clustering or SQL Server highavailability database mirroring. and two or more shared disks. but has functionality that provides automatic failover from one node to another if the current node becomes unavailable for any reason. Therefore.14-20 Designing a Microsoft® SharePoint® 2010 Infrastructure Introducing Strategies for Database Availability in SharePoint Server 2010 Key Points To support the availability of databases in your SharePoint Server 2010 environment.

• There are two operating modes for configuring database mirroring: • Asynchronous. Synchronous. A mirror server. This does not require a witness server instance. Synchronous mode with a witness server is recommended for high availability. You can optionally configure this by using a witness server. the principal and mirror servers communicate and cooperate as partners in a database mirroring session. Its copy of the database is the current mirror database. This server instance acts as a hot standby or warm standby server. the witness server does not serve the database. depending on the configuration and state of the mirroring session. The witness server enables SQL Server to automatically fail over from the principal server to the mirror server by regularly verifying whether the principal server is running correctly. • A witness server. You implement mirroring on a per-database basis and it works only with databases that use the full recovery model. In standard database mirroring. If you do so. This server instance serves the database to clients.Planning Business Continuity 14-21 SQL Server High-Availability Mirroring Database mirroring is a capability in SQL Server that you can use to gain database redundancy for your SharePoint Server 2010 databases. Database mirroring provides significant availability and presents an alternative or addition to failover clustering or log shipping that is far easier to manage. Unlike the principal server and the mirror server. you need to use high-availability database mirroring. • . High-availability database mirroring differs from standard database mirroring in that it uses the following three server instances: • A principal server. The two partners perform complementary roles in the session: the principal role and the mirror role. If you want to use database mirroring to gain high availability for your SharePoint Server 2010 farm. This role is the same for standard database mirroring and high-availability mirroring. an administrator must stop the database mirroring session manually. which means that there is no automatic failover. The mirror server instigates automatic failover only if the mirror server and the witness server remain connected to each other after both have been disconnected from the principal server. This is also sometimes referred to as high-safety mode with automatic failover. When the database server is not available. you get the benefit of the automatic failover feature. and its copy of the database is the current principal database.

For more information about how to configure SQL Server database mirroring. Additional Reading For more information about SQL Server failover clustering. SharePoint Server automatically attempts to contact the server that is specified as the failover database. see http://go. see http://go. database server location for your database after you have configured a database mirror instance of SQL Server. The witness server that is configured for SQL Server mirroring automatically swaps the roles of the primary and mirror databases. By setting a failover database location. .microsoft. In the event of a time-out event on the server running SQL Server.com/fwlink/?LinkID=200918&clcid=0x409. or mirror. 2.com/fwlink/?LinkID=201259&clcid=0x409. the following occurs: 1.microsoft.14-22 Designing a Microsoft® SharePoint® 2010 Infrastructure You can use SharePoint Central Administration or Windows PowerShell cmdlets to identify the failover. you add a parameter to the connection string that SharePoint Server 2010 uses to connect to the server running SQL Server.

Planning Business Continuity 14-23 Comparing Failover Clustering and High-Availability Mirroring Key Points There are several differences between the database availability strategies that the previous topic introduced. SQL Server high-availability mirroring Mirror takes over immediately upon failure. Yes. Yes. Factor Time to fail over SQL Server failover clustering Cluster member takes over immediately upon failure. The following table compares those strategies by using several key considerations and factors. . Yes. Transactional consistency? Transactional concurrency? Yes.

mirror. Reconfiguring after failover is manual. The database nodes automatically detect failure. Principal. storage is shared between cluster nodes. Protects against failed storage because both the principal and mirror database servers write to local disks. Does not protect against failed storage. . Can use less expensive direct attached storage. The operational burden is larger than for clustering. so failover is automatic. You can use the SQL Server simple recovery model. Cluster members must be on the same subnet. and witness servers must be on the same local area network (LAN) (up to 1 millisecond latency roundtrip).14-24 Designing a Microsoft® SharePoint® 2010 Infrastructure Factor Time to recovery Steps required for failover? SQL Server failover clustering Shorter time to recovery (milliseconds). The database automatically detects failure. failover is seamless and automatic. SQL Server high-availability mirroring Slightly longer time to recovery (milliseconds). Operational burden Set up and maintained at the server level. It also requires additional memory and processor overhead. Requires SQL Server full recovery model. SharePoint Server 2010 is aware of the mirror location. Must be set up and maintained for all databases. but the only available recovery point if the cluster is lost will be the last full backup. Performance overhead High-availability mirroring introduces transactional latency because it is synchronous. Recovery model SQL Server full recovery model recommended. Protection against failed storage? Storage types supported Location requirements Shared storage (more expensive). Some decrease in performance may occur while a failover is occurring.

Recycle Bins and versioning are key components of a business continuity strategy. You must use versioning to enable this functionality.Planning Business Continuity 14-25 Planning User-Controlled Business Continuity Features Key Points SharePoint Server 2010 includes several user-controlled capabilities and features that you can use for business continuity. SharePoint Server 2010 supports two stages of recycle bins: the first-stage Recycle Bin and the secondstage Recycle Bin. Protecting Content by Using Recycle Bins You can use Recycle Bins to retrieve deleted SharePoint Server 2010 objects such as files. You enable and configure the Recycle Bins at the Web application level. Note: You cannot use Recycle Bins to recover previous versions or accidental overwrites of documents. . documents. lists. and document libraries. list items. You must carefully plan how you might use them in your environment. You should plan to use the Recycle Bin and versioning features of SharePoint Server 2010 in your environment to help users protect and recover their data.

this time period is 30 days. the item goes to the secondstage Recycle Bin. The time limit for the Recycle Bin applies to the total time after the item was first deleted. or Full Control permissions on a site. First-Stage Recycle Bin The first-stage Recycle Bin is located at the site level and is available to users who have Contribute. The first-stage Recycle Bin process works as follows: • When a user deletes an item from a Web site. not the time spent in the Recycle Bin. and is organized into two views: . the item goes to the site's firststage Recycle Bin: • • Items in the first-stage Recycle Bin count toward the site quota. Items remain in the site’s first-stage Recycle Bin until a specified time period elapses. • When a user deletes an item from the Recycle Bin. By default. Action User deletes item Item state Item is held in the first-stage Recycle Bin until the item is deleted from the Recycle Bin or the item has been in the Recycle Bin for longer than the time limit configured for an item to be held in the Recycle Bin Item is held in the second-stage Recycle Bin Item restored by User or site collection administrator User deletes item from the Recycle Bin Site collection administrator Caution: Turning off the Recycle Bin for a Web application empties all Recycle Bins and permanently deletes all items in them. Design.14-26 Designing a Microsoft® SharePoint® 2010 Infrastructure The following table describes how an item is deleted and recovered from the firststage Recycle Bin and the second-stage Recycle Bin. Second-Stage (Site Collection) Recycle Bin The second-stage Recycle Bin is located at the site collection administrator level.

com/fwlink/?LinkId=90917&clcid=0x409.microsoft. the user can easily restore the previous version. this is 30 days) or until the second-stage Recycle Bin reaches its size limit (set as a percentage of the size quota). it goes to the second-stage Recycle Bin. your sites can exceed your storage capacity. For more information about how to manage site collection storage limits. the library or list keeps multiple copies of a document. For more information about how to configure Recycle Bin settings.Planning Business Continuity 14-27 • • Objects in the first-stage Recycle Bins of all sites in the site collection.microsoft.microsoft. If you do not limit the size of sites. or file. item. or document corruption. When a site owner turns on versioning in a document library or a list. see http://go. the sites can become quite large. an overwritten file. Additional Reading For more information about how to use the Recycle Bin in SharePoint Server 2010. Items remain in the second-stage Recycle Bin until either a specified time period elapses (by default. The second-stage Recycle Bin process works as follows: • When a user deletes an item from the first-stage Recycle Bin. • • When an item goes to the second-stage Recycle Bin. Objects in the second-stage Recycle Bin. You must closely manage your versioning implementation. In the event of an unwanted change. see http://go.com/fwlink/?LinkID=202092&clcid=0x409. You can enable versioning at the library or list level. and you can version both items and files. If sites have too many versions of files and documents. at which time the oldest items are deleted.com/fwlink/?LinkID=201260&clcid=0x409. see http://go. only a site collection administrator can recover it. Farm administrators can manage this issue by establishing SLAs with site owners and by setting size quotas on sites. Protecting Content by Using Versioning You can use versioning to help prevent data loss that is caused by someone overwriting a document. .

such as custom scripts for failover and recovery. When you plan your investment in a disaster recovery solution.14-28 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Disaster Recovery in SharePoint Server 2010 Key Points You must make several key decisions when you plan your disaster recovery strategy for an implementation of SharePoint Server 2010. Additional operational complexity. Evaluating Costs As you plan your disaster recovery requirements. the more complex and expensive your disaster recovery solution is liable to be. you must be aware that disaster recovery can be one of the more expensive requirements for a system. which often increase the complexity of operations between software applications. • . you must consider the following costs: • Additional hardware and software. The shorter the interval between failure and availability and the more systems that you decide to protect.

hardware. Tip: When you implement failover between server farms. the systems must match in at least the following areas: • • • Operating system versions and updates. For example. Whatever your scenario. your failover environment must be able to cope with the extra traffic that you would expect during a failover operation. and then implement and test the disaster recovery strategy. content that has a high impact on your business or an Internet publishing farm might need a greater degree of recoverability than other content. SharePoint Server 2010 product versions and updates. Choose a switching mechanism such as Domain Name System (DNS) or hardware load balancing that meets the needs of your organization and environment. Do all of your services require the same level of recoverability after a disaster? You should offer different degrees of disaster recovery for different content. or farms. so you should also: • • Ensure that infrastructure dependencies such as power. . directory. network. services. SQL Server versions and updates. Although we are principally discussing the availability of SharePoint Server 2010. it is recommended that you first deploy and tune the core solution within a farm. other components can affect the system uptime. You should keep in mind that the failover system may only serve a subset of users. At a minimum. your failover components and systems would match the primary components and systems in all areas: platform. Identifying System Requirements for Disaster Recovery In an ideal scenario. and Simple Mail Transfer Protocol (SMTP) are fully redundant.Planning Business Continuity 14-29 You should evaluate the costs of maintaining hot or warm standby data centers in conjunction with your business needs. cooling. sites. and number of servers.

or hot standby disaster recovery strategies. Strategy Cold standby Example scenario A business ships backups to support computer system recovery to local and regional offsite storage on a regular basis. warm. . A business ships virtual server images to local and regional disaster recovery farms.14-30 Designing a Microsoft® SharePoint® 2010 Infrastructure Choosing a Disaster Recovery Strategy You can choose from several approaches to provide disaster recovery for your SharePoint Server 2010 environment. Hot standby A business runs multiple data centers. operationally. Often relatively fast to recover. Can be very expensive and time-consuming to maintain. The following table lists example scenarios that show reasons for choosing cold. depending on your business needs. The business has contracts in place for emergency server rentals in another region. Often an expensive option to recover. Pros Often the cheapest option to maintain. Can be quite expensive to configure and maintain. Warm standby Often relatively inexpensive to recover because a virtual server farm can require little configuration upon recovery. Cons Usually the slowest option to recover. because it requires you to configure physical servers correctly after a disaster has occurred. but serves content and services through only one data center.

You can use SQL Server log shipping to create a disaster recovery farm in a geographically distributed data center for SharePoint Server 2010. you can provide a disaster recovery site that provides services when a failover occurs. Overview of SQL Server Log Shipping Log shipping enables you to configure SQL Server to continually send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. This server records the . Using this configuration. Log shipping can also include an optional third server instance.Planning Business Continuity 14-31 Using Log Shipping for Disaster Recovery in SharePoint Server 2010 Key Points The most common solution for providing disaster recovery for SharePoint Server 2010 is to use SQL Server log shipping. Continually backing up the transaction logs from a primary database and then copying and restoring them to a secondary database keeps the secondary database almost synchronized with the primary database. You then apply the transaction log backups to each secondary database individually. which is known as the monitor server.

3. including My Sites databases. You cannot use log shipping to send the configuration database to another farm because it contains computer-specific information. In the event of an unplanned failover. some data loss is possible. The minimum time that you can configure for synchronization is one minute. 2.14-32 Designing a Microsoft® SharePoint® 2010 Infrastructure history and status of backup and restore operations and raises alerts if these operations do not occur as scheduled. Back up the transaction log on the primary server instance. Considerations for Using Log Shipping for SharePoint Server 2010 You must consider several things when you plan to use log shipping for SharePoint Server 2010 disaster recovery: • • • • By default. Copy the transaction log file to the secondary server instance. depending on the frequency of log shipping and the time of failure. The image on the slide for this topic illustrates the log shipping process. from one SharePoint Server 2010 farm to one or more geographically dispersed secondary farms. You must maintain the same customizations and configuration settings on both farms manually. Restore the transaction log backup on the secondary server instance. you must run a SQL Server script to make all of the content databases writeable. Log shipping consists of three operations: 1. SharePoint Server 2010 and Log Shipping You can use SQL Server log shipping to send content databases. When failover happens. Site collections that are added to the primary farm are not automatically added to the configuration database on the secondary farm. • • . You can create scripts to automate failover. You must add them by using either Stsadm operations or a script. the failover process for log shipping is manual.

Question: What effects does implementing versioning have on your design? Question: What areas of your design are impacted by requirements for business continuity? .Planning Business Continuity 14-33 Discussion: High-Level Business Continuity Planning Key Points Answer the following questions in the context of the sample business continuity plan.

you will be able to: • • • Determine what to protect in your SharePoint Server 2010 environment.14-34 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 3 Creating a Backup and Restore Plan for SharePoint Server 2010 There are several strategies. tools. . This lesson describes the key tools and strategies for backing up and restoring your SharePoint Server 2010 environment. Plan the backup and restore of SharePoint Server 2010. Objectives After completing this lesson. and scenarios to consider when you create a successful backup and restore plan for SharePoint Server 2010. Identify backup and restore strategies for SharePoint Server 2010.

. Describe how to script backup and restore operations for SharePoint Server 2010.Planning Business Continuity 14-35 • • Identify virtual recovery scenarios for SharePoint Server 2010.

You can back up these items by using SharePoint Server 2010. Backing up and recovering the Search service application is a special case because of the complexity of interactions between the components of the application. . • Search and other service applications. When you use System Center Data Protection Manager 2010. You can back up these items by using either SharePoint Server 2010 or Microsoft System Center Data Protection Manager 2010. You cannot back up and restore these items as objects.14-36 Designing a Microsoft® SharePoint® 2010 Infrastructure Determining What to Protect in Your Environment Key Points Your business requirements will help you to determine which components of your SharePoint Server 2010 environment you must protect and the granularity with which you must be able to recover them: • Farm and Web applications. you can only recover these items by using a combination of a computer system backup and SharePoint Server backup. When you start a backup of the Search service application.

System Center Data Protection Manager 2010. You can back up these items by using SharePoint Server 2010. you can restore the databases for a service application and then reprovision the service application. You can back up these items by using SharePoint Server 2010. and also backs up the index partition files in parallel. document libraries. however. You can back up these items by using SharePoint Server 2010. You can use farm-level and database-level backup and restore for site collection recovery if a single site collection is stored in a database. • • SharePoint configuration settings. System Center Data Protection Manager 2010. • Content databases. or SQL Server: • You can use farm-level and database-level backups with unattached database recovery for SharePoint Server to restore site collections. or SQL Server. You can recover configuration settings from farm-level backups. lists. System Center Data Protection Manager 2010. and configurations. site collections. You can back up these items by using System Center Data Protection Manager 2010. and property databases. and document lists. You can recover the Central Administration content database and the configuration database for a farm in SharePoint Server 2010. • Web. You can back up these items by using SharePoint Server 2010. Content that is stored in remote binary large objects (BLOBs). Service applications in a SharePoint Server 2010 environment can consist of both service settings and one or more databases. System Center Data Protection Manager 2010.Planning Business Continuity 14-37 SharePoint Server 2010 starts a SQL Server backup of the Search administration database. • • List items and documents. as long as the remote BLOB storage (RBS) provider that you are using has this capability. You cannot restore a complete service application by restoring the database only. sites. crawl databases. but only as part of a full-farm recovery to the same farm with the same servers. . sites. or SQL Server. You can back up and restore these items with other content.config changes that were made by Central Admin or an application programming interface (API). or SQL Server: • • • You can use farm-level and database-level backups with unattached database recovery for SharePoint Server to restore configuration settings.

you can back up changes to Web. You can back up these items by using System Center Data Protection Manager 2010 or file system backup.14-38 Designing a Microsoft® SharePoint® 2010 Infrastructure When you use System Center Data Protection Manager 2010.config by using the file system backup option. • Web. see http://go.com/fwlink/?LinkID=200920&clcid=0x409. . you can back up changes to Web.config by using the file system backup option.microsoft. Additional Reading For more information about how to restore a service application.config changes that were not made by Central Admin or an API. When you use System Center Data Protection Manager 2010.

You determine this by calculating the amount of data that your organization can afford to lose in the event of a failure. Defining Business Requirements To define your business requirements. These decisions include determining which backup and recovery strategies to use and deciding which tools to use. You determine this by calculating the amount of time your organization can afford for the site or service to be unavailable. RLO. Define the maximum time that a data recovery process can take.Planning Business Continuity 14-39 Planning Backup and Restore for SharePoint Server 2010 Key Points You must make several key decisions when you plan for backup and restore in a SharePoint Server 2010 environment. you need to determine the: • RPO. Define the granularity with which you must be able to recover data. for each farm and service in your environment. You must determine whether you only need to be able to recover the farm as a • • . RTO. Define the maximum amount of time between the last available backup and any potential failure point.

Changes to the Web. you must determine whether you can meet the business continuity requirements that you have set for your organization within your budgetary constraints for time and resources. site. site collection. Then. or workflow activities and conditions. custom fields. or incremental. Determining What Backup and Restore Tools to Use To select the appropriate tools for backup and recovery. page layouts. site or list definitions. Web Parts. differential. Considering Protection for Customizations Customizations to SharePoint sites can include: • • • • • Master pages. or even item level.14-40 Designing a Microsoft® SharePoint® 2010 Infrastructure whole entity. Changes to standard XML files.config file by using Central Administration or the SharePoint APIs and object model.xml). it is best practice to deploy customizations by using solution packages. custom actions. . These objects are stored in the content database for a Web application. coded workflows. consider the following key issues: • • • • • Backup speed. you can make changes to the Web. When you are choosing tools. Supported backup types such as full. How you deploy customizations and how you make changes to the Web. Complexity of managing the backup tool. custom columns. To provide the greatest opportunity for recovery. Recovery granularity for objects. Custom site definitions (Webtemp. and cascading style sheets.config file.config file have a significant effect on which tools you can use to back up and recover customizations. or whether you need to perform more granular restores down to Web application. list. new content types. library. Completeness of recovery.

you must determine and document the backup and recovery strategies for your SharePoint Server 2010 environment.Planning Business Continuity 14-41 Data Backup and Restore Strategies Key Points Based on your business requirements. you can employ the strategies in the following table. you may also determine that you need to use more than one tool to protect your SharePoint Server 2010 environment. Example Strategies If your environment includes databases that database administrators manage. the determination of your recovery needs. As you determine the strategies that you must use. . and the determination of which backup tools to use.

Effect on performance that the backup has on the database. . Use SharePoint Server 2010 backups to protect services The backup interval that you set for each database is based on the: • • • Business impact of the service. You should test the effect that snapshots have on the performance of your system before you implement them. Standard rate of change for the database. However. Use SQL Server database snapshots stored on a separate physical disk to protect small. Standard rate of change for the database. Effect on performance that the snapshot has on the environment. Effect on performance that the backup has on the environment. rapidly changing content databases that have a high impact on the business The snapshot interval that you set for each database is based on the: • • • • Business impact of the content or service. the process of creating snapshots can decrease the performance of the underlying database.14-42 Designing a Microsoft® SharePoint® 2010 Infrastructure Example strategy Use SQL Server to back up all databases Strategy basis The backup interval that you set for each database is based on the: • • • Business impact of the content or service. and you should regularly discard your snapshots to reduce storage space requirements. Amount of space that is required to store the snapshot. along with its underlying database. Standard rate of change for the database. Perform all restore The choice of which restore system you use is operations by using determined by the type of backup that is available SharePoint Server 2010 and the objects being restored. Recovering from a snapshot is faster than standard recovery because SharePoint Server can treat a snapshot. as an unattached database.

When you use System Center Data Protection Manager 2010. At the offsite location. Virtualized Recovery Farms for System Center Data Protection Manager 2010 You can also use a virtualized recovery farm with System Center Data Protection Manager 2010 to improve its disaster recovery capabilities for SharePoint Server 2010. you must have an environment available in which you can easily configure and connect the images to re-create your farm environment. Warm Standby Data Centers You can create a warm standby solution by making sure that you consistently and frequently create virtual images of the servers in your farm and then transport them to a secondary offsite location. the typical strategy for restoring individual SharePoint Server 2010 items from backups is to .Planning Business Continuity 14-43 Implementing Disaster Recovery by Using Virtualization Key Points You can use a virtualized environment to help simplify your disaster recovery planning for SharePoint Server 2010.

you can either maintain it in a paused state or turn it off. The standard method for provisioning this virtualized recovery farm is to install all of the required roles on a single virtual server and ensure that it has sufficient storage capacity to store the largest possible content database in your environment. You can then use this farm solely for the purpose of recovering SharePoint content when you use System Center Data Protection Manager 2010. . If you use a virtualized environment. you can test your disaster recovery scenarios in a realworld environment with real data. When it is not in use.14-44 Designing a Microsoft® SharePoint® 2010 Infrastructure create a recovery farm that you use to restore the content database from which you will extract the required item. but they do not test the actual procedures with production data. Virtualization of SharePoint Farms for Disaster Recovery Testing An often disregarded task in many SharePoint implementations is testing disaster recovery failover of the SharePoint farm. or items. Organizations may have plans in place.

and they include: . several have been designed to cover major backup and restore operations. Windows PowerShell provides both a general command-line interface and a SharePoint-specific add-in tool called the SharePoint 2010 Management Shell. Of these SharePoint-related cmdlets. Web applications. Each object has several specifically related commands. SharePoint Backup and Restore Cmdlets There are over 500 SharePoint-related cmdlets for performing various tasks such as getting. In the context of SharePoint Server 2010 administration. it supersedes the Stsadm.Planning Business Continuity 14-45 Scripting Backup and Restore for SharePoint Server 2010 Key Points Windows PowerShell is the command-line tool and supporting scripting language from Microsoft for Windows® administration. creating. and deleting on various SharePoint objects such as sites. configuring. site collections. and service applications.exe administration tool.

you can use the SharePoint 2010 Management Shell to perform backup and restore operations on all of your servers from a central location.microsoft. see http://go. Additional Reading For more information about how to use Windows PowerShell with SharePoint Server 2010. Windows PowerShell includes a remote interface. you could run the following scripts in the SharePoint 2010 Management Shell to back up and restore your SharePoint Server 2010 farm configuration database. you could run all of your backups from your Windows 7 desktop computer. For example. Backup-SPConfigurationDatabase –Directory c:\backups –DatabaseServer servername –DatabaseName SharePoint_Config Restore-SPFarm –Directory c:\backups –RestoreMethod Overwrite – ConfigurationOnly Performing Remote Backup and Restore of SharePoint In addition.com/fwlink/?LinkID=200922&clcid=0x409. . Therefore.14-46 Designing a Microsoft® SharePoint® 2010 Infrastructure • • • • • • • Backup-SPFarm Restore-SPFarm Backup-SPSite Restore-SPSite Export-SPWeb Import-SPWeb Backup-SPConfigurationDatabase For example.

The information that your team requires is detailed in the supplied documents. . Read the supporting information. your team must create a business continuity plan for the SharePoint farm. Use these documents to produce your business continuity plan. Complete the SharePoint 2010 Backup and Restore Planning worksheet. The main tasks for this exercise are as follows: 1. Ltd and the physical architecture design. 2.Planning Business Continuity 14-47 Lab: Planning Business Continuity Exercise 1: Creating a Backup and Restore Plan Scenario Given the business continuity requirements for Contoso.

Restore a missing service application. Task 1: Verify that a service application is missing 1. In the E:\Labfiles\Lab14\Starter folder. Confirm that you have restored the missing service application and service application proxy. 4. Log on to 10231A-NYC-DC1-14 as CONTOSO\Ed with the password Pa$$w0rd. Verify that a service application is missing. The main tasks for this exercise are as follows: 1. Verify that the User Profile Service Application is not listed. view the list of managed service applications. Task 2: Complete the SharePoint 2010 Backup and Restore Planning worksheet • In the E:\Labfiles\Lab14\Starter folder. read the information in the Contoso Ltd. Read the lab scenario. 2. 3. . 2.14-48 Designing a Microsoft® SharePoint® 2010 Infrastructure Task 1: Read the supporting information 1.xlsx file. Restore a missing service application proxy. complete the worksheet in the SharePoint 2010 Backup and Restore Planning Worksheet. 3. Business Continuity Requirements. 2. In SharePoint 2010 Central Administration.docx file. Exercise 2: Testing the Recovery Process Scenario You are going to verify that a service application is missing and then restore it from a recent backup.

. Options Restore from a backup Service application proxy Restore options Value Full farm backup. restore a missing service application proxy from the most recent farm backup by using the information in the following table. Options Restore from a backup Service application Value Full farm backup. 2.Planning Business Continuity 14-49 Task 2: Restore a missing service application • In SharePoint 2010 Central Administration. Verify that the User Profile Service Application and the User Profile Service Application Proxy now both appear in the list. In SharePoint 2010 Central Administration.dated 6/15/2010 Shared Services\Shared Services Proxies\User Profile Service Same configuration Task 4: Confirm that you have restored the missing service application and service application proxy 1. restore a missing service application from the most recent farm backup by using the information in the following table.dated 6/15/2010 Shared Services\Shared Services Applications\User Profile Service Same configuration Login name: Use the default Password: Pa$$w0rd Restore options Login names and passwords Task 3: Restore a missing service application proxy • In SharePoint 2010 Central Administration. view the list of managed service applications.

What are the user control business continuity features that you may choose to include in your design? What are the key differences between RTOs and RPOs? What are the performance overheads if you decide to plan for high-availability with mirroring. .14-50 Designing a Microsoft® SharePoint® 2010 Infrastructure Module Review and Takeaways Review Questions 1. 3. rather than treating these as the same thing. rather than failover clustering? Best Practices Related to Designing a Security Plan Supplement or modify the following best practices for your own work situations: • Your planning should include options for availability and disaster recovery. 2.

Planning Business Continuity 14-51 • • You must establish RTO. and RLO metrics before you establish a formal business continuity SLA. . RPO. You must establish a budget for business continuity that reflects the resources necessary to achieve business goals.

.

Planning for Upgrading to SharePoint 2010 15-1 Module 15 Planning for Upgrading to SharePoint 2010 Contents: Lesson 1: Identifying Upgrade Scenarios Lesson 2: Planning Your Upgrade Lesson 3: Upgrade Considerations Lab: Planning for Upgrading to SharePoint 2010 15-4 15-23 15-42 15-57 .

because there is much more that can go wrong if you fail to prepare adequately. You must understand the methods and tools that are available with SharePoint 2010 so that you can plan an efficient and successful upgrade. It also requires technical project management and requirements analysis skills. You must plan upgrades with even more attention to detail than is necessary in a new installation. Microsoft® SharePoint® 2010 products offer a greatly enhanced upgrade experience over previous versions. It requires an in-depth understanding of at least two product versions. .15-2 Designing a Microsoft® SharePoint® 2010 Infrastructure Module Overview Planning an upgrade is one of the most complex tasks that solution architects perform.

Describe how to plan an upgrade to SharePoint 2010. . you will be able to: • • • Describe the range of upgrade requirement options and the available upgrade methods. Explain the key upgrade considerations.Planning for Upgrading to SharePoint 2010 15-3 Objectives After completing this module.

Describe the supported methods for upgrading from Microsoft Office SharePoint Server 2007 to SharePoint 2010.15-4 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 1 Identifying Upgrade Scenarios SharePoint 2010 offers a range of business benefits for users and IT staff. so it is likely that you will need to plan an upgrade. but you must understand which is most appropriate for your organization—particularly if you must upgrade from older product versions or migrate from platforms other than SharePoint Products and Technologies. Objectives After completing this lesson. you must also understand the business benefits of performing an upgrade. This will enable you to manage expectations and identify new opportunities. . you will be able to: • • Describe the benefits of upgrading to SharePoint 2010. SharePoint 2010 has well-documented upgrade options. In addition to your technical understanding.

Describe options for migrating from platforms other than SharePoint Products and Technologies to SharePoint 2010.Planning for Upgrading to SharePoint 2010 15-5 • • • Explain the options available for upgrading from older versions of Office SharePoint to SharePoint 2010. . Describe some of the solution-specific upgrade options that should be reflected in an upgrade plan.

SharePoint 2010 offers increased site deployment flexibility and usability through: • • A single platform for intranet. extranet. You should also identify current customizations that can be replaced by out-of-the-box functionality available in SharePoint 2010. instead. Stakeholders and the business community may not be aware of the potential benefits. so you should know what SharePoint 2010 can do for your organization.15-6 Designing a Microsoft® SharePoint® 2010 Infrastructure Benefits of Upgrading to SharePoint 2010 Key Points Solution architects must recognize the benefits of upgrading a current Office SharePoint product implementation to SharePoint 2010. . you should understand how the new functionality that is available meets your business requirements. and Internet sites that is often more cost-effective. The familiar Fluent user interface (UI). This does not mean that you should be selling the new solution. This functionality falls into the following areas: • Sites and collaboration.

• User self-service. Self-service site and My Site deployment. • Content management. SharePoint 2010 has greatly enhanced social computing features that can deliver: • • Personalized environments with My Site Web sites. and drill down into. . wikis. and blogs. you must be able to review the business requirements from corporate strategy to usability and map potential solutions to requirements. The ability to create more effective groups by identifying key team members. The ability to tag and comment on business content. businesses can manage: • • Business documents and records and Web content. information logging. such as SharePoint Designer 2010 and Dashboard Designer 2010. such as Microsoft Excel® 2010. • Community development. business information. SharePoint 2010 enables users to develop business solutions without the need to place additional workloads on IT staff through: • • The availability of composite development tools. These are primarily user benefits and opportunities. The flexibility to develop user dashboards for personal and organizational BI. Using SharePoint 2010. SharePoint 2010 provides greatly enhanced business intelligence (BI) options that provide: • • • The information that information workers need directly to their Web pages. Deployment of governance strategies and requirements through policies and workflows. Enhanced options for customized search solutions. but SharePoint 2010 can also provide platform and IT services advantages with better administrative tools.Planning for Upgrading to SharePoint 2010 15-7 • Search. and deployment security. As a solution architect. • Business insights. Integration with existing BI assets. The integration of Microsoft FAST Search Server 2010 for SharePoint technologies and the extension of People Search provides: • • • Greater speed and flexibility to search for.

. and it is recommended for small topologies. In-Place Upgrade An in-place upgrade installs SharePoint 2010 on an existing Office SharePoint Server 2007 implementation by installing the binaries and using the PSConfig command to configure the installation.15-8 Designing a Microsoft® SharePoint® 2010 Infrastructure Methods for Upgrading from Office SharePoint Server 2007 Key Points There are two supported methods to upgrade from Office SharePoint Server 2007 Service Pack 2 (SP2) or later to SharePoint 2010. as follows: • Advantages. This also means that URLs remain the same without any need for IT interventions. but there are advantages and disadvantages to this approach. although all customizations should be tested after the upgrade completes. There are some prerequisites. which must be available for you to be able to use this option. Farm-wide settings and customizations are preserved and upgraded. such as a 64bit server environment and SP2. This may sound the most obvious route to take. An in-place upgrade can maintain farm settings as long as these are compatible with the new SharePoint 2010 options.

It is therefore essential that you pilot an in-place upgrade. such as additional database capacity to hold two versions of the business data. This is affected by the size of the implementation (such as the number of servers) and the volume of data on the farm. because the original implementation remains available except during the upgrade of individual databases. to ensure that you know whether an in-place upgrade is practical. You must also review the automatic upgrade of Shared Services Provider (SSP) services. This is necessary so that you can estimate the effort and resources that you require to perform the upgrade. consolidating several together to take advantage of revised software boundaries. this entails more effort and available equipment. which may significantly reduce the overall upgrade time. For speed. The in-place upgrade is not granular. The rollback scenario is to restore the original Office SharePoint Server 2007 farm. You should identify all customizations. and it would be of no benefit to install the previous release to perform an in-place upgrade. this may not be an issue. This takes place on separate hardware that is currently in use on the Office SharePoint Server 2007 farm. This is because you will have to install new server versions on the new equipment. You can also reorganize your content databases.Planning for Upgrading to SharePoint 2010 15-9 • Disadvantages. You must have a thorough understanding of farm content. because it works on a server and farm basis. Database Attach Upgrade The second option is to perform a database attach upgrade. because the upgrade will run until completion or failure. with real data. you can plan to attach multiple databases simultaneously. which triggers a schema update on the SharePoint 2010 farm. because you must deploy a new environment while the old one remains in place. which may require manual intervention to ensure successful upgrade. There is also little opportunity for rollback. However. The process involves the installation and configuration of the SharePoint 2010 environment. . The major benefit of this approach is the ability to maintain business productivity. The implementation team then attaches the Office SharePoint Server 2007 content databases to the new farm environment. This has a greater cost in server and database hardware. customizations. if you are migrating from 32-bit servers to 64-bit servers. An in-place upgrade means that there will be server downtime during the upgrade process. and configuration before you attempt an in-place upgrade. The advantages and disadvantages include: • Advantages. Of course.

For implementations where you have large content databases.microsoft. this is definitely the preferred option. An example plan may recommend the following approach: • • • Detach content databases from the Office SharePoint Server 2007 farm. Hybrid Upgrade You can plan to use a combination of the two upgrade options. although it requires additional database resources. but does not automatically update all customizations. which triggers a database attach upgrade. Additional Reading For more information about hybrid upgrade options. The database attach upgrade is generally preferred for business continuity and control. This provides some of the advantage and disadvantages of each upgrade path: • • • You must have a 64-bit environment. This approach provides upgrades for site or SSP content databases.15-10 Designing a Microsoft® SharePoint® 2010 Infrastructure • Disadvantages. Reattach the content databases to the new SharePoint 2010 farm. but you will upgrade customizations.com/fwlink/?LinkID=200923&clcid=0x409. This minimizes rollback issues. You can create a read-only version of the content database and provide user access to this to mitigate loss of productivity. You will have downtime during the in-place upgrade. but you will have granularity of content upgrades. This hybrid approach enables you to take advantage of the simplicity of an in-place upgrade and also gives you greater control over the upgrade process itself. You have limited rollback options. see http://go. which now has no content. This means that you must re-create all customizations manually. Perform an in-place upgrade on the farm. . but you will be able to limit downtime by providing read-only copies of content databases. because you can upgrade databases in a granular manner.

However.0 Office SharePoint Server 2007 You may also find situations where you are asked to plan for “upgrades” from platforms other than SharePoint technologies.0 Microsoft Office SharePoint Portal Server 2003 Windows SharePoint Services 3. you will not always be in this situation.Planning for Upgrading to SharePoint 2010 15-11 Methods for Upgrading from Earlier Versions of SharePoint Key Points The supported scenarios are all based on Office SharePoint Server 2007 SP2 upgrades to SharePoint 2010. This is a migration rather than an upgrade. but it is often the case that these requests arise when you are planning to upgrade a platform. You will find that user departments may have a range of versions available to them. including: • • • • Windows® SharePoint Services 2. .

or ghosted. Gradual Upgrade A gradual upgrade is a granular side-by-side upgrade process that enables you to upgrade a Windows SharePoint Services 2. you must first upgrade the platform to Windows SharePoint Services 3.0 updates. The three options available are: • • • In-place upgrade Gradual upgrade Data migration In-Place Upgrade The in-place upgrade is functionally the same and retains the same issues regarding rollback. Whenever you complete a database update. or staging environments. it is essential that you perform a complete technical and user acceptance test review of the deployment. .0. because you maintain control over the entire upgrade process.15-12 Designing a Microsoft® SharePoint® 2010 Infrastructure You should include a full backup of the farm as part of your upgrade plan. This option was not included in the upgrade options from Office SharePoint Server 2007 to SharePoint 2010. The next step for any plan is an in-place or database attach upgrade. you must have a plan for a full restore in case of a catastrophic upgrade failure. so much of your plan involves getting the farm to a point at which you can perform one of these. You then require a plan that details the upgrade steps that are necessary to successfully upgrade your deployment. As with any upgrade. pages because users have modified pages that are now held in the content database. you should create new content database backups. If you opt for an in-place upgrade. This is because there was a major redesign of the database schema between these versions. Uncustomized. You must also test for capacity and time resource requirements. or unghosted. This may be a particular advantage if you have a large number of customized.0 For Windows SharePoint Services 2. pages are Web Part pages that are based on site definitions and are readily upgraded. When Office SharePoint Server 2007 was launched. Windows SharePoint Services 2. this approach was recommended only for development. irrespective of which version of Office SharePoint you want to upgrade. This is the most common form of upgrade. A gradual upgrade also enables you to support users through the changes. test.0 deployment by one site collection at a time.

Data migration is considered to be the same as an in-place upgrade. because the schema will have changed during the upgrade process. When you add databases to the new installation. You should make a new backup of content databases before you start any upgrade. unless you have a small and discrete farm.0 to Microsoft SharePoint Foundation 2010 or SharePoint 2010. you should first install the latest service pack and cumulative updates on the farm servers. which you can use to scan your farm to identify possible issues. This is because page layouts replace page templates in the new site architecture. you must build a SharePoint 2010 farm with the appropriate Web applications and configuration to match your site requirements. You should resolve any issues that the Pre-Upgrade Checker report identifies before you proceed to an in-place or database attach upgrade to the required version of SharePoint 2010. and you must specify which page layout to use for each page type. The service pack provides the Pre-Upgrade Checker tool. For Office SharePoint Portal Server 2003.0 When you plan to upgrade Windows SharePoint Services 3. you must create upgrade definition files for translating the page templates into new page layouts. With the farm servers at the appropriate software levels. The options are the same as for Windows SharePoint Services 2. Again.Planning for Upgrading to SharePoint 2010 15-13 Data Migration Data migration is the third upgrade strategy that is available when you move from old to new Office SharePoint environments. the upgrade process automatically upgrades them. however. During the pre-upgrade process. . to the site when you have completed the upgrade process. To continue. Windows SharePoint Services 3. Deploy any customizations.0 upgrades. The process of data migration involves the creation of a new SharePoint 2010 farm environment and the movement (or migration) and addition of the existing site databases to the new installation. the changes are made on a copy of the content rather than the content. you can choose to complete an in-place or database attach upgrade. the most common choice is to perform a database attach upgrade. you deploy the new custom site definition and any upgrade definition files to the installation directory so that they are available when you upgrade the site collections. you must first upgrade the farm to Office SharePoint Server 2007 SP2. You can then attach the content database and complete the upgrade. This is very similar in process and goals to the database attach option. Office SharePoint Portal Server 2003 For Office SharePoint Portal Server 2003 updates. such as custom master pages.

. you should first upgrade to the latest service pack and then run the Pre-Upgrade Checker tool.microsoft. This process is then the same as the upgrade path for Windows SharePoint Services 3. Additional Reading For more information about how to plan and prepare for upgrade to Office SharePoint Server 2007 and the tools that are available to support you.com/fwlink/?LinkID=200924&clcid=0x409. see http://go.15-14 Designing a Microsoft® SharePoint® 2010 Infrastructure Office SharePoint Server 2007 If you are upgrading an Office SharePoint Server 2007 or Office SharePoint Server 2007 SP1 farm.0.

Note: The acronym BDC is used in this section to describe the Office SharePoint Server 2007 Business Data Catalog Service. Business Data Catalog Upgrades If you have Office SharePoint Server 2007 applications that run the Business Data Catalog (BDC). You can perform an in-place upgrade. The acronym BCS is used to describe SharePoint 2010 Business Connectivity Services and all associated services. . so there will be a number of changes. or you can choose the database attach option. which involves greater configuration effort. you must make specific plans for upgrade or migration. The service application models are different for BDC and Microsoft Business Connectivity Services (BCS). including the Business Data Connectivity Service.Planning for Upgrading to SharePoint 2010 15-15 Upgrade Considerations Key Points There are a number of solution-specific options that you should review when you plan an upgrade.

you must plan to upgrade BDC individually. you automatically create a BCS instance. which directly replaces the BDC from Office SharePoint Server 2007 and supports the backward compatibility of solutions that are based on BDC. After you complete the upgrade. These customizations may include: • • • • • • • Custom protocol handlers. Customized noise-word files. Custom security trimmers. Search It is important to understand that the Search Service is not upgraded when you use the database attach upgrade option. . The Application Registry Service supports Office SharePoint Server 2007 applications that include: • • • Custom Web Parts Custom code Searching A copy of each application definition in BDC is added to the Application Registry Service. You should also recrawl content databases when you upgrade. If your organization uses Office SharePoint Search. This will have associated service databases for BCS and the Application Registry Service. Custom word-breakers. by first exporting the application definitions from the Office SharePoint Server 2007 BDC.15-16 Designing a Microsoft® SharePoint® 2010 Infrastructure When you perform an in-place upgrade of a farm that uses BDC. you must identify any customizations and prepare to redeploy them. Modifications to managed properties. and an upgraded version is added in BCS. you must plan for appropriate time to completely reindex your environment. Custom thesauruses. Custom iFilters. Depending on your content volumes and the dependence of your business on search. you must update the solution to use BCS and import the updated BDC models into the Business Data Connectivity Service. If you perform a database attach upgrade.

. For more information about how to manage BDC models in SharePoint 2010. In addition. You can use this to specify whether the upgrade should use a newer version of a feature. the features are maintained and used in their current form. various language templates will be made available to enable an environment to support languages other than the language in which the initial installation was performed. Additional Reading For more information about how to export application definitions. You must be fully aware of the language requirements for your environment. you must reconfigure Excel Services in your new farm.com/fwlink/?LinkID=200925&clcid=0x409. During the installation process. Feature Upgrades Office SharePoint Server 2007 included a move toward the use of features in the product.microsoft. SharePoint 2010 includes a feature upgrade capability. There is a version section in the XML of each Feature. you must plan to reinstall any Microsoft InfoPath® forms that are currently used in your environment.Planning for Upgrading to SharePoint 2010 15-17 Excel Services For the database attach upgrade approach. InfoPath Forms If you plan to use a database attach option. Language Packs SharePoint 2010 ships in a number of localized SKUs. installers will be prompted to choose which language they want to use. The decision that they make here will influence the language that Central Administration uses. You should check specifically for forms that use fully qualified URLs and any forms that are packaged with custom assemblies. you should review and test all forms.xml file. If no version is declared in the file. The command stsadm -o exportipfsadminobjects exports administrator-approved form templates and data connection files that are stored in the Office SharePoint Server 2007 or Microsoft Office Forms Server 2007 configuration database. see http://go. particularly in a global deployment. Irrespective of the upgrade approach. see http://go.microsoft.com/fwlink/?LinkId=189010. where you can declare the version number of the feature.

microsoft. see http://go. see http://go.com/fwlink/?LinkID=201264&clcid=0x409.com/fwlink/?LinkID=201263&clcid=0x409.microsoft.15-18 Designing a Microsoft® SharePoint® 2010 Infrastructure For more information about Excel Services administration. . For more information about upgrading forms templates.

because you can assume that most applications reflect business logic that the application itself is able to reproduce. by definition. It is far easier to migrate data than logic. You should review any request for an application migration to check whether it would be easier to re-create the application based on current requirements than to migrate the requirements that must. have been established in the past. Content migration is concerned with the movement of data rather than business logic.Planning for Upgrading to SharePoint 2010 15-19 Considerations for Migration from Other Platforms Key Points There are two key types of migration from non-SharePoint platforms to SharePoint 2010: • • Application migration Content migration Application migration involves the movement of application logic into a SharePoint 2010 environment. .

However. you will almost always find that an application migration leads to some loss of function. . If your file share has very long folder and file names or very deep folder hierarchies. File Shares You should concentrate your planning effort on the delivery of functionality to users. You may find that file shares are more appropriate for a particular file type. you can create a new SharePoint document library for new content and treat the existing content as an historical archive. you may have raw documents that you just need to move to a document library. For example. If a file share has complex ACLs and inheritance. you may not be able to manage these because the URLs may become too long. even if new functionality is available. such as virtual images or very large files that will gain little from content management features such as check-in. Remember to plan for any search issues that are associated with document interrogation. You can leave this as a self-service option. Security and Structure More complex considerations for file shares are the depth of hierarchy and the current application of access control lists (ACLs). If file creation or modification dates are important for regulatory compliance. The data is easy to move. so users migrate files to SharePoint sites as they require them. which generally have no interdependencies or links to external sources. it may seem obvious to migrate because they already have an application that they know. You can ask users to identify such additional complexities to ensure that you can plan for data access or file modification. you must establish whether this provides a business benefit. An obvious exception may be worksheets in Microsoft Office Excel that may have embedded links to external data sources. Data Types You must understand the type of data that you are going to migrate. or you may have complex business logic that will take a great deal of effort to migrate. Be aware that the creation date of a file will change when you migrate to SharePoint 2010. check-out.15-20 Designing a Microsoft® SharePoint® 2010 Infrastructure These two options can be extreme. file shares contain files and documents. or versioning. For users. Office SharePoint provides access through URLs. However. You should also establish whether an application is an off-the-shelf solution or a heavily customized solution. SharePoint 2010 can hold these files through the remote binary large object (BLOB) storage functionality. you will find that a direct security mapping is not a trivial task.

ACL management is more complex. It gives rights based on e-mail addresses rather than Active Directory® directory service service tokens. Web Content Management Content If you have a request to migrate from an existing Web content management system. Web Parts. You should plan for a developer or development team to review these to estimate any time that you may need to budget for re-creation of components. However. but users must have the Microsoft Office Outlook® client to view these. because Microsoft Exchange has a different ACL model. On a more technical level. especially if the environment has been in service for a long time. Solution components such as navigation. this is not easy to represent in HTML because a print screen is a Component Object Model (COM) component object. Public Folder Analysis One of the main difficulties can be the analysis of your public folders. You may find that the effort involved in public folder analysis is difficult to justify in terms of time and resources. . it is easy to move Web pages and image libraries directly into SharePoint 2010.Planning for Upgrading to SharePoint 2010 15-21 Microsoft Exchange Public Folders For Microsoft Exchange public folders. it is common to embed images. such as print screens. which can be a considerable effort. For example. For example. You can re-create these. but it will take effort. you must plan for the types of documents that you commonly find in a public folder. Compound documents—files that contain files—may also require a lot of planning. there are out-of-the-box forms for migration of entities such as contact lists directly into SharePoint 2010. As with shared folders. in e-mails. such as page layouts. but you must ensure that there are no environment-specific or applicationspecific components that the users assume will migrate. these may not be well documented. so your plan should include analysis of such requirements. it is unusual for you to find links between documents. You can save these as . You may have to manually map between these two. you must plan the move based on the complexity of this environment.msg files. and applets can cause difficulties.

You should not permit this to become part of the general upgrade plan. However. Instead. you should treat this as a separate project. because a complex application migration may extend your overall migration effort and impact overall productivity. you should establish a new project with new budget. . you should check for available tools to assist you in complex projects. such as forms-based data. you may find that you have well-established or business-critical systems that may be included in a data migration project. schedules. if you have a request to migrate from Lotus Domino. For example. is relatively simple. Migration of content. If you must migrate from an external platform. and success criteria.15-22 Designing a Microsoft® SharePoint® 2010 Infrastructure Third-Party Platforms Far more complex—and probably out of the scope of an upgrade plan—is migration from another application platform to SharePoint 2010.

Objectives After completing this lesson. You must be methodical in your approach. technical. The team must then establish the working practices and resources that are necessary for the upgrade to complete successfully. List the tasks that are necessary to plan an upgrade. from requirements analysis to support. which should deliver business. Describe the importance of business communications in the upgrade process. you will be able to: • • • • Describe the upgrade cycle. . Describe the goals of a farm survey. because you will have to prepare all of the solution design areas.Planning for Upgrading to SharePoint 2010 15-23 Lesson 2 Planning Your Upgrade Planning is critical to a successful upgrade project. Prepare by assembling the right team. and project management skills.

15-24 Designing a Microsoft® SharePoint® 2010 Infrastructure • • • • Describe how to use tools to gather information about the current environment. Describe how to develop an upgrade schedule. Describe how to use the upgrade planning worksheet. Describe the steps for cleaning up the current environment. .

Prepare Your upgrade plan should reflect what you have learned. The following sections describe these stages. It must have an exhaustive breakdown of events in chronological order. It should also include information about how to . Use the available tools to preempt issues such as missing dependencies or lack of storage capacity. You should know and evaluate the update options for your farm or farms. This plan should include all prerequisites. Learn Ensure that you fully understand—and your plan reflects—upgrade requirements such as 64-bit hardware and software. so that the administrators who implement your plan have all of the correct components in place. You must also ensure that your plan reflects business requirements such as system downtime. This should include development of a plan for the completion of all of the tasks that are necessary for all of the versions of Office SharePoint that you must upgrade.Planning for Upgrading to SharePoint 2010 15-25 The Upgrade Cycle Key Points There are five key stages to a successful upgrade.

you should have experienced users who can test the validity of data to reveal any potential issues. This will be of particular relevance to users who upgrade from Office SharePoint Portal Server 2003 or migrate from third-party platforms. but monitor the progress of your upgrade by viewing the status indicators. you must always pretest your plan.15-26 Designing a Microsoft® SharePoint® 2010 Infrastructure identify and manage any existing customizations and how to manage individual solutions and items. and not just the visual changes in the UI. of course. Validate Always validate an upgrade by reviewing logs and testing applications. it can be easy to ignore apparently minor errors. this should be no different for SharePoint 2010 upgrades. Use copies of production data and hardware if possible. You should have established how much time the upgrade will take through your test runs. such as a hardware or power problem. and it will cause greater problems for your organization. attempting to rebuild a business system after a failed upgrade will take longer. An upgrade failure may be beyond your control. Always establish a fallback position. Test If you are upgrading a business-critical system. Implement When you have completed your tests and are satisfied with your mitigation plan. After a long upgrade. If possible. As part of your upgrade. You should also test for user experience (UX) in addition to UI changes. take time. but you must check everything thoroughly. Your user acceptance testing must ensure that users are happy with any changes to working practices enforced by the upgrade. This will help you to assess any time differences between your tests and the upgrade exercises. you should schedule the upgrade. so you must have a plan for ensuring that your business users can still work in the morning. This does. you should build a test environment and test each component of your upgrade. . However. Note that the UX concerns the overall familiarity of your applications. but you can sample data and virtual machines to do worthwhile upgrade testing.

Plan business communications. Undertake farm surveys. Execute upgrade tools to gather information about the current environment. This means that in addition to planning to perform all of the installation tasks. The list of tasks that you should perform when planning an upgrade includes: • • • • • • • Gather business requirements. Perform environment cleanup. Build hardware. you must also plan a complete review of your existing environments. .Planning for Upgrading to SharePoint 2010 15-27 Upgrade Planning Tasks Key Points Planning an upgrade is more complex than planning a new deployment—it has all of the challenges of a fresh deployment and the additional problems of migrating existing business environments to the new platform. Test the upgrade.

Some of these areas. Establish launch and ongoing support management. . Establish a project schedule.15-28 Designing a Microsoft® SharePoint® 2010 Infrastructure • • • • • Perform pre-upgrade backups. Test rollback and restore options. Perform post-upgrade activities. such as backups. are covered elsewhere in this or other modules in this course and are not duplicated here. such as testing and business requirements gathering. Others may be specific to your organization and will not be covered in any detail.

.Planning for Upgrading to SharePoint 2010 15-29 Planning Business Communications Key Points Upgrades may affect users through changes to applications. unavailability of service. or changes to working practices. If you do not. This is not solely your responsibility and should be undertaken by the entire project leadership team. These team members are probably closer to the business than you and should be able to identify key departments and workers who must be engaged in the project or supported through the changes. You must prepare the users for these events. you may find that their response to the new—and hopefully improved—services may be negative. particularly the project sponsor and business stakeholders.

How you plan your upgrade can have a significant effect in this area. An inplace upgrade in any but a small departmental environment will involve more support staff in this role. Do not surprise users with a new deployment.15-30 Designing a Microsoft® SharePoint® 2010 Infrastructure The key elements of your communications planning should include the following: • Announce the upgrade. • • • . This will reduce support calls significantly and will engender a team ethic in the company. You should plan to have mentors available on launch day to help with any transition issues. even if everything happens during business downtime. This will minimize support desk calls on launch day. are fully conversant with both the applications and the administrative functions that they are likely to use. Plan launch support. so you should work to involve key users and their managers in this activity. Identify administration training. You and the upgrade team are almost certainly familiar with SharePoint 2010. You must ensure that project team stakeholders identify all of the groups and the changes that may occur to their working environments. but the administrators and system operators are still working to maintain the Office SharePoint Server 2007 environment. You must prepare users and preferably engage them in the preparation for the upgrade. You must plan and predeliver any training that is necessary on a test system. such as over a weekend. Make sure that these people. and they should work with users rather than just offering telephone support. who will include frontline support staff. These mentors should be staff from either the IT department or the business. It may also identify potential issues that you can then use as input to your overall upgrade plan. Identify user training requirements.

If you understand your farm environment. Steps that you may need to take include: • • Planning to run the Pre-Upgrade Checker tool to quickly identify problems that SharePoint 2010 flags. you will find it easier to ensure that your upgrade is trouble-free. Planning to perform a manual inspection of the farm to identify potential issues.Planning for Upgrading to SharePoint 2010 15-31 Planning a Farm Survey Key Points When you have your business requirements. This can be a sizeable effort. so do not underestimate the time that is necessary to complete a farm survey. you must plan a thorough review. and this is a good place to start. It you are not confident in your system documentation. You should already have documentation that supports your farm. the next step is to plan a thorough survey of your farm. such as customizations. .

but if your documentation is incomplete. you must factor this into your plan. Identifying numbers of sites and customizations.15-32 Designing a Microsoft® SharePoint® 2010 Infrastructure • Establishing whether you must identify changes by rebuilding an uncustomized version of your production farm and comparing it with the live environment—perhaps by running WinDiff. • . Clearly this is a major task.

and an HTML report. It provides two different types of information: . The utility reads SharePoint database information but makes no changes to your environment. a text log. These tools are primarily designed to help you discover the composition of your Office SharePoint Server 2007 deployment. You can run the command against the entire farm or against individual servers in the farm. These have been enhanced because Office SharePoint Server 2007 has the potential to include a large array of customizations. The command generates an XML log.Planning for Upgrading to SharePoint 2010 15-33 Gathering Information about the Current Environment Key Points There are several tools that you can use to gather information about the current environment so that you can plan the upgrade better. Many of these tools ship with Office SharePoint Server 2007 SP2. Pre-Upgrade Checker Tool You run this utility with the stsadm command. You can therefore run and rerun the utility as many times as you want to review changes that you make.

15-34

Designing a Microsoft® SharePoint® 2010 Infrastructure

Information report: • • • • • • • • Farm servers Databases Alternative address mapping configuration Site definitions Features Web Parts Event receivers Installed language packs

Issue report • • • • • Missing site definitions Missing features Missing assemblies Data orphans Modified content databases

The Pre-Upgrade Checker provides reference links to Knowledge Base articles that will support you in using the tool. You do not have to run the Pre-Upgrade Checker tool before you upgrade, as was the case with PreScan for Office SharePoint Server 2007. However, you are strongly advised to do so.

Gathering Information about Sites
There are several tools for gathering information about sites. Although it may seem surprising to some, most farm administrators are not aware of all of the sites that exist in their Office SharePoint Server 2007 farms. The stsadm –o EnumAllWebs command provides a list of all of the sites that exist in a farm. SPDiag V2 ships with the SharePoint Administration Toolkit. This can help you to identify customizations and custom settings in the current environment. SPDiag V2 is designed to collect and review data from SharePoint Web servers, application servers, and computers running Microsoft SQL Server®, which it stores in a SQL Server database for analysis. SPDiag V2 can collect performance data from: • • Internet Information Services (IIS) logs. Unified Logging Service logs.

Planning for Upgrading to SharePoint 2010

15-35

• •

Performance counters. Windows Management Instrumentation (WMI).

You can display data in the Trends pane of the SPDiag interface and use filters to reveal trends, bottlenecks, and other performance issues. You can also view the individual components and the logical structure of the farm in the Snapshot pane.

Gathering Information about Customizations
If your organization has deployed customized InfoPath form solutions, you should plan to run the stsadm -o ExportIPFSAdminObjects command. In these cases, a globally unique identifier (GUID) is inserted into the configuration database for which you may not have installation source code. The command gathers the deployment information, which you can then export for application if you perform a database attach upgrade.

Gathering Information about Content Databases
For content databases, you should plan to use the new Test-SPContentDatabase command. This tool tests the combination of a content database and the Web application. Again, this does not modify a database. You can run this on Office SharePoint Server 2007 and SharePoint 2010 prerelease versions. The report that this tool generates provides information about: • • • • • Current or potential issues. Data orphans. Missing site definitions. Missing features. Missing assemblies.

The report also shows table sizing metrics. There are also several Windows PowerShell™ commands that your administrators can use during the upgrade process. Although these are not necessarily important to your planning, you should ensure that the upgrade team is aware of the function and use of the following commands: • • • Upgrade-SPContentDatabase Upgrade-SPEnterpriseSearchServiceApplication Upgrade-SPSingleSignOnDatabase

15-36

Designing a Microsoft® SharePoint® 2010 Infrastructure

Cleaning Up the Current Environment

Key Points
You should always plan a system cleanup prior to an upgrade. Often, people regard the upgrade itself as the system cleanup; it is a chance to start again and leave behind issues from the previous version. If you fail to clean up your environment prior to upgrade, you may find that the problems from the past quickly become the problems of the present. You can minimize time and issues by removing components and content that you do not use. Always perform a full backup before you delete content or customizations that you believe are no longer used. As part of your upgrade, you should perform the following actions: • • Delete unused sites and Web applications. This reduces the time for the upgrade and may remove potential customization problems. Remove unnecessary document versions. This reduces the volume of data and will reduce upgrade time.

Planning for Upgrading to SharePoint 2010

15-37

Clean up templates, features, and Web Parts. This removes customizations that your organization no longer uses and will minimize the number of customization issues. This is particularly important if you plan to perform an in-place upgrade. Repair data issues. You should identify problems such as undeletable sites or lists. There are additional tools in Office SharePoint Server 2007 SP2 and cumulative updates that administrators can use for problems such as these. The tools include the following commands: • • • stsadm -o DatabaseRepair [-deletecorruption] stsadm -o ForceDeleteList stsadm -o VariationsFixupTool

15-38

Designing a Microsoft® SharePoint® 2010 Infrastructure

Planning the Upgrade Schedule

Key Points
Your upgrade is a long-term project. Most people only regard the upgrade as starting when you begin the first data backup; this is realistically the conclusion of your upgrade planning. You should spend far more time in planning and discussion than you spend in performing an upgrade. You must treat your upgrade as you do any large project. Assemble your team, which should include someone with project management experience. You should have an initial schedule, which defines the top-level activities and the key dates on which you must complete them to deliver the upgrade at the agreed time. You can keep this schedule information in an Excel 2010 workbook, but most upgrade projects are better organized in a Gantt chart. This is because all upgrades involve a team of business and technical staff and a number of interrelated steps. It is important to be able to track dependencies in this sort of project.

Planning for Upgrading to SharePoint 2010

15-39

Establishing Upgrade Milestones
Each milestone is associated with a series of dependent or independent activities, each of which you must complete before you can achieve the milestone. For anything less than the most trivial upgrade—a test environment—you should create a project plan that associates all milestones with activities and all activities with a named person who is responsible for them. You must also specify a completion date for each activity. If you follow this practice, you will find it possible to manage and preempt issues.

Planning for Risk Management
You should always plan for problems. This means that you provide additional time to ensure that you can deliver against your plan, even if problems occur; experience shows that you can never have too much time allocated to an upgrade project. It is notoriously difficult to give an exact timescale for an upgrade project. However, if you find that you are running ahead of schedule, you have an opportunity to reschedule the upgrade for an earlier date. The list of activities is too extensive to post here, and they are often specific to a company. The best way to test your plan is to perform a dry run in a meeting of the project team with an independent project manager acting as assessor or mentor. This independent view can ensure that you do not miss anything critical, such as ordering 64-bit equipment in time for the upgrade date.

15-40

Designing a Microsoft® SharePoint® 2010 Infrastructure

Documenting the Upgrade Plan

Key Points
You must document your upgrade plan in detail. A good way to document the upgrade plan is by using a worksheet. A worksheet can help you marshal the key upgrade information for an existing farm and establish the high-level steps that are necessary to complete your upgrade projects. The columns in the worksheet should include: • • • • • • • Farm. The name, or identifier, of the farm that you plan to upgrade. Site name. The name of the site to which you will upgrade. Parent site. The name of the parent site or Web application. Site URL. The URL for the site, based on the parent site prefix. Purpose. A description of the purpose of the site. Template. The template that was used to create the site. This is useful for identifying templates that may have been deprecated by Microsoft. Version. The current version of Microsoft Office.

Planning for Upgrading to SharePoint 2010

15-41

• •

Content database name. The name of the current content database. Customizations. A list of the customizations on the site, such as Web Parts, master pages, and site templates. This does not specify the particular Web Part or master page, which you should detail in a separate document. Operating system version. The Windows operating system server version and service pack level. SQL Server version. The SQL Server version and service pack level. Upgrade approach. The preferred upgrade option—database attach, in-place, or hybrid. Upgrade steps. The high-level steps for completing the upgrade. Note that this document assumes that elements such as requirements gathering have already been completed. There should be a more detailed plan that breaks each of these steps into procedures. Target Web application. The URL for the target Web application.

• • • •

The goal of the upgrade planning worksheet is to gather all of the core data in a single place. For highly complex or large upgrades, you should create additional documentation that details planning steps for specific issues.

Additional Reading
For more information about planning worksheets, see http://go.microsoft.com/fwlink/?LinkID=200926&clcid=0x409 and http://go.microsoft.com/fwlink/?LinkID=201265&clcid=0x409.

not just to have the latest version. You must always remember that the reason for upgrading is to enhance the productivity of the business. There are several technical and business elements that also have an effect on the plan. .15-42 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 3 Upgrade Considerations An upgrade plan provides the high-level steps for a project and possibly some detailed elements. Your plan must also reflect consideration for how the upgrade will affect users. you will be able to: • • List the hardware requirements for the upgrade. You should always create your upgrade plan and then review your plan with reference to these considerations. such as minimizing production downtime. Objectives After completing this lesson. SharePoint 2010 ships with several IT and user options that will affect how you perform and then manage the entire upgrade experience for IT staff and information workers. List the software requirements for the upgrade.

Planning for Upgrading to SharePoint 2010 15-43 • • • • Describe the options that you can use to minimize farm downtime during the upgrade process. . Explain how administrators can use the logging and reporting services that are available in SharePoint 2010 to maximize upgrade efficiency. Describe the options that you can use to preserve the appearance of the applications that you upgrade. Describe how to plan for and manage problems in a SharePoint 2010 upgrade.

Hardware Processor RAM Minimum requirements 64 bit. 8 GB for production use in a single-server or multiple-server farm. . Application Servers The following table describes the minimum hardware requirements for application servers.15-44 Designing a Microsoft® SharePoint® 2010 Infrastructure Hardware Requirements Key Points The requirements in the following sections apply both to installations on a single server with a built-in database and to servers running SharePoint Server 2010 in a multiple-server farm installation. four cores. 4 gigabytes (GB) for developer or evaluation use.

Hardware Processor Minimum requirements 64 bit. which is normally twice the amount of memory in a production environment. eight cores for medium deployments. RAM 8 GB for small deployments.com/fwlink/?LinkID=201270&clcid=0x409. Use SQL Server capacity recommendations for large deployments. 16 GB for medium deployments. For more information about storage and SQL Server capacity planning and configuration.microsoft. Maintain sufficient free space for memory swapping. four cores for small deployments. see http://go.com/fwlink/?LinkID=201266&clcid=0x409. Provide sufficient disk space for content databases and projected growth and peak period usage. Provide sufficient disk for content databases and projected growth for peaks and growth. 64 bit.microsoft.Planning for Upgrading to SharePoint 2010 15-45 Hardware Hard disk Minimum requirements 80 GB for system drive. Additional Reading For more information about the hardware requirements for SharePoint 2010. Hard disk 80 GB for system drive. which is normally twice the amount of memory in a production environment. . Database Servers The following table describes the minimum hardware requirements for database servers. see http://go. Maintain sufficient free space for memory swapping.

or Web Server Web server (IIS) role . Environment Database server in a farm Minimum requirements One of the following: • The 64-bit edition of Microsoft SQL Server 2008 with SP1 and cumulative update (CU) 2 or 5 • Microsoft SQL Server 2008 R2 • SQL Server 2005 with SP3 Single server with a built-in database One of the following: • The 64-bit edition of Windows Server® 2008 Standard. Enterprise. Enterprise. Datacenter. Datacenter.15-46 Designing a Microsoft® SharePoint® 2010 Infrastructure Software Requirements Key Points The following table lists the software requirements for SharePoint 2010 by server type. or Web Server with SP2 • The 64-bit edition of Windows Server 2008 R2 Standard.

5 SP1 Microsoft Sync Framework Runtime v1.0 Microsoft Chart Controls for the Microsoft .NET ADO. Datacenter.NET Framework 3.NET Framework 3.NET Framework version 3. Datacenter. Enterprise.5 SP1 Windows Identity Foundation (WIF) One of the following: • The 64-bit edition of Windows Server 2008 Standard.0 Microsoft Chart Controls for the Microsoft .0 SQL Server 2008 Native Client Microsoft SQL Server 2008 Analysis Services ADOMD.NET ADO. Enterprise.5 Windows PowerShell 2.0 (x64) Microsoft Filter Pack 2.NET Data Services Update for .5 SP1 WIF A supported browser. or Web Server Web server (IIS) role Microsoft software: • • • • • • • • • • Client computer Application server role Microsoft .NET Framework 3.Planning for Upgrading to SharePoint 2010 15-47 Environment Minimum requirements Microsoft software: • • • • • • • • • • • Web Front End (WFE) servers and application servers in a farm Application server role Microsoft .NET Framework 3.NET Data Services Update for .0 (x64) Microsoft Filter Pack 2.0 SQL Server 2008 Native Client Microsoft SQL Server 2008 Analysis Services ADOMD. preferably tier one .5 Windows PowerShell 2.NET Framework 3. or Web Server with SP2 • The 64-bit edition of Windows Server 2008 R2 Standard.5 SP1 SQL Server 2008 Express with SP1 Microsoft Sync Framework Runtime v1.

.microsoft.15-48 Designing a Microsoft® SharePoint® 2010 Infrastructure Additional Reading For more information about the software requirements for SharePoint 2010.com/fwlink/?LinkID=200868&clcid=0x409. see http://go.

because the production processes and the upgrade process may cause performance issues. You can . and particularly Web publishing environments. You can maintain content availability by providing a read-only version of the data that users can access while you update the original database. You can deliver this productivity by locking the copy version through SQL Server. Read-Only Content Databases For many databases.Planning for Upgrading to SharePoint 2010 15-49 Minimizing Downtime Key Points All upgrades take time and resources. You may also consider different systems for databases. SharePoint 2010 is coded to automatically trim all update functionality from the UI when it presents information from a read-only database. Note: The use of read-only databases requires different server machines. because you cannot install both Office SharePoint Server 2007 and SharePoint 2010 server code on the same system. most transactions are reads rather than writes. but you must minimize your farm downtime so that your organization can remain productive.

Content Database Attach with Alternate Access Mapping Redirection If your organization must upgrade in phases. it is difficult to develop a test scenario that behaves exactly like a production environment. This process does not replace an automated gradual upgrade system with a manual one. you can plan to use the redirect functionality that is now available to alternate access mapping in SharePoint 2010.microsoft. You may also need to use additional tools to complete the process. which means that you can upgrade more than one database at a time. Additional Reading For more information about how to use alternate access mapping URL redirection as part of the upgrade process in SharePoint Server 2010. service databases will not work as expected if set to read-only. You must test your hardware to establish how many upgrade sessions you can run concurrently. Parallel Database Upgrades You can plan to perform parallel database attach upgrades through a manual process. however. Note: This solution is available for content databases only. This is a complex option and has a large number of manual steps to achieve a working solution. . such as URL fix-up tools for InfoPath forms and form templates.15-50 Designing a Microsoft® SharePoint® 2010 Infrastructure test to see whether this may be a problem.com/fwlink/?LinkID=200927&clcid=0x409. see http://go. SharePoint 2010 supports multiple sessions.

Planning for Upgrading to SharePoint 2010 15-51 Using Visual Upgrade Key Points If business users have a reason for maintaining the look and feel of their SharePoint environment. You can delegate the UI migration to site collection administrators. you can preview the new UI at a site collection or site level. and later for education. you can choose to maintain the appearance of Office SharePoint Server 2007 in an upgraded SharePoint 2010 site. . Setting 3 specifies the Office SharePoint Server 2007 UI. As part of your test plan. Note: If you make changes to pages or add new pages while in preview mode. and setting 4 indicates the SharePoint 2010 UI. these pages may not work as expected if you revert to Office SharePoint Server 2007. There are properties on each site collection and site that you can use to specify a UI version for the site. SharePoint 2010 ships with Office SharePoint Server 2007 master pages and cascading style sheets (CSS) so that you can preserve application appearance. This is the default when you upgrade. such as the need for additional training.

although individual site page do revert. so you should test all screens and Web Parts as part of your visual check of upgraded pages in the SharePoint 2010 UI mode. . Report Server Web Parts.15-52 Designing a Microsoft® SharePoint® 2010 Infrastructure You should note in your plan that some pages only work in the new UI version: • • • The My Site host page. The new UI uses strict mode XHTML. A Project Web Access site collection. This may cause issues in rendering.

but you should plan for how your site administrators should use logs and status reports during the upgrade process. so there will be a log for each session in a parallel database attach upgrade. You should also review logs and reports on your test upgrades to mitigate problems later. Logging During Upgrades SharePoint 2010 provides a single upgrade log for each upgrade session.Planning for Upgrading to SharePoint 2010 15-53 Logging and Status Reporting During Upgrades Key Points The use of logs and status reports may seem to be a post-planning activity. You can now interrogate and report on all of the logs by using parsing tools. where the single log just grew larger with each upgrade. This may be true. because you can focus on specific upgrade tasks. This makes it easier to review issues. . which only writes errors to disk. This was not the case with previous versions of Office SharePoint. You should also plan for administrators to review all entries in the upgrade error log. because the report log schema is now structured.

. this enters multiple references for parallel upgrade sessions If your administrators prefer to use the command-line upgrade options. The status report tracks the upgrade history. these now have a status indicator. which is now available throughout the upgrade process. Again.15-54 Designing a Microsoft® SharePoint® 2010 Infrastructure Status Reporting During Upgrades It is also useful for you to ensure that administrators track the status page. so there should not be any doubt about whether the upgrade is proceeding.

and platform support issues. solution deployments. Identify and assess customizations so that you can redevelop or replace customizations that do not work with SharePoint 2010. problems. Preventing Issues If you prepare properly. so remember to: • Perform farm analysis so that you understand the current SharePoint structure. Prepare the farm so that you can minimize issues such as service application upgrade changes.Planning for Upgrading to SharePoint 2010 15-55 Mitigating Risks and Managing Failure Key Points For a smooth and successful upgrade. the business functionality. you will have a much smoother transition. and the hardware platform. This will enable you to develop both a cleanup schedule and a checklist for functional testing. you must have a mitigation plan for all possible upgrade risks. • • .

you must restart the upgrade process by using Psconfig.exe to upgrade the remaining sites. In some cases. the upgrade error log. you should initially consult the status page. you can restart upgrade by using a Windows PowerShell cmdlet to upgrade just the skipped sites. Perform a database content check to ensure that data validity is not compromised. Some of these errors already have links to Knowledge Base and other documents that refer to the errors that you may encounter. The process is as follows: • Determine the cause of failure. If you do not do so. you might have to restart the upgrade to finish upgrading your sites from Office SharePoint Server 2007 to SharePoint 2010. Fix the issue. Managing Failures If you do encounter issues during your upgrade process. This may seem obvious. During a database attach upgrade. but you must ensure that the people who implement your plan have the knowledge and the authority to fix problems. These are designed to trap and report errors that you can then troubleshoot. Resume the upgrade. There is a process for failure management. such as a minor customization. This means that you do not require a plan for backing out of a partial upgrade because of a minor problem that you can fix. you may find that the upgrade ended on Saturday morning for an error that could have been fixed in a very short period of time. you must not panic. • • • . Always check data with users. if the server restarts or the upgrade fails. and you must build this into your upgrade plan. You can restart SharePoint 2010 upgrades at the point of failure. In the event of a failure. After you have corrected any issues in the sites (such as a missing template or language pack.15-56 Designing a Microsoft® SharePoint® 2010 Infrastructure • • Test the upgrade in a test environment so that you can address functional and user issues before you perform the production environment upgrade. For example: • During an in-place upgrade. and then the upgrade log. any sites that cannot be upgraded will be skipped. or the site being set to read-only or having exceeded its quota).

0. Ltd is about to acquire a smaller pharmaceutical company. The Finance department at Trey Research would like to keep its farm independent of the central Contoso. and Office SharePoint 2007 deployments. Trey Research. However.Planning for Upgrading to SharePoint 2010 15-57 Lab: Planning for Upgrading to SharePoint 2010 Exercise 1: Creating an Upgrade and Migration Plan Scenario Contoso. Trey Research includes SharePoint deployments over three farms. The SharePoint infrastructure at Trey Research includes Windows SharePoint Services 2. Ltd IT will support this farm. You should reuse Trey Research hardware where appropriate. and it will require upgrading to SharePoint 2010.0. Contoso. . Your team must create an upgrade plan that will incorporate the intranet and research sites at Trey Research into the central SharePoint 2010 farm. Ltd farm. Windows SharePoint Services 3.

. Task 1: Read the supporting information 1. and Target Web Applications to complete the upgrade planning worksheet. The main tasks for this exercise are as follows: 1. Read the supporting information. Read the lab scenario. You have already gathered the requirements information about the three farms and included it in an upgrade planning worksheet. You must now add your recommendations on the Upgrade Approach. complete the worksheet in the Upgrade Planning Worksheet. Steps.15-58 Designing a Microsoft® SharePoint® 2010 Infrastructure Trey Research has a file share that it uses for document management. Complete the Upgrade Planning worksheet. Log on to 10231A-NYC-DC1-15 as CONTOSO\Ed with the password Pa$$w0rd. Task 2: Complete the Upgrade Planning worksheet • In the E:\Labfiles\Lab15\Starter folder. You must ensure that the documents in this file share are transferred into the Contoso. 2. Ltd document site collection (Docs).xlsx file. 2.

2.Planning for Upgrading to SharePoint 2010 15-59 Module Review and Takeaways Review Questions 1. Ensure that the environment is fully functioning before you perform an upgrade. 3. . What are the two options for upgrading to SharePoint 2010? If you perform an in-place upgrade of a farm with SSP. what happens to the services? How can the use of read-only databases help you to minimize upgrade downtime? Best Practices Related to Upgrade Preparation Supplement or modify the following best practices for your own work situations: • • Update your servers to SP2 of Office SharePoint Server 2007.

.15-60 Designing a Microsoft® SharePoint® 2010 Infrastructure • • Run the Pre-Upgrade Checker tool to look for potential issues. Perform a trial upgrade on a test farm first.

.Planning for Upgrading to SharePoint 2010 15-61 Course Evaluation Your evaluation of this course will help Microsoft understand the quality of your learning experience. Your open and honest feedback is valuable and appreciated. Please work with your training provider to access the course evaluation form. Microsoft will keep your answers to this survey private and confidential and will use your responses to improve your future learning experience.

.

Lab: Designing a Logical Architecture L1-1 Module 1 Lab Answer Key: Designing a Logical Architecture Contents: Exercise 1: Mapping Business Requirements to a Logical Architecture Design Exercise 2: Creating a Logical Architecture Diagram L1-2 L1-3 .

In Windows® Explorer.docx.L1-2 Module 1: Designing a Logical Architecture Module 1: Designing a Logical Architecture Lab: Designing a Logical Architecture Exercise 1: Mapping Business Requirements to a Logical Architecture Design Task 1: Read the supporting information 1. 5. In Windows Explorer. move to the E:\Labfiles\Lab01\Starter folder. Read the lab scenario. and then read the requirements document. 2.docx. . Log on to 10231A-NYC-DC1-01 as CONTOSO\Ed with the password Pa$$w0rd. double-click Logical Architecture Planning Worksheet. Compare your solution to the sample solution located at E:\Labfiles\Lab01\Solution\Logical Architecture Planning Worksheet Solution. 2. 3. double-click Contoso Business Requirements. in the E:\Labfiles\Lab01\Starter folder. Task 2: Complete the Logical Architecture Planning worksheet 1. Close all windows. Click Start. and then complete the worksheet. double-click Logical Architecture Requirements.xlsx. and then click Computer.xlsx. In Windows Explorer. 3. 4. and then read the requirements document.

Complete the Microsoft® Visio® diagram so that it looks similar to the sample solution located at E:\Labfiles\Lab01\Solution\Logical Architecture Diagram Solution.vsd. and then double-click Logical Architecture Diagram. move to the E:\Labfiles\Lab01\Starter folder.Lab: Designing a Logical Architecture L1-3 Exercise 2: Creating a Logical Architecture Diagram Task 1: Complete a logical architecture diagram 1. In Windows Explorer.vsd. . 2.

.

Lab 2: Planning a Service Application Architecture L2-1 Module 2 Lab Answer Key: Planning a Service Application Architecture Contents: Exercise 1: Designing a Logical Architecture Exercise 2: Creating Service Applications and Assigning Proxy Groups L2-2 L2-3 .

Compare your solution to the sample solution located at E:\Labfiles\Lab02\Solution\SharePoint 2010 Service Applications Planning Worksheet . . and then read the requirements document. and then click Computer.docx. double-click Logical Architecture Requirements. In Windows® Explorer. double-click SharePoint 2010 Service Applications Planning Worksheet. Task 2: Complete the Service Applications Planning worksheet 1. 5. move to the E:\Labfiles\Lab02\Starter folder. Read the lab scenario. In Windows Explorer. 4.docx. double-click Contoso Business Requirements. Close all windows. Log on to 10231A-NYC-DC1-02 as CONTOSO\Ed with the password Pa$$w0rd. 2. 3. In Windows Explorer. 2. and then read the requirements document.xlsx.xlsx. 3. Click Start.L2-2 Module 2: Planning a Service Application Architecture Module 2: Planning a Service Application Architecture Lab 2: Planning a Service Application Architecture Exercise 1: Designing a Logical Architecture Task 1: Read the supporting information 1.Solution. and then complete the worksheet.

click Use existing application pool. Under Web Application / Service Application. and then click OK. Click Start. click SharePoint Web Services Default. and then click SharePoint 2010 Central Administration. 7. and then click Managed Metadata Service. click Manage service applications. . 4. 3. 2. Under Service Applications. and then click OK. click Yes. click All Programs. click Configure service application associations. type MMS_Default In the Database Name box. 5. and then click Managed Metadata Service. In the User Account Control dialog box. and then click OK. type MMS_Research 10.Lab 2: Planning a Service Application Architecture L2-3 Exercise 2: Creating Service Applications and Assigning Proxy Groups Task 1: Create Managed Metadata Service applications 1. and then click Application Management. click Microsoft SharePoint 2010 Products. 8. In the Create New Managed Metadata Service dialog box. Click New. click [custom]. click SharePoint Web Services Default. click the Central Administration breadcrumb link. On the Browse tab. Click New. 5. Under Application Pool. click Use existing application pool. 6. in the Name box. In the Create New Managed Metadata Service dialog box. type TermStore_Default Under Application Pool. in the list. Task 2: Associate a service application with a custom proxy group 1. In the Configure Service Application Associations dialog box. Select the MMS_Research check box. in the list. 3. type TermStore_Research 11. 9. in the Name box. 2. click SharePoint Research. Under Application Management. 4. In the Database Name box. in the Edit the following group of connections list.

.

Lab: Planning for Performance and Capacity L3-1 Module 3 Lab Answer Key: Planning for Performance and Capacity Contents: Exercise 1: Creating a Performance Plan Exercise 2: Creating a Capacity Plan L3-2 L3-3 .

and then click Computer. Task 2: Complete the Performance worksheet in the Performance and Capacity Planning Worksheet. and then read the document. . double-click Performance and Capacity Planning Worksheet. In Windows Explorer.L3-2 Module 3: Planning for Performance and Capacity Module 3: Planning for Performance and Capacity Lab: Planning for Performance and Capacity Exercise 1: Creating a Performance Plan Task 1: Read the supporting information 1. In Windows Explorer. 2. double-click SharePoint 2010 Capacity Planning Excerpt. Read the lab scenario. In Windows Explorer.xlsx file 1. 2.xlsx.docx. 5. 4.xlsx.docx. double-click SPServer2010CapacitySizingOverview. In Windows® Explorer. double-click Performance and Capacity Requirements. and then read the Workload section within the Right-Sizing SharePoint Server 2010 Deployments section of the document. Log on to 10231A-NYC-DC1-03 as CONTOSO\Ed with the password Pa$$w0rd. and then complete the Performance worksheet. Click Start. move to the E:\Labfiles\Lab03\Starter folder. 3. and then read the document. Compare your solution to the sample solution located at E:\Labfiles\Lab03\Solution\Performance and Capacity Planning Worksheet – Solution. 6.docx.

and then read the Dataset section within the Right-Sizing SharePoint Server 2010 Deployments section of the document. Task 2: Complete the Capacity worksheet in the Performance and Capacity Planning Worksheet. . 3. In the Performance and Capacity Planning worksheet. 2. double-click SPServer2010CapacitySizingOverview. Close all windows and logoff. 2.docx.xlsx.xlsx file 1. Review the lab scenario. Compare your solution to the sample solution located at E:\Labfiles\Lab03\Solution\Performance and Capacity Planning Worksheet – Solution. complete the Capacity worksheet. In Windows Explorer.Lab: Planning for Performance and Capacity L3-3 Exercise 2: Creating a Capacity Plan Task 1: Read the supporting information 1.

.

Lab 4: Designing a Physical Architecture L4-1 Module 4 Lab Answer Key: Designing a Physical Architecture Contents: Exercise 1: Planning the Physical Architecture Exercise 2: Troubleshooting a Name Resolution Problem L4-2 L4-3 .

double-click Physical Architecture Diagram.Solution. 4. fill in the details for all production. and then complete the worksheet. 2.vsd. staging. 3. 3. 2. and test servers. In Windows® Explorer. In Windows Explorer. Task 2: Complete the Physical Architecture Planning worksheet 1. Close all windows. .L4-2 Module 4: Designing a Physical Architecture Module 4: Designing a Physical Architecture Lab 4: Designing a Physical Architecture Exercise 1: Planning the Physical Architecture Task 1: Read the supporting information 1. Compare your solution to the sample solution located at E:\Labfiles\Lab04\Solution\Physical Architecture Diagram . Compare your solution to the sample solution located at E:\Labfiles\Lab04\Solution\Physical Architecture Planning Worksheet – Solution. and then complete the diagram.xlsx.docx. and then read the non-functional requirements. Read the lab scenario. move to the E:\Labfiles\Lab04\Starter folder. On the Servers sheet. In Windows Explorer. double-click Physical Architecture Requirements. Log on to 10231A-NYC-DC1-04 as CONTOSO\Ed with the password Pa$$w0rd.vsd. and then click Computer. 2. double-click Physical Architecture Planning Worksheet. Click Start. 3.xlsx. Task 3: Complete the Physical Architecture diagram 1.

com. Expand Forward Lookup Zones. You will be able to browse the Contoso.80. Click Start. click Configure alternate access mappings. 3. 3. 9. 14.1 and then click Add Host. In the New Host dialog box. Click Edit Public URLs. 2. 13. point to All Programs. Click Start. Verify that you receive an error and the Web page cannot be displayed. Under System Settings. click Microsoft SharePoint 2010 Products. click Done. and then click New Host (A or AAAA).com. 4. 5. Click Start. in the Name box. type intranet 11. In the IP address box. point to All Programs. 10. In the DNS dialog box. and then click DNS.Lab 4: Designing a Physical Architecture L4-3 Exercise 2: Troubleshooting a Name Resolution Problem Task 1: Attempt to access the Contoso.10. 2. Task 2: Resolve the name resolution problem 1. In the Select An Alternate Access Mapping Collection dialog box. click SharePoint . click OK. expand Contoso. type http://intranet. right-click Contoso. click Internet Explorer. 7. click Yes. Verify that the Fully qualified domain name (FQDN) field contains intranet. and then click Change Alternate Access Mapping Collection. In Windows Internet Explorer®. . In the User Account Control dialog box.Contoso. point to Administrative Tools. go to http://intranet.contoso.contoso. In the Intranet box.com and then click Save. Ltd home page. and then go to http://nyc-dc1.com. 8. and then click SharePoint 2010 Central Administration. In the Alternate Access Mapping Collection. click No selection.10. 6. Minimize Internet Explorer. In the New Host dialog box. 12. type 10.com. 4. Ltd intranet by using two different URLs 1.

click Accessories. and then click Internet Information Services (IIS) Manager.com and then click OK.contoso. Under Connections. Right-click SharePoint – 80.contoso. where you previously failed to go to http://intranet. expand NYC-DC1 (CONTOSO\ed). In the User Account Control dialog box. Close all windows. You should now see that the intranet Host (A) record has a static timestamp. 31. At the command prompt. Click the Refresh button. Click Start. click Close.com and then press ENTER. 24. 27. In DNS Manager. Close DNS Manager. 17.10. 26. click Add.contoso. type ipconfig /flushdns and then press ENTER. At the command prompt. In the Site Bindings dialog box. click Yes. 21.com. and then expand Sites. In the Site Bindings dialog box. point to All Programs. right-click Contoso. Close the Command Prompt window. Click Start. At the command prompt.com. 18. in the Host name box. type intranet. point to Administrative Tools. 20. and then close IIS Manager. and then click Refresh.L4-4 Module 4: Designing a Physical Architecture 15. type ping intranet.contoso. 28. 23. Restore the minimized Internet Explorer window.com to the IP address 10.10. 25. and then log off. The ping command should fail.com and then press ENTER. and then click Edit Bindings. right-click Command Prompt. 30. point to All Programs. In the Add Site Bindings dialog box.contoso. . This command should successfully flush the Domain Name System (DNS) cache. 22. in the left pane. Ltd home page will appear. 16. 19. This command should now successfully resolve intranet.1. 29. The address will now be resolved and the Contoso. type ping intranet. and then click Run as administrator.

Lab 5: Designing a Security Plan L5-1 Module 5 Lab Answer Key: Designing a Security Plan Contents: Exercise 1: Designing for Least-Privilege Security Exercise 2: Identifying and Resolving Potential Security Issues Exercise 3: Granting Read Access to the Production Auditors Group L5-2 L5-3 L5-5 .

move to the E:\Labfiles\Lab05\Starter folder. 3. In Windows Explorer. and then review the document. 6. In Windows® Explorer. Click Start. and then review the diagram. 2. In Windows Explorer. double-click Logical Architecture Diagram Solution. and then review the worksheet. . 5. double-click SharePoint 2010 Security Planning Worksheet.Solution. double-click Contoso Business Requirements. and then click Computer. Close all windows.xlsx. Task 2: Complete the SharePoint 2010 Security Planning worksheet 1. and then complete the worksheet. 3. Read the lab scenario. Log on to 10231A-NYC-DC1-05 as CONTOSO\Ed with the password Pa$$w0rd. Compare your solution to the sample solution located at E:\Labfiles\Lab05\Solution\SharePoint 2010 Security Planning Worksheet Solution.L5-2 Module 5: Designing a Security Plan Module 5: Designing a Security Plan Lab 5: Designing a Security Plan Exercise 1: Designing for Least-Privilege Security Task 1: Read the supporting information 1. 4. 2. double-click SharePoint 2010 Service Applications Planning Worksheet .xlsx.xlsx.vsd.docx. In Windows Explorer.

click Configure service accounts. click Yes. In the User Account Control dialog box. click the drop-down list. point to All Programs. 11. 3.Lab 5: Designing a Security Plan L5-3 Exercise 2: Identifying and Resolving Potential Security Issues Task 1: Apply least privilege to the farm account and reset IIS 1. Click Start. point to New. Task 2: Create and register a new service account as a managed service account and modify which service account is used for an application pool 1. 12. and then click Run as administrator. on the Members tab. click the Managed Service Accounts container. click Accessories. Click Start. and then click OK. In the User Account Control dialog box. In the Select an account for this component list. 14. Minimize the Command Prompt window. Under Security. right-click Command Prompt. point to All Programs. click Yes. click OK. In the Domain Admins Properties dialog box. In Active Directory Users and Computers. 5. and then click SharePoint 2010 Central Administration. point to All Programs. 9. . click Microsoft SharePoint 2010 Products. 2. 4. click SharePoint server farm account. type iisreset and then press ENTER. 13. At the command prompt. and then click Active Directory Users and Computers. 6. 10. Right-click Managed Service Accounts. Click the Users container. double-click Domain Admins. In the Domain Admins Properties dialog box. Next to Credential Management. and in the right pane. In the Active Directory Domain Services dialog box. and then click Farm Account. 8. and then click User. 2. click Yes. and then click Remove. Click Start. click Administrative Tools. click CONTOSO\sp-farm. 7.

4. 14. Close the administrator Command Prompt window. In the New Object . 6. 7. 9. 5. type iisreset and then press ENTER. In the User name box. 5. under Security. On the Remove Managed Account page. Close Active Directory Users and Computers. click Next. under Security. At the command prompt. Restore the minimized administrator Command Prompt window. type sp-apppool and then click Next. and then click Finish. click Configure managed accounts. click OK. 12. In the Select an account for this component list.User dialog box. click Security. type CONTOSO\sp-apppool and in the Password box. Task 3: Remove an account from the managed accounts list and reset IIS 1. click OK. 15. under Remove. click General Security. and then click OK. Click Register Managed Account. On the left menu. click CONTOSO\spapppool. click General Security. 11. In the Message from webpage dialog box. 13. click Configure managed accounts. In SharePoint Central Administration. 10.L5-4 Module 5: Designing a Security Plan 3. 8. 4. . Next to Credential Management. click Configure service accounts. In Central Administration. Restore the Command Prompt window. 2. in the Full name box. and then click Web Application Pool – SharePoint – 80. type SharePoint App Pool Service Account and in the User logon name box. Next to CONTOSO\Administrator. click X. 3. 6. type iisreset and then press ENTER. In the Password and Confirm password boxes. type Pa$$w0rd and then click OK. click the drop-down list. type Pa$$w0rd Clear the User must change password at next logon check box. At the command prompt. and then under General Security.

click Add Users. click Next. . In the Policy for Web Application dialog box. 5. Close all windows. 7. In SharePoint Central Administration. Under Name. and then on the toolbar ribbon. On the Select the Zone page.Lab 5: Designing a Security Plan L5-5 Exercise 3: Granting Read Access to the Production Auditors Group Task 1: Grant a group Full Read access to a Web application 1. On the Add Users page. click OK. In the Policy for Web Application dialog box. type CONTOSO\production auditors and then click Check Names. Under Permissions. in the Users box. click Manage web applications. click SharePoint – 80. 2. click Application Management. and then click Finish. and then under Web Applications. 8. and then log off. 3. click User Policy. 6. select the Full Read – Has full read-only access check box. 4.

.

Lab 6: Planning Authentication L6-1 Module 6 Lab Answer Key: Planning Authentication Contents: Exercise 1: Planning Authentication for Contoso. Ltd Exercise 2: Enabling Claims-Based Authentication L6-2 L6-3 .

Close Microsoft Visio®. in the E:\Labfiles\Lab06\Starter folder. Compare your solution to the sample solution located at E:\Labfiles\Lab06\Solution\Logical Architecture Diagram with Authentication .xlsx. and then complete the worksheet. and then click Computer. Read the lab scenario.L6-2 Module 6: Planning Authentication Module 6: Planning Authentication Lab 6: Planning Authentication Exercise 1: Planning Authentication for Contoso. In Windows Explorer. Close Microsoft® Excel®. 3. double-click Planning Authentication Methods Worksheet.xlsx. move to the E:\Labfiles\Lab06\Starter folder.vsd. 5. Click Start. Log on to 10231A-NYC-DC1-06 as CONTOSO\Ed with the password Pa$$w0rd. . In Windows® Explorer. Ltd Task 1: Complete the Planning Authentication Methods worksheet 1. 2. 4. Compare your solution to the sample solution located at E:\Labfiles\Lab06\Solution\Planning Authentication Methods Worksheet Solution.Solution. 3. Task 2: Complete the Logical Architecture Diagram with Authentication diagram 1. double-click Logical Architecture Diagram with Authentication. 6. and then complete the diagram. 2.vsd.

and then on the toolbar ribbon. click OK. under Authentication. 5. In the Database Name and Authentication section. click SharePoint Internet. In the Security Configuration section. In the Application Pool section. point to All Programs.contoso. click Yes. click OK. click Anonymous Policy. on the toolbar ribbon. click Use an existing IIS web site. In Web Applications Management. Click Start. Task 2: Create a new Web application and configure it to allow anonymous access and to use claims-based authentication 1. 2. In the Message from webpage dialog box. 7. 4. Task 3: Set the anonymous policy for the SharePoint Internet Web application and set anonymous access for the site collection 1. 6. and then in the drop-down list. click Delete. click SharePoint – www. 2. click Manage web applications. In Web Applications Management. on the toolbar ribbon. click Yes. under Allow Anonymous.com Web application 1. click Use existing application pool. and then click Delete. 6. Under Application Management. and then click SharePoint 2010 Central Administration.contoso.com80 (CONTOSO\sp-farm). type Content_www and then click OK. 4. In the User Account Control dialog box. and then in the drop-down list. . verify that No is selected for both options. click the SharePoint Internet Web application. In the Create New Web Application dialog box. click Claims Based Authentication. Click SharePoint Internet. click New. 5. in the Database Name box. In the Delete Web Application dialog box. 3. 3.Lab 6: Planning Authentication L6-3 Exercise 2: Enabling Claims-Based Authentication Task 1: Delete the internet. click Microsoft SharePoint 2010 Products. In the Application Created dialog box. In the IIS Web Site section.

type Pa$$w0rd and then click OK. click Entire Web site. 3. On the Adventure Works home page. On the Permissions page. click Sign in as a different user. type http://www.contoso. 7. In the Windows Security dialog box.contoso.contoso. and then click Sign Out. 3. . Press CTRL+T to open a new tab. 8. 6. and then log off. and then click Site Permissions. Click Start. verify that Zones is set to All zones and Anonymous User Policy is set to None – No policy. On the home page. type http://www. click Yes. In the upper-right corner.com and then press ENTER. in the User name box. and then click OK. 6. 4. In the Anonymous Access Restrictions dialog box.com 1. verify that Sign In is displayed. click the Browse tab. in the Address bar. 2. Task 4: Test anonymous access to www. 5. Close all windows. 7. and then click Internet Explorer. In the Address bar. type CONTOSO\sp-farm and in the Password box.L6-4 Module 6: Planning Authentication 2. 5. point to All Programs. click System Account. in the upper-right corner. On the Error: Access Denied page. 4. In the Windows Internet Explorer dialog box. On the toolbar ribbon. and then click Save. This confirms that anonymous access is enabled. click Site Actions. In the Anonymous Access dialog box. and then close all Windows Internet Explorer® browser windows.com and then press ENTER. click Anonymous Access. and then click the Contoso Internet link.

Lab 7: Planning Managed Metadata L7-1 Module 7 Lab Answer Key: Planning Managed Metadata Contents: Exercise 1: Designing Content Types and a Term Set Framework Exercise 2: Creating the Managed Metadata Service Application Exercise 3: Importing Term Sets Exercise 4: Publishing a Content Type L7-2 L7-2 L7-4 L7-5 .

and then click Computer. Exercise 2: Creating the Managed Metadata Service Application Task 1: Create a site collection called CTHub on intranet.Solution. Log on to 10231A-NYC-DC1-07 as CONTOSO\Ed with the password Pa$$w0rd. Click Start. 2. Click Start. 3. . point to All Programs.L7-2 Module 7: Planning Managed Metadata Module 7: Planning Managed Metadata Lab 7: Planning Managed Metadata Exercise 1: Designing Content Types and a Term Set Framework Task 1: Read the supporting information 1. Under Application Management. Read the lab scenario. In the User Account Control dialog box. click Yes. double-click Managed Metadata Requirements. 4. move to the E:\Labfiles\Lab07\Starter folder. In Windows® Explorer.docx. 3.xlsx. Compare your solution to the sample solution located at E:\Labfiles\Lab07\Solution\MMS Planning Worksheet . 3.xlsx. double-click MMS Planning Worksheet. and then complete the Services and Content Types worksheets. and then click SharePoint 2010 Central Administration. and then read the additional requirements. 2. click Microsoft SharePoint 2010 Products. Task 2: Complete the Managed Metadata Planning worksheet 1.contoso. 2. Close all windows. In Windows Explorer. click Create site collections.com 1.

Scroll down to the bottom of the page. Press CTRL+T to open a new tab. and in the Content Type hub box. and in the Primary Site Collection Administrator section. Task 3: Verify that the Content Type Syndication Hub feature is active 1. Under Application Management.contoso. next to Managed Metadata Web Service. 7. 4. and then click OK. click New. 6. . In the toolbar ribbon. and then go to http://intranet. in the Name box. on the left menu. 5. type TermStore_Default Scroll down the page. and in the URL box. Scroll down the page. click Manage service applications. in the User name box.contoso. 9.Lab 7: Planning Managed Metadata L7-3 4. click OK. type CTHub and in the Description box. ensure that /sites/ is selected in the Choose a site prefix box. In the Service list. click Central Administration. type Contoso Content Type Hub In the Web Site Address section. Under System Settings. Task 2: Create a new Managed Metadata Service application to publish the CTHub site collection as the content type hub 1. 2. 8.com/sites/cthub. In the Use existing application pool list.com/sites/cthub and then click OK. click SharePoint Web Services Default. and in the Application Pool section. ensure that Team site is selected. click Manage services on server. in the Title box. 8. In the Title and Description section. type Managed Metadata Service Application In the Database Name box. and then click Managed Metadata Service. On the Top-Level Site Successfully Created page. 10. 5. click Use existing application pool. click Central Administration. type cthub In the Template Selection section. click Start. In the Create New Managed Metadata Service dialog box. type ed and click Check Names. On the left menu. type http://intranet. In Application Management. 7. 6. 3.

If required. browse to E:\Labfiles\Lab07\Starter. click Site collection features. 5. click the Contoso Sample Terms for Import – Cost Center. right-click the Contoso term set group. under TAXONOMY TERM STORE. In the Choose File to Upload dialog box. 2. . and then click Open. and then press ENTER.csv file. click Browse. In the left pane. click Browse. and then click Site Settings. 3. In the Properties pane. In the Term set import dialog box. click OK. 4. right-click the Contoso term set group. In Manage Service Applications. In the Term set import dialog box. In the Term Store Management Tool. In the Term set import dialog box. In the Choose File to Upload dialog box. click the Managed Metadata Service Application that you just created. type Contoso Terms and then click Save. 3. click the Contoso Sample Terms for Import – Department. Under Site Collection Administration. 5. verify that the Content Type Syndication Hub feature is Active. and then click Open. in the left pane. On the CTHub home page. in the Description box. Name the new term set group Contoso. On the Site Collection Features page. browse to E:\Labfiles\Lab07\Starter.csv file.L7-4 Module 7: Planning Managed Metadata 2. 6. 4. click Manage. 2. and on the ribbon. Task 2: Import the Cost Center and Department term files 1. click Activate. right-click Managed Metadata Service Application. 4. click Site Actions. and then click Import Term Set. and then click Import Term Set. Exercise 3: Importing Term Sets Task 1: Create a new term set group called Contoso 1. Close the Windows Internet Explorer® tab. 7. 3. In the left pane. and then click New Group.

7. 2.Lab 7: Planning Managed Metadata L7-5 8. In Site Content Types. In the Parent Content Type list.com/sites/cthub. click Document Content Types. in the URL box. Scroll up the page. . Exercise 4: Publishing a Content Type Task 1: Create a new site collection called Marketing 1. Under Put this site content type into.contoso. and then click OK. and then go to http://intranet. Under Settings. On the Top-Level Site Successfully Created page. and then click OK. type Contoso and then click OK. in the Title box. On the CTHub home page. type Marketing In the Web Site Address section. 9. Task 3: Publish the custom content type 1. 4. click Create site collections. 9. 2. 6. and in the Primary Site Collection Administrator section. type marketing Scroll down to the bottom of the page. 5. click Manage publishing for this content type. click New group. and in the box. 3. Task 2: Create a custom content type in the CTHub site collection 1. Under Galleries. 4. Under Application Management. 8. click OK. in the User name box. In the Name box. 3. click Site content types. In the Title and Description section. click Document. click Create. 5. 2. click Site Actions. type Marketing Document In the Description box. click OK. Ensure that Publish is selected. and then click Site Settings. type ed and click Check Names. In the Term set import dialog box. and then click the Central Administration link. Press CTRL+T to open a new tab. type Marketing Document In the Select parent content type from list.

4. Press CTRL+T to open a new tab. and then click OK. click Library Settings. On the left menu. and then click Content Type Hub. Click Run Now. click Contoso. Click Site Actions. In the Hubs section. click Yes. click Shared Documents. scroll down. Click Run Now.com/sites/marketing. click the Application Management tab. and then under Content Types. 3. 5. On the Add Content Types page.contoso. Scroll down the page. On the left menu. click Review job definitions. and then go to http://intranet. . On the ribbon. click Advanced settings. 2. 8.L7-6 Module 7: Planning Managed Metadata Task 4: Run timer jobs manually 1. 3. and then click Site Settings. click Add. Under Timer Jobs. 11. and then click OK. On the Document Library Settings page. 9. and then click OK. scroll down to the bottom of the page. In the Content Types section. 6. under Allow management of content types. 2. 13. and then click Monitoring. click Content type publishing. click Add from existing site content types. 6. 5. Click the Central Administration link. Task 5: Verify that the custom content type is available in the Marketing site 1. verify that Marketing Document is listed. Under Site Collection Administration. On the Library Tools tab. 7. In Windows Internet Explorer. and then click Content Type Subscriber – SharePoint 80. 4. under Select site content types from. 12. On the Library Tools tab. click Library. click Documents. under Subscribed Content Type. click Shared Documents. 10. 7. Scroll down the page. Under General Settings.

and then log off. and then verify that Marketing Document is now listed as a content type. Close all windows. . expand the New Document drop down. On the ribbon.Lab 7: Planning Managed Metadata L7-7 14. 15.

.

Lab 8: Planning Social Computing L8-1 Module 8 Lab Answer Key: Planning Social Computing Contents: Exercise 1: Planning User Profiles Exercise 2: Configuring User Profile Synchronization L8-2 L8-2 .

xlsx. and then read the document. 2. 2. In the Delegation of Control Wizard. Read the lab scenario. 3. double-click User Profile Requirements. Click Start. Log on to 10231A-NYC-DC1-08 as CONTOSO\Ed with the password Pa$$w0rd. Compare your solution to the sample solution located at E:\Labfiles\Lab08\Solution\User Profile Property Planning Worksheet Solution. on the Welcome to the Delegation of Control Wizard page. move to the E:\Labfiles\Lab08\Starter folder. 4. Task 2: Complete the User Profile Property Planning worksheet 1.L8-2 Module 8: Planning Social Computing Module 8: Planning Social Computing Lab 8: Planning Social Computing Exercise 1: Planning User Profiles Task 1: Read the supporting information 1. On the Users or Groups page. 3. Click Start. and then click Computer. and then click Active Directory Users and Computers. Close all windows.xlsx. In Windows Explorer. point to Administrative Tools.docx.com. click Add. double-click User Profile Property Planning Worksheet. Exercise 2: Configuring User Profile Synchronization Task 1: Configure Active Directory permission for synchronization 1. . 2. 3. Right-click Contoso. In Windows® Explorer. click Next. and then complete the worksheet. and then click Delegate Control. 4.

Task 2: Create a synchronization connection and a connection filter 1. On the Tasks to Delegate page. 6. and in the Account name box. Under Synchronization. point to All Programs. type Contoso Scroll down the page. type contoso\sp-farm and in the Password and Confirm password boxes.Lab 8: Planning Social Computing L8-3 5. 5. Double-click Neil Charney. on the Account tab. 6. or Groups dialog box. 4. Under Application Management. 12. and then close Active Directory Users and Computers. In the Connection Name box. 2. type sp-farm and click Check Names. 11. 7. scroll down the list. click Create a custom task to delegate. and then click SharePoint 2010 Central Administration. 9. click Manage. type Contoso and in the Forest name box. and then click Populate Containers. click Manage service applications. Expand Contoso. . On the ribbon. type Pa$$w0rd 10. On the Active Directory Object Type page. 8. Click User Profile Service Application. Click Cancel. In the Neil Charney Properties dialog box. and then click OK. and then click Next. Computers. On the Permissions page. Click Create New Connection. on the Service Applications tab. Click Start. ensure that General is selected. under Account options. scroll down. 10. click Next. 9. 7. click Yes. On the Users or Groups page. 14. In the User Account Control dialog box. Scroll down to the bottom of the page. 3. On the Completing the Delegation of Control Wizard page. and then click the Production Organizational Unit. In the Select Users. click Next.com. select the Replicating Directory Changes check box. click Configure Synchronization Connections. click Finish. click Microsoft SharePoint 2010 Products. 13. in the Enter the object names to select box. 8. and then verify that the Account is disabled check box is selected. and then click Next.

12. In the Operator list. In the Exclusion Filter for Users section. and then click OK. When it has completed. Task 4: Confirm the user profile synchronization by checking that the Ed Meadows and Adam Carter profiles were imported and that the Neil Charney profile was not imported 1. Refresh the page until the Profile Synchronization Status changes to Idle. Click User Profile Service Application. On the Synchronization Connections page. click Contoso. click Manage service applications. 6. Scroll down to the bottom of the page. Note: This process can take several minutes to complete.L8-4 Module 8: Planning Social Computing 11. Close the report. Expand CONTOSO. 14. In the left menu. 13. Under Synchronization. click userAccountControl. click Start Profile Synchronization. type ed and then click Find. Refresh the page until the Profile Synchronization Status changes to Synchronizing. and then click OK. 2. 8. 5. in the Attribute list. Task 3: Run the user profile import 1. click Manage User Profiles. 9. . Marketing. click Application Management. click Bit on equals. 3. Click Start Full Synchronization. and then click Edit Connection Filters. In the Find profiles box. type 2 and then click Add. select the IT. In the Filter box. 7. 15. click Idle to view the synchronization report. Under People. and then click OK. 2. 4. and Production check boxes. 16. Under Service Applications.

and then click My Site. Click My Profile. 6. On the Manage User Profiles page. This confirms that the profile for the disabled user account for Neil Charney was not imported. 5. on the upper right. 3. Scroll down the page to view his profile information. In the Find profiles box.Lab 8: Planning Social Computing L8-5 3. Click Contoso\Ed. 7. and then click Cancel and Go Back. in the user box. type Pa$$w0rd. Click Contoso\Adam. 9. Task 5: Provision Ed Meadows’ My Site Web site 1. In the Find profiles box. and then click Edit My Profile. . In the dialog box. type adam and then click Find. and then click Cancel and Go Back. click Ed Meadows. and then click OK. and then log off. type Ed and in the password box. 2. 4. type neil and then click Find. Click My Content. Close all windows. Scroll down the page to view his profile information. 4. 8. Verify that no results are displayed. 5. and then click Edit My Profile.

.

Lab 9: Designing an Enterprise Search Strategy L9-1 Module 9 Lab Answer Key: Designing an Enterprise Search Strategy Contents: Exercise 1: Planning for Search Exercise 2: Planning Physical Topology Exercise 3: Creating Search Service Applications Exercise 4: Configuring Search L9-2 L9-3 L9-4 L9-4 .

.xlsx.xlsx.Solution. and then complete the worksheet. double-click SharePoint 2010 Service Applications Planning Worksheet. 2. 2. 2. In Windows Explorer. and then click Computer.L9-2 Module 9: Designing an Enterprise Search Strategy Module 9: Designing an Enterprise Search Strategy Lab 9: Designing an Enterprise Search Strategy Exercise 1: Planning for Search Task 1: Read the supporting information 1. double-click Logical Architecture Planning Worksheet. Compare your solution to the sample solution located at E:\Labfiles\Lab09\Solution\SharePoint 2010 Service Applications Planning Worksheet . Task 2: Update the Logical Architecture Planning worksheet 1. 3. Log on to 10231A-NYC-DC1-09 as CONTOSO\Ed with the password Pa$$w0rd. In Windows Explorer. Read the lab scenario.xlsx. Click Start. Task 3: Update the SharePoint 2010 Service Applications Planning worksheet 1. 4. move to the E:\Labfiles\Lab09\Starter folder.docx. Compare your solution to the sample solution located at E:\Labfiles\Lab09\Solution\Logical Architecture Planning Worksheet Solution. and then complete the worksheet. In Windows® Explorer. and then read the additional requirements. double-click Contoso Search Requirements.xlsx.

Lab 9: Designing an Enterprise Search Strategy L9-3 Task 4: Update the Physical Architecture Planning worksheet 1. double-click Physical Architecture Diagram. and then complete the worksheet. Task 6: Complete the SharePoint 2010 Search Planning worksheet 1. Exercise 2: Planning Physical Topology Task 1: Plan the physical topology for search 1. doubleclick Physical Architecture Planning Worksheet. double-click SharePoint 2010 Search Planning Worksheet. 4.xlsx.vsd.Solution.xlsx. Compare your solution to the sample solution located at E:\Labfiles\Lab09\Solution\Physical Architecture Diagram . In Windows Explorer.xlsx. 2. 2. In Windows Explorer.xlsx. 2.xlsx. move to the E:\Labfiles\Lab09\Starter folder. In Windows Explorer. and then complete the worksheet.vsd. 3. In Windows Explorer. and then complete the worksheet. Compare your solution to the sample solution located at E:\Labfiles\Lab09\Solution\SharePoint 2010 Search Planning Worksheet Solution. Close all windows. double-click Physical Architecture Planning Worksheet. Task 5: Update the SharePoint 2010 Security Planning worksheet 1.xlsx.xlsx. In Windows Explorer. and then read the information. Compare your solution to the sample solution located at E:\Labfiles\Lab09\Solution\SharePoint 2010 Security Planning Worksheet Solution. Compare your solution to the sample solution located at E:\Labfiles\Lab09\Solution\Physical Architecture Planning Worksheet Solution. 2. . and then complete the diagram. double-click SharePoint 2010 Security Planning Worksheet.

click Manage service applications. Click Start. select SearchAdminAppPool. 9. click Application Management. Exercise 4: Configuring Search Task 1: Remove people searching from the default content source. 8. click Microsoft SharePoint 2010 Products. and run a full crawl 1. 2. in the Search Service Account list. click Central Administration. Click the Search Service Application 1 link. and on the left menu. Under Service Applications. configure the crawl schedule according to your plan. Under Application Management. click Use existing application pool. Under System Settings. 4. click Manage services on server. and from the list. 7. In the User Account Control dialog box. and then click SharePoint 2010 Central Administration. click Manage service applications. select SearchQueryAppPool. Task 2: Ensure that the SharePoint Server Search service is started 1. 6. Scroll down the page. In the Application Pool for Search Admin Web Service section. Click New.L9-4 Module 9: Designing an Enterprise Search Strategy Exercise 3: Creating Search Service Applications Task 1: Create the search service application 1. 3. point to All Programs. click Use existing application pool. . click CONTOSO\sp-serviceapp-search. 2. and then click Search Service Application. In the Create New Search Service Application dialog box. click Yes. 5. In the Application Pool for Search Query and Site Settings Web Service section. On the left menu. and from the list. 4. Click OK to close the Create New Search Service Application window. and verify that the SharePoint Server Search service is started. Scroll back up the page. 2. Click OK to close the Manage Search Topology window. 3.

click Create schedule. Under Incremental Crawl. and run a full crawl 1.com 6. 7. In the Manage Schedules dialog box. in the Every box. 6. In the Manage Schedules dialog box. and then click OK. In the Manage Schedules dialog box. click Create schedule. 9. click Content Sources. 3. 2. type People In the Start Addresses box. .Lab 9: Designing an Enterprise Search Strategy L9-5 3. click Weekly. select the Saturday check box. Click New Content Source. 4. Task 2: Create a new content source for People Search. select the Saturday check box. click Create schedule. select the Start full crawl of this content source check box. select the Repeat within the day check box.contoso. 10.contoso. Under Incremental Crawl. type 60 and then click OK. under Settings. Scroll down to the bottom of the page.com sps3://my. 8. select the Repeat within the day check box. configure the crawl schedule according to your plan. under Settings. and then under Full Crawl. and then click Edit.contoso. 8.contoso. click Weekly. Right-click Local SharePoint sites. select the Start full crawl of this content source check box. add the following addresses: • • 4. In the Name box. 5. In the Start Full Crawl section. In the Manage Schedules dialog box. click 3:00 AM.com Scroll down to the bottom of the page. in the Every box. On the left menu. and then under Full Crawl. type 60 and then click OK. In the Start Addresses section. in the Starting time list. 5.com sps3://intranet. click Create schedule. and then click OK. and then click OK. and then click OK. http://my. delete the following entries from the list: • • http://my. 7. In the Start Full Crawl section.

and then click OK. 6. 4. 6. next to http://intranet. and then click Enterprise Search Center. 3. type searchcenter Under Select a template. and then click OK. In the Start Full Crawl section. click File Shares. In the Primary Site Collection Administrator section. On the Top-Level Site Successfully Created page. 5. 9. in the User name box. click Create schedule. 7. In the Manage Schedules dialog box. Click Refresh to see the status of the three crawls. Under Application Management. type \\nyc-dc1\fileshare Scroll down to the bottom of the page.com. In the Manage Schedules dialog box. click Weekly. click the Enterprise tab. click OK. type Search Center In the Web Site Address section. select all of the month check boxes. 8. and in the Start Addresses box. and then click OK. 2. 7. and run a full crawl 1. select the Sunday check box.contoso. in the list. and then click OK. and then in the text box. click /sites/. Under Incremental Crawl. 3. configure the crawl schedule according to your plan. 4. type ed Click the Check Names icon. select the Start full crawl of this content source check box. 8. . Click the Central Administration link. Task 4: Create an enterprise search center site collection and search for a user and a file 1. Click New Content Source. type File Shares In the Content Source Type section. click Create schedule. click Monthly. In the Title box.L9-6 Module 9: Designing an Enterprise Search Strategy Task 3: Create a new content source for a file shares search. click Create site collections. In the Name box. 5. 2. and under Full Crawl.

On the Search Results page. type ed and then click the Search icon.com/sites/searchcenter. Above the search box. a people match for Ed Meadows.Lab 9: Designing an Enterprise Search Strategy L9-7 9. click People. Press CTRL+T to open a new tab. 12. 10. . verify that you can see a document called Microsoft SharePoint 2010 IT Professional Evaluation Guide. and then navigate to http://intranet. and then verify that Ed Meadows is displayed. In the search box. Close all windows and log off.contoso. 11. 13. and on the right side of the page.

.

Lab 10: Planning Enterprise Content Management L10-1 Module 10 Lab Answer Key: Planning Enterprise Content Management Contents: Exercise 1: Developing a Content Management Plan Exercise 2: Enabling and Configuring Document IDs and Content Organizer Exercise 3: Configuring Retention Policies and Records Management L10-2 L10-6 L10-2 .

4. Close all windows. Navigate to the intranet. and then click Internet Explorer. Log on to 10231A-NYC-DC1-10 as CONTOSO\Ed with the password Pa$$w0rd. Task 2: Complete the SharePoint 2010 ECM Planning worksheet 1. and then click Computer. Compare your solution to the sample solution located at E:\Labfiles\Lab10\Solution\SharePoint 2010 ECM Planning Worksheet Solution. . 2.xlsx. 3. 3.xlsx. move to the E:\Labfiles\Lab10\Starter folder. Click Start. Read the lab scenario. and then complete the worksheet. double-click ECM Business Requirements. double-click SharePoint 2010 ECM Planning Worksheet.com/sites/docs home page. Click Start. In Windows® Explorer.contoso.docx. In Windows Explorer. 2.L10-2 Module 10: Planning Enterprise Content Management Module 10: Planning Enterprise Content Management Lab 10: Planning Enterprise Content Management Exercise 1: Developing a Content Management Plan Task 1: Read the supporting information 1. point to All Programs. Exercise 2: Enabling and Configuring Document IDs and Content Organizer Task 1: Activate document IDs and reset all document IDs to use the same prefix 1. and then read the requirements document.

check Allow rules to specify another site as a target location. Under Site Collection Administration. 10. click Content Organizer Settings. Under Site Actions. and then click Site Settings. verify that Assign Document IDs is selected. Under Sending to Another Site. In the address box. Content Organizer Settings Content Organizer Rules Select Content Organizer Settings.contoso. Under Site Collection Administration. click Site collection features. and then click OK. . 8. click Manage site features. Under Site Administration. type intranet. 6.com/sites/hrdocs and then press ENTER. 9. 3. Next to Content Organizer. Click Site Actions. 5. click Activate. Click the Site Settings breadcrumb link. click Document ID settings. Task 2: Activate and configure the Content Organizer feature 1. 5. Click the Site Settings link. click Activate. Next to Content Organizer. and then verify that the following two new settings appear under Site Administration: • • 4. Next to Document ID Service. click Activate. and then change the prefix to CONTOSO. Under Site Actions. and then click OK.Lab 10: Planning Enterprise Content Management L10-3 2. Click Site Actions. and then click Site Settings. 6. and then verify that the following two new settings appear under Site Administration: • • Content Organizer Settings Content Organizer Rules 11. 3. 4. click Manage site features. 2. Select the Reset all Document IDs in this Site Collection to begin with these characters check box. and then click the Site Collection Administration breadcrumb link. 7.

and then click OK. 2. click Contoso Content Types. 2. and then click Paste to paste the URL that you copied previously into the box. 4.) Click Add Connection. type intranet. 7. On the left menu. click Yes. point to All Programs. 13. right-click it. in the Display name box. type HR Docs Content Organizer Right-click in the Send To URL box. 5. under the Rule Name section. Task 4: Create a new Content Organizer rule 1. 6. and then click Site Settings. 5. Under Submission Points. type Move Contoso Document items to HR Docs Under Content type. and then click OK. Click Add new item. under Send To Connections. Under External Service Connections. click Microsoft SharePoint 2010 Products and then click SharePoint 2010 Central Administration. In the address box. click Content Organizer Rules. Close the Central Administration window. click General Application Settings.contoso. 3. scroll up. 8. Under Connection Settings. in the Group list. 3. in the Name box. Under Site Administration. verify that the new connection is listed. In the User Account Control dialog box. 4. Task 3: Create a new Send To connection 1. click Configure send to connections. 7. . In the Content Organizer Rules: New Rule dialog box. (Delete any spaces at the end of the URL. In the Type list. click Copy. select the Create subfolders after a target location has too many items check box. Click Start. Under Folder Partitioning. click Contoso Document. 6. highlight the Web service URL entry.L10-4 Module 10: Planning Enterprise Content Management 12.com/sites/docs and then press ENTER. Click Site Actions.

In the left navigation menu. In the Choose File to Upload dialog box. click Save to save it. Double-click the document icon to open it. Name the document Non-HR Doc. click Save to save it. and then click OK.Lab 10: Planning Enterprise Content Management L10-5 8. 8. click Browse. 14. click the Internet Explorer icon to restore the window. Minimize the Windows Internet Explorer® window. verify the message Saved to final location is displayed. click Contoso Department. type HR. In the Drop Off Library: HR Doc dialog box. select HR 10. 19. 7. and then click Text Document. in the Property list. and then press ENTER. Right-click the desktop again. In the document.txt. In the Notepad dialog box. In the Submit Document dialog box. 9. point to New. 12. click the HR Doc. Right-click the desktop. click Another content organizer in a different site. and in the Value box.HR Doc.txt document. In the Drop Off Library . Click Add document. 6. and then click Submit. and then click Text Document. In the Submit Document dialog box. in the Expiration box type an appropriate date. . under Libraries. Under Target Location. On the taskbar. 5. click Drop Off Library. 17. In the document. and then click Open.txt. type HR Doc test and then close the document. 9. type HR Doc and in the Contoso Department box. 11. Name the document HR Doc. 3. 18. Double-click the document icon to open it. 13. and then click OK. 10. In the Conditions section. Verify that the Operator is set to is equal to. 16. type Non-HR Doc test and then close the document.txt dialog box. 2. click OK. 4. under Property-based conditions. and then press ENTER. in the Title box. point to New. In the Notepad dialog box. 15. select HR Docs Content Organizer. Task 5: Test the new Content Organizer rule 1.

point to All Programs. select the Enable Retention check box.com/sites/docs home page.txt document. click Drop Off Library. 2. type Marketing. 23. . and then click Submit. and then click Internet Explorer to go to the intranet. under Event. Under Contoso Content Types. type intranet. Verify that the Non-HR Doc document is listed in this drop off library.L10-6 Module 10: Planning Enterprise Content Management 20. In the Drop Off Library: Non-HR Doc dialog box. 27. In the address box. in the Title box. 4. click Site content types. 3. 7. in the Expiration box type an appropriate date. Under Retention. Under Galleries. 21. Click Add document. In the Submit Document dialog box. click OK. In the Drop Off Library . Click Site Actions. and then click Open. In the Submit Document dialog box. In the Stage properties . 5. click Expiration. 22. and then click OK. 6. Click Start. and then click Add a retention stage. 26.txt dialog box.Non-HR Doc..Webpage Dialog dialog box. 25.com/sites/hrdocs and then press ENTER. Exercise 3: Configuring Retention Policies and Records Management Task 1: Configure information management policy settings for document retention on a content type 1. and then click Site Settings. click Information management policy settings. 24. type Non-HR Doc and in the Contoso Department box.contoso. click Browse. and then type 0 for the number of years. verify the message Moved to Drop Off Library is displayed. 30. click Contoso Document. click the Non-HR Doc. 29. Verify that the HR Doc document is listed in this drop off library. in the Time Period list. Under Settings. Close all windows. In the Choose File to Upload dialog box. 28.contoso. Under Libraries.

click Available in all locations by default. in the Time Period list. click Permanently Delete. click Activate. 12. and then click Close. 6. Under Action.Webpage Dialog dialog box. . click OK. In the Compliance Details – Non-HR Doc . Next to In Place Records Management. under Event. Click the Site Settings link. and then click OK. In the Message from webpage dialog box. and then log off. 7. click OK. 11. click Site collection features. Under Action. On the Edit Policy page. 10.Lab 10: Planning Enterprise Content Management L10-7 8. ensure that Move to Recycle Bin is selected. and then click OK. 8. 2. verify that this document is now declared as a record.-Webpage Dialog dialog box. Close all windows.Webpage Dialog dialog box. Click the Site Collection Administration link. 9. 4. and then click OK. click Expiration. 9. click Record declaration settings. click Drop Off Library. 12. Under Site Collection Administration. and then type 3 for the number of years. Under Libraries. Under Site Collection Administration.. Under Record Declaration Availability. Position the cursor over the Non-HR Doc document. and then click Compliance Details.. In the Compliance Details – Non-HR Doc . click Declare as a record. click the drop-down arrow. 10. In the Stage properties . Click Add a retention stage. 3. 5. 11. Task 2: Activate and configure the In Place Records Management feature 1.

.

Lab 11: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy L11-1 Module 11 Lab Answer Key: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy Contents: Exercise 1: Planning the SharePoint Business Intelligence Implementation Exercise 2: Creating a BI Center and Enabling Excel Services L11-2 L11-3 .

In Windows® Explorer. Close all windows. Compare your solution to the sample solution located at E:\Labfiles\Lab11\Solution\Business Intelligence Planning Worksheet Solution. Read the lab scenario. double-click Business Intelligence Planning Worksheet. Task 2: Complete the Business Intelligence Planning worksheet 1.L11-2 Module 11: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy Module 11: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy Lab 11: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy Exercise 1: Planning the SharePoint Business Intelligence Implementation Task 1: Read the supporting information 1. and then read the requirements document. and then complete the worksheet. Log on to 10231A-NYC-DC1-11 as CONTOSO\Ed with the password Pa$$w0rd. In Windows Explorer. 2. double-click Contoso Business Requirements. 4.xlsx. 3.xlsx. and then click Computer. Click Start. 2. . 3. move to the E:\Labfiles\Lab11\Starter folder.docx.

5. Task 2: Create a new BI Center site collection and test the Excel Services application 1. In the Service list. In the Primary Site Collection Administrator section. in the Name box. In the User Account Control dialog box. 6. click Create site collections. In the Create New Excel Services Application dialog box. under the Title box. Under System Settings. 9. under Select a template. type BI Center In the Website Address section. click Manage services on server. . click Yes. click Business Intelligence Center. Under Application Management. type Excel Services 10231A In the Application Pool section. under the second URL list box. type ExcelServicesAppPool In the Configurable list. click CONTOSO\sp-serviceapp.Lab 11: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy L11-3 Exercise 2: Creating a BI Center and Enabling Excel Services Task 1: Create an Excel Services application and start the Excel Calculation Services service 1. under Create new application pool. in the User name box. 2. 6. next to http://intranet. Click New. Click Start. 10. 3. click Microsoft SharePoint 2010 Products and then click SharePoint 2010 Central Administration. 7. type ed Click Check Names. click Manage service applications. 3. point to All Programs. On the left menu. On the left menu. 8. click the Central Administration link. 2. and then click OK. 5. click Start. in the Application pool name box. on the Enterprise tab. In the Title and Description section. click the Central Administration link. Under Application Management. type BICenter In the Template section. 4. and then click Excel Services Application. 7. and then click OK.contoso. 4.com/sites/. next to Excel Calculation Services.

Under Document Libraries.L11-4 Module 11: Planning a SharePoint 2010 Implementation of a Business Intelligence Strategy 8. 14. 11. 12. 13.xslx opens in the browser window. and then log off. click the drop-down arrow. click Libraries. click Documents. 10.com/sites/BICenter link.contoso. Close all windows. On the left menu. 9. Move the mouse pointer over Excel Services Sample Workbook. . On the Top-Level Site Successfully Created page. and then click View in Browser. Verify that the Excel® Services Sample workbook. Maximize the BI Center window. click the http://intranet.

Lab 12: Developing a Plan for Governance L12-1 Module 12 Lab Answer Key: Developing a Plan for Governance Contents: Exercise 1: Creating a Governance Plan Exercise 2: Implementing the Governance Plan L12-2 L12-2 .

2. 3. and then complete the worksheet. Exercise 2: Implementing the Governance Plan Task 1: Enable self-service site creation on the SharePoint Team Web application 1.L12-2 Module 12: Developing a Plan for Governance Module 12: Developing a Plan for Governance Lab 12: Developing a Plan for Governance Exercise 1: Creating a Governance Plan Task 1: Read the supporting information 1. In the User Account Control dialog box. point to All Programs. and then click Computer. Log on to 10231A-NYC-DC1-12 as CONTOSO\Ed with the password Pa$$w0rd. 3. click Microsoft SharePoint 2010 Products and then click SharePoint 2010 Central Administration.xlsx. 2. Read the lab scenario. Under Application Management. click Manage web applications. Compare your solution to the sample solution located at E:\Labfiles\Lab12\Solution\SharePoint 2010 Governance Worksheet Solution. Task 2: Complete the SharePoint 2010 Governance worksheet 1. In Windows Explorer. Click Start. Click Start. 4. Close all windows. . 2. move to the E:\Labfiles\Lab12\Starter folder.docx. 3. click Yes. In Windows® Explorer. and then read the requirements document. double-click Contoso Provisioning and Customization Requirements.xlsx. double-click SharePoint 2010 Governance Worksheet.

click Self-Service Site Creation. click the drop-down arrow. In the Service list. Task 5: Configure the site storage individual quota limit for the SharePoint Team site 1. under Central Administration. click Manage services on server. clear the Enable SharePoint Designer check box. Task 4: Configure load balancing for sandboxed solutions in the farm 1. and then on the ribbon. . 2. next to Microsoft SharePoint Foundation Sandboxed Code Service. and then click SharePoint Designer. 5. click the System Settings link. click On. click Start. and then click OK. Click the SharePoint Team Web application. In the Self-Service Site Collection Management dialog box. Task 2: Disable SharePoint Designer for the SharePoint Team Web application 1. On the left menu. In the SharePoint Designer Settings dialog box. 3. Click the SharePoint Team Web application. 2. and then click OK. On the left menu. Task 3: Start the Microsoft SharePoint Foundation Sandboxed Code service 1. Under Farm Management. under Central Administration. under Central Administration. verify that Requests to run sandboxed code are routed by solution affinity is selected. and then click OK. under General Settings. On the left menu. 3. click Manage user solutions. Under Servers. Scroll down. click the System Settings link. 2. 3.Lab 12: Developing a Plan for Governance L12-3 4. On the ribbon. click the Application Management link.

click the Web Application list. 8. scroll down to the bottom of the page. . In the Select Web Application dialog box. In the Select Site Collection dialog box. 5. click Cancel. 5. In the address bar. type 1000 and then click OK.com and then press ENTER. Click Site Actions. and then click Change Web Application.com 1. select the Limit site storage check box. 4.contoso. Under Site Collections. 7. In the Solutions tab of the SharePoint ribbon. Close all windows. click Upload Solution. click Configure quotas and locks. 3. click OK. and then click Site Settings. 6. 7. This confirms that you can upload sandboxed solutions. click SharePoint Team. 2. Click the Solutions tab. and then click Change Site Collection. and then log off. In the Select Site Collection dialog box. 4. in the text box. Click the Site Collection list.L12-4 Module 12: Developing a Plan for Governance 2 3.contoso. In the Site Quota Information section. click Solutions. Under Galleries. Task 6: Verify that users can upload sandboxed solutions in team. In the Upload Document dialog box. type http://team. On the Site Collection Quotas and Locks page. 6.

Lab 13: Designing a Maintenance and Monitoring Plan L13-1 Module 13 Lab Answer Key: Designing a Maintenance and Monitoring Plan Contents: Exercise 1: Resolving an Error in SharePoint 2010 Exercise 2: Splitting a Content Database L13-2 L13-4 .

2. and then click SharePoint 2010 Central Administration. In Windows® Explorer. Under Application Management. 3. 6. 4. In the User Account Control dialog box. Click User Profile Service Application. Verify that you receive an error. Error Resolution Operational Procedures. Task 2: Document the steps for resolving an error in SharePoint 2010 1. 2. and then click Computer. 3. Log on to 10231A-NYC-DC1-13 as CONTOSO\Ed with the password Pa$$w0rd. 4. On the desktop. click Yes. point to All Programs.exe. Read the lab scenario. point to Open From. Click Start. On the File menu. move to the E:\Labfiles\Lab13\Starter folder. Document your steps for resolving an error in Microsoft® SharePoint 2010® by using a correlation ID. double-click UlsViewer. Click Start.docx. and then click ULS. 7. Compare your steps to the steps in Task 3 of this exercise. . 2. 5. click Microsoft SharePoint 2010 Products.L13-2 Module 13: Designing a Maintenance and Monitoring Plan Module 13: Designing a Maintenance and Monitoring Plan Lab 13: Designing a Maintenance and Monitoring Plan Exercise 1: Resolving an Error in SharePoint 2010 Task 1: Read the supporting information 1. Task 3: Identify an error in SharePoint 2010 1. and then double-click Contoso Ltd. click Manage service applications.

In the Setup the ULS Runtime feed dialog box. 18. right-click Command Prompt. Switch back to Windows Internet Explorer®. and then increase the width of the Message column. 3. In ULS Viewer.. and then click Go back to site. so that you can read it more easily. At the command prompt. 19. click Manage services on server. Scroll down to the bottom of the page. paste in the correlation ID characters that you copied previously. Read the message to determine what might be the cause of the problem: "This User Profile Application's connection is currently not available. 20. 15. After the service has started. point to All Programs. Under System Settings. This will then display the message in the top pane of the window." Task 4: Resolve the error 1. 16. in the drop-down list. Switch back to ULS Viewer. and then click Run as administrator. and in the Service list. scroll across to the rightmost side of the window. click Start. In the Filter by dialog box. 5.. 12. and then click Go back to site. next to User Profile Service. click Yes. type iisreset and then press ENTER. The Application Pool or User Profile Service may not have been started. In the list. and then click OK. In the Value box. click Filter. 10.Lab 13: Designing a Maintenance and Monitoring Plan L13-3 8. Copy the first eight characters of the correlation ID. On the toolbar. 4. 2. under Field. . 17. Switch back to the Error – Windows Internet Explorer window. click Accessories. Verify that you receive an error. 13. Under Application Management. 11. click Start. click the log entry that is second from the bottom. click Manage service applications. Click User Profile Service Application. 14. In the User Account Control dialog box. click Correlation. 6. 9. click OK.

docx.L13-4 Module 13: Designing a Maintenance and Monitoring Plan 7. Task 2: Split the content database. Log on to 10231A-NYC-DC1-13 as CONTOSO\sp-farm with the password Pa$$w0rd Click Start. and then click Run as Administrator. and then click SharePoint 2010 Central Administration. click Start. Content_Docs1 1. 5. Document your steps for splitting a content database with multiple site collections into multiple content databases. 4. 6. Click Application Management. 11. Compare your steps to the steps in Task 2 of this exercise. Exercise 2: Splitting a Content Database Task 1: Document the steps for splitting a content database 1. point to All Programs. Content Database Operational Procedures. and then click Log off. 3. Under Site Collections. point to All Programs. 3. Click Start. 9. click View all site collections. and then double-click Contoso Ltd. Click /sites/hrdocs. on the left menu. 4. move to the E:\Labfiles\Lab13\Starter folder. Verify that you can now manage this service. In the Services on Server window. 2. right-click on SharePoint 2010 Management Shell. Click User Profile Service Application. click Yes. Under Service Applications. 5. Click Start. In Windows Explorer. Close all open windows. verify that the Database Name is Content_Docs1. 8. click Microsoft SharePoint 2010 Products. close the Command Prompt window. click Manage service applications. 12. click Microsoft SharePoint 2010 Products. 2. click Application Management. 10. and then click OK. . When IIS restarts. and then click Computer. In the User Account Control dialog box.

type the command in the following code example. and then press ENTER. Click /sites/hrdocs. and then under Site Collections.com/sites/hrdocs DestinationDatabase content_docs2 9. This confirms that you have moved the database to another database. 10. Click OK. click Yes. 8. Switch back to the Application Management window. Close all windows. 13. 11. type iisreset and then press ENTER. type Y and then press ENTER. Move–SPSite –Identity http://intranet. At the administrator Windows PowerShell™ prompt.contoso. click View all site collections. and then verify that the Database Name is now Content_Docs2. 12. At the confirmation prompt. .Lab 13: Designing a Maintenance and Monitoring Plan L13-5 7. In the User Account Control dialog box. and then log off. At the confirmation prompt.

.

Lab 14: Planning Business Continuity L14-1 Module 14 Lab Answer Key: Planning Business Continuity Contents: Exercise 1: Creating a Backup and Restore Plan Exercise 2: Testing the Recovery Process L14-2 L14-2 .

Click Start. Under Application Management. Compare your solution to the sample solution located at E:\Labfiles\Lab14\Solution\SharePoint 2010 Backup and Restore Planning Worksheet . In Windows Explorer. double-click Contoso Ltd.Solution. Read the lab scenario. click Yes. Business Continuity Requirements. Log on to 10231A-NYC-DC1-14 as CONTOSO\Ed with the password Pa$$w0rd. 3.L14-2 Module 14: Planning Business Continuity Module 14: Planning Business Continuity Lab 14: Planning Business Continuity Exercise 1: Creating a Backup and Restore Plan Task 1: Read the supporting information 1. Exercise 2: Testing the Recovery Process Task 1: Verify that a service application is missing 1. In Windows® Explorer. and then complete the worksheet. 4. 2. and then click Computer. 2. 3.xlsx.xlsx. In the User Account Control dialog box. Click Start. Close all windows. and then read the requirements document. 3. Task 2: Complete the SharePoint 2010 Backup and Restore Planning worksheet 1. point to All Programs. click Manage service applications. . double-click SharePoint 2010 Backup and Restore Planning Worksheet. move to the E:\Labfiles\Lab14\Starter folder. 2.docx. click Microsoft SharePoint 2010 Products and then click SharePoint 2010 Central Administration.

Lab 14: Planning Business Continuity L14-3 4. Under Farm Backup and Restore. and then click Next. click the item dated 7/27/2010. 11. in the Password box. expand Shared Services Proxies. 3. Wait for a couple of minutes. Scroll down to the bottom of the page. under Type of restore. 2. and under Shared Services. and then verify the User Profile Service Application does not exist. in the Select column. In the Restore Options section. On the left menu. 6. click OK. In the list of backup jobs. 3. 2. click Same configuration. under User Profile Service. click the top item dated 7/27/2010. under Type of restore. In the backup jobs. Task 2: Restore a missing service application 1. click Restore from a backup. and under Shared Services. in the Select column. and then click Next. on the left menu. and then click Next. click Same configuration. expand Shared Services Applications. click Backup and Restore. 9. select the User Profile Service Application check box. Scroll down to the bottom of the page. Task 3: Restore a missing service application proxy 1. Under Farm Backup and Restore. 8. 4. and then click Next. and then click Start Restore. In the Message from webpage dialog box. When the Phase status changes to Completed. click Backup and Restore. Scroll down to the bottom of the page. 7. . 4. and then click Refresh. 5. select the User Profile Service Application check box. In the Login Names and Passwords section. Scroll down to the bottom of the page. 10. click Restore from a backup. In the Restore Options section. 5. Scroll down the page. type Pa$$w0rd Scroll down to the bottom of the page.

on the left menu. 9. and then log off. Under Service Applications. Scroll down the page. click Application Management. click Manage service applications. 4. Wait for a couple of minutes. and then click Refresh. 2. Task 4: Confirm that you have restored the missing service application and service application proxy 1. . 7. Click the User Profile Service Application link. 3.L14-4 Module 14: Planning Business Continuity 6. and then click Start Restore. click OK. and then verify that you can locate the User Profile Service Application and the User Profile Service Application Proxy. When the Phase status changes to Completed. In the Message from webpage dialog box. Close all windows. Scroll down to the bottom of the page. 8.

Lab: Planning for Upgrading to SharePoint 2010 L15-1 Module 15 Lab Answer Key: Planning for Upgrading to SharePoint 2010 Contents: Exercise 1: Creating an Upgrade and Migration Plan L15-1 .

3. Read the lab scenario.Solution.xlsx. and then click Computer. 2. move to the E:\Labfiles\Lab15\Starter folder. Click Start. . and then complete the worksheet. Compare your solution to the sample solution located at E:\Labfiles\Lab15\Solution\Upgrade Planning Worksheet . Task 2: Complete the Upgrade Planning worksheet 1. 2. double-click Upgrade Planning Worksheet. Log on to 10231A-NYC-DC1-15 as CONTOSO\Ed with the password Pa$$w0rd.xlsx.L15-2 Module 15: Planning for Upgrading to SharePoint 2010 Module 15: Planning for Upgrading to SharePoint 2010 Lab: Planning for Upgrading to SharePoint 2010 Exercise 1: Creating an Upgrade and Migration Plan Task 1: Read the supporting information 1. In Windows® Explorer.