Tuesday, June 23, 2015

Using SharePoint to view Operations Manager Data


System Center 2012 – Operations Manager includes a SharePoint Web Part that displays selected dashboards from the web console. A configured Web Part allows you to see at a glance the availability and performance metrics for applications in your environment.

The Operations Manager Web Part is particularly useful for providing current status views to individuals in your organization who are not Operations Manager users. Use the following procedures, as applicable, to set up dashboards on a SharePoint page.


How to Deploy the Operations Manager Web Part

The following are the prerequisites for deploying the Operations Manager web part:
  • The Operations Manager web console must be installed on a management server.
  • The SharePoint farm must be running SharePoint 2013, SharePoint Server 2010 Standard, SharePoint Server 2010 Enterprise, or SharePoint Foundation 2010.
    noteNote
    If the SharePoint farm is running SharePoint Foundation 2010, you can only deploy the web part in the same domain as the web console and you cannot use shared credentials.
  • You must have SharePoint administrator permissions for the SharePoint farm; specifically, you must have permissions to perform the following tasks:
    • Run the SharePoint PowerShell client
    • Start and stop the SPAdminV4 and SPTimerV4 services
    • Run the Add-SPSolution and Install-SPSolution cmdlets for the farm, and run the Enable-SPFeature cmdlet for all sites on the farm
The web part is a solution file named Microsoft.EnterpriseManagement.SharePointIntegration.wsp. To deploy the web part, you run a script named install-OperationsManager-DashboardViewer.ps1. This script is located in the Operations Manager installation folder under Setup\amd64\SharePoint.
noteNote
You can get more information on the scripts included with Operations Manager by using the command shell and the get-help cmdlet. For example: get-help install-OperationsManager-DashboardViewer.ps1.
Using the install-OperationsManager-DashboardViewer.ps1 script, you can deploy the web part to all sites and web applications in the farm or to a specific site or web application.

To deploy the Operations Manager web part

  1. Copy the install-OperationsManager-DashboardViewer.ps1 file and the Microsoft.Enterprisemanagement.Sharepointintegration.wsp file from the Operations Manager installation folder under Setup\amd64\SharePoint to a location that the SharePoint 2010 Management Shell can access.
  2. Open the SharePoint 2010 Management Shell and navigate to the directory where you saved the install-OperationsManager-DashboardViewer.ps1 file.
  3. In the SharePoint 2010 Management Shell, type the following command, and then press Enter.
    .\install-OperationsManager-DashboardViewer.ps1 –solutionPath <directory for Microsoft.EnterpriseManagement.SharePointIntegration.wsp> -url <optional, for installing to a specific portal address or website>
    Here is an example that deploys the web part to a specific portal address. In this example you are copying the files to “C:\Program Files\System Center Operations Manager 2012\”.
    .\install-OperationsManager-DashboardViewer.ps1 “C:\Program Files\System Center Operations Manager 2012\” http://localhost:4096
    If an error occurs when you run the script, you must disable the RemoteSigned default code-signing execution policy for the SharePoint 2010 Management Shell. To allow the install-OperationsManager-DashboardViewer.ps1 script to run, type the following command, and then press enter:
    Set-ExecutionPolicy Unrestricted
    You will see some confirmation messages, select Y to confirm, and then run the script.
  4. Verify that the web part is deployed and activated by performing the following steps:
    1. Open the site http://localhost.
    2. In the Site Actions dropdown menu, click Site Settings.
    3. In the Site Collection Administration section, click Site collection features.
    4. Locate Operations Manager Dashboard Web Part.
      • If the button to the right says Activate, then the feature was not automatically activated during deployment. To activate the web part, click the Activate button.
      • If the button to the right says Deactivate, no steps are required. The Operations Manager Dashboard web part can now be inserted into site pages.
  5. If you disabled the RemoteSigned default code-signing execution policy to run the install-OperationsManager-DashboardViewer.ps1 script, you should re-enable it after the script runs. Type the following command and then press enter:
    Set-ExecutionPolicy Restricted
    You will see some confirmation messages, select Y to confirm.

How to Configure the Web Part to Connect to a Web Console

After the web part is deployed and activated, you must configure the web part to connect to a web console or environment. You can add more environments at any time. Use the following procedure to configure the environment for a web part.

To configure the environment for a web part by using the user interface

  1. On the SharePoint central administration site, in the Site Actions dropdown menu, click View All Site Content.
  2. In Lists, click Operations Manager Web Console Environments.
  3. Click Add new item.
  4. In the Name field, enter a unique name.
  5. In the HostURI field, enter the URI to a server hosting the Operations Manager web console. For example: http://ServerName/OperationsManager/
  6. Click Save.

How to Add the Operations Manager Web Part to a SharePoint Page

