A: You did not define at least one IP addressfor a discovery scan.
A: If you set up the scan to run during scan windows, but you have not defined
Scan Windows for the group you are scanning. This could happen if you define a
Scan Window policy for the group, but you have not defined any Scan Windows in
the policy. The default for an unmodified Scan Windowpolicy is that scan
windows are open at all times. If you open and save the Scan Window policy for
any other reason; however, the windows change to closed. You must define scan
windows for both discovery and assessment scans if you modify the Scan Window
policy.
Q: Why does it take so long for an ad hoc scan to start?
A: An ad hoc scan might not start right away if both of these conditions are true:
vYou initiate the scan during a closed scan window.
vYou configure the scan to run only during scan windows.
Q: Why did my ad hoc scan continue to run even when the refresh cycle started
again?
A: Refresh cycles do not apply to ad hoc scans, therefore ad hoc scans continue to
run even if a new refresh cycle starts.
Q: When I rerun an ad hoc discovery scan, why does the assessment scan for the
group sometimes run again, but not always?
A: The answer depends on how you set up your Scan Control policy:
If you set up the Scan Control policy so
that the assessment scan... Then, the assessment scan...
Waits for the discovery scan to finish before
the assessment scan begins
Also runs again when you rerun the
discovery scan.
Does not wait for the discovery scan to
finish before the assessment scan begins
Does not run again when you rerun the
discovery scan.
Expected scanning behaviors for background scans
This section answers question you might have about what to expect from
background scans in different circumstances.
Expect the following with background scans:
Q: I changed a Scan Control policy when there were additional scan windows
available in the refresh cycle, but the scans did not start until the new refresh
cycle.
A: Scans will run only once during a refresh cycle. If you change the Scan Control
policy after the scans have run for that cycle, the changes do not go into effect
until the beginning of the next refresh cycle.
Q: When is a background scan scheduled in the Command Jobs window?
A: Background scans are displayed in the Command Jobs window in the following
ways:
100 Enterprise Scanner: User Guide