Re: Terminal server licence problem

Thanks for your help, I have posted in the SBS forum for the time being to
resolve the licence issue and will come back to you if necessary

Thanks
Paul

"Vera Noest [MVP]" wrote:

Since you do not have a TS Licensing problem, and *probably* a SBS
licensing problem, I suggest that you post in a SBS newsgroup.
The only thing I know is that SBS OS licensing is different from
standard 2003 server.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?UGF1bA==?= <paulbrett@xxxxxxxxxxxxxxx> wrote on 30 okt
2006:

The TS is set for 'per user' in the configuration. I have 10
'user' CALs There are several errors in the logs; some exchange
errors which we dont use anyway and
: Error 5513: lost the SID reestablish trust relationship.
: (however these
all relate to local machines not remote and all of the local
machines work fine.....?
And error 1111: all relating to printer drivers that are
installed on the local machines but the server does not
recognise. There are NO error logs relating to remote machines
attempting to connect to the server although many attempts have
been made and declined by the server unless the /console command
is used.

HOWEVER, there does seem to be a licencing problem.
In the licencing managment it states there are 15 licences
installed (on the SBS server) yet a maximum usage of 8 is
listed... I cannot find tany way of setting the maximum
connections to match the number of licences available

Thanks for your continued help
Paul

"Vera Noest [MVP]" wrote:

You write that you installed the TS CALs as Per user TS CAL.
Have you checked that the TS is configured to use the "Per
User" licensing mode? If not, you should see in the TS
Licensing Server that it has issued temporary Per Device TS
CALs. If the TS *is* in the Per User licensing mode, then TS
Licensing is *not* the cause of the problem, since Per User
licensing is currently unmanaged.

Then you should check the OS licensing status instead.
The error message that you get usually indicates a shortage of
"normal" CALs (not TS CALs).
Can you check the EventLog on the server and post the EventID,
Source and Description? The Events there should tell you where
excatly the problem lies.

If the above doesn't solve it, also check the number of allowed
connections on the TS, in terminal Services Configuration -
RDP-tcp properties - Network Card.
_________________________________________________________
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?UGF1bA==?= <paulbrett@xxxxxxxxxxxxxxx> wrote on 29
okt 2006 in microsoft.public.windows.terminal_services:

I have a Server running SBS 2003 enterprise edition (acting
as the licencing server and server to the 10 pcs in this
(main) office) and a terminal server running server 2003
standard edition to connect our second office to our software
and database here.

If i run remote desktop from any client outside of this
(main) office I get the message that the maximum number of
licences have been exceeded. The server is in 'application
mode'. If i go to the licencing screen and select the
licencing server it clearly shows 10 'user' cals (server
2003) and windows 2000 'device' cals set to 'unlimited'.

Is there anything else I can check to see why it says the
licences are exceeded?

In the (main) office the SBS2003 is set up for individual
users (not computers), is it possible because I have 10 local
'USERS' in the main office that the terminal server is
issuing them the cals first even though they are on the local
network?

All help will be greatly appreciated. Thanks.
Paul

.

Relevant Pages

  • Re: Add a DC to remote site via VPN
    ... I believe the licensing is the same on ... one in California are PE 1900 servers. ... that for the SBS migration but because of the OEM licensing I can't do ... server and reinstall W2K3, join it into the domain and ship it to ...
    (microsoft.public.windows.server.sbs)
  • Re: Licensing, CALs and Server 2003
    ... As an example, a BDC can become a PDC, but an RODC will not be anything but ... have a change starting in Server (and SBS) 2008. ... Windows Server farm where the roles can be distributed. ... As for the licensing questions, best to speak with a licensing ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS on two systems
    ... The following is a direct copy and paste from the Microsoft Licensing Product Use Rights Documents found at: ... Running Instances of the Server Software. ... the second SBS to boot will see the first (in my ... The same SBS install, ...
    (microsoft.public.windows.server.sbs)
  • Re: Software cost of setting up a TS server?
    ... The first time I looked at a TS licensing document, ... Regarding whether or not all other Windows servers are covered by SBS CALs, ... Windows Server 2003 Client Access License ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing model
    ... SBS doesn't do concurrent licensing. ... Historically speaking, in the Windows server world ... CALs for each server on our network, and the number of CALs on a given ...
    (microsoft.public.windows.server.sbs)
Loading