You may have seen here and there interesting KB articles, using the powerful customizations possibilities of FNMS to provide extensions to the out of the box value for reporting or automations... The issue is that the articles are spread and unless you know what you look for you may miss some interesting information.
The purpose of this post, that will be extended over the time, is to provide you with a "SAM Best Practices Hub", a single pane of glass to understand and use the published solutions and the coming features: SAM Optimization Hub in 2022 Q3, SAM Operations Transparency Hub in Q4 2022, a SAM Data Transparency Hub in 2023... where these best practices will be progressively incorporated.
The solutions are addressing both ends of the "SAM Maslow Pyramid" (from bottom to top) and are anticipating where Flexera goes with SAM:
An "Other Best Practices" section will provide at the end of the article useful pointers to solutions that don't fall under the umbrella of these three "hubs".
The first section of the article gives pointers to the recordings and supporting presentations of all delivered SAM Best Practices Webinars, that are delivered monthly and provide a deep dive on a topic in one hour.
Every month, one topic is covered in a one hour recorded session. The sessions are announced in the Community Hub you can subscribe to get the notifications. The sessions' recording and PowerPoint and additional documents are shared in the Hub too. Here are the available resources
If you are interested in joining these monthly calls and other Flexera presentations, keep an eye on the Community Hub and register to the events you are interested in.
You can also vote for the topics that represent most interest for you on your SAM journey to influence the order of presentation in these calls.
Let's start with the foundation: there are key questions that any SAM Manager must have answers to before even thinking about compliance or optimization... This structure anticipates the SAM Operations Hub that will provide KPIs and answers to these questions. Mockup below, please click on image to zoom.
The SAM Operations Hub provides a single pane of glass to monitoring 13 SAM performance KPIs (snapshot and one year trend), and provides all explanations and underlying reports that explain the details and allow to identify quality issues (gaps, false positives...).
An Enterprise Filter allows to slice the KPIs in the locations, corporate units or cost centers dimensions.
The structure of the Hub will be the following
More details and related published solutions
This should be the first check of the day. The system tasks screen (Out of the box) (Only show last run = Yes, Status = failed) will give the right data and the logs.
Beacons are key components of the ITAM architecture that transfer all inventory and discovery files run inventory tasks, schedule business imports, upload logs... A beacon could stop reporting due to the Beacon Engine Service being stopped, the upload scheduled task disabled, authentication issues (agents can't connect to the Beacon inventory web service and upload NDI files...).
The Beacons screen (Out of the box) gives the list of beacons with status, pending upload files data. Each beacon detail record gives detailed upload status.
The VMs Gaps From vCenters report (Released in 2021R1.4) catches the VMs reported by vCenter imports but not inventoried with an agent. This Community solution allows to create the report on premise.
The "out of date inventory" screen (Out of the box)adresses the need (out of the box). A pointer to the screen will be in the SAM Operations hub with a KPI (proportion of the full active inventory)
The Short Practice Guide on Managing SAM Operations in FNMS / Flexera One ITAM provides a word document that includes this script p13. Note that a "cleanup" feature has been implemented from 2021R1.4 to delete from Inventory Manager any aging inventory based on a threshold you can define (30, 90 days...)
The Merged Computers from Imported Computers report (Released in 2022R2.2) provides the two reports that that allow to understand computers (potentially coming from multiple sources) before they are merged. False positives and sticky applications can be caused by disabled sources (to be deleted absolutely) or duplicates from te same source (deleting computers from InventoryManager may be necessary). On older versions of FNMS (before 2020R1), ESX with the same serial number can alternatively be deleted and cause orphan virtual machines.
I have seen customers who had 3 times a different connection to the same SCCM database from three beacon. One was active, 2 were disabled but not deleted: imagine the billion of useless files evidences and the "sticky" applications reported by dormant sources. Note that FNMS 2020R2+ versions keep the latest of the merged record's evidence for recognition when they come from the same source. However, 3 SCCM connections are considered as three sources... A pointer to the inventory connections will allow to focus on these possible issues. The Data inputs / Inventory (Out of the box) screen will show you inventory sources, eventually disabled or that failed for a period... here are the candidates to fix... or delete!
Host to VM link is critical for many server applications licensing (Oracle, Windows & SQL Server, IBM PVU and VPC...). The vCenter Inventory Troubleshooting report (Released in 2022 R2.3) gives you the list of servers that reported from the vCenter discovery, with the dates (VMWare Inventory, VMWare discovery), the error logs and high level analysis. Community Solution here.
A VM with no host is the sign either of a vCenter inventory issue (the VM has been instantiated (with an inventory agent) but not yet reported by a vCenter) or an issue in status synchronization (The VM is decommissioned, no longer reported by vCenter (so... unlinked from its last host), but still active and inventoried).
As expensive server licenses require the link between VMs and hosts to compute license consumption, orphan VMs are a serious issue. For instance, on Windows Server, the VMs are unlicensed, which keeps them invisible in the license consumption.
The all Inventory screen (Out of the Box) filtered on "device type = Virtual Machine", Host is empty and Hosted In = "On premise" will show the issue. More than 10% of Orphan VMs is an issue.
The Oracle Inventory Troubleshooting report (Released in 2022R2.4) catches all issues and shows the last error logs. It prioritizes the issues based on issue type of logs information. This Community Solution provides a custom SQL report if you are on a previous on premise version.
A decommissioned instance still configured in an OEM will result into the instance reporting for options / management packs consumption, but not for Oracle Database Enterprise edition. A Possible Options False Positives From OEM report (Released in 2022 R2.3) catches these cases.
The Unrecognized Installer Evidence Analysis report (Released in 2022 R2.3) analyzes the installer unrecognized evidences (recognition in 90% of times triggered by installer evidences) and finds matching recognized raw evidences. It prioritizes the evidences to manage and suggests evidences (with the right wild cards). Community Solution here.
The unlicensed Installations screen (Out of the box) gives you a view on installations applications "under the radar". For Applications that have 0 licenses, no license monitors these applications, which opens a liability risk. Then, you could have licenses covering applications, but active devices have installations of these applications that are not "monitored" by licenses, in the case of restricted licenses or Named User licenses. Managed vendors should have no "unlicensed installations".
The License Consumption and unlicensed Product Risks report (Released in 2022R2) mixes License Consumption data with unlicensed products counts to provide a single pain of glass for your compliance and license gaps.
There are multiple approaches for managing purchases. You can import purchases and defer publishers that are out of scope (no link will be performed to licenses), or only import purchases for vendors in scope. In any case, your "Unprocessed purchases" screen (Out of the box) should have no record... otherwise, it means some licenses are missing entitlements and are pessimistic on your compliance position... or licenses have not been created, which opens a liability risk.
Having licenses linked to active maintenance purchases not covering all versions of a product may be the sign that upgrade / downgrade right have not been correctly applied. A more complex to identify use case is when a multi product license does not have consistent upgrade and downgrade rights across all products. That's a classical issue that a "Licenses issues analysis" report (Released in 2022 R2.3) addresses.
The Contract Renewals screen (Out of the box) gives this list. The Contracts with Expiring Terms or Conditions goes one steps deeps and check across terms and conditions that have their own dates.
A report showing all purchases with an expiry date within 30, 60 or 90 days and their linked licenses would address the visibility and renewal process activity visibility.
The SAM Publisher Hub (and related screen extensions) aim to provide an application Publisher centric view of your SAM. It will be adapted in the way organizations organize their SAM Practice per Publisher. It will allow also to solve a long lasting challenge that Purchase, Contracts and licenses publishers are not normalized (contrarily to the Application Publisher) and are technically vendors (Microsoft France, Adobe US etc.) that can be created by users or be imported with purchases for instance.
The Vendor screen will be extended
The screen (vendor detail) will include the license and Publisher tabs.
There will be a calculated (application) Publisher (based on historical data (Direct or indirect links between purchases, contracts and licenses)). User will be able to pick up manually a lined Application Publihser that will override the calculated publisher.
A New Publisher screen will be created
The Publisher detail will contain the full picture, with tabs that will allow the processes you can do from the generic screens
The SAM Publisher Hub will provide visualization and trends for the main topics... and a link to the Application Publisher Detail
More details and related published solutions
Bits and bytes that explain the the license liability
The Application transparency report (Released in 2021R1.4) and published the the community as a KB article provides the full details that links the dots between the raw evidences and the recognized (and eventually licensed) application installation.
The Raw Evidence on computer custom report published in the community based on a ComputerName|%EvidenceName% will return all installer, file and WMI evidence matching the evidence name input, eventually across all devices (for instance "|visio.exe" ).
The Oracle Feature to Options transparency report provides the reason why Options have been reported as used, across Oracle instances. It is using the Oracle transparency information that you can find on each instance when clicking on the "Yes" or "No" hyperlink of "used" column of the options tab.
What are my Oracle instances details?
The Oracle inventory details incl. exact version report provide the Instances details, including the exact version that can be found in the instance attributes.
The "Installed Applications Usage details" report provides user per user, all usage information
this is complex to understand across licenses what licenses are scoped to which entities, with eventual overlaps. The "Flat List Of License Restrictions" report provides this transparency.
The Details on SAP systems (Released in 2022R2.4) Inventory report gives the overview, system per system, of the number of users, engine and transaction data age, number of transaction records etc. Community Solution here.
The raw engine measurement data report give details on all reported engine measurements.
The SAP active users counts over one year report shows the evolution on the number of users, month per month, on each SAP system.
The Most Used Roles By License Type And System report allows to understand from real role usage per system the mapping between roles and license types.
Citrix is an area where transparency reports are critical, as users, based of access rights to VDIs, have remote access applications created on their computers. The Citrix Virtual Desktops Installer Evidence report for instance gives details on the end computer, user, VDI causing the installer evidence, AD group the user is related to... all the information that allow to link the dots on this tricky remote applications use case. Other reports give Citrix transparency that will be articulated in the SAM Transparency Hub.
A License Consumption including Charge Back REST API has been Published in 2021R1.4 for Cloud customers only that provides license per license the full details, including the license consumption recharged points and value, computed often at host level (for Windows Server, SQL Server, IBM PVU or VPC licenses, or even Cluster level (Oracle Processor)) and "rolled down" to the installed VMs level by the API. This way, shared resources may "carry" the consumption but installed resources (often owned by the liable entities) are charged for the license usage.
More reports will be included in Flexera One ITAM / in the community supporting this license consumption / charge back transparency.
Once foundations are solid (you can trust your inventory, licenses have been correctly created, the full installed estate is under control) you can start taking full advantage of compliance and compute optimizations: you have reached the top of the Pyramid and can really enjoy the full SAM value delivered by Flexera! Mockup below. Please click on the image to zoom.
The structure of the Hub will be the following
More details and related published solutions
Most of optimization reports have already been released and the SAM Optimization Hub will articulate the value of the reports around two pillars
The complex optimization calculations (Windows Server, SQL Server, Red Hat) are released first as reports (with possibility to allocate according to the calculated optimizations) and will later be included in the optimization logic of the license consumption algorithm.
Windows server has multiple editions (Standard and Data Center), can be licensed with System Center (Core Infrastructure Server (CIS)), has complex rules (90 day mobility rules for Windows Server Standard)... in the end, everybody tends to license ESX servers with Windows Server Data Center edition, or counts the number of VMs in clusters ("worst case") to decide when to use Windows Server or CIS Data Center or the Standard editions.
The Windows server Optimization report (released in 2021R1.4) computes the optimal license needs based on the 90 day peak number of Windows Server VMs, host per host. It also identifies when CIS is required. The report gives the total true up as well as the savings, host per host but also globally of the optimal license (when it is Standard edition) versus the classical and easy "Data Center" edition choice. The report can be implemented from this community solution.
SQL Server is a different story. SQL Server Enterprise can cover either Enterprise or Standard editions installations. A quick and expensive approach is to cover all VMs in a ESX with SQL Server Enterprise edition as soon as one VM is installed with the Enterprise edition.
The SQL server Optimization report (released in 2021R1.3) computes the optimal license needs evaluating host per host the "everything in Enterprise editions versus each VM licensed separately with the installed edition". he report gives the total true up as well as the savings, host per host but also globally of the optimal license (when it is Standard edition) versus the classical and easy "Enterprise" edition choice. The report can be implemented on premise from this community solution.
RHEL, like Windows Server has a cheaper edition (Server edition) that requires more licenses if you have more VMs on an host and a more expensive (Data Center Node edition) that covers an unlimited number of VM. No mobility rule for using the RHEL Server node edition on ESX server but you have the constraint that a cluster must be consistently licensed in a unique edition.
The Red Hat Enterprise Linux Optimization Report (released with 2021R1.2) compares for each cluster the cost of using one or the other option, computes the optimal cost and provides the saving when the optimal license for a host is Server Node edition. The report can be implemented on premise from this community solution.
Oracle, with the terrible "soft partitioning rule", can cost you millions if you make the mistake of having a VM with an expensive option in a large cluster.
The Oracle Optimization on Clusters report (Released in 2021R1) computes cluster per cluster the "total cost" and "total waste", comparing, for database and option per option the installed cores and licensed cores. The report can be implemented on premise from this community solution.
The Oracle License Consumption Details And Optimizations (Released in 2021R1) provides all details on Oracle Processor license consumption, it highlights all optimizations possibilities, host per host and provides a charge back consumption and value at installed devices (particularly on VMs) level. The report can be implemented on premise from this community solution.
The ideal Oracle VMWare architecture is when all VMs with consistent installed and used options are regrouped in specialized clusters. The Optimum Virtualized Target Architecture for Oracle Options report (Released in 2021R1.1) provides the full details of this target architecture along with the consumption saving. The report can be implemented on premise from this community solution.
Two other reports on Oracle (Released in 2021R1.1) provide simulations on the consumption and financial impact for the database and options Licenses on the various soft partitioning levels (cluster, vCenter, all vCenters...), for summary and details .
(Released in 2022 R1.4) will provide a user per user analysis of the installed and used applications, in the context of active subscriptions for all named users licenses.
It will also provide recommendations for downgrades and financial analysis on savings for Adobe and M365. The Adobe Optimization Report can be found in the Adobe Subscriptions Optimization Report & Adobe Portal Users importer KB article.
The Named User License consumption and Optimization report KB article provides the code of the released version for on premise customers.
The Cloud Migration License Impact Simulation Engine (Planned for Q1 2023) will allow to create simulations for migration of VMs to Cloud Service Providers.
You can choose the candidate VMs, determine the Cloud Service Providers you intend to migrate the VMs to and save the simulation. The Simulation engine will compute for all licenses in scope the consumption before and after the migration. You will get a view on the complex to anticipate and major licensing cost of moving to the Cloud.
Other useful Community pointers
In the SAP Licensing— translate 50 expensive shades of grey into cheaper black and white! blog ost, you will understand the subtleties of SAP licensing ambiguities and optimization.
The When good intentions, good will and sincerity lead to licensing nightmares and financial waste blog post gives a view on how licensing rules have tried to adapt to technological sophistications and how they have themselves become unmanageable for human beings.
Flexera One ITAM / FlexNet Manager has an extremely detailed Online Help, that gives you from the context of any page the full explanations on all fields and processes from the UI. Please think about clicking on the "?" when one the out of the box reports. Each report is documented in great details, for instance: the Windows Server Optimization report. Please also check the Features by Release documentation that contains the full history.
The Online documentation, in its root folder (IT Asset Management Help folder on top) contains a number of deep dive documentations.
Some hands-on best practices documentation have been initially written by Flexera Services: The Practice Guides on Software License Optimization, Microsoft, Oracle, IBM, Adobe and SAP can be found in the Flexera Learning Center, the Using FlexNet Business Adapters documentation provides practical view on the use of the Business Adapter Studio.
More generally, the Flexera Learning Center contains excellent resources and recordings if you want to learn more about Flexera ITAM and Software Asset Management.
The License exemption by file path (Released in 2021R1.4) automates exemptions for Java installations recognized thanks to file evidences on exempted paths. The Automating the Management of Embedded Java instances solution allows to anticipate the feature with a less sophisticated implementation that recognizes these instances separately as "Java embedded" and excludes them from
The SAM Operations Guide, that is a complement (and shorter version) to the Practice guides, provides the big picture and detailed guidance on starting a SAM project and managing SAM operations.
A detailed documentation on Managing unrecognized applications is also provided in this article.
The Allocation Automation Example for FNMS Cloud gives a sophisticated example of automation for locations calculation for servers based on they IP subnet, domain or server name. The solution reads the data in Flexera One ITAM using the GetCustomViewResult SOAP API (all details are provided on how to activate this API) and using a local SQL instance for running advanced SQL scripts.
Note that a similar REST API was release in June 2022
This KB article gives you the pointer to the newly released License Consumption (and charge back) REST API (Cloud only), some explanation and an Example of a PowerShell script that queries the API, license per license, "flattens" the JSON output and goes through paginated pages.
This KB article gives you the pointer to the newly released reportsExecute REST API (Cloud only), some explanation on this API that retrieves the output of any report created from the web client and an Example of a PowerShell script that queries the API, license per license, "flattens" the JSON output and goes through paginated pages.
Any object (Inventory device, installed application, license result, contract, purchase) with any possible link can now be queries through a REST API call!
When you need to create multiple similar licenses (for instance in the case of restricted licenses), it can be long to use the license creation wizard again and again. This License Duplication Wizard allows to create the wished number of copies after selecting licenses.
A KB article gives the details for collecting data from Nutanix or Red Hat RHEV cluster and integrating the data into FNMS / Flexera One ITAM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.