After you deploy the Operations Manager web part to a SharePoint site, you can add the web part to pages. When you add the web part, you configure it to display a specific dashboard view. For the configuration, you will need the URI for the dashboard view that you want displayed.
To obtain the URI, open the web console and navigate to the desired dashboard view. The address bar will display an address such as the following:
http://localhost/OperationsManager/#/dashboard%7Btype=Microsoft.SystemCenter.Visualization.Library!Visualization.SlaDashboardViewInstanceDaily%7D
The following procedure creates a SharePoint page with the Operations Manager Dashboard Viewer web part that can only be accessed by users who have an Operations Manager user role, such as Operator or Administrator. To configure the Operations Manager Dashboard Viewer web part so that those who are not Operations Manager users can view it, perform the following steps and then see the procedure How to Configure the Web Part to Use Shared Credentials.

To add the web part to a page

  1. Open an Internet browser, and then navigate to the SharePoint server.
  2. In the Site Actions dropdown menu, click New Page.
  3. Enter a name for the page, and then click Create.
  4. The new page opens with editing tools available. Below Editing Tools, click Insert.
  5. On the Insert toolbar, click Web Part.
  6. In Categories, click Microsoft System Center.
  7. In Web Parts, click Operations Manager Dashboard Viewer Web Part, and then click Add.
  8. Click the arrow in the top right of the web part, and then click Edit web part.
  9. Select the web console server in the Dashboard Server field, and enter the URI for the dashboard in the Dashboard Parameters field, and then click OK.
  10. On the menu bar, click Page.
  11. Click Save & Close.
noteNote
After you correctly set up a dashboard web part in SharePoint, you might receive an error message saying “ticket has expired”. This is because there is a very narrow time-out for an override ticket (by default, 5 seconds). If the time on the server running SharePoint and the Web console server differ by more than this value, the connection fails. This is a likely situation if the computers are in different domains and are using a different time source. You can increase the time-out on the SharePoint Server in the web console list, but this would make the server more vulnerable to attack. The best solution is to synchronize the time between the server running SharePoint and the web console server.

How to Configure the Web Part to Use Shared Credentials

To configure the Operations Manager Dashboard Viewer web part so that those who are not Operations Manager users can view it, perform the following procedures. In the first procedure, you configure credentials by creating a Target Application ID in SharePoint. Next, you configure the web part environment.
noteNote
Operations Manager provides two scripts in the setup\SharePoint directory to allow users to add and update the SharePoint web environment keys from the web config file: add-OperationsManager-WebConsole-Environment.ps1 and update-OperationsManager-WebConsole-Environment.ps1. These scripts strip the encryptionAlgorithm and encryptionValidationAlgorithm for the override ticket from the web config file and add or update it in the sharepoint environment. This allows you to automate the creation and rotation of keys. Procedures for using these scripts are in this section.
noteNote
You cannot configure shared credentials in SharePoint Foundation 2010.

To create a Target Application ID

  1. In SharePoint Central Administration, in the Application Management section, click Manage service applications.
  2. Double-click Secure Store Service.
  3. Click New.
  4. On the Application settings page, enter a Target Application ID, a display name, and an email contact address. The Target Application ID is a unique text string that is used by the Secure Store Service application to identify this target application. The display name is displayed in the user interface. The contact can be any legitimate email address and does not have to be the identity of an administrator of the Secure Store Service application. In Target Application Type, select Group. Click Next.
  5. On the Add Field page, accept the default of Windows User Name and Windows Password, and click Next.
  6. In Target Application Administrators, enter a domain account, and click OK.
  7. Click the dropdown arrow to the right of the name of the Target Application ID that you created, and click Set Credentials.
  8. In the Windows User Name field, enter the user name of the account you want the web part to use. Enter the password for the account and confirm the password, and then click OK.

To configure the Web Part environment to use shared credentials

  1. On the server hosting the Web console, in the installation folder for the Operations Manager web console, locate the Web.config file. The default installation path is C:\Program Files\System Center 2012\Operations Manager\WebConsole\WebHost.
  2. Open Web.config in a text editor.
  3. Locate the <encryption> section.
  4. Locate the OverrideTicketEncryptionKey entry. In the following example, the first bold value is the encryption algorithm key and the second bold value is the encryption validation algorithm key:
    Example: <key name="OverrideTicketEncryptionKey" algorithm="3DES" value="92799B26F0BF54EE76A40CFECDB29868927D2DA4D7E57EBD"> <validation algorithm="HMACSHA1" value="7526BAC9FC9562835A3872A3DC12CB8B"/>
  5. Copy both keys and close Web.config.
  6. On the SharePoint site, in the Site Actions dropdown menu, click View All Site Content.
  7. In Lists, click Operations Manager Web Console Environments .
  8. Click the web part that you want to configure, and then click Edit Item.
  9. In the TargetApplicationID field, enter the Target Application ID that you created in the previous procedure.
  10. In the Encryption Algorithm Key field, enter the encryption algorithm key that you copied from Web.config.
  11. In the Encryption Validation Algorithm Key field, enter the encryption validation algorithm key that you copied from Web.config.
  12. Click Save.
