Interoperability

TODAY’S SESSION Desktop as a Service

Desktop as a Service Agenda • • • • •

Customer pain points Desktop trends Design tenants Technology enablers Defining strategy

The perfect world… • What do customers want from a desktop? – Easy to manage – Easy to deploy – Secure – Stable – Flexible – Agile – Easy to upgrade

The real world… • What do customers actually see: – Application compatibility – Costs – Security – Repeated large scale refresh projects • Giving a result with a relatively short lifespan

The balancing act…

The end result… Application Distribution

Data and Configuration

Managing CDs and media, application packages, and installing to unique configurations is expensive and difficult

User data is trapped on a particular machine, as is user configuration - in the event of a hardware failure, both can be lost; workarounds are expensive and hard to implement

Application Portfolio Management Ensuring valid, licensed access to a local application implements custom, potentially risk-prone schemes Network support and managed services

Business Agility Changes to any aspect of the technology infrastructure is fraught with risk and fear, with thousands of interacting pieces

Looking at desktop trends…

Premise of Desktop as a Service • DaaS is not just VDI • VDI is not DaaS • Use appropriate methods of isolation, virtualisation, delivery and management to meet the requirements • Premise… – “A user should receive the right desktop and associated applications, at the right time on the right device. The desktop should not be associated with the device – the device can be thought of as a portal which surfaces the users applications, data, user state and authorisation and access”

Goal • Enable flexible and policy driven combination of delivery channel, operating system and applications as needed for the given user – Isolate users, applications and delivery channels into separately managed entities

• Establish the virtual desktop as a concept that spans all possible delivery channels – Applications and data are centrally managed – Deployment of application and data is centrally and consistently managed regardless of delivery channel – Applications and data are treated as cached entities and synchronized with an appstore and “user state store” respectively – The OS is cached and synchronized with an appstore

• Hardware or other failure is not a critical event for users • Enable reliable maintenance of applications and OS

11/11/2009

10

A User-Centric World… Applications

User Delivery Channels

Policies

The Vision: A Better Model

11/11/2009

12

What is a virtual desktop? User State Virtualisation

• General user settings • Roaming profiles, folder redirection • Application specific user settings

Virtual Presentation

• Remote Processes • Web Access to remote processes

Virtual Application(s) Virtual OS 11/11/2009

• APP-V based streaming • MED-V based legacy environment support (XP) • .NET application (xcopy-based deployment)

• ‘Physical’ deployment via boot-from-vhd (Windows 7+) • Virtual deployment to Hyper-V or equivalent hypervisor technology

13

Evolution of desktop virtualisation Windows XP / Vista

Windows Vista / 7 + App-V

Windows Next + Native VHD

(Today)

(2012+)

User Data

User Data

User Settings

User Settings

User Data User Settings Applications

Applications Applications

OS OS

OS

Hardware

Hardware

Hardware

Evolutionary adoption of desktop virtualization

11/11/2009

14

What are the available options? • Gartner say there are 10 client computing architectural options… – Local OS vs Streamed OS vs Hosted OS – Distributed (local) application vs Hosted application vs Streamed application

The Evolving Desktop

The evolving desktop stack Data, User settings

Issues IT Faces PC components bound together, difficult to replace hardware, software

What’s Changing Applications

Operating System

Hardware

Breaking ties using technologies like virtualization to increase agility

Options for the Desktop OS (1) • The traditional approach: Locally Installed – OS hosted locally on desktop, tied to hardware – Deployed using OS deployment processes

• The other traditional approach: Terminal Services / Citrix – OS hosted on server – Single OS hosting multiple user sessions

Options for the Desktop OS (2) • Server Hosted Virtualization: – Virtualized full desktop OS hosted on a server virtualization platform such as Hyper-V – Presented by server to a client device (can be thick or thin client)

• Locally Hosted Virtualization: – Virtualized full desktop OS hosted locally on the machine – Delivered through MED-V, aimed at App Compat

Options for the app stack (1) • The traditional approach: distributed applications: – Delivered via software delivery toolset/installed manually – Installed on local host machine, tied to that OS

• The other traditional approach: terminal services/citrix: – Server hosted applications presented to user using Citrix / RDS

Options for the app stack (2) • Application Virtualization: – App-to-App Isolation technology, runs each application in separate “bubble” – Still executes locally on host machine – Can be ‘streamed’ to machine for ‘instant on’ capability – Not suitable for all applications

• Distributed or streamed to device

Options for user data/settings (1) • The traditional approach: Locally hosted – Hosted locally on the OS – User profile different on each machine user logs in on – User data different on each machine user logs in on – Home drives used for shared / network data

Options for user data/settings (1) • Decoupling user data & settings from PC • Folder Redirection + offline files – Greatly improved since the XP days – Can redirect all profile folders (except AppData\Local)

• Roaming User Profiles – Contains mainly NTUSER.DAT – Roams user and application settings

Management Platforms

Virtual Desktop Infrastructure • A commonly talked about architecture is VDI • Utilises a combination of: – Server Hosted Virtualization – Presentation Virtualization – Application Virtualization

• Generally only suitable for specific scenarios

Developing your strategy

Develop a DaaS Strategy • Rationalise your environment – Well managed and implemented AD, GPO, software distribution, client deployment technologies, application portfolio, asset management, etc… – This gives you the basis for a well managed, optimised desktop

• • • •

Define user scenarios Map the available strategies Define user / site profiles Match technologies with user needs

End User Computing Scenarios Mobile

