--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # ACC-VC default checks and policies # Agent Client Collector for Visibility Content default checks and policies {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 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 Agent Client Collector for Visibility Content default checks and policies Agent Client Collector for Visibility Content (ACC-VC) delivers a suite of default checks, policies, and a business rule to help ServiceNow customers gather detailed software, process, and hardware data from endpoint devices. These checks and policies run primarily on a daily schedule to efficiently collect and update inventory, usage metrics, and compliance-related information across diverse operating systems including Windows, macOS, and Linux. Show full answer Show less ## Key Features * **Scheduled Policies:** ACC-VC policies execute once daily by default, ingesting approximately 572KB of data per machine based on typical endpoint configurations. * **Enhanced Discovery:** Runs on a configurable schedule (default 24 hours) to sync agent configurations and avoid discovery conflicts through adjustable system properties. * **Software Asset Management (SAM) Discovery:** Captures installed software and usage metrics on Windows and macOS endpoints, including background jobs processing Osquery logs for detailed insights. * **Installed Software Collection:** Gathers software installation data from non-Windows devices, storing results in the cmdbsamswinstall table. * **File-Based Discovery (FBD):** Supports scanning files using configurable rules and allowlists, enabling discovery of software files, SWID tags, and customized file management inventories. FBD requires activation through the Discovery Definition Configuration Console. * **Oracle GLAS Compliance:** Includes Java Process Discovery and hardware data collection to support Oracle license compliance reporting on relevant devices. * **Web and SaaS Usage Monitoring:** Policies to collect SaaS application metrics and web usage data from managed devices, with configurable activation and data collection frequency. * **Check Types:** ACC-VC defines Enhanced Discovery, SAM Advanced Discovery, and Installed Software check types, each invoking script includes that process respective data payloads. * **Business Rule:** The Enhanced Discovery -- On CI Delete business rule triggers rediscovery actions when a CI linked to an agent is deleted, ensuring data integrity. ## Practical Considerations for ServiceNow Customers * Adjust policy intervals and system properties to balance data freshness with system resource consumption. * Enable File-Based Discovery features explicitly via the Configuration Console to leverage advanced file and software metadata collection. * Ensure appropriate sudo permissions (e.g., for dmidecode and ss commands on Linux) to enable the agent to collect hardware serial numbers and network connection information. * Use delta scanning in File Management to optimize data transfer by sending only changes after the initial full scan. * Leverage Oracle GLAS policies if your environment requires Oracle license compliance data. * Activate and configure web usage and SaaS monitoring policies as needed to extend visibility into application and web usage patterns. Agent Client Collector for Visibility Content (ACC-VC) provides various checks and policies as well as a business rule. ## Policies {#acc-visibility-checks-policies__section_zvl_lfz_z4b} Note: ACC-VC policies execute at a frequency of once per day. The total data ingested would be approximately 572KB. This takes into consideration an average of approximately 1500 installed software applications and approximately 500 running processes other than CI data per machine. {#acc-visibility-checks-policies__table_g55_dyy_5dc__entry__3} | Name | Description | Check definitions | |-|-|-| | Enhanced Discovery | Runs on a schedule, by default every 24 hours (86400 seconds). The policy interval can be adjusted, for example to run every 4 hours (set the interval to 14400). The ACC-VC policy configuration is synced to all agents based on the policy filter defined by ACC-VC. Update the following ACC-F system properties, if needed: * sn_agent.disco_minimum_threshold_for_rediscovery_minutes: to avoid discovering the system too frequently. * sn_agent.disco_disable_ci_clobber_of_agentless_disco: to avoid Discovery conflicts. * sn_agent.disco_ci_clobber_of_agentless_disco_threshold_days: to avoid Discovery conflicts. {#acc-visibility-checks-policies__ul_ald_31z_5dc} | Enhanced Discovery | | SAM Discovery | Responsible for capturing the software installed on any endpoint device, such as Windows desktops or macOS servers. | Software installations and usage metrics | | SAM background | Enables a background job for processing the Osqueryd logs for SAM on Windows and macOS endpoint devices. | SAM background log check | | SAM background (Non OsqueryD) | Enables a background job to collect SAM information using osqueryi instead of osqueryd. | SAM Background Policy (Non OsqueryD) | | Software installed | Responsible for capturing the software installed on all devices except for Windows endpoint devices. The data collected is stored in the \[cmdb_sam_sw_install\] table. Scheduled to run every 24 hours. | installed software | | File-based Discovery background policy | Takes the config file as input from the instance to an agent. Scans the system using config file parameters and stores the output in two separate files on the agent. * FBDSAMOutput.json: Stores metadata related to the set of file names generated from the samp_file_name table. * FBDFileOutput.json: Stores metadata related to files scanned by a wildcard extension. {#acc-visibility-checks-policies__ul_xr4_lzd_k3c} Runs on the agent when file-based discovery is invoked. For details, see [Agent Client Collector File-Based Discovery](https://www.servicenow.com/docs/M01YQdofg5IIg~qKm4HPiw "Agent Client Collector File-Based Discovery (FBD) scans file systems on managed endpoints to discover installed software and track file inventories."). Default: false. To activate, navigate to AllDiscovery DefinitionConfiguration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch. | File-based discovery background | | File-based Discovery - SAM | Discovers known software files on the endpoint. Uses an allowlist of recognized software filenames maintained by ServiceNow. When a file on disk matches an allowlist entry, FBD uses the FileBasedDiscovery API to identify the collected software metadata (file name, path, size, and version), identifies the software package it belongs to and records the installation on the instance. Unrecognized files are tracked in the unidentified file records table (cmdb_unidentified_file_set). Runs daily. Default: false. To activate, navigate to AllDiscovery DefinitionConfiguration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch. | File-based discovery - SAM | | File-based Discovery - SWID tag | Enables SWID tag scanning on a Windows, Linux or macOS platform. When enabled, the scanner looks for .swid, .swidtag, and .cmptag files in the configured scan directories. Stores results in the following tables: * cmdb_swid_tag: Parsed SWID tag records * cmdb_file_information: Individual file records * cmdb_sam_sw_install: Individual software records {#acc-visibility-checks-policies__ul_s4h_wxl_djc} Default: false. To activate, navigate to AllDiscovery DefinitionConfiguration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch. | | | File-based Discovery - File management | Discovers files based on customer-defined rules. Administrators configure which file extensions to look for and define filename matching rules such as exact match, starts with, ends with, or contains. This policy builds a device-level file inventory based on the organization's specific needs. Results are stored in the sn_acc_vis_content_device_file_information table. Configure rules in the File Matching rules (sn_acc_vis_contet_file_config) and File extensions (sn_acc_vis_content_file_extension) properties. For details on these properties, see [Agent Client Collector File-Based Discovery properties](https://www.servicenow.com/docs/uYraH37ceqKybCyQfFkEtw "Configure File-Based Discovery behavior using system properties that control scanning paths, performance throttling, and file filtering options."). File Management supports delta scanning; after the initial full scan, only added, modified, and deleted files are sent on subsequent runs. For details on delta scanning, see [Agent Client Collector File-Based Discovery](https://www.servicenow.com/docs/M01YQdofg5IIg~qKm4HPiw "Agent Client Collector File-Based Discovery (FBD) scans file systems on managed endpoints to discover installed software and track file inventories."). Default: false. To activate, navigate to AllDiscovery DefinitionConfiguration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch. | File-based discovery - File management | | Oracle GLAS Java Process Discovery | Discovers running Java processes on endpoints and collects installation data for the Oracle GLAS license compliance report. Runs weekly. | Oracle GLAS Java Process Discovery | | Oracle GLAS HW data collection | Executes Oracle's hardware validation script on non-Oracle, non-macOS hosts to collect CPU/socket data for GLAS reporting. Runs weekly. | Oracle GLAS HW data collection | | VISC Get application metric | Retrieves the SaaS application metrics from the agents. For details on enabling SaaS usage monitoring with ACC-VC, see the [SaaS Usage Monitoring with Agent Client Collector \[KB2320193\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2320193) article in the Now Support Knowledge Base. | VISC Get application metric | | VISC Get browser extension device init | Initializes the DEX browser extension with the host sysID. | VISC Get browser extension device init | | VISC Get browser extension init | Initializes the DEX browser extension with logged-in users. | VISC Get browser extension init | | VISC Get URL metrics | Controls the collection of web usage data from Windows and macOS managed devices. Runs daily. Default: Inactive. To activate the policy, set the sn_acc_vis_content.enable_full_monitoring property to true. For details on web usage data system properties, see [Web usage data collection tables and fields](https://www.servicenow.com/docs/q9nsU01zExOBnhDel3eKjg "Description of the tables and their fields used when gathering web usage data from your Windows and macOS machines."). | * VISC Get URL metrics * VISC Get targeted URL metric | [Table 1. ACC-VC policies] {#acc-visibility-checks-policies__table_g55_dyy_5dc} Note: Windows endpoint devices include devices that have a Windows operating system and belong to CI class: computer. See [System properties](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&version=australia&pubname=australia-platform-administration&ft:locale=en-US) for more details. For more details on policies, see [Checks and policies](https://www.servicenow.com/docs/sQMAhnl2PqLHoSgSvIkQYg "A check is a combination of a command and its configuration. The check is executed on the Agent Client Collector's devices to gather data from those devices."). ## Check type {#acc-visibility-checks-policies__section_i2j_dzz_1pb} ACC-VC has the following check types: Enhanced Discovery, SAM Advanced Discovery, and Installed Software. Enhanced Discovery : This check type is responsible for invoking the EnhancedDiscoveryHandler script include that processes the payload produced by endpoint_discovery.rb as executed by ACC.Used by File-base Discovery. SAM Advanced Discovery : This check type is for the SAM Discovery policy that invokes the EnhancedDiscoveryHandler script include for processing the SAM data produced by the sam_advanced.rb file. Installed Software : This check type for the Software installed policy that invokes the EnhancedDiscoveryHandler script include for processing the installed software data produced by the installed_software.rb file. ## Check definitions {#acc-visibility-checks-policies__section_lck_mfz_z4b} {#acc-visibility-checks-policies__table_pkc_vdz_5dc__entry__2} | Name | Description | |-|-| | Enhanced Discovery | Synced to all agents based on the policy filter defined by ACC-VC. The Check definition is configured to run with certain assets and determines what gets synced between the agent and the MID Server. For more details on policies, see [Checks and policies](https://www.servicenow.com/docs/sQMAhnl2PqLHoSgSvIkQYg "A check is a combination of a command and its configuration. The check is executed on the Agent Client Collector's devices to gather data from those devices."). Note: For the agent to retrieve the OS serial numbers and TCP connections along with associated running processes, sudo access for "dmidecode" and "ss" is required on Linux systems. For example, this content could be added to /etc/sudoers or to an individual file in /etc/sudoers.d/: Cmnd_Alias AGENT_ACC_V = /usr/sbin/dmidecode -s baseboard-serial-number,/usr/sbin/dmidecode -s chassis-serial-number,/usr/sbin/dmidecode -s system-serial-number,/usr/sbin/dmidecode -s system-uuid,/usr/sbin/ss -tanp servicenow ALL=(root) NOPASSWD:AGENT_ACC_V | | SAM background log check | Runs every 8 minutes and performs inline aggregation of data generated from Osqueryd logs. After collecting the data, it writes all the intermediate data results into a temporary marker file which is reused in the next run. This reuse limits the number of log files and disk space needed on target systems. Note: You may notice a spike in system resource consumption, as the background aggregation check runs every interval. | | Software installations and usage metrics | Collects data every 24 hours. | | Installed software | Fetches installed software data for all devices other than Windows and macOS endpoint devices. | | File-based discovery background | Runs a file scanning background job on the agent. | | File-based discovery | Fetches the file data from the agent. | | Oracle GLAS Java Process Discovery | Runs `pbd_java_discovery.rb` via osquery to collect Java version, vendor, AMC, and licensing flags. Timeout: 600s. Runs on all platforms. | | Oracle GLAS HW data collection | Runs endpoint_discovery.rb --select=oracle_glas_hw_discovery to execute Oracle's `ct_cpuq` script. Executes Oracle's hardware validation script on non-Oracle, non-macOS hosts to collect CPU/socket data for GLAS reporting. Runs weekly. | | VISC Get targeted URL metric | Gathers per-day usage metrics for the monitored URL from each managed device, and sends the data back to the instance. | [Table 2. ACC-VC check definitions] {#acc-visibility-checks-policies__table_pkc_vdz_5dc} ## Business rule {#acc-visibility-checks-policies__section_iwf_chz_z4b} The Enhanced Discovery -- On CI Delete business rule triggers the Endpoint Discovery Check when the CI associated with a given CI is deleted from sn_agent_cmdb_ci_agent. *[\>]: and then