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
- Ports (category System Configuration)enabled in ThinManager. This port is configurable by: Double clicking on your server name to bring up the ThinManager Server Configuration Wizard Click3 KB (391 words) - 16:59, 18 February 2021
- for each ThinManager Server. Enter ThinManager Server Information Window Enter the name of the ThinManager Server in the ThinManager Server field. Enter5 KB (597 words) - 18:30, 14 November 2012
- Private:ThinManager Server Configuration
- Common Configuration Problems (section The configuration of the primary ThinManager Server and the secondary ThinManager Server are different)selecting Manage > ThinManager Server List or add both ThinManager Servers to the ThinManager Server Monitor List in the Terminal Configuration Wizard. Reboot14 KB (2,004 words) - 20:51, 1 May 2023
- In ThinManager: Select Manage > PXE Server to open the PXE Server Wizard. Select the Enable PXE Server checkbox on the PXE Server Configuration page13 KB (2,033 words) - 13:46, 11 September 2019
- License Activation (category ThinManager)hardware on the ThinManager Server(s). Licensing does not have to be done from the ThinManager Server, but the IDs must come from the server. Installation5 KB (673 words) - 20:39, 1 May 2023
- client in ThinManager. Open the iTMC application and define the ThinManager Server you will connect to. Connect to the listed ThinManager Server. Select3 KB (442 words) - 19:26, 12 February 2018
- changed on the Terminal Authentication page of the ThinManager Server Configuration Wizard. ThinManager 1. Fixed connection status of a terminal hosted137 KB (14,697 words) - 14:01, 6 March 2024
- Private:ThinManager Server Schedules
- Private:Biometric Fingerprint Readers
- Private:ThinManager Security Groups
- Private:Scheduling Configuration Backups
- ATMC (section Setup and Configuration Overview)client in ThinManager. Open the aTMC application and define the ThinManager Server you will connect to. Connect to the listed ThinManager Server. Select2 KB (304 words) - 17:25, 29 August 2018
- TermMon ActiveX Control (category ThinManager) (section For instructions in a PDF document click the TermMon ActiveX Control for ThinManager 9 link.)TermMon ActiveX Control Configuration Module must be added to the terminal configuration in ThinManager. In the module configuration, Allow ActiveX Connections27 KB (3,248 words) - 13:08, 6 September 2022
- Private:Shadowing
- License Activation with FactoryTalk Activation (category ThinManager) (section Steps to Use FactoryTalk Activation with ThinManager:)properly recognized by ThinManager, click the ThinManager Server button bar. From the ThinManager Server tree, select your ThinManager Server (RDS1 in the example8 KB (1,080 words) - 20:47, 1 May 2023
- Private:Reporting
- Private:Redundancy
- PXE booting with new UEFI thin clients (category ThinManager)standard DHCP server with Boot Options (PXE Disabled) then the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP1 KB (171 words) - 17:34, 3 December 2019
- 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
- Select Next and select a ThinManager Server -- This is important as the CalTouchScreen Utility is installed alongside ThinManager by default. Select Next3 KB (389 words) - 19:28, 14 November 2012
- SCADA… in the System Configuration Utility (SCU) to launch the SCADA Configuration. SCADA Configuration The terminal server is not a SCADA node so23 KB (3,052 words) - 17:18, 1 May 2023
- Private:Pre-Integration Considerations
- from ThinManager after the ThinManager Server IP(s) are specified. ThinManager XLi Compatible Thin Clients are units that PXE Boot from ThinManager. For79 KB (337 words) - 20:13, 1 May 2023
- desktop server right-click on the RDS Servers icon and select Add Remote Desktop Server. The Remote Desktop Server Name page of the Remote Desktop Server wizard2 KB (309 words) - 17:33, 16 August 2018
- Private:ThinManager's Evolution
- Allow log on through Terminal Services (category System Configuration)Windows Server does not allow login through remote desktop services by Non-Admin users. This can present problems when deploying ThinManager and configuring2 KB (227 words) - 19:46, 4 September 2014
- Private:DNS Configuration
- Private:Terminal Server Configuration
- Private:ThinManager Demo
- Private:Configuring Thin Clients to use Redundant ThinManager Servers
- Private:Terminal Server Schedules
- Private:FactoryTalk View SE and ThinManager
- Private:ThinManager Installation
- Category:Installation (section ThinManager)connect to the ThinManager Server and download the firmware and configuration. Step 2: The configuration will send them to the terminal server to login and4 members (0 subcategories, 0 files) - 13:50, 6 June 2017
- Private:Registry Entries
- Private:ThinManager Overview
- Private:SmartSession
- Private:Definitions
- Private:Display Servers
- Private:Active Directory and ThinManager
- Private:Windows Server 2008 R2
- Private:WinTMC Connection Issues
- terminal server client that can be managed by ThinManager. When the WinTMC program is launched it will connect to ThinManager, receive its configuration, and2 members (0 subcategories, 0 files) - 15:43, 9 November 2012
- to allow ThinManager users to search for any information they need regarding any portion of the ThinManager Platform. Intro (1): ThinManager is a thin6 KB (918 words) - 18:54, 1 May 2023
- Category:Licensing (section ThinManager Licenses)this configuration. Redundancy describes having two ThinManager Servers so that a ThinManager Ready thin client can always find a ThinManager Server to boot6 members (0 subcategories, 0 files) - 21:44, 8 September 2015
- Private:Static vs. DHCP IP Addressing
- Private:Upgrade Procedure: Mirrored/Redundant Systems
- Private:Upgrading ThinManager Hardware Capabilities
- Private:Upgrade Procedure: Standalone System
- Private:MultiMonitor
- Private:Citrix ICA
- Private:DCOM Permissions
- Private:Terminal Schedules
- Private:RDP Configuration
- Private:Active Directory and TermSecure
- Private:Replacing PXE Boot Clients
- Private:Microsoft Terminal Services
- Private:Getting Started
- Private:IP Cameras
- Private:Terminal Groups Configuration
- Category:DCOM (section COM and DCOM in ThinManager)info. ThinManager makes a COM connection (or DCOM on a remote computer) to make changes to the configuration database maintained by ThinServer. ThinServer3 members (1 subcategory, 0 files) - 18:24, 14 November 2012
- Private:PowerPoint on a Thin Client
- Private:SQL Editor
- Private:Sound
- Private:License Reactivation
- Private:Display Clients
- Private:Smart Cards
- Private:Auto-login
- Private:Using USB with Thin Clients
- Private:Troubleshooting
- Private:Windows Server 2012 R2 RDS Role Installation
- Private:Password Protected Screen Saver
- Private:MultiStation
- Private:VCenter Connection Error
- Private:TermSecure and View SE Security
- Private:TermSecure and iFIX Security
- Private:TermSecure and InTouch Security
- Private:Modules
- Private:Supported Hardware
- Private:InTouch Deployment
- Private:Initial Program in the Group Policy