--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # File-based Discovery references # File-based Discovery references {#ariaid-title1} Release version: Australia Updated March 24, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 enables efficient scanning of large networks by minimizing performance impacts on target machines, especially Windows computers. It uses optimized scanning techniques and configurable settings to reduce scan time, CPU load, and data payloads during discovery processes. Show full answer Show less ## Key Features * **Multi-phase scan:** Scans run in multiple phases where the initial probe starts a background scan on the target, and subsequent probes check progress and retrieve results only when the scan completes, preventing immediate data returns and reducing load. * **Scoped scanning:** Allows limiting scans to specific folders, including hidden folders, and selective scanning based on file extensions, enabling focused discovery and reducing unnecessary data collection. * **Platform-specific scanning optimizations:** UNIX scans use a fixed list of unique file names for filtering, while Windows scans generate a target-specific reduced list of file extensions to filter results before sending to the MID Server, lowering payload sizes. * **Scan throttling:** Windows scans include configurable sleep intervals to reduce CPU and I/O impact on target machines, which can be fine-tuned via Discovery properties. * **Data storage in tables:** * **File Information \[cmdbfileinformation\]:** Stores all discovered files related to a CI, including path, product, publisher, size, software installation, and version data when Software Asset Management Professional (SAMP) is activated. * **Unidentified File Set \[cmdbunidentifiedfileset\]:** Captures unmatched files with details like name, size, version, and optional fields to assist in future identification and matching. This data can be shared with Content Data Services (CDS) to improve discovery accuracy. ## Practical Benefits * Improves discovery efficiency and reduces system resource consumption during file scanning on target devices. * Enables focused and configurable scans tailored to business needs, limiting discovery scope and data volume. * Supports integration with Software Asset Management for enhanced software identification and asset tracking. * Facilitates ongoing improvement of software matching through sharing unidentified file data with CDS. ## Additional Resources For detailed configuration options, system properties, script includes, and troubleshooting guidance, customers should refer to the File-based Discovery Now Support Knowledge Base articles and issue resolution documentation. Review this reference material for further details on File-based Discovery. ## How File-based Discovery minimizes performance impact {#file-based-discovery-references__section_hpv_rpp_x2b} 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](https://www.servicenow.com/docs/Dd4Yjm8isniEARaNj8bgVw#c_DiscoveryConfigurationConsole "Use the Discovery Configuration Console to manage what kind of configuration items (CIs) and CI information you want to discover."). * 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: 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, which filters discovered files 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-references__ul_p5f_jnp_x2b} ## File-based Discovery tables {#file-based-discovery-references__fbd-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. {#file-based-discovery-references__ul_crk_rhy_1fb} 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 {#file-based-discovery-references__ul_ykh_spz_1fb} 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](https://www.servicenow.com/docs/access?context=t_AddACustomProduct&version=australia&pubname=australia-it-asset-management&ft:locale=en-US). For a full reference of File-based Discovery system properties and script includes, see the [File Based Discovery](https://support.servicenow.com/now/nav/ui/classic/params/target/kb?id=kb_article_view&sysparm_article=KB0813350) Now Support Knowledge Base article. ## File-based Discovery issue resolution {#file-based-discovery-references__section_n2m_1fv_phb} If you're experiencing any issues when setting up or running File-based Discovery, see [File-based Discovery issue resolution](https://www.servicenow.com/docs/jMday1zZtOq5Kn4n4gGPdQ "If you have any issues while setting up or running File-based Discovery, follow the actions listed here to help resolve them."). **Related concepts** * [File-based Discovery](https://www.servicenow.com/docs/RB2dlcuY_Ka2URmlGBvz7g "File-based Discovery helps you identify what software is running on your Windows and UNIX servers and devices, even if there’s no registration information available. You can then manage and maintain records of your software licenses, check for unlicensed files, detect forbidden or damaged files, and help evaluate any threats from unwanted files.")