Repeat this procedure for each Operations Manager environment.

To configure the environment for a Web Part by using a script

  1. Copy the add-OperationsManager-WebConsole-Environment.ps1 file, which is in the Operations Manager installation folder under Setup\amd64\SharePoint, to the SharePoint server.
  2. Open Operations Manager Shell.
  3. Run add-OperationsManager-WebConsole-Environment.ps1 using the following parameters:
    -title the name of the dashboard view
    -webconsoleUNCpath to the web.config file, not including filename
    noteNote
    The web.config file is found under Program Files\System Center 2012\Operations Manager\WebConsole\WebHost on the computer running the web console.
    -targetApplicationID the Target Application ID

How to Add Additional Environments to the Web Part

Adding new environments to the Web Part enables you to display dashboards from multiple management groups.

To add environments to the Web Part

  1. On the SharePoint site, in the Site Actions dropdown menu, click View All Site Content.
  2. In Lists, click Operations Manager Web Consoles.
  3. Click Add new item.
  4. In the Name field, enter a unique name.
  5. In the HostURI field, enter the URI to a server hosting the Operations Manager web console. For example: http://localhost/OperationsManager/
  6. Click Save.

To add environments to a Web Part by using a script

  1. Copy the update-OperationsManager-WebConsole-Environment.ps1 file, which is in the Operations Manager installation folder under Setup\amd64\SharePoint, to the SharePoint server.
  2. Open Operations Manager Shell.
  3. Run update-OperationsManager-WebConsole-Environment.ps1 using the following parameters:
    -title the name of the dashboard view
    -webconsoleUNCpath to the web.config file, not including filename
    noteNote
    The web.config file is found under Program Files\System Center 2012\Operations Manager\WebConsole\WebHost on the computer running the web console.
    -targetApplicationID the Target Application ID

How to Uninstall the Operations Manager Web Part

As with deploying the Operations Manager Web Part, you can uninstall the Web Part from all sites and web applications in the farm or from a specific site or web application. The Web Part can be uninstalled by using a script or retracted by using the SharePoint 2010 Central Administration site.

To uninstall the Web Part by using a Script

  1. Copy the install-OperationsManager-DashboardViewer.ps1 file to a location that the SharePoint 2010 Management Shell can access.
  2. Open the SharePoint 2010 Management Shell and navigate to the directory where you saved the install-OperationsManager-DashboardViewer.ps1 file.
  3. In the SharePoint 2010 Management Shell, type the following command, and then press Enter.
    .\uninstall-OperationsManager-DashboardViewer.ps1 –solutionPath <directory for Microsoft.EnterpriseManagement.SharePointIntegration.wsp> -url <optional, for uninstalling from a specific portal address or website>
    Example that uninstalls the Web Part from a specific portal address:
    .\uninstall-OperationsManager-DashboardViewer.ps1 “C:\Program Files\System Center Operations Manager 2012\” http://localhost:4096
    If an error occurs when you run the script, you must disable the RemoteSigned default code-signing execution policy for the SharePoint 2010 Management Shell. To allow the install-OperationsManager-DashboardViewer.ps1 script to run, type this command, and then press enter:
    Set-ExecutionPolicy Unrestricted
    You will see some confirmation messages, select Y to confirm, and then run the script.
  4. If you disabled the RemoteSigned default code-signing execution policy to run the install-OperationsManager-DashboardViewer.ps1 script, you should re-enable it after the script runs. Type this command, and then press enter:
    Set-ExecutionPolicy Restricted
    You will see some confirmation messages, select Y to confirm.

To retract the Web Part by using SharePoint Central Administration

  1. Open the SharePoint 2010 Central Administration site.
  2. Click System Settings.
  3. Click Manage Farm Solutions.
  4. Right-click the Microsoft.EnterpriseManagement.SharePointIntegration.wsp file, and then click Retract.

Wednesday, June 17, 2015

