Documentation Version: er2.0.28-docs-1.1

Start a Scan

This section assumes that you have set up and configured Targets to scan. See Targets Overview.

Start a scan from the following places in the Web Console:

To start a scan

  1. In DASHBOARD, TARGETS, or SCHEDULE MANAGER, click Start Search.

  2. On the Select Locations page, select Targets to scan from the list of Targets and click Next.
    To add Targets not listed in Select Locations, see Add Targets.
    From ER 2.0.21, you can browse and select the contents of Targets listed in Select Locations to add as scan locations. For details, see Probe Targets.
  3. On the Select Data Types page, select the Data Types to be included in your scan and click Next. See Data Type Profiles.
  4. Set a scan schedule in the Set Schedule section. Click Next.
  5. Click Start Scan.

Your scan configuration is saved and you are directed to the TARGETS page. The Target(s) you have started scans for should display Searched x.x% in the Searched column to indicate that the scan is in progress.

If your scan does not start immediately, your Master Server and the Node Agent system clocks may not be in sync. A warning is displayed in the Agent Manager page. See Server Information and Manage Agents for more information.

Set Schedule

The Set Schedule page allows you to configure the following optional parameters for your scan: 

Schedule Label

Enter a label for your scan. ER2 automatically generates a default label for the scan. The label must be unique, and will be displayed in the SCHEDULE MANAGER. See View and Manage Scans.

Scan Frequency

Decide to Scan Now, or to Schedule a future scan.

To schedule a scan:

  1. Select Schedule.
  2. Select the start date and time for the scan.
  3. (Optional) Set the scan to repeat by selecting an option under How Often?.

When scheduling a future scan, you can set a Time Zone. The Time Zone should be set to the Target host's local time. Setting the Time Zone here will affect the time zone settings for this scheduled scan only.

The Master Server resides in Dublin, and Target A is a network storage volume with the physical host residing in Melbourne. A scan on Target A is set for 2:00pm. The Time Zone for the scan should be set to "Australia/Melbourne" for it to start at 2.00pm local time for Target A.

Selecting the "Default" Time Zone will set the scan schedule to use the Master Server local time.

Daylight Savings Time

When setting up a scan schedule, Time Zone settings take into account Daylight Savings Time (DST).

  1. On the start day of DST, scan schedules that fall within the skipped hour are moved to run one hour later.
    On the start day for DST, a scan that was scheduled to run at 2:00am will start at 3:00am instead.
  2. On the end day of DST, scan schedules that fall within the repeated hour will run only during one occurrence of the repeated hour.

Set Notifications

To set notifications for the scan:

  1. Select Notify.
  2. Click + Add Notification.
  3. In the New Notification dialog box:
    • Select Users to send alerts and emails to specific users.
    • Select Email Addresses to send email notifications to specific email addresses.
  4. Under Notification Options, select Alert or Email for the event to send notifications when the event is triggered. Only the Email options are available if Email Addresses is selected in step 3.
  5. Click Save.

See Notifications and Alerts for more information.

Notification policies created here are not added to the Notifications and Alerts page.

Advanced Options

Configure the following scan schedule parameters in Advanced Options:

Automatic Pause Scan Window

Set scan to pause during the scheduled periods:


Set a scan pause schedule for every Wednesday and Friday from 8:00 am to 12:00 pm:

If a Time Zone is set, it will apply to the Automatic Pause Scan Window. If no Time Zone is set, the Time Zone menu will appear under How Often?, allowing the user to set the time zone for the scan. See Scan Frequency above for more information.

Limit CPU Priority

Sets the CPU priority for the Node Agent used.

If a Proxy Agent is used, CPU priority will be set for the Proxy Agent on the Proxy Agent host.

The default is Low Priority to keep ER2's resource footprint low.

Limit Search Throughput

Sets the rate at which ER2 scans the Target:

Trace Messages

Logs scan trace messages for the scanned Targets, select Enable Scan Trace. See Scan Trace Logs.

Scan Trace Logs may take up a large amount of disk space, depending on the size and complexity of the scan, and may impact system performance. Enable this feature only when troubleshooting.

Capture Context Data

Select to include contextual data when displaying matches in the Match Inspector. See Remediation.

Contextual data is data found before and after a found match to help you determine if the found match is valid.

Probe Targets

From ER 2.0.21, you can probe Targets to browse and select specific Target locations to scan when adding a new Target.

Requirements

Make sure that:

To Probe Targets

To probe a Target:

  1. Start a new scan.
  2. In Select Locations, click the arrow next to the Target name to expand and view available locations for that Target.
  3. Select the Target location(s) to scan.
  4. Click Next to continue configuring your new scan.