The DSM Explorer › Software Folder › Definitions Folder › Virtual Application Images Folder › How to Create a New Virtual Application Image › Specify Recognition Information

Specify Recognition Information

Use the Recognition tab page to specify recognition parameters, or software signatures, used to identify the virtual application image when it is discovered on an agent. The asset management agent uses these parameters for discovering and monitoring virtual applications.

To specify recognition parameters automatically

1. Click Detect to automatically populate the recognition parameters.

   A standard Browse for Folders dialog appears.

2. Select a directory folder containing the virtual application image or a file used by the virtual application image in the case of VMware ThinApp images.
3. Click OK.

   The Recognition tab page is populated with the relevant parameters.

4. Modify the recognition parameters as required.

To specify recognition parameters manually

1. Enter the main file name of the virtual application image in the Filename field.

   For VMware ThinApp images, this will normally be a .dat or .exe file. If the VMware ThinApp application contains more than one file, you must enter the file name of the main data container, which is easily recognized as largest file in the set.

   For Microsoft App-V (formerly SoftGrid) images, this will normally be a .sft file.

2. Select an image type from the Image Type drop-down list. CA ITCM currently supports the following virtual application image types: ThinApp and App-V.
3. (Optional) Select the Match File Size Range option, and then enter the minimum and maximum file sizes in bytes of the main image file entered in Step 1 in the appropriate fields.

   Only if a discovered image's file size falls within this range will it be recognized as this virtual application image definition.

4. (Optional - ThinApp only) Select the Match Last Modified Date/Time Range option, and then enter the earliest and latest last modified dates and times of the ThinApp image file entered in Step 1.

   Only if a discovered image's last modified dates and times falls within this range will it be recognized as this virtual application image definition.

5. (Optional - ThinApp only) In the Related Executables list view, enter all files related to the specified ThinApp image that should be excluded from being potentially listed as "Unknown" when discovered during the asset scan. For example, enter all shortcut .exe files for the ThinApp package.

   Note: Each file should be entered on a separate line. Pressing the Enter key moves the cursor to the next line.

6. (Optional - App-V only) Select the Package GUID option, and then enter the App-V's package GUID in the following format where X can be any hexadecimal character (0-9, A-F): XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

   You can obtain this value from the MS App-V Sequencer. To ensure accurate signature matching, CA recommends that you specify this value.

7. (Optional - App-V only) Select the Version GUID option, and then enter the App-V's current version GUID in the following format where X can be any hexadecimal character (0-9, A-F): XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

   You can obtain this value from the MS App-V Sequencer. To distinguish between versions of streamed App-V packages, the version GUID must be entered.

Note: When streaming App-V packages to clients, the package GUID is used to identify which package to download. The latest package version available at the App-V streaming server is streamed to the client. Until the App-V package has been accessed by the client, the exact version of the package that will be streamed cannot be determined. In this case, the original package version will be detected, based on the file name in the package URL. Once the package is accessed by the client for the first time, the precise package version will be detected. If the package is deleted from the App-V client cache, the version information is lost until the package is accessed again. For this reason, CA recommends that you do not fundamentally change the contents of App-V packages between minor package updates. For example, when upgrading to a completely new version of packaged software, we recommend you create a new App-V package rather than updating an existing package.