- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2023 04:37 PM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2023 02:20 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2023 11:58 PM
@jfortenbaugh, we've a similar issue with Microsoft Core Infrastructure Server and the System Center Suite components. One of the Components of System center is assigned to a M365 plan and we never get a valid results for our CIS licenses. I've hand over this case to the ServiceNow Support.
If the two very helpful hints by @mikew_samexpert & @Community Alums doesn't solve the issue, I would recommend to open a case.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2023 09:01 AM
Yeah it's really strange. I am able to get it to work correctly on our non-production environments.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2023 02:20 PM
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.