Adding Packages from a Local Machine or Network

AdminStudio 2020 | 19.0 | Automated Application Converter

To add packages from a a local machine or network to Automated Application Converter so that you can convert them to virtual applications, perform the following steps:

To select packages from a local machine or network:

1. Launch the Automated Application Converter.
2. Add one or more virtual machines, as described in Adding Virtual Machines Using the Virtual Machine Import Wizard.
3. Open the Packages tab.
4. Click Add Packages. The Package Import Wizard opens.
5. Click Next. The Select Package Source panel opens.
6. Select Browse local machine and network and click Next. The Select Packages panel opens with no packages listed.
7. If you want to select one package to add, perform the following steps:
a. Click Browse Files. The Select Package Installation File dialog box opens, prompting you to select the package you want to convert.
b. Select the installation file (.msi or .exe) or installation script (*.vbs, *.bat, *.cmd, or *.ps1) you want to convert and click Open.The Automated Application Converter adds the selected package to the list on the Select Packages panel.

Note:You can use installation scripts to run more complex installation scenarios.

If you want to select a directory of packages to add, perform the following steps:

a. Click Browse Folders. The Browse for Folder dialog box opens, prompting you to select the directory containing the packages you want to convert.
b. Select the directory that contains the installation files (.msi or .exe) and/or installation scripts (*.vbs, *.bat, *.cmd, or *.ps1) you want to convert and click Open. The Automated Application Converter searches the selected directory and its subdirectories to locate the installation files and/or scripts and adds them to the list on the Select Packages panel.

Important:The Automated Application Converter uses specific rules to determine which packages in the selected directory and its subdirectories would be added to the list on the Select Packages panel, and which of those files are automatically selected. See Automated Application Converter’s Selection Rules When Adding Packages from a Directory for more information.

8. On the Select Packages panel, click Next. The Selected Package List panel opens.
9. On the Selected Package List panel, an icon in the Virtualization Readiness column identifies whether the package requires repackaging prior to conversion to a virtual application:

Icon

Meaning

Description

Ready

Package is ready to virtualize; no repackaging is required.

Note:If a Windows Installer package does not contain any custom actions, conditional components, or unsupported tables, repackaging prior to virtualization is not required.

An example of an unsupported table is the IniFile table, which changes files on the target machine in ways that cannot be statically determined.

Requires repackaging

Package must be repackaged before it can be successfully virtualized.

Virtualization not supported

Automated Application Converter has determined that virtualization is not supported due to one of the following issues:

Package contains DLL surrogates.
Package installs boot services.
Package contains OS integrated files.
Package relies on a system-level driver.
Package’s .sft file name is over 56 characters in length.

Important:Packages with a status of Virtualization not supported will not be virtualized. In order to virtualize the package, you must first override the status and change it to Ready to Virtualize or Requires Repackaging.

Note:For more information, see Application Virtualization Compatibility Tests.

Virtualization not recommended

Automated Application Converter has determined that this package is not recommended for virtualization due to one of the following issues:

Package does not contain a shortcut.
Package includes a custom shell extension.
Package utilizes ClickOnce technology.

Note:For more information, see Application Virtualization Compatibility Tests.

Unknown

The Automated Application Converter was unable to determine whether this package is ready to be virtualized directly or whether it requires repackaging.

Note:If you want to override this setting, click in the Virtualization Readiness column and make a selection from the list.

10. Make sure that the packages that you want to convert are selected and click Next. The Package Import Wizard Complete panel opens.
11. Click Finish to close the wizard and add the selected packages to the project.
12. To proceed with the conversion, see Performing a Conversion Using the Application Conversion Wizard.

See Also