DWG TrueView 2015 has now been released and we have already been asked by a number of people about how to deploy this using Configuration Manager Software Catalog. The solution is very simple and the process that you should follow is exactly the same as the process that we have detailed for the 2014 version … Read more
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:
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.
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.
Autodesk 2020 Serial Number Collection Now Available!
This post has now been superseded by our Autodesk 2020 MOF file download. Click the button below to go to this latest version.
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:
mofcomp.exe "location of your test configuration.mof"
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:
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:
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:
In here, you should then click on the Set Classes… button:
You will then be presented with another dialogue box, you should then press the Add button:
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…
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:
We have made some major updates to our Autodesk products serial number reporting script which should fix all of the reporting issues that some people have seen. It also includes a large amount of additional languages and products.
WHAT PRODUCTS ARE INCLUDED?
The list of Autodesk products that this Configuration Item script will now report back to your SCCM database are the following:
AutoCAD – English / German / French / Italian / Spanish / Polish / Hungarian / Czech / Russian / Brazilian Portuguese / Simplified Chinese / Traditional Chinese / Korean / Japanese
AutoCAD LT – English / German / French / Italian / Spanish / Polish / Hungarian / Czech / Russian / Brazilian Portuguese / Simplified Chinese / Traditional Chinese / Korean / Japanese
Autodesk P&ID – English
Autodesk Architecture – English
Autodesk Mechanical – English
Autodesk Building Systems – English
Autodesk Inventor – English
Autodesk Plant 3D – English
Autodesk Civil 3D – English
Autodesk AutoCAD OEM – English
HOW DOES IT WORK?
This script runs on your users machines using the Configuration Item process of SCCM 2012. The script is a VBScript so can also be run using .vbs files (using login scripts or Group Policy). This then creates a new WMI class called cm_AutoDesk and will inject the following information into this WMI class:
Key Name (registry location of serial)
Standalone Network Type
Once this information is in the users machines WMI, SCCM 2012 can then be configured to collect this information using the Hardware Inventory function.
Full instructions on how to set this up in full can be found below using our step by step guide.
The updated script can be downloaded from the link below:
To install Autodesk DWG Trueview 2015 as a unattended silent install, which you can also use in SCCM to add the application to the software catalog and also in WDS as an application install, you should first download the installation files that you require from the link below:
I’ve been working on getting AutoCAD LT 2014 into our Software Catalog for some time now and I finally cracked it this week which I was delighted about! The idea was that any users that should have AutoCAD can upgrade their software or new starters can install it themselves without our desktop support staff having … Read more
After the success of our Autodesk serial collection and reporting blog post nearly a year ago now, we have had many requests to update the scripts to include the latest versions of Autodesk products and also include a wider range of Autodesk products like Revit.
If you are new to this, it would be worth taking a look at the original blog post which gives you a step by step guide on how to set this up:
This step by step guide will show you how to setup your System Center 2012 Configuration Manager to report to you the Autodesk software that is installed on your clients machines but will also give you the serial numbers for the software and what software package is installed. (If you find the pictures hard to … Read more
In the second part of my blogs about capturing serial numbers using SCCM, in this one I’m going to go through how to report on Autodesk products which of course includes AutoCAD full version and LT versions. Update Please note that we do now recommend a new way of collecting Autodesk serial number information. So … Read more