server=192.168.1.1
server=ts1.local
server=ts3.local:4000

server=vnc:192.168.1.5
server=vnc:tsx3.local:5000
server=rdweb:192.168.1.1,pt-br
server=password:rdweblocal

server=192.168.1.1,NLA

server=192.168.1.6;192.168.1.7;
server=tsx2.local,192.168.1.11:5000

server=--new--

server=192.168.1.1,--new--

application = chrome

application = vlc

application = shutdown

application = reboot

connection
server=192.168.1.1
displayName=RDP Connection
connection
application=shutdown
displayName=Turn off the computer

autostart_delay = 60

Automatically starts connection in 60 seconds (value specified in autostart_delay= option), if user won't press any keys and won't move mouse.

1. Definite values. The values you won't set user will have to specify in login window. Parameters user and domain are used:

   user = vasyapupkin
   domain = MYDOMAIN

   Also you can specify password:

   user = petja:password

2. Selection from menu.User can select login parameters from menu. Possible values for login parameters:

   DOMAIN\user[display_name]:password
   DOMAIN\user:password
   user[display_name]:password
   user:password
   DOMAIN\user[display_name]
   DOMAIN\user
   user

   display_name - is the to display in menu. When display_name is not specified user name is displayed in menu. These blocks are separated by semicolons. For example, this line creates menu with 5 items (users vasja and peter from DOMAIN2, basil's password is 'joke', john's password is '1'):

   user = DOMAIN2asil[Basil Washington]:joke;DOMAIN2\peter;john:1;july;Guest;--new--

   Keyword --new-- tells terminal to leave username empty. You can create as many items as can be placed on the screen. Terminal automatically shows them in columns.

user = vasya; peter; john; --only-listed--

shell = c:\windows\system32\cmd.exe

shell = C:\Program Files\Microsoft Office\Office10\winword.exe "c:\temp\document 1.doc"

By default Windows Server restricts running arbitrary programs. To make shell work you should add this program into RemoteApp Manager (remoteprograms.msc) list.

Another way: in policied you may allow to run arbitrary program. Run gpedit.msc, Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Connections, Allow remote start of unlisted programs.

To make sure that server is configured to sun needed program, create on Windows computer test.rdp file containing one line:

alternate shell:s:c:\windows\system32\calc.exe

Start this file in Windows. mstsc.exe will start and try to execute specified program. If instead of calculator you'll receive error, configure Windows Server as mentioned above.

shell = ||RMySuperRemoteApp

directory = c:\windows\temp

keyboard parameter determines default keyboard language in "Windows login" window and keyboard layout in RDP session. This parameter works only inside RDP session in Windows interface. Keyboard for login and password dialogs in WTware interface and for local Chromium is determined by language parameter. Keyboard for VNC client is determined by vncclient_keyboard parameter.

Default value is english layout ("en-us"), also you can set german:

keyboard = de

Or any other from listed below:

Also US International layboard layout may be specified, it grave in a different way:

keyboard = en-us-int

keyboard = pt-br-int

To turn on Japan IME layout set in configuration file:

keyboard = ja-ime

keyboard = 0xb0060409

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Keyboard Layouts

numlock = off

graphic = abcdefg

graphic = a

Windows 2003 Server shows desktop wallpaper only if you set to "Disabled": Start > Run > gpedit.msc > Computer configuration > Administrative templates > Windows components> Terminal services > Enforce removal of remote desktop wallpaper.

graphic = disable-gfx

graphic = disable-h264-fullscreen
graphic = disable-h264-window

graphic = disable-h264-hardware

graphic = a, disable-h264-fullscreen, disable-h264-window

Remote Desktop Gateway. Will be done in the next version.

You may connect to Hyper-V, RDP virtual machine console by VMBus. 2179 port is used. In Hyper-V server options should be enabled Enhanced Session Mode.

Virtual machine VM ID you may see from command line on Hyper-V server, run this command:

Get-VM | select Name,Id

