Software installs not being consumed by conditional software model

Cairns
Tera Expert

Hi,

As part of a process to clean up Adobe Creative Cloud installations for one of my customers, we have been creating software models with conditions to consume certain installs. One of these models targets installations with versions starting with 1.0. Our expectation is that any install with a version starting with 1.0 would be consumed, allowing us to uncheck the “license under management” box and ignore these during reconciliation. While this approach has worked for some installs, it hasn’t been effective for all. Specifically, installs with a version of 1.0.0000 are not being consumed as expected. Has anyone else encountered this issue, and if so, did you find a solution?

Thanks

1 ACCEPTED SOLUTION

dreinhardt
Tera Sage

Hi @Cairns,

could you please check the related links on you software model records about the matching discovery models?

If your "1.0.0000" discovery models does not appears, then I would check the normalization again and correct it if necessary. I have seen some strange things, for example spaces consisting of special ASCII codes that were only recognized with difficulty, but that prevented an exact match.

 

My Recommendation: Normalize all your discovery models (installs) in scope to the same publisher, product, version, edition value to ensure a clean baseline for your software model condition - Add a software pattern normalization rule (servicenow.com) could help.

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

View solution in original post

2 REPLIES 2

dreinhardt
Tera Sage

Hi @Cairns,

could you please check the related links on you software model records about the matching discovery models?

If your "1.0.0000" discovery models does not appears, then I would check the normalization again and correct it if necessary. I have seen some strange things, for example spaces consisting of special ASCII codes that were only recognized with difficulty, but that prevented an exact match.

 

My Recommendation: Normalize all your discovery models (installs) in scope to the same publisher, product, version, edition value to ensure a clean baseline for your software model condition - Add a software pattern normalization rule (servicenow.com) could help.

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

Hi Dennis,
So the discovery model for the 1.0.0000 installs wasn't showing in the "matching discovery models" of the software models. I have since re-normalized the problematic discovery models and this has seemed to work. I will keep an eye on them to see if the problem re-occurs after a content library update but for now I am happy.
Thank you for your recommendation