Article ID: 186499 - View products that this article applies to.
This article discusses the registry settings that can be used to modify application behavior on a Terminal Server computer.
For more information on MSI (Microsoft Windows Installer) Behavior based on Terminal Server Versions 2003 and later, go to KB 2002357
Controlling Application Execution in Execute ModeSeveral compatibility bits can be set for an application, registry path, or .ini file to change how a Terminal Server computer handles the merging of application initialization data when a session is in execute mode. These compatibility bits are set in the registry under the following subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\CompatibilityThere are three separate keys for applications, .ini files, and registry entries under this registry path.
The default settings work for most applications, but they can be further tuned by using the following compatibility bits.
WARNING: These compatibility bits should only be changed if an application is not working properly.
The first set of compatibility bits indicates the version of the application that the settings are for. Not all combinations are useful (for example, an MS-DOS application does make registry calls). Because the path to the file is not specified and multiple applications may use the same file name (for example, Setup.exe and Install.exe are now regularly used for installation programs), specify the application type to help make sure that the compatibility settings do not affect other applications with the same file name.
To determine the String Value, add the values of the bits that you want to set. For example, to return the user name instead of the computer name for both 16-bit and 32-bit versions of Myapp.exe, create a subkey in the registry by performing the following steps.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
ApplicationsThe following compatibility bits affect the application when it is running. They are located in the following registry subkey (where Appname is the name of the application's executable file):
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\Appname
Use the "Disable registry mapping for this application" bit to retain only one global copy of the registry variables that are used by the application.
If the "Do not substitute user Windows directory" bit is set, it retains the SystemRoot directory for GetWindowsDirectory API calls. If this bit is not set, all paths to the Windows directory are replaced with the path to the user's Windows directory.
.Ini FilesThe following compatibility bits control .ini file propagation. They are located in the following registry subkey (where Inifile is the name of the .ini file):
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\IniFiles\Inifile
If the "Do not substitute user Windows directory" bit is set, it retains the SystemRoot directory for file paths in the .ini file when the system master version of the .ini file is copied to the user's Windows directory. If this bit is not set, it replaces all paths to the Windows directory with the path to the user's Windows directory.
Registry PathsThe following compatibility bits control registry propagation. They are located in the following registry subkey (where PathName is the registry path under the key HKEY_CURRENT_USER\Software):
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\RegistryEntries\PathName
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/186514/ )Terminal Server does not support sentinel devices
Article ID: 186499 - Last Review: April 27, 2015 - Revision: 5.0