"Access Evidence" will contribute to consumption for client licenses using the Microsoft CAL (Client Access Licenses) metric only. See the documentation in the FNMS online help, please. Server licenses for "Microsoft Core Infrastructure Server Suite" (CIS) will use a different metric, like "Microsoft Server/Management Core". Any "Access Evidence" collected for desktop computers will not contribute to the consumption for these license types.   ... View more

In FNMS, the application "Microsoft Core Infrastructure Server Suite" (CIS) is modelled as a suite consisting of ten applications.     With the standard setting, at least three of the ten applications need to be detected on the same device for the suite to be reported. This means that in addition to the OS 'Windows Server 2016 Datacenter' and the SCCM client - "System Center Configuration Manager", now renamed to "Microsoft Endpoint Configuration Manager", only a single additional application like 'System Center Endpoint Protection 2012" is required. So you can potentially rectify this issue by: setting the 'Required' property for an additional application in the suite and/or Increasing the number of installations for suite recognition from three to a higher number ... View more

Hi Johan, Based on the RedHat documentation, the RH00270 SKU indeed is for purchasing extended support. In a purchase order (PO) in FNMS, you would set the purchase type to "Software maintenance" and apply this purchase oder to an existing license, please. Make sure that all entitlements on your license are covered by maintenance, as discussed in another post here in this forum. ... View more

Hi Kevin, If your purchase order is for "Annual SW Subscription & Support Renewal" - like the PO IBM_4300583982 example that you provided in your first screen shot - the "Purchase type" should be set to "Software maintenance" instead of "Software", please. This maintenance PO needs to be applied to an existing (perpetual) license. Maintenance settings for all entitlements on any given license should be consistent. Maintenance information is provided by the purchase orders linked to the license. In case maintenance settings on the linked purchase orders are not consistent - like in the second screen shot for the IBM ODM PVU license that you provided - FNMS will show the alert on the license that "All license entitlements must be covered by current maintenance" that is visible on your screen shot. Please check this KB Article on this specific alert, too. In the fourth screenshot on the purchase orders (POs) linked to your license, you can see that this license has: 100+100+250 = 450 entitlements where maintenance expired 3/31/2020 150 entitlements where maintenance expired on 12/31/2019 As you suspected already, the "best practice" recommendation is to: Split your existing license into two licenses having 450 and 150 entitlements respectively. In the FNMS Web UI, in the "License Compliance > Licenses > All Licenses" view, there is a "Move maintenance" button that triggers a wizard for splitting your license and moving maintenance from one license to another one (as documented in the FNMS online help). After splitting your single license, you can apply new purchase orders for maintenance to the resulting individual licenses. Applying a maintenance PO will generally extend the maintenance period for fixed time period (like for one year), starting on the date when the old maintenance expires. Once again, make sure that all entitlements on your license are covered by maintenance ending at the same date after applying the maintenance POs. As an example, the PO shown in your first screen shot has a purchase quantity of 100 only. In case the total number of entitlements on your maintenance POs is lower than the number of entitlements on one perpetual license, the recommendation would be to do another split of the license. ... View more

Hi Johan, Looks like you are correct. Feel free to submit this to the Flexera content team (via support) so they can update the SKU libary data. ... View more

Citation from the "Software License Optimization Guide v6.0.pdf" that is available for download in the "Learning Center" (page #34): Tutorials for understanding the Application Recognition process and how to manage unrecognized applications are discussed in the “Application Recognition in FlexNet Manager” content available in the Community Learning Center. We also recommend reviewing the chapter on “Evidence” available from our online help. Understanding all aspects of Application Evidence and how to manage that is covered in detail in our Online Help. ... View more

Hi Johan, If you Google for SKU 65297888BA03A12, you find that this Adobe SKU is for: 1 Jahr Subscription Renewal for Adobe Creative Cloud for Enterprise All Apps VIP License Download Win/Mac, Multilingual (50-99 Licenses) So strictly speaking, 50 would be the minimum package size. As a purchase order with this SKU can be used for up to 99 users, I would recommend using a package size of 99 instead. ... View more

This would only work if you are using a different installation process, like you are not using the identical installer and/or serial number for the activation for both "network" and "stand alone" installations. You will need some piece of evidence that can be collected by the Flexera agent that you can use to differentiate between the different installation types. ... View more

Installed generally means that evidence for the application has been detected on the device. Used means that usage data have been collected. If you see "Yes" in this column, usage data need to be collected in the underlying Inventory source. Usage data are provided by a Flexera Agent that is installed locally on the device, by SCCM, or by the Microsoft 365 adapter - but not for Microsoft Dynamics 365. Are you sure that the license for Microsoft Dynamics 365 that you are looking at has been created by the Microsoft 365 adapter? What application(s) is this license linked to? ... View more

I believe there might be a little confusion of terminology. Consumption (as shown on the consumption tab on a license) means that a license with a "User" or "Named User" metric can be assigned to individuals. This means that the users that the license has been assigned to will be consuming the license. The information required for assigning users to a license is provided by the FNMS Microsoft 365 adapter. Usage in the context of FNMS means that the application has been used, for example by a user accessing a server based application like Microsoft Dynamics 365. The KB article that "Captain Kirk" pointed us to indicates that information about "Usage" cannot be provided by the FNMS Microsoft 365 adapter. For server applications that require client software that is installed locally on computers, usage data for the client software can be provided if a Flexera agent is installed locally on the device. Hope this helps? ... View more

What do you mean by "Named License"? In case you selected "Named User" in the "License type" drop down, you must assign users to this license manually. FNMS will only calculate consumption for this license type if users are assigned to the license users are assigned to inventory devices where the software has been detected Typically, a business adapter (MGSBI) will be used for assigning users to this license type. ... View more

What license type (metric) did you configure on your license? ... View more

Could you provide the following screenshots, please: The License (Applications tab) The Application (Devices Tab) ... View more

Hi, If you are OK with creating one license per site, you can split a single purchase order (PO) and use it for multiple licenses. After selecting your single PO from the "Procurement > Purchase Orders > Unprocessed Purchases" view, you can trigger the license creation and set the "Quantity to process" value to 1 (one) select 'a new license (create)' from choices listed after the "Apply to" label The rest of the purchase order processing - setting maintenance, selecting the application(s), selecting the license type - is "business as usual". Unfortunately, you will have to repeat this process twenty times. A license of type "Site" is always compliant. As documented in the FNMS Online Help, you can set up a scoping rule for limiting the consumption to devices in a certain location (site). Using a business adapter for allocating devices to your site licenses might be a good idea. ... View more