deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

errorreporting eventlogservice experience

Browse Source
This commit is contained in:
Liz Long 2022-12-30 15:29:28 -05:00
parent 6c0dd8c1ae
commit 141f6913c5
3 changed files with 2126 additions and 1474 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

459
windows/client-management/mdm/policy-csp-errorreporting.md
View File

@ -1,302 +1,351 @@
--- ---
title: Policy CSP - ErrorReporting title: ErrorReporting Policy CSP
description: Learn how to use the Policy CSP - ErrorReporting setting to determine the consent behavior of Windows Error Reporting for specific event types. description: Learn more about the ErrorReporting Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.topic: article ms.date: 12/29/2022
ms.localizationpriority: medium
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.localizationpriority: medium
ms.date: 09/27/2019
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ErrorReporting-Begin -->
# Policy CSP - ErrorReporting # Policy CSP - ErrorReporting
> [!TIP] > [!TIP]
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md). > Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
> >
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy). > You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
> >
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). > The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<hr/> <!-- ErrorReporting-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ErrorReporting-Editable-End -->
<!--Policies--> <!-- CustomizeConsentSettings-Begin -->
## ErrorReporting policies ## CustomizeConsentSettings
<dl> <!-- CustomizeConsentSettings-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#errorreporting-customizeconsentsettings">ErrorReporting/CustomizeConsentSettings</a> |:--|:--|:--|
</dd> | :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<dd> <!-- CustomizeConsentSettings-Applicability-End -->
<a href="#errorreporting-disablewindowserrorreporting">ErrorReporting/DisableWindowsErrorReporting</a>
</dd>
<dd>
<a href="#errorreporting-displayerrornotification">ErrorReporting/DisplayErrorNotification</a>
</dd>
<dd>
<a href="#errorreporting-donotsendadditionaldata">ErrorReporting/DoNotSendAdditionalData</a>
</dd>
<dd>
<a href="#errorreporting-preventcriticalerrordisplay">ErrorReporting/PreventCriticalErrorDisplay</a>
</dd>
</dl>
<hr/> <!-- CustomizeConsentSettings-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ErrorReporting/CustomizeConsentSettings
```
<!-- CustomizeConsentSettings-OmaUri-End -->
<!--Policy--> <!-- CustomizeConsentSettings-Description-Begin -->
<a href="" id="errorreporting-customizeconsentsettings"></a>**ErrorReporting/CustomizeConsentSettings** <!-- Description-Source-ADMX -->
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting determines the consent behavior of Windows Error Reporting for specific event types. This policy setting determines the consent behavior of Windows Error Reporting for specific event types.
If you enable this policy setting, you can add specific event types to a list by clicking Show, and typing event types in the Value Name column of the Show Contents dialog box. Event types are those even types for generic, non-fatal errors: crash, no response, and kernel fault errors. For each specified event type, you can set a consent level of 0, 1, 2, 3, or 4. If you enable this policy setting, you can add specific event types to a list by clicking Show, and typing event types in the Value Name column of the Show Contents dialog box. Event types are those for generic, non-fatal errors: crash, no response, and kernel fault errors. For each specified event type, you can set a consent level of 0, 1, 2, 3, or 4.
- 0 (Disable): Windows Error Reporting sends no data to Microsoft for this event type. - 0 (Disable): Windows Error Reporting sends no data to Microsoft for this event type.
- 1 (Always ask before sending data): Windows prompts the user for consent to send reports. - 1 (Always ask before sending data): Windows prompts the user for consent to send reports.
- 2 (Send parameters): Windows Error Reporting automatically sends the minimum data required to check for an existing solution, and Windows prompts the user for consent to send any extra data requested by Microsoft. - 2 (Send parameters): Windows Error Reporting automatically sends the minimum data required to check for an existing solution, and Windows prompts the user for consent to send any additional data requested by Microsoft.
- 3 (Send parameters and safe extra data): Windows Error Reporting automatically sends the minimum data required to check for an existing solution, and data which Windows has determined (within a high probability) doesn't contain personally identifiable data, and prompts the user for consent, to send any extra data requested by Microsoft. - 3 (Send parameters and safe additional data): Windows Error Reporting automatically sends the minimum data required to check for an existing solution, as well as data which Windows has determined (within a high probability) does not contain personally identifiable data, and prompts the user for consent to send any additional data requested by Microsoft.
- 4 (Send all data): Any data requested by Microsoft is sent automatically. - 4 (Send all data): Any data requested by Microsoft is sent automatically.
If you disable or don't configure this policy setting, then the default consent settings that are applied are those settings specified by the user in Control Panel, or in the Configure Default Consent policy setting. If you disable or do not configure this policy setting, then the default consent settings that are applied are those specified by the user in Control Panel, or in the Configure Default Consent policy setting.
<!-- CustomizeConsentSettings-Description-End -->
<!--/Description--> <!-- CustomizeConsentSettings-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- CustomizeConsentSettings-Editable-End -->
<!--ADMXBacked--> <!-- CustomizeConsentSettings-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Customize consent settings*
- GP name: *WerConsentCustomize_2*
- GP path: *Windows Components/Windows Error Reporting/Consent*
- GP ADMX file name: *ErrorReporting.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- CustomizeConsentSettings-DFProperties-End -->
<hr/> <!-- CustomizeConsentSettings-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="errorreporting-disablewindowserrorreporting"></a>**ErrorReporting/DisableWindowsErrorReporting**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | WerConsentCustomize |
| Friendly Name | Customize consent settings |
| Location | Computer Configuration |
| Path | Windows Components > Windows Error Reporting > Consent |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting\Consent |
| ADMX File Name | ErrorReporting.admx |
<!-- CustomizeConsentSettings-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- CustomizeConsentSettings-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- CustomizeConsentSettings-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- CustomizeConsentSettings-End -->
<hr/>
<!--Scope--> <!-- DisableWindowsErrorReporting-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## DisableWindowsErrorReporting
> [!div class = "checklist"] <!-- DisableWindowsErrorReporting-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- DisableWindowsErrorReporting-Applicability-End -->
<hr/> <!-- DisableWindowsErrorReporting-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ErrorReporting/DisableWindowsErrorReporting
```
<!-- DisableWindowsErrorReporting-OmaUri-End -->
<!--/Scope--> <!-- DisableWindowsErrorReporting-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting turns off Windows Error Reporting, so that reports aren't collected or sent to either Microsoft or internal servers within your organization, when software unexpectedly stops working or fails. This policy setting turns off Windows Error Reporting, so that reports are not collected or sent to either Microsoft or internal servers within your organization when software unexpectedly stops working or fails.
If you enable this policy setting, Windows Error Reporting doesn't send any problem information to Microsoft. Additionally, solution information isn't available in Security and Maintenance in Control Panel. If you enable this policy setting, Windows Error Reporting does not send any problem information to Microsoft. Additionally, solution information is not available in Security and Maintenance in Control Panel.
If you disable or don't configure this policy setting, the Turn off Windows Error Reporting policy setting in Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings takes precedence. If Turn off Windows Error Reporting is also either disabled or not configured, user settings in Control Panel for Windows Error Reporting are applied. If you disable or do not configure this policy setting, the Turn off Windows Error Reporting policy setting in Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings takes precedence. If Turn off Windows Error Reporting is also either disabled or not configured, user settings in Control Panel for Windows Error Reporting are applied.
<!-- DisableWindowsErrorReporting-Description-End -->
<!--/Description--> <!-- DisableWindowsErrorReporting-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DisableWindowsErrorReporting-Editable-End -->
<!--ADMXBacked--> <!-- DisableWindowsErrorReporting-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Disable Windows Error Reporting*
- GP name: *WerDisable_2*
- GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- DisableWindowsErrorReporting-DFProperties-End -->
<hr/> <!-- DisableWindowsErrorReporting-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="errorreporting-displayerrornotification"></a>**ErrorReporting/DisplayErrorNotification**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | WerDisable |
| Friendly Name | Disable Windows Error Reporting |
| Location | Computer Configuration |
| Path | Windows Components > Windows Error Reporting |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting |
| Registry Value Name | Disabled |
| ADMX File Name | ErrorReporting.admx |
<!-- DisableWindowsErrorReporting-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- DisableWindowsErrorReporting-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- DisableWindowsErrorReporting-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- DisableWindowsErrorReporting-End -->
<hr/>
<!--Scope--> <!-- DisplayErrorNotification-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## DisplayErrorNotification
> [!div class = "checklist"] <!-- DisplayErrorNotification-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- DisplayErrorNotification-Applicability-End -->
<hr/> <!-- DisplayErrorNotification-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ErrorReporting/DisplayErrorNotification
```
<!-- DisplayErrorNotification-OmaUri-End -->
<!--/Scope--> <!-- DisplayErrorNotification-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting controls, whether users are shown an error dialog box that lets them report an error. This policy setting controls whether users are shown an error dialog box that lets them report an error.
If you enable this policy setting, users are notified in a dialog box that an error has occurred, and can display more details about the error. If the Configure Error Reporting policy setting is also enabled, the user can also report the error. If you enable this policy setting, users are notified in a dialog box that an error has occurred, and can display more details about the error. If the Configure Error Reporting policy setting is also enabled, the user can also report the error.
If you disable this policy setting, users aren't notified that errors have occurred. If the Configure Error Reporting policy setting is also enabled, errors are reported, but users receive no notification. Disabling this policy setting is useful for servers that don't have interactive users. If you disable this policy setting, users are not notified that errors have occurred. If the Configure Error Reporting policy setting is also enabled, errors are reported, but users receive no notification. Disabling this policy setting is useful for servers that do not have interactive users.
If you don't configure this policy setting, users can change this setting in Control Panel, which is set to enable notification by default on computers that are running Windows XP Personal Edition and Windows XP Professional Edition, and disable notification by default on computers that are running Windows Server. If you do not configure this policy setting, users can change this setting in Control Panel, which is set to enable notification by default on computers that are running Windows XP Personal Edition and Windows XP Professional Edition, and disable notification by default on computers that are running Windows Server.
See also the Configure Error Reporting policy setting. See also the Configure Error Reporting policy setting.
<!-- DisplayErrorNotification-Description-End -->
<!--/Description--> <!-- DisplayErrorNotification-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DisplayErrorNotification-Editable-End -->
<!--ADMXBacked--> <!-- DisplayErrorNotification-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Display Error Notification*
- GP name: *PCH_ShowUI*
- GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- DisplayErrorNotification-DFProperties-End -->
<hr/> <!-- DisplayErrorNotification-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="errorreporting-donotsendadditionaldata"></a>**ErrorReporting/DoNotSendAdditionalData**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | PCH_ShowUI |
| Friendly Name | Display Error Notification |
| Location | Computer Configuration |
| Path | Windows Components > Windows Error Reporting |
| Registry Key Name | Software\Policies\Microsoft\PCHealth\ErrorReporting |
| Registry Value Name | ShowUI |
| ADMX File Name | ErrorReporting.admx |
<!-- DisplayErrorNotification-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- DisplayErrorNotification-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- DisplayErrorNotification-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- DisplayErrorNotification-End -->
<hr/>
<!--Scope--> <!-- DoNotSendAdditionalData-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## DoNotSendAdditionalData
> [!div class = "checklist"] <!-- DoNotSendAdditionalData-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- DoNotSendAdditionalData-Applicability-End -->
<hr/> <!-- DoNotSendAdditionalData-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ErrorReporting/DoNotSendAdditionalData
```
<!-- DoNotSendAdditionalData-OmaUri-End -->
<!--/Scope--> <!-- DoNotSendAdditionalData-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting controls, whether extra data in support of error reports can be sent to Microsoft automatically. This policy setting controls whether additional data in support of error reports can be sent to Microsoft automatically.
If you enable this policy setting, any extra data requests from Microsoft in response to a Windows Error Reporting report are automatically declined, without notification to the user. If you enable this policy setting, any additional data requests from Microsoft in response to a Windows Error Reporting report are automatically declined, without notification to the user.
If you disable or don't configure this policy setting, then consent policy settings in Computer Configuration/Administrative Templates/Windows Components/Windows Error Reporting/Consent take precedence. If you disable or do not configure this policy setting, then consent policy settings in Computer Configuration/Administrative Templates/Windows Components/Windows Error Reporting/Consent take precedence.
<!-- DoNotSendAdditionalData-Description-End -->
<!--/Description--> <!-- DoNotSendAdditionalData-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DoNotSendAdditionalData-Editable-End -->
<!--ADMXBacked--> <!-- DoNotSendAdditionalData-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Do not send additional data*
- GP name: *WerNoSecondLevelData_2*
- GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- DoNotSendAdditionalData-DFProperties-End -->
<hr/> <!-- DoNotSendAdditionalData-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="errorreporting-preventcriticalerrordisplay"></a>**ErrorReporting/PreventCriticalErrorDisplay**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | WerNoSecondLevelData |
| Friendly Name | Do not send additional data |
| Location | Computer Configuration |
| Path | Windows Components > Windows Error Reporting |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting |
| Registry Value Name | DontSendAdditionalData |
| ADMX File Name | ErrorReporting.admx |
<!-- DoNotSendAdditionalData-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- DoNotSendAdditionalData-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- DoNotSendAdditionalData-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- DoNotSendAdditionalData-End -->
<hr/>
<!--Scope--> <!-- PreventCriticalErrorDisplay-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## PreventCriticalErrorDisplay
> [!div class = "checklist"] <!-- PreventCriticalErrorDisplay-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- PreventCriticalErrorDisplay-Applicability-End -->
<hr/> <!-- PreventCriticalErrorDisplay-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ErrorReporting/PreventCriticalErrorDisplay
```
<!-- PreventCriticalErrorDisplay-OmaUri-End -->
<!--/Scope--> <!-- PreventCriticalErrorDisplay-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting prevents the display of the user interface for critical errors. This policy setting prevents the display of the user interface for critical errors.
If you enable this policy setting, Windows Error Reporting doesn't display any GUI-based error messages or dialog boxes for critical errors. If you enable or do not configure this policy setting, Windows Error Reporting does not display any GUI-based error messages or dialog boxes for critical errors.
If you disable or don't configure this policy setting, Windows Error Reporting displays the user interface for critical errors. If you disable this policy setting, Windows Error Reporting displays the GUI-based error messages or dialog boxes for critical errors.
<!-- PreventCriticalErrorDisplay-Description-End -->
<!--/Description--> <!-- PreventCriticalErrorDisplay-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- PreventCriticalErrorDisplay-Editable-End -->
<!--ADMXBacked--> <!-- PreventCriticalErrorDisplay-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Prevent display of the user interface for critical errors*
- GP name: *WerDoNotShowUI*
- GP path: *Windows Components/Windows Error Reporting*
- GP ADMX file name: *ErrorReporting.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
<hr/> | Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- PreventCriticalErrorDisplay-DFProperties-End -->
<!-- PreventCriticalErrorDisplay-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--/Policies--> **ADMX mapping**:
## Related topics | Name | Value |
|:--|:--|
| Name | WerDoNotShowUI |
| Friendly Name | Prevent display of the user interface for critical errors |
| Location | Computer Configuration |
| Path | Windows Components > Windows Error Reporting |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting |
| Registry Value Name | DontShowUI |
| ADMX File Name | ErrorReporting.admx |
<!-- PreventCriticalErrorDisplay-AdmxBacked-End -->
<!-- PreventCriticalErrorDisplay-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- PreventCriticalErrorDisplay-Examples-End -->
<!-- PreventCriticalErrorDisplay-End -->
<!-- ErrorReporting-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ErrorReporting-CspMoreInfo-End -->
<!-- ErrorReporting-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md) [Policy configuration service provider](policy-configuration-service-provider.md)

373
windows/client-management/mdm/policy-csp-eventlogservice.md
View File

@ -1,234 +1,277 @@
--- ---
title: Policy CSP - EventLogService title: EventLogService Policy CSP
description: Learn how to use the Policy CSP - EventLogService setting to control Event Log behavior when the log file reaches its maximum size. description: Learn more about the EventLogService Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.topic: article ms.date: 12/29/2022
ms.localizationpriority: medium
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.localizationpriority: medium
ms.date: 09/27/2019
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- EventLogService-Begin -->
# Policy CSP - EventLogService # Policy CSP - EventLogService
<hr/> > [!TIP]
> Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
>
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
>
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<!--Policies--> <!-- EventLogService-Editable-Begin -->
## EventLogService policies <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EventLogService-Editable-End -->
<dl> <!-- ControlEventLogBehavior-Begin -->
<dd> ## ControlEventLogBehavior
<a href="#eventlogservice-controleventlogbehavior">EventLogService/ControlEventLogBehavior</a>
</dd>
<dd>
<a href="#eventlogservice-specifymaximumfilesizeapplicationlog">EventLogService/SpecifyMaximumFileSizeApplicationLog</a>
</dd>
<dd>
<a href="#eventlogservice-specifymaximumfilesizesecuritylog">EventLogService/SpecifyMaximumFileSizeSecurityLog</a>
</dd>
<dd>
<a href="#eventlogservice-specifymaximumfilesizesystemlog">EventLogService/SpecifyMaximumFileSizeSystemLog</a>
</dd>
</dl>
<hr/> <!-- ControlEventLogBehavior-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- ControlEventLogBehavior-Applicability-End -->
<!--Policy--> <!-- ControlEventLogBehavior-OmaUri-Begin -->
<a href="" id="eventlogservice-controleventlogbehavior"></a>**EventLogService/ControlEventLogBehavior** ```Device
./Device/Vendor/MSFT/Policy/Config/EventLogService/ControlEventLogBehavior
```
<!-- ControlEventLogBehavior-OmaUri-End -->
<!--SupportedSKUs--> <!-- ControlEventLogBehavior-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting controls Event Log behavior when the log file reaches its maximum size.
|Edition|Windows 10|Windows 11| If you enable this policy setting and a log file reaches its maximum size, new events are not written to the log and are lost.
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> If you disable or do not configure this policy setting and a log file reaches its maximum size, new events overwrite old events.
<hr/>
<!--Scope--> Note: Old events may or may not be retained according to the "Backup log automatically when full" policy setting.
[Scope](./policy-configuration-service-provider.md#policy-scope): <!-- ControlEventLogBehavior-Description-End -->
> [!div class = "checklist"] <!-- ControlEventLogBehavior-Editable-Begin -->
> * Device <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ControlEventLogBehavior-Editable-End -->
<hr/> <!-- ControlEventLogBehavior-DFProperties-Begin -->
**Description framework properties**:
<!--/Scope--> | Property name | Property value |
<!--Description--> |:--|:--|
This policy setting controls Event Log behavior, when the log file reaches its maximum size. | Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- ControlEventLogBehavior-DFProperties-End -->
If you enable this policy setting and a log file reaches its maximum size, new events aren't written to the log and are lost. <!-- ControlEventLogBehavior-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
If you disable or don't configure this policy setting and a log file reaches its maximum size, new events overwrite old events. **ADMX mapping**:
> [!NOTE] | Name | Value |
> Old events may or may not be retained according to the "Backup log automatically when full" policy setting. |:--|:--|
| Name | Channel_Log_Retention |
| Friendly Name | Control Event Log behavior when the log file reaches its maximum size |
| Location | Computer Configuration |
| Path | Windows Components > Event Log Service > Application |
| Registry Key Name | Software\Policies\Microsoft\Windows\EventLog\Application |
| Registry Value Name | Retention |
| ADMX File Name | EventLog.admx |
<!-- ControlEventLogBehavior-AdmxBacked-End -->
<!--/Description--> <!-- ControlEventLogBehavior-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- ControlEventLogBehavior-Examples-End -->
<!--ADMXBacked--> <!-- ControlEventLogBehavior-End -->
ADMX Info:
- GP Friendly name: *Control Event Log behavior when the log file reaches its maximum size*
- GP name: *Channel_Log_Retention_1*
- GP path: *Windows Components/Event Log Service/Application*
- GP ADMX file name: *eventlog.admx*
<!--/ADMXBacked--> <!-- SpecifyMaximumFileSizeApplicationLog-Begin -->
<!--/Policy--> ## SpecifyMaximumFileSizeApplicationLog
<hr/> <!-- SpecifyMaximumFileSizeApplicationLog-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- SpecifyMaximumFileSizeApplicationLog-Applicability-End -->
<!--Policy--> <!-- SpecifyMaximumFileSizeApplicationLog-OmaUri-Begin -->
<a href="" id="eventlogservice-specifymaximumfilesizeapplicationlog"></a>**EventLogService/SpecifyMaximumFileSizeApplicationLog** ```Device
./Device/Vendor/MSFT/Policy/Config/EventLogService/SpecifyMaximumFileSizeApplicationLog
```
<!-- SpecifyMaximumFileSizeApplicationLog-OmaUri-End -->
<!--SupportedSKUs--> <!-- SpecifyMaximumFileSizeApplicationLog-Description-Begin -->
<!-- Description-Source-ADMX -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting specifies the maximum size of the log file in kilobytes. This policy setting specifies the maximum size of the log file in kilobytes.
If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2,147,483,647 kilobytes) in kilobyte increments. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes), in kilobyte increments.
If you disable or don't configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 20 megabytes. If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 1 megabyte.
<!-- SpecifyMaximumFileSizeApplicationLog-Description-End -->
<!--/Description--> <!-- SpecifyMaximumFileSizeApplicationLog-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- SpecifyMaximumFileSizeApplicationLog-Editable-End -->
<!--ADMXBacked--> <!-- SpecifyMaximumFileSizeApplicationLog-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Specify the maximum log file size (KB)*
- GP name: *Channel_LogMaxSize_1*
- GP path: *Windows Components/Event Log Service/Application*
- GP ADMX file name: *eventlog.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- SpecifyMaximumFileSizeApplicationLog-DFProperties-End -->
<hr/> <!-- SpecifyMaximumFileSizeApplicationLog-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="eventlogservice-specifymaximumfilesizesecuritylog"></a>**EventLogService/SpecifyMaximumFileSizeSecurityLog**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | Channel_LogMaxSize |
| Friendly Name | Specify the maximum log file size (KB) |
| Location | Computer Configuration |
| Path | Windows Components > Event Log Service > Application |
| Registry Key Name | Software\Policies\Microsoft\Windows\EventLog\Application |
| ADMX File Name | EventLog.admx |
<!-- SpecifyMaximumFileSizeApplicationLog-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- SpecifyMaximumFileSizeApplicationLog-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- SpecifyMaximumFileSizeApplicationLog-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- SpecifyMaximumFileSizeApplicationLog-End -->
<hr/>
<!--Scope--> <!-- SpecifyMaximumFileSizeSecurityLog-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## SpecifyMaximumFileSizeSecurityLog
> [!div class = "checklist"] <!-- SpecifyMaximumFileSizeSecurityLog-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- SpecifyMaximumFileSizeSecurityLog-Applicability-End -->
<hr/> <!-- SpecifyMaximumFileSizeSecurityLog-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/EventLogService/SpecifyMaximumFileSizeSecurityLog
```
<!-- SpecifyMaximumFileSizeSecurityLog-OmaUri-End -->
<!--/Scope--> <!-- SpecifyMaximumFileSizeSecurityLog-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting specifies the maximum size of the log file in kilobytes. This policy setting specifies the maximum size of the log file in kilobytes.
If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2,147,483,647 kilobytes) in kilobyte increments. If you enable this policy setting, you can configure the maximum log file size to be between 20 megabytes (20480 kilobytes) and 2 terabytes (2147483647 kilobytes), in kilobyte increments.
If you disable or don't configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 20 megabytes. If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 20 megabytes.
<!-- SpecifyMaximumFileSizeSecurityLog-Description-End -->
<!--/Description--> <!-- SpecifyMaximumFileSizeSecurityLog-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- SpecifyMaximumFileSizeSecurityLog-Editable-End -->
<!--ADMXBacked--> <!-- SpecifyMaximumFileSizeSecurityLog-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Specify the maximum log file size (KB)*
- GP name: *Channel_LogMaxSize_2*
- GP path: *Windows Components/Event Log Service/Security*
- GP ADMX file name: *eventlog.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- SpecifyMaximumFileSizeSecurityLog-DFProperties-End -->
<hr/> <!-- SpecifyMaximumFileSizeSecurityLog-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="eventlogservice-specifymaximumfilesizesystemlog"></a>**EventLogService/SpecifyMaximumFileSizeSystemLog**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | Channel_LogMaxSize |
| Friendly Name | Specify the maximum log file size (KB) |
| Location | Computer Configuration |
| Path | Windows Components > Event Log Service > Security |
| Registry Key Name | Software\Policies\Microsoft\Windows\EventLog\Security |
| ADMX File Name | EventLog.admx |
<!-- SpecifyMaximumFileSizeSecurityLog-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- SpecifyMaximumFileSizeSecurityLog-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- SpecifyMaximumFileSizeSecurityLog-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- SpecifyMaximumFileSizeSecurityLog-End -->
<hr/>
<!--Scope--> <!-- SpecifyMaximumFileSizeSystemLog-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## SpecifyMaximumFileSizeSystemLog
> [!div class = "checklist"] <!-- SpecifyMaximumFileSizeSystemLog-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
<!-- SpecifyMaximumFileSizeSystemLog-Applicability-End -->
<hr/> <!-- SpecifyMaximumFileSizeSystemLog-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/EventLogService/SpecifyMaximumFileSizeSystemLog
```
<!-- SpecifyMaximumFileSizeSystemLog-OmaUri-End -->
<!--/Scope--> <!-- SpecifyMaximumFileSizeSystemLog-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting specifies the maximum size of the log file in kilobytes. This policy setting specifies the maximum size of the log file in kilobytes.
If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2,147,483,647 kilobytes) in kilobyte increments. If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes), in kilobyte increments.
If you disable or don't configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 20 megabytes. If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 1 megabyte.
<!-- SpecifyMaximumFileSizeSystemLog-Description-End -->
<!--/Description--> <!-- SpecifyMaximumFileSizeSystemLog-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- SpecifyMaximumFileSizeSystemLog-Editable-End -->
<!--ADMXBacked--> <!-- SpecifyMaximumFileSizeSystemLog-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Specify the maximum log file size (KB)*
- GP name: *Channel_LogMaxSize_4*
- GP path: *Windows Components/Event Log Service/System*
- GP ADMX file name: *eventlog.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
<hr/> | Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- SpecifyMaximumFileSizeSystemLog-DFProperties-End -->
<!-- SpecifyMaximumFileSizeSystemLog-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--/Policies--> **ADMX mapping**:
## Related topics | Name | Value |
|:--|:--|
| Name | Channel_LogMaxSize |
| Friendly Name | Specify the maximum log file size (KB) |
| Location | Computer Configuration |
| Path | Windows Components > Event Log Service > System |
| Registry Key Name | Software\Policies\Microsoft\Windows\EventLog\System |
| ADMX File Name | EventLog.admx |
<!-- SpecifyMaximumFileSizeSystemLog-AdmxBacked-End -->
<!-- SpecifyMaximumFileSizeSystemLog-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- SpecifyMaximumFileSizeSystemLog-Examples-End -->
<!-- SpecifyMaximumFileSizeSystemLog-End -->
<!-- EventLogService-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- EventLogService-CspMoreInfo-End -->
<!-- EventLogService-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md) [Policy configuration service provider](policy-configuration-service-provider.md)

2760
windows/client-management/mdm/policy-csp-experience.md
View File

File diff suppressed because it is too large Load Diff