Show-EventLog
Displays the event logs of the local or a remote computer in Event Viewer.
Syntax
Show-EventLog
[[-ComputerName] <String>]
[<CommonParameters>]
Description
The Show-EventLog
cmdlet opens Event Viewer on the local computer and displays in it all of the
classic event logs on the local computer or a remote computer.
To open Event Viewer on Windows Vista and later versions of the Windows operating system, the current user must be a member of the Administrators group on the local computer.
The cmdlets that contain the EventLog noun (the EventLog cmdlets) work only on classic event
logs. To get events from logs that use the Windows Event Log technology in Windows Vista and later
versions of the Windows operating system, use the Get-WinEvent
cmdlet.
Examples
Example 1: Display event logs for the local computer
Show-EventLog
This command opens Event Viewer and displays in it the classic event logs on the local computer.
Example 2: Display event logs for a remote computer
Show-EventLog -ComputerName "Server01"
This command opens Event Viewer and displays in it the classic event logs on the Server01 computer.
Parameters
-ComputerName
Specifies a remote computer. Show-EventLog
displays the event logs from the specified computer in
Event Viewer on the local computer. The default is the local computer.
Type the NetBIOS name, an IP address, or a fully qualified domain name of a remote computer.
This parameter does not rely on Windows PowerShell remoting. You can use the ComputerName parameter even if your computer is not configured to run remote commands.
Type: | String |
Aliases: | CN |
Position: | 0 |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Inputs
None
You cannot pipe input to this cmdlet.
Outputs
None
This cmdlet does not generate any output.
Notes
The Windows PowerShell command prompt returns as soon as Event Viewer opens. You can work in the current session while Event Viewer is open.
Because this cmdlet requires a user interface, it does not work on Server Core installations of Windows Server.