SharePoint 2013 Hardware Requirements - SharePoint 15

Hey there, MS published the SP 2013 hardware and software requirements (preview document).

If your current laptop, desktop, server doesn't proudly accept 24GB of RAM or more, you better start considering an additional investment into new RAM modules, or even machine...

You can read more about it on Technet's website...
http://technet.microsoft.com/en-us/library/cc262485(office.15).aspx

In this article:

• Overview
  
• Hardware requirements—web servers, application servers, and single server installations
  
• Hardware requirements—database servers
  
• Software requirements
  
• Optional software
  
• Links to applicable software
  
• Prerequisite installer operations and command-line options
  

Important:

The information in this article applies to SharePoint Foundation 2013 Preview and SharePoint Server 2013 Preview. For information about features that each version supports, see SharePoint 2013 Product Page. In addition, the hardware requirement values in this article are based on test results from SharePoint 2010 Products and may not represent the final values for SharePoint 2013 Preview. This article will be updated with appropriate values and republished when SharePoint 2013 Preview is released.

Overview

SharePoint 2013 Preview provides for several installation scenarios. Currently, these installations include single server with built-in database installations, single-server farm installations, and multiple-server farm installations. This article describes the hardware and software requirements for SharePoint 2013 Preview in each of these scenarios.

Hardware and software requirements for other SharePoint 2013 Preview capabilities

If you plan to use capabilities that are offered through SharePoint 2013 Preview or through other integration channels, such as SQL Server or Exchange Server, you also need to meet the hardware and software requirements that are specific to that capability. The following list provides links to hardware and software requirements for some SharePoint 2013 Preview capabilities:

• Hardware and software requirements (Project Server 2013)
  Pay additional attention to the supported web browsers for Project Web App users.
  
• Software requirements for business intelligence (SharePoint 2013 Preview)
  

Hardware requirements—web servers, application servers, and single server installations

The values in the following table are minimum values for installations on a single server with a built-in database and for web and application servers that are running SharePoint 2013 Preview in a multiple server farm installation. For information about the deployment types that are used in this table, see the SharePoint 2010 Products: Deployment model. You can download this model from the Installation and deployment for SharePoint 2013 IT Pros Resource Center.
For all installation scenarios, you must have sufficient hard disk space for the base installation and sufficient space for diagnostics such as logging, debugging, creating memory dumps, and so on. For production use, you must also have additional free disk space for day-to-day operations. In addition, maintain two times as much free space as you have RAM for production environments. For more information, see Capacity management and sizing for SharePoint Server 2010.

Installation Scenario	Deployment type and scale	RAM	Processor	Hard disk space
Single server with a built-in database or single server that uses SQL Server	Development or evaluation installation of SharePoint Foundation 2013 Preview	8 GB	64-bit, 4 cores	80 GB for system drive
Single server with a built-in database or single server that uses SQL Server	Development or evaluation installation of SharePoint Server 2013 Preview	24 GB	64-bit, 4 cores	80 GB for system drive
Web server or application server in a three-tier farm	Pilot, user acceptance test, or production deployment of SharePoint Server 2013 Preview	12 GB	64-bit, 4 cores	80 GB for system drive

Hardware requirements—database servers

The requirements in the following table apply to database servers in environments that have multiple servers in the farm.

Component	Minimum requirement
Processor	64-bit, 4 cores for small deployments 64-bit, 8 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). These values are larger than those recommended as the minimum values for SQL Server because of the distribution of data that is required for a SharePoint 2013 Preview environment. For more information about SQL Server system requirements, see Hardware and Software Requirements for Installing SQL Server 2008 R2.
Hard disk	80 GB for system drive Hard disk space depends on how much content that you have in your deployment. For information about how to estimate the amount of content and other databases for your deployment, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2010).

Software requirements

The requirements in the following section apply to the following installations:

• Single server with built-in database
  
• Server farm with a single server in the farm
  
• Server farm with multiple servers in the farm
  

Important:
SharePoint 2013 Preview does not support single label domain names. For more information, see Information about configuring Windows for domains with single-label DNS names.

The Microsoft SharePoint Products Preparation Tool can assist you in the installation of the software prerequisites for SharePoint 2013 Preview. Ensure that you have an Internet connection, because some prerequisites are installed from the Internet. For more information about how to use the Microsoft SharePoint Products Preparation Tool, see Install SharePoint 2013 Preview on a single server with SQL Server and Install SharePoint 2013 Preview across multiple servers for a three-tier farm.

Minimum software requirements

This section provides minimum software requirements for each server in the farm.
Minimum requirements for a database server in a farm:

• The 64-bit edition of SQL Server 2008 R2 Service Pack 1.
  For more information about the benefits of using SQL Server with SharePoint 2013 Preview, see SQL Server 2008 R2 and SharePoint 2010 Products: Better Together white paper.
  
• The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard, Enterprise, or Datacenter.
  
