Updates from: 04/28/2023 01:30:24
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Change User Storage https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/change-user-storage.md
As a global or SharePoint admin in Microsoft 365, you can set the OneDrive stora
When you need cloud storage for individual users beyond the initial 5 TB, additional cloud storage will be granted as follows: -- When a user has filled their 5 TB of OneDrive storage to at least 90% capacity, Microsoft will increase your default storage space in OneDrive to up to 25 TB per user (admins may set a lower per-user limit if they want to).
+- When a user has filled their 5 TB of OneDrive storage to at least 90% capacity, Microsoft will increase your default storage space in OneDrive to up to 25 TB per user (admins may set a lower per-user limit if they want to). The storage limit will be reset to 5 TB if OneDrive storage utilization drops below 90% of the 5 TB capacity.
- For any user that reaches at least 90% capacity of their 25 TB of OneDrive storage, additional cloud storage will be provided as 25 TB SharePoint team sites to individual users. For more information and assistance, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=869559).
SharePoint Delve For Office 365 Admins https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/delve-for-office-365-admins.md
Last updated 07/11/2018
Title: "Delve for admins" -+ recommendations: true audience: Admin
SharePoint Manage Loop Components https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/manage-loop-components.md
Just like other Microsoft 365 experiences, Loop also leverages core services acr
#### Microsoft 365 Groups for Cloud Policy
-You must create or use an existing Microsoft 365 group that defines which users in your organization this policy will apply to. You can learn how to create a Microsoft 365 group by visiting [Create a Microsoft 365 group](/microsoft-365/admin/create-groups/create-groups).
+This section is not required if you choose to apply the Loop settings to all the users in your tenant; however, if you want to scope, you must create or use an existing Microsoft 365 group that defines which users in your organization this policy will apply to. You can learn how to create a Microsoft 365 group by visiting [Create a Microsoft 365 group](/microsoft-365/admin/create-groups/create-groups).
-You'll need this group for the Cloud Policy setup procedure below.
+You'll be able to use this group for the Cloud Policy setup procedure below.
If you prefer, you can also create other types of groups to use with Cloud Policy. See [learn more about creating groups in the Microsoft 365 admin center](/microsoft-365/admin/email/create-edit-or-delete-a-security-group) or [learn more about creating dynamic groups in AzureAD](/azure/active-directory/external-identities/use-dynamic-groups).
To configure these Cloud Policy settings:
2. Select **Customization** from the left pane. 3. Select **Policy Management**. 4. Create a new policy configuration or edit an existing one.
-5. In **Choose the scope**, choose the group for which you want to apply the policy. See [Microsoft 365 Groups for Cloud Policy](#microsoft-365-groups-for-cloud-policy) for more information. If you do not apply to a group, your settings will not take effect in your tenant.
+5. In **Choose the scope**, choose either the "all users" option or select the group for which you want to apply the policy. See [Microsoft 365 Groups for Cloud Policy](#microsoft-365-groups-for-cloud-policy) for more information.
6. In **Configure Settings**, choose one of the settings listed at the top of this section. 7. In configuration setting, choose one of the following: - For **Create and view Loop files in Microsoft apps that support Loop**
SharePoint Onedrive In Citrix Virtual Apps Deployment Guide https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/onedrive-in-citrix-virtual-apps-deployment-guide.md
+ Last updated : 04/27/2023
+ Title: Set up OneDrive in Citrix Virtual Apps
++++
+audience: Admin
+f1.keywords:
+- NOCSH
++
+ms.localizationpriority: medium
+
+- Adm_O365
+search.appverid:
+- MET150
+- BCS160
+
+- Strat_OD_admin
+- M365-collaboration
+description: In this article, you'll learn how to enable OneDrive in Citrix Virtual Apps.
++
+# Set up OneDrive in Citrix Virtual Apps
+
+This article describes how to enable and use OneDrive in Citrix Virtual Apps.
+
+## Prerequisites:
+
+To enable OneDrive in Citrix Virtual Apps, you must have the following versions of Windows and Citrix Virtual Apps and Desktops (CVAD):
+
+**Windows**:
+
+- Windows 11: KB5014019
+- Windows Server 2022: KB5014021
+- Windows 10: KB5014023
+- Windows Server 2019: KB5014022
+
+**Citrix**:
+
+- CVAD 7 2203 LTSR CU1 or later.
+- VDA 2212 enables Shellbridge by default, all earlier versions require Shellbridge to be enabled manually.
+- To enable this feature, On 2203 LTSR TS VDA (2019 Server, 2022 Server, Windows 10 RDSH or Windows 11 RDSH) add the following registry details:
+
+ `HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Citrix Virtual Desktop Agent`<p>
+ `Name: Shellbridge`<p>
+ `Type: REG_DWORD`<p>
+ `Value: 1`
+
+To ensure that the feature is correctly enabled, open a command window (cmd.exe) and run `start ms-settings:printers`. If the feature is enabled, the printer setting window is displayed.
+
+**We recommend adding OneDrive.exe to `LogoffCheckSysModules`**.
+
+ `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI` <p>
+ `Value Name:LogoffCheckSysModules` <p>
+ `Type:REG_SZ` <p>
+ `String:OneDrive.exe, Microsoft.Sharepoint.exe` <p>
+
+> [!IMPORTANT]
+> [FSLogix](/fslogix/how-to-install-fslogix) must be used in conjunction with Citrix Virtual Apps for OneDrive to be supported.
+
+## How to setup OneDrive
+
+1. Install OneDrive Sync app per machine. See [Install the sync app per-machine](per-machine-installation.md).
+1. Install the latest version of FSLogix. See [Install FSLogix Applications](/fslogix/how-to-install-fslogix).
+
+ > [!NOTE]
+ > All non-persistent VDI environments require the latest version of FSLogix. Ensure you install the latest version. See [OneDrive sync error FSLogix_unsupported_environment on VMs](/sharepoint/troubleshoot/sync/fslogix-unsupported-environment-sync-error-vm).
+
+1. Add OneDrive to `HKLM\Software\Microsoft\Windows\CurrentVersion\` by using the following command:
+
+ `REG ADD HKLM\Software\Microsoft\Windows\CurrentVersion\Run /v OneDrive /t REG_SZ /d "\"C:\Program Files\Microsoft OneDrive\OneDrive.exe\" /background"`
+
+1. Silently configure user accounts. See [Silently configure user accounts](use-silent-account-configuration.md).
+
+ > [!NOTE]
+ > Silent sign-in should work if your machine is connected to Azure Active Directory. Make sure to turn off this setting if your computer is not Azure AD-joined.
SharePoint Sites Usage Guidelines https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/sites-usage-guidelines.md
Last updated 05/13/2019
Title: Create guidelines for site usage description: Checklist to help guide users to create their SharePoint site usage guidance.-+ audience: admin recommendations: true
SharePoint Viva Amplify https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/viva-amplify.md
Once you create a campaign, you can create the content on the **Main canvas** sc
To create a campaign, perform the following steps: 1. Go to the Microsoft Viva Amplify portal.
-2. Provide your credentials and sign in to the Microsoft Viva Amplify portal.
+2. Provide your credentials and sign in.
3. Select **+ Create a campaign**. The **Create a new campaign** screen is displayed. 4. Select **Create a campaign** on the bottom-left corner of the screen. 5. Enter the details for the text boxes and select **Next**. 6. From the **Add members to your campaign** text box, choose the person whom you want to add as a member of your campaign. 7. Select **Add to list**.
- The chosen person is added as a member of your campaign.
+ The chosen person is successfully added as a member of your campaign.
8. Select **Create a campaign**.
- The campaign is successfully created and is listed on the **Amplify Hub** screen.
+ The campaign is successfully created and listed on the **Amplify Hub** screen.
-Once you create content using the created campaign and transpile it to the distribution channels, you'll know and view the formatting changes that occur.
+You can create content using the created campaign and then transpile it to the distribution channels. Only after you transpile the content, you can view the formatting changes that occur.
> [!NOTE] > Formatting changes are applicable only to the **Outlook** distribution channel and not to the **SharePoint** distribution channel because the **Main canvas** screen itself is a type of SharePoint site. For more information, see [Formatting changes](#formatting-changes) and [Formatting changes in Outlook distribution channel](#formatting-changes-in-outlook-distribution-channel).
For example, when you click the "preview" icon under the **Outlook** distributio
**[Some properties like text on images, columns, and medium and large people web parts may have been changed for this distribution channel.](#formatting-changes)**
-When you click the link of the message **Learn more about formatting changes and editing**, you're taken to the screen that displays information about [formatting changes](#formatting-changes).
+When you click **Learn more about formatting changes and editing**, you're taken to the screen that displays information about [formatting changes](#formatting-changes).
## Formatting changes Formatting changes can be classified as:
-1. **Modifications to certain web parts**: When you use **Outlook** distribution channel, and then select certain web parts, there may be changes in the properties of the web parts. Such changes result in the web parts displaying a behavior different from its default behavior.
+1. **Modifications to certain web parts**: When you use **Outlook** distribution channel, and then select certain web parts, there may be changes in the properties of the web parts. Such changes result in the web parts displaying a behavior different from its default behavior.
- For example:
+For example, in the **Sections** layout, when you organize content into two or three columns, the same content gets stacked into a single column when being published.
- - In the **Sections** layout, when you organize content into two or three columns, the same content gets stacked into a single column when being published.
- - In the **Image** web part, properties such as "text on image" won't be supported.
-
-1. **Removal of certain web parts**: When you use **Outlook** distribution channel, certain web parts such as the spacer, the large people, and the countdown timer don't appear as they're removed automatically on account of incompatibility with Outlook.
+1. **Removal of certain web parts**: When you use **Outlook** distribution channel, certain web parts such as the spacer, the large people, and the countdown timer don't appear as they're removed automatically on account of their incompatibility with Outlook.
For detailed information about such other formatting changes in web parts for the **Outlook** distribution channel, see [Formatting changes in Outlook distribution channel](#formatting-changes-in-outlook-distribution-channel).
For detailed information about such other formatting changes in web parts for th
For the **Outlook** distribution channel, there are: - [Formatting changes in Image web part](#formatting-changes-in-image-web-part)-- [Formatting changes in Text web part](#formatting-changes-in-text-web-part) - [Formatting changes in People web part](#formatting-changes-in-people-web-part) - [Formatting changes in Section layout](#formatting-changes-in-sections-layout) #### Formatting changes in Image web part
-1. Text on the image isn't supported (Text will be dropped.).
-
- :::image type="content" source="media/text-image-not-supported.png" alt-text="The text on the image not being supported in Outlook.":::
-
-1. Image Hyperlink isn't supported. Transpiled images aren't clickable to link.
-
- :::image type="content" source="media/image-hyperlink-not-supported.png" alt-text="The image hyperlink not being supported in Outlook.":::
-
-#### Formatting changes in Text web part
-
-1. Theme colors for table aren't supported (Table style is changed to **default**.).
-
- :::image type="content" source="media/theme-colors-not-supported.png" alt-text="The screen depicting the formatting change of theme color not being supported":::
-
-1. Table Alignment isn't supported. Tables can only be left aligned.
+Text on the image is now transpiled to appear on top of the image on Outlook endpoint.
- :::image type="content" source="media/table-alignment-not-supported.png" alt-text="The table alignment not being supported in Outlook.":::
#### Formatting changes in People web part The **Small**, **Medium**, and **Large** layouts are supported. However, even if you transpile the content using the **Medium** and **Large** layouts, the descriptions and links added in these two layouts will be dropped. The content's output defaults to the **Small** layout view.
Each section consists of 1-3 columns.
For information on the default properties of sections and its columns, see [Add sections and columns on a SharePoint modern page](https://support.microsoft.com/office/add-sections-and-columns-on-a-sharepoint-modern-page-fc491eb4-f733-4825-8fe2-e1ed80bd0899).
-However, the following formatting changes have occurred in the default properties of sections and its columns:
+The sections and its columns too - much like other web parts - have experienced the following formatting changes in its default properties:
-1. When you use the **Two columns**, **Three columns**, **One-third left**, or the **One-third right** layout options to organize your content, the content gets stacked into a single column like the content published using the **One Column** layout option.
+1. When you use the **Two columns**, **Three columns**, **One-third left**, or the **One-third right** layout options to organize your content, the content gets stacked into a single column, similar to the **One Column** layout option's output.
- :::image type="content" source="media/multi-column-layout-option-not-supported.png" alt-text="The Multi Column layout option not being supported in Outlook.":::
+ :::image type="content" source="media/multi-column-layout-option-not-supported.png" alt-text="The Multi Column layout option not being supported in Outlook." lightbox="media/multi-column-layout-option-not-supported.png":::
1. Collapsible sections aren't supported, including section titles (which will be dropped).
- :::image type="content" source="media/option-make-sections-collapsible.png" alt-text="The option to make sections collapsible.":::
- :::image type="content" source="media/section-title-being-dropped.png" alt-text="Section title being dropped.":::
+ :::image type="content" source="media/option-make-sections-collapsible.png" alt-text="The option to make sections collapsible." lightbox="media/option-make-sections-collapsible.png":::
+ :::image type="content" source="media/section-title-being-dropped.png" alt-text="Section title being dropped." lightbox="media/section-title-being-dropped.png":::
1. Dividers between sections aren't supported.
- :::image type="content" source="media/dividers-between-sections-not-supported.png" alt-text="Dividers between sections not being supported in Outlook.":::
+ :::image type="content" source="media/dividers-between-sections-not-supported.png" alt-text="Dividers between sections not being supported in Outlook." lightbox="media/dividers-between-sections-not-supported.png":::
SharePoint Add And Configure The Recommended Items And Popular Items Web Part https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/add-and-configure-the-recommended-items-and-popular-items-web-part.md
Here are the steps to configure the RIWP:
![Edit WP](../media/OTCSP_EditWP.png)
-3. In the Web Part tool pane, select **Change query**. This opens a dialog.
+3. In the Web Part tool pane, select **Change query**. This option opens a dialog.
4. In the **Build Your Query** dialog, select the following:
Here are the steps to configure the RIWP:
![TIWP query](../media/OTCSP_RIWPQuery.png)
-You might be thinking "OK, that was easy, but what does it actually mean?" Understanding this can be is a bit difficult. Let's take a closer look.
+You might be thinking "OK, that was easy, but what does it actually mean?" Understanding this process can be a bit difficult. Let's take a closer look.
- **A token from the URL** means that we want to obtain recommendations for a value that is used in the URL.
- - **{URL.Token.2}** is a query variable that represents the second value in the URL as counted from right to left. For example, in the URL http://www.contoso.com/computers/desktops/5637145799/5637146352, the query variable **{URLToken.2}** represents the value *5637145799*. Remember when we connected our publishing site to the catalog (see [Stage 5: Connect your publishing site to a catalog in SharePoint Server](stage-5-connect-your-publishing-site-to-a-catalog.md)), we specified that the value of *Group Number* should be used as the second to last value in the URL of our catalog item page. That means the query variable **{URL.Token.2}** represents the value of *Group Number*. Also, we mapped [Change the mapping of the UsageAnalyticsID managed property](change-the-content-search-web-part-display-template-and-use-windows-powershell-t.md#BKMK_ChangeTheMappingFoTheUsageAnalyticsIDManagedPriperty) so the Usage analytics calculation would be based on *Group Number*.
+ - **{URL.Token.2}** is a query variable that represents the second value in the URL as counted from right to left. For example, in the URL `https://www.contoso.com/computers/desktops/5637145799/5637146352`, the query variable **{URLToken.2}** represents the value *5637145799*. Remember when we connected our publishing site to the catalog (see [Stage 5: Connect your publishing site to a catalog in SharePoint Server](stage-5-connect-your-publishing-site-to-a-catalog.md)), we specified that the value of *Group Number* should be used as the second to last value in the URL of our catalog item page. That means the query variable **{URL.Token.2}** represents the value of *Group Number*. Also, we mapped [Change the mapping of the UsageAnalyticsID managed property](change-the-content-search-web-part-display-template-and-use-windows-powershell-t.md#BKMK_ChangeTheMappingFoTheUsageAnalyticsIDManagedPriperty) so the Usage analytics calculation would be based on *Group Number*.
- **Specify a URL** means that we want to specify from which site we get recommendations, in this case our Authoring site.
- But from these settings, it is not clear which managed property is used in the query. So, to view more information about the query, select **TEST**. The query that is issued by the Web Part is shown in the **Query text** section.
+ But from these settings, it's not clear as to which managed property is used in the query. So, to view more information about the query, select **TEST**. The query that's issued by the Web Part is shown in the **Query text** section.
![Query text](../media/OTCSP_QueryText.png)
-If we break this down, we get the following:
+If we break the query down, we get the following components:
- **recommendedfor** is the managed property that is used in the query.
If we break this down, we get the following:
From the *URL of the Authoring site*, search for *document or list items* where the value of the managed property *recommendedfor* contains the value that is currently used as the second value in the URL, counting from right to left.
- Now we know what the query means. But we're not completely done with the configuration. In the **SEARCH RESULT PREVIEW** section, we can see that all items in a product group are displayed, for example all *SV Keyboard E10* (notice that they all have the same value for Group Number in the URL).
+ Now we know what the query means. But we're not done with the configuration. In the **SEARCH RESULT PREVIEW** section, we can see that all items in a product group are displayed, for example, all *SV Keyboard E10* (notice that they all have the same value for Group Number in the URL).
![Recommended Items](../media/OTCSP_RecommendedItems.png)
- All items in the product group are shown because the Usage analytics calculation is performed on the group level. Remember, in [Change the Content Search Web Part display template and use Windows PowerShell to start Usage analytics in SharePoint Server](change-the-content-search-web-part-display-template-and-use-windows-powershell-t.md), we mapped *UsageAnalyticsId* to *ows_ProductCatalogGroupNumber*. But we only want to display one item per product group. Luckily, we can do this by grouping search results.
+ All items in the product group are shown because the Usage analytics calculation is performed on the group level. Remember, in [Change the Content Search Web Part display template and use Windows PowerShell to start Usage analytics in SharePoint Server](change-the-content-search-web-part-display-template-and-use-windows-powershell-t.md), we mapped *UsageAnalyticsId* to *ows_ProductCatalogGroupNumber*. But we only want to display one item per product group, which can be done by grouping search results.
- To group search results, do the following:
+ To group search results, do the following steps:
5. Select **REFINERS --\> Show more**.
If we break this down, we get the following:
![Show all properties](../media/OTCSP_ShowAllProperties.png)
-7. We want to show only one item per product group. Therefore, we select *ProductCatalogGroupNumberOWSTEXT* (the managed property of *Group Number* ). We only want to display one item per group. So we leave the value in **Show there results** as **1**.
+7. We want to show only one item per product group. Therefore, we select *ProductCatalogGroupNumberOWSTEXT* (the managed property of *Group Number*). We only want to display one item per group. So we leave the value in **Show there results** as **1**.
![Group by Group Number](../media/OTCSP_GroupByGroupNumber.png)
If we break this down, we get the following:
Just as you do with the Content Search Web Part (CSWP), you use display templates to control how content should be displayed in a RIWP. [Stage 11: Upload and apply display templates to the Content Search Web Part in SharePoint Server](stage-11-upload-and-apply-display-templates-to-the-content-search-web-part.md) explains how to upload and apply display templates to the Content Search Web Part. You can do the same for the RIWP. The display template that is used by the RIWP contains important code that logs the two usage events: *Recommendation Displayed* and *Recommendation Clicked*.
-In [An introduction to recommendations and popular items in SharePoint Server](an-introduction-to-recommendations-and-popular-items.md) we told you about the three default usage events in SharePoint Server. The usage events *Recommendation Displayed* and *Recommendation Clicked* are used to record statistics of how visitors have interacted with the content on your website. When an item is displayed as a recommendation, a *Recommendation Displayed* usage event is recorded. When an item is clicked on when it is displayed as a recommendation, a *Recommendation Clicked* usage event is recorded. We'll show you how you can view these statistics in a later article.
+In [An introduction to recommendations and popular items in SharePoint Server](an-introduction-to-recommendations-and-popular-items.md), we told you about the three default usage events in SharePoint Server. The usage events *Recommendation Displayed* and *Recommendation Clicked* are used to record statistics of how visitors have interacted with the content on your website. When an item is displayed as a recommendation, a *Recommendation Displayed* usage event is recorded. When an item is clicked on when it is displayed as a recommendation, a *Recommendation Clicked* usage event is recorded. We'll show you how you can view these statistics in a later article.
In [Change the Content Search Web Part display template and use Windows PowerShell to start Usage analytics in SharePoint Server](change-the-content-search-web-part-display-template-and-use-windows-powershell-t.md), we changed the CSWP display template to log the *Views* usage event. The logging of the *Recommendation Displayed* and *Recommendation Clicked* usage events are performed in the RIWP. The default display template that is used by the RIWP is *Item_RecommendationsClickLogging*. This display template contains the two functions *LogRecsViewToEventStore* and *LogRecsClickToEventStore*. These two functions log the *Recommendation Displayed* and *Recommendation Clicked* usage events.
After applying the changed display template to the RIWP, the recommended items a
You can display the most popular, that is, *the most viewed* items within your catalog by adding a Popular Items Web Part (PIWP) to your category page. It's important to understand that when you add a PIWP to your catalog page, the PIWP will automatically show the most viewed items *within each category*. For example, if a visitor is viewing the *Cameras* category, the PIWP will show the most viewed items within the *Cameras* category. If a visitor is viewing the *Camcorders* category, the PIWP will show the most viewed items within the *Camcorders* category.
-To add a PIWP, navigate to the page where you want to add the PIWP. In our Contoso scenario, we'll add a PIWP to our category page. Do the following:
+To add a PIWP, navigate to the page where you want to add the PIWP. In our Contoso scenario, we'll add a PIWP to our category page. Do the following steps:
1. Select the **Settings** menu --> **Edit page**.
In our Contoso scenario, we'll show the PIWP above the CSWP.
![Edit PIWP](../media/OTCSP_EditPIWP.png)
-3. In the Web Part tool pane, select **Change query**. This will open a dialog.
+3. In the Web Part tool pane, select **Change query**. This option opens a dialog.
-4. In the **Restrict by app** section, select **Specify a URL** and enter the URL of your Authoring site.
+4. In the **Restrict by app** section, select **Specify a URL** and enter the URL of your Authoring site.
-5. In the **Restrict by** tag section, select **Restrict by current and child navigation terms**.
+5. In the **Restrict by** tag section, select **Restrict by current and child navigation terms**.
No results are displayed in the **SEARCH RESULT PREVIEW** section. What's going on? ![No Popular Results 2](../media/OTCSP_NoPopularResults2.png)
- To see more about the query that the PIWP issues, select **TEST**. On the **TEST** tab we can see the **Query text**.
+ To see more about the query that the PIWP issues, select **TEST**. On the **TEST** tab, we can see the **Query text**.
![PIWP Query Text](../media/OTCSP_PIWPQueryText.png)
The query text means the following:
- The colon : means "contains".
- - 91eb9f0d-3e5a-41a8-8487-78dfe234ca7c is the GUID of the current category. In this example the current category is *Cameras*.
+ - `91eb9f0d-3e5a-41a8-8487-78dfe234ca7c` is the GUID of the current category. In this example, the current category is *Cameras*.
- **(IsDocument:"True" OR contentclass:"STS_ListItem")** narrows the search result down to only documents or list items.
- If we put this information together, we can understand that the query means the following:
+ If we put this information together, the query provides us with the following understandings:
From the *URL of the Authoring site*, search for *document or list items* where the value of the managed property *owstaxIdMetadataAllTagsInfo* contains the GUID of the current navigation category or any of the children of the current navigation.
The query text means the following:
After you've changed the mapping of the property, you must start a full crawl, as explained in [Stage 4: Set up search and enable the crawling of your catalog content in SharePoint Server](stage-4-set-up-search-and-enable-the-crawling-of-your-catalog-content.md).
- There is one very important thing that you can't see in the query text, and that is how the search results are sorted. The PIWP sorts search results in a descending order on the *ViewsRecent* managed property. By default, the *ViewsRecent* managed property contains the number of views for an item within the last 14 days. Later in this series we'll explain how to change this, for example, to the past seven days. This means that the query issued by the PIWP will do the following:
+ There is one important thing that you can't see in the query text, and that is how the search results are sorted. The PIWP sorts search results in a descending order on the *ViewsRecent* managed property. By default, the *ViewsRecent* managed property contains the number of views for an item within the last 14 days. Later in this series, we'll explain how to change this time range, for example, to the past 7 days. This default behavior of the property means that the query issued by the PIWP will do the following tasks:
From the *URL of the authoring site*, search for *document or list items* where the value of the managed property *owstaxIdMetadataAllTagsInfo* contains the GUID of the current navigation category, or any of the children of the current navigation. Sort the search results in *descending order of views for the past 14 days*.
The query text means the following:
Our PIWP is working the way it should. Nice!
- So now you know how to configure the RIWP and the PIWP. When you you perform these tasks, you should be logged in to your own account.
+ So now you know how to configure the RIWP and the PIWP. When you perform these tasks, you should be logged in to your own account.
![Logged In User](../media/OTCSP_LoggedInUser.png)
-In the next article of this series, we'll explain how all this works if the website only has anonymous users, that is, users who are not logged in.
+In the next article of this series, we'll explain how all these configurations work if the website only has anonymous users, that is, users who are not logged in.
### Next article in this series
-[Use recommendations and popular items on websites with anonymous users in SharePoint Server](use-recommendations-and-popular-items-on-websites-with-anonymous-users.md)
-
-
+[Use recommendations and popular items on websites with anonymous users in SharePoint Server](use-recommendations-and-popular-items-on-websites-with-anonymous-users.md)
SharePoint Change Web Application Bindings https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/change-web-application-bindings.md
Title: "Update a web application URL and IIS bindings for SharePoint Server Subscription Edition" -+ Last updated 09/24/2021 audience: ITPro
SharePoint Configure Recommendations And Usage Event Types https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/configure-recommendations-and-usage-event-types.md
You can view the statistics for all usage event types in Popularity Trends and M
## Create a custom usage event type <a name="BKMK_CreateCustomUsageEventType"> </a>
-There are three default usage event types in SharePoint Server. You can create up to twelve custom usage event types by using Microsoft PowerShell.
+There are three default usage event types in SharePoint Server. You can create up to 12 custom usage event types by using Microsoft PowerShell.
**To create a custom usage event type**
There are three default usage event types in SharePoint Server. You can create u
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
There are three default usage event types in SharePoint Server. You can create u
- \<SiteName\> is the name of the site for which you want to create a custom usage event.
- - \<EventTypeName\> is the name of the new custom usage event type that you want to create ΓÇö for example, *BuyEventType* .
+ - \<EventTypeName\> is the name of the new custom usage event type that you want to createΓÇöfor example, *BuyEventType* .
This procedure creates a random GUID for the usage event type. Use this GUID when you add code to record the custom usage event, as described in [Record a custom usage event](configure-recommendations-and-usage-event-types.md#BKMK_RecordCustomUsageEvent).
There are three default usage event types in SharePoint Server. You can create u
## Record a custom usage event <a name="BKMK_RecordCustomUsageEvent"> </a>
-After you have created a custom usage event type, as described in [Create a custom usage event type](configure-recommendations-and-usage-event-types.md#BKMK_CreateCustomUsageEventType), you have to add code to the place where the event occurs ΓÇö for example, when a page loads, or when a user clicks a link or a button. This data is then sent to the analytics processing component, where it is recorded and processed.
+After you have created a custom usage event type, as described in [Create a custom usage event type](configure-recommendations-and-usage-event-types.md#BKMK_CreateCustomUsageEventType), you have to add code to the place where the event occursΓÇöfor example, when a page loads, or when a user clicks a link or a button. This data is then sent to the analytics processing component, where it's recorded and processed.
-If you are using cross-site publishing, where you show catalog content on a publishing site, you must record the usage event on the URL of the indexed item, and override some site settings. For example, if you have a catalog in an authoring site that you have published on a publishing site, when a user interacts with a catalog item on the publishing site, this usage event must be recorded on the item in the authoring site. Furthermore, the code that you add to record the usage event must override the SiteId and the WebId of the publishing site, and be replaced with the SiteId and the WebId of the authoring site.
+If you're using cross-site publishing, where you show catalog content on a publishing site, you must record the usage event on the URL of the indexed item, and override some site settings. For example, if you have a catalog in an authoring site that you have published on a publishing site, when a user interacts with a catalog item on the publishing site, this usage event must be recorded on the item in the authoring site. Furthermore, the code that you add to record the usage event must override the SiteId and the WebId of the publishing site, and be replaced with the SiteId and the WebId of the authoring site.
**To add code to record a custom usage event**
If you are using cross-site publishing, where you show catalog content on a publ
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
If you are using cross-site publishing, where you show catalog content on a publ
```
-4. In an HTML editor, open the file where the custom usage event should be logged ΓÇö for example, a display template for a Content Search Web Part, and add the following code:
+4. In an HTML editor, open the file where the custom usage event should be loggedΓÇöfor example, a display template for a Content Search Web Part, and add the following code:
```powershell window.Log<CustomUsageEventType>ToEventStore = function(url)
If you are using cross-site publishing, where you show catalog content on a publ
} ```
- - `CustomUsageEventType` is the name of the custom event ΓÇö for example, *BuyEventType* .
+ - `CustomUsageEventType` is the name of the custom eventΓÇöfor example, *BuyEventType* .
- - `GUID` is the numeric ID of the usage event type ΓÇö for example, *4e605543-63cf-4b5f-aab6-99a10b8fb257*.
+ - `GUID` is the numeric ID of the usage event typeΓÇöfor example, *4e605543-63cf-4b5f-aab6-99a10b8fb257*.
5. In an HTML editor, open the file that refers to the custom usage event, and add the following code:
If you are using cross-site publishing, where you show catalog content on a publ
- \<CustomUsageEventType\> is the name of the custom event type.
- - \<URL\> is the full URL of the item to which the usage event should be logged ΓÇö for example, *http://contoso.com/faq* .
+ - \<URL\> is the full URL of the item to which the usage event should be loggedΓÇöfor example, `https://contoso.com/faq`.
**To add code to record a custom usage event and override site settings**
If you are using cross-site publishing, where you show catalog content on a publ
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
If you are using cross-site publishing, where you show catalog content on a publ
```
-4. In an HTML editor, open the file where the custom usage event should be logged ΓÇö for example, a display template for a Content Search Web Part. The following example shows how to override the current SiteId, WebId and UserId.
+4. In an HTML editor, open the file where the custom usage event should be loggedΓÇöfor example, a display template for a Content Search Web Part. The following example shows how to override the current SiteId, WebId and UserId.
```powershell window.Log<CustomUsageEventType>ToEventStore = function(url, siteIdGuid, webIdGuid, spUser)
If you are using cross-site publishing, where you show catalog content on a publ
Where:
- - \<CustomUsageEventType\> is the name of the custom event type ΓÇö for example, *BuyEventType* .
+ - \<CustomUsageEventType\> is the name of the custom event typeΓÇöfor example, *BuyEventType* .
- - \<GUID\> is the numeric ID of the usage event type ΓÇö for example, *4e605543-63cf-4b5f-aab6-99a10b8fb257* .
+ - \<GUID\> is the numeric ID of the usage event typeΓÇöfor example, *4e605543-63cf-4b5f-aab6-99a10b8fb257* .
5. In an HTML editor, open the file that refers to the custom usage event type, and add the following code:
If you are using cross-site publishing, where you show catalog content on a publ
Where:
- - \<CustomUsageEventType\> is the name of the custom event type ΓÇö for example, BuyEventType.
+ - \<CustomUsageEventType\> is the name of the custom event typeΓÇöfor example, BuyEventType.
- \<URL\> is the URL found in the managed property OriginalPath.
If you are using cross-site publishing, where you show catalog content on a publ
## Record a default usage event <a name="BKMK_RecordDefaultUsageEvent"> </a>
-If you want to add code that refers to a default usage event type ΓÇö for example, views, you have to add code to the place where the event occurs.
+If you want to add code that refers to a default usage event typeΓÇöfor example, views, you have to add code to the place where the event occurs.
-If you are using cross-site publishing, which shows catalog content on a publishing site, you must record the usage event on the URL of the indexed item, and override some site settings. For example, if you have a catalog in an authoring site that you have published on a publishing site, when a user interacts with a catalog item on the publishing site, this usage event must be recorded on the item in the authoring site. Furthermore, the code that you add to record the usage event must override the SiteId and WebId of the publishing site, and be replaced with the SiteId and WebId of the authoring site.
+If you're using cross-site publishing, which shows catalog content on a publishing site, you must record the usage event on the URL of the indexed item, and override some site settings. For example, if you have a catalog in an authoring site that you have published on a publishing site, when a user interacts with a catalog item on the publishing site, this usage event must be recorded on the item in the authoring site. Furthermore, the code that you add to record the usage event must override the SiteId and WebId of the publishing site, and be replaced with the SiteId and WebId of the authoring site.
**To add code to record a default usage event**
If you are using cross-site publishing, which shows catalog content on a publish
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
If you are using cross-site publishing, which shows catalog content on a publish
```
-4. In an HTML editor, open the file where the custom usage event should be logged ΓÇö for example, a display template for a Content Search Web Part, and add the following code:
+4. In an HTML editor, open the file where the custom usage event should be loggedΓÇöfor example, a display template for a Content Search Web Part, and add the following code:
```powershell window.Log<DefaultUsageEventType>ToEventStore = function(url)
If you are using cross-site publishing, which shows catalog content on a publish
Where:
- - \<DefaultUsageEventType\> is the name of the default usage event type ΓÇö for example, *Views*.
+ - \<DefaultUsageEventType\> is the name of the default usage event typeΓÇöfor example, *Views*.
- - \<EventTypeId\> is the numeric ID of the usage event type ΓÇö for example, *1*.
+ - \<EventTypeId\> is the numeric ID of the usage event typeΓÇöfor example, *1*.
5. In an HTML editor, open the file that refers to the default usage event, and add the following code:
If you are using cross-site publishing, which shows catalog content on a publish
Where:
- - \<DefaultUsageEventType\> is the name of the default usage event type ΓÇö for example, *Views* .
+ - \<DefaultUsageEventType\> is the name of the default usage event typeΓÇöfor example, *Views* .
- - \<URL\> is the full URL of the item to which the usage event should be logged, ΓÇö for example, *http://contoso.com/careers*
+ - \<URL\> is the full URL of the item to which the usage event should be loggedΓÇöfor example, `https://contoso.com/careers`.
6. Save the file.
If you are using cross-site publishing, which shows catalog content on a publish
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
If you are using cross-site publishing, which shows catalog content on a publish
```
-4. In an HTML editor, open the file where the custom usage event should be logged ΓÇö for example, a display template for a Content Search Web Part. The example below shows how to override the current SiteId, the WebId and the UserId.
+4. In an HTML editor, open the file where the custom usage event should be loggedΓÇöfor example, a display template for a Content Search Web Part. The example below shows how to override the current SiteId, the WebId, and the UserId.
```powershell window.Log<DefaultUsageEventType>ToEventStore = function(url, siteIdGuid, webIdGuid, spUser)
If you are using cross-site publishing, which shows catalog content on a publish
Where:
- - \<DefaultUsageEventType\> is the name of the default event type ΓÇö for example, *Views* .
+ - \<DefaultUsageEventType\> is the name of the default event typeΓÇöfor example, *Views* .
- - \<EventTypeId\> is the numeric ID of the usage event type ΓÇö for example, *1* .
+ - \<EventTypeId\> is the numeric ID of the usage event typeΓÇöfor example, *1* .
5. In an HTML editor, open the file that refers to the default usage event type, and add the following code:
If you are using cross-site publishing, which shows catalog content on a publish
Where:
- - \<DefaultUsageEventType\> is the name of the default event type ΓÇö for example, *Views* .
+ - \<DefaultUsageEventType\> is the name of the default event typeΓÇöfor example, *Views* .
- - \<URL\> is the URL in the managed property *OriginalPath* .
+ - \<URL\> is the URL in the managed property *OriginalPath*.
- \<SiteId GUID\> is the SiteId GUID of the authoring site. For information on how to get the SiteId GUID, see [Get SiteId GUID and WebId GUID for a site](configure-recommendations-and-usage-event-types.md#BKMK_GetGUID).
The usage event type property, **RecommendationWeight**, is a numeric value that
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
The usage event type property, **RecommendationWeight**, is a numeric value that
Where:
- - \<EventTypeId\> is the numeric ID of the usage event type for which you want to change the weight ΓÇö for example, *256*.
+ - \<EventTypeId\> is the numeric ID of the usage event type for which you want to change the weightΓÇöfor example, *256*.
- - \<RecommendationWeightNumber\> is the level of importance that you want to apply to the user event type ΓÇö for example, *4*.
+ - \<RecommendationWeightNumber\> is the level of importance that you want to apply to the user event typeΓÇöfor example, *4*.
> [!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.
The usage event type property, **RecommendationWeight**, is a numeric value that
## Change the Recent time period for a usage event type <a name="BKMK_ChangeRecentTimePeriod"> </a>
-The usage event type property **RecentPopularityTimeframe** is a numeric value that defines the **Recent** time period in the **Most Popular Items** report. The Most Popular Items report shows the most popular items per usage event type for all items in a library or list ΓÇö for example, the most viewed items in a library or list. The report can be sorted by the time periods **Recent** or **Ever**. By default, the Recent time period is set to the last 14 days for each usage event. You can change this to a time period between one and 14 days.
+The usage event type property **RecentPopularityTimeframe** is a numeric value that defines the **Recent** time period in the **Most Popular Items** report. The Most Popular Items report shows the most popular items per usage event type for all items in a library or listΓÇöfor example, the most viewed items in a library or list. The report can be sorted by the time periods **Recent** or **Ever**. By default, the Recent time period is set to the last 14 days for each usage event. You can change this value to a time period between one and 14 days.
**To change the Recent time period for a usage event type**
The usage event type property **RecentPopularityTimeframe** is a numeric value t
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
The usage event type property **RecentPopularityTimeframe** is a numeric value t
Where:
- - \<EventTypeId\> is the numeric ID of the usage event type for which you want to change the **Recent** time frame ΓÇö for example, *256* .
+ - \<EventTypeId\> is the numeric ID of the usage event type for which you want to change the **Recent** time frameΓÇöfor example, *256*.
- - \<TimeFrame\> is the new **Recent** time frame that you want to apply to the user event type ΓÇö for example, *7*.
+ - \<TimeFrame\> is the new **Recent** time frame that you want to apply to the user event typeΓÇöfor example, *7*.
> [!NOTE] > The system updates any changes to the Recent time period only after the Usage Analytics Timer Job has run.
Users that are browsing the contents of a site without being connected to an acc
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
Users that are browsing the contents of a site without being connected to an acc
Where:
- - \<EventTypeId\> is the numeric ID of the usage event type that you want to enable for the logging of anonymous users ΓÇö for example, *256*.
+ - \<EventTypeId\> is the numeric ID of the usage event type that you want to enable for the logging of anonymous usersΓÇöfor example, *256*.
**To disable the logging of usage events of anonymous users**
Users that are browsing the contents of a site without being connected to an acc
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
Users that are browsing the contents of a site without being connected to an acc
Where:
- - \<EventTypeId\> is the numeric ID of the usage event type that you want to disable for the logging of anonymous users ΓÇö for example, *256*.
+ - \<EventTypeId\> is the numeric ID of the usage event type that you want to disable for the logging of anonymous usersΓÇöfor example, *256*.
> [!NOTE] > For the default usage event type *Views* , you cannot disable the logging of anonymous users.
You can use the following PowerShell commands to get the SiteId GUID and the Web
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
- Add memberships that are required beyond the minimums above. 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?view=sharepoint-ps&preserve-view=true).
+ > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Start the SharePoint Management Shell.
You can use the following PowerShell commands to get the SiteId GUID and the Web
Where:
- - _\<RootSiteURL\>_ is the URL of the root site that you want to get the SiteId GUID and the WebId GUID of ΓÇö for example, _http://contoso.com/sites/catalog_.
+ - _\<RootSiteURL\>_ is the URL of the root site that you want to get the SiteId GUID and the WebId GUID ofΓÇöfor example, `https://contoso.com/sites/catalog`.
- - _\<SubSiteLocation\>_ is the remainder of the URL path to the subsite after the root site URL. For example, if your root site URL is _http://contoso.com/sites/catalog_, and your subsite URL is _http://contoso.com/sites/catalog/products_, type _products_ for this placeholder.
+ - _\<SubSiteLocation\>_ is the remainder of the URL path to the subsite after the root site URL. For example, if your root site URL is `https://contoso.com/sites/catalog` and your subsite URL is `https://contoso.com/sites/catalog/products`, type _products_ for this placeholder.
> [!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.
SharePoint Create An Excel Services Dashboard Using An Odata Data Feed https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/create-an-excel-services-dashboard-using-an-odata-data-feed.md
Our example dashboard uses data that is imported into Excel via an OData data fe
4. On the **Connect to Database Server** page, in the **Location of the data feed** box, specify the website address (URL) for the data feed.
- For our example dashboard, we used http://services.odata.org/AdventureWorksV3/AdventureWorks.svc.
+ For our example dashboard, we used `https://services.odata.org/AdventureWorksV3/AdventureWorks.svc`.
5. In the **Log on credentials** section, take one of the following steps:
SharePoint Extend A Claims Based Web Application https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/extend-a-claims-based-web-application.md
Use the procedure described in this section to extend a claims-based SharePoint
- Click **Create a new IIS web site**, and then type the name of the web site in the **Name** box.
-5. In the **IIS Web Site** section, in the **Port** box, type the port number you want to use to access the web application. If you are creating a new web site, this box contains a suggested port number. If you are using an existing web site, this box contains the current port number.
+5. In the **IIS Web Site** section, in the **Port** box, type the port number you want to use to access the web application. If you're creating a new web site, this box contains a suggested port number. If you're using an existing web site, this box contains the current port number.
> [!NOTE] > The default port number for HTTP access is 80, and the default port number for HTTPS access is 443. To enable users to access the web application without typing in a port number, use the appropriate default port number.
Use the procedure described in this section to extend a claims-based SharePoint
> [!NOTE] > In general, this box is empty unless you want to configure two or more IIS web sites to use the same port on the same server and DNS has been configured to point multiple server names to the same server.
-7. In the **IIS Web Site** section, in the **Path** box, type the path to the site directory on the server. If you are creating a new web site, this box contains a suggested path. If you are using an existing web site, this box contains the current path of that web site.
+7. In the **IIS Web Site** section, in the **Path** box, type the path to the site directory on the server. If you're creating a new web site, this box contains a suggested path. If you're using an existing web site, this box contains the current path of that web site.
8. In the **Security Configuration** section, select the authentication method that you want to use for the web application and choose whether or not to use **Use Secure Sockets Layer (SSL)**.
Use the procedure described in this section to extend a claims-based SharePoint
If you're using [cross-site publishing](overview-of-cross-site-publishing.md), be careful about extending the web application. Depending on which site collection you extend the web application for, it can break the friendly URLs to your catalog items. Here's what you should do: -- On your authoring site, don't extend the web application. It'll break the friendly URLs to your catalog items. For example, the URL to your catalog item will not point to the friendly URL http://www.contoso.com/Computers/model101 but to the catalog item in your authoring site, for example http://www.contoso.com/sites/catalog/Lists/Products/DispForm.aspx?ID=1&amp;Source=http%3A%2F%.
+- On your authoring site, don't extend the web application. It will break the friendly URLs to your catalog items. For example, the URL to your catalog item won't point to the friendly URL `https://www.contoso.com/Computers/model101`, but to the catalog item in your authoring site, for example `https://www.contoso.com/sites/catalog/Lists/Products/DispForm.aspx?ID=1&amp;Source=http%3A%2F%`.
-- On your publishing site, if you want to extend the web application, for example to support different authentication providers, you have to extend the web application *before* you connect your publishing site to a catalog as described in [Connect a publishing site to a catalog in SharePoint Server](connect-a-publishing-site-to-a-catalog.md). If you've already connected your publishing site to a catalog, do the following:
+- On your publishing site, if you want to extend the web application, for example to support different authentication providers, you have to extend the web application *before* you connect your publishing site to a catalog as described in [Connect a publishing site to a catalog in SharePoint Server](connect-a-publishing-site-to-a-catalog.md). If you have already connected your publishing site to a catalog, do the following:
1. Disconnect the publishing site from the catalog.
SharePoint Host Named Site Collection Architecture And Deployment https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/host-named-site-collection-architecture-and-deployment.md
description: "Plan and implement host-named site collections in SharePoint Serve
[!INCLUDE[appliesto-2013-2016-2019-SUB-xxx-md](../includes/appliesto-2013-2016-2019-SUB-xxx-md.md)]
-Host-named site collections are the preferred method to deploy sites in SharePoint Server. Because the Microsoft 365 environment uses host-named site collections, new features are optimized for these site collections and they are expected to be more reliable. Learn how to plan for and implement host-named site collections, design URLs, and manage URLs.
+Host-named site collections are the preferred method to deploy sites in SharePoint Server. Because the Microsoft 365 environment uses host-named site collections, new features are optimized for these site collections and they're expected to be more reliable. Learn how to plan for and implement host-named site collections, design URLs, and manage URLs.
## Architecture and design for host-named site collections <a name="section1"> </a>
-Host-named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as `http://TeamA.contoso.com` and `http://TeamB.contoso.com`. This enables you to deploy many sites with unique DNS names in the same web application. It also enables hosters to scale an environment to many customers. If you do not use host-named site collections, your SharePoint web application will contain many path-based site collections that share the same host name (DNS name). For example, Team A has a site collection at `http://contoso.com/sites/teamA`, and Team B has a site collection at `http://contoso.com/sites/teamB`.
+Host-named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as `http://TeamA.contoso.com` and `http://TeamB.contoso.com`. This example shows that you to deploy many sites with unique DNS names in the same web application. It also enables hosters to scale an environment to many customers. If you don't use host-named site collections, your SharePoint web application will contain many path-based site collections that share the same host name (DNS name). For example, Team A has a site collection at `http://contoso.com/sites/teamA`, and Team B has a site collection at `http://contoso.com/sites/teamB`.
We recommend host-named site collections unless requirements dictate that path-based sites with alternate access mapping are necessary (described later in this article). This article describes how to implement host-named site collections in a recommended configuration with SharePoint Server. Information about advanced configurations is included at the end of this article: [Use multiple web applications with host-named site collections](host-named-site-collection-architecture-and-deployment.md).
This recommended configuration in the diagram includes the following elements:
- My Sites with site URLs in the following format: `http://my.contoso.com/personal/<site_name>`.
-The number of sites within the web application and the URLs for sites are not important for this example.
+The number of sites within the web application and the URLs for sites aren't important for this example.
When creating a Web application for host-named site collections, the URL of the Web application and the root site collection will be `http://<_webapp.contoso.com_>/`. ![URLs of the Web app and root site collection.](../media/HNSC_Webapp_root_URL.jpg)
-This architecture is recommended to deploy sites because it is the same architecture that the Microsoft 365 environment uses. Consequently this is the most heavily tested configuration. New features, including the App model and Request Management, are optimized for this configuration, and it is the most reliable configuration going forward.
+This architecture is recommended to deploy sites because it's the same architecture that the Microsoft 365 environment uses. So, this configuration is the most heavily tested configuration. New features, including the App model and Request Management, are optimized for this configuration, and it's the most reliable configuration going forward.
-The recommended configuration does not include the following elements:
+The recommended configuration doesn't include the following elements:
- Enabling apps in environments with multiple zones.
The recommended configuration does not include the following elements:
### Host-named site collections versus path-based site collections <a name="section1b"> </a>
-When you use host-named site collections, each site collection in a web application is assigned a unique DNS name. When you deploy many host-named site collections to a single web application, you increase scalability of the farm because resources are not used to support multiple application pools and web applications.
+When you use host-named site collections, each site collection in a web application is assigned a unique DNS name. When you deploy many host-named site collections to a single web application, you increase scalability of the farm because resources aren't used to support multiple application pools and web applications.
SharePoint Server supports both host-named and path-based site collections. The following table details the differences between the two options and provides more information about host-named site collections.
SharePoint Server supports both host-named and path-based site collections. The
|&nbsp;|Host-named site collections|Path-based site collections| |:--|:--|:--|
-|Creating sites|You can use Microsoft PowerShell to create host-named site collections. You cannot use Central Administration to create host-named site collections.|You can use Central Administration or PowerShell to create path-based site collections.|
+|Creating sites|You can use Microsoft PowerShell to create host-named site collections. You can't use Central Administration to create host-named site collections.|You can use Central Administration or PowerShell to create path-based site collections.|
|URLs|Each host-named site collection in a web application is assigned a unique DNS name. <br/> You can use zones to assign up to five URLs to host-named sites, including vanity URLs.|All path-based site collections in a web application share the same host name (DNS name) as the web application. You can extend a web application to implement up to five zones and create different host names for each zone. However, the host name for a zone applies to all site collections within the web application.|
-|Root site collection and search|A root site collection is required to crawl content in a web application. A root site collection can be a site collection that users cannot access.|Typically, a single path-based site collection serves as the root site collection within a web application. You can use managed paths to create additional site collections within the web application.|
+|Root site collection and search|A root site collection is required to crawl content in a web application. A root site collection can be a site collection that users can't access.|Typically, a single path-based site collection serves as the root site collection within a web application. You can use managed paths to create more site collections within the web application.|
|URL mapping|Use PowerShell commands to manage URLs (Set-SPSiteURL, Remove-SPSiteURL, Get-SPSiteURL).|Use Alternate Access Mappings to manage URLs.|
-|Self-service site creation|You need to use a custom solution for self-service site creation with host-named site collections. <br/> The Self Service Site Creation feature that is part of the default installation of SharePoint Server does not work with host-named site collections.|When you use the Self Service Site Creation feature that is part of the default installation of SharePoint Server, you create path-based sites.|
+|Self-service site creation|You need to use a custom solution for self-service site creation with host-named site collections. <br/> The Self Service Site Creation feature that is part of the default installation of SharePoint Server doesn't work with host-named site collections.|When you use the Self Service Site Creation feature that is part of the default installation of SharePoint Server, you create path-based sites.|
|Managed paths|Managed paths for host-named site collections apply at the farm level and are available for all web applications. <br/> You have to use PowerShell to create managed paths for host-named site collections.|Managed paths for path-based sites apply at the web application level. <br/> You can use Central Administration or Microsoft PowerShell to create managed paths for path-based site collections.| ### Design and manage URLs for host-named site collections
These cmdlets provide URL mapping functionality for host-named site collections
#### Zones and host-named site collections
-Host-named site collections are available through any zone. Host-named site collections are not limited to the default zone. If needed, you can implement multiple zones and use zones and host-named site collections to configure different authentication settings or policies.
+Host-named site collections are available through any zone. Host-named site collections aren't limited to the default zone. If needed, you can implement multiple zones and use zones and host-named site collections to configure different authentication settings or policies.
> [!NOTE] > To use different zones you need to extend existing web application.
-You can assign up to five URLs to a single site collection by assigning one URL per zone. Even if you follow the recommended architecture by implementing only one zone, you can still assign up to five URLs to host-named site collections. This is because if a zone is not implemented by extending the web application, SharePoint Server uses the default zone.
+You can assign up to five URLs to a single site collection by assigning one URL per zone. Even if you follow the recommended architecture by implementing only one zone, you can still assign up to five URLs to host-named site collections. This provision is because if a zone isn't implemented by extending the web application, SharePoint Server uses the default zone.
For example, the following URLs could provide access to the same Internet site:
For example, the following URLs could provide access to the same Internet site:
- www.Contoso.ie
-The search crawl account requires access to content through the Default zone by using Integrated Windows authentication (NTLM or Kerberos). Because claims authentication allows multiple types of authentication in one zone, this requirement should not affect other authentication requirements.
+The search crawl account requires access to content through the Default zone by using Integrated Windows authentication (NTLM or Kerberos). Because claims authentication allows multiple types of authentication in one zone, this requirement shouldn't affect other authentication requirements.
#### Managed paths and host-named site collections
-URLs that are configured for the same site collection may have different schemes and domains, but they must have the same managed paths, namely everything after the '/' that follows the domain must be the same. For example, `http://www.Contoso.com/sites/Site1` and `http://www.Fabrikam.com/sites/Site1` can both point to the same site collection but `http://www.Contoso.com/sites/Site1` and `http://www.bar.com/sites/Project1` cannot.
+URLs that are configured for the same site collection may have different schemes and domains, but they must have the same managed paths, namely everything after the '/' that follows the domain must be the same. For example, `http://www.Contoso.com/sites/Site1` and `http://www.Fabrikam.com/sites/Site1` can both point to the same site collection but `http://www.Contoso.com/sites/Site1` and `http://www.bar.com/sites/Project1` can't.
-The cmdlets that manage URLs only operate on the root site collection for a host name, for example `http://www.Contoso.com`. These cmdlets do not operate on a managed path site collection that is underneath the root, such as `http://www.Contoso.com/sites/Project1`. Sites below the root of a host-named site collection will inherit the URL settings of that root host-named site collection.
+The cmdlets that manage URLs only operate on the root site collection for a host name, for example `http://www.Contoso.com`. These cmdlets don't operate on a managed path site collection that is underneath the root, such as `http://www.Contoso.com/sites/Project1`. Sites below the root of a host-named site collection will inherit the URL settings of that root host-named site collection.
#### Off-box termination of SSL with host-named site collections
Although we recommend host-named site collections for most architectures, you sh
- You need to use the Self Service Site Creation feature that is part of the default installation of SharePoint Server.
- This does not apply to custom self-service site creation solutions.
+ This condition doesn't apply to custom self-service site creation solutions.
-- SSL termination is required but your SSL termination device cannot be configured to produce the necessary custom HTTP header.
+- SSL termination is required but your SSL termination device can't be configured to produce the necessary custom HTTP header.
- You can still use SSL bridging with host-named site collections with these devices if SSL termination is not a requirement.
+ You can still use SSL bridging with host-named site collections with these devices if SSL termination isn't a requirement.
-- You plan to use different application pools for the additional security that these provide or you need to use multiple proxy groups.
+- You plan to use different application pools for the extra security that these groups provide or you need to use multiple proxy groups.
- In these cases, you can use host-named site collections. However, the additional configuration that is required to map URLs for host-named site collections across multiple web applications greatly outweigh the benefits of using host-named site collections. For more information, see [Use multiple web applications with host-named site collections](host-named-site-collection-architecture-and-deployment.md). For more information about creating path-based site collections, see [Create a site collection in SharePoint Server](../sites/create-a-site-collection.md).
+ In these cases, you can use host-named site collections. However, the extra configuration that is required to map URLs for host-named site collections across multiple web applications greatly outweigh the benefits of using host-named site collections. For more information, see [Use multiple web applications with host-named site collections](host-named-site-collection-architecture-and-deployment.md). For more information about creating path-based site collections, see [Create a site collection in SharePoint Server](../sites/create-a-site-collection.md).
### Use host headers and host-named site collections <a name="section1e"> </a> Host headers allow the web server to host multiple web sites on the same IP Address and Port combination. If the incoming HTTP request includes a host header name, and a matching host header is configured in IIS, IIS will respond with the content from the appropriate web site.
-Host headers are configured at the Web Application (IIS web site) level, they are one of the website bindings properties.
+Host headers are configured at the Web Application (IIS web site) level, they're one of the website bindings properties.
-It is important to understand the distinction between Host headers in IIS and Host Named Site Collections. Host headers at the IIS web site level are only intended for path-based site collections.
+It's important to understand the distinction between Host headers in IIS and Host Named Site Collections. Host headers at the IIS web site level are only intended for path-based site collections.
-When using Host named site collections, SharePoint is responsible for resolving the correct site for the address based upon the incoming request passed through IIS. In most cases, applying a host header binding at the IIS web site level makes it impossible to access host-named site collections through the IIS web site. This is because IIS will not respond to requests for host names that differ from the host header binding.
+When using Host named site collections, SharePoint is responsible for resolving the correct site for the address based upon the incoming request passed through IIS. In most cases, applying a host header binding at the IIS web site level makes it impossible to access host-named site collections through the IIS web site. This inaccessibility is because IIS won't respond to requests for host names that differ from the host header binding.
> [!IMPORTANT]
-> If an existing web application has a host header binding set, IIS will not return pages from the host-named site collection until you remove the binding from IIS. For more information, see [Update a web application URL and IIS bindings for SharePoint 2013](update-a-web-application-url-and-iis-bindings.md).
+> If an existing web application has a host header binding set, IIS won't return pages from the host-named site collection until you remove the binding from IIS. For more information, see [Update a web application URL and IIS bindings for SharePoint 2013](update-a-web-application-url-and-iis-bindings.md).
### Mix host-named site collections and path-based site collections in the same web application <a name="section1f"> </a>
-You can use host-named and path based site collections in the same web application. To ensure that both types of site collections are accessible to users, do not put host header bindings on the IIS website of your web application, including IIS websites for zones that are extended from the web application. If an existing web application has a host header binding set, IIS will not return pages from the host-named site collection until you remove the binding from IIS.
+You can use host-named and path based site collections in the same web application. To ensure that both types of site collections are accessible to users, don't put host header bindings on the IIS website of your web application, including IIS websites for zones that are extended from the web application. If an existing web application has a host header binding set, IIS won't return pages from the host-named site collection until you remove the binding from IIS.
#### My Sites
When you use both types of site collections with My Sites, consider implementing
### Create a web application for host-named site collections <a name="section2a"> </a>
-If you do not intend to configure two or more IIS websites that share the same port number on the same server, create a web application in the Default zone. Do not apply a host header binding at the IIS website level.
+If you don't intend to configure two or more IIS websites that share the same port number on the same server, create a web application in the Default zone. Don't apply a host header binding at the IIS website level.
**To create a web application for host-named site collections**
If you do not intend to configure two or more IIS websites that share the same p
- The **db_owner** fixed database role on all databases that are to be updated.
- - The Administrators group on the server on which you are running the Microsoft PowerShell cmdlet.
+ - The Administrators group on the server on which you're running the Microsoft PowerShell cmdlet.
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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
+ 2. Open the **SharePoint Management Shell**.
If you do not intend to configure two or more IIS websites that share the same p
### Create a root site collection <a name="section2b"> </a>
-A root site collection is a requirement for any Web application. It is also necessary for crawling content. This site collection must have the same URL as the Web application. Currently, SharePoint prevents the creation of a host-named site collection with the same URL as a Web application. Therefore, the root site collection is created as a path-based site collection.
+A root site collection is a requirement for any Web application. It's also necessary for crawling content. This site collection must have the same URL as the Web application. Currently, SharePoint prevents the creation of a host-named site collection with the same URL as a Web application. Therefore, the root site collection is created as a path-based site collection.
![A web application with a root site.](../media/HNSC_rootsite.jpg)
The following example creates an empty site collection that is the root site col
New-SPSite 'http://<servername>' -Name 'Portal' -Description 'Portal on root' -OwnerAlias 'contoso\administrator' -language 1033 -Template 'STS#0' ```
-Only the root site collection of the web application appears in the content source. Even though all other host-named site collections in the web application do not appear in the content source, by default search automatically crawls the other host-named site collections.
+Only the root site collection of the web application appears in the content source. Even though all other host-named site collections in the web application don't appear in the content source, by default search automatically crawls the other host-named site collections.
### Create host-named site collections <a name="section2c"> </a>
-You must use Microsoft PowerShell to create a host-named site collection. You cannot use the SharePoint ServerCentral Administration web application to create a host-named site collection, but you can use Central Administration to manage the site collection after you have created it.
+You must use Microsoft PowerShell to create a host-named site collection. You can't use the SharePoint ServerCentral Administration web application to create a host-named site collection, but you can use Central Administration to manage the site collection after you have created it.
You can create a host-named site collection by using the Microsoft PowerShell New-SPSite cmdlet with the -HostHeaderWebApplication parameter, as shown in the following example:
You can create a host-named site collection by using the Microsoft PowerShell Ne
- The **db_owner** fixed database role on all databases that are to be updated.
- - The Administrators group on the server on which you are running the Microsoft PowerShell cmdlet.
+ - The Administrators group on the server on which you're running the Microsoft PowerShell cmdlet.
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?view=sharepoint-ps&preserve-view=true).
+ > If you don't have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Open the **SharePoint Management Shell**.
You can create a host-named site collection by using the Microsoft PowerShell Ne
New-SPSite 'http://portal.contoso.com' -HostHeaderWebApplication (Get-SPWebApplication 'Contoso Sites') -Name 'Portal' -Description 'Customer root' -OwnerAlias 'contoso\administrator' -language 1033 -Template 'STS#0' ```
-This creates a host-named site collection that has the URL, http://portal.contoso.com, in the SharePoint Server web application that has the URL, http://portal.contoso.com.
+This syntax creates a host-named site collection that has the URL, https://portal.contoso.com, in the SharePoint Server web application that has the URL, https://portal.contoso.com.
### Use managed paths with host-named site collections <a name="section2d"> </a> You can implement managed paths with host-named site collections. Hosters can provide multiple site collections to the same customer with each site collection sharing the customer's unique host name but differentiated by the URL path after the host name. Managed paths for host-named site collections are limited to 20 per farm. For more information, see [Software boundaries and limits for SharePoint Server 2016](../install/software-boundaries-and-limits.md#WebApplication).
-Managed paths for host-named site collections behave differently from managed paths for path-based site collections. Managed paths for host-named site collections are available to all host-named site collections within the farm regardless of the web application that the host-named site collection is in. In contrast, managed paths for path-based site collections only apply to sites within the same web application. Managed paths for path-based site collections do not apply to path-based site collections in other web applications. Managed paths for one type of site collection do not apply to the other type of site collection.
+Managed paths for host-named site collections behave differently from managed paths for path-based site collections. Managed paths for host-named site collections are available to all host-named site collections within the farm regardless of the web application that the host-named site collection is in. In contrast, managed paths for path-based site collections only apply to sites within the same web application. Managed paths for path-based site collections don't apply to path-based site collections in other web applications. Managed paths for one type of site collection don't apply to the other type of site collection.
To create a managed path, you must first create a site collection with the desired base URL. For example, to create `http://teams.contoso.com/finance` you must first create the site collection for `http://teams.contoso.com`.
You can use PowerShell to remove a managed path even if a site collection exists
### Map URLs to host-named site collections <a name="section2e"> </a>
-When you create a new hostname site collection, the default alternate access mappings will still exist but cannot be used. Use PowerShell commands to manage URL mappings for host-named site collections.
+When you create a new hostname site collection, the default alternate access mappings will still exist but can't be used. Use PowerShell commands to manage URL mappings for host-named site collections.
Add a mapping to an existing site:
Each URL mapping is applied to a single zone. Use one of the following zone name
- Extranet
-If you do not specify the **Zone** parameter and the URL mapping entry is new, the default zone is used. You still have a limitation to 5 URLs for a unique Site Collection.
+If you don't specify the **Zone** parameter and the URL mapping entry is new, the default zone is used. You still have a limitation to 5 URLs for a unique Site Collection.
Remove a mapping for a site:
You can configure a single web application that uses SSL and then create multipl
You need to acquire a wildcard certificate or subject alternate name (SAN) certificate and then use a host-named site collection URL format that matches that certificate. For example, if you acquire a \*.contoso.com wildcard certificate, you must generate host-named site collection URLs such as `https://site1.contoso.com`, `https://site2.contoso.com`, and so on, to enable these sites to pass browser SSL validation. However, if you require unique second-level domain names for sites, you must create multiple web applications rather than multiple host-named site collections.
-To configure SSL for host-named site collections, enable SSL when you create the web application. This will create an IIS website with an SSL binding instead of an HTTP binding. After you create the web application, open IIS Manager and assign a certificate to that SSL binding. You can then create site collections in that web application.
+To configure SSL for host-named site collections, enable SSL when you create the web application. This setting will create an IIS website with an SSL binding instead of an HTTP binding. After you create the web application, open IIS Manager and assign a certificate to that SSL binding. You can then create site collections in that web application.
-If you are implementing multiple zones with host-named site collections, ensure that the configuration of certificates and bindings (SSL or HTTP) is appropriate for each zone and corresponding IIS site.
+If you're implementing multiple zones with host-named site collections, ensure that the configuration of certificates and bindings (SSL or HTTP) is appropriate for each zone and corresponding IIS site.
### Use host-named site collections with off-box SSL termination <a name="section2g"> </a>
You can use host-named site collections with off-box SSL termination. There are
- If the client SSL request is sent to the default SSL port (443), then the SSL terminator or reverse proxy must forward the decrypted HTTP request to the front-end web server on the default HTTP port (80). If the client SSL request is sent to a non-default SSL port, then the SSL terminator or reverse proxy must forward the decrypted HTTP request to the front-end web server on the same non-default port. -- The device that terminates the SSL connection, such as a reverse proxy server, must be capable of generating a custom HTTP header: **Front-End-Https: On**. This is the same custom header that Outlook Web Access (OWA) uses: **Front-End-Https: On/Off**. More information about this custom header is included later in this section.
+- The device that terminates the SSL connection, such as a reverse proxy server, must be capable of generating a custom HTTP header: **Front-End-Https: On**. This header is the same custom header that Outlook Web Access (OWA) uses: **Front-End-Https: On/Off**. More information about this custom header is included later in this section.
To use host-named site collections with off-box SSL termination, configure your web application as you normally would for SSL termination and ensure that it meets the requirements described above. In this scenario, SharePoint Server will use HTTPS instead HTTP to render links of its host-named site collections in that web application.
-Reverse proxy servers can publish SharePoint Server host-named site collections and perform off-box SSL termination. In this scenario, the reverse proxy server changes the connection type between the end user and the SharePoint web front-end server from SSL/TLS to HTTP or vice versa. Reverse proxy servers in this scenario must insert an additional HTTP header in the user's request when it forwards the request to the SharePoint web front-end server. This additional HTTP header indicates to SharePoint Server the type of connection the end user initiated so that SharePoint Server renders URLs appropriately in its response. The HTTP header name is "Front-End-Https" and its acceptable values are as follows.
+Reverse proxy servers can publish SharePoint Server host-named site collections and perform off-box SSL termination. In this scenario, the reverse proxy server changes the connection type between the end user and the SharePoint web front-end server from SSL/TLS to HTTP or vice versa. Reverse proxy servers in this scenario must insert an extra HTTP header in the user's request when it forwards the request to the SharePoint web front-end server. This extra HTTP header indicates to SharePoint Server the type of connection the end user initiated so that SharePoint Server renders URLs appropriately in its response. The HTTP header name is "Front-End-Https" and its acceptable values are as follows.
**Table: Front-End-Https header values**
Reverse proxy servers can publish SharePoint Server host-named site collections
|On|The reverse proxy server received the end user's request over an encrypted (SSL or TLS) HTTPS connection. For example, **Front-End-Https: On**.| |Off|The reverse proxy server received the end user's request over an unencrypted HTTP connection.|
-The values are not case-sensitive. For example, on, ON, On, and oN are acceptable.
+The values aren't case-sensitive. For example, on, ON, On, and oN are acceptable.
-This custom header works only with host-named site collections. It does not work with path-based site collections.
+This custom header works only with host-named site collections. It doesn't work with path-based site collections.
The following example shows a host-named site collection created at https:
The following example shows a host-named site collection created at https:
New-SPSite 'https://portal.contoso.com' -HostHeaderWebApplication (Get-SPWebApplication 'Contoso Sites') -Name 'Portal' -OwnerAlias 'contoso\administrator' -language 1033 -Template 'STS#0' ```
-This example creates a host-named site collection that has the URL, https://portal.contoso.com, in the SharePoint Server web application that has the URL http://webapp.contoso.com.
+This example creates a host-named site collection that has the URL, `https://portal.contoso.com`, in the SharePoint Server web application that has the URL `https://webapp.contoso.com`.
### Enable apps in environments with multiple zones <a name="section2h"> </a>
This example creates a host-named site collection that has the URL, https://port
> [!NOTE] > This section applies only to SharePoint Server 2013.
-The March 2013 Public Update enables you to configure an app domain for each web application zone and use alternate access mapping and host-header web application configuration. Before the release of this update, you could only host one app domain and it had to be in the Default zone. You could not use the app domain on alternate access mappings or host-header web application configurations.
+The March 2013 Public Update enables you to configure an app domain for each web application zone and use alternate access mapping and host-header web application configuration. Before the release of this update, you could only host one app domain and it had to be in the Default zone. You couldn't use the app domain on alternate access mappings or host-header web application configurations.
To resolve this issue, apply the SharePoint Server Cumulative Update Server Hotfix Package: March 12, 2013, see [Updates for SharePoint 2013](../../Hub/index.yml).
To resolve this issue, apply the SharePoint Server Cumulative Update Server Hotf
### Determine host-named site collections in existing web applications <a name="section3a"> </a>
-When you migrate from SharePoint Server 2010 to SharePoint Server, we recommend that you determine how SharePoint Server 2010 sites were created. If sites were created as path-based sites, consider migrating these sites to host-named site collections. If host-named and path-based sites were implemented together, identify the sites that were created as path-based sites and consider migrating these sites to host-named site collections. To accomplish this, look for the 'HostHeaderIsSiteName' flag.
+When you migrate from SharePoint Server 2010 to SharePoint Server, we recommend that you determine how SharePoint Server 2010 sites were created. If sites were created as path-based sites, consider migrating these sites to host-named site collections. If host-named and path-based sites were implemented together, identify the sites that were created as path-based sites and consider migrating these sites to host-named site collections. To accomplish this migration, look for the 'HostHeaderIsSiteName' flag.
The following example determines if a site within a given web application is created as host-named or path based:
else
### Convert path-based site collections to host-named site collections <a name="section3b"> </a>
-You can convert path-based site collections to host-named site collections and host-named site collections to path-based site collections by using the PowerShell cmdlet Set-SPSite. After the site rename, an app pool recycle is recommended to force refreshing the cache. You cannot use the SharePoint Central Administration website or Windows PowerShell cmdlets that attach and detach, or mount and dismount content databases to convert site collections.
+You can convert path-based site collections to host-named site collections and host-named site collections to path-based site collections by using the PowerShell cmdlet Set-SPSite. After the site rename, an app pool recycle is recommended to force refreshing the cache. You can't use the SharePoint Central Administration website or Windows PowerShell cmdlets that attach and detach, or mount and dismount content databases to convert site collections.
The following example converts a standard site collection to a host-named site collection:
If you use more than one web application, you add more operational overhead and
- An organization requires the use of multiple proxy groups.
-It is more complex to implement host-named site collections with multiple web applications in a farm because you must complete more configuration steps. For example, URLs with host-named sites might be spread across multiple web applications that share the same port in a single farm. This scenario requires more configuration steps to ensure that requests are mapped to the correct web applications. You have to manually configure the mappings on each web server in the farm by configuring a separate IP address to represent each web application. You also have to create and manage host-header bindings to assign unique IP addresses for each site. Scripts can manage and replicate this configuration across servers; however, this adds complexity to the solution. Each unique URL also requires a mapping in DNS. Generally speaking, if multiple web applications are a requirement, we recommend path-based site collections with alternate access mapping.
+It's more complex to implement host-named site collections with multiple web applications in a farm because you must complete more configuration steps. For example, URLs with host-named sites might be spread across multiple web applications that share the same port in a single farm. This scenario requires more configuration steps to ensure that requests are mapped to the correct web applications. You have to manually configure the mappings on each web server in the farm by configuring a separate IP address to represent each web application. You also have to create and manage host-header bindings to assign unique IP addresses for each site. Scripts can manage and replicate this configuration across servers; however, this replication of configuration adds complexity to the solution. Each unique URL also requires a mapping in DNS. Generally speaking, if multiple web applications are a requirement, we recommend path-based site collections with alternate access mapping.
The following two tables contrast three different design choices to implement site collections. These tables are intended to help you understand the consequences of each approach and how configuration varies depending on the architecture.
The following two tables contrast three different design choices to implement si
|&nbsp;|Host-named site collections with all sites in a farm consolidated in one web application|Path-based site collections with alternate access mapping and multiple web applications|Host-named site collections with multiple web applications in a farm| |:--|:--|:--|:--| |Site collection provisioning|Use Microsoft PowerShell or a custom site collection provisioning solution to provision sites.|Use Central Administration or Microsoft PowerShell to deploy sites.|Use Microsoft PowerShell or a custom site collection provisioning solution to provision sites.|
-|URL management|You can map all site collections in DNS to point to a single IP address which represents the web application.|If you implemented more than one zone, you configure alternate access mapping for each site URL. Each zone also requires a mapping in DNS.|Additional configuration is required to ensure that requests for sites that share the same port are mapped to the correct web application. Each unique host name also requires a mapping in DNS. This configuration is manual and you must complete it on each web server in a farm for each site.|
-|Additional URLs|You can assign up to five URLs to a host-named site collection, one per zone. It is not necessary to extend the web application to multiple zones. If a zone is not implemented the default zone is used.|The number of URLs for a site collection is limited to five because this is the number of zones that is allowed.|You can assign up to five URLs to a host-named site collection, one per zone. It is not necessary to extend the web application to multiple zones. If a zone is not implemented the default zone is used.|
+|URL management|You can map all site collections in DNS to point to a single IP address that represents the web application.|If you implemented more than one zone, you configure alternate access mapping for each site URL. Each zone also requires a mapping in DNS.|Extra configuration is required to ensure that requests for sites that share the same port are mapped to the correct web application. Each unique host name also requires a mapping in DNS. This configuration is manual and you must complete it on each web server in a farm for each site.|
+|More URLs|You can assign up to five URLs to a host-named site collection, one per zone. It's not necessary to extend the web application to multiple zones. If a zone isn't implemented, the default zone is used.|The number of URLs for a site collection is limited to five because the allowed number of zones is five.|You can assign up to five URLs to a host-named site collection, one per zone. It's not necessary to extend the web application to multiple zones. If a zone isn't implemented, the default zone is used.|
|Service applications|All sites in the farm use a single service application group.|You can implement custom service application groups for different web applications.|You can implement custom service application groups for different web applications.|
-|Zones|You do not have to implement multiple zones to implement different URLs for the same site collection. If a zone is not implemented the default zone is used.|Zones are necessary to implement different URLs for the same site collection.|You do not have to implement multiple zones to implement different URLs for the same site collection. If a zone is not implemented the default zone is used.|
+|Zones|You don't have to implement multiple zones to implement different URLs for the same site collection. If a zone isn't implemented, the default zone is used.|Zones are necessary to implement different URLs for the same site collection.|You don't have to implement multiple zones to implement different URLs for the same site collection. If a zone isn't implemented, the default zone is used.|
|Authentication|With one web application, authentication options are limited to five zones. However, you can implement many authentication methods on one zone.|You can implement different authentication and zone designs for each web application.|You can implement different authentication and zone designs for each web application.| |Authentication|Provides client scripting isolation between domain URLs.|You can isolate web applications into dedicated application pools, if desired, to achieve process isolation. <br/> Provides isolation between domain URLs.|You can isolate web applications into dedicated application pools, if desired, to achieve process isolation. <br/> Provides isolation between domain URLs.| |Policy|You can use zones to assign different policies to host-named sites.|You can use policies at the web application level to enforce permissions, regardless of permissions that are configured on individual sites or documents. Additionally, you can implement different policies for different zones.|You can implement different policies for different web applications to enforce permissions, regardless of permissions that are configured on individual sites or documents. <br/> Additionally, you can implement different policies for different zones.|
The following table summarizes the configuration that is necessary to manage URL
|&nbsp;|Host-named site collections with all sites in a farm consolidated into one web application|Path-based site collections with alternate access mapping and multiple web applications|Host-named site collections with multiple web applications in a farm| |:--|:--|:--|:--|
-|Within SharePoint Server|Create the web application. <br/> Create a root-site collection that is not accessible to users (for example, `https://HNSC01.fabrikam.com`). <br/> Create the host-named site collections with the host header (for example, `https://intranet.fabrikam.com`). <br/> Optionally add more URLs for each site collection and configure zones by using **Set-SPSiteUrl**. (In corporate portal design samples there's no need because there's only one zone.)|Create the web application with the host header (for example, `https://intranet.fabrikam.com`). <br/> Optionally configure alternate access mapping. In the design sample there's no need because there's only one zone). <br/> Create the root path-based site collection.|Create the web application. <br/> Create a root-site collection that is not accessible to users (for example, `https://HNSC01.fabrikam.com`). <br/> Create the host-named site collections with the host header (for example, `https://intranet.fabrikam.com`). <br/> Optionally add more URLs for each site collection and configure zones by using **Set-SPSiteUrl**. (In corporate portal design samples there's no need because there's only one zone.)|
-|Within IIS|Associate an SSL certificate (wildcard certificate or SAN certificate) for all host-named site (domain) in the web application.|Associate an SSL certificate in IIS for each zone (each zone is a separate web application in IIS).|Associate an SSL certificate (wildcard certificate or SAN certificate) for a host-named site (domain) in the web applications. <br/> On each web server in the farm and for each web application that shares a port: <br/> Configure a separate IP address to represent each web application. <br/> Edit the IIS web site binding manually to remove the host header binding that was created when the web application was created and replace this with an IP address binding.|
+|Within SharePoint Server|Create the web application. <br/> Create a root-site collection that isn't accessible to users (for example, `https://HNSC01.fabrikam.com`). <br/> Create the host-named site collections with the host header (for example, `https://intranet.fabrikam.com`). <br/> Optionally add more URLs for each site collection and configure zones by using **Set-SPSiteUrl**. (In corporate portal design samples there's no need because there's only one zone.)|Create the web application with the host header (for example, `https://intranet.fabrikam.com`). <br/> Optionally configure alternate access mapping. In the design sample, there's no need because there's only one zone). <br/> Create the root path-based site collection.|Create the web application. <br/> Create a root-site collection that isn't accessible to users (for example, `https://HNSC01.fabrikam.com`). <br/> Create the host-named site collections with the host header (for example, `https://intranet.fabrikam.com`). <br/> Optionally add more URLs for each site collection and configure zones by using **Set-SPSiteUrl**. (In corporate portal design samples there's no need because there's only one zone.)|
+|Within IIS|Associate an SSL certificate (wildcard certificate or SAN certificate) for all host-named site (domain) in the web application.|Associate an SSL certificate in IIS for each zone (each zone is a separate web application in IIS).|Associate an SSL certificate (wildcard certificate or SAN certificate) for a host-named site (domain) in the web applications. <br/> On each web server in the farm and for each web application that shares a port: <br/> Configure a separate IP address to represent each web application. <br/> Edit the IIS web site binding manually to remove the host header binding that was created when the web application was created and replace this binding with an IP address binding.|
-If you use multiple web applications on different IP addresses, you might need to complete additional configuration for the NIC, DNS, and the load balancer for each server.
+If you use multiple web applications on different IP addresses, you might need to complete extra configuration for the NIC, DNS, and the load balancer for each server.
### Create multiple web applications with host-named site collections <a name="section4a"> </a>
If you use multiple web applications on different IP addresses, you might need t
To run multiple web applications on the same server and port in combination with host-named site collections, you have to assign different IP addresses to the web applications. This type of architecture requires that you add IP addresses to the web servers and configure the network router to point host names to the IP address of its web application. > [!NOTE]
-> You can create a web application that does not have a host header. If you create a web application that does not have a host header, you cannot create multiple web applications with host-named site collections on the same web server.
+> You can create a web application that doesn't have a host header. If you create a web application that doesn't have a host header, you can't create multiple web applications with host-named site collections on the same web server.
-The process that creates multiple web applications for a host-named site collections includes the following tasks:
+The process that creates multiple web applications for a host-named site collection includes the following tasks:
- Create the multiple web applications.
SharePoint Overview Of Managed Navigation https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/overview-of-managed-navigation.md
description: "Learn about managed navigation and navigation term sets for ShareP
[!INCLUDE[appliesto-2013-2016-2019-SUB-xxx-md](../includes/appliesto-2013-2016-2019-SUB-xxx-md.md)].
-The managed navigation feature in SharePoint Server enables you to build navigation for a publishing site that is derived from a SharePoint Server managed metadata taxonomy. In SharePoint Server 2010, by default, you could base navigation only on the structure of a site. To create site navigation based on any data structure, you had to create a custom navigation provider. By using managed navigation, you can design site navigation around important business concepts. Managed navigation also lets you create friendly URLs without changing the structure of your site. In SharePoint Server 2010, all publishing site URLs contained a reference to the Pages library and any folders within that library ΓÇö for example, http://contoso.com/Pages/AboutUs.aspx. In SharePoint Server 2016 and SharePoint Server 2013, you can create URLs that are better for Search Engine Optimization (SEO), and easier for site visitors to read ΓÇö for example, http://contoso.com/AboutUs. Managed navigation is not available in SharePoint Foundation 2013.
+The managed navigation feature in SharePoint Server enables you to build navigation for a publishing site that's derived from a SharePoint Server managed metadata taxonomy. In SharePoint Server 2010, by default, you could base navigation only on the structure of a site. To create site navigation based on any data structure, you had to create a custom navigation provider. By using managed navigation, you can design site navigation around important business concepts. Managed navigation also lets you create friendly URLs without changing the structure of your site. In SharePoint Server 2010, all publishing site URLs contained a reference to the Pages library and any folders within that libraryΓÇöfor example, `https://contoso.com/Pages/AboutUs.aspx`. In SharePoint Server 2016 and SharePoint Server 2013, you can create URLs that are better for Search Engine Optimization (SEO), and easier for site visitors to readΓÇöfor example, `https://contoso.com/AboutUs`. Managed navigation isn't available in SharePoint Foundation 2013.
This article describes the key elements of the managed navigation feature, its uses and benefits, how it works, how terms can be used in other locations, limitations of the feature, and includes examples of how managed navigation can be used in a publishing site.
The navigation term set is the backbone of the managed navigation feature. By de
> [!NOTE] > If automatic term creation is enabled, a new term will only be created if you choose **Add a page** on the **Settings** menu. Adding a page by using the **New Document** button on the **Files** tab in the ribbon does not create a new term in the navigation term set.
-Each term in a navigation term set has a friendly URL that loads a physical page in the context of that term. Terms in the navigation term set can be configured to do one of the following:
+Each term in a navigation term set has a friendly URL that loads a physical page in the context of that term. Terms in the navigation term set can be configured to do one of the following tasks:
- Point to the same page as other terms
If you use cross-site publishing, you must use a tagging term set on the authori
Target pages display page content, and are associated with terms and friendly URLs. You can change the default target pages that are used by the term and any child terms.
-When you use cross-site publishing, target pages are also known as category pages. A category page is a special page that can be automatically created when you connect a publishing site to a catalog. You can also create category pages by hand. The category page contains a Content Search Web Part that uses a term from the navigation term set to query for and dynamically display catalog content associated with the current navigation term. This enables you to use the same page repeatedly to display different content, based on the associated navigation term selected by the page visitor. For example, let's say you use cross-site publishing to display electronic products from a catalog. The category page that is used to show a list of products that use the navigation term Cameras is the same page that is also used to display a list of products that use the navigation term Printers. For more information about Content Search Web Parts, see [Plan publishing sites for cross-site publishing in SharePoint Server](plan-sharepoint-publishing-sites-for-cross-site-publishing.md).
+When you use cross-site publishing, target pages are also known as category pages. A category page is a special page that can be automatically created when you connect a publishing site to a catalog. You can also create category pages by hand. The category page contains a Content Search Web Part that uses a term from the navigation term set to query for and dynamically display catalog content associated with the current navigation term. This web part enables you to use the same page repeatedly to display different content based on the associated navigation term selected by the page visitor. For example, let's say you use cross-site publishing to display electronic products from a catalog. The category page that shows a list of products that use the navigation term Cameras is the same page that displays a list of products that use the navigation term Printers. For more information about Content Search Web Parts, see [Plan publishing sites for cross-site publishing in SharePoint Server](plan-sharepoint-publishing-sites-for-cross-site-publishing.md).
-A catalog-item page is also a special page that can be automatically created when you connect a publishing site to a catalog. Whereas a category page displays a set of items that match the current navigation term (for example, Laptops), the catalog-item page returns the details for a single item (for example, when a user chooses a specific model on the Laptops category page). The catalog-item page contains a Catalog-Item Reuse Web Part that uses the ID for a specific item that was returned in the results of a Content Search Web Part on a category page to show the details for the item. The ID is the set of primary key properties specified when the publishing site connects to the catalog. Catalog-item pages can be configured only when a site uses cross-site publishing and is connected to a catalog. For example, the URL http://contoso.com/cameras might contain a list of available camera models. If you click the link for the individual product Contoso Digital Camera M200, the catalog-item page displays specific information about that particular camera. Similar to the category page, the catalog-item page enables you to show different items without having to create a different page for each item in the catalog. You use the same page but it shows different content based on the selected item from a result set.
+A catalog-item page is also a special page that can be automatically created when you connect a publishing site to a catalog. Whereas a category page displays a set of items that match the current navigation term (for example, Laptops), the catalog-item page returns the details for a single item (for example, when a user chooses a specific model on the Laptops category page). The catalog-item page contains a Catalog-Item Reuse Web Part that uses the ID for a specific item that was returned in the results of a Content Search Web Part on a category page to show the details for the item. The ID is the set of primary key properties specified when the publishing site connects to the catalog. Catalog-item pages can be configured only when a site uses cross-site publishing and is connected to a catalog. For example, the URL `https://contoso.com/cameras` might contain a list of available camera models. If you click the link for the individual product Contoso Digital Camera M200, the catalog-item page displays specific information about that particular camera. Similar to the category page, the catalog-item page enables you to show different items without having to create a different page for each item in the catalog. You use the same page but it shows different content based on the selected item from a result set.
For more information about category pages and catalog-item pages, see "Publishing site collections for SharePoint cross-site publishing" in [Overview of cross-site publishing in SharePoint Server](overview-of-cross-site-publishing.md). ### Friendly URLs
-Friendly URLs are URLs that correspond to a term in the navigation term set, and that provide a shorter, more meaningful URL to a page. This makes the URL more useful to visitors to your site, and also improves search engine optimization (SEO) for your site. For example, the URL http://www.contoso.com/products/household/vacuum-cleaner is more meaningful to both users and search engines than the URL http://www.contoso.com/Products/Inventory/Pages/productViewer.aspx?productID=115&amp;name=vacuum%20cleaner&amp;CID=34q327234ef. By default, when you create a new page, a new navigation term is created, and a corresponding friendly URL is created for the page. You can use a single friendly URL to point to a single page. You can also have multiple friendly URLs that point to the same page, such as a category page. For example, if you use cross-site publishing to display content from a knowledge base, you can have separate friendly URLs for /kb/manuals, /kb/troubleshooting-guides, and /kb/product-specs that all point to the same category page, Category-KB-Articles.aspx. You do not have to use cross-site publishing to use multiple friendly URLs that point to the same page.
+Friendly URLs are URLs that correspond to a term in the navigation term set, and that provide a shorter, more meaningful URL to a page. This short and meaningful URL is more useful to visitors to your site and also improves search engine optimization (SEO) for your site. For example, the URL `https://www.contoso.com/products/household/vacuum-cleaner` is more meaningful to both users and search engines than the URL `https://www.contoso.com/Products/Inventory/Pages/productViewer.aspx?productID=115&amp;name=vacuum%20cleaner&amp;CID=34q327234ef`. By default, when you create a new page, a new navigation term is created, and a corresponding friendly URL is created for the page. You can use a single friendly URL to point to a single page. You can also have multiple friendly URLs that point to the same page, such as a category page. For example, if you use cross-site publishing to display content from a knowledge base, you can have separate friendly URLs for /kb/manuals, /kb/troubleshooting-guides, and /kb/product-specs that all point to the same category page, Category-KB-Articles.aspx. You don't have to use cross-site publishing to use multiple friendly URLs that point to the same page.
### Global navigation and current navigation controls
The global navigation control (called Top Navigation in the Snippet Gallery) is
## How managed navigation works in SharePoint Server <a name="section2"> </a>
-Managed navigation works by associating a term from a navigation term set with a friendly URL and a page in the Pages library. By default, when a new page is created, a new term is created in the navigation term set, and a friendly URL is configured that points to the page. If you are using a standard publishing site that uses the author-in-place publishing model, this means that you'll probably have a 1:1 relationship between pages that are created in the site and terms in the navigation term set. Managing many terms and their corresponding pages can become difficult if your site has many pages. By using cross-site publishing to show content from one or more catalogs, you can use a few category and catalog-item pages to easily display lots of data with minimal configuration and page management. By using managed navigation, you can change the navigation term set and have those changes appear on your site without having to add new pages or change the physical structure of the site and its content.
+Managed navigation works by associating a term from a navigation term set with a friendly URL and a page in the Pages library. By default, when a new page is created, a new term is created in the navigation term set, and a friendly URL is configured that points to the page. If you're using a standard publishing site that uses the author-in-place publishing model, this default behavior means that you'll probably have a 1:1 relationship between pages that are created in the site and terms in the navigation term set. Managing many terms and their corresponding pages can become difficult if your site has many pages. By using cross-site publishing to show content from one or more catalogs, you can use a few category and catalog-item pages to easily display lots of data with minimal configuration and page management. By using managed navigation, you can change the navigation term set and have those changes appear on your site without having to add new pages or change the physical structure of the site and its content.
-Before you can use managed navigation, it must be configured in Navigation Settings on the site collection. By default, managed navigation is enabled for site collections that are created by using the Publishing Portal or the Enterprise Wiki site collection templates. On the other hand, the Product Catalog site collection template uses structural navigation because it is intended to be used as a source for catalogs that will be shared with a publishing site for cross-site publishing. When managed navigation is configured, two additional settings are also configured: new pages are automatically added to navigation, and friendly URLs are automatically created for new pages. If you turn off both settings, new pages will not be added to the navigation, and no new terms will be added to the Site Navigation term set.
+Before you can use managed navigation, it must be configured in Navigation Settings on the site collection. By default, managed navigation is enabled for site collections that are created by using the Publishing Portal or the Enterprise Wiki site collection templates. On the other hand, the Product Catalog site collection template uses structural navigation because it's intended to be used as a source for catalogs that will be shared with a publishing site for cross-site publishing. When managed navigation is configured, two more settings are also configured: new pages are automatically added to navigation, and friendly URLs are automatically created for new pages. If you turn off both settings, new pages won't be added to the navigation, and no new terms will be added to the Site Navigation term set.
> [!NOTE] > To enable managed navigation for a non-publishing site, you must activate the SharePoint Server Publishing Infrastructure feature for the site collection, and activate the SharePoint Server Publishing feature for the site.
You should use managed navigation with any publishing site in which you want the
**Table: SharePoint managed navigation scenarios**
-|**Scenario**|**Description**|
+| Scenario | Description |
|:--|:--|
-|Internet business site <br/> |You can use cross-site publishing to create an Internet business site that contains a catalog that shows products to customers based on metadata. Users view pages that are created dynamically based on navigation, and users can filter results by using additional refiners. For more information, see "Plan refiners and faceted navigation" in [Plan search for cross-site publishing sites in SharePoint Server 2016](plan-search-for-sharepoint-cross-site-publishing-sites.md). <br/> |
+|Internet business site <br/> |You can use cross-site publishing to create an Internet business site that contains a catalog that shows products to customers based on metadata. Users view pages that are created dynamically based on navigation, and users can filter results by using more refiners. For more information, see "Plan refiners and faceted navigation" in [Plan search for cross-site publishing sites in SharePoint Server 2016](plan-search-for-sharepoint-cross-site-publishing-sites.md). <br/> |
|Intranet site <br/> |You can use cross-site publishing to create an internal Human Resources (HR) website that uses a tightly managed navigation structure to show authored content. <br/> | |Internet presence site <br/> |You can use author-in-place publishing to create an Internet Presence site where pages are automatically added to the managed navigation. Content authors can configure navigation properties directly from the pages they create. <br/> |
This section provides examples of how you can use term sets, tagging term sets,
### Simple managed navigation
-In the simplest form of managed navigation, every term in the navigation term set corresponds to a page in the site. Site navigation controls reflect the order and the hierarchy of terms in the navigation term set. To change the "structure" of your site ΓÇö the way the structure appears as displayed in the navigation controls ΓÇö you simply rearrange terms in the navigation term set.
+In the simplest form of managed navigation, every term in the navigation term set corresponds to a page in the site. Site navigation controls reflect the order and the hierarchy of terms in the navigation term set. To change the "structure" of your siteΓÇöthe way the structure appears as displayed in the navigation controlsΓÇöyou rearrange terms in the navigation term set.
For example, consider a structure that's common to many public websites. A global navigation menu is displayed horizontally across the top of the page. The global navigation menu has entries for the highest level of information that's contained on the site. In this example, the global navigation menu contains the following entries:
Cross-site publishing is available only in SharePoint Server Enterprise. If your
You can add tagging terms either by pinning them or by reusing them. A pinned term is essentially a link. If you change the term in the tagging term set, the changes also apply to the pinned term in the navigation term set. You can pin only a term, or you can pin a term and all of its sub-terms. A reused term is essentially a copy. No association is maintained between the tagging term and the reused navigation term.
-Returning to the example, assume that the publishing site uses cross-site publishing. There is an authoring site that has a tagging term set with the following hierarchy of terms:
+Returning to the example, assume that the publishing site uses cross-site publishing. There's an authoring site that has a tagging term set with the following hierarchy of terms:
- Cameras
If a visitor to the site selects the **Cameras** entry on the global navigation
- Film
-The navigation term set that represents this structure is the following:
+The navigation term set that represents this structure is:
- Products
You define the page that is generated by setting attributes on the term in the n
When you use cross-site publishing, there are two ways to use terms from an authoring site collection as navigation terms in a publishing site collection: you can pin terms or reuse terms.
-When you pin a term from a tagging term set in an authoring site collection into the site navigation of a publishing site collection, that term is shared with the navigation term set in the publishing site collection. Any changes that you make to the original term in the authoring site collection will be reflected anywhere that term is pinned. You can't change the general settings for a term in the publishing site collection where the term is pinned. You also can't add shared properties to the term from the publishing site collection. However, you can add local properties to the term. You can pin a single term, or you can pin a term with all its child terms.
+You can share a term with the navigation term set in the publishing site collection by pinning it from a tagging term set in an authoring site collection into the site navigation of a publishing site collection. Any changes that you make to the original term in the authoring site collection will be reflected anywhere that term is pinned. You can't change the general settings for a term in the publishing site collection where the term is pinned. You also can't add shared properties to the term from the publishing site collection. However, you can add local properties to the term. You can pin a single term, or you can pin a term with all its child terms.
-When you reuse a term from a tagging term set in an authoring site collection into the site navigation of a publishing site, that term is copied to the navigation term set in the publishing site collection and no association with the original term is maintained. Any changes that you make to the original term in the authoring site collection are not made on any reused copies of the term. You can change the general settings for the reused term in the publishing site collection. You can also add both shared and local properties to the term from the publishing site collection. You can reuse a single term, or a term with all its child terms.
+You can copy a term into the navigation term set in the publishing site collection. This task can be done by reusing it from a tagging term set in an authoring site collection into the site navigation of a publishing site. No association with the original term is maintained. Any changes that you make to the original term in the authoring site collection aren't made on any reused copies of the term. You can change the general settings for the reused term in the publishing site collection. You can also add both shared and local properties to the term from the publishing site collection. You can reuse a single term, or a term with all its child terms.
## Limitations of managed navigation in SharePoint Server <a name="section6"> </a> Because managed navigation uses term sets to build the site navigation, it has the same limitations as any other term set: -- There is no version control on terms. If you make a change to a term, you can't later revert the change back to an earlier version of the term.
+- There's no version control on terms. If you make a change to a term, you can't later revert the change back to an earlier version of the term.
-- There is no publishing workflow on terms. As soon as you make a change to a term, it will appear in the navigation with the change. If you are using cross-site publishing, this also means that when a new term is added to the navigation term set, the term itself may be visible in the navigation on the publishing site before the associated content is indexed by search. You can choose to hide terms from the navigation until the content is published and indexed by search.
+- There's no publishing workflow on terms. As soon as you make a change to a term, it will appear in the navigation with the change. Thus when you use cross-site publishing, a new term added to the navigation term set may be visible in the navigation on the publishing site before the associated content is indexed by search. You can choose to hide terms from the navigation until the content is published and indexed by search.
## See also <a name="section6"> </a>
SharePoint Plan Sharepoint Authoring Sites For Cross Site Publishing https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/plan-sharepoint-authoring-sites-for-cross-site-publishing.md
description: "Learn how to plan authoring site collections for a SharePoint Serv
[!INCLUDE[appliesto-2013-2016-2019-SUB-xxx-md](../includes/appliesto-2013-2016-2019-SUB-xxx-md.md)]
-When you use cross-site publishing in SharePoint Server, you use one or more authoring site collections for authoring and storing content, and one or more publishing site collections to control the design of the site and show content. This article describes how to plan authoring sites for your cross-site publishing solution.
+Cross-site publishing in SharePoint Server allows you to use:
+
+- One or more authoring site collections for authoring and storing content
+- One or more publishing site collections to control the design of the site and show content.
+
+This article describes how to plan authoring sites for your cross-site publishing solution.
-This article builds on the information in [Overview of cross-site publishing in SharePoint Server](overview-of-cross-site-publishing.md). After you finish reading this article, make sure that you read the next article, [Plan publishing sites for cross-site publishing in SharePoint Server](plan-sharepoint-publishing-sites-for-cross-site-publishing.md).
+This article builds on the information in [Overview of cross-site publishing in SharePoint Server](overview-of-cross-site-publishing.md). After you finish reading this article, make sure you read the next article, [Plan publishing sites for cross-site publishing in SharePoint Server](plan-sharepoint-publishing-sites-for-cross-site-publishing.md).
## Plan site collections and site structure for SharePoint authoring sites <a name="BKMK_SiteStructure"> </a>
-Authoring site collections must have the SharePoint Server Cross-Site Collection Publishing feature activated. We recommend that you use the Product Catalog Site Collection template to create authoring site collections because the Cross-Site Collection Publishing feature is activated by default when you use that template. If you use a site collection template that does not have the Cross-Site Collection Publishing feature activated, you must activate it. Additionally, if you use a site collection template, such as the Team Site template, that does not create a publishing site, and you want to use publishing features such as Approval workflows and scheduling, you must also activate those publishing features. For information about activating the Cross-Site Publishing feature, see "Activate the Cross-Site Collection Publishing feature" in [Configure cross-site publishing in SharePoint Server](configure-cross-site-publishing.md). For more information about how to use the publishing features on a site that is not a publishing site, see [Publishing features overview (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/ff628963(v=office.14)). For information about how to activate the publishing features, see [Enable publishing features](https://go.microsoft.com/fwlink/p/?LinkId=261798). For more information about how to design the logical architecture for a cross-site publishing solution, see [Plan the logical architecture for cross-site publishing in SharePoint Server](plan-the-logical-architecture-for-cross-site-publishing.md).
+Authoring site collections must have the SharePoint Server Cross-Site Collection Publishing feature activated. We recommend that you use the Product Catalog Site Collection template to create authoring site collections because the Cross-Site Collection Publishing feature is activated by default when you use that template. If you use a site collection template that doesn't have the Cross-Site Collection Publishing feature activated, you must activate it. Additionally, if you use a site collection template, such as the Team Site template, that doesn't create a publishing site, and you want to use publishing features such as Approval workflows and scheduling, you must also activate those publishing features. For information about activating the Cross-Site Publishing feature, see "Activate the Cross-Site Collection Publishing feature" in [Configure cross-site publishing in SharePoint Server](configure-cross-site-publishing.md). For more information about how to use the publishing features on a site that isn't a publishing site, see [Publishing features overview (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/ff628963(v=office.14)). For information about how to activate the publishing features, see [Enable publishing features](https://go.microsoft.com/fwlink/p/?LinkId=261798). For more information about how to design the logical architecture for a cross-site publishing solution, see [Plan the logical architecture for cross-site publishing in SharePoint Server](plan-the-logical-architecture-for-cross-site-publishing.md).
Because cross-site publishing separates the authoring and publishing environments, the structure of an authoring site can differ from the structure of the publishing site. As you plan how to structure authoring sites, consider the questions in the following list.
Because cross-site publishing separates the authoring and publishing environment
- You can use variations and translation with a Pages library to create multilingual content.
- - You can use the Approval workflow to route Pages library content for review and approval. The search system will not index pages that are not approved for publishing because they are not marked as major versions until they are published.
+ - You can use the Approval workflow to route Pages library content for review and approval. The search system won't index pages that aren't approved for publishing because they aren't marked as major versions until they're published.
- - You can use scheduling to specify when content will be available. The search system will not index pages that have not been scheduled for publishing. This is because pages are not marked as major versions until they are published.
+ - You can use scheduling to specify when content will be available. The search system won't index pages that haven't been scheduled for publishing. This restriction on indexing is because pages aren't marked as major versions until they're published.
- **How many Pages libraries do you have to have?**
- The primary drawback to using a Pages library is that you can have only one Pages library per site. Depending on how much Pages content you plan to create, a single, large catalog can be difficult to consume on publishing sites because the queries that show content are more complex and time-consuming to configure. Accordingly, when you plan Pages content, consider how much content you will create and whether the content should be stored together. If you want to store Pages content in separate catalogs, you must create separate sites within the authoring site collection hierarchy, and then share the Pages library in each site as a catalog. You can then connect to these catalogs from one or more publishing sites.
+ The primary drawback to using a Pages library is that you can have only one Pages library per site. Depending on how much Pages content you plan to create, a single, large catalog can be difficult to consume on publishing sites because the queries that show content are more complex and time-consuming to configure. Accordingly, when you plan Pages content, consider how much content you'll create and whether the content should be stored together. If you want to store Pages content in separate catalogs, you must create separate sites within the authoring site collection hierarchy, and then share the Pages library in each site as a catalog. You can then connect to these catalogs from one or more publishing sites.
- For example, in an intranet scenario in which you have a knowledge base site, you might want to keep troubleshooting articles separate from user manuals because they are authored by different groups of people. In the authoring site collection, you create one site to store troubleshooting articles in its Pages library, and another site to store user manuals in its Pages library. After you share both Pages libraries as catalogs, you can connect to them both from the same publishing site, and show the two types of content by using different Web Parts.
+ For example, in an intranet scenario in which you have a knowledge base site, you might want to keep troubleshooting articles separate from user manuals because they're authored by different groups of people. In the authoring site collection, you create one site to store troubleshooting articles in its Pages library, and another site to store user manuals in its Pages library. After you share both Pages libraries as catalogs, you can connect to them both from the same publishing site, and show the two types of content by using different Web Parts.
- **How many authoring site collections do you have to have?**
- In addition to deciding how many sites you must have in a single authoring site collection, you should also consider whether you have to have additional authoring site collections. You might use more than one authoring site collection if the content authors are in separate groups that have different security requirements, or are in separate geographical locations. For example, in an extranet scenario, you might use one authoring site collection for internal content authors who belong to a specific group in Active Directory Domain Services (AD DS), and a separate authoring site collection for external content authors who connect to the site by using forms-based authentication. Catalogs can be shared across web applications and farms so that you do not have to restrict authoring sites to a single web application or farm. Decide how many authoring site collections you must have, and then plan which catalogs to include in each site.
+ In addition to deciding how many sites you must have in a single authoring site collection, you should also consider whether you need to have more authoring site collections. You might use more than one authoring site collection if the content authors are in separate groups that have different security requirements, or are in separate geographical locations. For example, in an extranet scenario, you might use one authoring site collection for internal content authors who belong to a specific group in Active Directory Domain Services (AD DS), and a separate authoring site collection for external content authors who connect to the site by using forms-based authentication. Catalogs can be shared across web applications and farms so that you don't have to restrict authoring sites to a single web application or farm. Decide how many authoring site collections you must have, and then plan which catalogs to include in each site.
- **Do you plan to use variations to create multilingual content?**
- Do you have to provide content in more than one language? Even if you currently plan to only create and publish content in a single language, consider whether that business requirement might change in the future. If you might eventually want to use variations on the site, you should plan for using variations now. By setting up the site structure now to accommodate variations, you can save yourself and your organization time and resources in the future. If you have to change the site structure when you switch to using variations later, it is often more difficult and can affect the URLs that you planned for your sites. If you plan to use variations and cross-site publishing, each variation label has to be created as a separate site within the authoring site collection. You share the Pages library from each variation site as a catalog, and then you connect each publishing site collection to the catalog that matches its locale. For more information about variations, see [Variations overview in SharePoint Server](variations-overview.md). For more information about how to plan variation sites, see [Plan variations for multilingual cross-site publishing site in SharePoint Server](plan-variations-for-multilingual-cross-site-publishing-site.md).
+ Do you have to provide content in more than one language? Even if you currently plan to only create and publish content in a single language, consider whether that business requirement might change in the future. If you might eventually want to use variations on the site, you should plan for using variations now. By setting up the site structure now to accommodate variations, you can save yourself and your organization time and resources in the future. If you have to change the site structure when you switch to using variations later, it's often more difficult and can affect the URLs you planned for your sites. If you plan to use variations and cross-site publishing, each variation label has to be created as a separate site within the authoring site collection. You share the Pages library from each variation site as a catalog, and then you connect each publishing site collection to the catalog that matches its locale. For more information about variations, see [Variations overview in SharePoint Server](variations-overview.md). For more information about how to plan variation sites, see [Plan variations for multilingual cross-site publishing site in SharePoint Server](plan-variations-for-multilingual-cross-site-publishing-site.md).
- **What kind of navigation do you have to have on the authoring site?**
- Although you can use managed navigation on the authoring site so that the authoring site resembles the publishing site, this can confuse content authors. We recommend that you use structured navigation on the authoring site to make it easier for authors to create content. Consider the kind of content that will be created and stored on the authoring site. Will most content be HTML content that is stored in the Pages library? Or will you manually create or import list data? If you keep a simple structure for the authoring site and any lists and libraries, it makes it easier for content authors to create content.
+ Although you can use managed navigation on the authoring site so that the authoring site resembles the publishing site, this usage of managed navigation can confuse content authors. We recommend that you use structured navigation on the authoring site to make it easier for authors to create content. Consider the kind of content that will be created and stored on the authoring site. Will most content be HTML content that is stored in the Pages library? Or will you manually create or import list data? If you keep a structure for the authoring site and any lists and libraries, it makes it easier for content authors to create content.
## Plan security for SharePoint authoring sites <a name="BKMK_Security"> </a>
You plan security for authoring sites in the same way that you do for most other
For information about security, see [Permissions planning for sites and content in SharePoint Server](../sites/permissions-planning-for-sites-and-content.md).
-When you enable anonymous access for a catalog, security on the authoring site can be treated independently from how it is represented in search. When anonymous access is enabled, indexed content is searchable and viewable to anonymous users on the publishing site. However, if you change permissions to individual items in the catalog, those permissions are respected by the search system, and any items that are restricted to certain groups will not be available to anonymous users. This allows for greater flexibility when you plan to share content with anonymous users.
+When you enable anonymous access for a catalog, security on the authoring site can be treated independently from how it's represented in search. When anonymous access is enabled, indexed content is searchable and viewable to anonymous users on the publishing site. However, if you change permissions to individual items in the catalog, those permissions are respected by the search system, and any items that are restricted to certain groups won't be available to anonymous users. This specificity in permissions allows for greater flexibility when you plan to share content with anonymous users.
-You must also plan to grant the crawler access to content on authoring site collections. The crawler uses a default content access account. If the default content access account does not have at least Read permission level to content, the content is not indexed and is not available to queries on publishing site collections. You can use the default content access account, or you can use crawl rules to specify a different content access account to use when crawling particular content. For more information, see "Plan crawler authentication" in [Plan crawling and federation in SharePoint Server](../search/plan-crawling-and-federation.md).
+You must also plan to grant the crawler access to content on authoring site collections. The crawler uses a default content access account. If the default content access account doesn't have at least Read permission level to content, the content isn't indexed and isn't available to queries on publishing site collections. You can use the default content access account, or you can use crawl rules to specify a different content access account to use when crawling particular content. For more information, see "Plan crawler authentication" in [Plan crawling and federation in SharePoint Server](../search/plan-crawling-and-federation.md).
## Plan design and branding for SharePoint authoring sites <a name="BKMK_Design"> </a>
-As was mentioned earlier in this article, the structure of the authoring sites can differ from the structure of publishing sites. Likewise, the appearance of those sites can also be very different. If you want content authors to have a WYSIWYG user experience on the authoring site, you can use similar master pages, page layouts, and cascading style sheets to design the authoring site. However, the actual publishing sites might have different designs because of branding or other requirements. Therefore, the authoring site will not provide a complete WYSIWYG experience.
+As was mentioned earlier in this article, the structure of the authoring sites can differ from the structure of publishing sites. Likewise, the appearance of those sites can also be different. If you want content authors to have a WYSIWYG user experience on the authoring site, you can use similar master pages, page layouts, and cascading style sheets to design the authoring site. However, the actual publishing sites might have different designs because of branding or other requirements. Therefore, the authoring site won't provide a complete WYSIWYG experience.
-Even if you do not plan to apply the same branding to the authoring site that you use on the publishing site, if you plan to use Pages library content, you still have to plan for the basic page layouts that authors will use. As you plan the design of the authoring site, consider the following questions:
+Even if you don't plan to apply the same branding to the authoring site that you use on the publishing site, if you plan to use Pages library content, you still have to plan for the basic page layouts that authors will use. As you plan the design of the authoring site, consider the following questions:
-- **What site columns must you have?** Site columns can be added as page fields to page layouts to hold additional content, such as managed metadata.
+- **What site columns must you have?** Site columns can be added as page fields to page layouts to hold more content, such as managed metadata.
- **What content types must you have?** You can create custom content types that use the Article Page content type as the parent content type. You can add site columns to the custom content type, which will be included as page fields in any page layouts that you create by using the custom content type.
For information about authoring web pages, see [SharePoint page model overview](
## Plan term sets for tagging content on SharePoint authoring sites <a name="BKMK_PlanTaggingTermSetsForAuthoringSites"> </a>
-You use term sets to tag catalog content such as pages or list items on the authoring site. By doing this, terms help categorize the content into a hierarchy. These same terms are later used on the publishing site to issue queries, show information about category and catalog item pages, create friendly URLs, and for managed navigation. When you plan the term sets and terms to use for tagging content, consider how you want the hierarchy structured. You can combine terms from more than one tagging term set into a single customized term set for navigation on the publishing site. You do not have to create a single, highly complex structure for the tagging term set on the authoring site. Also consider how you want the URLs to look on the publishing site, and plan to create terms that will help users find what they want. For example, if you have a level 1 term called Computers, and underneath that, a level 2 term called Laptops, and the catalog item name is CM61438, the friendly URL for the page that shows that model will be http://contoso.com/computers/laptops/CM61428. For more information, see [Plan terms and term sets in SharePoint Server 2013](/previous-versions/office/sharepoint-server-2010/ee519604(v=office.14)), and [Plan navigation term sets in SharePoint Server](plan-navigation-term-sets.md).
+You use term sets to tag catalog content such as pages or list items on the authoring site. By doing this tagging, terms help categorize the content into a hierarchy. These same terms are later used on the publishing site to issue queries, show information about category and catalog item pages, create friendly URLs, and for managed navigation. When you plan the term sets and terms to use for tagging content, consider how you want the hierarchy structured. You can combine terms from more than one tagging term set into a single customized term set for navigation on the publishing site. You don't have to create a single, highly complex structure for the tagging term set on the authoring site. Also consider how you want the URLs to look on the publishing site, and plan to create terms that will help users find what they want. For example, if you have a level 1 term called Computers, and underneath that term, a level 2 term called Laptops, and the catalog item name is CM61438, the friendly URL for the page that shows that model will be `https://contoso.com/computers/laptops/CM61428`. For more information, see [Plan terms and term sets in SharePoint Server 2013](/previous-versions/office/sharepoint-server-2010/ee519604(v=office.14)), and [Plan navigation term sets in SharePoint Server](plan-navigation-term-sets.md).
For information about creating term sets for tagging content, see "Create and manage term sets for tagging content on authoring sites" in [Configure cross-site publishing in SharePoint Server](configure-cross-site-publishing.md).
After you decide whether to store content in one or more Pages libraries, and ho
- **What term set will you associate with Pages library content?**
- If you use a Pages library, you must plan to add at least one managed metadata site column to a Page Layout Content Type, and link the site column to a tagging term set. When a content author creates a new page that uses that content type, they will be able to select a term with which to tag the page. For example, in the intranet knowledge base scenario, you might have a tagging term set that is named Article Types that contains separate terms for Troubleshooting Guides and for User Manuals. You can create a site column called Article Type that is linked to the Article Types term set, and add it to the Article Page content type. When a content author creates a new page, they must choose a term from the list of available Article Types terms. When the Pages library is shared as a catalog, you have to select that managed metadata column as the one to use as a navigation term set on the publishing sites. For more information, see [Plan term sets for tagging content on SharePoint authoring sites](plan-sharepoint-authoring-sites-for-cross-site-publishing.md#BKMK_PlanTaggingTermSetsForAuthoringSites) earlier in this article.
+ If you use a Pages library, you must plan to add at least one managed metadata site column to a Page Layout Content Type, and link the site column to a tagging term set. When a content author creates a new page that uses that content type, they'll be able to select a term with which to tag the page. For example, in the intranet knowledge base scenario, you might have a tagging term set that is named Article Types that contains separate terms for Troubleshooting Guides and for User Manuals. You can create a site column called Article Type that is linked to the Article Types term set, and add it to the Article Page content type. When a content author creates a new page, they must choose a term from the list of available Article Types terms. When the Pages library is shared as a catalog, you have to select that managed metadata column as the one to use as a navigation term set on the publishing sites. For more information, see [Plan term sets for tagging content on SharePoint authoring sites](plan-sharepoint-authoring-sites-for-cross-site-publishing.md#BKMK_PlanTaggingTermSetsForAuthoringSites) earlier in this article.
- **What other fields must you add to the Page Layout Content Type?**
- In addition to planning the tagging field for navigation, you should consider any other fields that you want to add to a Page Layout Content Type. These can be other managed metadata fields that are linked to other term sets, or other kinds of fields, such as hyperlinks, numbers, and dates and times. By default, publishing page content types contain a Page Content field. This lets content authors insert HTML and images onto a page by using a rich text editor. You can create different page layouts that contain different fields, based on the content that is created. For example, in the intranet knowledge base scenario, you can use a page layout for Troubleshooting Articles that contains fields such as Applies To or Article Number, whereas you can use a page layout for User Manuals that contains fields such as Product Name or Model Number. As you plan Pages library content, decide what other site columns and content types are needed, what page layouts are needed, and which fields should go in which page layout. For more information, see [SharePoint page model overview](/sharepoint/dev/general-development/overview-of-the-sharepoint-page-model).
+ In addition to planning the tagging field for navigation, you should consider any other fields that you want to add to a Page Layout Content Type. These fields can be other managed metadata fields that are linked to other term sets, or other kinds of fields, such as hyperlinks, numbers, and dates and times. By default, publishing page content types contain a Page Content field. This field lets content authors insert HTML and images onto a page by using a rich text editor. You can create different page layouts that contain different fields, based on the content that is created. For example, in the intranet knowledge base scenario, you can use a page layout for Troubleshooting Articles that contains fields such as Applies To or Article Number, whereas you can use a page layout for User Manuals that contains fields such as Product Name or Model Number. As you plan Pages library content, decide what other site columns and content types are needed, what page layouts are needed, and which fields should go in which page layout. For more information, see [SharePoint page model overview](/sharepoint/dev/general-development/overview-of-the-sharepoint-page-model).
For more information, see [Plan Web pages (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/cc263106(v=office.14)), and [Plan for large Pages libraries (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/ee721053(v=office.14)).
When you plan to use lists to maintain catalog content, consider the following q
- **How many lists do you want to use?**
- Depending on the structure of the data, consider using several lists for creating and maintaining catalog content. You should consider using several lists when the attributes that are used to represent catalog items vary greatly between the different categories of data. For example, attributes representing washing machines are very different from the attributes representing MP3 players. In this case, consider creating one list for washing machines, and another list for MP3 players.
+ Depending on the structure of the data, consider using several lists for creating and maintaining catalog content. You should consider using several lists when the attributes that are used to represent catalog items vary greatly between the different categories of data. For example, attributes representing washing machines are different from the attributes representing MP3 players. In this case, consider creating one list for washing machines, and another list for MP3 players.
- **Which site columns do you have to have to represent the catalog items?**
When you plan to use lists to maintain catalog content, consider the following q
- **Is the data that you will input into a list consistent?**
- You should also plan a strategy to make sure that catalog list data is consistent. Catalog list data is often maintained by different people over a long time, and this can increase the inconsistency of the data. For example, let's say that you have a site column named Color, and you want to import the color information for individual items from an external system. The values in the external system vary in how the color is written (BLUE, Blue, blue). Before you import this data into a SharePoint list, make sure that the data is consistent. For this example, you make sure that all color names are represented as Blue.
+ You should also plan a strategy to make sure catalog list data is consistent. Catalog list data is often maintained by different people over a long time, increasing the chances of inconsistency of the data. For example, let's say you have a site column named Color, and you want to import the color information for individual items from an external system. The values in the external system vary in how the color is written (BLUE, Blue, blue). Before you import this data into a SharePoint list, make sure the data is consistent. For this example, you make sure all color names are represented as Blue.
- In addition to guaranteeing data consistency, you should also make sure that the managed metadata field that is used to tag catalog content is a required field. Missing data from this field may cause content to appear incorrectly on the publishing site.
+ In addition to guaranteeing data consistency, you should also make sure the managed metadata field that's used to tag catalog content is a required field. Missing data from this field may cause content to appear incorrectly on the publishing site.
For information about how to create list content for cross-site publishing, see "Create catalog content by using SharePoint lists" in [Configure cross-site publishing in SharePoint Server](configure-cross-site-publishing.md).
For performance considerations, see [Designing large lists and maximizing list p
### Plan asset library content <a name="BKMK_PlanListContent"> </a>
-When you plan to use assets in content, remember what is and is not indexed. The search system indexes some fields, such as text and HTML fields, but does not index assets such as pictures, audio and video files, and files such as Word documents or PDFs. These files are considered binary large objects (BLOBs), and are stored in the BLOB cache, not in the search index. This means that they will not be shown on the publishing site in the same manner as other content. As you plan the asset library content for authoring sites, consider the questions in the following list.
+When you plan to use assets in content, remember what is and isn't indexed. The search system indexes some fields, such as text and HTML fields, but doesn't index assets such as pictures, audio and video files, and files such as Word documents or PDFs. These files are considered binary large objects (BLOBs), and are stored in the BLOB cache, not in the search index. This treatment means that these files won't be shown on the publishing site in the same manner as other content. As you plan the asset library content for authoring sites, consider the questions in the following list.
- **Where should the asset library be located?**
- To use assets in content, authoring site collections and publishing site collections must have access to the asset library. The location of the asset library depends on the kind of site that you want to create, and the solution architecture. If the users of the publishing site can have Read permission level on the authoring site collection, the asset library can be stored on the authoring site collection. However, if users on the publishing site cannot have Read permission level on the authoring site collection, the asset library must be created on a separate site collection with different permission levels. For example, in an Internet scenario in which users on the publishing site have only anonymous access, the asset library should be stored on a separate site collection, in a separate web application that is configured to allow anonymous access. However, in an intranet scenario in which users on the publishing site can have read access, the asset library can be stored in the authoring site collection. When the asset library is stored in a site collection separate from both the authoring and publishing sites, make sure that you add it to the list of Suggested Browser Content Locations for the authoring site so content authors can find and insert items from the asset library into their content. If you plan to use image renditions with the asset library, renditions must be enabled and configured on the site collection that hosts the images.
+ To use assets in content, authoring site collections and publishing site collections must have access to the asset library. The location of the asset library depends on the kind of site that you want to create, and the solution architecture. If the users of the publishing site can have Read permission level on the authoring site collection, the asset library can be stored on the authoring site collection. However, if users on the publishing site can't have Read permission level on the authoring site collection, the asset library must be created on a separate site collection with different permission levels. For example, in an Internet scenario in which users on the publishing site have only anonymous access, the asset library should be stored on a separate site collection, in a separate web application that is configured to allow anonymous access. However, in an intranet scenario in which users on the publishing site can have read access, the asset library can be stored in the authoring site collection. When the asset library is stored in a site collection separate from both the authoring and publishing sites, make sure you add it to the list of Suggested Browser Content Locations for the authoring site so content authors can find and insert items from the asset library into their content. If you plan to use image renditions with the asset library, renditions must be enabled and configured on the site collection that hosts the images.
- **Does the asset library have to be shared as a catalog?**
When you plan to use assets in content, remember what is and is not indexed. The
- **Where will assets be cached?**
- When you plan to use assets in content, also plan for where the asset files will be cached. In general, always enable the BLOB cache for publishing sites. The BLOB cache improves web site performance by retrieving BLOB files from the database and storing them in a directory on the front-end web server where they are served to users. This reduces the network traffic to and load on the database server. For more information, see [Plan for caching and performance in SharePoint Server](caching-and-performance-planning.md).
+ When you plan to use assets in content, also plan for where the asset files will be cached. In general, always enable the BLOB cache for publishing sites. The BLOB cache improves web site performance by retrieving BLOB files from the database and storing them in a directory on the front-end web server where they're served to users. The BLOB cache reduces the network traffic to and load on the database server. For more information, see [Plan for caching and performance in SharePoint Server](caching-and-performance-planning.md).
- **How big are the asset files?**
- If you plan to use very large files such as videos in content, you should plan to increase the maximum upload file size on the server where the asset library is located. This will allow you to upload files that are larger than the default setting permitted by SharePoint Server. For more information about the BLOB cache, bit-rate throttling, and maximum upload file size, see [Plan for caching and performance in SharePoint Server](caching-and-performance-planning.md).
+ If you plan to use large files such as videos in content, you should plan to increase the maximum upload file size on the server where the asset library is located. This will allow you to upload files that are larger than the default setting permitted by SharePoint Server. For more information about the BLOB cache, bit-rate throttling, and maximum upload file size, see [Plan for caching and performance in SharePoint Server](caching-and-performance-planning.md).
For more information about how to plan for asset libraries, see [Plan digital asset libraries in SharePoint Server 2013](../sites/plan-digital-asset-libraries.md).
SharePoint Plan The Logical Architecture For Cross Site Publishing https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/plan-the-logical-architecture-for-cross-site-publishing.md
description: "Learn about components and typical architectures for SharePoint Se
[!INCLUDE[appliesto-2013-2016-2019-SUB-xxx-md](../includes/appliesto-2013-2016-2019-SUB-xxx-md.md)]
-Cross-site publishing is a publishing method in SharePoint Server in which you use one or more authoring site collections to author and store content, and one or more publishing site collections to control the design of the site and to show content. The authoring site collection can contain catalogs such as Pages libraries, and lists of items that are tagged with metadata. These catalogs are indexed by the search system and made available to the publishing site collection. The publishing site collection takes the data that has been indexed and shows it on web pages by using Web Parts that use search technology (referred to in this article as Search Web Parts). For more information, see [Overview of cross-site publishing in SharePoint Server](overview-of-cross-site-publishing.md).
+Cross-site publishing is a publishing method in SharePoint Server in which you use one or more authoring site collections to author and store content, and one or more publishing site collections to control the design of the site and to show content. The authoring site collection can contain catalogs such as Pages libraries, and lists of items that are tagged with metadata. The search system indexes these catalogs, which are then made available to the publishing site collection. The publishing site collection takes the data that has been indexed and shows it on web pages by using Web Parts that use search technology (referred to in this article as Search Web Parts). For more information, see [Overview of cross-site publishing in SharePoint Server](overview-of-cross-site-publishing.md).
This article describes the components of a cross-site publishing architecture and illustrates typical cross-site publishing architectures. ## Components of a SharePoint cross-site publishing architecture
-Most cross-site publishing architectures include two or more site collections, which separate the authoring environment from the publishing environment. The number of authoring and publishing site collections that you create depends on project requirements such as how many catalogs there will be and where they are located, and how many publishing sites will show the content. The number of application pools and web applications that you require depends on the type of site you want to create. For example, an intranet site might use the same application pool and web application for both authoring and publishing site collections. Conversely, an Internet site's authoring site collection would be inside the company firewall, and the publishing site collection might be in a separate application pool and web application that is configured to allow anonymous access for users. Because cross-site publishing works across web applications and server farms, you can create a cross-site publishing solution that fits your SharePoint Server topology.
+Most cross-site publishing architectures include two or more site collections, which separate the authoring environment from the publishing environment. The number of authoring and publishing site collections that you create depends on project requirements such as how many catalogs there will be and where they're located, and how many publishing sites will show the content. The number of application pools and web applications that you require depends on the type of site you want to create. For example, an intranet site might use the same application pool and web application for both authoring and publishing site collections. Conversely, the company firewall contains the Internet site's authoring site collection would be inside. A separate application pool and web application (configured to allow anonymous access for users) contains the publishing site collection. Because cross-site publishing works across web applications and server farms, you can create a cross-site publishing solution that fits your SharePoint Server topology.
Before you begin to plan the components that go into a cross-site publishing architecture, consider the following questions:
The following sections describe the components about which you must make key dec
### Authoring site collections
-Authoring site collections are where content is authored or stored. You can have one or more authoring site collections. A single site collection can have multiple libraries and lists. However, there can be only one Pages library per site. If you want to separate content into multiple Pages libraries, you must either create multiple site collections, or create multiple sites within a site collection. For more information, see "Plan site collections and site structure for SharePoint authoring sites" in [Plan authoring sites for cross-site publishing in SharePoint Server](plan-sharepoint-authoring-sites-for-cross-site-publishing.md).
+Authoring site collections are where content is authored or stored. You can have one or more authoring site collections. A single site collection can have multiple libraries and lists. However, there can be only one Pages library per site. If you want to separate content into multiple Pages libraries, you must either create multiple site collections, or create multiple sites within a site collection. For more information, see [Plan authoring sites for cross-site publishing in SharePoint Server](plan-sharepoint-authoring-sites-for-cross-site-publishing.md).
-Library and list content in authoring site collections is tagged by using terms in a managed metadata site column. When the content is indexed by the search system, the column is included as metadata in the index, and is used to categorize content to appear in the publishing site collection.
+Library and list content in authoring site collections is tagged by using terms in a managed metadata site column. When the search system indexes the content, the column is included as metadata in the index, and is used to categorize content to appear in the publishing site collection.
-You can create library and list content at the root of the site collection. However, if you think that you might eventually use variations in your site, we recommend that you create a site within the site collection, and create content there. If you later decide that you need to use variations, this will enable you to specify the site as the source variation site, and will simplify the creation of a variations hierarchy within the site collection.
+You can create library and list content at the root of the site collection. However, if you think you might eventually use variations in your site, we recommend that you create a site within the site collection, and create content there. If you later decide you need to use variations, this created site will enable you to specify it as the source variation site, and will simplify the creation of a variations hierarchy within the site collection.
As you plan authoring site collections for your cross-site publishing architecture, consider the following questions:
As you plan authoring site collections for your cross-site publishing architectu
### Publishing site collections
-Publishing site collections are where content is shown. You can have one or more publishing site collections. However, you do not have to create a site within the site collection, as recommended for authoring site collections. Typically, publishing site collections have URLs that separate sites based on criteria such as location, locale, or brand. This is often helpful when search engine optimization is an important business need. For example, for an extranet site, you might have one publishing site collection named https://partnerweb.contoso.com for external partners, and another publishing site collection named https://customerweb.contoso.com for customers.
+Publishing site collections are where content is shown. You can have one or more publishing site collections. However, you don't have to create a site within the site collection, as recommended for authoring site collections. Typically, publishing site collections have URLs that separate sites based on criteria such as location, locale, or brand. This segregation is often helpful when search engine optimization is an important business need. For example, for an extranet site, you might have one publishing site collection named https://partnerweb.contoso.com for external partners, and another publishing site collection named https://customerweb.contoso.com for customers.
As you plan publishing site collections for your cross-site publishing architecture, consider the following questions:
As you plan publishing site collections for your cross-site publishing architect
When you use cross-site publishing, you use search technology to retrieve and show content. The queries that are specified in the different Search Web Parts on the publishing site are sent to the search index to retrieve relevant content and show it in the Web Parts. Accordingly, the search crawler must have access to content on authoring site collections. For more information, see "Plan crawler authentication" in [Plan crawling and federation in SharePoint Server](../search/plan-crawling-and-federation.md).
-Content is shown on the publishing site collection based on search queries. The queries use terms from one or more term sets that were used to tag content on the authoring site. These terms are pinned to the navigation of the publishing site collection, where they are used to build the queries that get and show content from the search index. For more information, see "Plan term sets for tagging content on SharePoint authoring sites" in [Plan authoring sites for cross-site publishing in SharePoint Server](plan-sharepoint-authoring-sites-for-cross-site-publishing.md), "Plan navigation term sets for SharePoint publishing sites" in [Plan publishing sites for cross-site publishing in SharePoint Server](plan-sharepoint-publishing-sites-for-cross-site-publishing.md), and "Plan result sources and query rules" in [Plan search for cross-site publishing sites in SharePoint Server 2016](plan-search-for-sharepoint-cross-site-publishing-sites.md).
+Content is shown on the publishing site collection based on search queries. The queries use terms from one or more term sets that were used to tag content on the authoring site. These terms are pinned to the navigation of the publishing site collection, where they're used to build the queries that get and show content from the search index. For more information, see "Plan term sets for tagging content on SharePoint authoring sites" in [Plan authoring sites for cross-site publishing in SharePoint Server](plan-sharepoint-authoring-sites-for-cross-site-publishing.md), "Plan navigation term sets for SharePoint publishing sites" in [Plan publishing sites for cross-site publishing in SharePoint Server](plan-sharepoint-publishing-sites-for-cross-site-publishing.md), and "Plan result sources and query rules" in [Plan search for cross-site publishing sites in SharePoint Server 2016](plan-search-for-sharepoint-cross-site-publishing-sites.md).
### Asset libraries
-Asset libraries contain binary large objects (BLOBs) such as pictures and video files that are used in content on the authoring site. These assets must be accessible by two separate groups of users: content authors on the authoring site, and readers on the publishing site. If the publishing site is an Internet site available to anonymous users, the asset library must be in a separate site collection from the authoring site, and must be in a web application that is configured to allow anonymous access. This could be in the same web application as the publishing site, or in a separate web application. In either case, designers or content authors must be able to upload files to the asset library, and the library should be added to the list of Suggested Content Browser Locations for the authoring site so that content authors can locate and use assets stored within the library.
+Asset libraries contain binary large objects (BLOBs) such as pictures and video files that are used in content on the authoring site. These assets must be accessible by two separate groups of users: content authors on the authoring site, and readers on the publishing site. If the publishing site is an Internet site available to anonymous users, the asset library must be in a separate site collection from the authoring site, and must be in a web application that is configured to allow anonymous access. This asset library could be in the same web application as the publishing site, or in a separate web application. In either case, designers or content authors must be able to upload files to the asset library, and the library should be added to the list of Suggested Content Browser Locations for the authoring site so that content authors can locate and use assets stored within the library.
As you plan asset libraries for your cross-site publishing architecture, consider the following questions:
The following figure shows a simple one-to-one (1:1) authoring-to-publishing sit
![Published intranet sample architecture](../media/PublishedintranetarchitectureXSP.gif)
-Both site collections are located within a single web application that uses claims-based authentication. The authoring site collection (http://authoring) contains a single Pages library, and can also contain one or more lists or libraries that are not Pages libraries. All libraries and lists are shared as catalogs. The catalog content is shown in a single publishing site collection (http://contosoweb).
+Both site collections are located within a single web application that uses claims-based authentication. The authoring site collection (http://authoring) contains a single Pages library, and can also contain one or more lists or libraries that aren't Pages libraries. All libraries and lists are shared as catalogs. The catalog content is shown in a single publishing site collection (http://contosoweb).
Because the authoring and publishing site collections are in the same web application, asset library files are stored in the authoring site collection, and site users on http://contosoweb have read access to those assets.
The following figure shows a one-to-many (1:n) authoring-to-publishing site conf
![Published extranet sample architecture](../media/PublishedextranetarchitectureXSP.gif)
-The authoring and publishing site collections are located in separate web applications. The Authored content web application uses Active Directory Domain Services (AD DS) for authentication of content authors, whereas the web application that contains the Published extranet sites uses forms-based authentication for designers, customers, and partners. The extranet sites are located in a single web application, but are in separate site collections to provide for greater isolation between customers and partners. The authoring site collection (http://authoring/) contains two sites, one for customer content (http://authoring/customer) and one for partner content (http://authoring/partner). Each site contains a single Pages library, and can also contain one or more lists. All libraries and lists are shared as catalogs. The Pages library and list content is shown in two separate publishing site collections, one named https://customerweb.contoso.com for customers, and one named https://partnerweb.contoso.com for partners. For more information about how to plan an extranet site architecture, see [SharePoint Server design samples: Corporate portal and extranet sites](/previous-versions/office/sharepoint-server-2010/cc261995(v=office.14)).
+The authoring and publishing site collections are located in separate web applications. The Authored content web application uses Active Directory Domain Services (AD DS) for authentication of content authors, whereas the web application that contains the Published extranet sites uses forms-based authentication for designers, customers, and partners. The extranet sites are located in a single web application, but are in separate site collections to provide for greater isolation between customers and partners. The authoring site collection (http://authoring/) contains two sites, one for customer content (http://authoring/customer) and one for partner content (http://authoring/partner). Each site contains a single Pages library, and can also contain one or more lists. All libraries and lists are shared as catalogs. The Pages library and list content are shown in two separate publishing site collections, one named https://customerweb.contoso.com for customers, and one named https://partnerweb.contoso.com for partners. For more information about how to plan an extranet site architecture, see [SharePoint Server design samples: Corporate portal and extranet sites](/previous-versions/office/sharepoint-server-2010/cc261995(v=office.14)).
Because the publishing site collections are outside the firewall, the asset library is located in a separate site collection in the same web application as the published extranet site collection so that users on the publishing sites have read access to those assets. Internal users such as designers and other content authors have the Contribute permission level to add, update, and delete items in the asset library. The asset library is added to the Suggested Content Browser Locations list for the authoring site collection so that content authors can use those assets in their content.
The following figure shows a many-to-many (n:n) authoring-to-publishing site con
![Published Internet sample architecture](../media/PublishedInternetarchitectureXSP.gif)
-The authoring and publishing site collections are located in separate web applications. The Authored content web application uses AD DS for authentication of content authors, whereas the Published Internet sites web application uses forms-based authentication for designers and is also configured to allow anonymous access for external users. The authoring site (http://authoring) contains a single Pages library. The product catalog site collection (http://products) contains a list of product data. All libraries and lists are shared as catalogs. The catalog content appears in two separate publishing site collections, one named http://www.contoso.com and one named http://www.fabrikam.com. Different content and products are shown on the publishing sites based on the associated brand.
+The authoring and publishing site collections are located in separate web applications. The Authored content web application uses AD DS for authentication of content authors, whereas the Published Internet sites web application uses forms-based authentication for designers and is also configured to allow anonymous access for external users. The authoring site (http://authoring) contains a single Pages library. The product catalog site collection (http://products) contains a list of product data. All libraries and lists are shared as catalogs. The catalog content appears in two separate publishing site collections, one named https://www.contoso.com and one named https://www.fabrikam.com. Different content and products are shown on the publishing sites based on the associated brand.
Because the publishing site collections are outside the firewall, the asset library is located in a separate site collection in the same web application as the publishing site collections so that users on the publishing sites have read access to those assets. Internal users such as designers and other content authors have Contribute permission level to add, update, and delete items in the asset library. The asset library is added to the Suggested Content Browser Locations list for the authoring and product catalog site collections so that content authors can use those assets in their content.
SharePoint Stage 10 Configure The Query In A Content Search Web Part On A Catalog Item Page https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/stage-10-configure-the-query-in-a-content-search-web-part-on-a-catalog-item-page.md
description: "Learn how to configure the query in a Content Search Web Part on a
## Quick Overview
-[Stage 9: Configure the query in a Content Search Web Part on a category page in SharePoint Server](stage-9-configure-the-query-in-a-content-search-web-part-on-a-category-page.md) explained how to add a Content Search Web Part to a page and how to configure the query for a catalog page. The next step is to do the same for the catalog item page.
+[Stage 9: Configure the query in a Content Search Web Part on a category page in SharePoint Server](stage-9-configure-the-query-in-a-content-search-web-part-on-a-category-page.md) explains:
+- How to add a Content Search Web Part to a page
+- How to configure the query for a catalog page
+
+The next step is to do the same for the catalog item page.
In this article, you'll learn:
In this article, you'll learn:
### Defining how catalog items should be displayed on our Contoso site <a name="BKMK_DefiningHowCatalotItemsShouldBeDisplayedOnOurContosoSite"> </a>
-The various products featured in the Contoso catalog are all available in different colors. For example, by looking in our catalog list, you'll see that the *Northwind Traders 50W Car Radio* is available in five colors. The color versions of a product are grouped under a common *Group Number* .
+The various products featured in the Contoso catalog are all available in different colors. For example, by looking in our catalog list, you'll see that the *Northwind Traders 50W Car Radio* is available in five colors. The color versions of a product are grouped under a common *Group Number*.
![Catalog Car Radio](../media/OTCSP_CatalogCarRadio.png)
-When displaying a product on our Contoso site, visitors should easily see that the product is available in other colors. For example, when visitors browse to a silver colored version of the *Northwind Traders 50W Car Radio* , they should easily see which other color options are available for that item. They should also be able to view details quickly about the product in another color, without having to go back to the category page.
+When displaying a product on our Contoso site, visitors should easily see that the product is available in other colors. For example, when visitors browse to a silver colored version of the *Northwind Traders 50W Car Radio*, they should easily see which other color options are available for that item. They should also be able to view details quickly about the product in another color, without having to go back to the category page.
-So, on our catalog item page we want to display items that have the same *Group Number* . To do this, we must use the Content Search Web Part (CSWP).
+So, on our catalog item page, we want to display items that have the same *Group Number*. To do this configuration, we must use the Content Search Web Part (CSWP).
> [!NOTE] > The item details page that was automatically created when we connected our publishing site to our catalog as described in [Stage 5: Connect your publishing site to a catalog in SharePoint Server](stage-5-connect-your-publishing-site-to-a-catalog.md) contained several Catalog Item Reuse Web Parts (CIRWP). There are scenarios where using CIRWPs to display item detail content would be appropriate. But, because the CIRWP is only able to display one item at a time, we can't use this Web Part for our Contoso scenario.
Our catalog item page only has one Web Part zone. To add a CSWP to our catalog i
![CSWP Added](../media/OTCSP_CSWPadded.png)
-As was the case when we added a CSWP to our category page, the Web Part displays some content (Audio, Cameras and Computers), but does not display the content we want. To make the Web Part display Contoso catalog content, we must configure the query in the Web Part. To configure the query, we'll use what's known as a query variable. But first, let's take a look at what query variables are and how they're used when you configure a query.
+As was the case when we added a CSWP to our category page, the Web Part displays only content such as Audio, Cameras and Computers but not the content we want. To make the Web Part display Contoso catalog content, we must configure the query in the Web Part. To configure the query, we'll use what's known as a query variable. But first, let's take a look at what query variables are and how they're used when you configure a query.
### About query variables <a name="BKMK_AboutQueryVariables"> </a> A query variable is a placeholder that is replaced with a value when a query is run. Let's look at this definition within the context of our Contoso scenario.
-You might not have been aware of it, but in [Stage 9: Configure the query in a Content Search Web Part on a category page in SharePoint Server](stage-9-configure-the-query-in-a-content-search-web-part-on-a-category-page.md), when we configured the query in the CSWP on the catalog page, we used a query variable. When we selected **Restrict by current and child navigation terms**, a query variable was added to our query. That query variable was a placeholder for the navigation value in the URL (audio, camera, mp3, etc.). Whenever a visitor clicks a category, the query variable in the Web Part is replaced with the navigation value in the URL. As a result, the Web Part issued a query for catalog items that are tagged with "audio", "camera", "mp3", and so on
+You might not have been aware of it, but in [Stage 9: Configure the query in a Content Search Web Part on a category page in SharePoint Server](stage-9-configure-the-query-in-a-content-search-web-part-on-a-category-page.md), we used a query variable when we configured the query in the CSWP on the catalog page. When we selected **Restrict by current and child navigation terms**, a query variable was added to our query. That query variable was a placeholder for the navigation value in the URL such as audio, camera, or mp3. Whenever a visitor clicks a category, the query variable in the Web Part is replaced with the navigation value in the URL. As a result, the Web Part issued a query for catalog items that are tagged with "audio", "camera", "mp3", and so on.
-Coming back to our catalog item page, we want to display items that have the same Group Number. Remember in [Stage 3: How to enable a list as a catalog in SharePoint Server](stage-3-how-to-enable-a-list-as-a-catalog.md) how we added **Group Number** as one of the list columns to be used as a **Catalog Item URL Field**. We did this so the value of *Group Number* would be used in the URL.
+Coming back to our catalog item page, we want to display items that have the same Group Number. Remember in [Stage 3: How to enable a list as a catalog in SharePoint Server](stage-3-how-to-enable-a-list-as-a-catalog.md) how we added **Group Number** as one of the list columns to be used as a **Catalog Item URL Field**. We did this configuration so the value of *Group Number* would be used in the URL.
-The following screen shot shows our final Contoso site. Notice that the group number, *5637145950* , is used as the second to last value in the URL.
+The following screenshot shows our final Contoso site. Notice that the group number, *5637145950*, is used as the second to last value in the URL.
![Item Car Radido](../media/OTCSP_ItemCarRadido.png)
-If we browse to another product, we'll see the group number for this product ( *5637145875* , for example) is also used as the second to last value in the URL.
+If we browse to another product, we'll see the group number for this product (*5637145875*, for example) is also used as the second to last value in the URL.
![Item Camcorder](../media/OTCSP_ItemCamcorder.png) So, when you configure the query for the CSWP on our catalog item page, you should use a query variable that will represent the second to last value in the URL.
-Query variables are contained enclosed in braces as follows: {QueryVariable}. Don't worry about those braces, this isn't as scary or as complex as it might look.
+Query variables are contained enclosed in braces as follows: {QueryVariable}. Don't worry about those braces, this syntax isn't as scary or as complex as it might look.
-As mentioned above, when we configured the query in the CSWP on the catalog page we used a query variable. But we didn't have to deal with any scary looking braces. That was because the nice looking radio button, **Restrict by current and child navigation terms**, took care of it for us. To configure the query for our item catalog page, we must add a query variable with braces. Luckily, we'll have some friendly pull-down menus to help us along. So let's delve into the task of configuring the query.
+As mentioned above, when we configured the query in the CSWP on the catalog page we used a query variable. But we didn't have to deal with any scary looking braces because the nice looking radio button, **Restrict by current and child navigation terms**, took care of it for us. To configure the query for our item catalog page, we must add a query variable with braces. Luckily, we'll have some friendly pull-down menus to help us along. So let's delve into the task of configuring the query.
### How to configure a query in a Content Search Web Part on a catalog item page <a name="BKMK_HowToConfigureAQueryInAContentSearchWebPartOnACatalogItemPage"> </a> 1. In the Web Part, select the **Web Part** menu > **Edit Web Part**.
-2. In the Web Part tool pane, select **Change query**. This opens a dialog box.
+2. In the Web Part tool pane, select **Change query**. This option opens a dialog box.
3. In the dialog box, from the **Select a query** list, select your catalog result source. In our scenario, it's *catalog - Products Results*.
As mentioned above, when we configured the query in the CSWP on the catalog page
![Switch Advanced Mode](../media/OTCSP_SwitchAdvancedMode.png)
-In Advanced Mode, in the **Query text** field, you'll see some text. This is the query text that represents our result source *catalog - Products Results*. (We saw the same query text in Stage 9, when we looked at [How to view details of the query configuration](stage-9-configure-the-query-in-a-content-search-web-part-on-a-category-page.md#BKMK_HowToViewDetailsOfTheQueryConfiguration).)
+In Advanced Mode, in the **Query text** field, you'll see some text. This text is the query text that represents our result source *catalog - Products Results*. (We saw the same query text in Stage 9, when we looked at [How to view details of the query configuration](stage-9-configure-the-query-in-a-content-search-web-part-on-a-category-page.md#BKMK_HowToViewDetailsOfTheQueryConfiguration).)
![Search Results From a Particular Site](../media/OTCSP_QueryTextResultSource.png)
In Advanced Mode, in the **Query text** field, you'll see some text. This is the
![Query Set](../media/OTCSP_QuerySet.png)
- **ProductCatalogGroupNumberOWSTEXT** is the managed property name of the site column *Group Number* . (Earlier in this series, we looked at naming convention for this column in [Naming convention for the default site columns in the Products list](from-site-column-to-managed-propertywhat-s-up-with-that.md#BKMK_NamingConventionfortheDefaultSiteColumnsintheProductsList).) Selecting **Contains** and **Value of a token from URL** will create the query variable we want to use.
+ **ProductCatalogGroupNumberOWSTEXT** is the managed property name of the site column *Group Number*. (Earlier in this series, we looked at naming convention for this column in [Naming convention for the default site columns in the Products list](from-site-column-to-managed-propertywhat-s-up-with-that.md#BKMK_NamingConventionfortheDefaultSiteColumnsintheProductsList).) Selecting **Contains** and **Value of a token from URL** will create the query variable we want to use.
7. Select **Add property filter**.
So now you might be thinking "OK, that was easy, but what does **ProductCatalogG
- The colon : means "contains"
- - **{URLToken.1}** represents a value from the URL of the current page. The integer, in this case **1**, represents the value in the URL as counted from right to left. So, for example, in the URL *http://www.contoso.com/cameras/camcorders/563714875/6637146586*, the query variable {URLToken.1} represents the value *6637146586*.
+ - **{URLToken.1}** represents a value from the URL of the current page. The integer, in this case **1**, represents the value in the URL as counted from right to left. So, for example, in the URL *https://www.contoso.com/cameras/camcorders/563714875/6637146586*, the query variable {URLToken.1} represents the value *6637146586*.
- If we put the complete query together, it means the following:
+ If we put the complete query together, it means:
- From the result source *catalog - Products Results* , search for items where the value of the managed property *ProductCatalogGroupNumberOWSTEXT* contains the value that is currently used as the first value in the URL, counting from right to left.
+ From the result source *catalog - Products Results*, search for items where the value of the managed property *ProductCatalogGroupNumberOWSTEXT* contains the value that is currently used as the first value in the URL, counting from right to left.
In the last step of the procedure in [Stage 3: How to enable a list as a catalog in SharePoint Server](stage-3-how-to-enable-a-list-as-a-catalog.md), we defined that the item URL should contain both Group Number and Item Number as catalog Item and URL fields. This means that the first value in the URL, counting from right to left, is *Item Number*. We want to search for items that have the same *Group Number*. Therefore, we must make a small change to the query variable.
So now you might be thinking "OK, that was easy, but what does **ProductCatalogG
![URL Token 2](../media/OTCSP_URLToken2.png)
-Now the query in the Web Part will search for items where the value of the managed property *ProductCatalogGroupNumberOWSTEXT* contains the value that is currently used as the second value in the URL, counting from right to left.
+Now, the query in the Web Part will search for items whose *ProductCatalogGroupNumberOWSTEXT* value is the one currently used as the second value in the URL, counting from right to left.
9. To test that this query returns the correct results, select **Test query**. ![Test Query 2](../media/OTCSP_TestQuery2.png)
-Notice that five items are displayed under **RelevantResults**. This verifies that the query is correct, because we know that the *Northwind Traders 50W Car Radio* is available in five colors.
+Notice that five items are displayed under **RelevantResults**. This result verifies that the query is correct, because we know that the *Northwind Traders 50W Car Radio* is available in five colors.
10. Select **OK** and save the page. ![Query Results](../media/OTCSP_QueryResults.png)
-Even though three products are displayed instead of one, and we still don't have the Contoso look, this is progress. The query in the Web Part is now configured. In the next article we'll show you how to add display templates that will give our items the Contoso look.
+Even though three products are displayed instead of one, and we still don't have the Contoso look, this result denotes progress. The query in the Web Part is now configured. In the next article we'll show you how to add display templates that will give our items the Contoso look.
#### Next article in this series
SharePoint Stage 8 Assign A Category Page And A Catalog Item Page To A Term https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/stage-8-assign-a-category-page-and-a-catalog-item-page-to-a-term.md
description: "Learn how to assign a category page and a catalog item page to a t
## Quick overview
-In previous stages of this series we:
+In previous stages of this series, we:
- [Specify the full site navigation](stage-5-connect-your-publishing-site-to-a-catalog.md#BKMK_SpecifytheFullSiteNavigation)
In this article, you'll learn:
- [How to assign a category page and a catalog item page to a term](stage-8-assign-a-category-page-and-a-catalog-item-page-to-a-term.md#BKMK_HowToAssignACategoryPageAndACatalogItemPageToATerm) -- [About the friendly URL for category pages](stage-8-assign-a-category-page-and-a-catalog-item-page-to-a-term.md#BKMK_AboutTheFriendlyURLForCategoryPages)
+- [About the friendly URL for category pages](#about-the-friendly-url-for-category-pages)
## Start stage 8
Managed navigation was introduced in SharePoint Server 2016. This navigation met
One of the benefits of using managed navigation is that it separates the site navigation from the location of your content. By using managed navigation, it's not the location of your content that defines where in the navigation your content will appear, but how you tag your content with terms from a term set. For example, in earlier versions of SharePoint, if you wanted to add a new page under "About our company," you had to add that page under the "About our company" branch within your content. By using managed navigation, you can add a page to the branch that makes the most sense to you. By tagging that page with a term, and using Search Web Parts, it will appear in the correct place in the navigation.
-Another benefit of managed navigation is that it creates friendly URLs. In earlier versions of SharePoint, the URL to a page contained a reference to the **Pages** library and any folders within that library, for example: *http://www.contoso.com/pages/products/computers/laptops.aspx* . By using managed navigation, URLs are based on the terms in the term set that drives your site navigation, for example: *http://www.contoso.com/computers/laptops* .
+Another benefit of managed navigation is that it creates friendly URLs. In earlier versions of SharePoint, the URL to a page contained a reference to the **Pages** library and any folders within that library, for example: *https://www.contoso.com/pages/products/computers/laptops.aspx*. By using managed navigation, URLs are based on the terms in the term set that drives your site navigation, for example: *https://www.contoso.com/computers/laptops*.
[Stage 3: How to enable a list as a catalog in SharePoint Server](stage-3-how-to-enable-a-list-as-a-catalog.md) explained how terms from the **Product Hierarchy** term set are used to create a friendly URL.
When you display information in a catalog format, the layout and structure of th
![Two Categories](../media/OTCSP_TwoCategories.jpg)
-Also, regardless of what type of product a visitor views, the catalog item page should be consistent. For example always display an image of a product in the upper-left corner, followed by tables of product specifications.
+Also, regardless of the type of product a visitor views, the catalog item page should be consistent. For example always display an image of a product in the upper-left corner, followed by tables of product specifications.
![Two Products](../media/OTCSP_TwoProducts.jpg)
-By combining managed navigation with category pages and catalog item pages, you don't have to create several pages for your catalog categories or for your catalog items. For example, in our Contoso scenario, we'll use only use the two pages we created in [Stage 7: Upload page layouts and create new pages in a publishing site in SharePoint Server](stage-7-upload-page-layouts-and-create-new-pages-in-a-publishing-site.md).
+By combining managed navigation with category pages and catalog item pages, you don't have to create several pages for your catalog categories or for your catalog items. For example, in our Contoso scenario, we'll use only the two pages we created in [Stage 7: Upload page layouts and create new pages in a publishing site in SharePoint Server](stage-7-upload-page-layouts-and-create-new-pages-in-a-publishing-site.md).
So, after all that theory, in the next section, we'll show you how you can do this.
In the **Target Page Settings** and **Catalog Item Page Settings** sections, the
![Automatically Assigned Pages](../media/OTCSP_AutomaticallyAssignedPages.png)
-Remember [Stage 5: Connect your publishing site to a catalog in SharePoint Server](stage-5-connect-your-publishing-site-to-a-catalog.md), when we connected our publishing site to our catalog? In that stage, a category page and a catalog item page were automatically created and added to the **Pages** library. What we didn't cover in Stage 5 is that references to these pages were added to this term set, as shown in the screen shot above. In the next steps we'll change these references so they point to our newly created category page and catalog item page.
+Remember [Stage 5: Connect your publishing site to a catalog in SharePoint Server](stage-5-connect-your-publishing-site-to-a-catalog.md), when we connected our publishing site to our catalog? In that stage, a category page and a catalog item page were automatically created and added to the **Pages** library. What we didn't cover in Stage 5 is that references to these pages were added to this term set, as shown in the screenshot above. In the next steps, we'll change these references so they point to our newly created category page and catalog item page.
3. In the **Target page settings** section, do the following: 1. In the **Change target page for this term** section, select **Browse**.
-2. In the **Select an Asset** dialog box, select **Pages**, and then select the category page that you want to apply. In our scenario, this is **ContosoCategoryPage.aspx**.
+2. In the **Select an Asset** dialog box, select **Pages**, and then select the category page that you want to apply. In our scenario, this page is **ContosoCategoryPage.aspx**.
![Select Category Page](../media/OTCSP_SelectCategoryPage.png)
-By setting this reference, when visitors browse to "Audio" on the Contoso site, the page *ContosoCategoryPage.aspx* will be used to display information. It is important to understand that visitors won't see the page name *ContosoCategoryPage.aspx* , but instead a friendly URL. More information about friendly URLs will be provided in [About the friendly URL for category pages](stage-8-assign-a-category-page-and-a-catalog-item-page-to-a-term.md#BKMK_AboutTheFriendlyURLForCategoryPages), later in this article.
+By setting this reference, when visitors browse to "Audio" on the Contoso site, the page *ContosoCategoryPage.aspx* will be used to display information. It's important to understand that the visitors won't see the page name *ContosoCategoryPage.aspx*, but instead a friendly URL. More information about friendly URLs will be provided in [About the friendly URL for category pages](#about-the-friendly-url-for-category-pages), later in this article.
3. In the **Change target page for children of this term** section, repeat steps 3a and 3b. By setting this reference, when visitors browse to a child term of "Audio," for example "Speakers," the page *ContosoCategoryPage.aspx* is used to display information.
By setting this reference, when visitors browse to an item that is tagged with t
![Item Page Settings](../media/OTCSP_ItemPageSettings.png)
-5. Repeat Steps 2 - 4 for all terms to which you want to assign a category page and an item details page. In our scenario, we'll do this to all terms within the **Site Navigation** term set.
+5. Repeat Steps 2 - 4 for all terms to which you want to assign a category page and an item details page. In our scenario, we'll do these steps to all terms within the **Site Navigation** term set.
![All Terms](../media/OTCSP_AllTerms.png)
After applying the new category page and catalog item page to all terms, you can
![Audio Page](../media/OTCSP_AudioPage.png)
-This is good, because when we created a category page in [Stage 7: Upload page layouts and create new pages in a publishing site in SharePoint Server](stage-7-upload-page-layouts-and-create-new-pages-in-a-publishing-site.md), we created an empty page. To display content, we'll have to add Search Web Parts. We'll explain how to do this in the next article.
+This lack of much content is good, because when we created a category page in [Stage 7: Upload page layouts and create new pages in a publishing site in SharePoint Server](stage-7-upload-page-layouts-and-create-new-pages-in-a-publishing-site.md), we created an empty page. To display content, we'll have to add Search Web Parts, which We'll explain in the next article.
### About the friendly URL for category pages
-<a name="BKMK_AboutTheFriendlyURLForCategoryPages"> </a>
When you use managed navigation, the friendly URLs that visitors see are composed of the terms from the term set that drives site navigation. To see how friendly URLs are composed, on the **Term Store Management Tool** page, select a term, for example "Audio," and then select the **TERM-DRIVEN PAGES** tab.
-The friendly URL appears in the **Configure Friendly URL for this term** section.
+The friendly URL appears in the **Configure Friendly URL for this term** section.
![Configure Friendly URL](../media/OTCSP_FURLAudio.png)
Similarly, when you select "Car audio," you'll see the friendly URL for this pag
If you want to change a friendly URL, for example from "audio" to "audio players," you should change the actual term itself. That way, the friendly URL and the term that is used to tag your content will remain consistent.
-If this was somewhat confusing, don't worry. We'll explain more about how Search Web Parts work in the next article..
+If this concept was confusing, don't worry. We'll explain more about how Search Web Parts work in the next article.
### Next article in this series
-<a name="BKMK_AboutTheFriendlyURLForCategoryPages"> </a>
[Stage 9: Configure the query in a Content Search Web Part on a category page in SharePoint Server](stage-9-configure-the-query-in-a-content-search-web-part-on-a-category-page.md)
SharePoint Understanding Multi Tenancy https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/understanding-multi-tenancy.md
description: Learn about the multi-tenancy feature and the underlying components
[!INCLUDE[appliesto-2013-xxx-xxx-xxx-xxx-md](../includes/appliesto-2013-xxx-xxx-xxx-xxx-md.md)]
-This article describes the components and services related to multi-tenancy in SharePoint Server 2013 and also provides architectural, security, operational, and management guidance to help service providers in gaining an understanding of multi-tenancy in SharePoint Server 2013 for planning, designing, building, and managing a multi-tenant SharePoint Server 2013 hosting platform.
+This article describes the components and services that are related to multi-tenancy in SharePoint Server 2013 and also provides architectural, security, operational, and management guidance to help service providers in gaining an understanding of multi-tenancy in SharePoint Server 2013 for planning, designing, building, and managing a multi-tenant SharePoint Server 2013 hosting platform.
> [!NOTE] > Microsoft OneDrive with Yammer integration doesn't work for multi-tenancy or partitioned service applications for on-premises deployments.
This article describes the components and services related to multi-tenancy in S
### What is multi-tenancy?
-Before we introduce the multi-tenancy functionality in SharePoint Server 2013, you should understand the general concept of multi-tenancy and its related characteristics; doing this will help you make the appropriate decisions for planning, designing, operating, and managing your multi-tenant SharePoint Server 2013 hosting platform.
+Before we introduce the multi-tenancy functionality in SharePoint Server 2013, you should understand the general concept of multi-tenancy and its related characteristics. Understanding multi-tenancy and its related characteristics will help you make the appropriate decisions for planning, designing, operating, and managing your multi-tenant SharePoint Server 2013 hosting platform.
-Multi-tenancy refers to the ability to manage and partition data of sites and otherwise shared services or software in order to accommodate multiple tenants. This is in contrast to running multiple instances of a service, or setting up separate hardware. In Microsoft products and technologies, multi-tenancy of services creates a hosting environment wherein server farm resources are maximized. Before learning about hosting environments, it is important to understand the services architecture.
+Multi-tenancy refers to the ability to manage and partition data of sites and otherwise shared services or software to accommodate multiple tenants. This ability is in contrast to running multiple instances of a service, or setting up separate hardware. In Microsoft products and technologies, multi-tenancy of services creates a hosting environment wherein server farm resources are maximized. Before learning about hosting environments, it's important to understand the services architecture.
### Key components and services for enabling multi-tenancy in SharePoint Server 2013
A SharePoint 2013 web application is composed of an Internet Information Service
#### Host-named site collection
-Host-named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as `http://TeamA.contoso.com` and `http://TeamB.fabrikam.com`. This lets you deploy many sites that use unique DNS names in the same web application. It also enables service providers to scale an environment to many customers. If you do not use host-named site collections, the SharePoint web application will contain many path-based site collections that share the same host name (DNS name). For example, Team A would have a site collection at http://contoso.com/sites/teamA and Team B would have a site collection at http://fabrikam.com/sites/teamB.
+Host-named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as `http://TeamA.contoso.com` and `http://TeamB.fabrikam.com`. This provision lets you deploy many sites that use unique DNS names in the same web application. It also enables service providers to scale an environment to many customers. If you don't use host-named site collections, the SharePoint web application will contain many path-based site collections that share the same hostname (DNS name). For example, Team A would have a site collection at `https://contoso.com/sites/teamA` and Team B would have a site collection at `https://fabrikam.com/sites/teamB`.
-Host Named Site Collections are fundamentally the only way to scale for multi-tenancy environments, and provide ultimate flexibility with respect to the URL namespace used. If using path-based sites with multi-tenancy the software boundary for managed paths will be reached extremely quickly.
+Host Named Site Collections are fundamentally the only way to scale for multi-tenancy environments, and provide ultimate flexibility with respect to the URL namespace used. If using path-based sites with multi-tenancy, the software boundary for managed paths will be reached quickly.
-For additional information about how to plan for host-named site collections for SharePoint Server 2013, see [Host-named site collection architecture and deployment (SharePoint 2013)](host-named-site-collection-architecture-and-deployment.md).
+For more information about how to plan for host-named site collections for SharePoint Server 2013, see [Host-named site collection architecture and deployment (SharePoint 2013)](host-named-site-collection-architecture-and-deployment.md).
#### Service groups (proxy groups)
-A *service group*, also known as *proxy group*, is a group of service applications that are selected for use by a web application.
-
+A *service group*, also known as *proxy group*, is a group of service applications that are selected for a web application to use them.
+ By default, all service applications are included in the default group unless another group is specified at the time that the service application is created. You can add and remove service applications from the default group at any time. When you create a web application, you can select the default group, or you can create a custom group of services. You create a custom group of services by selecting only the service applications that you want the web application to use.
-Custom groups are not reusable across multiple web applications. Each time that you select "custom" when you create a web application, you are selecting services only for the web application that you are creating.
+Custom groups aren't reusable across multiple web applications. Each time that you select "custom" when you create a web application, you're selecting services only for the web application that you're creating.
#### Service proxy When you create a service application, a proxy for the service application is created at the same time. A proxy is a virtual entity that connects web applications to service applications. Proxies are listed on the Manage Service Applications page in the SharePoint Central Administration website.
-Proxies are automatically created if you use Central Administration or the SharePoint 2016 Products Configuration Wizard to create service applications. If you use Microsoft PowerShell to create service applications, proxies are not always automatically created and must be created by using Microsoft PowerShell.
+Proxies are automatically created if you use Central Administration or the SharePoint 2016 Products Configuration Wizard to create service applications. If you use Microsoft PowerShell to create service applications, proxies aren't always automatically created and must be created by using Microsoft PowerShell.
-Some proxies might include settings that can be changed. For example, if a web application is connected to multiple instances of the managed metadata service, you must indicate the proxies that are connected to the primary service application that hosts the corporate taxonomy. Generally speaking these settings move to tenant level configuration when using multi-tenancy.
+Some proxies might include settings that can be changed. For example, if a web application is connected to multiple instances of the managed metadata service, you must indicate the proxies that are connected to the primary service application that hosts the corporate taxonomy. These settings move to tenant level configuration when using multi-tenancy.
#### Service applications
-A service application is a logical representation of a given service, and its security and management configuration which defines its operational behavior. Examples include Managed Metadata and User Profiles. Different service applications are implemented in different ways and this will influence the design of multi-tenant solutions.
+A service application is a logical representation of a given service, and its security and management configuration, which defines its operational behavior. Examples include Managed Metadata and User Profiles. Different service applications are implemented in different ways and this flexibility will influence the design of multi-tenant solutions.
To determine the list of service applications that is available in SharePoint Server 2013 and their availability across SharePoint editions with multi-tenancy feature, see the **Services and Functionalities** section in [General guidance for hosters in SharePoint Server 2013](general-guidance-for-hosters-in-sharepoint-server-2013.md) #### Feature packs and licensing
-A feature pack in SharePoint is a way to group a set of site-scoped or web-scoped features together. Once the SharePoint features are grouped, they can be associated with a site subscription (i.e., tenant). All site collections in that site subscription (tenant) can use only the site-scoped or web-scoped features that are part of the feature pack. This capability enables service providers to provide tiered service offerings based on different sets of features.
+A feature pack in SharePoint is a way to group a set of site-scoped or web-scoped features together. Once the SharePoint features are grouped, they can be associated with a site subscription (that is, tenant). All site collections in that site subscription (tenant) can use only the site-scoped or web-scoped features that are part of the feature pack. This capability enables service providers to provide tiered service offerings based on different sets of features.
-In SharePoint Server 2013, a new feature has been added for assigning different SharePoint licenses on a per-user basis. It also turns on SharePoint license checks at run time. This feature provides additional flexibility for a service provider to build different service offerings throughout a simplified deployment model. In previous SharePoint versions, service providers had to build different SharePoint deployment models for each SharePoint version. For additional information about SharePoint features, see the **SharePoint feature availability across on-premises solutions** section of the following article: [SharePoint Service Description](/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-service-description).
+In SharePoint Server 2013, a new feature has been added for assigning different SharePoint licenses on a per-user basis. It also turns on SharePoint license checks at run time. This feature provides more flexibility for a service provider to build different service offerings throughout a simplified deployment model. In previous SharePoint versions, service providers had to build different SharePoint deployment models for each SharePoint version. For more information about SharePoint features, see the **SharePoint feature availability across on-premises solutions** section of the following article: [SharePoint Service Description](/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-service-description).
#### Information Rights Management
This section describes various considerations for architecting a multi-tenancy S
### Understand boundaries and limits in SharePoint Server 2013
-Understanding the software boundaries and limits of SharePoint Server 2013 will help you make the right decisions for selecting the appropriate architecture for a multi-tenancy SharePoint environment. For additional information about key boundaries and limits for a content database and site collection as they apply to a multi-tenancy environment of SharePoint Server 2013, see [Software boundaries and limits for SharePoint Server 2016](../install/software-boundaries-and-limits.md#ContentDB) and [Software boundaries and limits for SharePoint Server 2016](../install/software-boundaries-and-limits.md#SiteCollection).
+Understanding the software boundaries and limits of SharePoint Server 2013 will help you make the right decisions for selecting the appropriate architecture for a multi-tenancy SharePoint environment. For more information about key boundaries and limits for a content database and site collection as they apply to a multi-tenancy environment of SharePoint Server 2013, see [Software boundaries and limits for SharePoint Server 2016](../install/software-boundaries-and-limits.md#ContentDB) and [Software boundaries and limits for SharePoint Server 2016](../install/software-boundaries-and-limits.md#SiteCollection).
#### Shared farm vs. dedicated farm
Using a shared farm to host multi-tenant site collections on a single web applic
Use a dedicated web application and application pool per customer only if you need to satisfy requirements for isolation.
-Do not allow full-trust code to be deployed to sites.
+Don't allow full-trust code to be deployed to sites.
-Do not allow customizations that affect shared resources, such as the web.config file.
+Don't allow customizations that affect shared resources, such as the web.config file.
Use host-named site collections to create multiple, root-level site collections (domain-named sites) throughout a web application.
Use host-named site collections to create multiple, root-level site collections
Use dedicated web applications for tenants that require customizations affecting resources that are shared across a web application, such as the web.config file.
-When combining multiple tenants in a single farm, use a dedicated SharePoint web application for all authenticated content and a separate dedicated web application for all anonymous content. This will require two separate subscriptions IDs for tenants with both types of content. This will also simplify licensing.
+When combining multiple tenants in a single farm, use a dedicated SharePoint web application for all authenticated content and a separate dedicated web application for all anonymous content. This method will require two separate subscriptions IDs for tenants with both types of content. This method will also simplify licensing.
Some SharePoint features are bound to web application level, such as the Self-Service Site Collection Creation setting. After it's turned on, all tenants under the same web application will be able to create site collections. #### Single farm environment design
-In a multi-organization hosting environment in which tenant data and administration are isolated, the configuration of partitioned and shared services is very important. This example provides a practical implementation of partitioned services and also provides recommendations about how to deploy customer sites.
+In a multi-organization hosting environment in which tenant data and administration are isolated, the configuration of partitioned and shared services is important. This example provides a practical implementation of partitioned services and also provides recommendations about how to deploy customer sites.
This example details the following ways in which customer sites can be deployed in a farm:
This example details the following ways in which customer sites can be deployed
Use a dedicated application pool per customer only if you need to satisfy requirements for isolation. Use dedicated web applications for tenants that require customizations affecting resources that are shared across a web application, such as the web.config file.
-When combining multiple tenants in a single web application, use a dedicated web application for all authenticated content and a separate dedicated web application for all anonymous content. This will require two separate subscriptions IDs for tenants with both types of content. This will also simplify licensing.
+When combining multiple tenants in a single web application, use a dedicated web application for all authenticated content and a separate dedicated web application for all anonymous content. This method will require two separate subscriptions IDs for tenants with both types of content. This method swill also simplify licensing.
Do not allow full-trust code to be deployed to sites.
This tiered-environment design approach could provide different service level ag
## Security considerations <a name="begin"> </a>
-This section discusses various security considerations for planning and designing a multi-tenant SharePoint Server 2013 hosting platform. From this point forward, any section, such as the Organization Unit (OU) section, that talks about people picker configuration only works without additional customization with Windows authentication.
+This section discusses various security considerations for planning and designing a multi-tenant SharePoint Server 2013 hosting platform. From this point forward, any section, such as the Organization Unit (OU) section, that talks about people picker configuration only works without further customization with Windows authentication.
SharePoint Server 2013 supports many authentication methods and authentication providers for the following authentication types:
SharePoint Server 2013 supports many authentication methods and authentication p
- SAML token-based authentication
-The Windows authentication type takes advantage of your existing Windows authentication provider and the authentication protocols that a Windows domain environment uses to validate the credentials of connecting clients. Windows authentication methods, which are used by both claims-based authentication and classic mode, include the following:
+The Windows authentication type takes advantage of your existing Windows authentication provider and the authentication protocols that a Windows domain environment uses to validate the credentials of connecting clients. Windows authentication methods, which are used by both claims-based authentication and classic mode, include:
- NTLM
The Windows authentication type takes advantage of your existing Windows authent
- Basic
-Forms-based authentication is a claims-based identity management system that is based on ASP.NET membership and role provider authentication. Forms-based authentication can be used against credentials that are stored in an authentication provider, such as the following:
+Forms-based authentication is a claims-based identity management system that is based on ASP.NET membership and role provider authentication. Forms-based authentication can be used against credentials that are stored in an authentication provider, such as:
- Active Directory Domain Services (AD DS)
Forms-based authentication is a claims-based identity management system that is
Forms-based authentication validates users based on credentials that users enter into a logon form (typically a webpage). Unauthenticated requests are redirected to a logon page, where a user must provide valid credentials and submit the form. The system issues a cookie for authenticated requests that contains a key for reestablishing the identity for later requests.
-To use forms-based authentication to authenticate users against an identity management system that is not based on Windows or one that is external, you must register the membership provider and role manager in several web.config files. SharePoint Server 2013 uses the standard ASP.NET role manager interface to collect group information about the current user. Each ASP.NET role is treated as a domain group by the authorization process in SharePoint Server 2013. You register a role manager in a web.config file exactly as you register a membership provider for authentication.
+To use forms-based authentication to authenticate users against an identity management system that isn't based on Windows or one that is external, you must register the membership provider and role manager in several web.config files. SharePoint Server 2013 uses the standard ASP.NET role manager interface to collect group information about the current user. Each ASP.NET role is treated as a domain group by the authorization process in SharePoint Server 2013. You register a role manager in a web.config file exactly as you register a membership provider for authentication.
If you want to manage membership users or roles from the Central Administration website, you must register the membership provider and the role manager in the web.config file of the Central Administration website. You must also register the membership provider and the role manager in the web.config file of the web application that hosts the content and in the web.config file of the Security Token Service.
-SAML token-based authentication in SharePoint Server 2013 uses the SAML 1.1 protocol and the WS-Federation Passive Requestor Profile (WS-F PRP). It requires coordination with administrators of a claims-based environment, whether it is your own internal environment or a partner environment. If you use Active Directory Federation Services (AD FS) 2.0, you have a SAML token-based authentication environment.
+SAML token-based authentication in SharePoint Server 2013 uses the SAML 1.1 protocol and the WS-Federation Passive Requestor Profile (WS-F PRP). It requires coordination with administrators of a claims-based environment, whether it's your own internal environment or a partner environment. If you use Active Directory Federation Services (AD FS) 2.0, you have a SAML token-based authentication environment.
-For web applications that use claims-based authentication, People Picker is a control that is available within SharePoint Server 2013. The People Picker control uses claims providers to list, resolve, search, and determine the "friendly" display of users, groups, and claims. For additional information about people picker configuration, see [People Picker and claims providers overview](./people-picker-and-claims-providers-overview.md).
+For web applications that use claims-based authentication, People Picker is a control that is available within SharePoint Server 2013. The People Picker control uses claims providers to list, resolve, search, and determine the "friendly" display of users, groups, and claims. For more information about people picker configuration, see [People Picker and claims providers overview](./people-picker-and-claims-providers-overview.md).
-Zones represent different logical paths to gain access to the same sites in a web application. Each web application can include as many as five zones. When you create a web application, Central Administration creates the zone named **Default**. To create additional zones, extend the web application and select one of the remaining zone names: **Intranet**, **Extranet**, **Internet**, or **Custom**.
+Zones represent different logical paths to gain access to the same sites in a web application. Each web application can include as many as five zones. When you create a web application, Central Administration creates the zone named **Default**. To create more zones, extend the web application and select one of the remaining zone names: **Intranet**, **Extranet**, **Internet**, or **Custom**.
### Organizational Units
The SharePoint servers have a unique role not included in other servers in the d
#### Customers OU
-This top-level OU lets all user accounts to be segregated from the rest of the directory. The next level of OUs contains the customer OUs. There is one OU for each customer. This lets all user accounts and computer accounts of a customer to be segregated from those of other customers. Furthermore this is the required OU structure to support User Profile Synchronization in multi-tenant deployments.
+This top-level OU lets all user accounts to be segregated from the rest of the directory. The next level of OUs contains the customer OUs. There's one OU for each customer. This OU lets all user accounts and computer accounts of a customer to be segregated from those accounts of other customers. Furthermore, this OU structure is the one required to support User Profile Synchronization in multi-tenant deployments.
-To give the users the impression they are logging into their own custom domain, use the Active Directory Service Interfaces Editor (ADSI Edit) or another AD tool to edit the **uPNSuffixes** attribute of each Customer OU as shown in the following diagram.
+To give the users the impression they're logging into their own custom domain, use the Active Directory Service Interfaces Editor (ADSI Edit) or another AD tool to edit the **uPNSuffixes** attribute of each Customer OU as shown in the following diagram.
![This diagram shows the ADSI Property Editor Dialog for the uPNSuffixes attribute](../media/ADSIEdit.jpg)
Once the **uPNSuffixes** attribute of a Customer OU is configured, its value wil
#### User authentication
-User authentication is the validation of a user's identity against an authentication provider, which is a directory or database that contains the user's credentials and can confirm the user submitted them correctly. An example of an authentication provider is Active Directory Domain Services (AD DS). Other common names for an authentication provider are *user directory* and *attribute store* .
+User authentication is the validation of a user's identity against an authentication provider, which is a directory or database that contains the user's credentials and can confirm the user submitted them correctly. An example of an authentication provider is Active Directory Domain Services (AD DS). Other common names for an authentication provider are *user directory* and *attribute store*.
An authentication method is a specific exchange of account credentials and other information that assert a user's identity. The result of the authentication method is proof, typically in the form of a token that contains claims, that an authentication provider has authenticated a user.
Planning for user authentication types and methods should determine the followin
#### Active Directory Federation Services (AD FS)
-SharePoint Server 2013 supports claims-based authentication. Active Directory Federation Services (AD FS) can be configured to act as an Identity Provider Security Token Service (IP-STS) for a SharePoint Server 2013 web application. In this configuration, AD FS issues SAML-based security tokens consisting of claims so that client computers can access web applications that use claims-based authentication. You can use an alternative identity provider than AD FS. But it must support the WS-Federation standard. Also using AD FS configuration, custom code is required.
+SharePoint Server 2013 supports claims-based authentication. Active Directory Federation Services (AD FS) can be configured to act as an Identity Provider Security Token Service (IP-STS) for a SharePoint Server 2013 web application. In this configuration, AD FS issues SAML-based security tokens consisting of claims so that client computers can access web applications that use claims-based authentication. You can use an identity provider that's an alternative to AD FS. But it must support the WS-Federation standard. Also using AD FS configuration, custom code is required.
-For additional info about how to configure SAML-based claims authentication with AD FS for SharePoint Server 2013, see [Configure SAML-based claims authentication with AD FS in SharePoint Server](../security-for-sharepoint-server/security-for-sharepoint-server.md).
+For more information about how to configure SAML-based claims authentication with AD FS for SharePoint Server 2013, see [Configure SAML-based claims authentication with AD FS in SharePoint Server](../security-for-sharepoint-server/security-for-sharepoint-server.md).
## Management and operational considerations <a name="begin"> </a>
Capacity management is an ongoing process because no implementation remains stat
#### App management
-The apps for SharePoint provide a new method to deliver specific information or functionality to a SharePoint site. An app for SharePoint is a small, easy-to-use, stand-alone app that solves a specific end-user or business need. Site owners can discover and download apps for SharePoint from a public SharePoint Store or from their organization's internal App Catalog and install them on their SharePoint sites. These apps for SharePoint integrate the best of the web with SharePoint Server 2013. They do not replace SharePoint features and solution packages, which customize or increase SharePoint sites. Unlike features and solutions, which farm or site collection administrators have to install, apps for SharePoint are stand-alone applications that owners of sites can add to their SharePoint sites. The apps for SharePoint have a simple life-cycle: they can be installed, upgraded, and uninstalled by site owners.
+The apps for SharePoint provide a new method to deliver specific information or functionality to a SharePoint site. An app for SharePoint is a small, easy-to-use, stand-alone app that solves a specific end-user or business need. Site owners can discover and download apps for SharePoint from a public SharePoint Store or from their organization's internal App Catalog and install them on their SharePoint sites. These apps for SharePoint integrate the best of the web with SharePoint Server 2013. They don't replace SharePoint features and solution packages, which customize or increase SharePoint sites. Unlike features and solutions, which farm or site collection administrators have to install, apps for SharePoint are stand-alone applications that owners of sites can add to their SharePoint sites. The apps for SharePoint have a simple life-cycle: they can be installed, upgraded, and uninstalled by site owners.
The App Management Service in SharePoint Server 2013 is multi-tenancy aware. Most of app configuration and management functionality is exposed through the Tenant Administration site and allows each tenant administrator to configure their individual settings.
The App Management Service in SharePoint Server 2013 is multi-tenancy aware. Mos
When performing tenant-agnostic backup and restore operations on a multi-tenant SharePoint Server 2013 hosting platform, you can follow the general guidance for performing backup and restore operations on SharePoint Server 2013 environments, see [Backup and restore in SharePoint Server](./backup-and-recovery-overview.md).
-Notice that in SharePoint Server 2013, the Workflow platform is separate from the SharePoint platform. Therefore, backup and restore operations on the Workflow Manager should be coordinated with SharePoint backup and restore operations to ensure both remain in sync with one another. For additional guidance about how to plan backup and restore operations for Workflow Service Manager, see [Disaster Recovery and Scope Restore in Workflow Manager 1.0](/previous-versions/dotnet/workflow-manager/jj730570(v=azure.10))
+Notice that in SharePoint Server 2013, the Workflow platform is separate from the SharePoint platform. Therefore, backup and restore operations on the Workflow Manager should be coordinated with SharePoint backup and restore operations to ensure both remain in sync with one another. For more guidance about how to plan backup and restore operations for Workflow Service Manager, see [Disaster Recovery and Scope Restore in Workflow Manager 1.0](/previous-versions/dotnet/workflow-manager/jj730570(v=azure.10))
When you perform tenant-specific backup and restore operations on a multi-tenant SharePoint Server 2013 hosting platform, you might have to keep the following tenant-aware components in sync with one another: service applications, workflow, content databases, and site collections.
Service applications that are configured in Partition Mode have one or more asso
**App Management Service**
-The App Management service is the service application used for managing the app for SharePoint feature that is introduced in SharePoint Server 2013. The apps for SharePoint provide a new method to deliver specific information or functionality to a SharePoint site. An app for SharePoint is a small, easy-to-use, stand-alone app that solves a specific end-user or business need. The App Management Service does not support Partition Mode, however it is natively Site Subscription aware. In the multi-tenant SharePoint environment, most of App Management functionality (that is, Manage App Catalog, Manage App Licenses, App Permissions, and so on.) is obtained by using the Tenant Administration Site.
+The App Management service is the service application used for managing the app for SharePoint feature that is introduced in SharePoint Server 2013. The apps for SharePoint provide a new method to deliver specific information or functionality to a SharePoint site. An app for SharePoint is a small, easy-to-use, stand-alone app that solves a specific end-user or business need. The App Management Service doesn't support Partition Mode, however it's natively Site Subscription aware. In the multi-tenant SharePoint environment, most of App Management functionality (that is, Manage App Catalog, Manage App Licenses, App Permissions, and so on.) is obtained by using the Tenant Administration Site.
The following diagram shows App Management on the Tenant Administration Site.
The following diagram shows App Management on the Tenant Administration Site.
#### Business Data Connectivity service
-Once configured in partition mode, all configuration of the Business Data Connectivity service moves to tenant administration. However the Tenant Administration site template does not include the link to this page, which can be added using the customization technique in the Extending the Tenant Administration site template section
+Once configured in partition mode, all configuration of the Business Data Connectivity service moves to tenant administration. However, the Tenant Administration site template doesn't include the link to this page, which can be added using the customization technique in the Extending the Tenant Administration site template section
#### Secure Store service
-Once configured in partition mode, the generation of encryption keys remains a farm level configuration performed either via Central Administration or Windows PowerShell. The remainder of the Secure Store service configuration moves to tenant administration. However the Tenant Administration site template does not include the link to this page, which can be added using the customization technique in the Extending the Tenant Administration site template section.
+Once configured in partition mode, the generation of encryption keys remains a farm level configuration performed either via Central Administration or Windows PowerShell. The remainder of the Secure Store service configuration moves to tenant administration. However, the Tenant Administration site template doesn't include the link to this page, which can be added using the customization technique in the Extending the Tenant Administration site template section.
#### Managed metadata service
Write-Host "Tenant Site Collection Restore Script Completed!"
#### Monitoring
-There are many tools that allow you to monitor SharePoint Server 2013 and troubleshoot problems. Different tools cover different aspects of the environment, although there may be overlapping areas. Consider which tools can maximize your monitoring benefits. For additional guidance about how to plan monitoring for SharePoint Server 2013, see [Plan for monitoring in SharePoint Server](./monitoring-planning.md).
+There are many tools that allow you to monitor SharePoint Server 2013 and troubleshoot problems. Different tools cover different aspects of the environment, although there may be overlapping areas. Consider which tools can maximize your monitoring benefits. For more guidance about how to plan monitoring for SharePoint Server 2013, see [Plan for monitoring in SharePoint Server](./monitoring-planning.md).
#### Feature pack management
Write-Host "Feature Pack Created! " + $ffp.ID
In SharePoint Server 2013, a new licensing management capability has been added. Farm administrators can now assign licenses to users and enable runtime license checks. By using this new functionality, you can ensure that only users who have the appropriate license can use a specific feature. The functionality also simplifies the deployment model because you no longer have to build separate farms for standard and enterprise editions of SharePoint Server.
-User licenses are assigned by mapping claims to a known type of license. For example, a claim can be an Active Directory Domain Services (AD DS) Security group. By mapping the **ContosoFinanceDept** security group to an Enterprise license, you effectively assign an Enterprise license to all members of that group. Users who log on to SharePoint Server are assigned claims. SharePoint Server examines the claims of users to determine their license, if a user does not have a license to use a particular feature, SharePoint will block access to that feature at run time.
+User licenses are assigned by mapping claims to a known type of license. For example, a claim can be an Active Directory Domain Services (AD DS) Security group. By mapping the **ContosoFinanceDept** security group to an Enterprise license, you effectively assign an Enterprise license to all members of that group. Users who log on to SharePoint Server are assigned claims. SharePoint Server examines the claims of users to determine their license, if a user doesn't have a license to use a particular feature, SharePoint will block access to that feature at run time.
-This SharePoint Server 2013 license implementation is managed by using new Microsoft PowerShell cmdlets. By default, licensing is disabled in SharePoint Server. However administrators can opt to turn it on by using Microsoft PowerShell. For additional information about how to configure licensing in SharePoint Server 2013, see [Configure licensing in SharePoint Server](./monitoring-planning.md).
+This SharePoint Server 2013 license implementation is managed by using new Microsoft PowerShell cmdlets. By default, licensing is disabled in SharePoint Server. However administrators can opt to turn it on by using Microsoft PowerShell. For more information about how to configure licensing in SharePoint Server 2013, see [Configure licensing in SharePoint Server](./monitoring-planning.md).
#### Lifecycle management
-Whilst this white paper outlines the key infrastructure considerations when designing a multi-tenant SharePoint 2013 solution and it provides baseline scripts for configuration the overall management of the lifecycle of operations is imperative. For example custom tenant administration, de-provisioning of subscriptions, archiving, user management, self-service password reset and quotas are all common areas which require some combination of additional Windows PowerShell and customization effort in order to deliver a complete service offering. Each service provider will have different requirements in this sphere and it is incredibly important to ensure that these requirements are part of the initial scoping and design work for the infrastructure platform.
+Whilst this white paper outlines the key infrastructure considerations when designing a multi-tenant SharePoint 2013 solution and it provides baseline scripts for configuration the overall management of the lifecycle of operations is imperative. For example, custom tenant administration, de-provisioning of subscriptions, archiving, user management, self-service password reset, and quotas are all common areas that require some combination of more Windows PowerShell and customization effort in order to deliver a complete service offering. Each service provider will have different requirements in this sphere and it's incredibly important to ensure that these requirements are part of the initial scoping and design work for the infrastructure platform.
## Setup and configuration <a name="begin"> </a>
This section outlines the general steps for setting up and configuring a multi-t
## Acknowledgements <a name="begin"> </a>
-This section provides details and contains PowerShell scripts that demonstrate the creation and configuration of various components. These scripts are generally provided to demonstrate the configuration requirements for multi-tenancy and therefore do not represent the optimal provisioning order, however they can serve as the basis for developing your own customized end-to-end scripting solution.
+This section provides details and contains PowerShell scripts that demonstrate the creation and configuration of various components. These scripts are provided to demonstrate the configuration requirements for multi-tenancy and therefore don't represent the optimal provisioning order, however they can serve as the basis for developing your own customized end-to-end scripting solution.
-The Microsoft PowerShell scripts contained in the following sub-sections are based (either whole or in part) on the work of **Spencer Harbar** (http://www.harbar.net) and are reproduced here with his gracious consent. Please refer to the following documents for his original work.
+The Microsoft PowerShell scripts contained in the following sub-sections are based (either whole or in part) on the work of **Spencer Harbar** (http://www.harbar.net) and are reproduced here with his gracious consent. For more information on the original work of **Spencer Harbar**, see the following documents:
- http://www.harbar.net/articles/sp2013mt.aspx
The PowerShell scripts provided include variables, which should be modified to s
### Deployment example
-This section presents a deployment example which makes use of a single hosting web application using host named site collections and host header managed paths. It is deployed on a single server for the sake of simplicity, this is the intended design model for multi-tenancy with SharePoint 2013 and can be extended to a deployment where service instance roles are articulated across multiple computers. The deployment example uses HTTP for the web application. In a real deployment SSL should be used to protect sign-in, content and the authorization tokens used with SharePoint Apps and other OAuth2 related services such as Workflow Manager.
+This section presents a deployment example that makes use of a single hosting web application using host named site collections and host header managed paths. It's deployed on a single server for the sake of simplicity. This deployment example is the intended design model for multi-tenancy with SharePoint 2013 and can be extended to a deployment where service instance roles are articulated across multiple computers. The deployment example uses HTTP for the web application. In a real deployment SSL should be used to protect sign-in, content and the authorization tokens used with SharePoint Apps and other OAuth2 related services such as Workflow Manager.
#### DNS configuration
-Because host-named site collections will be used for a multi-tenant SharePoint environment, you must configure your DNS (that is, create appropriate DNS records, etc.) accordingly based on your plan. For additional guidance about how to plan host-named site collections for SharePoint Server 2013, see [Host-named site collection architecture and deployment (SharePoint 2013)](host-named-site-collection-architecture-and-deployment.md).
+Because host-named site collections will be used for a multi-tenant SharePoint environment, you must configure your DNS (that is, create appropriate DNS records, etc.) accordingly based on your plan. For more guidance about how to plan host-named site collections for SharePoint Server 2013, see [Host-named site collection architecture and deployment (SharePoint 2013)](host-named-site-collection-architecture-and-deployment.md).
-If you also plan to support apps for SharePoint, you must also configure DNS to support your environment. For additional information about how to configure an apps environment for SharePoint Server 2013, see [Configure an environment for apps for SharePoint Server](./configure-an-environment-for-apps-for-sharepoint.md).
+If you also plan to support apps for SharePoint, you must also configure DNS to support your environment. For more information about how to configure an apps environment for SharePoint Server 2013, see [Configure an environment for apps for SharePoint Server](./configure-an-environment-for-apps-for-sharepoint.md).
#### Active Directory configuration
-As described earlier, to support multi-tenancy in SharePoint, Active Directory must be correctly structured by creating a hierarchical Organization Unit structure to support User Profile Synchronization for each subscription. You also have to create appropriate service accounts for your environment. For additional information about how to plan service accounts for SharePoint Server 2013, see [Plan for administrative and service accounts in SharePoint Server](../security-for-sharepoint-server/plan-for-administrative-and-service-accounts.md). In this deployment example, the following three service accounts are used:
+As described earlier, to support multi-tenancy in SharePoint, Active Directory must be correctly structured by creating a hierarchical Organization Unit structure to support User Profile Synchronization for each subscription. You also have to create appropriate service accounts for your environment. For more information about how to plan service accounts for SharePoint Server 2013, see [Plan for administrative and service accounts in SharePoint Server](../security-for-sharepoint-server/plan-for-administrative-and-service-accounts.md). In this deployment example, the following three service accounts are used:
- **SPFarm** - the SharePoint Farm Account -- **SPServices** - the Application Pool identity which hosts Service Application endpoints
+- **SPServices** - the Application Pool identity that hosts Service Application endpoints
-- **SPContent** - the Application Pool identity which hosts the Content Web Application
+- **SPContent** - the Application Pool identity that hosts the Content Web Application
#### SharePoint farm creation and configuration
Write-Host "Farm Creation Done!"
#### Proxy Group, Hosting Web Application and Managed Paths
-Initially a Managed Account is created for the application pool hosting the content web application. A new proxy group is created, followed by the web application. Finally, configuration of the Web Application to allow self-service site creation and the creation of shared managed paths is performed. It is extremely important to create a "root" site collection in the hosting web application even though this site collection will not be accessed by end users. This is required for supportability and correct operational behavior of SharePoint 2013.
+Initially, a Managed Account is created for the application pool hosting the content web application. A new proxy group is created, followed by the web application. Finally, configuration of the Web Application to allow self-service site creation and the creation of shared managed paths is performed. It's important to create a "root" site collection in the hosting web application even though this site collection won't be accessed by end users. This "root" site collection is required for supportability and correct operational behavior of SharePoint 2013.
> [!NOTE] > This example uses HTTP for the web application.
Write-Host "Proxy Group and Web Application done!"
#### Non-partitioned services
-At this stage the non-partitioned service applications can be created. These service applications are either required in the farm for normal operations (for example the State Service) or do not require to be partitioned in order to support multi-tenancy as they do not store any data. To do this another managed account is required, and then each service application is created in turn.
+At this stage, the non-partitioned service applications can be created. These service applications are either required in the farm for normal operations (for example, the State Service) or don't require to be partitioned to support multi-tenancy as they don't store any data. To do this, another managed account is required, and then each service application is created in turn.
The following Microsoft PowerShell script shows how to create the non-partitioned service applications.
Write-Host "Non Partitioned Service Applications done!"
### Partitioned Service applications creation and configuration
-The following sections describe the Microsoft PowerShell procedures necessary to create and configure each service application which supports partitioning. The same general pattern applies to each service application with the exception of Search and User Profiles. However there are small differences related to the service application proxies.
+The following sections describe the Microsoft PowerShell procedures necessary to create and configure each service application that supports partitioning. The same general pattern applies to each service application except for Search and User Profiles. However there are small differences related to the service application proxies.
### Business Data Connectivity service
$proxyGroup | Add-SPServiceApplicationProxyGroupMember -Member $proxy
### Machine Translation service
-The Machine Translation service supports multi-tenancy by creating its service application in Partition Mode. There is no tenant-specific configuration and the service is managed at the farm level. Its database is effectively acting as a queue and therefore has to be partition/tenant aware.
+The Machine Translation service supports multi-tenancy by creating its service application in Partition Mode. There's no tenant-specific configuration and the service is managed at the farm level. Its database is effectively acting as a queue and therefore has to be partition/tenant aware.
The following Microsoft PowerShell script shows how to create the Machine Translation service application in Partition Mode.
$proxyGroup | Add-SPServiceApplicationProxyGroupMember -Member $proxy
### Secure Store service
-Once configured in partition mode, the generation of encryption keys remains a farm level configuration performed either via Central Administration or Windows PowerShell. The remainder of the Secure Store service configuration moves to tenant administration. However the Tenant Administration site template does not include the link to this page, which can be added using the customization technique in the Extending the Tenant Administration site template section.
+Once configured in partition mode, the generation of encryption keys remains a farm level configuration performed either via Central Administration or Windows PowerShell. The remainder of the Secure Store service configuration moves to tenant administration. However the Tenant Administration site template doesn't include the link to this page, which can be added using the customization technique in the Extending the Tenant Administration site template section.
The following Microsoft PowerShell script shows how to create the Secure Store Service application in Partition Mode and add it to a custom Service Proxy group.
Write-Host "Search complete!"
#### Word Automation Services
-The Word Automation Services service application supports Partition Mode. There is no cmdlet for creating a proxy.
+The Word Automation Services service application supports Partition Mode. There's no cmdlet for creating a proxy.
The following Microsoft PowerShell script shows how to create the Word Automation Services service application in Partition Mode.
$proxyGroup | Add-SPServiceApplicationProxyGroupMember -Member $proxy
#### User Profile Service
-The creation of the User Profile Service by using PowerShell as required when provisioning in partitioned mode presents a challenge when not running the Windows PowerShell as the SharePoint Farm account. In order to work around this, and in order to successfully start the User Profile Synchronization service, we leverage the **Start-Process** cmdlet and simulate executing the script as the farm account.
+The creation of the User Profile Service by using PowerShell as required when provisioning in partitioned mode presents a challenge when not running the Windows PowerShell as the SharePoint Farm account. To work around this challenge, and in order to successfully start the User Profile Synchronization service, we use the **Start-Process** cmdlet and simulate executing the script as the farm account.
Two scripts are required, the first script creates the UPA and the second script calls the first script.
Get-SPServiceApplication | ? {$_.Name -eq $upaName}
```
-The second script below performs the necessary work to call the UPA creation script and start the required service instances. The location of the UPA creation script should be updated in the **$upaScriptFile** variable. Additionally some required permissions are set on the UPA.
+The second script below performs the necessary work to call the UPA creation script and start the required service instances. The location of the UPA creation script should be updated in the **$upaScriptFile** variable. Additionally, some required permissions are set on the UPA.
``` $proxyGroupName = "Hosting Proxy Group"
Grant-ServiceAppPermission $upa $serviceUser "Full Control" $false
#### Information Rights Management configuration
-Information Rights Management support for multi-tenancy can be turned on by using the the SharePoint Central Administration website or the updated Microsoft PowerShell cmdlets.
+Information Rights Management support for multi-tenancy can be turned on by using the SharePoint Central Administration website or the updated Microsoft PowerShell cmdlets.
**Turn on Information Rights Management by using Central Administration**
Information Rights Management support for multi-tenancy can be turned on by usin
- **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.
+ - Administrators group on the server on which you're running the PowerShell cmdlets.
An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2013 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?view=sharepoint-ps&preserve-view=true).
+ > If you do not have permissions, contact your setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).
2. Open the **SharePoint Management Shell**.
$subscription=Get-SPSiteSubscription "http://www.contoso.com"
Set-SPSiteSubscriptionIRMConfig -identity $subscription -IrmEnabled -CertificateServerUrl "http://rms.contoso.com" ```
-Generally such configuration is performed as part of tenant provisioning.
+Such configuration is performed as part of tenant provisioning.
## Tenant provisioning and management <a name="begin"> </a>
To create a tenant, follow the steps in the table.
|2. Assign a feature pack to the site subscription and configure custom OU by using People Picker. <br/> |At the Microsoft PowerShell command prompt, type the following syntax: <br/> ```Set-SPSiteSubscriptionConfig -id $sub -FeaturePack $customerFeatures -UserAccountDirectoryPath "OU=$customerName,OU=Customers,DC=contoso,DC=com"```| |3. Create one or more site collections to be assigned to the site subscription. <br/> |At the Microsoft PowerShell command prompt, type the following syntax: <br/> ```Write-Host "Creating Member Site..." New-SPSite -url "http://$customerName.contoso.com" -SiteSubscription $sub -HostHeaderWebApplication $webApp -owneralias $customerTenantAdmin -owneremail $customerTenantAdminEmail -template sts#0 -ContentDatabase $contentDBName``````# create Tenant Admin site Write-Host "Creating Tenant Admin site..." New-SPSite -url "http://$customerName.contoso.com/admin" -SiteSubscription $sub -HostHeaderWebApplication $webApp -owneralias $customerTenantAdmin -owneremail $customerTenantAdminEmail -template tenantadmin#0 -AdministrationSiteType TenantAdministration -ContentDatabase $contentDBName``````Write-Host "Creating My Site Host..." New-SPSite -url "http://$customerName.contoso.com/mysites" -SiteSubscription $sub -HostHeaderWebApplication $webApp -owneralias $customerTenantAdmin -owneremail $customerTenantAdminEmail -template SPSMSITEHOST#0 -ContentDatabase $contentDBName```|
-The following PowerShell script shows how to create a tenant admin site that uses the **TENANTADMIN#0** template. If the tenant is configured to use an Enterprise Feature Pack, the Microsoft PowerShell script performs additional operations, that is, it creates the My Sites collection.
+The following PowerShell script shows how to create a tenant admin site that uses the **TENANTADMIN#0** template. If the tenant is configured to use an Enterprise Feature Pack, the Microsoft PowerShell script performs more operations, that is, it creates the My Sites collection.
``` Add-PSSnapin Microsoft.SharePoint.Powershell -EA 0
Write-Host "Tenant Provisioning Script Completed!"
```
-This approach can be further customized to contain other tenant configuration such as for Workflow, Apps and IRM. Generally such script is encapsulated into a function or custom cmdlets which enables it to be run repeatedly for future tenants.
+This approach can be further customized to contain other tenant configuration such as for Workflow, Apps, and IRM. Such script is encapsulated into a function or custom cmdlets, which enables it to be run repeatedly for future tenants.
## Workflow service <a name="begin"> </a>
-SharePoint Server 2013 brings a major advancement to workflow, including enterprise features such as fully declarative authoring, REST and Service Bus messaging, elastic scalability, and managed service reliability. SharePoint 2013 can use a new workflow service built on the Windows Workflow Foundation components of the .NET Framework 4.5. The new service is called Workflow Manager and it is designed to play a central role in the enterprise.
+SharePoint Server 2013 brings a major advancement to workflow, including enterprise features such as fully declarative authoring, REST and Service Bus messaging, elastic scalability, and managed service reliability. SharePoint 2013 can use a new workflow service built on the Windows Workflow Foundation components of the .NET Framework 4.5. The new service is called Workflow Manager and it's designed to play a central role in the enterprise.
-The SharePoint 2013 Workflow platform becomes available to you, and your tools, only after you download and install the new Workflow Manager Service and configure it to communicate with the SharePoint Server 2013 farm. For additional information about how to install and configure the Workflow Manager Service for SharePoint 2013, see [Install and configure workflow for SharePoint Server](../governance/install-and-configure-workflow-for-sharepoint-server.md).
+The SharePoint 2013 Workflow platform becomes available to you, and your tools, only after you download and install the new Workflow Manager Service and configure it to communicate with the SharePoint Server 2013 farm. For more information about how to install and configure the Workflow Manager Service for SharePoint 2013, see [Install and configure workflow for SharePoint Server](../governance/install-and-configure-workflow-for-sharepoint-server.md).
-To configure the Workflow Service, use the **Register-SPWorkflowService** cmdlet to register the farm with the Workflow Service Manager in Partition Mode. In doing this, use the **SPSite** parameter to pass the URL of any existing tenant site collection from your Farm and use the **ScopeName** parameter to define a named workflow scope for your farm.
+To configure the Workflow Service, use the **Register-SPWorkflowService** cmdlet to register the farm with the Workflow Service Manager in Partition Mode. In doing this farm registration, use the **SPSite** parameter to pass the URL of any existing tenant site collection from your Farm and use the **ScopeName** parameter to define a named workflow scope for your farm.
The following Windows PowerShell script shows how to register the SharePoint farm with the Workflow Service Manager in Partition Mode.
Register-SPWorkflowService -SPSite "http://tenant.contoso.com" -WorkflowHostUri
Write-Host "Farm Workflow Registration Script Completed!" ```
-To enable a specific tenant for SharePoint Workflow, you must configure the workflow service proxy. In doing this, obtain a reference to the root site collection of the tenant and register it with the workflow service proxy.
+To enable a specific tenant for SharePoint Workflow, you must configure the workflow service proxy. In doing this configuration, obtain a reference to the root site collection of the tenant and register it with the workflow service proxy.
The following PowerShell script shows how to enable a tenant for SharePoint Workflow.
$wfProxy.Connect($site)
Write-Host "Tenant Workflow Registration Script Completed!" ```
-After the tenant is configured to use Workflow Service Manager, you are then able to use SharePoint Designer to create workflows using the SharePoint 2013 Workflow option as shown in the following diagram.
+After the tenant is configured to use Workflow Service Manager, you're then able to use SharePoint Designer to create workflows using the SharePoint 2013 Workflow option as shown in the following diagram.
![This diagram shows the SharePoint 2013 Workflow option in SharePoint Designer](../media/Workflow_Tenant.jpg)
The following feature definition shows how to add a new group, several links, an
```
-For additional information about custom actions, such as the default IDs for built-in links, see [Custom Action Definition Schema](/previous-versions/office/developer/sharepoint-2010/ms465980(v=office.14)).
+For more information about custom actions, such as the default IDs for built-in links, see [Custom Action Definition Schema](/previous-versions/office/developer/sharepoint-2010/ms465980(v=office.14)).
#### Customizing the ribbon
The following XML shows how to replace the functionality of the **Disk Quota** b
```
-For additional information about how to customize the Server ribbon, see [Customizing the Server Ribbon](/previous-versions/office/developer/sharepoint-2010/ee539395(v=office.14)).
+For more information about how to customize the Server ribbon, see [Customizing the Server Ribbon](/previous-versions/office/developer/sharepoint-2010/ee539395(v=office.14)).
#### Extending a site subscription using custom properties
SharePoint Variations Overview https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/variations-overview.md
description: "Learn about variations and the benefits and scenarios for using va
[!INCLUDE[appliesto-2013-2016-2019-SUB-SPO-md](../includes/appliesto-2013-2016-2019-SUB-SPO-md.md)]
-The variations feature in SharePoint Server and SharePoint in Microsoft 365 makes content available to specific audiences on different sites by syncing content from a source variation site to each target variation site. When users visit the root site, they are redirected to the appropriate variation site, based on the language setting of their web browser. Content on a target variation site can be translated into other languages before it is published. Variations can be used only on sites that are created by using one of the Publishing site templates, or on sites for which the SharePoint Server Publishing Infrastructure feature was activated.
+The variations feature in SharePoint Server and SharePoint in Microsoft 365 syncs content from a source variation site to each target variation site to make the content available to specific audiences on different sites. When users visit the root site, they're redirected to the appropriate variation site, based on the language setting of their web browser. Content on a target variation site can be translated into other languages before it's published. You can use variations only on sites that are created by using one of the Publishing site templates, or on sites for which the SharePoint Server Publishing Infrastructure feature was activated.
-This article contains an overview of the variations feature. It describes the elements of the variations feature; provides an overview of site, list, and page creation for variation sites; lists some limitations of variations; and describes scenarios for using variations in SharePoint Server. This article does not describe the tasks that are involved in planning a solution that uses variations. For info about how to plan to use variations in your solution, see [Plan for variations in SharePoint Server](plan-for-variations.md). This article also does not describe how to create variation labels and hierarchies. For info about how to create a variation site, see [Create a multi-language website](https://go.microsoft.com/fwlink/p/?LinkId=279696).
+This article contains an overview of the variations feature. It describes the elements of the variations feature; provides an overview of site, list, and page creation for variation sites; lists some limitations of variations; and describes scenarios for using variations in SharePoint Server. This article doesn't describe the tasks that are involved in planning a solution that uses variations. For info about how to plan to use variations in your solution, see [Plan for variations in SharePoint Server](plan-for-variations.md). This article also doesn't describe how to create variation labels and hierarchies. For info about how to create a variation site, see [Create a multi-language website](https://go.microsoft.com/fwlink/p/?LinkId=279696).
> [!IMPORTANT] > - The variations will remain supported but deprecated for the SharePoint Server 2019 release. For more info, see [What's deprecated or removed from SharePoint Server 2019](../what-s-new/what-s-deprecated-or-removed-from-sharepoint-server-2019.md#variations).
This article contains an overview of the variations feature. It describes the el
## Use and benefits of variations <a name="use"> </a>
-Many organizations have a global reach. However, even in domestic markets, organizations must reach a diverse user base that might speak many languages or that might have to have specific information that is based on regional differences. These types of organizations need websites that deliver customized content to suit different cultures, different markets, and different geographic regions. Producing and maintaining different versions of a site can be difficult and time-consuming. By using the variations feature as part of a SharePoint Server 2013 solution, site architects and site administrators can simplify the process of producing and maintaining these sites. The variations feature automates the creation, management, synchronization, and translation of sites, lists, and pages, which eliminates having to manually create a site and all associated lists and pages for each instance of a needed variation.
+Many organizations have a global reach. However, even in domestic markets, organizations have to reach a diverse user base speaking many languages or having specific information based on regional differences. These types of organizations need websites that deliver customized content to suit different cultures, different markets, and different geographic regions. Producing and maintaining different versions of a site can be difficult and time-consuming. By using the variations feature as part of a SharePoint Server 2013 solution, site architects and site administrators can simplify the process of producing and maintaining these sites. The variations feature automates the creation, management, synchronization, and translation of sites, lists, and pages, thereby eliminating the need to manually create a site and all associated lists and pages for each instance of a needed variation.
## Scenarios for using variations <a name="scenarios"> </a> You can use variations to create sites, lists, and page content for specific languages. In this scenario, most of the content is authored in the language of the source variation site and synced to some or all of the target variation sites for translation into different languages. For example, the content might be authored in English and be synced to target variation sites for translation into German, French, and Spanish.
-You can also use variations to create content for specific locales. For example, a company based in North America might have target variation sites for the following locales: English (United States), English (Canada), French (Canada), and Spanish (Mexico). Most of the content is authored in English (United States), and the variation feature syncs that content to the target variation sites. Content on the French (Canada) and Spanish (Mexico) site is translated into French and Spanish, whereas content for English (Canada) is edited to account for regional differences in United States and Canadian English. Other content that is unique to a specific locale is created on the target variation sites for which it is needed.
+You can also use variations to create content for specific locales. For example, a company based in North America might have target variation sites for the following locales: English (United States), English (Canada), French (Canada), and Spanish (Mexico). Most of the content is authored in English (United States), and the variation feature syncs that content to the target variation sites. Content on the French (Canada) and Spanish (Mexico) site is translated into French and Spanish, whereas content for English (Canada) is edited to account for regional differences in United States and Canadian English. Other content that is unique to a specific locale is created on the target variation sites for which it's needed.
-In SharePoint Server 2010, you could use variations to create sites for different mobile devices, or that used different branding. In SharePoint Server 2016, variations is used only for multilingual sites. To create sites for different mobile devices, use Device Channels. To create sites that use different branding, use cross-site publishing. [Plan for cross-site publishing in SharePoint Server](plan-for-cross-site-publishing.md).
+In SharePoint Server 2010, you could use variations to create sites for different mobile devices, or that used different branding. In SharePoint Server 2016, variations are used only for multilingual sites. To create sites for different mobile devices, use Device Channels. To create sites that use different branding, use cross-site publishing. [Plan for cross-site publishing in SharePoint Server](plan-for-cross-site-publishing.md).
## Elements of variations <a name="elements"> </a> The variations feature consists of the following elements: -- **Variation root site** The variation root site provides the URL for all source and target variation sites and contains the landing page that redirects users to the correct variation site. This is not the same as the root site of a site collection, although you can specify the root site of a site collection to also be the root site of the variations hierarchy.
+- **Variation root site** The variation root site provides the URL for all source and target variation sites and contains the landing page that redirects users to the correct variation site. This site isn't the same as the root site of a site collection, although you can specify the root site of a site collection to also be the root site of the variations hierarchy.
- **Variation labels** A variation label is an identifier that names a new variation site. Variations of a site are defined by creating variation labels, one for each planned variation.
The variations feature consists of the following elements:
- **Variation sites** Variation sites are the sites that are created based on the defined variation labels. There are two types of variation sites:
- - **Source variation site** The source variation site is the site where shared content is authored and published, and it is the site from which the shared content is synced with target variation sites. There can be only one source variation site in a single site collection. After a source variation site is selected, it cannot be changed.
+ - **Source variation site** The source variation site is the site where shared content is authored and published, and it's the site from which the shared content is synced with target variation sites. There can be only one source variation site in a single site collection. After a source variation site is selected, it can't be changed.
- - **Target variation sites** The target variation sites receive most of their content from the source variation site. New content can be created on a target variation site. However, that content is not synced with other sites and is unique to the site on which it was created.
+ - **Target variation sites** The target variation sites receive most of their content from the source variation site. New content can be created on a target variation site. However, that content isn't synced with other sites and is unique to the site on which it was created.
- **Variations hierarchy** The variations hierarchy is the complete set of sites in all variation labels.
The variations feature consists of the following elements:
The variations feature creates sites and syncs content and supported list items from a source variation site to one or more target variation sites. By default, the variations feature syncs publishing pages from the Pages library of the source variation site, and any lists that are configured to be synced to specific target variation sites.
-By default, when users visit the root site, they are redirected to the appropriate variation site, based on the language setting of their web browser. For example, if a user's default browser language is French, SharePoint Server redirects that user to the French variation site. You can customize this behavior by replacing the default redirection page, VariationRoot.aspx, with a different page. This new page can implement logic that identifies the user's preferred language. For info about how to customize variation sites redirection, see [How to: Customize the Variation Root Landing Logic](/previous-versions/office/developer/sharepoint-2010/ms562040(v=office.14)).
+By default, when users visit the root site, they're redirected to the appropriate variation site, based on the language setting of their web browser. For example, if a user's default browser language is French, SharePoint Server redirects that user to the French variation site. You can customize this behavior by replacing the default redirection page, VariationRoot.aspx, with a different page. This new page can implement logic that identifies the user's preferred language. For info about how to customize variation sites redirection, see [How to: Customize the Variation Root Landing Logic](/previous-versions/office/developer/sharepoint-2010/ms562040(v=office.14)).
### Variation labels
The following illustration provides an example of a variation site hierarchy, an
![Planning site variations](../media/Site_Variations.gif)
-Three variation labels, "EN," "FR," and "DE," are created on the root site http://contoso.com. When the variations hierarchy is created, the corresponding variation sites, labeled "EN," "FR," and "DE," are created one level below the variation root site. Because site "http://contoso.com/EN" is specified as the source variation site, lists and pages that are authored and published on site "http://contoso.com/EN" are synced to the target variation sites, "http://contoso.com/FR" and "http://contoso.com/DE."
+Three variation labels, "EN," "FR," and "DE," are created on the root site https://contoso.com. When the variations hierarchy is created, the corresponding variation sites, labeled "EN," "FR," and "DE," are created one level below the variation root site. Because site "https://contoso.com/EN" is specified as the source variation site, lists and pages that are authored and published on site "https://contoso.com/EN" are synced to the target variation sites, "https://contoso.com/FR" and "https://contoso.com/DE."
-When you create a variation label, you select a locale for it to use. The locale setting assists with browser redirection and regional settings such as sort order and calendar. It does not affect the language of the user interface. If language packs were installed on the front-end web server, you can also select a language for the variation site. The language setting in SharePoint Server determines the language of the user interface on the variation site. If no language packs were installed, the option to select a language is not available, and the variation site uses the default language of the SharePoint Server installation on the server, regardless of the locale that is selected for the variation label. For example, if SharePoint Server was installed by using the English version, and no language packs were installed, when a new variation label is created for the Japanese locale, the user interface for the new variation target site is in English, not Japanese. If you want the user interface of a target variation site to be displayed using a specific language, you should install the language pack for each language before you create the variation sites. If a language pack is not available when a target variation site is created, the target variation site can still be created, and users can change the alternate language for a site by using the multilingual user interface. For information about the multilingual user interface, see [Plan for multilingual sites in SharePoint Server](../sites/plan-for-multilingual-sites.md). For info about how to install language packs, see [Install or uninstall language packs for SharePoint Server 2016](../install/install-uninstall-language-packs-2019.md).
+When you create a variation label, you select a locale for it to use. The locale setting assists with browser redirection and regional settings such as sort order and calendar. It doesn't affect the language of the user interface. If language packs were installed on the front-end web server, you can also select a language for the variation site. The language setting in SharePoint Server determines the language of the user interface on the variation site. If no language packs were installed, the option to select a language isn't available, and the variation site uses the default language of the SharePoint Server installation on the server, regardless of the locale that is selected for the variation label. For example, if SharePoint Server was installed by using the English version, and no language packs were installed, when a new variation label is created for the Japanese locale, the user interface for the new variation target site is in English, not Japanese. If you want the user interface of a target variation site to be displayed using a specific language, you should install the language pack for each language before you create the variation sites. If a language pack isn't available when a target variation site is created, the target variation site can still be created, and users can change the alternate language for a site by using the multilingual user interface. For information about the multilingual user interface, see [Plan for multilingual sites in SharePoint Server](../sites/plan-for-multilingual-sites.md). For info about how to install language packs, see [Install or uninstall language packs for SharePoint Server 2016](../install/install-uninstall-language-packs-2019.md).
When you create a variations hierarchy, a navigation term set is created for each variation label. By default, the term set for the source variation label is named Variations Navigation. The term set for a target variation label is named Variations Navigation ( _LabelName_). For example, if you have a target label named en-ca, the term set for that label will be named Variations Navigation (en-ca). By default, when the variations feature creates a target page for the first time, a corresponding navigation term is also created on the target variation site. When you export a page for translation, its associated navigation term is also exported.
The **Variations Settings** page contains the following options:
- **Site, List, and Page Creation Behavior** Determines whether sites, lists, and pages on the source variation site are created automatically on the target variation sites. By default, **Create Everywhere** is enabled. If you enable **Create Selectively**, the first time that you sync sites, lists, and pages from the source variation site to target variation sites, you must do so manually. Subsequent updates to items on the source variation site will be synced based on the target label sync preferences. -- **Recreate Deleted Target Page** Determines whether a page should be re-created on a target variation site if the page was deleted from the target variation site, and the page on the source variation site was republished. By default, this option is enabled. If you disable this option, deleted pages are not re-created on target variation sites. For example, consider the case in which a content author creates a page on the source variation site that is not relevant to a target variation site. However, because **Create Everywhere** is enabled, the page is created automatically on the target variation site, and the target label content owner later deletes the unwanted target page. The next time that the content author updates the source page, the page will not be re-created on the target variation site.
+- **Recreate Deleted Target Page** Determines whether a page should be re-created on a target variation site if the page was deleted from the target variation site, and the page on the source variation site was republished. By default, this option is enabled. If you disable this option, deleted pages aren't re-created on target variation sites. For example, consider the case in which a content author creates a page on the source variation site that isn't relevant to a target variation site. However, because **Create Everywhere** is enabled, the page is created automatically on the target variation site, and the target label content owner later deletes the unwanted target page. The next time that the content author updates the source page, the page won't be re-created on the target variation site.
- **Update Target Page Web Parts** Determines whether changes that were made to Web Parts on pages on a source variation site are also made on pages on target variation sites. By default, this option is enabled. -- **Notification** Sends an email message to the contact of the target label of a target variation site when a new page or site is created or to the contact person of the specified page when a page is updated with revisions from the source variation site. If the label does not have a contact, then the email message is sent to the contact of the welcome page of a target variation site. By default, this option is enabled.
+- **Notification** Sends an email message to the contact of the target label of a target variation site when a new page or site is created or to the contact person of the specified page when a page is updated with revisions from the source variation site. If the label doesn't have a contact, then the email message is sent to the contact of the welcome page of a target variation site. By default, this option is enabled.
For info about how to specify variations settings, see [Create a multi-language website](https://go.microsoft.com/fwlink/p/?LinkId=279696).
The variations feature uses timer jobs to perform tasks such as creating and pro
- **Variations Propagate List Items Job Definition** Creates and updates list items on target variation sites after a list is configured to send items to specific target variation labels. By default, this timer job runs every 15 minutes. -- **Variations Propagate Page Job Definition** Creates and updates pages on target variation sites after a page on the source variation site is approved or after it is manually submitted by a user. By default, this timer job runs every 15 minutes.
+- **Variations Propagate Page Job Definition** Creates and updates pages on target variation sites after a page on the source variation site is approved or after it's manually submitted by a user. By default, this timer job runs every 15 minutes.
- **Variations Propagate Sites and Lists Job Definition** Creates variation sites and lists when the **Create Everywhere** option is enabled. By default, this timer job runs every 30 minutes. > [!NOTE]
-> Timer jobs are not configurable in SharePoint in Microsoft 365.
+> Timer jobs aren't configurable in SharePoint in Microsoft 365.
For information about timer jobs, see [View timer job status in SharePoint Server 2016](view-timer-job-status.md). ## Understanding source variation and target variation site creation <a name="sitecreation"> </a>
-Source variation and target variation sites are always created one level below the variation root site. Each variation site is created by using the same site template that is used to create the variation root site. This means that by default, each variation site will use the same master page as the variation root site. However, each variation site can use separate master pages, page layouts, and CSS files. This is useful when you want to have separate layouts for different locales. For example, you can use a right-to-left layout for one language and a left-to-right layout for another language. For info, see [Overview of the SharePoint 2013 page model](/sharepoint/dev/general-development/overview-of-the-sharepoint-page-model).
+Source variation and target variation sites are always created one level below the variation root site. Each variation site is created by using the same site template that's used to create the variation root site. This same-template usage means that by default, each variation site will use the same master page as the variation root site. However, each variation site can use separate master pages, page layouts, and CSS files. This provision is useful when you want to have separate layouts for different locales. For example, you can use a right-to-left layout for one language and a left-to-right layout for another language. For info, see [Overview of the SharePoint 2013 page model](/sharepoint/dev/general-development/overview-of-the-sharepoint-page-model).
When the variations hierarchy is first created, only sites that are based on the list of defined variation labels are created. If the variation root site has sites below it in a hierarchical site structure, and you want to include those sites in the hierarchical site structure of each variation site, you must manually create the hierarchical structure of those sites below the source variation site after you create the variation hierarchy. By default, the next time that the Variations Create Hierarchies Job Definition timer job runs, the sites are synced only to any new target variation sites that are created at that time. For info about how sites below the source variation site are created on existing target variation sites, see [Understanding site, list, and page creation](variations-overview.md#pagecreation) later in this article.
After the variations hierarchy is first created, when you add a new label to the
## Understanding site, list, and page creation <a name="pagecreation"> </a>
-By default, sites that are created below the source variation site, and lists and pages that are published on the source variation site or on any sites below it in the site hierarchy are automatically synced to the target variation sites. The following list types (or lists that inherit from these types) are supported:
+By default, the following components are synced automatically to the target variation sites:
+
+- Sites that are created below the source variation site
+- Lists and pages that are published on the source variation site or on any sites below it in the site hierarchy
+
+The following list types (or lists that inherit from these types) are supported:
- 100 - Generic list
-
- 101 - Document library
-
- 104 - Announcements list
-
- 109 - Picture library
-
+ If **Create Selectively** is enabled, you must manually create any sites, lists, and pages on the selected target variation sites. This section describes the ways in which sites, lists, and pages are created on target variation sites. ### Site creation
-The first time that the Variations Create Hierarchies Job Definition timer job runs and creates the variations hierarchy from the list of variation labels, only the source variation and target variation sites are created. After the source variation site is created, you can create sites below it in the site hierarchy, and those sites are then created on the existing target variation sites the next time that the Variations Propagate Sites and Lists Job Definition timer job runs. If **Create Selectively** is enabled, use the **Site Variation Settings** page on any site that is below the source variation site to manually create a target variation of the current site on one or more target variation sites. The new site is created on the specified target variation site when the next Variations Propagate Sites and Lists Job Definition timer job runs. You can do this any time that **Create Selectively** is enabled.
+When the Variations Create Hierarchies Job Definition timer job runs for the first time and creates the variations hierarchy from the list of variation labels, only the source variation and target variation sites are created. After the source variation site is created, you can create sites below it in the site hierarchy, and those sites are then created on the existing target variation sites the next time that the Variations Propagate Sites and Lists Job Definition timer job runs. If **Create Selectively** is enabled, use the **Site Variation Settings** page on any site that is below the source variation site to manually create a target variation of the current site on one or more target variation sites. The new site is created on the specified target variation site when the next Variations Propagate Sites and Lists Job Definition timer job runs. You can create a target variation of the current site anytime after **Create Selectively** is enabled.
> [!NOTE]
-> When source variation and target variation sites are created, they are created by using the default site definition provided by the template selected when the source label was created. No custom site configurations or settings are synced to the new sites. If you want the source variation and target variation sites to have custom site configurations or settings, such as navigation customizations, you must make those changes on each site after you create the variations hierarchy.
+> When source variation and target variation sites are created, they're created by using the default site definition provided by the template selected when the source label was created. No custom site configurations or settings are synced to the new sites. If you want the source variation and target variation sites to have custom site configurations or settings, such as navigation customizations, you must make those changes on each site after you create the variations hierarchy.
### List and page creation
-List items are synced to variation target sites only when the list on the source variation site is configured to specify the target variation sites to which they should be synced. By default, when a list is configured to be synced to specific target variation sites, it is synced when the next Variations Propagate Sites and Lists Job Definition timer job runs. If a new item is added to a list that has already been synced to target variation sites, it is synced when the next Variations Propagate List Items Job Definition timer job runs. If a new target variation label is added after the variations hierarchy is created, the list will be created on the new target variation site. By default, content approval is enabled on target lists. When a new item is synced to a target list, it must be approved before it will appear in a Content Query Web Part on the target variation site.
+List items sync with variation target sites only when the list on the source variation site is configured to specify the target variation sites to which they should be synced. By default, list syncs with specific target variation sites only after it's configured so, and when the next Variations Propagate Sites and Lists Job Definition timer job runs. If a new item is added to a list that has already been synced to target variation sites, it's synced when the next Variations Propagate List Items Job Definition timer job runs. If a new target variation label is added after the variations hierarchy is created, the list will be created on the new target variation site. By default, content approval is enabled on target lists. When a new item is synced to a target list, it must be approved before it will appear in a Content Query Web Part on the target variation site.
> [!NOTE]
-> Although you can specify individual pages that you want to sync to specific target labels, you cannot sync individual list items. You can only specify a complete list to sync to specific target labels.
+> Although you can specify individual pages that you want to sync to specific target labels, you can't sync individual list items. You can only specify a complete list to sync to specific target labels.
-If the **Publishing Site** template was selected when the source variation site was created, pages on the source variation site or on any site below it in the site hierarchy must be published before they are eligible to be synced to target variation sites. If the **Publishing Site with Workflow** template was selected, pages must be approved for publication by using the publishing workflow before they are eligible to be synced to target variation sites. By default, after a new page is published or approved for publication, if it uses workflows, it is synced to all target variation sites when the next Variations Propagate Page Job Definition timer job runs. If the page was published previously and is changed and republished on the source variation site, and the **Automatically update target variation pages** setting is selected for the target labels, the page is synced to all target variation sites when the next Variations Propagate Page Job Definition timer job runs.
+If the **Publishing Site** template was selected when the source variation site was created, pages on the source variation site or on any site below it in the site hierarchy must be published before they're eligible to be synced to target variation sites. If the **Publishing Site with Workflow** template was selected, pages must be approved for publication by using the publishing workflow before they're eligible to be synced to target variation sites. By default, after a new page is published or approved for publication, if it uses workflows, it's synced to all target variation sites when the next Variations Propagate Page Job Definition timer job runs. If the page was published previously and is changed and republished on the source variation site, and the **Automatically update target variation pages** setting is selected for the target labels, the page is synced to all target variation sites when the next Variations Propagate Page Job Definition timer job runs.
> [!NOTE]
-> On target variation sites, a page that is synced from the source variation site is always assigned a minor version number. If the page is new to the target site, it is assigned version 0.1. If the page already exists on the target variation site, the synced page is assigned the next available minor version number. For example, if a target variation site has version 2.1 of a page and a new variation of that page is synced to the target site, the page becomes version 2.2. Pages and additional resources, such as images that are approved for publishing on the source variation site, are synced to the target variation site together with their **Approval** status set to **Draft**, and they must be approved before they can be viewed by readers of the site.
+> On target variation sites, a page that is synced from the source variation site is always assigned a minor version number. If the page is new to the target site, it's assigned version 0.1. If the page already exists on the target variation site, the synced page is assigned the next available minor version number. For example, if a target variation site has version 2.1 of a page and a new variation of that page is synced to the target site, the page becomes version 2.2. Pages and additional resources, such as images that are approved for publishing on the source variation site, are synced to the target variation site together with their **Approval** status set to **Draft**, and they must be approved before they can be viewed by readers of the site.
-If **Create Selectively** is enabled, a user must create the page for a specific variation label by using the **Create new targets** command in the **Variations** group on the **Publish** tab of the page on the source variation site. The new page is synced to one or more target variation sites when the next Variations Propagate Page Job Definition timer job runs. If the page was published previously and is changed and republished on the source variation site, it is synced only to the specified target variation site when the next Variations Propagate Page Job Definition timer job runs. For info about how to enable **Create Selectively** for variation pages, see [Create a multi-language website](https://go.microsoft.com/fwlink/p/?LinkId=279696).
+If **Create Selectively** is enabled, a user must create the page for a specific variation label by using the **Create new targets** command in the **Variations** group on the **Publish** tab of the page on the source variation site. The new page is synced to one or more target variation sites when the next Variations Propagate Page Job Definition timer job runs. If the page was published previously and is changed and republished on the source variation site, it's synced only to the specified target variation site when the next Variations Propagate Page Job Definition timer job runs. For info about how to enable **Create Selectively** for variation pages, see [Create a multi-language website](https://go.microsoft.com/fwlink/p/?LinkId=279696).
-By default, when a page that was synced from the source variation site is deleted from a target variation site, that page is re-created on the target variation site the next time that it is published on the source variation site and the next time that the Variations Propagate Page Job Definition timer job runs. If **Recreate Deleted Target Page** is disabled, deleted pages are not re-created on the target variation sites.
+By default, when a page that was synced from the source variation site is deleted from a target variation site, that page is re-created on the target variation site the next time it's published on the source variation site and the next time that the Variations Propagate Page Job Definition timer job runs. If **Recreate Deleted Target Page** is disabled, deleted pages aren't re-created on the target variation sites.
For info about how to create variation source pages and how to work with content on variation target pages, see [Create a multi-language website](https://go.microsoft.com/fwlink/p/?LinkId=279696).
For info about how to create variation source pages and how to work with content
The following list contains info about the limitations of the variations feature in SharePoint Server: -- **Variations feature is a single-tier hierarchy.** The source and target variation sites exist at the same level within the site hierarchy, one level down from the variations root site. However, you can have only one source variation site per site collection. A site cannot be both a source and a target site. You can sync content from a source variation site to one or more target variation sites, but you cannot sync content from one target variation site to another target variation site. For example, if you have a source variation site in English (United States), and a target variation site in French (France), which has a French (Canada) site below it, the variations feature will only sync content from the English (United States) source variation site to the French (France) target variation site. The variations feature cannot also sync content from the French target variation site to the French (Canada) site below it.
+- **Variations feature is a single-tier hierarchy.** The source and target variation sites exist at the same level within the site hierarchy, one level down from the variations root site. However, you can have only one source variation site per site collection. A site can't be both a source and a target site. You can sync content from a source variation site to one or more target variation sites, but you can't sync content from one target variation site to another target variation site. For example, if you have a source variation site in English (United States), and a target variation site in French (France), which has a French (Canada) site below it, the variations feature will only sync content from the English (United States) source variation site to the French (France) target variation site. The variations feature can't also sync content from the French target variation site to the French (Canada) site below it.
You can use variations together with cross-site publishing to reuse content from one variation site in the context of another variation site. For example, you could reuse content from the French (France) site on the French (Canada) site. For more info, see [Plan the logical architecture for cross-site publishing in SharePoint Server](plan-the-logical-architecture-for-cross-site-publishing.md). -- **Content syncing is unidirectional.** The variations feature syncs content from a source variation site to one or more target variation sites. You cannot use the variations feature to sync content from a target variation site back to a source variation site. Also, target variation sites cannot sync content to other target variation sites.
+- **Content syncing is unidirectional.** The variations feature syncs content from a source variation site to one or more target variation sites. You can't use the variations feature to sync content from a target variation site back to a source variation site. Also, target variation sites can't sync content to other target variation sites.
## See also <a name="limitations"> </a>
SharePoint Plan And Manage Cases In The Ediscovery Center https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/governance/plan-and-manage-cases-in-the-ediscovery-center.md
audience: ITPro
f1.keywords: - NOCSH + ms.localizationpriority: medium - tier1
SharePoint Account Permissions And Security Settings In Sharepoint Server 2016 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/account-permissions-and-security-settings-in-sharepoint-server-2016.md
The following sections describe recommendations on SharePoint Service accounts.
Microsoft recommends using a minimal number of Service Application Pool accounts in the farm. This recommendation is to reduce memory usage and increase performance while maintaining the appropriate level of security. -- Use an elevated, personally identifiable account for SharePoint installation, maintenance, and upgrades. This account will hold the roles required as outlined by the **SharePoint Farm Administrator account** outlined below. Each SharePoint admin should use a separate account to clearly identify activity performed by the administrator on the farm.
+- Use an elevated, personally identifiable account for SharePoint installation, maintenance, and upgrades. This account will hold the roles required as outlined in [SharePoint Farm Administrator account](#sharepoint-farm-administrator-account). Each SharePoint admin should use a separate account so that their activity performed on the farm is clearly identified.
-- If possible use a security group, **SharePoint Farm Administrators Groups**, to unify all individual SharePoint Farm Administrator accounts and grant permissions as outlined below. This usage of a security group simplifies the management of the SharePoint Farm Administrator accounts significantly.
+- If possible, use a security group, **SharePoint Farm Administrators Groups**, to unify all individual SharePoint Farm Administrator accounts and to grant permissions as outlined in [SharePoint Farm Administrator account](#sharepoint-farm-administrator-account). This usage of a security group simplifies the management of the SharePoint Farm Administrator accounts significantly.
- The **SharePoint Farm Service account** should only run the SharePoint Timer service, SharePoint Insights (if applicable), the IIS Application Pools for Central Administration, SharePoint Web Services System (used for the topology service), and SecurityTokenServiceApplicationPool (used for the Security Token Service). - A single account should be used for all Service Applications, named **Service Application Pool account**. This usage of a single account allows the administrator to use a single IIS Application Pool for all Service Applications. In addition, this account should run the following Windows -- A single account should be used for all Web Applications, named **Web Application pool account**. This usage of a single account allows the administrator to use a single IIS Application Pool for all Web Applications. The exception is the Central Administration Web Application, which as noted above, is run by the SharePoint farm service account.
+- A single account should be used for all Web Applications, named **Web Application pool account**. This usage of a single account allows the administrator to use a single IIS Application Pool for all Web Applications, except the Central Administration Web Application which is run by the SharePoint farm service account.
- Except for the Claims to Windows Token Service account, no Service Application Pool account should have Local Administrator access to any SharePoint server, nor any elevated SQL Server role, for example, the *sysadmin* fixed role. The SharePoint Farm Administrator account will require the *dbcreator* and *securityadmin* fixed roles unless you pre-provision SharePoint databases and manually assign permissions to each database. - Service Application Pool accounts, except for the account running the Claims to Windows Token Service, should have *Deny logon locally* and *Deny logon through Remote Desktop Services* in the Local *Security Policy\User Rights Assignment*. These values are set via *secpol.msc*. -- Use separate accounts for the **Content access** (Search crawler), **Portal Super Reader**, **Portal Super User**, and **User Profile Service Application Synchronization**, if applicable.
+- Use separate accounts for **Content access** (Search crawler), **Portal Super Reader**, **Portal Super User**, and **User Profile Service Application Synchronization**, if applicable.
-- The Claims to Windows Token Service account is a highly privileged account on the farm. Prior to deploying this service, verify it is required. If necessary, use a separate account for this service.
+- The Claims to Windows Token Service account is a highly privileged account on the farm. Prior to deploying this service, verify if it's required. If necessary, use a separate account for this service.
### Service accounts recommendations overview Service account name|What is it used for?|How many should be used? -|-|- SharePoint Farm Administrator account|Personally identifiable account for a SharePoint admin|1-n
-SharePoint Farm Service Account| Timer Service, Insights, IIS App for CA, SP Web Services System, Security Token Service App Pool|1
+SharePoint Farm Service account| Timer Service, Insights, IIS App for CA, SP Web Services System, Security Token Service App Pool|1
Default content access account|Search crawling internal and external sources|1 Content access accounts|Search crawling internal and external sources|1-n Web Application Pool account|All Web Applications without Central Administration|1
One of the following SharePoint components automatically configures most of the
### SharePoint Farm Administrator account
-This account is used to set up each server in your farm by running the SharePoint Products Configuration Wizard, the initial Farm Configuration Wizard, and PowerShell. For the examples in this article, the SharePoint Farm Administrator account is used for farm administration, and you can use Central Administration to manage it. Some configuration options, for example, configuration of the SharePoint Server Search query server, require local administration permissions. The SharePoint Farm Administrator account requires the following permissions:
+This account is used to set up each server in your farm by running the SharePoint Products Configuration Wizard (Psconfig), the initial Farm Configuration Wizard, and PowerShell. For the examples in this article, the SharePoint Farm Administrator account is used for farm administration, and you can use Central Administration to manage it. Some configuration options, for example, configuration of the SharePoint Server Search query server, require local administration permissions. The SharePoint Farm Administrator account has the following requirements:
- It must have domain user account permissions.
After you run the configuration wizards, machine-level permissions for the Share
- Membership in the *WSS_ADMIN_WPG* Windows security group. - After you run the configuration wizards, database permissions include: - *db_owner* on the SharePoint server farm configuration database.
After you run the configuration wizards, database permissions include:
- *db_owner* on the SharePoint Central Administration content database. > [!CAUTION]
-> If the account that you use to run the configuration wizards does not have the appropriate special SQL Server role membership or access as *db_owner* on the databases, the configuration wizards will not run correctly.
+> If the account that you use to run the configuration wizards doesn't have the appropriate special SQL Server role membership or access as *db_owner* on the databases, the configuration wizards won't run correctly.
### SharePoint Farm Service account
-The SharePoint Farm service account, which is also referred to as the database access account, is used as the application pool identity for Central Administration and as the process account for the SharePoint Timer Service. The server farm account requires the following permissions:
+The SharePoint Farm service account, which is also referred to as the database access account, is used as the application pool identity for Central Administration and as the process account for the SharePoint Timer Service. The server farm account has the following requirement:
- It must have domain user account permissions.
This section describes the SharePoint Application Pool accounts that are set up
The default content access account is used within a specific service application to crawl content, unless a different authentication method is specified by a crawl rule for a URL or URL pattern. This account requires the following permission configuration settings: -- The default content access account must be a domain user account that has read access to external or secure content sources that you want to crawl by using this account.
+- The default content access account must be a domain user account that has *read* access to external or secure content sources that you want to crawl by using this account.
-- For SharePoint Server sites that are not part of the server farm, you have to explicitly grant this account full read permissions to the web applications that host the sites.
+- For SharePoint Server sites that aren't part of the server farm, you have to explicitly grant this account full *read* permission to the Web Applications that host the sites.
- This account must not be a member of the Farm Administrators group.
The default content access account is used within a specific service application
Content access accounts are configured to access content by using the Search administration crawl rules feature. This type of account is optional, and you can configure it when you create a new crawl rule. For example, external content (such as a file share) might require this separate content access account. This account requires the following permission configuration settings: -- The content access account must have read access to external or secure content sources that this account is configured to access.
+- The content access account must have *read* access to external or secure content sources that this account is configured to access.
-- For SharePoint Server sites that are not part of the server farm, you have to explicitly grant this account full read permissions to the web applications that host the sites.
+- For SharePoint Server sites that aren't part of the server farm, you have to explicitly grant this account full *read* permission to the Web Applications that host the sites.
### Web Application Pool account The Web Application Pool account must be a domain user account. This account must not be a member of the Farm Administrators group.
-This account should be used for all web applications without Central Administration.
+This account should be used for all Web Applications without Central Administration.
+
+The following machine-level permission is configured automatically:
-The following machine-level permission is configured automatically: This account is a member of *WSS_WPG*.
+- This account is a member of *WSS_WPG*.
The following SQL Server and database permissions are configured automatically:
The following SQL Server and database permissions are configured automatically:
- This account is assigned to the *WSS_CONTENT_APPLICATION_POOLS* role that is associated with the SharePoint Admin content database. -- The application pool accounts for web applications are assigned to the *SPDataAccess* role for the content databases
+- The application pool accounts for Web Applications are assigned to the *SPDataAccess* role for the content databases.
### SharePoint Service Application Pool account The SharePoint Service Application Pool account must be a domain user account. This account must not be a member of the Administrators group on any computer in the server farm.
-The following machine-level permission is configured automatically: This account is a member of *WSS_WPG*.
+The following machine-level permission is configured automatically:
-The following SQL Server and database permissions are configured automatically:
+- This account is a member of *WSS_WPG*.
+
+The following SQL Server and database requirements/permissions are configured automatically:
- This account is assigned to the *SPDataAccess* role for the content databases. -- This account is assigned to the *SPDataAccess* role for search database that is associated with the web application.
+- This account is assigned to the *SPDataAccess* role for a search database that is associated with the Web Application.
- This account must have *read* and *write* access to the associated service application database.
This section describes the database roles that installation sets up by default o
### WSS_CONTENT_APPLICATION_POOLS database role
-The *WSS_CONTENT_APPLICATION_POOLS* database role applies to the application pool account for each web application that is registered in a SharePoint farm. This role applicability enables web applications to query and update the site map and have read-only access to other items in the configuration database. Setup assigns the *WSS_CONTENT_APPLICATION_POOLS* role to the following databases:
+The *WSS_CONTENT_APPLICATION_POOLS* database role applies to the application pool account for each Web Application that is registered in a SharePoint farm. This role applicability enables Web Applications to query and update the site map and have *read-only* access to other items in the configuration database. Setup assigns the *WSS_CONTENT_APPLICATION_POOLS* role to the following databases:
- The SharePoint Config database (the configuration database) - The SharePoint Admin Content database
-Members of the *WSS_CONTENT_APPLICATION_POOLS* role have the execute permission for a subset of the stored procedures for the database. In addition, members of this role have the select permission to the Versions table (dbo.Versions) in the SharePoint_AdminContent database. For other databases, the accounts planning tool indicates that access to read these databases is automatically configured. In some cases, limited access to write to a database is also automatically configured. To provide this access, permissions for stored procedures are configured.
+Members of the *WSS_CONTENT_APPLICATION_POOLS* role have the *execute* permission for a subset of the stored procedures for the database. In addition, members of this role have the *select* permission to the Versions table (dbo.Versions) in the SharePoint_AdminContent database. For other databases, the accounts planning tool indicates that access to read these databases is automatically configured. In some cases, limited access to write to a database is also automatically configured. To provide this access, permissions for stored procedures are configured.
#### SharePoint_SHELL_ACCESS database role
-The secure *SharePoint_SHELL_ACCESS* database role on the configuration database replaces the need to add an administration account as a **db_owner** on the configuration database. By default, the setup account is assigned to the *SharePoint_SHELL_ACCESS* database role. You can use a PowerShell command to grant or remove memberships to this role. Setup assigns the *SharePoint_SHELL_ACCESS* role to the following databases:
+The secure *SharePoint_SHELL_ACCESS* database role on the configuration database replaces the need to add an administration account as a *db_owner* on the configuration database. By default, the setup account is assigned to the *SharePoint_SHELL_ACCESS* database role. You can use a PowerShell command to grant or remove memberships to this role. Setup assigns the *SharePoint_SHELL_ACCESS* role to the following databases:
- The SharePoint_Config database (the configuration database). - One or more of the SharePoint Content databases. This database is configurable by using the PowerShell command that manages membership and the object that is assigned to this role.
-Members of the *SharePoint_SHELL_ACCESS* role have the execute permission for all stored procedures for the database. In addition, members of this role have the read and write permissions on all of the database tables.
+Members of the *SharePoint_SHELL_ACCESS* role have the *execute* permission for all stored procedures for the database. In addition, members of this role have the *read* and *write* permissions on all the database tables.
#### SPREADONLY database role
-The *SPREADONLY* role should be used for setting the database to read-only mode instead of using sp_dboption. This role as its name suggests should be used when only read access is required for data such as usage and telemetry data.
+The *SPREADONLY* role should be used for setting the database to *read-only* mode instead of using *sp_dboption*. This role as its name suggests should be used when only *read* access is required for usage and telemetry data.
> [!NOTE]
-> The sp_dboption stored procedure is not available in SQL Server 2012. For more information about sp_dboption, see [sp_dboption (Transact-SQL)](/previous-versions/sql/sql-server-2008-r2/ms187310(v=sql.105)).
+> The *sp_dboption* stored procedure isn't available in SQL Server 2012. For more information about *sp_dboption*, see [sp_dboption (Transact-SQL)](/previous-versions/sql/sql-server-2008-r2/ms187310(v=sql.105)).
The *SPREADONLY* SQL role will have the following permissions:
The *SPREADONLY* SQL role will have the following permissions:
- Grant SELECT on all SharePoint tables. -- Grant EXECUTE on user-defined type where schema is dbo.
+- Grant EXECUTE on user-defined types where schema is dbo.
#### SPDataAccess database role
-The *SPDataAccess* role is the default role for database access and should be used for all object model level access to databases. Add the application pool account to this role during upgrade or new deployments.
+The *SPDataAccess* role is the default role for database access and should be used for all object model-level access to databases. Add the application pool account to this role during upgrades or new deployments.
> [!NOTE]
-> The SPDataAccess role replaced the db_owner role in SharePoint Server 2016.
+> The *SPDataAccess* role replaced the *db_owner* role in SharePoint Server 2016.
-The SPDataAccess role will have the following permissions:
+The *SPDataAccess* role will have the following permissions:
- Grant EXECUTE or SELECT on all SharePoint stored procedures and functions. - Grant SELECT on all SharePoint tables. -- Grant EXECUTE on User-defined type where schema is dbo.
+- Grant EXECUTE on user-defined types where schema is dbo.
- Grant INSERT on AllUserDataJunctions table.
The SPDataAccess role will have the following permissions:
## Group permissions <a name="Section6"> </a>
-This section describes permissions of groups that the SharePoint Servers 2016 and 2019 setup and configuration tools create.
+This section describes the permissions of groups that the SharePoint Servers 2016 and 2019 setup and configuration tools create.
### WSS_ADMIN_WPG
-*WSS_ADMIN_WPG* has read and write access to local resources. The application pool accounts for the Central Administration and Timer services are in *WSS_ADMIN_WPG*. The following table shows the *WSS_ADMIN_WPG* registry entry permissions.
+*WSS_ADMIN_WPG* has *read* and *write* access to local resources. The application pool accounts for the Central Administration and Timer services are in *WSS_ADMIN_WPG*. The following table shows the *WSS_ADMIN_WPG* registry entry permissions:
>[!NOTE]
->SharePoint 2013 uses the registry path "15.0" instead of "16.0" and file system path "15" instead of "16". Some paths listed below do not apply to SharePoint Foundation 2013.
+>SharePoint 2013 uses the registry path "15.0" instead of "16.0" and file system path "15" instead of "16". Some paths listed in the subsequent tables don't apply to SharePoint Foundation 2013.
|**Key name**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
This section describes permissions of groups that the SharePoint Servers 2016 an
|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LauncherSettings|Read, write|No|This key contains settings for the document conversion service. Altering this key will break document conversion functionality.| |HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\Search|Full control|Not applicable|Not applicable| |HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Search|Full control|Not applicable|Not applicable|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Full control|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server installation on the machine will not function.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Full control|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server installation on the machine won't function.|
|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS|Full control|Yes|This key contains settings used during setup. If this key is altered, diagnostic logging might fail, and setup or post-setup configuration might fail.| The following table shows the WSS_ADMIN_WPG file system permissions. |**File system path**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|%AllUsersProfile%\ Microsoft\SharePoint|Full control|No|This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start, and the administrative actions might fail if this directory is altered or deleted.|
-|C:\Inetpub\wwwroot\wss|Full control|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable, and administrative actions might fail if this directory is altered or deleted, unless custom IIS Web site paths are provided for all IIS Web sites extended with SharePoint Server.|
-|%ProgramFiles%\Microsoft Office Servers\16.0|Full control|No|This directory is the installation location for SharePoint Server 2016 binaries and data. The directory can be changed during installation. All SharePoint Server functionality will fail if this directory is removed, altered, or removed after installation. Membership in the WSS_ADMIN_WPG Windows security group is required for some SharePoint Server services to be able to store data on disk.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\WebServices|Read, write|No|This directory is the root directory where back-end Web services are hosted, for example, Excel and Search. The SharePoint Server features that depend on these services will fail if this directory is removed or altered.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\Data|Full control|No|This directory is the root location where local data is stored, including search indexes. Search functionality will fail if this directory is removed or altered. WSS_ADMIN_WPG Windows security group permissions are required to enable search to save and secure data in this folder.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\Logs|Full control|Yes|This directory is the location where the run-time diagnostic logging is generated. Logging functionality will not function properly if this directory is removed or altered.|
+|%AllUsersProfile%\ Microsoft\SharePoint|Full control|No|This directory contains the file-system-backed cache of the farm configuration. If this directory is altered or deleted, processes might fail to start, and the administrative actions might fail.|
+|C:\Inetpub\wwwroot\wss|Full control|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Websites. If this directory is altered or deleted, SharePoint sites will be unavailable, and administrative actions might fail, unless custom IIS Website paths are provided for all IIS Websites extended with SharePoint Server.|
+|%ProgramFiles%\Microsoft Office Servers\16.0|Full control|No|This directory is the installation location for SharePoint Server 2016 binaries and data. The directory can be changed during installation. If this directory is removed, altered, or removed after installation, all SharePoint Server functionalities will fail. Membership in the WSS_ADMIN_WPG Windows security group is required for some SharePoint Server services to be able to store data on the disk.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\WebServices|Read, write|No|This directory is the root directory where back-end Web services are hosted, for example, Excel and Search. If this directory is removed or altered, the SharePoint Server features that depend on these services will fail.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\Data|Full control|No|This directory is the root location where local data is stored, including search indexes. If this directory is removed or altered, the Search functionality will fail. WSS_ADMIN_WPG Windows security group permissions are required to enable the Search functionality to save and secure data in this folder.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\Logs|Full control|Yes|This directory is the location where the runtime diagnostic logging is generated. If this directory is removed or altered, the Logging functionality won't function properly.|
|%ProgramFiles%\Microsoft Office Servers\16.0\Data\Office Server|Full control|Yes|Same as the parent folder.| |%windir%\System32\drivers\etc\HOSTS|Read, write|Not applicable|Not applicable| |%windir%\Tasks|Full control|Not applicable|Not applicable|
-|%COMMONPROGRAMFILES%Microsoft Shared\Web Server Extensions\16|Modify|Yes|This directory is the installation directory for core SharePoint Server files. If the access control list (ACL) is modified, feature activation, solution deployment, and other features will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Full control|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Full control|Yes|This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, web application provisioning will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Full control|No|This directory contains setup and runtime tracing logs. If the directory is altered, diagnostic logging will not function correctly.|
-|%windir%\temp|Full control|Yes|This directory is used by platform components on which SharePoint Server depends. If the access control list is modified, Web Part rendering and other deserialization operations might fail.|
-|%windir%\System32\logfiles\SharePoint|Full control|No|This directory is used by SharePoint Server usage logging. If this directory is modified, usage logging will not function correctly. This registry key applies only to SharePoint Server.|
+|%COMMONPROGRAMFILES%Microsoft Shared\Web Server Extensions\16|Modify|Yes|This directory is the installation directory for core SharePoint Server files. If the access control list (ACL) is modified, feature activation, solution deployment, and other features won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Full control|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Full control|Yes|This directory contains files used to extend IIS Websites with SharePoint Server. If this directory or its contents are altered, Web Application provisioning won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Full control|No|This directory contains setup and runtime tracing logs. If the directory is altered, diagnostic logging won't function correctly.|
+|%windir%\temp|Full control|Yes|This directory is used by platform components on which SharePoint Server depends. If the ACL is modified, Web Part rendering and other deserialization operations might fail.|
+|%windir%\System32\logfiles\SharePoint|Full control|No|This directory is used by SharePoint Server usage logging. If this directory is modified, usage logging won't function correctly. This registry key applies only to SharePoint Server.|
|%systemdrive\program files\Microsoft Office Servers\16 folder on Index servers|Full control|Not applicable|This permission is granted for a %systemdrive\program files\Microsoft Office Servers\16 folder on Index servers.| ### WSS_WPG
-*WSS_WPG* has read access to local resources. All application pool and services accounts are in WSS_WPG. The following table shows *WSS_WPG* registry entry permissions.
+*WSS_WPG* has *read* access to local resources. All application pool and services accounts are in WSS_WPG. The following table shows *WSS_WPG* registry entry permissions:
|**Key name**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--| |HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0|Read|No|This key is the root of the SharePoint Server registry settings.|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\Diagnostics|Read, write|No|This key contains settings for the SharePoint Server diagnostic logging. Altering this key will break the logging functionality.|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LoadBalancerSettings|Read, write|No|This key contains settings for the document conversion service. Altering this key will break document conversion functionality.|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LauncherSettings|Read, write|No|This key contains settings for the document conversion service. Altering this key will break document conversion functionality.|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Read|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server 2016 installation on the machine will not function.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\Diagnostics|Read, write|No|This key contains settings for the SharePoint Server diagnostic logging. If this key is altered, the Logging functionality will break.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LoadBalancerSettings|Read, write|No|This key contains settings for the document conversion service. If this key is altered, the document conversion functionality will break.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LauncherSettings|Read, write|No|This key contains settings for the document conversion service. If this key is altered, the document conversion functionality will break.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Read|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server 2016 installation on the machine won't function.|
|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS|Read|Yes|This key contains settings that are used during setup. If this key is altered, diagnostic logging might fail and setup or post-setup configuration might fail.|
+|HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg|Read|No|This key contains settings that control remote access to the registry.|
-The following table shows the WSS_WPG file system permissions.
+The following table shows the WSS_WPG file system permissions:
|**File system path**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|%AllUsersProfile%\ Microsoft\SharePoint|Read|No|This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start and the administrative actions might fail if this directory is altered or deleted.|
-|C:\Inetpub\wwwroot\wss|Read, execute|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable and administrative actions might fail if this directory is altered or deleted, unless custom IIS Web site paths are provided for all IIS Web sites extended with SharePoint Server.|
-|%ProgramFiles%\Microsoft Office Servers\16.0|Read, execute|No|This directory is the installation location for the SharePoint Server binaries and data. It can be changed during installation. All SharePoint Server functionality will fail if this directory is removed, altered, or moved after installation. WSS_WPG read and execute permissions are required to enable IIS sites to load SharePoint Server binaries.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\WebServices|Read|No|This directory is the root directory where back-end Web services are hosted, for example, Excel and Search. The SharePoint Server features that depend on these services will fail if this directory is removed or altered.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\Logs|Read, write|Yes|This directory is the location where the runtime diagnostic logging is generated. Logging functionality will not function properly if this directory is removed or altered.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Read|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Read|Yes|This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, web application provisioning will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Modify|No|This directory contains setup and runtime tracing logs. If the directory is altered, diagnostic logging will not function correctly.|
-|%windir%\temp|Read|Yes|This directory is used by platform components on which SharePoint Server depends. If the access control list is modified, Web Part rendering, and other deserialization operations might fail.|
-|%windir%\System32\logfiles\SharePoint|Read|No|This directory is used by SharePoint Server usage logging. If this directory is modified, usage logging will not function correctly. The registry key applies only to SharePoint Server.|
+|%AllUsersProfile%\ Microsoft\SharePoint|Read|No|This directory contains the file-system-backed cache of the farm configuration. If this directory is altered or deleted, processes might fail to start and the administrative actions might fail.|
+|C:\Inetpub\wwwroot\wss|Read, execute|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Websites. If this directory is altered or deleted, SharePoint sites will be unavailable and administrative actions might fail, unless custom IIS Website paths are provided for all IIS Websites extended with SharePoint Server.|
+|%ProgramFiles%\Microsoft Office Servers\16.0|Read, execute|No|This directory is the installation location for the SharePoint Server binaries and data. It can be changed during installation. If this directory is removed, altered, or moved after installation, all SharePoint Server functionalities will fail. *WSS_WPG* *read* and *execute* permissions are required to enable IIS Websites to load SharePoint Server binaries.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\WebServices|Read|No|This directory is the root directory where back-end Web services are hosted, for example, Excel and Search. If this directory is removed or altered, the SharePoint Server features that depend on these services will fail.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\Logs|Read, write|Yes|This directory is the location where the runtime diagnostic logging is generated. If this directory is removed or altered, the Logging functionality won't function properly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Read|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Read|Yes|This directory contains files used to extend IIS Websites with SharePoint Server. If this directory or its contents are altered, Web Application provisioning won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Modify|No|This directory contains setup and runtime tracing logs. If the directory is altered, diagnostic logging won't function correctly.|
+|%windir%\temp|Read|Yes|This directory is used by platform components on which SharePoint Server depends. If the ACL is modified, Web Part rendering and other deserialization operations might fail.|
+|%windir%\System32\logfiles\SharePoint|Read|No|This directory is used by SharePoint Server usage logging. If this directory is modified, usage logging won't function correctly. The registry key applies only to SharePoint Server.|
|%systemdrive\program files\Microsoft Office Servers\16|Read, execute|Not applicable|The permission is granted for %systemdrive\program files\Microsoft Office Servers\16 folder on Index servers.| ### Local service
The following table shows the local service registry entry permission:
|**Key name**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LoadBalancerSettings|Read|No|This key contains settings for the document conversion service. Altering this key will break document conversion functionality.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LoadBalancerSettings|Read|No|This key contains settings for the document conversion service. If this key is altered, the document conversion functionality will break.|
The following table shows the local service file system permission: |**File system path**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|%ProgramFiles%\Microsoft Office Servers\16.0\Bin|Read, execute|No|This directory is the installed location of the SharePoint Server binaries. All the SharePoint Server functionality will fail if this directory is removed or altered.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\Bin|Read, execute|No|This directory is the installed location of the SharePoint Server binaries. If this directory is removed or altered, all the SharePoint Server functionalities will fail.|
### Local system
The following table shows the local system registry entry permissions:
|**Key name**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LauncherSettings|Read|No|This key contains settings for the document conversion service. Altering this key will break document conversion functionality. This registry key applies only to SharePoint Server.|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Full control|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server installation on the machine will not function.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\16.0\LauncherSettings|Read|No|This key contains settings for the document conversion service. If this key is altered, the document conversion functionality will break. This registry key applies only to SharePoint Server.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Full control|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server installation on the machine won't function.|
|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure\FarmAdmin|Full control|No|This key contains the encryption key that is used to store secrets in the configuration database. If this key is altered, service provisioning and other features will fail.| |HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS|Full control|Yes|This key contains settings that are used during setup. If this key is altered, diagnostic logging might fail and setup or post-setup configuration might fail.|
The following table shows the local file system permissions:
|**File system path**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|%AllUsersProfile%\ Microsoft\SharePoint|Full control|No|This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start and administrative actions might fail if this directory is altered or deleted.|
-|C:\Inetpub\wwwroot\wss|Full control|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable and administrative actions might fail if this directory is altered or deleted, unless custom IIS Web site paths are provided for all IIS Web sites extended with SharePoint Server.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Full control|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Full control|Yes|If this directory or its contents are altered, Web Application provisioning will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Full control|No|This directory contains setup and run-time tracing logs. If the directory is altered, diagnostic logging will not function correctly.|
-|%windir%\temp|Full control|Yes|This directory is used by platform components on which SharePoint Server depends. If the access control list is modified, Web Part rendering, and other deserialization operations might fail.|
-|%windir%\System32\logfiles\SharePoint|Full control|No|This directory is used by SharePoint Server for usage logging. If this directory is modified, usage logging will not function correctly. This registry key applies only to SharePoint Server.|
+|%AllUsersProfile%\ Microsoft\SharePoint|Full control|No|This directory contains the file-system-backed cache of the farm configuration. If this directory is altered or deleted, processes might fail to start and administrative actions might fail.|
+|C:\Inetpub\wwwroot\wss|Full control|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Websites. If this directory is altered or deleted, SharePoint sites will be unavailable and administrative actions might fail, unless custom IIS Website paths are provided for all IIS Websites extended with SharePoint Server.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Full control|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Full control|Yes|This directory contains configuration files used to provision Web applications and service applications. If this directory or its contents are altered, Web Application provisioning won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Full control|No|This directory contains setup and runtime tracing logs. If this directory is altered, diagnostic logging won't function correctly.|
+|%windir%\temp|Full control|Yes|This directory is used by platform components on which SharePoint Server depends. If the ACL is modified, Web Part rendering and other deserialization operations might fail.|
+|%windir%\System32\logfiles\SharePoint|Full control|No|This directory is used by SharePoint Server for usage logging. If this directory is modified, usage logging won't function correctly. This registry key applies only to SharePoint Server.|
### Network service
The following table shows the administrators registry entry permissions:
|**Key name**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Full control|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server installation on the machine will not function.|
+|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure|Full control|No|This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server installation on the machine won't function.|
|HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure\FarmAdmin|Full control|No|This key contains the encryption key that is used to store secrets in the configuration database. If this key is altered, service provisioning and other features will fail.| |HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS|Full control|Yes|This key contains settings that are used during setup. If this key is altered, diagnostic logging might fail and setup or post-setup configuration might fail.|
The following table shows the administrators file system permissions:
|**File system path**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|%AllUsersProfile%\ Microsoft\SharePoint|Full control|No|This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start and administrative actions might fail if this directory is altered or deleted.|
-|C:\Inetpub\wwwroot\wss|Full Control|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable and administrative actions might fail if this directory is altered or deleted, unless custom IIS web site paths are provided for all IIS web sites that are extended with SharePoint Server.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Full control|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Full control|Yes|If this directory or its contents are altered, web application provisioning will not function correctly.|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Full control|No|This directory contains setup and run-time tracing logs. If the directory is altered, diagnostic logging will not function correctly.|
-|%windir%\temp|Full control|Yes|This directory is used by platform components on which SharePoint Server depends. If the ACL is modified, Web Part rendering, and other deserialization operations might fail.|
-|%windir%\System32\logfiles\SharePoint|Full control|No|This directory is used by SharePoint Server for usage logging. If this directory is modified, usage logging will not function correctly. This registry key applies only to SharePoint Server.|
+|%AllUsersProfile%\ Microsoft\SharePoint|Full control|No|This directory contains the file-system-backed cache of the farm configuration. If this directory is altered or deleted, processes might fail to start and administrative actions might fail.|
+|C:\Inetpub\wwwroot\wss|Full Control|No|This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Websites. If this directory is altered or deleted, SharePoint sites will be unavailable and administrative actions might fail, unless custom IIS Website paths are provided for all IIS Websites that are extended with SharePoint Server.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\ADMISAPI|Full control|Yes|This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\CONFIG|Full control|Yes|This directory contains configuration files used to provision Web applications and service applications. If this directory or its contents are altered, Web Application provisioning won't function correctly.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Full control|No|This directory contains setup and runtime tracing logs. If the directory is altered, diagnostic logging won't function correctly.|
+|%windir%\temp|Full control|Yes|This directory is used by platform components on which SharePoint Server depends. If the ACL is modified, Web Part rendering and other deserialization operations might fail.|
+|%windir%\System32\logfiles\SharePoint|Full control|No|This directory is used by SharePoint Server for usage logging. If this directory is modified, usage logging won't function correctly. This registry key applies only to SharePoint Server.|
### WSS_RESTRICTED_WPG
The following table shows the users group file system permissions:
|**File system path**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|%ProgramFiles%\Microsoft Office Servers\16.0|Read, execute|No|This directory is the installation location for SharePoint Server binaries and data. It can be changed during installation. All SharePoint Server functionality will fail if this directory is removed, altered, or moved after installation.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\WebServices\Root|Read, execute|No|This directory is the root directory where back-end root Web services are hosted. The only service initially installed on this directory is a search global administration service. Some search administration functionality that uses the server-specific Central Administration Settings page will not work if this directory is removed or altered.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\Logs|Read, write|Yes|This directory is the location where the run-time diagnostic logging is generated. Logging will not function properly if this directory is removed or altered.|
-|%ProgramFiles%\Microsoft Office Servers\16.0\Bin|Read, execute|No|This directory is the installed location of SharePoint Server binaries. All of the SharePoint Server functionality will fail if this directory is removed or altered.|
+|%ProgramFiles%\Microsoft Office Servers\16.0|Read, execute|No|This directory is the installation location for SharePoint Server binaries and data. It can be changed during installation. If this directory is removed, altered, or moved after installation, all SharePoint Server functionality will fail.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\WebServices\Root|Read, execute|No|This directory is the root directory where back-end root Web services are hosted. The only service initially installed on this directory is a search global administration service. If this directory is removed or altered, some search administration functionalities that use the server-specific Central Administration Settings page won't work.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\Logs|Read, write|Yes|This directory is the location where the runtime diagnostic logging is generated. If this directory is removed or altered, Logging won't function properly.|
+|%ProgramFiles%\Microsoft Office Servers\16.0\Bin|Read, execute|No|This directory is the installed location of SharePoint Server binaries. If this directory is removed or altered, all the SharePoint Server functionalities will fail.|
### All SharePoint Server service accounts
-The following table shows the all SharePoint Server service accounts file system permission:
+The following table shows the SharePoint Server service accounts' file system permission:
|**File system path**|**Permissions**|**Inherit**|**Description**| |:--|:--|:--|:--|
-|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Modify|No|This directory contains setup and run-time tracing logs. If this directory is altered, diagnostic logging will not function correctly. All SharePoint Server service accounts must have write permission to this directory.|
+|%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS|Modify|No|This directory contains setup and runtime tracing logs. If this directory is altered, diagnostic logging won't function correctly. All SharePoint Server service accounts must have *write* permission to this directory.|
## See also <a name="Section6"> </a>
SharePoint Configure My Sites https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/configure-my-sites.md
We recommend that you perform all of the procedures in the order listed for best
Because My Sites have dependencies on other service applications and features in SharePoint Server, ensure that you meet the prerequisites in this section before you perform the procedures in this task. > [!NOTE]
-> My Sites are hosted by a web application and rely on a User Profile service application. Both are described in this section. My Sites also requires a managed metadata service application. We recommend that you also have a Search service application to use with My Sites, but this is not required. Without the Search service application, some My Sites functionality is affected. For more information, see [Plan for My Sites in SharePoint Server](my-sites-planning.md).
+> My Sites are hosted by a web application and rely on a User Profile service application. Both are described in this section. My Sites also requires a managed metadata service application. We recommend that you also have a Search service application to use with My Sites, but this isn't required. Without the Search service application, some My Sites functionality is affected. For more information, see [Plan for My Sites in SharePoint Server](my-sites-planning.md).
### Web application <a name="webapp"> </a>
Because My Sites have dependencies on other service applications and features in
Although you can use an existing web application, for optimal performance and security, we recommend that you create the My Site host site collection in a dedicated web application. For more information, see [Create a web application in SharePoint Server](/previous-versions/office/sharepoint-server-2010/cc261875(v=office.14)). > [!IMPORTANT]
-> If a My Site host site collection was created during initial deployment and configuration, we recommend that you do not use it because it was created in the default web application. Delete this site collection, and create a new web application that is dedicated to hosting My Sites. Then create a new My Site host site collection in the dedicated web application.
+> If a My Site host site collection was created during initial deployment and configuration, we recommend that you don't use it because it was created in the default web application. Delete this site collection, and create a new web application that is dedicated to hosting My Sites. Then create a new My Site host site collection in the dedicated web application.
### User Profile service application and profile synchronization <a name="upsapp"> </a>
Ensure you have a User Profile service application that you want to use for My S
## Create a My Site host site collection <a name="mysitehost"> </a>
-The My Site host site collection is a site collection that uses the Enterprise site template named **My Site Host**. This site collection must be created in the web application that you want to host My Sites. Generally, this site collection can be created at the root path of the web application, although it can be created as an explicit inclusion managed path deeper in the URL as long as there is a site collection created at the web application root. For more information about how to select the path for the My Site host collection, see [Plan for My Sites in SharePoint Server](my-sites-planning.md).
+The My Site host site collection is a site collection that uses the Enterprise site template named **My Site Host**. This site collection must be created in the web application that you want to host My Sites. Generally, this site collection can be created at the root path of the web application, although it can be created as an explicit inclusion managed path deeper in the URL as long as there's a site collection created at the web application root. For more information about how to select the path for the My Site host collection, see [Plan for My Sites in SharePoint Server](my-sites-planning.md).
**To create a My Site host site collection** 1. Verify that you have the following administrative credentials:
- - To create a My Site host site collection, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website or a service application administrator for the services related to My Sites. If you are a service application administrator, you must also have permission to create site collections in the web application that you dedicate to host My Sites.
+ - To create a My Site host site collection, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website or a service application administrator for the services related to My Sites. If you're a service application administrator, you must also have permission to create site collections in the web application that you dedicate to host My Sites.
2. In Central Administration, click **Application Management**, and then click **Create site collections**.
-3. On the **Create Site Collection** page, in the **Web Application** section, ensure that the selected web application is the web application that you want to host My Sites. If it is not, expand the list, and then click **Change Web Application**. In the **Select Web Application** dialog, select a different web application.
+3. On the **Create Site Collection** page, in the **Web Application** section, ensure that the selected web application is the web application that you want to host My Sites. If it isn't, expand the list, and then click **Change Web Application**. In the **Select Web Application** dialog, select a different web application.
4. In the **Title and Description** section, type a title and description for the site collection.
The My Site host site collection is a site collection that uses the Enterprise s
7. In the **Primary Site Collection Administrator** section, and optionally in the **Secondary Site Collection Administrator** section, type an account in the format _domain\username_ to specify an administrator for the site collection.
-8. Optionally, in the **Quota Template** section, select a quota template for the My Site host site collection. This quota template does not affect the individual site collections that users create for their My Sites. For more information, see [Planning for storage requirements](my-sites-planning.md#storage) in [Plan for My Sites in SharePoint Server](my-sites-planning.md).
+8. Optionally, in the **Quota Template** section, select a quota template for the My Site host site collection. This quota template doesn't affect the individual site collections that users create for their My Sites. For more information, see [Planning for storage requirements](my-sites-planning.md#storage) in [Plan for My Sites in SharePoint Server](my-sites-planning.md).
9. Click **OK**. Copy this site collection URL for later reference.
The wildcard inclusion managed path is the path under which separate site collec
4. On the **Web Applications** tab, in the **Manage** group, click **Managed Paths**.
-5. In the **Define Managed Paths** dialog, in the **Add a New Path** section, in the **Path** box, type the path that you want to append to the URL namespace, and then select **Wildcard inclusion**. For example, if your web application URL is http://mysites.contoso.com/ and you want users' individual site collections created under a path named "personal", type personal in the **Path** box. Separate My Sites site collections will be created for each user under http://mysites.contoso.com/personal/.
+5. In the **Define Managed Paths** dialog, in the **Add a New Path** section, in the **Path** box, type the path that you want to append to the URL namespace, and then select **Wildcard inclusion**. For example, if your web application URL is `https://mysites.contoso.com/` and you want users' individual site collections created under a path named "personal", type personal in the **Path** box. Separate My Sites site collections will be created for each user under `https://mysites.contoso.com/personal/`.
6. Click **Add Path**, and then click **OK**.
After you have a My Site host site collection and wildcard inclusion managed pat
4. On the **Manage Profile Service** page, in the **My Site Settings** section, click **Setup My Sites**.
-5. On the **My Sites Settings** page, in the **Preferred Search Center** section, specify settings for the search center to direct users to when they search for people or documents from their **About Me** profile page. If you do not have a search center set up yet, you can skip this step and complete it later. For more information, see [Search service application](my-sites-planning.md#searchapp) in [Plan for My Sites in SharePoint Server](my-sites-planning.md).
+5. On the **My Sites Settings** page, in the **Preferred Search Center** section, specify settings for the search center to direct users to when they search for people or documents from their **About Me** profile page. If you don't have a search center set up yet, you can skip this step and complete it later. For more information, see [Search service application](my-sites-planning.md#searchapp) in [Plan for My Sites in SharePoint Server](my-sites-planning.md).
6. In the **My Site Host** section, type the URL of the My Site host site collection that you created earlier in this task.
After you have a My Site host site collection and wildcard inclusion managed pat
9. In the **Site Naming Format** section, select a naming format for the My Sites site collections that will be created when users view their My Sites for the first time. For more information about these formats, see [My Sites architecture](my-sites-planning.md#mysitesarch) in [Plan for My Sites in SharePoint Server](my-sites-planning.md).
-10. In the **Language Options** section, there is an option to specify whether users can select a preferred language for their My Site. However, the current behavior is to default to the installation language for SharePoint. [My Sites architecture](my-sites-planning.md#mysitesarch) in [Plan for My Sites in SharePoint Server](my-sites-planning.md)
+10. In the **Language Options** section, there's an option to specify whether users can select a preferred language for their My Site. However, the current behavior is to default to the installation language for SharePoint. [My Sites architecture](my-sites-planning.md#mysitesarch) in [Plan for My Sites in SharePoint Server](my-sites-planning.md)
> [!NOTE]
- > This section is not present in SharePoint Server 2019.
+ > This section isn't present in SharePoint Server 2019.
-11. In the **Read Permission Level** section, specify the users or groups that can view other users' My Sites when they are created. By default, this includes all authenticated users. However, you can select a more specific group or users depending on the needs of your deployment.
+11. In the **Read Permission Level** section, specify the users or groups that can view other users' My Sites when they're created. By default, this includes all authenticated users. However, you can select a more specific group or users depending on the needs of your deployment.
-12. In the **Security Trimming Options** section, specify how system generated posts are checked for permissions before they are displayed in feeds and on the **Tags and Notes** page.
+12. In the **Security Trimming Options** section, specify how system generated posts are checked for permissions before they're displayed in feeds and on the **Tags and Notes** page.
13. In the **Newsfeed** section, enable system generated posts to the feed on My Sites by selecting **Enable activities in My Site newsfeeds**. This option is selected by default. This is important in hosted environments where tenants can share the same User Profile service but have different requirements on whether they can enable newsfeeds for their users.
-14. In the **E-mail Notifications** section, specify an email address to use as the sender email address for My Site email notifications. This account does not have to be a real monitored email address. If you want to receive notifications for newsfeed activities, such as replies to your posts or when someone follows you, select **Enable newsfeed email notifications**.
+14. In the **E-mail Notifications** section, specify an email address to use as the sender email address for My Site email notifications. This account doesn't have to be a real monitored email address. If you want to receive notifications for newsfeed activities, such as replies to your posts or when someone follows you, select **Enable newsfeed email notifications**.
> [!IMPORTANT] > You must add the IP address of the farm's outbound SMTP server to the safe list in Exchange Server 2013 to prevent My Site email notifications from being sent to the Junk folder.
-15. In the **My Site Cleanup** section, specify a new owner of a My Site if the existing My Site user is removed from the profile database. For example, if a user leaves the company and is no longer in the profile database, the user's My Site will be deleted together with any content. However, before it is deleted, a new owner can recover any important content. Select **Enable access delegation** for the My Site cleanup job to first attempt to assign ownership of the My Site to the user's manager. If no manager is found, the My Site is assigned to the user specified in **Secondary Owner**. The new owner has two weeks to retrieve content from the My Site before it is deleted.
+15. In the **My Site Cleanup** section, specify a new owner of a My Site if the existing My Site user is removed from the profile database. For example, if a user leaves the company and is no longer in the profile database, the user's My Site will be deleted together with any content. However, before it's deleted, a new owner can recover any important content. Select **Enable access delegation** for the My Site cleanup job to first attempt to assign ownership of the My Site to the user's manager. If no manager is found, the My Site is assigned to the user specified in **Secondary Owner**. The new owner has two weeks to retrieve content from the My Site before it's deleted.
-16. In the **Privacy Settings** section, select **Make My Sites Public** to make all users' My Sites public. This option is not selected by default.
+16. In the **Privacy Settings** section, select **Make My Sites Public** to make all users' My Sites public. This option isn't selected by default.
> [!NOTE]
- > When a user's My Site is public, the user's list of followers, the user's list of people they are following, and all activities (including new follow notifications, social tagging and rating of content, birthdays, job title changes, workplace anniversary, updating Ask Me About, posting on a note board, and new blog posts) will be public. Any policies set within **People and Privacy** on the **Manage Policies** page is overridden.
+ > When a user's My Site is public, the user's list of followers, the user's list of people they're following, and all activities (including new follow notifications, social tagging and rating of content, birthdays, job title changes, workplace anniversary, updating Ask Me About, posting on a note board, and new blog posts) will be public. Any policies set within **People and Privacy** on the **Manage Policies** page is overridden.
17. Click **OK**.
There are other timer jobs related to My Sites that you might want to review and
3. On the **Job Definitions** page, in the **View** list, select **Service**. The **Service** list appears.
- - If the **Service** list does not display **User Profile Service**, in **Service**, click **No selection**, then click **Change Service**. On the **Select Service** page, use the arrows in the upper-right corner to locate **User Profile Service**, and then click it. The **Job Definitions** page updates with the User Profile service jobs.
+ - If the **Service** list doesn't display **User Profile Service**, in **Service**, click **No selection**, then click **Change Service**. On the **Select Service** page, use the arrows in the upper-right corner to locate **User Profile Service**, and then click it. The **Job Definitions** page updates with the User Profile service jobs.
4. Click the activity feed job for the User Profile service application that you created in [Prerequisites](configure-my-sites.md#prereq) earlier in this article. The job name is in the format _User_Profile_service_name_ - **Activity Feed Job**, where _User_Profile_service_name_ is the name that you specified for your User Profile service application.
If your organization wants to provide important information to users, it can do
### Start related services <a name="startsvcs"> </a>
-If the related services for My Sites have not been started yet, start them so that My Sites functionality is available in your environment. For more information, see [Start or stop a service in SharePoint Server](../administration/start-or-stop-a-service.md).
+If the related services for My Sites haven't been started yet, start them so that My Sites functionality is available in your environment. For more information, see [Start or stop a service in SharePoint Server](../administration/start-or-stop-a-service.md).
SharePoint My Sites Planning https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/my-sites-planning.md
The My Site host site collection and individual site collections are described m
The My Site host site collection is a special site collection that displays the newsfeed and profile pages of all users' My Sites. The site collection's site template must be the My Site host site template, available from the **Enterprise** tab of the **Create Site Collection** page. The My Site host site template can be used only once per User Profile service application, which is discussed later in this article.
-My Sites require that a site collection exist at the web application root (which is displayed as **/** in the user interface). Without this, you will receive a message that states that there is no site collection at the root when you try to enable self-service site creation for the web application. Because we recommend that you use a dedicated web application to host My Sites, you should use the root path for the My Site host collection unless you have a specific requirement to create the site collection deeper in the uniform resource locator (URL) path.
+My Sites requires a site collection to exist at the web application root (which is displayed as **/** in the user interface). Without this site collection, you'll receive a message that states that there's no site collection at the root when you try to enable self-service site creation for the web application. Because we recommend that you use a dedicated web application to host My Sites, you should use the root path for the My Site host collection unless you have a specific requirement to create the site collection deeper in the uniform resource locator (URL) path.
Although not recommended, if you create the My Site host deeper in the path, it must be under an explicit inclusion managed path. Additionally, you must create a separate site collection at the web application root, although this site collection can be empty and created without a template.
-The URL for a My Site host site collection is shared by all users of the same User Profile service application. The URL for **Newsfeed** is http:// _hostname_/default.aspx, and the URL for **About Me** is http:// _hostname_/person.aspx, where _hostname_ is the address of the site collection. For example, if you configure your My Site host site collection at http://contoso.com/my, users access their newsfeeds and profiles at http://contoso.com/my/default.aspx and http://contoso.com/my/person.aspx, respectively.
+The URL for a My Site host site collection is shared by all users of the same User Profile service application. The URL for **Newsfeed** is http:// _hostname_/default.aspx, and the URL for **About Me** is http:// _hostname_/person.aspx, where _hostname_ is the address of the site collection. For example, if you configure your My Site host site collection at https://contoso.com/my, users access their newsfeeds and profiles at https://contoso.com/my/default.aspx and https://contoso.com/my/person.aspx, respectively.
Although these URLs are the same for all users of a User Profile service application, the information displayed for each user is different. SharePoint Server determines the information to display based on the user's logon account. The information is targeted to that specific user and is provided by the SharePoint service applications referred to in this article.
-When a visitor views another user's My Site, the visitor can see only the user's profile page. This URL is http:// _hostname_/person.aspx?accountname= _account_, where _hostname_ is the address of the site collection and _account_ is the user name (and, if it is configured, the user's domain name). For example, http://contoso.com/my/person.aspx?accountname=sidney.
+When a visitor views another user's My Site, the visitor can see only the user's profile page. This URL is http:// _hostname_/person.aspx?accountname= _account_, where _hostname_ is the address of the site collection and _account_ is the user name (and, if it's configured, the user's domain name). For example, https://contoso.com/my/person.aspx?accountname=sidney.
### Individual site collections A user's individual site collection hosts the document library of the user's individual My Site. An individual site collection is created the first time that a user accesses the My Site. This ability to create an individual site collection requires the following configuration in SharePoint Server: -- The web application that hosts My Sites has a wildcard inclusion managed path, such as sites or personal. This is the path under which the individual site collections will be created when users access their My Sites for the first time.
+- The web application that hosts My Sites has a wildcard inclusion managed path, such as sites or personal. This path is the one under which the individual site collections will be created when users access their My Sites for the first time.
- The **Setup My Sites** settings for the User Profile service application are configured to use the URL of the My Site host site collection and the wildcard inclusion managed path for individual site collections. -- The web application is enabled for self-service site creation. This functionality enables the individual site collections to be created under the specified wildcard inclusion managed path. The self-service site creation feature has special security considerations for cross-site scripting. This strengthens the recommendation to host My Sites in a dedicated web application to isolate any scripts running in a My Site from affecting other sites in your environment.
+- The web application is enabled for self-service site creation. This functionality enables the individual site collections to be created under the specified wildcard inclusion managed path. The self-service site creation feature has special security considerations for cross-site scripting. These considerations strengthen the recommendation to host My Sites in a dedicated web application to isolate any scripts running in a My Site from affecting other sites in your environment.
- Users must have **Create Personal Site** permissions to create a My Site. By default, this permission is enabled for all authenticated users. For more information, see [Plan users and user permissions](my-sites-planning.md#planusers) later in this article.
-The URL to a user's document library section of a My Site is in the format of http:// _hostname_/ _managed_path_/ _account_/documents, where _hostname_ is the address of the My Site host site collection, _managed_path_ is the managed path for the My Site host, and _account_ is the account of the user logged on. For example, if you configure your My Site host site collection and managed path at http://contoso.com/my, users access their documents at http://contoso.com/my/ _account_/documents.
+The URL to a user's document library section of a My Site is in the format of http:// _hostname_/ _managed_path_/ _account_/documents, where _hostname_ is the address of the My Site host site collection, _managed_path_ is the managed path for the My Site host, and _account_ is the account of the user logged on. For example, if you configure your My Site host site collection and managed path at https://contoso.com/my, users access their documents at https://contoso.com/my/ _account_/documents.
With the _account_ part of the URL, when you set up My Sites, you have three options to specify how to name an individual user's site collection, as shown in the following table.
With the _account_ part of the URL, when you set up My Sites, you have three op
|**Option**|**Description**| |:--|:--|
-|**User name (do not resolve conflicts)** <br/> |By using this option, the My Site name is the user name of the account. This is not a user's display name. For example, if a user's friendly name is Sidney Higa and the user's account is sidney, the site collection is named sidney. Only choose the first option if you are sure that all user names in your organization are unique. Otherwise users will encounter conflicts when they provision their My Sites. If a conflict occurs, the first user who creates a My Site with a user name is successful. However, the next user who tries to use the same user name cannot create a My Site. <br/> |
-|**User name (resolve conflicts by using domain_username)** <br/> |By using this option, the first user who has a duplicate user name will have a My Site created by using the user name only, and a second user who has that same user name will have a My Site created by using both the domain name and user name. For example, the first user will have a My Site created under http://contoso.com/my/sidney/default.aspx while the second user will have a My Site created under http://contoso.com/my/CONTOSO_sidney/default.aspx. Choose this option when it is possible for a user name to exist multiple times in an organization, such as when you have multiple domains. Because a user name is guaranteed to be unique only within its own directory source, this option prevents two users who have the same user name but different domains from encountering issues when they create their My Sites. <br/> |
-|**Domain and user name (will not have conflicts)** <br/> |By using this option, all My Site names are created by using both the domain name and user name. For example, http://contoso.com/my/CONTOSO_sidney/default.aspx. Choose this option when you want My Sites to be consistently named with the domain name and user name, regardless of whether conflicts with user names exist or not. <br/> |
+|**User name (do not resolve conflicts)** <br/> |By using this option, the My Site name is the user name of the account. This name isn't a user's display name. For example, if a user's friendly name is Sidney Higa and the user's account is sidney, the site collection is named sidney. Only choose the first option if you're sure that all user names in your organization are unique. Otherwise users will encounter conflicts when they provision their My Sites. If a conflict occurs, the first user who creates a My Site with a user name is successful. However, the next user who tries to use the same user name can't create a My Site. <br/> |
+|**User name (resolve conflicts by using domain_username)** <br/> |By using this option, the first user who has a duplicate user name will have a My Site created by using the user name only, and a second user who has that same user name will have a My Site created by using both the domain name and user name. For example, the first user will have a My Site created under https://contoso.com/my/sidney/default.aspx while the second user will have a My Site created under https://contoso.com/my/CONTOSO_sidney/default.aspx. Choose this option when it's possible for a user name to exist multiple times in an organization, such as when you have multiple domains. Because a user name is guaranteed to be unique only within its own directory source, this option prevents two users who have the same user name but different domains from encountering issues when they create their My Sites. <br/> |
+|**Domain and user name (will not have conflicts)** <br/> |By using this option, all My Site names are created by using both the domain name and user name. For example, https://contoso.com/my/CONTOSO_sidney/default.aspx. Choose this option when you want My Sites to be consistently named with the domain name and user name, regardless of whether conflicts with user names exist or not. <br/> |
## Related service applications <a name="relsvcapps"> </a>
The User Profile service application is required for My Sites.
#### Plan for profile synchronization
-Although configuring the User Profile service application is required for My Sites, synchronizing profiles between SharePoint Server and directory services or business applications is optional but highly recommended. Profile synchronization provides rich functionality for My Sites by enabling the User Profile service application to collect information about users in an organization from directory services and business applications. As a result, consistent and timely information is always available on a user's My Site. Information about users can also be synchronized across the deployment among all site collections that use the same User Profile service application. User information can also be used by personalization features to increase the value of collaboration and relationships in an organization.
+Although configuring the User Profile service application is required for My Sites, synchronizing profiles between SharePoint Server and directory services or business applications is optional but recommended. Profile synchronization provides rich functionality for My Sites by enabling the User Profile service application to collect information about users in an organization from directory services and business applications. As a result, consistent and timely information is always available on a user's My Site. Information about users can also be synchronized across the deployment among all site collections that use the same User Profile service application. User information can also be used by personalization features to increase the value of collaboration and relationships in an organization.
#### Plan policies and privacy
-SharePoint Server provides a default set of policies that you can configure to make the appropriate information available to meet the needs of an organization. You can also create and deploy custom policy features to meet specific needs. When planning for My Sites, you should define which information is needed for key business processes in an organization and which information might be unsuitable for sharing across an organization. Between these extremes is the information that should be shared only among some users. In the case of information that might be unsuitable for sharing across an organization, you must create policies to address these specific situations.
+SharePoint Server provides a default set of policies that you can configure to make the appropriate information available to meet the needs of an organization. You can also create and deploy custom policy features to meet specific needs. When planning for My Sites, you should define which information is needed for key business processes in an organization and which information might be unsuitable for sharing across an organization. Between these extremes is the information that should be shared only among some users. If there's information that might be unsuitable for sharing across an organization, you must create policies to address these specific situations.
Additionally, My Site features might store or use personally identifiable information. When planning to deploy My Sites, make sure that you carefully plan how to control the behavior of these features ΓÇö or turn off the features ΓÇö to help protect the privacy of this information. These decisions are affected by several factors, such as corporate privacy practices, and regional or national/regional privacy laws.
For users to create My Sites, maintain their profiles, follow people and content
By default, all authenticated users are granted all these permissions, but you can configure specific permissions depending on your needs. For example, you could allow only full-time employees to create My Sites, instead of all workers in your organization. There are seven different combinations of user permissions available to grant to users. However, not all of these permission combinations provide the expected results. As a best practice, simplify administration by granting permissions to security groups instead of specific users. > [!NOTE]
-> Changing user permissions in the User Profile service application is not recommended. Any changes that you make will not impact the user experience in a meaningful way. For example, if you remove the **Follow People and Edit Profile** permission the user will still be able to edit profiles and other users will still be able to follow people they choose. Additionally, if you remove the **Follow People and Edit Profile** permission for a My Site user the Tags and Notes feature is disabled. We do not recommend removing any social features.
+> Changing user permissions in the User Profile service application isn't recommended. Any changes that you make won't impact the user experience in a meaningful way. For example, if you remove the **Follow People and Edit Profile** permission the user will still be able to edit profiles and other users will still be able to follow people they choose. Additionally, if you remove the **Follow People and Edit Profile** permission for a My Site user the Tags and Notes feature is disabled. We do not recommend removing any social features.
### Managed metadata service application <a name="mmsapp"> </a>
Although not required for My Sites, the SharePoint Server Search service applica
When a user searches for people, results contain links to the public profiles of users and links to contact them by email or messaging programs. When planning for My Sites, you might want to consider supplementing the default people search scope, and supplementing the **Search Center** tab with customized search scopes and tabs for more specific groups of users.
-If the administrator of the User Profile service application differs from the administrator of the Search service application, the User Profile service application administrator should review the information architecture and site hierarchy to determine the key business concepts that might relate to specific groups of users for whom other users might search across sites. Then the User Profile service application administrator can work with the Search service application administrator to develop search scopes and people search tabs for those specific groups. User Profile service application administrators can also use their knowledge of the user profiles they manage to determine other useful groups of users, and to create additional specific search scopes and search tabs for those groups.
+If the administrator of the User Profile service application differs from the administrator of the Search service application, the User Profile service application administrator should review the information architecture and site hierarchy to determine the key business concepts that might relate to specific groups of users for whom other users might search across sites. Then the User Profile service application administrator can work with the Search service application administrator to develop search scopes and people search tabs for those specific groups. User Profile service application administrators can also use their knowledge of the user profiles they manage to determine other useful groups of users, and to create more specific search scopes and search tabs for those groups.
Site collection administrators can also create site-level search scopes for users who are members of their site collections.
-People search planning also feeds back into user profile planning. Initial planning might reveal people or groups of users whom you want to make it easier to find. However, additional user profile properties might have to be created to allow for those users to be found easily.
+People search planning also feeds back into user profile planning. Initial planning might reveal people or groups of users whom you want to make it easier to find. However, more user profile properties might have to be created to allow for those users to be found easily.
### Expertise search <a name="searchapp"> </a> When planning My Sites, you should determine whether you want to enable users to locate colleagues within the organization based on the colleagues' expertise. People search and expertise tagging help users locate people inside an organization who have identified themselves as having significant experience with a particular subject. Users in your organization can add terms to their profile that describe areas in which they have experience. These terms are used by people search when a user searches for someone in the organization who has experience in a particular area.
-If email analysis is enabled, users can also find people by using email analysis in Outlook. Colleague suggestions are imported from Outlook if you are using Outlook email. If you are using Outlook, SharePoint Server analyzes sent email messages and then makes colleague and keyword suggestions based on this analysis. Users can then see these suggestions when they edit their profiles.
+If email analysis is enabled, users can also find people by using email analysis in Outlook. Colleague suggestions are imported from Outlook if you're using Outlook email. If you're using Outlook, SharePoint Server analyzes sent email messages and then makes colleague and keyword suggestions based on this analysis. Users can then see these suggestions when they edit their profiles.
Although you can enable email analysis for all users in Outlook or only for specific groups by using Group Policy, users can opt out of this feature. If email analysis is disabled for all users, individual users can still opt in.
You can enable or disable these jobs, and configure their schedules to meet the
## Planning for geographically distributed deployments <a name="geodist"> </a>
-When planning for My Sites, you must consider the location of the users in the organization and the number of farms or User Profile service applications that will host My Sites. If you have more than one farm or User Profile service application, you will likely have to configure trusted My Site host locations.
+When planning for My Sites, you must consider the location of the users in the organization and the number of farms or User Profile service applications that will host My Sites. If you have more than one farm or User Profile service application, you'll likely have to configure trusted My Site host locations.
### User Profile service deployment considerations for My Sites
-My Sites depend on the User Profile service application. In SharePoint Server, My Sites should be configured by using one User Profile service application. Server farm architectures using a single User Profile service application include the following:
+My Sites depend on the User Profile service application. In SharePoint Server, My Sites should be configured by using one User Profile service application. Server farm architectures using a single User Profile service application include:
- A single server farm with a single User Profile service application. -- An enterprise services farm sharing a single User Profile service application together with one or more consuming farms. The My Sites Host is located on one of the consuming farms. In SharePoint Server, the consuming farm must be physically located in the same datacenter as the enterprise services farm when you share the User Profile service application. Consuming the User Profile service application from another farm over a WAN connection is not supported. This means that both the User Profile service application and the My Site Host must be located in the same datacenter.
+- An enterprise services farm sharing a single User Profile service application together with one or more consuming farms. The My Sites Host is located on one of the consuming farms. In SharePoint Server, the consuming farm must be physically located in the same datacenter as the enterprise services farm when you share the User Profile service application. Consuming the User Profile service application from another farm over a WAN connection isn't supported. This limitation means that both the User Profile service application and the My Site Host must be located in the same datacenter.
### Trusted My Site host locations
The **Trusted My Site Host Locations** feature prevents a user from creating mor
For example, in a server farm deployment that spans geographic regions, you might have separate User Profile service applications for each region or regional server farms in the environment. By default, a user can create a different My Site in each User Profile service application or server farm, which could cause unwanted results from both an administration perspective and a user perspective. When you have multiple My Sites for an individual user in an organization, server resource needs increase. Additionally, users might not understand or want multiple My Sites.
-To prevent individual users from creating multiple My Sites, configure trusted My Site host locations. When specified, users are redirected to the single My Site host location that is intended for their accounts regardless of where they are browsing when they attempt to create or access their My Sites. This feature ensures that each user can create only one My Site in an organization.
+To prevent individual users from creating multiple My Sites, configure trusted My Site host locations. When specified, users are redirected to the single My Site host location that is intended for their accounts regardless of where they're browsing when they attempt to create or access their My Sites. This feature ensures that each user can create only one My Site in an organization.
Configuring trusted My Site host locations is optional. ## Planning for the multilingual user interface <a name="mui"> </a>
-When enabled, users can use the multilingual user interface feature for their My Sites. This feature is used to display the site's user interface in a secondary language that the user prefers instead of the default, primary language that was selected when the site was created. By default, when a new site is created, it is created in the default, primary language of the SharePoint Server installation on the server. A farm administrator must install language packs on the server before sites can be created in languages other than the default, primary language.
+When enabled, users can use the multilingual user interface feature for their My Sites. This feature is used to display the site's user interface in a secondary language that the user prefers instead of the default, primary language that was selected when the site was created. By default, when a new site is created, it's created in the default, primary language of the SharePoint Server installation on the server. A farm administrator must install language packs on the server before sites can be created in languages other than the default, primary language.
For My Sites, the multilingual user interface feature is controlled by the **Language Options** setting when you configure My Site settings. The languages that are available to users correspond to the language packs installed in the server farm. For more information about language packs, see [Install or uninstall language packs for SharePoint Server 2016](install-uninstall-language-packs-2019.md).
For My Sites, the multilingual user interface feature is controlled by the **Lan
Because My Site users can edit their profiles, generate newsfeed activities, upload and download documents, and so on, plan carefully for the storage and capacity needs of your environment. Take into consideration the content databases for My Sites and the databases for the related services of My Sites.
-Additionally, SharePoint Server includes a default Personal Site quota template, which has a storage limit of 100 MB and no user limit. This quota template is used for each user's individual site collection in the user's My Site. Because feed activity is now stored in lists in the user's My Site, and those lists are not archived, storage needs will continue to grow. Therefore, consider increasing the personal site quota to 500 MB or more depending on the activity that you expect in the feeds.
+Additionally, SharePoint Server includes a default Personal Site quota template, which has a storage limit of 100 MB and no user limit. This quota template is used for each user's individual site collection in the user's My Site. Because feed activity is now stored in lists in the user's My Site, and those lists aren't archived, storage needs will continue to grow. Therefore, consider increasing the personal site quota to 500 MB or more depending on the activity that you expect in the feeds.
Configuring quota templates is optional, but recommended. ## Planning for file types <a name="files"> </a>
-Like other web applications in SharePoint Server, you can configure the file types that users can upload to or download from the web application that hosts My Sites. This is useful if you want to prevent users from uploading or downloading file types that can be large, such as media file types, or file types that can be run on the client computer, such as executable files.
+Like other web applications in SharePoint Server, you can configure the file types that users can upload to or download from the web application that hosts My Sites. This configuration is useful if you want to prevent users from uploading or downloading file types that can be large, such as media file types, or file types that can be run on the client computer, such as executable files.
By default, SharePoint Server blocks certain file types. However, you can configure My Sites to allow these file types, or add other file types to block depending on the needs in your organization.
SharePoint Updated Product Servicing Policy For Sharepoint Server Se https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-server-se.md
audience: ITPro
f1.keywords: - NOCSH + ms.localizationpriority: medium - IT_Sharepoint_Server
SharePoint Configure And Use The Exchange Connector https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/search/configure-and-use-the-exchange-connector.md
Use one of the following procedures to create a content source for Exchange Serv
- _\<protocol\>_:// _host name_/public/ _subfolder_ - Where _\<protocol\>_ can be http or https, _host name_ is the NetBIOS or FQDN of the server that is running Exchange Server, and _subfolder_ is the name of the specific subfolder that you want to crawl.
- For example, if you want to crawl all subfolders in the public folder on a server that is named exch-01 and that is in the Contoso domain, and that server does not use SSL, you could type either http://exch-01/public or http://exch-01.contoso.com. To crawl only a specific subfolder named Bob in the same public folder, type http://exch-01/public/bob or http://exch-01.contoso.com/bob.
+ For example, if you want to crawl all subfolders in the public folder on a server that is named exch-01 and that is in the Contoso domain, and that server does not use SSL, you could type either `https://exch-01/public` or `https://exch-01.contoso.com`. To crawl only a specific subfolder named Bob in the same public folder, type `https://exch-01/public/bob` or `https://exch-01.contoso.com/bob`.
> [!NOTE] > For performance reasons, you cannot add the same start addresses to multiple content sources.
SharePoint Overview Of Analytics Processing https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/search/overview-of-analytics-processing.md
Information that results from the search analyses is used to enrich items in the
| **Analysis** | **Description** | | : | :-- | | Anchor text processing | Anchor text processing analyzes how items in the content corpus are interlinked. It also includes the anchor texts associated with the links in the analysis. The Analytics Processing Component uses the results of the analysis to add rank points to the items in the search index. |
-| Click Distance | The Click Distance analysis calculates the number of clicks between an authoritative page and the items in the search index. An authoritative page can be a top level site, for example http://www.contoso.com, or other pages that are viewed as important. You can define Authorative pages in Central Administration. <br/> <br/> The Analytics Processing Component uses the results of the analysis to add rank points to the items in the search index. |
+| Click Distance | The Click Distance analysis calculates the number of clicks between an authoritative page and the items in the search index. An authoritative page can be a top level site, for example, https://www.contoso.com, or other pages that are viewed as important. You can define Authoritative pages in Central Administration. <br/> <br/> The Analytics Processing Component uses the results of the analysis to add rank points to the items in the search index. |
| Search Clicks | The Search Clicks analysis uses information about which items users click in search results to boost or demote items in the search index. The analysis calculates a new ranking of items compared to the base relevance. <br/> <br/>The clicks data is stored in the Link database. | | Social Tags | The Social Tags analysis analyses social tags, which are words or phrases that users can apply to content to categorize information in ways that are meaningful to them. <br/> <br/>In SharePoint Server, social tags are not used for refinement, ranking, or recall by default. However, you can create custom search experiences that use social tags and the information from this analysis. | | Social Distance | The Social Distance analysis calculates the relationship between users who use the Follow person feature. The analysis calculates first and second level Followings: first level Followings first, and then Followings of Following. <br/> <br/>The information is used to sort People Search results by social distance. |
Information that results from the search analyses is used to enrich items in the
### Usage analytics <a name="BKMK_UsageAnalytics"> </a>
-Usage analytics is a set of analyses that receive information about user actions, or usage events, such as clicks or viewed items, on the SharePoint Server site. Usage analytics combines this information with information about crawled content from the Search analyses, and processes the information. Information about recommendations and usage events is added to the search index. Statistics on the different usage events is added to the search index and sent to the Analytics reporting database.
+Usage analytics is a set of analyses that receive information about user actions, or usage events, such as clicks or viewed items, on the SharePoint Server site. Usage analytics combines this information with information about crawled content from the Search analyses, and processes the information. Information about recommendations and usage events is added to the search index. Statistics on the different usage events are added to the search index and sent to the Analytics reporting database.
-A default set of usage events is defined out of the box. The default events are always registered and analyzed by SharePoint Server. You can also configure custom event types. For more information about the default usage events, see [The usage events used by Usage analytics](overview-of-analytics-processing.md#BKMK_TheDefaultUsageEvents).
+A default set of usage events are defined out of the box. The default events are always registered and analyzed by SharePoint Server. You can also configure custom event types. For more information about the default usage events, see [The usage events used by Usage analytics](overview-of-analytics-processing.md#BKMK_TheDefaultUsageEvents).
**Analyses in usage analytics** | **Analysis** | **Description** | | : | :- |
-| Usage counts | The Usage counts analysis analyzes events, such as viewed or clicked items. The analysis calculates how many times an item is opened *overall* , not just from the search result page, but also, for example, when a document is opened from Word or clicked in a SharePoint Server library. <br/> <br/>The analysis calculates both recent events and all time events, for all defined event types. By default, recent events is set to the last 14 days, but you can set it between 1 and 14 days (on-premises). The statistics data is aggregated on the site level, the site collection level, and the organization level (SharePoint in Microsoft 365). <br/> <br/>The usage events are stored temporarily on the web front end and are pushed to the Search Service Application every 15 minutes. Usage events are kept on disk for up to 14 days before they are deleted. Every day, the previous full day of Usage counts data is analyzed. <br/> <br/>Usage counts are added to the items in the search index to improve search relevancy. The information is also stored in the Analytics reporting database, and can be used to display popular items on a site. |
+| Usage counts | The Usage counts analysis analyzes events, such as viewed or clicked items. The analysis calculates how many times an item is opened *overall*, not just from the search result page, but also, for example, when a document is opened from Word or clicked in a SharePoint Server library. <br/> <br/>The analysis calculates both recent events and all time events, for all defined event types. By default, recent events are set to the last 14 days, but you can set it between 1 and 14 days (on-premises). The statistics data is aggregated on the site level, the site collection level, and the organization level (SharePoint in Microsoft 365). <br/> <br/>The usage events are stored temporarily on the web front end and are pushed to the Search Service Application every 15 minutes. Usage events are kept on disk for up to 14 days before they are deleted. Every day, the previous full day of Usage counts data is analyzed. <br/> <br/>Usage counts are added to the items in the search index to improve search relevancy. The information is also stored in the Analytics reporting database, and can be used to display popular items on a site. |
| Recommendations | The Recommendations analysis creates recommendations between items based on how users have interacted with the items on a site. The analysis uses the same event file as Usage counts, but looks for patterns in the usage. The analysis calculates an item-to-item relationship graph and adds the information to the items in the search index. <br/> <br/>The information can be used to display recommendations on a site, for example "People who viewed this also viewed". <br/> <br/>The data is stored in the Analytics reporting database for recovery purposes. Reports related to recommendations are based on the Usage counts analysis. | | Activity ranking | The Activity ranking analysis uses the activity tracking of usage events (the event rate) to influence search relevancy. Items that have high usage activity (clicks or views) typically get a higher activity rank score than less popular items. <br/> <br/>The analysis looks for *trends* in item activity. If you only count the number of events, older items will typically "win" in relevancy, because the older documents have had more time to collect activity. The activity tracking helps newer documents that have high usage activity get a higher rank. |
The Analytics Processing Component generates data that is used to create the fol
## Privacy protection of the data collected by the Analytics Processing Component <a name="BKMK_Reporting"> </a>
-Parts of the data that the Analytics Processing Component collects are related to personally identifiable information. SharePoint Server has different features to protect the privacy of this information.
+The Analytics Processing Component collects those parts of the data that are related to personally identifiable information. SharePoint Server has different features to protect the privacy of this information.
For each usage event, the Analytics Processing Component logs the following information:
SharePoint Improved Asp Net View State Security Key Management https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/security-for-sharepoint-server/improved-asp-net-view-state-security-key-management.md
Last updated 09/15/2021
Title: Improved ASP.NET view state security and key management -+ audience: ITPro f1.keywords:
SharePoint Onedrive For Business Planning https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/sites/onedrive-for-business-planning.md
In a SharePoint Server on-premises environment, you may have the option to save
The sync app also provides your users the added convenience of working with files directly from the local Microsoft OneDrive sync folder. Work with and saving your files directly in the folder is more convenient than opening your My Sites document library. > [!IMPORTANT]
-> Use the [previous OneDrive for Business sync app _Groove.exe_](/onedrive/install-previous-sync-app.md) to sync files in SharePoint Server 2016 or earlier. The new OneDrive sync app OneDrive.exe is supported in SharePoint Server Subscription Edition and 2019. For more information, see [configure-syncing-with-the-onedrive-sync-app](../install/configure-syncing-with-the-onedrive-sync-app.md).
+> Use the [previous OneDrive for Business sync app _Groove.exe_](/onedrive/install-previous-sync-app) to sync files in SharePoint Server 2016 or earlier. The new OneDrive sync app OneDrive.exe is supported in SharePoint Server Subscription Edition and 2019. For more information, see [configure-syncing-with-the-onedrive-sync-app](../install/configure-syncing-with-the-onedrive-sync-app.md).
**Changes in file location**
SharePoint Automatically Created Managed Properties In Sharepoint https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/automatically-created-managed-properties-in-sharepoint.md
description: "Learn about the naming conventions for automatically created crawl
## How site columns become managed properties <a name="BKMK_FromSiteColumnsToManagedProperties"> </a>
-When you add columns to a SharePoint library or list, you can choose to add regular columns or site columns. For information about the difference between regular columns and site columns, see [Introduction to columns](/previous-versions/office/developer/sharepoint-2010/ms450825(v=office.14)). In SharePoint, only site columns that contain values will automatically become managed properties when they are crawled. Regular columns will not automatically become managed properties when they are crawled.
+When you add columns to a SharePoint library or list, you can choose to add regular columns or site columns. For information about the difference between regular columns and site columns, see [Introduction to columns](/previous-versions/office/developer/sharepoint-2010/ms450825(v=office.14)). In SharePoint, only site columns that contain values will automatically become managed properties when they're crawled. Regular columns won't automatically become managed properties when they're crawled.
Before you can share content in a library or list with other site collections, you must share the library or list as a catalog, and then start a full crawl of the content. For more information, see "Share a library or list as a catalog" in [Configure cross-site publishing in SharePoint Server](../administration/configure-cross-site-publishing.md).
During the crawl of library content, the following actions are performed on the
|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.|
+|Number|ows_q_NMBR_SiteColumnName|SiteColumnNameOWSNMBR|Textual representation of the number. The value will use dot as a decimal symbol. <br/> This format can't 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 can't 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 can't 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.|
+|Hyperlink or Picture|ows_q_URLH_SiteColumnName|SiteColumnNameOWSURLH|URL, description. For example, https://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.|
+|Integer\*|ows_q_INTG_SiteColumnName|SiteColumnNameOWSINTG|Textual representation of the integer. <br/> This format can't 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;#|
SharePoint Certificate Notification Contacts Haven't Been Configured https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/certificate-notification-contacts-haven't-been-configured.md
Last updated 10/06/2021
Title: "Certificate notification contacts haven't been configured" -+ audience: ITPro f1.keywords:
SharePoint Ssl Certificates Expire https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/ssl-certificates-expire.md
Last updated 10/06/2021
Title: "SSL certificates are about to expire" -+ audience: ITPro f1.keywords:
SharePoint Ssl Certificates Have Expired https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/ssl-certificates-have-expired.md
Last updated 10/06/2021
Title: "SSL certificates have expired" -+ audience: ITPro f1.keywords:
SharePoint Upcoming Ssl Certificate Expirations https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/upcoming-ssl-certificate-expirations.md
Last updated 10/06/2021
Title: "Upcoming SSL certificate expirations" -+ audience: ITPro f1.keywords:
SharePoint New And Improved Features In Sharepoint Server Subscription Edition https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition.md
Last updated 06/25/2021
Title: "New and improved features in SharePoint Server Subscription Edition" -+ audience: ITPro f1.keywords:
SharePoint What S Deprecated Or Removed From Sharepoint Server Subscription Edition https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/what-s-deprecated-or-removed-from-SharePoint-Server-Subscription-Edition.md
Last updated 07/02/2021
Title: "What's deprecated or removed from SharePoint Server Subscription Edition?" -+ audience: ITPro f1.keywords: