About wwwyin

wwwyin · ‎Aug 24, 2021

@kclausen Understand what you're referring to but not what I'm describing. I'm questioning why the Calculated Consumption value is not being brought over to the Consumed column which affects my Peak consumption. For example, Calculated Consumption = 480 PVU, then Consumed = 0 @bfaller Good point, however I just checked again and can see the Hosts are known with Active Status. I'll throw another spanner in the works - when a manual recon is performed (by publisher), the Consumed PVU points corrects itself but after an overnight full recon, it appears to revert back to 0 Consumed. Keeping in mind this only impacts 4 LPARs under this license with inventory from BigFix. The other VMs (SCCM) seem to be working just fine, so maybe a BigFix issue....

wwwyin · ‎Aug 23, 2021

Hi All, I have an issue with some VMs returning a Calculated consumption on an IBM PVU license but the PVU Count does not become a Consumed value. I understand the conditions that need to be met, based on the OnlineHelp "Relationships Between Consumption Fields": The system-calculated consumption figure ( Calculated consumption ) becomes the final result ( Consumed ) for this device when all of the following conditions occur: The value of Overridden consumption for the inventory device is zero (or, for IBM PVU licenses, the Calculated consumption value was imported from ILMT, as shown in the Calculated by column, since in this case Overridden consumption has no effect and acts as a zero) For a cores-based license (such as IBM PVU), the inventory source has returned a valid Cores count for the inventory device (or a vCPU count for instances hosted in a known cloud service provider ). I can see both conditions being met, there is no overridden value and there are core counts for each VM so I'm a bit at a lost here. One commonality between these VMs is that they're missing a serial number and they're all LPARs although I'm unsure if this would prevent FNMS from reflecting the final Consumed result. In addition, the Calculated consumption is actually correct. It's calculating VM Core count x PVU per Core (e.g., 4 x 120 = 480 PVU) Running FNMS 2020 R2, PVU calculated by FlexNet (Internal) Any ideas appreciated Cheers

wwwyin · ‎Jul 20, 2021

Some further reading of the SQL Server 2019 Licensing guide, I was able to extract the following excerpt: "Software licenses and use rights are version-specific and as such, licenses for different software versions cannot be combined when licensing a single operating system environment. As a benefit of having access to the latest version of SQL Server software, SA customers licensed under the core licensing model (for example) can easily combine current version core licenses with future version core licenses, without the need to track or otherwise reassign covered licenses based on software version alone." I take this to mean, if I am an SA customer I can simply use the 2016 Per Core Licensing rules and apply that to all my different versions?

wwwyin · ‎Jul 20, 2021

Hi All, Having read through the Microsoft Practice guide, I understand there are some challenges when setting up SQL Server Per Core Licensing in FNMS. In a mixed environment with SQL Server 2008, 2012, 2014, 2016, 2019 would it be best practice to create separate licenses to cater for the differing license models? How does Microsoft view this if we have active SA on all of our entitlements? SQL Server 2008 = Per Processor SQL Server 2012-2014 = Core Factor Table (Points Rule set = SQL Server) SQL Server 2016 and up = Per Core (Points Rule set = SQL Server 2016) Setting up separate licenses would present challenges with consumption configuration and also splitting and allocating purchase entitlements to each license. Any thoughts appreciated. Thanks

Online Status	Offline
Date Last Visited	‎Sep 17, 2021 05:51 AM

Re: IBM PVU Calculated Consumption does not become Consume

IBM PVU Calculated Consumption does not become Consume

Re: SQL Server License configuration Per Core + Core Factor Table

SQL Server License configuration Per Core + Core Factor Table

Re: IBM PVU Calculated Consumption does not become Consume

IBM PVU Calculated Consumption does not become Consume

Re: SQL Server License configuration Per Core + Core Factor Table

SQL Server License configuration Per Core + Core Factor Table