[THIN] Re: MS Office

  • From: "Andrew Wood" <andrew.wood@xxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Thu, 6 Jan 2005 00:01:46 -0000

Yea Hames, you're right - by the terms of the EULA its 120 - which basically
is excellent revenue generation

As I've said my advice has always been use permissions to control access -
but it would be useful if the suggestions from partners and product managers
could be turned into cold hard recommendations :P

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jeremy Saunders
Sent: 05 January 2005 23:49
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MS Office





We discussed this with the Microsoft Office Product Manager a couple of
years ago, and he said that the Security Group and NTFS permissions would
suffice. If you are locking it down in this maner, then it's not considered
a concurrency model. But you are right Andrew, this is not covered off under
any of the scenario's on that URL you provided.

Scenario 3 is interesting. "A customer has 40 Windows-based workstations and
30 employees who will use Office on all 40 workstations. The customer will
need to acquire 40 Office licenses. This is consistent with the per-computer
licensing policy." We have a customer who has 120 thin clients with 50
Office licenses on their TS. Many users roam. This scenario suggests that
they should be puchasing 120 Office licenses. Hmmm.

I don't like the way they say "Windows-based workstations". In my mind that
doesn't clearly cover off all devices.




                                                                           
             "Andrew Wood"                                                 
             <andrew.wood@gilw                                             
             ood-cs.co.uk>                                              To 
             Sent by:                  <thin@xxxxxxxxxxxxx>                
             thin-bounce@freel                                          cc 
             ists.org                                                      
                                                                   Subject 
                                       [THIN] Re: MS Office                
             06/01/2005 07:03                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
                   thin                                                    
                                                                           
                                                                           




Fwiw if you read the license agreement as stated by MS (
http://www.microsoft.com/windows2000/server/howtobuy/pricing/licensoffice.a
sp)

It states:

'you must acquire a license for all devices that will be running a Microsoft
software application product (for example, Office) from the terminal server'

It goes on to say :-

'The Office EULA requires you to acquire and dedicate a license for each
device, or from which Office will be accessed. "Acquire and dedicate" means
you will need to obtain a license for each device that is to run Office on a
recurring basis.

This provision does not prevent you from reallocating licenses when
appropriate. You are allowed to reallocate a license from a computer when
that computer is no longer expected to run Office. However, you may not
continually reallocate licenses to only those devices running the software
at any given time'

It quite clearly states 'Dedicate a license for Office for every computer on
which you plan to use Office' and 'Do not use Office running on Terminal
Server to count and license only concurrent uses of Office. Every device
must be licensed.
'

I would agree with the sentiment of restriction by group and that's what
I've advocated in the past however this has been a serious concern for many
customers. The long and short of it is that Microsoft explicitly state that
every *device* that can run office should be licensed for office. That's the
rules as stated by MS - there examples show that if you have users
connecting from remote devices they should have a license.

That said, it'd be interesting to test this and I'd also be interested to
hear what others thoughts are


-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Robert K Coffman Jr - Info From Data Corporation
Sent: 05 January 2005 22:02
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MS Office

I ran into the same issue with Project, and ended up restricting it by
group.

- Bob Coffman

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Bill Beckett
Sent: Wednesday, January 05, 2005 4:45 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: MS Office


Clear as mud typically how MS licensing goes. However, I base our licensing
under the same premise as you...just curious how others interpreted it.

-----Original Message-----
From: Greg Reese [mailto:gareese@xxxxxxxxx]
Sent: Wednesday January 05, 2005 4:34 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MS Office


I've been told it is ok as long as you can ensure that you can control who
accesses and who does not.  that was from a MS person at iForum who seemed a
little unprepared to answer the question.

My reseller sold me licenses this way and said they checked with MS first.
I have it in writing so that is my recourse if I get in trouble for it since
the reseller is a "Platinum Partner".

Clear as mud right?

Greg


On Wed, 5 Jan 2005 16:13:42 -0500, Bill Beckett
<Bill.beckett@xxxxxxxxxxxxxxxxx> wrote:
>
>
> Question about access licensing on a terminal server as I've heard 
> different versions and would like the lists input. If you install MS 
> Access on a terminal server, I was under the impression that a license 
> was needed for anyone who connected to that terminal server because 
> they could potentially run Access. First question...true?
>
> Second question....could one not restrict availability by either not 
> publishing the app OR if their users were savvy enough to get to 
> explorer and run the executable, restrict access to to the executable 
> file itself?
>
********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names Register your .com domain
name for as low as $7.85 One of the lowest prices on the web! Part of The
Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm ThinWiki community - Awesome SBC Search
Capabilities! http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use
the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names Register your .com domain
name for as low as $7.85 One of the lowest prices on the web! Part of The
Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Awesome SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use
the below link:
http://thin.net/citrixlist.cfm


********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names Register your .com domain
name for as low as $7.85 One of the lowest prices on the web! Part of The
Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Awesome SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use
the below link:
http://thin.net/citrixlist.cfm

********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names Register your .com domain
name for as low as $7.85 One of the lowest prices on the web! Part of The
Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Awesome SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use
the below link:
http://thin.net/citrixlist.cfm


********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names Register your .com domain
name for as low as $7.85 One of the lowest prices on the web! Part of The
Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Awesome SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use
the below link:
http://thin.net/citrixlist.cfm

********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names
Register your .com domain name for as low as $7.85
One of the lowest prices on the web! Part of The Kenzig Group.
http://www.seamlessplanet.com
********************************************************** 
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Awesome SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm

Other related posts: