Switching from Smart Scan to Conventional Scan

When you switch clients to conventional scan, consider the following:

  1. Number of clients to switch

    Switching a relatively small number of clients at a time allows efficient use of Core Protection Module server and Smart Protection Server resources. These servers can perform other critical tasks while clients change their scan methods.

  2. Timing

    When switching back to conventional scan, clients will likely download the full version of the Virus Pattern and Spyware-active Monitoring Pattern from the Core Protection Module server. These pattern files are only used by conventional scan clients.

    Consider switching during off-peak hours to ensure the download process finishes within a short amount of time. Also consider switching when no clients is scheduled to update from the server. Also temporarily disable "Update Now" on clients and re-enable it after the clients have switched to conventional scan.

  3. Client tree settings

    Scan method is a granular setting that can be set on the root, domain, or individual clients level. When switching to conventional scan, you can:

    • Create a new clients group and add clients and use the following task on the clients group: Core Protection Module > Common Tasks > Core Protection Module > Client | Core Protection Module - Disable Smart Scan.

    • Select clients group and use the following task Core Protection Module > Common Tasks > Core Protection Module > Client | Core Protection Module - Disable Smart Scan.

    • Select one or several smart scan clients from a group and use the following task Core Protection Module > Common Tasks > Core Protection Module > Client | Core Protection Module- Disable Smart Scan.

    Note: Before switching endpoints back to Smart Scan, the following must be done:
    • Smart Protection Relays are deployed in the environment

    • Smart Protection Server list has been deployed to Core Protection Module clients