How to publish an App-V-enabled application in Citrix XenApp

, , , ,

Here is a guide on how to publish an App-V-enabled application in a Citrix XenApp environment.

To publish an App-V-enabled application in Citrix XenApp, follow these steps:

  1. Publish Sfttray.exe or publish Sftrun.exe.
  2. Publish the .OSD file.
  3. Publish the application name followed by a percent sign and then an asterisk (%*) or publish the application name and version followed by a percent sign and then an asterisk.

    Note A percent sign and then an asterisk are required in order to pass parameters to the executable that is specified in the FILENAME attribute of the .OSD file.

To hide the App-V Client from the notification area, use one of the following options.

Collapse this tableExpand this table
Version  
Option Description
Sfttray.exe Version 4 and later versions /hide The /hide command-line option was added in Sfttray.exe Version 4 and later versions. The Sftrun.exe executable was removed in Sfttray.exe Version 4 and later versions.
Sftrun.exe Version 3 and later versions The Sftrun.exe executable does not display the App-V Client in the notification area.

In XenApp XP FR-2, you can publish the .OSD file instead of Sfttray.exe or Sftrun.exe. When the .OSD file runs, the .OSD file uses Sfttray.exe or Sftrun.exe, based on the executable that the .OSD file is configured to use.

Note By default, .OSD files are configured to use Sftrun.exe.

The following table describes several examples of how to publish App-V-enabled applications.

Collapse this tableExpand this table
Example Description
PATH\sfttray.exe /hide /launch “Default App-V Application” [%*] The SOFTPKG NAME from the .OSD file. The name is case sensitive.
PATH\sftrun.exe “Default App-V Application 1.0” [%*] The SOFTPKG NAME and VERSION from the .OSD file. The name and version are case sensitive.
PATH\sftrun.exe “M:\App-V\DefaultApp.osd” [%*] The local or mapped drive to the .OSD file.
PATH\sftrun.exe “\\SERVER NAME\SHARE NAME\DefaultApp.osd” [%*] The Universal Naming Convention (UNC) path of the .OSD file.
PATH\sftrun.exe “https://SERVER NAME/SHARE NAME/DefaultApp.osd” [%*] HTTP path of the .OSD file.

Use the SOFTPKG NAME XML attribute and the VERSION XML attribute from the .OSD file. SOFTPKG NAME and VERSION are case sensitive. If you do not use the correct case, you will receive error code 04-00000A09.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

930631 (https://support.microsoft.com/kb/930631/ ) SoftGrid Client “Error code: xxxxxx-xxxxxx04-00000A09”

If the .OSD file exists in the M:\App-V directory on the App-V Client system when you publish the App-V-enabled application, the .OSD file is copied to the following folder:

%AllUsersProfile%\Documents\App-V Client\OSD Cache

Note M:\App-V is an example. M:\App-V is not an actual path that the product uses.

The .OSD file is used to publish the App-V-enabled application.

If the App-V Client is configured to update when you log on, the .OSD file that the App-V Management Console publishes is copied to the following folder:

%AllUsersProfile%\Documents\App-V Client\OSD Cache

When the .OSD file is copied to this folder, it overwrites the earlier version of the .OSD file. If the new .OSD file differs from the earlier version of the .OSD file, the App-V-enabled application may not be published.

To continue reading and see all the details check out the Knowledge Base article below:

KB931576 – How to publish an App-V-enabled application in Citrix XenApp

Related Posts