Remote Configuration Tool

You can use the Remote Configuration Tool to modify the SNMP trap event configuration on clients remotely, using a package. When using the Remote Event Configuration Tool (Eventcmt.exe), you specify a data file to update event configuration on clients. With the Event to Trap Translator window, you can configure events for one client and then click Export to export the configuration to a text file. You can then use this text file with the tool to configure many clients with the same configuration.

After you run the Remote Event Configuration Tool, it generates a status MIF file in the Windows NT Temp directory of the client computer to indicate the success or failure of the operation. The tool also generates a log file (Eventcmt.log) with more detailed information, which it places in the SMS client logs directory.

There are two versions of Eventcmt: One for the Intel (x86) platform, the other for the Alpha platform. Both platforms are located in the following directory:

SMS\Scripts\00000409\Eventcmt\.

Note If you are connecting to the SMS directory from another computer on the network, the location of this tool appears as SMS_sitecode\Scripts\00000409\Eventcmt\.

Command-Line Options

The Remote Event Configuration Tool (Eventcmt.exe) uses the following syntax:

eventcmt <config-file><options>

where

config-file is the name and path of the file that contains the event configuration to run on the client. If you use the Event to Trap Translator to create this file, it will have a .cnf filename extension. If you create this file yourself, you can specify a different filename extension; however, when the file is exported, the extension will be changed to .cnf.

Configuration files are text files that can contain comments (preceded by a semicolon) and configuration statements. Configuration statements use the following syntax:

#pragma [ADD|DELETE] EventLog "EventSource" EventID count time

#pragma [ADD_TRAP_DEST|DELETE_TRAP_DEST] community address

where

ADD or DELETE; On the client, adds or deletes the specified event configuration to or from the list of events to be translated into SNMP traps. If the specified EventID is already configured on the client when you run the ADD command, the configured count and time values are modified to use the count and time values specified in the command.
EventLog: A text string that specifies the Windows NT event log (Application, Security, or System) of the event.
"EventSource": A text string, enclosed in quotation marks, that specifies the source of an event. A source is the software (an application, a component of an application, or a component of the operating system) that logged the event.
EventID: A number (unique in each event source) that identifies the event.
count: The number of times the event must occur before an SNMP trap is generated. By default, the minimum count value is 1.
time: The length of time in which count number of events must occur to generate an SNMP trap. The first occurrence of an event starts the timer. When this option is selected, count is automatically set to 2 (unless you have specified a higher number).

ADD_TRAP_DEST or DELETE_TRAP_DEST

Adds or deletes the specified address to or from the list of trap destinations for the specified community. For ADD_TRAP_DEST, the specified community is created if it does not already exist, and the address is added to it.
community name: The SNMP security context that will be used when sending traps to particular IP addresses.
address: The IP addresses of the computers to which SNMP traps with the specified community name are sent.

Note This tool will automatically stop and start the SNMP Service if you use the ADD_TRAP_DEST or DELETE_TRAP_DEST options. However, if you use the /Nostopstart option, the SNMP Service will not be interrupted.

Related Topics

About SNMP Traps

Event to Trap Translator Overview

Translating SNMP Traps Overview