[THIN] Re: TS Licensing

you won't see per user licenses get handed out.  for per user, it just
checks that a valid licenses server is there and that's the end of it.  The
downisde is that if that server goes down, users can't connect where with a
per device, if the server is down but the device has a valid token, it's
good to go.

There's a good write up about TS Licensing at msterminalservices.org by
Michael Burke

http://www.msterminalservices.org/articles/Terminal-Server-License-Service-Discovery-Part1.html


On 7/30/07, Jim Medeiros <jmedpc@xxxxxxxxxxx> wrote:
>
>  Great question.  The old TS Lic server was setup with per device
> licenses.  We converted our licenses to per user and installed the per user
> on the new lic server.  I just noticed that we have given out 2 temporary
> per device lic recently on the new server.
>
> Thanks!
>
> Jim
>
> ----- Original Message -----
> *From:* Greg Reese <gareese@xxxxxxxxx>
> *To:* thin@xxxxxxxxxxxxx
> *Sent:* Monday, July 30, 2007 10:06 AM
> *Subject:* [THIN] Re: TS Licensing
>
>
> did you set up the new one per device or per user?
>
> Greg
>
>
> On 7/30/07, Jim Medeiros <jmedpc@xxxxxxxxxxx> wrote:
> >
> >  We recently installed a new MS TS Licensing service.  We activated our
> > licenses and eventually turned off the old TS Licensing service on the old
> > server.  It has been a few weeks now and still none of our clients have
> > received a license from the new server.  I found a utility (script) that you
> > can run on your TS servers to determine (and change) your current TS License
> > server that it is using.  All our Citrix servers are pointing to the new
> > server when I run this script, but still no users are getting licenses from
> > it.
> >
> > Does anyone have any suggestions on how I can troubleshoot this?  We
> > noticed (before that change) that several client licenses were about to
> > expire so we would expect that some licenses would have been issued by now.
> > However, when I look at TS licensing it shows that 0 have been issued.
> >
> > Thank you,
> >
> > Jim
> >
>
>

Other related posts: