This guide details how to add Products into the General Licence Statement to match up licence usages using Asset Intelligence.
What this means is that you can then use Asset Intelligence reports to see what your corporate software licence usages are against what you actually have purchased.
Open the Configuration Manager console. Go into the Asset and Compliance Workspace and then browse to Asset Intelligence > Inventoried Software:
On the right side window, you should now see all the software that has been inventoried and are in the SCCM database. To use this information to produce software licensing reports, you have to ensure that you use the exact Product Name that is in this Inventoried Software location.
As an example, if you wanted to add Microsoft Project 2013 to your Software Licencing usage reporting, you need to do the following:
You can type in the search area under Inventoried Software the product that you are looking for, so in this case, we type “project”. As you can see below, this brings down the number of software titles to look through to find the right one, keep scrolling down until you find the software title you are looking for:
Once you have found the software title, double click it to bring up a box that should be similar to the one below:
There are three parts that you are interested in, the rest of just categories that are not important at this time. What you are looking for are:
For any reports to work, your import of the GLS spread sheet must match these settings perfectly. So, once you have noted this information, you should open your GLS spread sheet that you have created. If you have not yet created one, you can download a template from here:
Also be aware that the spreadsheets are in CSV format and should never be changed from this format. In this guide, we’ll open up the GLS spreadsheet. When opened, it should look like this:
Obviously, the more software titles that are added to it, the more rows that will be added. You should take the next available free row and add in your information. You can fill out all area’s but only the three area’s as stated above are critical for this to work. However, you should correctly complete the EffectiveQuantity as this is the number of available licences to your business.
Once you have added your Project 2013 software title, the spread sheet should look like this (note that Publisher as labelled on the spread sheet is actually the Vendor from the software title):
Once you have added the software titles that you want to add, you should save this spread sheet (remembering to keep the CSV format) to a network location where your console can access it.
You should then go back into the Configuration Manager console and back to the Asset Intelligence folder. Once there, right click on the Asset Intelligence folder and select Import Software Licenses.
Then click on the General Licence Statement (.csv file) radio button and then enter the network location of where you saved the GLS file to:
Click next and complete the wizard. If your import has been successful, you should see the below summary page:
The import of your software titles to the asset intelligence system is now complete. To view this information, the report that you should use is:
Asset Intelligence > License 15A – General license reconciliation report When you run this report now, it should show you all the information you require to tally up the licences. This information is presented in the report as:
Licence Quantity (which is the EffectiveQuantity value entered into the spread sheet)
Inventory Count (licences used)
Difference (left over/over used licences – calculated as Licence Quantity – Inventory Count)
If you have any questions about this article or any feedback you would like to leave, please leave us a message below in our comments section and we will get back to you as soon as possible.
Although the below does help, the issue I had was actually with the WCF 3.0 Windows Update. It was this that messed up our MPs, having applied the MS “fix” (or reg hack quick fix as it really is) we have not had an issue since.
I’ve had an issue for the last few days where my clients were not working correctly with the software catalog. Having checked their certificates they were set to none on the clients too.
I removed the management point on my primary server and then re-installed it, which seemed to have fixed it, however, the problem returned the following day. So, I re-installed the MP again, fixed it, but next day, problem returns!
Having looked into it further I found that the problem was with the SMS Agent Host service on the primary server. It kept stopping itself and taking the MP down with it. If I restarted it, everything worked, but every night it stop again.
After going through yet more endless logs I couldn’t really find any problem with the configuration, until I checked our CM2012 servers Endpoint Protection policy. It turned out that I forgotten to add the service and it’s executables to the excluded processes and files. So, I added them and I’ve not had a problem since. Obviously the problem was that Endpoint was stopping the service when the daily scans were happening.
For your reference, the two processes and files you need to exclude to avoid a similar issue are:
Next time, I’ll know where to start looking for any strange issues!
If you would like to create a report to show you the number of different Operating System’s you have, you can use this script below which should provide you with the information for Servers and the various Windows OS’s. Query SELECT CASE WHEN Caption0 LIKE ‘%XP%’ THEN ‘XP’ WHEN Caption0 LIKE ‘%Windows 7%’ THEN ‘Windows … Read more
You may have noticed when setting up task sequence deployments for your OSD‘s or when setting up packages for the Software Catalog that you cannot run the task or program directly from the distribution point as the only option is to download the files and run from the local cache.
Well, there is a setting that you can change to allow you to run your task sequences directly from the local distribution point. To change this, you should ensure that all your packages associated to your task sequence (or just your single package for the software catalog..) have the following box ticked:
This will then allow you to change the settings under your deployment options to run from distribution point as well as download and run from the local cache.
Note that this does copy all the files in the package to your distribution points and will take up more space, so think about this before doing it.