Re: Adding new client to 2003 server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

You're welcome! And yes, that happens all the time: you *expect*
something to be complicated, and thus you overlook the easy
solution :-)
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VGluYQ==?= <Tina@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 12
okt 2006 in microsoft.public.windows.terminal_services:

Thank you, I suppose I'm making this harder than it needs to
be. I appreciate the explanation!

"Vera Noest [MVP]" wrote:

You don't have to do anything.

TS CALs have an expiration date of 52-89 days after issueing.
Licenses that are not used (because the old client does not
connect to the TS anymore) will automatically be returned to
the LS after the expiration date. In the meantime, your new
clients will get a temporary TS CAL, which is valid for 90
days.

Note that these time periods are choosen to make sure that your
temporary license lasts long enough for the old license to
become available again. So replacing one client with another
can never cause you to run out of TS CALs.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VGluYQ==?= <Tina@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
12 okt 2006 in microsoft.public.windows.terminal_services:

Thanks for the response. We are using terminal services so
all the software runs from the server. I have a question
about the TS licenses. These computers are actually
replacements. Do I need to transfer the current license from
the old computer to the replacement computer? Or is that
something I should manage in Active Directory???

"Kshaeta" wrote:
First, you only need terminal services if you want all of
the software
to run on your central server (much like a null terminal
connected to a
UNIX box, but prettier). It allows for centralization of
your
programs for easier management, as well as gives you more
control over what people can do. It also alleviates a lot
of security issues. Terminal services can also allow you to
access it via web access. So (theoretically) you could
access your data from a web browser. It makes it easier for
users to move from computer to computer, since their
settings are all saved on the terminal server.

But that's beyond just a network. If all you want is to
setup each workstation, and then install programs (word,
excel, donkey kong, whatever) on each workstation, you don't
need terminal services. You would just need to setup each
system the way you like, and then creates directories to
store data on the server(s), and create shares on the server
(so the clients can connect). There are quite a few steps to
this process, so I'll assume it's not what you want.


For terminal server, you would need:

Windows XP/2000 which comes with remote desktop (aka
terminal services) installed.

A windows 2000/2003 server to run terminal server, as well
as a server to run terminal services licensing.

You will need to purchase TS licenses, one for each user (or
computer) from a licensed microsoft distributor.

That's as brief as I get. I can't really go into the
particulars, it would take to much time.

If you go to windows website, you can find a section on
Terminal Server and some white papers. It might help.

Here are some links:
http://www.brianmadden.com/content/content.asp?id=154
http://www.brianmadden.com/subject.asp?ID=3
http://www.microsoft.com/windowsserver2003/techinfo/overview/
qui ckstart.mspx#EJAA
http://technet2.microsoft.com/windowsserver/en/whitepapers.ms
px


Good luck!
bill
.

Relevant Pages

  • Re: default printer
    ... Components - Terminal Services - Client/Server data redirection ... Specifies whether the client default printer is automatically set ... as the default printer in a Terminal Services session. ... the terminal server automatically maps the client default ...
    (microsoft.public.windows.terminal_services)
  • RE: Single server scenario workable?
    ... Your client can also go to a hosting provider for their terminal server ... you enable terminal services on a DC you will not have a local Remote ...
    (microsoft.public.windows.terminal_services)
  • Re: License Recovery
    ... Terminal Server, since the answer to your questions depends partly ... *No* client OS comes with a build-in license. ... In general, you cannot reallocate licenses, and it should not be ... If you run W2K on your TS and your TS CALs were installed *after* ...
    (microsoft.public.win2000.termserv.apps)
  • Re: SOME Windows 2003 Terminal Server users will log on to a blank screen
    ... Are you sure that the problem is user-related and not client ... When users change workstations, does the problem ... Q. Sometimes when I connect to my terminal server, ... > Windows Server 2003 with terminal services running on it. ...
    (microsoft.public.windows.terminal_services)
  • Re: Adding new client to 2003 server
    ... TS CALs have an expiration date of 52-89 days after issueing. ... Licenses that are not used (because the old client does not ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)