8.4.5 Monitor Windows event (execution condition item)
- Organization of this subsection
(1) Overview of function
This item executes a job upon the occurrence of a Windows event.
(2) List of settings
|
Name |
Required |
Format |
Can specify inherited information? |
|---|---|---|---|
|
Monitor event |
Yes |
Combo box (Log on, Log off, Screen lock, or Screen lock release) |
No |
|
Windows User Name |
No |
String (0 to 276 bytes) You can use alphanumeric characters and the following symbols: _ - \ . |
No |
(3) Settings
- Monitor event
-
Specify the types of Windows events to be monitored.
You can select from the following options: Log on, Log off, Screen lock, and Screen lock release.
After the detection of an event, event monitoring immediately resumes without any intervals between monitoring jobs.
- Windows User Name
-
Specify the Window user name to be monitored. If you do not specify this setting, all events are detected, regardless of who is triggering those events.
If a user belonging to a domain is to be monitored, specify NetBIOS-domain-name\user-name. If you omit the NetBIOS domain name, the item assumes that the local host name is set as the domain name.
If a Windows event is triggered by a user other than the specified user, monitoring continues without the event being detected.
The monitor does not distinguish between upper and lower case letters in the specified Windows user names.
(4) Example 1
Run the job when a user logs on to Windows.
|
Monitor event |
Log on |
|
Windows User Name |
-- |
- Legend:
-
-- : Not specified
(5) Example 2
Run the job when the designated user (UserA) unlocks the Windows screen.
|
Monitor event |
Screen lock release |
|
Windows User Name |
UserA |
(6) Notes
You can only use this item while the COM+ Event System service, the COM+ System Application service, and System Event Notification Service service are up and running. For details, see 2.3.5 Using the Windows event monitor function.
Note that, if you stop the above services while this item is being executed, events can no longer be detected, although event monitoring continues. In this state, events cannot be detected even when the services are restarted. You have to re-execute the item.