From time to time, an organization may find they have a need to merge two or more License pools into one.
Merging License Pools is a very easy and straightforward process. First, as shown in the image below, you want to delete the License Pool that needs to be merged into another.
If you make a mistake and delete the wrong pool, don't worry. You can easily recreate any License pool you may have unintentionally deleted.
In the example below, the License pool named “NL” will be merged with the License pool named “Netherlands”.
Next, locate the License pool that is the target of the merge and click on the Pool's name to enter edit mode.
Continuing with our example, you'll want to click on “Netherlands” as that is the License pool into which the pool named “NL” will be merged.
Once you are in edit mode for the target License pool, you can then perform the merge.
To accomplish this, you will tick the License pool that you previously “deleted” and then click “Submit”.
When merging License pools, please keep the following in mind:
- Merged License pools consist of the parent License pool as well as any member pools. In the example above, the parent License pool is “Netherlands” and the member pool is “NL”.
- License pools, whether they have been merged or not, continue to rely on whatever “Filter criteria” were originally chosen to configure your License pools.
- For reporting and license management purposes, the parent License pool is the governing pool. Member pools are invisible. Therefore, all data associated with the member pools will be reflected as part of the parent pool.
- For customers who rely on License pools in place of V-Tenants (e.g., EnableLpVTenants = Yes), merging License pools may impact the scope of access for any given operator.