Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Launching an App-V virtualized application on a Remote Desktop Web Access server launches the wrong virtualized application

Launching an App-V virtualized application on a Remote Desktop Web Access server launches the wrong virtualized application

View products that this article applies to.

Symptoms

When users login to a Remote Desktop Session Host server using a Remote Desktop Connection, all of the Microsoft Application Virtualization (App-V) applications work properly, however when users launch the same App-V applications on a Remote Desktop Web Access server the wrong virtualized app is launched. For example, the users receive App-V application B when App-V application A is selected even though the icon and the application names are displayed correctly.

↑ Back to the top

Cause

When the RemoteApps are configured using the RemoteApp configuration wizard, an Alias parameter is configured automatically. Since sfttray.exe is the application for all App-V virtualized apps, once the 2nd App-V application is added, the Alias parameter cannot be same name as another application therefore the Wizard increments the file name with a (1), (2) etc. An example of this is below:


Server1
App Alias
==========
App1 (Sfttray)
App2 (Sfttray1)
App3 (Sfttray2)
App4 (Sfttray3)		Server2
App Alias
==========
App1 (Sfttray1)
App2 (Sfttray2)
App3 (Sfttray3)
App4 (Sfttray)		Server3
App Alias
==========
App1 (Sfttray3)
App2 (Sfttray2)
App3 (Sfttray1)
App4 (Sfttray)

You will notice that the Alias is different for each one of the applications on each server. For example, the Alias for App1 on Server 1 is Sfttray, on Server 2 it is Sfttray1, and on Server 3 it is Sftray3. This is the source of the problem as the Aliases need to be identical for each application on each server.

↑ Back to the top

Resolution

To resolve this issue, edit the RemoteApp parameters for the App-V application so that the Alias parameters are the same for each application across all Remote Desktop Session Host servers. It is recommended that the application name referenced after the /launch switch of the sfttray command be used for the Alias.

Example where the App-V launch commands are:

App1 -sfttray.exe /launch "App1 1.1.1.1"
App2 -sfttray.exe /launch "App2 1.1.1.1"
App3 -sfttray.exe /launch "App3 1.1.1.1"
App4 -sfttray.exe /launch "App4 1.1.1.1"

Change the App1,2,3,4 RemoteApp configurations as follows:

App                   Alias
================
App1              (Sfttray)
App2              (Sfttray1)
App3              (Sfttray2)
App4              (Sfttray3)

To:

App1              App1 1.1.1.1
App2              App2 1.1.1.1
App3              App3 1.1.1.1
App4              App4 1.1.1.1

Make this change on all Remote Desktop Session Host servers.

↑ Back to the top

More Information

The most common scenario in which this can happen is when you have multiple Remote Desktop Session Host servers and Remote Desktop Web Access servers that are load balanced. When the App-V applications are manually installed on each Remote Desktop Session Host server, they may or may not have not been installed in exactly the same order. Also, the Applications configured in the RemoteApp Program wizard may or may not have not been configured in exactly the same order on the 3 Remote Desktop Session Host servers, thus the Alias names may not be in sync and in the same order on each server.

Application Virtualization 4.6 for Windows Server 2008 R2 Remote Desktop Services - whitepaper -
http://blogs.technet.com/b/appv/archive/2010/05/27/the-app-v-4-6-for-rds-whitepaper-is-now-available.aspx

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2638538
Revision : 2
Created on : 3/27/2020
Published on : 3/27/2020
Exists online : False
Views : 407