Replaceable PC flexibility, easy to migrate users Application Virtualization

Office

Bitlocker Drive Encryption

Task

Folder Redirection

Application Virtualization

Extending PC life security, low cost, carbon–neutral Terminal Services (Desktop)

Hot-desking flexibly, compliance, free seating

Folder Redirection

Contract/ Offshore

Hosted Image security, right apps and data Windows Vista Enterprise Centralized Desktop

Anywhere on non company PC

Working from Anywhere security , emergency access Windows Vista Enterprise Centralized Desktop

Windows Server 2008 Terminal Services Gateway

Terminal Services (LOB Application)

10 Client Computing Architectures Distributed Applications

Streamed Applications

Centralised Applications

Local Desktop OS

Mainstream viable now

Mainstream viable 2 to 5 years

Mainstream viable now

Streamed Desktop OS

Niche viable in 2 to 5 years

Not recommended

Niche viable in 2 to 5 years

Mainstream viable 2 to 5 years

Mainstream viable 2 to 5 years

Hosted Desktop Mainstream OS viable in 0 to 2 years

No Desktop OS

* Source – Gartner Feb 2010

Mainstream viable now

Which Architecture to Choose? • There is no single, one size fits all solution • Your desktop strategy depends on your user requirements; hence Desktop as a Service

What are your requirements?

Selecting the Architecture Client / HW Driven Approach Start

Yes

Application Driven Approach No

Special Peripherals

Smart Client

Volume Local Printing

Smart Client

Requires Mobility

Requires Offline

Requires Roaming

Applications Require Special or Full HW

Mobile Smart Client

Smart Client

Can the applications be delivered via Remote Desktop Services

Administrator Access needed

Local Hosting Needed

Remote Desktop Services

VDI

Local Hosted VDI

Basic Environment Active Directory Deployed

Group Policy Per Role Configured

80% Desktops >2GB Ram

80% Desktops > 25GB Free Space

Regulatory / Security Compliance

Network > 10Mb/s to the desktop

Environment Building Blocks (Profile / Role / Security / Data Management) Group Policy

The problem with this approach is that there is no recognition of the applications, or users needs and requirements

Corporate Base Image

Security Policy

Data Syncronization

Application Delivery and Requirements App Public Cloud

App Private Cloud Remote

App Federated Cloud Remote

i.e. Online CRM

i.e. Remote Business App

i.e. Remote Vendor App

Task

Office

Mobile

App App Private Cloud Centrally Controlled Virtualized Locally Deployed i.e. Office

Anywhere non company PC

i.e. Unified Comm.

Contract/ Offshore

App Legacy or Emulation i.e. 3270 App

Deploy your architecture Mobile

Rich Client

TS Remote Client

Contract/ Offshore

Office

Anywhere -on non company PC

Virtualized Applications

Task

VDI or Blade PC

Applying the different desktop virtualization technologies effectively Managed Desktops

User State Virtualization Microsoft Application Virtualization

Shared Remote Desktops (RDS)

Personalized Remote Desktops (VDI)

Managing Unmanaged Desktops

In Summary… • •

One size does not fit all Just because its feasible, doesn’t mean its necessarily practical – Different architectures can introduce additional complexity and management layers

•

Regardless of strategy, rationalise the environment – – – – – –

•

• •

Clean core image Implement best practice AD Define role based GPO’s Understand your network Implement OS build and software distribution technology Understand your application portfolio

Implement relevant desktop virtualisation technologies to isolate layers of the stack Map out desktop computing requirements Map requirements to available strategies

Recommended References – – – – – – –

– – – – –

Gartner: “TCO of Traditional Software Distribution vs. Application Virtualization”, Michael A. Silver, Terrence Cosgrove, Mark A. Margevicius, Brian Gammage. Publication Date: 16 April 2008 ID Number: G00155897 Gartner, “Total Cost of Ownership Comparison of PCs With Hosted Virtual Desktops”, Mark A. Margevicius, Michael A. Silver, Federica Troni, 4 August 2008 ID Number: G00155498 Gartner, “Desktop Total Cost of Ownership: 2008 Update”, Publication Date: 24 January 2008 ID Number: G00153705 Gartner PC Configuration Magic Quadrant Dec 2008 Gartner, “The TCO of Employee-Owned Notebooks Running a Corporate Virtual Machine”, Brian Gammage , Publication Date: 5 May 2008 ID Number: G00156851 Gartner: “How to Reduce Your PC TCO 30% in 2011 “, Federica Troni, Brian Gammage, Michael A. Silver, Publication Date: 20 March 2009 ID Number: G00166195 Gartner: “Organizations That Unlock PCs Unnecessarily Will Face High Costs“, Michael A. Silver, Ronni J. Colville, Publication Date: 19 December 2008 ID Number: G00161951 Gartner: “Hosted Virtual-Desktop Deployments Are Set to Accelerate” Gartner, Brian Gammage, Mark A. Margevicius, 28 July 2008, ID Number: G00159683 Gartner: “Choosing From 10 Client Computing Architectural Options”, Brian Gammage, Mark A. Margevicius. 10 December 2007, Publication Date: 27 February 2009 ID Number: G00164331 Gartner Hype Cycle for PC Technologies 2008, Publication Date: 1 July 2008, ID Number G00158516 Gartner - Dataquest, “Dataquest Insight: Growth in Thin-Client Terminal Markets Points to a Fundamental Shift in Computing Architecture”, 2 October 2008 ID Number: G00160724