The history has been (for products that require a server side license) that a separate license is required per server; examples include flashboards, arserver, and migrator.
The server side application licenses are new to the mix, starting with the 7.0 applications. I would imagine that BMC expects users to purchase a separate application license per server, right wrong or indifferent; which it seems you are confirming. The deployable apps 'require' the presence of an app license (in addition to user licenses), and this enforcement is (probably) BMC's method of enforcing what they always considered the proper usage/licensing of their applications. Development licenses are usually priced at a reduced rate from the regular list price, though if memory serves me correctly, the pricing on annual support/maintenance is against the list price. Even the products that Remedy acquired (ITMasters) that had a different licensing scheme (e.g., per desktop), were moved to the licensing model that Remedy applies to all it's products, which is per server. Unfortunately, this makes both the price entry point and growth price extremely expensive. Consider you want to use the following applications: - Asset - Change - Incident - Problem - Service Request Management - SLM It get's really expensive really fast when (1) you have multiple environments (dev, test, production) and (2) you have a growing user base, esp, when it is difficult to predict the growth of said user base. I also have reservations about the floating license model for development environments, simply due to the fact that purchasing them for a dev/test environment is cost prohibitive when the fixed can be used in all environments; we have been burned by a number of defects in the last couple of releases related to floating licenses (single users holding multiple floating licenses, no method in mid-tier to soundly release floating licenses, etc.). Axton Grams On 3/30/07, Ivan Runions <[EMAIL PROTECTED]> wrote:
I don't quite understand the phrase "stay with the user". The level of licenses required for Joe User to run Incident Management 7.0 is 1) An Application Fixed or Float license for the person 2) An ARS Fixed or Float license for the person 3) An application license for Incident Management 4) An ARS Server license for the server. My question is re: #3 above... is that a "site" license or a "server" license. -ivan- ARSList wrote: >I am curious doe the floating application licenses stay with the user? > >Nick >Havin' Fun in Sacramento > > >[EMAIL PROTECTED] > >-----Original Message----- >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Ivan Runions >Sent: Friday, March 30, 2007 12:39 PM >To: [email protected] >Subject: Application licensing question > >My question is on site licenses vs server licenses. > >The licensing tool basically enforces this, because User Fixed licenses >come up as being valid for a site, whereas User Float licenses come up >as being valid for a server. > >My question is on the Application license (not the Application >Fixed/Float license). The license tool accepts the Incident & Problem >Application license as being valid for a site, however my Sales Rep is >saying we need to purchase additional development copies for our Test >and QA servers. > >Can I get opinions, or better yet, facts? on this? > >-ivan- > > > -- Ivan Runions Information Technologies University of Calgary Calgary Alberta Canada (403) 220-4437 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
