220 likes | 559 Views
Extending Terminal Services And Hyper-V VDI In Windows Server 2008 R2. Agenda. What is presentation virtualization and why should you care? Goals for presentation virtualization and VDI in Windows Server 2008 R2 Customizing the presentation virtualization platform
E N D
Extending Terminal Services And Hyper-V VDI In Windows Server 2008 R2
Agenda • What is presentation virtualization and why should you care? • Goals for presentation virtualization and VDI in Windows Server 2008 R2 • Customizing the presentation virtualization platform • Customizing the user interface • Adding new content to the workspace • Extending connection brokering • Adding functionality to the session management UI • Additional resources
What Is Presentation Virtualization?Why should you care? • Runs an application or desktop on one computer and presents it on another • Virtualizing presentation can • Enable telecommuting and mobile workers • Speed some application performance • Reduce application management costs
What Is Virtual Desktop Infrastructure? • VDI enables a centralized desktop strategy • Gives users a personalized or temporary full desktop • Lets administrators store and maintain user work areas in the data center • Presents UI via a remote display protocol such as RDP
Terminal Server The terminal server runs applications locally and displays them on the client computer via display protocol. Each user has a separate session independent of other users. TSV Terminal Server TS Licensing TS Web Access TS Gateway RDP Session Broker Client
Terminal Services Virtualization The TS Virtualization server hosts the virtual desktops using Hyper-V. TSV Terminal Server TS Licensing TS Web Access TS Gateway RDP Session Broker Client
Terminal Server Web Access The TS Web Access server displays remote resources (VDI and TS) in a Web browser. TSV Terminal Server TS Licensing TS Web Access TS Gateway RDP Session Broker Client
Terminal Services Session Broker TS Session Broker sends incoming connection requests to the right endpoint, depending on load balancing rules, current connections, and the desired endpoint. The TS Session Broker also runs the publishing service to aggregate the remote resources. TSV Terminal Server TS Licensing TS Web Access TS Gateway RDP Session Broker Client
Terminal Services Gateway The TS Gateway server provides secure remote access to the network from the Internet. TSV Terminal Server TS Licensing TS Web Access TS Gateway RDP Session Broker Client
Terminal Serivices Licensing The TS Licensing Server manages distribution and tracking of the TSCALs required to access remote resources. TSV Terminal Server TS Licensing TS Web Access TS Gateway RDP Session Broker Client
Goals Of Presentation Virtualization In Windows Server 2008 R2 • Support both Terminal Services and VDI • Provide unified user experience and management model • Provide API for partners to extend the model • Change the look and feel of the user workspace • Add additional resources to user workspace • Enhance connection brokering logic • Add new functionality to the management UI
Displaying Remote Resources RemoteApp RemoteApp RemoteApp RemoteApp Publishing Service TSV Terminal Server Plug-in Feed TS Web Access Plug-in VM VM VM Session Broker VM “Workspaces” Windows Vista Windows XP Win7 Client
Customizing The User Interface • You can customize the standard look and feel for remote resource presentation in various ways, including • Visually sorting RemoteAppand virtual desktop icons • Branding for your customers • Filtering resource display • Creating a Silverlight-based UI
Adding New Content • Out of the box, the workspace delivers RemoteApps and VDI desktops. You could extend this to include • App-V applications streamed to the client • Resources delivered using additional protocols • Connections to physical desktops
Connection Brokering In Windows Server 2008 R2 • Connection brokering was introduced in Windows Server 2008 • Brokered connections to terminal servers • Supported extensibility API for replacing connection brokering logic • Connection Brokering is enhanced in Windows Server 2008 R2 • Brokers connections to both terminal servers and VMs • Adds new extensibility to enhance brokering logic, not replace it
Connection Brokering Architecture TS Session Broker 3.Prepare/ Start VM 2.Get Target 4.Return Target Hyper-V TSV TSV TSV TS Redirector VM 5.Redirect To VM 1.Connect Hyper-V 6.Connect to VM TSV TSV TSV VM Client
Session Management Tools • Terminal Services Manager shows current sessions on terminal server • View process and user information • Interact with user sessions • Uses WTS API
Typical Connection Management Sequence • Get handle to the remote server WTSOpenServer • Use the handle to the server to enumerate its sessions and name, ID and state of each WTSEnumerateSessions • Query information about specific sessions through the session ID WTSQuerySessionInformation • Use the session ID to take actions on specific sessions, for example: WTSDisconnectSession WTSLogoffSession WTSSendMessage
Extending Session Management • Using the new extended API you can manage virtual machine connections as well • Typical connection sequence does not change • Uses “extended” APIs to include virtual machine connection data • Organizes connections so that both VM and session can be identified • New APIs map closely to existing ones • WTSOpenServerEx • WTSEnumerateSessionsEx • WTSShutdownSystemEx • WTSEnumerateProcessesEx • WTSTerminateProcessEx
Additional Resources • 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
Evals & Recordings Please fill out your evaluation for this session at: This session will be available as a recording at: www.microsoftpdc.com
© 2008 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.