Re: Licensing



Once again, thank you for your assistance.

"Vera Noest [MVP]" wrote:

Yes, you have to change the licensing mode of the Terminal Server
to "Per User" licensing, in Administrative Tools - Terminal
Services Configuration - Server Settings - Licensing Mode

Because it is currently set to the Per Device licensing mode, it is
looking for a Device TS CAL and cannot issue your Per User TS CALs.

You do not have to contact the Clearinghouse for this change.

Check this article, it explains that even after you have
switched licensing mode on the TS, your Per User TS CAL count will
not be decremented:

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

Oh, and hire a different company next time you need help with your
Terminal 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
16 feb 2006 in microsoft.public.windows.terminal_services:

Thank you for your efforts.

The TS / LicenseServer is running SP1
I have also configured the Registry Setting today to ensure that
the server is found

As the machine was built by an external company I have been
digging around some more and found the following:

The Terminal Server Licenses are actually User CALs
The Terminal sever [configured by external company] has Per
Device in the Configuration/Services setup.

The Terminal server Licensing:
Existing: Type: Built-in Total:Unlimited
Available: unlimited Issued: 0
Temporary: Type:Temporary Total: - Available:
-
Issued: 7
Windows 2003: Type: Open Total: 5 Available:
5
Issued: N/A

Therefore is the following remedy correct: select the Per User
setup within the Configuration and reboot? or will I have to
contact the clearing house

Any further info would be appreciated.



"Vera Noest [MVP]" wrote:

OK, I get the picture now, I believe. Things to check:

Is the type of TS CALs (Per Device, you wrote) matching the
licensing mode on the Terminal Server? You can check this in
Administrative Tools - Terminal Services Configuration - Server
Settings - Licensing Mode

Are you running SP1 on the server? If not, check this:

834651 - Terminal Services licensing mode changes from Per User
or from Per Device to an invalid value after you add or remove
a Windows component
http://support.microsoft.com/?kbid=834651

Do the users of the 5 clients have write permission on the
Licensing key in the registry of the client computers? That's
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.

Have you pointed the Terminal Server to the TS Licensing
Server?

279561 - How to Override the License Server Discovery Process
in Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561

_________________________________________________________
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 15 feb 2006 in microsoft.public.windows.terminal_services:

Sorry if I confused you on this.

We only have 5 machines that require the use of the TS...each
one is XP Pro and both the CAL and TS Cals have been
purchased.

The TS shows in the License Manager that each machine has
been issued with a Temporary Licence. I will post the
requested information after taking the info at work tomorrow.

4 of the machines belong to a Workgroup at one of our branch
offices and connect via our VPN. The TS / TS Licence manager
has been activated and both are installed on the same machine
[operating in Enterprise mode] as the TS is configured to run
on the domain created using Active Directory.


Thanks for your assitance

"Vera Noest [MVP]" wrote:

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: License Service
    ... Q. What are the differences between user CALs and device CALs? ... A user CAL permits one user to access the server ... No. SBS 2003 R2 CALs are not concurrent. ... details the licensing mode is set to per server for x concurrent ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 License Disappears - Now shows 1 as Maximum
    ... to use the Licensing module in Server Management to back up the CALs. ... are built-in wizards there to backup and restore your CALs. ...
    (microsoft.public.windows.server.sbs)
  • RE: unable to login to sbs03 domain with 2 unused CALs on server
    ... For the problem why the CALs were reset, it can be caused by following ... the licensing checks that are performed by the Windows Small Business ... Server license service will fail because the license check or the Active ... Worldwide customers can use the Guide to Worldwide Microsoft Licensing ...
    (microsoft.public.windows.server.sbs)
  • Re: Licensing
    ... The Terminal Server Licenses are actually User CALs ... The Terminal server Licensing: ... Administrative Tools - Terminal Services Configuration - Server ...
    (microsoft.public.windows.terminal_services)
  • Re: XP Home User Temp Licence from W2K TS Box
    ... Keep an eye on the TS Licensing Manager on the 2003 DC, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... CALs issued. ...
    (microsoft.public.win2000.termserv.clients)