LAN 1 Chapter 14

Chapter 14
Lecture Outline
I.      Understanding Terminal Services
A.      Introduction

1.      Not so long ago, it was speculated that computer networks would be
made up of two types of PC's: thin clients and fat servers.  The thin
clients would be PC's devoid of larger hard drives, RAM, and expensive
peripherals.  Most of a client's needs could be handled completely
from the server.  This would include applications as well as other
locally managed services.  With the drastic reduction in hardware
prices, and the ever increasing speed and power of processors, the
focus has shifted back to fat PC's, both client and otherwise.  This
has not deterred Microsoft from implementing a Terminal Service
feature in Windows 2000 Server.

2.      Windows 2000 Server has two modes of Terminal Services that can be
installed.
a.      Application Server mode
b.      Remote Administration Server mode.

3.      Terminal Services can be run on any of the following client
operating systems:
a.      Windows CE platforms
b.      16-bit Windows PCs with Windows for Workgroups 3.11 and MS TCP/IP
32.
c.      32-bit Windows based PC's running either Windows 9x or Windows NT 

3.51 - 4.0, and Windows 2000 Professional.

4.      Terminal Services provides the ability to supply all server
resources to any requesting client.
a.      The requesting client will assume the server environment's look and
feel.
b.      For example, a Windows 3.11 16-bit "old fashioned" desktop will
assume that of Windows 2000 when connected via Terminal Services.
c.      Also the 32-bit processing power of the Windows 2000 Server will be
made available to the client machine requesting it.
d.      The potential longevity of the client is greatly extended.

5.      Terminal Services is built on two industry standard protocols.
a.      TCP/IP 
i.      This is used as the main transport for connectivity between client
and server.

b.      Remote Desktop Protocol (RDP)
i.      Application Protocol between client and server.
ii.     Informs the server of all client activity, allowing the server to
adapt the GUI so it can match the server.
iii.    Refer to Exercise 14-1 on page 673 to demonstrate how to connect
to a Terminal Server.

B.      Remote Administration Versus Application Server 

1.      When Terminal Services is set to run in Remote Administration mode,
only the minimum resources are installed.


2.      Remote Administration mode is limited to only two concurrent
connections due to licensing restrictions.

3.      Application Server mode allows clients to simultaneously access
Windows-based applications that run on the server.

4.      Applications need to be configured to function optimally on a
Terminal Service application server.

5.      Application mode requires significantly more resources than Remote
Administration mode.
C.      Remote Control Versus Remote Access

1.      Remote Control allows the server to see everything the client sees.
 This includes desktop and mouse pointer.

2.      Remote Control allows the user at the Server terminal to "take
over" a session and control the client machine's environment.

3.      Remote Access creates a user environment on the client machine that
allows the client to use the applications that are offered by the
server.

4.      The client machine does not have the applications physically
installed on it's own drives.

II.     Installing and Configuring Terminal Services
A.      Deciding Which Mode to Install During Installation.

1.      Application Server Mode or Remote Administration Server
a.      Refer to Exercise 14-2 to install Terminal Services in Remote
Administration Mode on page 676.
b.      Then refer to Exercise 14-3 on page 678 to install Terminal
Services in Application Server mode.

2.      Terminal Services Features
a.      Terminal services Licensing
i.      Used to allow access to Terminal Services running in Application
Server mode.
b.      Terminal Services Manager
i.      Allows monitoring sessions as well as killing or joining ongoing
sessions.
c.      Terminal Services Client Creator
i.      Allows you to create installation disks based on type of operating
system.
ii.     All clients must be running the 32-bit version of TCP/IP.
d.      Terminal Services Configuration
i.      Allows reconfiguration of choices made during installation.
ii.     Also allows for configuring server settings such as:
•       Status of temporary files on exit
•       Setting of temporary folders per session
•       Connectivity using the Internet
•       Use of Active Directory
B.      Terminal Services Licensing
1.      Can be extremely confusing
2.      Does not require licenses when running in Administration mode
3.      Requires separate licensing for clients
a.      CAL (client access license) required for all clients not running
Windows Professional.
b.      The License Server issues a license the first time a client
connects.
i.      Will issue temporary licenses (valid for 90 days) if none are
available.
c.      Each Windows Professional machine has a valid license to be a
Terminal Services client.
d.      200 concurrent anonymous Internet users are permitted.  These must
not be employees of your company.
C.      Remotely Administering Servers using Terminal Services 
1.      Perform most any administrative task using Terminal Services.
a.      De-fragmenting drives
b.      Editing registries
c.      Administering Printers
d.      Add COM+ components 
D.      Configuring terminal Services for Application Sharing
1.      Requires a Pentium or higher CPU.
2.      Also requires a minimum of 128MBof RAM.
3.      Additional clients require an additional 3.4 to 9MB of RAM
depending on usage (suggested).
E.      Configuring Applications for Use with Terminal Services

