License key discovery and access control tables
Summarize
Summary of License key discovery and access control tables
This documentation explains the tables, fields, access controls, and scheduled job used for license key discovery within the Agent Client Collector for Visibility - Content in ServiceNow's Australia release. It details how license keys are collected from endpoint devices, stored, and managed through specific configuration settings.
Show less
Key Features
- License Key Discovery Tables: Two main tables are involved:
- License Registry Configuration (snaccviscontentlicenseregistryconfig): Admin-managed list of registry paths and value names to collect license keys from endpoints.
- License Keys (snaccviscontentlicensekeys): Stores the actual license key values discovered from devices.
- License Keys Table Fields: Captures details such as the device (configuration item), associated SAM product, assigned user, the configuration rule that discovered the key, exact registry path, discovered key value, last scanned date, and an "Absent" status to indicate keys no longer found (records are not deleted but marked).
- License Registry Configuration Fields: Includes SAM product association, Windows registry path and value name to read, a combined name field, description notes, and an active indicator to control inclusion in data collection. Each configuration record must be unique based on product, registry path, and value name.
- Access Control: Defined roles include:
- ACC application admin: Full access (read, write, create) to registry configuration and read-only to license keys.
- Discovery admin: Full access to registry configuration and read-only to license keys.
- SAM admin: Read-only access to both tables.
- All other roles have no access.
- Scheduled Job: A daily scheduled job runs at 8:30 a.m. UTC to refresh the License Key Config File. This job only runs if the property
snaccviscontent.enablelicensekeydiscoveryis enabled and the SAM Professional plugin is activated.
Key Outcomes
ServiceNow customers can use these tables and configurations to effectively discover, track, and manage license keys on endpoint devices via registry data. The access controls ensure proper role-based security, while the scheduled job automates updating configuration data daily. The approach of marking keys as absent rather than deleting records supports historical tracking and auditability.
Reference information for the tables, fields, access control, and scheduled job used by license key discovery in Agent Client Collector for Visibility - Content.
Tables
License key discovery uses the following tables.
| Table | Label | Purpose |
|---|---|---|
| sn_acc_vis_content_license_registry_config | License Registry Configuration | Admin-managed list of registry paths and value names to collect from managed endpoints. |
| sn_acc_vis_content_license_keys | License Keys | Stores the license key values collected from endpoint devices. |
License Keys table fields
The License Keys [sn_acc_vis_content_license_keys] table stores the following fields for each discovered key.
| Field | Description |
|---|---|
| Configuration Item | Device the key was collected from. Table: cmdb_ci_computer. |
| Product | SAM product associated with this key. Table: samp_sw_product. |
| User | This field is automatically set to the user assigned to the CI. Table: sys_user. |
| License Key Config | Configuration rule that discovered this key. Table: sn_acc_vis_content_license_registry_config. |
| Resolved Registry Path | Exact registry path the key was read from on the endpoint. |
| License Key | Discovered key value. |
| Last Scanned | Date the key was last detected by the agent. |
| Absent | Selected when the key is no longer found on the device. Records are never deleted, they are marked Absent instead. |
License Registry Configuration form fields
The following table describes the fields in the License Registry Configuration [sn_acc_vis_content_license_registry_config] table.
| Field | Description |
|---|---|
| Product | SAM product this license key belongs to. Links to the SAM Professional product catalog. |
| Registry Path | Windows registry path where the key is stored. For example, HKLM\SOFTWARE\Microsoft\Office\16.0\Registration. |
| Registry Value Name | Specific registry value to read. For example, DigitalProductId. |
| Name | This field is automatically set to a combination of the Product and Registry Value Name values. |
| Description | Notes about this configuration record. |
| Active | Indicator of whether this record is included in future collections. Clearing this check box removes the record from future collections. |
Access control
The following table shows which roles can access each license key discovery table.
| Role | License Registry Configuration table | License Keys table |
|---|---|---|
| ACC application admin (agent_client_collector_admin) | Read, write, create | Read only |
| Discovery admin (discovery_admin) | Read, write, create | Read only |
| SAM admin (sam_admin) | Read only | Read only |
| All other roles | No access | No access |
Scheduled job
The following scheduled job supports license key discovery.
| Job | Schedule | Condition |
|---|---|---|
| Refresh License Key Config File | Daily at 8:30 a.m. UTC | Runs only when the sn_acc_vis_content.enable_license_key_discovery property is set to true and the SAM Professional plugin (com.snc.samp) is activated. |