-You can disable the integration by running `Set-SPOTenant -EnableAzureADB2BIntegration $false`.

-Content that was shared externally while the integration was enabled will need to be shared again with those people.

-

-

-

-

-

-

-

-

-

-Keep databases small to speed both backup and restore. For example, use multiple content databases for a web application instead of one large content database. For more information, see [Database types and descriptions in SharePoint Server](../technical-reference/database-types-and-descriptions.md).

-

-For a graphical overview of the databases that support SharePoint Server 2016, see [Quick reference guide: SharePoint Server 2016 and 2019 databases](../technical-reference/technical-diagrams.md#sharepoint-servers-2016-and-2019-databases).

-

-

-

-> SharePoint Server supports SQL Server backup compression. SQL Server data compression is not supported for SharePoint Server databases.

-

-

-

-If you are using the full recovery model, we recommend that you periodically truncate the transaction log files to avoid maintenance issues.

-

-

-

-

-If you use the `Export-SPWeb` PowerShell cmdlet, you can use the `NoFileCompression` parameter. By default, SharePoint Server uses file compression while exporting web applications, site collection, lists, or document libraries. You can use this parameter to suppress file compression while exporting and importing. File compression can use up to 30% more resources. However, the exported file uses approximately 25% less disk space. If you use the `NoFileCompression` parameter when you export, you have to also use it when you import the same content.

-

-You can also use the `NoLogFile` parameter. By default, SharePoint Server always creates a log file when you export content. Although you can use this parameter to suppress log file creation to save resources, we recommend that you always create logs. Logs are important for troubleshooting and log creation does not use many resources such as CPU or memory.

-

-When you use the `Backup-SPFarm` cmdlet, you can also use the `BackupThreads` parameter to specify how many threads SharePoint Server will use during the backup process. A higher number of threads will consume more resources during backup. But the overall time to make the backup is decreased. Because each thread is recorded in the log files, the number of threads does affect log file interpretation. By default, three threads are used. The maximum number of available threads is 10.

-

-> The backup threads setting is also available through Central Administration on the **Default Backup and Restore Settings** page in the **Backup and Restore** section.

-

-

-

-

-

-

-

-

-

-

-

-

-When you deploy SharePoint Server, record the accounts that you create, the computer names, passwords, and setup options. Keep this information in a safe and secure location. Possibly, keep multiple records to make sure this information is always available.

-

-

-

-

-

-

-> [!NOTE]

-> SharePoint Server 2019 supports the FILESTREAM provider that is included with SQL Server 2017. SharePoint Server 2016 supports the FILESTREAM provider that is included with SQL Server 2014. For more information, see [Enable and Configure FILESTREAM](/sql/relational-databases/blob/enable-and-configure-filestream?viewFallbackFrom=sql-server-2014).

-

-> SharePoint Server 2013 supports the FILESTREAM provider that is included in the [Microsoft® SQL Server® 2008 R2 Feature Pack](https://go.microsoft.com/fwlink/p/?LinkID=177388). The SQL Server 2012 and SQL Server 2014 installation media includes RBS as an optional add-on component.

-

-#### Concepts

-

-

-#### Other Resources

-[Transparent Data Encryption](https://social.technet.microsoft.com/wiki/contents/articles/34201.configuring-tde-in-sharepoint-content-databases.aspx)

-

-

-The best practices in this article are ordered based on the sequence in which they would apply, from installing and configuring SQL Server, to deploying SharePoint Server, and then maintaining the farm. Most of the practices apply to all versions of SQL Server. Practices that are unique to SQL Server versions are shown in separate sections.

-

-> If you plan to use SQL Server Business Intelligence components in a SharePoint Server 2016 farm you must use SQL Server 2016 CTP 3.1 or later. You can now download SQL Server 2016 CTP 3.1 or later to use the SQL Server Power Pivot for SharePoint add-in. You can also use Power View by installing SQL Server Reporting Services (SSRS) in SharePoint-integrated mode and the SSRS front-end add-in from the SQL Server installation media.

-

-

-> If you plan to use SQL Server Business Intelligence components in a SharePoint Server 2013 farm you must use SQL Server 2012 with Service Pack 1 (SP1) or SQL Server 2014. For information about SQL Server 2012 with SP1 BI and SharePoint Server 2013, see [Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1)](/previous-versions/sql/sql-server-2012/jj218795(v=sql.110)). For more information about SQL Server 2014 and SharePoint Server 2013, see [Install SQL Server 2014 Business Intelligence Features](/sql/sql-server/install/install-sql-server-business-intelligence-features).

-

-> Best practices in this article apply to the Relational Database Management System (RDBMS) of SQL Server with SharePoint Server.

-

-

-> The recommendation to use a dedicated server for relational databases also applies to deploying SQL Server in virtual environments.

-

-To ensure consistent behavior and performance, configure the following options and settings before you deploy SharePoint Server.

-

- - SQL statistics are managed by the health rule ΓÇ£Databases used by SharePoint have outdated index statisticsΓÇ¥ that calls proc_updatestatics

- - Content databases have the Auto Update Statistics property set to **False**

-

- - SQL statistics are not managed by the health rule ΓÇ£Databases used by SharePoint have outdated index statisticsΓÇ¥

- - Content databases have the Auto Update Statistics property set to **True** `

-

- > Setting the max degree of parallelism to any other number can cause a less optimal query plan to be used that will decrease SharePoint Server performance.

-

-

-For more information about these SQL Server settings and options, see [Set SQL Server options](storage-and-sql-server-capacity-planning-and-configuration.md#Section6_3).

-

-

-

-

-

-

-

-

-

-> Database mirroring will be deprecated in future versions of SQL Server. We recommend using Always On Availability Groups.

-

-

-

-

-

-

-

-

- The highest ranked item should be in the fastest drives.

-

- | Rank | Item |

-| :-- | :-- |

-| 1 | tempdb data files and transaction logs |

-| 2 | Content database transaction log files |

-| 3 | Search databases, except for the Search administration database |

-| 4 |Content database data files |

-

-

-

- | Rank | Item |

-| :-- | :-- |

-| 1 | tempdb data files and transaction logs |

-| 2 | Content database data files |

-| 3 | Search databases, except for the Search administration database |

-| 4 | Content database transaction log files |

-

-

-

-

-

-

- > If you manually restrict database size in SQL Server, you can cause unexpected system downtime when the capacity is exceeded.

-

-

-> Consider that how you measure disk speed varies between data files and log files. The fastest drives for database data may not be the fastest for log files. Consider usage patterns, I/O, and file size.

-

-

-

-

- > You must factor in the performance and operations issues associated with using autogrowth. For more information, see [Considerations for the "autogrow" and "autoshrink" settings in SQL Server](/troubleshoot/sql/admin/considerations-autogrow-autoshrink).

-

-

- - Set autogrowth values to a fixed number of megabytes instead of to a percentage. The bigger the database, the bigger the growth increment should be.

-

- > Use care when you set the autogrowth feature for SharePoint databases. If you set a database to autogrow as a percentage, for example at a 10-percent (%) growth rate, a database that is 5 GB grows by 500MB every time that a data file has to be expanded. In this scenario, you could run out of disk space.

-

- Consider for example, a scenario where content is gradually increased, say at 100MB increments, and autogrowth is set at 10MB. Then suddenly a new document management site requires a very large amount of data storage, perhaps with initial size of 50 GB. For this large addition, growth at 500 MB increments is more appropriate than 10MB increments.

-

-

-

-We recommend that you continuously monitor SQL Server storage and performance to make sure that each production database server is adequately handling the load put on it. Additionally, continuous monitoring enables you to establish benchmarks that you can use for resource planning.

-

-

-

-

-

-

-

-

-

-

-

-#### Concepts

-

-#### Other Resources

-[Securing SharePoint: Harden SQL Server in SharePoint Environments](/archive/blogs/rycampbe/securing-sharepoint-harden-sql-server-in-sharepoint-environments)

-

-Web Parts that use search technology to show content in a publishing environment (referred to in this article as Search Web Parts) show content that was crawled and added to the search index, as described in "Understanding how content is added to and managed in the search index" in [Overview of cross-site publishing in SharePoint Server](overview-of-cross-site-publishing.md). These Web Parts have queries defined in them, and when users browse to a page that contains a Web Part that uses search technology, the Web Part issues the query automatically. The query result is then displayed in the Web Part. You can modify the query in the search Web Part to fit your content needs.

-

-

-> Because SharePoint Server runs as websites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide. SharePoint Server supports the accessibility features of supported browsers. For more information, see the following resources: > [Plan browser support](../install/browser-support-planning-2016-2019.md)> [Accessibility guidelines in SharePoint](../accessibility-guidelines.md)> [Accessibility in SharePoint](/sharepoint/dev/general-development/accessibility-in-sharepoint)> [Keyboard shortcuts](https://support.office.com/article/466e33ee-613b-4f47-96bb-1c20f20b1015)> [Touch](/windows/win32/wintouch/windows-touch-gestures-overview).

-

-

-

- **To add a Content Search Web Part to a page**

-

-

-

-3. Click the **Settings** menu, and then click **Edit page**.

-

-

-

-

-

- **To configure the query for a Content Search Web Part**

-

-1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the publishing site collection.

-

-

-

-

-

-6. On the **BASICS** tab, do one of the following:

-

- - To define your query by using Quick Mode, select options as described in the following table:

-

- **Quick Mode (default)**

-|Value|Description|

-|:--|:--|

-|Select a query <br/> |Select a result source to specify which content should be searched. If you have shared a document library or list as catalog, the catalog result source will be displayed in this drop-down list. By default, this is set to **Recently changed items (System).** <br/> |

-|Restrict results by app <br/> |Select an option from the list to restrict results to a specific site, library, list, or URL. By default, this is set to **Current site**. <br/> |

-|Restrict by tag <br/> |You can limit results to content that is tagged with a term from a term set. <br/> |

-Select one of the following options:

-|Option|Description|

-|:--|:--|

-|Don't restrict by any tag <br/> |Search results will not be limited based on tags (default). <br/> |

-|Restrict by navigation term of current page <br/> |Search results will be limited to content that is tagged with the term of the current page. The current tag is displayed as the last part of the friendly URL. This option is only meaningful for sites that use managed navigation. <br/> |

-|Restrict by current and child navigation <br/> |Search results will be limited to content that is tagged with the term of the current page (displayed as the last part of the friendly URL), and content that is tagged with sub-terms of the current page. This option is only meaningful for sites that use managed navigation. <br/> Note that in a cross-site publishing scenario, this selection will only work when the result source selected in the **Select a query** section is the catalog result source that is created when a publishing site is connected to a catalog.|

-|Restrict on this tag <br/> |Search results will be limited to content that is tagged with the tag that you type inside the box. <br/> |

-

-

- - To create your own query by using Keyword Query Language (KQL), click **Switch to Advanced Mode**. For information about KQL, see [Keyword Query Language (KQL) syntax reference](/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). When you configure the query in Advanced Mode, you can also use query variables. Query variables are placeholders for values that change dynamically depending on the context of the page when the page that contains the Content Search Web Part is being displayed. The correct information is inserted dynamically from the context the query is sent to the index. Examples of query variables are {User.Name}, which represents the name of the user who is viewing the page, or {searchBoxQuery}, which represents the query that a user typed in a search box. Select options as described in the following table:

-

-

- **Advanced Mode**

-|Value|Description|

-|:--|:--|

-|Select a query <br/> |Select a result source to specify which content should be searched. <br/> Default result source is Local SharePoint Results (System). <br/> |

-|Keyword filter <br/> |You can use keyword filters to add query variables to your query. See [Query variables in SharePoint Server](../technical-reference/query-variables.md) for a list of available query variables. <br/> You can select pre-defined query variables from the drop-down list, and then add them to the query by clicking **Add keyword filter**. <br/> |

-|Property filter <br/> |You can use property filters to query the content of managed properties that are set to queryable in the search schema. <br/> You can select managed properties from the **Property filter** drop-down list. Click **Add property filter** to add the filter to the query. <br/> |

-|Query text <br/> |Type your query by using Keyword Query Language (KQL), or use the **Keyword filter** and **Property filter** lists to build the query. <br/> The keyword query can consist of free-text keywords, property filters, or operators. Use braces to enclose query variables. The query variables will be replaced with an actual value when the query is run. <br/> Keyword queries have a maximum length of 2,048 characters. <br/> |

-

-7. The **REFINERS** tab lists the managed properties that are enabled as refiners in the search schema. You can specify that the search results returned in the Content Search Web Part should be limited to one or more values from the refiners. Click a refiner in the list, and then click **Apply** to add it to the query.

-

-

-8. On the **SORTING** tab, you can specify how search results should be sorted.

-

-

- In the **Sort by** drop-down list, select a managed property from the list of managed properties that are set as sortable in the search schema, and then select **Descending** or **Ascending**. For example, to sort by relevance (that is, to use a ranking model) select **Rank**.

-

-

- > Sorting of search results is case sensitive.

-

- > If your result source contains sorting, you should not specify sorting in the Content Search Web Part. This is because the sorting in the result source overrides the sorting that you specify in the Content Search Web Part.

-

- If you selected **Rank** from the **Sort by** list, you can select which ranking model to use for sorting in the **Ranking Model** list.

-

- Under **Dynamic ordering**, you can specify additional ranking by adding rules that will change the order of results when certain conditions apply. Click **Add dynamic ordering rule**, and then specify conditional rules.

-

-9. On the **SETTINGS** tab, specify the settings that are listed in the following table.

-

-| Value | Description |

-|:--|:--|

-|Query Rules <br/> |Select whether to use Query Rules or not. <br/> |

-|URL Rewriting <br/> |Select if the URL rewrite to the item details page should continue to be relative for each catalog item as defined when you set up the catalog connection. If you select **Don't rewrite URLs**, the URLs for catalog items are pointed directly to the library item of the connected catalog. <br/> |

-|Loading Behavior <br/> |Select when the search results returned by the Content Search Web Part appear on the web page. The default option is **Sync option: Issue query from the server**. By using this loading behavior, queries are issued from the server, and the search results are included in the page response that is sent back from SharePoint Server. If you select **Async option: Issue query from the browser**, the queries will be issued from the end-users browser after the complete page is received. This option may be considered for secondary content on a page ΓÇö for example Recommendations or Popular Items. <br/> |

-|Priority <br/> |Select the level that best describes the relative importance of content that is displayed by this Web Part in relation to other Search Web Parts. If SharePoint Server is running under heavy load, the queries will be run according to their priority. <br/> |

-|Caching <br/> |Select one Active Directory security group if you want search results to be cached for users in the group. By caching search results for a security group, you can reduce page reload time. <br/> > [!NOTE]> You should only select a security group where search results are identical for all users in the group. For more information, see [this article](/archive/blogs/technet/helgesolheim/new-group-cache-for-the-content-search-web-part).|

-

-10. On the **TEST** tab, you can preview the query that is sent by the Content Search Web Part.

-

-|Value|Description|

-|:--|:--|

-|**Query text** <br/> | Shows the final query that will be run by the Content Search Web Part. It is based on the original query template where dynamic variables are substituted with current values. Other changes to the query may have to be made as part of query rules. <br/> |

-

-Click **Show more** to display additional information.

-

-|Value|Description|

-|:--|:--|

-|Query template <br/> |Shows the content of the query template that is applied to the query. <br/> |

-|Refined by <br/> |Shows the refiners applied to the query as defined on the **REFINERS** tab. <br/> |

-|Grouped by <br/> |Shows the managed property on which search results should be grouped as defined on the **REFINERS** tab. <br/> |

-|Applied query rules <br/> |Shows which query rules are applied to the query. <br/> |

-

-The **Query template variables** section shows the query variables that will be applied to the query, and the values of the variables that apply to the current page. You can type other values to test the effect they will have on the query. Click the **Test Query** button to preview the search results.

-

-You can also test how the query works for different user segment terms. Click **Add user segment term** to add terms to be added to the query. Click the **Test query** button to preview the search results.

-

-|Value|Description|

-|:--|:--|

-|Query text <br/> |Shows the final query that will be run by the Content Search Web Part. It is based on the original query template where dynamic variables are substituted with current values. Other changes to the query may have to be made as part of query rules. <br/> |

-

-

-

-

-

-

-

-

-

- **To add a Refinement Web Part to a page**

-

-1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the publishing site collection.

-

-

-3. Click the **Settings** menu, and then click **Edit Page**.

-

-

-

-

- **To configure the Refinement Part**

-

-

-

-

-4. In the Web Part, click the **Refinement Web Part Menu** arrow, and then click **Edit Web Part**.

-

-

- - To configure the Web Part for stand-alone refiners:

-

-1. In the Web Part tool pane, in the **Properties for Search Refinement** section, verify that the **Choose Refiners in this Web Part** is selected.

-

-2. Click **Choose Refiners…**

-

-3. On the **Refinement configuration** page, from the **Available refiners** section, use the buttons to select which refiners should be added to the term set, and also in which order that they should be displayed. If you have specified an alias for a refinable managed property, this alias is displayed in the **Configuration for** section.

-

-4. In the **Configuration for** section, set the configuration for how every refiner appears.

-

- > If you have a single language site, you can change the refiner display name in the **Display name** section. For multilingual sites, you have to change the refiner display language as described in [Change the refiner display name](configure-search-web-parts.md#BKMK_ChangeDisplayName).

-

- - To configure the Web Part for refiners for faceted navigation:

-

-1. In the Web Part tool pane, in the **Properties for Search Refinement** section, select the option **Use the refinement configuration defined in the Managed Navigation term set**.

-

-

- **To change the refiner display name**

-

-1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the publishing site collection.

-

-

-3. On the **Site Settings** page, in the **Web Designer Galleries** section, click **Master pages and page layouts**.

-

-

-

-6. On the **Language Files** page, click the folder that contains the language that you want to change the refiner display name for.

-

-7. Open the **CustomStrings.js** file.

-

-8. Add one line to the file for each managed property that is enabled as a refiner for which you want to change the display name by using the following syntax:

-

-

- For example, you can add the following line to change the display name for the managed property RefinableInt00 to Price:

-

-

-When you add a Refinement Web Part to a page, by default, the Web Part will not show refiner counts ΓÇö that is, the number of items for each refiner value. For example, if you have enabled the managed property Color as a refiner, the refiner values will only show colors such as Red, Green, and Blue. You can add refiner counts by changing a value in an HTML file so that the refiner values are shown as Red (10), Green (12), and Blue (8).

-

- **To add refiner counts to the Refinement Web Part**

-

-1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the publishing site collection.

-

-

-3. On the **Site Settings** page, in the **Web Designer Galleries** section, click **Master pages and page layouts**.

-

-

-

-6. Open the **Filter_Default.html** file.

-

-

-

- **To view display templates for the Refinement Web Part**

-

-

-

-3. On the **Site Settings** page, in the **Web Designer Galleries** section, click **Master pages and page layouts**.

-

-

-

-

-Before you begin this procedure, verify the following:

-

-

-

-

- **To add a Taxonomy Refinement Panel Web Part to a page**

-

-

-

-3. Click the **Settings** menu, and then click **Edit Page**.

-

-

-

-

- **To configure the Taxonomy Refinement Panel Web Part**

-

-

-

-

-4. In the Web Part, click the **Taxonomy Refinement Panel Web Part Menu** arrow, and then click **Edit Web Part**.

-

-5. In the Web Part tool pane, in the **Properties** section, in the **Query** section, on the **Refinement Target** menu, select the Web Part you want to associate with the Taxonomy Refinement Panel Web Part.

-

-6. In the Web Part tool pane, in the **Properties** section, in the **Query** section, on the **Refiner** menu, select the managed property that you have specified for Managed Navigation.

-

-You can use the Recommended Items Web Part to show content recommendations based how users have previously interacted with the site. For example, you can add this Web Part to a Catalog Item page. If a user views a specific item, this Web Part will display other items that users have previously viewed, such as "Users who viewed this item also viewed these items." For more information about recommendations, see [Plan usage analytics, usage events and recommendations](plan-search-for-sharepoint-cross-site-publishing-sites.md#BKMK_PlanAnalytics) in [Plan search for cross-site publishing sites in SharePoint Server 2016](plan-search-for-sharepoint-cross-site-publishing-sites.md).

-

- **To add a Recommended Items Web Part to a page**

-

-

-

-

-

-

-

- **To configure the query for a Recommended Items Web Part**

-

-

-

-

-4. In the Web Part, click the **Recommended Items Web Part Menu** arrow, and then click **Edit Web Part**.

-

-

-6. On the **BASICS** tab, define your query by selecting options described in the following table.

-

-|Value|Description|

-|:--|:--|

-|Get recommended items for <br/> |From the drop-down list, select from which value recommendations should be displayed. In a catalog scenario, this will often be **A token from a URL**. If you select this option, you will also have to select which URL token you want to obtain recommendations for. <br/> For example, let's say that you want to obtain recommendations for items in your catalog. You have a catalog item page where you display your catalog items, and the item number is part of your friendly URL ΓÇö for example, www.contoso/audio/mp3/4010101. (4010101 represents the item number.) When you want to obtain recommendations for a token from the URL, you should select {URLToken.1} (4010101) from the second drop-down list. <br/> |

-|Restrict results by app <br/> |Use this drop-down list to specify a scope for the search results. <br/> |

-|Restrict results by content type <br/> |Use this drop-down list to limit the search results to a specific content type. <br/> |

-|If there are too few recommended items <br/> |If you don't have much usage data ΓÇö for example, if your site is fairly new, or if the items do not have recommendations to display ΓÇö this Web Part will not display any search results. In order for the Web Part to display recommendations even though not enough user data has cumulated, you can select the option to **Select a query to fill in with additional results**. <br/> |

-

-7. The **REFINERS** tab lists the managed properties that are set as refiner-enabled in the search schema. You can specify that the search results returned in the Recommended Items Search Web Part should be limited to one or more values from the refiners. Click a refiner in the list, and then click **Apply** to add it to the query.

-

-

-8. On the **SETTINGS** tab, specify the following:

-

-|Value|Description|

-|:--|:--|

-|Query Rules| Select whether to use Query Rules or not. |

-|URL Rewriting|Select if the URL rewrite to the item details page should continue to be relative for each catalog item as defined when you set up the catalog connection. If you select **Don't rewrite URLs**, the URLs for your catalog items are pointed directly to the library item of the connected catalog.|

-|Loading Behavior|Select when the search results returned by the Recommended Items Web Part should be displayed on the web page. The default option is **Display the page and web party simultaneously**. By using this loading behavior, queries are issued from the server, and the search results are included in the page response that is sent back from SharePoint Server. If you select **Display the page and web part independently**, the queries will be issued from the end-users browser after the complete page is received. This option may be considered for secondary content on a page ΓÇö for example, Recommendations or Popular Items|

-|Priority|Select the level that best describes the relative importance of content that is displayed by this Web Part in relation to other Search Web Parts. If SharePoint Server is running under heavy load, the queries will be run according to their priority.|

-|Caching|Select one Active Directory security group if you want search results to be cached for users in the group. By caching search results for a security group, you can reduce page reload time.> [!NOTE]> You should only select a security group where search results are identical for all users in the group. For more information, see [this article](/archive/blogs/technet/helgesolheim/new-group-cache-for-the-content-search-web-part).|

-

-9. On the **TEST** tab, you can preview the query that is sent by the Recommended Items Web Part.

-

-|Value|Description|

-|:--|:--|

-|Query text <br/> |Shows the content of the query template that is applied to the query. <br/> |

-

-Click **Show more** to display additional information.

-

-|Value|Description|

-|:--|:--|

-|Refined by <br/> |Shows the refiners applied to the query as defined in the **REFINERS** tab. <br/> |

-|Grouped by <br/> |Shows the managed property on which search results should be grouped as defined in the **REFINERS** tab. <br/> |

-|Applied query rules <br/> |Shows which query rules are applied to the query. <br/> |

-

-In the **Query template variables** section, the selections that you made on the BASIC tab are displayed. In addition, you can type additional values for testing as outlined in the following table. Click the **Test query** button to preview the search results.

-

-|Value|Description|

-|:--|:--|

-|{RecsURL}\* <br/> |Shows the token you selected when specifying for which value recommendations should be displayed. <br/> |

-|{Scope}\* <br/> |Shows the scope that you selected for the search results. <br/> |

-|{ContentTypeID}\* <br/> |Shows the content type that you selected for the search results. <br/> |

-

-You can also test how the query works for different user segment terms. Click **Add user segment term for testing** to add terms to be added to the query. Click the **Test query** button to preview the search results.

-

-|Value|Description|

-|:--|:--|

-|Query text <br/> |Shows the final query that will be run by the Recommended Items Web Part. It is based on the original query template where dynamic variables are substituted with current values. Other changes to the query may have be made as part of query rules. <br/> |

-

-

-

-

-#### Concepts

-#### Other Resources

-[Blog series: How to set up a product-centric website in SharePoint Server 2013](https://blogs.technet.com/b/tothesharepoint/archive/2013/02/14/how-to-set-up-a-product-centric-web-site-in-sharepoint-2013.aspx)

-2. To open the **Sort (Category)** dialog, select **More Sort Options…**.

-3. In the **Connection Properties** dialog, on the **Definition** tab, next to **Excel Services**, select **Authentication Settings…**.

-|**For the authentication operation to succeed …** <br/> | Kerberos delegation must be set up on the SharePoint Server 2013. <br/> | The Secure Store Service must be provisioned and configured on the farm. It must also contain appropriate mapping information for a particular incoming user. Additionally the mapping information may need to be updated periodically to reflect password changes on the mapped account. <br/> | The Secure Store Service must be provisioned and configured on the farm. It must also contain the credentials for the Unattended Service Account. Additionally the mapping information may need to be updated periodically to reflect password changes on the mapped account. <br/> Excel Services Global Settings must be configured to use the Unattended Service Account. <br/> | The **EffectiveUserName** option must be enabled in Excel Services Global Settings. <br/> The user must be a member of the appropriate Analysis Services role. <br/> |

-|For the authentication operation to succeed … <br/> | Kerberos constrained delegation must be set up on the SharePoint farm. <br/> | Secure Store must be provisioned and configured on the farm. It must also contain appropriate mapping information for a particular incoming user. Additionally the mapping information may need to be updated periodically to reflect password changes on the mapped account. <br/> | Secure Store must be provisioned and configured on the farm. It must also contain the credentials for the Unattended Service Account. Additionally the mapping information may need to be updated periodically to reflect password changes on the mapped account. <br/> The Unattended Service Account must be configured in Visio Services Global Settings. <br/> |

-When modern authentication (a trusted identity provider) such as SAML 1.1 or OIDC 1.0 is used, the People Picker control canΓÇÖt search, resolve, and validate users and groups without writing a custom claim provider through C#.

- > This parameter canΓÇÖt be used to create an OIDC SPTrustedTokenIssuer.

- - There should be two agents inside the MIM synchronization Manager UX after MIM is set up. One agent is used to import user profiles from the source IDP to the MIM database. And another agent is used to export user profiles from the MIM database to the SharePoint User Profile service application.

-> [!Note]

- $tokenissuer = New-SPTrustedIdentityTokenIssuer -ClaimsMappings $sidClaimMap, $emailClaimMap …

- - For MIM synchronization, take the property mapping from the identity provider to MIM and then from MIM to the SharePoint User Profile service application so that MIM can synchronize the group **SID** from the identity provider to the SharePoint User Profile service application. ItΓÇÖs like how we do user profile synchronization for the **SPS-ClaimID** property for user profiles.

-

-

-

-Excel Services consists of Excel Calculation Services, the Excel Web Access Web Part, and Excel Web Services for programmatic access. It supports sharing, securing, managing, and using Excel workbooks in a browser by providing the following:

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-|&nbsp;|**SharePoint Server only**|**SharePoint Server with Excel Web App (SharePoint view mode)**|**SharePoint Server with Excel Web App (Office Web Apps Server view mode)**|

-|Excel Web Access Web Part <br/> |× <br/> |× <br/> ||

-|Refresh OData connections <br/> |× <br/> |× <br/> ||

-|View and interact with Power View reports <br/> |× <br/> |× <br/> ||

-|View and interact with Power Pivot data models <br/> |× <br/> |× <br/> ||

-|Refresh Power Pivot data models <br/> |× <br/> |× <br/> ||

-|Refresh data by using the Excel Services unattended service account <br/> |× <br/> |× <br/> ||

-|Refresh data by using Secure Store and Windows credentials <br/> |× <br/> |× <br/> |× <br/> |

-|Refresh data by using Effective User Name connections <br/> |× <br/> |× <br/> ||

-|Kerberos delegation <br/> |× <br/> |× <br/> ||

-

-#### Concepts

-

-That might not have been as straightforward as our simple example, and there is one exception to the rule…

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

- > This is shown on users' profile page when they fill in the **Ask Me About** field on their profile.

-

-

-

-

-> None of the procedures in this article remove the SharePoint Server enterprise social features and functionality permanently. The features are kept to let future upgrades of SharePoint Server finish successfully.

-

-

-

-

-

-

-

-

-

-

-

- > When the changes in this article are deployed, users can continue to use and fill in fields in the **Newsfeed Settings** page. But the information is no longer shown on My Site. However, information in the **Basic Information** and **Contact Information** pages are still shown on My Site.

-

-##SharePoint Server 2016

-###Remove Newsfeed Web Parts from Team Sites in SharePoint Server 2016

-1. From any site in SharePoint Server 2016 that has a Newsfeed web part, select **Edit**.

-3. On the ribbon, chose the **Web Part** tab, and then select **Delete**.

-

-5. On the ribbon, select the **Page** tab, and then select **Stop Editing**, and to save your changes, select **Save**.

-

-###Remove Newsfeed Web Parts from My Sites in SharePoint Server 2016

-1. Move the pointer over the **Newsfeed** Web Part, and select the box that appears on the right side of the Web Part.

-

-

-

-4. Repeat steps 2-4 for the **Followed Counts** and **Trending Hashtags** Web Parts.

-

-

-2. Hover over the **Site Feed** Web Part, and select the box that appears to the right of the Web Part.

-

-

-

-

-6. Check that the team site no longer shows the **Site Feed** Web Part.

-

-

-1. From any site in SharePoint Server 2013, to browse to a user's My Site, select **Newsfeed**.

-

-

-3. Move the pointer over the **Newsfeed** Web Part, and select the box that appears on the right side of the Web Part.

-

-

-

-6. Repeat steps 3-5 for the **Followed Counts** and **Trending Hashtags** Web Parts.

-

- > It's a good idea to remove all social Web Parts, hidden or not hidden, to improve performance.

-

-7. On the ribbon, to save your changes, select **Stop Editing**.

-

-

-

-9. To open the user's profile page, select **About me**.

-

-

-11. Move the pointer over the **Activity Feed** Web Part, and select the box that appears on the right side of the Web Part.

-

-

-

-14. On the ribbon, to save your changes, select **Stop Editing**.

-

-15. Check that the user's profile page no longer shows the **Activity Feed** Web Part.

-

-

-

-

-

-

-> To register the CSS file for a custom Master Page, you have to have Contribute permission on the My Site host site. To register the CSS file for an out-of-box Master Page, you have to be a farm admin to install the required custom delegate control, and you also need Site Owner permissions on the My Site to enable the control for that site.

-

-

-

-

-

-

- **Create the HideNewsfeed.css file**

-

-

-

-

-

- ```

- /* Hide the following SP Social features */

- /* Hide the microfeed div in MySite and team sites */

- #ms-microfeeddiv,

- /* Hide the Followed counts div in MySite */

- .ms-profile-followedCountDiv,

- /* Hide the trending tags div in MySite */

- .ms-mysite-contentBox .ms-mpSearchBox+.ms-webpart-zone,

- /* Hide the follow button on others' About Me page */

- /* Hide the ask me about option on the About Me page */

- #ms-profile-followLinkDiv, .ms-askMeAbout-valuesMoreThanFive, .ms-askMeAbout-valuesFooter,

- .ms-askMeAbout-bulletImage, .ms-askMeAbout-valuesFiveOrLess,

- /* Hide the follow tag option from the landing page */

- .ms-followedTags-followTag,

- /* Hide the follow people option from the landing page */

- .ms-people-followMultiplePeople{

- display:none!important;

- }

- ```

-

-

-

-

-

-

-

- **Register the CSS file for a custom Master Page**

-

-

-2. Copy and paste the following code into the Master Page immediately before the `</head>` tag:

-

- ```

- <SharePoint:CssRegistration ID="HideNewsfeedCssRegistration" Name="<% $SPUrl:~SiteCollection/Style Library/HideNewsfeed.css %>" runat="server" After="corev15.css" />

- ```

-

-

- **Register the CSS file for an out-of-box Master Page**

-

-

-

-

-

-

-

-

-

-

-

-

-

- ```

- <SharePoint:CssRegistration ID="HideNewsfeedCssRegistration" Name="<% $SPUrl:~SiteCollection/Style Library/HideNewsfeed.css %>" runat="server" After="corev15.css" />

- ```

-

-

-

-

-

-

- ```

- <?xml version="1.0" encoding="utf-8"?>

- <Elements xmlns="http://schemas.microsoft.com/sharepoint/">

- <Control Id="AdditionalPageHead" ControlSrc="~/_CONTROLTEMPLATES/15/HideNewsfeed/HideNewsfeed.ascx"ΓÇ»/>

- </Elements>

- ```

-

-

-

- The result is a SharePoint solution package that can be deployed and activated on the My Site Host site.

-

-

-

-

- > Instead of uploading the HideNewsfeed.css to the Style Library, you can create the CSS file in the SharePoint Solution package so that it is deployed together with the solution.

-

-24. Browse to the **Newsfeed** page to check that the controls are no longer shown on the page.

-

-

-

-

-Integrating social media within your organization can help you reach your organization's goals. The integration can be done on your organization's intranet to increase transparency, but you can also make social networks a part of your public-facing website to expand reach and increase conversion of your website.

-

-

-

-

-

-

-Integrating with social media is all about reaching as many people as possible. Information about the content on your website, whether it is articles, blog posts or products, when discovered and found valuable, it can be shared by your visitors with their friends, who again might share it with their friends. Before you know it, your content will reach people who otherwise might not have even known about your website. But, for this to occur, you have to to make sure that that when your content is shared on social networks, it looks exactly the way that you want it to look.

-

-Just as you can optimize your web content for Internet search engines, you can provide some meta information about your content to social networks. Many social networks such as Facebook or Yammer use [the Open Graph protocol](https://go.microsoft.com/fwlink/p/?LinkId=400785) to retrieve information about your content. To control how your content is displayed when it is shared on social networks, you have to integrate Open Graph metadata into your website. The metadata should describe the essence of your content so that anyone who sees your content on a social network will want to click on it.

-

-Publishing Open Graph metadata for a website that is built with SharePoint Server 2016 isn't complex. But there are several things that you should consider. First of all Open Graph defines different types of web content - similar to what you can achieve with Content Types in SharePoint. Before you start integrating Open Graph into your website, you should have a good understanding of what types of content that you have on your website, and how it can be described most effectively by using Open Graph.

-

-Next to the different types of content that you can publish on your website, there are also differences in how that content is published. SharePoint Server 2016 offers two content publishing models:

-

-

-

-These publishing models have two ways of publishing content and, depending on which one that you are using on your website, you should plan for publishing the information according to your content publishing model.

-

-Open Graph information is published using HTML meta tags. Those tags must be located in the head section of your website. To support publishing different Open Graph information for different types of pages and content publishing models, you should define a Content Place Holder in your Master Page. This will allow you to fill that placeholder with the appropriate metadata from the different Page Layouts.. The following code example shows a Content Place Holder added to the standard seattle.master Master Page to support publishing Open Graph information:

-

-```

-…

-…

-According to the Open Graph protocol there are four properties that are required for every web page: *title* , *type* , *image* , and *URL* . Although Open Graph defines several content types, if you are not publishing information about video or audio, the odds are high that you'll be using the *article* type for most your web pages. Because not every page is an article, you might want to use the website type. The website type is the default type if no type is specified. To simplify working with Open Graph we could expand the code example above by adding the information about the title, URL and type. This would prevent us from repeating the same code example within each Page Layout.

-

-Although the basic Open Graph information is a part of the SEO information published by SharePoint Server 2016, standard SharePoint Server 2016 SEO controls cannot be used directly to display this information on Master Pages and Page Layouts as Open Graph meta tags. To use those controls for publishing Open Graph metadata, we have built a set of wrapper controls and them published together with this article to explain how you can build similar wrapper controls.

-

-By using Search Engine Optimization capabilities of SharePoint Server 2016 we can retrieve the information about the page as follows:

-

-```

-…

-…

-This approach assumes that you want the title of your page to be published on social networks exactly like it is displayed in the title bar of a web browser. Should your scenario differ, you can replace the contents of the title property with a suitable alternative, or remove it, and then have it filled from the *OpenGraphPlaceHolder* content placeholder.

-

-The great benefit of using the standard SharePoint Server 2016 Search Engine Optimization controls, as shown above, is that they work for both classic in addition to search-driven content publishing model and will automatically retrieve the necessary content by using the necessary approach.

-

-The next step is to provide the page-type specific information according to the Open Graph protocol. For pages using the classic publishing model, you can use Publishing controls to retrieve the content, for example:

-

-```

-When using search-driven publishing you would use Catalog Item Reuse Web Parts instead:

-

-```

-When using cross-site publishing, in most scenarios the content of the detail pages, which is named catalog item page, is surfaced from the search index and can be retrieved as shown above.The content of overview pages, which are named category pages, is determined by the information coming from the Managed Metadata Service. Should you have to retrieve information from your taxonomy to display it as part of your Open Graph manifest, you can do so by using the *TermProperty* control:

-

-```

-Different social networks support different metadata. Depending on which social network that you want to integrate with your website, you should verify the relevant API. By using the techniques showed above, you can provide relevant information about your web pages, and to make sure that good presentation of your content on social networks.

-

-Having configured the basic information about our web pages, let's explore the different integration capabilities offered by social networks. For brevity we'll focus on Facebook, but presented mechanisms could apply to other social networks also.

-

-

-

-

-

-

-First there is the Facebook SDK call that should be included one time per page directly after the *body* tag:

-

-```

-

-```

-

-

-

-```

-

-According to the Like Button guidelines, the Like Button has to contain the absolute URL of the page on which it is integrated. In the code sample that was mentioned earlier the absolute URL is included in the *data-href* attribute. Because we want to place the code on the Page Layout we don't want to include a fixed URL. Instead we want to insert the URL of the current page rendered using the Page Layout. Considering that SharePoint Server 2016 offers support for physical and Friendly URLs, the best way to get the URL of the current page is to use the SharePoint Server 2016 Canonical URL control. Combined with the Like Button HTML code example, it would look as follows:

-

-```

-

-

-

-

-

-

-

-Giving your visitors the ability to use Facebook to comment on your content, can be of great benefit both to you and your visitors. Although it might depend on the audience of your website, many people have a Facebook account nowadays. It is easier for them to use their existing Facebook profile to leave a comment on your website instead of in following another registration process.

-

-

-

-

-

-```

-Similarly to the Facebook Like button, the *data-href* attribute should contain the absolute URL of the page for which you want to provide the commenting capability. As this is very likely to be the current page, you could again benefit of the *SeoCanonicalLink* control to retrieve the URL of the current page:

-

-```

-

-

-Using the Activity Plugin can help your visitors discover new content and with that help you expand the reach of your website. When your visitors are logged in with Facebook, the Activity Feed will show activities that your visitors' friends have made. As most of the time those are all people who your visitors know and trust. Therefore, the odds are high that they will follow their recommendations and discover new content on your website. If they are not logged in on the other hand, the Activity Feed plugin will show recommendations from across your site and of course suggest logging in to Facebook to show more relevant content.

-

-

-```

-

-Although you could place the Activity Feed on every page on your website, there is a chance that this would work against you and distract your visitors from your content. Because the Activity Feed allows you to expand the reach of your website, it might be a better idea to analyze your web analytics data and place the Activity Feed somewhat more strategically, for example on the frequent exit pages and landing pages such as the home page.

-

-

-

-A slightly different, nevertheless very interesting, plugin is the Recommendations Bar. This plugin can also help you expand the reach of your website by displaying recommended content. What's different about the Recommendations Bar is its usage scenario.

-

-

-

-```

-Because you want recommendations to be visible on every page, you should add it to the Page Layouts used by your detail pages. The following is the markup that you should add to your Page Layouts to to make sure that that the Recommendations Bar will work for every page. Notice how the contents of the *data-href* attribute are being set dynamically by using the SeoCanonicalLink control we discussed previously:

-

-```

-

-An alternative to integrating the Facebook Recommendations Bar that is worth considering is using the content recommendations capability that was provided with SharePoint Server 2016. Although it would require some customizations to achieve similar user experience as the one that Facebook Recommendations Bar has, the great advantage is that you can control which content is displayed as recommendations. Because content recommendations are based on SharePoint Server 2016 Search, you can use all its capabilities to to make sure that that the most relevant recommendations are displayed to your visitors.

-

-## Bonus:Yamming it!

-

-Although Yammer doesn't offer as many plugins as Facebook does, one thing that you could easily include in your website is a *Yam it* button. The Yam it button gives your visitors to share the page that they are currently visiting with their Yammer network with a single mouse click. The following is sample code of a *Yam it* button:

-

-```

-The *Yam it* button is completely based on JavaScript so you can include the previous snippet directly in SharePoint without changing it. From the integration perspective the *Yam it* button can be best compared with the Facebook Like button. So wherever you feel it is right to include the Facebook Like button, it is probably a good place to include the *Yam it* button also.

-

-

-

-

-This article provides security guidance and recommendations to help ensure that access to SharePoint Server 2013 and specific data in SharePoint is not compromised on a mobile device. This article also details the supported authentication types for select devices, and authentication specifics for the SharePoint Newsfeed App.

-

-

-

-

-

-

-

-

-

-| Exchange ActiveSync policy | Description |

-|:--|:--|

-|Remote wipe (this is a feature and not an Exchange ActiveSync policy) <br/> |If a mobile phone is lost, stolen, or otherwise compromised, you can issue a remote wipe command from the Exchange computer or from any web browser by using Outlook Web App. This command restores the device to factory defaults. <br/> > [!IMPORTANT]> After a remote device wipe has occurred, data recovery is very difficult. However, no data removal process leaves a device as free from residual data as when it is new. Recovery of data from a device may still be possible using sophisticated tools. |

-|Enforce password on device (DevicePasswordEnabled) <br/> |This setting enables the mobile phone password. <br/> |

-|Minimum password length (MinDevicePasswordLength) <br/> |This option specifies the length of the password for the mobile phone. The default length is 4 characters, but as many as 18 can be included. <br/> |

-|Require alphanumeric password (AlphanumericDevicePasswordRequired) <br/> |This setting requires that a password contains numeric and non-numeric characters. <br/> |

-|Allow simple password (AllowSimpleDevicePassword) <br/> |This setting enables or disables the ability to use a simple password such as 1234. <br/> |

-|Maximum inactivity time lock (MaxInactivityTimeDeviceLock) <br/> |This option determines how long the mobile phone must be inactive before the user is prompted for a password to unlock the mobile phone. <br/> |

-

-

-

-

-

-

-

-

-> To learn more about the Find My Phone service for Windows Phone, see [Find a lost phone](https://support.microsoft.com/help/17240/windows-10-mobile-find-phone).

-

-

-

-

-

-The following tables detail the authentication types supported for browsers, OneDrive, and the Office Hub Windows Phone experience in SharePoint Server 2013. For the below, OrgID refers to Microsoft Online Services ID, the identity provider for Microsoft 365. Also, MSOFBA refers to Microsoft Office Forms Based Authentication.

-

-| SharePoint Infrastructure | Mobile Devices |

-|--|--|

-|**Authentication Type** <br/> |**Authentication Protocol** <br/> |**ID Provider** <br/> |**SharePoint deployment** <br/> |**Windows Phone 7.5 (Internet Explorer Mobile)** <br/> |**Windows Phone 8 (Internet Explorer Mobile)** <br/> |**Windows 8 (Internet Explorer)** <br/> |**iOS 5.x or later versions (Safari Browser)** <br/> |**Android 4.x or later versions (Android Browser** ) <br/> |

-|**Windows Authentication** <br/> |NTLM <br/> |Active Directory <br/> |On-premises <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |

-|Basic Authentication <br/> |Active Directory <br/> |On-premises, extranet <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |

-|**Forms-Based Authentication (FBA)** <br/> |FBA <br/> |Active Directory, LDAP, SQL <br/> |On-premises, extranet <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |

-|FBA <br/> |OrgID <br/> |SharePoint in Microsoft 365, hybrid-based scenarios <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |

-|**SAML (Token-based)** <br/> |SAML <br/> |WS-Federation 1.1 compatible Identity Provider <br/> |On-Premises, SharePoint in Microsoft 365, hybrid-based scenarios <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |Yes <br/> |

-

-| Authentication type | Description | Supported | Administrator type required for configuration |

-|:--|:--|:--|:--|

-|**Org-ID** <br/> |Organizations with a Microsoft 365 or SharePoint organization without any federation. <br/> |Yes <br/> |Global admin <br/> |

-|**ADFS and Org-ID federation** <br/> |Organizations with a hybrid Microsoft 365 or SharePoint organization with users federated from an on-premises directory. <br/> |Yes <br/> |Global admin plus the on-premises network administrator plus the SharePoint admin <br/> |

-|**Windows authentication (NTLM)** <br/> |Organizations with a SharePoint environment configured to allow NTLM claims-based Windows authentication. <br/> |Yes <br/> |SharePoint admin <br/> |

-|**Forms-based authentication (FBA)** <br/> |Organizations with a SharePoint environment configured to allow Forms-based authentication or other compatible claims-based authentication via a standard web control. <br/> |Yes <br/> |SharePoint admin <br/> |

-|**Qualified non-ADFS identity providers** <br/> |Organizations with a Microsoft 365 or SharePoint environment configured to allow user sign-in that is federated with an identity provider qualified for rich clients in the [Works with Microsoft 365 - Identity program](https://go.microsoft.com/fwlink/p/?LinkId=511982). <br/> |Yes <br/> |SharePoint admin plus the on-premises Network administrator or Global admin (in some organizations the Global admin is a requirement, not an option.) <br/> |

-|**All other non-ADFS identity providers** <br/> |Organizations with a SharePoint environment configured to allow a non-ADFS identity provider. <br/> |No <br/> |SharePoint admin plus the on-premises network administrator <br/> |

-|**Kerberos authentication** <br/> |Organizations with a SharePoint environment configured to support Kerberos authentication. <br/> |No <br/> |SharePoint admin plus the on-premises network administrator <br/> |

-|**Basic authentication** <br/> |Organizations with a SharePoint environment configured to support Basic authentication. <br/> |No <br/> |SharePoint admin plus the on-premises network administrator <br/> |

-

-> If you're a Microsoft 365 multi-organization user, you can connect from the OneDrive app in any network environment, including Wi-Fi and cellular data. If you're not a Microsoft 365 multi-organization user, you can connect only when using your organization's on-site Wi-Fi network. If you're unsure which user you are, contact your SharePoint admin.

-

-| SharePoint Infrastructure | Client side | Mobile devices |

-|--|--|--|

-|**Authentication Type** <br/> |**Authentication Protocol** <br/> |**ID Provider** <br/> |**SharePoint deployment** <br/> |**Handled through:** <br/> |**Windows Phone 7.5 (Internet Explorer Mobile)** <br/> |**Windows Phone 8 (Internet Explorer Mobile)** <br/> |

-|**Windows Authentication** <br/> |NTLM <br/> |Active Directory <br/> |On-premises <br/> |NTLM <br/> |Yes <br/> |Yes <br/> |

-|Basic Authentication <br/> |Active Directory <br/> |On-premises, extranet <br/> |Basic Authentication <br/> |No <br/> |Yes (https) <br/> |

-|**Forms-Based Authentication (FBA)** <br/> |FBA <br/> |Active Directory, LDAP, SQL <br/> |On-premises, extranet <br/> |MSOFBA <br/> |Yes <br/> |Yes <br/> |

-|FBA <br/> |OrgID <br/> |SharePoint, hybrid-based scenarios <br/> |MSOFBA <br/> |Yes <br/> |Yes <br/> |

-|FBA <br/> |OrgID <br/> |SharePoint, hybrid-based scenarios <br/> |Active Authentication(IDCRL) <br/> |No <br/> |Yes <br/> |

-|**SAML (token-based)** <br/> |SAML <br/> |WS-Federation 1.1 compatible Identity Provider <br/> |On-premises, SharePoint, hybrid -based scenarios <br/> |MSOFBA <br/> |Yes <br/> |Yes <br/> |

-|SAML <br/> |WS-Federation 1.1 compatible Identity Provider <br/> |On-premises, SharePoint in Microsoft 365, hybrid-based scenarios <br/> |Active Authentication(IDCRL) <br/> |No <br/> |Yes <br/> |

-

-> For mobile devices to communicate with SharePoint servers, Internet Protocol Security (IPSec) must be disabled on the servers. The reason this must be done is that mobile devices are not domain-joined.

-

-This section provides authentication guidance and considerations for the SharePoint Newsfeed app. This includes information for on-premises based deployments, and using SharePoint in Microsoft 365.

-

- **Authentication support for the SharePoint Newsfeed App**

-

-

-**Table: Mobile authentication support matrix for the SharePoint Newsfeed App**\

-| SharePoint Infrastructure | Client side | Mobile devices |

-|--|--|--|

-|**Authentication Type** <br/> |**Authentication Protocol** <br/> |**ID Provider** <br/> |**SharePoint deployment** <br/> |**Handled through:** <br/> |**Windows Phone 7.5 Apps** <br/> |**Windows Phone 8 Apps** <br/> |**Windows 8 Apps** <br/> |**iOS 6.x or later versions Apps** <br/> |

-|**Windows Authentication** <br/> |NTLM <br/> |Active Directory <br/> |On-premises <br/> |NTLM <br/> |No <br/> |No <br/> |Yes <br/> |Yes <br/> |

-|Basic Authentication <br/> |Active Directory <br/> |On-premises, extranet <br/> |Basic Authentication <br/> |Yes <br/> |Yes <br/> |No <br/> |Yes (https) <br/> |

-|**Forms-Based Authentication (FBA)** <br/> |FBA <br/> |Active Directory, LDAP, SQL <br/> |On-premises, extranet <br/> |MSOFBA <br/> |Yes <br/> |Yes <br/> |No <br/> |Yes <br/> |

-|FBA <br/> |OrgID <br/> |SharePoint, hybrid-based scenarios <br/> |MSOFBA <br/> |Yes <br/> |Yes <br/> |No <br/> |Yes <br/> |

-|FBA <br/> |OrgID <br/> |SharePoint, hybrid-based scenarios <br/> |Active Authentication(IDCRL) <br/> |No <br/> |No <br/> |Yes <br/> |Yes <br/> |

-|**SAML (token-based)** <br/> |SAML <br/> |WS-Federation 1.1 compatible Identity Provider <br/> |On-premises, SharePoint in Microsoft 365, hybrid-based scenarios <br/> |MSOFBA <br/> |Yes <br/> |Yes <br/> |No <br/> |Yes <br/> |

-|SAML <br/> |WS-Federation 1.1 compatible Identity Provider <br/> |On-premises, SharePoint in Microsoft 365, hybrid -based scenarios <br/> |Active Authentication(IDCRL) <br/> |No <br/> |No <br/> |Yes <br/> |Yes <br/> |

-

-> For federated scenarios in SharePoint in Microsoft 365, only Active Directory Federation Services (ADFS) 2.0 is supported. During the setup process it is necessary to support a passive federation authentication URI of: *"urn:oasis:names:tc:SAML:2.0:ac:classes:Password"* .

-

- **Authentication Workflows**

-

-The SharePoint Newsfeed App is supported for both on-premises and SharePoint in Microsoft 365 use. Each option can present differences with end user authentication workflow. For example, this table provides sample authentication experiences for each type of implementation.

-

-| Deployment | Workflow | Details |

-|:--|:--|:--|

-|**On-premises** <br/> || Supported Authentication Types <br/> Windows Authentication <br/> Forms Based Authentication <br/> SAML <br/> |

-|**SharePoint in Microsoft 365** <br/> || Supported Authentication Types <br/> Forms-based Authentication <br/> SAML <br/> |

-

-

-#### Concepts

-

-

-

-

-

-

-

-

-

- On the Central Administration home page, click **Monitoring**, **Timer Jobs**. SharePoint Server uses configurable timer jobs to collect health data and then writes the data to the logging folder and to the Logging database. The data is then used in reports to display the health status of the farm servers.

-

-

- > Running timer jobs at the same time on all servers on the farm can affect system performance. You should plan timer jobs carefully to avoid overlap with other timer jobs.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

- SQL Server Reporting Services provides a full range of ready-to-use tools and services to help you create, deploy, and manage reports for your organization. It also has programming features that let you extend and customize reporting functionality. By using SQL Server Reporting Services, you can create interactive, tabular, graphical, or free-form reports from relational, multidimensional, or XML-based data sources. You can publish reports, schedule report processing, or access reports on-demand. You can use SQL Server Reporting Services to create reports based on predefined models, and to interactively explore data within the model. You can select from a variety of viewing formats, export reports to other applications, and subscribe to published reports. The reports that you create can be viewed over a Web-based connection or as part of a Windows application or SharePoint site. For more information, see [Reporting Services (SSRS)](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports?view=sql-server-2014).

-

-SharePoint Health Analyzer, Timer Jobs, Reporting, and PowerShell are built-in features, whereas System Center, System Center Management Pack for SharePoint Server 2016, and SQL Server Reporting Services are independent tools. SharePoint Developer Dashboard and WMI are built-in tools and intended for developers or system administrators. These tools are complementary and apply to different scenarios.

-

-

-|**Tool**|**Optional or built-in**|**Skill level required**|**Pros**|**Cons**|**Resources**|

-|:--|:--|:--|:--|:--|:--|

-|SharePoint Health Analyzer <br/> |Built-in <br/> |Basic <br/> | Gives step-by-step instructions for resolving a problem. <br/> Customizable. You can disable some rules if you don't need them. <br/> | Does not cover all possible problems. <br/> A rule is triggered only after a problem has already happened. <br/> |[Configure SharePoint Health Analyzer rules in SharePoint Server](configure-sharepoint-health-analyzer-rules.md) <br/> [View and resolve SharePoint Health Analyzer alerts in SharePoint Server](/previous-versions/office/sharepoint-server-2010/ee663488(v=office.14)) <br/> [SharePoint Health Analyzer rules reference for SharePoint Server 2016](../technical-reference/sharepoint-health-analyzer-rules-reference.md) <br/> |

-|Timer jobs <br/> |Built-in <br/> |Advanced: You have to consider the implications of enabling or disabling a timer job and changing schedules. <br/> | Wide range of monitoring items. <br/> Easy to reschedule. <br/> Customizable. You can create new timer jobs to meet your specific requirements. <br/> |Can affect system performance and conflict with one another. <br/> |[Configure SharePoint Health Analyzer timer jobs in SharePoint Server 2016](configure-sharepoint-health-analyzer-timer-jobs.md) <br/> [Timer job reference for SharePoint Server](../technical-reference/timer-job-reference-for-sharepoint-server.md) <br/> |

-|Reporting <br/> |Built-in <br/> |Viewing skill level: Basic <br/> |Flexible. Lets you configure the severity of events to log, enable event log flood protection, and configure trace logs. <br/> | Only shows administrative and health statistics, without any suggested solutions. <br/> You have to interpret the logging data. <br/> Can affect performance and disk usage. <br/> |[View reports and logs in SharePoint Server 2016](view-reports-and-logs.md) <br/> |

-|PowerShell <br/> |Built-in <br/> |Advanced: you have to know what to look for, and you have to run PowerShell commands. <br/> |Filters data, displays it in various ways, and outputs data to a grid with which you can filter, sort, group, and export the data to Excel 2016. <br/> |You have to know which PowerShell commands to run. <br/> |[View diagnostic logs in SharePoint Server](view-diagnostic-logs.md) <br/> |

-|System Center with System Center Management Pack for SharePoint Server <br/> |Optional but recommended <br/> |Advanced: you need to know what to look for and how to interpret data. <br/> |The tool can detect, diagnose, and alert you about software and hardware incidents, and refer you to knowledge articles. It helps you to do more monitoring with fewer people by monitoring many key scenarios. <br/> |Requires additional servers to deploy. <br/> |[System Center Management Pack for SharePoint Server 2016](https://www.microsoft.com/download/details.aspx?id=52043) <br/> |

-|Event Viewer <br/> |Built-in <br/> |Basic <br/> |You can view events from multiple event logs, save useful event filters as custom views that can be reused, schedule a task to run in response to an event, and create and manage event subscriptions. <br/> |Does not suggest resolutions. <br/> |[Event Viewer](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766042(v=ws.11)) <br/> |

-|SharePoint Developer Dashboard <br/> |Built-in <br/> |Advanced: you have to know what to look for and how to interpret data. <br/> |Easy to analyze performance of SharePoint pages. <br/> |Limited to monitoring performance of SharePoint pages. <br/> |[SharePoint Developer Dashboard](/previous-versions/office/developer/sharepoint-2010/ff512745(v=office.14)) <br/> |

-|Windows Management Instrumentation (WMI) <br/> |Built-in <br/> |Advanced: you have to know what to look for and how to write WMI scripts for the managed objects. <br/> |Can monitor, track, and control system events that are related to software applications, hardware components, and networks. <br/> | You have to identify which managed objects to monitor. <br/> You have to write WMI scripts. <br/> |[Windows Management Instrumentation (WMI) Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn265977(v=ws.11)) <br/> |

-|SQL Server Reporting Services <br/> |Optional but recommended. <br/> |Advanced: you have to design and manage reports. <br/> |Comprehensive platform to create and manage reports. <br/> |Advanced skills required to create and develop solutions. You have to know PerformancePoint Dashboard Designer and Visual Studio. <br/> |[Reporting Services (SSRS)](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports?view=sql-server-2014) <br/> |

-

-

-

-

-

-

-Identify the scenarios that you want to monitor ΓÇöfor example, health, workflows, search, SQL Server, virtual environments, and performance. The following table shows some key scenarios and the monitoring tools that you can use to monitor those scenarios.

-

-|**Tool\Scenario**|**Health**|**Search**|**Databases**|**Performance**|**Workflows**|**Virtual environments**|**Business Data Connectivity**|**Business Intelligence**|**Access Services**|**Farms**|**Servers**|**Service applications**|**Web applications**|

-|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|

-|SharePoint Health Analyzer <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |X <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |

-|Timer jobs <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |X <br/> |√ <br/> |X <br/> |X <br/> |X <br/> |√ <br/> |√ <br/> |

-|Reporting <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |

-|PowerShell <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |

-|System Center with System Center Management Pack for SharePoint Server <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |

-|Event Viewer <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |

-|SharePoint Developer Dashboard <br/> |X <br/> |X <br/> |X <br/> |√\* <br/> |X <br/> |X <br/> |X <br/> |X <br/> |X <br/> |X <br/> |X <br/> |X <br/> |X <br/> |

-|Windows Management Instrumentation (WMI) <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |√\*\* <br/> |X <br/> |√ <br/> |X <br/> |X <br/> |√ <br/> |X <br/> |X <br/> |

-|SQL Server Reporting Services <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |X <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |√ <br/> |

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-The following table shows approximately how many people of different skill levels are required to monitor the SharePoint environment depending on the number of servers. Note that this table only provides a very rough estimate.

-

-|**Number of servers**|**Personnel required**|**Skill level required**|

-|:--|:--|:--|

-|1~4 <br/> |1 <br/> |Basic <br/> |

-|4~10 <br/> |1~2 <br/> |Advanced <br/> |

-|10~40 <br/> |3~4 <br/> |Basic and Advanced <br/> |

-|40~100 <br/> |5+ <br/> |Basic and Advanced <br/> |

-|100+ <br/> |10+ <br/> |Basic and Advanced <br/> |

-

-

-

-

-|**Item**|**Description**|

-|:--|:--|

-|Alert/Event/Problem <br/> |The verbatim message, the verbatim event, or description of the problem. <br/> |

-|Affected services/applications <br/> |Services or applications that will be affected by the problem. <br/> |

-|Symptom <br/> |Symptom of the problem. <br/> |

-|Severity <br/> |Severity of the problem. Problems with high severity must have high priority. <br/> |

-|Problem must be resolved in (minutes or hours) <br/> |Acceptable lapse time of service. <br/> |

-|Possible causes <br/> |Possible causes of the problem. <br/> |

-|Resolutions <br/> |Resolutions of the problem. <br/> |

-|Contacts <br/> |People who should be contacted when this problem occurs. <br/> |

-|Escalation <br/> |People or teams that should be contacted if the resolutions did not successfully resolve the problem. <br/> |

-|Related resources <br/> |Any resources that may help resolve the problem, such as articles on docs.microsoft.com for SharePoint Server. <br/> |

-|Note <br/> |Any issues that you want to highlight. <br/> |

-

-

-

-

-

-

-> This article only describes how to move content databases. For information about how to move other kinds of databases that are associated with SharePoint Server, see [Move or rename service application databases in SharePoint Server](move-or-rename-service-application-databases.md) and [Move all databases in SharePoint Server](move-all-databases.md).

-

-

-

-

-

-

-

-

- > To move the content database file within the same instance SQL Server we recommend that you use the **FILENAME** clause of the **ALTER DATABASE** statement. For more information, see [Move User Databases](/sql/relational-databases/databases/move-user-databases?viewFallbackFrom=sql-server-2014).

-

- > To move a content database to another instance of SQL Server or to another server, we recommend that you use procedures found in [Database Detach and Attach (SQL Server)](/sql/relational-databases/databases/database-detach-and-attach-sql-server?viewFallbackFrom=sql-server-2014) or [Back Up and Restore of SQL Server Databases](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases?viewFallbackFrom=sql-server-2014).

-

-

-

-

- > Use the identical name when you add the content database or SharePoint Server creates a new content database.

-

-

-Use the following procedure to move the content databases in your SharePoint Server farm by using Central Administration.

-

-

-1. To record which content databases are associated with each web application ΓöÇ PowerShell

-

-4. To detach the content databases from SQL Server ΓöÇ SQL Server tools

-

-5. To move the content databases to a new location ΓöÇ File Explorer or Windows Explorer

-

-6. To attach the content databases to the new instance of SQL Server ΓöÇ SQL Server tools

-

-> [!NOTE]

-> The procedures in this section use Central Administration to move content databases. However, the first procedure, must be performed by using PowerShell.

-

-> If you are moving a content database to a different farm, you must make the server farm account a member of the Administrators group on the database server during the restore process. This enables the account to replicate the security setting for the databases. This access level can be removed after the content database is moved. For more information, see [Account permissions and security settings in SharePoint Server 2016](../install/account-permissions-and-security-settings-in-sharepoint-server-2016.md).

-

-The destination farm must be running the same version or a later version of SharePoint Server than the source farm is running.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- - The **dbcreator** and **securityadmin** fixed server roles on the destination server, in order to attach the database and configure SQL Server logins.

-

- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets.

-

- > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin).

-

-

-

- ```

- Get-SPContentDatabase -WebApplication <http://SiteName>

- ```

- Where: _\<http://SiteName\>_ is the URL of the web application.

-

- > We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

-

-

-

-

-

-

-3. On the **Manage Content Databases** page, click the content database that you want to move.

-

- The **Manage Content Database Settings** page opens.

-

- > If the content database does not appear in the list, it might be associated with another web application. To select another web application, on the **Web Application** menu, click **Change Web Application**.

-

-

- > Removing the content database does not delete the database. It only removes the association of the database with the web application.

-

-

-1. Verify that the user account that is performing this procedure is a member of the **db_owner** fixed database role on the database server where each database is stored.

-

-2. In SQL Server Management Studio, open the source SQL Server instance, and then expand the **Databases** node.

-

-

- > Use this procedure to move only content databases. Do not detach any other kinds of databases.

-

-

-

-

-1. Verify that the user account that is performing this procedure is a member of the **dbcreator** fixed server role on the database server where each database is stored.

-

-

-

-

-

-

-

-

-4. On the **Add Content Database** page, verify that the **Web Application** menu displays the correct web application.

-

-5. In the **Server** box, specify the database server that hosts the database.

-

-6. In the **Database Name** box, type the exact name of the transferred content database.

-

- > Verify that the name is correct. If it is not, a new database will be created.

-

-

-8. Repeat these steps for each database that you are adding. Be sure that you select the correct web application from the **Web Application** menu for each database.

-

-

-

-

-

-

-4. To detach the content databases from SQL Server ΓöÇ SQL Server tools

-

-5. To move the content databases to a new location ΓöÇ File Explorer

-

-6. To attach the content databases to the new instance of SQL Server ΓöÇ SQL Server tools

-

-> If you are moving a content database to a different farm, you must make the server farm account a member of the Administrators group on the database server during the restore process. This enables the account to replicate the security setting for the databases. This access level can be removed after the content database is moved.

-

-The destination farm must be running the same version or a later version of SharePoint Server than the source farm is running.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- - The **dbcreator** and **securityadmin** fixed server roles on the destination server, in order to attach the database and configure SQL Server logins.

-

- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets.

-

- > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin).

-

-

-

- ```

- Get-SPContentDatabase -WebApplication <http://SiteName>

- ```

- Where: _\<http://SiteName\>_ is the URL of the web application.

-

-

-> We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- - The **dbcreator** and **securityadmin** fixed server roles on the destination server, in order to attach the database and configure SQL Server logins.

-

- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets.

-

- > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin).

-

-

-

- ```

- Get-SPTimerJob -webapplication <http://WebApplicationURL> | select name | Out-File <c:\timerjobfile.txt> -Append -Encoding ascii

- ForEach($tmrjob in (Get-Content <c:\timerjobfile.txt>)) { Get-SPTimerJob -Identity $tmrjob | Disable-SPTimerjob }

-

- ```

- Where:

-

- - _\<http://WebApplicationURL\>_ is the Web application associated with the content database that you are moving.

-

- - _\<c:\timerjobfile.txt\>_ is the location of the file that you are creating that lists all timer jobs associated with the Web application.

-

-

-> We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- - The **dbcreator** and **securityadmin** fixed server roles on the destination server, in order to attach the database and configure SQL Server logins.

-

- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets.

-

- > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin).

-

-

-

- ```

- Dismount-SPContentDatabase "<ContentDB>"

- ```

- Where: _\<ContentDB\>_ is the name of the content database.

-

- > [!NOTE]

- > If you have multiple content databases that have the same name, you must use the content database GUID in this command instead of using the content database name. To retrieve the GUID of the content database, run the **Get-SPContentDatabase** cmdlet without arguments.

-

- For more information, see [Dismount-SPContentDatabase](/powershell/module/sharepoint-server/Dismount-SPContentDatabase) and [Get-SPContentDatabase](/powershell/module/sharepoint-server/Get-SPContentDatabase).

-

- > [!NOTE]

- > We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

-

-1. Verify that the user account that is performing this procedure is a member of the **db_owner** fixed database role on the database server where each database is stored.

-

-2. In Management Studio, open the source SQL Server instance, and then expand the **Databases** node.

-

-

-> Use this procedure to move only content databases. Do not detach any other kinds of databases.

-

-

-

-

-1. Verify that the user account that is performing this procedure is a member of the **dbcreator** fixed server role on the database server where each database is stored.

-

-

-

-

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- - The **dbcreator** and **securityadmin** fixed server roles on the destination server, in order to attach the database and configure SQL Server logins.

-

- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets.

-

- > [!NOTE]

- > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin).

