Windows 7 / Getting Started

Configuring WER Using Group Policy

Administrators can use Group Policy to configure WER in AD DS environments. Table below describes the policy settings you can use for configuring WER on targeted computers running Windows Vista and later. WER policy settings can be found in two locations:

Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Error Reporting

User Configuration\Policies\Administrative Templates\Windows Components\Windows Error Reporting

Note that all policy settings listed in this table are available as both per-computer and peruser policies except for the Configure Corporate Windows Error Reporting policy setting, which is available only as a per-computer policy.

Group Policy Settings for Configuring WER

Policy SettingDescription
Located under \Windows Error Reporting
Disable Windows Error ReportingIf this setting is enabled, WER will not send any problem information to Microsoft. Additionally, solution information will not be available in the Action Center Control Panel.
Prevent Display Of The User Interface For Critical ErrorsThis policy setting prevents the display of the user interface for critical errors. If you enable this policy setting, WER prevents the display of the user interface for critical errors. If you disable or do not configure this policy setting, WER displays the user interface for critical errors.
Disable LoggingIf this setting is enabled WER events will not be logged to the system event log.
Do Not Send Additional DataIf this setting is enabled any additional data requests from Microsoft in response to a WER event will be automatically declined without notice to the user.
Located under \Windows Error Reporting\Advanced Error Reporting Settings
Configure Report ArchiveThis setting controls the behavior of the WER archive. If Archive behavior is set to Store All, all data collected for each report will be stored in the appropriate location. If Archive behavior is set to Store Parameters Only, only the minimum information required to check for an existing solution will be stored. The setting for Maximum Number Of Reports To Store determines how many reports can be stored before old reports are automatically deleted. If this setting is disabled, no WER information will be stored.
Configure Corporate Windows Error ReportingThis setting determines the corporate server to which WER will send reports (instead of sending reports to Microsoft). Server port indicates the port to use on the target server. Connect using Secure Sockets Layer (SSL) determines whether Windows will send reports to the server using a secured connection.
List Of Applications To Be ExcludedThis setting determines the behavior of the error reporting exclusion list. Windows will not send reports for any process added to this list. Click Show to display the exclusion list. In the Show Contents dialog box in the Value column, type a process name to add a process to the list. To remove a process from the list, click the process name to be removed and press the Delete key. Click OK to save the list.
Configure Report QueueThis setting determines the behavior of the WER queue. If Queuing behavior is set to Default, Windows will decide each time a problem occurs whether the report should be queued or the user should be prompted to send it immediately. If Queuing behavior is set to Always Queue, all reports will be queued until the user is notified to send them or until the user chooses to send them using the Solutions to Problems Control Panel. If Queuing behavior is set to Always Queue For Administrator, reports will be queued until an administrator is notified to send them or chooses to send them using the Solutions to Problems Control Panel. The setting for Maximum Number Of Reports To Queue determines how many reports can be queued before old reports are automatically deleted. The setting for Number Of Days Between Solution Check Reminders determines the interval time between the display of system notifications which remind the user to check for solutions to problems. A setting of 0 will disable the reminder. If the WER queue setting is disabled, no WER information will be queued and users will be able to send reports only at the time a problem occurs.
Located under \Windows Error Reporting/Consent
Customize Consent SettingsThis policy setting determines the consent behavior of WER for specific event types. If this policy setting is enabled and the consent level is set to 0 (Disable), WER will not send any data to Microsoft for this event. If the consent level is set to 1 (Always Ask Before Sending Data), Windows will prompt the user for consent to send reports. If the consent level is set to 2 (Send Parameters), the minimum data required to check for an existing solution will be sent automatically, and Windows will prompt the user for consent to send any additional data requested by Microsoft. If the consent level is set to 3 (Send Parameters And Safe Additional Data), the minimum data required to check for an existing solution as well as data that Windows has determined does not contain (within a high probability) personally identifiable data will be sent automatically, and Windows will prompt the user for consent to send any additional data requested by Microsoft. If the consent level is set to 4 (Send All Data), any data requested by Microsoft will be sent automatically. If this setting is disabled or not configured then consent will default to the default consent setting.
Ignore Custom Consent SettingsThis setting determines the behavior of the default consent setting in relation to custom consent settings. If this setting is enabled, the default Consent level setting will always override any other consent setting. If this setting is disabled or not configured, each custom consent setting will determine the consent level for that event type and the default consent setting will determine the consent level of any other reports.
Advanced Error Reporting Settings\Configure Default ConsentThis setting determines the consent behavior of WER. If the consent level is set to Always Ask Before Sending Data, Windows will prompt the user for consent to send reports. If the consent level is set to Send Parameters, the minimum data required to check for an existing solution will be sent automatically, and Windows will prompt the user for consent to send any additional data requested by Microsoft. If the consent level is set to "Send parameters and safe additional data", the minimum data required to check for an existing solution as well as data which Windows has determined does not contain (within a high probability) personally identifiable data will be sent automatically, and Windows will prompt the user for consent to send any additional data requested by Microsoft. If the consent level is set to Send All Data, any data requested by Microsoft will be sent automatically. If this setting is disabled or not configured, then the consent level will default to Always Ask Before Sending Data.
[Previous] [Contents] [Next]

