51
Application Deployment Architectures The "Rich" versus "Thin" debate and beyond Prepared for Microsoft UK Thursday 2 nd August 2007 Version 1.0 Compiled by Michael Royster, CEng Solution Architect Microsoft Limited [email protected]

Application Deployment Architectures - …SSL Gateway support Microsoft and Citrix Systems agree that Windows Terminal ... (such as typing in Microsoft Word), ... Application Deployment

  • Upload
    vuanh

  • View
    223

  • Download
    0

Embed Size (px)

Citation preview

Application Deployment Architectures

The "Rich" versus "Thin" debate and beyond

Prepared for

Microsoft UK

Thursday 2nd August 2007

Version 1.0

Compiled by

Michael Royster, CEng

Solution Architect

Microsoft Limited

Microsoft UK

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

The descriptions of other companies’ products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.

This deliverable is provided AS IS without warranty of any kind and MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OTHERWISE.

All trademarks are the property of their respective companies.

©2007 Microsoft Corporation. All rights reserved.

Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Page iiApplication Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Revision and Signoff Sheet

Change Record

Date Author Version Change reference

06/04/07 Mroyster .1 Initial draft for review/discussion

24/04/07 Mroyster .2 Included initial comments

04/05/07 Mroyster .3 Included Comments

01/06/07 Mroyster .4 Updated external citations

20/06/07 Mroyster .5 Included updated management summary from Roger Hordley

02/08/07 Mroyster 1.0 Included review comments from Jerry Fishenden

Reviewers

Name Version approved Position Date

Page iiiApplication Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Table of Contents

1 Executive Summary........................................................................................................................1

2 Application Deployment Architectures......................................................................................32.1.1 Alternative Options.............................................................................................................4

2.2 Traditional Windows Rich Client (Desktop and Notebook).....................................................4

2.3 Microsoft SoftGrid Application Virtualisation............................................................................72.3.1 Benefits.............................................................................................................................. 72.3.2 Components of Microsoft SoftGrid Application Virtualization.............................................82.3.3 Availability........................................................................................................................ 102.3.4 Further Information...........................................................................................................10

2.4 Microsoft® Windows Terminal Services.................................................................................102.4.1 Benefits............................................................................................................................ 112.4.2 Components of Terminal Services...................................................................................112.4.3 Future Enhancements with Microsoft Windows Server 2008...........................................122.4.4 Further Information...........................................................................................................12

2.5 Microsoft® SoftGrid for Terminal Services..............................................................................122.5.1 Benefits............................................................................................................................ 132.5.2 Components..................................................................................................................... 13

2.6 Citrix Presentation Server TM..................................................................................................132.6.1 Presentation Server Additional Benefits...........................................................................142.6.2 Further Information...........................................................................................................15

2.7 Windows Embedded Powered Thin Client Devices...............................................................152.7.1 Benefits............................................................................................................................ 152.7.2 Operating System Choices..............................................................................................162.7.3 Example Devices.............................................................................................................17

2.8 Blade-PC Solutions...............................................................................................................18

2.9 Windows Vista Enterprise Centralised Desktop....................................................................19

2.10 Pure Browser Based Solutions........................................................................................20

3 Addressing Common Arguments used against the Microsoft Platform................................223.1.1 Total Cost of Ownership...................................................................................................223.1.2 Reducing the power consumption....................................................................................243.1.3 Cost of Acquisition...........................................................................................................25

4 Selecting the most appropriate technology.............................................................................27

5 Conclusion.................................................................................................................................. 29

6 Selected Case Studies...............................................................................................................30

6.1 Traditional Windows Rich Client (Desktop and Notebook)...................................................30

6.2 Microsoft SoftGrid®...............................................................................................................31

6.3 Microsoft Windows Terminal Services...................................................................................31Page iv

Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

6.4 CITRIX Presentation Server™..............................................................................................32

6.5 Windows Embedded Powered Thin Client Devices...............................................................32

Page vApplication Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

1 EXECUTIVE SUMMARYThis paper discusses the benefits of the various application deployment architectures and how Microsoft technology can deliver these benefits for an organisation.

The growth and advancement of the personal computer has been driven by the demand from users for new, evolving, more sophisticated applications. This trend will continue. While this has delivered benefits, these advancements have increased the complexity and cost of the deployment and operation of these applications by IT departments. This increasing cost and complexity led, a decade ago, to the development of the server based deployment model (thin client) as one alternative deployment model for PC applications.

Ten years on, however, the traditional rich client deployment model still remains the predominant choice for most organisations, while browser based solutions have found their rightful place as the number one choice for applications which require the greatest reach, such as consumer oriented web sites. The traditional Windows rich client deployment model is still the most popular means of deployment, presenting the lowest capital cost and the highest quality user experience leading to increased availability and offline support. It supports a wider range of client devices and is suitable for the widest range of application types with the widest accessibility support.

This deployment model, for example, has enabled Cornwallis school in Maidstone, Kent, U.K, to deploy a new mobile solution that enhances the learning process for students. A Tablet PC device is given to each student when they enter the school, and this remains with them until the day they leave. Tablet PCs replace the use of conventional books and offer a range of award-winning content, including interactive multimedia learning resources. As a result the students were more enthusiastic and motivated. For further details of this and other case studies see Selected Case Studies.

The traditional rich client deployment model is not without its challenges, with the most commonly cited being the cost and complexity of application deployment, security (data on the client device), total cost of ownership (where uncontrolled changes are made by end-user), and, energy consumption (there is a growing focus upon the direct energy costs for operating IT).

Many of the challenges with the Windows rich client deployment model are not inherently rooted in the rich client itself. They are often more likely associated with the management of the user device which contributes to the cost and complexity of application deployment and TCO.

Additionally, there is a growing awareness of, and focus upon, the direct energy costs for operating IT and the associated heating, ventilation, and air-conditioning (HVAC) required. Microsoft recognises the financial and environmental impacts of this and with the introduction of Windows Vista has significantly improved the power management and its default settings which impact how PCs consume energy. Windows Vista introduces new power saving features; in particular Vista has significantly improved idle power consumption compared to Windows XP and earlier operating systems. A UK study1 has shown that these features translate to a reduction in running costs of between £23 and £46 per system per year, depending on the model. For a 200-seat organisation this equates to annual savings of between £4,762 and £9,274. In terms of the environmental impact, this reduction in power consumption translates into reductions in carbon dioxide emissions, measured in tonnes per year for a UK based organisation. For a 200-computer organisation, this could be around 44 tonnes of carbon dioxide per year.

The earlier challenges, then, led to development of server-based computing, or thin client. This is the most mature and common alternative deployment architecture and it puts the application back on the server where it can be managed centrally. When a user runs such an application, the application execution takes place on the server, and only keyboard, mouse and display information is transmitted over the network.

1 Power consumption & management: Windows Vista versus Windows XP, PC Pro Labs http://download.microsoft.com/documents/uk/business/PC%20Pro%20Labs%20White%20Paper%20Mar%202007.pdf

Page 1Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Examples of this model are Microsoft Terminal Services and Citrix Presentation ServerTM. In most instances the server-based computing model (thin client) has a lower TCO than unmanaged PCs, and provides easier deployments and rollouts.

Nevertheless, if the objective is to drive down overall IT costs, an optimally managed full PC desktop is often a preferable option to looking at alternative client deployment architectures. A Gartner study2 found that the direct costs of a thin client solution were actually higher than a well managed traditional PC.

The server based model is just one approach; an alternative is application virtualisation and streaming. Unlike the server-based computing model, applications running under the virtualised model actually run on the client device and have access to the local resources, enabling a similar user experience to the traditional rich client. Application virtualisation enables applications to run without the need to install them locally – and without affecting the host operating system or other applications. This reduces the cost, time and complexity of application deployments.

Today, there is no “one-size-fits-all” answer. Different applications have different characteristics which may make them more suited to the traditional rich client deployment model, while others may be more suited to a server based computing model. Many organisations are beginning to deploy a hybrid of traditional rich client with a server based computing model (and in some cases, application virtualisation where this is appropriate).

The impact on the productivity of the end users or their learning experience must be central to the decision of an application deployment strategy. Graphics and media have become more widely used and the Web has led people to expect easy interaction with software. These rich graphical multi-media applications are particularly suited to the traditional rich client deployment model. Some industry analysts are now predicting that the pendulum is now moving again towards the rich client.

Whether the appropriate deployment model is rich client, server based (thin client), or application streaming, Microsoft has a breadth of integrated products across the spectrum of deployment architectures.

2 TCO Comparison of PCs With Server-Based Computing, 15 June 2006 Mark A. Margevicius Michael A. Silver Page 2

Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

