Your resource quota is 300 server resources

Use this workbook as you plan your upgrade process to ensure that you have all the information that you need before you begin.

Fill out each worksheet in this workbook to get a complete understanding of the servers, services, Web applications, sites, and customizations in your environment. Some of this information is generated for you when you run the pre-upgrade checker tool and can be copied from the XML report that the tool generates. You can also gather information by using the Stsadm -o enumallwebs command. These tools have been updated to include additional functionality in the October 2009 Cumulative Update (such as which sites use a feature and information about large lists).

After running these tools, you will have a preliminary list of the components in your environment. When you perform a trial upgrade, you can verify that you have a complete list of the components.

When you perform your actual upgrade, you can use this workbook as a checklist to verify that you have upgraded all the components in your environment. You can also add to this workbook if you have additional post-upgrade tasks to perform (such as identifying missing server files or following up on sites that were not upgraded correctly).

Link to the .xls on the Microsoft Download Center

Here is a great presentation from CriticalPath Training outlining the SharePoint 2010 Developer Roadmap and PowerShell Integration.

The presenter is Ted Pattison.

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

You can use Windows PowerShell cmdlets to help perform an upgrade from an earlier version of Microsoft SharePoint Server 2010.

The following cmdlets are available for Beta.

Cmdlet name

Test-SPContentDatabase

To download the SharePointProductsCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

Visio Graphics Service is a service in Microsoft SharePoint Server 2010 that users can use to view published Visio diagrams. The service also refreshes published Visio diagrams that are connected to supported data sources.

All Visio Graphics Service settings will support backup and recovery, regardless of whether there is a UI setting. This means all global settings will support backup and restore operations.

The Visio Graphics Service has Windows PowerShell functionality that you can use to provision a new instance, manage and configure available data sources, manage and configure a list of safe data providers, and configure all the global settings of the service.

The following cmdlets are available for Beta.

Cmdlet Name

Get-SPVisioExternalData

Get-SPVisioPerformance

Set-SPVisioPerformance

Get-SPVisioSafeDataProvider

New-SPVisioSafeDataProvider

Remove-SPVisioSafeDataProvider

Set-SPVisioSafeDataProvider

Get-SPVisioServiceApplication

New-SPVisioServiceApplication

Set-SPVisioServiceApplication

Get-SPVisioServiceApplicationProxy

New-SPVisioServiceApplicationProxy

To download the VisioServicesCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

Visio Graphics Service is a service in Microsoft SharePoint Server 2010 that users can use to view published Visio diagrams. The service also refreshes published Visio diagrams that are connected to supported data sources.

All Visio Graphics Service settings will support backup and recovery, regardless of whether there is a UI setting. This means all global settings will support backup and restore operations.

The Visio Graphics Service has Windows PowerShell functionality that you can use to provision a new instance, manage and configure available data sources, manage and configure a list of safe data providers, and configure all the global settings of the service.

The following cmdlets are available for Beta.

Cmdlet Name

Get-SPVisioExternalData

Get-SPVisioPerformance

Set-SPVisioPerformance

Get-SPVisioSafeDataProvider

New-SPVisioSafeDataProvider

Remove-SPVisioSafeDataProvider

Set-SPVisioSafeDataProvider

Get-SPVisioServiceApplication

New-SPVisioServiceApplication

Set-SPVisioServiceApplication

Get-SPVisioServiceApplicationProxy

New-SPVisioServiceApplicationProxy

To download the VisioServicesCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

Search is composed of several components, all of which provide specific functionality that is required for Search to operate. These components can be configured by using Windows PowerShell cmdlets.

The following cmdlets are available for Beta.

Administration

Cmdlet name

Get-SPEnterpriseSearchAdminComponent

Set-SPEnterpriseSearchAdminComponent

Crawling

Cmdlet name

Get-SPEnterpriseSearchCrawlComponent

Get-SPEnterpriseSearchCrawlContentSource

Get-SPEnterpriseSearchCrawlCustomConnector

Get-SPEnterpriseSearchCrawlDatabase

Get-SPEnterpriseSearchCrawlExtension

Get-SPEnterpriseSearchCrawlMapping

Get-SPEnterpriseSearchCrawlRule

Get-SPEnterpriseSearchCrawlTopology

