Re: Changing TS Licensing Mode

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



That's by design. Per User licenses are currently unmanaged, which
means that the Per User TS CAL count will not be decremented. You
will have to keep track of the number of connecting users by hand.
Documented here:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

_________________________________________________________
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?TWlrZQ==?= <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 07
sep 2006 in microsoft.public.windows.terminal_services:

Vera,

Yes, I didn't answer this in my first reply, I do have two
different machines, a license server, and the TS. I did make
the change last night from home, and was able to connect, so I
think I am good. One question I do have is that on the License
Server this morning, I went to lookat what it did to assign the
user CAL to me from last night ,and while the device CAL's show
who they are assigned to and when they will expire, the user
CAL's still show up as "non applicable", and that it hadn't
assigned a user CAL to me, but it did work for me last night.
Is that the way it works, or do I still have a configuration
issue.

Thanks,

Mike


"Mike" wrote:

Vera,

I see. I will check that in the morning. I assume that if I
save the mode as user CAL, my device CAL's will still work
normally, correct? Thanks for the reply.

Thanks,

Mike


"Vera Noest [MVP]" wrote:

You need to configure the licensing mode on the Terminal
Server, not on the TS Licensing Server.
You *do* have a separate Windows 2003 Terminal Server,
correct? You need one, because a SBS2003 server can only run
Remote Desktop for Administration, it cannot run Terminal
Services in multi-user mode. But an SBS2003 server *can* run
the 2003 TS Licensing Services to provide TS CALs for your
2003 Terminal Server.

_________________________________________________________
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?TWlrZQ==?= <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 06 sep 2006 in microsoft.public.windows.terminal_services:

Hi,

I have a SBS 2003 TS license server. I originally had 5
Device CAL's, and recently purchased 5 User CAL's, because
I need the flexibility of the user CAL. Anyway, I have
read on MS site that in order to use both types, you need
to change your licensing mode to user CAL mode. I think I
found where this is configured, which is "Admin tools | TS
Configuration | Server Settings. The only option I have is
"Remote Desktop for Administration" and there are no other
options. Am I in the right place, or do I need to look
somewhere else?

Thanks,

Mike



.



Relevant Pages

  • RE: local computer client access license error
    ... the Terminal Server Licensing server only has Per User CALS. ... Windows Server 2003 does not manage User CALs. ... even though there is a User CAL in the license server database, ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Confused about CALs
    ... You mention that the 5 CALs that come with the server do not ... Terminal Services client connection. ... License Server must be activated within 120 days of using the ...
    (microsoft.public.windows.terminal_services)
  • Re: Event ID 1004 No Terminal Server License
    ... The terminal server could not locate a license server in the kusch.de ... WINS/DNS, accepting network requests, and the Terminal Server Licensing ... The terminal server cannot issue a client license. ...
    (microsoft.public.windows.terminal_services)