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.
Could you please advise me what configuration is required on a Windows PC to allow for a WinTMC session to span multiple monitors? We found the configuration on the thin server but still can’t get the WinTMC session to maximize across both monitors on the client system.
It is almost the same process as setting up MultiMonitor for a thin client. In the terminal configuration wizard select Enable MultiMonitor, select the resolution of your monitors, and setup the layout of the sessions. If you choose the resolution that your monitors are running at it should open full screen across both monitors once it’s received its configuration.
-TM
_________________
There’s no total limit for the server that you are connecting to. You’re really only limited by the number of COM ports on the thin clients.
-TM
________________
I’d like to know if ThinManager works with video resolution with a ratio different than 4:3? I’m referring to wide screen resolution like 16:9 or 16:10. I’m going to test a generic PXE boot thin client: does it support wide screen?
Yes, there are multiple 4:3, 16:9, and 16:10 resolutions. The available resolutions in ThinManager is based on what thin client’s you are using. The software hides incompatible video modes. As long as the hardware that your using supports widescreen resolutions, then yes. A vast majority of thin clients support all the normal standard and widescreen resolutions up to 1920×1200.
-TM
_________________
I am in the process of evaluating ACP ThinManager and had a quick question. We currently have a few legacy systems that are on Windows NT 4.0 and are in the process of being virtualized. I would like to use ThinManager and a thin client to connect to the Virtual Server, is this possible?
We have not tested ThinManager against a Windows NT 4.0 System. It might work against NT 4.0 Terminal Server Edition but the oldest OS we have tested with is Server 2000 and we cannot guarantee any level of stability or performance.
You will not be able to install ThinManager onto your NT4.0 System as ThinManager 6.0 requires .NET Framework 4.0, which is only supported in Windows Server 2003 and above. If you have ThinManager setup on a Win2003+ Server and tell the Terminal to start a session on the 4.0 box, you might have some luck.
There are no known issues connecting a ThinManager Terminal to a Virtual Terminal Server.
I would like to recommend that you try ThinManager 6.0 SP3 (our latest release) with a demo code to see if you can connect. You can grab an install and a demo code from: http://downloads.thinmanager.com/
Also, our Compatibility Matrix has information on which OS’s are compatible with ThinManager.
http://www.thinmanager.com/kb/index.php/Compatibility_Matrix
-TM
__________________________________________
To view our “Tips & Gems” video tutorials, visit our video links page here.
To review 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.
