Modules

From ThinManager Knowledge Base
Jump to: navigation, search

Modules listed here are for Packages 5, 6, and 7 unless otherwise noted. Modules with an (*) are listed as Advanced Modules, typically should not be used, and are kept in for Legacy Purposes.

Contents

ICA

Citrix ICA UseAlternateAddress Module

The Citrix ICA UseAlternateAddress Module is used in Citrix Environments where applications can reside at more than one Browser Address.
See the Citrix BrowserProtocol Page at the Citrix Product Documentation Center.
Configurable Options:

Use Alternate Address: Must be set to 1 for module to be active.
Browser Protocol: Valid options are "HTTPonTCP" and "UDP" (no double quotes).
HttpBrowserAddress: Must be a valid IPv4 Dotted Decimal Address. ie. 10.0.0.1
HttpBrowserAddress2: Must be a valid IPv4 Dotted Decimal Address. ie. 10.0.0.1
HttpBrowserAddress3: Must be a valid IPv4 Dotted Decimal Address. ie 10.0.0.1

Citrix ICA wfclient.ini Extension Module

The Citrix ICA wfclient.ini Extension Module is used by advanced Citrix users. This module allows up to 8 strings of text to be added to the wfclient.ini file for passing Citrix parameters.

Citrix Receiver Version 12 (*)

The Citrix Receiver Version 12 Module will allow the Terminal to use Citrix Receiver Version 12.
NOTE: This is an Advanced Module and should not be used unless directed by ACP Technical Support. This module is supported in Packages 6 and 7.

ICA Client Version 6.0 (*)

The ICA Client Version 6.0 Module will allow the Terminal to be compatible with Citrix ICA v6.0.
NOTE: This is an Advanced Module and should not be used unless directed by ACP Technical Support.

ICA Client Version 8.0 (*)

The ICA Client Version 6.0 Module will allow the Terminal to be compatible with Citrix ICA v6.0.
NOTE: This is an Advanced Module and should not be used unless directed by ACP Technical Support.

Local Storage

The Local Storage modules allow the use of USB ports on thin clients. The USB ports are not active by default for security purposes.

USB Flash Drive Module

The USB Flash Drive Module allows USB flash drives to connect to a terminal. Once this module is enabled and properly configured, the terminal will be able to access the Flash Drive via the following path: \\tsclient\USBDISK

The USB Flash Drive Module configuration options include:

  • Drive Access Rights in Session: ReadWrite allows the user to read and write to the flash drive. ReadOnly allows the user to read data but not write data, and None sets the flash drive to access only the unique serial number to make it usable as a TermSecure ID device.
  • Use with TermSecure: This needs to be set to YES to allow the device to be a TermSecure identifier. A NO setting, in conjunction with a ReadWrite Access Rights setting, will allow the device to be used as a remote storage drive
  • Allow Manual Login: This value, when set to Yes, will allow a TermSecure user to log into a terminal without a TermSecure ID device. If set to No, TermSecure users must use a TermSecure ID device to log in.
  • Prompt for Password: This value, when set to Yes, will require a TermSecure User to enter their password for access, even if the password is configured in ThinManager.

USB Memory Card Reader Module

The USB Memory Card Reader Module allows USB card readers to connect to a terminal.
Configurable Options:

  • Number of Slots in Reader: This value sets the number of slots that the card reader uses.
  • Read Only Access: This value, when set to Yes, will limit the user to reading the card. This value, when set to No, will allow the user to read and write to the card.

Mouse

Mouse Modules are designed to change the way the mouse behaves to clicks are processed by both the Terminal and Terminal Server.

Mouse Configuration

The Mouse Configuration Module allows USB or PS/2 mice to be configured and allows the use of two mice. The number(s) in parenthesis determine which package the specific feature is associated with.
Configurable Options:

  • Primary Mouse Type (5):This setting allows both a PS/2 mouse and USB mouse to be used on a terminal. This setting will define which mouse is considered the primary mouse.
  • Mouse Protocol (5): This value allows the selection of different protocols used by the mouse.
  • Scroll Mouse (5): The value, when set to Yes, allows a scroll mouse to function on a terminal.
  • Use Acceleration Values (6,7): This setting configures the mouse to either use the Acceleration Values
  • Acceleration Multiplier (5,6,7): This value allows the mouse movement to be slowed down or sped up.
  • Acceleration Threshold (pixels) (5,6,7): - This value is the number of pixels a mouse must move before the acceleration multiplier takes effect.
  • Left Button (6,7): This will disable the left mouse button when set to Disabled.
  • Right Button (6,7): This will disable the right mouse button when set to Disabled.
  • Scroll Button (6,7): This will disable the scroll button when set to Disabled.
  • Scroll Wheel (6,7): This will disable the scroll wheel when set to Disabled.

