Distinguish between Adobe Acrobat 2017 Standard vs Professional editions

[boba]

We have a variety of Adobe Acrobat 2017 Standard and Adobe Acrobat 2017 Professional installations in our environment discovered by SCCM.  It appears as though there is no way to distinguish between the two when discovery models are created and normalized.  Are there people who are able to normalize these to the appropriate edition?  We believe that some of the values in the Primary Key may help us distinguish between the two editions, however this is not a pattern normalization field we can select. 

[Ron Lucas]

Hi Daniel.

What if Discovery is being used instead of SCCM to populate the CMDB for servers and workstations?  I see the same issue where Adobe Acrobat 2017 software installation records don't mention the edition.

Thanks,

Ron

[Daniel Slocum]

Hi Ron,

You should be able to write a Discovery Pattern to return the edition.  However, before walking that path, you should validate one isn't already available.  Pattern updates are released on a regular basis to the ServiceNow store and are downloadable for free.

[Ron Lucas]

Hi Daniel.

For Windows computers discovered using patterns, it appears Discovery still uses the probe "WMIRunner-Windows - Installed Software" to discover installed software.  This is mentioned in documentation here:

https://docs.servicenow.com/bundle/newyork-it-operations-management/page/product/discovery/reference...

I've opened a ticket with HI to see what they have to say about this before we customize anything.  If edition isn't identified by Discovery for all Adobe products, this is a significant defect as customers who purchase Discovery and SAMP expect this capability out of the box.

If I learn anything from HI, I'll reply back here.

Thanks,

Ron

[Daniel Slocum]

Ron

Please reply back here with what you learn from HI Support.  While I don't disagree with your assessment, I do want to make clear that all communication from Product Success (of which I'm a part), Product Line Sales and from the ITAM BU at ServiceNow identify that we recommend SCCM and SN Discovery as the sources of discovery best suited for SAM;  SCCM for end user computing devices and SN Discovery for infrastructure devices.  There are some drawbacks to using just SN Discovery for end user computing such as an inability to reclaim software and to identify usage levels.  

Daniel

[Frank1975]

Hi all, 

is this fix from Service Now working for anyone ? 

We have tried the fix and it won´t bring back the data for the edition. 

If someone got it up and running , please gimme a message. Would like to know where we got stuck or if its not working at all (should also fix the edition issue with SQL)

thanks
Frank