2 APPLICATION DEPLOYMENT ARCHITECTURES Organisations trying to find a single application deployment architecture which is correct for every application deployed in their organisation will find it an impossible task. There is simply no “one-size-fits-all” answer. Different applications have different characteristics which may make them more suited to the traditional rich client deployment model while others may be more suited to the server based computing model. Even the same application may be used differently by different classes of user: for example using the education sector to illustrate, students may use Learning Essentials for Office in the classroom while a teacher may wish to prepare a test at home using the same application using a laptop offline, with no connectivity. Individuals may also have their own specific requirements (such as accessibility needs) which may influence the appropriateness of the client deployment architecture.

Organisations need to avoid being drawn early into “black-and-white” technology choices and ensure the business objectives are truly considered. Within these objectives the impact on end-users must be central in consideration: too often an IT organisation’s own needs can outweigh those of the end-user. The impact on the productivity of the end users or their learning experience should be central to the decision of application deployment strategy.

Organisations should expect to deploy a hybrid of traditional rich client and server based computing model where they are appropriate. Typical scenarios where the server-based model should be considered include:

Delivering complex applications when bandwidth limited

Securely delivering native Windows application outside the firewall

Delivering Windows applications that are updated very frequently, or are hard to install or manage on rich clients

Delivering a new application to large number of users simultaneously

Having to roll out a centralised application into a heterogeneous organisation with no centralised image management or software distribution

Supporting a user population that predominantly shares desktops (e.g. shift workers)

Recently, graphics and media have become more widely used, and the Web has conditioned a generation of people to expect easy interaction with software. The trend is for more and more rich graphical multi-media applications which are particularly suited to the traditional rich client deployment model.

The introduction of Microsoft Windows Presentation Foundation in Windows Vista (also available for Windows XP) allows the building of interfaces that incorporate documents, media, two- and three-dimensional graphics, animations, Web-like characteristics, and much more. This is the start of a new generation of applications that require higher levels of graphical hardware support – mandating more powerful client devices. Some industry analysts are predicting that the pendulum is now moving again towards the rich client.

Whether the appropriate deployment model is rich client, server based (thin client), or application streaming. Microsoft has a breadth of integrated products across the spectrum of deployment architectures, with many products leading their respective markets: for example Microsoft technology powers more than 70% of all specialist thin client hardware devices sold world-wide.

The remainder of this paper discusses the benefits of the various deployment architectures and how Microsoft technology can deliver these benefits for an organisation.

Page 3Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

2.1.1 Alternative OptionsWhen considering application deployment there are a number of potential architecture choices. The following sections highlight the benefits of the various options, the way they map to Microsoft (and partner) technology, together with a high-level overview of the technology.

Traditional Windows Rich Client (Desktop and Notebook)

Application Virtualisation - Microsoft SoftGrid®

Server Based Computing

Microsoft® Windows Terminal Services

Microsoft® SoftGrid® for Terminal Services

Citrix Presentation ServerTM

Windows Embedded Powered Thin Client Devices

Vista Enterprise Centralised Desktop (VCED)

Blade-PC Solutions

Pure Browser Based Solutions

Figure 1 Deployment Options

2.2 Traditional Windows Rich Client (Desktop and Notebook)By far the most common deployment model for PC-based Microsoft Windows applications is the traditional rich client deployment model. In this model the applications execute directly on the client PC taking advantage of the local machine’s resources, including the local processor, disk and attached peripherals. Even with the introduction of sever-based computing models in the early 1990s the traditional rich client deployment model has remained the predominant choice for good

Page 4Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

reasons. PCs tend to be relatively inexpensive to buy, provide superior performance, provide a higher fidelity user experience, and provide users with familiar levels of control and management.

Benefit Description

Lower Capital Cost Unlike the server-based computing model (which has a dependency on both the servers to execute the applications plus the local client device), with the rich client model the processing is pushed back to the client devices, allowing the application to run without any server dependencies. In the server-based thin client model, with each server typically supporting 50 to 70 users, the capital costs of the servers soon ramp up to support any sizable user population,

The seemingly ever decreasing capital cost of PC’s allows the rich client model to offer the lowest overall capital cost in comparison to the server-based thin client deployment models.

Highest Quality User Experience

Utilisation of client processing power ensures an application’s performance is optimal and offers the highest level of responsiveness. End users do not experience any delays when completing time-sensitive complex processes like data validation, data manipulation (sorting, filtering, etc.) and real-time data visualisation. The use of the local graphics card ensures multi-media and graphics intensive applications provide the highest quality experience.

The high quality user experience increases the end-user’s productivity or learning experience.

Supports a wider range of client devices

The PC evolved during its 25 year history into a number of different formats and the traditional mouse and keyboard are no longer the only input devices. For example the TabletPC is equipped with a sensitive screen designed to interact with a complementary pen. You can use the pen directly on the screen just as you would a mouse to do things like select, drag, and open files; or in place of a keyboard to handwrite notes and communication. The ability to write notes is particularly suited to the traditional classroom and lecture environment.

Speech recognition is also making continual advances and is now included as a standard component of Windows Vista. Such features can be invaluable in meeting accessibility requirements for all users.

To exploit the full benefits of these new client devices requires the exploitation of the local client resources and are therefore only available in the rich client deployment model.

Increased availability and offline support

Unlike the server-based computing model which has a dependency on the availability of the central server or network, the rich client solution can continue to function should these be unavailable.

The rich client can also support connected and disconnected operations — where a single application can be run both online and offline using the same technology. This enables workers or students to continue to use an application without being connected to the network. The example which will resonate with most people is working

Page 5Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

with Microsoft Office offline, such as creating documents or working with email without any network connectivity.

Suitable widest range of application types

Access to the client processing power ensures the rich client deployment model is suitable for the widest range of applications. With the server-based computing model there are certain classes of application that are unsuitable for this type of deployment model including:

Applications exploiting sophisticated graphics, such as multimedia, audio-video conferencing and eLearning applications.

High-end engineering applications that may be CPU intensive.

3D modelling applications (e.g. AutoCAD® , MSC Nastran).

Even applications such as Microsoft Office have implications on their deployment in a thin-client environment, which are not applicable to a rich client deployment. For example, when you install Microsoft Office in a Terminal Services/Citrix environment, the users who connect to the server are limited to the configuration you created and they cannot add or remove features. If users need different feature sets, you need a separate terminal server for each configuration.

Widest Accessibility Support

The traditional rich client deployment also offers the widest range of accessibility support which is not available in thin client deployment models. For example access technology used by blind and partially sighted people, such as screen magnification or speech and Braille output systems (known as ‘screen readers’) typically rely on capabilities of the local PC to function correctly.

Thin client solutions rely on only small parts of the display change when applications are used, so very little image data needs to be transmitted between the client and the server. When using screen magnification, much more displayed information changes all the time, so a much larger amount of data has to be transmitted between the terminal and the client. This leads to poor responsiveness, making magnification impossible to use.

For a wider independent discussion See Accessibility Issues within a Terminal Server Environment, Ruth Loeb, Senior ICT Development Officer, RNIB Digital Accessibility http://www.rnib.org.uk/xpedio/groups/public/documents/publicwebsite/public_terminalserversword.doc

According to a 2004 Forrester Research study commissioned by Microsoft, some 57 percent of computer users are likely or very likely to benefit from the use of accessible technology due to experiencing a mild or severe difficulty/impairment. See Accessible Technology in Computing Examining Awareness, Use, and Future Potential, Forrester http://download.microsoft.com/download/0/1/f/01f506eb-2d1e-42a6-bc7b-1f33d25fd40f/ResearchReport.doc

Integration with Local The rich client model also enables applications to use a wide range of

Page 6Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Peripherals connected peripheral devices from within the application: for example, an intelligent whiteboard. With the thin client server based model not all local peripherals are available to the server-based application, in particular certain USB devices.

Graphics and media have become more widely used, and the Web has conditioned a generation of people to expect easy interaction with software. The more time people spend interacting with applications, the more important the interfaces to those applications become. To keep up with increasing expectations, the technology used to create user interfaces must also advance. In recognition of this Microsoft has developed Windows Presentation Foundation (WPF), which is shipped as part of Windows Vista (and also available for Windows XP). WPF allows the development of interfaces that incorporate documents, media, two- and three-dimensional graphics, animations, Web-like characteristics, and much more. This is the start of a new generation of applications that require higher levels of graphical hardware support which will mandate more powerful client devices.

The traditional Windows rich client deployment model however is not without its drawbacks, with the most widely cited being:

Higher Total Cost of Ownership: many studies have demonstrated that the total cost of ownership of the rich client deployment model is higher than thin client model in an unmanaged environment.

Security: with data persisted to the client device there is an increased risk of unauthorised access to the data, with the theft of laptop devices together with the content of their local hard disks being a high profile scenario. New technology such as Microsoft Windows® BitLocker™ Drive Encryption in Windows vista is helping mitigate some of these risks.

More difficult to manage: the complexity of deployment and version compatibility testing can make rich client deployments difficult to manage without the right supporting tools.

These drawbacks are discussed further in the following sections, in their inverse format – as benefits to alternative deployment models.

