Creative Bloq | Your daily dose of design tips and inspiration | Creative Bloq.
Author: escapebusinesssolutions
Upgrading to Microsoft SharePoint Foundation 2010

-
Upgrading to
Microsoft SharePoint Foundation 2010
Microsoft Corporation
Published: November 2010
Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com)
- Abstract
This book is designed to guide administrators and IT professionals through the process of upgrading to Microsoft SharePoint Foundation 2010 from Windows SharePoint Services 3.0.
The content in this book is a copy of selected content in the SharePoint Foundation 2010 technical library (http://go.microsoft.com/fwlink/?LinkId=181463) as of the publication date. For the most current content, see the technical library on the Web.

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
© 2010 Microsoft Corporation. All rights reserved.
Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
Contents
Upgrading to SharePoint Foundation 2010 1
About the upgrade process (SharePoint Foundation 2010) 3
What’s new in upgrade (SharePoint Foundation 2010) 4
Hardware requirement: 64-bit 4
Operating system requirement: Windows Server 2008 or Windows Server 2008 R2 5
Database requirement: 64-bit SQL Server 2005 SP3 or SQL Server 2008 SP1 5
Windows PowerShell command to check databases before attaching 7
New options for reducing downtime during upgrade 7
Changes in key features between versions 8
Upgrade process overview (SharePoint Foundation 2010) 12
Hybrid approach 1: Read-only databases 14
Hybrid approach 2: Detach databases 16
Upgrading from Windows SharePoint Services 2.0 to SharePoint Foundation 2010 19
Review required permissions 22
Review required hardware and software 23
Plan and prepare for upgrade (SharePoint Foundation 2010) 27
Determine upgrade approach (SharePoint Foundation 2010) 28
Review upgrade best practices (SharePoint Foundation 2010) 35
Review supported and unsupported upgrade paths (SharePoint Foundation 2010) 37
Review supported topologies for upgrade 37
Migrating from a stand-alone server to a server farm 38
Migrating from 32-bit hardware 38
Review system requirements for upgrade (SharePoint Foundation 2010) 39
Determine how to handle customizations (SharePoint Foundation 2010) 41
Identify customizations in your environment 41
Evaluate the customizations 41
Considerations for specific customizations 42
Ensure that future customizations follow best practices 43
Create a communication plan (SharePoint Foundation 2010) 46
Who is on the upgrade team? 46
When and what to communicate to the upgrade team 47
When and what to communicate to site users 48
Plan visual upgrade (SharePoint Foundation 2010) 49
Key planning phase of visual upgrade 49
Preserving the existing user interface 49
Upgrading to the new user interface 50
Training site collection owners and site owners 50
Testing and troubleshooting upgrade (SharePoint Foundation 2010) 52
Best practices for testing upgrade (SharePoint Foundation 2010) 54
Use a trial upgrade to find potential issues (SharePoint Foundation 2010) 56
Using a virtual test environment 57
Using a physical test environment 57
Additional test environments for database attach upgrade 58
Identify and install customizations 58
Copy real data to the test environment and try the upgrade 59
Try a database attach upgrade 60
Restart upgrade, if necessary 61
Adjust your plans and test again 62
Estimate the space that you need for the upgrade 63
Estimate how long the upgrade will take 64
Cleaning up your environment before upgrade (SharePoint Foundation 2010) 67
Delete unused or underused site collections and subwebs 67
Address large numbers of site collections in a content database 68
Remove extraneous document versions 68
Remove unused templates, features, and Web Parts 68
Troubleshoot upgrade issues (SharePoint Foundation 2010) 70
General principles for identifying issues 70
First, check upgrade status and log files 70
Then, address issues in order 71
Missing or deprecated server-side files or customizations 71
Incorrectly configured or missing settings for server farm, Web application, or services 72
Inconsistent or incorrect update levels 72
Missing global navigation for blogs 73
.Stp files are not working after upgrade 74
Cannot find new versions of the Fabulous 40 application templates 74
Recovering after a failed upgrade (SharePoint Foundation 2010) 76
Recovering when you have read-only databases in a standby environment (database attach upgrade) 76
Recovering when you have a full environment backup (in-place upgrade) 76
Recovering when you have database backups (in-place upgrade) 77
Resume upgrade (SharePoint Foundation 2010) 78
Restart upgrade for a server farm by using Psconfig.exe 78
Restart upgrade for a database by using Windows PowerShell 79
Perform pre-upgrade steps (SharePoint Foundation 2010) 80
Run the pre-upgrade checker (SharePoint Foundation 2010) 81
About the pre-upgrade checker report 81
Run the pre-upgrade checker 82
Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010) 84
Perform an in-place upgrade (SharePoint Foundation 2010) 85
Checklist for in-place upgrade (SharePoint Foundation 2010) 86
Upgrade in place to SharePoint Foundation 2010 91
Run the SharePoint Products Configuration Wizard 94
Check upgrade status for sites 96
Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010) 97
To detach databases and upgrade them in parallel on the same farm 99
To detach databases and upgrade them in parallel on a temporary small farm 99
Install available language template packs (SharePoint Foundation 2010) 102
About installing language packs and upgrading sites 102
Moving from a fully localized product to a language pack 102
Changing languages to a new language pack 103
Upgrade a stand-alone installation by using remote BLOB storage (in-place) 106
Perform a database attach upgrade to SharePoint Foundation 2010 119
Checklist for database attach upgrade (SharePoint Foundation 2010) 120
Perform post-upgrade steps 124
Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade 125
Create and configure the new environment 126
Configure service applications 126
Configure general farm settings 127
Create and configure Web applications 127
Verify the new environment 129
Attach databases and upgrade to SharePoint Foundation 2010 130
Set the previous version databases to be read-only (database attach with read-only databases) 132
Back up the previous version databases by using SQL Server tools 133
Detach the previous version databases (standard database attach) 135
Restore a backup copy of the database (database attach with read-only databases) 136
Attach a content database to a Web application 137
Verification: Verify upgrade for the first database 140
Attach the remaining databases 140
Verification: Verify upgrade for additional databases 140
Perform post-upgrade steps (SharePoint Foundation 2010) 141
Configure a forms-based Web application to use an LDAP provider by using Central Administration 142
Configure the LDAP Web.Config files 142
Configure a forms-based Web application to use an LDAP provider by using Windows PowerShell 146
Verify upgrade and review upgraded sites (SharePoint Foundation 2010) 148
Check upgrade status for sites 150
Customized (unghosted) pages 153
Manage visual upgrade (SharePoint Foundation 2010) 155
About using Visual Upgrade 155
View status of current user interface 155
Revert sites to previous user interface 156
Force an upgrade to the new user interface 157
Site owner options for visual upgrade 158
- Abstract
-
Getting help
Every effort has been made to ensure the accuracy of this book. This content is also available online in the Office System TechNet Library, so if you run into problems you can check for updates at:
http://technet.microsoft.com/office
If you do not find your answer in our online content, you can send an e-mail message to the Microsoft Office System and Servers content team at:
itspdocs@microsoft.com
If your question is about Microsoft Office products, and not about the content of this book, please search the Microsoft Help and Support Center or the Microsoft Knowledge Base at:
-
Upgrading to SharePoint Foundation 2010
Welcome to the upgrade guide for Microsoft SharePoint Foundation 2010. The articles in this guide help you plan for and perform an upgrade from Windows SharePoint Services 3.0 to SharePoint Foundation 2010.
For a graphical overview of the upgrade process, and information about how to plan and test upgrade, see the following upgrade models:
Upgrade planning (http://go.microsoft.com/fwlink/?LinkId=178376)
Upgrade approaches (http://go.microsoft.com/fwlink/?LinkId=178377)
Test your upgrade process (http://go.microsoft.com/fwlink/?LinkId=178378)
In this guide:
About the upgrade process (SharePoint Foundation 2010)
Learn about what’s new in upgrade and how the upgrade process works.
Plan and prepare for upgrade (SharePoint Foundation 2010)
Determine which approach you should take to upgrade to SharePoint Foundation 2010 and plan your upgrade process.
Testing and troubleshooting upgrade (SharePoint Foundation 2010)
Learn how to test your upgrade process ahead of time to understand what issues you might face in your actual upgrade, and determine the time and space you will need for upgrade. Also, learn how to troubleshoot issues that come up during the actual upgrade.
Perform pre-upgrade steps (SharePoint Foundation 2010)
Find out what steps you need to take before upgrading, including information about how to run the pre-upgrade checker.
Perform an in-place upgrade (SharePoint Foundation 2010)
Follow the steps in this section if you are upgrading in-place to SharePoint Foundation 2010. When you upgrade in-place, you install SharePoint Foundation 2010 on the same hardware, and then upgrade the content and settings on the server or server farm as part of a single process.
Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage)
Follow the steps in this section if you have a standalone installation with content databases that are approaching 4 GB.
Perform a database attach upgrade to SharePoint Foundation 2010
Follow the steps in this section if you are using the database attach upgrade method to upgrade to SharePoint Foundation 2010. When you use the database attach upgrade method, you upgrade the content for the environment on a separate farm.
Perform post-upgrade steps (SharePoint Foundation 2010)
Find out how to tell whether upgrade was completed successfully and what steps you need to perform after the upgrade to get your environment ready for users again.
Migrate from forms-based authentication to claims-based authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/3a725e05-9b73-48ff-a481-3ddd2b4091c6(Office.14).aspx)
This article provides guidance to help you migrate existing Windows SharePoint Services 3.0 Web applications, which were configured to use forms-based authentication, to work in a Microsoft SharePoint Foundation 2010 environment as claims-based Web applications.
Migrate from classic-mode to claims-based authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/aaa9a815-fcc4-42a0-b107-2a2108d08f1b(Office.14).aspx)
The procedures in this article provide guidance to help you migrate existing Microsoft SharePoint Server 2010 Web applications, which were configured to use classic-mode authentication, to use claims-based authentication.
-
See Also
Using AAM URL redirection as part of the upgrade process (SharePoint Foundation 2010) (white paper)
-
-
About the upgrade process (SharePoint Foundation 2010)
The first step in any upgrade process is to learn about the process itself so that you can plan and prepare appropriately. This section of the upgrade guide contains articles that help you understand how upgrade works.
In this section:
What’s new in upgrade (SharePoint Foundation 2010)
Find out about new requirements, approaches, and features that are available for upgrade to Microsoft SharePoint Foundation 2010.
Upgrade process overview (SharePoint Foundation 2010)
Get a visual overview of the steps involved in each upgrade approach.
Upgrading from Windows SharePoint Services 2.0 to SharePoint Foundation 2010
Understand using database attach upgrades to upgrade your content from Windows SharePoint Services 2.0 to Microsoft SharePoint Foundation 2010.
-
What’s new in upgrade (SharePoint Foundation 2010)
Microsoft SharePoint Foundation 2010 has been designed for scale and performance and as such requires new hardware and software requirements that are described in this article. These requirements apply to both the in-place and the database attach upgrade approaches. For more information, see Determine upgrade approach (SharePoint Foundation 2010).
In order to facilitate a predictable upgrade and minimize the impact of customization and environmental issues that may prevent a successful upgrade, you can use the Windows PowerShelltest-spcontentdatabase cmdlet, the new Visual Upgrade option, or the preupgradecheck Stsadm operation.
In this article:
Windows PowerShell command to check databases before attaching
-
Upgrade requirements
Before you can perform an in-place upgrade or database attach upgrade to SharePoint Foundation 2010, your existing Windows SharePoint Services 3.0 environment or new SharePoint Foundation 2010 environment must meet the following minimum requirements.
Note:
For more information about general system requirements for SharePoint Foundation 2010, see Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx). For more information about upgrade requirements, see Review system requirements for upgrade (SharePoint Foundation 2010).
-
Hardware requirement: 64-bit
SharePoint Foundation 2010 can only run on a 64-bit edition of the Windows Server 2008 R2 or Windows Server 2008 with SP2 operating system. If you plan an in-place upgrade, your Windows SharePoint Services 3.0 installation must be running in a 64-bit Windows Server 2008 environment. If your Windows SharePoint Services 3.0 installation is currently in a 32-bit environment, you cannot perform an in-place upgrade on the existing server or server farm. You must install SharePoint Foundation 2010 on a different server or farm that supports 64-bit applications, and then move your data to that server or farm by using database attach upgrade.
To more easily discover and address any issues in the migration and upgrade processes, we recommend that you do not combine the actions of migrating to a 64-bit environment and upgrading in-place to SharePoint Foundation 2010. Because you must have a 64-bit environment to be able to upgrade in place to SharePoint Foundation 2010, you must migrate to a 64-bit operating system before you perform an in-place upgrade. If you are using a database attach upgrade, you can migrate to 64-bit as part of your upgrade process.
Before you migrate to a 64-bit environment:
Update Windows SharePoint Services 3.0 to the same service pack or software update level on all computers in the source farm.
Find out whether you have to recompile existing 32-bit applications and custom assemblies — for example, Web Parts and event receivers — to run in the 64-bit environment. (Some applications can run in both environments and do not have to be recompiled.) If the existing applications are third-party applications, check with the third-party vendor about 64-bit versions and compatibility.
For more information about how to plan and perform a migration to a 64-bit environment, see the article Migrate an existing server farm to a 64-bit environment (Windows SharePoint Services 3.0) on TechNet (http://go.microsoft.com/fwlink/?LinkId=161120).
-
Operating system requirement: Windows Server 2008 or Windows Server 2008 R2
SharePoint Foundation 2010 must be run on a 64-bit edition of Windows Server 2008 R2 or Windows Server 2008 with Service Pack 2 (SP2). If you are currently running Windows SharePoint Services 3.0 on Windows Server 2003 and intend to upgrade to SharePoint Foundation 2010, you must plan to have a sufficient number of Windows Server licenses for the deployment on the newer operating system.
To more easily discover and address any issues in the migration and upgrade processes, we recommend that you do not combine the actions of upgrading or migrating to Windows Server 2008 or Windows Server 2008 R2 with the process of upgrading to SharePoint Foundation 2010. You can combine migration to 64-bit hardware with migration to Windows Server 2008 or Windows Server 2008 R2.
If you are already running 64-bit hardware, you can upgrade from Windows Server 2003 to Windows Server 2008 or Windows Server 2008 R2. For more information about how to perform an in-place upgrade to Windows Server 2008, see the article Upgrading to Windows Server 2008 for Windows SharePoint Services 3.0 with SP1 on TechNet (http://go.microsoft.com/fwlink/?LinkId=155575).
If you are migrating to 64-bit hardware, take the opportunity to also migrate to Windows Server 2008 or Windows Server 2008 R2 at the same time. For more information about how to install Windows SharePoint Services 3.0 on Windows Server 2008, see the article Deploy a simple farm on the Windows Server 2008 operating system (Windows SharePoint Services) on TechNet (http://go.microsoft.com/fwlink/?LinkID=95859).
-
Database requirement: 64-bit SQL Server 2005 SP3 or SQL Server 2008 SP1
SharePoint Foundation 2010 requires that its database server must be a 64-bit version of one of the following: Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3. If your current Windows SharePoint Services 3.0 installation uses SQL Server 2000, you must upgrade to one of these versions before you can upgrade to SharePoint Foundation 2010.
To more easily discover and address any issues in the migration and upgrade processes, we recommend that you do not combine the actions of migrating to 64-bit SQL Server with the process of upgrading to SharePoint Foundation 2010. You can combine the migration to 64-bit SQL Server with the overall process of migration to 64-bit hardware.
If you are combining the migration to SQL Server 2005 SP3 or SQL Server 2008 on 64-bit hardware with an overall migration to a 64-bit environment, follow the guidance about how to migrate to a 64-bit environment earlier in this article.
For more information about how to migrate all databases, see the article Move all databases (Windows SharePoint Services 3.0) on TechNet (http://go.microsoft.com/fwlink/?LinkId=161208).
If you already have 64-bit hardware, but have to upgrade to SQL Server 2005 SP3 or SQL Server 2008, follow the guidance in the SQL Server documentation.
-
-
Pre-upgrade checker
The pre-upgrade checker is a command-line tool that you run in a Windows SharePoint Services 3.0 environment to find any potential issues for upgrade and to review recommendations and best practices.
STSADM.exe –o preupgradecheck
By using the pre-upgrade checker, you can find information such as the following:
A list of all servers and components in the farm, and whether the servers meet the following requirements for upgrading: 64-bit hardware and the Windows Server 2008 operating system.
The alternate access mapping URLs that are being used in the farm.
A list of all site definitions, site templates, features, and language packs that are installed in the farm.
Whether there are customizations in the farm that are not supported (such as database schema modifications).
Whether there are any database or site orphans in the farm.
Whether there are missing or invalid configuration settings in the farm (such as a missing Web.config file, invalid host names, or invalid service accounts).
Whether the databases meet the requirements for upgrade — for example, databases are set to read/write, and any databases and site collections that are stored in Windows Internal Database are not larger than 4 GB.
The pre-upgrade checker is available with Windows SharePoint Services 3.0 Service Pack 2 and has been updated in the October 2009 Cumulative Update for Windows SharePoint Services 3.0. You can download and install the October 2009 Cumulative Update from October 2009 Cumulative Update Packages for SharePoint Server 2007 and Windows SharePoint Services 3.0 are published (http://go.microsoft.com/fwlink/?LinkID=169179). For more information about how to use the pre-upgrade checker, see the following articles on TechNet:
Preupgradecheck: Stsadm operation (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkId=161232)
Pre-upgrade scanning and reporting for future releases (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkID=152468)
-
Windows PowerShell command to check databases before attaching
You can use the Windows PowerShell cmdlet test-spcontentdatabase before you attach a content database to SharePoint Foundation 2010 to determine whether any server-side customizations are missing from the environment. For more information, see Attach databases and upgrade to SharePoint Foundation 2010 and Test-SPContentDatabase (http://technet.microsoft.com/library/ed095a0a-fa1a-4323-8503-624f0e09707d(Office.14).aspx).
-
Visual Upgrade
A new feature that is available with upgrade allows the server administrator or site owner to determine when and if the new look for SharePoint Foundation 2010 is used for a particular site collection. Server administrators can choose to adopt the new look and feel for all sites during upgrade, let site owners make the choice after upgrade, or keep the old look and feel for all sites.
If the server administrator lets the site owners decide, after a site is upgraded by using an in-place upgrade, a preview option is available in the site user interface. This option provides a preview of the SharePoint Foundation 2010 look for the site:
If the owner likes how the site looks and functions, the owner can accept the visual upgrade.
If the owner wants the site to keep the old look and feel, the owner can revert to the Windows SharePoint Services 3.0 look.
By default, the Windows SharePoint Services 3.0 look is retained. For more information, see Plan visual upgrade (SharePoint Foundation 2010).
-
Feature Upgrade
SharePoint Foundation 2010 provides new members and types that make it possible for you to upgrade custom Features through versioning and declarative upgrade actions. You can update any Features you created for Windows SharePoint Services 3.0 to work with SharePoint Foundation 2010 by using these members. For more information, see Upgrading Features (http://msdn.microsoft.com/en-us/library/aa544511(office.14).aspx).
-
New options for reducing downtime during upgrade
Depending on the environment and the complexity and number of SharePoint sites, the upgrade process can take a long time. To reduce downtime during this process, SharePoint Foundation 2010 supports the following options:
Upgrade multiple databases at the same time (parallel upgrade) When you upgrade to SharePoint Foundation 2010, you can manually initiate upgrade for multiple databases at the same time by using the detach databases hybrid approach for upgrade. In Windows SharePoint Services 3.0, only one upgrade process could run at a time, so that each database needed to be processed sequentially. There is a performance impact when you run the upgrade on multiple databases instead of on a single database, but it may be faster to upgrade multiple databases at the same time than to upgrade them sequentially. The number of databases that can be upgraded in parallel will depend on the hardware in your environment and on the structure of the content within the databases. For more information, see Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010).
Use read-only databases to provide continuous access to data If you perform a database attach upgrade — and if you set the original databases to read-only mode — the old farm can continue to serve content to users while you upgrade a copy of the databases on a new farm. If you do this, users can continue to access the data, although they cannot add new data or update the data. When the new farm is ready and all content has been successfully upgraded, users can be switched over to the new live farm.
For more information about read-only databases, see the article Run a farm that uses read-only databases (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/ee845027(Office.12).aspx).
For more information about these techniques to reduce downtime, see the article Determine upgrade approach (SharePoint Foundation 2010).
-
Changes in key features between versions
SharePoint Foundation 2010 has a new architecture and includes many new capabilities. The following tables list some of the key changes to terminology and features that immediately affect the administration and site management process after upgrading.
Concept, term, or feature
New or changed
Comments
Pre-upgrade checker
New
The pre-upgrade checker is an Stsadm command-line operation that you run in an Windows SharePoint Services 3.0 environment to find any potential issues for upgrade and to review recommendations and best practices.
Unlike the pre-upgrade scan tool (Prescan.exe) that was used when upgrading to Windows SharePoint Services 3.0, the pre-upgrade checker does not make any changes to your environment. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
SharePoint Central Administration Web site
Changed
The Central Administration Web site has been redesigned with such new available options and functionality as the following:
The ribbon makes it easier for you to view or change details about a Web application by supplying all the options on the same page.
For more information about Web applications, see Web applications management (SharePoint Foundation 2010) (http://technet.microsoft.com/library/5b82a45b-f871-49e3-8926-47972acde573(Office.14).aspx).
Configuration Wizards have been added to make the configuration process easier by guiding you through the steps to configure the server farm. For more information, see Deploy a single server with SQL Server (SharePoint Foundation 2010) (http://technet.microsoft.com/library/58d28a34-7a84-4564-a4cb-0e6b5425f67e(Office.14).aspx).
You can now perform a backup from the Backup and Restore page. For more information, see Backup (SharePoint Foundation 2010) (http://technet.microsoft.com/library/d01c3931-3069-4267-a1f0-1e6ebaf43fcd(Office.14).aspx).
Ribbon
New
The ribbon user interface has been introduced to ensure a consistent user experience and to make it easier for you to work with SharePoint sites. The ribbon is contextual so that you only see the options that are relevant to the tasks that you want to perform. The ribbon is also customizable.
Service applications
New
New services architecture that allows you to effectively manage and centralize services. Individual services can be configured independently and third-party companies can add services to the platform. For more information, see Configure services (SharePoint Foundation 2010) (http://technet.microsoft.com/library/88da9bdb-b7c2-4174-997b-d767b9b9c9ea(Office.14).aspx).
Master pages
Changed
A site owner can now apply branding to their site, independent of other sites, and administrators can specify whether the system pages in the _Layouts folder are rendered by using the site master pages provided by site owners or by default master pages available across the system. Also, it is possible to use Windows PowerShell to specify a customer master page to system error pages, login pages, confirmation pages, and other non-site-specific pages.
Themes
Changed
SharePoint Foundation 2010 has changed the way themes work, making them easier to customize. You can import Microsoft PowerPoint 2010 themes directly into SharePoint Foundation 2010. Additionally, themes can now be applied to all subsites from this interface. For more information, see Plan for using themes (SharePoint Foundation 2010) (http://technet.microsoft.com/library/683790b5-800b-4b13-83d6-348088c75d10(Office.14).aspx).
Business Connectivity Services (BCS)
New
Business Connectivity Services (BCS) builds on the Business Data Catalog functionality available in the previous product version to provide access to external systems from SharePoint-based solutions. BCS supports interacting with external systems using SharePoint lists and Web Parts, and also supports interacting with data from rich Office clients. For more information, see Business Connectivity Services overview (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ed9bb457-0ecb-48de-9076-06e61aac38d9(Office.14).aspx).
Claims-based authentication
New
Claims-based authentication is a new, more powerful and flexible authentication model that works with any corporate identity system, including Active Directory Domain Services (AD DS), LDAP-based directories, application-specific databases, and new user-centric identity models such as LiveID. For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010).
Throttling and list controls
New
Throttling and list controls are two new performance controls. Throttling provides a way to control server resources and is designed so that the server can be protected from overload during peak business hours. SharePoint Foundation 2010 also provides several different settings that will restrict the queries that can be run against a large list. These settings can be configured for each Web application.
SharePoint Designer
Changed
SharePoint Foundation 2010 gives administrators added control over how SharePoint Designer is used in each Web application; for example, administrators control whether site administrators are allowed to customize master pages and layout pages, and whether site administrators can manage the URL structure of their site.
Developer dashboard
New
This is a new addition to server diagnostics and displays detailed information for each page load and therefore helps troubleshoot performance issues.
Sandboxed solutions
New
You can now enable site administrators to upload custom user code by using sandboxed solutions. For more information, see Sandboxed solutions planning (SharePoint Foundation 2010) (http://technet.microsoft.com/library/832414b2-4b58-4e6c-9d08-c287e30e85a6(Office.14).aspx).
-
Upgrade process overview (SharePoint Foundation 2010)
You can choose between two basic upgrade approaches when you upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010: in-place upgrade and database attach upgrade. An in-place upgrade is used to upgrade all Microsoft SharePoint sites on the same hardware. A database attach upgrade enables you to move your content to a new farm or new hardware. You can also combine these two types of upgrade in hybrid approaches that reduce downtime during an upgrade.
For more information about these approaches, see Determine upgrade approach (SharePoint Foundation 2010).
This article helps you understand the steps that are involved in performing upgrades by using these approaches so that you can plan your upgrade process. For detailed information about how to use one of these upgrade processes, see the following topics:
Upgrade in place to SharePoint Foundation 2010
Attach databases and upgrade to SharePoint Foundation 2010
In this article:
Hybrid approach 1: Read-only databases
Hybrid approach 2: Detach databases
Important:
It is important that the server administrator communicate with site owners and users about what to expect during an upgrade. The administrator should inform them about downtime and the risk that the upgrade may take longer than expected or that some sites may need some rework after upgrade. For more information, see Create a communication plan (SharePoint Foundation 2010).
-
In-place upgrade
An in-place upgrade takes place on the same hardware as your previous version installation. When you run an in-place upgrade, the process upgrades the complete installation in a fixed order.
The following steps explain what happens as the in-place upgrade process runs:
1. After the server administrator performs all pre-upgrade steps, the administrator runs Setup for SharePoint Foundation 2010 on the server that runs the SharePoint Central Administration Web site. Because the previous version was installed, an in-place upgrade is automatically selected.
2. After Setup runs on the server that hosts the Central Administration Web site, the server administrator runs Setup on the remaining front-end Web servers and application servers in the farm.
3. The server administrator runs the SharePoint Products Configuration Wizard on the server that hosts the Central Administration Web site. This server, the configuration database, the services, and the content databases are upgraded sequentially.
When the configuration wizard finishes, the Central Administration Web site opens. A timer job schedules the upgrade process to run for each site collection. The upgrade process timer job upgrades each site collection. After all sites are upgraded, the upgrade process ends.
4. The server administrator runs the SharePoint Products Configuration Wizard on all the other servers in the farm.

5. The server administrator confirms that the upgrade has finished successfully.
6. If Visual Upgrade is being used, the server administrator or site owner previews sites in the Microsoft SharePoint Foundation 2010 look. When the administrator or site owner is ready, he or she completes the change to the SharePoint Foundation 2010 look.
-
Database attach upgrade
A database attach upgrade enables you to move to new hardware or a new farm. During a database attach upgrade, you detach all the content databases from an existing farm and then attach the databases to a new server farm installation. When you attach the databases to the new server farm, the upgrade process runs and upgrades the data in place.
The following steps explain what happens during a database attach upgrade:
1. The server administrator sets up and configures a new SharePoint Foundation 2010 farm. The administrator transfers all customizations to the new farm and tests the environment.
For more information about how to configure the new environment, see Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade.
2. The server administrator detaches the content databases from the old Windows SharePoint Services 3.0 farm and takes the old farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all the components and services on each server computer in the farm).
3. The server administrator attaches the content databases to the new farm and upgrades the content.

4. The server administrator confirms that the upgrade has finished successfully and then configures the new farm to start serving requests at the new URL.
-
Hybrid approach 1: Read-only databases
This approach gives users continuous read-only access to their data while you upgrade. The content databases in the original farm are set to read-only, and copies of the databases are upgraded on a new farm.
The following steps explain what happens during a database attach upgrade with read-only databases:
1. The server administrator sets up and configures a new SharePoint Foundation 2010 farm. The administrator transfers all customizations to the new farm and tests the environment.
2. The server administrator changes the content databases to read-only. The administrator then uses SQL Server to back up the content databases on the Windows SharePoint Services 3.0 farm and restore them to the new farm.

3. The server administrator attaches the new copies of the content databases, and the upgrade process runs and upgrades the content.

4. After the upgrade process runs, the server administrator confirms that the upgrade has finished successfully. The administrator then configures the new farm to start serving requests at the new URL and takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all the components and services on each server computer in the farm).
-
Hybrid approach 2: Detach databases
This approach enables you to speed up the upgrade process by detaching and attaching databases to upgrade multiple databases at the same time. It is an in-place upgrade because you are upgrading the original farm; however, you can also use another farm to perform the upgrade and then attach the upgraded databases to your original farm. Note that the original farm cannot serve requests during the upgrade process. As in a standard in-place upgrade, users cannot access their content while the upgrade is in progress.
The following steps explain what happens during an in-place upgrade with detached databases:
1. The server administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).
2. The server administrator detaches the content databases from the original farm.
3. The server administrator runs an in-place upgrade on the original farm servers, services, and configuration database.
4. The server administrator attaches the content databases to the original farm and upgrades the content.

Alternatively, you can use a separate, temporary small farm to perform the upgrade. In this approach, you attach the databases to the original farm after they have been upgraded.
The following steps explain what happens during an in-place upgrade with detached databases and a temporary small farm to upgrade the content databases:
1. The server administrator sets up a temporary small farm that is running the new version. Then the administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all the components and services on each server computer in the farm).
2. The server administrator detaches the content databases from the original farm.
3. The server administrator runs an in-place upgrade on the original farm to upgrade the servers, services, and configuration database.
4. The server administrator attaches the content databases to the temporary small farm and upgrades them in parallel.
5. The server administrator reattaches the content databases to the original farm.

6. The server administrator confirms that the upgrade has finished successfully.
7. If Visual Upgrade is being used, the server administrator or site owner previews sites in the Microsoft SharePoint Foundation 2010 look. When the administrator or site owner is ready, he or she completes the change to the Microsoft SharePoint Foundation 2010 look.
-
Upgrading from Windows SharePoint Services 2.0 to SharePoint Foundation 2010
You cannot upgrade directly from Windows SharePoint Services 2.0 to Microsoft SharePoint Foundation 2010.
The changes between versions are too great, and the hardware requirements differ so much between versions that a direct, in-place upgrade is not possible or supported. You can, however, perform a series of database attach upgrades to first upgrade your content to Windows SharePoint Services 3.0 and then to SharePoint Foundation 2010. This article describes the process of performing this double-database attach upgrade.
Note:
During this entire process, your old environment should be offline, to prevent users from making changes in the old environment while you are upgrading. After you have finished and validated the upgrade, you can grant access to your users again in the SharePoint Foundation 2010 environment.
In this article:
-
Process overview
Because this upgrade approach combines two upgrade processes that have already been documented, this article describes how the steps from each process fit together into the overall process. It does not provide details for every step, because those steps are available in the following articles:
Deploy a new server farm, then migrate content databases (http://technet.microsoft.com/en-us/library/cc303311(Office.12).aspx)
Attach databases and upgrade to SharePoint Foundation 2010
These articles, combined with this roadmap, give you the information you need to perform the double-database attach upgrade.
Important
Make sure that you try out this entire process in a test environment before you attempt to upgrade your actual live content. For more information about how to test your upgrade processes, see the following content:
-
Upgrade sequence
To upgrade your content across the two versions, follow these steps.
1. Prepare to upgrade
a. Prepare your original farm by running the pre-upgrade scan tool and making an inventory of all of your customizations.
b. Set up a small, temporary farm that is running Windows SharePoint Services 3.0.
c. Set up your full SharePoint Foundation 2010 farm, and verify that it is configured and running correctly.
2. First upgrade: Upgrade the content to Windows SharePoint Services 3.0
a. Detach the content databases from the old farm, and then take that farm offline.
Alternatively, you can leave the databases attached and make a copy of the databases if you want to ensure that your original farm can be restored to use quickly.
b. Attach the content databases to the Windows SharePoint Services 3.0 farm and upgrade them.
c. Verify that the content has been upgraded and that the Windows SharePoint Services 3.0 farm is working correctly.
3. Second upgrade: Upgrade the content to SharePoint Foundation 2010
a. Detach the content databases from the Windows SharePoint Services 3.0 farm.
b. Attach the content databases to the SharePoint Foundation 2010 farm and upgrade them (optionally, you can upgrade them in parallel).
c. Verify that the content has been upgraded and that the SharePoint Foundation 2010 farm is working correctly.
4. Start serving requests on the SharePoint Foundation 2010 farm.
The following diagrams illustrate this process:
The database attach upgrade to Windows SharePoint Services 3.0.

The database attach upgrade to SharePoint Foundation 2010.

-
-
Before you begin
Before you begin your upgrade, review the following information about permissions, hardware requirements, and software requirements. Follow the specified steps to install or configure prerequisite software or to modify settings.
-
Review required permissions
When you create your temporary environment for Windows SharePoint Services 3.0, you must have the appropriate permissions. For more information, see Plan for administrative and service accounts (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288210(Office.12).aspx).
When you create and configure your destination SharePoint Foundation 2010 farm, you must have the appropriate permissions. For more information, see Administrative and service accounts required for initial deployment (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b1aee1ea-45f6-4e05-ad93-9086f6ad7e79(Office.14).aspx).
-
Review required hardware and software
When you create your temporary environment for Windows SharePoint Services 3.0, you must meet specific hardware and software requirements. For more information, see Determine hardware and software requirements (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288751(Office.12).aspx).
When you create and configure your destination SharePoint Foundation 2010 farm, you must meet different hardware and software requirements. For more information, see Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx).
In some environments, you must coordinate the procedures for moving databases to a separate farm with the database administrator. Make sure that you follow any applicable policies and guidelines for handling databases.
-
-
Prepare to upgrade
Because you are performing two upgrades, you need to understand all of the steps involved both in upgrading to Windows SharePoint Services 3.0 and to SharePoint Foundation 2010. The following content is available to help you understand these upgrade processes:
Preparing to upgrade to Windows SharePoint Services 3.0
Read the Plan and prepare for upgrade (http://technet.microsoft.com/en-us/library/cc303312(Office.12).aspx) chapter on TechNet. In particular, read the following articles:
How the upgrade process works (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288775(Office.12).aspx)
Determine how to handle customizations (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287878(Office.12).aspx)
Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287930(Office.12).aspx)
Read the Perform pre-upgrade steps (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc303302(Office.12).aspx) chapter on TechNet. You must perform the following steps for a database attach upgrade (called database migration in this version):
Install Service Pack 2 for Windows SharePoint Services 2.0 (http://technet.microsoft.com/en-us/library/cc288052(Office.12).aspx)
Run the pre-upgrade scan tool (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287628(Office.12).aspx)
Important:
You follow these steps on your existing Windows SharePoint Services 2.0 farm.
Preparing to upgrade to SharePoint Foundation 2010
Plan and prepare for upgrade. Read the following article on TechNet:
Upgrade process overview (SharePoint Foundation 2010)
Perform pre-upgrade steps. Read the following article on TechNet:
Run the pre-upgrade checker (SharePoint Foundation 2010)
Important:
You perform these steps on your temporary Windows SharePoint Services 3.0 farm.
-
Prepare your farms
In this step, you follow the pre-upgrade steps on your existing farm, create your temporary farm for the upgrade to Windows SharePoint Services 3.0, and create your destination SharePoint Foundation 2010 farm. Use the following steps and related content when preparing your farm for the upgrades.
Create the temporary Windows SharePoint Services 3.0 farm
In a virtual or physical environment, create a temporary small farm that is running Windows SharePoint Services 3.0 with Service Pack 2 (SP2) and the October 2009 Cumulative Update. You will use this farm to upgrade your content to Windows SharePoint Services 3.0 on the way to SharePoint Foundation 2010.
Tip:
For best results, it is recommended that you apply the latest updates to the environment. The October 2009 Cumulative Update includes changes to the pre-upgrade checker that can help identify issues before upgrade. For a list of available updates, see Update Center for Microsoft Office, Office Servers, and Related Products (http://go.microsoft.com/fwlink/?LinkID=181115). For more information about applying updates, see Updates Resource Center for SharePoint Products and Technologies (http://go.microsoft.com/fwlink/?LinkID=181116).
1. Download the software for the temporary farm.
Download Windows SharePoint Services 3.0 with SP2 at one of the following links:
x86 version: Windows SharePoint Services 3.0 with Service Pack 2 (http://go.microsoft.com/fwlink/?LinkID=148403)
x64 version: Windows SharePoint Services 3.0 x64 with Service Pack 2 (http://go.microsoft.com/fwlink/?LinkId=181113)
2. Install any language template packs needed for your sites. For more information, see Install available language template packs (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287870(Office.12).aspx).
3. Configure the farm by using the appropriate farm settings for your environment and reapplying all of the customizations needed by your content. Make sure that you deploy the customizations and the upgrade definition files needed for any custom site definitions that might exist in your environment. You must create Web applications on the temporary farm for every virtual server that you had in your original farm. The URL for the new Web applications should match either the source farm URLs or the destination farm URLs, otherwise you risk adding references to additional temporary URLs to the content. Ideally, you should use the same URLs for the source farm and destination farm, so that the temporary farm URLs are exactly the same as well, including the port numbers used.
For more information about configuring the farm, see Prepare the new Windows SharePoint Services 3.0 environment (http://technet.microsoft.com/en-us/library/cc287900(Office.12).aspx). For more information about deploying custom site definitions and upgrade definitions, see Deploy upgrade definition files and new site definitions (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288457(Office.12).aspx).
Set up your full SharePoint Foundation 2010 farm
This is the farm you will use for your production environment eventually, so make sure that you plan your infrastructure appropriately to support the solution you are hosting. For more information about how to plan your server farm, see Server farm and environment planning (SharePoint Foundation 2010) (http://technet.microsoft.com/library/a8e97903-c472-4c13-a1e1-2c075b2f8585(Office.14).aspx).
1. Create your farm on 64-bit hardware with database servers that are running a 64-bit version of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2. For more information, see Multiple servers for a three-tier farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a(Office.14).aspx).
2. Install any language template packs needed for your sites. For more information, see Install available language template packs (SharePoint Foundation 2010).
3. Configure the farm by using the appropriate farm settings for your environment and reapplying all of the customizations needed by your content. Again, you must create Web applications on the destination farm for every virtual server that you had in your original farm.
For more information about how to create and configure a server farm for a database attach upgrade, see Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade.
-
Perform the first upgrade
With your farms set up and configured, you are ready to upgrade your content databases to Windows SharePoint Services 3.0.
Important:
Make sure that you have run the pre-upgrade scan tool on your original farm before you detach the databases. The upgrade process will not run if you have not scanned the databases. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287628(Office.12).aspx).
To perform a database attach upgrade (called database migration for this version), follow these steps:
1. Back up the content databases.
2. Restore the backed-up copies to your temporary farm.
3. Add the databases to the Web applications to start the upgrade process.
For complete information and steps to follow, see Migrate content databases (http://technet.microsoft.com/en-us/library/cc287634(Office.12).aspx).
-
Verify the first upgrade
To verify the upgrade, do the following:
Review the upgrade log file. For more information, see Migrate content databases (http://technet.microsoft.com/en-us/library/cc287634(Office.12).aspx).
Review the upgraded sites to make sure that they still work as expected and that your Web Parts and other custom elements work correctly.
-
Perform the second upgrade
After you have verified that your sites work correctly, you can begin the upgrade to SharePoint Foundation 2010.
Important:
Run the pre-upgrade checker and review the report so that you can address any potential issues on your temporary farm before you upgrade the content. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
To perform the database attach upgrade, follow these steps:
1. Back up the content databases.
2. Restore the backed-up copies to your destination farm.
3. Add the databases to the Web applications to start the upgrade process. In SharePoint Foundation 2010, you can attach databases in parallel to speed up the upgrade process.
For complete information and steps to follow, see Attach databases and upgrade to SharePoint Foundation 2010.
-
Verify the second upgrade
To verify the upgrade, do the following:
Review the upgrade log file.
Review the upgraded sites to make sure that they still work as expected and that your Web Parts and other custom elements work correctly.
For more information, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
-
Plan and prepare for upgrade (SharePoint Foundation 2010)
Now that you have learned how the upgrade process works by reading the articles in About the upgrade process (SharePoint Foundation 2010), you can begin your upgrade planning. This section contains articles that help you plan and prepare for upgrading from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010.
In this section:
Determine upgrade approach (SharePoint Foundation 2010)
Learn about the different upgrade approaches and choose the one that is best suited to your environment.
Review upgrade best practices (SharePoint Foundation 2010)
Avoid problems during the upgrade process by following these best practices.
Review supported and unsupported upgrade paths (SharePoint Foundation 2010)
Understand which installation types and topologies can be upgraded to SharePoint Foundation 2010.
Review system requirements for upgrade (SharePoint Foundation 2010)
Review the requirements to help ensure that your environment can be upgraded to SharePoint Foundation 2010.
Determine how to handle customizations (SharePoint Foundation 2010)
Learn how to identify and evaluate the customizations in your environment, and determine whether you will upgrade them, and how.
Create a communication plan (SharePoint Foundation 2010)
Create a plan to coordinate and communicate with the upgrade team, site owners and users, and stakeholders.
Plan visual upgrade (SharePoint Foundation 2010)
Learn about the different visual upgrade options and how to choose the option that best suits your business needs.
A worksheet is available so you can record information about your environment while you prepare for upgrade. Download the worksheet from http://go.microsoft.com/fwlink/?LinkId=179928 (http://go.microsoft.com/fwlink/?LinkId=179928).
-
Determine upgrade approach (SharePoint Foundation 2010)
Before you run any process to upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, you have to determine which upgrade approach to take. Use the information in this article to help compare the pros and cons for each approach and to review information about special cases that might influence your approach. In addition to the information in this article, be sure to read Review supported and unsupported upgrade paths (SharePoint Foundation 2010) to understand exactly which upgrade situations are valid and lead to successful upgrades.
Note:
To perform an upgrade, you must have installed Windows SharePoint Services 3.0 with Service Pack 2 (SP2).
In this article:
-
Choose an upgrade approach
There are two basic approaches to upgrade: in-place and database attach. In addition, there are various techniques you can use to combine aspects of these basic approaches to mitigate downtime or potentially improve performance.
The following table compares the in-place and database attach approaches.
Approach
Description
Pros
Cons
In-place upgrade
You can install SharePoint Foundation 2010 on the same hardware. You can also upgrade the content and settings in the server farm as part of a single process.
Farm-wide settings are preserved and upgraded. Customizations are available in the environment after the upgrade, although manual steps may be required to upgrade or rework them.
Servers and farms are offline while the upgrade is in progress. The upgrade proceeds continuously. Consequently, you must allocate enough time for all content to be upgraded in sequence.
Database attach upgrade
You can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users.
You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. You can use a database attach upgrade to combine multiple farms into one farm.
The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm. Any customizations must also be transferred to the new farm manually. Any missing customizations may cause unintended losses of functionality or user experience issues. Copying databases over a network takes time and bandwidth. You must plan for that. You need direct access to the database servers.
For more information about how in-place and database attach upgrades work, see Upgrade process overview (SharePoint Foundation 2010).
The following table lists the downtime mitigation techniques that you can use during upgrade to reduce the amount of time that users cannot access their content or to potentially increase upgrade performance.
Technique
Description
Pros
Cons
Parallel upgrade
You can attach and upgrade multiple databases at a time to speed up the upgrade process overall. The maximum number of parallel upgrades depends on your hardware. This technique works for either in-place or database attach upgrades.
Faster upgrade times for your overall environment.
This is a manual process that requires additional steps and monitoring.
Hybrid approach 1: Database attach with read-only databases
Lets you continue to provide read-only access to content during the upgrade process. For this approach, you set the databases to read-only while the upgrade is in progress on another farm. This method reduces perceived downtime for your users.
The existing farm can continue to host non-upgraded sites (in read-only mode) while you upgrade the content. As a result, there is minimal downtime for users.
You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade.
You can upgrade hardware in addition to software.
The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm.
Any customizations must also be transferred and upgraded manually. Any missing customizations may cause unintended losses of functionality or user experience issues.
Copying databases over a network takes time and bandwidth. You must plan for that.
You need direct access to the database servers.
Hybrid approach 2: In-place upgrade with detached databases
Lets you take advantage of an in-place upgrade’s ability to upgrade content and settings, while adding the speed of a database attach upgrade. For this approach, you use an in-place upgrade to upgrade the farm and settings, and to detach and upgrade multiple databases in parallel (on the same farm or a separate farm).
Farmwide settings can be preserved and upgraded.
Customizations are available in the environment after upgrade, although manual steps may be required to upgrade or rework them.
You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade.
Copying databases over a network takes time and bandwidth. You must plan for that.
You need direct access to the database servers.
Be aware that you can also combine these techniques. For example, you can set your original farm to read-only mode, create a copy of the farm and upgrade it without the content databases, use parallel upgrade to rapidly upgrade all the user content, and then finally switch users to the new farm after upgrade is completed. For more information about these downtime mitigation techniques work, see Upgrade process overview (SharePoint Foundation 2010).
Another option to consider if you are facing an overly long outage window is to use Alternate Access Mapping URL Redirection with a database attach approach, so that you temporarily redirect users to an existing farm while you upgrade the content on a new farm. This is an advanced method and should not be used unless other downtime mitigation techniques are not sufficient. For more information, see Using AAM URL redirection as part of the upgrade process (SharePoint Foundation 2010) (white paper).
-
Special cases
You might have other requirements or additional goals that you want to achieve when you perform an upgrade. The following table lists special cases and describes which upgrade approach is appropriate for each case.
Case
Upgrade approach
Upgrading a stand-alone installation with Windows Internal Database?
If you are running Windows SharePoint Services 3.0 on a stand-alone server with Windows Internal Database, your database will be migrated to SQL Server Express as part of the in-place upgrade process. If your database is larger than 4 GB, you must configure Remote BLOB Storage to store some of the data. For more information, see Upgrade a stand-alone installation by using remote BLOB storage (in-place).
Upgrading from a 32-bit to a 64-bit edition of SQL Server?
If you are running a 32-bit edition of SQL Server, you must migrate to a 64-bit edition. We recommend that you perform this migration before you upgrade to SharePoint Foundation 2010 to ensure best performance benefits. Ensure that you perform only one kind of upgrade or migration at a time to avoid upgrade failure. For more information, see Migrate an existing server farm to a 64-bit environment (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/dd637753(Office.12).aspx).
The following are two options for upgrading from a 32-bit to a 64-bit edition of SQL Server:
You can back up the whole set of databases for the farm, perform the upgrade, and then restore the databases. (This option is supported and recommended because you will have a full backup, and after you restore the databases, you do not have to change anything within SharePoint Foundation 2010).
You can move the SQL Server databases that you want to upgrade to a different 64-bit edition of SQL Server. You must add the different 64-bit edition, and then run a command to the computers running SharePoint Foundation 2010 to point them to the new 64-bit edition of SQL Server. (This option is supported but not recommended because it requires more work in SharePoint Foundation 2010 when, for example, the databases change location).
Note:
If you upgrade a SQL Server version — for example, from SQL Server 2005 SP2 to SQL Server 2008 — you can perform this upgrade before, during, or after you upgrade from a 32-bit to a 64-bit edition of SQL Server.
Upgrading from Windows Server 2003 to Windows Server 2008?
Upgrade the operating system before you attempt to upgrade to SharePoint Foundation 2010.
If you are running Windows SharePoint Services 3.0, you must perform specific steps to upgrade to Windows Server 2008. For more information, see Upgrading to Windows Server 2008 for Windows SharePoint Services 3.0 with SP1 (http://technet.microsoft.com/en-us/library/cc288690(Office.12).aspx).
Upgrading from a 32-bit operating system to a 64-bit operating system?
If you are using a 32-bit operating system, you must migrate to a 64-bit operating system before you upgrade. For more information, see Migrate an existing server farm to a 64-bit environment (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/dd637753(Office.12).aspx).
Upgrading an environment that uses forms-based authentication?
Additional steps are required to upgrade when you are using forms-based authentication. For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010).
Upgrading very large databases?
In general, very large databases — particularly databases that have a large number or large size of document versions inside them — take longer to upgrade than smaller databases. However, the complexity of the data determines how long it takes to upgrade, not the size of the database itself. If the upgrade process times out, it is usually because of connection issues. In Windows SharePoint Services 3.0, the upgrade process often timed out because of the time needed to execute a process, but this is rarely the case with SharePoint Foundation 2010. For more information about how long upgrade might take for your environment, see Estimate how long the upgrade process will take and the space that you need (SharePoint Foundation 2010).
Upgrading databases with a large number of site collections?
If you have 5,000 or more site collections in a database, consider breaking them out into multiple databases. In Windows SharePoint Services 3.0, there was a default warning at 9,000 site collections and a hard limit at 15,000 site collections. In SharePoint Foundation 2010, these values change to 2,000 site collections for the warning and 5,000 site collections for the limit. To avoid errors during upgrade or broken sites after upgrade, we recommend that you move some site collections into separate databases. If you have multiple content databases, you can also speed up your upgrade process by upgrading multiple databases in parallel.
For more information about moving site collections to a new database, see Move site collections to a new database (split a content database) (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc825327(office.12).aspx).
Upgrading from Windows SharePoint Services 2.0?
Use a database attach upgrade method to upgrade to Windows SharePoint Services 3.0, and then upgrade to SharePoint Foundation 2010. For more information about this upgrade process, see Upgrading from Windows SharePoint Services 2.0 to SharePoint Foundation 2010.
Changing languages?
You have two choices, depending on whether a single site or your entire environment is changing languages:
To change the language for a specific site, upgrade in the same language, and then install the new language pack and change to that language.
Caution
You must have the appropriate language packs installed to upgrade any sites based on a localized site definition. If you do not have the new language pack, the sites will not be accessible. Wait for the new language packs to be released before attempting to upgrade those sites.
Also, you must have any language packs you used for Windows SharePoint Services 3.0 installed before you can perform an in-place upgrade.
To change the installation language for your servers, use the database migration approach to migrate your data from the old version and language to the new version and language.
Using internationalized domain names?
Although Windows SharePoint Services 3.0 supported internationalized domain names (IDNs), SharePoint Foundation 2010 does not. If you currently use IDNs with Windows SharePoint Services 3.0 and you plan to upgrade or migrate to SharePoint Foundation 2010, you must stop using IDNs, delete any IDN settings, and set up a non-IDN environment before doing so. For more information, see Plan for multilingual sites (SharePoint Foundation 2010) (http://technet.microsoft.com/library/95dc3f61-13da-4447-926a-ddae0326393e(Office.14).aspx).
-
Review upgrade best practices (SharePoint Foundation 2010)
To ensure a smooth upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, follow these best practices:
1. Update your servers to Service Pack 2 (SP2) of Windows SharePoint Services 3.0 or later.
Your environment must be updated to Service Pack 2 of Windows SharePoint Services 3.0 to run the upgrade process, either for an in-place or database attach upgrade. We recommend that you install the October 2009 Cumulative Update because it includes improvements to the pre-upgrade checker tool. For more information about how to install service packs and updates, see the Updates Resource Center for SharePoint Products and Technologies (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx). For a list of all available updates, see Update Center for Microsoft Office, Office Servers, and Related Products (http://technet.microsoft.com/en-us/office/sharepointserver/ee748587.aspx).
2. Ensure that the environment is fully functioning before you perform an upgrade.
An upgrade does not solve any problems that might already exist in your environment. Therefore, ensure that the environment is fully functioning before you perform an upgrade. For example, if you have Web applications that are no longer being used, unextend them before you upgrade. If you want to delete a Web application in Internet Information Services (IIS), unextend the Web application before you delete it; otherwise, SharePoint Foundation 2010 will try to upgrade the Web application even though it does not exist, and the upgrade will fail. If you find and solve problems beforehand, you are more likely to meet the upgrade schedule that you have estimated.
3. Before you try an in-place upgrade, migrate to 64-bit servers. Upgrade your operating system to a 64-bit version of Windows Server 2008 R2 or Windows Server 2008 with Service Pack 2 (SP2). If you are using SQL Server, upgrade or migrate to a 64-bit version of Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3.
Do not try to combine these operations with your upgrade process. You cannot perform an in-place upgrade unless your system already runs on a supported operating system and platform. For more information, see What’s new in upgrade (SharePoint Foundation 2010).
4. Run the pre-upgrade checker to look for potential issues.
The pre-upgrade checker reports missing customizations and issues with orphaned sites, and more, so that you can address these issues before you perform your upgrade. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
5. Perform a trial upgrade on a test farm first.
Back up the live farm, restore to test servers, and then perform the upgrade. Examine the results to set expectations for what the live upgraded sites will look like, to determine how much post-upgrade customization will have to be done, and to estimate how long the upgrade will take. Try a full search indexing crawl. For more information, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010).
6. Plan for capacity.
Ensure that you have disk, processor, and memory capacity sufficient to handle upgrade requirements. For more information about system requirements, see Review system requirements for upgrade (SharePoint Foundation 2010). For more information about how to plan the disk space that is required for upgrade, see Estimate how long the upgrade process will take and the space that you need (SharePoint Foundation 2010).
7. Back up your environment.
Perform a full backup of your environment before upgrading. That way, you can recover your environment if you must roll back from an upgrade. For more information, see Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010).
8. Optimize your environment before upgrade.
A few key limits have changed in SharePoint Foundation 2010, such as query throttling on large lists and lower limits on the number of site collections allowed per content database (from 5,000 warning and 15,000 limit to 2,000 warning and 5,000 limit). Be sure to optimize your Windows SharePoint Services 3.0 environment to meet these limits or restrictions before upgrade to mitigate errors during the upgrade process or broken lists or sites after upgrade. For more information about the site collection limit, see SharePoint Server 2010 capacity management: Software boundaries and limits (http://technet.microsoft.com/library/6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe(Office.14).aspx). For more information about large lists and addressing the lower limit on site collections, see Cleaning up your environment before upgrade (SharePoint Foundation 2010).
9. (Optional) If you are using the database attach upgrade method, set the original databases to read-only.
If you expect a long outage window while you perform a database attach upgrade, you can set the databases in the original environment to be read-only so that users can continue to access their data without changing it. For more information, Attach databases and upgrade to SharePoint Foundation 2010.
10. Do not add any servers to your server farm after you begin the upgrade process.
Running the SharePoint Products Configuration Wizard upgrades the configuration database. The configuration database contains the list of servers in the farm. Servers added to the farm after the configuration wizard has been run are not included in the database. Therefore, servers added after the wizard runs do not appear in the upgraded version topology. If you need to add servers to your farm, do so either before you start the upgrade or after you have completed the upgrade process.
11. After upgrade, review the Upgrade Status page and upgrade logs to determine whether there are issues that must be addressed. Then review the upgraded sites.
The Upgrade Status page reports on the upgrade progress, and the upgrade logs list any errors or warnings that occurred during the upgrade process. You should verify all of the sites and test them before you consider the upgrade complete. For more information, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
-
Review supported and unsupported upgrade paths (SharePoint Foundation 2010)
When you plan your upgrade process, make sure that you verify that the upgrade path you want to pursue is supported. This article describes supported and unsupported upgrade paths for an in-place upgrade, and covers which specific topologies can be upgraded in place to Microsoft SharePoint Foundation 2010.
-
Review supported topologies for upgrade
When you upgrade, you must upgrade to the same kind of installation: stand-alone to stand-alone, or server farm to server farm. You cannot migrate from stand-alone to farm or vice versa during an in-place upgrade process. However, either before or after you upgrade, you can change the size and scale of a server farm to suit your requirements. Or, if you perform a database attach upgrade, you can attach the databases to a different installation type.
The Microsoft SQL Server topology — in addition to your network, physical storage, and caching — can significantly affect system performance. In planning your hardware, remember that for in-place upgrade, the server or server farm that you upgrade must be running a 64-bit version of Windows Server 2008 R2 or Windows Server 2008 with Service Pack 2 (SP2). For server farms, you must also be running a 64-bit version of Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3. For more information about upgrade requirements, see Review system requirements for upgrade (SharePoint Foundation 2010).
The following table lists the supported starting topologies in Windows SharePoint Services 3.0, and the supported and unsupported ending topologies when you upgrade in place to SharePoint Foundation 2010.
Starting topology (Windows SharePoint Services 3.0)
Supported ending topology (SharePoint Foundation 2010)
Unsupported ending topology (SharePoint Foundation 2010)
Stand-alone server with Windows Internal Database
Stand-alone server with Microsoft SQL Server 2008 Express
Any farm
Single server with SQL Server
Single server with SQL Server
Stand-alone server with Microsoft SQL Server 2008 Express
Any size farm
Any size farm
Stand-alone server with Microsoft SQL Server 2008 Express
If you want to change from a stand-alone server to a server farm, you can do so before you upgrade. To migrate from a stand-alone server to a server farm configuration, you must first create a new farm, and then move the databases from the stand-alone server to the server farm. For more information, see Migrate content databases from Windows Internal Database to an instance of SQL Server (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc287738(Office.12).aspx). After you have migrated, you can perform your upgrade to SharePoint Foundation 2010.
You cannot upgrade in-place from Windows SharePoint Services 3.0 to SharePoint Foundation 2010 if you are on 32-bit hardware. If you start in 32-bit, you must first migrate to 64-bit hardware. For more information, see Migrate an existing server farm to a 64-bit environment (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/dd637753(Office.12).aspx).
-
Review system requirements for upgrade (SharePoint Foundation 2010)
Before you can upgrade your environment from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, your servers must meet the following minimum requirements:
The hardware and software must meet or exceed the minimum system requirements to run the new version.
This includes the requirement for 64-bit hardware and 64-bit versions of the operating system and Microsoft SQL Server. Before you begin the upgrade process, make sure that your system meets or exceeds the minimum requirements in Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx). Before upgrading, determine how much production capacity you have to have in your upgraded environment and identify the hardware that you must have for your upgrade based on that information.
Windows SharePoint Services 3.0 must be updated to Service Pack 2
Your environment must be updated to at least Service Pack 2 of Windows SharePoint Services 3.0 to run the upgrade process, either for an in-place or database attach upgrade. We recommend that you install the October 2009 Cumulative Update because it includes improvements to the pre-upgrade checker tool. For more information about how to install service packs and updates, see the Updates Resource Center for SharePoint Products and Technologies (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx). For a list of all available updates, see Update Center for Microsoft Office, Office Servers, and Related Products (http://technet.microsoft.com/en-us/office/sharepointserver/ee748587.aspx).
-
About these requirements
It is important that your hardware meet at least the minimum requirements that are listed in the article Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx); otherwise, you might encounter issues during the upgrade process. For example, if your database server has insufficient memory or processor power, it may be unable to keep up with the number of transactions that occur during the upgrade process, and the upgrade may fail.
We recommend that you use a trial upgrade to determine exactly what hardware capacity you must have for an acceptable upgrade experience. For more information, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010). If you experience capacity problems with your hardware during the trial upgrade, you can increase the capacity and repeat the upgrade until you are satisfied that you have found the optimal level of upgrade performance.
Important:
It is important to track the following three resource components for a server that is running SQL Server: CPU, memory, and I/O subsystem. When one or more of these components seems to have reached capacity, analyze the appropriate strategy based on the current and projected work load, and determine whether to add more resources or to scale out to a new server that is running SQL Server. In general, we recommend that you consider scaling out, in addition to adding more resources.
-
Determine how to handle customizations (SharePoint Foundation 2010)
If you have extensively customized your sites based on Windows SharePoint Services 3.0, you must determine how you want to handle your customized sites when you upgrade to Microsoft SharePoint Foundation 2010. Your approach will vary based on the extent of the customizations, the kind of customization, the complexity of your site, and your goals for upgrading. Before you upgrade, you must identify and then evaluate the customizations in your environment and determine whether you will upgrade them, and how.
In this article:
Identify customizations in your environment
-
Identify customizations in your environment
As part of your upgrade testing process, you should create an inventory of the server-side customizations in your environment (solutions, features, Web Parts, event handlers, master pages, page layouts, CSS files, and so on). For more information about how to identify customizations, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010). You can use the Upgrade Planning worksheet to list specific customizations and then record the results of your evaluation in the next section. Download the worksheet from http://go.microsoft.com/fwlink/?LinkId=179928 (http://go.microsoft.com/fwlink/?LinkId=179928).
-
Evaluate the customizations
After you have identified the customizations, you can decide what to do about them. The following questions can help you evaluate the customizations:
Is the customization still valuable?
Does it serve a useful business need?
Is it widely deployed and used?
Is the customization well-designed?
Is it built on supported, predefined site definitions?
Does it follow best practices for customizations?
Is it a supported kind of customization, or does it introduce risk into your environment?
As you evaluate each individual customization, you can also think about your overall approach for customizations. You can choose from among these options:
1. Keep the customizations Use Visual Upgrade to continue to use the previous version’s user experience for specific sites. Although you can use this approach to keep the same functionality, you will not be able to take advantage of the new visuals — such as the Fluent user interface (UI), also called the ribbon — and capabilities that are available in the new version.
2. Replace or redo the customizations If you want to use new functionality, plan to redesign your sites, or are significantly changing the information architecture, the upgrade is your opportunity to start over with new features, a new look, or a new organization. When you replace or redo customizations, you can take advantage of the new capabilities, modify your design slightly if you want, or move to a more manageable design.
For more information about redoing and redeploying solutions, see Redeploying Customizations and Solutions in SharePoint Foundation 2010 and SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkId=182335).
3. Discard the customizations Replace the customizations by using default functionality. You can reset pages to the default site definitions and remove any Web Parts or features that you no longer want to support. If you decide to discard any customizations, you must fix any issues that result from removing the customizations in the sites that used them. You can use your customizations inventory to determine which sites require this kind of attention before or after upgrade.
-
Considerations for specific customizations
In addition to your overall decision about how to treat customizations in your environment during upgrade, you must examine specific types of customizations to determine whether you must perform any additional actions to make them work in the upgraded environment.
The following table lists some common customizations and a recommendation for addressing that kind of customization.
Customization type
Recommendation
Site templates (.stp files)
Site templates (.stp files) are a deprecated feature in SharePoint Foundation 2010. New site templates in SharePoint Foundation 2010 are saved as .wsp files (solution packages).
A site that was provisioned by using a site template will be upgraded, but you will be unable to create new sites that are based on that template. If you want to be able to create new sites, you can create and deploy a solution package instead. For more information, see Troubleshoot upgrade issues (SharePoint Foundation 2010).
Site definition
Migrate sites to a supported, predefined site definition, then apply custom features by using solution deployment.
You can also continue to use a custom site definition. You do not have to create a new site definition that is based on SharePoint Foundation 2010.
However, if you must perform custom upgrade actions for the definition, you might have to create an upgrade definition file for that site definition. For more information, see Upgrade Definition Files (http://go.microsoft.com/fwlink/?LinkId=182339) on MSDN.
“Fabulous 40” application templates
Microsoft is not creating new versions of these templates. Sites that are based on these templates can be upgraded, but make sure that you test each site before you upgrade the production environment. For more information, see Troubleshoot upgrade issues (SharePoint Foundation 2010).
Feature
Evaluate, then redesign or redeploy if necessary.
Workflows and server controls
Depends on the solution. Contact the vendor to find out whether there is an updated solution. If a workflow is compatible with the new version, redeploy.
Event handler
Rewrite and redeploy as a feature.
Managed paths (inclusions/exclusions)
Re-create inclusions for a database attach upgrade. Exclusions are assumed and do not have to be re-created.
Themes
Because of the extensive changes to the UI, custom themes that are based on Windows SharePoint Services 3.0 will not work in SharePoint Foundation 2010. Use Visual Upgrade to continue to use the sites in the old user experience until you can create and apply a new theme that is based on SharePoint Foundation 2010.
Toolbar actions
Move to the ribbon (Fluent UI).
Master pages and CSS files
Rework to accommodate the new user experience.
JavaScript
Test to determine whether any actions are required. In some cases, you might have to adjust the scripts to work with the new page model. Verify that it works on an upgraded site, and in both Visual Upgrade modes.
Search provider or security trimmer
Test to determine whether any actions are required.
Web Parts
Test to determine whether any actions are required. You might have to adjust the Web Parts to work with strict XHMTL mode.
If a Web Part is located on a page but not in a Web Part Zone (so that it is, basically, HTML code embedded directly in a page), it will not work if you revert the page to the default template.
Services
Test to determine whether any actions are required. Redesign or adjust code, as needed.
Authentication providers
Test to determine whether any actions are required. Redeploy the provider on a test farm and ensure that it works correctly with claims authentication.
The following kinds of customizations are not supported. If you have any of these customizations in your environment, you must replace them by using a supported kind of customization before you can upgrade. Otherwise, you might experience upgrade issues that cannot be fixed:
Predefined files, features, or site definitions that have been modified.
Warning:
Some predefined file types — such as document icons or actions — can be modified and although they will not be upgraded, their changes can be carried forward in a supportable way. Modifications to other predefined files, such as server-side ASPX pages, will be lost during upgrade if you revert to the site template. Depending on the files that have been changed and the extent of these changes, the upgrade experience can vary significantly. The best practice is to revert all changes in all files on the disk.
SharePoint databases that have been modified, either by directly changing data or changing the schema, including adding or removing triggers, tables, views, or indexes.
If you have any of these kinds of customizations, remove them and replace them with supported customizations before you attempt to upgrade. This is a best practice for helping to ensure that not only your current upgrade will work, but any future upgrades will go more smoothly. Changing predefined files and databases will remain unsupported.
-
Ensure that future customizations follow best practices
Ensure that your environment performs well and follows best practices. Deploy only those customizations that follow the best practices described in the following articles on MSDN and TechNet:
Best Practices: Using Disposable Windows SharePoint Services Objects (http://go.microsoft.com/fwlink/?LinkId=105945&clcid=0x409).
Development Tools and Techniques for Working with Code in Windows SharePoint Services 3.0 (Part 1 of 2) (http://go.microsoft.com/fwlink/?LinkID=101494&clcid=0x409).
Best Practices: Common Coding Issues When Using the SharePoint Object Model (http://go.microsoft.com/fwlink/?LinkId=105946&clcid=0x409).
SharePoint Products and Technologies customization policy (http://go.microsoft.com/fwlink/?LinkId=105947&clcid=0x409).
-
Create a communication plan (SharePoint Foundation 2010)
It is important that you communicate with your users during the upgrade process from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010. Site users need to know what to expect when they visit their sites again after upgrade, and site owners need to know how they can help prepare for upgrade and what they will have to do after upgrade. Both site users and site owners need to know when the upgrade will occur. As part of the planning process, determine the following:
Who are the members of your upgrade team, what other stakeholders are involved, and who will be affected by the upgrade.
What information must the upgrade team have, and when.
What information must site users and other stakeholders have, and when.
This article describes how to create your communication plan so that your upgrade team, your stakeholders, and your users know what to expect before, during, and after the upgrade.
In this article:
-
Who is on the upgrade team?
For small deployments in which sites have not been customized to any great degree, the upgrade team might consist of only one person. For larger deployments, on the other hand, several people with different roles can be required, as described in the following list:
Server administrators The server administrator performs most of the upgrade tasks. There must be at least one server administrator on the upgrade team because running the Setup wizard requires someone who is a member of the local Administrators group on each front-end Web server.
Note:
Farm administrators might not be local administrators for the server.
Database administrators If you have a separate database administration team, you must coordinate with them to schedule the upgrade and perform the upgrade, especially if you plan to use the database attach upgrade method.
Server security teams You must coordinate with your security teams, such as the Active Directory directory services team, to verify accounts and permissions or to take advantage of the new policy settings you can apply for SharePoint Foundation 2010.
Client deployment team Communicate with client deployment teams to coordinate deployments of new client and server applications. Client deployment might have to occur before you upgrade, or it could be an option available to users after their sites have been upgraded.
Site collection owners You must notify site collection owners when the upgrade process is about to occur, and warn them about any issues that you find when you run the pre-upgrade checker or when you upgrade their sites. If you are using Visual Upgrade, you must also communicate with site collection owners about the change to the new user interface and whether the farm administrators or site collection administrators will be completing that change.
Site designers and developers If you have custom templates, Web Parts, Web services, or other custom elements associated with your sites, you must work with the people responsible for developing or customizing those elements to ensure that you can create new versions of these custom elements or verify that these elements have been upgraded correctly. For more information about potential issues with custom elements, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010).
Site users Although you do not have to include site users in making decisions about the upgrade process, you must tell site users when it will happen and what they should expect.
Sponsors and other stakeholders You might have other people in your organization involved in the upgrade planning process. Make sure that you include them in your communication plan appropriately.
Note:
An upgrade team can include one or more members in each role, depending on your organization.
-
When and what to communicate to the upgrade team
In general, the server administrators and shared services administrators set the timeline for upgrade, and site owners are notified only when the process is about to begin. However, because team members have their own tasks to perform at particular points in the overall upgrade process, it is critical that you have a solid plan to communicate the progress of the upgrade to all team members so that everyone knows when it is time to perform their particular tasks.
The whole upgrade team needs to work together to determine the following:
The upgrade approach to use The Determine upgrade approach (SharePoint Foundation 2010) article contains information to help you decide which kind of upgrade to perform. The report generated by the pre-upgrade checker is also important to consider when you make this decision.
Dates and times to perform the upgrade We recommend (especially for an in-place upgrade) that you upgrade when site usage is low. For small single-server deployments, upgrade may be completed in less than a day. For larger deployments, such as server farms with large amounts of data, the database attach upgrade method or the in-place upgrade with detached databases method can be used to distribute the upgrade process over several outage windows. There is no way to determine the precise length of time that will be required to upgrade any particular site collection. Because of this, it is very important to communicate with other team members involved in the upgrade process in addition to end users. The day or days that you choose for upgrading should be far enough in the future that the upgrade team has enough time to complete all of the preliminary steps. When you plan the timeline, make sure that you schedule time to validate the upgraded sites and time to implement any changes or do any work to re-brand sites.
It is important to communicate with site owners, designers, and developers at the following points during the upgrade process:
Before the process begins, so that they know the general timeline and what their roles in the process will be.
After the pre-upgrade checker has been run, so that they can address any issues that have been identified by the checker. For more information about the pre-upgrade checker, see Run the pre-upgrade checker (SharePoint Foundation 2010). For example, issues such as customized site templates or custom Web Parts should be reported to the appropriate site owner, designer, or developer before you schedule the upgrade, to give them time to investigate the issues and take preliminary steps. Or a developer might decide that it would be prudent to rebuild a Web Part before the upgrade occurs. And site owners might want to note any customizations that have been done to their sites, including site templates and changes to core Active Server Page Extension (ASPX) files.
After their sites have been upgraded, so that they can review the sites and make any changes that are needed.
-
When and what to communicate to site users
It is equally important to communicate with the users of the sites to tell them about the following issues:
When their sites will be upgraded In the case of an in-place upgrade, they must also be informed that their sites will be unavailable during the upgrade.
When to expect their upgraded sites to be ready This means that the upgrade team has not only upgraded, but also verified the functionality of, the upgraded sites.
How the upgrade might affect them and what they should know about the new environment For example, the site will look different and function slightly differently in the new user interface. If you are using Visual Upgrade, inform your users whether they will see the new or old user experience and what to expect. You can also point them to available content, such as What’s New articles or training materials, to learn about the new version. For more information about feature changes and visual upgrade, see Plan visual upgrade (SharePoint Foundation 2010) and Changes in key features between versions in the article “What’s New in Upgrade”.
How to get help If they find an issue with their site after upgrade, where can they go to address it?
-
Plan visual upgrade (SharePoint Foundation 2010)
This article discusses the new visual upgrade feature in Microsoft SharePoint Foundation 2010. If your organization plans to perform an upgrade of Windows SharePoint Services 3.0, you can take advantage of this new feature. By default, the look and feel of sites is preserved during an upgrade from Windows SharePoint Services 3.0. Site owners can switch to the new user interface permanently, or they can choose to preview the new user interface for their SharePoint sites. By using the visual upgrade feature, you can choose to move all sites to the new user interface. If you select the latter option, you override the user interface for site collection owners and site owners. You can also choose to either preserve customized pages or you can choose to reset all customized pages. Both choices will update the look and feel of template pages, but the latter option deletes modifications from customized pages and cannot be undone.
Note:
The visual upgrade feature is not available if you are performing an upgrade on a single server with built-in database through the SharePoint Products Configuration Wizard. However, the visual upgrade feature is still available if you use the PSConfig command-line tool for upgrade.
This article lists key considerations for planning to use visual upgrade, and it also discusses known issues. For more information, see Manage visual upgrade (SharePoint Foundation 2010).
In this article:
Key planning phase of visual upgrade
-
Key planning phase of visual upgrade
Visual upgrade is a feature that is part of the upgrade process. Before you perform the upgrade, ensure that you know about the effects of choosing between the two different options visual upgrade has to offer.
-
Preserving the existing user interface
If you choose to preserve the look and feel of existing SharePoint sites, you give site collection owners control over their site collections and site owners control over their sites. All the data and settings from the original sites are preserved, and layout, command organization, and styles preserve the previous user interface. Regardless of the type of farm upgrade that you select, you receive all the infrastructure benefits of Microsoft SharePoint Foundation 2010 including improved reliability, scalability, and manageability. Preserving the previous user interface reduces the likelihood that customized content will cease to function. This ensures that you and the users can continue to use existing SharePoint sites until all upgrade work, including troubleshooting and updating customizations, has been completed.
-
Upgrading to the new user interface
If you choose to change all the existing SharePoint sites to the new user interface, site collection owners and site owners have no control over the upgrade. All the data and settings from the existing SharePoint sites are upgraded to the new user interface. You might want to choose this option if there are no customizations or if you have tested any customizations that you need before the upgrade. Even if you choose this option, you still have the option of either preserving customized pages or resetting customized pages. If you need to keep customizations, or if you are unsure whether to keep customizations, you should choose to preserve customized pages. Resetting the customized pages removes customizations and cannot be undone. Choose this option if you do not need the customizations any longer and if you know that no important data will be lost. For more information, see Determine how to handle customizations (SharePoint Foundation 2010), Use a trial upgrade to find potential issues (SharePoint Foundation 2010), and Redeploying Customizations and Solutions in SharePoint Foundation 2010 and SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkId=186372).
-
-
Training site collection owners and site owners
It is important that you train users about the effects of either preserving the look and feel of existing SharePoint sites or upgrading all sites to the new user interface. Educated users are prepared and know what to expect, which will minimize helpdesk support and frustrations.
If you upgrade all sites to the new user interface, inform users about changes and new features, such as the ribbon, the new page editing interface, and interactive calendars. Also, let them know about possible issues that they can expect. For instance, they might have issues with customizations, such as pages not displaying correctly. For information about general upgrade issues, see Troubleshoot upgrade issues (SharePoint Foundation 2010).
If you choose to preserve the look and feel of existing SharePoint sites, explain to site collection owners and site owners that the user interface will not change during upgrade, and tell them about the choices they can make.
By default, site owners have control over their sites. They can use the Preview New Visuals option (under Site Settings) to preview the new user interface and then switch between the previous and new user interface. This gives them time to ensure that everything works correctly, and they can fix any issues with their pages that appeared after upgrade. When site owners are ready, they can update their sites to the new user interface. However, site collection owners can choose to finalize the new user interface, which overrides the control that site owners have over visual upgrade for their sites. If site collection owners want to keep the previous user interface for their site collection, they also have an option to hide visual upgrade settings from site owners.
Site owners also need to know that if they make changes in the new user interface while they are in preview mode and then switch back to the previous user interface, this information may not display correctly.
We recommend that you have a plan and set a time limit for how long the previous user interface should be used in your SharePoint deployment. For example, each site collection administrator may be given 90 days to work with his or her site owners to transition from the previous to the new user interface. This time limit ensures that users are given a reasonable time to become familiar with the new user interface and to resolve any issues that might have occurred during the upgrade. Ensure that you communicate the time limit to the users, and that they know you can force through an upgrade of all sites. Also, you can view the current status of the user interface of upgraded sites to monitor the progress of these sites. For more information, see Manage visual upgrade (SharePoint Foundation 2010).
If site collection owners decide to use the new user interface for all sites within their site collection, they cannot change their minds. However, as a farm administrator, you can change these settings by reverting sites to the previous user interface with Windows PowerShell or SharePoint Object Model. For more information, see Manage visual upgrade (SharePoint Foundation 2010).
It is important to tell site collection owners and site owners that as long as sites use the previous user interface, new features—such as the ribbon, in-place editing for Wiki pages, interactive calendars, and list relationships—will not be available. However, once sites switch to the new user interface, application features automatically appear. Also, it is important to note that all new sites created after the upgrade use the new user interface by default.
-
Known issues
There are a few known issues to consider:
If you use SharePoint Foundation 2010, ensure that you use the same version and service pack of SharePoint Designer.
-
See Also
Upgrade in place to SharePoint Foundation 2010
-
-
Testing and troubleshooting upgrade (SharePoint Foundation 2010)
Before you upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, you should take time to test your upgrade process and understand what issues you might face in your actual upgrade. This section includes information about how to test upgrade and use the information from that test to predict how much time and how much space you will need for upgrade, and what steps you can take to clean up your environment before you perform your actual upgrade.
During and after upgrade, use the articles in this section to address any issues and resume the upgrade process.
In this section:
Best practices for testing upgrade (SharePoint Foundation 2010)
Follow these best practices to get the most out of your upgrade testing.
Use a trial upgrade to find potential issues (SharePoint Foundation 2010)
Find out how to plan for success by testing upgrade by using your actual data in either a physical or virtual environment.
Estimate how long the upgrade process will take and the space that you need (SharePoint Foundation 2010)
Use your test information to understand how long your upgrade will take.
Cleaning up your environment before upgrade (SharePoint Foundation 2010)
Upgrade runs more smoothly when you prepare your environment by cleaning up extra sites or data. This article lists common things that you should consider cleaning up before you start the upgrade process.
Troubleshoot upgrade issues (SharePoint Foundation 2010)
Follow these recommendations to troubleshoot any issues that occur during upgrade. You can also look up common issues and find out how to address them.
Recovering after a failed upgrade (SharePoint Foundation 2010)
If you created a backup of your environment and databases before you began an in-place upgrade, or if you set your environment to read-only before you began a database attach upgrade, you can recover your environment if the upgrade process fails.
Resume upgrade (SharePoint Foundation 2010)
If you encounter errors during upgrade, you can address them by using the troubleshooting article, and then use this article to restart or resume upgrade.
In addition, the following resources can be helpful when you test your upgrade process:
SharePoint Products 2010 Upgrade Worksheet
Use this worksheet to record information about your environment while you test your upgrade. Download the worksheet from http://go.microsoft.com/fwlink/?LinkId=179928 (http://go.microsoft.com/fwlink/?LinkId=179928).
Microsoft SharePoint 2010 Products – Test Your Upgrade Process model
This poster has a visual display of information about testing your upgrade process. Download the poster from http://go.microsoft.com/fwlink/?LinkId=166303 (http://go.microsoft.com/fwlink/?LinkId=166303).
-
Best practices for testing upgrade (SharePoint Foundation 2010)
To understand your environment before you try to perform an upgrade, and to plan accurately for the time that an upgrade will require, you should perform one or more trial upgrades. The goal of testing upgrade is to find issues early and address them so that you can have confidence in your process and the outcome when you perform the real upgrade. To perform an accurate and useful test of the upgrade process from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, follow these best practices:
1. Make your test environment as similar as possible to your real environment.
If possible, use the same kind of hardware and configure it by using the same settings, the same URLs, and so on. The more you can minimize the differences between your test environment and your real environment, the better. The more differences you introduce, the more time that you are likely to spend time tracking down unrelated issues to make sure that they will not occur during the actual upgrade.
2. Know what is in your environment. Do a full survey first.
Take the time to document the hardware and software that is present in your environment, what server-side customizations are installed and used, and where, and what settings you need. This will help you plan more fully, and also help you recover if upgrade fails. A worksheet is available so that you can record information about your environment while you prepare for upgrade. Download the worksheet from http://go.microsoft.com/fwlink/?LinkId=179928 (http://go.microsoft.com/fwlink/?LinkId=179928).
3. Use real data.
Use copies of your actual databases to run the tests. When you test by using real data, you can identify any trouble areas and also determine your upgrade performance. It also gives you the opportunity to measure how long different upgrade sequences and actions take on different kinds of data. If you cannot test all the data, test a representative subset of the data to make sure that you have uncovered any issues with the different kinds and sizes of sites, lists, libraries, and customizations that are present in your environment.
4. Run multiple tests.
A single test can tell you whether you will encounter big problems, but multiple tests will help ensure that you have uncovered all the issues that you might face and can also give you a more accurate timeline for the process. By running multiple tests, you can determine which upgrade approaches will work best for your environment, which downtime mitigation techniques you should plan to use, and how the process or performance may change after you address the issues that you uncovered in your first tests. Your final test pass can help you validate whether you have addressed all of the errors and are ready to upgrade your production environment.
5. Do not ignore warnings.
Even though it is not an error, a warning can lead to problems later in the upgrade process. Work through errors, yes, but also investigate any warnings to make sure that you know what the effect of that warning might be.
6. Test the upgraded environment, not just the upgrade process.
Check your service applications and services. Run a search crawl and review the log files. Verify that the My Site Web sites are working.
7. Verify sites in both Visual Upgrade modes.
Do not assume that because the site can be previewed well in one mode that it will work correctly in the other mode. Check both the previous version and new version user experience.
8. Consider a preview environment.
You can create a preview environment in which your users can verify their sites after a test upgrade, so that they can help you verify the upgrade and find issues. You can use a read-only environment, or you can let your users make changes but warn them that any changes they make will not be saved. Consider limiting this preview environment to a small set of representative sites, and limiting access to interested parties only, to reduce the time that you will need to host the preview environment and the amount of feedback you receive.
For more information about how to test upgrade, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010) and the “Test your upgrade process” poster available at http://go.microsoft.com/fwlink/?LinkId=166303 (http://go.microsoft.com/fwlink/?LinkId=166303).
-
Use a trial upgrade to find potential issues (SharePoint Foundation 2010)
Before you begin the process of upgrading from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, you will want to test the upgrade process to make sure that you know exactly what you have to do to have a successful upgrade. By using a trial upgrade to test the process, you can find out:
What customizations you have in your environment, so that you can plan for how to deal with them during upgrade.
Whether you should upgrade your hardware to make your upgrade run more efficiently and more quickly.
The timing for your upgrade, or how long upgrade will take for your environment.
What you need to plan for, operationally — for example, resources to have available.
In addition, you can use the trial upgrade to become familiar with the upgrade tools and the process itself, so that you know what to expect when you go through the actual process. Through testing, you can find out:
Which special cases apply to your environment and which upgrade approach will be most efficient for you?
What does the upgrade user interface look like? How do you know when you have finished one phase and are moving through another?
Where are the log files, and how do you read them? What information do they provide?
Which techniques can you use to mitigate downtime?
This article provides basic steps for testing upgrade, and it gives recommendations for reviewing the results and adjusting your upgrade plans based on what you learn during the tests.
In this article:
Identify and install customizations
Copy real data to the test environment and try the upgrade
Adjust your plans and test again
In addition, the following resources can be helpful when you test your upgrade process:
SharePoint Products 2010 Upgrade Worksheet
Use this worksheet to record information about your environment while you test your upgrade. Download the worksheet from http://go.microsoft.com/fwlink/?LinkId=179928 (http://go.microsoft.com/fwlink/?LinkId=179928).
Microsoft SharePoint 2010 Products – Test Your Upgrade Process model
This poster has a visual display of information about testing your upgrade process. Download the poster from http://go.microsoft.com/fwlink/?LinkId=166303 (http://go.microsoft.com/fwlink/?LinkId=166303).
-
Set up a test environment
You can use either virtual or physical hardware to test the upgrade process. Every environment is unique, so there are no general guidelines for how long upgrade will take or how difficult a particular customization will be to upgrade. The best way to gauge how your upgrade will go is to perform a series of trial upgrades.
When you create your test environment:
Make your test farm as similar as possible to your real farm — for example, hardware, software, and space available.
Use the same URLs in your test farm as in your real farm. (Otherwise, you will waste time diagnosing issues relating to the URLs that will not come up in the real upgrade.)
Be sure that you transfer all of your settings and customizations to the test environment. The section Identify and install customizations provides information about gathering this information.
-
Using a virtual test environment
When you test by using a virtualized environment, you do not need a lot of hardware. You can replicate your environment by using just two servers that are running Hyper-V. One server has images for the front-end Web servers and application servers, and the other server has images for the database servers.

-
Using a physical test environment
When you test by using a physical environment, you need to replicate your entire server farm environment as closely as possible. If you simplify the number of front-end Web servers, application servers, or database servers too much, you will not have an accurate estimate of how long the upgrade process will take and you may not account for complications that arise from interactions between servers in the same role (such as SQL Server transactions). If you have multiple servers in a role in your original farm, use at least two servers for that role in the test farm to test for such issues.

-
Additional test environments for database attach upgrade
If you are using the database attach upgrade approach, you might need to create one additional test environment: a single server farm that is running Windows SharePoint Services 3.0 that you can use to run the pre-upgrade checker before you attempt to upgrade the data.
You can avoid this step by running the pre-upgrade checker on your existing production farm.
-
-
Identify and install customizations
To have an accurate test process, you must find all the customizations in your current environment and copy them to the test environment. For more information about the types of customizations you need to identify, see Determine how to handle customizations (SharePoint Foundation 2010).
Use the pre-upgrade checker to identify site definitions, site templates, and features in your environment.
The pre-upgrade checker steps through each site collection and generates a report about the state of each site. It also saves list definition information for each list. You can review the reports to find issues and address them before you start the upgrade process. Unlike the pre-upgrade scan tool for Windows SharePoint Services 3.0, the pre-upgrade checker is a read-only tool and does not change your sites. For more information about this tool and steps for running it, see Pre-upgrade scanning and reporting for future releases (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/dd793607(Office.12).aspx) and Run the pre-upgrade checker (SharePoint Foundation 2010).
Use the Stsadm –o enumallwebs operation on all content databases in your Windows SharePoint Services 3.0 environment to identify specific customizations in subsites. This operation lists an ID for each site collection and subsite in your environment and the templates that the site relies on. This operation was first introduced in Windows SharePoint Services 3.0 with Service Pack 2 (SP2). For more information, see Enumallwebs: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/dd793606(Office.12).aspx).
Use a tool such as WinDiff (a tool that is provided with most Microsoft operating systems) to compare your production environment servers with your test farm servers. You can use this tool to see which files exist on your servers and the differences between them.
Check the web.config files for any changes, and look in the SafeControls element to find any custom controls.
Use the SharePoint Diagnostics Tool (SPDiag) to find deployed solutions. For more information, see SharePoint Diagnostics Tool (SPDiag) (http://technet.microsoft.com/en-us/library/dd745013(Office.12).aspx).
Create a list of all customizations that you find. Identify the source of the customizations, if possible. For example, are there third-party add-ins or templates that were customized in-house? After you identify the source, you can then check for updated or upgraded versions of the customizations. A worksheet is available that you can use to fill in information about your environment, based on the data you find in the results from the pre-upgrade checker and in your research on your customizations. Download the worksheet from http://go.microsoft.com/fwlink/?LinkId=179928 (http://go.microsoft.com/fwlink/?LinkId=179928) and customize it to suit your needs.
Tip
Whom do you contact about customizations that you did not create?
After you identify all the customizations, copy them to the appropriate servers in your test farm. You can use the Windows PowerShell cmdlet test-spcontentdatabase before you attach a database to SharePoint Foundation 2010 to determine whether any customizations are missing from the environment. Run this command for each database after you restore the databases to your database server, but before you run the upgrade. Note that this cmdlet runs silently — it will not return any output unless there is an error.
-
Copy real data to the test environment and try the upgrade
You cannot achieve your testing goals unless you use your actual data. You can use the following methods to create a copy of your data:
For in-place upgrade, create a farm backup and then restore it to the test environment. For more information, see Back up and restore the entire farm (Windows SharePoint Services 3.0 technology) (http://technet.microsoft.com/en-us/library/cc288019(Office.12).aspx).
For database attach upgrade, you need to use the Microsoft SQL Server backup and restore tools to create a copy of your content databases and any other databases that you want to upgrade. For more information, see Back up and restore content databases (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc719751(Office.12).aspx).
There is no better way to tell what may come up during upgrade than to perform the test on a copy of all of your data; however, this might not always be a realistic option for initial testing. You can phase the testing by testing one database at a time (if the databases are large) so that you can make sure you test whatever is unique about that data set, or you can assemble a subset of data from representative sites in your environment. If you want to first test by using a subset of your data, be sure that the subset has the following characteristics:
The data subset contains sites that are typical of the sites you support in your environment.
The size and complexity of the data subset is very similar to the actual size and complexity of your environment.
Important:
Testing a subset of your data does not produce a valid benchmark for how long it will take to process the entire volume of data for your environment.
After copying the data, take a first pass through the upgrade process to see what happens. This is just the preliminary round.
-
Try in-place upgrade
If you want to try an in-place upgrade approach, use the following steps to try out the upgrade process:
1. Create a backup of your farm.
2. Restore the backup to your test farm.
For more information, see Back up and restore the entire farm (Windows SharePoint Services 3.0 technology) (http://technet.microsoft.com/en-us/library/cc288019(Office.12).aspx).
3. Run the pre-upgrade checker. Make note of any issues it finds. You will want to address these issues in your original environment before you run the actual upgrade on your product farm. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
4. Follow the steps in Perform an in-place upgrade (SharePoint Foundation 2010) to try the in-place upgrade.
5. Review the results.
-
Try a database attach upgrade
1. Create a SQL Server backup of your content databases.
2. Use SQL Server to restore the backups into your single-server test farm and attach the content databases to that environment.
For more information, see Back up and restore content databases (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc719751(Office.12).aspx).
3. Run the pre-upgrade checker. Make note of any issues it finds and any changes it makes. You will want to address these issues and make these changes in your original environment before you run the actual upgrade on your product farm. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
4. Follow the steps in Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade to configure the test environment for a database attach upgrade.
5. Follow the steps in Attach databases and upgrade to SharePoint Foundation 2010 to try the database attach upgrade process.
-
-
Review your results
After your test upgrade has been completed, you can review the results and revisit your plans. Look at the log files, look at the upgraded sites, and check out your customizations. How did upgrade work for your environment? What did you find out? What do you need to rethink about your upgrade plan?
-
Review the log files
Review the following log files:
The pre-upgrade checker log file.
The log files for the pre-upgrade checker (stsadm -o preupgradecheck) are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS. The log files are named in the following format: PreUpgradeCheck_YYYYMMDD-HHMMSS-SSS–random-number.log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds) and the random number is used to differentiate between possible simultaneous attempts to run the pre-upgrade checker.
The SharePoint Products Configuration Wizard (Psconfig.exe) log file (generated when you run this wizard as part of your trial in-place upgrade).
The PSCDiagnostics log files are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\14\LOGS.
The upgrade log file and the upgrade error log file (generated when you run the upgrade).
The upgrade log file (.log) and the upgrade error log file (.err) are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\14\LOGS. The log files are named in the following format: Upgrade-YYYYMMDD-HHMMSS-SSS.log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds).
To review the log files to find and troubleshoot issues. start at the top of the files. Errors or warnings may be repeated if they occur for several site collections in the environment, or if they block the upgrade process altogether. For example, if you cannot connect to the configuration database, the upgrade process will try (and fail) several times and these attempts will be listed in the log file.
Search, or visually scan, for the following entries:
Finished upgrading SPFarm Name=<Name of Configuration Database>
In-place upgrade session finishes. Root object = SPFarm=<Name of Configuration Database>, recursive = True. 0 errors and 0 warnings encountered.
If you find these entries, the installation was successful.
If you do not find the entries from the previous step, you can identify specific issues that may have contributed to the failure by searching, or visually scanning, through the Upgrade.log file for the following terms:
Search for ERROR in the log files to find any failures (such as failing components or faulty database connections).
Search for WARNING to find issues such as missing features or components.
To find upgrade issues, you may find it useful to use a log parser to run queries against the log files.
-
Restart upgrade, if necessary
During a database attach upgrade, any sites that cannot be upgraded will be skipped. During an in-place upgrade, if the server restarts or the upgrade fails, you will need to restart the upgrade process to upgrade the remaining sites.
To see whether any sites were missed or skipped during upgrade, run the following Stsadm operation stsadm -o localupgradestatus on every front-end Web server in your SharePoint Foundation 2010 server farm. For more information about this operation, see Localupgradestatus: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc289007.aspx).
If the upgrade skipped any site collections, you can restart the upgrade process for the database that contains that site collection by using the following Windows PowerShell cmdlet: upgrade-spcontentdatabase -id <GUID>. For more information about this cmdlet, see Upgrade-SPContentDatabase (http://technet.microsoft.com/library/9c7f1a52-02a7-452d-9746-a4e89aa54874(Office.14).aspx).
For more information, see Resume upgrade (SharePoint Foundation 2010).
-
Review upgraded sites
Review your upgraded sites to identify any issues that need to be addressed before you run the upgrade process on your production environment. For more information about specific things to look for, Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
-
-
Adjust your plans and test again
Repeat the testing process until you are sure that you have found all the issues that you may face and that you know how to deal with them. Your goal is to know what your plan is if it is 4:00 P.M. on Sunday, you have to be back online Monday morning, and it is not going well. Is there a point of no return? Test your rollback plan and make sure that it works before you begin your real upgrade.
-
Estimate how long the upgrade process will take and the space that you need (SharePoint Foundation 2010)
An important part of planning your upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 is determining how long the upgrade process will take and how much storage space will be required. Every environment is unique and includes different hardware capabilities and different site characteristics. The space and the length of time that you need to run an upgrade will vary greatly depending on your environment. The best way to estimate these factors is to perform a trial upgrade, and then review the space and time that it took. For more information about how to perform a trial upgrade, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010).
In this article:
-
Estimate the space that you need for the upgrade
During both the in-place upgrade and database attach upgrade approaches, the databases might expand during upgrade. Also, many transactions take place while the upgrade process runs, so you must make sure that the log files have room to expand to accommodate the changes that are occurring. You have to plan for growth in both the databases and the log files.
When planning your upgrade, make sure that your current environment follows the best practices for storage for Windows SharePoint Services 3.0 so that you have the best experience and performance during upgrade. For more information, see Physical storage recommendations (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc298801.aspx). You should also review the best practices for SharePoint Foundation 2010 and make any adjustments needed to your upgraded environment.
Because of the changes in table structures in the new version, the databases grow temporarily while the data is reorganized. This space can be recovered after upgrade, but you should ensure that there is room for the databases to grow up to 50 percent larger than their current sizes during either an in-place or database attach upgrade (be aware that after upgrade, you can reduce the database again to recover much of this space). You should also make sure that there is room on your database servers for your databases to grow over time with typical use. To find out how large your databases currently are, use Enterprise Manager in Microsoft SQL Server. In addition to database space, you also must have room for the following items:
The temporary databases. Ensure that you have enough database space to enable quick growth of the temporary databases. If you have insufficient space, the upgrade process might time out and the upgrade will fail.
The upgrade log files.
The transaction log files for the databases. These log files must grow quickly to accommodate the number of changes occurring in the databases.
Note:
In very large environments, there is a possibility that the default growth rate for the transaction log files (10 percent) is not enough to keep up with the upgrade process; this can cause a time-out. Again, a trial upgrade is the best way to determine whether the transaction log files can keep up with the upgrade process. If your environment is very large, or if the process timed out during a trial upgrade, consider expanding the SQL Server transaction log files beforehand to make sure you have room for the number of transactions that must be processed. For more information about how to expand the SQL Server transaction logs, see Expanding a Database (SQL Server 2005) (http://go.microsoft.com/fwlink/?LinkId=182619) or Expanding a Database (SQL Server 2008) (http://go.microsoft.com/fwlink/?LinkId=182620).
-
Estimate how long the upgrade will take
With your disk space estimates in hand, and some testing under your belt, you can now calculate a rough estimate of how long the actual upgrade process will take. Upgrade times vary widely among environments. The performance for an upgrade depends greatly on the hardware being used, the complexity of the sites, and the particular characteristics of your implementation. For example, if you have many large document libraries, these may take longer to upgrade than a simpler site.
Factors that influence performance are described in the following table.
Content factors
Hardware factors
The number of:
Site collections
Subwebs
Lists
Document versions (number and size)
Documents
Links
Plus the overall database size itself.
SQL Server disk input/output per second
SQL Server database to disk layout
SQL Server temporary database optimizations
SQL Server CPU and memory characteristics
Web server CPU and memory characteristics
Network bandwidth and latency
How your data is structured can affect how long it takes to upgrade it. For example, 10,000 lists with 10 items each will have a longer upgrade time than 10 lists with 10,000 items. The actions required to upgrade the list infrastructure must be performed for each list, regardless of the number of items; therefore, more lists equals more actions. The same goes for most of the items in the “content factors” column in the table above.
The structure of your hardware can also have a big effect on performance. Generally, the database server performance is more important than Web server performance, but underpowered hardware or connectivity issues at either tier can significantly affect upgrade performance.
The upgrade approach you have chosen will also make a big difference in how long the process will take. Performing a database attach upgrade is the quickest method (however, the pre-upgrade and post-upgrade steps for this approach take longer than for in-place upgrade). An in-place upgrade takes a little more time because you are upgrading the environment in addition to the sites, but you do not have as many pre-upgrade and post-upgrade steps when you use this approach.
The best way to estimate overall time is to do a trial upgrade of a small part or all of the data, and then review the upgrade log files. The log files contain the duration for your upgrade — look for Total Elapsed Time at the bottom of the upgrade log file. Use this time to project a duration for your full set of content. You can also use the log files to check your progress during the upgrade process. The upgrade.log file is located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\14\LOGS.
The estimate you arrive at based on your trial upgrade is for the actual upgrade process for the data; it does not include all of the steps that you have to perform before and after this step, which can take more time than the upgrade of the data itself. When estimating how long the upgrade will take, in addition to the time that is required for data to be processed, you must also estimate how long the activities during the pre-upgrade and post-upgrade phases will take.
For pre-upgrade steps, consider the following factors:
Creating custom elements Upgrading Web Parts or re-doing custom templates to take advantage of new features will take some time. The process of creating custom elements should begin early, during the evaluation phase of your project.
Backing up the databases For in-place upgrade, you must perform a full backup — not a differential backup — of your entire environment to make sure that you can recover in the remote possibility that the upgrade fails and you must rebuild your server farm. For large environments, this step can take a significant amount of time. In particular, if you are backing up to a network location, network latency issues can slow this process down.
For post-upgrade steps, consider the following factors:
Verifying sites and making changes Allow enough time for users to validate their sites after the upgrade. This may take several days. For more information, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
Additional factors in your environment can also contribute to longer upgrade times, including the following:
Very large document libraries A document library with more than 250,000 documents all in the root of the document library (instead of in folders) will take a long time to upgrade, and the upgrade might not be successful. Following the Windows SharePoint Services 3.0 guidelines for using folders to break up large document libraries can help you manage the library size. For example, if you rearrange the same document library so that the 250,000 documents are divided into 125 folders, it should upgrade more easily.
Very large databases Databases larger than 100 GB can take a long time to upgrade.
Note
If you have content databases that are larger than 100 GB you might want to divide them up into smaller databases before you run the upgrade. Larger databases not only take longer to upgrade, but they can make it harder to recover if the upgrade is not completed successfully.
You can use the mergecontentdbs or the backup and restore operations in Stsadm.exe to move sites between databases. For more information, see Mergecontentdbs: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288557(Office.12).aspx) and Backup and restore: Stsadm operations (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288090(Office.12).aspx).
If you have a very large database (more than 100 GB) that you cannot break up because most of the content is in a single site collection, you may want to reconsider your upgrade approach. A database attach upgrade approach is more difficult with very large databases, because backing up and restoring such large databases is problematic.
Caution:
Be sure that you are following the capacity planning guidelines from the previous and new versions before you attempt the upgrade. If you have exceeded the guidelines for best performance, the upgrade process might take longer, or it might not succeed (for example, the process might time out repeatedly on the same large document library). If your deployment does not meet the recommended capacity guidelines, consider whether you need to do some work to meet those guidelines before you try the upgrade. Again, a trial upgrade can help you with that decision.
Communications requirements
You need to notify your users and your team of the upgrade schedule, and give them time to do their tasks. For more information, see Create a communication plan (SharePoint Foundation 2010).
Managing system center alerts and alarms
You need to monitor system performance during upgrade, but you will not need to monitor specific features. Pause any unnecessary alarms and alerts from Microsoft Systems Center Operations Manager or Microsoft Operations Manager, and then turn them on again after upgrade.
Turning SQL mirroring and log shipping on/off
You should turn off mirroring and log shipping before you upgrade, and then turn them on again after you are sure that your environment is running correctly after the upgrade. We recommend that you do not run mirroring or log shipping during upgrade, because this creates additional load on the servers running SQL Server and also wastes resources mirroring or shipping temporary data.
Test your upgrade process to find out how long it may take, then create a schedule for your upgrade operations and test that to determine your timeline. You should include the time that you need to do the pre-upgrade and post-upgrade steps in your operations timeline: If it takes 5 hours to back up your environment before you start, you need to include that time in your outage window. Also include buffer time in case you need to restore or recover — you should determine both your planned outage (realistic case) and your emergency outage (worst case) timelines.
-
Cleaning up your environment before upgrade (SharePoint Foundation 2010)
Before you begin upgrading from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, you should make sure that your environment is functioning in a healthy state and that you clean up any content that you do not have to upgrade. You can also take the time to remove or rearrange content so that you will have the structure that you want after you perform the upgrade.
In this article:
-
Items to clean up
Many of these items can be removed or repaired by using Stsadm.exe commands.
Important:
To run the Stsadm command-line tool, you must be a member of the Administrators group on the local computer.
-
Delete unused or underused site collections and subwebs
You do not want to upgrade content that you do not have to keep. If it has been unused for a long time and will not be needed in the future, back it up, and then delete it to free storage and administrative resources, improve upgrade performance, and reduce upgrade risk. Be sure to communicate with site owners or organizational contacts regarding the site status — you want to make sure that the site is not needed before you delete it (for example, you do not want to delete sites that are required for compliance, such as emergency procedures, even though they may not be updated frequently).
For more information about how to delete site collections and subwebs, see:
Deletesite: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288016(Office.12).aspx)
Deleteweb: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287710(Office.12).aspx)
-
Address large lists
By default, large list query throttling is applied after an upgrade to SharePoint Foundation 2010. If a list is very large, and users use a view or perform a query that exceeds the limit or throttling threshold, the view or query will not be permitted. Check any large lists in your environment and have the site owner or list owner address the issue before upgrade. For example, they can create indexed columns by using filtered views, organize items into folders, set an item limit on the page for a large view, or use an external list. For more information about how to address issues with large lists, see Manage lists and libraries with many items (http://go.microsoft.com/fwlink/?LinkId=182370) on Office Online.
-
Address large numbers of site collections in a content database
If you have 5,000 or more site collections in a database, consider breaking them out into multiple databases. In Windows SharePoint Services 3.0, there was a default warning at 9,000 site collections and a hard limit at 15,000 site collections. In SharePoint Foundation 2010, these values change to 2,000 site collections for the warning and 5,000 site collections for the limit. To avoid errors during upgrade or broken sites after upgrade, we recommend that you move some site collections into separate databases. If you have multiple content databases, you can also speed up your upgrade process by upgrading multiple databases in parallel.
For more information about moving site collections to a new database, see Move site collections to a new database (split a content database) (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc825327(office.12).aspx).
-
Address large ACLs
Using item-level permissions frequently can result in large access control list (ACL) entries, which can in turn create performance problems on your servers. For information about this issue and for tips on how to handle lots of users, see Knowledge Base Article 953132: How to add lots of users to a site, to a list, or to a document library in Windows SharePoint Services 3.0 and in SharePoint Server 2007 (http://go.microsoft.com/fwlink/?LinkId=182327).
-
Remove extraneous document versions
Large numbers of document versions can slow down an upgrade significantly. If you do not have to keep multiple versions, you can have users delete them manually or use the object model to find and remove them. For more information about how to programmatically remove extraneous versions, see Versions Web Service (http://go.microsoft.com/fwlink/?LinkId=182330) on MSDN.
-
Remove unused templates, features, and Web Parts
First, verify that no sites are using the template, feature, or Web Part. You can use the pre-upgrade checker (Stsadm -o preupgradecheck) and the Stsadm -o EnumAllWebs operation to identify these customizations in your environment. Both of these operations were updated in the October 2009 Cumulative Update (CU) and now identify Web Parts, features, event handlers, and setup files that are being used in your environment. The pre-upgrade checker specifies which server-side files exist in your environment and how many times they are used. The EnumAllWebs command specifies which files are used by which sites.
For more information about how to identify customizations in your environment, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010). If customizations are not being used, delete them. For more information about how to manage these kinds of customizations, see Features and Templates (http://go.microsoft.com/fwlink/?LinkId=182338) and Solutions and Web Part Packages (http://go.microsoft.com/fwlink/?LinkId=182332) on MSDN.
-
Repair data issues
Make sure that you repair any issues in your databases or site content before you upgrade. In particular, check the following items:
Check databases for corrupted data
Clean up your databases to remove any orphaned sites or other corrupted data, such as a corrupted list. Consider defragmenting if you have removed sites or subsites from the database. For more information, see:
Databaserepair: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288636.aspx)
Forcedeletelist: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287949(Office.12).aspx)
Check databases for duplicate or orphaned site collections
Make sure that site collections exist in only one content database. Occasionally, site collections can leave behind duplicate or orphaned references in old content databases if they are moved to new ones, or if a duplicate copy of a database was attached to the farm, or if there was an error when a site collection was provisioned. If a site collection is referenced in more than one content database or there is more than one instance of the site collection in a content database, it can cause issues when you upgrade by using the database attach upgrade method. If you upgrade a duplicate version of the site collection first, the site map in your configuration database might end up pointing to that version of the site rather than the current version.
Before you upgrade, use the pre-upgrade checker tool to identify all site collections and look for any duplicate or orphaned sites – any sites with the same URL or the same GUID as another site. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010). Also, use the enumallwebs operation in Stsadm.exe to find out which sites are in which content databases and compare the results. For more information, see Enumallwebs: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/dd793606(office.12).aspx). If you find duplicate or orphaned sites, you can use the deletesite operation in Stsadm.exe to remove the duplicate or orphaned sites from the database. To delete a site from a specific content database, use the following command:
Stsadm -o deletesite -force -siteid <SiteID> -database <databasename> –databaseserver <Servername>
For more information, see Deletesite: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288016(office.12).aspx).
-
-
Making structural changes
If you want to make structural changes to your environment, such as moving site collections around or changing how your databases are allocated, you can use the following methods:
Stsadm -o mergecontentdbs Use this to move site collections between databases. Upgrade is most efficient when databases contain similar data. Therefore, it is best if any site collections that share a content database are similar types. You can also use this operation to divide large databases if they contain multiple site collections. This can also help increase upgrade efficiency.
For more information, see Mergecontentdbs: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288557(Office.12).aspx).
Export and import sites Use this method to move subwebs or site collections within a farm or between farms. For more information, see Import and export: Stsadm operations (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288191(Office.12).aspx).
-
Troubleshoot upgrade issues (SharePoint Foundation 2010)
Even after you test the upgrade process to identify potential issues, you might experience unexpected issues during an upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010. If you experience issues after upgrade, the sooner you detect and fix them, the better the end-user experience will be.
This article describes general principles for identifying and addressing upgrade issues, and includes a list of common issues. After you have identified and addressed the issues, you can resume upgrade. For more information about how to resume upgrade, see Resume upgrade (SharePoint Foundation 2010).
In this article:
General principles for identifying issues
Missing or deprecated server-side files or customizations
Incorrectly configured or missing settings for server farm, Web application, or services
Inconsistent or incorrect update levels
Missing global navigation for blogs
.Stp files are not working after upgrade
Cannot find new versions of the Fabulous 40 application templates
-
General principles for identifying issues
Start by checking the upgrade status to see where upgrade stopped (if it did stop), and check log files to find any errors or warnings. Next, address the issues that you find before you resume the upgrade.
-
First, check upgrade status and log files
Upgrade status indicators and log files should give you an indication of what went wrong during the upgrade process. We recommend that you carefully review all the errors that were logged in the upgrade log files. Warnings might not always indicate an issue, but you should review them all to determine whether any of them are likely to cause even more issues.
1. Check upgrade status by doing one or both of the following:
Review the Upgrade Status page in the SharePoint Central Administration Web site.
Use the Stsadm.exe operation localupgradestatus to check upgrade status.
For more information about how to check upgrade status, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
2. Review the following log files:
The Setup.exe log file.
The SharePoint Products Configuration Wizard (Psconfig.exe) log file.
The upgrade error log file and the upgrade log file (which contains more detailed information than the upgrade error log file).
ULS or trace log files.
These files are stored in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\LOGS folder and are named Servername_YYYYMMDD–MMSS.log.
The application event log file.
This file can be viewed by using the Event Viewer.
For more information about the Setup.exe, PSconfig.exe, and upgrade log files, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010). For more information about the trace log file, see Trace Logs (http://go.microsoft.com/fwlink/?LinkId=182380) on MSDN.
-
Then, address issues in order
Some issues have more effect than others. For example, a missing server-side file can cause many seemingly unrelated errors at the site level.
Address issues in the following order:
1. Missing server-side files or customizations, such as features or Web Parts.
2. Configuration issues in the server farm, Web application, or services, such as managed paths or services that are not started.
3. Additional issues that you discover on a site-by-site basis, starting with high-impact, high-profile sites.
As you identify and fix the top-level issues, you can try running upgrade again to see whether any issues further along in the upgrade process have also been fixed.
-
-
Common issues
Check to see whether any of the following issues are causing an upgrade error or warning.
One common error during upgrade is missing server-side files — either files that were installed with Windows SharePoint Services 3.0 or customized files. When you prepared for upgrade, you should have created an inventory of the server-side customizations (such as site definitions, templates, features, Web Parts, assemblies) that your sites required. (The pre-upgrade checker can help identify these items.) Check this inventory to make sure that all the files that are needed for your customizations are installed in your upgrade environment.
If you are performing a database attach upgrade, you can use the test-spcontentdatabaseWindows PowerShell cmdlet before you upgrade the database to identify any missing files. You can also use the enumallwebs operation in Stsadm.exe to identify server-side customizations that are being used.
In the upgrade log files, you may see errors such as the following:
ERROR Found Reference Count web(s) using missing web template Site Template Identifier (lcid: Site Template Language Code) in ContentDatabase Content Database Name.
ERROR Found a missing feature Id = [Feature Identifier]
ERROR File [Relative File Path] is referenced [Reference Count] times in the database, but is not installed on the current farm.
WARNING WebPart class [Web Part Identifier] is referenced [Reference Count] times in the database, but is not installed on the current farm.
WARNING Assembly [Assembly Path] is referenced in the database, but is not installed on the current farm.
WARNING Feature could not be upgraded. Exception: Feature definition id ‘Feature Identifier’ could not be found.
If you can obtain a missing server-side file or dependency, install it and then run upgrade again for the affected sites. If the file or dependency (such as a Web Part) has been deprecated, you have to investigate whether you want to rebuild the site, page, or Web Part to use a different template, feature, or Web Part. If you can redo the customization by using dependencies that have not been deprecated, you can run upgrade again for the affected sites. If you cannot remove the dependency, you cannot upgrade the site.
After you install the missing file or dependency, use the test-SPContentDatabaseWindows PowerShell cmdlet on a test server to determine whether any other files for that database are missing. If you only run the pre-upgrade checker or run upgrade again, the error might not appear in the log files, even though it might still be occurring.
Verify your farm and Web application settings, and create and start any missing services.
Verify that any managed paths (included or excluded paths) are configured correctly for each Web application.
In the upgrade log files, you may see errors such as the following:
ERROR Template Template Id: SPSite Id=Site Id could not be accessed due to exception. Skipping SPWeb Id=Web Id for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id Site Id could not be found.
This error indicates that a managed path is missing. Add the managed path for the site collection into the Web application and restart upgrade for the content database that contains this site collection.
You must be running Windows SharePoint Services 3.0 with Service Pack 2 to run upgrade. If you do not meet this minimum requirement, you will see an error and upgrade will not run.
Another common error is the global navigation is missing for upgraded blogs. This occurs because the MySiteNavigation (6adff05c-d581-4c05-a6b9-920f15ec6fd9) feature is not enabled during the upgrade. To enable this feature, run the Enable-SPFeatureWindows PowerShell 2.0 cmdlet.
For more information, see Enable-SPFeature (http://technet.microsoft.com/library/9b68c192-b640-4cb8-8a92-a98008169b27(Office.14).aspx).
The following data issues can cause errors or warnings during upgrade:
Connectivity to data sources. If your servers cannot connect to the databases, they cannot be upgraded.
Orphaned sites or lists, or other database corruptions. For more information, see Cleaning up your environment before upgrade (SharePoint Foundation 2010).
Hidden column data. If the upgrade process adds a column to a list, and a custom column that has that same name already exists in the list, the custom column is renamed. After upgrade, you might have to readjust your views to include the renamed column.
In the upgrade log files, you may see errors such as the following:
WARNING The orphaned sites could cause upgrade failures.
ERROR Database [Content Database Name] contains a site (Id = [Site Collection Identifier], Url = [Site Collection URL]) that is not found in the site map.
Fix any orphaned items or database corruptions, and then run upgrade again.
Changes to the user interface (UI), such as the addition of the Fluent UI (also known as the ribbon) or adherence to XHTML standards, can cause problems in sites. Occasionally, custom elements (such as a content type) may have a name that conflicts with a name in the new version. You may also have pages that must be reverted to the standard site definition, or large lists for which you have to create new views.
For more information about how to review UI issues in sites, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
In the upgrade log files, you may see errors such as the following:
Failed to activate site collection features on site Site Url. Exception: A duplicate content type name “name” was found.
This error indicates that a 3rd party “Summary Info” content type was added to the specified site in o12 and during upgrade to o14 it name conflicts with our out of the box “Summary Info” content type. Delete or rename the 3rd party content type in the specified site to something other than “Summary Info” and re-run upgrade.
If you run out of space (for example, for transaction log files on your database servers), upgrade cannot continue. Free some space, or increase the size of the transaction log file before you resume upgrade. For more information, see Managing the Size of the Transaction Log File (http://go.microsoft.com/fwlink/?LinkID=124882).
Additional steps are necessary if you are upgrading an environment that uses forms-based authentication. Follow the steps in Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010) to upgrade forms-based authentication providers.
If you receive an error about an unknown account, or if a database is not upgraded, verify the following:
For an in-place upgrade, make sure that the account that you use to run the SharePoint Products Configuration Wizard is a member of the db_owner fixed database role for all the databases that you want to upgrade. If it is not a member of this role, you might see an error about an unknown user account when the wizard starts to upgrade the databases.
For a database attach upgrade, if you are moving databases between instances of SQL Server, make sure that you verify that security is configured correctly. Check that the accounts that you are using have the appropriate fixed roles and permissions on the databases, and that they will still be valid accounts if you are upgrading across domains.
Site templates (.stp files) are deprecated in SharePoint Foundation 2010 and cannot be used to create new sites. Existing sites that are based on .stp files will continue to function as usual. Solution packages (.wsp files) are the supported method for creating sites that are based on a template in SharePoint Foundation 2010. You can convert an .stp file to a .wsp file to continue to use the template after upgrade.
To convert an .stp file to a .wsp file
1. In Windows SharePoint Services 3.0, create a site that is based on the template, and then upgrade the site to SharePoint Foundation 2010.
2. In SharePoint Foundation 2010, on the Site Actions menu in the upgraded site, click Site Settings.
3. On the Site Settings page, under Site Actions, click Save site as template.
4. On the Save as Template page, enter a File name and Template name, and then click OK.
The site template is saved as a .wsp file to the Solutions Gallery for that site collection and you can create new sites that are based on that solution.
Many people have used the “Fabulous 40” templates that were created for Windows SharePoint Services 3.0. Some of these templates were created as site admin templates (.stp files) and some were created as server admin templates (.wsp files). Microsoft is not releasing new versions of these templates for SharePoint 2010 Products. Also, .stp files are deprecated and cannot be used to create new sites when you upgrade to SharePoint Foundation 2010.
You can upgrade sites that are based on these templates. However, you should try to upgrade these sites in a test environment before you upgrade the production environment so that you can discover any potential issues. Use the pre-upgrade checker to discover any issues. (Some people have seen problems with custom workflows or CAML-based views in the templates.) Note that after upgrade, you will be unable to use .stp files to create new templates.
The following table describes how the templates can be used.
Type of template
Can I upgrade sites that are based on this template?
Can I use the template after upgrade?
Site admin (.stp file or site template)
Yes
No
Server admin (.wsp file or solution package)
Yes*
Yes*
*There are issues with some .wsp files after upgrade. In particular, after upgrade, some customers cannot create new sites that are based on the following templates: Absence Request and Vacation Schedule Management, Call Center, Help Desk, IT Team Workspace, Knowledge Base, and Physical Asset Tracking and Management. If you have problems using any of these templates, you can post an issue to the SharePoint 2010 – Setup, Upgrade, Administration and Operation TechNet Forum (http://go.microsoft.com/fwlink/?LinkId=201600), or contact Microsoft Customer Support.
If you want to continue to create sites that are based on the site admin templates (.stp files) in SharePoint Foundation 2010, you must convert them to solution packages (.wsp files). For more information, see the section .Stp files are not working after upgrade earlier in this article.
-
See Also
Use a trial upgrade to find potential issues (SharePoint Foundation 2010)
Verify upgrade and review upgraded sites (SharePoint Foundation 2010)
-
-
Recovering after a failed upgrade (SharePoint Foundation 2010)
If the upgrade to Microsoft SharePoint Foundation 2010 has failed and you do not have time to continue to troubleshoot the issues or resume the upgrade process, you have to recover your Windows SharePoint Services 3.0 environment. The steps differ depending on the type of backup you have. If you were performing a database attach upgrade and you kept your original environment available — either by using read-only databases or by taking the environment offline — you can recover your environment easily. If you were performing an in-place upgrade, you must recover your entire environment and restore the data.
If you do have time, you should troubleshoot the issues and resume upgrade. For more information, see Troubleshoot upgrade issues (SharePoint Foundation 2010) and Resume upgrade (SharePoint Foundation 2010).
In this article:
Recovering when you have read-only databases on a standby environment (database attach upgrade)
Recovering when you have a full environment backup (in-place upgrade)
Recovering when you have database backups (in-place upgrade)
-
Recovering when you have read-only databases in a standby environment (database attach upgrade)
When you perform a database attach upgrade, you can choose to leave your existing environment available, but with the databases set to read-only. Recovering when you are in this state is the simplest recovery path, because your original environment is still available, it is merely set to read-only. If you have to recover your environment, you can merely switch the databases to read/write again and resume serving requests. The article Run a farm that uses read-only databases (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/ee845027(Office.12).aspx) describes the steps you take to set a farm to use read-only databases. To return the read-only farm to full operations, you set the Database Read-Only entry back to False, and then re-enable the timer jobs listed in the article.
-
Recovering when you have a full environment backup (in-place upgrade)
If you created a full backup of your environment before you started the upgrade process, you can restore that full backup to recover your environment. For more information about how to restore from a full backup, see Restore a farm by using built-in tools (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc288668(Office.12).aspx).
-
Recovering when you have database backups (in-place upgrade)
If you only created backups of your content databases, you can still recover your environment, but it will take longer and involve more steps. You basically have to build out your environment again and then restore the database backups. For more information about how to recover an environment and restore backed up content databases, see Restore a farm after a configuration database problem (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc512814(Office.12).aspx).
-
Resume upgrade (SharePoint Foundation 2010)
In some cases, you might have to restart upgrade to finish upgrading your sites from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010. For example:
During an in-place upgrade, if the server restarts or the upgrade fails, you must restart the upgrade process by using Psconfig.exe to upgrade the remaining sites.
During a database attach upgrade, any sites that cannot be upgraded will be skipped. After you have corrected any issues in the sites (such as a missing template or language pack, or the site being set to read-only or having exceeded its quota), you can restart upgrade by using a Windows PowerShell command to upgrade just the skipped sites.
Note:
One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Be sure that any custom elements that you need are installed on your front-end Web servers before you begin the upgrade process. You can use the pre-upgrade checker — and, for a database attach upgrade, the test-spcontentdatabaseWindows PowerShell cmdlet — to identify any custom elements that your sites might be using. For more information, see Identify and install customizations in the article “Use a trial upgrade to find potential issues.”
In this article:
Restart upgrade for a server farm by using Psconfig.exe
Restart upgrade for a database by using Windows PowerShell
-
Restart upgrade for a server farm by using Psconfig.exe
If you determine that upgrade stopped or failed before the SharePoint Products Configuration Wizard was completed, you can restart the upgrade from that point by running the SharePoint Products Configuration Wizard again or by using a command line operation. This process is also known as forcing a software upgrade. Be sure to research and address the problem that caused the failure or stoppage before you restart upgrade.
To restart upgrade for the server farm
1. Verify that you have the following administrative credentials:
To use Psconfig.exe, you must be a member of the local Administrators group on the server.
2. Open a Command Prompt window and navigate to the following directory:
%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\14\Bin\
3. Type the following command:
psconfig -cmd upgrade -inplace v2v -passphrase <passphrase> -wait
There is an optional parameter, -force, that can force the upgrade to continue if the command does not work. Add -force to the end of the command string to force the upgrade process to continue.
Note:
You can enable Windows Installer logging before you start the software upgrade installation again. To enable logging for Windows Installer, see Microsoft Knowledge Base article 99206: How to enable Windows Installer logging (http://go.microsoft.com/fwlink/?LinkID=99206).
-
Restart upgrade for a database by using Windows PowerShell
If the upgrade skipped any site collections during in-place upgrade or database attach upgrade, you can restart the upgrade process for the database that contains that site collection by using a Windows PowerShell cmdlet.
To restart upgrade for a database by using Windows PowerShell
1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt (PS C:\>), type the following command:
upgrade-spcontentdatabase -id <GUID>
Where GUID is the identifier for the database. You can run the following cmdlet to find the GUID for a content database:
Get-SPContentDatabase -Identity<content_database_name>
For more information, see Upgrade-SPContentDatabase (http://technet.microsoft.com/library/9c7f1a52-02a7-452d-9746-a4e89aa54874(Office.14).aspx).
-
Perform pre-upgrade steps (SharePoint Foundation 2010)
After you have planned your upgrade process to Microsoft SharePoint Foundation 2010, you can start the upgrade process by following the required pre-upgrade steps.
In this section:
Run the pre-upgrade checker (SharePoint Foundation 2010)
The pre-upgrade checker identifies potential upgrade issues in your environment. Run this as you plan your upgrade and before you start the upgrade process, so that you can address these issues.
Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010)
Create a full backup of your environment to ensure that you can recover if upgrade does not go as planned.
-
Run the pre-upgrade checker (SharePoint Foundation 2010)
You can use the pre-upgrade checker to report on the status of your environment and SharePoint sites before you upgrade to Microsoft SharePoint Foundation 2010. We highly recommend that the server administrator run the pre-upgrade checker and resolve as many problems as possible before scheduling the upgrade.
The pre-upgrade checker is an Stsadm operation that you run in a Windows SharePoint Services 3.0 environment to find any potential issues for upgrade and to review recommendations and best practices. The operation is available with Windows SharePoint Services 3.0 Service Pack 2 and has been updated in the October 2009 Cumulative Update for Windows SharePoint Services 3.0. You can download and install the October 2009 Cumulative Update from October 2009 Cumulative Update Packages for SharePoint Server 2007 and Windows SharePoint Services 3.0 are published (http://go.microsoft.com/fwlink/?LinkID=169179).
Note:
You might need to run the pre-upgrade checker more than once. For example, if you run the tool to evaluate your server farm but do not perform the upgrade for a few weeks, you can run the tool again just before you perform the upgrade to scan any new sites and to ensure that no additional issues have appeared in the meantime.
In this article:
About the pre-upgrade checker report
Note:
One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Be sure that any custom elements you need are installed on your front-end Web servers before you begin the upgrade process. You can use the pre-upgrade checker — and, for a database attach upgrade, the test-spcontentdatabaseWindows PowerShell cmdlet — to identify any custom elements that your sites might be using. For more information, see Identify and install customizations in the article “Use a trial upgrade to find potential issues.”
-
About the pre-upgrade checker report
The pre-upgrade checker reports information about the status of your environment and the SharePoint sites in that environment, including:
Upgrade readiness and supported paths Returns a list of all servers and components in the farm and information about whether the servers meet requirements for upgrading.
Alternate access mapping settings Returns a list of the alternate access mapping URLs that are being used in the farm.
Installed elements Returns a list of all site definitions, site templates, features, and language packs that are installed in the farm. You need to know which site templates have been installed or used so that you can verify that they are available after an upgrade or database attach. You also need to know which elements have been customized so you can verify the customizations again after the upgrade. For example, you need to know whether a site depends on a language pack for Windows SharePoint Services 3.0 that does not exist yet for SharePoint Foundation 2010, so you can plan how to handle that site during upgrade.
Unsupported customizations Reports whether any server-side customizations that are not supported (such as database schema modifications) exist in the farm.
Orphaned objects Lists any database or site orphans in the farm. Objects such as list items, lists, documents, Web sites, and site collections can become orphaned — that is, the objects exist but are not associated with a particular site. Because orphaned objects do not work in the previous version, they won’t work after the upgrade. If you perform an in-place upgrade, the orphaned items will still exist, but will not work. We recommend that you repair any orphaned objects before upgrading.
Tip:
Members of the Administrators group on the front-end Web servers can repair orphaned items before the upgrade by following the steps in Knowledge Base article 918744, Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services (http://go.microsoft.com/fwlink/?linkid=69958&clcid=0x409).
Valid configuration settings Reports any missing or invalid configuration settings (such as a missing Web.config file, invalid host names, or invalid service accounts) that exist in the farm.
Database requirements Reports whether the databases meet the requirements for upgrade — for example, databases are set to read/write, and any databases and site collections that are stored in the Windows Internal Database are not larger than 4 GB.
Use the information gathered from the pre-upgrade checker to determine:
Whether to perform an in-place upgrade or a database attach upgrade.
Determine upgrade approach (SharePoint Foundation 2010) provides information to help you decide which type of upgrade to perform. It is important to consider the report generated by the pre-upgrade checker when you make this decision. If your servers do not meet the requirements for in-place upgrade, you need to consider performing a database attach upgrade.
Whether to upgrade some or all site collections that contain customized sites.
Which sites need to have customizations reapplied or redone after upgrade and therefore might take longer than others in the review stage.
A worksheet is available so you can record information about your environment while you prepare for upgrade. Download the worksheet from http://go.microsoft.com/fwlink/?LinkId=179928 (http://go.microsoft.com/fwlink/?LinkId=179928).
-
Run the pre-upgrade checker
Before you perform this procedure, confirm that:
Your system is running Windows SharePoint Services 3.0 with Service Pack 2
To run the pre-upgrade checker
1. Verify that you have the following administrative credentials:
To use Stsadm, you must be a member of the local Administrators group on the server.
2. Click Start, right-click Command Prompt, and then click Run as administrator.
3. In the Command Prompt window, navigate to the following directory:
%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin
4. Type the following command and press ENTER:
STSADM.EXE -o preupgradecheck
This command checks both the local server and your farm-level settings. For a list of other parameters you can use with this operation, see Preupgradecheck: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/dd793605(Office.12).aspx). For a list of rules included in the pre-upgrade checker, see Pre-upgrade scanning and reporting for future releases (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/dd793607(Office.12).aspx).
After you run the pre-upgrade checker, the report automatically opens in your default browser. You can also view the report by opening it from its location in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\LOGS directory. The report is named in the following format: PreUpgradeCheck_YYYYMMDD-HHMMSS-SSS–random-number.htm, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds), and the random number is used to differentiate between possible simultaneous attempts to run the pre-upgrade checker. There are also TXT and XML versions of the report in the same location.
Use the report to find and troubleshoot issues. You can also share the relevant results with other members of the upgrade team. For example, you can report issues such as customized site templates or custom Web Parts to the appropriate site owner, Web designer, or developer before scheduling the upgrade, to give them time to resolve the issues.
-
Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010)
To ensure that you can recover the existing environment in case something goes wrong during the upgrade process, you must back up the Windows SharePoint Services 3.0 environment before you run the upgrade process.
If you are running Windows SharePoint Services 3.0 in a Hyper-V virtual environment, see Using SharePoint Products and Technologies in a Hyper-V virtual environment (http://go.microsoft.com/fwlink/?LinkID=125834&clcid=0x409).
-
Back up the environment
You can do a full backup of the Windows SharePoint Services 3.0 environment. We recommend that you perform a full backup of the farm before upgrading.
To back up the Windows SharePoint Services 3.0 environment, use the procedures described in Back up a farm by using built-in tools (Windows SharePoint Services 3.0) (http://go.microsoft.com/fwlink/?LinkID=105988&clcid=0x409).
If you have deployed customizations, you must also back up the customizations. For more information, see Back up and restore customizations (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkId=186627).
-
Test the backups
You have to be sure that these backups are valid so that you can recover if there is a hardware failure or data corruption during the upgrade process. To test the backups, set up a non-production Windows SharePoint Services 3.0 farm, restore the backups and install any customizations (such as site definitions, Web Parts, and so on), and then verify that the restored backup is functional.
To do this, use the procedures described in Restore a farm by using built-in tools (Windows SharePoint Services 3.0) (http://go.microsoft.com/fwlink/?LinkID=105989&clcid=0x409).
Back up and restore the farm (Windows SharePoint Services 3.0) (http://go.microsoft.com/fwlink/?LinkId=186630&clcid=0x409)
-
Perform an in-place upgrade (SharePoint Foundation 2010)
Now that you have learned about the upgrade process by reading the articles in About the upgrade process (SharePoint Foundation 2010), and planned for your upgrade by following the steps in the articles in Plan and prepare for upgrade (SharePoint Foundation 2010), you are ready to perform the in-place upgrade to Microsoft SharePoint Foundation 2010. You can use the steps in this section for both a trial upgrade and your actual in-place upgrade on your production farm.
In this section:
Checklist for in-place upgrade (SharePoint Foundation 2010)
Use this checklist to make sure that you follow all necessary steps as you prepare for upgrade, perform the upgrade, and perform post-upgrade steps.
Upgrade in place to SharePoint Foundation 2010
Get all the steps that you need to perform an in-place upgrade, from installing prerequisites to upgrading sites.
Upgrade a stand-alone installation by using remote BLOB storage (in-place)
Get the steps to upgrade to SharePoint Foundation 2010 from a stand-alone Windows SharePoint Services 3.0 system that has content databases that are larger than 4 gigabytes (GB).
Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010)
Understand the process for using the detach databases hybrid approach to upgrade. This approach combines an in-place upgrade with the efficiency and speed of upgrading multiple databases at the same time.
Install available language template packs (SharePoint Foundation 2010)
Install any language packs that you need for your environment, after you run Setup and before you run the SharePoint Products Configuration Wizard.
-
Checklist for in-place upgrade (SharePoint Foundation 2010)
This article contains a checklist you can use to make sure that you followed all necessary steps as you prepare for upgrade, perform the upgrade, and perform post-upgrade steps.
In this article:
Some of the steps include notes about the amount of time the steps might take. These are rough estimates only, to give you a relative idea of the duration of the step. To find out how much time each step will take for your environment, we recommend that you perform trial upgrades in a test environment. For more information, see Estimate how long the upgrade process will take and the space that you need (SharePoint Foundation 2010) and Use a trial upgrade to find potential issues (SharePoint Foundation 2010).
-
Prepare for upgrade
Follow these steps in order before you begin an in-place upgrade:
Pre-upgrade steps for an in-place upgrade
Notes
[ ]
Run the pre-upgrade checker
Run the pre-upgrade checker and address any issues. Use the report that is generated by the tool to fill out the Upgrade planning worksheet.
Detailed steps: Run the pre-upgrade checker (SharePoint Foundation 2010).
Perform this step multiple times as you clean up your environment and test your upgrade process.
Running the checker takes only a few minutes, but addressing any issues might take days or weeks.
[ ]
Clean up your environment
Before you begin the upgrade, make sure that your environment functions in a healthy state and that you clean up any content that you do not have to keep. Remove or repair any orphaned sites or data, address any large lists or large access control lists (ACLs), remove extraneous document versions, and remove any unused templates, features, or Web Parts.
Detailed steps: Cleaning up your environment before upgrade (SharePoint Foundation 2010).
Perform this step once for the whole environment.
This process might take days or weeks to complete.
[ ]
Record blocked file types
Blocked file types are not preserved during upgrade. Copy the list of blocked file types and save the list in the upgrade worksheet so you can reapply the settings after upgrade.
Perform this step once for the whole environment.
[ ]
Back up your environment
Back up your entire environment to ensure that you can recover the existing environment in case something goes wrong during the upgrade process.
Detailed steps: Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010).
Perform this step once for the whole environment.
This step can take an hour, several hours, or longer, depending on your data set and your environment.
-
Perform the upgrade
Follow these steps in order during an in-place upgrade. Steps required for in-place upgrade with detached databases are also included.
Warning:
When you upgrade in-place from an installation of Windows SharePoint Services 3.0 that uses Windows Internal Database and the database size approaches 4 GB, you must perform additional steps. For more information about these steps, see Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage).
Perform the in-place upgrade
Notes
[ ]
Run the pre-upgrade checker
Run the pre-upgrade checker again to identify any new or remaining issues before you start the upgrade.
Detailed steps: Run the pre-upgrade checker (SharePoint Foundation 2010).
Running the checker takes only a few minutes, but addressing any issues might take longer.
[ ]
Install prerequisites on all servers
Before you can upgrade, you must run the prerequisite installer successfully on each Web server that has Windows SharePoint Services 3.0 installed.
Detailed steps: Install prerequisites in the “Upgrade in place to SharePoint Foundation 2010” article.
Perform this step for each Web server in your environment.
[ ]
Detach databases (in-place upgrade with detached databases only)
If you are performing an in-place upgrade with detached databases, detach the databases before you run Setup.
Detailed steps: Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010).
Perform this step for each content database in your environment.
[ ]
Disconnect users
If you are upgrading a server farm, disconnect all the users from the server farm by stopping the World Wide Web Publishing Service (W3SVC) on all Web servers.
Perform this step on each Web server in your environment.
[ ]
Run Setup on all servers
Run Setup on all servers to upgrade the software.
Detailed steps: Run Setup on all servers in the “Upgrade in place to SharePoint Foundation 2010” article.
Perform this step for each Web server in your environment.
This step might take a few minutes or more than an hour, depending on how many servers are in your environment.
[ ]
Install language packs
Install any language packs you need before you run the SharePoint Products Configuration Wizard.
Detailed steps: Install available language template packs (SharePoint Foundation 2010).
Perform this step on each Web server in your environment.
This step should take only a few minutes per Web server.
[ ]
Run the SharePoint Products Configuration Wizard
If you are upgrading a server farm, first run the SharePoint Products Configuration Wizard on the server that is running SharePoint Central Administration, pause and run the wizard on the other servers in the farm, and then return to the first server to complete the wizard.
Important:
You must upgrade SharePoint Central Administration before you attempt to upgrade any other content in the farm. Completing the wizard on the server running SharePoint Central Administration allows you to do so.
Detailed steps: Run the SharePoint Products Configuration Wizard in the “Upgrade in place to SharePoint Foundation 2010” article.
Perform this step for each Web server in your environment.
This step might take an hour or more.
[ ]
Configure forms-based authentication for a claims-based Web application (in-place upgrade with detached databases only)
For Web applications that were configured to use forms-based authentication or Web single sign-on (Web SSO) authentication, you must perform additional steps before you attach and upgrade the databases. First, you convert the Windows SharePoint Services 3.0 Web applications to claims authentication. After you convert the Web applications to claims authentication, you configure your Web application zones for forms-based authentication (or Web SSO authentication, as appropriate). Then, you can migrate users and permissions to SharePoint Foundation 2010.
Detailed steps: Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010).
Perform this step now if you are following the in-place upgrade with detached databases approach. If you are following a standard in-place upgrade approach, perform this step after upgrade is completed.
Perform this step for any Web applications that used forms-based authentication in Windows SharePoint Services 3.0.
[ ]
Attach databases (in-place upgrade with detached databases only)
If you are performing an in-place upgrade with detached databases, attach the databases and then upgrade the data.
Detailed steps: Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010).
Perform this step for each content database in your environment.
This step might take an hour, several hours, or days, depending on your data set, whether you are upgrading multiple databases in parallel, and the hardware on the Web servers, database servers, and storage subsystem.
[ ]
Monitor upgrade progress
Use the Upgrade Status page in SharePoint Central Administration to monitor progress as your sites are upgraded.
Detailed steps: Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
Perform this step once for the whole environment.
This step might take an hour, several hours, or days, depending on your data set.
-
-
Perform post-upgrade steps
Perform the following steps in order after you perform an in-place upgrade.
Post-upgrade steps for an in-place upgrade
Notes
[ ]
Configure forms-based authentication for a claims-based Web application
For Web applications that were configured to use forms-based authentication or Web single sign-on (Web SSO) authentication, you must perform additional steps after upgrading. First, you convert the Windows SharePoint Services 3.0 Web applications to claims authentication. After you convert the Web applications to claims authentication, you configure your Web application zones for forms-based authentication (or Web SSO authentication, as appropriate). Then, you can migrate users and permissions to SharePoint Foundation 2010.
Detailed steps: Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010).
Perform this step for any Web applications that used forms-based authentication in Windows SharePoint Services 3.0.
[ ]
Verify upgrade and review upgraded sites
Review sites to be sure that they have been upgraded successfully and are ready for users to view.
Detailed steps: Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
Perform this step for every upgraded Web application and site collection in your environment.
This step might take an hour, several hours, or days, depending on your content.
You should also have site owners review their sites and report any issues.
-
See Also
Upgrade Worksheet for SharePoint 2010 Products (http://go.microsoft.com/fwlink/?LinkId=179928)
-
-
Upgrade in place to SharePoint Foundation 2010
When you run an in-place upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, the configuration data for the farm and all the content in the farm is upgraded on the existing hardware, in a fixed order. When you start the in-place upgrade process, Setup takes the Web server offline and the Web sites are unavailable until the upgrade is finished, and then Setup restarts the Web server. After you begin an in-place upgrade, you cannot pause the upgrade or roll back to the previous version.
Note:
One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Be sure that any custom elements you have to have are installed on your front-end Web servers before you begin the upgrade process. You can use the pre-upgrade checker to identify any custom elements that your sites might be using. For more information, see Identify and install customizations in the article “Use a trial upgrade to find potential issues.”
Upgrading in place from an installation of Windows SharePoint Services 3.0 that uses Windows Internal Database requires additional steps if your database size has exceeded 4 GB. For more information, see Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage).
You can also use many of the procedures in this article to perform a detach databases hybrid approach to upgrade, where you upgrade the server and infrastructure in place but upgrade the content databases by detaching and attaching them in parallel. For information about the detach databases process, see Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010). For more information about how to choose an upgrade approach, see Determine upgrade approach (SharePoint Foundation 2010) and Upgrade process overview (SharePoint Foundation 2010).
Important:
You must be running Service Pack 2 (SP2) of Windows SharePoint Services 3.0 in a 64-bit Windows Server 2008 environment to perform an in-place upgrade to SharePoint Foundation 2010. If you are in a server farm environment, you must also be running a 64-bit version of Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3.
In this article:
Run the SharePoint Products Configuration Wizard
-
Process overview
By using the procedures in this article, you install SharePoint Foundation 2010 and upgrade all of the SharePoint sites in the environment. We recommend that you try out the upgrade process on a test environment before you attempt to upgrade your production environment. For more information, see Use a trial upgrade to find potential issues (SharePoint Foundation 2010).
When you upgrade a server farm, install and configure the new version to the servers in the following order:
1. Install SharePoint Foundation 2010 on all servers in the server farm.
2. Install any language packs for SharePoint Foundation 2010 that you need. For more information, see Install available language template packs (SharePoint Foundation 2010).
3. Run the SharePoint Products Configuration Wizard on the front-end Web server that contains the SharePoint Central Administration Web site. To determine which server is running SharePoint Central Administration, open the Servers in Farm page (http://server_name:adminport/_admin/farmservers.aspx) and note which server or servers have Central Administration services running. Perform this step before you install SharePoint Foundation 2010, while SharePoint Central Administration for Windows SharePoint Services 3.0 is still available.
Note:
If you have multiple servers that are running SharePoint Central Administration, pick one and use that as the initial server on which to run upgrade. After you have completed the process on that one, you can continue with any other servers that are running SharePoint Central Administration.
4. Run the SharePoint Products Configuration Wizard on the remaining front-end Web servers and application servers in the farm in any order.
For an overview and diagrams of the each upgrade approach, see Upgrade process overview (SharePoint Foundation 2010).
Note:
If you are using the detach databases hybrid approach for upgrading, the process you follow is similar, but you detach all content databases before you run Setup, and then attach them again after you run the SharePoint Products Configuration Wizard. For more information about the detach databases upgrade approach, see Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010).
-
Before you begin
Before you begin the in-place upgrade, review the following information about permissions, hardware requirements, and software requirements and steps to perform before beginning the process.
Make sure that you have run the pre-upgrade checker tool (stsadm -o preupgradecheck, available in Windows SharePoint Services 3.0 Service Pack 2 and updated in the October 2009 Cumulative Update) and addressed any issues before you begin the upgrade process. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
We recommend that you back up your environment before you begin the upgrade process. For more information, see Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010).
Ensure that you have met all hardware and software requirements. You must have a 64-bit version of Windows Server 2008 or Windows Server 2008 R2. For server farms, you must also have a 64-bit version of SQL Server 2005 or SQL Server 2008. For more information about these requirements (such as specific updates that you must install), see Determine hardware and software requirements (SharePoint Foundation 2010).
Ensure that you are prepared to set up the required accounts by using appropriate permissions. For detailed information, see Administrative and service accounts required for initial deployment (SharePoint Foundation 2010).
Ensure that the account that you use to run the SharePoint Products Configuration Wizard is a member of the db_owner fixed database role for all the databases that you want to upgrade.
-
Install prerequisites
Before you can upgrade, you must run the prerequisite installer successfully on each Web server that has Windows SharePoint Services 3.0 installed. A prerequisite installer is available to install software needed to support SharePoint Foundation 2010.
To run the prerequisite installer
1. From the product disc, open the installation folder and run PrerequisiteInstaller.exe.
The Microsoft SharePoint Products Preparation Tool opens.
2. Click Next.
3. On the License Terms page, select the I accept the terms of the License Agreement(s) check box, and then click Next.
The tool runs, installing and configuring required software.
4. Click Next.
5. On the Installation Complete screen, verify that each prerequisite is listed as successfully installed or already installed.
6. Click Finish to close the wizard.
-
Run Setup on all servers
After all of the prerequisites are installed, you can run Setup.exe on all Web servers in your server farm.
Note:
If you are using the detach databases hybrid approach for upgrading, you should detach your content databases before you run Setup. For more information about how to detach databases, see Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010).
Important:
If you are running an in-place upgrade on a server farm, disconnect all the users from the server farm by stopping the World Wide Web Publishing Service (W3SVC) on all front-end Web servers. If you allow users in a server farm to connect after the files and databases have been updated on one Web server, but before the other Web servers have been updated, users will not be able to browse the Web sites.
To install the new version
1. Run Setup.exe.
2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.
3. On the Upgrade earlier versions page, click Install Now.
4. Setup runs and installs SharePoint Foundation 2010.
On the completion page, clear the Run the SharePoint Products Configuration Wizard now check box, and then click Close.
Before you run the SharePoint Products Configuration Wizard, install any language template packs for SharePoint Foundation 2010. For more information, see Install available language template packs (SharePoint Foundation 2010).
-
Run the SharePoint Products Configuration Wizard
If you are upgrading a single server, you can run the SharePoint Products Configuration Wizard on only that server and start to upgrade content. If you are upgrading a server farm, first run the SharePoint Products Configuration Wizard on the server that is running SharePoint Central Administration, pause and run the wizard on the other servers in the farm, and then return to the first server to complete the wizard. It is important to upgrade SharePoint Central Administration before you attempt to upgrade any other content in the farm, and completing the wizard on the server that is running SharePoint Central Administration allows you to do so.
Important:
Ensure that the account you use to run the SharePoint Products Configuration Wizard is a member of the db_owner fixed database role for all the databases that you want to upgrade. If it is not, you might see an error about an unknown user account when the wizard starts to upgrade the databases.
Be sure that you have installed any language template packs before you run the SharePoint Products Configuration Wizard.
Caution:
After you run the SharePoint Products Configuration Wizard, Windows SharePoint Services 3.0 will no longer be available. You cannot pause or roll back the setup and upgrade process. Be sure that you have a current and valid backup of your environment before you proceed with installing SharePoint Foundation 2010.
To run the SharePoint Products Configuration Wizard
1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products Configuration Wizard.
2. In the SharePoint Products Configuration Wizard, on the Welcome to SharePoint Products page, click Next.
A message appears, notifying you that Internet Information Services (IIS), the SharePoint Administration Services v4, and the SharePoint Timer Service v4 may need to be restarted or reset during configuration.
3. Click Yes to continue with the wizard.
4. On the Specify Farm Settings page, in the Passphrase box, type a passphrase and in the Confirm passphrase box, type the same passphrase.
The passphrase should consist of at least eight characters and should contain characters from at least three of the following four groups:
English uppercase characters (from A through Z)
English lowercase characters (from a through z)
Numerals (from 0 through 9)
Nonalphabetic characters (such as !, $, #, %)
5. On the Visual Upgrade page, select one of the following options:
Change existing SharePoint sites to use the new user experience. Administrators control the user experience for end users.
This option allows you to change all sites over to the new user experience without previewing that experience first. If you select this option, you can also choose between the following two options:
Preserve customized pages, but update template and application pages to use the new UI.
Reset all customized pages to their original templates. This option will delete modifications from customized pages and cannot be undone.
Preserve the look and feel of existing SharePoint sites, and allow end users to update their sites’ user experience.
This is the default option. This option allows the site owners to preview their sites in the new user experience and determine when they are ready to switch the sites over to the new user experience permanently.
6. On the Completing the SharePoint Products Configuration Wizard page, verify the settings, and then click Next.
The SharePoint Products Configuration Wizard runs and configures the configuration database and SharePoint Central Administration for SharePoint Foundation 2010.
7. A message appears, notifying you that if you have a server farm with multiple servers, you must run Setup on each server to install new binary files before you continue the SharePoint Products Configuration Wizard.
If this is the only server in your farm, or if you have already run Setup on all the servers in your farm, click OK to continue with the wizard.
If you have not yet run Setup on all the servers in your farm, run Setup on the remaining servers now, and then return to this server and click OK to continue with the wizard.
The SharePoint Products Configuration Wizard continues the upgrade process by setting up the configuration database and installing SharePoint Central Administration.
8. On the Configuration Successful, Upgrade in Progress page, review the settings that have been configured, and then click Finish.
The SharePoint Products Configuration Wizard closes and the Upgrade Status page opens. You might be prompted to enter your user name and password before the Upgrade Status page will open. The upgrade process might take awhile to complete, depending on how much data you have in your farm.
Note:
If you are following the detach databases hybrid approach for upgrade, you can now begin to attach content databases to upgrade them. For more information, see Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010).
9. If you are upgrading a server farm, you can now complete the SharePoint Products Configuration Wizard on the other servers in the farm.
-
Check upgrade status for sites
After the SharePoint Products Configuration Wizard has finished, you can monitor the upgrade process for each site from the Upgrade Status page in SharePoint Central Administration or by using the localupgradestatus operation in Stsadm.exe. For more information, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
After upgrade is completed successfully for all sites, if you stopped the World Wide Web Publishing Service (W3SVC) on all front-end Web servers before the upgrade, manually start the World Wide Web Publishing Service on the front-end Web servers to make the Web servers available to users.
Note:
Search results might be incomplete or might not be returned for a few minutes after upgrade. This is because the Search Synchronization Timer job must run after upgrade, and search results are not available until the job has finished.
-
Verification
If upgrade fails or reports issues, you can refer to the log and error files for more information. For more information about how to review the log files and how to restart upgrade after a failure, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010). If you are using Visual Upgrade, for more information about previewing sites and changing to the new user interface, see Manage visual upgrade (SharePoint Foundation 2010).
-
See Also
-
-
Roadmap for in-place upgrade with detached databases (SharePoint Foundation 2010)
When you upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, you can perform an in-place upgrade or a database attach upgrade, or you can combine certain aspects of both approaches to increase availability or throughput during the upgrade process. This article describes how to perform a hybrid approach that combines in-place upgrade with detaching and attaching databases so that you can upgrade multiple databases at the same time, possibly even on separate hardware. You can use this approach to upgrade two or more content databases at a time, and therefore upgrade more quickly than if you used a standard in-place upgrade (which upgrades individual content databases and site collections serially). This approach uses the following hybrid techniques:
Use an in-place upgrade to upgrade the farm and settings.
Detach and upgrade multiple databases in parallel.
Alternative upgrade sequence: Upgrade databases on a temporary small farm.
Note that if you decide to use a temporary small farm to perform the actual upgrade, you must have direct access to the database servers to copy the databases from. Copying databases over the network takes time and bandwidth — make sure you test this process to determine whether you have the resources you need to use a temporary small farm.
For more information about the pros and cons of the different upgrade approaches, see Determine upgrade approach (SharePoint Foundation 2010). For a brief overview and graphical description of the steps you take for each approach, see Upgrade process overview (SharePoint Foundation 2010).
Note:
One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Be sure that any custom elements you need are installed on your front-end Web servers before you begin the upgrade process. You can use the pre-upgrade checker — and, for a database attach upgrade, the test-spcontentdatabaseWindows PowerShell cmdlet — to identify any custom elements that your sites might be using. For more information, see Identify and install customizations in the article “Use a trial upgrade to find potential issues.”
In this article:
To detach databases and upgrade them in parallel on the same farm
To detach databases and upgrade them in parallel on a temporary small farm
Important:
You must be running Service Pack 2 (SP2) of Windows SharePoint Services 3.0 in a 64-bit Windows Server 2008 environment to perform an in-place upgrade to SharePoint Foundation 2010. If you are in a server farm environment, you must also be running a 64-bit version of one of the following: Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3.
-
Process overview
Because this upgrade approach is a hybrid of the techniques used for in-place upgrade and database attach upgrade, this article describes how the steps from each approach fit together into the hybrid process. It does not provide details for every step in the process, because those steps are available in the following articles:
Upgrade in place to SharePoint Foundation 2010
Attach databases and upgrade to SharePoint Foundation 2010
These articles, combined with this roadmap, give you the information you need to perform this hybrid upgrade.
There are two ways in which you can perform this type of hybrid upgrade: using one farm throughout or using a temporary small farm to perform the actual upgrade. The sections below provide the steps you need to take to perform the upgrade by using each of these methods.
-
Before you begin
Before you begin the in-place upgrade, review the following information about permissions, hardware requirements, and software requirements and steps to perform before beginning the process.
Be sure you have run the pre-upgrade checker tool (stsadm -o preupgradecheck, available in Windows SharePoint Services 3.0 Service Pack 2 and updated in the October 2009 Cumulative Update) and addressed any issues before you begin the upgrade process. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
We recommend that you back up your environment before you begin the upgrade process. For more information, see Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010).
Ensure that you have met all hardware and software requirements. You must have a 64-bit version of Windows Server 2008 or Windows Server 2008 R2. For server farms, you must also have a 64-bit version of SQL Server 2005 or SQL Server 2008. For more information about these requirements (such as specific updates that you must install), see Determine hardware and software requirements (SharePoint Foundation 2010).
Ensure that you are prepared to set up the required accounts by using appropriate permissions. For detailed information, see Administrative and service accounts required for initial deployment (SharePoint Foundation 2010).
-
To detach databases and upgrade them in parallel on the same farm
This section describes the steps to take to use the detach databases upgrade approach on a single farm.
Process for upgrading in-place with detached databases (same farm)
Detach databases
1. Use the following operation to detach the content databases:
Stsadm.exe -o deletecontentdb -url http://servername-databasenameContentDatabaseName
For more information about this operation, see Deletecontentdb: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287664(Office.12).aspx).
Upgrade the farm in place
1. Install all prerequisites to all servers in the farm.
2. Run Setup on all servers in the farm.
3. Run the SharePoint Products Configuration Wizard on all servers in the farm.
For detailed procedures that describe these steps, see Upgrade in place to SharePoint Foundation 2010.
Attach the databases and upgrade the content
1. Add the content databases to the Web applications.
Use the following Windows PowerShell cmdlet to add and upgrade the content databases:
Mount-SPContentDatabase –Name <DatabaseName> –DatabaseServer <ServerName> –WebApplication <URL> [-Updateuserexperience]
2. Verify upgrade for the first database.
3. Repeat the restore-and-add-database procedures for remaining databases in parallel.
For detailed procedures that describe these steps, see Perform a database attach upgrade to SharePoint Foundation 2010.
-
To detach databases and upgrade them in parallel on a temporary small farm
This section describes the steps to take to use the detach databases upgrade approach on two farms: the original farm and a temporary small farm.
Process for upgrading in-place with detached databases (temporary small farm)
Set up a temporary small farm to use in upgrading the databases
For detailed procedures that describe these steps, see Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade.
2 – Detach databases from the original farm
1. Back up the previous version databases by using SQL Server tools.
For detailed procedures about backing up the databases, see Perform a database attach upgrade to SharePoint Foundation 2010.
2. Use the following operation to detach the content databases:
Stsadm.exe -o deletecontentdb -url http://servername-databasenameContentDatabaseName
For more information about this operation, see Deletecontentdb: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287664(Office.12).aspx).
Upgrade the original farm in place
1. Install all prerequisites to all servers in the farm.
2. Run Setup on all servers in the farm.
3. Run the SharePoint Products Configuration Wizard on all servers in the farm.
For detailed procedures that describe these steps, see Perform an in-place upgrade (SharePoint Foundation 2010).
Attach the databases to the temporary small farm and upgrade the content
1. Restore the backup copy to the new farm.
2. Add the content databases to the Web applications.
Use the following Windows PowerShell cmdlet to add and upgrade the content databases:
Mount-SPContentDatabase –Name <DatabaseName> –DatabaseServer <ServerName> –WebApplication <URL> [-Updateuserexperience]
3. Verify upgrade for the first database.
4. Repeat the restore-and-add-database procedures for remaining databases in parallel.
For detailed procedures that describe these steps, see Perform a database attach upgrade to SharePoint Foundation 2010.
Back up the databases from the temporary small farm and attach them to the original farm
1. Back up the upgraded databases by using SQL Server tools.
2. Restore the backup copy to the original farm.
3. Add the upgraded content databases to the original Web applications.
This is basically the same process as the previous step; however, you are moving the databases from the temporary small farm back to the original farm. The same procedures apply as in the previous steps.
-
Verification
If upgrade fails or reports issues, you can refer to the log and error files for more information. For more information about reviewing the log files, and about restarting upgrade after a failure, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
-
Install available language template packs (SharePoint Foundation 2010)
Before you can upgrade any sites that are based on a language pack for the previous version, you have to install the language pack for the new version.
In this article:
About installing language packs and upgrading sites
-
About installing language packs and upgrading sites
If you want to install a language pack for Microsoft SharePoint Foundation 2010, do so after running Setup and before running the SharePoint Products Configuration Wizard. This way, you can upgrade any sites based on a language pack for a previous version along with the other sites during the upgrade process. For more information about installing language packs, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx) in the Deployment Guide.
You can also install a language pack after you have run the SharePoint Products Configuration Wizard, and after you have upgraded the sites in your environment that are not based on a language pack. If you choose this option, you must then use the PSConfig command-line tool to upgrade the sites based on the newly installed language pack.
-
About changing languages
Generally, a cross-language upgrade is not supported. You must upgrade from and to the same language. For example, if you are running U.S. English in the previous version, you need to upgrade to U.S. English in the new version. If you want to change languages, you must first perform the upgrade and then change the language for the site.
However, this process is complicated in some cases — for example, when the previous version had a fully localized product for a particular language but the new version only has a language pack, or when the new version has a language pack for a new language that was not available in the previous version.
-
Moving from a fully localized product to a language pack
Use the following procedure on each Web server to upgrade from a language that was supported with a fully localized product in the previous version, but that is only supported by a language pack in the new version:
To move from a fully localized product to a language pack
1. Verify that the user account performing this procedure is a member of the Farm Administrators SharePoint group. .
2. Choose a language to install for the new version (for example, English). This is the language that the SharePoint Central Administration Web site will use.
3. In the SharePoint Products Configuration Wizard, when you are prompted to install language packs, stop the wizard and install the appropriate language pack.
If you had additional previous-version language packs installed, install the corresponding SharePoint Foundation 2010 language packs now by canceling the wizard, and then running the appropriate Setup programs to install the language packs.
Note:
You must be a member of the Administrators group on the local computer to perform this step.
For more information about installing language packs, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx) in the Deployment Guide.
4. Start the configuration wizard again to complete the upgrade process.
-
Changing languages to a new language pack
Use the following process to upgrade from a language in the previous version to a different language in the new version (for example, if the language you want was not available in the previous version, but is now available as a language pack in the new version).
To change languages to a new language pack
1. Verify that the user account performing the next two steps is a member of the Administrators group on the local computer.
2. Upgrade to the new version in the same language that you used for the previous version.
3. After the upgrade is complete, install the new language pack.
4. Verify that the user account performing the next two steps is a member of the Farm Administrators SharePoint group.
5. Create new sites based on the new language pack.
6. Manually move your content to the new sites.
-
See Also
Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx)
-
-
Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage)
This article describes the circumstances in which you might want to upgrade from a stand-alone Windows SharePoint Services 3.0 system to SharePoint Foundation 2010 with Remote BLOB Storage (RBS).
When you upgrade from a stand-alone installation of Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, the upgrade process differs depending on the size of the content databases.
In a stand-alone installation of Windows SharePoint Services 3.0, content databases are stored in Windows Internal Database and have no size limitations. Conversely, in SharePoint Foundation 2010, the content databases are stored in Microsoft SQL Server 2008 Express and have a maximum size of 4 gigabytes (GB) per database. If you have databases that are larger than 4 GB, you must either use Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3, or install Remote BLOB Storage (RBS).
Note:
Microsoft SQL Server 2008 R2 Express supports databases up to 10 GB. If the installation includes databases that are larger than 4 GB but smaller than 10 GB, you can upgrade to SQL Server 2008 R2 Express for your content database storage solution instead of implementing RBS. SQL Server 2008 R2 Express is available for download and installation at Microsoft SQL Server 2008 R2 Express Edition (http://go.microsoft.com/fwlink/?LinkID=189418).
RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. RBS is an add-on that can be applied to SQL Server 2008 Express and to SQL Server 2008. For more information about RBS, see Overview of Remote BLOB Storage (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7522114b-7de5-434e-b028-8b99654a43be(Office.14).aspx).
If you are upgrading fromWindows SharePoint Services 3.0 and all databases are smaller than 4 GB, you can follow the standard in-place upgrade process. For details, see Upgrade in place to SharePoint Foundation 2010.
If you are upgrading from Windows SharePoint Services 3.0 and the search database is larger than 4 GB, you cannot migrate that database. To upgrade, you must remove the existing instance of search before migrating and upgrading. After upgrading, you can create a new instance of search. The search database is limited to 4 GB if the new installation is hosted on SQL Server 2008 Express.
If you are upgrading from Windows SharePoint Services 3.0 and the configuration database is larger than 4 GB, you cannot migrate the configuration database. Instead, you must either create a new SharePoint Foundation system that uses SQL Server 2008 Express (if the configuration database is not expected to grow larger than 4 GB), or create a new installation that uses SQL Server 2008 Standard or SQL Server 2008 Enterprise. You can also migrate the existing system to SQL Server 2008 Standard or SQL Server 2008 Enterprise and then upgrade it.
If you are not upgrading an existing Windows SharePoint Services 3.0 system and you want to install and configure RBS in SharePoint Foundation 2010, see Install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider(SharePoint Foundation 2010) (http://technet.microsoft.com/library/6348e3a7-e2f4-4321-b145-da42269883aa(Office.14).aspx).
Note
If after you move content into RBS, a content database remains that is larger than 4 GB, the migration operation will fail. This failure typically occurs only with very large databases (20 GB or larger), but it can also occur if there is a smaller database that contains too much metadata.
If the configuration includes SharePoint databases that are larger than 16 GB, RBS is unlikely to provide a full solution to the limitations of SQL Server 2008 Express and SQL Server 2008 R2 Express. In this case, you should be prepared to use SQL Server 2008 Standard or SQL Server 2008 Enterprise to support the SharePoint databases.
Before beginning the upgrade process, confirm that the hardware configuration supports SharePoint Foundation 2010. For more information, see Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx).
-
In This Section
Upgrade a stand-alone installation by using remote BLOB storage (in-place)
This article describes how to upgrade from a stand-alone Windows SharePoint Services 3.0 system that has content databases that are larger than 4 GB to SharePoint Foundation 2010.
Upgrade a stand-alone installation on a domain controller by using Remote BLOB Storage (RBS) (database attach)
This article describes how to upgrade from a stand-alone Windows SharePoint Services 3.0 system that has content databases that are larger than 4 GB to a SharePoint Foundation 2010 system that is running on a domain controller.
Upgrade a stand-alone installation to new hardware by using Remote BLOB Storage (database attach)
This article describes how to upgrade from a stand-alone Windows SharePoint Services 3.0 system that has content databases that are larger than 4 GB to SharePoint Foundation 2010 that is installed on new hardware.
-
See Also
Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010) (http://technet.microsoft.com/library/da8cf825-2f79-49dd-bd4c-4ad0aad83f94(Office.14).aspx)
-
-
Upgrade a stand-alone installation by using remote BLOB storage (in-place)
This article describes how to upgrade from a stand-alone Windows SharePoint Services 3.0 system that has content databases that range in size from 4 gigabytes (GB) to 16 GB to Microsoft SharePoint Foundation 2010 with Remote BLOB Storage (RBS).
Note:
Microsoft SQL Server 2008 R2 Express supports databases up to 10 GB. If the installation includes content databases that are larger than 4 GB but smaller than 10 GB, you can upgrade to SQL Server 2008 R2 Express for your content database storage solution instead of implementing RBS. For more information, see Microsoft SQL Server 2008 R2 Express Edition (http://go.microsoft.com/fwlink/?LinkID=189418).
Before performing the operations described in this article, we strongly recommend that you read the following articles to ensure that you are following the best upgrade path:
Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010) (http://technet.microsoft.com/library/da8cf825-2f79-49dd-bd4c-4ad0aad83f94(Office.14).aspx)
Overview of Remote BLOB Storage (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7522114b-7de5-434e-b028-8b99654a43be(Office.14).aspx)
Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage)
To upgrade from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 with RBS
1. Verify that the user account that is used to perform the upgrade and installation is a member of the Administrators group on the computer running Windows SharePoint Services 3.0 on which the upgrade is being performed and on which RBS is being installed.
2. Confirm that the hardware configuration supports SharePoint Foundation 2010. For more information, see Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx).
3. Verify that the available disk space meets the following requirements:
Available disk space is at least twice the size of the largest content database.
Available disk space is equal to or greater than the sum of the sizes of all content databases.
4. Download the SharePoint Foundation 2010 software updates from the upgrade site.
5. Open the local folder that contains the software download, and then double-click PrerequisiteInstaller. Accept the default values, and then complete the Prerequisite Installer Wizard.
6. Double-click Setup, accept the default values, and then complete the Setup Wizard.
When Setup completes, the SharePoint Products Configuration Wizard automatically runs.
If the wizard detects a SharePoint database that is larger than 4 GB, a message appears that notifies you that you must migrate the databases to RBS.
Note:
If any SharePoint database is larger than 4 GB, all SharePoint databases must be migrated to RBS, even if some databases are smaller than 4 GB.
7. If you have not previously installed RBS on the server, the SharePoint Products Configuration Wizard fails, and then displays an error message that explains that databases larger than 4 GB were detected and that RBS must be installed. If you must install RBS, continue with the following steps. If you have already installed RBS on the server, the wizard completes successfully without displaying the error message.
8. Go to http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388) to download the RBS_X64.msi file.
Important:
You must install the version of RBS that is included in the SQL Server Remote BLOB Store installation package from the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The version of RBS must be 10.50.xxx. No earlier version of RBS is supported for SharePoint Foundation 2010.
9. Open the folder that contains the file, and then double-click RBS_X64.msi to start the Install SQL Remote BLOB Storage Wizard.
10. In the Install SQL Remote BLOB Storage Wizard, on the Feature Selection page, expand Server, click the down arrow next to Execute scripts, and then click Entire feature will be unavailable.
11. Expand FILESTREAM Provider, expand Server, click the down arrow next to Execute scripts, and then click Entire feature will be unavailable.
12. Complete the wizard by using the default values.
13. Click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Products Configuration Wizard.
14. The wizard completes the upgrade.
-
See Also
-
-
Upgrade a stand-alone installation on a domain controller by using Remote BLOB Storage (RBS) (database attach)
This article discusses the upgrade procedures that are required to upgrade from a stand-alone Windows SharePoint Services 3.0 system that is running on a domain controller to Microsoft SharePoint Foundation 2010 with Remote BLOB Storage (RBS). We typically recommend that you use RBS if the content databases are 4 gigabytes (GB) or larger.
Important:
We strongly recommend that you read the article Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage) for important information and recommendations about how to upgrade from Windows SharePoint Services 3.0 to SharePoint Foundation 2010 with RBS.
You can use RBS to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. RBS is an add-on that can be applied to SQL Server 2008 Express and to SQL Server 2008.
The implementation of RBS that is discussed in this article uses the SQL Server FILESTREAM provider. For more information about RBS and the FILESTREAM provider, see Overview of Remote BLOB Storage (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7522114b-7de5-434e-b028-8b99654a43be(Office.14).aspx).
In SharePoint Foundation 2010, the content databases are stored in SQL Server 2008 Express and have a maximum size of 4 GB per database. Because Microsoft SQL Server 2008 R2 Express supports content databases that are up to 10 GB, we recommend that you install SQL Server 2008 R2 Express to support the content databases.
This article is not a comprehensive guide to upgrading to SharePoint Foundation 2010. Instead, it refers you to the articles you should read to perform the upgrade. This article contains the additional steps that are required to install and implement RBS on a domain controller installation of SharePoint Foundation 2010.
Before beginning the upgrade process, read the following articles and create an upgrade plan:
About the upgrade process (SharePoint Foundation 2010)
Plan and prepare for upgrade (SharePoint Foundation 2010)
Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage)
Procedures in this article:
To prepare for the upgrade to SharePoint Foundation 2010 with RBS on a domain controller
To install SQL Server 2008 Express R2
To install SharePoint Foundation 2010
To install SharePoint Foundation 2010
To prepare for the upgrade to SharePoint Foundation 2010 with RBS on a domain controller
1. Verify that the user account that is used to perform the upgrade and installation meets the requirements listed in Administrative and service accounts required for initial deployment (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b1aee1ea-45f6-4e05-ad93-9086f6ad7e79(Office.14).aspx).
2. Verify that the user account is a member of the Administrators group on the local computer.
3. Confirm that the hardware configuration supports SharePoint Foundation 2010. For more information, see Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx).
4. Verify that the available disk space meets the following requirements:
Available disk space is at least two times the size of the largest content database.
Available disk space is equal to or greater than the sum of the sizes of all content databases.
5. Perform the pre-upgrade tasks that are discussed in the article Perform pre-upgrade steps (SharePoint Foundation 2010). These are as follows:
Run the pre-upgrade checker (SharePoint Foundation 2010)
The pre-upgrade checker report includes the names of all content databases. You will need this list to enable RBS for the content databases.
If you have multiple Web applications, you should compile a list of which content databases are attached to which Web applications. You will need this information after the upgrade.
Back up the entire environment before an in-place upgrade (SharePoint Foundation 2010)
To install SQL Server 2008 Express R2
1. Download SQL Server 2008 R2 Express from Microsoft SQL Server 2008 R2 Express Edition (http://go.microsoft.com/fwlink/?LinkID=189418).
2. Follow the on-screen instructions to install SQL Server 2008 R2 Express on the domain controller.
For more information about how to install SQL Server 2008 R2 Express, see How to: Install SQL Server 2008 (Setup) (http://go.microsoft.com/fwlink/?LinkID=186119&clcid=0x409).
Accept the default settings for most of the installation options. You should specifically accept the following options:
a. On the Feature Selection page, you can select the components for the installation. Be sure to select SQL Server Management Studio as a feature to install.
b. On the Instance Configuration page, specify whether to install a default instance or a named instance. If you create a named instance, note the instance name because you will need this name in a later procedure in this article.
c. On the Server Configuration — Service Accounts page, you must specify login accounts for SQL Server services. You can assign the same login account to all SQL Server services, or you can configure each service account individually. You must use a domain account as the login account for the SQL Server Database Engine.
d. On the Database Engine Configuration page, make sure that the domain account that is used for this installation is listed as a SQL Server administrator.
To install RBS
1. Go to http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388) to download the RBS_X64.msi file.
Important:
You must install the version of RBS that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The version of RBS must be 10.50.xxx. No earlier version of RBS is supported for SharePoint Foundation 2010.
2. Open the folder that contains the file, and then double-click RBS_X64.msi to start the Install SQL Remote BLOB Storage Wizard.
3. In the Install SQL Remote BLOB Storage Wizard, on the Feature Selection page, expand Server, click the down arrow next to Execute scripts, and then click Entire feature will be unavailable.
4. Expand FILESTREAM Provider, expand Server, click the down arrow next to Execute scripts, and then click Entire feature will be unavailable.
Note:
The database that will host the scripts does not yet exist because it will be created during the database upgrade process. The Execute scripts option will be installed automatically during the installation of SharePoint Foundation 2010.
5. Complete the wizard by using the default values.
During the installation, a dialog box appears that describes an RBS Maintainer task. Click OK in that dialog box to continue with the installation.
To install SharePoint Foundation 2010
1. Uninstall all previous versions of SharePoint Products and Technologies that exist on the domain controller by using Control Panel.
2. Install SharePoint Foundation 2010 by following the instructions in Install SharePoint Foundation 2010 on the farm servers (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a.aspx#InstallSF). During the installation, you must use the database instance name that you created in Step 2 of the procedure To install SQL Server 2008 Express R2. If you used the default named instance in that step, you must enter it in this step as “SQLExpress”. If you used the default instance, you must type ” “ here instead of using the default SQLExpress named instance.
Note that you are creating a new installation of SharePoint Foundation 2010. You are performing a database attach upgrade, not an in-place upgrade.
Note:
After you install SharePoint Foundation 2010, do not create any Web applications until instructed to do this later in this article.
To migrate the content database to RBS and complete the installation
1. Verify that the user account that is performing this procedure is the same user account that was used to install the farm running SharePoint Foundation 2010 and RBS.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command to migrate the content database to RBS:
Move-SPBlobStorageLocation –SourceDatabase “<ContentDbName>” –DestinationDataSourceInstance “<InstanceName>”
Where:
<ContentDbName> is the name of the content database.
<InstanceName> is the name of the SQL Server database instance name that you created in Step 2 of the procedure To install SQL Server 2008 Express R2. If you used the default named instance in that step, you must enter it here as “SQLExpress”. If you used the default instance, you must type ” “ here instead of using the default “SQLExpress” named instance.
You must repeat this command for each content database. Refer to the list of content databases that was generated by the Pre-upgrade checker in Step 5 of the To prepare for the upgrade to SharePoint Foundation 2010 with RBS on a domain controller procedure earlier in this article.
6. Create the Web applications to which the content databases will be attached. For information about how to create a Web application in SharePoint Foundation 2010, see Create a Web application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/d91d600f-10e6-4aac-af24-5e5d69860049(Office.14).aspx) or Create a Web application that uses Windows-claims authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bac469d0-7bf2-493f-9bc4-6095f8d68480(Office.14).aspx).
7. To attach and upgrade the content database to a SharePoint Foundation 2010 Web application, type the following command:
Mount-SPContentDatabase “<ContentDbName>” –DatabaseServer “<DbServer>” –WebApplication <http://SiteName>
Where:
<ContentDbName> is the name of the database.
<DbServer>is the name of the database server.
<http://SiteName> is the URL of the Web application.
For more information, see Move-SPBlobStorageLocation (http://technet.microsoft.com/library/5b66feac-c365-4dfd-9ccb-a66a4faa617f(Office.14).aspx) and Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx).
8. Create or restore needed customizations onto the new system. For recommended post-upgrade steps, see Perform post-upgrade steps (SharePoint Foundation 2010).
-
See Also
Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010) (http://technet.microsoft.com/library/da8cf825-2f79-49dd-bd4c-4ad0aad83f94(Office.14).aspx)
-
-
Upgrade a stand-alone installation to new hardware by using Remote BLOB Storage (database attach)
This article discusses the upgrade procedures that are required to upgrade from a stand-alone Windows SharePoint Services 3.0 system to an installation of SharePoint Foundation 2010 with Remote BLOB Storage (RBS) onto a new hardware platform.
Important:
We strongly recommend that you read the article Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage) for important information and recommendations about how to upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 together with RBS.
RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. RBS is an add-on that can be applied to Microsoft SQL Server 2008 Express and Microsoft SQL Server 2008 R2 Express. This implementation of RBS uses the SQL FILESTREAM provider. For more information about RBS and the FILESTREAM provider, see Overview of Remote BLOB Storage (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7522114b-7de5-434e-b028-8b99654a43be(Office.14).aspx).
Because of the database size limitations in SQL Server 2008 Express, install Windows Internal Database and restore the Windows SharePoint Services 3.0 databases into Windows Internal Database. You then install RBS, move the content database from Windows Internal Database into SQL Server, and then move the BLOBs into a content database that is set to use RBS.
By default, content databases in SharePoint Foundation 2010 are stored in SQL Server 2008 Express, which has a maximum size of 4 gigabytes (GB) per content database. Because SQL Server 2008 R2 Express supports content databases that are up to 10 GB, we recommend you install SQL Server 2008 R2 Express to support content databases. SQL Server 2008 R2 Express is a free upgrade that you can download and install from Microsoft SQL Server 2008 R2 Express Edition (http://go.microsoft.com/fwlink/?LinkID=189418).
Note:
This article assumes that you have installed SQL Server Management Studio on the database server in the Windows SharePoint Services 3.0 farm. If you do not have this software installed, you can download and install it from Microsoft® SQL Server® 2008 Management Studio Express (http://go.microsoft.com/fwlink/?LinkID=186132&clcid=0x409).
This article is not a comprehensive guide to upgrading to SharePoint Foundation 2010. Before you begin the upgrade process, read the following articles and create an upgrade plan:
About the upgrade process (SharePoint Foundation 2010)
Plan and prepare for upgrade (SharePoint Foundation 2010)
Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage)
In this article:
To prepare for the upgrade to SharePoint Foundation 2010 on the original server
To prepare for the upgrade to SharePoint Foundation 2010 on the new server
To install and configure Windows Internal Database on the new server
To move the content databases to the new server
To install SQL Server Express 2008 R2 on the new server
To install RBS on the new server
To install SharePoint Foundation 2010 on the new server
To migrate the content database to RBS and complete the installation
To prepare for the upgrade to SharePoint Foundation 2010 on the original server
1. Verify that the user account that is used to perform this procedure meets the requirements listed in Administrative and service accounts required for initial deployment (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b1aee1ea-45f6-4e05-ad93-9086f6ad7e79(Office.14).aspx), and that the user account is a member of the Administrators group on the local computer.
2. Verify that Management Studio is installed on the original server.
3. Back up the content databases by using the procedure described in How to: Back Up a Database (SQL Server Management Studio) (http://go.microsoft.com/fwlink/?LinkID=187768&clcid=0x409). You can use the default settings for most options, but you must use the following settings:
In step 1, you must set the instance name for Windows Internal Database as \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query.
In Step 12, select the option Destination. Make sure that the destination media has sufficient free space for the backup.
4. Run the pre-upgrade checker that is discussed in the article Perform pre-upgrade steps (SharePoint Foundation 2010).
The pre-upgrade checker report includes the names of all content databases. You have to have this list to migrate content databases to RBS. If you have multiple Web applications, you should also note which content databases are attached to which Web applications.
To prepare for the upgrade to SharePoint Foundation 2010 on the new server
1. Verify that the user account that is used to perform the upgrade and installation meets the requirements listed in Administrative and service accounts required for initial deployment (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b1aee1ea-45f6-4e05-ad93-9086f6ad7e79(Office.14).aspx), and that the user account is a member of the Administrators group on the local computer.
2. Confirm that the hardware configuration supports SharePoint Foundation 2010. For more information, see Hardware and software requirements (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dcdb7f80-5d48-4b7c-9cb5-affa5f293653(Office.14).aspx).
3. Verify that the available disk space meets the following requirements:
Available disk space is at least twice the size of the largest content database.
Available disk space is equal to or greater than the sum of the sizes of all content databases.
To install and configure Windows Internal Database on the new server
1. Click Start, and click Server Manager.
2. In Server Manager, click Features and then click Add Features.
3. In the Add Features wizard, scroll down the list of features, and then select Windows Internal Database.
4. Click Install.
5. Exit Server Manager.
6. Click Start, click Administrative Tools, and then click Computer Management.
7. Expand Services and Applications.
8. Click Services.
9. In the Services pane, right-click Windows Internal Database, and then click Properties.
10. Use the drop-down menu to change the Startup type to Automatic.
11. Click Start to start the service.
12. Click OK, and then exit Computer Management.
To move the content databases to the new server
1. Copy the content database backup files that you created in the procedure To prepare for the upgrade to SharePoint Foundation 2010 on the original server to the new server.
2. On the new server, download and install Management Studio from Microsoft® SQL Server® 2008 Management Studio Express (http://go.microsoft.com/fwlink/?LinkID=186132&clcid=0x409).
3. Use the instructions at How to: Restore a Database Backup (SQL Server Management Studio) (http://go.microsoft.com/fwlink/?LinkID=187769&clcid=0x409) to restore the databases by using Management Studio. Use the following settings for the restore procedure:
In Step 1, use the following name for the Windows Internal Database instance: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query.
In Step 5, enter the correct database name to be restored. We recommend that you use the same name that was used when the database was backed up.
In Step 7, select the database file that you copied in Step 1.
Accept all other default options and complete the restore.
To install SQL Server Express 2008 R2 on the new server
1. Download SQL Server 2008 R2 Express from Microsoft SQL Server 2008 R2 Express Edition (http://go.microsoft.com/fwlink/?LinkID=189418).
2. Follow the onscreen instructions to install SQL Server 2008 R2 Express.
For additional information, see How to: Install SQL Server 2008 (Setup) (http://go.microsoft.com/fwlink/?LinkID=187771&clcid=0x409).
Especially note the following settings:
On the Instance Configuration page, specify whether to install a Default instance or a Named instance. If you create a named instance, note the instance name. You have to supply this name in a later procedure.
On the Server Configuration — Service Accounts page, you must specify login accounts for SQL Server services. You can assign the same login account to all SQL Server services, or you can configure each service account individually.
On the Database Engine Configuration page, make sure that the domain account that is being used for this installation is listed as a SQL Server administrator.
To install RBS on the new server
1. Go to http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388) to download the RBS_X64.msi file.
Important:
You must install the version of RBS that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The version of RBS must be 10.50.xxx. No earlier version of RBS is supported for SharePoint Foundation 2010.
2. Open the folder that contains the .msi file, and double-click RBS_X64.msi to start the Install SQL Remote BLOB Storage Wizard.
3. In the Install SQL Remote BLOB Storage Wizard, on the Feature Selection page, expand Server, click the down arrow next to Execute scripts, and then click Entire feature will be unavailable.
4. Expand FILESTREAM Provider, expand Server, click the down arrow next to Execute scripts, and then click Entire feature will be unavailable.
Note:
The database that will host the scripts does not yet exist. It is created during the database upgrade process. The Execute scripts option will be installed automatically during the installation of SharePoint Foundation 2010.
5. Complete the wizard by using the default values.
During the installation, a dialog box appears about an RBS Maintainer task. Click OK in that dialog box to proceed with the installation.
To install SharePoint Foundation 2010 on the new server
1. Install SharePoint Foundation 2010 by following the instructions in Install SharePoint Foundation 2010 on the farm servers (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a.aspx#InstallSF). You must use the database instance name that you created in Step 2 of the procedure To install SQL Server Express 2008 R2 on the new server that you performed earlier in this article. If you used the default named instance in that step, you must enter it here as “SQLExpress”. If you used the default instance, then you must enter ” “ here instead of using the default SQLExpress named instance.
Note that you are creating a new installation ofSharePoint Foundation 2010. You are performing a database attach upgrade, not an in-place upgrade.
Note:
After you install SharePoint Foundation 2010, do not create any Web applications until instructed to do this later in this article.
To migrate the content database to RBS and complete the installation
1. Verify that the same user account that was used to install SharePoint Foundation 2010 and RBS is the user account that is performing this procedure.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command to migrate the content database to RBS. You must repeat this command for each content database. Refer to the list of content databases that was generated by the Pre-upgrade checker in Step 4 of the procedure To prepare for the upgrade to SharePoint Foundation 2010 on the original server earlier in this article.
Move-SPBlobStorageLocation –SourceDatabase “<DbName>” –DestinationDataSourceInstance “<InstanceName>”
Where:
<DbName> is the name of the content database that you restored into Windows Internal Database.
<InstanceName> is the name of the SQL Server database instance that you created in the procedure To install SQL Server Express 2008 R2 on the new server earlier in this article. If you used the default named instance in that step, you must enter it here as “SQLExpress”. If you used the default instance, then you must enter ” “ here instead of using the default SQLExpress named instance.
6. Create the Web applications that attach to the content database. For information about how to create a Web application in SharePoint Foundation 2010, see Create a Web application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/d91d600f-10e6-4aac-af24-5e5d69860049(Office.14).aspx) or Create a Web application that uses Windows-claims authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bac469d0-7bf2-493f-9bc4-6095f8d68480(Office.14).aspx).
7. Type the following command to attach and upgrade a content database to a Web application:
Mount-SPContentDatabase “<DbName>” –WebApplication <http://SiteName>
Where:
<DbName> is the name of the database.
<http://SiteName> is the name of the Web application.
Repeat this command for each content database.
For more information, see Move-SPBlobStorageLocation (http://technet.microsoft.com/library/5b66feac-c365-4dfd-9ccb-a66a4faa617f(Office.14).aspx) and Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx).
8. Create or restore needed customizations onto the new system. For recommended post-upgrade steps, see Perform post-upgrade steps (SharePoint Foundation 2010).
-
See Also
Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010) (http://technet.microsoft.com/library/da8cf825-2f79-49dd-bd4c-4ad0aad83f94(Office.14).aspx)
-
-
Perform a database attach upgrade to SharePoint Foundation 2010
Now that you have learned about the upgrade process by reading the articles in About the upgrade process (SharePoint Foundation 2010), and planned for your upgrade by following the steps in the articles in Plan and prepare for upgrade (SharePoint Foundation 2010), you are ready to perform database attach upgrade to Microsoft SharePoint Foundation 2010. You can follow the steps in this section for both a trial upgrade and your actual in-place upgrade on your production farm.
In this section:
Checklist for database attach upgrade (SharePoint Foundation 2010)
Use this checklist to make sure that you follow all necessary steps as you prepare for upgrade, perform the upgrade, and perform post-upgrade steps.
Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade
Before you can attach and upgrade your databases, you must fully configure your new environment.
Attach databases and upgrade to SharePoint Foundation 2010
After your new environment is fully configured, follow these steps to attach the databases and upgrade your SharePoint sites.
-
Checklist for database attach upgrade (SharePoint Foundation 2010)
This article contains a checklist you can use to make sure that you followed all necessary steps as you prepare for upgrade, perform the upgrade, and perform post-upgrade steps.
In this article:
Some of the steps include notes about the amount of time the steps might take. These are rough estimates only, to give you a relative idea of the duration of the step. To find out how much time each step will take for your environment, we recommend that you perform trial upgrades in a test environment. For more information, see Estimate how long the upgrade process will take and the space that you need (SharePoint Foundation 2010) and Use a trial upgrade to find potential issues (SharePoint Foundation 2010).
-
Prepare for upgrade
Follow these steps in order before you begin a database attach upgrade:
Pre-upgrade steps for a database attach upgrade
Notes
Prepare for upgrade
[ ]
Run the pre-upgrade checker
Run the pre-upgrade checker and address any issues. Use the report that is generated by the tool to fill out the Upgrade planning worksheet.
Detailed steps: Run the pre-upgrade checker (SharePoint Foundation 2010).
Perform this step multiple times as you clean up your environment and test your upgrade process.
Running the checker takes only a few minutes, but addressing any issues might take days or weeks.
[ ]
Create an inventory of server-side customizations in the environment
Create an inventory of the server-side customizations in your environment (solutions, features, Web Parts, event handlers, master pages, page layouts, CSS files, and so on). Much of this information is reported when you run the pre-upgrade checker. Record all customizations needed for your environment in the upgrade worksheet.
Detailed steps: Identify and install customizations in the “Use a trial upgrade to find potential issues” article.
Perform this step for the whole environment. Check each Web server to make sure that you don’t miss any customizations. Keep the inventory up to date as you prepare for the upgrade.
[ ]
Clean up your environment
Before you begin upgrading, you should make sure that your environment is functioning in a healthy state and that you clean up any content that you do not have to upgrade. Clean up any orphaned sites or data, address any large lists and large ACLs, remove extraneous document versions, and remove any unused templates, features and Web Parts.
Detailed steps: Cleaning up your environment before upgrade (SharePoint Foundation 2010).
Perform this step once for the whole environment.
This process might take days or weeks to complete.
Prepare the new environment
Also see Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade.
[ ]
Install and configure SharePoint Foundation 2010 and any language packs
Install the prerequisite software, and then install and configure SharePoint Foundation 2010.
Perform these steps on each server in your farm.
This step might take one or more hours, depending on how many servers are in your environment.
[ ]
Configure general farm settings
Reapply any general farm settings that you must have from your previous farm — such as blocked file types and e-mail and quota settings — and add users or groups to the Farm Administrators group. Configure new settings such as usage and health data collection, diagnostic logging, and mobile accounts.
Important:
If you had disabled the Workflow Auto Cleanup timer job in your Windows SharePoint Services 3.0 environment, make sure that you disable this timer job in your new environment also. If this timer job is enabled in the new environment and disabled in the previous version environment, you might lose workflow associations when you upgrade. For more information about this timer job, see Disable preservation of workflow history (SharePoint Foundation 2010) (http://technet.microsoft.com/library/29e71181-0653-43ae-ab92-e6d109ac011b(Office.14).aspx).
Perform this step once for the whole environment.
[ ]
Create and configure Web applications
Create a Web application for each Web application that existed in the old environment.
Perform this step once for the whole environment.
[ ]
Reapply server-side customizations
Manually transfer all server-side customizations into your new farm. Refer to the inventory you created in the upgrade worksheet to make sure that you install any components that your sites depend on to work correctly.
Make sure that you reapply customizations to all Web servers in the farm.
[ ]
Verify the new environment
After you set up the new environment, you can perform tests to make sure it contains all the components you have to have before you upgrade your data.
Perform this step once for the whole environment.
-
Perform the upgrade
Follow these steps in order during a database attach upgrade. Steps required for database attach with read-only databases are also included.
Detailed steps: Attach databases and upgrade to SharePoint Foundation 2010.
Warning:
When you upgrade from an installation of Windows SharePoint Services 3.0 that uses Windows Internal Database and the database size exceeds 4 GB, you must perform additional steps. For more information about these steps, see Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage).
Perform the database attach upgrade
Notes
[ ]
Run the pre-upgrade checker
Run the pre-upgrade checker again to identify any new or remaining issues before you set the databases to read-only or back up the databases.
Detailed steps: Run the pre-upgrade checker (SharePoint Foundation 2010).
Running the checker takes only a few minutes, but addressing any issues might take longer.
[ ]
Set the previous version databases to be read-only (database attach with read-only databases)
If you want your original environment to remain available to users in a read-only state, set the databases to read-only before you back them up.
Perform this step for each content database in your environment.
Depending on your organization, you might need a database administrator to perform this task.
[ ]
Back up databases
Back up all of your content databases before you begin the database attach upgrade process.
Perform this step for each content database in your environment.
This step can take an hour, several hours, or longer, depending on your data set and your environment.
Depending on your organization, you might need a database administrator to perform this task.
[ ]
Detach the previous version databases (standard database attach)
If you are going to upgrade the original databases (rather than a backup copy), detach the original databases from the instance of Microsoft SQL Server so that you can move them to the new environment.
Perform this step for each content database in your environment.
Depending on your organization, you might need a database administrator to perform this task.
[ ]
Restore a backup copy of the database (database attach with read-only databases)
If you are going to upgrade a copy of the databases, restore the databases from the backup.
Perform this step for each content database in your environment.
This step can take an hour or longer, depending on your data set and your environment.
Depending on your organization, you might need a database administrator to perform this task.
[ ]
Verify custom components
Use the Test-SPContentDatabaseWindows PowerShell cmdlet to verify that you have all the custom components that you need for that database.
Perform this step for each content database in your environment.
Running the cmdlet takes only a few minutes, but addressing any issues might take longer.
[ ]
Verify permissions
Ensure that the account that you use to attach the databases is a member of the db_owner fixed database role for the content databases that you want to upgrade.
[ ]
Attach a content database to a Web application
Attach the first content database that you want to upgrade. You must perform this action from the command line. You can use the Mount-SPContentDatabaseWindows PowerShell cmdlet or the AddContentDB Stsadm operation.
Perform this step for one content database in your environment.
This step might take an hour, several hours, or longer, depending on your data set and hardware on the Web servers, database servers, and storage subsystem.
[ ]
Verify upgrade for the first database
Verify that upgrade succeeded for the first database, and review the site to see if there are any issues.
Detailed steps: Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
Perform this step for the content database you just attached.
[ ]
Attach remaining databases
Attach and upgrade the remaining content databases in your environment. You must perform this action from the command line.
Perform this step for each of the remaining content databases in your environment.
This step might take an hour, several hours, or longer, depending on your data set, whether you are upgrading multiple databases in parallel, and the hardware on the Web servers, database servers, and storage subsystem.
[ ]
Monitor upgrade progress
Use the Upgrade Status page in SharePoint Central Administration to monitor progress as your sites are upgraded.
Detailed steps: Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
Perform this step for each content database that you upgrade.
This step might take an hour, several hours, or days, depending on your data set.
[ ]
Verify upgrade for the remaining database
Verify that upgrade succeeded for the remaining databases, and review the sites to see if there are any issues.
Detailed steps: Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
Perform this step for each of the remaining content databases in your environment.
This step might take an hour, several hours, or days, depending on your content.
-
Perform post-upgrade steps
Follow these steps in order after you perform a database attach upgrade.
Post upgrade steps for database attach upgrade
Notes
[ ]
Verify upgrade and review upgraded sites
Review sites to be sure that they have been upgraded successfully and are ready for users to view.
Detailed steps: Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
Perform this step for every upgraded database and site collection in your environment.
This step might take an hour, several hours, or days, depending on your content.
You should also have site owners review their sites and report any issues.
-
See Also
Upgrade Worksheet for SharePoint 2010 Products (http://go.microsoft.com/fwlink/?LinkId=179928)
-
-
Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade
When you upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 by using the database attach approach, you upgrade only the content for your environment and not the configuration settings. Using a database attach upgrade is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process. For more information about how to choose an upgrade approach, see Determine upgrade approach (SharePoint Foundation 2010).
Before you can upgrade the data, you must configure a new server or server farm by using SharePoint Foundation 2010. This article explains the elements you need to configure to create that new environment. For more information about the general process of upgrading by using the database attach upgrade approach, see Upgrade process overview (SharePoint Foundation 2010).
Important:
To perform the steps in this article, you must have administrator rights on the local server computer. For more information, see Administrative and service accounts required for initial deployment (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b1aee1ea-45f6-4e05-ad93-9086f6ad7e79(Office.14).aspx).
In this article:
-
Before you begin
Before you begin to create the new environment for a database attach upgrade, review the following information about permissions, hardware requirements, and software requirements.
Ensure that you have met all hardware and software requirements. You must have a 64-bit version of Windows Server 2008 or Windows Server 2008 R2. For server farms, you must also have a 64-bit version of SQL Server 2005 or SQL Server 2008. For more information about these requirements (such as specific updates that you must install), see Determine hardware and software requirements (SharePoint Foundation 2010).
Ensure that you are prepared to set up the required accounts by using appropriate permissions. For detailed information, see Administrative and service accounts required for initial deployment (SharePoint Foundation 2010).
Run the pre-upgrade checker on your original environment. The pre-upgrade checker identifies potential upgrade issues in your environment so that you can address them before you upgrade. It can also help you identify settings that you need in your new environment. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
-
Create and configure the new environment
The process of creating and configuring the new environment contains several steps, which must be performed in the correct sequence. These steps are:
1. Install SharePoint Foundation 2010 on the server or servers.
2. Configure service applications.
3. Configure general farm settings.
4. Create and configure Web applications.
5. Reapply customizations.
The remainder of this section describes these steps and provides links to other articles that contain step-by-step instructions for performing them. After you have performed these steps, you can verify the environment and then perform the upgrade.
-
Install
The first step in creating your new environment is to install SharePoint Foundation 2010 and configure your new server or server farm. You must do the following:
1. Run the Microsoft SharePoint Products Preparation Tool to install all required software.
2. Run Setup to install the product.
3. Install any language packs that you need in your environment.
4. Run the SharePoint Products Configuration Wizard to configure your server or servers.
The following articles provide step-by-step instructions for performing these tasks.
Install and configure the product
Follow the steps in one of the following articles to install and configure SharePoint Foundation 2010 on a single server or server farm:
Deploy a single server with SQL Server (SharePoint Foundation 2010) (http://technet.microsoft.com/library/58d28a34-7a84-4564-a4cb-0e6b5425f67e(Office.14).aspx)
Multiple servers for a three-tier farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a(Office.14).aspx)
For more deployment scenarios (such as installing in a stand-alone environment with SQL Express), see Deployment scenarios (SharePoint Foundation 2010) (http://technet.microsoft.com/library/e13a061c-6c24-42a7-a584-933b44e3433d(Office.14).aspx).
Install and configure language packs
Follow the steps in Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx) to install and configure any language packs that are needed for the sites in your environment.
-
Configure service applications
You must configure any services you want to use in your new environment, such as the Business Data Connectivity service. The steps included in the deployment scenarios articles listed above describe how to use the Initial Farm Configuration Wizard to enable all services. However, you can also configure services manually. For more information about how to configure services manually, see Configure services (SharePoint Foundation 2010) (http://technet.microsoft.com/library/88da9bdb-b7c2-4174-997b-d767b9b9c9ea(Office.14).aspx).
-
Configure general farm settings
The next step in creating the new environment is to apply general farm settings. You must manually reapply configuration settings from your previous version farm, including the following:
Incoming and outgoing e-mail settings
Any farm–level security and permission settings, such as adding user or group accounts to the Farm Administrators group.
Blocked file types
Quota templates
And you must configure any new farm-level settings that you want to use, such as the following:
Usage and health data collection
Diagnostic logging
Mobile accounts
For more information about how to configure these settings, see Configure farm settings (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7c6d7151-57f4-49c3-beba-6bd8e252a8ec(Office.14).aspx).
Important:
If you had disabled the Workflow Auto Cleanup timer job in your Windows SharePoint Services 3.0 environment, make sure that you disable this timer job in your new environment also. If this timer job is enabled in the new environment and disabled in the previous version environment, you might lose workflow associations when you upgrade. For more information about this timer job, see Disable preservation of workflow history (SharePoint Foundation 2010) (http://technet.microsoft.com/library/29e71181-0653-43ae-ab92-e6d109ac011b(Office.14).aspx).
-
Create and configure Web applications
Create a Web application for each Web application that existed in the original environment. For each Web application, do the following:
Use the same URL and configure any alternate-access mapping settings.
Note:
If you use a different URL, Microsoft Office applications might not be redirected correctly to the new URLs and any bookmarks to the old URLs will not work.
Use the same authentication method.
Important
If you were using forms-based authentication, you will need to configure claims-based authentication instead. You must also create a Web application policy to grant Full Control to the user account that will be performing the database attach upgrade.
For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010).
Re-create included paths (such as /Sites).
Enable self-service site creation for any Web application that used it in the previous environment.
For more information about how to configure Web applications and authentication, see the following articles:
For classic authentication: Create a Web application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/d91d600f-10e6-4aac-af24-5e5d69860049(Office.14).aspx)
For claims-based authentication: Create a Web application that uses Windows-claims authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bac469d0-7bf2-493f-9bc4-6095f8d68480(Office.14).aspx) and Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010)
-
Reapply customizations
One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Make sure that any custom elements you have to have are installed on your front-end Web servers before you begin the upgrade process. You can use the pre-upgrade checker to compile a list of server-side customizations in your environment. For more information, see Identify and install customizations in the article “Use a trial upgrade to find potential issues.”
In this step, you manually transfer all customizations into your new farm. Make sure to install any components that your sites depend on to work correctly, including the following:
Custom site definitions
Note:
If the site definition was created in Windows SharePoint Services 3.0, you can copy it over to the new environment as-is. If, however, it was created in Windows SharePoint Services version 2.0, you might have to create an upgrade definition file to map the site definition to the new features in Windows SharePoint Services 3.0. For more information, see Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287930(Office.12).aspx) and Deploy upgrade definition files and new site definitions (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288457(Office.12).aspx).
Custom style sheets, including cascading style sheets, and images
Custom Web Parts
Custom Web services
Custom features and solutions
Custom assemblies
Web.config changes (such as security)
Ensure that you transfer any unique settings from the Web.config files for each Web application to the new servers.
Any other components or files on which your sites depend.
For more information about how to update customizations for use in SharePoint Foundation 2010, see: Redeploying Customizations and Solutions in SharePoint Foundation 2010 and SharePoint Server 2010 (http://msdn.microsoft.com/en-us/library/ee662217(office.14).aspx). For more information about how to deploy customizations to your environment, see Deploy customizations – overview (SharePoint Foundation 2010) (http://technet.microsoft.com/library/5894888f-51b6-4fff-840e-2d82008d73ee(Office.14).aspx).
-
-
Verify the new environment
After you have set up the new environment, you can perform tests to make sure it contains all the components you need before you upgrade your data. To test your new environment, you can use the following methods:
Create a new Web application and then use the Windows PowerShellTest-SPContentDatabase cmdlet to verify that all the server-side customizations that are needed for that content database are present in the new environment. Do not attach or upgrade the database. For more information, see Test-SPContentDatabase (http://technet.microsoft.com/library/ed095a0a-fa1a-4323-8503-624f0e09707d(Office.14).aspx).
Note:
You can also run this command on the original content database, but the database should not be in active use at the time.
Use the enumallwebs Stsadm operation in your Windows SharePoint Services 3.0 environment to see which template each site is associated with and then verify whether the template is installed in your SharePoint Foundation 2010 environment. The October Cumulative Update includes improvements to the enumallwebs operation that can help you find customizations in use. For more information about this operation, see Enumallwebs: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/dd793606(Office.12).aspx).
-
Perform the upgrade
After you finish preparing the new environment, you can attach and upgrade the databases.
Follow the steps in Attach databases and upgrade to SharePoint Foundation 2010 to attach and upgrade the databases from the Windows SharePoint Services 3.0 server or server farm to the new SharePoint Foundation 2010 server or server farm.
Important:
When you upgrade from an installation of Windows SharePoint Services 3.0 that uses Windows Internal Database and the database size exceeds 4 GB, you must perform additional steps. For more information, see Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage).
-
Attach databases and upgrade to SharePoint Foundation 2010
When you upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 by using the database attach upgrade approach, you upgrade only the content for your environment and not the configuration settings. Using a database attach upgrade approach is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process. For more information about how to choose an upgrade approach, see Determine upgrade approach (SharePoint Foundation 2010).
The first step in the process is to set up a new environment to host the upgraded content. If you have not yet set up and configured the new environment, follow the steps in Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade to do so.
After you set up the new environment, you can use the procedures in this article to detach and then reconnect the databases to perform the actual upgrade. This article contains the steps required to perform a standard database attach upgrade and a database attach upgrade with read-only databases.
In this article:
Set the previous version databases to be read-only (database attach with read-only databases)
Back up the previous version databases by using SQL Server tools
Detach the previous version databases (standard database attach)
Restore a backup copy of the database (database attach with read-only databases)
Attach a content database to a Web application
Verification: Verify upgrade for the first database
Attach the remaining databases
Verification: Verify upgrade for additional databases
Note:
One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Be sure that any custom elements you have to have are installed on your front-end Web servers before you begin the upgrade process. Use the pre-upgrade checker — and, for a database attach upgrade, also use the test-spcontentdatabaseWindows PowerShell cmdlet — to identify any custom elements that your sites might be using. For more information, see Identify and install customizations in the article “Use a trial upgrade to find potential issues.”
For more information about the general process of upgrading by using the database attach upgrade approach, see Upgrade process overview (SharePoint Foundation 2010).
-
Process overview
When you upgrade by using database attach upgrade, you detach the databases in the old farm and then attach them to the new farm. When you attach a database to the new farm, the upgrade process runs and upgrades the whole database. The database attach upgrade process is similar to the in-place upgrade process. The difference is that the database attach upgrade process is performed manually, and is performed in a separate environment.
If you want to preserve your original farm and allow users to continue to access their data, you must set the databases to read-only and then attach a backup copy of the databases.
Note:
The part of the process in this article that is specific to moving a database from one computer that is running Microsoft SQL Server to a different computer that is running SQL Server is known as planned relocation. For more information about planned relocation, see Moving User Databases (http://go.microsoft.com/fwlink/?LinkId=148425).
For a general overview of the upgrade process, see Upgrade process overview (SharePoint Foundation 2010).
-
Before you begin
Before you begin the database attach upgrade, review the following information about permissions, hardware requirements, and software requirements. Follow the specified steps to install or configure prerequisite software or to modify settings.
Ensure that you have met all hardware and software requirements. You must have a 64-bit version of Windows Server 2008 or Windows Server 2008 R2. For server farms, you must also have a 64-bit version of SQL Server 2005 or SQL Server 2008. For more information about these requirements (such as specific updates that you must install), see Determine hardware and software requirements (SharePoint Foundation 2010).
Ensure that you are prepared to set up the required accounts by using appropriate permissions. For detailed information, see Administrative and service accounts required for initial deployment (SharePoint Foundation 2010).
Ensure that the account you use to attach the databases is a member of the db_owner fixed database role for the content databases that you want to upgrade.
Run the pre-upgrade checker tool on the sites that are stored in the databases. The pre-upgrade checker identifies potential upgrade issues in your environment so that you can address them before you upgrade. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
Create a new server farm environment. For information about how to create the new environment, see Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade.
Check for and repair any database consistency errors. For more information, see Database maintenance for Windows SharePoint Services 3.0 (white paper) (http://technet.microsoft.com/en-us/library/cc307161(Office.12).aspx).
-
Set the previous version databases to be read-only (database attach with read-only databases)
If you are using the read-only databases hybrid approach to upgrade, set the previous version databases to read-only before you back up the databases. In any type of database attach upgrade, you can also set the databases to read-only temporarily to ensure that you capture all the data in the backup so that you are restoring and upgrading the current state of the environment. If the databases are set to read-only, users can continue to view content, but they will be unable to add or change content.
Important:
You cannot upgrade a database that is set to read-only. If you are using a database attach with read-only databases, you restore a copy of the database and perform the upgrade on the copy. If you are not using this method, but want to set content databases to read-only temporarily while you back up the current data, make sure that you set the databases to read-write before you attach and upgrade the databases.
Important:
Be sure you have run the pre-upgrade checker before you perform this procedure. For more information, see Run the pre-upgrade checker (SharePoint Foundation 2010).
To set a database to read-only in SQL Server 2000
1. In SQL Server Enterprise Manager, right-click the name of the database that you want to set to read-only, and then click Properties.
2. In the Properties dialog box, click the Options tab.
3. Under Access, select the Read-only check box, and then click OK.
To set a database to read-only in SQL Server 2005
1. In SQL Server Management Studio, right-click the name of the database that you want to set to read-only, and then click Properties.
2. In the Select a page section, click Options.
3. In the right pane, under Other options, in the State section, next to Database Read-Only, click the arrow, and then select True.
To set a database to read-only in SQL Server 2008
1. In SQL Server Management Studio, in Object Explorer, connect to an instance of the Database Engine, expand the server, and then expand Databases.
2. Select the database that you want to configure to be read-only, right-click the database, and then click Properties.
3. In the Database Properties dialog box, in the Select a page section, click Options.
4. In the right pane, under Other options, in the State section, next to Database Read-Only, click the arrow, and then select True.
You can configure the READ_ONLY database availability option by using Transact-SQL. For more information about how to use the SET clause of the ALTER DATABASE statement, see Setting Database Options (http://go.microsoft.com/fwlink/?LinkId=148362).
-
Back up the previous version databases by using SQL Server tools
Follow the appropriate procedure to back up databases in SQL Server 2000, SQL Server 2005, or SQL Server 2008. Repeat these steps for each content database in your server farm.
You do not have to back up the configuration or admin content databases, because you will re-create these databases in the new server farm.
For more information about the kinds of databases that you might have in a Windows SharePoint Services 3.0 server farm, see Database types and descriptions (Windows SharePoint Services 3.0) (http://technet.microsoft.com/en-us/library/cc974471(Office.12).aspx).
At the end of this procedure, you will have created duplicates of the read-only content databases.
To back up a database in SQL Server 2000
1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
2. In SQL Server Enterprise Manager, expand Microsoft SQL Servers.
3. Expand SQL Server Group.
4. Expand (local) (Windows NT).
5. Expand Databases.
6. Right-click the database that you want to back up, point to All Tasks, and then click Backup Database.
7. In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then in the Backup area, select Database – complete.
8. In the Destination area, either select an existing destination or do the following:
a. Click Add.
b. In the Select Backup Destination box, select File Name, and then next to the File Name box, click Browse.
c. In the Backup Device Location – (local) dialog box, in the File name box, type a file name, and then click OK.
d. Click OK again to close the Select Backup Destination dialog box.
9. Click OK to start the backup process.
10. Click OK to acknowledge that the backup process is complete.
Repeat the previous procedure to back up all the other content databases that are used by Windows SharePoint Services 3.0 in your environment.
To back up a database in SQL Server 2005
1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
2. In the Connect to Server box, fill in the connection information, and then click Connect.
3. After you connect to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by expanding the server name.
4. Expand Databases, right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
5. In the Source area, in the Database box, verify the database name.
6. In the Backup type box, select Full.
7. Under Backup component, select Database.
8. In the Backup set area, in the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set.
9. In the Destination area, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.
10. Click OK to start the backup process.
Repeat the previous procedure to back up all the other content databases that are used by Windows SharePoint Services 3.0 in your environment.
To back up a database in SQL Server 2008
1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
2. In the Connect to Server box, fill in the connection information, and then click Connect.
3. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.
4. Expand Databases, right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
5. In the Source area, in the Database box, verify the database name.
6. In the Backup type box, select Full.
7. Under Backup component, select Database.
8. In the Backup set area, in the Name text box, either accept the default backup set name or type a new name.
9. In the Destination area, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.
10. Click OK to start the backup process.
Repeat the previous procedure to back up all the other content databases that are used by Windows SharePoint Services 3.0 in your environment.
-
Detach the previous version databases (standard database attach)
Before you can attach your databases to the new environment and upgrade the data, you need to detach them from the current environment. After you have detached the databases, you can move them to a new database server or leave them on the existing database server and attach them to the Web applications.
Important:
Do not use the following procedure if you are performing a database attach upgrade with read-only databases. To continue to provide your users with access to their content, you need to leave the databases attached, and follow the steps in the Restore a backup copy of the database (database attach with read-only databases) (http://technet.microsoft.com/library/38ef5fbb-181b-49bf-aa7a-2d5c47b3811c.aspx#restore) section later in this article to make a copy of the databases instead.
To detach a content database from a Web application
1. In Central Administration, on the Application Management page, in the SharePoint Web Application Management section, click Content databases.
2. On the Manage Content Databases page, click the content database you want to detach.
Note:
If the content database does not appear, it might be associated with another Web application. To select another Web application, on the Web Application menu, click Change Web Application.
3. On the Manage Content Database Settings page, in the Remove Content Database section, select the Remove content database check box, and then click OK.
Note:
Removing the content database does not delete the database; it only removes the association of the database with the Web application.
4. Repeat steps 2 and 3 for each content database that you want to detach.
You can also use the deletecontentdb Stsadm operation to detach a content database from a Web application. For more information, see Deletecontentdb: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287664(Office.12).aspx).
If you are moving the databases to a different database server, you must also detach the databases from the instance of SQL Server before you move them and attach them to the new instance of SQL Server after you move them.
Important:
If you move your databases to a different instance of SQL Server, make sure to verify that security is configured correctly. Check that the accounts you use have the appropriate fixed roles and permissions on the databases, and that they will still be valid accounts if you are moving across domains.
To detach a database from an instance of SQL Server and move it to another instance of SQL Server
1. In SQL Server 2005 Management Studio, open the source instance of SQL Server, and then expand the Databases node.
2. Right-click the content database, point to Tasks, and then click Detach. Repeat this step for each content database that you want to detach and move.
Note:
Use this procedure to move only content databases. Do not detach any other databases.
3. In Windows Explorer, browse to the location of the .mdf and .ldf files for the content databases.
4. Select the .mdf and .ldf files for the database you want to move and either copy or move them to the destination directory.
5. In SQL Server 2005 Management Studio, open the source instance of SQL Server.
6. Right-click the Databases node, point to Tasks, and then click Attach.
7. In the Attach Database dialog box, browse to the location to which you transferred the .mdf and .ldf files, select the .mdf file for the database you want to attach, and then click OK.
8. Repeat steps 6 and 7 for each content database that you are moving.
-
Restore a backup copy of the database (database attach with read-only databases)
After you configure the new server farm, you can restore the backup copies of the databases on one of the following: Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3. Note that you must restore to a 64-bit version of SQL Server 2008 R2, SQL Server 2008 with SP1 and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3. Start with one database, and then verify that the restoration has worked before you restore the other databases.
The following section provides procedures for restoring the backups.
To restore a backup copy of a database in SQL Server 2005 Enterprise Edition
1. In SQL Server Management Studio, right-click Databases, and then click Restore Database. The Restore Database dialog box appears.
2. In the Restore Database dialog box, on the General page, in the To database box, type the name of the database you are restoring.
3. In the To a point in time text box, keep the default (Most recent possible).
4. To specify the source and location of the backup sets to restore, click From device, and then click Browse to select the backup file.
5. In the Specify Backup dialog box, in the Backup media box, make sure that File is selected.
6. In the Backup location area, click Add.
7. In the Locate Backup File dialog box, select the file that you want to restore, and then click OK.
8. In the Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.
9. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.
10. Click OK to start the restore process.
To restore a backup copy of a database in SQL Server 2008 Enterprise
1. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.
2. Right-click Databases, and then click Restore Database. The Restore Database dialog box appears.
3. In the Restore Database dialog box, on the General page, type the name of the database to be restored in the To database list.
4. In the To a point in time text box, retain the default (Most recent possible).
5. To specify the source and location of the backup sets to restore, click From device, and then click Browse to select the backup file.
6. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.
7. In the Backup location area, click Add.
8. In the Locate Backup File dialog box, select the file that you want to restore, click OK, and then, in the Specify Backup dialog box, click OK.
9. In the Restore Database dialog box, under Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.
10. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.
11. Click OK to start the restore process.
-
Verify custom components
Before you attach the content databases to the Web applications, use the Test-SPContentDatabaseWindows PowerShell cmdlet to verify that you have all the custom components that you need for that database.
To verify custom components are available by using Windows PowerShell
1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command:
Test-SPContentDatabase -Name <DatabaseName> -WebApplication <URL>
Where:
<DatabaseName> is the name of the database you want to test.
<URL> is the URL for the Web application that will host the sites.
For more information, see Test-SPContentDatabase (http://technet.microsoft.com/library/ed095a0a-fa1a-4323-8503-624f0e09707d(Office.14).aspx).
-
Attach a content database to a Web application
When you attach a content database, make sure that the root site for the Web application is included in the first content database that you attach. In other words, before you continue, examine the root of the Web application in the original server farm to determine the first site collection. After you attach the database that contains the root site, you can attach the other content databases for the Web application in any order. You do not have to create any site collections to store the content before you attach the database; this process creates the site collections for you. Make sure that you do not add any new site collections until you have restored all the content databases.
Important:
If you are moving the content databases across domains or forests or into another environment that has different service accounts, ensure that the permissions for the service accounts are still correct before you attach the databases.
You can use either the Mount-SPContentDatabase cmdlet in Windows PowerShell or the addcontentdb Stsadm command to attach a content database to a Web application. Using the SharePoint Central Administration pages to attach a content database is not supported for upgrading.
Ensure that the account you use to attach the databases is a member of the db_owner fixed database role for the content databases that you want to upgrade.
Important
If you were using forms-based authentication, you will need to configure claims-based authentication for your Web application before you attach any databases. You must also create a policy to grant Full Control to the Web application to the user account that will be performing the database attach upgrade.
For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010).
Tip
You cannot attach the same content database more than once to a farm, even on different Web applications. Each site collection in a content database has a GUID that is associated with it, which is registered in the configuration database. Therefore, you cannot add the same site collection twice to the farm, even in separate Web applications. Although you can successfully attach the database in this situation, you will be unable to start the site collection.
If you need a duplicate copy of a site collection in the same farm, first attach the database that contains the site collection to a separate farm, and then use the Stsadm backup and restore operations to copy the site collection over to the other farm. The Stsadm backup and restore process creates a new GUID for the site collection.
To attach a content database to a Web application by using Windows PowerShell
1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command:
Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> [-Updateuserexperience]
Where:
<DatabaseName> is the name of the database you want to upgrade.
<ServerName> is server on which the database is stored.
<URL> is the URL for the Web application that will host the sites.
Updateuserexperience is the choice to update to the new user experience or stay in the old user experience (part of Visual Upgrade). When you include this parameter, the site is set to preview the new user experience. Omit this parameter if you want the site to remain in the old user experience after upgrade. For more information, see Plan visual upgrade (SharePoint Foundation 2010). For more information, see Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx)
.
Note:
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.
To attach a content database to a Web application by using the Stsadm command-line tool
1. On the drive on which SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.
2. Type the following command, and then press ENTER:
stsadm -o addcontentdb -url<URL> -databasename<DatabaseName>
[-databaseserver<ServerName>] [-databaseuser<UserName>]
[-databasepassword<Password>] [-sitewarning<SiteWarningCount>]
[-preserveolduserexperiencetrue/false]
[-sitemax<SiteMaxCount>]
[-assignnewdatabaseid][-clearchangelog]
Note
When you set the preserveolduserexperience parameter to true, the sites in the content database keep the look of the previous version after upgrade. When you set this parameter to false, the sites are upgraded to the new look and feel. The default for this parameter is true, which preserves the old look and feel.
This parameter is part of the Visual Upgrade feature. For more information, see Plan visual upgrade (SharePoint Foundation 2010).
For more information, see Addcontentdb: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc288692(Office.12).aspx).
-
Verification: Verify upgrade for the first database
After you have attached a database, you can use the Upgrade Status page in Central Administration to check the status of upgrade on your site collections. After the upgrade process is complete, you can review the upgrade log file to see whether there were any issues during upgrade. Also, you can review each upgraded site to find and address any issues with how the content is displayed. For more information, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).
To view the Upgrade Status page
In Central Administration, click Upgrade and Migration, and then click Check upgrade status.
To open the upgrade log file
The upgrade error log file and the upgrade log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\14\LOGS. The logs are named in the following format: Upgrade-YYYYMMDD-HHMMSS-SSS-error.log and Upgrade-YYYYMMDD-HHMMSS-SSS.log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds). An example for an upgrade error log is Upgrade-20090415-132126-374-error.log, and an example for an upgrade log is Upgrade-20090415-132126-374.log.
Note:
The upgrade log file includes the name of the content database being upgraded.
-
Attach the remaining databases
After you restore the first content database and verify the upgrade by reviewing the upgrade log file, you can continue by restoring and upgrading the next database or databases. You can attach multiple databases at the same time in separate Command Prompt windows to run multiple upgrades at one time. After you successfully restore and upgrade all the content databases, you can review the sites to make sure that they were upgraded correctly.
-
Verification: Verify upgrade for additional databases
After upgrading any additional databases, view the Upgrade Status page to monitor progress and verify that the upgrade process is complete. Review the log file to identify any other issues, and then review each upgraded site to find and address any issues with how the content is displayed. For more information, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010) and Manage visual upgrade (SharePoint Foundation 2010).
-
See Also
-
-
Perform post-upgrade steps (SharePoint Foundation 2010)
After you have performed an in-place upgrade or a database attach upgrade to Microsoft SharePoint Foundation 2010, you can verify your upgrade and follow the necessary configuration steps to get your environment ready for your users again.
In this section:
Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010)
Upgrade existing Windows SharePoint Services 3.0 Web applications that were configured to use forms-based authentication to work with SharePoint Foundation 2010.
Verify upgrade and review upgraded sites (SharePoint Foundation 2010)
Find out how to tell whether upgrade was completed successfully (both from the software standpoint and from a visual review of your sites) or any issues remain to address. If you must restart upgrade after a failure, you will find the steps to do so in this article.
Recovering after a failed upgrade (SharePoint Foundation 2010)
Follow these steps if the upgrade to Microsoft SharePoint Foundation 2010 has failed and you do not have time to continue to troubleshoot the issues or resume the upgrade process.
-
Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010)
The procedures in this article provide guidance to enable you to configure forms-based authentication for a Microsoft SharePoint Foundation 2010 claims-based Web application. Perform the steps in the following procedures to configure a forms-based Web application to use an LDAP provider.
Configure a forms-based Web application to use an LDAP provider by using Central Administration
Configure the LDAP Web.Config files
Configure a forms-based Web application to use an LDAP provider by using Windows PowerShell
-
Configure a forms-based Web application to use an LDAP provider by using Central Administration
Perform the steps in the following procedure to use Central Administration to configure forms-based authentication for a claims-based Web application.
To configure forms-based authentication for a claims-based Web application by using Central Administration
1. Verify that the user account that is performing this procedure is a site collection administrator.
2. In Central Administration, in the Application Management section, click Manage web applications.
3. In the Contribute group of the ribbon, click New.
4. In the Authentication section of the Create New Web Application dialog box, click Claims Based Authentication.
5. In the Claims Authentication Types section, select Enable Forms Based Authentication (FBA).
6. Type a membership provider name and a role manager name. In the example Web.Config file depicted in this article, the name of the membership provider is membership, and the name of the role manager is rolemanager.
7. Click OK to create the Web application.
-
Configure the LDAP Web.Config files
After you have successfully created the Web application (described in the preceding procedure), modify the following Web.Config files:
The Central Administration Web application Web.Config file
The Security Token Service Web.Config file
The forms-based authentication claims-based Web application Web.Config file
To configure the Central Administration Web.Config file
1. Start IIS Manager by typing INETMGR at a command prompt.
2. Go to the SharePoint Central Administration site in IIS.
3. Right-click SharePoint Central Administration and then click Explore.
4. Open the Web.Config file.
5. Find the <Configuration> <system.web> section and add the following entry:
<membership defaultProvider=”AspNetSqlMembershipProvider”>
<providers>
<add name=”membership”
type=”Microsoft.Office.Foundation.Security.LdapMembershipProvider, Microsoft.Office.Foundation, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
server=”yourserver.com”
port=”389″
useSSL=”false”
userDNAttribute=”distinguishedName”
userNameAttribute=”sAMAccountName”
userContainer=”OU=UserAccounts,DC=internal,DC=yourcompany,DC= distinguishedName (of your userContainer)”
userObjectClass=”person”
userFilter=”(ObjectClass=person)”
scope=”Subtree”
otherRequiredUserAttributes=”sn,givenname,cn” />
</providers>
</membership>
<roleManager enabled=”true” defaultProvider=”AspNetWindowsTokenRoleProvider” >
<providers>
<add name=”roleManager”
type=”Microsoft.Office.Foundation.Security.LdapRoleProvider, Microsoft.Office.Foundation, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
server=”yourserver.com”
port=”389″
useSSL=”false”
groupContainer=”DC=internal,DC=yourcompany,DC= distinguishedName (of your groupContainer)”
groupNameAttribute=”cn”
groupNameAlternateSearchAttribute=”samAccountName”
groupMemberAttribute=”member”
userNameAttribute=”sAMAccountName”
dnAttribute=”distinguishedName”
groupFilter=”((ObjectClass=group)”
userFilter=”((ObjectClass=person)”
scope=”Subtree” />
</providers>
</roleManager>
Important:
After you have added the preceding entry, save and close the Web.Config file.
To configure the Security Token Service Web.Config file
1. Start IIS Manager by typing INETMGR at a command prompt.
2. Go to the SharePoint Web Services site.
3. Go to the SecurityTokenServiceAppliction sub-site.
4. Right-click SecurityTokenServiceAppliction and then click Explore.
5. Open the Web.Config file.
6. Find the <Configuration> <system.web> section and add the following entry:
<membership>
<providers>
<add name=”membership”
type=”Microsoft.Office.Foundation.Security.LdapMembershipProvider, Microsoft.Office.Foundation, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
server=”yourserver.com”
port=”389″
useSSL=”false”
userDNAttribute=”distinguishedName”
userNameAttribute=”sAMAccountName”
userContainer=”OU=UserAccounts,DC=internal,DC=yourcompany,DC=com”
userObjectClass=”person”
userFilter=”(&(ObjectClass=person))”
scope=”Subtree”
otherRequiredUserAttributes=”sn,givenname,cn” />
</providers>
</membership>
<roleManager enabled=”true” >
<providers>
<add name=”rolemanager”
type=”Microsoft.Office.Foundation.Security.LdapRoleProvider, Microsoft.Office.Foundation, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
server=”yourserver.com”
port=”389″
useSSL=”false”
groupContainer=”DC=internal,DC=yourcompany,DC=com”
groupNameAttribute=”cn”
groupNameAlternateSearchAttribute=”samAccountName”
groupMemberAttribute=”member”
userNameAttribute=”sAMAccountName”
dnAttribute=”distinguishedName”
groupFilter=”(&(ObjectClass=group))”
userFilter=”(&(ObjectClass=person))”
scope=”Subtree” />
</providers>
</roleManager>
Important:
After you have added the preceding entry, save and close the Web.Config file.
To configure the forms-based authentication claims-based Web application Web.Config file
1. Start IIS Manager by typing INETMGR at a command prompt.
2. Go to the Claims Forms site.
3. Right-click Claims Forms and then click Explore.
4. Open the Web.Config file.
5. Find the <Configuration> <system.web> section.
6. Find the <membership defaultProvider=”i”> section and add the following entry:
<add name=”membership”
type=”Microsoft.Office.Foundation.Security.LdapMembershipProvider, Microsoft.Office.Foundation, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
server=”yourserver.com”
port=”389″
useSSL=”false”
userDNAttribute=”distinguishedName”
userNameAttribute=”sAMAccountName”
userContainer=”OU=UserAccounts,DC=internal, DC=yourcompany,DC=com”
userObjectClass=”person”
userFilter=”(&(ObjectClass=person))”
scope=”Subtree”
otherRequiredUserAttributes=”sn,givenname,cn” />
Find the <roleManager defaultProvider=”c” enabled=”true” cacheRolesInCookie=”false”> section and add the following entry:
<add name=”roleManager”
type=”Microsoft.Office.Foundation.Security.LdapRoleProvider, Microsoft.Office.Foundation, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
server=”yourserver.com”
port=”389″
useSSL=”false”
groupContainer=”DC=internal,DC=yourcompany,DC=com”
groupNameAttribute=”cn”
groupNameAlternateSearchAttribute=”samAccountName”
groupMemberAttribute=”member”
userNameAttribute=”sAMAccountName”
dnAttribute=”distinguishedName”
groupFilter=”(&(ObjectClass=group))”
userFilter=”(&(ObjectClass=person))”
scope=”Subtree” />
Important:
After you have added the preceding entry, save and close the Web.Config file.
Warning:
Do not overwrite any existing entries in this Web.Config file.
-
Configure a forms-based Web application to use an LDAP provider by using Windows PowerShell
Perform the steps in the following procedure to use Windows PowerShell to configure forms-based authentication for a claims-based Web application.
To configure a forms-based Web application to use an LDAP provider by using Windows PowerShell
1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. From the Windows PowerShell command prompt, type the following:
$ap = New-SPAuthenticationProvider -Name “ClaimsForms” -ASPNETMembershipProvider “membership” -ASPNETRoleProviderName “rolemanager”
$wa = New-SPWebApplication -Name “Claims Windows Web App” -ApplicationPool “Claims App Pool” -ApplicationPoolAccount “internal\appool”
-Url http://servername -Port 80 -AuthenticationProvider $ap
Note:
The value of the ApplicationPoolAccount parameter must be a managed account on the farm.
6. After you have successfully created an authentication provider and a Web application, modify the following Web.Config files by using the sample entries provided in the Configure the LDAP Web.Config files section of this article:
To configure the Central Administration Web.Config file
To configure the Security Token Service Web.Config file
To configure the forms-based authentication claims-based Web application Web.Config file
7. After you have modified the Web.Config files, create a SPClaimsPrincipal and a site collection, as shown in the following example:
$cp = New-SPClaimsPrincipal -Identity “membership:SiteOwner” -IdentityType FormsUser
$sp = New-SPSite http://servername:port -OwnerAlias $cp.Encode() -Template “STS#0”
For more information, see New-SPClaimsPrincipal (http://technet.microsoft.com/library/0831e64b-3ec0-4016-8128-639991530172(Office.14).aspx).
Note:
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.
-
See Also
Migrate from forms-based authentication to claims-based authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/3a725e05-9b73-48ff-a481-3ddd2b4091c6(Office.14).aspx)
-
-
Verify upgrade and review upgraded sites (SharePoint Foundation 2010)
After you have performed either an in-place upgrade or a database attach upgrade to Microsoft SharePoint Foundation 2010, you must verify that the content was successfully upgraded to the new version. You can verify the status of the upgrade (is it still in progress, or has it been completed successfully or with errors or failures?) and then also review the upgraded sites to see whether any issues remain for you to address. When you follow these steps as part of a trial upgrade, you can use them to identify customizations that have to be reworked before you attempt to upgrade your production environment. When you upgrade your production environment, it is even more critical that you know when the upgrade was completed, which sites have been upgraded successfully, and which sites require additional work before you allow users access to them again.
In some cases, you might have to restart upgrade to finish upgrading your sites. For more information about how to restart upgrade, see Resume upgrade (SharePoint Foundation 2010).
In this article:
-
Verify upgrade status
The upgrade process has several phases. For in-place upgrade, you run Setup.exe to install the new software, and then run the SharePoint Products Configuration Wizard to upgrade the configuration database and the admin content database, and then the SharePoint Central Administration Web site opens. At this point, the content upgrade process starts. There are different ways to check the status of the upgrade process during each of these phases: You can review log files for Setup.exe, for the SharePoint Products Configuration Wizard, and for the content upgrade. In SharePoint Central Administration, you can view the version number to make sure that it is correct for the version that you upgraded to. Also, you can use the Upgrade Status page in SharePoint Central Administration or the localupgradestatus operation in Stsadm to find out which sites have been — or are currently being — upgraded. If upgrade was not successfully completed, you can view the log files to find the issues, address them, and then restart the upgrade process.
-
Review the log files
To verify that upgrade has succeeded, you can review the following log and error files:
The Setup.exe log file for SharePoint Foundation 2010.
The Setup log file is stored in the temp directory for the user account that is running Setup (%USERTEMP% or %WINDIR%\Users\user account\AppData\Local\Temp). It is named SharePoint Foundation Setup(YYYYMMDD-HHMMSS-SSS).log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds).
The SharePoint Products Configuration Wizard (Psconfig.exe) log file.
The Psconfig.exe log files are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\14\LOGS. The logs are named in the following format: PSCDiagnostics_MM_DD_YYYY_HH_MM_SS_SSS_randomnumber.log, where MM_DD_YY is the date and HH_MM_SS_SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds), and the random number is used to differentiate between possible simultaneous attempts to run the Psconfig.exe program.
The upgrade log file and the upgrade error log file.
The upgrade log file and the upgrade error log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\14\LOGS. The logs are named in the following format: Upgrade-YYYYMMDD-HHMMSS-SSS.log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds). The upgrade error log file combines all errors and warnings into a shorter file and is named Upgrade-YYYYMMDD-HHMMSS-SSS-error.log.
To review the log files to find and troubleshoot issues, start at the top of the files. Errors or warnings may be repeated if they occur for several site collections in the environment, or if they block the upgrade process completely. For example, if you cannot connect to the configuration database, the upgrade process will try (and fail) several times and these attempts will be listed in the log file.
To review the log files
1. Verify that you have the following administrative credentials:
To view the log files, you must be a member of the local Administrators group on the server.
2. In Windows Explorer, change to the directory that contains the log file that you want to view.
3. Use a text editor to open the log file.
4. In the upgrade log file, search, or visually scan, for the following entry:
Upgrade session finished successfully!
If you find this entry, the installation was successful.
5. If you do not find the entries from the previous step in the upgrade log file, or if you are reviewing one of the other log files, you can identify specific issues that may have contributed to a failure by searching, or visually scanning, through the file for the following terms:
Search for ERROR in the log files to find any failures (such as failing components and faulty database connections).
Search for WARNING to find issues such as missing features or components.
To find issues, you may find it useful to use a log parser to run queries against the log files.
If you find blocking issues in the log file, you can resolve the issues and then restart upgrade to continue with the process.
-
Verify the version number
In addition to viewing the upgrade log file, you can verify that the upgrade was successful by using the SharePoint Central Administration Web site to view the version number on the Servers in Farm page.
To verify the version number on the Servers in Farm page
1. Verify that you have the following administrative credentials:
To use SharePoint Central Administration, you must be a member of the Farm Administrators group.
2. On the Central Administration Home page, under System Settings, click Manage servers in this farm.
3. Under Farm Information, next to Configuration database version, verify that the number starts with “14”.
-
Check upgrade status for sites
To find out which sites have been upgraded or are currently being upgraded, you can use either the Upgrade Status page in SharePoint Central Administration or the localupgradestatus operation in Stsadm.exe.
The Upgrade Status page lists the upgrade sessions and gives details about the state of each session — whether it succeeded or failed, and how many errors or warnings occurred for each server. The Upgrade Status page also includes information about the log and error files for the upgrade process and suggests remedies for issues that might have occurred.
To see which sites were missed or skipped during upgrade, you can use the localupgradestatus operation in Stsadm.exe. You must run the command on every front-end Web server in a server farm.
To view upgrade status in SharePoint Central Administration
1. Verify that you have the following administrative credentials:
To use SharePoint Central Administration, you must be a member of the Farm Administrators group.
2. On the Central Administration Home page, under Upgrade and Migration, click Check upgrade status.
To view upgrade status from the command line
1. Verify that you have the following administrative credentials:
To use Stsadm, you must be a member of the local Administrators group on the server.
2. Click Start, right-click Command Prompt, and then click Run as administrator.
3. In the Command Prompt window, navigate to the following directory:
%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin
4. Type the following command and press ENTER:
Stsadm -o localupgradestatus
For more information about the localupgradestatus operation, see Localupgradestatus: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc289007(Office.12).aspx).
-
-
Review upgraded sites
Review your upgraded sites to identify any issues that must be addressed before you run the upgrade process on your production environment. If you performed an in-place upgrade and chose to use Visual Upgrade, you can use the Visual Upgrade feature to preview the sites in the new user interface.
For more information about previewing sites using Visual Upgrade, see Manage visual upgrade (SharePoint Foundation 2010).
If you want to verify basic functionality, you can create a new site collection by using a representative set of lists, libraries, Web Parts, and so on. Review the new site to make sure that the common, basic elements of your sites are working.
If pages are not rendered, you can check the Site Settings page by going directly to the URL (http:// siteurl/_layouts/settings.aspx). If the Site Settings page works and the upgrade has succeeded, there might be issues with the master page or home page. If the Site Settings page does not work, go to the log file to see whether you can get more information about the problem.
Begin by validating high-impact or high-profile sites, and then move on to lower-priority sites. As part of the planning process, you should have identified which sites are high-impact and high-profile and require immediate attention, and which can wait a bit longer.
Use the following checklists to review your upgraded sites and look for issues.
-
Web Parts
The following table lists issues with Web Parts that can occur after upgrade and how to address them.
Tip:
To test your Web Parts quickly, you can build a new Web Part page that contains all of your custom Web Parts before you test your upgrade, and then review the page for any missing or broken Web Parts after the trial upgrade.
What to check
What to do if there is a problem
Do all the Web Parts from your original site appear in your upgraded site?
If a Web Part zone exists in a customized (unghosted) page, but not in the site definition, the Web Parts from that Web Part zone may have been moved into the bottom zone on the page during the upgrade.
Either in Edit Mode for the page in the browser or in Microsoft SharePoint Designer 2010, look for missing Web Parts in the bottom zone or other zones, or check to see whether the Web Parts have been closed. For more information about how to work with Web Parts and Web Part zones in SharePoint Designer 2010, see the SharePoint Designer Help system.
Are the Web Parts displayed correctly (in the correct zone, location, and size)?
Either in Edit Mode for the page in the browser or in SharePoint Designer 2010, drag the Web Part into the correct zone or modify the Web Part properties to correct any sizing or positioning problems.
Are there any extra or missing Web Parts?
Open the page either in Edit Mode for the page in the browser or in SharePoint Designer 2010. If you see extra Web Parts on your page, look for closed or inactive Web Parts on the original version of the page. Were the closed or inactive Web Parts opened by the upgrade process? If so, you can modify the Web Part properties to close these Web Parts.
If Web Parts are missing, look for errors in SharePoint Designer 2010 such as “Error Rendering Control” or “Missing Assembly.” These errors indicate that the Web Part was not installed or was configured incorrectly for the new environment and must be reinstalled or reconfigured.
Do the Web Parts work correctly?
Open the page either in Edit Mode for the page in the browser or in SharePoint Designer 2010, and look for errors that indicate that a component or service is missing. Make sure that any components or services that the Web Parts rely on exist in the upgraded site. Particularly for the database attach upgrade approach, you must make sure that you have installed all the components or services that you must have for your Web Parts, and that you have configured them correctly (for example, you have configured the Web.config Safe Controls list).
Update and redeploy any Web Parts that exist but no longer function correctly.
Tip:
If you have problems with a Web Part, append contents=1 to the end of the URL syntax (http:// siteurl/default.aspx?contents=1), and then press ENTER. This opens the Web Part Maintenance page where you can remove and repair the broken Web Part.
-
Large lists
By default, large list query throttling is applied after an upgrade to SharePoint Foundation 2010. If a list is very large, and users use a view or perform a query that exceeds the limit or throttling threshold, the view or query will not be permitted. Check any large lists in your environment and have the site owner or list owner address the issue. For example, they can create indexed columns with filtered views, organize items into folders, set an item limit on the page for a large view, or use an external list.
-
Styles and appearance
The following table lists common issues with the style and appearance of your Web site after upgrade and how to address them.
Tip:
Most of the issues in this section can be solved by correcting the links to an item.
What to check
What to do if there is a problem
Are all the images on your pages displayed correctly?
Verify or fix the links to the images.
Are the appropriate cascading style sheet colors and styles used in the appropriate locations?
Verify or fix the links to the cascading style sheet file. Verify the link on the master page.
Does the theme that you applied to your site still look the same?
Your site’s home page, or other pages on your site, may look different after the site is upgraded. You may have to re-create or revise a theme and reapply it.
Do you have any scripted controls that are not working?
Verify or fix the links to the controls.
Are your pages displayed correctly in Windows Internet Explorer 8?
Verify that any HTML on the page is in strict XHTML mode.
Are any script errors displayed on any pages?
Verify the scripts and links, and verify that any HTML is in strict XHTML mode.
-
Permissions
Do the appropriate people and groups still have the correct level of permissions to sites, pages, lists, and items?
You can use the Check Permissions button in the Permission Tools section of the ribbon to see who has permissions to which items in a site or subsite.
-
Customized (unghosted) pages
Customized (unghosted) pages are pages that have been edited and are now unique versions of the pages, instead of the default template pages. The following table lists issues with customized pages that can occur after upgrade and how to address them.
What to check
What to do if there is a problem
Are your customizations still in the correct locations?
Determine whether you have only one issue or a larger problem with the whole page.
If you added a brand new page to your original site (for example, if you replaced Default.aspx with a different file instad of changing the existing Default.aspx file), the new page has no association with the site definition. Therefore, it might not resemble the other pages on the upgraded site — nor can it be reset to resemble them. If you want your customized page to have the same look and feel as the other pages on your site, consider creating a brand-new page that is based on the site definition and then transferring your customizations to that new page.
Can you still access the editing controls on the pages?
If you customized the editing controls (for example, the Site Actions link or the Edit Page link), check whether they still appear. If they don’t appear, you can replace them with the editing controls of the new version by resetting the page to the default version.
Use the Reset to Template command in SharePoint Designer to reset the page to the default version (also known as reghosting). After you have restored the default page, you can then reapply your customizations in the browser by applying a different master page, or by reapplying the customizations in SharePoint Designer.
Are your customizations still appropriate in the new environment, or do you want to update to the new functionality and look?
If you want the new functionality and features, you must reset any customized pages to use the template. Resetting the page basically discards the customizations and attaches your page to the appropriate master page. Any customizations you want can then be transferred to the master page instead of being stored in individual pages.
Use the Reset to Template command in SharePoint Designer to reset the page to the default version (that is, reghost it). After you have restored the default page, you can then reapply your customizations in the browser by applying a different master page, or by reapplying the customizations in SharePoint Designer.
Are any pages still checked out?
If you check out a page to make changes, make sure that you check in the page again.
-
See Also
-
-
Manage visual upgrade (SharePoint Foundation 2010)
This article provides procedures related to the Visual Upgrade feature. When you upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, you can choose to use the Visual Upgrade feature to give site collection owners and site owners the opportunity to preserve the previous user interface temporarily. This allows them to update customizations to work in the new user interface. For a full description of Visual Upgrade and related choices, see Plan visual upgrade (SharePoint Foundation 2010).
In this article:
View status of current user interface
Revert sites to previous user interface
-
About using Visual Upgrade
When you upgrade, either by using in-place upgrade or by using the database attach upgrade method, you can choose to use Visual Upgrade.
During an in-place upgrade, you make the choice to use Visual Upgrade as a step in the SharePoint Products Configuration Wizard. The visual upgrade feature is not available in the SharePoint Products Configuration Wizard if you are performing an upgrade on a stand-alone server with built-in database. However, the Visual Upgrade feature is available in this case from the Psconfig command-line tool. You can then use the syntax: psconfig.exe -cmd upgrade [–preserveolduserexperience <true|false>].
During a database attach upgrade, the choice to update to the new user experience or stay in the old user experience is accomplished by using either:
The Updateuserexperience parameter of the Mount-SPContentDatabase Windows PowerShell cmdlet.
The preserveolduserexperience parameter of the addcontentdatabase Stsadm operation.
For additional information about using these parameters during an upgrade, see Attach databases and upgrade to SharePoint Foundation 2010.
-
View status of current user interface
You can view the current user interface status by generating a list of all Web sites in a site collection and their corresponding visual upgrade data. This is useful if you have set a time limit by which site owners must have prepared their sites for the new user interface and you want to monitor their progress.
The following procedure shows you how to view the current user interface status.
To view status of current user interface by using Windows PowerShell
1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command:
$sc = Get-SPSite http://machinename/sites/collectionname; $sc.GetVisualReport() | Format-Table
For more information, see Get-SPSite (http://technet.microsoft.com/library/f3422bf4-0f9b-4f22-94c8-2a0606a31b16(Office.14).aspx).
-
Revert sites to previous user interface
If a site collection owner or site owner finalizes the new user interface by mistake, or if they have a problem that they cannot solve, you can revert back to the previous user interface by using Windows PowerShell. This procedure shows you how to revert one or all sites in a site collection to the previous user interface.
To revert sites to the previous user interface by using Windows PowerShell
1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. To revert a specific site in a site collection to the previous UI, at the Windows PowerShell command prompt, type the following command:
Get-SPSite http://machinename/sites/V3UI | Get-SPWeb “webname” | Foreach{$_.UIVersionConfigurationEnabled=1;$_.UIVersion=3;$_.Update();}
To reverts all sites in a site collection to the previous user interface, at the Windows PowerShell command prompt, type the following command:
Get-SPSite http://machinename/sites/V3UI | Foreach{$_. UIVersionConfigurationEnabled=1;$_.UIVersion=3;$_.Update();}
For more information, see Get-SPSite (http://technet.microsoft.com/library/f3422bf4-0f9b-4f22-94c8-2a0606a31b16(Office.14).aspx).
-
Force an upgrade to the new user interface
If you want to forcibly apply the new user interface after an upgrade has taken place, you might first want to give site collection owners and site owners a specified time during which they can preview the new user interface and fix any issues they might have. When you force an upgrade to the new user interface, you can use a script or use the SharePoint Products Configuration Wizard during the initial upgrade. For information about upgrade and the SharePoint Products Configuration Wizard, see Run the SharePoint Products Configuration Wizard. The following procedure shows you how to programmatically upgrade all site collections and all sites to the new user interface.
To force through an upgrade to the new user interface by using Windows PowerShell
1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command:
$webapp = Get-SPWebApplication http://sitename
foreach ($s in $webapp.sites)
{$s.VisualUpgradeWebs() }
For more information, see Get-SPWebApplication (http://technet.microsoft.com/library/11d6521f-f99c-433e-9ab5-7cf9e953457a(Office.14).aspx)
To upgrade a single site collection to the new user interface, type the following commands at the Windows PowerShell command prompt:
$site = Get-SPSite http://server
$site.VisualUpgradeWebs()
To upgrade a single site to the new user interface, type the following commands at the Windows PowerShell command prompt:
$web = Get-SPWeb http://server/site
$web.UIVersion = 4
$web.UIVersionConfigurationEnabled = 0
$web.Update()
-
Site owner options for visual upgrade
The site owner can use the Site Setting user interface to toggle between the Use the previous user interface and Preview the updated user interface options. Once the site owner is satisfied with how the site looks, the new UI can be finalized by selecting the Update the user interface option.
The following table describes the different upgrade options that are available for the site owner to choose for their sites. The upgrade modes are available from the Site Settings page in the Title, Description, and Icon section.
Mode type
Description
Use the previous user interface
Site owners use this mode to have all their sites use the interface from Windows SharePoint Services 3.0.
Preview the updated user interface
Site owners use this mode to evaluate how their sites will look and function in the new interface. When this mode is chosen, features from the previous version interface will not be available.
Update the user interface
Site owners use this option when they are satisfied with the changes and are ready to switch to the new user interface. If needed, an administrator can restore the user interface to the previous version interface.
-
See Also
-
-
Using AAM URL redirection as part of the upgrade process (SharePoint Foundation 2010) (white paper)
This white paper describes the planning activities that you need to successfully deploy and use the alternate access mapping (AAM) URL redirection feature in Microsoft SharePoint Foundation 2010 to help mitigate downtime during a server computer or server farm upgrade. It also describes the procedures necessary to successfully complete the configuration of this feature by modifying existing Windows SharePoint Services 3.0 server computers.
Important:
The process described in this white paper is an advanced technique for avoiding downtime during upgrade. It should only be used if other techniques, such as read-only databases and upgrade in-place with detached databases, would cause an unacceptably long period of downtime for your users. Do not consider using this technique unless you know your upgrade process will take more than a long weekend. If your upgrade is not likely to take that long, you won’t save any time by performing the procedures in this paper. For more information about other approaches to upgrade, see Determine upgrade approach (SharePoint Foundation 2010).
Download this white paper as a Microsoft Word document (.doc). (http://go.microsoft.com/fwlink/?LinkId=168857)
Download this white paper as a PDF file. (http://go.microsoft.com/fwlink/?LinkId=168858)
Business continuity management for Microsoft SharePoint Foundation 2010
-
Business continuity management for Microsoft SharePoint Foundation 2010
Microsoft Corporation
Published: April 2011
Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com)
- Abstract
This book provides information about business continuity management, which consists of the business decisions, processes, and tools you put in place in advance to handle crises. Information includes features of Microsoft SharePoint Foundation 2010 that are likely to be part of your business continuity management strategy.
The content in this book is a copy of selected content in the SharePoint Foundation 2010 technical library (http://go.microsoft.com/fwlink/?LinkId=181463) as of the publication date. For the most current content, see the technical library on the Web.

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
© 2011 Microsoft Corporation. All rights reserved.
Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
Plan for business continuity management (SharePoint Foundation 2010) 1
Business continuity management capabilities 1
Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010) 5
Protecting content by using recycle bins 5
Protecting content by using versioning 7
Plan for backup and recovery (SharePoint Foundation 2010) 8
Define business requirements 8
Choose what to protect and recover in your environment 9
Plan for enhanced backup and recovery performance 15
Backup and recovery overview (SharePoint Foundation 2010) 17
Backup and recovery scenarios 17
Plan for availability (SharePoint Foundation 2010) 28
Choosing an availability strategy and level 30
Plan for disaster recovery (SharePoint Foundation 2010) 37
Choose a disaster recovery strategy 38
Planning for cold standby data centers 39
Planning for warm standby data centers 39
Planning for hot standby data centers 39
System requirements for disaster recovery 43
Backup (SharePoint Foundation 2010) 44
Back up all or part of a farm 44
Back up a farm (SharePoint Foundation 2010) 46
Considerations when backing up a farm 46
Use Windows PowerShell to back up a farm 47
Use Central Administration to back up a farm 48
Use SQL Server tools to back up a farm 49
Back up a farm configuration (SharePoint Foundation 2010) 51
Use Windows PowerShell to back up a farm configuration 52
Use Central Administration to back up a farm configuration 53
Back up a Web application (SharePoint Foundation 2010) 55
Considerations when backing up a Web application 55
Use Windows PowerShell to back up a Web application 56
Use Central Administration to back up a Web application 57
Use SQL Server tools to back up a Web application 58
Back up a service application (SharePoint Foundation 2010) 60
Use Windows PowerShell to back up a service application 61
Use Central Administration to back up a service application 62
Back up a site collection (SharePoint Foundation 2010) 64
Use Windows PowerShell to back up a site collection 64
Use Central Administration to back up a site collection 66
Back up customizations (SharePoint Foundation 2010) 67
Backing up solution packages 68
Backing up authored site elements 70
Backing up changes to the Web.config file 71
Backing up third-party products 71
Backing up changes made by direct editing 71
Backing up developed customizations that are not packaged as solutions 72
Back up a content database (SharePoint Foundation 2010) 73
Use Windows PowerShell to back up a content database 74
Use Central Administration to back up a content database 75
Use SQL Server tools to back up a content database 76
Back up databases to snapshots (SharePoint Foundation 2010) 77
Use SQL Server tools to back up a database to a snapshot 77
Export a site, list, or document library (SharePoint Foundation 2010) 79
Use Windows PowerShell to export a site, list, or document library 79
Use Central Administration to export a site, list, or document library 80
Back up or archive logs (SharePoint Foundation 2010) 82
[Essential] Back up transaction logs 82
[Recommended] Collect usage data 83
[Recommended] Archive diagnostic logs 83
Configuring permissions for backup and recovery (SharePoint Foundation 2010) 86
Permissions for the SPTimerV4 timer service and SQL Server account 86
Group memberships required to run backup and restore operations in Central Administration 86
Setting permissions for running backup and restore operations by using Windows PowerShell 87
Configuring permissions for backup and recovery (SharePoint Server 2010) 89
Permissions for the SPTimerV4 timer service and SQL Server account 89
Group memberships required to run backup and restore operations in Central Administration 89
Setting permissions for running backup and restore operations by using Windows PowerShell 90
Recovery (SharePoint Foundation 2010) 92
Recover all or part of a farm 92
Restore a farm (SharePoint Foundation 2010) 94
Considerations when recovering a farm 94
Use Windows PowerShell to restore a farm 96
Use Central Administration to restore a farm 97
Use SQL Server tools to restore a farm 98
Restore a farm configuration (SharePoint Foundation 2010) 101
Use Windows PowerShell to restore a farm’s configuration 101
Use Central Administration to restore a farm’s configuration 102
Use SQL Server to restore a farm’s configuration 103
Document farm configuration settings (SharePoint Foundation 2010) 104
Copy configuration settings from one farm to another (SharePoint Foundation 2010) 110
Back up and recover a farm without content databases to copy configuration settings 111
Back up and recover configuration settings only 112
Create a scripted deployment to copy configuration settings 112
Restore a Web application (SharePoint Foundation 2010) 113
Considerations when restoring a Web application 113
Use Windows PowerShell to restore a Web application 113
Use Central Administration to restore a Web application 114
Use SQL Server tools to restore databases associated with a Web application 115
Additional steps to restore a Web application that uses forms-based authentication 116
Restore a service application (SharePoint Foundation 2010) 118
Use Windows PowerShell to restore a service application 119
Use Central Administration to restore a service application 120
Use SQL Server tools to restore the databases for a service application 121
Restore a site collection (SharePoint Foundation 2010) 122
Use Windows PowerShell to restore a site collection 122
Restore customizations (SharePoint Foundation 2010) 124
Restoring solution packages 124
Restoring authored site elements 126
Restoring changes to the Web.config file 127
Recovering changes made by direct editing 127
Restoring developed customizations that are not packaged as solutions 128
Restore a content database (SharePoint Foundation 2010) 129
Use Windows PowerShell to restore a content database 129
Use Central Administration to restore a content database 130
Use SQL Server tools to restore a content database 131
Attach and restore a read-only content database (SharePoint Foundation 2010) 133
Use Windows PowerShell to attach and restore a read-only content database 133
Import a list or document library (SharePoint Foundation 2010) 135
Import a site, list or document library 135
Availability configuration (SharePoint Foundation 2010) 137
Configure availability by using SQL Server clustering (SharePoint Foundation 2010) 138
Configure availability by using SQL Server database mirroring (SharePoint Foundation 2010) 139
Configure high-availability database mirroring 143
Configure SharePoint 2010 Products to be aware of mirrored databases 143
User experience during a failover 144
Monitoring and troubleshooting mirroring 144
Sample script for configuring SQL Server mirroring (SharePoint Foundation 2010) 145
Configure database mirroring with certificates and full recovery 145
Transfer permissions to the mirror server 152
Removing mirroring from a server 152
- Abstract
-
Getting help
Every effort has been made to ensure the accuracy of this book. This content is also available online in the Office System TechNet Library, so if you run into problems you can check for updates at:
http://technet.microsoft.com/office
If you do not find your answer in our online content, you can send an e-mail message to the Microsoft Office System and Servers content team at:
itspdocs@microsoft.com
If your question is about Microsoft Office products, and not about the content of this book, please search the Microsoft Help and Support Center or the Microsoft Knowledge Base at:
http://support.microsoft.com
-
Plan for business continuity management (SharePoint Foundation 2010)
Published: May 12, 2010
Business continuity management consists of the business decisions, processes, and tools you put in place in advance to handle crises. A crisis might affect your business only, or be part of a local, regional, or national event.
Features of Microsoft SharePoint Foundation 2010 are likely to be part of your business continuity management strategy, but your overall plan should be much more comprehensive and include the following elements:
- Clearly documented procedures.
- Offsite storage of key business records.
- Clearly designated contacts.
- Ongoing staff training, including practices and drills.
- Offsite recovery mechanisms.
In this article:
-
Business continuity management capabilities
Microsoft SharePoint Foundation 2010 includes the following capabilities that support business continuity management.
-
Versioning Users can lose data by overwriting a document. With versioning, users can keep multiple versions of the same document in a document library. In the event of an unwanted change, an overwritten document, or document corruption, the previous version can easily be restored by the user. When versioning is enabled, users can recover their data themselves.
For more information, see Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010).
-
Recycle Bin SharePoint Foundation 2010 includes a two-stage Recycle Bin. Users who have the appropriate permissions can use the first-stage Recycle Bin to recover documents, list items, lists, and document libraries that have been deleted from a site. Site collection administrators can use the second-stage Recycle Bin, also called the Site Collection Recycle Bin, to recover items that have been deleted from the first-stage Recycle Bin. When the first-stage Recycle Bin is enabled, users can recover their data themselves.
For more information, see Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010).
- Backup and recovery You can use Windows PowerShell cmdlets or the SharePoint Central Administration Web site to back up and recover farms, databases, Web applications, and site collections. There are also many external and third-party tools that you can use to back up and recover data. For more information, see Plan for backup and recovery (SharePoint Foundation 2010).
-
Availability No single feature provides availability within a SharePoint Foundation 2010 environment. You can choose among many approaches to improve availability, including the following:
- Fault tolerance of components and the network.
-
Redundancy of server roles and servers within a farm.
For more information about availability, see Plan for availability (SharePoint Foundation 2010).
-
Disaster recovery No single feature provides disaster recovery within a SharePoint Foundation 2010 environment. You can choose among many approaches to improve availability when a data center goes offline, including the following:
- Offsite storage of backups, both within and outside your region.
- Shipping images of servers to offsite locations.
-
Running multiple data centers, but serving data only through one, keeping the others available on standby.
For more information about disaster recovery, see Plan for disaster recovery (SharePoint Foundation 2010).
-
-
Service level agreements
Business continuity management is a key area in which IT groups offer service level agreements (SLAs) to set expectations with customer groups. Many IT organizations offer various SLAs that are associated with different chargeback levels.
The following list describes common features of business continuity management SLAs:
-
Versioning
- Whether offered.
- Amount of space allocated.
-
Recycle Bins
- Whether offered.
- Amount of space allocated for the first-stage Recycle Bin and second-stage Recycle Bin.
- Length of time that items are held before they are permanently deleted in each Recycle Bin.
- Additional charges for recovering items that have been permanently deleted from the second-stage Recycle Bin.
-
Backup and recovery
Backup and recovery SLAs usually identify objects and services that can be backed up and recovered, and the recovery time objective, recovery point objective, and recovery level objective for each. The SLA may also identify the available backup window for each object. For more information about backup and recovery SLAs, see Plan for backup and recovery (SharePoint Foundation 2010).
- Recovery time objective (RTO) is the objective for the maximum time a data recovery process will take. It is determined by the amount of time the business can afford for the site or service to be unavailable.
- Recovery point objective (RPO) is the objective for the maximum amount of time between the last available backup and any potential failure point. It is determined by how much data the business can afford to lose in the event of a failure.
- Recovery level objective (RLO) is the objective that defines the granularity with which you must be able to recover data — whether you must be able to recover the entire farm, Web application, site collection, site, list or library, or item.
-
Availability
For each component within a farm that is covered by an availability plan, an availability SLA may identify availability as a percentage of uptime, often expressed as the number of nines — that is, the percentage of time that a given system is active and working. For example, a system with a 99.999 uptime percentage is said to have five nines of availability.

Note:When calculating availability, most organizations specifically exempt or add hours for planned maintenance activities.
For more information, see Plan for availability (SharePoint Foundation 2010).
-
Disaster recovery
For each component within a farm that is covered by a disaster recovery plan, an SLA may identify the recovery point objective and recovery time objective. Different recovery time objectives are often set for different circumstances, for example a local emergency versus a regional emergency.
For more information, see Plan for disaster recovery (SharePoint Foundation 2010).
-
-
Related content
-
Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010)
Published: May 12, 2010
Plan to use recycle bins and versioning in an environment to help users protect and recover their data. Recycle bins and versioning are key components of a business continuity strategy.
Recycle bins Users can use recycle bins to retrieve deleted objects. Microsoft SharePoint Foundation 2010 supports two stages of recycle bins, the first-stage Recycle Bin and the Site Collection — also called the second-stage — Recycle Bin. When Recycle Bins are enabled, users can restore items that are in them, including deleted files, documents, list items, lists, and document libraries.
Versioning Users can use versioning to help prevent data loss that is caused by overwriting a document. When a site owner turns on versioning in a document library or a list, the library or list keeps multiple copies of a document, item, or file. In the event of an unwanted change, an overwritten file, or document corruption, the previous version can be easily restored by the user.
In this article:
-
Protecting content by using recycle bins
SharePoint Foundation 2010 supports two stages of recycle bins, the first-stage Recycle Bin and the Site Collection, or second-stage, Recycle Bin. The recycle bins are enabled and configured at the Web application level. The recycle bins collect deleted documents and list items. When a list item is deleted, any attachments to the item are also deleted and can be restored from the Recycle Bin.
The Recycle Bins can contain multiple copies of a document that each have the same file name and source. These documents cannot be restored over an existing copy of a document. The Recycle Bins cannot be used to recover previous versions or accidental overwrites of documents — you must use versioning to enable this functionality.
The following table describes how an item is deleted and recovered from the first-stage Recycle Bin and the second-stage Recycle Bin.
When a user does this
The item is
The item can be restored by
Deletes an item
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 longer than the time limit configured for an item to be held in the Recycle Bin.
Users or site collection administrators
Deletes an item from the Recycle Bin
Held in the second-stage Recycle Bin
Site collection administrators
Turning off the Recycle Bin for a Web application empties all Recycle Bins and permanently deletes all items in them.
First-stage Recycle Bin
The first-stage Recycle Bin is located at the site level and is available to users who have Contribute, Design, or Full Control permissions on a site.When a user deletes an item from a Web site, the item is sent to the site’s first-stage Recycle Bin. Items located in the first-stage Recycle Bin count toward the site quota.Items remain in one of the first-stage Recycle Bins in the site until a specified time period has been reached (the default setting is 30 days).
When an item is deleted from the Recycle Bin, the item is sent to the second-stage Recycle Bin.

Note:The time limit for the Recycle Bins applies to the total time after the item was first deleted — not the time spent in either Recycle Bin stage.
Second stage (Site Collection) Recycle Bin
The second-stage Recycle Bin is located at the site collection administrator level. The second-stage Recycle Bin is organized into two views: objects in the first-stage Recycle Bins of all sites in the site collection, and objects in the second-stage Recycle Bin. When an item is deleted from the first-stage Recycle Bin, it can be recovered only by a site collection administrator from the second-stage Recycle Bin.
Items remain in the second-stage Recycle Bin until a specified time period has been reached (the default setting is 30 days) or until the second-stage Recycle Bin reaches its size limit, at which time the oldest items are deleted. The time limit for the Recycle Bins applies to the total time after the item was initially deleted — not the time spent in either Recycle Bin stage.
When a second-stage Recycle Bin is enabled for a Web application, we recommend that you designate how much disk space is available to the second-stage Recycle Bin as a percentage of the quota allotted to the Web application. Items stored in the second-stage Recycle Bin do not count toward the site quota; however, the size that is specified for the second-stage Recycle Bin increases the total size of the site and the content database that hosts it. If no site quota has been set, there is no limit on the size of the second-stage Recycle Bin.
For example, if you have allotted 100 megabytes (MB) of space for the Web application, allotting a 50 percent quota for the second-stage Recycle Bin allots 50 MB for the second-stage Recycle Bin and 150 MB for the Web application as a whole. You can allot up to 100 percent for the second-stage Recycle Bin quota.
For more information about setting quotas, see
- Plan for site maintenance and management (SharePoint Foundation 2010)
- Create quota templates (SharePoint Foundation 2010)
For more information about how users can use the Recycle Bin in SharePoint Foundation 2010, see View, restore, or delete items in the Recycle Bin (http://go.microsoft.com/fwlink/?LinkId=90917&clcid=0x409)
For information about configuring the Recycle Bins, see Configure the Recycle Bin (SharePoint Foundation 2010).
-
Protecting content by using versioning
Versioning addresses the issue of losing data by overwriting a document. It allows the document library to keep multiple copies of the same document. In the event of an unwanted change, an overwrite, or a document corruption, the previous version can easily be restored by the user. Versioning can be enabled at the library or list level. Items and files can be versioned.
Before configuring versioning, be sure to read Plan for site maintenance and management (SharePoint Foundation 2010) .
For more information about configuring versioning, see Enable and configure versioning (SharePoint Foundation 2010) .
Administrators must closely manage versioning, because if sites have many versions of files and documents, the sites can become quite large. If you do not restrict the size of sites, your sites can surpass your storage capacity. Farm administrators can manage this issue by establishing service level agreements with site owners and by setting size quotas on sites. For more information about managing versioning, see Manage versioning by using quotas (SharePoint Foundation 2010).
-
Plan for backup and recovery (SharePoint Foundation 2010)
Updated: July 8, 2010
This article describes the stages involved in planning for backup and recovery, which include determining backup and recovery strategies for a Microsoft SharePoint Foundation environment and deciding which tools to use. The stages do not need to be done in the order listed, and the process may be iterative.
When you plan for how you will use backup and recovery for disaster recovery, consider common events, failures, and errors; local emergencies; and regional emergencies.
For detailed information about Microsoft SharePoint Foundation backup and recovery, see Backup and recovery overview (SharePoint Foundation 2010).
In this article:
-
Define business requirements
To define business requirements, determine the following for each farm and service in the environment:
- Recovery point objective (RPO) is the objective for the maximum amount of time between the last available backup and any potential failure point. It is determined by the amount of data that the business can afford to lose in the event of a failure.
- Recovery time objective (RTO) is the objective for the maximum time a data recovery process will take. It is determined by the amount of time the business can afford for the site or service to be unavailable.
- Recovery level objective (RLO) is the objective that defines the granularity with which you must be able to recover data — whether you must be able to recover the entire farm, Web application, site collection, site, list or library, or item.
Shorter RPO and RTO, and greater granularity of RLO, all tend to cost more.
A worksheet to help you plan your strategies for backup and recovery for your SharePoint Foundation 2010 environment can be downloaded from SharePoint 2010 Products backup and recovery planning workbook (http://go.microsoft.com/fwlink/?LinkID=184385).
-
Choose what to protect and recover in your environment
Your business requirements will help you determine which components of the environment you need to protect, and the granularity with which you need to be able to recover them.
The following table lists components of a SharePoint environment that you might decide to protect, and the tools that can be used to back up and recover each component.
Component
SharePoint backup
Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2
System Center Data Protection Manager (DPM) 2010
File system backup
Farm
Yes
Yes6
Service applications
Yes
Web application
Yes
Content databases
Yes
Yes
Yes
Site collection
Yes1, 2
Yes1, 2
Yes1, 2
Site
Yes2
Yes2
Yes
Document library or list
Yes2
Yes2
Yes
List item or document
Yes
Content stored in remote BLOB stores
Yes3
Yes3
Yes3
Customizations deployed as solution packages
Yes7
Yes7
Yes6, 7
Changes to Web.config made by using Central Administration or an API
Yes
Yes
Yes4
Configuration settings (SharePoint)
Yes2, 8
Yes2, 8
Yes 2, 9
Customizations not deployed as solution packages
Yes. Files can be recovered if protected as files.4, 5
Yes
Changes to Web.config not made by using Central administration or an API
Yes4
Yes
IIS configurations not set through SharePoint
Yes5
Yes
SQL Server Reporting Services databases
Yes
Yes
1. Farm-level and database-level backup and restore can be used for site collection recovery if a single site collection is stored in a database.
2. Farm-level and database-level backups can be used with SharePoint Foundation unattached database recovery to restore site collections, sites, lists, and configurations.
3. Content stored in remote BLOB stores is backed up and restored with other content, as long as the Remote BLOB Storage (RBS) provider in use has this capability.
4. Changes to Web.config can be backed up by using file system backup from DPM 2010.
5. IIS configurations can be recovered by using a bare metal backup from DPM 2010.
6. DPM 2010 can recover this item by using a combination of a bare metal backup and SharePoint Foundation backup. It cannot be backed up and recovered as an object.
7. Fully-trusted solution packages are stored in the configuration database, and sandboxed solutions are stored in content databases. They can be recovered as part of farm or content database recovery.
8. Configuration settings can be recovered from farm-level backups. For more information, see Restore a farm (SharePoint Foundation 2010).
9. The Central Administration content database and the configuration database for a SharePoint Foundation 2010 farm can be recovered but only as part of a full-farm recovery to the same farm, with the same computers.

Note:You can register SharePoint Foundation 2010 with Windows Server Backup by using the stsadm.exe -o -registerwsswriter operation to configure the Volume Shadow Copy Service (VSS) writer for SharePoint Foundation. Windows Server Backup then includes SharePoint Foundation 2010 in server-wide backups. When you restore from a Windows Server backup, you can select Microsoft SharePoint Foundation (no matter which version of SharePoint 2010 Products is installed), and all components reported by the VSS writer forSharePoint Foundation 2010 on that server at the time of the backup will be restored.
Windows Server Backup is recommended only for use with for single-server deployments.
Choose what to recover from within SharePoint content databases
From within a content database, you can recover site collections, sites, lists and libraries.
Backup and recovery tools provide different levels of recovery for content within a content database. Recovering an object from within a content database is always more complex than recovering an entire content database.
Protecting customizations
Customizations to SharePoint sites can include:
- Master pages, page layouts and cascading style sheets. These objects are stored in the content database for a Web application.
- Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions.
- Third-party solutions and their associated binary files and registry keys, such as IFilters.
- Changes to standard XML files.
- Custom site definitions (Webtemp.xml).
- Changes to the Web.config file.
How customizations are deployed, and how changes are made to the Web.config file, have a significant effect on which tools can be used to back up and recover customizations. To provide the greatest opportunity for recovery, we recommend that you deploy customizations by using solution packages and make changes to the Web.config file by using Central Administration or the SharePoint APIs and object model.
Protecting workflows
Workflows are a special case of customizations that you can back up and recover. Make sure that your backup and recovery plan addresses any of the following scenarios that apply to your environment:
- Declarative workflows, such as those created in Microsoft SharePoint Designer 2010, are stored in the content database for the site collection to which they are they are deployed. Backing up the content database protects these workflows.
- Custom declarative workflow actions have components in the following three locations:
- The Visual Studio assemblies for the Activities are stored in the global assembly catalog (GAC).
- The XML definition files (.ACTIONS files) are stored in the 14\TEMPLATE\{LCID}\Workflow directory.
-
An XML entry to mark the activity as an authorized type is stored in the Web.config file for the Web applications in which it is used.
If your farm workflows use custom actions, you should use a file backup system to protect these files and XML entries. Similar to SharePoint Foundation features such as Web parts and event receivers, these files should be reapplied to the farm as needed after recovery.
- Workflows that depend on custom code, such as those that are created by using Visual Studio, are stored in two locations. The Visual Studio assemblies for the workflow are stored in the global assembly catalog (GAC), and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Foundation features such as Web parts and event receivers. If the workflow was installed as part of a solution package, backing up the content database protects these workflows.
- If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must back up both site collections to protect the workflow. This includes workflows that write to a history list or other custom list in another site collection. Performing a farm backup is sufficient to back up all site collections in the farm and all workflows that are associated with them.
- Workflows that are not yet deployed must be backed up and restored separately like any other data file. When you are developing a new workflow but have not yet deployed it to the SharePoint Foundation farm, make sure that you back up the folder where you store your workflow project files by using Windows Backup or another file system backup application.
Protecting service applications
Service applications in a SharePoint Foundation environment can be made up of both service settings and one or more databases, or just service settings. You cannot restore a complete service application by restoring the database only; however, you can restore the databases for a service application and then reprovision the service application. For more information, see Restore a service application (SharePoint Foundation 2010).
Protecting SQL Server Reporting Services databases
SharePoint Foundation backup and recovery does not include SQL Server Reporting Services databases. You must use SQL Server tools. For more information, see Backup and Restore Operations for a Reporting Services Installation (http://go.microsoft.com/fwlink/?LinkId=186642).
-
Choose tools
To choose the right tools for backup and recovery, you need to determine whether you can meet the continuity requirements you have set for your business within your budget for time and resources.
Key factors to consider when choosing tools include:
- Speed of backup: Can the tool perform within the maintenance window for your databases? You should test any backup system to ensure that it meets your needs on your hardware.
- Completeness of recovery.
- Granularity of objects that can be recovered.
- Backup type supported (full, differential, or incremental).
- Complexity of managing the tool.
The following table compares the type of backup and size of farm that can be backed up in a six-hour window for backup and recovery tools available from Microsoft.
Tool
Backup type
Size of backup completed in six hours1
SharePoint farm backup and recovery
Full, differential
600 GB
SQL Server
Full, differential
600 GB
System Center Data Protection Manager
Incremental
Terabytes
1Backup size was determined by backing up a system that totals the specified size on the test hardware listed in the following section.

Note:The SharePoint Foundation and SQL Server backups were performed with backup compression turned on.
Test hardware
The following table lists the hardware used in the tests that determined the size of backup that could be completed in a six-hour window.
Component
Description
Processor
64-bit dual processor, 3 GHz
RAM
8 GB
Disk
2 terabyte NTFS file system-formatted partition
Network
100 megabits per second (Mbps) or faster connection between client computers and server
Network share
Network share with 1.25 terabytes free space

Note:The upper size limit for performing SharePoint Foundation 2010 site collection backups is 85 GB.
For detailed information about the backup and recovery systems that can be used with Microsoft SharePoint Foundation, see the following resources:
-
Determine strategies
Based on your business requirements, recovery needs, and the tools you have chosen, determine and document the backup and recovery strategies for your environment.
It is not uncommon for IT departments that support SharePoint Foundation environments to decide to use more than one tool to protect the environment, as they determine the strategies that they will use.
For example, in an environment with databases that are managed by DBAs, the strategies in the following list might be employed:
-
All databases are backed up by SQL Server. The backup interval that is set for each database is based on the following:
- The business impact of the content or service.
- The standard rate of change for the database.
- The effect on performance that the backup has on the environment.
-
Small, rapidly changing, very high-business-impact content databases are additionally protected by SQL Server database snapshots that are stored on a separate physical disk. Only one snapshot is stored per database, and snapshots are discarded regularly, so that the effect on performance is minimized. The snapshot interval that is set for each database is based on the following:
- The business impact of the content or service.
- The standard rate of change for the database.
- The effect on performance that the snapshot has on the environment.
-
The amount of space required to store the snapshot.
Recovering from a snapshot is faster than standard recovery because a snapshot, along with its underlying database, can be treated by SharePoint Foundation as an unattached database. However, the process of creating snapshots can decrease the performance of the underlying database. We recommend that the effect that snapshots have on the performance of your system be tested before they are implemented, and that snapshots be discarded regularly to reduce the space required.

Note:If you are using RBS, and the RBS provider that you are using does not support snapshots, you cannot use snapshots for backup. For example, the SQL FILESTREAM provider does not support snapshots.
-
SharePoint Foundation backup is used to protect service applications. The backup interval is based on the following:
- The business impact of the service.
- The standard rate of change for the database.
- The effect on performance that the backup has on the database.
- All restore operations are performed through SharePoint Foundation. The choice of which restore system to use is determined by the type of backup that is available and the object being restored.
Other tools should be part of your business continuity strategy. Consider how you will use Recycle Bins and versioning in site collections throughout the environment. For more information, see Plan for business continuity management (SharePoint Foundation 2010).
-
-
Plan for enhanced backup and recovery performance
As you plan your backup and recovery strategy, consider the following recommendations to help you decrease the effect of backup and recovery on system performance.
By design, most backup jobs consume as many I/O resources as they can to finish the job in the available time for maintenance; therefore, you might see disk queuing and you might see that all I/O requests come back more slowly than usual. This is typical and should not be considered a problem.
Follow recommendations for configuring SQL Server and storage
Follow the general recommendations for configuring SQL Server and storage for a SharePoint Foundation environment. For more information, see Plan for SQL Server, storage and BLOB configuration (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dc219657-46b7-49fe-aa57-03e229ac9bc0(Office.14).aspx).
Minimize latency between SQL Server and the backup location
In general, it is best to use a local disk, not a network drive, for backups. If you are backing up multiple servers, you may want to have a directly connected computer that both servers can write to. Network drives that have 1 millisecond or less latency between them and the computers that are running SQL Server will perform well. If your farm has multiple servers in it (including the computer that is running SQL Server), you must use UNC network paths for the SharePoint farm backup location.
Avoid processing conflicts
Do not run backup jobs during times in which users require access to the system.
To avoid I/O bottlenecks, perform the main backup to a separate disk, and only then copy to tape.
Consider staggering backups so that not all databases are backed up at the same time.
SharePoint Foundation backups use SQL Server backups. When using compression with your backups, be mindful not to overwhelm SQL Server. For example, some third-party backup tools compress data during backup, which can disrupt SQL Server performance. There are tools available to throttle the compression processes and control the effect on SQL Server.
Follow SQL Server backup and restore optimization recommendations
If you are running SQL Server 2008 Enterprise, we recommend that you use backup compression. For more information, see Backup Compression (SQL Server) (http://go.microsoft.com/fwlink/?LinkId=179525).
If you are using SQL Server backups, use a combination of full, differential, and transaction log backups for the full recovery model to minimize recovery time.
Differential database backups are usually faster to create than full database backups, and they reduce the amount of transaction log required to recover the database.
If you are using the full recovery model in SQL Server 2008, we recommend that you use the truncate option during backup to avoid maintenance issues.
For detailed recommendations about how to optimize SQL Server backup and restore performance, see Optimizing Backup and Restore Performance in SQL Server (http://go.microsoft.com/fwlink/?LinkId=126630).
Ensure sufficient write performance on the backup drive
Carefully consider whether to use redundant array of independent disks (RAID) on your disk backup device. For example, RAID 5 has low write performance, approximately the same speed as for a single disk. (This is because RAID 5 maintains parity information.) Using RAID 10 for a backup device may provide faster backups. For more information about how to use RAID with backups, see Configure RAID for maximum SQL Server I/O throughput (http://go.microsoft.com/fwlink/?LinkId=126632).
-
Related content
-
Backup and recovery overview (SharePoint Foundation 2010)
Updated: October 21, 2010
This article describes the backup architecture and recovery processes that are available in Microsoft SharePoint Foundation 2010, including farm and granular backup and recovery, and recovery from an unattached content database. Backup and recovery operations can be performed through the user interface or through Windows PowerShell cmdlets. Built-in backup and recovery tools may not meet all the needs of your organization.
In this article:
-
Backup and recovery scenarios
Backing up and recovering data supports many business scenarios, including the following:
- Recovering unintentionally deleted content that is not protected by the Recycle Bin or versioning.
- Moving data between installations as part of a hardware or software upgrade.
- Recovering from an unexpected failure.
-
Backup architecture
SharePoint Foundation 2010 provides two backup systems: farm and granular.
Farm backup architecture
The farm backup architecture in SharePoint Foundation 2010 starts a Microsoft SQL Server database backup of content and service application databases and also writes configuration content to files.
The following illustration shows the farm backup system.
Both full and differential backups are supported. Full backups create a new backup of the complete system. Differential backups create a backup of all the data that is stored in databases that has changed since the last full backup.
The farm backup system is organized hierarchically. The components in a farm that can be selected for backup include the following:
-
Farm The farm is the highest-level object. You can select from the following options when you perform a farm backup:
-
Content and configuration data (default)
The whole server farm is backed up. This includes settings from the configuration database.
-
Configuration only
Configuration database settings are backed up so that you can apply configurations across farms. For more information, see Configuration-only backup use and benefits later in this article.
-
-
Web application Within a Web application, you can select one or more of the content databases to back up.
A Web application backup includes the following:
- Application pool name and application pool account
- Authentication settings
- General Web application settings such as alerts and managed paths
- Internet Information Services (IIS) binding information, such as the protocol type, host header, and port number
- Changes to the Web.config file that have been made through the object model or Central Administration

Note:Changes to the Web.config file that have been made to support claims-based application that uses forms-based authentication are not included in backups, because those changes are made manually. For more information, see Considerations for using farm backups later in this article.
-
Sandboxed solutions
For recommendations about how to protect these settings, see Plan for backup and recovery (SharePoint Foundation 2010).

Important:Backups of service applications do not include the related proxy. To back up both the service application and the service application proxy, you must either back up the farm or perform two consecutive backups, selecting the service application in one backup, and selecting the associated service application proxy in the second backup.
Many service application databases cannot be backed up individually from SharePoint Foundation 2010. To back up service application databases only, you must use SQL Server backup.
- Proxies for service applications that are not shared.
- Shared Services Shared services require both a service application and a service application proxy to run. If you select the Shared Services node, all of the service applications and the related service application proxies on the farm will be backed up.

Note:The backup hierarchy enables you to select individual service applications and service application proxies to back up. However, when you select one or all service applications, or one or all proxies, the related objects are not backed up by default. To back up both parts of a specific service, you must either select the Shared Services node or perform two consecutive backups, selecting the service application in one backup, and selecting the associated service application proxy in the second backup.

Note:Some settings in the SharePoint Foundation environment are not included in a farm backup. They include the following settings that are stored on Web servers:
- Application pool account passwords
- HTTP compression settings
- Time-out settings
- Custom Internet Server Application Programming Interface (ISAPI) filters
- Computer domain membership
- Internet Protocol security (IPsec) settings
- Network Load Balancing settings
- Secure Sockets Layer (SSL) certificates
- Dedicated IP address settings
Configuration-only backup use and benefits
A configuration-only backup extracts and backs up the configuration settings from a configuration database. By using built-in tools, you can back up the configuration of any configuration database, whether it is currently attached to a farm or not. For detailed information about how to back up a configuration, see Back up a farm configuration (SharePoint Foundation 2010).
A configuration backup can be restored to the same — or any other — server farm. When a configuration is restored, it will overwrite any settings present in the farm that have values that are set in the configuration backup. If any settings present in the farm are not contained in the configuration backup, they will not be changed. For detailed information about how to restore a farm configuration, see Restore a farm configuration (SharePoint Foundation 2010).

Note:Web application and service application settings are not included in a configuration backup. You can use Windows PowerShell cmdlets to document and copy settings for service applications. For more information, see Document farm configuration settings (SharePoint Foundation 2010) and Copy configuration settings from one farm to another (SharePoint Foundation 2010).
Situations in which you might want to restore a configuration from one farm to another farm include the following:
- Replicating a standardized farm configuration to be used throughout an environment.
- Moving configurations from a development or test environment to a production environment.
- Moving configurations from a stand-alone installation to a farm environment.
- Configuring a farm to serve as part of a standby environment.
SharePoint Foundation stores the following kinds of settings in the configuration-only backup:
- Antivirus
- Information rights management (IRM)
- Outbound e-mail settings (only restored when you perform an overwrite).
- Customizations deployed as trusted solutions
- Diagnostic logging
Considerations for using farm backups
Consider the following before you use farm backups:
- There is no built-in scheduling system for backups. To schedule a backup, we recommend that you create a backup script by using Windows PowerShell, and then use Windows Task Scheduler to run the backup script on a regular basis.
- We do not recommend that you use IIS metabase backup to protect IIS settings. Instead, document all IIS configurations for each Web server by using a tool that provides the configuration monitoring you want, such asMicrosoft System Center Configuration Manager 2010.
-
SharePoint Foundation 2010 backup and recovery can be run together with SQL Server Enterprise features such as backup compression and transparent data encryption.
If you are running SQL Server Enterprise, we strongly recommend that you use backup compression. For more information about backup compression, see Backup Compression (SQL Server) http://go.microsoft.com/fwlink/?LinkID=129381).
If you decide to run databases with transparent data encryption, you must manually back up the key and restore the key — SharePoint Foundation 2010 backup and restore will not remind you about the key.
For more information about transparent data encryption, see Understanding Transparent Data Encryption (TDE) (http://go.microsoft.com/fwlink/?LinkID=129384).
- If a content database is set to use the SQL FILESTREAM remote BLOB storage (RBS) provider, the RBS provider must be installed both on the database server that is being backed up and on the database server that is being recovered to.
-
SharePoint Foundation 2010 backup does not protect:
- Changes to the Web.config file on Web servers that are not made through Central Administration or the object model.
- Customizations to a site that are not deployed as part of a trusted or sandboxed solution.
-
If you are sharing service applications across farms, be aware that trust certificates that have been exchanged are not included in farm backups. You must back up the certificate store separately or keep the certificates in a separate location. When you restore a farm that shares a service application, you must import and redeploy the certificates and then re-establish any inter-farm trusts.
For more information, see Exchange trust certificates between farms (SharePoint Foundation 2010) (http://technet.microsoft.com/library/679d334b-913d-49b3-b086-66a60093b261(Office.14).aspx).
- When you restore a farm or Web application that is configured to use any kind of claims-based authentication, duplicate or additional providers may appear to be enabled. If duplicates appear, you must manually save each Web application zone to remove them.
-
Additional steps are required when you restore a farm that contains a Web application that is configured to use forms-based authentication. You must re-register the membership and role providers in the Web.config file, and then redeploy the providers. You must perform these steps whether you are restoring at the Web application level or at the farm level.
For more information, see Back up a Web application (SharePoint Foundation 2010), Plan authentication methods (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b6bc8fec-c11c-4ed7-a78d-3ad61c7ef6c0(Office.14).aspx) and Configure claims authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ef8c3024-26de-4d06-9204-3c6bbb95fb14(Office.14).aspx).
Granular backup and export architecture
The granular backup and export architecture uses Transact-SQL queries and export calls. Granular backup and export is a more read-intensive and processing-intensive operation than farm backup.
From the granular backup system, a user can back up a site collection, or export a site or list.

Note:Workflows are not included in exports of sites or lists.
If you are running SQL Server Enterprise, the granular backup system can optionally use SQL Server database snapshots to ensure that data remains consistent while the backup or export is in progress. When a snapshot is requested, a SQL Server database snapshot of the appropriate content database is taken, SharePoint Foundation uses it to create the backup or export package, and then the snapshot is deleted. Database snapshots are linked to the source database where they originated. If the source database goes offline for any reason, the snapshot will be unavailable. For more information about database snapshots, see Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=166158).
Benefits of backing up a site collection by using a snapshot include the following:
- The snapshot ensures that the data that is being read remains consistent while the operation is being performed.
- Users can continue to interact with the site collection while it is being backed up from the database snapshot. This includes adding, editing, and deleting content. However, the changes that users make to the live site will not be included in the site collection backup because the backup is based on the database snapshot.
However, database snapshots can adversely affect performance. For more information about database snapshots and performance, see Limitations and Requirements of Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=166159).
You can use granular backup and export for content that is stored in a database that is configured to use the SQL FILESTREAM RBS provider.

Note:If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots.

Note:We do not recommend that you use SharePoint Foundation 2010 site collection backup for site collections larger than 85 GB.
The following illustration shows the granular backup and export system.
-
-
Recovery processes
SharePoint Foundation 2010 supports the following primary, built-in recovery options:
- Restore from a farm backup that was created by using built-in tools, or restore from the backup of a component taken by using the farm backup system.
- Restore from a site collection backup.
- Connect to a content database by using the unattached content database feature, back up or export data from it, and then restore or import the data.
Restoring from a farm backup
Items that can be recovered from a farm backup include the following:
-
Farm
-
Content and configuration data (default)
The whole server farm is restored. This includes settings from the configuration database, and trusted solution packages.
-
Configuration only
Only the configuration data is restored. This overwrites any settings in the farm that have values that are set within the configuration-only backup.
-
-
Web applications
Restores Web applications.
-
Service applications
Restores service applications. Service application recovery can be complex because SharePoint Foundation 2010 cannot fully reconfigure service application proxies during the restore process. Service application proxies are restored, but are not put in proxy groups. Therefore, they are not associated with any Web applications. For specific information about the operations involved in restoring specific service applications, see Restore a service application (SharePoint Foundation 2010).
-
Content databases
When content databases are restored, the sandboxed solutions associated with the related site collections are also restored.
Restoring as new versus restoring as overwrite
By default, SharePoint Foundation 2010 recovery restores any object as a new instance of the object, instead of overwriting any existing instances with the same name.
When you restore a farm or object as new, the following objects will not work without adjustments, because all GUIDs for objects are assigned new values:
-
Farm. When you restore a farm as new, you must do the following:
- Re-create alternate access mapping settings. SharePoint Foundation 2010 recovery only restores the Default zone of the Web application.
- Re-associate service application proxies with proxy groups because service application proxies are not assigned to proxy groups when restored. All Web applications will be associated with the default proxy group. You must associate Web applications with other proxy groups if you want to do that.
-
Web application.
- If the Web application name and URL that you provide match a Web application name and URL that already exist in the farm, SharePoint Foundation 2010 recovery combines them.
- If you do not want to combine Web applications, you must rename the Web application when you restore it as new.
- When you restore a Web application as new in the same environment but do not combine Web applications, many other parameters and objects must also be changed. For example, you may have to provide different database file paths and different database names.
-
Service applications and service application proxies
- If you recover a service application and also recover the related service application proxy, you must associate the service application proxy with a proxy group.
- If you recover a service application and do not also recover the related service application proxy, you must re-create the service application proxy.

Note:You cannot restore a service application as new in the same farm. You can restore a service application as new in another farm.
When you restore an object and overwrite the existing object, no changes are necessary.
Restoring from a site collection backup
Only site collections can be recovered from a site collection backup.
Recovering from an unattached content database
SharePoint Foundation 2010 provides the ability to connect to, and back up from, a content database that is attached to an instance of SQL Server but is not associated with a local SharePoint Web application. Unattached databases that you can connect to include read-only content databases that have been restored from any supported backup technology and SQL Server database snapshots of content databases.
Recovery is the following two-stage process:
- Back up or export the object from the unattached content database.
- Restore or import the output of the prior step into SharePoint Foundation 2010.
The following items can be backed up or exported from an unattached database by using granular backup and export, and then restored:
-
Site collection
Back up by using site collection backup, and then recover by using a site collection restore.
-
Site
Export, and then import.
-
Lists and libraries
Export, and then import.
You can use import to recover content that you backed up from a database configured to use the SQL FILESTREAM RBS provider. The recovered content will be stored by SharePoint Foundation 2010 using the currently defined storage provider for that content database — that is, if the content database is not set to use RBS, the data will be stored in the content database; if the content database is set to use RBS, the data will be stored in RBS.
-
Related content
-
Plan for availability (SharePoint Foundation 2010)
Updated: June 17, 2010
This article describes key decisions in choosing availability strategies for a Microsoft SharePoint Foundation 2010 environment.
As you carefully review your availability requirements, be aware that the higher the level of availability and the more systems that you protect, the more complex and costly your availability solution is likely to be.
Not all solutions in an organization are likely to require the same level of availability. You can offer different levels of availability for different sites, different services, or different farms.
In this article:
-
Availability overview
Availability is the degree to which a SharePoint Foundation environment is perceived by users to be available. An available system is a system that is resilient — that is, incidents that affect service occur infrequently, and timely and effective action is taken when they do occur.
Availability is part of business continuity management (BCM), and is related to backup and recovery and disaster recovery. For more information about these related processes, see Plan for backup and recovery (SharePoint Foundation 2010) and Plan for disaster recovery (SharePoint Foundation 2010).

Note:When calculating availability, most organizations specifically exempt or add hours for planned maintenance activities.
One of the most common measures of availability is percentage of uptime expressed as number of nines — that is, the percentage of time that a given system is active and working. For example, a system with a 99.999 uptime percentage is said to have five nines of availability.
The following table correlates uptime percentage with calendar time equivalents.
Acceptable uptime percentage
Downtime per day
Downtime per month
Downtime per year
95
72.00 minutes
36 hours
18.26 days
99 (two nines)
14.40 minutes
7 hours
3.65 days
99.9 (three nines)
86.40 seconds
43 minutes
8.77 hours
99.99 (four nines)
8.64 seconds
4 minutes
52.60 minutes
99.999 (five nines)
0.86 seconds
26 seconds
5.26 minutes
If you can make an educated guess about the number of total hours downtime you are likely to have per year, you can use the following formulas to calculate the uptime percentage for a year, a month, or a week:
% uptime/year = 100 – (8760 – number of total hours downtime per year)/8760
% uptime/month = 100 – ((24 × number of days in the month) – number of total hours downtime in that calendar month)/(24 × number of days in the month)
% uptime/week = 100 – (168 – number of total hours downtime in that week)/168
Costs of availability
Availability is one of the more expensive requirements for a system. The higher the level of availability and the more systems that you protect, the more complex and costly an availability solution is likely to be. When you invest in availability, costs include the following:
- Additional hardware and software, which can increase the complexity of interactions among software applications and settings.
- Additional operational complexity.
The costs of improving availability should be evaluated in conjunction with your business needs — not all solutions in an organization are likely to require the same level of availability. You can offer different levels of availability for different sites, different services, or different farms.
Availability is a key area in which information technology (IT) groups offer service level agreements (SLAs) to set expectations with customer groups. Many IT organizations offer various SLAs that are associated with different chargeback levels.
Determining availability requirements
To gauge your organization’s tolerance of downtime for a site, service, or farm, answer the following questions:
- If the site, service, or farm becomes unavailable, will employees be unable to perform their expected job responsibilities?
- If the site, service, or farm becomes unavailable, will business and customer transactions be stopped, leading to loss of business and customers?
If you answered yes to either of these questions, you should invest in an availability solution.
-
Choosing an availability strategy and level
You can choose among many approaches to improve availability in a SharePoint Foundation environment, including the following:
- Improve the fault tolerance of server hardware components.
- Increase the redundancy of server roles within a farm.
Hardware component fault tolerance
Hardware component fault tolerance is the redundancy of hardware components and infrastructure systems such as power supplies at the server level. When planning for hardware component fault tolerance, consider the following:
- Complete redundancy of every component within a server may be impossible or impractical. Use additional servers for additional redundancy.
- Ensure that servers have multiple power supplies connected to different power sources for maximum redundancy.
In any system, we recommend that you work with hardware vendors to obtain fault-tolerant hardware that is appropriate for the system, including redundant array of independent disks (RAID) arrays.
Redundancy within a farm
SharePoint Foundation 2010 supports running server roles on redundant computers (that is, scaling out) within a farm to increase capacity and to provide basic availability.
The capacity that you require determines both the number of servers and the size of the servers in a farm. After you have met your base capacity requirements, you may want to add more servers to increase overall availability. The following illustration shows how you can provide redundancy for each server role.
Availability within a server farm
The following table describes the server roles in a SharePoint Foundation 2010 environment and the redundancy strategies that can be used for each within a farm.
Server role
Preferred redundancy strategy within a farm
Front-end Web server
Deploy multiple front-end Web servers within a farm, and use Network Load Balancing (NLB).
Application server
Deploy multiple application servers within a farm.
Database server
Deploy database servers by using clustering or high-availability database mirroring.
Database availability strategies
You can use Microsoft SQL Server failover clustering or SQL Server high-availability database mirroring to support availability of databases in a SharePoint Foundation environment.
SQL Server failover clustering
Failover clustering can provide availability support for an instance of SQL Server. A failover cluster is a combination of one or more nodes or servers, and two or more shared disks. A failover cluster instance appears as a single computer, but has functionality that provides failover from one node to another if the current node becomes unavailable. SharePoint Foundation can run on any combination of active and passive nodes in a cluster that is supported by SQL Server.
SharePoint Foundation references the cluster as a whole; therefore, failover is automatic and seamless from the perspective of SharePoint Foundation.
For detailed information about failover clustering, see Getting Started with SQL Server 2008 Failover Clustering (http://go.microsoft.com/fwlink/?LinkID=102837&clcid=0x409) and Configure availability by using SQL Server clustering (SharePoint Foundation 2010).
SQL Server high-availability mirroring
Database mirroring is a SQL Server technology that can deliver database redundancy on a per-database basis. In database mirroring, transactions are sent directly from a principal database and server to a mirror database and server when the transaction log buffer of the principal database is written to disk. This technique can keep the mirror database almost up to date with the principal database. SQL Server Enterprise Edition provides additional functionality that improves database mirroring performance.
For mirroring within a SharePoint Foundation farm, you must use high-availability mirroring, also known as high-safety mode with automatic failover. High-availability database mirroring involves three server instances: a principal, a mirror, and a witness. The witness server enables SQL Server to automatically fail over from the principal server to the mirror server. Failover from the principal database to the mirror database typically takes several seconds.
A change from previous versions is that SharePoint Foundation is mirroring-aware. After you have configured a database mirror instance of SQL Server, you then use SharePoint Central Administration or Windows PowerShell cmdlets to identify the failover (mirror) database server location for a configuration database, content database, or service application database. Setting a failover database location adds a parameter to the connection string that SharePoint Foundation uses to connect to SQL Server. In the event of a SQL Server time-out event, the following occurs:
- The witness server that is configured for SQL Server mirroring automatically swaps the roles of the primary and mirror databases.
- SharePoint Foundation automatically attempts to contact the server that is specified as the failover database.
For information about how to configure database mirroring, see Configure availability by using SQL Server database mirroring (SharePoint Foundation 2010).
For general information about database mirroring, see Database Mirroring (http://go.microsoft.com/fwlink/?LinkID=180597).
|
|
|
Databases that have been configured to use the SQL Server FILESTREAM remote BLOB store provider cannot be mirrored. |
Comparison of database availability strategies for a single farm: SQL Server failover clustering vs. SQL Server high-availability mirroring
The following table compares failover clustering to synchronous SQL Server high-availability mirroring.
|
SQL Server failover clustering |
SQL Server high-availability mirroring |
|
|
Time to failover |
Cluster member takes over immediately upon failure. |
Mirror takes over immediately upon failure. |
|
Transactional consistency? |
Yes |
Yes |
|
Transactional concurrency? |
Yes |
Yes |
|
Time to recovery |
Shorter time to recovery (milliseconds) |
Slightly longer time to recovery (milliseconds). |
|
Steps required for failover? |
Failure is automatically detected by database nodes; SharePoint Foundation 2010 references the cluster so that failover is seamless and automatic. |
Failure is automatically detected by the database; SharePoint Foundation 2010 is aware of the mirror location, if it has been configured correctly, so that failover is automatic. |
|
Protection against failed storage? |
Does not protect against failed storage, because storage is shared between nodes in the cluster. |
Protects against failed storage because both the principal and mirror database servers write to local disks. |
|
Storage types supported |
Shared storage (more expensive). |
Can use less-expensive direct-attached storage (DAS). |
|
Location requirements |
Members of the cluster must be on the same subnet. |
Principal, mirror, and witness servers must be on the same LAN (up to 1 millisecond latency roundtrip). |
|
Recovery model |
SQL Server full recovery model recommended. You can use the SQL Server simple recovery model, but the only available recovery point if the cluster is lost will be the last full backup. |
Requires SQL Server full recovery model. |
|
Performance overhead |
Some decrease in performance may occur while a failover is occurring. |
High-availability mirroring introduces transactional latency because it is synchronous. It also requires additional memory and processor overhead. |
|
Operational burden |
Set up and maintained at the server level. |
The operational burden is larger than clustering. Must be set up and maintained for all databases. Reconfiguring after failover is manual. |
Service application redundancy strategies
The redundancy strategy you follow for protecting service applications that run in a farm varies, depending on where the service application stores data.
Service applications that store data in databases
To help protect service applications that store data in databases, you must follow these steps:
- Install the service on multiple application servers to provide redundancy within the environment.
- Configure SQL Server clustering or mirroring to protect the data.
The following service applications store data in databases:
- Business Data Connectivity service application
-
Application Registry service application
We do not recommend mirroring the Application Registry database, because it is only used when upgrading Windows SharePoint Services 3.0 Business Data Catolog information to SharePoint Foundation 2010.
- Usage and Health Data Collection service application
|
|
|
We recommend that you do not mirror the Usage and Health Data Collection service application Logging database. |
- Microsoft SharePoint Foundation Subscription Settings service
-
Redundancy and failover between closely located data centers configured as a single farm (“stretched” farm)
Some enterprises have data centers that are located close to one another with high-bandwidth connections so that they can be configured as a single farm. This is called a “stretched” farm. For a stretched farm to work, there must be less than 1 millisecond latency between SQL Server and the front-end Web servers in one direction, and at least 1 gigabit per second bandwidth.
In this scenario, you can provide fault tolerance by following the standard guidance for making databases and service applications redundant. The following illustration shows a stretched farm.
Stretched farm
-
Plan for disaster recovery (SharePoint Foundation 2010)
Updated: March 3, 2011
This article describes key decisions in choosing disaster recovery strategies for a Microsoft SharePoint Foundation 2010 environment.
In this article:
-
Disaster recovery overview
For the purposes of this article, we define disaster recovery as the ability to recover from a situation in which a data center that hosts SharePoint Foundation becomes unavailable.
The disaster recovery strategy that you use for SharePoint Foundation must be coordinated with the disaster recovery strategy for the related infrastructure, including Active Directory domains, Exchange Server, and Microsoft SQL Server. Work with the administrators of the infrastructure that you rely on to design a coordinated disaster recovery strategy and plan.
The time and immediate effort to get another farm up and running in a different location is often referred to as a hot, warm, or cold standby. Our definitions for these terms are as follows:
Hot standby A second data center that can provide availability within seconds or minutes.
Warm standby A second data center that can provide availability within minutes or hours.
Cold standby A second data center that can provide availability within hours or days.
Disaster recovery can be one of the more expensive requirements for a system. The shorter the interval between failure and availability and the more systems you protect, the more complex and costly a disaster recovery solution is likely to be.
When you invest in hot or warm standby data centers, costs include:
- Additional hardware and software, which often increase the complexity of operations between software applications, such as custom scripts for failover and recovery.
- Additional operational complexity.
The costs of maintaining hot or warm standby data centers should be evaluated based on your business needs. Not all solutions within an organization are likely to require the same level of availability after a disaster. You can offer different levels of disaster recovery for different content, services, or farms — for example, content that has high impact on your business, or search services, or an Internet publishing farm.
Disaster recovery is a key area in which information technology (IT) groups offer service level agreements (SLAs) to set expectations with customer groups. Many IT organizations offer a variety of SLAs that are associated with different chargeback levels.
When you implement failover between server farms, we recommend that you first deploy and tune the core solution within a farm, and then implement and test disaster recovery.
-
Choose a disaster recovery strategy
You can choose among many approaches to provide disaster recovery for a SharePoint Foundation environment, depending on your business needs. The following examples show why companies might choose cold, warm, or hot standby disaster recovery strategies.
-
Cold standby disaster recovery strategy: A business ships backups to support bare metal recovery to local and regional offsite storage on a regular basis, and has contracts in place for emergency server rentals in another region.
Pros:
- Often the cheapest option to maintain, operationally.
-
Often an expensive option to recover, because it requires that physical servers be configured correctly after a disaster has occurred.
Cons: The slowest option to recover.
-
Warm standby disaster recovery strategy: A business ships virtual server images to local and regional disaster recovery farms.
Pros: Often relatively inexpensive to recover, because a virtual server farm can require little configuration upon recovery.
Cons: Can be very expensive and time consuming to maintain.
-
Hot standby disaster recovery strategy: A business runs multiple data centers, but serves content and services through only one data center.
Pros: Often relatively fast to recover.
Cons: Can be quite expensive to configure and maintain.

Important:No matter which disaster recovery solution you decide to implement for your environment, you are likely to incur some data loss.
-
-
Planning for cold standby data centers
In a cold standby disaster recovery scenario, you can recover by setting up a new farm in a new location, (preferably by using a scripted deployment), and restoring backups. Or, you can recover by restoring a farm from a backup solution such as Microsoft System Center Data Protection Manager 2007 that protects your data at the computer level and lets you restore each server individually. This article does not contain detailed instructions for how to create and recover in cold standby scenarios. For more information, see:
-
Planning for warm standby data centers
In a warm standby disaster recovery scenario, you can create a warm standby solution by making sure that you consistently and frequently create virtual images of the servers in your farm that you ship to a secondary location. At the secondary location, you must have an environment available in which you can easily configure and connect the images to re-create your farm environment.
This article does not contain detailed instructions for creating warm standby solutions. For more information about how to plan to deploy farms by using virtual solutions, see Plan for virtualization (SharePoint Foundation 2010) (http://technet.microsoft.com/library/4cf78c3a-d466-4a69-a067-af03ae069749(Office.14).aspx).
-
Planning for hot standby data centers
In a hot standby disaster recovery scenario, you can set up a failover farm to provide disaster recovery in a separate data center from the primary farm. An environment that has a separate failover farm has the following characteristics:
- A separate configuration database and Central Administration content database must be maintained on the failover farm.
- All customizations must be deployed on both farms.

Note:We recommend that you use scripted deployment to create the primary and failover farm by using the same configuration settings and customizations.
- Updates must be applied to both farms, individually.
- SharePoint Foundation content databases can be successfully asynchronously mirrored or log-shipped to the failover farm.

Note:SQL Server mirroring can only be used to copy databases to a single mirror server, but you can log-ship to multiple secondary servers.
- Service applications vary in whether they can be log-shipped to a farm. For more information, see Service application redundancy across data centers later in this article.
This topology can be repeated across many data centers, if you configure SQL Server log shipping to one or more additional data centers.
Consult with your SAN vendor to determine whether you can use SAN replication or another supported mechanism to provide availability across data centers. The following illustration shows primary and failover farms before failover.
Primary and failover farms before failover
Service application redundancy across data centers
To provide availability across data centers for service applications, we recommend that for the services that can be run cross-farm, you run a separate services farm that can be accessed from both the primary and the secondary data centers.
For services that cannot be run cross-farm, and to provide availability for the services farm itself, the strategy for providing redundancy across data centers for a service application varies. The strategy employed depends on whether:
- There is business value in running the service application in the disaster recovery farm when it is not in use.
- The databases associated with the service application can be log-shipped or asynchronously mirrored.
- The service application can run against read-only databases.
The following sections describe the disaster recovery strategies that we recommend for each service application. The service applications are grouped by strategy.
Databases that can be log-shipped or asynchronously mirrored
After a service application has been initially deployed on a secondary farm, the databases that support the following service applications can be asynchronously mirrored or log-shipped across farms:
-
Application Registry service application
Databases: Application Registry service
-
Usage and Health Data Collection service application
Databases: Logging

Note:It is possible to log-ship or mirror the Logging database. However, we recommend that you do not run the Usage and Health Data Collection service on the disaster recovery farm, and that you do not mirror nor log-ship the Logging database.
Service applications and databases that cannot be log-shipped or asynchronously mirrored
The following service applications must be deployed on both the primary and failover farms, and cannot be log-shipped or asynchronously mirrored. For most of these service applications, we recommend that you deploy them and then verify that the failover farm has the same configuration settings as the primary farm. If configuration changes that affect the service are made on the primary farm, you must update the failover farm.
-
Business Data Connectivity service application
Databases: Business Data Connectivity
-
Microsoft SharePoint Foundation Subscription Settings service application
Database: Subscription Settings

Note:Log-shipping the Subscription Settings database is not supported.
-
System requirements for disaster recovery
In an ideal scenario, the failover components and systems match the primary components and systems in all ways: platform, hardware, and number of servers. At a minimum, the failover environment must be able to handle the traffic that you expect during a failover. Keep in mind that only a subset of users may be served by the failover site. The systems must match in at least the following:
- Operating system version and all updates
- SQL Server versions and all updates
- SharePoint 2010 Products versions and all updates
Although this article primarily discusses the availability of SharePoint 2010 Products, the system uptime will also be affected by the other components in the system. In particular, make sure that you do the following:
- Ensure that infrastructure dependencies such as power, cooling, network, directory, and SMTP are fully redundant.
- Choose a switching mechanism, whether DNS or hardware load balancing, that meets your needs.
-
Backup (SharePoint Foundation 2010)
Published: May 12, 2010
The articles in this section are written to meet the requirements of information technology (IT) professionals who are responsible for the planning, design, deployment, and operations of backup and recovery solutions. These solutions might be in enterprise, corporate, or branch office environments. The IT professionals who are responsible for backup and recovery solutions are expected to have an understanding of the technical details that are contained in this section.
A backup is a copy of data that is used to restore and recover that data after a system failure. Backups allow you to restore data after a failure. If you make the appropriate backups, you can recover from many system failures, including the following:
- Media failure
- User errors (such as deleting a file by mistake)
- Hardware failures (such as a damaged hard disk or permanent loss of a server)
- Natural disasters
Additionally, it is useful to keep backups of data for routine purposes. Those purposes include copying a database from one server to another, setting up database mirroring, and archiving to comply with regulatory requirements.
-
Back up all or part of a farm
The following tasks for backup and recovery are performed on the entire farm, farm databases, sites, subsites, or files:
-
This article describes the procedures that you can use to back up the entire farm.
-
This article describes the procedures that you can use to back up farm configuration settings.
-
This article describes the procedures that you can use to copy configuration settings from one farm to another, including how to back up and recover a farm without the content databases, how to back up and recover configurations only, and how to create a deployment script.
-
This article describes the procedures that you can use to back up a Web application that is associated with the farm, including configuration and content databases.
-
This article describes the procedures that you can use to back up a service application that is associated with the farm, including configuration and content databases.
-
This article describes the procedures that you can use to back up a site collection that is associated with the farm.
-
This article describes the procedures that you can use to back up a content database that is associated with the farm.
-
This article describes the procedures that you can use to back up a content database that is associated with the farm by saving the database to a snapshot.
-
This article describes the procedures that you can use to back up customizations that are associated with the farm.
-
This article describes the procedures that you can use to export a list, site, or document library that is associated with the farm. You can then import the items into another farm or move them to another place in this farm.
-
This article describes the procedures that you can use to back up or archive log files that are associated with the farm.
-
-
Concepts
Recovery (SharePoint Foundation 2010)
-
Back up a farm (SharePoint Foundation 2010)
Updated: September 16, 2010
This topic describes how to back up a whole server farm.
Procedures in this task:
- Use Windows PowerShell to back up a farm
- Use Central Administration to back up a farm
- Use SQL Server tools to back up a farm
For information about which tool to use for backups, see Plan for backup and recovery (SharePoint Foundation 2010).
We recommend that you regularly back up the complete farm by backing up both the configuration and content. Regularly backing up the farm reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that all the farm data and configurations are available for recovery, if that is required.
-
Considerations when backing up a farm
Consider the following when you prepare to back up a farm:
- Performing a backup does not affect the state of the farm. However, it does require resources and might slightly affect farm performance when the backup is running. You can avoid performance issues by backing up the farm during hours when farm use is lowest, such as outside office hours.
- The farm backup process does not back up any certificates that you used to form trust relationships. Endure that you have copies of these certificates before you back up the farm. You must re-establish these trust relationships after restoring the farm.
- Backing up the farm backs up the configuration and Central Administration content databases, but these cannot be restored using Microsoft SharePoint Foundation 2010 tools. For more information about backing up and restoring all the farm databases, see Move all databases (SharePoint Foundation 2010) (http://technet.microsoft.com/library/0aaf3261-f06b-4f4f-96d0-96fecdf78bc6(Office.14).aspx).
- When you back up a farm that contains a Web application that is configured to use forms-based authentication, you must also use a file backup system to protect the Web.config files because the Web.config files have been updated manually to register the membership and role providers, and manual changes to the Web.config files are not backed up. Similarly, Web.config files are not restored when you restore a Web application. After recovery, you must update the Web.config files and redeploy the providers. For more information, see Plan authentication methods (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b6bc8fec-c11c-4ed7-a78d-3ad61c7ef6c0(Office.14).aspx) and Configure claims authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ef8c3024-26de-4d06-9204-3c6bbb95fb14(Office.14).aspx).
-
SharePoint Foundation 2010 backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm.
If you restore the Business Data Connectivity service or the farm and then restore the data service to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might not be able to locate the data source.
-
SharePoint Foundation 2010 backup backs up remote Binary Large Object (BLOB) stores but only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores.
If you are using another provider, you must manually back up the remote BLOB stores.
- If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your environment by using either SharePoint tools or SQL Server tools, the TDE encryption key in not backed up or restored. You must back up the key manually. When restoring, you must manually restore the key before restoring the data. For more information, see Understanding Transparent Data Encryption (TDE) (http://go.microsoft.com/fwlink/?LinkID=196394).
-
Task requirements
Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see Prepare to back up and recover (SharePoint Foundation 2010) (http://technet.microsoft.com/library/cca219c4-4930-454b-9d6e-3ce1ad4799f5(Office.14).aspx).
-
Use Windows PowerShell to back up a farm
You can use Windows PowerShell to back up the farm manually or as part of a script that can be run at scheduled intervals.
To back up a farm by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt, type the following command:
|
Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} [-Verbose] |
Where <BackUpFolder> is the path of a folder on the local computer or the network in which you want to store the backups.
|
|
|
If you are backing up the farm for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. |
For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to back up a farm
You can use Central Administration to back up the farm.
To back up a farm by using Central Administration
- To perform this procedure, you must be a member of the Farm Administrators group on the computer that is running Central Administration.
- In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
- On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click Next.
- On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.
|
|
|
If you are backing up the farm for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. |
- In the Back Up Only Configuration Settings section, click Back up content and configuration settings.
- In the Backup File Location section, type the UNC path of the backup folder, and then click Start Backup.
-
You can view the general status of all backup jobs at the top of the Backup and Restore Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6.
-
Use SQL Server tools to back up a farm
If you want to back up the complete farm, you must use either Windows PowerShell or Central Administration. You cannot back up the complete farm by using the SQL Server tools because you cannot use the tools to back up the farm’s configuration. However, you can back up all the databases that are associated with the farm.
To back up the databases associated with a farm by using SQL Server tools
- To use SQL Server tools to back up SharePoint Foundation 2010 databases, the account that is used to back up the databases must be a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.
- Open SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
- Right-click the database that you want to back up, point to Tasks, and then click Back Up.
- In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396).
- In the Backup component area, click Database.
- Either use the default name provided or specify a name for the backup set in the Name text box.
- Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).
- In the Destination area, specify where you want to store the backup.
- Click OK to back up the database.
- Repeat steps 1-10 for each farm database.
-
Related content
-
Back up a farm configuration (SharePoint Foundation 2010)
Published: May 12, 2010
This article describes how to back up the configuration of a server farm.
In earlier versions of Microsoft SharePoint Foundation, you could not back up or restore the configuration database. In Microsoft SharePoint Foundation 2010, you can perform the equivalent operation by backing up or restoring the configuration of the server farm.
We recommend that you regularly back up the complete farm by backing up both the configuration and content. However, you might want to perform configuration-only backups in test or development environments. Similarly, if you are using Microsoft SQL Server tools to back up the databases for the farm, you will want to back up the configuration. Regularly backing up the farm reduces the possibility of data losses that can occur from hardware failures, power outages, or other problems. It helps to ensure that all the farm data and configurations are available for recovery. For more information about what to back up, see Plan for backup and recovery (SharePoint Foundation 2010).
The configuration backup will extract and back up the configuration settings from a SharePoint Foundation 2010 configuration database. You can back up configuration from any configuration database that includes the configuration database for the current farm or another farm, or a configuration database that is not associated with any farm.
For information about which tool to use for backups, see Plan for backup and recovery (SharePoint Foundation 2010).
Procedures in this task:

Note:You cannot use either SQL Server tools or Data Protection Manager to back up the farm configuration.
-
Task requirements
Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see Prepare to back up and restore (SharePoint Foundation) (http://technet.microsoft.com/library/cca219c4-4930-454b-9d6e-3ce1ad4799f5(Office.14).aspx).

Important:Backing up the farm configuration will not back up the information you have to have to restore service applications. If you want to restore a service application, you must perform a configuration and content backup of the farm. For more information about backing up service applications, see Back up a service application (SharePoint Foundation 2010).
-
Use Windows PowerShell to back up a farm configuration
You can use Windows PowerShell to back up the configuration from any configuration database on the current farm, on another farm, or from a configuration database that is not associated with any farm. You can back up a farm configuration manually or as part of a script that can be run at scheduled intervals.
To back up the configuration from any configuration database by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
|
Backup-SPConfigurationDatabase -Directory <BackupFolder> -DatabaseServer <DatabaseServerName> -DatabaseName <DatabaseName> -DatabaseCredentials <WindowsPowerShellCredentialObject> [-Verbose] |
Where:
- <BackupFolder> is the path to the folder with the correct backup files.
- <DatabaseServerName> is the name of the database server for the farm that you are backing up.
- <DatabaseName> is the name of the farm configuration database.
-
If you are not logged on with an account with db_backupoperator fixed database role on the database server where the configuration database is stored, you must specify the value for DatabaseCredentials
parameter.
For more information, see Backup-SPConfigurationDatabase (http://technet.microsoft.com/library/28ddc176-1b7f-47dd-868f-39b7c403a900(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to back up a farm configuration
You can use Central Administration to back up the configuration of the farm that Central Administration is running on. To back up the configuration of a remote farm, you must use the Central Administration Web site that is running on the remote farm. You cannot use Central Administration to back up an unattached configuration database.
To back up a farm configuration by using Central Administration
- Verify that the user account performing this procedure is a member of the Farm Administrators group.
- On the Central Administration Home page, in the Backup and Restore section, click Perform a backup.
- On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click Next.
|
|
|
You can back up the configuration for any service or application. However, common practice is to back up configuration at the farm level. |
- On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select Full.
- In the Backup Only Configuration Settings section, select the Backup only configuration settings option.
- In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
- You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually refresh the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5.
-
Concepts
Restore a farm configuration (SharePoint Foundation 2010)
-
Back up a Web application (SharePoint Foundation 2010)
Updated: September 16, 2010
This article describes how to back up a Web application. Regularly backing up a Web application reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that can help to ensure that all the Web application-related data and configurations are available for recovery, if that is required. We recommend that Web application backups be created in addition to regular backups at the farm level.
This topic describes how to back up a single Web application.
In this topic:
-
Considerations when backing up a Web application
Consider the following when you prepare to back up a Web application.
- You can back up only one Web application at a time by using the procedures in this article. However, you can simultaneously back up all Web applications by backing up the entire farm.
- Backing up a Web application does not affect the state of the farm. However, it does require resources and might slightly affect farm performance when the backup is running. You can avoid performance issues by backing up the Web application during hours when farm use is lowest, such as outside office hours.
- If the Web application uses the object cache, you must manually configure two special user accounts for the Web application after you restore the Web application. For more information about the object cache and how to configure these user accounts, see Configure object cache user accounts (http://technet.microsoft.com/library/cd646bb3-28c6-4040-866c-7d7936837ade(Office.14).aspx).
- When you back up a Web application, the Internet Information Services (IIS) settings and all content databases that are associated with the Web application are also backed up.
- When you back up a Web application that is configured to use forms-based authentication, you must also use a file backup system to protect the Web.config files because the Web.config files have been updated manually to register the membership and role providers, and manual changes to the Web.config files are not backed up. Similarly, Web.config files are not restored when you restore a Web application. After recovery, you must update the Web.config files and redeploy the providers. For more information, see Plan authentication methods (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b6bc8fec-c11c-4ed7-a78d-3ad61c7ef6c0(Office.14).aspx) and Configure claims authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ef8c3024-26de-4d06-9204-3c6bbb95fb14(Office.14).aspx).
-
Task requirements
Before you begin, you must create a network folder in which to store the backups. Both the Windows SharePoint Services Timer V4 service account and the server farm user account must have Full Control permissions to this folder. For more information about how to create a backup folder, see Prepare to backup and recover (SharePoint Foundation) (http://technet.microsoft.com/library/cca219c4-4930-454b-9d6e-3ce1ad4799f5(Office.14).aspx).
-
Use Windows PowerShell to back up a Web application
You can use Windows PowerShell to back up a Web application manually or as part of a script that can be run at scheduled intervals.
To back up a Web application by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin. Additionally, the user account performing this procedure must be a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
|
Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <WebApplicationName> [-Verbose] |
Where:
- <BackupFolder> is the path of the folder you use for storing backup files.
- <WebApplicationName> is the name of the Web application.
|
|
|
If you are backing up the Web application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. |
For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to back up a Web application
You can use Central Administration to back up a Web application.
To back up a Web application by using Central Administration
- Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
- On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the Web application from the list of components, and then click Next.
|
|
|
The Web application might consist of several components. You must select the top-level component. |
- On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.
|
|
|
If you are backing up the Web application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. |
- In the Back Up Only Configuration Settings section, click Back up content and configuration settings.
- In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
-
You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6.
-
Use SQL Server tools to back up a Web application
You cannot back up the complete Web application by using SQL Server tools. However, you can back up all the databases that are associated with the Web application. To back up the complete Web application, use either Windows PowerShell or Central Administration.
To back up a Web application by using SQL Server tools
- Verify that the user account that is used to back up the databases is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored. Additionally, verify that the user account has Full Control permissions on the backup folder.
- Open SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
- Right-click the database that you want to back up, point to Tasks, and then click Back Up.
- In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396).
- In the Backup component area, click Database.
- Either use the default name provided or specify a name for the backup set in the Name text box.
- Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).
- In the Destination area, specify where you want to store the backup.
- Click OK to back up the database.
- Repeat steps 1-10 for each database that is associated with the Web application.
-
Related content
-
Back up a service application (SharePoint Foundation 2010)
Published: May 12, 2010
We recommend that you regularly back up at the farm level. However, business or IT requirements might require that you back up a service application. Regularly backing up a service application reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps to ensure that all the service application-related data and configurations are available for recovery, if that is required. You can back up one service application at a time, or you can back up all service applications at once.
For information about what to back up and which tools to use, see Plan for backup and recovery (SharePoint Foundation 2010). For more information, see Back up a farm (SharePoint Foundation 2010).
Backing up a service application does not affect the state of the farm. However, it does require resources. Therefore, backing up a service application might affect farm performance while the backup is running. You can avoid performance issues by backing up the service application during hours when farm use is lowest.

Note:SharePoint Foundation 2010 backup backs up remote Binary Large Object (BLOB) stores but only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores.
If you are using another provider, you must manually back up the remote BLOB stores.
Procedures in this topic:
- Use Windows PowerShell to back up a service application
- Use Central Administration to back up a service application

Note:You cannot use SQL Server tools or Data Protection Manager to back up a service application.
-
Task requirements
Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see Prepare to backup and recover (SharePoint Foundation) (http://technet.microsoft.com/library/cca219c4-4930-454b-9d6e-3ce1ad4799f5(Office.14).aspx).

Note:Microsoft SharePoint Foundation 2010 backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm.
If you back up the Business Data Connectivity service or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might not be able to locate the data source.
-
Use Windows PowerShell to back up a service application
You can use Windows PowerShell to back up one or more service applications manually or as part of a script that can be run at scheduled intervals.
To back up a service application by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt, type the following command:
Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <ServiceApplicationName> [-Verbose]
Where:
- <BackupFolder> is the path of a folder on the local computer or on the network in which you want to store the backups.
- <ServiceApplicationName> is the name of the service application that you want to back up.
|
|
|
To back up all the service applications, at the Windows PowerShell command prompt, type the following command: Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item “Farm\Shared Service Applications” [-Verbose] |
|
|
|
If you are backing up the service application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. Some service applications always require a full backup. For these service applications, even if you select the Differential option, the system performs a full backup. |
For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to back up a service application
You can use Central Administration to back up a service application.
To back up a service application by using Central Administration
- Verify that the user account that performs this procedure is a member of the Farm Administrators group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
- On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the service application from the list of components, and then click Next. To back up all the service applications, select the Shared Service Applications node.
|
|
|
The service application might consist of several components. You must select the top-level component. |
- On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.
|
|
|
If you are backing up the service application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. Some service applications always require a full backup. For these service applications, the system performs a full backup even if you select the Differential option. |
- In the Backup File Location section, in the Backup location box, type the path of the backup folder, and then click Start Backup.
-
You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5.
-
Concepts
Restore a service application (SharePoint Foundation 2010)
-
Back up a site collection (SharePoint Foundation 2010)
Published: May 12, 2010
This article describes how to back up an individual site collection. We recommend that you regularly back up the complete farm. However, IT practices might require that you also back up a site collection. For more information about what to back up, see Plan for backup and recovery (SharePoint Foundation 2010).

Note:If the site collection’s Lock status is set to Not locked or Adding content prevented, Microsoft SharePoint Foundation 2010 temporarily sets the site to Read-Only while the backup operation is occurring. SharePoint Foundation 2010 does this to reduce the possibilities of users changing the site collection while it is being backed up. After the backup is finished, the setting is changed back its normal status.
Performing a site collection backup might require resources and might slightly affect farm performance when the backup is running. You can help avoid performance issues by backing up the farm during hours when farm use is lowest, such as outside office hours.
Procedures in this task:
-
Task requirements
Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder.
For more information about how to create a backup folder, see Prepare to backup and recover (SharePoint Foundation) (http://technet.microsoft.com/library/cca219c4-4930-454b-9d6e-3ce1ad4799f5(Office.14).aspx).
-
Use Windows PowerShell to back up a site collection
You can use Windows PowerShell to back up a site collection manually or as part of a script that can be run at scheduled intervals.
To back up a site collection by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt type the following command:
Backup-SPSite -Identity <Site collection name> -Path <backup file> [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose]
If you want to overwrite a previously used backup file, use the Force
parameter. You can use the NoSiteLock
parameter to keep the read-only lock from being set on the site collection while it is being backed up. However, using this parameter can allow users to change the site collection while it is being backed up and might lead to possible data corruption during backup.
If the database server is running an Enterprise Edition of Microsoft SQL Server, we recommend that you also use the UseSqlSnapshot
parameter for more consistent backups. You can also export sites or lists from these snapshots.
|
|
|
When you perform a backup that uses the UseSqlSnapshot parameter, a backup will be completed successfully. However, you will see an error similar to the following: Backup-SPSite : Operation is not valid due to the current state of the object. At line:1 char:14 + Backup-SPSite <<<< http://site -Path + CategoryInfo : NotSpecified: (:) [Backup-SPSite], InvalidOperationException + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.SharePoint.PowerShell.SPCmdletBackupSite\\yourpath |
|
|
|
If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots. |
For more information about using SQL snapshots, see Back up databases to snapshots (SharePoint Foundation 2010).
For more information, see Backup-SPSite (http://technet.microsoft.com/library/d4c31a1a-82a7-425f-b1bb-22e70bedd338(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to back up a site collection
You can use Central Administration to back up a site collection.
To back up a site collection by using Central Administration
- Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service has Full Control permissions on the backup folder.
- In Central Administration, on the Home page, in the Backup and Restore section, click Perform a site collection backup.
- On the Site collection backup page, select the site collection from the Site Collection list.
- Type the local path of the backup file in the Filename box.
|
|
|
If you want to reuse a file, select the Overwrite existing file check box. |
- Click Start Backup.
-
You can view the general status of all backup jobs at the top of the Granular Backup Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Site Collection Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, you can review them in the Failure Message column of the Granular Backup Job Status page.
-
Concepts
Restore a site collection (SharePoint Foundation 2010)
-
Back up customizations (SharePoint Foundation 2010)
Updated: August 12, 2010
This article describes how to back up customizations that have been made to Microsoft SharePoint Foundation 2010 sites.
The following kinds of customizations can be made to sites:
-
Customizations packaged as solutions (.wsp files). Solutions contain developed site elements, and are typically created by developers. Developed site elements include the following:
- Web Parts
- Workflows
- Site and list definitions
- Document converters
- Event receivers
- Timer jobs
- Assemblies
-
Authored site elements, which are typically created by Web designers, are not explicitly compiled and reside in a content database. Authored site elements include the following:
- Master pages
- Cascading style sheets
- Forms
- Layout pages
- Changes to the Web.config file
- Third-party solutions and their associated binary files and registry keys, such as IFilters
- Changes to sites created by direct editing through the browser
- Developed customizations that are not packaged as solutions
Each of these kinds of customizations requires a different type of backup.
In this article:
-
-
Backing up solution packages
Solution packages can be created by using Microsoft SharePoint Designer 2010 or Microsoft Visual Studio 2010. We strongly recommend that all customizations be deployed as solution packages.
A solution package is a deployable, reusable file that can contain a set of Features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually. Solution packages can include Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions.
The method that you use to back up solution packages is determined by whether the customizations are deployed as trusted solutions or sandboxed solutions.
Trusted solutions are solution packages that farm administrators deploy. Trusted solutions are deployed to the entire farm and can be used on any site within the farm. Trusted solutions are stored in the configuration database. Trusted solutions are backed up when a farm is backed up by using SharePoint Foundation 2010 backup, and are included in configuration-only backups. You can also back up trusted solutions as a group or individually. Trusted solutions are visible in the backup hierarchy.
Sandboxed solutions are solution packages that site collection administrators can deploy to a single site collection. Sandboxed solutions are stored in the content database that is associated with the site collection to which the solution packages are deployed. They are included in SharePoint Foundation 2010 farm, Web application, content database, and site collection backups, but are not visible in the backup hierarchy and cannot be selected or backed up individually.
We recommend that you keep a backup of the original .wsp file as well as the source code used to build the .wsp file for both trusted solutions and sandboxed solutions.
To back up trusted solutions by using Central Administration
- Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
-
On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select Solutions, and then click Next.
You can also select an individual solution, if you only want to back up a single solution.
- On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.
|
|
|
If you are backing up the solution for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. |
- In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
-
You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.
To back up trusted solutions by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt, type the following command to back up all of the solutions in the farm. To back up a single solution, add the name of the solution to the item path “farm\solutions”.
|
Backup-SPFarm -backupmethod full -directory <UNC location> -item “farm\solutions” |
Where:
- <UNC location> is UNC location of the directory that you want to back up to.
For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
Backing up sandboxed solutions
You cannot back up only sandboxed solutions. Instead, you must back up the farm, Web application, or content database with which the sandboxed solution is associated. For more information about these methods of backing up, see Related content.
-
Backing up authored site elements
You cannot back up only authored site elements. Instead, you must back up the farm, Web application, or content database with which the authored site element is associated. For more information about these methods of backing up, see Related content.
-
Backing up workflows
Workflows are a special case of customizations that you can back up. Make sure that your backup and recovery plan addresses any of the following scenarios that apply to your environment:
- Declarative workflows, such as those created in Microsoft SharePoint Designer 2010, are stored in the content database for the site collection to which they are they are deployed. Backing up the content database protects these workflows.
- Custom declarative workflow actions have components in the following three locations:
- The Visual Studio 2010 assemblies for the actions are stored in the global assembly cache (GAC).
- The XML definition files (.ACTIONS files) are stored in the 14\TEMPLATE\<LCID>\Workflow directory.
-
An XML entry to mark the action as an authorized type is stored in the Web.config file for the Web applications in which it is used.
If the farm workflows use custom actions, you should use a file backup system to protect these files and XML entries. Similar to SharePoint Foundation features such as Web Parts and event receivers, these files should be reapplied to the farm as needed after recovery.
- Workflows that depend on custom code, such as those that are created by using Visual Studio 2010, are stored in two locations. The Visual Studio 2010 assemblies for the workflow are stored in the GAC, and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Foundation features such as Web Parts and event receivers. If the workflow was installed as part of a solution package, backing up the farm, Web application, content database, or site collection protects these workflows.
- If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must back up both site collections to protect the workflow. This includes workflows that write to a history list or other custom list in another site collection. Performing a farm backup is sufficient to back up all site collections in the farm and all workflows that are associated with them.
- Workflows that are not yet deployed must be backed up and restored separately. When you are developing a new workflow but have not yet deployed it to the SharePoint Foundation farm, make sure that you back up the folder where you store the workflow project files by a file system backup application.
-
Backing up changes to the Web.config file
A common customization to SharePoint Foundation 2010 is to change the Web.config file. We strongly recommend that you make changes to the Web.config file by using Central Administration or the SharePoint Foundation 2010 APIs and object model. Because these changes are stored in the configuration database, they can be recovered from a farm or configuration-only backup.
Changes to the Web.config file that are not made by using Central Administration or the SharePoint Foundation 2010 APIs and object model should be protected by using a file system backup.

Note:If you are using forms-based authentication, provider registration in the Web.config file is manual, and is not protected by SharePoint Foundation 2010 backup. In this case, be sure to back up the Web.config file by using a file system backup.
-
Backing up third-party products
If third-party products are deployed as solution packages, they are protected by SharePoint Foundation 2010 backup. We recommend that you keep all the original files, distribution media, documentation, and the license and product keys that are required for installation.
-
Backing up changes made by direct editing
Changes made directly to a site by directly editing through the browser can be difficult to back up. The following table describes backup strategies for specific objects.
Edited object
Backup strategy
List
Use SharePoint Designer 2010 and save as a template. For more information, see Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkId=199515).
Site
Use SharePoint Designer 2010 and save as a template. For more information, see Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkId=199515).
Site collection
Use site collection backup. For more information, see Back up a site collection (SharePoint Foundation 2010).
-
Backing up developed customizations that are not packaged as solutions
Backing up developed customizations that are not deployed as solution packages can be a complex process because the customization file locations might not be stored in standardized places and SharePoint Foundation 2010 does not automatically back them up.
Consult with the development team or customization vendor to determine whether the customizations involve additional add-in software or files in other locations. We recommend that you back up these directories with a file system backup solution. The following table lists locations where developed customizations are typically stored on Web servers.
Location
Description
%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14
Commonly updated files, custom assemblies, custom templates, custom site definitions
Inetpub
Location of IIS virtual directories
%WINDIR%\Assembly
Global assembly cache (GAC): a protected operating system location where the Microsoft .NET Framework code assemblies are installed to provide full system access
-
Related content
-
Back up a content database (SharePoint Foundation 2010)
Updated: June 24, 2010
Microsoft SharePoint Foundation 2010 content databases can grow to be very large. Therefore, you might want to back them up separately from farm backups. Regularly backing up content databases reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that all the data is available for recovery, if that is required. You can only back up one content database at a time.
This topic describes how to back up a single content database.
Procedures in this task:
-
Task requirements
Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder.

Note:SharePoint Foundation 2010 backup backs up remote Binary Large Objects (BLOB) stores but only if you are using the SQL Filestream remote BLOB store provider to place data in remote BLOB stores.
If you are using another provider you must manually back up these remote BLOB stores.

Important:If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your environment by using either SharePoint tools or SQL Server tools, the TDE encryption key in not backed up or restored. You must backup the key manually. When restoring, you must manually restore the key before restoring the data. For more information, see Understanding Transparent Data Encryption (TDE) (http://technet.microsoft.com/en-us/library/bb934049.aspx)
-
Use Windows PowerShell to back up a content database
You can use Windows PowerShell to back up a content database manually or as part of a script that can be run at scheduled intervals.
To back up a content database by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Backup-SPFarm -Directory <Backup folder> -BackupMethod {Full | Differential} -Item <Content database name> [-Verbose]
|
|
|
If you are backing up the content database for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. |
For more information, see Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx)
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to back up a content database
You can use Central Administration to back up a content database.
To back up a content database by using Central Administration
- Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
- On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the content database that you want to back up from the list of components, and then click Next.
|
|
|
Not all content databases can be selected in the list. If a database is not selectable, you must use Windows PowerShell to back up the content database. |
- On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.
|
|
|
If you are backing up the content database for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. |
- In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
-
You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.
-
Use SQL Server tools to back up a content database
You can use SQL Server tools to back up a content database.
To back up a content database by using SQL Server tools
- Verify that the user account that is performing this procedure is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.
- Open SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
- Right-click the database that you want to back up, point to Tasks, and then click Back Up.
- In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396) in SQL Server Books Online.
- In the Backup component area, click Database.
- Either use the default name provided or specify a name for the backup set in the Name text box.
- Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).
- In the Destination area, specify where you want to store the backup.
- Click OK to back up the database.
- Repeat steps 1-9 for each content database that you want to back up.
-
Concepts
Restore a content database (SharePoint Foundation 2010)
-
Back up databases to snapshots (SharePoint Foundation 2010)
Published: May 12, 2010
This topic describes how to back up a farm database to a snapshot.
You can only use SQL Server tools to back up a farm database to a snapshot.

Important:You must be running Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2 Enterprise Edition to take database snapshots.
We recommend that you regularly back up the complete farm. Regularly backing up the farm reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that that all the farm data and configurations are available for recovery, if that is required. For more information, see Back up a farm (SharePoint Foundation 2010). However, IT requirements might require that you backup databases to snapshots. Although you can back up any farm database to a snapshot, you typically back up content databases.
A database snapshot provides a read-only, static view of a source database as it existed at snapshot creation, minus any uncommitted transactions. Uncommitted transactions are rolled back in a newly created database snapshot because the Database Engine runs recovery after the snapshot has been created (transactions in the database are not affected). For more information about database snapshots, see Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=163950).
-
Task requirements
Before you begin, you must create a folder on the database server. If you want to store the snapshots at another location, you can move the backup files to a backup folder on the network after the operation is finished.
-
Use SQL Server tools to back up a database to a snapshot
If you want to back up databases to snapshots, you must use SQL Server tools. The databases that are associated with the farm are determined by the features that you have installed on the farm.
To back up a database to a snapshot by using SQL Server tools
- Verify that the account that is used to back up the databases is a member of the SQL Server db_owner fixed database role.
- Open SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
- Select the database that you want to back up, and then click New Query.
- Copy the following text, and then paste it to the query pane.
|
CREATE DATABASE <snapshot name> |
-
Other Resources
Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=163950)
-
Export a site, list, or document library (SharePoint Foundation 2010)
Published: May 12, 2010
We recommend that you regularly back up the complete farm. However, business or IT requirements might require that you export a site, list, or document library. Regularly exporting sites, lists, and document libraries reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that data is available for recovery, if that is required. You can only export one site, list, or document library at a time.
For information about what to back up and which tools to use, see Plan for backup and recovery (SharePoint Foundation 2010).
Procedures in this task:
- Use Windows PowerShell to export a site, list, or document library
- Use Central Administration to export a site, list, or document library

Note:You cannot use SQL Server tools or Data Protection Manager to export a site, list or document library.
-
Task requirements
Before you begin, you must create a folder on the local computer or the network in which to store the export file. For better performance, we recommend that you export to the local computer and then move the export file to a network folder.
-
Use Windows PowerShell to export a site, list, or document library
You can use Windows PowerShell to export a site, list, or document library manually or as part of a script that can be run at scheduled intervals.
To export a site, list or document library by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Export-SPWeb -Identity <Site URL> -Path <Path and file name> [-ItemUrl <URL of site, list, or library>] [-IncludeUserSecurity] [-IncludeVersions] [-NoFileCompression] [-GradualDelete] [-Verbose]
If you are exporting a large site, list, or document library, you can use the GradualDelete
parameter. When this parameter is used, the site collection is marked as deleted, which immediately prevents any further access to its content. The data in the deleted site collection is then deleted gradually over time by a timer job instead of all at once, which reduces its impact on the performance of farm servers and SQL Server.
To specify which version of the site, list, or document library to include, use the IncludeVersions
parameter and specify “LastMajor” (default), “CurrentVersion”, “LastMajorandMinor”, or “All”. To include the user security settings with the list or document library, use the IncludeUserSecurity
parameter. If you want to overwrite the file that you specified, use the Force
parameter. To view the progress of the backup operation, use the Verbose
parameter.
The NoFileCompression
parameter lets you specify that no file compression is performed during the export process. Using this parameter can lower resource usage up to 30% during the export process. Using this parameter will result in a backup folder being created instead of a compressed file. If you use the NoFileCompression
parameter in the Export-SPWeb
command, you must also use it when you import the content by using the Import-SPWeb
command.
For more information, see Export-SPWeb (http://technet.microsoft.com/library/cd85bf19-6f24-4f13-bd9c-37bbf279ea2b(Office.14).aspx)
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to export a site, list, or document library
You can use Central Administration to export a site, list, or document library. You can only export one site, list, or document library at a time.
To export a site, list, or document library by using Central Administration
- Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
- In Central Administration, on the Home page, click Backup and Restore.
- On the Backup and Restore page, in the Granular Backup section, click Export a site or list.
- On the Site or List Export page, in the Site Collection section, select the site collection from the Site Collection list, and then select the site from the Site list.
- If you are exporting a site, skip this step, Select the list or document library from the List list.
- In the File Location section, in the Filename box, type the UNC path of the shared folder and the file to which you want to export the list or document library. The file name must use the .cmp extension.
- If the file already exists and you want to use this file, select the Overwrite existing files check box. Otherwise, specify a different file name.
- If you want to export all the security and permissions settings with the list or library, in the Export Full Security section, select the Export full security check box.
- If you want to specify which version of the list or library to export, select one of the following versions from the Export versions list:
- All Versions
- Last Major
- Current Version
- Last Major and Last Minor
- When you have specified the settings that you want, click Start Export.
-
You can view the status of all backup jobs at the top of the Granular Backup Job Status page. You can view the status of the current backup job in the Content Export section of the page. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the <file name>.export.log file at the UNC path that you specified in step 6.
-
Back up or archive logs (SharePoint Foundation 2010)
Published: May 12, 2010
A system-wide strategy for data protection should include backing up or archiving the logs in which data related to Microsoft SharePoint Foundation 2010 is recorded. This data can be useful for performance analysis, troubleshooting, monitoring compliance with service level agreements, and legal, regulatory, or business reasons. Therefore, protect this data as part of the routine maintenance by backing up or archiving the logs.
The following sections are labeled in the following manner to indicate how important it is to back up or archive this kind of log:
- [Essential] means that the log contains data that is essential to the environment. The data would be lost if a disk failure or other problem occurred.
- [Recommended] means that the log contains data that is useful in most environments for troubleshooting, operational, legal, or other needs.
In this article:
-
[Essential] Back up transaction logs
Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 transaction logs record all changes that were made to a database since the last checkpoint or full backup. These logs contain required data for restoring the farm.
We recommend that you back up these logs every 5–10 minutes. When you back up these logs, they are automatically truncated. You can use the Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 tools to back up the transaction log. For more information, see Creating Transaction Log Backups (http://go.microsoft.com/fwlink/?LinkId=124881) in the Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 documentation.
Transaction logs are also automatically backed up when you back up the farm, Web application, or databases by using either the SharePoint Central Administration Web site or the Windows PowerShell. For more information, see Back up a farm (SharePoint Foundation 2010).
How transaction log size affects farm backup times
When you back up SharePoint Foundation 2010, the size of the transaction log can affect how long the backup operation takes. Because the transaction log records all changes to a database since the last checkpoint or full backup, the log can grow very large over time. If the transaction log has grown very large, backups might take a very long time. For more information, see How to stop the transaction log of a SQL Server database from growing unexpectedly (http://go.microsoft.com/fwlink/?LinkID=111458).
The recommended way to truncate the transaction log if you are using a full recovery model is to back up the log. Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 automatically truncates the inactive parts of the transaction log when you back up the log. We also recommend that you pre-grow the transaction log to avoid auto-growing the log. For more information, see Managing the Size of the Transaction Log File (http://go.microsoft.com/fwlink/?LinkId=124882). For more information about using a full recovery model, see Backup Under the Full Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127985). For more information about using a simple recovery model, see Backup Under the Simple Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127987).
We do not recommend that you manually shrink the transaction log size or manually truncate the log by using the Truncate method.
-
[Recommended] Collect usage data
Usage analysis enables you to track how Web sites are being used. Log files are created daily to track usage. You can configure the setting for the collection of usage data. One of the most important settings is the location of the log files. By default, the log folder is configured to be on the same drive partition where SharePoint Foundation 2010 is installed. To make sure that the log files to not fill up that drive, you should change the log folder to be on a separate drive.
The location of the log directory is a farm-level setting, and the directory that is specified in this setting must exist on all servers in the farm. These logs are automatically backed up when you back up the farm.
For most environments, the default settings are adequate. For more information about configuring usage data collection settings, see Configure usage and health data collection (SharePoint Foundation 2010) (http://technet.microsoft.com/library/5c97fd40-008a-4fbc-8b3a-98244d8f0016(Office.14).aspx).
-
[Recommended] Archive diagnostic logs
Diagnostic logs provide detailed information about the operation of the farm. You can configure the level of detail that is logged. We recommend that you archive these logs when you archive the farm. You can archive the logs for the whole farm or a specific server. You can archive these files by manually copying them to a shared folder, or by using the Windows PowerShell Merge-SPlogFile cmdlet. You can use the Merge-SPLogFIle cmdlet to archive the log files on all of the farm servers at once.
You can use the Windows PowerShell Copy-Item cmdlet to archive log files from a single server. The Copy-Item cmdlet does not provide filtering and you must copy the entire log file.
For more information about how to configure diagnostic logging, see Configure diagnostic logging (SharePoint Foundation 2010) (http://technet.microsoft.com/library/a5641210-8224-4e11-9d93-4f96fa4c327c(Office.14).aspx)
To archive diagnostic logs from all farm servers by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt, type the following command:
Merge-SPLogFile -Path “<path to merged log file>.log” -Overwrite
For example, Merge-SPLogFile -Path “C:\Logs\MergedFiles\AllFarm_merged_12.20.2009.log” -Overwrite
|
|
|
Merging all log entries for all farm servers can take a long time and use resources. We recommend filtering the entries to match a specific set of criteria before merging. |
To merge log entries that match a specific set of criteria, type the following command:
Merge-SPLogFile -Path “<path to merged log file>.log” -Area “<Area>” -Category “<Category>”
You can filter by one or more of the following:
- Area (one or more, wildcard)
- Category (one or more, wildcard)
- Level
- Correlation (one or more)
- EventID (one or more, wildcard)
- Message (wildcard)
- StartTime
- EndTime
- Process (one or more, wildcard)
- ThreadID (one or more)
|
|
|
You can name the merged log file however you want. We recommend that you use a naming convention that makes it easy to determine what the log file contains, such as “<date merged>_<farm name>_<filtering criteria>. For example, to signify all the farm server log entries forSharePoint Foundation 2010 that involve the database category and are marked as “High” use, “Dec_2009_ContosoInternet_Foundation_Database_High.log”. |
For more information, see Merge-SPLogFile (http://technet.microsoft.com/library/759702d7-bda2-4302-9345-abb43b609ad4(Office.14).aspx)
To archive diagnostic logs for a specific server by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt, type the following command:
Copy-Item <Log folder path> -Destination <Archive folder path> -Recurse
For more information, type Get-Help Copy-Item -Full
.
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Configuring permissions for backup and recovery (SharePoint Foundation 2010)
Published: May 12, 2010
Before backing up or restoring Microsoft SharePoint Foundation 2010, you must ensure that the timer service account, SQL Server service account, and users running the backup or restore operations have the correct permissions or are members of the correct Windows security groups or SharePoint groups.
These permissions and group memberships must be configured initially. Subsequently, they must be updated when new farm components are added to the environment and if you want to add users who will perform backup and restore operations.
In this topic:
-
Permissions for the SPTimerV4 timer service and SQL Server account
The Windows SharePoint Services Timer V4 (SPTimerV4) and the SQL Server service account in SharePoint Foundation 2010 perform backup and restore operations on behalf of the user. These service accounts require Full Control permissions on any backup folders.
-
Group memberships required to run backup and restore operations in Central Administration
You must ensure that all user accounts that will be backing up or restoring your farm and farm components by using Central Administration have the group memberships that are described in the following table.
Required group memberships
Farm component
Member of Administrators group on the local computer
Member of Farm Administrators SharePoint group
Farm
Yes
No
Content Database
Yes
No
Site Collection
No
Yes
Site, list, document library
No
Yes
-
Setting permissions for running backup and restore operations by using Windows PowerShell
You must ensure that all user accounts that will be backing up or restoring your farm and farm components by using Windows PowerShell are added to the SharePoint_Shell_Access role for a specified database and have the permissions described in the table later in this section.
You can run the Add-SPShellAdmin
cmdlet to add a user account to this role. You must run the command for each user account. Moreover, you must run the command for all databases to which you want to grant access.

Note:You only need to grant a user account access to back up and restore a specific farm component one time. You will have to perform this task again only when new farm components are added to your environment or when you want to add users to perform backup and restore operations.
To add a user to or remove a user from the SharePoint_Shell_Access role by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Add-SPShellAdmin -Username <User account> -Database <Database ID>
To add a user account to all the databases in the farm, type the following command, and then press ENTER:
ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username <User account> -Database $db}
To remove a user account from all the databases in the farm, type the following command, and then press ENTER:
ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username <User account> -Database $db}
To view the user accounts currently added to the databases in the farm, type the following command, and then press ENTER:
ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db}
For more information, see Add-SPShellAdmin (http://technet.microsoft.com/library/2ddfad84-7ca8-409e-878b-d09cb35ed4aa(Office.14).aspx)
You might also have to grant additional permissions to the users running the backup or restore operation by using Windows PowerShell. The following table shows the permissions that are required.
Required permissions for Windows PowerShell
|
Farm component |
Member of Administrators group on the local computer |
Member of Farm Administrators SharePoint group |
Full Control on backup folder |
|
Farm |
Yes |
No |
Yes |
|
Content database |
Yes |
No |
Yes |
|
Site collection |
No |
Yes |
Yes |
|
Site, list, document library |
Yes |
No |
Yes |
-
Configuring permissions for backup and recovery (SharePoint Server 2010)
Published: May 12, 2010
Before backing up or restoring Microsoft SharePoint Foundation 2010, you must ensure that the timer service account, SQL Server service account, and users running the backup or restore operations have the correct permissions or are members of the correct Windows security groups or SharePoint groups.
These permissions and group memberships must be configured initially. Subsequently, they must be updated when new farm components are added to the environment and if you want to add users who will perform backup and restore operations.
In this topic:
-
Permissions for the SPTimerV4 timer service and SQL Server account
The Windows SharePoint Services Timer V4 (SPTimerV4) and the SQL Server service account in SharePoint Foundation 2010 perform backup and restore operations on behalf of the user. These service accounts require Full Control permissions on any backup folders.
-
Group memberships required to run backup and restore operations in Central Administration
You must ensure that all user accounts that will be backing up or restoring your farm and farm components by using Central Administration have the group memberships that are described in the following table.
Required group memberships
Farm component
Member of Administrators group on the local computer
Member of Farm Administrators SharePoint group
Farm
Yes
No
Service Application
Yes
No
Content Database
Yes
No
Site Collection
No
Yes
Site, list, document library
No
Yes
-
Setting permissions for running backup and restore operations by using Windows PowerShell
You must ensure that all user accounts that will be backing up or restoring your farm and farm components by using Windows PowerShell are added to the SharePoint_Shell_Access role for a specified database and have the permissions described in the table later in this section.
You can run the Add-SPShellAdmin
cmdlet to add a user account to this role. You must run the command for each user account. Moreover, you must run the command for all databases to which you want to grant access.

Note:You only need to grant a user account access to back up and restore a specific farm component one time. You will have to perform this task again only when new farm components are added to your environment or when you want to add users to perform backup and restore operations.
To add a user to or remove a user from the SharePoint_Shell_Access role by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Add-SPShellAdmin -Username <User account> -Database <Database ID>
To add a user account to all the databases in the farm, type the following command, and then press ENTER:
ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username <User account> -Database $db}
To remove a user account from all the databases in the farm, type the following command, and then press ENTER:
ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username <User account> -Database $db}
To view the user accounts currently added to the databases in the farm, type the following command, and then press ENTER:
ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db}
For more information, see Add-SPShellAdmin (http://technet.microsoft.com/library/2ddfad84-7ca8-409e-878b-d09cb35ed4aa(Office.14).aspx)
You might also have to grant additional permissions to the users running the backup or restore operation by using Windows PowerShell. The following table shows the permissions that are required.
Required permissions for Windows PowerShell
|
Farm component |
Member of Administrators group on the local computer |
Member of Farm Administrators SharePoint group |
Full Control on backup folder |
|
Farm |
Yes |
No |
Yes |
|
Service application |
Yes |
No |
Yes |
|
Content database |
Yes |
No |
Yes |
|
Site collection |
No |
Yes |
Yes |
|
Site, list, document library |
Yes |
No |
Yes |
-
Recovery (SharePoint Foundation 2010)
Published: May 12, 2010
The articles in this section are written to meet the requirements of information technology (IT) professionals who are responsible for the planning, design, deployment, and operations of backup and recovery solutions. These solutions might be in enterprise, corporate, or branch office environments.
The IT professionals who are responsible for backup and recovery solutions are expected to have an understanding of the technical details that are contained in this section. However, service-level expertise is not needed to understand the enterprise-level discussions and decisions.
Before you restore a farm, ensure that the following requirements are met:
- To restore a farm by using the SharePoint Central Administration Web site, you must be a member of the Farm Administrators group.
- To restore a farm by using Windows PowerShell, you must meet the following minimum requirements: See Add-SPShellAdmin.
- The database server’s SQL Server account, the Timer service account, and the Central Administration application pool account must have Read permissions to the backup locations. (The Timer service account and the Central Administration application pool account are usually the same.) The database server’s SQL Server account must be a member of the sysadmin fixed server role.
- Your login account must have Read permissions to the backup locations.
- Ensure that the SharePoint Foundation Administration service is started on all farm servers. By default, this service is not started on stand-alone installations.
Consider the following before you restore a farm:
- Restoring from one version of SharePoint Products and Technologies to a different version is not supported.
- After recovery, search might take as long as 15 minutes to be available again. It can take longer than 15 minutes if the search system has to crawl all the content again. If you back up and restore the complete service, the system does not have to perform a full crawl.
- You can only perform one recovery or one backup operation at a time.
-
Recover all or part of a farm
The following tasks for recovery are performed on the entire farm, farm databases, sites, subsites, or lists:
-
This article describes the procedures that you can use to restore the entire farm from a backup.
-
This article describes the procedures that you can use to restore the farm configuration to the same farm from a backup.
-
This article describes how to use Windows PowerShell to document the configuration settings for your farm. Documenting configuration settings is important both so that you can create scripted deployments for your environment, and so that you can quickly re-create a set of configurations in the event of a failure.
-
This article describes the procedures that you can use to copy configuration settings from one farm to another, including how to back up and recover a farm without the content databases, how to back up and recover configurations only, and how to create a deployment script.
-
This article describes the procedures that you can use to restore a Web application that is associated with the farm, including configuration and content databases, from a backup.
-
This article describes the procedures that you can use to restore a service application that is associated with the farm, including configuration and content databases, from a backup.
-
This article describes the procedures that you can use to restore a content database from a backup.
-
This article describes the procedures that you can use to restore a site collection from a backup.
-
This article describes the procedures that you can use to restore customizations that are associated with the farm from backups.
-
This article describes the procedures that you can use to attach a read-only content database to the farm.
-
This article describes the procedures that you can use to restore a site, list, or document library from a backup.
-
-
Concepts
Backup (SharePoint Foundation 2010)
-
Restore a farm (SharePoint Foundation 2010)
Updated: September 16, 2010
This article describes how to restore a Microsoft SharePoint Foundation 2010 farm. Farm-level recovery is usually performed only after a failure that involves the complete farm, or where partial recovery of part of the farm is not possible. If you only have to restore part of the farm, a specific database, a service application, a list, or document library, or a specific document, use another recovery method. For more information about alternate forms of recovery, see Related content.
Farm recovery is usually performed for any of the following reasons:
- Restoring a farm after a fire, disaster, equipment failure, or other data-loss event.
- Restoring farm configuration settings and data to a specific previous time and date.
- Moving a SharePoint Foundation 2010 deployment from one farm to another farm.
In this article:
-
Considerations when recovering a farm
When you prepare to recover a farm, be aware of the following issues:
- You cannot restore a multiple-server farm to a single-server farm or a single-server farm to a multiple-server farm.
- You cannot back up from one version of Microsoft SharePoint Foundation and restore to another version of SharePoint Foundation.
- Backing up the farm will back up the configuration and Central Administration content databases, but these cannot be restored using Microsoft SharePoint Foundation 2010 tools. For more information about backing up and restoring all the farm databases, see Move all databases (SharePoint Foundation 2010) (http://technet.microsoft.com/library/0aaf3261-f06b-4f4f-96d0-96fecdf78bc6(Office.14).aspx)
- When you restore the farm by using Microsoft SharePoint Foundation 2010, the restore process will not automatically start all of the service applications. You must manually start them by using Central Administration or Windows PowerShell. Do not use SharePoint Products Configuration Wizard to start the services because doing so will also re-provision the services and service proxies.
- The identifier (ID) of each content database is retained when you restore or reattach a database by using built-in tools. Default change log retention behavior when using built-in tools is as follows:
- The change logs for all databases are retained when you restore a farm.
-
The change log for content databases is retained when you reattach or restore a database.
When a database ID and change log are retained, the search system continues crawling based on the regular schedule that is defined by crawl rules.
When you restore an existing database and do not use the overwrite option, a new ID is assigned to the restored database, and the database change log is not preserved. The next crawl of the database will add data from the content database to the index.
If a restore is performed and the ID in the backup package is already being used in the farm, a new ID is assigned to the restored database and a warning is added to the restore log. The ability to perform an incremental crawl instead of a full crawl depends on the content database ID being the same as before and the change log token that is used by the search system being valid for the current change log in the content database. If the change log is not preserved, the token is not valid and the search system has to perform a full crawl.
-
SharePoint Foundation 2010 backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm.
If you restore the Business Data Connectivity service or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might be unable to locate the data source.
-
SharePoint Foundation 2010 restores remote Binary Large Objects (BLOB) stores only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores.
If you are using another provider, you must manually restore the remote BLOB stores.
- If a user has taken copies of content for off-line editing in Microsoft SharePoint Workspace 2010 and the content is restored from a backup on the server, when the user re-connects, the server automatically synchronizes the off-line content with the restored content. This might result in data loss on the user’s copies of the content.
-
If you are sharing service applications across farms, be aware that trust certificates that have been exchanged are not included in farm backups. You must back up your certificate store separately or retain the certificates in a separate location. When you restore a farm that shares a service application, you must import and redeploy the certificates, and then re-establish any inter-farm trusts.
For more information, see Exchange trust certificates between farms (SharePoint Foundation 2010) (http://technet.microsoft.com/library/679d334b-913d-49b3-b086-66a60093b261(Office.14).aspx)
- After a Web application that is configured to use claims-based authentication has been restored, duplicate or additional claims providers are often visible. If duplicates appear, you must then manually save each Web application zone to remove them. For more information, see Restore a Web application (SharePoint Foundation 2010).
- Additional steps are required when you restore a farm that contains a Web application that is configured to use forms-based authentication. For more information, see Restore a Web application (SharePoint Foundation 2010).
-
Use Windows PowerShell to restore a farm
You can use Windows PowerShell to restore a farm.
To restore a farm by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt, type the following command:
|
Restore-SPFarm -Directory <BackupFolder> -RestoreMethod Overwrite [-BackupId <GUID>] |
Where:
- <BackupFolder> is the path of the folder you use for storing backup files.
- <GUID> is the identifier of the backup to restore from.
|
|
|
If you are not logged on as the Farm account, you are prompted for the Farm account’s credentials. |
If you do not specify the BackupId
, the most recent backup will be used. To view the backups for the farm, type the following command:
|
Get-SPBackupHistory -Directory <BackupFolder> -ShowBackup [-Verbose] |
Where:
-
<BackupFolder> is the path of the folder you use for storing backup files.
You cannot use a configuration-only backup to restore content databases together with the configuration.
- To restart a service application, type the following command:
|
Start-SPServiceInstance -Identity <ServiceApplicationID> |
Where:
-
<ServiceApplicationID> is the GUID of the service application.
Start-SPServiceInstance
For more information about restarting service applications by using Windows PowerShell, see Start-SPServiceInstance (http://technet.microsoft.com/library/fcb4a4f8-a95f-468e-918b-d9a2d736cd2d(Office.14).aspx)
For more information about restoring the farm by using Windows PowerShell, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx)
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to restore a farm
You can use the Central Administration Web site to restore a farm.
To restore a farm by using Central Administration
- Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
- On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the farm backup, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.
|
|
|
If the correct backup job does not appear, in the Backup Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore the farm. |
- On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the farm, and then click Next.
-
On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that Farm appears in the Restore the following component list.
In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected.
In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box will appear that asks you to confirm the operation. Click OK.
|
|
|
If the Restore Only Configuration Settings section does not appear, the backup that you selected is a configuration-only backup. You must select another backup. |
Click Start Restore.
-
You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.
- When the restore process has completed, you may need to restart one or more service applications. In Central Administration, on the Home page, in the Application Management section, click Manage services on server.
- On the Services on Server page, start any services related to service applications that you want to run by clicking Start in the Actions column next to the service application.
- Re-establish any trust relationships. For more information, see Exchange trust certificates between farms (SharePoint Foundation 2010) (http://technet.microsoft.com/library/679d334b-913d-49b3-b086-66a60093b261(Office.14).aspx).
-
Use SQL Server tools to restore a farm
Although you cannot restore the complete farm by using SQL Server tools, you can restore most of the farm databases. If you restore the databases by using SQL Server tools, you must restore the farm configuration by using Central Administration or Windows PowerShell. For more information about how to restore the farm’s configuration settings, see Restore a farm configuration (SharePoint Foundation 2010).

Note:The search index is not stored in SQL Server. If you use SQL Server tools to back up and restore search, you must perform a full crawl after you restore the content database.
Before you restore SharePoint Foundation 2010, we recommend that you configure a recovery farm for site and item recovery.
Restore the databases by following these steps:
- If possible, back up the live transaction log of the current database to protect any changes that were made after the last full backup.
- Restore the last full database backup.
- Restore the most recent differential database backup that occurred after the most recent full database backup.
- Restore all transaction log backups that occurred after the most recent full or differential database backup.
To restore a farm by using SQL Server tools
- Verify that the user account that is performing this procedure is a member of the sysadmin fixed server role.
- If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore all the databases that you have to restore.
- Start SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
-
Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.
The database is automatically taken offline during the recovery operation and cannot be accessed by other processes.
-
In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.
The default values for destination and source are appropriate for most recovery scenarios.
- In the Select a page pane, click Options.
- In the Restore options section, select only Overwrite the existing database. Unless your environment or policies require otherwise, do not select the other options in this section.
- In the Recovery state section:
- If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY.
- If you must restore additional transaction logs, select RECOVER WITH NORECOVERY.
- The third option, RECOVER WITH STANDBY is not used in this scenario.
|
|
|
For more information about these recovery options, see Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420). |
- Click OK to complete the recovery operation.
- Except for the configuration database, repeat steps 4 through 9 for each database that you are restoring.
- To restore the configuration settings, you must use the existing configuration database or manually create a new database and restore the configuration to that database. For more information about restoring the farm configuration, see Restore a farm configuration (SharePoint Foundation 2010).
- Start the Windows SharePoint Services Timer service.
-
Related content
-
Restore a farm configuration (SharePoint Foundation 2010)
Published: May 12, 2010
This topic describes how to a restore the configuration of a farm.

Note:In previous versions of Microsoft SharePoint Foundation 2010, you could not restore the configuration database and, therefore, you could not restore the configuration of a farm. In this version of SharePoint Foundation 2010, you do not have to restore the configuration database because you can restore the farm configuration directly.
Procedures in this task:
-
Overview
Farm-level configuration recovery is performed only after a failure that involves the configuration database but does not involve other farm data, such as a content database or Web application. If restoring the farm configuration does not solve the problems, you must restore the complete farm.
For more information about restoring the complete farm, see Restore a farm (SharePoint Foundation 2010).
You can restore the configuration from a farm backup that used either the Backup content and configuration settings option or the Backup only configuration settings option.
-
Use Windows PowerShell to restore a farm’s configuration
You can use Windows PowerShell to restore a farm’s configuration.
To restore a farm’s configuration by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
From the Windows PowerShell command prompt (that is, PS C:\>), type the following command and press ENTER:
Restore-SPFarm -Directory <RestoreShare> -RestoreMethod Overwrite -ConfigurationOnly
You must use the ConfigurationOnly
parameter. To view the progress of the operation, use the Verbose
parameter.
For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx)
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to restore a farm’s configuration
You can use Central Administration to restore a farm’s configuration.
To restore a farm’s configuration by using Central Administration
- Ensure that you are a member of the Farm Administrators SharePoint group on the computer that is running Central Administration and a member of the sysadmin fixed server role on the database server where each database is stored.
- In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
- On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, select the backup job that contains the farm backup from the list of backups, and then click Next.
|
|
|
You can view additional information about the backups by expanding the row that contains the backup. |
|
|
|
If the correct backup job does not appear, in the Backup Directory Location text box, enter the UNC path of the correct backup folder, and then click Refresh. |
- On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the farm, and then click Next.
-
On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that “Farm” appears in the Restore the following content list.
In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected.
In the Restore Options section, select the Type of Restore option. Use the Same configuration setting. A dialog box will appear that asks you to confirm the operation. Click OK.
|
|
|
If the Restore Only Configuration Settings section does not appear, then the backup that you selected is a configuration-only backup. |
Click Start Restore.
-
You can view the general status of all recovery jobs at the top of the Backup and Restore Status page in the Readiness section. You can view the status of the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 2.
-
Use SQL Server to restore a farm’s configuration
You cannot restore a farm’s configuration by using SQL Server tools.
-
Concepts
Back up a farm configuration (SharePoint Foundation 2010)
-
Document farm configuration settings (SharePoint Foundation 2010)
Published: May 12, 2010
This article describes how to use Windows PowerShell 2.0 to document the configuration settings for your farm. Documenting configuration settings is important both so that you can create scripted deployments for your environment, and so that you can quickly re-create a set of configurations in the event of a failure.
To document configuration settings by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- Using Notepad, create a text file and then copy and paste the following script into the file. The commands in the example create XML files that document the configurations of the Web applications and service applications in the current farm. Choose only those commands that are relevant to your environment.
|
## #Retrieve custom layout information. #Determine how SharePoint designer access is configured #Retrieve information about alternate access mapping #Retrieve information about content databases #Retrieve database properties for each database #Retrieve information about all SharePoint Products installed in the farm, and the versions of all updates installed for each product. #Retrieve farm information #Retrieve information about the servers in the farm #Retrieve information about installed features #Retrieve information about globally-installed site templates #Retrieve information about deployed solutions #Retrieve information about sandboxed solutions deployed in a site collection #Retrieve information about installed Help #Retrieve information about the logging levels that have been set #Retrieve information about the sites in the farm #Retrieve ULS logging information #Retrieve information about accounts registered in the configuration database #Retrieve information about the Mobile Messaging account. ## #Retrieve information about the services running in the farm #Retrieve information about common Web service settings ## #Application Discovery and Load Balancer Service Application #Business Data Connectivity Service #Security Token Service Application #Usage and Health data collection ###Note: These cmdlets are commented out because you are unlikely to want to run them. ### # Get-SPSite | %{$web=Get-SPWeb $_.Url;$webid=$web.Id;$web | Export-Clixml .\Get-SPWeb-$webid.xml} |
- To run the script, in the Windows PowerShell console, at the command prompt (that is, PS C:\>), type the following command and press ENTER:C:\<path>\<filename>.ps1
For more information, see Export-Clixml (http://technet.microsoft.com/en-us/library/dd347657.aspx) Get-SPWebApplication (http://technet.microsoft.com/library/11d6521f-f99c-433e-9ab5-7cf9e953457a(Office.14).aspx), Get-SPServiceApplication (http://technet.microsoft.com/library/71a467dc-3b95-4b65-af93-0d0d6ebb8326(Office.14).aspx).
-
Example of using a cmdlet
This section provides an example of ways that you can use one of the recommended cmdlets.
The Get-SPAlternateURL cmdlet provides information about alternate access mapping. Piping the cmdlet to the Export-Clixml cmdlet writes the information to an XML file.
Get-SPAlternateURL | Export-Clixml .\Get-SPAlternateURL.xml
The following section lists the content of the Get-SPAlternateURL.xml file. Some sections are collapsed.
– <Objs Version=”1.1.0.1″ xmlns=”http://schemas.microsoft.com/powershell/2004/04″>
+ <Obj RefId=”0″>
– <Obj RefId=”7″>
<TNRef RefId=”0″ />
<ToString>Microsoft.SharePoint.Administration.SPAlternateUrl</ToString>
– <Props>
<S N=”IncomingUrl”>http://servername</S>
<URI N=”Uri”>http://servername/</URI>
+ <Obj N=”UrlZone” RefId=”8″>
– <Obj N=”Collection” RefId=”9″>
<TNRef RefId=”2″ />
– <IE>
– <Obj RefId=”10″>
<TNRef RefId=”0″ />
<ToString>Microsoft.SharePoint.Administration.SPAlternateUrl</ToString>
+ <Props>
– <MS>
<S N=”Zone”>Default</S>
<S N=”PublicUrl”>http://servername</S>
</MS>
</Obj>
</IE>
– <Props>
<I32 N=”Count”>1</I32>
<B N=”IsReadOnly”>false</B>
<S N=”TypeName”>Alternate Access Mapping Collection</S>
<S N=”DisplayName”>SharePoint – 80</S>
<U64 N=”DiskSizeRequired”>0</U64>
<B N=”CanSelectForBackup”>false</B>
<B N=”CanRenameOnRestore”>false</B>
<B N=”CanSelectForRestore”>false</B>
<S N=”Name”>SharePoint – 80</S>
<G N=”Id”>5b65a69a-222d-4fe0-904b-0fb928bc7a89</G>
<S N=”Status”>Online</S>
<S N=”Parent”>SPFarm Name=SERVERNAME_SharePoint_Configuration_Database</S>
<I64 N=”Version”>3661</I64>
+ <Obj N=”Properties” RefId=”12″>
<TNRef RefId=”3″ />
<DCT />
</Obj>
<S N=”Farm”>SPFarm Name=SERVERNAME_SharePoint_Configuration_Database</S>
<Ref N=”UpgradedPersistedProperties” RefId=”11″ />
</Props>
</Obj>
<Ref N=”UpgradedPersistedProperties” RefId=”11″ />
</Props>
+ <MS>
+ <Obj N=”Zone” RefId=”13″>
<TNRef RefId=”1″ />
<ToString>Default</ToString>
<I32>0</I32>
</Obj>
<S N=”PublicUrl”>http://servername</S>
</MS>
</Obj>
</Objs>This example imports the output from the XML file, so that you can see its contents more easily.
Import-Clixml .\Get-SPAlternateURL.xml
Once an XML file is imported, you can use the objects in the pipeline as though they were real objects of the given type.
Import-Clixml .\Get-SPAlternateURL.xml | %{$_.Uri}
You can also pipe the objects as part of the cmdlet, and view all of the expected properties, methods, and TypeNames. The following example pipes URIs.
Import-Clixml .\Get-SPAlternateURL.xml | %{$_.Uri | Get-Member}
For more information, see Export-Clixml (http://technet.microsoft.com/en-us/library/dd347657.aspx), Import-Clixml (http://technet.microsoft.com/en-us/library/dd315355.aspx), Get-SPAlternateURL (http://technet.microsoft.com/library/ea38119d-a535-48a3-b498-9daa443399fb(Office.14).aspx), ForEach-Object (http://technet.microsoft.com/en-us/library/dd347608.aspx), Get-Member (http://technet.microsoft.com/en-us/library/dd315351.aspx).
-
Copy configuration settings from one farm to another (SharePoint Foundation 2010)
Published: May 12, 2010
This article describes how to copy configuration settings from one Microsoft SharePoint Foundation 2010 farm to another SharePoint Foundation 2010 farm. Copying the configuration settings of one farm to another can be useful in the following circumstances:
- Setting up similar development, test, and production environments.
- Establishing an organization standard for farm configuration settings.
- Setting up a disaster recovery environment.
In this article:
- Back up and recover a farm without content databases to copy configuration settings
- Back up and recover configuration settings only
- Create a scripted deployment to copy configuration settings
There are many ways in which you can copy configurations from one farm to another. Determine which method to use based on the configuration settings that you want to copy and how often you need to copy them.
- Back up and recover a farm without the content databases attached. This method provides you with farm settings and Web application settings, in addition to the settings for any service applications that you select.
- Back up and recover configurations only. This method provides you with the core SharePoint Foundation 2010 settings only.

Note:This method does not include Web application or service application settings. If Web application settings are required in the recovered farm, use one of the other methods.
- Create a deployment script, based on your documented configuration. This method may be more work initially, but is easy to use to maintain standardization.
-
Back up and recover a farm without content databases to copy configuration settings
To copy configuration settings by using a farm backup, we recommend that you first detach the content databases from the farm. This is not a step that we recommend that you take with a live production farm.

Note:Creating a farm backup without content databases does back up the service applications.
To back up and recover a farm without content databases by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt, type the following command to document the current Web application URLs and content database mappings.
|
Get-SPWebApplication | %{$_.Name;$_.Url;%{$_.ContentDatabases|%{$_.Name};Write-Host “”}} |
- Either dismount all content databases, as in the following example:
|
Get-SPContentDatabase | Dismount-SPContentDatabase |
Or dismount a specific content database, as in the following example:
|
Get-SPContentDatabase WSS_Content | Dismount-SPContentDatabase |
- Back up the farm.
|
Backup-SPFarm -Directory \\servername\share -BackupMethod Full |
|
|
|
You can view the progress of the backup by looking at the \\servername\share\spbr####\spbackup.log file. |
- After the backup is complete, re-mount the content databases. Replace <WSS_Content> and <http://servername> with each of the mappings documented in step 5).
|
Mount-SPContentDatabase -Name <WSS_Content> -WebApplication <http://servername> |
-
Back up and recover configuration settings only
As part of farm backup, you can choose to back up only configuration settings. A configuration-only backup extracts and backs up many, but not all, configuration settings from a configuration database. By using built-in tools, you can back up the configuration of any configuration database, whether it is currently attached to a farm or not. For detailed information about how to back up a configuration, see Back up a farm configuration (SharePoint Foundation 2010) .A configuration backup can be restored to the same — or any other — server farm. When a configuration is restored, it will overwrite any settings present in the farm that have values that are set within the configuration backup. If any settings present in the farm are not contained in the configuration backup, they will not be overwritten. For detailed information about how to restore a farm configuration, see Restore a farm configuration (SharePoint Foundation 2010).
-
Create a scripted deployment to copy configuration settings
When you create a scripted deployment of SharePoint Foundation 2010, you are creating copies of configuration settings.
-
Restore a Web application (SharePoint Foundation 2010)
Updated: January 20, 2011
This article describes how to restore a Web application. When you restore a Web application, you also restore the Internet Information Services (IIS) settings and all content databases that are associated with the Web application.
In this article:
- Considerations when restoring a Web application
- Use Windows PowerShell to restore a Web application
- Use Central Administration to restore a Web application
- Use SQL Server tools to restore databases associated with a Web application
- Additional steps to restore a Web application that uses forms-based authentication
- Additional steps to remove duplicate claims providers after restoring a Web application that uses claims-based authentication
-
Considerations when restoring a Web application
Consider the following information as you prepare to restore a Web application:
- You can only restore one Web application at a time by using the procedures in this article. However, you can simultaneously restore all the Web applications in the farm by restoring the complete farm.
- You cannot use SQL Server tools to restore a Web application.
- When you restore a Web application that is configured to use claims-based authentication, there are additional steps that you must follow after restoring the Web application to restore claims-based authentication.
-
Use Windows PowerShell to restore a Web application
You can use Windows PowerShell to restore a Web application manually or as part of a script that can be run at scheduled intervals.
To restore a Web application by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt, type the following command:
|
Restore-SPFarm -Directory <BackupFolderName> -RestoreMethod Overwrite -Item <WebApplicationName> [-BackupId <GUID>] [-Verbose] |
Where:
- <BackupFolderName> is the full path to the folder you use for backup files.
- <WebApplicationName> is the name of the Web application that was backed up.
-
<GUID> is the identifier of the back up to use for the restore operation.
If you do not specify the value of the BackupID
parameter, the most recent backup will be used. You cannot restore a Web application by using a configuration-only backup. You can view the backups for the farm by typing the following:
|
Get-SPBackupHistory -Directory <BackupFolderName> -ShowBackup |
For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to restore a Web application
You can use Central Administration to restore a Web application.
To restore a Web application by using Central Administration
- Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service and the Farm Database Access account have Full Control permissions on the backup folder.
- In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
- On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the farm or Web application backup, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.
|
|
|
If the correct backup job does not appear, in the Current Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore the Web application. |
- On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the Web application, and then click Next.
-
On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\<Web application> appears in the Restore the following content list.
In the Restore Only Configuration Settings section, make sure that the Restore content and configuration settings option is selected.
In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK.
|
|
|
If the Restore Only Configuration Settings section does not appear, the backup that you selected is a configuration-only backup. You must select another backup. |
Click Start Restore.
-
You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified.
-
Use SQL Server tools to restore databases associated with a Web application
You cannot restore the complete Web application by using SQL Server tools. However, you can restore all the databases that are associated with the Web application. To restore the complete Web application, use either Windows PowerShell or Central Administration.
To restore databases associated with a Web application by using SQL Server tools
- Verify that the user account performing this procedure is a member of the sysadmin fixed server role.
- If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore the databases.
- Start SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
-
Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.
The database is automatically taken offline during the recovery operation and cannot be accessed by other processes.
-
In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.
The default values for destination and source are appropriate for most recovery scenarios.
- In the Select a page pane, click Options.
- In the Restore options section, select only Overwrite the existing database. Unless the environment or policies require otherwise, do not select the other options in this section.
- In the Recovery state section:
- If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY.
- If you must restore additional transaction logs, select RECOVER WITH NORECOVERY.
- The third option, RECOVER WITH STANDBY is not used in this scenario.
|
|
|
For more information about these recovery options, see Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420). |
- Click OK to complete the recovery operation.
- Repeat steps 4 through 10 for each database that you are restoring.
- Start the Windows SharePoint Services Timer service.
-
Additional steps to restore a Web application that uses forms-based authentication
After you restore a Web application that uses forms-based authentication, you must perform the following steps to reconfigure the Web application to use forms-based authentication.
- Re-register the membership and role providers in the Web.config file.
- Redeploy the providers.
For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/f7b57d4b-87d7-41e6-9e55-350d6ad41894(Office.14).aspx).
-
Additional steps to remove duplicate claims providers after restoring a Web application that uses claims-based authentication
After a Web application that is configured to use claims-based authentication has been restored, duplicate or additional claims providers are often visible. You must use the following process to remove the duplicate providers:
- In Central Administration, click Manage Web application, select a Web application that uses claims-based authentication, and then click Authentication Providers.
- Select a zone that the Web application is associated with to open the Edit Authentication page, and then click Save.
- Repeat for each zone, and then for each Web application that uses claims-based authentication.
-
Related content
-
Restore a service application (SharePoint Foundation 2010)
Updated: July 8, 2010
There are situations in which you might have to restore a specific service application instead of restoring the complete farm. Some service applications — for example, the Business Data Connectivity service application — provide data to other services and sites. As a result, users might experience some service interruption until the recovery process is finished.
For information about how to simultaneously restore all the service applications in a farm, see Restore a farm (SharePoint Foundation 2010).

Important:You cannot back up from one version of Microsoft SharePoint Foundation and restore to another version of SharePoint Foundation.

Note:SharePoint Foundation 2010 backs up the Business Data Connectivity Service metadata store, which includes external content types, external systems, and BDC models. For more information, see Business Data Connectivity service administration (SharePoint Foundation 2010) (http://technet.microsoft.com/library/203a1cbd-49d9-49cb-be83-598753e8b07e(Office.14).aspx). Note that this does not back up the external data sources. To protect the data, the external data sources must be backed up.
If you restore the service application or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity Service might not be able to locate the data source.

Note:SharePoint Foundation 2010 restores remote Binary Large Object (BLOB) stores but only if you are using the FILESTREAM provider to put data in remote BLOB stores.
If you are using another provider, you must manually restore remote BLOB stores.
Procedures in this article:
- Use Windows PowerShell to restore a service application
- Use Central Administration to restore a service application
- Use SQL Server tools to restore the databases for a service application

Note:You cannot restore the complete service application but you can restore the databases associated with the service application.
-
Use Windows PowerShell to restore a service application
You can use Windows PowerShell to restore a service application.
To restore a service application by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt, type the following command:
Restore-SPFarm -Directory <BackupFolder> -Item <ServiceApplicationName> -RecoveryMethod Overwrite [-BackupId <GUID>] [-Verbose]
To specify which backup to use, use the BackupId
parameter. You can view the backups for the farm by typing the following: Get-SPBackupHistory -Directory <Backup folder> -ShowBackup
. If you do not specify the BackupId
, the most recent backup will be used. You cannot restore a service application from a configuration-only backup.
For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to restore a service application
Use the following procedure to restore a service application by using the SharePoint Central Administration Web site.
To restore a service application by using Central Administration
- Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
- On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, select the backup job that contains the service application backup, or a farm-level backup, from the list of backups, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.
|
|
|
If the correct backup job does not appear, in the Backup Directory Location text box, type the path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore the farm. |
- On the Restore from Backup — Step 2 of 3: Select Component to Restore page, expand Shared Services Applications, select the check box that is next to the service application, and then click Next.
-
On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\Shared Services Applications\<Service application> appears in the Restore the following component list.
In the Restore Options section, under Type of restore, select the Same configuration option. A dialog box will appear that asks you to confirm the operation. Click OK.
Click Start Restore.
-
You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically.
You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take a several seconds for the recovery to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.
-
Use SQL Server tools to restore the databases for a service application
You cannot restore the complete service application by using SQL Server tools. However, you can use SQL Server tools to restore the databases that are associated with the service application. To restore the complete service application, use either Windows PowerShell or Central Administration.
To restore the databases for a service application by using SQL Server tools
- Verify that the user account that you are using to restore the databases is a member of the SQL Server sysadmin fixed server role on the database server where each database is stored.
- Open SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
- Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.
- In the Restore Database dialog box, on the General page, select the database to restore to from the To database drop-down list.
- Select the restore source from the From database drop-down list.
- In the Select the backup sets to restore section area, select the check box next to the database.
-
On the Options tab, select the recovery state from the Recover state section.
For more information about which recovery type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396) in SQL Server Books Online.
- Click OK to restore the database.
- Repeat steps 1-9 for each database that is associated with the service application.
-
Restore a site collection (SharePoint Foundation 2010)
Updated: June 24, 2010
You can use only Windows PowerShell to restore a site collection.
-
Use Windows PowerShell to restore a site collection
You can use Windows PowerShell to restore a site collection manually or as part of a script that can be run at scheduled intervals.

Note:If a user has taken copies of content for off-line editing in Microsoft SharePoint Workspace 2010 and the content is restored from a backup on the server, when the user re-connects, the server automatically synchronizes the off-line content with the restored content. This might result in data loss on the user’s copies of the content.
To restore a site collection by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin. Additionally, verify that the user account performing this procedure has read permissions to the backup folder and is a member of the db_owner fixed database role on both the farm configuration database and the content database where the site collection is being restored.
- On the Start menu, click Administrative Tools.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Restore-SPSite -Identity <Site collection URL> -Path <Backup file> [-DatabaseServer <Database server name>] [-DatabaseName <Content database name>] [-HostHeader <Host header>] [-Force] [-GradualDelete] [-Verbose]
If you want to restore the site collection to a specific content database, use the DatabaseServer
and DatabaseName
parameters to specify the content database. If you do not specify a content database, the site collection will be restored to a content database chosen by Microsoft SharePoint Foundation 2010.
If you are restoring a host-named site collection, use the Identity
parameter to specify the URL of the host-named site collection and use the HostHeader
parameter to specify the URL of the Web application that will hold the host-named site collection.
If you want to overwrite an existing site collection, use the Force
parameter.
|
|
|
If the site collection that you are restoring is 1 gigabyte or larger, you can use the GradualDelete parameter for better performance during the restore process. When this parameter is used, the site collection that is overwritten is marked as deleted, which immediately prevents any additional access to its content. The data in the marked site collection is then deleted gradually over time by a timer job instead of all at the same time, which reduces the impact on server performance. |
For more information, see Restore-SPSite (http://technet.microsoft.com/library/90f19a58-0455-470c-a8ee-3129fc341f62(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Concepts
Back up a site collection (SharePoint Foundation 2010)
-
Restore customizations (SharePoint Foundation 2010)
Updated: August 12, 2010
This article describes how to restore customizations that have been made to sites in a Microsoft SharePoint Foundation farm.
This article assumes that you are familiar with the concepts and procedures in Back up customizations (SharePoint Foundation 2010).
In this article:
-
Restoring solution packages
The method that you use to restore solution packages is determined by whether the customizations were deployed as trusted solutions or sandboxed solutions.
Trusted solutions are solutions that farm administrators deploy. They are deployed to the entire farm, and can be used on any site within the farm. Trusted solutions are stored in the configuration database. Trusted solutions are backed up when a farm is backed up by using SharePoint Foundation 2010 backup, and are included in configuration-only backups, and can also be backed up as a group, or individually. They are visible in the restore hierarchy.
Sandboxed solutions are solutions that site collection administrators can deploy to a single site collection. Sandboxed solutions are stored in the content database associated with the site collection that they are deployed to. They are included in SharePoint Foundation 2010 farm, Web application, content database, and site collection backups, but are not visible in the restore hierarchy, and cannot be selected or restored individually.
We recommend that you keep a backup of the original .wsp file as well as the source code used to build the .wsp file for both trusted and sandboxed solutions.
To restore a trusted solution by using Central Administration
- Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
- On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the solution package, and then click Next. You can view more details about each backup by clicking the (+) next to the backup.
|
|
|
If the correct backup job does not appear, in the Backup Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh. |
- On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the solution, and then click Next.
-
On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that Solution appears in the Restore the following component list.
In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected.
In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK.
Click Start Restore.
-
You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.
To restore a trusted solution by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
- At the Windows PowerShell command prompt, type the following command:
|
Restore-SPFarm -Directory <BackupFolder> -RestoreMethod Overwrite -BackupId <GUID> -Item <SolutionPath> |
Where:
- <BackupFolder> is the UNC location of the directory that you want to restore from.
- <GUID> is the GUID of the backup ID that you want to restore from. If you do not specify a backup, the most recent one is used.
- <SolutionPath> is the path of the solution within the backup tree (usually farm\solutions\SolutionName).
For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
Restoring a sandboxed solution
You cannot restore only customizations that were deployed as sandboxed solutions. Instead, you must restore the farm, Web application, content database, or site collection with which the customization is associated. For more information about these methods of restoring, see Related content later in this article.
-
Restoring authored site elements
You cannot restore only authored site elements. Instead, you must restore the farm, Web application, or content database with which the authored site element is associated. For more information about these methods of backing up, see Related content.
-
Restoring workflows
Workflows are a special case of customizations that you can restore. Make sure that the backup and recovery plan includes any of the following scenarios that apply to the environment:
- Declarative workflows, such as those created in Microsoft SharePoint Designer 2010, are stored in the content database for the site collection to which they are they are deployed. Restoring the content database or site collection restores these workflows.
- Custom declarative workflow actions have components in the following three locations:
- The Microsoft Visual Studio 2010 assemblies for the actions are stored in the global assembly cache (GAC).
- The XML definition files (.actions files) are stored in the 14\TEMPLATE\<LCID>\Workflow directory.
-
An XML entry to mark the action as an authorized type is stored in the Web.config file for the Web applications in which it is used.
If the farm workflows use custom actions, you should use a file restore system to restore these files and XML entries. You can reapply the files as needed after recovery.
- Workflows that depend on custom code, such as those that are created by using Visual Studio 2010, are stored in two locations. The Visual Studio 2010 assemblies for the workflow are stored in the GAC, and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Foundation features such as Web Parts and event receivers. If the workflow was installed as part of a solution package, follow the instructions for restoring solution packages.
- If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must restore both site collections to recover the workflow. Restoring a farm is sufficient to recover all site collections in the farm and all workflows that are associated with them.
- Workflows that have not been deployed must be restored separately by using a file system backup application.
-
Restoring changes to the Web.config file
You can recover changes to the Web.config file made by using Central Administration or the SharePoint Foundation 2010 APIs and object model by performing a farm or configuration-only restore. You should use a file system backup to protect changes to the Web.config file that are not made by using Central Administration or the SharePoint APIs and object model. You can recover the backup by using a file system restore.
-
Recovering changes made by direct editing
Changes made directly to a site by directly editing through the browser can be difficult to recover. The following table describes recovery strategies for specific objects.
Edited object
Backup strategy
List
If you have used SharePoint Designer 2010 to save as a template, you can deploy and activate the template. For more information, see Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkID=199515).
Site
If you have used SharePoint Designer 2010 to save as a template, you can deploy and activate the template. For more information, see Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkID=199515).
Site collection
Use site collection recovery. For more information, see Restore a site collection (SharePoint Foundation 2010).
-
Restoring developed customizations that are not packaged as solutions
Restoring developed customizations that are not packaged as solutions can be a complex process because the customization file locations are not standardized.
Consult with the development team or customization vendor to determine whether the customizations involve additional add-in software or files in other locations. We recommend that you restore directories with a file system restore solution. The following table lists locations where customizations are typically stored on Web servers.
Location
Description
%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14
Commonly updated files, custom assemblies, custom templates, custom site definitions
Inetpub
Location of IIS virtual directories
%WINDIR%\Assembly
Global assembly cache (GAC): a protected operating system location where the Microsoft .NET Framework code assemblies are installed to provide full system access
-
Related content
-
Restore a content database (SharePoint Foundation 2010)
Updated: June 24, 2010
You can restore any content database or several content databases, one at a time. For information about how to back up all the content databases in a farm at the same time, see Back up a farm (SharePoint Foundation 2010).

Note:SharePoint Foundation 2010 restores up remote Binary Large Objects (BLOB) stores but only if you are using the SQL Filestream remote BLOB store provider to place data in remote BLOB stores.
If you are using another provider you must manually restore these remote BLOB stores.

Note:If a user has taken copies of content for off-line editing in Microsoft SharePoint Workspace 2010 and the content is restored from a backup on the server, when the user re-connects, the server automatically synchronizes the off-line content with the restored content. This might result in data loss on the user’s copies of the content.
Procedures in this task:
-
Use Windows PowerShell to restore a content database
You can use Windows PowerShell to restore a content database.
To restore a content database by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Restore-SPFarm -Directory <Backup folder name> -RestoreMethod Overwrite -Item <Content database name> [-BackupId <GUID>] [-Verbose]
|
|
|
If you are not logged on as the Farm account, you are prompted for the Farm account’s credentials. |
If you do not use the BackupId
parameter, the most recent backup will be used. To view a list of the backups, including their Backup IDs, type the following command, and then press ENTER:
Get-SPBackupHistory -Directory <Backup folder>
For more information, see Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Use Central Administration to restore a content database
You can use Central Administration to restore a farm or components of a farm.
To restore a content database by using Central Administration
- Verify that you are logged on as a member of the Farm Administrators group.
- In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup.
- On the Restore from Backup — Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the content database backup, and then click Next.
|
|
|
If the correct backup job does not appear, in the Current Directory Location text box, enter the path of the correct backup folder, and then click Refresh. |
- On the Restore from Backup — Step 2 of 3: Select Component to Restore page, select the check box that is next to the content database, and then click Next.
|
|
|
If the content database is not selectable, you must use Windows PowerShell or SQL Server tools to restore the content database. |
-
On the Restore from Backup — Step 3 of 3: Select Restore Options page, in the Restore Options section, under Type of Restore, click the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK.
Click Start Restore.
-
You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.
If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 2.
-
Use SQL Server tools to restore a content database
You can use SQL Server tools to restore a content database by following these steps:
- If possible, back up the live transaction log of the content database to protect any changes that were made after the last full backup.
- Restore the last full database backup.
- Restore the most recent differential database backup that occurred after the most recent full database backup.
- Restore all transaction log backups that occurred after the most recent full or differential database backup.
To restore a content database by using SQL Server tools
- Verify that the user account performing this procedure is a member of the sysadmin fixed server role.
- If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore the content databases.
- Start SQL Server Management Studio and connect to the database server.
- In Object Explorer, expand Databases.
-
Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.
The database is automatically taken offline during the recovery operation and cannot be accessed by other processes.
-
In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.
The default values for destination and source are appropriate for most recovery scenarios.
- In the Select a page pane, click Options.
- In the Restore options section, select only Overwrite the existing database. Unless the environment or policies require otherwise, do not select the other options in this section.
- In the Recovery state section:
- If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY.
- If you must restore additional transaction logs, select RECOVER WITH NORECOVERY.
- The third option, RECOVER WITH STANDBY is not used in this scenario.
|
|
|
For more information about these recovery options, see Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420). |
- Click OK to complete the recovery operation.
- Repeat steps 4 through 10 for each database that you are restoring.
- Start the Windows SharePoint Services Timer service.
-
Concepts
Back up a content database (SharePoint Foundation 2010)
-
Attach and restore a read-only content database (SharePoint Foundation 2010)
Published: May 12, 2010
A Microsoft SharePoint Foundation 2010 farm in which content databases have been set to be read-only can be part of a failure recovery environment that runs against mirrored or log-shipped content databases or part of a highly available maintenance or patching environment that provides user access when another version of the farm is being updated. When you re-attach the read-only databases, they become read-write.
For more information about how to use read-only databases, see Run a farm that uses read-only content databases (Windows SharePoint Services “14”) (http://technet.microsoft.com/library/db27f4ab-af50-4400-ad9a-5092868a5398(Office.14).aspx).
-
Use Windows PowerShell to attach and restore a read-only content database
You can use only Windows PowerShell to attach and restore a read-only content database.
To attach and restore a read-only content database by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Mount-SPContentDatabase -Name <Database name> -WebApplication <Web application ID> [-Verbose]
|
|
|
Attaching a content database by using the Mount-SPContentDatabase cmdlet differs from attaching a database in SQL Server by using SQL Server tools. Mount-SPContentDatabase associates the content database with a Web application so that the contents can be read. |
For more information, see Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Concepts
Recovery (SharePoint Foundation 2010)
-
Import a list or document library (SharePoint Foundation 2010)
Published: May 12, 2010
Although you can use either Windows PowerShell or Central Administration to export a site, list, or document library, you can use only Windows PowerShell to import a site, list, or document library. For information about how to export lists or libraries, see Export a site, list, or document library (SharePoint Foundation 2010).
You can use importing as a method of restoring the items, or as a method of moving or copying the items from one farm to another farm. You can import a site, list, or document library from a backup of the current farm, from a backup of another farm, or from a read-only content database. To import from a read-only content database, you must first attach the read-only database. For more information, see Attach and restore a read-only content database (SharePoint Foundation 2010).

Important:You cannot import a site, list or document library exported from one version of Microsoft SharePoint Foundation to another version of SharePoint Foundation.
-
Import a site, list or document library
You can use Windows PowerShell to manually import a site, list, or document library or as part of a script that can be run at regular intervals.
To import a site, list or document library by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER:
Import-SPWeb -Identity <Site URL> -Path <Export file name> [-Force] [-NoFileCompression] [-Verbose]
|
|
|
The site or subsite that you are importing must have a template that matches the template of the site specified by Identity . |
You can also use the Get-SPWeb
cmdlet and pass the ID to Import-SPWeb
by using the Windows PowerShell pipeline. The value of the Path
parameter specifies the path and file name of the file from which to import the list or library. To include the user security settings with the list or document library, use the IncludeUserSecurity
parameter. To overwrite the list or library that you specified, use the Force
parameter. You can use the UpdateVersions
parameter to specify how versioning conflicts will be handled. To view the progress of the operation, use the Verbose
parameter.
The NoFileCompression
parameter lets you specify that no file compression is performed during the import process. Using this parameter can lower resource usage up to 30% during the export and import process. If you are importing a site, list, or document library that you exported from Central Administration, or if you exported a site, list, or document library by using Windows PowerShell and you did not use the NoFileCompression
parameter in the Export-SPWeb
cmdlet, you cannot use this parameter in the Import-SPWeb
cmdlet.
|
|
|
There is no facility in the Import-SPWeb cmdlet import a subset of the items in the export file. Therefore, the import operation will import everything from the file. |
For more information, see Import-SPWeb (http://technet.microsoft.com/library/2ecc5b6e-1b23-4367-a966-b7bd3377db3a(Office.14).aspx).
|
|
|
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. |
-
Concepts
Export a site, list, or document library (SharePoint Foundation 2010)
-
Availability configuration (SharePoint Foundation 2010)
Published: May 12, 2010
This section describes how to configure availability for Microsoft SharePoint Foundation 2010. The articles assume that you are familiar with the concepts and terms presented in Plan for availability (SharePoint Foundation 2010).
In this section:
-
This article describes how to use SQL Server clustering with SharePoint Foundation 2010.
-
This article describes how to configure SQL Server database mirroring for use with SharePoint Foundation 2010.
-
This article provides a script to use in configuring SQL Server database mirroring for use with SharePoint Foundation 2010 in a test environment. In a production environment, we recommend that a database professional configure mirroring.
-
-
Concepts
Plan for availability (SharePoint Foundation 2010)
-
Configure availability by using SQL Server clustering (SharePoint Foundation 2010)
Published: May 12, 2010
Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2 failover clustering can be used to configure availability within a farm for Microsoft SharePoint Foundation 2010. This article assumes that you are familiar with the concepts and terms presented in Plan for availability (SharePoint Foundation 2010).
Failover clustering provides availability support for an instance of SQL Server 2008 with SP1 and Cumulative Update 2. A failover cluster is a combination of one or more nodes or servers and two or more shared disks. A failover cluster instance appears as a single computer, but has functionality that provides failover from one node to another if the current node becomes unavailable.
SharePoint Foundation 2010 references the cluster as a whole; therefore, failover is automatic and seamless from the perspective of SharePoint Foundation 2010.
For detailed information about failover clustering, see Getting Started with SQL Server 2008 Failover Clustering (http://go.microsoft.com/fwlink/?LinkID=102837&clcid=0x409).
There are no instructions specific to setting up clustering for SharePoint Foundation 2010. For instructions on how to set up failover clustering, see Installing a SQL Server 2008 Failover Cluster (http://go.microsoft.com/fwlink/?LinkId=132112&clcid=0x409).
-
Configure availability by using SQL Server database mirroring (SharePoint Foundation 2010)
Published: May 12, 2010
This article describes how to use high-availability database mirroring to configure availability within a farm for Microsoft SharePoint Foundation 2010. The article assumes that you are familiar with the concepts and terms presented in Plan for availability (SharePoint Foundation 2010).
Microsoft SQL Server database mirroring provides availability support by sending transactions directly from a principal database and server to a mirror database and server when the transaction log buffer for the principal database is written to disk. For availability within a Microsoft SharePoint Foundation 2010 farm, you use high-availability database mirroring, also known as high-safety mode with automatic failover. High-availability database mirroring involves three server instances: a principal, a mirror, and a witness. The witness server enables SQL Server to automatically fail over from the principal server to the mirror server. Failover from the principal database to the mirror database typically takes several seconds.
Within a SharePoint Foundation 2010 farm, mirroring can provide redundancy for the content and configuration databases, and for many service databases. Even if your databases are mirrored to the same server, each database fails over individually. The following figure shows how mirroring is configured to provide availability within a SharePoint Foundation 2010 farm.
SharePoint Foundation 2010 is mirroring-aware. To use mirroring in your environment, first configure mirroring, and then set the failover database value in SharePoint Foundation.
In this article:
-
Before you begin
Before you begin to configure mirroring, make sure that your database administrator is aware of the following requirements and supported topologies.
Database mirroring requirements
Become familiar with the recommendations in the following list, and ensure that your databases and system meet any requirements before you configure database mirroring for a SharePoint Foundation environment:
- We recommend that your system have latency no more than 1 millisecond.
- System bandwidth should preferably be 1 gigabyte (GB) per second.
- Logs are copied in real time between the principal and the mirror servers, and copying can affect performance. Make sure that you have sufficient memory and bandwidth on both the principal and mirror server.
- The principal server and mirror server must run the same version and edition of SQL Server, and they must run in the same language. Database mirroring is available only in the Standard, Developer, and Enterprise editions. The witness server can run any version of SQL Server, including SQL Server 2008 Express.
-
Mirroring works only with databases that use the full recovery model.
By default, SharePoint Foundation 2010 databases are configured to use the simple recovery model. To configure database mirroring, the recovery model of the database must be set to Full. For information about how to set the recovery model for a database, see How to: View or Change the Recovery Model of a Database (SQL Server Management Studio) (http://go.microsoft.com/fwlink/?LinkId=132075&clcid=0x409).
- If you plan to mirror databases, consider that the size of the transaction logs for these databases may become very large. To work around this, you can establish a recovery plan that truncates transaction logs as necessary. For more information, see the following article in the Microsoft Knowledge Base: How to stop the transaction log of a SQL Server database from growing unexpectedly (http://go.microsoft.com/fwlink/?LinkId=111458&clcid=0x409).
- Every database mirroring session creates at least two threads for each database. Ensure that your database server has enough threads to allocate for mirroring all the supported databases. If you have insufficient threads, performance can decrease as more databases are added to a session.
For more information about performance for database mirroring, see Database mirroring best practices and performance considerations (http://go.microsoft.com/fwlink/?LinkId=185119).
Security associated with database mirroring
Database mirroring uses TCP sessions to transport the transaction log from one server to another and to monitor the current health of the system for automatic failovers. Authentication is performed at the session level when a port is opened for connection. Database mirroring supports both Windows authentication (NTLM or Kerberos) and certificates.
Unless the network is secure, the data transmitted during the session should be encrypted. Database mirroring supports both Advanced Encryption Standard (AES) and RC4 encryption algorithms. For more information about the security associated with database mirroring, see Database Mirroring Transport Security (http://go.microsoft.com/fwlink/?LinkId=83569&clcid=0x409).
SharePoint 2010 Products security and mirrored servers
When you set up a mirrored database, the SQL Server logins and permissions for the database to be used with a SharePoint farm are not automatically configured in the master and msdb databases on the mirror server. Instead, you must configure the permissions for the required logins. These include, but are not limited to, the following:
- The Central Administration application pool account should be a member of the dbcreator and securityadmin fixed server roles.
- All application pool accounts, the default content access accounts, and any accounts required for service applications should have SQL Server logins, although they should not be assigned to SQL Server fixed server or fixed database roles.
- Members of the Farm Administrators SharePoint group should also have SQL Server logins and should be members of the same SQL Server roles as the Central Administration application pool account.
We recommend that you transfer your logins and permissions from the principal server to the mirror server by running a script. An example script is available in Knowledge Base article 918992 How to transfer the logins and the passwords between instances of SQL Server 2005 (http://go.microsoft.com/fwlink/?LinkId=122053&clcid=0x409). For more information about how to transfer SQL Server metadata between instances, see the SQL Server Books Online article Managing Metadata When Making a Database Available on Another Server Instance (http://go.microsoft.com/fwlink/?LinkId=122055&clcid=0x409).
Supported topologies
We recommend that you maintain a one-to-one mapping of principal server and database instance to mirror server and database instance to ensure compatibility with SharePoint Foundation 2010.
The supported topologies include mirroring all content databases, the configuration database, the Central Administration content database, and the service application databases except for the Web Analytics Staging database and the User Profile Synchronization database.

Note:We do not recommend that you mirror the Usage and Health Data Collection Logging database. A SharePoint environment can continue to run if this database fails, and this data can be quickly regenerated.
Avoid topologies that do not have matching principal server and database instances and mirror server and database instances. Also, keep the configuration database and the administration content database on the same server.
-
Configure high-availability database mirroring
We recommend that a SQL Server database administrator configure high-availability mirroring for a production environment. For a test environment, we have provided Transact-SQL scripts that you can use to configure your environment. For more information, see Sample script for configuring SQL Server mirroring (SharePoint Foundation 2010).
-
Configure SharePoint 2010 Products to be aware of mirrored databases
To make SharePoint Foundation 2010 aware that failover mirrored databases exist, perform the following procedure for all configuration and content databases.

Note:We recommend that you use Windows PowerShell cmdlets to set failover database values. Although you can use the Central Administration Web site to set some failover database values, you cannot use it for all databases.
To configure SharePoint 2010 Products to be aware of mirrored databases by using Windows PowerShell
- Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
- On the Start menu, click All Programs.
- Click Microsoft SharePoint 2010 Products.
- Click SharePoint 2010 Management Shell.
-
At the Windows PowerShell command prompt, type the following commands, and then press ENTER:
$db = get-spdatabase | where {$_.Name -eq “database name“}
$db.AddFailoverServiceInstance(“mirrored database name“)
$db.Update()
For more information, see Get-SPDatabase (http://technet.microsoft.com/library/c9802bf8-5216-4ade-b559-7ee25fcfa666(Office.14).aspx).
-
User experience during a failover
While SQL Server is switching to using a mirrored database, users of a SharePoint site that runs against the database may experience brief connectivity issues and data loss.
-
Monitoring and troubleshooting mirroring
To monitor the status and performance of mirroring within a farm, database administrators can use the Database Mirroring Monitor. Monitoring enables you to determine whether and how well data is flowing in the database mirroring session. Database Mirroring Monitor is also useful for troubleshooting the cause of reduced data flow. For more information, see Database Mirroring Monitor Overview (http://go.microsoft.com/fwlink/?LinkId=185068). Another resource to use in troubleshooting is the SQL Server Books Online article Troubleshooting Database Mirroring Setup (http://go.microsoft.com/fwlink/?LinkId=185069).
-
Other Resources
Database Mirroring (http://go.microsoft.com/fwlink/?LinkID=180597)
-
Sample script for configuring SQL Server mirroring (SharePoint Foundation 2010)
Published: May 12, 2010
This article contains a series of sample scripts that you can use to set up Microsoft SQL Server mirroring for a test Microsoft SharePoint Foundation 2010 environment. We recommend that a SQL Server database administrator configure mirroring for a production environment.
To set up database mirroring with SharePoint Foundation 2010, you must work individually with each database that you want to mirror.
In this article:
- Configure database mirroring with certificates and full recovery
- Set up a witness server
- Transfer permissions to the mirror server
The steps in the following section apply to the following server farm topology:
- One or more front-end Web servers
- Three servers that are running SQL Server 2008: principal server, mirror server, and witness server
- One configuration database
- Multiple content databases
- One or more service application databases
-
Configure database mirroring with certificates and full recovery
Each step lists the server on which it should be performed. Use Transact-SQL to send these commands to SQL Server. Placeholder information is denoted by angle brackets (<>); replace this with information that is specific to your deployment.
To set up the principal server for outbound connections
- On the principal server, create a certificate and open a port for mirroring.
|
–On the master database, create the database master key, if needed |
- On the principal server, back up the certificate.
|
–Back up the HOST_A certificate. |
- On the principal server, back up the database. This example uses the configuration database. Repeat for all databases.
|
USE master; |
- Copy the backup file to the mirror server. Repeat for all databases.
- By using any secure copy method, copy the backup certificate file (C:\HOST_HostA_cert.cer, for example) to the mirror server.
- On the principal server, create a login and user for the mirror server, associate the certificate with the user, and grant the login connect permissions for the partnership.
|
–Create a login on HOST_A for HOST_B |
To set up the mirror server for outbound connections
- On the mirror server, create a certificate and open a port for mirroring.
|
–On the master database, create the database master key, if needed. |
- On the mirror server, back up the certificate.
|
–Back up the HOST_B certificate. |
- By using any secure copy method, copy the backup certificate file (C:\HOST_HostB_cert.cer, for example) to the principal server.
- On the mirror server, restore the database from the backup files. This example uses the configuration database. Repeat for all databases.
|
RESTORE DATABASE SharePoint_Config |
To set up the mirror server for inbound connections
- On the mirror server, create a login and user for the principal server, associate the certificate with the user, and grant the login connect permissions for the partnership.
|
–Create a login on HOST_B for HOST_A |
To set up the principal server for inbound connections
- On the principal server, create a login and user for the mirror server, associate the certificate with the user, and grant the login connect permissions for the partnership.
|
–Create a login on HOST_A for HOST_B |
To set up the mirroring partners
- On the principal server, set up the mirroring partnership. This example uses the configuration database. Repeat for all databases.
|
–At HOST_A, set the server instance on HOST_B as a partner (mirror server). |
- On the mirror server, set up the mirroring partnership. This example uses the configuration database. Repeat for all databases.
|
–At HOST_B, set the server instance on HOST_A as a partner (principal server): |
-
Set up a witness server
Each step lists the server on which it should be performed. Use Transact-SQL to send these commands to SQL Server. Placeholder information is denoted by angle brackets (<>); replace this with information that is specific to your deployment.
- On the witness server, set up the certificate and open the port.
|
–On the master database, create the database master key, if needed |
- On the witness server, back up the certificate.
|
–Back up the HOST_C certificate |
- By using any secure copy method, copy the backup certificate file (C:\WITNESS_HOSTC_cert.cer, for example) to the principal server and the mirror server.
- On the witness server, create logins and users for the principal and mirror servers, associate the certificates with the users, and grant the logins connect permissions for the partnership.
|
–Create a login on witness HOST_C for principal HOST_A |
- On the principal server, create a login and user for the witness server, associate the certificate with the user, and grant the login connect permissions for the partnership. Repeat for the mirror server.
|
–Create a login on master HostA for witness HostC |
- On the principal server, attach the witness server. This example uses the configuration database. Repeat for all databases.
|
–Set up the witness server |
-
Transfer permissions to the mirror server
When you set up a mirrored database, the SQL Server logins and permissions for the database that will be used with a SharePoint farm are not automatically configured in the master and msdb databases on the mirror server. Instead, you must configure the permissions for the required logins.
We recommend that you transfer your logins and permissions from the principal server to the mirror server by running a script. The script that we recommend that you use is available in Knowledge Base article 918992: How to transfer the logins and the passwords between instances of SQL Server 2005 (http://go.microsoft.com/fwlink/?LinkId=122053&clcid=0x409).
-
Removing mirroring from a server
To remove mirroring from a server, see How to: Remove Database Mirroring (Transact-SQL) (http://go.microsoft.com/fwlink/?LinkId=185070).

-
Planning guide for
Microsoft SharePoint Foundation 2010
Microsoft Corporation
Published: November 2010
Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com)
- Abstract
This book provides information and guidelines to lead a team through the steps of planning the deployment of a solution based on Microsoft SharePoint Foundation 2010. The audiences for this book are business application specialists, line-of-business specialists, information architects, IT generalists, program managers, and infrastructure specialists who are planning a solution based on SharePoint Foundation 2010.
The content in this book is a copy of selected content in the SharePoint Foundation 2010 technical library (http://go.microsoft.com/fwlink/?LinkId=181463) as of the publication date. For the most current content, see the technical library on the Web.
This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
© 2010 Microsoft Corporation. All rights reserved.
Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
Contents
Planning and architecture for SharePoint Foundation 2010 1
Technical diagrams (SharePoint Foundation 2010) 2
Site and solution planning (SharePoint Foundation 2010) 7
Fundamental site planning (SharePoint Foundation 2010) 8
Sites and site collections overview (SharePoint Foundation 2010) 9
Site templates included in SharePoint Foundation 2010 10
Plan sites and site collections (SharePoint Foundation 2010) 14
About planning sites and site collections 14
Plan sites by organizational hierarchy 15
Plan Internet presence sites 16
Site planning data worksheet 17
Site navigation overview (SharePoint Foundation 2010) 18
Navigation controls overview 18
Navigation controls on master pages 19
Plan site navigation (SharePoint Foundation 2010) 21
Create a site navigation diagram 21
Understanding inherited navigation 22
Determine which sites inherit the top link bar 23
Determine which additional links to add manually to the top link bar 24
Determine other site navigation options 24
Site planning data worksheet 24
Themes overview (SharePoint Foundation 2010) 25
Uploading your own custom themes to the theme gallery 26
Plan for using themes (SharePoint Foundation 2010) 27
About planning for using themes 27
Decide whether to use themes 27
Determine how many themes are needed 28
Decide who makes the themes 28
Site planning data worksheet 29
Plan for multilingual sites (SharePoint Foundation 2010) 30
About planning multilingual sites 30
Determine language and locale requirements 31
Determine language pack requirements 31
Determine requirements for word breakers and stemmers 33
Multilingual user interface overview (SharePoint Foundation 2010) 35
Use and benefits of the multilingual user interface 35
How the multilingual user interface works 36
What is supported by the multilingual user interface 37
Adding and modifying application content 38
Exporting and importing translated content 39
Limitations of the multilingual user interface 39
Plan for the multilingual user interface (SharePoint Foundation 2010) 40
Determine language requirements for your sites 40
Plan for translating content 40
Plan for installing service packs 41
Security planning for sites and content (SharePoint Foundation 2010) 42
Plan site permissions (SharePoint Foundation 2010) 43
About assigning permissions 44
About permission inheritance 45
Permission inheritance and fine-grained permissions 45
Permission inheritance and subsites 45
About effective permissions 46
Plan for permission inheritance 47
Determine permission levels and groups (SharePoint Foundation) 49
Review available default groups 49
Review available permission levels 50
Determine whether you need additional permission levels or groups 51
Do you need custom permission levels? 51
Choose security groups (SharePoint Foundation 2010) 53
Determine which Windows security groups and accounts to use for granting access to sites 53
Decide whether to allow access for all authenticated users 54
Decide whether to allow access for anonymous users 54
Choose administrators and owners for the administration hierarchy (SharePoint Foundation 2010) 56
Best practices for using fine-grained permissions (white paper) (SharePoint Foundation 2010) 58
Sandboxed solutions planning (SharePoint Foundation 2010) 59
Sandboxed solutions overview (SharePoint Foundation 2010) 60
Deploying and running a sandboxed solution 60
Isolating sandboxed solutions 62
What a sandboxed solution cannot contain 62
Comparison of sandboxed and farm solutions 63
Benefits of using sandboxed solutions 64
Planning sandboxed solutions (SharePoint Foundation 2010) 65
Determine when to use sandboxed solutions 65
Plan to load balance sandboxed solution code 66
Determine where to deploy sandboxed solutions 66
Determine who can deploy sandboxed solutions 67
Determine which site collections will run sandboxed solutions using quotas 67
Plan resource usage quotas for sandboxed solutions 67
Plan sandboxed solutions governance 69
Plan for collaboration sites (SharePoint Foundation 2010) 70
Determine number of collaboration sites 70
Integration with Microsoft SharePoint Workspace 2010 71
Document management planning (SharePoint Foundation 2010) 72
Document library planning (SharePoint Foundation 2010) 73
Content types planning (SharePoint Foundation 2010) 75
Versioning, content approval, and checkout planning (SharePoint Foundation 2010) 78
About versioning, content approval, and check-outs 78
Plan check-out and check-in 80
Co-authoring overview (SharePoint Foundation 2010) 82
Co-authoring functionality in SharePoint Foundation 2010 82
Understanding the end-user experience 83
Software Version Requirements 85
Co-authoring in a mixed Office environment 85
Mixed environment that has Microsoft Office PowerPoint and Word 2007 85
Mixed environment that has Microsoft Office OneNote 2007 86
Performance and scalability 86
Business data and processes planning (SharePoint Foundation) 87
Plan for Business Connectivity Services (SharePoint Foundation 2010) 88
Business Connectivity Services overview (SharePoint Foundation 2010) 89
Typical solutions based on Business Connectivity Services 89
Business Connectivity Services security overview (SharePoint Foundation 2010) 91
Business Connectivity Services security architecture 91
Business Connectivity Services authentication overview 93
Configuring Business Connectivity Services for credentials authentication 93
Configuring Business Connectivity Services for claims-based authentication 97
Business Connectivity Service permissions overview 99
What can permissions be set on? 99
Special permissions on the Business Data Connectivity service 103
Common tasks and their related permissions 104
Securing Business Connectivity Services 105
Server to server communication 105
Applications that use FileBackedMetadataCatalog 105
Diagnostic logging in Business Connectivity Services overview (SharePoint Foundation 2010) 106
Diagnostic logging in Business Connectivity Services 106
Diagnostic logging on servers 109
Example: using diagnostic logging 109
Plan workflows (SharePoint Foundation 2010) 111
Workflows overview (SharePoint Foundation 2010) 112
Benefits of using workflows 113
Automating business processes 113
Workflows improve collaboration 114
Workflow types: Declarative and compiled 116
Choose a workflow authoring tool (SharePoint Foundation) 119
Authoring workflows with Visual Studio 2010 and WF Workflow Designer 120
Authoring workflows with Microsoft SharePoint Designer 2010 122
Plan for workflow security and user management (SharePoint Foundation 2010) 127
List manager, administrator, and developer roles and responsibilities 127
List administrators (anyone with Manage List or Web Designer permissions) 128
Running workflows as an administrator 128
Workflow configuration settings 128
Required permissions to start a workflow 129
Central Administration settings 129
Information disclosure in task and workflow history lists 130
Spoofing and tampering attacks in the task and workflow history lists 131
Security issues in the workflow history list 131
User-Impersonation Step type for declarative workflows 132
Approval Workflow: A Scenario (SharePoint Foundation 2010) 134
Associating a workflow with a site 135
Interacting with a workflow 136
Plan site creation and maintenance (SharePoint Foundation 2010) 138
Plan process for creating sites (SharePoint Foundation 2010) 139
Determine who can create sites and a method for site creation 139
Plan for Self-Service Site Management 140
Plan for custom site creation processes 141
Plan site maintenance and management (SharePoint Foundation 2010) 142
Plan for managing site collections 143
Plan site collection quotas 143
Plan site use confirmation and deletion 144
Plan quota management (SharePoint Foundation 2010) 145
About planning quota management 145
Determine quota template settings 146
Determine recycle bin settings 146
Plan e-mail integration (SharePoint Foundation 2010) 148
Plan incoming e-mail (SharePoint Foundation 2010) 149
Key decisions for planning incoming e-mail 149
Using an advanced scenario 150
Configuration options and settings modes 154
Plan incoming e-mail worksheet 154
Plan outgoing e-mail (SharePoint Foundation 2010) 156
Key planning phases of outgoing e-mail 157
From and Reply-to addresses 157
Server farm and environment planning (SharePoint Foundation 2010) 159
System requirements (SharePoint Foundation 2010) 160
Hardware and software requirements (SharePoint Foundation 2010) 161
Hardware requirements—Web servers, application servers, and single server installations 161
Hardware requirements—Database servers 162
Access to applicable software 166
Plan browser support (SharePoint Foundation 2010) 170
About planning browser support 170
Key planning phase of browser support 170
URL path length restrictions (SharePoint Foundation 2010) 184
Understanding URL and path lengths 184
SharePoint URL composition 184
URL path length limitations 186
SharePoint URL path length limitations 186
Internet Explorer URL length limitations 187
Resolving URL length problems 187
IP support (SharePoint Foundation 2010) 188
Logical architecture planning 190
Services architecture planning (SharePoint Foundation 2010) 191
About service applications 191
Services infrastructure and design principles 192
More granular configuration of services 192
Service application groups 193
Connections for service applications 195
Service application administration 195
Plan for host-named site collections (SharePoint Foundation 2010) 196
About host-named site collections 196
Create a host-named site collection 198
Programmatically create a host-named site collection 198
Use managed paths with host-named site collections 199
Expose host-named sites over HTTP or SSL 199
Configure SSL for host-named site collections 200
Use host-named site collections with off-box SSL termination 200
Plan authentication (SharePoint Foundation 2010) 201
Plan authentication methods (SharePoint Foundation 2010) 202
Supported authentication methods 202
Authentication modes — classic or claims-based 203
Implementing Windows authentication 205
Implementing forms-based authentication 207
Implementing SAML token-based authentication 208
Choosing authentication for LDAP environments 210
Planning zones for Web applications 210
Architecture for SAML token-based providers 213
Plan security hardening (SharePoint Foundation 2010) 217
Web server and application server roles 217
Specific port, protocol, and service guidance 219
Blocking the standard SQL Server ports 220
Service application communication 221
File and Printer Sharing service requirements 221
Service requirements for e-mail integration 222
SharePoint 2010 Products services 223
Plan automatic password change (SharePoint Foundation 2010) 225
Configuring managed accounts 225
Resetting passwords automatically on a schedule 225
Detecting password expiration 226
Resetting the account password immediately 226
Synchronizing SharePoint Foundation account passwords with Active Directory Domain Services 226
Resetting all passwords immediately 226
SQL Server and storage (SharePoint Foundation 2010) 228
Overview of SQL Server in a SharePoint environment (SharePoint Foundation 2010) 229
SharePoint 2010 Products and the SQL Server database engine 229
Working with the SQL Server databases that support SharePoint 2010 Products 230
SQL Server as a data platform for business intelligence in SharePoint 2010 Products 230
SQL Server database engine 230
SQL Server Analysis Services (SSAS): multi-dimensional data 230
SQL Server Analysis Services: data mining 231
SQL Server Reporting Services (SSRS) 231
SQL Server Integration Services (SSIS) 231
Business Intelligence Development Studio (BIDS) 232
PowerPivot for Excel and PowerPivot for SharePoint 232
StreamInsight and complex event processing 232
Overview of Remote BLOB Storage (SharePoint Foundation 2010) 234
Using RBS together with SharePoint 2010 Products 235
Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010) 237
Plan for business continuity management (SharePoint Foundation 2010) 241
Business continuity management capabilities 241
Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010) 245
Protecting content by using recycle bins 245
Second stage (Site Collection) Recycle Bin 246
Protecting content by using versioning 247
Plan for backup and recovery (SharePoint Foundation 2010) 248
Define business requirements 248
Choose what to protect and recover in your environment 249
Choose what to recover from within SharePoint content databases 251
Protecting service applications 252
Protecting SQL Server Reporting Services databases 253
Plan for enhanced backup and recovery performance 255
Follow recommendations for configuring SQL Server and storage 256
Minimize latency between SQL Server and the backup location 256
Avoid processing conflicts 256
Follow SQL Server backup and restore optimization recommendations 256
Ensure sufficient write performance on the backup drive 257
Backup and recovery overview (SharePoint Foundation 2010) 258
Backup and recovery scenarios 258
Granular backup and export architecture 263
Restoring from a farm backup 265
Restoring from a site collection backup 266
Recovering from an unattached content database 266
Plan for availability (SharePoint Foundation 2010) 268
Determining availability requirements 269
Choosing an availability strategy and level 270
Hardware component fault tolerance 270
Plan for disaster recovery (SharePoint Foundation 2010) 277
Disaster recovery overview 277
Choose a disaster recovery strategy 278
Planning for cold standby data centers 278
Planning for warm standby data centers 279
Planning for hot standby data centers 279
Service application redundancy across data centers 281
System requirements for disaster recovery 282
Virtualization planning (SharePoint Foundation 2010) 283
Virtualization support and licensing (SharePoint Foundation 2010) 284
SharePoint 2010 Products support for virtualization 284
Server virtualization using Hyper-V technology 284
Operating system environment (OSE) licensing 284
SharePoint 2010 Products licensing 285
Hyper-V virtualization requirements (SharePoint Foundation 2010) 286
Plan for virtualization (SharePoint Foundation 2010) 288
Create a plan for deploying SharePoint Foundation 2010 in a virtual environment 288
Performance and capacity test results and recommendations (SharePoint Foundation 2010) 293
Planning worksheets for SharePoint Foundation 2010 294
Planning worksheets by task 294
Planning worksheets by title 296
- Abstract
-
Getting help
Every effort has been made to ensure the accuracy of this book. This content is also available online in the Office System TechNet Library, so if you run into problems you can check for updates at:
http://technet.microsoft.com/office
If you do not find your answer in our online content, you can send an e-mail message to the Microsoft Office System and Servers content team at:
itspdocs@microsoft.com
If your question is about Microsoft Office products, and not about the content of this book, please search the Microsoft Help and Support Center or the Microsoft Knowledge Base at:
-
Planning and architecture for SharePoint Foundation 2010
IT pros can use the content in the planning and architecture guides to develop conceptual, logical, and physical designs for configuring Microsoft SharePoint Foundation 2010 features, servers, and topologies. This section also provides recommendations for system designs based on customer scenarios and includes information to help IT pros design a highly reliable, consistently available, and scalable system.
-
Downloadable resources
-
Planning articles
Site and solution planning
Server and farm environment planning
-
Technical diagrams (SharePoint Foundation 2010)
Many of these resources are visual representations of recommended solutions. They include poster-sized documents available in formats including Microsoft Office Visio 2007 or Microsoft Visio 2010 files (.vsd), PDF files, and XPS files. You might need extra software to view these files. See the following table for information about opening these files.
File type
Software
.vsd
Office Visio 2007, Microsoft Visio 2010, or the free Visio viewer (http://go.microsoft.com/fwlink/?LinkId=118761&clcid=0x409)
If you use the Visio viewer, right-click the VSD link, click Save Target As, save the file to your computer, and then open the file from your computer.
.pdf
Any PDF viewer, such as Adobe Reader (http://go.microsoft.com/fwlink/?LinkId=134751&clcid=0x409)
.xps
Windows 7, Windows Vista, Windows XP with .NET Framework 3.0, or XPS Essentials Pack (http://go.microsoft.com/fwlink/?LinkId=134750&clcid=0x409)
-
Models
Models are 34-by-44-inch posters that detail a specific technical area. These models are intended to be used with corresponding articles on TechNet. These models are created by using Office Visio 2007. You can modify the Visio files to illustrate how you plan to incorporate Microsoft SharePoint 2010 Products in your own environment.
Title
Description
SharePoint 2010 Products Deployment

Visio (http://go.microsoft.com/fwlink/?LinkId=183024) PDF (http://go.microsoft.com/fwlink/?LinkId=183025)
Presents such deployment-related information as the different deployment stages and environments, plus a flowchart that illustrates the steps for installing and configuring SharePoint 2010 Products.
Services in SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkID=167090)
Describes and illustrates the services architecture, including and common ways to deploy services in your overall solution design.
Extranet Topologies for SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkId=187987)
Illustrates the specific extranet topologies that have been tested with SharePoint 2010 Products. Provides a comparison of ISA Server, Forefront TMG, Forefront UAG when used as a firewall or gateway product with SharePoint 2010 Products.
Hosting Environments in SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkID=167084)
Summarizes the support for hosting environments and illustrates common hosting architectures.
Search Technologies for SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkID=167731)
Compares and contrasts the search technologies that work with SharePoint Products 2010:
SharePoint Foundation 2010
Search Server 2010 Express
Search Server 2010
SharePoint Server 2010
FAST Search Server 2010 for SharePoint
Databases That Support SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkId=187970)
Describes the Microsoft SQL Server databases on which SharePoint Foundation 2010 runs.
SharePoint 2010 Products: Virtualization Process

Visio (http://go.microsoft.com/fwlink/?LinkId=195021)
Provides guidance related to virtualization and the various stages of deployment, as well as requirements and examples.
-
Tips for printing posters
If you have a plotter, you can print these posters in their full size. If you don’t have plotter, use the following steps to print on smaller paper.
Print posters on smaller paper
1. Open the poster in Visio.
2. On the File menu, click Page Setup.
3. On the Print Setup tab, in the Printer paper section, select the size of paper you want to print on.
4. On the Print Setup tab, in the Print zoom section, click Fit to, and then enter 1 sheet across by 1 sheet down.
5. On the Page Size tab, click Size to fit drawing contents, and then click OK.
6. On the File menu, click Print.
-
Site and solution planning (SharePoint Foundation 2010)
This section describes how to plan your site and solution components in a Microsoft SharePoint Foundation 2010 environment.
Plan for collaboration sites (SharePoint Foundation 2010)
Plan for Business Connectivity Services (SharePoint Foundation 2010)
Security planning for sites and content (SharePoint Foundation 2010)
Fundamental site planning (SharePoint Foundation 2010)
Choose a workflow authoring tool (SharePoint Foundation)
Approval Workflow: A Scenario (SharePoint Foundation 2010)
-
Fundamental site planning (SharePoint Foundation 2010)
This section provides information that helps IT pros plan sites that use Microsoft SharePoint Foundation 2010 features.
The effectiveness of a site or a group of sites depends on many factors, but one of the most important factors is the ability to predictably locate the site and the content that you need within the site. The structure of a site or a group of sites and the navigation inside and among sites are important for helping users find and share information and work together.
In this section:
Sites and site collections overview (SharePoint Foundation 2010) describes site collections and sites, and it contains information about the site templates that are used to create sites in SharePoint Foundation 2010.
Plan sites and site collections (SharePoint Foundation 2010) describes the process and important considerations for planning SharePoint Foundation 2010 sites and site collections.
Site navigation overview (SharePoint Foundation 2010) provides an overview of the types of navigation that are available in a site.
Plan site navigation (SharePoint Foundation 2010) helps you design the navigation for your site.
Themes overview (SharePoint Foundation 2010) provides an overview of themes and how they work.
Plan for using themes (SharePoint Foundation 2010) discusses how to plan for using themes across your sites, and it includes important steps to plan how to use themes for your sites.
Plan for multilingual sites (SharePoint Foundation 2010) discusses how to plan for multilingual SharePoint Foundation 2010 sites.
Multilingual user interface overview (SharePoint Foundation 2010) describes the multilingual user interface in SharePoint Foundation 2010.
Plan for the multilingual user interface (SharePoint Foundation 2010) describes how to plan for using the multilingual user interface in your SharePoint Foundation 2010 site solution.
-
Sites and site collections overview (SharePoint Foundation 2010)
A Microsoft SharePoint Foundation 2010 site collection is a hierarchical site structure that is made up of one top-level site and any sites below it. This article describes site collections and sites and contains information about the site templates that are used to create sites in SharePoint Foundation 2010.
In this article:
-
Site collections overview
The sites in a site collection have shared administration settings, common navigation, and other common features and elements. Each site collection contains a top-level site and (usually) one or more sites below it in a hierarchical structure.
You must group your site’s content and features into a site collection. This provides the following benefits:
For site designers, a site collection’s galleries and libraries (such as the master page gallery or the site collection images library) provide a means for creating a unified, branded user experience across all sites in the site collection.
For site collection administrators, a site collection provides a unified mechanism and scope for administration. For example, security, policies, and features can be managed for a whole site collection; Site Collection Web Analytics Reports, audit log reports, and other data can help administrators track site collection security and performance.
For farm administrators, site collections provide scalability for growth based on how much content is stored. Because each site collection can use a unique content database, administrators can easily move them to separate servers.
For site authors, a site collection’s shared site columns, content types, Web Parts, authoring resources, workflows, and other features provide a consistent authoring environment.
For site users, a site collection’s unified navigation, branding, and search tools provide a unified Web site experience.
-
Sites overview
A site collection consists of a top-level site and one or more sites below it. Each top-level site and any sites below it in the site structure are based on a site template and can have other unique settings and unique content. Partition your site collection content into separate sites to obtain finer control of the appearance, content, and features of the various pages in your site collection. The following list includes site features that you can configure uniquely:
Templates You can make each site have a unique template. For more information, see Site templates included in SharePoint Foundation 2010.
Language If language packs have been installed on the Web server, you can select a language-specific site template when you create a new site. Text that appears on the site is displayed in the site template’s language. For more information, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx).
Security You can define unique user groups and permissions for each site.
Navigation You can fine-tune your site’s navigation experience by configuring unique navigation links in each part of your site’s hierarchy. Site navigation reflects the relationships among the sites in a site collection. Therefore, planning navigation and planning sites structures are closely related activities. For more information, see Site navigation overview (SharePoint Foundation 2010).
Web pages You can make each site have a unique welcome page and other pages.
Site layouts You can make unique layouts or master pages available in a site.
Themes You can change colors and fonts on a site. For more information, see Plan for using themes (SharePoint Foundation 2010).
Regional settings You can change the regional settings, such as locale, time zone, sort order, time format and calendar type.
Search You can make each site have unique search settings. For example, you can specify that a particular site never appears in search results.
Content types You can make each site have unique content types and site columns.
Workflows You can make each site have unique workflows. For more information, see Plan workflows (SharePoint Foundation 2010).
-
Site templates included in SharePoint Foundation 2010
The following section contains information about the site templates that are included in SharePoint Foundation 2010. Although you can use a site template with its default configuration, you can also change the site’s default settings by using the site administration pages, and then saving the site as a new template. In addition, you can modify a template’s design and features by using Microsoft SharePoint Designer 2010 or Microsoft Visual Studio 2010.
The following table lists every site template, describes the purpose of each, and indicates whether the template is available at the site collection level, site level, or both. The category that is used to group the templates might be different, depending on the level at which a site is created.
Template
Purpose
Category in Site Collection
Category in Site
< Select template later>
An empty site for which you can select a template later.
Custom
N/A
Basic Meeting Workspace
A site on which you can plan, organize, and capture the results of a meeting. It provides lists for managing the agenda, meeting attendees, and documents.
Meetings
Meetings
Blank Meeting Workspace
A blank meeting site that you can customize based on your requirements.
Meetings
Meetings
Blank Site
A blank site that you can customize based on your requirements.
Collaboration
Blank & Custom
Blog
A site on which a person or team can post ideas, observations, and expertise that site visitors can comment on.
Collaboration
Content
Decision Meeting Workspace
A site on which you can track status or make decisions at meetings. It provides lists to create tasks, store documents, and record decisions.
Meetings
Meetings
Document Workspace
A site on which colleagues can work together on a document. It provides a document library for storing the primary document and supporting files, a tasks list for assigning to-do items, and a links list to point to resources that are related to the document.
Collaboration
Collaboration, Content
Group Work Site
This template provides a groupware solution that teams can use to create, organize, and share information. It includes the Group Calendar, Circulation, Phone-Call Memo, the document library and the other basic lists.
Collaboration
Collaboration
Multipage Meeting Workspace
A site on which you can plan a meeting and capture the meeting’s decisions and other results. It provides lists for managing the agenda and meeting attendees. It also provides two blank pages that you can customize based on your requirements.
Meetings
Meetings
Social Meeting Workspace
A site on which you can plan social occasions. It provides lists for tracking attendees, providing directions, and storing pictures of the event.
Meetings
Meetings
Team Site
A site on which a team can organize, author, and share information. It provides a document library, and lists for managing announcements, calendar items, tasks, and discussions.
Collaboration
Collaboration
-
See Also
Plan sites and site collections (SharePoint Foundation 2010)
-
-
Plan sites and site collections (SharePoint Foundation 2010)
Microsoft SharePoint Foundation 2010 sites are made up of a site collection, which is a hierarchical structure that includes one top-level site and any sites below it. This article describes the process and important considerations for planning SharePoint Foundation 2010 sites and site collections, and it recommends a method for recording your site structure decisions. For information about sites and site collections, and the site templates that are used to create sites in SharePoint Foundation 2010, see Sites and site collections overview (SharePoint Foundation 2010).
In this article:
About planning sites and site collections
Plan sites by organizational hierarchy
-
About planning sites and site collections
In general, you plan your sites and site collections in the following order:
Determine the number and types of top-level sites and any sites below them in the hierarchy that are needed.
Determine the number and types of site collections into which the sites will be organized.
-
Determine types of sites
The first step in planning a solution that is based on SharePoint Foundation 2010 is to determine the types of sites your organization and its customers need. Determining the types of sites affects later planning decisions, such as where the sites will be implemented in your server topology, what features to plan for each site, how processes that span multiple sites are implemented, and how information is made available across one or more sites. This section contains information about how to plan different kinds of sites.
Plan the basic sites that you need based on the scale and structure of your organization. Each of these sites can contain information that is needed for a project or division within your larger organization, and each will link to collaboration sites that are relevant to that project or division. Some sites for larger divisions or projects will also aggregate information that is found on all the smaller sites that are devoted to smaller divisions or projects.
Use the following guidelines when you plan sites that are based on your organizational structure:
Divisional or team sites Plan to create one site for a small organization or one site for every division or project of 50–100 people in a medium to large organization. In large organizations, there might be several levels of sites, with each site focusing on the content that is created and managed at its level of the organization.
You can design a site for members of your organization to collaborate on content related to your business or organizational goals. These can be self-contained or they can work with other sites as part of a publishing process. Often, these sites will have a mixture of collaborative content that is used internally and content that is intended for publication to an audience.
Rollup sites A rollup site contains general cross-organization content. It makes it possible for users across divisions to find information, experts, and access to organization-wide processes. It often contains sites that are related to the overall organizational information architecture and that are usually mapped to the structure of the divisional or project sites. For each organization, plan to create a centralized rollup site that uses an aggregated view of all related sites.
An application site organizes team processes and provides mechanisms for running them. Application sites often include digital dashboards and other features to view and manipulate data that is related to the site’s purpose. The information that is presented in an application site usually comes from diverse sources, such as databases or other SharePoint sites.
For example, the human resources organization in an organization could design an application site to provide employees with:
Access to general information, such as employee handbooks and career opportunities.
Ways to do common tasks, such as submitting timecards and expense reports.
Dashboards to view personalized information, such as an employee’s salary and benefits history.
As another example, the internal technical support group in an organization could design a Help Desk application site to provide technical support to members of the organization. Features of the application site could include the following:
Access to a knowledge base of past support incidents and best-practices documentation.
Ways to do common tasks, such as starting a support incident or reviewing the status of an ongoing incident.
Integration with communications features that support online meetings and discussions.
Personalized views of data. For example, support managers could view dashboards that provide views of their team members’ productivity and customer satisfaction ratings. Support engineers could view their current unresolved incidents.
Internet presence sites are customer-facing sites. They are usually branded and are characterized by consistent stylistic elements, such as colors, fonts, and logos in addition to structural elements such as navigation features and the structure of site pages. Although the appearance of an Internet presence site is tightly controlled, the content of the site can be dynamic and can frequently change.
For example, a corporate Internet presence site communicates important company information to customers, partners, investors, and potential employees. This includes descriptions of products and services, company news, annual reports, public filings, and job openings. As another example, an online news Internet site provides frequently updated information, together with interactive features such as stock tickers and blogs.
You can make it possible for team members to create other sites, such as Document Workspace sites, when they collaborate on documents and other projects. Similarly, you can give users of an Internet site access to collaboration sites as part of a Web-based service. For example, you can give them permissions to create Meeting Workspace sites and participate in online meetings as part of their experience of using your site.
For information about the kinds of sites you can create, see Sites and site collections overview (SharePoint Foundation 2010).
-
Determine site collections
After you determine what types of sites your solution requires, the next step is to plan how these sites are implemented across site collections. A site collection is a hierarchical set of sites that can be managed together. Sites in a site collection have common features, such as shared permissions, galleries for templates, content types, and Web Parts, and they often share a common navigation. A site is often implemented as a site collection with the top-level site as the home page of the site collection.
In general, when you plan a solution that is based on SharePoint Foundation 2010, put the following kinds of sites in separate site collections:
Internet sites (staging)
Internet sites (production)
All team sites related to a divisional site or Internet site
All sites in a site collection are stored together in the same SQL database. This can potentially affect site and server performance, depending on how your site collections and sites are structured, and depending on the purpose of the sites. Be aware of the following limits when you plan how to allocate your content across one or more site collections:
Keep extremely active sites in separate site collections. For example, a knowledge base site on the Internet that allows anonymous browsing could generate lots of database activity. If other sites use the same database, their performance could be affected. By putting the knowledge base site in a separate site collection with its own database, you can make resources available for other sites that no longer have to compete with it for database resources.
Because all content in a site collection is stored in the same content database, the performance of database operations — such as backing up and restoring content — will depend on the amount of content across the site collection; the size of the database; the speed of the servers hosting the database; and other factors. Depending on the amount of content and the configuration of the database, you might have to divide a site collection into multiple site collections to meet service-level agreements for backing up and restoring, throughput, or other requirements. It is beyond the scope of this article to provide prescriptive guidance about how to manage the size and performance of databases.
Creating too many sites below a top-level site in a site collection might affect performance and usability. Limit the number of sites of any top-level site to a maximum of 2,000.
-
Site planning data worksheet
Download an Excel version of the Site planning data worksheet (http://go.microsoft.com/fwlink/?LinkID=167838&clcid=0x409). Use this worksheet to record your site structure.
-
See Also
Sites and site collections overview (SharePoint Foundation 2010)
-
-
Site navigation overview (SharePoint Foundation 2010)
Site navigation provides the primary interface for site users to move around on the sites and pages on your site. Microsoft SharePoint Foundation 2010 includes a set of customizable and extensible navigation features that help orient users of your site so they can move around on its sites and pages. This article describes the navigation controls that are available in SharePoint Foundation 2010. It does not explain how to add navigation controls to Web pages, how to configure navigation controls, or how to create custom navigation controls.
In this article:
Navigation controls overview
-
Navigation controls overview
Navigation controls can be displayed on master pages, and—by using Web Part zones—directly in a page’s content.
SharePoint Foundation 2010 bases its navigation model on the hierarchical structure of the site collection. By using the navigation features, you can link to the following:
Sites below the current site
A site’s peer sites
Sites higher in the site structure
Web pages in a site
Additionally, you can create links to arbitrary locations, such as to an external Web site.
Navigation links in SharePoint Foundation 2010 are security-sensitive. If a site user does not have permissions to a SharePoint Foundation 2010 site or page that is linked from the site navigation, the user cannot see the link. Other content which has had links manually added to the navigation are still visible to users.
SharePoint Foundation 2010 navigation is based on the ASP.NET features in the .NET Framework version 3.5, which you can use to customize the following:
The site map provider.
The data source, which anchors and filters the structure that is provided by the site map provider.
The menus, which control the visual appearance of the navigation elements and how deep a hierarchy to display.
-
Navigation controls on master pages
A master page defines the outer frame of the Web pages in a site. Master pages contain the elements that you want all pages in your site to share, such as branding information; common commands, such as Search; and navigation elements that you want to be available throughout the site. This includes top link bar navigation, and Quick Launch navigation.
Master pages also provide the menu style of the navigation controls. You can configure master-page menu style by using Microsoft SharePoint Designer 2010 or Microsoft Visual Studio 2010.
The top link bar is a navigation menu which typically links to the sites that are one level below the current site in a site hierarchy. It is common for the top link bar to appear at the top of each page in a site. By default, all sites that are one level below the current site are added to the top link bar, and each site has its own unique top link bar for navigation. Site administrators can customize the navigation for a specific site by removing a site from the top link bar. They can also configure the top link bar so that only the home page link is shown and no other sites in the site hierarchy are displayed.
Site administrators can choose to inherit the top link bar from the parent site. This approach allows users to switch from one site to another from anywhere within the site collection, by allowing the top link bar to stay the same in all the sites in the site collection. For example, an Internet site that is used to market an organization’s products could have a site for each line of its products. By displaying each product’s site in the top link bar of each site, site designers can make it possible for users to easily switch from one site to another without having to return to the site home page.
Other top link bar configuration features include the following:
Linking to specified external sites.
Linking to specified sites or pages that are anywhere in the site.
Manually sorting the items on the top link bar.
All top link bar features, such as linking to external, can be defined uniquely for each site.
By using SharePoint Designer 2010 or Visual Studio 2010, you can additionally customize the appearance and functionality of the top link bar. For example, you can do the following:
Customize the cascading style sheets to change the appearance of the top link bar.
Modify the data source, for example to decrease the number of sites that are displayed in the top link bar.
The Quick Launch navigation typically highlights the important content in the current site, such as lists and libraries. It is common for Quick Launch navigation to appear on the left of each page in a site.
Quick Launch navigation configuration features include the following:
Linking to specific external sites or to pages in the current site.
Organizing links under headings.
Manually sorting the items in the Quick Launch navigation.
Just as you customize the top link bar, you can also customize the appearance and functionality of Quick Launch navigation by using SharePoint Designer 2010 or Visual Studio 2010.
Breadcrumb navigation displays a dynamically generated set of links at the top of Web pages, to show users their current position in the site hierarchy. By using SharePoint Designer 2010 or Visual Studio 2010, you can configure the breadcrumb navigation control. For example, you can specify a custom navigation provider.
Tree view navigation displays site content, such as lists, libraries, and sites that are below the current site, in a hierarchical structure. It is common for tree view navigation to appear on the left of each page in a site.
By default, tree view navigation is turned off. Site administrators can add tree view navigation to a site by using the Tree View page.
-
See Also
Plan site navigation (SharePoint Foundation 2010)
Sites and site collections overview (SharePoint Foundation 2010)
Plan sites and site collections (SharePoint Foundation 2010)
-
-
Plan site navigation (SharePoint Foundation 2010)
Site navigation provides the primary interface for site users to move around the sites and pages in your site. Microsoft SharePoint Foundation 2010 includes a set of navigation features that can be customized and extended to help orient the users of your site so they can move around its sites and pages. This article contains general guidance about how to plan site navigation for your SharePoint Foundation 2010 sites. This article does not describe the types of navigation controls that are available in SharePoint Foundation 2010, nor does it explain how to add navigation controls to Web pages, how to configure navigation controls, or how to create custom navigation controls. For more information about site navigation controls, see Site navigation overview (SharePoint Foundation 2010).
In this article:
Create a site navigation diagram
Understanding inherited navigation
Determine which sites inherit the top link bar
Determine which additional links to add manually to the top link bar
-
Create a site navigation diagram
Make a diagram of the sites that you want to create. For example, the following diagram is for a small travel company named Margie’s Travel. The company has a set of internal sites to help them organize their core business, which is planning conventions.

Your diagram might include a single site collection, such as the example for Margie’s Travel, or it might have multiple site collections if you have a more complex set of sites. Be sure to include all top-level Web sites, sites, Meeting Workspace or Document Workspace sites, and other sites that you plan to create, and leave room for future expansion.
You might also want to include the lists and libraries for each site, especially if you are deciding whether to create a site for document storage or one or more document libraries.
-
Understanding inherited navigation
The global navigation, or top link bar, appears at the top of all pages in the site, below the site title. By default, each site uses its own, unique top link bar, or you can decide to allow sites to inherit the top link bar from the parent site.
The top link bar can display two levels of sites in a site collection. For example, the top link bar for the Margie’s Travel site collection might contain links for Margie’s Travel Home, Office Management, Convention Planning, and Sales and Marketing. In this example, the top link bar looks like the following:
Home | Office Management | Convention Planning | Sales and Marketing
Note:
Although the top link bar can display two levels of sites, this does not mean that all sites at the second level have to be displayed on the top link bar. You can determine whether a site appears on the top link bar when you create it, or you can configure the navigation later in Site Settings.
However, by default, sites at a third level in the hierarchy do not appear on the top link bar for the top-level site, even if they inherit the navigation. For example, the Reports site would not be displayed on the top link bar of Margie’s Travel Home because it is a site that is below the Convention Planning site. If you want this site to be displayed, you can manually add it to the top link bar or create it at the second level in the site hierarchy (as a site below Margie’s Travel Home, instead of as a site below the Convention Planning site).
The top link bar cannot be shared between sites in different site collections. However, you can always manually add a link to a site in a different site collection.
-
Determine which sites inherit the top link bar
If you want the Home tab of a site to open that site’s home page instead of the inherited navigation site’s home page, then you should use unique navigation. Otherwise, you should use inherited navigation. For example, the Margie’s Travel site collection could inherit the top links among all of the second-level sites so that all sites have the same navigation:
Home | Office Management | Convention Planning | Sales and Marketing
This works for a small team, such as in Margie’s Travel, where all the users in the organization work with all the sites. Each user in the site collection uses each site so an inherited top link bar is useful. However, if the Convention Planning and Sales and Marketing teams work fairly independently and do not need access to each other’s sites, then the navigation for Margie’s Travel could be customized to be inherited at the second level, instead of the top level, as in the following:
Margie’s Travel Home site: Home | Office Management
Convention Planning site: Convention Planning | Reports
Sales and Marketing site: Sales and Marketing
Remember that the global breadcrumb navigation always contains a link back to the top-level site in the site collection. Therefore, even though users of the Convention Planning site cannot visit Margie’s Travel Home from the top link bar, they can visit it directly from the global breadcrumb navigation.
Note:
Although the choice of whether to inherit a navigation bar is made during site creation, you can change this option later. You might have to manually create links if you change your mind, but you can do so easily by using the Top Link Bar page in Site Settings for the affected sites.
-
Determine which additional links to add manually to the top link bar
Whether or not you decide to inherit the top link bar, you can customize the top link bar to include links to any other URL that you need. Depending on the extent of customization that you need, you can choose between the following methods to customize the top link bar:
If you want to add, remove, or rearrange the links in a top link bar, use the Top Link Bar page in Site Settings for the site.
If you want to create a completely customized top link bar and apply it to all sites in a site collection or to sites in a different site collection, use Microsoft SharePoint Designer 2010 or Microsoft Visual Studio 2010.
-
Determine other site navigation options
Other site navigation options that you can configure include Quick Launch and the tree view. The Quick Launch navigation typically highlights the important content in the current site.
You can customize the items that are displayed in the Quick Launch by adding new links, adding or changing headings, and changing the order in which links are displayed. To configure the Quick Launch navigation, use the Quick Launch page in Site Settings for the site.
Tree view navigation displays site content such as lists, libraries, and sites below the current site in a hierarchical manner. It is common for tree view navigation to appear on the left of each page in a site. By default, tree view navigation is turned off.
If you want to display your site content in a hierarchical way, you can display the tree view for users of your site. To enable the tree view for a site, use the Tree view page in Site Settings for the site.
-
Site planning data worksheet
Download an Excel version of the Site planning data worksheet (http://go.microsoft.com/fwlink/?LinkID=167838&clcid=0x409). Use this worksheet to help record your decisions about site navigation.
Site navigation overview (SharePoint Foundation 2010)
Sites and site collections overview (SharePoint Foundation 2010)
Plan sites and site collections (SharePoint Foundation 2010)
-
Themes overview (SharePoint Foundation 2010)
Themes provide a quick and easy way to apply colors and fonts to sites in Microsoft SharePoint Foundation 2010. When a theme is applied to a site, the color of most page elements — such as background images, text, and hyperlinks — changes. The fonts used for some page elements, such as titles, also change. Themes can be used with the standard SharePoint Foundation 2010 site templates, or with custom master pages, and then themes can be created that site owners can apply to their sites. This article includes an overview of themes and how they work. This article does not describe how to create custom themes by using Microsoft Office 2010 applications, or how to upload and manage themes in a theme library. It also does not discuss how to plan for the overall branding of sites by using master pages or cascading style sheets. For more information, see Building Block: Pages and User Interface (http://go.microsoft.com/fwlink/?LinkID=201009&clcid=0x409).
In this article:
-
About using themes
Themes enable lightweight branding of a SharePoint Foundation 2010 site by allowing a site owner or a user with designer rights to make changes to the colors and fonts of user interface elements of a site. Themes are applied directly in the user interface, and do not require knowledge of cascading style sheets or master pages.
Note:
If you apply a theme to a SharePoint Foundation 2010 site, anonymous users who browse the site will see only the default theme. To make the selected theme appear for all users, you must add a link in the master page to the generated CSS file.
An advantage of using themes is that developer resources are not needed for site owners and users with designer rights to make basic changes to a site. Themes are a simple method of branding a site; they do not affect the layout of a site.
Note:
Themes in SharePoint Foundation 2010 have been redesigned to simplify the process of generating themes. Themes created in Windows SharePoint Services 3.0 are not compatible with SharePoint Foundation 2010. If you are upgrading from Windows SharePoint Services 3.0 to SharePoint Foundation 2010, you can use Visual Upgrade to continue to use sites in the old user interface. However, we recommend that you use the new user interface in SharePoint Foundation 2010 to create themes and apply them to your sites.
-
Ways to use themes
There are two ways to use themes on a site:
Use a preinstalled theme.
Upload a custom theme to the theme library.
SharePoint Foundation 2010 comes with preinstalled themes, including the default SharePoint theme. When a new site is created, it will use the default SharePoint theme.
You can create custom themes by modifying styles in an Office 2010 application, such as Microsoft PowerPoint 2010, and saving the theme. This creates a .thmx file that you can upload to the theme gallery for a site collection. Customized themes in the theme gallery are available to all sites in that site collection.
-
See Also
-
-
Plan for using themes (SharePoint Foundation 2010)
Themes provide a quick and easy way to apply colors and fonts to sites in Microsoft SharePoint Foundation 2010. When a theme is applied to a site, the color of most page elements — such as background images, text, and hyperlinks — changes. The fonts used for some page elements, such as titles, also change. Themes can be used with the standard SharePoint Foundation 2010 site templates, or with custom master pages, and then themes can be created that site owners can apply to their sites. For more information, see Themes overview (SharePoint Foundation 2010).
This article discusses how to plan for using themes across your SharePoint Foundation 2010 sites, and includes key steps in planning to use themes for your sites. This article does not describe how to create custom themes by using Microsoft Office 2010 applications, or how to upload and manage themes in a theme library. It also does not discuss how to plan for the overall branding of sites by using master pages or cascading style sheets. For more information, see Building Block: Pages and User Interface (http://go.microsoft.com/fwlink/?LinkID=201009&clcid=0x409).
Before reading this article, be sure to read the article Plan sites and site collections (SharePoint Foundation 2010).
In this article:
About planning for using themes
Decide whether to use themes
-
About planning for using themes
There are three primary decisions to make as you plan to use themes:
Decide whether or not to use themes.
If you are going to use themes, determine how many themes are needed.
Decide who will make the custom themes.
The remainder of this article will explain these decisions and describe additional planning considerations.
-
Decide whether to use themes
The first step to planning for using themes is to decide whether or not themes are the appropriate option for your scenario. Other options for customizing a site include using an alternate CSS file and creating custom master pages. These options require the skills of either a designer or a developer to implement, and so they may not be appropriate for your scenario.
To decide whether or not to use themes, determine how much change to the existing look and feel is needed for your sites, and then choose the option that most closely fits what you want to do. You can use a combination of one or more of these options, depending on the customization that you want to do for your sites. The following table describes different levels of customization and recommends the option best suited for each level.
If you want to
Then use
Allow site owners to change colors and fonts
Themes
Make changes to other design elements such as font size and spacing
Cascading style sheets
Completely change the page structure and design
Master Pages
Note:
If you apply a theme to a SharePoint Foundation 2010 site, anonymous users who browse the site will see only the default theme. To make the selected theme appear for all users, you must add a link in the master page to the generated CSS file.
If you decide to use themes, continue reading the rest of this article.
-
Determine how many themes are needed
After deciding to use themes, you must determine how many themes are needed for your sites. Consider whether the themes that are installed with SharePoint Foundation 2010 are sufficient for your purposes, or if you will need to create custom themes to be used across sites. If you will be creating custom themes, you must also determine how many themes will be needed and decide which sites will use which themes.
Use the site planning data worksheet to record which sites should use a theme, and to determine how many unique themes are needed.
-
Decide who makes the themes
If you will be using custom themes, you must determine who will be responsible for creating the *.thmx files. Because custom themes are created in an Office 2010 application such as PowerPoint, you do not need a graphic designer to make a theme; however, you may want to include a graphic designer during the planning phase to provide guidance on color values and font styles that will be used in the themes.
You must also decide who will be responsible for uploading the themes to the theme gallery. Will the person who creates the themes also be responsible for uploading the *.thmx files to the theme gallery, or will they save the theme files to a directory for a site collection administrator to upload? A user must have either administrator or designer privileges for the site collection that contains the theme gallery in order to upload *.thmx files to the gallery.
-
Site planning data worksheet
Download an Excel version of the Site planning data worksheet (http://go.microsoft.com/fwlink/?LinkID=167838&clcid=0x409). Use this worksheet to help record your decisions about themes.
-
See Also
Themes overview (SharePoint Foundation 2010)
Sites and site collections overview (SharePoint Foundation 2010)
Plan sites and site collections (SharePoint Foundation 2010)
-
-
Plan for multilingual sites (SharePoint Foundation 2010)
Microsoft SharePoint Foundation 2010 has several features that enable you to support users in different regions or users who speak different languages. You can use these features to create Web sites in different languages.
This article discusses how to plan for multilingual SharePoint Foundation 2010 sites. This article does not describe how to create multilingual sites or how to install language packs. For information about creating multilingual sites, see Create sites in different languages from the default language (http://go.microsoft.com/fwlink/?LinkID=198972&clcid=0x409). For information about language packs, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx).
In this article:
About planning multilingual sites
Determine language and locale requirements
-
About planning multilingual sites
If your organization has to support users in different regions or users who speak different languages, you must determine what your multilingual requirements are and plan for multilingual site deployment when you plan your overall site structure and navigation.
To determine your multilingual requirements, you must:
Determine the languages and locales that you have to support.
To plan for multilingual site deployment, you must determine which language features and components to install or configure on your servers. These can include:
Language packs.
Word breaker support.
Note:
Although Windows SharePoint Services 3.0 supported internationalized domain names (IDNs), SharePoint Foundation 2010 does not. If you currently use IDNs with Windows SharePoint Services 3.0 and you plan to upgrade or migrate to SharePoint Foundation 2010, you must stop using IDNs, delete any IDN settings, and set up a non-IDN environment before you upgrade or migrate to SharePoint Foundation 2010.
-
Determine language and locale requirements
You might have to create sites in multiple languages for any of the following reasons:
You want to provide Web site content to users in different regions.
You are required by government regulation or organizational policy to provide Web site content in more than one language.
Be sure to consult all potential site owners when you determine your language requirements, and be sure to list all languages that you might have to support in the future. It is easier to install language support during initial deployment instead of waiting to install language support when your servers are running in a full production environment. After a site has been created for a specific language, the default language of the site cannot be changed. However, a user who is logged on to the site can use the multilingual user interface to select an alternative language in which to display the site. This changes the way the site user interface is displayed to the user, but it does not change the site content. For example, if the site was provisioned in French, and the Spanish language pack has also been installed on the server, a site user can change the language to Spanish so that when they view the site, the user interface will be in Spanish. This changes the user interface for that user only and does not affect how the site is displayed to other users. Also, any content that was created in French will still be displayed in French. For more information about the multilingual user interface, see Multilingual user interface overview (SharePoint Foundation 2010).
Note:
If a user changes their personal site settings to display the site in an alternative language, some site elements, such as column names, might still be displayed in the default site language.
Do not assume that you have to create a Web site or a site collection in multiple languages only because a document library contains documents in multiple languages. A document library can contain documents in multiple languages without requiring you to create Web sites or site collections in multiple languages. For example, the document library for an English site collection can contain documents that are written in French and documents that are written in Japanese.
When you are planning multilingual sites, you should also consider what locales are necessary to support your sites. Locale is a regional setting that specifies the way numbers, dates and times are displayed on a site. However, locale does not change the language in which the site is displayed. For example, selecting the Thai locale changes the default sort order of list items and uses the Buddhist calendar instead of the default calendar. The locale is a setting that is configured independently of the language specified when a site is created, but unlike the language, the locale can be changed at any time. For more information about translation of the user interface, see Determine language pack requirements.
-
Determine language pack requirements
Based on the language requirements of your Web site, determine the language packs that have to be installed on your front-end Web servers. Language packs enable you to create sites and site collections in multiple languages without requiring separate installations of SharePoint Foundation 2010. Language packs are installed on the front-end Web servers in your server farm and contain language-specific site templates. When you create a site or a site collection that is based on a language-specific site template, the user interface text that appears on the site or the site collection is displayed in the language of the specified site template. For example, when you decide to create a site in French, the toolbars, navigation bars, lists, and column headings for that site will appear in French. Likewise, if you decide to create a site in Arabic, the toolbars, navigation bars, lists, and column headings for that site will appear in Arabic, and the default left-to-right orientation of the site changes to a right-to-left orientation to properly display Arabic text.
If your site will have users who cannot work in the default language that you plan to use for the site, you should also install language packs that will enable users to work in their chosen language by using the multilingual user interface. If you do not provide support for additional languages, users might find it difficult to use site features in their non-native language. Language packs provide language-specific translation of user interface elements such as the following:
Ribbon elements
List and site column headers
Site settings interface
Templates for new lists, document libraries, and sites
Relevant search indexing of content that is not in the default language of the site.
Note:
Language packs provide translation only of the user interface. They do not translate content that is created and displayed in content pages or Web Parts.
The list of available languages that you can use to create a site or site collection, and which users can select in the multilingual user interface, is generated by the language packs that are installed on the front-end Web servers of your server farm. By default, sites and site collections are created in the language in which SharePoint Foundation 2010 was installed. For example, if you install the Spanish version of SharePoint Foundation 2010, the default language for sites, site collections, and Web pages is Spanish. If you have to create sites, site collections, or Web pages in a language other than the default SharePoint Foundation 2010 language, you must first install the language pack for that other language on the front-end Web servers before you can select another language in which to create a site. For example, if you are information about how to deploy language packs, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx).
Even though you specify a language for a site, some user interface elements such as error messages, notifications, or dialog boxes might not appear in the language that you choose. This is because SharePoint Foundation 2010 relies on several supporting technologies — such as the .NET Framework, Microsoft Windows Workflow Foundation, ASP.NET, and Microsoft SQL Server — and some of these supporting technologies are localized into only a limited number of languages. If a user interface element is generated by one of the supporting technologies, and if the supporting technology is not localized into the language that the site administrator specified for the site, the user interface element appears in English.
In addition, some text might originate from the original installation language, which can create a mixed-language experience. This type of mixed-language experience is typically seen only by content creators or site administrators and is not seen by site users.running the French version of SharePoint Foundation 2010 and you want to create sites in French, English, and Spanish, then you must install the English and Spanish language packs on the front-end Web servers before you can create the English and Spanish sites.
Language packs for SharePoint Foundation 2010 are not bundled or grouped into multilingual installation packages: you must install a specific language pack for each language that you want to support. Also, language packs must be installed on every front-end Web server in the server farm to ensure that each Web server can render content in the specified language. For information about what language packs are available, see Language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/3d599354-863e-4528-9fe8-867df5f45658(Office.14).aspx).
Note:
Error logs that SharePoint Foundation 2010 stores on the server are always in English.
For more information about installing language packs, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx).
-
Determine requirements for word breakers and stemmers
Word breakers and stemmers are components that are part of the indexing and querying processes. A word breaker is a component that is used to break strings of text into individual words during the indexing and querying processes. A stemmer is a component that finds the root word of a term and can also generate variations of that term. The rules for word breaking and stemming differ for different languages, and you can specify different rules for different languages. Word breakers for each language enable the resulting terms to be more accurate for that language. Where there is a word breaker for a language family, but not for a specific sub-language, the major language is used. For example, the French word breaker is used to handle text that is French Canadian. If no word breaker is available for a particular language, the neutral word breaker is used. With the neutral word breaker, words are broken at neutral characters such as spaces and punctuation marks.
If you install any language packs or supplemental language support, we recommend that you install the appropriate word breaker and stemmer for each of the languages that you have to support. Word breakers and stemmers must be installed on all servers that are running the Search service. For a list of the languages for which SharePoint Foundation 2010 provides word breakers and stemmers, see Languages for word breakers and stemmers (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx).
-
See Also
Multilingual user interface overview (SharePoint Foundation 2010)
Plan for the multilingual user interface (SharePoint Foundation 2010)
-
-
Multilingual user interface overview (SharePoint Foundation 2010)
This article discusses the new multilingual user interface feature in Microsoft SharePoint Foundation 2010. Previously, in Windows SharePoint Services 3.0, when you created a site collection or site, if language packs were installed on the server, you could also choose the language in which to display the site user interface. However, after the language for a site had been set, it could not be changed. The multilingual user interface feature introduces the concept of secondary languages that users can select. This feature is used to display the site user interface in a secondary language that the user selects and that is different from the primary language that was chosen when the site was created.
This article describes the multilingual user interface in SharePoint Foundation 2010. This article does not describe how to deploy the language packs that are required to use the multilingual user interface or how to configure site settings to enable users to set their preferred language. It also does not discuss how to plan for using the multilingual user interface in your site solution. For information about how to let individual users change the language that is used to display their site’s user interface, see Make multiple languages available for your site’s user interface (http://go.microsoft.com/fwlink/?LinkID=198970&clcid=0x409). For more information about planning to use the multilingual user interface, see Plan for the multilingual user interface (SharePoint Foundation 2010).
In this article:
Use and benefits of the multilingual user interface
How the multilingual user interface works
What is supported by the multilingual user interface
Adding and modifying application content
-
Use and benefits of the multilingual user interface
The multilingual user interface enables users to collaborate in a single site by using their selected secondary language, regardless of which language was selected when the site was created. When you create a new site, if language packs have been installed on the server, you can specify the primary language for the site. The site will use that primary language to display the site user interface, such as site navigation and administrative pages. If you want site users to be able to view the site user interface in a secondary language, you can specify which languages are available to users by using the Language Settings page. A user who is logged on to the site can use the Select Display Language option on the user menu to select a secondary language in which to display the site user interface. After the user selects a language, all sites within that domain name are displayed in their preferred language. However, this does not change the default, primary language of the site. Other users who view the site still see the site user interface displayed in the primary language. The site user interface is changed only for those users who have selected a different, secondary language in which to display the site.
By using the multilingual user interface, team members can work on documents and projects in a shared, common language, while they are viewing the site and performing tasks in their preferred language. In addition to team collaboration, the multilingual user interface enables farm and site administrators to perform administrative tasks in their preferred language. For example, farm administrators can change the primary language of the Central Administration Web site so that the administrative links and instructions are displayed in their preferred language.
Note:
The multilingual user interface displays only site user interface elements in another language. It does not translate or display content such as documents or list items in another language.
In addition to letting users change the primary language for a site, the multilingual user interface also enables users to make changes to new and existing application content, such as list or library titles and descriptions, and it enables users to have those changes be reflected in the user interface for other users of other languages. For example, a team member who uses English as the preferred language creates a new document library named “Team Reports.” Another team member who has the preferred language set to German, logs on to the site and changes the library title to “Mannschaftsberichte.” The next time that a user, who has the preferred language set to German, logs on to the site, the name of the document library is displayed as “Mannschaftsberichte.” However, a user who has the preferred language set to English still sees the document library name displayed as “Team Reports.”
SharePoint Foundation 2010 provides three methods that you can use to translate certain application content, such as list or library titles and descriptions: by using the user interface, by exporting and importing translations for a site, and by using the object model.
-
How the multilingual user interface works
By default, when a new site is created, it is created in the default language of the SharePoint Foundation 2010 installation on the server. A farm administrator must install language packs on the server before sites can be created in languages other than the default language. For more information, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx).
After language packs have been installed on the server, the Language Settings link is added to the Site Settings page. Site administrators use the Language Settings page to specify which secondary languages the site will support. After the site administrator has enabled secondary languages for a site, users can log on to the site and use the Select Display Language option on the user menu to change the display language when they browse to any page in the site collection. When a user changes the display language of a page, the new display language becomes the user’s preferred language for the whole site collection.
SharePoint Foundation 2010 selects the language in which to display pages of a site collection by using the first of the following rules that applies:
1. Does the user have a preferred language for this site collection on this computer? If so, use the user’s preferred language.
2. Is the language preference that is specified in the Web browser one of the supported languages for the page? If so, use the preferred language of the browser.
3. Otherwise, use the default language for the site collection.
SharePoint Foundation 2010 provides three methods that you can use to modify certain application content, such as list or library titles and descriptions: by using the user interface, by exporting and importing translations for a site, and by using the SPUserResource class in the Microsoft.SharePoint namespace. Not all user interface elements can be changed directly in the user interface. For example, user actions and commands can be changed only by using the SPUserResource class. For more information, see SPUserResource class (http://go.microsoft.com/fwlink/?LinkID=193203&clcid=0x409).
-
What is supported by the multilingual user interface
When a user views a site in a secondary language, certain elements of the user interface are provided in the preferred language. The following list includes examples of items that are supported by the multilingual user interface:
Settings pages, such as those in the _layouts and the _admin virtual directories.
Help.
Application content, such as menus, controls, site actions, site title and description, list or library titles and descriptions, top link bar links, Quick Launch links, local breadcrumbs, site and list content types, and site and list columns.
Developer content, such as features, and solutions.
However, not all user interface elements are translated. The following list includes examples of items that are not supported by the multilingual user interface:
Web Parts (except those that are linked to lists or libraries).
Global breadcrumbs.
User created content, such as list item data, documents and Web pages in libraries, permissions levels, groups, views, and Web Parts.
Although most site templates are supported by the multilingual user interface, the following site templates are not supported:
The Blog template.
Any of the meeting workspace templates.
Any of the Web database templates.
-
Adding and modifying application content
A user can add or modify application content, such as list titles or column names and descriptions, in one of two ways: by adding or modifying content in the primary language or by adding or modifying content in one or more secondary languages.
When a user views a site by using the primary language of the site, any new application content that is created is displayed in the primary language, even when the site is viewed in a secondary language. For example, if the primary language for a site is English, when a user views the site in the primary language and creates a new document library called “Team Documents”, the library title is still displayed as “Team Documents” when a user views the site in any secondary language. To translate new user interface strings into a secondary language, a user must change the user preferences to display the site in a secondary language and then make the change to the user interface element.
When a user views a site by using a secondary language, any new application content that is created is displayed in that language even when the site is viewed in the primary language or in any other secondary language. For example, if the primary language for a site is English, and a user views the site in German and adds a document library called “Mannschaftsdokumente”, the library title is displayed as “Mannschaftsdokumente” even when the site is viewed in English. To translate new user interface strings into the primary language or to other secondary languages, the user must change the user preferences to display the site in the required language and then make the change to the user interface. The Language Settings page contains an Overwrite Translations option that affects how changes to existing application content are made to other languages for the site. If the Overwrite Translations option is enabled, any changes that are made to the user interface in the primary language overwrite any changes that have been made to user interface elements in secondary languages.
By default, when a user views a site by using the primary language of the site, any changes that are made to existing application content are changed for that language only. The strings that are associated with that user interface element in the secondary languages remain unchanged. However, if the Overwrite Translations option is enabled, the strings that are associated with that user interface element for every language are replaced with the new primary language string. For example, if the primary language for a site is English, and a user changes the title of the “Shared Documents” library to “Team Documents”, by default, the title is changed only for the primary language of the site. However, if the Overwrite Translations option is enabled, the title is changed to “Team Documents” for every secondary language, and it must be retranslated.
When a user views a site by using a secondary language, any changes that are made to existing application content are changed for that language only. The strings that are associated with that user interface element in the primary language and other secondary languages remain unchanged. To translate user interface strings into the primary language, or to other secondary languages, the user must change the user preferences to display the site in the required language and then make the change to the user interface.
-
Exporting and importing translated content
The multilingual user interface feature lets you export and import application content for bulk translation. Instead of translating application content one item at a time, you can export the strings for any new or modified application content in the primary language or in one of the secondary languages. To export content, you use the Export Translations link on the Site Settings page. When you export application content for a secondary language, you can decide to export all content or only content that has not been translated.
When the application content is exported, it is saved as a .resx file, which can be opened by using a text editor or any third-party tool that can open resource files. For more information, see Resources in .Resx File Format (http://go.microsoft.com/fwlink/?LinkID=193206&clcid=0x409). After the resource strings have been translated, you use the Import Translations link on the Site Settings page to import the .resx file.
-
Limitations of the multilingual user interface
As mentioned previously, not all user interface elements are supported by the multilingual user interface. The following list describes additional limitations that apply when you use the multilingual user interface:
Search Search indexes content in the default language of the SharePoint installation. Even if content is provided in secondary languages, that content is only searchable by using the default language of the site. For example, if your preferred language is German, but the primary language for the site is English, a search for “Freigegebene Dokumente” does not return any search results. However, a search for “Shared Documents” does return search results.
Web Parts Web Part titles and descriptions do not change in the user interface, unless a Web Part is a list-based Web Part. For example, the title and description for Web Parts that display list and library data, such as Announcements and Shared Documents, are displayed in a user’s preferred language, whereas the title and description for other Web Parts, such as the Content Editor and the Content Query Web Parts, are displayed only in the primary site language.
-
See Also
Plan for the multilingual user interface (SharePoint Foundation 2010)
-
-
Plan for the multilingual user interface (SharePoint Foundation 2010)
The new multilingual user interface feature in Microsoft SharePoint Foundation 2010 introduces the concept of a secondary language that the user can select. This feature displays the site user interface in a secondary language that the user selects and that is different from the primary language that was chosen when the site was created.
This article describes how to plan for using the multilingual user interface in your SharePoint Foundation 2010 site solution. This article does not describe how to deploy the language packs that are required to use the multilingual user interface or how to configure site settings to enable users to set their preferred language. For information about how to let individual users change the language that is used to display their site’s user interface, see Make multiple languages available for your site’s user interface (http://go.microsoft.com/fwlink/?LinkID=198970&clcid=0x409). For more information about the multilingual user interface, see Multilingual user interface overview (SharePoint Foundation 2010).
In this article:
Determine language requirements for your sites
-
Determine language requirements for your sites
Before you can use the multilingual user interface in your SharePoint sites, the farm administrator must deploy language packs to the server so that they are available for use on sites. Decide which language packs are needed and when they will be deployed to the server. Site administrators must configure the language settings for individual sites to make specific languages available to site users. You should decide which languages are needed for each site and plan to have the site administrators enable specific languages for the sites they manage. For information about planning multilingual sites, see Plan for multilingual sites (SharePoint Foundation 2010). For information about deploying language packs, see Deploy language packs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/bd2a9863-954a-4e44-bafc-af8c9599cb47(Office.14).aspx).
-
Plan for translating content
If you will enable the multilingual user interface on your site to provide users a way to collaborate while they are using their preferred language, you must decide whether using the default multilingual user interface will be sufficient or whether application content will have to be translated. If you have application content that has to be translated, you should consider the following questions:
How will new and existing application content be translated? Will individual team members translate application content directly in the user interface as it becomes necessary, or will you export resource files in the languages that are needed for the site and have them all translated at once? If users create new application content in a secondary language, you must plan for who will translate that content into the primary language of the site and for the other secondary languages. If you plan to create complex pages, such as new menu pages, or develop custom solutions, such as features that create lists, you must plan to use the object model to provide translations in secondary languages.
Who will translate the application content? Will the translation of resource files be done by someone within your organization, or will you need to have a third-party translate them for you?
How will updates to the application content be handled? Will changes to the user interface be translated as changes are made, or will changes be made on a periodic schedule? This might depend on the size and scale of the sites and the content that is included.
How should translation overwrites be handled? Do you want changes in the primary language to overwrite string values in secondary languages? If so, then you must enable the Overwrite Translations option on the Language Settings page.
What column names must be changed? What column names must be translated, and for which languages? Will the column names be at the list level or at the site level?
-
Plan for installing service packs
If language packs are updated as part of a service pack release for SharePoint, you must update the language packs on the server when the service pack is installed. You should plan to coordinate with the farm administrator to monitor the release of service packs and any associated language packs so that you are aware of updated language packs that need to be installed for your users.
-
See Also
Multilingual user interface overview (SharePoint Foundation 2010)
-
-
Security planning for sites and content (SharePoint Foundation 2010)
Some of the sites in your enterprise probably contain content that should not be available to all users. For example, proprietary technical information should be accessible only on a need-to-know basis. An intranet portal for employee benefits should be available only to full-time employees, whereas the home page of an Internet Web site is accessible by anonymous clients.
Permissions control access to your sites and site content. You can manage permissions by using Microsoft SharePoint Foundation 2010 groups, which control membership, and fine-grained permissions, which help to secure content at the item and document level. This section describes permissions for sites and site content and provides considerations for choosing permissions.
In this section:
Plan site permissions (SharePoint Foundation 2010) helps you understand how permissions are assigned and helps you choose the appropriate permissions to use in your site collection or subsite.
Determine permission levels and groups (SharePoint Foundation) reviews the available permission levels and groups, and helps you determine whether you need additional permission levels or groups.
Choose security groups (SharePoint Foundation 2010) helps you determine which Microsoft Windows security groups and user accounts to use to grant access to sites, decide whether to use the Authenticated Users group, and decide whether to allow anonymous access.
Choose administrators and owners for the administration hierarchy (SharePoint Foundation 2010) defines the levels of administration from the server level to the subsite level and helps you choose administrators for each level.
Best practices for using fine-grained permissions (white paper) (SharePoint Foundation 2010) provides guidance for using fine-grained permissions in SharePoint 2010 Products.
-
Plan site permissions (SharePoint Foundation 2010)
This article helps you plan access control at the site collection, site, and subsite levels. This article also describes permission inheritance and fine-grained permissions, and explains how to determine effective permissions for users and groups at different scopes within a site collection hierarchy.
In this article:
Permission inheritance and fine-grained permissions
-
Introduction
Site and content access is controlled by giving users and groups a set of permissions for a specific site, list or library, folder, document, or item. When you develop your plan for site and content access, you should consider the following issues:
How tightly you want to control permissions for the site or site content. For example, you might want to control access at the site level, or you might need more restrictive security settings for a specific list, folder, or item.
How to use groups to categorize and manage your users. Groups have no permissions until they are assigned a permission level for a specific site or for specific site content. When you assign permission levels to SharePoint groups at the site collection level, by default, all sites and site content inherit those permission levels. For more information about categorizing users into groups, see “Choose security groups”.
This article describes site permissions and helps you determine which sites or site content will require unique permissions. This article does not address planning the security of your entire server or server farm.
-
About site permissions
You should understand the following concepts before you configure access to sites and site content:
Individual user permissions Individual permissions grant a user the ability to perform specific actions. For example, the View Items permission grants the user the ability to view items in a list or folder, but not to add or remove items. For information about available permissions, see User permissions and permission levels (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7238eb84-12d3-4323-a65c-277016f8bc4d(Office.14).aspx).
Permission level This set of permissions grants users permission to perform a set of related tasks. For example, the Read permission level includes the View Items, Open Items, View Pages, and View Versions permissions (and others), all of which are needed to read documents, items, and pages of a SharePoint site. Individual permissions can be included in more than one permission level. Permission levels can be customized by anyone assigned to a permission level that includes the Manage Permissions permission. The default permission levels are Limited Access, Read, Contribute, Design, and Full Control. For information about default permission levels and the permissions included in each level, see User permissions and permission levels (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7238eb84-12d3-4323-a65c-277016f8bc4d(Office.14).aspx).
Group A group can be either a Windows security group or a group, such as Site Owners, Site Members, or Site Visitors. Groups are created and managed at the site collection level. Each SharePoint group is assigned a default permission level, but the permission level for any group can be customized. Anyone assigned to a permission level that includes the Create Groups permission, which is included in the Full Control permission level by default, can create custom SharePoint groups.
User A user is a person with a user account that can be authenticated by the same authentication method that was used for the server. We recommend that you assign permissions to groups instead of users, although you can directly give individual users permissions to a site or specific site content or directly assign a permission level to a user. Because it is inefficient to maintain individual user accounts, you should assign permissions on a per-user basis only as an exception. For more information about user account types, see User permissions and permission levels (SharePoint Foundation 2010) (http://technet.microsoft.com/library/7238eb84-12d3-4323-a65c-277016f8bc4d(Office.14).aspx).
Securable object A securable object is a site, list, library, folder, document, or item for which permission levels can be assigned to users or groups. By default, all lists and libraries within a site inherit permissions from the site. You can use list-level, folder-level, and item-level permissions to additionally control which users can view or interact with site content. For example, if a permission level for a specific securable object includes the Manage Permissions permission, anyone who is assigned that permission level can change the permissions for that securable object. You can resume inheriting permissions from a parent list, the site as a whole, or a parent site at any time.
-
About assigning permissions
You can assign a user or group a permission level for a specific securable object. Individual users or groups can have different permission levels for different securable objects.
-
About permission inheritance
Permissions on securable objects within a site are inherited from the site itself by default. You can use fine-grained permissions — unique permissions on the list or library, folder, or item or document level — to gain more control of the actions users can take on your site.
You can break permission inheritance for any securable object at a lower level in the site hierarchy by creating a fine-grained permission on that securable object. For example, you can edit the permissions for a document library, which breaks the inheritance from the site. However, the inheritance is broken only for the specific securable object for which you changed permissions; the rest of the site’s permissions are unchanged. You can resume inheriting permissions from the parent list or site at any time.
Tip:
If you are using fine-grained permissions, you should use groups to avoid having to track individual user accounts. For example, because people move in and out of teams and change responsibilities frequently, tracking those changes and updating the permissions for uniquely secured objects would be time-consuming and error-prone.
The following securable objects can accept fine-grained permission assignments:
Site: Controls access to the site as a whole.
List or library: Controls access to a specific list or library.
Folder: Controls access to folder properties (such as the name of the folder).
Item or document: Controls access to a specific list item or document.
Inheriting permissions is the default behavior and is the easiest way to manage a group of Web sites. However, if a subsite inherits permissions from its parent, that set of permissions is shared with the parent. If the subsite’s owners edit its permissions, the site’s permissions will also change, which could compromise security or prevent users from accessing content.
If you want to change permissions for the subsite only, you must first stop inheriting permissions from the site and then create fine-grained permissions on the subsite. For example, if specific lists, libraries, folders, items, or documents contain sensitive data that requires an increased level of protection, you can create fine-grained permissions for a specific group or individual user who requires access.
Creating unique permissions copies the groups, users, and permission levels from the parent site to the subsite and then breaks the inheritance. If you restore inherited permissions, the subsite will inherit its users, groups, and permission levels from the parent site again, and you will lose any users, groups, or permission levels that were unique to the subsite.
Note:
As a best practice, you should arrange sites and subsites so they can share most of their permissions, and do the same for lists and libraries. Place any sensitive data into separate lists, libraries, or subsites.
-
About effective permissions
Configuring security settings or performing bulk operations requires accurate information about user and group permissions on site resources. For example, many SharePoint sites give all authenticated users (the NTAUTHORITY\AUTHENTICATED USERS domain group) access to at least some site content. If you want to additionally restrict access, you must determine exactly which permissions authenticated users have, and on which site content.
Tracing inherited permissions and areas where inheritance is broken complicates the process of determining the correct permissions. Microsoft SharePoint Foundation 2010 uses effective permissions to determine a user or group’s permissions on all resources within a site collection. You can now find both the user’s directly assigned permissions and the permissions assigned to any groups of which the user is a member.
Important:
Effective permissions make it easier to find permissions in a site collection. However, they should never be used as a substitute for a carefully planned permissions structure.
-
Choose permission levels
When you create permissions, you must balance ease of administration and performance against the need to control access to individual items. If you use fine-grained permissions extensively, you will spend more time managing the permissions, and users may experience slower performance when they try to access site content.
Use the following guidelines to configure site permissions:
Follow the principle of least privilege: Users should have only the permission levels or individual permissions they need to perform their assigned tasks.
Use standard groups (such as Members, Visitors, and Owners) and control permissions at the site level.
Make most users members of the Members or Visitors groups. By default, users in the Members group can contribute to the site by adding or removing items or documents, but cannot change the structure, site settings, or appearance of the site. The Visitors group has read-only access to the site, which means that they can see pages and items, and open items and documents, but cannot add or remove pages, items, or documents.
Limit the number of people in the Owners group. Only those users you trust to change the structure, settings, or appearance of the site should be in the Owners group.
You can create additional SharePoint groups and permission levels if you need more control over the actions that your users can take. For example, if you do not want the Read permission level on a specific subsite to include the Create Alerts permission, break the inheritance and customize the Read permission level for that subsite.
-
Plan for permission inheritance
It is much easier to manage permissions when there is a clear hierarchy of permissions and inherited permissions. It becomes more difficult when some lists within a site have fine-grained permissions applied, and when some sites have subsites with unique permissions and others with inherited permissions.
For example, it is much easier to manage a site that has permission inheritance, as shown in the following table.
Securable object
Description
Unique or inherited permissions
SiteA
Group home page
Unique
SiteA/SubsiteA
Sensitive group
Unique
SiteA/SubsiteA/ListA
Sensitive data
Unique
SiteA/SubsiteA/LibraryA
Sensitive documents
Unique
SiteA/SubsiteB
Group shared project information
Inherited
SiteA/SubsiteB/ListB
Non-sensitive data
Inherited
SiteA/SubsiteB/LibraryB
Non-sensitive documents
Inherited
However, it is not as easy to manage a site that has permission inheritance, as shown in the following table.
Securable object
Description
Unique or inherited permissions
SiteA
Group home page
Unique
SiteA/SubsiteA
Sensitive group
Unique
SiteA/SubsiteA/ListA
Non-sensitive data
Unique, but same permissions as SiteA
SiteA/SubsiteA/LibraryA
Non-sensitive documents, but with one or two sensitive documents
Inherited, with unique permissions at the document level
SiteA/SubsiteB
Group shared project information
Inherited
SiteA/SubsiteB/ListB
Non-sensitive data, but with one or two sensitive items
Inherited, with unique permissions at the item level
SiteA/SubsiteB/LibraryB
Non-sensitive documents, but with a special folder that contains sensitive documents
Inherited, with unique permissions at the folder and document level
-
Determine permission levels and groups (SharePoint Foundation)
This article reviews the default groups and permission levels and helps you decide whether to use them, customize them, or add new groups and permission levels to promote security.
In this article:
Review available default groups
Review available permission levels
Determine whether you need additional permission levels or groups
The most important decision about your site and content security in Microsoft SharePoint Foundation 2010 is to decide how to categorize your users and what permission levels to assign.
There are several default SharePoint groups that are intended to help you categorize your users based on the kinds of actions they need to perform, but you might have unique requirements or other ways of looking at sets of users. Likewise, there are default permission levels, but they might not always align exactly with the tasks that your groups need to perform.
In this article, you review the default groups and permission levels and decide whether to use them as they are, customize them, or create different groups and permission levels.
-
Review available default groups
With SharePoint groups, you manage sets of users instead of individual users. SharePoint groups can be composed of many individual users, can hold a single Windows security group, or can be some combination of the two. SharePoint groups confer no specific rights to the site; they are merely a way to contain a set of users. You can organize users into any number of groups, depending on the size and complexity of your organization or Web site.
The following table shows the default groups that are created for sites in SharePoint Foundation 2010.
Group name
Default permission level
<Site name> Visitors
Read
<Site name> Members
Contribute
<Site name> Owners
Full Control
In addition, the following special users and groups are available for higher-level administration tasks:
Site collection administrators You can designate one or more users as primary and secondary site collection administrators. These users are recorded in the database as the contacts for the site collection, have full control of all sites within the site collection, can audit all site content, and receive any administrative alerts (such as verifying whether the site is still being used). Generally, you designate site collection administrators when you create the site, but you can change them as needed by using the Central Administration site or Site Settings pages.
Farm administrators Controls which users can manage server and server farm settings. The Farm Administrators group replaces the need for adding users to the Administrators group for the server. Farm administrators have no access to site content by default; they must take ownership of the site to view any content. They do this by adding themselves as site collection administrators, which action is recorded in the audit logs. The Farm Administrators group is used in Central Administration only, and is not available for any sites.
Administrators Members of the Administrators group on the local server can perform all farm administrator actions and more, including the following:
Installing new products or applications.
Deploying Web Parts and new features to the global assembly cache.
Creating new Web applications and new IIS Web sites.
Starting services.
Like the Farm Administrators group, members of the Administrators group on the local server have no access to site content, by default.
After you determine the groups you need, determine the permission levels to assign to each group on your site.
-
Review available permission levels
The ability to view, change, or manage a particular site is determined by the permission level that you assign to a user or group. This permission level controls all permissions for the site and for any subsites, lists, document libraries, folders, and items or documents that inherit the site’s permissions. Without the appropriate permission levels, your users might be unable to perform their tasks, or they might be able to perform tasks that you did not intend them to perform.
By default, the following permission levels are available:
Limited Access Includes permissions that enable users to view specific lists, document libraries, list items, folders, or documents when granted permissions.
Read Includes permissions that enable users to view items on the site pages.
Contribute Includes permissions that enable users to add or change items on the site pages or in lists and document libraries.
Design Includes permissions that enable users to change the layout of site pages by using the browser or Microsoft Office SharePoint Designer 2007.
Full Control Includes all permissions.
-
Determine whether you need additional permission levels or groups
The default groups and permission levels provide a general framework for permissions, covering many different organization types and roles within those organizations. However, they might not map exactly to how your users are organized or to the many different tasks that your users perform on your sites. If the default groups and permission levels do not suit your organization, you can create custom groups, change the permissions included in specific permission levels, or create custom permission levels.
-
Do you need custom groups?
The decision to create custom groups is fairly straightforward and has little effect on your site’s security. Essentially, you should create custom groups instead of using the default groups if any of the following applies:
You have more (or fewer) user roles within your organization than are apparent in the default groups. For example, if in addition to Designers, you have a set of people who are tasked with publishing content to the site, you might want to create a Publishers group.
There are well-known names for unique roles within your organization that perform very different tasks in the sites. For example, if you are creating a public site to sell your organization’s products, you might want to create a Customers group that replaces Visitors or Viewers.
You want to preserve a one-to-one relationship between Windows security groups and the SharePoint groups. (For example, your organization has a security group for Web Site Managers, and you want to use that name as a group name for easy identification when managing the site).
You prefer other group names.
-
Do you need custom permission levels?
The decision to customize permission levels is less straightforward than the decision to customize SharePoint groups. If you customize the permissions assigned to a permission level, you must keep track of that change, verify that it works for all groups and sites affected by that change, and ensure that the change does not negatively affect your security or your server capacity or performance.
For example, regarding security, if you customize the Contribute permission level to include the Create Subsites permission that is typically part of the Full Control permission level, Contributors can create and own subsites, potentially inviting malicious users to their subsites or posting unapproved content. Or, regarding capacity, if you change the Read permission level to include the Create Alerts permission that is typically part of the Contribute permission level, all members of the Visitors group can create alerts, which might overload your servers.
You should customize the default permission levels if either of the following situations applies:
A default permission level includes all permissions except one that your users need to do their jobs, and you want to add that permission.
A default permission level includes a permission that your users do not need.
Note:
You should not customize the default permission levels if your organization has security or other concerns about a particular permission and wants to make that permission unavailable for all users assigned to the permission level or levels that include that permission. In this case, you should turn off this permission for all Web applications in your server farm, rather than change all of the permission levels.
If you need to make several changes to a particular permission level, it is better to create a custom permission level that includes all of the permissions you need.
You might want to create additional permission levels if either of the following situations applies:
You want to exclude several permissions from a particular permission level.
You want to define a unique set of permissions for a new permission level.
To create a permission level, you can copy an existing permission level and then make changes, or you can create a permission level and then select the permissions that you want to include.
Note:
Some permissions depend on other permissions. If you clear a permission that another permission depends on, the other permission is also cleared.
-
Choose security groups (SharePoint Foundation 2010)
This article describes the security and distribution groups that are included in Active Directory Domain Services (AD°DS). This article also provides recommendations for using those groups to organize the users of your SharePoint sites.
In this article:
Determine which Windows security groups and accounts to use for granting access to sites
Decide whether to allow access for all authenticated users
-
Introduction
Managing users of SharePoint sites is easier if you assign site permissions to groups instead of to individual users. In AD°DS, the following groups are typically used to organize users:
Distribution group A group that is used only for e-mail distribution and that is not security-enabled. Distribution groups cannot be listed in discretionary access control lists (DACLs), which are used to define permissions on resources and objects.
Security group A group that can be listed in DACLs. A security group can also be used as an e-mail entity.
You can use security groups to control permissions for your site by directly adding the security group to the site and granting permissions to the entire group. You cannot directly add distribution groups, but you can expand a distribution group and add the individual members to a SharePoint group. If you use this method, you must manually keep the SharePoint group synchronized with the distribution group. If you use security groups, you do not need to manage the individual users in the SharePoint application. Because you included the security group itself and not the individual members of the group, AD°DS manages the users for you.
Note
Security groups that contain the following items may be more difficult to manage:
-
Determine which Windows security groups and accounts to use for granting access to sites
Each organization sets up its Windows security groups differently. For easier permission management, security groups should be:
Large and stable enough that you are not continually adding groups to your SharePoint sites.
Small enough that you can assign appropriate permissions.
For example, a security group called “all users in building 2” is probably not small enough to assign permissions, unless all users in building 2 have the same job function, such as accounts receivable clerks. This is rarely the case, so you should look for a smaller, more specific set of users, such as “Accounts Receivable.”
-
Decide whether to allow access for all authenticated users
If you want all users within your domain to be able to view content on your site, consider granting access to all authenticated users (the Domain Users Windows security group). This special group enables all members of your domain to access a Web site (at the permission level that you choose), without your having to enable anonymous access.
-
Decide whether to allow access for anonymous users
You can enable anonymous access to let users view pages anonymously. Most Internet Web sites allow for anonymous viewing of a site, but might ask for authentication when someone wants to edit the site or buy an item on a shopping site. Anonymous access must be granted at the Web application level at the time that the Web application is created.
If anonymous access is enabled for the Web application, site administrators can decide whether to:
Grant anonymous access to a site.
Grant anonymous access only to lists and libraries.
Block anonymous access to a site completely.
Anonymous access relies on the anonymous user account on the Web server. This account is created and maintained by Internet Information Services (IIS), not by your SharePoint site. By default in IIS, the anonymous user account is IUSR. When you enable anonymous access, you are in effect granting that account access to the SharePoint site. Allowing access to a site, or to lists and libraries, grants the View Items permission to the anonymous user account. However, even with the View Items permission, there are restrictions to what anonymous users can do. Anonymous users cannot:
Open sites for editing in Microsoft SharePoint Designer 2010; in other words, they cannot use remote procedure call (RPC).
View sites in My Network Places; in other words, they cannot use Web Distributed Authoring and Versioning (WebDAV), the Web Folders protocol in Windows.
Upload or edit documents in document libraries, including wiki libraries.
Important:
To improve security for sites, lists, or libraries, do not enable anonymous access. Enabling anonymous access lets users contribute to lists, discussions, and surveys, possibly using up server disk space and other resources. Anonymous access also allows for anonymous users to discover site information, including user e-mail addresses and any content posted to lists, and libraries, and discussions.
You can set permission policies for the anonymous user for different zones (Internet, Extranet, Intranet, Other) if you have the same Web application serving content in those different zones. The policies are described in the following list:
None No policy. This is the default option. No additional permission restrictions or additions are applied to site anonymous users.
Read Anonymous users can read content, unless the site administrator turns off anonymous access.
Deny Write Anonymous users cannot write content, even if the site administrator specifically attempts to grant the anonymous user account that permission.
Deny All Anonymous users cannot have any access, even if site administrators specifically attempt to grant the anonymous user account access to their sites.
-
Choose administrators and owners for the administration hierarchy (SharePoint Foundation 2010)
This article describes the administrator roles that correspond to the Microsoft SharePoint Foundation 2010 server and site hierarchy. Many people can be involved in managing SharePoint Foundation 2010. Administration of SharePoint Foundation 2010 occurs at the following levels:
Server farm
Shared services
Sites
Document library or list
Individual items
In this article:
-
Introduction
Most levels of the server and site hierarchy have a corresponding administration group. The Web application level does not have a unique administrator group, but farm administrators control the Web applications within their scope. Members of the Farm Administrators group and members of the Administrators group on the local server can define a policy to grant individual users permissions at the Web application level.
-
Levels of administration
The following groups of users have administrative permissions at different levels of the administration hierarchy:
Server or server farm level
Farm Administrators group Members of the Farm Administrators group have permissions to and responsibility for all servers in the server farm. Members can perform all administrative tasks in Central Administration for the server or server farm. Members of this group can also use Windows PowerShell to create and manage configuration database objects. They can assign administrators to manage service applications, which are instances of shared services. This group does not have access to individual sites or their content.
Administrators group Members of the Administrators group on the local server can perform all farm administrator actions. Administrators on the local server can perform additional tasks, such as installing new products or applications, deploying Web Parts and new features to the global assembly cache, creating new Web applications and new Internet Information Services (IIS) Web sites, and starting services. Like farm administrators, members of this group on the local server have no access to site content, by default.
Note:
Farm administrators and local administrators can take ownership of specific site collections, if it is necessary. For example, if a site administrator leaves the organization and a new administrator must be added, the farm administrator or a member of the local Administrators group can take ownership of the site collection to make the change.
Shared services level
Service application administrators These administrators are delegated by the farm administrator. They can configure settings for a specific service application within a farm. However, these administrators cannot create service applications, access any other service applications in the farm, or perform any farm-level operations, including topology changes. For example, the service application administrator for a Search service application in a farm can configure settings for that Search service application only.
Feature administrators A feature administrator is associated with a specific feature or features of a service application. These administrators can manage a subset of service application settings, but not the entire service application. For example, a Feature administrator might manage the Audiences feature of the User Profile service application.
Site level
Site collection administrators These administrators have the Full Control permission level on all Web sites within a site collection. They have access to content in all sites in that site collection, even if they do not have explicit permissions on that site.
Site owners By default, members of the Owners group for a site have the Full Control permission level on that site. They can perform administration tasks for the site, and for any list or library within that site. They receive e-mail notifications for events, such as the pending automatic deletion of inactive sites and requests for site access.
-
Best practices for using fine-grained permissions (white paper) (SharePoint Foundation 2010)
This white paper describes best practices for fine-grained permissions (FGP) and how to use them within your organization when implementing Microsoft SharePoint Foundation 2010.
Download the white paper from the following link: http://go.microsoft.com/fwlink/?LinkId=201596 (http://go.microsoft.com/fwlink/?LinkId=201596)
-
Sandboxed solutions planning (SharePoint Foundation 2010)
Sandboxed solutions restrict access to network and local resources to provide greater security and stability. You can use sandboxed solutions for load balancing solutions, for solutions that have not been fully tested, and for deploying user solutions in a hosted environment. Sandboxed solutions run in a separate worker thread so that they cannot access resources that belong to other solutions, and they have limited access to local and network resources.
-
In this section
-
Sandboxed solutions overview (SharePoint Foundation 2010)
You can deploy a Microsoft SharePoint Foundation 2010 solution directly onto your SharePoint Foundation farm, or you can deploy the solution into a sandbox. A sandbox is a restricted execution environment that enables programs to access only certain resources, and that keeps problems that occur in the sandbox from affecting the rest of the server environment.
Solutions that you deploy into a sandbox, which are known as sandboxed solutions, cannot use certain computer and network resources, and cannot access content outside the site collection they are deployed in. For more information about the restrictions on sandboxed solutions, see What a sandboxed solution cannot contain.
Because sandboxed solutions cannot affect the whole server farm, they do not have to be deployed by a farm administrator. Sandboxed solutions can be deployed by a site collection administrator or, in certain situations, by a user who has full control at the root of the site collection. Only a farm administrator can promote a sandboxed solution to run directly on the farm, outside its sandbox.
It is especially appropriate to use sandboxed solutions in two scenarios:
When an organization want to run code for employees on a production SharePoint Foundation site, and that code has not been stringently code reviewed and tested.
When a hoster wants to let the owners of hosted SharePoint Foundation sites upload and run custom code.
This article introduces the concepts that are related to sandboxed solutions, explains the differences between sandboxed solutions and solutions that are deployed on the farm, and summarizes how sandboxed solutions are deployed and run. This article does not contain detailed procedures for configuring sandboxing or for deploying sandboxed solutions.
In this article:
Deploying and running a sandboxed solution
Isolating sandboxed solutions
What a sandboxed solution cannot contain
-
Deploying and running a sandboxed solution
Any page of a SharePoint Foundation application can contain components that run in a sandbox in addition to components that run directly on the farm. The components that are deployed to the farm run in the Internet Information Services (IIS) worker process. The components that are deployed to the sandbox run in a sandboxed process.
The following list identifies several of the components that you might deploy in a sandbox:
Web Parts
Event receivers
Feature receivers
Custom Microsoft SharePoint Designer workflow activities
Microsoft InfoPath business logic
The following steps describe how to deploy a sandboxed solution:
1. A farm administrator performs the following tasks. These have to be done only one time.
A farm administrator enables sandboxing and starts the sandboxing service on each server that will run sandboxed solutions.
A farm administrator determines which load balancing scheme to use. The load balancing scheme applies to all sandboxed solutions in all site collections on the farm.
A farm administrator sets resource quotas that the combination of all sandboxed solutions in a site collection cannot exceed.
2. A site collection administrator or a user who has full control at the root of the site collection uploads a solution the site collection’s solution gallery.
3. A site collection administrator activates the solution. If the solution does not contain an assembly, a user who has full control at the root of the site collection can also activate the solution. Validation tools run against the solution. If the solution fails validation, it is not activated.
When a request to run a sandboxed solution is processed, the following activities occur:
1. Based on load balancing scheme, SharePoint Foundation determines which server to run the solution on. If load balancing is local, the solution runs on the same server that is servicing the request. If load balancing is remote, the server that the solution runs on is selected based on solution affinity. In both cases, the server must be running the sandboxing service.
2. SharePoint Foundation selects a sandbox worker process to run the solution in; loads a “shim” dynamic-link library (dll) into the process; and then loads the solution assembly into the process.
3. As the solution runs, its code passes through the shim before it is executed by SharePoint Foundation. If the solution code attempts to use APIs that sandboxed solutions are restricted from using, the shim signals an exception instead of letting the code pass through and run.
4. SharePoint Foundation monitors the resources that sandboxed solutions use. If the sandboxed solution exceeds a hard limit (for example, if it uses more than a predefined amount of CPU time,) SharePoint Foundation terminates the sandbox worker process. If the combination of all sandboxed solutions in the site collection exceeds the site collection’s resource quota, SharePoint Foundation turns off all sandboxed solutions in the site collection for the rest of the day.
5. A site collection administrator can monitor the resources that sandboxed solutions use, and can deactivate solutions in the site collection.
If necessary, a farm administrator can block a solution from running on the farm. Optionally, a farm administrator can also remove the requirement that a solution be run in a sandbox. If the requirement to run in a sandbox is removed, when the solution runs in any site collection in the farm, it will no longer run in a sandbox.
-
Isolating sandboxed solutions
You can isolate sandboxed solutions to various degrees. Each additional level of isolation increases your ability to protect the main part of your SharePoint Foundation site from code that might consume too many resources. At the first level, sandboxed code runs in a rights-restricted, isolated process. Code Access Security (CAS) limits the operations that the code can perform. You can increase isolation by using remote load balancing and by running the sandboxing service on only specific servers. In a production environment, we recommend that you use remote load balancing and dedicate a separate server to running sandboxed solutions.
-
What a sandboxed solution cannot contain
A SharePoint Foundation solution must contain the configuration file that is named manifest.xml, and may also contain additional configuration files and assemblies. If the solution will run in a sandbox, the assembly and configuration files are limited in what they can contain.
The following list identifies the most common things that an assembly that will run in a sandbox cannot do.
Connect to resources that are not located on the local server.
Access a database.
Change the threading model.
Call unmanaged code.
Write to disk.
Access resources in a different site collection.
The manifest.xml file refers to feature files; feature files refer to element files; and element files contain feature elements. The only feature elements that are permitted in a sandboxed solution are:
ContentType
Field
CustomAction
Module
ListInstance
ListTemplate
Receivers
WebTemplate
WorkflowAssociation
PropertyBag
WorkflowActions
-
Comparison of sandboxed and farm solutions
The following table compares aspects of solutions that run in a farm to solutions that run in a sandbox.
Aspect
Farm
Sandbox
Deployment process
Add the solution, and then deploy it to the farm.
Upload the solution to a site collection, and then activate it in the site collection.
Who can deploy
Farm administrator.
If the solution contains an assembly, only a site collection administrator can deploy it. If the solution does not contain an assembly, a user who has full control at the root of the site collection can deploy it.
Data access
Unrestricted.
The solution can only access content from the site collection in which it was deployed.
Process the solution runs in
Unrestricted IIS worker process, or whichever process the solution is deployed into.
Separate worker process that has restricted rights.
Code access security
The solution developer can set the code access security policy when packaging the solution.
Restricted. For more information, see Deploying a sandboxed solution (http://go.microsoft.com/fwlink/?LinkId=177369&clcid=0x409).
Monitoring
Not monitored.
Monitored, and limited by quotas set by the farm administrator.
Load balancing
Varies, based on the kind of solution.
Configurable separately from non-sandboxed solutions.
Solution functionality
Unrestricted.
Restricted, as described in What a sandboxed solution cannot contain.
-
Benefits of using sandboxed solutions
The main benefits of using sandboxed solutions are as follows:
Solutions can be added to a production SharePoint Foundation environment without the risk of affecting processes outside the sandbox.
Site collection administrators can deploy sandboxed solutions, freeing farm administrators from this task.
Scalability and flexibility are increased because sandboxes run in separate process that can be restricted by quotas, and their effect on the farm can be monitored.
A solution does not have to be modified or recompiled if it is moved from a sandbox to running directly on the farm.
-
See Also
Sandboxed solutions administration (SharePoint Foundation 2010) (http://technet.microsoft.com/library/9202709d-2854-4663-989f-6e2f0d3d930b(Office.14).aspx)
Sandboxed solutions planning (SharePoint Foundation 2010)
Sandboxed solutions architecture (http://go.microsoft.com/fwlink/?LinkId=177368&clcid=0x409)
Deploying a sandboxed solution (http://go.microsoft.com/fwlink/?LinkId=177369&clcid=0x409)
-
-
Planning sandboxed solutions (SharePoint Foundation 2010)
Sandboxed solutions restrict access to network and local resources to provide greater security and stability. You can use sandboxed solutions for load balancing solutions, for solutions that have not been fully tested, and for deploying user solutions in a hosted environment. Sandboxed solutions run in a separate worker thread so that they cannot access resources that belong to other solutions, and they have limited access to local and network resources.
When you plan sandboxed solutions, decide first whether to use sandboxed solutions at all. You should determine whether your primary consideration is performance or security. A farm that uses sandboxed solutions generates more worker and proxy processes than a farm that does not use sandboxed solutions. Using sandboxed solutions provides more process isolation, which enhances the security of your farm.
For more information about sandboxed solutions, see Sandboxed solutions overview (SharePoint Foundation 2010).
In this article:
Determine when to use sandboxed solutions
Plan to load balance sandboxed solution code
Determine where to deploy sandboxed solutions
Determine who can deploy sandboxed solutions
Determine which site collections will run sandboxed solutions
-
Determine when to use sandboxed solutions
Using sandboxed solutions is appropriate in scenarios where you want to load balance solutions across multiple servers, or where you want to provide the ability to run code that has not been fully tested or that your organization does not support. Sandboxed solutions can play a valuable part of a scaled deployment path for developers in your organization, from their test environment to a sandboxed solution in the production environment. Sandboxed solutions can later be changed to full trust status by a farm administrator when the solution is shown to be safe for full deployment.
It is especially appropriate to use sandboxed solutions in the following scenarios:
When you want to load balance solutions between multiple SharePoint Foundation servers.
When an organization wants to run code for employees on a production SharePoint Foundation site, and that code has not been stringently code reviewed and tested.
When an Internet hosting provider wants to let the owners of hosted SharePoint Foundation sites upload and run custom code.
When you use sandboxed solutions, you must activate the SharePoint 2010 User Code Host service on each server on which you want to run the sandboxed solutions.
-
Plan to load balance sandboxed solution code
You can select one of two load balancing schemes for sandboxed solutions. Based on the load balancing scheme, Microsoft SharePoint Foundation 2010 determines which server to run the solution on. In local load balancing, the solution runs on the same server that received the request. If you choose remote load balancing, the server that the solution runs on is selected based on solution affinity, and the sandboxed solution is run on a server where it is already loaded and has already been run. This saves time in servicing the request for the solution. In both cases, each server must be running the SharePoint Foundation Sandboxed Code Service.
Your load balancing choice determines the model that is used by the entire SharePoint Foundation farm. You cannot use a mixture of local and remote load balancing, but instead you must choose to implement one or the other. When you are deciding which mode to implement consider the following:
Local mode requires less administration, but its scalability is limited by the resources of the local server.
Remote mode is more scalable than local mode, but it requires administrative tasks to be performed on more servers.
You obtain better performance by using the remote load balancing model in a SharePoint Foundation farm where there are multiple servers on which to run sandboxed solutions. If you are using sandboxed solutions as part of a development process, and you want to keep them restricted to the server from which they are called, use the local mode load balancing.
For more information, see Sandboxed solutions overview (SharePoint Foundation 2010).
-
Determine where to deploy sandboxed solutions
Sandboxed solutions are deployed at the root of a site collection. Anyone who is a site collection administrator can deploy a sandboxed solution. When it is deployed in a site collection, the sandboxed solution can be used anywhere within that site collection.
You can choose to run sandboxed solutions only on certain servers within your SharePoint Foundation farm or to all servers. To enable sandboxed solutions on a server, you must enable the SharePoint Foundation Sandboxed Code Service. This service must be enabled on every server on which you want to run sandboxed solutions.
-
Determine who can deploy sandboxed solutions
When you plan for the user roles that are involved in deploying sandboxed solutions, you must determine who will be authorized to deploy the solutions and who will be authorized to administer the solutions. Members of the site collection administrators group can deploy sandboxed solutions.
You must be a member of the farm administrators group to perform administrative tasks such as enabling or disabling the SharePoint Foundation Sandboxed Code Service, blocking or unblocking a solution, and adjusting or resetting quotas.
Note:
It is not enough to be a site collection owner, to deploy and activate a sandboxed solution you must be a site collection administrator for the site collection where you are deploying the sandboxed solution.
Because farm administrators can change sandboxed solutions to fully trusted solutions that can be deployed anywhere on the farm, you should be careful to limit the membership of the farm administrators group to appropriate users. The same consideration applies to adding users to the site collection administrators group if there is any concern over the security of the sandboxed solutions being deployed.
-
Determine which site collections will run sandboxed solutions using quotas
Sandboxed solutions can be enabled or disabled on specific site collections by adjusting their quotas. If you set the quota for sandboxed solutions to 0 on a specific site collection, sandboxed solutions will not run on that site collection. In this way you can fine tune the use of sandboxed solutions in your farm.
To plan where to deploy sandboxed solutions you should consider both which servers will run the SharePoint Foundation Sandboxed Code Service, and which site collections will be able to run sandboxed solutions. If you enable sandboxed solutions on some site collections you should disable them on the remaining site collections by setting the quotas on those site collections to 0.
-
Plan resource usage quotas for sandboxed solutions
Sandboxed solutions are monitored for resource usage based on default resource quotas. If a sandboxed solution exceeds any of the resource quotas, the solution is disabled for the remainder of the day or until a farm administrator manually resets the solution. This helps administrators to know when a particular sandboxed solution is making excessive demands on shared resources or in some cases where a resource-intensive sandboxed solution requires an increased quota.
The default quotas are satisfactory for most scenarios; however, you can adjust individual quota limits to permit higher limits where appropriate.
If you determine that a sandboxed solution is consistently misusing server resources, you can block that solution until the developer can correct the situation. For more information about blocking and unblocking sandboxed solutions, see Block or unblock a sandboxed solution (SharePoint Foundation 2010) (http://technet.microsoft.com/library/6687e357-8531-4904-9c17-faa6908a793d(Office.14).aspx).
The default values that are assigned to sandboxed solution quotas are listed in the following table.
Resource
Description
Units
Resources per Point
Absolute Limit
AbnormalProcessTerminationCount
Abnormally terminated process
occurrence
1
1
CPUExecutionTime
CPU Execution Time for site
seconds
3,600
60
CriticalExceptionCount
Critical Exception Events
events
10
3
InvocationCount
Solution Invocation Events
events
<TBD>
<TBD>
PercentProcessorTime
Percent CPU usage by solution
percentage
85
100
ProcessCPUCycles
Solution CPU cycles
cycles
1 x10^11
1 x10^11
ProcessHandleCount
Windows handles count
items
10,000
1,000
ProcessIOBytes
Windows handles count
items
0
1 x10^8
ProcessThreadCount
Thread count in overall process
instances
10,000
200
ProcessVirtualBytes
Memory consumed
bytes
0
1.0×10^9
SharePointDatabaseQueryCount
Number of SharePoint database queries
instances
20
100
SharePointDatabaseQueryTime
Elapsed time to execute query
seconds
120
60
UnhandledExceptionCount
Number of unhandled exceptions
instances
50
3
UnresponsiveProcessCount
Number of unresponsive processes
instances
2
1
-
Plan sandboxed solutions governance
While you are still planning for sandboxed solutions, you should consider your processes for governance issues, including the following:
At what point will the farm administrator block or unblock a sandboxed solution? Identifying the administrative policy for blocking and unblocking sandboxed solutions will eliminate confusion if there is any doubt about the need to block a solution.
At what point will you transfer a sandboxed solution to the global catalog as a full trust solution? This decision applies to solution code that is developed by your organization’s developers. You should establish a policy for determining what level of testing is required for a sandboxed solution to be considered ready for production use in your organization.
When you are planning for who can deploy sandboxed solutions, will you choose to add people to the site collection administrators group or establish a procedure for a limited number of site collection administrators to deploy sandboxed solutions on behalf of their users? Depending on the security concerns in your organization, you can decide to add people directly to the site collection administrators group rather than requiring them to ask permission to deploy the sandboxed solution.
-
Plan for collaboration sites (SharePoint Foundation 2010)
With Microsoft SharePoint Foundation 2010, you can support collaboration sites in your environment. Collaboration sites store information that individuals and groups can collectively author, share, and revise. These sites do not need to be associated with a particular portal site collection or part of a publishing site collection. They can be stand-alone sites that are available for teams or groups of users who need to collaborate on projects or share information. For example, a team at an engineering firm might want a collaboration site to discuss current project status, assign tasks, or arrange group lunches, without publishing this internal information to the corporate intranet.
Collaboration sites can be made available for searching from your portal or publishing site so that information from these sites is not lost to your organization. However, for easier data recovery and maintenance, collaboration sites should be hosted either on a separate Web application or in separate content databases in the same Web application as your portal or publishing site.
You can create these collaboration sites for your users, or you can allow the users to create these sites on their own.
For more information about collaboration sites and architectural planning, see Logical architecture sample design: collaboration sites.
In this article:
-
Determine number of collaboration sites
Estimate approximately how many collaboration sites to expect in your environment, and how many such sites that you are willing to support. If you require users to request a collaboration site, you can control how many are created. If you let users create their own collaboration sites, you will have many of these sites in your environment.
-
Specific paths
You can use specific paths in Microsoft SharePoint Foundation 2010 to contain the SharePoint site collections, similar to the way that folders contain files or documents in the file system. By default, when you create a Web application, two paths are made available for you:
Root path (/) This is an explicit inclusion that can contain one site collection. For example, if you want a URL to appear as http://company_name/default.aspx, you would create the site collection at this root path.
Sites path (/sites) This is a general path that can contain many site collections. For example, when you use the /sites path, the URL for a site named Site_A would be similar to http://server_name/sites/Site_A/default.aspx.
Note:
The name of the /sites path varies depending on the specific language that was used during installation.
-
Additional paths
You can also create additional paths. This enables you to group site collections. Then, when you create a site collection, you can choose from the following alternatives:
Create the site collection at the root of the Web application (if no site collection has already been created there).
Create the site collection under the /sites path.
Create the site collection under any additional paths that have been made available for that Web application.
In general, the /sites path should be sufficient for most installations. However, consider using other paths for the following situations:
You have a complex installation and expect to have many site collections, and you want to group similar sites together.
For example, you could use /personal for individual user sites and /team for group collaboration sites, instead of using /sites for all.
You want to be able to add a filter to your firewall or router to constrain a specific namespace to internal access only.
For example, you could expose the /team path for external collaboration, but not /personal.
-
Integration with Microsoft SharePoint Workspace 2010
Microsoft SharePoint Workspace 2010 provides a rich client for Microsoft SharePoint Foundation 2010, which enables real-time synchronization of desktop content with SharePoint documents and lists. Microsoft SharePoint Workspace 2010 also provides options for creating ad hoc Groove collaboration workspaces and shared folder workspaces. Information can be easily synchronized both online and offline with a designated SharePoint site or with external partners and offsite team members via shared workspaces. Microsoft SharePoint Workspace 2010 is installed automatically with enterprise versions of Microsoft Office 2010 or it can be installed separately from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkID=48516&clcid=0x409).
For more information, see Plan for SharePoint Workspace 2010 (http://technet.microsoft.com/library/e8a433c1-ea1f-4cf7-adc8-50972f58d465(Office.14).aspx).
-
Document management planning (SharePoint Foundation 2010)
These articles will guide you in planning the document management features of your solution that is based on Microsoft SharePoint Foundation 2010.
The articles in this section include the following:
Document library planning (SharePoint Foundation 2010)
This article describes how to use document libraries to organize documents in your enterprise.
Content types planning (SharePoint Foundation 2010)
This article describes how to plan content types, which are the SharePoint Foundation 2010 mechanism to define and share the attributes of documents, list items, and folders.
Versioning, content approval, and checkout planning (SharePoint Foundation 2010)
This article describes how to plan content governance by using versioning, check-in and check-out, and approval for publishing content.
Co-authoring overview (SharePoint Foundation 2010) describes the feature and provides administrators an understanding of the settings that can be used to manage co-authoring.
-
Document library planning (SharePoint Foundation 2010)
This article describes how to plan document libraries and integrate libraries into your Microsoft SharePoint Foundation 2010 document management solution.
Document libraries are collections of files on SharePoint Foundation 2010 that you share with other site users. Most document management features are delivered through document libraries. As part of document management planning, you should determine the kind of document libraries that best fit your organization’s needs.
-
Plan document libraries
Document libraries are collections of files on SharePoint Foundation 2010 that you share with other site users. Most SharePoint Foundation 2010 document management features are delivered through document libraries. As part of document management planning, you should determine the document libraries that best fit your organization’s needs.
SharePoint Foundation 2010 includes the following kinds of document libraries:
Document Library Use a Document Library for general purpose document storage, document collaboration, and easy sharing of content.
Picture Library Use a Picture Library to share, manage, and reuse digital pictures.
Use document libraries to store content on which your workgroup is collaborating and to create shared knowledge bases. For example, a workgroup that designs products can use a document library to store works-in-progress such as design proposals, specifications, and supporting information. Using metadata, displayed as columns of information, the status of each design document can be maintained and made public, together with each document’s author, the project name, and so on. Completed documents can be stored separately in a searchable knowledge base document library that is used as source of information when researching new projects
In SharePoint Foundation 2010, document libraries can contain multiple kinds of documents. To implement this, you associate one or more content types with the document library. When multiple content types are associated with a library, the New command for that library will let users create new documents of any content type associated with the library, and metadata for all content types that the library can contain are displayed in document library views. For more information about content types planning, see Content types planning (SharePoint Foundation 2010).
Other document library features that support collaboration include the following:
Templates You can design a template and associate it with a document library to standardize the documents created in the library.
Workflows Using a custom workflow (see Plan workflows (SharePoint Foundation 2010)), business processes can be run on documents. For example, a workflow could send a document for review.
Check in and out You can require that users check documents in and out of a document library before editing them.
Versioning You can choose from three versioning options.
-
Content types planning (SharePoint Foundation 2010)
This article describes content types and workflows and provides guidance about how to plan how you can integrate them into your Microsoft SharePoint Foundation 2010 document management solution.
-
Plan content types
In this section:
A content type defines the attributes of a list item, a document, or a folder. Each content type can specify:
Properties to associate with items of its type.
Workflows that can be launched from items of its type.
Document templates (for document content types).
Document conversions to make available (for document content types).
Custom features.
You can associate a content type with a list or library. When you do this, you are specifying that the list or library can contain items of that content type and that the New command in that list or library will let users create new items of that type.
Note:
You can also associate properties, workflows, policies, and templates directly with a list or library. However, doing this can limit these associations to the list or library and is not reusable across your solution. In SharePoint Foundation 2010 site level workflows can be associated with multiple lists or libraries.
Document libraries and lists can contain multiple content types. For example, a library can contain both the documents and the graphics related to a project. When a list or library contains multiple content types, the following apply:
By default, the New command in that list or library lets users select from among all available content types when they create a new item. Content type owners can configure the New command to display only certain content types.
The columns associated with all available content types are displayed.
You can define custom content types in a site’s content type gallery. A custom content type must be derived, directly or indirectly, from a core content type such as Document or Item. After it is defined in a site, a custom content type is available in that site and in all sites below that site. To make a content type most widely available within a site collection, define it in the content type gallery of the top-level site.
For example, if your organization uses a particular contract template, in the content type gallery of the top-level site in a site collection you can create a content type that defines the metadata for that contract, the contract’s template, and workflows required to review and complete the contract. Then, any document library in your site collection to which you associate the Contract content type will include all these features and will enable authors to create new contracts based on the template.
In sites based on SharePoint Foundation 2010, each default list item or library item, such as Contact, Task, or Document, has a corresponding content type in the site’s content type gallery. When planning content types, you can use these out-of-box content type definitions as starting points, basing new content types on existing content types as needed or modifying the default types.
Content types are organized into a hierarchy that enables one content type to inherit its characteristics from another content type. This enables classes of documents to share characteristics across an organization, while also enabling teams to customize these characteristics for particular sites or lists.
For example, all customer deliverable documents in an enterprise may require a set of metadata such as account number, project number, and project manager. By creating a top-level Customer Deliverable content type, from which all other customer deliverable document types inherit, you ensure that required information such as account numbers and project numbers will be associated with all variants of customer deliverable documents in your organization. Note that if another required column is added to the top-level Customer Deliverable content type, the content type owner can propagate the changes to all content types that inherit from it, which will add the new column to all customer deliverable documents.
Each item of metadata that is associated with a content type is a column, which is a location in a list to store information. Lists or libraries are often displayed graphically as columns of information. However, depending on the view associated with the list, the columns can appear in other forms, such as days in a calendar display. In forms associated with a list or library, columns are displayed as fields.
You can define columns for use in multiple content types. To do this, create them in a Column Templates gallery. There is a Column Templates gallery in each site in a site collection. As with content types, columns defined in the Column Templates gallery of a site are available in that site and in all sites below it.
Folder content types define the metadata that is associated with a folder in a list or library. When you apply a folder content type to a list or library, the New command in that list or library will include the folder content type, which makes it possible for users create folders of that type.
You can define views in a list or library that are available only in folders of a particular content type. This is useful when you want a folder to contain a particular kind of document and you want views in that folder to only display columns that are relevant to the document type contained in that folder.
By using the SharePoint Foundation 2010 object model, you can customize the New command for a folder content type so that, when a user creates a new folder of that type, the folder is prepopulated with multiple files and documents based on templates stored on the server. This is useful, for example, for implementing a compound document type that requires multiple files to contribute to a single deliverable document.
-
Versioning, content approval, and checkout planning (SharePoint Foundation 2010)
This article describes how to plan to use versioning, content approval, and check-out in Microsoft SharePoint Foundation 2010 to control document versions throughout their life cycle.
In this article:
-
About versioning, content approval, and check-outs
SharePoint Foundation 2010 includes the following features that can help you control documents in a document library:
Versioning is the method by which successive iterations of a document are numbered and saved.
Content approval is the method by which site members with approver permissions control the publication of content.
Check-out and Check-in are the methods by which users can better control when a new version of a document is created and also comment on changes that were made when a document is checked in.
You configure settings for the content control features discussed in this article in document libraries. To share these settings across libraries in your solution, you can create document library templates that include your content control settings; this ensures that new libraries will reflect your content control decisions.
-
Plan versioning
The default versioning control for a document library depends on the site collection template. However, you can configure versioning control for a document library depending on your particular requirements. Each document library can have a different versioning control that best suits the type of documents in the library. SharePoint Foundation 2010 has three versioning options:
No versioning Specifies that no previous versions of documents are saved. When no versioning is being used, previous versions of documents are not retrievable, and document history is also not retained because comments that accompany each iteration of a document are not saved. Use this option on document libraries that contain unimportant content or content that will never change.
Create major versions Specifies that numbered versions of documents are retained using a simple versioning scheme (such as 1, 2, 3). To control the effect on storage space, you can specify how many previous versions to keep, counting back from the current version.
In major versioning, every time that a new version of a document is saved, all users who have permissions to the document library will be able to view the content. Use this option when you do not want to differentiate between draft versions of documents and published versions. For example, in a document library that is used by a workgroup in an organization, major versioning is a good choice if everyone on the team must be able to view all iterations of each document.
Create major and minor (draft) versions Specifies that numbered versions of documents are retained by using a major and minor versioning scheme (such as 1.0, 1.1, 1.2, 2.0, 2.1). Versions ending in .0 are major versions and versions ending with non-zero extensions are minor versions. Previous major and minor versions of documents are saved together with current versions. To control the effect on storage space, you can specify how many previous major versions to keep, counting back from the current version. You also can specify how many major versions being kept should include their respective minor versions. For example, if you specify that minor versions should be kept for two major versions and the current major version is 4.0, then all minor versions starting at 3.1 will be kept.
In major and minor versioning, any user who has read permissions can view major versions of documents. You can specify which users can also view minor versions. Typically, grant users who can edit items permissions to view and work with minor versions, and restrict users who have read permissions to viewing only major versions.
Use major and minor versioning when you want to differentiate between published content that can be viewed by an audience and draft content that is not yet ready for publication. For example, on a human resources Web site that describes organizational benefits, use major and minor versioning to restrict employees’ access to benefits descriptions while the descriptions are being revised.
Note:
Regardless of the versioning control you choose, you must consider the effect that retaining multiple versions of the same document can have on storage space.
-
Plan content approval
Use content approval to formalize and control the process of making content available to an audience. For example, an enterprise that publishes content as one of its products or services might require a legal review and approval before publishing the content. Content publishing can also be scheduled depending on the document state.
A document draft awaiting content approval is in the Pending state. When an approver reviews the document and approves the content, it becomes available for viewing by site users who have read permissions. A document library owner can enable content approval for a document library and optionally can associate a workflow with the library to run the approval process.
The way that documents are submitted for approval varies depending on the versioning settings in the document library:
No versioning If no versioning is being used and changes to a document are saved, the document’s state becomes Pending. SharePoint Foundation 2010 keeps the earlier version of the document so that users with read permissions can still view it. After the pending changes have been approved, the new version of the document is made available for viewing by users who have read permissions and the earlier version is not retained.
If no versioning is being used and a new document is uploaded to the document library, it is added to the library in the Pending state and is not viewable by users who have read permissions until it is approved.
Create major versions If major versioning is being used and changes to a document are saved, the document’s state becomes Pending and the previous major version of the document is made available for viewing by users who have read permissions. After changes to the document are approved, a new major version of the document is created and made available to site users who have read permissions, and the previous major version is saved to the document’s history list.
If major versioning is being used and a new document is uploaded to the document library, it is added to the library in the Pending state and is not viewable by users who have read permissions until it is approved as version 1.
Create major and minor (draft) versions If major and minor versioning is being used and changes to a document are saved, the author has the choice of saving a new minor version of the document as a draft or creating a new major version, which changes the document’s state to Pending. After the changes to the document are approved, a new major version of the document is created and made available to site users who have read permissions. In major and minor versioning, both major and minor versions of documents are kept in a document’s history list.
If major and minor versioning is being used and a new document is uploaded to the document library, it can be added to the library in the Draft state as version 0.1, or the author can immediately request approval in which case the document’s state becomes Pending.
-
Plan check-out and check-in
You can require that users check out documents from a document library before editing the documents. It is always recommended to do this. The benefits of requiring check-out and check-in include the following:
Better control of when document versions are created. When a document is checked out, the author can save the document without checking it in. Other users of the document library will be unable to see these changes and a new version is not created. A new version (visible to other users) is only created when an author checks in a document. This gives the author more flexibility and control.
Better capture of metadata. When a document is checked in, the author can write comments that describe the changes that were made to the document. This promotes creation of an ongoing historical record of the changes that are made to the document.
If your solution requires that users check in and check out documents when editing them, the Microsoft Office 2010 client applications include features that support these actions. Users can check out documents, undo check-outs, and check in documents from Office 2010 client applications.
When a document is checked out, it is saved in the user’s My Documents folder in a subfolder named “SharePoint Drafts.” This folder is displayed in the Office 2010 client applications. When the document is checked out, the user can only save edits to this local folder. When the user is ready to check the document in, the document is saved back to the original server location.
From Office 2010 client applications, users can also decide to leave checked-out documents on the server by changing content editing options.
-
See Also
-
-
Co-authoring overview (SharePoint Foundation 2010)
In today’s highly connected work environment, documents created by multiple authors, editors, and stakeholders are becoming the rule, instead of the exception. Organizations look to the communication and collaboration capabilities of Microsoft SharePoint Foundation 2010 to help them foster communication and collaboration between end-users while reducing administration required to support it. Microsoft Office 2010 continues this trend with co-authoring functionality for Microsoft PowerPoint 2010, Microsoft Word 2010, and Microsoft OneNote 2010 documents on SharePoint Foundation 2010.
Co-authoring removes barriers to server-based document collaboration and helps organizations to reduce the overhead associated with traditional document sharing through attachments. Co-authoring simplifies collaboration by enabling multiple users to work productively on the same document without intruding on one another’s work or locking one another out. This functionality requires no additional server setup and is the default state for documents stored in SharePoint Foundation 2010. Co-authoring functionality is managed by using the same tools and technologies that are already used to manage SharePoint Foundation, helping to minimize the impact on administrators.
In this article:
Co-authoring functionality in SharePoint Foundation 2010
Understanding the end-user experience
Software Version Requirements
-
Co-authoring functionality in SharePoint Foundation 2010
In traditional collaboration, documents are shared via e-mail attachments. Tracking versions and edits from multiple authors is difficult and time-consuming for users. E-mail systems have to contend with storing multiple copies of the same document, not to mention increased network traffic as documents are sent repeatedly.
The use of SharePoint Foundation to store documents for collaboration has reduced these problems by providing consistent access to up-to-date versions of documents, the ability to track previous versions, and centralized management. Storing a single document, instead of many attachments, also reduces network and storage overhead.
But this solution hasn’t been perfect. When one author has a document open, other authors cannot work on it. If someone forgets to close a document or check it in, other users may be locked out indefinitely, a situation that often requires a call to the IT department to resolve the problem.
Co-authoring in SharePoint Foundation 2010 addresses these issues by making it possible for multiple users to work on a document, at any time, without interfering with each other’s changes. This approach streamlines many common document-collaboration scenarios. For example:
Two or more authors are working on different parts of a composite document. While one author works on his section of the document, another author can work on hers, without either interrupting their work.
Several authors are working on a composite slide show. Each author can add slides to the presentation and edit them, instead of working in isolation and trying to merge several documents and make them consistent all at the same time.
A document is sent out to several experts and stakeholders, each of whom has some edits or additions. No user’s edits are lost, because they are all working on a central, server-stored document.
-
Understanding the end-user experience
Co-authoring is easy to use from the end user’s point of view. When a user wants to work on a document in Word 2010, PowerPoint 2010, or OneNote 2010, he or she merely opens it from SharePoint Foundation, as usual. If another user already has the document open, both users are able to edit the document at the same time; access to the document is not blocked and no error appears
In Word 2010 and PowerPoint 2010, saving to a document notifies other users viewing the document that there are new edits. Those users can refresh their view immediately to see those changes or continue their work and refresh later to see the latest edits. The authors can also see one another’s work, and everyone knows who is working on the document. SharePoint Foundation 2010 versioning and tracking tools protect the document so that authors can roll back unwanted changes. When Office Communication Server is available, users can see the online status of fellow co-authors and initiate instant messaging conversations without leaving the document.
With OneNote 2010, shared notebooks enable users to share notes seamlessly. When a user edits a page of the notebook, those edits are automatically synchronized with other users of that notebook to ensure everybody has a complete set of notes. Edits made by multiple users on the same page appear automatically, enabling near real-time collaboration. Versioning and other shared features in OneNote make it possible for users to roll back edits, show what edits are new, and determine who made a specific edit.
The Excel 2010 client application does not support co-authoring workbooks in SharePoint Foundation 2010. However, the Excel client application does support non-real-time co-authoring workbooks stored locally or on network (UNC) paths by using the Shared Workbook feature. Co-authoring workbooks in SharePoint Foundation is supported by using the Microsoft Excel Web App, included with Office Web Apps. Office Web Apps is available to users through Windows Live and to business customers with Microsoft Office 2010 volume licensing and document management solutions based on Microsoft SharePoint 2010 Products. For more information, see Office Web Apps (Installed on SharePoint 2010 Products) (http://technet.microsoft.com/library/8a58e6c2-9a0e-4355-ae41-4df25e5e6eee(Office.14).aspx).
-
Important considerations
There are several factors that administrators will want to consider when planning how to use co-authoring in their environment.
Co-authoring functionality in SharePoint Foundation is designed to be easy to set up and requires minimal effort to manage. However there are several things to consider when you set up and manage co-authoring:
Permissions – For multiple users to be able to edit the same document, users need edit permissions for the document library where that document is stored. The simplest way to ensure this is to give all users access to the SharePoint site where documents are stored. In cases in which only a subset of users should have permission to co-author documents in a particular library, SharePoint permissions can be used to manage access.
Versioning –SharePoint Foundation versioning keeps track of changes to documents while they are being edited, and even stores previous versions for reference. By default, this feature is turned off in SharePoint Foundation 2010. SharePoint Foundation 2010 supports two kinds of versioning, major and minor. It is best that minor versioning not be turned on for document libraries used for co-authoring in OneNote, as this may interfere with the synchronization and versioning capabilities that are part of the product. This limitation only applies to minor versioning; major versioning may be used with OneNote.
Number of versions – The number of document versions retained affects storage requirements on the server. This number can be tuned in the document library settings to limit the number of versions retained. OneNote notebooks that are frequently updated may result in many versions being stored on the server. To avoid using unnecessary disk space, we recommend that an administrator set the maximum number of versions retained to a reasonable number on document libraries used to store OneNote notebooks.
Versioning period – The versioning period determines how often SharePoint Foundation will create a new version of a Word or PowerPoint document that is being co-authored. Setting this period to a low value will capture versions more often, for more detailed version tracking, but may require more server storage. The versioning period does not impact OneNote notebooks. This value can be altered by adjusting the coAuthoringVersionPeriod property on the server. For more information about adjusting this setting, see Configure the co-authoring versioning period (SharePoint Foundation 2010) (http://technet.microsoft.com/library/21b24d64-74bc-49c4-b91c-35ed1f45bdc4(Office.14).aspx).
Check out – When a user checks out a document for editing, this locks the document for editing to only that user, which prevents co-authoring. Require Check Out should not be enabled in document libraries where co-authoring will be used. By default, Require Check Out is not enabled in SharePoint Foundation 2010. Users should not check out documents manually when co-authoring is being used.
-
OneNote Notebooks
Unlike Microsoft Word and Microsoft PowerPoint, Microsoft OneNote stores version information within the file itself. For this reason, administrators should follow these recommended practices when storing OneNote notebooks in a SharePoint Foundation document library:
Do not enable minor versioning. By default, minor versioning is not enabled in SharePoint Foundation 2010.
If major versioning is enabled, set a reasonable maximum number of versions to store. By default, major versioning is not enabled in SharePoint Foundation 2010.
-
Software Version Requirements
For users to co-author documents by using Office 2010, those documents must be stored in SharePoint Server 2010 or SharePoint Foundation 2010. To take advantage of the co-authoring functionality, users must have Word 2010, PowerPoint 2010, or OneNote 2010.
Note:
The co-authoring functionality in Office 2010 can also be used without SharePoint Server 2010 or SharePoint Foundation 2010 if users have Windows Live SkyDrive accounts. Using co-authoring without SharePoint Server 2010 or SharePoint Foundation 2010 is not covered in this article.
-
Co-authoring in a mixed Office environment
Some organizations may want to use co-authoring in an environment where users have different versions of Office.
-
Mixed environment that has Microsoft Office PowerPoint and Word 2007
Users of earlier versions of PowerPoint and Word can share and edit documents stored in SharePoint Foundation 2010 exactly as with previous versions of SharePoint Foundation. However, they cannot use co-authoring to work on them at the same time. To collaborate best in PowerPoint and Word, we recommend that all users work with Office 2010. Users of Office PowerPoint and Word 2007 will not experience any significant difference between their current experience and their user experience on Office 2010. For instance, if Office 2007 users open a document stored in Office 2010 that is currently being edited by another user, they will see a message that the document is being used and will be unable to edit it. If no other user is editing the document, Office 2007 users will be able to open it as usual. When an Office 2007 user opens a document, this creates a lock on the document and prevents users of Office 2010 from using co-authoring to edit the document. This behavior matches earlier versions of SharePoint Foundation.
-
Mixed environment that has Microsoft Office OneNote 2007
OneNote 2010 is backward compatible with the Office OneNote 2007 file format and supports co-authoring with OneNote 2007 users. In mixed environments, notebooks must be saved in the OneNote 2007 file format for OneNote 2007 and OneNote 2010 users to work on it together. By upgrading to the OneNote 2010 file format, however, users gain several key features, including compatibility with the Microsoft OneNote Web App that allows users without any version of OneNote installed to edit and co-author notebooks.
OneNote 2010 includes the ability to upgrade OneNote 2007 files to OneNote 2010 files at any time, providing an easy upgrade path for organizations that are moving from a mixed environment to a unified environment on Office 2010.
-
-
Performance and scalability
SharePoint Foundation 2010 and Office 2010 applications have been designed to minimize the performance and scalability impact associated with co-authoring in your environment. Office clients do not send or download co-authoring information from the server until more than one author is editing. When a single user is editing a document, the performance impact resembles that of previous versions of SharePoint Foundation.
Office clients are configured to reduce server impact by reducing the frequency of synchronization actions related to co-authoring when the server is under heavy load, or when a user is not actively editing the document, further helping to reduce overall performance impact.
-
See Also
Co-authoring administration (SharePoint Foundation 2010) (http://technet.microsoft.com/library/83f79b8d-4e27-4c3f-819c-3546476fe923(Office.14).aspx)
-
-
Business data and processes planning (SharePoint Foundation)
The topics in this section will help you plan and build solutions that integrate business processes with your organization’s data.
In this section:
Plan for Business Connectivity Services (SharePoint Foundation 2010)
-
Plan for Business Connectivity Services (SharePoint Foundation 2010)
This section describes how to plan for Business Connectivity Services within a Microsoft SharePoint Foundation 2010 environment.
In this section:
Business Connectivity Services overview (SharePoint Foundation 2010)
Business Connectivity Services security overview (SharePoint Foundation 2010)
Diagnostic logging in Business Connectivity Services overview (SharePoint Foundation 2010)
-
Business Connectivity Services overview (SharePoint Foundation 2010)
Microsoft SharePoint Foundation 2010 includes Microsoft Business Connectivity Services, which are a set of services and features that provide a way to connect SharePoint solutions to sources of external data and to define external content types that are based on that external data. External content types resemble content types and allow the presentation of and interaction with external data in SharePoint lists (known as external lists) and Web Parts. External systems that Microsoft Business Connectivity Services can connect to include SQL Server databases, SAP applications, Web services (including Windows Communication Foundation Web services), custom applications, and Web sites based on SharePoint. By using Microsoft Business Connectivity Services, you can design and build solutions that extend SharePoint collaboration capabilities to include external business data and the processes that are associated with that data.
Microsoft Business Connectivity Services solutions use a set of standardized interfaces to provide access to business data. As a result, developers of solutions do not have to learn programming practices that apply to a specific system or adapter for each external data source. Microsoft Business Connectivity Services also provide the run-time environment in which solutions that include external data are loaded, integrated, and executed.
-
Typical solutions based on Business Connectivity Services
Information workers typically perform much of their work outside the formal processes of a business system. For example, they collaborate by telephone or e-mail messages, use documents and spreadsheets from multiple sources, and switch between being online and offline. Solutions that are based on Microsoft Business Connectivity Services can be designed to fit within these informal processes that information workers use:
They can be built by combining multiple services and features from external data systems to deliver solutions that are targeted to specific roles.
They support informal interactions and target activities and processes that occur mostly outside formal enterprise systems. Because they are built by using SharePoint 2010 Products, solutions that are based on Microsoft Business Connectivity Services promote collaboration.
They help users perform tasks within the familiar user interface of SharePoint 2010 products.
Here are some examples of solutions that are based on Microsoft Business Connectivity Services:
Help desk An enterprise implements its help desk, which provides internal technical support, as a solution that is based on Microsoft Business Connectivity Services. Support requests and the technical support knowledge base are stored in external databases and are integrated into the solution by using the Business Data Connectivity service. The solution displays both support requests and the knowledge base in the Web browser. Information workers can view their current requests and tech support specialists view the requests assigned to them. Workflows take support issues through each of their stages. Managers on the technical support team can view dashboards that display help desk reports. Typical reports indicate the number of support issues assigned to each support specialist, the most critical issues currently, and the number of support incidents that are handled by each support specialist during a given time period.
Sales Dashboard A sales dashboard application helps sales associates in an organization quickly find the information that they need and enter new data. Sales orders and customer information are managed in an external database and integrated into the solution by using Microsoft Business Connectivity Services. Depending on their roles, team members can view sales analytics information, individual team members’ sales performance data, sales leads, and a customer’s contact information and orders. Sales professionals can view their daily calendars, view tasks assigned to them by their managers, collaborate with team members, and read industry news.
noteDXDOC112778PADS Security Note
We recommend that you use Secure Sockets Layer (SSL) on all channels between client computers and front end servers. Also we recommend using Secure Sockets Layer or Internet Protocol Security (IPSec) between servers running Microsoft SharePoint Foundation 2010 and external systems.
-
Business Connectivity Services security overview (SharePoint Foundation 2010)
This article describes the security architecture of the Microsoft Business Connectivity Services server and client, the supported security environments, the authentication modes available to connect external content types to external systems, the authorization options available on stored objects, and the general techniques for configuring Microsoft Business Connectivity Services security.
In this article:
Business Connectivity Services security architecture
Business Connectivity Services authentication overview
-
About this article
Microsoft Business Connectivity Services include security features for authenticating users to access external systems and for configuring permissions on data from external systems. Microsoft Business Connectivity Services are highly flexible and can accommodate a range of security methods from within supported Microsoft Office 2010 applications and from the Web browser.
-
Business Connectivity Services security architecture
This section describes the Microsoft Business Connectivity Services security architecture.
noteDXDOC112778PADS Security Note
We recommend that you use Secure Sockets Layer (SSL) on all channels between client computers and front end servers. Also we recommend using Secure Sockets Layer or Internet Protocol Security (IPSec) between servers running Microsoft SharePoint Foundation 2010 and external systems. An exception is that you cannot use SSL when transmitting messages to external systems using the SOAP 1.1 protocol or when connecting to a SQL server database. However, in those cases you can use IPSec to protect the data exchange.
-
Accessing external data
When a user accesses external data from a Web browser, three systems are involved: the logged on user’s client computer, the Web server farm, and the external system.

1. From Web browsers, users typically interact with external data in external lists or by using Web Parts.
2. The BDC Server Runtime on front-end servers uses data from the Business Data Connectivity service to connect to and execute operations on external systems.
3. The Secure Store Service securely stores credential sets for external systems and associates those credential sets to individual or group identities.
Important:
The Secure Store Service is not included in SharePoint Foundation 2010. If you need a secure store in SharePoint Foundation 2010, you must supply a custom secure store provider.
4. The Security Token Service is a Web service that responds to authentication requests by issuing security tokens made up of identity claims that are based on user account information.
5. Microsoft Business Connectivity Services can pass credentials to databases and Web services that are configured to use claims-based authentication. For an overview of claims-based authentication, see Plan authentication methods (SharePoint Foundation 2010).
-
-
Business Connectivity Services authentication overview
Microsoft Business Connectivity Services can be configured to pass authentication requests to external systems by using the following types of methods:
Credentials These are typically in the form of name/password. Some external systems may also require additional credentials such as a personal identification number (PIN) value.
Claims Security Assertion Markup Language (SAML) tickets can be passed to claims-aware services that supply external data.
Microsoft Business Connectivity Services can use credentials that a user supplies to authenticate requests for external data. The following methods by which users can supply credentials for accessing external data are supported:
Windows authentication:
Windows Challenge/Response (NTLM)
Microsoft Negotiate
Authentication other than Windows
Forms-based
Digest
Basic
When configuring Microsoft Business Connectivity Services to pass credentials, the solution designer adds authentication-mode information to external content types. The authentication mode gives Microsoft Business Connectivity Services information about how to process an incoming authentication request from a user and map that request to a set of credentials that can be passed to the external content system. For example, an authentication mode could specify that the user’s credentials be passed directly through to the external data system. Alternatively, it could specify that the user’s credentials should be mapped to an account that is stored in a Secure Store Service which should then be passed to the external system.
You associate an authentication mode with an external content type in the following ways:
When you create an external content type in Microsoft SharePoint Designer.
If the external system is a Web service, you can use the Microsoft Business Connectivity Services administration pages to specify the authentication mode.
You can specify the authentication mode by directly editing the .XML file that defines the external content type.
The following table describes the authentication modes of the Microsoft Business Connectivity Services:
Authentication mode
Description
PassThrough
Passes the credentials of the logged-on user to the external system. This requires that the user’s credentials are known to the external system.
Note:
If the Web application is not configured to authenticate with Windows credentials, the NT Authority/Anonymous Logon account is passed to the external system rather than the user’s credentials.
This mode is called User’s Identity in the Microsoft Business Connectivity Services administration pages and in SharePoint Designer 2010.
RevertToSelf
When the user is accessing external data from a Web browser, this mode ignores the user’s credentials and sends the application pool identity account under which the BCS runtime is running on the Web server to the external system. When the user is accessing external data from an Office client application, this mode is equivalent to PassThrough mode, because Microsoft Business Connectivity Services running on the client will be running under the user’s credentials.
This mode is called BDC Identity in the Microsoft Business Connectivity Services administration pages and in SharePoint Designer 2010.
Note:
By default, RevertToSelf mode is not enabled. You must use Windows PowerShell to enable RevertToSelf mode before you can create or import models that use RevertToSelf. For more information, see RevertToSelf authentication mode (http://technet.microsoft.com/library/453fa20f-7223-4bb7-96c3-fc92c2eb436d.aspx#BDCIdentity). RevertToSelf mode is not supported in hosted environments.
WindowsCredentials
For external Web services or databases, this mode uses a Secure Store Service to map the user’s credentials to a set of Windows credentials on the external system.
This mode is called Impersonate Windows Identity in the Microsoft Business Connectivity Services administration pages and in SharePoint Designer 2010.
Credentials
For an external Web service, this mode uses a Secure Store Service to map the user’s credentials to a set of credentials that are supplied by a source other than Windows and that are used to access external data. The Web service should use basic or digest authentication when this mode is used.
Important:
To help preserve security in this mode, we recommend that the connection between the Microsoft Business Connectivity Services and the external system should be secured by using Secure Sockets Layer (SSL) or Internet Protocol Security (IPSec).
This mode is called Impersonate Custom Identity in the Microsoft Business Connectivity Services administration pages and in Office SharePoint Designer.
RDBCredentials
For an external database, this mode uses a Secure Store Service to map the user’s credentials to a set of credentials that are supplied by a source other than Windows. To help preserve security in this mode, we recommend that the connection between the Microsoft Business Connectivity Services and the external system should be secured by using Secure Sockets Layer (SSL) or IPSec.
This mode is called Impersonate Custom Identity in the Microsoft Business Connectivity Services administration pages and in Office SharePoint Designer.
DigestCredentials
For a WCF Web service, this mode uses a Secure Store Service to map the user’s credentials to a set of credentials using Digest authentication.
This mode is called Impersonate Custom Identity – Digest in the Microsoft Business Connectivity Services administration pages and in SharePoint Designer 2010.
The following illustration shows the Microsoft Business Connectivity Services authentication modes when it uses credentials.

In PassThrough (User’s Identity) mode (A) the logged-on user’s credentials are passed directly to the external system.
In RevertToSelf (BDC Identity) mode (B) the user’s logon credentials are replaced with the credentials of the process account under which Microsoft Business Connectivity Services is running, and those credentials are passed to the external system.
Three modes use the Secure Store Service: WindowsCredentials (Impersonate Windows ID,) RdbCredentials (Impersonate Custom ID,) and Credentials. In those modes, the user’s credentials are mapped to a set of credentials for the external system and Microsoft Business Connectivity Services passes those credentials to the external system. Solution administrators can either map each user’s credentials to a unique account on the external system or they can map a set of authenticated users to a single group account.
Microsoft Business Connectivity Services can provide access to external data based on an incoming security tokens and it can pass security tokens to external systems. A security token is made up of a set of identity claims about a user, and the use of security tokens for authentication is called “claims-based authentication.” SharePoint Foundation includes a Security Token Service that issues security tokens.
The following illustration shows how the Security Token Service and the Secure Store Service work together in claims-based authentication:

1. A user tries an operation on an external list that is configured for claims authentication.
2. The client application requests a security token from the Secure Token Service.
3. Based on the requesting user’s identity, the Secure Token Service issues a security token that contains a set of claims and a target application identifier. The Secure Token Service returns the security token to the client application.
4. The client passes the security token to the Secure Store Service.
5. The Secure Store Service evaluates the security token and uses the target application identifier to return a set of credentials that apply to the external system.
6. The client receives the credentials and passes them to the external system so that an operation (such as retrieving or updating external data) can be performed.
-
Business Connectivity Service permissions overview
Permissions in Microsoft Business Connectivity Services associate an individual account, group account, or claim with one or more permission levels on an object in a metadata store. By correctly setting permissions on objects in Microsoft Business Connectivity Services, you help enable solutions to securely incorporate external data. When planning a permissions strategy, we recommend that you give specific permissions to each user or group that needs it, in such a way that the credentials provide the least privilege needed to perform the needed tasks.
Caution:
Properly setting permissions in Microsoft Business Connectivity Services is one element in an overall security strategy. Equally important is securing the data in external systems. How you do this depends on the security model and features of the external system and is beyond the scope of this article.
Note:
Business Connectivity Services uses the permissions on the metadata objects and the permissions on the external system to determine authorization rules. For example, a security trimmer can keep external data from appearing in users’ search results. However, if users somehow discover the URL to the trimmed external data, they can access the external data if they have the necessary permissions to the metadata object and the external system. The correct way to prevent users from accessing external data is to set the appropriate permissions both in Business Connectivity Services and in the external system.
-
What can permissions be set on?
Each instance of the Business Data Connectivity service (or, in the hosting case, each partition) contains a metadata store that includes all the models, external systems, external content types, methods, and method instances that have been defined for that store’s purpose. These objects exist in a hierarchy as depicted in the following illustration:

Note:
In the previous hierarchy graphic, labels in parentheses are the names of objects as they are defined in the Microsoft Business Connectivity Services metadata schema. The labels that are not in parentheses are the names of each object as it appears in the user interface of the Business Data Connectivity service. For a full discussion of the Microsoft Business Connectivity Services metadata schema, along with walkthroughs of many development tasks, see the Microsoft SharePoint 2010 Software Development Kit (http://go.microsoft.com/fwlink/?LinkId=166117&clcid=0x409).
The hierarchy of objects in a metadata store determines which objects can propagate their permissions to other objects. In the illustration, each object on which permissions can be set, and optionally propagated, is shown with a solid line; each object that takes its permissions from its parent object is shown with a dotted line. For example, the illustration shows that an External System (LobSystem) can be secured by assigning permissions to it, but an Action cannot be assigned permissions directly. Objects that cannot be assigned permissions take the permissions of their parent object. For example, an Action takes the permissions of its parent External Content Type (Entity).
noteDXDOC112778PADS Security Note
When the permissions on an object in a metadata store are propagated, permission settings to all children of that item are replaced by the permissions of the propagating object. For example, if permissions are propagated from an External Content Type, all Methods and Method Instances of that External Content Type receive the new permissions.
Four permission levels can be set on the metadata store and the objects it contains:
Edit
noteDXDOC112778PADS Security Note
The Edit permission should be considered highly privileged. With the Edit permission, a malicious user can steal credentials or corrupt a server farm. We recommend that, in a production system, you give Edit permission only to users whom you trust to have administrator-level permissions.
Execute
Selectable in clients
Set permissions
The following table defines the meaning of these permissions on the various objects for which they can be set.
Object
Definition
Edit permissions
Execute permissions
Selectable in clients permissions
Set permissions permissions
Metadata store
The collection of XML files, stored in the Business Data Connectivity service, that each contain definitions of models, external content types, and external systems.
The user can create new external systems.
Although there is no “Execute” permission on the metadata store itself, this setting can be used to propagate Execute permissions to child objects in the metadata store.
Although there is no “Selectable in clients” permission on the metadata store itself, this setting can be used to propagate these permissions to child objects in the metadata store.
The user can set permissions on any object in the metadata store by propagating them from the metadata store.
Model
An XML file that contains sets of descriptions of one or more external content types, their related external systems, and information that is specific to the environment, such as authentication properties.
The user can edit the model file.
The “Execute” permission is not applicable to models.
The “Selectable in clients” permission is not applicable to models.
The user can set permissions on the model.
External system
The metadata definition of a supported source of data that can be modeled, such as a database, Web service, or .NET connectivity assembly.
The user can edit the external system. Setting this permission also makes the external system and any external system instances that it contains visible in SharePoint Designer.
Although there is no “Execute” permission on an external system itself, this setting can be used to propagate Execute permissions to child objects in the metadata store.
Although there is no “Selectable in clients” permission on an external system itself, this setting can be used to propagate these permissions to child objects in the metadata store.
The user can set permissions on the external system.
External content type
A reusable collection of metadata that defines a set of data from one or more external systems, the operations available on that data, and connectivity information related to that data.
Although there is no “Edit” permission on an external content type itself, this setting can be used to propagate these permissions to child objects in the metadata store.
The user can execute operations on the external content type.
The user can create external lists of the external content type.
The user can set permissions on the external content type.
Method
An operation related to an external content type.
The user can edit the method.
Although there is no “Execute” permission on a method itself, this setting can be used to propagate Execute permissions to child objects in the metadata store.
There is no “Selectable in clients” permission on a method.
The user can set permissions on the method.
Method instance
For a particular method, describes how to use a method by using a specific set of default values.
The user can edit the method instance.
The user can execute the method instance.
There is no “Selectable in clients” permission on a method instance.
The user can set permissions on the method instance.
-
Special permissions on the Business Data Connectivity service
Along with the general capabilities of setting permissions described earlier, there is a set of special permissions for the Business Data Connectivity service:
Farm administrators have full permissions to the Business Data Connectivity service. This is necessary, for example, to be able to maintain or repair an instance of the service. However, be aware that the farm administrator does not have execute permissions on any object in the metadata store and this right must be given explicitly by an administrator of an instance of the Business Data Connectivity service if it is required.
Windows PowerShell users are farm administrators and can run commands on the Business Data Connectivity service.
Application pool accounts on front end servers have the same permissions to the Business Data Connectivity service as farm administrators. This permission is necessary to generate deployment packages based on Microsoft Business Connectivity Services.
SharePoint Designer users should, in most cases, be given the following permissions on the whole metadata store: Edit, Execute, and Selectable in clients. SharePoint Designer users should not be given Set permissions permissions. If necessary, you can limit the permissions of the SharePoint Designer user to a subset of the metadata store.
Caution:
To help ensure a secure solution, SharePoint Designer should be used to create external content types in a test environment in which Edit permissions can be assigned freely. When deploying the tested solution to a production environment, remove the edit permissions to help protect the integrity of the external data.
-
Common tasks and their related permissions
This section describes common tasks in the Business Data Connectivity service and the required permissions to perform them.
Task
Permissions
Create a new object in the metadata store
To create a new metadata object, a user must have edit permissions on the parent metadata object. For example, to create a new method in an external content type, a user must have permissions on the external content type. See the illustration earlier in this article for child/parent relationships among objects in the metadata store.
Delete an object from the metadata store
To delete a metadata object, a user must have edit permissions on that object. To delete an object and all its child objects (such as deleting an external content type and all its methods) the edit permission is also required on all the child objects.
Adding an external content type to a model
To add an external content type to a model, a user must have edit permissions on the model.
Importing models
To import a model to the metadata store, a user must have edit permissions on the metadata store. If explicit permissions are not assigned on the model, the user who imported it will be given edit permissions on the model.
Exporting models
To export a model from the metadata store, a user must have edit permissions on the model and on all external systems contained in the model.
Generating a deployment package
Deployment packages are generated by the application pool account that is used by the front-end server. This account has full permissions to the metadata store so that it can perform this task.
Setting initial permissions on the metadata store.
When an instance of the Business Data Connectivity service is first created, its metadata store is empty. The farm administrator has full permissions to the store and can set initial permissions.
-
-
Securing Business Connectivity Services
This section discusses additional measures that can be used to help secure Business Connectivity Services
-
Service account
For security isolation, the Business Data Connectivity service application and the front-end server should not use the same service account.
-
Server to server communication
Securing the communication between the Business Data Connectivity service application and external systems helps ensure that sensitive data is not compromised. You need to use an encrypted communication channel to protect data that is sent between servers running SharePoint Foundation 2010 and external systems. Internet Protocol security (IPsec) is one method that can be used to help protect communication. The choice of which method to use depends on the specific communication channels you are securing and the benefits and tradeoffs that are most appropriate for your organization.
-
Applications that use FileBackedMetadataCatalog
For security reasons, RevertToSelf authentication mode is disabled on SharePoint Foundation 2010 by default. However, this does not prevent applications that use the FileBackedMetadataCatalog class from importing models and executing calls that use RevertToSelf authentication. This can result in elevating privileges for users by granting privileges to the application pool account. You should review all applications to ensure that they do not use FileBackedMetadataCatalog class and RevertToSelf authentication before installing them on a production system.
-
-
Diagnostic logging in Business Connectivity Services overview (SharePoint Foundation 2010)
You can troubleshoot issues related to Microsoft Business Connectivity Services on servers that are running Microsoft SharePoint Foundation 2010 by using event logs and trace logs on either client or server. Also, each entry to the event log or trace log has an associated Activity ID that can be used to track a problem from the server to the external data source.
Note:
In addition to the logging methods discussed in this topic, you can use Microsoft System Center Operations Manager Management Pack to monitor a solution that is based on Microsoft Business Connectivity Services. For more information about how to configure System Center Operations Manager Management Pack, see the guide including in the management pack download at Microsoft SharePoint 2010 Products Management Pack (http://go.microsoft.com/fwlink/?LinkId=184971&clcid=0x409).
In this article:
Diagnostic logging in Business Connectivity Services
-
Diagnostic logging in Business Connectivity Services
For solutions that are based on Microsoft Business Connectivity Services, diagnostic logging occurs on servers that are running Microsoft SharePoint Foundation. There are two logs: the event log and the trace log. They both record diagnostic information that Microsoft Business Connectivity Services generate. Event logs record error messages. Trace logs contain more in-depth information, such as stack traces and informational messages. In general, trace logs provide more details than event logs.
Each logged item of information includes an Activity ID, which is a unique GUID value. Activity ID values can also be sent to external systems when a Create, Update, or Delete operation occurs on an item. By using Activity IDs, an action can be traced from the server or client to the external data source. For more information about Activity IDs, see About Activity IDs .
You can set the level of diagnostic logging for the event log and for the trace log. This will limit the types and amount of information that will be written to each log. The following tables define the levels of logging available for the event log and trace log:
Event log levels
Level
Definition
None
No logging occurs.
Critical
This message type indicates a serious error that has caused a major failure in the solution.
Error
This message type indicates an urgent condition. All error events should be investigated.
Warning
This message type indicates a potential problem or issue that might require attention. Warning messages should be reviewed and tracked for patterns over time.
Information
Information messages do not require any action, but they can provide valuable data for monitoring the state of your solution.
Verbose
This event log level corresponds to lengthy events or messages.
Trace log levels
Level
Definition
None
No trace logs are written.
Unexpected
This level is used to log messages about events that cause solutions to stop processing. When set to log at this level, the log will only include events at this level.
Monitorable
This level is used to log messages about any unrecoverable events that limit the solution’s functionality but do not stop the application. When set to log at this level, the log will also include critical errors (Unexpected level).
High
This level is used to log any events that are unexpected but which do not stall the processing of a solution. When set to log at this level, the log will include warnings, errors (Monitorable level) and critical errors (Unexpected level).
Medium
When set to this level, the trace log includes everything except Verbose messages. This level is used to log all high-level information about operations that were performed. At this level, there is enough detail logged to construct the data flow and sequence of operations. This level of logging could be used by administrators or support professionals to troubleshoot issues.
Verbose
When set to log at this level, the log includes messages at all other levels. Almost all actions that are performed are logged when you use this level. Verbose tracing produces many log messages. This level is typically used only for debugging in a development environment.
Diagnostic logs are useful both in development and production environments, but requirements for the level of logging will probably differ depending on the kind of environment. When planning for diagnostic logging in Microsoft Business Connectivity Services, consider the business needs and the lifecycle stage of the environment before you set the logging level.
For example, during solution design, you might, for debugging purposes, set both logging levels to Verbose to capture all the messages that are generated about the state of the system. Conversely, in a production environment, you might want to capture only messages in the categories High, Monitorable, and Unexpected for trace logs and the categories Critical and Error for event logs. Doing this will save logging disk space and limit any negative performance effects of logging.
-
About Activity IDs
A unique GUID value called an Activity ID is generated for each Create, Update, or Delete operation on external data in a solution based on Microsoft Business Connectivity Services. Anything related to the operation that is logged in the trace log or event log includes its Activity ID value.
Important:
In the event logs and trace log files on the server, Activity ID values are labeled as “CorrelationId” values.
The Activity ID value generated for a Create, Update, or Delete operation is sent to the external system along with other information related to that operation. If the external system has a logging mechanism, this value can be captured and logged on that system. Therefore, if an operation causes entries to the SharePoint logs, the same operation can be traced to the external system by using its Activity ID value. This facilitates end-to-end troubleshooting of issues.
Often, an operation such as Create will cause multiple events to be written to the logs. When this happens, the same Activity ID value is used for all events that are logged for the operation. This is useful in troubleshooting issues because the recurring value of the Activity ID facilitates finding all events for a particular operation. Conversely, when the same type of operation occurs repeatedly, a unique Activity ID value is generated for each operation instance. For example, if an item of an external content type is updated twice, each update operation will be associated with a unique Activity ID value.
Tip:
In some circumstances, the Business Data Connectivity service will retry an operation if it failed to go through to the external system. In those cases, the same Activity ID will be used for the retried operation.
-
Diagnostic logging on servers
By default, Microsoft Business Connectivity Services logging is enabled on SharePoint Foundation servers. The default logging levels are:
For the event log: Critical and Error
For the trace log: Medium
Should diagnostic logging of Microsoft Business Connectivity Services become disabled, enable it by selecting Business Connectivity Services on the Diagnostic Logging page in SharePoint Foundation Central Administration. You can also use Windows PowerShell to configure event logs and trace logs on the server. For example, you can change the drive that logging writes to, and you can set the level of verbosity of logging.
For more information about logging in SharePoint Foundation 2010, such as how to set the location of the log files, see Configure diagnostic logging (SharePoint Foundation 2010) (http://technet.microsoft.com/library/a5641210-8224-4e11-9d93-4f96fa4c327c(Office.14).aspx).
You can use Windows PowerShell to view the event logs on the server by and you can export the logs, for example to a spreadsheet program. For more information, see View diagnostic logs (SharePoint Foundation 2010) (http://technet.microsoft.com/library/28a72c44-2c3a-459d-aa64-918c3a71c858(Office.14).aspx).
Microsoft Business Connectivity Services output two categories to the trace log on SharePoint Foundation front end Web servers: BDC_Shared_Services and SS_Shared_Service. You can use the Event Viewer to open the trace log, and you can filter on the relevant log entries by searching on “SPS_BusinessData” (for Microsoft Business Connectivity Services outputs) and “SPS_SecureStoreService”.
-
Example: using diagnostic logging
This short, simplified scenario illustrates the use of diagnostic logging in a production environment. An enterprise has deployed a new time card submission solution based on Microsoft Business Connectivity Services. This solution uses an external system to store timecard information for employees, such as vacation time and sick leave, and to interact with employees and the payroll system when employees report absence from work. Employees use a Web Part to interact with the system.
On the server farm, the logging levels are set to the default values for Microsoft Business Connectivity Services:
For the event log: Critical and Error
For the trace log: Medium
In this scenario, an employee submits a value for the number of sick leave hours but neither the employee nor his manager receives a confirming email message reporting that the sick leave time was successfully submitted. The employee calls the internal technical support service and reports the issue.
The support technician recognizes that the time card application is based on Microsoft Business Connectivity Services. She checks the event log but finds no error associated with the identity of the user at the time the user submitted the time card request. She then checks the trace log, where she finds the evidence of the activity: an Update operation associated with the user at the appropriate time. The Update operation in the trace log includes an Activity ID value which the support technician notes.
The support technician knows that logging is also supported on the external system. Using the Activity ID, she locates the item logged on the external system and finds evidence of an error written to the log at the end of the Update operation: the update failed because the employee had used up all of his allotted sick leave time. She also notes that there is no log entry confirming that an email message was generated on the external system immediately at the end of the Update operation. The support technician concludes that there is an error in the logic of the time card application. Although the application properly did not allocate sick time pay when the employee exceeded his allotted amount of hours, it failed to generate an email message informing the employee of the issue. She reports the problem to the development team that created the application and the development team updates the application.
-
See Also
Monitoring overview (SharePoint Foundation 2010) (http://technet.microsoft.com/library/d2e48b54-1a32-4ec6-8b9e-b884b7faca8f(Office.14).aspx)
Configure diagnostic logging (SharePoint Foundation 2010) (http://technet.microsoft.com/library/a5641210-8224-4e11-9d93-4f96fa4c327c(Office.14).aspx)
Business Connectivity Services overview (SharePoint Foundation 2010)
-
-
Plan workflows (SharePoint Foundation 2010)
A workflow is a feature of Microsoft SharePoint Foundation 2010 that moves documents or list items through a specific sequence of actions or tasks related to a business process. Workflows can be used to manage common business processes such as document review or approval.
In this section:
Workflows overview (SharePoint Foundation 2010)
This article introduces the types of business processes that workflows can facilitate and describes the workflows included in SharePoint Foundation 2010.
Choose a workflow authoring tool (SharePoint Foundation)
This article describes the different Microsoft supported workflow authoring tools, how they can be used together for rapid workflow authoring.
Plan for workflow security and user management (SharePoint Foundation 2010)
This article highlights some aspects of workflow behavior that relate to security and raises other issues for administrators and workflow developers to consider when they plan to configure and develop workflows.
Approval Workflow: A Scenario (SharePoint Foundation 2010)
This article shows how an approval-type workflow that is created in Microsoft SharePoint Designer 2010 or Workflow Designer in Visual Studio 2010, and that is then hosted by using SharePoint Foundation 2010 might look.
-
See Also
Workflow administration (SharePoint Foundation 2010) (http://technet.microsoft.com/library/30f3251d-53a8-4fd4-ad87-31c48591a0f7(Office.14).aspx)
-
-
Workflows overview (SharePoint Foundation 2010)
The workflow feature in Microsoft SharePoint Foundation 2010 enables solution architects, designers, and administrators to improve business processes. Fundamentally, a workflow consists of two things: the forms that a workflow uses to interact with its users and the logic that defines the workflow’s behavior. Understanding how workflows are created requires knowledge about both.
In this article:
-
Workflow overview
Workflows in SharePoint Foundation 2010 enable enterprises to reduce the amount of unnecessary interactions between people as they perform business processes. For example, to reach a decision, groups typically follow a series of steps. The steps can be a formal, standard operating procedure, or an informal implicitly understood way to operate. Collectively, the steps represent a business process. The number of human interactions that occur in business processes can inhibit speed and the quality of decisions. Software that simplifies and manages this “human workflow” enables the automation of interactions among groups who participate in the process. This automation results in more speed, overall effectiveness of the interactions, and often a reduction in errors.
You can model business processes by using flow charts, such as those created using Microsoft Visio 2010 and can represent business processes by using workflow terminology. You can automate business processes, such as document approval, by associating a workflow with data in SharePoint Foundation 2010. For example, you can create a workflow to route a document for review, track an issue through its various stages of resolution, or guide a contract through an approval process.
One problem that many IT departments face when implementing business processes that require participation of information workers is that those processes do not integrate with the way people actually work. For a business process to be effective, it must be integrated with the familiar, everyday tools and applications used in the workplace so that it becomes part of the daily routine of information workers. In the electronic workplace, this includes integration with e-mail, calendars, task lists, and collaboration Web sites.
-
Benefits of using workflows
The primary benefits of using workflows are to facilitate business processes and improve collaboration.
Business processes that enterprises use depend on the flow of information or documents. These business processes require the active participation of information workers to complete tasks that contribute to their workgroup’s decisions or deliverables. In SharePoint Foundation 2010, these types of business processes are implemented and managed by using workflows.
Examples of business processes that could be facilitated by workflows include:
Contract approval Guiding a proposed contract among members of an organization who must approve or reject it.
Expense reporting Managing the submission of an expense report and associated receipts, reviewing the report, approving it, and reimbursing the submitter.
Technical support Guiding the progress of a technical support incident as it is opened by a customer, investigated by a support engineer, routed to technical experts, resolved, and added to a knowledge base.
Interviewing Managing the process of interviewing a job candidate. This includes scheduling and tracking interview appointments, collecting interview feedback as it accumulates, making that feedback available to subsequent interviewers, and facilitating the hire/no-hire decision.
-
Automating business processes
Businesses depend on business processes. Although those processes often involve software, the most important processes in many organizations depend on people. Workflows can automate interactions among the people who participate in a process to improve how that process functions, increase its efficiency, and lower its error rate.
Many processes can benefit from automated support for human interactions. Examples include the following:
Approval A common aspect of human-oriented business processes is the requirement to get approval from multiple participants. What is being approved can vary widely, ranging from a Microsoft Word document that contains next year’s marketing plan to an expense report from a trip to a conference. In every case, some number of people must review the information, perhaps appending comments, and then indicate approval or rejection.
Coordinating group efforts Whether it is preparing a response to a request for proposal (RFP), managing the translation of a document into one or more languages, or something else, many processes require people to work together in an organized way. By defining the steps of the process through an automated workflow, the group’s work can be made more efficient and the process itself more predictable.
Issue tracking Many business processes generate a list of outstanding issues. An automated workflow can be used to maintain that list, assign issues to the people who can resolve them, and track the status of that resolution.
To support these kinds of automated business processes, SharePoint Foundation 2010 can run workflow applications. Based on Windows Workflow Foundation 3.5, these applications interact with people through a Web browser. For more information about Windows Workflow Foundation 3.5, see Windows Workflow Foundation (http://go.microsoft.com/fwlink/?LinkId=127778).
-
Workflows improve collaboration
Workflows help people collaborate on documents and manage project tasks by implementing business processes on documents and items on a SharePoint site or site collection. Workflows help organizations follow consistent business process practices. Workflows increase organizational efficiency and productivity through management of the tasks and steps involved in those business processes. Workflows speed up decision making by helping to ensure that the appropriate information is made available to the appropriate people at the time that they need it. Workflows also help ensure that individual workflow tasks are completed by the appropriate people and in the appropriate sequence. This enables the people who perform these tasks to concentrate on performing the work instead of on the work processes.
For example, on a SharePoint Foundation 2010 site, you can create a workflow to be used with a document library to route a document to a group of people for approval. When the author starts this workflow, the workflow creates document approval tasks, assigns these tasks to the workflow participants, and then sends e-mail alerts to the participants.
When the workflow is in progress, the workflow owner or the workflow participants can check progress on the Workflow Status page. When the workflow participants complete their workflow tasks, the workflow ends, and the workflow owner is automatically notified that the workflow has finished.
-
-
Predefined workflows
For sites and site collections created in Microsoft SharePoint Foundation 2010, a predefined Three-state workflow is included by default, and is the only predefined workflow available in SharePoint Foundation 2010. The Three-state workflow can be used to manage business processes that require organizations to track a high volume of issues or list items, such as customer support issues, sales leads, or project tasks.
The Three-state workflow is so named because it tracks the status of an issue or item through three different states, and through two transitions between the states. For example, when a Three-state workflow is initiated on an issue in an Issues list, SharePoint Foundation 2010 creates a task for the assigned user. When the user completes the task, the workflow changes from its initial state (Active) to its middle state (Resolved) and creates a task for the assigned user. When the user completes the task, the workflow changes from its middle state (Resolved) to its final state (Closed), and creates another task for the user the workflow is assigned to at that time. Note that when you associate the Three-state workflow with a list, you can choose to specify different state names, other than Active, Resolved, and Closed. Note that the Three-state workflow is not supported for use with libraries.
You can also make a copy of the predefined workflow to use as a starting point when creating a custom workflow.
-
Sample workflow scenario
Imagine that you work for Adventure Works, a sports store franchise that sells bicycles worldwide. This company has sales representatives that visit different countries to help new franchisees open new sports stores.
The scenario described in this section is one where an expense report is submitted for approval. If the expense report is for less than $5,000.00, a manager is required to approve, disapprove, or forward it. If the expense report is equal to, or more than, $5,000.00, a manager must review the expense report, comment on it, and then if the manager recommends approval, it is forwarded to a vice-president, who must approve or disapprove it.
In this scenario, the expense report form is an ASPX form displayed to the user on a SharePoint Web page. The workflow is a sequential type of workflow project created in Microsoft SharePoint Designer 2010, and is composed of both automated tasks and tasks that require human action. The workflow is running on SharePoint Foundation 2010.
1. The sales representative — the first workflow participant — browses to an intranet self-service portal and selects the Expense Report form. A data entry page opens. The sales representative first fills out a simple expense report form that contains entries for the person’s name, the expense purpose, the expense total, and the name and e-mail address of the person’s direct manager. The sales representative then clicks Submit to submit the form.
Upon submission of the form, the data is saved centrally, the workflow is initiated, and the review task is assigned to the approver (in this case, the sales representative’s manager).
2. The workflow notifies the sales representative’s manager. The notification is an e-mail message that contains instructions for completing the task and provides a link to a Web site that displays the Expense Report form.
3. The manager, the second workflow participant, goes to the Web site and reviews the expense report. The workflow task item provides three actions that the manager can perform: Approve, Disapprove or Forward.
If the expense report is less than $5,000.00, the manager sees options to Approve or Disapprove the expense report.
If the expense report is more than $5,000.00, the manager sees options to Forward the expense report to a company vice president, or to Disapprove the expense report at the manager’s level.
4. The manager takes action to approve, disapprove, or forward the expense report, and the workflow continues:
If the expenses are approved by the manager, the task completion sends a message to the workflow indicating that the task is completed, the workflow notifies the sales representative through an e-mail message, and then the workflow adds the expense data to the line-of-business (LOB) accounting system.
If the expenses are not approved by the manger, he types an explanation for his decision. The task completion sends a message to the workflow indicating that the task is completed, and then the workflow notifies the sales representative through an e-mail message.
If the manager selects the option to forward the expense report to a company vice president, the manager makes relevant comments in the form and then clicks Forward. The workflow then notifies the vice president through an e-mail message that contains instructions for completing the task and provides a link to a Web site that displays the Expense Report form.
5. The vice president — the third workflow participant — is given the option to Approve or Disapprove the expense report. When the vice president acts to approve or disapprove the expense report, the workflow continues.
If the vice president approves the expenses, the expense data is added to the accounting system, the workflow notifies the sales representative and manager through e-mail, and then the workflow notifies SharePoint that the task is completed.
If the vice president does not approve the expenses, the vice president types an explanation for the decision into the form. The workflow notifies the sales representative and manager through e-mail, and then the workflow notifies SharePoint that the task is completed.
As you can imagine, there are many ways to expand the functionality of this workflow within the context of this scenario. For example, you can configure the workflow so that if the vice president disapproves the expense report, the report is returned to the sales representative’s manager. The manager can further justify the expense and resubmit it for approval to the vice president, can pass along the disapproval to the sales representative, or take some other action.
In this sample expense report scenario, the business rules are always the same. This workflow solution defines the manager and vice president approvers, defines the business logic for the routing of the workflow, and predefines the content of the notifications. However, many real-world applications have complex business rules. Routing for approval can depend on many business variables. Notifications can also change, depending on other variables.
For example, imagine that in the same expense reporting solution, you have to route the expense report to as many as ten managers, depending on the expense purpose, the expense total, and the date of submission. Additionally, depending on the expense purpose, the content of the notifications sent by the workflow contain some small differences. This means that there can be multiple workflow solutions with different routing levels and notifications.
Microsoft SharePoint Foundation 2010 enables you to create and implement workflow solutions to meet the business needs of your organization. It does this by leveraging the workflow design and customization features of SharePoint Designer 2010 and Microsoft Visual Studio.
-
Workflow types: Declarative and compiled
An important distinction to understand about workflows is whether they are a declarative workflow, such as those created using Microsoft SharePoint Designer 2010 or a compiled workflow, such as those created using Visual Studio 2010. A declarative workflow is a workflow that is built from conditions and actions that are assembled into rules and steps, and that sets the parameters for the workflow without writing any code.
A compiled workflow, like declarative workflows, can also be built from conditions and actions without the workflow author actually writing code but also enable the workflow author to add custom code to the workflow. Regardless of whether a workflow author adds custom code to a code-centric workflow, the most important distinction to understand is the difference in the way that declarative and compiled workflows are run on the server. A compiled workflow is stored on a server running SharePoint Foundation 2010 as a precompiled dll file whereas a declarative workflow is deployed on a server running SharePoint Foundation 2010 as an Extensible Object Markup Language (XOML) file and compiled in the content database each time an instance of the workflow is started.
For more information about the Microsoft supported tools for authoring workflows, see Choose a workflow authoring tool (SharePoint Foundation).
-
Workflow templates
When creating a custom workflow using SharePoint Designer 2010, you can choose to create a workflow that will only be used with a specific list, library, content type, or site. Alternatively, you can choose to create a reusable workflow template, which can be associated with multiple lists, libraries, content types, or sites.
Note:
SharePoint Designer 2010 does not support creating reusable workflows for sites. Instead, you can use Visual Studio 2010 to create them.
When authoring a workflow, you can also choose to make it global, which means that once it is activated on a site it will be active for all the sub-sites below that site as well. However, you cannot use SharePoint Designer 2010 to create a global workflow and then save the workflow as a WSP file.
-
Workflow associations
SharePoint Foundation 2010 takes advantage of the Workflow Foundation runtime. One or more workflow templates, each containing the code that defines a particular workflow, can be installed on a server. Once this is done, an association can be created between a specific template and a document library, list, content type, or site. This template can then be loaded and executed by the SharePoint Foundation 2010-hosted Workflow Foundation runtime, creating a workflow instance.
Like all Workflow Foundation workflows, those based on SharePoint Foundation 2010 rely on Workflow Foundation runtime services. The Workflow Foundation standard persistence service allows the state of a persisted workflow to be linked with the document or item, and allows for long-running business processes that can span days, months, or years.
SharePoint workflows can be associated with lists, libraries, and content types. Reusable workflows created using Visual Studio 2010 can also be associated with sites. The following table describes the minimum permissions required to associate a workflow.
Associate workflow with
Minimum permissions required
List or library
Full Control permission level on the list or library
List or library content type
Member of the Site Owners group on the SharePoint site
Site content type
Member of the Site Owners group on the SharePoint site
Site
Member of the Site Owners group on the SharePoint site
For more information about workflow associations, see Add a workflow association (SharePoint Foundation 2010) (http://technet.microsoft.com/library/19872b79-f5ac-4b56-a24b-75af33c89763(Office.14).aspx).
-
Choose a workflow authoring tool (SharePoint Foundation)
What is a workflow? Fundamentally, it consists of two things: the forms a workflow uses to interact with its users and the logic that defines the workflow’s behavior. Understanding how workflows are created requires knowing something about both.
Because it communicates with users through a Web browser, a workflow relies on ASP.NET to display its forms. Accordingly, those forms are defined as .aspx pages. A workflow can potentially display its own forms at four points in its lifecycle:
Association: When an administrator associates a workflow template with a particular document library or list, he might be able to set options that will apply to every workflow instance created from this association. If a workflow author chooses to allow this, she must provide a form that lets the administrator specify this information.
Initiation: The initiator of a workflow might be allowed to specify options when he starts a running instance. In the approval scenario just described, for instance, the options included specifying the list of workflow participants and defining how long each one had to complete his or her task. If a workflow allows this, its author must provide a form to allow the initiator to set these options.
Task Completion: The running workflow instance must display a form to the participants in the workflow to let them complete their task. This form is what allowed the approvers in the earlier scenario to make comments on the document and indicate their approval or rejection.
Modification: The creator of a workflow can allow it to be modified while it’s running. For example, a workflow might allow adding new participants after it has begun executing or extending the due date for completing tasks. If this option is used, the workflow must display a form at this point to let a participant specify what changes should be made.
Workflows built solely on Microsoft SharePoint Foundation 2010 define their forms as .aspx pages. A workflow’s logic is always defined as a group of activities, just as with any workflow based on the Windows Workflow Foundation (WF). To specify the logic and forms for a workflow, Microsoft provides two different tools, each targeting a different audience. Software developers can use the Workflow Designer feature of Windows Workflow Foundation. This tool runs inside Visual Studio 2010 Professional Edition and provides a graphical environment for organizing activities into workflows. Information workers, a less technical group, can use Microsoft SharePoint Designer 2010 to create workflows without writing code. The next two sections examine how workflows can be created by using each of these tools.
-
Authoring workflows with Visual Studio 2010 and WF Workflow Designer
In many ways, a workflow is like a flowchart. Given this, it makes sense to provide a graphical tool that lets developers specify a workflow’s actions. This tool is SharePoint Workflow tools in Visual Studio 2010 Professional, which is a project type that uses the Windows Workflow Foundation (WF) Designer, and adds deployment and forms support for SharePoint Workflows. Developers can use WF Workflow Designer to define graphically a workflow’s activities and the order in which those activities will be executed. The screen below shows a simple example of how this looks in Microsoft Visual Studio.
Collect Feedback Workflow

The activities available for use appear in the Toolbox on the left side of the screen. A developer can drag these activities onto the design surface to define the steps in a workflow. The properties of each activity can then be set in the Properties window that appears in the lower right corner.
The Base Activity Library Windows Workflow Foundation provides a group of fundamental activities, as described earlier. Microsoft SharePoint Foundation also provides a set of activities designed expressly for creating workflows. Among the most important of these are the following:
OnWorkflowActivated: provides a standard starting point for a workflow. Among other things, this activity can accept information supplied by a SharePoint administrator by using the Association form when the workflow is associated with a document library, list, content type, or site. It can also accept information supplied by the Initiation form when the workflow is started. Every workflow must begin with this activity.
CreateTask: creates a task assigned to a particular user in a task list. For example, the approval workflow in the scenario described earlier used this activity to add a task to the task list used by each of the participants. This activity also has a SendEmailNotification property that, when set to true, automatically sends an e-mail message to the person for whom this task was created.
OnTaskChanged: accepts information from the Task Completion form. The approval workflow in the earlier scenario used this activity to accept the input of each participant when the document was approved.
CompleteTask: marks a task as completed.
DeleteTask: removes a task from a task list.
OnWorkflowModified: accepts information from the Modification form, which can then be used to change how this instance of the workflow behaves. If the workflow’s creator chooses not to include any instances of this activity in the workflow, that workflow cannot be modified while it’s running.
SendEmail: sends e-mail to a specified person or group of people.
LogToHistoryList: writes information about the workflow’s execution to a history list. The information in this list is used to let users see where a workflow is in its execution, look at the workflow’s history after it’s completed, and more. To allow this kind of monitoring, the workflow’s author must write information to a History list at appropriate points in the workflow’s execution. Because it provides its own mechanism for tracking workflows, Microsoft SharePoint Foundation doesn’t support WF’s standard tracking service.
A typical pattern for a simple workflow begins with an OnWorkflowActivated activity, and then uses a CreateTask activity to assign a task to a participant in the workflow. The BAL’s standard While activity might then be used to wait until the user completes the task. To learn when this has happened (perhaps the user makes multiple changes to the task, then checks a box on the Task Completion form when she’s done), an OnTaskChanged activity executes within the While, extracting whatever information the user has entered on that form. When the user has completed the task, a CompleteTask activity might execute, followed by a DeleteTask. The workflow can then go on to the next participant, using CreateTask to assign a task to him, and so on. And of course, other things can occur, such as sending e-mail, logging information to the history list, or even including the BAL’s Code activity, which allows running arbitrary code.
All of the activities provided by SharePoint Foundation are concerned with letting workflows operate within the SharePoint environment. The business logic a workflow implements is entirely up to the creator of that workflow. In fact, a developer authoring a workflow is free to create and use her own custom activities—she’s not required to use only those provided by SharePoint Foundation and WF.
As described earlier, Windows Workflow Foundation supports sequential, parallel, and state machine workflows. A workflow created with the WF Workflow Designer can also use any of these options. To allow this, SharePoint Foundation adds project types to Visual Studio, one for each of these workflow styles.
Whatever style is chosen, the developer must define more than just the workflow’s logic; he must also specify the .aspx form it should use. To do this, the developer relies on a file named element.xml. This file provides a template that the developer fills in to specify what form, if any, should be displayed at each of the four points at which a workflow is allowed to do this.
A developer must do some work to pass information between a workflow and the .aspx forms it uses. The Microsoft.Windows.SharePoint.Workflow namespace exposes an object model for developers. Using the types in this namespace, the creator of a workflow can pass information from an .aspx form to the workflow and vice-versa.
Once a workflow and its forms have been created, the developer must package them into what is referred to as a Feature. A SharePoint administrator must then install this Feature, which includes installing the workflow’s assemblies to the target system’s global assembly cache. The new workflow will now be visible to the administrator as a workflow template that can be associated with a document library, list, content type, or site.
For a software developer, creating a workflow by using Visual Studio and the WF Workflow Designer isn’t especially hard. The developer needs to understand the specifics of working in this environment, but much of what he’s doing will be familiar. Yet software developers aren’t the only people who’d like to author workflows. As described next, people who aren’t professional developers can also create workflows by using Microsoft SharePoint Designer 2010.
-
Authoring workflows with Microsoft SharePoint Designer 2010
Microsoft SharePoint Designer 2010 is a separate application that is available as a free download. Microsoft SharePoint Designer enables information workers and others to add application logic (implemented as a workflow) to SharePoint sites. This is certainly a useful goal, but Microsoft SharePoint Designer also addresses another important problem. If a developer creates a workflow by using Visual Studio, that workflow must be deployed on a server running SharePoint Foundation like any other feature. Yet many SharePoint administrators won’t allow arbitrary code to be deployed on their servers, believing that the risk of destabilizing the system is too great. Being able to create straightforward business logic tied to documents and list items is very useful, however, and it’s something that many SharePoint users need. Along with allowing less technical people to create workflows, Microsoft SharePoint Designer also addresses this problem by providing a safer way to define and deploy business logic on servers running SharePoint Foundation.
The workflow scenarios that Microsoft SharePoint Designer is intended to address are different in some ways from those addressed by Visual Studio and WF Workflow Designer. While it’s certainly possible to create complex applications, the intent of Microsoft SharePoint Designer is to let users add business logic to SharePoint sites. For example, suppose that a site contains a list that allows its users to submit change requests. Microsoft SharePoint Designer could be used to create a workflow that automatically informs the submitter when her change request is accepted or rejected. Similarly, a custom workflow might inform a particular group of users whenever a new document is added to a particular document library. Performing this kind of custom notification isn’t complicated—creating the workflows is easy—but it’s challenging with earlier versions of SharePoint Foundation because of administrators’ reluctance to install user-written code.
There’s an obvious question here: why should logic created with Microsoft SharePoint Designer be treated any differently? What makes SharePoint administrators willing to allow workflows built with this tool to be deployed on the systems for which they’re responsible? The answer is that workflows built with Microsoft SharePoint Designer can only use activities from an administrator-controlled list. In addition to the activities provided by SharePoint Foundation, a site administrator can choose whether to include custom activities created by a developer on this list. By defining exactly what workflows are allowed to do, a SharePoint administrator can have more confidence that deploying logic created by using Microsoft SharePoint Designer won’t destabilize his system.
Both because it’s intended for information workers rather than developers and because it emphasizes simpler scenarios, Microsoft SharePoint Designer uses a different model for creating workflows than the Visual Studio-hosted WF Workflow Designer. Instead of a graphical approach, Microsoft SharePoint Designer uses a rule-based approach. It’s somewhat similar to the Rules Wizard in Microsoft Outlook, a tool that’s familiar to many people. The screen below illustrates how a user of Microsoft SharePoint Designer defines a step in a workflow. Notice that this workflow runs some actions in parallel; some actions run serially. Earlier versions of SharePoint Foundation supported running actions only serially; actions only ran consecutively.
Process Order Workflow

Each step can have a condition and an action. The condition determines whether this step’s action should be executed, as in the If statement shown above. The choices for actions include things such as assigning an entertainer to an event, collecting approval, and many more. Each of these actions is actually carried out by some SharePoint Foundation activity, and the activities used here are the same as with Visual Studio and WF Workflow Designer. The list of actions can also include any other activities allowed by the SharePoint administrator for this site, including custom activities created by developers.
Even though its user interface looks quite different from the graphical approach used with Visual Studio and WF Workflow Designer, Microsoft SharePoint Designer creates a standard WF workflow. What’s actually produced is a workflow that is sequential, parallel, or combination of both with conditions expressed using the WF rules engine. Workflows created with this tool do have some limitations, however. For example, they can’t be modified while they’re running, unlike those built using Visual Studio and WF Workflow Designer, and only sequential and parallel workflows can be created—state machines aren’t supported. Also, workflows built with this tool can be authored against a specific document library, list, or site when they’re designed. Workflow authors can also create a general workflow template that can be later associated with any library, list, or content type. While this does place limits on how a workflow can be used, it also makes deploying the workflow much simpler. In fact, when a user finishes authoring a workflow with Microsoft SharePoint Designer, the tool provides a one-click deployment of the workflow to the target site, which includes activating the workflow. This is significantly less complicated than the multi-step deployment process required for workflows created using Visual Studio and WF Workflow Designer.
Workflows created by using Microsoft SharePoint Designer can also display customized forms. Rather than require workflow authors to create .aspx pages directly, however, the tool instead generates those pages. The author specifies details about how the generated pages should look, such as what fields they should contain, and Microsoft SharePoint Designer takes care of the rest. Of the four points in a workflow’s lifecycle where forms can be used, however, only two are used with workflows created by using Microsoft SharePoint Designer: Initiation and Task Completion. Because every workflow created with this tool must be associated with a particular document library, list, content type, or site there’s no need for an association step and hence no Association form. And since these workflows can’t be modified while they’re running, there’s no need for a Modification form.
Microsoft SharePoint Designer also provides the ability to import workflows that were created using Microsoft Visio 2010. This enables business managers or workflow authors to create the workflow logic using a well known graphical environment. A workflow author can then import the workflow logic into Microsoft SharePoint Designer, modify it if necessary, and then publish it to a SharePoint site.
SharePoint Foundation provides a great deal of functionality for creating document-oriented workflows. Yet ultimately, it’s a platform for development and execution. On its own, it provides no workflow functionality that’s directly usable by end users. Workflows running on SharePoint Foundation also have other restrictions, such as the inability to interact with participants by using Office client applications.
-
Authoring tool comparison
The following table shows the important differences between the tools that Microsoft supports for creating workflows in SharePoint Foundation by using both SharePoint Designer and WF Workflow Designer in Visual Studio 2010 Professional Edition.
Capability/Requirement
SharePoint Designer
WF Workflow Designer in Visual Studio
Workflows can be created using only actions that are approved by site administrators?
Yes
No
Workflows are accessible in client applications (other than the browser)?
Yes
Yes
Can use Microsoft Visio Professional to create workflow logic?
Yes
No
Need to write code?
No
Yes
Additional activities (other than those provided by SharePoint Foundation) are provided?
No
Yes
Can create custom activities?
No
Yes
Workflow can be modified while it is running?
No
Yes
One-click publishing of workflows?
Yes
Yes
Workflows can be deployed remotely?
Yes
No
Can be made available across the farm?
No
Yes
Can be scoped to a site collection?
Yes
Yes
-
Plan for workflow security and user management (SharePoint Foundation 2010)
Before deploying workflows in Microsoft SharePoint Foundation 2010 to users, administrators might have concerns about security issues, such as information disclosure or elevation of privilege. This article highlights some aspects of workflow behavior that relate to security and raises other issues for administrators and workflow developers to consider when they plan to configure and develop workflows.
In this article:
List manager, administrator, and developer roles and responsibilities (http://technet.microsoft.com/library/cda43349-4574-4eec-97cd-78963542d8b6.aspx#BKMK_Rolesandresponsibilities)
Running workflows as an administrator (http://technet.microsoft.com/library/cda43349-4574-4eec-97cd-78963542d8b6.aspx#BKMK_Workflowsrunasadministrator)
Workflow configuration settings (http://technet.microsoft.com/library/cda43349-4574-4eec-97cd-78963542d8b6.aspx#BKMK_Workflowconfigurationsettings)
Information disclosure in task and workflow history lists (http://technet.microsoft.com/library/cda43349-4574-4eec-97cd-78963542d8b6.aspx#BKMK_Disclosure)
Spoofing and tampering attacks in the task and workflow history lists (http://technet.microsoft.com/library/cda43349-4574-4eec-97cd-78963542d8b6.aspx#BKMK_Spoofing)
User-Impersonation Step type for declarative workflows (http://technet.microsoft.com/library/cda43349-4574-4eec-97cd-78963542d8b6.aspx#BKMK_UserStep)
-
List manager, administrator, and developer roles and responsibilities
The following are some common workflow actions and the related responsibilities, which explain the role of administrators and developers in running workflows.
-
Workflow developers
Develop workflow schedule and template Workflow developers are responsible for coding the assembly that contains the business logic that will run on a SharePoint item. This assembly is called a workflow schedule. They are also responsible for packaging the workflow forms and assembly into a workflow feature, or into a workflow template.
-
Site administrators
Manage Central Administration workflow settings Site administrators can control general workflow settings, such as task alert results and external participant settings on the SharePoint Central Administration Web site.
Deploy Workflow features Site administrators can install workflow features on a site collection to make them available for association.
-
List administrators (anyone with Manage List or Web Designer permissions)
Add workflows List administrators must associate (add) a workflow template to a list or content type, according to the business needs of the list or content type. This association makes the workflow template available to end users, who can then select default values and settings.
Remove workflows List administrators can remove workflow associations from a list or content type, or prevent new instances from running.
Terminate a workflow If a workflow instance fails, list administrators can stop a running workflow instance, such as when a workflow instance produces an error or does not start, by using the Terminate this workflow link on the Workflow Status page. This action is reserved for administrators.
-
-
Running workflows as an administrator
The most important security concept to be aware of is that workflows run as part of the system account in SharePoint Foundation 2010, through the identity application pool settings on the server computer and domain. This means that within SharePoint Foundation 2010, workflows have administrator permissions. On the server, workflows have the same permissions as the application pool, which frequently has administrator permissions. These permissions enable workflows to perform actions that ordinary users cannot perform, such as routing a document to a specific location or records center, or adding a user account to the system.
This setting, that workflows have administrator permissions, cannot be changed. It is up to the workflow schedule (that is, the workflow code) to detect user actions and, based on those actions, continue or roll back changes, or impersonate a user in order to mimic that user’s permissions.
When they deploy workflows, administrators must understand the actions that the workflow will perform so that they can assess possible risks associated with elevation of permission in a workflow and help the workflow developer reduce any security concerns.
-
Workflow configuration settings
SharePoint Foundation 2010 has some configuration settings that administrators have to set according to their security needs.
-
Required permissions to start a workflow
In addition to preventing the elevation of permissions in the code, list administrators can restrict the permission level that is required to start a workflow during the association process. Administrators can select either of two permission levels to start a specific workflow association: Edit Item or Manage List.
The default setting for associating a workflow is to allow users with Edit Item permissions to manually start a workflow. This means that any authenticated SharePoint Foundation 2010 user on the list who has Edit Item permissions can start an instance of this workflow association. If during workflow creation the administrator selects the option to require that the user have Manage Lists permissions in order to start the workflow, only list administrators can start an instance of this association.
Because workflows are designed to be used by standard contributors, most workflows do not require the restriction to Manage Lists permissions. However, administrators can use this setting for workflows such as a document disposal workflow, where the administrator wants only certain people to execute the disposal actions.
-
Central Administration settings
The following settings can be found on the Central Administration page by clicking Application Management and, in the Web Applications section, clicking Manage web applications. On the Web applications page, select the Web application that you want to configure, and in the Manage group of the ribbon click General Settings, and then select Workflow. The Workflow Settings page opens, and the following settings are displayed:
User-Defined Workflows
Workflow Task Notifications
-
Enable user-defined workflows
By default, user-defined workflows are enabled for all sites on the Web application, as shown in the User-Defined Workflows section of the Workflow Settings page. When this option is selected, users can define workflows in a workflow editor such as the SharePoint Designer 2010 workflow editor. Users who define these workflows must have Manage List permissions on the site to which they are deploying the workflow.
-
Task notification for users without site access
On the Workflow Settings page, in the Workflow Task Notifications section, you can set options for sending notifications about pending workflow tasks to users who do not have access to the site.
Internal users
In SharePoint Foundation 2010 it is possible to resolve the names of internal users in the directory service who are not members of the site or who do not have access to that task. In this case, an administrator can select the Alert internal users who do not have site access when they are assigned a workflow task option in the Workflow Task Notifications section to set whether such users receive a task notification by e-mail. This option means that users are alerted when they are assigned a workflow task. This option is enabled by default, and the e-mail message that users receive contains a link that they can click to request access to the site (administrators must still grant access). This e-mail message might also contain information about the document. This information can include the title of the document and instructions from the workflow owner. If there are information disclosure concerns associated with internal users who are not members of the site, administrators might want to disable the Alert internal users who do not have site access when they are assigned a workflow task setting.
External users
External users who are not in the directory service but who are assigned a well-formed SMTP e-mail address can still be assigned workflow tasks. Because external users will find it difficult to access the document, SharePoint Foundation 2010 includes a setting, Allow external users to participate in workflow by sending them a copy of the document, which makes it possible to send external users a task notification by e-mail with the document attached. When this option is enabled, the task is assigned to the workflow owner, and the external user can complete the task by sending e-mail to the owner.
By default, the option Allow external users to participate in workflow by sending them a copy of the document is disabled. But this setting can be useful in situations that require external participation, such as approval of business documents that involve external customers. Administrators who enable this setting (select Yes) must verify that the workflow schedule supports the external participant setting. For example, when a task is created for an external user, the custom workflow must specify the external e-mail address in the OnBehalfEmail property in the SPWorkflowTaskProperties object that was used to initialize the task). Several built-in workflows in SharePoint Foundation 2010 support this setting.
Custom workflow developers who want to enable this functionality must work with administrators to determine whether there are information disclosure risks in attaching the actual document to an external e-mail message. Administrators must evaluate the benefits and risks when enabling this setting.
-
-
Information disclosure in task and workflow history lists
Because tasks and history list items can contain data about users and the actions they perform on documents, the items might disclose confidential information. For example, a promotion Approval workflow might collect feedback on its tasks that an organization wants only the workflow owner and each participant in the task to see.
Task and history lists are typical lists in a site. By default, therefore, all readers can view tasks and history items. Administrators and developers must determine the information that cannot be disclosed and decide whether to help secure task and history items that are created by the workflow.
Securing these items can be done in several ways. For example, administrators can set list-level permissions. If disclosure is to be private — that is, not publicly available but available to a specific group of people — administrators can create a new task or history list and set permissions for the list that are targeted to that group. If administrators do not want anyone to see history events on a workflow status page, they can remove view permissions to the workflow history list from which a status page pulls its information. Users who do not have permissions to view the history list itself, or any item on the list, will receive an Access Denied error when they open any status page that pulls data from that history list.
If finer restrictions are required, workflow developers can set per-item permissions when they create tasks or history items. The CreateTask activity has a SpecialPermissions property that gives only specified permissions to access the newly created task. The LogToHistoryList activity does not have such a property, so to set per-item permissions on history list items, administrators must use the object model (OM) in SharePoint Foundation 2010. Per-item permissions can affect performance negatively and should not be used unless they are necessary.
Tasks and history items do not have to be handled in the same manner. Administrators can mix and match list permissions and item-level permissions.
-
Spoofing and tampering attacks in the task and workflow history lists
Any contributor can modify tasks or history items if there are no restrictions on those lists. This means that malicious users can modify task descriptions to give participants incorrect instructions or to order participants to click malicious links. To change the perceived results of a process, malicious users also can add false or inaccurate history events or can modify history events to make them false or inaccurate.
As detailed earlier, task and history lists are normal lists in a site. By default, there are no permission restrictions on either task lists or history lists. To avoid spoofing and tampering attacks, administrators must determine the vulnerabilities that exist and either restrict access to columns in a list (for example, make vulnerable columns such as task descriptions read-only so that only the workflow can set them on item creation), set special permissions on the list, or set item-level permissions on the items in a list.
-
Security issues in the workflow history list
A key benefit of workflows is the ability to track process information to provide visibility into a process. The workflow history list is a repository for this information, where a workflow status page can search for data related to a workflow instance and can make this information available to users. Users can see all items to which they have access in the history list.
However, because the workflow history list tracks information, users might assume that it can be used as an audit trail for events. This is not the case: Workflow history is not a security feature. History lists are standard SharePoint lists that are used for storing events that are visible to any user and that have no special permissions associated with them. By default, users can modify and add events if they have edit and add permissions on the site. To audit events, use the SharePoint’s Audit Log feature. Only administrators can access this log and the log does not require additional work to protect it from tampering attacks.
To better protect the history list, administrators can restrict edit and add permissions to the list, so that only system account administrators (for example, workflow administrators) and list administrators can add items. List administrators must have add permissions to log “Terminate this workflow” events. If edit and add permissions are restricted on the history list, users still must be granted view permissions in order to see status information.
-
-
User-Impersonation Step type for declarative workflows
The User-Impersonation Step type can be used to run sections of declarative workflows by the person who authored the workflow rather than by the workflow’s initiator. Declarative means a model that you use to create the workflow and set the parameters for the workflow without writing any code.
In SharePoint Foundation 2010, declarative workflows always run in the user context of the workflow initiator unless an impersonation step is encountered. If an impersonation step is encountered, the declarative workflow is run in the context of the workflow associator. The default workflow tasks respect SharePoint permissions by impersonating the user who started a workflow when the workflow is run. This arrangement keeps things fairly safe in SharePoint Foundation 2010, but blocks many scenarios in which a workflow designer with high permission levels wants to author a powerful workflow that can be completed successfully by users who have lower permission levels.
Through a safe and scoped form of privilege elevation, site actions can be automated through workflow. This reduces the burden on a SharePoint site administrator. Automation of a high-security process is useful in publishing and approval scenarios in which existing actions are enabled to impersonate someone other than the workflow’s initiator.
The following are sample scenarios that demonstrate the User-Impersonation Step type:
Publish to a secure list
Jackie has locked down the Pages document library for the public face of her SharePoint site. She has set up an Approval workflow that, by using Microsoft SharePoint Designer 2010, submits content from site contributors for approval. Jackie puts her workflow actions in an impersonation step so that the workflow actions will always impersonate her, a site administrator, as the author of the workflow.
When Connie (a contributor) posts a content draft to the Pages library of the site, and tries to publish her article, that action causes Jackie’s Approval workflow to start so that the post can be reviewed and approved. Tasks are sent out to the approvers in the workflow on behalf of Connie. Upon review and approval by the approvers, the system sets the moderation status of the post to “Approved”, even though Connie does not have permission to approve pages.
Granting permissions to users
Joanne has set up a workflow in SharePoint Designer 2010 that uses a user-impersonation action “Add User to Group” to grant Design permissions to her site. Because the workflow uses an impersonation scope, the action of adding a user to the group will always be performed on Joanne’s behalf.
The rest of the workflow lets contributors visit the site and complete a form to log their access request to a list.
For example, a separate user, Olivier, receives a task when Connie, a user, logs a request, and when he approves the task, Connie is added to the Designer group for the site even though neither Olivier nor Connie has Manage Lists permissions on Joanne’s site.
Templates and taking ownership
William created several workflows in SharePoint Designer 2010 and saved them as templates for reuse across the company, but he soon leaves the company. His account is removed, his administrator status is revoked, and now the SharePoint Designer 2010 workflows that William created fail to complete due to the loss of William’s permissions.
A parent SharePoint site administrator, John, can intervene for each workflow, without having to re-create the workflows in SharePoint Designer 2010. John takes ownership of the administrative symptoms in each broken template. After doing this, secure publishing and access granting now occur under John’s name instead of William’s — and nothing else has changed.
The following are workflow actions that can be impersonated:
Set Content Approval Status (as Owner)
Create List Item (as Owner)
Update List Item (as Owner)
Delete List Item (as Owner)
Add/Remove/Set/Inherit List Item Permissions (as Owner)
As a SharePoint administrator, you must consider the possible security effects of incorporating impersonation into workflows on the SharePoint site. This applies to new actions but also to existing actions such as updating list items.
For example, consider a model in which user-impersonation actions in the workflow could still run as the initiator. If a user has administrator permissions only over a site in the site collection, that user could maliciously create a workflow to gain rights to the parent Web of the site. All that the malicious user would have to do is to persuade the administrator to upload a file to a document library on the malicious user’s site to begin the workflow’s attack and compromise the whole parent Web of the site.
This risk prompted development of the restriction “user-impersonation actions always impersonate their associator” in SharePoint Designer 2010. The associator is the person who associates a workflow to a particular list or Web. In SharePoint Foundation 2010 declarative workflows, the associator is the same person as the workflow author; that is, the user who builds the workflow in SharePoint Designer 2010. However, the associator can also be anyone who associates a declarative workflow template. The concern now is that the author/associator is forced to accept responsibility for anything that occurs because of a User-Impersonation Step type, because the author/associator’s credentials are being used in the elevation. This requires that the authors/associators understand the workflows they design or associate. Therefore, during workflow creation, SharePoint Designer 2010 provides a cautionary message on the workflow creation page to the author/associator about the User-Impersonation Step type.
-
Approval Workflow: A Scenario (SharePoint Foundation 2010)
The most common example of human workflow in most organizations is some variation of approval: A group of people must approve or reject some document, and perhaps add comments to explain their decisions. This article shows how an approval-type workflow that is created in SharePoint Designer 2010 or Workflow Designer in Visual Studio 2010, and that is then hosted by using SharePoint Foundation 2010 might look. Before reading this example, it is useful to define the roles that different people play.
Workflow author The developer or information worker who creates a workflow template.
SharePoint Foundation 2010 administrator The person who installs a workflow template and associates it with a document library or list.
Workflow initiator The person who starts a workflow, causing a workflow instance to be created from a particular workflow association.
Workflow participants The people who interact with a workflow instance to complete the business process that it supports.
As described in the following section, people in each of these roles play their own parts in creating, installing, starting, and using a workflow.
-
Authoring a workflow
Microsoft provides two options for creating workflows in SharePoint Foundation 2010. Developers use Visual Studio 2010 and Workflow Designer, whereas information workers use the rules-based approach that SharePoint Designer 2010 provides. In both cases, the result is a workflow template that must be deployed to a server that is running SharePoint Foundation 2010. This scenario assumes that a workflow template has already been created.
-
Associating a workflow
Before you can use a workflow, you must install a workflow template on a server that is running SharePoint Foundation 2010, and then you must associate the workflow with a particular document library, list, content type, or (in the case of a site workflow) site. You can then start the workflow from any document or item in that library or list. Although workflows cannot be explicitly started from content types, a workflow that is associated with a content type can be started from a document or list item to which that content type is attached. Because workflows operate in the same manner on items and documents, a workflow template can typically be attached to a list, library, or content type. You can also create a template that can be associated only with a particular list or library.
Both installation and association are performed automatically for workflows that are deployed by using SharePoint Designer 2010. However, when you use Visual Studio to deploy workflows, a server administrator must explicitly install the workflow template. In addition, a user must associate the template with a library, list, content type, or site. Whoever creates this association also assigns the association a unique name, which enables users to reference it. Optionally, the workflow author can let the person who creates the association set options for the workflow behavior, such as a default list of people who can always participate in the process. The same template can be associated with multiple libraries, lists, or content types, and each association can be customized as required. After the association is created and any available options are set, a workflow initiator can create a workflow instance from this association, as described in the following section.
-
Associating a workflow with a site
Site workflows are associated with the site itself. An item does not have to be started for the workflow to run.
You can use site workflows for processes that do not have a list item context. For example, you could create a workflow to request permissions for the site, a workflow to request and provision a new site, or a workflow that uses context that is stored outside the SharePoint site, without having to create a corresponding SharePoint list item from which to start the workflow.
Site workflows can be associated with a site through the site’s settings and can be started on the site itself. SharePoint Designer 2010 can also deploy site workflows directly to a site.
Site workflows work in the same way as list items, as described earlier in this article, except that site workflows cannot be started from a document or item in a library or list.
For more information, see Add a workflow association (SharePoint Foundation 2010) (http://technet.microsoft.com/library/19872b79-f5ac-4b56-a24b-75af33c89763(Office.14).aspx).
-
Starting a workflow
SharePoint Foundation 2010 provide three options to start an instance of a workflow. All three options run the workflow from the beginning every time. (If an instance of a workflow that is created from a particular association is already running on a particular document or list item, it is not possible to start another instance of the workflow on the same document or item.) The following are the options for starting a workflow:
A SharePoint Foundation 2010 user can manually start a workflow.
You can configure a workflow to run automatically when a user creates a document or item.
You can configure a workflow to run automatically when a user changes a document or item.
For example, a Microsoft Word user can upload a new document to a site’s document library. This causes an instance of a workflow that is associated with that library to start.
This scenario uses the first of these three options: manually starting an Approval workflow for a document. To start a workflow instance from a document in a document library, a SharePoint Foundation 2010 user does the following:
1. Points to the document and selects Workflows from the drop-down menu.
2. Selects the workflow to start.
This example assumes that a workflow that will route the document for approval has been created.
When a workflow is started (that is, when an instance of a workflow is created), it can also display a screen that enables a user to specify relevant information. For a workflow that routes a document for approval, this information can include the name of each person who must approve the document, an indication of when each approval is due, and a list of people to be notified. After this information is supplied, the user clicks Start. The workflow begins to execute and requests each participant to review the document in the order in which names were entered on this screen.
When a workflow is started, it can also optionally send an e-mail message to the person who started it. Similarly, a workflow can inform its creator by e-mail when it has finished. You can also configure the workflow to notify the participants in the workflow — in this example, the people who are approving the document—by e-mail that the workflow has something for them to do.
-
Interacting with a workflow
The concept of tasks models the interaction between a person and a running workflow. A task is a unit of work that is assigned to an individual. For example, each person on this workflow’s approval list will be assigned a task that requests approval of the document. SharePoint Foundation 2010 can have a task list for every site, and a running workflow can add tasks to this list that specify the person or persons who are assigned to each task. Users of that site can see the work that is awaiting them by accessing their task list through a Web browser. Optionally, you can have a custom task list for just your workflow tasks.
To a SharePoint Foundation 2010 user, the list of waiting tasks is merely another list. In this example, the user browses to the team SharePoint site and selects the option to view the list of Tasks that are assigned to him. To work on a task, the user in this example clicks the task name.
Because the way that a workflow interacts with participants can vary, the workflow itself defines the screen that is displayed to the user. In this example, the workflow provides options to approve or reject the document and a text box in which participants can type comments.
Other available options let users reassign the task to another person or to request a change. Here, the user might type a comment, and then click Approve. The workflow then creates a task in the task list of the next person in its list of approvers. When every participant has responded, the workflow ends.
SharePoint Foundation 2010 workflows also provide other options, including the following:
The initiator of a workflow can check the status of the workflow.
For example, in the scenario described here, the initiator might check the progress of the approval process.
A workflow can be modified while it is executing.
The workflow’s author determines the allowed modifications, if any. An Approval workflow, for example, could allow the addition of a new approver while the workflow is in progress. The ability to modify in-progress workflows is important because it reflects how people actually work. Because spontaneous change to business processes is a part of life within any business, SharePoint Foundation 2010 workflows were designed to let users handle this.
-
Summarizing the process
When a workflow template is installed on a site and associated with a document library, list, site, or content type, a site user can start an instance of a workflow.
1. The process starts when the workflow initiator selects a document and starts an instance of a workflow.
2. The initiator creates a workflow instance from this association.
3. The user customizes this new instance and starts it.
4. The running instance of the workflow adds a task to the task list of a participant.
The approval workflow that is used in this scenario assigns these tasks sequentially. However, you can assign tasks to many participants at the same time, which allows tasks to be performed in parallel.
5. Participants in the workflow can learn about tasks that the workflow has assigned to them by checking their task lists.
6. Each participant interacts with the running instance of the workflow to complete assigned tasks.
In the example described here, this interaction required approving a document, but the interaction could be anything that the workflow author wants.
It is worth noting that the document on which a workflow runs is not itself sent from person to person. Instead, the document remains on the site, and each workflow participant is given a link to it. In fact, there is no requirement that the workflow use the document or item with which it is associated. Another point worth emphasizing is that SharePoint Foundation 2010 itself defines what is displayed to the initiator of the workflow and the participants in the workflow in steps 1, 2, and 5. However, the workflow author defines and creates the ASPX Web pages that are used in step 3 and step 6. This allows the author to control how users customize and interact with the workflow.
-
Plan site creation and maintenance (SharePoint Foundation 2010)
If you plan on having more than a few site collections in your Microsoft SharePoint Foundation 2010 environment, you need to be sure that you have a plan for site creation and maintenance. Without such a plan, it is difficult to control or track when SharePoint sites are created, whether sites are still active, and when you can safely remove inactive sites. Before you deploy and make sites available to users, you need to answer questions such as:
Do you want to tightly control site creation or to allow many users to create sites?
At which level in the site hierarchy should additional sites be created?
How do you find and remove unused sites in your environment?
Articles and worksheets help you design and record a plan for site creation and maintenance. This will help you prepare to manage growth in your environment.
In this section:
Plan process for creating sites (SharePoint Foundation 2010)
Discusses how to determine which type of site creation process will fit your organization, and which method to use to implement that process.
Plan site maintenance and management (SharePoint Foundation 2010)
Discusses how to plan for maintaining your SharePoint sites from the beginning to make sure that your sites stay current, useful, and usable.
Plan quota management (SharePoint Foundation 2010)
Contains guidance about how to determine settings for quota templates and recycle bins, and how to decide whether or when to delete unused Web sites.
-
Plan process for creating sites (SharePoint Foundation 2010)
Some organizations need to maintain tight control over who can create sites, or when sites are created. Other organizations can allow users more access and freedom to create sites when needed. This article helps you determine which type of site creation process will fit your organization, and which method to use to implement that process.
In this article:
Determine who can create sites and a method for site creation
Plan for Self-Service Site Management
-
Determine who can create sites and a method for site creation
By default, new site collections (and therefore new top-level Web sites) can only be created by using Central Administration, which means that they can only be created by members of the Farm Administrators group. This behavior might suit your organization if you want your environment to be tightly controlled and managed, with only a few people allowed to add top-level sites. However, the default top-level site creation method might not suit your organization if you have any of the following requirements:
You want users to be able to easily create informal, perhaps even disposable, top-level sites, such as for short-term projects.
You want to create an informal space for team, group, or community interaction.
You are hosting top-level sites (either internally or externally) and want the process for requesting and receiving a top-level site to be as quick and low cost as possible.
There are several ways to allow users to create their own sites, while still maintaining some control over your environment. Consider which of the following methods will work best for your organization.
Self-Service Site Management In Central Administration, you can turn on Self-Service Site Management to allow users to create site collections under the /sites path (or other path you specify) within a particular Web application. This method is best used when you want to allow groups or communities to create sites. This method also works well if you are hosting sites and want to allow users to create sites without waiting for a complicated process. The sign-up page for Self-Service Site Management can be customized or replaced with a page that includes all of the information you might need to integrate with a billing system or to track custom metadata about the site at creation time. This method does not work well when large numbers of users need access to multiple sites. Because Self-Service Site Management creates site collections, which have separate permissions, users need to be added uniquely to different site collections. If you use subsites instead, the users can be inherited from the parent site in the site collection. Search works within a specific site collection. Therefore, if you want users to be able to find content across multiple sites, make the sites into subsites within a site collection.
Subsites of existing sites Limit users to creating subsites of existing sites, rather than new site collections and top-level sites. Any user who has the Full Control or Manage Hierarchy permission level on an existing site can create a subsite. This method is the most limited, because you still control how many site collections there are. Because the sites are always subsites of other sites, they can either be easy to organize (if there are just a few) or very difficult to organize and browse (for example, if everyone in your organization wants a subsite and they create them at different levels in the site collection’s hierarchy, the site collection can soon become very difficult to navigate).
Note:
If you do not want users to have this capability, you can remove the Create Subsites right from the Full Control and Manage Hierarchy permission levels, either at the site collection or Web application level.
Note:
Keep in mind that none of these methods can control how much space each site takes up in your content databases. To control site sizes, you should use quotas and set a size limit for site collections. You cannot set individual size limits for subsites. For more information, see Plan site maintenance and management (SharePoint Foundation 2010).
-
Plan for Self-Service Site Management
Self-Service Site Management allows users to create and manage their own top-level Web sites automatically. When you turn on Self-Service Site Management for a Web application, users can create their own top-level Web sites under a specific path (by default, the /sites path). When turned on, this capability advertises itself with an announcement added to the top-level site at the root path of the Web application, so any users who have permission to view that announcement can follow the link.
Note:
If you want to use a path other than /sites for Self-Service Site Management, you must add the path as a wildcard inclusion. For more information, see Plan for collaboration sites (SharePoint Foundation 2010).
This capability can obviously affect the security for your Web server. Self-Service Site Management is disabled by default — you must turn on the feature to use it. You enable Self-Service Site Management for a single Web application at a time. If you want to use it on all Web applications in your server farm, you must enable it for every Web application individually.
If you enable Self-Service Site Management, you should consider the following:
Generally, you should require a secondary site collection administrator. Administrative alerts, such as those for when quotas are exceeded, or checking for unused Web sites, go to the primary and secondary administrators. Having more than one contact reduces administrator involvement with these sites because the secondary contact can perform required tasks even if the primary contact is not available.
Define a storage quota and set it as the default quota for the Web application.
Review the number of sites allowed per content database. Combined with quotas, this will help you limit the size of the databases in your system.
Enable unused Web site notifications, so that sites that are forgotten or no longer of value can be identified.
Because Self-Service Site Management creates new top-level Web sites on an existing Web application, any new sites automatically conform to the Web application’s default quota settings, unused Web site notification settings, and other administrative policies.
-
Plan for custom site creation processes
You can, of course, create your own process for site creation by using a custom form to request a site that integrates with a back-end billing system to charge a customer’s credit card or a corporate cost center. If you have a complicated system or process that you want to include as part of site creation, you should create a custom application to call the site creation interface and perform any other tasks you require. However, if you simply want to add a few custom fields to the site creation page (for example, to track which department in your company is requesting a particular site), you should consider using Self-Service Site Management and customize the sign-up page to include the information that you need. You can customize the scsignup.aspx page in the site definition to include the metadata that you need without having to develop an entire application.
For more information about building custom applications or editing pages in a site definition, see the SharePoint 2010 developer portal on MSDN (http://go.microsoft.com/fwlink/?LinkId=178818).
-
Worksheet
Use the following worksheet to plan the process for creating sites:
Site Creation and Maintenance Worksheet (http://go.microsoft.com/fwlink/?LinkId=193521&clcid=0x409)
-
Plan site maintenance and management (SharePoint Foundation 2010)
All Web sites, particularly sites that have more than one author, get cluttered. Periodic review and cleanup can help keep your site functioning well, whether your site is large or small. If you build a plan for maintaining your site or sites from the beginning, you can ensure that they stay current, useful, and usable.
In this article:
-
Plan for site maintenance
Your site maintenance plan will be different from that for any other environment, and it will contain different elements. Site maintenance is different for sites managed by an IT department than it is for user-created sites and managed sites. However, some best practices for a site maintenance plan include:
Ask users what they want in IT-managed sites. Perform periodic surveys to determine what your users need from the site.
Use usage logs and reports to find out which areas of the site are being used, and then correlate that with user surveys to find out what can be improved.
Archive obsolete content or sites. However, if you are going to archive or delete obsolete content or sites, be sure that users understand that plan and that you perform these actions only at predictable times. For example, publish a schedule of when you are going to archive content or delete unused sites.
Periodically review site permissions. For example, review the permissions quarterly to remove permissions for any users who have left the group or project.
Select a reasonable time interval for your maintenance activities. For example, if you plan to conduct periodic user surveys, do not conduct them more than twice a year (and preferably, no more than once a year).
Create a plan for regular backups of site content. Determine or discover how often backups will be made, and the process for restoring content when necessary. For more information about planning for backup and restore, see Plan for backup and recovery (SharePoint Foundation 2010).
Start now, during your planning process, to create a plan for site maintenance. Record your plan, including how often to tune up the site and archive content. Get your plan reviewed by members of your team and representatives of your user base. This way, you can identify any concerns that users might have now, determine how best to address these concerns, and have a plan for site maintenance in place by the time your site goes live.
You can record this information in the Site Creation and Maintenance Worksheet (http://go.microsoft.com/fwlink/?LinkId=193521&clcid=0x409).
-
Plan for managing site collections
One part of your site maintenance plan should be a plan for how to manage the size and number of site collections in your environment. This is most important if you are allowing Self-Service Site Management. Most organizations want to be able to predict and control how much growth they can expect from sites because of the impact that they can have on database resources. For example, if a particular content database contains 100 sites, and one of those sites is taking up more than 50 percent of the space, then that site might need to be in its own content database. This will ensure that you preserve some room for additional growth, while maintaining the ability to back up and restore the databases.
Two methods for managing site collections are:
Site collection quotas Use this method to control how large site collections can become.
Site use confirmation and deletion Use this method to monitor and remove unused site collections.
-
Plan site collection quotas
Use quotas to track and limit site storage. You can send a warning e-mail message to site collection administrators when site storage reaches a particular size (in megabytes), and then lock the site to further content when site storage reaches a maximum size. When you perform your database and server capacity planning, determine what size limits (if any) you want to enforce. The following list describes how to take the best advantage of quotas:
Create different quota templates for different site types. For example, you might want different quotas for different divisions, or for different customer types, or for different paths (perhaps sites under the /sites path only get 100 MB per site collection, whereas sites under the /vip path can take up to 300 MB per site collection). Whenever you create a site collection from Central Administration, you can specify on which quota template it is based. Note that sites created by using Self-Service Site Management use the default quota for the Web application. For more information, see Create, edit, and delete quota templates (SharePoint Foundation 2010) (http://technet.microsoft.com/library/6d984258-158b-40d5-b4a5-cdb2cfe8e5f3(Office.14).aspx).
Give enough room for reasonable growth in sites. Depending on what each site is used for, storage space needs can vary dramatically. Sites are designed to grow over time as they are used. A quota limit of 50 MB is unlikely to be enough storage space to start with for most sites, and is unlikely to be anywhere near enough for a site that has a long life.
Allow for reasonable notice between the warning e-mail message and locking the site for exceeding its quota. For example, do not set the warning limit to 80 MB and the site storage limit to 85 MB. If users are in the middle of uploading several large files, they will not be happy if blocked from completing that task with very little notice.
-
Plan site use confirmation and deletion
You need to plan how to handle sites that become inactive after a project has ended, or sites that users created just to test out some ideas, and then abandoned. Site use confirmation and deletion can help you keep your environment cleaner, by helping you identify when sites are no longer needed. This feature works by automatically sending an e-mail message to site owners to see if they consider their site active. If the owner does not respond to the e-mail message (after a specified number of messages over a specified length of time), the site can be deleted.
To plan for site use confirmation and deletion, decide the following:
How long you want to wait before checking to see if a site is inactive. The default length of time for team or project sites is 90 days after site creation, but you should probably give owners longer than that. For a test or personal site, 90 days is probably too long. Usually a site that was created, was actively used, and is now ready to be deleted or archived, took at least six months and probably a few years to complete that life cycle. Reminders every six months are valuable for those situations.
How often you want to send an e-mail message to site owners to see if their sites are inactive. After the first e-mail message, if the site administrator does not respond, you can continue with additional notices at daily, weekly, or monthly intervals.
Whether you want to automatically delete unused sites. If the site administrator does not respond to multiple e-mail messages, do you want to go ahead and delete the site automatically? We recommend that you make a backup first. You can do so by making sure that regular backups are performed. You can use the SharePoint 2010 developer portal on MSDN (http://go.microsoft.com/fwlink/?LinkId=178818) to customize this functionality so that it automatically makes a backup of the site before deletion, but this is not default behavior.
If you are going to automatically delete unused sites, how many e-mail messages will you send to site owners before you do so? By default, four weekly notices are sent before site deletion, but you can increase or decrease this number to suit your needs.
For more information, see Manage unused Web sites (SharePoint Foundation 2010) (http://technet.microsoft.com/library/eb760fce-48e0-43a8-9bcf-febb868f7115(Office.14).aspx).
-
-
Worksheet
Use the following worksheet to plan for site maintenance and management:
Site Creation and Maintenance Worksheet (http://go.microsoft.com/fwlink/?LinkId=193521)
-
Plan quota management (SharePoint Foundation 2010)
A quota specifies storage limit values for the maximum amount of data that can be stored in a site collection. Quotas also specify the storage size that, when reached, triggers an e-mail alert to the site collection administrator. Quota templates apply these settings to any site collection in a SharePoint farm.
By default, a quota contains 300 points. A point is a relative measurement of resource usage, for example, CPU cycles, memory, or page faults. Points enable comparisons between measurements of resource usage that could not be compared otherwise. For example, it takes millions of CPU cycles to make up one point, but each time a sandboxed solution stops working is counted as one point. For more information about sandboxed solutions, see Sandboxed solutions overview (SharePoint Foundation 2010).
Quotas are particularly useful when you are using Microsoft SharePoint Foundation 2010 in enterprise environments, such as a company-wide intranet or an Internet Service Provider (ISP). You should use quotas in these environments to ensure that one site collection cannot use so many resources that other site collections can no longer function. You can assign a quota template to a site collection when you create the site collection, or you can assign a quota template at a later time. You can also reverse a decision to use quotas at any place in the site collection hierarchy.
In this article:
About planning quota management
Determine quota template settings
-
About planning quota management
The basic steps to plan quota management are the following:
1. Determine quota template settings
2. Determine recycle bin settings
3. Delete unused Web sites
This article contains guidance about how to determine the quota settings for site collections in an enterprise. This article does not include prerequisite information such as how to configure outgoing e-mail, start the Disk Quota Warning timer job, or plan performance and capacity.
-
Determine quota template settings
There is no default quota template for site collections in a SharePoint Foundation 2010 environment. For example, a quota for a site collection might use the following settings as a starting point:
1. Automated e-mail is sent to a site collection administrator when the size of the site reaches 450 megabytes (MB).
2. Users are prevented from uploading additional documents when the size of a site collection reaches 500 MB.
You must evaluate the size and number of items that you expect users to store in their sites. You must also adjust these settings appropriately to ensure that the sites are used in accordance with an organization’s best practices. For example, if a specific team or group in an organization has a business need to store a greater volume of content on its team site, you can adjust the quota limits for that site collection.
The size of the data reported by quotas does not necessarily match the size of the storage in the database. This is because the quota feature estimates storage figures for empty sites (that is, sites that contain no user content) and includes those figures in the quota, in addition to the actual storage from the database. The estimated size of an empty site includes the real size of the template pages for SharePoint Foundation 2010, for example, the forms pages and the pages in the _layouts directory.
If you change the values for a quota template, those changes apply only to new site collections to which you apply the template. SharePoint Foundation 2010 does not apply the changed quota values to existing sites collections unless you use the object model to update the quota values in the database.
-
Determine recycle bin settings
The recycle bin can help to prevent the permanent deletion of content. The recycle bin enables site owners to retrieve items that users have deleted, without requiring administrator intervention such as restoring files from backup tapes. Key planning considerations include whether to use the second-stage recycle bin and how much space to allocate.
The recycle bin is turned on and off at the Web application level. By default, the recycle bin is turned on in all the site collections in a Web application.
The recycle bin has two stages. When a user deletes an item, the item is automatically sent to the first-stage recycle bin. By default, when an item is deleted from the first-stage recycle bin, the item is sent to the second-stage recycle bin. The second-stage recycle bin stores items that users have deleted from their recycle bins. Only site collection administrators can restore items from the second-stage recycle bin. The size that is specified for the second-stage recycle bin increases the total size of the site. You must plan data capacity accordingly.
Consider allocating at least a small amount of space, for example, 10 percent, to the second-stage recycle bin to accommodate cases in which a user mistakenly deletes an important document, a folder in a document library, or a column in a list.
Items in both the first-stage and the second-stage recycle bins are automatically deleted when the time period specified for the deleted items expires (by default, 30 days). However, when the size limit of the second-stage recycle bin is reached, items are automatically deleted starting with the oldest items. Site collection administrators can also empty the second-stage recycle bin manually. For more information, see Configure Recycle Bin settings (SharePoint Foundation 2010) (http://technet.microsoft.com/library/267e6d15-1411-458f-8944-ee8cbf305368(Office.14).aspx).
-
Delete unused Web sites
You can delete a quota template if you change your quota structures. However deleting a quota template does not delete quota values from site collections to which a quota template has been applied. If you want to remove quotas from all site collections that use a specific quota template, you must use the object model or perform a SQL Server query.
Automatic deletion of unused Web sites can help you lessen the risk of deleting data that is critical to business operations. You should include the following tasks in your planning process:
Require a secondary contact for all sites. If the site owner is not available or leaves the organization, the secondary contact can confirm the usage of the site. If you do not have a secondary contact and you shorten the number of days or number of notices that are given before you delete an unused site, you might accidentally delete a site that is still required.
Archive sites before they are deleted automatically. You will be able to restore the sites that contain business-critical information or plan to store the content databases for a longer duration, so that a deleted site can be restored.
For more information, see Manage unused Web sites (SharePoint Server 2010) (http://technet.microsoft.com/library/4737381b-24e5-4c32-bdff-10dd4a81e648(Office.14).aspx).
-
Plan e-mail integration (SharePoint Foundation 2010)
Enabling communication is a critical component for creating Web applications in which group members can interact with each other and keep up with changes to information through the use of alerts. The site collection features that are dependent on communications being properly set up include:
Alerts that notify group members when things have changed.
Administrative messages related to requests for site access and other site administration issues.
Discussion groups.
To make the most effective use of the communications features, planning should include understanding the software requirements and maintenance considerations.
Plan communication by using the following articles:
Plan incoming e-mail (SharePoint Foundation 2010), which provides information on how to set up e-mail for discussion groups.
Plan outgoing e-mail (SharePoint Foundation 2010), which provides information on how to use alerts and administrative messages.
-
Plan incoming e-mail (SharePoint Foundation 2010)
The incoming e-mail feature of Microsoft SharePoint Foundation 2010 enables SharePoint sites to receive and store e-mail messages and attachments in lists and libraries. This article helps server and farm administrators understand the choices they need to make before they deploy the incoming e-mail feature for their organization.
In this article:
-
About incoming e-mail
The incoming e-mail feature enables teams to store the e-mail that they send to other team members without opening the SharePoint site and uploading the content that was sent in e-mail. This is possible because most types of lists and libraries can be assigned a unique e-mail address.
Before configuring incoming e-mail, you must perform the following tasks:
If you are using the basic scenario, each SharePoint front-end Web server must be running the Simple Mail Transfer Protocol (SMTP) service and the Microsoft SharePoint Foundation Web Application service.
If you are using the advanced scenario, you can use one or more servers in the server farm to run the SMTP service and to have a valid SMTP server address. Alternatively, you must know the name of a server outside the farm that is running the SMTP service and the location of the e-mail drop folder.
For more information about installing the SMTP service, see Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx).
-
Key decisions for planning incoming e-mail
As you plan to implement incoming e-mail, you must decide whether to use a basic or and advanced scenario, as described below.
-
Using a basic scenario
You can enable a basic incoming e-mail scenario by installing the Simple Mail Transfer Protocol (SMTP) service on the server running SharePoint Foundation 2010 and enabling incoming e-mail by using the automatic settings mode with all default settings. In this scenario, e-mail is delivered directly to your SMTP server and SharePoint Foundation 2010 periodically checks for e-mail in the default e-mail drop folder that is automatically configured by the SMTP service.
Selecting the automatic settings mode and accepting all the default settings is the easiest way to enable incoming e-mail because all configuration settings are made for you and, therefore, little expertise is required. For most organizations, this configuration is all that is needed.
You enable a basic incoming e-mail scenario in the following steps:
1. The server administrator uses the Add Features Wizard to install the SMTP Server feature on the server from which you want to receive incoming e-mail. This installs and starts the SMTP service on that server.
2. The farm administrator enables incoming e-mail by using the automatic settings mode and accepting all the default values.
3. The site collection administrator enables the incoming e-mail feature on the libraries and lists in which they want to store incoming e-mail and assigns each library and list a unique e-mail address in the form address@SMTPserveraddress, for example, sharedfiles@SMTPserver.contoso.com.
When users send e-mail to the address of a list or library, SharePoint Foundation 2010 detects that new e-mail has been delivered and sends it to the appropriate list or library based on the e-mail address.
Note:
You can also use the automatic settings option in an advanced scenario and select whether to use the Microsoft SharePoint Directory Management service, a safe e-mail server, and an incoming e-mail server display address. These options are all discussed in the “Using the advanced scenario” later in this article.
If this basic scenario meets your needs, you can skip the remainder of this article. For more information, see Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx).
-
Using an advanced scenario
For more advanced administrators, additional choices are available, some of which require more expertise to deploy than choosing the basic scenario with all default options. This section describes the following configuration options:
SharePoint Directory Management service
Incoming e-mail server display address
Safe e-mail server
E-mail drop folder
If you use the advanced scenario to configure incoming e-mail, you will need to perform additional procedures. For more information, see Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx).
-
SharePoint Directory Management service
The SharePoint Directory Management service connects SharePoint sites to your organization’s user directory to provide enhanced e-mail features. The benefit of using this service is that it enables users to create and manage e-mail distribution groups from SharePoint sites. This service also creates contacts in your organization’s user directory so people can find e-mail-enabled SharePoint lists in their address books. However, using SharePoint Directory Management service requires more management because it is communicating with Active Directory Domain Services (AD DS).
Note:
It is recommended that you use Microsoft Exchange Server together with SharePoint Directory Management service. If you do not, you must customize your own directory management service.
You can configure the SharePoint Directory Management service by using either the automatic or the advanced settings mode. You can choose to enable the SharePoint Directory Management service in your SharePoint server farm, or you can use the SharePoint Directory Management service of another farm. One advantage of using the service running on another farm is that Active Directory permissions are managed in a centralized place (that is, on the other farm).
To enable this service on a server or server farm runningSharePoint Foundation 2010, the SharePoint Central Administration application pool account used by SharePoint Foundation 2010 must have write access to the container that you specify in Active Directory. This requires an Active Directory administrator to set up the organizational unit (OU) and the permissions on the OU. The advantage of using the SharePoint Directory Management service on a remote farm is that you do not need the help of an Active Directory administrator to create and configure the OU if the OU already exists.
Note:
There are a number of procedures that you need to perform if you plan to use SharePoint Directory Management service. For more information, see Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx).
A typical directory management scenario proceeds in the following steps:
1. A site collection administrator creates a new SharePoint group.
2. The administrator chooses to create a distribution list to associate with that SharePoint group and assigns an e-mail address to that distribution list.
3. Over time, the administrator adds users to and removes users from this SharePoint group. As users are added to and removed from the group, the SharePoint Directory Management service automatically adds and removes them from the distribution list, which is stored in the Active Directory directory service. Because distribution lists are associated with a particular SharePoint group, this distribution list is available to all members of that SharePoint group.
4. By default, e-mail addresses are automatically generated for discussion boards and calendars on team sites and then added to the team distribution list. The e-mail addresses for these two lists will be in the following form, by default: GroupAddress.discussions and GroupAddress.calendar.
5. By including e-mail addresses for discussion boards and calendars in the distribution list, all e-mail and meeting invitations sent to this distribution list will be archived in the team site.
For more information about SharePoint Directory Management Service, see Inside SharePoint: SharePoint Directory Integration (http://technet.microsoft.com/en-us/magazine/2008.09.insidesharepoint.aspx) (http://go.microsoft.com/fwlink/?LinkId=151766).
-
SharePoint Directory Management Service configuration options
When you configure the SharePoint Directory Management service to create distribution groups and contacts in Active Directory, you must provide the following information:
Name of the Active Directory container in which new distribution groups and contacts will be created. This must be provided in the following format:
OU=ContainerName, DC=DomainName, DC=TopLevelDomainName
Example
OU=SharePointContacts,DC=Contoso,DC=com
Name of the SMTP server to use for incoming e-mail (or accept the default SMTP server if one exists). This must be provided in the following format:
Server.subdomain.domain.top-level_domain
For example, SharePointServer.support.contoso.com
Whether to accept messages from only authenticated users.
Whether to allow users to create distribution groups from SharePoint sites. If you choose yes for this option, you can also choose whether users can do any combination of the following actions:
Create a new distribution group.
Change a distribution group’s e-mail address.
Change a distribution group’s title and description.
Delete a distribution group.
When configuring the SharePoint Directory Management service to create distribution groups and contacts using a remote SharePoint Directory Management service, you must provide the following information:
The URL of the remote directory management service, for example, http://server:adminport/_vti_bin/SharePointEmailWS.asmx.
The name of the SMTP server to use for incoming e-mail.
Whether to accept messages from only authenticated users.
Whether to allow users to create distribution groups from SharePoint sites.
-
Incoming e-mail server display address
Administrators can specify the e-mail server address that will be displayed in Web pages when users create an incoming e-mail address for a site, list, or group. This setting is often used in conjunction with the SharePoint Directory Management service to provide a more friendly e-mail server address for users to type, for example, mylist@example.com.
-
Safe e-mail server
You can configure SharePoint Foundation 2010 to accept e-mail from any e-mail server or only e-mail that has been routed through a safe-e-mail server application.
You can derive the following benefits by routing e-mail through a safe e-mail server:
User authentication: The SMTP service cannot authenticate users who send e-mail to your site, but Exchange Server can. The server administrator can use the SharePoint Central Administration Web site to specify that the system accept e-mail from authenticated users only if the e-mail is sent through Exchange Server.
Spam filtering:Exchange Server provides spam filtering to eliminate unsolicited commercial e-mail before it is forwarded to its destination — in this case, the server running SharePoint Foundation 2010. Another technique that can reduce spam is to allow members of the team site to archive e-mail only in lists on which you have granted write permissions to members.
Virus protection:Exchange Server provides virus protection for e-mail routed through it.
Note:
Because this option is only available in automatic mode, you cannot specify one or more safe e-mail servers and also specify an e-mail drop folder.
-
E-mail drop folder
If the SMTP service is running on another server than on the SharePoint server, you must specify the location from which SharePoint Foundation 2010 retrieves incoming e-mail. You specify the e-mail drop folder so that SharePoint Foundation 2010 knows from where to retrieve incoming e-mail. However, if you specify a specific e-mail drop folder, SharePoint Foundation 2010 cannot detect configuration changes on the remote e-mail server that is delivering the e-mail to your drop folder. This means that if an administrator configures the e-mail server to no longer deliver e-mail to this folder, SharePoint Foundation 2010 cannot detect that the configuration has changed, and therefore will not be able to retrieve the files from the new location.
Note:
When incoming e-mail is set to advanced mode, you must ensure that you have the proper permissions on the e-mail drop folder. For more information, see Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx).
Note:
Because this option is only available in advanced mode, you cannot specify an e-mail drop folder and also specify one or more safe e-mail servers.
-
-
Configuration options and settings modes
As a farm administrator, you have two settings modes from which to choose when enabling incoming e-mail: automatic and advanced. As described in the “Using a basic scenario” section, you can choose the automatic settings mode with default settings. However, the automatic settings mode has additional options that you can choose.
The following table describes the configuration options and whether they are configured on the Configure Incoming E-Mail Settings page in Central Administration by using the automatic settings mode or the advanced settings mode.
Configuration option
Automatic settings mode
Advanced settings mode
Safe e-mail servers
Yes
No
E-mail drop folder
No
Yes
SharePoint Directory management service
Yes
Yes
Incoming e-mail server display address
Yes
Yes
The advanced and automatic settings modes are similar in that they both enable farm administrators to configure the SharePoint Directory Management service and the e-mail server address to display in Web pages. These settings modes differ in that the automatic settings mode replaces the ability to choose what e-mail servers to accept e-mail from with the ability to specify the folder to which e-mail is dropped. SharePoint Foundation 2010 uses this e-mail drop folder to detect new e-mail messages.
Note:
The e-mail drop folder setting is not available in automatic mode, because that mode automatically sets the e-mail drop folder to the folder that is specified by the SMTP service.
-
Plan incoming e-mail worksheet
Download a Word version of the Plan incoming e-mail worksheet (http://go.microsoft.com/fwlink/?LinkId=200542). Use this worksheet to plan incoming e-mail in order to enable SharePoint sites to receive and store e-mail messages and attachments in lists and libraries.
Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx)
Plan outgoing e-mail (SharePoint Foundation 2010)
Configure outgoing e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ebb924d4-b9a2-4e40-bcb3-0ee582cc5a21(Office.14).aspx)
-
Plan outgoing e-mail (SharePoint Foundation 2010)
Outgoing e-mail is the foundation on which site administrators can implement several e-mail notification features. These features help end users track changes and updates to individual site collections and allow site administrators to deliver status messages.
This article helps site administrators understand both the uses for integrating outgoing e-mail and the requirements for integrating it into their site collections.
In this article:
-
About outgoing e-mail
Properly configuring outgoing e-mail is a requirement for implementing e-mail alerts and notifications. The outgoing e-mail feature uses an outbound Simple Mail Transfer Protocol (SMTP) service to relay e-mail alerts and notifications. These e-mail features include the following:
Alerts
In a large and growing site collection, users need an efficient way to keep up with updates to lists, libraries, and discussions. Setting up alerts provides an effective means to stay on top of changes. For example, if many users work on the same document, the owner of the document can set up alerts to be notified whenever there are changes to this document. Users can specify which areas of the site collection or which documents they want to track and decide how often they want to receive alerts.
Note:
Users must have at least View permissions to set up alerts.
Administrative messages
Site administrators might want to receive notices when users request access to a site or when site owners have exceeded their specified storage space. Setting up outgoing e-mail enables site administrators to receive automatic notifications for site administration issues.
Outgoing e-mail support can be enabled at both the server farm level (available in the System Settings section of the Central Administration Web site) and at the Web application level (available in the Application Management section of the Central Administration Web site). Therefore, you can specify different settings for a specific Web application. Outgoing e-mail settings at the Web application level override those set up at the server farm level.
-
Key planning phases of outgoing e-mail
Before you configure outgoing e-mail, you must have an SMTP service to relay e-mail alerts and notifications.
The outgoing e-mail settings include several components that must be considered when planning for this feature:
An SMTP service to relay e-mail alerts and notifications. You will need the DNS name or IP address of the SMTP mail server to use.
An address to use in the header of an alert message that identifies the sender of the message.
A Reply-to address that is displayed in the To field of a message when a user replies to an alert or notification.
A character set to use in the body of alert messages.
-
Outbound SMPT server
The SMTP service is a component of Internet Information Services (IIS); however, it is not enabled by default with IIS. It can be enabled by using Add or Remove Programs in Control Panel.
After determining which SMTP server to use, the SMTP server must be configured to allow anonymous access and to allow e-mail messages to be relayed. Additionally, the SMTP server must have Internet access if you want the ability to send messages to external e-mail addresses.
For more information about installing, configuring, and managing the SMTP service, see Help for Internet Information Services (IIS) Manager (http://go.microsoft.com/fwlink/?LinkId=72343).
Note:
Only a member of the Farm Administrators group can configure an SMTP server. The user must also be a member of the local Administrators group on the server.
-
From and Reply-to addresses
When configuring outgoing e-mail, you can configure the following two addresses:
From address
Alerts and notifications are sent from an administrative account on the server farm. This account is probably not the one you want to be displayed in the From field of an e-mail message. The address that you use does not need to correspond to an actual e-mail account; it can be a simple friendly address that is recognizable to an end user. For example, “Site administrator” might be an appropriate From address.
Reply-to address
This is the address that will be displayed in the To field of a message if a user replies to an alert or notification. The Reply-to address should also be a monitored account to ensure that end users receive prompt feedback for issues they might have. For example, a help desk alias might be an appropriate Reply-to address.
-
Character set
When you configure outgoing e-mail, you will need to specify the character set to use in the body of e-mail messages. A character set is a mapping of characters to their identifying code values. The default character set for outgoing e-mail is Unicode UTF-8, which allows most combination of characters (including bidirectional text) to co-exist in a single document. In most cases, the default setting of UTF-8 works well, although East Asian languages are best rendered with their own character set.
Be aware that if you select a specific language code, the text is less likely to appear correctly in mail readers configured for other languages.
Configure outgoing e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ebb924d4-b9a2-4e40-bcb3-0ee582cc5a21(Office.14).aspx)
-
-
Server farm and environment planning (SharePoint Foundation 2010)
This section describes how to plan server farms and environments.
In this section:
System requirements (SharePoint Foundation 2010)
Services architecture planning (SharePoint Foundation 2010)
Plan authentication (SharePoint Foundation 2010)
Plan security hardening (SharePoint Foundation 2010)
Plan automatic password change (SharePoint Foundation 2010)
Plan for host-named site collections (SharePoint Foundation 2010)
SQL Server and storage (SharePoint Foundation 2010)
Plan for business continuity management (SharePoint Foundation 2010)
Virtualization planning (SharePoint Foundation 2010)
Performance and capacity test results and recommendations (SharePoint Foundation 2010)
-
System requirements (SharePoint Foundation 2010)
Before you install Microsoft SharePoint Foundation 2010, you must ensure that you have installed all required hardware and software. To effectively plan your deployment, you must understand the level of support provided for the Web browsers that you will be using in your environment and how support for IP versions 4 and 6 is implemented in SharePoint Foundation 2010. You must also understand the URL and path length restrictions in SharePoint Foundation 2010.
The articles in this section help you prepare for the installation of SharePoint Foundation 2010 by providing information about the prerequisites that you need to run SharePoint Foundation 2010.
Hardware and software requirements (SharePoint Foundation 2010)
This article describes the hardware and software requirements that you must meet to successfully install SharePoint Foundation 2010.
Plan browser support (SharePoint Foundation 2010)
This article describes levels of support for Web browsers to use with SharePoint Foundation 2010.
URL path length restrictions (SharePoint Foundation 2010)
This article discusses the specific URL path length and character restrictions in SharePoint Foundation 2010, Internet Explorer 7, and Internet Explorer 8 that you should be aware of when planning sites, navigation, and structure.
IP support (SharePoint Foundation 2010)
This article describes SharePoint Foundation 2010 support for IP version 4 (IPv4) and IP version 6 (IPv6).
-
Hardware and software requirements (SharePoint Foundation 2010)
This article lists the minimum hardware and software requirements to install and run Microsoft SharePoint Foundation 2010.
Important:
If you contact Microsoft technical support about a production system that does not meet the minimum hardware specifications described in this document, support will be limited until the system is upgraded to the minimum requirements.
In this article:
Hardware requirements—Web servers, application servers, and single server installations
-
Overview
Microsoft SharePoint Foundation 2010 provides for a number of installation scenarios. Currently, these installations include single server with built-in database installations and single-server or multiple-server farm installations.
-
Hardware requirements—Web servers, application servers, and single server installations
The requirements in the following table apply both to installations on a single server with a built-in database and to servers running SharePoint Foundation 2010 in a multiple server farm installation.
Component
Minimum requirement
Processor
64-bit, four cores
RAM
4 GB for developer or evaluation use
8 GB for production use in a single server or multiple server farm
Hard disk
80 GB for system drive
For production use, you need additional free disk space for day-to-day operations. Maintain twice as much free space as you have RAM for production environments. For more information, see Capacity management and sizing for SharePoint Server 2010 (http://technet.microsoft.com/library/031b0634-bf99-4c23-8ebf-9d58b6a8e6ce(Office.14).aspx).
-
Hardware requirements—Database servers
The requirements in the following table apply to database servers in production environments with multiple servers in the farm.
Note:
Our definitions of small and medium deployments are those described in the “Reference Architectures” section in Capacity management and sizing for SharePoint Server 2010 (http://technet.microsoft.com/library/031b0634-bf99-4c23-8ebf-9d58b6a8e6ce(Office.14).aspx).
Component
Minimum requirement
Processor
64-bit, four cores for small deployments
64-bit, eight cores for medium deployments
RAM
8 GB for small deployments
16 GB for medium deployments
For large deployments, see the “Estimate memory requirements” section in Storage and SQL Server capacity planning and configuration (SharePoint Server 2010) (http://technet.microsoft.com/library/a96075c6-d315-40a8-a739-49b91c61978f(Office.14).aspx).
Note:
These values are higher than those recommended as the minimum values for SQL Server because of the distribution of data required for a SharePoint Products 2010 environment. For more information about SQL Server system requirements, see Hardware and Software Requirements for Installing SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=129377).
Hard disk
80 GB for system drive
Hard disk space is dependent on the size of your SharePoint content. For information about estimating the size of content and other databases for your deployment, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2010) (http://technet.microsoft.com/library/a96075c6-d315-40a8-a739-49b91c61978f(Office.14).aspx).
-
Software requirements
The requirements in the following tables apply to single server with built-in database installations and server farm installations that include a single server and multiple servers in the farm.
Important:
SharePoint Foundation 2010 does not support single label domain names. For more information, see Information about configuring Windows for domains with single-label DNS names (http://support.microsoft.com/kb/300684).
The Microsoft SharePoint Products Preparation Tool — which you access from the SharePoint Foundation 2010 Start page — can assist you in the installation of the software prerequisites for SharePoint Foundation 2010. Ensure that you have an Internet connection, because some of these prerequisites are installed from the Internet. For more information, see Deploy a single server with SQL Server (SharePoint Foundation 2010) (http://technet.microsoft.com/library/58d28a34-7a84-4564-a4cb-0e6b5425f67e(Office.14).aspx), Deploy a single server with a built-in database (SharePoint Foundation 2010) (http://technet.microsoft.com/library/6181fe5b-90ca-40cf-aade-abd59cf3c907(Office.14).aspx), and Multiple servers for a three-tier farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a(Office.14).aspx).
-
Minimum requirements
Environment
Minimum requirement
Database server in a farm
One of the following:
The 64-bit edition of Microsoft SQL Server 2008 R2.
The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2. From the Cumulative update package 2 for SQL Server 2008 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=165962) page, click the View and request hotfix downloads link and follow the instructions. On the Hotfix Request page, download the SQL_Server_2008_SP1_Cumulative_Update_2 file. When you install Microsoft SQL Server 2008 SP1 on Windows Server 2008 R2, you might receive a compatibility warning. You can disregard this warning and continue with your installation.
Note:
We do not recommend that you use CU3 or CU4, but instead CU2, CU5, or a later CU than CU5. For more information, see Cumulative update package 5 for SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=196928). Download the SQL_Server_2008_RTM_CU5_SNAC file.
The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3). From the Cumulative update package 3 for SQL Server 2005 Service Pack 3 (http://go.microsoft.com/fwlink/?LinkId=165748) page, click the View and request hotfix downloads link and follow the instructions. On the Hotfix Request page, download the SQL_Server_2005_SP3_Cumulative_Update_3 file.
For more information about choosing a version of SQL Server, see SQL Server 2008 R2 and SharePoint 2010 Products: Better Together (white paper) (SharePoint Server 2010) (http://technet.microsoft.com/library/665876e1-2706-42ad-bd76-8e4d1da0ce92(Office.14).aspx).
Single server with built-in database
The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2, or the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server. If you are running Windows Server 2008 without SP2, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 automatically.
Note:
You must download an update for Windows Server 2008 and Windows Server 2008 R2 before you run Setup. The update is a hotfix for the .NET Framework 3.5 SP1 that is installed by the Preparation tool. It provides a method to support token authentication without transport security or message encryption in WCF. For more information and links, see the “Access to Applicable Software” section later in this article.
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577).
For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/?LinkId=192578).
The preparation tool installs the following prerequisites:
Web Server (IIS) role
Application Server role
Microsoft .NET Framework version 3.5 SP1
SQL Server 2008 Express with SP1
Microsoft Sync Framework Runtime v1.0 (x64)
Microsoft Filter Pack 2.0
Microsoft Chart Controls for the Microsoft .NET Framework 3.5
Windows PowerShell 2.0
SQL Server 2008 Native Client
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
ADO.NET Data Services Update for .NET Framework 3.5 SP1
A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
Windows Identity Foundation (WIF)
Note:
If you have Microsoft “Geneva” Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF).
Front-end Web servers and application servers in a farm
The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2, or the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server. If you are running Windows Server 2008 with SP1, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 automatically.
Note:
You must download an update for Windows Server 2008 and Windows Server 2008 R2 before you run Setup. The update is a hotfix for the .NET Framework 3.5 SP1 that is installed by the Preparation tool. It provides a method to support token authentication without transport security or message encryption in WCF. For more information and links, see the “Access to Applicable Software” section.
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577)
For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/?LinkId=192578).
The preparation tool installs the following prerequisites:
Web Server (IIS) role
Application Server role
Microsoft .NET Framework version 3.5 SP1
Microsoft Sync Framework Runtime v1.0 (x64)
Microsoft Filter Pack 2.0
Microsoft Chart Controls for the Microsoft .NET Framework 3.5
Windows PowerShell 2.0
SQL Server 2008 Native Client
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
ADO.NET Data Services Update for .NET Framework 3.5 SP1
A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
Windows Identity Foundation (WIF)
Note:
If you have Microsoft “Geneva” Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF).
Client computer
A supported browser. For more information, see Plan browser support (SharePoint Foundation 2010).
-
Optional software
Environment
Optional software
Single server with built-in database
Windows 7 or Windows Vista. For more information, see Setting Up the Development Environment for SharePoint Server (http://go.microsoft.com/fwlink/?LinkID=164557).
Client computer
Microsoft Office 2010 client. For more information, see Microsoft Office 2010 (http://go.microsoft.com/fwlink/?LinkId=195843).
Microsoft Silverlight 3.
-
-
Access to applicable software
To install Windows Server 2008 or Microsoft SQL Server, you can go to the Web sites listed in this section. You can install all other software prerequisites through the SharePoint Foundation Start page. Most of the software prerequisites are also available from Web sites listed in this section. The Web Server (IIS) role and the Application Server role can be enabled manually in Server Manager.
In scenarios where installing prerequisites directly from the Internet is not possible or not feasible, you can install the prerequisites from a network share. For more information, see Install prerequisites from a network share (SharePoint Foundation 2010) (http://technet.microsoft.com/library/3fdf5e00-dffa-46bb-a6b8-abaf66aa583f(Office.14).aspx).
SharePoint Foundation 2010 (http://go.microsoft.com/fwlink/?LinkId=197422)
Language Packs for SharePoint Foundation 2010 (http://go.microsoft.com/fwlink/?LinkId=197424)
Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=197426)
Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=197428)
SQL Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=197429)
SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkID=179611)
SQL Server 2005 (http://go.microsoft.com/fwlink/?LinkId=197431)
Microsoft SQL Server 2008 SP1 (http://go.microsoft.com/fwlink/?LinkId=166490)
Cumulative update package 2 for SQL Server 2008 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=165962)
Cumulative update package 5 for SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=197434). Download the SQL_Server_2008_RTM_CU5_SNAC file.
Microsoft SQL Server 2005 SP3 (http://go.microsoft.com/fwlink/?LinkId=166496)
Cumulative update package 3 for SQL Server 2005 Service Pack 3 (http://go.microsoft.com/fwlink/?LinkId=165748)
Microsoft Windows Server 2008 SP2 (http://go.microsoft.com/fwlink/?LinkId=166500)
Windows Server 2008 with SP 2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=160770)
Windows Server 2008 R2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=166231)
Microsoft .NET Framework 3.5 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=131037)
Microsoft SQL Server 2008 Express Edition Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=166503)
Windows Identity Foundation for Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkID=160381)
Windows Identity Foundation for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=166363)
Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/?LinkID=141237)
Microsoft Office 2010 Filter Packs (http://go.microsoft.com/fwlink/?LinkId=191851)
Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://go.microsoft.com/fwlink/?LinkID=141512)
Windows PowerShell 2.0 (http://go.microsoft.com/fwlink/?LinkId=161023)
Microsoft SQL Server 2008 Native Client (http://go.microsoft.com/fwlink/?LinkId=166505)
Microsoft SQL Server 2008 Analysis Services ADOMD.NET (http://go.microsoft.com/fwlink/?linkid=160390)
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577)
For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163519) for Windows Server 2008 SP2
ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163524) for Windows Server 2008 R2 or Windows 7
Microsoft Silverlight 3 (http://go.microsoft.com/fwlink/?LinkId=166506)
Microsoft Office 2010 (http://go.microsoft.com/fwlink/?LinkID=195843)
Office Communicator 2007 R2 (http://go.microsoft.com/fwlink/?LinkId=196930)
Microsoft SharePoint Designer 2010 (32-bit) (http://go.microsoft.com/fwlink/?LinkId=196931)
Microsoft SharePoint Designer 2010 (64-bit) (http://go.microsoft.com/fwlink/?LinkId=196932)
Microsoft SQL Server 2008 SP1 (http://go.microsoft.com/fwlink/?LinkId=166490)
Cumulative update package 2 for SQL Server 2008 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=165962).
Microsoft SQL Server 2005 SP3 (http://go.microsoft.com/fwlink/?LinkId=166496)
Cumulative update package 3 for SQL Server 2005 Service Pack 3 (http://go.microsoft.com/fwlink/?LinkId=165748).
Microsoft Windows Server 2008 SP2 (http://go.microsoft.com/fwlink/?LinkId=166500)
Windows Server 2008 with SP 2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=160770).
Windows Server 2008 R2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=166231).
Microsoft .NET Framework 3.5 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=131037)
Microsoft SQL Server 2008 Express Edition Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=166503)
Windows Identity Framework for Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkID=160381)
Windows Identity Framework for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=166363)
Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/?LinkID=141237&clcid=0x409)
Microsoft Office 2010 Filter Packs (http://go.microsoft.com/fwlink/?LinkId=191851)
Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://go.microsoft.com/fwlink/?LinkID=141512)
Windows PowerShell 2.0 (http://go.microsoft.com/fwlink/?LinkId=161023)
Microsoft SQL Server 2008 Native Client (http://go.microsoft.com/fwlink/?LinkId=166505)
Microsoft SQL Server 2008 Analysis Services ADOMD.NET (http://go.microsoft.com/fwlink/?LinkId=130651)
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577)
For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/?LinkId=192578).
Microsoft Office 2010 (http://go.microsoft.com/fwlink/?LinkID=195843)
Microsoft Silverlight 3 (http://go.microsoft.com/fwlink/?LinkId=166506)
ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163519) for Windows Server 2008 SP2
ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163524) for Windows Server 2008 R2 or Windows 7
-
Plan browser support (SharePoint Foundation 2010)
Microsoft SharePoint Foundation 2010 supports several commonly used Web browsers. This article describes different levels of Web browser support, and it explains how ActiveX controls affect features.
In this article:
About planning browser support
-
About planning browser support
SharePoint Foundation 2010 supports several commonly used Web browsers. However, certain Web browsers might cause some SharePoint Foundation 2010 functionality to be downgraded, limited, or available only through alternative steps. In some cases, functionality might be unavailable for noncritical administrative tasks.
As part of planning your deployment of SharePoint Foundation 2010, we recommend that you review the browsers used in your organization to ensure optimal performance with SharePoint Foundation 2010.
-
Key planning phase of browser support
Browser support is an important part of your SharePoint Foundation 2010 implementation. Before you install SharePoint Foundation 2010, ensure that you know which browsers SharePoint Foundation 2010 supports. The information in this topic covers the following areas:
Browser support levels
Browser support matrix
Browser details
-
Browser support levels
Browser support for SharePoint Foundation 2010 can be divided into three different levels, as follows:
Supported
A supported Web browser is a Web browser that is supported to work with SharePoint Foundation 2010, and all features and functionality work. If you encounter any issues, support can help you to resolve these issues.
Supported with known limitations
A supported Web browser with known limitations is a Web browser that is supported to work with SharePoint Foundation 2010, although there are some known limitations. Most features and functionality work, but if there is a feature or functionality that does not work or is disabled by design, documentation on how to resolve these issues is readily available.
Not tested
A Web browser that is not tested means that its compatibility with SharePoint Foundation 2010 is untested, and there may be issues with using the particular Web browser. SharePoint Foundation 2010 works best with up-to-date, standards-based Web browsers.
-
Browser support matrix
The following table summarizes the support levels of commonly used browsers.
Browser
Supported
Supported with limitations
Not tested
Internet Explorer 8 (32-bit)
X
Internet Explorer 7 (32-bit)
X
Internet Explorer 8 (64-bit)
X
Internet Explorer 7 (64-bit)
X
Internet Explorer 6 (32-bit)
X
Mozilla Firefox 3.6 (on Windows operating systems)
X
Mozilla Firefox 3.6 (on non-Windows operating systems)
X
Safari 4.04 (on non-Windows operating systems)
X
-
Browser details
You should review the details of the Web browser that you have or plan to use in your organization to ensure that the Web browser works with SharePoint Foundation 2010 and according to your business needs.
Internet Explorer 8 (32-bit)
Internet Explorer 8 (32-bit) is supported on the following operating systems:
Windows Server 2008 R2
Windows Server 2008
Windows Server 2003
Windows 7
Windows Vista
Windows XP
Known limitations
There are no known limitations for Internet Explorer 8 (32-bit).
Internet Explorer 7 (32-bit)
Internet Explorer 7 (32-bit) is supported on the following operating systems:
Windows Server 2008
Windows Server 2003
Windows Vista
Windows XP
Known limitations
There are no known limitations for Internet Explorer 7 (32-bit).
Internet Explorer 6 (32-bit)
SharePoint Foundation 2010 does not support Internet Explorer 6 (32-bit).
Internet Explorer 8 (64-bit)
Internet Explorer 8.0 (64-bit) is supported on the following operating systems:
Windows Server 2008 R2
Windows Server 2008
Windows Server 2003
Windows 7
Windows Vista
Windows XP
Known limitations
The following table lists features and their know limitations in Internet Explorer 8 (64-bit).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Works with an ActiveX control and the stssync:// protocol. Therefore, functionality may be limited without an ActiveX control, such as the one that is included in Microsoft Office 2010. The feature also requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Edit in Microsoft Office application
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views and these may not work.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. If Microsoft Excel is not installed, and if no other application is configured to open this file, then this feature will not work.
File upload and copy
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft InfoPath 2010 integration
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft PowerPoint 2010 Picture Library integration
Requires a 64-bit ActiveX control, such as the one that is delivered in Microsoft Office 2010. The user can use the following workarounds when no control has been installed:
If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
New Document
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Send To
Can leverage a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Spreadsheet and Database integration
Require a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. The user can use the following workarounds when no control has been installed:
If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
Internet Explorer 7 (64-bit)
Internet Explorer 7 (64-bit) is supported on the following operating systems:
Windows Server 2008
Windows Server 2003
Windows Vista
Windows XP
Known limitations
The following table lists features and their know limitations in Internet Explorer 7 (64-bit).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Works with an ActiveX control and the stssync:// protocol. Therefore, functionality may be limited without an ActiveX control, such as the one that is included in Microsoft Office 2010. This feature requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Edit in Microsoft Office application
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. If Microsoft Excel is not installed, and if no other application is configured to open this file, then this feature will not work.
File upload and copy
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft InfoPath 2010 integration
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft PowerPoint 2010 Picture Library integration
Requires a 64-bit ActiveX control, such as the one that is delivered in Microsoft Office 2010. The user can use the following workarounds when no control has been installed:
If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
New Document
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Send To
Can leverage a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Spreadsheet and Database integration
Require a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. The user can use the following workarounds when no control has been installed:
If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
Mozilla Firefox 3.6 (on Windows operating systems)
Mozilla Firefox 3.6 is supported on the following operating systems:
Windows Server 2008 R2
Windows Server 2008
Windows Server 2003
Windows 7
Windows Vista
Windows XP
Known limitations
The following table lists features and their know limitations in Mozilla Firefox 3.6 (on Windows operating systems).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Works with an ActiveX control, but requires a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. The feature also requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Drag and Drop Web Parts
Cannot be moved by using drag and drop on Web Part pages. Users must click Edit on the Web Part, select Modify Web Part, and then select the zone from the Layout section of the Web Part properties page. Web Parts can be moved using drag and drop on Pages.
Edit in Microsoft Office application
Requires an ActiveX control, such as the one that is delivered in SharePoint Foundation 2010, and a Firefox control adaptor. For more information about Microsoft Office 2010 Firefox Plug-in, see FFWinPlugin Plug-in (http://go.microsoft.com/fwlink/?LinkId=199867). If you install and configure the Office Web Applications on the server, the Edit functionality works and you can modify Office documents in your browser. This functionality only works with Microsoft Office 2010 or an equivalent product together with a Firefox plug-in.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views, and these may not work. Explorer view requires Internet Explorer.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. If Microsoft Excel is not installed, and if no other application is configured to open this file, then this feature will not work.
File upload and copy
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Microsoft InfoPath 2010 integration
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Microsoft PowerPoint 2010 Picture Library integration
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. The user can use the following workarounds when no control has been installed:
If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires an ActiveX control, such as the one delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
New Document
Requires an ActiveX control, such as the one delivered in Microsoft Office 2010, and a Firefox control adaptor. For more information about Microsoft Office 2010 Firefox Plug-in, see FFWinPlugin Plug-in (http://go.microsoft.com/fwlink/?LinkId=199867). Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Rich Text Editor – Basic Toolbar
A user can update the Rich Text Editor basic toolbar to a Full Rich Text Editor that includes the ribbon by changing the field’s properties, as follows: On the FldEdit.aspx, in the List Settings menu, select Specific Field Settings. Next, under Columns, click Description. In the Additional Columns Settings section, under Specify the type of text to allow, select Enhanced rich text (Rich text with pictures, tables, and hyperlinks).
Send To
Can leverage an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Spreadsheet and Database integration
Require ActiveX controls, such as those that are delivered in Microsoft Office 2010, and Firefox control adaptors. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. The user can use the following workarounds when no control has been installed:
If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
Mozilla FireFox 3.6 (on non-Windows operating systems)
Mozilla FireFox 3.6 is supported on the following operating systems:
Mac OSX
UNIX/Linux
Known limitations
The following table lists features and their know limitations in Mozilla FireFox 3.6 (on non-Windows operating systems).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires an ActiveX control that is not supported on this platform. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Drag and Drop Web Parts
Cannot be moved by using drag and drop on Web Part pages. Users must click Edit on the Web Part, select Modify Web Part, and then select the zone from the Layout section of the Web Part properties page. Web Parts can be moved using drag and drop on Pages.
Edit in Microsoft Office application
Requires an ActiveX control that is not supported on this platform. If you install and configure the Office Web Applications on the server, the Edit functionality works and you can modify Office documents in your browser.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views, and these may not work. Explorer view requires Internet Explorer.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. Requires an application that is configured to open this file.
File upload and copy
Requires an ActiveX control that is not support on this platform.
Microsoft InfoPath 2010 integration
Requires an ActiveX control that is not support on this platform.
Microsoft PowerPoint 2010 Picture Library integration
Requires an ActiveX control that is not supported on this platform. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. The user can use the following workarounds when no control has been installed:
If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires an ActiveX control that is not supported on this platform.
New Document
Requires an ActiveX control that is not supported on this platform. Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Rich Text Editor – Basic Toolbar
A user can update the Rich Text Editor basic toolbar to a Full Rich Text Editor that includes the ribbon by changing the field’s properties, as follows: On the FldEdit.aspx, in the List Settings menu, select Specific Field Settings. Next, under Columns, click Description. In the Additional Columns Settings section, under Specify the type of text to allow, select Enhanced rich text (Rich text with pictures, tables, and hyperlinks).
Send To
Can leverage an ActiveX control that is not supported on this platform. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires an ActiveX control that is not supported on this platform.
Spreadsheet and Database integration
Require ActiveX controls that is not supported on this platform. The user can use the following workarounds when no control has been installed:
If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
Note:
FireFox browsers on UNIX/Linux systems may not work with the Web Part menu.
Note:
Some ActiveX features, such as list Datasheet view and the control that displays user presence information, do not work in Mozilla Firefox 3.6. Firefox users can use the Microsoft Office 2010 Firefox Plug-in to launch documents.
Safari 4.04 (on non-Windows operating systems)
Safari 4.0.4 is supported on the following operating systems:
Mac OSX (Version 10.6, Snow Leopard)
Known limitations
The following table lists features and their know limitations in Safari 4.04 (on non-Windows operating systems).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires an ActiveX control that is not supported on this platform.
Drag and Drop Web Parts
Cannot be moved by using drag and drop on Web Part pages. Users must click Edit on the Web Part, select Modify Web Part, and then select the zone from the Layout section of the Web Part properties page. Web Parts can be moved using drag and drop on Pages.
Edit in Microsoft Office application
Requires an ActiveX control that is not supported on this platform. If you install and configure the Office Web Applications on the server, the Edit functionality works and you can modify Office documents in your browser.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views. Explorer view requires Internet Explorer.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. Requires an application that is configured to open this file.
File upload and copy
Requires an ActiveX control that is not supported on this platform.
Microsoft InfoPath 2010 integration
Requires an ActiveX control that is not supported on this platform.
Microsoft PowerPoint 2010 Picture Library integration
Requires an ActiveX control that is not supported on this platform. The user can use the following workarounds when no control has been installed:
If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires an ActiveX control that is not supported on this platform.
New Document
Requires an ActiveX control that is not supported on this platform. Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Rich Text Editor – Basic Toolbar
A user can update the Rich Text Editor basic toolbar to a Full Rich Text Editor that includes the ribbon by changing the field’s properties, as follows: On the FldEdit.aspx, in the List Settings menu, select Specific Field Settings. Next, under Columns, click Description. In the Additional Columns Settings section, under Specify the type of text to allow, select Enhanced rich text (Rich text with pictures, tables, and hyperlinks).
Send To
Can leverage an ActiveX control that is not supported on this platform. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires an ActiveX control that is not supported on this platform.
Spreadsheet and Database integration
Require ActiveX controls that are not supported on this platform. The user can use the following workarounds when no control has been installed:
If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
-
-
ActiveX controls
Some of the features in SharePoint Foundation 2010 use ActiveX controls. In secure environments, these controls must be able to work on the client computer before their features will function. Some ActiveX controls, such as those included in Microsoft Office 2010, does not work with 64-bit browser versions. For Microsoft Office 2010 (64-bit), only the following control works with 64-bit browsers:
name.dll – Presence information
-
URL path length restrictions (SharePoint Foundation 2010)
This article discusses the specific URL path length and character restrictions in Microsoft SharePoint Foundation 2010, Internet Explorer 7, and Internet Explorer 8 that you should be aware of when planning sites, navigation, and structure. This article does not discuss URL length limitations in other browsers. For this information, see the browser documentation.
In this article:
-
Understanding URL and path lengths
This section discusses URL composition, how SharePoint Foundation 2010 builds URLs, how URLs are encoded and lengthened, and passed as parameters in other URLs.
-
SharePoint URL composition
The total length of a SharePoint URL equals the length of the folder or file path, including the protocol and server name and the folder or file name, plus any parameters that are included as part of the URL. The formula is as follows:
URL = protocol + server name + folder or file path + folder or file name+ parameters
For example, the following is a typical URL path to a file stored in SharePoint Foundation 2010:
http://www.contoso.com/sites/marketing/documents/Shared%20Documents/Promotion/Some%20File.xlsx
Where the parts of the URL path are as listed in the following table.
URL part
Example
Protocol
http://
Server name
www.contoso.com/
Folder or file path
sites/marketing/documents/Shared%20Documents/Promotion/
File name
Some%20File.xlsx
-
URL Encoding
URL encoding ensures that all browsers will correctly transmit text in URL strings. Characters such as a question marks (?), ampersands (&), slash marks (/), and spaces might be truncated or corrupted by some browsers. SharePoint Foundation 2010 adheres to the standards for URL encoding that are defined in The Internet Engineering Task Force (IETF) RFC 3986 (http://go.microsoft.com/fwlink/?LinkId=195564&clcid=0x409).
If you have non-standard ASCII characters, such as high-ASCII or double-byte Unicode characters, in the SharePoint URL, each of those characters is URL-encoded into two or more ASCII characters when they are passed to the Web browser. Thus, a URL with many high-ASCII characters or double-byte Unicode characters can become longer than the original un-encoded URL. The list below gives examples of the multiplication factors:
High-ASCII characters — for example, (!, “, #, $, %, &, [Space]): multiplication factor = 3
Double byte Unicode characters — for example, Japanese, Chinese, Korean, Hindi: multiplication factor = 9
For example, when you translate the names of sites, library, folder, and file in the URL path http://www.contoso.com/sites/marketing/documents/Shared%20Documents/Promotion/Some%20File.xlsx into Japanese, the resulted encoded URL path will become something like the following:
http://www.contoso.com/sites/%E3%83%9E%E3%83%BC%E3%82%B1%E3%83%86%E3%82%A3%E3%83%B3%E3%82%B0/%E6%96%87%E6%9B%B8/DocLib/%E3%83%97%E3%83%AD%E3%83%A2%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3/%E3%83%95%E3%82%A1%E3%82%A4%E3%83%AB.xlsx. This path is 224 characters, whereas the original URL path is only 94 characters.
Important:
The following characters cannot be used in an un-encoded URL: (~, #, %, &, *, {}, \, :, <>, /, +, |, “).
-
URL parameters
URL parameters are data that are included as part of the URL that are processed. These parameters are also URL-encoded and can be encoded multiple times, producing very long URLs.
For example, if you browse to a list, the URL might be something like the following: http://www.contoso.com/sites/marketing/documents/Shared%20Documents/Forms/AllItemA.aspx?RootFolder=%2Fsites%2Fmarketing%2Fdocuments%2FShared%20Documents%2FPFPromoti&FolderCTID=0x012000F2A09653197F4F4F919923797C42ADEC&View={CD527605-9A7A-448D-9A35-67A33EF9F766}. This URL is 260 characters.
If you then click Create View on the Library tab, the entire URL is included in the resulting URL as the source parameter and it is encoded to be much longer — for example, http://www.contoso.com/sites/marketing/documents/_layouts/ViewType.aspx?List=%7BED6E21E0%2DDF28%2D4165%2DBC3E%2D5371987CC2D2%7D&Source=http%3A%2F%2Fwww%2Econtoso%2Ecom%2Fsites%2Fmarketing%2Fdocuments%2FShared%2520Documents%2FForms%2FAllItems%2Easpx%3FRootFolder%3D%252Fsites%252Fmarketing%252Fdocuments%252FShared%2520Documents%252FPromotion%26FolderCTID%3D0x012000F2A09653197F4F4F919923797C42ADEC%26View%3D%7BCD527605%2D9A7A%2D448D%2D9A35%2D67A33EF9F766%7D. This URL is 457 characters.
Important
SharePoint Foundation 2010 truncates the URL source parameter if the total URL length to be passed to Internet Explorer is more than 1950 bytes. The source parameter is a reference to a previously visited page. The result of the truncation of the source parameter is that the user will be referred back to default location rather than the location specified in the source parameter.
Other parameters, such as sort orders, root folder parameters, and views are not truncated.
-
-
URL path length limitations
This section discusses the different URL length limitations in SharePoint Foundation 2010 and Internet Explorer, and how to plan for URL path lengths.
-
SharePoint URL path length limitations
The limitations In this section apply to the total length of the URL path to a folder or a file in SharePoint Foundation 2010 but not to the length of any parameters. Also, these limitations apply only to un-encoded URLs, not to encoded URLs. There is no limit to encoded URLs in SharePoint Foundation 2010. The limitations are the following:
260 Unicode (UTF-16) code units – the characters in a full file path, not including a domain/server name.
256 Unicode (UTF-16) code units – the characters in a full folder path, not including the file name and the domain/server name.
128 Unicode (UTF-16) code units – characters in a path component, that is, a file or folder name.
260 Unicode (UTF-16) code units – the characters in a full path, including a domain/server name for use with Office clients.
256 Unicode (UTF-16) code units – the characters in a full path including the domain/server name, for use with Active X controls.
For more information, see Microsoft Knowledge Base article 894630, You receive a “The specified file or folder name is too long” error message (http://go.microsoft.com/fwlink/?LinkId=195567&clcid=0x409).
Note:
Understanding code units – In most cases, one UTF-16 character equals one UTF-16 code unit. However, characters that use Unicode code points greater than U+10000 will equal two UTF-16 code units. These characters include, but are not limited to, Japanese or Chinese surrogate pair characters. If your paths include these characters, the URL length will exceed the URL length limitation with fewer than 256 or 260 characters.
-
Internet Explorer URL length limitations
Internet Explorer also has limitations that are separate from those in SharePoint Foundation 2010. Even though you make the SharePoint Foundation 2010 URL path shorter than the limitations, you might experience an Internet Explorer URL length limitation because of added parameters and encoding of the URL. You must use the most restrictive limitation as a guideline for planning URL lengths.
Both Internet Explorer 7 and Internet Explorer 8 have a maximum URL length of 2,083 UTF-8 characters and a maximum path length of 2,048 UTF-8 characters. However, in Internet Explorer 7, under certain circumstances, the effective URL length limitation is 1024 UTF-8 characters, not 2083 UTF-8 characters. For more information about the URL length limits in Internet Explorer, see Microsoft Knowledge Base article 208427, Maximum URL length is 2,083 characters in Internet Explorer (http://go.microsoft.com/fwlink/?LinkId=195568&clcid=0x409).
Important:
Unless all of the browsers in the environment are Internet Explorer 8, use the effective limit of 1024 UTF-8 characters.
-
-
Resolving URL length problems
There are several ways that you can resolve or mitigate URL length problems in the SharePoint Foundation 2010 environment. The following list provides suggestions:
Upgrade all the end-user browsers to Internet Explorer 8, which has a longer URL length limit.
Use shorter names for sites, folders, and documents and control the depth of the site and folder structures to reduce the lengths of URLs.
If possible or allowed, use ASCII names for sites, folders, and documents. This will avoid situations where the URL will be lengthened by being encoded.
To reduce the risk that the SharePoint Foundation 2010 end-users will encounter problems because of URL length limitations, we recommend that you apply the following effective limits in the deployment:
256 Unicode (UTF-16) Code units – the effective file path length limitation, including a domain/server name
128 Unicode (UTF-16) Code units – the path component length limitation
-
IP support (SharePoint Foundation 2010)
This article explains the support for Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6) addressing in Microsoft SharePoint 2010 Products.
SharePoint 2010 Products support the following environments:
Pure IPv4 environment
Mixed IPv4 and IPv6 environment
Pure IPv6 environment
In a SharePoint environment, “mixed” can be defined as one of the following likely scenarios:
Both IPv4 and IPv6 protocols are running in your environment.
Some of your client computers are using IPv4 and some of them are using IPv6.
Your client computers are using IPv4, but the computer running Microsoft SQL Server is using IPv6.
By default, the IPv6 protocol and the IPv4 protocol are both installed and enabled in Windows Server 2008 and Windows Server 2008 R2. When both IPv4 and IPv6 are enabled, IPv6 is given preference over IPv4. Additionally, you can remove the IPv4 protocol so that the computer runs IPv6 exclusively.
To determine what version is being used, you can use the IPConfig.exe tool. For additional information, see IPConfig (http://go.microsoft.com/fwlink/?LinkId=122336&clcid=0x409).
The following list shows other important considerations regarding IPv6:
For any computer that is authenticated by using a domain controller and is only running IPv6 within a SharePoint 2010 Products environment, the domain controller must be running Windows Server 2008 or Windows Server 2008 R2. Ensure that you use the correct service pack and any additional software prerequisites. For more information, see Hardware and software requirements (SharePoint Foundation 2010).
All versions of Microsoft SQL Server supported for SharePoint 2010 Products also support IPv6. For more information about IPv6 support for SQL Server 2008, see Connecting Using IPv6 (http://go.microsoft.com/fwlink/?LinkId=183115). For more information about IPv6 support for SQL Server 2005, see Connecting Using IPv6 (http://go.microsoft.com/fwlink/?LinkId=183118).
In SharePoint 2010 Products, when using IPv6 protocol, all end-user Uniform Resource Locators (URLs) must be based on DNS names with AAAA records. Browsing to SharePoint URLs that use IPv6 literal addresses is not supported. An example of a literal address URL is http://%5B2001:db8:85a3:8d3:1319:8a2e:370:7344%5D. However, SharePoint 2010 Products support entering IPv6 literal addresses for certain farm administration functionality, such as entering the server name when creating or attaching databases. For server names that use a literal address format, you must enclose the literal address within square brackets. For more information about AAAA records, see Adding a Resource Record to a Forward Lookup Zone (http://go.microsoft.com/fwlink/?LinkId=181956).
For additional information about IPv6, see Internet Protocol Version 6 (IPv6) (http://go.microsoft.com/fwlink/?LinkId=120794&clcid=0x409) and IP Addressing (http://go.microsoft.com/fwlink/?LinkId=120795&clcid=0x409).
-
See Also
Internet Protocol, Version 6 (IPv6) Specification (http://go.microsoft.com/fwlink/?LinkId=183119)
-
-
Logical architecture planning
This section contains articles to help you learn about and plan logical architectures for Microsoft SharePoint Foundation 2010.
In this section:
Services architecture planning (SharePoint Foundation 2010)
Plan for host-named site collections (SharePoint Foundation 2010)
-
Services architecture planning (SharePoint Foundation 2010)
This article describes the services architecture for sharing service applications and provides example architectures for Microsoft SharePoint Foundation 2010.
In this article:
Services infrastructure and design principles
The following poster-size models are also available to use with this article. You can modify the diagrams within the models to represent your own organization plans.
Services in Microsoft SharePoint 2010 Products
Visio (http://go.microsoft.com/fwlink/?LinkID=167090)
PDF (http://go.microsoft.com/fwlink/?LinkID=167092)
XPS (http://go.microsoft.com/fwlink/?LinkID=167091)
Cross-farm services in SharePoint 2010 Products
Visio (http://go.microsoft.com/fwlink/?LinkID=167093)
-
About service applications
SharePoint Foundation 2010 includes a set of services that can be shared across Web applications. These services are called service applications. Some service applications can be shared across farms. Sharing service applications across Web applications and farms greatly reduces the resources required to provide these services across multiple sites.
The following service applications are provided with SharePoint Foundation 2010:
Business Data Connectivity service — Gives access to line-of-business data systems.
Usage and Health Data Collection service — Collects farm wide usage and health data, and provides the ability to view various usage and health reports.
Microsoft SharePoint Foundation Subscription Settings Service — Provides multi-tenant functionality for service applications. Tracks subscription IDs and settings for services that are deployed in partitioned mode. Deployed through Windows PowerShell only.
Some service applications are provided by other Microsoft products, including Microsoft Office Web Apps. Office Web Apps are online companions to Microsoft Word, Excel, PowerPoint, and OneNote, enabling people to access and do light editing or sharing of Office documents from virtually anywhere. Business customers licensed for Microsoft Office 2010 through a Volume Licensing program can run Office Web Apps on-premises on a server running SharePoint Foundation 2010.
The services infrastructure is extensible, and third party companies can create additional service applications that can be used with SharePoint Foundation 2010.
Service applications are different from the services that are started and stopped on specific servers and listed on the Services on Server page in the SharePoint Central Administration Web site. Some of the services listed on this page are associated with service applications, but service applications represent specific instances of services that can be configured and shared in specific ways.
-
Services infrastructure and design principles
SharePoint 2010 Products improves the services infrastructure that was introduced in the previous version. In SharePoint 2010 Products, the infrastructure for hosting services moves into SharePoint Foundation 2010 and the configuration of service offerings is much more flexible. Individual services can be configured independently, and third-party companies can add services to the platform.
-
Deploying services
You deploy service applications within a farm by using one of the following methods:
Selecting services when you run the SharePoint Products Configuration Wizard.
Adding services one by one on the Manage Service Applications page in the Central Administration site.
Using Windows PowerShell.
-
More granular configuration of services
The service application infrastructure gives you more control over which services are deployed and how service applications are shared:
1. You can deploy only the service applications that are needed to a farm.
2. Web applications can be configured to use only the service applications that are needed, instead of all the services that have been deployed.
3. You can deploy multiple instances of the same service in a farm and assign unique names to the resulting service applications.
4. You can share service applications across multiple Web applications within the same farm.
You can choose the service applications for a Web application when you create the Web application. You can also modify the service applications that are associated with a Web application later.
-
Service application groups
By default, all service applications are included in a default group, unless you change this setting for a service application when it is created. You can add and remove service applications from the default group at any time.
The following diagram shows a typical deployment with all service applications contained in the default service group.

When you create a Web application, you can select the default group or you can create a custom group of service applications. You create a custom group of service applications by selecting only the service applications that you want the Web application to use.
Custom groups that are created in Central Administration are not reusable across multiple Web applications. Each time that you select custom when you create a Web application, you are selecting service applications only for the Web application that you are creating.
-
Logical architecture
Service applications are deployed within a single Internet Information Services (IIS) Web site. This is the default behavior and cannot be changed. However, you can customize the configuration of service application groups and the association of Web applications to service application groups.
The following diagram shows the logical architecture for a more complex deployment.

Notice the following characteristics of the farm in the diagram:
All service applications are contained within the same IIS Web site.
There are two groups of service applications: the default group and a custom group. Not all service applications have to be included in the default group. In the diagram, an additional instance of the Business Data Connectivity service is added to the farm but not included in the default group. It is used only by one Web application.
Web applications connect either to the default group or to a custom group of service applications. In the diagram, there is one custom group.
Service applications can be deployed to different application pools to achieve process isolation. However, if you want to optimize the performance of your farm, we recommend that you deploy service applications to one application pool.
To achieve physical isolation for a service application, choose or create a different application pool for the service application.
-
Connections for service applications
When you create a service application, a connection for the service application is created at the same time. A connection is a virtual entity that connects Web applications to service applications. In Windows PowerShell, these connections are called proxies. “Proxy” appears at the end of the type description for connections on the Manage Service Applications page in Central Administration.
-
Service application administration
Service applications are managed directly in Central Administration rather than through a separate administration site. If needed, service applications can be monitored and managed remotely. Service applications can also be managed and scripted by using Windows PowerShell.
-
-
Plan for host-named site collections (SharePoint Foundation 2010)
In this article:
About host-named site collections
Create a host-named site collection
Programmatically create a host-named site collection
Use managed paths with host-named site collections
Expose host-named sites over HTTP or SSL
Configure SSL for host-named site collections
Use host-named site collections with off-box SSL termination
Microsoft SharePoint Foundation 2010 supports both path-based and host-named site collections. The primary difference between path-based and host-named site collections is that all path-based site collections in a Web application share the same host name (DNS name), and each host-named site collection in a Web application is assigned a unique DNS name.
Path-based site collections provide a corporate hosting solution with all site collections sharing the same host name of the Web application. In a path-based deployment, you can have a single site collection at the root of the Web application and additional site collections under managed paths within the Web application.
Host-named site collections provide a scalable Web hosting solution with each site collection assigned to a unique DNS name. In a Web hosting deployment, each host-named site collection has its own vanity host name URL, such as http://customer1.contoso.com, http://customer2.contoso.com, or http://www.customer3.com.
SharePoint Foundation 2010 provides two significant improvements to host-named site collections: the ability to use managed paths with host-named site collections, and the ability to use off-box SSL termination with host-named site collections.
-
About host-named site collections
Web hosters provide customers with Web server space to host their own Web sites. In a path-based SharePoint Foundation 2010 environment, these sites would typically be assigned to http://www.contoso.com/sites/customer1, http://www.contoso.com/sites/customer2, and so on. However, Web hosting customers typically want to have their Web sites available at a vanity domain name, such as http://customer1.contoso.com, http://customer2.contoso.com, and so on.
One way to support this customer request is to provide each customer with their own Web application and assign the customer’s unique DNS name to the Web application. However, SharePoint Foundation 2010 Web applications do not scale as well as SharePoint Foundation 2010 site collections. SharePoint Foundation 2010 supports host-named site collections as an alternative to creating individual Web applications for each customer. Host-named site collections can scale to thousands of site collections because they can all exist within a single Web application and still offer vanity naming capability.
Because host-named site collections have a single URL, they do not support alternate access mappings and are always considered to be in the Default zone. If you need to support site collections responding to multiple host-name URLs, consider using path-based site collections with alternate access mappings instead of host-named site collections.There are several additional configuration options to consider when provisioning a new SharePoint Foundation 2010 site. Specifying the appropriate site template during site creation will determine which preconfigured Web parts and other user interface elements are available on the new site. In a hosting scenario, you will probably want to select either a team site template (value of “STS#0” when creating the site) or a blank site with no Web parts or prebuilt lists (value of “STS#1”). Also consider specifying site quotas on each newly provisioned site collection.
-
About host headers
Host headers refer to the portion of the HTTP protocol that tells the Web server the DNS name of the site that the client is connecting to. You can apply host headers at two different levels in SharePoint Foundation 2010:
The Web application (IIS Web site) level
The site collection level
It’s important to understand the distinction between these two levels. Host headers at the IIS Web site level are only intended for path-based site collections. Host headers at the site collection level are only intended for host-named site collections. In most cases, applying a host header binding at the IIS Web site level makes it impossible to access host-named site collections through the IIS Web site. This is because IIS will not respond to requests for host names that differ from the host header binding.
Path-based site collections and host-named site collections can co-exist in the same Web application and can exist in multiple Web applications. To ensure that both types of site collections are accessible to users, do not put host header bindings on the IIS Web site assigned to the Default zone of your Web application, if you have host-named site collections in that Web application. You can apply host header bindings to the IIS Web sites in the other zones of your Web application. This enables you to use the Default zone with host-named site collections while allowing you to use alternate access mapping functionality in the other zones for path-based site collections.
You can manually modify host header bindings on the IIS Web site from the IIS Manager, but this is not recommended. Any changes you make using the IIS Manager will not be recorded in SharePoint Foundation 2010. If SharePoint Foundation 2010 tries to provision an IIS Web site on another computer in the farm for the same Web application and zone, the original host header binding is used instead of the modified binding. If you want to modify an existing binding for an IIS Web site, remove the Web application from the zone and then re-extend the Web application into the zone with the binding you want to use.
-
Create a host-named site collection
You must use Windows PowerShell to create a host-named site collection. You cannot use the SharePoint Foundation 2010 Central Administration Web application to create a host-named site collection, but you can use Central Administration to manage the site collection after you have created it.
You can create a host-named site collection by using the Windows PowerShell New-SPSite cmdlet with the -HostHeaderWebApplication parameter, as shown in the following example:
1. To create a host-named site collection using Windows PowerShell, verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. From the Windows PowerShell command prompt (that is, PS C:\>), type the following:
New-SPSite http://host.header.site.url -OwnerAlias DOMAIN\username –
HostHeaderWebApplication http://servername
This creates a host-named site collection with the URL http://host.header.site.url in the SharePoint Foundation 2010 Web application with the URL http://servername.
-
Programmatically create a host-named site collection
In addition to using the Windows PowerShell to create host-named sites, you can use the SharePoint Foundation 2010 object model. The following code sample creates the host-named site collection with the URL http://host.header.site.url in the SharePoint Foundation 2010 Web application with the URL http://servername:
SPWebApplication webApp = SPWebApplication.Lookup(new
Uri(“http://www.contoso.com”));
SPSiteCollection sites = webApp.Sites;
SPSite Site = null;
Site = sites.Add(“http://hoster.contoso.com”, “Site_Title”,
“Site_Description”, 1033, “STS#0”, “contoso\owner”,
“Owner_Display_Name”, “Owner_Email”, “contoso\secondaryowner,
“Secondary_Owner_Display_Name”, “Secondary_Owner_Email”, true);
SharePoint Foundation 2010 ships with a set of Web services for various user and administrative tasks. One of these administrative tasks is creating a new site collection. The CreateSite Web service method does not support the creation of host-named site collections. A workaround for this issue is to write a Web service that wraps the API sample code.
-
Use managed paths with host-named site collections
SharePoint Foundation 2010 adds support for managed paths with host-named site collections. Hosters can provide multiple site collections to the same customer with each site collection sharing the customer’s unique host name but differentiated by the URL path after the host name.
Managed paths for host-named site collections are different from managed paths for path-based site collections. Managed paths for host-named site collections do not apply to path-based site collections; nor do managed paths for path-based site collections apply to host-named site collections. Managed paths created for host-named site collections are available to all host-named site collections within the farm regardless of which Web application the host-named site collection is in. You must create a root host-named site collection for a host name before you can create a managed path host-named site collection for that host name.
You can create a managed path for use with host-named site collections by using the Windows PowerShell New-SPManagedPath cmdlet with the -HostHeader parameter, as shown in the following example:
New-SPManagedPath pathname –HostHeader
A host-named site collection created at a managed path is shown in the following example:
New-SPSite http://host.header.site.url/pathname/sitename -OwnerAlias DOMAIN\username -HostHeaderWebApplication http://servername
-
Expose host-named sites over HTTP or SSL
Host-named site collections will use the same protocol scheme as the public URL in the Default zone of their Web application. If you wish to provide the host-named site collections in your Web application over HTTP, ensure that the public URL in the Default zone of your Web application is an HTTP-based URL. If you wish to provide host-named site collections in your Web application over SSL, ensure that the public URL in the Default zone of your Web application is an HTTPS-based URL.
Unlike an earlier version, SharePoint Foundation 2010 does not support a host-named site collection using both HTTP- and SSL-based URLs simultaneously. If some host-named site collections need to be available over HTTP while other host-named site collections need to be available over SSL, separate the host-named site collections into two different Web applications dedicated for that type of access. In this scenario, HTTP host-named site collections should be in a Web application dedicated for HTTP access and SSL host-named site collections should be in a Web application dedicated for SSL access.
-
Configure SSL for host-named site collections
In hosting scenarios, hosters can configure a single Web application with SSL and then create multiple host-named site collections within that Web application. To browse to a site over SSL, a server certificate has to be installed and assigned to the IIS Web site. Each host-named site collection in a Web application will share the single server certificate assigned to the IIS Web site.
Hosters need to acquire a wildcard certificate or subject alternate name certificate and then use a host-named site collection URL policy that matches that certificate. For example, if a hoster acquires a *.contoso.com wildcard certificate, the hoster has to generate host-named site collection URLs such as https://site1.contoso.com, https://site2.contoso.com, and so on, to enable these sites to pass browser SSL validation. However, if customers require unique second-level domain names for their sites, the hoster has to create multiple Web applications rather than multiple host-named site collections.
To configure SSL for host-named site collections, enable SSL when creating the Web application. This will create an IIS Web site with an SSL binding instead of an HTTP binding. After the Web application is created, open IIS Manager and assign a certificate to that SSL binding. You can then create site collections in that Web application.
-
Use host-named site collections with off-box SSL termination
Because SharePoint Foundation 2010 uses the public URL in the Default zone of the Web application to determine whether host-named site collections will be rendered as HTTP or SSL, you can now use host-named site collections with off-box SSL termination. There are 3 requirements to use SSL termination with host-named site collections:
The public URL in the Default zone of the Web application must be an HTTPS-based URL.
The SSL terminator or reverse proxy must preserve the original HTTP host header from the client.
If the client SSL request is sent to the default SSL port (443), then the SSL terminator or reverse proxy must forward the decrypted HTTP request to the front-end Web server on the default HTTP port (80). If the client SSL request is sent to a non-default SSL port, then the SSL terminator or reverse proxy must forward the decrypted HTTP request to the front-end Web server on the same non-default port.
To use host-named site collections with off-box SSL termination, configure your Web application as you normally would for SSL termination and ensure that it meets the requirements described above. In this scenario, SharePoint Foundation 2010 will render links of its host-named site collections in that Web application using HTTPS instead of HTTP.
-
Plan authentication (SharePoint Foundation 2010)
This section describes how to plan for authentication.
In this section:
-
Plan authentication methods (SharePoint Foundation 2010)
This article describes the authentication methods and authentication modes that are supported by Microsoft SharePoint Foundation 2010. Authentication is the process of validating a user’s identity. After a user’s identity is validated, the authorization process determines which sites, content, and other features the user can access. Authentication modes determine how accounts are used internally by SharePoint Foundation 2010.
In this article:
Supported authentication methods
Authentication modes — classic or claims-based
Implementing Windows authentication
Implementing forms-based authentication
Implementing SAML token-based authentication
Choosing authentication for LDAP environments
-
Supported authentication methods
SharePoint Foundation 2010 supports authentication methods that were included in previous versions and also introduces token-based authentication that is based on Security Assertion Markup Language (SAML) as an option. The following table lists the supported authentication methods.
Method
Examples
Notes
Windows
NTLM
Kerberos
Anonymous
Basic
Digest
At this time, Windows certificate authentication is not supported.
Forms-based authentication
Lightweight Directory Access Protocol (LDAP)
SQL database or other database
Custom or third-party membership and role providers
SAML token-based authentication
Active Directory Federation Services (AD FS) 2.0
Third-party identity provider
Lightweight Directory Access Protocol (LDAP)
Supported only with SAML 1.1 that uses the WS-Federation Passive profile.
-
Authentication modes — classic or claims-based
SharePoint Foundation 2010 introduces claims-based authentication, which is built on Windows Identity Foundation (WIF). You can use any of the supported authentication methods with claims-based authentication. Or, you can use classic-mode authentication, which supports Windows authentication.
When you create a Web application, you select one of the two authentication modes to use with the Web application, either claims-based or classic-mode.

If you select classic-mode, you can implement Windows authentication and the user accounts are treated by SharePoint Foundation 2010 as Active Directory Domain Services (AD DS) accounts.
If you select claims-based authentication, SharePoint Foundation 2010 automatically changes all user accounts to claims identities, resulting in a claims token for each user. The claims token contains the claims pertaining to the user. Windows accounts are converted into Windows claims. Forms-based membership users are transformed into forms-based authentication claims. Claims that are included in SAML-based tokens can be used by SharePoint Foundation 2010. Additionally, SharePoint developers and administrators can augment user tokens with additional claims. For example, user Windows accounts and forms-based accounts can be augmented with additional claims that are used by SharePoint Foundation 2010.
The following chart summarizes the support for authentication types by each authentication mode.
Type
Classic-mode authentication
Claims-based authentication
Windows
NTLM
Kerberos
Anonymous
Basic
Digest
Yes
Yes
Forms-based authentication
LDAP
SQL database or other database
Custom or third-party membership and role providers
No
Yes
SAML token-based authentication
AD FS 2.0
Windows Live ID
Third-party identity provider
LDAP
No
Yes
A SharePoint Foundation 2010 farm can include a mix of Web applications that use both modes. Services do not differentiate between user accounts that are traditional Windows accounts and Windows claims accounts. Consequently, a user who belongs to sites that are configured to use a mix of authentication modes will receive search results that include results from all the sites that the user has access to, regardless of the mode that is configured for Web applications. The user is not interpreted as two different user accounts. This is because services and service applications use claims identities for inter-farm communication regardless of the mode that is selected for Web applications and users.
However, users who belong to more than one user repository that is recognized by SharePoint Server Web applications are treated as separate user accounts, depending on which identity they use to log in.
The following guidance will help you decide which mode to select:
For new implementations of SharePoint Foundation 2010, use claims-based authentication. With this option, all supported authentication types are available for Web applications. There is no practical reason to select classic-mode authentication for new deployments, even if your environment includes only Windows accounts. Windows authentication is implemented the same way regardless of the mode that is selected. There are no additional steps to implement Windows authentication when you use the claims-based authentication mode.
If you are upgrading a previous version solution to SharePoint Foundation 2010 and the solution includes only Windows accounts, you can use classic-mode authentication. This lets you use the same design for zones and URLs.
If you are upgrading a solution that requires forms-based authentication, the only option is to upgrade to claims-based authentication.
If you are upgrading from an earlier version to SharePoint Foundation 2010 and you select claims-based authentication, be aware of the following considerations:
Custom code might need to be updated. Web Parts or other custom code that relies on or uses Windows identities will have to be updated. If the custom code uses Windows identities, use classic-mode authentication until the code is updated.
Migrating many Windows users to claims identities takes time. When you change a Web application from classic mode to claims-based during the upgrade process, you must use Windows PowerShell to convert Windows identities to claims identities. This can be a time-consuming process. Be sure to allow enough time during the upgrade process to complete this task.
Search alerts are currently not supported with claims-based authentication.
Claims authentication is built on WIF. WIF is a set of .NET Framework classes that are used to implement claims-based identity. Claims authentication relies on standards such as WS-Federation, WS-Trust, and protocols such as SAML. For more information about claims authentication, see the following resources:
Claims-based Identity for Windows: An Introduction to Active Directory Federation Services 2.0, Windows CardSpace 2.0, and Windows Identity Foundation (white paper) (http://go.microsoft.com/fwlink/?LinkId=198942)
Windows Identity Foundation home page (http://go.microsoft.com/fwlink/?LinkId=198943)
You do not have to be a claims architect to use claims authentication in SharePoint Foundation 2010. However, implementing SAML token-based authentication requires coordination with administrators of your claims-based environment, as described later in this article.
-
Implementing Windows authentication
The process of implementing Windows authentication methods is similar for both authentication modes (classic or claims-based). Choosing claims-based authentication for a Web application does not increase the complexity of implementing Windows authentication methods. This section summarizes the process for each method.
Integrated Windows authentication — Kerberos and NTLM
Both Kerberos protocol and NTLM are Integrated Windows authentication methods, which let clients seamlessly authenticate without being prompted for credentials. Users who access SharePoint sites from Windows Explorer will authenticate by using the credentials the Internet Explorer process is running under. By default, these credentials are the credentials that the user used to log on to the computer. Services or applications that access SharePoint Server in Integrated Windows authentication mode will attempt to authenticate by using the credentials of the running thread, which is the identity of the process by default.
NTLM is the simplest form of Windows authentication to implement. Simply select this option when you are creating a Web application.
Kerberos protocol is a secure protocol that supports ticketing authentication. Use of the Kerberos protocol requires additional configuration of the environment. To enable Kerberos authentication, the client and server computers must have a trusted connection to the domain Key Distribution Center (KDC). Configuring the Kerberos protocol involves setting up service principal names (SPNs) in AD DS before you install SharePoint Foundation 2010.
The following steps summarize the process of configuring Kerberos authentication:
1. Configure Kerberos authentication for SQL communications by creating SPNs in AD DS for the SQL Server service account.
2. Create SPNs for Web applications that will use Kerberos authentication.
3. Install the SharePoint Foundation 2010 farm.
4. Configure specific services within the farm to use specific accounts.
5. Create the Web applications that will use Kerberos authentication.
For more information, see Configure Kerberos authentication (SharePoint Server 2010) (http://technet.microsoft.com/library/3f849874-1580-47d3-af88-042a3494909f(Office.14).aspx).
Additionally, for claims-authentication Web applications, the claims to Windows token service must be configured for constrained delegation. Constrained delegation is required to convert claims to Windows tokens. For environments that include multiple forests, a two-way trust between forests is required to use the claims to Windows token service. For more information about how to configure this service, see Configure Kerberos authentication for the claims to Windows token service (SharePoint Server 2010) (http://technet.microsoft.com/library/9736e391-1dbf-4a37-b95d-3fdaa5baac7d(Office.14).aspx).
Kerberos authentication allows delegation of client credentials to access back-end data systems, which requires additional configuration depending on the scenario. The following table provides examples.
Scenario
Additional configuration
Delegating a client’s identity to a back-end server.
Displaying RSS feeds to authenticated content.
Configure Kerberos constrained delegation for computers and service accounts.
Identity delegation for Microsoft SQL Server Reporting Services (SSRS)
Configure SPNs for SQL Server Reporting Services accounts.
Configure delegation for SQL Server Reporting Services.
Identity delegation for Excel Services in SharePoint
Configure constrained delegation for servers that run Excel Services.
Configure constrained delegation for the Excel Services service account.
For more information about how to configure Kerberos authentication, including configuration steps for common scenarios, see Configuring Kerberos Authentication for Microsoft SharePoint 2010 Products and Technologies (white paper) (http://go.microsoft.com/fwlink/?LinkID=197178).
Digest and Basic
Implementing Digest and Basic authentication requires configuring these authentication methods directly in Internet Information Services (IIS).
-
Implementing forms-based authentication
Forms-based authentication is an identity management system that is based on ASP.NET membership and role provider authentication. In SharePoint Foundation 2010, forms-based authentication is available only when you use claims-based authentication.
Forms-based authentication can be used against credentials stored in AD DS, in a database such as a SQL Server database, or in an LDAP data store such as Novell eDirectory, Novell Directory Services (NDS), or Sun ONE. Forms-based authentication enables user authentication based on validation of credential input from a logon form. Unauthenticated requests are redirected to a logon page, where the user must provide valid credentials and submit the form. If the request can be authenticated, the system issues a cookie that contains a key for reestablishing the identity for subsequent requests.
To use forms-based authentication to authenticate users against an identity management system that is not based on Windows or that is external, you must register the membership provider and role manager in the Web.config file. Registering the role manager is a new requirement for SharePoint Foundation 2010. In the previous version, this was optional. SharePoint Foundation 2010 uses the standard ASP.NET role manager interface to gather group information about the current user. Each ASP.NET role is treated as a domain group by the authorization process in SharePoint Foundation 2010. You register role managers in the Web.config file the same way that you register membership providers for authentication.
If you want to manage membership users or roles from the SharePoint Central Administration Web site, you must register the membership provider and the role manager in the Web.config file for the Central Administration Web site. You must also register the membership provider and the role manager in the Web.config file for the Web application that hosts the content.
For more information about how to configure forms-based authentication, see the following resources:
TechNet article: Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010) (http://technet.microsoft.com/library/fd1391bb-c787-4742-b007-bf57e18dad66(Office.14).aspx)
MSDN blog article: Claims-based authentication “Cheat Sheet” Part 1 (http://go.microsoft.com/fwlink/?LinkId=198944)
MSDN article: Forms Authentication in SharePoint Products and Technologies (Part 2): Membership and Role Provider Samples (http://go.microsoft.com/fwlink/?LinkId=198945)
-
Implementing SAML token-based authentication
SAML token-based authentication requires coordination with administrators of a claims-based environment, whether it is your own internal environment or a partner environment. AD FS 2.0 is an example of a claims-based environment.
A claims-based environment includes an identity provider security token service (IP-STS). The IP-STS issues SAML tokens on behalf of users who are included in the associated user directory. Tokens can include any number of claims about a user, such as a user name and groups the user belongs to.
SharePoint Foundation 2010 takes advantage of claims that are included in tokens provided by an IP-STS to authorize users. In claims environments, an application that accepts SAML tokens is known as a relying party STS (RP-STS). A relying party application receives the SAML token and uses the claims inside to decide whether to grant the client access to the requested resource. In SharePoint 2010 Products, each Web application that is configured to use a SAML provider is added to the IP-STS server as a separate RP-STS entry. A SharePoint farm can include multiple RP-STS entries.
Implementing SAML token-based authentication with SharePoint 2010 Products involves the following processes that require advance planning:
1. Export the token-signing certificate from the IP-STS. This certificate is known as the ImportTrustCertificate. Copy the certificate to a server computer in the SharePoint Foundation 2010 farm.
2. Define the claim that will be used as the unique identifier of the user. This is known as the identity claim. Many examples of this process use the user e-mail name as the user identifier. Coordinate with the administrator of the IP-STS to determine the correct identifier because only the owner of the IP-STS knows which value in the token will always be unique per user. Identifying the unique identifier for the user is part of the claims-mapping process. Claims mappings are created by using Windows PowerShell.
3. Define additional claims mappings. Define which additional claims from the incoming token will be used by the SharePoint Foundation 2010 farm. User roles are an example of a claim that can be used to permission resources in the SharePoint Foundation 2010 farm. All claims from an incoming token that do not have a mapping will be discarded.
4. Create a new authentication provider by using Windows PowerShell to import the token-signing certificate. This process creates the SPTrustedIdentityTokenIssuer. During this process, you specify the identity claim and additional claims that you have mapped. You must also create and specify a realm that is associated with the first SharePoint Web applications that you are configuring for SAML token-based authentication. After the SPTrustedIdentityTokenIssuer is created, you can create and add more realms for additional SharePoint Web applications. This is how you configure multiple Web applications to use the same SPTrustedIdentityTokenIssuer.
5. For each realm that is added to the SPTrustedIdentityTokenIssuer, you must create an RP-STS entry on the IP-STS. This can be done before the SharePoint Web application is created. Regardless, you must plan the URL before you create the Web applications.
6. Create a new SharePoint Web application and configure it to use the newly created authentication provider. The authentication provider will appear as an option in Central Administration when claims mode is selected for the Web application.
You can configure multiple SAML token-based authentication providers. However, you can only use a token-signing certificate once in a farm. All providers that are configured will appear as options in Central Administration. Claims from different trusted STS environments will not conflict.
If you are implementing SAML token-based authentication with a partner company and your own environment includes an IP-STS, we recommend that you work with the administrator of your internal claims environment to establish a trust relationship from your internal IP-STS to the partner STS. This approach does not require adding an additional authentication provider to your SharePoint Foundation 2010 farm. It also allows your claims administrators to manage the whole claims environment.
Note:
If you use SAML token-based authentication with AD FS on a SharePoint Foundation 2010 farm that has multiple Web servers in a load-balanced configuration, there might be an effect on the performance and functionality of client Web-page views. When AD FS provides the authentication token to the client, that token is submitted to SharePoint Foundation 2010 for each permission-restricted page element. If the load-balanced solution is not using affinity, each secured element is authenticated to more than one SharePoint Foundation 2010 server, which might result in rejection of the token. After the token is rejected, SharePoint Foundation 2010 redirects the client to reauthenticate back to the AD FS server. After this occurs, an AD FS server might reject multiple requests that are made in a short time period. This behavior is by design, to protect against a denial of service attack. If performance is adversely affected or pages do not load completely, consider setting network load balancing to single affinity. This isolates the requests for SAML tokens to a single Web server.
For more information about how to configure SAML token-based authentication, see the following resources:
TechNet article: Configure authentication using a SAML security token (SharePoint Server 2010) (http://technet.microsoft.com/library/33a9bbc3-fcf5-4aaa-97ec-cd1c7a44d279(Office.14).aspx)
MSDN blog article: Claims-based authentication “Cheat Sheet” Part 2 (http://go.microsoft.com/fwlink/?LinkId=198946)
TechNet blog article: Planning Considerations for Claims Based Authentication in SharePoint 2010 (http://go.microsoft.com/fwlink/?LinkId=198947)
TechNet blog article: Creating both an Identity and Role Claim for a SharePoint 2010 Claims Auth Application (http://go.microsoft.com/fwlink/?LinkId=198948)
TechNet blog article: How to Create Multiple Claims Auth Web Apps in a Single SharePoint 2010 Farm (http://go.microsoft.com/fwlink/?LinkId=198949)
-
Choosing authentication for LDAP environments
LDAP environments can be implemented by using either forms-based authentication or SAML token-based authentication. We recommend that you use forms-based authentication because it is less complex. However, if the environment supports WS-Federation 1.1 and SAML Token 1.1, then SAML is recommended. Profile synchronization is not supported with LDAP providers that are not associated with ADFS 2.0.
-
Planning zones for Web applications
Zones represent different logical paths for gaining access to the same sites in a Web application. Each Web application can include as many as five zones. When a Web application is created, the default zone is created. Additional zones are created by extending the Web application and selecting one of the remaining zone names: intranet, extranet, Internet, or custom.
In previous versions, zones are used to implement different types of authentication for users coming from different networks or authentication providers. In the current version, claims authentication allows multiple types of authentication to be implemented on the same zone.
Your plan for zones will depend on which of the following modes is selected for a Web application:
Classic mode — Similar to previous versions, only one type of authentication can be implemented per zone. However, in the current version, only Windows authentication can be implemented when classic mode is selected. Consequently, multiple zones can be used only to implement multiple types of Windows authentication, or to implement the same type of Windows authentication against different Active Directory stores.
Claims authentication — Multiple authentication providers can be implemented on a single zone. Multiple zones can be used also.
Implementing more than one type of authentication on a single zone
If you are using claims authentication and implementing more than one type of authentication, we recommend that you implement multiple types of authentication on the default zone. This results in the same URL for all users.
When you are implementing multiple types of authentication on the same zone, the following restrictions apply:
Only one instance of forms-based authentication can be implemented on a zone.
Central Administration allows you to use both an Integrated Windows method and Basic at the same time. Otherwise, more than one type of Windows authentication cannot be implemented on a zone.
If multiple SAML token-based authentication providers are configured for a farm, these will all appear as options when you create a Web application or a new zone. Multiple SAML providers can be configured on the same zone.
The following diagram illustrates multiple types of authentication implemented on the default zone for a partner collaboration site.

In the diagram, users from different directory stores access the partner Web site by using the same URL. A dashed box surrounding partner companies shows the relationship between the user directory and the authentication type that is configured in the default zone. For more information about this design example, see Design sample: Corporate deployment (SharePoint Server 2010) (http://technet.microsoft.com/library/1cffb278-6497-46fc-abd0-3dd652064c89(Office.14).aspx).
Planning for crawling content
The crawl component requires access to content using NTLM. At least one zone must be configured to use NTLM authentication. If NTLM authentication is not configured on the default zone, the crawl component can use a different zone that is configured to use NTLM authentication.
Implementing more than one zone
If you plan to implement more than one zone for Web applications, use the following guidelines:
Use the default zone to implement your most secure authentication settings. If a request cannot be associated with a specific zone, the authentication settings and other security policies of the default zone are applied. The default zone is the zone that is created when you initially create a Web application. Typically, the most secure authentication settings are designed for end-user access. Consequently, end users are likely to access the default zone.
Use the minimum number of zones that are required to provide access to users. Each zone is associated with a new IIS site and domain for accessing the Web application. Only add new access points when these are required.
Ensure that at least one zone is configured to use NTLM authentication for the crawl component. Do not create a dedicated zone for the index component unless it is necessary.
The following diagram illustrates multiple zones that are implemented to accommodate different authentication types for a partner collaboration site.

In the diagram, the default zone is used for remote employees. Each zone has a different URL associated with it. Employees use a different zone depending on whether they are working in the office or are working remotely.
For more information about this design example, see Design sample: Corporate deployment (SharePoint Server 2010) (http://technet.microsoft.com/library/1cffb278-6497-46fc-abd0-3dd652064c89(Office.14).aspx).
-
Architecture for SAML token-based providers
The architecture for implementing SAML token-based providers includes the following components:
SharePoint security token service This service creates the SAML tokens that are used by the farm. The service is automatically created and started on all servers in a server farm. The service is used for inter-farm communication because all inter-farm communication uses claims authentication. This service is also used for authentication methods that are implemented for Web applications that use claims authentication, including Windows authentication, forms-based authentication, and SAML token-based authentication. You must configure the security token service during the deployment process. For more information, see Configure the security token service (SharePoint Server 2010) (http://technet.microsoft.com/library/156cbd50-a05b-4490-b869-f74e2fc0e09d(Office.14).aspx).
Token-signing certificate (ImportTrustCertificate) This is the certificate that is exported from an IP-STS. The certificate is copied to one server in the farm. Once you use this certificate to create an SPTrustedIdentityTokenIssuer, you cannot use it again to create another one. If you want to use the certificate to create a different SPTrustedIdentityTokenIssuer, you must delete the existing one first. Before you delete an existing one, you must disassociate it from any Web applications that may be using it.
Identity claim The identity claim is the claim from a SAML token that is the unique identifier of the user. Only the owner of the IP-STS knows which value in the token will always be unique for each user. The identity claim is created as a regular claims mapping during the process of mapping all desired claims. The claim that serves as the identity claim is declared when the SPTrustedIdentityTokenIssuer is created.
Other claims These claims consist of additional claims from a SAML ticket that describe users. These can include user roles, user groups, or other kinds of claims such as age. All claims mappings are created as objects that are replicated across the servers in a SharePoint Foundation farm.
Realm In the SharePoint claims architecture, the URI or URL that is associated with a SharePoint Web application that is configured to use a SAML token-based provider represents a realm. When you create a SAML-based authentication provider on the farm, you specify the realms, or Web application URLs, that you want the IP-STS to recognize, one at a time. The first realm is specified when you create the SPTrustedIdentityTokenIssuer. Additional realms can be added after the SPTrustedIdentityTokenIssuer is created. Realms are specified by using syntax similar to the following: $realm = “urn:sharepoint:mysites”. After you add the realm to the SPTrustedIdentityTokenIssuer, you must create an RP-STS trust with the realm on the IP-STS server. This process involves specifying the URL for the Web application.
SPTrustedIdentityTokenIssuer This is the object that is created on the SharePoint farm that includes the values necessary to communicate with and receive tokens from the IP-STS. When you create the SPTrustedIdentityTokenIssuer, you specify which token-signing certificate to use, the first realm, the claim that represents the identity claim, and any additional claims. You can only associate a token-signing certificate from an STS with one SPTrustedIdentityTokenIssuer. However, after you create the SPTrustedIdentityTokenIssuer, you can add more realms for additional Web applications. After a realm is added to the SPTrustedIdentityTokenIssuer, it must also be added to the IP-STS as a relying party. The SPTrustedIdentityTokenIssuer object is replicated across servers in the SharePoint Foundation farm.
Relying party security token service (RP-STS) In SharePoint Foundation 2010, each Web application that is configured to use a SAML provider is added to the IP-STS server as an RP-STS entry. A SharePoint Foundation farm can include multiple RP-STS entries.
Identity provider security token service (IP-STS) This is the secure token service in the claims environment that issues SAML tokens on behalf of users who are included in the associated user directory.
The following diagram illustrates the SharePoint 2010 Products claims architecture.

The SPTrustedIdentityTokenIssuer object is created by using several parameters. The following diagram illustrates the key parameters.

As the diagram illustrates, an SPTrustedIdentityTokenIssuer can include only one identity claim, one SignInURL parameter, and one Wreply parameter. However, it can include multiple realms and multiple claims mappings. The SignInURL parameter specifies the URL to redirect a user request to in order to authenticate to the IP-STS. Some IP-STS servers require the Wreply parameter, which is set to either true or false and is false by default. Only use the Wreply parameter if it is required by the IP-STS.
-
Plan security hardening (SharePoint Foundation 2010)
This article describes security hardening for Microsoft SharePoint Foundation 2010 Web server, application server, and database server roles, and gives detailed guidance about the specific hardening requirements for ports, protocols, and services in Microsoft SharePoint 2010 Products.
In this article:
Secure server snapshots (http://technet.microsoft.com/library/7dcb6a86-f9d4-4c0f-b7c6-fa12a47029c4.aspx#ServerSnapshots)
-
Secure server snapshots
In a server farm environment, individual servers play specific roles. Security hardening recommendations for these servers depend on the role each server plays. This article contains secure snapshots for two categories of server roles:
Web server and application server roles
The snapshots are divided into common configuration categories. The characteristics defined for each category represent the optimal hardened state for Microsoft SharePoint 2010 Products. This article does not include hardening guidance for other software in the environment.
This section identifies hardening characteristics for Web servers and application servers. Some of the guidance applies to specific service applications; in these cases, the corresponding characteristics need to be applied only on the servers that are running the services associated with the specified service applications.
Category
Characteristic
Services listed in the Services MMC snap-in
Enable the following services:
File and Printer Sharing
World Wide Web Publishing Service
Ensure that these services are not disabled:
Claims to Windows Token Service
SharePoint 2010 Administration
SharePoint 2010 Timer
SharePoint 2010 Tracing
SharePoint 2010 VSS Writer
Ensure that these services are not disabled on the servers that host the corresponding roles:
SharePoint 2010 User Code Host
SharePoint Foundation Search V4
Ports and protocols
TCP 80, TCP 443 (SSL)
File and Printer Sharing service —either of the following, used by search roles:
Direct-hosted SMB (TCP/UDP 445) — this is the recommended port
NetBIOS over TCP/IP (NetBT) (TCP/UDP ports 137, 138, 139) — disable this port if you do not use it
Ports required for communication between Web servers and service applications (the default is HTTP):
HTTP binding: 32843
HTTPS binding: 32844
net.tcp binding: 32845 (only if a third party has implemented this option for a service application)
UDP port 1434 and TCP port 1433 — default ports for SQL Server communication. If these ports are blocked on the SQL Server computer (recommended) and databases are installed on a named instance, configure a SQL Server client alias for connecting to the named instance.
TCP/IP 32846 for the Microsoft SharePoint Foundation User Code Service (for sandbox solutions) — This port must be open for outbound connections on all Web servers. This port must be open for inbound connections on Web servers or application servers where this service is turned on.
Ensure that ports remain open for Web applications that are accessible to users.
Block external access to the port that is used for the Central Administration site.
TCP/25 (SMTP for e-mail integration)
Registry
No additional guidance
Auditing and logging
If log files are relocated, ensure that the log file locations are updated to match. Update directory access control lists (ACLs) also.
Code access security
Ensure that you have a minimal set of code access security permissions enabled for your Web application. The <trust> element in the Web.config file for each Web application should be set to WSS_Minimal (where WSS_Minimal has its low defaults as defined in 14\config\wss_minimaltrust.config or by your own custom policy file, which is minimally set.)
Web.config
Follow these recommendations for each Web.config file that is created after you run Setup:
Do not allow compilation or scripting of database pages via the PageParserPaths elements.
Ensure <SafeMode> CallStack=””false”” and AllowPageLevelTrace=””false””.
Ensure that the Web Part limits around maximum controls per zone is set low.
Ensure that the SafeControls list is set to the minimum set of controls needed for your sites.
Ensure that your Workflow SafeTypes list is set to the minimum level of SafeTypes needed.
Ensure that customErrors is turned on (<customErrors mode=””On””/>).
Consider your Web proxy settings as needed (<system.net>/<defaultProxy>).
Set the Upload.aspx limit to the highest size you reasonably expect users to upload (default is 2 GB). Performance can be affected by uploads that exceed 100 MB.
The primary recommendation forSharePoint 2010 Products is to secure inter-farm communication by blocking the default ports used for Microsoft SQL Server communication and establishing custom ports for this communication instead. For more information about how to configure ports for SQL Server communication, see Blocking the standard SQL Server ports, later in this article.
Category
Characteristic
Ports
Block UDP port 1434.
Consider blocking TCP port 1433.
This article does not describe how to secure SQL Server. For more information about how to secure SQL Server, see Securing SQL Server (http://go.microsoft.com/fwlink/?LinkId=186828).
-
Specific port, protocol, and service guidance
The rest of this article describes in greater detail the specific hardening requirements for SharePoint 2010 Products.
In this section:
Blocking the standard SQL Server ports
Service application communication
File and Printer Sharing service requirements
User Profile service hardening requirements
Connections to external servers
Service requirements for e-mail integration
Service requirements for session state
SharePoint 2010 Products services
The specific ports used to connect to SQL Server are affected by whether databases are installed on a default instance of SQL Server or a named instance of SQL Server. The default instance of SQL Server listens for client requests on TCP port 1433. A named instance of SQL Server listens on a randomly assigned port number. Additionally, the port number for a named instance can be reassigned if the instance is restarted (depending on whether the previously assigned port number is available).
By default, client computers that connect to SQL Server first connect by using TCP port 1433. If this communication is unsuccessful, the client computers query the SQL Server Resolution Service that is listening on UDP port 1434 to determine the port on which the database instance is listening.
The default port-communication behavior of SQL Server introduces several issues that affect server hardening. First, the ports used by SQL Server are well-publicized ports and the SQL Server Resolution Service has been the target of buffer overrun attacks and denial-of-service attacks, including the “Slammer” worm virus. Even if SQL Server is updated to mitigate security issues in the SQL Server Resolution Service, the well-publicized ports remain a target. Second, if databases are installed on a named instance of SQL Server, the corresponding communication port is randomly assigned and can change. This behavior can potentially prevent server-to-server communication in a hardened environment. The ability to control which TCP ports are open or blocked is essential to securing your environment.
Consequently, the recommendation for a server farm is to assign static port numbers to named instances of SQL Server and to block UDP port 1434 to prevent potential attackers from accessing the SQL Server Resolution Service. Additionally, consider reassigning the port used by the default instance and blocking TCP port 1433.
There are several methods you can use to block ports. You can block these ports by using a firewall. However, unless you can be sure that there are no other routes into the network segment and that there are no malicious users that have access to the network segment, the recommendation is to block these ports directly on the server that hosts SQL Server. This can be accomplished by using Windows Firewall in Control Panel.
-
Configuring SQL Server database instances to listen on a nonstandard port
SQL Server provides the ability to reassign the ports that are used by the default instance and any named instances. In SQL Server 2005 and SQL Server 2008, you reassign ports by using SQL Server Configuration Manager.
-
Configuring SQL Server client aliases
In a server farm, all front-end Web servers and application servers are SQL Server client computers. If you block UDP port 1434 on the SQL Server computer, or you change the default port for the default instance, you must configure a SQL Server client alias on all servers that connect to the SQL Server computer.
To connect to an instance of SQL Server 2005 or SQL Server 2008, you install SQL Server client components on the target computer and then configure the SQL Server client alias by using SQL Server Configuration Manager. To install SQL Server client components, run Setup and select only the following client components to install:
Connectivity Components
Management Tools (includes SQL Server Configuration Manager)
For specific hardening steps for blocking the standard SQL ports, see Harden SQL Server for SharePoint environments (SharePoint Foundation 2010) (http://technet.microsoft.com/library/2b390dec-8719-4d18-b283-f97140dfea92(Office.14).aspx).
By default, communication between Web servers and service applications within a farm takes place by using HTTP with a binding to port 32843. When you publish a service application, you can select either HTTP or HTTPS with the following bindings:
HTTP binding: port 32843
HTTPS binding: port 32844
Additionally, third parties that develop service applications can implement a third choice:
net.tcp binding: port 32845
You can change the protocol and port binding for each service application. On the Service Applications page in Central Administration, select the service application, and then click Publish.
Communication between service applications and SQL Server takes place over the standard SQL Server ports or the ports that you configure for SQL Server communication.
Several core features depend on the File and Printer Sharing service and the corresponding protocols and ports. These include, but are not limited to, the following:
Search queries All search queries require the File and Printer Sharing service.
Crawling and indexing content To crawl content, servers that include crawl components send requests through the front-end Web server. The front-end Web server communicates with content databases directly and sends results back to the servers that include crawl components. This communication requires the File and Printer Sharing service.
The File and Printer Sharing service requires the use of named pipes. Named pipes can communicate by using either direct-hosted SMB or NetBT protocols. For a secure environment, direct-hosted SMB is recommended instead of NetBT. The hardening recommendations provided in this article assume that SMB is used.
The following table describes the hardening requirements that are introduced by the dependency on the File and Printer Sharing service.
Category
Requirements
Notes
Services
File and Printer Sharing
Requires the use of named pipes.
Protocols
Named pipes that use direct-hosted SMB
Disable NetBT
Named pipes can use NetBT instead of direct-hosted SMB. However, NetBT is not considered as secure as direct-hosted SMB.
Ports
Either of the following:
Direct-hosted SMB (TCP/UDP 445) — recommended
NetBT (TCP/UDP ports 137, 138, 139)
Disable NetBT (ports 137, 138, and 139) if it is not being used
For more information about how to disable NetBT, see the Microsoft Knowledge Base article 204279, Direct hosting of SMB over TCP/IP (http://go.microsoft.com/fwlink/?LinkId=76143).
E-mail integration requires the use of two services:
Microsoft SharePoint Directory Management service
E-mail integration requires the use of the Simple Mail Transfer Protocol (SMTP) service on at least one of the front-end Web servers in the server farm. The SMTP service is required for incoming e-mail. For outgoing e-mail, you can either use the SMTP service or route outgoing email through a dedicated e-mail server in your organization, such as a Microsoft Exchange Server computer.
SharePoint 2010 Products include an internal service, the Microsoft SharePoint Directory Management Service, for creating e-mail distribution groups. When you configure e-mail integration, you have the option to enable the Directory Management Service feature, which lets users create distribution lists. When users create a SharePoint group and they select the option to create a distribution list, the Microsoft SharePoint Directory Management Service creates the corresponding Active Directory distribution list in the Active Directory environment.
In security-hardened environments, the recommendation is to restrict access to the Microsoft SharePoint Directory Management Service by securing the file associated with this service, which is SharePointEmailws.asmx. For example, you might allow access to this file by the server farm account only.
Additionally, this service requires permissions in the Active Directory environment to create Active Directory distribution list objects. The recommendation is to set up a separate organizational unit (OU) in Active Directory for SharePoint 2010 Products objects. Only this OU should allow write access to the account that is used by the Microsoft SharePoint Directory Management Service.
Do not disable services that are installed by SharePoint 2010 Products (listed in the snapshot previously).
If your environment disallows services that run as a local system, you can consider disabling the SharePoint 2010 Administration service only if you are aware of the consequences and can work around them. This service is a Win32 service that runs as a local system.
This service is used by the SharePoint 2010 Timer service to perform actions that require administrative permissions on the server, such as creating Internet Information Services (IIS) Web sites, deploying code, and stopping and starting services. If you disable this service, you cannot complete deployment-related tasks from the Central Administration site. You must use Windows PowerShell to run the Start-SPAdminJob (http://technet.microsoft.com/library/a96146cd-9973-4680-9a0b-d91ec51200d5(Office.14).aspx) cmdlet (or use the Stsadm.exe command-line tool to run the execadmsvcjobs operation) to complete multiple-server deployments for SharePoint 2010 Products and to run other deployment-related tasks.
The .NET Framework, and ASP.NET in particular, use XML-formatted configuration files to configure applications. The .NET Framework relies on configuration files to define configuration options. The configuration files are text-based XML files. Multiple configuration files can, and typically do, exist on a single system.
System-wide configuration settings for the .NET Framework are defined in the Machine.config file. The Machine.config file is located in the %SystemRoot%\Microsoft.NET\Framework\%VersionNumber%\CONFIG\ folder. The default settings that are contained in the Machine.config file can be modified to affect the behavior of applications that use the .NET Framework on the whole system.
You can change the ASP.NET configuration settings for a single application if you create a Web.config file in the root folder of the application. When you do this, the settings in the Web.config file override the settings in the Machine.config file.
When you extend a Web application by using Central Administration, SharePoint 2010 Products automatically create a Web.config file for the Web application.
The Web server and application server snapshot presented earlier in this article lists recommendations for configuring Web.config files. These recommendations are intended to be applied to each Web.config file that is created, including the Web.config file for the Central Administration site.
For more information about ASP.NET configuration files and editing a Web.config file, see ASP.NET Configuration (http://go.microsoft.com/fwlink/?LinkID=73257).
-
-
Plan automatic password change (SharePoint Foundation 2010)
To simplify password management, the automatic password change feature enables you to update and deploy passwords without having to perform manual password update tasks across multiple accounts, services, and Web applications. You can configure the automatic password change feature to determine if a password is about to expire and reset the password using a long, cryptographically-strong random string. To implement the automatic password change feature, you have to configure managed accounts.
In this article:
Configuring managed accounts
Resetting passwords automatically on a schedule
Detecting password expiration
Resetting the account password immediately
Synchronizing SharePoint Foundation account passwords with Active Directory Domain Services
Resetting all passwords immediately
Credential change process
-
Configuring managed accounts
Microsoft SharePoint Foundation 2010 supports the creation of managed accounts to improve security and ensure application isolation. Using managed accounts, you can configure the automatic password change feature to deploy passwords across all services in the farm. You can configure SharePoint Web applications and services, running on application servers in a SharePoint farm, to use different domain accounts. You can create multiple accounts in Active Directory Domain Services (AD DS), and then register each of these accounts in SharePoint Foundation 2010. You can map managed accounts to various services and Web applications in the farm.
-
Resetting passwords automatically on a schedule
Prior to the implementation of the automatic password change feature, updating passwords required resetting each account password in AD DS and then manually updating account passwords on all of the services running on all the computers in the farm. To do this, you had to run the Stsadm command-line tool or use the SharePoint Central Administration Web application. Using the automatic password change feature, you can now register managed accounts and enable SharePoint Foundation 2010 to control account passwords. Users have to be notified about planned password changes and related service interruptions, but the accounts used by a SharePoint farm, Web applications, and various services can be automatically reset and deployed within the farm as necessary, based on individually configured password reset schedules.
-
Detecting password expiration
IT departments typically impose a policy requiring that all domain account passwords be reset on a regular basis, for example, every 60 days. SharePoint Foundation 2010 can be configured to detect imminent password expiration, and send an e-mail notification to a designated administrator. Even without administrator intervention, SharePoint Foundation 2010 can be configured to generate and reset passwords automatically. The automatic password reset schedule is also configurable to ensure that the impact of possible service interruptions during a password reset will be minimal.
-
Resetting the account password immediately
You can always override any automatic password reset schedule and force an immediate service account password reset, using a specific password value. In this scenario, the password for the service account can also be changed in AD DS by SharePoint Foundation 2010. The new password is then immediately propagated to other servers in the farm.
-
Synchronizing SharePoint Foundation account passwords with Active Directory Domain Services
If AD DS and SharePoint Foundation 2010 account passwords are not synchronized, services in the SharePoint farm will not start. If an Active Directory administrator changes an Active Directory account password without coordinating the password change with a SharePoint administrator, there is a risk of service interruptions. In this scenario, a SharePoint administrator can immediately reset the password from the Account Management page using the password value that was changed in AD DS. The password is updated and immediately propagated to the other servers in the SharePoint farm.
-
Resetting all passwords immediately
If an administrator suddenly leaves your organization, or if the service account passwords need to be immediately reset for any other reason, you can quickly create a Windows PowerShell script that calls the password change cmdlets. You can use the script to generate new random passwords and deploy the new passwords immediately.
-
Credential change process
When SharePoint Foundation 2010 changes the credentials for a managed account, the credential change process will occur on one server in the farm. Each server in the farm will be notified that the credentials are about to change and servers can perform critical pre-change actions, if necessary. If the account password has not yet been changed, then SharePoint Foundation 2010 will attempt to change the password using either a manually entered password, or a long, cryptographically-strong random string. The complexity settings will be queried from the appropriate policy (network or local), and the generated password will be equivalent to the detected settings.SharePoint Foundation 2010 will attempt to commit a password change. If it is unable to commit the password change, it will retry, using a new sequence, for a specified number of times. If the account password update process succeeds, it will proceed to the next dependent service, where it will again attempt to commit a password change. If it does not ultimately succeed, each dependent service will be notified that they can resume normal activity. Either success in committing a password change or failure to commit will result in the generation of an automated password change status notification that will be sent by e-mail to farm administrators.
-
See Also
Configure automatic password change (SharePoint Foundation 2010) (http://technet.microsoft.com/library/a1784b2d-68a4-409d-a8fa-35d0ab885e24(Office.14).aspx)
-
-
SQL Server and storage (SharePoint Foundation 2010)
This section describes how to plan for Microsoft SQL Server and storage configuration for Microsoft SharePoint Foundation 2010.
In this section:
Overview of SQL Server in a SharePoint environment (SharePoint Foundation 2010)
This article describes the relationship between SharePoint Foundation 2010 and supported versions of SQL Server. It also describes how you can interact with the databases, and introduces ways of using the reporting and business intelligence (BI) features of SQL Server with SharePoint Foundation 2010.
Overview of Remote BLOB Storage (SharePoint Foundation 2010)
This article describes how SharePoint Foundation 2010 works with remote BLOB storage.
Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010)
This article describes the factors to consider when moving to a remote BLOB storage solution.
-
Overview of SQL Server in a SharePoint environment (SharePoint Foundation 2010)
This article describes the relationship between Microsoft SharePoint Foundation 2010 and supported versions of Microsoft SQL Server. It also describes how you can interact with the databases, and it introduces ways of using the reporting and business intelligence (BI) features of SQL Server with SharePoint Foundation 2010.
For more information about the supported versions of SQL Server, see Hardware and software requirements (SharePoint Foundation 2010).
In this article:
SharePoint 2010 Products and the SQL Server database engine
SQL Server as a data platform for business intelligence in SharePoint 2010 Products
-
SharePoint 2010 Products and the SQL Server database engine
SharePoint Foundation 2010 is an application that is built on the SQL Server database engine. Most content and settings in SharePoint Foundation 2010 are stored in relational databases. SharePoint Foundation 2010 uses the following kinds of databases:
Configuration The Configuration database and Central Administration content database are called configuration databases. They contain data about farm settings such as the databases used, Internet Information Services (IIS) Web sites or web applications, solutions, Web Part packages, site templates, default quota, and blocked file types. A farm can only have one set of configuration databases.
Content Content databases store all site content: site documents, such as files in document libraries, list data; Web Part properties; and user names and rights. All the data for a specific site resides in one content database. Each Web application can contain many content databases. Each site collection can be associated with only one content database, although a content database can be associated with many site collections.
Service application Service application databases store data for use by a service application. The databases for service applications vary significantly in what they are used for.
For a full list of all of the databases that support SharePoint Foundation 2010, see Database types and descriptions (SharePoint Server 2010) (http://technet.microsoft.com/library/9b1e8b21-7675-4186-beb6-3adeef4360e6(Office.14).aspx).Database types and descriptions (SharePoint Foundation 2010) (http://technet.microsoft.com/library/da66a206-369d-46bc-b974-cf3564baadff(Office.14).aspx).
-
Working with the SQL Server databases that support SharePoint 2010 Products
The SQL Server databases that support SharePoint Foundation 2010 can be created either by SharePoint Foundation 2010, or by a database administrator. For more information, see Deploy by using DBA-created databases (SharePoint Foundation 2010) (http://technet.microsoft.com/library/c7647e52-2178-4d3d-9376-84b2c9a35a1e(Office.14).aspx).
Microsoft does not support directly querying or modifying the databases that support SharePoint Foundation 2010, except for the Usage and Health Data Collection service application database, which can be queried directly and can have its schema added to.
The SQL Server databases that support SharePoint Foundation 2010 are subject to sizing limitations and to configuration recommendations that are not standard for SQL Server.
-
-
SQL Server as a data platform for business intelligence in SharePoint 2010 Products
SharePoint Foundation 2010 can be used with SQL Server BI tools to analyze and display BI data in meaningful ways. SQL Server provides the primary data infrastructure and business intelligence platform that gives report authors and business users trusted, scalable, and secure data.
The following sections describe the technologies and features in SQL Server that support business intelligence functionality and features in SharePoint Foundation 2010.
-
SQL Server database engine
The SQL Server database engine is the core service for storing, processing, and securing data. BI data can be collected from the SQL Server database engine. For more information, see SQL Server Database Engine (http://go.microsoft.com/fwlink/?LinkId=199540).
-
SQL Server Analysis Services (SSAS): multi-dimensional data
Microsoft SQL Server Analysis Services (SSAS) multidimensional data enables you to design, create, and manage multidimensional structures that contain detail and aggregated data from multiple data sources. A cube wizard is available in SQL Server 2008 R2 that simplifies how you can create cubes. Dimensional data or cube data is a prototypical data source for the types of analysis that can be done by using the business intelligence-related service applications in SharePoint Foundation 2010. For more information, see SQL Server Analysis Services – Multidimensional Data (http://go.microsoft.com/fwlink/?LinkId=199541).
-
SQL Server Analysis Services: data mining
SQL Server Analysis Services data mining tools provide a set of industry-standard data mining algorithms and other tools that help you discover trends and patterns in your data. The following Excel add-ins help you perform predictive analysis:
Table Analysis Tools for Excel provide easy-to-use tools that take advantage of Analysis Services Data Mining to perform powerful analytics on spreadsheet data. For more information, see SQL Server Analysis Services – Data Mining (http://go.microsoft.com/fwlink/?LinkId=199543).
Data Mining Client for Excel lets users build, test, and query data mining models within Microsoft Office Excel 2007 by using either worksheet data or external data available through Analysis Services.
Note:
To enable add-ins, you must have a connection to the server.
-
SQL Server Reporting Services (SSRS)
Microsoft SQL Server Reporting Services (SSRS) and SharePoint Foundation 2010 are easily integrated. SQL Server Reporting Services has a full range of tools with which you can create, deploy, and manage reports for your organization. It also has features that enable you to extend and customize your reporting functionality.
The available functionality includes:
Creating reports with Report Builder 3, one of the SQL Server Reporting Services authoring tools, which you can launch directly from SharePoint Foundation 2010.
Publishing SSRS reports in SharePoint Foundation 2010.
You can publish report server content types to a SharePoint library and then view and manage those documents from a SharePoint site.
For more information about SSRS, see SQL Server Reporting Services (http://go.microsoft.com/fwlink/?LinkId=199545). For more information about how to install the different integration modes, see Overview of documentation for SQL Server Reporting Services reports in SharePoint (http://technet.microsoft.com/library/44be0f8c-e167-4b92-9125-2c03b4e440cf(Office.14).aspx).
-
SQL Server Integration Services (SSIS)
Microsoft SQL Server Integration Services (SSIS) provides rich data integration and data transformation solutions. You can create a repeatable extract, transform, and load (ETL) process to automate moving data from sources such as XML data files, flat files, or relational data sources to one or more destinations. If data comes from disparate sources and is not mined or cleansed for the benefits that are provided in BI applications, SQL Server Integration Services helps prepare the data. For more information, see SQL Server Integration Services (http://go.microsoft.com/fwlink/?LinkId=199546).
-
Business Intelligence Development Studio (BIDS)
Microsoft Business Intelligence Development Studio (BIDS) provides intuitive wizards for building integration, reporting, and analytic solutions in a unified environment. BIDS supports the complete development life cycle of developing, testing, and deploying solutions and reports. BIDS is based on the Visual Studio 2005 development environment but customizes it with the SQL Server services–specific extensions and project types for reports, ETL data flows, OLAP cubes, and data mining structure.
-
PowerPivot for Excel and PowerPivot for SharePoint
PowerPivot is an add-in that enables users to create self-service BI solutions. It also facilitates sharing and collaboration on those solutions in a SharePoint Foundation 2010 environment. PowerPivot also enables IT organizations to increase operational efficiencies through Microsoft SQL Server 2008 management tools. Components of PowerPivot include the following:
PowerPivot for Excel 2010 is a data analysis add-in that delivers computational power directly to Microsoft Excel 2010. PowerPivot for Excel (formerly known as “Gemini”) lets users analyze large quantities of data, and its integration with SharePoint Foundation 2010 helps IT departments monitor and manage how users collaborate. The add-in removes the one-million-row limit for worksheets and provides rapid calculations for large data sets. For more information, see PowerPivot Overview (http://go.microsoft.com/fwlink/?LinkId=199547).
PowerPivot for SharePoint 2010 extends SharePoint Foundation 2010 and Excel Services to add server-side processing, collaboration, and document management support for the PowerPivot workbooks that you publish to SharePoint sites. For more information, see PowerPivot for SharePoint (http://go.microsoft.com/fwlink/?LinkId=199547).
-
Master Data Services
SQL Server Master Data Services lets you centrally manage important data assets companywide and across diverse systems to provide more trusted data to your BI applications. Master Data Services helps you create a master data hub that includes a thin-client data management application for a data steward. The application can also apply workflow to assigned owners, apply extensible business rules to safeguard data quality, and apply hierarchy and attribute management strategies. For more information, see Master Data Services (http://go.microsoft.com/fwlink/?LinkId=199548).
-
StreamInsight and complex event processing
Microsoft StreamInsight is a new feature in SQL Server 2008 R2 that provides a powerful platform for developing and deploying complex event processing (CEP) applications. CEP is a technology for processing streams of events with high-throughput and low-latency. StreamInsight lets you analyze data without first storing it, and helps you monitor data from multiple sources to detect patterns, trends, and exceptions almost instantly. The ability to monitor, analyze, and act on data in motion in an event-driven manner provides significant opportunity to make more rapid, informed business decisions. For more information, see Microsoft StreamInsight (http://go.microsoft.com/fwlink/?LinkId=199549).
-
-
Related content
-
Overview of Remote BLOB Storage (SharePoint Foundation 2010)
This article describes how you can use Microsoft SharePoint Foundation 2010 together with Remote BLOB Storage (RBS) and Microsoft SQL Server 2008 Express and Microsoft SQL Server 2008 R2 Express to optimize database storage resources.
Before you implement RBS, we highly recommend that you evaluate its potential costs and benefits. For more information and recommendations about using RBS in a SharePoint Foundation 2010 installation, see Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010).
In this article:
-
Introduction to RBS
RBS is a library API set that is incorporated as an add-on feature pack for Microsoft SQL Server. It can be run on the local server running Microsoft SQL Server 2008 R2, SQL Server 2008 or SQL Server 2008 R2 Express. To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise edition. RBS is not supported for Microsoft SQL Server 2005.
Binary large objects (BLOBs) are data elements that have either of the following characteristics:
Unstructured data that has no schema (such as a piece of encrypted data).
A large amount of binary data (many megabytes or gigabytes) that has a very simple schema, such as image files, streaming video, or sound clips.
By default, SQL Server stores BLOB data in its databases. As a database’s usage increases, the total size of its BLOB data can expand quickly and grow larger than the total size of the document metadata and other structured data that is stored in the database. Because BLOB data can consume a lot of file space and uses server resources that are optimized for database access patterns, it can be helpful to move BLOB data out of the SQL Server database, and into a separate file.
Before RBS was supported in SQL Server, expensive storage such as RAID 10 was required for the whole SQL database including BLOB data. By using RBS, you can move 80 to 90 percent of the data (that is, BLOBs) onto less expensive storage such as RAID 5 or external storage solutions.
RBS uses a provider to connect to any dedicated BLOB store that uses the RBS APIs. Storage solution vendors can implement providers that work with RBS APIs. SharePoint Foundation 2010 supports a BLOB storage implementation that accesses BLOB data by using the RBS APIs through such a provider. You can implement RBS for Microsoft SharePoint 2010 Products by using a supported provider that you obtain from a third-party vendor. Most third-party providers store BLOBs remotely.
In addition to third-party providers, you can use the RBS FILESTREAM provider that is available through the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The RBS FILESTREAM provider uses the SQL Server FILESTREAM feature to store BLOBs in an additional resource that is attached to the same database and stored locally on the server. The FILESTREAM feature manages BLOBs in a SQL database by using the underlying NTFS file system.
The location that an RBS provider stores the BLOB data depends on the provider that you use. In the case of the SQL FILESTREAM provider, the data is not stored in the MDF file, but in another file that is associated with the database.
This implementation of the FILESTREAM provider is known as the local FILESTREAM provider. You can conserve resources by using the local RBS FILESTREAM provider to place the extracted BLOB data on a different (cheaper) local disk such as RAID 5 instead of RAID 10. You cannot use RBS with the local FILESTREAM provider on remote storage devices, such as network attached storage (NAS). The FILESTREAM provider is supported when it is used on local hard disk drives only.
A remote RBS FILESTREAM provider that is available in SQL Server 2008 R2 Express can store BLOB data on remote commodity storage such as direct-attached storage (DAS) or NAS. However, SharePoint Foundation 2010 does not currently support the remote RBS FILESTREAM provider.
-
Using RBS together with SharePoint 2010 Products
SharePoint Foundation 2010 supports the FILESTREAM provider that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2. This version of RBS is available at http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388). Be aware that this is the only version of RBS that is supported by SharePoint Foundation 2010. Earlier versions are not supported. Third-party RBS providers can also be used with the RBS APIs to create a BLOB storage solution that is compatible with SharePoint Foundation 2010.
In SharePoint Foundation 2010, site collection backup and restore and site import or export will download the file contents and upload them back to the server regardless of which RBS provider is being used. However, the FILESTREAM provider is the only provider that is currently supported for SharePoint 2010 Products farm database backup and restore operations.
When RBS is implemented, SQL Server itself is regarded as an RBS provider. You will encounter this factor when you migrate content into and out of RBS.
If you plan to store BLOB data in an RBS store that differs from your SharePoint Foundation 2010 content databases, you must run SQL Server 2008 with SP1 and Cumulative Update 2. This is true for all RBS providers.
The FILESTREAM provider that is recommended for upgrading from stand-alone installations of Windows SharePoint Services 3.0 that have content databases that are over 4 gigabytes (GB) to SharePoint Foundation 2010 associates data locally with the current content database, and does not require SQL Server Enterprise Edition.
Important:
RBS does not enable any kind of direct access to any files that are stored in Microsoft SharePoint 2010 Products. All access must occur by using SharePoint 2010 Products only.
In a stand-alone installation of Windows SharePoint Services 3.0, content databases are stored in Windows Internal Database and have no size limitations. Conversely, in SharePoint Foundation 2010, the content databases are stored in SQL Server 2008 Express and have a maximum size of 4 GB per database.
SQL Server 2008 R2 Express supports databases that are as large as 10 GB. If your installation includes databases that are larger than 4 GB but smaller than 10 GB, we recommend that you upgrade to SQL Server 2008 R2 Express for your content database storage solution. SQL Server 2008 R2 Express is a free upgrade that you can download and install from http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388).
If you are upgrading from Windows SharePoint Services 3.0 and have content databases that are 10 GB or larger, you must implement RBS. Or, you can use a standard or enterprise edition of Microsoft SQL Server 2008 or .
For additional guidance about how to upgrade from Windows SharePoint Services 3.0 to SharePoint Foundation 2010 together with RBS, see Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage) (http://technet.microsoft.com/library/393810e0-a520-4bd4-82b5-b858bee46b1a(Office.14).aspx).
-
See Also
FILESTREAM Overview (http://go.microsoft.com/fwlink/?LinkID=166020&clcid=0x409)
FILESTREAM Storage in SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkID=165746&clcid=0x409)
Remote BLOB Store Provider Library Implementation Specification (http://go.microsoft.com/fwlink/?LinkID=166066&clcid=0x409)
-
-
Plan for remote BLOB storage (RBS) (SharePoint Foundation 2010)
By default, Microsoft SQL Server stores binary large object (BLOB) data in its databases. As a database’s usage increases, the total size of the BLOB data that is stored in it can expand quickly and grow larger than the total size of the document metadata and other structured data that is stored in the database. BLOB data consumes large amounts of file space and uses server resources that are optimized for database access patterns instead of for the storage of large files.
Remote BLOB Storage (RBS) is a library API set that is incorporated as an add-on feature pack for Microsoft SQL Server. It can be run on the local server running Microsoft SQL Server 2008 R2, SQL Server 2008 or SQL Server 2008 R2 Express. To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise edition. RBS is designed to move the storage of BLOBs from database servers to commodity storage solutions. RBS saves significant space, conserves expensive server resources, and provides a standardized model for applications to access BLOB data. In Microsoft SharePoint Foundation 2010, RBS can be used for content databases only.
For more background information about RBS, including a discussion about the FILESTREAM provider, see Overview of Remote BLOB Storage (SharePoint Foundation 2010).
RBS can provide the following benefits:
BLOB data can be stored on less expensive storage devices that are configured to handle simple storage.
The administration of the BLOB storage is controlled by a system that is designed specifically to work with BLOB data.
Database server resources are freed for database operations.
These benefits are not free. Before you implement RBS with SharePoint Foundation 2010, you should evaluate whether these potential benefits override the costs and limitations of implementing and maintaining RBS. This article describes this evaluation process.
In this article:
-
Review the environment
To start your analysis of RBS, review the size of the content databases. If the content database sizes meet the criteria for a RBS recommendation, you should then consider what kind of content is being accessed and how it is being used.
-
Content database sizes
You can expect to benefit from RBS in the following cases:
The content databases are larger than 500 gigabytes (GB).
The BLOB data files are larger than 256 kilobytes (KB).
The BLOB data files are at least 80 KB and the database server is a performance bottleneck. In this case, RBS reduces the both the I/O and processing load on the database server.
Although the presence of many small BLOBs can create some decrease in performance, the cost of storage is usually the most important consideration when you evaluate RBS. The predicted decrease in performance is usually an acceptable trade-off for the cost savings in storage hardware.
In the case of SharePoint Foundation 2010, consider implementing RBS if you want to remain on a free version of Microsoft SQL Server, and you estimate that the databases will be larger than 4 GB. If you do not expect that the content databases will grow to 4 GB, we do not recommend that you implement RBS.
Note:
If you are upgrading from Windows SharePoint Services 3.0 to SharePoint Foundation 2010, you should read Upgrading from a stand-alone installation of Windows SharePoint Services 3.0 to SharePoint Foundation 2010 when content databases exceed 4 GB (Remote BLOB Storage) (http://technet.microsoft.com/library/393810e0-a520-4bd4-82b5-b858bee46b1a(Office.14).aspx) for additional upgrade advice.
By default, Microsoft SharePoint Foundation 2010 is installed together with Microsoft SQL Server 2008 Express. SQL Server 2008 Express has a 4 GB size limit for any database. You can immediately extend the supported size of the content databases by installing Microsoft SQL Server 2008 R2 Express, which supports databases up to 10 GB. SQL Server 2008 R2 Express is a free download that is available at http://go.microsoft.com/fwlink/?LinkID=189418 (http://go.microsoft.com/fwlink/?LinkID=189418).
The remainder of this section assumes that you will install SQL Server 2008 R2 Express to support SharePoint Foundation 2010 databases. In this case, if you expect that the content databases will be 10 GB or larger, consider the following options:
If the content databases will be up to 16 GB and you do not expect that they contain more than 10 GB of metadata, you should implement RBS. In this case, RBS lets you continue to use a free version of SQL Server. In making this recommendation, we assume that when you migrate a 16 GB content database to RBS, the metadata does not exceed 10 GB.
If the content databases are larger than 16 GB, you must purchase Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3 to support the databases instead of remaining on a free version of SQL Server.
RBS is most beneficial in systems that store very large files, such as digital media. RBS is typically implemented in environments in which large stored files are infrequently accessed, such as an archive. If this situation describes your environment, you should consider implementing RBS.
If you are storing many small (less than 256 KB) files that are frequently accessed by many users, you might experience increased latency on sites that have many small files that are stored in RBS. Increased latency is one cost factor that you should consider when you evaluate RBS for your storage solution. However, it is unlikely to be the strongest consideration. The amount of increased latency is also related to the RBS provider that you use.
-
-
Evaluate provider options
RBS requires a provider that connects the RBS APIs and SQL Server. Microsoft SQL Server 2008 Express and Microsoft SQL Server 2008 R2 Express include the FILESTREAM provider.
Important:
RBS can be run on the local server running Microsoft SQL Server 2008 R2, SQL Server 2008 or SQL Server 2008 R2 Express. To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise edition. SharePoint Foundation 2010 requires you to use the version of RBS that is included with the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. Earlier versions of RBS will not work with SharePoint Foundation 2010. In addition, RBS is not supported in SQL Server 2005.
BLOBs can be kept on commodity storage such as direct-attached storage (DAS) or network attached storage (NAS), as supported by the provider. The FILESTREAM provider is supported by SharePoint Foundation 2010 when it is used on local hard disk drives only. You cannot use RBS with FILESTREAM on remote storage devices, such as NAS.
The following table summarizes FILESTREAM benefits and limitations.
Operational requirement
RBS with FILESTREAM
RBS without FILESTREAM
SQL Server integrated backup and recovery of the BLOB Store
Yes
Yes
Scripted migration to BLOBs
Yes
Yes
Supports mirroring
No
No
Log shipping
Yes
Yes, with provider implementation
Database snapshots
No1
No1
Geo replication
Yes
No
Encryption
NTFS only
No
Network Attached Storage (NAS)
Not supported by SharePoint 2010 Products
Yes, with provider implementation
1If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots.
If FILESTREAM is not a practical provider for your environment, you can purchase a supported third-party provider. In this case, you should evaluate the following criteria when shopping for a provider:
Backup and restore capability
Tested disaster recovery
Deployment and data migration
Performance impact
Long-term administrative costs
Important:
We do not recommend that you develop your own provider unless you are an independent software vendor (ISV) that has significant development experience in designing storage solutions.
-
Plan for business continuity management (SharePoint Foundation 2010)
Business continuity management consists of the business decisions, processes, and tools you put in place in advance to handle crises. A crisis might affect your business only, or be part of a local, regional, or national event.
Features of Microsoft SharePoint Foundation 2010 are likely to be part of your business continuity management strategy, but your overall plan should be much more comprehensive and include the following elements:
Clearly documented procedures.
Offsite storage of key business records.
Clearly designated contacts.
Ongoing staff training, including practices and drills.
Offsite recovery mechanisms.
In this article:
-
Business continuity management capabilities
Microsoft SharePoint Foundation 2010 includes the following capabilities that support business continuity management.
Versioning Users can lose data by overwriting a document. With versioning, users can keep multiple versions of the same document in a document library. In the event of an unwanted change, an overwritten document, or document corruption, the previous version can easily be restored by the user. When versioning is enabled, users can recover their data themselves.
For more information, see Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010).
Recycle Bin SharePoint Foundation 2010 includes a two-stage Recycle Bin. Users who have the appropriate permissions can use the first-stage Recycle Bin to recover documents, list items, lists, and document libraries that have been deleted from a site. Site collection administrators can use the second-stage Recycle Bin, also called the Site Collection Recycle Bin, to recover items that have been deleted from the first-stage Recycle Bin. When the first-stage Recycle Bin is enabled, users can recover their data themselves.
For more information, see Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010).
Backup and recovery You can use Windows PowerShell cmdlets or the SharePoint Central Administration Web site to back up and recover farms, databases, Web applications, and site collections. There are also many external and third-party tools that you can use to back up and recover data. For more information, see Plan for backup and recovery (SharePoint Foundation 2010).
Availability No single feature provides availability within a SharePoint Foundation 2010 environment. You can choose among many approaches to improve availability, including the following:
Fault tolerance of components and the network.
Redundancy of server roles and servers within a farm.
For more information about availability, see Plan for availability (SharePoint Foundation 2010).
Disaster recovery No single feature provides disaster recovery within a SharePoint Foundation 2010 environment. You can choose among many approaches to improve availability when a data center goes offline, including the following:
Offsite storage of backups, both within and outside your region.
Shipping images of servers to offsite locations.
Running multiple data centers, but serving data only through one, keeping the others available on standby.
For more information about disaster recovery, see Plan for disaster recovery (SharePoint Foundation 2010).
-
Service level agreements
Business continuity management is a key area in which IT groups offer service level agreements (SLAs) to set expectations with customer groups. Many IT organizations offer various SLAs that are associated with different chargeback levels.
The following list describes common features of business continuity management SLAs:
Versioning
Whether offered.
Amount of space allocated.
Recycle Bins
Whether offered.
Amount of space allocated for the first-stage Recycle Bin and second-stage Recycle Bin.
Length of time that items are held before they are permanently deleted in each Recycle Bin.
Additional charges for recovering items that have been permanently deleted from the second-stage Recycle Bin.
Backup and recovery
Backup and recovery SLAs usually identify objects and services that can be backed up and recovered, and the recovery time objective, recovery point objective, and recovery level objective for each. The SLA may also identify the available backup window for each object. For more information about backup and recovery SLAs, see Plan for backup and recovery (SharePoint Foundation 2010).
Recovery time objective (RTO) is the objective for the maximum time a data recovery process will take. It is determined by the amount of time the business can afford for the site or service to be unavailable.
Recovery point objective (RPO) is the objective for the maximum amount of time between the last available backup and any potential failure point. It is determined by how much data the business can afford to lose in the event of a failure.
Recovery level objective (RLO) is the objective that defines the granularity with which you must be able to recover data — whether you must be able to recover the entire farm, Web application, site collection, site, list or library, or item.
Availability
For each component within a farm that is covered by an availability plan, an availability SLA may identify availability as a percentage of uptime, often expressed as the number of nines — that is, the percentage of time that a given system is active and working. For example, a system with a 99.999 uptime percentage is said to have five nines of availability.
Note:
When calculating availability, most organizations specifically exempt or add hours for planned maintenance activities.
For more information, see Plan for availability (SharePoint Foundation 2010).
Disaster recovery
For each component within a farm that is covered by a disaster recovery plan, an SLA may identify the recovery point objective and recovery time objective. Different recovery time objectives are often set for different circumstances, for example a local emergency versus a regional emergency.
For more information, see Plan for disaster recovery (SharePoint Foundation 2010).
-
Related content
-
Plan to protect content by using recycle bins and versioning (SharePoint Foundation 2010)
Plan to use recycle bins and versioning in an environment to help users protect and recover their data. Recycle bins and versioning are key components of a business continuity strategy.
Recycle bins Users can use recycle bins to retrieve deleted objects. Microsoft SharePoint Foundation 2010 supports two stages of recycle bins, the first-stage Recycle Bin and the Site Collection — also called the second-stage — Recycle Bin. When Recycle Bins are enabled, users can restore items that are in them, including deleted files, documents, list items, lists, and document libraries.
Versioning Users can use versioning to help prevent data loss that is caused by overwriting a document. When a site owner turns on versioning in a document library or a list, the library or list keeps multiple copies of a document, item, or file. In the event of an unwanted change, an overwritten file, or document corruption, the previous version can be easily restored by the user.
In this article:
-
Protecting content by using recycle bins
SharePoint Foundation 2010 supports two stages of recycle bins, the first-stage Recycle Bin and the Site Collection, or second-stage, Recycle Bin. The recycle bins are enabled and configured at the Web application level. The recycle bins collect deleted documents and list items. When a list item is deleted, any attachments to the item are also deleted and can be restored from the Recycle Bin.
The Recycle Bins can contain multiple copies of a document that each have the same file name and source. These documents cannot be restored over an existing copy of a document. The Recycle Bins cannot be used to recover previous versions or accidental overwrites of documents — you must use versioning to enable this functionality.
The following table describes how an item is deleted and recovered from the first-stage Recycle Bin and the second-stage Recycle Bin.
When a user does this
The item is
The item can be restored by
Deletes an item
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 longer than the time limit configured for an item to be held in the Recycle Bin.
Users or site collection administrators
Deletes an item from the Recycle Bin
Held in the second-stage Recycle Bin
Site collection administrators
Turning off the Recycle Bin for a Web application empties all Recycle Bins and permanently deletes all items in them.
-
First-stage Recycle Bin
The first-stage Recycle Bin is located at the site level and is available to users who have Contribute, Design, or Full Control permissions on a site.When a user deletes an item from a Web site, the item is sent to the site’s first-stage Recycle Bin. Items located in the first-stage Recycle Bin count toward the site quota.Items remain in one of the first-stage Recycle Bins in the site until a specified time period has been reached (the default setting is 30 days).
When an item is deleted from the Recycle Bin, the item is sent to the second-stage Recycle Bin.
Note:
The time limit for the Recycle Bins applies to the total time after the item was first deleted — not the time spent in either Recycle Bin stage.
-
Second stage (Site Collection) Recycle Bin
The second-stage Recycle Bin is located at the site collection administrator level. The second-stage Recycle Bin is organized into two views: objects in the first-stage Recycle Bins of all sites in the site collection, and objects in the second-stage Recycle Bin. When an item is deleted from the first-stage Recycle Bin, it can be recovered only by a site collection administrator from the second-stage Recycle Bin.
Items remain in the second-stage Recycle Bin until a specified time period has been reached (the default setting is 30 days) or until the second-stage Recycle Bin reaches its size limit, at which time the oldest items are deleted. The time limit for the Recycle Bins applies to the total time after the item was initially deleted — not the time spent in either Recycle Bin stage.
When a second-stage Recycle Bin is enabled for a Web application, we recommend that you designate how much disk space is available to the second-stage Recycle Bin as a percentage of the quota allotted to the Web application. Items stored in the second-stage Recycle Bin do not count toward the site quota; however, the size that is specified for the second-stage Recycle Bin increases the total size of the site and the content database that hosts it. If no site quota has been set, there is no limit on the size of the second-stage Recycle Bin.
For example, if you have allotted 100 megabytes (MB) of space for the Web application, allotting a 50 percent quota for the second-stage Recycle Bin allots 50 MB for the second-stage Recycle Bin and 150 MB for the Web application as a whole. You can allot up to 100 percent for the second-stage Recycle Bin quota.
For more information about setting quotas, see
Plan for site maintenance and management (SharePoint Foundation 2010)
Create quota templates (SharePoint Foundation 2010)
For more information about how users can use the Recycle Bin in SharePoint Foundation 2010, see View, restore, or delete items in the Recycle Bin (http://go.microsoft.com/fwlink/?LinkId=90917&clcid=0x409)
For information about configuring the Recycle Bins, see Configure the Recycle Bin (SharePoint Foundation 2010).
-
-
Protecting content by using versioning
Versioning addresses the issue of losing data by overwriting a document. It allows the document library to keep multiple copies of the same document. In the event of an unwanted change, an overwrite, or a document corruption, the previous version can easily be restored by the user. Versioning can be enabled at the library or list level. Items and files can be versioned.
Before configuring versioning, be sure to read Plan for site maintenance and management (SharePoint Foundation 2010) .
For more information about configuring versioning, see Enable and configure versioning (SharePoint Foundation 2010) .
Administrators must closely manage versioning, because if sites have many versions of files and documents, the sites can become quite large. If you do not restrict the size of sites, your sites can surpass your storage capacity. Farm administrators can manage this issue by establishing service level agreements with site owners and by setting size quotas on sites. For more information about managing versioning, see Manage versioning by using quotas (SharePoint Foundation 2010).
-
Plan for backup and recovery (SharePoint Foundation 2010)
This article describes the stages involved in planning for backup and recovery, which include determining backup and recovery strategies for a Microsoft SharePoint Foundation environment and deciding which tools to use. The stages do not need to be done in the order listed, and the process may be iterative.
When you plan for how you will use backup and recovery for disaster recovery, consider common events, failures, and errors; local emergencies; and regional emergencies.
For detailed information about Microsoft SharePoint Foundation backup and recovery, see Backup and recovery overview (SharePoint Foundation 2010).
In this article:
Define business requirements
-
Define business requirements
To define business requirements, determine the following for each farm and service in the environment:
Recovery point objective (RPO) is the objective for the maximum amount of time between the last available backup and any potential failure point. It is determined by the amount of data that the business can afford to lose in the event of a failure.
Recovery time objective (RTO) is the objective for the maximum time a data recovery process will take. It is determined by the amount of time the business can afford for the site or service to be unavailable.
Recovery level objective (RLO) is the objective that defines the granularity with which you must be able to recover data — whether you must be able to recover the entire farm, Web application, site collection, site, list or library, or item.
Shorter RPO and RTO, and greater granularity of RLO, all tend to cost more.
A worksheet to help you plan your strategies for backup and recovery for your SharePoint Foundation 2010 environment can be downloaded from SharePoint 2010 Products backup and recovery planning workbook (http://go.microsoft.com/fwlink/?LinkID=184385).
-
Choose what to protect and recover in your environment
Your business requirements will help you determine which components of the environment you need to protect, and the granularity with which you need to be able to recover them.
The following table lists components of a SharePoint environment that you might decide to protect, and the tools that can be used to back up and recover each component.
Component
SharePoint backup
Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2
System Center Data Protection Manager (DPM) 2010
File system backup
Farm
Yes
Yes6
Service applications
Yes
Web application
Yes
Content databases
Yes
Yes
Yes
Site collection
Yes1, 2
Yes1, 2
Yes1, 2
Site
Yes2
Yes2
Yes
Document library or list
Yes2
Yes2
Yes
List item or document
Yes
Content stored in remote BLOB stores
Yes3
Yes3
Yes3
Customizations deployed as solution packages
Yes7
Yes7
Yes6, 7
Changes to Web.config made by using Central Administration or an API
Yes
Yes
Yes4
Configuration settings (SharePoint)
Yes2, 8
Yes2, 8
Yes 2, 9
Customizations not deployed as solution packages
Yes. Files can be recovered if protected as files.4, 5
Yes
Changes to Web.config not made by using Central administration or an API
Yes4
Yes
IIS configurations not set through SharePoint
Yes5
Yes
SQL Server Reporting Services databases
Yes
Yes
1Farm-level and database-level backup and restore can be used for site collection recovery if a single site collection is stored in a database.
2Farm-level and database-level backups can be used with SharePoint Foundation unattached database recovery to restore site collections, sites, lists, and configurations.
3Content stored in remote BLOB stores is backed up and restored with other content, as long as the Remote BLOB Storage (RBS) provider in use has this capability.
4Changes to Web.config can be backed up by using file system backup from DPM 2010.
5IIS configurations can be recovered by using a bare metal backup from DPM 2010.
6DPM 2010 can recover this item by using a combination of a bare metal backup and SharePoint Foundation backup. It cannot be backed up and recovered as an object.
7Fully-trusted solution packages are stored in the configuration database, and sandboxed solutions are stored in content databases. They can be recovered as part of farm or content database recovery.
8Configuration settings can be recovered from farm-level backups. For more information, see Restore a farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/f7fd691f-bcf0-4b21-8bb6-d443be711f1e(Office.14).aspx).
9The Central Administration content database and the configuration database for a SharePoint Foundation 2010 farm can be recovered but only as part of a full-farm recovery to the same farm, with the same computers.
Note
You can register SharePoint Foundation 2010 with Windows Server Backup by using the stsadm.exe -o -registerwsswriter operation to configure the Volume Shadow Copy Service (VSS) writer for SharePoint Foundation. Windows Server Backup then includes SharePoint Foundation 2010 in server-wide backups. When you restore from a Windows Server backup, you can select Microsoft SharePoint Foundation (no matter which version of SharePoint 2010 Products is installed), and all components reported by the VSS writer forSharePoint Foundation 2010 on that server at the time of the backup will be restored.
Windows Server Backup is recommended only for use with for single-server deployments.
From within a content database, you can recover site collections, sites, lists and libraries.
Backup and recovery tools provide different levels of recovery for content within a content database. Recovering an object from within a content database is always more complex than recovering an entire content database.
-
Protecting customizations
Customizations to SharePoint sites can include:
Master pages, page layouts and cascading style sheets. These objects are stored in the content database for a Web application.
Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions.
Third-party solutions and their associated binary files and registry keys, such as IFilters.
Changes to standard XML files.
Custom site definitions (Webtemp.xml).
Changes to the Web.config file.
How customizations are deployed, and how changes are made to the Web.config file, have a significant effect on which tools can be used to back up and recover customizations. To provide the greatest opportunity for recovery, we recommend that you deploy customizations by using solution packages and make changes to the Web.config file by using Central Administration or the SharePoint APIs and object model.
Workflows are a special case of customizations that you can back up and recover. Make sure that your backup and recovery plan addresses any of the following scenarios that apply to your environment:
Declarative workflows, such as those created in Microsoft SharePoint Designer 2010, are stored in the content database for the site collection to which they are they are deployed. Backing up the content database protects these workflows.
Custom declarative workflow actions have components in the following three locations:
a. The Visual Studio assemblies for the Activities are stored in the global assembly catalog (GAC).
b. The XML definition files (.ACTIONS files) are stored in the 14\TEMPLATE\{LCID}\Workflow directory.
c. An XML entry to mark the activity as an authorized type is stored in the Web.config file for the Web applications in which it is used.
If your farm workflows use custom actions, you should use a file backup system to protect these files and XML entries. Similar to SharePoint Foundation features such as Web parts and event receivers, these files should be reapplied to the farm as needed after recovery.
Workflows that depend on custom code, such as those that are created by using Visual Studio, are stored in two locations. The Visual Studio assemblies for the workflow are stored in the global assembly catalog (GAC), and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Foundation features such as Web parts and event receivers. If the workflow was installed as part of a solution package, backing up the content database protects these workflows.
If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must back up both site collections to protect the workflow. This includes workflows that write to a history list or other custom list in another site collection. Performing a farm backup is sufficient to back up all site collections in the farm and all workflows that are associated with them.
Workflows that are not yet deployed must be backed up and restored separately like any other data file. When you are developing a new workflow but have not yet deployed it to the SharePoint Foundation farm, make sure that you back up the folder where you store your workflow project files by using Windows Backup or another file system backup application.
-
Protecting service applications
Service applications in a SharePoint Foundation environment can be made up of both service settings and one or more databases, or just service settings. You cannot restore a complete service application by restoring the database only; however, you can restore the databases for a service application and then reprovision the service application. For more information, see Restore a service application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/8fbb74e0-90e2-4143-8e16-3fe902a7e5c9(Office.14).aspx).
-
Protecting SQL Server Reporting Services databases
SharePoint Foundation backup and recovery does not include SQL Server Reporting Services databases. You must use SQL Server tools. For more information, see Backup and Restore Operations for a Reporting Services Installation (http://go.microsoft.com/fwlink/?LinkId=186642).
-
-
Choose tools
To choose the right tools for backup and recovery, you need to determine whether you can meet the continuity requirements you have set for your business within your budget for time and resources.
Key factors to consider when choosing tools include:
Speed of backup: Can the tool perform within the maintenance window for your databases? You should test any backup system to ensure that it meets your needs on your hardware.
Completeness of recovery.
Granularity of objects that can be recovered.
Backup type supported (full, differential, or incremental).
Complexity of managing the tool.
The following table compares the type of backup and size of farm that can be backed up in a six-hour window for backup and recovery tools available from Microsoft.
Tool
Backup type
Size of backup completed in six hours1
SharePoint farm backup and recovery
Full, differential
600 GB
SQL Server
Full, differential
600 GB
System Center Data Protection Manager
Incremental
Terabytes
1Backup size was determined by backing up a system that totals the specified size on the test hardware listed in the following section.
Note:
The SharePoint Foundation and SQL Server backups were performed with backup compression turned on.
-
Test hardware
The following table lists the hardware used in the tests that determined the size of backup that could be completed in a six-hour window.
Component
Description
Processor
64-bit dual processor, 3 GHz
RAM
8 GB
Disk
2 terabyte NTFS file system-formatted partition
Network
100 megabits per second (Mbps) or faster connection between client computers and server
Network share
Network share with 1.25 terabytes free space
Note:
The upper size limit for performing SharePoint Foundation 2010 site collection backups is 85 GB.
For detailed information about the backup and recovery systems that can be used with Microsoft SharePoint Foundation, see the following resources:
Backup and recovery overview (SharePoint Foundation 2010)
Backing Up and Restoring Databases in SQL Server (http://go.microsoft.com/fwlink/?LinkID=186643)
Data Protection Manager 2010 Release Candidate Overview (http://go.microsoft.com/fwlink/?LinkID=186655)
-
-
Determine strategies
Based on your business requirements, recovery needs, and the tools you have chosen, determine and document the backup and recovery strategies for your environment.
It is not uncommon for IT departments that support SharePoint Foundation environments to decide to use more than one tool to protect the environment, as they determine the strategies that they will use.
For example, in an environment with databases that are managed by DBAs, the strategies in the following list might be employed:
All databases are backed up by SQL Server. The backup interval that is set for each database is based on the following:
The business impact of the content or service.
The standard rate of change for the database.
The effect on performance that the backup has on the environment.
Small, rapidly changing, very high-business-impact content databases are additionally protected by SQL Server database snapshots that are stored on a separate physical disk. Only one snapshot is stored per database, and snapshots are discarded regularly, so that the effect on performance is minimized. The snapshot interval that is set for each database is based on the following:
The business impact of the content or service.
The standard rate of change for the database.
The effect on performance that the snapshot has on the environment.
The amount of space required to store the snapshot.
Recovering from a snapshot is faster than standard recovery because a snapshot, along with its underlying database, can be treated by SharePoint Foundation as an unattached database. However, the process of creating snapshots can decrease the performance of the underlying database. We recommend that the effect that snapshots have on the performance of your system be tested before they are implemented, and that snapshots be discarded regularly to reduce the space required.
Note:
If you are using RBS, and the RBS provider that you are using does not support snapshots, you cannot use snapshots for backup. For example, the SQL FILESTREAM provider does not support snapshots.
SharePoint Foundation backup is used to protect service applications. The backup interval is based on the following:
The business impact of the service.
The standard rate of change for the database.
The effect on performance that the backup has on the database.
All restore operations are performed through SharePoint Foundation. The choice of which restore system to use is determined by the type of backup that is available and the object being restored.
Other tools should be part of your business continuity strategy. Consider how you will use Recycle Bins and versioning in site collections throughout the environment. For more information, see Plan for business continuity management (SharePoint Foundation 2010).
-
Plan for enhanced backup and recovery performance
As you plan your backup and recovery strategy, consider the following recommendations to help you decrease the effect of backup and recovery on system performance.
By design, most backup jobs consume as many I/O resources as they can to finish the job in the available time for maintenance; therefore, you might see disk queuing and you might see that all I/O requests come back more slowly than usual. This is typical and should not be considered a problem.
-
Follow recommendations for configuring SQL Server and storage
Follow the general recommendations for configuring SQL Server and storage for a SharePoint Foundation environment. For more information, see SQL Server and storage (SharePoint Foundation 2010).
-
Minimize latency between SQL Server and the backup location
In general, it is best to use a local disk, not a network drive, for backups. If you are backing up multiple servers, you may want to have a directly connected computer that both servers can write to. Network drives that have 1 millisecond or less latency between them and the computers that are running SQL Server will perform well. If your farm has multiple servers in it (including the computer that is running SQL Server), you must use UNC network paths for the SharePoint farm backup location.
-
Avoid processing conflicts
Do not run backup jobs during times in which users require access to the system.
To avoid I/O bottlenecks, perform the main backup to a separate disk, and only then copy to tape.
Consider staggering backups so that not all databases are backed up at the same time.
SharePoint Foundation backups use SQL Server backups. When using compression with your backups, be mindful not to overwhelm SQL Server. For example, some third-party backup tools compress data during backup, which can disrupt SQL Server performance. There are tools available to throttle the compression processes and control the effect on SQL Server.
-
Follow SQL Server backup and restore optimization recommendations
If you are running SQL Server 2008 Enterprise, we recommend that you use backup compression. For more information, see Backup Compression (SQL Server) (http://go.microsoft.com/fwlink/?LinkId=179525).
If you are using SQL Server backups, use a combination of full, differential, and transaction log backups for the full recovery model to minimize recovery time. Differential database backups are usually faster to create than full database backups, and they reduce the amount of transaction log required to recover the database.
If you are using the full recovery model in SQL Server 2008, we recommend that you use the truncate option during backup to avoid maintenance issues.
For detailed recommendations about how to optimize SQL Server backup and restore performance, see Optimizing Backup and Restore Performance in SQL Server (http://go.microsoft.com/fwlink/?LinkId=126630).
-
Ensure sufficient write performance on the backup drive
Carefully consider whether to use redundant array of independent disks (RAID) on your disk backup device. For example, RAID 5 has low write performance, approximately the same speed as for a single disk. (This is because RAID 5 maintains parity information.) Using RAID 10 for a backup device may provide faster backups. For more information about how to use RAID with backups, see Configure RAID for maximum SQL Server I/O throughput (http://go.microsoft.com/fwlink/?LinkId=126632).
-
-
Related content
-
Backup and recovery overview (SharePoint Foundation 2010)
This article describes the backup architecture and recovery processes that are available in Microsoft SharePoint Foundation 2010, including farm and granular backup and recovery, and recovery from an unattached content database. Backup and recovery operations can be performed through the user interface or through Windows PowerShell cmdlets. Built-in backup and recovery tools may not meet all the needs of your organization.
In this article:
-
Backup and recovery scenarios
Backing up and recovering data supports many business scenarios, including the following:
Recovering unintentionally deleted content that is not protected by the Recycle Bin or versioning.
Moving data between installations as part of a hardware or software upgrade.
Recovering from an unexpected failure.
-
Backup architecture
SharePoint Foundation 2010 provides two backup systems: farm and granular.
-
Farm backup architecture
The farm backup architecture in SharePoint Foundation 2010 starts a Microsoft SQL Server database backup of content and service application databases and also writes configuration content to files.
The following illustration shows the farm backup system.

Both full and differential backups are supported. Full backups create a new backup of the complete system. Differential backups create a backup of all the data that is stored in databases that has changed since the last full backup.
The farm backup system is organized hierarchically. The components in a farm that can be selected for backup include the following:
Farm The farm is the highest-level object. You can select from the following options when you perform a farm backup:
Content and configuration data (default)
The whole server farm is backed up. This includes settings from the configuration database.
Configuration only
Configuration database settings are backed up so that you can apply configurations across farms. For more information, see Configuration-only backup use and benefits later in this article.
Web application Within a Web application, you can select one or more of the content databases to back up.
A Web application backup includes the following:
Application pool name and application pool account
Authentication settings
General Web application settings such as alerts and managed paths
Internet Information Services (IIS) binding information, such as the protocol type, host header, and port number
Changes to the Web.config file that have been made through the object model or Central Administration
Note:
Changes to the Web.config file that have been made to support claims-based authentication that uses forms-based authentication are not included in backups, because those changes are made manually. For more information, see Considerations for using farm backups later in this article.
Sandboxed solutions
For recommendations about how to protect these settings, see Plan for backup and recovery (SharePoint Foundation 2010).
Important:
Backups of service applications do not include the related proxy. To back up both the service application and the service application proxy, you must either back up the farm or perform two consecutive backups, selecting the service application in one backup, and selecting the associated service application proxy in the second backup.
Many service application databases cannot be backed up individually from SharePoint Foundation 2010. To back up service application databases only, you must use SQL Server backup.
Proxies for service applications that are not shared.
Shared Services Shared services require both a service application and a service application proxy to run. If you select the Shared Services node, all of the service applications and the related service application proxies on the farm will be backed up.
Note:
The backup hierarchy enables you to select individual service applications and service application proxies to back up. However, when you select one or all service applications, or one or all proxies, the related objects are not backed up by default. To back up both parts of a specific service, you must either select the Shared Services node or perform two consecutive backups, selecting the service application in one backup, and selecting the associated service application proxy in the second backup.
Note
Some settings in the SharePoint Foundation environment are not included in a farm backup. They include the following settings that are stored on Web servers:
A configuration-only backup extracts and backs up the configuration settings from a configuration database. By using built-in tools, you can back up the configuration of any configuration database, whether it is currently attached to a farm or not. For detailed information about how to back up a configuration, see Back up a farm configuration (SharePoint Foundation 2010) (http://technet.microsoft.com/library/6d006882-8dc4-4e28-9a47-9d2d592437dc(Office.14).aspx).
A configuration backup can be restored to the same — or any other — server farm. When a configuration is restored, it will overwrite any settings present in the farm that have values that are set in the configuration backup. If any settings present in the farm are not contained in the configuration backup, they will not be changed. For detailed information about how to restore a farm configuration, see Restore a farm configuration (SharePoint Foundation 2010) (http://technet.microsoft.com/library/25cffd9e-d1d5-43ef-86c2-e2d966a1f1e8(Office.14).aspx).
Note:
Web application and service application settings are not included in a configuration backup. You can use Windows PowerShell cmdlets to document and copy settings for service applications. For more information, see Document farm configuration settings (SharePoint Foundation 2010) (http://technet.microsoft.com/library/dd025503-84ec-40b8-aab3-a58b814d162f(Office.14).aspx) and Copy configuration settings from one farm to another (SharePoint Foundation 2010) (http://technet.microsoft.com/library/6635b76f-ad53-4231-9fda-f111f64dcadb(Office.14).aspx).
Situations in which you might want to restore a configuration from one farm to another farm include the following:
Replicating a standardized farm configuration to be used throughout an environment.
Moving configurations from a development or test environment to a production environment.
Moving configurations from a stand-alone installation to a farm environment.
Configuring a farm to serve as part of a standby environment.
SharePoint Foundation stores the following kinds of settings in the configuration-only backup:
Antivirus
Information rights management (IRM)
Outbound e-mail settings (only restored when you perform an overwrite).
Customizations deployed as trusted solutions
Diagnostic logging
Consider the following before you use farm backups:
There is no built-in scheduling system for backups. To schedule a backup, we recommend that you create a backup script by using Windows PowerShell, and then use Windows Task Scheduler to run the backup script on a regular basis.
We do not recommend that you use IIS metabase backup to protect IIS settings. Instead, document all IIS configurations for each Web server by using a tool that provides the configuration monitoring you want, such asMicrosoft System Center Configuration Manager 2010.
SharePoint Foundation 2010 backup and recovery can be run together with SQL Server Enterprise features such as backup compression and transparent data encryption.
If you are running SQL Server Enterprise, we strongly recommend that you use backup compression. For more information about backup compression, see Backup Compression (SQL Server) (http://go.microsoft.com/fwlink/?LinkID=129381).
If you decide to run databases with transparent data encryption, you must manually back up the key and restore the key — SharePoint Foundation 2010 backup and restore will not remind you about the key. For more information about transparent data encryption, see Understanding Transparent Data Encryption (TDE) (http://go.microsoft.com/fwlink/?LinkID=129384).
If a content database is set to use the SQL FILESTREAM remote BLOB storage (RBS) provider, the RBS provider must be installed both on the database server that is being backed up and on the database server that is being recovered to.
SharePoint Foundation 2010 backup does not protect:
Changes to the Web.config file on Web servers that are not made through Central Administration or the object model.
Customizations to a site that are not deployed as part of a trusted or sandboxed solution.
If you are sharing service applications across farms, be aware that trust certificates that have been exchanged are not included in farm backups. You must back up the certificate store separately or keep the certificates in a separate location. When you restore a farm that shares a service application, you must import and redeploy the certificates and then re-establish any inter-farm trusts.
For more information, see Exchange trust certificates between farms (SharePoint Foundation 2010) (http://technet.microsoft.com/library/679d334b-913d-49b3-b086-66a60093b261(Office.14).aspx).
When you restore a farm or Web application that is configured to use any kind of claims-based authentication, duplicate or additional providers may appear to be enabled. If duplicates appear, you must manually save each Web application zone to remove them.
Additional steps are required when you restore a farm that contains a Web application that is configured to use forms-based authentication. You must re-register the membership and role providers in the Web.config file, and then redeploy the providers. You must perform these steps whether you are restoring at the Web application level or at the farm level.
For more information, see Back up a Web application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/cb1fa2d2-5dd7-4640-a1b5-99c10561d9ef(Office.14).aspx), Plan authentication methods (SharePoint Foundation 2010) and Configure claims authentication (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ef8c3024-26de-4d06-9204-3c6bbb95fb14(Office.14).aspx).
-
Granular backup and export architecture
The granular backup and export architecture uses Transact-SQL queries and export calls. Granular backup and export is a more read-intensive and processing-intensive operation than farm backup.
From the granular backup system, a user can back up a site collection, or export a site or list.
Note:
Workflows are not included in exports of sites or lists.
If you are running SQL Server Enterprise, the granular backup system can optionally use SQL Server database snapshots to ensure that data remains consistent while the backup or export is in progress. When a snapshot is requested, a SQL Server database snapshot of the appropriate content database is taken, SharePoint Foundation uses it to create the backup or export package, and then the snapshot is deleted. Database snapshots are linked to the source database where they originated. If the source database goes offline for any reason, the snapshot will be unavailable. For more information about database snapshots, see Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=166158).
Benefits of backing up a site collection by using a snapshot include the following:
The snapshot ensures that the data that is being read remains consistent while the operation is being performed.
Users can continue to interact with the site collection while it is being backed up from the database snapshot. This includes adding, editing, and deleting content. However, the changes that users make to the live site will not be included in the site collection backup because the backup is based on the database snapshot.
However, database snapshots can adversely affect performance. For more information about database snapshots and performance, see Limitations and Requirements of Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=166159).
You can use granular backup and export for content that is stored in a database that is configured to use the SQL FILESTREAM RBS provider.
Note:
If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots.
Note:
We do not recommend that you use SharePoint Foundation 2010 site collection backup for site collections larger than 85 GB.
The following illustration shows the granular backup and export system.

-
-
Recovery processes
SharePoint Foundation 2010 supports the following primary, built-in recovery options:
Restore from a farm backup that was created by using built-in tools, or restore from the backup of a component taken by using the farm backup system.
Restore from a site collection backup.
Connect to a content database by using the unattached content database feature, back up or export data from it, and then restore or import the data.
-
Restoring from a farm backup
Items that can be recovered from a farm backup include the following:
Farm
Content and configuration data (default)
The whole server farm is restored. This includes settings from the configuration database, and trusted solution packages.
Configuration only
Only the configuration data is restored. This overwrites any settings in the farm that have values that are set within the configuration-only backup.
Web applications
Restores Web applications.
Service applications
Restores service applications. Service application recovery can be complex because SharePoint Foundation 2010 cannot fully reconfigure service application proxies during the restore process. Service application proxies are restored, but are not put in proxy groups. Therefore, they are not associated with any Web applications. For specific information about the operations involved in restoring specific service applications, see Restore a service application (SharePoint Foundation 2010) (http://technet.microsoft.com/library/8fbb74e0-90e2-4143-8e16-3fe902a7e5c9(Office.14).aspx).
Content databases
When content databases are restored, the sandboxed solutions associated with the related site collections are also restored.
-
Restoring as new versus restoring as overwrite
By default, SharePoint Foundation 2010 recovery restores any object as a new instance of the object, instead of overwriting any existing instances with the same name.
When you restore a farm or object as new, the following objects will not work without adjustments, because all GUIDs for objects are assigned new values:
Farm. When you restore a farm as new, you must do the following:
Re-create alternate access mapping settings. SharePoint Foundation 2010 recovery only restores the Default zone of the Web application.
Re-associate service application proxies with proxy groups because service application proxies are not assigned to proxy groups when restored. All Web applications will be associated with the default proxy group. You must associate Web applications with other proxy groups if you want to do that.
Web application.
If the Web application name and URL that you provide match a Web application name and URL that already exist in the farm, SharePoint Foundation 2010 recovery combines them.
If you do not want to combine Web applications, you must rename the Web application when you restore it as new.
When you restore a Web application as new in the same environment but do not combine Web applications, many other parameters and objects must also be changed. For example, you may have to provide different database file paths and different database names.
Service applications and service application proxies
If you recover a service application and also recover the related service application proxy, you must associate the service application proxy with a proxy group.
If you recover a service application and do not also recover the related service application proxy, you must re-create the service application proxy.
Note:
You cannot restore a service application as new in the same farm. You can restore a service application as new in another farm.
When you restore an object and overwrite the existing object, no changes are necessary.
-
Restoring from a site collection backup
Only site collections can be recovered from a site collection backup.
-
Recovering from an unattached content database
SharePoint Foundation 2010 provides the ability to connect to, and back up from, a content database that is attached to an instance of SQL Server but is not associated with a local SharePoint Web application. Unattached databases that you can connect to include read-only content databases that have been restored from any supported backup technology and SQL Server database snapshots of content databases.
Recovery is the following two-stage process:
1. Back up or export the object from the unattached content database.
2. Restore or import the output of the prior step into SharePoint Foundation 2010.
The following items can be backed up or exported from an unattached database by using granular backup and export, and then restored:
Site collection
Back up by using site collection backup, and then recover by using a site collection restore.
Site
Export, and then import.
Lists and libraries
Export, and then import.
You can use import to recover content that you backed up from a database configured to use the SQL FILESTREAM RBS provider. The recovered content will be stored by SharePoint Foundation 2010 using the currently defined storage provider for that content database — that is, if the content database is not set to use RBS, the data will be stored in the content database; if the content database is set to use RBS, the data will be stored in RBS.
-
-
Related content
-
Plan for availability (SharePoint Foundation 2010)
This article describes key decisions in choosing availability strategies for a Microsoft SharePoint Foundation 2010 environment.
As you carefully review your availability requirements, be aware that the higher the level of availability and the more systems that you protect, the more complex and costly your availability solution is likely to be.
Not all solutions in an organization are likely to require the same level of availability. You can offer different levels of availability for different sites, different services, or different farms.
In this article:
Choosing an availability strategy and level
Redundancy and failover between closely located data centers configured as a single farm (“stretched” farm)
-
Availability overview
Availability is the degree to which a SharePoint Foundation environment is perceived by users to be available. An available system is a system that is resilient — that is, incidents that affect service occur infrequently, and timely and effective action is taken when they do occur.
Availability is part of business continuity management (BCM), and is related to backup and recovery and disaster recovery. For more information about these related processes, see Plan for backup and recovery (SharePoint Foundation 2010) and Plan for disaster recovery (SharePoint Foundation 2010).
Note:
When calculating availability, most organizations specifically exempt or add hours for planned maintenance activities.
One of the most common measures of availability is percentage of uptime expressed as number of nines — that is, the percentage of time that a given system is active and working. For example, a system with a 99.999 uptime percentage is said to have five nines of availability.
The following table correlates uptime percentage with calendar time equivalents.
Acceptable uptime percentage
Downtime per day
Downtime per month
Downtime per year
95
72.00 minutes
36 hours
18.26 days
99 (two nines)
14.40 minutes
7 hours
3.65 days
99.9 (three nines)
86.40 seconds
43 minutes
8.77 hours
99.99 (four nines)
8.64 seconds
4 minutes
52.60 minutes
99.999 (five nines)
0.86 seconds
26 seconds
5.26 minutes
If you can make an educated guess about the number of total hours downtime you are likely to have per year, you can use the following formulas to calculate the uptime percentage for a year, a month, or a week:
-
Costs of availability
Availability is one of the more expensive requirements for a system. The higher the level of availability and the more systems that you protect, the more complex and costly an availability solution is likely to be. When you invest in availability, costs include the following:
Additional hardware and software, which can increase the complexity of interactions among software applications and settings.
Additional operational complexity.
The costs of improving availability should be evaluated in conjunction with your business needs — not all solutions in an organization are likely to require the same level of availability. You can offer different levels of availability for different sites, different services, or different farms.
Availability is a key area in which information technology (IT) groups offer service level agreements (SLAs) to set expectations with customer groups. Many IT organizations offer various SLAs that are associated with different chargeback levels.
-
Determining availability requirements
To gauge your organization’s tolerance of downtime for a site, service, or farm, answer the following questions:
If the site, service, or farm becomes unavailable, will employees be unable to perform their expected job responsibilities?
If the site, service, or farm becomes unavailable, will business and customer transactions be stopped, leading to loss of business and customers?
If you answered yes to either of these questions, you should invest in an availability solution.
-
-
Choosing an availability strategy and level
You can choose among many approaches to improve availability in a SharePoint Foundation environment, including the following:
Improve the fault tolerance of server hardware components.
Increase the redundancy of server roles within a farm.
-
Hardware component fault tolerance
Hardware component fault tolerance is the redundancy of hardware components and infrastructure systems such as power supplies at the server level. When planning for hardware component fault tolerance, consider the following:
Complete redundancy of every component within a server may be impossible or impractical. Use additional servers for additional redundancy.
Ensure that servers have multiple power supplies connected to different power sources for maximum redundancy.
In any system, we recommend that you work with hardware vendors to obtain fault-tolerant hardware that is appropriate for the system, including redundant array of independent disks (RAID) arrays.
-
Redundancy within a farm
SharePoint Foundation 2010 supports running server roles on redundant computers (that is, scaling out) within a farm to increase capacity and to provide basic availability.
The capacity that you require determines both the number of servers and the size of the servers in a farm. After you have met your base capacity requirements, you may want to add more servers to increase overall availability. The following illustration shows how you can provide redundancy for each server role.
Availability within a server farm

The following table describes the server roles in a SharePoint Foundation 2010 environment and the redundancy strategies that can be used for each within a farm.
Server role
Preferred redundancy strategy within a farm
Front-end Web server
Deploy multiple front-end Web servers within a farm, and use Network Load Balancing (NLB).
Application server
Deploy multiple application servers within a farm.
Database server
Deploy database servers by using clustering or high-availability database mirroring.
-
Database availability strategies
You can use Microsoft SQL Server failover clustering or SQL Server high-availability database mirroring to support availability of databases in a SharePoint Foundation environment.
-
SQL Server failover clustering
Failover clustering can provide availability support for an instance of SQL Server. A failover cluster is a combination of one or more nodes or servers, and two or more shared disks. A failover cluster instance appears as a single computer, but has functionality that provides failover from one node to another if the current node becomes unavailable. SharePoint Foundation can run on any combination of active and passive nodes in a cluster that is supported by SQL Server.
SharePoint Foundation references the cluster as a whole; therefore, failover is automatic and seamless from the perspective of SharePoint Foundation.
For detailed information about failover clustering, see Getting Started with SQL Server 2008 Failover Clustering (http://go.microsoft.com/fwlink/?LinkID=102837&clcid=0x409) and Configure availability by using SQL Server clustering (SharePoint Foundation 2010) (http://technet.microsoft.com/library/069d9586-815b-4e5d-b8f7-dbd161c10e4e(Office.14).aspx).
-
SQL Server high-availability mirroring
Database mirroring is a SQL Server technology that can deliver database redundancy on a per-database basis. In database mirroring, transactions are sent directly from a principal database and server to a mirror database and server when the transaction log buffer of the principal database is written to disk. This technique can keep the mirror database almost up to date with the principal database. SQL Server Enterprise Edition provides additional functionality that improves database mirroring performance.
For mirroring within a SharePoint Foundation farm, you must use high-availability mirroring, also known as high-safety mode with automatic failover. High-availability database mirroring involves three server instances: a principal, a mirror, and a witness. The witness server enables SQL Server to automatically fail over from the principal server to the mirror server. Failover from the principal database to the mirror database typically takes several seconds.
A change from previous versions is that SharePoint Foundation is mirroring-aware. After you have configured a database mirror instance of SQL Server, you then use SharePoint Central Administration or Windows PowerShell cmdlets to identify the failover (mirror) database server location for a configuration database, content database, or service application database. Setting a failover database location adds a parameter to the connection string that SharePoint Foundation uses to connect to SQL Server. In the event of a SQL Server time-out event, the following occurs:
1. The witness server that is configured for SQL Server mirroring automatically swaps the roles of the primary and mirror databases.
2. SharePoint Foundation automatically attempts to contact the server that is specified as the failover database.
For information about how to configure database mirroring, see Configure availability by using SQL Server database mirroring (SharePoint Foundation 2010) (http://technet.microsoft.com/library/142fc165-8f11-4509-b698-d7d44dfdbd22(Office.14).aspx).
For general information about database mirroring, see Database Mirroring (http://go.microsoft.com/fwlink/?LinkID=180597).
Note:
Databases that have been configured to use the SQL Server FILESTREAM remote BLOB store provider cannot be mirrored.
-
Comparison of database availability strategies for a single farm: SQL Server failover clustering vs. SQL Server high-availability mirroring
The following table compares failover clustering to synchronous SQL Server high-availability mirroring.
SQL Server failover clustering
SQL Server high-availability mirroring
Time to failover
Cluster member takes over immediately upon failure.
Mirror takes over immediately upon failure.
Transactional consistency?
Yes
Yes
Transactional concurrency?
Yes
Yes
Time to recovery
Shorter time to recovery (milliseconds)
Slightly longer time to recovery (milliseconds).
Steps required for failover?
Failure is automatically detected by database nodes; SharePoint Foundation 2010 references the cluster so that failover is seamless and automatic.
Failure is automatically detected by the database; SharePoint Foundation 2010 is aware of the mirror location, if it has been configured correctly, so that failover is automatic.
Protection against failed storage?
Does not protect against failed storage, because storage is shared between nodes in the cluster.
Protects against failed storage because both the principal and mirror database servers write to local disks.
Storage types supported
Shared storage (more expensive).
Can use less-expensive direct-attached storage (DAS).
Location requirements
Members of the cluster must be on the same subnet.
Principal, mirror, and witness servers must be on the same LAN (up to 1 millisecond latency roundtrip).
Recovery model
SQL Server full recovery model recommended. You can use the SQL Server simple recovery model, but the only available recovery point if the cluster is lost will be the last full backup.
Requires SQL Server full recovery model.
Performance overhead
Some decrease in performance may occur while a failover is occurring.
High-availability mirroring introduces transactional latency because it is synchronous. It also requires additional memory and processor overhead.
Operational burden
Set up and maintained at the server level.
The operational burden is larger than clustering. Must be set up and maintained for all databases. Reconfiguring after failover is manual.
-
Service application redundancy strategies
The redundancy strategy you follow for protecting service applications that run in a farm varies, depending on where the service application stores data.
-
Service applications that store data in databases
To help protect service applications that store data in databases, you must follow these steps:
1. Install the service on multiple application servers to provide redundancy within the environment.
2. Configure SQL Server clustering or mirroring to protect the data.
The following service applications store data in databases:
Business Data Connectivity service application
Application Registry service application
We do not recommend mirroring the Application Registry database, because it is only used when upgrading Windows SharePoint Services 3.0 Business Data Catolog information to SharePoint Foundation 2010.
Usage and Health Data Collection service application
Note:
We recommend that you do not mirror the Usage and Health Data Collection service application Logging database.
Microsoft SharePoint Foundation Subscription Settings service
-
-
Redundancy and failover between closely located data centers configured as a single farm (“stretched” farm)
Some enterprises have data centers that are located close to one another with high-bandwidth connections so that they can be configured as a single farm. This is called a “stretched” farm. For a stretched farm to work, there must be less than 1 millisecond latency between SQL Server and the front-end Web servers in one direction, and at least 1 gigabit per second bandwidth.
In this scenario, you can provide fault tolerance by following the standard guidance for making databases and service applications redundant.
The following illustration shows a stretched farm.
Stretched farm

-
Plan for disaster recovery (SharePoint Foundation 2010)
This article describes key decisions in choosing disaster recovery strategies for a Microsoft SharePoint Foundation 2010 environment.
In this article:
Choose a disaster recovery strategy
-
Disaster recovery overview
For the purposes of this article, we define disaster recovery as the ability to recover from a situation in which a data center that hosts SharePoint Foundation becomes unavailable.
The disaster recovery strategy that you use for SharePoint Foundation must be coordinated with the disaster recovery strategy for the related infrastructure, including Active Directory domains, Exchange Server, and Microsoft SQL Server. Work with the administrators of the infrastructure that you rely on to design a coordinated disaster recovery strategy and plan.
The time and immediate effort to get another farm up and running in a different location is often referred to as a hot, warm, or cold standby. Our definitions for these terms are as follows:
Hot standby A second data center that can provide availability within seconds or minutes.
Warm standby A second data center that can provide availability within minutes or hours.
Cold standby A second data center that can provide availability within hours or days.
Disaster recovery can be one of the more expensive requirements for a system. The shorter the interval between failure and availability and the more systems you protect, the more complex and costly a disaster recovery solution is likely to be. When you invest in hot or warm standby data centers, costs include:
Additional hardware and software, which often increase the complexity of operations between software applications, such as custom scripts for failover and recovery.
Additional operational complexity.
The costs of maintaining hot or warm standby data centers should be evaluated based on your business needs. Not all solutions within an organization are likely to require the same level of availability after a disaster. You can offer different levels of disaster recovery for different content, services, or farms — for example, content that has high impact on your business, or search services, or an Internet publishing farm.
Disaster recovery is a key area in which information technology (IT) groups offer service level agreements (SLAs) to set expectations with customer groups. Many IT organizations offer a variety of SLAs that are associated with different chargeback levels.
When you implement failover between server farms, we recommend that you first deploy and tune the core solution within a farm, and then implement and test disaster recovery.
-
Choose a disaster recovery strategy
You can choose among many approaches to provide disaster recovery for a SharePoint Foundation environment, depending on your business needs. The following examples show why companies might choose cold, warm, or hot standby disaster recovery strategies.
Cold standby disaster recovery strategy: A business ships backups to support bare metal recovery to local and regional offsite storage on a regular basis, and has contracts in place for emergency server rentals in another region.
Pros:
Often the cheapest option to maintain, operationally.
Often an expensive option to recover, because it requires that physical servers be configured correctly after a disaster has occurred.
Cons: The slowest option to recover.
Warm standby disaster recovery strategy: A business ships virtual server images to local and regional disaster recovery farms.
Pros: Often relatively inexpensive to recover, because a virtual server farm can require little configuration upon recovery.
Cons: Can be very expensive and time consuming to maintain.
Hot standby disaster recovery strategy: A business runs multiple data centers, but serves content and services through only one data center.
Pros: Often relatively fast to recover.
Cons: Can be quite expensive to configure and maintain.
Important:
No matter which disaster recovery solution you decide to implement for your environment, you are likely to incur some data loss.
-
Planning for cold standby data centers
In a cold standby disaster recovery scenario, you can recover by setting up a new farm in a new location, (preferably by using a scripted deployment), and restoring backups. Or, you can recover by restoring a farm from a backup solution such as Microsoft System Center Data Protection Manager 2007 that protects your data at the computer level and lets you restore each server individually. This article does not contain detailed instructions for how to create and recover in cold standby scenarios. For more information, see:
Restore a farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/f7fd691f-bcf0-4b21-8bb6-d443be711f1e(Office.14).aspx)
Restore customizations (SharePoint Foundation 2010) (http://technet.microsoft.com/library/8d1b2aba-edd3-4089-8255-8f3ef2b1b211(Office.14).aspx)
-
Planning for warm standby data centers
In a warm standby disaster recovery scenario, you can create a warm standby solution by making sure that you consistently and frequently create virtual images of the servers in your farm that you ship to a secondary location. At the secondary location, you must have an environment available in which you can easily configure and connect the images to re-create your farm environment.
This article does not contain detailed instructions for creating warm standby solutions. For more information about how to plan to deploy farms by using virtual solutions, see Plan for virtualization (SharePoint Foundation 2010).
-
Planning for hot standby data centers
In a hot standby disaster recovery scenario, you can set up a failover farm to provide disaster recovery in a separate data center from the primary farm. An environment that has a separate failover farm has the following characteristics:
A separate configuration database and Central Administration content database must be maintained on the failover farm.
All customizations must be deployed on both farms.
Note:
We recommend that you use scripted deployment to create the primary and failover farm by using the same configuration settings and customizations.
Updates must be applied to both farms, individually.
SharePoint Foundation content databases can be successfully asynchronously mirrored or log-shipped to the failover farm.
Note:
SQL Server mirroring can only be used to copy databases to a single mirror server, but you can log-ship to multiple secondary servers.
Service applications vary in whether they can be log-shipped to a farm. For more information, see Service application redundancy across data centers later in this article.
This topology can be repeated across many data centers, if you configure SQL Server log shipping to one or more additional data centers.
Consult with your SAN vendor to determine whether you can use SAN replication or another supported mechanism to provide availability across data centers.
The following illustration shows primary and failover farms before failover.
Primary and failover farms before failover

To provide availability across data centers for service applications, we recommend that for the services that can be run cross-farm, you run a separate services farm that can be accessed from both the primary and the secondary data centers.
For services that cannot be run cross-farm, and to provide availability for the services farm itself, the strategy for providing redundancy across data centers for a service application varies. The strategy employed depends on whether:
There is business value in running the service application in the disaster recovery farm when it is not in use.
The databases associated with the service application can be log-shipped or asynchronously mirrored.
The service application can run against read-only databases.
The following sections describe the disaster recovery strategies that we recommend for each service application. The service applications are grouped by strategy.
-
Databases that can be log-shipped or asynchronously mirrored
After a service application has been initially deployed on a secondary farm, the databases that support the following service applications can be asynchronously mirrored or log-shipped across farms:
Application Registry service application
Databases: Application Registry service
Business Data Connectivity service application
Databases: Business Data Connectivity
Usage and Health Data Collection service application
Databases: Logging
Note:
It is possible to log-ship or mirror the Logging database. However, we recommend that you do not run the Usage and Health Data Collection service on the disaster recovery farm, and that you do not mirror nor log-ship the Logging database.
-
Service applications and databases that cannot be log-shipped or asynchronously mirrored
The following service applications must be deployed on both the primary and failover farms, and cannot be log-shipped or asynchronously mirrored. For most of these service applications, we recommend that you deploy them and then verify that the failover farm has the same configuration settings as the primary farm. If configuration changes that affect the service are made on the primary farm, you must update the failover farm.
Microsoft SharePoint Foundation Subscription Settings service application
Database: Subscription Settings
Note:
Log-shipping the Subscription Settings database is not supported.
-
-
System requirements for disaster recovery
In an ideal scenario, the failover components and systems match the primary components and systems in all ways: platform, hardware, and number of servers. At a minimum, the failover environment must be able to handle the traffic that you expect during a failover. Keep in mind that only a subset of users may be served by the failover site. The systems must match in at least the following:
Operating system version and all updates
SQL Server versions and all updates
SharePoint 2010 Products versions and all updates
Although this article primarily discusses the availability of SharePoint 2010 Products, the system uptime will also be affected by the other components in the system. In particular, make sure that you do the following:
Ensure that infrastructure dependencies such as power, cooling, network, directory, and SMTP are fully redundant.
Choose a switching mechanism, whether DNS or hardware load balancing, that meets your needs.
-
Virtualization planning (SharePoint Foundation 2010)
This section contains articles that are designed to help you plan and implement a server virtualization solution for Microsoft SharePoint Foundation 2010 server farms.
In this section:
Virtualization support and licensing (SharePoint Foundation 2010)
Hyper-V virtualization requirements (SharePoint Foundation 2010)
-
Virtualization support and licensing (SharePoint Foundation 2010)
This article provides support and licensing information for using server virtualization technologies to deploy SharePoint 2010 Products in a virtual environment.
-
SharePoint 2010 Products support for virtualization
All elements of Microsoft SharePoint Foundation 2010 are fully supported when deployed in a Windows Server 2008 Hyper-V technology environment. In addition, any related or required supporting technologies are also supported.
Note:
Support for SharePoint Foundation 2010 virtualization includes third-party virtualization technologies that are hosted or hardware-based, and certified by Microsoft. For more information about certification and participating vendors, see the Server Virtualization Validation Program (SVVP) (http://go.microsoft.com/fwlink/?LinkId=125649).
-
Server virtualization using Hyper-V technology
Beginning withWindows Server 2008, server virtualization using Hyper-V has been an integral part of the operating system. Hyper-V is available with all editions of the operating system, as well as with Microsoft Hyper-V Server 2008.
We recommend using Windows Server 2008 R2 or Microsoft Hyper-V Server 2008 R2 as virtualization servers for your SharePoint 2010 Products deployment. These releases provide:
Added capabilities, such as increased virtual processor support and increased memory support for virtual machines.
Performance improvements, such as improved virtual hard drive performance and network adapter performance.
For more information, see What’s New in Hyper-V in Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=155234).
-
Operating system environment (OSE) licensing
Before you start planning for virtualization you need to determine the licensing requirements for your virtualization environment. Two types of operating system environments (OSEs) exist:
One physical operating system environment
One or more virtual operating system environment(s)
A virtual operating system environment is configured to run on a virtual (or otherwise emulated) hardware system. Use of technologies that create virtual OSEs does not change the licensing requirements for the operating system and any applications running in the OSE.
The Windows Server operation system licensing model for physical multicore processor systems is based on the number of physical processors installed on the hardware. This model extends to virtual processors configured for a virtual machine running on a virtualization server. For licensing purposes, a virtual processor is considered to have the same number of threads and cores as each physical processor on the underlying physical hardware system.
For more information about licensing requirements:
Licensing Microsoft Server Products in Virtual Environments (http://go.microsoft.com/fwlink/?LinkId=187741)
This white paper gives an overview of Microsoft licensing models for the server operating system and server applications under virtual environments.
Windows Server Virtualization Calculators (http://go.microsoft.com/fwlink/?LinkId=187742)
The Windows Server Virtualization Calculators provide two ways to estimate the number and cost of Windows Server Standard Edition, Enterprise Edition, and Datacenter Edition licenses needed for your virtualization scenarios to help you determine the most cost-effective edition of Windows Server.
Note:
Although Microsoft Hyper-V Server 2008 R2 does not require a license for the virtualization server, licensing requirements must be met for the virtual OSEs.
-
SharePoint 2010 Products licensing
Every element of a SharePoint farm that is installed on a virtual machine must comply with the licensing requirements for SharePoint Foundation 2010 as well as related and supporting technologies.
-
Hyper-V virtualization requirements (SharePoint Foundation 2010)
This article provides hardware and software requirements for using hardware-based virtualization. Although Windows Server 2008 Hyper-V technology is the focal point of this document, the basic hardware requirements for enabling hardware-based virtualization also apply to third-party virtualization technologies that are certified by Microsoft.
-
Hardware
The requirements for hardware-based virtualization are as follows:
Hardware-assisted virtualization, which is available in processors that include a virtualization option—specifically processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology.
Hardware-enforced Data Execution Prevention (DEP) is available and enabled.
You can use one of the following tools to determine if the processor on an existing server supports Hyper-V:
AMD Hyper-V Compatibility Check Utility (.zip file) (http://go.microsoft.com/fwlink/?LinkId=150561)
Intel Processor Identification Utility (Windows Version) (http://go.microsoft.com/fwlink/?LinkId=150562)
-
Software
One of the following Microsoft products is required for Hyper-V:
Windows Server 2008 (all editions of Windows Server 2008, except for Windows Server 2008 for Itanium-Based Systems, Windows Web Server 2008, and Windows Server 2008 Foundation)
Microsoft Hyper-V Server 2008
Windows Server 2008 R2 (all editions of Windows Server 2008 R2, except for Windows Server 2008 R2 for Itanium-Based Systems, Windows Web Server 2008 R2, and Windows Server 2008 R2 Foundation)
Hyper-V Server R2
We recommend Windows Server 2008 R2 for virtualization servers because of the many improvements introduced for Hyper-V, such as:
Live migration to move a running virtual machine from one cluster node to another
Significant gains in performance and scalability
Enhanced processor support
Enhanced virtual machine storage
Enhanced networking support
For more information, see What’s New in Hyper-V in Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=155234).
-
See Also
Virtualization support and licensing (SharePoint Foundation 2010)
-
-
Plan for virtualization (SharePoint Foundation 2010)
This article describes the planning process to follow in order to successfully deploy Microsoft SharePoint Foundation 2010 in a virtual environment. Each step in the planning process includes links to the appropriate documentation. It is assumed that you have determined the SharePoint Foundation 2010 solution that you want to deploy in a virtual environment. On the surface, deploying a SharePoint Foundation 2010 farm on virtual machines is the same as deploying a farm on physical servers. However, deploying in a virtual environment involves a different level of planning that takes into account the characteristics of Windows Server 2008 Hyper-V technology as well as how virtual machines, the virtual network adapters, and virtual hard disks are implemented on a virtualization server.
Before you start developing your virtualization plan, we recommend that you read the Hyper-V Planning and Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=187964).
Detailed information about the following subjects is out-of-scope for this article, but is provided in other articles:
Capacity management
Security requirements
Health and performance monitoring
Backup and recovery
A virtual environment consists of two interrelated layers, one physical and one virtual. A configuration change in either layer effects servers in the other layer. This interrelationship becomes evident when you plan for, deploy, and use SharePoint Foundation 2010 in a virtual environment.
-
Create a plan for deploying SharePoint Foundation 2010 in a virtual environment
You should approach planning for a virtual farm the same way as you would plan for a physical farm. Most, if not all, of the issues and requirements for deploying SharePoint Foundation 2010 on physical servers apply equally to virtual machines. Any decisions that you make, such as minimum processor or memory requirements, have a direct bearing on number of virtualization hosts required, as well as their ability to adequately support the virtual machines that you identify for the farm.
After you finish planning a physical farm, you have all the information you need to design virtualization architecture. Ideally, this architecture is as close as possible to the final virtualization solution that you intend to put into production. Realistically, the architecture is likely to change as you move through the deployment phase of the system lifecycle. In fact, you may determine that some farm server roles are not good candidates for virtualization.
The key planning steps, tasks, and references are summarized in following the procedure.
To create a virtualization plan
1. Determine virtualization scope
Determining the scope of farm virtualization is a key contributing factor to successfully implementing, managing, and evaluating your virtualization project. When determining scope, you have to decide whether you will virtualize some or the entire supporting virtual machine infrastructure.
Use the following list of tasks to determine the scope of virtualization.
Task 1: Identify all the farms that are required to implement your solution. Take into consideration the fact that most solutions have several farm components. For example, an Internet-facing Web portal typically has a publishing farm, an authoring farm, and a testing or quality assurance farm.
Task 2: For each farm, determine the number of servers that are required as well as the role that each server will have in the farm.
Task 3: Identify which farms you want to deploy in in a virtual environment.
Refining the scope of a solution also refines the scope of a deployment, which makes it easier to implement and manage. For more information, see Site and solution planning (SharePoint Foundation 2010). In many cases, solutions share common elements; however, each solution may have its own requirements. For more information, see Fundamental site planning (SharePoint Foundation 2010). The article shows one of the popular solutions.
Note:
Expect to refine the scope of your solution as you move through the phases of deploying your farm in a production environment.
2. Identify servers to virtualize
Identify servers that are good candidates for virtualization. From a technical and Microsoft support perspective, all SharePoint servers can be virtualized. The decision to virtualize a particular farm server should be based on:
Corporate compliance policies (for example, legal and technical)
Benefits derived from server consolidation, such as reduced power consumption and physical space requirements. For more information, see Server virtualization (http://go.microsoft.com/fwlink/?LinkId=187965).
Capacity requirements (see next planning step)
3. Identify capacity requirements for each farm server
Determine the resource requirements for each farm server as if it was a physical server. Take into account specialized server roles, such as hosting Enterprise Search components. You need to specify the amount of resources needed for each of the following server components:
Memory
Number of processors and minimum clock speed
Number and size of hard disks
Number of network adapters and their required throughput speed
4. Determine if virtual machine can meet physical requirements.
You have to determine whether each virtual machine that you identified in Step 3 can meet the capacity requirements of a corresponding physical server. At a minimum, complete the following tasks:
Task 1: Assess the memory requirement in the context of available virtualization host capacity.
Task 2: Assess the processor requirement. Hyper-V has a hard limit of four virtual processors per virtual machine. If a physical farm server requires eight processors, determine whether this requirement can be met by scaling out the number of virtual machines in a farm.
Task 3: Assess the virtual machine storage requirement in the context of local physical storage or SAN.
5. Determine virtualization host requirements
Determine the minimum host requirements (memory, number of cores, number and size of local hard drives, number of network adapters)Also consider and plan for the following:
Scalability: Determine if you can add more CPUs, more memory, more hard disks, and more network adapters to the host computer.
Important:
Depending on the manufacturer and computer model, you may not be able to increase capacity. You need to have this information before you use or purchase a server.
Extra host capacity: Determine whether or not the host has the capacity to scale up existing virtual machines, or to add additional virtual machines. This is very important if you plan to use Hyper-V failover clustering, quick migration, or live migration.
Important:
Plan for peak load and determine how short term spikes in load will be handled.
6. Design virtualization architecture
A well-designed architecture is required for a successful solution. For SharePoint Foundation 2010, a basic three-tier topology provides the foundation for all the solutions. The following elements form a good design that is based on the recommended foundation topology:
Good overall performance
Ease of maintenance and upgrade
Flexibility
Scalability
High availability
A virtualization architecture model consists of the virtualization hosts and the virtual machines that make up the farm topology. This model enables you to visualize the virtual environment that you plan to deploy.
Note:
Be prepared to refine the architecture as you move through the planning process. The following steps may dictate changes to the architecture.
7. Identify storage requirements
Determine how much local physical storage or SAN storage is required for Hyper-V-related storage such as configuration files, Virtual Hard Disks (VHDs), and snapshots.
8. Identify backup and recovery requirements
In addition to the farm servers, you have to plan backup and recovery for all or part of a farm. For more information, see Backup and recovery (SharePoint Foundation 2010) (http://technet.microsoft.com/library/48dbef54-1f1b-424f-a918-d2c428c3216e(Office.14).aspx).
9. Determine high availability requirements and design a solution
Identify approaches for achieving high availability for Web servers, application servers, and databases. Typical strategies include the following:
Redundant hardware and servers
Hot-swappable components
Failover clustering for virtual and physical servers. For more information, see Hyper-V: Using Hyper-V and Failover Clustering (http://go.microsoft.com/fwlink/?LinkId=187967).
Clustering or mirroring for database servers. For more information, see Plan for availability (SharePoint Foundation 2010).
10. Identify health and capacity indicators for monitoring the virtual environment.
Combine the key indicators that you derived in the previous steps with the planning you did for SharePoint Foundation 2010. For more information, see Server farm and environment planning (SharePoint Foundation 2010) . You have to determine all the health and capacity indicators in order to collect measurements from the following objects in the virtual environment:
Virtual machines with SharePoint Foundation 2010 installed
Virtual machines that are not part of the farm, such as a firewall server
Virtualization hosts
Network components
After you start to collect data from the virtual environment, you can create a baseline, which can be used to assess and tune the virtual environment during deployment and after the farm goes into production.
11. Create a deployment plan for the deployment phase of the system lifecycle.
For more information, see the SharePoint 2010 Products Deployment model, available in the Technical diagrams (SharePoint Foundation 2010) article.
12. Create a maintenance plan
Create a maintenance plan that enables you to implement password changes and apply software updates, service packs, and hotfixes. This plan should include the virtual machines and the virtualization hosts.
-
Performance and capacity test results and recommendations (SharePoint Foundation 2010)
This section contains a series of white papers describing the performance and capacity impact of specific feature sets included in Microsoft SharePoint Foundation 2010. These white papers include information about the performance and capacity characteristics of the feature and how it was tested by Microsoft, including:
Test farm characteristics
Test results
Recommendations
Troubleshooting performance and scalability
The following table describes the available white paper. You can download the white paper as a Microsoft Word document (.doc) (http://www.microsoft.com/downloads/details.aspx?FamilyID=e8a1fb0d-957d-4f96-8e0a-f5c74df0796e).
Title
Description
SharePoint Foundation 2010 Search Capacity Planning
Provides guidance on how to plan for search in SharePoint Foundation 2010.
-
See Also
Capacity management and sizing for SharePoint Server 2010 (http://technet.microsoft.com/library/031b0634-bf99-4c23-8ebf-9d58b6a8e6ce(Office.14).aspx)
-
-
Planning worksheets for SharePoint Foundation 2010
In this article:
Planning worksheets by title
This article provides links to worksheets that you can use to record information that you gather and decisions that you make as you plan your deployment of Microsoft SharePoint Foundation 2010. Use these worksheets in conjunction with — not as a substitute for — Planning and architecture for SharePoint Foundation 2010.
-
Planning worksheets by task
-
Planning worksheets by title
Use this worksheet
For this task
To do this
Backup and recovery planning workbook (http://go.microsoft.com/fwlink/?LinkID=184385)
Help you plan strategies for backup and recovery for SharePoint Foundation 2010 environment.
Plan incoming e-mail worksheet (http://go.microsoft.com/fwlink/?LinkId=200542)
Plan incoming e-mail in order to enable SharePoint sites to receive and store e-mail messages and attachments in lists and libraries.
Site planning data worksheet (http://go.microsoft.com/fwlink/?LinkID=167838&clcid=0x409)
Plan sites and site collections (SharePoint Foundation 2010)
Plan top level site collections and sites, and record decisions about site themes and navigation.
Upgrade worksheet (http://go.microsoft.com/fwlink/?LinkId=179928)
Plan and prepare for upgrade (SharePoint Foundation 2010) (http://technet.microsoft.com/library/cb22a4d2-e8ac-4578-8fb0-4ab03dafd3bd(Office.14).aspx)
Record information about your environment while you prepare for upgrade.
Getting started with Microsoft SharePoint Foundation 2010
-
Getting started with
Microsoft SharePoint Foundation 2010
Microsoft Corporation
Published: June 2011
Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com)
- Abstract
The content in the book covers information about how to get started with the installation, configuration, and upgrade to Microsoft SharePoint Foundation 2010.
The content in this book is a copy of selected content in the SharePoint Foundation 2010 technical library (http://go.microsoft.com/fwlink/?LinkId=181463) as of the publication date. For the most current content, see the technical library on the Web.

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
© 2011 Microsoft Corporation. All rights reserved.
Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
Contents
Introduction to Getting Started for SharePoint Foundation 2010 1
What’s new in SharePoint Foundation 2010 2
Changes from Windows SharePoint Services 3.0 to SharePoint Foundation 2010 3
Features removed from SharePoint Foundation 2010 3
Hardware and software requirements (SharePoint Foundation 2010) 7
Hardware requirements—Web servers, application servers, and single server installations 7
Hardware requirements—Database servers 8
Access to applicable software 14
Plan browser support (SharePoint Foundation 2010) 18
About planning browser support 18
Key planning phase of browser support 18
Deploy a single server with SQL Server (SharePoint Foundation 2010) 35
Install SharePoint Foundation 2010 36
Deploy a single server with a built-in database (SharePoint Foundation 2010) 45
Install SharePoint Foundation 2010 46
Configure Windows Server Backup 51
Roadmap to SharePoint Foundation 2010 content 52
- Abstract
-
Getting help
Every effort has been made to ensure the accuracy of this book. This content is also available online in the Office System TechNet Library, so if you run into problems you can check for updates at:
http://technet.microsoft.com/office
If you do not find your answer in our online content, you can send an e-mail message to the Microsoft Office System and Servers content team at:
itspdocs@microsoft.com
If your question is about Microsoft Office products, and not about the content of this book, please search the Microsoft Help and Support Center or the Microsoft Knowledge Base at:
http://support.microsoft.com
-
Introduction to Getting Started for SharePoint Foundation 2010
Microsoft SharePoint Foundation 2010 is a versatile technology that organizations and business units of all sizes can use to increase the efficiency of business processes and improve team productivity. SharePoint Foundation 2010 gives people access to information they need by using tools for collaboration that help people stay connected across organizational and geographic boundaries.
This Getting Started guide for SharePoint Foundation 2010 covers what’s new in SharePoint Foundation 2010, and includes some end-to-end deployment scenarios to get you started quickly with an evaluation environment for SharePoint Foundation 2010. The following list describes each topic in this guide.
- “What’s new in SharePoint Foundation 2010” provides a list of links to content that will introduce you to the new capabilities and features in SharePoint Foundation 2010.
- “Changes from Windows SharePoint Services 3.0 to SharePoint Foundation 2010” describes the features that have been deprecated or removed from Windows SharePoint Services 3.0 to SharePoint Foundation 2010.
- “Hardware and software requirements (SharePoint Foundation 2010)” describes the minimum and recommended hardware and software that are required to run SharePoint Foundation 2010.
- “Plan browser support (SharePoint Foundation 2010)” describes the functionality available — and level of support — for SharePoint Foundation 2010 features that you can expect when you are using several common Web browsers.
- “Deploy a single server with SQL Server (SharePoint Foundation 2010)” provides end-to-end installation instructions for setting up SharePoint Foundation 2010 on a single server farm. This installation scenario is ideal for evaluating SharePoint Foundation 2010 functionality or for hosting a very small installation of SharePoint Foundation 2010. It is also useful if you want to configure a farm to meet your needs first, and then add servers to the farm later.
- “Deploy a single server with a built-in database (SharePoint Foundation 2010)” provides end-to-end instructions for installing SharePoint Foundation 2010 on a single server with a built-in database. This configuration is useful if you want to evaluate SharePoint Foundation 2010 features and capabilities, such as collaboration, document management, and search. This configuration is also useful if you are deploying only a few Web sites and you want to minimize administrative overhead.
- “Roadmap to SharePoint Foundation 2010 content” summarizes the content and resources that are available on the Microsoft.com Web site that can help you understand and use SharePoint Foundation 2010 as you go beyond the basics that are presented in this guide.
-
What’s new in SharePoint Foundation 2010
Published: May 12, 2010
Microsoft SharePoint Foundation 2010 is the essential solution for organizations that need a secure, manageable, Web-based collaboration platform. It helps teams stay connected and productive by providing easy access to the people, documents, and information that they need to make well-informed decisions and get work done.
To see what’s new in SharePoint Foundation 2010, review the following:
- What’s New in Microsoft SharePoint Foundation 2010 (http://go.microsoft.com/fwlink/?LinkId=188355) The TechNet Resource Center page points to articles and other resources to introduce you to new features such as Windows PowerShell, the new command-line interface and scripting language; health monitoring, an integrated health analysis tool (SharePoint Maintenance Manager) that enables SharePoint to automatically check for potential configuration, performance, and usage problems; and sandboxed solutions, a restricted execution environment that enables programs to access only certain resources and keep problems that occur in the sandbox from affecting the rest of the server environment.
- SharePoint Foundation 2010 home page (http://go.microsoft.com/fwlink/?LinkId=188906) This site gives an overview of SharePoint Foundation 2010 and includes videos that demonstrate key features that can improve productivity, provide flexible deployment, and create a scalable, unified infrastructure.
-
Changes from Windows SharePoint Services 3.0 to SharePoint Foundation 2010
Published: May 12, 2010
This article describes the features that have been deprecated or removed from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010. Deprecated features are provided in SharePoint Foundation 2010 for compatibility with previous product versions. These features will be removed in subsequent versions.
In this article:
- Deprecated features
- Features removed from SharePoint Foundation 2010
-
Deprecated features
The following feature is shipped with SharePoint Foundation 2010 but will be removed from subsequent versions.
Stsadm command-line tool
Description: The Stsadm command-line tool has been deprecated.
Reason for change: The Stsadm command-line tool will be superseded by Windows PowerShell 2.0.
Migration path: The Stsadm command-line tool is included to support compatibility with previous product versions. You should use Windows PowerShell 2.0 when performing command-line administrative tasks.
-
Features removed from SharePoint Foundation 2010
The following features and functionality are no longer available in SharePoint Foundation 2010.
32-bit operating systems
Description: SharePoint Foundation 2010 requires a 64-bit operating system. Running SharePoint Foundation 2010 on 32-bit operating systems is no longer supported.
Reason for change: SharePoint Foundation 2010 has numerous features that benefit from the performance provided by 64-bit operating systems.
Migration path: Install SharePoint Foundation 2010 on 64-bit operating systems.
Description: The ability to perform side-by-side installation of Windows SharePoint Services 3.0 and SharePoint Foundation 2010 on the same server is being removed. This change is related to the removal of support for Gradual upgrade.
Reason for change: Compatibility and performance issues prevent side-by-side installation.
Migration path: Perform upgrade-in-place installation on the same hardware, or perform database attach to a new farm. Use new hardware if both Windows SharePoint Services 3.0 and SharePoint Foundation 2010 versions of a farm must exist at the same time.
For more information, see Perform a database attach upgrade to SharePoint Foundation 2010 (http://technet.microsoft.com/library/caaf9332-63bc-46b6-997f-edbfe8a84ad1(Office.14).aspx).
Description: Support for the gradual upgrade feature is being removed as part of the removal of Side-by-side installation.
Reason for change: Compatibility and performance issues prevent side-by-side installation.
Migration path: Use the read-only database capability of Windows SharePoint Services 3.0 with the database attach upgrade capability of SharePoint Foundation 2010 to minimize downtime.
For more information, see Perform a database attach upgrade to SharePoint Foundation 2010 (http://technet.microsoft.com/library/caaf9332-63bc-46b6-997f-edbfe8a84ad1(Office.14).aspx).
For long upgrade periods where you must maintain both Windows SharePoint Services 3.0 and SharePoint Foundation 2010 versions of a farm, you can use the alternate access mapping (AAM) URL redirection capability provided in SharePoint Foundation 2010. Upgrades that use AAM URL redirection are performed by using database attach upgrade command-line operations instead of timer job-based events that are scheduled from the user interface (UI).
For more information, see Using AAM URL redirection as part of the upgrade process (SharePoint Foundation 2010) (http://technet.microsoft.com/library/f63d606b-e8bf-4b0c-986a-39382da76781(Office.14).aspx).
Web discussions
Description: Web discussions enable users to add comments about documents and pages without modifying their actual content. SharePoint Foundation 2010 does not support Web discussions.
Reason for change: This feature was deprecated in Windows SharePoint Services 3.0 because of its low adoption rate. The feature has now been removed from the product.
Migration path: This functionality is no longer available.
SQL Server 2000 data sources
Description: SQL Server 2000 data sources are no longer supported in SharePoint Foundation 2010.
Reason for change: SQL Server 2000 does not fully support many of the newer data features available in SharePoint Foundation 2010.
Migration path: Use data sources that are on Microsoft SQL Server 2005 or Microsoft SQL Server 2008.
ODBC data sources
Description: ODBC data sources are no longer supported in SharePoint Foundation 2010.
Reason for change: Newer and more versatile database connection options have replaced the functionality of ODBC.
Migration path: ODBC is no longer listed as an option for connecting to a data source. Use another data connection type.
Version 3 themes
Description: A theme is a set of colors, fonts, and decorative elements that enable you to quickly change the appearance of a site. The functionality provided in the version 3 themes is not available in the newly designed version 4 themes.
Reason for change: Version 4 themes are redesigned to simplify the process of generating themes. The new architecture is not compatible with the architecture of version 3 themes.
Migration path: Version 3 themes are still supported if the UI mode is kept at version 3. Version 3 themes are not supported in version 4 UI mode.
Web bot software agents
Description: A Web bot software agent is a dynamic object on a Web page that is evaluated when the page is saved or, in some cases, when the page is opened in a Web browser. Search crawlers and indexers are examples of Web bots. Developers can no longer use Web bot entry points and users cannot add Web bots to SharePoint Foundation 2010 sites.
Reason for change: This functionality is replaced by Web Parts.
Migration path: Use Web Parts instead of Web bots.
E-mail enabled groups and Microsoft SharePoint Directory Management service (DMS)
Description: The Microsoft SharePoint Directory Management service (DMS) connects SharePoint sites to an organization’s user directory to provide enhanced e-mail features. If a SharePoint farm is using DMS, users cannot enable SharePoint groups to use e-mail.
Reason for change: The type of authentication used in DMS is being replaced with claims authentication.
Migration path: This feature is not available in SharePoint Foundation 2010. Use claims authentication instead.
For more information, see Plan authentication methods (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b6bc8fec-c11c-4ed7-a78d-3ad61c7ef6c0(Office.14).aspx).
Permissions for sub-webs
Description: When you assign a permission level to a parent site, that permission level is inherited by all sub-webs of the parent site by default. In Windows SharePoint Services 3.0, if you wanted a sub-web to have different permissions from its parent, you could edit the inherited permission level definition at the sub-web scope. The result was that you would have two permission levels with the same name but different permissions, depending on their scope. For example, suppose you assigned the Design permission level to a parent site, but you want to change the permissions on a sub-web so that users will not be able to apply style sheets to pages in that sub-web. In Windows SharePoint Services 3.0, you could edit the Design permission level on the sub-web itself, remove the Apply Style Sheets permission, and save the permission level as Design. It would not be possible, just by looking at permission levels, to determine that the sub-web actually had a different set of permissions than its parent site.
Migration path: In SharePoint Foundation 2010, if you want to give different permissions to a sub-web, you must assign a separate permission level to the sub-web. Site collections that are upgraded from Windows SharePoint Services 3.0 and have these unique permission level structures will continue to work. However, the user interface in SharePoint Foundation 2010 does not have a way to edit an inherited permission level at the sub-web scope, so you cannot change them or create new permission level definitions of this type. If you have a specific business need for continuing to use the Windows SharePoint Services 3.0 process, use the SharePoint Foundation 2010 object model.
Internationalized domain names
Description: Although Windows SharePoint Services 3.0 supported internationalized domain names (IDNs), SharePoint Foundation 2010 does not.
Reason for change: Support of internationalized domain names (IDNs) has been deprecated.
Migration path: If you currently use IDNs with Windows SharePoint Services 3.0 and you plan to upgrade or migrate to SharePoint Foundation 2010, you must stop using IDNs, delete all IDN settings, and then set up an environment that does not use IDN before doing so.
-
Hardware and software requirements (SharePoint Foundation 2010)
Updated: March 31, 2011
This article lists the minimum hardware and software requirements to install and run Microsoft SharePoint Foundation 2010.

Important:If you contact Microsoft technical support about a production system that does not meet the minimum hardware specifications described in this document, support will be limited until the system is upgraded to the minimum requirements.
In this article:
-
Overview
Microsoft SharePoint Foundation 2010 provides for a number of installation scenarios. Currently, these installations include single server with built-in database installations and single-server or multiple-server farm installations.
-
Hardware requirements—Web servers, application servers, and single server installations
The requirements in the following table apply both to installations on a single server with a built-in database and to servers running SharePoint Foundation 2010 in a multiple server farm installation.
Component
Minimum requirement
Processor
64-bit, four cores
RAM
- 4 GB for developer or evaluation use
- 8 GB for production use in a single server or multiple server farm
Hard disk
80 GB for system drive
You must have sufficient space for the base installation and sufficient space for diagnostics such as logging, debugging, creating memory dumps, and so on. For production use, you also need additional free disk space for day-to-day operations. Maintain twice as much free space as you have RAM for production environments. For more information, see Capacity management and sizing for SharePoint Server 2010 (http://technet.microsoft.com/library/031b0634-bf99-4c23-8ebf-9d58b6a8e6ce(Office.14).aspx).
-
Hardware requirements—Database servers
The requirements in the following table apply to database servers in production environments with multiple servers in the farm.

Note:Our definitions of small and medium deployments are those described in the “Reference Architectures” section in Capacity management and sizing for SharePoint Server 2010 (http://technet.microsoft.com/library/031b0634-bf99-4c23-8ebf-9d58b6a8e6ce(Office.14).aspx).
Component
Minimum requirement
Processor
- 64-bit, four cores for small deployments
- 64-bit, eight cores for medium deployments
RAM
- 8 GB for small deployments
- 16 GB for medium deployments
For large deployments, see the “Estimate memory requirements” section in Storage and SQL Server capacity planning and configuration (SharePoint Server 2010) (http://technet.microsoft.com/library/a96075c6-d315-40a8-a739-49b91c61978f(Office.14).aspx).

Note:These values are higher than those recommended as the minimum values for SQL Server because of the distribution of data required for a SharePoint Products 2010 environment. For more information about SQL Server system requirements, see Hardware and Software Requirements for Installing SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=129377).
Hard disk
80 GB for system drive
Hard disk space is dependent on the size of your SharePoint content. For information about estimating the size of content and other databases for your deployment, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2010) (http://technet.microsoft.com/library/a96075c6-d315-40a8-a739-49b91c61978f(Office.14).aspx).
-
Software requirements
The requirements in the following tables apply to single server with built-in database installations and server farm installations that include a single server and multiple servers in the farm.

Important:SharePoint Foundation 2010 does not support single label domain names. For more information, see Information about configuring Windows for domains with single-label DNS names (http://support.microsoft.com/kb/300684).
The Microsoft SharePoint Products Preparation Tool — which you access from the SharePoint Foundation 2010 Start page — can assist you in the installation of the software prerequisites for SharePoint Foundation 2010. Ensure that you have an Internet connection, because some of these prerequisites are installed from the Internet. For more information, see Deploy a single server with SQL Server (SharePoint Foundation 2010), Deploy a single server with a built-in database (SharePoint Foundation 2010), and Multiple servers for a three tier farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a(Office.14).aspx).
Minimum requirements
Environment
Minimum requirement
Database server in a farm
One of the following:
- The 64-bit edition of Microsoft SQL Server 2008 R2.
- The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2. From the Cumulative update package 2 for SQL Server 2008 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=165962) page, click the View and request hotfix downloads link and follow the instructions. On the Hotfix Request page, download the SQL_Server_2008_SP1_Cumulative_Update_2 file. When you install Microsoft SQL Server 2008 SP1 on Windows Server 2008 R2, you might receive a compatibility warning. You can disregard this warning and continue with your installation.

Note:We do not recommend that you use CU3 or CU4, but instead CU2, CU5, or a later CU than CU5. For more information, see Cumulative update package 5 for SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=196928). Download the SQL_Server_2008_RTM_CU5_SNAC file.
- The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3). From the Cumulative update package 3 for SQL Server 2005 Service Pack 3 (http://go.microsoft.com/fwlink/?LinkId=165748) page, click the View and request hotfix downloads link and follow the instructions. On the Hotfix Request page, download the SQL_Server_2005_SP3_Cumulative_Update_3 file.
For more information about choosing a version of SQL Server, see SQL Server 2008 R2 and SharePoint 2010 Products: Better Together (SharePoint Server 2010): white paper (http://technet.microsoft.com/library/665876e1-2706-42ad-bd76-8e4d1da0ce92(Office.14).aspx).
Single server with built-in database
- The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2; the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server; or the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server. If you are running Windows Server 2008 with SP1, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 automatically.

Note:You must download an update for Windows Server 2008 and Windows Server 2008 R2 before you run Setup. The update is a hotfix for the .NET Framework 3.5 SP1 that is installed by the Preparation tool. It provides a method to support token authentication without transport security or message encryption in WCF. For more information and links, see the “Access to Applicable Software” section later in this article.
-
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577).
- For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
-
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/?LinkId=192578).
The preparation tool installs the following prerequisites:
- Web Server (IIS) role
- Application Server role
- Microsoft .NET Framework version 3.5 SP1
- SQL Server 2008 Express with SP1
- Microsoft Sync Framework Runtime v1.0 (x64)
- Microsoft Filter Pack 2.0
- Microsoft Chart Controls for the Microsoft .NET Framework 3.5
- Windows PowerShell 2.0
- SQL Server 2008 Native Client
- Microsoft SQL Server 2008 Analysis Services ADOMD.NET
- ADO.NET Data Services Update for .NET Framework 3.5 SP1
- A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
- Windows Identity Foundation (WIF)

Note:If you have Microsoft “Geneva” Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF).
Front-end Web servers and application servers in a farm
- The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2; the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server; or the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server. If you are running Windows Server 2008 with SP1, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 automatically.

Note:You must download an update for Windows Server 2008 and Windows Server 2008 R2 before you run Setup. The update is a hotfix for the .NET Framework 3.5 SP1 that is installed by the Preparation tool. It provides a method to support token authentication without transport security or message encryption in WCF. For more information and links, see the “Access to Applicable Software” section.
-
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577)
- For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
-
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/?LinkId=192578).
The preparation tool installs the following prerequisites:
- Web Server (IIS) role
- Application Server role
- Microsoft .NET Framework version 3.5 SP1
- Microsoft Sync Framework Runtime v1.0 (x64)
- Microsoft Filter Pack 2.0
- Microsoft Chart Controls for the Microsoft .NET Framework 3.5
- Windows PowerShell 2.0
- SQL Server 2008 Native Client
- Microsoft SQL Server 2008 Analysis Services ADOMD.NET
- ADO.NET Data Services Update for .NET Framework 3.5 SP1
- A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
- Windows Identity Foundation (WIF)

Note:If you have Microsoft “Geneva” Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF).
Client computer
- A supported browser. For more information, see Plan browser support (SharePoint Foundation 2010).
Optional software
Environment
Optional software
Single server with built-in database
- Windows 7 or Windows Vista. For more information, see Setting Up the Development Environment for SharePoint Server (http://go.microsoft.com/fwlink/?LinkID=164557).
Client computer
- Microsoft Office 2010 client. For more information, see Microsoft Office 2010 (http://go.microsoft.com/fwlink/?LinkId=195843).
- Microsoft Silverlight 3.
-
Access to applicable software
To install Windows Server 2008 or Microsoft SQL Server, you can go to the Web sites listed in this section. You can install all other software prerequisites through the SharePoint Foundation Start page. Most of the software prerequisites are also available from Web sites listed in this section. The Web Server (IIS) role and the Application Server role can be enabled manually in Server Manager.
In scenarios where installing prerequisites directly from the Internet is not possible or not feasible, you can install the prerequisites from a network share. For more information, see Install prerequisites from a network share (SharePoint Foundation 2010) (http://technet.microsoft.com/library/3fdf5e00-dffa-46bb-a6b8-abaf66aa583f(Office.14).aspx).
- SharePoint Foundation 2010 (http://go.microsoft.com/fwlink/?LinkId=197422)
- Language Packs for SharePoint Foundation 2010 (http://go.microsoft.com/fwlink/?LinkId=197424)
- Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=197426)
- Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=197428)
- Windows Server 2008 R2 SP1 (http://go.microsoft.com/fwlink/?LinkId=214566)
- SQL Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=197429)
- SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkID=179611)
- SQL Server 2005 (http://go.microsoft.com/fwlink/?LinkId=197431)
- Microsoft SQL Server 2008 SP1 (http://go.microsoft.com/fwlink/?LinkId=166490)
- Cumulative update package 2 for SQL Server 2008 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=165962)
- Cumulative update package 5 for SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=197434). Download the SQL_Server_2008_RTM_CU5_SNAC file.
- Microsoft SQL Server 2005 SP3 (http://go.microsoft.com/fwlink/?LinkId=166496)
- Cumulative update package 3 for SQL Server 2005 Service Pack 3 (http://go.microsoft.com/fwlink/?LinkId=165748)
- Microsoft Windows Server 2008 SP2 (http://go.microsoft.com/fwlink/?LinkId=166500)
- Windows Server 2008 with SP 2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=160770)
- Windows Server 2008 R2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=166231)
- Microsoft .NET Framework 3.5 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=131037)
- Microsoft SQL Server 2008 Express Edition Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=166503)
- Windows Identity Foundation for Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkID=160381)
- Windows Identity Foundation for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=166363)
- Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/?LinkID=141237)
- Microsoft Office 2010 Filter Packs (http://go.microsoft.com/fwlink/?LinkId=191851)
- Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://go.microsoft.com/fwlink/?LinkID=141512)
- Windows PowerShell 2.0 (http://go.microsoft.com/fwlink/?LinkId=161023)
- Microsoft SQL Server 2008 Native Client (http://go.microsoft.com/fwlink/?LinkId=166505)
- Microsoft SQL Server 2008 Analysis Services ADOMD.NET (http://go.microsoft.com/fwlink/?linkid=160390)
-
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577)
- For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
- For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
- ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163519) for Windows Server 2008 SP2
- ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163524) for Windows Server 2008 R2 or Windows 7
- Microsoft Silverlight 3 (http://go.microsoft.com/fwlink/?LinkId=166506)
- Microsoft Office 2010 (http://go.microsoft.com/fwlink/?LinkID=195843)
- Office Communicator 2007 R2 (http://go.microsoft.com/fwlink/?LinkId=196930)
- Microsoft SharePoint Designer 2010 (32-bit) (http://go.microsoft.com/fwlink/?LinkId=196931)
- Microsoft SharePoint Designer 2010 (64-bit) (http://go.microsoft.com/fwlink/?LinkId=196932)
- Microsoft SQL Server 2008 SP1 (http://go.microsoft.com/fwlink/?LinkId=166490)
- Cumulative update package 2 for SQL Server 2008 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=165962).
- Microsoft SQL Server 2005 SP3 (http://go.microsoft.com/fwlink/?LinkId=166496)
- Cumulative update package 3 for SQL Server 2005 Service Pack 3 (http://go.microsoft.com/fwlink/?LinkId=165748).
- Microsoft Windows Server 2008 SP2 (http://go.microsoft.com/fwlink/?LinkId=166500)
- Windows Server 2008 with SP 2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=160770).
- Windows Server 2008 R2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=166231).
- Microsoft .NET Framework 3.5 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=131037)
- Microsoft SQL Server 2008 Express Edition Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=166503)
- Windows Identity Framework for Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkID=160381)
- Windows Identity Framework for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=166363)
- Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/?LinkID=141237&clcid=0x409)
- Microsoft Office 2010 Filter Packs (http://go.microsoft.com/fwlink/?LinkId=191851)
- Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://go.microsoft.com/fwlink/?LinkID=141512)
- Windows PowerShell 2.0 (http://go.microsoft.com/fwlink/?LinkId=161023)
- Microsoft SQL Server 2008 Native Client (http://go.microsoft.com/fwlink/?LinkId=166505)
- Microsoft SQL Server 2008 Analysis Services ADOMD.NET (http://go.microsoft.com/fwlink/?LinkId=130651)
-
KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation (http://go.microsoft.com/fwlink/?LinkId=192577)
- For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
-
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/?LinkId=192578).
- Microsoft Office 2010 (http://go.microsoft.com/fwlink/?LinkID=195843)
- Microsoft Silverlight 3 (http://go.microsoft.com/fwlink/?LinkId=166506)
- ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163519) for Windows Server 2008 SP2
- ADO.NET Data Services Update for .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkId=163524) for Windows Server 2008 R2 or Windows 7
-
Plan browser support (SharePoint Foundation 2010)
Updated: April 7, 2011
Microsoft SharePoint Foundation 2010 supports several commonly used Web browsers. This article describes different levels of Web browser support, and it explains how ActiveX controls affect features.
In this article:
-
About planning browser support
SharePoint Foundation 2010 supports several commonly used Web browsers. However, certain Web browsers might cause some SharePoint Foundation 2010 functionality to be downgraded, limited, or available only through alternative steps. In some cases, functionality might be unavailable for noncritical administrative tasks.
As part of planning your deployment of SharePoint Foundation 2010, we recommend that you review the browsers used in your organization to ensure optimal performance with SharePoint Foundation 2010.
If you are upgrading from SharePoint Portal Server 2003 to SharePoint Foundation 2010, additional considerations for browser support exist. For information, see Upgrade from SharePoint Portal Server 2003 to SharePoint Server 2010 (http://technet.microsoft.com/library/ba5a173b-8ff1-4096-a7ab-8c8412b9114c(Office.14).aspx).
-
Key planning phase of browser support
Browser support is an important part of your SharePoint Foundation 2010 implementation. Before you install SharePoint Foundation 2010, ensure that you know which browsers SharePoint Foundation 2010 supports. The information in this topic covers the following areas:
- Browser support levels
- Browser support matrix
- Browser details
Browser support levels
Browser support for SharePoint Foundation 2010 can be divided into three different levels, as follows:
-
Supported
A supported Web browser is a Web browser that is supported to work with SharePoint Foundation 2010, and all features and functionality work. If you encounter any issues, support can help you to resolve these issues.
-
Supported with known limitations
A supported Web browser with known limitations is a Web browser that is supported to work with SharePoint Foundation 2010, although there are some known limitations. Most features and functionality work, but if there is a feature or functionality that does not work or is disabled by design, documentation on how to resolve these issues is readily available.
-
Not tested
A Web browser that is not tested means that its compatibility with SharePoint Foundation 2010 is untested, and there may be issues with using the particular Web browser. SharePoint Foundation 2010 works best with up-to-date, standards-based Web browsers.
Browser support matrix
The following table summarizes the support levels of commonly used browsers.
Browser
Supported
Supported with limitations
Not tested
Internet Explorer 9 (32-bit)
X
Internet Explorer 8 (32-bit)
X
Internet Explorer 7 (32-bit)
X
Internet Explorer 9 (64-bit)
X
Internet Explorer 8 (64-bit)
X
Internet Explorer 7 (64-bit)
X
Internet Explorer 6 (32-bit)
X
Mozilla Firefox 3.6 (on Windows operating systems)
X
Mozilla Firefox 3.6 (on non-Windows operating systems)
X
Safari 4.04 (on non-Windows operating systems)
X
Browser details
You should review the details of the Web browser that you have or plan to use in your organization to ensure that the Web browser works with SharePoint Foundation 2010 and according to your business needs.
Internet Explorer 8 (32-bit) and Internet Explorer 9 (32-bit)
Internet Explorer 8 (32-bit) and Internet Explorer 9 (32-bit) are supported on the following operating systems:
- Windows Server 2008 R2
- Windows Server 2008
- Windows Server 2003
- Windows 7
- Windows Vista
- Windows XP
Known limitations
There are no known limitations for Internet Explorer 8 (32-bit) and Internet Explorer 9 (32-bit).
Internet Explorer 7 (32-bit)
Internet Explorer 7 (32-bit) is supported on the following operating systems:
- Windows Server 2008
- Windows Server 2003
- Windows Vista
- Windows XP
Known limitations
There are no known limitations for Internet Explorer 7 (32-bit).
Internet Explorer 6 (32-bit)
SharePoint Foundation 2010 does not support Internet Explorer 6 (32-bit).
Internet Explorer 8 (64-bit) and Internet Explorer 9 (64-bit)
Internet Explorer 8.0 (64-bit) and Internet Explorer 9 (64-bit) are supported on the following operating systems:
- Windows Server 2008 R2
- Windows Server 2008
- Windows Server 2003
- Windows 7
- Windows Vista
- Windows XP
Known limitations
The following table lists features and their known limitations in Internet Explorer 8 (64-bit) and Internet Explorer 9 (64-bit).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Works with an ActiveX control and the stssync:// protocol. Therefore, functionality may be limited without an ActiveX control, such as the one that is included in Microsoft Office 2010. The feature also requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Edit in Microsoft Office application
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views and these may not work.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. If Microsoft Excel is not installed, and if no other application is configured to open this file, then this feature will not work.
File upload and copy
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft InfoPath 2010 integration
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft PowerPoint 2010 Picture Library integration
Requires a 64-bit ActiveX control, such as the one that is delivered in Microsoft Office 2010. The user can use the following workarounds when no control has been installed:
- If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
- If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
- If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
New Document
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Send To
Can leverage a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Spreadsheet and Database integration
Require a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. The user can use the following workarounds when no control has been installed:
- If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
- In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
- Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
Internet Explorer 7 (64-bit)
Internet Explorer 7 (64-bit) is supported on the following operating systems:
- Windows Server 2008
- Windows Server 2003
- Windows Vista
- Windows XP
Known limitations
The following table lists features and their known limitations in Internet Explorer 7 (64-bit).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Works with an ActiveX control and the stssync:// protocol. Therefore, functionality may be limited without an ActiveX control, such as the one that is included in Microsoft Office 2010. This feature requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Edit in Microsoft Office application
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. If Microsoft Excel is not installed, and if no other application is configured to open this file, then this feature will not work.
File upload and copy
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft InfoPath 2010 integration
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Microsoft PowerPoint 2010 Picture Library integration
Requires a 64-bit ActiveX control, such as the one that is delivered in Microsoft Office 2010. The user can use the following workarounds when no control has been installed:
- If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
- If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
- If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
New Document
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Send To
Can leverage a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control.
Spreadsheet and Database integration
Require a 64-bit ActiveX control. Microsoft Office 2010 does not provide a 64-bit version of this control. The user can use the following workarounds when no control has been installed:
- If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
- In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
- Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
Mozilla Firefox 3.6 (on Windows operating systems)
Mozilla Firefox 3.6 is supported on the following operating systems:
- Windows Server 2008 R2
- Windows Server 2008
- Windows Server 2003
- Windows 7
- Windows Vista
- Windows XP
Known limitations
The following table lists features and their known limitations in Mozilla Firefox 3.6 (on Windows operating systems).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Works with an ActiveX control, but requires a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. The feature also requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Drag and Drop Web Parts
Cannot be moved by using drag and drop on Web Part pages. Users must click Edit on the Web Part, select Modify Web Part, and then select the zone from the Layout section of the Web Part properties page. Web Parts can be moved using drag and drop on Pages.
Edit in Microsoft Office application
Requires an ActiveX control, such as the one that is delivered in SharePoint Foundation 2010, and a Firefox control adaptor. For more information about Microsoft Office 2010 Firefox Plug-in, see FFWinPlugin Plug-in (http://go.microsoft.com/fwlink/?LinkId=199867). If you install and configure the Office Web Applications on the server, the Edit functionality works and you can modify Office documents in your browser. This functionality only works with Microsoft Office 2010 or an equivalent product together with a Firefox plug-in.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views, and these may not work. Explorer view requires Internet Explorer.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. If Microsoft Excel is not installed, and if no other application is configured to open this file, then this feature will not work.
File upload and copy
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Microsoft InfoPath 2010 integration
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Microsoft PowerPoint 2010 Picture Library integration
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. The user can use the following workarounds when no control has been installed:
- If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
- If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
- If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires an ActiveX control, such as the one delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
New Document
Requires an ActiveX control, such as the one delivered in Microsoft Office 2010, and a Firefox control adaptor. For more information about Microsoft Office 2010 Firefox Plug-in, see FFWinPlugin Plug-in (http://go.microsoft.com/fwlink/?LinkId=199867). Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Rich Text Editor – Basic Toolbar
A user can update the Rich Text Editor basic toolbar to a Full Rich Text Editor that includes the ribbon by changing the field’s properties, as follows: On the FldEdit.aspx, in the List Settings menu, select Specific Field Settings. Next, under Columns, click Description. In the Additional Columns Settings section, under Specify the type of text to allow, select Enhanced rich text (Rich text with pictures, tables, and hyperlinks).
Send To
Can leverage an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires an ActiveX control, such as the one that is delivered in Microsoft Office 2010, and a Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Spreadsheet and Database integration
Require ActiveX controls, such as those that are delivered in Microsoft Office 2010, and Firefox control adaptors. Microsoft Office 2010 does not provide a Firefox control adaptor for this control. The user can use the following workarounds when no control has been installed:
- If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
- In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
- Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
Mozilla FireFox 3.6 (on non-Windows operating systems)
Mozilla FireFox 3.6 is supported on the following operating systems:
- Mac OSX
- UNIX/Linux
Known limitations
The following table lists features and their known limitations in Mozilla FireFox 3.6 (on non-Windows operating systems).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires an ActiveX control that is not supported on this platform.
Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
Drag and Drop Web Parts
Cannot be moved by using drag and drop on Web Part pages.
Users must click Edit on the Web Part, select Modify Web Part, and then select the zone from the Layout section of the Web Part properties page.
Web Parts can be moved using drag and drop on Pages.
Edit in Microsoft Office application
Requires an ActiveX control that is not supported on this platform.
If you install and configure the Office Web Applications on the server, the Edit functionality works and you can modify Office documents in your browser.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views, and these may not work.
Explorer view requires Internet Explorer.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. Requires an application that is configured to open this file.
File upload and copy
Requires an ActiveX control that is not support on this platform.
Microsoft InfoPath 2010 integration
Requires an ActiveX control that is not support on this platform.
Microsoft PowerPoint 2010 Picture Library integration
Requires an ActiveX control that is not supported on this platform. Microsoft Office 2010 does not provide a Firefox control adaptor for this control.
The user can use the following workarounds when no control has been installed:
- If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
- If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
- If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires an ActiveX control that is not supported on this platform.
New Document
Requires an ActiveX control that is not supported on this platform. Although the New Document command may not work, you can use the Upload Document functionality.
If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Rich Text Editor – Basic Toolbar
A user can update the Rich Text Editor basic toolbar to a Full Rich Text Editor that includes the ribbon by changing the field’s properties, as follows:
On the FldEdit.aspx, in the List Settings menu, select Specific Field Settings.
Next, under Columns, click Description.
In the Additional Columns Settings section, under Specify the type of text to allow, select Enhanced rich text (Rich text with pictures, tables, and hyperlinks).
Send To
Can leverage an ActiveX control that is not supported on this platform. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires an ActiveX control that is not supported on this platform.
Spreadsheet and Database integration
Require ActiveX controls that is not supported on this platform.
The user can use the following workarounds when no control has been installed:
- If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
- In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
- Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.

Note:FireFox browsers on UNIX/Linux systems may not work with the Web Part menu.

Note:Some ActiveX features, such as list Datasheet view and the control that displays user presence information, do not work in Mozilla Firefox 3.6. Firefox users can use the Microsoft Office 2010 Firefox Plug-in to launch documents.
Safari 4.04 (on non-Windows operating systems)
Safari 4.0.4 is supported on the following operating systems:
- Mac OSX (Version 10.6, Snow Leopard)
Known limitations
The following table lists features and their known limitations in Safari 4.04 (on non-Windows operating systems).
Feature
Limitation
Connect to Outlook, Connect to Office, and Sync to SharePoint Workspace
Requires an application that is compatible with the stssync:// protocol, such as Microsoft Outlook.
Datasheet view
Requires an ActiveX control that is not supported on this platform.
Drag and Drop Web Parts
Cannot be moved by using drag and drop on Web Part pages. Users must click Edit on the Web Part, select Modify Web Part, and then select the zone from the Layout section of the Web Part properties page. Web Parts can be moved using drag and drop on Pages.
Edit in Microsoft Office application
Requires an ActiveX control that is not supported on this platform. If you install and configure the Office Web Applications on the server, the Edit functionality works and you can modify Office documents in your browser.
Explorer view
Removed in SharePoint Foundation 2010. Libraries that have been upgraded from earlier versions of SharePoint Foundation 2010 may still have Explorer views. Explorer view requires Internet Explorer.
Export to Excel
Downloads a file with an .iqy extension to the Web browser. Requires an application that is configured to open this file.
File upload and copy
Requires an ActiveX control that is not supported on this platform.
Microsoft InfoPath 2010 integration
Requires an ActiveX control that is not supported on this platform.
Microsoft PowerPoint 2010 Picture Library integration
Requires an ActiveX control that is not supported on this platform. The user can use the following workarounds when no control has been installed:
- If a user wants to upload multiple pictures in a picture library, the user must upload one picture at a time by using Upload.aspx.
- If a user wants to edit a picture in a picture library, the user must download the picture, edit it, and then upload the picture to the picture library.
- If a user wants to download more than one picture from a picture library, the user must download one picture at a time by clicking on the picture link.
Microsoft Visio 2010 diagram creation
Requires an ActiveX control that is not supported on this platform.
New Document
Requires an ActiveX control that is not supported on this platform. Although the New Document command may not work, you can use the Upload Document functionality. If you install and configure Office Web Applications on the server, the New Document command works, and you can create an Office document in your browser.
Rich Text Editor – Basic Toolbar
A user can update the Rich Text Editor basic toolbar to a Full Rich Text Editor that includes the ribbon by changing the field’s properties, as follows: On the FldEdit.aspx, in the List Settings menu, select Specific Field Settings. Next, under Columns, click Description. In the Additional Columns Settings section, under Specify the type of text to allow, select Enhanced rich text (Rich text with pictures, tables, and hyperlinks).
Send To
Can leverage an ActiveX control that is not supported on this platform. Without the control, files cannot be sent from one SharePoint farm to another SharePoint farm. However, files can still be sent from one site to another site.
Signing Forms (InfoPath Form Services)
Requires an ActiveX control that is not supported on this platform.
Spreadsheet and Database integration
Require ActiveX controls that are not supported on this platform. The user can use the following workarounds when no control has been installed:
- If a user wants to edit a document, the user must download the document, edit it, and then save it back to the server.
- In a list that requires a document to be checked out for editing, a user must use the Edit menu to check out the document, edit it, and then check it in by using the Edit menu.
- Export to spreadsheet. Users can export a SharePoint list as a spreadsheet by clicking Export to Spreadsheet on the List tab on the ribbon.
Web Part to Web Part Connections
May require deactivation of browsers pop-up blockers for SharePoint sites.
-
ActiveX controls
Some of the features in SharePoint Foundation 2010 use ActiveX controls. In secure environments, these controls must be able to work on the client computer before their features will function. Some ActiveX controls, such as those included in Microsoft Office 2010, does not work with 64-bit browser versions. For Microsoft Office 2010 (64-bit), only the following control works with 64-bit browsers:
- name.dll – Presence information
-
Deploy a single server with SQL Server (SharePoint Foundation 2010)
Updated: June 10, 2010
This article describes how to perform a clean installation of Microsoft SharePoint Foundation 2010 on a single server farm.
In this article:
-
Overview
When you install SharePoint Foundation 2010 on a single server farm, you can configure SharePoint Foundation 2010 to meet your specific needs. After Setup and the SharePoint Products Configuration Wizard have been completed, you will have installed binaries, configured security permissions, registry settings, the configuration database, and the content database, and installed the SharePoint Central Administration Web site.
Next, you can choose to run the Farm Configuration Wizard to configure the farm, select the services that you want to use in the farm, and create the first site collection, or you can manually perform the farm configuration at your own pace.
A single server farm typically consists of one server that runs both Microsoft SQL Server and SharePoint Foundation 2010. You can deploy SharePoint Foundation 2010 in a single server farm environment if you are hosting only a few sites for a limited number of users. This configuration is also useful if you want to configure a farm to meet your needs first, and then add servers to the farm at a later stage.

Note:This guide does not explain how to install SharePoint Foundation 2010 in a multiple server farm environment or how to upgrade from previous releases of SharePoint Foundation. For more information, see Multiple servers for a three tier farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a(Office.14).aspx). For more information about upgrade, see Upgrading to SharePoint Foundation 2010 (http://technet.microsoft.com/library/91046a84-57a1-40cb-a32c-ff3395073dc9(Office.14).aspx).
-
Before you begin
Before you begin deployment, do the following:
- Ensure that you are familiar with the operating-system guidelines described in Performance Tuning Guidelines for Windows Server 2008 (http://www.microsoft.com/whdc/system/sysperf/Perf_tun_srv.mspx) and Performance Tuning Guidelines for Windows Server 2008 R2 (http://www.microsoft.com/whdc/system/sysperf/Perf_tun_srv-R2.mspx).
- Ensure that you have met all hardware and software requirements. For more information, see Hardware and software requirements (SharePoint Foundation 2010).
- Ensure that you perform a clean installation of SharePoint Foundation 2010. You cannot install the RTM version of SharePoint Foundation 2010 without first removing the beta version of SharePoint Foundation 2010.
- Ensure that you are prepared to set up the required accounts with appropriate permissions, as described in Administrative and service accounts required for initial deployment (SharePoint Foundation 2010) (http://technet.microsoft.com/library/b1aee1ea-45f6-4e05-ad93-9086f6ad7e79(Office.14).aspx).

Note:As a security best practice, we recommend that you install SharePoint Foundation 2010 by using least-privilege administration.
- Ensure that you have decided which services to use for your Web application, as described in Configure services (SharePoint Foundation 2010) (http://technet.microsoft.com/library/88da9bdb-b7c2-4174-997b-d767b9b9c9ea(Office.14).aspx).
-
Install SharePoint Foundation 2010
To install and configure SharePoint Foundation 2010, follow these steps:
- Run the Microsoft SharePoint Products Preparation Tool, which installs all required prerequisites to use SharePoint Foundation 2010.
- Run Setup, which installs binaries, configures security permissions, and sets registry settings for Microsoft SharePoint Foundation.
- Run SharePoint Products Configuration Wizard, which installs and configures the configuration database, the content database, and installs the SharePoint Central Administration Web site.
- Configure browser settings.
- Run the Farm Configuration Wizard, which configures the farm, creates the first site collection, and selects the services that you want to use in the farm.
- Perform post-installation steps.
|
|
|
To complete the following procedures, you must be a member of the Administrators group on the local computer. |
Run the Microsoft SharePoint Products Preparation Tool
Use the following procedure to install software prerequisites for SharePoint Foundation 2010.
To run the Microsoft SharePoint Products Preparation Tool
- Insert your SharePoint Foundation 2010 installation disc.
- On the SharePoint Foundation 2010 Start page, click Install software prerequisites.
|
|
|
Because the preparation tool downloads components from the Microsoft Download Center, you must have Internet access on the computer on which you are installing Microsoft SharePoint Foundation. |
- On the Welcome to the Microsoft SharePoint Products Preparation Tool page, click Next.
- On the License Terms for software product page, review the terms, select the I accept the terms of the License Agreement(s) check box, and then click Next.
- On the Installation Complete page, click Finish.
Run Setup
The following procedure installs binaries, configures security permissions, and sets registry settings for SharePoint Foundation 2010.
To run Setup
- On the SharePoint Foundation 2010 Start page, click Install SharePoint Foundation.
- On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.
- On the Choose the installation you want page, click Server farm.
- On the Server Type tab, click Complete.
- Optional: To install SharePoint Foundation 2010 at a custom location, click the Data Location tab, and then either type the location or click Browse to find the location.
- Click Install Now.
- When Setup finishes, click Close.
|
|
|
If Setup fails, check the TEMP folder of the user who ran Setup. Ensure that you are logged in as the user who ran Setup, and then type %temp% in the location bar in Windows Explorer. If the path %temp% resolves to a location that ends in a “1” or “2”, you will need to navigate up one level to view the log files. The log file name is Microsoft SharePoint Foundation 2010 Setup (<timestamp>). |
|
|
|
To access the SharePoint Products Configuration Wizard, click Start, point to All Programs, and then click Microsoft SharePoint 2010 Products. If the User Account Control dialog box appears, click Continue. |
Run the SharePoint Products Configuration Wizard
The following procedure installs and configures the configuration database, the content database, and installs the SharePoint Central Administration Web site.
To run the SharePoint Products Configuration Wizard
- On the Welcome to SharePoint Products page, click Next.
- In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.
- On the Connect to a server farm page, click Create a new server farm, and then click Next.
-
On the Specify Configuration Database Settings page, do the following:
- In the Database server box, type the name of the computer that is running SQL Server.
- In the Database name box, type a name for your configuration database, or use the default database name. The default name is SharePoint_Config.
- In the Username box, type the user name of the server farm account. Ensure that you type the user name in the format DOMAIN\user name.
|
|
|
The server farm account is used to create and access your configuration database. It also acts as the application pool identity account for the SharePoint Central Administration application pool, and it is the account under which the Microsoft SharePoint Foundation Workflow Timer service runs. The SharePoint Products Configuration Wizard adds this account to the SQL Server Login accounts, the SQL Server dbcreator server role, and the SQL Server securityadmin server role. The user account that you specify as the service account must be a domain user account, but it does not need to be a member of any specific security group on your front-end Web servers or your database servers. We recommend that you follow the principle of least privilege and specify a user account that is not a member of the Administrators group on your front-end Web servers or your database servers. |
- In the Password box, type the user password.
- Click Next.
-
On the Specify Farm Security Settings page, type a passphrase, and then click Next.
Ensure that the passphrase meets the following criteria:
- Contains at least eight characters
-
Contains at least three of the following four character groups:
- English uppercase characters (from A through Z)
- English lowercase characters (from a through z)
- Numerals (from 0 through 9)
- Nonalphabetic characters (such as !, $, #, %)
|
|
|
Although a passphrase is similar to a password, it is usually longer to enhance security. It is used to encrypt credentials of accounts that are registered in Microsoft SharePoint Foundation; for example, the Microsoft SharePoint Foundation system account that you provide when you run the SharePoint Products Configuration Wizard. Ensure that you remember the passphrase, because you must use it each time you add a server to the farm. |
-
On the Configure SharePoint Central Administration Web Application page, do the following:
- Either select the Specify port number check box and type the port number you want the SharePoint Central Administration Web application to use, or leave the Specify port number check box cleared if you want to use the default port number.
- Click either NTLM or Negotiate (Kerberos).
- Click Next.
- On the Completing the SharePoint Products Configuration Wizard page, review your configuration settings to verify that they are correct, and then click Next.
|
|
|
If you want to automatically create unique accounts for users in Active Directory Domain Services (AD DS), click Advanced Settings, and enable Active Directory account creation. |
- On the Configuration Successful page, click Finish.
|
|
|
If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint Foundation is installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\LOGS folder. |
|
|
|
If you are prompted for your user name and password, you might need to add the SharePoint Central Administration Web site to the list of trusted sites and configure user authentication settings in Internet Explorer. You might also want to disable the Internet Explorer Enhanced Security settings. Instructions for how to configure or disable these settings are provided in the following section. |
|
|
|
If you see a proxy server error message, you might need to configure your proxy server settings so that local addresses bypass the proxy server. Instructions for configuring proxy server settings are provided later in the following section. |
Configure browser settings
After you run the SharePoint Products Configuration Wizard, you should ensure that SharePoint Foundation 2010 works properly for local administrators in your environment by configuring additional settings in Internet Explorer.
|
|
|
If local administrators are not using Internet Explorer, you might need to configure additional settings. For information about supported browsers, see Plan browser support (SharePoint Foundation 2010). |
If you are prompted for your user name and password, perform the following procedures:
- Add the SharePoint Central Administration Web site to the list of trusted sites
- Disable Internet Explorer Enhanced Security settings
If you receive a proxy server error message, perform the following procedure:
- Configure proxy server settings to bypass the proxy server for local addresses
For more information, see Getting Started with IEAK 8 (http://go.microsoft.com/fwlink/?LinkId=151359&clcid=0x409).
To add the SharePoint Central Administration Web site to the list of trusted sites
- In Internet Explorer, on the Tools menu, click Internet Options.
- On the Security tab, in the Select a zone to view or change security settings area, click Trusted Sites, and then click Sites.
- Clear the Require server verification (https:) for all sites in this zone check box.
- In the Add this Web site to the zone box, type the URL to your site, and then click Add.
- Click Close to close the Trusted Sites dialog box.
- Click OK to close the Internet Options dialog box.
To disable Internet Explorer Enhanced Security settings
- Click Start, point to All Programs, point to Administrative Tools, and then click Server Manager.
- In Server Manager, select the root of Server Manager.
-
In the Security Information section, click Configure IE ESC.
The Internet Explorer Enhanced Security Configuration dialog box opens.
- In the Administrators section, click Off to disable the Internet Explorer Enhanced Security settings, and then click OK.
To configure proxy server settings to bypass the proxy server for local addresses
- In Internet Explorer, on the Tools menu, click Internet Options.
- On the Connections tab, in the Local Area Network (LAN) settings area, click LAN Settings.
- In the Automatic configuration area, clear the Automatically detect settings check box.
- In the Proxy Server area, select the Use a proxy server for your LAN check box.
- Type the address of the proxy server in the Address box.
- Type the port number of the proxy server in the Port box.
- Select the Bypass proxy server for local addresses check box.
- Click OK to close the Local Area Network (LAN) Settings dialog box.
- Click OK to close the Internet Options dialog box.
Run the Farm Configuration Wizard
You have now completed Setup and the initial configuration of SharePoint Foundation 2010. You have created the SharePoint Central Administration Web site.
You can now create your farm and sites, and you can select services by using the Farm Configuration Wizard.
To run the Farm Configuration Wizard
- On the SharePoint Central Administration Web site, on the Configuration Wizards page, click Launch the Farm Configuration Wizard.
- On the Help Make SharePoint Better page, click one of the following options, and then click OK:
- Yes, I am willing to participate (Recommended.)
- No, I don’t want to participate.
- On the Configure your SharePoint farm page, click Walk me through the settings using this wizard, and then click Next.
- In the Service Account section, click a service account that you want to use to configure your services.
|
|
|
For security reasons, we recommend that you use a different account from the farm administrator account to configure services in the farm. If you decide to use an existing managed account — that is, an account that SharePoint Foundation is aware of — ensure that you click that option before you continue. |
- Select the services that you want to use in the farm, and then click Next.
|
|
|
For more information, see Configure services (SharePoint Foundation 2010) (http://technet.microsoft.com/library/88da9bdb-b7c2-4174-997b-d767b9b9c9ea(Office.14).aspx). If you are using Microsoft Office Web Apps, see Office Web Apps (Installed on SharePoint 2010 Products) (http://technet.microsoft.com/library/8a58e6c2-9a0e-4355-ae41-4df25e5e6eee(Office.14).aspx). |
-
On the Create Site Collection page, do the following:
- In the Title and Description section, in the Title box, type the name of your new site.
- Optional: In the Description box, type a description of what the site contains.
- In the Web Site Address section, select a URL path for the site.
- In the Template Selection section, in the Select a template list, select the template that you want to use for the top-level site in the site collection.
|
|
|
To view a template or a description of a template, click any template in the Select a template list. |
- Click OK.
- On the Configure your SharePoint farm page, review the summary of the farm configuration, and then click Finish.
-
Post-installation steps
After you install and configure SharePoint Foundation 2010, your browser window opens to the Central Administration Web site of your new SharePoint site. Although you can start adding content to the site or customizing the site,
we recommend that you first perform the following administrative tasks by using the SharePoint Central Administration Web site.
-
Configure usage and health data collection You can configure usage and health data collection in your server farm. The system writes usage and health data to the logging folder and to the logging database.
For more information, see Configure usage and health data collection (SharePoint Foundation 2010) (http://technet.microsoft.com/library/5c97fd40-008a-4fbc-8b3a-98244d8f0016(Office.14).aspx).
-
Configure diagnostic logging You can configure diagnostic logging that might be required after initial deployment or upgrade. The default settings are sufficient for most situations, but depending upon the business needs and lifecycle of the farm, you might want to change these settings.
For more information, see Configure diagnostic logging (SharePoint Foundation 2010) (http://technet.microsoft.com/library/a5641210-8224-4e11-9d93-4f96fa4c327c(Office.14).aspx).
-
Configure incoming e-mail You can configure incoming e-mail so that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail so that SharePoint sites can archive e-mail discussions as they happen, save e-mailed documents, and show e-mailed meetings on site calendars. In addition, you can configure the SharePoint Directory Management Service to provide support for e-mail distribution list creation and management.
For more information, see Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx).
-
Configure outgoing e-mail You can configure outgoing e-mail so that your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and notifications to site administrators. You can configure both the “From” e-mail address and the “Reply” e-mail address that appear in outgoing alerts.
For more information, see Configure outgoing e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ebb924d4-b9a2-4e40-bcb3-0ee582cc5a21(Office.14).aspx).
- Configure a mobile account You can configure a mobile account so that SharePoint sends text message (SMS) alerts to your, or site users’, mobile phones. For more information, see Configure a mobile account (SharePoint Foundation 2010) (http://technet.microsoft.com/library/36d537dc-2726-4594-a6e6-f7b2c035179f(Office.14).aspx).
-
Install and configure Remote BLOB Storage You can install and configure Remote BLOB Storage (RBS) for an instance of SQL Server 2008 that supports a SharePoint farm.
For more information, see Install and configure Remote BLOB Storage (SharePoint Foundation 2010) (http://technet.microsoft.com/library/6348e3a7-e2f4-4321-b145-da42269883aa(Office.14).aspx).
***BEGIN MOSS ONLY***
-
-
Deploy a single server with a built-in database (SharePoint Foundation 2010)
Published: May 12, 2010
This article describes how to perform a clean installation of Microsoft SharePoint Foundation 2010 on a single server with a built-in database.
In this article:
-
Overview
You can quickly publish a SharePoint site by deploying SharePoint Foundation 2010 on a single server with a built-in database. This configuration is useful if you want to evaluate SharePoint Foundation 2010 features and capabilities, such as collaboration, document management, and search. This configuration is also useful if you are deploying a small number of Web sites and you want to minimize administrative overhead. When you deploy SharePoint Foundation 2010 on a single server with a built-in database by using the default settings, Setup installs Microsoft SQL Server 2008 Express and the SharePoint product, and then the SharePoint Products Configuration Wizard creates the configuration database and content database for your SharePoint sites. Additionally, the SharePoint Products Configuration Wizard installs the SharePoint Central Administration Web site and creates your first SharePoint site collection.

Note:This article does not describe how to install SharePoint Foundation 2010 in a farm environment, or how to upgrade from previous releases of SharePoint Foundation. For more information about installing SharePoint Foundation 2010 on a single server farm, see Deploy a single server with SQL Server (SharePoint Foundation 2010). For more information about installing SharePoint Foundation 2010 on a multiple server farm, see Multiple servers for a three tier farm (SharePoint Foundation 2010) (http://technet.microsoft.com/library/246fb1c9-660e-40b5-860b-7d681f04505a(Office.14).aspx). For more information about upgrade, see Upgrading to SharePoint Foundation 2010 (http://technet.microsoft.com/library/91046a84-57a1-40cb-a32c-ff3395073dc9(Office.14).aspx).
Consider the following restrictions of this method of installation:
- You cannot install the single server with built-in database version of SharePoint Foundation on a domain controller.
- A SQL Server 2008 Express database cannot be larger than 4 GB.
-
Before you begin
Before you begin deployment, ensure that you have met all hardware and software requirements. For more information, see Hardware and software requirements (SharePoint Foundation 2010). Also, ensure that you perform a clean installation of SharePoint Foundation 2010. You cannot install the RTM version of SharePoint Foundation 2010 without first removing the beta version of SharePoint Foundation 2010
-
Install SharePoint Foundation 2010
To install and configure SharePoint Foundation 2010, follow these steps:
- Run the Microsoft SharePoint Products Preparation Tool, which installs all prerequisites to use SharePoint Foundation 2010.
- Run Setup, which installs SQL Server 2008 Express and the SharePoint product.
- Run SharePoint Products Configuration Wizard, which installs the SharePoint Central Administration Web site and creates your first SharePoint site collection.
- Configure browser settings.
- Perform post-installation steps.
|
|
|
To complete the following procedures, you must be a member of the Administrators group on the local computer. |
Run the Microsoft SharePoint Products Preparation Tool
Use the following procedure to install software prerequisites for SharePoint Foundation 2010.
To run the Microsoft SharePoint Products Preparation Tool
- Insert your SharePoint Foundation 2010 installation disc.
- On the SharePoint Foundation 2010 Start page, click Install software prerequisites.
|
|
|
Because the preparation tool downloads components from the Microsoft Download Center, you must have Internet access on the computer on which you are installing SharePoint Foundation. |
- On the Welcome to the Microsoft SharePoint Products Preparation Tool page, click Next.
- On the Installation Complete page, click Finish.
Run Setup
The following procedure installs SQL Server 2008 Express and the SharePoint product. At the end of Setup, you can choose to start the SharePoint Products Configuration Wizard, which is described later in this section.
To run Setup
- On the SharePoint Foundation 2010 Start page, click Install SharePoint Foundation.
- On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.
- On the Choose the installation you want page, click Standalone.
- When Setup finishes, a dialog box prompts you to complete the configuration of your server. Ensure that the Run the SharePoint Products Configuration Wizard now check box is selected.
- Click Close to start the configuration wizard.
|
|
|
If Setup fails, check the TEMP folder of the user who ran Setup. Ensure that you are logged in as the user who ran Setup, and then type %temp% in the location bar in Windows Explorer. If the path %temp% resolves to a location that ends in a “1” or “2”, you will need to navigate up one level to view the log files. The log file name is Microsoft SharePoint Foundation 2010 Setup (<timestamp>). |
|
|
|
To access the SharePoint Products Configuration Wizard, click Start, point to All Programs, and then click Microsoft SharePoint 2010 Products. If the User Account Control dialog box appears, click Continue. |
Run the SharePoint Products Configuration Wizard
The following procedure installs and configures the configuration database, the content database, and installs the SharePoint Central Administration Web site. It also creates your first SharePoint site collection.
To run the SharePoint Products Configuration Wizard
- On the Welcome to SharePoint Products page, click Next.
- In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.
- On the Configuration Successful page, click Finish.
|
|
|
If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint Foundation is installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\LOGS folder. |
|
|
|
If you are prompted for your user name and password, you might need to add the SharePoint Central Administration Web site to the list of trusted sites and configure user authentication settings in Internet Explorer. You might also want to disable the Internet Explorer Enhanced Security settings. Instructions for how to configure or disable these settings are provided in the following section. |
|
|
|
If you see a proxy server error message, you might need to configure your proxy server settings so that local addresses bypass the proxy server. Instructions for configuring proxy server settings are provided later in the following section. |
Configure browser settings
After you run the SharePoint Products Configuration Wizard, you should ensure that SharePoint Foundation works properly for local administrators in your environment by configuring additional settings in Internet Explorer.
|
|
|
If local administrators are not using Internet Explorer, you might need to configure additional settings. For information about supported browsers, see Plan browser support (SharePoint Foundation 2010). |
If you are prompted for your user name and password, perform the following procedures:
- Add the SharePoint Central Administration Web site to the list of trusted sites
- Disable Internet Explorer Enhanced Security settings
If you receive a proxy server error message, perform the following procedure:
- Configure proxy server settings to bypass the proxy server for local addresses
For more information, see Getting Started with IEAK 8 (http://go.microsoft.com/fwlink/?LinkId=151359&clcid=0x409).
To add the SharePoint Central Administration Web site to the list of trusted sites
- In Internet Explorer, on the Tools menu, click Internet Options.
- On the Security tab, in the Select a zone to view or change security settings area, click Trusted Sites, and then click Sites.
- Clear the Require server verification (https:) for all sites in this zone check box.
- In the Add this Web site to the zone box, type the URL to your site, and then click Add.
- Click Close to close the Trusted Sites dialog box.
-
Click OK to close the Internet Options dialog box.
If you are using a proxy server in your organization, use the following steps to configure Internet Explorer to bypass the proxy server for local addresses.
To disable Internet Explorer Enhanced Security settings
- Click Start, point to All Programs, point to Administrative Tools, and then click Server Manager.
- In Server Manager, select the root of Server Manager.
-
In the Security Information section, click Configure IE ESC.
The Internet Explorer Enhanced Security Configuration dialog box opens.
- In the Administrators section, click Off to disable the Internet Explorer Enhanced Security settings, and then click OK.
To configure proxy server settings to bypass the proxy server for local addresses
- In Internet Explorer, on the Tools menu, click Internet Options.
- On the Connections tab, in the Local Area Network (LAN) settings area, click LAN Settings.
- In the Automatic configuration area, clear the Automatically detect settings check box.
- In the Proxy Server area, select the Use a proxy server for your LAN check box.
- Type the address of the proxy server in the Address box.
- Type the port number of the proxy server in the Port box.
- Select the Bypass proxy server for local addresses check box.
- Click OK to close the Local Area Network (LAN) Settings dialog box.
- Click OK to close the Internet Options dialog box.
-
Post-installation steps
After you install SharePoint Foundation 2010, your browser window opens to the Central Administration Web site of your new SharePoint site. Although you can start adding content to the site or you can start customizing the site,
we recommend that you first perform the following administrative tasks by using the SharePoint Central Administration Web site:
-
Configure usage and health data collection You can configure usage and health data collection in your server farm. The system writes usage and health data to the logging folder and to the logging database.
For more information, see Configure usage and health data collection (SharePoint Foundation 2010) (http://technet.microsoft.com/library/5c97fd40-008a-4fbc-8b3a-98244d8f0016(Office.14).aspx).
- Configure diagnostic logging You can configure diagnostic logging that might be required after initial deployment or upgrade. The default settings are sufficient for most situations, but depending upon the business needs and lifecycle of the farm, you might want to change these settings. For more information, see Configure diagnostic logging (SharePoint Foundation 2010) (http://technet.microsoft.com/library/a5641210-8224-4e11-9d93-4f96fa4c327c(Office.14).aspx).
- Configure incoming e-mail You can configure incoming e-mail so that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail so that SharePoint sites can archive e-mail discussions as they happen, save e-mailed documents, and show e-mailed meetings on site calendars. In addition, you can configure the SharePoint Directory Management Service to provide support for e-mail distribution list creation and management. For more information, see Configure incoming e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/445dd72e-a63b-46d0-b92d-bcf0aa9d8d06(Office.14).aspx).
- Configure outgoing e-mail You can configure outgoing e-mail so that your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and notifications to site administrators. You can configure both the “From” e-mail address and the “Reply” e-mail address that appear in outgoing alerts. For more information, see Configure outgoing e-mail (SharePoint Foundation 2010) (http://technet.microsoft.com/library/ebb924d4-b9a2-4e40-bcb3-0ee582cc5a21(Office.14).aspx).
- Configure a mobile account You can configure a mobile account so that SharePoint sends text message (SMS) alerts to your, or site users’, mobile phones. For more information, see Configure a mobile account (SharePoint Foundation 2010) (http://technet.microsoft.com/library/36d537dc-2726-4594-a6e6-f7b2c035179f(Office.14).aspx).
- Install and configure Remote BLOB Storage You can install and configure Remote BLOB Storage (RBS) for an instance of SQL Server 2008 that supports a SharePoint server farm. For more information, see Install and configure Remote BLOB Storage (SharePoint Foundation 2010) (http://technet.microsoft.com/library/6348e3a7-e2f4-4321-b145-da42269883aa(Office.14).aspx).
-
-
Configure Windows Server Backup
If you want to use Windows Server Backup with SharePoint Foundation 2010, you must register the SharePoint 2010 VSS Writer with Windows Server Backup by running the stsadm -o registerwsswriter command. For more information, see Registerwsswriter: Stsadm operation (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc287616.aspx).
-
Roadmap to SharePoint Foundation 2010 content
Published: May 12, 2010
This article describes the content available for IT professionals to assist you when you are planning, deploying, administering, and troubleshooting SharePoint Foundation 2010.
For SharePoint Foundation 2010 developer content, see the SharePoint Developer Center (http://go.microsoft.com/fwlink/?LinkId=159918).
Content resources
The SharePoint Foundation 2010 TechCenter (http://go.microsoft.com/fwlink/?LinkId=188950) is your primary gateway to in-depth technical information about SharePoint Foundation 2010. Through the TechCenter, you can access the following:
- SharePoint Foundation 2010 Resource Centers (http://go.microsoft.com/fwlink/?LinkId=188951) Resource centers provide specific links to more information specific to a particular feature of SharePoint Foundation 2010. You can find resource centers for features such as installation and deployment, Business Connectivity Services, enterprise content management, and enterprise search, to name a few.
- SharePoint Foundation 2010 Downloads (http://go.microsoft.com/fwlink/?LinkId=188952) Go to this page to download service packs, add-ins, tools, and trial software to help you optimize your SharePoint Foundation organization.
- SharePoint Foundation 2010 library (http://technet.microsoft.com/library/7019bcb6-43fe-455b-889d-b845cb43286f(Office.14).aspx) The library contains the most up-to-date IT pro content. This content is reviewed and approved by the SharePoint Foundation product team and will evolve over the life cycle of SharePoint Foundation 2010. Also make sure that you check out Newly published content for SharePoint Foundation 2010 (http://technet.microsoft.com/library/8a9690e4-6917-4aab-82ce-cdbe989a2053(Office.14).aspx) in the library. This article contains a list of new or updated library content and is also available as an RSS feed. (http://go.microsoft.com/fwlink/?LinkId=188953). It is updated whenever a new article is published or an existing article is updated.
- SharePoint Foundation 2010 support (http://go.microsoft.com/fwlink/?LinkId=188954) Locate support and troubleshooting resources for SharePoint Foundation. You can search the Microsoft Knowledge Base, TechNet, or blogs for additional help.
Offline resources
If you are working offline and need access to library articles, the following option is available to you:
- SharePoint Foundation 2010 Beta Technical Library in Compiled Help format (http://go.microsoft.com/fwlink/?LinkId=188955) This downloadable .chm file is updated monthly and includes all articles published to the library as of the .chm file’s release date.
Additional resources
The following visual resources supplement the library articles and can assist you when you plan your projects:
- Technical diagrams (SharePoint Foundation 2010) (http://technet.microsoft.com/library/99462701-d16a-4477-af4e-36c8f5083dbf(Office.14).aspx) These poster-size models provide a visual representation of recommended solutions and correspond to various articles in the library. You can modify these models by using Microsoft Office Visio 2007 to reflect your plans for SharePoint Foundation and how it will fit into your own environment.
Community resources
You can use the community resources to learn more about SharePoint Foundation 2010 and to foster discussion, ask questions, and exchange ideas about your experiences with SharePoint Foundation 2010:
- Microsoft SharePoint Team Blog (http://go.microsoft.com/fwlink/?LinkID=82560) This is the official blog of the SharePoint product group. It includes articles written by members of the product team, and product announcements and updates.
- To The SharePoint (http://go.microsoft.com/fwlink/?LinkId=188956) This is the IT pro documentation team blog. This blog includes documentation highlights and announcements for SharePoint Foundation 2010.
- SharePoint 2010 forums (http://go.microsoft.com/fwlink/?LinkId=188957) The forum provides a place for users and SharePoint Foundation product team members to discuss the product.
Windows IT Pro Best Practices for Protecting Your Windows Server 2012 and Hyper-V Based Infrastructures
Windows IT Pro
Best Practices for
Protecting Your Windows
Server 2012 and Hyper-V
Based Infrastructures
sponsored by
Tech Advisor • Symantec | p. 2
Many administrators remember the challenges of architecting a
backup solution for their datacenter, ensuring all the right data
was protected and finding solutions to files that were open
during backup processes. The Virtual Shadow Copy Service (VSS)
completely changed how Windows operating systems were
backed up. Application vendors can now create components
(VSS writers) that the VSS backup framework could call, allowing
an application to flush all transactions and data to disk, thus
ensuring a backup that would be usable in a restore scenario by
having all application data on disk in a consistent state.
Looking at a datacenter today and that of 10 years ago demonstrates
the shift in how IT datacenters are architected. Organizations
have moved from one operating system per server to many
operating systems per server, which is achieved through server
virtualization. Windows Server 2012 provides many new features,
including a new version of Hyper-V. The new hypervisor has seen
large increases in its scalability, allowing for virtual machines
with 64 virtual processors, a terabyte of memory, and virtual hard
disks that are 64 terabytes in size. Additional new features include
virtual fibre channel, SMB 3.0 support allowing virtual machines
to be stored on SMB file shares, and shared nothing live migration
that allow virtual machines to be migrated between hosts that
are not clustered or that share storage with no downtime. The
new scalability and functionality means systems that were previously
not virtualized due to limitations in virtualization are now
capable of being virtualized. The percentage of virtual operating
systems will increase and very large, critical systems will now be
virtualized, making the backup of the virtualization environment
even more important.
The adoption of virtualization adds a new dimension to your organization’s
backup plans and this paper will walk through some
key considerations when hosting services on Windows Server
2012 Hyper-V.
The importance of backups, even in a
virtual environment
Virtualization offers a number of very useful features related to
the state of a virtual machine that can sometimes seem to reduce
the need for backups; however, this is not the case. Likewise
many services offer replication capabilities that are also not
replacements for solid backup processes.
Snapshots are a common feature of virtualization platforms,
including Hyper-V, that allow a point-in-time view of a virtual
machine to be taken. If a virtual machine is running when a
snapshot is taken its current storage content is saved and its
memory and device state is stored. While snapshots provide a
point-in-time copy of a virtual machine the operating system
within the virtual machine is unaware that a snapshot has been
taken, which means data on disk may not be in a consistent state
because the VSS backup framework is not utilized. Additionally,
when a snapshot is applied to a virtual machine it restores a virtual
machine to that point in time and the OS has no knowledge
that its state has been changed back in time. This may cause serious
problem for certain types of service and can cause security
and data problems. Typically, snapshots should be avoided in any
production environment; they are best utilized in development
environments where it can be very useful as part of testing or
troubleshooting to be able to revert an operating system to a
known state repeatedly.
Hyper-V also provides a feature called Hyper-V Replica, which is
an asynchronous replication of storage changes of enabled virtual
machines every five minutes to an alternate Hyper-V server in
a separate location. The goal of this feature is to provide disaster
recovery capability for organizations using inbox capabilities
without the need for separate storage replication technologies.
The typical Hyper-V Replica operation works by sending the content
of the Hyper-V Replica log file, which contains the changes
to the storage over the previous five minutes, to the alternate
Hyper-V server, which then merges the changes into its copy of
the virtual hard disks. Like a snapshot, Hyper-V Replica is not typically
notifying the operating system of the storage replication,
making the data on disk possibly inconsistent. Hyper-V Replica
does offer the capability to initiate a VSS request to the virtual
machine periodically, which forces data to be flushed to disk,
making that specific Hyper-V Replica application data consistent.
However, this feature is in no way designed to be a backup solution
and requires a completely separate Hyper-V server for the
continuous receiving of five-minute storage deltas.
Both snapshots and Hyper-V Replica only work with virtual hard
disks, which means if applications are storing data using pass-
through storage or on storage accessed via iSCSI or virtual fibre
channel, then the data is not backed up. Even more importantly
both snapshots and Hyper-V Replica are only aware at the operating
system level rather than understanding specific applications
and data groups within the virtual machine, which would
severely limit the granularity of restoration.
Where to perform backups
Traditionally, a backup is performed via a backup agent running
on the operating system being backed up. The backup agent
communicates to a central backup service, sending the data to
be protected. For operating systems that are virtualized this approach
can still be used; however, there is another option.
For Hyper-V supported guest operating systems (Windows Server
2003 and above), integration services are provided that enhance
the functionality and performance of the operating systems running
within the virtual machines. Once installed the integration
services add a number of specific capabilities between the operating
system running in the virtual machine and the Hyper-V host.
One of these integrations is “Backup (volume snapshot),” which allows
the Hyper-V host to notify the guest operating system within
the virtual machine when a backup it taken of the virtual machine
at the Hyper-V host. The guest operating system then calls all the
registered VSS writers within the virtual machine, which causes all
the applications to flush information to disk and then notifies the
Hyper-V host that the virtual machines virtual hard disks can be
backed up, thus ensuring an app-consistent backup.
Remember that the granularity of what you are protecting and,
therefore, what can be restored is the most important factor.
When a backup agent is running within the virtual machine on
the guest OS it has direct interaction with registered VSS writers
and knowledge of applications running within the operating
system. This enables the backup to be configured to backup
specific units of application data; for example, for a database
server specific databases could be protected; for a mail server,
specific mailboxes. When the backup is application aware the
restore can equally be application aware, offering application-
specific restoration. If, however, the virtual machine was backed
up at the Hyper-V host level—although the VSS writers in the
virtual machine are still called to ensure the data on disk is in a
consistent state—the data being backed up is the entire virtual
machine, which means at restoration time the only thing that
could be restored is the entire virtual machine or perhaps files
from the associated hard disks. This would mean that backing
up within the virtual machine would be the best option where
application-aware backups are required. However, some backup
solutions on the market take the backup pass-through capability
native to Hyper-V to another functional level by also exposing
application awareness from the virtual machines. This means that
even though backups are taken at the Hyper-V host level, the
backups can still be configured to back up particular application
data and restore at application data unit levels.
Another aspect of the virtual machine’s data must be considered
when performing backups: the actual location of the virtual
machine configuration and virtual hard disks. In basic scenarios
the virtual hard disks and configuration files for virtual machines
are stored on direct-attached storage. However, for environments
that leverage clusters of Hyper-V hosts or that wish to use consolidated
storage, then storage local to a host is not optimal and
shared storage must be used.
Windows Server 2008 R2 introduced Cluster Shared Volumes
(CSV,) which allow an NTFS formatted LUN on a SAN to be concurrently
accessed by all hosts in a cluster. This removed previous
problems associated with dismounting and mounting LUNs
when a virtual machine is migrated between hosts. A special process
is required to back up CSV-enabled volumes, which means
it’s critical that your backup solution has CSV support. Windows
Server 2012 provides improvements to CSV processes by labelling
CSV volumes as CSVFS instead of NTFS, making them easy to
identify. In addition, backups of CSV volumes no longer have to
be performed on a specific member of the cluster, known as the
coordinator node. In Windows Server 2012 volume-level backup
of a CSV can be performed from any node connecting to the CSV
and backups do not interfere with running virtual machines.
Another new shared storage option for Windows Server 2012
Hyper-V virtual machines is to use a Server Message Block (SMB)
3.0 file share. This file share can be hosted on a Windows Server
2012 file server or cluster or a storage appliance with SMB 3.0
support. Windows Server 2012 includes a new “File Server VSS
Agent Service,” which must be enabled on all servers acting as
SMB 3.0 servers for Hyper-V. This enables remote VSS backups
to be performed. This is a very new feature so very few backup
solutions have support for remote VSS SMB backups at the time
of writing. However, talk to your backup vendor to ascertain their
plans and timing for SMB 3.0 support. If your organization wishes
to leverage SMB 3.0 prior to support from the backup solution,
one option is to run the backup agent within the virtual machine
to ensure protection of the operating systems and applications.
What to back up
With all the different components in a virtualized datacenter and
the replication capabilities of many services it can often seem
confusing to decide which operating system instances and which
copies of data should be backed up. Often there is no absolute
right or wrong answer, but there are certain must haves—and
generally you can’t back up too much. It’s better to have
redundant backups of the same data than to miss data.
As previously discussed it’s critical that all data in the organization is
backed up, even if it’s also replicated because backup and
replication meet different needs. But if a data set is replicated three
times is it necessary to back up all three copies? For example,
Exchange has the concept of Database Availability Groups (DAG)
where mailbox databases are stored on multiple servers. The
general rule to follow is to make sure all unique data is backed up
by at least one backup process, which means if a database is
replicated between three services make sure at least one of them is
backed up. The same applies to domain controllers within the
same domain. Typically, domain controllers are highly replaceable
so if a domain controller has a problem another one can be
provisioned in its place very quickly. But it’s important there is a
backup of the Active Directory routinely on at least one, and ideally
two, domain controllers. Care must be taken to ensure that backup
is not lost as databases are moved between different servers and
there is a risk if backups are not running on all servers that a data
set falls out of scope of a backup. As a side note if certain copies are
not backed up its important to ensure there are no negative
effects, such as log files never being truncated or deleted which
normally occurs as part of a backup.
It’s important to back up the operating systems and the
application installs that utilize application data because often it
can be very time consuming to perform an installation of a server
application. Thus restoring the server operating system and the
installed application is the most expedient recovery possible.
Ensure any servers that are required for the primary workload
being backed up are also backed up and recoverable. For
example, a service may have requirements on Active Directory,
on DNS or another server running a middleware service. Make
sure all these systems are backed up to provide protection in a
disaster situation where whole racks of servers or even entire
datacenters are lost.
For the Hyper-V host backup it is important in the event of a server
failure that the virtual machines are not affected, so always use
clusters of Hyper-V hosts which enable virtual machines to move
between hosts. It’s critical to replace failed hosts quickly to restore
resiliency from further failure. Performing backups of Hyper-V hosts
provides a very efficient way of restoring this protection.
When considering the backup of the Hyper-V host and virtual
machines from the host do not back up the same guest
operating system twice. If backups are being performed within
the virtual machine via a backup agent installed on the guest
operating system inside the virtual machine, do not also back up
the virtual machine from the Hyper-V host. This leads to wasted
space and possible conflicts.
Putting it all together
Given how critical backups are to every environment one aspect
that is often overlooked in a process that often backs up to disk is
ensuring protection of the backup itself. While backing up to
disks local to the datacenter provides great performance and very
fast restores it leaves the backup vulnerable to the same disaster
scenarios that could affect the protected servers themselves.
Therefore, always ensure backups are also stored offsite (e.g., to a
second location via disk replication, to a repository on tape, or
replicated to public cloud-based storage).
Additionally, ensure backup and restore processes are frequently
tested and revised. Performing regular test recoveries helps
ensure in the event the backup is really needed it contains the
required information and can be used as desired. Any time a new
system is added to the environment ensure backup and restore
processes are updated accordingly to include the new system
and any systems it is dependent upon.
By following these basic guidelines you can help ensure that your data
and your organization are well protected in the most efficient way.
Getting Started as an Entrepreneur – Wikibooks, open books for an open world
Unleashing the Ideavirus
Unleashing the Ideavirus 1 http://www.ideavirus.com
Unleashing the Ideavirus
By Seth Godin
Foreword by Malcolm Gladwell
©2000 by Do You Zoom, Inc.
You have permission to post this, email this, print this and pass it along for free to
anyone you like, as long as you make no changes or edits to its contents or digital
format. In fact, I’d love it if you’d make lots and lots of copies. The right to bind this
and sell it as a book, however, is strictly reserved. While we’re at it, I’d like to keep
the movie rights too. Unless you can get Paul Newman to play me.
Ideavirus™ is a trademark of Do You Zoom, Inc. So is ideavirus.com™.
Designed by Red Maxwell
You can find this entire manifesto, along with slides and notes and other good stuff, at
This version of the manifesto is current until September 17, 2000. After that date, please go
to http://www.ideavirus.com and get an updated version. You can buy this in book form on
September 1, 2000.
This book is dedicated to Alan Webber and Jerry Colonna. Of course.
Unleashing the Ideavirus 2 http://www.ideavirus.com
STEAL THIS IDEA!
Here’s what you can do to spread the word about Unleashing the Ideavirus:
1. Send this file to a friend (it’s sort of big, so ask first).
2. Send them a link to http://www.ideavirus.com so they can download it themselves.
3. Visit http://www.fastcompany.com/ideavirus to read the Fast Company article.
4. Buy a copy of the hardcover book at
http://www.amazon.com/exec/obidos/ASIN/0970309902/permissionmarket.
5. Print out as many copies as you like.
Unleashing the Ideavirus 3 http://www.ideavirus.com
Look for the acknowledgments at the end. This is, after all, a new digital format, and you want to get right to it!
The #1 question people ask me after reading
Permission Marketing:
ÒSo, how do we get attention to ask for
permission in the first place?”
This manifesto is the answer to that question.
Unleashing the Ideavirus 4 http://www.ideavirus.com
Foreword
The notion that an idea can become contagious, in precisely the same way that a virus does,
is at once common-sensical and deeply counter-intuitive. It is common-sensical because all of
us have seen it happen: all of us have had a hit song lodged in our heads, or run out to buy a
book, or become infected with a particular idea without really knowing why. It is counterintuitive,
though, because it doesn’t fit with the marketer’s traditional vision of the world.
Advertisers spent the better part of the 20th century trying to control and measure and
manipulate the spread of information—to count the number of eyes and ears that they could
reach with a single message. But this notion says that the most successful ideas are those that
spread and grow because of the customer’s relationship to other customers—not the
marketer’s to the customer.
For years, this contradiction lay unresolved at the heart of American marketing. No longer.
Seth Godin has set out to apply our intuitive understanding of the contagious power of
information—of what he so aptly calls the ideavirus—to the art of successful
communication. “Unleashing the Ideavirus” is a book of powerful and practical advice for
businesses.
But more than that, it is a subversive book. It says that the marketer is not—and ought not
to be—at the center of successful marketing. The customer should be. Are you ready for that?
Malcolm Gladwell
Author
The Tipping Point
Unleashing the Ideavirus 5 http://www.ideavirus.com
Introduction
If you don’t have time to read the whole book, here’s what it says:
Marketing by interrupting people isn’t cost-effective anymore. You
can’t afford to seek out people and send them unwanted marketing
messages, in large groups, and hope that some will send you money.
Instead, the future belongs to marketers who establish a foundation
and process where interested people can market to each other. Ignite
consumer networks and then get out of the way and let them talk.
If you’re looking for mindblowing new ideas, you won’t find them in this, or any other
marketing book. Guerrilla marketing, 1:1 marketing, permission marketing—these ideas are
not really new, but they are thoughtful constructs that let you figure out how to do
marketing better. The fact is, if we built factories as badly as we create advertising campaigns,
the country would be in a shambles. This book will help you better understand the timehonored
marketing tradition of the ideavirus, and help you launch your own.
Questions the book answers:
1.
Why is it foolish to launch a new business with millions of dollars in TV ads?
2.
Are the market leaders in every industry more vulnerable to sudden successes by the
competition than ever before?
3.
Should book publishers issue the paperback edition of a book before the hardcover?
4.
What’s the single most important asset a company can create—and what is the simple
thing that can kill it?
5.
Every ad needs to do one of two things to succeed…yet most ads do neither. What’s the
right strategy?
6.
Does the Net create a dynamic that fundamentally changes the way everything is
marketed?
7.
How can every business…big and small…use ideavirus marketing to succeed?
Unleashing the Ideavirus 6 http://www.ideavirus.com
Foreword……………………………………………………………………………………………………………………….5
Introduction……………………………………………………………………………………………………………………6
SECTION 1: Why Ideas Matter…………………………………………………………………………………… 11
Farms, Factories And Idea Merchants ………………………………………………………………………………….12
Why Are Ideaviruses So Important?…………………………………………………………………………………….21
And Five Things Ideaviruses Have In Common……………………………………………………………………….22
Seven Ways An Ideavirus Can Help You: ……………………………………………………………………………… 23
The Sad Decline of Interruption Marketing ………………………………………………………………………….. 24
We Live In A Winner-Take-Almost-All World………………………………………………………………………….. 25
The Traffic Imperative: Why Sites Fail ……………………………………………………………………………….. 28
We Used To Make Food. We Used To Make Stuff. Now We Make Ideas…………………………………………. 30
People Are More Connected Than They Ever Were Before. We Have Dramatically More Friends Of Friends
And We Can Connect With Them Faster And More Frequently Than Ever……………………………………….31
ThereÕs A Tremendous Hunger To Understand The New And To Remain On The Cutting Edge……………34
While Early Adopters (The Nerds Who Always Want To Know About The Cool New Thing In Their Field)
Have Always Existed, Now WeÕve Got More Nerds Than Ever Before. If YouÕre Reading This, YouÕre A
Nerd!………………………………………………………………………………………………………………………….. 35
Ideas Are More Than Just Essays And Books. Everything From New Technology To New Ways Of Creating
To New Products Are Winning Because Of Intelligent Ideavirus Management By Their Creators………..36
The End Of The Zero Sum Game ………………………………………………………………………………………… 37
SECTION 2: How To Unleash An Ideavirus…………………………………………………………………..39
While It May Appear Accidental, ItÕs Possible To Dramatically Increase The Chances Your Ideavirus Will
Catch On And Spread. ……………………………………………………………………………………………………..40
The Heart Of The Ideavirus: Sneezers ………………………………………………………………………………….41
Sneezers Are So Important, We Need To Subdivide Them………………………………………………………… 42
The Art Of The Promiscuous …………………………………………………………………………………………….. 47
ItÕs More Than Just Word Of Mouth ……………………………………………………………………………………..51
An Ideavirus Adores A Vacuum …………………………………………………………………………………………. 52
Unleashing the Ideavirus 7 http://www.ideavirus.com
Once It Does Spread, An Ideavirus Follows A Lifecycle. Ignore The Lifecycle And The Ideavirus Dies Out.
Feed It Properly And You Can Ride It For A Long Time…………………………………………………………….54
Viral Marketing Is An Ideavirus, But Not All Ideaviruses Are Viral Marketing ……………………………….. 55
What Does It Take To Build And Spread An Ideavirus? ……………………………………………………………. 57
There Are Three Key Levers That Determine How Your Ideavirus Will Spread:………………………………60
Ten Questions Ideavirus Marketers Want Answered ………………………………………………………………. 64
Five Ways To Unleash An Ideavirus ……………………………………………………………………………………. 65
SECTION THREE: The Ideavirus Formula ……………………………………………………………………. 78
Managing Digitally-Augmented Word Of Mouth……………………………………………………………………… 79
Tweak The Formula And Make It Work …………………………………………………………………………………80
Advanced Riffs On The Eight Variables You Can Tweak In Building Your Virus………………………………. 85
Hive …………………………………………………………………………………………………………………………… 88
Velocity………………………………………………………………………………………………………………………. 92
Vector………………………………………………………………………………………………………………………… 94
Medium ………………………………………………………………………………………………………………………. 96
SMOOTHNESS: It Would All Be Easy If We Had Gorgons……………………………………………………………. 98
Persistence …………………………………………………………………………………………………………………100
Amplifier …………………………………………………………………………………………………………………….102
SECTION 4: Case Studies and Riffs…………………………………………………………………………..104
The Vindigo Case Study…………………………………………………………………………………………………..105
Saving The World With An Ideavirus ………………………………………………………………………………….. 107
Moving Private To Public…………………………………………………………………………………………………..111
YouÕre In The Fashion Business! ………………………………………………………………………………………..113
The Money Paradox ………………………………………………………………………………………………………..117
Think Like A Music Executive (Sometimes)…………………………………………………………………………..119
Is That Your Final Answer?……………………………………………………………………………………………….121
A Dozen ideaviruses Worth Thinking About…………………………………………………………………………. 123
Why I Love Bestseller Lists………………………………………………………………………………………………124
How A Parody Of Star Wars Outsold Star Wars …………………………………………………………………….. 127
Unleashing the Ideavirus 8 http://www.ideavirus.com
Wassup? ……………………………………………………………………………………………………………………..129
Judging a book by its cover ……………………………………………………………………………………………..131
Being The Most ……………………………………………………………………………………………………………. 133
In Defense Of World Domination ………………………………………………………………………………………. 135
If YouÕre A Member Of The Academy, You Go To Movies For Free …………………………………………….. 137
How An Ideavirus Can Drive The Stock Market …………………………………………………………………….. 139
Bumper Sticker Marketing……………………………………………………………………………………………….142
No, You Go First! ………………………………………………………………………………………………………….. 143
Digital Media Wants to Be Free…………………………………………………………………………………………145
Van Gogh Lost His Ear To Prove A Point ……………………………………………………………………………..148
Answering InaÕs Question………………………………………………………………………………………………..150
Crossing The Chasm With An Ideavirus ……………………………………………………………………………….152
The Myth Of The Tipping Point ………………………………………………………………………………………….156
The Compounding Effect …………………………………………………………………………………………………158
Bill GatesÕ Biggest Nightmare…………………………………………………………………………………………..160
Hey, Skinny!…………………………………………………………………………………………………………………164
Get Big Fast? The Mistake So Many Companies MakeÉ…………………………………………………………..165
The Heart Of Viral Marketing……………………………………………………………………………………………168
The Great Advertising Paradox………………………………………………………………………………………….171
Permission: The Missing Ingredient…………………………………………………………………………………… 174
How A Virus And Permission Team Up To Find Aliens…………………………………………………………….. 176
The Art of Creating an Ideavirus………………………………………………………………………………………. 177
Is He Really More Evil Than Satan Himself? ………………………………………………………………………… 178
Case Study: Why Digimarc Is Going To Fail…………………………………………………………………………..179
Why Are These Cows Laughing?…………………………………………………………………………………………181
Never Drink Alone …………………………………………………………………………………………………………183
The Power Of Parody ……………………………………………………………………………………………………..185
Bee Stings And The Measles …………………………………………………………………………………………….186
But IsnÕt It Obvious?………………………………………………………………………………………………………187
Unleashing the Ideavirus 9 http://www.ideavirus.com
Your CompanyÕs Worst Enemy ………………………………………………………………………………………….189
Step By Step, Ideavirus Tactics: ……………………………………………………………………………………….192
The Future Of The Ideavirus: What Happens When Everyone Does It? ………………………………………..194
Acknowledgments ………………………………………………………………………………………………..196
Unleashing the Ideavirus 10 http://www.ideavirus.com
SECTION 1: Why Ideas Matter
STEAL THIS IDEA!
Here’s what you can do to spread the word about Unleashing the Ideavirus:
1. Send this file to a friend (it’s sort of big, so ask first).
2. Send them a link to http://www.ideavirus.com so they can download it themselves.
3. Visit http://www.fastcompany.com/ideavirus to read the Fast Company article.
4. Buy a copy of the hardcover book at
http://www.amazon.com/exec/obidos/ASIN/0970309902/permissionmarket.
5. Print out as many copies as you like.
Unleashing the Ideavirus 11 http://www.ideavirus.com
Farms, Factories And Idea Merchants
Imagine for a second that you’re at your business school reunion, trading lies and bragging
about how successful you are and are about to become. Frank the jock talks about the dotcom
company he just started. Suzie the ex-banker is now focusing her energy on rebuilding
Eastern Europe. And then the group looks at you. With a wry look of amusement, you
answer:
“Well, the future—the really big money—is in owning a farm. A small one, maybe 100
acres. I intend to invest in a tractor of course, and expect that in just a few years my husband
and I can cash out and buy ourselves a nice little brownstone in the city.”
Ludicrous, no? While owning a farm may bring tremendous lifestyle benefits, it hasn’t been a
ticket to wealth for, say, 200 years.
What about owning a factory then? Perhaps the road to riches in the new economy would be
to buy yourself a hot-stamping press and start turning out steel widgets. Get the UAW to
organize your small, dedicated staff of craftsmen and you’re on your way to robber-baron
status.
Most of us can agree that the big money went out of owning a factory about thirty years ago.
When you’ve got high fixed costs and you’re competing against other folks who also know
how to produce both quantity and quality, unseemly profits fly right out the window.
Fact is, the first 100 years of our country’s history were about who could build the biggest,
most efficient farm. And the second century focused on the race to build factories. Welcome
to the third century, folks. The third century is about ideas.
Alas, nobody has a clue how to build a farm for ideas, or even a factory for ideas. We
recognize that ideas are driving the economy, ideas are making people rich and most
important, ideas are changing the world. Even though we’re clueless about how to best
organize the production of ideas, one thing is clear: if you can get people to accept and
Unleashing the Ideavirus 12 http://www.ideavirus.com
embrace and adore and cherish your ideas, you win. You win financially, you gain power and
you change the world in which we live.
So how do you win? What do you need to do to change the status quo of whatever industry
you’re in, or, if you’re lucky, to change the world?
If you’re a farmer, you want nothing more than a high price for your soybeans. If you’re a
manufacturer of consumer goods, you want a display at the cash register at Wal-Mart. But
what if you’re an idea merchant?
The holy grail for anyone who trafficks in ideas is this: to unleash an ideavirus.
An idea that just sits there is worthless. But an idea that moves and grows and infects
everyone it touches… that’s an ideavirus.
In the old days, there was a limit on how many people you could feed with the corn from
your farm or the widgets from your factory. But ideas not only replicate easily and well, they
get more powerful and more valuable as you deliver them to more people.
How does an ideavirus manifest itself? Where does it live? What does it look like? It’s useful
to think of ideas of every sort as being similar. I call them manifestos. An idea manifesto is a
powerful, logical “essay” that assembles a bunch of existing ideas and creates a new one.
Sometimes a manifesto is a written essay. But it can be an image, a song, a cool product or
process… the medium doesn’t matter. The message does. By lumping all sorts of
ideas—regardless of format—into the same category (manifestos) it’s much easier to think of
them as versions of the same thing. As long as you can use your manifesto to change the way
people think, talk or act… you can create value.
Definition: MEDIUM In order to move, an idea has to be encapsulated in a medium. It
could be a picture, a phrase, a written article, a movie, even a mathematical formula (e=mc2).
The Medium used for transmitting the ideavirus determines how smooth it is as well as the
velocity of its growth. A medium is not a manifesto—every idea is a manifesto, trying to
make its point, and the medium is the substance that the idea lives in.
Unleashing the Ideavirus 13 http://www.ideavirus.com
Not only is this an essay about ideas and ideaviruses…it’s also a manifesto striving to become
an ideavirus! If this manifesto changes your mind about marketing and ideas, maybe you’ll
share it with a friend. Or two. Or with your entire company. If that happens, this idea will
become an ideavirus, and spread and gain in value.
We live in a world where consumers actively resist marketing. So it’s imperative to stop
marketing at people. The idea is to create an environment where consumers will market to
each other.
Is an ideavirus a form of marketing? Sure it is. And today, marketing is all there is. You don’t
win with better shipping or manufacturing or accounts payable. You win with better
marketing, because marketing is about spreading ideas, and ideas are all you’ve got left to
compete with.
The future belongs to the people who unleash ideaviruses.
What’s an ideavirus? It’s a big idea that runs amok across the target audience. It’s a
fashionable idea that propagates through a section of the population, teaching and changing
and influencing everyone it touches. And in our rapidly/instantly changing world, the art
and science of building, launching and profiting from ideaviruses is the next frontier.
Have you ever heard of Hotmail? Ever used it? If so, it’s not because Hotmail ran a lot of TV
ads (they didn’t). It’s because the manifesto of free email got to you. It turned into an
ideavirus. Someone you know and trust infected you with it. What about a Polaroid
camera… was your first exposure (no pun intended!) in a TV ad, or did you discover it when
a friend showed you how cool the idea of an instant photograph was?
Sometimes it seems like everyone is watching the same TV show as you, or reading the same
book, or talking about the same movie or website. How does that happen? It usually occurs
because the idea spreads on its own, through an accidental ideavirus, not because the
company behind the product spent a ton of money advertising it or a lot of time
Unleashing the Ideavirus 14 http://www.ideavirus.com
orchestrating a virus. And how the idea spreads, and how to make it spread faster—that’s the
idea behind unleashing an ideavirus.
Word of mouth is not new—it’s just different now. There were always ideaviruses—gossip or
ideas or politics that spread like wildfire from person to person. Without running an ad or
buying a billboard, Galileo managed to upset all of Pisa with his ideas. Today, though,
ideaviruses are more important and more powerful than ever. Ideaviruses are easier to launch
and more effective. Ideaviruses are critical because they’re fast, and speed wins and speed
kills—brands and products just don’t have the time to develop the old way. Ideaviruses give
us increasing returns—word of mouth dies out, but ideaviruses get bigger. And finally,
ideaviruses are the currency of the future. While ideaviruses aren’t new, they’re important
because we’re obsessed with the new, and an ideavirus is always about the new.
Remember the slogan, “Only her hairdresser knows for sure?” That was classic brand
marketing, and it flew in the face of word of mouth. It was an ad for a product that was
supposed to be a secret—a secret between you, your hairdresser and Clairol.
A few years later, Herbal Essence took a totally different tack… they tried to encourage you
to tell your friends. But while word of mouth works great among the people who use a
product and their immediate friends—if I love your story or hate your service, I’ll tell a few
friends—it dies out fast. There’s no chance a friend of a friend is going to tell you about my
horrible experience on United Airlines or how much I loved flying on Southwest. Word of
mouth fades out after a few exchanges.
But now, aided by the Net and abetted by the incredible clutter in our universe, ideaviruses
are spreading like wildfire. We’re all obsessed with ideas because ideas, not products, are the
engine of our new economy.
I wore Converse sneakers growing up… so did you. But the shareholders of Converse never
profited from the idea of the shoe—they profited from the manufacture of a decent sneaker.
If two sneakers were for sale, you bought the cheaper one.
Unleashing the Ideavirus 15 http://www.ideavirus.com
It took Converse generations to build a brand and years to amortize a factory and they were
quite happy to extract a modest profit from every pair of sneakers sold, because Converse
knew their factory would be around tomorrow and the day after that. So sneakers, like
everything else, were priced by how much they cost, and sold one pair at a time by earnest
shoe salesmen who cared about things like how well the shoes fit.
Converse could take their time. They were in this for the long haul. Those days are long
gone. Twenty years later, it’s the idea of Air Jordan sneakers, not the shoe, that permits Nike
to sell them for more than $100. It’s the sizzle, not the fit. The idea makes Nike outsized
profits. And Nike knows that idea won’t last long, so they better hurry—they need another
ideavirus, fast.
In the old days, we used to sneer at this and call it a fad. Today, everything from presidential
politics to music to dentistry is driven by fads—and success belongs to marketers who
embrace this fact.
Source: Forrester Research
It took 40 years for radio to have ten million users. By then, an industry had grown that
could profit from the mass audience. It took 15 years for TV to have ten million users. It
Unleashing the Ideavirus 16 http://www.ideavirus.com
only took 3 years for Netscape to get to 10 million, and it took Hotmail and Napster less
than a year. By aggregating mass audiences to themselves (and not having to share them with
an entire industry), companies like Netscape and Hotmail are able to realize huge profits,
seemingly overnight. And they do it by spreading ideaviruses.
Ideas can now be carried in the ether. Because the medium for carrying ideas is fast and
cheap, ideas move faster and cheaper! Whether it’s the image of the new VW Beetle (how
long did it take for the idea of that car to find a place in your brain?) or the words of a new
Stephen King novel (more than 600,000 people read it in the first week it was available
online), the time it takes for an idea to circulate is approaching zero.
Why should we care? Why does it matter that ideas can instantly cross international
boundaries, change discussions about politics, crime and justice or even get us to buy
something? Because the currency of our future is ideas, and the ideavirus mechanism is the
way those ideas propagate. And the science and art of creating ideaviruses and using them for
profit is new and powerful. You don’t have to wait for an ideavirus to happen organically or
accidentally. You can plan for it and optimize for it and make it happen.
Sure, some ideaviruses are organic. They happen and spread through no overt action or
intent on the part of the person who creates them (the Macarena wasn’t an organized plot…
it just happened). Others, though, are the intentional acts of smart entrepreneurs and
politicians who know that launching and nurturing an ideavirus can help them accomplish
their goals.
In the old days, the way we sold a product was through interruption marketing. We’d run
ads, interrupt people with unanticipated, impersonal, irrelevant ads and hope that they’d buy
something. And sometimes, it worked.
The advantage of this branding strategy is that the marketer is in complete and total control.
The disadvantage is that it’s hard and expensive. Every time a catalog clothier (Land’s End,
Eddie Bauer, you name it) wants to sign up a new customer, they need to buy a few hundred
stamps, send out some carefully designed catalogs and hope that one person sends them
money.
Unleashing the Ideavirus 17 http://www.ideavirus.com
What marketers are searching for is a way to circumvent the tyranny of cost-per-thousand
interruptions. They need something that ignites, a way to tap into the invisible currents that
run between and among consumers, and they need to help those currents move in better,
faster, more profitable ways. Instead of always talking to consumers, they have to help
consumers talk to each other.
A beautifully executed commercial on the Super Bowl is an extraordinarily risky bet.
Building a flashy and snazzy website is almost certain to lead to failure. Hiring a celebrity
spokesperson might work on occasion, but more often than not, it won’t break through the
clutter. Whenever advertisers build their business around the strategy of talking directly to
the customer, they become slaves to the math of interruption marketing.
In traditional interruption marketing, the marketer talks directly to as many consumers as possible, with no
intermediary other than the media company. The goal of the consumer is to avoid hearing from the advertiser. The
goal of the marketer is to spend money buying ads that interrupt people who don’t want to be talked to!
Unleashing the Ideavirus 18 http://www.ideavirus.com
In creating an ideavirus, the advertiser creates an environment in which the idea can replicate and spread. It’s the
virus that does the work, not the marketer.
Fortunately, there are already proven techniques you can use to identify, launch and profit
from ideas that can be turned into viruses. There’s a right and a wrong way to create them,
and more important, the care and feeding of your ideavirus can dramatically affect its
potency.
One of the key elements in launching an ideavirus is concentrating the message. If just 1% or
even 15% of a group is excited about your idea, it’s not enough. You only win when you
totally dominate and amaze the group you’ve targeted. That’s why focusing obsessively on a
geographic or demographic or psychographic group is a common trait among successful idea
merchants.
Why are new companies launching on the Net so obsessed with traffic and visitors? Why is a
company like GeoCities sold for more than $2 billion, when it has close to zero revenue and
interesting, but by no means unique, software?
Because infecting large populations with the ideavirus is the first step to building a profitable
business model. The key steps for Internet companies looking to build a virus are:
Unleashing the Ideavirus 19 http://www.ideavirus.com
1.
Create a noteworthy online experience that’s either totally new or makes the user’s life
much better. Or make an offline experience better/faster/cheaper so that switching is
worth the hassle.
2.
Have the idea behind your online experience go viral, bringing you a large chunk of the
group you’re targeting WITHOUT having to spend a fortune advertising the new
service.
3.
Fill the vacuum in the marketplace with YOUR version of the idea, so that competitors
now have a very difficult time of unteaching your virus and starting their own.
4.
Achieve “lock in” by creating larger and larger costs to switching from your service to
someone else’s.
5.
Get permission from users to maintain an ongoing dialogue so you can turn the original
attention into a beneficial experience for users and an ongoing profit stream for you.
6.
Continue creating noteworthy online experiences to further spread new viruses, starting
with your core audience of raving fans.
Unleashing the Ideavirus 20 http://www.ideavirus.com
Why Are Ideaviruses So Important?
1.
We live in a winner-take-almost-all world. (Zipf’s law.)
2.
We used to focus on making food. We used to make stuff. Now we make ideas.
3.
People are more connected than ever. Not only are we more aware that our friends have
friends but we can connect with them faster and more frequently.
4.
There’s a tremendous hunger to understand the new and to remain on the cutting edge.
5.
While early adopters (the nerds who always want to know about the cool new thing in
their field) have always existed, now we’ve got more nerds than ever. If you’re reading this,
you’re a nerd!
6.
The profit from creating and owning an ideavirus is huge.
Unleashing the Ideavirus 21 http://www.ideavirus.com
And Five Things Ideaviruses Have In Common
1.
The most successful ideaviruses sometimes appear to be accidents, but it is possible to
dramatically increase the chances your ideavirus will catch on and spread.
2.
An ideavirus adores a vacuum. (This is a big idea. Read on to see what I mean).
3.
Once an ideavirus spreads, it follows a lifecycle. Ignore the lifecycle and the ideavirus dies
out. Feed it properly and you can extend its useful life and profit from it for a long time.
4.
Ideaviruses are more than just essays and books. Everything from new technology to new
ways of creating new products are winning because of intelligent seeding by their
creators.
5.
Viral marketing is a special case of an ideavirus. Viral marketing is an ideavirus in which
the carrier of the virus IS the product.
Unleashing the Ideavirus 22 http://www.ideavirus.com
Seven Ways An Ideavirus Can Help You:
1.
When everyone in town tells ten friends about your amazing ice cream
shop and a line forms out the door (supercharged word of mouth due to
the virus having dominated the town so completely).
2.
When your company’s new mass storage format catches on and it
becomes the next Zip drive.
3.
When an influential sports writer names your daughter as a high school
All-American basketball player and coaches line up outside the door
with scholarships.
4.
When Steve Jobs commissions the iMac, which spreads the word about
the Mac faster than any advertising ever could, raising market share and
saving your favorite computer company from bankruptcy.
5.
When you write a report for your boss about how your company should
deal with an opportunity in Cuba and it gets passed on, from person to
person, throughout the company, making you a hero and a genius.
6.
When the demo recording you made becomes a bestseller on MP3.com
and you get a call from Sony, who wants to give you a recording
contract.
7.
When you are able to devise a brand-new Internet business plan for a
product that’s useful and also embodies viral marketing…growing from
nothing to a million users in a month and making you rich along the
way.
Unleashing the Ideavirus 23 http://www.ideavirus.com
The Sad Decline of Interruption Marketing
When I first starting writing about Permission Marketing about four years ago, much of
what I said was considered heresy. “What do you mean TV ads are going to decline in
effectiveness?” “How dare you say anything negative about banner ads—of course they
work!” or “Direct mail has never been healthier!”
History, fortunately for me, has borne out my cries of doom and gloom about interruption
marketing. The TV networks are diversifying away from their traditional network TV
business as fast as they can. Banner clickthrough rates are down 85% or more. Ads are
sprouting up on the floors of the supermarket, in the elevator of the Hilton hotel in Chicago
and even in urinals. And everywhere you look, unanticipated, impersonal and irrelevant ads
are getting more expensive and less effective.
There’s a crisis in interruption marketing and it’s going to get much worse. It took more
than thirty pages to build the case against this wasteful, costly ($220 billion a year)
outmoded expense in Permission Marketing, so I’ll only spend a page on it here. If you want
to read the entire jeremiad, send a note to free@permission.com and I’ll send it to you for
free.
Unless you find a more cost-effective way to get your message out, your business is doomed.
You can no longer survive by interrupting strangers with a message they don’t want to hear,
about a product they’ve never heard of, using methods that annoy them. Consumers have
too little time and too much power to stand for this any longer.
Unleashing the Ideavirus 24 http://www.ideavirus.com
We Live In A Winner-Take-Almost-All World
Quick! Name an oil painting hanging in a museum somewhere in the world.
Did you say, “the Mona Lisa”?
As I walk through the Louvre, arguably one of the top ten most packed-with-high-qualitypaintings
museums on the planet, I pass one empty room after another, then come to an
alcove packed with people. Why? Why are these people clawing all over each other in order
to see a painting poorly displayed behind many inches of bullet-proof glass?
The reason the Mona Lisa is the most famous painting in the world is
that something had to be the most famous painting in the world and it
might as well be the Mona Lisa.
Busy people don’t have time to look at every painting. They only have
room in their overcrowded, media-hyped brains for a few paintings.
And when you come right down to it, most people would like to see only the “celebrity”
paintings. And just as there can only be one “My most favorite famous actress” (Julia
Roberts) and one “this site equals the Internet” (Yahoo!), there’s only room for one “most
famous painting in the world” and the safe choice is the Mona Lisa.
There’s a name for this effect. It’s called Zipf’s law, after George Kingsley Zipf (1902-1950),
a philologist and professor at Harvard University. He discovered that the most popular word
in the English language (“the”) is used ten times more than the tenth most popular word,
100 times more than the 100th most popular word and 1,000 times more than the 1,000th
most popular word.
Unleashing the Ideavirus 25 http://www.ideavirus.com
It’s also been discovered that this same effect applies to market share for software, soft drinks,
automobiles, candy bars, and the frequency of hits on pages found on a website. The chart
above shows actual visits to the different pages at Sun’s website.
In almost every field of endeavor, it’s clear that being #1 is a lot better than being #3 or #10.
There isn’t an even distribution of rewards, especially in our networked world.
On the Net, the stakes are even larger. The market capitalization of Priceline, eBay and
Amazon approaches 95% of the total market capitalization of every other consumer ecommerce
stock combined. Clearly, there’s a lot to be gained by winning.
An ideavirus lets you make something like this happen to your idea, to your business, to your
product. While the benefits of being #1 for a public Internet stock or an oil painting are
clear, it’s just as important to small businesses and individuals.
Ideaviruses are faced with a brickwall filter. In electronics, a brickwall filter wipes out certain
frequencies and lets the rest through. There’s no room for second place or extra
effort—either you’re in or you’re out. Ideaviruses are win/lose propositions. Either the
velocity and smoothness are high enough that it becomes a bonafide epidemic, or they’re not
and it dies out. Either your ideavirus works or it doesn’t. Smart propagators know when to
quit if their ideavirus isn’t getting through the filter.
Definition: VELOCITY
The velocity is a measure of how fast the idea spreads from
one party to another. If an idea is going to hit ten people before it gets to me, the multiplier
effect is large indeed—fast steps lead to more people being infected before it dies out.
Unleashing the Ideavirus 26 http://www.ideavirus.com
Definition: SMOOTHNESS SMOOTHNESS
How easy is it for an end user to spread this particular
ideavirus? Can I click one button or mention some magic phrase, or do I have to go through
hoops and risk embarrassment to tell someone about it?
For example, it’s pretty easy to talk about your hairdresser. Someone tells you you’ve got a
great haircut, and you say, “Yeah, I went to Bob at Bumble & Bumble.” On the other hand,
spreading the word about your reflexology therapist is pretty tricky. You’re not sure when to
bring it up, and you really don’t have words to describe it.
The smoothest viruses, like Hotmail, spread themselves. Just the act of using the product
spreads the virus. There’s an obvious relationship between smoothness and catchiness. A
product that’s easy to recommend is often a product that’s easy to get hooked on.
Eric Raymond was a little known programmer when he wrote an essay called “The Cathedral
and the Bazaar.” It was a manifesto—an essay designed to become an ideavirus—arguing
why the open source approach to coding (creating stuff like Linux) made sense. But instead
of having a magazine or a book publisher bring it to market, he posted the essay online, in
text, postscript and audio form. And he gave it away for free.
Within months, tens of thousands of people had read it. Months after that, Raymond
published this essay with some of his other free essays in a book. That book became an
“instant” bestseller. Of course, it wasn’t instant at all. He had laid the foundation long
before, by building an ideavirus.
So, what has creating an ideavirus done for Raymond’s value? Let’s take a crass look at his
financial situation: The virus led to increased demand for his services as a programmer (he
can pick his jobs if he likes), as a consultant, and even as a public speaker. The last I saw, he
had just written an essay about what it was like to make a fortune during an IPO!
Unleashing the Ideavirus 27 http://www.ideavirus.com
The Traffic Imperative: Why Sites Fail
A site without traffic doesn’t exist.
According to Forrester Research, only 20% of 50 leading online retailers expect to turn a
profit this year. Just 18% more expect to be profitable next year. It’s becoming increasingly
obvious that many of these sites will never turn a profit, and that they’re hoping to last long
enough to be acquired or sell their stock.
A recent McKinsey and Co. study found that the vast majority of online retailers are not
only unprofitable, they’re actually losing money on every sale. Without even computing the
cost of advertising and clicks, these sites have discounted their prices so significantly that the
contribution margin from each sale is negative. The average online drugstore, for example,
loses $16.42 on each and every sale, before computing the cost of traffic.
Why? Many of these sites are confusing low prices with an effective customer acquisition
tool. There’s probably no way that’s less effective and more costly than cutting your prices to
the point where you lose money on each sale (for Amazon naysayers—they actually make a
profit of about $5 on the average book order).
Add to this mess the obscene cost of customer acquisition—estimated by the Boston
Consulting Group to be more than $80 a visitor (that’s for visitors, not even customers) for
most online merchants. Now you can see the huge hurdle these sites are going to have to
cross in order to be profitable.
This problem isn’t unique to the online world, of course. When I was enrolled at Tufts
University in 1980, there were two homemade ice cream stores within two miles of campus.
One was Joey’s, which made a terrific product (they used Hydrox cookies instead of Oreos,
by the way, so you could avoid the animal fat if you wanted) and there was never, ever a line.
Unleashing the Ideavirus 28 http://www.ideavirus.com
In the other direction was the now famous Steve’s Ice Cream. His prices were a bit higher
than Joey’s, but his profits were clearly much higher. Why? Because there was always a line at
Steve’s. A long line. Sometimes you’d wait an hour to get an ice cream cone.
What happened? Why did one ice cream shop go viral and the other languished at the edge
of profitability? It certainly wasn’t about advertising, because neither shop did any. The
reason Steve Herrell’s shop did so well is that it was famous for having a line! People brought
folks from out of town to have the experience. Locals came back because they’d convinced
themselves that if the hive liked it enough to wait an hour for an ice cream cone, well, it
must be worth it. Suddenly, it wasn’t about the ice cream. It was about the experience.
Most online merchants, being risk averse copycats afraid to innovate, are guaranteeing that
there will be no ideavirus created around their businesses. By paying millions to AOL and
Yahoo! for “traffic,” they’re investing in exactly the wrong sort of buzz. The
alternative—focusing on people who can promote your site, affiliate programs, unique
promotions and building wow, zing and magic into the site—is just too much work for most
sites.
Unleashing the Ideavirus 29 http://www.ideavirus.com
We Used To Make Food. We Used To Make Stuff. Now We Make Ideas.
Here are some astonishing facts you should think about long and hard on your way to work
tomorrow:
Twenty years ago, the top 100 companies in the Fortune 500 either dug something out of
the ground or turned a natural resource (iron ore or oil) into something you could hold.
Today, fewer than half of the companies on the list do that. The rest make unseemly profits
by trafficking in ideas.
In 1998, there were 30,000 new musical CDs published, including one from the Pope (his,
which I like a lot, features a little rap, a little techno and a lot of worldbeats).
Ninety-nine percent of Yahoo’s market capitalization is due to brand, sizzle, user loyalty and
other “soft” ideas. Only 1% of the company’s value is due to actual unique stuff that you
can’t get anywhere else.
Nathan Mhyrvold, former chief scientist at Microsoft, says a great programmer is worth
10,000 times more than an average one. Why? Because of the quality of her ideas.
The important takeaway is this: Ideas aren’t a sideshow that make our factory a little more
valuable. Our factory is a sideshow that makes our ideas a little more valuable!
Unleashing the Ideavirus 30 http://www.ideavirus.com
People Are More Connected Than They Ever Were Before. We Have
Dramatically More Friends Of Friends And We Can Connect With Them Faster
And More Frequently Than Ever.
Think back. Really far. Ten years ago.
How many people did you have regular telephone contact with ten years ago? Probably ten
or twenty or thirty in your personal life, and maybe 100 at work?
Now, take a look at your email inbox and your ICQ (the most popular instant messenger
program) buddy list. How many people do you hear from every week?
We’re far more connected than we ever were. And now, we’ve got second or third or fourth
order connections. There’s an email in my box from someone who is married to someone I
went to summer camp with twenty years ago who got my email address from a third friend.
Another message is from a former employee, telling me about a doctor who’s about to lose
his license for trying radical medical treatments, and how her mother-in-law will suffer if this
guy can’t practice any longer.
It’s hard for me to imagine either person contacting me if they had to walk across the village
and bang on the door of my hut or pick up the phone and call me. But the moment you
connect to the Internet, you connect, at some level, to all of us. And the connections make
ideas travel. Fast.
What’s the difference between word of mouth and an ideavirus? Two differences. First, word
of mouth tends to spread slower, be more analog. If you like a book, you might tell a friend
or two. And then your friends are unlikely to tell someone else until they read it for
themselves.
Second, word of mouth dies off. Because the numbers are smaller, it doesn’t take many
people who don’t participate in the word of mouth for each generation to be smaller than the
one before it.
Unleashing the Ideavirus 31 http://www.ideavirus.com
Here’s a schematic of typical word of mouth. Notice how few cycles there are, and how it drops off
over time.
Here’s an ideal ideavirus. Note how much more frequently the cycles occur, and how each cycle sees
the virus grow.
With an ideavirus, both principles no longer apply. Ideaviruses spread fast and they spread
far. With word of mouse (word of mouth augmented by the power of online
communication), you can tell 100 friends, or a thousand friends. Because the numbers are
larger and faster, the virus grows instead of slows.
Even before the Net, there were special cases of viruses. In traditional word of mouth in the
book business, someone reads a book and tells a friend. It’s nice, but it’s not usually enough.
The Bridges of Madison County, however, became the bestselling novel of the decade, because
booksellers adopted it and told people. As a bookseller, you’ve got exposure not just to a few
people, but hundreds of people. So the serendipitous word of mouth that helps some books
is replaced by a rapid, virulent alternative.
Unleashing the Ideavirus 32 http://www.ideavirus.com
On the other hand, most Americans have never had a massage from a professional masseuse.
Why? Because in order to understand the power of a massage, you have to get one. We don’t
currently have the word or picture tools to adequately describe the positive benefits of a
massage, and just as important, there isn’t a powerful spokesperson for massage who has
spent the time and energy to develop the ideavirus. There’s no real medium to transmit the
message. So the message travels slowly. So there is no virus around the idea of a massage.
Unleashing the Ideavirus 33 http://www.ideavirus.com
ThereÕs A Tremendous Hunger To Understand The New And To Remain On The
Cutting Edge.
Jed Clampett discovered that finding oil on his property was a sure road to riches. Today, the
road seems to be paved with awareness. If you know what’s news, if you know what’s the
latest, hottest, most impactful new idea, it’s much easier to succeed. You can profit in the
stock market, do better in politics, find breakthroughs in science, or programming or
marketing.
Why does this matter? Because in a society where the new isn’t valued, your social standing
doesn’t increase when you become a nerd. And because ideaviruses are really nothing but
amplified gossip about new stuff, they can’t take root in a culture that doesn’t care about the
new.
Take a look at the Top 40 charts in Billboard magazine. Thirty or forty years ago, a record
could easily stay on the list for six months or more. Today, new records come and go much
faster. Why? Because we are happily saturated in the current hit, and then move on.
Last year, 1,778 business books were published in the U.S. alone. Every one of them got read
by someone, some by an awful lot of people. Why? Because as our world changes faster and
faster and faster, knowing is just as important as having. And that makes the population ready
and eager for the next ideavirus.
As the speed of new ideas entering the community has increased, so has our respect for
people who know. And because it’s valuable, we’re open to both hearing about the new and
telling others about it.
Unleashing the Ideavirus 34 http://www.ideavirus.com
While Early Adopters (The Nerds Who Always Want To Know About The Cool
New Thing In Their Field) Have Always Existed, Now WeÕve Got More Nerds
Than Ever Before. If YouÕre Reading This, YouÕre A Nerd!
The Internet turned us all into nerds. AltaVista isn’t cool any more—google.com is. Don’t
use the Palm, that’s passé. Try this Handspring instead. Suddenly we’re ready, willing and
able to be at the bleeding edge, all the time.
The profit from creating and owning an ideavirus is huge, huger than it ever was before. It
used to be that only a few stereotypical nerds cared about the latest pocket calculator. Today,
you’ll see people talking about their handheld computer on the subway. It used to be that
only a few people knew about the latest Salsa hit out of Mexico or the coolest new chef in
Los Angeles. Today, the roles are totally reversed. Your parents are nerds!
It’s not just that our society is rewarding people who are sensitive enough or smart enough or
cool enough to know about the next new thing. It’s that many of us have crossed over a line
and gone from being the vast majority who waited for something to become
mainstream—we’ve become the early adopters, the folks on the bleeding edge who actually
seek out innovation. The combined circulation of Wired, Fast Company and PC Magazine is
rapidly approaching the total circulation of Sports Illustrated.
Because the population has shifted, the sweet spot has shifted. Companies no longer make
most of their money harvesting money from the laggards who finally get around to buying
something at K-Mart. They make their money the first day, the first week, the first month an
idea is out there.
If something is new and different and exciting and getting buzzed about, we want to know
about it, be part of it. The fashion is now to be in fashion, and ideas are the way we keep up.
Unleashing the Ideavirus 35 http://www.ideavirus.com
Ideas Are More Than Just Essays And Books. Everything From New
Technology To New Ways Of Creating To New Products Are Winning Because
Of Intelligent Ideavirus Management By Their Creators.
A manifesto is a carefully organized series of ideas, designed to get someone to come around
to your point of view. But while one way to make a complicated argument is with a book,
you can just as easily (and sometimes more effectively) send it through a song (Bob Dylan
did this for Hurricane Carter) or with something as elegant as an OXO vegetable peeler.
When you first see the OXO, you instantly understand the idea behind it. You just know it
will work better and cut you less often. If you’ve ever peeled a vegetable, you want an OXO.
The design of the OXO is quite simply a manifesto that says, “There’s a smart, comfortable
way to do this annoying task.” Is the OXO going to get viral? Not across the general
population, of course, but if you hang out with a group of people who have arthritis or love
kitchen stuff, it already has. Just take a look at the glowing reviews of this peeler on
Amazon’s kitchen site.
Unleashing the Ideavirus 36 http://www.ideavirus.com
The End Of The Zero Sum Game
Traditional advertising is a game with winners and losers. If your product gets attention from
the targeted consumer, you win “mindshare” and your customer loses time. When a
consumer is foolish enough to listen to an irrelevant ad, she loses time and doesn’t even gain
useful information. It’s an old economy model in which every transaction has someone
taking something.
Permission marketing and the ideavirus are both very different from this model. These
models create a game in which everyone can win! If there’s a great idea, and it moves through
the hive for free, everyone who touches it wins in several ways.
First, you as the consumer win for recommending it to a friend. This increases your status as
a powerful sneezer (or your compensation as a promiscuous sneezer.) Because you respect
your peers, you’re not suggesting or pitching something that doesn’t make your friends’ lives
better. Violate this respect and your power as a sneezer goes way down.
Definition: SNEEZER Some people are more likely to tell their friends about a great new
idea. These people are at the heart of the ideavirus. Identifying and courting sneezers is a key
success factor for ideamerchants.
Second, the recipient benefits as well. He benefits from the way the idea changes his life, and
he benefits because he now has the ability to sneeze the idea to someone else, thus increasing
his power.
Third, the creator of the idea succeeds because her idea propagates and because she can sell
souvenirs (speeches, consulting, value-added services) to people who are now open and
receptive to her idea.
My friend, Chris Meyer, co-author of Blur, had this to say: “The one thing that distinguishes
effective sneezing campaigns from ineffective ones is RESPECT for the time, attention, and
reputation of the next guy to catch the virus. It’s important to note that the decision to
sneeze is, in general, a distributed one, made by each of us as to whether to clog our friend’s
Unleashing the Ideavirus 37 http://www.ideavirus.com
email or whatever with the virus in question, because our (local, at least) reputation is at
stake.”
This insight goes to the core of why ideaviruses are succeeding and why traditional marketers
don’t immediately grasp this approach (or permission marketing for that matter.) The
distributed nature of the decision is the antithesis of the command-and-control General
Patton approach that marketers have taken previously.
The reason that The Red Herring, The Industry Standard and other magazines are jammed
with ads is not because the ads always work. They don’t. The reason the ads are purchased is
that in exchange for money the marketer gets the illusion that they’re in charge of the
conversation, at least for a few seconds.
Bill Bernbach, the dean of American Advertising, was co-founder of DDB Advertising. He
died twenty years ago, but before he left us, he pointed the way to this “new” way of
marketing:
“You cannot sell a man who isn’t listening; word of mouth is the best
medium of all; and dullness won’t sell your product, but neither will
irrelevant brilliance.”
The answer, of course, is to give people a reason to listen and then create an infrastructure
that will amplify their ability to spread word of mouth. And core to both of those tasks is the
new respect that marketers need to show newly powerful consumers.
Unleashing the Ideavirus 38 http://www.ideavirus.com
SECTION 2: How To Unleash An Ideavirus
STEAL THIS IDEA!
Here’s what you can do to spread the word about Unleashing the Ideavirus:
1. Send this file to a friend (it’s sort of big, so ask first).
2. Send them a link to http://www.ideavirus.com so they can download it themselves.
3. Visit http://www.fastcompany.com/ideavirus to read the Fast Company article.
4. Buy a copy of the hardcover book at
http://www.amazon.com/exec/obidos/ASIN/0970309902/permissionmarket.
5. Print out as many copies as you like.
Unleashing the Ideavirus 39 http://www.ideavirus.com
While It May Appear Accidental, ItÕs Possible To Dramatically Increase The
Chances Your Ideavirus Will Catch On And Spread.
This is the really cool part. Once you understand the fundamental elements behind the
propagation of an ideavirus, you can unleash your own.
Just because ideaviruses have usually spread through unknown means or accidental events
doesn’t mean that there isn’t a science to building and managing them.
You can invest in designing your product to make it virusworthy. Then if you understand
the eight elements of the ideavirus formula, you increase your chances of spreading your
ideavirus with every step along the way.
This can change the way you approach all of your marketing. If launching an ideavirus is the
most powerful thing you can do for a product and service, and there are steps you can take to
increase the likelihood that this will occur, you’ve got to try!
Unleashing the Ideavirus 40 http://www.ideavirus.com
The Heart Of The Ideavirus: Sneezers
SNEEZERS Some people are far more likely to spread an ideavirus than others. Malcolm
Gladwell (author of the brilliant book and ideavirus, The Tipping Point) calls this the Law of
the Few and breaks the key virus spreaders into three groups: Connectors, Mavens and
Salespeople. What’s critical in the analysis is understanding that some folks are dead ends,
while others will enable and amplify your ideavirus.
In his best example, Gladwell talks about the success of Paul Revere in warning us that the
British were coming. It turns out that a second man, William Dawes, went on a similar ride
the same night—but his was a total failure.
Why did Dawes fail where Revere succeeded? It’s because people knew Paul Revere. They
trusted him. He had credibility. And so when he said something, people were willing to
listen and believe. Revere was a sneezer. Dawes, a loner, tried hard but couldn’t get the idea
to become a virus.
Sneezers are at the core of any ideavirus. Sneezers are the ones who when they tell ten or
twenty or 100 people—people believe them.
Unleashing the Ideavirus 41 http://www.ideavirus.com
Sneezers Are So Important, We Need To Subdivide Them
There are two basic kinds of sneezers:
Promiscuous Sneezers
This is your uncle the insurance salesman. These are members of a hive who can be counted
on to try to “sell” their favorite ideavirus to almost anyone, almost any time.
1.
Promiscuous sneezers can be motivated by money or other inducements.
2.
Promiscuous sneezers are rarely held in high esteem as opinion leaders, but if they’re
promiscuous enough, they can be extremely effective.
DEFINITION: HIVE People are not one amorphous mass. We’re self-organized into
groups, or hives that have several things in common: a way to communicate among
ourselves; spoken or unspoken rules and standards; a common history; fashion leaders. Some
examples: Fraternity brothers at a college, orthodox Jews, readers of Fast Company,
Deadheads.
Many of the Net businesses that are now being organized around ideaviruses are targeting
this group (people who are willing to sell to their friends for personal gain). Companies like
Mercata, All Advantage and even Amazon are offering inducements to customers that
compensate them for spreading ideas to their friends and acquaintances in an attempt to
acquire new customers. As the value of creating ideaviruses increases, we’ll see more of this,
and we’ll also see more and more people becoming promiscous sneezers—basically, we’re
paying folks enough to corrupt them into spreading ideas in exchange for cash.
Powerful Sneezers
The hat business is near the end of an eighty-year downward spiral to total irrelevance. Each
year has brought worse news, with one manufacturer after another going out of business, and
most towns left with one (if they’re lucky) haberdasher.
In the midst of all this dismal news, about twenty years ago there was one bright spot.
Harrison Ford. With a bullwhip. Wearing a hat.
Unleashing the Ideavirus 42 http://www.ideavirus.com
Indiana Jones sold more hats for Stetson than any single person since the invention of the
Marlboro Man. Why? Because Ford has the influence to set style, because his appearance in a
movie wearing that hat coaxed millions of men who wanted to be like him into buying a hat.
The paradox of the powerful sneezer is that he can’t be bought. Every time a powerful
sneezer accepts a bribe in exchange for spreading a virus, his power decreases. When Bruce
Springsteen does ads in Japan, or Whoopi Goldberg shills for Flooz, they have less leverage as
powerful sneezers. The public knows that they can be motivated by more than just taste.
In fact, every time a powerful sneezer tries something new and introduces a new idea, she
takes a risk. If her followers reject the virus (for whatever reason), her ability to introduce
future viruses decreases. For this reason, it’s difficult to manipulate powerful sneezers, and
equally difficult to predict what might motivate them to adopt an ideavirus.
Here’s an analogy that demonstrates the difference between promiscuous sneezers and
powerful sneezers, and more important, explains how they might converge:
Anyone can buy an ad in the Pennysaver, or even write and insert a “special advertising
section” in some fancy magazine. The advantage of this kind of presentation, obviously, is
that it gives the marketer complete control over how the message appears and what it says.
Advertising is basically paid sneezing. And because the public realizes that that’s all it is, it
doesn’t have an awful lot of credibility. It still works, but it’s not as effective as real sneezing
from a powerful sneezer.
On the other hand, it’s up to the editor in chief of the New York Times to decide what
articles appear in the paper. No matter how much money a marketer spends (even though
spending a lot might get you noticed by the editorial staff), there’s no guarantee that an
article will appear—and no guarantee that if it does appear, it will say what you want it to
say.
Unleashing the Ideavirus 43 http://www.ideavirus.com
Enter the web. There are plenty of websites where the line between editorial content and
advertising is blurred, where sponsoring a website also gives you the right to say what you
want to say.…
So let’s imagine for a second that the New York Times embraced this shocking idea. That
they said, “Okay marketers, write your own articles! And pay us to run them!” Now there’d
be some ground rules. First, the marketer would specify how much they’d be willing to pay
to have a story featured. For example, a restaurant could decide it might be worth $10,000
for a feature on their new chef to appear in print.
Second, the Times would get final say over what was printed.
Obviously, a wholesale switch from powerful sneezer to promiscuous sneezer would decimate
the circulation base of the Times. If the Times accepted any article, regardless of credibility
and interest, just because the marketer was the highest bidder, it would totally destroy the
paper within a week.
But what if the Times realized that picking only the very best articles that were submitted
(maybe just a few a day) could ensure that people would still be delighted to read the paper?
What if the Times knew that for every 199 badly written restaurant fluff pieces, a great one
would show up? And what if the editor in chief had enough guts to pick just the great articles
and resist pressure to completely sell out?
Journalistic handwringing aside, this is already happening (not at the fabled Times, of
course), and it’s going to happen more. It’s happening on websites. It’s happening on
television (witness the CBS coverage of iWon.com awarding prizes—CBS owns a chunk of
iWon.) And far more interesting than this tortured analogy, it’s already happening with
people’s personal sneezing ethics.
A hundred years ago, there weren’t many opportunities for playwrights, actors and captains
of industry to sell out. Today, Whoopi Goldberg pitches Flooz, William Shatner pitches
Priceline and Gerald Ford is on the board of directors of several companies. In each case, the
celebrity is shifting from role of influential, powerful, can’t-be-bought-I’m-a-style-statesman
Unleashing the Ideavirus 44 http://www.ideavirus.com
to promiscuous sneezer, available for sale. William Shatner had lost his ability to set style
through his actions—he was past his prime as a powerful sneezer. So the segue to paid
sneezer made sense for his career. It would probably be a dumb move for Tom Cruise or Mel
Gibson, though.
After I left Yahoo!, I had many opportunities to serve on boards and do endorsements. I
chose not to. Why? Because I didn’t want to squander the powerful sneezing points I’d
earned by writing my last book. The one ad I did, I did for free. I’m still hearing about it.
Think about your own situation…. Have you ever signed up a friend for MCI’s Friends and
Family program? Or tried to get someone to use your Amazon affiliate links to buy books?
Or join with you to buy something at Mercata.com? In every case, you’re getting paid to
alter your behavior. That makes you more promiscuous and less powerful.
As the Net makes it easier to measure ideaviruses and motivate sneezers, we’re going to see
far more people become Promiscuous Sneezers, but, at the same time, the role of the
powerful sneezer will become ever more important. As available attention becomes ever more
precious, we’re going to be far more likely to listen to someone who’s spreading a virus for
non-personal gain.
Epinions.com is a fascinating model of the intersection between the powerful and the
promiscuous sneezers. Here’s a site where hundreds of thousands of people come to hear the
opinions of thousands of sneezers. Everything is reviewed, from books to dishwashers. And
the reviewers are clearly identified and constantly ranked. Promiscuous sneezers (who get
paid to do the reviews) suddenly become powerful! How? If a lot of people read and like
your reviews, your reviews carry more weight, regardless of your compensation scheme.
“Xyz” has posted more than 1,000 reviews and been read more than 100,000 times. She’s
compensated every time someone reads one of her reviews, so she certainly qualifies as
promiscous. She works hard to get others to read her reviews. But at the same time, she’s
developing a reputation as a powerful sneezer.
Unleashing the Ideavirus 45 http://www.ideavirus.com
Referrals.com is a business based around the idea of paying people to help with job searches.
Instead of just giving some headhunter the names of five friends who might be perfect for a
job (and having the headhunter collect a $30,000 fee if you’re right), referrals.com turns the
idea upside down. With their system, YOU send the job offer along to your friends, and if
they take the job, you get a check for $4,000.
If Referrals.com only attracts promiscuous sneezers, the business will fail. Why? Because the
very best people try hard not to listen to interruptions from promiscuous sneezers. The very
best people know that if someone can be bought, they’re not much more than a walking
billboard, and just as they ignore the billboards on the highway, they’re going to ignore the
most promiscuous sneezers in their midst. (Aside: If you’ve ever been called by a headhunter,
you know just how promiscuous people are willing to be in exchange for cash!)
Referrals.com is working very hard to turn powerful sneezers within very select, high-end
hives into people who, on occasion, are willing to sell out for a $4,000 payoff. These are folks
who might not hassle you just so they can make $5 or $10 in bonuses. But the idea of
becoming a headhunter and making $4,000 in exchange for sending a few emails is too
irresistible to pass up. This idea that even the powerful can become promiscuous for the right
inducement and in the right setting is a key building block to unleashing the ideavirus in an
organized way.
What a paradox. Powerful sneezers become less powerful when you buy them off. But
sometimes, promiscuous sneezers become powerful again when they get particularly
successful at it. It’s a cycle, with people switching off from one to another, always trying to
figure out how to be both promiscuous (read profitable) and powerful.
Unleashing the Ideavirus 46 http://www.ideavirus.com
The Art Of The Promiscuous
How do you attract and keep promiscuous sneezers? There are six key principles:
1. Make big promises
2. Show them how to make it up in volume
3. Describe an attainable path
4. When someone succeeds, tell the rest of them
5. Give the successful ones a way to show the non-sneezers it worked
6. Have a Mary Kay convention
Make big promises
One of the things that drives someone to become a promiscuous sneezer is the opportunity
for a change in lifestyle. Certain rewards, though small, are not as enticing as slightly less
certain rewards that are much larger. Human nature (especially among the optimists) will
give you the benefit of the doubt on the risks, but it won’t cut you any slack on the rewards.
So, I’m much more likely to help you out for a chance to get free dry cleaning for six months
than I am to get a certain reward of $4 off my next dry cleaning bill.
Show them how to make it up in volume
Of course, the promise has to be believable. One of the best ways to do that is to make it
clear to the promiscuous sneezer that the system can be gamed. That if they work the system,
the odds of winning go way up.
If I look at the offer you make and say, “Wait. If I go to ten friends, not just one, then I’m a
lock to win this great prize…” you’ve done it right. I may think I’m scamming you by going
to so many people to adjust the odds in my favor, but actually, I’m doing just what you
wanted me to do—and then some.
Many of the online affiliate programs work this way. These programs offer a commission for
referrals that result in a sale. First designed as a cheap way to get new customers referred from
relevant web sites, they’ve evolved into something far bigger. If you’re at an online pet store,
Unleashing the Ideavirus 47 http://www.ideavirus.com
for example, and you see a link to a book about training dogs, you can click on the link and
buy it from Amazon.com. Amazon then sends the affiliate (the online pet store) a
commission. Small businesspeople have looked at these programs and said “Wait! If I build a
site that does nothing but sell books and Barnes and Noble does all the work, I’ll scam the
system and make a ton of money.” Of course, the online bookstore doesn’t care a wit about
where the customers come from. They’re just happy to have them. In essence, hundreds of
thousands of entrepreneurs are now building businesses dedicated to finding customers for
other merchants.
Describe an attainable path
Alas, trust is in short supply, even among optimistic promiscuous sneezers. Thus you’ve got
to make it clear to potential sneezers that there is in fact a way for them to profit from this
adventure.
This is especially true for offers where you don’t have a lot of time to make your case. By
showing the sneezer how smooth the system is, by making it trivially easy to forward that
email or whisper to that friend, you’re far more likely to get their initial enthusiasm. The first
few sneezes are the most difficult to get an individual to perform.
When someone succeeds, tell the rest of them
This is so important and so overlooked. I’m presuming that you’ve gained permission to talk
with your sneezers on an ongoing basis. So now talk to them! I’m a member of several online
affiliate programs, but not one of them does this. Why not send announcements detailing
how the most effective affiliates are doing? Why not invite me to visit their sites and see them
in action? By making it really clear that some sneezers are happily profiting, you dramatically
increase the chances you’ll get better performance from the rest of your sneezers.
Give the successful ones a way to show the non-sneezers it worked
Mary Kay cosmetics gives its best salespeople a pink Cadillac. This is no accident.
There are plenty of ways to pay off a promiscuous sneezer. Why do it with a pink Cadillac?
Because it is a persistent amplifier of this sneezer’s success. Because it attracts new sneezers to
Unleashing the Ideavirus 48 http://www.ideavirus.com
the fold. Because it’s proof to the rest of your organization and to the world that you can get
rich by selling cosmetics to your friends.
Have a sales convention
Just because it’s a new century doesn’t mean we should abandon the idea of getting together
in real life. Zig Ziglar tells the story of how Mary Kay went to a sales convention when she
was a struggling salesperson. She didn’t even have enough money to eat the meals there…
she brought her own crackers and cheese. But at the final banquet, when the salespeople
queued up to shake the company president’s hand, Mary Kay looked at him and said, “Next
year, I’ll be back as the #1 salesperson.” The president, who could have easily brushed off the
claim, stopped what he was doing, paused for a full thirty seconds, looked her in the eye and
said, “Yes, yes, I believe you will.”
And the rest is sales history. But without the convention, I seriously doubt this would have
occurred. How can you get together with your best promiscuous sneezers?
In addition to these six principles, there are two things you can do to totally and completely
wreck your network of promiscuous sneezers:
1. Change the rules in the middle
2. View the relationship as an expense
Don’t change the rules in the middle
Alladvantage.com is one of the fastest growing websites on the planet. The idea was to create
a multi-level marketing organization where each member would get paid for the ads they saw
and, more importantly, for the ads seen by the people they recruited. This led to a classic
MLM (multi-level marketing) network marketing business, where people made more money
bringing in new salespeople than they did actually using the product.
After growing to more than five million registered users, the company took a look at the
numbers and realized that the path to profitability was going to be hampered by the high
rates they were paying. So, well within the fine print they had published when they first
started, they changed the rates.
Unleashing the Ideavirus 49 http://www.ideavirus.com
All hell broke loose. The very best sneezers started sneezing against the company. The growth
rate hiccupped. Bad news. They’ll survive, and they might even continue their record
growth. But far better to have run the numbers in advance and had a payment schedule they
could live with forever.
Don’t view the relationship as an expense
It’s so easy to move your relationship with promiscuous sneezers from investment to expense.
After all, at the beginning it’s great because these people are dramatically cutting your
acquisition costs and helping you grow. But once you do grow, it’s easy to assume your
growth might be able to continue without the “high cost” of paying your sneezers.
In practice, there are two terrible side effects. The first is that you’ll inevitably try to trim the
benefits you offer your sneezers as well as the effort you put into keeping them happy. Better
to just cancel the program outright than to start disappointing these critical allies (remember,
an unhappy promiscuous sneezer can quickly become an angry powerful sneezer).
Second, you’ll find yourself trying to grow using techniques that you haven’t evolved, tested,
measured or practiced. And more often than not, that means failure.
A better strategy is to put a cap on your new sneezer acquisition efforts at the same time you
love and reward your existing sneezers. During this interregnum period, get really good at
tapping other ways to grow. Only after you’re confident that you’ve got the transition
working should you start to phase out the sneezers who got you there in the first place.
Unleashing the Ideavirus 50 http://www.ideavirus.com
ItÕs More Than Just Word Of Mouth
Marketers have been pursuing word of mouth for years. There are five important principles
that someone unleashing an ideavirus should understand—principles that marketers
pursuing old-fashioned word of mouth didn’t use:
1. An idea merchant understands that creating the virus is the single most important part of
her job. So she’ll spend all her time and money on creating a product and environment that
feeds the virus.
2. An idea merchant understands that by manipulating the key elements of idea
propagation—the velocity, the vector, the smoothness, the persistence and the identification
of sneezers—she can dramatically alter a virus’s success.
Definition: PERSISTENCE Some ideas stick around a long time with each person,
influencing them (and those they sneeze on) for months or years to come. Others have a
much shorter half-life before they fade out.
Definition: VECTOR As an ideavirus moves through a population, it usually follows a
vector. It could be a movement toward a certain geographic or demographic audience, for
example. Sometimes an ideavirus starts in a sub-group and then breaks through that niche
into the public consciousness. Other times, it works its way through a group and then just
stops. Napster vectored straight to college kids. Why? Because they combined the three
things necessary for the virus to catch on: fast connection, spare time and an obsession with
new music.
3. The idea merchant remembers that digital word of mouth is a permanent written record
online, a legacy that will follow the product, for good or for ill, forever.
4. An idea merchant realizes that the primary goal of a product or service is not just to satisfy
the needs of one user. It has to deliver so much wow, be so cool, so neat and so productive
that the user tells five friends. Products market themselves by creating and reinforcing
ideaviruses.
5. An idea merchant knows that the ideavirus follows a lifecycle and decides at which
moment to shift from paying to spread it, to charging the user and profiting from it.
Unleashing the Ideavirus 51 http://www.ideavirus.com
An Ideavirus Adores A Vacuum
It’s very hard to keep two conflicting ideaviruses in your head at the same time
(Communism: evil or benign? Martha Stewart: pro or con? Can’t have both). So if an idea
already inhabits space in your consumer’s brain, your idea can’t peacefully coexist. It usually
has to dislodge a different idea, the incumbent, and that’s always tough.
Given that, the best friend of an ideavirus is a vacuum. When “60 Minutes” ran the story
about runaway acceleration in Audi cars, it was an ideal ideavirus. Why? Because most people
had never driven an Audi. Most people had never interacted with the Audi company. Most
people didn’t have a best friend who loved his Audi. As a result, the virus rushed in, filled the
vacuum and refused to be dislodged.
Audi, of course, did exactly the wrong thing in fighting the virus. They issued a tight-lipped
response and relied on engineering data to PROVE that they were right. Very correct, very
German and totally ineffective. It cost the company billions of dollars in lost sales.
Audi didn’t have to go out and spread the idea that Audi’s were good cars. That would have
been pretty straightforward if they were starting from scratch. Instead, Audi had to undo the
idea that had been spread by “60 Minutes”. And responding “did not” to TV’s “did too” was
a recipe for failure.
Instead, they could have countered the virus by filling in the rest of the vacuum. I would
have advised them to put an Audi 5000 in every major shopping mall in America. Let people
sit in it. Invite them to take the “Audi Sudden Acceleration Test” and see for themselves
what the car was like. By creating a more vivid and forceful alternative to a television hatchet
job, Audi could have unleashed its own countervirus.
At the beginning, the Internet was a vacuum. A Yahoo! or an eBay or an Amazon could walk
in and propagate its ideavirus fast and cheap. Today, though, launching a new search engine
or a new email service is hard indeed. Why? Because the vacuum’s gone.
Unleashing the Ideavirus 52 http://www.ideavirus.com
Take the much-coveted Aeron chair from Herman Miller. The company introduced this
puffy, bouncy desk chair for star executives and invented a market where none had
previously existed. Suddenly, you could spend a lot of money on a chair that actually worked
better, as opposed to just one that made you look bigger when you were busy firing people.
When Internet marketing pioneer Site Specific raised its first round of venture capital, the
principals went out and spent $15,000 on these chairs! This is a chair so remarkable, it was
featured on the front page of the Wall Street Journal.
Now, of course, there are plenty of neat, ergonomic desk chairs. One of Herman Miller’s
biggest competitors is betting the farm on their new Leap chair. Their MBA’s have taken a
hard look at Aeron’s success and market share and decided that they can capture x% of the
market. The problem, of course, is that there’s no longer a vacuum. The problem is that
now, instead of spreading a virus about how you can be more comfortable all day, they have
to spread a much smaller, and less compelling virus about why their chair is a little better
than the chair you’ve already heard of.
There are vacuums in your industry. But not for long….
Unleashing the Ideavirus 53 http://www.ideavirus.com
Once It Does Spread, An Ideavirus Follows A Lifecycle. Ignore The Lifecycle
And The Ideavirus Dies Out. Feed It Properly And You Can Ride It For A Long
Time.
Tom Peters co-wrote In Search of Excellence nearly twenty years ago. Through some smart
marketing moves (not to mention a great virus) the book became an epidemic and turned
into the bestselling business book ever written.
Tom’s career could have followed the arc of almost every other business writer… a big hit
followed by a long decline into obscurity. But instead of ignoring the lifecycle, Tom insisted
on riding it.
And he’s still riding it today. Every few years he unleashes a new ideavirus. He writes
mindblowing articles (like the “Brand Called You” cover piece for Fast Company a few years
ago) and follows up with books and exhausting worldwide speaking tours. When he shows
up in a town to give a speech, perhaps a third of the people there are dyed-in-the-wool Tom
Peters fans. And the rest of the audience? Brought there by the fans, exposed to his virus,
ready to be turned into fans.
By leveraging the base that his first book brought him, Tom has built a career out of
launching new ideaviruses. Sure, none of them were as big as In Search of Excellence, but the
vacuum keeps getting smaller, so the opportunities are smaller.
Other companies and ideas have ridden their first wave and then disappeared. People no
longer clamor to dance the Hustle or to get into Studio 54. They don’t visit the once hot
jennicam website or pay a premium for front row seats at Cats. Why? Because instead of
institutionalizing the process of improving, honing and launching new ideaviruses to replace
the dying ones, the “owners” of these viruses milked them until they died.
Unleashing the Ideavirus 54 http://www.ideavirus.com
Viral Marketing Is An Ideavirus, But Not All Ideaviruses Are Viral Marketing
Viral marketing is a special case of an ideavirus. Viral marketing is an ideavirus in which the
medium of the virus IS the product. It’s an idea where the idea is the amplifier.
DEFINITION: AMPLIFIER A key difference between word of mouth and an ideavirus is
that word of mouth dies out while an ideavirus gets bigger. Why? Because something
amplifies the recommendations to a far larger audience. That could be TV or other forms of
media (a good review in the New York Times that amplifies the message of one reviewer to
many readers) or it could be the web (a site like planetfeedback.com amplifies the message of
a single user).
Steve Jurvetson, the venture capitalist behind Hotmail, coined the term “viral marketing” to
describe the way the service grew. Hotmail offered free email. That alone was a very
compelling two-word business proposition. But the magic of the company was that in every
single email you sent using the service, there was a little ad on the bottom of the note. And
the ad said, “Get Your Private, Free Email from Hotmail at http://www.hotmail.com”.
Every time you sent a note, you spread the virus. The magic of viral marketing is that the
medium carries the message. The more you use Hotmail, the more you spread the virus. But
note: It was also extremely smooth…. The Hotmail site was just a click away from an email,
and it took just a few clicks more to start using it—and sending Hotmail’s built-in ads to
your friends.
Unfortunately, not every product lends itself to viral marketing. Viral marketing requires
that the product you’re using be communications-focused or very public. The new VW
Beetle is an example of viral marketing. Why? Because the more you drive it, the more
people see it. And the more Beetles people see, the more they want one. It’s not audible and
it’s not as smooth as Hotmail, but it is most definitely viral.
Many of the very best Internet ideas are built around some level of viral marketing. Using an
earlier example, Referrals.com pays big money to people who recruit their friends for hot
Unleashing the Ideavirus 55 http://www.ideavirus.com
jobs. Of course, the act of recruiting your friends is also the act of telling them about
Referrals.com.
Try not to get too obsessed with the magic, self-referencing nature of viral marketing
companies. They’re a very special case—for example, it’s hard to imagine how most books
could use viral marketing. Interesting, though, that line-dances like the Hustle and the
Macarena DID use viral marketing. After all, you can’t do the dance unless you teach your
friends how!
Unleashing the Ideavirus 56 http://www.ideavirus.com
What Does It Take To Build And Spread An Ideavirus?
There are two questions you can ask yourself about your idea before you launch
it…questions that will help you determine how likely your idea will become an ideavirus.
Is it worth it?
Nobody spreads an ideavirus as a favor to you. They do it because it’s remarkable, thoughtprovoking,
important, profitable, funny, horrible or beautiful. In today’s winner-take-all
world, there’s no room for a me-too offering, or worse, BORING products and services. If
it’s not compelling, it will never lead to an ideavirus.
Face it. Nobody is going to hand out big rewards ever again for being on time, performing
work of good quality, being useful, finishing a project on budget or being good enough.
That’s expected. That’s a given. The rewards (and the ideavirus) belong to the first, the
fastest, the coolest, the very best.
The biggest mistake companies make is that they chicken out. If your idea doesn’t become a
virus, it’s most likely because it didn’t deserve to become a virus.
If you’re now defining yourself as an idea merchant (hey, it’s either that or lose), then you
must accept the fact that being brave and bold in the creation of ideas is the only reason you
went to work today.
Is it smooth?
After someone’s been exposed to an ideavirus just once, they’re not likely to actually catch it.
We’ve made our brains bulletproof and ideaproof. There’s so much clutter, so much noise,
so many ideas to choose from that the vast majority of them fail to make a dent.
Think about the last time you walked through a bookstore (the home of ideaviruses waiting
to happen). How many books did you stop and look at? Pick up? Turn over? And how many
of those books ended up in your shopping basket? Got read? Led you to tell ten friends?
Precious few, that’s for sure.
Unleashing the Ideavirus 57 http://www.ideavirus.com
Compare this to the Harry Potter phenomenon… the bestselling books of the last few years,
created just because kids told kids. A classic ideavirus, and one that initially grew with no
promotion at all from the publisher.
It’s difficult to get from awareness to the “sale” of an idea, to convert a stranger into a friend
and a friend into a carrier of your ideavirus. An ideavirus succeeds when it pierces our natural
defenses and makes an impact.
In greek mythology, they tell the story of the Medusa. The Medusa was part of the race of
Gorgons—beings with a horrible curse. Anyone who looked in their eyes immediately and
permanently turned to stone.
There are plenty of marketers who wish that their ads or their product had the power of the
Medusa: that every person who saw it would be immediately transfixed, rooted to the spot,
and converted into a customer for life. (Of course, they don’t want their customers to die a
horrible death and be turned into stone, but I couldn’t find a Greek myth in which an evil
goddess turned you into a frequent shopper of Kate Spade purses, getting a second mortgage
just to pay for them.)
Alas, there are precious few Gorgon products and even fewer ad campaigns with Gorgon-like
properties. It’s foolish to expect that one exposure to your message will instantly convert
someone from stranger to raving ideavirus-spreading fan. So plan on a process. Plan on a
method that takes people from where they are to where you want them to go.
And while you’re at it, work on the product. Because a catchier, more compelling, more viral
product makes your job 100 times easier.
These are critical decisions because of the attention deficit marketers are facing. In 1986, the
year I published my first book, there were about 300 other business books published. In
1998, there were 1,778 business books brought to market.
The supermarket sees about 15,000 new products introduced every year. The Levenger
catalog alone features more than 50 different pens and pencils, none of which were available
Unleashing the Ideavirus 58 http://www.ideavirus.com
just a couple years ago. There isn’t a marketplace out there that isn’t more crowded than it
was a decade ago.
In a world where products are screaming for attention, the most precious commodity is
attention. And attention is harder and harder to achieve.
If you already understand the power of permission, your next question might be, “Fine, but
how do we get permission? How do we get the first date… the first interaction where we ask
people if we can start an ongoing dialogue about our products and their needs?”
My answer used to be a rather weak mumble about buying ads. The right answer, however,
is to create an ideavirus. The right answer is to let the market tell itself about your products
and services and give you permission to continue the dialogue without your having to pay for
it each time. The right answer is to create products so dynamic and virusworthy that you
earn the attention.
Unleashing the Ideavirus 59 http://www.ideavirus.com
There Are Three Key Levers That Determine How Your Ideavirus Will Spread:
Where do you start? What are the key elements worth focusing on to turbocharge your idea
and turn it into a virus? There are three things to focus on:
1. How big do you launch?
2. How smooth is it?
3. How can you turn trial into persistence?
1. How many people know about it before the spreading starts?
You can launch big or you can launch small. Vindigo (a viral phenomenon discussed in
detail later) launched their Palm ideavirus with just 100 people. Within weeks, that number
had grown to 3,000, and then quickly to more than 100,000. All without advertising.
However, if you’re entering a vacuum and there’s plenty of competition on the horizon,
launching big (while more expensive) can increase the chances that you’ll succeed.
How to launch big? With traditional interruption advertising. With sponsorships. With free
samples. One of the dumbest things marketers do is put artificial barriers in the way of trial.
For example, it’s obvious that one of the best ways to kill sales of a new car is to charge
people $100 to take a test drive.
But charging for a test drive is just as dumb as a politician charging people to hear a speech,
or a movie studio charging for the coming attractions. When you launch an ideavirus, the
more people who can see it fast, the faster it will spread.
Unleashing the Ideavirus 60 http://www.ideavirus.com
2. The importance of smoothness.
In addition to being persistent and cool, an ideavirus spreads the fastest when it’s smooth.
Persistence matters because the longer people are sneezing about your idea, the more people
they infect. Cool is critical because if it’s not virusworthy, it’s just not going to take off. But
smooth is essential because if you make it easy for the virus to spread, it’s more likely to do
so. In viral marketing (for products like the Polaroid camera and Ofoto.com) the ideal
solution is to build smooth transference tools right into the idea—which can be difficult.
But that doesn’t mean you shouldn’t try. Amazon tried with “Member Get a Member”
promotions, in which they bribe members to tell their friends to buy books from Amazon
(get $5 for your friends and $5 for you!). ZDNet puts a button next to every story they
publish on their website: click here to send this article to a friend. Smooth.
Tupperware built an entire company around the smooth transfer of product enthusiasm
from one friend to another. When you have a Tupperware party you are simultaneously
hanging out with friends, demonstrating products you like, selling them and recruiting other
Unleashing the Ideavirus 61 http://www.ideavirus.com
people to do the same to their friends. By focusing obsessively on how to make it smooth,
you can dramatically increase the velocity of the ideavirus.
3. Turning trial into persistence.
Sooner or later, you’ve got to turn momentary attention into an embrace of your idea, and
then, hopefully, into conversion of the user into a sneezer.
Permission marketing becomes a critical tool in working people through this transition. The
Hare Krishnas have grown their sect by inviting people to eat a vegetarian dinner with them.
Intrigued or just hungry, people give them momentary attention and then permission to talk
to them about this new way of life.
Sometimes people leave, having done nothing but eaten dinner. Sometimes, people listen to
what’s being said and decide to embrace the ideals being discussed. And sometimes, they
become converted and turn into sneezers, volunteering to go out and invite other people over
for dinner the next night.
Note that they didn’t start by walking up to a stranger and proselytizing about their religion.
Instead, they used a gradual technique to sell their idea effectively and turn it into a virus.
Are there religions that are not viruses? Sure, the Shakers were. They didn’t try to convert at
all. That’s why there are no Shakers left.
On the web, this multi-step process is too often overlooked by companies facing short-term
financial pressure (combine this with the legendary short attention span of entrepreneurs and
you can see why this happens). Instead of building a virusworthy cool product or service,
identifying a hive, promoting an idea, and making it smooth and persistent, they just spend a
few million dollars to buy advertising.
The hope, of course, is that somehow by spending enough money on clever ads, they’ll
magically create a critical mass of positive energy that will turn their idea into a virus.
They’re looking for a shortcut, and as a result, leading their companies to doom. Building a
virus takes insight, talent and most of all, patience.
Unleashing the Ideavirus 62 http://www.ideavirus.com
After a consumer is interested enough to visit ZDNet or Google.com or some other neat new
site, what should these sites do to augment the ideavirus? Three things:
1. Get permission to follow up: make it easy for me to learn about why I should embrace this
idea over time. All those ads you ran are a great way to get someone to your site, but it might
cost your site $100 in marketing expenditures to get that one visit from just one consumer. If
you don’t get permission to follow up, the entire $100 is wasted.
2. Make as many supporting manifestos available as possible, in whatever forms necessary, to
turn consumers from skeptics into converts. This can include endorsements, press reviews,
even criticisms and commonly made objections. Think of the Hare Krishnas at dinner. The
more they can expose you to during that hour, the better the odds of spreading the virus.
3. Make it easy for consumers to spread the ideavirus by providing a multitude of tell-afriend
tools, as well as overt rewards for becoming a sneezer.
Unleashing the Ideavirus 63 http://www.ideavirus.com
Ten Questions Ideavirus Marketers Want Answered
1.
Have we chosen a hive we’re capable of dominating?
2.
How likely are the powerful sneezers to adopt our virus?
3.
Do we know who the powerful sneezers are and how to contact them?
4.
What can we do to our product to make it more virusworthy?
5.
Are we rewarding promiscuous sneezers sufficiently to get them on our side?
6.
Have we figured out what we want the sneezers to say? How are we teaching them to say
it?
7.
Even if our product isn’t purely viral by nature, is it possible to add more viral marketing
elements to it (or to our marketing approach)?
8.
Do we know how to get permission from people once they’ve been touched by the virus?
Do we know what to say after we get permission?
9.
How smooth is the transfer of the ideavirus?
10. Is our offering good enough to wow this hive?
11. Do we have the resources and time to dominate this hive before others rush in to fill the
vacuum?
12. Have we built in multiple feedback loops so we can alter the virus as it moves and grows?
13. Have we identified the vector we want the virus to move in, and have we built the tools
and plans to keep it moving in the vector we’d like?
Unleashing the Ideavirus 64 http://www.ideavirus.com
Five Ways To Unleash An Ideavirus
Of the five ways to unleash an ideavirus, the most important element they share is that for
best results you must build this thinking in from the very beginning. If you’ve got an existing
product or service and you’re hoping to build a virus around it, your job will be more
difficult. The ideas behind the lightning fast success stories have all worked because the
ideavirus concept was baked in from the start. That’s one of the reasons more established
companies are having so much trouble competing in the new economy—they’re restricted
because of the standards and systems they built in years ago.
The five techniques, in order of sheer market power, are:
1. Go full viral. The more you use it, the more you market it (whether you want to or not).
In essence, using the product is the same as marketing it.
2. Pay off the promiscuous.
3. Make it smooth for the powerful.
4. Digitally augment word of mouth.
5. Altruism…reward the friends of the promiscuous.
1. Go full viral. This is the holy grail of ideavirus marketing. The beauty of viral marketing is
that if you properly construct the virus, you can grow like a weed and dominate the
market—if you can do it before the competition.
Polaroid and Hotmail are the poster children for viral marketing, but there are a few other
that are worth looking at:
Blue Mountain Arts was a pioneer in creating a virus around the idea of sending electronic
greeting cards. The virus is simple to understand—in order to send a greeting card
Unleashing the Ideavirus 65 http://www.ideavirus.com
successfully, you’ve got to send it to someone. Of course, once someone receives the card, if
they like the idea, they’re just a click away from sending someone else a card!
Even though the cards featured by Blue Mountain Arts could charitably be called “cheesy,”
the virus caught on. People got the idea that it might be fun to send electronic cards to their
friends… and the idea spread. The company started small, with no real advertising. Just a
few people sent the first batch of cards.
But then the magic of viral marketing kicked in. Let’s assume that each person sends cards to
five people. Let’s also assume that those recipients have a 50% chance of being interested
enough in the concept to go to the site and send cards to five of their friends. If we start with
ten people, the generations look like this:
10 people send 50 cards
which means that 25 people get the virus and send 125 cards
which means that 63 people get the virus and send 315 cards
which means that 162 people get the virus and send 810 cards
which means that 405 people get the virus and send 2025 cards…
Now, that may seem like a slow start, but if you assume that each generation takes three days
to occur (I send out ten cards and within three days, five friends show up and do the same
thing), then you’d have 58 million users in 54 days!
Of course, that doesn’t really happen. It’s unlikely you’ll be able to continue to get a 50%
conversion rate. And it’s certain that you’ll soon hit duplication, with individuals starting to
get cards from different people. But the math is nevertheless stunning.
The key number in the equation is the percentage of people who convert. If you lower it
from 50% in the Blue Mountain Arts example to 30%, the number of users drops from 58
million to less than 10,000. Which is why conversion is so critical.
The battle between Hallmark and Blue Mountain in this space is fascinating. Hallmark and
American Greetings, both old-line card companies, were well aware of the potential of the
Unleashing the Ideavirus 66 http://www.ideavirus.com
Internet. But they were also unable to imagine a world in which cards didn’t cost money—so
they made the cards they sold online available for a fee.
As a result, no virus emerged from the Hallmark site. If someone was charmed by a card and
came to the site to send a few, they discovered that they’d have to pay to do that. They didn’t
convert. Conversion fell below the magic number and the virus never ignited.
You can compute the magic number by multiplying the number of cards the average user
sends (in the example above, it’s 5) by the percentage of people who convert (50%). In this
case, the magic number is 2.5, which is how much bigger each generation will be than the
one before. Until the magic number exceeds 1.2 or 1.3, it’s hard for a product to get viral fast
enough to beat the competition.
By focusing on smoothness (it’s only three clicks to send a card and it’s free, so go ahead and
try it), Blue Mountain built an amazing conversion machine. As a result, the site grew and
grew until Excite bought it for nearly a billion dollars worth of stock. Whatever Blue
Mountain’s goal—to make a lot of money, to affect a lot of people or to spread their idea far
and wide—they’ve succeeded.
Hallmark and American Greetings have seen the light, and now they, along with Yahoo! and
others, offer free greeting cards. The challenge that they face is that there’s no longer a
vacuum, so their ideavirus can’t spread as fast, and their magic number is far lower than that
which Blue Mountain Arts enjoyed at its peak (the number must go down as the population
of untouched people approaches zero).
Another example of viral marketing worth looking at is Ofoto. Ofoto is an Internet
alternative to Fotomat. Instead of dropping your film off at the corner, you send your digital
camera files to Ofoto and they send back beautiful prints.
This is a compelling story, but there isn’t enough money in the world to communicate it
through traditional marketing means. Kodak spends $100 million a year in advertising (and
has been advertising for a hundred years). On top of the huge amount of noise out there,
Unleashing the Ideavirus 67 http://www.ideavirus.com
there are just no easy media channels Ofoto can use to spread its message in a cost-effective,
fast way to the target hive: digital photography users.
So Ofoto also launched a digital photo album. This album lets you post your favorite digital
photos online, for free, and invite friends to come see them. Here’s the good part: a digital
photo album with no one looking at it is worthless!
Thus, once you upload your photos, you’ve got to motivate your friends and relatives to stop
by and see the photos. You become Ofoto’s #1 marketing weapon.
Take pictures of your kid’s soccer team. Upload them. Tell everyone on the team where to
find the photos.
Some of the parents will like the photos so much they’ll click a button and buy a print.
Ofoto has a new customer. Interestingly, the content was created by someone else —not the
person who bought the photo. This is an effect that never happens to Kodak.
Even better, some people who see the photos of the soccer team will realize that they too
would like to be able to post pictures for friends. So the torch passes, and Ofoto has added
another photographer to its ever growing stable.
It’s worth noting that the conversion rate for Ofoto is almost certainly going to be lower
than it was for Blue Mountain Arts. First, it’s much less smooth. In order to spread the word
that you’ve posted someone’s picture, you’ve got to find that person and tell them about it,
and then they’ve got to hustle themselves to a computer and go look at it… not as clean as
the all-electronic approach of Blue Mountain.
Second, the virus is less smooth. If I want to buy a print, I’ve got to enter my name and
address, AND I’ve got to pay for it. If I want to upload photos, I’ve got to figure out how to
use my digital camera upload files, or I’ve got to mail in my traditional film to Ofoto for
developing.
Unleashing the Ideavirus 68 http://www.ideavirus.com
Despite these obstacles, Ofoto has a very positive magic number as demonstrated by the fact
that they’ve amassed more than 500,000 users in less than 12 weeks.
The astute reader has probably noticed a critical difference between Hotmail and Blue
Mountain Arts vs. Ofoto.
Hotmail and Blue Mountain Arts are self-referencing ideaviruses. The virus spreads with the
use of the product whether the user wants it to or not. When you first start using Hotmail, the
self-promoting signature line promoting Hotmail is automatically included in every email
you send. You didn’t choose to do that (though you can turn it off), it just goes along
anyway.
In the case of Blue Mountain, the symbiotic relationship between the product and the
marketing is even more obvious. The card is the marketing, so using it is, by definition,
promoting it.
Ofoto, on the other hand, does no such thing. You could quite happily use Ofoto for
developing, sorting and storing your photos and never recommend it to anyone.
Clearly, if the marketing element is benign and totally integrated into your offering, your
magic number is going to be much higher; the symbiosis pays off with big dividends. The
product has 100% efficiency…every user becomes a promoter. The challenge is this: it only
works for a very select group of products and services—probably not yours.
Why have I gone to great lengths to point out that viral marketing is merely a subset of
ideavirus marketing? Because while very few of us will ever be lucky enough to enjoy the full
fruits of a viral marketing campaign, most of us can unleash an ideavirus.
2. Pay off the promiscuous.
Paying powerful sneezers in an effort to make them promiscuous (but have them keep the
power) is an extremely difficult balancing act, but if you can do it successfully, you can turn
it into a billion dollar business.
Unleashing the Ideavirus 69 http://www.ideavirus.com
Some people call it network marketing or multi-level marketing. Others think of it as a paid
celebrity endorsement. But it can be as simple as member-get-a-member for your local health
club.
The basic idea is simple: If your recommendation is going to help my business, I’m happy to
pay you to recommend me.
The implementations vary all over the map. When Nike paid the coach of the Duke
University basketball team millions of dollars (for him, not Duke) to coerce his team
members to switch to Nike shoes, they were turning a formerly powerful sneezer into a
promiscuous one. Why? When people see what the Blue Devils wear, they might decide to
wear the same thing.
On the Net, technology makes it easy to take this model and make it much more personal.
Amazon’s affiliate program, in which Amazon pays users a portion of the book revenue they
generate through referrals, is built around this model.
Go to http://www.permission.com. There, at the bottom of the page, is a link where you can buy a
copy of Permission Marketing. Click on it and it will take you to Barnes & Noble or
Amazon—right to the page on the site that sells Permission Marketing. Both stores give me a
kickback on every sale.
Did I send you to Amazon just because I’m going to get a kickback? Nope. It doesn’t do me
any good to recommend a bookseller where you won’t end up buying the book—I’ll end up
with no kickback and no book sales either. I recommended Amazon because you’re likely to
have one-click shopping already set up, increasing the chances the book will get sold. I also
recommended Barnes & Noble, because their affiliate program is at least as good, and some
of my customers would prefer to shop there. But the kickback still influenced my decision,
and has clearly motivated hundreds of thousands of individuals and businesses to set up links
to their favorite books at Amazon and at Barnes & Noble.
Unleashing the Ideavirus 70 http://www.ideavirus.com
This approach is far less risky than Nike’s. Nike has no idea if the Blue Devils actually sell
shoes. They also have to pay for the endorsement in advance, with no refunds if they’re
wrong.
Amazon and other affiliate marketers, on the other hand, are using the power of the Net to
create a deal with no losers and no downside. You can set up an affiliate link in a few
minutes. For free. If it works, you get paid. If it doesn’t work, you don’t. And it doesn’t cost
Amazon a dime.
Because of this risk model, affiliate programs are flourishing. Be Free, a leading provider of
services to marketers using this approach, calls it Performance Marketing. They currently list
235 websites that are offering affiliate programs.
While it may be interesting to earn a dollar or two on a sale (interesting, that is, if you can
sell thousands a month), some companies are taking a different tack.
Woody Chin, founder of Referrals.com, thinks he’s found a way to change the way people
interact when it comes to job hunts and other sorts of business-to-business commerce.
Instead of paying people a nickel or even a buck, he’s paying people $1,000 to $5,000 each
for that priceless commodity: a referral.
Here’s how job filling works before Referrals.com: Hire a contingency headhunter. Offer to
pay a third of the final salary, but only if you hire someone the headhunter brings along. So
the hunter stands to earn $20,000 or more.
Now, the headhunter hits the phones. She calls everyone she can, and basically begs for leads.
There’s no obvious benefit to the referrer, except for the possible goodwill that occurs when
you find a friend a job.
Woody and Referrals.com are aiming to change that.
With Referrals.com, the hiring manager sends out a description of the job to people she
thinks might know good candidates. These referrers can be people she knows in the industry,
Unleashing the Ideavirus 71 http://www.ideavirus.com
company insiders or super-agents (and anyone can be a super-agent—read on). The key here
is that the referrals are from people whose opinion she values. The description includes a
bounty she is willing to pay for a hire as well as a limit to how deep and how wide a referral
tree she desires.
It’s fascinating to see that Referrals.com is building in a limit to the ideavirus! They don’t
want any given job search to get out of control and start being passed from friend to friend
ad infinitum. Instead, they artificially limit how deep a job search can go into the
community. This limit ensures that employers can focus their searches on a certain hive
without it running amok throughout the entire population. The web has turned what might
have been a multi-level marketing business into a carefully regulated ideavirus.
Anyone who gets involved in referring can sign-up to be a “super-agent.” Once you sign up
as a super-agent, your performance ratings will be available to hiring managers (in recruiting)
looking to find experts to help with their search. And of course, you get first crack at the new
job listings.
Let’s say the company wants a CTO. Let’s say they’re willing to pay $5,000 for a successful
hire. And let’s say they’re only willing to go two levels down the referral tree.
Now, a super-agent can send an email to five people he knows who might be perfect for the
job. If one of them takes the job, the super-agent gets $5,000 just for sending five emails.
But let’s say none of the recipients want the job. But one of them knows someone who does.
Bang. He forwards the mail a second time, and this time it lands on the desk of the perfect
hire. Assuming this guy gets the job, the first super-agent and the second referrer split the
money.
All of a sudden, you’ve monetized word of mouth! Referrals.com could create a class of
thousands of “super-agents” who spend their time doing nothing but finding people through
networking. Essentially, it lets just about anyone become a contingency headhunter. (Now, I
know what you think of contingency headhunters… but the small scale of each person’s tree
makes it unlikely it’ll ever get that bad!)
Unleashing the Ideavirus 72 http://www.ideavirus.com
Of course, it goes deeper than this. If it works for headhunting, maybe it works for finding
new clients for Viant, or for people who are looking to take a cruise. Or what about real
estate? If everyone could become a contingency broker, doesn’t life online get interesting? If
the Internet succeeds when it monetizes previously random analog events (like garage sales at
eBay) then this may just be the killer app for this space.
Does Referrals.com work? I actually have no idea. It’s just launching. We don’t know if the
promiscuous will overwhelm the powerful and pollute the whole system. We don’t know the
velocity of the idea or how long this particular virus will last. But it’s clear that something will
replace the current model of headhunters spamming powerful sneezers and essentially
stealing their rolodex.
Alladvantage.com wanted to take the multi-level marketing approach instead. Each person
they signed up got a commission on the revenue generated by the people those people signed
up. And so on.
They got off to a very hot start, signing up millions of users in a very short period of time.
But now, according to the Wall Street Journal, they’ve discovered that maybe they were
paying these promiscuous sneezers too much to make any money in the end. So Alladvantage
just announced new rules in the way they pay their sneezers.
The result was predictable… their most important sneezers were outraged. When you pay
people to refer on your behalf, you’ve got to expect that they are indeed motivated by
money, and when the money goes, so will your sneezers.
Multi-level marketing has gotten a bad reputation among powerful sneezers. Why? Because
individuals are encouraged to suspend their judgment and embrace the idea that several
generations down the pike, they’ll be rich.
While this is a fine choice for an individual to make, it’s problematic for those who are
friends with this individual. Why? Because the personal interaction is no longer on a level
playing field. Person A uses his friendship with person B to encourage her to buy or use
Unleashing the Ideavirus 73 http://www.ideavirus.com
something that isn’t necessarily in her best interest. If she agrees, then person A sees a
significant return, while person B inevitably sees LESS of a return. If she resists, the
friendship is strained.
If the pyramid is steep enough (if there’s enough money promised at the end of the tunnel),
this sort of approach can work. But it usually leaves scorched earth in its path, and
disappointments in the form of broken friendships or financial promises not reached.
To date, very few companies—online or off—have figured out a way to turn network or
multi-level marketing into a large, sustainable business. Those that have, like Rexall, Amway
and perhaps Alladvantage, now have to work even harder to undo the bad reputation that
this approach has earned.
3. Make it smooth for the powerful.
One of the most elegant ways to take advantage of the new tight networking among
consumers is to identify the powerful members of a hive and make it as easy as possible for
them to tell each other about an ideavirus.
When online content sites first debuted, they were extremely hesitant about sharing their
articles. Some of them went so far as to make it impossible to copy and paste the text in an
article. They were petrified that one person would copy an article and no one else would
come to the site and see the ads.
What they soon learned, however, was that the easier they made it to share, the more likely
people were to tell their friends. And if someone came in to read one article, they were likely
to read more. ZDNet.com was one of the first sites I encountered that used this technique.
In one promotion my former company Yoyodyne did for them, they found that more than
20% of the people exposed to a compelling piece of content actually forwarded it to a friend.
Fast Company magazine—devoted to bootstrapping start-ups—does the same thing. Visit
http://www.fastcompany.com/team/wtaylor.html and you can see a list of the articles that co-
Unleashing the Ideavirus 74 http://www.ideavirus.com
founder Bill Taylor has written for that magazine. They’re all there, unabridged, and you can
read them for free.
But the smooth part of this wannabe ideavirus is the little button on the bottom that says
“Click here to send this page to a friend.” All you have to do is type in their email address
and your email address and—boom—it’s done. If his articles contain ideas that are
virusworthy, the Fast Company site is doing a good job in helping them go viral.
Inside.com, which sells subscriptions to its online media newsletter and website for $200, is
happy to have people send these pricey articles to non-subscribing friends. In fact, there’s a
big “send to a friend” button on the bottom of every article. The reason is obvious. Once
you’ve read one, you might be willing to pay for more. All they need is a few of the ideas
they publish to become viral and suddenly the business of selling subscriptions will get a lot
healthier.
In essence, Inside.com is hoping that its readers will market the site for them, spreading ideas
that might go viral and then bringing in new paying customers as a result.
4. Digitally augment word of mouth.
This is a really interesting way of looking at the fundamental change that’s occurring, and
understanding how word of mouth is different from an ideavirus.
If I was delighted by a movie in the old days, I’d tell a friend or two. My comments would
end up influencing three or four or six people.
There are plenty of books on this topic and marketers have always been enamored by the
potential of word of mouth. Alas, without amplification, it usually peters out.
Today, if I like a movie, I can post my comments on a variety of online movie sites. Or I can
email ten friends (who can each forward the mail to ten friends). Later, when the video
comes out, I can post my review on Amazon, where hundreds or thousands of people might
read it.
Unleashing the Ideavirus 75 http://www.ideavirus.com
Using a service like Epinions.com, I can go online and search out opinions on everything
from BMW motorcycles to summer camps.
What’s neat about digital word of mouth (let’s call it word of mouse) is:
1.
It is extremely persistent. Unlike a comment at the watercooler or over the phone, a
comment in a newsgroup, on Epionions or Amazon lasts forever.
2.
It has much greater velocity. The number of ripples my stone makes when dropped in
the pond of public opinion is far greater online. Why? Because if I tell you I like my car,
it might be months before that sort of car comes up again in conversation. But online,
conversations are happening 24 hours a day, and the “conversation” on any given web
page is precisely about what that page is about. As a result, the number of interactions
multiplies geometrically.
3.
It can have more credibility. At first, the opposite was true. An anonymous stock tip or
other form of online recommendation was totally suspect. The sneezer could be a paid
mole, or worse, someone with horrible taste. But now, thanks to rating systems and the
presence of powerful sneezers, it’s possible to know how congruent your tastes are with
those of the sneezer, so it ends up having a ton of credibility.
Amazon is now rating the reviewers! A visit to
http://www.amazon.com/exec/obidos/tg/cm/member-reviews/-/AFVQZQ8PW0L/102-72353452994554
shows me that Harriet Klausner is the top ranked reviewer on the entire site.
Harriet, a retired librarian, has written more than 500 reviews and has received more than
5,000 votes from other folks who agree with her taste. If Harriet likes a book that you like,
you’re certainly going to give her sneeze some credence in the future.
5. Altruism.
Several years ago, a hot chef in Chicago decided to go out on his own and open his first
restaurant. Realizing how competitive the market was, he did a neat thing. He never opened
it to the public. He refused to accept reservations from strangers.
Unleashing the Ideavirus 76 http://www.ideavirus.com
If you wanted to get into Les Nomades, you had to be a member. And how did you do that?
Well, the first 500 people were given memberships because the chef knew them as regular
customers at his old job, and he personally invited them.
Then he told each member that they were welcome to sponsor other members. All they had
to do was vouch for someone and he’d make them a member too.
So, what’s in it for the member to nominate someone else? Simple. They scored points with
their friends as powerful sneezers because they could “get you in” to the hottest restaurant in
town.
Of course, this wouldn’t have worked if the restaurant hadn’t been spectacular. But it was.
And it was exclusive. But by allowing his members to do his marketing for him, by giving
them an altruistic tool that increased their power as professional sneezers, the chef was able to
get out of the way and let his customers sell for him.
Unleashing the Ideavirus 77 http://www.ideavirus.com
SECTION THREE: The Ideavirus Formula
STEAL THIS IDEA!
Here’s what you can do to spread the word about Unleashing the Ideavirus:
1. Send this file to a friend (it’s sort of big, so ask first).
2. Send them a link to http://www.ideavirus.com so they can download it themselves.
3. Visit http://www.fastcompany.com/ideavirus to read the Fast Company article.
4. Buy a copy of the hardcover book at
http://www.amazon.com/exec/obidos/ASIN/0970309902/permissionmarket.
5. Print out as many copies as you like.
Unleashing the Ideavirus 78 http://www.ideavirus.com
Managing Digitally-Augmented Word Of Mouth
That’s what I would have called this book if it had been published by the Harvard Business
Review. And you probably wouldn’t be reading it now! Words matter. Understanding
exactly what we’re talking about makes it far easier to actually do something about the world
around us. That’s why I take such great pains to invent new words and get us all thinking
about exactly what they mean.
If we bump into each other at some convention and you ask me to talk about your business,
I’ll instantly start using words like hive and sneezer and velocity and smoothness. Why?
Because these shorthand phrases make it easy for us to communicate. By using words that
indicate we both understand the underlying factors that leverage an ideavirus, we’re far
likelier to actually get something done.
The ideavirus formula has eight co-efficients. Each one represents not just a concept, but a
variable that you can tweak to make your product or service more viral, to create the
elements you need to drive your idea into the community.
Unleashing the Ideavirus 79 http://www.ideavirus.com
Tweak The Formula And Make It Work
It may be possible to write down the key elements of building and spreading a virus as a
mathematical formula. No, I don’t think you’ll use it. But understanding the co-efficients
makes it far easier to see what’s important and what’s not. They also help you see the wide
range of factors that can help an idea go viral; focusing on the most highly leveraged factor
for your idea is a first step in launching the virus.
Multiply these five factors:
[reputation benefit to powerful sneezer of recommending virus]
[selfish benefit to promiscuous sneezer of recommending virus]
[smoothness of sharing the virus with a friend]
[power of the amplifier used to spread positive word of mouth]
[frequency of interactions among hive members]
Divided by the sum of these two factors:
[number of times you need to expose someone in this hive in order for the virus to catch]
[number of different sneezers who have to recommend a virus to a given individual for it to
ignite]
And then multiply that by the product of these four factors:
[percentage of infected hive members likely to sneeze]
[number of people the infected sneezer is likely to contact]
[persistence of the virus (how long does a sneezer sneeze?)]
[number of people infected /(divided by) number of people in the hive]
Comments on each component:
[reputation benefit to powerful sneezer of recommending virus]
Powerful sneezers can’t be bought. But don’t forget that they are selfishly motivated. Will
this make me look smart? Will it make someone else happy? Will it make the world a better
place? There are plenty of levers that motivate powerful sneezers to spread the word, and they
are often complicated and subtle. Some of our favorite powerful sneezers: Zagats, Linus
Unleashing the Ideavirus 80 http://www.ideavirus.com
Torvald, Paul Newman, Ruth Reichl, Randall Rothenberg, Andy Hertzfeld, Chuck Close,
Spike Lee, Bill Taylor, Don Peppers, Peter Mayles, Alan Greenspan and Yo-Yo Ma. You may
not know all of these names, and there are plenty of hive-based sneezers I’ve never heard of,
but what they all have in common is that they’re perceived as insightful and altruistic. Once
people think they can be bought off, their power plummets.
[selfish benefit to promiscuous sneezer of recommending virus]
As we saw in the Amazon affiliate example, if you can make the benefit to the individual
both significant and easy to achieve, people will respond to it. Amazon signed up hundreds
of thousands of affiliates with a simple offer (get a percentage kickback on everything you
recommend) and backed it up with a two-minute procedure for qualifying and actually
getting started.
[smoothness of sharing the virus with a friend]
Once I want to tell someone about your idea, how do I do it? If it’s got a dumb, hard-to-say
name, or an embarrassing implication, I’ll probably pass. On the other hand, Hotmail is
smooth indeed, because every time I send email I’m talking about the idea.
The Polaroid camera used this smoothness brilliantly. After all, the only reason to take a
picture is to show it to other people, and if you can make the showing (and the waiting) turn
into a discussion of the idea, so much the better.
The beauty of Vindigo is similar. In order to tell you about Vindigo, I’m going to pull my
Palm out of my pocket and show it to you. But once I show it to you, I’m only one button
away from actually giving it to you. The thing I want to show you is how easy it is to give
you, so the virus self-reinforces.
Ideally, you’ll figure out not only what a sneezer should say to someone when they talk about
your idea, you’ll also make it easy and automatic for them to do so.
[power of the amplifier used to spread positive word of mouth]
The mother of a friend of mine was runner up for Miss America in the early 1960s. I think
she lost to Anita Bryant. Alas, coming in second did very little for her career. Anita, on the
Unleashing the Ideavirus 81 http://www.ideavirus.com
other hand, made her fortune squeezing oranges. Point is that once she conquered that hive
of a few judges, the news was amplified far and wide. And the amplification (as per Zipf’s
law) gave her the foundation to create a career.
A challenge in tailoring your ideavirus is to make sure that when you do conquer an
individual or dominate a hive, the good news is amplified as far as possible, preferably at no
cost to you.
[frequency of interactions among hive members]
Some hives (like teenage girls) interact with each other far more frequently (and with much
more intensity) than others—like senior citizens. By understanding the frequency of hive
interaction and then trying to focus on moments of high interactivity, you can dramatically
increase the velocity of a virus.
Trade shows, for example, bring sneezers together for intense periods of information
exchange. By doing something as simple as handing out hats with your logo on them, you
make it more likely that you’ll reinforce your message during this critical time.
[number of times you need to expose someone in this hive in order for the virus to catch]
Some viruses are smooth indeed. See them once and you understand them. It only took one
exposure to the Macarena to get it. In general, the simpler the idea and the lower the risk, the
more likely someone is to get infected. Most of all, though, this variable is driven by how
viral the idea is to begin with. Meaning: is it cool, wonderful, important, dramatically better
and fun?
[number of different sneezers who have to recommend a virus for it to ignite]
Not all ideas have Medusa qualities. We usually need to hear from external sources before
we’re willing to buy into the new thing, especially for risky ideas. Bestseller lists for books
and other products are terrific, as are the sort of seal-of-approval validations that institutional
sneezers look for. “Hey, if it’s good enough for IBM…” say the more timid prospects.
Unleashing the Ideavirus 82 http://www.ideavirus.com
Bestseller lists are a stand-in for the number of recommendations you need to decide. A
bestseller list says, “There are 24,000 other people who liked this idea.” The reviews on
Amazon are another great example of this. When 50 people post a positive review, it counts
for something.
The alternative, which also works, is actually hearing from sneezers one by one. Some ideas
need only one sneezer to get you try it (like a restaurant) while others might need a hundred
(like switching over to using email or a Palm to run your business).
[percentage of infected hive members likely to sneeze]
Some hives are filled with sneezers. And some ideas make people sneeze more than others.
When John McCain tried to capture his party’s presidential nomination, he discovered an
entire population of people, previously dormant, who were so moved by his candor and
campaign finance message that they started sneezing on his behalf. Not accidentally, many of
these sneezers were in the media, carrying his message far and wide.
Another variable is your ability to increase the likelihood that people who don’t usually
sneeze decide that they’ll make an exception just for you. Focus on the time and place of
your introduction to the hive. Want your employees to spread an important new idea among
themselves? Don’t introduce it at the Friday afternoon beer blast, but rather make it a special
event. Give them the tools they need to spread the word. Reward them for doing so, or make
it clear how the virus will dramatically help your company. It’s not an afterthought—it’s the
core of your marketing campaign.
[number of people the infected sneezer is likely to contact]
This is an especially important metric for promiscuous sneezers. Once you’ve converted
people into spreading your message for their own personal gain, how can you incent them to
spread the word to a LOT of their friends? One way to do this is by offering increasing
returns to the sneezer—the more you bring us, the more we give you (but be careful not to
turn sneezers into spammers, who end up proselytizing strangers and causing a backlash).
Referrals.com aims to do this by turning their best sneezers into super-agents, giving them
better information and more money.
Unleashing the Ideavirus 83 http://www.ideavirus.com
The same reasoning is obviously a factor in choosing which members of the media to
contact. Saul Hansell at the New York Times has far more reach and influence than Jason
Snaggs at the Phoenix Register. Seems obvious, but what most marketers miss is the fact that a
very small number of powerful sneezers can have an impact far outside their perceived
influence. A reporter with the right readers could have far more sway over your virus than
someone with plenty of reach but little influence.
[persistence of the virus (how long does a sneezer sneeze?)]
A short-lived experience that leaves no lasting effects is hard to turn into a virus, especially if
it’s not a social event like pop music (does every generation after ours realize just how bad
their pop tunes are?). Tattoos, on the other hand, are extraordinarily persistent, so even
though they’re not very smooth, they continue to infect people for decades, making up what
they lack in impact with sheer stick-to-it-ness.
[number of people infected /(divided by) number of people in the hive]
This is about measuring hive dominance. If just a small percentage of people in your chosen
hive have been infected, you really have your work cut out for you. While you shouldn’t
compromise the essence of your idea in order to get a wide platform, you should be superwary
that you don’t start with too small a sample of too large a hive. It’s very easy for your
virus to fade before it catches on.
Unleashing the Ideavirus 84 http://www.ideavirus.com
Advanced Riffs On The Eight Variables You Can Tweak In Building Your Virus
In this section, we’ll take a look at each of the eight underlying variables in the ideavirus
formula, and try to get a handle on exactly how you can manipulate them for your product.
No two industries rely on the eight fundamental principles in precisely the same way. But
virtually every ideavirus I’ve ever seen uses some of these principles in an extraordinary way,
and just about every one could be improved if it expanded further into the other areas.
The Eight:
1. Sneezers
2. Hive
3. Velocity
4. Vector
5. Medium
6. Smoothness
7. Persistence
8. Amplifier
Unleashing the Ideavirus 85 http://www.ideavirus.com
Sneezers
As described earlier, there are two kinds of sneezers: Powerful and Promiscuous. While all
eight elements of the formula are critical, this is the area where many brand marketers have
the most control, and thus the most influence.
Choose your sneezers—don’t let them choose you. By focusing obsessively on who you’re
choosing to sneeze on your behalf, you build the foundation for your virus.
Powerful sneezers are certainly the most seductive, in that the right word from the right
sneezer can make all the difference to your virus. If David Letterman visits your diner on
television, or the New Yorker writes a twenty-page rave about your website, or if you win a
MacArthur Fellowship Grant, well, you’ve really made it.
Oprah Winfrey is quite possibly the most successful sneezer of our generation. She has
single-handledly turned more than a dozen books into national bestsellers. She has launched
a magazine that already has more than half a million subscribers. She can influence millions
of the most powerful consumers in America, just by uttering a few sentences.
It’s interesting to see how effectively Oprah and her brandmate Martha Stewart have
successfully monetized their position as powerful sneezers. If they trip and get perceived as
promiscuous sneezers, as sneezers for hire, their effectiveness is quite reduced. But if they can
maintain their position at the same time they sell books and magazines or sheets and towels,
they’ve effectively leveraged their fame.
But few of us are that lucky. Most times, you’re going to have to focus on powerful but less
influential sneezers—individuals or organizations that have something to gain by endorsing
your idea but aren’t so out there that they’re tagged as promiscous sneezers.
Some powerful sneezers are very prominent and thus very hard to reach. The challenge for
most marketers is to find the second tier of sneezer—the approachable, interested sneezer
who can do almost as much for you as Oprah or Martha, but with whom you have a far
greater chance of making an impact.
Unleashing the Ideavirus 86 http://www.ideavirus.com
The story of The Bridges of Madison County is a great example of this. Warner Books, the
publisher, realized that most other publishers were doing very little to market to the
independent bookstores, and that if he could court them and give them something to sell
that made them feel special, it would translate into a bestseller.
Of course, as soon as the legions of independent booksellers succeeded in turning Bridges
into a phenomenon, they were assaulted by dozens of other less imaginative publishers, all
trying to rush in and use the same strategy. Too late. It got cluttered. They got busy. No one
else ever repeated the focused, obvious success of this approach.
Remember, an ideavirus adores a vacuum, and Bridges filled that vacuum. As other book
marketers rushed in, no one was able ever again to persuade a critical mass of booksellers to
support just one book.
Does this mean Warner was doomed never to be able to repeat this process again? Is that all
there is—just one new gimmick after another? No! Instead, Warner needed to gain
permission from this critical sneezer audience and use that permission to promote the next
book and the next through a channel they were clever enough to build.
Unleashing the Ideavirus 87 http://www.ideavirus.com
Hive
Winning with an ideavirus begins with the choice of hive. And this choice is so important,
I’d suggest the following: choose your hive first, then build the idea.
Traditionally, marketers start with a problem, or a factory, and go from there. I’ve got a great
widget, and now I need a way to take it to market. Or, we’ve got this excess plant
capacity—let’s find a way to fill it. But that’s not what works today. Choose your market by
identifying a hive that has a problem and has the right concentration of sneezers, the right
amplified networking, the right high velocity of communication and, most of all, an
appropriate vacuum.
Success will come to marketers who attack small but intimate hives. Yes, Yahoo! and eBay hit
huge home runs, but they’re remarkable precisely because success across such a large hive is
rare indeed. We can learn a more relevant lesson from magazines.
Fast Company is one of the fastest-growing (and most profitable) magazines ever. Why? Well
it certainly helps that it’s a great magazine. It also helps that the Internet created a huge
demand for this sort of advertising space. But the real success came in the hive that the
editors selected.
Turns out there are hundreds of thousands of people in mid-sized to large companies who
are eager to do a great job, but feel frustrated at the slow pace and mind-numbing
bureaucracy they face every day. Until Fast Company, the members of this hive didn’t even
know there were others just like them. They didn’t have a tool they could use to reach their
peers.
Fast Company became the identity, the bible, the badge of honor for this new hive. It gave
them a way to communicate, to learn and to have confidence in themselves. By every
measure, the magazine was virusworthy.
Just about every reader of Fast Company became a powerful sneezer. With no compensation
and very little encouragement, they started signing up co-workers for subscriptions, Xeroxing
Unleashing the Ideavirus 88 http://www.ideavirus.com
page after page of the magazine and passing it around the office. The readers even created a
worldwide network of support groups, meeting in cities on a monthly basis, with no help at
all from the magazine.
Fast Company filled a vacuum. It got viral. It enchanted and connected with a huge legion of
powerful sneezers. All because the editors chose the right hive and created a virusworthy
product.
A few years later, Time Warner launched Real Simple magazine, inspired by the significant
sales of books about simple living. So they launched a magazine dedicated to simplifying our
lives. Obviously, it’s aimed at a very different hive than that of Fast Company. Alas, the
magazine is off to a slow start.
Why?
Because this hive isn’t the right one at the right time. Because there’s a real lack of aggressive
powerful sneezers. Because the hive doesn’t have a built-in forum for communicating with
each other (it’s not office-centric like Fast Company). As a result, the magazine is having a
much harder time going viral.
Choosing your hive
The Zagats Guide to New York City Restaurants is a fascinating document. According to
Zagats, the book is put together by 100,000 reviewers, who ate out an average of four times a
week, spending an average of $40 a person. Do the math. That’s more than $8,000 of mostly
after-tax money spent on eating out every year.
This very special hive of people shares a demographic but is by no means typical of the U.S.
population (which in itself is very different from the world at large). Trying to appeal to
everyone is almost sure to fail, for the simple reason that everyone wants something different!
The reason there isn’t one restaurant in Cincinnati or Indianapolis or Tallahassee that’s as
good as the Union Square Café in New York is not that the population can’t afford the tab.
Unleashing the Ideavirus 89 http://www.ideavirus.com
There’s certainly enough money in those towns to keep the seats filled in several restaurants
of this ilk. It’s simply that the hive that can afford these restaurants don’t have a high velocity
way to get the word out fast enough to keep the restaurateur happy. And it’s not clear that
they’d persist. In other words, eating in a New York-style fancy restaurant probably isn’t the
way these “out-of-town” hives choose to spend their time and money. Same’s thing true for a
New York hive that wouldn’t reward a French restaurant that might do just great in Paris.
All of which is a very fancy way of saying, “If the hive doesn’t want it, you picked the wrong
hive.”
Selecting a hive that respects the core value of your virus is a critical first step in laying the
foundation for promoting the idea. College students want something different from
gardeners, who are quite different from computer geeks. Targeting everyone is a sure path to
failure.
Of course, the real reason you want to pick the right hive is not because their values match
the benefits of your product. It’s because when you pick the right hive (and a small enough
hive) you have a chance of overwhelming it—of pumping so much positive juice into your
digital word of mouth that you really do dominate, that so many sneezers are recommending
you to the rest of the hive that the majority surrenders and the entire hive converts.
Once your idea starts coursing through a hive again and again and again, you’ll have a piling
on effect. People will want to be exposed to your idea just because everyone else in the hive
they respect is talking about it.
The mistake that’s so easy to make is to get greedy as you choose your hive, to say, “this
product is for everyone” or “anyone can benefit from this idea.” Well, there are seven billion
people on the planet, so it’s unlikely your comment is correct; even if it is, there’s little
chance that a virus would spread across a hive that big.
Far better to pick smaller hives and conquer them a few at a time. Far better to identify
consumers when they’re grouped in bunches (at a trade show, say, or geographically) and
then allow the concentrated essence of your virus spread to other hives.
Unleashing the Ideavirus 90 http://www.ideavirus.com
Coors did this with beer years ago. You could only get Coors in Colorado, then you could
only get it west of the Mississippi. By concentrating their marketing dollars, they addressed a
smaller hive. This enabled them to get a larger percentage of the hive to sample the product.
This core group then had a smooth way to spread the word, and it quickly conquered one
state after another.
Without any effort from the Coors people, the virus spread to the East Coast. Coors fielded
thousands of requests from disappointed drinkers who wanted to try this new beer they’d
heard about, but couldn’t.
Coors dominated a hive. Then they went national to try to fulfill the demand created when
their hive spread the word. Unfortunately, the new hive was so large, it turned out to be
difficult to satisfy and dominate.
Compare the powerful, nearly effortless spread of their idea with the challenges they face
today. As a national brand in a stagnant market, growth by any method is hard to come by.
They built their company on a unique virus, but they couldn’t continue to grow their
company the same way.
Unleashing the Ideavirus 91 http://www.ideavirus.com
Velocity
Napster is a worldwide file sharing database that lets Internet users share MP3 files. In
essence, you can listen to the digital record collection of millions of other people. The idea
behind Napster turned into a virus and grew like crazy. Why?
They hit college campuses—a hotbed of communication. A virus can spread across a campus
in a matter of hours. When a dear friend of mine went to Tufts in the late 1970s his
roommate started a rumor that Paul McCartney had died (this was before John Lennon’s
tragic death—they weren’t that callous). Within an hour, they started hearing the rumor
back—from friends of friends of friends who couldn’t precisely remember where or how
they’d heard it.
Napster was spread the same way. How? Because in addition to being on a college campus,
Napster lives on the Internet. So, instead of being word of mouth as in the Paul McCartney
example, it was digitally augmented word of mouth. On college campuses, everyone has
email, and email is both instantaneous and amplified. You can send an email to thirty or
forty friends as easily as you can write to one. So once a powerful sneezer had tried the
software and confirmed that it worked as advertised, the word spread fast.
Why is velocity so important? Remember, filling a vacuum is far easier than going second. If
the velocity of a virus isn’t fast enough, a competitor may leapfrog past you into a new hive
before you can get there, dominating as the “original” in that market.
This happened with beer, in which regional favorites have long survived the introduction of
nationwide refrigerated delivery. It even happened with the college entrance exams, in which
the ACT is favored in the Midwest, years after the SAT became the standard almost
everywhere else in the world. The only reason this happened is that the ACT got to the
Midwest first.
How does the Net change our economy so dramatically? Because it dramatically increases the
velocity of viruses in various hives. Where it used to take weeks or months for a contractor to
Unleashing the Ideavirus 92 http://www.ideavirus.com
talk with suppliers before building an office tower, he can now do it in just a day using the
Net.
This increase in velocity fundamentally changes the dynamic of a virus. Something
newsworthy might have 20 or 30 or 100 cycles of communications before the issue itself
becomes boring. In the days before the Net, if each cycle only touched one or two or three
people, the virus would die before it got old. Today, these cycles allow the virus to mutate
and evolve as it touches millions of people.
Unleashing the Ideavirus 93 http://www.ideavirus.com
Vector
Richard Dawkins, a brilliant evolutionary theorist, had his own word for the phenomenon
I’m calling ideaviruses: memes. He pointed out that a meme was like a living organism,
surviving not in the real world, but in our world of ideas.
Like a real organism, memes could live and die, and more important, they could evolve.
Every time a meme is passed from person to person, it gets touched, changed
and—sometimes—improved.
Once a meme has been passed around enough, it ceases to evolve as quickly and just becomes
a building block for future memes. Pop singers are experts at stringing together memes and
turning them into concise snapshots of our lives. (Paul Simon is a favorite—Graceland,
Kodachrome, the pop charts… you get the idea).
One of the behaviors noticed by Dawkins and practiced by anyone who markets with
ideaviruses is that memes follow a vector. An idea doesn’t spread evenly and nicely through a
population. Instead, people are more likely to send it in one direction instead of another.
At college, there was always someone who knew where the good parties were (and which
ones to avoid). In your town, there’s someone who just seems to have the inside buzz on
which restaurants are hot. On the Internet, some people seem to be on the vector of the
latest email joke, while others—even in the same company or the same cliques—just don’t
seem to get touched as often.
When you create an idea and lay the groundwork for it to become a virus, it pays to study
the vector you’d like it to follow. Why? Because there’s plenty you can do to influence its
vector, and the vector you choose will have a lot to do with who “gets” the virus. The vector
controls the hives through which the idea flows.
If you’re on the Net, for example, the barriers you erect will influence your vector. If your
site needs Shockwave and Flash and a high-bandwidth connection, you’re not likely to vector
straight into the heart of the AOL user universe, regardless of where you start. If your goal is
Unleashing the Ideavirus 94 http://www.ideavirus.com
to create a trading card mania among third graders, launching a series of cards available only
at liquor stores isn’t going to enhance the vector, even if you seed the virus by handing the
cards out at the local elementary school.
But this is about more than simple access. Remember, the goal is to market to people and
then get out of the way. So an email joke (which almost anyone with a job in this country
could access at home, at work or at the library) will still find its vector. How? There are three
factors:
1.
Who it starts with. Often, the way we decide which direction to send an idea is based on
where it came from. It’s hard, for example, to bring home a joke from the office. Instead,
we’re more likely to send it straight back into the quadrant of life from which it came.
2.
Who it resonates with . An idea has to have impact to be worth sharing at all, and we’re
much more likely to share that idea with someone whom we believe it will impact as
well. After all, if we spread ideas that don’t go viral, it hurts our reputation as powerful
sneezers. This encompasses the idea of access… I’m not likely to spread an idea if the
recipient doesn’t have the energy or the technology or the resources to get engaged with
it.
3.
What’s easy. The medium drives the spread of ideas more than you might imagine. If I
have to print something out, put it in an envelope and mail it to someone, that virus is
going to stop right there. That’s why TV and the Internet have proven to be such
powerful media for the spread of viruses—they’re easy.
Unleashing the Ideavirus 95 http://www.ideavirus.com
Medium
Scientists wasted hundreds of years looking for the medium by which light traveled. They
knew it was making it through the vacuum of space, through water and through air, but
without a medium, they couldn’t figure out how it worked.
The medium is probably the most overlooked part of ideavirus planning and construction.
It’s so obvious, we often don’t see it.
In Japan, teenage schoolgirls started and built a craze to billion-dollar proportions. They
continue to line up to use a special kind of photo booth. Here’s how it works: You enter the
photo booth (similar to the old Polaroid ones of our youth), insert a some coins and it takes
your picture.
But, instead of giving you four shots on a strip, it prints out 16 little tiny one-square-inch
images on stickers.
Now, what are you going to do with 16 pictures of yourself on stickers? Obvious—share
them with your friends! As a result, every popular Japanese schoolgirl has an autograph book
loaded with dozens or hundreds of these stickers. Sort of like your high school yearbook
signing ceremony, but on steroids.
A friend of mine, Sam Attenberg, developed and patented this technology in the States. And
while it never became a full-fledged virus in the U.S., it did develop pockets of intense
activity in certain hives. Some machines were turning $70 an hour in sticker business, every
hour on the hour for weeks at a time. In Japan, two companies dominate a multi-billiondollar
industry in Sticker Stations.
So what’s the medium? It’s the person-to-person exchange of stickers. The medium is the key
to the entire virus. Once the first person got the sheet of stickers, the only way she could use
them was by sharing them with 15 friends. But in sharing them, in using the medium
provided, she had to explain where she got them. Boom. Virus spreads.
Unleashing the Ideavirus 96 http://www.ideavirus.com
PayPal.com is another example of an extremely virulent idea that spread because the medium
was so powerful. PayPal.com is an online service that allows customers of eBay—and other
auction site—customers to transfer money online safely and securely. Now, when you pay
for something you buy on eBay, you can just PayPal.com your money to the person.
Here, the medium is the money. People care a lot about money, and since, in this case, it
solves a time-consuming problem (sending checks and waiting for them to clear), it’s
particularly welcome. And, just as we saw in the Sticker Station example, the act of using the
medium causes us to teach others about the idea.
In both cases, a focus on the medium led to the ultimate success of the virus.
Unleashing the Ideavirus 97 http://www.ideavirus.com
SMOOTHNESS: It Would All Be Easy If We Had Gorgons
The goal, of course, is to have an ideavirus so smooth that once someone is exposed to it,
they are instantly hooked. A virus so powerful that all it takes is one guitar lick on the radio,
one phrase in a book review, one glimpse of a website and you completely and totally “get
it.” And not only do you get it, but you want it. Now and forever.
One of the talents of the great Steve Jobs is that he knows how to design Medusa-like
products. While every Macintosh model has had flaws (some more than others), most of
them have had a sexiness and a design sensibility that has turned many consumers into
instant converts. Macintosh owners upgrade far more often than most computer users for
precisely this reason. We have to own that new flat panel display. We must have the new
color of iBook.
Vindigo is Medusa-like in the way the virus spreads so smoothly. It only takes one look at a
friend’s Palm in order to get hooked (and one file beaming to get it forever). The Nextel
phone has that power, and so (for some people) does Britney Spears.
Alas, it’s not going to happen for you. While you can aspire to make your product more
Medusa-like, it’s a mistake to spend all your time wishing for it to happen. The odds are long
indeed, especially if your product is not groundbreaking. The longer it takes someone to get
Unleashing the Ideavirus 98 http://www.ideavirus.com
the basic concept behind your idea, the less Medusa-like it is. But often, that’s a good thing.
Real change, and the profit that goes with it, often comes from unsettling ideas that
significantly alter the way people interact with each other and with your company. And those
ideas aren’t as smooth as some others.
Unleashing the Ideavirus 99 http://www.ideavirus.com
Persistence
In our quest for the quick hit, the easy way to start a business or just to increase our power as
sneezers, there’s a real desire for a shallow virus. A joke. A gimmick. A neat new technology
geegaw that won’t be around tomorrow.
Laser pointers are a fine example. I was in a meeting last month where the presenter used a
laser pointer to highlight various things on his deathly boring Powerpoint slides.
Unfortunately for me, not only was the presentation boring, but he kept aiming the laser at
the TV monitor, which reflected this highly focused electromagnetic radiation right at my
face, hitting me in the eye a few times. I finally got him to turn the thing off, but not
without considerable struggle.
Other than this unfortunate incident, I can’t remember how many years ago it was that I saw
someone actually using one of these pointers.
What happened was that the pointer came out, and for a few early adopters, it felt
marvelous. It touched a Jungian need in us (especially men, I think) to have a magic stick
that could project our thoughts on the wall. Of course, the best place to use one was in a
meeting of other nerds. And all the other nerds noticed the laser pointer and a virus was
spread.
But after we all went out and bought laser pointers, we discovered that they weren’t
particularly useful. After all, how much information could one really have to present that we
needed a high-tech device to point out the good stuff from the bad?
So the lasers ended up in a drawer.
In other words, the virus wasn’t persistent. Those who resisted the initial temptation to rush
out and buy a laser pointer stopped being exposed to them, and the virus died off.
Unleashing the Ideavirus 100 http://www.ideavirus.com
Compare this to the Palm virus. Every day, somebody else marches into your office,
declaring their undying love and devotion to his new pocket wonder. And unlike laser
pointers, people who love them keep using them. They persist.
In Gladwell’s terms, the Palm has now tipped in certain hives. So many people are using it so
often that you’re constantly reminded that unless you get one, you’re a loser. It’s the
persistence of the Palm more than any other viral factor that has led to its success.
Unleashing the Ideavirus 101 http://www.ideavirus.com
Amplifier
Word of mouth by itself isn’t enough. As discussed earlier, unamplified word of mouth dies
off too soon to be much good to the average business. The goal of a marketer creating an
ideavirus is to create a system that allows the positive word of mouth to be amplified (and
the negative to be damped!).
This simple idea is behind the success of Planetfeedback.com. It’s impossible for me to
understand why any business invited by Planetfeedback to participate would hesitate for even
a moment before signing up.
If a consumer has a complaint or a compliment about a company, she can go to
Planetfeedback and turn it into a letter to the company. Then, with a click, she can have a
copy of the email go to the relevant congressmen, media and regulatory agencies. Another
click can send a copy of the letter to the consumer’s ten closest friends and co-workers.
Instant amplification.
Now, if your company is the target of a complaint, which course of action makes sense? You
could either proactively grab the opportunity to stamp out a negative virus, to turn the
complainer from an angry reporter of bad news into a now-satisfied witness to how much
your company cares, or you could ignore them and hope they’ll go away. Of course, they
won’t go away. They—and the people already infected—will continue to amplify the
message.
Planetfeedback is providing a great service to all parties involved. By taking previously
invisible word of mouth and aggregating it, they’re making it far easier for companies to
understand the viruses that are already being spread, and they’re giving them an opportunity
to do something about them. And yes, they are viruses—ideas that are running amok, being
passed from person to person. At the same time, Planetfeedback gives consumers far more
power, and makes it easier for them to get attention.
Unleashing the Ideavirus 102 http://www.ideavirus.com
Of course, you don’t have to sponsor Planetfeedback. Some day they may offer a different
program… or your competitors can pay to talk to your unhappy customers instead of you.
Unleashing the Ideavirus 103 http://www.ideavirus.com
SECTION 4: Case Studies and Riffs
STEAL THIS IDEA!
Here’s what you can do to spread the word about Unleashing the Ideavirus:
1. Send this file to a friend (it’s sort of big, so ask first).
2. Send them a link to http://www.ideavirus.com so they can download it themselves.
3. Visit http://www.fastcompany.com/ideavirus to read the Fast Company article.
4. Buy a copy of the hardcover book at
http://www.amazon.com/exec/obidos/ASIN/0970309902/permissionmarket.
5. Print out as many copies as you like.
Unleashing the Ideavirus 104 http://www.ideavirus.com
The Vindigo Case Study
One of the best examples of a company unleashing an ideavirus is Vindigo. You can find
them at vindigo.com on the web, and you’ll need a Palm (or something compatible) to use
the software.
Vindigo is a directory of restaurants, entertainment venues and stores in major U.S. cities.
You download it to your Palm and carry it with you. Tell it where you’re standing (in the
illustration above, you’re on the corner of Amsterdam and Broadway in New York City), and
it will show you whatever sort of restaurant or fun you’re looking for. Sorted by distance
from where you are. With ratings. For free.
What a killer app! I need to tell everyone. This is why they invented handheld computers!
IT’S SO COOL!
But, while that alone is grounds for this to become an ideavirus, as described it doesn’t seem
particularly smooth. After all, after a sneezer tells you about this cool software, you’ve got to
remember the name (vindaloo? indigo?), go home, type it into your browser, download it,
synchronize it, etc. A disaster. No way it’s going to work.
Which is where the smooth part comes in. You see, right on the bottom, underneath the
buttons for eating, shopping and entertainment, is a button that says “give.”
Unleashing the Ideavirus 105 http://www.ideavirus.com
So, when a sneezer is going on and on and on about how cool this is, you just take out your
Palm, they take out their Palm, press the give button and sixty seconds later the entire product
is now on your Palm!
That’s smooth. It’s about as close to perfect smoothness as you can get.
It goes beyond smooth. It’s persistent. The next time you synchronize your Palm with your
PC, it will automatically upload all the ratings you’ve put into the computer and get you an
updated version. Instantly. Automatically.
The ideavirus has stuck.
Is it working? Well, the folks at Vindigo seeded just 100 sneezers with the original version of
the program. Then they spent virtually nothing on advertising and waited to see if the virus
would spread. It’s now the fastest-growing application on the Palm.
Note that this isn’t viral marketing in the sense that Hotmail is. You can happily use Vindigo
for months without mentioning its existence to a friend. Vindigo works really well, but it
also happens to be optimized for spreading the ideavirus.
Unleashing the Ideavirus 106 http://www.ideavirus.com
Saving The World With An Ideavirus
The Prius is a new car from Toyota. And it’s the only car that’s ever won an award from the
Sierra Club. This is the car that’s supposed to save us from ourselves, to take a whack out of
the greenhouse effect and to conserve our remaining fossil fuels.
How? By using an engine that’s a hybrid of gasoline and electricity. By getting more than 90
miles to the gallon, giving very good performance and emitting close to zero pollution. I
dearly hope it succeeds. THIS CAR IS IMPORTANT!
Unfortunately, because Toyota is a factory-based company that uses ideas (instead of being
an idea company that owns factories) they’ve built the product completely backwards. I’m
confident that someday everybody is going to be driving a car as positive for the world as the
Prius, but it won’t be because of the way this car is marketed.
Let’s start with the name. How can you tell someone about a car you’re excited about if you
don’t know how to pronounce it? Is it pry-us, or is it pree-us? I don’t want to feel stupid, so I
just won’t say the name.
Second, is there a smooth way for me to spread the word? A visit to the Toyota website
doesn’t even show the Prius on the home page, and when I search for it, I get a very nice
page. But where’s the “tell a friend” button? How can I set up a test drive? Is there a place for
me to give my email address so I can give permission to get information on when the car is
going to be available in my neighborhood? Alas, no on all three counts.
What about a community activism component with teenagers going door to door with
petitions, hoping to lobby the local government to buy Prius police cars? Or letter-writing
campaigns that spring up from grassroots environmental organizations around the
country…?
Unleashing the Ideavirus 107 http://www.ideavirus.com
But the biggest mistake Toyota made was the way they designed the car. Unlike the VW
Beetle and the Mazda Miata, the Prius is not a driving billboard for itself. Here’s what it
looks like:
You could have 1,000 of these cars drive by and you’d never, ever notice it. You wouldn’t
notice the styling, you wouldn’t notice the gas mileage or the lack of emissions—and you
certainly wouldn’t aspire to own one just by looking at it.
Is Toyota on a mission from God? Are they acting like zealots, aggressively pushing a car that
will change the world for the better, the most powerful idea to come out of the car industry
since Henry Ford perfected the assembly line? We need passion from our manufacturers.
What a lost opportunity! An idea merchant in search of a virus would take a very different
tack. Instead of trying to make it cheap and boring, they’d realize that the first people to buy
a car like this are people with money to risk on an unproven technology. Realize that the
opinion leaders and nerds who are most susceptible to this idea are also the most likely to
want to drive an exceptional car.
I’d redesign the thing to be stunning. Different. Unique. Maybe a permanent bumper sticker
announcing my current gas mileage on an LCD readout. Or a fleet of far-out colors. The
first 50,000 people who buy this car will be doing it to make a statement. And every person
who does will be making that statement to the 1,000 or 10,000 people who see them driving
it. A virus waiting to happen.
Remember what I said about the VW Beetle? 180° difference.
Unleashing the Ideavirus 108 http://www.ideavirus.com
Toyota forgot to pick a vector for this car. They don’t know exactly who they want to buy it,
so they designed it for everyone. Precisely the opposite strategy of the new VW Bug. But
remember, an ideavirus adores a vacuum, and there is a very big and very empty vacuum just
sitting here, waiting to be plucked. Toyota could have picked any vector they wanted,
leading to any hive they chose, and yet they chose none.
And finally, I wouldn’t let just anyone buy the first models off the line. I’d select the very
best sneezers, the loudmouths, the pillars in their community and do whatever it took to get
these folks to drive a car. James Bond? Julia Roberts in her next film? The mayor of Carmel,
California or the head of Greenpeace?
This is urgent. This isn’t about making another few million bucks from a website. It’s about
infecting the population with a good virus, and doing it before the vacuum fills up with junk
and it’s too noisy to communicate about it.
Unleashing the Ideavirus 109 http://www.ideavirus.com
Is UNLEASHING THE IDEAVIRUS An Ideavirus?
Here is the step by step plan I’m using to turn this manifesto into an ideavirus:
1.
Describe something important and cool and neat and useful and new, and do it in
compelling, clear and exciting words.
2.
Launch the virus to the largest audience of sneezers I can find. In this case, that means
the readership of Fast Company. Do it with graphic splash and panache and impact.
3.
Make it smooth. Post the entire manifesto at http://www.ideavirus.com. Include commentary
from big-name authors, pundits and industry professionals. Include the entire text of not
just the manifesto but the entire book. Make it easy to send the book to a friend. Include
an audio version of the book. Include my powerpoint slides. All for free.
4.
Run ads to create an environment in which sneezers feel comfortable spreading the
manifesto to others.
5.
Maintain the virus as it grows by doing speaking engagements and distributing free
copies of the hard-copy version of the manifesto to appropriate sneezers.
Unleashing the Ideavirus 110 http://www.ideavirus.com
Moving Private To Public
One of the challenges facing oldline companies as the ideavirus becomes more important is
that they’re used to providing private services. Your friends and acquaintances probably have
no idea what brand of PC you have, whether you have gas or oil heat, how often you see the
chiropractor or what your favorite kind of wine is.
Because of the private nature of these relationships, the only way to expand the market for
them is for the marketer to spend more money and interrupt more people with more junk
ads. BUT, if they can figure out how to make them public, if they can figure out how to
launch an ideavirus, the whole equation changes.
Here’s an example: your frequent flyer miles.
American Airlines has made a fortune using frequent flyer miles to induce loyalty, and just as
important, to establish a currency that they sell to other companies.
But none of your friends really knows your frequent flyer habits. You almost never talk about
them unless something exceptional happens that you want to brag about… like buying
tickets for the whole family to fly to France with your miles.
There are a number of things that American Airlines can do to move miles out of the closet
and turn them into an ideavirus. For instance, they could allow people to buy, sell or trade
their miles. Would this lead to more mileage redemptions (a bad thing)? Sure. But it would
also turn miles back into a nationwide fascination.
Far more clever would be to make the following announcement at a convention jammed
with business travelers: “If you can find someone at this convention who has precisely the
same number of miles as you do, we’ll give you both a million miles.” Suddenly, every
person you meet wants to talk to you about your mileage status.
Unleashing the Ideavirus 111 http://www.ideavirus.com
Hakuhodo, one of the largest ad agencies in Japan, used a similar approach and turned it
into a national craze. It seems that sending New Year’s cards is a big deal in Japan…much
bigger than Christmas cards.
Most people buy their cards at the post office—envelope and stamp included. When you
send a card, it comes with a lottery ticket, good for a small prize if the recipient wins (a
bicycle, a radio, etc.).
Hakuhodo runs their promotion on the Net. And the cards are free to send (no stamps, no
fee). But the best part is that if the person you’re writing to wins, you win the same prize. So,
the more you send, the happier your friends are, and of course, the happier you are.
Not only did this promotion go viral, it turned into an epidemic. In 1998, 25% of the
people with Net access in Japan either sent or received one of Hakuhodo’s cards. And
Hakuhodo cashed out by selling ads in each and every one of those cards.
In order to turn these public ideaviruses into useful, long-term assets, the companies that
create them need to gain permission from people to follow up directly. Then, they go back to
private marketing, at a very low cost, with excellent results, until they’re ready to go public
again with another virus.
Of course, going public doesn’t mean you have to run a selfishly oriented promotion. When
I was in college, the gay and lesbian center ran a campus-wide activity called “Wear jeans on
Wednesday if you’re gay.” Suddenly, something that had been a private topic was now the
topic of discussion among everyone. If you weren’t wearing jeans, was that because you were
afraid that people thought you were gay? Is there something wrong with being seen as gay,
whether you were or not?
One simple act turned the notion of sexual preference into an ideavirus and generated
thousands of hours of intense discussions about how society (and how we) viewed the issue.
Unleashing the Ideavirus 112 http://www.ideavirus.com
YouÕre In The Fashion Business!
Without question, the most difficult part of unleashing a manifesto is creating something
that’s virusworthy. And one of the key components of that art is understanding the fashion
moment.
Why do open-toed shoes come and go? Bell-bottoms? Miniskirts?
How is it that every year, multiple clothing designers launch very similar clothes, without
consulting with each other in advance?
Source: Corbis
Why is it that we rarely see people dressed like the two women above? Did these folks wake
up one morning and go out and buy the entire outfit at once, or did it happen gradually?
Why do some Internet businesses (group scheduling, free email, health portals) seem to
appear simultaneously, even though it took them months or years to launch?
Unleashing the Ideavirus 113 http://www.ideavirus.com
The fashion moment occurs when a respected hive member takes a chance and tries out
something new.
One of two things occurs when a hive member shows up with a new “outfit”:
1.
The hive embraces the new. They start wearing a nose ring or get a tatoo or switch from
using a Filofax to using a Palm. When this occurs, the respected member gets MORE
respect, becomes more influential and reinforces his position as a powerful sneezer.
2.
The hive rejects the new. Many times, the person who introduces the new item will be
ignored or ridiculed (this happens more to the less-respected members of the hive, but it
happens to everyone sooner or later). When this happens, the person who tried to
introduce the new fashion loses respect, becomes less influential and is usually less likely
to try again in the near future.
Obviously, respected members are hesitant to lose their positions of influence, hence the
consistency and uniformity among hives.
Some hives are incredibly conservative (go to the Assocation of American Actuaries annual
meeting and you won’t see an awful lot of surprising new innovation), while others are
known for their daring (the trends demonstrated on the New York City nightclub scene
oscillate like the NASDAQ).
Some people—I call them fashion editors—seem to have an innate sense for knowing when a
hive is ready to adopt a new virus. Successful venture capitalists, journalists, chefs, research
and development labs and record label executives are great fashion editors.
Clive Davis at Arista Records was a stellar fashion editor in the music business for
generations. He launched dozens of breakthrough acts… from Aretha Franklin to Whitney
Houston, Carlos Santana to Patti Smith. The only thing they had in common was that they
were just right for their time. A month earlier or a month later and they might never have
succeeded. (Well, maybe Aretha would have succeeded no matter what…)
But no fashion editor is infallible, and if they’re not careful, they fall into one of two traps:
Unleashing the Ideavirus 114 http://www.ideavirus.com
They lose touch with the hive and fall in love with their own taste. Without the feedback loop
the hive provides, they “lose their touch.” Someone who had a seemingly hot hand starts
failing.
Warren Buffet is a brilliant stock market investor with an extraordinary ability to understand
what other people are going to want to invest in. But when Internet mania started to hit the
stock market, Buffet lost his ability to predict what the hive would predict. I think he DID
know, but overruled his sense of what would happen with his own common sense. Buffet left
billions of dollars of profit on the table because he refused to believe that the Internet stock
ideavirus would spread across the hive of investors.
They stop thinking of themselves as fashion editors and start to believe that they are fashion
makers. Rather than acting like someone who has a sense as to what virus will hit the hive
next, they believe that they are respected enough by the hive to FORCE them to accept the
next virus.
Fashion designers are famous for this, as are rock groups, authors and product marketers.
Take a look at New Coke—the biggest flaw in the introduction of this product was that
Coke believed that if they willed the consumer to adopt a new formula, the consumer would
do as they were told. Instead of spreading like a virus from a respected hive member, they
tried to ram the formula for New Coke on the hive. The hive rejected it.
The challenge your business faces is finding or training a fashion editor. Launching products
too early is just as bad as launching them too late—if you miss the timing, you fail to fill the
vacuum with your virus. Miss the timing and the profit belongs to someone with better
timing and better fashion sense than you.
To those dedicated to the idea that your business is a factory, all this must sound like heresy.
After all, if you wanted to go into the fashion business, you’d have gone into the fashion
business! But, like it or not, we’re all in the fashion business.
Unleashing the Ideavirus 115 http://www.ideavirus.com
A few years ago, there was plenty of cherry wood to go around. People weren’t making much
furniture out of it… it wasn’t in style. Then a furniture designer named Thomas Moser
decided that his fashion sense was telling him that cherry wood would make a comeback.
That once people saw how beautiful the wood was, the idea of furnishing your house in this
warm, comfortable wood would spread through his chosen hive.
Moser built an entire company around cherry wood furniture, and bought thousands of acres
of prime cherry in anticipation of demand. Today, Thomas Moser has grown more than
30% a year for the last ten years, with showrooms in New York and overseas selling $5,000
tables and $3,000 chairs. Not because the furniture is great (which it is) but because he
created a fashion that resonated with his hive, because he launched an ideavirus.
Unleashing the Ideavirus 116 http://www.ideavirus.com
The Money Paradox
The sooner you ask for money, the less you’ll make.
The single biggest mistake idea merchants make is that they ask for money too soon. On one
hand, you want to charge early and often, so you don’t waste time on people who are just
looking, and so you can maximize your income before your idea fades. “Take the money and
run” is a cliché for a reason.
But this strategy introduces friction into the system. Many marketers require people to pay
the most when they know the least. For example, why don’t movie studios run a day of free
sneak previews to get the virus started, and then charge more once everyone wants to see the
movie? Today, if you want to taste a new movie, you’ve got to pay $8 for the privilege.
On the Internet, dozens of new businesses have discovered how important this model is. A
company called eFax offers a service that lets you get faxes delivered to your email box. They
launched it as a totally free service. Why? Because it’s scary enough to be one of the first
people to try something as flaky as eliminating your fax machine. And it’s even scarier to pay
money for the privilege as well…
So eFax has a plan: get people hooked on a free system. Build an ideavirus. Then upgrade
people to a paid system that offers all sorts of extras.
1. Fill the vacuum
2. Achieve lock-in
3. Extract revenue
They can fill the vacuum by getting in first and furious and spreading the virus. They can
achieve lock-in by making it hard for people to switch to a competitor (what a hassle to keep
changing your fax number!). And finally, they can extract revenue by offering value-added
services or selling advertising.
In that order!
Unleashing the Ideavirus 117 http://www.ideavirus.com
Will eFax be guaranteed an easy upgrade path to paying customers? I have no idea. Some
businesses (like email) will be stuck at FREE forever, thus making the whole journey hard to
justify. In this case, they could offer free faxes with an eight-hour delay before you get them,
but for $5 a month, you get the faxes instantly. So it’s free for me to try out, free to spread,
but profitable after lock-in is achieved.
The challenge, of course, is to figure out which businesses have a payoff at the end. The
challenge is also to be patient enough to wait, to introduce the friction of charging at just the
right moment.
Watts Wacker catapulted his career by writing The 500 Year Delta. After the book came out,
people started to hand it around, to embrace his ideas. This led to larger audiences and a
dramatic increase in bookings for speaking engagements. In a few months, I’m confident he
made more in speaking fees than he had from royalties on the book. By letting the ideavirus
grow before trying to extract much profit, he was able to make more money in the end.
In very transparent markets like the Internet, the fear is that all ideaviruses will be so
competitive that you’ll never be able to extract money. That’s why the race to fill the vacuum
is so intense. If you can fill the vacuum aggressively and permanently, it is far easier to extract
money.
Unleashing the Ideavirus 118 http://www.ideavirus.com
Think Like A Music Executive (Sometimes)
There are plenty of lessons you can learn about viruses from folks in the music industry
(current behavior notwithstanding, but more on that later).
First, industry executives realize that nobody buys a CD because they like the quality of the
polycarbonate disc. If you don’t like the idea of the music, you’re not going to buy it.
Second, they realize that making money later is way more important than making money
now. They learned this the hard way. Consider radio for a second. Before radio, music sales
were tiny. Why would you buy a song for your Victrola if you’d never heard it before? How
could you know if it was any good?
At first, radio might seem like a threat to the recorded music industry. After all, they play the
ENTIRE song, not just a few notes. And if it’s a hit song, you can hear it night and day on
the radio every few minutes if you’re so inclined.
For a while, the music business fought the idea of radio stations playing songs for little or no
compensation. Then, in the 1950s, they realized how valuable airplay was—so valuable that
a congressional inquiry discovered that music labels were bribing disk jockeys to play their
records.
Fast forward a few decades to MTV. Once again, the music labels balked at supporting
MTV’s insistence that they provide expensively produced music videos—for free! It took a
year or two for them to discover that MTV made hits—that giving away the music for free
turned out to be the best way to sell the music.
Music execs know that you’ll pay nothing to hear a song on the radio, but if you like it,
you’ll gladly pay $15 for the CD. And that if you love the CD, you’re more likely to pay $40
for tickets to the local concert, where you might be converted to a raving sneezer, much more
likely to infect your friends and neighbors with raves about the band, the song, even the
souvenirs!
Unleashing the Ideavirus 119 http://www.ideavirus.com
For some reason, history is repeating itself. Rather than embracing Napster, the software that
lets millions of people listen to each other’s CD collections, music moguls, fronted by the
hard rock band Metallica, are once again complaining about the free distribution model.
Even if the record companies are able to beat Napster in court (a likely outcome) it won’t
matter. There are already dozens of technologies (like gnutella) waiting to take its place, and
each will be harder to stamp out than the one before.
Patience! Instead of hassling Napster, they ought to figure out how to license Napster and
the others, probably in exchange for intensive promotion of their hottest acts. Why not let
me subscribe to my favorite bands, paying for live performances or attending private concerts
or buying T-shirts. I’m certain that if the Grateful Dead were still around, their primary
income source would be souvenirs, followed closely by live concerts. Is that what the record
companies want? Doesn’t matter. It’s what the network is going to deliver, regardless of how
they feel.
Is the CD going to disappear? Absolutely, regardless of what happens to Napster. What will
determine the future of the record business is whether music execs are able to redefine their
jobs around what happens after they ignite a virus over Napster or its successor.
Unleashing the Ideavirus 120 http://www.ideavirus.com
Is That Your Final Answer?
When a sneezer is ready to spread your ideavirus, what should he say?
It sounds like a simple, almost silly question, but it goes to the core of how smooth you can
make your virus. If you give sneezers easy-to-follow, effective instructions, they’re likely to
follow them, because, after all, their goal is to spread the virus.
On “Who Wants to Be a Millionaire?” the producers insist that Regis Philbin repeat the
catchphrase, “Is that your final answer?” almost to distraction. But now it’s become a
powerful, smooth tool for sneezers who want to spread the virus. I must have heard the
phrase fifty times and read it in dozens of newspaper columns before I saw the show for the
first time.
By giving loyal watchers a five-word catchphrase, the producers created (intentionally or not)
a powerful shorthand for referencing the show. Hotmail did the same thing with the sig file
in the free email each person sent. Right there at the bottom of each email, with no
additional work on the part of the sneezer, were specific instructions on how to get Hotmail.
Buffalo Springfield and the Beatles did the same thing with some of their songs. It took just a
few notes—an investment by the listener of seconds, not minutes—for them to expose their
“idea” to a new listener. By working so hard on the first chords of the song, pop music
producers (and Beethoven for that matter) made their products far smoother. It’s easier to
share the song when you can hum the riff.
For most ideas, the web can be a powerful tool to help with this. What might a website for
sneezers look like?
The first touch, the first impression and first visit, must go beautifully. It’s got to be fast.
It should contain exactly what you’ve tested and discovered that most effectively captures the
attention of the first time-visitor. You’re in control in this moment, and you can make it
work or not.
Unleashing the Ideavirus 121 http://www.ideavirus.com
The site should also be filled with tools that make it really easy for a visitor to become a
sneezer. Get out of the way. Give the sneezer something to share. Do like Tom Peters (at
http://www.tompeters.com) and include all your Powerpoint slides. Don’t require registration or
permission at this stage. Let them in, sell them on the idea, then give them the (free) tools to
share.
Unleashing the Ideavirus 122 http://www.ideavirus.com
A Dozen ideaviruses Worth Thinking About
Company Big idea How you spread the virus (the
medium)
Polaroid Instant photography “HEY! Look at this,” you say at
the party.
Tupperware The best food storage devices Get your friends to sell their
friends—multi-level marketing
Fax machine Documents delivered by phone The more you sell to your
business associates, the better
your machine works.
Home Shopping Network Shopping via cable TV “Hey Madge! Look what’s on
Home Shopping,” you say to
your friends on the phone.
Fast Company Journal of the new economy Company of Friends—monthly
meetings of local fans of the
magazine.
CarmineÕs Restaurant Tons of food, tons of garlic Six-person minimum for
reservations—you need to sell
your friends to get in.
Beany Babies Collectible teddy bears If other people start collecting,
your collection increases in
value.
Gamesville Super sticky games on the web Word of mouse—email your
friends and invite them over.
Hotmail Free email Totally viral…every mail you
send promotes it.
Tommy Hilfiger Urban preppy chic Logo virus—the more you wear
the logo, the more people see it.
ÒThe Cathedral and the
BazaarÓ
Open source programming
works
Enabling powerful web sneezers
to spread the word by giving
them a powerful manifesto they
can share.
Vindigo Zagats on my Palm “Give it to me,” and a friend
can beam it over in seconds.
Unleashing the Ideavirus 123 http://www.ideavirus.com
Why I Love Bestseller Lists
One of the critical moments in the spread of an ideavirus is the question the consumer asks
before diving in: “Is it worth my time/money?”
Of course, your recommendation is important to me. Of course, I want to look as good as
you, be as smart as you, have as much fun as you. But I also care desperately about everyone
else’s opinion. After all, none of us is as smart as all of us!
The most common way this popularity is reinforced is that the user will hear about a new
ideavirus from more than one person. Usually, we hear about something first from a
promiscuous sneezer, someone who has some sort of benefit from making the
recommendation, or at the least, someone who’s always recommending stuff. We all know
somebody who eats out every night or listens to every CD or is into whatever bizarre
conspiracy theory has gripped insomniacs this week.
But then, sometimes we hear about the same ideavirus from someone else. And then another
person. Finally, we realize that something is really going on, and we investigate.
In the real world, these reinforcements are usually caused by sightings or physical
interactions. Riding through the New York subway last year, I encountered a kid wearing
what appeared to be a black stocking on his head. But along the hem were the words,
“Tommy Hilfilger.” It seemed like an odd affectation and I let it go.
A week later, I saw four more Hilfiger skull caps. In the week after that, a dozen. If I were in
search of genuine urban chic, I certainly would have bought one at that point, if only to
protect my trademark bald pate from the winter chill.
The same thing happened with the VW Beetle. First there was one in my neighborhood (a
yellow one) and then a few, and then a dozen. With all these reinforcements, I assumed that
it was now a safe thing to consider, and went to the dealer to have a look for myself.
Unleashing the Ideavirus 124 http://www.ideavirus.com
Online, the rules are very different. There is no physical world to bump into. Instead (and
even better for the statistician in each of us), there are actual digital counters and accurate, up
to the minute bestseller lists. No guessing. No inferences. The real scoop.
Amazon.com has a bestseller list more than a million titles long. Visit any title and you can
see where it stands compared to every single other title in the world. Wow. Now we instantly
understand what’s hot and what’s not.
MP3.com has done the same thing with music. As a track gets played more and more often,
it moves up their digital bestseller list. And yes, Zipf’s law works here too—the topmost
tunes are downloaded far often more than those just below them.
We use the same math when we look at the MediaMetrix list of the most visited websites, or
Variety’s tally of the weekly box office numbers (some people saw “Titanic” just because it
seemed that everyone else was). Various organizations also track bestselling cars, bestselling
vodka and highest-paid executives.
One of the best ways to facilitate adoption of your ideavirus is to find a bestseller list that
makes sense and then dominate it. If that’s impossible, figure out how to create your own
bestseller list and popularize that!
This isn’t just conjecture. A breakthrough paper by Stanford Business School professor Kirk
Hanson demonstrated this in a really profound way. His team artificially boosted the
bestseller status of files for download on the web (they downloaded one file over and over
again, increasing the counter of how often it had been downloaded). The result? Heavily
downloaded files get downloaded more often! Nothing was changed but the counter, but
users were more interested in seeing the most popular files. Simple, but true.
Want to launch a new drink using your company’s chi-chi liquer? Why not identify the right
bar, frequented by powerful sneezers in the hive you’re targeting. Then pay the bar to post a
“bestselling drinks list.” Now, bribe enough folks to go in and buy themselves a drink. Soon,
you’ll see your drink climbing the bestselling drinks list, and this alone ought to be enough
to get other—less easily bribed drinkers—to give it a try.
Unleashing the Ideavirus 125 http://www.ideavirus.com
Of course, sampling doesn’t always lead to the spreading of a virus, but without sampling,
you’ve got no chance, do you?
Unleashing the Ideavirus 126 http://www.ideavirus.com
How A Parody Of Star Wars Outsold Star Wars
According to USA Today, a parody called George Lucas In Love is currently outselling the
new Star Wars movie on video on Amazon. How is this possible? How can mighty
Twentieth Century Fox be beat by a nine-minute, $8 handmade film?
Because the parody is an ideavirus. And because the medium of the Net is the perfect place
for the word to spread.
In the old days, if you made a movie, you needed movie theaters across the country to show
it. That’s way outside the reach of an entrepreneur, regardless of how clever his movie is.
Videotape leveled the playing field a bit (Blockbuster can carry hundreds or thousands of
titles) but it’s still very difficult, time-consuming and expensive to force your way into
nationwide distribution.
But Amazon is a different story. Amazon prides itself on carrying just about everything. Since
they don’t have to carry much inventory, Amazon doesn’t take much of a risk by listing a
title. And the entrepreneur can certainly find his tape listed along with the thousands of
others available.
Unleashing the Ideavirus 127 http://www.ideavirus.com
So distribution is the easy part. But how to spread the idea?
Well, the parody fills a vacuum. In this case, the vacuum was “funny and interesting news
about Star Wars.” Certainly, the launch of the videotape was a yawner, the mania about the
film version having largely subsided. Would many people buy the video for their libraries?
No doubt. But it wasn’t news.
But now, here’s an email telling me that someone has seen the funniest little video. It’s
hysterical, my friend says. So I click on over to Amazon (using his affiliate link, I notice—he
may be a powerful sneezer, but he’s also making a profit on this virus). There, I note more
than 100 reviews, all of them positive. I see that it’s a bestseller. I realize that there’s almost
no risk here, certainly worth ten bucks and a few minutes of my time. I buy it.
And after I see it, I’ll tell five friends. This time using my affiliate relationship.
A classic ideavirus. Yes, it would have grown faster if the filmmaker had just put the video
online for free, but he was stuck in the mindset of making money now. Yes, the charge and
the wait for shipping definitely slowed the virus down, but at the same time, it was a nice
balancing act—a slightly slower virus in exchange for tens of thousands of dollars (and
probably a contract for a real movie from a studio).
If it were me, I probably would have posted a low-resolution excerpt of some of the funny
parts online… it’s going to happen anyway, so the filmmaker might as well do it and thus
control what the sneezers say while also increasing the velocity of the virus.
Unleashing the Ideavirus 128 http://www.ideavirus.com
Wassup?
I first heard about the Superfriends parody in an email. Apparently, some clever animator
had taken the soundtrack of the ubiquitous Budweiser commercial and replaced the video
portion with Batman, Superman and Aquaman hamming it up and having a few brews.
Clicking on a link (pretty smooth transition from interest to exposure, you’ll notice), I see
that it’s on a reputable site and happens to be one of the most downloaded files (a bestseller
list!).
Soon, I’m laughing out loud. It really is funny. Of course, I’ve got to tell three friends, so I
do. It’s going viral.
A few weeks later, a site launches another Wassup parody. This one uses the AP photo of
Elian Gonzales as the star. But this time, the virus grows far faster, with more than 100,000
people seeing it in less than 24 hours.
Why did it grow so fast? Because everyone who had seen Superfriends and liked it didn’t
need much coaxing to get infected by this one. By tapping into a virus-friendly base, it took
much less effort for the marketer to get the message to spread.
(Of course, this is a paradox, because the ideavirus loves a vacuum. In this case there wasn’t
a vacuum—the Wassup parody was an old joke. So, in order to make an impact, it had to be
fresh and at least as funny. But once it cleared that hurdle, the rest was taken for granted.)
This time, though, the ending of the cycle was very different. The Associated Press fired off a
letter to the site behind the virus, claiming copyright infringement and not interested at all in
the idea of parody and its protection. So the short movie came down.
Inevitably, if you create a piece of digital media that becomes popular, someone is going to
parody it, or at the very least, use it in a way that you’re not delighted with. If your digital
media becomes that popular, odds are you should embrace it, not fight it. Budweiser, for
Unleashing the Ideavirus 129 http://www.ideavirus.com
example, has wisely let the parody virus spread unfettered. Being parodied online is a
shortcut to burning the Budweiser brand further into our subconscious.
Unleashing the Ideavirus 130 http://www.ideavirus.com
Judging a book by its cover
No question, a great cover can make or break your book. Kurt Andersen wrote one of the
funniest books I’ve ever read (Turn of the Century) but, by all accounts, it didn’t meet sales
expectations. Why? One reason is the cover, which is one of the worst I’ve ever seen in my
life.
Remember, the search for Medusa is usually a hopeless quest. But just as it’s difficult to sell
someone on your ideavirus with just an image, it’s also nearly impossible to suck them
further in if the image is offputting, inconsistent or boring.
Boring is probably the worst offense. Whether your product is a book, a trading card, a car
or even the tag on a bag of tea, boring is the obvious, but wrong, solution.
You’ve worked very hard on the stuff “inside.” You’ve refined, tested, edited and slaved to
make sure that the idea is powerful indeed. And then it comes time to make the
package—the cover. The prevailing wisdom is to create a cover that’s attractive but not
offensive. Something that will attract attention from everyone and offend no one.
This is nonsense, of course. It can’t possibly attract everyone and offend no one. The very
best cover images are like a cold glass of water thrown in your face. They break one or more
rules of graphic design or industry rules of thumb. They play off existing images but change
them in a vital and important way. They’re loud. They attract the eye, but they also hold it.
And most of all, they intrigue us enough that we need to understand what’s inside: we set
ourselves up to be exposed to the virus.
When Yahoo! first launched, the company name and logo broke every rule in the book. But
co-founder Jerry Yang will be the first to tell you that in a world populated with Lycos,
AltaVista, InfoSeek and Architext/Excite, Yahoo! was the easy winner. Easy to spell. Easy to
type. Easy to tell other people about.
And it had personality. It meant something.
Unleashing the Ideavirus 131 http://www.ideavirus.com
Was it risky? I don’t think so. A boring, hard to spell, meaningless name like Lycos was risky.
Unleashing the Ideavirus 132 http://www.ideavirus.com
Being The Most
Turns out there’s been a battle going on for a few years—the battle to make the hottest hot
sauce in the world.
At the beginning, you made a hot sauce by using peppers. Hotter peppers made hotter sauce.
And a sauce made from Scotch Bonnet Peppers (the hottest peppers on Earth) was the
hottest sauce on Earth.
Then, some nutty scientist figured out how to extract just the essence of hotness from Scotch
Bonnet Pepper puree. By using gas chromotagraphy or some other evil technology, he was
able to create a sauce more than 1,000,000 times spicier than your basic pepper.
Why does this matter? Because being the hottest hot sauce ever made is like being the Mona
Lisa. Because if I’ve managed to eat chili with the hottest hot sauce ever made in it, I’m
going to tell my friends. I’m going to spread your hot-sauce virus. If it’s the second or third
hottest, who cares?
There’s always room in any list for the world record holder. The greatest basketball player
who ever lived, or the nastiest restaurant owner, or the fastest computer. It’s noteworthy. It’s
news. It’s worth sharing.
My dad’s hospital crib company dominates the market, making most of the cribs that are
used in hospitals around the world. Their standard models cost $700 to $2,000 each, and
they last forever. How to grow the business? How to get more attention and more sales?
His engineers found a leading hospital, and together they designed the best (and the most
expensive) hospital crib in the world. With all the options, it costs about $7,000. Yet it’s
selling like crazy, from the Philippines to Tuscon. Why? Because it’s worth talking about.
Because it embodies an idea, and it’s an idea worth sharing.
Google.com has plenty of traffic, yet they’ve never spent a nickel on advertising. How?
Because it’s the fastest and most complete search engine ever built. Electronically amplified
Unleashing the Ideavirus 133 http://www.ideavirus.com
voices—from nerds to magazines—are happy to trumpet the idea that there is a faster, better
way to search than using the tried and true favorites.
As you think about a corporate virus or a personal one, consider: What you are the best or
the most at? How can you refine and amplify those traits to create a Wow! product…a
world’s record holder that is worth mentioning?
And by the way, if you’re not facing a vacuum (and most of us aren’t lucky enough to be in
that position) you’ve got to be ten times better than what’s already there, if you’re going to
start your own virus.
Unleashing the Ideavirus 134 http://www.ideavirus.com
In Defense Of World Domination
Targeting isn’t enough. Being a world record holder isn’t enough either. You also need to
dominate your hive.
Having 5,000 loyal, rabid fans of your ideavirus is great. Unless, of course, your audience is
the population of Massachusetts. To dominate Massachusetts you need a lot more fans than
that. Without the power of reinforcement, your virus will peter out. Unless individuals are
hearing from sneezers again and again, your virus will slow and will probably die out over
time.
Imagine, instead, that you have 5,000 fans at Stanford University, which is a hive with a
population of about 15,000. The chances that you’ll be exposed to every other member of
the hive is huge. Why? Because if each one of the 5,000 fans tells just a few other people,
you’re already hitting each person more than once. And if the idea is virusworthy, that’s
probably enough to dominate the entire campus. Even the laggards will surrender when they
see everyone else is doing it (even the accounting department at my old company did the
Macarana at the company Christmas party).
Malcolm Gladwell calls this the tipping pointD—the idea that creating and propagating an
ideavirus is not enough. The biggest win comes the last time your virus doubles in size. The
biggest win comes when you’ve so dominated the hive that the last folks (who are often the
most profitable folks) can’t help but come along. They tip because they hear from so many
respected sneezers that they feel they have no choice but to get on the bandwagon.
This happened with AOL. A few years ago, AOL was paying $300 in marketing costs to get
one new member. All those CDs that showed up in every magazine were expensive, but they
were effective.
But how could AOL justify spending $300 to get a member who had a lifetime value of just
$124? Jan Brandt, the genius behind the campaign, realized that if she could win at this
expensive part of the curve, the game would soon turn in her favor. She knew that once she
Unleashing the Ideavirus 135 http://www.ideavirus.com
got over the hump and dominated the hive of people about to go online, the next generation
of users would come along far cheaper.
She was right. Once AOL established dominance for new users, they established a network of
powerful sneezers. Powerful, because these were folks who until quite recently had been new
users. These once-new, once-lost users had the credibility to spread the word to those just
behind them on the learning curve. They were powerful because they’d been there, and their
personal experience counted for more than any salesperson’s could.
The virus had authority, because every “bestseller” list credited AOL with being far and away
the most popular Internet service provider in the land. Today, someone at Sun City who
until recently had no idea what they were talking about when they said “Internet” could
proudly recommend AOL to the person in the next condo. AOL now spends about $100 in
marketing to get a new member—because their virus tipped.
There’s plenty of interesting action that occurs before the tipping point, though. Viruses
need to spread before they tip, and a smart marketer can be quite happy indeed along the
way.
Dominating the hive is essential in starting the virus in the first place. And most marketers
make the mistake of picking too big a hive to focus on in the first place.
If you go to the Consumer Electronics Show in Las Vegas, you’ll see one of the largest trade
shows in the world, and you’ll also see hundreds of companies spending millions of dollars
trying to dominate the show. All of them fail. Which is why it’s so rare for a virus to be
launched at the CES. It’s just too noisy, and there are no exciting but safe recommendations
for the most powerful sneezers to make.
The smart marketers take a different path. They launch at Demo or Spotlight or Esther
Dyson’s conference—a much smaller venue, but a higher concentration of powerful sneezers.
Here, for about the same money as making a whisper at CES, you can completely dominate
the discussion.
Unleashing the Ideavirus 136 http://www.ideavirus.com
If YouÕre A Member Of The Academy, You Go To Movies For Free
If there’s an association of powerful sneezers, it’s the Academy of Motion Picture Arts and
Sciences. This association of actors, screenwriters and directors has celebrated movies every
year for nearly a century, and every year it seems to get more popular and more influential.
If your movie wins an Oscar, you can count on a blip at the box office, and even better, a
long, profitable life on video. And of course, any actor who wins one has a label that will
enhance his career forever.
So, how much do the studios charge Academy members to go to a movie? That’s right,
nothing. Not only that, but the studios are delighted to deliver the latest movies to an
Academy member’s home, on her choice of VHS or DVD.
Why? Why give the movie away? Well, here it should be pretty obvious. The leverage that
comes from building buzz among Academy members more than pays for the cost of sharing
the movie with them. In fact, the benefits are so obvious that studios like Miramax have been
accused of trying to buy the Oscars by throwing hundreds of thousands of dollars of trade
advertising at Academy members.
Well, if this is so obvious, why bring it up? Because your idea, regardless of marketplace, has
a similar group. Maybe it’s not as easy to find or as easy to reach, but there are powerful
sneezers in the audience for almost every idea. It’s the money paradox, but on a much smaller
scale. Finding these sneezers and giving them a sample of your idea for free is a no-brainer.
Even better, figure out what it costs to deliver it with impact.
I met with a marketing executive from Hong Kong last week. He’s building a company that
is targeting the health care and financial services industries. He’s got a big idea, and if he can
persuade some of the key sneezers in the industry, then most of the other companies are sure
to follow.
Unleashing the Ideavirus 137 http://www.ideavirus.com
The good news is that he was invited to speak at a gathering of 100 top chief information
officers from the financial services industry he’s targeting. The bad news is that he was
planning just to give a speech.
What an opportunity! What a chance to talk to all the key sneezers at once and dominate the
hive. We did the math, and it’s clear that even if he needs to buy each one of the attendees a
BMW to get their attention, it’s worth it.
When you have an opportunity to dominate not just a hive, but the sneezers in the hive, you
need to spare no expense to do so. Don’t just give a speech about how your product works
well. Fly in three satisfied customers to tell their stories in person. Don’t just give a speech
and ask for questions. Sponsor a cocktail party afterward so you can meet individuals and
answer their questions. Don’t just give a speech about how your product is safe and secure.
Give each attendee a first aid kit for their car. By focusing on this key moment, by overinvesting,
you can lay the foundation for a virus to come later.
Unleashing the Ideavirus 138 http://www.ideavirus.com
How An Ideavirus Can Drive The Stock Market
When you think about it, the stock market is nothing but thousands of ideaviruses. (That’s
right, thousands. An ideavirus doesn’t have to dominate our entire culture to be an
ideavirus… some last for just a few days in a very isolated hive, then disappear.) When you
buy a share of stock, you don’t really get anything—just the right to sell that stock to
someone else tomorrow. So… if a positive virus catches on and the demand for the stock
skyrockets, you win.
The market’s respect for ideavirus thinking starts before the company even goes public.
Choosing an investment bank for your IPO is a first step. Firms like Goldman Sachs and
Alex.Brown are powerful sneezers (even though they can easily be bought off with millions of
dollars in investment banking fees by eager companies looking to go public). If one of these
firms aggressively recommends the stock to institutions, the virus starts off on the right foot.
The alternative—marketing the stock through a smaller, less respected (and perhaps cheaper)
investment bank—is almost certain to lead to a lower return.
The next step is pricing the IPO. The current rage is to underprice the stock being offered to
the public, because that will lead to a huge first day appreciation in the stock. It’s not
unusual for an IPO (like Globe.com, Martha Stewart Omnimedia or Street.com) to
dramatically increase in price on the first day of trading.
Why do this? Why leave all those proceeds on the table so that the folks lucky enough to buy
into your IPO make the money instead of your company? The answer is simple, and it has
two parts:
First, by rewarding the powerful sneezers who are lucky enough to buy into your IPO, you
maximize the chance that they’ll participate and will tell their less powerful (but more
numerous friends) about this exciting new investment.
Second, the rapid rise in the first day of trading allows other powerful sneezers (the news
media and brokers you don’t have direct contact with) to talk with excitement and
amazement to the next group of potential investors. In other words, this is cheap marketing.
Unleashing the Ideavirus 139 http://www.ideavirus.com
It’s a way of communicating news (this is a hot stock) to large numbers of people in a
powerful way.
After the stock is public, the company has its work cut out for it. There’s a multi-layered
community of intermediaries between the stock and the people who want to buy it, and the
company must work the hive to find the most powerful sneezers able to spread the word
about the stock.
The first stop is the market analysts who cover the stock. Once again, the marketplace sees
this group as being powerful sneezers (when one analyst recommended Amazon.com, the
price of the stock doubled in just a few days). By courting the analyst community, a
company can find a way to communicate the story they’ve created around the stock.
Don’t underestimate the power of the story. There are almost no other cues available to
persuade someone to spread the word about a stock. You can’t see it or touch it or smell
it—it’s just an intangible right to make money in the future. As a result, the story must be
able to describe the reason why the stock is selling for x today but will be selling for 3x
tomorrow.
Brokers are a fascinating component in the spreading of an ideavirus around a stock.
Remember, they’re not paid unless people trade. Buy and hold is the enemy of most
stockbroker compensation schemes, since they only charge for trades and are paid by
commission. Yet, for many decades, brokers were seen as powerful sneezers, especially if they
helped make you money in the past. In fact, they’ve always been promiscuous sneezers,
motivated (whether in the short term or the long term) by their ultimate financial gain. A
“good” broker is one who realizes that if he postpones financial gain in exchange for helping
his clients make money in the long run he’ll get more and more clients.
All this is changing as the world shifts to trading online, and more important, getting stock
news online. Suddenly, anyone can talk about stocks, anyone can post to a bulletin board,
and anyone can spread a rumor.
Unleashing the Ideavirus 140 http://www.ideavirus.com
As a result, stock ideaviruses spread much more often and much faster. In one case, the
public markets knew about a CEO’s plan to quit before his board of directors did. Because
the individuals who post these notes are anonymous and possess unknown motivations, the
chances that they’ll develop into powerful sneezers is slight. But the sheer number of posts
(more than 100,000 a day on Yahoo!’s bulletin boards alone) means that they have influence.
An astute CFO or CEO can look at the key factors in the creation and spread of a stock
ideavirus and launch a campaign to move the virus with a velocity and vector they’re
comfortable with, and more important, aim it at the appropriate hive.
Note, for example, that some stocks, like Iomega, are the darlings of online stock bulletin
boards. As a direct result, those stocks are far more volatile than the average. Live by the
sword…
Yahoo! has worked hard for years to manage the story about its stock. Gary Valenzuela, the
legendary former CFO at Yahoo!, was obsessed with three things:
1. Become a blue-chip stock, one that institutions would happily own.
2. Become profitable, to distinguish the Yahoo! story from its competitors.
3. Underpromise and overdeliver, always beating the “whisper numbers” that analyst
established for the company’s quarterly earnings.
As a result, Yahoo! stock has consistently and regularly outperformed its competitors. And
due to the success in labeling Yahoo! an Internet blue chip, the stock is much less susceptible
to swings due to rumors.
Was that expensive in the short run? No doubt. When the market was looking for good news
and hype, Yahoo! often refused to deliver. Short term gains were forsaken for building a
story, a story that could become an ideavirus to be delivered by analysts and other powerful
sneezers.
One way to predict the future of a stock, then, is to see beyond the story and understand
whether the company is actively managing the ideavirus, and doing it in a way that will move
it to the right hive.
Unleashing the Ideavirus 141 http://www.ideavirus.com
Bumper Sticker Marketing
Years ago, I was a walking parody of a high-tech yuppie.
I worked as a poorly compensated marketer at a start-up software company in Cambridge,
Massachusetts. I drove a dented old Saab. I used a Macintosh. And on the back of my Saab I
proudly affixed a bumper sticker that read, “I’d rather be driving a Macintosh.”
This is an ancient form of ideavirus marketing, of course. I used my car as an amplifier,
exposing my message to hundreds or thousands of people. But even better, given the
neighborhood I was driving in, I was focusing the message on an appropriate hive, and given
the car I was driving, adding power to my sneezing.
Think about it. If the bumper sticker had been on the back of a junker Chevy, rusting
outside an abandoned farm in Oklahoma, you would have had a very different response to
the message, no?
The neatest thing about this technique is the way Apple converted the private (what sort of
computer do I use) to the public (my proclamation of how happy I was to be a Mac user).
There are countless opportunities for marketers to do precisely the same thing today. And
not just on your bumper. Some marketers ride along with their product—the Ralph Lauren
pony, for example, is advertising on the front of your shirt all day long. Others manage to
make it a more political choice—Marlboro, for example, was one of the ten largest marketers
of imprinted clothing a few years ago.
Picking the medium for your “bumper sticker” is important, but it’s just as important to
determine why someone is going to be willing to stick his neck out to promote your product.
Personal pride is an excellent tactic! If people are willing to sneeze on your behalf because
they’re proud of you, your product and their association with it, you’re in. Now all you’ve
got to do is give them a smooth way to spread the word.
Unleashing the Ideavirus 142 http://www.ideavirus.com
No, You Go First!
The challenge of the new idea is that very few people want to go first. Who was the first to
swim in the Charles River in Cambridge, Massachusetts after years of it being off limits for
health reasons? Who was the first to give their kid the chicken pox vaccine? Which company
chose to be the first to file its taxes electronically?
One of the key reasons to launch an ideavirus is that you can give people a risk-free, cost-free
way to check out the safety of your idea before they commit. And more important, you can
create an aura around your idea—an aura of inevitability, of invincibility. When everyone is
buzzing about a new technique, tactic, service, musical style, club, food—whatever—it’s far
easier to put fear aside and try it.
But just as people are hesitant to be the first to buy a fancy new product, many are hesitant
to try a fancy new idea. There are plenty of people who want nothing to do with a new song
or a new book… they’re happy to wait until it’s been screened, filtered and accepted by the
mainstream.
So, depending on the hive you choose, you need to make it clear to that consumer that your
idea has arrived. That the water’s warm, the air is safe to breathe and your idea is a
comfortable, tried and true one.
One way to do this is with bestseller lists. And with testimonials. And by exposing the digital
word of mouth record to let them see the countless people who have tried it and liked it. Do
it with the specific objective of reminding people that others have taken the risk and happily
survived. If you work at this and do it on purpose, you’ll be amazed at how much water you
can drain from the river—how easy it is to bring the rocks to the surface, how powerful you
can make the message when you expose the connections that led you from person A to
person B. It’s in this sort of active ideavirus marketing that many brands are able to run rings
around the competition.
Even before you do this, offering your idea in trial-sized, bite-sized portions is critical. Many
companies have created neat, effective online products, only to see them fail because they
Unleashing the Ideavirus 143 http://www.ideavirus.com
required consumers to go through a time-consuming download before they could use
them… and if they couldn’t use it, they couldn’t understand why they wanted it! Catch-22:
a product you don’t know if you want to download until you download it.
Give them a version instead that doesn’t require a download and doesn’t work as well—but
still makes their life better. Why? Because now that I’ve sampled it without risking a virus or
taking a lot of time or trying to understand the arcane intricacies of downloading in
Windows, now I’m willing to invest the time to do it.
Unleashing the Ideavirus 144 http://www.ideavirus.com
Digital Media Wants to Be Free
When was the last time you bought some table salt?
Odds are, you didn’t pay very much. Salt is cheap. Why? Because once you own a salt mine
and pay for a salt factory, the cost of making a pound of salt is low indeed. But because
there’s more than one salt mine out there, the competition for getting salt sales is pretty
intense. And given that all salt is pretty much the same, why pay more?
Pricing battles are certainly not unusual in physical goods. In fact, almost every competitive
category of item that’s entirely physical (without an idea attached) uses cost-based pricing. In
other words, it’s a commodity. When those rules are abandoned (as they were with crude oil
during the Arab oil embargo) consumers are shocked and angry.
For a number of reasons, this pricing approach hasn’t really kicked in with intellectual
property. It only costs McKinsey a few hundred bucks to write a report for Chrysler, but
they happily charge a few million dollars for it. One more copy of a Bob Dylan CD only
costs 80 cents to make (less than a vinyl record!) but it sells for twenty times that.
Why?
The biggest reason is that intellectual property is rarely a commodity. There are many kinds
of salt, but there’s only one Bob Dylan. And when you want to listen to Dylan, it’s not clear
that 10,000 Maniacs is an acceptable substitute.
Because intellectual property is unique, it has long resisted a trend toward commodity
pricing at the margin. In fact, the price of most forms of intellectual property has increased.
Barring one big exception:
Stuff that went from being expensive to being free.
The most popular web server software (the programs they use to run most giant websites) is
not sold by Microsoft. And it doesn’t cost $10,000. It’s free.
Unleashing the Ideavirus 145 http://www.ideavirus.com
The most popular web browsers are free.
The cost of listening to a Beethoven concerto went from $30 (at some fancy theater in
London) to $0 after radio was invented.
The cost of watching a movie on network television is zero.
The mathematics of the ideavirus make it too compelling for the creators of viruses to stay
greedy.
The more people know your virus, the more it is worth!
Thus, if charging people for exposure to your virus is going to slow down its spread, give it
away.
Apple just cut the price of WebObjects software from $50,000 a copy to $699. That’s a
98.7% decrease in the price.
Why? Because Apple realized that unless a lot of people use their software, no one will use it.
Take a look at http://www.mp3.com. Pick an obscure music category like Celtic. Go to the end of
the bestseller list: there are 1,168 songs listed. These are not illegal copyright scams, where
the music has been stolen by the artist. These are real songs, posted by the artists or their
labels. The whole song… not part of it.
Why would anyone do this? Give away an entire album of music when Bob Dylan can
charge $16?
Look at it from your point of view. An unknown artist is a commodity. An unknown artist is
the same as a box of salt. If you don’t know why the artist is unique, why pay?
Look at it from the artist’s point of view. The cost of giving away songs is literally zero. Once
you’ve made a record, the cost of one more copy of an MP3 is nothing. And if it helps you
Unleashing the Ideavirus 146 http://www.ideavirus.com
get listened to, if it helps you build your virus, then you’re one step closer to no longer being
a commodity!
In fact, many artists would pay people to listen to their MP3 cuts if they thought it would
help them break through the clutter and get famous. Take a look at the Payola section of
MP3.com. You can do exactly that… pay money to have your song promoted so you can
give it away for free.
Of course, once you’re famous, you can go ahead and charge $16 for your CDs.
Or can you?
Sure, there’s going to be room for collectibles. For live events. For autographed guitars. But
once something is no longer hot and fresh and the latest, rarest thing, why wouldn’t the selfinterested
artist go ahead and give it away free to stoke the ideavirus for the next release? In a
competitive marketplace where there’s transparent information about who’s listening to
what, the Internet becomes radio. And artists know that charging radio stations is dumb.
This same logic applies to books. And to just about any other sort of digital media you can
think of. Unless there’s an extraordinarily unique property of the media being offered, I
maintain that sooner or later it’s going to be free. The Bloomberg machine used by stock
brokers, for example, commanded a huge price premium for years, because the combination
of excellent data and locked-in user interface meant it wasn’t worth switching. But as the
web replicates more and more of the data available, it’s inevitable Bloomberg’s market share
will decrease—and their prices will as well.
The exciting thing is that people who go first, who put their previously expensive digital
media out there for free, will gain the lion’s share of attention and launch bigger and longer
lasting viruses.
So. Who wants to go first? And who wants to go… last?
Unleashing the Ideavirus 147 http://www.ideavirus.com
Van Gogh Lost His Ear To Prove A Point
When Vincent was painting, he often sold his work for just enough money to cover the cost
of paints and canvas. Back then, his ideas and his paintings were one and the same, and
neither was held in very high regard.
Over the last hundred years or so, something has changed. Instead of selling for $200, or
$2,000 or even $20,000, it’s not unusual to read of a $10,000,000 sale of a Van Gogh. Over
time his paintings have increased in value with each sale. But the paintings haven’t changed
at all, have they?
What’s changed is the value of his ideas and the popularity of his ideas—not the ideas
themselves. It’s easy to get a reproduction of a Van Gogh. For a few hundred dollars, you can
even get a painted reproduction that only a trained expert can tell isn’t the original. So why
pay twenty million dollars?
Because you’re buying a souvenir. An expensive souvenir, no doubt, but a souvenir
nonetheless. The original painting is a priceless keepsake that reminds you of the idea
Vincent Van Gogh first unleashed on the world. And unfortunately for Van Gogh and his
heirs, it took far too long for the ideavirus to spread.
Compare this inexorable and dramatic increase in value with the resale value of a newspaper.
Today’s newspaper is “worth” fifty cents to a dollar. The combination of recent news and
events in one handy packet makes it a reasonable purchase. However, yesterday’s paper is
virtually worthless. And if you’ve got a big stack of them, you’re going to have to pay me to
take them away.
Why? What happened? Simple: the newspaper is a vessel for ideas with very short half-lives,
and once the ideas aren’t fresh any more, they’re worthless. Imagine, though, how much you
could sell tomorrow’s paper for—especially if you sold it while the stock market was still
open.
Unleashing the Ideavirus 148 http://www.ideavirus.com
This is a lesson in one way to make your digital media valuable: keep it fresh. It’s getting
harder and harder to do; they used to send Charles Dickens’ serialized novels over here by
boat—news that was three weeks old was considered fresh—but that doesn’t mean you can’t
succeed.
By focusing on souvenirs and speed, creators of digital media can create two effective ways to
profit when we play by the coming new set of rules.
Unleashing the Ideavirus 149 http://www.ideavirus.com
Answering InaÕs Question
So how is a bookstore to make money? Or a publisher? Or an art dealer or a consultant or a
music label?
The biggest objection to ideavirus thinking is that it represents a substantial change from
standard operating procedures. Successful companies are in no hurry to rock the boat…
especially if it represents a significant change in the status quo and a risk to planned-for
revenue and profits.
Mighty Words (an Internet articles publisher) is aggressively targeting traditional book
publishers and re-sellers by creating a new online business that cuts out all the middlemen
and lets authors sell works (preferably 15 to 60 pages) directly to readers. Go to their site and
you can find thousands of articles, priced from $3 to $30 each.
Mighty Words gets half the revenue, the author gets half, the reader gets insight and wisdom
and everybody wins. By creating new markets for mid-length ideas, the company seems to be
filling a niche. Of course, then they can turn their success into dominance by integrating up
the food chain until they disrupt all the competition in the publishing world and profit
mightily.
So you’d think that the concept of ideaviruses would be attractive to this maverick company.
After all, they’re only a few months old.
Not true. It bugs them terribly to give away ideas, because it flies in the face of their brand
new business model. After all, if an author profits most by giving away her work, how does
Mighty Words make money?
If you catch yourself asking this question about a new business model innovation (“How
would we make money?”) you’re headed for trouble. The Internet doesn’t care how you
make money. The Internet isn’t going to wait while you figure out how to react. Instead,
there’s some crazy entrepreneur who’s willing to spend years of his life making you miserable
by wrecking your business model.
Unleashing the Ideavirus 150 http://www.ideavirus.com
Email didn’t ask the fax companies if it was okay with them if a new, instant, permanent,
digital communications tool came along and wrecked the fax business. Matchmaker.com
didn’t hold meetings with the extremely profitable video dating services out there to find out
if it was okay for them to launch. Who cares if Matchmaker.com never makes money? What
matters to the existing businesses is that these new kids on the block have wrecked the
business landscape for the old providers.
Giving digital media away is a reality. Non-dominant players in any industry will always
succeed more by giving away digital content and then profiting later than they will by
holding back to preserve somebody else’s business model.
It was a mistake for the record companies to fight radio and MTV. It’s a mistake for them to
fight Napster. Rather than fighting to patch the leaky bucket, perhaps they could redefine
their roles so they can figure out how to profit from a “free” world.
Unleashing the Ideavirus 151 http://www.ideavirus.com
Crossing The Chasm With An Ideavirus
In his brilliant book, Crossing the Chasm, Geoffrey Moore unleashed a powerful ideavirus
about how new businesses and new ideas get spread. Basically, there’s a chasm in the product
adoption cycle.
The curve used to look like this:
On the left are early adopters, the nerds who love new stuff, who want to get their hands on
anything neat and potentially wonderful. On the right are the laggards, who are still having
trouble getting rid of their steam engine cars.
The meat is obviously in the center. That’s where the vast majority of us live, and where the
combination of big audience and pretty decent pricing is most attractive to a marketer.
In the old days, people believed that you could introduce a product to the early adopters, use
the high profits from those sales to ramp up production and advertising, and then roll the
product out to the masses.
There’s a problem with this view: there’s a gap in the curve. A chasm.
Unleashing the Ideavirus 152 http://www.ideavirus.com
What happened? Turns out people on the right side of the chasm aren’t just lazier or less
intellectually curious than the folks on the left of the chasm. It turns out that people on the
right are fundamentally different from the folks on the left. How?
Pre-chasm people want something cool. Post-chasm people want something that works.
A nerd wants the latest personal digital assistant. An executive wants to keep her
appointments straight.
A cutting-edge IT guy at Allstate wants a device that will use satellite technology to update
claims instantly. The CEO at Nationwide wants something that will reduce costs.
A fashionista wants the latest haute couture outfit from Paris, regardless of how ridiculous it
looks. The party girl wants something that’ll get her a hot date next week.
The foodie wants maple-jalapeño corncakes, layered with crème fraiche and bourbon. The
hungry person just wants something to eat.
As you can see, focusing on the folks who will give you early feedback, be your initial
sneezers, your first customers and probably your start-up’s employees is a one-way ticket to
doom. Their advice will help you make stuff that’s expensive, heavy, hard to use, awkward
Unleashing the Ideavirus 153 http://www.ideavirus.com
and difficult to understand. You’ll be the darling of some well-respected sneezers, and then
you’ll fail. This is why many ideaviruses start with plenty of powerful sneezers but end up
dying.
It happened to Apple with the Newton. It happened to Microsoft with almost every product
they’ve ever launched (Bill Gates is to the far, far left of the chasm—that’s why it takes
Microsoft to version 3 to build something that catches on). It happened to Reebok and to
Stephen Sondheim and to Lou Reed. In every case, they indulged the pre-chasm audience
and lost the big wins on the right. (Of course, in some cases—like Microsoft—sheer staying
power is able to force you over the chasm.)
The challenge in launching an ideavirus is to understand who the pre-chasm sneezers are,
and using them but not letting them use you. In other words, they’re the ones who are most
likely to embrace your new idea and talk about it, but if you don’t get past them to the rest
of the curve, you’re doomed.
Why do Woody Allen movies consistently sell so few tickets? They’re certainly adored by
critics, nominated for awards and attended by a core group of sneezers. The reason is simple:
the virus hits a chasm. There’s a huge gap between the Woody Allen audience and the rest of
the population. Because of this chasm, the word rarely spreads as far and as wide as it could.
The success of his latest movie, “Small Time Crooks,” points to the problem. This movie has
box-office results that rank among the top four he’s ever released for one simple reason.
During the month it was released, it was the only clean family movie available. By focusing
(intentionally or not) on creating a wry, funny movie that was understandable at many levels
and worth bringing your kids to, Woody crossed the chasm. Suddenly, the sneezers were
saying, “This is a great movie for your family,” instead of saying, “this is another great
Woody Allen movie.”
Some viruses are just never going to cross the chasm. Try as they might, the computer nerds
are having no luck at all getting normal people to start using Linux. And the guys who sell
the hottest hot sauce in the world are just not going to find themselves on the table at TGI
Friday’s restaurant.
Unleashing the Ideavirus 154 http://www.ideavirus.com
But that’s okay. It’s okay because these idea merchants understand that the hive they’re
targeting is not everyone. They understand that if they choose the right hive, it’s okay if it’s
small, it’s okay if it’s not everyone. The caveat, of course, is to match your expenses and your
expectations to the size of the hive you’ve chosen. If you spend big on product development
and marketing, figuring that will get you over the chasm, it better.
Unleashing the Ideavirus 155 http://www.ideavirus.com
The Myth Of The Tipping Point
One of the most seductive ideas in Gladwell’s The Tipping Point is that somehow a magic
moment appears when the entire population goes from blissful unawareness of your offering
to total and complete infatuation.
While this certainly appears to happen, it’s not a reality for most companies and most ideas,
and it’s not even a requisite for mindblowing success. There are two related reasons for this.
The first is that it ignores the power of the hive. The chances that you’re going to launch an
ideavirus that consumes the entire population is slim indeed. After all, there are seven billion
people out there, and all of them have very different needs and communication cycles. Even
if you just boil it down to the United States, or to Republicans with Internet access, it’s
pretty clear that large hives very rarely tip about anything.
The second reason is that winning and tipping aren’t the same thing. In order to really win
with an ideavirus, you have to concentrate your message very tightly on a specific hive. But
even then it’s not clear to me that you have to tip to win.
Let’s take a look at eBay, for example. By almost any measure, eBay is a winner. It’s
employees are millionaires and billionaires. Early investors are delighted. Users are happy,
with time spent on the service going up all the time.
But has eBay tipped? Certainly not in terms of awareness among the general population.
When asked to name an online service, only a tiny fraction of the population picks eBay as
their first choice. But it gets even more obvious when you ask people where they go to buy
and sell used junk. The vast majority of people are using classified ads and garage sales, not
eBay.
Yes, the management of eBay is on the cover of Fortune and Business Week at least once a
month, or so it seems. Yes, every meeting at certain high-tech companies includes the
sentence, “But will this allow us to become the eBay of [insert business here].” Within a very
small, very focused, very profitable hive, eBay is a winner. But it didn’t happen because some
Unleashing the Ideavirus 156 http://www.ideavirus.com
magical tipping process took place. It happened because a smart, focused, powerful ideavirus
started and spread across a concentrated hive of investors and pundits, and this led a tiny
company to have a huge stock market valuation.
The reason I point out this myth is that it’s dangerous. Dangerous because it leads idea
merchants to believe that if they just wait long enough, something will happen and make
them tip—like Yahoo! or the Atkins diet or Nike or the Macarena. I don’t buy it. The odds
are with you if you focus on small hives, filled with pre-chasm sneezers, and then obsess with
crossing the chasm as fast as you possibly can. If you tip, that’s a bonus.
Unleashing the Ideavirus 157 http://www.ideavirus.com
The Compounding Effect
One of the factors that makes the tipping point myth seem more real is the power that comes
from multiple sneezers. While one or two recommendations might make for a smooth
transition, there’s no doubt that as the number of powerful sneezers recommending an idea
to you increases, the chances that you’re going to use it dramatically increases.
This is a genuine side effect of the tipping point. As you are surrounded by hive members
who loudly sneeze about a new idea, the greater your chances of at least trying the idea.
Rather than decreasing returns, as we find in advertising, there are actually increasing returns
from an ideavirus. The more people who have it, the more you want it.
Are there iconoclasts who fight every trend? Of course. They wouldn’t be seen in a hip car or
a hip restaurant or listening to a pop tune. But for most individuals, in most hives, the
compounding effect is quite strong.
Thus, one of the most essential tasks an idea merchant can accomplish is to bring all positive
news to the forefront. They make every hive member think that every other hive member is
already converted to the virus, thus creating the self-fulfilling prophecy that leads to success.
Publishing houses do this when they print lots and lots of copies of a book and ship it out to
stores. If there are tons stacked up by the cash register, many people think that this must be
the hot new book, so they buy it. On the basis of this trial, the book shows up on the
bestseller lists soon after being published. This, of course, leads to more people trying it,
because, after all, it’s on the bestseller list. So, without any genuine “word of mouth,” the
book has established a much larger foundation. It won’t get any bigger unless the idea is
virusworthy, but at least the book got a shot.
On Eric Raymond’s page promoting his essay “The Cathedral and the Bazaar,” he lists and
points to critiques of his work. Why? Because bringing these critiques (both positive and
negative) to the forefront is an excellent way to bring the compounding effect into play.
Unleashing the Ideavirus 158 http://www.ideavirus.com
Most marketers focus on getting organic word of mouth going without taking the time to lay
a framework for the compounding effect. Music Direct, on the other hand, goes to great
lengths to leverage powerful sneezers. On their site (www.amusicdirect.com) they list the
recommended recordings of several high-end stereo magazines. Each one is linked directly to
their online ordering service. Thus, you can read a review in Stereophile and know that you’re
only a click away from buying it on their site. Look at a few of the lists and you’ll notice that
the same record shows up more than once. Boom. Even if you weren’t considering buying
that title, the fact that three trusted sneezers have recommended it makes it much more likely
that you’ll consider it.
The folks at Telarc Records learned this lesson early on. Unable to compete with the big
boys at the other classical music labels, they recorded the Cincinnati Orchestra playing
dramatic renditions of songs that only a stereo lover could love. Big cymbals. Cannons. You
get the idea.
Then, they worked hard to get high-end stereo shops to use the CDs they were recording to
demonstrate their equipment. Thousands of consumers who might never have rushed out to
buy another recording of Tchaikovsky’s “1812 Overture” now discovered that Telarc’s
recording was being used anytime they listened to $5,000 speakers or $3,000 amplifiers.
Hey, if you were willing to drop 20 large on a stereo system, certainly it was worth a few
more bucks to have the best CDs to play on it, wasn’t it?
Unleashing the Ideavirus 159 http://www.ideavirus.com
Bill GatesÕ Biggest Nightmare
One of the repeated mantras during the Microsoft anti-trust sideshow was that middleware
threatened the very essence of Microsoft’s cash cow: the Windows OS.
Basically, middleware is software that sits on top of the operating system on your computer
and talks to the Internet or other programs. Once you develop a killer piece of middleware, it
doesn’t matter what operating system you’re running—the middleware works the same. The
first successful example of middleware was the browser, but you can be sure there will be
more.
Today I spoke to a woman named Louise Wannier who developed a piece of software called
enfish. You can find it at http://www.enfish.com.
What if there were a piece of middleware that was designed for people who had an “always
on” connection to the Net. And what if that software let you automatically track your stocks,
your email, your calendar, your instant messages—all the stuff you spend time doing online,
but in an organized way, and all at once?
If you’re like me, that accounts for the vast majority of time you use the computer.
Suddenly, Windows is obsolete.
Sounds like it’s time for Louise to start shopping for a new Porsche, no?
But there are some problems. And all of them are related to the idea she’s created and how to
turn it into an ideavirus.
Problem #1 In order to use enfish, you have to download code. Experience has shown us that
this is a huge amount of friction with which to saddle a new idea. Basically, you can’t enjoy
the software until you go through the pain and suffering of downloading and installing it.
Unleashing the Ideavirus 160 http://www.ideavirus.com
Products like Shockwave and various forms of wallets have shown us that it can cost as much
as $100 in direct to consumer marketing expenditures to get someone to download a piece of
software. In the case of enfish, this is way, way too much.
Solution: Get rid of the download if possible. If not, make it swift and painless.
Problem #2: This is a private experience. Unlike ICQ or Hotmail, which are both based on
communications and are thus pretty viral, enfish saves you time by organizing your life and
your data, and so you’re not naturally inclined to spread the idea. In other words, it doesn’t
do its own sneezing, nor does it reward you for sneezing on its behalf.
Solution: Make it public. Let people post their bookmarks and layouts for their co-workers.
Figure out how to turn it into a communications tool because communications tools are the
most likely to go viral.
Problem #3: It’s not very smooth. It’s awfully difficult to describe what enfish does, because
it’s not simple. It’s biggest strength—that it solves a problem you didn’t know you had—is
also a huge hassle when it comes to marketing the thing. “Free Email” is smooth indeed.
“Automated organizer for always-on Internet knowledge workers that saves you three hours a
day” is not.
Solution: This is the hardest one. Breakthroughs frequently have this problem. Figure out
how to teach the sneezers what to say… even if it means giving them a pre-written email to
forward to friends.
Problem #4: There’s no existing amplifier. There are plenty of sites where people talk about
cars or hobbies or restaurants. Find a hive and you can talk to them. There are magazines
about gardening and starting Internet companies. There are TV shows about cooking and
the weather. But there’s no natural way to amplify a message about the problem that enfish
solves. There are few easily identifiable hives that are just sitting there, waiting to hear from
enfish.
Solution: Use advertising to feature your most satisfied users.
Unleashing the Ideavirus 161 http://www.ideavirus.com
Problem #5: The ideavirus isn’t a natural monopoly. In other words, once they do a great job
of spreading the virus, it’s not clear that enfish’s solution will be the only one to triumph.
One of the amazing things about ICQ, for example, is that the better they did, the better
they did. In other words, there were network effects that created a natural monopoly.
Unfortunately for enfish, there isn’t an obvious reason why an enfish knock-off couldn’t be
as good as enfish.
Solution: The same communication tools that made it go viral will also support its position
as a monopoly.
The good news is that once it catches on, enfish will be extraordinarily persistent. It will sit
on your desk for years, saving you time and making enfish a profit as they go.
The other good news is that because the benefit delivered by enfish is so awesome, once the
virus starts to spread through a hive, it ought to spread with high velocity, and with the
support of the very best kind of powerful sneezers. This is a product that can easily attract
the attention of sneezers on the left side of the chasm (the early adopters) but also offers very
real benefits that will make it fairly smooth to transfer to the right side of the chasm.
So what should enfish do?
My recommendation is that they focus on a single hive: people who trade stocks online.
Why?
Well, the hive is pretty easy to talk to. There are eight or so online brokerage companies who
could all benefit by sneezing about enfish to their best customers. And online traders talk to
each other constantly, meaning that the message can spread through this community with
enormous velocity.
Further, the benefit to online traders is much, much easier to describe, so it’s a lot smoother:
Make more money by trading in a more organized way.
Unleashing the Ideavirus 162 http://www.ideavirus.com
There’s also a vacuum here. Nobody else is offering this value proposition to this audience.
And finally, because online traders tend to be more technically astute, the friction induced by
the download will be less of a barrier.
After infecting the trader hive, will the enfish virus jump to other hives? Perhaps. But in
order to do that, enfish needs to make two significant changes to their product (remember,
the best ideaviruses are integrated right into the product, not tacked on at the end by the
marketing department).
The first change is to create significant benefits to users that derive from enfish’s scale. In
other words, create a network effect so there’s a natural monopoly.
The second change is to create clear and obvious incentives for existing enfish users to
evangelize and bring in new enfish users. These could be simple bribes, but it’s much, much
more effective if the incentives are related to the product—making it work better when you
have more buddies involved.
If they can accomplish these two tricky tasks (so tricky you’ll notice I haven’t even told you
how to do it!), then the odds of the virus jumping from the trader hive to the Net audience
at large increases dramatically.
Unleashing the Ideavirus 163 http://www.ideavirus.com
Hey, Skinny!
One of the most successful books of the last five years has been The Atkins Diet. Dr. Atkins
has sold more than seven million copies of his books…with almost no advertising.
How does a marketing phenomenon like this happen? Conventional marketing wisdom says
that he would need to spend tens or even hundreds of millions of dollars to motivate the one
out of every 40 Americans who has rushed out and bought his book.
The secret to the book’s success is that the diet was virusworthy. Unlike other diets, it really
generates remarkable results in a very short time (let’s leave the health discussion for another
book).
But being virusworthy isn’t enough. It was also smooth. All you had do to tell someone what
diet you were on was say one word, “Atkins.” Because the author became synonymous with
the diet, it was easy to spread.
But the real secret was amplification. Word of mouth could never generate seven million
conversions, not without being amplified.
So what was the amplifier? Your skinnyness! Whenever the diet worked, nosy and proud
friends would ask the dieter, “Hey, skinny! You look great. How’d you do it?” And the dieter
would proudly respond: “Atkins.”
This self-fueling virus saved Atkins millions. And it would never work for transcendental
meditation, St. Johns Wort or reflexology. Nobody is going to notice your inner peace, after
all. Yes, we may be obsessed with the way we look, but it also leads to powerful viruses.
If you doubt the power of this, take a look at all the tattooed kids on the beach.
Unleashing the Ideavirus 164 http://www.ideavirus.com
Get Big Fast? The Mistake So Many Companies MakeÉ
Why was there so much bloodletting among consumer etailers this spring? How did
Boo.com burn through more than a hundred million dollars in start up cash? Why is
Salon.com, arguably one of the most literate sites on the web, floundering?
The answer for almost all these high profile sites is the same: Get Big Fast isn’t always the
right advice.
Remember, an ideavirus adores a vacuum. So many companies, especially those racing to be
the first to fill a vacuum, spend a huge percentage of their funds trying to prime an ideavirus
by buying huge amounts of poorly executed, poor performing interruption advertising.
Big-spending interruption marketers hope the following:
1.
That sheer bulk will make this bad advertising work.
2.
That sheer bulk will scare off the competition.
3.
That an ideavirus will be spawned and they will become instantly and permanently
popular.
4.
That once they are a center of an ideavirus, their truly flawed business model will
magically make sense. Sort of the AOL effect—you can’t be profitable if you’re small and
illogical, but if you’re big and illogical, you can make a fortune from the companies that
pay you because you have a huge market.
They also fear:
1. That someone else will come along and spend more and move faster than them.
2. That if they take their time, the market will realize that their business model is totally
flawed and they won’t be able to get any more funding.
Alas, the pursuit of an ideavirus has confused their analysis. Instead of viewing themselves as
a natural monopoly, as virusworthy, as needing to fill a vacuum, they could have considered
a very different analysis:
Unleashing the Ideavirus 165 http://www.ideavirus.com
1. The ideavirus space for “online merchant” is already filled. It’s filled by Amazon, and to a
lesser, more twisted degree, by eBay and Priceline.
2. Given that the big space is filled, they ought to understand that the virus they’re going to
spread is going to be far smaller and far more quirky. Thus, the win is smaller, but the good
news is that they’ll need far less money to get there.
3. Once you accept the second point, you can realize that growing a virus slowly is actually a
better strategy. Why? Because you get to perfect your business model as you grow, and you
get holistic, organic virus growth, instead of the forced growth a Super Bowl ad brings you.
In other words, you actually get to earn the people who visit your site.
Diamond Organics (www.diamondorganics.com) is following this approach, and it’s
working. Instead of trying to be a category killer and spending tons of money to persuade the
world that their organic vegetable-by-Federal-Express business is a good one, they’re instead
focused on delighting one customer at a time.
By spending little and scaling a lot more slowly, Diamond is able to build serious sneezers,
sneezers who are quite powerful and need little additional inducement to spread the word.
By getting their systems into shape they avoid the pitfalls that struck ToysRUs.com last
Christmas.
But doesn’t this fly in the face of the ideavirus mantra? In many ways it does. It also
challenges the permission marketing idea that once a consumer solves a problem, they’re not
in any hurry to find someone else to solve the same problem, so vendors can achieve lockout.
The problem with implementing the grow-slow strategy is that you might not get the
chance. If you’re a CEO or marketing executive in a new business, you’re subject to the
Catch-22 of rapid business development. You can’t grow (and you can’t get funded) if you
don’t make promises, but those promises might not be able to be kept. And if the promises
aren’t kept (ToysRUs.com failing to ship in time for Christmas) or the promises cost too
much to keep (Boo.com) it doesn’t matter anyway, because you’ll be bust. So most
entrepreneurs make the promises anyway, even though they realize that organic growth is the
better strategy.
Unleashing the Ideavirus 166 http://www.ideavirus.com
So, there has to be a middle ground. And the middle ground that makes the most sense to
me is to not launch a business that can’t sustain an ideavirus. And second, not to force an
ideavirus to happen before the market is ready for it.
My best example is Amazon. My firm belief is that if Jeff Bezos had launched it a year later
or a year earlier, it would never have worked. A year too early and there wouldn’t have been
enough sneezers and the medium wouldn’t have been ready to spread the word. A year too
late and the market would have been so overheated that his promise would have never
broken through the clutter and attracted the attention of sneezers in the first place.
It’s hard for me to imagine how a $50 million marketing campaign is ever appropriate for
any business to launch an ideavirus. If you need to interrupt that many people, you’re doing
something wrong. Sure, you need that much (actually, much more than that) to launch a
brand and to do traditional marketing. But if you’re virusworthy, you generally can do it for
a lot less money than that.
So you need to match the speed of your virus not just with the money you raise but also with
the promises you make to your investors. Yes, Hotmail and Netscape and ICQ and eBay
grew fast, fast, fast. But that doesn’t mean you will. Optimize for the virus and build it into
your company—or expect that it isn’t going to happen.
Unleashing the Ideavirus 167 http://www.ideavirus.com
The Heart Of Viral Marketing
Remember, viral marketing is a special case of the ideavirus where the amplifier for the virus
is built right into the product. And the hot spot for this wonderful self-propagating process is
in communication products.
Let’s take a look at the history of interpersonal business communication over the last 120
years:
Stamps
Telegraph
Telegram
Telephone
Telex
Fax
Conference Calls
Federal Express
Cell Phones
Videoconferencing
The Web
ICQ and Instant Messaging
It’s a pretty extraordinary list. Twenty-five years ago, when I got my first real job, we had no
voice mail, no web pages, no fax machine, no cell phones, no pagers and no email. I
sometimes wonder what we did all day!
So why is there such rapid innovation in this field, when, at the same time, we are still using
precisely the same Qwerty keyboard found on the early typewriters and the same pink “while
you were out” message pads that came with the first phone?
Unleashing the Ideavirus 168 http://www.ideavirus.com
The answer is pretty simple: Each one of these devices creates long-term profits for its
inventor but is spread at a relatively low cost. And the reason it spreads? Because of viral
marketing.
Communication products demand viral marketing because they’re worthless without
someone at the other end. Metcalfe’s law tells us that the value of a network increases with
the square of the number of people using it. So when there are 10 fax machines in the world,
that’s 25 times better than when there were just 2.
Once I buy a communications device, two things happen. First, I become a powerful sneezer,
telling all my friends to buy one so I can send them stuff. And second, provided it’s a tool
that uses an existing channel (like FedEx or Hotmail), every time I send someone a message,
it’s selling the medium.
The story of Post-It notes is so good it ought to be apocryphal but it’s actually true. Nobody
was buying them. 3M was going to cancel the whole program. Then the brand manager of
the product persuaded the secretary of the chairman of 3M to send a case of Post-Its to the
secretaries of the chairmen of the other 499 Fortune 500 companies.
Suddenly, the most powerful sneezers in the most powerful companies in the country were
sending around memos, all containing comments scrawled on Post-Its. It took just a few
months after that for it to become yet another successful business communication device. A
classic ideavirus.
When I was in business school, a classmate spent a year working on a secret project he
wouldn’t tell anyone about. Turns out he was working to launch MCI Mail, the first
commercial email system. It’s a shame he couldn’t tell anyone, because a bunch of us would
have been happy to tell him what we knew, even 20 years ago: An email system isn’t going to
work if there isn’t anyone to send email to!
MCI was charging about $100 to set you up, and another $20 or so a month, plus usage, for
this new service. Big mistake! They inserted friction early in the process, ensuring that people
would never try it, especially so early in the virus’s life.
Unleashing the Ideavirus 169 http://www.ideavirus.com
My idea was that they give MCI Mail, plus a computer to send it with, to 50 people in each
of the top 100 companies in a given industry. FREE. Suddenly, that industry’s leaders would
be communicating with each other fast and frequently. It would change the culture of the
company. The virus would spread. MCI would win.
What’s the lesson? There are two:
3.
If you can somehow convert your idea into a virus that has to do with communication,
it’s much easier to make it go viral. The best sort of communication is an actual
communication tool (like the fax machine or ICQ) but inventing words, new musical
concepts or other ways people communicate goes a long way as well.
4.
Find the powerful sneezers and beg, cajole and bribe them to use your new tool.
Unleashing the Ideavirus 170 http://www.ideavirus.com
The Great Advertising Paradox
Imagine for a second that there was a machine your company could buy. Figure it costs
anywhere from $1 million to $100 million. You’re promised by the salesman that using this
machine can transform your business, dramatically increase sales and profits and turn your
business into a success.
Interested?
What if the salesperson also tells you that companies who don’t buy the machine have a hard
time growing and often languish… and then she points out that one company, Procter &
Gamble, spent more than $2 billion on machines just like this one last year. Interested?
Oh. There’s one caveat. Actually two:
The ongoing output of the machine can’t be measured. You have almost no idea if it’s
working or not—and there’s no guarantee. If it doesn’t work, tough.
Still interested? Well, after those caveats, there’s just one more fact to mention: On average,
the machine only works for about one out of every ten companies that use it. Ninety percent
of the time, the machine fails to work.
By now, you’ve probably figured out that I’m talking about advertising. Mass market
advertising is one of the most puzzling success stories of our economy. Companies spend
billions of dollars to interrupt people with ads they don’t want about products they don’t
need. The ads rarely work. Ads that are created by less than competent ad agencies and
clients almost never work. One day, I’d like to write a book about the worst ads ever run, but
my fear is that it would be too long.
Now, writing off all marketing expenditures because most of the time they don’t work isn’t
the right answer, either. Hence the paradox. You can’t grow without it. But you often can’t
grow with it, either.
Unleashing the Ideavirus 171 http://www.ideavirus.com
So if advertising is such a crap shoot, such a dangerous venture, why do it? Because for the
last 100 years, the single best way to determine whether a company was going to get big or
stay small was to look at its advertising. Time and time again, aggressive companies with
great advertising—regardless of their industry—have managed to make the ads pay and to
grow and become profitable.
So what changed?
A few things. First, the clutter in the marketplace has finally made advertising even less
effective. A threshold has been crossed, and with hundreds of TV channels, thousands of
magazines and literally millions of websites, there’s just too much clutter to reliably interrupt
people. Add to this the “consumerization” of business-to-business sales (with more ads
directed at businesses than ever before) and the explosion of dot-com advertising, and it’s
easy to see that the game is fundamentally different.
So, what should we do about it? Consider the ironic situation that MarchFirst, Inc. finds
itself in. MarchFirst was formed in 2000, the result of a merger between USWeb/CKS,
which does websites and consulting and advertising, and Whittman-Hart, an Internet
consulting firm.
According to the New York Times, MarchFirst wants to launch with a bang, so they’ve
announced a $50,000,000 advertising campaign designed to “cut through the clutter” and to
“get the name out there, to create strong brand awareness,” according to Robert Bernard,
their CEO.
How are they going to do this? By buying full-page ads in newspapers and Internet trade
magazines, by running TV commercials during sporting events, and even running ads in
lifestyle magazines.
Now, be honest. If you’re flipping through a magazine or surfing through channels on TV
and you come across an ad that is based on “the human desire to be first,” will you stop and
pay attention? Will the slogan “a new company for the new economy” make you sit up and
take notice? Will you give up a few minutes of your precious time to read an ad about a
Unleashing the Ideavirus 172 http://www.ideavirus.com
company you’ve never heard of, which solves a problem you probably don’t have? Not
bloody likely.
Surely there’s a better way for this company to spend fifty million dollars. Surely there’s a
more effective way to start a relationship with the 10,000 people who matter to them than
interrupting millions of us over and over and over….
Old-fashioned, hand-crafted, fun-to-make, sorta-fun-to-watch interruption advertising isn’t
going to disappear altogether. But it’s just a matter of time before CEOs and investors start
measuring their ever-increasing ad budgets with the same critical eye they use for every other
insanely expensive investment they make.
Unleashing the Ideavirus 173 http://www.ideavirus.com
Permission: The Missing Ingredient
When Hotmail launched their free email service, they did almost everything right. They
built a product that was worthy of an ideavirus. They made is smooth. They built
amplification right into the product. They approached the right people and started with just
enough push to make the thing take off.
But then they made a huge error.
They forgot to get permission to follow up. They failed to ask their users (the folks who were
infected by the virus) if it was okay to send them an anticipated, personal and relevant email
every week. They didn’t build an asset.
As a result, the Hotmail website has one and only one way to make money. By selling banner
ads. And nobody clicks on banner ads when they’re reading their email. So advertising on the
Hotmail site is super cheap. And probably overpriced.
We’re talking a multi-billion-dollar mistake here. If they had permission to follow up with
20 million people every single week with an email that was filled with useful information and
relevant ads, they could easily sell the slots in this email for a buck a week. That’s a billion
dollars a year in lost revenue, which, using stock market multiples, is a gazillion dollars in
market cap. All because they forgot to ask for permission.
Let’s face it: It’s unlikely that every single idea you come up with is virusworthy. If we’re
going to have to grow our businesses in a reliable, predictable way, it’s unwieldy to have to
depend on an ideavirus catching on every time we want to grow. We still need a way to
communicate with people directly, to do it when we want to, to talk to the marketplace
without a filter.
Advertising used to be the way to do this. But what a waste! What a waste to have to pay a
magazine for an ad to reach a user you already have! You’ve got a pair of Nike sneakers in
your closet. But Nike has to buy an ad to reach you—they don’t have permission or the
ability to talk to you directly.
Unleashing the Ideavirus 174 http://www.ideavirus.com
Same is true with Stevie Wonder. You bought “Innervisions” because you heard it at a
friend’s house, or on the radio, not because you saw an ad. Yet when Stevie comes out with a
new album, his record label has to start all over again, interrupting you using mass media.
Both Stevie and his label waste a huge asset every single time you buy an album. They have
no idea who you are, and worse, they don’t have permission to contact you again.
The challenge of the idea merchant is to turn the virus into an asset. And you turn the virus
into an asset when you ask the user for permission to follow up directly!
This is probably the biggest mistake that ideavirus marketers have made to date. They launch
a virus—a website, a book, a record, a software program, a food—and enjoy the fruits of the
virus while it lasts, but fail to gain a long term asset. And without that asset, they can’t
launch new products or leverage their existing ones without long lag times and the high costs
associated with contacting the users they’ve already converted.
Unleashing the Ideavirus 175 http://www.ideavirus.com
How A Virus And Permission Team Up To Find Aliens
Turns out that the best way to find alien life somewhere in the universe is to listen.
Specifically, to use powerful supercomputers to scan the spectrums for anomalous sounds.
Unfortunately, there isn’t a supercomputer available that’s powerful enough to get the job
done in our lifetime. Which is why the SETI built the largest distributed computer network
in the world. More than 2,000,000 computers are working, in their spare time, to process
these huge chunks of data.
The mechanics of the system are elegant. Whenever your computer has some downtime, a
screensaver pops up, and behind the scenes, your Pentium processor starts cranking through
data that the computer downloads through the web. But what’s really neat is the fact that all
2,000,000 computers in the network signed up without any advertising or financial
inducement.
Instead, the SETI project launched an ideavirus. Word spread among nerds the world over
that they could help find alien intelligence by having their computers participate in the
network. It’s a classic ideavirus, propagated by some powerful sneezers.
The power of the network, though, comes from the fact that they don’t have to relaunch the
thing every week. That it’s incredibly persistent, of course (once you set it up, it stays set up
until you take the initiative to turn it off), but even better, they have permission to
communicate to their users.
This permission is an asset. You can measure it. You can leverage it. You could turn it into
cash if you wanted to.
Let’s take one more look at the sequence:
1. Invent a virusworthy idea.
2. Make it smooth and persistent.
3. Incent powerful sneezers.
4. Get their permission to follow up.
Unleashing the Ideavirus 176 http://www.ideavirus.com
The Art of Creating an Ideavirus
So far, much of what we’ve discussed is science. Mathematical formulas, game theory,
categories of individuals. This is stuff you have to do well to allow your virus to take hold.
And as the understanding of propagating viruses increases, companies will get better and
better at the tactics.
The hard part, though, is building the virus in the first place. The hard part is inventing an
idea that’s so compelling, so ¡Wow! that it spreads through the hive with high velocity,
converting everyone in its path.
How is it that some ideas move so quickly while others just languish? Why did the Apple
Newton fail so badly, while the Palm took off just a few years later?
Caveat: If I knew the answer, I’m not sure I would tell you! To date, no one has come up
with a repeatable formula for creating viruses in a reliable way. There are precious few people
who are serial virus starters.
My hope was that this would be a long chapter, and I could answer your big question about
how. Alas, I don’t know. I know it when I see it, but I fear the rest is art.
Which means you win by trying. And failing. Test, try, fail, measure, evolve, repeat, persist.
It’s old fashioned and hot and dusty and by no means guaranteed to work. Sigh.
Unleashing the Ideavirus 177 http://www.ideavirus.com
Is He Really More Evil Than Satan Himself?
The Google.com search engine is perhaps the most effective and accurate way to search the
web. Why? Because instead of reading every site and trying to understand the content of
every page, Google just reads the links to sites, and selects the pages that plenty of other sites
link to. This way, popular pages rise to the top, and it’s far harder to trick the engine into
pointing to your page by loading up on clever phrases.
Anyway, a few months ago, if you typed, “More Evil Than Satan Himself” into the Google
search engine, the top link it would return was Microsoft.com. Other links that followed
involved mostly Bill Gates.
How did this happen? How was it that enough hackers, nerds and online intelligentsia
building web pages had a strong enough opinion about Bill & Co. that they would go to the
trouble of creating links to Microsoft that used the words like evil and Satan?
Regardless of the dynamics of the virus itself, there’s no question that it’s pervasive, that it
will take years to erase and that it cost Microsoft dearly. By filling the vacuum and creating
an ideavirus of Microsoft as an all-powerful demon, trouncing anyone who came into its
path, the company’s critics brought the Justice Department knocking on its door.
Intel and Cisco have similar market share in the computer space. McDonald’s has similar
impact in the fast food business. There are plenty of companies that could have attracted
attention. But because Microsoft (through its actions—and inaction) spawned a virus, it was
easier for its critics to get the attention of the government. Regardless of your position on the
case, it’s clear that the negative virus (and Microsoft’s actions that reinforced that impression)
affected the judge’s ruling.
Unleashing the Ideavirus 178 http://www.ideavirus.com
Case Study: Why Digimarc Is Going To Fail
Looking at the world through the ideavirus lens makes it easier to prognosticate about a
company’s success or failure. Consider the case of Digimarc.
Digimarc is a fascinating idea. Create a tiny series of dots that can easily be hidden in
magazine ad. Then, if a consumer wants to go to the advertiser’s website, all they have to do
is hold the magazine up to the camera connected to their PC, and Digimarc’s software will
read the dots and automatically take the user to the company’s site.
Charge the advertisers a tiny fee per ad and everyone wins! The magazines win because it
makes their publications more useful. The advertisers win because it creates a direct and
impactful link between the consumer and the ad. And the user wins because she finds special
promotions or discounts on the site… without having to type in a pesky URL.
So why is it going to be an utter failure?
Because there isn’t enough money in the world to turn this into a success, and the shortcut
path of creating an ideavirus isn’t going to happen any time soon either. I know that I’m
going out on a limb here, as this technology has just been featured in Wired and other
magazines and has gotten a lot of press. Still, bear with me….
First, there are few sneezers. The participating magazines have agreed to run full-page ads
promoting the service (if it helps their advertisers, it’s well worth it) but other than that,
who’s going to talk about it?
There are no promiscuous sneezers. No individual is compensated in any way for spreading
the word. There are no powerful sneezers. It’s not such a great, awe-inspiring or even totally
neat thing to do with your computer. There aren’t overwhelming discounts or secret bits of
information, because, after all, if the advertiser was willing to give a discount to a Digimarc
user, he’d probably be willing to give it to everyone, right?
Unleashing the Ideavirus 179 http://www.ideavirus.com
In addition to having a hard time describing why the service might be virusworthy, it’s not
smooth, either. In order to even find out if you like the service, you have to buy a PC camera
($100, plus the hassle of setting it up) as well as download and install a piece of software on
your PC to run the thing.
Once it is set up, it’s not clear if it’s persistent. The incremental benefit of each use of the
service doesn’t appear to go up—you don’t get better and better rewards the more you use it.
So, as the novelty wears off, the likelihood you’ll keep using it and keep sneezing about it is
small indeed.
Finally, they forgot to focus on just one hive. The ads are running in a wide variety of
magazines, targeting a wide variety of users. Because there’s no overwhelming concentration
in just one hive, the odds of the virus popping are small indeed.
So, wise guy, what would you do instead? Well, I’d re-orient the launch from a general massmarket
consumer to a very vertical business-to-business offering. For example, imagine
putting it on the factory floor. Now, instead of a technician having to drop everything and
type in a URL to see a certain page in a manual, he could just hold up the shop manual to
the camera on his already configured PC. Once you can show that it makes an overwhelming
difference in just a few shops, the word can quickly spread across the hive.
If I really wanted to find the consumer market, I’d focus only on the techiest markets (like
the readers of Wired, but I’d create a benefit to promiscuous sneezers within that market.
Rather than creating a flat environment (each ad goes straight to the user), I’d introduce an
email component that rewards the few people who came in at the beginning for emailing
their techno-friendly friends.
My guess is that if Digimarc values the advertising at retail, they’re probably going to spend
$300 for every regular user they get. In order for it to be profitable, my guess is that they
need to get that number down to $3. Problem.
Unleashing the Ideavirus 180 http://www.ideavirus.com
Why Are These Cows Laughing?
If you were in Chicago last summer or lucky enough to walk through Manhattan this June,
you may have noticed a few cows in the street. Actually, hundreds of cows. Big fiberglass
cows—practically life-sized—located on heavily trafficked corners.
The cows cost under $2,000 to make, yet when they’re sold in a charity auction at the end of
the cow invasion, they’ll go for $10,000, $30,000… up to $50,000 a piece.
What happened? How did a $2,000 cow turn into a $50,000 cow?
Well, it helps that the cows are painted by local artists. Some are poignant, some are
whimsical, but they’re all extremely interesting.
However, that doesn’t explain the whole thing. After all, it’s a used cow, having sat out in the
rain and sleet and soot for months. Add to that the fact that the cows are well-designed, but
the artists behind them are by no means famous. In fact, it’s fair to say that in most cases, the
price of the cow will be among the single highest price these artists have ever received at
auction.
A $2,000 cow turns into a $50,000 cow because of amplification. The same cow sitting in a
SOHO gallery wouldn’t be famous. The same cow straight from the artist would just be art,
not a souvenir of a special moment in the history of a city.
Literally hundreds of articles have been written about the cows. But more important, tens of
thousands of conversations have occurred. It’s impossible to walk down the street with a
friend and pass a cow without mentioning it. After all, it’s a cow, just standing there in the
street.
Like all good art, these cows create conversations. But unlike art in an art gallery, these cows
are amplifying the number of conversations. By sitting there. Every day. Calmly. Sort of
like—cows.
Unleashing the Ideavirus 181 http://www.ideavirus.com
As you pass more cows and different cows and provocative cows, your litany of cow lore
increases. Your ability to talk in interesting ways about the cows increases. “Hey, if you think
this cow is cute, wait until you hear about the cow I saw downtown….”
All of which goes to say that street art, performance art, guerrilla marketing performances…
any sort of interruption of our regular routine can lead to a moment of conversation. When
Abby Hoffman and the Yippies dropped dollar bills in the middle of Wall Street during
lunch hour, they generated a virus among the people who were there, which spread to the
media and beyond. By getting people to interact in a way that they weren’t accustomed to,
the Yippies created more impact than they would have if they’d spent five times as much
cash running an ad.
While this sort of interruption of routine is highly amplified, it is by nature not very
persistent. If you keep interrupting the routine, the routine stops being routine and the
interruptions are. If they kept the cows there for years at a time, they’d be boring. If Abby
Hoffman dropped dollar bills every day, people would quickly stop being excited by it.
That’s why the bar for interruption and guerrilla marketers keeps moving. You can’t do what
created buzz yesterday, because there’s no way that’s going to create more buzz today.
Unleashing the Ideavirus 182 http://www.ideavirus.com
Never Drink Alone
Alcohol manufacturers have two spectacular advantages over most marketers. First, there’s a
huge profit margin built in. Second, drinking is a social phenomenon, perfect for spawning
ideaviruses.
Yet, given this natural platform, most distillers are lazy and just buy a huge number of
interruption marketing events—billboards, magazine ads, liquor store displays. They work
sometimes—remember, all vodka is the same, yet people gladly pay double for Absolut.
Most telling of all is the fact that St. Pauli Girl and Becks Light are made on precisely the
same brewery line in Hamburg, yet people will insist that they prefer one over the other.
Despite their successes, though, virtually all of the money spent on liquor advertising is
wasted. Last year, alcohol marketers spent more than a billion dollars advertising their wares,
but you probably can’t even name the top 20 advertisers off the top of your head.
It’s far, far more effective for alcohol manufacturers to focus on advertising to your friends,
not to you, to invest in building viruses that make it more likely that the group will discuss a
brand and eventually order it… or at the very least, admire the person who does.
One of my favorite examples was reportedly created by the brilliant marketer Bob Dorf.
When Dorf was a PR guy, I’m told he was hired by Galliano to turn their obscure liquer into
a nationwide phenomenon. Realizing that there wasn’t enough money in the world to buy
enough “Drink Galliano” billboards, he took a very different tack. He riffed on an invention
by a California bartender named Harvey and decided to popularize the Harvey Wallbanger.
Unleashing the Ideavirus 183 http://www.ideavirus.com
Harvey was a fairly primitive cartoon, a bit better drawn than Kilroy. But he was also a
drink, a drink that coincidentally used a lot of Galliano.
Dorf then set out to teach the newly-counterculture 1970s drinking crowd about this fun
(hey, it was a cartoon) drink. He printed T-shirts, taught bartenders how to mix the drink
and even sent people into popular bars and had them order the drinks (loudly).
The result was an ideavirus. When one fashion-forward powerful sneezer in a group ordered
one, he’d have to stop and explain to everyone else in the group what it was. That group
took the news to the hive, and the virus spread.
The virus wasn’t particularly persistent (from what I’m told, a Harvey Wallbanger wasn’t
that good) but it was extremely smooth. After someone told you about the drink, all you had
to do to get one was say, “I’ll have one too, please.” High velocity, the virus did exactly what
Galliano had asked for… it put the drink on the radar screen.
Unleashing the Ideavirus 184 http://www.ideavirus.com
The Power Of Parody
The sequel to Mission: Impossible had a huge opening this summer. People talked about the
trailer, and more important, told their friends to go see the movie after they’d been.
But how was Warner going to encourage people to see it two or three or four times? How to
get to the hive of media-friendly, time-wasting teenagers just sitting around looking for ways
to spend money? Most important, how could they cost-effectively remind people that MI:2
was out there and worth seeing again?
They decided to unleash an ideavirus that parodied their own movie.
Mission: Imp is a five minute long web film designed to go viral. It features almost famous
Hollywood stars, better than usual production values (for a web virus) and best of all, a “send
to a friend” button.
Unfortunately, it’s not very funny—so while the foundation is there, it’s not as virusworthy
as it might have been if it were made by someone who wasn’t nervous about offending Tom
Cruise. Either way, though, it’s a smart and aggressive way to get out there and start a virus
to keep a product in the public eye.
Unleashing the Ideavirus 185 http://www.ideavirus.com
Bee Stings And The Measles
My friend Kate was on a canoe trip in Algonquin Park and was lucky enough to find an
outhouse on a deserted island. Relishing the chance to relieve herself without having to dig a
hole in the woods, she rushed in and sat down.
Bad news for Kate, there was a beehive inside. Forty stings later, she found herself sitting in
the lake, waiting for the pain to subside. After a long paddle back to base camp, she got
herself to a doctor. The good news is that after a little pain, she was back to normal.
Unfortunately, she’s now extremely sensitive to bee stings, and has to be ever vigilant, lest she
develop an allergic reaction.
Compare that to the childhood ritual of getting the measles. You get the measles, you sit
through a week of annoying itching, and then you’re done. You’re never going to get the
measles again. You’re immune.
In the first case, exposure to an invading poison led the body to become sensitized. In the
second, it led to immunity. Your ideavirus might behave in either way.
Yes, in general, the ideavirus adores a vacuum. It will spread faster and farther when no
similar virus has preceded it. The idea that you can follow a leader to great success might
work in the old economy (like Schick in razors or Burger King in fast food) but it clearly
isn’t a winning strategy in the new one.
But here’s the interesting special case: Sometimes, after being sensitized by one ideavirus, the
market is more susceptible to a new one. The failure of the Newton, for example, made early
adopters and sneezers more aware of the PDA concept, and it paved the way for the Palm to
succeed. The second Thai restaurant in a given town is more likely to turn a profit than the
first one. Michael Jordan wasn’t the first basketball hero by any means, but our desire to have
a hero, as sparked by earlier stars like Wilt Chamberlain and Larry Bird, made it easier for
Michael to walk in and fill a role that had to be filled by someone.
Unleashing the Ideavirus 186 http://www.ideavirus.com
But IsnÕt It Obvious?
One of the big challenges I faced with Permission Marketing and now with Unleashing the
Ideavirus is that a lot of stuff in these books seems pretty obvious. It’s obvious that marketing
to people who want to be marketed to is more effective than interrupting people who hate
you. It’s obvious that word of mouth is more powerful than ads. It’s obvious that the winner
takes all online. It’s obvious….
But precisely because it’s so obvious, it needs to be written about. Defined. Measured.
Because it’s so obvious, it’s easy to fall into a 100-year-old habit and start doing business the
old-fashioned (expensive but easy) way.
After all, if ideavirus marketing is so obvious, why does eToys need to raise $100 million in
venture capital to pay for old-fashioned advertising? Why are the TV networks having their
best year ever in advertising revenues? Why do really smart businesses suddenly turn stupid
when faced with ad opportunities like Planetfeedback.com?
Because to embrace ideavirus marketing techniques you also have to accept a change from
the status quo. And many of the executives who are now in charge made their way to the top
by embracing the status quo, not fighting it.
It’s much easier to raise venture money with a plan that says you’re going to spend $30
million or $60 million dollars on traditional advertising than it is with a plan that says you’ll
only spend $3 million but employ elegant but difficult techniques to get the word out.
It’s much easier to run the marketing department of a Fortune 500 company around the
command-and-control interruption techniques that got the company there in the first place
than it is to allow the customer to be in charge. And it’s far more difficult to devote your
research and development efforts to building ideaviruses than it is to stick with the
traditional incremental improvements.
Even marketers have heroes. Some kids grow up wanting to be like Sandy Koufax or Bart
Starr. But most of us imagined creating the next great TV commercial or building the next
Unleashing the Ideavirus 187 http://www.ideavirus.com
great brand. We envy the folks who built Coke or Nike or Starbucks or Star Wars. But all
these heroes found their success in a different world—in a factory-based, interruptionfocused
marketing environment.
Today, the world is suddenly very different. Almost without exception, every single win on
the consumer side of the Internet has been due to marketing, and the most effective part of
that marketing is about the ideavirus.
Hotmail, Yahoo!, eBay, Amazon, GeoCities, Broadcast.com, Google—all of them succeeded
because an ideavirus was unleashed and spread.
So, yes, the underlying tenets behind the ideavirus are obvious indeed. But executing against
them, fighting the status quo, getting it right—that’s not obvious at all.
Unleashing the Ideavirus 188 http://www.ideavirus.com
Your CompanyÕs Worst Enemy
She might just work in your office. She’s certainly underpaid. And not very well respected.
I’m talking about the folks who staff your customer service department. Admit it—you and
most of the folks in your company would be delighted if you never heard from or about
these guys and what they do. Their job is to make angry customers go away… quietly.
In the old days, this was a pretty easy job. After all, very few people went to all the trouble to
find your mailing address, get an envelope, get a stamp and write a letter. And if you sent the
writer a coupon good for a few bucks, well that was the end of the story.
Today, it’s very different. Planetfeedback (find them at http://www.planetfeedback.com) makes it
easy for angry customers to find you. And they can carbon-copy their congressman or the
FAA or ten friends.
With digitally augmented word of mouth, an angry customer can leave an online record…
one that lasts for centuries! There’s no statute of limitations online.
Take a look at
http://www.deja.com/products/at_a_glance/glance.xp?PCID=11819&PDID=32765. As I write
this, more than 90 people have ranked Flashcom, a provider of DSL services. Flashcom is
ranked as one of the worst providers of DSL service in the country. Actual comments:
Don’t make this mistake
This is a Mickey Mouse operation. Actually, that’s an insult to Mickey Mouse. Their tech
support is incompetent, their customer service is a front, and their technicians are
useless.
Impossible to get a live person through customer service. Sent over 7 emails and have
gotten back one reply. Had to cancel because of this and they charged me an additional
$150 for early termination. Completely bad attitude.
Unleashing the Ideavirus 189 http://www.ideavirus.com
Fraudulent Thieves
Took my $100 deposit (in October!), didn’t deliver a thing, and won’t give it back (they
deny having any record of it). Their “customer care” people use a wide variety of lies to
string you along. STAY AWAY FROM THESE PREDATORS!!!
Now, Flashcom may be running a first-rate organization. But there’s no way to tell that from
these comments. Question: How many expensive full-page ads will the marketing
department have to run to undo the damage that these public posts are going to do to their
brand for years to come?
Compare those reviews to these for Worldspy.com:
Pound for pound the best…
After trying AltaVista, I had about given up on the notion of a “useable” free ISP. I then
stumbled upon WorldSpy… I’ve never gotten a busy signal through WorldSpy and
consistently connect at 52kbps or higher. I’ve never been disconnected and love the
lack of an ad banner blocking my view.
Great so far
Thanks to all for your reviews that helped me find this service. I imagine it is tempting to
keep something like this a secret in order to keep good service for those in the know. I
know I considered that before I wrote this review! But I felt that as I benefited from
others’ recommendations, I owed it to the Deja community to share my experiences. I
have now been using WorldSpy for a few weeks, and have been pleased with it.
Now, we’re not comparing apples to apples here (Worldspy is free) but that only reinforces
the point. The 290 or more people who posted positive reviews are busy telling all their
friends about this service, spreading the positive news. (NB that Worldspy just tanked. An
ideavirus does you no good if you can’t stay in business!)
Unleashing the Ideavirus 190 http://www.ideavirus.com
Finally, take a look at the reviews for Big Planet. They have more than 1,000 reviews, but it
turns out that many of them are posted by Big Planet affiliates, looking to profit from
bringing on new users.
Thus, we see one ISP on the road to failure because it appears that they’ve refused to invest
any time, money or training in the way they treat customers. We see one that has used a very
different business model (free) and combined it with excellent quality and customer service,
and we see a third that’s busy paying promiscuous sneezers to spread the word. What’s your
company doing?
Instead of putting your weakest people into customer service, what would happen if you put
your best there? Instead of asking for reports on how much pain they’re alleviating, why not
let them tell you about how much joy and delight they’re adding to the customer service
experience?
American Express, ordinarily a terrific, data-driven marketer, has gone in almost entirely the
wrong direction on this issue. Every letter and every phone call is designed to reduce costs,
not to increase personal relationship and delight. And with the amplifying power now
available to sneezers, many companies, on the web and off, will either use this as a weapon or
be the victim of it.
Unleashing the Ideavirus 191 http://www.ideavirus.com
Step By Step, Ideavirus Tactics:
• Make it virusworthy.
If it’s not worth talking about, it won’t get talked about.
• Identify the hive.
You won’t get the full benefit of the ideavirus until you dominate your hive.
• Expose the idea.
Expose it to the right people, and do whatever you need to do to get those people
deep into the experience of the idea as quickly as possible. Pay them if necessary,
especially at the beginning. NEVER charge for exposure if you can help it.
• Figure out what you want the sneezers to say.
You’ve got to decide what you want the sneezers to say to the population. If you
don’t decide, either they’ll decide for you and say something less than optimal, or
they won’t even bother to spend the time.
• Give the sneezers the tools they need to spread the virus.
After you’ve got a potential sneezer, make it easy for him to spread the idea. Give
him a way to send your idea to someone else with one click. Let me join your
affiliate program in sixty seconds or less. Reward the people I spread the virus to,
so I don’t feel guilty for spreading it.
• Once the consumer has volunteered his attention, get permission.
The goal of the ideavirus marketer is to use the virus to get attention, then to
build a more reliable, permanent chain of communication so that further
enhancements and new viruses can be launched faster and more effectively, under
your control this time.
• Amaze your audience so that they will reinforce the virus and keep it growing.
Where are the Cabbage Patch Kids? Why do some viruses burn out more quickly
than others? The simplest reason is that marketers get greedy and forget that a
short-term virus is not the end of the process, it’s the beginning. By nurturing the
attention you receive, you can build a self reinforcing virus that lasts and lasts and
benefits all involved.
• Admit that few viruses last forever. Embrace the lifecycle of the virus.
Cats was a terrific success on Broadway. But even great shows don’t last forever.
By understanding that the needs of the virus change over time (and that the
Unleashing the Ideavirus 192 http://www.ideavirus.com
benefits received change as well) the marketer can match expenditures to the
highly leveraged moments.
Unleashing the Ideavirus 193 http://www.ideavirus.com
The Future Of The Ideavirus: What Happens When Everyone Does It?
Interruption marketing (the kind they do on TV) is doomed to fail, because each marketer
who enters the field has more to gain by adding to the clutter than they do by trying to make
the medium work for everyone else. It’s the classic Hudson River pollution problem—once a
big factory is polluting the river, you might as well too.
Permission marketing, on the other hand, is self-limiting. When people have had enough,
they’ll stop giving permission to marketers, and thus there will be no clutter crisis. Sure,
some folks will cheat by spamming or invading privacy or buying and selling names. But
societal pressure and a few key government regulations should stop the cheaters.
But what about the ideavirus? After it dawns on marketers that it’s working, won’t we all be
flooded by offers to make us promiscuous and an incredible flow of free this and free that?
You bet. I think a few things will occur:
1. The race goes to the swift. Just as Frank Zappa and David Bowie supercharged their
careers by getting on CD early, some marketers will fill vacuums and enjoy profits for years
to come. Latecomers will get hurt.
2. The cost of spreading a virus will increase. The bounties to turn people promiscuous will
increase. The benefit to powerful sneezers will increase. When there’s huge demand for
recommendations, marketers will have to pay more to get them.
3. There will be a significant benefit to becoming a powerful sneezer. Everyone will want to
be Esther Dyson or Walter Cronkite, because that sort of genuine credential can be turned
into a profit for years and years. Thus, we’ll see fewer institutional efforts and more
individuals (free agents) who figure out that they can profit mightily by spreading their own
viruses (this manifesto is a living example of that technique).
4. It’s going to be noisy and loud and cluttered as we transition, with a few huge winners and
many satisfied marketers who dominate a hive but don’t necessarily tip. After that, once the
various media settle down, an equilibrium will return and (hopefully) the good stuff will win.
Unleashing the Ideavirus 194 http://www.ideavirus.com
Good luck. Tell me how it goes for you! Sethgodin@ideavirus.com
STEAL THIS IDEA!
Here’s what you can do to spread the word about Unleashing the Ideavirus:
1. Send this file to a friend (it’s sort of big, so ask first).
2. Send them a link to http://www.ideavirus.com so they can download it themselves.
3. Visit http://www.fastcompany.com/ideavirus to read the Fast Company article.
4. Buy a copy of the hardcover book at
http://www.amazon.com/exec/obidos/ASIN/0970309902/permissionmarket.
5. Print out as many copies as you like.
Unleashing the Ideavirus 195 http://www.ideavirus.com
Acknowledgments
First, some professional sneezing (you can find all these links at http://www.ideavirus.com as well):
1. If you ever get the chance to have Red Maxwell design something for you, grab it. He’s an
extraordinary talent, and even better, a brilliant project manager and a great friend. You can
reach Red at red@designfactorynet.com.
2. One of the best ways to start and spread an ideavirus is to have your company write a
book about it. Books are still the most leveraged way to get powerful sneezers to understand
your ideas and spread them. And the partners at Lark Productions—Lisa DiMona, Karen
Watts and Robin Dellabough (robinlark@mindspring.com) are among the best I’ve ever
found at turning ideas into books. In the past twelve months, they’ve handled the words of
Kinko’s, the Dalai Lama (who wrote the foreword for Bo Lozoff’s inspiring new book) and
me. How cool is that?
3. If you haven’t been reading Fast Company, don’t panic. You can catch up on what you’ve
missed at http://www.fastcompany.com. In a world of hype and shallowness, you’ll find very little
of either here.
4. Malcolm Gladwell’s book, The Tipping Point, will radically shift your thinking. That’s a
good thing. Find this and his other writings at http://www.gladwell.com.
5. A lot of people haven’t kept up with Tom Peters since they bought his very first book.
Don’t hesitate! I reread his stuff as often as I can. Find it at http://www.tompeters.com.
6. I also recommend four other great writers and thinkers. Chris Meyer co-wrote Blur
among other things, and despite his protestations, is beginning to share my hairline. Jay
Levinson is the original marketing bigthinker, and you’re selling yourself short if you haven’t
picked up his books lately. And finally, Don Peppers and Martha Rogers who continue to
be way ahead of me and everyone else in how they’re deconstructing and reconstructing the
way we think about marketing.
Unleashing the Ideavirus 196 http://www.ideavirus.com
7. The guys at Peanut Press are terrific. If you’ve got a Palm, point your browser to
http://www.peanutpress.com and go get some books for it. Thanks, Mike!
I’d like also like to thank Susan Greenspan Cohen, Bob Dorf, Louise Wannier, Alison
Heisler and the wonderful people at Fast Company (especially the incredible Alan Webber)
for advice, insight and encouragement as I plowed through this manifesto. And thanks to my
role model and friend Lester Wunderman.
Jerry Colonna, Fred Wilson, Bob Greene, Tom Cohen, Seth Goldstein and their friends,
partners and associates at Flatiron Partners have been generous enough to give me a platform
and a lab to mess with a lot of new thinking. They certainly keep me on my toes, and are
nice enough to sit through my endless slide shows. Fred Wilson and Tom Cohen, though,
deserve extra thanks. Without the two of them, my internet company would have never
thrived, and you wouldn’t be reading this book. Steve Kane and Stu Roseman are, amazingly
enough, about to throw themselves into this maelstrom. Can’t wait.
Thanks to Don Epstein and David Evenchick at the Greater Talent Network in New York
City for believing in me and then being true to their word and keeping me busy.
For the last year, two people have done everything to keep things in perspective for me…
Lisa Gansky and my Dad. Thanks, guys.
Of course, as always, the real joy in my life comes from my wife Helene and our little
entrepreneurs, Alex and Max.
Unleashing the Ideavirus 197 http://www.ideavirus.com
Script Convert-WindowsImage.ps1 – WIM2VHD for Windows 8!
Whats Coming in SharePoint 2013 — Redmond Developer News
What’s Coming in SharePoint 2013
Many SharePoint 2013 features are already available for testing in the Office 365 previews.
Microsoft offered more details on the improvements in its SharePoint collaboration platform, which is slated to be released as a service and a server in 2013.
Many SharePoint 2013 features are already available for testing in the Office 365 previews, which the company released last month.
Jared Spataro, senior director for SharePoint product management at Microsoft, offered a quick tour of some highlights in the new SharePoint, during a demonstration for technology reviewers on Tuesday. According to Spataro, the underlying architecture hasn’t changed very much with this release, but the company has added some upgrades and I/O performance improvements.
The user experience has also been updated. Users of the new SharePoint will see a flat, spare “modern” UI, with a narrow menu bar at the top.
Microsoft also highlighted the collaboration and social networking aspects of SharePoint, which are among the product’s top uses, according to a Forrester Research survey. However, nothing was really said during the talk about Microsoft’s Yammer acquisition, which will bring Yammer’s enterprise social networking technologies across SharePoint, Office 365, Microsoft Dynamics and Skype.
Better Tagging
In general, Microsoft has improved the metadata aspects in the new SharePoint, allowing users to tag content while posting, Spataro said. People are considered first-class objects in SharePoint. They can be followed, by SharePoint users, but it’s also possible to follow documents, sites and tags across a Web site. SharePoint also points users to content based on a “suggested sites” feature. Users can hover over user profiles and get access to their contact cards, which bring in profile information, including info from LinkedIn and Facebook social networking pages.
My Site in the new SharePoint has its functionality split into three hubs: Newsfeed, SkyDrive Pro and Sites, as explained in this SharePoint team blog. The Newsfeed application has a sort of Facebook-like appearance with photos and e-mail threads, as well as a “Like” button. The Sites application is a tracker of site locations that are important to the user. SkyDrive Pro is a cloud-based storage place for files that works with SharePoint. Spataro said that SkyDrive Pro replaces what used to be called “SharePoint Documents” or “My Documents” in earlier editions, adding that it had been renamed to highlight Microsoft’s investments in consumer cloud storage. Microsoft also offers a free SkyDrive service for consumers.
SkyDrive Pro Replacing SharePoint Workspaces
SkyDrive Pro provides storage, synchronization and sharing capabilities for users. Cloud-based apps will sync to the desktop app by just clicking on the desktop. There’s also drag-and-drop file uploading capabilities from the desktop to the browser-based app, and even drag-and-drop capabilities within the browser-based app, which Spataro called “a new modality for people.” He claimed that he works more in Web apps these days because of the richness of the applications. SkyDrive Pro works with various Office Web Apps, such as Word, Excel, PowerPoint and OneNote.
SkyDrive Pro has access to all of the new SharePoint capabilities. “All of the content manageable in SharePoint can be managed in SkyDrive Pro,” Spataro said.
The fate of SharePoint Workspace (previously known as “Groove”) in SharePoint 2013 got cleared up during the Q&A session. Groove was the invention of former Microsoft Chief Software Architect Ray Ozzie, whose retirement was announced in October 2010.
“SharePoint Workspace was the way that we did document sync and offline access with the previous version of SharePoint,” Spataro explained. “And in fact, SharePoint Workspace was the evolution of the Groove client. The document store, share and sync capabilities that I showed you are actually based on the next evolution of that SharePoint Workspace. We actually used the underlying component that came from Groove, part of the sync engine, to do it. And going forward, our strategy will be to focus on SkyDrive Pro that I showed you today.”
He added that people can still get access to SharePoint Workspace, “but our go-forward strategy investment will be focused on SkyDrive Pro.”
Team Site Gets OneNote
The Team Site is considered the “center of gravity for people in SharePoint,” Spataro said, and Microsoft has enhanced it by adding a centralized OneNote built into it. OneNote is a Microsoft Office application that lets users store photos and text in a sort of digital scrapbook. The OneNote that’s part of Team Site is capable of synchronization, and it can be viewed on various mobile devices with “the same rich view,” Spataro contended. The Team Site also has its own newsfeed, which will sync up with a user’s main Newsfeed. Users tend to use this newsfeed service as a replacement for e-mail, he added.
Spataro said that the new SharePoint is about task completion and using social interactions to do work, so there’s a My Tasks interface that users can plot against a timeline. It’s capable of drag-and-drop operations, so users can create a list of tasks in Excel and drop the file into tasks lists. It’s possible to edit in real time and assign tasks to different people. The whole timeline is viewable in a “project summary” page. Spataro suggested this approach is an improvement over past SharePoint releases where it was “tough to track things.”
There are some SharePoint business intelligence improvements enabled by SQL Server 2012. For instance, the Excel Web App can be used to display a Power View executive dashboard, which graphically displays data. It allows slice-and-dice operations to be performed using the data or the data can be plotted over time. With these capabilities, Spataro said that Microsoft is bringing together social, task management and business insights.
Lastly, Spataro pointed to the Microsoft partner ecosystem and the extra support users can get though SharePoint apps. The apps are available in the SharePoint library or they can be downloaded from the SharePoint Store.
Spataro said he left out a lot in his presentation, noting that FAST search in the new SharePoint now has e-discovery capabilities across SharePoint, Exchange and Lync file shares. Search was one of the SharePoint features that participants in Forrester’s survey said they least liked. However, it’s apparently improved in the new SharePoint.
An overview of the new SharePoint features was described earlier in this blog post by Jeff Teper, corporate vice president of SharePoint.
About the Author
Kurt Mackie is online news editor, Enterprise Group, at 1105 Media Inc.




















































































