If you would like to speak with one of our engineers, please Submit a Question or give us a call at the phone number here. In North America, To route your phone support request directly to a technical support engineer, call toll-free 1-888-382-1583 or 1-440-646-3434, select Option 3 (Technical Support), then select Option 5 (More Options). When prompted, enter the ThinManager Direct Dial Code 201. |
Search results
- Private:Terminal Server Configuration
- Common Configuration Problems (section The configuration of the primary ThinManager Server and the secondary ThinManager Server are different)connect to the terminal server Check Terminal Configuration Wizard to make sure a terminal server is specified Cannot Connect to Server xxx (0.0.0.0)14 KB (2,004 words) - 20:51, 1 May 2023
- Private:SmartSession
- ThinManager Server Configurations Wizard. Synchronize ThinManager Server Configuration Wizard Highlight the primary ThinManager Server as the Configuration5 KB (597 words) - 18:30, 14 November 2012
- Ports (category System Configuration)ThinManager Server Configuration Wizard. This port is configurable by: Double click you server name to bring up the ThinManager Server Configuration Wizard3 KB (391 words) - 16:59, 18 February 2021
- ITMC (section Setup and Configuration Overview)ThinManager Server you will connect to. Connect to the listed ThinManager Server. Select the pre-configured terminal from the list of offline terminals, or select3 KB (442 words) - 19:26, 12 February 2018
- Private:Terminal Server Schedules
- PXE Server checkbox on the PXE Server Configuration page. Select the Using standard DHCP server radio button on the Network Interface Configuration page13 KB (2,033 words) - 13:46, 11 September 2019
- The TermMon (Terminal Monitoring) ActiveX can be embedded into an application that will run on the terminal server. When a terminal starts a session27 KB (3,248 words) - 13:08, 6 September 2022
- Private:Microsoft Terminal Services
- Private:Sound
- Private:Citrix ICA
- Release Notes (section Terminal Capabilities Database)creation and move of a terminal server before finishing wizard 10. Fixed terminal server list in priority dialog showing duplicated servers 11. Fixed package137 KB (14,697 words) - 14:01, 6 March 2024
- 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 terminal44 KB (6,830 words) - 21:22, 24 February 2014
- Private:Display Clients
- operator. In a terminal services environment the terminal server acts as the View node. Each client that connects to a terminal server will start a session23 KB (3,052 words) - 17:18, 1 May 2023
- Private:Display Servers
- on the ThinManager Server(s). Licensing does not have to be done from the ThinManager Server, but the IDs must come from the server. Installation IDs5 KB (673 words) - 20:39, 1 May 2023
- Windows Server 2016 Workgroup RDS Role Installation (section For instructions with pictures see Windows Server 2016 RDS Role Installation)Desktop Services role on Windows Server 2016 in a workgroup is not recommended. The Remote Desktop Services configuration tool is not accessible without1 KB (131 words) - 22:09, 18 February 2019
- ATMC (section Setup and Configuration Overview)ThinManager Server you will connect to. Connect to the listed ThinManager Server. Select the pre-configured terminal from the list of offline terminals, or select2 KB (304 words) - 17:25, 29 August 2018
- Private:PowerPoint on a Thin Client
- Private:ThinManager Overview
- Allow log on through Terminal Services (category System Configuration)Remote Desktop Services" ("Terminal Services" in pre 2008 R2 releases) via: Start > Run > gpedit.msc Expand: Computer Configuration > Windows Settings > Security2 KB (227 words) - 19:46, 4 September 2014
- window. Select the Finish button on the Module Selection page of the Terminal Configuration Wizard and restart the thin client to apply the changes. To initiate3 KB (389 words) - 19:28, 14 November 2012
- ThinManager, click the ThinManager Server button bar. From the ThinManager Server tree, select your ThinManager Server (RDS1 in the example provided). Click8 KB (1,080 words) - 20:47, 1 May 2023
- will be listed under their respective Manufacturer's List in the Terminal Configuration Wizard. XLi Compatible thin clients listed here have been79 KB (337 words) - 20:13, 1 May 2023
- Private:ThinManager's Evolution
- Category:Windows Server 2003 (section Windows Server 2003 Initial Setup Instructions and Terminal Services Role Installation)Windows Server 2003 Terminal Services Role Installation Network Level Authentication DCOM Permissions Permissions DCOM Errors Common Configuration Problems0 members (0 subcategories, 0 files) - 15:45, 3 December 2015
- Category:Windows Server 2008 (section Windows Server 2008 Initial Setup Instructions and Terminal Services Role Installation)Windows Server 2008 Terminal Services Role Installation Network Level Authentication DCOM Permissions Permissions DCOM Errors Common Configuration Problems0 members (0 subcategories, 0 files) - 15:37, 3 December 2015
- Private:DNS Configuration
- Private:2003R2
- Private:Terminal Schedules
- Private:ThinManager Server Configuration
- Private:2008 Standard
- Private:Windows Server 2008 R2
- Private:WinTMC Connection Issues
- Private:Shadowing
- Private:Terminal Groups Configuration
- Private:Redundancy
- Private:ThinManager Server Schedules
- Private:RDP Configuration
- Private:Microsoft Commands
- Private:Pre-Integration Considerations
- Private:Windows Server 2012 R2 Workgroup RDS Role Installation
- Build a terminal server with the Microsoft Windows 2003,2008,2008R2,2012,2012R2,2016 Server operating system. Create a Microsoft Licensing Server and add4 members (0 subcategories, 0 files) - 13:50, 6 June 2017
- Private:Auto-login
- Private:Definitions
- launched it will connect to ThinManager, receive its configuration, and connect to a terminal server and start a session. WinTMC has a major advantage over2 members (0 subcategories, 0 files) - 15:43, 9 November 2012
- Private:MultiMonitor
- Private:Biometric Fingerprint Readers
- Private:Password Protected Screen Saver
- Private:IP Cameras
- Private:Static vs. DHCP IP Addressing
- Private:Configuring Thin Clients to use Redundant ThinManager Servers
- If the terminal is assigned to three or more terminal servers the terminal will then start a second session on the next available terminal server. The6 members (0 subcategories, 0 files) - 21:44, 8 September 2015
- Private:Getting Started
- Private:Network Level Authentication
- Private:Upgrade Procedure: Standalone System
- Private:Troubleshooting
- Private:ThinManager Demo
- display clients can be generated by a session running on a display server (e.g. a Terminal Server, a shadowed thin client, an image from an IP camera, or VMWare®6 KB (918 words) - 18:54, 1 May 2023
- Private:Windows Server 2012 R2 RDS Role Installation
- Private:MultiStation
- Private:Smart Cards
- Private:Modules
- Private:Reporting
- Private:Active Directory and TermSecure
- Private:Replacing PXE Boot Clients
- Private:SQL Editor
- Private:DCOM Permissions
- on a remote computer) to make changes to the configuration database maintained by ThinServer. ThinServer makes a COM connection (or DCOM on a remote computer)3 members (1 subcategory, 0 files) - 18:24, 14 November 2012
- Private:ThinManager Security Groups
- Private:Printer Installation
- Private:ThinManager Installation
- Private:Using USB with Thin Clients
- Private:InTouch Deployment
- Private:Registry Entries
- Private:Active Directory and ThinManager
- Private:TermSecure and iFIX Security
- Private:TermSecure and InTouch Security
- Private:License Reactivation
- Private:TermSecure and View SE Security
- Private:Upgrading ThinManager Hardware Capabilities
- Private:Terminal Firmware Open Source Licenses