Discussion Locked

Save money with thin clients

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

What do you think about the potential of Citrix MetaFrame XPe? What experiences do you have with thin client solutions? How is your organization trying to cut costs? Tell us what you think about deploying Citrix MetaFrame XPe, as featured in this week's Government IT e-newsletter.

If you haven't subscribed to our free Government IT e-newsletter, you're missing out on some great information. Subscribe today!

https://www.techrepublic.com/techmails.jhtml?repID=r001

12 replies

by armourbl

I work for a City Government. We provide several contractors City computer systems in order to allow them to access City business type information. This basically means, they need access to emails, and maybe an application or two.

In the past we have had to provide them a complete desktop system at the tune of about $1,400 for the hardware.

Another factor has been problems with misuse of the computer equipment and access.

Using the thin client, we can reduce the cost hardware to about $400. We can additionally use Group Policy in Windows 2000 Server Active Directory to limit the access/applications that these contractors have available.

We are just now beginning to role out the thin client, but so far it looks like it is reallygoing to benefit our operations.

One side note: Something we didn't realize about the thin client was how much it could benefit systems connected over a WON. We have one particular installation that is connected to our backbone over a T1. Performance was descent, but not anywhere near the performance of systems connected via the 100MB LAN. Because all the processing is now taking place on the Citrix Server, we are seeing an improvement in application performance for this remote installation.

ben

by oldefar

Many companies have a churn rate on telephones approaching 100% - most often a reflection of personnel movement within their facilities. Each change in the switch port assignment typically has an associated change in workstation location and quite often a move, add, or change charge. At a minimum, there is an equipment relocation cost and some risk of damage due to the move.

Moving to a thin client opens the opportunity to make the workstation as stationary as the cubes. Since the personalization is no longer associated with the workstation, relocations to support business needs have a lower cost. With MAC charges averaging around $150 each, an organization with 5,000 employees and 100% churn can avoid $750K in MAC annually. Internal or external charges, this still results in a better environment for the business units.

Other soft benefits include greater protection from user introduced viruses, lower physical security costs associated with workstation protection, and faster MTR for workstation failures due to the ability to keep a spare in the area. This is in addition to the commonly considered cost savings from initial equipment to upgrades and support.

by rykerabel

We are migrating from a completely disorganized WinNT workgroup scenario with each school having its own unique network. Now we have Citrix for our 5000+ teachers, but each classroom has a printer. These printers have not been standardized in the past, so supporting the print drivers on Citrix has been a real chore. Now all schools request all computers and peripherals through the central office, so the future looks much brighter.

Just research your printer driver needs before trying citrix, and you'll have a much easier implementation.

Ryker Abel, MCSE, MCSA, MCP, Comptia A+
ryker.abel@stpsb.org

by tnunetworksupport

Three years ago, we deployed MetaFrame 1.8 with a 3 server farm using a published desktop and 50-70 Espirit thin clients. We also transformed many traditional computers into "fat clients".

Over the past 9 months, we have replaced our MetaFrame1.8 farm with a MetaFrame XPe farm and added a server. As part of this project, we have deployed NFuse and PNAgent. NFuse gives us the abilitity to deliver our applications to anyone anywhere. We still have our original thin clients (which have an expected runtime of 10 years! No moving parts!). In addition, we have plans to replace 25-50 traditional computers this summer with thin clients.

Printing was a challenge and AutoProf's Profile Maker has saved the day in that arena. It is notcheap, but if you have an enterprise environment, it is worth the money.

To date, we have around 120 concurrent users on Citrix farm during business hours. Our next phase is to deploy to our 1800+ students!!

-Joe

by dlw6

Citrix has a great concept. It has advantages not only in TCO but in security as well.

The problem arises when the clients have to pass through the Internet to get to the server. Then, it's like running Win2K on a 486 processor. You can take a coffee break between starting an Office application and being able to actually open a document, and at peak usage periods the application is likely to not start at all. That loses money, because the wasted seconds add up over the course of a day.

Good fortune,
Don

by Ramon Padilla Jr.

Regarding the comment via Citrix slowness via the Internet. I use Citrix frequently via the Internet going through Citrix Secure Gateway and connecting through a DSL connection. Frankly, it is just as fast this way as it is via a connection via the LAN. Even through a 56K dial up, it is much more tolerable than a PC Anywhere connection. If you are getting slowness, something is configured incorrectly.

Ramon

by mwojcik

I use Citrix via the Internet going through Citrix Secure Gateway and connect via a cable connection. It is just as fast as the LAN and so much more reliable than PCAnywhere.

by wbrown

I heartily agree that Citrix is a great alternative to the rollout of new PC's. However, look into the Thin Client units instead of PC's. When we first deployed Citrix, many of our users were using the Program Neighborhood on old PC's. We found that our support calls were actually increasing due to hardware failure and unfamiliarity with the "new way" they were supposed to use the PC's. In areas where we made the full switch to Thin Clients , we have had few support calls once the initial learning period is over. SO not only do I get a low cost replacement (under $300), I reduce call volume and increase customer satisfaction! We also use Citrix low bandwidth to relieve some of our over burdened T-1 lines. It is a win-win!

by nd_it

The thin client has saved us $$. We have nothing deployed in our production area but thin clients. The enviroment is a dusty, not very clean, bad for hardware components. We have more than enough bandwidth to compensate for the traffic, since thethin clients only use RDP, all the processes are done on the server side. We even have rolled out a couple wireless thin client tablets for testing and mobility.

by mwojcik

I work for a local government agency that has been using Citrix servers since 1997. We moved to a Citrix server because of a 16-bit Fox pro application that needed to be available to mutiple sites. We began with a WinFrame server and have since moved to the MetaFrame server.
I am the Network Administrator of 4 sites that connect to the MetaFrame server, via T1 and fiber optics.
The most important feature for us, is the shadowing feature that allows me to take over the clients session to get them out of a jam, or for help with any of the applications. 45 users; and I can sit at my desk to help, instead of driving to the sites. Another important feature is that one of the sites uses Macintosh computers. The Mac users are able to file, print, scan and share files with no problems.
We now have 15 thin client terminals and are down to 13 PC's. The terminals last about 5 years, PC's are still replaced every three. The terminals are reliable and cut down on administration. Cost for thin client terminals runs about $400.
I would recommend thin client computing to everyone.

by andy.carnahan

We use metaframe to deliver applications (both corporate and desktop) and the performance across low bandwidth lines is sensational.
The other *killer* use of Metaframe is for remote dialup users. Instead of trundling along on 56k network connection, Metaframe lets you fly.

But the licensing is diabolical to understand. You need to work it out carefully. For instance, even if your laptop has MS Office, if you use Metaframe, I have been told you need a second Office licence on the Metaframe server.

If anyone can clarify how the licensing works, you will have won a friend!

This discussion is closed to new replies.