2.3 Microsoft SoftGrid Application VirtualisationToday, the Windows desktop in many organisations has many applications installed onto it. Each installed application – plus patches and updates – requires lengthy compatibility testing and deployment processes before it reaches production. This testing is required since each application installation can potentially impact an existing installed application.

Microsoft SoftGrid® is an Application Virtualisation and Streaming technology which eliminates the traditional, tedious application management steps – including regression testing and installation/uninstalls – dramatically reducing labour costs.

2.3.1 Benefits

Benefit Description

Accelerate application management

By eliminating many tedious application management processes—including testing and installations—and enabling applications to run on clients without being installed on them, SoftGrid accelerates the entire process. Your IT team can easily assign the latest approved applications to end users, who access them by simply clicking an icon.

Page 7Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Reduce total cost of ownership

SoftGrid significantly reduces application management labor costs by streamlining, automating, and eliminating complex tasks. And because the applications are not installed on the PC, it also greatly increases application reliability because they no longer conflict with one another. It also enables applications that are not performing properly to be refreshed instantly. This means increased user productivity and reduced helpdesk and IT expense.

Ensure continuity of applications and user uptime

End users don't have to worry about losing productivity from application downtime because SoftGrid enables users to access their applications even during unplanned outages or scheduled migration projects. With SoftGrid, virtualized applications can be replicated to a backup site like any other enterprise data to maintain instant-on failover for applications, with user preferences totally intact. Users can also roam freely from computer to computer, confident in their ability to access the applications needed to perform their jobs.

Simplify IT environments

SoftGrid centralizes application management, enabling easy application delivery to any client device from a single management console. It also simplifies operating system (OS) and desktop administration. Because most applications do not have to be repackaged for OS migrations, even large-scale projects can be handled quickly and easily. In addition, by minimizing the number of applications in OS images, SoftGrid decreases image size and complexity and enables organizations to standardize and consolidate images, simplifying maintenance.

SoftGrid customers consistently validate these findings in their own implementations. For example, at Clarion Health Partners, instead of taking three to four weeks and costing $3,500/application, it estimates that SoftGrid is cutting the time to just three days and the cost to just $500/application. Scotland’s Dundee City Council estimates they saved £155,000 on IT support, replacement, server consolidation and license.

2.3.2 Components of Microsoft SoftGrid Application VirtualizationSoftGrid is the only application virtualisation solution on the market to deliver software that is never installed, yet securely follows users anywhere. It consists of the SoftGrid® Platform, an engine that turns applications into centrally managed virtual services that are delivered instantly.

SoftGrid consolidates each step of the application management lifecycle, changing it from a series of separate, manual processes into an automated, unified system that accelerates the pace of doing business. As a result, SoftGrid makes it easy to transform your entire IT environment into a utility: centrally manageable, measurable and easily used by IT and business users with a simple click of a mouse.

2.3.2.1 The Softgrid Application Virtualisation PlatformSoftGrid drastically reduces the complexities inherent in deploying and updating applications and simplifies overall Windows desktop administration through the following technologies:

Page 8Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Application virtualisation: Enables applications to run without the need to install them locally – and without affecting the host operating system or other applications. This eliminates application conflicts and allows applications to be handled like any other enterprise data.

On-demand streaming: Applications are instantly delivered to the desktop resource that needs them, upon user demand. Rather than "pushing" down and installing entire applications, the first time an application is requested, the client rapidly "pulls" only the code necessary to start the program from a central Server—typically 20–40% of the total code.

Centralised, policy-based management: Everything from deployment, patching and updating through application support and termination is managed for all users – including mobile, branch office and disconnected users – via policies and administered through a single console.

Software asset tracking: Real-time application usage tracking makes it easy to determine how applications are – or are not – being used so you can better manage license compliance.

Business continuity: Applications and updates can be replicated – just like data – to back-up servers, and application states and user profiles can be instantly restored, cutting end-user downtime from hours or days to just minutes.

Branch server infrastructures: Application updates and patches can be replicated to branch office servers – minimising WAN traffic while keeping application management centralised.

Figure 2 SoftGrid Components

Page 9Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

2.3.3 AvailabilityFrom June 2007 SoftGrid Application Virtualisation for Desktops is only be available through the Microsoft Desktop Optimisation Pack for Software, Microsoft SoftGrid Application Virtualisation for Terminal Services will continue to be sold as a perpetual CAL.

The Microsoft Desktop Optimisation Pack for Software Assurance is an add-on subscription license available to Software Assurance customers. It uses innovative technologies to help reduce the total cost of ownership (TCO) of the Windows desktop by accelerating operating system and application management and enhancing IT responsiveness and end-user uptime. It will enable you to better control the desktop, accelerate and simplify desktop deployments and management, and create a dynamic infrastructure by turning software into centrally managed services.

The Microsoft Desktop Optimisation Pack for Software Assurance provides 4 technologies:

Microsoft SoftGrid Application Virtualisation

Microsoft Asset Inventory Services is designed to analyse all programs on employee PCs, and provide the most current, accurate inventory.

Microsoft Advanced Group Policy Management increases control over Group Policy Objects (GPOs) – the component rules within Windows’ administrative management system – and is intended to allow IT administrators to delegate or assign administrative control of specific tasks based on employees’ titles or roles.

Microsoft Diagnostic and Recovery Toolset makes it possible for the IT department to quickly pinpoint the causes of PC troubles, recover lost data and prevent future downtime with post-crash analysis.

2.3.4 Further InformationFor further information on Microsoft SoftGrid Application Virtualization, see

Application Virtualization: The Next Frontier http://download.microsoft.com/download/6/4/f/64f5dc66-832a-4df3-baf4-3b4e7fb9e500/SGAV%20White%20Paper%20-The%20Next%20Frontier.pdf

Microsoft Desktop Optimisation Pack for Software Assurance http://download.microsoft.com/download/6/4/F/64F5DC66-832A-4DF3-BAF4-3B4E7FB9E500/datasheet-overview.pdf

Microsoft SoftGrid Application Virtualization Under the Covers—Exploring the SoftGrid Platform http://download.microsoft.com/download/6/4/f/64f5dc66-832a-4df3-baf4-3b4e7fb9e500/WP%20-%20SG%20Under%20the%20Covers%20-%20Arial.pdf

Return on Virtualization (ROV): Calculating the Economic Impact of SoftGrid, http://download.microsoft.com/download/6/4/f/64f5dc66-832a-4df3-baf4-3b4e7fb9e500/WP%20-%20SG%20Return-on-Virtualization.pdf

2.4 Microsoft® Windows Terminal ServicesTerminal Services is a component of Microsoft® Windows Server™ 2003 which builds on functionality provided in Windows 2000 Terminal Services and Windows NT 4.0 (Terminal Server Edition). Terminal Services lets you deliver Windows-based applications, or the Windows desktop itself, to virtually any computing device—including those that cannot run Windows, for example an Apple Mac.

When a user runs an application on Terminal Services, the application execution takes place on the server, and only keyboard, mouse and display information is transmitted over the network. Each

Page 10Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

user sees only his or her individual session, which is managed transparently by the server operating system, and is independent of any other client session.

2.4.1 Benefits

Benefit Description

Reduces Cost and Complexity of application deployment.

Terminal Services provides the ability to centralise application access and deployment. Centralised application access is gaining momentum as a way to reduce the deployment costs for applications.

The centralised deployment model significantly reduces the complexity of application deployments. Application deployments can be done without touching every desktop computer: simply install the application on a terminal server, and it will be available to information workers the next time they log on to the server.

Rapid, centralised deployment of applications

Terminal Services is suited for rapidly deploying Windows-based applications to computing devices across an organisation — especially applications that are frequently updated, infrequently used, or hard to manage.

When an application is managed on Terminal Server, and not on each device, administrators can be certain that users are running the latest version of the application.

Low-bandwidth access to data

Terminal Services considerably reduces the amount of network bandwidth required to access data remotely.

Using Terminal Services to run an application over bandwidth-constrained connections, such as dial-up or shared WAN links, is very effective for remotely accessing and manipulating large amounts of data because only a screen view of the data is transmitted, rather than the data itself.

Windows anywhere

Terminal Services helps users become more productive by enabling access to current applications on any device—including under-powered hardware and non-Windows desktops.

Improved Security Terminal Services can improve the security of some application types which traditionally maintain data locally. Using the server model the data is always retained securely in the data centre and not persisted to local PC.

2.4.2 Components of Terminal ServicesTerminal Services provides remote access to a Windows desktop through “thin client” software, allowing the client computer to serve as a terminal emulator. It provides an effective and reliable way to distribute Windows-based programs, providing a single point of installation with multiple users having access to the Windows Server 2003 operating system desktop, where they can run programs, save files, and use network resources as if they were sitting at that computer.

Terminal Services comprises two major components:

