Windows Terminal server

Windows Terminal server

When using Windows Terminal Server, the appropriate parameters must be set. We will show you the user settings in the following steps.

1. Setting up Data Execution Prevention (DEP) on the server

Terminal Server after installation: WinXP SP2, Win Server 2003 SP1 or Windows Vista uses a Data Execution Prevention mechanism that disables the execution of ARES code in PANTHEON.

For more information, see en.wikipedia.org/wiki/Data_Execution_Prevention.

To do this, the AlwaysOn (less recommended) or OptOut (more recommended) options must be set either in the operating system registry or via the user interface: Ssystem|Advanced system settings|Additional tab | Settings | Data Implementation Override.

The user sets the following value in the registry:

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

In the Control Panel aboutfor Advanced system settings, select the Additional tab and Settings. In theData Execution Prevention check: Enable DEP for all software services except the selected ones.

Click the Use button.

WARNING After setting these values, it is mandatory to restart the computer.

2. Setting the virtual workstation name

To ensure that PANTHEON works correctly, you need to set a virtual workstation name in the .INI file used to start PANTHEON in terminal mode.

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

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

workstation_name is an arbitrary name, which must be different for each user.

Each terminal user must use their own shortcut to start PANTHEON.

For more information on command line switchers, see Command Line Parameters.

WARNING If you do not set a virtual name, you may experience malfunctions or malfunctions. From incorrect creation of temporary tables, incorrect licence checking, failure to implement certain modules, etc.