1. Sudarshan Yadav Sr. Program Manager, Microsoft Email: syadav@microsoft.com

2. Agenda Introduce key roles of Remote Desktop Services How the traditional Terminal Server (now known as Remote Desktop) sessions and Virtual Desktop Infrastructure (VDI) scenarios work side by side Access from anywhere scenarios with RD Gateway

3. Runs an application or desktop on one computer and presents it on another Remotes user experience via display protocol Is remote resource-agnostic Virtualizing presentation can: Speed some application performance Improve Remote worker efficiency Help Secure Data and Applications Remote Desktop Services in Win2K8 R2

4. Session Based Infrastructure Runs applications on a central server Allows users to share an operating system Isolates users into sessions

5. Virtual Desktop Infrastructure Runs virtual machines on a central server Gives each user their own operating system Personal Temporary

6. What's Available? RD Licensing RD Server Virtual desktop Server Connection BrokerRD Gateway Client RD Web Access The RD server runs applications locally and displays them on the client computer. Each user has a separate session The virtual desktop server hosts the virtual desktops using Hyper-V. Each user has a separate VM

7. What Do I See? RD Licensing RD Server Connection Broker RD Web Access RD Gateway Client The RD Web Access server displays remote resources in a Web browser. Virtual desktop server The ConnectionBroker runs the publishing service to aggregate the remote resources

8. How Do I Connect to It? RD Licensing RD Server Connection BrokerRD Gateway Client Connection Broker sends incoming connection requests to the right endpoint RD Web Access Virtual desktop server The RD Gateway server provides secure remote access to the network from the Internet

9. How Do I License Access? RD Licensing RD Server Connection BrokerRD Gateway Client The RD Licensing Server manages distribution and tracking of the TSCALs required to access remote resources. RD Web Access Virtual desktop server

10. Remote Apps & Shell Integration RD Server TSVhost-suds Connection Broker RD-CB Client Local Win7 Client RD Web Access RD-CB Publishing the app

11. Connection Brokering Architecture RD Redirector RD Server Connection Broker ClientClient TSVTSV TSVTSV TSVTSV VMVM TSVTSV TSVTSV TSVTSV VMVM Hyper-VHyper-V Hyper-VHyper-V 1.Connect 2.Get Target 4.Return Target 3.Prepare/ Start VM 5.Redirect To VM 6.Connect to VM

12. VDI – Personal Domain Desktop Connection Broker RD-CB Client Local Win7 Client RD Web Access RD-CB AD Shan-w7s-3 Virtual desktop server TSVhost-suds

13. Connection Brokering in Windows 2008 R2 Session broker was introduced in Windows 2008 Brokered connections to terminal servers Supported extensibility API for replacing connection brokering logic Session Brokering is enhanced in Windows 2008 R2 and is known as Connection broker Brokers connections to both terminal servers and VMs Adds new extensibility to enhance brokering logic, not replace it

14. New Endpoints Brokering Service Plug- in RD Server Plug- in Connection Broker Win7 ClientPhysical Desktop Plug- in Windows VistaWindows XP Virtual Desktop Server VM

15. New Behavior Virtual Desktop Server VM Brokering Service Plug- in RD Server Plug- in Connection Broker Win7 Client Plug- in Windows VistaWindows XP Wake On LAN Physical Desktop X Placing VMs Assigning VMs

16. New Load Balancing Rules Virtual Desktop Server VM Brokering Service Plug- in RD Server Plug- in Connection Broker Win7 Client Plug- in Windows VistaWindows XP Server stress Time of day Originating IP address

17. Secure Internet Connections Prior to WS08, there were two options for enabling TS access from outside: Open 3389 Set up VPNs Using RD Gateway, you can: Connect using 443 and no VPN Restrict access to certain people Limit the resources they can use

18. How RD Gateway Works DMZ HTTPS / 443 Internet Corp LAN RD Server Hotel External Firewall Internal Firewall Home Business Partner/ Client Site Other RDP Hosts Eg. Desktops RDV Serve r Internet Tunnels RDP over RPC/HTTPS Passes RDP/SSL traffic to TS Strips off RPC/HTTPS Network Policy Server Active Directory DC RD Gateway Server

19. Connection Authorization Policies What authentication methods are allowed Which users can connect Which computers can connect

20. Connection Authorization Policies Control what devices can be redirected Enable or disable device redirection

21. Resource Authorization Policies Control what computers can be connected to by Active Directory Security Group… … or by TSG managed groups Control what ports can be connected

22. Key Points Centralized computing can take different forms Separate remote users into sessions Separate remote users into virtual machines Microsoft knows centralized computing Support for remote desktops and remote applications isn’t new in Win2K R2… it just adds a new way of organizing centralized computing resources

23. References Terminal Server Home Page http://www.microsoft.com/windowsserver2008/en/us/ts-product- home.aspx Terminal Services Team Blog http://blogs.msdn.com/ts/ Terminal Services Newsgroup http://www.microsoft.com/technet/archive/community/newsgroups/ topics/termsvcs.mspx?mfr=true Terminal Services Development Documentation http://msdn.microsoft.com/en-us/library/aa383494(VS.85).aspx Terminal Services App Compat Programming Guidelines http://msdn.microsoft.com/en- us/library/aa383490%28VS.85%29.aspx Windows Server 2008 Terminal Services Resource Kit http://www.microsoft.com/MSPress/books/12716.aspx

24. Feedback / QnA Your Feedback is Important! Please take a few moments to fill out our online feedback form at: > For detailed feedback, use the form at http://www.connectwithlife.co.in/vtd/helpdesk.aspx Or email us at vtd@microsoft.com Use the Question Manager on LiveMeeting to ask your questions now!

25. © 2007 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.