VPP Licensing Reservations (v14+)

The History

Prior to version 14 of FileWave, license reservations for VPP applications could be problematic when purchasing additional licenses.  If you look below, we purchased 25 licenses of this app initially, and the fileset (payload) that was then auto-created had a reservation for exactly 25 licenses.

P0bXAXSeKRvYsiKo-embedded-image-yn4gqx6n.png

The inefficiency of this model would show itself whenever we purchased more licenses for this app.  For instance, assume that we purchased 10 additional licenses...the fileset shown above would not change from the original 25, so we could effectively run out of licenses, even though we had 10 more available.  This necessitated a manual change to the original fileset, which was not efficient.

The Change

Starting with v14 reservation of licenses for VPP Filesets (payloads) has made optional in order to offer more convenience when purchasing additional licenses.  You can think of the licenses now more as a dynamic quota than as a restriction.  Here is how it works:

YhXxOL5oLrM5VvQj-embedded-image-2hjzk3jy.pngoAzdFIcviJF3qe0V-embedded-image-eoxditak.png

Examples

If you purchased 100 licenses for a new app (Firefox):

Some more complex examples, building on the above:


Revision #2
Created 2023-07-24 13:26:40 UTC by Josh Levitsky
Updated 2024-09-09 09:25:39 UTC by Josh Levitsky