Standalone Windows scanning tool

In certain applications, computer and server assets are located on systems that typically cannot be reached by BMC Discovery, either because of network security or because the systems are on an isolated network.

The standalone Windows scanning tool enables you to perform discovery on these standalone systems. The tool gathers data from Windows computers that are not connected to a network and creates scanner files with the discovered data.

The standalone Windows scanning tool complements the equivalent UNIX scanner scripts.

Related topics

Windows-Hosts

Loading a scanner file onto the appliance

Standalone-UNIX-scanning

This functionality does not permit interactive running of patterns to gather the full depth of data that a Windows proxy or Outpost provides; however, it enables BMC Discovery to contain data about hosts that would otherwise be unreachable and to synchronize this information to BMC CMDB. After the tool is run on the target host, the collected data must be manually uploaded to BMC Discovery.

The standalone Windows scanning tool is only supported on 64-bit versions of Windows. 

Warning

The standalone Windows scanner can be used to manually collect a limited set of information from a Windows host. The scanner is designed to be used solely on isolated systems or networks. It is not equivalent to a Windows proxy or Outpost, because it collects only basic host, process, and package information that can be obtained by WMI queries, not additional data such as NIC registry information (for NIC discovery).

Accessing and downloading the tool

The Windows scanning tool is a .zip archive file that can be extracted onto the target system or onto some form of removable storage (such as a USB drive). The .zip archive file contains everything you need to scan the Windows system; no connection to BMC Discovery is required.
To access and download the file:

  1. From the main menu, select Manage > Discovery Tools.

    windows_standalone_scan_tool_2008.png

  2. In the Standalone Windows Scanner section, click Download the Standalone Windows Scanner archive to download a .zip file.
  3. Extract the .zip file to a directory on a writable a USB flash drive or similar removable media.

Supported platforms

The standalone Windows scanning tool is supported on the following 64 bit versions of Windows:

  • Windows Server 2022
  • Windows Server 2019 version 1809
  • Windows Server 2016 version 1607
  • Windows Server 2012 R2 version 6.3
  • Windows 10 x64 version 1909
  • Windows 7 x64 SP1 version 6.1 
  • Windows Server 2012 version 6.2 * 
  • Windows Server 2008 R2 SP1 x64 version 6.1 *
  • Windows Server 2008 SP2 x64 version 6.0 *
  • Windows 8.1 x64 version 6.3 *
  • Windows 8 x64 version 6.2 *

In testing, the starred * versions required the Microsoft Visual C++ 2015 run-time DLLs to be installed.

Using the tool

Note

The Windows scanning tool requires the  Microsoft Visual C++ 2015 run-time DLLs. The run-time DLLs are usually installed on the operating system, but on a minimal or custom Windows installation, you might need to manually install them. To do so, use the vcredist_x64.exe installer that is included in the standalone Windows scanner .zip file.

The standalone Windows scanning tool runs as a portable console application directly from an external flash drive.
To use the tool:

  1. Insert the USB flash drive into the host system and explore the contents.
  2. If necessary, change the command options.
    For example, it is recommended that you select a target IP address, if known, to avoid the possibility of overlapping IP addresses.

  3. Double-click the tw_windows_scanner.exe file.
    A command window opens, and the tool begins collecting data.
    The following example output lists the informational messages the tool displays during data collection:

    U:> tw_windows_scanner
    Output file is results\192.168.1.1.scan
    Collecting Host Information ... DONE
    Collecting Interface Information ... DONE
    Collecting Process Information ... DONE
    Collecting Service Information ... DONE
    Collecting File System Information ... DONE
    Collecting Package Information ... DONE

Changing the command options

By default, the scan files are named based on the IP address of the Windows system (the lowest selected by the tool, after it ignores the localhost 127.0.0.1 address). The system does not overwrite existing scan files unless you change the options shown in the following table.

Changing the IP address to be scanned

In certain cases, the IP address of the Windows system (the lowest selected by the tool, after it ignores the localhost 127.0.0.1 address) might not be correct (for example, a VPN connection). Although these occurrences are uncommon, the tool will display an error message and exit. To help prevent these occurrences, it might be necessary to explicitly specify the IP address you want to use. To do so, run the tool and use the --target IPADDR option to set the target system.

It is also possible to scan other sytems using this option, as long as your user account has the required privileges (typically Administrator privileges). Setting the IP address to a specific target is especially useful for scanning an isolated subnet, because you would need only to insert the tool into one computer to collect data from all of them.

Uploading the data to the appliance

After you have collected the data, upload it to the appliance by using the SCP utility to transfer the files to the appliance as the upload user.

For more information about uploading scanner files to an appliance, see Loading a scanner file onto the appliance.

After the data is uploaded, it is processed by BMC Discovery. For more information about scanner files, see Standalone-UNIX-scanning. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*