Page 11Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Terminal Services Client, called “Remote Desktop Connection,” (RDC) is an application that establishes and maintains the connection between a client and a server computer running Terminal Services.

Terminal Server provides the ability to host multiple, simultaneous client sessions on a Microsoft Windows Server 20033. The Terminal Server is an integral part of the operating system and is resident on the server at all times, regardless of whether Terminal Services is enabled or not.

A Terminal Services client can exist in a variety of forms. Thin-client hardware devices that run an embedded Windows-based operating system can run the Terminal Services client software to connect to a server computer running Terminal Services. Windows, Macintosh, or UNIX computers can run Terminal Services client software to connect to a Terminal Services server to display Windows-based applications. This combination of Terminal Services clients provides access to Windows-based applications from virtually any operating system.

2.4.3 Future Enhancements with Microsoft Windows Server 2008With Terminal Services in Windows Server 2008 "Longhorn," further enhancements to Terminal Services will be provided. Terminal Services will provides seamless centralised access to individual applications without the need to provide the whole remote desktop. Applications running remotely are integrated with the local user’s desktop—looking, feeling, and behaving like local applications.

Organisations can provide access to these centralised applications, desktops, and resources from the Internet, by using HTTPS without needing to provide complete access via Virtual Private Network (VPN) or opening up unwanted ports on firewalls. This reduces the complexity needed to provide access to applications for users, partners, or customers.

For further information see Terminal Services in Windows Server “Longhorn” Beta 2 , http://www.microsoft.com/windowsserver/longhorn/terminal-services/default.mspx

2.4.4 Further InformationFor further information on Terminal Services, see

Technical Overview of Terminal Services http://www.microsoft.com/windowsserver2003/techinfo/overview/termserv.mspx

Deploying Microsoft Office 2003 in a Terminal Services Environment, http://www.microsoft.com/technet/prodtechnol/office/office2003/deploy/o2k3dpts.mspx

Licensing of Microsoft Desktop Application Software Through Terminal Services http://download.microsoft.com/download/1/7/7/17745e4a-5d31-4de4-a416-07c646336d94/desktop_application_with_windows_server_terminal_services.doc

2.5 Microsoft® SoftGrid for Terminal Services The individual benefits provided by Windows Terminal Services and SoftGrid can be combined using Microsoft SoftGrid for Terminal Services.

Server growth is a costly issue for organisations that rely on Terminal Services. To avoid post-installation application conflicts applications must be tested up front to determine which applications will collide and, therefore, must be separated and run on different Terminal Server silos – a time consuming and costly process. Servers are routinely underutilised because each one is locked into a specific configuration, capable of serving only a limited set of non-conflicting applications, typically using just 25% of capacity. Often, 20 servers are required to support 1,000 users. Microsoft SoftGrid for Terminal Services completely changes this situation.

3 Or Windows NT 4-Terminal Server Edition and Windows 2000Page 12

Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

2.5.1 Benefits

Benefit Description

Increase ROI for Terminal Server Farm

SoftGrid’s application virtualisation allows any application to run alongside any other— even applications that normally conflict, or multiple versions of the same application, and many applications that previously could not run under Terminal Services. This eliminates the need for server silos and significantly improves server utilisation. As a result, the number of servers needed is much lower, operational costs for managing the remaining servers are reduced, and the server farm ROI is increased. For instance, it has enabled a financial institution shrink their application server farms by 33–40%.

Reduces Application deployment time

By eliminating the need to permanently install applications on servers, and shielding the operating system and applications from changes created when installed applications run, Microsoft SoftGrid for Terminal Services prevents problems that hinder deployments. The need to perform lengthy regression testing is also significantly reduced.

Reduce application deployment costs

Applications that use SoftGrid only need to be packaged once for desktop or terminal services platforms. This reduces the need for "double packaging" or creating two different processes and packages when providing the choice for running an application on a desktop or via a Terminal Server. This simplifies administration, troubleshooting, and support.

Increase Application Availability

Replicate your virtualised applications like any other enterprise data to maintain an instant-on failover plan for your applications. Applications can be kept up to date between live sites and back-up sites by automatically replicating virtualised application files on the live sites’ SoftGrid servers to SoftGrid servers at a back-up site (using third-party tools).

2.5.2 Components The components for Microsoft® SoftGrid for Terminal Services are the combined components of Terminal Services and SoftGrid integrated together with Microsoft® SoftGrid for Terminal Services. See Figure 2 for details.

SoftGrid's unique approach enables applications to be centrally stored and then delivered and executed on Terminal Server on demand. Application files are only delivered once from the SoftGrid server to the Terminal Server, where they are cached for repeat use by multiple users. As a result, SoftGrid is a bandwidth-efficient method of distributing applications to Terminal Servers ensuring that the SoftGrid server can support many Terminal Servers and thousands of connected users.

2.6 Citrix Presentation Server TM

Microsoft Terminal Services and Citrix Presentation ServerTM (and its predecessor Citrix MetaFrame) both provide the same baseline server based computing functionality. As with Terminal Services, when a user runs an application on Citrix Presentation Server, the application

Page 13Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

execution takes place on the server, and only keyboard, mouse and display information is transmitted over the network.

Microsoft Corporation and Citrix Systems Inc. have a long established partnership agreement to facilitate sharing of technologies and patent licensing between Microsoft Terminal Services and Citrix Presentation Server. Since both products share a common base technology platform, Citrix offers the same benefits as those listed for Terminal Services previously. Citrix does however offer more features but with higher licensing costs.

2.6.1 Presentation Server Additional BenefitsThe following are additional benefits of Citrix Presentation Server 4.5 compared to Windows Server 2003 Terminal Services.

Benefit Description

Enhanced usability and performance of applications.

Citrix enhances the usability and performance of applications running on Terminal Services. This results in higher user satisfaction and eased support requirements for IT.

Examples include:

Faster Printing

Seamless concurrent use of local desktop and remote applications.

Ability to roam between devices and networks while maintaining their sessions.

Enhanced Management and Configuration

Citrix enhances Terminal Services with a set of mature and easy-to-use management and monitoring tools. This increases IT and user productivity and provides additional capabilities not available in the base-level Terminal Services environment.

Examples include:

Application and Content Publishing, allowing users to access applications from desktop shortcuts or the start menu rather than starting remote sessions.

Improved load balancing

Improved Compatibility

Citrix addresses the needs of heterogeneous IT environments by supporting a wide variety of devices and applications.

Examples include:

Wider range of client platforms including UNIX, DOS, Linux, IBM OS/2, SymbianTM and EPOCTM

Enhanced Security and Control

Citrix technologies enhance the security of a centralised architecture by providing additional security and control features.

Examples include

SSL Gateway support

Page 14Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Microsoft and Citrix Systems agree that Windows Terminal Services and Citrix both fulfil baseline server based computing functionality and can deliver the benefits of a thin client solution.

The question for an organisation is whether Terminal Services alone meets all your needs or whether you require the additional functionality provided by Citrix Presentation Server and that the benefits they bring outweigh the increased licensing cost.

For more a more detailed feature comparison, see

Citrix Value-Add to Windows Terminal Services. This Citrix Systems Inc. document compares the base-level features within Windows Terminal Services to the value-added features of Citrix Presentation Server 4.5. http://www.citrix.com/English/ps2/products/documents_onecat.asp?contentid=186&cid=White+Papers#top

The Difference between Microsoft RDP and Citrix ICA, http://msdn2.microsoft.com/en-us/embedded/aa714324.aspx

2.6.2 Further InformationFor further information see

Reduce IT Costs using Citrix Presentation Server 4, http://www.citrix.com/English/ps2/products/documents_onecat.asp?contentid=186&cid=White+Papers#top

Citrix Presentation Server 4.5 Product Overview, http://www.citrix.com/English/ps2/products/documents.asp?contentid=186#top

Citrix Presentation Server Comparative Matrix http://www.citrix.com/English/ps2/products/documents.asp?contentid=186#top

2.7 Windows Embedded Powered Thin Client DevicesWindows Terminal Services and Citrix Presentation Server are software foundations for thin client server based computing model based on the Windows platform. Although not inherently a "thin client," traditional PCs can be used as thin-client devices by running either Microsoft Terminal Services client software or Citrix Systems Presentation Server client software. In 2005 between 70 and 75% of thin client deployments continue to use a traditional PC as the thin client device.

As an alternative solution, specialist thin client hardware devices can be used to replace the traditional PC. The primary difference between a PC that is used as a thin client and a true thin client (in which all applications reside on the server) is the PC's ability to maintain some local storage and applications on the device. Whether the thin client is a specialist hardware device or a traditional PC the server infrastructure remains the same, i.e. Windows Terminal Services or Citrix Presentation Server.

2.7.1 BenefitsThe benefits of a specialist thin client hardware device are a combination of the benefits of using Terminal Services (or Citrix Presentation Server) and the following additional benefits:

Benefit Description

Lower Purchase Costs

