cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Lots of SQL Server installations detected without edition

Jump to solution

After latest ARL update a couple of SQL Server applications appeared on installed applications list. In most cases they are detected on the same devices with "normal" SQL Server applications, where edition is specified. However, significant amount of installations is detected on end user devices where SQL Server is not expected.  These applications are classified as commercial, but since edition is not present, it's impossible to assign them to proper licenses. Is this an expected behaviour or a an error in ARL?

1 Solution
PrasadAmin
Level 7 Flexeran
Level 7 Flexeran

Hello,

We should map evidence that doesn't carry information about the edition to SQL Server (Unknown component) and so did the same as part of this week's release and ignored the SQL Server without edition.

As part of SQL Server Integration Services, we removed suspicious evidence which is causing wrong recognition of the same product. It will be rectified in this week's release.

Thanks,
Team Content

View solution in original post

9 Replies

What is your data source on these installations?   It has been my experience that specific editions are reported by only the FlexNet Agent installed on these systems.   Sources like MECM will show you the product, but not edition, therefore can't be tied to specific licensing.

0 Kudos

It's a mix of data from FNMS Agent and SCCM. Applications are discovered via installer evidences. I can see that they were in ARL since Februray, but all installations were detected on 2022-10-16, so I assume it has something to do with the latest ARL update.

0 Kudos

I am seeing the same situation. Also a mix of inventory between SCCM and agent. 

 

I also am noticing a big change in SQL Server Integration Services 2019 with a massive increase in devices now reporting this product as installed. Since SSIS is a licensable SQL service, I have it as a primary app on my SQL licenses which have in turn had their consumption spike.

 

Any update from Flexera on this? 

0 Kudos
shuduguru
Level 7 Flexeran
Level 7 Flexeran

Hello,

We are looking into this and update you here with our findings. 

Thank you, 

Team Content

PrasadAmin
Level 7 Flexeran
Level 7 Flexeran

Hello,

We should map evidence that doesn't carry information about the edition to SQL Server (Unknown component) and so did the same as part of this week's release and ignored the SQL Server without edition.

As part of SQL Server Integration Services, we removed suspicious evidence which is causing wrong recognition of the same product. It will be rectified in this week's release.

Thanks,
Team Content

I still see many installs of SQL Server Unspecified Edition. Is this being addressed by a future ARL update?

0 Kudos

Unfortunately this behavior is still applicable after installing ARL v2711. In fact, this is now also occurring for version 2017 (besides 2016 and 2019).  I also noticed that the app shows als "local "source but I cannot change the app so this is also not correct and on top op of this we see overlapping evidence.

Can you take a look again in order to mitigate this.

In my opinion, this should not be marked as 'Solved'. This portion still remains open:

"We should map evidence that doesn't carry information about the edition to SQL Server (Unknown component) and so did the same as part of this week's release and ignored the SQL Server without edition."

Dear Rudi,

we have also seen that behaviour even daily updating libraries.

I have solved this by removing all "Local" and "Flexera extended" Evidences from "All Evicences".

Of course only related to Name like "sql" and Pubslisher = "Microsoft".

A reconciliation is also required after that.

Disclaimer: if you have customised Evidences / Applications for sql set up, they will be deleted as well and you will be running kind of like Out Of The Box loosing any customisation you might have done for SQL recognition.