Microsoft SQL server editions can't be determined correctly from SCCM
Summary
Microsoft SQL server editions can't be determined correctly if the compliance source is SCCM.
Synopsis
Microsoft SQL server editions (Enterprise, professional, standard) can't be determined correctly if the compliance source is SCCM.
Discussion
This is because SQL server version information is stored as WMI evidence on the servers, SCCM does not collect WMI evidence so this information will not be imported into FNMS/ITAM
Workaround
Customers who primarily use Microsoft SCCM as their inventory and compliance data source can use one of the following methods to collect accurate SQL Server edition information:
-
Deploy the FlexNet Inventory Agent
- Install the FlexNet Inventory Agent on the SQL Server hosts.
- The agent will periodically collect and report detailed inventory information, including SQL Server edition data, to FNMS/ITAM.
-
Schedule Remote Inventory Collection
- Configure and run a scheduled FlexNet Inventory Scanner task against the SQL Server hosts.
- Schedule regular inventory collection and import processes to ensure SQL Server edition information remains up to date.
-
Use Agentless (Zero-Footprint) Inventory Collection
- Leverage the Zero-Footprint (Agentless) Inventory capability through the FlexNet Inventory Beacon.
- This method enables inventory collection without installing software agents directly on the target SQL Servers.
Note: SCCM inventory alone may not provide all the SQL Server edition details required for accurate license compliance calculations. Flexera recommends using one of the inventory collection methods above to ensure complete and reliable SQL Server edition discovery.
