Suite Inference Levels

[jfortenbaugh]

When running reconciliation for Microsoft products, some results are returned with a Suite Inference Level value of 999.  I cannot locate any reference materials to determine the meaning of this value as the suite shouldn't go any higher than 3 according to the Suite structure defined in the associated Software Models.

 

These are 2 SQL Server software installation records.  I removed the device names per customer policy.

When comparing values of both records, I cannot determine where the difference lies.  Something must be different for them to be treated differently.

[Amarjeet Pal]

Hello @jfortenbaugh ,

 
A Suite Inference Level value of 999 indicates that no suite inference was performed for that record, and it was not matched to any suites in the system.

It's possible that the difference between the two SQL Server software installation records lies in their underlying data, such as differences in version numbers or other attributes. You can try comparing all relevant fields and values between the two records to identify any differences.

If you are unable to identify any differences between the two records, you may want to review your Software Models configuration and ensure that it accurately reflects the suite structure for Microsoft products. It's also possible that there could be some issue with your reconciliation job or associated Business Rules, so reviewing those settings may also be helpful.

Thanks

Amarjeet Pal

[jfortenbaugh]

Thanks for the reply.  I'm unable to determine the difference between the 2 records after comparing all available data.

Is there reference material that documents the correct suite structure?

I'm experiencing the same issue across various Microsoft software types.  As an example, for the following discovery model:

Microsoft Windows Server 2022 Standard 10.0.20348

Should the "Software Model" field contain:

Microsoft Windows Server Standard

or

 Microsoft Windows Server 2022 Standard

My inexperience leads to a lot of trial and error, but I feel like I am spinning my wheels more often than not.

I created a suite structure of Microsoft Windows Server 2022 Standard -> Microsoft Windows Server Standard

It seemed logical to place the model identified in the software entitlement at the top (parent) of the suite structure.

[Amarjeet Pal]

To answer your question, the correct suite structure for Microsoft Windows Server 2022 Standard would depend on your organization's specific entitlements and licensing agreements. You may need to consult with your software vendor or licensing team to determine the appropriate suite structure for your environment. In general, it is advisable to create a suite structure that aligns with your organization's licensing agreements and matches the hierarchy of suites defined by the vendor. However, this can vary depending on the specific software and entitlements in question.

Please hit Helpful to all my responses.

Thanks

Amarjeet Pal

[jfortenbaugh]

Thanks for the reply.

Sorry for the confusion.  I was trying to clarify how ServiceNow interprets the relationship between the following data:

- Software entitlement software model field

  -- Within the entitlement, if using a product part number, the software model field is auto-populated.

- Discovery model software model field

  -- As this is not a mandatory field, how is it used?  If populated, does ServiceNow attempt to force the relationship?

- Software model suite structure

  -- As a rule, should products be structured in multiple levels or limit to 2-3 levels?

  -- i.e. Windows Server > WIndows Server 2019 > WIndows Server 2019 Standard > Windows Server Standard

     --- Or list multiple versions as children directly to the parent (Windows Server Standard)

         ---- Windows Server, Windows Server 2019, Windows Server 2019 Standard, etc

I'm going to pose these questions in a new post to hopefully get more eyes and replies.  Thanks for your assistance.