Environment Variables in ThinManager

From ThinManager Knowledge Base
Jump to: navigation, search

Note: Windows per-user environment variables for initial applications are only valid in Windows Server 2003 and older operating systems.

Using Environment Variables in ThinManager

System environment variables can be used in the Application Link path name. For example, you can substitute %WINDIR% for the explicit path of the Windows folder (such as C:\Windows) (Windows environment variables) or #TERMINALNAME# for the terminal's name (such as HMI01) (ThinManager environment variables). Starting with Server 2008, you cannot use Microsoft Windows per-user environment variables.

ThinManager Environment Variables

The above Display Client, when running on a terminal named HMI01, will launch Notepad with the document stored at C:\docs\HMI01.txt

ThinManager Specific Environment Variables

ThinManager specific environment variables was introduced in the initial release of ThinManager 8.0.

Environment Variable Evaluates To
#TERMINALNAME# name of the terminal
#MODEL# model of the terminal
#WINDOWUSERNAME# Windows username for Display Client
#TERMSECUREUSERNAME# TermSecure username for the logged in user
#DISPLAYCLIENTNAME# Display Client name
#LOCATIONNAME# Relevance Location name

Custom Variables

Custom ThinManager environment variables were introduced in the initial release of ThinManager 8.1.

Users may now define their own custom variables for Terminals, TermSecure Users, and Relevance Locations. These environment variables can be used the same way as the above ThinManager specific environment variables and also may be accessed through the TermMon ActiveX Control. The value of the variable can either be shown or hidden.

ThinManager Custom Environment Variables

For example, using #VISIBLE# in a Display Client path will cause ThinManager to substitute "Value" into the path. C:/#VISIBLE#.txt will result in C:/Value.txt.