Re: How does Terminal Service Setup

From: Vera Noest [MVP] (Vera.Noest_at_remove-this.hem.utfors.se)
Date: 12/14/04 

Date: Tue, 14 Dec 2004 07:30:10 -0800

Installing Terminal Services on a 2003 server implies "Application
mode" (as it was called in W2K). This means you need a Licensing
Server and TS CALs, and you get unlimited user connections.

If you only want Remote Administration, you do not install
Terminal Services at all. You just enable Remote Administration in
System - properties - Remote, just like in XP.
Then you get a maximum of 2 connections, and you don't need
licensing.

What is it you want, Remote Administration or multi-user Terminal
Services?

 --
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"Carlos" <c@here.com> wrote on 14 dec 2004:

> I dont quite understand what you mean by this?
> When I go to install Termninal Services on the other server, the
> only option I have it for Full Security or Relaxed Security. Am
> I missing something, can you please elaborate a bit more.
>
> Thanks
>
> Carlos
>
> "Matthew Harris [MVP]" <harris@crocker.ucdavis.edu> wrote in
> message
> news:384A2CF6-C1C5-4927-9A6D-99DE81EE9DDC@microsoft.com...
>>A terminal services licensing server is only required if you
>>have terminal
>> services in application mode, not if you have it in remote
>> administration mode. If you have terminal services in remote
>> administration mode then you
>> are fine and don't need to do anything else.
>>
>> -M
>>
>> "Carlos" wrote:
>>
>>> The other servers already has Terminal Server installed on the
>>> "the default"
>>> of 2 connections maximum. So that is probably why it did not
>>> detect it. What are my options now? Please advise.
>>>
>>> Carlos
>>>
>>>
>>>
>>> "Matthew Harris [MVP]" <harris@crocker.ucdavis.edu> wrote in
>>> message
>>> news:88379DD6-05D9-4F72-9A10-3198EDCCD14E@microsoft.com...
>>> > All the other terminal servers should search your domain
>>> > automatically to
>>> > find the activated TS license server. you shouldn't have to
>>> > tell the terminal servers where the TS license server is, it
>>> > should be discovered
>>> > automatically. From the TS FAQ at
>>> >
http://www.microsoft.com/windowsserver2003/community/centers/
>>> > terminal/terminal_faq.mspx:
>>> >
>>> > Q. How does a terminal server discover a Terminal Services
>>> > licensing server?
>>> > (How does TS look for license server?)
>>> >
>>> > A. How the terminal server discovers the licensing server
>>> > depends on the
>>> > environment:
>>> >
>>> > For Windows 2000 Terminal Servers:
>>> >
>>> > . For a Windows 2000 domain the terminal server will
>>> > enumerate the domain
>>> > controllers, and check with each to see if it hosts a
>>> > licensing server in
>>> > Domain mode. It will then check with Active DirectoryŽ for
>>> > any licensing
>>> > servers in Enterprise mode. The terminal server creates two
>>> > lists, one for
>>> > Domain and one for Enterprise. It will first try to connect
>>> > to a Domain licensing server, or failing that, an Enterprise
>>> > licensing server.
>>> >
>>> > . Alternately, for a Windows NT 4.0 domain or workgroup, the
>>> > terminal server
>>> > will broadcast to the subnet, and any licensing server will
>>> > respond. Note
>>> > this means that the terminal server can only discover
>>> > licensing servers in
>>> > the same subnet.
>>> >
>>> > . If you use the registry-key override, then the terminal
>>> > will not use the
>>> > licensing server names found in the discovery, it will speak
>>> > directly to
>>> > the
>>> > licensing server listed in the registry key (see Q239107).
>>> > The discovery
>>> > process will still run, but the results will be ignored.
>>> >
>>> > . Once the terminal server has compiled a list of available
>>> > licensing servers, it will select one of these at random to
>>> > use. It will ping that
>>> > server once every two hours to ensure the licensing service
>>> > is still running,
>>> > and restart the discovery process if it is not. This is a
>>> > very limited communication, requiring negligible bandwidth
>>> > from the network, the terminal
>>> > server or the licensing server. The poll period can be
>>> > changed through registry entries.
>>> >
>>> >
>>> > For Windows Server 2003 Terminal Servers:
>>> >
>>> > . First the terminal server checks for license servers
>>> > listed in the registry (see Q279561 How to Override the
>>> > License Server Discovery Process
>>> > in
>>> > Windows Server 2003). If one of these license servers can be
>>> > contacted, discovery ends.
>>> >
>>> > . Otherwise, for a Windows 2000 or Windows Server 2003
>>> > domain the terminal
>>> > server will check with Active DirectoryŽ for any licensing
>>> > servers in Enterprise mode, found in the same site. If one
>>> > is found, and can be contacted, discovery ends. If not, the
>>> > terminal server will enumerate the
>>> > domain controllers (first on-site, then off-site), and check
>>> > with each to
>>> > see
>>> > if it hosts a licensing server in Domain mode. The first one
>>> > found will end
>>> > the discovery process.
>>> >
>>> > . Alternately, for a Windows NT 4.0 domain or workgroup, the
>>> > terminal server
>>> > will broadcast to the subnet, and any licensing server will
>>> > respond. Note
>>> > that this means that the terminal server can only discover
>>> > licensing servers
>>> > in the same subnet.
>>> >
>>> >
>>> > See the licensing white paper for more information.
>>> >
>>> > Hope this helps.
>>> >
>>> > -M
>>> >
>>> > "Carlos" wrote:
>>> >
>>> >> I am not sure I quite understand how this works. Okay I
>>> >> have 5 servers and
>>> >> they are all in the same network, and all Windows Server
>>> >> 2003. I have set
>>> >> one of them up as the Terminal Server Licensing Server. I
>>> >> got it activitated
>>> >> with the cals and all that jazz. Its activated and ready to
>>> >> rock. My problem
>>> >> is I dont know what I am suppose to do with the other
>>> >> servers. How do I
>>> >> set
>>> >> up properly so they reference the License Server. What am I
>>> >> to install on
>>> >> the other server do I go Add/Remove Program and and select
>>> >> Terminal server?
>>> >> If so how does it know to link to the main server for the
>>> >> license. If this
>>> >> not the right thing to do, then what is, what I am suppose
>>> >> to do/configure
>>> >> on the other server so they reference the Terminal License
>>> >> server?
>>> >>
>>> >> Please advise,
>>> >> Thanks.
>>> >> Carl