-

-

-

- ```

- Mount-SPContentDatabase "<ContentDB>" -DatabaseServer "<DBServer>" -WebApplication <http://SiteName>

- ```

- Where:

-

- - _\<ContentDB\>_ is the name of the content database to be attached.

-

- - _\<DBServer\>_ is the name of the database server.

-

- - _\<http://SiteName\>_ is the URL of the Web application to which the content database is being attached.

-

-

- > We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- - The **dbcreator** and **securityadmin** fixed server roles on the destination server, in order to attach the database and configure SQL Server logins.

-

- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets.

-

- > [!NOTE]

- > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin).

-

-

-

- ```

- ForEach($tmrjob in (Get-Content <c:\timerjobfile.txt>)) {Get-SPTimerJob -Identity $tmrjob | Enable-SPTimerjob}

-

- ```

- Where: _\<c:\timerjobfile.txt\>_ is the location of the file that you created that lists all of the timer jobs associated with the Web application.

-

-

- > We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

-

-[Move all databases in SharePoint Server](move-all-databases.md)

-

-

-Renaming service application databases is often done to remove the GUID from the database name after you've used SharePoint Products Configuration Wizard and SharePoint Server Product Configuration Wizard to create the service application databases in your farm. You might also need to align the database names with your organization's naming standards.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-> Don't attempt to move and rename a database in one procedure. You should either move a database or rename a database, not perform both actions at the same time.

-

-

-

-

