VA001 - Missing Shortcuts

Description: The Windows Installer database is scanned for the presence of at least one shortcut.

Background: At least one shortcut should be present in the package as it is necessary to act as entry point for the virtualized application.

More Information: None available.

Manual Remediation: A shortcut can be created to an existing or dummy file in the package. The users have to be made aware that they will have to start the application through this shortcut to activate it.

VA002 - Drivers

Description: The Windows Installer database is scanned for the presence of drivers.

Background: Most drivers cannot be virtualized and will not work in the virtualized application.

More Information: None available.

Manual Remediation: The driver should be removed from the virtual packaage and be installed physically on the machine.

VA003 - Fonts

Description: The Windows Installer database is scanned for the presence of fonts in the File, Registry, and Font table.

Background: Fonts that are installed with a virtual application will only be available for that software. Issues may occur in case the font should also be available for other (physically installed) software.

More Information: None available.

Manual Remediation: The font should be removed from the virtual package and be installed physically on the machine.

VA004 - Custom Actions

Description: The Windows Installer database is scanned for the presence of Custom Actions.

Background: Custom Actions may contain operations that alter existing or add new resources (not being part of the standard MSI tables) to the system. As Custom Actions are discarded when converting the package into a virtual format, all changes made by them will not be part of the virtualized application which will cause the package to be incomplete.

More Information: None available.

Manual Remediation: None available.

VA005 - Conditions on Components

Description: The Windows Installer database is scanned for the presence of Conditions on Components.

Background: Components can contain a conditional statement that controls whether or not a component is installed. As Component Conditions are discarded when converting a package into a virtual format, the content of all components will be part of the virtualized application which may result in undesired content.

More Information: None available.

Manual Remediation: None available.

VA006 - Hardcoded shortcuts

Description: The Windows Installer database is scanned for the presence of hardcoded shortcuts.

Background: Shortcuts are used as entry points for the virtualized application. As the installation folder for virtual software may vary, these shortcuts should contain relative paths to the target, working directory, and arguments.

More Information: None available.

Manual Remediation: All hardcoded paths in the properties of the shortcut should be changed to relative paths.

VA007 - Shell extensions

Description: The Windows Installer database is scanned for the presence of shell extensions.

Background: If application contains shell extensions cannot be convert to virtual format.

More information: None available.

Manual Remediation: Please note that for App-V this rule can be ignored from version 5.0 SP2 onwards.

VA008 - App-V filename length limitation

Description: The length of the Windows installer database filename is checked. It should not exceed 56 characters.

Background: Microsoft App-V stores the name of the .sft file in the Name field of DBO.Packages table in the SQL database. This Name filed has a length limitation of 64 characters and is made up of the name of the .sft file followed by "_Package", thus limiting the name of the .sft file to 56 characters.

More Information: None available.

Manual Remediation: The name of the Windows Installer database file should be limited to 56 characters.

VA010 - Office Add-ins

Description: Scan the Registry table for existence of Office Add-ins

Background: Office add-ins are not supported and they will not work in virtual applications. To work properly, add-ins should be installed physically on the machine.

More Information: https://msdn.microsoft.com/en-us/library/aa371168%28v=vs.85%29.aspx

Manual Remediation: The Office Add-ins should be removed from the virtual package and be installed physically on the machine.

VA011 - Services

Description: The Windows Installer database is scanned for the presence of services with automatic Startup Type.

Background: Services with Startup Type equal to Automatic (boot services) are not supported for virtualization.

More Information: None available.

Manual Remediation: the Startup Type for each service should be changed from Automatic to Manual.

VA012 - RELS files

Description: Scan the file table for the existence of files with extension .rels.

Background: If an application contains an OPC relationship part (.rels) file, the Microsoft App-V 5.0 sequencer fails to package the application.

More Information: https://support.microsoft.com/en-us/kb/2843030

Manual Remediation: To work around the limitation, manually delete all relationship files from the package source folder prior to saving the package.

VA013 - Hosts file

Description: The Windows Installer database is scanned for the presence of hosts file.

Background: The packages that update the hosts file cannot be virtualized.

More Information: None available.

Manual Remediation: None available.

VA014 - Hard-coded Paths

Description: The Windows Installer database is scanned for the presence of hard-coded paths.

Background: Paths should be relative...

More Information: None available.

Manual Remediation: All hard-coded paths should be changed to relative paths.