James ONeill : Microsoft UK http:blogs'technet'comjamesone

1
Windows Server 2008Terminal Services

• James ONeill Microsoft UKhttp//blogs.technet
  .com/jamesone

2
What are we going to cover ?

• Because Terminal Services isnt new, is it ?

True Type
Device Support
Server Roles
Display Changes
SingleSign-on
SessionBroker
RemoteApp
TS Gateway
TS Web-Access
3
Server 2008 Virtualization Technologies
Server Virtualization
Presentation Virtualization
Windows Server Virtualization
Management
Desktop Virtualization
Application Virtualization
4
Support for Client side improvements

• Making Terminal Services a first class citizen

5
Device support

• Can use clients
• Audio
• Printer
• Clipboard
• Smart Card
• Serial port
• Drives
• Camera / MP3 player

6
RDC display changes

• Display improvements
• Display was 43 and capped at 1600x1200
• Now can be any size, including spanned monitors
• ClearType supported
• Vista-style desktop experience supported
• Display prioritization
• Print jobs dont affect user experience

7
Experience options (off vs. on)
8
Single sign-on

• Requires Vista or Server 2008 as the client
• Group Policy setting
• /Computer Configuration /Administrative
  Templates /System /Credentials
  Delegation.
• In Allow Delegating Default CredentialsAdd
  termsrv/Servername

9
Server Changes
10
Terminal Services Roles
11
TS Remote App
12
TS Remote App

• Client sees an application not a desktop
• Applications identified at the server
• Published in one of 3 ways
• .MSI file
• .RDP file
• TS Web access

13
TS Remote App
Add app.
Manage AppsManage Config Manage Sessions
Connectionsettings
Copy apps
Create Installfiles
14
Demo

• TS Remote App

15
TS Web access

• Making available apps browsable

16
TS Web Access

• Can embed TS client object on web page
• Since NT 4.0 !!
• Now have ability to launch apps or desktop
• Pull down RDP file from web page
• Run normal client

17
Demo

• TS Web Access

18
(No Transcript)
19
TS Session broker

• Moving from servers to farms

20
TS Session Broker

• Load balances sessions to terminal servers
• Basic operation
• User connects to a terminal server
• Server knows it is in a farm
• Server asks broker where should this go ?
• User session is re-directed

21
Brokers decision process

• Does this user have a session ?
• Reconnecting an open session
• Second TS App session
• If so connect to the same server
• Does the server participate in load balancing ?
• If not let it have the session
• Otherwise, which servers allow new sessions ?
• Calculate sessions / relative weight
• Connect to server with lowest relative load

22
Server roles in a farm

• Broker
• Tracks sessions
• Redirector
• All servers which users initially connect to
• Connection might be round robin DNSor more
  sophisticated
• Terminal server
• Runs the users workload

23
Configuring Farm membership

• Group Policy
• Or TS configuration

24
TS Gateway

• Or VPN considered harmful

25
TS Gateway

• Tunnel RDP using RPC over HTTP technology
• Allow client to connect from anywhere

26
Adds Additional roles...
27
Configuration

• Client
• Setting in Group policy, or per connection
• Server
• Install role
• Choose a Certificate
• Set a Connection Access policy
• Who and How
• Set a Resource Access Policy
• What
• Multiple Servers can form farms
• Publish with ISA...

28
Demo

• TS Gateway

29
Combining Web Access with gateway

• The Apps on offer in Web accesscan specify the
  gateway
• (And can specify the TS Farm)
• So publish the Web Access page andpublish the
  gateway ....
• Users get a portal of published LOB apps
  Accessible from wherever they are

30
Conclusions

• Publish Apps not desktops
• Better client experience
• Multiple publication options
• Anywhere Access
• Access Mail, IM anywhere, why not L.o.B apps ?
• Scale with server farms
• Third parties (e.g. Citrix) still add value

31
Questions ?

• More information on my blog at
• http//blogs.technet.com/jamesone

32
Momentum

• IT Pro specific program for early adopters

33
Momentum

• Qualifying Technologies