These parameters can be changed by highlighting the parameter and choosing a new value in the Value dropdown box. Use the Set button to accept the new parameter value.
ThinManager supports USB mice by default. The Mouse Configuration Module allows configuration of USB mice.
A thin client can have both a USB and a PS/2 mouse installed. This module allows the selection of the primary mouse when using two mice.

PS/2 Mouse Configuration (Package 5 only)

The PS/2 Mouse Module is the forerunner of the Mouse Configuration Module. It allows the changing of PS/2 settings like mouse type, acceleration and threshold. All of these features are now available in the Mouse Configuration Module. This module is for Package 5 only.
Configurable Options:

  • Mouse Type: This value allows the selection of PS/2 or USB mouse type.
  • Scroll Mouse: The value, when set to Yes, allows a scroll mouse to function on a terminal.
  • Acceleration Multiplier: This value allows the mouse movement to be slowed down or sped up.
  • Acceleration Threshold (pixels): This value is the number of pixels a mouse must move before the acceleration multiplier takes effect.

Serial Mouse Driver

The Serial Mouse Driver allows a serial mouse to be used with terminals.
Configurable Options:

  • Mouse Type: This value defines what type of mouse is used.
  • Serial Port: Set this value to the serial port number used for the mouse.

Share Keyboard and Mouse Modules

The Share Keyboard and Mouse Module allows several thin clients to be controlled with a single keyboard and mouse without the need of a KVM switch (Keyboard/Video/Mouse).
The Share Keyboard and Mouse has a Master module that is added to the controlling terminal, and a Slave module that is added to the dependent terminals.

ModulesSKM.png
Shared Keyboard and Mouse Layout

The Share Keyboard and Mouse can be used by placing several monitors connected to thin clients, side-by-side or top-to-bottom. The Share Keyboard and Mouse Master Module is loaded on the center thin client. This module is configured by adding the IP addresses of the secondary slave thin clients. The other terminals receive the Share Keyboard and Mouse Slave Module. Once the Share Keyboard and Mouse Master Module is added to a terminal, it can be configured by highlighting it in the Installed Module window and selecting the Configure button.
Configurable Options:

  • Left Terminal IP Address: Enter the correct IP address for the Slave terminal on the left of the master terminal, if used, and select the Set button.
  • Right Terminal IP Address: Enter the correct IP address for the Slave terminal on the right of the master terminal, if used, and select the Set button.
  • Top Terminal IP Address: Enter the correct IP address for the Slave terminal on the top of the master terminal, if used, and select the Set button.
  • Bottom Terminal IP Address: Enter the correct IP address for the Slave terminal on the bottom of the master terminal, if used, and select the Set button.
  • Allow Interactive Shadow of Master: Normally a terminal with the master module loaded is blocked from interactive shadow. If you want to allow interactive shadowing on the master, highlight the Allow Interactive Shadow of Master parameter, select Yes from the Value drop-down, and select the Set button.

Share Keyboard and Mouse Slave Module

The Share Keyboard and Mouse Slave Module is loaded on the secondary terminals using the same methods as other modules are loaded.

Configurable Options:

  • Master IP Address: This setting allows the slave module to be configured to connect to a specified master by entering the IP address of the master terminal and selecting the Set button.

Select the Done button when finished.
Once the terminals are booted, the mouse on the master terminal can be moved seamlessly into the other desktops. The keyboard will be active in whatever screen the mouse pointer is on.
This allows an operator to have control of several displays with only one keyboard and mouse. The mouse movement is seamless, allowing access to displays without switching.


Note: A Master Share Keyboard and Mouse session cannot be interactively shadowed in ThinManager unless it is configured to allow it.


The keyboards and mice for the slave thin clients can be left attached but stowed away until a multi-user configuration is needed.

RDP

RDP Experience Module

The RDP Experience Module allows a session connected to a Windows 2003 or higher Terminal Server with RDP to add visual features to the session. These typically don’t need to be turned on unless Windows Aesthetics are valued more than System Resources.
Configurable Options:

  • Allow Desktop Background: This setting, if set to Yes, will allow a terminal to show a desktop background.
  • Show Window Contents While Dragging: This setting, if set to Yes, will allow a terminal to show window contents while dragging.
  • Allow Menu and Window Animation: This setting, if set to Yes, will allow a terminal to show window and menu animations.
  • Allow Themes: This setting, if set to Yes, will allow a terminal to show a Desktop Theme.

RDP Port Module