-

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- > For additional information about Microsoft PowerShell permissions, see [Permissions](/powershell/module/sharepoint-server/add-spshelladmin?view=sharepoint-ps&preserve-view=true).

-

-

-3. You need to know the service GUID for the next step. Use the **Get-SPServiceInstance** cmdlet to retrieve a list of all services in the farm together with their GUIDs.

-

-

- Where _\<ServiceGUID\>_ is the GUID of the service.

-

-

-

-1. Use an account that has the **db_owner** fixed database role for all of the databases that you're moving.

-

-2. In SQL Server Management Studio, connect to the SQL Server instance that the service application database is attached to, and then expand the **Databases** node.

-

-

-

-

-

-1. Use an account that has the **db_owner** fixed database role for all of the databases that you're moving.

-

-

-

-

-

-

-1. In SQL Server Management Studio, connect to the source SQL Server instance, and then expand the **Databases** node.

-

-

-

-

-

-3. On the Manage Service application page, click the empty area in the row next to the service application name. The ribbon becomes active, click **Properties** and the **Edit Service Application** dialog appears.

-

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- > For additional information about Microsoft PowerShell permissions, see [Permissions](/powershell/module/sharepoint-server/add-spshelladmin?view=sharepoint-ps&preserve-view=true).

-

-

-

-

- - _\<ServiceApplicationName\>_ is the name of the Managed Metadata service application.

-

- - _\<DatabaseName\>_ is the name of the renamed database.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- > For additional information about Microsoft PowerShell permissions, see [Permissions](/powershell/module/sharepoint-server/add-spshelladmin?view=sharepoint-ps&preserve-view=true).

-

-

-

-

- - _\<ServiceApplicationName\>_ is the name of the PerformancePoint service application.

-

- - _\<DatabaseServerName\DatabaseName\>_ is the location of and the name of the renamed or moved database. Do not include the location if you are just renaming the database.

-

-The State Service database stores temporary state information data. You can use PowerShell to point the State Service service application to a moved database by performing one of the following procedures:

-

-

-

-

- - Stopping a service application

-

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

- - Administrators group on the server on which you are running the PowerShell cmdlets.

-

- > For additional information about Microsoft PowerShell permissions, see [Permissions](/powershell/module/sharepoint-server/add-spshelladmin?view=sharepoint-ps&preserve-view=true).

-

-

-

- New-SPStateServiceDatabase -Name "<NewDatabaseName>"

-

-

- - _\<NewDatabaseName\>_ is the name of the new database that you want to create.

-

- - _\<OldDatabaseName\>_ is the name of the old database that you want to disassociate with the State service and detach from SQL Server.

-

-

-

- Where _\<DatabaseID\>_ is the State Service database to remove from the service application. The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a state database, or an instance of a valid **SPStateServiceDatabase** object.

-

-

-

-

-

- - _\<DatabaseName\>_ is the name of the database to associate with the State service.

-

- - _\<ServerName\>_ is the name of the SQL Server that hosts the State service database.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

-

- > For additional information about Microsoft PowerShell permissions, see [Permissions](/powershell/module/sharepoint-server/add-spshelladmin?view=sharepoint-ps&preserve-view=true).

-

-

-

-

-

- - _\<ServiceApplicationName\>_ is the name of the usage and health data collection service application.

-

- - _\<DatabaseName\>_ is the name of the database.

-

- - _\<SQLServerName\>_ is the name of the database server.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

-

- > For additional information about Microsoft PowerShell permissions, see [Permissions](/powershell/module/sharepoint-server/add-spshelladmin?view=sharepoint-ps&preserve-view=true).

-

-

-

-

- - _\<ServiceApplicationName\>_ is the name of the Word Automation service application.

-

- - _\<DatabaseName\>_ is the name of the renamed or moved database.

-

- - _\<DatabaseServer\>_ is the location of the renamed or moved database. Do not include this parameter if you are pointing to a renamed database in the same location.

-

-

- - **securityadmin** fixed server role on the SQL Server instance.

-

- - **db_owner** fixed database role on all databases that are to be updated.

-

-

- > For additional information about Microsoft PowerShell permissions, see [Permissions](/powershell/module/sharepoint-server/add-spshelladmin?view=sharepoint-ps&preserve-view=true).

-

-

-

-

- - _\<ServiceApplicationName\>_ is the name of the Subscription Settings service application.

-

- - _\<DatabaseName\>_ is the name of the renamed database.

-

- - _\<DatabaseServer\>_ is the name of the renamed database.

-

-

-

-

-

-

-When moving or renaming the Business Data Connectivity service application and User Profile service application databases requires extra steps. The extra steps required for both service application databases is that after you move or rename the databases we recommend that you delete the service application and then re-create it.

-

-

-

-

-

-

-

-

- Where _\<ServiceGUID\>_ is the GUID of the service. If you don't know the service GUID, you can retrieve a list of all services in the farm together with their GUIDs by using the **Get-SPServiceInstance** cmdlet.

-

-

-1. Use an account that has the **db_owner** fixed database role for all of the databases that you're moving.

-

-2. In SQL Server Management Studio, connect to the source SQL Server instance, and then expand the **Databases** node.

-

-

-

-

-

-1. Use an account that has the **db_owner** fixed database role for all of the databases that you're moving.

-

-

-

-

-The method for pointing a service application to a moved database that works for most service applications is to delete the service application and then re-create the service application. When you re-create the service application, use the new name or new location.

-

-

-

-

-3. On the **Service Applications** page, place your cursor next to Business Data Connectivity service and then click the empty row.

-

-

-

-5. In the Delete Service Application dialog, select the check box next to **Delete data associated with the Service Applications** if you want to delete the service application database. If you want to retain the database, leave this check box cleared.

-

-6. Click **OK** to delete the service application, or click **Cancel** to stop the operation.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

- Where _\<SearchServiceApplicationName\>_ is the name of the Search service application associated with the database move.

-

-1. Use an account that is a member of the **db_owner** fixed database role for the content database.

-

-

-

-

-

-

-

-

-

-

-

-1. Use an account that is a member of the SQL Server **db_backupoperator** fixed database role on the database server where each database is stored.

-

-

-

-

-5. In the **Back Up Database** dialog, in the **Source** area, select the kind of backup that you want to perform from the **Backup type** list.

-

-

-

-7. Either use the default name or specify a name for the backup set in the **Name** box.

-

-

-

-9. In the **Destination** area, specify where you want to store the backup.

-

-10. Click **OK** to back up the database.

-

-

-

-

-

-

-

-

-

-4. In the **Max Degree of Parallelism** box, select **1** to limit the number of processors to use in parallel plan execution.

-

-

-1. Use an account that is a member of the SQL Server **sysadmin** fixed server role on the database server where each database is stored.

-

-

-

-4. Right-click the database that you want to restore, point to **Tasks**, point to **Restore**, and then click **Database**.

-

-5. In the **Restore Database** dialog, on the **General** page, select the database to restore to from the **To database** list.

-

-6. Select the restore source from the **From database** list.

-

-7. In the **Select the backup sets to restore section** area, select the check box next to the database.

-

-8. On the **Options** tab, select the recovery state from the **Recover state** section.

-

-

-9. Click **OK** to restore the database.

-

-

-

-

-

-

- - _\<NewDbName\>_ is the name of the database.

-

- - _\<NewServerName\>_ is the new database location.

-

- ```powershell

- Add-SPServerScaleOutDatabase -ServiceApplication $ssa -DatabaseServer <OriginalServerName> [-DatabaseName <NewDbName>]

- $temp = Get-SPServerScaleOutDatabase -ServiceApplication $ssa

- Remove-SPServerScaleOutDatabase -Database $temp[0] -ServiceApplication $ssa

- ```

-

- Where:

-

- - _\<OriginalServerName\>_ is the name of the original SQL server.

-

-

- $CrawlDatabase0 = ([array]($ssa | Get-SPEnterpriseSearchCrawlDatabase))[0]

-

- $LinksDatabase0 = ([array]($ssa | Get-SPEnterpriseSearchLinksDatabase))[0]

-

- Where _\<Search Server\>_ is the name of the server that hosts the search components.

-

-

- Where _\<SearchServiceApplicationName\>_ is the name of the Search service application associated with the database move.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

- Where _\<SearchServiceApplicationName\>_ is the name of the Search service application associated with the database move.

-

-1. Use an account that is a member of the **db_owner** fixed database role for the content database.

-

-

-

-

-

-

-

-

-

-

-

-1. Use an account that is a member of the SQL Server **db_backupoperator** fixed database role on the database server where each database is stored.

-

-

-

-

-5. In the **Back Up Database** dialog, in the **Source** area, select the kind of backup that you want to perform from the **Backup type** list.

-

-

-

-7. Either use the default name or specify a name for the backup set in the **Name** box.

-

-

-

-9. In the **Destination** area, specify where you want to store the backup.

-

-10. Click **OK** to back up the database.

-

-

-

-

-

-

-

-

-

-4. In the **Max Degree of Parallelism** box, select **1** to limit the number of processors to use in parallel plan execution.

-

-

-1. Use an account that is a member of the SQL Server **sysadmin** fixed server role on the database server where each database is stored.

-

-

-

-4. Right-click the database that you want to restore, point to **Tasks**, point to **Restore**, and then click **Database**.

-

-5. In the **Restore Database** dialog, on the **General** page, select the database to restore to from the **To database** list.

-

-6. Select the restore source from the **From database** list.

-

-7. In the **Select the backup sets to restore section** area, select the check box next to the database.

-

-8. On the **Options** tab, select the recovery state from the **Recover state** section.

-

-

-9. Click **OK** to restore the database.

-

-

-

-> [!NOTE]

-> These instructions assume you will use the same PowerShell session for all commands.

-

- - _\<SearchServiceApplication\>_ is the name of the Search service application associated with the database.

- - _\<SearchAdministrationServiceDatabase\>_ is the name of the Search service application Administration database.

- - _\<SearchServiceDatabaseServer\>_ is the name of the new databse server hosting the Search service application databases.

- - _\<SearchServiceAnalyticsDatabase\>_ is the name of the Search service application Analytics database.

- - _\<SearchServiceDatabaseServer\>_ is the name of the new databse server hosting the Search service application databases.

- - _\<SearchServiceCrawlDatabase\>_ is the name of the Search service application Crawl database.

- - _\<SearchServiceDatabaseServer\>_ is the name of the new databse server hosting the Search service application databases.

- - _\<OldCrawlStoreDatabase\>_ is the name of the old Search service application Crawl database.

- New-SPEnterpriseSearchLinksDatabase -DatabaseName <SearchServiceLinksDatabase> ΓÇôSearchApplication $ssa -DatabaseServer <SearchServiceDatabaseServer>

- - _\<SearchServiceLinksDatabase\>_ is the name of the Search service application Links database.

- - _\<SearchServiceDatabaseServer\>_ is the name of the new databse server hosting the Search service application databases.

-[Move all databases in SharePoint Server](move-all-databases.md)

-Client certificate authentication over SMTP is an optional, advanced authentication configuration that allows the ΓÇ£clientΓÇ¥ (in this scenario, SharePoint) to authenticate to the SMTP server using an X.509 certificate that the client presents to the server. This authentication is either ΓÇ£instead ofΓÇ¥ or ΓÇ£in addition toΓÇ¥ the username/password credentials. This configuration isnΓÇÖt common, but it can be used in high security environments where standard username/password authentication isnΓÇÖt considered sufficient.

-> You donΓÇÖt have to use client certificate authentication to use TLS connection encryption to the SMTP server.

-1. The SMTP server must be configured to support STARTTLS for TLS connection encryption.

-2. The SMTP server must be configured to either accept or require client certificates when establishing TLS connections using STARTTLS.

-3. SharePoint must be configured to use TLS connection encryption to the SMTP server.

-4. SharePoint must be configured to use a client certificate when connecting to the SMTP server.

-5. SharePoint process accounts that send emails (which may include the SharePoint farm service account and the web application service account) must have permission to read the private key of the X.509 certificate.

-6. The X.509 certificate must meet the following requirements:

- - The X.509 certificate must be in the ΓÇ£End EntityΓÇ¥ certificate store in SharePoint.

-1. Create a dedicated "Custom" receive connector for the SharePoint farm.

-2. Set the receive connector's permission group to "Exchange Servers".

-3. Set the receive connector's authentication type to "externally secured".

-[Overview of Business Connectivity Services in SharePoint Server](business-connectivity-services-overview.md) 

-

-

-

-

-

-You will need to know who has daily administrative responsibility over the external data source. This is the group that you will need to work with to help set up connectivity to the external data. They will be able to tell you how the data is made available for external consumption, how it is secured, and so on. You might need them to create credentials in the external system for you to use. Be prepared to answer their questions on the impact of your Business Connectivity Services solution on their data and their external system.

-

-

-

-

-

-

-

-

-

-

-As part of your requirement gathering, you need to find out from your business stakeholders what they need the solution to do and how they need users to interact with it. They might need the users to interact with the data in SharePoint Server, via external lists, and external web parts and Office apps. Or, they might need the solution to surface data through Office apps and SharePoint applications. For more info about apps for Office and SharePoint, see [(OLD) Overview of apps for SharePoint 2016](./plan-for-apps-for-sharepoint.md). Or, the solution might require some other combination of browser, client, and application access to the external data.

-

-

- **Business Connectivity Services-scoped external content types** are stored centrally in the BDC Metadata Store and a farm administrator manages security on them. You can share these external content types with multiple Business Connectivity Services web applications.

-

- **The apps for Office and SharePoint-scoped external content types** are stored as an XML file in the app for Office and SharePoint application itself. They cannot be used by any other apps for Office and SharePoint applications.

-

- **Connection settings objects** can only be used with OData data sources. They contain connection information, such as a service address for the service that surfaces the external data, the type of authentication to use, the Internet-facing URL, and the names of any required certificates. Connection settings objects are separate objects from an external content type. When a Business Connectivity Services solution needs to connect to an external system, it uses the information in a connection settings object. You would typically choose to define the connection information separately from the external content type when the external content type developer doesn't know, or doesn't have access to, the necessary connection information when the external content type is developed. Both app-scoped external content types and service-scoped external content types can use connection settings objects. Connection settings objects can be used by multiple Business Connectivity Services solutions. Each solution must be granted permissions to use a connection settings object.

-

-

-

-

-

-

-

-

-

- **The BDC Metadata Store** This SQL Server database that stores the model definitions, external content types, and external system definitions.

-

-|**To allow a user or group to…**|**Give them the following permissions…**|**On…**|

-|:--|:--|:--|

-|Set permissions on any object contained in the BDC Metadata Store via propagation <br/> |SetPermissions <br/> |The BDC Metadata Store <br/> |

-

-**The model** A model is a XML file that contains sets of descriptions of one or more external content types, the related external systems, and information that is specific to the environment, such as authentication properties.

-

- **Table: Mapping permissions on the model**

-|**To allow a user or group to…**|**Give them the following permissions…**|**On…**|

-|:--|:--|:--|

-|Create new models <br/> |Edit <br/> |The BDC Metadata Store <br/> |

-|Edit a model <br/> |Edit <br/> |The model <br/> |

-|Set permissions on a model <br/> |SetPermissions <br/> |The model <br/> |

-|Import a model <br/> |Edit <br/> |The BDC Metadata Store <br/> |

-|Export a model <br/> |Edit <br/> |The model and all external systems in the model <br/> |

-

-**The external system in the BDC Metadata Store** An external system is the metadata definition of a supported source of data that can be modeled, such as a database, web service, or .NET connectivity assembly.

-

- **Table: Mapping permissions on the external system in the BDC Metadata Store**

-|**To allow a user or group to…**|**Give them the following permissions…**|**On…**|

-|:--|:--|:--|

-|Create new external systems <br/> |Edit <br/> |The BDC Metadata Store <br/> |

-|Edit an external system <br/> |Edit <br/> |The external system object <br/> |

-|Set permissions on the external system <br/> |SetPermissions <br/> |The external system object <br/> |

-

-**External content type** An external content type is a reusable collection of metadata that defines a set of data from one or more external systems, the operations available on that data, and connectivity information related to that data.

-

- **Table: Mapping permissions on the external content type**

-|**To allow a user or group to …**|**Give them the following permissions …**|**On …**|

-|:--|:--|:--|

-|Create new external content types <br/> |Edit <br/> |The external system <br/> |

-|Execute operations on an external content type <br/> |Execute <br/> |The external content type (method instances of the operation) <br/> |

-|Create lists of the external content type <br/> |Selectable in clients <br/> |The external content type <br/> |

-|Set permissions on the external content type <br/> |SetPermissions <br/> |The external content type <br/> |

-

-**The method** A Business Data Connectivity method is an XML definition of how Business Connectivity Services can interact with an external data source.

-

- **Table: Mapping permissions on the method**

-|**To allow a user or group to …**|**Give them the following permissions …**|**On …**|

-|:--|:--|:--|

-|Edit a method <br/> |Edit <br/> |The method <br/> |

-|Set permissions on a method <br/> |SetPermissions <br/> |The method <br/> |

-

-**The method instance** A method instance describes, for a particular method, how to use a method by using a specific set of default values.

-

- **Table: Mapping permissions on the method instance**

-|**To allow a user or group to…**|**Give them the following permissions…**|**On…**|

-|:--|:--|:--|

-|Edit a method instance <br/> |Edit <br/> |The method instance <br/> |

-|Execute a method instance <br/> |Execute <br/> |The method instance <br/> |

-|Set permissions on a method instance <br/> |SetPermissions <br/> |The method instance <br/> |

-

-

-

-**Advantages**

-**Disadvantages**

-#### Install RBS library to evert SharePoint front end and application server

-#### Enable RBS feature in specific content database

-#### Setting up credentials for Remote Share Provider

-#### Registering BLOB store with Remote Share Provider

-#### Switching and activating BLOB store

-#### Grant permission to web application pool account and SharePoint service application pool account

-#### Resetting IIS

-### Managing and configuring remote share BLOB store

-Get-SPRemoteShareBlobStore ΓÇôRemoteShareBlobStore <SPRemoteShareBlobStorePipeBind>

-3. In the **Apps** section, point to the app that you want to remove, click **…**, and then click **Remove**.

-

-

-

-

-

-

- **Delegation of administration to the **Business Data Connectivity service****

-

-

- **Managing permission on the Metadata Store and its contents**

-

-

-**Figure: Metadata Store permissions**

-

-

-

-

-

-

-

-

- **Recommendations for managing Metadata Store permissions**

-

-1. Pick one account, probably your Business Connectivity Services administrator account, and grant it **Set Permissions** permissions at the Metadata Store level. This will satisfy the requirement that every item has one user or group that has **Set Permissions** permissions with a securely managed administrative account. If you don't explicitly set an account, the farm account is used by default. Do not select the **Propagate permissions to all** option. You don't have to select the **Propagate permissions to all** option because every item will inherit this configuration when it is added to the Metadata Store. This also prevents unnecessary accounts from gaining access to any external systems, BDC models, or external content types that they shouldn't have.

-

-2. Use the direct application method, configure the permissions on the individual items, again not selecting the **Propagate permissions to all** option. This will allow you to maintain unique permissions configuration on each object.

-

-

-4. You should only use the **Propagate all permissions** option when you must completely reset all the permissions on the parent item and all its children. Note that this is a destructive process and all custom permissions on child items are lost. This action can break BCS solutions for users or groups that lose their permissions.

-

- **Mapping accounts and groups in Secure Store Service**

-

-

-

-

-

- **Managing permissions on the Business Data Connectivity Service application**

-

-

-

-#### Concepts

-5. Next to **Excel Services**, click **Authentication Settings…**, and then take one of the following steps:

-5. Next to **Excel Services**, click **Authentication Settings…**, and then take one of the following steps:

-5. Next to **Excel Services**, select **Authentication Settings…**.

-5. In the **Source** section, select **Device**, and then click the ellipsis ( **…**) button.

-

-

