Hello Listers,
I found Carey's superb example of 'restricting' the Floating Licenses via pools. I have multiple applications supports our customer base. App ABC, App MNO & App XYZ Does it make sense to create a set of groups just for controlling the tokens? Example: Team_ABC = 5, Team_XYZ = 5 and Team_MNO = 25. Now my ABC people paid for 5 licenses, same for the XYZ's The MNO group would be for the support teams that have to work on ABC, MNO & XYZ requests. Team_MNO's licenses are legacy. Am I correct in thinking that this will keep the 9 ABC people locked down to 5 Floats, the 12 XYZ people to 5 floats and the 50+ MNO people will be able to work with their 25 floats? My reasoning for the "token groups" is due to the MNO people needing to help out the ABC and XYZ's without affecting the number of tokens available for each team. Thanks, --- John J. Reiser Senior Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