New-SPEnterpriseSearchCrawlComponent

New-SPEnterpriseSearchCrawlContentSource

New-SPEnterpriseSearchCrawlCustomConnector

New-SPEnterpriseSearchCrawlDatabase

New-SPEnterpriseSearchCrawlExtension

New-SPEnterpriseSearchCrawlMapping

New-SPEnterpriseSearchCrawlRule

New-SPEnterpriseSearchCrawlTopology

Remove-SPEnterpriseSearchCrawlComponent

Remove-SPEnterpriseSearchCrawlContentSource

Remove-SPEnterpriseSearchCrawlCustomConnector

Remove-SPEnterpriseSearchCrawlDatabase

Remove-SPEnterpriseSearchCrawlExtension

Remove-SPEnterpriseSearchCrawlMapping

Remove-SPEnterpriseSearchCrawlRule

Remove-SPEnterpriseSearchCrawlTopology

Set-SPEnterpriseSearchCrawlContentSource

Set-SPEnterpriseSearchCrawlDatabase

Set-SPEnterpriseSearchCrawlRule

Set-SPEnterpriseSearchCrawlTopology

Service Application

Cmdlet name

Get-SPEnterpriseSearchService

Get-SPEnterpriseSearchServiceApplication

Get-SPEnterpriseSearchServiceApplicationProxy

Get-SPEnterpriseSearchServiceInstance

New-SPEnterpriseSearchServiceApplication

New-SPEnterpriseSearchServiceApplicationProxy

Remove-SPEnterpriseSearchServiceApplication

Remove-SPEnterpriseSearchServiceApplicationProxy

Restore-SPEnterpriseSearchServiceApplication

Set-SPEnterpriseSearchService

Set-SPEnterpriseSearchServiceApplication

Set-SPEnterpriseSearchServiceApplicationProxy

Set-SPEnterpriseSearchServiceInstance

Start-SPEnterpriseSearchServiceInstance

Stop-SPEnterpriseSearchServiceInstance

Upgrade-SPEnterpriseSearchServiceApplication

Querying

Cmdlet name

Get-SPEnterpriseSearchQueryAuthority

Get-SPEnterpriseSearchQueryComponent

Get-SPEnterpriseSearchQueryDemoted

Get-SPEnterpriseSearchQueryKeyword

Get-SPEnterpriseSearchQueryScope

Get-SPEnterpriseSearchQueryScopeRule

Get-SPEnterpriseSearchQuerySuggestionCandidates

Get-SPEnterpriseSearchQueryTopology

Get-SPEnterpriseSearchRankingModel

Get-SPEnterpriseSearchSecurityTrimmer

New-SPEnterpriseSearchQueryAuthority

New-SPEnterpriseSearchQueryComponent

New-SPEnterpriseSearchQueryDemoted

New-SPEnterpriseSearchQueryKeyword

New-SPEnterpriseSearchQueryScope

New-SPEnterpriseSearchQueryScopeRule

New-SPEnterpriseSearchQueryTopology

New-SPEnterpriseSearchRankingModel

New-SPEnterpriseSearchSecurityTrimmer

Remove-SPEnterpriseSearchQueryAuthority

Remove-SPEnterpriseSearchQueryComponent

Remove-SPEnterpriseSearchQueryDemoted

Remove-SPEnterpriseSearchQueryKeyword

Remove-SPEnterpriseSearchQueryScope

Remove-SPEnterpriseSearchQueryScopeRule

Remove-SPEnterpriseSearchQueryTopology

Remove-SPEnterpriseSearchRankingModel

Remove-SPEnterpriseSearchSecurityTrimmer

Restart-SPEnterpriseSearchQueryComponent

Set-SPEnterpriseSearchQueryAuthority

Set-SPEnterpriseSearchQueryComponent

Set-SPEnterpriseSearchQueryKeyword

Set-SPEnterpriseSearchQueryScope

Set-SPEnterpriseSearchQueryScopeRule

Set-SPEnterpriseSearchQueryTopology

Set-SPEnterpriseSearchRankingModel

Metadata

Cmdlet name

Get-SPEnterpriseSearchMetadataCategory

Get-SPEnterpriseSearchMetadataCrawledProperty

Get-SPEnterpriseSearchMetadataManagedProperty

