I can't even count the number of times I've run into this issue. Here's a strategy that helped at one of my clients.
Pass 1: Analyzed the heck out of our user profiles and assigned fixed vs. floating smartly...giving hour heavy users a fixed. Pass 2: Started grouping our floaters by organizational divisions and by feature teams...then setup license pools for each grouping of division and feature teams. What ended up happening is that when people were irresponsible with their licenses, they ended up burning other people in their division/team... At first, we reported out license usage by pool, so *they* could go yell at someone on their team to logoff. Before long, the teams began self-managing. It just seemed that people were more conscious when they knew they were victimizing their own folks. Tim --- On Tue, 8/4/09, Arner, Todd <[email protected]> wrote: From: Arner, Todd <[email protected]> Subject: Encouraging Float License Users to Log Off When Inactive To: [email protected] Date: Tuesday, August 4, 2009, 11:25 AM ** Encouraging Float License Users to Log Off When Inactive Hello Everyone, We are currently experiencing an issue with our float license users not logging out when they are inactive in Remedy. Needless to say this is holding a float license open for an hour that other users could have been using it. My question is, have you found an effective way to encourage your users to log off when inactive? We have sent emails which helps for about a day but then they forget again. Thanks in advance for any suggestions you may have. Todd Arner Great Lakes _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
