|
Home > Archive > alt.certification.mcse > October 2002 > 70-215 and Term Services
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
70-215 and Term Services
|
|
|
| I'm having trouble with the practice exams on Terminal Service
questions, as I have been basically answering the questions based on
study guides. I have Server and workstation, but I'm confused as to
setting up the "application server" . I'd like some walkthru step by
step sample. I have the 120 day version of server that I've installed
probably 120 times by now. It asks for a license for the application
server, but in my readings I recall that the 2k Pro client comes w/ a
license. So why does it ask for a license on the server. I'm a PC
Anywhere kinda guy. I need some external motivation, because I keep
funking this section.
| |
| Rob Hammersmith 2002-10-08, 9:25 am |
| Saying that W2K Pro comes with a TS CAL is misleading. W2K and XP will
obtain an "Existing" TS CAL "token" from a Terminal Server Licensing Server.
If a Terminal Server Licensing Server does not exist on the network, W2K and
XP can not obtain a TS CAL "token". So to say that they "comes with a
license" is misleading. More explanation:
Every client that attempts to establish a terminal server session on a TS in
Application Mode is prompted by the TS for the client's TS CAL token. If the
client has a valid token, the TS proceeds to authenticate the user and
establish the TS session. If the client does not have a token, the TS
directs the client to a Terminal Server Licensing Server on the network to
obtain a token. The TS Licensing server asks the client for it's operating
system version. If the client is W2K (Pro or Server) or XP, the TS Licensing
Server gives the client an "Existing" TS CAL token. If the client is
anything other than W2K or XP, the TS Licensing Server gives the client an
available "Purchased" TS CAL token that has been installed on the TS
Licensing Server. If the TS Licensing Server has no "Purchased" TS CAL
tokens available for the non-W2K/XP client, it will give the client a
"Temporary" TS CAL token that will work like any other TS CAL token but only
for 90 days. When a TS is presented with a "Temporary" TS CAL, the TS
directs the client to try an obtain a "Purchased" TS CAL token. If the
client is not able to obtain a "Purchased" TS CAL, the TS will allow the
client to establish a TS session only if the 90 day "Temporary" TS CAL has
not expired. If it has expired, the client is denied access to the TS
session.
Note: There is a 4th type of token called an "Internet Connection" TS CAL
token, but it only works for anonymous connections from the Internet.
If a Terminal Server Licensing Server is not on the network, clients can not
obtain TS CAL tokens to present to the TS in order to establish sessions. If
the TS has been in Application Mode for less than 90 days, the TS will allow
clients to establish TS sessions without presenting TS CAL tokens. If the TS
has been in Application Mode for more that 90 days, clients are denied
access to TS sessions if they have no TS CAL token, or if their "Temporary"
token has expired and they could not obtain a "Purchased" TS CAL token. This
is why a TS in Application Mode says you must have a TS Licensing Server on
the network within 90 days, or terminal services will cease to function.
--
Rob Hammersmith
MCP, CCEA
"bt" <No@spam.com> wrote in message
news:45h4quoq0ktvjh8o5fjnqs7hm
s4t5o8p79@4ax.com...
> I'm having trouble with the practice exams on Terminal Service
> questions, as I have been basically answering the questions based on
> study guides. I have Server and workstation, but I'm confused as to
> setting up the "application server" . I'd like some walkthru step by
> step sample. I have the 120 day version of server that I've installed
> probably 120 times by now. It asks for a license for the application
> server, but in my readings I recall that the 2k Pro client comes w/ a
> license. So why does it ask for a license on the server. I'm a PC
> Anywhere kinda guy. I need some external motivation, because I keep
> funking this section.
| |
| aaron@[aaronguilmette][.][com] 2002-10-08, 10:24 am |
| W2K Terminal Services is the best thing to happen to Windows computing
(IMHO) in a long time. If you've ever been to a library and used a
dumb terminal (or have worked in a UNIX environment), you've been
exposed to a TS type of environment. The concept of Terminal Server
is that you put all of the computing power in one spot and then send
screen shots and mouse/keyb. info back and forth.
Let's say you have 20 486dx33's running Windows 95 and you just
invested in a new server. You have the licenses for Office 2000, but
none of the computers are fast enough to install Office, and you don't
have the time, money, or energy to deploy 20 new workstations as well
as migrate all of the old data, etc. Enter Terminal Server. Install
Terminal Services on your Windows 2000 server, configure it in
application mode, and install Office 2000. You run the TS client
setup on all of your workstations and create a user profile on the
Terminal Server that runs "Microsoft Word." You configure a
connection object on a client and you connect to the TS. It runs MS
Word for you. No client upgrade needed--your server supplies the
necessary horsepower to run your application and only passes
keys/clicks and screen information back and forth.
If you purchase Citrix MetaFrame, you get specialized client software
that will allow *nix machines to connect to your Windows server and
run applications as well. That way, if you have a bunch of UNIX CAD
designers that need to compose MS-Word documents, you don't need to
give the designers a separate PC to do their word processing/email
tasks. Simply install the Citrix MetaFrame client and they can click
an icon on their desktop and have a terminal window session with a
Windows server in which they can do their word processing, email, or
whatever else they need to do without leaving their UNIX environment.
Now, where TS *differs* from programs like PCAnywhere, VNC, or other
remote control products is that TS isn't sending all bitmaps (which
makes PCAnywhere/VNC/et. al.) *extremely slow.* Instead, TS relies on
standard windowing APIs and sends coordinates back to the client
(which the client processes and draws itself), making the entire
process seem local, not sluggish. If you've ever used a remote X
session on a *nix box, you're familiar with the concept and how well
it can work.
There are two licensing modes for Terminal Server: Remote
Administration and Application Server. Remote Administration is
designed for just that--remotely administering the server. It
provides two client licenses and lets you run TS normally.
Application Server mode allows you to purchase licenses so you can
harness your server's CPU cycles to run applications as opposed to
running network-installations of applications (generally a bad idea)
or upgrading your client PCs.
For learning purposes, however, the usage is the same. You can
configure Terminal Services in Remote Administration mode and the
server will function the same way as it does in Application Server
mode--the only difference will be the number of licenses you consume.
As soon as you configure TS, one thing you will notice is that while
installing many software packages is that you will now have to do it
through Add/Remove Programs so that Windows can configure the
application for all users who will log on to the system.
If you have at least two PCs, give it a whirl. If you need any help,
just email me or reply here.
Aaron
bt <No@spam.com> wrote in message news:< 45h4quoq0ktvjh8o5fjnqs7hms4t5o
8p79@4ax.com>...
> I'm having trouble with the practice exams on Terminal Service
> questions, as I have been basically answering the questions based on
> study guides. I have Server and workstation, but I'm confused as to
> setting up the "application server" . I'd like some walkthru step by
> step sample. I have the 120 day version of server that I've installed
> probably 120 times by now. It asks for a license for the application
> server, but in my readings I recall that the 2k Pro client comes w/ a
> license. So why does it ask for a license on the server. I'm a PC
> Anywhere kinda guy. I need some external motivation, because I keep
> funking this section.
| |
|
| aaron@aaronguilmette.com (aaron@[aaronguilmette][.][com]) wrote in message news:<e80282cd.0210080625.b28b14f@posting.google.com>...
~snip~
> Aaron
>
Aaron and Rob,
Excellent posts! A few months ago I got a Compaq DL380 G2 rack server
and had to put Win2k TS on it to run an Accounting package here at
work. Took me aages to wade thru documents on Technet and the net in
general before I finally (kind of) got the whole "Win2k Pro has a TS
license but you still need to install a license server" etc etc thing.
I got it all happening, but it was painful compared to the old NT
Server 4 Terminal Server edition that was previously being used. Works
really well though once sorted, I think.
The 2 posts also cleared up some things that I wasn't 100% on so I
think I'll keep a copy for future reference. Nice one!
Regards,
AmC.
| |
|
| yeah, thanks to you both. I saved the posts.
|
|
|
|
|