Using SCCM to collect Autodesk serial numbers

Autodesk AutoCAD Logo

In the past we have released SCCM Configuration Item VBScripts to collect Autodesk serial numbers and then inject this information in to the WMI to be collected by the next hardware inventory.

After much researching and testing, we have now made a decision that this is not the best way to collect this source of information from user machines. We will now be using a similar, yet much simpler way of doing this.



This involves editing the SCCM configuration.mof file on the primary server and adding a class to the hardware inventory collection.

Using this method allows us to collect the following information from users machines:

  • Product Name
  • Product Release
  • Serial Number
  • Stand Alone Network Type

Update

AutoCAD 2019 & AutoCAD LT 2019 have now been added to our MOF script!

We have collated a huge text file which has what we believe, every single Autodesk product on the market (not just AutoCAD) and the registry entries that the configuration.mof will look at to collect the data from the end users machine.

Below we will supply you with this text file and also full instructions on what to do with it.

Using this method we’ll also be releasing other text files for serial number collection such as NitroPDF and PDF-X Change. If you have a product that you would like us to look into for you for similar data collection then please leave a comment at the end of this guide.

Downloads

You can now download the Autodesk 2019 MOF pack & the Full Autodesk MOF pack from us by clicking the links below.

Download Autodesk MOF 2018 Full Pack

Download AutoCAD 2019 & AuoCAD LT 2019 MOF Script

Instructions

Once you have downloaded the text file from above, you need to go to the following location on your primary SCCM server:

 Take a copy of your configuration.mof file and copy it to a test machine that has the Configuration Manager Console installed on it.

Edit the test configuration.mof file on your test machine using a product like Notepad++ and at the very bottom of the file you will see a bit of code like this:

In the middle of this code you should copy and paste the contents of the text file that you have downloaded from our site earlier. So, the end of your configuration.mof file should look like this (note that we’ve stripped it right down to one product for demo purposes, yours should be A LOT longer!):

You should then save the configuration.mof file on your test machine.

Once you have done that, you need to compile the configuration.mof file on your test machine, this will allow us to use the test machine to import the hardware inventory class later in this guide.

To do this, open a command prompt as administrator and type in the following command:

To continue reading, please click the next page below….



3 Responses

  1. Chiangpah says:

    Hello
    This is a great piece but I do not seem to have any populated results once I run the query.
    I created a new custom client device setting that included only the hardware inventory with a refresh interval of 15 minutes.
    I am not sure if I should recreate it to include both hardware and software inventories…

    I appreciate your help

  2. Joe B says:

    HI,

    Great work with this, it’s been really helpful. Can you explain what the meaning of the data in the StandaloneorNetwork column means? I seem to be only getting the value 2 or NULL. Is a non NULL value a standalone installation and a NULL value a network licensed installation, or have I got that completely wrong?

Leave us a message...