Get-SPEnterpriseSearchMetadataMapping

New-SPEnterpriseSearchMetadataCategory

New-SPEnterpriseSearchMetadataCrawledProperty

New-SPEnterpriseSearchMetadataManagedProperty

New-SPEnterpriseSearchMetadataMapping

Remove-SPEnterpriseSearchMetadataCategory

Remove-SPEnterpriseSearchMetadataManagedProperty

Remove-SPEnterpriseSearchMetadataMapping

Set-SPEnterpriseSearchMetadataCategory

Set-SPEnterpriseSearchMetadataCrawledProperty

Set-SPEnterpriseSearchMetadataManagedProperty

Set-SPEnterpriseSearchMetadataMapping

Topology

Cmdlet name

Import-SPEnterpriseSearchTopology

Export-SPEnterpriseSearchTopology

General

Cmdlet name

Get-SPEnterpriseSearchIndexPartition

Get-SPEnterpriseSearchLanguageResourcePhrase

Get-SPEnterpriseSearchPropertyDatabase

Get-SPEnterpriseSearchSiteHitRule

New-SPEnterpriseSearchLanguageResourcePhrase

New-SPEnterpriseSearchPropertyDatabase

New-SPEnterpriseSearchSiteHitRule

Remove-SPEnterpriseSearchLanguageResourcePhrase

Remove-SPEnterpriseSearchPropertyDatabase

Remove-SPEnterpriseSearchSiteHitRule

Set-SPEnterpriseSearchIndexPartition

Set-SPEnterpriseSearchPropertyDatabase

Microsoft FAST Search Server 2010 for SharePoint

Microsoft FAST Search Server 2010 for SharePoint can replace SharePoint Server search features in environments where scale and performance requirements exceed the capabilities of SharePoint Server search. FAST Search Server 2010 for SharePoint can be deployed across multiple servers for redundancy and to increase performance and capacity. Deployment and management take place primarily through command-line operations — not the SharePoint Central Administration Web site — and can be scripted by using Windows PowerShell. FAST Search Server 2010 for SharePoint is only available with a SharePoint Server Enterprise Client Access License (CAL).

The following table describes the cmdlets for FAST Search Server 2010 for SharePoint.

Cmdlet name

Get-SPEnterpriseSearchExtendedConnectorProperty

Set-SPEnterpriseSearchExtendedConnectorProperty

Set-SPEnterpriseSearchExtendedQueryProperty

Get-SPEnterpriseSearchExtendedQueryProperty

Get-SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition

