1 / 9

Thin Client

Thin Client. WLD – Subject Orientation June 2007. What you need to know. Basic concept of thin clients Status of activities Awareness thin clients will not be identical. Roots of thin clients. Developed to counter the high costs of PCs Frequent replacement schedule

carnig
Download Presentation

Thin Client

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Thin Client WLD – Subject Orientation June 2007

  2. What you need to know • Basic concept of thin clients • Status of activities • Awareness thin clients will not be identical

  3. Roots of thin clients • Developed to counter the high costs of PCs • Frequent replacement schedule • High management support costs • Higher the flexibility –the higher the support costs • Blend of current user interface (Windows)with the dumb terminal concept • Windows user friendly • Dumb clients – very cost effective

  4. What is a thin client? • 1/3 size of a pc • Kleenex box • No moving parts • Less maintenance • 5-7 year life • Vs 3-4 for PCs • Windows ‘dumb terminals’ • Really thin clients • all processing done on the servers • Newer thin clients • Embedded XP – have enough sw to run internet browser • Kiosks • Not blade computers (which you may have heard about) • Not Discover Station

  5. Thin Client Feasibility Test • Refer to the attached scope document

  6. Why thin clients for Weld? • Cost savings of an estimated 1/2 million over 10 years • Increased stability • Higher ratio of clients to IT staff members • Longer life of equipment • Shared licensing vs per machine • http://www.military-medical-technology.com/article.cfm?DocID=1428

  7. Project status • Four machines in Eaton have been running for several weeks • 2 PAC • 2 Internet • Two Pacs at Farr • Deployed for over a month • Two Public Internet • Deployed at Farr

  8. Will be different • Example: patrons will need to put in flash drives prior to launching and Office Suite applications • Don’t load applications on them • Should be viewed as fairly static devices UNLESS the application can be deployed via a browser • May be more difficult to get a wide variety of games running on them • Refer to risks section of the scope document

  9. Next Steps • July 8 • Go/no go decision for full conversion of CV public machines • Deployment of machines • August • Final go/no go for new facilities • Final go/no go for branch replacements

More Related