‎Jun 03, 2019 12:48 PM
Hi, thanks for raising this.
This is a known issue in 2017 R2 and is resolved in later versions of FNMS where the consumption of the license is per core and not per 2-pack, so in your case would result in a the correct consumption of 32.
In the meantime the best approach is to adjust the unit quantity of the purchase/s from 2 to 1 so that the license consumption and the purchase are both represented in terms of 2-packs. If you have a SKU for your purchase you will, I think, need to override this (you can add something to the end so that it is not recognized) otherwise it will not accept the change in unit quantity.
If your purchase is already assigned to the License you will also need to update the number assigned to the license, which you can do in the Licenses tab of the purchase after you change the quantity. Alternatively you can remove and re-link the purchase to the license.
Regards,
Stewart
‎Jun 04, 2019 09:19 AM
Hi, thanks for raising this.
This is a known issue in 2017 R2 and is resolved in later versions of FNMS where the consumption of the license is per core and not per 2-pack, so in your case would result in a the correct consumption of 32.
In the meantime the best approach is to adjust the unit quantity of the purchase/s from 2 to 1 so that the license consumption and the purchase are both represented in terms of 2-packs. If you have a SKU for your purchase you will, I think, need to override this (you can add something to the end so that it is not recognized) otherwise it will not accept the change in unit quantity.
If your purchase is already assigned to the License you will also need to update the number assigned to the license, which you can do in the Licenses tab of the purchase after you change the quantity. Alternatively you can remove and re-link the purchase to the license.
Regards,
Stewart
‎Jun 04, 2019 09:19 AM