- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2025 09:19 AM
Hi all, I have been pulling my hair out over this all day. I am looking at installation data I have a list of installations where they have the same display name, same discovery model, same DMAP yet some of the installations do not have a software model assigned to them. I cannot see why this has occurred and where to start looking. What conditions can cause this?
The discovery model does have a software model assigned and as far as I know everything is OOTB.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2025 10:40 PM
Hi @andynewey ,
Here’s what I’d suggest checking:
1: Start with the Discovery Model Mapping
Even though the discovery model looks the same, open it up and double-check that it’s mapped to a software model.
Go to:
- Software Asset > Normalize > Discovery Models
- Is the Software Model field populated?
- Is the Normalization Status set to Active?
Also confirm the Publisher matches what your software model expects (in your case, “N/A” might be the reason — sometimes mismatched publishers can break normalization quietly).
2: Look at the Normalization Logs
Head over to:
Software Asset > Normalize > Normalization Log
- Look for any errors or skips. You’ll often find entries like:
- No software model found
- Normalization skipped due to missing mapping
This will tell you why normalization didn’t happen for certain installs.
3: Check When the Records Were Created
If the installations came in before the discovery model was mapped to a software model, those entries won’t be backfilled automatically.
To fix this:
- rerun the Normalization job manually
- This usually forces the mapping to apply again.
Look closely at things like:
- Publisher field being N/A — this might cause some installs to not match the mapping
- Version formatting — a small mismatch can stop normalization from assigning the model
- Try editing one of the installs manually with the correct Publisher (e.g., Adobe Systems) and trigger normalization to see if it resolves.
4: Reconcile After Fixing
After making changes or fixing mappings, make sure to run:
Software Asset Workspace > Reconcile Software Install
This updates your software model assignments and ensures your compliance data is accurate.
5: Optional — Manual Mapping
If this is a recurring issue with specific installs, consider adding a manual override:
Go to the Discovery Model
- Assign a fixed Software Model to it directly, or
- Create a custom mapping rule based on version/publisher/display name
That way, you’re not relying entirely on automated logic that might miss these edge cases.
Regards,
Abhishek
Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2025 10:40 PM
Hi @andynewey ,
Here’s what I’d suggest checking:
1: Start with the Discovery Model Mapping
Even though the discovery model looks the same, open it up and double-check that it’s mapped to a software model.
Go to:
- Software Asset > Normalize > Discovery Models
- Is the Software Model field populated?
- Is the Normalization Status set to Active?
Also confirm the Publisher matches what your software model expects (in your case, “N/A” might be the reason — sometimes mismatched publishers can break normalization quietly).
2: Look at the Normalization Logs
Head over to:
Software Asset > Normalize > Normalization Log
- Look for any errors or skips. You’ll often find entries like:
- No software model found
- Normalization skipped due to missing mapping
This will tell you why normalization didn’t happen for certain installs.
3: Check When the Records Were Created
If the installations came in before the discovery model was mapped to a software model, those entries won’t be backfilled automatically.
To fix this:
- rerun the Normalization job manually
- This usually forces the mapping to apply again.
Look closely at things like:
- Publisher field being N/A — this might cause some installs to not match the mapping
- Version formatting — a small mismatch can stop normalization from assigning the model
- Try editing one of the installs manually with the correct Publisher (e.g., Adobe Systems) and trigger normalization to see if it resolves.
4: Reconcile After Fixing
After making changes or fixing mappings, make sure to run:
Software Asset Workspace > Reconcile Software Install
This updates your software model assignments and ensures your compliance data is accurate.
5: Optional — Manual Mapping
If this is a recurring issue with specific installs, consider adding a manual override:
Go to the Discovery Model
- Assign a fixed Software Model to it directly, or
- Create a custom mapping rule based on version/publisher/display name
That way, you’re not relying entirely on automated logic that might miss these edge cases.
Regards,
Abhishek
Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2025 05:35 AM
Hi @andynewey ,
I just tested this on my instance and realized the information I shared earlier wasn’t accurate — some of the details I mentioned don't seem to apply as expected.
Apologies for the confusion. Please feel free to ignore my previous post for now — I’ll recheck everything and come back with a proper, verified response shortly.
Thanks for your understanding.
Regards,
Abhishek