1. Interoperability

2. TODAY’S SESSION Desktop as a Service

3. Customer pain points Desktop trends Design tenants Technology enablers Defining strategy Desktop as a Service Agenda

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

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

6. The balancing act…

7. Application Distribution Managing CDs and media, application packages, and installing to unique configurations is expensive and difficult Data and Configuration 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 Network support and managed services Ensuring valid, licensed access to a local application implements custom, potentially risk-prone schemes The end result… Business Agility Changes to any aspect of the technology infrastructure is fraught with risk and fear, with thousands of interacting pieces

8. Looking at desktop trends…

9. 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” Premise of Desktop as a Service

10. 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/200910

11. A User-Centric World… User Applications Policies Delivery Channels

12. The Vision: A Better Model 11/11/200912

13. What is a virtual desktop? General user settings Roaming profiles, folder redirection Application specific user settings User State Virtualisation Remote Processes Web Access to remote processes Virtual Presentation APP-V based streaming MED-V based legacy environment support (XP).NET application (xcopy-based deployment) Virtual Application(s) ‘Physical’ deployment via boot-from-vhd (Windows 7+) Virtual deployment to Hyper-V or equivalent hypervisor technology Virtual OS 11/11/200913

14. Evolution of desktop virtualisation 11/11/200914 Hardware OS User Settings Applications User Data Windows XP / Vista Hardware OS User Settings Applications User Data Windows Vista / 7 + App-V (Today) Hardware OS User Settings Applications User Data Windows Next + Native VHD (2012+) Evolutionary adoption of desktop virtualization

15. 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 What are the available options?

16. The Evolving Desktop

17. Hardware Operating System Data, User settings Applications What’s Changing Breaking ties using technologies like virtualization to increase agility The evolving desktop stack Issues IT Faces PC components bound together, difficult to replace hardware, software

18. 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 (1)

19. 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 Desktop OS (2)

20. 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 (1)

21. 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 the app stack (2)

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

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

24. Management Platforms

25. A commonly talked about architecture is VDI Utilises a combination of: – Server Hosted Virtualization – Presentation Virtualization – Application Virtualization Generally only suitable for specific scenarios Virtual Desktop Infrastructure

26. Developing your strategy

27. 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 Develop a DaaS Strategy

28. End User Computing Scenarios Mobile Bitlocker Drive Encryption Application Virtualization Folder Redirection Replaceable PC flexibility, easy to migrate users Office Application Virtualization Folder Redirection Terminal Services (LOB Application) Hot-desking flexibly, compliance, free seating Task Terminal Services (Desktop) Extending PC life security, low cost, carbon–neutral Anywhere on non company PC Windows Vista Enterprise Centralized Desktop Windows Server 2008 Terminal Services Gateway Working from Anywhere security, emergency access Contract/ Offshore Windows Vista Enterprise Centralized Desktop Hosted Image security, right apps and data

29. 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 Hosted Desktop OS Mainstream viable in 0 to 2 years Mainstream viable 2 to 5 years No Desktop OSMainstream viable now * Source – Gartner Feb 2010

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

31. Selecting the Architecture Client / HW Driven Approach Application Driven Approach Basic Environment ActiveDirectoryDeployedActiveDirectoryDeployed Group Policy Per Role Configured Group Policy Per Role Configured 80% Desktops >2GB Ram 80% Desktops >2GB Ram 80% Desktops > 25GB Free Space 80% Desktops > 25GB Free Space Regulatory / SecurityCompliance SecurityCompliance Network > 10Mb/s to the desktop Network > 10Mb/s to the desktop The problem with this approach is that there is no recognition of the applications, or users needs and requirements Contract/ Offshore Task Mobile Office Anywhere non company PC Environment Building Blocks (Profile / Role / Security / Data Management) GroupPolicyGroupPolicyCorporate Base Image Corporate SecurityPolicySecurityPolicyDataSyncronizationDataSyncronization StartStart SpecialPeripheralsSpecialPeripherals Volume Local Printing Printing RequiresMobilityRequiresMobilityRequiresOfflineRequiresOfflineRequiresRoamingRequiresRoaming Applications Require Special or Full HW Applications Require Special or Full HW Administrator Access needed Administrator LocalHostingNeededLocalHostingNeeded SmartClientSmartClient SmartClientSmartClient Mobile Smart Client Mobile SmartClientSmartClient VDIVDI Local Hosted VDI VDIRemoteDesktopServicesRemoteDesktopServices YesNo Can the applications be delivered via Remote Desktop Services Can the applications be delivered via Remote Desktop Services Application Delivery and Requirements App Public Cloud App i.e. Online CRM App Private Cloud RemoteApp Remote i.e. Remote Business App App Federated CloudRemote CloudRemote i.e. Remote Vendor App App Private Cloud VirtualizedApp Virtualized i.e. Office App Centrally Controlled Locally Deployed App Centrally Controlled Locally Deployed i.e. Unified Comm. App Legacy or EmulationApp Emulation i.e. 3270 App

32. Deploy your architecture Rich Client TS Remote Client Virtualized Applications VDI or Blade PC Contract/ Offshore Task Mobile Office Anywhere -on non company PC

33. Applying the different desktop virtualization technologies effectively Managed Desktops Managing Unmanaged Desktops User State Virtualization Microsoft Application Virtualization Personalized Remote Desktops (VDI) (VDI) Shared Remote Desktops (RDS) (RDS)

34. 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 In Summary…

35. – 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 Recommended References

36. Interoperability