Windows Terminal Server

Windows Terminal Server

When using the Windows Terminal Server, suitable parameters must be set. The user settings are presented in the following steps.

1. Setting Data Execution Prevention (DEP) on Server

The terminal server after installing: WinXP SP2, Win Server 2003 SP1 or Windows Vista uses the Data Execution Prevention mechanism that disables running the ARES code in PANTHEON.

For more information, see the website http://en.wikipedia.org/wiki/Data_Execution_Prevention.

For this purpose, the AlwaysOn or OptOut (recommended) options must be set either in the operation system register or through the user interface: System | Advanced System Settings | Advanced tab | Settings | Data Execution Prevention.

In the register, the user sets the following value:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
Value Name: <DIR>\<APPNAME>.exe (npr: c:\program files\DataLab\Pantheon55_SQL.exe)
Value Data: DisableNXShowUI

In the Control Panel, the user opens Advanced System Settings, selects the Advanced tab and Settings.

On the Data Execution Prevention tab, the user marks: Enable DEP for all software services except selected ones..

The user clicks the Apply button.

WARNING After setting these values, the computer must be restarted.

2. Setting the Virtual Work Station Name

To ensure correct function of PANTHEON, a virtual name of the work station must be set in the terminal mode of the .ini file used to run PANTHEON.

The user sets the virtual name of the work station by setting the command line switch in the shortcut used to start PANTHEON in the .ini file:

"C:\Program Files\DataLab\Pantheon.exe" /INI="C:\Program Files\DataLab\dl.ini" /WN=moje_ime_postaje

work_station_name is a custom name that must be unique for each user.

Every terminal user must use their own unique shortcut to run PANTHEON.

For more information on command line checkboxes, see the chapter Command Line Parameters.

WARNING If the virtual name is not set, disruptions to function and errors may occur. This includes the incorrect creation of temporary tables, incorrect license verification, non-implementation of certain modules, etc.