The RDP Port Module allows the port that RDP uses to be changed from the default TCP 3389. See the IANA's Service Name and Transport Protocol Port Number Registry for a complete list of reserved ports.
Configurable Options:

  • RDP Server Port Number (decimal) - Enter the new port number for RDP in this field.

RDP Serial Port Redirection Module

The serial ports on a terminal can be remapped by adding the RDP Serial Port Redirection Module to the terminal without additional configuration. Once the terminal is booted, the COM1 in the session will refer to the COM1 on the terminal, while the COM2 in the session will refer to the COM2 on the terminal. This function requires Windows 2003 or higher to work.
Additionally the COM Port Mapping needs to be allowed. This is done on the Remote Desktop Session Host Configuration Console. To open the Remote Desktop Session Host Configuration Console in Windows 2008 R2 select Start > Administrative Tools > Remote Desktop Session Host Configuration.
Launch the RDP-tcp Properties page by highlighting the Connections folder in the tree pane and double-clicking the RDP-tcp in the right pane. This will launch the RDP-tcp Properties page.
The Com Port Mapping checkbox must be unselected to allow the RDP Serial Port module to function on the terminal server.

RDP Session IP Module

The RDP Session IP Module allows a terminal to use an alias IP address for a specific Display Client session. This module would be useful where a supervisor’s instance of an application runs on a different server than everyone else’s. Configuration options include:

  • Group Name: This specifies the Display Client to use as listed in ThinManager.
  • Session IP Address: This is the IP address to use as the alias.
  • Session IP Address for Instant Failover: This is the IP address to use for a backup session it the Display Client is configured to use Instant Failover.

Screen Saver

MultiSession Screen Saver Module

The MultiSession Screen Saver Module has two modes. It can be set to cycle through the MultiSession windows when the terminal is inactive, or it can be set to return to the main MultiSession screen when the terminal is inactive.
Configurable Options:

  • Mode: The Cyclic mode will switch between all active sessions on the terminal. The GotoFirstGroup mode will switch the terminal to the main session when it is inactive.
  • Start Delay Time in secs: This is the number of seconds of inactivity that the terminal will allow before starting the screen saver.
  • Switch Interval in secs (Cyclic only): This is the number of seconds that the terminal will display each session when using the Cyclic mode.

Screen Saver Module

Screen Saver Module is a module that loads a screen saver on the client. The screen saver will run when the terminal is idle to protect the monitor. Since the screen saver runs on the client, it saves CPU resources on the terminal server.
Configurable Options:'

  • Screen Saver: the graphic that is displayed when the screen saver is active.
  • Wait Time in Minutes: the length of time that the terminal needs to be idle before the screen saver starts.
  • Use Disable Time Period: the screen saver can be set to be disabled or unavailable during a time block. This could be used to prevent the screen saver from running during normal business hours.
  • Disable Start Time (0-23): This sets the start of the disabled time block. 0 is Midnight and 23 is 11:00 p.m.
  • Disable End Time (0-23): This sets the end of the disabled time block. 0 is Midnight and 23 is 11:00 p.m.
  • Force Off when Start Hour is Reached: If set to Yes, this will turn the screen saver off when the Disable End Time is reached.

TermSecure

RF Ideas pcProx Module

The RF Ideas pcProx Module allows a terminal to use RF Ideas pcProx cards as TermSecure ID cards.
Configurable Options:

  • Port: This selects the port that the RF Ideas pcProx card reader is installed.
  • Number of Data Bits: Different cards use different numbers of data bits in their format. This sets the number of data bits to match that used by the card as an identifier. The choices are 26, 37, or Raw.
  • Use Facility Code: This value, when set to Yes, will require the addition of the card’s Facility Code to the Card / Badge ID number.
  • Allow Manual Login - This, when set to Yes, will allow a TermSecure user to log into a terminal without a TermSecure ID device. If set to No, TermSecure users must use a TermSecure ID device to log in.
  • Prompt for Password: This, when set to Yes, will require a TermSecure to enter their password for access, even if the password is configured in ThinManager.
  • Zero Pad Facility Code and ID: This will add a zero to the number string. This is rarely needed.


For a full list of supported RF-ID Readers, see the RF-ID Readers Article

RF Ideas pcProx USB Module

The RF Ideas pcProx USB Module uses a USB device that allows a terminal to use RF Ideas pcProx cards as TermSecure ID cards.
Configurable Options:

  • Mode: This allows the device to be used in TermSecure Mode or Wedge mode. The Wedge mode sends data straight to the session as a keyboard wedge.
  • Allow Manual TermSecure Login: This, when set to Yes, will allow a TermSecure user to log into a terminal without a TermSecure ID device. If set to No, TermSecure users must use a TermSecure ID device to log in.
  • Prompt for TermSecure Password: This, when set to Yes, will require a TermSecure to enter their password for access, even if the password is configured in ThinManager.