Relevant Pages

  • Re: Does Terminal Server Licensing turn off Remote Desktop for Adm
    ... Why would you keep Terminal Server Licensing Service, ... There is no need whatsoever for TS Licensing in this situation. ... Remote Desktop for Administration does *not* need any TS CALs, ... a license after I have installed Terminal Services?" ...
    (microsoft.public.win2000.termserv.apps)
  • Re: No terminal service license is available.
    ... Remote Desktop for Administration. ... without the need to install a TS Licensing Server ... As soon as you install full-blown Terminal Services (in Control ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services Licensing --- An opinion
    ... we'll change the licensing as you suggested. ... > express an opinion about Terminal Services Licensing. ... A large chunk of that cost is, ... > the CALs for the Server Operating system. ...
    (microsoft.public.windows.server.general)
  • Re: Licensing - Remote Desktop for Administration
    ... So this sentence says that TS licensing is independent from OS ... It is not possible to have more than one console session (for ... If you use Terminal Services, *all* normal connections need a TS ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • RE: Remote Administration on W2K
    ... Subject: Remote Administration on W2K ... Well I replaced the files on my test server with the ones I downloaded from ... To copy files with the built-in TS, use RDPClip from the W2K Resource ... When you speak of terminal services - if by "unnecessary load" you mean ...
    (Security-Basics)