The Terminal Configuration Wizard establishes the terminal settings for a terminal, while the Terminal Group Configuration Wizard establishes the terminal settings for a group ofl terminals. The Terminal Configuration Wizard and the Group Configuration Wizard are very similar, with few different settings.
The Group wizard will have Group Setting checkboxes for each setting. Selecting this checkbox will force that setting to be inherited by nested sub-groups and member terminals. This is a significant difference from previous versions of ThinManager that allowed any Group Setting to be un-selected and individually configured for a terminal.
The Group Settings of any sub-group or terminal will be grayed out to prevent changes if the group setting is selected on the parent. Changes need to be made at the Group level.
The Terminal Creation Wizard can be launched by either:
Terminal Configuration Wizard - Terminal Name
When a Terminal is first created, giving it a name is the first priority. Use numbers, letters, hyphens (-), and underscores (_), but don’t use spaces or other characters.
Note: The terminal name should be less than 15 characters because of limitations of the terminal server.
The terminal can be added to a Terminal Group by selecting the Group name in the Group drop-down box. Terminals added to a Group will be assigned the Group properties
The Change Group button will launch a Select Group window.
Select Group Window
The Select Group window will show a tree displaying the group hierarchy. Highlight the Terminal Group that you want to join and select the OK button to join or select the Cancel button to quit without joining.
Terminal Name Page - Group Membership
The Terminal Group you joined will now be displayed in the Group field.
The Copy Settings from another Terminal checkbox will copy an established configuration to the new terminal. Selecting the Copy Settings from another Terminal checkbox and clicking the Copy From button will launch the Select Terminal window that allows the terminal to copy settings from another terminal.
The Select Terminal window will show a tree of the configured Terminal Groups and terminals. Highlight the terminal that you wish to copy and select the OK button to load the settings and return to the Terminal Configuration Wizard. The Cancel button will close the Select Terminal window without making changes.
The Permission button allows the Terminal Group to be assigned Access Groups for security. This is covered in TermSecure. See Permissions for details.
Select the Next button to continue or select the Cancel button to close the configuration wizard without saving.
Terminal Configuration Wizard - Hardware Configuration
Select the make and model of the ThinManager Ready Thin Client from the drop-down boxes. These parameters are from the Terminal Capability database (TermCap data base). If the unit has an integrated flat panel, it will display the touch screen controller type.
The Clear button will remove the Terminal ID identifier from the configuration of an inactive terminal. This will free hardware that has already been tied to a configuration and allow the terminal to be assigned to a different configuration, without deleted its original configuration.
If the make and model of your ThinManager Ready thin client does not appear in the list, download a new TermCap Database from www.thinmanager.com. See Install New Firmware and TermCap Database for details.
If you do not know what model it will be, leave the default setting. When a terminal is connected and receives this configuration, ThinManager will update the hardware settings to match the actual hardware.
Terminal Configuration Wizard - WinTMC Setup
Note: A WinTMC connection needs to be configured as Generic/Personal Computer.
Select Next to continue.
Terminal Options Page
Terminal Server Specification
The Method of Terminal Server Selection radio button provides options for terminal server connections.
If the Use Terminal Server Groups is selected, three other settings become available.
Terminals may connect to a series of individual terminal servers by selecting the Select Individual Terminal Servers on the Terminal Server Specification page.
The Terminal Connection Type page is displayed next to allow the selection of the desired Client Communication Protocol.
Terminal Configuration Wizard - Connection Type
Thin clients use a client communication protocol to connect to the Terminal Servers. Select the correct protocol and select the Next button.
The RDP protocol is used by default.
Terminal Configuration Wizard -Terminal Server Selection
If Published Applications or Terminal Server Groups are not being used, the terminal will need to be assigned to a Terminal Server. The Terminal Server is a server that allows a terminal to logon and run applications in an independent session.
If the Available Terminal Server column is empty, the Terminal Server List wizard needs to be run to add terminal servers to the ThinManager system. Select the Edit Server List button to launch the Terminal Server List Wizard as shown in Terminal Server List Wizard.
Once the Terminal Server List wizard has run, each Terminal Server that is identified in the Terminal Server List Wizard will initially appear in the Available Terminal Server box on the left side of the Terminal Server Selection page.
To select a terminal server for the terminal double-click or the listed terminal server or highlight it and click the Right arrow button. This will put the terminal server into the Selected Terminal Server list on the right. The terminal server on the top of the Selected Terminal Server list will be the Primary Terminal Server, the first terminal server that the terminal will attempt to login to. If the Primary Terminal Server fails, or is unavailable, the terminal will connect to the other terminal servers in the order that they are listed.
To change the order of the terminal servers in the Terminal Server Selection list, highlight a terminal server and use the Up arrow button and the Down arrow button to move it up or down in the list.
The Enforce Primary Terminal Server Connection will cause a terminal to return to the primary terminal server whenever that server is available.
Select the Next button to continue configuration or select the Finish button to complete the terminal configuration.
Terminals may connect to Terminal Server Groups by selecting the Use Terminal Server Groups on the Terminal Server Specification page instead of using the Select Individual Terminal Servers setting.
Terminal Configuration Wizard - Terminal Server Specification
If Use Terminal Server Groups is selected, an Enable MultiSession checkbox will be displayed.
Select Next to continue configuration.
The Terminal Server Selection page is displayed to allow the selection of the desired Terminal Server Groups that contain terminal servers that will host the sessions.
Terminal Configuration Wizard - Terminal Server Group Selection
If the Available Terminal Server Groups column is empty, the Terminal Server Groups List wizard needs to be run to configure Terminal Server Groups. Select the Edit Server Groups button to launch the Terminal Server Group Wizard as shown in Terminal Server Group List.
Once the Terminal Server Group wizard has run, each Terminal Server Group that is identified in the Terminal Server Group Wizard will initially appear in the Available Terminal Server Groups box on the left of the Terminal Server Selection page. To select a Terminal Server Group double-click on the Terminal Server Group or highlight it in the list on the left and click the Right Arrow button. This will put the Terminal Server Group into the Selected Terminal Server Group list on the right. The terminal connect to the terminal servers in the Selected Terminal Server Groups list.
Note: The Available Terminal server Groups will only list Terminal Server Groups that are appropriate. Only RDP Terminal Server Groups will be shown if the terminal is using RDP. If the Enable MultiSession checkbox was selected on the Terminal Server Specification page, only Terminal Server Groups with MultiSession capabilities are shown in the Available Terminal Server Groups list.
MultiSession Not Enabled Warning
If two Terminal Server Groups are selected without Enable MultiSession checked, a message will be displayed warning that the Enable MultiSession checkbox needs to be checked to allow the MultiSession.
Select the Next button to continue configuration or select the Finish button to complete the configuration.
Terminal Configuration Wizard - Terminal Interface Options
A terminal using MultiSession will need to have a method to switch between sessions. This is configured on the Terminal Interface Options page.
Group Selector Options allow on-screen switching of sessions.
Terminal Hotkeys allow the selection of keyboard combinations that allow switching between sessions.
Select the OK button to continue or the Cancel button to close without accepting changes.
The configuration paths (Independent Terminal Servers vs. Terminal Server Groups, MetaFrame vs. Device Services and RDP) unite at the Login Configuration.
Terminal Configuration Wizard - Login Information
If the Username, Password, and Domain fields are filled with a valid Microsoft user account, ThinManager will pass this information to the Microsoft Terminal Server when the ThinManager Ready Thin Client connects, letting the terminal login automatically.
If the Username, Password, and Domain fields are left blank, or are filled with invalid data, the Microsoft Windows login window will be presented on the terminal and the user will need to login manually.
Note: It is recommended that each terminal should login to a Terminal Server with a unique profile.
Note: Windows 2000 Server will not allow RDP auto-login by default. See Configuring RDP for Auto-Login for details.
The Initial Program loads the designated program instead of the Windows desktop when the terminal connects to the Terminal Server. If a program is launched as the initial program, it is the only program that will run. This provides a level of security and control because that program is the only program that will run in that session. If the Initial Program is closed on the terminal, the session on the Terminal Server will close and the ThinManager Ready Thin Client will reconnect to the Terminal Server and re-launch the Initial Program. This effectively makes the Initial Program the only program.
Note: When using the Initial Program with failover, the path must be identical on all terminal servers. If the path is different,, use a batch file to launch the application
Terminals using Terminal Server Groups do not display the Initial Program field. AppLink instead provides the Initial Program function. See AppLink for details.
Login Information - Use Terminal Server Groups
Windows 2003 Computer Management – Local Users and Groups
Note: Users need to be Administrators or members of Microsoft’s Remote Desktop Users Group when connecting to a Windows 2003 terminal server.
Select the Next button to continue terminal configuration or select the Finish button to complete the terminal configuration.
Terminal Configuration Wizard - Video Configuration
The Video Resolution Configuration has a drop-down box that allows the video resolution to be set for the terminal.
The standard terminal connection uses a 256-color depth. The 64K-color depth is available by using RDP connected to a Windows 2003 Terminal Server.
Select the Next button to continue configuration or select the Finish button to complete the Terminal configuration.
WinTMC Settings
WinTMC clients can be configured on the WinTMC Settings page. These only apply to connections made by the WinTMC fat client.
Note: This page will only be shown if GENERIC is chosen for the Make/OEM and :PersonalComputer is chosen for the Model on the Terminal Hardware page.
See WinTMC Fat Client for details on the WinTMC client.
Terminal Configuration Wizard - Module Selection
A Module is a component of the firmware that is not needed for the basic functionality, but may be desired for advanced functionality. These features include Touch Screen drivers, serial mouse drivers, High Speed Serial drivers, Shared Keyboard and Mouse, USB Memory Card Reader, and Instant Failover. See Module Overview for details.
To add a Module to a Terminal, select the Add… button to launch the Attach Module to Terminal window.
Attach Module to Terminal
The Attach Module to Terminal window will show the modules that are available to the terminal. The Module Type drop-down box sorts the modules by categories to make the modules easier to find.
Highlight the desired module and select the OK button to add the module to the configuration.
Module Configuration
Select the Next button to continue configuration or select the Finish button to complete the terminal configuration.
Terminal Configuration Wizard - ThinManager Server Monitor List
By default a terminal sends it's status to the ThinManager Server that it boots from. To get the green light/red light information to be displayed on backup ThinManager Servers requires that the desired ThinManager Servers be listed in the Selected ThinManager Servers list on the ThinManager Server Monitor List page of the terminal's configuration.
If the Available ThinManager Server column is empty, the ThinManager Server List Wizard needs to be run to define the ThinManager Servers. Select the Edit Server List button to launch the ThinManager Server List Wizard as shown in ThinManager Server List Wizard.
Once the ThinManager Server List wizard has run, each ThinManager Server will initially appear in the Available ThinManager Server box. To select a ThinManager Server for the terminal, double-click on it or highlight it in the Available ThinManager Server list on the left and click the right arrow button to move it into the Selected ThinManager Server list on the right. The terminal will send connection status (red/green icon lights) to all ThinManager Servers in the Selected ThinManager Server list.
Select the Next button to continue configuration or select the Finish button to complete the configuration.
Terminal Configuration Wizard - Monitoring Configuration
ThinManager Ready Thin Clients have a socket connect to the terminal server it has a session on. If the terminal detects a socket disconnect it will try to reconnect with the terminal server. If this fails it will try to connect to the next terminal server in the Selected Terminal Server List.
The Monitoring Connection sets the frequency that the terminal tries to contact the failed terminal server before switching to another terminal server. Use the Monitor Interval radio buttons to use a default frequency or select Custom and choose a setting of your own.
A Fast setting of the Monitor Connection will detect Terminal Server failure quickly. However, the faster the setting is, the more sensitive it is and it may drop the Terminal Server when the network is busy but not offline. Setting the Monitoring Connection to a slower setting gives the terminal server more time to respond when it is busy.
Select the Finish button to complete the terminal configuration.
(Updated 7/25/2007)