To actually get the software edition information, you will need to write out some Powershell code that SCCM will run against the systems it’s managing and on top of that, you will more than likely need a custom section of code for each and every software package you would like to get the edition information for. The solution proposed in the KB article is a lengthy 25 step process that needs to be performed on the SCCM server, and it only gets SCCM ready to pull that information and then pass it over to ServiceNow. If you have a Servicenow HI account, you can find that article here. You’ll find the information for SCCM to get software editions in a Servicenow Knowledge Base(KB) article titled “Custom solution to gather editions in SCCM”. Click To TweetĬhecking the ServiceNow documentation for configuring Software Asset Management with SCCM here, you can find the following statement under the Normalization heading: “The normalization process compares the discovered publisher, discovered product, and discovered version and edition values against the ServiceNow repository of normalized equivalents.” If you look around on the same page, you will find no mention of that fact that to get the edition information, further configuration within SCCM is needed. You would be forgiven for thinking that SCCM pulls this information because according to ServiceNow, it does. It makes a difference because in order to link the installations on a given system to your pool of Software Entitlements or Licenses, ServiceNow will need to know the edition. “Standard” and “Professional” would be your editions. In this example, Edition is the difference between Acrobat Standard and Acrobat Professional. I’ll use Adobe Acrobat as an example because a lot of people will be familiar with it.

If you are asking yourself, “What is Software Edition?”, let me give you a brief example and then tell you why it makes a big difference when it comes to Software Asset Management.

It can pull that information, but to do so requires a lot of work that will need to be done by someone who not only has access to all of the SCCM managed systems but someone who also knows how to write code in Powershell. It turns out that SCCM does not actually pull Software Edition information for software installed on the systems that SCCM manages out of the box.

In working with a client recently, we came across a problem that exists when trying to incorporate System Center Configuration Manager (SCCM) software installations with Software Asset Management.

Sccm servicenow