Copy VM ID into WTware configuration file:

vmconnect = c4355813-ac42-4f09-bb6e-eadf9c792cbe

Without domain connection to Hyper-V console won't work. User, that connects to Hyper-V consile, must be in Hyper-V Administrators group.

Terminal resolution must be exactly the same as virtual machine resolution. WTware without license is not able to connect to Hyper-V console because of banner, that reduces screen width. You may contact WTware licensing service and ask for license to test connection to Hyper-V console.

You may test connection to Hyper-V console using mstsc.exe. Create text file with these three lines:

full address:s:192.168.1.1
pcb:s:c4355813-ac42-4f09-bb6e-eadf9c792cbe
server port:i:2179

Specify correct server IP and VM ID. Save with extension .rdp and run. mstsc.exe should run. If mstsc.exe won't connect you should configure Hyper-V server correctly.

loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.NameSC

loadbalanceinfo = tsv://MS Terminal Services Plugin.1.NameSC

rdpcompression = on

scale_factor = 125

The scale factor (as a percentage) applied to Windows Desktop Applications. Possible values: 100 (default), 125, 150.

In order to set VNC client keyboard layout specify vncclient_keyboard. RDP client keyboard layout is set by keyboard option. Keyboard layout for WTware login dialogue and for local Chromium is set by language option.

By default WTware sends keys scan-codes. It works for VNC server, embedded into VMware Player and VMware Workstation. For VNC servers, that you install on Windows (UltraVNC, TightVNC), symbols, not scan-codes, should be sent. Num Lock should work with this setting:

vncclient_keyboard = en

chrome_url=http://wtware.com/doc.html http://wtware.com/logs.html

chrome_mode = window

chrome_mode = kiosk

chrome_mode = kiosk-nopointer

chrome_language = nl

chrome_profile=empty

chrome_pac=http://192.168.1.1/proxy.pac

chrome_proxy=192.168.1.1:3128
chrome_proxy="https=proxy1:80;http=socks4://baz:1080"

chrome_share=\\10.1.2.3\sharename

chrome_share=\\10.1.2.3\sharename, user vasja, password 123

chrome_share=\\10.1.2.3\sharename, ro

chrome_share=\\10.1.2.3\sharename, vers 1.0

chrome_camera=on

vlc_cmdline=-I dummy rtsp://10.1.1.32:8556/6

vlc_files=background.jpg,vlm.txt

vlc_restart=4

vlc_timeout=off

One of terminal server settings: in group policy (Start -> Run -> gpedit.msc) goto Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection and specify policy "Do not allow drive redirection" to "Disabled".

disk = cdrom

disk = usb

disk = usb(r/o)

disk = cdrom;usb(r/o)

shared_disk = cdrom

shared_disk = usb

shared_disk = usb(r/o)

shared_disk = cdrom;usb(r/o)

There are four ways of using printer that is connected to terminal. They are managed by printer=, rdp_printer=, vhusb= and usb= parameters. Select the most suitable for you and use it. For more details read article about printers.

Possible parameter values:

printer = lpt1

printer = usb

printer = usb(1234:abcd), usb(5678:cdef)

printer = usb(delay 300)

printer = com1

printer = com1(38400)

Terminal with attached printer should have fixed IP address. For more details about how to make Microsoft DHCP to give fixed terminals addresses see this article. About printer drivers installation on the server read at this article.

How to print from DOS on terminal read here

WTware terminal emulates HP JetDirect hardware print-server (hardware print-server is a small box, that connects computer network and printer). With WTware terminal:

• work all printers able to work with hardware print-server HP JetDirect (as well as with any other print-server, all hardware print-servers are HP JetDirect copies),
• work all printers which drivers are included into Window distributive,
• work all printers able to print from DOS without additional drivers,
• don't work so called Win-printers. Some of win-printers: HP 700c, 820c, 1000c, 3300c, 3400c, DJ 820cxi, LJ 3100; Canon LBP-250/810/1110/1120/1210/2410; Epson LP1300,EPL 5800/2050+/6200L, C900; Lexmark X5150;Dell A920/940/960, J740; Minolta 1350W/1250W/2300W.

