This all from memory, and I have never actually used license pooling, so forgive me if someone corrects me and I end up being wrong. My understanding about floating license pooling is as such. When it is determined that you need a floating write token it first looks to see if there are any available in pools that you are a member of, if none are found it then looks in the un-pooled arena. So in your situation creating the restricted group would in fact ensure that they use those licenses first. If you however leave the remaining licenses 'un pooled' then the system will venture outside of the pool for any available. What you will likely need to do is create two groups, Restricted and TheRest. Assign your limited amount to the Restricted group and give your restricted list that group. Allocate the remaining to your 'TheRest' group and make every other user of the system (but none of the restricted list) access to that group. This would effectively limit the restricted group to their license count, and allow the rest of the users to utilize the remaining floating licenses
_____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Friday, November 09, 2007 12:09 PM To: arslist@ARSLIST.ORG Subject: License Pooling ** We are looking for a way to limit users who belong to a certain group to a number of Floating Write licenses. There will be only one group in our system that has this restriction. All other groups can use as many licenses as are available. Users in this special (restricted) group will also belong to other non restricted groups. So, I think what needs to be done is to create a new group, assign it a certain number of floating tokens and add that group to certain users. When the number of users logged that are part of that group exceeds the number of tokens allotted the special group then they will not be able to write. The documentation on this feature is not very explicit on it works so I am looking for validation. Thank you and have a great weekend! Frank __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
