Hi, Anthony: This may be based on your Float License Timeout setting. If it is set for x number of hours, does the Last Access Time for those accounts reflect access time for more than the timeout setting? If so, it is working as designed.
FYI: There is a quirky bug in the 6.3 Admin Tool, that is fixed in 6.3 patch 17. The Last Access Time does not display accurate data. This bug would inaccurately display Last Access Times from hours or even days ago. A lot of those accounts listed should have dropped off the list. I installed Admin Tool 6.3 patch 17 for another issue, and it indeed fixed the bug mentioned immediately above. Hope this helps, Michelle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Caressimo Sent: Tuesday, July 25, 2006 8:55 AM To: [email protected] Subject: License issues - read issued - floating unavailable Hi all: I am just curious; i been tracking our license usage and noticing that remedy still issues a read(floating) even though floating licenses were available. Why would this be happening? I would expect to see 0 unless floating licenses were at a max. There were times when only 6 out of 25 floats were in use and users were still issued reads(floating). We are running ar server 6.3 p16, SQL, mid tier 6.3 ws2k3 sp1. Using AR user floating and help desk floating licenses. thanks AC ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
