This summer, representatives from ACP will once again embark on what has become a time-honored tradition – The ThinManager Roadshow. For more than twelve years,ACP has been traveling across North America spreading the gospel of ThinManager everywhere they can and by any means necessary. It is a somewhat outdated concept in a modern world filled with industry specific expos and online demonstrations, but to the people at ACP, it is just another thing that helps to differentiate them from the pack.
Here at ACP we often speak at great length about all of the amazing features ThinManager has to make your facility more secure and efficient. But while perusing our blog archives, I realized that perhaps we have neglected explaining the basics and have placed the cart before the horse. So I have decided to dedicate this week to explaining one of the most basic processes necessary to implementing ThinManager – setting up a ThinManager ready thin client.
To connect a new terminal to your ThinServer, you must first set the basic configuration via DHCP or via a static IP. Once the server and the terminal are communicating with each other, it is just a matter of clicking the appropriate selection boxes as you navigate the Terminal Configuration Wizard
• IT and production are in separate facilities.
• IT was losing valuable resources while traveling to other sites for maintenance.
• ThinManager Remote Administration allows IT to control and manage a remote site from one location.
Many companies have one IT department that covers a number of locations requiring the IT staff to make regular visits to the other plants for maintenance and repair.
Using standard ThinManager utilities this same staff has access to all remote sites allowing the IT staff to manage them from a central location. They can even shadow sessions and view process and load statistics.
We all know that ThinManager is great, but do you know all the ways ThinManager can help you? Here are the top 10 advantages of using ThinManager:
1. Security: ThinManager knows the best security is not letting the problem close enough to be an issue, so we’ve created a secure environment. Terminal Servers can be secured away from public access, USB ports are closed by default and there are no CD or floppy drives to compromise security. With TermSecure™ we added a second level of security with features like having users access and privileges controlled by administrator, an Auto-login option, and a key blocking module.
As best I can tell, Tim Negris is the man who coined the term Thin Client when he was with Oracle. It originally described scaled down applications that ran in conjunction with a full version of an application that was loaded on a server.
When Windows OS versions that allowed multiple users came on the scene, one of the first hardware companies to start selling client hardware was Wyse with the introduction of their WinTerm in 1995. This made sense – Wyse was already a huge seller of “dumb” terminals for mainframes and providing a Windows Terminal was logical.
Question: We would like to put together a Thin Client system that will have a total of seven Thin Clients. While some of these clients will be standard Thin Client hardware, we would also like to use some of our PCs as clients as well. We also need to allow for some spare capacity for the future.
Can you please specify the hardware and software (ACP and Microsoft) requirements for a reliable system?
Answer: There are multiple ways to build this system. I will start by specifying the basic system (the minimum required) and then work up to a system with redundancy that will guarantee uninterrupted operation in almost every case. Each system will have the following four parts – the Thin Clients, the hosting Windows Terminal Server, the Microsoft software and the ACP software.