Specifications

Bankway Network Standards Guide - Distributed Terminal Server in Every Branch
This constitutes a trade secret of Fidelity National Information Services, Inc. 03/08 Research & Development
Page 56 of 63
This section describes how applications are integrated and run in a Windows Terminal Server
environment. Microsoft has developed a series of processes that allow applications not written
specifically for the Terminal Server environment to be executed successfully
Microsoft Windows Terminal Server differentiates between applications installed specifically for
the current user and applications that will be made available to all users. To separate these two
installation processes, Windows forces you to physically change the installation mode when
installing an application for all users. If applications are installed using the control panel’s
"Add/Remove Programs" icon, you will receive a prompt about the availability of the application.
When installing without the use of "Add/Remove Programs", the mode must be switched using
the command prompt and the following commands.
change user /execute
Sets the installation mode to run programs or to install for only the
current user. This is the default mode at system start-up.
change user /install
Sets the installation mode to install for all users.
change user /query
Displays the current installation mode.
While in the multi-user install mode, any registry changes made to the HKEY_LOCAL_USER
registry key will be replicated for all users.
Because many applications expect access to individual configuration files, such as .INI files,
Microsoft has designed a method of creating components for individual users. This is provided in
the form of compatibility scripts that are executed for every logon to the terminal server. These
scripts make sure that each user gets these user-specific configuration files.
When logging on, every user has their home drive mapped to a specified drive letter. This drive
letter then becomes the user’s root directory. If an application requires an .INI file in the
Windows directory, the compatibility script for that application would instead check for the
existence of the file in the user’s home directory. If the file is not present, the script creates the
directory and copies the .INI file. In this fashion, individual user settings can be maintained
separately. The home drive mapping is configured in the following script file.
Server 2003 - %SystemRoot%\Application Compatibility Scripts\RootDrv2.cmd
Where: %SystemRoot% = C:\WINDOWS
During the user logon process, the following scripts are executed in sequential order.