RE: ts cal problem



OK, I'm glad that the problem is solved, and thanks for posting the
results back here, Cristian!

_________________________________________________________
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?Q3Jpc3RpYW4gQ2FyYWNjaW8=?=
<CristianCaraccio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 31 mar 2007
in microsoft.public.windows.terminal_services:

Don't worry, be happy !
Today problem solved, the problem was that at first - second
log-on the license is temp, now all device have good license,
thanks for the help of all, regards.
Cristian Caraccio
Italy


"Vera Noest [MVP]" wrote:

Matt, I'm not having a bad day, and I don't start a flame.

I'm not even critizing you for giving a solution which doesn't
fix the problem, I object to the fact that you tell people that
a certain situation (permanent license is not issued on second
connection despite the fact that a permanent license is
available) can be safely ignored because you believe that this
is a flaw in the licensing issueing mechanism. I feel that this
is ill advice which can cause people to get into a situation
where users are refused to connect.

And I don't provide the next step, because Cristian has already
replied that "Today is the first day I use this psa", so it's
likely that he only has connected once.

But for the sake of completeness, the next step is to check the
EventLog.
_________________________________________________________
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?TWF0dFNoZWxs?= <MattShell@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 30 mar 2007 in
microsoft.public.windows.terminal_services:

Vera,

I was under, and maybe mistaken, impression that the period
that the temp liciences would expire was already over,
meaning that they were not expiring.
From his next post I would say that he has not had this time
pass yet which
means the server could disconnect and not let the device back
in again. Which as you stated would be a problem.

From here I would advise him to google out his device and TS
and see if there are some problems with it accepting TS Cals
for the device and if there is a workaround in that way, not
sit on his thumbs and wait.

I also stated that I have had devices that do not pickup
licences as they should based on the fact that they don't,
maybe I do have a problem, but I have yet to work with a
Terminal Server that always issues on the second time.

Vera, you critize me for supposedly giving a solution that
will not fix his problem, yet all you do is jump on the board
in flame me? Why don't you provide the next step then
because obviously I don't understand how Terminal Services
works in the depth that you do, oh powerful MVP. You having
a bad day? Lets fix the problem rather than making this a
personal fight.

Matt



"Vera Noest [MVP]" wrote:

comments inline.

=?Utf-8?B?TWF0dFNoZWxs?=
<MattShell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 30 mar 2007
in microsoft.public.windows.terminal_services:

TS Cals are given as temporary at first and after the
second log on (Microsoft says) they should recieve a
permantant one. Here is the deal, I don't believe that
Mircosoft quite has this worked out as I have had
computers that have loged on 7 or 8 times and they
continue to recieve a temp cal even though I have permant
ones to hand out.

Matt, I can assure you that "Microsoft has worked this out".
If your clients are not receiving a permanent TS CAL after
the second logon, you have a problem.

I would not worry too much about it. It is nice to see
exactly how many you have and are using in one screen, but
as along as people are not getting denied access, and you
are within the rules of using TS Cal's I would not sweat
it to much.

Are you seriously advising posters here to just sit and wait
until their users get refused?
How exactly are you going to explain that to them when (not
if) that happens? Something like: "Yes, I have noticed from
the beginning that licenses were not issued as they should,
but I believed it was a bug in Windows, so I didn't take any
action to solve the problem."?
I know that neither my users nor my boss would be impressed
by such an explanation.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
.



Relevant Pages

  • Re: Bandwidth
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Vera Noest schreef: ... servers session takes. ...
    (microsoft.public.windows.terminal_services)
  • Re: Office Concurrent Licenses
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... You must obtain a license to the Software for each ... Vera Noest wrote: ...
    (microsoft.public.windows.terminal_services)
  • Re: internate links
    ... > Vera Noest ... > MCSE,CCEA, Microsoft MVP - Terminal Server ... >> restore default level all those things in internate explorer ...
    (microsoft.public.windows.terminal_services)
  • Re: No more logon on Terminal Server possible
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... SQL troubleshooting: http://sql.veranoest.net ... >> Vera Noest ... >> MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Any way to make the Remote Desktop Snap-in portable?
    ... Vera Noest wrote: ... MCSE, CCEA, Microsoft MVP - Terminal Server ... The XML file is binary or encrypted as I can't see the ...
    (microsoft.public.windows.terminal_services)