File-based Discovery references

  • Release version: Australia
  • Updated March 24, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of File-based Discovery references

    File-based Discovery in ServiceNow is designed to efficiently scan large networks, especially Windows environments, by minimizing performance impact on target systems and reducing processing time. It achieves this by using optimized scanning techniques and configurable settings accessible via the Discovery Configuration Console.

    Show full answer Show less

    Key Features

    • Multi-phase scan: Scanning is divided into phases where an initial probe starts a background scan on the target, and subsequent probes check scan progress and fetch results only after completion. This means results are only returned on subsequent Discovery runs, avoiding long scan delays.
    • Scoped scanning: You can limit scans to specific folders, include hidden folders, and focus on particular file extensions while ignoring others.
    • UNIX and Windows file scanning: UNIX scans use a predefined list of unique file names for filtering directly on the target, while Windows scans generate a filtered list of file extensions on the MID Server to reduce payload size.
    • Reduced payloads: Only files matching signature lists are returned to the instance, decreasing network and processing load.
    • Scan throttling: Windows scans are periodically paused to reduce CPU and I/O load on target machines. This behavior can be tuned via Discovery properties, though it may extend scan duration.
    • File-based Discovery tables:
      • File Information [cmdbfileinformation]: Stores all discovered files related to a CI, including path, product, publisher, size, version, and associated software installation when SAMP is enabled.
      • Unidentified File Set [cmdbunidentifiedfileset]: Stores unmatched files with details like name, size, version, and optional metadata to assist in future identification. Integration with Software Asset Management Professional (SAMP) allows uploading this data to Content Data Services (CDS) to improve matching accuracy.

    Practical Benefits for ServiceNow Customers

    • Improved discovery performance with minimal impact on target systems, enabling more efficient network-wide file scanning.
    • Configurable scanning parameters help tailor discovery to organizational needs, focusing on relevant files and folders.
    • Integration with SAMP enhances software asset management by identifying installed software from discovered files and refining software identification over time.
    • Structured data storage in dedicated tables facilitates easier management and analysis of discovered files and unidentified files.
    • Mechanisms for issue resolution and detailed configuration guidance are available to support smooth deployment and operation.

    Review this reference material for further details on File-based Discovery.

    How File-based Discovery minimizes performance impact

    Scanning large networks, particularly for Windows computers, can extend scan time considerably. Moreover, file scanning can create heavy CPU demands on target machines and produce large payloads that greatly increase processing time. To avoid performance issues, File-based Discovery allows you to optimize processing with many of the settings configured using the Discovery Configuration Console.
    • Multi-phase scan: Probes are triggered in multiple phases to reduce long scan times. The first probe creates the scanning process on the target, which runs in the background. Subsequent probes check the progress of this scan each time Discovery runs and return the results when the scan is complete. For example, if a file scan is initiated via Quick Discovery or from a Discovery schedule, no information is returned if a background scan is still running. If the scan is finished the next time the server is discovered, the probe returns the data.
      Important:
      The multi-phase scan that File-based Discovery uses does not return results immediately. Do not expect any results from a file-based scan until Discovery runs again on those targets and fetches the list of files discovered by the previous scan.
    • Scan folders: You can limit the scope of the scan to particular folders as well as scan hidden folders.
    • Scan extensions: You can retrieve all files for a given list of extensions as well as ignore specific file extensions when scanning.
    • Scan UNIX file names: Because the number of unique file names used to identify installed software on UNIX is relatively small, the complete list of file names is included in the UNIX probe. This enables the probe to filter the files it discovers against the signature list on the target. No additional filtering is required until the results are returned to the instance.
    • Scan Windows file names: For Windows File-based Discovery, the probe does not initiate a scan on target for full signature list. Instead, Discovery generates a list of file extensions that the probe attempts to match on the target. This reduced list is then filtered on the MID Server against the entire Windows signature list.
    • Reduced payloads: By filtering the scan results with the file signature list before the results get to the instance, Discovery reduces the size of the payload from target servers. Only those files from the targets that match the files specified in this list are returned to the instance.
    • Scan throttling: To reduce the impact on Windows CPU and I/O performance on remote targets, Windows File-based Discovery is configured to sleep occasionally during scans. You can fine-tune this behavior with Discovery properties. Throttling Windows scans can make those scans take longer.

    File-based Discovery tables

    Descriptions of the tables provided by the File-based Discovery [com.snc.discovery.file_based_discovery] plugin for storing data:
    File Information [cmdb_file_information]
    This table stores all the files, matched or unmatched, that were discovered on a particular CI. The files are available in a related list on CI computer records. The following columns are provided in the default view:
    • Path: Path in which the file was found on the target.
    • Product: Software product name. This field is populated when SAMP is activated and a match exists.
    • Publisher: Name of the publisher of the file, such as Oracle or Microsoft. This is a reference to the Company [core_company] table. This field is populated when SAMP is activated and a match exists.
    • Size: Size of the file.
    • Software installation: Name of the installed software associated with this file, from the Software Installation [cmdb_sam_sw_install] table. This field is populated when SAMP is activated and a match exists.
    • Version: Version of the file. Currently, for Windows only.
    Unidentified File Set [cmdb_unidentified_file_set]
    This table stores all the files returned by Discovery that cannot be matched to a software product, with or without SAMP. Discovery populates the name, size, and version of each unmatched file in the record. These optional fields can be used to further identify the file and make it available for future file matching:
    • Publisher
    • Product
    • Version
    • Edition
    • Platform
    • Language
    Note:
    A feature in Software Asset Management Professional (SAMP) allows signature data in this table to be shared with Content Data Services (CDS). When you enable data sharing, the system automatically uploads records from the Unidentified File Set [cmdb_unidentified_file_set] table to CDS when you provide the missing information. Uploading the identified files makes them available to improve future file matching. For details, see Add a custom software product.

    For a full reference of File-based Discovery system properties and script includes, see the File Based Discovery Now Support Knowledge Base article.

    File-based Discovery issue resolution

    If you're experiencing any issues when setting up or running File-based Discovery, see File-based Discovery issue resolution.