Creates a new event log and a new event source on a local or remote computer.
Syntax
 Copy Code |
|
|---|---|
New-EventLog [-LogName] <string> [-Source] <string[]> [[-ComputerName] <string[]>] [-CategoryResourceFile <string>] [-MessageResourceFile <string>] [-ParameterResourceFile <string>] [<CommonParameters>] |
|
Description
This cmdlet creates a new classic event log on a local or remote computer. It can also register an event source that writes to the new log or to an existing log.
The cmdlets that contain the EventLog noun (the Event log 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 Windows, use Get-WinEvent.
Parameters
-CategoryResourceFile <string>
Specifies the path to the file that contains category strings for the source events. This file is also known as the Category Message File.
The file must be present on the computer on which the event log is being created. This parameter does not create or move files.
|
Required? |
false |
|
Position? |
named |
|
Default Value |
none |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
-ComputerName <string[]>
Creates the new event logs on the specified computers. The default is the local computer.
Type the NetBIOS name, an Internet Protocol (IP) address, or a fully qualified domain name of a remote computer. To specify the local computer, type the computer name, a dot (.), or "localhost".
This parameter does not rely on Windows PowerShell remoting. You can use the ComputerName parameter of Get-EventLog even if your computer is not configured to run remote commands.
|
Required? |
false |
|
Position? |
3 |
|
Default Value |
. |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
-LogName <string>
Specifies the name of the event log.
If the log does not exist, New-EventLog creates the log and uses this value for the Log and LogDisplayName properties of the new event log. If the log exists, New-EventLog registers a new source for the event log.
|
Required? |
true |
|
Position? |
1 |
|
Default Value |
none |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
-MessageResourceFile <string>
Specifies the path to the file that contains message formatting strings for the source events. This file is also known as the Event Message File.
The file must be present on the computer on which the event log is being created. This parameter does not create or move files.
|
Required? |
false |
|
Position? |
named |
|
Default Value |
none |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
-ParameterResourceFile <string>
Specifies the path to the file that contains strings used for parameter substitutions in event descriptions. This file is also known as the Parameter Message File.
The file must be present on the computer on which the event log is being created. This parameter does not create or move files.
|
Required? |
false |
|
Position? |
named |
|
Default Value |
none |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
-Source <string[]>
Specifies the names of the event log sources, such as application programs that write to the event log. This parameter is required.
|
Required? |
true |
|
Position? |
2 |
|
Default Value |
none |
|
Accept Pipeline Input? |
false |
|
Accept Wildcard Characters? |
false |
<CommonParameters>
This command supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, OutBuffer, OutVariable, WarningAction, and WarningVariable. For more information, see about_CommonParameters.
Inputs and Outputs
The input type is the type of the objects that you can pipe to the cmdlet. The return type is the type of the objects that the cmdlet returns.
|
Inputs |
None You cannot pipe input to this cmdlet. |
|
Outputs |
System.Diagnostics.EventLogEntry |
Notes
To use New-EventLog on Windows Vista and later versions of Windows, open Windows PowerShell with the "Run as administrator" option.
To create an event source in Windows Vista, Windows XP Professional, or Windows Server 2003, you must be a member of the Administrators group on the computer.
When you create a new event log and a new event source, the system registers the new source for the new log, but the log is not created until the first entry is written to it.
The operating system stores event logs as files. When you create a new event log, the associated file is stored in the %SystemRoot%\System32\Config directory on the specified computer. The file name is the first eight characters of the Log property with an .evt file name extension.
Example 1
| Copy Code |
|
|---|---|
C:\PS>new-eventlog -source TestApp -logname TestLog -MessageResourceFile C:\Test\TestApp.dll |
|
Description
-----------
This command creates the TestLog event log on the local computer and registers a new source for it.
Example 2
| Copy Code |
|
|---|---|
C:\PS>$file = "C:\Program Files\TestApps\NewTestApp.dll" C:\PS> new-eventlog -computername Server01 -source NewTestApp -logname Application -MessageResourceFile $file -CategoryResourceFile $file |
|
Description
-----------
This command adds a new event source, NewTestApp, to the Application log on the Server01 remote computer.
The command requires that the NewTestApp.dll file is located on the Server01 computer.