Specialist thin client hardware devices have lower purchase costs than traditional PCs, although the cost differential has eroded recently. List prices for such devices start around £150. The reason for the differential is that these straightforward devices allow original equipment manufacturers (OEMs) to maintain a substantially lower bill

Page 15Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

of materials (BOM) cost on each device that they sell, because less powerful processors, more limited memory, and fewer parts overall can be used in designs.

Lower Total Cost of Ownership (TCO)

The maintenance costs of thin client devices can be reduced by as much as 80%4. Many thin client devices do not include any moving parts including hard disks and processor fans, which are the most common hardware failure points in hardware devices. This provides a very long (150,000 hours) Mean Time Between Failures (MTBF).

Being diskless, fanless and convection cooled the devices also benefit from being quieter.

Lower power consumption

The devices have lower power consumption, for example a Wyse S30 power usage is quoted as 5.6W-hours with 1 keyboard, 1 PS/2 mouse, and 1 monitor connected.

2.7.2 Operating System ChoicesWorldwide thin-client hardware shipments are continuing to grow at more than 30% per annum and top more than 2¼ million units. Wyse, Neoware and HP are three of the largest thin-client vendors, with an estimated 70 percent of the worldwide market. Microsoft’s operating systems power an estimated 70% of thin client devices shipped worldwide, with almost half equipped with Windows CE Embedded and 22% with Windows XP Embedded.

OEMs building thin client devices choose between Windows CE 5.0 and Windows XP Embedded based on how their customers will use the device: as a terminal that is only used to remotely run applications on a server; as a terminal with the addition of Web browsing capabilities; or as a locked-down device that can act as a thin client to a server, browse the Web, and run line of business (LOB) applications.

Windows CE 5.0 thin client features include:

Windows Terminal Server and Remote Desktop Protocol 5.5 support

Internet Explorer 6 for Windows CE.

Familiar and skinnable Windows desktop user interface.

Microsoft Device Management Client for Windows CE 5.0.

Microsoft .NET Compact Framework to run Web-based applications, XML Web services, and stand-alone applications.

Windows XP Embedded thin clients include most Windows CE 5.0 features as well as:

Over 9,000 component device drivers with device driver signing and rollback support.

Flexible boot and storage options (HDD, Flash ROM, battery-backed RAM, CD-ROM Remote Boot, and others).

Local and remote management services (Active Directory, Group Policy, Windows Management Instrumentation (WMI), Windows Script Host (WSH), Microsoft Management Console (MMC), System Deployment Image and Device Update Agent).

4 Source: Zona Research, Intelliquest, META Group StudyPage 16

Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Full .NET Framework to run Web-based applications, XML Web services, and stand-alone applications.

Full Win32 API support to run your Win32-based applications with little or no porting required.

The key benefit for XP Embedded are primarily being the wider peripheral support, the improved management and the flexible and remote boot capabilities. For a more complete comparison see Windows Embedded Operating Systems and Thin Client Requirements, http://msdn2.microsoft.com/en-us/embedded/aa714336.aspx.

2.7.2.1 Thin Client Device SegmentationThe growing local application functionality available in thin clients has resulted in three primary, industry-acknowledged device segments:

Basic terminals. Basic terminals are often used as terminal and green-screen replacements, offering a terminal services client and networking protocol support to connect automatically to a terminal server and access server-hosted applications. Terminals offer the lowest device acquisition cost and the least functionality, due to limited memory and storage requirements, the absence of moving parts, and overall simplicity of design.

Recommended Operating System: Terminal Windows CE 5.0

Browser terminals. In addition to basic terminal functionality, browser terminals add a local Windows-like UI shell and browser software, providing access to Web-based and Terminal Services-hosted applications.

Recommended Operating System: Windows CE 5.0 for Browser Terminals that are deployed and used primarily for accessing defined Intranet content. Windows XP Embedded for Browser Terminals that need broad access to Internet content and require the ability to download plug-ins and ActiveX Controls.

LOB terminals. In addition to basic and browser terminal functionality, LOB terminals add support that enables the local execution of a limited number (typically one) of managed or unmanaged applications in environments with non-persistent network connectivity or requirements for offline use.

Recommended Operating System: Terminal Windows XP Embedded

2.7.3 Example Devices Wyse S30, based on the new Windows® CE 5.0 operating system and features a

compact, sleek design with high-speed I/O, and innovative attachment system. http://uk.wyse.com/products/winterm/S30/index.asp

Wyse S90, A lightweight, compact, fanless, and diskless unit running Windows® XP Embedded. http://uk.wyse.com/products/winterm/S90/index.asp

HP Compaq t5520, Offering enhanced features for mainstream business use with support for legacy ports and software.http://h10010.www1.hp.com/wwpc/uk/en/sm/WF02a/35123-342039-342039.html?jumpid=in_r2515_tcs/psc

HP Compaq t5720, Powerful, innovative and secure – the industry’s most complete desktop alternative. http://h10010.www1.hp.com/wwpc/uk/en/sm/WF02a/35123-342039-342039.html?jumpid=in_r2515_tcs/psc

Neoware c50 is a speedy entry-level thin client with a high speed processor and double-speed memory. http://www.neoware.com/products/hardware/thin_client_c50.php

Page 17Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Neoware m100, mobile thin client notebook delivers productivity in a mobile environment, without sacrificing the security of thin client computing. http://www.neoware.com/products/hardware/thin_client_m100.php

2.7.3.1 Microsoft Windows Fundamentals for Legacy PCsMicrosoft Windows Fundamentals for Legacy PCs is a Windows-based operating system designed for customers who have older computers running earlier operating systems and who are not in a position to purchase new hardware. This operating system is available only to Microsoft Software Assurance customers and helps you get the most from your older hardware, thereby reducing your total cost of ownership. This Software Assurance benefit provides improvements to security and manageability to reduce the strain on your IT team, improve end-user productivity, and close security gaps.

Windows Fundamentals for Legacy PCs is based on Microsoft Windows XP Embedded Service Pack 2 (SP2), enabling you to upgrade to the security and stability of the Microsoft Windows XP platform. This eases the transition to Windows Vista Enterprise when you eventually replace your computers.

Windows Fundamentals for Legacy PCs is not a general-purpose operating system. It is designed to work with the Microsoft Remote Desktop Connection client or third-party clients such as the Citrix ICA client. In addition, it allows for a limited number of workloads to be executed locally, including security software, management software, terminal emulation software, document viewers, and the .NET Framework.

Benefit Description

Reduced cost of ownership

Repurpose older hardware as terminal services clients

Move line-of-business and productivity applications to the server

Run a fully supported Windows operating system

Install only the components your organisation requires to minimise on-disk footprint

Reduce help desk calls by delivering the same end-user experience to your entire organisation

Improved manageability

Use the latest management tools with older hardware

Bring old computers into your well-managed environment

Reduce the number of operating systems your organisation must support

Improved security Use the latest security tools with older hardware

Reduce the attack surface of all of your computers

2.8 Blade-PC SolutionsAn alternative server based solution is the Blade-PC. In this deployment model the PC’s primary functions (processing, disk storage and memory) remain in the data centre and only the presentation layer of the user interface (video, keyboard and mouse) delivered to the accessing device. This is common to how server-based computing solutions (such as Terminal Services or Citrix) operate; in fact most blade-PC solutions use the Microsoft Remote Desktop Protocol (RDP) as used by Terminal Services. However unlike the server-based computing solutions which include

Page 18Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

a server software component to share server resources, the clients of blades-PC are allocated a dedicated blade-PC on the server. The client access devices are very basic connection devices, with no local operating system or peripherals.

In some respects, the Blade PC architecture can be considered a different implementation from the traditional PC. However, Blade PCs generally allow a level of flexibility not associated with traditional PCs: when the user logs on, they are associated with an available blade, which then retrieves the user image from storage. The result is that a single access device can easily support multiple users without any additional security or management issues. Because Blade PCs are located inside the data centre, they are generally easier to manage and secure.

Benefit Description

Improved Security Blade-PCs can improve the security of some application types which traditionally maintain data locally. Using the server model the data is always retained securely in the data centre and not persisted to local PC.

Responsive and predictable end- user experience

Unlike server-based computing solutions where server load can impact the responsiveness of applications which can severely impair the end user experience. Blade PC’s have dedicated server processing which ensure the user experience remains consistent.

Reduced Support Costs

The centralised computing model reduces the support costs as Blade-PC deployments typically see a reduction in the number of break/fix help desk support calls.

Blade-PC solutions also have their downsides which include:

The initial cost and the devices typically have a higher acquisition cost than a traditional PC deployment.

The local access devices only support a very restricted set of peripherals and do not benefit from the wide device driver range which Windows powered embedded devices enjoy.

Blade-PC solutions tend to be used in more niche scenarios as they do not have all the benefits of traditional PCs and have higher costs than the more traditional server-based computing models