To configure Workflow Manager on a server that is part of the SharePoint 2013 farm and on which communication takes place by using HTTPS

  1. Determine if you need to install Workflow Manager certificates in SharePoint.
    Under some circumstances, you have to obtain and install Workflow Manager certificates. If your installation requires that you obtain and install these certificates, you must complete that step before continuing. To learn whether you need to install certificates, and for instructions, see Install Workflow Manager certificates in SharePoint Server 2013.
  2. Log into the computer in the SharePoint Server 2013 farm where Workflow Manager was installed.
  3. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell and choosing Run as administrator.
  4. Run the Register-SPWorkflowService cmdlet.
    Example:
    Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290"
  5. Log on to each server in the SharePoint Server 2013 farm.
    Each server in the SharePoint Server 2013 farm must have the Workflow Manager Client installed.
    Note

    Note:
    When you install Workflow Manager on a server it automatically installs the Workflow Manager Client on that server. You will still have to install the Workflow Manager Client on any additional servers. For example, if you have a farm that contains five servers and you install Workflow Manager on one of those servers you will still need to install the Workflow Manager Client on the four additional servers.
  6. Install the Workflow Manager Client on each server in the SharePoint farm.
    Download and install the Workflow Manager Client here: http://go.microsoft.com/fwlink/p/?LinkID=268376
To configure Workflow Manager on a server that is NOT part of the SharePoint 2013 farm and on which communication takes place by using HTTPS   

  1. Determine whether you need to install Workflow Manager certificates in SharePoint 2013.
    Under some circumstances, you have to obtain and install Workflow Manager certificates. If your installation requires that you obtain and install these certificates, you must complete that step before continuing. To learn whether you need to install certificates, and for instructions, see Install Workflow Manager certificates in SharePoint Server 2013.
  2. Log on to each server in the SharePoint Server 2013 farm.
  3. Install the Workflow Manager Client on each server in the SharePoint farm.
    Before you can run the workflow pairing cmdlet, you must install Workflow Manager Client on each of the servers in the SharePoint farm.
    Download and install the Workflow Manager Client here: http://go.microsoft.com/fwlink/p/?LinkID=268376
  4. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell command and choosing Run as administrator.
  5. Run the Register-SPWorkflowService cmdlet.
    Example:

    Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290"
    
    Important

    Important:
    You must install the Workflow Manager Client on each server in the SharePoint farm before you run the pairing cmdlet. 
    

Wednesday, May 27, 2015

Provision User Profile Service Application

The following are the steps for creating the User Profile Service Application:
1.       Go to Central Administration -> Application Management -> Manage service applications.
2.       Click on New -> User Profile Service Application.
3.       Fill up the required information in the New User Profile Service Application form with the following        information:


4.       Go to Central Administration -> System Settings -> Manage services on this server.
5.       Start the User Profile Service on the application servers.

6.       Validate that the service is started.
7.       Using the Local Users and Groups management console (lusrmgr.msc), ensure that the farm admin account (svc_prdspfarmadmin) is a local administrator in SPAS02.  If not, go ahead and do this.  Restart the machine after this step.
8.       Using the Local Security management console, ensure that the farm admin account (svc_prdspfarmadmin) has log on locally rights.  If not, go ahead and do this.  Restart the machine after this step.
9.       Start the User Profile Synchronization Service onSPAS02.

10.   Wait until the service status is Started.  It normally takes 2-3 minutes to provision everything.
During the creation of the User Profile Service Application, you can specify the name of the MySites host site collection.  If this doesn’t exist yet, you can use the following steps:
1.       Go to Central Administration -> Application Management -> Manage web applications.

2.       Click on New to create the MySites web application.
3.       Complete the New Web Application form as follows:

4.       Once the web application has been created, proceed to create the site collection.
5.       Complete the New Site Collection page as follows:

Note: It is important to choose My Site Host as the template.


6.       The last thing to do is to add personal as a managed path.  The name of the managed path can be changed.  However for this production build, personal was used.  To do this, go to the Manage Web Applications page, select the MySites web application, and click on Managed Path.

7.       Type in personal and click on the Add Path button.






8.       Once added, click on Ok.

Thursday, August 21, 2014

Overlay a SharePoint calendar with a calendar from Exchange or SharePoint

Overlay a SharePoint calendar on another SharePoint calendar

  1. In a SharePoint calendar, choose the Calendar tab and then select Calendar Overlays.
  2. In the Calendar Overlay Settings page, choose New Calendar.
  3. In the Name and Type section, type the Calendar Name and then select SharePoint.
  4. In the Calendar Overlay Settings section, type a Description for the calendar (optional), and change the Colortheme for the calendar (optional).
     TIP    Selecting different colors for different calendars makes it easier to distinguish which calendar an event is from.
  5. Type the Web URL for the SharePoint site that the calendar is in, such as https://contoso.com/TWGroupWorkSite/calendar, and then select Resolve. If the calendar is in the same site as the group calendar, Web URL will already be populated accurately.
  6. Select the List drop-down arrow and then select the calendar that you want to add to the calendar.
  7. Select the view that you want to use from the List View options.
  8. If you want the overlaid SharePoint calendar to always display in the SharePoint group calendar, select Always Show.
  9. Click OK to accept the overlay specification, and then click OK to complete the process.

Overlay an Exchange calendar on a SharePoint calendar