-Although tests were not run on SQL Server 2014 (SP1), SQL Server 2016, SQL Server 2017 RTM, or SQL Server 2019 you can use these test results as a guide to help you plan for and configure the storage and SQL Server database tier in SharePoint Server Subscription Edition, 2019, or 2016 environments. For training about how to configure and tune SQL Server 2012, see [SQL Server 2012 for SharePoint Server 2013](#Section8A). The test results are the same as in SharePoint 2013.

-

-

-

-

-

-

-

-

-

-

-

-

-Before you start to plan storage, you should understand the databases that SharePoint Server can use.

-

-

-

-

-

-

-

-

-Some SharePoint Server, SQL Server Database Engine, and SQL Server Reporting Services (SSRS) databases have specific location recommendations or requirements. For information about these database locations, see [Database types and descriptions in SharePoint Server](../technical-reference/database-types-and-descriptions.md). The **Quick reference guide: SharePoint Servers 2016 and 2019 Databases**, is available to download as either a [PDF](https://download.microsoft.com/download/7/9/7/79700E8E-9896-4657-B9E6-4940B295B71A/DBrefguideSPS2019_tabloid.pdf) or [Visio](https://download.microsoft.com/download/7/9/7/79700E8E-9896-4657-B9E6-4940B295B71A/DBrefguideSPS2019_tabloid.vsdx) file.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-Configuration and content storage and IOPS are the base layer that you must plan for in every SharePoint Server deployment.

-

-Storage requirements for the Configuration database and the Central Administration content database are not large. We recommend that you allocate 2 GB for the Configuration database and 1 GB for the Central Administration content database. Over time, the configuration database may grow beyond 1 GB. It does not grow quickly ΓÇö it grows by approximately 40 MB for each 50,000 site collections.

-

-

-

-

-Estimating the storage and IOPS required for content databases is not a precise activity. In testing and explaining the following information, we intend to help you derive estimates to use to determine the initial size of your deployment. However, when your environment is running, we expect that you'll revisit your capacity needs based on the data from your live environment.

-

-

-

-

- Database size = ((D × V) × S) + (10 KB × (L + (V × D)))

-

- > The value, 10 KB, in the formula is a constant that approximately estimates the amount of metadata required by SharePoint Server. If your system requires significant use of metadata, you may want to increase this constant.

-

-2. Calculate the expected number of documents. This value is known as D in the formula.

-

- How you calculate the number of documents will be determined by the features that you are using. For example, for My Sites or collaboration sites, we recommend that you calculate the expected number of documents per user and multiply by the number of users. For records management or content publishing sites, you may calculate the number of documents that are managed and generated by a process.

-

-

-3. Estimate the average size of the documents that you'll be storing. This value is known as S in the formula. It may be worthwhile to estimate averages for different types or groups of sites. The average file size for My Sites, media repositories, and different department portals can vary significantly.

-

-4. Estimate the number of list items in the environment. This value is known as L in the formula.

-

- List items are more difficult to estimate than documents. We generally use an estimate of three times the number of documents (D), but estimation formula this will vary based on how you expect to use your sites.

-

-5. Determine the approximate number of versions. Estimate the average number of versions any document in a library will have. This value will usually be much lower than the maximum allowed number of versions. This value is known as V in the formula.

-

- The value of V must be above zero.

-

-

-|**Input**|**Value**|

-|:--|:--|

-|Number of documents (D) <br/> |200,000 <br/> Calculated by assuming 10,000 users times 20 documents <br/> |

-|Average size of documents (S) <br/> |250 KB <br/> |

-|List items (L) <br/> |600,000 <br/> |

-|Number of non-current versions (V) <br/> |2 <br/> Assuming that the maximum versions allowed is 10 <br/> |

-

-Database size = (((200,000 x 2)) × 250) + ((10 KB × (600,000 + (200,000 x 2))) = 110,000,000 KB or 105 GB

-

-> Efficient File I/O in SharePoint Server is a storage method in which a file is split into pieces that are stored and updated separately. These pieces are streamed together when a user requests the file. This increases the I/O performance but it normally does not increase the file size. However, small files can see a small increase in the disk storage that is required.

-

-

-

-

-

-

-> Office Online Server is the next version of Office Web Apps Server. Using Office Online Server with SharePoint Servers 2016, 2019, Subscription Edition doesn't affect the size of the content database. To deploy Office Online Server in your SharePoint Server 2016 farm, see [Deploy Office Online Server](/officeonlineserver/deploy-office-online-server).

-

-

-

-After you estimate content storage and IOPS needs, you must determine the storage and IOPS required by the service applications that are being used in your environment.

-

-

-|**Database**|**Scaling**|**Disk IOPS**|**Disk size**|**10M items**|**100M items**|

-|:--|:--|:--|:--|:--|:--|

-|Crawl <br/> |One DB per 20M items <br/> SQL IOPS: 10 per a DPS <br/> |Medium/High <br/> |Medium <br/> |15 GB <br/> 2 GB log <br/> |110 GB <br/> 50 GB log <br/> |

-|Link <br/> |One DB per 60M items <br/> SQL IOPS: 10 per 1M items <br/> |Medium <br/> |Medium <br/> |10 GB <br/> 0.1 GB log <br/> |80 GB <br/> 5 GB log <br/> |

-|Analytics Reporting <br/> |Split when reaching 100-300 GB <br/> |Medium <br/> |Medium <br/> |Usage dependent <br/> |Usage dependent <br/> |

-|Search Administration <br/> |One DB <br/> |Low <br/> |Low <br/> |0.4 GB <br/> 1 GB log <br/> |1 GB data <br/> 2 GB log <br/> |

-

-|**Service application**|**Size estimation recommendation**|

-|:--|:--|

-|User Profile <br/> |The User Profile service application is associated with three databases: Profile, Synchronization, and Social Tagging. <br/> **Note**: The testing for the User Profile database storage requirements and IOPS recommendations is not yet complete. Check back for additional information. <br/> For User Profile database information, see [Database types and descriptions in SharePoint Server](../technical-reference/database-types-and-descriptions.md). <br/> |

-|Managed Metadata Service <br/> |The Managed Metadata service application has one database. The size of the database is affected by the number of content types and keywords used in the system. Many environments will include multiple instances of the Managed Metadata service application. <br/> |

-|Secure Store Service <br/> |The size of the Secure Store service application database is determined by the number of credentials in the store and the number of entries in the audit table. We recommend that you allocate 5 MB for every 1,000 credentials for it. It has minimal IOPS. <br/> |

-|State Service <br/> |The State service application has one database. We recommend that you allocate 1 GB for it. It has minimal IOPS. <br/> |

-|Word Automation Services <br/> |The Word Automation service application has one database. We recommend that you allocate 1 GB for it. It has minimal IOPS. <br/> |

-|PerformancePoint Services <br/> |The PerformancePoint service application has one database. We recommend that you allocate 1 GB for it. It has minimal IOPS. <br/> |

-|Business Data Connectivity service <br/> |The Business Data Connectivity service application has one database. This database is small and significant growth is unlikely. It has minimal IOPS. The PerformancePoint Services is not applicable for Subscription Edition. <br/> |

-|App Management <br/> |The App Management service application has one database. This database is small and significant growth is unlikely. It has minimal IOPS. <br/> |

-|Power Pivot <br/> |The Power Pivot Service application has one database. This database is small and has no significant I/O impact. We recommend that you use the same IOPS as the SharePoint content database. Content databases have significantly higher I/O requirements than the Power Pivot service application database. <br/> |

-

-Availability is how much a SharePoint Server environment is perceived by users to be available. An available system is a system that is resilient ΓÇö that is, incidents that affect service occur infrequently, and timely and effective action is taken when they do occur.

-

-

-We recommend that for SharePoint Server Subscription Edition, 2019, or 2016 you consider running your environment on the Enterprise Edition of the following SQL Servers to take advantage of the other performance, availability, security, and management capabilities that these versions provide.

-

-

-

-For more information about the benefits of these versions, see [Features Supported by the Editions of SQL Server 2014](/sql/sql-server/sql-server-2014-release-notes?view=sql-server-2016&preserve-view=true), [Editions and supported features of SQL Server 2016](/sql/sql-server/editions-and-components-of-sql-server-2016), [Editions and supported features of SQL Server 2017](/sql/sql-server/editions-and-components-of-sql-server-2017), and [https://docs.microsoft.com/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15](/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15&preserve-view=true)).

-

-In particular, you should consider your need for the following features:

-

-

- > SQL Server data compression is not supported for SharePoint Server, except for the Search service application databases.

-

-

-

- > If you are using a Remote BLOB storage provider that does not support database snapshots, you can't use snapshots for content deployment or backup.

-

- **SharePoint Server Subscription Edition**

-

- **SharePoint Server 2019**

- - SQL Server 2019

-

- **SharePoint Server 2016**

- - SQL Server 2014 (SP1)

- - SQL Server 2016

-

-

- **SharePoint 2013**

-

-

-

-

-

-

-

-

-

-

-

-

-SharePoint Server supports Direct Attached Storage (DAS), Storage Area Network (SAN), and Network Attached Storage (NAS) storage architectures, although NAS is only supported for use with content databases that are configured to use remote BLOB storage. Your choice depends on factors within your business solution and your existing infrastructure.

-

-

-

-

-SAN is an architecture to attach remote computer storage devices (such as disk arrays and tape libraries) to servers in such a way that the devices appear as locally attached to the operating system (for example, block storage).

-

-In general, we recommend that you choose a SAN when the benefits of shared storage are important to your organization.

-

-

-

-

-

-A NAS unit is a self-contained computer that is connected to a network. Its sole purpose is to supply file-based data storage services to other devices on the network. The operating system and other software on the NAS unit provide the functionality of data storage, file systems, and access to files, and the management of these functionalities (for example, file storage).

-

-> NAS is only supported for use with content databases that are configured to use remote BLOB storage (RBS). Any network storage architecture must respond to a ping within 1 ms and must return the first byte of data within 20 ms. This restriction does not apply to the local SQL Server FILESTREAM provider, because it only stores data locally on the same server.

-

-> Some confusion exists about if you use the Internet Small Computer System Interface (iSCSI) and assume that it is a NAS protocol. If you access this iSCSI storage through the Common Internet File System (CFIS), it is a NAS protocol. This means that you can't use this storage with content databases if they aren't configured to use RBS. If however, you access this iSCSI storage through a locally attached hard disk, it is considered a SAN architecture. This means that you can use it with NAS.

-

-

-

-

-

-

-

-

-

-All RAID types are supported for SharePoint Server. However, we recommend that you use RAID 10 or a vendor-specific RAID solution that has equivalent performance.

-

-

-For more information about provisioning RAID for SQL Server, see [RAID](/previous-versions/sql/sql-server-2008-r2/ms184252(v=sql.105)).

-

-The memory that is required for SharePoint Server is directly related to the size of the content databases that you are hosting on a server that is running SQL Server.

-

-

-|**Combined size of content databases**|**RAM recommended for computer running SQL Server**|

-|:--|:--|

-|Minimum for small production deployments <br/> |8 GB <br/> |

-|Minimum for medium production deployments <br/> |16 GB <br/> |

-|Recommendation for up to 2 terabytes <br/> |32 GB <br/> |

-|Recommendation for the range of 2 terabytes to 5 terabytes <br/> |64 GB <br/> |

-|Recommendation for more than 5 terabytes <br/> |Extra RAM over 64 GB can improve SQL Server caching speed <br/> |

-

-> These values are higher than those recommended as the minimum values for SQL Server because of the distribution of data required for a SharePoint Server environment. For more information about SQL Server system requirements, see [Hardware and Software Requirements for Installing SQL Server 2014](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server) and [Hardware and Software Requirements for Installing SQL Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server) for SQL Servers 2016 and 2017.

-

-

-

-

-

-

-

-

-

-

-

- > If you use iSCSI, make sure each network adapter is dedicated to either network communication or iSCI, not both.

-

-

-

-

-

-

-

-

-

-The following instructions are general guidance for when to deploy an extra server that will run a SQL Server instance:

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-> Although you can use the backup and recovery tools that are built in to SharePoint Server to back up and recover multiple data files, if you overwrite in the same location, the tools can't restore multiple data files to a different location. For this reason, we strongly recommend that when you use multiple data files for a content database, you use SQL Server backup and recovery tools. For more information about how to back up and recover SharePoint Server, see [Plan for backup and recovery in SharePoint Server](backup-and-recovery-planning.md).

-

-

-Plan for database sizing that will improve manageability, performance, and ease of upgrade for your environment.

-

-

-

-

-

-

-

- - If the calculated size of the content database is not expected to reach the recommended maximum size of 200 GB within the next year, set it to the maximum size the database is predicted to reach in a year ΓÇö with 20 percent extra margin for error ΓÇö by using the **ALTER DATABASE MAXSIZE** property. Periodically review this setting to make sure that it is still an appropriate value, depending on past growth rates.

-

-

-

-Test the backup solution that you are using to make sure that it can back up the system within the available maintenance window. If the backup solution can't meet the SLAs your business requires, consider using an incremental backup solution such as Microsoft System Center Data Protection Manager.

-

-It is important to track the following resource components of a server that is running SQL Server: CPU, memory, cache/hit ratio, and I/O subsystem. When one or more of the components seems slow or overburdened, analyze the appropriate strategy based on the current and projected workload. For more information, see [Monitor and Tune for Performance](/sql/relational-databases/performance/monitor-and-tune-for-performance).

-

-

-

-

-

- - **User connections** This counter shows the number of user connections on your computer that is running SQL Server. If you see this number increase by 500 percent from your baseline, you may see a performance reduction.

-

-

- - **Transactions/sec** This counter shows the number of transactions on a given database or on the entire server per second. This number is more for your baseline and to help you troubleshoot issues.

-

-

- - **Average Wait Time (ms)** This counter shows the average amount of wait time for each lock request that resulted in a wait.

-

- - **Lock Wait Time (ms)** This counter shows the wait time for locks in the last second.

-

- - **Lock waits/sec** This counter shows the number of locks per second that couldn't be satisfied immediately and had to wait for resources.

-

- - **Number of deadlocks/sec** This counter shows the number of deadlocks on the computer that is running SQL Server per second. This number should not increase above 0.

-

-

- - **Average Latch Wait Time (ms)** This counter shows the average latch wait time for latch requests that had to wait.

-

- - **Latch Waits/sec** This counter shows the number of latch requests that couldn't be granted immediately.

-

-

- - **SQL Compilations/sec** This counter indicates the number of times the compile code path is entered per second.

-

- - **SQL Re-Compilations/sec** This counter indicates the number statement recompiles per second.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-For more information and memory troubleshooting methods, see [Monitoring Memory Usage](/previous-versions/sql/sql-server-2008-r2/ms176018(v=sql.105)) for SQL Server 2008 R2 with SP1, [Monitoring Memory Usage](/previous-versions/sql/sql-server-2012/ms176018(v=sql.110)) for SQL Server 2012, and [Monitor Memory Usage](/sql/relational-databases/performance-monitor/monitor-memory-usage) for SQL Server 2014.

-

-

-

-

-

-

-

-

-

-

- - **Logical Disk: Avg. Disk sec/Read** This counter shows the average time, in seconds, of a read operation from the disk. On a well-tuned system, ideal values are from 1 through 5 ms for logs (ideally 1 ms on a cached array), and from 4 through 20 ms for data (ideally less than 10 ms). Higher latencies can occur during peak times. However, if high values occur regularly, you should investigate the cause.

-

- - **Logical Disk: Avg. Disk sec/Write** This counter shows the average time, in seconds, of a write operation to the disk. On a well-tuned system, ideal values are from 1 through 5 ms for logs (ideally 1 ms on a cached array), and from 4 through 20 ms for data (ideally less than 10 ms). Higher latencies can occur during peak times. However, if high values occur regularly, you should investigate the cause.

-

- When you are using RAID configurations with the **Logical Disk: Avg. Disk Bytes/Read** or **Logical Disk: Avg. Disk Bytes/Write** counters, use the formulas listed in the following table to determine the rate of input and output on the disk.

-

-|**RAID level**|**Formula**|

-|:--|:--|

-|RAID 0 <br/> |I/Os per disk = (reads + writes) / number of disks <br/> |

-|RAID 1 <br/> |I/Os per disk = [reads + (2 × writes)] / 2 <br/> |

-|RAID 5 <br/> |I/Os per disk = [reads + (4 × writes)] / number of disks <br/> |

-|RAID 10 <br/> |I/Os per disk = [reads + (2 × writes)] / number of disks <br/> |

-

-

-|**Counter**|**Value**|

-|:--|:--|

-|**Avg. Disk sec/Read** <br/> |80 <br/> |

-|**Logical Disk: Avg. Disk sec/Write** <br/> |70 <br/> |

-|**Avg. Disk Queue Length** <br/> |5 <br/> |

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-The following Microsoft PowerShell script shows how to create the User Profile Service application in Partition Mode and add it to a custom Service Proxy group…

-In this scenario, workflows that are created after you connect to the Workflow Manager installation finish successfully. However, workflows that are created before you connect to Workflow Manager donΓÇÖt finish. Instead, they get stuck when they try to finish or they remain in a suspended state. For workflows that remain suspended, you receive an HTTP 500 error. Additionally, the following entry is logged in the ULS log: *Cannot get app principal permission information.*

-2. In the query result, click the value in the SecuritySettings column to open the XML on a separate tab in SQL Server Management Studio.

-In this scenario, workflows that are created after you connect to the Workflow Manager installation finish successfully. However, workflows that are created before you connect to Workflow Manager donΓÇÖt finish. Instead, they get stuck when they try to finish or they remain in a suspended state. For workflows that remain suspended, you receive an HTTP 500 error. Additionally, the following entry is logged in the ULS log: *Cannot get app principal permission information.*

-2. In the query result, click the value in the SecuritySettings column to open the XML on a separate tab in SQL Server Management Studio.

-4. In the result window, right-click, and then click **Select All**. Then right-click and then click **Save Results As…**.

-

-

-

-

-This article discusses the following scenarios:

-

-

-

-

-

-

-

-

-

- Cross-Site Collection Publishing and the Content Search Web Part enable content reuse across site collections in these scenarios. These features and functionality affect how you plan for capacity. For more information, see [Overview of cross-site publishing in SharePoint Server](overview-of-cross-site-publishing.md).

-

-> Cross-Site Collection Publishing is known as cross-site publishing in this article.

-

- Managed navigation in SharePoint Server 2013 provides taxonomy-driven navigation for a publishing site. For more information, see [Overview of managed navigation in SharePoint Server](overview-of-managed-navigation.md).

-

-

-> The scenarios that are addressed in this article can be achieved by both cross-site publishing and author-in-place sites. The cross-site publishing and managed navigation features do not depend on one another and can be used independently.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-This section provides our test data for two areas: cross-site publishing with anonymous users and author-in-place publishing.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-The server topology that we used to test this scenario is in the following diagram:

-

-

-

-

-

-

-> The computers in this test are physical computers that run Windows Server 2008 R2. Refer to the Search capacity planning and [Capacity planning for SharePoint Server 2013](capacity-planning.md) for recommendations about how to use virtual machines and Windows Server 2012.

-

-> The configuration for our test lab topology is optimized for search-driven publishing scenarios. This configuration is different from collaboration types of SharePoint deployments. For example, our configuration uses the front-end web servers as search index servers to get the best performance. > In our test lab topology we learned that the computer that hosts the application server was underutilized. As a result, we put the Distributed Cache Service on this application server instead of on a dedicated server. You may decide to host the Distributed Cache Service on a dedicated server in your environment. For best performance we do not recommend that you host the Distributed Cache Service on a front-end web server that has the search index server role.

-

-

-> We did not use browser caching or dependent requests, such as images or JavaScript files in our VSTS tests. Depending on how you customize your publishing site, the amount of dependent requests that occur can vary considerably. > The pages that we used in our tests made almost 50 page load time 1 (PLT1) request types (empty browser cache) and about 3 requests for PLT2 request types (subsequent requests with results from the browser cache). Usually, SharePoint BLOB Cache serves requests for these items and will not alter our performance numbers significantly.

-

-|**Server Components**|**Servers running SharePoint Server**|

-|:--|:--|

-|**Processors** <br/> |Intel Xeon CPUs @2.27GHz (2 processors, 8 cores total, 16 threads total) <br/> |

-|**RAM** <br/> |24 GB <br/> |

-|**Operating system** <br/> |Windows Server 2008 R2 Enterprise SP1, 64-bit <br/> |

-|**Size of the SharePoint drive** <br/> |200 GB on internal disk <br/> |

-|**Storage used for Search Index** <br/> |78 GB on an external disk array (2 x Dell PERC H700 SCSI) <br/> |

-|**Number of network adapters** <br/> |2 <br/> |

-|**Network adapter speed** <br/> |1 gigabit <br/> |

-|**Authentication** <br/> |None ΓöÇ Anonymous <br/> |

-|**Software version** <br/> |SharePoint Server 2013 <br/> |

-

-|**Server Components**|**Database servers**|

-|:--|:--|

-|**Processors** <br/> |Intel Xeon CPUs L5520 @2.27GHz (2 processors, 8 cores total, 16 threads total <br/> |

-|**RAM** <br/> |24 GB <br/> |

-|**Operating system** <br/> |Windows Server 2008 R2 Enterprise SP1, 64-bit <br/> |

-|**Disk Array** <br/> |2 x Dell H700 SCSI <br/> |

-|**Number of network adapters** <br/> |2 <br/> |

-|**Network adapter speed** <br/> |1 gigabit <br/> |

-|**Authentication** <br/> |NTLM <br/> |

-|**Software version** <br/> |Microsoft SQL Server 2008 R2 SP1 <br/> |

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Number of VSTS users (simulating concurrent users):** <br/> |60 <br/> |100 <br/> |

-|**Server Response Time 50th percentile\*:** <br/> |219 ms. <br/> |302 ms. <br/> |

-|**Server Response Time 95th percentile\*:** <br/> |412 ms. <br/> |635 ms. <br/> |

-|**Page views per second:** <br/> |78 <br/> |98 <br/> |

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Total queries per second:** <br/> |235 <br/> |294 <br/> |

-|**Queries served from Anonymous Results Cache:** <br/> |145 <br/> |182 <br/> |

-|**Queries served from Search:** <br/> |90 <br/> |112 <br/> |

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Average CPU (Search index nodes per front-end web server)** <br/> |59% <br/> |80% <br/> |

-|**Average CPU (application server including Distributed Cache)** <br/> |8% <br/> |9% <br/> |

-|**Average CPU (Search CPC nodes)** <br/> |5% <br/> |5% <br/> |

-|**Average CPU (SQL Server)** <br/> |Not measured <br/> |Not measured <br/> |

-|**Peak Memory usage (Search index nodes per front-end web server)** <br/> |7.5 GB <br/> |7.5 GB <br/> |

-|**Peak memory usage (application server including Distributed Cache)** <br/> |10.1 GB <br/> |10 GB <br/> |

-|**Peak memory usage (Search CPC nodes)** <br/> |6.5 GB <br/> |6.5 GB <br/> |

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-$webapp.Properties["SearchResultsCacheTTL"] = <number of seconds to keep in cache>

-

-

-

-

-

-

-

-

-

-

-

-

-> There is a known issue in SharePoint Server 2013 when pages that have Output Caching enabled also contain Content Search Web Parts. To avoid this issue in your deployment, install [SharePoint Server 2013 update: March 12, 2013](https://go.microsoft.com/fwlink/p/?LinkID=286308).

-

-The following graph shows some results from our test environment where we use Output Caching on the homepage and category pages that receive 60 percent of the site traffic.

-

-

-> Content Search Web Parts have a setting to run in asynchronous mode. Output Caching does not apply to the load from asynchronous Content Search Web Parts.

-

-

-

-

-

-

-

-

-

-

-|**Test Schedule**|**Update Relationship Graph**|**Runtime (hours)**|**Total Peak Disk Usage**|**Usage Analytics Peak Disk Usage**|

-|:--|:--|:--|:--|:--|

-|**Day 1** <br/> |No <br/> |02:35 <br/> ||2.65 GB <br/> |

-|**Day 2** <br/> |No <br/> |02:43 <br/> |||

-|**Day 3** <br/> |No <br/> |03:23 <br/> |||

-|**Day 4** <br/> |No <br/> |04:39 <br/> |||

-|**Day 5** <br/> |No <br/> |06:08 <br/> |||

-|**Day 6** <br/> |No <br/> |07:35 <br/> |||

-|**Day 7** <br/> |Yes <br/> |08:29 <br/> |82.4 GB <br/> |4 GB <br/> |

-

-

-

- SharePoint publishing is used commonly on intranet sites. By using SharePoint Server 2013, these sites can also be powered by cross-site publishing. The following sections show some important distinctions to consider when you plan for a cross-site publishing site that uses authenticated users. Other than the exceptions mentioned in the following sections, the rules that apply to anonymously accessed sites still apply to sites that authenticated users access.

-

-As mentioned in the [Anonymous Search Results Cache](#anon) section earlier, this cache only takes effect for users who are accessing the SharePoint site anonymously. Compared to anonymously accessed sites that use the Anonymous Search Results Cache, the throughput capacity of sites that are accessed by authenticated users will be significantly lower. Typically intranet sites rarely receive loads as high as the ones mentioned in the previous section (up to 100 page views / second). However, this is an important distinction to consider.

-

-

-> Content Search Web Parts have a setting that, if it is enabled, causes them to run in asynchronous mode. The output cache does not apply to the load from asynchronous Content Search Web Parts.

-

-Depending on the size of the enterprise that deploys SharePoint Server 2013, intranet deployments for SharePoint Server 2013 will typically index larger numbers of documents. This means that the required Search topology to index those documents will be different compared to the topology described in the previous section. Refer to [Plan search in SharePoint Server](../search/search-planning.md) to size your SharePoint deployment appropriately.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-|**Server Components**|**SharePoint Servers**|

-|:--|:--|

-|**Processors** <br/> |Intel Xeon CPUs @2.33GHz (2 processors, 8 cores total, 8 threads total) <br/> |

-|**RAM** <br/> |24 GB <br/> |

-|**Operating system** <br/> |Windows Server 2008 R2 Enterprise, 64-bit <br/> |

-|**Number of network adapters** <br/> |2 <br/> |

-|**Network adapter speed** <br/> |1 Gbps <br/> |

-|**Authentication** <br/> |None ΓöÇ Anonymous <br/> |

-|**Load balancer type** <br/> |Windows software load balancer <br/> |

-|**Software version** <br/> |SharePoint Server 2013 <br/> |

-

-|**Server Components**|**Database server**|

-|:--|:--|

-|**Processors** <br/> |Intel Xeon CPUs MP7130M @2.79GHz (2 processors, 8 cores total, 16 threads total <br/> |

-|**RAM** <br/> |16 GB <br/> |

-|**Operating system** <br/> |Windows Server 2008 R2 Enterprise, 64-bit <br/> |

-|**Disk array** <br/> |2 x Dell PERC 5/E <br/> |

-|**Number of network adapters** <br/> |1 <br/> |

-|**Network adapter speed** <br/> |1 gigabit or Gbps <br/> |

-|**Authentication** <br/> |NTLM <br/> |

-|**Software version** <br/> |Microsoft SQL Server 2008 R2 SP1 <br/> |

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Number of VSTS users:** <br/> |5 <br/> |15 <br/> |

-|**Server Response Time 50th percentile:** <br/> |69 ms. <br/> |112 ms. <br/> |

-|**Server Response Time 95th percentile:** <br/> |92 ms. <br/> |221 ms. <br/> |

-|**Page views per second:** <br/> |57 <br/> |93 <br/> |

-|**Average CPU (application server and front-end web server)** <br/> |55 <br/> |97 <br/> |

-|**Average CPU (SQL Server)** <br/> |7 <br/> |9 <br/> |

-|**Peak memory usage (application server and front-end web server)** <br/> |8.9 GB <br/> |8.9 GB <br/> |

-

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Number of VSTS users:** <br/> |5 <br/> |15 <br/> |

-|**Server Response Time 50th percentile:** <br/> |2 ms. <br/> |2 ms. <br/> |

-|**Server Response Time 95th percentile:** <br/> |74 ms. <br/> |88 ms. <br/> |

-|**Page views per second:** <br/> |190 <br/> |418 <br/> |

-|**Average CPU (application server and front-end web server)** <br/> |58 <br/> |85 <br/> |

-|**Average CPU (SQL Server)** <br/> |5 <br/> |7 <br/> |

-|**Peak memory usage (application server and front-end web server)** <br/> |9.2 GB <br/> |9.4 GB <br/> |

-

-

-

-

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Number of VSTS users:** <br/> |5 <br/> |15 <br/> |

-|**Server Response Time 50th percentile:** <br/> |70 ms. <br/> |111 ms. <br/> |

-|**Server Response Time 95th percentile:** <br/> |95 ms. <br/> |215 ms. <br/> |

-|**Page views per second:** <br/> |56 <br/> |94 <br/> |

-|**Average CPU (application server and front-end web server)** <br/> |54 <br/> |97 <br/> |

-|**Average CPU (SQL Server)** <br/> |7 <br/> |9 <br/> |

-|**Peak memory usage (application server and front-end web server)** <br/> |8 GB <br/> |8 GB <br/> |

-

-

-

-

-

-

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Number of VSTS users:** <br/> |5 <br/> |15 <br/> |

-|**Server Response Time 50th percentile:** <br/> |76 ms. <br/> |107 ms. <br/> |

-|**Server Response Time 95th percentile:** <br/> |103 ms. <br/> |194 ms. <br/> |

-|**Page views per second:** <br/> |54 <br/> |100 <br/> |

-|**Average CPU (application server and front-end web server)** <br/> |50 <br/> |97 <br/> |

-|**Average CPU (SQL Server)** <br/> |6 <br/> |9 <br/> |

-|**Peak Memory Usage (application server and front-end web server)** <br/> |9.5 GB <br/> |9.5 GB <br/> |

-

-

-

-

-

-

-|**Test Features**|**Green Zone**|**Red Zone**|

-|:--|:--|:--|

-|**Number of VSTS users:** <br/> |6 <br/> |18 <br/> |

-|**Server Response Time 50th percentile:** <br/> |17 ms. <br/> |29 ms. <br/> |

-|**Server Response Time 95th percentile:** <br/> |87 ms. <br/> |118 ms. <br/> |

-|**Page views per second:** <br/> |114 <br/> |236 <br/> |

-|**Average CPU (application server and front-end web server)** <br/> |50 <br/> |97 <br/> |

-|**Average CPU (SQL Server)** <br/> |7 <br/> |10 <br/> |

-|**Peak Memory Usage (application server and front-end web server)** <br/> |9.9 GB <br/> |10 GB <br/> |

-

-

-

-

-

-

-[Plan for caching and performance in SharePoint Server](caching-and-performance-planning.md)

-1. Assign yourself permissions to the user's OneDrive account. This can be done in the Microsoft 365 admin center as described here.

-3. Run the DeleteODBLists PowerShell script below (or a customized version of the script); for example:

-The script will permanently delete the hidden lists containing these settings.

-

-> Do not run this script on OneDrive accounts for active users that are still in the organization.

- write-host "$($_.Exception.Message)" -foregroundcolor red

-

-$webFeatures = $ctx.Web.Features

- $list = $lists.GetByTitle($listTitle)

-

- #Delete the list

-This is a sample script and can be adapted to meet your organizationΓÇÖs needs. For example, an admin can extract the information for user1@contoso.com by using the following procedure.

-1. Assign yourself admin permissions to the user's OneDrive account. This can be done [in the Microsoft 365 admin center](/office365/admin/add-users/get-access-to-and-back-up-a-former-user-s-data).

-3. Run the ExportODBLists PowerShell script below (or a customize version of the script):

- write-host "$($_.Exception.Message)" -foregroundcolor red

-

- $list = $lists.GetByTitle($listTitle)

- $listItems = $list.GetItems([Microsoft.SharePoint.Client.CamlQuery]::CreateAllItemsQuery())

- $ctx.load($listItems)

- $ctx.executeQuery()

-

- #Array to Hold List Items

- $listItemCollection = @()

- $exportItem = New-Object PSObject

- $fieldValue = $item[$field]

- #Array to Hold List Items

- $listItemCollection = @()

- $exportItem = New-Object PSObject

- $fieldValue = $item[$field.InternalName]

-

-}

-3. Click the three dots **…** to display the **Open Menu**.

-|**To plan …**|**See …**|

-If you plan to configure Cloud hybrid search with HA topologies in SharePoint Server, you can configure it with Hybrid picker. Hybrid picker has automated certain configuration steps needed to connect your on-premises SharePoint Server environment with SharePoint in Microsoft 365 for Cloud hybrid search. [Learn more](./configure-cloud-hybrid-searchroadmap.md).

-***When should I deploy Cloud hybrid search or hybrid federated search?  Are there any recommendations ?***

-Items secured with SAML claims when crawled using Cloud Search Service application will not show up in search results. This does not work as those identities cannot be interpreted during the ACL mapping process in the Cloud search service application. As of today, we do not have a way to map an on-premises SAML identity to a Microsoft 365 user, which is a core requirement for ACL mapping to work. This is by design. For such supportability questions, a request can be submitted at [SharePoint Feedback portal](https://feedbackportal.microsoft.com/feedback/forum/06735c62-321c-ec11-b6e7-0022481f8472) for evaluation.

-Yes, this is expected. Users will see http:// prefix in the search results. As my friend Brian explains it very nicely [here](/archive/blogs/sharepoint_strategery/beware-crawling-the-non-default-zone-for-a-sharepoint-2013-web-application), SharePoint Server URL-related managed properties including Path, ParentURL and SPSiteUrl all store values relative to the URL that was crawled. The crawler simply passes what it can gather to the Search Content Services in the cloud. SharePoint in Microsoft 365 search has no knowledge of the Alternate Access Mappings on your on-premises farm and so is unable to correctly set the mappings you would expect to see. Thus, it's recommended to crawl the Default zone for a SharePoint Server Web Application.

-

-

-> For the most reliable outcome, complete the procedures in the order they are shown in this article.

-

-

-

-**To verify that a web application meets the requirement**

-

-

-

-

-4. In the **Authentication Providers** dialog box, in the **Zone** column, select the zone the search center site is associated with.

-

-5. In the **Edit Authentication** dialog box, verify that Integrated Windows authentication and NTLM are selected as shown in the following picture.

-

-

-By default, OAuth in SharePoint Server requires **HTTPS**. If you configured your primary web application to use **HTTP** instead of SSL, you have to enable OAuth over **HTTP** on every web server in your SharePoint Server farm.

-

-> If you configured your primary web application to use SSL, this step is not required.

-

-

-

-

-

-

-

-When you set up server-to-server authentication for hybrid environments, you create a **trust relationship** between your **on-premises SharePoint farm** and your **SharePoint in Microsoft 365** **tenant**, which uses Azure Active Directory as a trusted token signing service. By adding the required PowerShell modules and snap-ins, this process can occur in a single PowerShell window on an on-premises SharePoint web server.

-

-> You'll want to keep a record of your steps, the PowerShell cmdlets you run, and any errors that you might encounter. You should capture all the contents of the PowerShell buffer when you have finished and before you close the window. This will give you a history of the steps that you took, which will be helpful if you have to troubleshoot or explain the process to others. This can also be useful to refresh your memory if the setup happens in stages.

-

-

-

-

-

-

-

-

-

-

-

-

-

-This is most easily accomplished on a web server in your SharePoint farm because it's easier to load the *Microsoft.SharePoint.PowerShell* snap-in on the web servers than on servers that don't have SharePoint Server installed.

-

-

-> To make it easier to complete the steps in this section, we'll open a PowerShell Command Prompt window on a SharePoint Server web server and add the modules and snap-ins that let you connect to SharePoint Server, SharePoint in Microsoft 365, and Azure Active Directory. (We'll give you detailed steps on how to do this later in this article.) We'll then keep this window open to use for all the remaining PowerShell steps in this article.

-

-

-

-

-

- For additional info, see [Introduction to the SharePoint in Microsoft 365 Management Shell](/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell).

-

-

-

-

-6. In the PowerShell Properties window, select the **Layout** tab.

-

-

-8. This step loads the modules you downloaded so you can use them in your PowerShell session. Copy the following commands into your PowerShell session, and press **Enter**.

-

-

-

-

-

-

-This section describes the variables you will set in the procedure that follows. These variables contain important information used in many of the remaining configuration steps.

-

-| Variable | Comments |

-|$spcn |The root domain name of your public domain. This value should not be in the form of a URL; it should be the **domain name only**, with **no protocol**. <br/> An example is adventureworks.com. |

-|$spsite |The internal URL of your on-premises primary web application, such as **http://sharepoint** or **`https://sharepoint.adventureworks.com`**. This value is a full URL using the proper protocol (either **http:** // or **https://** ). <br/> This is the internal URL of the web application that you are using for hybrid functionality. <br/> An example is http://sharepoint or `https://sharepoint.adventureworks.com`. |

-|$site |The object of your on-premises primary web application. The command that populates this variable gets the object of the site you specified in the **$spsite** variable. <br/> This variable is automatically populated. |

-|$spoappid |The SharePoint in Microsoft 365 application principal ID is always 00000003-0000-0ff1-ce00-000000000000. This generic value identifies SharePoint in Microsoft 365 objects in a Microsoft 365 organization. |

-|$spocontextID |The context ID (ObjectID) of your SharePoint in Microsoft 365 tenant. This value is a unique GUID that identifies your SharePoint in Microsoft 365 tenant. <br/> This value is automatically detected when you run the command to set the variable. |

-|$metadataEndpoint |The URL that is used by your Azure Active Directory proxy to connect to your Azure Active Directory tenancy. <br/> You don't need to input a value for this variable. |

-

-Now that you identified the variables that you need to set, use these instructions to set them. Pre-populating the most commonly used variables should help you do the remaining steps faster. These variables remain populated as long as you don't close the PowerShell session. Be careful to provide accurate information wherever you see angle brackets (< >), and always remove the angle brackets before you run the command. Don't alter the code *outside* of the angle brackets.

-

-> If you have to do any of these configuration steps again later, you should begin by running the following PowerShell commands in this step to repopulate the important variables.

-

-

-After you populate these variables, you can view their values by entering the variable name in the PowerShell window. For example, entering `$metadataEndpoint` returns a value similar to the following:

-

-

-

-

-The commands in this step add the on-premises STS certificate (public key only) to the SharePoint in Microsoft 365 *principal object* of your Microsoft 365 organization.

-

-

-In this step, you add a service principal name (SPN) to your Azure Active Directory tenant. The SharePoint in Microsoft 365 principal object and your company's public DNS namespace form the SPN.

-

-

-

-

-

-

-

-

-

-

-Using a wildcard value lets SharePoint in Microsoft 365 validate connections with *any host* in that domain. This is useful if you ever need to change the host name of the external endpoint (if your topology includes one) or if you want to change your SharePoint Server web application, in the future.

-

-

-$spns.Add("$spoappid/$spcn")

-

-$spns = $msp.ServicePrincipalNames

-

-

-This should be the *only* SPN in the list that includes your public root domain name.

-

-

-

-

-

-

-

-

-

-

-> If you have configured farm setup scripts that specify the farm authentication realm value, you should update the setup scripts with this new value before you run them again. > For more information about the requirements for realm values in farm setup scripts, see [Plan for server-to-server authentication in SharePoint Server](../security-for-sharepoint-server/plan-server-to-server-authentication.md). Because you have now configured this SharePoint farm to participate in the hybrid configuration, the SharePoint farm authentication realm value must always match the tenant context identifier. If you change this value, the farm will no longer participate in hybrid functionality.

-

-In this step, you create an Azure Active Directory proxy service in the SharePoint Server farm. This enables Azure Active Directory as a *trusted token issuer* that SharePoint Server will use to sign and authenticate claims tokens from SharePoint in Microsoft 365.

-

-

-To validate the **New-SPAzureAccessControlServiceApplicationProxy** command:

-

-

-

-

-

- The output that's expected is a description of the farm's trusted token issuer, where the value of the **RegisteredIssuerName** property is the following:

-

-

-

-

-1. Go to <CentralAdminURL>/_layouts/appinv.aspx and Search for **c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1**, where you should find **Greenland Federated Search Bot Skill**.

-

-

-

- ```xml

-<AppPermissionRequests>

-<AppPermissionRequest Scope="http://sharepoint/search" Right="QueryAsUserIgnoreAppPrincipal" />

-</AppPermissionRequests>

- ```

-

-

-

-

-

-ΓÇó Are you staying on Server (on-premises) for the foreseeable future?

-ΓÇó Do you currently have existing pieces of your system in the cloud?

-ΓÇó What customizations or features do you no longer use?

-ΓÇó Are you ready for a modern approach?

- ΓÇó What is working well now, and what isnΓÇÖt?

-As you install a new version of SharePoint Server, take time to evaluate any service applications or features that you currently rely on that are no longer supported or listed as ΓÇ£deprecatedΓÇ¥.

-ΓÇó Workflows, User Alerts, and custom master pages will not transfer to SharePoint. We recommend you use Power Automate for workflows, reconfigure alerts once migrated, and use the out of the box customization for site look and feel changes.

-ΓÇó Custom Search schema will not transfer to SharePoint. When content is migrated to SharePoint, you may want to re-implement any custom Search schema configuration necessary.

-ΓÇó Use SharePoint Add-ins with the Low Trust model. To learn more, see [Creating SharePoint add in that use low trust authorization](/sharepoint/dev/sp-add-ins/creating-sharepoint-add-ins-that-use-low-trust-authorization).

-ΓÇó Use SharePoint Framework solutions for custom business solutions. To get started, see [SharePoint Framework Overview](/sharepoint/dev/spfx/sharepoint-framework-overview).

-ΓÇó Where is your data? Where will it reside?

-If a portion of your sites are already in the cloud, or if you intend on moving online in the future, adopting the modern features now will help ΓÇ£futureproofΓÇ¥ your installation.

-ΓÇó Use Microsoft 365 Groups and Power Automate. Retire the use of email, Site mailboxes, or Mobile Accounts (SMS/Text Messaging)

-ΓÇó Solutions that intercept and/or modify the HTTP pipeline you could use Azure Conditional Access Policies by fronting the farm by using the Azure AD App Proxy. For more information on how to use AD FS, see [Access Control Policies in Windows Server 2016 AD FS](/windows-server/identity/ad-fs/operations/access-control-policies-in-ad-fs).

-ΓÇó Implement only the necessary Web Application Policies, such as self-service site creation, Object Cache, and Search Crawler accounts, but try to avoid further usage of Web Application Policies as they are not available in SharePoint.

-ΓÇó For security purposes, phase out the use of anonymous SharePoint Server sites. Also note that anonymous site access is not available in SharePoint in Microsoft 365.

-

-> If you contact Microsoft Customer Support Services about a production system that does not meet the minimum hardware specifications described in this document, support will be limited until the system is upgraded to the minimum requirements.

-

-

-Some enterprises have datacenters that are in close proximity to one another and connected by high-bandwidth fiber optic links. In this environment, you can configure the two datacenters as a single farm. This distributed farm topology is called a stretched farm. Stretched farms for SharePoint Server 2016 are supported.

-

-

-

-

-

-> [!NOTE]

-

-

-

-

-|**Installation scenario**|**Deployment type and scale**|**RAM**|**Processor**|**Hard disk space**|

-|:--|:--|:--|:--|:--|

-|Single server role that uses SQL Server <br/> |Development or evaluation installation of SharePoint Server 2016 with the minimum recommended services for development environments. Use the Single-Server farm role that will let you choose which service applications to provision. For additional information on Single-Server farm role, see [Overview of MinRole Server Roles in SharePoint Server 2016](overview-of-minrole-server-roles-in-sharepoint-server.md) <br/> |16 GB <br/> |64-bit, 4 cores <br/> |80 GB for system drive <br/> 100 GB for second drive <br/> |

-|Single server role that uses SQL Server <br/> |Pilot or user acceptance test installation of SharePoint Server 2016 running all available services for development environments. <br/> |24 GB <br/> |64-bit, 4 cores <br/> |80 GB for system drive <br/> 100 GB for second drive and additional drives <br/> |

-|SharePoint server in a multiple server farm <br/> |Development or evaluation installation of SharePoint Server 2016 with a minimum number of services. <br/> |12 GB <br/> |64-bit, 4 cores <br/> |80 GB for system drive <br/> 80 GB for second drive <br/> |

-|SharePoint server in a multiple server farm <br/> |Pilot, user acceptance test, or production deployment of SharePoint Server 2016 running all available services. <br/> |16 GB <br/> |64-bit, 4 cores <br/> |80 GB for system drive <br/> 80 GB for second drive and additional drives <br/> |

-

-

-

-

-

-> Before you run the SharePoint prerequisite installer on Windows Server 2012 R2, you need to install [Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014](https://support.microsoft.com/kb/2919355). The SharePoint prerequisite installer does not install this update for you.

-

-

-> SharePoint Server 2016 does not support single label domain names. For more information, see [Information about configuring Windows for domains with single-label DNS names](/troubleshoot/windows-server/identity/deployment-operation-ad-domains).

-

-

-

-

-

-> SQL Server products and all future public updates are supported through the SQL Server product lifecycle.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-|**Environment**|**Optional software**|

-|:--|:--|

-|Single server farm, front-end web servers, and application servers in a farm <br/> | .NET Framework Data Provider for SQL Server (part of Microsoft .NET Framework) <br/> .NET Framework Data Provider for OLE DB (part of Microsoft .NET Framework) <br/> Workflow Manager <br/> You can install Workflow Manager on a dedicated computer. <br/> Microsoft SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint Technologies <br/> This add-in is used by Access Services for SharePoint Server 2016. <br/> Microsoft SQL Server 2012 Data-Tier Application (DAC) Framework 64-bit edition <br/> Microsoft SQL Server 2012 Transact-SQL ScriptDom 64-bit edition <br/> Microsoft System CLR Types for Microsoft SQL Server 2012 64-bit edition <br/> Microsoft SQL Server 2012 with SP1 LocalDB 64-bit edition <br/> Microsoft Data Services for the .NET Framework 4 and Silverlight 4 (formerly ADO.NET Data Services) <br/> Exchange Web Services Managed API, version 1.2 <br/> Microsoft SQL Server 2008 R2 Remote Blob Store which is part of the Microsoft SQL Server 2008 R2 Feature Pack <br/> SQL Server 2008 R2 Analysis Services ADOMD.NET <br/> |

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

- - You have sufficient hard disk space for the base installation.

- - You have sufficient hard disk space for diagnostics such as logging, debugging,

- creating memory dumps, and so on.

- - You have additional free disk space for day-to-day operations.

- - Maintain two times as much as free space as you have RAM

-|**Installation scenario**|**Deployment type and scale**|**Processor**|**RAM**|**Hard disk**|

-|:--|:--|:--|:--|:--|

-|Single server role that uses SQL Server <br/> |Development or evaluation installation with the minimum recommended services for development environments. <br/> |64-bit, 4 cores <br/> |16 GB <br/> |80 GB for system drive <br/> 100 GB for second drive <br/> |

-|Single server role that uses SQL Server <br/> |Pilot or user acceptance test installation running all available services. <br/> |64-bit, 4 cores <br/> |24 GB <br/> |80 GB for system drive <br/> 100 GB for second drive and additional drives <br/> |

-|SharePoint server in a multi-tier farm <br/> |Development or evaluation installation with a minimum number of services. <br/> |64-bit, 4 cores <br/> |12 GB <br/> |80 GB for system drive <br/> 80 GB for second drive <br/> |

-|SharePoint server in a multi-tier farm <br/> |Pilot or user acceptance test installation running all available services. <br/> |64-bit, 4 cores <br/> |16 GB <br/> |80 GB for system drive <br/> 80 GB for second drive and additional drives <br/>

-

-

-

-Word breakers and stemmers enable you to search efficiently and effectively across content on SharePoint sites and site collections in multiple languages without requiring separate installations of SharePoint Server. Word breakers and stemmers are automatically installed on SharePoint servers by Setup.

-

-> If you are uninstalling SharePoint Server, you must uninstall all language packs before you uninstall SharePoint Server.

-

-

-The language that they select has a language identifier (ID). The language ID determines the language that is used to display and interpret text that is on the site or site collection. For example, when a site owner creates a site in French, the site's toolbars, navigation bars, lists, and column headings appear in French. Similarly, if a site owner creates a site in Arabic, the site's toolbars, navigation bars, lists, and column headings appear in Arabic. In addition, the default left-to-right orientation of the site changes to a right-to-left orientation to correctly display Arabic text.

-

-

-

-

-> You cannot change an existing site, site collection, or web page from one language to another by applying different language-specific site templates. After you use a language-specific site template for a site or a site collection, the site or site collection always displays content in the language of the original site template. For example, SharePoint can render the same site in multiple languages based on the preferred language of the userΓÇÖs web browser. But for this to work, the SharePoint language pack that matches the userΓÇÖs preferred language must be installed on each server in the SharePoint farm.

-

-

-Each language pack that you install creates a folder at `%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\Locale_ID` that contains language-specific data. In each locale_ID folder, you must have only one HTML error file that contains the error information that is used when a file cannot be found. Anytime a file cannot be found for any site in that language, this file will be used. You can specify the file to use by setting the **FileNotFoundPage()** for each web application.

-

-

-

-> By default, the Microsoft PowerShell Help files are installed in English (en-us). To view these files in the same language as the operating system, install the language pack for the same language in which the operating system was installed.

-

-

-`_LanguageID_` is the Language ID number for the language that you are installing.

-

-> The language pack is installed in its native language. The procedure that follows is for the English language pack.

-

- ### Install a language pack on Windows Server with Desktop Experience

-

-

-

-

-

-5. Run the SharePoint Products Configuration Wizard by using the default settings.

-

-

-

-

-

-

-3. Click **Yes** in the dialog that alerts you that some services might have to be restarted during configuration.

-

-

-

-

-

-1. Mount the ISO disc image as a drive on your computer by using the [Mount-DiskImage](/powershell/module/storage/mount-diskimage?view=windowsserver2019-ps) cmdlet, or by specifying it as a virtual drive in your virtual machine manager.

-

-

-

-

-8. Run **Install-SPApplicationContent**.

-

-

-

-

-6. After the language pack has been successfully uninstalled, click **Close**.

-

- $env:CommonProgramFiles\Microsoft Shared\SERVER16\Server Setup Controller\setup.exe" /config "$env:CommonProgramFiles\Microsoft Shared\SERVER16\Server Setup Controller\config.xml" /uninstall OSMUI.JA-JP

-Each folder name has a language tag appended to it, in the form ll-cc. That tag identifies the language and culture. For example, U.S. English language folders are identified by the folder name extension en-us.

-|:--|:--|:--|

-|Arabic <br/>|ar-sa <br/> | 1025 <br/>|

-|Azerbaijani <br/> |az-latn-az <br/> |1068 <br/>|

-|Basque <br/> |eu-es <br/> |1069 <br/>|

-|Bosnian (Latin) <br/> |bs-latn-ba <br/> |5146 <br/>|

-|Bulgarian <br/> |bg-bg <br/> |1026 <br/>|

-|Catalan <br/> |ca-es <br/> |1027 <br/>|

-|Chinese (Simplified) <br/> |zh-cn <br/> |2052 <br/>|

-|Chinese (Traditional) <br/> |zh-tw <br/> |1028 <br/>|

-|Croatian <br/> |hr-hr <br/> |1050 <br/>|

-|Czech <br/> |cs-cz <br/> |1029 <br/>|

-|Danish <br/> |da-dk <br/> |1030 <br/>|

-|Dutch <br/> |nl-nl <br/> |1043 <br/>|

-|English <br/> |en-us <br/> |1033 <br/>|

-|Estonian <br/> |et-ee <br/> |1061 <br/>|

-|Finnish <br/> |fi-fi <br/> |1035 <br/>|

-|French <br/> |fr-fr <br/> |1036 <br/>|

-|Galician <br/> |gl-es <br/> |1110 <br/>|

-|German <br/> |de-de <br/> |1031 <br/>|

-|Greek <br/> |el-el <br/> |1032 <br/>|

-|Hebrew <br/> |he-il <br/> |1037 <br/>|

-|Hindi <br/> |hi-in <br/> |1081 <br/>|

-|Hungarian <br/> |hu-hu <br/> |1038<br/>|

-|Indonesian <br/> |id-id <br/> |1057 <br/>|

-|Irish <br/> |ga-ie <br/> |2108 <br/>|

-|Italian <br/> |it-it <br/> |1040 <br/>|

-|Japanese <br/> |ja-jp <br/> |1041 <br/>|

-|Kazakh <br/> |kk-kz <br/> |1087 <br/>|

-|Korean <br/> |ko-kr <br/> |1042 <br/>|

-|Latvian <br/> |lv-lv <br/> |1062 <br/>|

-|Lithuanian <br/> |lt-lt <br/> |1063 <br/>|

-|Macedonian (FYROM) <br/> |mk-mk <br/> |1071 <br/>|

-|Malay (Malaysia) <br/> |ms-my <br/> |1086 <br/>|

-|Norwegian (Bokmål) <br/> |nb-no <br/> |1044 <br/>|

-|Polish <br/> |pl-pl <br/> |1045 <br/>|

-|Portuguese (Brazil) <br/> |pt-br <br/> |1046 <br/>|

-|Portuguese (Portugal) <br/> |pt-pt <br/> |2070<br/>|

-|Romanian <br/> |ro-ro <br/> |1048 <br/>|

-|Russian <br/> |ru-ru <br/> |1049 <br/>|

-|Serbian (Cyrillic) <br/> |sr-cyrl-rs <br/> |10266 <br/>|

-|Serbian (Latin) <br/> |sr-latn-rs <br/> |9242 <br/>|

-|Slovak <br/> |sk-sk <br/> |1051 <br/>|

-|Slovenian <br/> |sl-si <br/> |1060 <br/>|

-|Spanish <br/> |es-es <br/> |3082 <br/>|

-|Swedish <br/> |sv-se <br/> |1053 <br/>|

-|Thai <br/> |th-th <br/> |1054 <br/>|

-|Turkish <br/> |tr-tr <br/> |1055 <br/>|

-|Ukrainian <br/> |uk-ua <br/> |1058<br/>|

-|Vietnamese <br/> |vi-vn <br/> |1066 <br/>|

-|Welsh <br/> |cy-gb <br/> |1106 <br/>|

-

-

-Word breakers and stemmers enable you to search efficiently and effectively across content on SharePoint sites and site collections in multiple languages without requiring separate installations of SharePoint Server. Word breakers and stemmers are automatically installed on SharePoint servers by Setup.

-

-> If you are uninstalling SharePoint Server, you must uninstall all language packs before you uninstall SharePoint Server.

-

-

-The language that they select has a language identifier (ID). The language ID determines the language that is used to display and interpret text that is on the site or site collection. For example, when a site owner creates a site in French, the site's toolbars, navigation bars, lists, and column headings appear in French. Similarly, if a site owner creates a site in Arabic, the site's toolbars, navigation bars, lists, and column headings appear in Arabic. In addition, the default left-to-right orientation of the site changes to a right-to-left orientation to correctly display Arabic text.

-

-

-

-

-> You cannot change an existing site, site collection, or web page from one language to another by applying different language-specific site templates. After you use a language-specific site template for a site or a site collection, the site or site collection always displays content in the language of the original site template. For example, SharePoint can render the same site in multiple languages based on the preferred language of the userΓÇÖs web browser. But for this to work, the SharePoint language pack that matches the userΓÇÖs preferred language must be installed on each server in the SharePoint farm.

-

-

-Each language pack that you install creates a folder at %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\Locale_ID that contains language-specific data. In each locale_ID folder, you must have only one HTML error file that contains the error information that is used when a file cannot be found. Anytime a file cannot be found for any site in that language, this file will be used. You can specify the file to use by setting the **FileNotFoundPage()** for each web application.

-

-

-

-> By default, the Microsoft PowerShell Help files are installed in English (en-us). To view these files in the same language as the operating system, install the language pack for the same language in which the operating system was installed.

-

-

-

-> The language pack is installed in its native language. The procedure that follows is for the English language pack.

-

- **To install a language pack**

-

-

-

-

-

-

-

- **To rerun the SharePoint Products Configuration Wizard**

-

-

-

-

-3. Click **Yes** in the dialog that alerts you that some services might have to be restarted during configuration.

-

-

-

-

-

-

-When you install language packs, the language-specific site templates are installed in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\TEMPLATE\ _LanguageID_ directory, where _LanguageID_ is the Language ID number for the language that you are installing. For example, the United States English language pack installs to the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\TEMPLATE\1033 directory. After you install a language pack, site owners and site collection administrators can create sites and site collections based on the language-specific site templates by specifying a language when they are creating a new SharePoint site or site collection.

-

-

-Each folder name has a language tag appended to it, in the form ll-cc. That tag identifies the language and culture. For example, U.S. English language folders are identified by the folder name extension en-us.

-|:--|:--|:--|

-|Arabic <br/>|ar-sa <br/> | 1025 <br/>|

-|Azerbaijani <br/> |az-latn-az <br/> |1068 <br/>|

-|Basque <br/> |eu-es <br/> |1069 <br/>|

-|Bosnian (Latin) <br/> |bs-latn-ba <br/> |5146 <br/>|

-|Bulgarian <br/> |bg-bg <br/> |1026 <br/>|

-|Catalan <br/> |ca-es <br/> |1027 <br/>|

-|Chinese (Simplified) <br/> |zh-cn <br/> |2052 <br/>|

-|Chinese (Traditional) <br/> |zh-tw <br/> |1028 <br/>|

-|Croatian <br/> |hr-hr <br/> |1050 <br/>|

-|Czech <br/> |cs-cz <br/> |1029 <br/>|

-|Danish <br/> |da-dk <br/> |1030 <br/>|

-|Dari <br/> |prs-af <br/> |1164 <br/>|

-|Dutch <br/> |nl-nl <br/> |1043 <br/>|

-|English <br/> |en-us <br/> |1033 <br/>|

-|Estonian <br/> |et-ee <br/> |1061 <br/>|

-|Finnish <br/> |fi-fi <br/> |1035 <br/>|

-|French <br/> |fr-fr <br/> |1036 <br/>|

-|Galician <br/> |gl-es <br/> |1110 <br/>|

-|German <br/> |de-de <br/> |1031 <br/>|

-|Greek <br/> |el-el <br/> |1032 <br/>|

-|Hebrew <br/> |he-il <br/> |1037 <br/>|

-|Hindi <br/> |hi-in <br/> |1081 <br/>|

-|Hungarian <br/> |hu-hu <br/> |1038<br/>|

-|Indonesian <br/> |id-id <br/> |1057 <br/>|

-|Irish <br/> |ga-ie <br/> |2108 <br/>|

-|Italian <br/> |it-it <br/> |1040 <br/>|

-|Japanese <br/> |ja-jp <br/> |1041 <br/>|

-|Kazakh <br/> |kk-kz <br/> |1087 <br/>|

-|Korean <br/> |ko-kr <br/> |1042 <br/>|

-|Latvian <br/> |lv-lv <br/> |1062 <br/>|

-|Lithuanian <br/> |lt-lt <br/> |1063 <br/>|

-|Macedonian (FYROM) <br/> |mk-mk <br/> |1071 <br/>|

-|Malay (Malaysia) <br/> |ms-my <br/> |1086 <br/>|

-|Norwegian (Bokmål) <br/> |nb-no <br/> |1044 <br/>|

-|Polish <br/> |pl-pl <br/> |1045 <br/>|

-|Portuguese (Brazil) <br/> |pt-br <br/> |1046 <br/>|

-|Portuguese (Portugal) <br/> |pt-pt <br/> |2070<br/>|

-|Romanian <br/> |ro-ro <br/> |1048 <br/>|

-|Russian <br/> |ru-ru <br/> |1049 <br/>|

-|Serbian (Cyrillic) <br/> |sr-cyrl-rs <br/> |10266 <br/>|

-|Serbian (Latin) <br/> |sr-latn-rs <br/> |9242 <br/>|

-|Slovak <br/> |sk-sk <br/> |1051 <br/>|

-|Slovenian <br/> |sl-si <br/> |1060 <br/>|

-|Spanish <br/> |es-es <br/> |3082 <br/>|

-|Swedish <br/> |sv-se <br/> |1053 <br/>|

-|Thai <br/> |th-th <br/> |1054 <br/>|

-|Turkish <br/> |tr-tr <br/> |1055 <br/>|

-|Ukrainian <br/> |uk-ua <br/> |1058<br/>|

-|Vietnamese <br/> |vi-vn <br/> |1066 <br/>|

-|Welsh <br/> |cy-gb <br/> |1106 <br/>|

-

-

-**Dedicated Roles:** Dedicated roles are optimized for performance and scalability and are typically used in large-scale farms. They can also be used in medium scale farms with shared roles.

-

-| Server Role | Description | Notes |

-|:--|:--|:--|

-|Front-end |Service applications, services, and components that serve user requests belong on a Front-end server. These servers are optimized for high performance. |The Application server and the Front-end server roles host a similar set of services. However, each role serves a different purpose. The Front-end role is performance-sensitive and optimized for serving user traffic by running service instances appropriate for user requests on the local server. It's normal for the Front-end server role to run service instances that would have been hosted on the Application server role in previous versions. |

-|Application |Service applications, services, and components that serve back-end requests, such as search crawl requests, belong on an Application server. These servers are optimized for high throughput. |2. From SharePoint 2016, the use of the term "Application server" has a different meaning from the common use of the term in previous versions. In previous versions of SharePoint, the Application server typically hosted service application endpoints that Front-end servers would call while serving user requests. In SharePoint Servers 2016, 2019, and Subscription Edition, the Application server role runs background tasks such as Timer jobs, and can be the target for search crawl requests. |

-|Distributed Cache |Service applications, services, and components that are required for a distributed cache belong on a Distributed Cache server. |Distributed Cache doesn't support High Availability the way that other services do. While you can have multiple Distributed Cache servers in your SharePoint farm to help distribute the load, the data cached on each Distributed Cache server is not replicated to the other Distributed Cache servers. If a Distributed Cache server unexpectedly goes down, the data cached in that server will be lost. |

-|Search |Service applications, services, and components that are required for search belong on a Search server. |Once a server is assigned to the Search role, it must then be configured in Search topology management. For more information about Search topology, see [Manage the search topology in SharePoint Server](../search/manage-the-search-topology.md). |

-

-**Shared Roles:** Shared roles are optimized for fewer servers in a farm by combining dedicated roles together. They can also be used in medium scale farms with dedicated roles. Shared roles may require higher available system resources because they are running more services.

-

-| Server Role | Description | Notes |

-|:--|:--|:--|

-|Front end with Distributed Cache |Shared role that combines the Front-end and Distributed Cache roles on the same server. Make sure the server meets the system requirements for hosting a shared server role. |This shared role was introduced in the November Public Update for SharePoint Server 2016 (Feature Pack 1). |

-|Application with Search |Shared role that combines the Application and Search roles on the same server. Make sure the server meets the system requirements for hosting a shared server role. |This shared role was introduced in November Public Update for SharePoint Server 2016 (Feature Pack 1). |

-

-**Special Roles:** For special case scenarios, testing, development, and services that are not integrated with MinRole.

-

-| Server Role | Description | Notes |

-|:--|:--|:--|

-|Single-Server Farm |Service applications, services, and components required for a single-server farm belong on a server running the Single-Server Farm role. Use this role for development, testing, and limited production tasks. |The Single-Server Farm role replaces the Standalone Install mode available in previous SharePoint Server releases. Unlike Standalone Install, the SharePoint admin must separately install and prepare Microsoft SQL Server. The SharePoint admin must also configure the SharePoint farm services and web applications, either manually or by running the Farm Configuration Wizard. A SharePoint farm with the Single-Server Farm role cannot have more than one SharePoint server in the farm. |

-|Custom |Service applications, services, and components that you want to manage, instead of using MinRole to manage them, belong on a Custom server. |This server role is typically used to run services that do not integrate with MinRole. The farm administrator has full control over which service instances can run on servers assigned to the Custom server role. MinRole will not attempt to manage servers assigned to this role. |

-

-

-

-

-

-

-Each type of SharePoint farm requires different MinRole server roles to function properly. Refer to the table below for the list of server roles required for each type of farm.

-

-| Server Role | Required for Content Farm? | Required for Services Farm? | Required for Search Farm? |

-|:--|:--|:--|:--|

-|Front-end |Yes |No |No |

-|Application |Yes |Yes |No |

-|Distributed Cache |Yes |Yes |No |

-|Search |Yes, if hosting Search |Yes, if hosting Search |Yes |

-

-> SQL Server can be running on the same server or a different server as SharePoint, but for better performance we recommend running SQL Server on a separate server.

-

-| Content Farm Topology | Total Servers in Farm | Description |

-|:--|:--|:--|

-|Single-Server Farm |1 | One server with all roles: <br/> Evaluation, development, testing. <br/> Very light and simple production workloads. |

-|Small Non-High Availability MinRole farm |2 | Two servers with two shared roles: <br/> One Front end with Distributed Cache server <br/> One Application with Search server |

-|Small High Availability (HA) MinRole farm |4 | Four servers with two shared roles: <br/> Two Front-ends with Distributed Cache servers <br/> Two Application with Search servers |

-|Medium Non-High Availability MinRole farm |4 | Four servers with four dedicated roles: <br/> One Front-end server <br/> One Distributed Cache server <br/> One Application server <br/> One Search server |

-|Medium High Availability (HA) MinRole farm (Search optimized) |6 | Six servers with both dedicated and shared roles: <br/> Two Front-ends with Distributed Cache servers <br/> Two Application servers <br/> Two Search servers |

-|Medium High Availability (HA) MinRole farm (user optimized) |6 | Six servers with both dedicated and shared roles: <br/> Two Front-end servers <br/> Two Distributed Cache servers <br/> Two Application with Search servers |

-|Large High Availability (HA) MinRole farm |8 | Eight servers with four dedicated roles: <br/> Two Front-end servers <br/> Two Distributed Cache servers <br/> Two Application servers <br/> Two Search servers |

-

-

-

-

-The MinRole feature introduces two new command-line parameters for PSConfig.exe and PowerShell. The **LocalServerRole** parameter specifies the role of the local server when you create a new farm or join a server to an existing farm. The **LocalServerRole** parameter accepts the following values:

-

-

-

-

-

-

-

-

-

-The **ServerRoleOptional** parameter configures the farm not to require a server role to be specified when creating a farm or adding a server to a farm. It can be used when you create a new server farm. If no server role is specified, the server defaults to the Custom role.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-> This guidance does not apply to farms that use the Custom server role.

-

-

-

-

-If you have existing deployment scripts that you do not want to modify to support MinRole, you can specify the **ServerRoleOptional** parameter when you create a new SharePoint farm by using the PSConfig.exe command-line tool or PowerShell. This parameter configures the farm to not require a server role to be specified. If no server role is specified, the server defaults to the Custom role.

-

-## See also

-

-

-description: "This article explains the updated product servicing policy of SharePoint Server."

-

-

-

-

-|**SharePoint Server 2019**|**Support End Date**|

-|:--|:--|

-|RTM (16.0.10337.12109) - October 2019 Public Update <br/> |10/31/2020 <br/> |

-|November 2019 Public Update - October 2020 Public Update <br/> |10/31/2021 <br/> |

-|November 2020 Public Update - October 2021 Public Update <br/> |10/31/2022 <br/> |

-|November 2021 Public Update - October 2022 Public Update <br/> |10/31/2023 <br/> |

-|November 2022 Public Update - October 2023 Public Update <br/> |10/31/2024 <br/> |

-|November 2023 Public Update - all future Public Updates <br/> |07/14/2026 <br/> |

-

- ***Question:** Why is Microsoft doing this?

-

- **Answer:** Previously, servicing for SharePoint was tied to specific types of releases - the initial RTM release and service packs. However, Microsoft has no plans to release new service packs for SharePoint and will instead only update SharePoint by way of monthly Public Updates. This new servicing policy ensures that customers are running a build that contains fixes for the most common issues that customers have been reporting to us, even if there are no additional service packs released.

-

- **Question:** Will Microsoft release service packs for SharePoint Server 2019?

-

- **Answer:** No, Microsoft has no plans to release service packs for SharePoint Server 2019. Functionality, performance, and stability improvements for SharePoint Server 2019 will be delivered by way of our monthly Public Updates.

-

- **Question:** Where can I find the Public Updates for SharePoint Server 2019?

-

- **Answer:** The current list of Public Updates for SharePoint Server 2019 can be found in our [SharePoint Updates](/officeupdates/sharepoint-updates) article.

-

- **Question:** Do the monthly Public Updates contain all of the fixes included in the previous Public Updates?

-

- **Answer:** Yes, the monthly Public Updates are cumulative. Each Public Update contains all of the fixes provided in the previous Public Updates.

-

- **Question:** Do I need to install an earlier Public Update before I can install the latest Public Update?

-

- **Answer:** No, you don't need to install an earlier Public Update before you install the latest Public Update. You can install any Public Update directly on an RTM installation, or on top of any previous Public Update.

-

- **Question:** Should I install the monthly Public Updates for SharePoint Server 2019 immediately or should I install them only if they contain a fix for a specific issue I'm having?

-

- **Answer:** Microsoft recommends that all customers install Public Updates for SharePoint Server 2019 as soon as they become available. Microsoft performs rigorous validation of each Public Update, both internally and with a select set of partners and customers before it is released to ensure it has the highest quality.

-**Answer:** As previously announced in KB article [4086137](https://support.microsoft.com/help/4086137/office-2019-on-premises-release-details-february-1-2018), the Microsoft Office 2019 family of products will provide 5 years of mainstream support, followed by 2 years of extended support. This will allow Microsoft to better support our customers as we rapidly innovate these products and cloud services. SharePoint Server 2016 was released later than the other products in the Microsoft Office 2016 family and therefore has a later extended support end date. To ensure that SharePoint Server 2019 doesn't end support earlier than previous versions of SharePoint Server, SharePoint Server 2019 will align its extended support end date with the SharePoint Server 2016 extended support end date.

-description: "This article explains the updated product servicing policy of SharePoint Server."

-

-

-

-

-|**SharePoint Server 2016**|**Support End Date**|

-|:--|:--|

-|RTM (16.0.4351.1000) - April 2017 Public Update <br/> |4/30/2018 <br/> |

-|May 2017 Public Update - April 2018 Public Update <br/> |4/30/2019 <br/> |

-|May 2018 Public Update - April 2019 Public Update <br/> |4/30/2020 <br/> |

-|May 2019 Public Update - April 2020 Public Update <br/> |4/30/2021 <br/> |

-|May 2020 Public Update - April 2021 Public Update <br/> |4/30/2022 <br/> |

-|May 2021 Public Update - all future Public Updates <br/> |7/14/2026 <br/> |

-

- **Question:** Why is Microsoft doing this?

-

- **Answer:** Previously, servicing for SharePoint was tied to specific types of releases - the initial RTM release and service packs. However, Microsoft has no plans to release new service packs for SharePoint and will instead only update SharePoint by way of monthly Public Updates. This new servicing policy ensures that customers are running a build that contains fixes for the most common issues that customers have been reporting to us, even if there are no additional service packs released.

-

- **Question:** Will Microsoft release service packs for SharePoint Server 2016?

-

- **Answer:** No, Microsoft has no plans to release service packs for SharePoint Server 2016. Functionality, performance, and stability improvements for SharePoint Server 2016 will be delivered by way of our monthly Public Updates.

-

- **Question:** Where can I find the Public Updates for SharePoint Server 2016?

-

- **Answer:** The current list of Public Updates for SharePoint Server 2016 can be found in our [SharePoint Updates](/officeupdates/sharepoint-updates) article.

-

- **Question:** Do the monthly Public Updates contain all of the fixes included in the previous Public Updates?

-

- **Answer:** Yes, the monthly Public Updates are cumulative. Each Public Update contains all of the fixes provided in the previous Public Updates.

-

- **Question:** Do I need to install an earlier Public Update before I can install the latest Public Update?

-

- **Answer:** No, you don't need to install an earlier Public Update before you install the latest Public Update. You can install any Public Update directly on an RTM installation.

-

- **Question:** Should I install the monthly Public Updates for SharePoint Server 2016 immediately or should I install them only if they contain a fix for a specific issue I'm having?

-

- **Answer:** Microsoft recommends that all customers install Public Updates for SharePoint Server 2016 as soon as they become available. Microsoft performs rigorous validation of each Public Update, both internally and with a select set of partners and customers before it is released to ensure it has the highest quality.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-The following steps provide a high-level overview of the tasks that are involved to install and configure the Indexing Connector for Documentum for use with SharePoint Server.

-

-

-

-

-

-

- - [Edit the machine.config file](configure-and-use-the-documentum-connector.md#DCTM_machineconfig) to set the Documentum bindings.

-

-1. [Install the Indexing Connector for Documentum](configure-and-use-the-documentum-connector.md#DCTM_Deployconn) on each SharePoint server in the farm that hosts a crawl component.

-

-2. [Register the Indexing Connector for Documentum to the Search service application](configure-and-use-the-documentum-connector.md#DCTM_Registerconn) by using Microsoft PowerShell.

-

-[Configure the Indexing Connector for Documentum](configure-and-use-the-documentum-connector.md#DCTM_ConfigureConn) on each SharePoint server in the farm that hosts a crawl component by using the Indexing Connector for Documentum PowerShell cmdlet. Choose one of the following configurations:

-

-| **Configuration** | **ACL Translation** | **Description** | **See this section** |

-| :-- | : | :- | : |

-| Support crawling EMC Documentum Trusted Content Services (TCS) content or regular Documentum content with automatic user mapping. | Claims | You enable automatic user mapping by configuring a separate Security Trimmer Sync Service and pre- and post-trimmers. | [Configure the Indexing Connector for Documentum to support TCS and automatic user mapping](configure-and-use-the-documentum-connector.md#DCTM_Configure_TCS) |

-| Support crawling Documentum content and use a manually created user mapping table. | UserMappingTable | You manually create a user mapping table in SQL Server to specify how the Documentum users are mapped to Active Directory Domain Services (AD DS) or Active Directory service users. You configure the connector by specifying in which database you have created the user mapping table by using Microsoft PowerShell. | [Configure the Indexing Connector for Documentum using a user mapping table](configure-and-use-the-documentum-connector.md) |

-| Support crawling Documentum content when Documentum and Windows user accounts are the same. | SameAccountName | The Indexing Connector for Documentum assumes that Documentum and SharePoint users share the same account, such as a shared account in Active Directory. Once an account is found that is not valid, the Indexing Connector for Documentum discards the account permission. | [Using the SPEnterpriseSearchDCTMConnectorConfig cmdlet](configure-and-use-the-documentum-connector.md) |

-| Support crawling Documentum content without security trimming the search results. | NoSecurity | All users will be able to see all Documentum search results. This can be useful if you have a public Documentum repository that everyone can access, for example. | [Using the SPEnterpriseSearchDCTMConnectorConfig cmdlet](configure-and-use-the-documentum-connector.md) |

-

-

-

-3. Perform a full crawl.

-

-

-1. Locate the following DFS Productivity Layer .NET assemblies and verify that the version number is **6.7.2000.36** for all files. When extracted to the default path, these files are located in the `%local%\emc-dfs-sdk-6.7\emc-dfs-sdk-6.7\lib\dotnet` directory.

-

- > You can drag and drop the four DLLs into the global assembly cache ( `%windir%\assembly`) to deploy them, but you might have to turn off User Account Control to do this.

-

-

-The WCF settings that you are about to set in [Edit the machine.config file](configure-and-use-the-documentum-connector.md#DCTM_machineconfig) allow a maximum of 30 megabytes (MB) per Documentum content object (the document file plus its metadata) transferred. The administrator can increase *maxReceivedMessageSize* in *DfsDefaultService* binding for larger content.

-

-

-

-2. Copy the following XML snippet to the **\<configuration\>** element:

-

- ```

-

-

-

-

-

- ```

- Where:

-

- - _\<name of your Search service application\>_ is the name of the Search service application that you are registering the connector to.

-

- - _\<%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\15\CONFIG\SearchConnectors\Documentum\MODEL.xml\>_ is the path of the Indexing Connector for Documentum model file. The default location is given in this example.

-

-You configure the connector settings with the Indexing Connector for Documentum PowerShell cmdlet ( `Set-SPEnterpriseSearchDCTMConnectorConfig`). The settings are stored in `%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\15\CONFIG\SearchConnectors\Documentum\DCTMConfig.xml` and must be the same on each SharePoint Server 2016 server that hosts a crawl component.

-

-Which PowerShell cmdlet parameters you use and which additional configuration steps you must perform depends on configuration mode you choose.

-

-

-The Security Trimmer Sync Service maps Documentum users to AD users by looking at the Documentum fields **user_os_domain**, **user_login_name**, **user_source** and **user_ldap_dn**. If the **user_ldap_dn** field is populated, the Security Trimmer Sync Service will try to extract a domain from the first DC value. For example, if the **user_ldap_dn** field is populated with " **CN=User Name, OU=Unit,DC=Domain,DC=Department,DC=Company** ", the Security Trimmer Sync Service will extract the domain from **DC=Domain** and will ignore **DC=Department,DC=Company**.

-

-

-

- ```

-

-

-

- - _\<MyWebTopServer:PortOfMyWebTopServer\>_ is the name and the port number of the DFS Web Top Server you are using.

-

- - _\<MyRepository n\>_ is the name of Documentum repository that you want to crawl.

-

- - _\<DFSWebServices n\>:\<30000\>_ is the name and the port number of the Documentum Web Services server that hosts the Documentum repository that you want to crawl.

-

-

- **IMPORTANT:** Do not use the Services on Server page on the SharePoint Central Administration website to restart this service. Doing so resets the search index, which requires you to do a full crawl of all content to rebuild the index.

-

- - Verify that the user account that is performing this procedure is an administrator for the server that hosts the crawl component.

-

- - Open a Command Prompt window.

-

- - To stop the OSearch15 service, type this command: **net stop osearch15**

-

- - To start the OSearch15 service, type this command: **net start osearch15**

-

-

-

- - In the **Emc.Documentum** section, in the **ModuleInfo** element, do the following:

-

- - In the **host** attribute, type the host name of the Documentum server.

-

- - In the **port** attribute, type the port number of the Documentum server.

-

- - In the **Data Source: Documentum Settings** section, in the **Repositories** element, do the following:

-

- - In the **repository id** attribute, type the Documentum repository ID.

-

- - In the **name** attribute, type the name of the Documentum repository.

-

- - In the **login** attribute, type the Documentum login name. Use the same login name as the Documentum content access account. This should be a user who has elevated user permissions on the Documentum Content Server.

-

- - In the **dfs** attribute, type the location of the Documentum Foundation Services (DFS) by providing the URI for the DFS.

-

- - (Optional) If your Documentum connection requires SSL/HTTPS, you have to change the security mode.

-

- - In the **Data Source: Documentum Settings** section, subsection **Documentum**, in the **basicHttpBinding** element, set the security mode attribute from _None_ to _Transport_ for the following bindings:

-

- - **DfsAgentService**

-

- - **DfsContextRegistryService**

-

- - **DfsDefaultService**

-

- - In the **Data Source: Documentum Settings** section, subsection **Documentum**, in the **netNamedPipeBinding** element, set the security mode attribute from _None_ to _Transport_ for the following bindings:

-

- - **localNamedPipeBinding**

-

-3. Save and close the file.

-

-

- - Locate the following DFS Productivity Layer .NET assemblies and verify that the version number is **6.7.2000.36** for all files. When extracted to the default path, these files are located in the `%local%\emc-dfs-sdk-6.7\emc-dfs-sdk-6.7\lib\dotnet` directory.

-

-

- - Emc.Documentum.FS.DataModel.Shared.dll

-

-

-

- - On the server that hosts the Security Trimming Sync Service, log on with an account that is a member of the Administrators group on that server and deploy the DFS Productivity Layer .NET assemblies to the global assembly cache `%windir%\assembly`.

-

- > You can drag and drop the four DLLs into the global assembly cache ( `%windir%\assembly`) to deploy them, but you might have to turn off User Account Control to do this.

-

-5. Configure authentication for the Security Trimming Sync Service and install the service.

-

-

- - Open a Command Prompt window on each server that hosts a query processing component.

-

-

- When prompted, enter the password for the account that you provided in the **login** attribute. Use the same login name as the Documentum content access account. The password will now automatically be encrypted and added to the Security Trimming Sync Service config file.

-

- - Install the Security Trimming Sync Service. Type the following command: **Microsoft.Office.Server.Search.Connector.Documentum.TrimmerSync.exe -i**

-

-6. Start the Security Trimming Sync Service.

-

-

- - Expand the **Configuration** menu and click **Services**.

-

-

- - Right-click the **SharePoint Documentum Security Sync** service and then click **Start**.

-

- - Verify that the **Status** column changes to **Started**.

-

-7. Verify that the service is running and that the security sync is completed.

-

- - Run the command **Microsoft.Office.Server.Search.Connector.Documentum.TrimmerSync.exe -d** to write the Security Trimming Sync Service memory to a text file.

-

- - Verify that the Security Trimming Sync Service connects to the Documentum server. Read the file DCTMSecuritySync.log that is located in the directory `<Microsoft Office Server path>\15.0\Data\Office Server\Applications\Search\Nodes`

-

-

-Before you can add the pre- and post- security trimmers, you must add one simple crawl rule for Documentum. Later, you can further specify or expand the crawl rules.

-

-1. Verify that the user account that is performing this procedure is an administrator for the Search service application.

-

-

-

-4. On the Search Administration page, in the **Crawling** section, click **Crawl Rules**.

-

-

-

- - In **Path** box, type **dctm://\***.

-

-

-

- - Make sure that the **Do not allow Basic Authentication** check box is cleared.

-

-7. Click **OK** to add the crawl rule.

-

-

-

- ```

-

-

- - _\<name of your Search service application\>_ is the name of the Search service application.

-

-3. Restart the SharePoint Search Host Controller.

-

- - Open a Command Prompt window.

-

-

-

-

-

-

-

-First, create a user mapping table in SQL Server 2008 or a later version. The user mapping table must have the following format:

-

-| **Column name** | **SQL datatype** | **Description** |

-| :-- | :- | :-- |

-| DCTMCredentialDomain | nvarchar(255) NOT NULL | Domain name of a Documentum account. Populate this column when the account comes from the local computer or an LDAP system. The *User Source* property of the Documentum account should equal *None* or *LDAP* . Otherwise, leave the column empty. |

-| DCTMCredentialRepository | nvarchar (32) NOT NULL | Repository name of a Documentum account. Populate this column when the account comes from a Documentum repository. |

-| DCTMCredentialLoginName | nvarchar (80) NOT NULL | Login name of the Documentum account. |

-| NTCredential | nvarchar (255) NOT NULL | Windows domain user account that searches Documentum contents in SharePoint Server 2016. |

-

-

-```

-DCTMCredentialDomain nvarchar (255) NOT NULL ,

-DCTMCredentialRepository nvarchar (32) NOT NULL ,

-DCTMCredentialLoginName nvarchar (80) NOT NULL ,

-NTCredential nvarchar (255) NOT NULL ,

-CONSTRAINT PK_CredentialMapping PRIMARY KEY CLUSTERED

-)

-

-

-

-

-| &nbsp; | &nbsp; |

-| :-- | : |

-| DCTMCredentialDomain | '' |

-| DCTMCredentialRepository | Finance |

-| DCTMCredentialLogonName | dpark |

-| NTCredential | Contoso\dpark |

-

-> If any cells have no value assigned, they cannot be **null** or empty. You must assign the following empty string value: `''`. > For each Documentum group there must be a Windows NT group in the user mapping table and they must both contain the same user information.

-

-

-

-

- ```

-

-

-

- - _\<MyWebTopServer:PortOfMyWebTopServer\>_ is the name and the port number of the DFS Web Top Server you are using.

-

- - _\<YourDatabaseServerName\>_ is the name of the database server on which you created the user mapping table.

-

- - _\<YourDatabaseInstanceName\>_ is the name of the database instance of the database server on which you created the user mapping table.

-

- - _\<YourMappingDatabaseName\>_ is the name of the database in which you created the user mapping table.

-

- - _\<YourMappingTableName\>_ is the name of the user mapping table that you created.

-

- - _\<MyRepository n\>_ is the name of Documentum repository that you want to crawl.

-

- - _\<DFSWebServices n\>:\<30000\>_ is the name and port number of the Documentum Web Services server that hosts the Documentum repository that you want to crawl.

-

-

- > Do not use the Services on Server page on the SharePoint Central Administration website to restart this service. Doing so resets the search index, which requires you to do a full crawl of all content to rebuild the index.

-

- - Verify that the user account that is performing this procedure is an administrator for the server that hosts the crawl component.

-

-

-

-

-

-You must create a crawled properties category that will contain the Documentum crawled properties. To do so, you use the [New-SPEnterpriseSearchMetadataCategory](/powershell/module/sharepoint-server/New-SPEnterpriseSearchMetadataCategory?view=sharepoint-ps&preserve-view=true) cmdlet and specify the predefined value 34972762-7E3F-4f4f-AE5C-5ABBA92EC530 for the cmdlet's PropSet parameter. Use the following PowerShell code to create the crawled properties category in this way.

-

-```

-

-1. Verify that the user account that is performing this procedure is an administrator for the Search service application.

-

-

-

-4. On the Search Administration page, in the **Crawling** section, click **Crawl Rules**.

-

-

-

-

-

- - In the **Specify Authentication** section, select **Specify a different content access account**, and then type the Documentum content access account and password in the boxes. See _Determine which Documentum content access account to use_ earlier in this article.

-

- - Make sure that the **Do not allow Basic Authentication** check box is cleared.

-

-7. Click **OK** to add the crawl rule.

-

- > You can create multiple crawl rules for Documentum to include or exclude Documentum content.

- >

- > You can use different crawl rules to specify different content access accounts for different Documentum content. For example, you have two repositories and two content access accounts for each repository. The Documentum content access account specified in a crawl rule will only be applied to Documentum content covered by the path in that crawl rule. If you use the Security Trimming Sync Service, you must set up this service for each Documentum server.

-

-You create a content source for Documentum content to specify which Documentum content repositories you want to crawl.

-

-

-

-3. Click the Search service application in which you want to create a content source.

-

-

-

-

- 1. In the **Name** box, type the name for the new content source.

-

-

- 1. In the **Type of Repository** section, select **SharePoint Indexing Connector for Documentum**. Use the name that you specified when you registered the Indexing Connector for Documentum with the Search service application.

-

-

- 1. In the **Crawl Schedules** section, select schedules from the **Full Crawl** and **Incremental Crawl** drop-down lists, or create schedules for each kind of crawl.

-

- 1. In the **Content Source Priority** section, assign a priority level to the content source according to your business requirements.

-

-

-

-The Documentum content source is configured and the system can crawl Documentum content repositories that are specified in the content source.

-

-

-

-| **Type of Documentum object** | **Syntax for the path or the start address** |

-| :- | :- |

-| Repository | dctm://\<clientapphostname\>/\<repository name\> |

-| Cabinet | dctm://\<clientapphostname\>/\<repository name\>/\<cabinet name\> |

-| Folder | dctm://\<clientapphostname\>/\<repository name\>/\<cabinet name\>/\<folder name\> |

-| Document | dctm://\<clientapphostname\>/\<repository name\>/\<cabinet name\>/\<folder name\>/…/\<folder name\>?DocSysID=\<r_object_id\> (where r_object_id is the object ID of that document) |

-

- *\<clientapphostname\>* is the host name of your Documentum client application such as Webtop or DA. The *\<clientapphostname\>* configured here must be the same as the one that is used in the content source. *\<repository name\>* , *\<cabinet name\>* , and *\<folder name\>* are case-sensitive.

-

-

-

-

-The Set-SPEnterpriseSearchDCTMConnectorConfig cmdlet accepts three parameter sets. You use the *Shared* parameter set to change the configuration settings that affect all the Documentum repositories that you crawl. You use the *Repository* parameter set to change the configuration settings that affect only a specific repository. You use the *Remove* parameter set to remove a specific repository from the connector configuration.

-

-

-| **Action** | **Mandatory parameters** | **Optional parameters** |

-| :- | :- | :- |

-| Configure shared repository settings | Shared | DFSURL, UserMappingTableSQLServer, UserMappingTableSQLInstance, UserMappingTableDBName, UserMappingTableName, ACLTranslation, UnmappedAccount, DisplayURLPatternForDocument, DisplayURLPatternForContainer. |

-| Configure settings for a specific repository | Repository, RepositoryName | DFSWebServiceURL, IndexAllVersions, ACLTranslation, UnmappedAccount, DisplayURLPatternForDocument, DisplayURLPatternForContainer. |

-| Remove a repository from configuration | Remove, RepositoryName | |

-

-3. In the Search Results Web Part, click the **Search Results Web Part Menu** arrow, click **Export…**, and then save the Web Part to your computer.

-

-

-> You can only deploy one thesaurus per SharePoint Server farm.

-

-

-To define the entries in your thesaurus, you enter terms and their corresponding synonyms in a comma separated (.csv) file. Optionally, you can also specify in which language the query should be written for a synonym to apply.

-

-If you want to define more than one synonym for one key, you have to create multiple entries in the thesaurus. Also, if you want the synonym to work both ways, for example, if you want the term "IE" to also return search results for "Internet Explorer" and you want the term "Internet Explorer" to also return results for "IE", you have to create two thesaurus entries.

-

-To create your thesaurus terms, you can use alphabetical Unicode characters such as a, ø, ü, or é. Your terms can also include underscores (_), hyphens (-), and straight apostrophes ('). Your terms can't include non-alphabetical Unicode characters, such as hashtag (#), slash (/), backslash (\\), period (.), or question mark (?). You also can't use abbreviations that include non-alphabetical Unicode characters, such as E.K.G or d\r.

-

-

- **To create a thesaurus**

-

-1. Create a .csv file with the columns **Key**, **Synonym** and **Language**. Make sure you use a comma as the column separator. If the file contains non-ASCII characters such as diacritics, you must encode it in UTF-8. Save the file to a location that is accessible from the server from which you will run the Microsoft PowerShell cmdlet to deploy the thesaurus.

-

- - In the **Key** column, enter the term (single or multiple words) that you want to trigger a synonym for when the term occurs in a query. Make sure there are no leading or trailing spaces around the terms.

-

- - In the **Synonym** column, enter the synonym (single or multiple words) that you want to add to the query if the term specified in the **Key** column occurs in a query. Synonyms consisting of multiple words will be added as phrases to the query.

-

- - In the optional **Language** column, enter the abbreviation for the language for which the synonym should apply. See the table in [Linguistic search features in SharePoint Server](../technical-reference/linguistic-search-features.md) for an overview of available languages and their code. If you leave this column empty, the query is expanded with the synonym regardless of the query language. Make sure there are no leading or trailing spaces around the language codes.

-

-

-You create and maintain the thesaurus file in a file external to SharePoint Server before you import it into SharePoint Server to make the synonyms available to the search system. You can't export a thesaurus from SharePoint Server. If you want to make changes to your synonyms, you have to update the thesaurus file and then redeploy it.

-

-> When you redeploy a thesaurus file, the existing thesaurus will be overwritten with the information from the updated thesaurus file.

-

- **To import a thesaurus file**

-

-

-

-

- ```

- $searchApp = Get-SPEnterpriseSearchServiceApplication

-

-

- - _\<Path\>_ specifies the full UNC path of the .csv file (the thesaurus) to be imported.

-

-This series will show how to change the way search results are displayed from this…

- Notice that 52 results were returned. (I will tell you why this is kind of cool in the next section…).

-

-

-

-A *content source* is a definition of a group of crawl settings such as which hosts to crawl, the type of content that will be crawled (such as SharePoint content or file shares), a crawl schedule, and how deep to crawl.

-

-When you create a Search service application, the service application automatically provides the pre-configured content source **Local SharePoint sites**. You can use this content source to specify how to crawl all SharePoint content in web applications that are associated with the Search service application.

-

-

-

-

-

-

-

-

-

-| **Use this kind of content source** | **For this content** |

-| :- | : |

-| SharePoint sites | SharePoint sites from the same farm or different SharePoint Server farms. <br/><br/> SharePoint sites from the same farm or different SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013, SharePoint Server 2010, SharePoint Foundation 2010, or Microsoft Search Server 2010 farms. <br/> <br/>SharePoint sites from the same farm or different Office SharePoint Server 2007, Windows SharePoint Services 3.0, or Search Server 2008 farms. |

-| Web sites | Other web content in your organization that is not located in SharePoint sites. <br/><br/> Content on web sites on the Internet. |

-| File shares | Content on file shares in your organization. <br/> <br/>**Security note:** When the Search service crawls a file share, if the permissions on a file on the share are different from the permissions on folders that contain the file, then the permissions on the file take precedence and are used for security trimming of search results. Therefore, to ensure that only appropriate items appear in search results, make sure that the permissions for files on file shares are appropriate. For cases in which file permissions are not appropriate, you can delete particular items from the search index or from search results. For more information, see [Delete items from the search index or from search results in SharePoint Server](delete-items-from-the-search-index-or-from-search-results.md). |

-| Exchange public folders | Exchange 2007 and Exchange Server 2010 public folders. |

-| Lotus Notes | E-mail messages stored in Lotus Notes databases. <br/> <br/>**Note:** Unlike all other kinds of content sources, the Lotus Notes content source option does not appear in the user interface until you have installed and configured the appropriate prerequisite software. For more information, see [Configure and use the Lotus Notes connector for SharePoint Server](configure-and-use-the-lotus-notes-connector.md) (also applies to SharePoint Server). |

-| Documentum | Content from the EMC Documentum system. <br/> <br/>**Note:** You can't crawl EMC Documentum content before you have installed and configured the appropriate prerequisite software and the Microsoft SharePoint Indexing Connector for Documentum. For more information, see [Configure and use the Documentum connector in SharePoint Server](configure-and-use-the-documentum-connector.md) (also applies to SharePoint Server). |

-| Line-of-business data | Business data that is stored in line-of-business applications. |

-| Custom repository | Content sources that can only be crawled after a custom connector is installed and registered. |

-

-Business data content sources require that the applications hosting the data are specified in an Application Model in a Business Data Connectivity service application. You can create one content source to crawl all applications that are registered in the Business Data Connectivity service, or you can create separate content sources to crawl individual applications. For more information, see [Search connector framework in SharePoint 2013](/sharepoint/dev/general-development/search-connector-framework-in-sharepoint) (This MSDN article also applies to SharePoint Server).

-

-Often, the people who plan for integration of business data into site collections are not the same people involved in the overall content planning process. Therefore, include business application administrators in content planning teams so that they can advise you how to integrate the business application data into content and effectively present it in the site collections.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-| **For this kind of content source** | **If this pertains** | **Use this crawl setting option** |

-| :- | :- | : |

-| SharePoint sites | You want to include the content that is on the site itself and you do not want to include the content that is on subsites, or you want to crawl the content that is on subsites on a different schedule. | Crawl only the SharePoint site of each start address. |

-| SharePoint sites | You want to include the content on the site itself. <br/> <br/> -or- <br/> <br/> You want to crawl all content under the start address on the same schedule. | Crawl everything under the host name of each start address. |

-| Web sites | Content available on linked sites is unlikely to be relevant. | Crawl only within the server of each start address. |

-| Web sites | Relevant content is located on only the first page. | Crawl only the first page of each start address. |

-| Web sites | You want to limit how deep to crawl the links on the start addresses. | Custom ΓÇö Specify the number of pages deep and number of server hops to crawl. <br/> <br/> **Note:** For a highly connected site, we recommend that you start with a small number, because specifying more than three pages deep or more than three server hops can crawl the entire Internet. |

-| File shares <br/> Exchange public folders | Content available in the subfolders is unlikely to be relevant. | Crawl only the folder of each start address. |

-| File shares<br/> Exchange public folders | Content in the subfolders is likely to be relevant. | Crawl the folder and subfolders of each start address. |

-| Business data | All applications that are registered in the Business Data Catalog metadata store contain relevant content. | Crawl the whole Business Data Catalog metadata store. |

-| Business data | Not all applications that are registered in the BDC metadata store contain relevant content. <br/> <br/> -or- <br/> <br/> You want to crawl some applications on a different schedule. | Crawl selected applications. |

-

-The crawler uses connectors (known as "protocol handlers" in earlier versions of SharePoint Server) to acquire and index content. For the most commonly-used protocols, SharePoint Server provides and automatically uses the appropriate connectors. To crawl content that requires a connector that is not provided by default, you must first install a third-party connector or build a custom connector. For a list of connectors that are installed by default, see [Default connectors in SharePoint Server](../technical-reference/default-connectors.md) (also applies to SharePoint Server).

-

-

-

-

-

-

-

-

-

-

-Because crawling content consumes resources and bandwidth, it is better to include a smaller amount of content that you know is relevant than a larger amount of content that might be irrelevant. After the initial deployment, you can review the query and crawl logs and adjust content sources and crawl rules to be more relevant and include more content.

-

-

-We recommend that the account that you specify as the default content access account has access to most of your crawled content. Only use other content access accounts when security considerations require separate content access accounts.

-

-

-> Ensure that the domain account that is used for the default content access account or any other content access account is not the same domain account that is used by an application pool associated with any Web application that you crawl. Doing so can cause unpublished content in SharePoint sites and minor versions of files (that is, history) in SharePoint sites to be crawled and indexed.

-

-

-If you are using claims-based authentication, make sure that Windows authentication is enabled on any Web applications to be crawled.

-

-

-You can map crawled properties to managed properties and configure property settings by editing the search schema. The content processing component reads the search schema and uses it to carry out the mapping. Only managed properties are included in the search index. Managed properties can be used to create refiners, for example. For more information, see [Overview of the search schema in SharePoint Server](search-schema-overview.md).

-

-

-

-

-

-

-> You can extend the initial collection of file formats that SharePoint Server can parse by adding third-party filter-based format handlers, known as iFilters. A third party iFilter can override a built-in format handler.

-

-When you plan to include content in the search index from content repositories that have file types that are **not** on the Manage File Types page, review the following:

-

-

-

-

-

-

-You can configure the search system to look for "entities" in unstructured content, such as in the body text or the title of a document. These entities can be words or phrases, such as product names. To specify which entities to look for, you can create and deploy your own dictionaries.

-

-The extracted entities are stored in the search index as separate managed properties, which are automatically configured to be searchable, queryable, retrievable, sortable and refinable. You can use those properties in search refiners, for example, to help users filter their search results.

-

-

-

-****

-| **Custom entity extractor / dictionary** | **Description** |

-| : | :-- |

-| Word Extraction | Case-insensitive, maximum 5 dictionaries. For example, the entry "anchor" would match "anchor" and "Anchor", but not "anchorage". |

-| Word Part Extraction | Case-insensitive, maximum 5 dictionaries. For example, the entry "anchor" would match "anchor", "Anchor" and within "anchorage". |

-| Word Exact Extraction | Case-sensitive, maximum 1 dictionary. For example, the entry "anchor" would match "anchor", but not "Anchor" or "Anchorage". |

-| Word Part Exact Extraction | Case-sensitive, maximum 1 dictionary. For example, the entry "anchor" would match "anchor" and within "anchorage", but not "Anchor". |

-

-

-

-

-

-

-

-

-

-To use federation in SharePoint Server, you select one of the following protocols in the **Protocol** section on the Add/Edit Result Source page:

-

-| **You select this protocol** | **To get federated search results from this kind of provider** |

-| : | :-- |

-| **Remote SharePoint** | The index of a search service in another SharePoint Server farm |

-| **OpenSearch 1.0/1.1** | An external search engine or feed that uses the OpenSearch protocol, such as Bing |

-| **Exchange** | Exchange Server 2013 |

-

-> On the Add/Edit Result Source page, when you select one of the protocols shown in the preceding table, you must also fill in other related fields on the page to fully specify the result source.

-

-

-

-

-

-

-[Search connector framework in SharePoint 2013](/sharepoint/dev/general-development/search-connector-framework-in-sharepoint)

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-| **Volume of content (SharePoint 2016)** | **Sample search architecture** | **Volume of content (SharePoint 2013)** |

-| :-- | :-- | :-- |

-| 0-20 million items | Small search farm | 0-10 million items |

-| 0-80 million items | Medium search farm | 0-40 million items |

-| 0-200 million items | Large search farm | 0-100 million items |

-| 0-500 million items | Extra large search farm | Not supported |

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-Add storage for the SQL log space for each database server. If you don't set the database server to back up the databases often, the SQL log space uses lots of storage. For more information about how to plan SQL databases, see [Storage and SQL Server capacity planning and configuration (SharePoint Server)](../administration/storage-and-sql-server-capacity-planning-and-configuration.md) .

-

-

-

-| **Server** | **On host** | **Storage** | **RAM** | **Processor¹** | **Network bandwidth** |

-| :-- | :- | :- | : | : | :-- |

-| Application server that has query processing and index components. | A, B | 500 GB^2,3 | 32 GB^2,3 | 1.8 GHz 8x CPU cores^2,3 | 1 Gbps |

-| Application server that has crawl, search administration, analytics and content processing components. | A, B | 200 GB | 8 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-| Database server that has all search databases. | C, D | 100 GB | 16 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-

-

-²With SharePoint Server 2013 the minimum amount of resources needed are 500 GB storage, 16 GB RAM, and four CPU cores.

-

-³With SharePoint Server 2016 you can also use 250 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.

-

-

-| **Server** | **On host** | **Storage** | **RAM** | **Processor¹** | **Network bandwidth** |

-| :- | :- | :- | : | : | :-- |

-| Application server that has query processing and index components. | A, B, C, D | 500 GB^2,3 | 32 GB^2,3 | 1.8 GHz 8x CPU cores^2,3 | 1 Gbps |

-| Application server that has an index component. | A, B, C, D | 500 GB^2,3 | 32 GB^2,3 | 1.8 GHz 8x CPU cores^2,3 | 1 Gbps |

-| Application server that has analytics and content processing components. | E, F | 300 GB | 8 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-| Application server that has crawl, search administration, and content processing components. | E, F | 100 GB | 8 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-| Database server that has all search databases. | G, H | 400 GB | 16 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-

-

-²With SharePoint Server 2013 the minimum amount of resources needed are 500 GB storage, 16 GB RAM, and four CPU cores.

-

-³With SharePoint Server 2016 you can also use 250 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.

-

-

-| **Server** | **On host** | **Storage** | **RAM** | **Processor¹** | **Network bandwidth** |

-| : | : | :-- | :- | :- | :-- |

-| Application server that has query processing and index components. | A, B, C, D, E, G, H | 500 GB^{2, 3} | 32 GB^{2, 3} | 1.8 GHz 8x CPU cores^{2, 3} | 1 Gbps |

-| Application server that has an index component. | A, B, C, D, E, F, G, H, I, J | 500 GB^{2, 3} | 32 GB^{2, 3} | 1.8 GHz 8x CPU cores^{2, 3} | 1 Gbps |

-| Application servers that have analytics and content processing components | K, L, M, N | 300 GB | 8 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-| Application servers that have crawl and search administration components | K, L | 100 GB | 8 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-| Database server that have search databases | O, P, Q, R | 500 GB | 16 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-

-

-²With SharePoint Server 2013 the minimum amount of resources needed are 500 GB storage, 16 GB RAM, and four CPU cores.

-

-³With SharePoint Server 2016 you can also use 250 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.

-

-

-| **Server** | **On host** | **Storage** | **RAM** | **Processor¹** | **Network bandwidth** |

-| :- | :- | :- | : | : | :-- |

-| Application server that has index components. | A-X | 500 GB | 32 GB | 1.8 GHz 8x CPU cores | 1 Gbps |

-| Application server that has query processing and index components. | Y, Z | 500 GB | 32 GB | 1.8 GHz 8x CPU cores | 1 Gbps |

-| Application servers that have crawl, search administration, or content processing components | AA-AF | 100 GB | 8 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-| Application servers that have analytics processing components | AG, AH | 800 GB | 8 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-| Database servers that have search databases | AI-AL | 500 GB | 16 GB | 1.8 GHz 4x CPU cores | 1 Gbps |

-

-

-

-

-

-

- > You can set a custom location for search component data when you install SharePoint Server on a host. Any search component on the host that needs to store data, stores it in this location. To change this location later, you have to reinstall SharePoint Server on that host.

-

-

-

-| **Component name** | **Component details** | **IOPS requirements** | **Use of separate storage volume/partition** |

-| : | :-- | : | :- |

-| Index component | Uses storage when merging the index and when handling and responding to queries. | 300 IOPS for 64 KB random reads. <br/> 100 IOPS for 256 KB random writes. <br/> 200 MB/s for sequential reads. <br/> 200 MB/s for sequential writes. | Yes |

-| Analytics component | Analyzes data locally, in bulk processing. | No | Yes |

-| Crawl component | Stores downloaded content locally, before it sends it to a content processing component. Storage is limited by network bandwidth. | No | Yes |

-

-| **Database name** | **IOPS requirements** | **Typical load on I/O subsystem.** |

-| :-- | :-- | :-- |

-| Crawl database | Medium to high IOPS | 10 IOPS per 1 document per second (DPS) crawl rate. |

-| Link database | Medium IOPS | 10 IOPS per 1 million items in the search index. |

-| Search administration database | Low IOPS | Not applicable. |

-| Analytics reporting database | Medium IOPS | Not applicable. |

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-| **Test number** | **Scope** | **Command** |

-| :-- | : | :- |

-| 1 | 64 KB read [IOPS] | `diskspd -t4 -b64K -o25 -r -d300 testfile` |

-| 2 | 256 KB write [IOPS] | `diskspd -t4 -b256K -o25 -r -w100 -d300 testfile` |

-| 3 | 100 MB read [MB/s] | `diskspd -t1 -o1 -b100M -r -d300 testfile` |

-| 4 | 100 MB write [MB/s] | `diskspd -t1 -o1 -b100M -r -w100 -d300 testfile` |

-

-

-

-

-| &nbsp; | &nbsp; | &nbsp; | &nbsp; | &nbsp; | &nbsp; |

-| : | :-- | :-- | :-- | :-- | : |

-| Disk layout | Test 1 | Test 2 | Test 3 | Test 4 | |

-| Recommended minimum IOPS during ordinary operations | 300 | 100 | 200 | 200 | |

-| 4x 1 TB 7200 RPM NLSAS in RAID5 on Dell H710 RAID controller (64kB stripe size, 64kB block size) | 1181 | 206 | 284 | 296 | |

-| 8x 1TB 7200 RPM NLSAS in RAID5 on Dell H710 RAID controller (64kB stripe size, 64kB block size) | 2082 | 337 | 610 | 645 | |

-| 16x 1TB 7200 RPM NLSAS in RAID5 on Dell H710 RAID controller (64kB stripe size, 64kB block size) | 3763 | 595 | 1173 | 1181 | |

-| 16x 1TB 7200 RPM NLSAS in RAID50 (2x8) on Dell H710 RAID controller (64kB stripe size, 64kB block size) | 3613 | 545 | 1139 | 1164 | |

-| 16x 1TB 7200 RPM NLSAS in RAID10 on Dell H710 RAID controller (256kB stripe size, 64kB block size) | 4030 | 1146 | 970 | 775 | |

-| 4x SmartStorage Optimus 800GB SSDs in RAID5 on Dell H710 RAID controller (64kB stripe size, 64kB block size) | 32385 | 3781 | 1714 | 1319 | |

-| 4x SmartStorage Optimus 800GB SSDs in RAID0 on Dell H710 RAID controller (256kB stripe size, 64kB block size) | 31747 | 7149 | 1643 | 1798 | ||

-

-

-

-

-

-

-

-

-

-

-

-

-

-It's a good idea to measure search performance first with a synthetic load, and then with a small set of live users, and live content. When you use live users and live content, you can observe how the search architecture is performing. If your content increases faster than you intended, it might be worth considering using the next size search architecture. Or, if your users are more active than anticipated, then we suggest that you increase the amount of storage space of the analytics database.

-

-

-

-This article describes how content is collected in and retrieved from the search index by using the search schema. The search schema contains crawled properties, crawled property categories, the crawled to managed property mapping and the managed property settings. Managed property settings define what you can search for and how, for example if you can refine or query on a property.

-

-

-

-Each item that has been crawled and passed on to the content processing component has crawled properties associated with it. Examples of properties are **Author**, **Title**, and **Creation Date**. Any new crawled properties will be discovered automatically.

-

-Crawled properties are grouped into categories that are based on the IFilter or protocol handler of the item. Example categories are **Office** (crawled properties from Word documents, Excel worksheets, and so on), **Business Data** (crawled properties from for example databases), and **Web** (crawled properties from web sites).

-

-

-To include the contents and metadata of crawled properties in the search index, you must map crawled properties to managed properties. Only managed properties are written to the search index.

-

-

-You can map multiple crawled properties to a single managed property. For example, you can map both the "Writer" and "Author" crawled properties to the "Author" managed property. Or, you can map a single crawled property to multiple managed properties.

-

-Also, the order in which crawled properties are mapped to a managed property can determine the content of a managed property. For example, a managed property can have multiple crawled properties mapped to it and can be set to includes all values from all crawled properties mapped to it. But, if you give the crawled property containing the SharePoint title priority over another title in the mapping, it will show the SharePoint title in the search results.

-

-

-

-You can change the default mapping or any other mapping from crawled to managed properties, create new mappings, or create new managed properties. When you create a new managed property, or when you change certain settings on existing managed properties, a full crawl must complete before the managed property and its value is included in the search index. If the new or changed property is in a SharePoint library or list, you can reindex that individual library or list without starting a full crawl of the entire SharePoint content source. This has the same effect as a full crawl.

-

-See the table [Managed property settings overview](search-schema-overview.md#MP_Overview) later in this article for more information.

-

-The search schema is stored in the Search Administration database. The search schema contains:

-

-

-

-

-

-

-You can create multiple search schemas. The main search schema is defined in the Search service application and can be edited in the Central Administration. Site collection administrators and tenant administrators can change the search schema for a particular site collection or tenant. For example, a site collection administrator can customize what is included in the search index by changing the search schema for that site collection and, by doing this, customize the search experience for that site collection. Site owners can view the search schema, but not change it.

-

-> You can't view or change the site collection search schema in Central Administration. To view or make changes in the search schema for a site collection, you have to use Site Collection Administration.

-

-

-

-

-

-

-

-

-

-

-There are two pre-defined full-text indexes other than the default full-text index: the SharePoint Terms full-text index ( **SpTermsIdx** ) and the People index ( **PeopleIdx** ).

-

-Most managed properties are already mapped to a suitable context and full-text index by default. We do not recommend changing the context of any of the existing searchable managed properties.

-

-Settings on the managed properties determine how content is saved in the search index and if and how people can search for and retrieve it.

-

-

-| **Managed property setting** | **What it does** | **Example** | **Available in** | **Full crawl or reindex SharePoint list/library required after changing setting** |

-| :-- | : | : | : | :-- |

-| Searchable | Enables querying against the content of the managed property. The content of this managed property is included in the full-text index. | If the property is "author", a simple query for "Smith" returns items that contain the word "Smith" and items whose author property contains "Smith". | Central Administration / Site Collection Administration / Tenant Administration | Yes |

-| Advanced Searchable Settings | Enables viewing and changing the full-text index that the managed property is written to. It also allows you to change the context of the managed property for the relevance rank calculation. We do not recommend changing the context of any of the existing managed properties. For more information, see the section [Influence the ranking of search results by using the search schema](overview-of-search-result-ranking.md#Ranking_Schema) in the article [Overview of search result ranking in SharePoint Server](overview-of-search-result-ranking.md). | | Central Administration / Site Collection Administration / Tenant Administration | Yes |

-| Queryable | Enables querying against the specific managed property. The managed property name must be included in the query, either specified in the query itself or included in the query programmatically. | If the managed property is "author", the query must contain "

-| Retrievable | Enables the content of this managed property to be returned in search results. Enable this setting for managed properties that are relevant to present in search results. | | Central Administration /Site Collection Administration /Tenant Administration | From disabled to enabled. |

-| Allow multiple values | Allows multiple values of the same type in this managed property. | If this is the "author" managed property, and a document has multiple authors, each author name will be stored as a separate value in the managed property. | Central Administration | Yes |

-| Refinable | Yes - active: Enables using the property as a refiner for search results in the front end. You must manually configure the refiner in the web part. <br/> <br/> Yes - latent: Enables switching refinable to active later, without having to do a full re-crawl when you switch. <br/> <br/> Both options require a full crawl to take effect. <br/><br/> **IMPORTANT:** If you select Yes - active or Yes - latent, you must also make the managed property Queryable.<br/><br/>Not supported in the modern search experience. | If the "author" managed property is set to Refinable, you can set up Author as a refiner in your search front-end later. | Central Administration | From disabled to enabled (if not already set to Sortable) |

-| Sortable | Yes - active: Enables sorting the result set based on the property before the result set is returned. <br/> <br/> Yes - latent: Enables switching sorting to active later without having to do a full re-crawl when you switch. <br/> <br/> Both options require a full crawl to take effect.<br/><br/>Not supported in the modern search experience. | Use for large result sets that cannot be sorted and retrieved at the same time. | Central Administration | From disabled to enabled (if not already set to Refinable) |

-| Alias | Defines an alias for a managed property if you want to use the alias instead of the managed property name in queries and in search results. Use the original managed property and not the alias to map to a crawled property. | Use an alias if you don't want to or don't have permission to create a new managed property. | Central Administration / Site Collection Administration / Tenant Administration | No |

-| Token normalization | Enables returning results independent of letter casing and diacritics used in the query. | The query "curacao" will also match "Curaçao", "curacao" and "Curacao". | Central Administration / Site Collection Administration / Tenant Administration | Yes |

-| Complete matching | By default, search returns partial matches between queries against a managed property and the content of the managed property. <br/> <br/>Select Complete Matching for search to return exact matches instead. | If a managed property "Title" contains "Contoso Sites", only the query Title: "Contoso Sites" will give a result. | Central Administration / Site Collection Administration / Tenant Administration | Yes |

-| Language neutral tokenization (SharePoint Server 2019 only) | Select language neutral tokenization if you have multilingual content and the managed property contains tags that are based on metadata term sets or other identifiers.<br/> <br/>By default, search depends on language when it breaks queries and content into parts (tokenization). For example, a document library containing both English and Chinese product datasheets where product identifiers have non-alphanumerical characters, such as ΓÇ£11.132-84-115#4ΓÇ¥. When search processes a datasheet, it detects its language, and tokenizes **everything** in it according to that language. When users search for a product identifier, search tokenizes their query according to the language setting of the SharePoint site theyΓÇÖre on. If the site is set to English, and the user searches for a product identifier that was tokenized as Chinese text, the tokens **might not** match, and the users get no results.<br/> <br/> To make results better for users, map the crawled property for the product identifier to a new managed property, ΓÇ£ProductIDΓÇ¥, with language neutral tokenization enabled. Instruct users to search for product identifiers against the new managed property, like this: ProductID:ΓÇ¥11.132-8ΓÇ¥. | If the crawled property for a product identifier is mapped to a the managed property ΓÇ£ProductIDΓÇ¥, then search uses language neutral tokenization for queries against "ProductID". | Central Administration / Site Collection Administration / Tenant Administration | Yes |

-| Finer query tokenization (SharePoint Server 2019 only) | Use this setting to help users get better search results when they search in managed properties that contain metadata with non-alphanumeric characters. This setting makes queries against the managed property slower.<br/> <br/>Users who prefer to quickly enter a query and then browse the results to find the datasheet theyΓÇÖre looking for, typically enter queries like ProductID:ΓÇ¥132-884ΓÇ¥. Because search by default breaks content for the search index into smaller parts than it does for queries, search might not find matches for these queries. When the query is tokenized finer, itΓÇÖs more likely that there are matches between the tokens in the search index and in the query. Users can also query for the middle or last part of the product identifier.<br/> <br/>Users who search for a datasheet and expect to only get results that match the full product identifier, typically write queries like ProductID:ΓÇ¥11.132-884-115#4ΓÇ¥. Finer query tokenization doesnΓÇÖt make a difference for such queries. | If you have a managed property "Product identifier" that contains ΓÇ£11.132-884-115#4ΓÇ¥, searches like ProductID:ΓÇ¥132-884ΓÇ¥ will likely get results. | Central Administration / Site Collection Administration / Tenant Administration | No |

-| Mappings to crawled properties | The list shows all the crawled properties that are mapped to this managed property. A managed property can get its content from one or more crawled properties. <br/> <br/> You can either include content from all crawled properties or include content from the first crawled property that is not empty, based on a specified order. | | Central Administration / Site Collection Administration / Tenant Administration | Yes |

-| Company name extraction | Enables the system to extract company name entities from the managed property when crawling new or updated items. The extracted entities can later be used to set up refiners. <br/> <br/> There is one pre-populated dictionary for company name extraction. The system saves the original managed property content unchanged in the index, and, in addition, copies the extracted entities to the managed property "companies". The "companies" managed property is configured to be searchable, queryable, retrievable, sortable and refinable. <br/> <br/> You can edit the company name dictionary in the Term Store. <br/> <br/> For more information, see [Manage company name extraction in SharePoint Server](manage-company-name-extraction.md).<br/><br/>Not supported in the modern search experience. | | Central Administration / Site Collection Administration / Tenant Administration | Yes |

-| Custom entity extraction | Enables one or more custom entity extractors to be associated with this managed property. This enables the system to extract entities from the managed property when crawling new or updated items. The extracted entities can later be used to set up refiners. <br/><br/> For more information, see [Create and deploy custom entity extractors in SharePoint Server](create-and-deploy-custom-entity-extractors.md).<br/><br/>Not supported in the modern search experience. | | Central Administration / Site Collection Administration | Yes |

-

-

-

-[Plan crawling and federation in SharePoint Server](plan-crawling-and-federation.md)

-But why is "CSH_Configure_ **result_types…** "displayed in the search results? In the list item we can see that this is the value for Project/File Name, but the managed property for that site column is not included in the **ManagedPropertyMapping** element in display template. Neither is it listed as one of the hit highlighted properties in the Search Results Web Part. So why is this value displayed?

-## Overview ##

-Request Manager is functionality in SharePoint Server that enables administrators to manage incoming requests and determine how SharePoint Server routes these requests.

-|**Area**|**Scenario**|**Resolution**|

-|:--|:--|:--|

-|**Reliability and performance** <br/> |Routing new requests to web front end with low performance can increase latency and cause timeouts. <br/> |Request Manager can route to front-end web servers that have better performance, keeping low performance front-end web servers available. <br/> |

-|Requests from users and bots have equal priority.<br/> |Prioritize requests by throttling requests from bots to instead serve requests from end-users).<br/> |

-|**Manageability, accountability, and capacity planning** <br/> |SharePoint Server fails or generally responds slowly, but itΓÇÖs difficult to identify the cause of a failure or slowdown. <br/> |Request Manager can send all requests of a specific type, for example, Search, User Profiles, or Office Online, to specific computers. When a computer is failing or slow, Request Manager can locate the problem. <br/> |

-|All front-end web servers must be able to handle the requests because they could be sent to any front-end web server. <br/> |Request Manager can send multiple or single requests to front-end web servers that are designated to handle them. <br/> |

-|**Scaling limits** <br/> |Hardware scaling limited by load balancer <br/> |Request Manager can perform application routing and scale out as needed so that a load balancer can quickly balance loads at the network level. <br/> |

-## Setup and Deployment ##

-**NOTE**: There is no user interface to configure properties of Request Manager. The Windows PowerShell cmdlet is the only way to perform this task.

-Request Manager has two supported deployment modes: Dedicated and Integrated.

-### Dedicated mode ###

-### Integrated mode ###

-In an integrated mode deployment, all SharePoint front-end web servers run Request Manager. Hardware load balancers send requests to all front-end web servers. When a front-end web server receives a request, Request Manager decides how to handle it: .

-## Configuration ##

-**Note**: You configure Request Manager on a farm and functionality occurs at a web application level in SharePoint Server 2013 and the web application role in SharePoint Servers 2016 and 2019.

-### General settings ##

-|**Situation**|**Microsoft PowerShell example**|&nbsp;|

-|:--|:--|:--|

-|Enable routing and throttling for all web applications <br/>| ```Get-SPWebApplication | Set-SPRequestManagementSettings ΓÇôRoutingEnabled $true ΓÇôThrottlingEnabled $true ```<br/> ||

-|Enable routing with static weighting for all web applications <br/>| ```Get-SPWebApplication | Get-SPRequestManagementSettings | Set-SPRequestManagementSettings ΓÇôRoutingEnabled $true ΓÇôThrottlingEnabled $false ΓÇôRoutingWeightScheme Static```<br/> ||

-In some situations, multiple front-end web servers will be suitable destinations for a particular request. In this case, by default, SharePoint Server selects one server randomly and uniformly.

-### Decision information ###

-### Routing targets ###

-Request routing determines the routing targets that are available when a routing pool is selected for a request. The scope of routing targets is currently for front-end web servers only, but Request ManagerΓÇÖs design does not exclude routing to application servers, too. A list of front-end web servers in a farm is automatically maintained by using the configuration database. An administrator who wants to change that list, typically in dedicated mode, has to use the appropriate routing cmdlets to get, add, set, and remove routing targets.

-|**Task**|**Microsoft PowerShell example**|&nbsp; |

-|:--|:--|:--|

-|Return a list of routing targets for all available web applications <br/>| ```Get-SPWebApplication | Get-SPRequestManagementSettings | Get-SPRoutingMachineInfo ΓÇôAvailability Available ```<br/> ||

-|Add a new routing target for a specified web application. <br/>| ```$web=Get-SPWebApplication -Identity <URL of web application> ``` <br/> ||

-| <br/>| ```$rm=Get-SPRequestManagementSettings -Identity $web ``` <br/> ||

-| <br/>| ```Add-SPRoutingMachineInfo ΓÇôRequestManagementSettings $rm -Name <MachineName> -Availability Available ``` <br/> ||

-|Edit an existing routing targetΓÇÖs availability and static weight for a specified web application. <br/>| ```$web=Get-SPWebApplication -Identity <URL of web application> ``` <br/> ||

-| <br/>| ```$rm=Get-SPRequestManagementSettings -Identity $web ``` <br/> ||

-| <br/>| ```$m=Get-SPRoutingMachineInfo -RequestManagementSettings $rm -Name <MachineName> ``` <br/> ||

-| <br/>| ```Set-SPRoutingMachineInfo -Identity $m -Availability Unavailable ``` <br/> ||

-|Remove a routing target from a specified web application. <br/>| ```$web=Get-SPWebApplication -Identity <URL of web application> ``` <br/> ||

-| <br/>| ```$rm=Get-SPRequestManagementSettings -Identity $web ``` <br/> ||

-| <br/>| ```$m=Get-SPRoutingMachineInfo -RequestManagementSettings $rm -Name <MachineName> ``` <br/> ||

-| <br/>| ```Remove-SPRoutingMachineInfo -Identity $M ``` <br/> ||

-**Note**: You cannot remove front-end web servers that are in the farm. Instead, you can use the **Availability** parameter of the **Set-SPRoutingMachineInfo** cmdlet to make them unavailable.

-### Routing and throttling rules ##

-## Request Routing ##

-Request processing is divided into the components:

-### Incoming request handler ###

-1. Request is determined if it should be throttled or routed

-2. For routed requests, load balance algorithm is run

-3. Request routed to load balancer endpoint

-Request routing and Request throttling and prioritizing only run if it is enabled and is routed once per farm. Request load balancer only runs if a request has been determined as routable. The outgoing request handler only runs if the request has to be sent to a different front-end web server. The role of the outgoing request handler is to send the request to the selected front-end web server, wait for a response, and send the response back to the source.

-### Request routing ###

-The role of request routing is to select a front-end web server to route a request. By using no routing rules that are defined, the routing scheme is as easy as randomly selecting an available front-end web server.

-The algorithm of request routing is defined by two parts: request-rule matching and front-end web server selection.

-### Request rule matching ###

-| Match property | Match type | &nbsp; |

-|:--|:--|:--|

-|Hostname <br/>| ReqEx| <br/> ||

-|URL <br/>| Equals<br/> ||

-|Port number <br/>| Starts with<br/> ||

-|MIME type <br/>| Ends with<br/> ||

-For example, an administrator would use the following match criteria to match http://contoso requests: Match Property=URL; Match value= http://contoso; Match type=RegEx.

-### Front-end web server selection ###

-The front-end web server selection uses all routing rules, whether they match or do not match a given request. Rules that match have machine pools, a request sends load balanced to any machine in any matching ruleΓÇÖs machine pool. If a request does not match any request, it sends load balanced to any available routing target.

-### Request routing and prioritizing ###

-1. The routing pool is either the current front-end web server or one or more front-end web servers that request routing selects.

-2. All matching rules are checked to find the smallest health threshold value.

-3. Remove front-end web servers in the routing pool that have health scores greater than or equal to the smallest health threshold value.

-For example, request routing is disabled and the current front-end web server has a health score of 7 and a rule ΓÇ£Block OneNoteΓÇ¥ without a health threshold (that is, health threshold = 0) is created.

-### Request load balancing ###

-## Monitoring and maintenance ##

-Monitoring and logging are keys to managing requests from Request Manager.

-| Counter name | Description | &nbsp; |

-|:--|:--|:--|

-|Connections Current <br/>| The total number of connections that are currently open by Request Manager.| <br/> ||

-|Connections Reused / Sec <br/>| The number of connections per second that are reused when the same client connection makes another request without closing the connection.<br/> ||

-|Routed Requests / Sec <br/>| The number of routed requests per second. The instance determines the application pool and server for which this counter tracks.<br/> ||

-|Throttled Requests / Sec <br/>| The number of throttled requests per second.<br/> ||

-Failed Requests / Sec <br/>| Ends with<br/> ||

-|MIME type <br/>| The number of failed requests per second.<br/> ||

-|Average Processing Time<br/>| Ends with<br/> ||

-|MIME type <br/>| The time to process the request that is, the time to evaluate all the rules and determine a routing target.<br/> ||

-|Last Ping Latency<br/>| The last ping latency (that is, Request Manager's PING feature) and the instance determine which application pool and machine target.<br/> ||

-|Connection Endpoints Current <br/>| The total number of endpoints that are connected for all active connections.<br/> ||

-|Routed Requests Current <br/>| The number of unfinished routed requests. The instance determines which application pool and machine target.<br/> ||

-```

-Set-SPLogLevel ΓÇ£Request ManagementΓÇ¥ ΓÇôTraceSeverity Verbose

-> If you do not update each of these locations, you run the risk of systems failing to connect to each other using TLS 1.1 or TLS 1.2. The systems will instead fall back to an older security protocol; and if the older security protocols are disabled, the systems may fail to connect entirely. > **Example:** SharePoint servers may fail to connect to SQL Server databases, or client computers may fail to connect to your SharePoint sites.

-|The following steps are **recommended**. Although not directly required by SharePoint Server 2016, they may be necessary for other software that integrates with SharePoint Server 2016. <br/> |

-|The following step is **optional**. You may choose to run this step based on your organization's security and compliance requirements. <br/> |

-5. Click **Yes** to update your Windows Registry with these changes.

-|The following step is **recommended**. Although not directly required by SharePoint Server 2016, they provide better security by restricting the use of weak encryption algorithms. <br/> |

-|The following step is **optional**. You may choose to run this step based on your organization's security and compliance requirements. <br/> |

-> If you do not update each of these locations, you run the risk of systems failing to connect to each other using TLS 1.1 or TLS 1.2. The systems will instead fall back to an older security protocol; and if the older security protocols are disabled, the systems may fail to connect entirely. > **Example:** SharePoint servers may fail to connect to SQL Server databases, or client computers may fail to connect to your SharePoint sites.

-|The following steps are **recommended**. Although not directly required by SharePoint Server 2013, they may be necessary for other software that integrates with SharePoint Server 2013. <br/> |

-|The following step is **optional**. You may choose to run this step based on your organization's security and compliance requirements. <br/> |

-|The following step is **recommended**. Although not directly required by SharePoint Server 2013, they provide better security by restricting the use of weak encryption algorithms. <br/> |

-|The following step is **optional**. You may choose to run this step based on your organization's security and compliance requirements. <br/> |

-1. Check that you have the following memberships:

-2. To migrate a web application to include all content databases, type the following at the Windows PowerShell command prompt.

-1. Check that you have the following memberships:

-2. To migrate specific web applications and content databases, type the following at the Windows PowerShell command prompt.

- **System.Data.SqlClient.SqlException… \<operation type\> permission denied in database \<database\>. Table \<table\>**

-TLS 1.3 is the latest version of the TLS encryption protocol. SharePoint Server Subscription Edition by default supports TLS 1.3 when deployed with Windows Server 2022 and 2021-06 Cumulative Update for .NET Framework 3.5, and 4.8 for Microsoft server operating system x64 (KB5003529)ΓÇ¥.

-> [!NOTE]

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-|**Type**|**Name**|**Description**|**Availability**|

-|**Collaboration** <br/> |Team Site <br/> |A place to work together with a group of people. <br/> **SharePoint Server 2019** offers a modern and classic team site. <br/> |Site collection and site <br/> |

-|**Collaboration** <br/> |Blog <br/> |A site for a person or team to post ideas, observations, and expertise that site visitors can comment on. <br/> |Site collection and site <br/> |

-|**Collaboration** <br/> |Developer Site <br/> |A site for developers to build, test, and publish apps for Office. <br/> |Site collection only <br/> |

-|**Collaboration** <br/> |Project Site <br/> |A site for managing and collaborating on a project. This site template brings all status, communication, and artifacts relevant to the project into one place. <br/> |Site collection and site <br/> |

-|**Collaboration** <br/> |Community Site <br/> |A place where community members discuss topics of common interest. Members can browse and discover relevant content by exploring categories, sorting discussions, by popularity or by viewing only posts that have a best reply. Members gain reputation points by participating in the community, such as starting discussions and replying to them, liking posts, and specifying best replies. <br/> |Site collection and site <br/> |

-|**Enterprise** <br/> |Document Center <br/> |A site to centrally manage documents in your enterprise. <br/> |Site collection and site <br/> |

-|**Enterprise** <br/> |In-Place Hold Policy Center <br/> |A site to manage policies to preserve content for specific amounts of time. <br/> |Site collection only <br/> |

-|**Enterprise** <br/> |eDiscovery Center <br/> |A site to manage the preservation, search, and export of content for legal matters and investigations. <br/> |Site collection only <br/> |

-|**Enterprise** <br/> |Records Center <br/> |This template creates a site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site also lets you manage whether records can be deleted or modified after they are added to the repository. <br/> |Site collection and site <br/> |

-|**Enterprise** <br/> |Business Intelligence Center <br/> |A site for presenting Business Intelligence content. <br/> |Site collection and site <br/> |

-|**Enterprise** <br/> |Compliance Policy Center <br/> |A site to manage policies and delete documents after specified times. <br/> |Site collection and site <br/> |

-|**Enterprise** <br/> |Enterprise Search Center <br/> |A site focused on delivering an enterprise-wide search experience. <br/> **Note:** <br/> Search Centers should be separate site collections because they search for information across a company portal or division. If you create a Search Center as a subsite, you might have to create some workarounds for a full customization. For more info, see [Customizing the Search Center](/previous-versions/office/developer/sharepoint-2010/ee872308(v=office.14)). <br/> |Site collection and site <br/> |

-|**Enterprise** <br/> |My Site Host <br/> |A site used for hosting personal sites (My Sites) and the public People Profile page. <br/> |Site collection only <br/> |

-|**Enterprise** <br/> |Community Portal <br/> |A site for discovering communities. <br/> |Site collection only <br/> |

-|**Enterprise** <br/> |Basic Search Center <br/> |A site focused on delivering a basic search experience. It includes a welcome page with a search box that connects users to a search results page and an advanced search page. This Search Center will not appear in navigation. <br/> **Note:** <br/> Search Centers should be separate site collections because they search for information across a company portal or division. If you create a Search Center as a subsite, you might have to create some workarounds for a full customization. For more info, see [Customizing the Search Center](/previous-versions/office/developer/sharepoint-2010/ee872308(v=office.14)). <br/> |Site collection and site <br/> |

-|**Enterprise** <br/> |Visio Process Repository <br/> |A site for viewing, sharing, and storing Visio process diagrams. It includes a versioned document library and templates for Basic Flowcharts, Cross-functional Flowcharts, and BPMN diagrams. <br/> **Note:** <br/> The Visio Process Repository site template will be removed in the next version of SharePoint Server. <br/> |Site collection and site <br/> |

-|**Publishing** <br/> |Publishing Portal <br/> |A starter hierarchy for an Internet-facing site or a large intranet portal. This site can be customized easily with distinctive branding. Typically, this site has many more readers than contributors and it is used to publish web pages with approval workflows. <br/> |Site collection only <br/> |

-|**Publishing** <br/> |Enterprise Wiki <br/> |A site for publishing knowledge that you capture and want to share across the enterprise. <br/> |Site collection and site <br/> |

-|**Publishing** <br/> |Product Catalog <br/> |A site for managing product catalog data that can be published to an Internet-facing site through search. <br/> |Site collection only <br/> |

-|**Publishing** <br/> |Communication Site <br/> |Available in SharePoint Server 2019 only as a modern experience. A site for publishing dynamic, modern content to people in your organization to keep them informed and engaged on topics, events, or projects. <br/> |Site collection only <br/> |

-|**Custom** <br/> |\<Select template later…\> <br/> |Create an empty site and pick a template for the site at a later time. <br/> |Site collection only <br/> |

-

-

-|**Type**|**Name**|**Description**|**Availability**|

-|**Collaboration** <br/> |Team Site <br/> |A place to work together with a group of people. <br/> |Site collection and site, Server, and Foundation <br/> |

-|**Blog** <br/> ||A site for a person or team to post ideas, observations, and expertise that site visitors can comment on. <br/> |Site collection and site, Server, and Foundation <br/> |

-|**Develop Site** <br/> ||A site for developers to build, test, and publish apps for Office. <br/> |Site collection and site, Server, and Foundation <br/> |

-|**Project Site** <br/> ||A site for managing and collaborating on a project. This site template brings all status, communication, and artifacts relevant to the project into one place. <br/> |Site collection and site, Server only <br/> |

-|**Community Site** <br/> ||A place where community members discuss topics of common interest. Members can browse and discover relevant content by exploring categories, sorting discussions, by popularity or by viewing only posts that have a best reply. Members gain reputation points by participating in the community, such as starting discussions and replying to them, liking posts, and specifying best replies. <br/> |Site collection and site, Server only <br/> |

-|**Enterprise** <br/> |Document Center <br/> |A site to centrally manage documents in your enterprise. <br/> |Site collection and site, Server only <br/> |

-|**eDiscovery Center** <br/> ||A site to manage the preservation, search, and export of content for legal matters and investigations. <br/> |Site collection only, Server only <br/> |

-|**Records Center** <br/> ||This template creates a site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site also lets you manage whether records can be deleted or modified after they are added to the repository. <br/> |Site collection and site, Server only <br/> |

-|**Business Intelligence Center** <br/> ||A site for presenting Business Intelligence content. <br/> |Site collection and site, Server only <br/> |

-|**Enterprise Search Center** <br/> ||A site focused on delivering an enterprise-wide search experience. <br/> **Note:** <br/> Search Centers should be separate site collections because they search for information across a company portal or division. If you create a Search Center as a subsite, you might have to create some workarounds for a full customization. For more information, see [Customizing the Search Center](/previous-versions/office/developer/sharepoint-2010/ee872308(v=office.14)) in the MSDN Library. <br/> |Site collection and site, Server only <br/> |

-|**My Site Host** <br/> ||A site used for hosting personal sites (My Sites) and the public People Profile page. <br/> |Site collection only, Server only <br/> |

-|**Community Portal** <br/> ||A site for discovering communities. <br/> |Site collection only, Server only <br/> |

-|**Basic Search Center** <br/> ||A site focused on delivering a basic search experience. It includes a welcome page with a search box that connects users to a search results page and an advanced search page. This Search Center will not appear in navigation. <br/> **Note:** <br/> Search Centers should be separate site collections because they search for information across a company portal or division. If you create a Search Center as a subsite, you might have to create some workarounds for a full customization. For more information, see [Customizing the Search Center](/previous-versions/office/developer/sharepoint-2010/ee872308(v=office.14)) in the MSDN Library. <br/> |Site collection and site, Server, and Foundation <br/> |

-|**Visio Process Repository** <br/> ||A site for viewing, sharing, and storing Visio process diagrams. It includes a versioned document library and templates for Basic Flowcharts, Cross-functional Flowcharts, and BPMN diagrams. <br/> **Note:** <br/> The Visio Process Repository site template will be removed in the next version of SharePoint Server. <br/> |Site collection and site, Server only <br/> |

-|**Publishing** <br/> |Publishing Portal <br/> |A starter hierarchy for an Internet-facing site or a large intranet portal. This site can be customized easily with distinctive branding. Typically, this site has many more readers than contributors and it is used to publish web pages with approval workflows. <br/> |Site collection only, Server only <br/> |

-|**Enterprise Wiki** <br/> ||A site for publishing knowledge that you capture and want to share across the enterprise. <br/> |Site collection and site, Server only <br/> |

-|**Product Catalog** <br/> ||A site for managing product catalog data that can be published to an Internet-facing site through search. <br/> |Site collection only, Server only <br/> |

-|**Blank** <br/> |Publishing site <br/> |A blank site for expanding your website and quickly publishing web pages. Contributors can work on draft versions of pages and publish them to make them visible to readers. The site includes document and image libraries for storing web publishing assets. <br/> |Site only, Server only <br/> |

-||Publishing Site with workflow <br/> |A site for publishing web pages on a schedule by using approval workflows. It includes document and image libraries for storing web publishing assets. By default, only sites with this template can be created under this site. <br/> |Site only, Server only <br/> |

-|**Custom** <br/> |\<Select template later…\> <br/> |Create an empty site and pick a template for the site at a later time. <br/> |Site collection only, Server, and Foundation <br/> |

-

-

-|**Type**|**Name**|**Description**|**Availability**|

-|Collaboration <br/> |Team Site <br/> |Same functionality as the 2013 Team site. <br/> |Site collection and site, Server, and Foundation <br/> |

-|Blank Site <br/> |A blank site for you to customize based on your requirements. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Document Workspace <br/> |A site for colleagues to work together on a document. It provides a document library for storing the primary document and supporting files. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Blog <br/> |Same functionality as the 2013 Blog site. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Group Work Site <br/> |This template provides a groupware solution that enables teams to create, organize, and share information. It includes a Group Calendar, Circulation, Phone-Call Memo, a document library, and other basic lists. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Visio Process Repository <br/> |Same functionality as the 2013 Visio Process Repository. <br/> |Site collection and site, Server only <br/> |Site collection and site, Server, and Foundation <br/> Site collection and site, Server, and Foundation <br/> |

-|Meetings <br/> |Basic Meeting Workspace <br/> |A site to plan, organize, and capture the results of a meeting. It provides lists for managing the agenda, meeting attendees, and documents. <br/> |Site collection and site, Server, and Foundation <br/> |

-|Blank Meeting Workspace <br/> |A blank meeting site for you to customize based on your requirements. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Decision Meeting Workspace <br/> |A site for meetings that track status or make decisions. It provides lists for creating tasks, storing documents, and recording decisions. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Social Meeting Workspace <br/> |A site to plan social occasions. It provides lists for tracking attendees, providing directions, and storing pictures of the event. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Multipage Meeting Workspace <br/> |A site to plan, organize, and capture the results of a meeting. It provides lists for managing the agenda and meeting attendees in addition to two blank pages for you to customize based on your requirements. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server, and Foundation <br/> |

-|Enterprise <br/> |Document Center <br/> |A site to centrally manage documents in your enterprise. <br/> |Site collection and site, Server only <br/> |

-|Records Center <br/> |This template creates a site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. <br/> |Site collection and site, Server only <br/> |Site collection and site, Server only <br/> |

-|Business Intelligence Center <br/> |Same functionality as the 2013 Business Intelligence site. <br/> |Site collection only, Server only <br/> |Site collection and site, Server only <br/> |

-|Enterprise Search Center <br/> |A site for delivering the search experience. It includes a search box with scopes for general searches and for people searches. You can add and customize tabs to focus on other search scopes or result types. <br/> |Site collection and site, Server only <br/> |Site collection and site, Server only <br/> |

-|My Site Host <br/> |Same functionality as the 2013 My Site Host site. <br/> |Site collection only, Server only <br/> |Site collection and site, Server only <br/> |

-|Basic Search Center <br/> |A site for delivering the search experience. The site includes pages for search results and advanced searches. <br/> |Site collection and site, Server, and Foundation <br/> |Site collection and site, Server only <br/> |

-|FAST Search Center <br/> |A site for delivering the FAST search experience. <br/> |Site collection and site, Server only <br/> |Site collection and site, Server only <br/> |

-|Publishing <br/> |Publishing Portal <br/> |Same functionality as the 2013 Publishing Portal site. <br/> |Site collection only, Server only <br/> |

-|Enterprise Wiki <br/> |Same functionality as the 2013 Enterprise Wiki site. <br/> |Site collection only, Server only <br/> |Site collection only, Server only <br/> |

-|Publishing Site with Workflow <br/> |Same functionality as the 2013 Publishing Site with Workflow site. <br/> |2010 site only, Server only <br/> |Site collection only, Server only <br/> |

-|Custom <br/> |\<Select template later…\> <br/> |Same functionality as the 2013 \<Select template later…\> option. <br/> |Site collection only, Server, and Foundation <br/> |

-|Web Databases <br/> |Assets Web Database <br/> |Create an assets database to keep track of assets, including asset details and owners. <br/> |2010 site only <br/> |

-|Charitable Contributions Web Database <br/> |Create a database to track information about fundraising campaigns including donations made by contributors, campaign-related events, and pending tasks. <br/> |2010 site only <br/> |2010 site only <br/> |

-|Contacts Web Database <br/> |Create a contacts database to manage information about people that your team works with, such as customer and partner. <br/> |2010 site only <br/> |2010 site only <br/> |

-|Issues Web Database <br/> |Create an issues database to manage a set of issues or problems. You can assign, prioritize, and follow the progress of issues from start to finish. <br/> |2010 site only <br/> |2010 site only <br/> |

-|Projects Web Database <br/> |Create a project tracking database to track multiple projects and assign tasks to different people. <br/> |2010 site only <br/> |2010 site only <br/> |

-

-> The Web Databases site templates that are available through the 2010 experience sites in SharePoint 2013 are no longer available in the 2013 experience sites in SharePoint 2013. In SharePoint Server 2016, you create an Access database by creating a new app, instead of creating a site.

-

-> Some SharePoint 2010 Products site templates, such as the Document Workspace Site templates, were deprecated and are not available as an option in SharePoint 2013. Existing sites that were created by using these deprecated site templates and then upgraded will continue to operate in SharePoint 2013. The deprecated site templates will be removed completely from the next version of SharePoint.

-

-

-

-

-

-> You cannot save a SharePoint publishing site collection or site as a template. If you activate the SharePoint Server Publishing Infrastructure feature on a non-publishing site collection, the **Save site as template** link is removed from the **Site Actions** section on the **Site Settings** page.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-[Overview of site policies in SharePoint Server](site-policy-overview.md)

-

-

-

-

-

-

-

-

-

-

-

-> The four letter code represents the site column type, not the managed property type. All automatically created managed properties are of type Text.

-

-| Site column type | Crawled property name | Managed property name | Data format |

-|Single line of text | ows_q_TEXT_SiteColumnName |SiteColumnNameOWSTEXT |As is. |

-|Multiple lines of text |ows_r_MTXT_SiteColumnName |SiteColumnNameOWSMTXT |As is. |

-|Choice |ows_q_CHCS_SiteColumnName |SiteColumnNameOWSCHCS |The text value of the choice. |

-|Choice (allow multiple selections) |ows_q_CHCM_SiteColumnName |SiteColumnNameOWSCHCM |Selected values separated by semicolon and hash mark ΓÇö for example, MultiValue 2;# MultiValue 4;#. |

-|Number |ows_q_NMBR_SiteColumnName |SiteColumnNameOWSNMBR |Textual representation of the number. The value will use dot as a decimal symbol. <br/> This format cannot be used in a greater than or less than comparison with other integers. It should only be used when querying for and displaying an exact value. |

-|Currency |ows_q_CURR_SiteColumnName |SiteColumnNameOWSCURR |Textual representation of the number. The value will use dot as a decimal symbol. <br/> This format cannot be used in a greater than or less than comparison with other integers. It should only be used when querying for and displaying an exact value. |

-|Date and Time |ows_q_DATE_SiteColumnName |SiteColumnNameOWSDATE |Textual representation of the date in the format YYYY-MM-DDTHH:MM:SSZ. For example, December 25, 2012, 7 AM GMT is 2012-12-25T07:00:00Z. <br/> This format cannot be used in a greater than or less than comparison with other dates. It should only be used when querying for and displaying an exact date. |

-|Yes/No |ows_q_BOOL_SiteColumnName |SiteColumnNameOWSBOOL |For true, use value 1. For false, use value 0. |

-|Person or Group |ows_q_USER_SiteColumnName |SiteColumnNameOWSUSER |Email, Display name, or Encoded claim. For example, ellenk@contoso.com, Ellen Kessels, or i:0#.w&#x7c;contoso\ellenk|

-|Hyperlink or Picture |ows_q_URLH_SiteColumnName |SiteColumnNameOWSURLH |URL, description. For example, http://www.contoso.com, Welcome to the home page of Contoso. |

-|Publishing HTML |ows_r_HTML_SiteColumnName |SiteColumnNameOWSHTML |Html escaped enclosed in a paragraph tag. For example, \<p\>&amp;lt;div&amp;gt;&amp;lt;b&amp;gt;some html &amp;lt;/b&amp;&amp;lt;/div&amp;gt;\</p\>. |

-|Publishing Image |ows_q_IMGE_SiteColumnName |SiteColumnNameOWSIMGE |Html image tag. For example, \<img alt="" src="/sites/pub/SiteCollectionImages/home.jpg" style="BORDER&amp;#58;0px solid;" \/>. |

-|Publishing Link |ows_q_LINK_SiteColumnName |SiteColumnNameOWSLINK |Html link tag. For example, \<a href="http&amp;#58;//www.microsoft.com" target="_blank" title="mytooltip"\>Microsoft Website\</a\>. |

-|Managed Metadata |ows_taxId_SiteColumnName |owstaxIdSiteColumnName |See "Data format for Managed Metadata" below. |

-|Integer\* |ows_q_INTG_SiteColumnName |SiteColumnNameOWSINTG |Textual representation of the integer. <br/> This format cannot be used in a greater than or less than comparison with other integers. It should only be used when querying for and displaying an exact value. |

-|GUID\* |ows_q_GUID_SiteColumnName |SiteColumnNameOWSGUID |Values separated by hyphens, enclosed in brackets. For example, {147C6BA1-709C-4401-964A-27AC36B62C54}. |

-|Grid Choice\* |ows_q_CHCG_SiteColumnName |SiteColumnNameOWSCHCG |For each row, row name separated by semi-colon and hash mark, followed by the selected value. |

-|ContentTypeIDFieldType\* |ows_q_CTID_SiteColumnName |SiteColumnNameOWSCTID |Name:#ContentTypeID;# |

-|SPS average rating |ows_q_RAVG_SiteColumnName |SiteColumnNameOWSRAVG |Textual representation of the number. The value will use dot as a decimal symbol. |

-|SPS rating count |ows_q_RCNT_SiteColumnName |SiteColumnNameOWSRCNT |Textual representation of the integer. |

-

-\*Column creation not available through user interface.

-

-> Automatic creation of managed properties is not supported for the following site column types: > Lookup > Calculated > Task outcome > Summary Links data > Rich media data for publishing

-

-

-To query for items tagged with a Managed Metadata field, you have to use the Unique Identifier for each label. You can find the Unique Identifier for each term in a term set in the Term Store Management Tool, on the **GENERAL** tab. In addition, the data format that is used in the query has to specify from which level in the term set the query should apply. This specification is set by adding one of the following prefixes to the Unique Identifier:

-

-

-

-

-For example, let's say that you have a catalog of restaurants around the world. The catalog has a managed metadata site column named Location, which is tied to the term set named World. The term set has the following structure (the GUID for each term is shown in parentheses):

-

-

- - India (`c8a43f13-5ea1-45f2-b46d-3a1986a1cbd7`)

-

- - Mumbai (`ad491ed9-c21c-46d9-896c-c0d148957c60`)

-

- - Delhi (`c195b6e0-9062-446a-9af1-8ec1a642fede`)

-

- - France (`17587ed2-8433-45a4-9f4b-6825164fcd09`)

-

- - Paris (`01031cfe-2492-47f1-8723-45c63ef70ec9`)

-

- - Lyon (`3b2137a9-3c3a-4676-a50a-14f72ab29175`)

-

-The catalog entries and examples of queries are shown in the following tables.

-

-| Restaurant | Location |

-|Restaurant 1 |Mumbai |

-|Restaurant 2 |Mumbai |

-|Restaurant 3 |Delhi |

-|Restaurant 4 |Paris |

-|Restaurant 5 |Lyon |

-

-| Query for | Data format | Query will return |&nbsp;|

-|All restaurants in Mumbai |GP0|#ad491ed9-c21c-46d9-896c-c0d148957c60 |Restaurant 1, Restaurant 2 |

-|All restaurants in Delhi |GP0|#c195b6e0-9062-446a-9af1-8ec1a642fede |Restaurant 3 |

-|All restaurants in India |GPP|#c8a43f13-5ea1-45f2-b46d-3a1986a1cbd7 |Restaurant 1, Restaurant 2, Restaurant 3 |

-|All restaurants in the World |GTSet|#fc01ae6d-8ed3-4872-9cef-d2199d52d61c |Restaurant 1, Restaurant 2, Restaurant 3, Restaurant 4, Restaurant 5 |

-

-

-

-| Site column name | Crawled property name | Managed property name |

-|Germanäö |ows_q_TEXT_ Germanäö |GermanOWSTEXT |

-|Site_Column# |ows_q_TEXT_Site_Column# |SiteColumnOWSTEXT |

-

-> The following Unicode code blocks are considered non-supported characters: Unicode 0000-0021, Unicode 0080 - 00a1, Unicode 2000 - 2070, Unicode ff00 ff10, and Unicode ff1a ff20.

-

-

-| Site column name | Crawled property name | Managed property name |

-|Title |Title |Title |

-|Item Number |ows_q_TEXT_ProductCatalogItemNumber |ProductCatalogItemNumberOWSTEXT |

-|Group Number |ows_q_TEXT_ProductCatalogGroupNumber |ProductCatalogGroupNumberOWSTEXT |

-|Language Tag |ows_q_CHCS_ProductCatalogLanguageTag |ProductCatalogLanguageTagOWSCHCS |

-|Item Category |ows_taxId_ProductCatalogItemCategory |owstaxIdProductCatalogItemCategory |

-|Rollup Image |ows_r_IMGE_PublishingRollupImage |PublishingImage |

-|**Property name** |**Type** |**Multi-valued** |**Queryable** |**Searchable** |**Retrievable** |**Refinable** |**Sortable** |**Mapped crawled properties** |**Aliases** |

-|:--|:--|:--|:--|:--|:--|:--|:--|:--|:--|

-|AboutMe |Text |No |Yes |No |Yes |No |No |People:AboutMe, ows_Notes ||

-|Account |Text |No |Yes |No |Yes |No |No |ows_Name ||

-|AccountName |Text |No |Yes |Yes |Yes |No |No |People:AccountName ||

-|acronym |Text |No |No |No |Yes |No |No |||

-|acronymaggre |Text |No |Yes |Yes |Yes |No |No |||

-|acronymexpansion |Text |No |No |No |Yes |No |No |||

-|acronymexpansionaggre |Text |No |No |No |Yes |No |No |||

-|AnchorText |Text |No |No |Yes |No |No |No |Basic:28 ||

-|AssignedTo |Text |No |Yes |No |Yes |No |No |ows_AssignedTo, ows_Assigned_x0020_To ||

-|AttachmentDescription |Text |No |No |No |Yes |No |No |ows_MediaLinkDescription ||

-|AttachmentType |Integer |No |Yes |No |Yes |Yes |No |ows_MediaLinkType ||

-|AttachmentURI |Text |No |No |No |Yes |No |No |ows_MediaLinkURI ||

-|Author |Text |Yes |Yes |Yes |Yes |No |Yes |MetadataExtractorAuthor, Author, MailFrom, Mail:6 |DocAuthor, urn:schemas-microsoft-com:office:office#Author |

-|BaseOfficeLocation |Text |No |Yes |No |Yes |Yes |No |People:SPS-Location ||

-|BasicScope |Binary Data |No |No |No |Yes |No |No |||

-|body |Text |No |No |Yes |No |No |No |||

-|CategoryNavigationUrl |Text |No |Yes |No |No |No |No |Basic:CategoryUrlNavigation ||

-|CCAMetadata |Text |No |No |No |Yes |No |No |||

-|charset |Text |No |Yes |No |Yes |No |No |||

-|clickdistance |Integer |No |No |No |No |No |Yes |||

-|CollapsingStatus |Integer |No |No |No |Yes |No |No |||

-|Colleagues |Text |Yes |Yes |No |No |No |No |People:Colleagues ||

-|CombinedName |Text |Yes |No |Yes |Yes |No |No |People:CombinedName ||

-|CombinedUserProfileNames |Text |No |Yes |No |No |Yes |No |||

-|companies |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|contentclass |Text |No |Yes |No |Yes |Yes |No |DAV:contentclass, DAV:contentclass, DAV:contentclass |DAV:contentclass |

-|ContentModifiedTime |Date and Time |No |No |No |Yes |No |No |||

-|Contents |Text |No |No |Yes |No |No |No |ows_VideoSetDescription, ows_DocumentSetDescription, Basic:19 ||

-|ContentsHidden |Text |Yes |Yes |Yes |No |No |No |People:SPS-Location, People:Office, People:SPS-PastProjects ||

-|ContentSource |Text |No |Yes |No |Yes |No |No |||

-|ContentType |Text |No |Yes |No |Yes |Yes |No |Basic:5, ows_ContentType |MimeType, DAV:getcontenttype |

-|ContentTypeId |Text |No |Yes |No |Yes |Yes |No |ows_ContentTypeId ||

-|Created |Date and Time |No |Yes |No |Yes |Yes |Yes |Office:12, Basic:15 |DocCreatedTm, urn:schemas-microsoft-com:office:office#Created, DAV:creationdate |

-|CreatedBy |Text |No |Yes |No |Yes |No |No |ows_Created_x0020_By ||

-|Date00 |Date and Time |No |Yes |No |No |No |No |||

-|Date01 |Date and Time |No |Yes |No |No |No |No |||

-|Date02 |Date and Time |No |Yes |No |No |No |No |||

-|Date03 |Date and Time |No |Yes |No |No |No |No |||

-|Date04 |Date and Time |No |Yes |No |No |No |No |||

-|Date05 |Date and Time |No |Yes |No |No |No |No |||

-|Date06 |Date and Time |No |Yes |No |No |No |No |||

-|Date07 |Date and Time |No |Yes |No |No |No |No |||

-|Date08 |Date and Time |No |Yes |No |No |No |No |||

-|Date09 |Date and Time |No |Yes |No |No |No |No |||

-|Decimal00 |Decimal |No |Yes |No |No |No |No |||

-|Decimal01 |Decimal |No |Yes |No |No |No |No |||

-|Decimal02 |Decimal |No |Yes |No |No |No |No |||

-|Decimal03 |Decimal |No |Yes |No |No |No |No |||

-|Decimal04 |Decimal |No |Yes |No |No |No |No |||

-|Decimal05 |Decimal |No |Yes |No |No |No |No |||

-|Decimal06 |Decimal |No |Yes |No |No |No |No |||

-|Decimal07 |Decimal |No |Yes |No |No |No |No |||

-|Decimal08 |Decimal |No |Yes |No |No |No |No |||

-|Decimal09 |Decimal |No |Yes |No |No |No |No |||

-|deeplinks |Text |No |Yes |No |Yes |No |No |||

-|def |Text |No |No |No |Yes |No |No |||

-|defaggre |Text |No |Yes |Yes |Yes |No |No |||

-|DefaultEncodingURL |Text |No |No |No |Yes |No |No |ows_VideoSetDefaultEncoding, ows_EncodedAbsUrl ||

-|definitioncontent |Text |No |No |No |Yes |No |No |||

-|definitioncontentaggre |Text |No |No |No |Yes |No |No |||

-|Department |Text |No |Yes |No |Yes |Yes |No |People:Department, ows_Department |urn:schemas-microsoft-com:sharepoint:portal:profile:Department |

-|Description |Text |No |Yes |No |Yes |No |No |Description, Office:6, DESCRIPTION |urn:schemas.microsoft.com:fulltextqueryinfo:description |

-|DetectedLanguage |Text |No |Yes |No |Yes |No |No |ows_q_TEXT_TranslationLanguage ||

-|DetectedLanguageRanking |Integer |No |No |No |No |No |Yes |||

-|DiscoveredTime |Date and Time |No |No |No |Yes |No |No |||

-|DisplayAuthor |Text |Yes |Yes |No |Yes |Yes |No |||

-|DisplayDate |Date and Time |No |Yes |No |Yes |No |No |ows_ImageCreateDate, ows_Image_x0020_CreateDate |DatePictureTaken, ImageCreateDate |

-|DMSDocAccessRight |Text |No |Yes |No |Yes |No |Yes |ows_DMSDocAccessRight ||

-|DMSDocAuthor |Text |No |Yes |Yes |Yes |Yes |Yes |ows_DMSDocAuthor ||

-|DMSDocTitle |Text |No |Yes |Yes |Yes |No |Yes |ows_DMSDocTitle ||

-|DMSLeaseTerm |Text |No |No |Yes |Yes |No |No |ows_DMSLeaseTerm ||

-|docacl |Text |No |Yes |No |No |No |No |||

-|docaclmeta |Text |No |No |No |Yes |No |No |||

-|DocComments |Text |No |Yes |No |No |No |No |Description, Office:6 ||

-|DocId |Text |No |Yes |No |Yes |No |No |ows__dlc_DocId ||

-|DocKeywords |Text |No |Yes |No |No |No |No |Office:5 |urn:schemas-microsoft-com:office:office#Keywords |

-|docrank |Integer |No |No |No |Yes |No |Yes |||

-|DocSignature |Text |No |Yes |No |No |No |No |Basic:6 |urn:schemas.microsoft.com:fulltextqueryinfo:docsignature |

-|DocSubject |Text |No |Yes |No |Yes |No |No |Subject, Office:3 ||

-|DocumentSignature |Integer |Yes |Yes |No |Yes |No |Yes |||

-|DocumentSummary |Binary Data |No |No |No |Yes |No |No |||

-|DocumentSummarySize |Integer |No |No |No |Yes |No |No |||

-|docvector |Text |No |No |No |Yes |No |No |||

-|domain |Text |No |Yes |No |Yes |No |No |||

-|Double00 |Double precision float |No |Yes |No |No |No |No |||

-|Double01 |Double precision float |No |Yes |No |No |No |No |||

-|Double02 |Double precision float |No |Yes |No |No |No |No |||

-|Double03 |Double precision float |No |Yes |No |No |No |No |||

-|Double04 |Double precision float |No |Yes |No |No |No |No |||

-|Double05 |Double precision float |No |Yes |No |No |No |No |||

-|Double06 |Double precision float |No |Yes |No |No |No |No |||

-|Double07 |Double precision float |No |Yes |No |No |No |No |||

-|Double08 |Double precision float |No |Yes |No |No |No |No |||

-|Double09 |Double precision float |No |Yes |No |No |No |No |||

-|DuplicateHash |Integer |Yes |Yes |No |Yes |No |No |||

-|Duplicates |Text |No |No |No |Yes |No |No |||

-|EduAssignmentCategory |Text |No |Yes |No |Yes |No |No |ows_EduAssignmentCategory ||

-|EduAssignmentFormat |Text |No |Yes |No |Yes |No |No |ows_EduAssignmentFormat ||

-|EduEntityId |Text |No |No |No |Yes |No |No |ows_EduEntityId ||

-|EduMaximumScore |Text |No |Yes |No |Yes |No |No |ows_EduMaximumScore ||

-|EndDate |Date and Time |No |Yes |No |Yes |No |No |ows_End_x0020_Date ||

-|EventRate |Double precision float |No |No |No |No |No |Yes |||

-|ExcludeFromSummary |Text |No |No |No |Yes |No |No |EmbeddedContent, LINK.OFFICECHILD, Description ||

-|ExpirationTime |Date and Time |No |Yes |No |No |No |Yes |ows_Announcement_x0020_Expires, ows_Expires ||

-|ExternalMediaURL |Text |No |No |No |Yes |No |No |ows_VideoSetExternalLink ||

-|ExtractedAuthor |Text |No |Yes |No |Yes |No |No |||

-|ExtractedDate |Date and Time |No |Yes |No |Yes |No |No |||

-|fcocount |Integer |No |No |No |Yes |No |No |||

-|FileExtension |Text |No |Yes |No |Yes |Yes |Yes |FileExtension, ows_File_x0020_Type, ows_FileType ||

-|Filename |Text |No |Yes |Yes |Yes |No |Yes |Basic:10 |DAV:displayname |

-|FileType |Text |No |Yes |No |Yes |Yes |No |FileType ||

-|FirstLevelColleagues |Text |Yes |Yes |No |Yes |No |No |||

-|FirstLevelMutualFollowings |Text |Yes |Yes |No |Yes |No |No |||

-|FirstName |Text |Yes |Yes |No |Yes |No |Yes |People:FirstName, People:SPS-PhoneticFirstName ||

-|FollowAllAnchor |Text |No |Yes |No |No |No |No |Basic:31 ||

-|format |Text |No |Yes |No |Yes |Yes |No |||

-|FullPostBody |Text |No |No |No |Yes |No |No |ows_SearchContent ||

-|FullPostTitle |Text |No |No |No |Yes |No |No |ows_SearchTitle ||

-|GeneratedTitle |Text |No |Yes |Yes |Yes |No |No |||

-|Genre |Text |No |Yes |No |Yes |No |No |||

-|HierarchyUrl |Text |No |Yes |No |Yes |No |No |People:ProfileHierarchyViewUrl ||

-|HitHighlightedProperties |Text |No |Yes |No |Yes |No |No |||

-|HitHighlightedSummary |Text |No |Yes |No |Yes |No |No |||

-|HostingPartition |Text |No |Yes |No |No |Yes |No |||

-|hwboost |Integer |No |Yes |No |No |No |Yes |||

-|ImageDateCreated |Date and Time |No |Yes |No |Yes |No |No |ows_ImageCreateDate, ows_Image_x0020_CreateDate ||

-|importance |Integer |No |Yes |No |Yes |No |Yes |||

-|Int00 |Integer |No |Yes |No |No |No |No |||

-|Int01 |Integer |No |Yes |No |No |No |No |||

-|Int02 |Integer |No |Yes |No |No |No |No |||

-|Int03 |Integer |No |Yes |No |No |No |No |||

-|Int04 |Integer |No |Yes |No |No |No |No |||

-|Int05 |Integer |No |Yes |No |No |No |No |||

-|Int06 |Integer |No |Yes |No |No |No |No |||

-|Int07 |Integer |No |Yes |No |No |No |No |||

-|Int08 |Integer |No |Yes |No |No |No |No |||

-|Int09 |Integer |No |Yes |No |No |No |No |||

-|Int10 |Integer |No |Yes |No |No |No |No |||

-|Int11 |Integer |No |Yes |No |No |No |No |||

-|Int12 |Integer |No |Yes |No |No |No |No |||

-|Int13 |Integer |No |Yes |No |No |No |No |||

-|Int14 |Integer |No |Yes |No |No |No |No |||

-|Int15 |Integer |No |Yes |No |No |No |No |||

-|Int16 |Integer |No |Yes |No |No |No |No |||

-|Int17 |Integer |No |Yes |No |No |No |No |||

-|Int18 |Integer |No |Yes |No |No |No |No |||

-|Int19 |Integer |No |Yes |No |No |No |No |||

-|Int20 |Integer |No |Yes |No |No |No |No |||

-|Int21 |Integer |No |Yes |No |No |No |No |||

-|Int22 |Integer |No |Yes |No |No |No |No |||

-|Int23 |Integer |No |Yes |No |No |No |No |||

-|Int24 |Integer |No |Yes |No |No |No |No |||

-|Int25 |Integer |No |Yes |No |No |No |No |||

-|Int26 |Integer |No |Yes |No |No |No |No |||

-|Int27 |Integer |No |Yes |No |No |No |No |||

-|Int28 |Integer |No |Yes |No |No |No |No |||

-|Int29 |Integer |No |Yes |No |No |No |No |||

-|Int30 |Integer |No |Yes |No |No |No |No |||

-|Int31 |Integer |No |Yes |No |No |No |No |||

-|Int32 |Integer |No |Yes |No |No |No |No |||

-|Int33 |Integer |No |Yes |No |No |No |No |||

-|Int34 |Integer |No |Yes |No |No |No |No |||

-|Int35 |Integer |No |Yes |No |No |No |No |||

-|Int36 |Integer |No |Yes |No |No |No |No |||

-|Int37 |Integer |No |Yes |No |No |No |No |||

-|Int38 |Integer |No |Yes |No |No |No |No |||

-|Int39 |Integer |No |Yes |No |No |No |No |||

-|Int40 |Integer |No |Yes |No |No |No |No |||

-|Int41 |Integer |No |Yes |No |No |No |No |||

-|Int42 |Integer |No |Yes |No |No |No |No |||

-|Int43 |Integer |No |Yes |No |No |No |No |||

-|Int44 |Integer |No |Yes |No |No |No |No |||

-|Int45 |Integer |No |Yes |No |No |No |No |||

-|Int46 |Integer |No |Yes |No |No |No |No |||

-|Int47 |Integer |No |Yes |No |No |No |No |||

-|Int48 |Integer |No |Yes |No |No |No |No |||

-|Int49 |Integer |No |Yes |No |No |No |No |||

-|Interests |Text |Yes |Yes |No |Yes |No |No |People:SPS-Interests ||

-|InternalFileType |Integer |No |No |No |Yes |No |Yes |||

-|IsContainer |Yes/No |No |Yes |No |Yes |No |No |Basic:7 ||

-|IsData |Yes/No |No |Yes |Yes |Yes |No |No |ows_IsData, IsData ||

-|IsDefaultView |Yes/No |No |No |No |Yes |No |No |ows_IsDefaultView ||

-|IsDocument |Yes/No |No |Yes |No |Yes |No |No |SharePoint:isdocument, SharePoint:isdocument, Basic:22 |urn:schemas.microsoft.com:sharepoint:portal:isdocument |

-|IsEmptyList |Yes/No |No |No |No |Yes |No |No |ows_IsEmptyList ||

-|IsListItem |Yes/No |No |No |No |Yes |No |No |ows_isItem ||

-|IsMyDocuments |Yes/No |No |Yes |No |Yes |No |No |ows_IsMyDocuments ||

-|IsPublishingCatalog |Text |No |Yes |No |Yes |No |No |IsPublishingCatalog ||

-|IsReport |Yes/No |No |Yes |Yes |Yes |No |No |ows_IsReport, IsReport ||

-|ItemCategoryText |Text |No |No |Yes |No |No |No |ProductCatalogItemCategory ||

-|JobTitle |Text |No |Yes |Yes |Yes |Yes |No |People:SPS-JobTitle, People:Title, ows_JobTitle |urn:schemas-microsoft-com:sharepoint:portal:profile:Title |

-|Keywords |Text |No |Yes |No |Yes |No |No |ows_Keywords ||

-|language |Text |No |Yes |No |Yes |No |No |ows_ProductCatalogLanguageTag ||

-|languages |Text |Yes |Yes |No |Yes |Yes |No |||

-|LastAnalyticsUpdateTime |Integer |No |No |No |Yes |No |No |||

-|LastModifiedTime |Date and Time |No |Yes |No |Yes |Yes |Yes |LastSavedDateTime, Basic:14, Basic:16 |Write, FileWrite, DAV:getlastmodified |

-|LastName |Text |No |Yes |No |Yes |No |No |People:LastName, People:SPS-PhoneticLastName ||

-|LevelsToTop |Integer |No |No |No |Yes |No |Yes |People:LevelsToTop ||

-|LikesCount |Integer |No |No |No |Yes |No |No |ows_LikesCount ||

-|ListID |Text |No |Yes |No |Yes |No |No |ows_ListID ||

-|ListItemID |Text |No |Yes |No |Yes |No |No |ows_ListItemID ||

-|ListUrl |Text |No |Yes |No |Yes |No |No |ListUrl ||

-|Location |Text |No |Yes |No |Yes |Yes |No |ows_Location ||

-|ManagedProperties |Text |Yes |Yes |No |No |Yes |No |||

-|MediaDuration |Integer |No |Yes |No |Yes |Yes |No |ows_MediaLengthInSeconds ||

-|Memberships |Text |Yes |Yes |Yes |Yes |No |No |People:QuickLinks ||

-|MetadataAuthor |Text |No |Yes |No |Yes |No |No |Author, MailFrom, Mail:6 ||

-|MicroBlogType |Integer |No |Yes |No |Yes |No |No |ows_MicroBlogType ||

-|MobilePhone |Text |No |Yes |No |Yes |No |No |People:CellPhone, ows_CellPhone, ows_Cell_x0020_Phone ||

-|ModifiedBy |Text |No |Yes |No |Yes |No |Yes |ows_ModifiedBy, ows_Modified_x0020_By, LastModifiedBy ||

-|NLCodePage |Integer |No |Yes |No |No |No |No |Web:4 ||

-|Notes |Text |No |Yes |No |Yes |No |No |ows_Note, ows_Notes ||

-|NumItemsInCollection |Integer |No |No |No |Yes |No |No |||

-|OfficeNumber |Text |No |Yes |No |Yes |No |No |People:Office ||

-|OrgNames |Text |Yes |Yes |No |Yes |No |No |People:OrganizationNames, ows_Company |Company |

-|OrgParentNames |Text |Yes |Yes |No |Yes |No |No |People:OrganizationParentNames ||

-|OrgParentUrls |Text |Yes |Yes |No |Yes |No |No |People:OrganizationParentURLs ||

-|OrgUrls |Text |Yes |Yes |No |Yes |No |No |People:OrganizationURLs ||

-|OriginalPath |Text |No |No |No |Yes |No |No |Basic:11, Basic:9, Web:2 ||

-|OWS_ItemURL |Text |No |No |No |Yes |No |No |||

-|OWS_URL |Text |No |Yes |No |No |No |No |ows_URL ||

-|owsmetadatafacetinfo |Text |No |Yes |No |Yes |Yes |No |ows_MetadataFacetInfo ||

-|owstaxidmetadataalltagsinfo |Text |Yes |Yes |No |Yes |Yes |No |ows_taxId_MetadataAllTagsInfo ||

-|owstaxIdProductCatalogItemCategory |Text |Yes |Yes |Yes |Yes |Yes |No |ows_taxId_ProductCatalogItemCategory ||

-|ParentLink |Text |No |Yes |No |Yes |No |No |ows_ParentURL ||

-|PastProjects |Text |Yes |Yes |No |Yes |No |No |People:SPS-PastProjects ||

-|Path |Text |No |Yes |No |Yes |No |No |Basic:11, Basic:9, Web:2 |DAV:href, VPath, DocAddress, ... |

-|People |Text |Yes |Yes |No |Yes |Yes |No |ows_People, Author, MailFrom ||

-|PeopleInMedia |Text |Yes |Yes |No |Yes |Yes |No |ows_PeopleInMedia ||

-|PeopleKeywords |Text |Yes |Yes |No |Yes |Yes |No |People:SPS-Responsibility, People:SPS-Skills, People:SPS-Interests ||

-|PhoneNumber |Text |Yes |Yes |No |Yes |No |No |||

-|PictureHeight |Integer |No |Yes |No |Yes |No |No |ows_ImageHeight, ows_VideoHeightInPixels |ImageHeight, urn:schemas-microsoft-com:office:office#ows_ImageHeight |

-|PictureThumbnailURL |Text |No |Yes |No |Yes |No |No |ows_AlternateThumbnailUrl, ows_EncodedAbsThumbnailUrl, ows_DMSCoverImage ||

-|PictureURL |Text |No |Yes |No |Yes |No |No |ows_PictureURL, People:PictureURL |urn:schemas.microsoft.com:fulltextqueryinfo:PictureURL |

-|PictureWidth |Integer |No |Yes |No |Yes |No |No |ows_ImageWidth, ows_VideoWidthInPixels |ImageWidth, urn:schemas-microsoft-com:office:office#ows_ImageWidth |

-|PopularSocialTags |Text |Yes |No |No |Yes |No |No |||

-|PostAuthor |Text |No |Yes |No |Yes |Yes |No |ows_PostAuthor ||

-|PreferredName |Text |No |Yes |Yes |Yes |No |No |People:PreferredName |urn:schemas-microsoft-com:sharepoint:portal:profile:PreferredName |

-|Priority |Text |No |Yes |No |Yes |No |No |ows_Priority ||

-|PrivateColleagues |Text |Yes |Yes |No |No |No |No |People:ColleaguesNonPublic ||

-|processingtime |Date and Time |No |Yes |No |Yes |No |Yes |||

-|ProductCatalogGroupNumberOWSTEXT |Text |No |Yes |No |Yes |No |Yes |ows_ProductCatalogGroupNumber ||

-|ProfileExpertise |Text |No |Yes |No |No |No |No |People:SPS-Responsibility, People:SPS-PastProjects, People:SPS-Skills ||

-|ProfileName |Text |No |Yes |No |No |No |No |People:PreferredName, People:FirstName, People:LastName ||

-|Pronunciations |Text |No |Yes |Yes |Yes |No |No |People:FirstName, People:LastName, People:PreferredName ||

-|PublishingCatalogSettings |Text |No |No |No |Yes |No |No |PublishingCatalogSettings ||

-|PublishingImage |Text |No |No |No |Yes |No |No |||

-|Purpose |Text |No |Yes |No |No |No |No |ows_Purpose ||

-|QueryTerms |Text |Yes |No |No |Yes |No |No |||

-|Rank |Integer |No |No |No |Yes |No |No |urn:schemas.microsoft.com:fulltextqueryinfo:rank ||

-|RankDetail |Text |No |Yes |No |Yes |No |No |||

-|RankingWeightHigh |Text |Yes |Yes |Yes |No |No |No |People:OrganizationNames, People:Department ||

-|RankingWeightLow |Text |Yes |Yes |Yes |No |No |No |People:SPS-Skills, People:SPS-Interests ||

-|RankingWeightName |Text |Yes |Yes |Yes |No |No |No |People:CombinedName, People:UserName, People:WorkEmail ||

-|Rating |Double precision float |No |No |No |Yes |No |No |||

-|recommendedfor |Text |Yes |Yes |No |No |Yes |Yes |||

-|RecsClickedLifeTime |Integer |No |No |No |Yes |No |Yes |||

-|RecsClickedRecent |Integer |No |No |No |Yes |No |Yes |||

-|RefinableDate00 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate01 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate02 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate03 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate04 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate05 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate06 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate07 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate08 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate09 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate10 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate11 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate12 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate13 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate14 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate15 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate16 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate17 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate18 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDate19 |Date and Time |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal00 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal01 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal02 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal03 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal04 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal05 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal06 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal07 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal08 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDecimal09 |Decimal |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble00 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble01 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble02 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble03 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble04 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble05 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble06 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble07 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble08 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableDouble09 |Double precision float |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt00 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt01 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt02 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt03 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt04 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt05 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt06 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt07 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt08 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt09 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt10 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt11 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt12 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt13 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt14 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt15 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt16 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt17 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt18 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt19 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt20 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt21 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt22 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt23 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt24 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt25 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt26 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt27 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt28 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt29 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt30 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt31 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt32 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt33 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt34 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt35 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt36 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt37 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt38 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt39 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt40 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt41 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt42 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt43 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt44 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt45 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt46 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt47 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt48 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableInt49 |Integer |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString00 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString01 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString02 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString03 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString04 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString05 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString06 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString07 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString08 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString09 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString10 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString11 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString12 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString13 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString14 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString15 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString16 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString17 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString18 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString19 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString20 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString21 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString22 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString23 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString24 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString25 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString26 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString27 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString28 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString29 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString30 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString31 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString32 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString33 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString34 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString35 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString36 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString37 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString38 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString39 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString40 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString41 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString42 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString43 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString44 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString45 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString46 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString47 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString48 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString49 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString50 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString51 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString52 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString53 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString54 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString55 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString56 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString57 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString58 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString59 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString60 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString61 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString62 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString63 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString64 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString65 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString66 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString67 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString68 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString69 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString70 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString71 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString72 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString73 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString74 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString75 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString76 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString77 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString78 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString79 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString80 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString81 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString82 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString83 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString84 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString85 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString86 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString87 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString88 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString89 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString90 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString91 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString92 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString93 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString94 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString95 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString96 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString97 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString98 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|RefinableString99 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|ReplyCount |Integer |No |No |No |Yes |No |No |ows_ReplyCount ||

-|Responsibilities |Text |Yes |Yes |Yes |Yes |Yes |No |People:SPS-Responsibility |Responsibility |

-|RobotsNoIndex |Yes/No |No |Yes |No |No |No |No |ows_RobotsNoIndex ||

-|RootPostID |Text |No |Yes |No |Yes |No |No |ows_RootPostID ||

-|RootPostOwnerID |Text |No |Yes |No |Yes |No |No |ows_RootPostOwnerID ||

-|RootPostUniqueID |Text |No |Yes |No |Yes |No |No |ows_RootPostUniqueID ||

-|Schools |Text |Yes |Yes |No |Yes |No |No |People:SPS-School ||

-|SecondaryFileExtension |Text |No |Yes |No |Yes |No |No |ows_FileType, ows_File_x0020_Type ||

-|SecondLevelColleagues |Text |Yes |Yes |No |Yes |No |No |||

-|SectionIndexes |Text |Yes |No |No |Yes |No |No |||

-|SectionNames |Text |Yes |No |No |Yes |No |No |||

-|ServerRedirectedEmbedURL |Text |No |No |No |Yes |No |No |ows_ServerRedirectedEmbedUrl ||

-|ServerRedirectedPreviewURL |Text |No |No |No |Yes |No |No |ows_ServerRedirectedPreviewUrl ||

-|ServerRedirectedURL |Text |No |Yes |No |Yes |No |No |ows_ServerRedirectedUrl ||

-|ServiceApplicationID |Text |No |Yes |No |Yes |No |No |||

-|SharedWithInternal |Text |Yes |Yes |No |Yes |Yes |No |ows_SharedWithInternal ||

-|SipAddress |Text |No |Yes |Yes |Yes |No |No |People:SPS-SipAddress ||

-|Site |Text |No |Yes |No |Yes |Yes |No |urn:schemas.microsoft.com:fulltextqueryinfo:sitename ||

-|SiteClosed |Yes/No |No |Yes |No |No |No |No |||

-|SiteDescription |Text |No |No |No |Yes |No |No |ows_SiteDescription ||

-|SiteID |Text |No |Yes |No |Yes |No |No |ows_SiteID ||

-|SiteLogo |Text |No |No |No |Yes |No |No |LogoURL ||

-|SitemapChangeFrequency |Integer |No |No |No |Yes |No |No |||

-|SitemapPriority |Double precision float |No |No |No |Yes |No |No |||

-|SiteMembers |Text |Yes |No |No |Yes |No |No |||

-|sitename |Text |No |Yes |No |Yes |Yes |No |||

-|SiteOwners |Text |Yes |No |No |Yes |No |No |||

-|siterank |Integer |No |No |No |No |No |Yes |||

-|SiteTitle |Text |No |Yes |No |Yes |No |No |ows_SiteName |urn:schemas-microsoft-com:office:office#ows_SiteName |

-|Size |Integer |No |Yes |No |Yes |Yes |Yes |Basic:12, ows_ImageSize |DAV:getcontentlength, PictureSize, ImageSize |

-|Skills |Text |Yes |Yes |No |Yes |No |No |People:SPS-Skills ||

-|SocialTag |Text |No |Yes |Yes |Yes |No |No |||

-|SocialTagTextUrl |Text |Yes |Yes |No |No |No |No |People:SocialTagTextUrl ||

-|SPContentType |Text |No |Yes |No |No |Yes |No |ows_ContentType ||

-|SpellingTerms |Text |No |No |Yes |No |No |No |||

-|SPSiteURL |Text |No |Yes |No |Yes |No |Yes |ows_SPSiteURL ||

-|SPVersion |Integer |No |No |No |Yes |No |No |ows_SPVersion ||

-|StartDate |Date and Time |No |Yes |No |Yes |No |No |ows_Start_x0020_date, ows_DMSReleaseDate ||

-|Status |Text |No |Yes |No |Yes |No |No |ows_Issue_x0020_Status, ows_Task_x0020_Status ||

-|Tags |Text |Yes |Yes |No |Yes |Yes |No |ows_SearchTag1, ows_SearchTag2, ows_SearchTag3 ||

-|teaser |Text |No |No |No |Yes |No |No |||

-|Text1 |Text |No |No |Yes |No |No |No |||

-|Text2 |Text |No |No |Yes |No |No |No |||

-|Text3 |Text |No |No |Yes |No |No |No |||

-|Title |Text |No |Yes |Yes |Yes |No |No |MetadataExtractorTitle, Office:2, ows_BaseName, Title |DocTitle, urn:schemas.microsoft.com:fulltextqueryinfo:displaytitle |

-|tld |Text |No |Yes |No |Yes |No |No |||

-|UniqueID |Text |No |No |No |Yes |No |No |ows_UniqueID ||

-|url |Text |No |No |No |Yes |No |No |ows_DMSDocAuthorURL ||

-|UrlDepth |Integer |No |Yes |No |Yes |Yes |Yes |||

-|urlkeywords |Text |No |Yes |Yes |No |No |No |||

-|urls |Text |Yes |Yes |No |Yes |No |No |||

-|UsageAnalyticsId |Text |No |Yes |No |Yes |No |No |ows_ProductCatalogItemNumber ||

-|UsageEvent10LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent10Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent11LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent11Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent12LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent12Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent1LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent1Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent2LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent2Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent3LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent3Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent4LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent4Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent5LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent5Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent6LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent6Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent7LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent7Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent8LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent8Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent9LifeTime |Integer |No |No |No |Yes |No |Yes |||

-|UsageEvent9Recent |Integer |No |No |No |Yes |No |Yes |||

-|UsageEventItemId |Text |No |Yes |No |Yes |Yes |No |ows_ProductCatalogItemNumber ||

-|UserEncodingURL |Text |No |No |No |Yes |No |No |ows_VideoSetUserOverrideEncoding ||

-|UserName |Text |No |Yes |Yes |Yes |No |No |People:UserName, ows_FullName, ows_Full_x0020_Name ||

-|UserProfile_GUID |Text |No |Yes |No |Yes |No |No |People:UserProfile_GUID ||

-|ViewsLast1Days |Integer |No |No |No |Yes |No |No |||

-|ViewsLast1DaysUniqueUsers |Integer |No |No |No |Yes |No |No |||

-|ViewsLast2Days |Integer |No |No |No |Yes |No |No |||

-|ViewsLast2DaysUniqueUsers |Integer |No |No |No |Yes |No |No |||

-|ViewsLast3Days |Integer |No |No |No |Yes |No |No |||

-|ViewsLast3DaysUniqueUsers |Integer |No |No |No |Yes |No |No |||

-|ViewsLast4Days |Integer |No |No |No |Yes |No |No |||

-|ViewsLast4DaysUniqueUsers |Integer |No |No |No |Yes |No |No |||

-|ViewsLast5Days |Integer |No |No |No |Yes |No |No |||

-|ViewsLast5DaysUniqueUsers |Integer |No |No |No |Yes |No |No |||

-|ViewsLast6Days |Integer |No |No |No |Yes |No |No |||

-|ViewsLast6DaysUniqueUsers |Integer |No |No |No |Yes |No |No |||

-|ViewsLast7Days |Integer |No |No |No |Yes |No |No |||

-|ViewsLast7DaysUniqueUsers |Integer |No |No |No |Yes |No |No |||

-|ViewsLastMonths1 |Integer |No |No |No |Yes |No |No |||

-|ViewsLastMonths1Unique |Integer |No |No |No |Yes |No |No |||

-|ViewsLastMonths2 |Integer |No |No |No |Yes |No |No |||

-|ViewsLastMonths2Unique |Integer |No |No |No |Yes |No |No |||

-|ViewsLastMonths3 |Integer |No |No |No |Yes |No |No |||

-|ViewsLastMonths3Unique |Integer |No |No |No |Yes |No |No |||

-|ViewsLifeTime |Integer |No |No |No |Yes |No |Yes |||

-|ViewsLifeTimeUniqueUsers |Integer |No |No |No |Yes |No |Yes |||

-|ViewsRecent |Integer |No |No |No |Yes |No |Yes |||

-|ViewsRecentUniqueUsers |Integer |No |No |No |Yes |No |Yes |||

-|WebId |Text |No |Yes |No |Yes |No |No |ows_WebId ||

-|WebTemplate |Text |No |Yes |No |No |Yes |No |WebTemplate ||

-|WeightedMemberships |Text |Yes |No |No |Yes |No |No |People:WeightedMemberships ||

-|WikiCategory |Text |No |Yes |No |Yes |No |No |ows_Wiki_x0020_Page_x0020_Categories ||

-|WordCustomRefiner1 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordCustomRefiner2 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordCustomRefiner3 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordCustomRefiner4 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordCustomRefiner5 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordExactCustomRefiner |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordPartCustomRefiner1 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordPartCustomRefiner2 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordPartCustomRefiner3 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordPartCustomRefiner4 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordPartCustomRefiner5 |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WordPartExactCustomRefiner |Text |Yes |Yes |No |Yes |Yes |Yes |||

-|WorkEmail |Text |No |Yes |Yes |Yes |No |No |People:WorkEmail, ows_EMail, ows_EMail_x0020_ |urn:schemas-microsoft-com:sharepoint:portal:profile:WorkEmail |

-|WorkId |Integer |No |No |No |Yes |No |No |||

-|WorkPhone |Text |No |Yes |No |Yes |No |No |People:WorkPhone, ows_WorkPhone, ows_Work_x0020_Phone |urn:schemas-microsoft-com:sharepoint:portal:profile:WorkPhone |

-|YomiDisplayName |Text |No |Yes |No |Yes |No |No |People:SPS-PhoneticDisplayName ||