Product Documentation

Import and analyze settings

Jun 15, 2016

Use the Import and Analyze page of the Settings dialog box to customize the imports performed from the Direct Import tab of the Import Applications screen. To open the Settings dialog box, choose Edit > Settings.

Options:

Auto analyze – For retail licenses, application analysis begins immediately after applications are imported unless you clear this check box. For trial licenses, you must manually start an analysis. If multiple users import simultaneously, Citrix recommends that you clear this check box to prevent locks on the database.

Finger print override – Select this check box if you want AppDNA to consider each re-import of a desktop application to be a separate application. However, this has licensing implications because AppDNA licensing restricts the number of applications for which you can view reports. Clear this check box if you want a desktop application to be considered the same application on re-import if its fingerprint has not changed by more than 10%. This is the default behavior and means that if you modify a desktop application as part of the remediation process and then re-import it, it is generally considered to be the same application.

Server side queuing –Select this check box to enable queue processing on the server. This can increase the success of multiple simultaneous imports and analyses by adding the tasks to a first in first out queue on the server. This reduces the likelihood of database deadlocks and resource contention and makes AppDNA more responsive.

Simultaneous imports (1-3) – This controls the number of imports that take place simultaneously. The optimum value is dependent on your hardware configuration. If you increase the value of this setting and then find that imports fail with a "deadlock" error, decrease it. The default and generally recommended setting is 3.

Select all MSTs – Select this check box to automatically apply MST files to the MSI files during the import. This only applies when the MST and MSI files are stored in the same location. MST files are used to transform or manipulate MSI files. MST files are not relevant to non-MSI installation files.

Expand all MSTs – When you select an MSI file for import and there are MST files in the same directory, AppDNA puts a + to the left of the application's name in the Import Applications screen. When you click the +, AppDNA shows the associated MST files. Select this option to automatically show all MST files without needing to click the +.

Preserve log files – Select this check box to save log files. This can sometimes be useful for diagnostic purposes. Clear this check box if you do not want to save log files – for example, to save disk space.

SFT intermediate folder – When AppDNA imports .sft or .appv files, it unpacks them into an intermediate folder. To keep the extracted files, set the location of the intermediate folder here. If you do not specify a location, a temporary folder is used and it is cleared after each .sft and .appv import.

When AppDNA unpacks .sft and .appv files, it preserves their internal directory structure. This can sometimes lead to the maximum number of characters that Windows allows in a file path being exceeded, which will cause the import to fail. You can reduce the chance of this happening by setting the shortest possible file path here.

Validation profile (*.cub) – To perform ICE validation of MSI files during import, specify the location of the CUB files here. CUB files store the ICE validation rules.

Validation engine – To perform ICE validation of MSI files during import, specify the location of the package validation tool such as Msival2.exe.

Additional parameters – Specify any command line parameters for the ICE validation engine here. See http://msdn.microsoft.com/en-us/library/windows/desktop/aa370504(v=vs.85).aspx for information about the Msival2.exe parameters.

Perform ICE validation – Select this check box to perform Internal Consistency Evaluator (ICE) validation during the import process to detect potential problems with MSI files.