Management of application licenses on a Windows 2003 TS

  • Thread starter Thread starter Hauke Fath
  • Start date Start date
H

Hauke Fath

Guest
All,

I am planning the setup of a Windows 2003 terminal server, to provide a
group of ~20 employees who work on Debian machines with easy access to
MS Office applications. Unfortunately, I had to realize that WTS 2003
does not even keep track of its own (per-user) licenses, let alone
enable me to set up a floating-license scheme for applications on the
server.

All that came up when I googled for application license management on
WTS was the www.appsense.com product. Does the group have any
experiences with that? Are there any alternative products on the market?

Thanks,
hauke

--
Now without signature.
 
Re: Management of application licenses on a Windows 2003 TS

Not exactly an answer to your question, but:
Office is *always* licensed per device (not concurrent!), so you
will need to know the *total* number of connecting devices.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

dont-spam-usenet@googlemail.com (Hauke Fath) wrote on 21 feb 2008:

> All,
>
> I am planning the setup of a Windows 2003 terminal server, to
> provide a group of ~20 employees who work on Debian machines
> with easy access to MS Office applications. Unfortunately, I had
> to realize that WTS 2003 does not even keep track of its own
> (per-user) licenses, let alone enable me to set up a
> floating-license scheme for applications on the server.
>
> All that came up when I googled for application license
> management on WTS was the www.appsense.com product. Does the
> group have any experiences with that? Are there any alternative
> products on the market?
>
> Thanks,
> hauke
 
Re: Management of application licenses on a Windows 2003 TS

Vera Noest [MVP] <Vera.Noest@remove-this.hem.utfors.se> wrote:

> Office is *always* licensed per device (not concurrent!), so you
> will need to know the *total* number of connecting devices.

Uh huh. "Connecting device" is what, exactly? Any *nix machine on the
internet with an rdesktop(1) installation? I bet Microsoft would like
that...

hauke

--
Now without signature.
 
Re: Management of application licenses on a Windows 2003 TS

Hauke Fath <dont-spam-usenet@googlemail.com> wrote:

> Vera Noest [MVP] <Vera.Noest@remove-this.hem.utfors.se> wrote:
>
> > Office is *always* licensed per device (not concurrent!), so you
> > will need to know the *total* number of connecting devices.
>
> Uh huh. "Connecting device" is what, exactly? Any *nix machine on the
> internet with an rdesktop(1) installation? I bet Microsoft would like
> that...

The document at
<http://www.appsense.com/files/documentation/Windows_Terminal_Server_Sof
tware_Licensing_Control_UK.pdf> has an overview of MS application
licensing on a TS - so all the "Application Manager" can do in the case
of MS Office is restrict device access. Ah well.

Again - any experiences in the group with that or similar tools?

hauke

--
Now without signature.
 
Re: Management of application licenses on a Windows 2003 TS

dont-spam-usenet@googlemail.com (Hauke Fath) wrote on 21 feb 2008
in microsoft.public.windows.terminal_services:

> Vera Noest [MVP] <Vera.Noest@remove-this.hem.utfors.se> wrote:
>
>> Office is *always* licensed per device (not concurrent!), so
>> you will need to know the *total* number of connecting devices.
>
> Uh huh. "Connecting device" is what, exactly? Any *nix machine
> on the internet with an rdesktop(1) installation? I bet
> Microsoft would like that...

A device is any piece of hardware that is used to work with Office,
be it installed locally or accessed in any other way.

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