Every Friday, we dedicate this space to sharing solutions for some of the most frequently asked questions posed to our ThinManager Technical Support team. This weekly feature will help educate ThinManager Platform users and provide them with answers to questions they may have about licenses, installation, integration, deployment, upgrades, maintenance, and daily operation. Great technical support is an essential part of the ThinManager Platform, and we are constantly striving to make your environment as productive and efficient as possible.
I am currently running ThinManager 3.2 with a number of thick client running WinTMC 188.8.131.52. We are planning to add a new terminal and this terminal will not connect the servers. The only install file I have access to for setting up the new terminal is WinTMC 184.108.40.206. Is there an install file for WinTMC 220.127.116.11?
They can get it there as a free download.
We are having an issue with a new terminal we’re setting up. We are currently using ThinManager 6.0 and have a Termtek thin client, which when it starts and we select a session, runs fine. But when switching to our new Uno 3172, it boots up and displays a ThinManager 5.0 logo. It then says that the terminal is configured to use package 6, restarts, loads with a ThinManager 6.0 logo and works OK. How can I set the default terminal to use package 6 at initial boot up?
Go to Manage>Packages to change default package.
Or select allow Package at Individual.
If your client was running 5 you might have to manually set it to 6 while turned off from replacement.
On our server there is application that makes a SQL connection. During the failover process, the application on the redundant server must start up and make the same SQL connection. How does the server know to open the “right” application and make the correct SQL connection and what happens with the sql data during this failover process?
Usually the SQL call is made by the user account. If each terminal has a unique user then the SQL call source will remain the same regardless of failover.
Or they do it by IP. If that is the case they need to code it to use the unique terminal IP and not the communal server IP.
Please advise whether a new windows group in Windows Server and added into the “Thinmanager Security Group” can allow control of only a single terminal group. I can’t find any specific configuration to perform this.
The ThinManager Security Groups are global. A setting here affects all users. If you want to control access to an application on a terminal you can use TermSecure Access Groups and the Permission button to limit access to members of that group.–
To review the cost savings of using the ThinManager Platform, visit our ROI Calculator here.
To read about successful ThinManager Platform deployments, visit here.
To see when the next ThinManager 2-Day Training Session is being offered, visit here.