The following procedure describes how to overlay an Exchange calendar onto a SharePoint calendars for a SharePoint calendar. After you overlay the calendar, you can use this calendar to create a special calendar view.
 IMPORTANT    You can only overlay your own Exchange calendar. That is, the Exchange calendar overlay works with the account credentials of the user who is current logged on. SharePoint uses the account information of the current user to retrieve calendar data from the Exchange Web Service.
To overlay an Exchange calendar, follow these steps:
  1. In a SharePoint calendar, in the ribbon, on the Calendar tab, click Calendar Overlays.
  2. In the Calendar Overlay Settings page, click New Calendar.
  3. In the Name and Type section, type the Calendar Name and select Exchange.
  4. In the Calendar Overlay Settings section, type a Description for the calendar (optional), and change the defaultColor theme for the calendar (optional).
Screenshot of the Calendar Overlay dialog box in SharePoint. The dialog box shows the Calendar name, calendar type (Exchange), and gives the URLs for Outlook Web Access and Exchange Web Access.
  1. Click Find to automatically fill in web addresses for Outlook Web Access URL and Exchange Web Service URL. IfFind does not work in your environment, type the URLs manually.
If you want this Exchange calendar to always appear with the SharePoint group calendar, select Always Show.

  1. Click OK and then click OK again.

Thursday, July 3, 2014

Boundaries and Limits for SharePoint 2013/2010

Software boundaries and limits for SharePoint 2013

This data is taken from the Microsoft TechNet article entitled: SharePoint Server 2010 capacity management: Software boundaries and limits as well as the article entitled:Software boundaries and limits for SharePoint 2013.  To get more detailed information, go directly to these articles.
Microsoft also states that this data is just a guideline to be used for planning and is based on testing performed at Microsoft, on live properties. The results are likely to vary based on the equipment used and the features and functionality that are implemented for underlying sites.

This article describes software boundaries and limits of SharePoint Server 2013 followed by a comparison chart with 2010.

These include the following:
Boundaries: Static limits that cannot be exceeded by design
Thresholds: Configurable limits that can be exceeded to accommodate specific requirements
Supported limits: Configurable limits that have been set by default to a tested value.
However certain basic important ones are listed as below:

  • Application pools:10 per web server 
The maximum number is determined by hardware capabilities.
This limit is dependent largely upon:
    The amount of memory allocated to the web servers
    The workload that the farm is serving, that is, the user base and the usage characteristics (a single highly active application pool can utilize 10 GB or more) 

  • Site collections per farm: 750,000 (500,000 Personal Sites and 250,000 other sites per farm)

  • Web site: 250,000 per site collection

  • Number of content databases: 500 per farm
The maximum number of content databases per farm is 500. With 500 content databases per web application, end user operations such as opening the site or site collections are not affected. But administrative operations such as creating a new site collection will experience decrease in performance. We recommend that you use Windows PowerShell to manage the web application when a large number of content databases are present, because the management interface might become slow and difficult to navigate.

  • Content database size (general usage scenarios): 200 GB per content database
 We strongly recommended limiting the size of content databases to 200 GB.
If you are using Remote BLOB Storage (RBS), the total volume of remote BLOB storage and metadata in the content database must not exceed this limit. 

  • Content database items: 60 million items including documents and list items
The largest number of items per content database that has been tested on SharePoint Server 2013 is 60 million items, including documents and list items. If you plan to store more than 60 million items in SharePoint Server 2013, you must deploy multiple content databases. 

  • File size: 2 GB               
The default maximum file size is 250 MB. This is a configurable limit that can be increased up to 2 GB (2,047 MB). However, a large volume of very large files can affect farm performance.

  • Documents: 30,000,000 per library               
You can create very large document libraries by nesting folders, or using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored. 

  • Major versions: 400,000               
If you exceed this limit, basic file operations—such as file open or save, delete, and viewing the version history— may not succeed. 
  • Minor versions: 511 
The maximum number of minor file versions is 511. This limit cannot be exceeded. 

  • Items: 30,000,000 per list 
You can create very large lists using standard views, site hierarchies, and metadata navigation. This value may vary depending on the number of columns in the list and the usage of the list. 

  • Bulk operations: 100 items per bulk operation               
The user interface allows a maximum of 100 items to be selected for bulk operations. 

  • Coauthoring in Word and PowerPoint for .docx, .pptx and .ppsx files: 10 concurrent editors per document               
Recommended maximum number of concurrent editors is 10. The boundary is 99.
If there are 99 co-authors who have a single document opened for concurrent editing, each successive user sees a “File in use” error, and can only open a read-only copy.
More than 10 co-editors will lead to a gradually degraded user experience with more conflicts, and users might have to go through more iteration to successfully upload their changes to the server.

  • Web parts: 25 per wiki or Web Part page              
This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected.

  • Blog posts: 5,000 per site               
