Deploying App-V packages

Deploy the App-V package in stand-alone mode to endpoints with the App-V client installed.

A complete App-V package includes the following files:

  • An .sft file, which contains the data of the sequenced application.
  • An .osd file for each application in the App-V package.
  • A manifest.xml file, which contains information about the entire App-V package.
  • Icon files used to display the application on the endpoint.

If these files are packaged together, the Software Distribution dashboard generates a default installation command to deploy the App-V package in stand-alone mode (without streaming servers) to endpoints with the App-V client installed.

The App-V Sequencer might also generate an .msi file. This file can be used to deploy and install the package with the Software Distribution dashboard if the following conditions are met:
  • The MSI is accompanied by all other files in the App-V package, as previously described.
  • The App-V client is already installed on the endpoint.
  • The App-V client has the "AllowIndependentFileStreaming" setting enabled.
  • If App-V runs in a stand-alone configuration (no streaming server), the App-V client has the "RequireAuthorizationIfCached" setting set to 0. Otherwise, the application installs, but fails when the App-V client fails to contact the streaming server.

These conditions are tested by the task relevance. However, you must build a package in stand-alone mode before it can be deployed.