2.9 Windows Vista Enterprise Centralised DesktopFor enterprise early-adopter customers specifically looking to centralise Windows execution or storage, Microsoft provides two new options as part of Windows Vista Enterprise: Diskless PCs and Windows Vista Enterprise Centralised Desktop.

Windows Vista Enterprise

Diskless PCs and Remote Boot: Reduce TCO by eliminating PC hard drives and centralising data storage and applications. The operating system and applications use the PC hardware to execute locally.

Windows Vista Enterprise Centralised Desktop (VCED)

Centralised Desktop for PCs: Windows Vista Enterprise Centralised Desktop (VECD) provides licensing for Windows Vista Enterprise virtual machines (VMs) running on servers on

Page 19Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

top of PCs running Windows. This enables enterprises to combine PC productivity and local execution with the advantages of centralised deployment.

Centralised Desktop for Thin Clients: To centralise desktop computers on the server for thin clients, use Windows VECD to provide secure Windows Vista Enterprise VMs on a server-based infrastructure delivering the Windows experience to reduced desktop hardware.

VECD enables you to deploy Windows Vista centrally in VMs using the same base image you already deploy on the desktop. You can take advantage of the identical patching, application compatibility and support scenarios that you receive with traditional desktops. Equally important, VECD isolates users from each other through VMs, making it easier to enable scenarios such as outsourced development. Customers considering VECD should note that, like Terminal Services deployments, it requires a constant network connection.

Benefit Description

Increased Flexibility

Tailor deployment options to specific enterprise needs by using optimal combinations of:

Local VMs

Centralised desktop computers

Diskless PCs

Optional Microsoft SoftGrid Application Virtualisation, part of MDOP

Centralised Security

Improve security, protect and centralise corporate data, and simplify regulatory compliance:

Centralised data

Sandboxed virtual environments

Centralised applications and operating system with optional SoftGrid

Streamlined Deployment

Reduce TCO through streamlined and flexible deployment:

Reduce hardware costs

Reduce support costs

Centralised resource

2.10 Pure Browser Based SolutionsFor an organisation considering thin-client architectures there are essentially two fundamental approaches to choose from:

Server-Based Computing Model With a server-based computing model, applications run on a server, and the user interface is projected to the client for the look and feel of a Windows application. It is this model which is provided by Microsoft Terminal Services and Citrix Presentation Server discussed previously.

Browser-Based Model, In this approach, the user interface is simpler (less rich) than the server-based user interface because it is merely described to the client (HTML, DHTML

Page 20Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

and on-page scripting exclusively), rather than projected from its native platform GUI. Browser based solutions also have no permanent effect on the end-user’s computer after the browser has been exited (apart from the browser cache). This model provides greater scalability and reach to more users on more platforms.

The primary benefits of browser-based applications are well known: they are easy to install and maintain, can target many desktops, and have no impact on the state of the client computer.

The table below summarises the key benefits of the browser based model

Benefit Description

Widest Reach Browser based solution can run across the widest range of multiple platforms or browsers.

Reduces Cost and Complexity of application deployment.

The cost and complexity of application deployments is considerably reduced as browser solutions only require the solution to be published to the web site. There are no client side deployments required and no client side dependencies or interoperability issues which require consideration.

Greatest Scalability

Browser based solution provide the most scalable solution for very large user bases. In addition to the technology fundamentally scaling more efficiently, the server-based computing solutions typically have a cost per user which prohibits their use in large user bases such as public Internet solutions.

The most significant problem with pure browser-based applications is their update-and-refresh usage model. The model, with its absence of state on the client, no immediate user feedback and limited navigation model, all lessen the functional possibilities. The browser base model’s limitations include:

The perceived “slow” performance of browser-based applications (due to server round-trips and page download times) can significantly reduce user productivity or learning experience and negatively impact user satisfaction.

Lower fidelity user interface, as it is the browser not the application which controls the user input/output which again impact the user productivity or learning experience.

Browser solutions cannot easily exploit local peripheral devices.

No offline support, the browser based application cannot operate without the network and server being available.

Consider Amazon.com's web site, an excellent browser based order entry application. This is from a company which has invested millions of dollars improving usability as part of an ongoing improvement process. This investment shows – the interface is both intuitive and appealing to users. However even this exemplary illustration of browser based solutions lacks the immediacy and responsiveness that a “run of the mill” Windows application can provide. Amazon.com sets the usability bar very high, however not every Web app out there—in fact very few—offer the Amazon level of commitment, resources, or attention required to build really usable, intuitive, thin-client applications.

Browser based solutions have their place where reach is the primary driver and an application must target users spread across multiple organisations or consumer-based markets.

Page 21Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

3 ADDRESSING COMMON ARGUMENTS USED AGAINST THE MICROSOFT PLATFORM

3.1.1 Total Cost of Ownership “Our model shows that the thin-client solution will actually have higher direct costs than the well-managed traditional PC, although the significantly lower indirect costs more than offset them. Overall, our model shows that the TCO of a thin client is 9 percent to 12 percent lower than that of a locked-down, well-managed, traditional PC. Source: Gartner5

Many business cases supporting the server based computing model (thin client) are drawn up on the basis of reductions in TCO. The majority of these business cases use primarily savings in direct costs, i.e. the Hardware, Software, Operations and Administration as their primary justification. Independent studies have shown that thin client solutions actually have higher direct TCO costs than a well managed Windows XP desktop. Additionally, well managed desktops are shown to have lower downtime costs than a thin client solution.

The area where a traditional rich client deployment has higher costs is in indirect end-user operations costs including peer support, casual learning and self support, formal learning and file and data management. These costs however are much more subjective and dependent upon the end user environment. For example these costs would be lower for a student in a secondary supervised classroom environment compared to a knowledge worker in an office environment.

Where the TCO of the rich client is higher than the thin client is in the unmanaged desktop environment. If the an organisation’s objective is to drive down overall IT costs then introducing a managed full PC desktop is often a preferable option rather looking at alternative client deployment architectures. Below are just some of the Microsoft tools available which can help organisations manage their desk top population, and reduce the TCO:

Windows Group Policy

Microsoft Systems Management Server (SMS)

Microsoft Solution Accelerator for Business Desktop Deployment

Microsoft Application Compatibility Toolkit

An additional factor to be taken into consideration for a migration to thin client is the migration cost which is both economic and environmental. In adopting the hybrid approach which using a mixture of rich and thin clients as appropriate enables the repurposing of hardware replaced with a thin client device.

Windows Group Policy

A component of Windows which allows administrators to lock down a rich desktop in the same way as a terminal, preventing curious users meddling with their desktop’s operating system settings. Locking down the desktop can reduce the management and maintenance by more than 50%. Group Policy enables administrators to define and apply settings for groups of users which control such things as:

What is on the desktop (including lockdown) What is on the Start menu (including lockdown) What software is installed What access privileges Network locations Operating system configuration, including registry settings.

System Centre Configuration Manager

5 TCO Comparison of PCs With Server-Based Computing, 15 June 2006 Mark A. Margevicius Michael A. Silver Page 22

Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

System Centre Configuration Manager (previously known as Microsoft Systems Management Server) provides tools to automate and simplify application deployment, security and patch management, asset management, task automation, compliance management, and policy based security management.

Microsoft Solution Accelerator for Business Desktop Deployment

The Microsoft Solution Accelerator for Business Desktop Deployment (BDD) is part of a family of Microsoft solution offerings aimed at providing reusable components and repeatable processes to achieve timely and cost-effective information technology (IT) solutions.

The BDD solution is designed to help a team deploy Microsoft Windows XP Professional, Office Professional Edition 2003, and other applications quickly and reliably to computers across an organisation. It addresses both Windows XP Professional and Microsoft Windows XP Tablet PC Edition. The latest accelerator also include Windows Vista and the 2007 Office system.

To achieve this goal, this accelerated solution provides fully developed processes for:

Workstation imaging

Software and hardware inventory

Application compatibility evaluation and remediation

Application packaging and scripting

Network inventory and analysis

Workstation deployment, including data migration

Microsoft Application Compatibility Toolkit

The Microsoft Application Compatibility Toolkit is a lifecycle management tool that assists in identifying and managing your overall application portfolio, reducing the cost and time involved in resolving application compatibility issues, and helping you quickly deploy Windows and Windows Updates.

Microsoft Shared Computer Toolkit for Windows XP

The Toolkit is designed for people who want an integrated and easy solution that will help them to set up, safeguard, and manage shared computers so people can enjoy a more safe and private shared computing experience.

3.1.1.1 Management Tools Further Information System Centre Configuration Manager, http://www.microsoft.com/smserver/default.mspx

Solution Accelerator for Business Desktop Deployment Standard Edition http://www.microsoft.com/technet/desktopdeployment/bdd/standard/default.mspx

Solution Accelerator for Business Desktop Deployment Enterprise Edition http://www.microsoft.com/technet/desktopdeployment/bdd/enterprise/default.mspx

