License Allocation prevention

Adam_Dzyacky

Being able to track and report on license usage per user/device is fantastic within AM. But I'm curious if anyone has been presented with the following scenario yet...

Scenario: We have several per user licenses, but would like to "hold" the remaining one for select departments within the organization. So if someone in Department  A goes to the Request Offering they see this perceived Seats Remaining count.


Honestly the best thing I can come up with is extend the License class to support this new logic. Then have SCO/SMA control the values. It seems really messy/not a truly shareable solution since deployments have all sorts of varying numbers of departments within their organization. Would be great to hear some other possible ways out of this!

joivan_hedrick

Are you looking to store different licenses for each organization? For example, SnagIt 12 might have licenses for your IT department, Sales department, and Accounting departments, and you need to be able to differentiate available software between all three departments? This scenario is possible through setting up one software asset per department and using the Authorization tab. 

Though, if you are looking to differentiate between sub-departments, for example, IT (web dev), IT (helpdesk), and IT (server team), then negative. You cannot have a held license in this regard, and you'd have to extend the class, or use some type of Authorization.

Adam_Dzyacky

Makes sense. But what about where the License has no corresponding Software Asset and the License is in and of itself the Asset which you care about? This would be applicable for something like Office 365 licensing, unless there is an alternative way to accomplish something like this?

joivan_hedrick

Ah, negative on that one too. You can assign users, Windows computer objects, or both to a license object. But you can't reserve a seat without some type of extension/automation/trickery. 

Though if you're looking for some tacky trickery, you could create some dummy Windows Computer objects and assign them to your license objects, with the end result of an accurate Seats Remaining count, and licenses being held for a real Windows Computer/user. Not ideal, but effective and requires no customization.