The following appendices identify hosts that were successfully scanned and hosts that were not scanned.
This appendix displays a list of hosts that were successfully scanned.
Successfully Scanned Hosts. Hosts were scanned and results are included in your report.
This appendix displays a list of hosts that were not scanned for various reasons.
Scan paused by [user | administrator | the service]. Hosts were not scanned because the scan task was paused. Scans may be paused by a user on the scan history list, by an administrator or automatically by the service as specified in scheduled scan settings. To launch a new scan on these remaining hosts, resume the paused scan from the scan history list.
Scan canceled by [user | administrator | the service]. Hosts were not scanned because the scan task was canceled. Scans may be canceled by a user on the scan history list, by an administrator or automatically by the service as specified in scheduled scan settings.
Excluded Hosts. Hosts were not scanned because they were excluded. Hosts may be excluded on a per scan basis (by the user launching or scheduling the scan) or globally for all scans. Managers and Unit Managers have privileges to edit the global excluded hosts list for the subscription.
Hosts Not Alive. Hosts were not scanned because they were not "alive" at the time of the scan, meaning that they did not respond to probes sent by the scanning engine, and the option to Scan Dead Hosts was not enabled.
Hostname Not Found. Hosts were scanned but could not be reported because the NetBIOS or DNS hostname, whichever tracking method is specified for each host, could not be resolved.
Scan Discontinued. Hosts were not scanned because the scan task was abruptly discontinued. This is a rare occurrence that may be caused for various reasons. If your scan results include hosts in this appendix, contact Support for assistance. To send an email, go to Help > Contact Support. For phone support, see the phone numbers provided on the same page.
Host Technology Not In Policy (CPE mismatch). This section may appear only for an FDCC scan. Live hosts were not scanned for FDCC compliance because the hosts were found to have a different technology than the technology defined in the FDCC policy. An FDCC policy is defined for only one technology.