 Hello
SysAdminNews Readers!
System administrators are overworked people, and I’m sure none
of you admins out there will disagree with that assessment.
You already have enough to do - the last thing you need is a
lot of running around your building, or even worse, between
buildings, to install and update software
.
 |
Profile
Maker - Intuitive Desktop Management - FREE
Trial |
Windows 2000 Terminal Services is ready to ride to your rescue.
It’s a built in feature that is available with all Windows 2000
(and above) server packages. Among other timesaving features,
it lets you do almost anything to your server from anywhere
– including rebooting! Check out today’s article from TechTutorials
for details on how to configure Terminal Services on your server,
and take al look at some of the ways it can save you time. Terminal
Services - it’s the next best thing to being there.
Windows 2000 Terminal Services
By TechTutorials
Introduction
Terminal Services is a centralized computing architecture that
lets users execute Windows-based applications on a remote Windows
2000 server. Previously, a special edition of NT 4.0 called
Terminal Services Edition had to be installed to gain this functionality.
Now it is built into Windows 2000 Server and above. Terminal
Services supports a full range of clients inlcuding Windows
3.x 9x, NT, CE, 2000. With additional software it will also
support Unix, Macintosh and MS-DOS. Terminal Services enhances
computing environments by allowing companies to deploy a "thin
client" solution to deliver 32-bit Windows applications to a
wide range of legacy desktop hardware devices. This can be particularly
useful during the period of migration to Windows 2000.
During a virtual session, video, keyboard, and mouse information
is exchanged between the client and server. Because all of the
processing occurs at the server, the client can be very old
hardware that would not normally be able to run the application
on its own. Terminal Services main benefits are improved application
performance over slow network connections, easier to update
software, reduced hardware costs and provides administrators
the ability to remotely administer the server. The new version
also includes a great new feature that allows you to "remote
control" a client as can be done with SMS.
 |
FREE
Trial!!! Profile
Maker - Map Drives,
connect Network Printers & configure Shortcuts, Configure
Outlook, Office & IE settings, and more.
|
Terminal Services Modes
Terminal Services can be enabled in 1 of 2 modes, unfortunately,
you cannot enable both at the same time. In order to switch
between the 2 modes, you must use the add/remove programs control
panel. These modes are discussed below.
Remote Administration Mode
Ever used SMS's Remote Control feature that allows you to "shadow"
a user session? Remote administration mode is very similar.
It allows you to open a remote session to any server running
Terminal Services in this mode and remotely administer it. You
can perform nearly any task from your remote location that you
could while sitting in front of the server (including rebooting/shutdown).
Since it works through nearly any kind of connection, an administrator
could be at home and have the capability of configuring, maintaining
and troubleshooting these servers.
Remote Administration Mode Installation
It is highly recommended that you only install Terminal Services
on a server that has been installed on an NTFS partition.
- Open the Add/Remove Programs control panel.
- Click Add/Remove Windows Components.
- Select Terminal Services and click Next.
- On the next screen select Remote administration mode.
- You will need to reboot
Note: You do not need to enable terminal services licensing
for this mode.
Application Mode
This mode provides a way to distribute Windows-based programs
with a network server. It delivers the Windows 2000 desktop
and Windows-based applications to computers that might not normally
be able to run them. For example, you may work at a school where
all of the computers are using old hardware and can only run
Windows 3.x. At the same time you have a need to used Office
2000. Office 2000 obviously will not run on Windows 3.x, so
you can set up Terminal Services in application mode on a Windows
2000 and "serve" the Office 2000 applications to the Windows
3.x clients.
Application Mode Installation
It is highly recommended that you only install Terminal Services
on a server that has been installed on an NTFS partition.
- Open the Add/Remove Programs Control Panel.
- Click Add/Remove Windows Components.
- Select Terminal Services and click Next.
- In Terminal Services Setup, click Application server mode.
- Next, you need to choose whether you want permissions
to be compatible with Windows 2000 Users or with Terminal
Server 4.0 Users. The Windows 2000 Users option is the more
secure option.
- In Terminal Services Licensing Setup, specify whether
you want to license your entire network/enterprise or just
your domain and then provide the directory location for
the database. Click next.
- On the next scree click finish.
- You will need to reboot.
Note: Terminal Services Licensing is a required component.
It is recommended that you do not enable Terminal Services Licensing
on the same computer with Terminal Services. For more information
on licensing, click
here.
After installation, all shared applications should be re-installed.
Some older applications require an application compatibility
script to be run in order to correct registry issues and other
problems. Microsoft supplies such a script for Office 2000 in
the Office 2000 Resource Kit.
Client Installation
You will then need to install the client software on the client.
There are a couple of ways to install the client software. The
easiest way is to browse to the %SystemRoot%System32ClientsTsclientNet
directory on the server running terminal services. Here you
will see a "win16" and a "win32" folder. Select the one that
corresponds to the operating system that you will be using.
Inside the "win32" folder you will see 2 more folders titled
"disk1" and "disk2". You can place each of these on a floppy,
CD or copy them to the client hardrive. Another option is to
run the "Terminal Services Client Creator" which will walk you
through creating the setup floppies. In either case, when this
is done you can run the installation program which will install
the client services.
Additional Information
Communication between the client and server occurs using an
application-layer protocol called Remote Desktop Protocol(RDP).
This protocol is optimized for the transmission of graphical
data. RDP allows for automatic disconnection, remote configuration,
and supports three levels of encryption.
When utilizing Terminal Services in application mode, make sure
that there is only one version of the each application installed
on the server as application versions may share DLL files. For
example, both Microsoft Internet Explorer 3.x and Microsoft
Internet Explorer 4.x share various DLLs that will fail to work
properly when both versions are installed on the same server.
While optimized for Windows 32-bit programs, MS-DOS and 16-bit
Windows-based applications can be used as well. Note that the
latter require more memory. Typically, Microsoft recommends
8mb of RAM for every concurrent user that will be accessing
the server. This means that if you have 256mb of RAM installed
that you will be able to support about 32 typical users at a
time.
Originally published at http://www.techtutorials.com/tutorials/2000/terminal.shtml
MCMCSE.com is a popular certification portal / reference center.
It has an excellent knowledge base of certification tools for
a myriad of systems and is the sister site of tutorial portal
TechTutorials.com. Both sites are run by Jason Sprague and you
can find them at: www.techtutorials.com
and www.mcmcse.com. |
| WebmasterFree
Download |
| |
For
more free downloads from WebmasterFree - Click
Here |
|
