Auto FE Updater

Terminal Server RemoteApp

To setup the Auto FE Updater to run on a terminal server read the overview on the Terminal Server/Citrix page.   This page focuses on Terminal Server RemoteApp functionality.   For the system administrator information can be found at TS RemoteApp Step-by-Step Guide

Setup the StartMDB on your file server and from the Terminal Server run the Auto FE Updater wizard and do whatever updates you require to get your application running on Terminal Server in Terminal Server mode.  

You will also want to create a server shortcut as we will need the command-line argument of the shortcut target property in the RemoteApp.   Alternatively you can create Server Shortcut CMD file which will also have the necessary command line arguments in it.

You don't want to create any desktop, quick launch or program menu shortcuts as they aren't needed for RemoteApp.  The RDP or installer file the system administrator creates is the equivalent.  You may also get some very interesting messages if you do so.  Therefore if you also have regular Terminal Server users who will be using your app as well as RemoteApp users then you should create two separate configuration files.   You can copy a configuration file by clicking on a configuration file, selecting File on the menu and then the Copy ... menu item.

From either the server shortcut target parameter or the CMD file extract the command line argument from /cmd to the end of the line as per the following screen shots.  Note that my example is likely a lot shorter then a typical network setup which would typically contain \\server name\share name\folder name\Auto FE Updater\.

You will want to give the above command-line argument to the system administrator.

Terminal Server RemoteApp setup

The following must be done by a system administrator.

Create the RemoteApp browsing to the StartMDB.exe on the file server.   In the Command-line arguments place the above highlighted command line.  

You will very likely want to change the RemoteApp program name from StartMDB.exe to something more meaningful such as your application name.  In this example I used Granite Fleet Manager.

In my admittedly brief testing you do not need change the Alias to be unique.   The wording on the Technet page states "The alias is a unique identifier for the program that defaults to the program's file name (without the extension). We recommend that you do not change this name."

Changing the Icon didn't seem to have any purpose as the RDP file doesn't use that icon.    Maybe the TS Web Access uses that but I didn't test that option.

Finally you will likely want the administrator to create an RDP file which can then be distributed to your RemoteApp users.   Or use the TS Web Access option.