Monitoring local events
Events can be monitored locally and centrally once the data is uploaded to the CM database, and they can be monitored individually for single device or for all the members of the group. This section provides information on monitoring local events.
After the status for the device group members displays
Executed, the rule is received on the target and the specified peripheral device control is activated. You can now monitor what is happening concerning device management locally on each of the devices of your group. For this some device management activities need to be carried out on one of the devices, that is, the master.
Once some power management activities are carried out on one of the devices you can monitor these as follows locally:
Open the node Device Topology> Master> Agent Configuration> Module Configuration> Windows Device Management.
This node displays in its first tab the configuration parameter concerning the event logging which was activated via the first operational rule.
Select the next tab, Rule List .
Here you can see the list of all steps of the device rules that are assigned to the currently selected device. In our example there is only one rule yet, consisting of two steps. The first step, the rule reset step, will never appear in this list.
Now select the tab Events.
As we have activated event logging, every time a USB storage is connected to the device an event is logged in this table.
- Connect the USB storage device to the master that was admitted in the second step. Execute some operations on it, copying, creating, deleting, and so on.
Now connect another USB storage device to the master.
The master will recognise the new hardware, it displays in the Windows Device Manager window but not in the Windows Explorer, because it is unusable. Depending on the operating systems of the master, an error message might appear in the SysTray that an error occurred with the newly found device.
- In addition an event is logged by the "/> agent and displayed in the tab.
For information about monitoring events centrally, see Monitoring the results on the master.