That answer below is not in line with how I understand licensing to work.
In the ITSM apps the license really exists to modify existing records. Assuming you are in Submitter Locked mode - which I think the vast majority of people are - a user logging in and having workflow create new records in some kind of log should not take a license token. Also, if you can change that user to read license, Incident Viewer and the log in with no problems are they still writing to log files? If so then obviously the floating user didn't need to take a token. And if not then the floating user doesn't need to write to logs either. I would take this up with BMC. It seems to be in conflict with everything I've ever heard about how/when floating tokens are actually taken. William Rentfrow wrentf...@stratacominc.com Office: 715-204-3061 or 701-232-5697x25 Cell: 715-498-5056 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Lippincott, Levi (OMA-GIS) Sent: Friday, October 30, 2015 1:05 PM To: arslist@ARSLIST.ORG Subject: Re: Serious flaw in BMC Remedy Licensing Ryan, We ran into this issue too and when we spoke to BMC about this they said this was operating as designed because when someone first logs into the system and views the data it writes to some logs and therefore needs a write license. Our user base that was experiencing this issue though did not live in the system all day so we just had to train them when they closed the system to actually hit the Logout link so they freed that license up immediately for others. Levi Lippincott / Remedy Administrator +1 402 561 7014 office +1 402 321 5421 mobile levi.lippinc...@interpublic.com Interpublic Group 6825 Pine Street, Omaha, NE 68106 "Talent is a Gift; But Character is a Choice." -Matt Grotewold- -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of laurent matheo Sent: Friday, October 30, 2015 12:55 PM To: arslist@ARSLIST.ORG Subject: Re: Serious flaw in BMC Remedy Licensing Personaly I don't see why you could not post this on bmc community but ok :) I am no license expert so well, did you contact bmc support or someone from BMC about it? In which version are you? Mobilis in Mobile. > Le 30 oct. 2015 à 18:50, Ryan Nicosia <ryan.nicosia....@socom.mil> a écrit : > > Didn't think BMC wanted me to post this on their communities but we have > found what I would consider a serious flaw in the way that BMC counts a > license against a user. > > Here is the scenario: > > User A has been giving a FLOATING license for Incident. User A has his IT > home page configured as overview console to display all INC's, CR's, and > TASKS assigned to his group. > > User A's support group has NO incidents assigned to it. > > User A logs into Remedy and immediately shows up in license review as > consuming a "write" license (NOT A READ LICENSE) for Incident. > > User A refreshes his overview console every half hour. Since the "write" > license doesn't switch back over to "read" for 15 minutes, he is virtually > consuming a "write" license for Incident all day long. > > And this is the really stupid part. He has never even opened an Incident. > > > What we have found through our use of the RRR License tool is that some of > our top "Incident License" users are people who have NEVER even opened an > Incident. We've taken the list of people who (according to BMC) have > consumed an Incident "write" license and searched for their login ID in the > HPD audit log and work log forms. To our amazement, over 1/4 of them aren't > in there. > > So, this begs the question. Has anybody else figured this out? If so, does > it bother you as much as it bothers us that a user who has been given an > Incident User (FLOAT) license and NEVER uses it, can still cost your > organization money in license fees? > > I know we can adjust our licenses and give out Incident viewer but it seems > like an administrative nightmare to figure out who should get what when the > real answer would be for the tool to do a better job of counting who is > really using a license. > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" This message contains information which may be confidential and privileged. Unless you are the intended recipient (or authorized to receive this message for the intended recipient), you may not use, copy, disseminate or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail, and delete the message. Thank you very much. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4830 / Virus Database: 4365/10845 - Release Date: 10/18/15 Internal Virus Database is out of date. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
