WSV304 Microsoft RemoteFX : Rich User Experience for VDI and Session Virtualization

2. WSV304Microsoft RemoteFX: Rich User Experience for VDI and Session Virtualization Tad Brockway RemoteFX Product Unit Manager Microsoft Corporation

3. RemoteFX Clients Windows Server & RemoteFX Windows Server & RemoteFX Traditional PC Traditional PC HTML 5 Requires a local IT Pro. Powerful Microsoft Silverlight Manageable from anywhere. Consumes ~170W. Flexible DirectX Apps Power footprint is shared. Cannot meet certain regulatory reqs. Diverse Windows Media Helps meet regulatory reqs. Versatile Vulnerable to hardware failures. Aero Glass Recoverable from hardware failures. Portable Limited to PC form factors. Adobe Flash Enables full range of client form factors. 3

4. RemoteFX Compared to RDP 7 demo

5. New Concept for RDP 7.1 RDP Host Rendering RDP Client Rendering Separate host intercept for each graphics stack & client equivalents – gaps Single intercept point for all graphics – predictable and complete UX Leverages Rich Client HW and SW Lightweight Clients & Complexity Shifted to Host Can lead to better bandwidth utilization for intercepted graphics types Typically requires more bandwidth as traffic is sent as compressed bitmaps

6. Hyper-V VDI + RemoteFX Components WS08 R2 Hyper-V Server Inter-VM Communications Hyper-V Integrated Shared Memory Comms • VGPU output rendered to physical GPU via DirectX. • First phase of CODEC runs on GPU. • Screen deltas captured from GPU. Protocol Fundamentals (e.g. Authn, Encryption, & Client device Redirection) Hyper-V Parent Partition W7 Guest OS UMRDP WDDM driver exposes parent GPU to guest OS. RCC VGPU Driver VMBUS RemoteFX Hardware ASIC and Driver Optionally offloads CODEC from CPU/GPU increasing fidelity and scale. GPU 6

7. RemoteFX-for-VDI OS & System Requirements • Hyper- V Host • Windows Server 2008 R2 with SP1 (Hyper-v, Standard, Enterprise, and DataCenter editions) • VDI Virtual Machine • Windows 7 Enterprise with SP1 • Windows 7 Ultimate with SP1 • Remote Client Device • Windows 7 with SP1 • Devices with RDP 7.1

8. RemoteFX-for-Sessions (aka TS) Session [1…n] Session 0 TS Core Other Office IE LSM TERMSRV RDPWSX GDI User Kernel Windows Server with RDSH Enabled WIN32K.SYS RDP Core RDPDD (RDP Display Driver) TERMDD RemoteFX HW Encode Driver RDP RemoteFX Encode Library RDPWD RemoteFX Encode ASIC TDTCP CPU

9. RemoteFX-for-Sessions Requirements • Windows Server 2008 R2 with SP1 • Remote Client Device • Windows 7 with SP1 • Devices with RDP 7.1

10. RDP Device Redirection + RemoteFX! Isochronous RDP 7.0 + RemoteFX USB Device Redirection

11. RemoteFX USB Redirection demo

12. Questions

13. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

14. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. Backup

16. Windows Server Desktop Virtualization Industry Term: Terminal Server RD Web Access RD Session Host RD Client RD Virtualization Host RD Connection Broker RD Gateway Licensing Server Active Directory® Industry Term: Virtual Desktop Infrastructure (VDI)

17. RemoteFX-for-RDVH (VDI) Virtual GPU and Rendering Pipeline RemoteFX Hyper-V VM Bus Parent Integration IE9 Windows App RCC Hyper-V VMBUS Shared Memory Comms Hyper-V Parent Partition GDI DX9 APIs W7 Child Partition DX9 APIs RemoteFX VGPU Driver GPU Vendor Driver RemoteFX Hyper-V VM Bus Child Integration GPU

18. RemoteFX-for-RDVH (VDI) Capture and Encoding Pipeline RemoteFX Hyper-V VM Bus Parent Integration User Mode RDP RDP RCC Hyper-V VMBUS Shared Memory Comms Hyper-V Parent Partition W7 Child Partition DX10 APIs RemoteFX VGPU Driver GPU Vendor Driver RemoteFX ASIC DRIVER RemoteFX Hyper-V VM Bus Child Integration GPU RemoteFX ASIC

19. RemoteFX-for-RDSH (aka TS) Session [1…n] Session 0 TS Core Other Office IE LSM TERMSRV RDPWSX GDI User Kernel Windows Server with RDSH Enabled WIN32K.SYS RDP Core RDPDD (RDP Display Driver) TERMDD RemoteFX HW Encode Driver RDP RemoteFX Encode Library RDPWD RemoteFX Encode ASIC TDTCP CPU

20. The RemoteFX ‘Payload’ RDSH (TS) RDVH RemoteFX Remote Desktop Protocol (RDP) RDS Server Infrastructure RemoteFX-enabled RDS Server Infrastructure RemoteFX-enabled Remote Client Remote Client RemoteFXleverages the RDP protocol structure Graphics Virtual Channels (VCs) Device VCs Mouse &Keyboard VCs Partner Virtual Channel Plug-Ins Virtual Channel Multiplexing and Framing Bulk Compression (RDP5+, RDP6.0, RDP6.1) Security Layer (SSL/Kerberos/NTLM) Transport Layer (e.g. TCP, RPC/HTTP, Windows Live Tunnel)

21. RDP 7.1 Client Components and Graphics Pipeline RDP 7 Graphics Providers (GDI, AERO, Windows Media) Core Services Networking/ Security Virtual Channels Devices Bulk Decompress Key/Mouse Display Device RemoteFX Decode Abstraction Layer RemoteFX SW Decoder GPU RDP RDP Client Components CPU RemoteFX HW Decode Driver RemoteFX Decode ASIC

22. The RemoteFX Hardware Ecosystem Remote Desktop Services Server LCD Display ULW Thin Client Graphics Card Graphics Card PCIe Encoder Card Decoder Engine Decoder Engine GPU GPU Encoder Chip Thin Client SOC RemoteFX VDI Servers and Chassis Thin Clients Supporting Semiconductors GPUs Encode Coprocessor ASICS Thin Terminal SoC’s LCD Controller

23. GPUs in the Datacenter?

24. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.