Discussion Locked

benefit of 'thin client' vs windows desktop for medium company ?

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

Here in Paris , France, we're runing , as a lot of small companies I guess, Dell desktops and laptops all conneted to a Win2k3 server for about 15 users. We are full ip over an ethernet lan. The existing link to Internet for browsing and emailing is an ADSL 1024 Ko, and seems ok to all users...even those who're playing with MS Messenger ;-). More professionaly, they all are running office 2k3, a dedicated database on the same server and web access via XP Pro.

I have to open 3 offices in foreign countries where risks are high and are not safe. In each one I should excpect about 5 users.

We immediately thought about thin clients like wyse winterm, all connected to Paris server on which I'm thinking of installing Office2k3 for them remotely runing it.

Before going further, I would like your point of view :
- what are the risks ?
- are we going the right way ?
- will network traffic be hughe ?
- what about a full web-based solution ? does it exists ?
- what should I think about, absolutely not bypass ?
- should I then move all people to winterm ?

Thanks in advance for your comments, tips and warning.

PS : sorry for my English mistakes, but you know these french, people when they try to write english...

8 replies

by dtmilano

You should try this (http://pxes.sf.net).
It's free, open source, lets you use old equipment (starting at Pentium I, 32 MB RAM), free from vendor lock-in and connect to all major server centric platforms.
There's also a live CD for a risk free test.
See complete list of features in the web site.

by roger99a

You might want to look at Thinstation (search www.sourceforge.org for it). It probably works much like the PXES. I have found it quite easy to use.
As for security, running high encryption RDP through a VPN should be about as secure as you're going to get with an internet connection. The other advantages will come with lower adminstration costs. All the backups will be local to the server and downed systems can be replaced by the end user since there is no workstation configuration involved. A local TFTP server would be advisable for faster boot times. I have 5 clients running over a 384K leased line and they love it. Much faster than accessing data directly. Read the EPIA article on the Thinstation site. Our units cost about $200 each for hardware.

by hal 9000

I would think you would need a decent server at each office for when the Internet is down so that they can continue working. As you have said that this is a difficult environment I would be looking at loosing the Internet on a regular basis along with all telephones unless you have satellite phones.

As for power I'm guessing that is just something that you'll have to live with as I do not think it will be a viable alternative to have generators on-site and setup to cut in on power outages.

If you keep each office server isolated and then transmit the days data at the end of the day or when power and the Internet is available network traffic shouldn't be too high although I would be using a VPN to connect to these offices.

"what are the risks ?"

Well basic security for one and if they are using thin clients from the main office they will not be able to work when they loose the net.

"are we going the right way ?"

That really depends on the business as with thin clients if the place is raided there is no physical data on-site which could be used against you or the company.

"will network traffic be hughe ?"

This depends on how things are setup but if you are running the thin clients from a central office in a different part of the world you will of course have a much higher network traffic than you currently have and depending on the number involved the currently listed 2 offices of 5 workers should not tax the system overly but if it starts growing it could become a real problem.

While the above posting is a viable alternative it would lack the tax incentives that most likely would be of up most importance to the company.

by awfernald

I'll take the PS first..... I'll answer you in English since your English is definitely better than my French :)

As far as the answers to your questions, some additional information that you should provide is regarding the new sites, what exactly are the high risks? Are the risks in equipment theft? information theft? risky connectivity? etc...

As far as utilizing a terminal client vs. a thinclient vs. full client, you yourself need to answer this question based upon the information you have available.

To answer your questions (and I'm sure others will add even more information to my answers), here goes:
1. What are the risks?
With each system you have certain risks.

Thick client solution, you have local data storage/backup/reliability, information sharing, possibly user training issues. Also, support becomes a larger issue when you need to coordinate software/hardware upgrades across various locations to ensure that you maintain full compatibility.

Remote client solution, you eliminate all of the distributed information issues and most of the support issues, however, you now require a much more sophisticated server configuration, increase the risk of loss productivity due to network/internet outages, and risk the total loss of all productivity in the case of your server(s) going down for any reason.

2. Are you going the right way?
For your new/remote sites, my gut feeling is that utilizing terminal clients will be the best solution for you (as long as your internet is relatively reliable). As the level of technical know-how/support at the new sites is not stated, I will assume worst-case situation that the support there is very limited. In this case, it is relatively simple to preconfigure all of the equipment, ship it to the site, and have one of your techs fly in and perform the installation and provide basic instruction in how to connect new stations/troubleshoot problems.

3. The network traffic from the new sites to the central site will be significant, however, I would not go so far as to say it would be huge. Most terminal clients are designed to be run over slower circuits (<64k bandwidth), and with only five clients, having at least 128kb (preferred 256kb) should be more than enough. The largest issue would be if you start to print out documents to the remote sites, as that could possibly clog a low speed link for quite some time. Make sure the printers are configured as IP printers.

4. Web based solution? Hundreds, thousands, millions of web based solutions are out there, however, without knowing what solutions you actually need, it is impossible to say.

5. What should you think about?
The most important to think about is, how long can these remote sites be "offline" before you start experiencing significant financial impact to your company? If this is low, than you are fine, if this is high, than you need to consider how to keep the clients working regardless of which method you ultimately use.

6. Should you move everyone to winterm?
Evaluate it. How do your people work? Would it be economical? You already have 15 people/PCs working independently, would it be worth the money invested to purchase a new winterm server for them? I would not really consider this until you have the remote clients set up (to show how well it works), than (if feasible), migrate to winterm as you start having to replace the computers at your central site.

by jadium

My company uses Citrix for our terminal service needs. It has a higher initial cost, but I believe the benefits are worth it. The setup is not too difficult, and the clients are updated regularly. The connection is very secure, and requires a minimal amount of bandwidth per client. Citrix has clients that will run the gambit of Operating Systems, from DOS to Windows to Linux. An added benefit is the ability to publish printers, and push updates to the clients.

In a few of our remote locations I am using some older hardware (P-1 200MHz) and Citrix and they are able to run MS Office 2003 with no problems.

The cost per user is higher than just using terminal services, but I believe that the benefits are worth it.

My $.02

by notsochiguy

I used to work for a manufacturing company that had 13 different office locations; a few of them in less than hospitable locations. This is sort of what we did:
*Each office had it's own server for local files/location specific stuff which was setup with Citrix
*For company-wide and mission critical apps, we had a Citrix server a tcorporate.
*Each user had either a new Winterm or an old PC configured with the Citrix client.
*We setup offsite storage for the backups at each site (the backups were encrypted)

All in all, this worked for us. They key, as previously mentioned, is really accessing how much risk you can afford at each site (both in terms of local security issues and loss of productivity caused by downtime).

Personaly, I'm a big fan of thin-clients...as close to giving end users Etch-a-Sketches as I can ever hope to get!! ;)

This discussion is closed to new replies.