Re: Licencing TS via SBS Server = free CALs???

You would think so, but no, they can connect and receive no message like
"your licence has expired". All 12 users are currently using Terminal
Services with expired licences on the TS Server, but (seemingly) being
licenced via the SBS Server.

I'm as confused as you!

"Vera Noest [MVP]" wrote:

> OK, let's continue the thread here.
>
> So your clients are *not* issued "full" licenses, they are issued
> temporary licenses, as can be expected, since you didn't install
> any purchased TS CALs.
>
> Have you tried to connect with one of the clients who have an
> expired temporary license? I expect that those 12 clients cannot
> connect anymore.
>
> _________________________________________________________
> 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?RnVuQm9iYnk=?=" <FunBobby@xxxxxxxxxxxxxxxxxxxxxxxxx>
> wrote on 27 aug 2005 in
> microsoft.public.windows.terminal_services:
>
> > Hi TP
> >
> > The Terminal Server is set to Per Device.
> >
> > Terminal Server licencing shows two servers with the following
> > details:
> >
> > Windows SBS 2003 Server [Activated]: Existing Windows 2000
> > Server - Terminal Services CAL Token (Per Device). Built-in,
> > Unlimited, Unlimited, 0
> >
> > Windows 2003 Server (Terminal Server) [Deactivated]: Existing
> > Windows 2000 Server - Terminal Services CAL Token (Per Device).
> > No entries for any column
> >
> > Temporary Licences for Windows Server 2003 - Terminal Server Per
> > Device CAL Token. Total of 23 tokens issued, 12 of which have
> > expired by 7 days or more, Quantity of 1 for each Token.
> >
> >
> > I'm as confused as anyone! What I want to ensure is that there
> > isn't some other kind of gotcha that will occur at some point in
> > the future, or that whilst this works it is in contravention of
> > MS licencing.
> >
> > Thanks again
> >
> >
> > "TP" wrote:
> >
> >> What licensing mode is your Terminal Server set to?
> >>
> >> To check the licensing mode:
> >>
> >> 1. Logon to your Windows 2003 TS.
> >> 2. Open up Terminal Services Configuration
> >> 3. Click on Server Settings on the left
> >> 4. The licensing mode is listed on the right
> >>
> >> What exactly is listed in TS Licensing on your SBS server,
> >> as well as your TS?
> >>
> >> - Open up TS Licensing on both servers, and tell me what
> >> entries are there, as well as the value for each column
> >>
> >> Product, Type, Total, Available, Issued
> >>
> >> And then drill-down into each entry to get details
> >>
> >> Issued To, Issued On, Expires On, Quantity
> >>
> >> Thanks.
> >>
> >> -TP
> >>
> >> FunBobby wrote:
> >> > Thanks TP and Vera for the responses.
> >> >
> >> > However, I'm still a little confused, and here's why ....
> >> >
> >> > When the Terminal Server (Win2003) was set up, I installed TS
> >> > Licence Manager and it started handing out temporary
> >> > licences. When our supplier
> >> > mentioned about SBS licencing I then set up Licence Manager
> >> > on the SBS 2003
> >> > server.
> >> >
> >> > On Tuesday all the temporary licences expired. But all the
> >> > systems are
> >> > still logging in using the Licence Manager installed on the
> >> > SBS 2003 Server.
> >> > The systems are assigned full (rather than temporary)
> >> > licences, but I have
> >> > bought no TS CALs, simply authorised the SBS Server.
> >> >
> >> > Here's the only quote I could find on the process:
> >> >
> >> > "For a small organization, it is recommended that one server
> >> > run Windows
> >> > Small Business Server and a second server run Terminal
> >> > Services. To facilitate this and to simplify the licensing
> >> > requirements for this scenario,
> >> > Microsoft allows the client-access license (CAL) for Windows
> >> > Small Business
> >> > Server to satisfy the CAL requirement for Windows Server on
> >> > the second server."
> >> >
> >> > (http://h71028.www7.hp.com/ActiveAnswers/downloads/WP_Terminal
> >> > _Server_ProLiant_Servers.pdf page 10)
> >> >
> >> > Any ideas why this works and if it is legal?
> >> >
> >> > Thanks again.
>
.

Relevant Pages

  • Re: Terminal server licence problem
    ... I have posted in the SBS forum for the time being to ... The only thing I know is that SBS OS licensing is different from ... MCSE, CCEA, Microsoft MVP - Terminal Server ... there does seem to be a licencing problem. ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal server licence problem
    ... Since you do not have a TS Licensing problem, and *probably* a SBS ... MCSE, CCEA, Microsoft MVP - Terminal Server ... there does seem to be a licencing problem. ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal server licence problem
    ... I have 10 'user' CALs ... local machines but the server does not recognise. ... there does seem to be a licencing problem. ... you should see in the TS Licensing Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal server licence problem
    ... You write that you installed the TS CALs as Per user TS CAL. ... you should see in the TS Licensing Server ... Can you check the EventLog on the server and post the EventID, ... the licencing server and server to the 10 pcs in this ...
    (microsoft.public.windows.terminal_services)
  • Re: expiring user account passwords
    ... when it expires ... > FTP doesn't support that. ... >> access to there ftp data or front page data on the server without any ...
    (microsoft.public.inetserver.iis.security)