For a full list of supported RF-ID Readers, see the RF-ID Readers Article

RF Ideas pcProx Sonar Module (Package 6 only)

The RF Ideas pcProx Sonar Module enables the use of the RF Ideas pcProx USB Sonar Device which is a sonar based presence detector. It sends a configurable keystroke to the terminal when a user is present. It sends a different configurable keystroke to the terminal when the user’s presence is no longer detected. This avoids having to rely on the TermSecure User timeout if the user fails to log out. The TermSecure User will be logged out immediately upon walking away from the terminal.
Configurable Options:

  • Walk-Away Modifier: CTRL, ALT, CTRL+ALT
  • Walk-Away Key: A-Z, Esc. Tab, Backspace, F1 - F12
  • Walk-Up Modifier: CTRL, ALT, CTRL+ALT
  • Walk-Up Key: A-Z, Esc. Tab, Backspace, F1 - F12

Configuration of this module is a two step process:

  1. Download and install the RF Ideas pcProx Configuration Utility from the RF Ideas pcProx Sonar Website.
  2. Specify the Walk-Away and Walk-Up values within the Configuration Utility.
  3. Specify the Walk-Away and Walk-Up values within the Module in ThinManager.

The purpose of configuring the Walk-Away and Walk-Up values in both ThinManager and the Configuration Utility is that when the Sonar device sends a key stroke to the terminal and that key combination is defined in the module, the key combination will get processed by the terminal but not sent to the terminal session.

TermMon ActiveX Configuration

The TermMon ActiveX Configuration Module configures the terminal to accept commands from the TermMon ActiveX Control which collects terminal information and can perform terminal functions.
Configurable Options:

  • Allow ActiveX Connections: This value, when set to Yes, will allow the ActiveX control to function. Setting this value to No will prevent any ActiveX communication to the terminal, including the default terminal server to terminal access.
  • Only Allow Connections from Session: This value, when set to Yes, will allow other terminal server sessions and PCs to communicate to the terminal with the ActiveX functions. If set to No, the only communication allowed is between the terminal and a session on the terminal server belonging to the terminal, providing that the Allow ActiveX Connections value is set to Yes.

The TermMon ActiveX Control is typically integrated into an existing program on the Terminal Server to add in additional functionality to your applications. The control must be registered with regsvr32 before it can be used.
See the TermMon ActiveX Control Article for details on the control itself.

USB Flash Drive Module

The USB Flash Drive Module allows USB flash drives to connect to a terminal. Once this module is enabled and properly configured, the terminal will be able to access the Flash Drive via the following path: \\tsclient\USBDISK
Configurable Options:

  • Drive Access Rights in Session: ReadWrite allows the user to read and write to the flash drive. ReadOnly allows the user to read data but not write data, and None sets the flash drive to access only the unique serial number to make it usable as a TermSecure ID device.
  • Use with TermSecure: This needs to be set to YES to allow the device to be a TermSecure identifier. A NO setting, in conjunction with a ReadWrite Access Rights setting, will allow the device to be used as a remote storage drive
  • Allow Manual Login: This value, when set to Yes, will allow a TermSecure user to log into a terminal without a TermSecure ID device. If set to No, TermSecure users must use a TermSecure ID device to log in.
  • Prompt for Password: This value, when set to Yes, will require a TermSecure User to enter their password for access, even if the password is configured in ThinManager.

Wavetrend Tag Reader Module (Package 5 only)

The Wavetrend Tag Reader Module allows a terminal to use Wavetrend RF-ID cards as TermSecure ID cards. This allows a user to login through TermSecure when they approach the terminal and logs them out when they leave the area. The distance required to login and log out are configurable in the module.
Configurable Options:

  • Port:The WaveTrend Tag Reader Module connects to a thin client through the serial port. The Port setting specifies which COM Port the reader is attached to.
  • Use Vendor Code: This, if set to YES, includes the vendor code as part of the identifier number.
  • Allow Manual Login: If set to YES, this allows a TermSecure User to use the hotkey to initiate logins, or the device. If set to NO, it will force a TermSecure User to use a device to login.
  • Prompt for Password: NO allows the device to login without a password. YES forces every TermSecure User to enter a password after using the device.
  • Entry Signal Strength: The signal strength required to register the card as in range.
  • Exit Signal Strength: The signal strength required to register the card as out of range.
  • Entry Sensitivity: The number of reads above the Entry Signal Strength reads that are required to register as “Entered”.
  • Exit Sensitivity: The number of reads below the Exit Signal Strength that are required to register as “Exited”.

