THIN CLIENTS Understanding the Costs

Total Page:16

File Type:pdf, Size:1020Kb

THIN CLIENTS Understanding the Costs WHITE PAPER December, 2006 THIN CLIENTS Understanding the costs We will also examine some changes in PCs that Contents have the potential to further alter the PC/thin client Executive summary ...............................................2 cost equation. Thin-client terminology ..........................................2 Costs to consider...................................................3 We begin, however, by reviewing some PC changes…………………………………………..7 terminology that is helpful when discussing thin Summary……………………………………………...8 clients and the infrastructure necessary to support them. Executive summary Intel Corporation commissioned Principled Key thin-client terminology Technologies, Inc. (PT) to examine the changes and Thin clients come in several different styles, each costs organizations should consider when deploying of which uses a somewhat different architecture to thin clients. delivering computing power to users. Different vendors and analysts often use different terms for As we have discussed in a previous white paper the same concepts and approaches. To avoid (http://principledtechnologies.com/clients/reports/Intel/ confusion, we will use the following consistent set ThinClientWP.pdf), thin clients serve certain market of terms to help make clear which thin-client niches well. On the surface, cost comparisons of thin approaches and technologies we’re discussing. and rich clients may seem as simple as checking which device is less expensive to purchase. Thin client z Server-side computing – A form of advocates also frequently tout lower Total Cost of computing in which almost all of the Ownership (TCO) as a major inherent advantage of processing (with the usual exception of the thin clients due to their relatively simple architectures. display of information) happens on a shared server rather than on a client The real picture, however, is predictably much more system. A single server almost always complicated. The complication stems from the fact that serves the computational needs of many of the costs of adopting thin clients are not multiple clients. (If each server supported initially visible. Instead, those costs emerge only as only one client, the servers would organizations put in place the infrastructure necessary effectively be acting as PCs that to support thin clients. happened to sit far away from the users.) The server may in turn use other devices, These costs come from both the potentially major such as file servers, to meet some of its infrastructure costs necessary to support thin clients requirements, such as disk storage. initially and the additional support costs organizations Server-side computing is basically what will face over the lifetime of the systems. To compare mainframes and minicomputers provided those costs to the costs of using rich clients, to all users before the era of the PC. organizations must also consider management z Shared server – A server that allows initiatives in the rich-client space as well as a variety of multiple thin clients to run applications on intangibles and the "future-proofing" that newer it simultaneously. A shared server is generations of rich clients can provide. typically providing server-side computing to the thin clients. In the rest of this white paper we will look at the z Blade PC – A PC on a card that operates following key thin client cost areas: in a chassis in a rack-mounted configuration. To use a blade PC, a user z Thin client hardware typically runs a thin client device on his or z Application servers her desktop, and that device in turn uses z Network infrastructure the blade PC for its computing. Blade PCs z Application migration were traditionally dedicated, meaning one z Training blade PC served one user. Sharing the z Software licenses computational power of a single blade PC z Productivity among multiple thin clients is certainly z Intangibles possible with more powerful blade PCs, z The future and some vendors are doing so. z Thin client – A thin client is a computer that relies on a server or other back-end system, such as a blade PC, to supply Principled Technologies, Inc.: Thin clients: Understanding the costs 2 most or all of its computation needs. While benefits of thin clients will eventually go away or such a device often possesses a lot more get so small as to be inconsequential.” intelligence than most terminals did in years past, its primary task is displaying information. As an example of how complex this picture can Newer thin clients have begun to include the be, consider a set of test beds that we assembled ability to run browsers and some other during April and May of 2006. Our goal was to set applications locally. The more thin clients up five-unit test beds that employed different types provide such abilities, of course, the closer of clients: they come to being PC-like rich clients. z Microsoft Remote Desktop Protocol (RDP) – z typical business PCs (Dell OptiPlex RDP is a protocol that allows a user to 210Ls) connect to a computer running Microsoft z Sun Ray thin clients (Sun Ray 2s) Terminal Services. Typically, a thin client front- z Wyse thin clients (Winterm 5150SEs) end device will use RDP to connect to a server. The front-end device, however, could The table below summarizes what we had to also be a PC running software that uses this spend to set up each test bed. Each test bed used protocol. the exact same model and configuration of server, z Citrix Independent Computing Architecture so we do not include that server's cost. We also do (ICA) – ICA is a protocol that is closely related not include the cost of monitors, because we used to RDP and that also allows a user to connect the exact same model monitor on all systems. We to a computer running the appropriate also omitted shipping and tax. underlying software. In this case, that software is the Citrix Presentation Server. As with RDP, Five-client test bed Price the front-end device has traditionally been a Sun thin clients thin client, and the other system a server. The Sun Fire v240 server $ 6,924 front-device, however, could also be a PC 5 Sun Ray 2 thin clients $ 1,814 running the necessary Citrix software. Total $ 8,738 z Terminal Services – Terminal Services is a set Wyse thin clients of software capabilities that is part of newer 5 Wyse Winterm 5150SE $ 2,055 versions of Microsoft Windows. It lets a user Citrix 5-user license $ 1,017 access applications on a server over a Total $ 3,072 network connection using RDP. PCs 5 Dell OptiPlex 210L $ 4,215 Costs to consider Total $ 4,215 Accurate cost assessments of thin clients can be difficult because thin clients require a supporting As you can see, both types of thin client devices hardware and software infrastructure that is not always were significantly cheaper than the PCs. The Sun immediately evident. In the following sub-sections, we Ray 2 devices, however, required a Sun Fire v240 examine the key types of costs that organizations may server to be able to talk to our test Windows face when adopting thin clients. server, so the total cost of the hardware necessary to run the Sun Ray 2 thin clients was actually Thin client hardware higher than that of the PCs. (Sun has since Not many years ago, the purchase price difference announced the ability to run the Sun Ray clients between PCs and thin clients was huge. Today's lower directly against the Windows server using RDP, so PC costs have cut into that difference significantly. It is this cost would go away.) The Wyse clients still the case, however, that many thin client hardware required a Citrix license, which brought their devices are significantly cheaper than PCs--as long as purchase price up significantly. you consider only the cost of the device itself. Note also that we did not choose anywhere near The story becomes more complex when you factor in the cheapest PCs available. Instead, we went for the software and, in some cases, hardware necessary standard OptiPlex systems with Intel processors to support the thin clients. Bob O’Donnell’s guidance with HT Technology. from the 2005 IDC thin-client market analysis included this observation: “One critical point that thin client All that said, the per-seat cost of the hardware vendors need to plan for is the rapidly approaching devices themselves is clearly lower with thin price points of low-cost PCs….the purchase price-only Principled Technologies, Inc.: Thin clients: Understanding the costs 3 clients, though by far smaller a margin than in the past. increasing the available bandwidth out of the data center; we discuss this topic further in the next The total hardware cost, however, is actually greater section. than this picture shows, because the thin clients by their very mode of operation demand more computing This approach can also be a problem for highly power from servers than PCs and thus lead to higher distributed organizations, because in such groups server hardware costs. many user communities may not be near a corporate data center. For those groups, the local As our tests found equipment room, often known as the "wiring (http://www.principledtechnologies.com/clients/reports/ closet," may be the only viable solution. Intel/ThinvsPCperf.pdf), in many common business scenarios PC clients place relatively small demands Many organizations call these rooms wiring on servers, while thin-client demands can be closets because that's what the rooms used to be. significant. The following subsection examines the Often, phone and network cables terminate there, types of application server costs that adopting thin so the room has some power and contains one or clients can bring. more network devices, such as a switch or router. Such devices do not, however, typically have the Application servers power or cooling requirements of servers.
Recommended publications
  • Key Features in Windows Server 2008 R2 and Windows Server
    With Windows Server® 2008 R2 Remote Desktop Services (RDS), Microsoft is progressing in its vision to provide the best virtualization platform for accelerating and extending desktop and application deployments from the data center to any device. In addition to the traditional session virtualization scenario (formerly known as “Terminal Services”), Remote Desktop Services is expanding its role to provide an extensible platform for a Virtual Desktop Infrastructure (VDI). RDS is a cost-effective infrastructure platform for any type of organization, particularly those with a roaming workforce, structured task workers or knowledge workers with a need for flexible desktop or application access, including contractors, offshore workers and office workers that require a free seating environment or have a need to work from home. SOLUTION BENEFITS ACCELERATE DESKTOP & APPLICATION HELP SECURE DATA AND INCREASE REMOTE WORKER DEPLOYMENT APPLICATIONS EFFICIENCY Remote Desktop Services accelerates and Remote Desktop Services helps Remote Desktop Services helps extends the deployment of desktops and organizations keep critical simplify remote connectivity, applications to a wide array of client devices, intellectual property highly secure enabling rich applications to be helping make your organization more agile and helps radically simplify accessed from a web page and and responsive. RDS also enables flexible regulatory compliance by removing seamlessly integrated with a local work scenarios such as hot-desking and work applications and data from the desktop, improving remote worker from home. desktop. efficiency. Key Features in Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1: • Microsoft RemoteFX introduces a new set of end user experience capabilities, enabling local-like access to media-rich applications for virtual and session-based desktops; it can be deployed to a range of thick and thin client access devices.
    [Show full text]
  • Rich Client Architecture
    Base One International Corp. www.boic.com Base One's Rich Client Architecture Base One provides a unique approach How Rich Client works for developing Internet-enabled applications, combining both efficiency and ease of programming through its "Rich Client" architecture. With this architecture, it is possible to build graphically intensive programs that look and perform like sophisticated client/server Windows applications, but where data is actually stored and retrieved across the Internet. At the same time, Base One makes it easy to develop such applications on a laptop or desktop and deploy them over the Internet without any changes. In Base One's model, each Rich Client looks like In contrast to thin client models, a rich a normal database application - because a Base client application shifts the burden away One Internet Server (BIS) acts as a transparent from shared network resources and proxy for a database across the Internet. server machines onto client computers, for better overall performance and application flexibility. While many applications are adequately handled by thin client architectures, some applications are much better suited to Base One's Rich Client model. (See table below for the types of applications that benefit the most.) A Service Oriented Architecture Like systems based on Web Services, Base One's Rich Client model is also a type of Service Oriented Architecture (SOA). It comprises independent, co- operating components (services) that can be distributed within or outside of an A Rich Client consists of a custom application organization's physical boundaries and written in Visual C++, C#, VB or VB.NET, using security domains, using varying platforms Base One's class libraries (BFC), and running on and programming languages.
    [Show full text]
  • Better Together: Rich Client Pcs and Cloud Computing
    IT@Intel Brief Better Together: Rich Client Intel Information Technology Computer Manufacturing PCs and Cloud Computing Cloud Computing Cloud computing poses new questions about the optimal March 2009 Profile: Rich Clients and enterprise client computing strategy. With more and more Cloud Computing services delivered from the cloud, which combination of • Users can access both cloud and client platforms and service delivery models best meets conventional computing services the needs of users and IT organizations? The Intel IT environment contains a mixture of • All service delivery models supported conventional and cloud computing services, delivered primarily to rich client PCs. We have found that whether services are kept in-house or outsourced to the cloud, the ability to perform local computing on the client offers the best user experience and the flexibility to run different types of applications. Only rich clients support the full range of service delivery methods, as shown in Figure 1. In addition, rich clients deliver full mobile computing capabilities for our users, including the ability to work offline. Rich clients remain an important part of our IT strategy as we work toward our future direction of migrating services to the cloud, supporting a wider range of client platforms, and enabling client virtualization. External Cloud Internal Cloud Software as a Service (SaaS) Applications Remote Access • Staffing • Other SaaS Applications and Portal Services • Messaging and Collaboration • Productivity Applications • Benefits • Hosted
    [Show full text]
  • Global Supplier Info Pack
    Global Supplier Info Pack FEDE Integration List of Fact sheets available List of Fact sheets available .............................................................................................. 2 First Steps: ....................................................................................................................... 4 What is FEDE [Ford Engineering Design Environment]? ..................................................... 4 GSI Overview .................................................................................................................... 4 Global Supplier Implementation (GSI) ....................................................................................... 4 FEDE process flow chart .................................................................................................... 6 FEDE Website Access ...................................................................................................... 10 Methods Pages Access .................................................................................................... 10 1. Supplier Company Access ................................................................................................... 11 2. Supplier Access Gatekeeper (SAG): ...................................................................................... 11 3. Supplier User Access: .......................................................................................................... 11 Direct Connection options - functionality comparison.....................................................
    [Show full text]
  • „Thin Clients Vs. Rich Clients
    Diplomarbeit „Thin Clients vs. Rich Clients Grundlagen, Features und Einsatzgebiete“ Ausgeführt zum Zweck der Erlangung des akademischen Grades eines DI (FH) für Telekommunikation und Medien am Fachhochschul-Diplomstudiengang Telekommunikation und Medien St. Pölten unter der Leitung von DI Grischa Schmiedl ausgeführt von Martin Berger 0210038010 Zweitbegutachter: FH-Prof. DI Georg Barta St. Pölten, am 05. September 2006 Unterschrift: Ehrenwörtliche Erklärung Ich versichere, dass • ich diese Diplomarbeit selbständig verfasst, andere als die ange- gebenen Quellen und Hilfsmittel nicht benutzt und mich auch sonst keiner unerlaubten Hilfe bedient habe. • ich dieses Diplomarbeitsthema bisher weder im Inland noch im Ausland einem Begutachter/einer Begutachterin zur Beurteilung oder in irgendeiner Form als Prüfungsarbeit vorgelegt habe. Diese Arbeit stimmt mit der vom Begutachter beurteilten Arbeit über- ein. ……………………………….. …………………………………... Ort, Datum Unterschrift Kurzfassung In dieser Diplomarbeit werden die Ansätze Thin und Rich Client näher betrachtet sowie deren Vor- und Nachteile gegenübergestellt. Es wird ebenfalls bei beiden Ansätzen zwischen Hard- und Software un- terschieden, da die Begriffe für beides verwendet werden. Dazu wird ein Beispielbetrieb analysiert. Ein Thin Client – von der Hardwareseite aus betrachtet – ist ein etwa modemgroßer Rechner mit CPU, RAM und Grafikkarte. Allerdings be- sitzt er keine lokalen Speichermedien wie z. B. Festplatten. Der Unter- schied zu einem klassischen Terminal liegt darin, dass der Thin Client selbst einen Browser und/oder eine Javaumgebung ausführt. Innerhalb dieser werden Thin Client Applikationen lokal ausgeführt. Der Browser kann zum Beispiel auf einem internen Flashspeicher oder auf einem Chip (etwa vergleichbar mit dem BIOS) gespeichert werden. Der Gedanke hinter einer Thin Client-Applikation ist der, dass alle Da- ten vom Server bezogen und sämtliche Verarbeitung von Benutzerein- gaben sowie Berechnungen der Geschäftslogik vom Server durchge- führt werden.
    [Show full text]
  • Windows Virtual Desktop Solution Brief
    Windows Virtual Desktop Solution Brief The best virtual Windows and Office experience, delivered on Azure Delivers the only multi-session Windows 10 experience Take the self-assessment Access the fully managed, always up to date, rich Windows user experience from any end-user to see if Windows Virtual device platform with your choice of virtualised OS, including Window 7. Client-like experience includes Cortana, Edge, desktop search, and Microsoft Store. Desktop is right for you: You have complete access control for security and cost efficiencies. You need the ability to Enable optimizations for Office 365 ProPlus add users quickly and Deliver the best Office 365 ProPlus experience in a multi-session environment to your users. New easily Container technology enables fast load times and provide a performant experience for Outlook, You need to scale OneDrive, Cortana, Search, Skype. Create persistent and non-persistent environments, efficiently on demand Virtualise entire desktop or select applications only. Your end-users need Deploy and scale in minutes a seamless rich client Manage users and security via a unified administrative interface in the Azure Portal. experience with Outlook, Use familiar tools like Rest API & PowerShell to customize setup, deployment & UI. Dynamically Search, Cortana, scale virtual machines using depth-first or breadth-first load balancing. Benefit from the integrated OneDrive, and Skype security and management of Microsoft 365 and rich partner solutions. You need to manage different deployment Migrate your existing Windows Server (RDS) desktops and apps to Azure types across different Bring existing Remote Desktop Services (RDS) and Windows Server desktops and apps to any deployment planes computer.
    [Show full text]
  • The Eclipse Rich Client Platform (RCP)
    Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, IBM Corporation The Eclipse Rich Client Platform (RCP) Chris Laffra IBM Ottawa Labs http://eclipsefaq.org/chris Chris Laffra — The Eclipse Rich Client Platform (RCP) Page 1 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, IBM Corporation Roadmap Introduction Rich Client Programming The Eclipse RCP Project ¾Examples of RCP applications ¾All about plug-ins ¾Building your own Eclipse RCP application Conclusions Chris Laffra — The Eclipse Rich Client Platform (RCP) Page 2 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, IBM Corporation Source of Materials Material sources: ¾ RCP tutorials at eclipse.org ¾ RCP samples from eclipse.org ¾ Feedback from Eclipse committers ¾ The Official Eclipse 3.0 FAQs Æ Chris Laffra — The Eclipse Rich Client Platform (RCP) Page 3 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, IBM Corporation Format Each slide is one question with an answer We will introduce ¾ Some background; what is a Rich Client? ¾ The Eclipse project and RCP ¾ Show lots of sample code and demos After this presentation, you should be able to develop your own Eclipse RCP application. Chris Laffra — The Eclipse Rich Client Platform (RCP) Page 4 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, IBM Corporation What Is a Rich Client? Google dictionary: A computer program that can download files for manipulation, run applications, or request application- based services from a file server. Need some form
    [Show full text]
  • Smart Client Architecture and Design Guide
    Smart Client Architecture and Design Guide Foreword by Mark Boulter Smart Client Architecture and Design Guide patterns & practices David Hill, Microsoft Corporation Brenton Webster, Microsoft Corporation Edward A. Jezierski, Microsoft Corporation Srinath Vasireddy, Microsoft Corporation Mo Al-Sabt, Microsoft Corporation Blaine Wastell, Ascentium Corporation Jonathan Rasmusson, ThoughtWorks Paul Gale, ThoughtWorks Paul Slater, Wadeware LLC Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. © 2004 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Active Directory, BizTalk, InfoPath, MSDN, Outlook, Visual Basic, Visual C++, Visual C#, Visual Studio, and Win32 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
    [Show full text]
  • Client Virtualization Next-Generation Technologies Enable IT to Increase Productivity, Reduce Complexity, Cut Costs and Improve Management of Devices
    WHITE PAPER Client Virtualization Next-generation technologies enable IT to increase productivity, reduce complexity, cut costs and improve management of devices. It’s time to take a serious look. 1 Executive Summary Table of Contents 2 What Is Client Virtualization? 2 Why Client Virtualization? 3 Presentation Virtualization 4 Application Virtualization 5 Desktop Virtualization 6 Where Is the ROI? 6 Understanding the Risks 7 Managing the User Experience 7 Getting Started 8 CDW: Your Client Virtualization Partner Executive Summary For organizations with hundreds to thousands of endpoints, managing their devices can be an enormous challenge. Employees are more mobile than ever, working from home and on the road, and easy access to the Internet means that most organiza- tions now operate on 24x7 schedules, 365 days a year. The challenges and costs of supporting hundreds or thousands of users utilizing all kinds of devices is something IT has been trying to get under control for quite a while. Client virtualization brings a wide array of products and solutions that offer the promise of finally enabling IT to gain more control over their client infrastructure while at the same time still offering a rich, rewarding experience to users throughout the organization. With client virtualization, IT has the opportunity to reduce total costs, improve security, and enhance compliance and business continuity, thereby beginning to put in place an infrastructure that will be practical, efficient, flexible and scalable for years to come. 2 CLIENT VIRTUALIZATION What Is Client Virtualization? organization would expect to see after implementing client virtualization technologies. At its most basic level, client virtualization technologies enable Patch Management: Think about the tasks involved in patch IT to deploy both applications and desktops in a more efficient management.
    [Show full text]
  • Database Layout: Client Architecture
    There are two areas of consideration for the needs for data management software 1. Database layout: Centralized Data or Distributed Data 2. Client architecture: Thin-client or Rich-client Database layout: Centralized Data: Pros: Having your data centralized gives the obvious benefit of always having access to the most recent copy of the data. Cons: Computing resources must be shared amongst all logged in users. When querying information there is an increased risk of having "dirty" or "unfinished" data. Because the data originates at the local sites, local personnel may be required to resolve matches or fix problems directly in the central shared data. Legal ownership of and access to the centralized data must also be considered. Distributed Data: Pros: Database computing is distributed across all data systems separately and independently. Data can be "cleaned" prior to transmission to the upper level central database. Data is owned and maintained at local sites. This allows for independent data usage activities that may only be related to local sties. Redundancy provides backup. Cons: Updates to data come incrementally and depending on the system, the lower (source) databases are not updated with subsequent changes from upper levels. There is more effort required to support separate systems. Client architecture: Thin-client: Pros: Minimal installation on user computers. Often access is available from any computer with network access. Cons: Usability tied more closely to the network (speed, availability, security, etc) and sometimes limited in functionality. Lack of technology or network access restrictions prevent some local sites from connecting. Options: Citrix, Windows Terminal Services/Remote Desktop or access over a web page.
    [Show full text]
  • Smart Client in Business: Expanding the Edges of the Enterprise Network
    Smart Clients in Business: Expanding the Edges of the Enterprise Network White Paper Abstract In the past few years there has been a convergence of two distinct trends in business and technology. Organizations are seeking to extend their enterprises and provide knowledge workers with ever-greater mobility and access to information and applications. Powerful new computing and communications devices along with wireless networks are helping provide that mobility. This has sparked the creation of “smart clients,” or applications and devices that can take advantage of the power of local processing but have the flexibility of Web-based computing. This paper provides a high-level overview of smart clients, the highlights of the technology underlying them, and how businesses are taking advantage of Microsoft technologies to create and use smart clients to address business opportunities. Contents Introduction ................................................................................................................................ 1 Smart Clients: An Overview....................................................................................................... 2 Enabling Smart Clients with Web Services ............................................................................... 5 Creating Smart Clients............................................................................................................... 6 Smart Clients at Work Today.....................................................................................................8
    [Show full text]
  • Thin Client Glossary
    Thin Client Glossary A B C D E F G H I J K L M N O P Q R S T U V W X Y Z AS400 is the common way most people write AS/400 on the Internet. In keeping with this practice we have decided to use AS400 as the standard spelling in this glossary. A AS400 thin client An AS400 thin client is a thin client device which can access AS/400 / iSeries / System i data. AS/400 thin client The correct spelling of AS400 thin client. B Blade PC A blade PC, also called a PC blade, is a computer that is entirely contained in a thin, modular circuit card placed in a centralized, secure location such as a server rack. A cable connects the card to the user's display, keyboard and mouse...A blade PC, in contrast to a thin client, is a complete computer that includes all the components normally found in a desktop PC including the microprocessor, memory chips, hard drive, video card and network card. Boot image Boot image is a computer file containing the complete contents and structure of a computer storage media. When it is transferred on a boot device it allows the associated hardware to boot. This usually includes the operating system, utilities and diagnostics, as well as boot and data recovery information. In a thin client the word "thin" refers to the small boot image which such clients typically require to connect to a network and start up a dedicated web browser or Remote Desktop connection.
    [Show full text]