Using a Stored Event Handler Record in Windows
| Anchor |
|---|
| 104075110407611040751 |
|---|
| 1040761 |
|---|
|
In this example, a demand-driven UEM Server will watch for the creation of a file called
uemtest.dat in the
C:\UEM Files directory.
| Anchor |
|---|
| 104075210407621040752 |
|---|
| 1040762 |
|---|
|
If the file completes before the inactive time of
20:00 elapses, the event occurrence will be set to the
triggered state, and UEM will execute the command or script contained in the event handler
h001, which is the ID of a record in the event handler database.
| Anchor |
|---|
| 104075310407631040753 |
|---|
| 1040763 |
|---|
|
If the file does not complete before the inactive time elapses, the event occurrence will be set to a rejected state. Since no event handler information is provided for a rejected occurrence, no further action will be taken by the UEM Server.
| Anchor |
|---|
| 104075410407641040754 |
|---|
| 1040764 |
|---|
|
If the UEM Server does not detect the presence of
C:\UEM Files\uemtest.dat before the inactive time of
20:00 elapses, the event will be set to an
expired state.
...
The command line options used in this example are:
Option | Description |
|---|
-host | List of one or more hosts upon which a command may run. |
-event_type | Type of event to monitor. |
-filespec | Name or pattern of the file whose creation should be detected and tracked for completion. |
-inact_date_time | Date and time at which the state of the monitored event should be made inactive. |
-userid | ID of a remote user account that the UEM Server uses to establish the security context in which event monitoring is performed. |
-pwd | Password associated with -userid. |
-triggered | Event state that, when encountered, will result in the execution of the associated event handler. |
-handler_id | ID of a stored event handler record. |
Components
Universal Event Monitor Manager for Windows
