Axonius - Run Windows WMI Scan
  • 22 Sep 2024
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Axonius - Run Windows WMI Scan

  • Dark
    Light
  • PDF

Article summary

Axonius - Run Windows WMI Scan runs a WMI (Windows Management Instrumentation) scan on each of the query results entities, which are windows devices.

As part of the WMI scan, Axonius reaches out to devices directly and execute commands on them in memory, without installing anything or leaving any traces. The WMI scan retrieves important information about the device, including (but not limited to):

  • Hostname
  • Network Interfaces - including MAC addresses, IP addresses and subnets
  • Operating system, kernel version and distribution
  • List of installed software
  • Users and admin users
  • Hard drives and file systems
  • CPUs and RAM
  • Hardware details, including serial numbers

If Run WMI Scan action was executed on specific device, Windows Management Instrumentation (WMI) adapter is also listed as one of the device different adapters listed under the Adapter Connections tab, on the Device Profile page. Most of the WMI scan information is also displayed under the various Aggregated tables.
For more details, see Device Profile page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

Note:

General Settings

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

Use stored credentials from the Active Directory adapter - Select this option to use the first connected Microsoft Active Directory (AD) adapter credentials.

Note:

To use this option, you must successfully configure a Microsoft Active Directory (AD) adapter connection.

Required Fields

These fields must be configured to run the Enforcement Set.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Additional Fields

These fields are optional.

  • User name and Password - Provide credentials to connect and to execute the command on the windows device: user name and password.
  • DNS Servers - Specify a comma-separated list of DNS servers to be used to resolve the hostnames in the saved query supplied as a trigger (or devices that have been selected in the asset table).
    • If supplied, Axonius will use the specified DNS server to resolve the devices' hostnames. For each asset, the first response will be the one to be used.
    • If not supplied or if no response has been received from any of the specified DNS servers, the default DNS server will be used.
  • Use NBNS - Use the NetBIOS Name Service.
  • Registry keys to check for existence - Specify the registry keys that you want to check whether they exist. These values are stored in the 'Validated Registry Keys - Existing' or 'Validated Registry Keys - Not Existing' fields of the device depending whether they exist or not.
  • Registry keys to get key-value pairs - Enter Registry keys for which the system will search for the values on specific registries of the windows computer and stores them in a field called 'Validated Registry Keys - Existing Values' in the device.
  • Fetch software licenses information (default: false) - Select this option to fetch software licensing product information from each host. The results are presented in a list field called 'Software Licensing Product Information'.
  • Fetch Remote Desktop client access licensing information (default: false) - Select this option to fetch information from the Remote Desktop Client Access Licensing Server. This setting only works for RDS Licensing Server hosts. Refer to Activate the Remote Desktop Services license server to learn how to activate this on a host.
  • Fetch SQL Server License information - Set this option to search for Microsoft SQL Server license information on the machine’s registries and fetch it
  • Fetch installed software from Win32_Product class - Select this option to fetch data from the Win32_Product class.
  • Gateway Name - Select the Gateway through which to connect to perform the action.

For more details about other Enforcement Actions available, see Action Library.


Was this article helpful?