Using Windows 2000

Terminal Services

Name: John Skaris

E-mail: jskaris@analysts.com
Company: Sequoia Services Group
Terminal Services Overview
 Windows 2000 Server
Terminal Services

 Centralized deployment of the latest

Windows-based applications to a wide
variety of desktops
 Remote execution of applications
over low-bandwidth connections
 Remote Administration for the
Windows 2000 Server family
What is Terminal Services?
RDP
Terminal Server
TCP/IP

My Documents My Network
Places

Client My Computer
Recycle Bin

Internet Explorer

Start 12:00 PM
 Windows 2000 Server
Terminal Services
 A fully integrated component of:

Terminal Services
 Overview of Application
Deployment Technologies
 Centralized Hosting
 Terminal Services Application Server
(terminal server)
 Application Distribution Technologies
 Intellimirror
 Application publishing via Group Policy
and Active Directory to Windows 2000
Professional desktops
 “My apps, settings, data” follow me
 Systems Management Server (SMS)
 Application Types
 Personal Productivity Applications
 Relatively static
 Upgraded once per year or less
 Random Usage
 Lots of options
 Good installation routines
 Data saved on file system
 Extensively tested
 Example: Office XP suite, Visio
 Application Types (Cont)
 Line of Business Applications
 Heads down data entry by small user
population or infrequent use by large user
population
 Less options
 Business rules can change frequently
 Frequent patches and upgrades
 Data saved in databases
 Large data sets
 Example: Siebel, PeopleSoft, Great
Plains
 Application versus User
Characterization
 Determining CPU and RAM usage
 Random datasets and usage in
productivity apps make accurately
predicting RAM, CPU and Network
utilization impossible
 LOB apps much easier to quantify
resource usage
 Determining Usage Patterns
 Typing rates affect CPU performance on a
terminal server
 Concurrent Active vs Idle Users
 The Ideal Application for a
Terminal Server
 Works on a Win2k or Win XP Pro PC
 Would work if used by more than one
user on the same device
 A Win32 application with no heavy
graphics, multimedia or animation
 When is a PC better?

 Not easy to predict how much resources are

required at any one time
 Graphics performance
 Types of users who should use a PC
 Accountants
 Graphics designers
 Content Creators
 Developers
 Types of applications that require a PC
 CAD, Extensive graphics/multimedia, Voice
recognition, Plug and Play peripheral support
 When is Terminal Services
better?
 Non-windows desktops
 Legacy desktops
 Sites with no local support staff
 Terminal server located at a branch, HQ or
ASP
 Bandwidth considerations
 Dial-up roaming user
Deploying Office XP on
Terminal Services
Many Clients Install Office Here Once
 Office XP on Terminal
Services
 Install Office XP one time
 Still need to license Office for
everyone who will use it
 Makes deployment management
of Office XP easier
 Allows you to run Office XP on
lower level PC’s and non-
windows devices
When to Use a Windows-based
Terminal
 Hostile situations
 User or Environment
 Factory floor, Education, Kiosks
 Remote offices or businesses (using an
ASP, for example) with no local support
staff
 Green screen replacement
 Call centers, Data entry
 Roaming support staff (Mobile WBT)
 Why a Windows app on a
Terminal Server is better than a
Web app
 100% server-based execution
 No local data downloaded
 Instant field validation
 Simplified testing and support
 Applications development/support
tools and skills are widely available
Licensing Office XP in a
Terminal Services
Environment
Terminal Services Licensing
 Feature of all versions of Windows
2000 Server (Windows 2000 Service)
 Formerly Separate Version of NT4
Server
 New License tracking in Terminal
Server
 License Manager tracks license
tokens
 License Tokens (software) loaded on
client machine when connected to
Terminal Server
 Every client device needs a license
token regardless of location/use or it
cannot connect to the server
Terminal Server Licensing
 Three components to TS licensing
 Server license (Windows 2000 Server)
 Windows 2000 CAL
 Windows 2000 TS CAL
 Exception
 If client connecting to Terminal Services is
a Windows 2000 Pro client, no TS CAL is
required (TS CAL is built into W2k Pro)
 TS CAL is only needed for legacy clients
(NTW, Win 9x, DOS, UNIX,Mac etc…)
 More info and TS licensing paper at:
 www.microsoft.com/windows2000/library/h
owitworks/terminal/Tslicensing.asp
Terminal Services Licensing
& Citrix
 Citrix allows concurrent usage
licensing; however, Microsoft
does not
 A separate TS CAL is still required
for each and every device using
Terminal Services
 Scenario: 100 PCs, 25 User Citrix
License using Win2K TS
 Even though your total user
connections are limited to 25
“concurrent” users by your Citrix
license, you need 100 Win2K TS
CALs
 Conclusions
 A terminal server is generally best for
deployment of applications, over LAN,
WAN and Dial-up
 PCs are generally best for execution of
high graphic and processor intensive
 Windows-based Terminals are best for
hostile, unsupported environments or
green screen replacement
 Windows Terminal Services allows fast
application deployment and easy
management for Office XP
Resources
 Office XP Resource Kit
 TechNET: Q articles from the knowledge
base:
 Q290375 “How To Install Office on
Windows 2000 Terminal Server”
 Q311241 “How To Customize Office XP for
Terminal Server”
 Q290205 “Precedence Among Registry
Customizations Made by CIW and CMW
 Web Sites
 Office XP Resource Kit—Deploying On
Terminal Services
 http://www.microsoft.com/office/ork/xp/one
/deph02.htm