The maximum number of blog posts is 5,000 per site. 

  • Comments: 1,000 per post 
The maximum number of comments is 1,000 per post. 

  • File size of Visio web drawings: 50 MB               
Visio Services has a configuration setting that enables the administrator to change the maximum size of web drawings that Visio processes. 
Larger file sizes have the following side effects:
    Increase in the memory footprint of Visio Services.
    Increase in CPU usage.
    Reduction in application server requests per second.
    Increase overall latency.
    Increase SharePoint farm network load 

  • Users in a site collection        : 2 million per site collection
COMPARISON CHART:
Limit Name
SharePoint 2010 Maximum Value
SharePoint 2013 Maximum Value
Web application limits


Web application
Not Published
20 per farm
Content database
300 per Web application
300 per Web application
Zone
5 per Web application
5 per Web application
Managed path
20 per Web application
20 per Web application
Solution cache size
300 MB per Web application
300 MB per Web application
Site collection
250,000 per Web application
250,000 per Web application
Web server and application server limits


Application pools
10 per Web server
10 per Web server
Content database limits


Number of content databases
300 per Web application
500 per farm
Content database size (general usage scenarios)
200 GB per content database
200 GB per content database
Content database size (all usage scenarios)
4 TB per content database
4 TB per content database
Content database size (document archive scenario)
No explicit content database limit
No explicit content database limit
Content database items
60 million items including documents and list items
60 million items including documents and list items
Site collections per content database
2,000 recommended
5,000 maximum
2,000 recommended
5,000 maximum
MySites per content database
Not Published
5,000 per content database
Remote BLOB Storage (RBS) storage subsystem on Network Attached Storage (NAS)
Time to first byte of any response from the NAS cannot exceed 20 milliseconds
Time to first byte of any response from the NAS cannot exceed 20 milliseconds
Site collection limits


Site collection
Not Published
2,000,000 per farm
Web site
250,000 per site collection
250,000 per site collection
MySites per farm
Not Published
500,000 per farm
Site collection size
Maximum size of the content database
Maximum size of the content database
Number of device channels per publishing site collection
Not Available in SharePoint 2010
10
List and library limits


List row size
8,000 bytes per row
8,000 bytes per row
File size
2 GB
2 GB
Documents
30,000,000 per library
30,000,000 per library
Major versions
400,000
400,000
Minor versions
Not Published
511
Items
30,000,000 per list
30,000,000 per list
Rows size limit
6 table rows internal to the database used for a list or library item
6 table rows internal to the database used for a list or library item
Bulk operations
100 items per bulk operation
100 items per bulk operation
List view lookup threshold
8 join operations per query
8 join operations per query
List view threshold
5,000
5,000
List view threshold for auditors and administrators
20,000
20,000
Subsite
2,000 per site view
2,000 per site view
Coauthoring in Word and PowerPoint for .docx, .pptx and .ppsx files
10 concurrent editors per document
10 concurrent editors per document
Security scope
1,000 per list
1,000 per list
Column limits


Single line of text
276
276
Multiple Lines of Text
192
192
Choice
276
276
Number
72
72
Currency
72
72
Date and Time
48
48
Lookup
96
96
Yes / No
96
96
Person or group
96
96
Hyperlink or picture
138
138
Calculated
48
48
GUID
6
6
Int
96
96
Managed metadata
94
94
Page limits


Web parts
25 per wiki or Web part page
25 per wiki or Web part page
Security limits


Number of SharePoint groups a user can belong to
5,000
5,000
Users in a site collection
2 million per site collection
2 million per site collection
Active Directory Principles/Users in a SharePoint group
5,000 per SharePoint group
5,000 per SharePoint group
SharePoint groups
10,000 per site collection
10,000 per site collection
Security principal: size of the Security Scope
5,000 per Access Control List (ACL)
5,000 per Access Control List (ACL)
Search limits


