mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 06:47:21 +00:00
Merge branch 'main' into v-smandalika-5694287-B17
This commit is contained in:
Siddarth Mandalika
GitHub
commit
e836b74c7f
@ -17,22 +17,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "hololens",
|
||||
"build_source_folder": "devices/hololens",
|
||||
"build_output_subfolder": "hololens",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "internet-explorer",
|
||||
"build_source_folder": "browsers/internet-explorer",
|
||||
@ -49,22 +33,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "keep-secure",
|
||||
"build_source_folder": "windows/keep-secure",
|
||||
"build_output_subfolder": "keep-secure",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "microsoft-edge",
|
||||
"build_source_folder": "browsers/edge",
|
||||
@ -81,22 +49,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "release-information",
|
||||
"build_source_folder": "windows/release-information",
|
||||
"build_output_subfolder": "release-information",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "smb",
|
||||
"build_source_folder": "smb",
|
||||
@ -193,22 +145,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-device-security",
|
||||
"build_source_folder": "windows/device-security",
|
||||
"build_output_subfolder": "win-device-security",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-hub",
|
||||
"build_source_folder": "windows/hub",
|
||||
@ -225,22 +161,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-plan",
|
||||
"build_source_folder": "windows/plan",
|
||||
"build_output_subfolder": "windows-plan",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-privacy",
|
||||
"build_source_folder": "windows/privacy",
|
||||
@ -273,38 +193,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-update",
|
||||
"build_source_folder": "windows/update",
|
||||
"build_output_subfolder": "windows-update",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-threat-protection",
|
||||
"build_source_folder": "windows/threat-protection",
|
||||
"build_output_subfolder": "win-threat-protection",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-whats-new",
|
||||
"build_source_folder": "windows/whats-new",
|
||||
@ -360,13 +248,13 @@
|
||||
"Pdf"
|
||||
]
|
||||
},
|
||||
"need_generate_pdf_url_template": true,
|
||||
"targets": {
|
||||
"Pdf": {
|
||||
"template_folder": "_themes.pdf"
|
||||
}
|
||||
},
|
||||
"docs_build_engine": {},
|
||||
"need_generate_pdf_url_template": true,
|
||||
"contribution_branch_mappings": {},
|
||||
"need_generate_pdf": false,
|
||||
"need_generate_intellisense": false
|
||||
|
||||
@ -19559,6 +19559,21 @@
|
||||
"source_path": "windows/deployment/deploy-windows-mdt/deploy-a-windows-11-image-using-mdt.md",
|
||||
"redirect_url": "/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/get-minecraft-device-promotion.md",
|
||||
"redirect_url": "/education/windows/get-minecraft-for-education",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-application-control/deploy-windows-defender-application-control-policies-using-group-policy.md",
|
||||
"redirect_url": "/windows/security/threat-protection/windows-defender-application-control/deployment/deploy-windows-defender-application-control-policies-using-group-policy",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-application-control/deploy-windows-defender-application-control-policies-using-intune.md",
|
||||
"redirect_url": "/windows/security/threat-protection/windows-defender-application-control/deployment/deploy-windows-defender-application-control-policies-using-intune",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -2,39 +2,9 @@
|
||||
|
||||
|
||||
|
||||
## Week of May 02, 2022
|
||||
## Week of June 27, 2022
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 5/3/2022 | [Reset devices with Autopilot Reset](/education/windows/autopilot-reset) | modified |
|
||||
| 5/3/2022 | [Change history for Windows 10 for Education (Windows 10)](/education/windows/change-history-edu) | modified |
|
||||
| 5/3/2022 | [Change to Windows 10 Education from Windows 10 Pro](/education/windows/change-to-pro-education) | modified |
|
||||
| 5/3/2022 | [Chromebook migration guide (Windows 10)](/education/windows/chromebook-migration-guide) | modified |
|
||||
| 5/3/2022 | [Windows 10 configuration recommendations for education customers](/education/windows/configure-windows-for-education) | modified |
|
||||
| 5/3/2022 | [Deploy Windows 10 in a school district (Windows 10)](/education/windows/deploy-windows-10-in-a-school-district) | modified |
|
||||
| 5/3/2022 | [Deploy Windows 10 in a school (Windows 10)](/education/windows/deploy-windows-10-in-a-school) | modified |
|
||||
| 5/3/2022 | [Deployment recommendations for school IT administrators](/education/windows/edu-deployment-recommendations) | modified |
|
||||
| 5/3/2022 | [For IT administrators get Minecraft Education Edition](/education/windows/school-get-minecraft) | modified |
|
||||
| 5/3/2022 | [What's in Set up School PCs provisioning package](/education/windows/set-up-school-pcs-provisioning-package) | modified |
|
||||
| 5/3/2022 | [Take a Test app technical reference](/education/windows/take-a-test-app-technical) | modified |
|
||||
| 5/3/2022 | [Set up Take a Test on multiple PCs](/education/windows/take-a-test-multiple-pcs) | modified |
|
||||
| 5/3/2022 | [For teachers get Minecraft Education Edition](/education/windows/teacher-get-minecraft) | modified |
|
||||
| 5/3/2022 | [Test Windows 10 in S mode on existing Windows 10 education devices](/education/windows/test-windows10s-for-edu) | modified |
|
||||
|
||||
|
||||
## Week of April 25, 2022
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 4/25/2022 | [Deploy Windows 10 in a school district (Windows 10)](/education/windows/deploy-windows-10-in-a-school-district) | modified |
|
||||
| 4/25/2022 | [Deploy Windows 10 in a school district (Windows 10)](/education/windows/deploy-windows-10-in-a-school-district) | modified |
|
||||
|
||||
|
||||
## Week of April 18, 2022
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 4/21/2022 | [For IT administrators get Minecraft Education Edition](/education/windows/school-get-minecraft) | modified |
|
||||
| 6/30/2022 | Get Minecraft Education Edition with your Windows 10 device promotion | removed |
|
||||
|
||||
@ -53,8 +53,6 @@
|
||||
href: teacher-get-minecraft.md
|
||||
- name: "For IT administrators: get Minecraft Education Edition"
|
||||
href: school-get-minecraft.md
|
||||
- name: "Get Minecraft: Education Edition with Windows 10 device promotion"
|
||||
href: get-minecraft-device-promotion.md
|
||||
- name: Test Windows 10 in S mode on existing Windows 10 education devices
|
||||
href: test-windows10s-for-edu.md
|
||||
- name: Enable Windows 10 in S mode on Surface Go devices
|
||||
|
||||
@ -1,90 +0,0 @@
|
||||
---
|
||||
title: Get Minecraft Education Edition with your Windows 10 device promotion
|
||||
description: Windows 10 device promotion for Minecraft Education Edition licenses
|
||||
keywords: school, Minecraft, education edition
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
author: dansimp
|
||||
searchScope:
|
||||
- Store
|
||||
ms.author: dansimp
|
||||
ms.date: 06/05/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
|
||||
# Get Minecraft: Education Edition with Windows 10 device promotion
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
|
||||
The **Minecraft: Education Edition** with Windows 10 device promotion ended January 31, 2018.
|
||||
|
||||
Qualifying customers that received one-year subscriptions for Minecraft: Education Edition as part of this program and wish to continue using the game in their schools can purchase new subscriptions in Microsoft Store for Education.
|
||||
For more information on purchasing Minecraft: Education Edition, see [Add Minecraft to your Store for Education](./school-get-minecraft.md?toc=%2fmicrosoft-store%2feducation%2ftoc.json).
|
||||
|
||||
>[!Note]
|
||||
>**Minecraft: Education Edition** with Windows 10 device promotion subscriptions are valid for 1 year from the time
|
||||
of redemption. At the end of 1 year, the promotional subscriptions will expire and any people using these subscriptions will be reverted to a trial license of **Minecraft: Education Edition**.
|
||||
|
||||
To prevent being reverted to a trial license, admins or teachers need to purchase new **Minecraft: Education Edition** subscriptions from Store for Education, and assign licenses to users who used a promotional subscription.
|
||||
|
||||
|
||||
<!---
|
||||
For qualifying customers, receive a one-year, single-user subscription for Minecraft: Education Edition for each Windows 10 device you purchase for your K-12 school. You’ll need your invoice or receipt, so be sure to keep track of that. For more information including terms of use, see [Minecraft: Education Edition promotion](https://info.microsoft.com/Minecraft-Education-Edition-Signup.html).
|
||||
|
||||
## Requirements
|
||||
- Qualified Educational Users in K-12 education institutions
|
||||
- Windows 10 devices purchased from May 2, 2017 - January 31, 2018
|
||||
- Redeem Minecraft: Education Edition licenses from July 1, 2017 - March 17, 2018
|
||||
- Microsoft Store for Education admin must submit request for Minecraft: Education Edition licenses
|
||||
- Proof of device purchase is required (invoice required)
|
||||
|
||||
Full details available at [Minecraft: Education Edition promotion](https://info.microsoft.com/Minecraft-Education-Edition-Signup.html).
|
||||
|
||||
## Redeem Minecraft: Education Edition licenses
|
||||
Redeeming your licenses takes just a few steps:
|
||||
- Visit the device promotion page
|
||||
- Submit a device purchase statement
|
||||
- Provide proof of your device purchase
|
||||
|
||||
After that, we’ll add the appropriate number of Minecraft: Education Edition licenses to your product inventory in **Microsoft Store for Education** as **Minecraft: Education Edition [subscription]**.
|
||||
|
||||
**To redeem Minecraft: Education Edition licenses**
|
||||
1. Visit [Minecraft: Education Edition and Windows 10 device promotion](https://educationstore.microsoft.com/store/mee-device-promo?setflight=wsfb_devicepromo) in **Microsoft Store for Education**.
|
||||
|
||||
|
||||
|
||||
2. Sign in to **Microsoft Store for Education** using a school account. If you don’t have one, we’ll help you set one up. <br>
|
||||
-or-
|
||||
|
||||
If you're already signed in to Microsoft Store for Education, the device special offer is available on **Benefits**. </br>
|
||||
Click **Manage**, **Benefits**, and then click **Minecraft: Education Edition Device Promotion**.
|
||||
|
||||
3. **On Minecraft Windows 10 device special offer**, click **Submit a device purchase**.
|
||||
|
||||
|
||||
|
||||
4. Provide info for **Proof of Purchase**. Be sure to include a .pdf or .jpg of your invoice, and then click **Next**.
|
||||
|
||||
> [!NOTE]
|
||||
> Your one-year subscription starts when you submit your proof-of-purchase info. Be sure to submit your request when you'll be using licenses in the classroom.
|
||||
|
||||
|
||||
|
||||
5. Accept the **Promotion Terms of use**, and then click **Submit**. </br>
|
||||
|
||||
Success look like this!
|
||||
|
||||
|
||||
|
||||
6. Click **Actions** and then click **Manage** to go to the management page for **Minecraft: Education Edition** and distribute licenses.
|
||||
|
||||
## Distribute Minecraft: Education Edition licenses
|
||||
Teachers or admins can distribute the licenses:
|
||||
- [Learn how teachers can distribute **Minecraft: Education Edition**](teacher-get-minecraft.md#distribute-minecraft)
|
||||
- [Learn how IT administrators can distribute **Minecraft: Education Edition**](school-get-minecraft.md#distribute-minecraft)
|
||||
-->
|
||||
@ -56,11 +56,11 @@ Windows 11 SE comes with some preinstalled apps. The following apps can also run
|
||||
|FortiClient |7.0.1.0083 |Win32 |Fortinet|
|
||||
|Free NaturalReader |16.1.2 |Win32 |Natural Soft|
|
||||
|GoGuardian |1.4.4 |Win32 |GoGuardian|
|
||||
|Google Chrome |100.0.4896.127|Win32 |Google|
|
||||
|Google Chrome |102.0.5005.115|Win32 |Google|
|
||||
|Illuminate Lockdown Browser |2.0.5 |Win32 |Illuminate Education|
|
||||
|Immunet |7.5.0.20795 |Win32 |Immunet|
|
||||
|JAWS for Windows |2022.2112.24 |Win32 |Freedom Scientific|
|
||||
|Kite Student Portal |8.0.1 |Win32 |Dynamic Learning Maps|
|
||||
|Kite Student Portal |8.0.3.0 |Win32 |Dynamic Learning Maps|
|
||||
|Kortext |2.3.433.0 |Store |Kortext|
|
||||
|Kurzweil 3000 Assistive Learning |20.13.0000 |Win32 |Kurzweil Educational Systems|
|
||||
|LanSchool |9.1.0.46 |Win32 |Stoneware|
|
||||
@ -83,7 +83,7 @@ Windows 11 SE comes with some preinstalled apps. The following apps can also run
|
||||
|Safe Exam Browser |3.3.2.413 |Win32 |Safe Exam Browser|
|
||||
|Secure Browser |14.0.0 |Win32 |Cambium Development|
|
||||
|Secure Browser |4.8.3.376 |Win32 |Questar, Inc|
|
||||
|Senso.Cloud |2021.11.15.0 |Win32|Senso.Cloud|
|
||||
|Senso.Cloud |2021.11.15.0 |Win32|Senso.Cloud|
|
||||
|SuperNova Magnifier & Screen Reader |21.02 |Win32 |Dolphin Computer Access|
|
||||
|Zoom |5.9.1 (2581)|Win32 |Zoom|
|
||||
|ZoomText Fusion |2022.2109.10|Win32 |Freedom Scientific|
|
||||
|
||||
@ -97,6 +97,7 @@ Firewall
|
||||
----------------Protocol
|
||||
----------------LocalPortRanges
|
||||
----------------RemotePortRanges
|
||||
----------------IcmpTypesAndCodes
|
||||
----------------LocalAddressRanges
|
||||
----------------RemoteAddressRanges
|
||||
----------------Description
|
||||
@ -340,6 +341,12 @@ Comma separated list of ranges, For example, 100-120,200,300-320.
|
||||
If not specified, the default is All.
|
||||
Value type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
|
||||
<a href="" id="icmptypesandcodes"></a>**FirewallRules/_FirewallRuleName_/IcmpTypesAndCodes**
|
||||
ICMP types and codes applicable to the firewall rule. To specify all ICMP types and codes, use the “\*” character. For specific ICMP types and codes, use the “:” character to separate the type and code, for example, 3:4, 1:\*. The “\*” character can be used to represent any code. The “\*” character cannot be used to specify any type; examples such as “\*:4” or “\*:\*” are invalid.
|
||||
If not specified, the default is All.
|
||||
Value type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
<a href="" id="localaddressranges"></a>**FirewallRules/*FirewallRuleName*/LocalAddressRanges**
|
||||
Comma-separated list of local addresses covered by the rule. The default value is "*". Valid tokens include:
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
ms.date: 06/28/2022
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -19,7 +19,7 @@ The table below shows the applicability of Windows:
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|No|No|
|
||||
|Windows SE|No|No|
|
||||
|Windows SE|No|Yes|
|
||||
|Business|No|No|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
@ -1483,7 +1483,7 @@ This policy setting allows you to enable or disable low CPU priority for schedul
|
||||
|
||||
If you enable this setting, low CPU priority will be used during scheduled scans.
|
||||
|
||||
If you disable or don't configure this setting, not changes will be made to CPU priority for scheduled scans.
|
||||
If you disable or don't configure this setting, no changes will be made to CPU priority for scheduled scans.
|
||||
|
||||
Supported values:
|
||||
|
||||
@ -1922,10 +1922,7 @@ The following list shows the supported values:
|
||||
> [!NOTE]
|
||||
> This policy is only enforced in Windows 10 for desktop.
|
||||
|
||||
Selects the time of day that the Windows Defender quick scan should run.
|
||||
|
||||
> [!NOTE]
|
||||
> The scan type will depends on what scan type is selected in the **Defender/ScanParameter** setting.
|
||||
Selects the time of day that the Windows Defender quick scan should run. The Windows Defender quick scan runs daily if a time is specified.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -4415,7 +4415,7 @@ The following list shows the supported values:
|
||||
<!--/SupportedValues-->
|
||||
<!--ADMXBacked-->
|
||||
ADMX Info:
|
||||
- GP Friendly name: *Allows enterprises to provide their users with a single-browser experience*
|
||||
- GP Friendly name: *Enable extended hot keys in Internet Explorer mode*
|
||||
- GP name: *EnableExtendedIEModeHotkeys*
|
||||
- GP path: *Windows Components/Internet Explorer/Security Features/Add-on Management*
|
||||
- GP ADMX file name: *inetres.admx*
|
||||
@ -14317,4 +14317,4 @@ ADMX Info:
|
||||
|
||||
## Related topics
|
||||
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
|
||||
@ -34,11 +34,11 @@ manager: dansimp
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Pro|No|Yes|
|
||||
|Windows SE|No|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|Business|No|Yes|
|
||||
|Enterprise|No|Yes|
|
||||
|Education|No|Yes|
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
<hr/>
|
||||
@ -83,4 +83,4 @@ ADMX Info:
|
||||
|
||||
## Related topics
|
||||
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/18/2022
|
||||
ms.date: 06/15/2022
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.collection: highpri
|
||||
@ -3478,7 +3478,7 @@ The following list shows the supported values:
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="update-setpolicydrivenupdatesourcefordriver"></a>**Update/SetPolicyDrivenUpdateSourceForDriver**
|
||||
<a href="" id="update-setpolicydrivenupdatesourcefordriver"></a>**Update/SetPolicyDrivenUpdateSourceForDriverUpdates**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
The table below shows the applicability of Windows:
|
||||
@ -3508,12 +3508,12 @@ The table below shows the applicability of Windows:
|
||||
Configure this policy to specify whether to receive Windows Driver Updates from Windows Update endpoint, managed by Windows Update for Business policies, or through your configured Windows Server Update Service (WSUS) server.
|
||||
|
||||
If you configure this policy, also configure the scan source policies for other update types:
|
||||
- SetPolicyDrivenUpdateSourceForFeature
|
||||
- SetPolicyDrivenUpdateSourceForQuality
|
||||
- SetPolicyDrivenUpdateSourceForOther
|
||||
- SetPolicyDrivenUpdateSourceForFeatureUpdates
|
||||
- SetPolicyDrivenUpdateSourceForQualityUpdates
|
||||
- SetPolicyDrivenUpdateSourceForOtherUpdates
|
||||
|
||||
>[!NOTE]
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point your WSUS server, this policy will have no effect.
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
@ -3536,7 +3536,7 @@ The following list shows the supported values:
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="update-setpolicydrivenupdatesourceforfeature"></a>**Update/SetPolicyDrivenUpdateSourceForFeature**
|
||||
<a href="" id="update-setpolicydrivenupdatesourceforfeature"></a>**Update/SetPolicyDrivenUpdateSourceForFeatureUpdates**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
The table below shows the applicability of Windows:
|
||||
@ -3566,12 +3566,12 @@ The table below shows the applicability of Windows:
|
||||
Configure this policy to specify whether to receive Windows Driver Updates from Windows Update endpoint, managed by Windows Update for Business policies, or through your configured Windows Server Update Service (WSUS) server.
|
||||
|
||||
If you configure this policy, also configure the scan source policies for other update types:
|
||||
- SetPolicyDrivenUpdateSourceForQuality
|
||||
- SetPolicyDrivenUpdateSourceForDriver
|
||||
- SetPolicyDrivenUpdateSourceForOther
|
||||
- SetPolicyDrivenUpdateSourceForQualityUpdates
|
||||
- SetPolicyDrivenUpdateSourceForDriverUpdates
|
||||
- SetPolicyDrivenUpdateSourceForOtherUpdates
|
||||
|
||||
>[!NOTE]
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point your WSUS server, this policy will have no effect.
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
@ -3594,7 +3594,7 @@ The following list shows the supported values:
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="update-setpolicydrivenupdatesourceforother"></a>**Update/SetPolicyDrivenUpdateSourceForOther**
|
||||
<a href="" id="update-setpolicydrivenupdatesourceforother"></a>**Update/SetPolicyDrivenUpdateSourceForOtherUpdates**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
The table below shows the applicability of Windows:
|
||||
@ -3624,12 +3624,12 @@ The table below shows the applicability of Windows:
|
||||
Configure this policy to specify whether to receive Windows Driver Updates from Windows Update endpoint, managed by Windows Update for Business policies, or through your configured Windows Server Update Service (WSUS) server.
|
||||
|
||||
If you configure this policy, also configure the scan source policies for other update types:
|
||||
- SetPolicyDrivenUpdateSourceForFeature
|
||||
- SetPolicyDrivenUpdateSourceForQuality
|
||||
- SetPolicyDrivenUpdateSourceForDriver
|
||||
- SetPolicyDrivenUpdateSourceForFeatureUpdates
|
||||
- SetPolicyDrivenUpdateSourceForQualityUpdates
|
||||
- SetPolicyDrivenUpdateSourceForDriverUpdates
|
||||
|
||||
>[!NOTE]
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point your WSUS server, this policy will have no effect.
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
@ -3652,7 +3652,7 @@ The following list shows the supported values:
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="update-setpolicydrivenupdatesourceforquality"></a>**Update/SetPolicyDrivenUpdateSourceForQuality**
|
||||
<a href="" id="update-setpolicydrivenupdatesourceforquality"></a>**Update/SetPolicyDrivenUpdateSourceForQualityUpdates**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
The table below shows the applicability of Windows:
|
||||
@ -3682,12 +3682,12 @@ The table below shows the applicability of Windows:
|
||||
Configure this policy to specify whether to receive Windows Driver Updates from Windows Update endpoint, managed by Windows Update for Business policies, or through your configured Windows Server Update Service (WSUS) server.
|
||||
|
||||
If you configure this policy, also configure the scan source policies for other update types:
|
||||
- SetPolicyDrivenUpdateSourceForFeature
|
||||
- SetPolicyDrivenUpdateSourceForDriver
|
||||
- SetPolicyDrivenUpdateSourceForOther
|
||||
- SetPolicyDrivenUpdateSourceForFeatureUpdates
|
||||
- SetPolicyDrivenUpdateSourceForDriverUpdates
|
||||
- SetPolicyDrivenUpdateSourceForOtherUpdates
|
||||
|
||||
>[!NOTE]
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point your WSUS server, this policy will have no effect.
|
||||
>If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
@ -4013,4 +4013,4 @@ ADMX Info:
|
||||
|
||||
## Related topics
|
||||
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
|
||||
@ -24,9 +24,10 @@ The table below shows the applicability of Windows:
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
The RemoteWipe configuration service provider can be used by mobile operators DM server or enterprise management server to remotely wipe a device. The RemoteWipe configuration service provider can make the data stored in memory and hard disks difficult to recover if the device is remotely wiped after being lost or stolen.
|
||||
The RemoteWipe configuration service provider can be used by mobile operators DM server or enterprise management server to remotely reset a device. The RemoteWipe configuration service provider can make the data stored in memory and hard disks difficult to recover if the device is remotely reset after being lost or stolen.
|
||||
|
||||
The following example shows the RemoteWipe configuration service provider management object in tree format as used by both OMA DM and OMA Client Provisioning. Enterprise IT Professionals can update these settings by using the Exchange Server.
|
||||
|
||||
```
|
||||
./Vendor/MSFT
|
||||
RemoteWipe
|
||||
@ -39,15 +40,16 @@ RemoteWipe
|
||||
--------LastError
|
||||
--------Status
|
||||
```
|
||||
|
||||
<a href="" id="dowipe"></a>**doWipe**
|
||||
Specifies that a remote wipe of the device should be performed. The return status code indicates whether the device accepted the Exec command.
|
||||
Exec on this node starts a remote reset of the device. A remote reset is equivalent to running "Reset this PC > Remove everything" from the Settings app, with **Clean Data** set to No and **Delete Files** set to Yes. The return status code indicates whether the device accepted the Exec command. If a doWipe reset is started and then interrupted, the PC will attempt to roll-back to the pre-reset state. If the PC can't be rolled-back, the recovery environment will take no additional actions and the PC could be in an unusable state and Windows will have to be reinstalled.
|
||||
|
||||
When used with OMA Client Provisioning, a dummy value of "1" should be included for this element.
|
||||
|
||||
Supported operation is Exec.
|
||||
|
||||
<a href="" id="dowipepersistprovisioneddata"></a>**doWipePersistProvisionedData**
|
||||
Specifies that provisioning data should be backed up to a persistent location, and then a remote wipe of the device should be performed.
|
||||
Exec on this node specifies that provisioning packages in the `%SystemDrive%\ProgramData\Microsoft\Provisioning` folder will be retained and then applied to the OS after the reset.
|
||||
|
||||
When used with OMA Client Provisioning, a dummy value of "1" should be included for this element.
|
||||
|
||||
@ -56,14 +58,14 @@ Supported operation is Exec.
|
||||
The information that was backed up will be restored and applied to the device when it resumes. The return status code shows whether the device accepted the Exec command.
|
||||
|
||||
<a href="" id="doWipeProtected"></a>**doWipeProtected**
|
||||
Added in Windows 10, version 1703. Exec on this node performs a remote wipe on the device and fully clean the internal drive. In some device configurations, this command may leave the device unable to boot. The return status code indicates whether the device accepted the Exec command.
|
||||
Added in Windows 10, version 1703. Exec on this node performs a remote reset on the device and also fully cleans the internal drive. Drives that are cleaned with doWipeProtected aren't expected to meet industry or government standards for data cleaning. In some device configurations, this command may leave the device unable to boot. The return status code indicates whether the device accepted the Exec command, but not whether the reset was successful.
|
||||
|
||||
The doWipeProtected is functionally similar to doWipe. But unlike doWipe, which can be easily circumvented by simply power cycling the device, doWipeProtected will keep trying to reset the device until it’s done.
|
||||
The doWipeProtected is functionally similar to doWipe. But unlike doWipe, which can be easily circumvented by simply power cycling the device, if a reset that uses doWipeProtected is interrupted, upon restart it will clean the PC's disk partitions. Because doWipeProtected will clean the partitions in case of failure or interruption, use doWipeProtected in lost/stolen device scenarios.
|
||||
|
||||
Supported operation is Exec.
|
||||
|
||||
<a href="" id="doWipePersistUserData"></a>**doWipePersistUserData**
|
||||
Added in Windows 10, version 1709. Exec on this node will perform a remote reset on the device, and persist user accounts and data. The return status code shows whether the device accepted the Exec command.
|
||||
Added in Windows 10, version 1709. Exec on this node will perform a remote reset on the device, and persist user accounts and data. This setting is equivalent to selecting "Reset this PC > Keep my files" when manually starting a reset from the Settings app. The return status code shows whether the device accepted the Exec command.
|
||||
|
||||
<a href="" id="automaticredeployment"></a>**AutomaticRedeployment**
|
||||
Added in Windows 10, version 1809. Node for the Autopilot Reset operation.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.topic: troubleshooting
|
||||
author: Deland-Han
|
||||
ms.localizationpriority: medium
|
||||
ms.author: delhan
|
||||
ms.date: 8/22/2019
|
||||
ms.date: 07/12/2022
|
||||
ms.reviewer: dcscontentpm
|
||||
manager: dansimp
|
||||
---
|
||||
@ -183,6 +183,63 @@ To specify that you don't want to overwrite any previous kernel or complete memo
|
||||
|
||||
- Set the **Overwrite** DWORD value to **0**.
|
||||
|
||||
#### Automatic Memory Dump
|
||||
|
||||
This is the default option. An Automatic Memory Dump contains the same information as a Kernel Memory Dump. The difference between the two is in the way that Windows sets the size of the system paging file. If the system paging file size is set to **System managed size**, and the kernel-mode crash dump is set to **Automatic Memory Dump**, then Windows can set the size of the paging file to less than the size of RAM. In this case, Windows sets the size of the paging file large enough to ensure that a kernel memory dump can be captured most of the time.
|
||||
|
||||
If the computer crashes and the paging file is not large enough to capture a kernel memory dump, Windows increases the size of the paging file to at least the size of RAM. For more information, see [Automatic Memory Dump](/windows-hardware/drivers/debugger/automatic-memory-dump).
|
||||
|
||||
To specify that you want to use an automatic memory dump file, run the following command or modify the registry value:
|
||||
|
||||
- ```cmd
|
||||
wmic recoveros set DebugInfoType = 7
|
||||
```
|
||||
|
||||
- Set the **CrashDumpEnabled** DWORD value to **7**.
|
||||
|
||||
To specify that you want to use a file as your memory dump file, run the following command or modify the registry value:
|
||||
|
||||
- ```cmd
|
||||
wmic recoveros set DebugFilePath = <filepath>
|
||||
```
|
||||
|
||||
- Set the **DumpFile** Expandable String Value to \<filepath\>.
|
||||
|
||||
To specify that you don't want to overwrite any previous kernel or complete memory dump files, run the following command or modify the registry value:
|
||||
|
||||
- ```cmd
|
||||
wmic recoveros set OverwriteExistingDebugFile = 0
|
||||
```
|
||||
|
||||
- Set the **Overwrite** DWORD value to **0**.
|
||||
|
||||
#### Active Memory Dump
|
||||
|
||||
An Active Memory Dump is similar to a Complete Memory Dump, but it filters out pages that are not likely to be relevant to troubleshooting problems on the host machine. Because of this filtering, it is typically significantly smaller than a Complete Memory Dump.
|
||||
|
||||
This dump file includes any memory allocated to user-mode applications. It also includes memory allocated to the Windows kernel and hardware abstraction layer, as well as memory allocated to kernel-mode drivers and other kernel-mode programs. The dump includes active pages mapped into the kernel or user space that are useful for debugging, as well as selected Pagefile-backed Transition, Standby, and Modified pages such as the memory allocated with VirtualAlloc or page-file-backed sections. Active dumps do not include pages on the free and zeroed lists, the file cache, guest VM pages, and various other types of memory that are not likely to be useful during debugging. For more information, see [Active Memory Dump](/windows-hardware/drivers/debugger/active-memory-dump).
|
||||
|
||||
To specify that you want to use an active memory dump file, modify the registry value:
|
||||
|
||||
- Set the **CrashDumpEnabled** DWORD value to **1**.
|
||||
- Set the **FilterPages** DWORD value to **1**.
|
||||
|
||||
To specify that you want to use a file as your memory dump file, run the following command or modify the registry value:
|
||||
|
||||
- ```cmd
|
||||
wmic recoveros set DebugFilePath = <filepath>
|
||||
```
|
||||
|
||||
- Set the DumpFile Expandable String Value to \<filepath\>.
|
||||
|
||||
To specify that you don't want to overwrite any previous kernel or complete memory dump files, run the following command or modify the registry value:
|
||||
|
||||
- ```cmd
|
||||
wmic recoveros set OverwriteExistingDebugFile = 0
|
||||
```
|
||||
|
||||
- Set the **Overwrite** DWORD value to **0**.
|
||||
|
||||
>[!Note]
|
||||
>If you contact Microsoft Support about a Stop error, you might be asked for the memory dump file that is generated by the Write Debugging Information option.
|
||||
|
||||
@ -191,6 +248,7 @@ To view system failure and recovery settings for your local computer, type **wmi
|
||||
>[!Note]
|
||||
>To successfully use these Wmic.exe command line examples, you must be logged on by using a user account that has administrative rights on the computer. If you are not logged on by using a user account that has administrative rights on the computer, use the **/user:user_name** and **/password:password** switches.
|
||||
|
||||
|
||||
### Tips
|
||||
|
||||
- To take advantage of the dump file feature, your paging file must be on the boot volume. If you've moved the paging file to another volume, you must move it back to the boot volume before you use this feature.
|
||||
@ -201,4 +259,4 @@ To view system failure and recovery settings for your local computer, type **wmi
|
||||
|
||||
## References
|
||||
|
||||
[Varieties of Kernel-Mode Dump Files](/windows-hardware/drivers/debugger/varieties-of-kernel-mode-dump-files)
|
||||
[Varieties of Kernel-Mode Dump Files](/windows-hardware/drivers/debugger/varieties-of-kernel-mode-dump-files)
|
||||
|
||||
@ -94,7 +94,7 @@ You can also use Group Policy to manage access to Microsoft Store.
|
||||
4. On the **Turn off the Store application** setting page, click **Enabled**, and then click **OK**.
|
||||
|
||||
> [!Important]
|
||||
> Enabling **Turn off the Store application** policy turns off app updates from Microsoft Store.
|
||||
> When you enable the policy to **Turn off the Store application**, it turns off app updates from the Microsoft Store. To allow store apps to update, disable the policy to **Turn off automatic download and install of Updates**. This configuration allows in-box store apps to update while still blocking access to the store.
|
||||
|
||||
## Show private store only using Group Policy
|
||||
|
||||
|
||||
@ -139,8 +139,8 @@ When you configure your MDT Build Lab deployment share, you can also add applica
|
||||
|
||||
On **MDT01**:
|
||||
|
||||
1. Download the Enterprise distribution version of [Adobe Acrobat Reader DC](https://get.adobe.com/reader/enterprise/) (AcroRdrDC2200120117_en_US.exe) to **D:\\setup\\adobe** on MDT01.
|
||||
2. Extract the .exe file that you downloaded to an .msi (ex: .\AcroRdrDC2200120117_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
|
||||
1. Download the Enterprise distribution version of [Adobe Acrobat Reader DC](https://get.adobe.com/reader/enterprise/) (AcroRdrDC2200120142_en_US.exe) to **D:\\setup\\adobe** on MDT01.
|
||||
2. Extract the .exe file that you downloaded to an .msi (ex: .\AcroRdrDC2200120142_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
|
||||
3. In the Deployment Workbench, expand the **MDT Production** node and navigate to the **Applications** node.
|
||||
4. Right-click the **Applications** node, and create a new folder named **Adobe**.
|
||||
|
||||
@ -560,6 +560,12 @@ Some properties to use in the MDT Production rules file are as follows:
|
||||
- **USMTMigFiles(\*).** List of USMT templates (controlling what to backup and restore).
|
||||
- **EventService.** Activates logging information to the MDT monitoring web service.
|
||||
|
||||
> [!NOTE]
|
||||
> For more information about localization support, see the following articles:
|
||||
>
|
||||
> - [MDT sample guide](/mem/configmgr/mdt/samples-guide#fully-automated-lti-deployment-for-a-refresh-computer-scenario)
|
||||
> - [LCID (Locale ID) codes](/openspecs/office_standards/ms-oe376/6c085406-a698-4e12-9d4d-c3b0ee3dbc4a)
|
||||
|
||||
### Optional deployment share configuration
|
||||
|
||||
If your organization has a Microsoft Software Assurance agreement, you also can subscribe to the additional Microsoft Desktop Optimization Package (MDOP) license (at an additional cost). Included in MDOP is Microsoft Diagnostics and Recovery Toolkit (DaRT), which contains tools that can help you troubleshoot MDT deployments, as well as troubleshoot Windows itself.
|
||||
|
||||
@ -42,7 +42,7 @@ Each MDM Policy links to its documentation in the CSP hierarchy, providing its e
|
||||
| Policy | Data type | Value | Function |
|
||||
|--------------------------|-|-|------------------------------------------------------------|
|
||||
|**Provider/*ProviderID*/**[**CommercialID**](/windows/client-management/mdm/dmclient-csp#provider-providerid-commercialid) |String |[Your CommercialID](update-compliance-get-started.md#get-your-commercialid) |Identifies the device as belonging to your organization. |
|
||||
|**System/**[**AllowTelemetry**](/windows/client-management/mdm/policy-csp-system#system-allowtelemetry) |Integer | 1 - Basic |Configures the maximum allowed diagnostic data to be sent to Microsoft. Individual users can still set this value lower than what the policy defines. For more information, see the following policy. |
|
||||
|**System/**[**AllowTelemetry**](/windows/client-management/mdm/policy-csp-system#system-allowtelemetry) |Integer | 1 - Basic |Sends basic device info, including quality-related data, app compatibility, and other similar data to keep the device secure and up-to-date. For more information, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization). |
|
||||
|**System/**[**ConfigureTelemetryOptInSettingsUx**](/windows/client-management/mdm/policy-csp-system#system-configuretelemetryoptinsettingsux) |Integer |1 - Disable Telemetry opt-in Settings | (in Windows 10, version 1803 and later) Determines whether users of the device can adjust diagnostic data to levels lower than the level defined by AllowTelemetry. We recommend that you disable this policy or the effective diagnostic data level on devices might not be sufficient. |
|
||||
|**System/**[**AllowDeviceNameInDiagnosticData**](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata) |Integer | 1 - Allowed | Allows device name to be sent for Windows Diagnostic Data. If this policy is Not Configured or set to 0 (Disabled), Device Name will not be sent and will not be visible in Update Compliance, showing `#` instead. |
|
||||
| **System/**[**AllowUpdateComplianceProcessing**](/windows/client-management/mdm/policy-csp-system#system-allowUpdateComplianceProcessing) |Integer | 16 - Allowed | Enables data flow through Update Compliance's data processing system and indicates a device's explicit enrollment to the service. |
|
||||
|
||||
@ -40,7 +40,7 @@ Before you begin the process to add Update Compliance to your Azure subscription
|
||||
- **Diagnostic data requirements**: Update Compliance requires devices to send diagnostic data at *Required* level (previously *Basic*). Some queries in Update Compliance require devices to send diagnostic data at *Optional* level (previously *Full*) for Windows 11 devices or *Enhanced* level for Windows 10 devices. To learn more about what's included in different diagnostic levels, see [Diagnostics, feedback, and privacy in Windows](https://support.microsoft.com/windows/diagnostics-feedback-and-privacy-in-windows-28808a2b-a31b-dd73-dcd3-4559a5199319).
|
||||
- **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).
|
||||
- **Azure AD device join**: All devices enrolled in Update Compliance must meet all prerequisites for enabling Windows diagnostic data processor configuration, including the Azure AD join requirement. This prerequisite will be enforced for Update Compliance starting on October 15, 2022.
|
||||
- **Azure AD device join** or **hybrid Azure AD join**: All devices enrolled in Update Compliance must meet all prerequisites for enabling Windows diagnostic data processor configuration, including the Azure AD join requirement. This prerequisite will be enforced for Update Compliance starting on October 15, 2022.
|
||||
|
||||
## Add Update Compliance to your Azure subscription
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ author: mestew
|
||||
ms.author: mstewart
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.date: 06/06/2022
|
||||
ms.date: 06/30/2022
|
||||
---
|
||||
|
||||
# Update Compliance prerequisites
|
||||
@ -66,11 +66,15 @@ For more information about what's included in different diagnostic levels, see [
|
||||
> [!NOTE]
|
||||
> Enrolling into Update Compliance from the [Azure CLI](/cli/azure) or enrolling programmatically another way currently isn't supported. You must manually add Update Compliance to your Azure subscription.
|
||||
|
||||
## Microsoft 365 admin center permissions (optional)
|
||||
## Microsoft 365 admin center permissions (currently optional)
|
||||
|
||||
When you use the [Microsoft admin center software updates (preview) page](update-status-admin-center.md) with Update Compliance, the following permissions are also recommended:
|
||||
- To configure settings for the **Software Updates** page: [Global Admin role](/microsoft-365/admin/add-users/about-admin-roles)
|
||||
- To view the **Software Updates** page: [Global Reader role](/microsoft-365/admin/add-users/about-admin-roles)
|
||||
When you use the [Microsoft admin center software updates (preview) page](update-status-admin-center.md) with Update Compliance, the following permissions are also needed:
|
||||
|
||||
- To configure settings and view the **Software Updates** page:
|
||||
- [Global Administrator role](/azure/active-directory/roles/permissions-reference#global-administrator)
|
||||
- [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator)
|
||||
- To view the **Software Updates** page:
|
||||
- [Global Reader role](/azure/active-directory/roles/permissions-reference#global-reader)
|
||||
|
||||
## Log Analytics prerequisites
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.collection:
|
||||
- M365-analytics
|
||||
- highpri
|
||||
ms.topic: article
|
||||
ms.date: 05/07/2022
|
||||
ms.date: 06/20/2022
|
||||
---
|
||||
|
||||
# Microsoft admin center software updates (preview) page
|
||||
@ -34,8 +34,12 @@ The **Software updates** page has following tabs to assist you in monitoring upd
|
||||
|
||||
- [Update Compliance](update-compliance-v2-overview.md) needs to be enabled with clients sending data to the solution
|
||||
- An appropriate role assigned for the [Microsoft 365 admin center](https://admin.microsoft.com)
|
||||
- To configure settings for the **Software Updates** page: [Global Admin role](/microsoft-365/admin/add-users/about-admin-roles)
|
||||
- To view the **Software Updates** page: [Global Reader role](/microsoft-365/admin/add-users/about-admin-roles)
|
||||
- To configure settings and view the **Software Updates** page:
|
||||
- [Global Administrator role](/azure/active-directory/roles/permissions-reference#global-administrator)
|
||||
- [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator)
|
||||
- To view the **Software Updates** page:
|
||||
- [Global Reader role](/azure/active-directory/roles/permissions-reference#global-reader)
|
||||
|
||||
|
||||
## Limitations
|
||||
|
||||
|
||||
@ -25,6 +25,9 @@ ms.topic: article
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Server _doesn't_ get feature updates from Windows Update, so only the quality update policies apply. This behavior doesn't apply to [Azure Stack hyperconverged infrastructure (HCI)](/azure-stack/hci/).
|
||||
|
||||
You can use Group Policy or your mobile device management (MDM) service to configure Windows Update for Business settings for your devices. The sections in this topic provide the Group Policy and MDM policies for Windows 10, version 1511 and later, including Windows 11. The MDM policies use the OMA-URI setting from the [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider).
|
||||
|
||||
> [!IMPORTANT]
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Delivery Optimization Frequently Asked Questions
|
||||
ms.reviewer:
|
||||
ms.reviewer: aaroncz
|
||||
manager: dougeby
|
||||
description: The following is a list of frequently asked questions for Delivery Optimization.
|
||||
ms.prod: w10
|
||||
@ -37,17 +37,23 @@ For Delivery Optimization to successfully use the proxy, you should set up the p
|
||||
|
||||
## What hostnames should I allow through my firewall to support Delivery Optimization?
|
||||
|
||||
For communication between clients and the Delivery Optimization cloud service: **\*.do.dsp.mp.microsoft.com**.
|
||||
**For communication between clients and the Delivery Optimization cloud service**:
|
||||
|
||||
- `*.do.dsp.mp.microsoft.com`
|
||||
|
||||
**For Delivery Optimization metadata**:
|
||||
|
||||
- *.dl.delivery.mp.microsoft.com
|
||||
- *.emdl.ws.microsoft.com
|
||||
- `*.dl.delivery.mp.microsoft.com`
|
||||
- `*.emdl.ws.microsoft.com`
|
||||
|
||||
**For the payloads (optional)**:
|
||||
|
||||
- *.download.windowsupdate.com
|
||||
- *.windowsupdate.com
|
||||
- `*.download.windowsupdate.com`
|
||||
- `*.windowsupdate.com`
|
||||
|
||||
**For group peers across multiple NATs (Teredo)**:
|
||||
|
||||
- `win1910.ipv6.microsoft.com`
|
||||
|
||||
## Does Delivery Optimization use multicast?
|
||||
|
||||
|
||||
@ -147,15 +147,19 @@ S = Supported; Not considered a downgrade or an upgrade
|
||||
|
||||
**Destination Edition: (Starting)**
|
||||
|
||||
|Edition|Home|Pro|Pro for Workstations|Pro Education|Education|Enterprise LTSC|Enterprise|
|
||||
|--- |--- |--- |--- |--- |--- |--- |--- |
|
||||
|Home||||||||
|
||||
|Pro||||||||
|
||||
|Pro for Workstations||||||||
|
||||
|Pro Education||||||||
|
||||
|Education||✔|✔|✔|||S|
|
||||
|Enterprise LTSC||||||||
|
||||
|Enterprise||✔|✔|✔|S|||
|
||||
 (green checkmark) = Supported downgrade path</br>
|
||||
 (blue checkmark) = Not considered a downgrade or an upgrade<br>
|
||||
 (X) = not supported or not a downgrade</br>
|
||||
|
||||
| **Edition** | **Home** | **Pro** | **Pro for Workstations** | **Pro Education** | **Education** | **Enterprise LTSC** | **Enterprise** |
|
||||
|-----------------| ------------------------------------ | --------------------------- | ------------------------- | -------------------------------------- | ----------------------------------- | --------------------------------------------- |--------------------------------------------- |
|
||||
| **Home** |  |  |  |  |  |  |  |
|
||||
| **Pro** |  |  |  |  |  |  |  |
|
||||
| **Pro for Workstations** |  |  |  |  |  |  |  |
|
||||
| **Pro Education** |  |  |  |  |  |  |  |
|
||||
| **Education** |  |  |  |  |  |  |  |
|
||||
| **Enterprise LTSC** |  |  |  |  |  |  |  |
|
||||
| **Enterprise** |  |  |  |  |  |  |  |
|
||||
|
||||
> **Windows N/KN**: Windows "N" and "KN" SKUs follow the same rules shown above.
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ ms.collection:
|
||||
search.appverid:
|
||||
- MET150
|
||||
ms.topic: article
|
||||
ms.date: 06/16/2022
|
||||
ms.date: 07/12/2022
|
||||
---
|
||||
|
||||
# Windows 10/11 Subscription Activation
|
||||
@ -26,9 +26,11 @@ Windows 10 Pro supports the Subscription Activation feature, enabling users to "
|
||||
|
||||
With Windows 10, version 1903 and later, the Subscription Activation feature also supports the ability to step-up from Windows 10 Pro Education or Windows 11 Pro Education to the Enterprise grade editions for educational institutions—**Windows 10 Education** or **Windows 11 Education**.
|
||||
|
||||
If you have devices that are licensed for Windows 7, 8, and 8.1 Professional, Microsoft 365 Business Premium provides an upgrade to Windows 10 Pro, which is the prerequisite for deploying [Windows 10 Business](/microsoft-365/business-premium/microsoft-365-business-faqs#what-is-windows-10-business).
|
||||
|
||||
The Subscription Activation feature eliminates the need to manually deploy Enterprise or Education edition images on each target device, then later standing up on-premises key management services such as KMS or MAK based activation, entering Generic Volume License Keys (GVLKs), and subsequently rebooting client devices.
|
||||
|
||||
See the following articles:
|
||||
For more information, see the following articles:
|
||||
|
||||
- [Subscription Activation](#subscription-activation-for-windows-1011-enterprise): An introduction to Subscription Activation for Windows 10/11 Enterprise.
|
||||
- [Subscription Activation for Education](#subscription-activation-for-windows-1011-enterprise): Information about Subscription Activation for Windows 10/11 Education.
|
||||
|
||||
@ -17,8 +17,9 @@
|
||||
href: prepare/windows-autopatch-configure-network.md
|
||||
- name: Enroll your tenant
|
||||
href: prepare/windows-autopatch-enroll-tenant.md
|
||||
- name: Fix issues found by the Readiness assessment tool
|
||||
href: prepare/windows-autopatch-fix-issues.md
|
||||
items:
|
||||
- name: Fix issues found by the Readiness assessment tool
|
||||
href: prepare/windows-autopatch-fix-issues.md
|
||||
- name: Deploy
|
||||
href: deploy/index.md
|
||||
items:
|
||||
@ -32,33 +33,48 @@
|
||||
- name: Update management
|
||||
href: operate/windows-autopatch-update-management.md
|
||||
items:
|
||||
- name: Windows quality updates
|
||||
href: operate/windows-autopatch-wqu-overview.md
|
||||
items:
|
||||
- name: Windows quality end user experience
|
||||
href: operate/windows-autopatch-wqu-end-user-exp.md
|
||||
- name: Windows quality update signals
|
||||
href: operate/windows-autopatch-wqu-signals.md
|
||||
- name: Windows quality update communications
|
||||
- name: Windows updates
|
||||
href:
|
||||
items:
|
||||
- name: Windows quality updates
|
||||
href: operate/windows-autopatch-wqu-overview.md
|
||||
items:
|
||||
- name: Windows quality end user experience
|
||||
href: operate/windows-autopatch-wqu-end-user-exp.md
|
||||
- name: Windows quality update signals
|
||||
href: operate/windows-autopatch-wqu-signals.md
|
||||
- name: Windows feature updates
|
||||
href: operate/windows-autopatch-fu-overview.md
|
||||
items:
|
||||
- name: Windows feature end user experience
|
||||
href: operate/windows-autopatch-fu-end-user-exp.md
|
||||
- name: Windows quality and feature update communications
|
||||
href: operate/windows-autopatch-wqu-communications.md
|
||||
- name: Conflicting and unsupported policies
|
||||
href: operate/windows-autopatch-wqu-unsupported-policies.md
|
||||
- name: Microsoft 365 Apps for enterprise
|
||||
href: operate/windows-autopatch-microsoft-365-apps-enterprise.md
|
||||
- name: Microsoft Edge
|
||||
href: operate/windows-autopatch-edge.md
|
||||
- name: Microsoft Teams
|
||||
href: operate/windows-autopatch-teams.md
|
||||
- name: Deregister a device
|
||||
href: operate/windows-autopatch-deregister-devices.md
|
||||
- name: Maintain the Windows Autopatch environment
|
||||
href: operate/windows-autopatch-maintain-environment.md
|
||||
- name: Submit a support request
|
||||
href: operate/windows-autopatch-support-request.md
|
||||
- name: Deregister a device
|
||||
href: operate/windows-autopatch-deregister-devices.md
|
||||
- name: Unenroll your tenant
|
||||
href: operate/windows-autopatch-unenroll-tenant.md
|
||||
- name: Reference
|
||||
href:
|
||||
items:
|
||||
- name: Update policies
|
||||
href:
|
||||
items:
|
||||
- name: Windows update policies
|
||||
href: operate/windows-autopatch-wqu-unsupported-policies.md
|
||||
- name: Microsoft 365 Apps for enterprise update policies
|
||||
href: references/windows-autopatch-microsoft-365-policies.md
|
||||
- name: Privacy
|
||||
href: references/windows-autopatch-privacy.md
|
||||
- name: Windows Autopatch preview addendum
|
||||
href: references/windows-autopatch-preview-addendum.md
|
||||
|
||||
|
||||
href: references/windows-autopatch-preview-addendum.md
|
||||
@ -14,9 +14,6 @@ msreviewer: hathind
|
||||
|
||||
# Add and verify admin contacts
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The Admin contacts blade isn't available during public preview. However, we'll use the admin contacts provided by you during public preview onboarding.
|
||||
|
||||
There are several ways that Windows Autopatch service communicates with customers. To streamline communication and ensure we're checking with the right people when you [submit a support request](../operate/windows-autopatch-support-request.md), you must provide a set of admin contacts when you onboard with Windows Autopatch.
|
||||
|
||||
> [!IMPORTANT]
|
||||
@ -34,7 +31,7 @@ Your admin contacts will receive notifications about support request updates and
|
||||
| Area of focus | Description |
|
||||
| ----- | ----- |
|
||||
| Devices | <uL><li>Device registration</li><li>Device health</li></ul> |
|
||||
| Updates | <ul><li>Windows quality updates</li><li>Microsoft 365 Apps for enterprise</li><li>Microsoft Teams updates</li><li>Microsoft Edge</li></ul> |
|
||||
| Updates | <ul><li>Windows quality updates</li><li>Windows feature updates</li><li>Microsoft 365 Apps for enterprise updates</li><li>Microsoft Edge updates</li><li>Microsoft Teams updates</li></ul> |
|
||||
|
||||
**To add admin contacts:**
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Register your devices
|
||||
description: This article details how to register devices in Autopatch
|
||||
ms.date: 06/24/2022
|
||||
ms.date: 07/06/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: how-to
|
||||
@ -68,16 +68,17 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
|
||||
- [Supported Windows 10/11 Enterprise and Professional edition versions](/windows/release-health/supported-versions-windows-client)
|
||||
- Either [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid) (personal devices aren't supported).
|
||||
- Managed by Microsoft Endpoint Manager.
|
||||
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune) or [Configuration Manager Co-management](../prepare/windows-autopatch-prerequisites.md#co-management-requirements).
|
||||
- [Switch Microsoft Endpoint Manager-Configuration Manager Co-management workloads to Microsoft Endpoint Manager-Intune](/mem/configmgr/comanage/how-to-switch-workloads) (either set to Pilot Intune or Intune). This includes the following workloads:
|
||||
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune) and/or [Configuration Manager Co-management](/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites#configuration-manager-co-management-requirements).
|
||||
- Must switch the following Microsoft Endpoint Manager-Configuration Manager [Co-management workloads](/mem/configmgr/comanage/how-to-switch-workloads) to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune):
|
||||
- Windows updates policies
|
||||
- Device configuration
|
||||
- Office Click-to-run
|
||||
- Last Intune device check-in completed within the last 28 days.
|
||||
- Last Intune device check in completed within the last 28 days.
|
||||
- Devices must have Serial Number, Model and Manufacturer.
|
||||
> [!NOTE]
|
||||
> Windows Autopatch doesn't support device emulators that don't generate Serial number, Model and Manufacturer. Devices that use a non-supported device emulator fail the **Intune or Cloud-Attached** pre-requisite check. Additionally, devices with duplicated serial numbers will fail to register with Windows Autopatch.
|
||||
|
||||
For more information on how Configuration Manager workloads work, see [How to switch Configuration Manager workloads to Intune](/mem/configmgr/comanage/how-to-switch-workloads).
|
||||
|
||||
See [Prerequisites](../prepare/windows-autopatch-prerequisites.md) for more details.
|
||||
See [Windows Autopatch Prerequisites](../prepare/windows-autopatch-prerequisites.md) for more details.
|
||||
|
||||
## About the Ready and Not ready tabs
|
||||
|
||||
@ -96,7 +97,7 @@ A role defines the set of permissions granted to users assigned to that role. Yo
|
||||
- Intune Service Administrator
|
||||
- Modern Workplace Intune Administrator
|
||||
|
||||
For more information, see [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](/mem/intune/fundamentals/role-based-access-control).
|
||||
For more information, see [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](/mem/intune/fundamentals/role-based-access-control).
|
||||
|
||||
> [!NOTE]
|
||||
> The Modern Workplace Intune Admin role is a custom created role during the Windows Autopatch tenant enrollment process. This role can assign administrators to Endpoint Manager roles, and allows you to create and configure custom Endpoint Manager roles.
|
||||
@ -110,7 +111,9 @@ Registering your devices in Windows Autopatch does the following:
|
||||
|
||||
## Steps to register devices
|
||||
|
||||
**To register devices into Windows Autopatch:**
|
||||
### Physical devices
|
||||
|
||||
**To register physical devices into Windows Autopatch:**
|
||||
|
||||
1. Go to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).
|
||||
2. Select **Windows Autopatch** from the left navigation menu.
|
||||
@ -121,12 +124,43 @@ Registering your devices in Windows Autopatch does the following:
|
||||
> [!NOTE]
|
||||
> The **Windows Autopatch Device Registration** hyperlink is in the center of the Ready tab when there's no devices registered with the Windows Autopatch service. Once you have one or more devices registered with the Windows Autopatch service, the **Windows Autopatch Device registration** hyperlink is at the top of both Ready and Not ready tabs.
|
||||
|
||||
Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices and runs software-based prerequisite checks to try to register them with its service.
|
||||
Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices, and runs software-based prerequisite checks to try to register them with its service.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> It might take up to an hour for a device to change its status from **Ready for User** to **Active** in the Ready tab during the public preview.
|
||||
### Virtual devices
|
||||
|
||||
## Additional device management lifecycle scenarios
|
||||
#### Windows Autopatch on Windows 365 Enterprise Workloads
|
||||
|
||||
With Windows 365 Enterprise, you can include Windows Autopatch onboarding as part of your provision process providing a seamless experience for admins and users to ensure your Cloud PCs are always up to date.
|
||||
|
||||
#### Deploy Windows Autopatch on a Windows 365 Provisioning Policy
|
||||
|
||||
For general guidance, see [Create a Windows 365 Provisioning Policy](/windows-365/enterprise/create-provisioning-policy).
|
||||
|
||||
**To deploy Windows Autopatch on a Windows 365 Provisioning Policy:**
|
||||
|
||||
1. Go to the [Microsoft Endpoint Manager](https://endpoint.microsoft.com/) admin center.
|
||||
1. In the left pane, select **Devices**.
|
||||
1. Navigate to Provisioning > **Windows 365**.
|
||||
1. Select Provisioning policies > **Create policy**.
|
||||
1. Provide a policy name and select **Join Type**. For more information, see [Device join types](/windows-365/enterprise/identity-authentication#device-join-types).
|
||||
1. Select **Next**.
|
||||
1. Choose the desired image and select **Next**.
|
||||
1. Under the **Microsoft managed services** section, select **Windows Autopatch**. Then, select **Next**. If the *Windows Autopatch (preview) cannot manage your Cloud PCs until a Global Admin has finished setting it up.* message appears, you must [enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md) to continue.
|
||||
1. Assign your policy accordingly and select **Next**.
|
||||
1. Select **Create**. Now your newly provisioned Windows 365 Enterprise Cloud PCs will automatically be enrolled and managed by Windows Autopatch.
|
||||
|
||||
#### Deploy Autopatch on Windows 365 for existing Cloud PC
|
||||
|
||||
All your existing Windows 365 Enterprise workloads can be registered into Windows Autopatch by leveraging the same method as your physical devices. For more information, see [Physical devices](#physical-devices).
|
||||
|
||||
#### Contact support
|
||||
|
||||
Support is available either through Windows 365, or Windows Autopatch for update related incidents.
|
||||
|
||||
- For Windows 365 support, see [Get support](/mem/get-support).
|
||||
- For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request).
|
||||
|
||||
## Device management lifecycle scenarios
|
||||
|
||||
There's a few more device lifecycle management scenarios to consider when planning to register devices in Windows Autopatch.
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 168 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 168 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 297 KiB |
@ -14,12 +14,15 @@ msreviewer: hathind
|
||||
|
||||
# Operating with Windows Autopatch
|
||||
|
||||
This section includes information about Windows Autopatch update management, types of updates managed by Windows Autopatch, and how to contact the Windows Autopatch Service Engineering Team:
|
||||
This section includes information about Windows Autopatch update management, types of updates managed by Windows Autopatch, maintaining your Windows Autopatch environment, how to contact the Windows Autopatch Service Engineering Team, and unenrolling your tenant:
|
||||
|
||||
- [Update management](windows-autopatch-update-management.md)
|
||||
- [Windows quality updates](windows-autopatch-wqu-overview.md)
|
||||
- [Windows feature updates](windows-autopatch-fu-overview.md)
|
||||
- [Microsoft 365 Apps for enterprise updates](windows-autopatch-microsoft-365-apps-enterprise.md)
|
||||
- [Microsoft Edge updates](windows-autopatch-edge.md)
|
||||
- [Microsoft Teams updates](windows-autopatch-teams.md)
|
||||
- [Maintain the Windows Autopatch environment](windows-autopatch-maintain-environment.md)
|
||||
- [Deregister devices](windows-autopatch-deregister-devices.md)
|
||||
- [Submit a support request](windows-autopatch-support-request.md)
|
||||
- [Unenroll your tenant](windows-autopatch-unenroll-tenant.md)
|
||||
|
||||
@ -14,7 +14,7 @@ msreviewer: andredm7
|
||||
|
||||
# Deregister a device
|
||||
|
||||
To avoid end-user disruption, device de-registration in Windows Autopatch only deletes the Windows Autopatch device record itself. Device deregistration can't delete Microsoft Intune and/or the Azure Active Directory device records. Microsoft assumes you'll keep managing those devices yourself in some capacity.
|
||||
To avoid end-user disruption, device deregistration in Windows Autopatch only deletes the Windows Autopatch device record itself. Device deregistration can't delete Microsoft Intune and/or the Azure Active Directory device records. Microsoft assumes you'll keep managing those devices yourself in some capacity.
|
||||
|
||||
**To deregister a device:**
|
||||
|
||||
|
||||
@ -0,0 +1,73 @@
|
||||
---
|
||||
title: Windows feature update end user experience
|
||||
description: This article explains the Windows feature update end user experience
|
||||
ms.date: 07/11/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: conceptual
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# Windows feature update end user experience
|
||||
|
||||
Windows Autopatch aims to deploy updates predictably while minimizing the effect to end users by preventing reboots during business hours.
|
||||
|
||||
## User notifications
|
||||
|
||||
In this section we'll review what an end user would see in the following three scenarios:
|
||||
|
||||
1. Typical update experience
|
||||
2. Feature update deadline forces an update
|
||||
3. Feature update grace period
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Autopatch doesn't yet support feature updates without notifying end users.
|
||||
|
||||
### Typical update experience
|
||||
|
||||
In this example, we'll be discussing a device in the First ring. The Autopatch service updates the First ring’s DSS policy to target the next version of Windows 30 days after the start of the release. When the policy is applied to the device, the device will download the update, and notify end users that the new version of Windows is ready to install. The end user can either:
|
||||
|
||||
1. Restart immediately to install the updates
|
||||
1. Schedule the installation, or
|
||||
1. Snooze (the device will attempt to install outside of active hours.)
|
||||
|
||||
In the following example, the user schedules the restart and is notified 15 minutes prior to the scheduled restart time. The user can reschedule, if necessary, but isn't able to reschedule past the deadline.
|
||||
|
||||
:::image type="content" source="../media/windows-feature-typical-update-experience.png" alt-text="Typical Windows feature update experience":::
|
||||
|
||||
### Feature update deadline forces an update
|
||||
|
||||
The following example builds on the scenario outlined in the typical user experience, but the user ignores the notification and selects snooze. Further notifications are received, which the user ignores. The device is also unable to install the updates outside of active hours.
|
||||
|
||||
The deadline specified in the update policy is five days. Therefore, once this deadline is passed, the device will ignore the active hours and force a restart to complete the installation. The user will receive a 15-minute warning, after which, the device will install the update and restart.
|
||||
|
||||
:::image type="content" source="../media/windows-feature-force-update.png" alt-text="Force Windows feature update":::
|
||||
|
||||
### Feature update grace period
|
||||
|
||||
In the following example, the user is on holiday and the device is offline beyond the feature update deadline. The user then returns to work and the device is turned back on.
|
||||
|
||||
Since the deadline has already passed, the device is granted a two-day grace period to install the update and restart. The user will be notified of a pending installation and given options to choose from. Once the two-day grace period has expired, the user is forced to restart with a 15-minute warning notification.
|
||||
|
||||
:::image type="content" source="../media/windows-feature-update-grace-period.png" alt-text="Window feature update grace period":::
|
||||
|
||||
## Servicing window
|
||||
|
||||
Windows Autopatch understands the importance of not disrupting end users but also updating the devices quickly. To achieve this goal, updates are automatically downloaded and installed at an optimal time determined by the device. Device restarts occur outside of active hours until the deadline is reached. By default, active hours are configured dynamically based on device usage patterns. If you wish to specify active hours for your organization, you can do so by deploying both the following policies:
|
||||
|
||||
| Policy | Description |
|
||||
| ----- | ----- |
|
||||
| [Active hours start](/windows/client-management/mdm/policy-csp-update#update-activehoursstart) | This policy controls the start of the protected window where devices won't restart. Supported values are from zero through to 23. Zero is 12∶00AM, representing the hours of the day in local time on that device. |
|
||||
| [Active hours end](/windows/client-management/mdm/policy-csp-update#update-activehoursend) | This policy controls the end of the protected window where devices won't restart. Supported values are from zero through to 23. Zero is 12∶00AM, representing the hours of the day in local time on that device. This value can be no more than 12 hours after the time set in active hours start. |
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Both policies must be deployed for them to work as expected.
|
||||
|
||||
A device won't restart during active hours unless it has passed the date specified by the update deadline policy. Once the device has passed the deadline policy, the device will update as soon as possible.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If your devices must be updated at a specific date or time, they aren't suitable for Windows Autopatch. Allowing you to choose specific dates to update devices would disrupt the rollout schedule and prevent us from delivering the service level objective. The use of any of the following CSPs on a managed device will render it ineligible for management: <ul><li>[Update/ScheduledInstallDay](/windows/client-management/mdm/policy-csp-update#update-scheduledinstallday)</li><li>[Update/ScheduledInstallEveryWeek](/windows/client-management/mdm/policy-csp-update#update-scheduledinstalleveryweek)</li><li>[Update/ScheduledInstallFirstWeek](/windows/client-management/mdm/policy-csp-update#update-scheduledinstallfirstweek)</li><li>[Update/ScheduledInstallFourthWeek](/windows/client-management/mdm/policy-csp-update#update-scheduledinstallfourthweek)</li><li>[Update/ScheduledInstallSecondWeek](/windows/client-management/mdm/policy-csp-update#update-scheduledinstallsecondweek)</li><li>[Update/ScheduledInstallThirdWeek](/windows/client-management/mdm/policy-csp-update#update-scheduledinstallthirdweek)</li><li>[Update/ScheduledInstallTime](/windows/client-management/mdm/policy-csp-update#update-scheduledinstalltime)</li></ul>
|
||||
@ -0,0 +1,106 @@
|
||||
---
|
||||
title: Windows feature updates
|
||||
description: This article explains how Windows feature updates are managed in Autopatch
|
||||
ms.date: 07/11/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: conceptual
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# Windows feature updates
|
||||
|
||||
## Service level objective
|
||||
|
||||
Windows Autopatch aims to keep at least 99% of eligible devices on a supported version of Windows so that they can continue receiving Windows feature updates.
|
||||
|
||||
## Device eligibility
|
||||
|
||||
For a device to be eligible for Windows feature updates as a part of Windows Autopatch it must meet the following criteria:
|
||||
|
||||
| Criteria | Description |
|
||||
| ----- | ----- |
|
||||
| Activity | Devices must have at least six hours of usage, with at least two hours being continuous since the start of the update. |
|
||||
| Intune sync | Devices must have checked with Intune within the last five days. |
|
||||
| Storage space | Devices must have more than one GB (GigaBytes) of free storage space. |
|
||||
| Deployed | Windows Autopatch doesn't update devices that haven't yet been deployed. |
|
||||
| Internet connectivity | Devices must have a steady internet connection, and access to Windows [update endpoints](../prepare/windows-autopatch-configure-network.md). |
|
||||
| Windows edition | Devices must be on a Windows edition supported by Windows Autopatch. For more information, see [Prerequisites](../prepare/windows-autopatch-prerequisites.md). |
|
||||
| Mobile device management (MDM) policy conflict | Devices must not have deployed any policies that would prevent device management. For more information, see [Conflicting and unsupported policies](../operate/windows-autopatch-wqu-unsupported-policies.md). |
|
||||
| Group policy conflict | Devices must not have group policies deployed which would prevent device management. For more information, see [Group policy](windows-autopatch-wqu-unsupported-policies.md#group-policy) |
|
||||
|
||||
## Windows feature update releases
|
||||
|
||||
When the service decides to move to a new version of Windows, the following update schedule is indicative of the minimum amount of time between rings during a rollout.
|
||||
|
||||
The final release schedule is communicated prior to release and may vary a little from the following schedule to account for business weeks or other scheduling considerations. For example, Autopatch may decide to release to the Fast Ring after 62 days instead of 60, if 60 days after the release start was a weekend.
|
||||
|
||||
| Ring | Timeline |
|
||||
| ----- | ----- |
|
||||
| Test | Release start |
|
||||
| First | Release start + 30 days |
|
||||
| Fast | Release start + 60 days |
|
||||
| Broad | Release start + 90 days |
|
||||
|
||||
:::image type="content" source="../media/windows-feature-release-process-timeline.png" alt-text="Windows feature release timeline":::
|
||||
|
||||
## New devices to Windows Autopatch
|
||||
|
||||
If a device is enrolled and it's below Autopatch's currently targeted Windows feature update, that device will update to the service's target version within five days of meeting eligibility criteria.
|
||||
|
||||
If a device is enrolled and it's on, or above the currently targeted Windows feature update, there won't be any change to that device.
|
||||
|
||||
## Feature update configuration
|
||||
|
||||
When releasing a feature update, there are two policies that are configured by the service to create the update schedule described in the previous section. You’ll see four of each of the following policies in your tenant, one for each ring:
|
||||
|
||||
- **Modern Workplace DSS Policy**: This policy is used to control the target version of Windows.
|
||||
- **Modern Workplace Update Policy**: This policy is used to control deferrals and deadlines for feature and quality updates.
|
||||
|
||||
| Ring | Target version (DSS) Policy | Feature update deferral | Feature update deadline | Feature update grace period |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Test | 21H2 | 0 | 5 | 0 |
|
||||
| First | 21H2 | 0 | 5 | 0 |
|
||||
| Fast | 21H2 | 0 | 5 | 2 |
|
||||
| Broad | 21H2 | 0 | 5 | 2 |
|
||||
|
||||
> [!NOTE]
|
||||
> Customers are not able to select a target version for their tenant.
|
||||
|
||||
During a release, the service modifies the Modern Workplace DSS policy to change the target version for a specific ring in Intune. That change is deployed to devices and updates the devices prior to the update deadline.
|
||||
|
||||
To understand how devices will react to the change in the Modern Workplace DSS policy, it's important to understand how deferral, deadline, and grace periods effect devices.
|
||||
|
||||
| Policy | Description |
|
||||
| ----- | ----- |
|
||||
| [Deferrals](/windows/client-management/mdm/policy-csp-update#update-deferqualityupdatesperiodindays) | The deferral policy determines how many days after a release the feature update is offered to a device. The service maximizes control over feature updates by creating individual DSS policies for each ring and modifying the ring's DSS policy to change the target update version. Therefore, the feature update deferral policy for all rings is set to zero days so that a change in the DSS policy is released as soon as possible. |
|
||||
| [Deadlines](/windows/client-management/mdm/policy-csp-update#update-autorestartdeadlineperiodindays) | Before the deadline, restarts can be scheduled by users or automatically scheduled outside of active hours. After the deadline passes, restarts will occur regardless of active hours and users won't be able to reschedule. The deadline for a specific device is set to be the specified number of days after the update is offered to the device. |
|
||||
| [Grace periods](/windows/client-management/mdm/policy-csp-update#update-configuredeadlinegraceperiod) | This policy specifies a minimum number of days after an update is downloaded until the device is automatically restarted. This policy overrides the deadline policy so that if a user comes back from vacation, it prevents the device from forcing a restart to complete the update as soon as it comes online. |
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Deploying deferral, deadline, or grace period policies which conflict with Autopatch's policies will render a device ineligible for management. Also, if any update related to group policy settings are detected, the device will also be ineligible for management.
|
||||
|
||||
## Windows 11 testing
|
||||
|
||||
To allow customers to test Windows 11 in their environment, there's a separate DSS policy that enables you to test Windows 11 before broadly adopting within your environment. When you add devices to the **Modern Workplace - Windows 11 Pre-Release Test Devices** group they'll update to Windows 11.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This group is intended for testing purposes only and shouldn't be used to broadly update to Windows 11 in your environment.
|
||||
|
||||
## Pausing and resuming a release
|
||||
|
||||
You can pause or resume a Windows feature update from the Release management tab in Microsoft Endpoint Manager.
|
||||
|
||||
## Rollback
|
||||
|
||||
Windows Autopatch doesn't support the rollback of feature updates.
|
||||
|
||||
## Incidents and outages
|
||||
|
||||
If devices in your tenant aren't meeting the [service level objective](#service-level-objective) for Windows feature updates, Autopatch will raise an incident will be raised. The Windows Autopatch Service Engineering Team will work to bring those devices onto the latest version of Windows.
|
||||
|
||||
If you're experiencing other issues related to Windows feature updates, [submit a support request](../operate/windows-autopatch-support-request.md).
|
||||
@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Maintain the Windows Autopatch environment
|
||||
description: This article details how to maintain the Windows Autopatch environment
|
||||
ms.date: 07/11/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# Maintain the Windows Autopatch environment
|
||||
|
||||
After you've completed enrollment in Windows Autopatch, some management settings might need to be adjusted. Use the following steps:
|
||||
|
||||
1. Review the [Microsoft Intune settings](#microsoft-intune-settings) described in the following section.
|
||||
1. If any of the items apply to your environment, make the adjustments as described.
|
||||
|
||||
> [!NOTE]
|
||||
> As your operations continue in the following months, if you make changes after enrollment to policies in Microsoft Intune, Azure Active Directory, or Microsoft 365 that affect Windows Autopatch, it's possible that Windows Autopatch could stop operating properly. To avoid problems with the service, check the specific settings described in [Fix issues found by the readiness assessment tool](../prepare/windows-autopatch-fix-issues.md) before you change the policies listed there.
|
||||
|
||||
## Microsoft Intune settings
|
||||
|
||||
| Setting | Description |
|
||||
| ----- | ----- |
|
||||
| Conditional access policies | If you create any new conditional access or multi-factor authentication policies related to Azure AD, or Microsoft Intune after Windows Autopatch enrollment, exclude the Modern Workplace Service Accounts Azure AD group from them. For more information, see [Conditional Access: Users and groups](/azure/active-directory/conditional-access/concept-conditional-access-users-groups). Windows Autopatch maintains separate conditional access policies to restrict access to these accounts.<p>**To review the Windows Autopatch conditional access policy (Modern Workplace – Secure Workstation):**</p><p>Go to Microsoft Endpoint Manager and navigate to **Conditional Access** in **Endpoint Security**. Do **not** modify any Azure AD conditional access policies created by Windows Autopatch that have "**Modern Workplace**" in the name.</p> |
|
||||
| Update rings for Windows 10 or later | For any update rings for Windows 10 or later policies you've created, exclude the **Modern Workplace Devices - All** Azure AD group from each policy. For more information, see [Create and assign update rings](/mem/intune/protect/windows-10-update-rings#create-and-assign-update-rings).<p>Windows Autopatch will also have created some update ring policies. all of which The policies will have "**Modern Workplace**" in the name. For example:</p><ul><li>Modern Workplace Update Policy [Broad]-[Windows Autopatch]</li><li>Modern Workplace Update Policy [Fast]-[Windows Autopatch]</li><li>Modern Workplace Update Policy [First]-[Windows Autopatch]</li><li>Modern Workplace Update Policy [Test]-[Windows Autopatch]</li></ul><p>When you update your own policies, ensure that you don't exclude the **Modern Workplace Devices - All** Azure AD group from the policies that Windows Autopatch created.</p><p>**To resolve the Not ready result:**</p><p>After enrolling into Autopatch, make sure that any update ring policies you have **exclude** the **Modern Workplace Devices - All** Azure Active Directory (AD) group.For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).</p><p>**To resolve the Advisory result:**</p><ol><li>Make sure that any update ring policies you have **exclude** the **Modern Workplace Devices - All** Azure Active Directory (AD) group.</li> <li>If you have assigned Azure AD user groups to these policies, make sure that any update ring policies you have also **exclude** the **Modern Workplace - All** Azure AD group that you add your Windows Autopatch users to (or an equivalent group).</li></ol><p>For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).</p> |
|
||||
@ -82,27 +82,11 @@ Windows Autopatch will either:
|
||||
|
||||
Since quality updates are bundled together into a single release in the [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview), we can't roll back only a portion of the update for Microsoft 365 Apps for enterprise.
|
||||
|
||||
## Conflicting and unsupported policies
|
||||
## Compatibility with Servicing Profiles
|
||||
|
||||
Deploying any of the following policies to a managed device will make that device ineligible for management since the device will prevent us from delivering the service as designed.
|
||||
[Servicing profiles](/deployoffice/admincenter/servicing-profile) is a feature in the [Microsoft 365 Apps admin center](https://config.office.com/) that provides controlled update management of monthly Office updates, including controls for user and device targeting, scheduling, rollback, and reporting.
|
||||
|
||||
### Update policies
|
||||
|
||||
Window Autopatch deploys mobile device management (MDM) policies to configure Microsoft 365 Apps and requires a specific configuration. If any [Microsoft 365 Apps update settings](/deployoffice/configure-update-settings-microsoft-365-apps) are deployed which conflict with our policies, then the device won't be eligible for management.
|
||||
|
||||
| Update setting | Value | Usage reason |
|
||||
| ----- | ----- | ----- |
|
||||
| Set updates to occur automatically | Enabled | Enable automatic updates |
|
||||
| Specify a location to look for updates | Blank | Don't use this setting since it overwrites the update branch |
|
||||
| Update branch | Monthly Enterprise | Supported branch for Windows Autopatch |
|
||||
| Specify the version of Microsoft 365 Apps to update to | Variable | Used to roll back to a previous version if an error occurs |
|
||||
| Set a deadline by when updates must be applied | 3 | Update deadline |
|
||||
| Hide update notifications from users | Turned off | Users should be notified when Microsoft 365 Apps are being updated |
|
||||
| Hide the option to turn on or off automatic Office updates | Turned on | Prevents users from disabling automatic updates |
|
||||
|
||||
## Microsoft 365 Apps servicing profiles
|
||||
|
||||
A service profile takes precedence over other management tools, such as Microsoft Endpoint Manager or the Office Deployment Tool. This means that the servicing profile will affect all devices that meet the [device eligibility requirements](#device-eligibility) regardless of existing management tools in your environment. So, if you're targeting a managed device with a servicing profile it will be ineligible for Microsoft 365 App update management.
|
||||
A [service profile](/deployoffice/admincenter/servicing-profile#compatibility-with-other-management-tools) takes precedence over other management tools, such as Microsoft Endpoint Manager or the Office Deployment Tool. This means that the servicing profile will affect all devices that meet the [device eligibility requirements](#device-eligibility) regardless of existing management tools in your environment. So, if you're targeting a managed device with a servicing profile it will be ineligible for Microsoft 365 App update management.
|
||||
|
||||
However, the device may still be eligible for other managed updates. For more information about a device's eligibility for a given [update type](windows-autopatch-update-management.md#update-types), see the Device eligibility section of each respective update type.
|
||||
|
||||
|
||||
@ -0,0 +1,57 @@
|
||||
---
|
||||
title: Unenroll your tenant
|
||||
description: This article explains what unenrollment means for your organization and what actions you must take.
|
||||
ms.date: 07/11/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# Unenroll your tenant
|
||||
|
||||
If you're looking to unenroll your tenant from Windows Autopatch, this article details what unenrollment means for your organization and what actions you must take.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must be a Global Administrator to unenroll your tenant.
|
||||
|
||||
Unenrolling from Windows Autopatch requires manual actions from both you and from the Windows Autopatch Service Engineering Team. The Windows Autopatch Service Engineering Team will:
|
||||
|
||||
- Remove Windows Autopatch access to your tenant.
|
||||
- Deregister your devices from the Windows Autopatch service. Deregistering your devices from Windows Autopatch won't remove your devices from Intune, Azure AD or Configuration Manager. The Windows Autopatch Service Engineering Team follows the same process and principles as laid out in Deregister a device.
|
||||
- Delete all data that we've stored in the Windows Autopatch data storage.
|
||||
|
||||
> [!NOTE]
|
||||
> We will **not** delete any of your customer or Intune data.
|
||||
|
||||
## Microsoft's responsibilities during unenrollment
|
||||
|
||||
| Responsibility | Description |
|
||||
| ----- | ----- |
|
||||
| Windows Autopatch data | Windows Autopatch will delete user data that is within the Windows Autopatch service. We won’t make changes to any other data. For more information about how data is used in Windows Autopatch, see [Privacy](../references/windows-autopatch-privacy.md). |
|
||||
| Windows Autopatch cloud service accounts | Windows Autopatch will remove the cloud service accounts created during the enrollment process. The accounts are:<ul><li>MsAdmin</li><li>MsAdminInt</li><li>MsTest</li></ul> |
|
||||
| Conditional access policy | Windows Autopatch will remove the Modern Workplace – Secure Workstation conditional access policy. |
|
||||
| Microsoft Endpoint Manager roles | Windows Autopatch will remove the Modern Workplace Intune Admin role. |
|
||||
|
||||
## Your responsibilities after unenrolling your tenant
|
||||
|
||||
| Responsibility | Description |
|
||||
| ----- | ----- |
|
||||
| Updates | After the Windows Autopatch service is unenrolled, we’ll no longer provide updates to your devices. You must ensure that your devices continue to receive updates through your own policies to ensure they're secure and up to date. |
|
||||
| Optional Windows Autopatch configuration | Windows Autopatch won’t remove the configuration policies or groups used to enable updates on your devices. You're responsible for these policies following tenant unenrollment. If you don’t wish to use these policies for your devices after unenrollment, you may safely delete them. |
|
||||
|
||||
## Unenroll from Windows Autopatch
|
||||
|
||||
**To unenroll from Windows Autopatch:**
|
||||
|
||||
1. [Submit a support request](windows-autopatch-support-request.md) and request to unenroll from the Windows Autopatch service.
|
||||
1. The Windows Autopatch Service Engineering Team will communicate with your IT Administrator to confirm your intent to unenroll from the service.
|
||||
1. You'll have 14 days to review and confirm the communication sent by the Windows Autopatch Service Engineering Team.
|
||||
2. The Windows Autopatch Service Engineering Team can proceed sooner than 14 days if your confirmation arrives sooner.
|
||||
1. The Windows Autopatch Service Engineering Team will proceed with the removal of all items listed under [Microsoft's responsibilities during unenrollment](#microsofts-responsibilities-during-unenrollment).
|
||||
1. The Windows Autopatch Service Engineering Team will inform you when unenrollment is complete.
|
||||
1. You’re responsible for the items listed under [Your responsibilities after unenrolling your tenant](#your-responsibilities-after-unenrolling-your-tenant).
|
||||
@ -20,7 +20,8 @@ Keeping your devices up to date is a balance of speed and stability. Windows Aut
|
||||
|
||||
| Update type | Description |
|
||||
| ----- | ----- |
|
||||
| Window quality update | Windows Autopatch uses four update rings to manage Windows quality updates. For more detailed information, see [Windows quality updates](../operate/windows-autopatch-wqu-overview.md). |
|
||||
| Windows quality update | Windows Autopatch uses four update rings to manage Windows quality updates. For more detailed information, see [Windows quality updates](../operate/windows-autopatch-wqu-overview.md). |
|
||||
| Windows feature update | Windows Autopatch uses four update rings to manage Windows feature updates. For more detailed information, see [Windows feature updates](windows-autopatch-fu-overview.md).
|
||||
| Anti-virus definition | Updated with each scan. |
|
||||
| Microsoft 365 Apps for enterprise | For more information, see [Microsoft 365 Apps for enterprise](windows-autopatch-microsoft-365-apps-enterprise.md). |
|
||||
| Microsoft Edge | For more information, see [Microsoft Edge](../operate/windows-autopatch-edge.md). |
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: End user experience
|
||||
title: Windows quality update end user experience
|
||||
description: This article explains the Windows quality update end user experience
|
||||
ms.date: 05/30/2022
|
||||
ms.prod: w11
|
||||
@ -12,7 +12,7 @@ manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# End user experience
|
||||
# Windows quality update end user experience
|
||||
|
||||
Windows Autopatch aims to deploy updates predictably while minimizing the effect to end users by preventing reboots during business hours.
|
||||
|
||||
|
||||
@ -72,8 +72,11 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win
|
||||
|
||||
If we pause the release, a policy will be deployed which prevents devices from updating while the issue is investigated. Once the issue is resolved, the release will be resumed.
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Autopatch doesn't allow you to request that a release be paused or resumed during public preview.
|
||||
You can pause or resume a Windows quality update from the Release management tab in Microsoft Endpoint Manager.
|
||||
|
||||
## Rollback
|
||||
|
||||
Windows Autopatch will rollback updates if we detect a [significant issue with a release](../operate/windows-autopatch-wqu-signals.md).
|
||||
|
||||
## Incidents and outages
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Conflicting and unsupported policies
|
||||
description: This article explains the conflicting and unsupported policies in Windows quality updates
|
||||
ms.date: 05/30/2022
|
||||
title: Windows update policies
|
||||
description: This article explains Windows update policies in Windows Autopatch
|
||||
ms.date: 07/07/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: conceptual
|
||||
@ -12,11 +12,94 @@ manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# Conflicting and unsupported policies
|
||||
# Windows update policies
|
||||
|
||||
## Update rings for Windows 10 and later
|
||||
|
||||
The following policies contain settings which apply to both Windows quality and feature updates. After onboarding there will be four of these policies in your tenant with the following naming convention:
|
||||
|
||||
**Modern Workplace Update Policy [ring name] – [Windows Autopatch]**
|
||||
|
||||
### Windows 10 and later update settings
|
||||
|
||||
| Setting name | Test | First | Fast | Broad |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Microsoft product updates | Allow | Allow | Allow | Allow |
|
||||
| Windows drivers | Allow | Allow | Allow | Allow |
|
||||
| Quality update deferral period | 0 | 1 | 6 | 9 |
|
||||
| Feature update deferral period | 0 | 0 | 0 | 0 |
|
||||
| Upgrade Windows 10 to latest Windows 11 release | No | No | No | No |
|
||||
| Set feature update uninstall period | 30 days | 30 days | 30 days | 30 days |
|
||||
| Servicing channel | General availability | General availability | General availability | General availability |
|
||||
|
||||
### Windows 10 and later user experience settings
|
||||
|
||||
| Setting name | Test | First | Fast | Broad |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Automatic update behaviour | Reset to default | Reset to default | Reset to default | Reset to default |
|
||||
| Restart checks | Allow | Allow | Allow | Allow |
|
||||
| Option to pause updates | Disable | Disable | Disable | Disable |
|
||||
| Option to check for Windows updates | Default | Default | Default | Default |
|
||||
| Change notification update level | Default | Default | Default | Default |
|
||||
| Deadline for feature updates | 5 | 5 | 5 | 5 |
|
||||
| Deadline for quality updates | 0 | 2 | 2 | 5 |
|
||||
| Grace period | 0 | 2 | 2 | 2 |
|
||||
| Auto-restart before deadline | Yes | Yes | Yes | Yes |
|
||||
|
||||
### Windows 10 and later assignments
|
||||
|
||||
| Setting name | Test | First | Fast | Broad |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Included groups | Modern Workplace Devices–Windows Autopatch-Test | Modern Workplace Devices–Windows Autopatch-First | Modern Workplace Devices–Windows Autopatch-Fast | Modern Workplace Devices–Windows Autopatch-Broad |
|
||||
| Excluded groups | None | None | None | None |
|
||||
|
||||
## Feature update policies
|
||||
|
||||
The service deploys policies using Microsoft Intune to control how feature updates are deployed to devices.
|
||||
|
||||
### Feature updates for Windows 10 and later
|
||||
|
||||
These policies control the minimum target version of Windows which a device is meant to accept. Throughout the rest of the article, you will see these policies referred to as DSS policies. After onboarding there will be four of these policies in your tenant with the following naming convention:
|
||||
|
||||
**Modern Workplace DSS Policy [ring name]**
|
||||
|
||||
#### Feature update deployment settings
|
||||
|
||||
| Setting name | Test | First | Fast | Broad |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Name | Current targeted version of Windows | Current targeted version of Windows | Current targeted version of Windows | Current targeted version of Windows |
|
||||
| Rollout options | Immediate start | Immediate start | Immediate start | Immediate start |
|
||||
|
||||
#### Feature update policy assignments
|
||||
|
||||
| Setting name | Test | First | Fast | Broad |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Included groups | Modern Workplace Devices–Windows Autopatch-Test | Modern Workplace Devices–Windows Autopatch-First | Modern Workplace Devices–Windows Autopatch-Fast | Modern Workplace Devices–Windows Autopatch-Broad |
|
||||
| Excluded groups | Modern Workplace – Windows 11 Pre-Release Test Devices | Modern Workplace – Windows 11 Pre-Release Test Devices | Modern Workplace – Windows 11 Pre-Release Test Devices | Modern Workplace – Windows 11 Pre-Release Test Devices |
|
||||
|
||||
#### Windows 11 testing
|
||||
|
||||
To allow customers to test Windows 11 in their environment, there's a separate DSS policy which enables you to test Windows 11 before broadly adopting within your environment.
|
||||
|
||||
##### Windows 11 deployment setting
|
||||
|
||||
| Setting name | Test |
|
||||
| ----- | ----- |
|
||||
| Name | Windows 11 |
|
||||
| Rollout options | Immediate start |
|
||||
|
||||
##### Windows 11 assignments
|
||||
|
||||
| Setting name | Test |
|
||||
| ----- | ----- |
|
||||
| Included groups | Modern Workplace – Windows 11 Pre-Release Test Devices |
|
||||
| Excluded groups | None |
|
||||
|
||||
## Conflicting and unsupported policies
|
||||
|
||||
Deploying any of the following policies to a Windows Autopatch device will make that device ineligible for management since the device will prevent us from delivering the service as designed.
|
||||
|
||||
## Update policies
|
||||
### Update policies
|
||||
|
||||
Window Autopatch deploys mobile device management (MDM) policies to configure devices and requires a specific configuration. If any policies from the [Update Policy CSP](/windows/client-management/mdm/policy-csp-update) are deployed to devices that aren't on the permitted list, those devices will be excluded from management.
|
||||
|
||||
@ -26,7 +109,7 @@ Window Autopatch deploys mobile device management (MDM) policies to configure de
|
||||
| [Active hours end](/windows/client-management/mdm/policy-csp-update#update-activehoursend) | Update/ActiveHoursEnd | This policy controls the end of the protected window where devices won't reboot.<p><p>Supported values are from zero through to 23, where zero is 12∶00AM, representing the hours of the day in local time on that device. This value can be no more than 12 hours after the time set in active hours start. |
|
||||
| [Active hours max range](/windows/client-management/mdm/policy-csp-update#update-activehoursmaxrange) | Update/ActiveHoursMaxRange | Allows the IT admin to specify the max active hours range.<p><p>This value sets the maximum number of active hours from the start time. Supported values are from eight through to 18. |
|
||||
|
||||
## Group policy
|
||||
### Group policy
|
||||
|
||||
Group policy takes precedence over mobile device management (MDM) policies. For Windows quality updates, if any group policies are detected which modify the following hive in the registry, the device will be ineligible for management:
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ metadata:
|
||||
description: Answers to frequently asked questions about Windows Autopatch.
|
||||
ms.prod: w11
|
||||
ms.topic: faq
|
||||
ms.date: 06/02/2022
|
||||
ms.date: 07/06/2022
|
||||
audience: itpro
|
||||
ms.localizationpriority: medium
|
||||
manager: dougeby
|
||||
@ -25,7 +25,7 @@ sections:
|
||||
- question: Is Windows 365 for Enterprise supported with Windows Autopatch?
|
||||
answer: |
|
||||
Windows Autopatch supports Windows 365 for Enterprise. Windows 365 for Business isn't supported.
|
||||
- question: Does Windows Autopatch support Windows Education (A3) or Windows Front Line Worker (F3) licensing?
|
||||
- question: Does Windows Autopatch support Windows Education (A3/A5) or Windows Front Line Worker (F3) licensing?
|
||||
answer: |
|
||||
Autopatch isn't available for 'A' or 'F' series licensing.
|
||||
- question: Will Windows Autopatch support local domain join Windows 10?
|
||||
@ -34,6 +34,9 @@ sections:
|
||||
- question: Will Windows Autopatch be available for state and local government customers?
|
||||
answer: |
|
||||
Windows Autopatch is available for all Windows E3 customers using Azure commercial cloud. However, Autopatch isn't currently supported for government cloud (GCC) customers.
|
||||
- question: What if I enrolled into Windows Autopatch using the promo code? Will I still have access to the service?
|
||||
answer: |
|
||||
Yes. For those who used the promo code to access Windows Autopatch during public preview, you'll continue to have access to Windows Autopatch even when the promo code expires. There is no additional action you have to take to continue using Windows Autopatch.
|
||||
- name: Requirements
|
||||
questions:
|
||||
- question: What are the prerequisites for Windows Autopatch?
|
||||
@ -43,7 +46,7 @@ sections:
|
||||
- [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
|
||||
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune)
|
||||
Additional pre-requisites for devices managed by Configuration Manager:
|
||||
- [Co-management](../prepare/windows-autopatch-prerequisites.md#co-management-requirements)
|
||||
- [Configuration Manager Co-management requirements](../prepare/windows-autopatch-prerequisites.md#configuration-manager-co-management-requirements)
|
||||
- [A supported version of Configuration Manager](/mem/configmgr/core/servers/manage/updates#supported-versions)
|
||||
- [Switch workloads for device configuration, Windows Update and Microsoft 365 Apps from Configuration Manager to Intune](/mem/configmgr/comanage/how-to-switch-workloads) (minimum Pilot Intune. Pilot collection must contain the devices you want to register into Autopatch.)
|
||||
- question: What are the licensing requirements for Windows Autopatch?
|
||||
@ -59,6 +62,15 @@ sections:
|
||||
- question: Can Autopatch customers individually approve or deny devices?
|
||||
answer: |
|
||||
No you can't individually approve or deny devices. Once a device is registered with Windows Autopatch, updates are rolled out to the devices according to its ring assignment. Individual device level control isn't supported.
|
||||
- question: Does Autopatch on Windows 365 Cloud PCs have any feature difference from a physical device?
|
||||
answer: |
|
||||
No, Windows 365 Enterprise Cloud PC's support all features of Windows Autopatch. For more information, see [Virtual devices](/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices#virtual-devices).
|
||||
- question: Do my Cloud PCs appear any differently in the Windows Autopatch admin center?
|
||||
answer: |
|
||||
Cloud PC displays the model as the license type you have provisioned. For more information, see [Virtual devices](/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices#virtual-devices).
|
||||
- question: Can I run Autopatch on my Windows 365 Business Workloads?
|
||||
answer: |
|
||||
No. Autopatch is only available on enterprise workloads. For more information, see [Virtual devices](/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices#virtual-devices).
|
||||
- name: Update Management
|
||||
questions:
|
||||
- question: What systems does Windows Autopatch update?
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What is Windows Autopatch? (preview)
|
||||
title: What is Windows Autopatch?
|
||||
description: Details what the service is and shortcuts to articles
|
||||
ms.date: 05/30/2022
|
||||
ms.date: 07/11/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: conceptual
|
||||
@ -12,10 +12,7 @@ manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# What is Windows Autopatch? (preview)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **Windows Autopatch is in public preview**. It's actively being developed and may not be complete. You can test and use these features in production environments and [provide feedback](https://go.microsoft.com/fwlink/?linkid=2195593) or start a discussion in our [Windows Autopatch Tech Community](https://aka.ms/Community/WindowsAutopatch).
|
||||
# What is Windows Autopatch?
|
||||
|
||||
Windows Autopatch is a cloud service that automates Windows, Microsoft 365 Apps for enterprise, Microsoft Edge, and Microsoft Teams updates to improve security and productivity across your organization.
|
||||
|
||||
@ -39,6 +36,7 @@ The goal of Windows Autopatch is to deliver software updates to registered devic
|
||||
| Management area | Service level objective |
|
||||
| ----- | ----- |
|
||||
| [Windows quality updates](../operate/windows-autopatch-wqu-overview.md) | Windows Autopatch aims to keep at least 95% of eligible devices on the latest Windows quality update 21 days after release. |
|
||||
| [Windows feature updates](../operate/windows-autopatch-fu-overview.md) | Windows Autopatch aims to keep at least 99% of eligible devices on a supported version of Windows so that they can continue receiving Windows feature updates. |
|
||||
| [Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md) | Windows Autopatch aims to keep at least 90% of eligible devices on a supported version of the Monthly Enterprise Channel (MEC). |
|
||||
| [Microsoft Edge](../operate/windows-autopatch-edge.md) | Windows Autopatch configures eligible devices to benefit from Microsoft Edge's progressive rollouts on the Stable channel. |
|
||||
| [Microsoft Teams](../operate/windows-autopatch-teams.md) | Windows Autopatch allows eligible devices to benefit from the standard automatic update channel. |
|
||||
@ -59,33 +57,13 @@ Microsoft remains committed to the security of your data and the [accessibility]
|
||||
|
||||
## Need more details?
|
||||
|
||||
### Prepare
|
||||
| Area | Description |
|
||||
| ----- | ----- |
|
||||
| Prepare | The following articles describe the mandatory steps to prepare and enroll your tenant into Windows Autopatch:<ul><li>[Prerequisites](../prepare/windows-autopatch-prerequisites.md)</li><li>[Configure your network](../prepare/windows-autopatch-configure-network.md)</li><li>[Enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md)</li><li>[Fix issues found by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md)</li></ul> |
|
||||
| Deploy | Once you've enrolled your tenant, this section instructs you to:<ul><li>[Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md)</li><li>[Register your devices](../deploy/windows-autopatch-register-devices.md)</li></ul> |
|
||||
| Operate | This section includes the following information about your day-to-day life with the service:<ul><li>[Update management](../operate/windows-autopatch-update-management.md)</li><li>[Maintain your Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md)</li><li>[Submit a support request](../operate/windows-autopatch-support-request.md)</li><li>[Deregister a device](../operate/windows-autopatch-deregister-devices.md)</li></ul>
|
||||
| References | This section includes the following articles:<ul><li>[Windows update policies](../operate/windows-autopatch-wqu-unsupported-policies.md)</li><li>[Microsoft 365 Apps for enterprise update policies](../references/windows-autopatch-microsoft-365-policies.md)</li><li>[Privacy](../references/windows-autopatch-privacy.md)</li><li>[Windows Autopatch Preview Addendum](../references/windows-autopatch-preview-addendum.md)</li></ul> |
|
||||
|
||||
The following articles describe the mandatory steps to prepare and enroll your tenant into Windows Autopatch:
|
||||
### Have feedback or would like to start a discussion?
|
||||
|
||||
- [Prerequisites](../prepare/windows-autopatch-prerequisites.md)
|
||||
- [Configure your network](../prepare/windows-autopatch-configure-network.md)
|
||||
- [Enroll your tenant with Windows Autopatch](../prepare/windows-autopatch-enroll-tenant.md)
|
||||
- [Fix issues found by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md)
|
||||
|
||||
### Deploy
|
||||
|
||||
Once you've enrolled your tenant, this section instructs you to:
|
||||
|
||||
- [Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md)
|
||||
- [Register your devices](../deploy/windows-autopatch-register-devices.md)
|
||||
|
||||
### Operate
|
||||
|
||||
This section includes the following information about your day-to-day life with the service:
|
||||
|
||||
- [Update management](../operate/windows-autopatch-update-management.md)
|
||||
- [Submit a support request](../operate/windows-autopatch-support-request.md)
|
||||
- [Deregister a device](../operate/windows-autopatch-deregister-devices.md)
|
||||
|
||||
### References
|
||||
|
||||
This section includes the following articles:
|
||||
|
||||
- [Privacy](../references/windows-autopatch-privacy.md)
|
||||
- [Windows Autopatch Preview Addendum](../references/windows-autopatch-preview-addendum.md)
|
||||
You can [provide feedback](https://go.microsoft.com/fwlink/?linkid=2195593) or start a discussion in our [Windows Autopatch Tech Community](https://aka.ms/Community/WindowsAutopatch).
|
||||
|
||||
@ -19,4 +19,4 @@ The following articles describe the steps you must take to onboard with Windows
|
||||
1. [Review the prerequisites](windows-autopatch-prerequisites.md)
|
||||
1. [Configure your network](windows-autopatch-configure-network.md)
|
||||
1. [Enroll your tenant](windows-autopatch-enroll-tenant.md)
|
||||
1. [Fix issues found in the Readiness assessment tool](windows-autopatch-fix-issues.md)
|
||||
1. [Fix issues found in the Readiness assessment tool](windows-autopatch-fix-issues.md)
|
||||
|
||||
@ -32,7 +32,7 @@ The Windows Autopatch URL is used for anything our service runs on the customer
|
||||
|
||||
| Microsoft service | URLs required on allowlist |
|
||||
| ----- | ----- |
|
||||
| Windows Autopatch | <ul><li>mmdcustomer.microsoft.com</li><li>mmdls.microsoft.com</li></ul>|
|
||||
| Windows Autopatch | <ul><li>mmdcustomer.microsoft.com</li><li>mmdls.microsoft.com</li><li>logcollection.mmd.microsoft.com</li><li>support.mmd.microsoft.com</li></ul>|
|
||||
|
||||
### Required Microsoft product endpoints
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Enroll your tenant
|
||||
description: This article details how to enroll your tenant
|
||||
ms.date: 05/30/2022
|
||||
ms.date: 07/11/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: how-to
|
||||
@ -16,7 +16,10 @@ msreviewer: hathind
|
||||
|
||||
Before you enroll in Windows Autopatch, there are settings and other parameters you must set ahead of time.
|
||||
|
||||
The Readiness assessment tool, accessed through the [Windows Autopatch admin center](https://endpoint.microsoft.com/), checks management or configuration -related settings. This tool allows you to check the relevant settings and detailed steps to fix any settings that aren't configured properly for Windows Autopatch.
|
||||
> [!IMPORTANT]
|
||||
> You must be a Global Administrator to enroll your tenant.
|
||||
|
||||
The Readiness assessment tool, accessed through the [Windows Autopatch admin center](https://endpoint.microsoft.com/), checks management or configuration-related settings. This tool allows you to check the relevant settings, and details steps to fix any settings that aren't configured properly for Windows Autopatch.
|
||||
|
||||
## Step 1: Review all prerequisites
|
||||
|
||||
@ -27,18 +30,18 @@ To start using the Windows Autopatch service, ensure you meet the [Windows Autop
|
||||
> [!IMPORTANT]
|
||||
> The online Readiness assessment tool helps you check your readiness to enroll in Windows Autopatch for the first time. Once you enroll, you'll no longer be able to access the tool again.
|
||||
|
||||
The Readiness assessment tool checks the settings in [Microsoft Endpoint Manager](#microsoft-intune-settings) (specifically, Microsoft Intune) and [Azure Active Directory](#azure-active-directory-settings) (Azure AD) to ensure they'll work with Windows Autopatch. We aren't, however, checking the workloads in Configuration Manager necessary for Windows Autopatch. For more information about workload prerequisites, see [Co-management requirements](../prepare/windows-autopatch-prerequisites.md#co-management-requirements).
|
||||
The Readiness assessment tool checks the settings in [Microsoft Endpoint Manager](#microsoft-intune-settings) (specifically, Microsoft Intune) and [Azure Active Directory](#azure-active-directory-settings) (Azure AD) to ensure they'll work with Windows Autopatch. We aren't, however, checking the workloads in Configuration Manager necessary for Windows Autopatch. For more information about workload prerequisites, see [Configuration Manager Co-management requirements](../prepare/windows-autopatch-prerequisites.md#configuration-manager-co-management-requirements).
|
||||
|
||||
**To access and run the Readiness assessment tool:**
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must be a Global Administrator to enroll your tenant.
|
||||
> You must be a Global Administrator to run the Readiness assessment tool.
|
||||
|
||||
1. Go to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).
|
||||
2. In the left pane, select Tenant administration and then navigate to Windows Autopatch > **Tenant enrollment**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you don't see the Tenant enrollment blade, this is because you don't meet the prerequisites or the proper licenses. For more information, see [Windows Autopatch prerequisites](windows-autopatch-prerequisites.md).
|
||||
> If you don't see the Tenant enrollment blade, this is because you don't meet the prerequisites or the proper licenses. For more information, see [Windows Autopatch prerequisites](windows-autopatch-prerequisites.md#more-about-licenses).
|
||||
|
||||
A Global Administrator should be used to run this tool. Other roles, such as the Global Reader and Intune Administrator have insufficient permissions to complete the checks on Conditional Access Policies and Multi-factor Authentication. For more information about the extra permissions, see [Conditional access policies](../prepare/windows-autopatch-fix-issues.md#conditional-access-policies).
|
||||
|
||||
@ -50,8 +53,8 @@ The following are the Microsoft Intune settings:
|
||||
|
||||
| Check | Description |
|
||||
| ----- | ----- |
|
||||
| Update rings for Windows 10 or later | Verifies that Intune's Update rings for Windows 10 or later policy doesn't target all users or all devices. The policy shouldn't target any Windows Autopatch devices. |
|
||||
| Unlicensed admin | Verifies that this setting is enabled to avoid a "lack of permissions" error when we interact with your Azure Active Directory (AD) organization. |
|
||||
| Update rings for Windows 10 or later | Verifies that Intune's Update rings for Windows 10 or later policy doesn't target all users or all devices. Policies of this type shouldn't target any Windows Autopatch devices. For more information, see [Configure update rings for Windows 10 and later in Intune](/mem/intune/protect/windows-10-update-rings). |
|
||||
| Unlicensed admin | Verifies that this setting is enabled to avoid a "lack of permissions" error when we interact with your Azure Active Directory (AD) organization. For more information, see [Unlicensed admins in Microsoft Intune](/mem/intune/fundamentals/unlicensed-admins). |
|
||||
|
||||
### Azure Active Directory settings
|
||||
|
||||
@ -59,38 +62,27 @@ The following are the Azure Active Directory settings:
|
||||
|
||||
| Check | Description |
|
||||
| ----- | ----- |
|
||||
| Conditional access | Verifies that conditional access policies and multi-factor authentication aren't assigned to all users.<p><p>Conditional access policies shouldn't be assigned to Windows Autopatch service accounts. For more information on steps to take, see [Conditional access policies](../prepare/windows-autopatch-fix-issues.md#conditional-access-policies). |
|
||||
| Windows Autopatch service accounts | Checks that no usernames conflict with ones that Windows Autopatch reserves for its own use. |
|
||||
| Conditional access | Verifies that conditional access policies and multi-factor authentication aren't assigned to all users.<p><p>Your conditional access policies must not prevent our service accounts from accessing the service and must not require multi-factor authentication. For more information, see [Conditional access policies](../prepare/windows-autopatch-fix-issues.md#conditional-access-policies). |
|
||||
| Windows Autopatch cloud service accounts | Checks that no usernames conflict with ones that Windows Autopatch reserves for its own use. The cloud service accounts are:<ul><li>MsAdmin</li><li>MsAdminInt</li><li>MsTest</li></ul> For more information, see [Tenant access](../references/windows-autopatch-privacy.md#tenant-access). |
|
||||
| Security defaults | Checks whether your Azure Active Directory organization has security defaults enabled. |
|
||||
| Licenses | Checks that you've obtained the necessary [licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses). |
|
||||
|
||||
### Check results
|
||||
|
||||
For each check, the tool will report one of four possible results:
|
||||
|
||||
| Result | Meaning |
|
||||
| ----- | ----- |
|
||||
| Ready | No action is required before completing enrollment. |
|
||||
| Advisory | Follow the steps in the tool or this article for the best experience with enrollment and for users.<p><p>You can complete enrollment, but you must fix these issues before you deploy your first device. |
|
||||
| Not ready | Enrollment will fail if you don't fix these issues. Follow the steps in the tool or this article to resolve them. |
|
||||
| Not ready | You must fix these issues before enrollment. You won’t be able to enroll into Windows Autopatch if you don't fix these issues. Follow the steps in the tool or this article to resolve them. |
|
||||
| Error | The Azure Active Directory (AD) role you're using doesn't have sufficient permissions to run this check. |
|
||||
|
||||
### Seeing issues with your tenant?
|
||||
## Step 3: Fix issues with your tenant
|
||||
|
||||
If the Readiness assessment tool is displaying issues with your tenant, see [Fix issues found by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md) for more information on how to remediate.
|
||||
|
||||
### Delete data collected from the Readiness assessment tool
|
||||
|
||||
Windows Autopatch retains the data associated with these checks for 12 months after the last time you ran a check in your Azure Active Directory organization (tenant). After 12 months, we retain the data in a de-identified form. You can choose to delete the data we collect directly within the Readiness assessment tool.
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Autopatch will only delete the results we collect within the Readiness assessment tool; Autopatch won't delete any other tenant-level data.
|
||||
|
||||
**To delete the data we collect:**
|
||||
|
||||
1. Go to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).
|
||||
2. Navigate to Windows Autopatch > **Tenant enrollment**.
|
||||
3. Select **Delete all data**.
|
||||
|
||||
## Step 3: Enroll your tenant
|
||||
## Step 4: Enroll your tenant
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must be a Global Administrator to enroll your tenant.
|
||||
@ -105,4 +97,24 @@ Within the Readiness assessment tool, you'll now see the **Enroll** button. By s
|
||||
- Provide Windows Autopatch with IT admin contacts.
|
||||
- Setup of the Windows Autopatch service on your tenant. This step is where we'll create the policies, groups and accounts necessary to run the service.
|
||||
|
||||
Once these actions are complete, you've now successfully enrolled your tenant. Ensure you've [added and verified your admin contacts](../deploy/windows-autopatch-admin-contacts.md) before you [register your devices](../deploy/windows-autopatch-register-devices.md).
|
||||
Once these actions are complete, you've now successfully enrolled your tenant.
|
||||
|
||||
### Delete data collected from the Readiness assessment tool
|
||||
|
||||
You can choose to delete the data we collect directly within the Readiness assessment tool.
|
||||
|
||||
Windows Autopatch retains the data associated with these checks for 12 months after the last time you ran a check in your Azure Active Directory organization (tenant). After 12 months, we retain the data in a de-identified form.
|
||||
|
||||
> [!NOTE]
|
||||
> Windows Autopatch will only delete the results we collect within the Readiness assessment tool; Autopatch won't delete any other tenant-level data.
|
||||
|
||||
**To delete the data we collect:**
|
||||
|
||||
1. Go to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).
|
||||
2. Navigate to Windows Autopatch > **Tenant enrollment**.
|
||||
3. Select **Delete all data**.
|
||||
|
||||
## Next steps
|
||||
|
||||
1. Maintain your [Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md).
|
||||
1. Ensure you've [added and verified your admin contacts](../deploy/windows-autopatch-admin-contacts.md) before you [register your devices](../deploy/windows-autopatch-register-devices.md).
|
||||
|
||||
@ -14,13 +14,17 @@ msreviewer: hathind
|
||||
|
||||
# Fix issues found by the Readiness assessment tool
|
||||
|
||||
Seeing issues with your tenant? This article details how to remediate issues found with your tenant.
|
||||
|
||||
## Check results
|
||||
|
||||
For each check, the tool will report one of four possible results:
|
||||
|
||||
| Result | Meaning |
|
||||
| ----- | ----- |
|
||||
| Ready | No action is required before completing enrollment. |
|
||||
| Advisory | Follow the steps in the tool or this article for the best experience with enrollment and for users.<p><p>You can complete enrollment, but you must fix these issues before you deploy your first device. |
|
||||
| Not ready | Enrollment will fail if you don't fix these issues. Follow the steps in the tool or this article to resolve them. |
|
||||
| Not ready | You must fix these issues before enrollment. You won’t be able to enroll into Windows Autopatch if you don't fix these issues. Follow the steps in the tool or this article to resolve them. |
|
||||
| Error | The Azure Active Directory (AD) role you're using doesn't have sufficient permissions to run this check. |
|
||||
|
||||
> [!NOTE]
|
||||
@ -44,8 +48,8 @@ Your "Windows 10 update ring" policy in Intune must not target any Windows Autop
|
||||
|
||||
| Result | Meaning |
|
||||
| ----- | ----- |
|
||||
| Not ready | You have an "update ring" policy that targets all devices, all users, or both. Change the policy to use an assignment that targets a specific Azure Active Directory (AD) group that doesn't include any Windows Autopatch devices.<p><p>After enrolling into Autopatch, make sure that any update ring policies you have exclude the **Modern Workplace Devices - All** Azure Active Directory (AD) group.</p><p>For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).</p>|
|
||||
| Advisory | Both the **Modern Workplace Devices - All** and **Modern Workplace - All** Azure AD groups are groups that we create after you enroll in Windows Autopatch. This advisory is flagging an action you should take after enrolling into the service:<ol><li>Make sure that any update ring policies you have exclude the **Modern Workplace Devices - All** Azure Active Directory (AD) group.</li><li>If you have assigned Azure AD user groups to these policies, make sure that any update ring policies you have also exclude the **Modern Workplace - All** Azure AD group that you add your Windows Autopatch users to (or an equivalent group).</li></ol><br>For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure). |
|
||||
| Not ready | You have an "update ring" policy that targets all devices, all users, or both.<p>To resolve, change the policy to use an assignment that targets a specific Azure Active Directory (AD) group that doesn't include any Windows Autopatch devices.</p><p>For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).</p> |
|
||||
| Advisory | Both the **Modern Workplace Devices - All** and **Modern Workplace - All** Azure AD groups are groups that we create after you enroll in Windows Autopatch.<p>You can continue with enrollment. However, you must resolve the advisory prior to deploying your first device. To resolve the advisory, see [Maintain the Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md).</p>|
|
||||
|
||||
## Azure Active Directory settings
|
||||
|
||||
@ -68,13 +72,13 @@ Windows Autopatch requires the following licenses:
|
||||
| ----- | ----- |
|
||||
| Not ready | Windows Autopatch requires Windows 10/11 Enterprise E3 (or higher) to be assigned to your users. Additionally, Azure Active Directory Premium, and Microsoft Intune are required. For more information, see [more about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses). |
|
||||
|
||||
### Windows Autopatch service accounts
|
||||
### Windows Autopatch cloud service accounts
|
||||
|
||||
Certain account names could conflict with account names created by Windows Autopatch.
|
||||
|
||||
| Result | Meaning |
|
||||
| ----- | ----- |
|
||||
| Not ready | You have at least one account name that will conflict with account names created by Windows Autopatch. Work with your Microsoft account representative to exclude these account names. We don't list the account names publicly to minimize security risk. |
|
||||
| Not ready | You have at least one account name that will conflict with account names created by Windows Autopatch. The cloud service accounts are:<ul><li>MsAdmin</li><li>MsAdminInt</li><li>MsTest</li></ul><p>You must either rename or remove conflicting accounts to move forward with enrolling to the Windows Autopatch service as we'll create these accounts as part of running our service. For more information, see [Tenant Access](../references/windows-autopatch-privacy.md#tenant-access).</p> |
|
||||
|
||||
### Security defaults
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Prerequisites
|
||||
description: This article details the prerequisites needed for Windows Autopatch
|
||||
ms.date: 05/30/2022
|
||||
ms.date: 06/30/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: conceptual
|
||||
@ -16,12 +16,15 @@ msreviewer: hathind
|
||||
|
||||
Getting started with Windows Autopatch has been designed to be easy. This article outlines the infrastructure requirements you must meet to assure success with Windows Autopatch.
|
||||
|
||||
> [!NOTE]
|
||||
> For those who used the promo code to access Windows Autopatch during public preview, you'll continue to have access to Windows Autopatch even when the promo code expires. There is no additional action you have to take to continue using Windows Autopatch.
|
||||
|
||||
| Area | Prerequisite details |
|
||||
| ----- | ----- |
|
||||
| Licensing | Windows Autopatch requires Windows 10/11 Enterprise E3 (or higher) to be assigned to your users. Additionally, Azure Active Directory Premium and Microsoft Intune are required. For details about the specific service plans, see [more about licenses](#more-about-licenses).<p><p>For more information on available licenses, see [Microsoft 365 licensing](https://www.microsoft.com/microsoft-365/compare-microsoft-365-enterprise-plans).<p><p>For more information about licensing terms and conditions for products and services purchased through Microsoft Commercial Volume Licensing Programs, see the [Product Terms site](https://www.microsoft.com/licensing/terms/). |
|
||||
| Connectivity | All Windows Autopatch devices require connectivity to multiple Microsoft service endpoints from the corporate network.<p><p>For the full list of required IPs and URLs, see [Configure your network](../prepare/windows-autopatch-configure-network.md). |
|
||||
| Azure Active Directory | Azure Active Directory must either be the source of authority for all user accounts, or user accounts must be synchronized from on-premises Active Directory using the latest supported version of Azure Active Directory Connect to enable Hybrid Azure Active Directory join.<br><ul><li>For more information, see [Azure Active Directory Connect](/azure/active-directory/hybrid/whatis-azure-ad-connect) and [Hybrid Azure Active Directory join](/azure/active-directory/devices/howto-hybrid-azure-ad-join)</li><li>For more information on supported Azure Active Directory Connect versions, see [Azure AD Connect:Version release history](/azure/active-directory/hybrid/reference-connect-version-history).</li></ul> |
|
||||
| Device management | Windows Autopatch devices must be managed by Microsoft Intune. Intune must be set as the Mobile Device Management (MDM) authority or co-management must be turned on and enabled on the target devices.<p><p>At a minimum, the Windows Update, Device configuration and Office Click-to-Run apps workloads must be set to Pilot Intune or Intune. You must also ensure that the devices you intend on bringing to Windows Autopatch are in the targeted device collection. For more information, see Co-management requirements for Windows Autopatch below.<p>Other device management prerequisites include:<ul><li>Devices must be corporate-owned. Windows bring-your-own-devices (BYOD) are blocked during device registration prerequisite checks.</li><li>Devices managed only by Microsoft Endpoint Configuration Manager aren't supported.</li><li>Devices must be in communication with Microsoft Intune in the last 28 days. Otherwise, the devices won't be registered with Autopatch.</li><li>Devices must be connected to the internet.</li></ul><p>For more information on co-management, see [Co-management for Windows devices](/mem/configmgr/comanage/overview). |
|
||||
| Device management | Windows Autopatch devices must be managed by Microsoft Intune. Intune must be set as the Mobile Device Management (MDM) authority or co-management must be turned on and enabled on the target devices.<p><p>At a minimum, the Windows Update, Device configuration and Office Click-to-Run apps workloads must be set to Pilot Intune or Intune. You must also ensure that the devices you intend on bringing to Windows Autopatch are in the targeted device collection. For more information, see Co-management requirements for Windows Autopatch below.<p>Other device management prerequisites include:<ul><li>Devices must be corporate-owned. Windows bring-your-own-devices (BYOD) are blocked during device registration prerequisite checks.</li><li>Devices must be managed by either Intune or Configuration Manager Co-management. Devices only managed by Configuration Manager aren't supported.</li><li>Devices must be in communication with Microsoft Intune in the **last 28 days**. Otherwise, the devices won't be registered with Autopatch.</li><li>Devices must be connected to the internet.</li><li>Devices must have a **Serial number**, **Model** and **Manufacturer**. Device emulators that don't generate this information fail to meet **Intune or Cloud-attached** prerequisite check.</li></ul><p>See [Register your devices](/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices) for more details on device prerequisites and on how the device registration process works.<p>For more information on co-management, see [Co-management for Windows devices](/mem/configmgr/comanage/overview).</p> |
|
||||
| Data and privacy | For more information on Windows Autopatch privacy practices, see [Windows Autopatch Privacy](../references/windows-autopatch-privacy.md). |
|
||||
|
||||
## More about licenses
|
||||
@ -42,7 +45,7 @@ The following Windows 64-bit editions are required for Windows Autopatch:
|
||||
- Windows 10/11 Enterprise
|
||||
- Windows 10/11 Pro for Workstations
|
||||
|
||||
## Co-management requirements
|
||||
## Configuration Manager Co-management requirements
|
||||
|
||||
Windows Autopatch fully supports co-management. The following co-management requirements apply:
|
||||
|
||||
|
||||
@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Microsoft 365 Apps for enterprise update policies
|
||||
description: This article explains the Microsoft 365 Apps for enterprise policies in Windows Autopatch
|
||||
ms.date: 07/11/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: conceptual
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
msreviewer: hathind
|
||||
---
|
||||
|
||||
# Microsoft 365 Apps for enterprise update policies
|
||||
|
||||
## Conflicting and unsupported policies
|
||||
|
||||
Deploying any of the following policies to a managed device will make that device ineligible for management since the device will prevent us from delivering the service as designed.
|
||||
|
||||
### Update policies
|
||||
|
||||
Window Autopatch deploys mobile device management (MDM) policies to configure Microsoft 365 Apps and requires a specific configuration. If any [Microsoft 365 Apps update settings](/deployoffice/configure-update-settings-microsoft-365-apps) are deployed which conflict with our policies, then the device won't be eligible for management.
|
||||
|
||||
| Update setting | Value | Usage reason |
|
||||
| ----- | ----- | ----- |
|
||||
| Set updates to occur automatically | Enabled | Enable automatic updates |
|
||||
| Specify a location to look for updates | Blank | Don't use this setting since it overwrites the update branch |
|
||||
| Update branch | Monthly Enterprise | Supported branch for Windows Autopatch |
|
||||
| Specify the version of Microsoft 365 Apps to update to | Variable | Used to roll back to a previous version if an error occurs |
|
||||
| Set a deadline by when updates must be applied | 3 | Update deadline |
|
||||
| Hide update notifications from users | Turned off | Users should be notified when Microsoft 365 Apps are being updated |
|
||||
| Hide the option to turn on or off automatic Office updates | Turned on | Prevents users from disabling automatic updates |
|
||||
@ -58,11 +58,21 @@ Windows Autopatch only processes and stores system-level data from Windows 10 op
|
||||
|
||||
For more information about the diagnostic data collection of Microsoft Windows 10, see the [Where we store and process personal data](https://privacy.microsoft.com/privacystatement#mainwherewestoreandprocessdatamodule) section of the Microsoft Privacy Statement.
|
||||
|
||||
## Tenant access
|
||||
|
||||
Windows Autopatch creates and uses guest accounts leveraging just-in-time access functionality when signing into a customer tenant to manage the Windows Autopatch service. To provide additional locked down control, Windows Autopatch maintains a separate conditional access policy to restrict access to these accounts.
|
||||
|
||||
| Account name | Usage | Mitigating controls |
|
||||
| ----- | ----- | -----|
|
||||
| MsAdmin@tenantDomain.onmicrosoft.com | <ul><li>This is a limited-service account with administrator privileges. This account is used as an Intune and User administrator to define and configure the tenant for Windows Autopatch devices.</li><li>This account doesn't have interactive login permissions. The account performs operations only through the service.</li></ul> | Audited sign-ins |
|
||||
| MsAdminInt@tenantDomain.onmicrosoft.com |<ul><li>This account is an Intune and User administrator account used to define and configure the tenant for Windows Autopatch devices.</li><li>This account is used for interactive login to the customer’s tenant.</li><li>The use of this account is extremely limited as most operations are exclusively through MsAdmin (non-interactive) account.</li></ul> | <ul><li>Restricted to be accessed only from defined secure access workstations (SAWs) through a conditional access policy</li><li>Audited sign-ins</li</ul> |
|
||||
| MsTest@tenantDomain.onmicrosoft.com | This is a standard account used as a validation account for initial configuration and roll out of policy, application, and device compliance settings. | Audited sign-ins |
|
||||
|
||||
## Microsoft Windows Update for Business
|
||||
|
||||
Microsoft Windows Update for Business uses data from Windows diagnostics to analyze update status and failures. Windows Autopatch uses this data and uses it to mitigate, and resolve problems to ensure that all registered devices are up to date based on a predefined update cadence.
|
||||
|
||||
## Microsft Azure Active Directory
|
||||
## Microsoft Azure Active Directory
|
||||
|
||||
Identifying data used by Windows Autopatch is stored by Azure Active Directory (Azure AD) in a geographical location. The geographical location is based on the location provided by the organization upon subscribing to Microsoft online services, such as Microsoft Apps for Enterprise and Azure. For more information on where your Azure AD data is located, see [Azure Active Directory - Where is your data located?](https://msit.powerbi.com/view?r=eyJrIjoiODdjOWViZDctMWRhZS00ODUzLWI4MmQtNWM5NjBkZTBkNjFlIiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9)
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.collection:
|
||||
- M365-modern-desktop
|
||||
- highpri
|
||||
ms.topic: tutorial
|
||||
ms.date: 05/12/2022
|
||||
ms.date: 07/12/2022
|
||||
---
|
||||
|
||||
# Demonstrate Autopilot deployment
|
||||
@ -42,14 +42,11 @@ You'll need the following components to complete this lab:
|
||||
|
||||
| Component | Description |
|
||||
|:---|:---|
|
||||
|**Windows 10 installation media**|Windows 10 Professional or Enterprise ISO file for a supported version of Windows 10, general availability channel. If you don't already have an ISO to use, download an evaluation version of Windows 10 Enterprise.|
|
||||
|**Windows 10 installation media**|Windows 10 Enterprise ISO file for a supported version of Windows 10, general availability channel. If you don't already have an ISO to use, download an [evaluation version of Windows 10 Enterprise](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise).|
|
||||
|**Internet access**|If you're behind a firewall, see the detailed [networking requirements](/mem/autopilot/software-requirements#networking-requirements). Otherwise, just make sure that you have a connection to the internet.|
|
||||
|**Hyper-V or a physical device running Windows 10**|The guide assumes that you'll use a Hyper-V VM, and provides instructions to install and configure Hyper-V if needed. To use a physical device, skip the steps to install and configure Hyper-V.|
|
||||
|**An account with Azure Active Directory (Azure AD) Premium license**|This guide will describe how to get a free 30-day trial Azure AD Premium subscription that can be used to complete the lab.|
|
||||
|
||||
> [!NOTE]
|
||||
> The Microsoft Evaluation Center is temporarily unavailable. To access Windows client evaluation media, see [Accessing trials and kits for Windows (Eval Center workaround)](https://techcommunity.microsoft.com/t5/windows-11/accessing-trials-and-kits-for-windows-eval-center-workaround/m-p/3361125).<!-- 6049663 -->
|
||||
|
||||
## Procedures
|
||||
|
||||
A summary of the sections and procedures in the lab is provided below. Follow each section in the order it's presented, skipping the sections that don't apply to you. Optional procedures are provided in the appendices.
|
||||
@ -142,10 +139,7 @@ After you determine the ISO file location and the name of the appropriate networ
|
||||
|
||||
### Set ISO file location
|
||||
|
||||
Download an ISO file for an evaluation version of the latest release of Windows 10 Enterprise. Choose a 64-bit version.
|
||||
|
||||
> [!NOTE]
|
||||
> The Microsoft Evaluation Center is temporarily unavailable. To access this download, see [Accessing trials and kits for Windows (Eval Center workaround)](https://techcommunity.microsoft.com/t5/windows-11/accessing-trials-and-kits-for-windows-eval-center-workaround/m-p/3361125).<!-- 6049663 -->
|
||||
Download an ISO file for an evaluation version of the latest release of Windows 10 Enterprise from the [Evaluation Center](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise). Choose a 64-bit version.
|
||||
|
||||
After you download an ISO file, the name will be long. For example, `19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso`
|
||||
|
||||
@ -180,7 +174,8 @@ All VM data will be created under the current path in your PowerShell prompt. Co
|
||||
|
||||
```powershell
|
||||
New-VMSwitch -Name AutopilotExternal -AllowManagementOS $true -NetAdapterName (Get-NetAdapter | Where-Object {$_.Status -eq "Up" -and !$_.Virtual}).Name
|
||||
New-VM -Name WindowsAutopilot -MemoryStartupBytes 2GB -BootDevice VHD -NewVHDPath .\VMs\WindowsAutopilot.vhdx -Path .\VMData -NewVHDSizeBytes 80GB -Generation 2 -Switch AutopilotExternal
|
||||
New-VM -Name WindowsAutopilot -MemoryStartupBytes 4GB -BootDevice VHD -NewVHDPath .\VMs\WindowsAutopilot.vhdx -Path .\VMData -NewVHDSizeBytes 80GB -Generation 2 -Switch AutopilotExternal
|
||||
Set-VMProcessor WindowsAutopilot -Count 2
|
||||
Add-VMDvdDrive -Path c:\iso\win10-eval.iso -VMName WindowsAutopilot
|
||||
Start-VM -VMName WindowsAutopilot
|
||||
```
|
||||
|
||||
@ -74,18 +74,59 @@ The following provides information on the current configurations:
|
||||
- [Microsoft Managed Desktop](/microsoft-365/managed-desktop/service-description/device-policies#windows-diagnostic-data)
|
||||
- [Desktop Analytics](/mem/configmgr/desktop-analytics/overview)
|
||||
|
||||
## New Windows diagnostic data processor configuration
|
||||
## Significant changes coming to the Windows diagnostic data processor configuration
|
||||
|
||||
> [!IMPORTANT]
|
||||
> There are some significant changes planned for the Windows diagnostic data processor configuration. To learn more, [review this information](configure-windows-diagnostic-data-in-your-organization.md#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
|
||||
Currently, to enroll devices in the [Window diagnostic data processor configuration](configure-windows-diagnostic-data-in-your-organization.md#enable-windows-diagnostic-data-processor-configuration) option, IT admins can use policies, such as the “Allow commercial data pipeline” policy, at the individual device level.
|
||||
|
||||
Enterprise customers have an option for controlling their Windows diagnostic data for their Azure Active Directory-joined devices. This configuration option is supported on the following versions of Windows:
|
||||
To enable efficiencies and help us implement our plan to [store and process EU Data for European enterprise customers in the EU](https://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/), we'll be introducing the following significant change for enterprise Windows devices that have diagnostic data turned on.
|
||||
|
||||
- Windows 11 Enterprise, Professional, and Education
|
||||
- Windows 10, Enterprise, Professional, and Education, version 1809 with at least the July 2021 update.
|
||||
***We’ll stop using policies, such as the “Allow commercial data pipeline” policy, to configure the processor option. Instead, we’ll be introducing an organization-wide configuration based on Azure Active Directory (Azure AD) to determine Microsoft’s role in data processing.***
|
||||
|
||||
Previously, enterprise customers had two options in managing their Windows diagnostic data: 1) allow Microsoft to be the [controller](/compliance/regulatory/gdpr#terminology) of that data and responsible for determining the purposes and means of the processing of Windows diagnostic data in order to improve the Windows operating system and deliver analytical services, or 2) turn off diagnostic data flows altogether.
|
||||
We’re making this change to help ensure the diagnostic data for all devices in an organization is processed in a consistent way, and in the same geographic region.
|
||||
|
||||
Now, customers will have a third option that allows them to be the controller for their Windows diagnostic data, while still benefiting from the purposes that this data serves, such as quality of updates and device drivers. Under this approach, Microsoft will act as a data [processor](/compliance/regulatory/gdpr#terminology), processing Windows diagnostic data on behalf of the controller.
|
||||
### Devices in Azure AD tenants with a billing address in the European Union (EU) or European Free Trade Association (EFTA)
|
||||
|
||||
This new option will enable customers to use familiar tools to manage, export, or delete data to help them meet their compliance obligations. For example, using the Microsoft Azure portal, customers will have the means to respond to their own users’ requests, such as delete and export diagnostic data. Admins can easily enable the Windows diagnostic data processor configuration for Windows devices using group policy or mobile device management ([MDM](/windows/client-management/mdm/policy-csp-system)). For more information, see [Enable Windows diagnostic data processor configuration](configure-windows-diagnostic-data-in-your-organization.md#enable-windows-diagnostic-data-processor-configuration) in [Configure Windows diagnostic data in your organization](configure-windows-diagnostic-data-in-your-organization.md)
|
||||
For Windows devices with diagnostic data turned on and that are joined to an [Azure AD tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) in the EU or EFTA, the Windows diagnostic data for that device will be automatically configured for the processor option. The Windows diagnostic data for those devices will be processed in Europe.
|
||||
|
||||
From a compliance standpoint, this change means that Microsoft will be the processor and the organization will be the controller of the Windows diagnostic data. IT admins for those organizations will become responsible for responding to their users’ [data subject requests](/compliance/regulatory/gdpr-dsr-windows).
|
||||
|
||||
### Devices in Azure AD tenants with a billing address outside of the EU and EFTA
|
||||
|
||||
For Windows devices with diagnostic data turned on and that are joined to an [Azure AD tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) outside of the EU and EFTA, to enable the processor configuration option, the organization must sign up for any of the following enterprise services, which rely on diagnostic data:
|
||||
|
||||
- [Update Compliance](/windows/deployment/update/update-compliance-monitor)
|
||||
- [Windows Update for Business deployment service](/windows/deployment/update/deployment-service-overview)
|
||||
- [Microsoft Managed Desktop](/managed-desktop/intro/)
|
||||
- [Endpoint analytics (in Microsoft Endpoint Manager)](/mem/analytics/overview)
|
||||
|
||||
*(Additional licensing requirements may apply to use these services.)*
|
||||
|
||||
If you don’t sign up for any of these enterprise services, Microsoft will act as controller for the diagnostic data.
|
||||
|
||||
> [!NOTE]
|
||||
> In all cases, enrollment in the Windows diagnostic data processor configuration requires a device to be joined to an Azure AD tenant. If a device isn't properly enrolled, Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
|
||||
|
||||
### Rollout plan for this change
|
||||
|
||||
This change will roll out initially to Windows devices enrolled in the [Dev Channel](/windows-insider/flighting#dev-channel) of the Windows Insider program no earlier than July 2022. Once the rollout is initiated, devices in the Dev Channel that are joined to an Azure AD tenant with a billing address in the EU or EFTA will be automatically enabled for the processor configuration option.
|
||||
|
||||
During this initial rollout, the following conditions apply to devices in the Dev Channel that are joined to an Azure AD tenant with a billing address outside of the EU or EFTA:
|
||||
|
||||
- Devices can't be enabled for the Windows diagnostic data processor configuration at this time.
|
||||
- The processor configuration will be disabled in any devices that were previously enabled.
|
||||
- Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
|
||||
|
||||
It's recommended Insiders on these devices pause flighting if these changes aren't acceptable.
|
||||
|
||||
For Windows devices in the Dev Channel that aren't joined to an Azure AD tenant, Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
|
||||
|
||||
For other Windows devices (not in the Dev Channel), additional details on supported versions of Windows 11 and Windows 10 will be announced at a later date. These changes will roll out no earlier than the last quarter of calendar year 2022.
|
||||
|
||||
To prepare for this change, ensure that you meet the [prerequisites](configure-windows-diagnostic-data-in-your-organization.md#prerequisites) for Windows diagnostic data processor configuration, join your devices to Azure AD (can be a hybrid Azure AD join), and keep your devices secure and up to date with quality updates. If you're outside of the EU or EFTA, sign up for any of the enterprise services.
|
||||
|
||||
As part of this change, the following policies will no longer be supported to configure the processor option:
|
||||
- Allow commercial data pipeline
|
||||
- Allow Desktop Analytics Processing
|
||||
- Allow Update Compliance Processing
|
||||
- Allow WUfB Cloud Processing
|
||||
- Configure the Commercial ID
|
||||
@ -85,7 +85,7 @@ The following table lists the endpoints related to how you can manage the collec
|
||||
|Connected User Experiences and Telemetry | v10.events.data.microsoft.com <br></br> v10c.events.data.microsoft.com <br></br> v10.vortex-win.data.microsoft.com |
|
||||
| [Windows Error Reporting](/windows/win32/wer/windows-error-reporting) | watson.telemetry.microsoft.com <br></br> umwatsonc.events.data.microsoft.com <br></br> *-umwatsonc.events.data.microsoft.com <br></br> ceuswatcab01.blob.core.windows.net <br></br> ceuswatcab02.blob.core.windows.net <br></br> eaus2watcab01.blob.core.windows.net <br></br> eaus2watcab02.blob.core.windows.net <br></br> weus2watcab01.blob.core.windows.net <br></br> weus2watcab02.blob.core.windows.net |
|
||||
|Authentication | login.live.com <br></br> <br></br> IMPORTANT: This endpoint is used for device authentication. We do not recommend disabling this endpoint.|
|
||||
| [Online Crash Analysis](/windows/win32/dxtecharts/crash-dump-analysis) | oca.microsoft.com <br></br> kmwatsonc.telemetry.microsoft.com <br></br> *-kmwatsonc.telemetry.microsoft.com |
|
||||
| [Online Crash Analysis](/windows/win32/dxtecharts/crash-dump-analysis) | oca.telemetry.microsoft.com <br></br> oca.microsoft.com <br></br> kmwatsonc.events.data.microsoft.com <br></br> *-kmwatsonc.events.data.microsoft.com |
|
||||
|Settings | settings-win.data.microsoft.com <br></br> <br></br> IMPORTANT: This endpoint is used to remotely configure diagnostics-related settings and data collection. For example, we use the settings endpoint to remotely block an event from being sent back to Microsoft. We do not recommend disabling this endpoint. This endpoint does not upload Windows diagnostic data. |
|
||||
|
||||
### Data access
|
||||
@ -256,7 +256,7 @@ Use [Policy Configuration Service Provider (CSP)](/windows/client-management/mdm
|
||||
## Enable Windows diagnostic data processor configuration
|
||||
|
||||
> [!IMPORTANT]
|
||||
> There are some significant changes planned for diagnostic data processor configuration. To learn more, [review this information](#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
|
||||
> There are some significant changes planned for diagnostic data processor configuration. To learn more, [review this information](changes-to-windows-diagnostic-data-collection.md#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
|
||||
|
||||
The Windows diagnostic data processor configuration enables you to be the controller, as defined by the European Union General Data Protection Regulation (GDPR), for the Windows diagnostic data collected from your Windows devices that meet the configuration requirements.
|
||||
|
||||
@ -267,7 +267,7 @@ The Windows diagnostic data processor configuration enables you to be the contro
|
||||
- Enterprise
|
||||
- Professional
|
||||
- Education
|
||||
- The device must be joined to Azure Active Directory.
|
||||
- The device must be joined to Azure Active Directory (can be a hybrid Azure AD join).
|
||||
|
||||
For the best experience, use the most current build of any operating system specified above. Configuration functionality and availability may vary on older systems. See [Lifecycle Policy](/lifecycle/products/windows-10-enterprise-and-education)
|
||||
|
||||
@ -325,63 +325,6 @@ Windows Update for Business:
|
||||
|
||||
- [How to enable deployment protections](/windows/deployment/update/deployment-service-overview#how-to-enable-deployment-protections)
|
||||
|
||||
### Significant changes coming to the Windows diagnostic data processor configuration
|
||||
|
||||
Currently, to enroll devices in the Window diagnostic data processor configuration option, IT admins can use policies, such as the “Allow commercial data pipeline” policy, at the individual device level.
|
||||
|
||||
To enable efficiencies and help us implement our plan to [store and process EU Data for European enterprise customers in the EU](https://blogs.microsoft.com/eupolicy/2021/05/06/eu-data-boundary/), we'll be introducing the following significant change for enterprise Windows devices that have diagnostic data turned on.
|
||||
|
||||
***We’ll stop using policies, such as the “Allow commercial data pipeline” policy, to configure the processor option. Instead, we’ll be introducing an organization-wide configuration based on Azure Active Directory (Azure AD) to determine Microsoft’s role in data processing.***
|
||||
|
||||
We’re making this change to help ensure the diagnostic data for all devices in an organization is processed in a consistent way, and in the same geographic region.
|
||||
|
||||
#### Devices in Azure AD tenants with a billing address in the European Union (EU) or European Free Trade Association (EFTA)
|
||||
|
||||
For Windows devices with diagnostic data turned on and that are joined to an [Azure AD tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) in the EU or EFTA, the Windows diagnostic data for that device will be automatically configured for the processor option. The Windows diagnostic data for those devices will be processed in Europe.
|
||||
|
||||
From a compliance standpoint, this change means that Microsoft will be the processor and the organization will be the controller of the Windows diagnostic data. IT admins for those organizations will become responsible for responding to their users’ [data subject requests](/compliance/regulatory/gdpr-dsr-windows).
|
||||
|
||||
#### Devices in Azure AD tenants with a billing address outside of the EU and EFTA
|
||||
|
||||
For Windows devices with diagnostic data turned on and that are joined to an [Azure AD tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) outside of the EU and EFTA, to enable the processor configuration option, the organization must sign up for any of the following enterprise services, which rely on diagnostic data:
|
||||
|
||||
- [Update Compliance](/windows/deployment/update/update-compliance-monitor)
|
||||
- [Windows Update for Business deployment service](/windows/deployment/update/deployment-service-overview)
|
||||
- [Microsoft Managed Desktop](/managed-desktop/intro/)
|
||||
- [Endpoint analytics (in Microsoft Endpoint Manager)](/mem/analytics/overview)
|
||||
|
||||
*(Additional licensing requirements may apply to use these services.)*
|
||||
|
||||
If you don’t sign up for any of these enterprise services, Microsoft will act as controller for the diagnostic data.
|
||||
|
||||
> [!NOTE]
|
||||
> In all cases, enrollment in the Windows diagnostic data processor configuration requires a device to be joined to an Azure AD tenant. If a device isn't properly enrolled, Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
|
||||
|
||||
#### Rollout plan for this change
|
||||
|
||||
This change will roll out initially to Windows devices enrolled in the [Dev Channel](/windows-insider/flighting#dev-channel) of the Windows Insider program no earlier than July 2022. Once the rollout is initiated, devices in the Dev Channel that are joined to an Azure AD tenant with a billing address in the EU or EFTA will be automatically enabled for the processor configuration option.
|
||||
|
||||
During this initial rollout, the following conditions apply to devices in the Dev Channel that are joined to an Azure AD tenant with a billing address outside of the EU or EFTA:
|
||||
|
||||
- Devices can't be enabled for the Windows diagnostic data processor configuration at this time.
|
||||
- The processor configuration will be disabled in any devices that were previously enabled.
|
||||
- Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
|
||||
|
||||
It's recommended Insiders on these devices pause flighting if these changes aren't acceptable.
|
||||
|
||||
For Windows devices in the Dev Channel that aren't joined to an Azure AD tenant, Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
|
||||
|
||||
For other Windows devices (not in the Dev Channel), additional details on supported versions of Windows 11 and Windows 10 will be announced at a later date. These changes will roll out no earlier than the last quarter of calendar year 2022.
|
||||
|
||||
To prepare for this change, ensure that you meet the [prerequisites](#prerequisites) for Windows diagnostic data processor configuration, join your devices to Azure AD, and keep your devices secure and up to date with quality updates. If you're outside of the EU or EFTA, sign up for any of the enterprise services.
|
||||
|
||||
As part of this change, the following policies will no longer be supported to configure the processor option:
|
||||
- Allow commercial data pipeline
|
||||
- Allow Desktop Analytics Processing
|
||||
- Allow Update Compliance Processing
|
||||
- Allow WUfB Cloud Processing
|
||||
- Configure the Commercial ID
|
||||
|
||||
## Limit optional diagnostic data for Desktop Analytics
|
||||
|
||||
For more information about how to limit the diagnostic data to the minimum required by Desktop Analytics, see [Enable data sharing for Desktop Analytics](/mem/configmgr/desktop-analytics/enable-data-sharing).
|
||||
|
||||
@ -147,7 +147,7 @@ An administrator can disable a user’s ability to delete their device’s diagn
|
||||
#### _2.3.7 Diagnostic data: Enabling the Windows diagnostic data processor configuration_
|
||||
|
||||
> [!IMPORTANT]
|
||||
> There are some significant changes planned for the Windows diagnostic data processor configuration. To learn more, [review this information](configure-windows-diagnostic-data-in-your-organization.md#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
|
||||
> There are some significant changes planned for the Windows diagnostic data processor configuration. To learn more, [review this information](changes-to-windows-diagnostic-data-collection.md#significant-changes-coming-to-the-windows-diagnostic-data-processor-configuration).
|
||||
|
||||
**Applies to:**
|
||||
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Access Control Overview (Windows 10)
|
||||
description: Access Control Overview
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Active Directory Accounts (Windows 10)
|
||||
description: Active Directory Accounts
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Active Directory Security Groups
|
||||
description: Active Directory Security Groups
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Dynamic Access Control Overview (Windows 10)
|
||||
description: Learn about Dynamic Access Control and its associated elements, which were introduced in Windows Server 2012 and Windows 8.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Local Accounts (Windows 10)
|
||||
description: Learn how to secure and manage access to the resources on a standalone or member server for services or users.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Microsoft Accounts (Windows 10)
|
||||
description: Microsoft Accounts
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Security identifiers (Windows 10)
|
||||
description: Security identifiers
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Security Principals (Windows 10)
|
||||
description: Security Principals
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: Service Accounts (Windows 10)
|
||||
description: Service Accounts
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -3,10 +3,6 @@ title: Special Identities (Windows 10)
|
||||
description: Special Identities
|
||||
ms.prod: m365-security
|
||||
ms.technology: windows-sec
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -1,14 +1,8 @@
|
||||
---
|
||||
title: Configure S/MIME for Windows
|
||||
description: S/MIME lets users encrypt outgoing messages and attachments so that only intended recipients with a digital ID, also known as a certificate, can read them.
|
||||
ms.assetid: 7F9C2A99-42EB-4BCC-BB53-41C04FBBBF05
|
||||
ms.reviewer:
|
||||
keywords: encrypt, digital signature
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Additional mitigations
|
||||
description: Advice and sample code for making your domain environment more secure and robust with Windows Defender Credential Guard.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Advice while using Windows Defender Credential Guard (Windows)
|
||||
description: Considerations and recommendations for certain scenarios when using Windows Defender Credential Guard in Windows.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
@ -26,27 +22,27 @@ ms.reviewer:
|
||||
|
||||
Passwords are still weak. We recommend that in addition to deploying Windows Defender Credential Guard, organizations move away from passwords to other authentication methods, such as physical smart cards, virtual smart cards, or Windows Hello for Business.
|
||||
|
||||
Windows Defender Credential Guard uses hardware security, so some features such as Windows To Go, are not supported.
|
||||
Windows Defender Credential Guard uses hardware security, so some features such as Windows To Go, aren't supported.
|
||||
|
||||
## Wi-fi and VPN Considerations
|
||||
When you enable Windows Defender Credential Guard, you can no longer use NTLM classic authentication for Single Sign-On. You will be forced to enter your credentials to use these protocols and cannot save the credentials for future use. If you are using WiFi and VPN endpoints that are based on MS-CHAPv2, they are subject to similar attacks as for NTLMv1. For WiFi and VPN connections, Microsoft recommends that organizations move from MSCHAPv2-based connections such as PEAP-MSCHAPv2 and EAP-MSCHAPv2, to certificate-based authentication such as PEAP-TLS or EAP-TLS.
|
||||
When you enable Windows Defender Credential Guard, you can no longer use NTLM classic authentication for Single Sign-On. You'll be forced to enter your credentials to use these protocols and can't save the credentials for future use. If you're using WiFi and VPN endpoints that are based on MS-CHAPv2, they're subject to similar attacks as for NTLMv1. For WiFi and VPN connections, Microsoft recommends that organizations move from MSCHAPv2-based connections such as PEAP-MSCHAPv2 and EAP-MSCHAPv2, to certificate-based authentication such as PEAP-TLS or EAP-TLS.
|
||||
|
||||
## Kerberos Considerations
|
||||
|
||||
When you enable Windows Defender Credential Guard, you can no longer use Kerberos unconstrained delegation or DES encryption. Unconstrained delegation could allow attackers to extract Kerberos keys from the isolated LSA process. Use constrained or resource-based Kerberos delegation instead.
|
||||
|
||||
## 3rd Party Security Support Providers Considerations
|
||||
Some 3rd party Security Support Providers (SSPs and APs) might not be compatible with Windows Defender Credential Guard because it does not allow third-party SSPs to ask for password hashes from LSA. However, SSPs and APs still get notified of the password when a user logs on and/or changes their password. Any use of undocumented APIs within custom SSPs and APs are not supported. We recommend that custom implementations of SSPs/APs are tested with Windows Defender Credential Guard. SSPs and APs that depend on any undocumented or unsupported behaviors fail. For example, using the KerbQuerySupplementalCredentialsMessage API is not supported. Replacing the NTLM or Kerberos SSPs with custom SSPs and APs. For more info, see [Restrictions around Registering and Installing a Security Package](/windows/win32/secauthn/restrictions-around-registering-and-installing-a-security-package) on MSDN.
|
||||
Some 3rd party Security Support Providers (SSPs and APs) might not be compatible with Windows Defender Credential Guard because it doesn't allow third-party SSPs to ask for password hashes from LSA. However, SSPs and APs still get notified of the password when a user logs on and/or changes their password. Any use of undocumented APIs within custom SSPs and APs aren't supported. We recommend that custom implementations of SSPs/APs are tested with Windows Defender Credential Guard. SSPs and APs that depend on any undocumented or unsupported behaviors fail. For example, using the KerbQuerySupplementalCredentialsMessage API isn't supported. Replacing the NTLM or Kerberos SSPs with custom SSPs and APs. For more info, see [Restrictions around Registering and Installing a Security Package](/windows/win32/secauthn/restrictions-around-registering-and-installing-a-security-package) on MSDN.
|
||||
|
||||
## Upgrade Considerations
|
||||
As the depth and breadth of protections provided by Windows Defender Credential Guard are increased, subsequent releases of Windows 10 with Windows Defender Credential Guard running may impact scenarios that were working in the past. For example, Windows Defender Credential Guard may block the use of a particular type of credential or a particular component to prevent malware from taking advantage of vulnerabilities. Test scenarios required for operations in an organization before upgrading a device using Windows Defender Credential Guard.
|
||||
|
||||
### Saved Windows Credentials Protected
|
||||
|
||||
Starting with Windows 10, version 1511, domain credentials that are stored with Credential Manager are protected with Windows Defender Credential Guard. Credential Manager allows you to store three types of credentials: Windows credentials, certificate-based credentials, and generic credentials. Generic credentials such as user names and passwords that you use to log on to websites are not protected since the applications require your cleartext password. If the application does not need a copy of the password, they can save domain credentials as Windows credentials that are protected. Windows credentials are used to connect to other computers on a network. The following considerations apply to the Windows Defender Credential Guard protections for Credential Manager:
|
||||
* Windows credentials saved by Remote Desktop Client cannot be sent to a remote host. Attempts to use saved Windows credentials fail, displaying the error message "Logon attempt failed."
|
||||
Starting with Windows 10, version 1511, domain credentials that are stored with Credential Manager are protected with Windows Defender Credential Guard. Credential Manager allows you to store three types of credentials: Windows credentials, certificate-based credentials, and generic credentials. Generic credentials such as user names and passwords that you use to log on to websites aren't protected since the applications require your cleartext password. If the application doesn't need a copy of the password, they can save domain credentials as Windows credentials that are protected. Windows credentials are used to connect to other computers on a network. The following considerations apply to the Windows Defender Credential Guard protections for Credential Manager:
|
||||
* Windows credentials saved by Remote Desktop Client can't be sent to a remote host. Attempts to use saved Windows credentials fail, displaying the error message "Logon attempt failed."
|
||||
* Applications that extract Windows credentials fail.
|
||||
* When credentials are backed up from a PC that has Windows Defender Credential Guard enabled, the Windows credentials cannot be restored. If you need to back up your credentials, you must do this before you enable Windows Defender Credential Guard. Otherwise, you cannot restore those credentials.
|
||||
* When credentials are backed up from a PC that has Windows Defender Credential Guard enabled, the Windows credentials can't be restored. If you need to back up your credentials, you must do this before you enable Windows Defender Credential Guard. Otherwise, you can't restore those credentials.
|
||||
|
||||
## Clearing TPM Considerations
|
||||
Virtualization-based Security (VBS) uses the TPM to protect its key. So when the TPM is cleared then the TPM protected key used to encrypt VBS secrets is lost.
|
||||
@ -61,17 +57,17 @@ As a result Credential Guard can no longer decrypt protected data. VBS creates a
|
||||
> Credential Guard obtains the key during initialization. So the data loss will only impact persistent data and occur after the next system startup.
|
||||
|
||||
### Windows credentials saved to Credential Manager
|
||||
Since Credential Manager cannot decrypt saved Windows Credentials, they are deleted. Applications should prompt for credentials that were previously saved. If saved again, then Windows credentials are protected Credential Guard.
|
||||
Since Credential Manager can't decrypt saved Windows Credentials, they're deleted. Applications should prompt for credentials that were previously saved. If saved again, then Windows credentials are protected Credential Guard.
|
||||
|
||||
### Domain-joined device’s automatically provisioned public key
|
||||
Beginning with Windows 10 and Windows Server 2016, domain-devices automatically provision a bound public key, for more information about automatic public key provisioning, see [Domain-joined Device Public Key Authentication](/windows-server/security/kerberos/domain-joined-device-public-key-authentication).
|
||||
|
||||
Since Credential Guard cannot decrypt the protected private key, Windows uses the domain-joined computer's password for authentication to the domain. Unless additional policies are deployed, there should not be a loss of functionality. If a device is configured to only use public key, then it cannot authenticate with password until that policy is disabled. For more information on Configuring devices to only use public key, see [Domain-joined Device Public Key Authentication](/windows-server/security/kerberos/domain-joined-device-public-key-authentication).
|
||||
Since Credential Guard can't decrypt the protected private key, Windows uses the domain-joined computer's password for authentication to the domain. Unless additional policies are deployed, there should not be a loss of functionality. If a device is configured to only use public key, then it can't authenticate with password until that policy is disabled. For more information on Configuring devices to only use public key, see [Domain-joined Device Public Key Authentication](/windows-server/security/kerberos/domain-joined-device-public-key-authentication).
|
||||
|
||||
Also if any access control checks including authentication policies require devices to have either the KEY TRUST IDENTITY (S-1-18-4) or FRESH PUBLIC KEY IDENTITY (S-1-18-3) well-known SIDs, then those access checks fail. For more information about authentication policies, see [Authentication Policies and Authentication Policy Silos](/windows-server/security/credentials-protection-and-management/authentication-policies-and-authentication-policy-silos). For more information about well-known SIDs, see [[MS-DTYP] Section 2.4.2.4 Well-known SID Structures](/openspecs/windows_protocols/ms-dtyp/81d92bba-d22b-4a8c-908a-554ab29148ab).
|
||||
|
||||
### Breaking DPAPI on domain-joined devices
|
||||
On domain-joined devices, DPAPI can recover user keys using a domain controller from the user's domain. If a domain-joined device has no connectivity to a domain controller, then recovery is not possible.
|
||||
On domain-joined devices, DPAPI can recover user keys using a domain controller from the user's domain. If a domain-joined device has no connectivity to a domain controller, then recovery isn't possible.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> Best practice when clearing a TPM on a domain-joined device is to be on a network with connectivity to domain controllers. This ensures DPAPI functions and the user does not experience strange behavior. <br>
|
||||
@ -79,11 +75,11 @@ Auto VPN configuration is protected with user DPAPI. User may not be able to use
|
||||
|
||||
If you must clear the TPM on a domain-joined device without connectivity to domain controllers, then you should consider the following.
|
||||
|
||||
Domain user sign-in on a domain-joined device after clearing a TPM for as long as there is no connectivity to a domain controller:
|
||||
Domain user sign-in on a domain-joined device after clearing a TPM for as long as there's no connectivity to a domain controller:
|
||||
|
||||
|Credential Type | Windows version | Behavior
|
||||
|---|---|---|
|
||||
| Certificate (smart card or Windows Hello for Business) | All | All data protected with user DPAPI is unusable and user DPAPI does not work at all. |
|
||||
| Certificate (smart card or Windows Hello for Business) | All | All data protected with user DPAPI is unusable and user DPAPI doesn't work at all. |
|
||||
| Password | Windows 10 v1709 or later | If the user signed-in with a certificate or password prior to clearing the TPM, then they can sign-in with password and user DPAPI is unaffected.
|
||||
| Password | Windows 10 v1703 | If the user signed-in with a password prior to clearing the TPM, then they can sign-in with that password and are unaffected.
|
||||
| Password | Windows 10 v1607 or earlier | Existing user DPAPI protected data is unusable. User DPAPI is able to protect new data.
|
||||
@ -91,7 +87,7 @@ Domain user sign-in on a domain-joined device after clearing a TPM for as long a
|
||||
Once the device has connectivity to the domain controllers, DPAPI recovers the user's key and data protected prior to clearing the TPM can be decrypted.
|
||||
|
||||
#### Impact of DPAPI failures on Windows Information Protection
|
||||
When data protected with user DPAPI is unusable, then the user loses access to all work data protected by Windows Information Protection. The impact includes: Outlook 2016 is unable to start and work protected documents cannot be opened. If DPAPI is working, then newly created work data is protected and can be accessed.
|
||||
When data protected with user DPAPI is unusable, then the user loses access to all work data protected by Windows Information Protection. The impact includes: Outlook 2016 is unable to start and work protected documents can't be opened. If DPAPI is working, then newly created work data is protected and can be accessed.
|
||||
|
||||
**Workaround:** Users can resolve the problem by connecting their device to the domain and rebooting or using their Encrypting File System Data Recovery Agent certificate. For more information about Encrypting File System Data Recovery Agent certificate, see [Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate](/windows/threat-protection/windows-information-protection/create-and-verify-an-efs-dra-certificate).
|
||||
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: How Windows Defender Credential Guard works
|
||||
description: Learn how Windows Defender Credential Guard uses virtualization to protect secrets, so that only privileged system software can access them.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
@ -25,13 +21,13 @@ ms.reviewer:
|
||||
- Windows Server 2019
|
||||
|
||||
|
||||
Kerberos, NTLM, and Credential manager isolate secrets by using virtualization-based security. Previous versions of Windows stored secrets in the Local Security Authority (LSA). Prior to Windows 10, the LSA stored secrets used by the operating system in its process memory. With Windows Defender Credential Guard enabled, the LSA process in the operating system talks to a new component called the isolated LSA process that stores and protects those secrets. Data stored by the isolated LSA process is protected using Virtualization-based security and is not accessible to the rest of the operating system. LSA uses remote procedure calls to communicate with the isolated LSA process.
|
||||
Kerberos, NTLM, and Credential manager isolate secrets by using virtualization-based security. Previous versions of Windows stored secrets in the Local Security Authority (LSA). Prior to Windows 10, the LSA stored secrets used by the operating system in its process memory. With Windows Defender Credential Guard enabled, the LSA process in the operating system talks to a new component called the isolated LSA process that stores and protects those secrets. Data stored by the isolated LSA process is protected using Virtualization-based security and isn't accessible to the rest of the operating system. LSA uses remote procedure calls to communicate with the isolated LSA process.
|
||||
|
||||
For security reasons, the isolated LSA process doesn't host any device drivers. Instead, it only hosts a small subset of operating system binaries that are needed for security and nothing else. All of these binaries are signed with a certificate that is trusted by virtualization-based security and these signatures are validated before launching the file in the protected environment.
|
||||
|
||||
When Windows Defender Credential Guard is enabled, NTLMv1, MS-CHAPv2, Digest, and CredSSP cannot use the signed-in credentials. Thus, single sign-on does not work with these protocols. However, applications can prompt for credentials or use credentials stored in the Windows Vault, which are not protected by Windows Defender Credential Guard with any of these protocols. It is recommended that valuable credentials, such as the sign-in credentials, are not to be used with any of these protocols. If these protocols must be used by domain or Azure AD users, secondary credentials should be provisioned for these use cases.
|
||||
When Windows Defender Credential Guard is enabled, NTLMv1, MS-CHAPv2, Digest, and CredSSP can't use the signed-in credentials. Thus, single sign-on doesn't work with these protocols. However, applications can prompt for credentials or use credentials stored in the Windows Vault, which aren't protected by Windows Defender Credential Guard with any of these protocols. It is recommended that valuable credentials, such as the sign-in credentials, aren't to be used with any of these protocols. If these protocols must be used by domain or Azure AD users, secondary credentials should be provisioned for these use cases.
|
||||
|
||||
When Windows Defender Credential Guard is enabled, Kerberos does not allow unconstrained Kerberos delegation or DES encryption, not only for signed-in credentials, but also prompted or saved credentials.
|
||||
When Windows Defender Credential Guard is enabled, Kerberos doesn't allow unconstrained Kerberos delegation or DES encryption, not only for signed-in credentials, but also prompted or saved credentials.
|
||||
|
||||
Here's a high-level overview on how the LSA is isolated by using Virtualization-based security:
|
||||
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Windows Defender Credential Guard - Known issues (Windows)
|
||||
description: Windows Defender Credential Guard - Known issues in Windows Enterprise
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Manage Windows Defender Credential Guard (Windows)
|
||||
description: Learn how to deploy and manage Windows Defender Credential Guard using Group Policy, the registry, or hardware readiness tools.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: v-tappelgate
|
||||
manager: dansimp
|
||||
@ -53,19 +49,21 @@ You can use Group Policy to enable Windows Defender Credential Guard. This will
|
||||
|
||||
To enforce processing of the group policy, you can run `gpupdate /force`.
|
||||
|
||||
### Enable Windows Defender Credential Guard by using Intune
|
||||
### Enable Windows Defender Credential Guard by using Microsoft Endpoint Manager
|
||||
|
||||
1. From **Home**, select **Microsoft Intune**.
|
||||
1. From **Microsoft Endpoint Manager admin center**, select **Devices**.
|
||||
|
||||
1. Select **Device configuration**.
|
||||
1. Select **Configuration Profiles**.
|
||||
|
||||
1. Select **Profiles** > **Create Profile** > **Endpoint protection** > **Windows Defender Credential Guard**.
|
||||
1. Select **Create Profile** > **Windows 10 and later** > **Settings catalog** > **Create**.
|
||||
|
||||
> [!NOTE]
|
||||
> It will enable VBS and Secure Boot and you can do it with or without UEFI Lock. If you will need to disable Credential Guard remotely, enable it without UEFI lock.
|
||||
1. Configuration settings: In the settings picker select **Device Guard** as category and add the needed settings.
|
||||
|
||||
> [!NOTE]
|
||||
> Enable VBS and Secure Boot and you can do it with or without UEFI Lock. If you will need to disable Credential Guard remotely, enable it without UEFI lock.
|
||||
|
||||
> [!TIP]
|
||||
> You can also configure Credential Guard by using an account protection profile in endpoint security. For more information, see [Account protection policy settings for endpoint security in Intune](/mem/intune/protect/endpoint-security-account-protection-profile-settings).
|
||||
> You can also configure Credential Guard by using an account protection profile in endpoint security. For more information, see [Account protection policy settings for endpoint security in Microsoft Endpoint Manager](/mem/intune/protect/endpoint-security-account-protection-profile-settings).
|
||||
|
||||
### Enable Windows Defender Credential Guard by using the registry
|
||||
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Windows Defender Credential Guard protection limits & mitigations (Windows)
|
||||
description: Scenarios not protected by Windows Defender Credential Guard in Windows, and additional mitigations you can use.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Windows Defender Credential Guard protection limits (Windows)
|
||||
description: Some ways to store credentials are not protected by Windows Defender Credential Guard in Windows. Learn more with this guide.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
@ -28,18 +24,18 @@ Some ways to store credentials are not protected by Windows Defender Credential
|
||||
|
||||
- Software that manages credentials outside of Windows feature protection
|
||||
- Local accounts and Microsoft Accounts
|
||||
- Windows Defender Credential Guard does not protect the Active Directory database running on Windows Server 2016 domain controllers. It also does not protect credential input pipelines, such as Windows Server 2016 servers running Remote Desktop Gateway. If you're using a Windows Server 2016 server as a client PC, it will get the same protection as it would when running Windows 10 Enterprise.
|
||||
- Windows Defender Credential Guard doesn't protect the Active Directory database running on Windows Server 2016 domain controllers. It also doesn't protect credential input pipelines, such as Windows Server 2016 servers running Remote Desktop Gateway. If you're using a Windows Server 2016 server as a client PC, it will get the same protection as it would when running Windows 10 Enterprise.
|
||||
- Key loggers
|
||||
- Physical attacks
|
||||
- Does not prevent an attacker with malware on the PC from using the privileges associated with any credential. We recommend using dedicated PCs for high value accounts, such as IT Pros and users with access to high value assets in your organization.
|
||||
- Doesn't prevent an attacker with malware on the PC from using the privileges associated with any credential. We recommend using dedicated PCs for high value accounts, such as IT Pros and users with access to high value assets in your organization.
|
||||
- Third-party security packages
|
||||
- Digest and CredSSP credentials
|
||||
- When Windows Defender Credential Guard is enabled, neither Digest nor CredSSP have access to users' logon credentials. This implies no Single Sign-On use for these protocols.
|
||||
- Supplied credentials for NTLM authentication are not protected. If a user is prompted for and enters credentials for NTLM authentication, these credentials are vulnerable to be read from LSASS memory. Note that these same credentials are vulnerable to key loggers as well.-
|
||||
- Kerberos service tickets are not protected by Credential Guard, but the Kerberos Ticket Granting Ticket (TGT) is.
|
||||
- When Windows Defender Credential Guard is deployed on a VM, Windows Defender Credential Guard protects secrets from attacks inside the VM. However, it does not provide additional protection from privileged system attacks originating from the host.
|
||||
- Supplied credentials for NTLM authentication aren't protected. If a user is prompted for and enters credentials for NTLM authentication, these credentials are vulnerable to be read from LSASS memory. These same credentials are vulnerable to key loggers as well.-
|
||||
- Kerberos service tickets aren't protected by Credential Guard, but the Kerberos Ticket Granting Ticket (TGT) is.
|
||||
- When Windows Defender Credential Guard is deployed on a VM, Windows Defender Credential Guard protects secrets from attacks inside the VM. However, it doesn't provide additional protection from privileged system attacks originating from the host.
|
||||
- Windows logon cached password verifiers (commonly called "cached credentials")
|
||||
do not qualify as credentials because they cannot be presented to another computer for authentication, and can only be used locally to verify credentials. They are stored in the registry on the local computer and provide validation for credentials when a domain-joined computer cannot connect to AD DS during user logon. These “cached logons”, or more specifically, cached domain account information, can be managed using the security policy setting **Interactive logon: Number of previous logons to cache** if a domain controller is not available.
|
||||
don't qualify as credentials because they can't be presented to another computer for authentication, and can only be used locally to verify credentials. They're stored in the registry on the local computer and provide validation for credentials when a domain-joined computer can't connect to AD DS during user logon. These “cached logons”, or more specifically, cached domain account information, can be managed using the security policy setting **Interactive logon: Number of previous logons to cache** if a domain controller isn't available.
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Windows Defender Credential Guard Requirements (Windows)
|
||||
description: Windows Defender Credential Guard baseline hardware, firmware, and software requirements, and additional protections for improved security.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Scripts for Certificate Issuance Policies in Windows Defender Credential Guard (Windows)
|
||||
description: Obtain issuance policies from the certificate authority for Windows Defender Credential Guard on Windows.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dulcemontemayor
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
|
||||
@ -1,14 +1,9 @@
|
||||
---
|
||||
title: Protect derived domain credentials with Windows Defender Credential Guard (Windows)
|
||||
description: Windows Defender Credential Guard uses virtualization-based security to isolate secrets so that only privileged system software can access them.
|
||||
ms.assetid: 4F1FE390-A166-4A24-8530-EA3369FEB4B1
|
||||
ms.reviewer:
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
@ -43,3 +38,8 @@ By enabling Windows Defender Credential Guard, the following features and soluti
|
||||
- [What's New in Kerberos Authentication for Windows Server 2012](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831747(v=ws.11))
|
||||
- [Authentication Mechanism Assurance for AD DS in Windows Server 2008 R2 Step-by-Step Guide](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd378897(v=ws.10))
|
||||
- [Trusted Platform Module](/windows/device-security/tpm/trusted-platform-module-overview)
|
||||
- [Mitigating Credential Theft using the Windows 10 Isolated User Mode](/shows/seth-juarez/mitigating-credential-theft-using-windows-10-isolated-user-mode)
|
||||
- [Isolated User Mode Processes and Features in Windows 10 with Logan Gabriel](/shows/seth-juarez/isolated-user-mode-processes-features-in-windows-10-logan-gabriel)
|
||||
- [More on Processes and Features in Windows 10 Isolated User Mode with Dave Probert](/shows/seth-juarez/more-on-processes-features-in-windows-10-isolated-user-mode-dave-probert)
|
||||
- [Isolated User Mode in Windows 10 with Dave Probert](/shows/seth-juarez/isolated-user-mode-in-windows-10-dave-probert)
|
||||
- [Windows 10 Virtual Secure Mode with David Hepkin](/shows/seth-juarez/windows-10-virtual-secure-mode-david-hepkin)
|
||||
|
||||
@ -2,11 +2,7 @@
|
||||
title: Windows Defender Device Guard and Windows Defender Credential Guard hardware readiness tool
|
||||
description: Windows Defender Device Guard and Windows Defender Credential Guard hardware readiness tool script
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: SteveSyfuhs
|
||||
ms.author: stsyfuhs
|
||||
manager: dansimp
|
||||
|
||||
@ -1,9 +1,6 @@
|
||||
---
|
||||
title: Enterprise Certificate Pinning
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
description: Enterprise certificate pinning is a Windows feature for remembering; or pinning a root issuing certificate authority, or end entity certificate to a given domain name.
|
||||
audience: ITPro
|
||||
author: dulcemontemayor
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
@ -11,7 +8,6 @@ ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.prod: m365-security
|
||||
ms.technology: windows-sec
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.reviewer:
|
||||
|
||||
@ -2,10 +2,6 @@
|
||||
title: WebAuthn APIs
|
||||
description: Learn how to use WebAuthn APIs to enable password-less authentication for your sites and apps.
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Multi-factor Unlock
|
||||
description: Learn how Windows 10 and Windows 11 offer multi-factor device unlock by extending Windows Hello with trusted signals.
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, hybrid, cert-trust, device, registration, unlock, multi, factor, multifactor, multi-factor
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Azure Active Directory join cloud only deployment
|
||||
description: Use this deployment guide to successfully use Azure Active Directory to join a Windows 10 or Windows 11 device.
|
||||
keywords: identity, Hello, Active Directory, cloud,
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Having enough Domain Controllers for Windows Hello for Business deployments
|
||||
description: Guide for planning to have an adequate number of Windows Server 2016 or later Domain Controllers for Windows Hello for Business deployments
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, hybrid, key-trust
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,13 +1,8 @@
|
||||
---
|
||||
title: Windows Hello and password changes (Windows)
|
||||
description: When you change your password on a device, you may need to sign in with a password on other devices to reset Hello.
|
||||
ms.assetid: 83005FE4-8899-47A6-BEA9-C17CCA0B6B55
|
||||
ms.reviewer:
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,13 +1,7 @@
|
||||
---
|
||||
title: Windows Hello biometrics in the enterprise (Windows)
|
||||
description: Windows Hello uses biometrics to authenticate users and guard against potential spoofing, through fingerprint matching and facial recognition.
|
||||
ms.assetid: d3f27d94-2226-4547-86c0-65c84d6df8Bc
|
||||
keywords: Windows Hello, enterprise biometrics
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Prepare and Deploy Windows AD FS certificate trust (Windows Hello for Business)
|
||||
description: Learn how to Prepare and Deploy Windows Server 2016 Active Directory Federation Services (AD FS) for Windows Hello for Business, using certificate trust.
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Configure Windows Hello for Business Policy settings - certificate trust
|
||||
description: Configure Windows Hello for Business Policy settings for Windows Hello for Business. Certificate-based deployments need three group policy settings.
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
@ -60,7 +55,7 @@ The Group Policy object contains the policy settings needed to trigger Windows H
|
||||
3. Right-click **Group Policy object** and select **New**.
|
||||
4. Type *Enable Windows Hello for Business* in the name box and click **OK**.
|
||||
5. In the content pane, right-click the **Enable Windows Hello for Business** Group Policy object and click **Edit**.
|
||||
6. In the navigation pane, expand **Policies** under **User Configuration**.
|
||||
6. In the navigation pane, expand **Policies** under **User Configuration** (this is the only option for Windows Server 2016, but for Windows Server 2019 and later this step can also be done in **Computer Configuration**).
|
||||
7. Expand **Administrative Templates > Windows Component**, and select **Windows Hello for Business**.
|
||||
8. In the content pane, double-click **Use Windows Hello for Business**. Click **Enable** and click **OK**.
|
||||
9. Double-click **Use certificate for on-premises authentication**. Click **Enable** and click **OK**. Close the **Group Policy Management Editor**.
|
||||
@ -70,7 +65,7 @@ The Group Policy object contains the policy settings needed to trigger Windows H
|
||||
1. Start the **Group Policy Management Console** (gpmc.msc).
|
||||
2. Expand the domain and select the **Group Policy Object** node in the navigation pane.
|
||||
3. Right-click the **Enable Windows Hello for Business** Group Policy object and click **Edit**.
|
||||
4. In the navigation pane, expand **Policies** under **User Configuration**.
|
||||
4. In the navigation pane, expand **Policies** under **User Configuration** (this is the only option for Windows Server 2016, but for Windows Server 2019 and later this step can also be done in **Computer Configuration**).
|
||||
5. Expand **Windows Settings > Security Settings**, and click **Public Key Policies**.
|
||||
6. In the details pane, right-click **Certificate Services Client – Auto-Enrollment** and select **Properties**.
|
||||
7. Select **Enabled** from the **Configuration Model** list.
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Update Active Directory schema for cert-trust deployment (Windows Hello for Business)
|
||||
description: How to Validate Active Directory prerequisites for Windows Hello for Business when deploying with the certificate trust model.
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
@ -25,7 +20,10 @@ ms.reviewer:
|
||||
- On-premises deployment
|
||||
- Certificate trust
|
||||
|
||||
The key registration process for the On-premises deployment of Windows Hello for Business needs the Windows Server 2016 Active Directory or later schema. The key-trust model receives the schema extension when the first Windows Server 2016 or later domain controller is added to the forest. The certificate trust model requires manually updating the current schema to the Windows Server 2016 or later schema. If you already have a Windows Server 2016 or later domain controller in your forest, you can skip the **Updating the Schema** and **Create the KeyCredential Admins Security Global Group** steps.
|
||||
The key registration process for the on-premises deployment of Windows Hello for Business needs the Windows Server 2016 Active Directory or later schema. The key-trust model receives the schema extension when the first Windows Server 2016 or later domain controller is added to the forest. The certificate trust model requires manually updating the current schema to the Windows Server 2016 or later schema.
|
||||
|
||||
> [!NOTE]
|
||||
> If you already have a Windows Server 2016 or later domain controller in your forest, you can skip the "Updating the Schema" and "Create the KeyCredential Admins Security Global Group" steps that follow.
|
||||
|
||||
Manually updating Active Directory uses the command-line utility **adprep.exe** located at **\<drive>:\support\adprep** on the Windows Server 2016 or later DVD or ISO. Before running adprep.exe, you must identify the domain controller hosting the schema master role.
|
||||
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Validate and Deploy MFA for Windows Hello for Business with certificate trust
|
||||
description: How to Validate and Deploy Multi-factor Authentication (MFA) Services for Windows Hello for Business with certificate trust
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Validate Public Key Infrastructure - certificate trust model (Windows Hello for Business)
|
||||
description: How to Validate Public Key Infrastructure for Windows Hello for Business, under a certificate trust model.
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business Deployment Guide - On Premises Certificate Trust Deployment
|
||||
description: A guide to on premises, certificate trust Windows Hello for Business deployment.
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business Deployment Overview
|
||||
description: Use this deployment guide to successfully deploy Windows Hello for Business in an existing environment.
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,13 +1,8 @@
|
||||
---
|
||||
title: Windows Hello for Business Deployment Known Issues
|
||||
description: A Troubleshooting Guide for Known Windows Hello for Business Deployment Issues
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
params: siblings_only
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business Deployment Guide - On Premises Key Deployment
|
||||
description: A guide to on premises, key trust Windows Hello for Business deployment.
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Deploying Certificates to Key Trust Users to Enable RDP
|
||||
description: Learn how to deploy certificates to a Key Trust user to enable remote desktop with supplied credentials
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, hybrid, cert-trust, device, registration, unlock, remote desktop, RDP
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,13 +1,7 @@
|
||||
---
|
||||
title: Windows Hello errors during PIN creation (Windows)
|
||||
description: When you set up Windows Hello in Windows 10/11, you may get an error during the Create a work PIN step.
|
||||
ms.assetid: DFEFE22C-4FEF-4FD9-BFC4-9B419C339502
|
||||
keywords: PIN, error, create a work PIN
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,14 +1,8 @@
|
||||
---
|
||||
title: Event ID 300 - Windows Hello successfully created (Windows)
|
||||
description: This event is created when a Windows Hello for Business is successfully created and registered with Azure Active Directory (Azure AD).
|
||||
ms.assetid: 0DD59E75-1C5F-4CC6-BB0E-71C83884FF04
|
||||
ms.reviewer:
|
||||
keywords: ngc
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Conditional Access
|
||||
description: Ensure that only approved users can access your devices, applications, and services from anywhere by enabling single sign-on with Azure Active Directory.
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, hybrid, cert-trust, device, registration, unlock, conditional access
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Dual Enrollment
|
||||
description: Learn how to configure Windows Hello for Business dual enrollment. Also, learn how to configure Active Directory to support Domain Administrator enrollment.
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, hybrid, cert-trust, device, registration, unlock, dual enrollment,
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
@ -1,19 +1,14 @@
|
||||
---
|
||||
title: Dynamic lock
|
||||
description: Learn how to set Dynamic lock on Windows 10 and Windows 11 devices, by configuring group policies. This feature locks a device when a Bluetooth signal falls below a set value.
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, hybrid, cert-trust, device, registration, unlock, conditional access
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 09/09/2019
|
||||
ms.date: 07/12/2022
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
@ -25,6 +20,9 @@ ms.reviewer:
|
||||
|
||||
Dynamic lock enables you to configure Windows devices to automatically lock when Bluetooth paired device signal falls below the maximum Received Signal Strength Indicator (RSSI) value. This makes it more difficult for someone to gain access to your device if you step away from your PC and forget to lock it.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This feature only locks the computer if the Bluetooth signal falls and the system is idle. If the system isn't idle (for example, an intruder gets access _before_ the Bluetooth signal falls below the limit), the device won't lock. Therefore, the dynamic lock feature is an additional barrier. It doesn't replace the need for the user to lock the computer. It only reduces the probability of someone gaining access if the user forgets to lock it.
|
||||
|
||||
You configure the dynamic lock policy using Group Policy. You can locate the policy setting at **Computer Configuration\Administrative Templates\Windows Components\Windows Hello for Business**. The name of the policy is **Configure dynamic lock factors**.
|
||||
|
||||
The Group Policy Editor, when the policy is enabled, creates a default signal rule policy with the following value:
|
||||
|
||||
@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Pin Reset
|
||||
description: Learn how Microsoft PIN reset services enables you to help users recover who have forgotten their PIN.
|
||||
keywords: identity, PIN, Hello, passport, WHFB, hybrid, cert-trust, device, reset
|
||||
ms.prod: m365-security
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: GitPrakhar13
|
||||
ms.author: prsriva
|
||||
manager: dansimp
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user