Microsoft Solution Accelerator for Business Desktop Deployment 2007 http://www.microsoft.com/technet/desktopdeployment/bdd/2007/default.mspx

Microsoft Application Compatibility Toolkit http://technet.microsoft.com/en-us/windowsvista/aa905102.aspx

Microsoft Shared Computer Toolkit for Windows XP, http://www.microsoft.com/windowsxp/sharedaccess/overview.mspx

3.1.2 Reducing the power consumption Enterprise IT staff are very aware of the energy costs for operating PCs and the associated heating, ventilation, and air-conditioning (HVAC) required. Vendors of thin client solutions

Page 23Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

frequently use the power consumption of the client device as a primary differentiator against Microsoft based solutions. For example “The typical power consumption of a Sun Ray 2FS client is only 7.86 watts. Compare this to PCs, which operate on 80 watts or more”, Source: Sun Microsystems. At first reading these arguments can often be misinterpreted for a number of reasons:

1. In the server based computing model the application is executed on the server, which requires additional servers which themselves consume power. Therefore to get the true power consumption this must be taken into account. The servers are also always powered on while the client will typically be in power saving modes when not in use.

2. The claims that a PC operates at 80W is just one quoted rating, The power consumption is dependent upon the type of PC, for example using a respected survey by the Lawrence Berkeley National Laboratory6, reported an average consumption for Pentium 4 desktop PC as 67W with laptops consuming 19W on average.

3. When comparing like-with-like, Microsoft powered thin client devices have a similarly low power consumption: for example Wyse S30 terminal running Windows CE is quoted as 5.6W-hours with 1 keyboard, 1 PS/2 mouse, and 1 monitor connected.

Taking these factors into account, the overall power consumption of a thin client deployment running with LCD monitors including the server estate and environment, operating 24 hours per day, is possibly little different to a rich client deployment of laptops running Windows Vista. There are no comparative studies of the two approaches currently published.

3.1.2.1 Power Consumption Improvements with Windows Vista Windows Vista introduces significant changes to power management and its default settings. These changes impact how PCs running Microsoft Vista consume energy.

Central to these changes is a new sleep state which significantly reduces the power consumption. A typical Pentium 4 PC with a 17" LCD monitor draws about 102.6 watts of power (67w and 35w for the PC and monitor respectively). That same PC and display in a sleep state draws only 5.6 watts, or 97 fewer watts. If you consider that a PC is used for active work for 10 hours a day, 5 days a week, 52 weeks per year, that is 2,600 operating hours. With 8,760 hours in a year (365*24), there are actually 6,160 potential idle hours per year. Since sleep mode uses 97 fewer watts than full power mode, the total savings is 597 kWh per year. The impact is obviously even greater (760 kWh) if you use a CRT monitor since they draw more power than LCDs.

Vista addresses many of the arguments that have blocked companies from adopting a power-management strategy. The Sleep state is now a much improved user experience – the fact computers resume from Sleep in under two seconds is almost the same amount of time that a screen takes to reactivate from Idle mode in Windows XP. Vista also has built-in management tools via Group Policy.

Financial Impact

A recent UK PC Pro Labs study compared two scenarios: Windows XP at its default settings and Windows Vista at its default settings. This survey found that Vista’s power conservation features equate to savings of between £23 and £46 per system per year7 in power consumption alone, depending on the PC model. For a 200-seat organisation this equates to annual savings of between £4,762 and £9,274.

6 Lawrence Berkeley National Laboratory, University of California "Energy Use and Power Levels in New Monitors and Personal Computers," Paper LBNL-48581, July 23, 200 http://repositories.cdlib.org/lbnl/LBNL-48581

7 All figures are based on a cost of 0.09p per unit (kWh).

Page 24Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

When a more aggressive power management policy was applied the survey found additional savings of up to £3 per system per year8 could be achieved.

The study was based on genuine usage patterns at work: these scenarios are based on the computer being idle for 40% of the time during an eight-hour working day. 30% of the time the computer is performing light tasks (such as typing in Microsoft Word), 15% of the time medium-intensive tasks (such as MP3 playback), and 15% of the time intensive tasks (such as video encoding).

In the XP default settings, the system will idle by default when not being used. In Vista, the system will go into Sleep mode after 60 minutes, and Hibernate mode after a further 18 hours. In the Group Policy scenario, machines were set to go into Sleep mode after 20 minutes and Hibernate after a further 60 minutes.

Environmental Impact

According to DEFRA (Department for Environment, Food and Rural Affairs), each kWh of electricity consumed via the UK mains equates to 0.43kg of carbon dioxide emissions. The PC Pro study demonstrated that Vista’s power savings translate to annual carbon dioxide emissions savings of between 114 and 222 Kg per system per year depending on the PC model. For a 200-seat organisation this equates to annual savings of between 22 and 44 tonnes in carbon emissions.

When more aggressive power management policy was applied an additional 7 to 14Kg per system per year can be saved.

For Further Information See

Power consumption & management: Windows Vista versus Windows XP, PC Pro Labs, http://download.microsoft.com/documents/uk/business/PC%20Pro%20Labs%20White%20Paper%20Mar%202007.pdf

“Windows Vista Energy Conservation”, October 2006, http://www.microsoft.com/whdc/system/pnppwr/powermgmt/VistaEnergyConserv.mspx

This paper outlines the potential energy savings available when deploying Windows Vista and the significant changes from Windows XP. These savings are presented in terms of both financial and environmental impact.

3.1.3 Cost of Acquisition Vendors who offer server based computing models which support Microsoft Windows based applications still utilise Microsoft Terminal Services or Citrix Presentation Services in their solution. For example using Sun Microsystems Sun Ray solutions as an example, this still requires the hardware to host Terminal Services or Citrix, (either separately on a standalone server or on a internally hosted co-processor card running Windows in the Sun Ray Server). This is in addition to the licence costs of Windows Server (and Citrix if used) and the applications themselves. If you are only hosting Windows based applications on the Sun Ray server is therefore an additional overhead in terms of initial acquisition cost and ongoing operational costs. There is also the environment impact of the disposal of the hardware replaced by the terminal devices if this hardware cannot be repurposed.

When support, training, and integration costs are added up, a complete Microsoft solution ends up being more cost-effective.

8

Page 25Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

4 SELECTING THE MOST APPROPRIATE TECHNOLOGYThe table in Figure 3 summarises the attributes of the various client deployment architectures discussed in this paper.

Capabilities

Traditional Rich Client

Rich Client- w. SoftGrid

Remote Boot. 1:1 w/o Local Caching

w/ SoftGrid

Terminal Services

Terminal Services

w/ SoftGrid

Blade PC Pure Browser

Users

Rich User Experience Ë Ë Ë O O O ▬

Offline Use Ë Ë ▬ ▬ ▬ ▬ ▬

Apps/Data Follow User ▬ Ë Ë Ë Ë Ë

Ë

IT

App Compatibility ▬ Ë Ë ▬ Ë O

Ë

Security O Ë Ë Ë Ë ËË

TCO/TCA O/Ë Ë/O O/O Ë/▬ Ë/▬ ▬/▬ Ë/Ë

Rich (Local) Thin (Centralised)

Ë Advantage, O Neutral, ▬ WeaknessFigure 3 Client Architecture Attributes

As previously discussed there will be no “one-size-fits-all” answer and the recommended approach is to use business objectives to drive the decision. The following framework may be of assistance in planning the application deployment strategy for the various applications within an organisation.

1. Analyse user population

Which user groups are task-based vs. knowledge workers

Which user groups don’t need offline access

Are there users with specific accessibility requirements.

Page 26Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Note: studies have shown that 57% of the user population can typically benefit from accessibility features, the assumption should be that a PC should have accessibility features which can be enabled by its user as required.

2. Analyse application characteristics

Which applications are client/server or require a network

Which applications behave well in a Terminal Services/Citrix environment

CPU/Memory usage footprint

Multimedia or intensive screen drawing (CAD/CAM)

Frequency of application updates

Usage of diverse client peripherals

Which applications have compatibility issues

Which applications exploit characteristics of specific devices, such as handwriting recognition

3. Analyse client management methods

Which desktops are managed and to what degree

Where are the users located

4. Develop an application access strategy

Most customers develop a “hybrid” strategy

100% remote applications for certain users

100% local or ‘rich’ applications for certain users

Hybrid desktop for the majority of users that need ‘best of both worlds’

Use Application Virtualisation where application compatibility is an issue

Both Client and for Terminal Services.

Rich PCs as Terminal Services clients provide the most versatility and flexibility

Manage and lock down entire infrastructure with common tools

Page 27Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

5 CONCLUSIONOrganisations trying to find a single application deployment architecture which is correct for every application deployed in their organisation will find it an impossible task. There is simply no “one-size-fits-all” answer. Different applications have different characteristics which may make them more suited to the traditional rich client deployment model while others may be more suited to the server based computing model or application virtualisation.