Search service applications
20 per farm
20 per farm
Crawl databases
10 crawl databases per search service application
25 million items per crawl database
5 crawl databases per search service application
Crawl components
16 per search service application
2 per search service application
Index components
Not Published
60 per Search service application
Index partitions
20 per search service application
128 total
20 per search service application
Index replicas
Not Available in SharePoint 2010
3 per index partition
Indexed items
100 million per search service application;
10 million per index partition
100 million per search service application;
10 million per index partition
Crawl log entries
100 million per search application
100 million per search application
Property databases
10 per search service application;128 total
10 per search service application;128 total
Link database
Not Available in SharePoint 2010
Two per Search service application
Query processing components
128 per search application
64/(total crawl components) per server
1 per server computer
Content processing components
Not Published
One per server computer
Scope rules
100 scope rules per scope; 600 total per search service application
100 scope rules per scope; 600 total per search service application
Scopes
200 site scopes and 200 shared scopes per search service application
200 site scopes and 200 shared scopes per search service application
Display groups
25 per site
25 per site
Alerts
1,000,000 per search application (seems like a mistake)
100,000 per search application
Content sources
50 per search service application
50 per search service application
Start addresses
100 per content source
100 per content source
Concurrent crawls
20 per search application
20 per search application
Crawled properties
500,000 per search application
500,000 per search application
Crawl impact rule
100
no limit
Crawl rules
100 per search service application
no limit
Managed properties
100,000 per search service application
50,000 per search service application
Values per managed property
Not Published
100
Indexed managed property size
Not Published
512 KB per searchable/queryable managed property
Managed property mappings
100 per managed property
100 per managed property
Retrievable managed property size
Not Published
16 KB per managed property
Sortable and refinable managed property size
Not Published
16 KB per managed property
URL removals
100 removals per operation
100 removals per operation
Authoritative pages
1 top level and minimal second and third level pages per search service application
1 top level and minimal second and third level pages per search service application
Keywords
200 per site collection
200 per site collection
Metadata properties recognized
10,000 per item crawled
10,000 per item crawled
Analytics processing components
Not Available in SharePoint 2010
6 per Search service application
Analytics reporting database
Not Available in SharePoint 2010
Four per Search service application
Maximum eDiscovery KeywordQuery text length
Not Available in SharePoint 2010
16 KB
Maximum KeywordQuery text length
Not Available in SharePoint 2010
4 KB
Maximum length of eDiscovery KeywordQuery text at Search service application level
Not Available in SharePoint 2010
20 KB
Maximum length of KeywordQuery text at Search service application level
Not Available in SharePoint 2010
20 KB
Maximum size of documents pulled down by crawler
Not Available in SharePoint 2010
64 MB (3 MB for Excel documents)
Navigable results from search
Not Available in SharePoint 2010
100,000 per query request per Search service application
Number of entries in a custom entity extraction dictionary
Not Available in SharePoint 2010
1 million
Number of entries in a custom search dictionary
Not Available in SharePoint 2010
5,000 terms per tenant
Number of entries in a thesaurus
Not Available in SharePoint 2010
1 million
Ranking models
Not Available in SharePoint 2010
1,000 per tenant
Results removal
Not Available in SharePoint 2010
No limit
Term size
Not Available in SharePoint 2010
300 characters
Unique terms in the index
Not Available in SharePoint 2010
2^31 (>2 billion terms)
Unique contexts used for ranking
Not Available in SharePoint 2010
15 unique contexts per rank model
User defined full text indexes
Not Available in SharePoint 2010
10
User Profile Service limits


User profiles
2,000,000 per service application
2,000,000 per service application
Social tags, notes and ratings
500,000,000 per social database
500,000,000 per social database
Maximum Number of Users Imported Via FIM
Not Published
1000000
Content deployment limits


Content deployment jobs running on different paths
20
20
Blog limits


Blog posts
5,000 per site
5,000 per site
Comments
1,000 per post
1,000 per post
Business Connectivity Services limits


ECT (in-memory)
5,000 per Web server (per tenant)
5,000 per Web server (per tenant)
External system connections
500 per Web server
500 per Web server
Database items returned per request
2,000 per database connector
2,000 per database connector
Response latency
Not Published
600 seconds
Service response size
Not Published
150,000,000 bytes
Filter Descriptor (in-store)
Not Published
200 per ECT method
ECT Identifier (in-store)
Not Published
20 per ECT
Database Item
Not Published
1,000,000 per request
Workflow limits


Workflow postpone threshold
15
15
Workflow timer batch size
100
100
Workflow associations
Not Published
100 per list
List items or documents that can be bulk created or uploaded to start workflow instances
Not Published
5,000 items
Published workflow definitions per site
Not Published
1,000 per site
Total workflow associations per site
Not Published
1,799 per site
Maximum workflow definition (xaml) size
Not Published
5,120 KB
Maximum depth of a workflow sub-step in xaml (workflow complexity)
Not Published
121 levels
Workflow instance activations per second per web server
Not Published
6 per second
Rest calls from SharePoint workflow per second per web server
Not Published
60 per second
Workflow variable value size
Not Published
256 KB
Maximum list size for workflow lookups to non-indexed fields
Not Published
5,000 items per list view
Maximum list size for auto-start workflow associations
Not Published
10 million items per list
Managed Metadata term store (database) limits


Maximum number of levels of nested terms in a term store
7
7
Maximum number of term sets in a term store
1,000
1,000
Maximum number of terms in a term set
30,000
30,000
Total number of items in a term store
1,000,000
1,000,000
Number of Variation Labels
Not Available in SharePoint 2010
209 per term store
Visio Services limits


