Windows 7 / Getting Started

Using the Windows Events Command-Line Utility for Event Monitoring

The Windows Events Command-Line Utility (Wevtutil.exe) lets you manage event logs on a computer from the command line by performing tasks such as:

  • Retrieving information about event logs and publishers.
  • Installing and uninstalling event manifests.
  • Executing queries for specific event.
  • Exporting, archiving, and clearing event logs.

Wevtutil should be run from an elevated command prompt. The general syntax for Wevtutil is as follows.

wevtutil command [argument [argument] ...] [/option:value [/option:value] ...]

Here, command can be any of the following:

  • al (archive-log) Archives an exported log
  • cl (clear-log) Clears a log
  • el (enum-logs) Lists log names
  • ep (enum-publishers) Lists event publishers
  • epl (export-log) Exports a log
  • gl (get-log) Gets log configuration information
  • gli (get-log-info) Gets log status information
  • gp (get-publisher) Gets publisher configuration information
  • im (install-manifest) Installs event publishers and logs from manifest
  • qe (query-events) Queries events from a log or log file
  • sl (set-log) Modifies configuration of a log
  • um (uninstall-manifest) Uninstalls event publishers and logs from manifest

Common examples for option include:

  • /r:value (remote) If specified, runs the command on a remote computer named value. Note that im (install-manifest) and um (uninstall-manifest) do not support remote operation.
  • /u:value (username) Specifies a different user to log on to a remote computer. Here value is a user name in the form domain\user or user. This option is applicable only when option /r (remote) is specified.
  • /p:value (password) Specifies a password for the specified user. If not specified, or if the value is "*", the user will be prompted to enter a password. This option is applicable only when the /u (user name) option is specified.
  • /a:value (authentication) Specifies an authentication type for connecting to a remote computer. The value can be Default, Negotiate, Kerberos, or NTLM. The default is Negotiate.
  • /uni:value (unicode) Displays output in Unicode. The value can be true or false (if true, output is in Unicode).

Note You can use either the short (ep /uni) or long (enum-publishers /unicode) version of the command and option names; and all commands, options, and option values are case-insensitive.

More Info To learn more about a specific command, type wevtutil command /? at an elevated command prompt. For additional information concerning Wevtutil.exe, see http://technet.microsoft.com/en-us/library/cc732848.aspx.

[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