To download the SearchCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta(http://go.microsoft.com/fwlink/?LinkId=179124).

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

In Microsoft SharePoint Server 2010, the User Profile Service is used to store and process information about users. This information is stored as a collection of user profile properties per user. The user information must be imported into the user profile store before it can be used by various personalization-related features and people search. These properties can be imported from line-of-business applications and directory services (primarily Active Directory directory service and Lightweight Directory Access Protocol (LDAP)).

In SharePoint Server 2010, the use of social tagging, expertise tagging, and profile synchronization are new features.

SharePoint Server 2010 provides an enterprise-wide repository for storing social and expertise tags and for associating those tags with a user’s profile. Administrators can control who can tag items on a given site, decide which tags can be used, and delete tags prior to a specific date or based on a specific user profile ID. Tagging relies on the Managed Metadata Service and can be enabled by using either the UI or Windows PowerShell cmdlets.

Profile synchronization synchronizes data in the SharePoint profile store with profile information contained in directory services across the enterprise, such as Active Directory or LDAP. After a connection to the appropriate directory service has been set up, profile synchronization can be scheduled to run on a regular basis.

You can use User Profile Service Windows PowerShell cmdlets to create and configure the User Profile Service and profile tags, and to configure permissions and all global settings for the User Profile Service.

The following cmdlets are available for Beta.

Cmdlet name

New-SPProfileServiceApplication

Set-SPProfileServiceApplication

New-SPProfileServiceApplicationProxy

Set-SPProfileServiceApplicationProxy

Add-SPProfileServiceApplicationTenant

Remove-SPProfileServiceApplicationTenant

Set-SPProfileServiceApplicationTenant

To download the UserProfileCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

In Microsoft SharePoint Server 2010, the Secure Store service replaces the single sign-on (SSO) service that was used in Microsoft Office SharePoint Server 2007. The Secure Store Service is a claims-aware authentication service that includes a secure database for storing credentials that are associated with application IDs. These application IDs can be used to authorize access to external data sources. The Secure Store Service provides the capability of securely storing credentials and associating them to specific identities or a group of identities. A common scenario for Secure Store Servcie is an application trying to authenticate against a system in which the current user is known by a different name or has a different account for authentication. When used with Microsoft Business Connectivity Services, the Secure Store Service provides a means to authenticate against external data sources.

When you use Windows PowerShell cmdlets, you can create and configure a Secure Store Service instance, configure the settings of a credentials database, and configure all global settings of the Secure Store Service.

The following cmdlets are available for Beta.

Cmdlet name

Clear-SPSecureStoreCredentialMapping

Update-SPSecureStoreCredentialMapping

Disable-SPSingleSignOn

Get-SPSecureStoreApplication

New-SPSecureStoreApplication

Remove-SPSecureStoreApplication

Set-SPSecureStoreApplication

New-SPSecureStoreServiceApplication

Set-SPSecureStoreServiceApplication

New-SPSecureStoreTargetApplication

New-SPSecureStoreTargetApplicationField

Update-SPSecureStoreCredentialMapping

Upgrade-SPSingleSignOnDatabase

Update-SPSecureStoreGroupCredentialMapping

Update-SPSecureStoreMasterKey

Update-SPSecureStoreApplicationServerKey

To download the SecureStoreCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

There are Windows PowerShell cmdlets used to support a session state and the state service.

The following cmdlets are available for Beta.

Cmdlet name

Disable-SPSessionStateService

Dismount-SPStateServiceDatabase

Enable-SPSessionStateService

Get-SPSessionStateService

Get-SPStateServiceApplication

Get-SPStateServiceApplicationProxy

Get-SPStateServiceDatabase

Initialize-SPStateServiceDatabase

Mount-SPStateServiceDatabase

New-SPStateServiceApplication

New-SPStateServiceApplicationProxy

New-SPStateServiceDatabase

Remove-SPStateServiceDatabase

Resume-SPStateServiceDatabase

Set-SPSessionStateService

Set-SPStateServiceApplication

Set-SPStateServiceApplicationProxy

Set-SPStateServiceDatabase

Suspend-SPStateServiceDatabase

To download the StateServiceCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).

Updated: 2009-12-14

[This article is pre-release documentation and is subject to change in future releases.]

InfoPath Services is a service in Microsoft SharePoint Server 2010 that you can use to view, edit, and configure a form template in Microsoft InfoPath 2010 or viewed within a Web browser.

All InfoPath Services settings will support backup and recovery regardless of whether there is a UI setting in the Central Administration Web site. However, backup and recovery only apply to the service and administrative-level settings; end-user content is not backed up as part of this process.

The following cmdlets are available for Beta.

Cmdlet name
Description

Get-SPDataConnectionFile

Get-SPDataConnectionFileDependent

Install-SPDataConnectionFile

Set-SPDataConnectionFile

Uninstall-SPDataConnectionFile

Add-SPInfoPathUserAgent

Get-SPInfoPathUserAgent

Remove-SPInfoPathUserAgent

Disable-SPInfoPathFormTemplate

Enable-SPInfoPathFormTemplate

Get-SPInfoPathFormTemplate

Install-SPInfoPathFormTemplate

Set-SPInfoPathFormTemplate

Start-SPInfoPathFormTemplate

Stop-SPInfoPathFormTemplate

Test-SPInfoPathFormTemplate

Uninstall-SPInfoPathFormTemplate

Update-SPInfoPathFormTemplate

Export-SPInfoPathAdministrationFiles

Import-SPInfoPathAdministrationFiles

Get-SPInfoPathFormsService

Set-SPInfoPathFormsService

Get-SPInfoPathWebServiceProxy

Set-SPInfoPathWebServiceProxy

Update-SPInfoPathUrl

Update-SPInfoPathUserFileUrl

To download the InfoPathCmdlets.chm file, see Windows PowerShell for SharePoint Server 2010 Beta (http://go.microsoft.com/fwlink/?LinkId=179124).