Configuring AppLink

From ThinManager Knowledge Base
Jump to: navigation, search

ThinManager can control access to applications with the AppLink feature of Terminal Server Display Clients. This deploys a single application per session without a desktop, start button, or icons that would let the user launch undesired programs. AppLink is configured by default to keep the application running; if they close it, the application will re-open.
AppLink is configured on the Terminal Server Display Client Wizard.

Navigate through the wizard to the Terminal Server Display Client Options Page.

Display Client Wizard – Terminal Services Display Client Options
Display Client Wizard – Terminal Services Display Client Options

Select the Application Link checkbox. Other options can be selected in combination with AppLink.
Select the Next button to continue to the AppLink page of the Display Client Wizard.

Display Client Wizard – AppLink
Display Client Wizard – AppLink

Enter the path to the program you want to run in the Program Path and Filename field. This may require the use of quotation marks if there are spaces in the path name.
The Command Line Options field provides a space for command line options and switches. This field may not be required.
The Start in the following folder field is provided in case you need to specify the working directory for the program when using a relative path for the initial program. This field may not be required.
The Browse button will launch a Browse window that will allow the Program Path and Filename field to be filled in by ThinManager instead of typing the path manually.

Note: The AppLink Display Client may contain a single terminal server or may contain many terminal servers. If a Terminal Services Display Client contains several terminal servers, the path must be valid on all terminal servers. If different terminal servers have different paths to the desired program, write a batch file to open the program.

Note: If the Display Client is to be run on multiple platforms (i.e.: a thin client *and* with WinTMC and/or with iTMC), then a batch file is recommended to launch the application if it has a complex path. For example, if the Program Path and Filename is:

"c:\Program Files (x86)\HMI\HMI.exe c:\HMI"

This syntax may work well for a thin client, but not for WinTMC and/or iTMC. Therefore, a simple batch file should be created with the contents as:

start "" "c:\Program Files (x86)\HMI\HMI.exe c:\HMI"

Then the AppLink Program Path and Filename would point to the newly created batch file.

Personal tools