Sound

The use of sound from a thin client requires four things:

  • Audio Capable Hardware
  • Amplified speaker(s) or headphones
  • The Universal Sound Driver Module
  • Either Windows RDP Session or Citrix server-side software.

Universal Sound Driver

The Universal Sound Driver will allow the use of sound on a support device. If this module is applied while a Terminal has an existing session on a Terminal Server, that session will need to be reset to allow the use of audio.
Configurable Options:

  • Audio Bandwidth (ICA Only): This parameter can be set to Low, Medium, or High bandwidth when using Citrix ICA.
  • Sound in Session: This setting, when set to Enabled, will allow sound generated within the session to be played through the terminal. When this is set to Disabled the session sounds will be turned off but system sounds will still be generated during TermSecure login for audio feedback during the login process.
  • Terminal Sound Effects: This setting, when set to Enabled, will allow terminal sound effects like TermSecure login sounds on the terminal.

Video Drivers

Core Video/Core Video2 Module (*)

The Core Video Module (Package 6)/Core Video2 (Package 5) will automatically be selected and downloaded by ThinManager when necessary without user intervention. This module is only selectable via Advanced Modules and should not applied unless specifically told to do so by ACP Technical Support.

Custom Video Mode Module

The Custom Video Mode Module is used when a terminal is having difficulty displaying out to a monitor or HDTV and should be used when the display is garbled, malpositioned, or showing abnormal behavior. Configurable Options:

  • Monitor Number: This values allows you specify which monitor the settings will apply to. Multiple monitors will require multiple copies of this module.
  • Video Mode Type: This allows the setting of the ATSC or VESA Video Standards to the terminal. Those options listed with a “720” will produce a video resolution of 1280x720 with varying refresh rates and those with a “1080” will produce a video resolution of 1920x1080 with varying refresh rates.

Monitor Configuration Module (Packages 6,7)

The Monitor Configuration Module will override the display driver’s intended output. This module is not needed unless listed in the Compatibility List or directed by ACP Technical Support.
See the Supported Hardware Article for further information.

Legacy Video Module (Package 5 only)Legacy Video Module (Package 5 only)

The Legacy Video Module will automatically be selected and downloaded by ThinManager when necessary without user intervention. This module is only selectable in Package 5 via Advanced Modules and should not applied unless specifically told to do so by ACP Technical Support.

Ati Radeon Video2 Driver (Package 5 only)

The Ati Radeon Video2 Driver will automatically be selected and downloaded by ThinManager when necessary without user intervention. This module is only selectable via Advanced Modules and should not applied unless specifically told to do so by ACP Technical Support.

Keyboard

Key Block Module

The Key Block module traps certain keystrokes and prevents them from being sent to the terminal server for processing. This module is recommended for use when users need to be locked out of Windows Specific Keyboard Shortcuts (ie. Win-R for a run box, Ctrl-Esc for start menu, Ctrl-Shift-Esc for Task Manager, etc.) or to block keyboard input into an AppLink Program.
Configurable Options: The Keyblock Module has several options that may be configured with either a YES or NO value.

  • Block Ctrl
  • Block Ctrl+Alt+Del
  • Block Ctrl+Esc
  • Block Alt
  • Block Alt+F4
  • Block Alt+F
  • Block Alt+Tab
  • Block Windows Key
  • Block Menu Key

Key Block Single Key Module

The Key Block Single Key module traps specific individual keystrokes and prevents them from being sent to the terminal server for processing.

Configurable Options:
Modifier: All, Ctrl, Alt, Ctrl-Alt
Key to Block: Configurable to A - Z, Tab, Esc, Backspace, F1 - F12. (Only one key may be specified at a time).

Keyboard Configuration Module

The Keyboard Configuration Module allows key settings on a keyboard attached to a terminal to be set.
Configurable Options:

  • Num Lock State: This allows the Number Lock to be set to On at startup, Off at startup, always On, or always Off.
  • Cap Lock State: This allows the Caps Lock to be set to On at startup, Off at startup, always On, or always Off.
  • Scroll Lock State: This allows the Scroll Lock to be set to On at startup, Off at startup, always On, or always Off.
  • Repeat Delay (ms): This parameter sets the amount of time that a key needs to be held down before it starts repeating the keystroke. If this parameter is set to Disable a key will only send one keystroke even if the key is held down.
  • Repeat Rate (char/sec): This parameter sets the number of characters per second that a held down key will send.
  • Disable Repeat for Enter Key: This parameter, when set to Yes, will prevent the Enter key from repeating if it is held down.
  • Keyboard Layout: This parameter allows the thin client to use keyboards other than the default English (United States) keyboard map.

