Re: Licensing



I don't understand what you mean with this:
The licenses are soecifically to do with the 5 machines only,
hence no more licenses are required

Every client which connects to the Terminal Server needs both a CAL
and a TS CAL.

Can you post the complete information from the TS Licensing
Manager? I.e. the figures showing under the headings Type - Total -
Available - Issued, for all types of licenses?

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

"=?Utf-8?B?Z2l6bW8=?=" <gizmo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
14 feb 2006 in microsoft.public.windows.terminal_services:

Thanks for your info.

There are no issues shown in the eventlog.
The licenses are soecifically to do with the 5 machines only,
hence no more licenses are required

After looking through the various Manager app, the TS Server
fully qualified domain name is shown where querying the
properties etc.

"Vera Noest [MVP]" wrote:

Have you checked in the TS Licensing Manager if you still have
TS CALs available? Sounds like all 5 TS CALs have already been
issued?

Is there anything in the EventLog on the terminal Server
regarding licensing? More specifically: can the TS locate the
TS Licensing Server?

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

"=?Utf-8?B?Z2l6bW8=?=" <gizmo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 14 feb 2006 in microsoft.public.windows.terminal_services:

Scenario:
Win2003 TS machine running on standalone box within the
Active-Directory. Machine is also running the Licensing
manager and everything seems to be correct
5 Cals running as Per Device on the machine and all been
activated

Issue:
We bought a smaller company out sometime ago and they use Win
XP Pro on their machines but in a peer-to-peer environment.
These users are now receiving the pop-up message about their
temporary licence about to finish.

I have checked the License manager and it shows temporary
licenses for these users but it also shows for two PCs on the
Domain as temporary.

I read that the TS should be configured as Domain not
Enterprise for these users but requires enterprise if its in
an active-directory domain [which it is]
My fear is that they will not be able to connect anymore....
1. Is this correct
2. What is require to allow these licences to become
permanent on these machines

any help will be appreciated!
.



Relevant Pages

  • Re: Windows 2000 terminal servers in 2003 domain
    ... So, in my case, it will not work with my purchsed W2K TS per device CALs (at ... CAL when they connect to your W2K Terminal Server. ... Server can have Windows 2000 Terminal Server per Device Licenses ...
    (microsoft.public.windows.terminal_services)
  • Re: What is the best licensing option for TS?
    ... which will cost you a lot more than the 2003 TS CALs. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... I don't mind eating the licenses if in the long run I am better ... I have read that XP Pro clients come with a built in TS ...
    (microsoft.public.windows.terminal_services)
  • Re: Corrupted Licenses?
    ... I'll need to check the affected machines, but mine doesn't show any entries ... it was a message that Terminal Server cannot ... Jer ... > Per User or Per Device licenses? ...
    (microsoft.public.windows.terminal_services)
  • Licensing Server question
    ... 200 devices licenses for the CALs. ... There are some additional Win95 machines ... Win95 machines don't take up the Device CALs, ... How does Windows Server 2003 ...
    (microsoft.public.windows.server.general)
  • Re: Terminal server using temporary license instead of installed CAL
    ... Thanks for the response. ... >822134 - The Function of Terminal Server CALs in Windows ... >> licenses??? ...
    (microsoft.public.windows.terminal_services)