mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge pull request #4754 from MicrosoftDocs/master
Publish 02/12/21, 3:30 PM
This commit is contained in:
Gary Moore
GitHub
commit
f7f775fe60
@ -11,7 +11,7 @@
|
||||
}
|
||||
:scores {
|
||||
;;:terminology 100
|
||||
:qualityscore 65 ;; Confirmed with Hugo that you just comment out the single score and leave the structure in place
|
||||
:qualityscore 80 ;; Confirmed with Hugo that you just comment out the single score and leave the structure in place
|
||||
;;:spelling 40
|
||||
}
|
||||
}
|
||||
|
||||
@ -731,7 +731,6 @@ ms.date: 07/18/2019
|
||||
- [RemoteShell/SpecifyMaxRemoteShells](./policy-csp-remoteshell.md#remoteshell-specifymaxremoteshells)
|
||||
- [RemoteShell/SpecifyShellTimeout](./policy-csp-remoteshell.md#remoteshell-specifyshelltimeout)
|
||||
- [Search/AllowCloudSearch](./policy-csp-search.md#search-allowcloudsearch)
|
||||
- [Search/AllowCortanaInAAD](./policy-csp-search.md#search-allowcortanainaad)
|
||||
- [Search/AllowFindMyFiles](./policy-csp-search.md#search-allowfindmyfiles)
|
||||
- [Search/AllowIndexingEncryptedStoresOrItems](./policy-csp-search.md#search-allowindexingencryptedstoresoritems)
|
||||
- [Search/AllowSearchToUseLocation](./policy-csp-search.md#search-allowsearchtouselocation)
|
||||
|
||||
@ -7571,9 +7571,6 @@ The following diagram shows the Policy configuration service provider in tree fo
|
||||
<dd>
|
||||
<a href="./policy-csp-search.md#search-allowcloudsearch" id="search-allowcloudsearch">Search/AllowCloudSearch</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-search.md#search-allowcortanainaad" id="search-allowcortanainaad">Search/AllowCortanaInAAD</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-search.md#search-allowfindmyfiles" id="search-allowfindmyfiles">Search/AllowFindMyFiles</a>
|
||||
</dd>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/27/2019
|
||||
ms.date: 02/12/2021
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -25,9 +25,6 @@ manager: dansimp
|
||||
<dd>
|
||||
<a href="#search-allowcloudsearch">Search/AllowCloudSearch</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#search-allowcortanainaad">Search/AllowCortanaInAAD</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#search-allowfindmyfiles">Search/AllowFindMyFiles</a>
|
||||
</dd>
|
||||
@ -137,7 +134,6 @@ The following list shows the supported values:
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="search-allowcortanainaad"></a>**Search/AllowCortanaInAAD**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
@ -178,30 +174,6 @@ The following list shows the supported values:
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Added in Windows 10, version 1803. This specifies whether the Cortana consent page can appear in the Azure Active Directory (AAD) device out-of-box-experience (OOBE) flow. If this policy is left in its default state, Cortana will not be shown in the AAD OOBE flow. If you opt-in to this policy, then the Cortana consent page will appear in the AAD OOBE flow..
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
- GP English name: *Allow Cortana Page in OOBE on an AAD account*
|
||||
- GP name: *AllowCortanaInAAD*
|
||||
- GP path: *Windows Components/Search*
|
||||
- GP ADMX file name: *Search.admx*
|
||||
|
||||
<!--/ADMXMapped-->
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 (default) - Not allowed. The Cortana consent page will not appear in AAD OOBE during setup.
|
||||
- 1 - Allowed. The Cortana consent page will appear in Azure AAD OOBE during setup.
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="search-allowfindmyfiles"></a>**Search/AllowFindMyFiles**
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@
|
||||
"audience": "ITPro",
|
||||
"ms.topic": "article",
|
||||
"feedback_system": "None",
|
||||
"hideEdit": true,
|
||||
"hideEdit": false,
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-configuration",
|
||||
|
||||
@ -31,7 +31,7 @@ The following table describes the log files created by Windows Update.
|
||||
To merge and convert Windows Update trace files (.etl files) into a single readable WindowsUpdate.log file, see [Get-WindowsUpdateLog](https://docs.microsoft.com/powershell/module/windowsupdate/get-windowsupdatelog?view=win10-ps&preserve-view=tru).
|
||||
|
||||
>[!NOTE]
|
||||
>When you run the **Get-WindowsUpdateLog** cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpate.log unless you run **Get-WindowsUpdateLog** again.
|
||||
>When you run the **Get-WindowsUpdateLog** cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpdate.log unless you run **Get-WindowsUpdateLog** again.
|
||||
|
||||
### Windows Update log components
|
||||
The Windows Update engine has different component names. The following are some of the most common components that appear in the WindowsUpdate.log file:
|
||||
|
||||
@ -11,4 +11,4 @@ ms.topic: include
|
||||
---
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The improved [Microsoft 365 security center](https://security.microsoft.com) is now available in public preview. This new experience brings Defender for Endpoint, Defender for Office, 365 Microsoft 365 Defender, and more into the Microsoft 365 security center. [Learn what's new](https://docs.microsoft.com/microsoft-365/security/mtp/overview-security-center). This topic might apply to both Microsoft Defender for Endpoint and Microsoft 365 Defender. Refer to the **Applies To** section and look for specific call outs in this article where there might be differences.
|
||||
> The improved [Microsoft 365 security center](https://security.microsoft.com) is now available in public preview. This new experience brings Defender for Endpoint, Defender for Office 365, Microsoft 365 Defender, and more into the Microsoft 365 security center. [Learn what's new](https://docs.microsoft.com/microsoft-365/security/mtp/overview-security-center). This topic might apply to both Microsoft Defender for Endpoint and Microsoft 365 Defender. Refer to the **Applies To** section and look for specific call outs in this article where there might be differences.
|
||||
|
||||
@ -13,7 +13,7 @@ ms.author: deniseb
|
||||
ms.custom: nextgen
|
||||
ms.reviewer: pahuijbr
|
||||
manager: dansimp
|
||||
ms.date: 02/04/2021
|
||||
ms.date: 02/12/2021
|
||||
ms.technology: mde
|
||||
---
|
||||
|
||||
@ -78,11 +78,11 @@ All our updates contain
|
||||
<br/><br/>
|
||||
|
||||
<details>
|
||||
<summary> January-2021 (Platform: 4.18.2101.8 | Engine: 1.1.17800.5)</summary>
|
||||
<summary> January-2021 (Platform: 4.18.2101.9 | Engine: 1.1.17800.5)</summary>
|
||||
|
||||
 Security intelligence update version: **1.327.1854.0**
|
||||
 Released: **February 2, 2021**
|
||||
 Platform: **4.18.2101.8**
|
||||
 Platform: **4.18.2101.9**
|
||||
 Engine: **1.1.17800.5**
|
||||
 Support phase: **Security and Critical Updates**
|
||||
|
||||
@ -93,6 +93,7 @@ All our updates contain
|
||||
- Increased visibility for credential stealing attempts
|
||||
- Improvements in antitampering features in Microsoft Defender Antivirus services
|
||||
- Improved support for ARM x64 emulation
|
||||
- Fix: EDR Block notification remains in threat history after real-time protection performed initial detection
|
||||
|
||||
### Known Issues
|
||||
No known issues
|
||||
@ -146,7 +147,7 @@ After a new package version is released, support for the previous two versions i
|
||||
 Released: **October 01, 2020**
|
||||
 Platform: **4.18.2009.7**
|
||||
 Engine: **1.1.17500.4**
|
||||
 Support phase: **Security and Critical Updates**
|
||||
 Support phase: **Technical upgrade support (only)**
|
||||
|
||||
### What's new
|
||||
|
||||
@ -172,7 +173,8 @@ No known issues
|
||||
 Released: **August 27, 2020**
|
||||
 Platform: **4.18.2008.9**
|
||||
 Engine: **1.1.17400.5**
|
||||
|
||||
 Support phase: **Technical upgrade support (only)**
|
||||
|
||||
### What's new
|
||||
|
||||
- Add more telemetry events
|
||||
|
||||
@ -57,7 +57,8 @@ To add device tags using API, see [Add or remove device tags API](add-or-remove-
|
||||
Tags are added to the device view and will also be reflected on the **Devices list** view. You can then use the **Tags** filter to see the relevant list of devices.
|
||||
|
||||
>[!NOTE]
|
||||
> Filtering might not work on tag names that contain parenthesis.
|
||||
> Filtering might not work on tag names that contain parenthesis.<br>
|
||||
> Filtering will only find portal set tags.
|
||||
|
||||
You can also delete tags from this view.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user