• KB 2554876 (http://support.microsoft.com/kb/2554876)
  
• Windows KB -IIS Configuration Changes KB 2708075 (http://support.microsoft.com/kb/2708075)
  
• Microsoft .NET Framework version 4.5 Release Candidate (RC)
  

Minimum requirements for a single server with built-in database:

• The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard, Enterprise, or Datacenter.
  
• KB 2554876 (http://support.microsoft.com/kb/2554876)
  
• Windows KB -IIS Configuration Changes KB 2708075 (http://support.microsoft.com/kb/2708075)
  
• The Setup program installs the following prerequisite for a single server with built-in database:
  
  • Microsoft SQL Server 2008 R2 SP1 - Express Edition
    
• The Microsoft SharePoint Products Preparation Tool installs the following prerequisites for a single server with built-in database:
  
  • Web Server (IIS) role
    
  • Application Server role
    
  • Microsoft .NET Framework version 4.5 Release Candidate (RC)
    
  • SQL Server 2008 R2 SP1 Native Client
    
  • Microsoft WCF Data Services 5.0
    
  • Microsoft Information Protection and Control Client (MSIPC)
    
  • Microsoft Sync Framework Runtime v1.0 SP1 (x64)
    
  • Windows Management Framework 3.0 Release Candidate (RC) which includes Windows PowerShell 3.0
    
  • Windows Identity Foundation (WIF) 1.0 and Microsoft Identity Extensions (previously named WIF 1.1).
    
  • Windows Server AppFabric
    
  • Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)
    

Minimum requirements for front-end web servers and application servers in a farm:

• The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard, Enterprise, or Datacenter.
  
• KB 2554876 (http://support.microsoft.com/kb/2554876)
  
• Windows KB -IIS Configuration Changes KB 2708075 (http://support.microsoft.com/kb/2708075)
  
• The Microsoft SharePoint Products Preparation Tool installs the following prerequisites for front-end web servers and application servers in a farm:
  
  • Web Server (IIS) role
    
  • Application Server role
    
  • Microsoft .NET Framework version 4.5 Release Candidate (RC)
    
  • SQL Server 2008 R2 SP1 Native Client
    
  • Microsoft WCF Data Services 5.0
    
  • Microsoft Information Protection and Control Client (MSIPC)
    
  • Microsoft Sync Framework Runtime v1.0 SP1 (x64)
    
  • Windows Management Framework 3.0 Release Candidate (RC) which includes Windows PowerShell 3.0
    
  • Windows Identity Foundation (WIF) 1.0 and Microsoft Identity Extensions (previously named WIF 1.1)
    
  • Windows Server AppFabric
    
  • Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)
    

Minimum requirements for client computers

• A supported browser. For more information, see Plan browser support in SharePoint 2013 Preview.
  

Optional software

Environment	Optional software
Single server with built-in database, front-end web servers, and application servers in a farm	.NET Framework Data Provider for SQL Server (part of Microsoft .NET Framework) .NET Framework Data Provider for OLE DB (part of Microsoft .NET Framework) Windows Azure Workflow 1.0 Preview. This server is pre-release software that is available from the download center. This server can be installed on a dedicated computer. Microsoft SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint Technologies. This add-in is used by Access Services for SharePoint 2013 Preview. Microsoft Data Services for .NET Framework 4 and Silverlight 4 (formerly ADO.NET Data Services) Exchange Web Services Managed API, version 1.2 Windows 7. For more information, see Setting Up the Development Environment for SharePoint Server. Microsoft SQL Server 2008 R2 Remote Blob Store which is part of the Microsoft SQL Server 2008 R2 Feature Pack. SQL Server 2008 R2 Analysis Services ADOMD.NET If you are running a geo-distributed deployment and your servers are running Windows Server 2008 R2, then installing KB 2472264 can optimize network latency in a dedicated datacenter network. For more information, and to download the software, see You cannot customize some TCP configurations by using the netsh command in Windows Server 2008 R2 For additional requirements for Business Intelligence, see Software requirements for business intelligence (SharePoint 2013 Preview).
Client computer	Office 2013 Preview. For more information, see Microsoft Office on the download center. Silverlight 3.

Links to applicable software

To install Windows Server 2008 R2 SP1, Windows Server 2012 Release Candidate, SQL Server, or SharePoint 2013 Preview, you can go to the web sites that are listed in this section. You can install most software prerequisites through the SharePoint 2013 Preview Start page. The software prerequisites are also available from web sites that are listed in this section. You can enable the Web Server (IIS) role and the Application Server role in Server Manager. Office 2013 Preview is available for download from the download center.
In scenarios where installing prerequisites directly from the Internet is not possible you can download the prerequisites and then install them from a network share. For more information, see Install prerequisites for SharePoint 2013 Preview from a network share.

• Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) (KB 976932)
  
• KB 2554876 (http://support.microsoft.com/kb/2554876)
  
• Windows KB -IIS Configuration Changes KB 2708075 (http://support.microsoft.com/kb/2708075)
  
• Windows Server 2012 release candidate, Datacenter Edition, Standard Edition
  
• Microsoft SQL Server 2008 R2 Service Pack 1
  
• Microsoft .NET Framework version 4.5 Release Candidate (RC)
  
• Microsoft SQL Server 2008 R2 SP1 - Express Edition
  
• WCF Data Services 5.0 for OData
  
• Microsoft Information Protection and Control Client (MSIPC)
  
• Windows Management Framework 3.0 Release Candidate (RC) which includes Windows PowerShell 3.0
  
• Microsoft Sync Framework Runtime v1.0 SP1 (x64)
  
• Windows Identity Foundation 1.0 for Windows Server 2008 R2
  
• Windows Identity Extensions for Windows Server 2008 R2
  
• Microsoft SQL Server 2008 R2 Feature Pack which includes the Microsoft SQL Server 2008 R2 SP1 Native Client and the SQL Server Remote BLOB Store
  
• Microsoft SQL Server 2008 R2 SP1 Feature pack which includes Microsoft SQL Server 2008 R2 ADOMD.NET
  
• Microsoft Silverlight 3
  
• Exchange Web Services Managed API, version 1.2
  
• Microsoft SQL Server 2012 Feature Pack which includes the following optional components:
  
  • Microsoft SQL Server 2012 Native Client 64-bit edition - ENU\x64\sqlncli.MSI
    
  • Microsoft SQL Server 2012 Data-Tier Application (DAC) Framework 64-bit edition - ENU\x64\dacframework.msi
    

Prerequisite installer operations and command-line options

The SharePoint 2013 Preview prerequisite installer (prerequisiteinstaller.exe) installs the following software, if it has not already been installed on the target server, in this order:

1. Microsoft .NET Framework version 4.5 Release Candidate (RC)
   
2. Windows Management Framework 3.0 Release Candidate (RC)
   
3. Application Server Role, Web Server (IIS) Role
   
4. Microsoft SQL Server 2008 R2 SP1 Native Client
   
5. Windows Identity Foundation (KB974405)
   
6. Microsoft Sync Framework Runtime v1.0 SP1 (x64)
   
7. Windows Identity Extensions
   
8. Microsoft Information Protection and Control Client
   
9. Microsoft WCF Data Services 5.0
   
10. Windows Server AppFabric
    
11. Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)
    

You can run prerequisiteinstaller.exe at a command prompt with the following options. When you run prerequisiteinstaller.exe at a command prompt, you may be asked to restart the server one or more times during the installation process. After rebooting, you should continue the prerequisite installation by running prerequisiteinstaller.exe with the /continue option.

• /? Display command-line options
  
• /continue This is used to tell the installer that it is continuing from a restart
  
• /unattended No user interaction
  

The installer installs from the file that you specify in the command-line options described in the following list. In this list, <file> signifies the file from which you want to install. If you do not specify the <file> option, the installer downloads the file from the Internet and installs it. If the option does not apply to the current operating system, it is ignored.

• /SQLNCli:<file> Install Microsoft SQL Server 2008 SP1 Native Client from <file>
  
• /PowerShell:<file> Install Windows Management Framework 3.0 Release Candidate (RC) from <file>
  
• /NETFX:<file> Install Microsoft .NET Framework version 4.5 from <file>
  
• /IDFX:<file> Install Windows Identity Foundation (KB974405) from <file>
  
• /IDFX11:<file> Install Windows Identity Foundation v1.1 from <file>
  
• /Sync:<file> Install Microsoft Sync Framework Runtime SP1 v1.0 (x64) from <file>
  
• /AppFabric:<file> Install Windows Server AppFabric from <file> (AppFabric must be installed with the options /i CacheClient,CachingService,CacheAdmin /gac)
  
• /KB2671763:<file> Install Microsoft AppFabric 1.1 for Windows Server (AppFabric 1.1) from <file>
  
• /MSIPCClient:<file> Install Microsoft Information Protection and Control Client from <file>
  
• /WCFDataServices:<file> Install Microsoft WCF Data Services from <file>
  

Installation options

Certain prerequisites are installed by the prerequisite installer with specific options. Those prerequisites with specific installation options are listed below with the options used by the prerequisite installer.

• Windows AppFabric
  /i CacheClient,CachingService,CacheAdmin /gac
  
• Microsoft WCF Data Services
  /quiet
  

The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller...log. You can check these log files for specific details about all changes the installer makes to the target computer.

SharePoint 2010 PowerShell Commandlets - A quick overview

Colleagues keep asking me about the most regular PowerShell commands.. This is the list created by the community that I quite often use...
 

SPAccessServiceApplication

• Get-SPAccessServiceApplication – Gets an {Access Service} application object.
• New-SPAccessServiceApplication
• Set-SPAccessServiceApplication – Sets a global property for an {Access Services} application.

SPAdminJob

• Start-SPAdminJob – Immediately starts any waiting administrative job on the local computer.

SPAlternateURL

• Get-SPAlternateURL – Return all alternate URLs that match a given criteria.
• New-SPAlternateUrl – Creates a new public or internal URL for the specified Web application zone or resource.
• Remove-SPAlternateUrl – Completely deletes the specified alternate URL.
• Set-SPAlternateUrl – Configures the specified alternate URL.

SPApplicationContent

• Install-SPApplicationContent

SPAssignment

• Start-SPAssignment – Initiates a new assignment store.
• Stop-SPAssignment – Disposes of objects in the provided Assignment Collection.

SPBackupHistory

• Get-SPBackupHistory

SPBlobStorageLocation

• Move-SPBlobStorageLocation

SPBrowserCustomerExperienceImprovementProgram

• Get-SPBrowserCustomerExperienceImprovementProgram
• Set-SPBrowserCustomerExperienceImprovementProgram

SPBusinessDataCatalogAclToChildren

• Copy-SPBusinessDataCatalogAclToChildren

SPBusinessDataCatalogEntity

• Disable-SPBusinessDataCatalogEntity
• Enable-SPBusinessDataCatalogEntity

SPBusinessDataCatalogMetadataObject

• Get-SPBusinessDataCatalogMetadataObject
• Grant-SPBusinessDataCatalogMetadataObject
• Revoke-SPBusinessDataCatalogMetadataObject
• Set-SPBusinessDataCatalogMetadataObject

SPBusinessDataCatalogModel

• Export-SPBusinessDataCatalogModel
• Import-SPBusinessDataCatalogModel
• Remove-SPBusinessDataCatalogModel

SPBusinessDataCatalogPartition

• Remove-SPBusinessDataCatalogPartition

SPBusinessDataCatalogPartitionData

• Clear-SPBusinessDataCatalogPartitionData
• Export-SPBusinessDataCatalogPartitionData
• Import-SPBusinessDataCatalogPartitionData

SPBusinessDataCatalogServiceApplication

• New-SPBusinessDataCatalogServiceApplication
• Set-SPBusinessDataCatalogServiceApplication

SPBusinessDataCatalogServiceApplicationProxy

• New-SPBusinessDataCatalogServiceApplicationProxy

SPBusinessDataCatalogThrottleConfig

• Get-SPBusinessDataCatalogThrottleConfig
• Remove-SPBusinessDataCatalogThrottleConfig
• Set-SPBusinessDataCatalogThrottleConfig

SPCentralAdministration

• New-SPCentralAdministration – Creates a new Central Administration Web application.
• Set-SPCentralAdministration

SPCertificate

• Get-SPCertificate
• New-SPCertificate
• Remove-SPCertificate

SPCertificateStore

• Get-SPCertificateStore

SPClaimMapping

• Add-SPClaimMapping
• New-SPClaimMapping
• Remove-SPClaimMapping

SPClaimProviderManager

• Get-SPClaimProviderManager

SPClaimsObject

• New-SPClaimsObject

SPClaimsPrincipal

• New-SPClaimsPrincipal

SPConfigurationDatabase

• Backup-SPConfigurationDatabase – Performs a configuration only backup.
• Connect-SPConfigurationDatabase – Connects the computer to an existing configuration database.
• Disconnect-SPConfigurationDatabase
• New-SPConfigurationDatabase – Creates a new configuration database.
• Remove-SPConfigurationDatabase – Permanently removes the specified configuration database.

SPContentDatabase

• Check-SPContentDatabase
• Dismount-SPContentDatabase
• Get-SPContentDatabase
• Initialize-SPContentDatabase
• Mount-SPContentDatabase
• New-SPContentDatabase
• Remove-SPContentDatabase
• Set-SPContentDatabase
• Upgrade-SPContentDatabase

SPContentDeploymentJob

• Get-SPContentDeploymentJob
• New-SPContentDeploymentJob
• Remove-SPContentDeploymentJob
• Set-SPContentDeploymentJob
• Start-SPContentDeploymentJob

SPContentDeploymentPath

• Get-SPContentDeploymentPath
• New-SPContentDeploymentPath
• Remove-SPContentDeploymentPath
• Set-SPContentDeploymentPath

SPCustomLayoutsPage

• Get-SPCustomLayoutsPage
• Set-SPCustomLayoutsPage

SPDatabase

• Get-SPDatabase – Retrieves all properties of a database.

SPDataConnectionFile

• Get-SPDataConnectionFile – Returns a data connection file or a collection of data connection files.
• Install-SPDataConnectionFile – Installs the provided data connection file.
• Set-SPDataConnectionFile – Sets properties of a data connection file.
• Uninstall-SPDataConnectionFile – Removes a data connection file.

SPDataConnectionFileDependent

• Get-SPDataConnectionFileDependent – Returns administrator deployed form templates on the server dependent on a Universal Data Connection (UDC).

SPDesignerSettings

• Get-SPDesignerSettings
• Set-SPDesignerSettings

SPDiagnosticConfig

• Get-SPDiagnosticConfig
• Set-SPDiagnosticConfig

SPDiagnosticsProvider

• Get-SPDiagnosticsProvider
• Set-SPDiagnosticsProvider

SPediscoveryHub

• Set-SPediscoveryHub

SPEdiscoveryHubSearchScope

• Get-SPEdiscoveryHubSearchScope

SPediscoveryHubSite

• Get-SPediscoveryHubSite

SPEnterpriseSearchAdministrationComponent

• Get-SPEnterpriseSearchAdministrationComponent – Returns the administration component for a shared search application.
• Set-SPEnterpriseSearchAdministrationComponent – Sets properties of an administration component for a shared search application.

SPEnterpriseSearchCrawlComponent

• Get-SPEnterpriseSearchCrawlComponent – Returns a crawl component for a shared search application.
• New-SPEnterpriseSearchCrawlComponent – Creates a crawl component for a shared search application.
• Remove-SPEnterpriseSearchCrawlComponent – Deletes a crawl component from a shared search application.

SPEnterpriseSearchCrawlContentSource

• Get-SPEnterpriseSearchCrawlContentSource – Returns a crawl content source.
• New-SPEnterpriseSearchCrawlContentSource – Creates a new crawl content source for a shared search application.
• Remove-SPEnterpriseSearchCrawlContentSource – Deletes a specified crawl content source from a search application.
• Set-SPEnterpriseSearchCrawlContentSource – Sets the properties of a crawl content source for a shared search application.

SPEnterpriseSearchCrawlCustomConnector

• Get-SPEnterpriseSearchCrawlCustomConnector
• New-SPEnterpriseSearchCrawlCustomConnector
• Remove-SPEnterpriseSearchCrawlCustomConnector

SPEnterpriseSearchCrawlDatabase

• Get-SPEnterpriseSearchCrawlDatabase – Returns a crawl store.
• New-SPEnterpriseSearchCrawlDatabase – Adds a crawl store to a shared search application.
• Remove-SPEnterpriseSearchCrawlDatabase – Deletes a content crawl store.
• Set-SPEnterpriseSearchCrawlDatabase

SPEnterpriseSearchCrawlExtension

• Get-SPEnterpriseSearchCrawlExtension – Returns the extension rule for the extension collection.
• New-SPEnterpriseSearchCrawlExtension – Adds an extension rule to a shared search application.
• Remove-SPEnterpriseSearchCrawlExtension – Removes a file name extension from the list of files that can be crawled.

SPEnterpriseSearchCrawlMapping

• Get-SPEnterpriseSearchCrawlMapping – Returns a crawl mapping for the search application.
• New-SPEnterpriseSearchCrawlMapping – Creates a crawl mapping rule for a shared search application.
• Remove-SPEnterpriseSearchCrawlMapping – Deletes a crawl mapping.

SPEnterpriseSearchCrawlRule

• Get-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.
• New-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.
• Remove-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.
• Set-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.

SPEnterpriseSearchCrawlTopology

• Get-SPEnterpriseSearchCrawlTopology – Returns a crawl topology.
• New-SPEnterpriseSearchCrawlTopology – Adds a crawl topology to a shared search application.
• Remove-SPEnterpriseSearchCrawlTopology – Deletes a crawl topology.
• Set-SPEnterpriseSearchCrawlTopology – Sets the properties of a crawl topology on a shared search application.

SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition

• Get-SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition

SPEnterpriseSearchExtendedConnectorProperty

• Get-SPEnterpriseSearchExtendedConnectorProperty
• Set-SPEnterpriseSearchExtendedConnectorProperty

SPEnterpriseSearchExtendedQueryProperty

• Get-SPEnterpriseSearchExtendedQueryProperty
• Set-SPEnterpriseSearchExtendedQueryProperty

SPEnterpriseSearchIndexPartition

• Get-SPEnterpriseSearchIndexPartition – Returns an index partition for a query topology.
• Set-SPEnterpriseSearchIndexPartition – Sets properties of an index partition for a query topology.

SPEnterpriseSearchLanguageResourcePhrase

• Get-SPEnterpriseSearchLanguageResourcePhrase – Returns a language resource phrase.
• New-SPEnterpriseSearchLanguageResourcePhrase – Adds a language resource phrase to a shared search application.
• Remove-SPEnterpriseSearchLanguageResourcePhrase – Deletes a language resource phrase from a shared search application.

SPEnterpriseSearchManagerService

• Get-SPEnterpriseSearchManagerService – Returns the search manager service.

SPEnterpriseSearchManagerServiceInstance

• Get-SPEnterpriseSearchManagerServiceInstance – Returns the service manager service instance.
• Start-SPEnterpriseSearchManagerServiceInstance – Starts an instance of a search manager service.
• Stop-SPEnterpriseSearchManagerServiceInstance – Stops an instance of a search manager service.

SPEnterpriseSearchManagerServiceProxy

• Get-SPEnterpriseSearchManagerServiceProxy – Returns the search manager service proxy.

SPEnterpriseSearchMetadataCategory

• Get-SPEnterpriseSearchMetadataCategory – Returns a crawled property category.
• New-SPEnterpriseSearchMetadataCategory – Adds a crawled property category to a shared search application.
• Remove-SPEnterpriseSearchMetadataCategory – Deletes a crawled property category.
• Set-SPEnterpriseSearchMetadataCategory – Sets properties of a crawled property category for a shared search application.

SPEnterpriseSearchMetadataCrawledProperty

• Get-SPEnterpriseSearchMetadataCrawledProperty – Returns a crawled property.
• New-SPEnterpriseSearchMetadataCrawledProperty – Adds a crawled property category to a shared search application.
• Set-SPEnterpriseSearchMetadataCrawledProperty – Sets the properties of a metadata crawled property for a shared search application.

SPEnterpriseSearchMetadataManagedProperty

• Get-SPEnterpriseSearchMetadataManagedProperty – Returns a managed property.
• New-SPEnterpriseSearchMetadataManagedProperty – Adds a managed property to a shared search application.
• Remove-SPEnterpriseSearchMetadataManagedProperty – Deletes a metadata managed property.
• Set-SPEnterpriseSearchMetadataManagedProperty – Sets the properties of a metadata managed property.

SPEnterpriseSearchMetadataMapping

• Get-SPEnterpriseSearchMetadataMapping – Returns the current state of a managed property mapping.
• New-SPEnterpriseSearchMetadataMapping – Adds a managed property mapping to a shared search application.
• Remove-SPEnterpriseSearchMetadataMapping – Deletes a metadata mapping from a managed property.
• Set-SPEnterpriseSearchMetadataMapping – Sets the properties of a managed property mapping for a shared search application.

SPEnterpriseSearchPropertyDatabase

• Get-SPEnterpriseSearchPropertyDatabase – Returns a property store.
• New-SPEnterpriseSearchPropertyDatabase – Adds a new property store to a shared search application.
• Remove-SPEnterpriseSearchPropertyDatabase – Deletes a property store.
• Set-SPEnterpriseSearchPropertyDatabase

SPEnterpriseSearchQueryAuthority

• Get-SPEnterpriseSearchQueryAuthority – Returns an authoritative page.
• New-SPEnterpriseSearchQueryAuthority – Adds an authoritative page to a shared search application.
• Remove-SPEnterpriseSearchQueryAuthority – Deletes an authoritative page.
• Set-SPEnterpriseSearchQueryAuthority – Sets the properties of an authoritative page for a shared search application.

SPEnterpriseSearchQueryComponent

• Get-SPEnterpriseSearchQueryComponent – Returns a query component.
• New-SPEnterpriseSearchQueryComponent – Adds a query component to a query topology.
• Remove-SPEnterpriseSearchQueryComponent – Deletes a query component.
• Restart-SPEnterpriseSearchQueryComponent
• Set-SPEnterpriseSearchQueryComponent

SPEnterpriseSearchQueryDemoted

• Get-SPEnterpriseSearchQueryDemoted – Returns a demoted site rule.
• New-SPEnterpriseSearchQueryDemoted – Adds a demoted site rule to a shared search application.
• Remove-SPEnterpriseSearchQueryDemoted – Deletes a demoted site rule.

SPEnterpriseSearchQueryKeyword

• Get-SPEnterpriseSearchQueryKeyword – Returns a keyword term.
• New-SPEnterpriseSearchQueryKeyword – Adds a keyword term to a shared search application.
• Remove-SPEnterpriseSearchQueryKeyword – Deletes a query keyword.
• Set-SPEnterpriseSearchQueryKeyword – Sets the properties of a keyword term for a shared search application.

SPEnterpriseSearchQueryScope

• Get-SPEnterpriseSearchQueryScope – Returns a query results scope.
• New-SPEnterpriseSearchQueryScope – Adds a query results scope to a shared search application.
• Remove-SPEnterpriseSearchQueryScope – Deletes a query scope.
• Set-SPEnterpriseSearchQueryScope – Sets the properties of a query results scope for a shared search application.

SPEnterpriseSearchQueryScopeRule

• Get-SPEnterpriseSearchQueryScopeRule – Returns a shared scope rule.
• New-SPEnterpriseSearchQueryScopeRule – Adds a shared scope rule to a query scope.
• Remove-SPEnterpriseSearchQueryScopeRule – Deletes query results scope rules.
• Set-SPEnterpriseSearchQueryScopeRule – Sets the properties of a shared scope rule for a query scope.

SPEnterpriseSearchQuerySuggestionCandidates

• Get-SPEnterpriseSearchQuerySuggestionCandidates

SPEnterpriseSearchQueryTopology

• Get-SPEnterpriseSearchQueryTopology – Returns a query topology.
• New-SPEnterpriseSearchQueryTopology – Adds a query topology to a shared search application.
• Remove-SPEnterpriseSearchQueryTopology – Deletes a query topology.
• Set-SPEnterpriseSearchQueryTopology – Sets the properties of a query topology for a shared search application.

SPEnterpriseSearchRankingModel

• Get-SPEnterpriseSearchRankingModel – Returns a ranking model.
• New-SPEnterpriseSearchRankingModel – Adds a ranking model to a shared search application.
• Remove-SPEnterpriseSearchRankingModel – Deletes a ranking model.
• Set-SPEnterpriseSearchRankingModel – Sets the properties of a ranking model for a shared search application.

SPEnterpriseSearchSecurityTrimmer

• Get-SPEnterpriseSearchSecurityTrimmer – Returns a custom security trimmer.
• New-SPEnterpriseSearchSecurityTrimmer – Adds a custom security trimmer to a shared search application.
• Remove-SPEnterpriseSearchSecurityTrimmer – Deletes a custom security trimmer.

SPEnterpriseSearchService

• Get-SPEnterpriseSearchService – Returns the search service for the farm.
• Set-SPEnterpriseSearchService – Sets the properties of a search service for a farm.

SPEnterpriseSearchServiceApplication

• Get-SPEnterpriseSearchServiceApplication – Returns the search service application for a farm.
• New-SPEnterpriseSearchServiceApplication – Adds a search service application to a farm.
• Remove-SPEnterpriseSearchServiceApplication – Deletes a search service application.
• Restore-SPEnterpriseSearchServiceApplication
• Set-SPEnterpriseSearchServiceApplication – Sets the properties of a search service application for a farm.
• Upgrade-SPEnterpriseSearchServiceApplication

SPEnterpriseSearchServiceApplicationProxy

• Get-SPEnterpriseSearchServiceApplicationProxy – Returns the search service application proxy.
• New-SPEnterpriseSearchServiceApplicationProxy – Adds a site hit rule for a search application.
• Remove-SPEnterpriseSearchServiceApplicationProxy – Deletes a search service application proxy.
• Set-SPEnterpriseSearchServiceApplicationProxy – Sets properties of a search service application proxy.

SPEnterpriseSearchServiceInstance

• Get-SPEnterpriseSearchServiceInstance – Returns the search service instance for a farm.
• Set-SPEnterpriseSearchServiceInstance – Sets the properties of a search service instance.
• Start-SPEnterpriseSearchServiceInstance – Starts an instance of a search service.
• Stop-SPEnterpriseSearchServiceInstance – Stops an instance of a search service.

SPEnterpriseSearchSiteHitRule

• Get-SPEnterpriseSearchSiteHitRule – Returns shared site hit rule.
• New-SPEnterpriseSearchSiteHitRule – Output an SiteHitRule Object.
• Remove-SPEnterpriseSearchSiteHitRule – Output an SiteHitRule Object.

SPEnterpriseSearchTopology

• Export-SPEnterpriseSearchTopology – Saves an existing search topology.
• Import-SPEnterpriseSearchTopology – Imports and activates a topology from an XML file.

SPExcelBlockedFileType

• Get-SPExcelBlockedFileType
• New-SPExcelBlockedFileType
• Remove-SPExcelBlockedFileType

SPExcelDataConnectionLibrary

• Get-SPExcelDataConnectionLibrary
• New-SPExcelDataConnectionLibrary
• Remove-SPExcelDataConnectionLibrary
• Set-SPExcelDataConnectionLibrary

SPExcelDataProvider

• Get-SPExcelDataProvider
• New-SPExcelDataProvider
• Remove-SPExcelDataProvider
• Set-SPExcelDataProvider

SPExcelFileLocation

• Get-SPExcelFileLocation
• New-SPExcelFileLocation
• Remove-SPExcelFileLocation
• Set-SPExcelFileLocation

SPExcelServiceApplication

• Get-SPExcelServiceApplication – Gets an {Excel Service} application object.
• New-SPExcelServiceApplication -
• Set-SPExcelServiceApplication – Sets a global property for an {Excel Services} application.

SPExcelUserDefinedFunction

• Get-SPExcelUserDefinedFunction
• New-SPExcelUserDefinedFunction
• Remove-SPExcelUserDefinedFunction
• Set-SPExcelUserDefinedFunction

SPFarm

• Backup-SPFarm – Creates a backup of an individual database, Web application, or the entire farm.
• Get-SPFarm – Returns the local SharePoint farm.
• Restore-SPFarm

SPFarmConfig

• Get-SPFarmConfig
• Set-SPFarmConfig

SPFarmEncryptionKey

• Update-SPFarmEncryptionKey – Changes the farm encryption key to a new value and re-encrypts all data currently encrypted with the current farm encryption key with the new one.

SPFeature

• Disable-SPFeature – Disables an installed feature at a given scope.
• Enable-SPFeature – Enables an installed feature at the given scope.
• Get-SPFeature – Returns the features based on a give scope.
• Install-SPFeature – Install a feature using the Feature.xml file.
• Uninstall-SPFeature – Uninstalls an installed feature definition.

SPFeatureSet

• Get-SPFeatureSet
• New-SPFeatureSet
• Remove-SPFeatureSet

SPFeatureSetMember

• Add-SPFeatureSetMember
• Remove-SPFeatureSetMember

SPHelpCollection

• Get-SPHelpCollection
• Install-SPHelpCollection – Install the provided help collection files.
• Uninstall-SPHelpCollection

SPIdentityProvider

• Get-SPIdentityProvider
• New-SPIdentityProvider
• Remove-SPIdentityProvider
• Set-SPIdentityProvider

SPIisWebServiceApplicationPool

• Get-SPIisWebServiceApplicationPool – Returns the specified Internet Information Services (IIS) Application pool.
• New-SPIisWebServiceApplicationPool – Creates a new Web service application pool.
• Remove-SPIisWebServiceApplicationPool – Completely deletes the specified Web service application pool.
• Set-SPIisWebServiceApplicationPool – Changes the account used for the Identity of the specified application pool.

SPIisWebServiceSettings

• Get-SPIisWebServiceSettings – Returns the common Web Service settings.
• Set-SPIisWebServiceSettings – Configures one or more common settings for all Web services.

SPInfoPathAdministrationFiles

• Export-SPInfoPathAdministrationFiles – Saves form templates on the SharePoint Central Administration Web site and UDCX files to a CAB file.
• Import-SPInfoPathAdministrationFiles – Imports form templates and UDCX files located on the SharePoint Central Administration Web site.

SPInfoPathFormsService

• Get-SPInfoPathFormsService – Returns the forms service settings in the farm.
• Set-SPInfoPathFormsService – Sets paramaters for the InfoPath Forms Services.

SPInfoPathFormTemplate

• Disable-SPInfoPathFormTemplate – Deactivate a form template from the specified site collection.
• Enable-SPInfoPathFormTemplate – Activates a form template in the specified site collection.
• Get-SPInfoPathFormTemplate – Returns an InfoPath form template.
• Install-SPInfoPathFormTemplate – Installs an InfoPath form template on a farm.
• Set-SPInfoPathFormTemplate – Sets properties of an InfoPath form template.
• Start-SPInfoPathFormTemplate – Unquieces an InfoPath form template on a farm after an upgrade.
• Stop-SPInfoPathFormTemplate – Disables an InfoPath form template on a farm before an upgrade.
• Test-SPInfoPathFormTemplate – Validates that a form template can be browser-enabled.
• Uninstall-SPInfoPathFormTemplate – Removes a form template from a farm.
• Update-SPInfoPathFormTemplate – Upgrades all forms templates on the farm.

SPInfoPathUrl

• Update-SPInfoPathUrl – Executes InfoPath XSN/UDC fix-up on SharePoint Services.

SPInfoPathUserAgent

• Add-SPInfoPathUserAgent – Adds a user agent to a farm.
• Get-SPInfoPathUserAgent – Returns a user agent or all the currently defined user agents for the farm.
• Remove-SPInfoPathUserAgent – Removes a user agent.

SPInfoPathWebServiceProxy

• Get-SPInfoPathWebServiceProxy – Returns the Web proxy settings for the Web application.
• Set-SPInfoPathWebServiceProxy – Sets parameters for an existing SharePoint Web service application.

SPLogEvent

• Get-SPLogEvent

SPLogFile

• Merge-SPLogFile
• New-SPLogFile

SPLogLevel

• Clear-SPLogLevel
• Get-SPLogLevel
• Set-SPLogLevel

SPManagedAccount

• Get-SPManagedAccount – Retrieves accounts registered in configuration database.
• New-SPManagedAccount – Registers a new managed account.
• Remove-SPManagedAccount – Removes a managed account from the farm.
• Set-SPManagedAccount – Configures the managed account.

SPManagedPath

• Get-SPManagedPath – Returns all managed paths that match the given criteria.
• New-SPManagedPath – Creates a new managed path for the given Web application for all host header site collections.
• Remove-SPManagedPath – Deletes the specified managed path from the specified host header or Web application.

SPMetadataServiceApplication

• Get-SPMetadataServiceApplication – Get a MetadataWebServiceApplication instance
• New-SPMetadataServiceApplication – Create a Metadata Shared Service Application
• Set-SPMetadataServiceApplication – Set properties on a Metadata Shared Service Application

SPMetadataServiceApplicationProxy

• Get-SPMetadataServiceApplicationProxy – Get a MetadataWebServiceApplicationProxy instance
• New-SPMetadataServiceApplicationProxy – Create proxy for remote or local Metadata shared service application
• Set-SPMetadataServiceApplicationProxy – Update metadata proxy settings

SPMetadataWebServicePartitionData

• Clear-SPMetadataWebServicePartitionData
• Export-SPMetadataWebServicePartitionData
• Import-SPMetadataWebServicePartitionData

SPMobileMessagingAccount

• Get-SPMobileMessagingAccount – Retrieves mobile messaging accounts for the specified Web application.
• Set-SPMobileMessagingAccount – Configures the specified mobile messaging account.

SPObaSolutionPackage

• New-SPObaSolutionPackage

SPObjectSecurity

• Get-SPObjectSecurity – Returns the security information for the specified service application.

SPParentFarmTrust

• Get-SPParentFarmTrust
• New-SPParentFarmTrust
• Remove-SPParentFarmTrust
• Set-SPParentFarmTrust

SPPassPhrase

• Set-SPPassPhrase – Sets the Passphrase to a new value.

SPProcessAccount

• Get-SPProcessAccount

SPProduct

• Get-SPProduct – Returns a list of the SharePoint related products installed in the farm and the versions of all updates installed for each of them.

SPProfileServiceApplication

• New-SPProfileServiceApplication
• Set-SPProfileServiceApplication

SPProfileServiceApplicationProxy

• New-SPProfileServiceApplicationProxy
• Set-SPProfileServiceApplicationProxy

SPProfileServiceApplicationTenant

• Add-SPProfileServiceApplicationTenant
• Export-SPProfileServiceApplicationTenant
• Import-SPProfileServiceApplicationTenant
• Remove-SPProfileServiceApplicationTenant
• Set-SPProfileServiceApplicationTenant

SPResourceSecurity

• Initialize-SPResourceSecurity

SPSearchService

• Get-SPSearchService – Returns a search service.
• Set-SPSearchService – Sets properties of a search service.

SPSearchServiceInstance

• Get-SPSearchServiceInstance – Returns an instance of a search service.
• Set-SPSearchServiceInstance – Sets properties of a search service instance.

SPSecureStoreApplication

• Get-SPSecureStoreApplication
• New-SPSecureStoreApplication
• Remove-SPSecureStoreApplication
• Set-SPSecureStoreApplication

SPSecureStoreApplicationField

• New-SPSecureStoreApplicationField

SPSecureStoreApplicationServerKey

• Update-SPSecureStoreApplicationServerKey

SPSecureStoreCredentialMapping

• Clear-SPSecureStoreCredentialMapping
• Update-SPSecureStoreCredentialMapping

SPSecureStoreGroupCredentialMapping

• Update-SPSecureStoreGroupCredentialMapping

SPSecureStoreMasterKey

• Update-SPSecureStoreMasterKey

SPSecureStoreServiceApplication

• New-SPSecureStoreServiceApplication
• Set-SPSecureStoreServiceApplication

SPSecureStoreServiceApplicationProxy

• New-SPSecureStoreServiceApplicationProxy

SPSecureStoreTargetApplication

• New-SPSecureStoreTargetApplication

SPSecurityTokenService

• Get-SPSecurityTokenService

SPServer

• Get-SPServer – Returns the server(s) in the farm that match the given identity.
• Rename-SPServer – Renames a server that is currently connected to the farm.

SPServiceApplication

• Get-SPServiceApplication – Return the specified service application.
• Grant-SPServiceApplication – Grants a user account access to the Service Application.
• Publish-SPServiceApplication – Share the specified local Service Application outside the farm.
• Remove-SPServiceApplication – Deletes the specified service application on the local server.
• Revoke-SPServiceApplication – Revokes a user’s access to a service application.
• Set-SPServiceApplication
• Unpublish-SPServiceApplication – Stop sharing the specified service application outside the farm.

SPServiceApplicationProxy

• Get-SPServiceApplicationProxy – Returns an instance of the specified Service Application Proxy.
• Remove-SPServiceApplicationProxy – Delete the specified service application proxy.

SPServiceApplicationProxyGroup

• Get-SPServiceApplicationProxyGroup – Returns the proxy group for the specified service application.
• New-SPServiceApplicationProxyGroup – Creates a new service application proxy group.
• Remove-SPServiceApplicationProxyGroup – Completely deletes the specified service application proxy group.

SPServiceApplicationProxyGroupMember

• Add-SPServiceApplicationProxyGroupMember – Adds a member to the service application proxy group.
• Remove-SPServiceApplicationProxyGroupMember – Removes one or more proxies from the specified service application proxy group.

SPServiceContext

• Get-SPServiceContext

SPServiceEndpoint

• Get-SPServiceEndpoint
• Set-SPServiceEndpoint

SPServiceInstance

• Get-SPServiceInstance – Returns the services instance for a specific server or the farm.
• Start-SPServiceInstance – Starts the Service Instance for a Service on a specific server or the farm.
• Stop-SPServiceInstance – Stops the Service Instance for a Service.

SPSessionStateService

• Disable-SPSessionStateService
• Enable-SPSessionStateService
• Get-SPSessionStateService
• Set-SPSessionStateService

SPSharedServiceApplicationInfo

• Receive-SPSharedServiceApplicationInfo

SPSingleSignOn

• Disable-SPSingleSignOn – Disables the SharePoint Single Sign On service

SPSingleSignOnDatabase

• Upgrade-SPSingleSignOnDatabase – Upgrades the SSO 12 data to a Secure Store database

SPSite

• Backup-SPSite – Performs a backup of a site collection.
• Get-SPSite – Returns all site collections that match the given criteria.
• New-SPSite – Creates a new site collection at the specified URL.
• Remove-SPSite – Completely deletes an existing site collection and all sub-sites.
• Restore-SPSite – Restores a site collection.
• Set-SPSite – Configures the specified sites.

SPSiteAdministration

• Get-SPSiteAdministration – Returns a site administration object which allows a farm administrator to view certain information about site collections they may not have access to.
• Set-SPSiteAdministration – Allows farm administrators to configure any site collection.

SPSiteSubscription

• Get-SPSiteSubscription – Returns the site subscription for the given URL or all site subscriptions in the local farm.
• New-SPSiteSubscription – Creates a new site subscription.
• Remove-SPSiteSubscription – Removes a site subscription along with all contained site collections and settings.

SPSiteSubscriptionConfig

• Get-SPSiteSubscriptionConfig
• Set-SPSiteSubscriptionConfig

SPSiteSubscriptionMetadataConfig

• Get-SPSiteSubscriptionMetadataConfig
• Remove-SPSiteSubscriptionMetadataConfig
• Set-SPSiteSubscriptionMetadataConfig

SPSiteSubscriptionSettings

• Export-SPSiteSubscriptionSettings
• Import-SPSiteSubscriptionSettings
• Remove-SPSiteSubscriptionSettings

SPSolution

• Add-SPSolution
• Get-SPSolution
• Install-SPSolution
• Remove-SPSolution
• Uninstall-SPSolution
• Update-SPSolution

SPSolutionDeploymentLock

• Remove-SPSolutionDeploymentLock

SPStateServiceApplication

• Get-SPStateServiceApplication
• New-SPStateServiceApplication
• Set-SPStateServiceApplication

SPStateServiceApplicationProxy

• Get-SPStateServiceApplicationProxy
• New-SPStateServiceApplicationProxy
• Set-SPStateServiceApplicationProxy

SPStateServiceDatabase

• Dismount-SPStateServiceDatabase
• Get-SPStateServiceDatabase
• Initialize-SPStateServiceDatabase
• Mount-SPStateServiceDatabase
• New-SPStateServiceDatabase
• Remove-SPStateServiceDatabase
• Resume-SPStateServiceDatabase
• Set-SPStateServiceDatabase
• Suspend-SPStateServiceDatabase

SPSubscriptionSettingsServiceApplication

• New-SPSubscriptionSettingsServiceApplication
• Set-SPSubscriptionSettingsServiceApplication

SPSubscriptionSettingsServiceApplicationProxy

• New-SPSubscriptionSettingsServiceApplicationProxy

SPTaxonomySession

• Get-SPTaxonomySession – Get a TaxonomySession instance

SPTimerJob

• Disable-SPTimerJob
• Enable-SPTimerJob
• Get-SPTimerJob
• Set-SPTimerJob
• Start-SPTimerJob

SPTopologyWebServiceApplication

• Get-SPTopologyWebServiceApplication
• Set-SPTopologyWebServiceApplication

SPTopologyWebServiceProxy

• Get-SPTopologyWebServiceProxy
• Set-SPTopologyWebServiceProxy

SPUsageApplication

• Get-SPUsageApplication
• New-SPUsageApplication
• Remove-SPUsageApplication
• Set-SPUsageApplication

SPUsageDefinition

• Get-SPUsageDefinition
• Set-SPUsageDefinition

SPUsageLogFile

• New-SPUsageLogFile

SPUsageService

• Get-SPUsageService
• Set-SPUsageService

SPUser

• Get-SPUser – Returns the user(s) that match a given search criteria.
• Move-SPUser – Migrates a user account in .
• New-SPUser – Adds an existing user to a site with the designated permissions.
• Remove-SPUser – Removes a user from a web site.
• Set-SPUser – Configures properties on an existing user.

SPUserProfilePhotoStore

• Update-SPUserProfilePhotoStore

SPUserSolution

• Add-SPUserSolution
• Get-SPUserSolution
• Install-SPUserSolution
• Remove-SPUserSolution
• Uninstall-SPUserSolution
• Update-SPUserSolution

SPVisioExternalData

• Get-SPVisioExternalData – Returns the settings for external data connections for a Visio Service application.
• Set-SPVisioExternalData

SPVisioPerformance

• Get-SPVisioPerformance – Returns the Visio Graphics Services settings for the performance of a Visio Service application.
• Set-SPVisioPerformance – Sets performance properties for a Visio Services application.

SPVisioSafeDataProvider

• Get-SPVisioSafeDataProvider – Returns the settings of a safe data provider for a Visio Services application.
• New-SPVisioSafeDataProvider – Adds a new data provider to a Visio Services application.
• Remove-SPVisioSafeDataProvider – Removes a data provider from a Visio Services application.
• Set-SPVisioSafeDataProvider – Specifies a description of a safe data provider for a Visio Services application.

SPVisioServiceApplication

• Get-SPVisioServiceApplication – Returns properties of a Visio Services application or a collection of Visio Services applications.
• New-SPVisioServiceApplication – Adds a new Visio Services application to a farm.
• Remove-SPVisioServiceApplication – Removes a Visio Services application from a farm.
• Set-SPVisioServiceApplication – Sets the ServiceApplicationPool property of a Visio Services application.

SPVisioServiceApplicationProxy

• Get-SPVisioServiceApplicationProxy – Returns properties of a Visio Services application proxy or a collection of Visio Services application proxies.
• New-SPVisioServiceApplicationProxy – Adds a new Visio Services application proxy to a farm.
• Remove-SPVisioServiceApplicationProxy – Removes a Visio Services application proxy from a farm.

SPWeb

• Export-SPWeb – Exports a site collection, Web application, list, or library.
• Get-SPWeb – Returns all sub-sites that match the given criteria.
• Import-SPWeb – Imports a site collection, Web application, list, or library.
• New-SPWeb – Creates a new sub-site under any existing site collection.
• Remove-SPWeb – Completely deletes the specified Web.
• Set-SPWeb – Configures the specified sub-site.

SPWebAnalyticsServiceApplication

• Get-SPWebAnalyticsServiceApplication – Returns the settings for a Web Analytics Service application.
• New-SPWebAnalyticsServiceApplication – Adds a new Web Analytics Service application to the farm.
• Set-SPWebAnalyticsServiceApplication – Sets properties of a Web Analytics Service application.

SPWebAnalyticsServiceApplicationProxy

• New-SPWebAnalyticsServiceApplicationProxy – Adds a new Web Analytics Service application proxy to the farm.

SPWebApplication

• Get-SPWebApplication – Returns all Web applications that match the given criteria.
• New-SPWebApplication – Creates a new Web application within the local farm.
• Remove-SPWebApplication – Deletes the specified Web application.
• Set-SPWebApplication – Configure the specified Web application.

SPWebApplicationExtension

• New-SPWebApplicationExtension – Creates a new zone instance for the Web application.

SPWebApplicationHttpThrottling

• Disable-SPWebApplicationHttpThrottling
• Enable-SPWebApplicationHttpThrottling

SPWebApplicationHttpThrottlingMonitor

• Set-SPWebApplicationHttpThrottlingMonitor

SPWebApplicationHttpThrottlingMonitors

• Get-SPWebApplicationHttpThrottlingMonitors

SPWebApplicationSiginRedirectUrl

• Set-SPWebApplicationSiginRedirectUrl

SPWebPartPack

• Get-SPWebPartPack – Return the Web part packages installed for the specified scope.
• Install-SPWebPartPack – Installs the specified Web part package to the specified location.
• Uninstall-SPWebPartPack – Uninstall the specified Web part package.

SPWebTemplate

• Get-SPWebTemplate – Displays all globally installed site templates that match the given identity.
• Install-SPWebTemplate – Installs the given site template.
• Set-SPWebTemplate – Changes the title and description of an installed site template.
• Uninstall-SPWebTemplate – Uninstall the given site template.

SPWordConversionServiceApplication

• New-SPWordConversionServiceApplication – Creates a new service application.
• Set-SPWordConversionServiceApplication – Sets parameters on a service application.

SPWordConversionServiceApplicationProxy

• New-SPWordConversionServiceApplicationProxy – Creates a new service application proxy.

SPWorkflowConfig

• Get-SPWorkflowConfig – Returns workflow settings for the specified Web application.
• Set-SPWorkflowConfig – Configures the workflow settings for the specified Web application.

Ten, seven, three, one GO! Delivering Sharepoint on 11/11/2011 - part 1 of 11 as seen by Boris the SharePoint-Architect.com

SharePoint 2010, SharePoint 2007, SharePoint 2003, SharePoint 2001... GO!

I just recently had a SharePoint Service Line strategy planning meeting on a customer site.. and somehow that brought back some memories... so this post was prepared in a bit different style... and the 11/11/11 is a great date to reflect those 11 years+ of my SharePointing :)

It has been an amazing SharePoint ride so far! And it's getting even better! Yahooo!
 With my first SharePoint project kick-off in August 2000 (and first SP sneak-peak in March'00) and project for 2000 users and 3 languages delivered in March 2001 (early adopters rock!) we were just getting used to the name SharePoint... Resilience? Scalabilty? DR? yeah right! But the usability was definitely there and we still did deliver a kick-a...rchitecture solution... and even resolved a major challenge after MS support team in Munich gave up... whatta ride!

"Tahoe" as it's project code name was... used to be Microsoft's "state-of-the-art" built on a WebStore with webparts... and it all started for me as a Head of MS department with MS Partner company in Slovenia :)

With all ups and down's on previous and current SharePoint versions... and 106 projects later (btw.. I am on #107 at the moment... deploying for 50k users on a 6MIO investment project...) the SharePoint 2010 is boosting with new features and capabilities almost on daily basis!

Moreover tomorrow's SharePointSaturday UK (#spsuk) will feature one of the SharePoint Online top evangelists... Steve Fox, MS Consulting Services Director... a man with 1000 and 111 tasks on his mind who still has time to write a book about the next steps that every SharePoint developer should at least flick-through... Developing Microsoft SharePoint Applications Using Windows Azure does offer a brief overview of the next SharePoint's big steps...

Intranet, extranet, internet, mobile and digital in general.. are the fields where SharePoint will allow you to excel if you plan, design, develop, deploy, support (and improve) the project correctly...

But in order to get there, there are quite few areas (52 on my list) that one will need to consider at some point before, during  or after the project...in order to keep things a bit more structured.. I will focus on 11 major areas - at a VERY high level and with large organizations in mind (which may not rule out the use of ideas in smaller companies):

• 01 - SharePoint Service Line  - The SharePoint Universe, Vision, Strategy and the Team
• 02 - SharePoint Project Management & Agile Approach - Implementation of Change
• 03 - SharePoint Business Analysis - Understanding the Needs
• 04 - SharePoint Content, Process and Lifecycle - the 5W's of SharePoint
• 05 - SharePoint Versions and Features - Playing with Super Billy's Sports Bag
  
• 06 - SharePoint Solution Design - Scoping the Beast
• 07 - SharePoint Infrastructure
• 08 - SharePoint Development & Testing
• 09 - SharePoint Service Deployment, Transition, Support & Management
• 10 - SharePoint Reusability - Existing and 3rd Party Solutions
• and 11 - Celebrations - Life after SharePoint - the SharePint part of life... my favourite! :)

SharePoint Governance

‘SharePoint Governance’ means a lot of different things to a lot of different people and for the most part they are all just a little bit wrong! 

Governance in the SharePoint world is most definitely the ‘new black’, it’s what the cool-kids on 

Twitter are talking about, disagreeing with and almost fighting over! But do they really know what they’re talking about?


Everyone has their own opinions about what Governance in a SharePoint context is and I believe that each of those people is looking through their own lens based on their individual anchor bias (a form of cognitive bias), some examples include:

• SharePoint Governance is about architecture, infrastructure, disaster recovery
• SharePoint Governance is about Project and stakeholder management
• SharePoint Governance is about Information Architecture and security
• SharePoint Governance is about telling the users what they can and can’t do
• SharePoint Governance is about running a viable SharePoint Service and having a sound Service Catalog (and related SLAs)

Each view is perfectly valid, but is not the whole story and in some cases I would venture to state that focussing on just one of these ‘views’ is more detrimental to the business than ignoring governance completely!

Lets explain what I mean; firstly Wikipedia states:

The word governance derives from the Greek verb kubernáo which means to steer and was used for the first time in a metaphorical sense by Plato.

Based upon that definition, let’s unpack this using a sailing analogy, especially as I am Boris Kapitanovic (Capitano)...

If you have any appreciation of sailing you will realise that there’s a host of factors that influence your success in racing a sailing boat around a course, these may include:

• Having the boat set-up correctly
• Having a fast boat
• Being great at sailing
• Taking the weather into consideration (wind strength, direction etc)
• Knowing where you are
• Awareness of obstacles (other boats, shore etc)
• Be fit
• Knowing the course (where you’re trying to get to)
• Use great tactics
• Steering the boat the right way.

This is not unlike designing, implementing and maintaining a SharePoint platform. But to be successful at sailing you have to focus continually on all these aspects (and more), so let’s look at what happens if you focus on only one of those facets?

• I’m a great Sailor, years of experience – I’m sailing faster than the competition, but I’m sailing fast, in the wrong direction, I don’t follow the right course, I miss out marks, I get disqualified!
• I’m an awesome tactician – Tactically I’m sailing really well, but I’m not looking at where the wind is and everyone is sailing faster than me and I didn’t notice that island… bump…sink…fail!
• I have a fast boat – My boat is the newest, most expensive, fastest and is full of go-faster gadgets, but I don’t know how to sail very well, the sails are flapping and I’m not sure where I’m going…. the boat goes very slowly, I didn’t finish the race, I’m not a winner!

As you can see in sailing, just concentrating on one thing isn’t going to guarantee you success and in SharePoint land it’s exactly the same.
Very few people (in my opinion) are looking at Governance as a whole i.e. what is Governance in the context of the SharePoint Platform, what I’ll call for the purpose of this and future posts ‘SharePoint Governance 3.0′.

Based upon our experience and thinking on this, we feel that ‘SharePoint Governance 3.0′ is made up of five equally important elements in no particular order:

• IT Assurance
• Project Governance
• Information Governance
• Technology & Business Alignment
• Service Governance
• Continuous Improvement

If we implement SharePoint spending equal amounts of focus on all of these elements, then we can truly say that our SharePoint environment is being effectively governed and is delivering measurable business value.

Let me take a few minutes to prove to you that these are all equally important elements of SharePoint Governance 3.0, by painting some scenarios where we’ve missed out one crucial element:

Scenario 1 – No IT Assurance
This one’s easy… Power-cut, no back-up taken for the last few weeks, CEO has lost his revisions to the annual report he is giving tonight.
Or what about poorly spec’d server farm, organisation is in rapid growth, system performance is poor and the users can’t do their jobs effectively.
So, we can agree we need IT Assurance – Check 1

Scenario 2 - No Project Governance
If there’s no project governance, and you don’t know what you’re meant to be delivering or why, then how will you know when the project ends and is successful? Upwardly cycling project costs, expanding time-scales and no measurable business value? Your boss is not going to be happy and just wait until Finance hear about the money you’ve wasted!
So, we can agree we need Project Governance – Check 2

Scenario 3 – No Information Governance
Your SharePoint project is successfully delivered (thanks project governance). The business stakeholders and end users are now let loose on the platform (in conjunction with the right level of change management and training). But we didn’t have time to define an Information Architecture, we haven’t been tuning the search results and everyone’s getting frustrated about the meta data they have to add to the content. We’ve tried to measure business value, but the results aren’t what we were expecting, content is all over the place, no-one can find anything and people just aren’t using SharePoint any more.
So, we can agree we need Information Governance – Check 3

Scenario 4 – No Technology and Business Alignment
Our IT department wanted SharePoint so they’ve implemented a new intranet on the platform, based on the features of the old technology solution, like-for-like. We’re a growing business and our business model and working practices have significantly evolved over the last few years. Adoption of the new platform is poor, we can’t hit the ROI figures we presented to the board and some teams are complaining that they are less efficient.
So, we can agree we need Technology and Business Alignment – Check 4

Scenario 5 - No Continuous Improvement
Our project life-cycles are typical of many other businesses. Business problem identified and then wait a few months while we plan, gather requirements, design solution, implement and then we find that the requirements have changed…Business problem identified and then wait a few months while we plan, gather requirements, design solution, implement and then we find that the requirements have changed…Business problem identified and then wait a few months while we plan, gather requirements, design solution, implement and then we find that the requirements have changed…
This approach isn’t solving our business problems, it rarely delivers business value and the ROI of the SharePoint platform isn’t being met. The business aren’t bought into the IT changes we make, they don’t see the value of SharePoint and business cases are becoming more demanding each time.
So, we can agree we need Project Governance – Check 5

Conclusion
As we can see a SharePoint project is likely to fail, cause organisational issues, not deliver business value or require loads of financial investment to maintain if we miss any of those 5 essential elements, therefore it makes sense that Governance is very much like my sailing analogy and the reality is that in our context (SharePoint) is defined as follows:

The Definition of SharePoint Governance 3.0 is…
A guiding, facilitative and inclusive approach to implementing the SharePoint platform and delivering measurable business outcomes that support the organisational strategy by  combining:
-  IT Assurance
-  Project Governance
-  Information Governance
-  Technology & Business Alignment
-  Service Governance
-  Continuous Improvement

Now we have a definition can we just get on with delivering great technology that changes the way people work and facilitates organisations achieving their ‘Big Hairy Audacious Goals’!

Where is the Intranet Collaboration Template in SharePoint 2010

by Fabian Williams

Synopsis

So I am on a client site this week yet again and I am doing an Envisioning, ADS, and a SharePoint Intranet Base Install.  Now that I am about to talk Taxonomy and Information Architecture, we touched on just having a few sites to begin with so they are not overwhelmed,  but more importantly I only have a limited time on this project and there are quick wins that I can have by using that old Microsoft Office SharePoint Server (MOSS) templates called “Intranet Publishing Portal Template” which was under the Publishing Tab for Creating Sites. Now in SharePoint Server 2010 that Template is not in the GUI under that Tab, however you can get to it and provision a site using that Template using PowerShell

Disclaimer

I have seen a few conversations by folks in the community that I have great respect for taking the position of both using that Template for provisioning new sites in the SharePoint 2010 world v/s NOT using that Template and rather using the newer templates on Microsoft SharePoint 2010
Microsoft does have some guidance on it on the Technet Planning Sheet Sites
http://technet.microsoft.com/en-us/library/cc262410.aspx
Pay attention to the last paragraph on the page which reads in part…
“Some Microsoft Office SharePoint Server 2007 site templates, such as the site directory, news, and collaboration portal templates, are not available as an option in SharePoint Server 2010…These templates are also still available as options in the UI if the SharePoint Server 2010 farm is upgraded from Office SharePoint Server 2007. Otherwise use the social tagging features in SharePoint Server 2010 to get much of the functionality provided in these templates”

How To

SO here we go…
If you are provisioning a Site Collection for an Intranet Site in SharePoint 2010 “I have seen” where folks use Templates out of the Tabs of either of the below two screenshots below. There are several food for thought as to using one over the other; one way is to start out with a Blank Site and just activate the features you need accordingly.

New SharePoint Site

New SharePoint Site

Powershell to the Rescue

So you can, with three (3) commands gain access to the Template that you had in MOSS, see below for the command and execution

Just to Verify; run the following command and look 9 from the bottom

To actually provision the site you need to run yet another PowerShell command as indicated below which identifies the template of choice with the other parameters needed.

And BoooYaaaH you have your Intranet Collaboration Site Created in SharePoint 2010 with all the starter sites at your disposal.

In Closing

Remember I told you. Microsoft does not have this in the GUI for whatever reasons which means that I did above is probably unsupported or has issues buried somewhere, or maybe not. The truth of the matter is that I dont know.
Use at your own risk
I welcome any questions, comments, rants

Cheers!

SharePoint 2010 - Which Site Template Is Right For my Intranet?

By Todd Baginski– November 20, 2009

When MOSS 2007 came out I created a blog post very similar to this one.  It turned out to be one of my most popular posts and I received many comments and private emails thanking me for putting the post together.  Since the post helped out so many folks I decided to create an updated version for SharePoint 2010.

SharePoint 2010 ships with many predefined site templates you may use to create site collections and sub sites. Sometimes the out of the box site templates will meet the needs of your project. Other times, the out of the box site templates may need to be enhanced.
Knowing which site template has the functionality you need to deploy, or use as a baseline for a custom site definition, is one of the key decisions you make when you architect a SharePoint deployment. This being said, it is important to understand the templates SharePoint 2010 comes with out of the box and what sub sites, lists and pages they support.
This post outlines the site templates SharePoint 2010 comes with out of the box and what sub sites, lists and pages they support.  As usual, I’ve documented several useful pieces of information developers will find handy when working with the out of the box SharePoint site templates.
If you install Silverlight on your machine you’ll be presented with a fancy new interface to create sites (shown below).  As you can see, SharePoint 2010 offers some guidance when creating new sites by providing descriptions and preview images for each out of the box template. However, not all of the descriptions list which resources the site comes provisioned with and the preview images are no help at all. See the image below, I think you will agree.

To better understand the inventory of out of the box site templates, I created a site collection based on each out of the box site template. After creating 29 different site collections (that’s 6 more than MOSS 2007 if you are keeping track) I realized it would be hard to remember what each one looks like and what resources they offer. So, I decided to take some screenshots and document the site templates.

Preview Images

If you care to see what all of the preview images look like, you can find them in the following directory on your SharePoint server:
C:Program FilesCommon FilesMicrosoft Sharedweb server extensions14TEMPLATELAYOUTS1033IMAGES
The file names for the preview images corresponding to each site template are listed in the tables below.

A More Detailed Look

If you care to see what each of the home pages for the site templates look like you can download screenshots of each and every site template in this zip file. The screenshots should provide you with a good understanding of the different layouts that come with each out of the box template.  This should save you a lot of time creating each type of site template on your own machine!
Here’s an example, showing the new Business Intelligence Center; oh how fancy!

Important planning information related to the out of the box site Templates!

Available Sub Site Templates

The next table lists the WEBTEMP XML fragment files each site template and configuration are defined in, the concatenated template and configuration string you need when making sites with the site template programmatically, and the file name of the preview image. If you wish to change the out of the box preview images I recommend backup up the existing preview images, then replacing them with your new preview images that have the same file names. Feel free to use the images I created from screenshots of each site template’s out of the box home page to do so. You can download them here.
Note: You may have to perform this process again after a service pack is applied in the future. Editing the various WEBTEMP files that come out of the box is not a recommended approach; that’s why I recommend this approach.
As I mentioned before, knowing which sub sites, lists, and pages are available within a given site template are key peices of information you will want to know when you architect a SharePoint solution.  The table below displays which sub site templates are available for a given parent site template.
Select a site template to filter the table:

Available Sub Site Templates	Site Definition	Config	Concatenated String	Preview Image Name	Defined in this WEBTEMP File
Team Site	STS	0	STS#0	stts.png	WEBTEMP.XML
Blank Site	STS	1	STS#1	stbs.png	WEBTEMP.XML
Document Workspace	STS	2	STS#2	stdw.png	WEBTEMP.XML
Blog	BLOG	0	BLOG#0	stbg.png	WEBTEMP.XML
Group Work Site	SGS	0	SGS#0	stgb.png	WEBTEMP.XML
Visio Process Repository	VISPRUS	1	VISPRUS#0	custprev.png	WEBTEMPVISPR.XML
Basic Meeting Workspace	MPS	0	MPS#0	stmw.png	WEBTEMP.XML
Blank Meeting Workspace	MPS	1	MPS#1	stbm.png	WEBTEMP.XML
Decision Meeting Workspace	MPS	2	MPS#2	stdm.png	WEBTEMP.XML
Social Meeting Workspace	MPS	3	MPS#3	stsm.png	WEBTEMP.XML
Multipage Meeting Workspace	MPS	4	MPS#4	stmm.png	WEBTEMP.XML
Assets Web Database	ACCSRV	1	ACCSRV#1		WEBTEMPACCSRV.XML
Charitable Contributions Web Database	ACCSRV	3	ACCSRV#3		WEBTEMPACCSRV.XML
Contacts Web Database	ACCSRV	4	ACCSRV#41		WEBTEMPACCSRV.XML
Issues Web Database	ACCSRV	6	ACCSRV#6		WEBTEMPACCSRV.XML
Projects Web Database	ACCSRV	5	ACCSRV#5		WEBTEMPACCSRV.XML
Document Center	BDR	7	BDR#0	preview.png	WEBTEMPBDR.EN-US.XML
Records Center	OFFILE	1	OFFILE#1	strc.png	WEBTEMPOFFILE.XML
Business Intelligence Center	BICenterSite	0	BICenterSite#0	bicenterlogo.png	WEBTEMPPPSMA.XML
My Site Host	SPSMSITEHOST	0	SPSMSITEHOST#0	perstemp.gif	WEBTEMPSPS.XML
Personalization Site	SPSMSITE	0	SPSMSITE#0	stps.png	WEBTEMPSPS.XML
Enterprise Search Center	SRCHCEN	0	SRCHCEN#0	template_srch_cntr.png	WEBTEMPSPS.XML
Basic Search Center	SRCHCENTERLITE	0	SRCHCENTERLITE#0	template_srch_cntr_lite.png	WEBTEMPSRCH.XML
FAST Search Center	SRCHCENTERFAST	0	SRCHCENTERFAST#0	template_srch_cntr_lite.png	WEBTEMPSRCH.XML
Enterprise Wiki	ENTERWIKI	0	ENTERWIKI#0	IPPT.gif	WEBTEMPSPS.XML
Publishing Portal	BLANKINTERNETCONTAINER	0	BLANKINTERNETCONTAINER#0	IPPT.gif	WEBTEMPSPS.XML
Publishing Site	CMSPUBLISHING	0	CMSPUBLISHING#0	stpb.png	WEBTEMPSPS.XML
Publishing Site With Workflow	BLANKINTERNET	2	BLANKINTERNET#2	stpw.png	WEBTEMPSPS.XML

New Site Templates

The following site templates are new to SharePoint 2010.

Group Work Site

Visio Process Repository

Assets Web Database

Charitable Contributions Web Database

Contacts Web Database

Issues Web Database

Projects Web Database

Business Intelligence Center

Enterprise Search Center

Basic Search Center

FAST Search Center

Enterprise Wiki

Deprecated / Removed Site Templates

The following site templates are deprecated or removed in SharePoint 2010.

Wiki Site

Site Directory

Report Center

Search Center with Tabs

Search Center

Collaboration Portal

News Site

Available Lists

Similarly, the table below displays which lists are available for a given site template.
Select a site template to filter the table:

Available Lists
Asset Library
Dashboards Library
Data Connection Library
Document Library
Form Library
Picture Library
Process Diagram Library (US Units)
Report Library
Slide Library
Translation Management
Wiki Page Library
Agenda
Announcements
Calendar
Circulations
Contacts
Custom List
Custom List in Datasheet View
Decisions
Discussion Board
External List
Import Spreadsheet
Issue Tracking
Languages and Translators
Links
Microsoft IME Dictionary List
Objectives
PerformancePoint Content List
Project Tasks
Status List
Survey
Tabs List
Tasks
Text Box
Things To Bring
Administrator Tasks
Distribution Groups

Available Pages

Finally, the table below displays which types of pages are available to create within a given site template.
Select a site template to filter the table:

Content Page	Publishing Page	Web Part Page
Yes	No	Yes
Yes	Yes	Yes
No	No	No

Buried Treasure: Hidden Templates!

Many of the site templates listed in the following table are left over from the previous versions of SharePoint and are marked obsolete. However some of them may be created programmatically. I included the list of all the hidden site templates here for reference.
Hidden site templates (not including Global template or Central Administration):

Site Template Name	Site Definition	Configuration	Concatenated String	Preview Image Name	Defined in this WEBTEMP File
Wiki Site	WIKI	0	WIKI#0	wikiprev.png	WEBTEMP.XML
Tenant Admin Site	TENANTADMIN	0	TENANTADMIN#0		WEBTEMP.XML
Access Services Site	ACCSRV	0	ACCSRV#0	bsprev.png	WEBTEMPACCSRV.XML
(obsolete) Records Center	OFFILE	0	OFFILE#0	strc.png	WEBTEMPOFFILE.XML
Shared Services Administration Site	OSRV	0	OSRV#0		WEBTEMPOSRV.XML
PerformancePoint	PPMASite	0	OSRV#0	rchome.png	WEBTEMPOSRV.XML
SharePoint Portal Server Site	SPS	0	SPS#0	spshome.gif	WEBTEMPSPS.XML
SharePoint Portal Server Personal Space	SPSPERS	0	SPSPERS#0	perstemp.gif	WEBTEMPSPS.XML
Contents Area Template	SPSTOC	0	SPSTOC#0	spshome.gif	WEBTEMPSPS.XML
Topic Area Template	SPSTOPIC	0	SPSTOPIC#0	spshome.gif	WEBTEMPSPS.XML
News Site	SPSNEWS	0	SPSNEWS#0	spshome.gif	WEBTEMPSPS.XML
Publishing Site	BLANKINTERNET	0	BLANKINTERNET#0	stpb.png	WEBTEMPSPS.XML
Press Releases Site	BLANKINTERNET	1	BLANKINTERNET#1	stpb.png	WEBTEMPSPS.XML
News Site	SPSNHOME	0	SPSNHOME#0	template_news.png	WEBTEMPSPS.XML
Site Directory	SPSSITES	0	SPSSITES#0	template_site_dir.png	WEBTEMPSPS.XML
Community Area Template	SPSCOMMU	0	SPSCOMMU#0	spshome.gif	WEBTEMPSPS.XML
Report Center	SPSREPORTCENTER	0	SPSREPORTCENTER#0	strp.png	WEBTEMPSPS.XML
Collaboration Portal	SPSPORTAL	0	SPSPORTAL#0		WEBTEMPSPS.XML
Profiles	PROFILES	0	PROFILES#0		WEBTEMPSPS.XML
Basic Search Center	SRCHCENTERLITE	1	SRCHCENTERLITE#1	template_srch_center_lite.png	WEBTEMPOSRV.XML

Leverage this information to create SharePoint sites programmatically

The concatenated template and configuration string is used when creating sites programmatically. See the last line of code below for an example.

//Create a new SPSite object corresponding to your top level site

SPSite newSite = new SPSite("http://dev");

//Create a new SPWeb object from the newSite object

SPWeb newWeb = newSite.OpenWeb();

//Return the collection of sub sites

SPWebCollection subSites = newWeb.Webs;

//Create a new sub site by adding it to the sub site collection

//The new site will have the following metadata:

//Full URL once created: http://dev/newsite

//Name: New Site

//Description: This is the description for my new site.

//Local ID set to 1033 – English

//Site Template: Team Site

//Use Unique Permissions: True

SPWeb newSubWeb = subSites.Add("newsite", "New Site", "This is the description for my new site.", 1033, "STS#0", true, false);

Once again, I hope this post comes in handy for you and saves you the time I spent digging through the SharePoint file system and creating dozens of SharePoint sites to find the information. All the information in this post comes from the public beta 2 version of SharePoint Server 2010.  I’ll update this post once SharePoint 2010 goes RTM.