You can directly import desktop applications for which an .msi, .appv, or .sft file is available.
If you have both a standard Windows installer (.msi) file and an App-V (.sft or .appv) package file, it is generally preferable to import the .msi. This is because the App-V package is prepared for the virtual environment and therefore does not include all of the application DNA for a native Windows environment. For example, it might omit information about drivers and registry settings. Therefore Citrix recommends that you import the .msi file if one is available.
To import applications:
You can add new imports while other application imports are in progress. Note: The Import button is available when the cursor highlights any application import which is not in progress. If your selection includes multiple applications where some import processes are in progress and others complete, then the Import button is disabled until all processing has completed.
Track the progress of the import in:
To cancel an import, click the Cancel button. If the import is canceled during client-side processing, the Canceled status displays once the MSI extraction is complete.
You can use .mst files with .msi files to transform or manipulate the installation package.
If an .mst file is available in the same location as the .msi file, you can choose to apply it during the import. To do this for all applications for which an .mst file is available, select the Select All MSTs check box.
Alternatively, you can select .mst files for specific applications. To do this, click the + to the left of the application and select the .mst file to apply.
Alternatively, you can click in the Group column to select a group for an individual application.
When a desktop application is first imported into AppDNA, its fingerprint is stored. The fingerprint is a combination of the application's product name, manufacturer's name, version number, and the number of files and registry entries it has. If the application is imported into AppDNA again, by default the application is considered the same if the fingerprint is the same or has not changed by more than 10%. This means that if you modify an application as part of the remediation process and then re-import it, it is generally considered the same application. Similarly, AppDNA generally considers new versions of an application to be the same application.
You can, however, change this behavior so that the application is always considered different even if there is no change in the fingerprint. To do this, select the Finger print override check box in Import and Analyze Settings. However, be aware that this has licensing implications because AppDNA licensing controls the number of applications for which you can view reports.
When you re-import an application from the same location, AppDNA shows the text in the Path column in bold to indicate that the application was previously imported from the same location.