1.      Best method is to install applications using the Add/Remove
Programs in the Control Panel.

2.      Applications may be installed from the command prompt using CHANGE
USER /INSTALL and CHANGE USER /EXECUTE.

3.      Some applications do not complete installation until after the
Terminal Services server is rebooted.

III.    Monitoring and troubleshooting Terminal Services
A.      Introduction

1.      Administrators can administer sessions with clients using the
Terminal Services Manager.

2.      An administrator can monitor the overall performance of Terminal
Server using the Performance application, similar to monitoring any
other server.

3.      Rebooting the Terminal Services server is done through the TSSHUTDN
command from the command line.

4.      Refer to the "From the Classroom" explanation on page 685 for a
more detailed description of the TSSHUTDN command.

5.      Exercise 14-4 on page 686 demonstrates how to implement Remote
Control of a Terminal Services Session.
B.      Establishing Policies for Terminal Services

1.      Access to Terminal Services is most easily controlled through the
use of Group Polices.

2.      To set up a Terminal Services user account, users must have an
account on the server or the domain.
C.      Terminal Services Environment Versus Local Environment Settings
1.      Local environment may vary greatly from Terminal Services
Environment.
2.      Configurable settings:
a.      Network connections
b.      Printer settings 
c.      Available options in the start menu
d.      Available applications

IV.     Understanding Internet Information Services 5.0 (IIS 5.0)
A.      Introduction

1.      Internet Information Services 5.0 replaces IIS 4.0 that was
available through the Windows NT 4.0 Option Pack.

2.      Gives Windows 2000 Server the ability to host Web content for
Internet/intranet distribution.

3.      IIS 5.0 permits hosting more than one Web site without multihoming
the server.

4.      IIS is installed as a Windows 2000 component as opposed to Option
Pack installation in Windows NT 4.0.

5.      Exercise 14-5 on page 691 walks you through the Installation of
Internet Information Services.
B.      Monitoring, Configuring, and Troubleshooting Access to Web Sites
1.      Monitoring an IIS 5.0 Server is done through the Performance
utility.
2.      Performance can measure usage of RAM, CPU and physical disks
associated with the Web server.
3.      Process Accounting is a new feature that allows the administrator
to record information about how a Web site uses the CPU.
C.      Accessing Files and Folders via Web Services
1.      IIS 5.0 permits usage with Dfs available in Windows 2000 Server.
2.      IIS 5.0 can be administered using either the snap-in-based
Microsoft Management Console or the HTML-based administration utility.

3.      IIS 5.0 permits anonymous Web and FTP access to the server.  FTP is
used to make a Web-based location for the sharing of files.
a.      FTP clients can upload and download files to the server based on
their credentials.
b.      FTP server can be accessed using DOS, Internet Browser, or 3rd
party FTP client software.

4.      Server Level Administration
a.      At the server level, administration can set many different
parameters.
i.      MIME mappings provide the Web server with the ability to create a
common understanding of various file extensions and their parent
applications that client machines may not recognize.

ii.     Server Extensions that provide significant power for Web
developers, such as simplified publishing of sites, and added
HTML-based components that would otherwise require Web-based
programming. (Hit Counters, Dynamic Page Transitions, etc.)

iii.    Bandwidth Throttling allows the Web server to allocate bandwidth
provided by the Web connection to the Web server that requires the
most.

iv.     Master Web site properties for defaults can also be set.

5.      Site Level Administration
a.      At the site level, administration can set the following
parameters.

i.      IP addresses, HTTP headers and ports of the Web site.  Allows
Administrator to designate exact location of Web site.

ii.     The type of logging can be set in order to keep track of the
number and type of users the server is serving.  Certain strategies
should be applied to conserve server resources.

iii.    Custom error messages can be designed to maintain the look and
feel of the site even when an error occurs.

iv.     Permissions and Restriction settings can be designated at the site
level to prevent or grant access to a Web server based upon user,
computer, or network credentials