Thin Client SBC

1

• Thin Client (SBC)
• Good and Bad

Presented by.. Bryan Gallagher Thin Client
Practice Mgr / Senior Network Architect
2
What is Thin Client ? (Server Based Computing)
BranchOffices
WindowsTerminalsand NCs
RemoteComputing
WinFrame MetaFrameServer Farms
Cross-PlatformDesktops
WebComputing
Wireless Terminals and Information Appliances

• 100 Server-based Application Execution
• A Mainframe approach to user Applications

3
How Does It Work?
Applications User Interface and other Device
Access Executes at Client
Separates Application Device Access During
Execution
Applications Logic Executes at Server
Any Network Layer LAN / WAN / Modem / Wireless
etc..
4
Who are the Main Players ?

• Microsoft NT Terminal Services
• Citrix MetaFrame

Load Balancing
ICA
RDP
NFuse
5
Alternative SBC Players

• New Moon Canaveral IQ
• GraphOn GO-Global
• Softricity SoftGrid
• Dat Group Panther Server 2002
• ThinSoft Inc WinConnect
• HOB HobLink JWT (Java Client)
• Menta Software WinToNet (Java Client)
• Suns SunRay
• Tarantella Enterprise 3

6
Is an SBC Strategy Good for You?

• What are your Business Driver(s) ?
• Company Culture
• People Culture
• Supporting Infrastructure
• Locations and User Dispersment
• Skill of Support Staff
• Identify User Roles / Groups

7
Best Practise Rule of Thumb

• 32bit Apps
• Better than 60 of users can be migrated to a SBC
  environment
• As many apps on core servers as possible
• Plan for 15 to 20 users per CPU
• Use Dual Processor servers where possible
• Use a N1 or Staging Server Strategy
• Published Applications instead of Full Desktop
  sessions if possible

8
Look n Feel
Company Culture Branding Functionality Role Flexib
ility Training Standardised Effort
9
Network Infrastructure Considerations

• Allow 16kbps (ICA) per Concurrent user 28kbps
  (RDP)
• Allow packet overhead for other protocols
  (Browsing, Media, Telnet, printing, e-mail etc)
• Define Business SLA re need for redundant network
  links etc.

• Configure Routers for Packet Queuing
  Prioritisation

10
Web Development vs Webifying Apps

• Web Development Can be Expensive
• Can have Long Development Times
• You Have to Allow for Continuing Support
• Plug-in Compatibility and Socability Issues

11
Bandwidth ICA or HTTP
Inbound Traffic (from Client)
Bandwidth Utilisation per/Protocol Direction
Outbound Traffic (to Client)
Total Bandwidth Consumed
12
SBC Web and Multimedia

• 1st Rule
• Dont do it! (if at all possible)
• 2nd Rule
• If you have to, only do it on high bandwidth
  LANs.
• 3rd Rule
• - Offload processing of media files to local
  device where ever possible

13
SBC and Multimedia (cont.)
Published Apps
Published Video
Hyperlink Video
Published Media
Internet Content
Embedded App
14
Summary

• May extend Life of Current PCs by 2-3years
• Large upfront costs Infrastructure and Network
  Costs (possibly Licensing)
• Management, Support, Application Deployment, DR,
  Security, etc. far easier
• Will reduce Base Line Support costs over 3 to 5
  years

15
Supporting Information References

• http//www.citrix.com/solutions/
• http//www.tweakcitrix.com/
• http//www.thethin.net/
• http//www.xs4all.nl/soundtcr/
• http//www.microsoft.com/ntserver/ProductInfo/term
  inal/default.asp
• http//www.microsoft.com/windows2000/appserver/int
  ro.asp
• http//www.newmoon.com
• http//www.graphon.com
• http//download2.citrix.com/ctxlibrary/press/pdf/t
  ei_mf_serv_based_compsolut.pdf
• Measuring the Multimedia Performance of Server
  Based Computing White Paper (Columbia University)