christa anderson program manager ii microsoft corporation niraj agarwala senior test lead microsoft...
Post on 21-Dec-2015
215 views
TRANSCRIPT
Extending Terminal Services And Hyper-V VDI In Windows 7
Christa AndersonProgram Manager IIMicrosoft Corporation
Niraj AgarwalaSenior Test LeadMicrosoft Corporation
ES22
Agenda
What is presentation virtualization and why should you care?
Goals for presentation virtualization and VDI in Windows 7
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
TS Licensing
RDP
Terminal Server
TSV
Session Broker
TS Gateway
Client
TS Web Access
The terminal server runs applicationslocally and displays them on the clientcomputer via display protocol. Eachuser has a separate session independent of other users.
Terminal Services Virtualization
TS Licensing
RDP
Terminal Server
TSV
Session BrokerTS Web Access
TS Gateway
Client
The TS Virtualization server hosts the virtual desktops using Hyper-V.
Terminal Server Web Access
TS Licensing
RDP
Terminal Server
TSV
Session BrokerTS Web Access
TS Gateway
Client
The TS Web Access server displaysremote resources (VDI and TS) ina Web browser.
Terminal Services Session Broker
TS Licensing
RDP
Terminal Server
TSV
Session Broker
TS Gateway
Client
TS Session Broker sends incomingconnection requests to the rightendpoint, depending on load balancingrules, current connections, and thedesired endpoint. The TS Session Brokeralso runs the publishing service toaggregate the remote resources.
TS Web Access
Terminal Services Gateway
TS Licensing
RDP
Terminal Server
TSV
Session Broker
TS Gateway
Client
The TS Gateway server providessecure remote access to the networkfrom the Internet.
TS Web Access
Terminal Serivices Licensing
TS Licensing
RDP
Terminal Server
TSV
Session Broker
TS Gateway
Client
The TS Licensing Server manages distribution and tracking of the TSCALs required to access remote resources.
TS Web Access
Goals Of Presentation Virtualization In Win7
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
Terminal Server
TSV
TS Web Access
Publishing Service
Plug-in
Plug-inFe
ed
Session Broker
Win7 Client
VMVM
VMVM
RemoteAppRemoteApp
RemoteAppRemoteApp
“Workspaces”
Windows Vista
Windows XP
Customizing The User Interface
You can customize the standard look and feel for remote resource presentation in various ways, including Visually sorting RemoteApp
and virtual desktop icons Branding for your customers Filtering resource display Creating a Silverlight-based UI
Customizing The User Interface
Niraj AgarwalaSenior Test LeadPHDV
demo
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
Adding New Content To The Workspace
Niraj AgarwalaSenior Test LeadPHDV
demo
Connection Brokering In Windows 7
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 Win7
Brokers connections to both terminal servers and VMs
Adds new extensibility to enhance brokering logic, not replace it
Connection Brokering Architecture
18
TS Redirector
TSSession Broker
Client
TSVTSVTSVVM
TSVTSVTSVVM
Hyper-V
Hyper-V1.Connect
2.Get Target 4.Return Target
3.Prepare/Start VM
5.RedirectTo VM
6.Connect to VM
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
1. Get handle to the remote serverWTSOpenServer
2. Use the handle to the server to enumerate its sessions and name, ID and state of eachWTSEnumerateSessions
3. Query information about specific sessions through the session IDWTSQuerySessionInformation
4. 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
Please use the microphones provided
Q&A
© 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.