Everything you read about thin clients, zero clients, or anything other than a PC will tell you there is a device that is better and saves you more money compared to their competition. More often than not, these claims are validated by a report paid for by a hardware manufacturer that only talks about their specific client matched up against another client chosen as comparative fodder because they know they can beat it. These reports are not false, nor are they inaccurate. They are, however, slanted to omit where the savings really are to paint a far prettier picture. After all, their first, last, and only reason for commissioning such a report is to sell you their newest hardware release.
This is the third and final part of our three part series focusing on the entire process of Virtualizing in an industrial environment. While there is a lot of talk about Virtualizing and VDI, we wanted to focus on the viability and deployment of Virtualization in an industrial and manufacturing environment which would speak to the concerns and difficulties specific to this industry.
Part 3: Managing Your Environments?
In Part 2 of this series, we discussed whether or not Virtualization is necessary once you’ve centralized, and, if it is, how far do you go. For most System Administrators, RDS is the easiest and most cost effective place to begin. The need to only install OS’s and applications once, and having them deploy to multiple clients, can provide enough time savings and reduced administrative headaches that Virtualization could very well just be an added cost to a system that already does everything the end user requires.
This is the second in a three part article focusing on the entire process of Virtualizing in an industrial environment. While there is a lot of talk about Virtualizing and VDI, we wanted to focus on the viability and deployment of Virtualization in an industrial and manufacturing environment which would speak to the concerns and difficulties specific to this industry.
Part 2: How Much Virtualization is Needed?
In Part 1 of this series, we discussed the need to centralize computer resources before considering whether or not to virtualize them. The vast majority of ThinManager customers use Remote Desktop Services (formerly Terminal Services) as their Centralization solution. One reason for this is that RDS is included with every Windows Server installation, so there are fewer initial costs incurred when centralizing.
This is the first in a three part article focusing on the entire process of Virtualizing in an industrial environment. While there is a lot of talk about Virtualizing and VDI, we wanted to focus on the viability and deployment of Virtualization in an industrial and manufacturing environment which would speak to the concerns and difficulties specific to this industry.
Part 1: Centralization Before Virtualization
It is everywhere and there is no escaping it. It is written about, discussed, recommended, and deployed in offices and facilities around the world every day. It is the iPhone of IT…you might not know why you are buying it, you just know that everyone else is using it so it must be the next great thing. But as implementation of virtualized environments continues to become the norm rather than the exception, industry publications are reporting that up to 40% of Virtualization deployments are never completed and eventually scrapped.
Imagine having the power to turn a PC work station into an easy to manage secure terminal in any industrial situation. Now imagine that work station being a simple and reliable system with increased functionality paired with decreased ownership cost. Your imagination is here.
With WinTMC, ThinManager provides a complete solution for organizations that need to use PCs as part of their terminal server network. For many network administrators, WinTMC may be the missing piece to help their network be more cost effective, productive and easier to manage.
Over the course of the last decade, the growth of thin client computing in factories and industrial environments has continued to increase as demand has steadily risen. In these facilities, where environmental and safety factors are often the primary influence when deciding on a reliable computing platform, there is a definite need for technology that replaces the PC. As a machine, the PC is not intended to operate in an area filled with vibration, airborne particulates, or hazardous gases. Such concerns and factors explain why there is constant growth in the industrial thin client computing arena. But this beckons the question, if industrial operations continue moving to the thin client because they HAVE TO, then what is the impetus for the front office CHOOSING TO?
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
With the completion of the ThinManager 6.0 Launch & Training event, we are gearing up for the inevitable landslide of reviews and requests that follow a successful launch. Some people are just hearing about ThinManager for the first time, while long-term end users are making plans for upgrading the ThinManager centralized management platform currently running in their facility. One of the most common questions we are asked is, “Why do I need ThinManager if I already have another centralized management solution running my daily operations?”