Organisations should expect to deploy a hybrid of traditional rich client with a server based computing model (and in some cases, application virtualisation where this is appropriate). Whether the appropriate deployment model is rich client, server based (thin client), or application streaming, Microsoft offers a breadth of integrated technologies to manage an efficient IT environment, from thin-client, server-based to traditional rich client PCs

Page 28Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

6 SELECTED CASE STUDIES

6.1 Traditional Windows Rich Client (Desktop and Notebook) Cornwallis School, U.K., U.K. School Uses Mobile Solution to Support a Revolution in

Learning http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=1000003793

Cornwallis school in Maidstone, Kent, in the United Kingdom (U.K.), joined the New Line Learning federation of schools in 2005. Since that time, it has developed and deployed a new mobile solution that enhances the learning process for students. A Microsoft® Windows® XP Tablet PC Edition device is given to each student when they enter the school, and this remains with them until the day they leave. Tablet PCs replace the use of conventional books and offer a range of award-winning content, including interactive multimedia learning resources developed by the school. As a result of the project, students are more enthusiastic and motivated. The paperless school concept has also helped Cornwallis cut the costs associated with reporting and administration.

Denbigh High School, Teachers’ Lesson Preparation Time Reduced with Free Education Support Tools http://www.microsoft.com/uk/casestudies/casestudy.aspx?casestudyid=1000003764

Denbigh High School is a specialist sports college and award-winning school based in Luton, U.K. Its vision statement clearly underlines its commitment: “High achievement for all is our shared responsibility.” The school has won several awards, including Investors in People; the Healthy Schools Award; and the coveted National Association of Advisors for Computers in Education quality standard for excellence mark—for all-round provision in information and communication technology (ICT). In delivering a supportive educational environment, the school recognised that targeted use of ICT contributes to improving student learning outcomes and curriculum provision. Already using Microsoft® Office XP and the Microsoft Office System, Clare Chambers, Head of E-Learning, chose to implement a project running Learning Essentials across more than 300 desktop and laptop computers.

Northern Lights Public School, Northern Lights Public School Builds an Award-Winning Learning Environment http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=49024

Aurora, Ontario-based Northern Lights Public School oversees the education of 458 students in primary grades. The award-winning school is a technology hub—where students across all grades work closely with the latest technology tools. In December 2003, the school introduced wireless-enabled Tablet PCs, running on Microsoft® Windows® XP Tablet PC Edition and the Microsoft Office System, to its Grade 8 class. With the new tools, the school has been able to create a rich learning environment for the students, improve collaboration between students and staff, and provide parents with a new way of getting involved in their children’s education.

University of Manchester, U.K. University Bids for World-Class Status with Support of Latest Operating System. http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=201100

“The Windows Vista experience encourages students to produce their best. They particularly enjoy the tab browsing feature within Microsoft Internet Explorer 7.” Dr. David Buckley, Senior IT Officer, University of Manchester

Page 29Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

6.2 Microsoft SoftGrid® Dundee City Council, Eliminating application conflicts and enabling reliable, centralised

IT service. http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=201489

“SoftGrid is a truly unique solution. We can implement and migrate new users faster, deploy applications very efficiently, and invest our savings in critical, strategic IT projects." — Ged Bell, IT Implementation Manager, Dundee City Council.

Fontys Hogescholen, Providing instant, flexible application access to widely distributed user base, while improving total cost of ownership http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=201293

“SoftGrid has played a critical role in making ‘Anytime, Anyplace, Anywhere’ applications a reality. Our users have maximum freedom in the way they work, and our IT environment is extremely flexible, manageable and secure.” Rens Van der Vorst, Chief Technology Officer, Fontys Hogescholen

Swedish Medical Center, Swedish Medical Center’s IT department supports more than 500 applications on 4,500 desktop and laptop PCs and 150 thin terminals. Its clinicians and administrative staff are spread across multiple hospital campuses and clinics. Deploying and supporting applications for users who need to work from many different locations was incredibly challenging. http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=201290

" SoftGrid resulted in huge benefits right off the bat, including ease and speed of deploying applications, true roaming experiences, and the ability to easily swap out desktops. It's been a fantastic solution for us.." – Mike Criss, Manager of Infrastructure Engineering, Swedish Medical Center

6.3 Microsoft Windows Terminal Services Tri-Centre Community Schools, School Enhances Education, Streamlines Cost with

Robust IT Infrastructure, 10/14/2004

Tri-Centre Community Schools needed to improve its use of technology. Students weren't getting the computer experience they needed, while teachers and administrators wasted time on manual processes. Even though the school district had a computer network, it was undependable and costly to maintain. In addition, a bevy of disparate computers that couldn't be connected hampered productivity—making it even harder to develop a long-term information technology (IT) strategy. Tri-Centre contacted Heartland Technology Solutions, which crafted a solution based on Microsoft Windows Server System integrated server software. As a result, Tri-Centre has enhanced its quality of education, boosted teacher and administrator productivity, and decreased system maintenance. Tri-Centre also has a solution that can grow along with its needs.

http://wwwppe/casestudies/casestudy.aspx?casestudyid=53225

Moorfields Eye Hospital , Moorfields Opens Its Eyes to 24-bit Colour and Reduced Costs, 07/15/2003

Moorfields Eye Hospital uses state of the art research to treat people with eye conditions in and around London. Given the nature of its work, it needs to access current patient records and associated charts and photographs easily and consistently across its 11 sites. To achieve this, Moorfields has implemented a centrally managed network based on Microsoft Windows Server 2003. By doing so, it can maximise the performance of its client PCs and has created a platform which it can rely on today and in the future.

http://wwwppe/casestudies/casestudy.aspx?casestudyid=52009

Page 30Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

Heald College, Overcoming bandwidth limitations, improving application performance with Terminal Services, 07/29/2002

Heald College had a custom-built client/server solution that integrated admissions, financial aid, education, and career service functions. But with the application based in San Francisco and Heald’s 1,000 users on 11 campuses spread out between Hawaii and Oregon, application performance, accessibility, and reliability were low while administrative overhead was high. Heald needed to improve application performance and reliability. It also needed to reduce expenses. By redeploying as a thin-client application running on Microsoft® Windows® 2000 Advanced Server with Terminal Services, Heald accomplished all its goals.

http://wwwppe/casestudies/casestudy.aspx?casestudyid=50834

6.4 CITRIX Presentation Server™ Cardiff University Gains First-class Information Access

http://www.citrix.com/English/aboutCitrix/caseStudies/caseStudy.asp?storyID=14967

“With this project we have challenged convention and been able to deliver our strategic commitment of equality of access to all — regardless of location, device or connection.” Tony Rucinski, Assistant Director and Head of the Strategy Group, Cardiff University Information Services Directorate

Lemon Grove School District Improving Achievement with One-to-One Computing http://www.citrix.com/English/aboutCitrix/caseStudies/caseStudy.asp?storyID=22137

“Our Citrix solution has made it possible for us to achieve our vision of a one-to-one computing ratio. Kids now have greater choice and flexibility, and teachers can instruct at multiple, focused levels.” Darryl LaGace, Director of Information Services, Lemon Grove School District

Northumbria University, Boosts Student Achievement with Flexible, Wireless Access http://www.citrix.com/English/aboutCitrix/caseStudies/caseStudy.asp?storyID=25566

“Going wireless wasn’t a great leap for us because we already had the building blocks in place, thanks to our existing investment in Citrix Presentation Server.”Trevor Cornwell, Assistant Director, IT Services, Northumbria University

6.5 Windows Embedded Powered Thin Client Devices Ashton on Mersey School, http://uk.wyse.com/resources/casestudies/pdf/ashton06.pdf

“The department is responsible for ensuring that the school’s computer system is fully supported so that its 1300 secondary level pupils have available the resources and applications they need for learning” Nick David Business and Finance Manager

Steyning St Andrew's, http://uk.wyse.com/resources/casestudies/pdf/steyning06.pdf

“Steyning St Andrew’s CE Primary School is committed to providing a dynamic learning environment for 460 children in West Sussex. We’re responsible for raising the profile of ICT in the school, facilitating its use in different subjects and for tracking children’s progress through their school life” Julian Scott Teacher & ICT Technician

Evry University (Paris) reduce the total cost of ownership of its desktops by more than 50% with the help of Neoware thin client devices. http://www.neoware.com/solutions/education/evry-university.php

Evry University — located close to Paris, France — has reduced the total cost of ownership of its desktops by more than 50% by deploying Neoware Image Manager, Neoware’s on-demand streaming software. Neoware Image Manager has enabled Evry

Page 31Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2

Microsoft UK

University to deliver its Windows® XP operating system and its applications to PCs on-demand while improving manageability, enhancing security, and lowering costs.

Page 32Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 FinalPrepared by Michael Royster"document.doc" last modified on 16 Aug. 07, Rev 2