Up to 4 printers can work on the terminal. Blocks containing each printer data are separated by semicolons. 2nd printer uses port 9101, 3rd printer uses port 9102 and 4th printer uses port 9103. If you connect more than one printers of the same type (lpt1 and lpt2, or usb and usb), then check experimentally physical naming order by printing test pages.

printer  = lpt1;lpt2;usb;com1(38400)

To turn on printer debug information logging specify in configuration file:

printer = usb, debug

Send full terminal log to [email protected]. In this mode a lot of debug messages will be saved into terminal log. Turn on only when needed.

There are four ways of using printer that is connected to terminal. They are managed by printer, rdp_printer, vhusb= and usb= parameters. Select the most suitable for you and use it. For more details read article about printers.

rdp_printer=HP LaserJet 1020

clienthostname=w*MAC

rdp_printer=HP LaserJet 1020:usb 03f0:2b17

rdp_printer=auto

rdp_printer=TSC TDP-225:com1

rdp_printer=HP LaserJet 400 MFP M425dn:tcp 192.168.1.50:9100

rdp_printer=HP LaserJet 400 MFP M425dn [Printer at reception]:tcp 192.168.1.50:9100

rdp_printer=HP LaserJet 1020:usb 03f0:2b17, HP LaserJet 1022:usb 03f0:2c17, TSC TDP-225:com1, HP LaserJet 400 MFP M425dn:tcp 192.168.1.50:9100

VirtualHere License:

vhusb_license=1234050617ea4984,0,CMICDwCbZ6kF1QLfgUwRe/EGQQIPAKnVhp2ED1dcd8CCKXVl

To turn on debug information logging specify in configuration file:

usb=0403:6001, debug

Send full terminal log to [email protected]. In this mode a lot of debug messages will be saved into terminal log. Turn on only when needed.

USB redirection for Linux. Terminal makes usbip bindfor specified device. usbip attach on terminal server side you should make manually. You may specify USB ID device identificator:

usbip=0403:6001

Or bus id, USB port address, then will be redirected any device, connected to this port:

usbip=1-1.3

USB ID and bus id you may find in USB section of terminal web-interface.

Turn on debug mode in configuration file:

usb=0403:6001, 0403:6002, debug

Then full terminal log send to [email protected] this mode terminal will send to log many messages, turn on only when needed.

sound = on

sound = on, hw:1:0

Specify sound=on and reboot terminal. On terminal web-interface you'll see the list of all sound devices, that terminal has drivers for, and buttons for testing sound.

sound = remote

sound = on, stereo

sound = on, raw

Terminal sound level:

sound_level = 50

Possible values - from 0 (sound muted) to 100 (maximum level). You may show volume control in popup window:

sound_level = 75, infobox

Microphone redirection. Supported only by Windows 7 Ultimate, Windows Server 2008r2 and newer:

microphone = on

USB microphone (only microphone without headphones):

microphone = on, hw:1:0

Terminal microphone sound level:

microphone_level = 50

Possible values - from 0 (microphone muted) to 100 (maximum level). You may show volume control in popup window:

microphone_level = 100, infobox

camera = on

camera = on, raw

serial = com1

serial = com1;com2

serial = com1(usb)

