Application Deployment Architectures

Microsoft UK

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

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.

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 ii

/ Application Deployment Architectures, The "Rich" versus "Thin" debate and beyond, Version .1 Final
Prepared by Michael Royster
"application deployment architectures v10 (final).docx" last modified on 15 Aug. 07, Rev 17

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

Table of Contents

1 Executive Summary 1

2 Application Deployment Architectures 3

2.1.1 Alternative Options 4

2.2 Traditional Windows Rich Client (Desktop and Notebook) 4

2.3 Microsoft SoftGrid Application Virtualisation 7

2.3.1 Benefits 7

2.3.2 Components of Microsoft SoftGrid Application Virtualization 8

2.3.3 Availability 10

2.3.4 Further Information 10

2.4 Microsoft® Windows Terminal Services 10

2.4.1 Benefits 11

2.4.2 Components of Terminal Services 11

2.4.3 Future Enhancements with Microsoft Windows Server 2008 12

2.4.4 Further Information 12

2.5 Microsoft® SoftGrid for Terminal Services 12

2.5.1 Benefits 13

2.5.2 Components 13

2.6 Citrix Presentation Server TM 13

2.6.1 Presentation Server Additional Benefits 14

2.6.2 Further Information 15

2.7 Windows Embedded Powered Thin Client Devices 15

2.7.1 Benefits 15

2.7.2 Operating System Choices 16

2.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 22

3.1.1 Total Cost of Ownership 22

3.1.2 Reducing the power consumption 24

3.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 31

6.4 CITRIX Presentation Server™ 32

6.5 Windows Embedded Powered Thin Client Devices 32

Page v

Microsoft UK

1 Executive Summary

This 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 study[1] 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.

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 study[2] 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 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.

2.1.1 Alternative Options

When 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 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.