Report AutoCAD Product and Serial Numbers using Configuration Manager

Autodesk Transparent Logo

This post is a rehash of an old post we did back in December 2013 but with the recent release of version 2016 of AutoCAD and AutoCAD LT and also the release of our updated code to retrieve the serial numbers from machines for this updated product; we thought that we would slightly update this post and re-publish it.


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

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.


You should first ensure that you have downloaded the file below – this is the text file that contains all the information you will need to retrieve your AutoCAD serial numbers from the WMI on users machines.

Autodesk 2021 Serial Number Collection Now Available!

This post has now been superseded by our Autodesk 2021 MOF file download. Click the button below to go to this latest version.

This download is now available direct from our site by clicking the button below.

Download Autodesk Latest MOF File


Editing the configuration.mof file

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

%programfiles%\Microsoft Configuration Manager\inboxes\clifiles.src\hinv

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:

// Added extensions Start
// Added extensions end

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!):

// Added extensions Start
#pragma namespace (".rootcimv2")
#pragma deleteclass("Autodesk_Inventory", NOFAIL)
Class Autodesk_Inventory
[key] string KeyName;
String ProductName;
String Release;
String SerialNumber;
Uint32 StandaloneNetworkType;
Instance of Autodesk_Inventory
KeyName="AutoCAD 2000";
[PropertyContext("Local|HKEY_LOCAL_MACHINESoftwareAutodeskAutoCADR15.0ACAD-1:409|ProductName"),Dynamic,Provider("RegPropProv")] ProductName;
[PropertyContext("Local|HKEY_LOCAL_MACHINESoftwareAutodeskAutoCADR15.0ACAD-1:409|Release"),Dynamic,Provider("RegPropProv")] Release;
[PropertyContext("Local|HKEY_LOCAL_MACHINESoftwareAutodeskAutoCADR15.0ACAD-1:409|SerialNumber"),Dynamic,Provider("RegPropProv")] SerialNumber;
[PropertyContext("Local|HKEY_LOCAL_MACHINESoftwareAutodeskAutoCADR15.0ACAD-1:409|StandaloneNetworkType"),Dynamic,Provider("RegPropProv")] StandaloneNetworkType;
// Added extensions end

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

Compile the MOF file

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:

mofcomp.exe "location of your test configuration.mof"

For example:

Report AutoCAD Product and Serial Numbers using Configuration Manager 1

When you press enter, you may get an error about PRAGMA AUTORECOVER, you can add this if you like, but for this guide, I’m going to ignore this:

Report AutoCAD Product and Serial Numbers using Configuration Manager 2

Hardware Inventory

Now that you have the correct MOF compilations on your test machine, you should now open up the Configuration Manager Console. Go into the Administration > Client Settings page:

Report AutoCAD Product and Serial Numbers using Configuration Manager 3

You then need to edit the Default Client Settings, right click on it and select Properties. This will bring up your Default Client Settings, you then need to go into the Hardware Inventory options:

Report AutoCAD Product and Serial Numbers using Configuration Manager 4

In here, you should then click on the Set Classes… button:

Report AutoCAD Product and Serial Numbers using Configuration Manager 5

You will then be presented with another dialogue box, you should then press the Add button:

Report AutoCAD Product and Serial Numbers using Configuration Manager 6

This is now where we connect to the local namespace of the test machine and select the Autodesk_Inventory and Autodesk_Inventory_64 classes and click OK. This will then import these classes into the SCCM primary servers hardware inventory classes.

However, there is still one more thing left to do…

Update master configuration.mof file

Now that you have your client settings ready to collect the WMI classes hardware inventory on your end users machines, you still need to update the configuration.mof file on your primary SCCM server.

I would highly recommend taking a backup of your current configuration.mof file on your primary server first, then take the edited file from your test machine and overwrite the one on your primary server with it. This will then give your end users machines this updated configuration.mof file and when the hardware inventory runs on the machines, the requested data will be collected into an SQL table in your SCCM database.

You can then use SSRS to create a report to display all the data collected.

If you keep a check on our website, we will be releasing further product collections that you can add to your hardware inventory and configuration.mof allowing you to build up a collection of reports that will give you your productions information and serial numbers.

How do I create the SSRS report?

We have now created a guide that will help you to create your SSRS reports based on the data that this guide will pull into the Configuration Manager database.

You can access this guide by clicking the link below:

Create a SSRS Report using Configuration Manager Database Data


If you have any problems with this or just want to ask a question, please leave a mssage below using our comments section.

SQL Reporting Services Error – Maximum request length exceeded

system center

When running or trying to create a large report in SSRS, you may come across an error stating the below:

Error 2: There was an exception running the extensions specified in the config file. Maximum request length exceeded.

SQL Reporting Services Error - Maximum request length exceeded 7

It took us a while to figure this one out but it is actually very simple. After speaking to our SQL and web development guys, it basically means that you are trying to pull more data than what the system is configured to allow. This is why you get the error, but it is simple to fix if you have a basic understanding of IIS.

You need to amend the web.config file on the reporting server which you should find in the location below unless you have installed it elsewhere:

C:\Program Files\Microsoft SQL Server\MSSQL.12\Reporting Services\ReportServer

Open the web.config file with notepad and then search for the following line:

<executionTimeout = “9000”>

After the 9000 text, you can add a maxRequestLength variable to allow more data to flow. 500000 equals 5mb:

<executionTimeout = “9000” maxRequestLength=”500000″ />

The IIS service then needs to be restarted, so you can either restart the reporting server or type “iisreset” into a command prompt on the server.


If you have any questions or comments about this guide, please feel free to leave a comment below using our comments system.

CM2012 Console Create Report Fix

sccm logo

If you have Configuration Manager 2012 and you are using SQL Reporting, you may want to create some custom reports. In your Configuration Manager 2012 Console, you can browse to Monitoring, then into the Reporting module. This will display all the reports that are currently available to you. If you want to create a custom report, you can click on the Create Report button on the ribbon:
CM2012 Console Create Report Fix 8

However, you may find that when you do this, you get the following error pop up:

The Report Builder click once application does not exist on the report server “your-report-server”. Ensure that the report builder application manifest exist on the server and try again

The reason for this is that there is a registry key that needs to be updated to version 3 as when the CM2012 console is installed, it puts in the version 2 key and the report builder will not work.

To make this fix as simple as possible, we have created an MSI installer that will make the changes required and then allow you to create custom reports from the CM2012 Console. As it is an MSI file, you can also add it to your Software Catalog to distribute to other should this be required.


Download CM Report Builder Fix

PAD File

Download PAD File


If you have any comments, please leave them below using our comments system.