In this tutorial:

  1. Windows 7 Desktop Maintenance
  2. Performance Monitoring
  3. Improvements to Performance Monitoring in Windows 7
  4. Using Performance Monitor
  5. Real-Time Performance Monitoring
  6. Performance Monitor Logging
  7. Creating a Data Collector Set
  8. Configuring a Data Collector Set
  9. Using Data Manager to View Performance Data
  10. Starting and Stopping Data Logging
  11. Viewing Performance Data
  12. Comparing Performance Monitor Logs
  13. Performance Monitor User Rights
  14. Remote Data Collection
  15. Using Windows PowerShell for Performance Monitoring
  16. Resource Monitor
  17. Overview Tab
  18. CPU Tab
  19. Memory Tab
  20. Disk Tab
  21. Network Tab
  22. Reliability Monitor
  23. How Reliability Monitor Works
  24. Windows Performance Tools Kit
  25. Event Monitoring
  26. Understanding the Windows Event Architecture
  27. Channels
  28. Improvements to Event Monitoring in Windows 7
  29. Using Event Viewer
  30. Understanding Views
  31. Viewing Event Logs
  32. Saving Event Logs
  33. Configuring Event Subscriptions
  34. Considerations for Workgroup Environments
  35. Creating a New Subscription
  36. Using the Windows Events Command-Line Utility for Event Monitoring
  37. Using Windows PowerShell for Event Monitoring
  38. Using Task Scheduler
  39. Improvements to Task Scheduler in Windows 7
  40. Understanding Tasks
  41. Understanding the Task Scheduler Architecture
  42. Understanding Task Scheduler Security
  43. Credentials Management
  44. Securing Running Tasks
  45. Understanding AT and Task Scheduler v1.0 Compatibility Modes
  46. Understanding the Task Scheduler Snap-in
  47. Understanding Default Tasks
  48. Creating Tasks
  49. Defining Triggers
  50. At Startup Trigger
  51. On Connection To AND Disconnect From User Session Triggers
  52. On Workstation Lock AND Unlock Triggers
  53. Defining Actions
  54. Defining Conditions
  55. Defining Settings
  56. Managing Tasks
  57. Viewing History
  58. Using SchTasks.exe for Creating and Managing Tasks
  59. Task Scheduler Events
  60. Troubleshooting Task Scheduler
  61. Tasks Won't Run If the Service Is Not Started
  62. The Task Will Run Only When a Certain User Is Logged On
  63. The Task Action Failed to Execute
  64. Interpreting Result and Return Codes
  65. Understanding the Windows System Assessment Tool
  66. Understanding WinSAT Assessment Tests
  67. Examining the WinSAT Features Assessment
  68. Running WinSAT from the Command Line
  69. Understanding WinSAT Command Exit Values
  70. Running WinSAT Using Performance Information and Tools
  71. System Capabilities Section
  72. OEM Upsell And Help Section
  73. Understanding Windows Error Reporting
  74. Overview of Windows Error Reporting
  75. How WER Works
  76. Store Management System
  77. ReportArchive Folder
  78. WER Service
  79. Understanding the Error Reporting Cycle
  80. Understanding WER Data
  81. Configuring WER Using Group Policy
  82. Configuring WER Using the Action Center