Detect Software on a 64-bit OS Using Both 32-bit and 64-bit Registry

Configuring Asset Management › Custom Software Signatures › Additional Information on Intellisigs › Detect Software on a 64-bit OS Using Both 32-bit and 64-bit Registry

Detect Software on a 64-bit OS Using Both 32-bit and 64-bit Registry

You can specify the architecture value of a registry when creating custom traditional signatures in DSM Explorer for both registry and file entries. The specified value checks that a binary is built for the specified Windows architecture.

Follow these steps:

Navigate to DSM Explorer, Software, Definitions, software category, Release of software category, Properties, Recognition, Advanced, Registry.
Select any one of the following values in the Architecture drop-down box for a 64-bit OS:

32

Triggers a search in the 32-bit registry hives.

64

Triggers a search in the 64-bit registry hives.

Note: If you change the OS group type to UNIX, the Architecture drop-down box is disabled.

Set Default Timeout for Intellisigs

The default timeout of Intellisigs helps ensure that faulty Intellisigs do not run indefinitely on a computer. You can define a default timeout value for all the Intellisig scripts that are executed on a computer or for a specific Intellisig. You can apply a longer default time to agents where the load is high, for example, database servers, and where Intellisigs require extra time to complete. For desktop computers, where the load is low, you can configure a lower timeout value.

Follow these steps:

Navigate to DSM, Agent, Asset Management.
Define a value for the following parameter:

IntellisigDefaultExecutionTimeout

Specifies the default timeout value in minutes.

Default: 5

Note: When you create an Intellisig, set its timeout value to default. This action helps ensure that the agent applies the configured default timeout. If the Intellisig has a timeout value greater than zero, the specified value is enforced when the Intellisig is run.

intellisigcmd - Command Line Tool

intellisigcmd is a command line tool for Intellisigs. This tool has the following format:

intellisigcmd <cmd> param1=value1 param2=value2 ... [<DB_Credentials>]

cmd

Specifies the import, export, or genuuid command.

DB_credentials

Specifies the database credentials of the MDB. By default, the credentials are retrieved from the comstore.

Use the following sample format to specify the DB credentials:

Example: SQLServer DB Credentials format

dbvendor=mssql dbhost=myhost dbname=mdb dbuser=ca_itrm dbpassword=mypwd dbinstance=inst

Example: Oracle DB Credentials format

dbvendor=oracle dbhost=myhost dbname=orcl dbuser=ca_itrm dbpassword=mypwd dbinstance=1521

intellisigcmd export—Export Intellisigs

The intellisigcmd export command lets you export Intellisigs.You can either use the DSM Explorer or use the command to export Intellisigs. For more information about using DSM Explorer, see Export Intellisigs

This command has the following format:

intellisigcmd export file=<export name> [type=xml|zip] [platform=all|windows|unix]

export name

Specifies the name of the Intellisig XML or zip file that you want to export. If you do not provide the file extension, and the type is xml, the command creates a folder with the supplied name.

type

Specifies whether you want to export an XML or zip file. If you do not include the type parameter, the command assumes the export type depending on the export file extension.

Valid values: xml, zip

platform

Specifies the platform to determine which Intellisigs are exported.

Valid values: all, windows, unix

Default: all

intellisigcmd import—Import Intellisigs

The intellisigcmd import command lets you import Intellisigs.You can either use the DSM Explorer or use the command to import Intellisigs. For more information about using DSM Explorer, see Import Intellisigs.

This command has the following format:

intellisigcmd import [file=<import source>] [type=xml|zip] [mode=replace|mergenew|mergeall] [updateactive=yes|no] [delete=yes|no]

import source

Specifies the name of the XML or zip file to which you want to import the Intellisig. If you do not provide the file extension, the command assumes the file extension depending on the type.

Note: If you want to import to an XML file, verify that the supporting directories exist in the same folder as the XML file.

type

Specifies whether you want to import as XML or zip file. If you do not include this parameter, the command assumes the import type depending on the import file extension.

Valid values: xml, zip

mode

Specifies the import mode. Following import modes are supported:

Default: mergenew

replace: Replaces existing definitions with the definition being imported. Existing definitions are lost.
mergenew: Appends new Intellisig versions to the definitions on the manager. Existing definitions are not modified.
mergeall: Appends new Intellisig versions and updates the existing definitions that are included in the import file. Intellig versions that are not defined in the import files are not modified.

updateactive

Specifies whether active Intellisig versions can be updated during the import.

Valid values: Yes, Y, true, 1 or No, N, false, 0

Default: Yes

delete

Specifies whether you want to delete Intellisigs before the import. If you do not include the delete switch, none of the Intellisigs are deleted before import.

Default: No

intellisigcmd genuuid—Generate UUIDs

The intellisigcmd genuuid command lets you generate unique UUIDs which you can use when creating custom Intellisigs.

This command has the following format:

intellisigcmd genuuid [num=<count>]

num: Specifies the number of UUIDs to be generated. If you do not specify this parameter, a single UUID is generated. Otherwise, <count> UUIDs are generated.
Valid Values: 1 to 1000