Updates from: 06/26/2021 03:17:56
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Manage Query Suggestions https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/manage-query-suggestions.md
description: "Learn how to add phrases that you want the system to suggest to us
# Customize query suggestions in SharePoint search
-Query spelling suggestions are words that appear below the search box as a user types a query. SharePoint automatically creates a query suggestion when you've clicked a search result for a query at least six times. For example, if you've entered the query word "coffee" and then clicked a search result six times, "coffee" automatically becomes a query suggestion.
+Query spelling suggestions are words that appear below the search box as a user types a query. SharePoint automatically creates query suggestions from frequently entered queries that resulted in a click on a search result. For example, if you've repeatedly entered the query word "coffee" and then clicked a search result each time, "coffee" automatically becomes a query suggestion.
-Automatic query suggestions are generated daily for each result source and each site collection, so the query suggestions can be different for different result sources and site collections.
+Automatic query suggestions are generated periodically for each result source and each site collection, so the query suggestions can be different for different result sources and site collections.
For example, in the following screenshot, "contoso" is automatically suggested. ![Screenshot of Query Suggestion.](media/query-suggestion.png)
Query suggestions are turned on by default. To turn them off, go to **Search Sug
### Related tasks
-You can edit a list of query suggestions that you've manually created. To edit a list that you've already imported in to SharePoint, choose **Export to text file**, update the text file with your changes, and then re-import it. After you've uploaded your query suggestions file, it might take a few hours until your query suggestions are displayed. You can check that they're working properly by entering a phrase from your list of query suggestions in the search box. The query suggestion should appear below the search box.
+You can edit a list of query suggestions that you've manually created. To edit a list that you've already imported into SharePoint, choose **Export to text file**, update the text file with your changes, and then re-import it. After you've uploaded your query suggestions file, it might take up to a week until your query suggestions are displayed. You can check that they're working properly by entering a phrase from your list of query suggestions in the search box. The query suggestion should appear below the search box.
To get rid of a list of query terms, you must overwrite it. Do this by importing an empty text file.
SharePoint Manage Sites In New Admin Center https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/manage-sites-in-new-admin-center.md
When you select a built-in or custom view, you can add a card to your home page
![A tracked view card](media/tracked-view.png) > [!NOTE]
-> If you remove a tracked view card from your home page, you can't add it back from the Add cards panel. YOu need to open the view on the Active sites page and select **Track view**.
+> If you remove a tracked view card from your home page, you can't add it back from the Add cards panel. You need to open the view on the Active sites page and select **Track view**.
## Search for a site <a name="search"> </a>
SharePoint Security Considerations Of Allowing Custom Script https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/security-considerations-of-allowing-custom-script.md
If you've allowed custom script, you can change the setting to later prevent use
The [SharePoint Framework](/sharepoint/dev/spfx/sharepoint-framework-overview) is a page and web part model that provides a governed and fully supported way to build solutions using scripting technologies with support for open-source tooling. Key features of the SharePoint Framework: -- The framework runs in the context of the current user and connection in the browser. It doesn't use iFrames.
+- The framework runs in the context of the current user and connection in the browser.
- The controls are rendered in the normal page Document Object Model (DOM).
The [SharePoint Framework](/sharepoint/dev/spfx/sharepoint-framework-overview) i
- Developers can access the lifecycle. Also to render, they can access load, serialize and deserialize, configuration changes, and more. -- You can use any browser framework you like: React, Handlebars, Knockout, AngularJS, and more.
+- You can use any browser framework you like: React, Handlebars, Knockout, Angular, and more.
-- The toolchain is based on common open source client development tools like npm, TypeScript, Yeoman, web pack, and gulp.
+- The toolchain is based on common open source client development tools like npm, TypeScript, Yeoman, webpack, and gulp.
- Admins have governance tools to immediately disable solutions regardless of the number of instances that have been used and the number of pages or sites across which they've been used.
SharePoint Tenant Rename https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/tenant-rename.md
description: "Learn how to change your SharePoint domain name using PowerShell"
It's now possible to change the SharePoint domain name for your organization in Microsoft 365. For example, if the name of your organization changes from "Contoso" to "Fabrikam," you can change `contoso.sharepoint.com` to `fabrikam.sharepoint.com`. > [!IMPORTANT]
-> - This feature is only available for customers that have been accepted into the Private Preview program. If you would like to do so, you can [nominate yourself into the Private Preview](https://aka.ms/SPOTenantRenameNomination). Note that the nomination does not necessarily mean that you will be accepted. We review these on a case-by-case basis and will only be in contact if you are accepted.
-> - This feature is not available for organizations that have set up a multi-geo.
+> - This feature is available only for customers who have been accepted into the Private Preview program. [Request to join the Private Preview](https://aka.ms/SPOTenantRenameNomination). Note that submitting a nomination does not guarantee acceptance into the program. We review the nominations on a case-by-case basis and will contact you if you're accepted.
+> - This feature is not available for organizations that have set up multi-geo.
> [!NOTE]
-> This change affects only SharePoint and OneDrive URLs. It doesn't impact email addresses. For info about changing a site address, for example, from `https://contoso.sharepoint.com/sites/sample1` to `https://contoso.sharepoint.com/sites/sample2`, see [Change a site address](change-site-address.md).
+> - This change affects only SharePoint and OneDrive URLs. It doesn't impact email addresses.
+> - For info about changing a site address, for example, from `https://contoso.sharepoint.com/sites/sample1` to `https://contoso.sharepoint.com/sites/sample2`, see [Change a site address](change-site-address.md).
+> - When you rename your SharePoint domain, we create a redirect at the previous address.
## Limitations
It's now possible to change the SharePoint domain name for your organization in
|App/feature |Limitation |Action required | |||| | Deleted sites | Any sites that have been deleted can't be restored after the change. | Before changing your domain name, review the Deleted sites page in the SharePoint admin center and restore any sites that you might want to keep. |
-| Long URLs | Any absolute URLs to sites or content that exceed the maximum URL length limit of 400 characters won't work. | If the new domain name is longer than the original, review the URLs of all sites, lists, document libraries, list items, and files before your change the domain name to make sure the new URLs won't exceed 400 characters. |
| Multi-Geo configurations | Your SharePoint domain name can't be changed if your organization is currently set up for Microsoft 365 Multi-Geo or was previously set up for it. | No action available. | | Point-in-time restoration | Restoring a site to a previous time before the domain name change isn't possible. | No action available.| | Vanity domain configurations | Your domain name can't be changed if you have a vanity domain configuration. | No action available. | - ## Step 1: Add the new domain name 1. Check the availability of the new domain you want by entering the full SharePoint URL in your browser (for example, `https://fabrikam.sharepoint.com`). If you get a ΓÇ£not foundΓÇ¥ (404) error, it indicates the domain is most likely available. If the domain is already registered by another customer, we can't provide any information or contact the customer.
It's now possible to change the SharePoint domain name for your organization in
> If you installed a previous version of the SharePoint Online Management Shell, go to Add or remove programs and uninstall "SharePoint Online Management Shell." 2. Connect to SharePoint as a [global admin or SharePoint admin](./sharepoint-admin-role.md) in Microsoft 365. To learn how, see [Getting started with SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online).+
+ Example:
+
+ `Connect-SPOService -Url "https://contoso-admin.sharepoint.com"`
3. Run the following command to specify the new domain name: ```PowerShell
- Start-SPOTenantRename -DomainName <DomainName> -ScheduleDateTime <YYYY-MM-DDTHH:MM:SSZ> [-WhatIf] [-Confirm]
+ Start-SPOTenantRename -DomainName <DomainName> -ScheduledDateTime <YYYY-MM-DDTHH:MM:SS> [-WhatIf] [-Confirm]
```
- Where "ScheduleDateTime" is at least 24 hours in the future, but not more than 30 days.
+ Where "DomainName" is the part before "sharepoint.com" or "onmicrosoft.com" and "ScheduledDateTime" is at least 24 hours in the future, but not more than 30 days.
+
+ Example:
+
+ `Start-SPOTenantRename -DomainName "fabrikam" -ScheduledDateTime "2021-12-31T10:25:00"`
You can get the status of the rename by running `Get-SPOTenantRenameStatus`.
+During and after the rename, you can get the state of a site by running `Get-SPOSiteRenameState`. For more info about this cmdlet, see [Get-SPOSiteRenameState](/powershell/module/sharepoint-online/get-spositerenamestate).
+ ## Step 3: Review features and settings after the rename 1. Review any firewall rules that might block access to the new domain.
SharePoint Turn On Automated Document Translation https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/administration/turn-on-automated-document-translation.md
For more information, see [Set-SPTranslationServiceApplication](/powershell/modu
- If the account that is used by the application pool that was assigned to the Machine Translation service application differs from the one used by the User Profile service application, you must add it to the list of accounts that can use the User Profile service application and grant it Full Control permissions. For more information, see [Restrict or enable access to a service application in SharePoint Server](restrict-or-enable-access-to-a-service-application.md). -- The Microsoft Translator Hub is an extension of Microsoft Translator and lets you build automatic language translation systems that integrate with your website. After you build a custom system, the **Test System** page on the **Projects** tab in the Microsoft Translator Hub displays a category ID. You can configure the Machine Translation Service to use the custom translation system by passing the category ID in the `MachineTranslationCategory` parameter. For more information about the Microsoft Translator Hub, see [About Microsoft Translator Hub](https://go.microsoft.com/fwlink/?LinkId=330174).
+- Microsoft Custom Translator is a feature of Microsoft Translator and lets you achieve much higher adherence to the domain-specific terminology and style by training a custom translation system on previously translated in-domain documents. You can configure the Machine Translation Service to use the custom translation system by passing the category ID in the MachineTranslationCategory parameter. For more information about the Microsoft Custom Translator, see [What is Custom Translator?](https://docs.microsoft.com/azure/cognitive-services/translator/custom-translator/overview)
## See also <a name="more"> </a>
For more information, see [Set-SPTranslationServiceApplication](/powershell/modu
[Variations overview in SharePoint Server](variations-overview.md)
-[Plan for variations in SharePoint Server](plan-for-variations.md)
+[Plan for variations in SharePoint Server](plan-for-variations.md)
SharePoint Default Timer Jobs In Sharepoint Server 2019 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/technical-reference/default-timer-jobs-in-sharepoint-server-2019.md
The following table lists the default timer jobs for SharePoint Server 2019.
| Diagnostic Data Provider: SQL Memory DMV | Collects SQL Dynamic Management Views (DMV) data. | Disabled | | Diagnostic Data Provider: Trace Log | Collects Trace Log entries. | Disabled | | Disk Over Quota Warning | Sends out disk over quota warning e-mail notifications. | Daily |
-| Document and List Static Data Fixed Sample job | Timer job to collect fixed sampled static documents and lists information. | Daily |
+| Document and List Static Data Fixed Sample job[<sup>1</sup>](#Note1) | Timer job to collect fixed sampled static documents and lists information. | Daily |
| Document Full Crawl Blob Compression Processing | | Disabled | | Document ID assignment job | Work item that assigns Document ID to all items in the site collection. | Daily | | Document ID enable/disable job | Work item that propagates content type changes across all sites when the Document ID feature is reconfigured. | Daily |
The following table lists the default timer jobs for SharePoint Server 2019.
| Workflow auto Cleanup | Deletes tasks and workflow instances which have been marked complete longer than the expiration specified in the workflow associa... | Daily | | Workflow Failover | Processes events for workflows that have failed and are marked to be retried. | 15 Minutes |
+<a name="Note1"><sup>1</sup></a> This timer job is not needed by SharePoint Server 2019 and is removed by the <a href="https://support.microsoft.com/topic/description-of-the-security-update-for-sharepoint-server-2019-march-9-2021-kb4493230-123bf257-222a-41f5-2ad4-96efe8b5df87">security update for SharePoint Server 2019: March 9, 2021 (KB4493230)</a>.
+ ## See also <a name="DefaultJobs"> </a>
SharePoint Sharepoint Server 2016 Zero Downtime Patching Steps https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/upgrade-and-update/sharepoint-server-2016-zero-downtime-patching-steps.md
For the most part, everything you do on one side of the line (to the 01 servers)
Make sure you've rebooted and tested your WFEs before you take either out of the load balancer to avoid situations where the WFE to be patched first is taken out of rotation, and other WFEs don't handle the resulting load. All servers in the farm should be fresh from a reboot and healthy before you patch. Also, consider stopping Search crawls and Profile Imports during the upgrade or patch window. > [!IMPORTANT]
-> Side-by-side functionality, previously enabled with the below script, has been enabled regardless of the 'enableSideBySide' value as of [KB3178672](https://support.microsoft.com/help/3178672) (March 2017 update) for SharePoint Server 2016 and above.
+> Running in side-by-side ensures that all the web front ends in the farm serve the same static content during the upgrade, even if static files on a given WFE are being upgraded or replaced. Side-by-side is built into PSCONFIG but must be enabled. This feature makes sure users have the same experience of the sites when browsing SharePoint and working on their files, even while file-system files are being changed and updated.
>
-> For SharePoint Server 2016 farms without KB3178672 or higher applied, side-by-side functionality can be applied with the following PowerShell scripts:
+> To enable the side-by-side functionality, execute the following PowerShell script once by using the URL for one of the content web applications:
> > `$webapp = Get-SPWebApplication <webappURL>` > `$webapp.WebService.EnableSideBySide = $true` > `$webapp.WebService.update()` >
-> Running in side-by-side ensures that all the web front ends in the farm serve the same static content during the upgrade, even if static files on a given WFE are being upgraded or replaced. Side-by-side is built in to PSCONFIG but must be enabled. This feature makes sure users have the same experience of the sites when browsing SharePoint and working on their files, even while file-system files are being changed and updated.
-
+> As of [KB3178672](https://support.microsoft.com/help/3178672) (March 2017 update) for SharePoint Server 2016 and above, PSCONFIG will automatically copy all .js, .css, and .htm files within the `16-HIVE\TEMPLATE\LAYOUTS` folder to the `16-HIVE\TEMPLATE\LAYOUTS\<NEW BUILD NUMBER>` folder, required to be able to switch to the new user interface files and complete the side-by-side process as outlined later in this topic in **Phase 2 - PSCONFIG upgrade (4)**.
+>
### Phase 1 - Patch install
Every node in the SharePoint Server 2016 farm has the patches installed, and all
> [!IMPORTANT] > After all servers have been through PSCONFIG successfully, remember to run the SharePoint 2016 Management Shell command below to switch to the new user interface files and complete the side-by-side process:
+ > `$webapp = Get-SPWebApplication <webappURL>`
> `$webapp.WebService.SideBySideToken = <current build number in quotes, ex: "16.0.4338.1000">` > `$webapp.WebService.update()`
The goals here are high availability and fault tolerance. That means top priorit
In examples used here, I draw out physical servers to make concepts easier to grapple with. When it comes time to plan for ZDP, you should draw out your own environment, wherever it lives (complete with rack names/numbers, and server names where each SharePoint Server role can be found). This is one of the quickest ways to isolate any violations of the goals of role redundancy and fault tolerance that might have snuck into your setup, no matter the size your setup may be. ## Related Topics-
-[Video demo of Zero Downtime Patching in SharePoint Server 2016](video-demo-of-zero-downtime-patching-in-sharepoint-server-2016.md)
+[Video demo of Zero Downtime Patching in SharePoint Server 2016](video-demo-of-zero-downtime-patching-in-sharepoint-server-2016.md)