|Alpharetta, Georgia, October 5, 2010
Automation Control Products and it’s flagship software, ThinManager, have moved to a new space that allows for exponential growth in the coming years. The new office has expanded many areas that make ACP’s ThinManager the elite terminal server management and thin client software, such as a state-of-the-art Tech Support Lab, Webinar Room, Marketing & Education Departments and our award-winning support staff.
Tech Support Lab
Marketing & Education Departments
AutomaTech, Control Dynamics, Industrial Network Systems and McNaughton-McKay now offering ThinManager and ThinManager Ready Thin Clients
Alpharetta, Georgia, June 10, 2010 – Automation Control Products is proud to announce the recent signing of new partners to its nationwide distributor sales channel. These companies’ commitment to their customers and their understanding of rapidly changing technology make each one of them a great fit with ACP’s ThinManager and its focus on building the most robust industrial software platform for the modern plant floor.
In addition to selling ACP’s Thin Client management software ThinManager, each of these distributors will also be selling ThinManager Ready hardware from ACP’s existing hardware partners.
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.
A Thin Client computer runs what looks like a full Windows NT 4.0 operating system on each Client installed in a factory. This is accomplished by having a powerful server running a version of Microsoft’s NT 4.0 designed for Thin Clients, NT Terminal Server 4.0. This version of Windows allows multiple users to log in and establish a full Windows session running on the server. Each user gets a dedicated share of memory, some slices of CPU time, and access to the server’s disks and applications.
Since its introduction in 1999 ThinManager has undergone a number of improvements. But the most significant changes have come with the latest releases.
Here is a look at the most important features added and enhanced since ThinManager 2.3.
Introduced in ThinManager 2.4
On June 18, 2007 ACP will release version 3.1 of ThinManager. This thin client configuration, management, and security suite for thin client networks now offers even more functionality.
MultiMonitor adds support for up to 5 monitors using available hardware from Advantech and Arista. Using the MultiMonitor wizard a user can configure up to five monitors in a variety of layouts using spanning and screening. When used with MultiSession the thin client can be configured to run a separate session on each monitor through a single thin client.