Don't know what to head this?????

Tech-Archive recommends: Speed Up your PC by fixing your registry

We run all our branches on terminal server with nothing special added to it
other than Office and Bit defender AV, we just installed Kerrige (K8), at
one of our branches. K8 is our new Sales Account and so on package it runs
on redhat and a proprietary database.

Our problem is this. The K8 License server see’s our TS as one client and
therefore misappropriates the licenses, the licensing is a bit complicated so
I am not going to get into it, but surface to say the license server gets it
wrong, so we run out of licenses. Secondly the licensing only allows for 10
concurrent connections from one terminal, so if 10 clients log on no one else
can, which is a problem as our one branch has 23 clients and then there are
still 4 more to go on this system. But in the K8 management app each
terminal is seen separately, which is what it is supposed to do.

I have spoken to someone who run’s TS on this app but he has chosen the
“Start the following program at logon” option and choose to load their client
as the explorer. He says that works fine, but his users do not need access
to office and other apps where mine do. As far as I know we are their only
site to be running like that.

So we have a problem. I know nothing about this app so I cannot give you
much more info on how they work stuff out internally, but they are trying to
tell me that I should also look for a solution to what is essentially their
problem. So Here I am, is there any way to ‘fool’ the system into thinking
that all the connections are coming for different terminals, by changing
something in the TS config.

Please and help here would be a appreciated, because, firstly I need this
solved ASAP for my sake, and secondly, I would love to solve it before they
do.

Thanx
.

Relevant Pages

  • RE: "You do not have access to logon to this Session" from remote
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > to get W2K3 TS licenses issued, installed, TSLS running on W2K3 ... > preferred Windows 2000 Terminal Services license server). ... If yes, then 2003 terminals ...
    (microsoft.public.windows.terminal_services)
  • Re: licensing problem
    ... under "Existing Windows 2000 Server - Terminal Services CAL token ... The thin clients need a purchased license. ... 14 terminals are win2k ...
    (microsoft.public.windows.terminal_services)
  • Re: Win2003 Terminal Server with 5 License from MSDN
    ... You can run the TSLS on the 2003 Terminal Server, ... there doesnt appear to be any Windows TerminalS ervices ... >> The terminal server cannot issue a client license. ...
    (microsoft.public.windows.terminal_services)
  • RE: Dont know what to head this?????
    ... I am not going to get into it, but surface to say the license server gets it ... But in the K8 management app each ... “Start the following program at logon” option and choose to load their client ... that all the connections are coming for different terminals, ...
    (microsoft.public.windows.terminal_services)
  • RE: Dont know what to head this?????
    ... I am not going to get into it, but surface to say the license server gets it ... But in the K8 management app each ... “Start the following program at logon” option and choose to load their client ... that all the connections are coming for different terminals, ...
    (microsoft.public.windows.terminal_services)