Merge branch 'master' into MandiOhlinger-GHI10004
@ -1,5 +1,10 @@
|
|||||||
{
|
{
|
||||||
"redirections": [
|
"redirections": [
|
||||||
|
{
|
||||||
|
"source_path": "windows/whats-new/windows-11.md",
|
||||||
|
"redirect_url": "/windows/whats-new/windows-11-whats-new",
|
||||||
|
"redirect_document_id": false
|
||||||
|
},
|
||||||
{
|
{
|
||||||
"source_path": "windows/configuration/use-json-customize-start-menu-windows.md",
|
"source_path": "windows/configuration/use-json-customize-start-menu-windows.md",
|
||||||
"redirect_url": "/windows/configuration/customize-start-menu-layout-windows-11",
|
"redirect_url": "/windows/configuration/customize-start-menu-layout-windows-11",
|
||||||
@ -18960,6 +18965,11 @@
|
|||||||
"redirect_url": "/windows/security/",
|
"redirect_url": "/windows/security/",
|
||||||
"redirect_document_id": false
|
"redirect_document_id": false
|
||||||
},
|
},
|
||||||
|
{
|
||||||
|
"source_path": "windows/deploy-windows-cm/upgrade-to-windows-with-configuraton-manager.md",
|
||||||
|
"redirect_url": "/windows/deploy-windows-cm/upgrade-to-windows-with-configuration-manager",
|
||||||
|
"redirect_document_id": false
|
||||||
|
},
|
||||||
{
|
{
|
||||||
"source_path": "windows/deployment/update/waas-deployment-rings-windows-10-updates.md",
|
"source_path": "windows/deployment/update/waas-deployment-rings-windows-10-updates.md",
|
||||||
"redirect_url": "/windows/deployment/update/waas-servicing-strategy-windows-10-updates",
|
"redirect_url": "/windows/deployment/update/waas-servicing-strategy-windows-10-updates",
|
||||||
@ -19015,6 +19025,11 @@
|
|||||||
"redirect_url": "/windows/deployment/waas-manage-updates-wufb",
|
"redirect_url": "/windows/deployment/waas-manage-updates-wufb",
|
||||||
"redirect_document_id": false
|
"redirect_document_id": false
|
||||||
},
|
},
|
||||||
|
{
|
||||||
|
"source_path": "windows/security/threat-protection/windows-security-baselines.md",
|
||||||
|
"redirect_url": "/windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines",
|
||||||
|
"redirect_document_id": false
|
||||||
|
},
|
||||||
{
|
{
|
||||||
"source_path": "windows/deployment/update/change-history-for-update-windows-10.md",
|
"source_path": "windows/deployment/update/change-history-for-update-windows-10.md",
|
||||||
"redirect_url": "/windows/deployment/deploy-whats-new",
|
"redirect_url": "/windows/deployment/deploy-whats-new",
|
||||||
|
@ -33,6 +33,7 @@ Organizations that use Windows Server Update Services (WSUS) must take action to
|
|||||||
|
|
||||||
1. Download the FOD .cab file:
|
1. Download the FOD .cab file:
|
||||||
|
|
||||||
|
- [Windows 11, version 21H2](https://software-download.microsoft.com/download/sg/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd_64~~.cab)
|
||||||
- [Windows 10, version 2004](https://software-download.microsoft.com/download/pr/6cf73b63/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab)
|
- [Windows 10, version 2004](https://software-download.microsoft.com/download/pr/6cf73b63/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab)
|
||||||
- [Windows 10, version 1903 and 1909](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package-31bf3856ad364e35-amd64.cab)
|
- [Windows 10, version 1903 and 1909](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package-31bf3856ad364e35-amd64.cab)
|
||||||
- [Windows 10, version 1809](https://software-download.microsoft.com/download/pr/microsoft-windows-holographic-desktop-fod-package31bf3856ad364e35amd64_1.cab)
|
- [Windows 10, version 1809](https://software-download.microsoft.com/download/pr/microsoft-windows-holographic-desktop-fod-package31bf3856ad364e35amd64_1.cab)
|
||||||
@ -49,7 +50,8 @@ Organizations that use Windows Server Update Services (WSUS) must take action to
|
|||||||
```
|
```
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> You must rename the FOD .CAB file to : **Microsoft-Windows-Holographic-Desktop-FOD-Package\~31bf3856ad364e35\~amd64\~\~.cab**
|
> * On Windows 10, you must rename the FOD .CAB file to : **Microsoft-Windows-Holographic-Desktop-FOD-Package\~31bf3856ad364e35\~amd64\~\~.cab**
|
||||||
|
> * On Windows 11, you must rename the FOD .CAB file to: **Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e45~amd_64~~.cab**
|
||||||
|
|
||||||
1. In **Settings** > **Update & Security** > **Windows Update**, select **Check for updates**.
|
1. In **Settings** > **Update & Security** > **Windows Update**, select **Check for updates**.
|
||||||
|
|
||||||
|
@ -13,8 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_DCOM
|
# Policy CSP - ADMX_DCOM
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -93,12 +98,6 @@ If you do not configure this policy setting, DCOM will only look in the locally
|
|||||||
> This policy setting applies to all sites in Trusted zones.
|
> This policy setting applies to all sites in Trusted zones.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -160,7 +159,7 @@ ADMX Info:
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
This policy setting allows you to view and change a list of DCOM server application IDs (appids), which are exempted from the DCOM Activation security check.
|
This policy setting allows you to view and change a list of DCOM server application IDs (app ids), which are exempted from the DCOM Activation security check.
|
||||||
DCOM uses two such lists, one configured via Group Policy through this policy setting, and the other via the actions of local computer administrators.
|
DCOM uses two such lists, one configured via Group Policy through this policy setting, and the other via the actions of local computer administrators.
|
||||||
DCOM ignores the second list when this policy setting is configured, unless the "Allow local activation security check exemptions" policy is enabled.
|
DCOM ignores the second list when this policy setting is configured, unless the "Allow local activation security check exemptions" policy is enabled.
|
||||||
DCOM server application IDs added to this policy must be listed in curly brace format.
|
DCOM server application IDs added to this policy must be listed in curly brace format.
|
||||||
@ -169,15 +168,15 @@ For example, `{b5dcb061-cefb-42e0-a1be-e6a6438133fe}`.
|
|||||||
If you enter a non-existent or improperly formatted application ID DCOM will add it to the list without checking for errors.
|
If you enter a non-existent or improperly formatted application ID DCOM will add it to the list without checking for errors.
|
||||||
- If you enable this policy setting, you can view and change the list of DCOM activation security check exemptions defined by Group Policy settings.
|
- If you enable this policy setting, you can view and change the list of DCOM activation security check exemptions defined by Group Policy settings.
|
||||||
|
|
||||||
If you add an application ID to this list and set its value to 1, DCOM will not enforce the Activation security check for that DCOM server.
|
If you add an application ID to this list and set its value to one, DCOM will not enforce the Activation security check for that DCOM server.
|
||||||
If you add an application ID to this list and set its value to 0 DCOM will always enforce the Activation security check for that DCOM server regardless of local
|
If you add an application ID to this list and set its value to zero DCOM will always enforce the Activation security check for that DCOM server regardless of local
|
||||||
settings.
|
settings.
|
||||||
- If you disable this policy setting, the application ID exemption list defined by Group Policy is deleted, and the one defined by local computer administrators is used.
|
- If you disable this policy setting, the application ID exemption list defined by Group Policy is deleted, and the one defined by local computer administrators is used.
|
||||||
|
|
||||||
If you do not configure this policy setting, the application ID exemption list defined by local computer administrators is used. Notes: The DCOM Activation security check is done after a DCOM server process is started, but before an object activation request is dispatched to the server process.
|
If you do not configure this policy setting, the application ID exemption list defined by local computer administrators is used. Notes: The DCOM Activation security check is done after a DCOM server process is started, but before an object activation request is dispatched to the server process.
|
||||||
This access check is done against the DCOM server's custom launch permission security descriptor if it exists, or otherwise against the configured defaults. If the DCOM server's custom launch permission contains explicit DENY entries this may mean that object activations that would have previously succeeded for such specified users, once the DCOM server process was up and running, might now fail instead.
|
This access check is done against the DCOM server's custom launch permission security descriptor if it exists, or otherwise against the configured defaults. If the DCOM server's custom launch permission contains explicit DENY entries this may mean that object activations that would have previously succeeded for such specified users, once the DCOM server process was up and running, might now fail instead.
|
||||||
|
|
||||||
The proper action in this situation is to reconfigure the DCOM server's custom launch permission settings for correct security settings, but this policy setting may be used in the short-term as an application compatibility deployment aid.
|
The proper action in this situation is to reconfigure the DCOM server's custom launch permission settings for correct security settings, but this policy setting may be used in the short term as an application compatibility deployment aid.
|
||||||
DCOM servers added to this exemption list are only exempted if their custom launch permissions do not contain specific LocalLaunch, RemoteLaunch, LocalActivate, or RemoteActivate grant or deny entries for any users or groups.
|
DCOM servers added to this exemption list are only exempted if their custom launch permissions do not contain specific LocalLaunch, RemoteLaunch, LocalActivate, or RemoteActivate grant or deny entries for any users or groups.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@ -187,12 +186,6 @@ DCOM servers added to this exemption list are only exempted if their custom laun
|
|||||||
> This policy setting applies to all sites in Trusted zones.
|
> This policy setting applies to all sites in Trusted zones.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -205,8 +198,5 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are currently only available as part of a Windows Insider release.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,8 +13,12 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_DeviceCompat
|
# Policy CSP - ADMX_DeviceCompat
|
||||||
> [!WARNING]
|
> [!TIP]
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -85,12 +89,6 @@ manager: dansimp
|
|||||||
Changes behavior of Microsoft bus drivers to work with specific devices.
|
Changes behavior of Microsoft bus drivers to work with specific devices.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -155,12 +153,6 @@ ADMX Info:
|
|||||||
Changes behavior of third-party drivers to work around incompatibilities introduced between OS versions.
|
Changes behavior of third-party drivers to work around incompatibilities introduced between OS versions.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
|
@ -13,8 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_DeviceGuard
|
# Policy CSP - ADMX_DeviceGuard
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -95,12 +100,6 @@ If using a signed and protected policy then disabling this policy setting doesn'
|
|||||||
2. Disable the setting and then remove the policy from each computer, with a physically present user.
|
2. Disable the setting and then remove the policy from each computer, with a physically present user.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -112,8 +111,6 @@ ADMX Info:
|
|||||||
<!--/ADMXBacked-->
|
<!--/ADMXBacked-->
|
||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are currently only available as part of a Windows Insider release.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,10 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_DFS
|
# Policy CSP - ADMX_DFS
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
|
||||||
|
|
||||||
|
|
||||||
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
<!--Policies-->
|
<!--Policies-->
|
||||||
@ -93,12 +96,6 @@ This value is specified in minutes.
|
|||||||
> The minimum value you can select is 15 minutes. If you try to set this setting to a value less than 15 minutes, the default value of 15 minutes is applied.
|
> The minimum value you can select is 15 minutes. If you try to set this setting to a value less than 15 minutes, the default value of 15 minutes is applied.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -111,8 +108,6 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are currently only available as part of a Windows Insider release.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,8 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_DiskDiagnostic
|
# Policy CSP - ADMX_DiskDiagnostic
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -96,12 +101,6 @@ The DPS can be configured with the Services snap-in to the Microsoft Management
|
|||||||
> For Windows Server systems, this policy setting applies only if the Desktop Experience optional component is installed and the Remote Desktop Services.
|
> For Windows Server systems, this policy setting applies only if the Desktop Experience optional component is installed and the Remote Desktop Services.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -179,12 +178,6 @@ This policy setting takes effect only when the DPS is in the running state. When
|
|||||||
> For Windows Server systems, this policy setting applies only if the Desktop Experience optional component is installed and the Remote Desktop Services role is not installed.
|
> For Windows Server systems, this policy setting applies only if the Desktop Experience optional component is installed and the Remote Desktop Services role is not installed.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -197,8 +190,6 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are for upcoming release.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,8 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_EventLogging
|
# Policy CSP - ADMX_EventLogging
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -89,12 +94,6 @@ You can use the Unprotect-CmsMessage PowerShell cmdlet to decrypt these encrypte
|
|||||||
- If you disable or do not configure this policy setting, components will not encrypt event log messages before writing them to the event log.
|
- If you disable or do not configure this policy setting, components will not encrypt event log messages before writing them to the event log.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -107,8 +106,6 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are currently only available as part of a Windows Insider release.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,8 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_EventViewer
|
# Policy CSP - ADMX_EventViewer
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -89,12 +94,7 @@ manager: dansimp
|
|||||||
This is the program that will be invoked when the user clicks the `events.asp` link.
|
This is the program that will be invoked when the user clicks the `events.asp` link.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -160,12 +160,6 @@ ADMX Info:
|
|||||||
This specifies the command line parameters that will be passed to the `events.asp` program.
|
This specifies the command line parameters that will be passed to the `events.asp` program.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -233,12 +227,6 @@ Change this value if you want to use a different Web server to handle event info
|
|||||||
|
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
|
@ -14,8 +14,12 @@ manager: dansimp
|
|||||||
|
|
||||||
# Policy CSP - ADMX_ExternalBoot
|
# Policy CSP - ADMX_ExternalBoot
|
||||||
|
|
||||||
> [!WARNING]
|
> [!TIP]
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -98,12 +102,6 @@ This policy specifies whether the PC can use the hibernation sleep state (S4) wh
|
|||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
|
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -174,13 +172,6 @@ If you disable or do not configure this setting, Windows, when started from a Wi
|
|||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
|
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
- GP Friendly name: *Disallow standby sleep states (S1-S3) when starting from a Windows to Go workspace*
|
- GP Friendly name: *Disallow standby sleep states (S1-S3) when starting from a Windows to Go workspace*
|
||||||
@ -253,13 +244,6 @@ If you do not configure this setting, users who are members of the Administrator
|
|||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
|
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
- GP Friendly name: *Windows To Go Default Startup Options*
|
- GP Friendly name: *Windows To Go Default Startup Options*
|
||||||
|
@ -13,8 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_FileRevocation
|
# Policy CSP - ADMX_FileRevocation
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -90,12 +95,6 @@ Any other Windows Runtime application will only be able to revoke access to cont
|
|||||||
> Information the user should notice even if skimmingFile revocation applies to all content protected under the same second level domain as the provided enterprise identifier. Therefore, revoking an enterprise ID of `mail.contoso.com` will revoke the user’s access to all content protected under the contoso.com hierarchy.
|
> Information the user should notice even if skimmingFile revocation applies to all content protected under the same second level domain as the provided enterprise identifier. Therefore, revoking an enterprise ID of `mail.contoso.com` will revoke the user’s access to all content protected under the contoso.com hierarchy.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -108,8 +107,6 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are currently only available as part of a Windows Insider release.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,9 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_FramePanes
|
# Policy CSP - ADMX_FramePanes
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
|
||||||
|
|
||||||
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
<!--Policies-->
|
<!--Policies-->
|
||||||
@ -95,12 +99,6 @@ This policy setting shows or hides the Details Pane in File Explorer.
|
|||||||
This is the default policy setting.
|
This is the default policy setting.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -169,12 +167,6 @@ Hides the Preview Pane in File Explorer.
|
|||||||
- If you disable, or do not configure this setting, the Preview Pane is hidden by default and can be displayed by the user.
|
- If you disable, or do not configure this setting, the Preview Pane is hidden by default and can be displayed by the user.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -186,8 +178,5 @@ ADMX Info:
|
|||||||
<!--/ADMXBacked-->
|
<!--/ADMXBacked-->
|
||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are currently only available as part of a Windows Insider release.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,8 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_FTHSVC
|
# Policy CSP - ADMX_FTHSVC
|
||||||
> [!WARNING]
|
|
||||||
> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -91,12 +96,6 @@ The DPS can be configured with the Services snap-in to the Microsoft Management
|
|||||||
No system restart or service restart is required for this policy setting to take effect: changes take effect immediately.
|
No system restart or service restart is required for this policy setting to take effect: changes take effect immediately.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -110,7 +109,5 @@ ADMX Info:
|
|||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> These policies are currently only available as part of a Windows Insider release.
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -13,8 +13,9 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_HotSpotAuth
|
# Policy CSP - ADMX_HotSpotAuth
|
||||||
>[!TIP]
|
|
||||||
> These are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
>
|
>
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
>
|
>
|
||||||
@ -95,7 +96,6 @@ This policy setting defines whether WLAN hotspots are probed for Wireless Intern
|
|||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
- GP Friendly name: *Enable Hotspot Authentication*
|
- GP Friendly name: *Enable Hotspot Authentication*
|
||||||
|
@ -13,8 +13,9 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_IIS
|
# Policy CSP - ADMX_IIS
|
||||||
>[!TIP]
|
|
||||||
> These are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
>
|
>
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
>
|
>
|
||||||
|
@ -13,13 +13,13 @@ manager: dansimp
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - ADMX_LeakDiagnostic
|
# Policy CSP - ADMX_LeakDiagnostic
|
||||||
>[!TIP]
|
|
||||||
> These are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
>
|
>
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
>
|
>
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
<!--Policies-->
|
<!--Policies-->
|
||||||
@ -116,6 +116,5 @@ ADMX Info:
|
|||||||
<!--Policies-->
|
<!--Policies-->
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -51,28 +51,34 @@ manager: dansimp
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -89,7 +95,7 @@ manager: dansimp
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1703. Specifies the authentication endpoint for acquiring OAuth tokens. This policy must target ./User, otherwise it fails.
|
Specifies the authentication endpoint for acquiring OAuth tokens. This policy must target ./User, otherwise it fails.
|
||||||
|
|
||||||
The datatype is a string.
|
The datatype is a string.
|
||||||
|
|
||||||
@ -106,28 +112,34 @@ The default value is an empty string. Otherwise, the value should contain the UR
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -144,7 +156,7 @@ The default value is an empty string. Otherwise, the value should contain the UR
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1703. Specifies the GUID of a client application authorized to retrieve OAuth tokens from the OAuthAuthority. This policy must target ./User, otherwise it fails.
|
Specifies the GUID of a client application authorized to retrieve OAuth tokens from the OAuthAuthority. This policy must target ./User, otherwise it fails.
|
||||||
|
|
||||||
The datatype is a string.
|
The datatype is a string.
|
||||||
|
|
||||||
@ -161,28 +173,34 @@ The default value is an empty string. Otherwise, the value should contain a GUID
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -199,7 +217,7 @@ The default value is an empty string. Otherwise, the value should contain a GUID
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1703. Specifies the per-user resource URL for which access is requested by the enterprise cloud print client during OAuth authentication. This policy must target ./User, otherwise it fails.
|
Specifies the per-user resource URL for which access is requested by the enterprise cloud print client during OAuth authentication. This policy must target ./User, otherwise it fails.
|
||||||
|
|
||||||
The datatype is a string.
|
The datatype is a string.
|
||||||
|
|
||||||
@ -216,28 +234,34 @@ The default value is an empty string. Otherwise, the value should contain a URL.
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -254,7 +278,7 @@ The default value is an empty string. Otherwise, the value should contain a URL.
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1703. Specifies the per-user end point for discovering cloud printers. This policy must target ./User, otherwise it fails.
|
Specifies the per-user end point for discovering cloud printers. This policy must target ./User, otherwise it fails.
|
||||||
|
|
||||||
The datatype is a string.
|
The datatype is a string.
|
||||||
|
|
||||||
@ -271,28 +295,34 @@ The default value is an empty string. Otherwise, the value should contain the UR
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -309,7 +339,7 @@ The default value is an empty string. Otherwise, the value should contain the UR
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1703. Defines the maximum number of printers that should be queried from a discovery end point. This policy must target ./User, otherwise it fails.
|
Defines the maximum number of printers that should be queried from a discovery end point. This policy must target ./User, otherwise it fails.
|
||||||
|
|
||||||
The datatype is an integer.
|
The datatype is an integer.
|
||||||
|
|
||||||
@ -324,28 +354,34 @@ The datatype is an integer.
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>2</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -362,7 +398,7 @@ The datatype is an integer.
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1703. Specifies the per-user resource URL for which access is requested by the Mopria discovery client during OAuth authentication. This policy must target ./User, otherwise it fails.
|
Specifies the per-user resource URL for which access is requested by the Mopria discovery client during OAuth authentication. This policy must target ./User, otherwise it fails.
|
||||||
|
|
||||||
The datatype is a string.
|
The datatype is a string.
|
||||||
|
|
||||||
@ -372,16 +408,6 @@ The default value is an empty string. Otherwise, the value should contain a URL.
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -14,7 +14,12 @@ manager: dansimp
|
|||||||
|
|
||||||
# Policy CSP - ErrorReporting
|
# Policy CSP - ErrorReporting
|
||||||
|
|
||||||
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
@ -48,28 +53,34 @@ manager: dansimp
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -103,12 +114,6 @@ If you enable this policy setting, you can add specific event types to a list by
|
|||||||
If you disable or do not configure this policy setting, then the default consent settings that are applied are those specified by the user in Control Panel, or in the Configure Default Consent policy setting.
|
If you disable or do not configure this policy setting, then the default consent settings that are applied are those specified by the user in Control Panel, or in the Configure Default Consent policy setting.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -128,28 +133,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -173,12 +184,6 @@ If you enable this policy setting, Windows Error Reporting does not send any pro
|
|||||||
If you disable or do not configure this policy setting, the Turn off Windows Error Reporting policy setting in Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings takes precedence. If Turn off Windows Error Reporting is also either disabled or not configured, user settings in Control Panel for Windows Error Reporting are applied.
|
If you disable or do not configure this policy setting, the Turn off Windows Error Reporting policy setting in Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings takes precedence. If Turn off Windows Error Reporting is also either disabled or not configured, user settings in Control Panel for Windows Error Reporting are applied.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -198,28 +203,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -247,12 +258,6 @@ If you do not configure this policy setting, users can change this setting in Co
|
|||||||
See also the Configure Error Reporting policy setting.
|
See also the Configure Error Reporting policy setting.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -272,28 +277,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -317,12 +328,6 @@ If you enable this policy setting, any additional data requests from Microsoft i
|
|||||||
If you disable or do not configure this policy setting, then consent policy settings in Computer Configuration/Administrative Templates/Windows Components/Windows Error Reporting/Consent take precedence.
|
If you disable or do not configure this policy setting, then consent policy settings in Computer Configuration/Administrative Templates/Windows Components/Windows Error Reporting/Consent take precedence.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -342,28 +347,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -387,12 +398,6 @@ If you enable this policy setting, Windows Error Reporting does not display any
|
|||||||
If you disable or do not configure this policy setting, Windows Error Reporting displays the user interface for critical errors.
|
If you disable or do not configure this policy setting, Windows Error Reporting displays the user interface for critical errors.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -405,16 +410,6 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -45,28 +45,34 @@ manager: dansimp
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -92,12 +98,6 @@ If you disable or do not configure this policy setting and a log file reaches it
|
|||||||
Note: Old events may or may not be retained according to the "Backup log automatically when full" policy setting.
|
Note: Old events may or may not be retained according to the "Backup log automatically when full" policy setting.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -117,28 +117,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -162,12 +168,6 @@ If you enable this policy setting, you can configure the maximum log file size t
|
|||||||
If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog and it defaults to 20 megabytes.
|
If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog and it defaults to 20 megabytes.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -187,28 +187,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -232,12 +238,6 @@ If you enable this policy setting, you can configure the maximum log file size t
|
|||||||
If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog and it defaults to 20 megabytes.
|
If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog and it defaults to 20 megabytes.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -257,28 +257,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -302,12 +308,6 @@ If you enable this policy setting, you can configure the maximum log file size t
|
|||||||
If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog and it defaults to 20 megabytes.
|
If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog and it defaults to 20 megabytes.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -320,16 +320,6 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -373,7 +373,7 @@ The following list shows the supported values:
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1703. This policy turns on Find My Device.
|
This policy turns on Find My Device.
|
||||||
|
|
||||||
When Find My Device is on, the device and its location are registered in the cloud so that the device can be located when the user initiates a Find command from account.microsoft.com. In Windows 10, version 1709 devices that are compatible with active digitizers, enabling Find My Device will also allow the user to view the last location of use of their active digitizer on their device; this location is stored locally on the user's device after each use of their active digitizer.
|
When Find My Device is on, the device and its location are registered in the cloud so that the device can be located when the user initiates a Find command from account.microsoft.com. In Windows 10, version 1709 devices that are compatible with active digitizers, enabling Find My Device will also allow the user to view the last location of use of their active digitizer on their device; this location is stored locally on the user's device after each use of their active digitizer.
|
||||||
|
|
||||||
@ -610,7 +610,7 @@ The following list shows the supported values:
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> This policy is only enforced in Windows 10 for desktop and not supported in Windows 10 Mobile.
|
> This policy is only enforced in Windows 10 for desktop and not supported in Windows 10 Mobile.
|
||||||
|
|
||||||
Added in Windows 10, version 1703. This policy allows you to prevent Windows from using diagnostic data to provide customized experiences to the user. If you enable this policy setting, Windows will not use diagnostic data from this device to customize content shown on the lock screen, Windows tips, Microsoft consumer features, or other related features. If these features are enabled, users will still see recommendations, tips and offers, but they may be less relevant. If you disable or do not configure this policy setting, Microsoft will use diagnostic data to provide personalized recommendations, tips, and offers to tailor Windows for the user's needs and make it work better for them.
|
This policy allows you to prevent Windows from using diagnostic data to provide customized experiences to the user. If you enable this policy setting, Windows will not use diagnostic data from this device to customize content shown on the lock screen, Windows tips, Microsoft consumer features, or other related features. If these features are enabled, users will still see recommendations, tips and offers, but they may be less relevant. If you disable or do not configure this policy setting, Microsoft will use diagnostic data to provide personalized recommendations, tips, and offers to tailor Windows for the user's needs and make it work better for them.
|
||||||
|
|
||||||
Diagnostic data can include browser, app and feature usage, depending on the "Diagnostic and usage data" setting value.
|
Diagnostic data can include browser, app and feature usage, depending on the "Diagnostic and usage data" setting value.
|
||||||
|
|
||||||
@ -925,7 +925,7 @@ The following list shows the supported values:
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> This policy is only enforced in Windows 10 for desktop and not supported in Windows 10 Mobile.
|
> This policy is only enforced in Windows 10 for desktop and not supported in Windows 10 Mobile.
|
||||||
|
|
||||||
Added in Windows 10, version 1703. This policy allows administrators to prevent Windows spotlight notifications from being displayed in the Action Center. If you enable this policy, Windows spotlight notifications will no longer be displayed in the Action Center. If you disable or do not configure this policy, Microsoft may display notifications in the Action Center that will suggest apps or features to help users be more productive on Windows.
|
This policy allows administrators to prevent Windows spotlight notifications from being displayed in the Action Center. If you enable this policy, Windows spotlight notifications will no longer be displayed in the Action Center. If you disable or do not configure this policy, Microsoft may display notifications in the Action Center that will suggest apps or features to help users be more productive on Windows.
|
||||||
|
|
||||||
Most restricted value is 0.
|
Most restricted value is 0.
|
||||||
|
|
||||||
@ -999,7 +999,7 @@ The following list shows the supported values:
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1803. This policy allows IT admins to turn off Suggestions in Settings app. These suggestions from Microsoft may show after each OS clean install, upgrade or an on-going basis to help users discover apps/features on Windows or across devices, to make their experience productive.
|
This policy allows IT admins to turn off Suggestions in Settings app. These suggestions from Microsoft may show after each OS clean install, upgrade or an on-going basis to help users discover apps/features on Windows or across devices, to make their experience productive.
|
||||||
|
|
||||||
- User setting is under Settings -> Privacy -> General -> Show me suggested content in Settings app.
|
- User setting is under Settings -> Privacy -> General -> Show me suggested content in Settings app.
|
||||||
- User Setting is changeable on a per user basis.
|
- User Setting is changeable on a per user basis.
|
||||||
@ -1078,7 +1078,7 @@ The following list shows the supported values:
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> This policy is only enforced in Windows 10 for desktop and not supported in Windows 10 Mobile.
|
> This policy is only enforced in Windows 10 for desktop and not supported in Windows 10 Mobile.
|
||||||
|
|
||||||
Added in Windows 10, version 1703. This policy setting lets you turn off the Windows spotlight Windows welcome experience feature.
|
This policy setting lets you turn off the Windows spotlight Windows welcome experience feature.
|
||||||
The Windows welcome experience feature introduces onboard users to Windows; for example, launching Microsoft Edge with a webpage that highlights new features. If you enable this policy, the Windows welcome experience will no longer be displayed when there are updates and changes to Windows and its apps. If you disable or do not configure this policy, the Windows welcome experience will be launched to inform onboard users about what's new, changed, and suggested.
|
The Windows welcome experience feature introduces onboard users to Windows; for example, launching Microsoft Edge with a webpage that highlights new features. If you enable this policy, the Windows welcome experience will no longer be displayed when there are updates and changes to Windows and its apps. If you disable or do not configure this policy, the Windows welcome experience will be launched to inform onboard users about what's new, changed, and suggested.
|
||||||
|
|
||||||
Most restricted value is 0.
|
Most restricted value is 0.
|
||||||
@ -1747,16 +1747,5 @@ Supported values:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
- 9 - Available in Windows 10, version 20H2.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
@ -36,28 +36,34 @@ manager: dansimp
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -118,15 +124,5 @@ Here is an example:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
@ -14,6 +14,12 @@ manager: dansimp
|
|||||||
|
|
||||||
# Policy CSP - FileExplorer
|
# Policy CSP - FileExplorer
|
||||||
|
|
||||||
|
> [!TIP]
|
||||||
|
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
||||||
|
>
|
||||||
|
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
||||||
|
>
|
||||||
|
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||||
|
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
@ -39,28 +45,34 @@ manager: dansimp
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -80,12 +92,6 @@ manager: dansimp
|
|||||||
Disabling data execution prevention can allow certain legacy plug-in applications to function without terminating Explorer.
|
Disabling data execution prevention can allow certain legacy plug-in applications to function without terminating Explorer.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
@ -105,28 +111,34 @@ ADMX Info:
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -145,14 +157,6 @@ ADMX Info:
|
|||||||
<!--Description-->
|
<!--Description-->
|
||||||
Disabling heap termination on corruption can allow certain legacy plug-in applications to function without terminating Explorer immediately, although Explorer may still terminate unexpectedly later.
|
Disabling heap termination on corruption can allow certain legacy plug-in applications to function without terminating Explorer immediately, although Explorer may still terminate unexpectedly later.
|
||||||
|
|
||||||
<!--/Description-->
|
|
||||||
> [!TIP]
|
|
||||||
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
|
|
||||||
>
|
|
||||||
> You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
|
|
||||||
>
|
|
||||||
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
|
||||||
|
|
||||||
<!--ADMXBacked-->
|
<!--ADMXBacked-->
|
||||||
ADMX Info:
|
ADMX Info:
|
||||||
- GP Friendly name: *Turn off heap termination on corruption*
|
- GP Friendly name: *Turn off heap termination on corruption*
|
||||||
@ -164,16 +168,5 @@ ADMX Info:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -36,28 +36,34 @@ manager: dansimp
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -87,16 +93,6 @@ The following list shows the supported values:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -36,28 +36,34 @@ manager: dansimp
|
|||||||
<!--SupportedSKUs-->
|
<!--SupportedSKUs-->
|
||||||
<table>
|
<table>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Windows Edition</th>
|
<th>Edition</th>
|
||||||
<th>Supported?</th>
|
<th>Windows 10</th>
|
||||||
|
<th>Windows 11</th>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Home</td>
|
<td>Home</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Pro</td>
|
<td>Pro</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3<sup></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Business</td>
|
<td>Business</td>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td>No</td>
|
||||||
|
<td>No</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Enterprise</td>
|
<td>Enterprise</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3<sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>Education</td>
|
<td>Education</td>
|
||||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3<sup></td>
|
<td>Yes</td>
|
||||||
|
<td>Yes</td>
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
@ -74,7 +80,7 @@ manager: dansimp
|
|||||||
|
|
||||||
<!--/Scope-->
|
<!--/Scope-->
|
||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10. version 1709. This policy allows an enterprise to configure the default mode for the handwriting panel.
|
This policy allows an enterprise to configure the default mode for the handwriting panel.
|
||||||
|
|
||||||
The handwriting panel has 2 modes - floats near the text box, or docked to the bottom of the screen. The default configuration to is floating near text box. If you want the panel to be fixed or docked, use this policy to fix it to the bottom of the screen.
|
The handwriting panel has 2 modes - floats near the text box, or docked to the bottom of the screen. The default configuration to is floating near text box. If you want the panel to be fixed or docked, use this policy to fix it to the bottom of the screen.
|
||||||
|
|
||||||
@ -101,16 +107,5 @@ The following list shows the supported values:
|
|||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnotes:
|
|
||||||
|
|
||||||
- 1 - Available in Windows 10, version 1607.
|
|
||||||
- 2 - Available in Windows 10, version 1703.
|
|
||||||
- 3 - Available in Windows 10, version 1709.
|
|
||||||
- 4 - Available in Windows 10, version 1803.
|
|
||||||
- 5 - Available in Windows 10, version 1809.
|
|
||||||
- 6 - Available in Windows 10, version 1903.
|
|
||||||
- 7 - Available in Windows 10, version 1909.
|
|
||||||
- 8 - Available in Windows 10, version 2004.
|
|
||||||
|
|
||||||
<!--/Policies-->
|
<!--/Policies-->
|
||||||
|
|
||||||
|
@ -116,7 +116,7 @@
|
|||||||
- name: Replace a device
|
- name: Replace a device
|
||||||
href: deploy-windows-cm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md
|
href: deploy-windows-cm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md
|
||||||
- name: In-place upgrade
|
- name: In-place upgrade
|
||||||
href: deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md
|
href: deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md
|
||||||
- name: Deploy Windows client with MDT
|
- name: Deploy Windows client with MDT
|
||||||
items:
|
items:
|
||||||
- name: Deploy to a new device
|
- name: Deploy to a new device
|
||||||
|
@ -25,4 +25,4 @@
|
|||||||
- name: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
- name: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||||
href: replace-a-windows-7-client-with-windows-10-using-configuration-manager.md
|
href: replace-a-windows-7-client-with-windows-10-using-configuration-manager.md
|
||||||
- name: Perform an in-place upgrade to Windows 10 using Configuration Manager
|
- name: Perform an in-place upgrade to Windows 10 using Configuration Manager
|
||||||
href: upgrade-to-windows-10-with-configuraton-manager.md
|
href: upgrade-to-windows-10-with-configuration-manager.md
|
||||||
|
@ -201,7 +201,7 @@ When the process is complete, you will have a new Windows 10 computer in your do
|
|||||||
<br>
|
<br>
|
||||||

|

|
||||||
|
|
||||||
Next, see [Perform an in-place upgrade to Windows 10 using Configuration Manager](upgrade-to-windows-10-with-configuraton-manager.md).
|
Next, see [Perform an in-place upgrade to Windows 10 using Configuration Manager](upgrade-to-windows-10-with-configuration-manager.md).
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
@ -135,8 +135,6 @@ On **PC0004**:
|
|||||||
<br>
|
<br>
|
||||||

|

|
||||||
|
|
||||||
In-place upgrade with Configuration Manager
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Windows 10 deployment scenarios](../windows-10-deployment-scenarios.md)<br>
|
[Windows 10 deployment scenarios](../windows-10-deployment-scenarios.md)<br>
|
@ -30,6 +30,6 @@ Windows 10 provides new deployment capabilities, scenarios, and tools by buildi
|
|||||||
- [Deploy Windows 10 with MDT](../deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md)
|
- [Deploy Windows 10 with MDT](../deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md)
|
||||||
- [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
- [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||||
- [Upgrade to Windows 10 with MDT](../deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
|
- [Upgrade to Windows 10 with MDT](../deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||||
- [Upgrade to Windows 10 with Configuration Manager](../deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md)
|
- [Upgrade to Windows 10 with Configuration Manager](../deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md)
|
||||||
- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd)
|
- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd)
|
||||||
|
|
@ -79,7 +79,7 @@ sections:
|
|||||||
- question: |
|
- question: |
|
||||||
Can I upgrade computers from Windows 7 or Windows 8.1 without deploying a new image?
|
Can I upgrade computers from Windows 7 or Windows 8.1 without deploying a new image?
|
||||||
answer: |
|
answer: |
|
||||||
Computers running Windows 7 or Windows 8.1 can be upgraded directly to Windows 10 through the in-place upgrade process without a need to reimage the device using MDT and/or Configuration Manager. For more information, see [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](../deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md) or [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md).
|
Computers running Windows 7 or Windows 8.1 can be upgraded directly to Windows 10 through the in-place upgrade process without a need to reimage the device using MDT and/or Configuration Manager. For more information, see [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](../deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md) or [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||||
|
|
||||||
- question: |
|
- question: |
|
||||||
Can I upgrade from Windows 7 Enterprise or Windows 8.1 Enterprise to Windows 10 Enterprise for free?
|
Can I upgrade from Windows 7 Enterprise or Windows 8.1 Enterprise to Windows 10 Enterprise for free?
|
||||||
|
@ -17,10 +17,15 @@ ms.topic: article
|
|||||||
|
|
||||||
# Manually Configuring Devices for Update Compliance
|
# Manually Configuring Devices for Update Compliance
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> As of May 10, 2021, a new policy is required to use Update Compliance: "Allow Update Compliance Processing." For more details, see the Mobile Device Management policies and Group policies tables.
|
> As of May 10, 2021, a new policy is required to use Update Compliance: "Allow Update Compliance Processing." For more details, see the Mobile Device Management policies and Group policies tables.
|
||||||
|
|
||||||
There are a number of requirements to consider when manually configuring devices for Update Compliance. These can potentially change with newer versions of Windows 10. The [Update Compliance Configuration Script](update-compliance-configuration-script.md) will be updated when any configuration requirements change so only a redeployment of the script will be required.
|
There are a number of requirements to consider when manually configuring devices for Update Compliance. These can potentially change with newer versions of Windows client. The [Update Compliance Configuration Script](update-compliance-configuration-script.md) will be updated when any configuration requirements change so only a redeployment of the script will be required.
|
||||||
|
|
||||||
The requirements are separated into different categories:
|
The requirements are separated into different categories:
|
||||||
|
|
||||||
|
@ -16,6 +16,7 @@ ms.topic: article
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Configuring Microsoft Endpoint Manager devices for Update Compliance
|
# Configuring Microsoft Endpoint Manager devices for Update Compliance
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
@ -17,6 +17,11 @@ ms.topic: article
|
|||||||
|
|
||||||
# Configuring devices through the Update Compliance Configuration Script
|
# Configuring devices through the Update Compliance Configuration Script
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> A new policy is required to use Update Compliance: "AllowUpdateComplianceProcessing." If you're already using Update Compliance and have configured your devices prior to May 10, 2021, you must rerun the script so the new policy can be configured.
|
> A new policy is required to use Update Compliance: "AllowUpdateComplianceProcessing." If you're already using Update Compliance and have configured your devices prior to May 10, 2021, you must rerun the script so the new policy can be configured.
|
||||||
|
|
||||||
|
@ -1,5 +1,5 @@
|
|||||||
---
|
---
|
||||||
title: Delivery Optimization in Update Compliance (Windows 10)
|
title: Delivery Optimization in Update Compliance
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
description: Learn how the Update Compliance solution provides you with information about your Delivery Optimization configuration.
|
description: Learn how the Update Compliance solution provides you with information about your Delivery Optimization configuration.
|
||||||
@ -17,6 +17,12 @@ ms.custom: seo-marvel-apr2020
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Delivery Optimization in Update Compliance
|
# Delivery Optimization in Update Compliance
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||

|

|
||||||
The Update Compliance solution provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
|
The Update Compliance solution provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
|
||||||
|
|
||||||
@ -30,7 +36,7 @@ The Delivery Optimization Status section includes three blades:
|
|||||||
|
|
||||||
|
|
||||||
## Device Configuration blade
|
## Device Configuration blade
|
||||||
Devices can be set to use different download modes; these download modes determine in what situations Delivery Optimization will use peer-to-peer distribution to accomplish the downloads. The top section shows the number of devices configured to use peer-to-peer distribution in *Peering On* compared to *Peering Off* modes. The table shows a breakdown of the various download mode configurations seen in your environment. For more information about the different configuration options, see [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization-setup.md).
|
Devices can be set to use different download modes; these download modes determine in what situations Delivery Optimization will use peer-to-peer distribution to accomplish the downloads. The top section shows the number of devices configured to use peer-to-peer distribution in *Peering On* compared to *Peering Off* modes. The table shows a breakdown of the various download mode configurations seen in your environment. For more information about the different configuration options, see [Configure Delivery Optimization for Windows client updates](waas-delivery-optimization-setup.md).
|
||||||
|
|
||||||
## Content Distribution (%) blade
|
## Content Distribution (%) blade
|
||||||
The first of two blades showing information on content breakdown, this blade shows a ring chart summarizing **Bandwidth Savings %**, which is the percentage of data received from peer sources out of the total data downloaded (for any device that used peer-to-peer distribution).
|
The first of two blades showing information on content breakdown, this blade shows a ring chart summarizing **Bandwidth Savings %**, which is the percentage of data received from peer sources out of the total data downloaded (for any device that used peer-to-peer distribution).
|
||||||
|
@ -17,6 +17,11 @@ ms.custom: seo-marvel-apr2020
|
|||||||
|
|
||||||
# Feature Update Status
|
# Feature Update Status
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
[  ](images/UC_workspace_FU_status.png#lightbox)
|
[  ](images/UC_workspace_FU_status.png#lightbox)
|
||||||
|
|
||||||
The Feature Update Status section provides information about the status of [feature updates](waas-quick-start.md#definitions) across all devices. This section tile in the [Overview Blade](update-compliance-using.md#overview-blade) gives a percentage of devices that are on the latest applicable feature update; [Servicing Channel](waas-overview.md#servicing-channels) is considered in determining applicability. Within this section are two blades; one providing a holistic view of feature updates, the other containing three **Deployment Status** tiles, each charged with tracking the deployment for a different [Servicing Channel](waas-overview.md#servicing-channels).
|
The Feature Update Status section provides information about the status of [feature updates](waas-quick-start.md#definitions) across all devices. This section tile in the [Overview Blade](update-compliance-using.md#overview-blade) gives a percentage of devices that are on the latest applicable feature update; [Servicing Channel](waas-overview.md#servicing-channels) is considered in determining applicability. Within this section are two blades; one providing a holistic view of feature updates, the other containing three **Deployment Status** tiles, each charged with tracking the deployment for a different [Servicing Channel](waas-overview.md#servicing-channels).
|
||||||
@ -38,7 +43,7 @@ Refer to the following list for what each state means:
|
|||||||
|
|
||||||
## Safeguard holds
|
## Safeguard holds
|
||||||
|
|
||||||
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *safeguard hold* is generated to delay the device's upgrade and protect the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all safeguard holds on the Windows 10 release information page for any given release.
|
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *safeguard hold* is generated to delay the device's upgrade and protect the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all safeguard holds on the Windows client release information pages for any given release.
|
||||||
|
|
||||||
## Queries for safeguard holds
|
## Queries for safeguard holds
|
||||||
|
|
||||||
|
@ -17,6 +17,11 @@ ms.topic: article
|
|||||||
|
|
||||||
# Get started with Update Compliance
|
# Get started with Update Compliance
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
> **A new policy is required to use Update Compliance: "AllowUpdateComplianceProcessing"**. If you're already using Update Compliance and have configured your devices prior to May 10, 2021, you must configure devices with this additional policy. You can do this by rerunning the [Update Compliance Configuration Script](update-compliance-configuration-script.md) if you configure your devices through Group Policy, or refer to [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md) for details on manually configuring the new policy for both Group Policy and MDM.
|
> **A new policy is required to use Update Compliance: "AllowUpdateComplianceProcessing"**. If you're already using Update Compliance and have configured your devices prior to May 10, 2021, you must configure devices with this additional policy. You can do this by rerunning the [Update Compliance Configuration Script](update-compliance-configuration-script.md) if you configure your devices through Group Policy, or refer to [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md) for details on manually configuring the new policy for both Group Policy and MDM.
|
||||||
|
|
||||||
@ -35,11 +40,11 @@ After adding the solution to Azure and configuring devices, it can take some tim
|
|||||||
|
|
||||||
Before you begin the process to add Update Compliance to your Azure subscription, first ensure you can meet the prerequisites:
|
Before you begin the process to add Update Compliance to your Azure subscription, first ensure you can meet the prerequisites:
|
||||||
|
|
||||||
- **Compatible Operating Systems and Editions**: Update Compliance works only with Windows 10 Professional, Education, and Enterprise editions. Update Compliance supports both the typical Windows 10 Enterprise edition, as well as [Windows 10 Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq). Update Compliance only provides data for the standard Desktop Windows 10 version and is not currently compatible with Windows Server, Surface Hub, IoT, etc.
|
- **Compatible operating systems and editions**: Update Compliance works only with Windows 10 or Windows 11 Professional, Education, and Enterprise editions. Update Compliance supports both the typical Windows 10 or Windows 11 Enterprise edition, as well as [Windows 10 Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq). Update Compliance only provides data for the standard Desktop Windows client version and is not currently compatible with Windows Server, Surface Hub, IoT, or other versions.
|
||||||
- **Compatible Windows 10 Servicing Channels**: Update Compliance supports Windows 10 devices on the Semi-Annual Channel and the Long-term Servicing Channel (LTSC). Update Compliance *counts* Windows Insider Preview (WIP) devices, but does not currently provide detailed deployment insights for them.
|
- **Compatible Windows client servicing channels**: Update Compliance supports Windows client devices on the General Availability Channel and the Long-term Servicing Channel (LTSC). Update Compliance *counts* Windows Insider Preview devices, but does not currently provide detailed deployment insights for them.
|
||||||
- **Diagnostic data requirements**: Update Compliance requires devices be configured to send diagnostic data at *Required* level (previously *Basic*). To learn more about what's included in different diagnostic levels, see [Diagnostics, feedback, and privacy in Windows 10](https://support.microsoft.com/help/4468236/diagnostics-feedback-and-privacy-in-windows-10-microsoft-privacy).
|
- **Diagnostic data requirements**: Update Compliance requires devices be configured to send diagnostic data at *Required* level (previously *Basic*). To learn more about what's included in different diagnostic levels, see [Diagnostics, feedback, and privacy in Windows 10](https://support.microsoft.com/help/4468236/diagnostics-feedback-and-privacy-in-windows-10-microsoft-privacy).
|
||||||
- **Data transmission requirements**: Devices must be able to contact specific endpoints required to authenticate and send diagnostic data. These are enumerated in detail at [Configuring Devices for Update Compliance manually](update-compliance-configuration-manual.md).
|
- **Data transmission requirements**: Devices must be able to contact specific endpoints required to authenticate and send diagnostic data. These are enumerated in detail at [Configuring Devices for Update Compliance manually](update-compliance-configuration-manual.md).
|
||||||
- **Showing Device Names in Update Compliance**: For Windows 10, version 1803 or later, device names will not appear in Update Compliance unless you individually opt-in devices by using policy. The steps to accomplish this is outlined in [Configuring Devices for Update Compliance](update-compliance-configuration-manual.md).
|
- **Showing device names in Update Compliance**: For Windows 10, version 1803 or later, device names will not appear in Update Compliance unless you individually opt-in devices by using policy. The steps to accomplish this is outlined in [Configuring Devices for Update Compliance](update-compliance-configuration-manual.md).
|
||||||
|
|
||||||
## Add Update Compliance to your Azure subscription
|
## Add Update Compliance to your Azure subscription
|
||||||
|
|
||||||
|
@ -1,8 +1,8 @@
|
|||||||
---
|
---
|
||||||
title: Monitor Windows Updates and Microsoft Defender AV with Update Compliance (Windows 10)
|
title: Monitor Windows Updates and Microsoft Defender AV with Update Compliance
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
description: You can use Update Compliance in Azure Portal to monitor the progress of updates and key antimalware protection features on devices in your network.
|
description: You can use Update Compliance in Azure portal to monitor the progress of updates and key anti-malware protection features on devices in your network.
|
||||||
keywords: oms, operations management suite, wdav, updates, upgrades, antivirus, antimalware, signature, log analytics
|
keywords: oms, operations management suite, wdav, updates, upgrades, antivirus, antimalware, signature, log analytics
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
@ -18,24 +18,29 @@ ms.custom: seo-marvel-apr2020
|
|||||||
|
|
||||||
# Monitor Windows Updates with Update Compliance
|
# Monitor Windows Updates with Update Compliance
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
Update Compliance enables organizations to:
|
Update Compliance enables organizations to:
|
||||||
|
|
||||||
* Monitor security, quality, and feature updates for Windows 10 Professional, Education, and Enterprise editions.
|
* Monitor security, quality, and feature updates for Windows 10 or Windows 11 Professional, Education, and Enterprise editions.
|
||||||
* View a report of device and update issues related to compliance that need attention.
|
* View a report of device and update issues related to compliance that need attention.
|
||||||
* Check bandwidth savings incurred across multiple content types by using [Delivery Optimization](waas-delivery-optimization.md).
|
* Check bandwidth savings incurred across multiple content types by using [Delivery Optimization](waas-delivery-optimization.md).
|
||||||
|
|
||||||
Update Compliance is offered through the Azure portal, and is included as part of Windows 10 licenses listed in the [prerequisites](update-compliance-get-started.md#update-compliance-prerequisites). Azure Log Analytics ingestion and retention charges are not incurred on your Azure subscription for Update Compliance data.
|
Update Compliance is offered through the Azure portal, and is included as part of Windows 10 or Windows 11 licenses listed in the [prerequisites](update-compliance-get-started.md#update-compliance-prerequisites). Azure Log Analytics ingestion and retention charges are not incurred on your Azure subscription for Update Compliance data.
|
||||||
|
|
||||||
Update Compliance uses Windows 10 diagnostic data for all of its reporting. It collects system data including update deployment progress, [Windows Update for Business](waas-manage-updates-wufb.md) configuration data, and Delivery Optimization usage data, and then sends this data to a customer-owned [Azure Log Analytics](/azure/log-analytics/query-language/get-started-analytics-portal) workspace to power the experience.
|
Update Compliance uses Windows client diagnostic data for all of its reporting. It collects system data including update deployment progress, [Windows Update for Business](waas-manage-updates-wufb.md) configuration data, and Delivery Optimization usage data, and then sends this data to a customer-owned [Azure Log Analytics](/azure/log-analytics/query-language/get-started-analytics-portal) workspace to power the experience.
|
||||||
|
|
||||||
See the following topics in this guide for detailed information about configuring and using the Update Compliance solution:
|
See the following articles in this guide for detailed information about configuring and using the Update Compliance solution:
|
||||||
|
|
||||||
- [Get started with Update Compliance](update-compliance-get-started.md) provides directions on adding Update Compliance to your Azure subscription and configuring devices to send data to Update Compliance.
|
- [Get started with Update Compliance](update-compliance-get-started.md) provides directions on adding Update Compliance to your Azure subscription and configuring devices to send data to Update Compliance.
|
||||||
- [Using Update Compliance](update-compliance-using.md) breaks down every aspect of the Update Compliance experience.
|
- [Using Update Compliance](update-compliance-using.md) breaks down every aspect of the Update Compliance experience.
|
||||||
|
|
||||||
## Related topics
|
## Related articles
|
||||||
|
|
||||||
* [Get started with Update Compliance](update-compliance-get-started.md)
|
* [Get started with Update Compliance](update-compliance-get-started.md)
|
||||||
* [Use Update Compliance to monitor Windows Updates](update-compliance-using.md)
|
* [Use Update Compliance to monitor Windows Updates](update-compliance-using.md)
|
||||||
|
@ -14,9 +14,15 @@ ms.prod: w10
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Needs attention!
|
# Needs attention!
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
The **Needs attention!** section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section.
|
The **Needs attention!** section provides a breakdown of all Windows client device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> The summary tile counts the number of devices that have issues, while the blades within the section break down the issues encountered. A single device can have more than one issue, so these numbers might not add up.
|
> The summary tile counts the number of devices that have issues, while the blades within the section break down the issues encountered. A single device can have more than one issue, so these numbers might not add up.
|
||||||
@ -26,7 +32,7 @@ The different issues are broken down by Device Issues and Update Issues:
|
|||||||
## Device Issues
|
## Device Issues
|
||||||
|
|
||||||
* **Missing multiple security updates:** This issue occurs when a device is behind by two or more security updates. These devices might be more vulnerable and should be investigated and updated.
|
* **Missing multiple security updates:** This issue occurs when a device is behind by two or more security updates. These devices might be more vulnerable and should be investigated and updated.
|
||||||
* **Out of support OS Version:** This issue occurs when a device has fallen out of support due to the version of Windows 10 it is running. When a device has fallen out of support, it will no longer receive important security updates, and might be vulnerable. These devices should be updated to a supported version of Windows 10.
|
* **Out of support OS Version:** This issue occurs when a device has fallen out of support due to the version of Windows client it is running. When a device has fallen out of support, it will no longer receive important security updates, and might be vulnerable. These devices should be updated to a supported version of Windows client.
|
||||||
|
|
||||||
## Update Issues
|
## Update Issues
|
||||||
|
|
||||||
@ -39,7 +45,7 @@ The different issues are broken down by Device Issues and Update Issues:
|
|||||||
Selecting any of the issues will take you to a [Log Analytics](/azure/log-analytics/query-language/get-started-analytics-portal) view with all devices that have the given issue.
|
Selecting any of the issues will take you to a [Log Analytics](/azure/log-analytics/query-language/get-started-analytics-portal) view with all devices that have the given issue.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> This blade also has a link to the [Setup Diagnostic Tool](../upgrade/setupdiag.md), a standalone tool you can use to obtain details about why a Windows 10 feature update was unsuccessful.
|
> This blade also has a link to the [Setup Diagnostic Tool](../upgrade/setupdiag.md), a standalone tool you can use to obtain details about why a Windows client feature update was unsuccessful.
|
||||||
|
|
||||||
## List of Queries
|
## List of Queries
|
||||||
|
|
||||||
|
@ -16,9 +16,14 @@ ms.topic: article
|
|||||||
|
|
||||||
# Privacy in Update Compliance
|
# Privacy in Update Compliance
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
Update Compliance is fully committed to privacy, centering on these tenets:
|
Update Compliance is fully committed to privacy, centering on these tenets:
|
||||||
|
|
||||||
- **Transparency:** Windows 10 diagnostic data events that are required for Update Compliance's operation are fully documented (see the links for additional information) so you can review them with your company's security and compliance teams. The Diagnostic Data Viewer lets you see diagnostic data sent from a given device (see [Diagnostic Data Viewer Overview](/windows/configuration/diagnostic-data-viewer-overview) for details).
|
- **Transparency:** Windows client diagnostic data events that are required for Update Compliance's operation are fully documented (see the links for additional information) so you can review them with your company's security and compliance teams. The Diagnostic Data Viewer lets you see diagnostic data sent from a given device (see [Diagnostic Data Viewer Overview](/windows/configuration/diagnostic-data-viewer-overview) for details).
|
||||||
- **Control:** You ultimately control the level of diagnostic data you wish to share. In Windows 10, version 1709 we added a new policy to Limit enhanced diagnostic data to the minimum required by Windows Analytics.
|
- **Control:** You ultimately control the level of diagnostic data you wish to share. In Windows 10, version 1709 we added a new policy to Limit enhanced diagnostic data to the minimum required by Windows Analytics.
|
||||||
- **Security:** Your data is protected with strong security and encryption.
|
- **Security:** Your data is protected with strong security and encryption.
|
||||||
- **Trust:** Update Compliance supports the Online Services Terms.
|
- **Trust:** Update Compliance supports the Online Services Terms.
|
||||||
|
@ -15,12 +15,17 @@ ms.custom: seo-marvel-apr2020
|
|||||||
|
|
||||||
# Security Update Status
|
# Security Update Status
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
The Security Update Status section provides information about [security updates](waas-quick-start.md#definitions) across all devices. The section tile within the [Overview Blade](update-compliance-using.md#overview-blade) lists the percentage of devices on the latest security update available. Meanwhile, the blades within show the percentage of devices on the latest security update for each Windows 10 version and the deployment progress toward the latest two security updates.
|
The Security Update Status section provides information about [security updates](waas-quick-start.md#definitions) across all devices. The section tile within the [Overview Blade](update-compliance-using.md#overview-blade) lists the percentage of devices on the latest security update available. Meanwhile, the blades within show the percentage of devices on the latest security update for each Windows client version and the deployment progress toward the latest two security updates.
|
||||||
|
|
||||||
The **Overall Security Update Status** blade provides a visualization of devices that are and do not have the latest security updates. Below the visualization are all devices further broken down by operating system version and a count of devices that are up to date and not up to date. The **Not up to date** column also provides a count of update failures.
|
The **Overall Security Update Status** blade provides a visualization of devices that are and do not have the latest security updates. Below the visualization are all devices further broken down by operating system version and a count of devices that are up to date and not up to date. The **Not up to date** column also provides a count of update failures.
|
||||||
|
|
||||||
The **Latest Security Update Status** and **Previous Security Update Status** tiles are stacked to form one blade. The **Latest Security Update Status** provides a visualization of the different deployment states devices are in regarding the latest update for each build (or version) of Windows 10, along with the revision of that update. The **Previous Security Update Status** blade provides the same information without the accompanying visualization.
|
The **Latest Security Update Status** and **Previous Security Update Status** tiles are stacked to form one blade. The **Latest Security Update Status** provides a visualization of the different deployment states devices are in regarding the latest update for each build (or version) of Windows client, along with the revision of that update. The **Previous Security Update Status** blade provides the same information without the accompanying visualization.
|
||||||
|
|
||||||
The rows of each tile in this section are interactive; selecting them will navigate you to the query that is representative of that row and section.
|
The rows of each tile in this section are interactive; selecting them will navigate you to the query that is representative of that row and section.
|
||||||
|
@ -1,5 +1,5 @@
|
|||||||
---
|
---
|
||||||
title: Using Update Compliance (Windows 10)
|
title: Using Update Compliance
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
description: Learn how to use Update Compliance to monitor your device's Windows updates.
|
description: Learn how to use Update Compliance to monitor your device's Windows updates.
|
||||||
@ -18,11 +18,16 @@ ms.custom: seo-marvel-apr2020
|
|||||||
|
|
||||||
# Use Update Compliance
|
# Use Update Compliance
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
In this section you'll learn how to use Update Compliance to monitor your device's Windows updates and Microsoft Defender Antivirus status. To configure your environment for use with Update Compliance, refer to [Get started with Update Compliance](update-compliance-get-started.md).
|
In this section you'll learn how to use Update Compliance to monitor your device's Windows updates and Microsoft Defender Antivirus status. To configure your environment for use with Update Compliance, refer to [Get started with Update Compliance](update-compliance-get-started.md).
|
||||||
|
|
||||||
|
|
||||||
Update Compliance:
|
Update Compliance:
|
||||||
- Provides detailed deployment monitoring for Windows 10 Feature and Quality updates.
|
- Provides detailed deployment monitoring for Windows client feature and quality updates.
|
||||||
- Reports when devices need attention due to issues related to update deployment.
|
- Reports when devices need attention due to issues related to update deployment.
|
||||||
- Shows bandwidth usage and savings for devices that are configured to use [Delivery Optimization](waas-delivery-optimization.md).
|
- Shows bandwidth usage and savings for devices that are configured to use [Delivery Optimization](waas-delivery-optimization.md).
|
||||||
- Provides all of the above data in [Log Analytics](#using-log-analytics), which affords additional querying and export capabilities.
|
- Provides all of the above data in [Log Analytics](#using-log-analytics), which affords additional querying and export capabilities.
|
||||||
@ -49,21 +54,21 @@ When you select this tile, you will be redirected to the Update Compliance works
|
|||||||

|

|
||||||
|
|
||||||
Update Compliance's overview blade summarizes all the data Update Compliance provides. It functions as a hub from which you can navigate to different sections. The total number of devices detected by Update Compliance is reported in the title of this blade. What follows is a distribution for all devices as to whether they are up to date on the following items:
|
Update Compliance's overview blade summarizes all the data Update Compliance provides. It functions as a hub from which you can navigate to different sections. The total number of devices detected by Update Compliance is reported in the title of this blade. What follows is a distribution for all devices as to whether they are up to date on the following items:
|
||||||
* Security updates: A device is up to date on quality updates whenever it has the latest applicable quality update installed. Quality updates are monthly cumulative updates that are specific to a version of Windows 10.
|
* Security updates: A device is up to date on quality updates whenever it has the latest applicable quality update installed. Quality updates are monthly cumulative updates that are specific to a version of Windows client.
|
||||||
* Feature updates: A device is up to date on feature updates whenever it has the latest applicable feature update installed. Update Compliance considers [Servicing Channel](waas-overview.md#servicing-channels) when determining update applicability.
|
* Feature updates: A device is up to date on feature updates whenever it has the latest applicable feature update installed. Update Compliance considers [Servicing Channel](waas-overview.md#servicing-channels) when determining update applicability.
|
||||||
* AV Signature: A device is up to date on Antivirus Signature when the latest Windows Defender Signatures have been downloaded. This distribution only considers devices that are running Microsoft Defender Antivirus.
|
* AV Signature: A device is up to date on Antivirus Signature when the latest Windows Defender Signatures have been downloaded. This distribution only considers devices that are running Microsoft Defender Antivirus.
|
||||||
|
|
||||||
The blade also provides the time at which your Update Compliance workspace was [refreshed](#update-compliance-data-latency).
|
The blade also provides the time at which your Update Compliance workspace was [refreshed](#update-compliance-data-latency).
|
||||||
|
|
||||||
The following is a breakdown of the different sections available in Update Compliance:
|
The following is a breakdown of the different sections available in Update Compliance:
|
||||||
* [Need Attention!](update-compliance-need-attention.md) - This section is the default section when arriving to your Update Compliance workspace. It provides a summary of the different issues devices are facing relative to Windows 10 updates.
|
* [Need Attention!](update-compliance-need-attention.md) - This section is the default section when arriving to your Update Compliance workspace. It provides a summary of the different issues devices are facing relative to Windows client updates.
|
||||||
* [Security Update Status](update-compliance-security-update-status.md) - This section lists the percentage of devices that are on the latest security update released for the version of Windows 10 it is running. Selecting this section provides blades that summarize the overall status of security updates across all devices and a summary of their deployment progress towards the latest two security updates.
|
* [Security Update Status](update-compliance-security-update-status.md) - This section lists the percentage of devices that are on the latest security update released for the version of Windows client it is running. Selecting this section provides blades that summarize the overall status of security updates across all devices and a summary of their deployment progress towards the latest two security updates.
|
||||||
* [Feature Update Status](update-compliance-feature-update-status.md) - This section lists the percentage of devices that are on the latest feature update that is applicable to a given device. Selecting this section provides blades that summarize the overall feature update status across all devices and a summary of deployment status for different versions of Windows 10 in your environment.
|
* [Feature Update Status](update-compliance-feature-update-status.md) - This section lists the percentage of devices that are on the latest feature update that is applicable to a given device. Selecting this section provides blades that summarize the overall feature update status across all devices and a summary of deployment status for different versions of Windows client in your environment.
|
||||||
* [Delivery Optimization Status](update-compliance-delivery-optimization.md) - This section summarizes bandwidth savings incurred by utilizing Delivery Optimization in your environment. It provides a breakdown of Delivery Optimization configuration across devices, and summarizes bandwidth savings and utilization across multiple content types.
|
* [Delivery Optimization Status](update-compliance-delivery-optimization.md) - This section summarizes bandwidth savings incurred by utilizing Delivery Optimization in your environment. It provides a breakdown of Delivery Optimization configuration across devices, and summarizes bandwidth savings and utilization across multiple content types.
|
||||||
|
|
||||||
|
|
||||||
## Update Compliance data latency
|
## Update Compliance data latency
|
||||||
Update Compliance uses Windows 10 diagnostic data as its data source. After you add Update Compliance and appropriately configure your devices, it could take 48-72 hours before they first appear.
|
Update Compliance uses Windows client diagnostic data as its data source. After you add Update Compliance and appropriately configure your devices, it could take 48-72 hours before they first appear.
|
||||||
|
|
||||||
The data powering Update Compliance is refreshed every 24 hours, and refreshes with the latest data from all devices part of your organization that have been seen in the past 28 days. The entire set of data is refreshed in each daily snapshot, which means that the same data can be re-ingested even if no new data actually arrived from the device since the last snapshot. Snapshot time can be determined by the TimeGenerated field for each record, while LastScan can be used to roughly determine the freshness of each record's data.
|
The data powering Update Compliance is refreshed every 24 hours, and refreshes with the latest data from all devices part of your organization that have been seen in the past 28 days. The entire set of data is refreshed in each daily snapshot, which means that the same data can be re-ingested even if no new data actually arrived from the device since the last snapshot. Snapshot time can be determined by the TimeGenerated field for each record, while LastScan can be used to roughly determine the freshness of each record's data.
|
||||||
|
|
||||||
|
@ -1,5 +1,5 @@
|
|||||||
---
|
---
|
||||||
title: Configure BranchCache for Windows 10 updates (Windows 10)
|
title: Configure BranchCache for Windows client updates
|
||||||
description: In this article, learn how to use BranchCache to optimize network bandwidth during update deployment.
|
description: In this article, learn how to use BranchCache to optimize network bandwidth during update deployment.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
@ -12,21 +12,22 @@ ms.topic: article
|
|||||||
ms.custom: seo-marvel-apr2020
|
ms.custom: seo-marvel-apr2020
|
||||||
---
|
---
|
||||||
|
|
||||||
# Configure BranchCache for Windows 10 updates
|
# Configure BranchCache for Windows client updates
|
||||||
|
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||||
|
|
||||||
BranchCache is a bandwidth-optimization feature that has been available since the Windows Server 2008 R2 and Windows 7 operating systems. Each client has a cache and acts as an alternate source for content that devices on its own network request. Windows Server Update Services (WSUS) and Microsoft Endpoint Manager can use BranchCache to optimize network bandwidth during update deployment, and it's easy to configure for either of them. BranchCache has two operating modes: Distributed Cache mode and Hosted Cache mode.
|
BranchCache is a bandwidth-optimization feature that has been available since the Windows Server 2008 R2 and Windows 7 operating systems. Each client has a cache and acts as an alternate source for content that devices on its own network request. Windows Server Update Services (WSUS) and Microsoft Endpoint Manager can use BranchCache to optimize network bandwidth during update deployment, and it's easy to configure for either of them. BranchCache has two operating modes: Distributed Cache mode and Hosted Cache mode.
|
||||||
|
|
||||||
- Distributed Cache mode operates like the [Delivery Optimization](waas-delivery-optimization.md) feature in Windows 10: each client contains a cached version of the BranchCache-enabled files it requests and acts as a distributed cache for other clients requesting that same file.
|
- Distributed Cache mode operates like the [Delivery Optimization](waas-delivery-optimization.md) feature in Windows client: each client contains a cached version of the BranchCache-enabled files it requests and acts as a distributed cache for other clients requesting that same file.
|
||||||
|
|
||||||
>[!TIP]
|
>[!TIP]
|
||||||
>Distributed Cache mode is preferred to Hosted Cache mode for Windows 10 updates to get the most benefit from peer-to-peer distribution.
|
>Distributed Cache mode is preferred to Hosted Cache mode for Windows clients updates to get the most benefit from peer-to-peer distribution.
|
||||||
|
|
||||||
- In Hosted Cache mode, designated servers at specific locations act as a cache for files requested by clients in its area. Then, rather than clients retrieving files from a latent source, the hosted cache server provides the content on its behalf.
|
- In Hosted Cache mode, designated servers at specific locations act as a cache for files requested by clients in its area. Then, rather than clients retrieving files from a latent source, the hosted cache server provides the content on its behalf.
|
||||||
|
|
||||||
@ -36,7 +37,7 @@ For detailed information about how Distributed Cache mode and Hosted Cache mode
|
|||||||
|
|
||||||
Whether you use BranchCache with Configuration Manager or WSUS, each client that uses BranchCache must be configured to do so. You typically make your configurations through Group Policy. For step-by-step instructions on how to use Group Policy to configure BranchCache for Windows clients, see [Client Configuration](/previous-versions/windows/it-pro/windows-7/dd637820(v=ws.10)) in the [BranchCache Early Adopter's Guide](/previous-versions/windows/it-pro/windows-7/dd637762(v=ws.10)).
|
Whether you use BranchCache with Configuration Manager or WSUS, each client that uses BranchCache must be configured to do so. You typically make your configurations through Group Policy. For step-by-step instructions on how to use Group Policy to configure BranchCache for Windows clients, see [Client Configuration](/previous-versions/windows/it-pro/windows-7/dd637820(v=ws.10)) in the [BranchCache Early Adopter's Guide](/previous-versions/windows/it-pro/windows-7/dd637762(v=ws.10)).
|
||||||
|
|
||||||
In Windows 10, version 1607, the Windows Update Agent uses Delivery Optimization by default, even when the updates are retrieved from WSUS. When using BranchCache with Windows 10, simply set the Delivery Optimization mode to Bypass to allow clients to use the Background Intelligent Transfer Service (BITS) protocol with BranchCache instead. For instructions on how to use BranchCache in Distributed Cache mode with WSUS, see the section WSUS and Configuration Manager with BranchCache in Distributed Cache mode.
|
In Windows 10, version 1607, the Windows Update Agent uses Delivery Optimization by default, even when the updates are retrieved from WSUS. When using BranchCache with Windows client, simply set the Delivery Optimization mode to Bypass to allow clients to use the Background Intelligent Transfer Service (BITS) protocol with BranchCache instead. For instructions on how to use BranchCache in Distributed Cache mode with WSUS, see the section WSUS and Configuration Manager with BranchCache in Distributed Cache mode.
|
||||||
|
|
||||||
## Configure servers for BranchCache
|
## Configure servers for BranchCache
|
||||||
|
|
||||||
@ -49,21 +50,3 @@ In addition to these steps, there is one requirement for WSUS to be able to use
|
|||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>Configuration Manager only supports Distributed Cache mode.
|
>Configuration Manager only supports Distributed Cache mode.
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
|
||||||
|
|
||||||
- [Update Windows 10 in the enterprise](index.md)
|
|
||||||
- [Overview of Windows as a service](waas-overview.md)
|
|
||||||
- [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md)
|
|
||||||
- [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md)
|
|
||||||
- [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md)
|
|
||||||
- [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md)
|
|
||||||
- [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md)
|
|
||||||
- [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)
|
|
||||||
- [Configure Windows Update for Business](waas-configure-wufb.md)
|
|
||||||
- [Integrate Windows Update for Business with management solutions](waas-integrate-wufb.md)
|
|
||||||
- [Walkthrough: use Group Policy to configure Windows Update for Business](waas-wufb-group-policy.md)
|
|
||||||
- [Walkthrough: use Intune to configure Windows Update for Business](/intune/windows-update-for-business-configure)
|
|
||||||
- [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)
|
|
||||||
- [Deploy Windows 10 updates using Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service)
|
|
||||||
- [Manage device restarts after updates](waas-restart.md)
|
|
@ -55,7 +55,7 @@ The following table summarizes various Windows 10 deployment scenarios. The scen
|
|||||||
Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old.
|
Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old.
|
||||||
</td>
|
</td>
|
||||||
<td align="center">
|
<td align="center">
|
||||||
<a href="/windows/deployment/deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit">Perform an in-place upgrade to Windows 10 with MDT</a><br><a href="/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager">Perform an in-place upgrade to Windows 10 using Configuration Manager</a>
|
<a href="/windows/deployment/deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit">Perform an in-place upgrade to Windows 10 with MDT</a><br><a href="/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager">Perform an in-place upgrade to Windows 10 using Configuration Manager</a>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
@ -262,12 +262,13 @@ The deployment process for the replace scenario is as follows:
|
|||||||
|
|
||||||
2. Deploy the new computer as a bare-metal deployment.
|
2. Deploy the new computer as a bare-metal deployment.
|
||||||
|
|
||||||
**Note**<br>In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk.
|
> [!NOTE]
|
||||||
|
> In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk.
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
|
- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||||
- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md)
|
- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md)
|
||||||
- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230)
|
- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230)
|
||||||
- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md)
|
- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md)
|
||||||
- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference)
|
- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference)
|
||||||
|
96
windows/hub/images/winlogo.svg
Normal file
@ -0,0 +1,96 @@
|
|||||||
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||||||
|
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
|
||||||
|
<!-- Generated by Microsoft Visio, SVG Export winlogo.svg Page-1 -->
|
||||||
|
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ev="http://www.w3.org/2001/xml-events"
|
||||||
|
xmlns:v="http://schemas.microsoft.com/visio/2003/SVGExtensions/" width="6.06944in" height="6.09028in"
|
||||||
|
viewBox="0 0 437 438.5" xml:space="preserve" color-interpolation-filters="sRGB" class="st2">
|
||||||
|
<v:documentProperties v:langID="1033" v:viewMarkup="false"/>
|
||||||
|
|
||||||
|
<style type="text/css">
|
||||||
|
<![CDATA[
|
||||||
|
.st1 {fill:none;stroke:none;stroke-width:0.25}
|
||||||
|
.st2 {fill:none;fill-rule:evenodd;font-size:12px;overflow:visible;stroke-linecap:square;stroke-miterlimit:3}
|
||||||
|
]]>
|
||||||
|
</style>
|
||||||
|
|
||||||
|
<g v:mID="0" v:index="1" v:groupContext="foregroundPage">
|
||||||
|
<title>Page-1</title>
|
||||||
|
<v:pageProperties v:drawingScale="1" v:pageScale="1" v:drawingUnits="0" v:shadowOffsetX="9" v:shadowOffsetY="-9"/>
|
||||||
|
<g id="shape1-1" v:mID="1" v:groupContext="shape" transform="translate(0.25,-0.25)">
|
||||||
|
<title>Sheet.1</title>
|
||||||
|
<rect v:rectContext="foreign" x="0" y="0.500011" width="436.5" height="438" class="st1"/>
|
||||||
|
<image x="0" y="0.500011" width="436.5" height="438" preserveAspectRatio="none" xlink:href="data:image/png;base64,iV
|
||||||
|
BORw0KGgoAAAANSUhEUgAAAkYAAAJICAYAAACE1yscAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAAFiUAABYlAU
|
||||||
|
lSJPAAABTLSURBVHhe7dYxTiBQDENBjs1B9z6shL4r3EREaZgnTe/SH1+SJEn6zjGSJEl6OUaSJEkvx0iSJOnlGEmSJL1+HKOPz38Av3
|
||||||
|
Jd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bAD
|
||||||
|
CRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2
|
||||||
|
DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQ
|
||||||
|
PARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEco
|
||||||
|
yAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117
|
||||||
|
UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8
|
||||||
|
kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l
|
||||||
|
3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AE
|
||||||
|
wkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCF
|
||||||
|
h3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2w
|
||||||
|
AwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHC
|
||||||
|
Ng3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW
|
||||||
|
0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARH
|
||||||
|
KMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdd
|
||||||
|
e1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNAB
|
||||||
|
PJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAt
|
||||||
|
Zd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNg
|
||||||
|
BMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxw
|
||||||
|
hYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3Xd
|
||||||
|
sAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkR
|
||||||
|
wjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3X
|
||||||
|
VtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwE
|
||||||
|
RyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgH
|
||||||
|
XXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQ
|
||||||
|
ATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQ
|
||||||
|
LWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1z
|
||||||
|
YATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJM
|
||||||
|
cIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd1
|
||||||
|
3bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJ
|
||||||
|
EcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN
|
||||||
|
11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8
|
||||||
|
BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjI
|
||||||
|
B117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BE+nGMJEmS/mqOkSRJ0ssxkiRJejlGkiRJL8dIkiTp5RhJkiS9HCNJkqSXYy
|
||||||
|
RJkvRyjCRJkl6OkSRJ0ssxkiRJejlGkiRJL8dIkiTp5RhJkiS9HCNJkqSXYyRJkvRyjCRJkl6OkSRJ0ssxkiRJejlGkiRJL8dIkiTp5R
|
||||||
|
hJkiS9HCNJkqSXYyRJkvRyjCRJkl6OkSRJ0ssxkiRJejlGkiRJrx/H6OPzH8CvXNc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQ
|
||||||
|
ATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQ
|
||||||
|
LWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1z
|
||||||
|
YATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJM
|
||||||
|
cIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd1
|
||||||
|
3bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJ
|
||||||
|
EcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN
|
||||||
|
11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8
|
||||||
|
BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjI
|
||||||
|
B117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ
|
||||||
|
0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyT
|
||||||
|
EC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXd
|
||||||
|
c2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATC
|
||||||
|
THCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWH
|
||||||
|
dd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bAD
|
||||||
|
CRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2
|
||||||
|
DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQ
|
||||||
|
PARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEco
|
||||||
|
yAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117
|
||||||
|
UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8
|
||||||
|
kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l
|
||||||
|
3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AE
|
||||||
|
wkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCF
|
||||||
|
h3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2w
|
||||||
|
AwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHC
|
||||||
|
Ng3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW
|
||||||
|
0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARH
|
||||||
|
KMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdd
|
||||||
|
e1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNAB
|
||||||
|
PJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAt
|
||||||
|
Zd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxwhYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNg
|
||||||
|
BMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3XdsAMJEcI2DddW0DwERyjIB117UNABPJMQLWXdc2AEwkxw
|
||||||
|
hYd13bADCRHCNg3XVtA8BEcoyAdde1DQATyTEC1l3XNgBMJMcIWHdd2wAwkRwjYN11bQPARHKMgHXXtQ0AE8kxAtZd1zYATCTHCFh3Xd
|
||||||
|
sAMJF+HCNJkqS/mmMkSZL0cowkSZK++/r6DwqOoucNyrLNAAAAAElFTkSuQmCC"/>
|
||||||
|
<rect v:rectContext="foreign" x="0" y="0.500011" width="436.5" height="438" class="st1"/>
|
||||||
|
</g>
|
||||||
|
</g>
|
||||||
|
</svg>
|
After Width: | Height: | Size: 9.0 KiB |
@ -1,121 +1,243 @@
|
|||||||
### YamlMime:Landing
|
### YamlMime:Hub
|
||||||
|
|
||||||
title: Windows client resources and documentation for IT Pros # < 60 chars
|
title: Windows client documentation for IT Pros # < 60 chars
|
||||||
summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # < 160 chars
|
summary: Evaluate, plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # < 160 chars
|
||||||
|
# brand: aspnet | azure | dotnet | dynamics | m365 | ms-graph | office | power-apps | power-automate | power-bi | power-platform | power-virtual-agents | sql | sql-server | vs | visual-studio | windows | xamarin
|
||||||
|
brand: windows
|
||||||
|
|
||||||
metadata:
|
metadata:
|
||||||
title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars.
|
title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars.
|
||||||
description: Evaluate, plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars.
|
description: Evaluate, plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars.
|
||||||
services: windows-10
|
services: windows-10
|
||||||
ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM.
|
ms.service: subservice #Required; service per approved list. service slug assigned to your service by ACOM.
|
||||||
ms.subservice: subservice
|
ms.subservice: subservice # Optional; Remove if no subservice is used.
|
||||||
ms.topic: landing-page # Required
|
ms.topic: hub-page # Required
|
||||||
ms.collection: windows-10
|
ms.collection: windows-10 # Optional; Remove if no collection is used.
|
||||||
author: greg-lindsay #Required; your GitHub user alias, with correct capitalization.
|
author: dougeby #Required; your GitHub user alias, with correct capitalization.
|
||||||
ms.author: greglin #Required; microsoft alias of author; optional team alias.
|
ms.author: dougeby #Required; microsoft alias of author; optional team alias.
|
||||||
ms.date: 06/01/2020 #Required; mm/dd/yyyy format.
|
ms.date: 10/01/2021 #Required; mm/dd/yyyy format.
|
||||||
localization_priority: medium
|
localization_priority: medium
|
||||||
|
|
||||||
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
|
# highlightedContent section (optional)
|
||||||
|
# Maximum of 8 items
|
||||||
|
highlightedContent:
|
||||||
|
# itemType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
|
||||||
|
items:
|
||||||
|
# Card
|
||||||
|
- title: Become a Windows Insider
|
||||||
|
itemType: overview
|
||||||
|
url: https://insider.windows.com
|
||||||
|
# Card
|
||||||
|
- title: See what's new in Windows release health
|
||||||
|
itemType: overview
|
||||||
|
url: /windows/release-health/
|
||||||
|
# Card
|
||||||
|
- title: Learn more about Hybrid Work
|
||||||
|
itemType: overview
|
||||||
|
url: https://www.microsoft.com/hybridwork/
|
||||||
|
|
||||||
landingContent:
|
|
||||||
# Cards and links should be based on top customer tasks or top subjects
|
# productDirectory section (optional)
|
||||||
# Start card title with a verb
|
productDirectory:
|
||||||
# Card (optional)
|
title: Get to know Windows 11 # < 60 chars (optional)
|
||||||
- title: What's new
|
summary: Learn more about what's new, what's updated, and what you get in Windows 11 # < 160 chars (optional)
|
||||||
linkLists:
|
items:
|
||||||
- linkListType: overview
|
# Card
|
||||||
links:
|
- title: What's new in Windows 11
|
||||||
- text: Windows 11 overview
|
imageSrc: /windows/resources/images/winlogo.svg
|
||||||
url: /windows/whats-new/windows-11
|
summary: Get more information about features and improvements that are important to admins
|
||||||
- text: Windows 11 requirements
|
url: /windows/whats-new/windows-11-whats-new
|
||||||
|
- title: Windows 11 requirements
|
||||||
|
imageSrc: /windows/resources/images/winlogo.svg
|
||||||
|
summary: See the system requirements for Windows 11, including running Windows 11 on a virtual machine
|
||||||
url: /windows/whats-new/windows-11-requirements
|
url: /windows/whats-new/windows-11-requirements
|
||||||
- text: Plan for Windows 11
|
- title: Trusted Platform Module (TPM)
|
||||||
url: /windows/whats-new/windows-11-plan
|
imageSrc: /windows/resources/images/winlogo.svg
|
||||||
- text: Prepare for Windows 11
|
summary: Learn more about TPM, and why it's a good thing
|
||||||
url: /windows/whats-new/windows-11-prepare
|
url: /windows/security/information-protection/tpm/trusted-platform-module-overview
|
||||||
- text: What's new in Windows 10, version 21H1
|
|
||||||
url: /windows/whats-new/whats-new-windows-10-version-21H1
|
# conceptualContent section (optional)
|
||||||
- text: Windows release information
|
conceptualContent:
|
||||||
url: /windows/release-health/release-information
|
# Supports up to 3 sections
|
||||||
|
# itemType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
|
||||||
|
|
||||||
|
title: Windows client resources and documentation for IT Pros
|
||||||
|
summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows 11.
|
||||||
|
items:
|
||||||
|
# card
|
||||||
|
- title: Overview
|
||||||
|
links:
|
||||||
|
- url: /windows/whats-new/windows-11-whats-new
|
||||||
|
itemType: overview
|
||||||
|
text: What's new in Windows 11
|
||||||
|
- url: /windows/whats-new/windows-11-plan
|
||||||
|
itemType: overview
|
||||||
|
text: Plan for Windows 11
|
||||||
|
- url: /windows/whats-new/windows-11-prepare
|
||||||
|
itemType: overview
|
||||||
|
text: Prepare for Windows 11
|
||||||
|
- url: /windows/whats-new/whats-new-windows-10-version-21H1
|
||||||
|
itemType: overview
|
||||||
|
text: What's new in Windows 10, version 21H1
|
||||||
|
- url: /windows/release-health/release-information
|
||||||
|
itemType: overview
|
||||||
|
text: Windows release information
|
||||||
|
|
||||||
# Card (optional)
|
# Card (optional)
|
||||||
- title: Configuration
|
- title: Configuration
|
||||||
linkLists:
|
|
||||||
- linkListType: how-to-guide
|
|
||||||
links:
|
links:
|
||||||
- text: Configure Windows
|
- url: /windows/configuration/index
|
||||||
url: /windows/configuration/index
|
itemType: overview
|
||||||
- text: Accessibility information for IT Pros
|
text: Configure Windows
|
||||||
url: /windows/configuration/windows-10-accessibility-for-itpros
|
- url: /windows/configuration/provisioning-packages/provisioning-packages
|
||||||
- text: Configure access to Microsoft Store
|
itemType: how-to-guide
|
||||||
url: /windows/configuration/stop-employees-from-using-microsoft-store
|
text: Use Provisioning packages to configure new devices
|
||||||
- text: Set up a shared or guest PC
|
- url: /windows/configuration/windows-10-accessibility-for-itpros
|
||||||
url: /windows/configuration/set-up-shared-or-guest-pc
|
itemType: overview
|
||||||
|
text: Accessibility information for IT Pros
|
||||||
|
- url: /windows/configuration/customize-start-menu-layout-windows-11
|
||||||
|
itemType: how-to-guide
|
||||||
|
text: Customize the Start menu layout
|
||||||
|
- url: /windows/configuration/stop-employees-from-using-microsoft-store
|
||||||
|
itemType: how-to-guide
|
||||||
|
text: Control access to Microsoft Store
|
||||||
|
- url: /windows/configuration/set-up-shared-or-guest-pc
|
||||||
|
itemType: how-to-guide
|
||||||
|
text: Set up a shared or guest PC
|
||||||
|
|
||||||
# Card (optional)
|
# Card (optional)
|
||||||
- title: Deployment
|
- title: Deployment
|
||||||
linkLists:
|
|
||||||
- linkListType: deploy
|
|
||||||
links:
|
links:
|
||||||
- text: Deploy and update Windows
|
- url: /windows/deployment/index
|
||||||
url: /windows/deployment/index
|
itemType: deploy
|
||||||
- text: Windows deployment scenarios
|
text: Deploy and update Windows
|
||||||
url: /windows/deployment/windows-10-deployment-scenarios
|
- url: /windows/deployment/windows-10-deployment-scenarios
|
||||||
- text: Create a deployment plan
|
itemType: deploy
|
||||||
url: /windows/deployment/update/create-deployment-plan
|
text: Windows deployment scenarios
|
||||||
- text: Prepare to deploy Windows client
|
- url: /windows/deployment/update/create-deployment-plan
|
||||||
url: /windows/deployment/update/prepare-deploy-windows
|
itemType: deploy
|
||||||
|
text: Create a deployment plan
|
||||||
|
- url: /windows/deployment/update/prepare-deploy-windows
|
||||||
|
itemType: deploy
|
||||||
|
text: Prepare to deploy Windows client
|
||||||
|
|
||||||
# Card
|
# Card
|
||||||
- title: App management
|
- title: App management
|
||||||
linkLists:
|
|
||||||
- linkListType: how-to-guide
|
|
||||||
links:
|
links:
|
||||||
- text: Windows application management
|
- url: /windows/application-management/index
|
||||||
url: /windows/application-management/index
|
itemType: overview
|
||||||
- text: Understand the different apps included in Windows 10
|
text: Windows application management
|
||||||
url: /windows/application-management/apps-in-windows-10
|
- url: /windows/application-management/apps-in-windows-10
|
||||||
- text: Get started with App-V for Windows 10
|
itemType: overview
|
||||||
url: /windows/application-management/app-v/appv-getting-started
|
text: Learn more about the different apps types for Windows
|
||||||
- text: Keep removed apps from returning during an update
|
- url: /windows/application-management/private-app-repository-mdm-company-portal-windows-11
|
||||||
url: /windows/application-management/remove-provisioned-apps-during-update
|
itemType: how-to-guide
|
||||||
|
text: Use the private app repo on Windows 11
|
||||||
|
- url: /windows/application-management/remove-provisioned-apps-during-update
|
||||||
|
itemType: how-to-guide
|
||||||
|
text: Keep removed apps from returning during an update
|
||||||
|
|
||||||
# Card
|
# Card
|
||||||
- title: Client management
|
- title: Client management
|
||||||
linkLists:
|
|
||||||
- linkListType: how-to-guide
|
|
||||||
links:
|
links:
|
||||||
- text: Windows client management
|
|
||||||
url: /windows/client-management/index
|
- url: /windows/client-management/index
|
||||||
- text: Administrative tools
|
itemType: overview
|
||||||
url: /windows/client-management/administrative-tools-in-windows-10
|
text: Windows client management
|
||||||
- text: Create mandatory user profiles
|
- url: /windows/client-management/administrative-tools-in-windows-10
|
||||||
url: /windows/client-management/mandatory-user-profile
|
itemType: overview
|
||||||
- text: New policies for Windows 10
|
text: Administrative tools
|
||||||
url: /windows/client-management/new-policies-for-windows-10
|
- url: /windows/client-management/mandatory-user-profile
|
||||||
- text: Configuration service provider reference
|
itemType: how-to-guide
|
||||||
url: /windows/client-management/mdm/configuration-service-provider-reference
|
text: Create mandatory user profiles
|
||||||
|
- url: /windows/client-management/new-policies-for-windows-10
|
||||||
|
itemType: overview
|
||||||
|
text: New policies for Windows 10
|
||||||
|
- url: /windows/client-management/mdm/configuration-service-provider-reference
|
||||||
|
itemType: reference
|
||||||
|
text: Configuration service provider reference
|
||||||
|
|
||||||
# Card (optional)
|
# Card (optional)
|
||||||
- title: Security and Privacy
|
- title: Security and Privacy
|
||||||
linkLists:
|
|
||||||
- linkListType: how-to-guide
|
|
||||||
links:
|
links:
|
||||||
- text: Windows Enterprise Security
|
- url: /windows/security/index
|
||||||
url: /windows/security/index
|
itemType: overview
|
||||||
- text: Windows Privacy
|
text: Windows Enterprise Security
|
||||||
url: /windows/privacy/index
|
- url: /windows/privacy/index
|
||||||
- text: Identity and access management
|
itemType: overview
|
||||||
url: /windows/security/identity-protection/index
|
text: Windows Privacy
|
||||||
- text: Threat protection
|
- url: /windows/security/hardware
|
||||||
url: /windows/security/threat-protection/index
|
itemType: overview
|
||||||
- text: Information protection
|
text: Hardware security
|
||||||
url: /windows/security/information-protection/index
|
- url: /windows/security/operating-system
|
||||||
- text: Required diagnostic data
|
itemType: overview
|
||||||
url: /windows/privacy/required-windows-diagnostic-data-events-and-fields-2004
|
text: Operating system security
|
||||||
- text: Optional diagnostic data
|
- url: /windows/security/apps
|
||||||
url: /windows/privacy/windows-diagnostic-data
|
itemType: overview
|
||||||
- text: Changes to Windows diagnostic data collection
|
text: Application security
|
||||||
url: /windows/privacy/changes-to-windows-diagnostic-data-collection
|
- url: /windows/security/identity
|
||||||
|
itemType: overview
|
||||||
|
text: User and identity security
|
||||||
|
- url: /windows/security/cloud
|
||||||
|
itemType: overview
|
||||||
|
text: Cloud services
|
||||||
|
|
||||||
|
# additionalContent section (optional)
|
||||||
|
# Card with summary style
|
||||||
|
additionalContent:
|
||||||
|
# Supports up to 4 subsections
|
||||||
|
sections:
|
||||||
|
- title: More Windows resources # < 60 chars (optional)
|
||||||
|
items:
|
||||||
|
# Card
|
||||||
|
- title: Windows 11 product site
|
||||||
|
summary: Find out more about Windows 11 for enterprise and Windows 11 for business
|
||||||
|
url: https://www.microsoft.com/microsoft-365/windows
|
||||||
|
- title: Windows blogs
|
||||||
|
summary: Keep up with the latest news about Windows
|
||||||
|
url: https://blogs.windows.com/
|
||||||
|
- title: "Planning for Windows 11: best practices for organizations"
|
||||||
|
summary: Blog article with best practices to help you plan for Windows 11
|
||||||
|
url: https://aka.ms/Windows/blog002
|
||||||
|
- title: Windows 11 security explained
|
||||||
|
summary: Blog article to learn how Windows 11 enables security by design from the chip to the cloud
|
||||||
|
url: https://aka.ms/Windows/blog010
|
||||||
|
# Card
|
||||||
|
- title: Participate in the Tech Community
|
||||||
|
summary: Learn how to be part of the Windows Tech Community
|
||||||
|
url: https://techcommunity.microsoft.com/t5/windows/ct-p/Windows10
|
||||||
|
# Card
|
||||||
|
- title: Ask the community
|
||||||
|
summary: Get help, and help others
|
||||||
|
url: https://answers.microsoft.com/windows/forum
|
||||||
|
|
||||||
|
- title: Other resources
|
||||||
|
items:
|
||||||
|
- title: Microsoft Endpoint Manager
|
||||||
|
links:
|
||||||
|
- text: Microsoft Endpoint Manager documentation
|
||||||
|
url: /mem
|
||||||
|
- text: Overview of Microsoft Endpoint Manager
|
||||||
|
url: /mem/endpoint-manager-overview
|
||||||
|
- text: Getting started with Microsoft Endpoint Manager
|
||||||
|
url: /mem/endpoint-manager-getting-started
|
||||||
|
- text: Microsoft Endpoint Manager blog
|
||||||
|
url: https://aka.ms/memblog
|
||||||
|
- title: Windows 365
|
||||||
|
links:
|
||||||
|
- text: Windows 365 documentation
|
||||||
|
url: /windows-365
|
||||||
|
- text: What is Windows 365
|
||||||
|
url: /windows-365/overview
|
||||||
|
- text: Windows 365 blog
|
||||||
|
url: https://www.microsoft.com/microsoft-365/blog/
|
||||||
|
- title: Windows Server
|
||||||
|
links:
|
||||||
|
- text: Windows Server documentation
|
||||||
|
url: /windows-server
|
||||||
|
- text: What's new in Windows Server 2022?
|
||||||
|
url: /windows-server/get-started/whats-new-in-windows-server-2022
|
||||||
|
- text: Get started with Windows Server
|
||||||
|
url: /windows-server/get-started/get-started-with-windows-server
|
||||||
|
- text: Windows Server blog
|
||||||
|
url: https://cloudblogs.microsoft.com/windowsserver/
|
@ -68,6 +68,8 @@ The following methodology was used to derive these network endpoints:
|
|||||||
|||HTTP|dmd.metaservices.microsoft.com|
|
|||HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic Data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft. ||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-priv-feedback)|
|
|Diagnostic Data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft. ||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-priv-feedback)|
|
||||||
|||TLSv1.2/HTTPS/HTTP|v10.events.data.microsoft.com|
|
|||TLSv1.2/HTTPS/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting. To turn off traffic for these endpoints, enable the following Group Policy: Administrative Templates > Windows Components > Windows Error Reporting > Disable Windows Error Reporting. This means error reporting information will not be sent back to Microsoft.|TLSv1.2|telecommand.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting. To turn off traffic for these endpoints, enable the following Group Policy: Administrative Templates > Windows Components > Windows Error Reporting > Disable Windows Error Reporting. This means error reporting information will not be sent back to Microsoft.|TLSv1.2|telecommand.telemetry.microsoft.com|
|
||||||
|||TLS v1.2/HTTPS/HTTP|watson.*.microsoft.com|
|
|||TLS v1.2/HTTPS/HTTP|watson.*.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand. If you turn off traffic for these endpoints, you will not be able to download fonts on demand.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#6-font-streaming)|
|
|Font Streaming|The following endpoints are used to download fonts on demand. If you turn off traffic for these endpoints, you will not be able to download fonts on demand.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#6-font-streaming)|
|
||||||
@ -79,8 +81,9 @@ The following methodology was used to derive these network endpoints:
|
|||||||
|Microsoft Account|||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-microsoft-account)|
|
|Microsoft Account|||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-microsoft-account)|
|
||||||
||The following endpoints are used for Microsoft accounts to sign in. If you turn off traffic for these endpoints, users cannot sign in with Microsoft accounts. |TLSv1.2/HTTPS|login.live.com|
|
||The following endpoints are used for Microsoft accounts to sign in. If you turn off traffic for these endpoints, users cannot sign in with Microsoft accounts. |TLSv1.2/HTTPS|login.live.com|
|
||||||
|Microsoft Edge|||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#13-microsoft-edge)|
|
|Microsoft Edge|||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#13-microsoft-edge)|
|
||||||
||This network traffic is related to the Microsoft Edge browser. The Microsoft Edge browser requires this endpoint to contact external websites.|HTTPS|iecvlist.microsoft.com|
|
||This traffic is related to the Microsoft Edge browser.|HTTPS|iecvlist.microsoft.com|
|
||||||
||The following endpoint is used by Microsoft Edge Update service to check for new updates. If you disable this endpoint, Microsoft Edge won’t be able to check for and apply new edge updates.|TLSv1.2/HTTPS/HTTP|msedge.api.cdp.microsoft.com|
|
||The following endpoint is used by Microsoft Edge Update service to check for new updates. If you disable this endpoint, Microsoft Edge won’t be able to check for and apply new edge updates.|TLSv1.2/HTTPS/HTTP|msedge.api.cdp.microsoft.com|
|
||||||
|
|Microsoft forward link redirection service (FWLink)|The following endpoint is used by the Microsoft forward link redirection service (FWLink) to redirect permanent web links to their actual, sometimes transitory, URL. FWlinks are similar to URL shorteners, just longer. If you disable this endpoint, Windows Defender won't be able to update its malware definitions; links from Windows and other Microsoft products to the Web won't work; and PowerShell updateable Help won't update. To disable the traffic, instead disable the traffic that's getting forwarded.|HTTP|go.microsoft.com|
|
||||||
|Microsoft Store|||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#26-microsoft-store)|
|
|Microsoft Store|||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#26-microsoft-store)|
|
||||||
||The following endpoint is used to download image files that are called when applications run (Microsoft Store or Inbox MSN Apps). If you turn off traffic for these endpoints, the image files won't be downloaded, and apps cannot be installed or updated from the Microsoft Store. Additionally, the Microsoft Store won't be able to revoke malicious apps and users will still be able to open them.|HTTPS|img-prod-cms-rt-microsoft-com.akamaized.net|
|
||The following endpoint is used to download image files that are called when applications run (Microsoft Store or Inbox MSN Apps). If you turn off traffic for these endpoints, the image files won't be downloaded, and apps cannot be installed or updated from the Microsoft Store. Additionally, the Microsoft Store won't be able to revoke malicious apps and users will still be able to open them.|HTTPS|img-prod-cms-rt-microsoft-com.akamaized.net|
|
||||||
||The following endpoint is needed to load the content in the Microsoft Store app.|HTTPS|livetileedge.dsx.mp.microsoft.com|
|
||The following endpoint is needed to load the content in the Microsoft Store app.|HTTPS|livetileedge.dsx.mp.microsoft.com|
|
||||||
@ -111,7 +114,7 @@ The following methodology was used to derive these network endpoints:
|
|||||||
|||TLSv1.2/HTTPS/HTTP|config.edge.skype.com|
|
|||TLSv1.2/HTTPS/HTTP|config.edge.skype.com|
|
||||||
|Teams|The following endpoint is used for Microsoft Teams application.||[Learn how to turn off traffic to all of the following endpoint(s).]( manage-connections-from-windows-operating-system-components-to-microsoft-services.md#26-microsoft-store)|
|
|Teams|The following endpoint is used for Microsoft Teams application.||[Learn how to turn off traffic to all of the following endpoint(s).]( manage-connections-from-windows-operating-system-components-to-microsoft-services.md#26-microsoft-store)|
|
||||||
|||TLSv1.2/HTTPS/HTTP|config.teams.microsoft.com|
|
|||TLSv1.2/HTTPS/HTTP|config.teams.microsoft.com|
|
||||||
|Microsoft Defender Antivirus|The following endpoint is used for Windows Defender when Cloud-based Protection is enabled. If you turn off traffic for this endpoint, the device will not use Cloud-based Protection.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-defender)|
|
|Windows Defender|The following endpoint is used for Windows Defender when Cloud-based Protection is enabled. If you turn off traffic for this endpoint, the device will not use Cloud-based Protection.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-defender)|
|
||||||
|||HTTPS/TLSv1.2|wdcp.microsoft.com|
|
|||HTTPS/TLSv1.2|wdcp.microsoft.com|
|
||||||
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications. If you turn off traffic for these endpoints, SmartScreen notifications will not appear.|HTTPS|*smartscreen-prod.microsoft.com|
|
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications. If you turn off traffic for these endpoints, SmartScreen notifications will not appear.|HTTPS|*smartscreen-prod.microsoft.com|
|
||||||
|||HTTPS/HTTP|checkappexec.microsoft.com|
|
|||HTTPS/HTTP|checkappexec.microsoft.com|
|
||||||
|
@ -65,8 +65,10 @@ The following methodology was used to derive these network endpoints:
|
|||||||
||The following endpoint is used to authenticate a device. If you turn off traffic for this endpoint, the device will not be authenticated.|HTTPS|login.live.com*|
|
||The following endpoint is used to authenticate a device. If you turn off traffic for this endpoint, the device will not be authenticated.|HTTPS|login.live.com*|
|
||||||
|Device metadata|The following endpoint is used to retrieve device metadata. If you turn off traffic for this endpoint, metadata will not be updated for the device.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#4-device-metadata-retrieval)|
|
|Device metadata|The following endpoint is used to retrieve device metadata. If you turn off traffic for this endpoint, metadata will not be updated for the device.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#4-device-metadata-retrieval)|
|
||||||
|||HTTP|dmd.metaservices.microsoft.com|
|
|||HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic Data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. <br/>If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft. ||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-priv-feedback)|
|
|Diagnostic Data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft. ||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#bkmk-priv-feedback)|
|
||||||
|||TLSv1.2/HTTPS/HTTP|v10.events.data.microsoft.com|
|
|||TLSv1.2/HTTPS/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting. To turn off traffic for these endpoints, enable the following Group Policy: Administrative Templates > Windows Components > Windows Error Reporting > Disable Windows Error Reporting. This means error reporting information will not be sent back to Microsoft.|TLSv1.2|telecommand.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting. To turn off traffic for these endpoints, enable the following Group Policy: Administrative Templates > Windows Components > Windows Error Reporting > Disable Windows Error Reporting. This means error reporting information will not be sent back to Microsoft.|TLSv1.2|telecommand.telemetry.microsoft.com|
|
||||||
|||TLS v1.2/HTTPS/HTTP|watson.*.microsoft.com|
|
|||TLS v1.2/HTTPS/HTTP|watson.*.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand. If you turn off traffic for these endpoints, you will not be able to download fonts on demand.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#6-font-streaming)|
|
|Font Streaming|The following endpoints are used to download fonts on demand. If you turn off traffic for these endpoints, you will not be able to download fonts on demand.||[Learn how to turn off traffic to all of the following endpoint(s).](manage-connections-from-windows-operating-system-components-to-microsoft-services.md#6-font-streaming)|
|
||||||
|
@ -31,7 +31,7 @@ The following methodology was used to derive the network endpoints:
|
|||||||
5. The test virtual machine(s) was logged into using a local account, and was not joined to a domain or Azure Active Directory.
|
5. The test virtual machine(s) was logged into using a local account, and was not joined to a domain or Azure Active Directory.
|
||||||
6. All traffic was captured in our lab using a IPV4 network. Therefore, no IPV6 traffic is reported here.
|
6. All traffic was captured in our lab using a IPV4 network. Therefore, no IPV6 traffic is reported here.
|
||||||
7. These tests were conducted in an approved Microsoft lab. It's possible your results may be different.
|
7. These tests were conducted in an approved Microsoft lab. It's possible your results may be different.
|
||||||
8. These tests were conducted for one week. If you capture traffic for longer, you may have different results.
|
8. These tests were conducted for one week. If you capture traffic for longer you may have different results.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
|
> Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
|
||||||
@ -40,7 +40,7 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|
|
||||||
| **Area** | **Description** | **Protocol** | **Destination** |
|
| **Area** | **Description** | **Protocol** | **Destination** |
|
||||||
|-----------|--------------- |------------- |-----------------|
|
|-----------|--------------- |------------- |-----------------|
|
||||||
| Activity Feed Service |The following endpoints are used by Activity Feed Service, which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
| Activity Feed Service |The following endpoints are used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
||||||
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
||||||
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||||||
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||||||
@ -53,7 +53,9 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
||||||
|Device Directory Service|Used by Device Directory Service to keep track of user-device associations and storing metadata about the devices.|HTTPS/HTTP|cs.dds.microsoft.com|
|
|Device Directory Service|Used by Device Directory Service to keep track of user-device associations and storing metadata about the devices.|HTTPS/HTTP|cs.dds.microsoft.com|
|
||||||
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. <br/>If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
||||||
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
||||||
@ -104,7 +106,8 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|||TLSv1.2|definitionupdates.microsoft.com|
|
|||TLSv1.2|definitionupdates.microsoft.com|
|
||||||
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications.|TLSv1.2|*.smartscreen.microsoft.com|
|
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications.|TLSv1.2|*.smartscreen.microsoft.com|
|
||||||
|||TLSv1.2/HTTP|checkappexec.microsoft.com|
|
|||TLSv1.2/HTTP|checkappexec.microsoft.com|
|
||||||
|Windows Spotlight|The following endpoints are used to retrieve Windows Spotlight metadata that describes content, such as references to image locations, as well as suggested apps, Microsoft account notifications, and Windows tips.|TLSv1.2/HTTPS/HTTP|arc.msn.com*</br>ris.api.iris.microsoft.com|
|
|Windows Spotlight|The following endpoints are used to retrieve Windows Spotlight metadata that describes content, such as references to image locations, as well as suggested apps, Microsoft account notifications, and Windows tips.|TLSv1.2/HTTPS/HTTP|arc.msn.com*|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|ris.api.iris.microsoft.com|
|
||||||
|||HTTPS|mucp.api.account.microsoft.com|
|
|||HTTPS|mucp.api.account.microsoft.com|
|
||||||
|Windows Update|The following endpoint is used for Windows Update downloads of apps and OS updates, including HTTP downloads or HTTP downloads blended with peers.|TLSv1.2/HTTPS/HTTP|*.prod.do.dsp.mp.microsoft.com|
|
|Windows Update|The following endpoint is used for Windows Update downloads of apps and OS updates, including HTTP downloads or HTTP downloads blended with peers.|TLSv1.2/HTTPS/HTTP|*.prod.do.dsp.mp.microsoft.com|
|
||||||
|||TLSv1.2/HTTP|emdl.ws.microsoft.com|
|
|||TLSv1.2/HTTP|emdl.ws.microsoft.com|
|
||||||
@ -114,16 +117,18 @@ The following methodology was used to derive the network endpoints:
|
|||||||
||The following endpoints enable connections to Windows Update, Microsoft Update, and the online services of the Store to help keep the device secure.|TLSv1.2/HTTPS/HTTP|*.update.microsoft.com|
|
||The following endpoints enable connections to Windows Update, Microsoft Update, and the online services of the Store to help keep the device secure.|TLSv1.2/HTTPS/HTTP|*.update.microsoft.com|
|
||||||
||The following endpoint is used for compatibility database updates for Windows.|HTTP/HTTPS|adl.windows.com|
|
||The following endpoint is used for compatibility database updates for Windows.|HTTP/HTTPS|adl.windows.com|
|
||||||
||The following endpoint is used for content regulation.|TLSv1.2/HTTPS/HTTP|tsfe.trafficshaping.dsp.mp.microsoft.com|
|
||The following endpoint is used for content regulation.|TLSv1.2/HTTPS/HTTP|tsfe.trafficshaping.dsp.mp.microsoft.com|
|
||||||
|Xbox Live|The following endpoints are used for Xbox Live.|TLSv1.2/HTTPS/HTTP|dlassets-ssl.xboxlive.com|
|
|Xbox Live|The following endpoints are used for Xbox Live.|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|dlassets-ssl.xboxlive.com|
|
||||||
|||TLSv1.2/HTTPS|da.xboxservices.com|
|
|||TLSv1.2/HTTPS|da.xboxservices.com|
|
||||||
|||HTTPS|www.xboxab.com|
|
|||HTTPS|www.xboxab.com|
|
||||||
|
|
|
||||||
|
|
||||||
## Windows 11 Pro
|
## Windows 11 Pro
|
||||||
|
|
||||||
| **Area** | **Description** | **Protocol** | **Destination** |
|
| **Area** | **Description** | **Protocol** | **Destination** |
|
||||||
| --- | --- | --- | ---|
|
| --- | --- | --- | ---|
|
||||||
| Activity Feed Service |The following endpoints are used by Activity Feed Service, which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
|
||||||
|
| Activity Feed Service |The following endpoints are used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
||||||
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
||||||
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||||||
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||||||
@ -132,13 +137,16 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|Cortana and Live Tiles|The following endpoints are related to Cortana and Live Tiles|TLSv1.2/HTTPS/HTTP|www.bing.com*|
|
|Cortana and Live Tiles|The following endpoints are related to Cortana and Live Tiles|TLSv1.2/HTTPS/HTTP|www.bing.com*|
|
||||||
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
||||||
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. <br/>If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft. |TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
||||||
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
||||||
|Maps|The following endpoints are used to check for updates to maps that have been downloaded for offline use.|HTTPS/HTTP|maps.windows.com|
|
|Maps|The following endpoints are used to check for updates to maps that have been downloaded for offline use.|HTTPS/HTTP|maps.windows.com|
|
||||||
|Microsoft Account|The following endpoints are used for Microsoft accounts to sign in. |TLSv1.2/HTTPS/HTTP|*login.live.com|
|
|Microsoft Account|The following endpoints are used for Microsoft accounts to sign in|TLSv1.2/HTTPS/HTTP|*login.live.com|
|
||||||
|Microsoft Edge|The following endpoint is used by Microsoft Edge Update service to check for new updates. If you disable this endpoint, Microsoft Edge won’t be able to check for and apply new edge updates. |HTTPS/HTTP|msedge.api.cdp.microsoft.com|
|
|Microsoft Edge|The following endpoint is used by Microsoft Edge Update service to check for new updates.|HTTPS/HTTP|msedge.api.cdp.microsoft.com|
|
||||||
|
|Microsoft forward link redirection|The following endpoint is used by the Microsoft forward link redirection service (FWLink) to redirect permanent web links to their actual, sometimes transitory, URL. FWlinks are similar to URL shorteners, just longer|TLSv1.2/HTTPS/HTTP|go.microsoft.com|
|
||||||
|Microsoft Store|The following endpoint is used to download image files that are called when applications run (Microsoft Store or Inbox MSN Apps)|TLSv1.2/HTTPS/HTTP|img-prod-cms-rt-microsoft-com.akamaized.net|
|
|Microsoft Store|The following endpoint is used to download image files that are called when applications run (Microsoft Store or Inbox MSN Apps)|TLSv1.2/HTTPS/HTTP|img-prod-cms-rt-microsoft-com.akamaized.net|
|
||||||
||The following endpoint is used for the Windows Push Notification Services (WNS). WNS enables third-party developers to send toast, tile, badge, and raw updates from their own cloud service. This provides a mechanism to deliver new updates to your users in a power-efficient and dependable way.|TLSv1.2/HTTPS|*.wns.windows.com|
|
||The following endpoint is used for the Windows Push Notification Services (WNS). WNS enables third-party developers to send toast, tile, badge, and raw updates from their own cloud service. This provides a mechanism to deliver new updates to your users in a power-efficient and dependable way.|TLSv1.2/HTTPS|*.wns.windows.com|
|
||||||
||The following endpoint is used to revoke licenses for malicious apps in the Microsoft Store.|TLSv1.2/HTTPS/HTTP|storecatalogrevocation.storequality.microsoft.com|
|
||The following endpoint is used to revoke licenses for malicious apps in the Microsoft Store.|TLSv1.2/HTTPS/HTTP|storecatalogrevocation.storequality.microsoft.com|
|
||||||
@ -167,11 +175,13 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|Skype|The following endpoint is used to retrieve Skype configuration values.|TLSv1.2/HTTPS/HTTP|*.pipe.aria.microsoft.com|
|
|Skype|The following endpoint is used to retrieve Skype configuration values.|TLSv1.2/HTTPS/HTTP|*.pipe.aria.microsoft.com|
|
||||||
|||TLSv1.2/HTTPS/HTTP|config.edge.skype.com|
|
|||TLSv1.2/HTTPS/HTTP|config.edge.skype.com|
|
||||||
|Teams|The following endpoint is used for Microsoft Teams application.|TLSv1.2/HTTPS/HTTP|config.teams.microsoft.com|
|
|Teams|The following endpoint is used for Microsoft Teams application.|TLSv1.2/HTTPS/HTTP|config.teams.microsoft.com|
|
||||||
|Microsoft Defender Antivirus|The following endpoints are used for Windows Defender when Cloud-based Protection is enabled|TLSv1.2/HTTPS|wdcp.microsoft.com</br>wdcpalt.microsoft.com|
|
|Windows Defender|The following endpoint is used for Windows Defender when Cloud-based Protection is enabled|TLSv1.2/HTTPS|wdcp.microsoft.com|
|
||||||
|
||||wdcpalt.microsoft.com|
|
||||||
|||HTTPS/HTTP|*.smartscreen-prod.microsoft.com|
|
|||HTTPS/HTTP|*.smartscreen-prod.microsoft.com|
|
||||||
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications.|TLSv1.2|*.smartscreen.microsoft.com|
|
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications.|TLSv1.2|*.smartscreen.microsoft.com|
|
||||||
|||TLSv1.2/HTTP|checkappexec.microsoft.com|
|
|||TLSv1.2/HTTP|checkappexec.microsoft.com|
|
||||||
|Windows Spotlight|The following endpoints are used to retrieve Windows Spotlight metadata that describes content, such as references to image locations, as well as suggested apps, Microsoft account notifications, and Windows tips.|TLSv1.2/HTTPS/HTTP|arc.msn.com*</br>ris.api.iris.microsoft.com|
|
|Windows Spotlight|The following endpoints are used to retrieve Windows Spotlight metadata that describes content, such as references to image locations, as well as suggested apps, Microsoft account notifications, and Windows tips.|TLSv1.2/HTTPS/HTTP|arc.msn.com*|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|ris.api.iris.microsoft.com|
|
||||||
|Windows Update|The following endpoint is used for Windows Update downloads of apps and OS updates, including HTTP downloads or HTTP downloads blended with peers.|TLSv1.2/HTTPS/HTTP|*.prod.do.dsp.mp.microsoft.com|
|
|Windows Update|The following endpoint is used for Windows Update downloads of apps and OS updates, including HTTP downloads or HTTP downloads blended with peers.|TLSv1.2/HTTPS/HTTP|*.prod.do.dsp.mp.microsoft.com|
|
||||||
|||TLSv1.2/HTTP|emdl.ws.microsoft.com|
|
|||TLSv1.2/HTTP|emdl.ws.microsoft.com|
|
||||||
|||TLSv1.2/HTTPS/HTTP|*.dl.delivery.mp.microsoft.com|
|
|||TLSv1.2/HTTPS/HTTP|*.dl.delivery.mp.microsoft.com|
|
||||||
@ -180,17 +190,16 @@ The following methodology was used to derive the network endpoints:
|
|||||||
||The following endpoints enable connections to Windows Update, Microsoft Update, and the online services of the Store to help keep the device secure.|TLSv1.2/HTTPS/HTTP|*.update.microsoft.com|
|
||The following endpoints enable connections to Windows Update, Microsoft Update, and the online services of the Store to help keep the device secure.|TLSv1.2/HTTPS/HTTP|*.update.microsoft.com|
|
||||||
||The following endpoint is used for compatibility database updates for Windows.|HTTP/HTTPS|adl.windows.com|
|
||The following endpoint is used for compatibility database updates for Windows.|HTTP/HTTPS|adl.windows.com|
|
||||||
||The following endpoint is used for content regulation.|TLSv1.2/HTTPS/HTTP|tsfe.trafficshaping.dsp.mp.microsoft.com|
|
||The following endpoint is used for content regulation.|TLSv1.2/HTTPS/HTTP|tsfe.trafficshaping.dsp.mp.microsoft.com|
|
||||||
|Xbox Live|The following endpoints are used for Xbox Live.|TLSv1.2/HTTPS/HTTP|dlassets-ssl.xboxlive.com|
|
|Xbox Live|The following endpoints are used for Xbox Live.|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|dlassets-ssl.xboxlive.com|
|
||||||
|||TLSv1.2/HTTPS|da.xboxservices.com|
|
|||TLSv1.2/HTTPS|da.xboxservices.com|
|
||||||
|
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Windows 11 Education
|
## Windows 11 Education
|
||||||
|
|
||||||
| **Area** | **Description** | **Protocol** | **Destination** |
|
| **Area** | **Description** | **Protocol** | **Destination** |
|
||||||
| --- | --- | --- | ---|
|
| --- | --- | --- | ---|
|
||||||
| Activity Feed Service |The following endpoints are used by Activity Feed Service, which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
| Activity Feed Service |The following endpoints are used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
||||||
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
||||||
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||||||
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||||||
@ -201,14 +210,17 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|||TLSv1.2|odinvzc.azureedge.net|
|
|||TLSv1.2|odinvzc.azureedge.net|
|
||||||
|||TLSv1.2|b-ring.msedge.net|
|
|||TLSv1.2|b-ring.msedge.net|
|
||||||
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. <br/>If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
||||||
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
||||||
|Location|The following endpoints are used for location data.|TLSV1.2|inference.location.live.net|
|
|Location|The following endpoints are used for location data.|TLSV1.2|inference.location.live.net|
|
||||||
|Maps|The following endpoints are used to check for updates to maps that have been downloaded for offline use.|HTTPS/HTTP|maps.windows.com|
|
|Maps|The following endpoints are used to check for updates to maps that have been downloaded for offline use.|HTTPS/HTTP|maps.windows.com|
|
||||||
|Microsoft Account|The following endpoints are used for Microsoft accounts to sign in|TLSv1.2/HTTPS/HTTP|*login.live.com|
|
|Microsoft Account|The following endpoints are used for Microsoft accounts to sign in|TLSv1.2/HTTPS/HTTP|*login.live.com|
|
||||||
|Microsoft Edge|The following endpoint is used by Microsoft Edge Update service to check for new updates. If you disable this endpoint, Microsoft Edge won’t be able to check for and apply new edge updates.|HTTPS/HTTP|msedge.api.cdp.microsoft.com|
|
|Microsoft Edge|The following endpoint is used by Microsoft Edge Update service to check for new updates.|HTTPS/HTTP|msedge.api.cdp.microsoft.com|
|
||||||
|
|Microsoft forward link redirection|The following endpoint is used by the Microsoft forward link redirection service (FWLink) to redirect permanent web links to their actual, sometimes transitory, URL. FWlinks are similar to URL shorteners, just longer|TLSv1.2/HTTPS/HTTP|go.microsoft.com|
|
||||||
|Microsoft Store|The following endpoint is used to download image files that are called when applications run (Microsoft Store or Inbox MSN Apps)|TLSv1.2/HTTPS/HTTP|img-prod-cms-rt-microsoft-com.akamaized.net|
|
|Microsoft Store|The following endpoint is used to download image files that are called when applications run (Microsoft Store or Inbox MSN Apps)|TLSv1.2/HTTPS/HTTP|img-prod-cms-rt-microsoft-com.akamaized.net|
|
||||||
||The following endpoint is used for the Windows Push Notification Services (WNS). WNS enables third-party developers to send toast, tile, badge, and raw updates from their own cloud service. This provides a mechanism to deliver new updates to your users in a power-efficient and dependable way.|TLSv1.2/HTTPS|*.wns.windows.com|
|
||The following endpoint is used for the Windows Push Notification Services (WNS). WNS enables third-party developers to send toast, tile, badge, and raw updates from their own cloud service. This provides a mechanism to deliver new updates to your users in a power-efficient and dependable way.|TLSv1.2/HTTPS|*.wns.windows.com|
|
||||||
||The following endpoint is used to revoke licenses for malicious apps in the Microsoft Store.|TLSv1.2/HTTPS/HTTP|storecatalogrevocation.storequality.microsoft.com|
|
||The following endpoint is used to revoke licenses for malicious apps in the Microsoft Store.|TLSv1.2/HTTPS/HTTP|storecatalogrevocation.storequality.microsoft.com|
|
||||||
@ -229,11 +241,13 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|Skype|The following endpoint is used to retrieve Skype configuration values.|TLSv1.2/HTTPS/HTTP|*.pipe.aria.microsoft.com|
|
|Skype|The following endpoint is used to retrieve Skype configuration values.|TLSv1.2/HTTPS/HTTP|*.pipe.aria.microsoft.com|
|
||||||
|||TLSv1.2/HTTPS/HTTP|config.edge.skype.com|
|
|||TLSv1.2/HTTPS/HTTP|config.edge.skype.com|
|
||||||
|Teams|The following endpoint is used for Microsoft Teams application.|TLSv1.2/HTTPS/HTTP|config.teams.microsoft.com|
|
|Teams|The following endpoint is used for Microsoft Teams application.|TLSv1.2/HTTPS/HTTP|config.teams.microsoft.com|
|
||||||
|Microsoft Defender Antivirus|The following endpoints are used for Windows Defender when Cloud-based Protection is enabled|TLSv1.2/HTTPS|wdcp.microsoft.com</br>wdcpalt.microsoft.com|
|
|Windows Defender|The following endpoint is used for Windows Defender when Cloud-based Protection is enabled|TLSv1.2/HTTPS|wdcp.microsoft.com|
|
||||||
|
||||wdcpalt.microsoft.com|
|
||||||
|||HTTPS/HTTP|*.smartscreen-prod.microsoft.com|
|
|||HTTPS/HTTP|*.smartscreen-prod.microsoft.com|
|
||||||
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications.|TLSv1.2|*.smartscreen.microsoft.com|
|
||The following endpoints are used for Windows Defender SmartScreen reporting and notifications.|TLSv1.2|*.smartscreen.microsoft.com|
|
||||||
|||TLSv1.2/HTTP|checkappexec.microsoft.com|
|
|||TLSv1.2/HTTP|checkappexec.microsoft.com|
|
||||||
|Windows Spotlight|The following endpoints are used to retrieve Windows Spotlight metadata that describes content, such as references to image locations, as well as suggested apps, Microsoft account notifications, and Windows tips.|TLSv1.2/HTTPS/HTTP|arc.msn.com*</br>ris.api.iris.microsoft.com|
|
|Windows Spotlight|The following endpoints are used to retrieve Windows Spotlight metadata that describes content, such as references to image locations, as well as suggested apps, Microsoft account notifications, and Windows tips.|TLSv1.2/HTTPS/HTTP|arc.msn.com*|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|ris.api.iris.microsoft.com|
|
||||||
|Windows Update|The following endpoint is used for Windows Update downloads of apps and OS updates, including HTTP downloads or HTTP downloads blended with peers.|TLSv1.2/HTTPS/HTTP|*.prod.do.dsp.mp.microsoft.com|
|
|Windows Update|The following endpoint is used for Windows Update downloads of apps and OS updates, including HTTP downloads or HTTP downloads blended with peers.|TLSv1.2/HTTPS/HTTP|*.prod.do.dsp.mp.microsoft.com|
|
||||||
|||TLSv1.2/HTTP|emdl.ws.microsoft.com|
|
|||TLSv1.2/HTTP|emdl.ws.microsoft.com|
|
||||||
|||TLSv1.2/HTTPS/HTTP|*.dl.delivery.mp.microsoft.com|
|
|||TLSv1.2/HTTPS/HTTP|*.dl.delivery.mp.microsoft.com|
|
||||||
@ -242,5 +256,6 @@ The following methodology was used to derive the network endpoints:
|
|||||||
||The following endpoints enable connections to Windows Update, Microsoft Update, and the online services of the Store to help keep the device secure.|TLSv1.2/HTTPS/HTTP|*.update.microsoft.com|
|
||The following endpoints enable connections to Windows Update, Microsoft Update, and the online services of the Store to help keep the device secure.|TLSv1.2/HTTPS/HTTP|*.update.microsoft.com|
|
||||||
||The following endpoint is used for compatibility database updates for Windows.|HTTP/HTTPS|adl.windows.com|
|
||The following endpoint is used for compatibility database updates for Windows.|HTTP/HTTPS|adl.windows.com|
|
||||||
||The following endpoint is used for content regulation.|TLSv1.2/HTTPS/HTTP|tsfe.trafficshaping.dsp.mp.microsoft.com|
|
||The following endpoint is used for content regulation.|TLSv1.2/HTTPS/HTTP|tsfe.trafficshaping.dsp.mp.microsoft.com|
|
||||||
|Xbox Live|The following endpoints are used for Xbox Live.|TLSv1.2/HTTPS/HTTP|dlassets-ssl.xboxlive.com|
|
|Xbox Live|The following endpoints are used for Xbox Live.|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|dlassets-ssl.xboxlive.com|
|
||||||
|||TLSv1.2/HTTPS|da.xboxservices.com|
|
|||TLSv1.2/HTTPS|da.xboxservices.com|
|
||||||
|
@ -33,7 +33,7 @@ The following methodology was used to derive the network endpoints:
|
|||||||
5. The test virtual machine(s) was logged into using a local account, and was not joined to a domain or Azure Active Directory.
|
5. The test virtual machine(s) was logged into using a local account, and was not joined to a domain or Azure Active Directory.
|
||||||
6. All traffic was captured in our lab using a IPV4 network. Therefore, no IPV6 traffic is reported here.
|
6. All traffic was captured in our lab using a IPV4 network. Therefore, no IPV6 traffic is reported here.
|
||||||
7. These tests were conducted in an approved Microsoft lab. It's possible your results may be different.
|
7. These tests were conducted in an approved Microsoft lab. It's possible your results may be different.
|
||||||
8. These tests were conducted for one week. If you capture traffic for longer, you may have different results.
|
8. These tests were conducted for one week. If you capture traffic for longer you may have different results.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
|
> Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
|
||||||
@ -42,7 +42,7 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|
|
||||||
| **Area** | **Description** | **Protocol** | **Destination** |
|
| **Area** | **Description** | **Protocol** | **Destination** |
|
||||||
|-----------|--------------- |------------- |-----------------|
|
|-----------|--------------- |------------- |-----------------|
|
||||||
| Activity Feed Service |The following endpoints are used by Activity Feed Service, which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
| Activity Feed Service |The following endpoints are used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
||||||
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
||||||
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||||||
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||||||
@ -55,7 +55,9 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
||||||
|Device Directory Service|Used by Device Directory Service to keep track of user-device associations and storing metadata about the devices.|HTTPS/HTTP|cs.dds.microsoft.com|
|
|Device Directory Service|Used by Device Directory Service to keep track of user-device associations and storing metadata about the devices.|HTTPS/HTTP|cs.dds.microsoft.com|
|
||||||
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. <br/>If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
||||||
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
||||||
@ -131,7 +133,7 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|
|
||||||
| **Area** | **Description** | **Protocol** | **Destination** |
|
| **Area** | **Description** | **Protocol** | **Destination** |
|
||||||
| --- | --- | --- | ---|
|
| --- | --- | --- | ---|
|
||||||
| Activity Feed Service |The following endpoints are used by Activity Feed Service, which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
| Activity Feed Service |The following endpoints are used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
||||||
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
||||||
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||||||
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||||||
@ -140,7 +142,9 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|Cortana and Live Tiles|The following endpoints are related to Cortana and Live Tiles|TLSv1.2/HTTPS/HTTP|www.bing.com*|
|
|Cortana and Live Tiles|The following endpoints are related to Cortana and Live Tiles|TLSv1.2/HTTPS/HTTP|www.bing.com*|
|
||||||
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
|Device authentication|The following endpoint is used to authenticate a device.|HTTPS|login.live.com*|
|
||||||
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. <br/>If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
||||||
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
||||||
@ -200,7 +204,7 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|
|
||||||
| **Area** | **Description** | **Protocol** | **Destination** |
|
| **Area** | **Description** | **Protocol** | **Destination** |
|
||||||
| --- | --- | --- | ---|
|
| --- | --- | --- | ---|
|
||||||
| Activity Feed Service |The following endpoints are used by Activity Feed Service, which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
| Activity Feed Service |The following endpoints are used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows|TLSv1.2/HTTPS/HTTP|activity.windows.com|
|
||||||
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
|Apps|The following endpoints are used for the Weather app.|TLSv1.2/HTTPS/HTTP|tile-service.weather.microsoft.com|
|
||||||
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||The following endpoint is used by the Photos app to download configuration files, and to connect to the Office 365 portal's shared infrastructure, including Office in a browser.|TLSv1.2/HTTPS/HTTP|evoke-windowsservices-tas.msedge.net|
|
||||||
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||The following endpoint is used for OneNote Live Tile.|HTTPS/HTTP|cdn.onenote.net|
|
||||||
@ -211,7 +215,9 @@ The following methodology was used to derive the network endpoints:
|
|||||||
|||TLSv1.2|odinvzc.azureedge.net|
|
|||TLSv1.2|odinvzc.azureedge.net|
|
||||||
|||TLSv1.2|b-ring.msedge.net|
|
|||TLSv1.2|b-ring.msedge.net|
|
||||||
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
|Device metadata|The following endpoint is used to retrieve device metadata.|TLSv1.2/HTTP|dmd.metaservices.microsoft.com|
|
||||||
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service. <br/>If you turn off traffic for this endpoint, diagnostic and usage information, which helps Microsoft find and fix problems and improve our products and services, will not be sent back to Microsoft.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
|Diagnostic data|The following endpoints are used by the Connected User Experiences and Telemetry component and connects to the Microsoft Data Management service.|TLSv1.2/HTTP|v10.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTPS/HTTP|v20.events.data.microsoft.com|
|
||||||
|
|||TLSv1.2/HTTP|www.microsoft.com|
|
||||||
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||The following endpoints are used by Windows Error Reporting.|TLSv1.2/HTTPS/HTTP|watson.telemetry.microsoft.com|
|
||||||
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
|Font Streaming|The following endpoints are used to download fonts on demand.|TLSv1.2/HTTPS|fs.microsoft.com*|
|
||||||
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
|Licensing|The following endpoint is used for online activation and some app licensing.|HTTPS/HTTP|*licensing.mp.microsoft.com|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
### YamlMime:Landing
|
### YamlMime:Landing
|
||||||
|
|
||||||
title: Windows security # < 60 chars
|
title: Windows security # < 60 chars
|
||||||
summary: Windows is a Zero Trust-ready operating system that provides security from chip to cloud. # < 160 chars
|
summary: Built with Zero Trust principles at the core to safeguard data and access anywhere, keeping you protected and productive. # < 160 chars
|
||||||
|
|
||||||
metadata:
|
metadata:
|
||||||
title: Windows security # Required; page title displayed in search results. Include the brand. < 60 chars.
|
title: Windows security # Required; page title displayed in search results. Include the brand. < 60 chars.
|
||||||
|
@ -19,6 +19,8 @@ ms.date: 09/21/2021
|
|||||||
|
|
||||||
Security and privacy depend on an operating system that guards your system and information from the moment it starts up, providing fundamental chip-to-cloud protection. Windows 11 is the most secure Windows yet with extensive security measures designed to help keep you safe. These measures include built-in advanced encryption and data protection, robust network and system security, and intelligent safeguards against ever-evolving threats.
|
Security and privacy depend on an operating system that guards your system and information from the moment it starts up, providing fundamental chip-to-cloud protection. Windows 11 is the most secure Windows yet with extensive security measures designed to help keep you safe. These measures include built-in advanced encryption and data protection, robust network and system security, and intelligent safeguards against ever-evolving threats.
|
||||||
|
|
||||||
|
Watch the latest [Microsoft Mechanics Windows 11 security](https://youtu.be/tg9QUrnVFho) video that shows off some of the latest Windows 11 security technology.
|
||||||
|
|
||||||
Use the links in the following table to learn more about the operating system security features and capabilities in Windows 11.<br/><br/>
|
Use the links in the following table to learn more about the operating system security features and capabilities in Windows 11.<br/><br/>
|
||||||
|
|
||||||
| Security Measures | Features & Capabilities |
|
| Security Measures | Features & Capabilities |
|
||||||
|
@ -1,83 +0,0 @@
|
|||||||
---
|
|
||||||
title: Windows security baselines
|
|
||||||
description: Learn how to use Windows security baselines in your organization. Specific to Windows 10, Windows Server, and Microsoft 365 Apps for enterprise.
|
|
||||||
keywords: virtualization, security, malware
|
|
||||||
ms.prod: m365-security
|
|
||||||
ms.mktglfcycl: deploy
|
|
||||||
ms.localizationpriority: medium
|
|
||||||
ms.author: dansimp
|
|
||||||
author: dulcemontemayor
|
|
||||||
manager: dansimp
|
|
||||||
audience: ITPro
|
|
||||||
ms.collection: M365-security-compliance
|
|
||||||
ms.topic: conceptual
|
|
||||||
ms.date: 06/25/2018
|
|
||||||
ms.reviewer:
|
|
||||||
ms.technology: mde
|
|
||||||
---
|
|
||||||
|
|
||||||
# Windows security baselines
|
|
||||||
|
|
||||||
**Applies to**
|
|
||||||
|
|
||||||
- Windows 10
|
|
||||||
- Windows Server
|
|
||||||
- Microsoft 365 Apps for enterprise
|
|
||||||
- Microsoft Edge
|
|
||||||
|
|
||||||
## Using security baselines in your organization
|
|
||||||
|
|
||||||
Microsoft is dedicated to providing its customers with secure operating systems, such as Windows 10 and Windows Server, and secure apps, such as Microsoft Edge. In addition to the security assurance of its products, Microsoft also enables you to have fine control over your environments by providing various configuration capabilities.
|
|
||||||
|
|
||||||
Even though Windows and Windows Server are designed to be secure out-of-the-box, many organizations still want more granular control over their security configurations. To navigate the large number of controls, organizations need guidance on configuring various security features. Microsoft provides this guidance in the form of security baselines.
|
|
||||||
|
|
||||||
We recommend that you implement an industry-standard configuration that is broadly known and well-tested, such as Microsoft security baselines, as opposed to creating a baseline yourself. This helps increase flexibility and reduce costs.
|
|
||||||
|
|
||||||
Here is a good blog about [Sticking with Well-Known and Proven Solutions](/archive/blogs/fdcc/sticking-with-well-known-and-proven-solutions).
|
|
||||||
|
|
||||||
## What are security baselines?
|
|
||||||
|
|
||||||
Every organization faces security threats. However, the types of security threats that are of most concern to one organization can be completely different from another organization. For example, an e-commerce company may focus on protecting its Internet-facing web apps, while a hospital may focus on protecting confidential patient information. The one thing that all organizations have in common is a need to keep their apps and devices secure. These devices must be compliant with the security standards (or security baselines) defined by the organization.
|
|
||||||
|
|
||||||
A security baseline is a group of Microsoft-recommended configuration settings that explains their security impact. These settings are based on feedback from Microsoft security engineering teams, product groups, partners, and customers.
|
|
||||||
|
|
||||||
## Why are security baselines needed?
|
|
||||||
|
|
||||||
Security baselines are an essential benefit to customers because they bring together expert knowledge from Microsoft, partners, and customers.
|
|
||||||
|
|
||||||
For example, there are over 3,000 Group Policy settings for Windows 10, which does not include over 1,800 Internet Explorer 11 settings. Of these 4,800 settings, only some are security-related. Although Microsoft provides extensive guidance on different security features, exploring each one can take a long time. You would have to determine the security impact of each setting on your own. Then, you would still need to determine the appropriate value for each setting.
|
|
||||||
|
|
||||||
In modern organizations, the security threat landscape is constantly evolving, and IT pros and policy-makers must keep up with security threats and make required changes to Windows security settings to help mitigate these threats. To enable faster deployments and make managing Windows easier, Microsoft provides customers with security baselines that are available in consumable formats, such as Group Policy Objects Backups.
|
|
||||||
|
|
||||||
## How can you use security baselines?
|
|
||||||
|
|
||||||
You can use security baselines to:
|
|
||||||
- Ensure that user and device configuration settings are compliant with the baseline.
|
|
||||||
- Set configuration settings. For example, you can use Group Policy, Microsoft Endpoint Configuration Manager, or Microsoft Intune to configure a device with the setting values specified in the baseline.
|
|
||||||
|
|
||||||
## Where can I get the security baselines?
|
|
||||||
|
|
||||||
You can download the security baselines from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=55319). This download page is for the Security Compliance Toolkit (SCT), which comprises tools that can assist admins in managing baselines in addition to the security baselines.
|
|
||||||
|
|
||||||
The security baselines are included in the [Security Compliance Toolkit (SCT)](security-compliance-toolkit-10.md), which can be downloaded from the Microsoft Download Center. The SCT also includes tools to help admins manage the security baselines.
|
|
||||||
|
|
||||||
[](security-compliance-toolkit-10.md)
|
|
||||||
[](get-support-for-security-baselines.md)
|
|
||||||
|
|
||||||
## Community
|
|
||||||
|
|
||||||
[](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/bd-p/Security-Baselines)
|
|
||||||
|
|
||||||
## Related Videos
|
|
||||||
|
|
||||||
You may also be interested in this msdn channel 9 video:
|
|
||||||
- [Defrag Tools](https://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-174-Security-Baseline-Policy-Analyzer-and-LGPO)
|
|
||||||
|
|
||||||
## See Also
|
|
||||||
|
|
||||||
- [Microsoft Endpoint Configuration Manager](https://www.microsoft.com/cloud-platform/system-center-configuration-manager)
|
|
||||||
- [Operations Management Suite](https://www.microsoft.com/cloud-platform/operations-management-suite)
|
|
||||||
- [Configuration Management for Nano Server](/archive/blogs/grouppolicy/configuration-management-on-servers/)
|
|
||||||
- [Microsoft Security Guidance Blog](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/bg-p/Microsoft-Security-Baselines)
|
|
||||||
- [Microsoft Security Compliance Toolkit Download](https://www.microsoft.com/download/details.aspx?id=55319)
|
|
||||||
- [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=55319)
|
|
@ -3,8 +3,8 @@
|
|||||||
- name: Windows 11
|
- name: Windows 11
|
||||||
expanded: true
|
expanded: true
|
||||||
items:
|
items:
|
||||||
- name: Windows 11 overview
|
- name: What's new in Windows 11
|
||||||
href: windows-11.md
|
href: windows-11-whats-new.md
|
||||||
- name: Windows 11 requirements
|
- name: Windows 11 requirements
|
||||||
href: windows-11-requirements.md
|
href: windows-11-requirements.md
|
||||||
- name: Plan for Windows 11
|
- name: Plan for Windows 11
|
||||||
|
After Width: | Height: | Size: 3.3 KiB |
After Width: | Height: | Size: 10 KiB |
After Width: | Height: | Size: 75 KiB |
After Width: | Height: | Size: 10 KiB |
After Width: | Height: | Size: 11 KiB |
After Width: | Height: | Size: 9.9 KiB |
@ -27,8 +27,8 @@ landingContent:
|
|||||||
linkLists:
|
linkLists:
|
||||||
- linkListType: overview
|
- linkListType: overview
|
||||||
links:
|
links:
|
||||||
- text: Windows 11 overview
|
- text: What's new
|
||||||
url: windows-11.md
|
url: windows-11-whats-new.md
|
||||||
- text: Windows 11 requirements
|
- text: Windows 11 requirements
|
||||||
url: windows-11-requirements.md
|
url: windows-11-requirements.md
|
||||||
- text: Plan for Windows 11
|
- text: Plan for Windows 11
|
||||||
|
@ -2,7 +2,7 @@
|
|||||||
title: Windows 11 requirements
|
title: Windows 11 requirements
|
||||||
description: Hardware requirements to deploy Windows 11
|
description: Hardware requirements to deploy Windows 11
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: dougeby
|
||||||
ms.audience: itpro
|
ms.audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.author: greglin
|
ms.author: greglin
|
||||||
@ -21,7 +21,7 @@ ms.custom: seo-marvel-apr2020
|
|||||||
|
|
||||||
- Windows 11
|
- Windows 11
|
||||||
|
|
||||||
This article lists the system requirements for Windows 11. Windows 11 is also supported on a virtual machine (VM).
|
This article lists the system requirements for Windows 11. Windows 11 is also [supported on a virtual machine (VM)](#virtual-machine-support).
|
||||||
|
|
||||||
## Hardware requirements
|
## Hardware requirements
|
||||||
|
|
||||||
@ -80,6 +80,22 @@ Some features in Windows 11 have requirements beyond those listed above. See the
|
|||||||
- **Windows Projection**: requires a display adapter that supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct.
|
- **Windows Projection**: requires a display adapter that supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct.
|
||||||
- **Xbox app**: requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active [Xbox Game Pass](https://www.xbox.com/xbox-game-pass) subscription.
|
- **Xbox app**: requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active [Xbox Game Pass](https://www.xbox.com/xbox-game-pass) subscription.
|
||||||
|
|
||||||
|
## Virtual machine support
|
||||||
|
|
||||||
|
The following configuration requirements apply to VMs running Windows 11.
|
||||||
|
|
||||||
|
- Generation: 2<b> \*</b>
|
||||||
|
- Storage: 64 GB or greater
|
||||||
|
- Security: Secure Boot capable, virtual TPM enabled
|
||||||
|
- Memory: 4 GB or greater
|
||||||
|
- Processor: 2 or more virtual processors
|
||||||
|
|
||||||
|
The VM host CPU must also meet Windows 11 [processor requirements](/windows-hardware/design/minimum/windows-processor-requirements).
|
||||||
|
|
||||||
|
<b>\*</b> In-place upgrade of existing generation 1 VMs to Windows 11 is not possible.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> Procedures to configure required VM settings depend on the VM host type. For VM hosts running Hyper-V, virtualization (VT-x, VT-d) must be enabled in BIOS. Virtual TPM 2.0 is emulated in the guest VM independent of the Hyper-V host TPM presence or version.
|
||||||
|
|
||||||
## Next steps
|
## Next steps
|
||||||
|
|
||||||
@ -89,5 +105,5 @@ Some features in Windows 11 have requirements beyond those listed above. See the
|
|||||||
## See also
|
## See also
|
||||||
|
|
||||||
[Windows minimum hardware requirements](/windows-hardware/design/minimum/minimum-hardware-requirements-overview)<br>
|
[Windows minimum hardware requirements](/windows-hardware/design/minimum/minimum-hardware-requirements-overview)<br>
|
||||||
[Windows 11 overview](windows-11.md)
|
[What's new in Windows 11 overview](windows-11-whats-new.md)
|
||||||
|
|
||||||
|
210
windows/whats-new/windows-11-whats-new.md
Normal file
@ -0,0 +1,210 @@
|
|||||||
|
---
|
||||||
|
title: Windows 11, what's new and overview for administrators
|
||||||
|
description: Learn more about what's new in Windows 11. Read about see the features IT professionals and administrators should know about Windows 11, including security, using apps, the new desktop, and deploying and servicing PCs.
|
||||||
|
ms.reviewer:
|
||||||
|
manager: dougeby
|
||||||
|
ms.audience: itpro
|
||||||
|
author: MandiOhlinger
|
||||||
|
ms.author: mandia
|
||||||
|
ms.prod: w10
|
||||||
|
ms.mktglfcycl: deploy
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.localizationpriority: medium
|
||||||
|
audience: itpro
|
||||||
|
ms.topic: article
|
||||||
|
ms.custom:
|
||||||
|
---
|
||||||
|
|
||||||
|
# What's new in Windows 11
|
||||||
|
|
||||||
|
**Applies to**:
|
||||||
|
|
||||||
|
- Windows 11
|
||||||
|
|
||||||
|
Windows 11 is the next client operating system, and includes features that organizations should know. Windows 11 is built on the same foundation as Windows 10. If you use Windows 10, then Windows 11 is a natural transition and update to what you know, and what you're familiar with.
|
||||||
|
|
||||||
|
It offers innovations focused on enhancing end-user productivity, and is designed to support today's hybrid work environment.
|
||||||
|
|
||||||
|
Your investments in update and device management are carried forward. For example, many of the same apps and tools can be used in Windows 11. Many of the same security settings and policies can be applied to Windows 11 devices, including PCs. You can use Windows Autopilot with a zero touch deployment to enroll your Windows devices in Microsoft Endpoint Manager. You can also use newer features, such as Azure Virtual Desktop and Windows 365 on your Windows 11 devices.
|
||||||
|
|
||||||
|
This article lists what's new, and some of the features & improvements. For more information on what's new for OEMs, see [What's new in manufacturing, customization, and design](/windows-hardware/get-started/what-s-new-in-windows).
|
||||||
|
|
||||||
|
## Security and scanning
|
||||||
|
|
||||||
|
The security and privacy features in Windows 11 are similar to Windows 10. Security for your devices starts with the hardware, and includes OS security, application security, and user & identity security. There are features available in the Windows OS to help in these areas. This section describes some of these features. For a more comprehensive view, including zero trust, see [Windows security](/windows/security/).
|
||||||
|
|
||||||
|
- The **Windows Security** app is built into the OS. This app is an easy-to-use interface, and combines commonly used security features. For example, your get access to virus & threat protection, firewall & network protection, account protection, and more.
|
||||||
|
|
||||||
|
For more information, see [the Windows Security app](/windows/security/threat-protection/windows-defender-security-center/windows-defender-security-center).
|
||||||
|
|
||||||
|
- **Security baselines** includes security settings that already configured, and ready to be deployed to your devices. If you don't know where to start, or it's too time consuming to go through all the settings, then you should look at Security Baselines.
|
||||||
|
|
||||||
|
For more information, see [Windows security baselines](/windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines).
|
||||||
|
|
||||||
|
- **Microsoft Defender Antivirus** is built into Windows, and helps protect devices using next-generation security. When used with Microsoft Defender for Endpoint, your organization gets strong endpoint protection, and advanced endpoint protection & response. If your devices are managed with Endpoint Manager, you can create policies based on threat levels found in Microsoft Defender for Endpoint.
|
||||||
|
|
||||||
|
For more information, see:
|
||||||
|
|
||||||
|
- [Microsoft Defender Antivirus](/microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-windows)
|
||||||
|
- [Microsoft Defender for Endpoint](/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint)
|
||||||
|
- [Enforce compliance for Microsoft Defender for Endpoint](/mem/intune/protect/advanced-threat-protection)
|
||||||
|
|
||||||
|
- The Application Security features help prevent unwanted or malicious code from running, isolate untrusted websites & untrusted Office files, protect against phishing or malware websites, and more.
|
||||||
|
|
||||||
|
For more information, see [Windows application security](/windows/security/apps).
|
||||||
|
|
||||||
|
- **Windows Hello for Business** helps protect users and identities. It replaces passwords, and uses a PIN or biometric that stays locally on the device. Device manufacturers are including more secure hardware features, such as IR cameras and TPM chips. These features are used with Windows Hello for Business to help protect user identities on your organization devices.
|
||||||
|
|
||||||
|
As an admin, going passwordless help secures user identities. The Windows OS, Azure AD, and Endpoint Manager work together to remove passwords, create more secure policies, and help enforce compliance.
|
||||||
|
|
||||||
|
For more information, see:
|
||||||
|
|
||||||
|
- [Windows Hello for Business Overview](/windows/security/identity-protection/hello-for-business/hello-overview)
|
||||||
|
- [Trusted Platform Module Technology Overview](/windows/security/information-protection/tpm/trusted-platform-module-overview)
|
||||||
|
- [Integrate Windows Hello for Business with Endpoint Manager](/mem/intune/protect/windows-hello)
|
||||||
|
|
||||||
|
For more information on the security features you can configure, manage, and enforce using Endpoint Manager, see [Protect data and devices with Microsoft Endpoint Manager](/mem/intune/protect/device-protect).
|
||||||
|
|
||||||
|
## Easier access to new services, and services you already use
|
||||||
|
|
||||||
|
- **Windows 365** is a desktop operating system that's also a cloud service. From another internet-connected device, including Android and macOS devices, you can run Windows 365, just like a virtual machine.
|
||||||
|
|
||||||
|
For more information, see [What is Windows 365 Enterprise?](/windows-365/overview).
|
||||||
|
|
||||||
|
- **Microsoft Teams** is included with the OS, and is automatically available on the taskbar. Users select the chat icon, sign in with their personal Microsoft account, and start a call:
|
||||||
|
|
||||||
|
:::image type="content" source="./images/windows-11-whats-new/windows-11-taskbar-microsoft-teams.png" alt-text="On the Windows 11 taskbar, select the camera chat icon to start a Microsoft Teams call.":::
|
||||||
|
|
||||||
|
This version of Microsoft Teams is for personal accounts. For organization accounts, such as `user@contoso.com`, you can deploy the Microsoft Teams app using MDM policy, such as Endpoint Manager. For more information, see:
|
||||||
|
|
||||||
|
- [Get started with Microsoft Endpoint Manager](/mem/endpoint-manager-getting-started)
|
||||||
|
- [Add Microsoft 365 apps to Windows 10 devices with Microsoft Intune](/mem/intune/apps/apps-add-office365)
|
||||||
|
- [Install Microsoft Teams using Microsoft Endpoint Configuration Manager](/microsoftteams/msi-deployment)
|
||||||
|
|
||||||
|
Users can manage preinstalled apps using the **Settings** app > **Apps** > **Apps & Features**. Admins can [create a policy that pins apps, or removes the default pinned apps from the Taskbar](/windows/configuration/customize-taskbar-windows-11).
|
||||||
|
|
||||||
|
- **Power Automate for desktop** is included with the OS. Your users can create flows with this low-code app to help them with everyday tasks. For example, users can create flows that save a message to OneNote, notify a team when there's a new Forms response, get notified when a file is added to SharePoint, and more.
|
||||||
|
|
||||||
|
For more information, see [Getting started with Power Automate in Windows 11](/power-automate/desktop-flows/getting-started-windows-11).
|
||||||
|
|
||||||
|
Users can manage preinstalled apps using the **Settings** app > **Apps** > **Apps & Features**.
|
||||||
|
|
||||||
|
## Customize the desktop experience
|
||||||
|
|
||||||
|
- **Snap Layouts, Snap Groups**: When you open an app, hover your mouse over the minimize/maximize option. When you do, you can select a different layout for the app:
|
||||||
|
|
||||||
|
:::image type="content" source="./images/windows-11-whats-new/windows-11-snap-layouts.png" alt-text="In Windows 11, use the minimize or maximize button on an app to see the available snap layouts.":::
|
||||||
|
|
||||||
|
This feature allows users to customize the sizes of apps on their desktop. And, when you add other apps to the layout, the snapped layout stays in place.
|
||||||
|
|
||||||
|
When you add your apps in a Snap Layout, that layout is saved in a Snap Group. In the taskbar, when you hover over an app in an existing snap layout, it shows all the apps in that layout. This feature is the Snap Group. You can select the group, and the apps are opened in the same layout. As you add more Snap Groups, you can switch between them just by selecting the Snap Group.
|
||||||
|
|
||||||
|
Users can manage some snap features using the **Settings** app > **System** > **Multitasking**. For more information on the end-user experience, see [Snap your windows](https://support.microsoft.com/windows/snap-your-windows-885a9b1e-a983-a3b1-16cd-c531795e6241).
|
||||||
|
|
||||||
|
You can also add Snap Layouts to apps your organization creates. For more information, see [Support snap layouts for desktop apps on Windows 11](/windows/apps/desktop/modernize/apply-snap-layout-menu).
|
||||||
|
|
||||||
|
- **Start menu**: The Start menu includes some apps that are pinned by default. You can customize the Start menu layout by pinning (and unpinning) the apps you want. For example, you can pin commonly used apps in your organization, such as Outlook, Microsoft Teams, apps your organization creates, and more.
|
||||||
|
|
||||||
|
Using policy, you can deploy your customized Start menu layout to devices in your organization. For more information, see [Customize the Start menu layout on Windows 11](/windows/configuration/customize-start-menu-layout-windows-11).
|
||||||
|
|
||||||
|
Users can manage some Start menu features using the **Settings** app > **Personalization**. For more information on the end-user experience, see [See what's on the Start menu](https://support.microsoft.com/windows/see-what-s-on-the-start-menu-a8ccb400-ad49-962b-d2b1-93f453785a13).
|
||||||
|
|
||||||
|
- **Taskbar**: You can also pin (and unpin) apps on the Taskbar. For example, you can pin commonly used apps in your organization, such as Outlook, Microsoft Teams, apps your organization creates, and more.
|
||||||
|
|
||||||
|
Using policy, you can deploy your customized Taskbar to devices in your organization. For more information, see [Customize the Taskbar on Windows 11](/windows/configuration/customize-taskbar-windows-11).
|
||||||
|
|
||||||
|
Users can manage some Taskbar features using the **Settings** app > **Personalization**. For more information on the end-user experience, see:
|
||||||
|
|
||||||
|
- [Customize the taskbar notification area](https://support.microsoft.com/windows/customize-the-taskbar-notification-area-e159e8d2-9ac5-b2bd-61c5-bb63c1d437c3)
|
||||||
|
- [Pin apps and folders to the desktop or taskbar](https://support.microsoft.com/windows/pin-apps-and-folders-to-the-desktop-or-taskbar-f3c749fb-e298-4cf1-adda-7fd635df6bb0)
|
||||||
|
|
||||||
|
- **Widgets**: Widgets are available on the Taskbar. It includes a personalized feed that could be weather, calendar, stock prices, news, and more:
|
||||||
|
|
||||||
|
:::image type="content" source="./images/windows-11-whats-new/windows-11-taskbar-widgets.png" alt-text="On the Windows 11 taskbar, select the widgets icon to open and see the available widgets.":::
|
||||||
|
|
||||||
|
You can enable/disable this feature using the `Computer Configuration\Administrative Templates\Windows Components\widgets` Group Policy. You can also deploy a customized Taskbar to devices in your organization. For more information, see [Customize the Taskbar on Windows 11](/windows/configuration/customize-taskbar-windows-11).
|
||||||
|
|
||||||
|
For information on the end-user experience, see [Stay up to date with widgets](https://support.microsoft.com/windows/stay-up-to-date-with-widgets-7ba79aaa-dac6-4687-b460-ad16a06be6e4).
|
||||||
|
|
||||||
|
- **Virtual desktops**: On the Taskbar, you can select the Desktops icon to create a new desktop:
|
||||||
|
|
||||||
|
:::image type="content" source="./images/windows-11-whats-new/windows-11-taskbar-virtual-desktops.png" alt-text="On the Windows 11 taskbar, select the desktop icon to create many virtual desktops.":::
|
||||||
|
|
||||||
|
Use the desktop to open different apps depending on what you're doing. For example, you can create a Travel desktop that includes web sites and apps that are focused on travel.
|
||||||
|
|
||||||
|
Using policy, you can deploy a customized Taskbar to devices in your organization. For more information, see [Customize the Taskbar on Windows 11](/windows/configuration/customize-taskbar-windows-11).
|
||||||
|
|
||||||
|
Users can manage some desktop features using **Settings** app > **System** > **Multitasking**. For more information on the end-user experience, see [Multiple desktops in Windows](https://support.microsoft.com/windows/multiple-desktops-in-windows-11-36f52e38-5b4a-557b-2ff9-e1a60c976434).
|
||||||
|
|
||||||
|
## Use your same apps, improved
|
||||||
|
|
||||||
|
- Your Windows 10 apps will also work on Windows 11. **[App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure)** is also available if there are some issues.
|
||||||
|
|
||||||
|
You can continue to use **MSIX packages** for your UWP, Win32, WPF, and WinForm desktop application files. Continue to use **Windows Package Manager** to install Windows apps. Use **Azure Virtual desktop with MSIX app attach** to virtualize desktops and apps. For more information on these features, see [Overview of apps on Windows client devices](/windows/application-management/apps-in-windows-10).
|
||||||
|
|
||||||
|
In the **Settings** app > **Apps**, users can manage some of the app settings. For example, they can get apps anywhere, but let the user know if there's a comparable app in the Microsoft Store. They can also choose which apps start when they sign in.
|
||||||
|
|
||||||
|
Using an MDM provider, like Endpoint Manager, you can create policies that also manage some app settings. For a list of settings, see [App Store in Endpoint Manager](/mem/intune/configuration/device-restrictions-windows-10#app-store).
|
||||||
|
|
||||||
|
- If you manage devices using Endpoint Manager, then you might be familiar with the **Company Portal app**. Starting with Windows 11, the Company Portal is your private app repository for your organization apps. For more information, see [Private app repository in Windows 11](/windows/application-management/private-app-repository-mdm-company-portal-windows-11).
|
||||||
|
|
||||||
|
For public and retail apps, continue using the Microsoft Store.
|
||||||
|
|
||||||
|
- **Windows Terminal app**: This app is included with the OS. On previous Windows versions, it's a separate download in the Microsoft Store. For more information, see [What is Windows Terminal?](/windows/terminal/).
|
||||||
|
|
||||||
|
This app combines Windows PowerShell, a command prompt, and Azure Cloud Shell all within the same terminal window. You don't need to open separate apps to use these command-line applications. It has tabs. And when you open a new tab, you can choose your command-line application:
|
||||||
|
|
||||||
|
:::image type="content" source="./images/windows-11-whats-new/windows-terminal-app.png" alt-text="On Windows 11, open the Windows Terminal app to use Windows PowerShell, the command prompt, or Azure Cloud Shell to run commands.":::
|
||||||
|
|
||||||
|
If users or groups in your organization do a lot with Windows PowerShell or the command prompt, then use policy to add the Windows Terminal app to the [Start menu layout](/windows/configuration/customize-start-menu-layout-windows-11) or the [Taskbar](/windows/configuration/customize-taskbar-windows-11).
|
||||||
|
|
||||||
|
Users can also search for the Terminal app, right-select the app, and pin the app to the Start menu and taskbar.
|
||||||
|
|
||||||
|
- The **Microsoft Store** has a new look, and includes more public and retail apps. For more information on the end-user experience, see:
|
||||||
|
|
||||||
|
- [Get updates for apps and games in Microsoft Store](https://support.microsoft.com/account-billing/get-updates-for-apps-and-games-in-microsoft-store-a1fe19c0-532d-ec47-7035-d1c5a1dd464f)
|
||||||
|
- [How to open Microsoft Store on Windows](https://support.microsoft.com/account-billing/how-to-open-microsoft-store-on-windows-10-e080b85a-7c9e-46a7-8d8b-3e9a42e32de6)
|
||||||
|
|
||||||
|
- The **Microsoft Edge** browser is included with the OS, and is the default browser. Internet Explorer (IE) isn't available in Windows 11. In Microsoft Edge, you can use IE Mode if a website needs Internet Explorer. Open Microsoft Edge, and enter `edge://settings/defaultBrowser` in the URL.
|
||||||
|
|
||||||
|
To save system resources, Microsoft Edge uses sleeping tabs. Users can configure these settings, and more, in `edge://settings/system`.
|
||||||
|
|
||||||
|
Using Group Policy or an MDM provider, such as Endpoint Manager, you can configure some Microsoft Edge settings. For more information, see [Microsoft Edge - Policies](/deployedge/microsoft-edge-policies) and [Configure Microsoft Edge policy settings](/mem/intune/configuration/administrative-templates-configure-edge).
|
||||||
|
|
||||||
|
## Deployment and servicing
|
||||||
|
|
||||||
|
- **Install Windows 11**: The same methods you use to install Windows 10 can also be used to install Windows 11. For example, you can deploy Windows to your devices using Windows Autopilot, Microsoft Deployment Toolkit (MDT), Configuration Manager, and more. Windows 11 will be delivered as an upgrade to eligible devices running Windows 10.
|
||||||
|
|
||||||
|
For more information on getting started, see [Windows client deployment resources and documentation](/windows/deployment/) and [Plan for Windows 11](windows-11-plan.md).
|
||||||
|
|
||||||
|
For more information on the end-user experience, see [Ways to install Windows 11](https://support.microsoft.com/windows/e0edbbfb-cfc5-4011-868b-2ce77ac7c70e).
|
||||||
|
|
||||||
|
- **Windows Autopilot**: If you're purchasing new devices, you can use Windows Autopilot to set up and pre-configure the devices. When users get the device, they sign in with their organization account (`user@contoso.com`). In the background, Autopilot gets them ready for use, and deploys any apps or policies you set. You can also use Windows Autopilot to reset, repurpose, and recover devices. Autopilot offers zero touch deployment for admins.
|
||||||
|
|
||||||
|
If you have a global or remote workforce, then Autopilot might be the right option to install the OS, and get it ready for use. For more information, see [Overview of Windows Autopilot](/mem/autopilot/windows-autopilot).
|
||||||
|
|
||||||
|
- **Microsoft Endpoint Manager** is a mobile application management (MAM) and mobile device management (MDM) provider. It helps manage devices, and manage apps on devices in your organization. You configure policies, and then deploy these policies to users and groups. You can create and deploy policies that install apps, configure device features, enforce PIN requirements, block compromised devices, and more.
|
||||||
|
|
||||||
|
If you currently use Group Policy to manage your Windows 10 devices, you can also use Group Policy to manage Windows 11 devices. In Endpoint Manager, there are [administrative templates](/mem/intune/configuration/administrative-templates-windows) and the [settings catalog](/mem/intune/configuration/settings-catalog) that include many of the same policies. [Group Policy analytics](/mem/intune/configuration/group-policy-analytics) analyze your on-premises group policy objects.
|
||||||
|
|
||||||
|
- **Windows Updates and Delivery optimization** helps manage updates, and manage features on your devices. Starting with Windows 11, the OS feature updates are installed annually. For more information on servicing channels, and what they are, see [Servicing channels](/windows/deployment/update/waas-overview#servicing-channels).
|
||||||
|
|
||||||
|
Like Windows 10, Windows 11 will receive monthly quality updates.
|
||||||
|
|
||||||
|
You have options to install updates on your Windows devices, including Endpoint Manager, Group Policy, Windows Server Update Services (WSUS), and more. For more information, see [Assign devices to servicing channels](/windows/deployment/update/waas-servicing-channels-windows-10-updates).
|
||||||
|
|
||||||
|
Some updates are large, and use bandwidth. Delivery optimization helps reduce bandwidth consumption. It shares the work of downloading the update packages with multiple devices in your deployment. Windows 11 updates are smaller, as they only pull down source files that are different. You can create policies that configure delivery optimization settings. For example, set the maximum upload and download bandwidth, set caching sizes, and more.
|
||||||
|
|
||||||
|
For more information, see [Delivery Optimization for Windows updates](/windows/deployment/update/waas-delivery-optimization).
|
||||||
|
|
||||||
|
For more information on the end-user experience, see:
|
||||||
|
|
||||||
|
- [Installation & updates](https://support.microsoft.com/office/installation-updates-2f9c1819-310d-48a7-ac12-25191269903c#PickTab=Windows_11)
|
||||||
|
- [Manage updates in Windows](https://support.microsoft.com/windows/manage-updates-in-windows-643e9ea7-3cf6-7da6-a25c-95d4f7f099fe)
|
||||||
|
|
||||||
|
## Next steps
|
||||||
|
|
||||||
|
- [Windows 11 requirements](windows-11-requirements.md)
|
||||||
|
- [Plan for Windows 11](windows-11-plan.md)
|
||||||
|
- [Prepare for Windows 11](windows-11-prepare.md)
|
||||||
|
- [Windows release health](https://aka.ms/windowsreleasehealth)
|
@ -1,92 +0,0 @@
|
|||||||
---
|
|
||||||
title: Windows 11 overview
|
|
||||||
description: Overview of Windows 11
|
|
||||||
ms.reviewer:
|
|
||||||
manager: laurawi
|
|
||||||
ms.audience: itpro
|
|
||||||
author: greg-lindsay
|
|
||||||
ms.author: greglin
|
|
||||||
ms.prod: w11
|
|
||||||
ms.mktglfcycl: deploy
|
|
||||||
ms.sitesec: library
|
|
||||||
ms.localizationpriority: medium
|
|
||||||
audience: itpro
|
|
||||||
ms.topic: article
|
|
||||||
ms.custom: seo-marvel-apr2020
|
|
||||||
---
|
|
||||||
|
|
||||||
# Windows 11 overview
|
|
||||||
|
|
||||||
**Applies to**
|
|
||||||
|
|
||||||
- Windows 11
|
|
||||||
|
|
||||||
This article provides an introduction to Windows 11, and answers some frequently asked questions.
|
|
||||||
|
|
||||||
Also see the following articles to learn more about Windows 11:
|
|
||||||
|
|
||||||
- [Windows 11 requirements](windows-11-requirements.md): Requirements to deploy Windows 11.
|
|
||||||
- [Plan for Windows 11](windows-11-plan.md): Information to help you plan for Windows 11 in your organization.
|
|
||||||
- [Prepare for Windows 11](windows-11-prepare.md): Procedures to ensure readiness to deploy Windows 11.
|
|
||||||
|
|
||||||
## Introduction
|
|
||||||
|
|
||||||
Windows 11 is the next evolution of Windows; it is the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end-user productivity in a fresh experience that is flexible and fluid. Windows 11 is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever.
|
|
||||||
|
|
||||||
Windows 11 is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows 11 also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows 11.
|
|
||||||
|
|
||||||
## How to get Windows 11
|
|
||||||
|
|
||||||
Windows 11 will be delivered as an upgrade to eligible devices running Windows 10, beginning on October 5, 2021. Windows 11 will also be available on eligible new devices.
|
|
||||||
|
|
||||||
For administrators managing devices on behalf of their organization, Windows 11 will be available through the same, familiar channels that you use today for Windows 10 feature updates. You will be able to use existing deployment and management tools, such as Windows Update for Business, Microsoft Endpoint Manager, and Windows Autopilot. For more information, see [Plan for Windows 11](windows-11-plan.md).
|
|
||||||
|
|
||||||
For devices that are not managed by an organization, the Windows 11 upgrade will be offered to eligible Windows 10 devices through Windows Update using Microsoft's intelligent rollout process to ensure a smooth upgrade experience.
|
|
||||||
|
|
||||||
For more information about device eligibility, see [Windows 11 requirements](windows-11-requirements.md).
|
|
||||||
|
|
||||||
If you are interested in testing Windows 11 before general availability, you can join the [Windows Insider Program](https://insider.windows.com) or [Windows Insider Program for Business](https://insider.windows.com/for-business). You can also preview Windows 11 by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS).
|
|
||||||
|
|
||||||
If you are an administrator, you can manage installations of Windows 11 Insider Preview Builds across multiple devices in your organization using Group Policy, MDM solutions such as Intune, Configuration Manager, or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). For more information, see [Manage Insider Preview builds across your organization](/windows-insider/business/manage-builds).
|
|
||||||
|
|
||||||
## Before you begin
|
|
||||||
|
|
||||||
The following sections provide a quick summary of licensing, compatibility, management, and servicing considerations to help you get started with Windows 11.
|
|
||||||
|
|
||||||
#### Licensing
|
|
||||||
|
|
||||||
There are no unique licensing requirements for Windows 11 beyond what is required for Windows 10 devices.
|
|
||||||
|
|
||||||
Microsoft 365 licenses that include Windows 10 licenses will permit you to run Windows 11 on supported devices. If you have a volume license, it will equally cover Windows 11 and Windows 10 devices before and after upgrade.
|
|
||||||
|
|
||||||
#### Compatibility
|
|
||||||
|
|
||||||
Most accessories and associated drivers that work with Windows 10 are expected to work with Windows 11. Check with your accessory manufacturer for specific details.
|
|
||||||
|
|
||||||
Windows 11 preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows 11. For more information, see [Application compatibility](windows-11-plan.md#application-compatibility).
|
|
||||||
|
|
||||||
#### Familiar processes
|
|
||||||
|
|
||||||
Windows 11 is built on the same foundation as Windows 10. Typically, you can use the same tools and solutions you use today to deploy, manage, and secure Windows 11. Your current management tools and processes will also work to manage monthly quality updates for both Windows 10 and Windows 11.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> Check with the providers of any non-Microsoft security and management solutions that you use to ensure compatibility with Windows 11, particularly those providing security or data loss prevention capabilities.
|
|
||||||
|
|
||||||
For more information, see [Prepare for Windows 11](windows-11-prepare.md).
|
|
||||||
|
|
||||||
#### Servicing Windows 11
|
|
||||||
|
|
||||||
Like Windows 10, Windows 11 will receive monthly quality updates. However, it will have a new feature update cadence. Windows 11 feature updates will be released once per year.
|
|
||||||
|
|
||||||
When Windows 11 reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the [Windows release health](https://aka.ms/windowsreleasehealth) hub. Monthly release notes will also be available from a consolidated Windows 11 update history page at that time. For more information, see [Servicing and support](windows-11-plan.md#servicing-and-support).
|
|
||||||
|
|
||||||
## Next steps
|
|
||||||
|
|
||||||
[Windows 11 requirements](windows-11-requirements.md)<br>
|
|
||||||
[Plan for Windows 11](windows-11-plan.md)<br>
|
|
||||||
[Prepare for Windows 11](windows-11-prepare.md)
|
|
||||||
|
|
||||||
## Also see
|
|
||||||
|
|
||||||
[What's new in Windows 11](/windows-hardware/get-started/what-s-new-in-windows)<br>
|
|
||||||
[Windows 11: The Optimization and Performance Improvements](https://www.youtube.com/watch?v=oIYHRRTCVy4)
|
|