No fair David, you have the classified cheat sheet. :) And have the benefit of being the meetings where these changes are decided.
To Nathan's point it is impossible to match up the licensing console to your support renewal to validate you are not breaching contract. I think I have mentioned before that our Account Managers (many of them) have not be helpful (I haven't met our new one so we can try again). As products have been rename/merged/dropped over the years we have products that are not listed on our support renewal (which has also completely changed after going blue) and we have little evidence that we are entitled to use them at the configured capacity. All we have are some emails between us and BMC, and the original POs where we purchased the license/capacity (usually under a different product name or licensing scheme). The 7.1 license key change has been very nice from a flexibility standpoint but it is a real guessing game now when you go to add licenses to a new server that will replace your old pre ITSM 7 server. One benefit before from a license management perspective was that you needed to purge and reissue each license to put it on a new server; if you were not entitled you couldn't reissue it to the new server. Jason On Thu, Jul 7, 2011 at 10:01 AM, Easter, David <david_eas...@bmc.com> wrote: > ** > > **Ø **extra credit to the first person who can correctly identify what > actual Remedy keys should be applied to the AR Server when purchasing > “Service Mgt Specialist” license**** > > ** ** > > Well, since AR System 7.1.00, there are no longer license keys for users, > applications or modules – so it is a trick question and the answer is > “none”.**** > > ** ** > > However, if you meant “licenses”, then there are two business licenses > associated with the Service Management Specialist:**** > > ** ** > > **1. **AR System User**** > > **2. **SRM Analyst / Admin**** > > ** ** > > Since SRM uses the AR System user for its license checks (i.e. there is no > SRM application user license technically within the system), the Service > Management Specialist would enable the entering of an additional count in > the AR System User fixed/floating row while in the Add/Remove License > console. The number would be a one-to-one correlation of the number of SM > Specialist licenses purchased… so if you bought 5, you would enter (or add) > 5 to the count of the AR System User license row.**** > > ** ** > > -David J. Easter**** > > Manager of Product Management, Remedy Platform**** > > BMC Software, Inc.**** > > **** > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc.**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Nathan Aker > *Sent:* Thursday, July 07, 2011 09:51 AM > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: BMC Software Acquires Aeroprise**** > > ** ** > > ** **** > > You gotta remember the BMC Naming Standards checklist that the new > acquisition rename must adhere to:**** > > ** ** > > **1.) **Does it contain the words “Service”,”Management”, or > “Automation” (if no, try again)**** > > **2.) **Can it be represented in a 3-5 letter acronym that is earily > similar to everything else we sell?**** > > **3.) **Has it been renamed in the last 6 months (if no, rename > immediately. This applies to existing product portfolio as well)**** > > **4.) **Is it completely unrelated to the legacy name that is well > known in the marketplace (if no, try for something more ambiguous)**** > > **5.) **Have we shoe-horned the inherent licensing key structure into > the BMC Blue pricing model making it impossible for any rational person to > figure out how to apply the correct license keys per their purchased license > names? (extra credit to the first person who can correctly identify what > actual Remedy keys should be applied to the AR Server when purchasing > “Service Mgt Specialist” license)**** > > **6.) **Will the new name look good on the BSM Marketing diagram?**** > > **7.) **Can we put “cloud” or “on demand” in the name to capitalize on > industry marketing trends and buzz?**** > > **8.) **Will the resulting acronym look like something my 3 year old > randomly pounded out on the keyboard?**** > > ** ** > > *Nate***** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Meyer, Jennifer L > *Sent:* Thursday, July 07, 2011 9:57 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: BMC Software Acquires Aeroprise**** > > ** ** > > ** **** > > Thanks. From now on, I’m going to just chuck the B’s, T’s, and S’s, > convert Roman Numerals to Arabic, and refer to all of their products by > number.**** > > ** ** > > Jennifer Meyer**** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Chowdhury, Tauf > *Sent:* Thursday, July 07, 2011 10:54 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: BMC Software Acquires Aeroprise**** > > ** ** > > ** **** > > Well, for the ones that you can actually use, which is MCMIM, it’s 2901 :) > **** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Meyer, Jennifer L > *Sent:* Thursday, July 07, 2011 10:50 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: BMC Software Acquires Aeroprise**** > > ** ** > > ** **** > > Does anyone know offhand what BMCMITSM is in Roman Numerals?**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Chowdhury, Tauf > *Sent:* Thursday, July 07, 2011 10:21 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: BMC Software Acquires Aeroprise**** > > ** ** > > ** **** > > What? What’s wrong with BMCMITSM? It rolls right off the tongue.**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Meyer, Jennifer L > *Sent:* Thursday, July 07, 2011 10:13 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: BMC Software Acquires Aeroprise**** > > ** ** > > ** **** > > How does BMC manage to slaughter the names of the products it acquires so > thoroughly? “Aeroprise” was good. It was pronounceable. It was > memorable. “BMC Mobility for IT Service Management” is forgettable garble. > **** > > ** ** > > Jennifer Meyer**** > > Remedy Technical Support Specialist**** > > State of North Carolina**** > > Office of Information Technology Services **** > > Service Delivery Division ITSM & ITAM Services**** > > Office: 919-754-6543**** > > ITS Service Desk: 919-754-6000**** > > jennifer.me...@nc.gov**** > > http://its.state.nc.us**** > > ** ** > > E-mail correspondence to and from this address may be subject to the North > Carolina Public Records Law and may be disclosed to third parties only by an > authorized State Official.**** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller > *Sent:* Thursday, July 07, 2011 9:57 AM > *To:* arslist@ARSLIST.ORG > *Subject:* BMC Software Acquires Aeroprise**** > > ** ** > > ** **** > > http://www.bmc.com/home/2011/bmc-acquires-aeroprise.html**** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > ------------------------------ > > This e-mail and its attachments may contain Forest Laboratories, Inc. > proprietary information that is privileged, confidential or subject to > copyright belonging to Forest Laboratories, Inc. This e-mail is intended > solely for the use of the individual or entity to which it is addressed. If > you are not the intended recipient of this e-mail, or the employee or agent > responsible for delivering this e-mail to the intended recipient, you are > hereby notified that any dissemination, distribution, copying or action > taken in relation to the contents of and attachments to this e-mail is > strictly prohibited and may be unlawful. If you have received this e-mail in > error, please notify the sender immediately and permanently delete the > original and any copy of this e-mail and any printout.**** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > ------------------------------ > > This e-mail and its attachments may contain Forest Laboratories, Inc. > proprietary information that is privileged, confidential or subject to > copyright belonging to Forest Laboratories, Inc. This e-mail is intended > solely for the use of the individual or entity to which it is addressed. If > you are not the intended recipient of this e-mail, or the employee or agent > responsible for delivering this e-mail to the intended recipient, you are > hereby notified that any dissemination, distribution, copying or action > taken in relation to the contents of and attachments to this e-mail is > strictly prohibited and may be unlawful. If you have received this e-mail in > error, please notify the sender immediately and permanently delete the > original and any copy of this e-mail and any printout.**** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
