Monitoring Algorithm
The algorithm used in the monitoring process is simple but effective:
1. First of all DeviceLock Enterprise Server tries to scan the monitored computer to determine whether or not it is working. If the scan succeeds then the computer receives the available status and computer monitoring continues. Otherwise, it receives the unavailable status and computer monitoring stops (the record is written to the monitoring log).
2. Then DeviceLock Enterprise Server tries to connect to DeviceLock Service. If the connection succeeds then DeviceLock Service receives the available status and computer monitoring continues. Otherwise, it receives the unavailable status and computer monitoring stops (the record is written to the monitoring log).
3. If this task should verify DeviceLock Service policy integrity then computer monitoring continues. Otherwise, computer monitoring stops (nothing logged).
4. DeviceLock Enterprise Server downloads the policy from DeviceLock Service and compares it with the master policy assigned to this task. If no difference is found computer monitoring stops (nothing logged). If there is a difference between the two policies then computer monitoring continues (the record is written to the monitoring log).
5. If this task should restore the broken policy, then DeviceLock Enterprise Server writes the master policy to DeviceLock Service and computer monitoring stops (the record is written to the monitoring log). Otherwise, computer monitoring just stops (nothing logged).
If some error occurs at any step described above, then the record about that will be written to the monitoring log. If this error is not critical, computer monitoring may continue. If it is a critical error then computer monitoring stops. Also, some very critical errors (such as “no memory”) can halt execution of the whole task.