File size of Visio Web drawings
50 MB
50 MB
Visio Web drawing recalculation time-out
120 seconds
120 seconds
Visio Services minimum cache age (data connected diagrams)
Minimum cache age: 0 to 24hrs
Minimum cache age: 0 to 24hrs
Visio Services maximum cache age (non-data connected diagrams)
Maximum cache age: 0 to 24hrs
Maximum cache age: 0 to 24hrs
SharePoint Web Analytics service limits


SharePoint entities
30,000 per farm when Web Analytics is enabled
Deprecated
PerformancePoint Services limits


Cells
1,000,000 per query on Excel Services data source
1,000,000 per query on Excel Services data source
Columns and rows
15 columns by 60,000 rows
15 columns by 60,000 rows
Query on a SharePoint list
15 columns by 5,000 rows
15 columns by 5,000 rows
Query on a SQL Server data source
15 columns by 20,000 rows
15 columns by 20,000 rows
Word Automation Services limits


Input file Size
512 MB
512 MB
Frequency with which to start conversions (minutes)
1 minute (recommended) 
15 minutes (default)
59 minutes (boundary)
1 minute (recommended) 
15 minutes (default)
59 minutes (boundary)
Number of conversions to start per conversion process
For PDF/XPS output formats: 30 x M For all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)
For PDF/XPS output formats: 30 x M For all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)
Conversion job size
100,000 conversion items
100,000 conversion items
Total active conversion processes
N-1, where N is the number of cores on each application server
N-1, where N is the number of cores on each application server
Word Automation Services database size
2 million conversion items
2 million conversion items
SharePoint Workspace limits (Renamed to Office Live Workspace)


Office Live Workspace list items
30,000 items per list
30,000 items per list
Office Live Workspace documents
1,800 documents limit in SharePoint Workspace
1,800 documents in Office Live Workspace
OneNote limits


Number of Sections and Section Groups in a OneNote Notebook (on SharePoint)
See limit for “Documents” in List and library limits
See limit for “Documents” in List and library limits
Maximum size of a section
See limit for “File size” in List and library limits
See limit for “File size” in List and library limits
Maximum size of an image, embedded file, and XPS OneNote printout in a OneNote section.
See limit for “File size” in List and library limits
See limit for “File size” in List and library limits
Maximum size of all images, embedded files, and XPS printouts in a single OneNote page.
Default limit is double the “File size” limit.
Default limit is double the “File size” limit.
Merge operations
One per CPU core per Web server
One per CPU core per Web server
Excel Services limits


Maximum workbook size
Not Published
10 MB
Machine Translation Service limits


Input file size for binary files
Not Available in SharePoint 2010
524,288 KB per file
Input file size for text files
Not Available in SharePoint 2010
15,360 KB per file
Maximum character count for Microsoft Word Documents
Not Available in SharePoint 2010
10,000,000 per document
Total concurrent translation processes
Not Available in SharePoint 2010
5
Delay between translations
Not Available in SharePoint 2010
59 minutes
Number of translations per translation process
Not Available in SharePoint 2010
1,000 per process
Maximum concurrent translation requests
Not Available in SharePoint 2010
300
Files per translation job
Not Available in SharePoint 2010
100,000 files
Machine Translation Service database size
Not Available in SharePoint 2010
1,000,000 files
Office Web Application Service limits


Cache size
100 GB
100 GB
Renders
One per document per second per CPU core per application server (maximum eight cores)
One per document per second per CPU core per application server (maximum eight cores)
OneNote concurrent merge operations
Not Available in SharePoint 2010
8 per document
Project Server limits


End of project time
Date: 12/31/2049
Date: 12/31/2049
Deliverables per project plan
1,500 deliverables
1,500 deliverables
Number of fields in a view
256
256
Number of clauses in a filter for a view
50
50
SharePoint Apps limits


Maximum Access app size on Office 365/SQL Azure
Not Available in SharePoint 2010
100 Mb
Apps displayed in Manage Licenses page
Not Available in SharePoint 2010
2,000
Number of app licenses per tenant
Not Available in SharePoint 2010
1,000,000
Number of apps displayed in the Add an App page
Not Available in SharePoint 2010
240
Number of managers per app license
Not Available in SharePoint 2010
30
Number of app licenses assigned to a user viewable by that user
Not Available in SharePoint 2010
2,000
Number of apps in the corporate catalog viewable by a single user
Not Available in SharePoint 2010
500
Miscellaneous limits


Number of User agent substrings per device channel
Not Available in SharePoint 2010
150
Number of SharePoint sources per EDiscovery case
Not Available in SharePoint 2010
100
Number of Exchange sources (mailboxes) per EDiscovery case
Not Available in SharePoint 2010
1500
Maximum size of EDiscovery Query
Not Available in SharePoint 2010
16K characters or 500 keywords
Number of nodes in managed navigation term set
Not Available in SharePoint 2010
2000