If you need to redirect two or more devices with USB to Serial converter, you should specify USB ID (unique USB device model ID, it's common for similar USB to Serial adapters) or bus ID (physical USB connector address on computer) for each of these devices. Terminal needs to determine corresponding port for each device. Connect all needed devices to terminal. Boot terminal. On another windows-computer in network open web-browser and enter terminal IP in address line. In "USB Bus" section you'll see list of all devices, USB ID (marked green) and bus ID (marked orange) of each device. Syntax of serial= parameter in such case is:

serial = com2(usb 0403:6001), com3(usb 0c2e:0720), com6(usb 11ca:0207)

Or for bus ID (Do not mix! Specify either USB IDs of all devices or bus IDs of all devices):

serial = com1(usb 2-1.1), com3(usb 1-1)

Some USB devices represent two COM ports. It is configured so:

serial = com1(usb), com2(usb second)

Some advanced programs require COM-ports' names for different terminals to be unique. To work with these programs specify in configuration file:

serial = com25(com1),eklmn10(com2),com45(usb)

This line redirects com1 port from terminal, it will be named com25 on server. com2 terminal port on server will be named eklmn10 (yes, it's possible). Connected to USB device with com-usb interface (barcode scanner, receipt printer, scales etc.) on server will be named com45.

Redirected by RDP COM ports are not displayed in Device Manager! To make sure, that everything is right: connect to terminal server, start command line prompt and execute change port command. Correct result is (redirected COM1 port):

COM1 = \Device\RdpDrPort\;COM1:1\\tsclient\COM1
COM11 = \Device\Serial0
COM12 = \Device\Serial1

To turn on debug information logging specify in configuration file:

serial = com1, debug

Send full terminal log to [email protected]. In this mode a lot of debug messages

In this mode a lot of debug messages will be saved into terminal log. Turn on only when needed.

ser2net = com1 115200
ser2net = usb 9600
ser2net = usb 0c2e:0720 9600 NONE 1STOPBIT 8DATABITS XONXOFF LOCAL -RTSCTS

USB ID, BUS ID and serial number of the USB device (if there is one, not every USB device manufacturer identifies devices by serial number) can be found on terminal web interface.

scanner = on

To turn on debug information logging specify in configuration file:

scanner = on, debug

Send full terminal log to [email protected]. In this mode a lot of debug messages

In this mode a lot of debug messages will be saved into terminal log. Turn on only when needed.

To redirect smartcards to terminal in configuration file specify:

smartcard = etoken

Terminal can understand 2 or three (not more than three) card types:

smartcard = etoken, rutoken, omnikey

Next devices are supported:

• auto - Autodetect connected reader
• etoken - eToken 72K Java (0529:0620)
• jacarta - JaCarta, JaCarta LT (24dc:0101, 24dc:0102)
• jacarta_0402 - JaCarta LT new (24dc:0402)
• rutoken - Rutoken S, ECP, lite, iBank2 A (0a89:0020, 0a89:0060, 0a89:0030, 0a89:0025)
• rutoken_scr - Rutoken SCR 3001 (0a89:0069)
• acr122 - ACR122 (072f:2200)
• acs - ASC CCID USB (072f:90cc)
• acr128u - ACR1281U (072f:2224)
• acr3901u - ACR3901U (072f:b000)
• acr39u - ACR39U, some devices are not supported (072f:b100)
• acr38u - ACR38U (072f:9000)
• ezzccid - EZCCID, EZ100PU (0ca6:00a0)
• gempctwin - Gemplus (08e6:3437)
• gempckey - Gemplus (08e6:3438)
• ibank2_blue - iBank2Key blue token (23a0:0002, 23a0:0004)
• omni1021 - OMNIKEY CardMan 1021 (076b:1021)
• omnikey - OMNIKEY (076b:5321)
• omni3021 - OMNIKEY (076b:3021, 076b:3022)
• omni3x21 - OMNIKEY (076b:3031)
• asedrive - ASEDrive (0dc3:1004)
• multisoft - MultiSoft SCR2 (2a0c:0001)
• trustscreen - BIFIT Trustscreen (23a0:0005)
• watchdata - Watchdata (163c:0407, 163c:0417)
• cryptomate64 - ACS CryptoMate64 (072f:90db)
• esmart - ESMART Token (2ce4:7479)
• safetouch - SafeTouch (24a2:0102)
• identive_5710 - Identive CLOUD 2700 F (04e6:5710)
• identive_5810 - Identive CLOUD 2700 R (04e6:5810)
• angara - BIFIT ANGARA (23a0:0008)
• starsign - G&D StarSign (1059:0017, 1059:0019)
• vdtoken - vdToken (2bb1:0f10)
• avtor - Avtor (15cf:0019)
• ezio - Gemalto Ezio Shield (08e6:34c0, 08e6:34c1)
• dell - Dell Keyboard (413c:2101)
• kobil - Kobil Smart Token (0d46:3014)
• minilector - Bit4id miniLector EVO (25dd:3111)
• DigitalDNA - Bit4id Digital-DNA (25dd:2351)
• avbign - AVEST AvBign (28a1:0601)
• scr3311 - SCM SCR3311 (04e6:5116, 04e6:511d)
• au9540 - Alcor AU9540 (058f:9540)
• ePass2003 - Feitian ePass2003 (096e:0807)
• ePass2003Auto - Feitian ePass2003Auto (096e:080a)
• scr301 - Feitian SCR301 (096e:0503)
• acr1252 - ACR1252 (072f:223b)
• almaz1c - IIT Almaz-1C (03eb:9324)
• JCR721 - Aladdin JCR721 reader (24dc:0428)
• yubikey_ofc - YubiKey OTP+FIDO+CCID (1050:0407)
• tokenMe_CC_v2 - Bit4id tokenMe CC v2 (25dd:1101)
• iToken - BIFIT iToken (23a0:0003)

Terminal may autodetect smartcard reader, if it's from the list of supported readers and is connected before terminal turned on:

smartcard = auto

Only one smartcard can be redirected, two cards at once can't be redirected.

To turn on debug information logging specify in configuration file:

smartcard = etoken, debug

Send full terminal log to [email protected]. In this mode a lot of debug messages will be saved into terminal log. Turn on only when needed.

clienthostname = terminal1

clienthostname = ca*MAC

clienthostname = wt*IP1

clienthostname = wt*IP3

rdweb_password = 192.168.1.1

server=password:192.168.1.1, pt-BR

turnoffmenu = on

turnoffmenu = always

turnoffmenu = on,msg:Turn it off NOW!

turnoffmenu = poweroff

autoshutdown = 5

sleep = 10
sleep = 20,standby

By default Raspberry Pi doesn't turn off display. To turn off display backlight add this line in config.txt file on boot SD card:

hdmi_blanking=1

infobox = lctrl
infobox = rctrl
infobox = lalt
infobox = ralt
infobox = lshift
infobox = rshift
infobox = never

infobox = nomac

infobox = noinfo

infobox = ralt,noinfo

infobox = shutdown

infobox = reboot

screenswitch = Win-Ctrl-N

screenswitch = Win-Alt-N

screenswitch = none

onerror = 60

onerror = quiet

redraw_delay = 50

connect_timeout = 5..60

TCP keepalive timer configuration, it determines when to drop connection if network link broke:

keepalive = 10,3,5

Better not to change this parameter. Numebers - TCP_KEEPIDLE, TCP_KEEPINTVL, TCP_KEEPCNT - are described in TCP/IP documentation. By default =on, is the same as =10,3,5. With these settings terminal will show that link is broken in 10 + 3 * 5 = 25 seconds. To turn off this timer specify:

keepalive = off

Firmware for drivers.

Load and launch external files.

language = de, default

keyswitch = alt-shift

clipboard = on

ask_password = on

ask_password = nopin

ask_password = username:Nom d'utilisateur, password:Mot de passe

Animation speed during switching screens:

animation_speed = 3

timezone = hawaii

timezone = local:America/Sao_Paulo

timezone = hawaii, local:Pacific/Honolulu

ntp = pool.ntp.org

ntp = disable

• menu.png - background for server selection menu, user selection menu login window.
• wait.png - background for wait screen with "Please, wait" text.
• saver.png - screensaver.
• popup.png - logo for popup window in right bottom corner. If there's custom logo, WTware logo and version won't be printed. Size should be not more than 280х38 pixels.

C:\Program Files (x86)\WTware\TFTPDROOT\Graphic\sample\

skin = sample

background=ff0000,00ff00,3a6ea5,0000ff

menu_colors=00ff00,ff0000

menu_colors=00ff00,ff0000,5aaaff,ffffff,808080,0000ff

SIP = user:[email protected]

SIP = user:[email protected], ring:1:0, talk:3:0

SIP = user:[email protected], nolock

SIP = user:[email protected], auto-answer

SIP = user:[email protected], port:55555

SIP = user:[email protected], tls
SIP = user:[email protected], tls, nocert

SIP = user:[email protected], tls, srtp

SIP = user:[email protected], config:my_enterprise_sip.wtc

SIP = user:[email protected], debug:2

SIP = user:[email protected], contacts:morecontactsforreception.txt

SIP = user:[email protected], wav:local.wav

SIP_usb_sound_level = 75

SIP_usb_sound_level = 75, infobox

display = 1920x1080

display = 1920x1080, hdmi

display = 1920x1080, 42%

Some drivers allow to rotate display:

display = 1920x1080,portrait
display = 1920x1080,landscape flipped
display = 1920x1080,portrait flipped

On Raspberry Pi rotation should be specified in config.txt file on boot SD card in display_hdmi_rotate option.

Rotated screen always works slower than normal, not rotated.

display = 1920x1080, hdmi, noddc

display = 1920x1080, hdmi, noddc, 75Hz

display = 1680х1050, "146.3 1680 1960 2136 2240 1050 1053 1059 1089"

mouse_accel_mult = 0.05

mouse_accel_mult = touch:12

mouse_accel_mult = 3, touch:12

• video = auto          Autodetect
• Linux kernel Framebuffer drivers, suffix (F)
  • video = VESA(F)          VESA, no widescreen modes!
  • video = efi(F)           EFI (default resolution)
  • video = amd(F)           AMD GPU
  • video = vmwgfx(F)        VMware virtual
  • video = nouveau(F)       nVidia new
  • video = i915(F)          Intel i915..newest
  • video = radeon(F)        ATI new
  • video = gma(F)           Intel GMA500/600/3600/3650
  • video = aty128fb(F)      ATI Rage128
  • video = gxfb(F)          Geode GX
  • video = gx1fb(F)         Geode GX1
  • video = i810fb(F)        Intel i810, i815
  • video = lxfb(F)          Geode LX
  • video = hyperv_fb(F)     Microsoft Hyper-V
  • video = nvidiafb(F)      nVidia
  • video = matroxfb_base(F) Matrox
  • video = radeonfb(F)      ATI Radeon
  • video = rivafb(F)        nVidia RIVA 128/TNT/TNT2
  • video = sisfb(F)         SIS/XGI
  • video = viafb(F)         VIA, S3 Unichrome
  • video = vt8623fb(F)      VIA VT8623 [CLE266]
• The newest X.org graphic library drivers, suffix (U)
  • video = efi(U)           EFI (default resolution)
  • video = ati(U)           ATI
  • video = intel(U)         Intel
  • video = modesetting(U)   Kernel modesetting
  • video = nouveau(U)       Nvidia
  • video = openchrome(U)    Openchrome for VIA
  • video = sis(U)           SIS
  • video = vesa(U)          VESA, no widescreen modes!
• X.org 1.5.3 graphic library drivers, suffix (X)
  • video = apm(X)           APM, Alliance Technology
  • video = ark(X)           ARK Logic
  • video = chips(X)         Chips & Technologies
  • video = cirrus(X)        Cirrus Logic
  • video = geode(X)         Geode
  • video = glint(X)         GLINT/Permedia
  • video = i810(X)          Intel i8xx/i9xx
  • video = mga(X)           Matrox
  • video = nsc(X)           NSC
  • video = rdc(X)           RDC
  • video = rdcm12(X)        RDC M2012
  • video = rendition(X)     Rendition/Micron
  • video = s3(X)            S3
  • video = s3virge(X)       S3 Virge
  • video = savage(X)        S3 Savage
  • video = sis(X)           SIS
  • video = tdfx(X)          3Dfx
  • video = trident(X)       Trident
  • video = tseng(X)         Tseng Labs
  • video = unichrome(X)     Unichrome for VIA
  • video = xgi(X)           XGI
  • video = vesa(X)          VESA Universal driver

bpp = 16
bpp = 32

kbdrate = 30,250

kbdrate = 2,1000

managed = on

managed = 192.168.10.15, 192.168.10.16, 192.168.1.0/24

rsh.exe 192.168.10.50 reboot

rsh.exe 192.168.10.50 update

rsh.exe 192.168.10.50	shutdown

echo -en "0\0\0\0reboot\0" | nc 192.168.1.50 514

httpd = 192.168.1.1, 192.168.1.2, 192.168.2.0/24

httpd = off

Terminal remote control. Works by WTware protocol. It can do all the that embedded VNC server can do. And additionally:

• Shows local Chromium.
• Shows popup window in top bottom corner.
• Shows two terminal displays.
• Works correctly with keyboard.
• Connection is SSL encrypted.
• Shows image faster.

To start remote control on Windows run WTware configurator, right-click on needed terminal in the list.

This line in configuration file allows to run terminal remote control from any computer:

wtrc = on

This line allows to run remote control only from specified IP-addresses:

wtrc = 192.168.10.15, 192.168.10.16, 192.168.1.0/24

By default user has no information about connection from remote control. With such line terminal will ask user to allow terminal remote control:

wtrc = allow after timeout

If in 30 seconds user won't allow connection, remote control will automatically start.

Another line:

wtrc = reject after timeout

By default remote control password is the same as password for Setup menu, that appears at terminal boot start, or as password for HTTPS management. You may specify another password in wtrc_password option.

Zoom (possible values 50%, 75%, by default 100%):

wtrc = on, 75%

Terminal remote control is turned on by wtrc option. By default remote control password is the same as password for Setup menu, that appears at terminal boot start, or as password for HTTPS management. You may specify another password:

wtrc_password = 12345

We recommend to specify password in configurator, for it will encrypt password to store it on disk safely.

You may allow remote control without password:

wtrc_password = mode:none

Password for view, without terminal mouse or keyboard control:

wtrc_password = view 123

Passwords for view (123) and control (the same as Setup password) must be different:

vnc_password = view 123, control mode:setup

You can connect to terminal by VNC protocol to view terminal screen and to help user with his problem. It became more important when Microsoft removed Remote Desktop Connection from Windows 2012 Server.

Next configuration file line allows connection to terminal by VNC from any computer:

vnc = on

vnc = 192.168.10.15, 192.168.10.16, 192.168.1.0/24

If terminal uses two monitors, then to view second monitor by VNC connection specify while connecting 5901 port.

If terminal is over slow channel, specify in configuration file:

vnc=4to1

By default user knows nothing about VNC-connection.You may ask user for permission. With such line:

vnc=allow after timeout

Another line:

vnc=reject after timeout

Password for connection to WTware VNC server:

vnc_password = 12345

Password length is from 1 to 8 symbols. Allowed latin letters and digits. Specified in configuration file password is available to everone - from TFTP configuration file or terminal log. It's more secure to store in configuration file password hash. It won't protect from serious hack, but at least it'll force to spend some time. To generate password hash use WTware graphic configurator. For example:

vnc_password=hex:a0987527920893f174515708320c7fe3

Password for view, without terminal mouse or keyboard control:

vnc_password = view 123

Passwords for view and control must be different:

vnc_password = view 123, control 12345

syslog = 192.168.1.1

syslog = 192.168.1.1:9099

discover = 192.168.1.1

keyboard_log = on