Inventory Gap Analysis custom reports (VMs from vCenter, Oracle issues, merged computers, ESX Ghots...)
- Owner: Nicolas Rousseau
- Solution Type: Custom SQL Reports
- Flexera Product & Version: FNMS on Premise
- Development Effort: 2 day
- Implementation Days: 0.1 Day
- Pre-Requisites: DB access with read write access
SOLUTIONS ARE PROVIDED ON AN "AS IS" BASIS. NEITHER FLEXERA NOR ITS SUPPLIERS MAKE ANY WARRANTIES, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. LICENSEE MAY HAVE OTHER STATUTORY RIGHTS. HOWEVER, TO THE FULL EXTENT PERMITTED BY LAW, THE DURATION OF STATUTORILY REQUIRED WARRANTIES, IF ANY, WILL BE LIMITED TO THE SHORTER OF (I) THE STATUTORILY REQUIRED PERIOD OR (II) THIRTY (30) DAYS FROM LICENSEE’S ACCEPTANCE OF THE AGREEMENT.
Set of reports that provide relevant information to address the following inventory gaps analysis:
Virtual Machines collected from vCenter but not inventoried
The report catches inventoried and not inventoried VMs (reported by vCenter import) with information that will help closing the gaps (host entity etc.).
Merged Computers (leading to license consumption false positives)
The document gives more details, but it can happen the multiple "imported computers" coming from multiple sources or even from the same are merged by the import. If the computers inventory dates are the same (two different sources (SCCM and FNMS agent) for the same computer), there is no issue. If one of the merged records is aging, this can lead to false positives. It is always good to delete old records that are merged from the source database.
Note that a menu introduced with FNMS 2020R2 shows the matching criteria. The report focuses on the merged computers
Oracle Inventory Collection issues
Understanding when an Oracle inventory fails can be extremely time consuming (need to check the logs on discovered device.
The report will catch all issues and show the last error logs. It will prioritize the issues based on issue type of logs information.
Duplicate Computers (leading to orphan VMs (Ghost ESX))
Please refer to the Word document for detais... two ESX server with the same UUID will trigger an "isDuplicate" flag that will cause the deletion of the duplicate record and will make related VMs orphan. The reports shows such duplicate ESX servers.