Allow simultaneous multiple versions

Morgado asked a question.

October 24, 2019 at 7:00 AM

Hello Snowers,

In our environment we have several applications which are listed twice in the "installed applications".

One of the examples is Windows SQL Server.

This is happening because the machines may have two different agents installed inventorying data (Ivanti and BigFix). As BigFix uses pre-recognition, the SQL server in most cases shows with the Edition (e.g. Microsoft SQL Server 2016 Standard). And as the Ivanti recogniziton is "poor", the SQL may show without edition (e.g. Microsoft SQL Server 2016).

This situation causes that we have the same Application listed twice and of course with the double of license requirements.

We have tried to use the option "Allow simultaneous multiple versions" but doesn't appear to help. Both entries continue to have license requirements.

While this issue between connectors recognition is not sorted out, do you have any idea why this solution is not working? If there is no edition this couldnt be considered a standard one as there is a "standard" edition installed?

Thanks in advance for your inputs.

Gonçalo Morgado.

SamuelBaughan
7 years ago
Hey Gonçalo, To understand why this does not work, you can execute this query: SELECT Name, EditionIndex, VersionIndex FROM tblApplication where Name LIKE 'Microsoft SQL Server 2016%' Snow will apply the benefit of "Allow Multiple Versions" only if those versions also have the same edition index. This query above shows that the edition index for Microsoft SQL Server 2016 is 90 while the edition index for Microsoft SQL Server 2016 Standard is 110: Solution: If you have only the Standard edition, you can create your own application bundle that groups the "Standard" edition along with the generic one detected without edition. Then assign your licenses to the bundle.
Expand Post
- Morgado
  7 years ago
  Thanks Samuel. Humm. well.. it makes sense. Making the assumption that those without edition are standard... ..that's as simple as override the Ms. SQL Server 2016 Bundle and add to this bundle the same Index? Like this snip below. Thanks again ‌
  Expand Post
  - SamuelBaughan
    7 years ago
    Yes, that should do the same Let us know if that works for you!
    Expand Post
    Morgado
    7 years ago
    Thanks ‌. It worked! However we have two scenarios.. Let me explain: SQL Server 2016 + SQL Server 2016 Standard (this scenario can be "fixed" with the bundle shown above + multiple versions activated). SQL Server 2016 + SQL Server 2016 Enterprise. For this last case would be possible to "merge" both applications or use the bundle option to say if both Apps are installed just consider the SQL Server 2016 Enterprise? Any tip on what could be done here? I am giving the example of v2016 but this is happening for all versions. Thanks again.
    Expand Post
SamuelBaughan
7 years ago
If you have this happening as a more general issue, a good idea would be to find out why Snow does not detect the edition of SQL Server installed. In the case of SQL 2016 Standard, for example, the fact that Snow did not detect the edition for the bundle is caused by the fact that it did not find any of the following registry records: You can try to find why it was not found: The registry record is missing => is it cause by how you install the application? Could you manually add the record? A registry record is there but the Snow agent did not find it => Is the config file applying some kind of restriction on the scan? A registry record is there but it does not match any of the rules => ask Snow to adjust the rules
Expand Post
- Morgado
  7 years ago
  The problem is that Ivanti (called before LANDesk) inventory is very poor and doesnt retrieve the Edition.. It looks to add & remove programs, a few installation paths but still not enough to get the Edition. So we trust om BigFix for SQL version and edition, but when both agents are running in the same device cause trouble with duplicated records for Software installed.
  Expand Post
  - SamuelBaughan
    7 years ago
    Is it possible to use a pre-DUJ custom step to clean out those inaccurate Ivanti records? We have had in the past to do some cleanup in our Inventory because there was some wrong data brought back by earlier versions of the Snow Agent. In this case, if the connector does not bring back the edition, you might be able to get some help from Snow Support to set up this cleanup task.
    Expand Post
    Morgado
    7 years ago
    We have high hopes that this "connector" situation be solved somehow in future. If we clean the data it will eventually come back again in next scan. So probably you are suggesting a custom procedure to clean this daily. Our experience with custom procedures is not the best.. all time a new version is coming up we face issues to adapt, performance, etc. Therefore we would rather use an out of the box solution even if it is just cosmetic (help with license requirements, etc.)
    Expand Post
    Portal User
    7 years ago
    Surely the best solution would be not to rely on the Ivanti data at all and install snow agents on these devices?
    Expand Post
    Portal User
    7 years ago
    Surely the best solution would be not to rely on the Ivanti data at all and install snow agents on these devices?
    Expand Post

10 of 17

Related Product Forums

→ Flexera One

→ Snow Atlas

→ FlexNet Manager

→ Snow License Manager

→ App Broker

Need help finding an answer?

Ask a Question →