Software Model Suite Parent not matching after reconciliation

jfortenbaugh
Tera Expert

After running reconciliation for Microsoft products, software installation records are not showing the correct Software model result in the Software Installations table.

 

In the "Microsoft Windows 10" software model, I entered the "Microsoft 365 Government G5" software model as the Suite Parent to "Microsoft Windows 10" since it is the active software entitlement for these licenses in my environment.  After running reconciliation, the Windows 10 installations are showing as noncompliant.  The Software model result associated to these installations is "Microsoft Windows 10".

 

I verified all Windows 10 discovery models have been normalized.  I'm not certain where to go from here.

1 ACCEPTED SOLUTION

jfortenbaugh
Tera Expert

I was able to resolve the issue.  Entitlements must be in a published ("in use") state for the reconciliation to work.  I hadn't published this new entitlement, which caused the unlicensed installations.  Thanks to everyone who offered their assistance.

View solution in original post

7 REPLIES 7

mikew_samexpert
Mega Guru

 What inference percentage have you set against the M365 Government G5 software model?

Inference percentage on that model is set to 0 (zero).

 

The strange thing is I am able to get the suite associations to calculate correctly on our other dev/test environments.  Our production environment uses live data, while the others use cloned data.  Software installation records, software models, discovery models, and software entitlements appear identical on PROD and non-PROD environments.

 

 

Community Alums
Not applicable

Hi @jfortenbaugh ,

 

Can you please check the the parent software and their suits should be assigned to the same user in software installation table. If those are assigned to same user and is less than the inference percentage defined in the parent software model, then it will be counted as one and reconciliation result will be fine.

 

I guess you didn't checked the assigned to field and then calculated the compliance.

 

Thank you,

Santosh Poudel

I have the inference percentage set to 0 (zero).  This works perfectly in our non-production environments, which uses cloned data from our production environment.