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"
