---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# ACC-VC system properties

# ACC-VC system properties {#ariaid-title1}

Release version: Brazil  
Updated October 15, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 10 minutes to read  
System properties that control how Agent Client Collector for Visibility Content (ACC-VC) discovers, collects, and stores data on your instance.
All properties in this topic belong to the ACC-VC (`sn_acc_vis_content`) application. To view or update a property, navigate to All and enter <kbd class="ph userinput">sys_properties.list</kbd> in the filter, and then search
for the property name.

The properties are grouped by the area of ACC-VC that they affect.

## General discovery and logging properties {#accvc-system-properties__section-accvc-general-properties}

{#accvc-system-properties__table-accvc-general-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.enable_discovery_on_agent_up | * Type: true \| false * Default value: false {#accvc-system-properties__ul_mrd_rr3_xkc} Runs discovery when an agent comes up (the Agent Up event). Warning: Enabling this property might cause performance issues, especially with many agents or if agents frequently go offline and come back online. The impact is greater if all agents come online at the same time. |
| sn_acc_vis_content.logging.verbosity | * Type: string * Default value: info {#accvc-system-properties__ul_nrd_rr3_xkc} Controls the logging verbosity for the ACC-VC application. Valid values are `debug`, `info`, `warn`, and `error`. |
[Table 1. ACC-VC general discovery and logging properties]

{#accvc-system-properties__table-accvc-general-properties}

## File-based discovery properties {#accvc-system-properties__section-accvc-file-discovery-properties}

For additional file-based discovery (FBD) properties and how they work together, see [Agent Client Collector File-Based Discovery properties](https://www.servicenow.com/docs/FaIAX_IrfC~rFuwTzDTXnw "Configure File-Based Discovery behavior using system properties that control scanning paths, performance throttling, and file filtering options.").
{#accvc-system-properties__table-accvc-file-discovery-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.file_discovery.enable_fbd_fullscan | * Type: true \| false * Default value: false Controls which files ACC-VC sends to the instance during FBD. * When <kbd class="ph userinput">false</kbd>, ACC-VC ignores the extensions set in the configuration console table and sends only the files specified in the `sn_acc_vis_content_file_config` tableto the instance. * When <kbd class="ph userinput">true</kbd>, ACC-VC recognizes the extensions set in the configuration console, even if they aren't specified in the `sn_acc_vis_content_file_config` table. If no files are listed in that table, ACC-VC retrieves all files of the specified extension type. If files are listed in that table, ACC-VC retrieves only those files. |
| sn_acc_vis_content.file_discovery.fbd_process_scan_enabled | * Type: true \| false * Default value: false Enables process-based FBD discovery. When set to <kbd class="ph userinput">true</kbd>: * The FBD Software Asset Management (SAM) Process Scan agent policy is activated. The `fbd_process_scan.rb` script runs every 5 minutes and collects the directories of running processes into the ProcessScanPaths.ndjson file. * The `processScanEnabled=true` setting is synced into the AgentFBDWindowsParameters.json and AgentFBDUnixParameters.json files, so that the `files_background.rb` script includes the process-discovered directories in its daily scan. For details, see [Running process-based discovery](https://www.servicenow.com/docs/phlhYcyZdhh1Qa9GSmqvMw "Running process-based discovery extends File-Based Discovery (FBD) with process-based path detection, enabling the Agent Client Collector for Visibility Content agent to detect software running outside of standard configured scan directories."). |
| sn_acc_vis_content.file_discovery.archive_scan_enabled | * Type: true \| false * Default value: false Enables scanning inside ZIP and JAR archive files during FBD. When true, the agent reads the internal index of the ZIP and JAR archives in the configured scan paths and reports the files inside them, using the same SAM and File Management filtering rules as for regular files. ACC-VC doesn't extract or decompress any file content. It collects only metadata: the file name, size, extension, and path. The agent automatically skips archives that are larger than 500 MB, contain more than 50,000 entries, or take longer than 30 seconds to scan. It doesn't scan nested archives, which are archives inside other archives. For details, see [Archive file scanning filtering rules and limits](https://www.servicenow.com/docs/ldqOh1AqsNznazfG~o3iWA "Reference information for the filtering rules and performance safeguards that apply when Agent Client Collector for Visibility Content scans ZIP and JAR archive files during File-Based Discovery."). |
| sn_acc_vis_content.file_discovery.enable_glas_hw_collection | * Type: true \| false * Default value: false Enables the collection of Oracle hardware data for the Oracle GLAS report. |
| sn_acc_vis_content.file_discovery.enable_java_discovery | * Type: true \| false * Default value: true Enables Java discovery in ACC-VC file-based discovery. |
| sn_acc_vis_content.file_discovery.encode_swid_tag_content | * Type: true \| false * Default value: true Enables Base64 encoding of SWID tag content before ACC-VC stores it on the instance. |
| sn_acc_vis_content.file_discovery.fresh_scan_frequency_by_delta_count | * Type: integer * Default value: 5 Defines how often, in number of delta payload processing cycles, ACC-VC performs a fresh (full) scan. For example, a value of 5 means that a full scan runs after every 5 delta payloads. |
| sn_acc_vis_content.file_discovery.additional_swid_extensions | * Type: string * Default value: empty Defines additional file extensions that FBD treats as SWID tag files, along with the built-in defaults (`.swid`, `.swidtag`, and `.cmptag`). The agent scans files that match these extensions for SWID tag content, instead of evaluating them for SAM or File Management discovery. The extensions that you configure are added to the defaults and never replace them. Separate multiple extensions with a pipe character (`|`). You can enter each extension as `*.ext`, `.ext`, or `ext`. ACC-VC normalizes all formats automatically. For example: `*.tag|.customtag|customtag` To use only the default SWID extensions, leave the value empty. Warning: Add extensions with caution. The agent scans any file that matches a configured extension only as a SWID tag file, and no longer evaluates it for SAM or File Management discovery. An extension that is too broad can cause unrelated files to be misclassified and increase the scan overhead. Don't add common, general-purpose extensions, such as `.xml`, `.txt`, or `.log`. These extensions match a very large number of unrelated files on a typical endpoint, which significantly increases the scan time and can cause performance issues on the instance. |
| sn_acc_vis_content.file_discovery.mime_type.unix | * Type: string * Default value: empty Defines the list of MIME types to scan on Unix platforms. Separate multiple MIME types with a colon (`:`). Don't include spaces or quotation marks. For example: `application/x-pie-executable:application/x-sharedlib:text/x-shellscript:text/x-script.python` |
| sn_acc_vis_content.file_discovery.version_skip_extension_list.unix | * Type: string * Default value: A predefined list of file extensions Defines the file extensions for which ACC-VC doesn't query the file version on Unix platforms. For a file with an extension in this list, ACC-VC collects the name and size and automatically skips the version. Separate multiple extensions with a pipe character (`|`). For example: `*.so|*.py|*.sh` |
| sn_acc_vis_content.file_discovery.version_skip_extension_list.windows | * Type: string * Default value: A predefined list of file extensions Defines the file extensions for which ACC-VC doesn't query the file version on Windows platforms. For a file with an extension in this list, ACC-VC collects the name and size and automatically skips the version. Separate multiple extensions with a pipe character (`|`). For example: `*.txt|*.var|*.json` |
[Table 2. ACC-VC file-based discovery properties]

{#accvc-system-properties__table-accvc-file-discovery-properties}

## License key discovery properties {#accvc-system-properties__section-accvc-license-key-properties}

{#accvc-system-properties__table-accvc-license-key-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.enable_license_key_discovery | * Type: true \| false * Default value: false {#accvc-system-properties__ul_krd_rr3_xkc} Turns license key discovery on or off. When set to `true`, ACC-VC processes and stores license key data collected from the Windows registry and license key files discovered by file-based discovery (FBD) scans. For details, see [License key discovery](https://www.servicenow.com/docs/QBzDRSOHIj3AXrbqcjpspw "License key discovery in Agent Client Collector for Visibility Content automatically collects software license keys from the Windows registry on managed endpoints."). |
[Table 3. ACC-VC license key discovery properties]

{#accvc-system-properties__table-accvc-license-key-properties}

## Host and network properties {#accvc-system-properties__section-accvc-host-network-properties}

{#accvc-system-properties__table-accvc-host-network-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.persist_os_user_type | * Type: string * Default value: `local,system` {#accvc-system-properties__ul_xmf_vt3_xkc} Defines which types of operating system user data ACC-VC discovery stores. Valid values are `local` and `system`. Separate multiple values with a comma and no spaces. |
| sn_acc_vis_content.windows_model_number_filter_enabled | * Type: true \| false * Default value: false {#accvc-system-properties__ul_hrd_rr3_xkc} Controls whether ACC-VC uses the `model_number` value collected from a Windows server when it performs the Make and Model lookup to identify the hardware product model of the CI. * When `false`, `model_number` is included in the lookup. * When `true`, `model_number` is excluded from the lookup, which helps prevent invalid product model records from being created. {#accvc-system-properties__ul_ird_rr3_xkc} A change to the value takes effect on the next ACC-VC discovery run. This property affects only Windows CIs. CIs that run Linux, macOS, or any other operating system aren't affected. |
| sn_acc_vis_content.network_adapter_exclusion_list | * Type: string * Default value: empty {#accvc-system-properties__ul_ymf_vt3_xkc} Defines regular expressions for the network adapter names and IP addresses to exclude from the Network Adapter and IP Address tables. For details, see [Setting exclusion lists for IPs and NICs](https://www.servicenow.com/docs/dZeUD~aeaenJjK1N~wASXg "Agent Client Collector for Visibility Content (ACC-VC) version 1.3.0 supports exclusion lists for IPs and Network Interface Controllers (NICs). A flexible mechanism filters out values for IPs and NICs when creating or updating the host CI and related items."). Enter the network adapter expressions and the IP address expressions on separate lines, using `nic` and `ip_addr` as the keywords. Separate multiple expressions on the same line with a comma. Don't use a comma inside a regular expression. For example: nic = bond0 ip_addr = 10\.196\.\d+\.\d+ The regular expressions and keywords are case-sensitive. A value that doesn't follow this format is treated as an invalid regular expression, which leads to incorrect exclusion or persistence issues. |
[Table 4. ACC-VC host and network properties]

{#accvc-system-properties__table-accvc-host-network-properties}

## User mapping and assignment properties {#accvc-system-properties__section-accvc-user-mapping-properties}

{#accvc-system-properties__table-accvc-user-mapping-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.set_assigned_to | * Type: true \| false * Default value: false {#accvc-system-properties__ul_rmf_vt3_xkc} Controls whether ACC-VC overrides the Assigned to value of a computer CI. * When `true`, ACC-VC overrides the Assigned to value. * When `false`, the existing Assigned to value is unchanged. {#accvc-system-properties__ul_smf_vt3_xkc} |
| sn_acc_vis_content.assigned_to_user_order | * Type: string * Default value: `computer_system_username,logged_in_users` {#accvc-system-properties__ul_tmf_vt3_xkc} Defines the priority order of the username sources that ACC-VC uses to set the Assigned to value of a computer CI. The username from the first source in the list takes precedence. Separate sources with a comma. Valid sources are: * `computer_system_username`: The username that ACC-VC derives from the native command on a Windows machine. * `logged_in_users`: The logged-in users that ACC-VC gets from the osquery table. {#accvc-system-properties__ul_umf_vt3_xkc} |
| sn_acc_vis_content.column_name_for_user_mapping | * Type: string * Default value: empty {#accvc-system-properties__ul_vmf_vt3_xkc} Maps a user (the Assigned to value) to an agent CI, and maps SAM usage to a user, based on the Active Directory (AD) domain. The value is the name of the column in the `sys_user` table that ACC-VC uses to verify the username and domain and map them to the right CI. * If the value is empty, ACC-VC maps the Assigned to value by username only, not by domain. * The column can be a base system column or a custom column in the `sys_user` table. * The supported username and domain formats are `username@domain` and `domain\username`. * The domain is case-sensitive. {#accvc-system-properties__ul_wmf_vt3_xkc} |
[Table 5. ACC-VC user mapping and assignment properties]

{#accvc-system-properties__table-accvc-user-mapping-properties}

## Software discovery and usage metrics properties {#accvc-system-properties__section-accvc-software-usage-properties}

{#accvc-system-properties__table-accvc-software-usage-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.enable_sam_collection_without_osqueryd | * Type: true \| false * Default value: false {#accvc-system-properties__ul_g3r_ks3_xkc} When set to <kbd class="ph userinput">true</kbd>, ACC-VC collects Software Asset Management (SAM) metering information without requiring configuration on Windows and macOS machines. |
| sn_acc_vis_content.persist_sam_usage_metrics | * Type: true \| false * Default value: true {#accvc-system-properties__ul_f3r_ks3_xkc} Controls whether ACC-VC stores SAM-related usage information. When set to `true`, ACC-VC stores the information. |
| sn_acc_vis_content.sw_categorization.enabled | * Type: true \| false * Default value: false {#accvc-system-properties__ul_jrd_rr3_xkc} Turns software categorization on or off. When set to `true`, ACC-VC matches newly discovered software packages against install signatures and categorizes them. For details, see [Software packages categorization](https://www.servicenow.com/docs/XlSTCl79yWt~cQmPBVNHGw "Agent Client Collector for Visibility (ACC-VC) classifies discovered software packages in your environment into categories. This categorization removes the need to tag software records manually and provides an accurate software inventory."). |
| sn_acc_vis_content.disable_sam_reclamation_rules_for_licensable_softwares | * Type: true \| false * Default value: false {#accvc-system-properties__ul_h3r_ks3_xkc} Controls whether reclamation rules apply to licensed software when ACC-VC stores SAM usage. * When `true`, ACC-VC stores SAM usage for all licensed software, with or without a defined reclamation rule. It also stores usage for any non-licensed software that has a reclamation rule defined. * When `false`, ACC-VC stores SAM usage according to the defined reclamation rules. {#accvc-system-properties__ul_i3r_ks3_xkc} |
[Table 6. ACC-VC software discovery and usage metrics properties]

{#accvc-system-properties__table-accvc-software-usage-properties}

## SaaS usage metrics properties {#accvc-system-properties__section-accvc-saas-usage-properties}

{#accvc-system-properties__table-accvc-saas-usage-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.enable_full_monitoring | * Type: true \| false * Default value: false {#accvc-system-properties__ul_vy2_t53_xkc} Enables full monitoring for all URLs. For details on web usage collection, see [Collect web usage data using Agent Client Collector for Visibility Content](https://www.servicenow.com/docs/xF3tAbVM8IDz~AEklYhX0g "Track website visits across your organization and gain visibility into web applications your users access using Agent Client Collector for Visibility Content (ACC-VC)."). |
| sn_acc_vis_content.max_daywise_aggregation_domains | * Type: integer * Default value: 500 {#accvc-system-properties__ul_xy2_t53_xkc} Maximum number of top domains, ranked by page views, for which ACC-VC aggregates day-wise page visit data. |
| sn_acc_vis_content.full_url_discovery_daily_max_rows | * Type: integer * Default value: 200 {#accvc-system-properties__ul_yy2_t53_xkc} Maximum number of distinct domain rows that Full URL Discovery stores each day in the agent-local `url_monitoring` table. The first domains that the agent sees each day are the ones stored. After the limit is reached for a day, ACC-VC drops new domains, and existing rows continue to update. |
| sn_acc_vis_content.acc_vis_targeted_url_metric_daily_max_rows | * Type: integer * Default value: 200 {#accvc-system-properties__ul_zy2_t53_xkc} Maximum number of distinct URL rows that ACC-VC stores each day in the agent-local `acc_vis_targeted_url_metric_daily` table. The first URLs that the agent sees each day are the ones stored. After the limit is reached for a day, ACC-VC drops new URLs, and existing rows continue to update. |
| sn_acc_vis_content.web_usage_retention_days | * Type: integer * Default value: 7 {#accvc-system-properties__ul_wy2_t53_xkc} Number of days that ACC-VC retains web usage data. |
| sn_acc_vis_content.saas_metric_tables_retention_period | * Type: integer * Default value: 2678400 {#accvc-system-properties__ul_az2_t53_xkc} Retention period, in seconds, for the SaaS usage metrics tables. The default value is 31 days. |
[Table 7. ACC-VC SaaS usage metrics properties]

{#accvc-system-properties__table-accvc-saas-usage-properties}

For the tables that ACC-VC uses to store web usage data, see [Web usage data collection tables and fields](https://www.servicenow.com/docs/AHHxwVBiCw5~1kj3OWFuYw "Description of the tables and their fields used when gathering web usage data from your Windows and macOS machines.").

## Browser extension discovery properties {#accvc-system-properties__section-accvc-browser-extension-properties}

{#accvc-system-properties__table-accvc-browser-extension-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.full_browser_extension_discovery | * Type: true \| false * Default value: false {#accvc-system-properties__ul_qmy_my3_xkc} Controls the browser extension discovery mode. For details, see [Browser extension discovery and categorization](https://www.servicenow.com/docs/PSq~HaH1aABkyQG_VjgjZQ "Agent Client Collector for Visibility (ACC-VC) browser extension discovery inventories browser extensions installed on the endpoints in your environment. When an admin-defined signature matches, ACC-VC classifies each extension into a category, such as AI Tools, Productivity, or Security."). * When `false`, ACC-VC uses signature mode. The agent matches the discovered extensions against the active signatures and reports only the matched extensions, so the tables receive only known extensions that have a signature. * When `true`, ACC-VC uses full discovery mode. The agent reports every discovered browser extension. Extensions that match a signature are classified. Extensions that don't match are added to the catalog with empty classification fields. {#accvc-system-properties__ul_rmy_my3_xkc} |
| sn_acc_vis_content.collect_extended_browser_extension_metadata | * Type: true \| false * Default value: false {#accvc-system-properties__ul_smy_my3_xkc} Controls whether agents collect extended browser extension metadata, such as manifest permissions, host access, install source and timestamps, and sideload signals, and the basic identifier, name, version, and status fields. * When `false`, agents report only the basic fields. They don't fetch extended metadata, which keeps the payload smaller. * When `true`, agents also collect and report the extended fields, and ACC-VC stores them in the `sn_acc_vis_content_browser_extension_metadata` table. {#accvc-system-properties__ul_tmy_my3_xkc} This property is independent of sn_acc_vis_content.full_browser_extension_discovery. That property controls which extensions are reported. This property controls whether the reported extensions include the extended fields. |
[Table 8. ACC-VC browser extension discovery properties]

{#accvc-system-properties__table-accvc-browser-extension-properties}

## TLS/SSL certificate discovery properties {#accvc-system-properties__section-accvc-tls-ssl-properties}

{#accvc-system-properties__table-accvc-tls-ssl-properties__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.tls_ssl_scanner_ports | * Type: string * Default value: `443,8443,9443,636,993,995,989,990,25,110,143,389,21,587` {#accvc-system-properties__ul_lx3_xz3_xkc} Ports that ACC-VC scans for SSL certificates. |
| sn_acc_vis_content.tls_ssl_scan_all_open_ports | * Type: true \| false * Default value: false {#accvc-system-properties__ul_nx3_xz3_xkc} Enables certificate discovery on all available open ports. |
| sn_acc_vis_content.tls_ssl_keep_original_cert | * Type: true \| false * Default value: false {#accvc-system-properties__ul_ox3_xz3_xkc} Whether the agent TLS/SSL certificate discovery returns the original certificate. |
[Table 9. ACC-VC TLS/SSL certificate discovery properties]

{#accvc-system-properties__table-accvc-tls-ssl-properties}

## Non-persistent VDI properties {#accvc-system-properties__section-accvc-npvdi-properties-summary}

The following properties apply only to Windows non-persistent virtual desktop infrastructure (NPVDI) endpoints. For the full description of each property, see [ACC-VC NPVDI system properties](https://www.servicenow.com/docs/5QN32zZh8isD17p8mHvAkg "System properties that control how Agent Client Collector for Visibility Content (ACC-VC) runs Enhanced Discovery and installed software checks on Windows non-persistent virtual desktop infrastructure (NPVDI) endpoints.").
{#accvc-system-properties__table-accvc-npvdi-properties-summary__entry__2}

| Property | Description |
|-|-|
| sn_acc_vis_content.np_vdi.cache_installed_software_enabled | Caches the full installed software scan on NPVDI endpoints so that it runs only one time for each golden image. |
| sn_acc_vis_content.np_vdi.enhanced_discovery_skip_modules | Lists the Enhanced Discovery modules to skip on NPVDI endpoints. |
[Table 10. ACC-VC NPVDI properties]

{#accvc-system-properties__table-accvc-npvdi-properties-summary}