RF Ideas pcProx USB Module

The RF Ideas pcProx USB Module uses a USB device that allows a terminal to use RF Ideas pcProx cards as TermSecure ID cards.
Configurable Options:

  • Mode: This allows the device to be used in TermSecure Mode or Wedge mode. The Wedge mode sends data straight to the session as a keyboard wedge.
  • Allow Manual TermSecure Login: This, when set to Yes, will allow a TermSecure user to log into a terminal without a TermSecure ID device. If set to No, TermSecure users must use a TermSecure ID device to log in.
  • Prompt for TermSecure Password: This, when set to Yes, will require a TermSecure to enter their password for access, even if the password is configured in ThinManager.


For a full list of supported RF-ID Readers, see the RF-ID Readers Article

Share Keyboard and Mouse Modules

The Share Keyboard and Mouse Module allows several thin clients to be controlled with a single keyboard and mouse without the need of a KVM switch (Keyboard/Video/Mouse).
The Share Keyboard and Mouse has a Master module that is added to the controlling terminal, and a Slave module that is added to the dependent terminals.

ModulesSKM.png
Shared Keyboard and Mouse Layout

The Share Keyboard and Mouse can be used by placing several monitors connected to thin clients, side-by-side or top-to-bottom. The Share Keyboard and Mouse Master Module is loaded on the center thin client. This module is configured by adding the IP addresses of the secondary slave thin clients. The other terminals receive the Share Keyboard and Mouse Slave Module. Once the Share Keyboard and Mouse Master Module is added to a terminal, it can be configured by highlighting it in the Installed Module window and selecting the Configure button.
Configurable Options:

  • Left Terminal IP Address: Enter the correct IP address for the Slave terminal on the left of the master terminal, if used, and select the Set button.
  • Right Terminal IP Address: Enter the correct IP address for the Slave terminal on the right of the master terminal, if used, and select the Set button.
  • Top Terminal IP Address: Enter the correct IP address for the Slave terminal on the top of the master terminal, if used, and select the Set button.
  • Bottom Terminal IP Address: Enter the correct IP address for the Slave terminal on the bottom of the master terminal, if used, and select the Set button.
  • Allow Interactive Shadow of Master: Normally a terminal with the master module loaded is blocked from interactive shadow. If you want to allow interactive shadowing on the master, highlight the Allow Interactive Shadow of Master parameter, select Yes from the Value drop-down, and select the Set button.

Share Keyboard and Mouse Slave Module

The Share Keyboard and Mouse Slave Module is loaded on the secondary terminals using the same methods as other modules are loaded.

Configurable Options:

  • Master IP Address: This setting allows the slave module to be configured to connect to a specified master by entering the IP address of the master terminal and selecting the Set button.

Select the Done button when finished.
Once the terminals are booted, the mouse on the master terminal can be moved seamlessly into the other desktops. The keyboard will be active in whatever screen the mouse pointer is on.
This allows an operator to have control of several displays with only one keyboard and mouse. The mouse movement is seamless, allowing access to displays without switching.


Note: A Master Share Keyboard and Mouse session cannot be interactively shadowed in ThinManager unless it is configured to allow it.


The keyboards and mice for the slave thin clients can be left attached but stowed away until a multi-user configuration is needed.

Miscellaneous

These are modules that don’t fit in other categories.

Add Serial Port

The Add Serial Port Module is only used to configure the serial ports of daughter boards that add additional serial ports to terminals. Add a module for each additional serial port. Each module will let the user configure one additional port.

  • Port Number: This value is to be set to the port number of the new port.
  • Port Address: This value is to be set to the port address of the new port.
  • IRQ: This value is to be set to the IRQ of the new port.
  • UART: This value is set to the chipset type for the new port.

Domain Name System Module (Package 6 only)

  • Domain Name: This value is to be populated with your Domain Name.
  • Name Server 1 IP Address: This is the first DNS Server the terminal will try to use.
  • Name Server 2 IP Address: This is the second DNS Server the terminal will try to use.
  • Name Server 3 IP Address: This is the third DNS Server the terminal will try to use.
  • Search Domain: This value is to be set to the domain where you want your terminal to find hosts.

Firmware Update Module (formerly the Disk On Chip / Compact Flash Update Module)

