Custom solution to gather editions in SCCMIssue Introduction Edition information for installed products is not captured by SCCM OOB processes and each publisher stores in a unique location. This custom solution parses through registry keys to gather edition for products such as Adobe Acrobat, Microsoft SQL Server, and Windows Exchange Server. One can choose to add additional modules to gather for other products. Requirements Need to have SCCM integration plugin and Software Asset Management Professional plugin installedAll the client machines should have PowerShell installedProduct and Publisher values in the PowerShell script are hardcoded and is following the convention below. It is required to follow the convention in order to identify the right software install to populate the edition. The product should be an exact match from the samp_sw_product table and prod_name field which is the normalized product on software install recordThe publisher should be an exact match from the samp_sw_product table and publisher field which is the normalized publisher on software install record How it works Service Graph Connector for Microsoft SCCM Software Edition data source brings in the edition records from SCCM DB, each row is transformed using a script and processed in two phases. If a matching install is found in phase one, its edition override field is populated and proceeds to next row. If match not found, goes into phase two and tries to find a matching install. If both fail, it skips the row and moves onto the next row. Below are the matching criteria in both the phases: Phase 1 normalized productnormalized publisherversioninstalled on (CI)created by application pattern = falseempty edition override Phase 2 normalized productnormalized publisherempty versioninstalled on (CI)created by application pattern = falseempty edition override Setup Two types of setup are required, one on SCCM Manager and the other on ServiceNow instance. SCCM Manager Setup 1. Create a shared folder on the same machine as SCCM manager and copy the network path. For example, mine is called \\SAMLABVM501\Shared Download fetchEditions.txt and save in the above created shared folder. Note: Fix the extension to .ps1 which denotes PowerShell script (it's currently .txt) and should not be deleted since its required by SCCM manager to execute on schedule. Note: If implementing for the first time, proceed to step 2. If upgrading the current implementation (the above file when download will have version=2.0) Replace original fetchEditions.ps1 file with newly downloaded fetchEditions.ps1 file in the shared folder.Go to SCCM manager -> software Library -> Application Management -> Packages. Right click on the package you had previously created to fetch editions and select "Update Distribution Points" as documented by Microsoft here. Click OK. This is to instruct client machines to fetch information as per 2.0 changes. 2. Go to SCCM manager -> Software Library -> Application Management -> Packages. Click “Create Package” on the top left to create a new package 3. Fill out the Package information as shown below and make sure the source folder has the network path you copied in step 1 and click Next 4. Select Standard Program and click Next 5. Fill out the next set of fields as shown in below snapshot (Note: file name at the end of the command should match to the file copied to the shared folder) and click Next Command line: "C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -ExecutionPolicy Bypass -Command .\fetchEditions.ps1 6. Go to the shared folder and look up the size of the PowerShell script. Change the maximum allowed run time to 15 minutes instead of the default and populate disk space as below and click Next. 7. Shows a summary of all the configuration we did from step 4-7, click Next. 8. You will see a successful completion dialog, click Close. 9. The package we just created will show up in Software Library -> Application Management -> Packages as below: 10. Right click on the package name and click Distribute Content: 11. Click Next 12. Select Add and select the method of distribution you need, I am choosing Distribution Point. Click Next. 13. Shows the summary, click Next. 14. After completed successfully, click Close. 15. Right click on the package name again and click Deploy 16. Select the collection you want to deploy the package to as below and click Next 17. A distribution point should be pre-selected, if not, go ahead and Add and click Next: 18. Make sure the Purpose is set to Required and click Next. 19. Click New to create an Assignment schedule as below: Click schedule: Create a custom schedule, I opted as below and click OK: Click OK: Make sure Rerun Behavior is set to Always rerun program as below and click Next: 20. Check and uncheck fields as below and click Next: 21. Switch both options to Run program from distribution point since this is a fairly small program and click Next as below: 22. Shows the Summary, click Next 23. Click Close on the successfully completed screen 24. Give it a few minutes and check to make sure the package is executed successfully on all client machines Go to SCCM Manager -> Monitoring -> Deployments and find the package you just created. Double click on it and you should see as below under success tab: Note: If you see entries in the Error tab as below, then go back to Software Library -> Packages -> find your package, right click and click Update Distribution Points. Give it a few mins and go back to Monitoring -> Deployments and check again. Click OK 25. Add the newly created WMI class (created in the PowerShell script we downloaded) to hardware inventory. Go to SCCM Manager -> Administration -> Client Settings Right click on Default Client Settings and click on Properties as below: Go into Hardware Inventory and click Set Classes as below: Click on Add as below: Click on Connect as below. When we deployed the package, it ran successfully on client machines (on SAMLABVM303 in snapshot), I will need to connect to that machine to pick the WMI class. Find and check against SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION and click OK as below: It shows up selected on the Hardware Inventory Classes as below and click OK and click OK on the Default Settings screen. If you go into all the other custom client settings -> Properties -> Hardware Inventory -> Set Classes, you should see SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION checked already as below: Once client machines receive new machine policy and hardware inventory changes, in the next hardware inventory collection cycle, the WMI class (SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION) data will be sent back. This class creates a view in SCCM DB called v_GS_SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION ServiceNow Setup On the left navigation: Go to Integration – Service Graph Connector for Microsoft SCCM Software Edition. To enable it, check the Active field and click UpdateGo to Integration – Service Graph Connector for Microsoft SCCM -> Click on the related list transforms, Update software install with edition transform. To enable it, check the Active field and click Update Verification Make sure there are entries in SCCM database -> Views -> v_GS_SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION viewRun Integration - Service Graph Connector for Microsoft SCCM –> Scheduled ImportGo to Integration - Service Graph Connector for Microsoft SCCM –> Progress and click All on the filter, you should see an entry for Creating import set: sn_sccm_integrate_sccm_2019_software_edition or Creating import set: with Completion Code Success. This ensures Software Edition data source executed successfullyEdition data should be populated on the edition override field on the software install recordsThis would trigger a re-normalization of the discovery model associated with the install record. Normalization uses content rules / packages to map the number formatted editions (7760) to text editions (Professional) and updates the discovery model accordingly. No changes will be made to the install records after re-normalization. Troubleshooting If the desired software install is not updated with edition, check following Make sure Service Graph Connector for Microsoft SCCM Software Edition scheduled import record is activeMake sure Update software install with edition transform map is activeTest the Service Graph Connector for Microsoft SCCM Software Edition data sourceMake sure the product and publisher used to populate in PowerShell script is exists in the samp_sw_product table. If the V_GS_ SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION view has no records, on any of the client machines, check CCM log (execmgr.log), it should read “Script for Package:P0100009, Program: Fetch Editions succeeded with exit code 0”. Failed execution will say something like: “Script for Package:P0100007, Program: Fetch Editions failed with exit code 1” Disable Software Edition Solution In case the user is having unexpected issues with the above solution and would like to discontinue its execution they can follow the step below: 1. Disable this schedule import Service Graph Connector for Microsoft SCCM 'Software Edition' on the instance by unchecking the 'Active' field checkbox to have this import as Active = false going forward which will not make it execute.