Overview

The target machine was offline and missed the agent scanning schedule window. When such a computer comes online the agent scan will not start automatically.

This article answers the question of whether it is possible to configure agent scans to run immediately once the agent computer is connected to the internal network and provides recommendations on how to address this issue.

Solution

If the client machine was offline or was not able to communicate with the LanGuard server at the time of the scheduled agent scan, the scan won't happen. The agent scan would not start once the computer connects to the network but will trigger again during the next scheduled time.

Refer to our recommendations below on how to adjust the configuration depending on your environment and use case.

1. If the machine is usually offline at the scheduled time, it is recommended to Change the Agent Scan Schedule to normal working hours based on the availability pattern. The schedule can be changed for a group of agents as well.

   It may be necessary to split the scan schedules up further or add additional attributes and define the most likely times when the machines will be online in order to achieve the best results.

2. Alternatively, If the machine is physically connected to the network and is sleeping or powered off, you can use console-based scanning instead that will wake up the target machine(s):

   1. Create a Scheduled Console Scan and enable Wake up offline computers for this job.
      
   2. Configure Wake-On-Lan of Scan Targets.
   3. (optional) DIsable Agent scans for target computers.

Related Articles

• GFI LanGuard Not Scanning All Target Machines in the Network Range