ACP enables some models of terminals to store the firmware with Disk On Chip or Compact Flash storage so that the unit doesn’t have to download the entire firmware at boot, but can boot locally and download just the configuration to save bandwidth. This is most commonly used with units that will connect over low bandwidth networks, like wireless networks or WANs. These units can use the Firmware Update module to download and flash new firmware when the firmware is updated in ThinManager.
The ability to update stored firmware terminals eliminates the need to send the terminal back to the manufacturer to update the firmware.
Configurable Options: The Firmware Update module has two configurable parameters.

  • Confirm at Terminal: This setting, if set to Yes, will prompt the operator to choose between immediately updating firmware or waiting until the next boot up. If Confirm at Terminal is set to No, the firmware download will take place immediately.
  • Force Update: Normally a stored firmware terminal with the Firmware Update module will check firmware version numbers at boot and only download a new firmware if the versions are different. This setting, if set to Yes, will force the terminal to always download the firmware for re-flashing.

Note: The module will download firmware when it detects a different firmware. Since this will only happen at the first reboot after updating the ThinManager firmware, it is safe to leave this module added to terminals permanently when Force Update is set to No. It does not need to be added and removed each time the firmware is updated. However, since it will update when the firmware is different, it will try to update the firmware if you boot it from a ThinManager server with older firmware.


Firmware Update Program

Once the new firmware has downloaded, an update program will run on the terminal to rewrite the new firmware to the storage. The program will display a warning stating that the terminal must not be reset or powered off during the process, usually around 30 seconds. Ignoring the warning can corrupt the stored firmware, so it is important to leave the terminal alone for that period of time.


Note: A loss of power during the firmware update can lead to a bricked thin client.
It is recommended that updates be done over a wired LAN instead of over a wireless connection, when possible.


Instant Failover Module (*) (Package 5 only)

The Instant Failover Module is no longer used in ThinManager and exists solely for Legacy Compatibility. This module is only selectable via Advanced Modules and should not applied unless specifically told to do so by ACP Technical Support.

Local Printer Module

The Local Printer Module simplifies printing through the parallel port on terminals.
Configurable Options:

  • Printer Driver Name: The Local Print module works when the name of the print driver is entered in the Value field for the Printer Driver Name. The Printer Driver name is provided by the Printer Properties Page.

Finding your Printer Driver Name can be accomplished in three steps:

  1. Install the printer driver on the terminal servers that the client will connect to.
  2. Add the Local Print Module to the thin client as described in Adding a Module to a Group or Terminal.
  3. Configure the Print Driver Name parameter in the module to contain the printer driver’s name.

The Printer Properties page for a printer can be launched by selecting: Start > Control Panel > Hardware and Sound > Devices and Printers > Right Click on Printer > Printer Properties > Advanced Tab.

See the Printing from Thin Clients Article for details on how local parallel printing works in Terminal Services.

Redundant Ethernet Module

Some terminals have two network ports. The Redundant Ethernet Module allows the terminal to use both ports with a single IP address and a single MAC address.
This module is designed with the intention that the route the interface takes to the terminal server(s) is different than its counterpart, while remaining on the same subnet.
The terminal will use the primary (LAN1) port under normal conditions. If this port, cable, or switch fails, the Redundant Ethernet module will allow the terminal to activate and switch to the backup (LAN2) port in a seamless fashion.

Second Network Module

Some terminals have two network ports. The Second Network Module allows the terminal to use both ports on different networks. This module can be useful in a situation where the terminals do not have a router in their network, but need to access outside resources such as another ThinManager Server.
Configurable Options:

  • IP Method: This allows the second port to use DHCP or a static IP.
  • IP Address (Static Only): This allows the second port to be assigned a static IP address.
  • NetMask (Static Only): This allows the second port to be assigned a subnet mask.
  • Router (Static Only): This allows the second port to be assigned a router.

Serial to TCP Module

The Serial to TCP Module allows for a serial device plugged into a thin client to transmit data over TCP on a specified port. Configuring the setup includes plugging the serial device into the thin client, and having the remote PC connect to your specified port on the thin client’s IP.
Configurable Options:

  • TCP Port: Specifies which TCP/IP Port will be used for Serial Port Traffic.
  • Serial Port: This setting is used to determine which ThinClient COM port will be used.
  • Baud Rate: Used to specify the Baud Rate for the COM Port.
  • Parity: Used to specify how the parity bit will be used, if at all.
  • Data bits: Used to specify how many bits will contain information.
  • Stop Bits: Used to determine how many bits will be used for the stop signal
  • Send Character Threshold: Used to set the minimum number of characters that will be transmitted in a single TCP/IP packet.

TermMon ActiveX Configuration

The TermMon ActiveX Configuration Module configures the terminal to accept commands from the TermMon ActiveX Control which collects terminal information and can perform terminal functions.
Configurable Options:

  • Allow ActiveX Connections: This value, when set to Yes, will allow the ActiveX control to function. Setting this value to No will prevent any ActiveX communication to the terminal, including the default terminal server to terminal access.
  • Only Allow Connections from Session: This value, when set to Yes, will allow other terminal server sessions and PCs to communicate to the terminal with the ActiveX functions. If set to No, the only communication allowed is between the terminal and a session on the terminal server belonging to the terminal, providing that the Allow ActiveX Connections value is set to Yes.

