mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-17 15:57:23 +00:00
Merge branch 'release-win11-2309' of https://github.com/MicrosoftDocs/windows-docs-pr into tempctrl-sept-8092554
This commit is contained in:
commit
6ded00bee5
@ -76,7 +76,7 @@
|
|||||||
href: operate/windows-autopatch-edge.md
|
href: operate/windows-autopatch-edge.md
|
||||||
- name: Microsoft Teams
|
- name: Microsoft Teams
|
||||||
href: operate/windows-autopatch-teams.md
|
href: operate/windows-autopatch-teams.md
|
||||||
- name: Windows quality and feature update reports
|
- name: Windows quality and feature update reports overview
|
||||||
href: operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md
|
href: operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md
|
||||||
items:
|
items:
|
||||||
- name: Windows quality update reports
|
- name: Windows quality update reports
|
||||||
|
@ -21,9 +21,10 @@ ms.collection:
|
|||||||
|
|
||||||
The Windows quality reports provide you with information about:
|
The Windows quality reports provide you with information about:
|
||||||
|
|
||||||
Quality update device readiness
|
- Quality update device readiness
|
||||||
Device update health
|
- Device update health
|
||||||
Device update alerts
|
- Device update alerts
|
||||||
|
|
||||||
Together, these reports provide insight into the quality update state and compliance of Windows devices that are enrolled into Windows Autopatch.
|
Together, these reports provide insight into the quality update state and compliance of Windows devices that are enrolled into Windows Autopatch.
|
||||||
|
|
||||||
The Windows quality report types are organized into the following focus areas:
|
The Windows quality report types are organized into the following focus areas:
|
||||||
@ -106,4 +107,4 @@ Within each 24-hour reporting period, devices that are Not Ready are reevaluated
|
|||||||
|
|
||||||
## Data export
|
## Data export
|
||||||
|
|
||||||
Select **Export devices** to export data for each report type. Only selected columns will be exported.
|
Select **Export devices** to export data for each report type. Only selected columns are exported.
|
||||||
|
@ -32,7 +32,7 @@ You can set several rule options within a WDAC policy. Table 1 describes each ru
|
|||||||
| **3 Enabled:Audit Mode (Default)** | Instructs WDAC to log information about applications, binaries, and scripts that would have been blocked, if the policy was enforced. You can use this option to identify the potential impact of your WDAC policy, and use the audit events to refine the policy before enforcement. To enforce a WDAC policy, delete this option. | No |
|
| **3 Enabled:Audit Mode (Default)** | Instructs WDAC to log information about applications, binaries, and scripts that would have been blocked, if the policy was enforced. You can use this option to identify the potential impact of your WDAC policy, and use the audit events to refine the policy before enforcement. To enforce a WDAC policy, delete this option. | No |
|
||||||
| **4 Disabled:Flight Signing** | If enabled, binaries from Windows Insider builds aren't trusted. This option is useful for organizations that only want to run released binaries, not prerelease Windows builds. | No |
|
| **4 Disabled:Flight Signing** | If enabled, binaries from Windows Insider builds aren't trusted. This option is useful for organizations that only want to run released binaries, not prerelease Windows builds. | No |
|
||||||
| **5 Enabled:Inherit Default Policy** | This option is reserved for future use and currently has no effect. | Yes |
|
| **5 Enabled:Inherit Default Policy** | This option is reserved for future use and currently has no effect. | Yes |
|
||||||
| **6 Enabled:Unsigned System Integrity Policy (Default)** | Allows the policy to remain unsigned. When this option is removed, the policy must be signed and any supplemental policies must also be signed. The certificates that are trusted for future policy updates must be identified in the UpdatePolicySigners section. Certificates that are trusted for supplemental policies must be identified in the SupplementalPolicySigners section. | Yes |
|
| **6 Enabled:Unsigned System Integrity Policy (Default)** | Allows the policy to remain unsigned. When this option is removed, the policy must be signed and any supplemental policies must also be signed. The certificates that are trusted for future policy updates must be identified in the UpdatePolicySigners section. Certificates that are trusted for supplemental policies must be identified in the SupplementalPolicySigners section. | No |
|
||||||
| **7 Allowed:Debug Policy Augmented** | This option isn't currently supported. | Yes |
|
| **7 Allowed:Debug Policy Augmented** | This option isn't currently supported. | Yes |
|
||||||
| **8 Required:EV Signers** | This option isn't currently supported. | No |
|
| **8 Required:EV Signers** | This option isn't currently supported. | No |
|
||||||
| **9 Enabled:Advanced Boot Options Menu** | The F8 preboot menu is disabled by default for all WDAC policies. Setting this rule option allows the F8 menu to appear to physically present users. | No |
|
| **9 Enabled:Advanced Boot Options Menu** | The F8 preboot menu is disabled by default for all WDAC policies. Setting this rule option allows the F8 menu to appear to physically present users. | No |
|
||||||
|
Loading…
x
Reference in New Issue
Block a user