Parallels Desktop for Chrome OS Enterprise and Education Edition licensing model

6 users found this article helpful

In Parallels Desktop for Chrome OS Enterprise and Education Edition the licensing is managed by Google’s licensing server, that Parallels Cloud interacts with. This also results in a different logic governing Parallels Desktop For Chrome OS Enterprise and Education Edition licenses. 

Google App licensing model

Google has its own component designed to manage the product licenses. It assigns and manages the licenses on a “per user” basis. 

Google App uses a paradigm of a “pool” of licenses. Licenses can be added into a pool by packs (tranches). To be credited with the licenses (to get a tranche of licenses), the organization must redeem a code for a corresponding number of licenses. 

Licenses have a validity period of 12 months starting a date/time when they were credited to an organization. Licenses that have been added into an organization’s pool in different tranches expire at different times. Nevertheless, licenses purchased together (credited in the same tranche) expire simultaneously. 

The license pool itself does not have an expiration date. 

Example: 100 licenses (tranche A) were originally credited to an organization on the date Da; 25 additional licenses (tranche B) have been credited on the date Db. Licenses from tranche A expire on Da+1year, while the licenses from tranche B expire on Db+1year. 

The number of licenses available to an organization at any given time includes licenses from all packs which remain valid (non-expired) by the moment of observation. 

If you need more licenses, you must redeem a code valid for the required amount. 

During the lifecycle of an organization’s product license pool, some packs of licenses expire, while others remain valid. There is not a single moment in time when you would have to renew all licenses in the pool at once. To renew the licenses you must redeem a code(s) suitable for a number of licenses big enough to compensate for the licenses which have already expired or are about to expire soon. 

 

As illustrated in the diagram above, the licenses added in tranche A expire on the date Da+1year. To make up the balance the Customer has to add the new pack of licenses (tranche C) before/on/after the date Da+1year. The pack of licenses from tranche C will expire on the date Dc+1year. 

Google App takes care of automatic re-allocation of the licenses from the pool to the users which were granted the licenses before. 

Resolution

Was this article helpful?

Tell us how we can improve it.