The TermMon ActiveX Control is typically integrated into an existing program on the Terminal Server to add in additional functionality to your applications. The control must be registered with regsvr32 before it can be used.
See the TermMon ActiveX Control Article for details on the control itself.

Time Zone Redirection Module

The Time Zone Redirection Module allows a terminal to display local time when it is connected to a terminal server in another time zone.

  • Time Zone - This parameter can be highlighted to activate the Value drop-down that contains time zones.

Windows terminal servers need to have time zone redirection allowed in the Group Policy Console.

The Allow Time Zone Redirection policy is found under:

  • Server 2003: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Client > Server data redirection folder
  • Server 2008 R2: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Terminal Server > Device and Resource Redirection

User Override Module

The User Override Module is a temporary module that allowed users of ThinManager 3.1 to use the User Override function in Display Clients and is no longer needed in ThinManager 3.2+.
See the Application Override Article for information on the correct way to assign overrides to Display Clients.

Touch Screen

Touch Screens may be enabled by assigning one of the below Modules to a Terminal. If you have more than one touch screen attached to a Terminal, add the appropriate Module to the Terminal Module list for each touch screen.
The named touch screen drivers should only be used on Serial based touch screens and the USB Touch Screen Driver should be used for USB Devices.

  • Arista ARP-16XX/ADM1506-1512 Touch Screen Driver
  • CarrollTouch Touch Screen Driver Driver
  • Contec Touch Screen Driver (Package 5 only)
  • DMC TSC Series Touch Screen Driver
  • DMC Touch Screen Driver (Package 5 only)
  • Dynapro Touch Screen Driver
  • eGalax Touch Screen Driver
  • Elographics Touch Screen Driver
  • Gunze AHL Touch Screen Driver
  • Hampshire TSHARC Touch Screen Driver
  • MicroTouch Touch Screen Driver (Package 5 only)
  • Panjit TouchSet Touch Screen Driver
  • PenMount Touch Screen Driver
  • Ronics Touch Screen Driver (Package 5 only)
  • Touch Control Touch Screen Driver
  • Touch International IR Touch Screen Driver (Package 5 only)
  • USB Touch Screen Driver
  • Xycom 33XX Touch Screen Driver (Package 5 only)
  • Zytronic Touch Screen Driver

Configurable Options:

Connection:

  • Connection Type: Sets whether the touch screen uses Serial or USB to connect.
  • Port or Port (Serial Only): Sets the COM port that a serial touch screen is connected to.
  • Baud Rate: Sets the speed used for communication between the terminal and the touch screen on some serial touch screens.
  • Monitor Number: Used to specify which monitor in a MultiMonitor scheme will use for the touch screen. MultiMonitor terminals with multiple touch screens will need a module loaded for each touch screen used.
  • Controller Type: Sets the model of touch screen controller on some touch screens.

Calibration

  • Number of Calibration Points: This sets the number of calibration points that the calibration program uses during the calibration process.
  • Calibration Margin Percentage: This sets the distance from the edge of the screen that the calibration points are displayed.
  • Calibration Hotkey: This allows a function key to be set as a hotkey so that the calibration can be launched from a keyboard.
  • Calibration Hotkey Modifier: This setting adds CTL or ALT to the hotkey to launch the calibration from the keyboard, if desired.
  • Calibration Touch Down Time (seconds): This setting, when enabled, will launch the calibration program when the screen is touched and held for the assigned number of seconds. This cannot be used with the Right Click Hold Time.
  • Calibration (entered automatically): This is set automatically by machine. These are the values set during the calibration process.
  • Orientation (entered automatically): This is set automatically by machine. Used at the direction of Tech Support in error correction.
  • Swap XY Coordinates: If X and Y are reversed, this setting will correct the orientation.

Touch Settings

  • Double Touch Area (pixels): This sets the size of the area that a second touch will register as a double touch.
  • Double Touch Time (milliseconds): The amount of time between touches that qualifies as a double touch.
  • Touch De-Bounce Timeout: a time interval used to prevent a single touch from being registered as multiple touches.

Right Click

  • Right Click Hold Time (milliseconds): This setting, when enabled, will treat a touch that is held for the assigned number of seconds as a Right Click of the mouse. This cannot be used with the Calibration Touch Down Time.
  • Right Click Area (pixels): This sets the size of the area that a second touch will register as a right click.
Personal tools
Namespaces

Variants
Actions
Navigation
Events
Toolbox