Hi Rita, As long as all applications reported on an Inventory device are covered by the Adobe Creative Cloud (CC) Suite Enterprise license (with version and edition matching), you will not need another CC Suite license for the older applications. FNMS should consume entitlements of the Adobe Creative Cloud (CC) Suite Enterprise license (which has downgrade rights configured) for the Inventories having Creative Cloud for Enterprise 2017 applications, too. ... View more

Hi, If you process a purchase order that is based on SKU 65291079BA23A12 (ARL/PURL/SKU = 2607/486/486) accepting all defaults and review the applications linked to the license created, in the second list box on the 'Applications' tab where the 'Applications covered by upgrade/downgrade rights' are listed, you should see: Creative Cloud for Enterprise (Version 2017) Acrobat 2017 Pro plus 15 additional applications that belong to 'CC (2017)', 'CC (2017.1)' or DC (2017) Continuous/Classic Is this what you have been looking for? ... View more

According to the 'Microsoft Practice Guide', yes. However, there are some other recommendations for configuring a CISS license in this document that you may want to look at. ... View more

In the 'Microsoft Practice Guide' PDF document available for download for registered users, there is a chapter 'Core Infrastructure Server Suite (CISS)' (page #45). In this chapter, you find the following recommendations for recognizing CISS: CISS is by default recognized as an Application Suite in FlexNet Manager where Windows Server and System Center component applications are found on the same device – this is discouraged in most cases and can be overridden by changing the number of applications necessary for recognition in the Application Suite evidence page of the Evidence Tab of the Application. By adjusting the suite recognition criteria to requiring 10 installations to trigger recognition you can ensure that only the components of CISS are recognised (Done in the Application Suite tab seen on the Evidence tab of the Application). Instead the CISS license should have the component products of CISS assigned (Windows Server, System Center SCCM (Recognized separately in the ARL). The 'Microsoft Practice Guide' v5.0 can be found in the 'Practice Guide' section in the 'Learning Center' here in the community. ... View more

Did you change the status of the Inventory from 'Active' to 'Ignored' already? FNMS will not automatically disregard any Inventory just because it has not been updated for months. The Inventory record will remain active indefinitely. You have to manually change the status of the Inventory, or delete it from the underlying Inventory data source. You can automate this process using a SQL or PowerShell script that runs on a regular basis. There are some sample scripts available here on the Community. ... View more

This behavior is by design. Based on the most recent evidence data found in the Inventory source, FNMS dynamically links applications to devices during the compliance import process. Evidence data may change daily, as software is being installed or uninstalled on devices. For the application recognition process, the date when the evidence has been collected for a device does not matter. As a best practice, you should check the out-of-date inventory on a regular basis and change its state from 'Active' to 'Ignored' when the device has been retired. ... View more

FNMS will not change any license settings automatically. If you create a license using a purchase oder where the SKU is initially not recognized, or if the software vendor updates the use rights that are linked to the SKU on a purchase that you used when creating a license, FNMS will create a 'recommendation' for updating the license configuration. This use case is what the view "License Compliance > Compliance > Recommended License Changes" has been designed for. In this view, you can select any recommendation in the list and either accept or ignore it. Only if you accept a recommendation in this view, the license configuration will be updated. ... View more

Hi Rajesh, IBM PVU consumption data calculated by ILMT will be imported during the Inventory import into FNMS for viewing purposes. FNMS has read-only access to ILMT data only. Running the report in FNMS will not have any impact on existing IBM data/reports. The report will display both the PVU consumption data calculated by ILMT as well as the PVU consumption data calculated by FNMS for comparison. ... View more

Hi Rajesh, What is meant here is that you can use the following standard IBM PVU License Consumption report in FNMS for comparing results. This report can be found in the following folder in the "Reports" section of the FNMS Web UI: Reports > License Compliance > Compliance > License Positions from FlexNet Manager and ILMT Using this report, you can compare: IBM PVU consumption results calculated by FNMS with IBM PVU consumption results are imported together with Hardware and Software Inventory data from the IBM PVU data source. ... View more

Hi Ravi, Generally a license will be required for any device that is used for making a software product available to users. If you install a desktop application - like Microsoft Project and Microsoft Office Professional - on a server, these installations will need a software license, too. Software vendors are very clear on this in their license agreements. Installing desktop applications on production servers is not considered to be a "best practice" approach. There is a number of reasons: You will have to provide licenses for your servers and This may have a negative impact on the stability of your servers. ... View more

Hi, The IBM PVU license consumption calculation relies on peak usage data by definition. PVU consumption related raw data can be collected either by ILMT or by using the Flexera agent. In any case, you must historical consumption data available for your servers to allow for  calculation of peak usage data. If you manually assign a license with PVU metric to additional computers, you have to: Make sure that conditions for PVU usage calculation are met. The agents running on these computers have to learn (via download of the policy) that these computers are linked to a license with PVU metric now. Make sure that FNMS is configured correctly for PVU licensing. This will allow Flexera agents and VMware scanning to run every 30 minutes as required by IBM Only after agents running on all servers linked to a license with PVU metric have downloaded the PVU settings, they will start collecting IBM PVU related consumption data and will be doing the frequent hardware scanning required by IBM. You have to be patient and wait for the agents running on the two computers that have been linked to the PVU license recently to pick up the new information. Give them some time to collect and upload PVU related consumption data. Once these agents have collected PVU data for a reasonable amount of time you will see peak consumption data. Once peak consumption data are available for your servers, PVU consumption will be calculated for servers that have been manually allocated to a PVU metric license, too. ... View more