What is Thin Client, and how does it work?
Will it work with predictive dialer, and will it work with a Windows or Linux server? I want to connect Thin Client with my predictive dialers and server for a BPO process. What role with Thin Client play in this? Is it a replacement for computers? If we use Thin Client, how will it help us in reducing costs?
Any information is helpful.
Yes, Thin Clients were design primarily to reduce costs. They are used instead of PCs and the idea is that a Thin Client is a terminal with no moving parts, requires no software installation and maintenance.
Mining companies love Thin Clients because they work under extreme conditions and if one fails anyone can replace the device.
Thin Clients are only half the solution, they work with a technology solution that is called Server Based Computing. Citrix invented this technology and it works by centralising all the IT infrastructure at your data centre and you just deliver keyboard strokes, mouse clicks and video updates over the network.
It works really well for users located anywhere on the planet.
Ankur - several good answers on what Thin Client is. All discuss the pro part. If you're thinking about this topic at all, you should recognize the inherent con: if you're not connected to the server, you have nothing. No local files, no Microsoft office to do work off-line, no nothing. Just you and your writing pad and your phone (unless that is VOIP too). If a back-end server goes down, then everybody has nothing. We use thin client at my current work-site and it works pretty well most of the time. If you have unpredictable power or internet service, or you are in a mobile situation, thin client may be impractical or inadvisable.
I would not consider myself an expert on Thin Clients, but I can speak to how I have seen them used. A thin client, in essence, is a small computer that is pulling information from a larger computer, or in many cases, a server. So instead of having a large cpu at a computer station, you just have a thin client that is pulling information (in cases I have seen) from a large server or mainframe.
An example in the world I work in:
I teach medical records software in classrooms with 12-24 computer stations. We log in to a training environment and practice the software in that environment. Some employers, instead of having a standard cpu computer station with the software on each cpu, instead use thin clients at each of these computer stations and then pull from their mainframe server.
I cannot speak to Thin Client use with predictive dialer, but I know it can be used on Windows or Linux servers.
A Thin Client offering Windows Embedded can be customized to use pretty much any software you would need locally but a Thin Client is meant to connect to a server at lower cost and energy consumption point than a traditional desktop computer. A Thin Client running an X11 client or connecting to a traditional Linux environment over XDMCP or an SSH App can be connected to from a Linux OS and the WES (Windows Embedded Standard) devices as well as the Linux devices can connect to any Microsoft Server setup that you could have.
Well, I'll try to give the explanation in the shortest possible way -
According to WikiPedia: "A thin client (sometimes also called a lean, zero or slim client) is a computer or a computer program that depends heavily on some other computer (its server) to fulfil its computational roles. This is different from the traditional fat client, which is a computer designed to take on these roles by itself." and as far as your question is concerned, yes thin client can be connected with the predictive dialers.
The major benefits offered by a thin client is:
1. Cost Savings
2. Simplified Management
3. Enhanced Security
4. Increased Productivity
An example of a hybrid thin client would be Chrome OS, where full functionality is only obtained when connected to the internet. Hardware thin clients are a great cost saver from a maintenance and management perspective, but each client requires the same licencing as a full operating system (Windows). That said, you should be able to do anything on a "thin" client that you can do on a "thick" (full computer) client.
Thin client is a cheaper replacement for a computer. Predictive dialers should run on the thin client. To answer this query absolutely accurately, I may need to llok at the details of actual products, the PD, thin client, etc.
The below answers provide you good detail. I would only add that thin clients vary by vendor. Those optimized for the PCoIP protocol typically have no Windows run-time SW, which means they should be more secure and the lowest maintenance option. Others using older thinclient protocols, e.g. Citrix HDX (ICA) have required some Windows functionality on the end-device which defeats the purpose of a thin-client to begin with.
There's a detail explanation on this at Wikipedia maybe in case you've missed it.
Put simply, a thin client allows application processing to occur on the back end server instead of the local desktop. This provides you with the ability to reduce your hardware footprint on local desktops considerably.
There are many other benefits to thin clients including tighter controls around your "Standard Operating Environments [SOE]". Ease of deployment for end user desktops. Geographical relocation of users without the need to move hardware. There are too many benefits to list.
Depending on which software vendor you choose (VMware, Microsoft, Citrix, AWS, etc.) all have different prerequisites for their thin clients. You will find that most if not all of the software vendors in the market have the ability to build the back end server farm on Windows or Linux. In reality it doesnt make much difference, which OS platform you use.
As for the "Predictive Dialer", depending on which product you use, they will have a list of supported platforms for servers and whether the product supports visualization or not. You will need to contact the vendor to confirm.
Thin client mean two things hardware and software
In both cases the job done on server side
Hardware: Terminal computer has UI capability all data on the server.
Software: Database server will process client request and send result to the client.
You have received a lot of very good answers to your question (I believe that Jason Ball provided the best advice). However, I also wonder if perhaps you asked the wrong question. Perhaps the question should be framed something like, "What are my options for the implementation of a BPO process within my organization?" I would suggest that the considerations are business issues and some elements are IT technology related. But do not fall into the trap of having the tail (technological elements) wag the dog (the business issues).
For this reason I would carefully consider Jason Ball's comments.
"Thin Client" is another way of saying "Little computer box that generally has no moving parts and communicates with the central computing brain, or the cloud-based server." You can run an entire network of computers in a thin client environment, and never again have to worry about upgrading each PC in the office with the latest software and anti-virus protection. Updates within the Thin Client environment happen at the server level. Thin Clients work great for offices with many computers and an IT team that doesn't want to be bothered by end-user machines. You can even set up PC's to act as Thin Clients if you want to get maximum return on investment as you phase in the Thin Client hardware. The downside of going with a Thin Client environment is that all computer functions require access to the server, meaning if you don't have the proper connectability, you're down. In a true cloud server environment, you must have adequate bandwidth, and proper design, or you'll be pulling your hair out every day. (Side note: You can also deploy a wireless solution to enhance the network "ease of scalability." We recommend Ruckus Wireless for true enterprise class wireless solutions.) Thin Client solutions will work with all the same programs you currently use or want. It's a hardware issue, and you can make it all work, but whether a pc network or a Thin Client network, they all can work with dialer systems. Yes, Thin Clients will work with Windows or Linux servers. In the long run, there may be cost savings due to a lesser expense on end-user hardware, but there are end-user costs that may not be readily apparent on the surface. People generally want Thin Clients for convenience in maintaining the network, not always for cost savings. There are so many variables that make it work or not work for any given business that you should talk to an IT engineer to make sure you don't go down a road that leads to problems. Solutions are always preferable, especially when they save you lots of money and aggravation. There are companies that can assess your network, make it secure, and alleviate pitfalls that will inevitably cost more money in the long run. Many IT professionals understand how to make things work, but make sure you get with a team of true engineers who know how to design networks properly. Most IT companies will throw some Tier 2 technicians into the field to help, when you really need Tier 3 engineers. Better yet, get an outsourced CIO or a Chief Architect to meet with you to make recommendations.
I´m not sure about using with predictive dialer, in fact, I haven´t previous experience with predictive dialer but I´ve worked with thin clients a couple of times.
So I´ll try answering as much as I can your questions.
You could use thin clients with linux or windws, there are thin clients server for both. We normally use thin clients as desktop substitution, a thin client is a dedicated piece of hardware with very limited hardware capabilities, and it´s unusual find thin clients diskless. Other option is using legacy desktop to act as a thin client. In both scenarios (a dedicated hardware or a old desktop), thin client will boot without a operational system and will request a O.S image from bootp protocol (these little guys must have a PXE support in their network cards). At this point a thin client server will send a S.O. image throw lan to thin client stations.
So, in general lines, a thin client is a two layer client-server application.
As a solution, thin client could help you reducing costs with works stations, but you´ll need to invest in a good thin client server.
If you I could help you with anything else, please, let me know.
usually very little logic on the client, mostly processed on the server, like a web application
Thin clients are designed to eliminate most of the need for a workstation or desktop computer. The idea is that a server located somewhere in the world has applications that may be remotely run by thin client applications.
All that being said, the thin client concept has been largely replaced by web enabled applications that are accessible through your browser and mobile applications alike.
Thin Client typically means the business logic is built on a server somewhere and downloaded to the client system on demand. This means the client system itself can be smaller (and cheaper) than in "fat client" implementations.
Thin Clients can be small, cheap machines. However, the beauty of loading the business logic from the central server is that it's easily updated for all users.
Is it cheaper to build? Not really since you rely on really good network connections. It's cheaper to manage, though, since you don't spend so much time trying to finesse updates & patches. Of course, you have to build the system so that it's resilient and won't take your business off the air when it fails.