TechyGeeksHome

How to deploy AutoCAD using SCCM
This is going to be quite a lengthy guide but one that we think you might find very useful.

We have previously shown you how to report Autodesk serial numbers using SCCM and this has led to a number of questions being sent to us on how to deploy AutoCAD using SCCM and in turn, using the software catalog.

So, this guide will show you how to setup your CAD deployments as an application allowing you to either push out or allow as a request through the software catalog.

PRE-REQUISITES

Before we start there are a few things that you should be aware of before using this guide:
INSTRUCTIONS

Once you are happy with the above, then we can start the process of adding AutoCAD LT 2016 - English into our software catalog as an application in SCCM.

You should login to your Autodesk customer portal and download the FULL installer, it should be around 1.3GB in total size and a single file. The filename should be similar to this:

 AutoCAD_LT_2016_SWL_English_Win_64bit_dlm.sfx.exe  

Double click the file and it will ask you to extract to a location, for the purposes of this guide, we will extract it to the default C:\Autodesk folder:


Depending on the machine you are using, this can take some time to extract the full 2.6GB of data.

Once this has completed you should then go to the C:\Autodesk folder and run the standard setup file:

This will start to load the AutoCAD LT 2016 installer and will eventually give you the options to Create Deployment, Install Tools & Utilties or the standard Install. We want to create a deployment so click that button:


You will then be asked to complete the information required for the deployment. You will need to enter the following details:
Once completed, it should look something like this:


Click Next and then accept the terms and conditions, then click Next again to take you to the licence page. 

Here you should enter your serial number and product key and then click Next - or you can chose not to enter anything here and you can enter your licence keys on the end users machines after deployment:


Click Next once you are happy with your licence entry and you can then select the options that you want to have installed as part of the deployment process:


When you have made all your custom selection options, you can click the Create button. This will then run through what looks like a standard installation process and this can take some time:


When this process has completed, you will now have a source location ready to use for your SCCM deployment.

You should now go to the Administrative Image Path location that you stated during the Create Deployment process and you should see a file structure like this:


You will see a folder called SMS_SCCM scripts, go into this folder and then open the text file called "YOUR DEPLOYMENT NAME_SCCM.txt". In here you will find the installation script that you will need to use - so take note of this somewhere as you will need it later in this process. It should be similar to this:

 .\Img\Setup.exe /W /q /I Img\AutoCAD LT 2016 - English.ini /language en-us  

Now we need to actually create the application in SCCM, so open up your SCCM console and go into the Software Library ribbon and then drill down into Applications. Then right click on Applications and Create Application.

We are going to create this application using the MSI files available to us, so you should browse for an MSI file to this location:

 \\DP01\Share\ACADLT\2016\x64\AutoCAD_LT_2016_English\Img\x64\acadlt  

This is your Administrative Image Path and then drill down into Img\x64\acadlt (or x86 if you are deploying x86).

In this folder, you will find an MSI file called acadlt.msi - use this as your starting point to create the application and click Next.

You can then enter all the custom details that you want, however, there is a very important part you must change to make this whole process work, the Installation program. Remember we looked at the SCCM.txt file earlier in the process and there was an installation script? this is where you should now copy and paste that script and overwrite what is in there by default. So your page should look something like this:


You should now run through and complete this wizard to completion.

This will have now created the application with a lot of default settings, but there are still changes to make as the deployment is still looking in the wrong place for its source files, so edit the application and go into the Deployment Types tab and edit the deployment:


You should now go to the Content tab and you need to amend the Content location. Instead of it being in the Img\x64\acadlt folder, you should remove this part and make it so that your Content location is the root of your deployment source.


So you should end up with a Content location similar to this:

 \\DP01\Share\ACADLT\2016\x64\English  

You can then change any other settings you wish here to customise your deployment.

Once you have completed this, you can now deploy the application and you should then see it available in your Software Catalog.

Come back and visit us soon as we will also be writting up a guide on how to add AutoCAD language packs to your Software Catalog.

COMMENTS

If you have any comments or questions on this guide, let please feel free to use our disqus system below to leave a message.

Labels: , ,

Report AutoCAD Product and Serial Numbers using Configuration Manager
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:
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. 

DOWNLOAD

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. This download is now available from our Download microsite by clicking the Download button below then you will find it under the Autodesk folder of our Downloads section.


INSTRUCTIONS

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  
 //========================  
 //Autodesk_Inventory_x86  
 #pragma namespace ("\\\\.\\root\\cimv2")  
 #pragma deleteclass("Autodesk_Inventory", NOFAIL)  
 [DYNPROPS]  
 Class Autodesk_Inventory  
 {  
 [key] string KeyName;  
 String ProductName;  
 String Release;  
 String SerialNumber;  
 Uint32 StandaloneNetworkType;  
 };  
 [DYNPROPS]  
 Instance of Autodesk_Inventory  
 {  
 KeyName="AutoCAD 2000";  
 [PropertyContext("Local|HKEY_LOCAL_MACHINE\\Software\\Autodesk\\AutoCAD\\R15.0\\ACAD-1:409|ProductName"),Dynamic,Provider("RegPropProv")] ProductName;  
 [PropertyContext("Local|HKEY_LOCAL_MACHINE\\Software\\Autodesk\\AutoCAD\\R15.0\\ACAD-1:409|Release"),Dynamic,Provider("RegPropProv")] Release;  
 [PropertyContext("Local|HKEY_LOCAL_MACHINE\\Software\\Autodesk\\AutoCAD\\R15.0\\ACAD-1:409|SerialNumber"),Dynamic,Provider("RegPropProv")] SerialNumber;  
 [PropertyContext("Local|HKEY_LOCAL_MACHINE\\Software\\Autodesk\\AutoCAD\\R15.0\\ACAD-1:409|StandaloneNetworkType"),Dynamic,Provider("RegPropProv")] StandaloneNetworkType;  
 };  
 //========================  
 // Added extensions end  
 //========================  

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"  

For example:


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:

Create a SSRS Report using Configuration Manager Database Data

BUG REPORTING & COMMENTS

If you have any problems with this or just want to ask a question, please leave a comment below using our Disqus system and we will try and answer when we can.

Labels: , ,

AutoCAD 2016 Serial Number Collection Update
We have now updated our Autodesk serial number collection script to include the recently released AutoCAD 2016 and AutoCAD LT 2016.

The following additions have been made to the script:
This is an extension of the full script that we released back in December 2013. The full instructions on how to use this script can be found below:

INSTRUCTIONS

Using SCCM to collect Autodesk serial numbers

DOWNLOAD

You can download the fully updated script below from our Downloads microsite from the Autodesk folder at our Downloads section.


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

COMMENTS

If you have any problems with any of the above, then please leave your comments and questions below using our Disqus system and we will try to get back to you as soon as we can.

We also like to hear back any success stories too, so if you have used our guide and found it helpful, we would love to hear from you.

Labels: ,

DWG TrueView 2015 Released - ConfigMgr Deployment & Unattended Install
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 which can be found below:

INSTRUCTIONS

DWG Trueview 2014 - Unattended Command Line Installation

DOWNLOAD

To download the new version of DWG TrueView, you should use the link below:

DWG TrueView 2015 Download Link

COMMENTS

If you have any questions about doing this and just a general comment, then please use our Disqus system below and we will try and get back to you as soon as we can.

Labels: , , , , ,

Autodesk Products Serial Number Reporting Script Update Version 4.1 - Major Release
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:
WHAT LANGUAGES ARE INCLUDED?
  • 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)
  • Product Name
  • Release Version
  • Serial Number
  • 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.

DOWNLOAD

The updated script can be downloaded from the link below:

Download Autodesk Serial Collector Script

INSTRUCTIONS

Full our full step by step guide on setting this up using SCCM 2012, please click the link below:

Step by Step Guide to Report AutoCAD Serial Numbers

The file that you will download on this page is just the script that is used for the Configuration Item and this can be used to replace your current (or you can add as a new) CI in SCCM.

If you have any problems with this, please feel free to leave a comment.

Labels: , ,

DWG Trueview 2015 - Unattended Command Line Installation
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:

DOWNLOAD

DWG TrueView 2015 Download Link

INSTRUCTIONS

Once you have downloaded the executable file, you should extract the installation files from it. Then use the command line below from the root of the extracted setup files:

 setup.exe /w /t /l /q setup.ini  

You can then also use the command line below for the uninstall string (change x86 for x64 where appropriate):

 msiexec /x "x86\dwgviewr\dwgviewr.msi" /q /norestart  

You can then also use the MSI file located here for the detection method (change x86 for x64 where appropriate):

 x86\dwgviewr\dwgviewr.msi  

A little tip as well is that the full version of Microsoft Dot Net 4 Framework is required for this install, if you do not have it installed, create this as an application as well and add it as a Dependency and it will install it for you as part of this installation. I've added another post on how to add Microsoft Dot Net Framework as an application in SCCM here.

COMMENTS

If you have any questions about this guide, please use our Disqus system below to leave comment and we will get back to you as soon as we can.

Labels: , , , ,

AutoCAD Installation Failures - Error 1606. Could not access network location.
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 to spend time manually installing it.

Having created the AutoCAD deployment share and then building the application into my Software Catalog, the user side installation was failing. I tested the installation manually and I was getting the error as below:


This led me into looking at various solutions but eventually I realised what the problem was...

We have a large number of machines that have split partitions and the user profiles are on the second partition (created and relocated during SCCM OSD process...). Having run the installation on a machine without the split partition I found that this worked perfectly. This proved that the issue was with the registry settings for the user profile location. I checked all the settings and found that I needed to change the following additional settings (this assumes that the user profile is on the D: partition):

 Windows Registry Editor Version 5.00  

 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
 "Common Desktop"="d:\\Users\\Public\\Desktop"  
 "CommonVideo"="d:\\Users\\Public\\Videos"  
 "CommonPictures"="d:\\Users\\Public\\Pictures"  
 "CommonMusic"="d:\\Users\\Public\\Music"  
 "Common Documents"="d:\\Users\\Public\\Documents"  

Having made these changes and rebooting the machine, running the AutoCAD LT 2014 installation from the Software Catalog then worked correctly.

Labels: ,

Autodesk Serial Number Reporting - v3 Release Code
RECOMMENDED UPDATE

We now strongly recommend using a new method to complete this process of Autodesk serial number collection. Please click the link below to go to the full guide for the new method:

Autodesk Serial Number Collection using SCCM

===============================================================

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:

Step by step guide to reporting Autodesk serial numbers

I am now very pleased to announce the release of version 3.0 of the Configuration Item (CI) code and a new report.

We have updated the CI collection script to cover the following:
The new report is now a little more streamlined and will not report NULL values. Also it will tell you if the installation is a Standalone or Network version (boxed or subscription).

You can download the updated codes from our site using the links below:

Autodesk Configuration Item Script v3.1

Autodesk Custom Report v3.1

If you have any problems with this, please feel free to post a comment and I'll help when I can.

We provide all our work for free so your feedback is always welcome.

Labels: ,

AutoCAD Serial Number Reporting - Updated Scripts up to 2013
UPDATE - We now recommend using a new way of collecting Autodesk serial numbers, please see a full guide on the new method by click the link below:

Autodesk Serial Number Collection using SCCM

You may have seen a previous post of mine on how to report on AutoCAD serial numbers using SCCM 2012 here:

Step by Step Guide to Reporting AutoCAD Serial Numbers

Well, this worked up to around AutoCAD 2011 but I've now had the time to update the script to capture up to AutoCAD 2013 and AutoCAD LT 2013 and back to previous versions up to AutoCAD 2000.

You should follow the same process as my previous post but when importing the Configuration Items CAB file, you can now use the link below to update your reporting.

AutoCAD Configuration Items CAB - February 2013

If you have any problems with this, please leave a comment and I'll help when I can.

Labels: , ,

AutoCAD & AutoDesk serial number reporting using SCCM 2012
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 see, you can click on them to enlarge them).

To do this, you will first need to download the Autodesk Serial Number package that I have created.

This can be found here:

Download Package Link

UPDATE! - There is now an updated version of the CI code and report which is available here:

Autodesk Serial Number Reporting v4

Once you have this package, make sure you have unzipped it ready to use.

You are now ready to start configuring your Configuration Manager.

Go into the Administration tab and then go into Client Settings





Right click on Default Client Settings and click Properties

Click on Hardware Inventory and click Set Classes button


Click the Import button


Browse to the AutodeskMofEdit.mof file that you downloaded earlier

You will see the following Import Summary


Click Import button and ensure that you have selected Import both hardware inventory classes and hardware inventory class settings

Once import is complete, you should see the classes in the hardware class list like below:


Then click OK until back to the main console screen.

Once you have successfully imported the hardware class you then need to create the DCM settings, so now go into Assets and Compliance then Configuration Items


Right click on Configuration Items and click Import Configuration Data

Click on the Add button and browse for the CAB file that is in the package that you earlier downloaded called “Autodesk Serial Numbers Configuration Items.cab” and import this file.

If you get a verification message, just click Yes to continue then click ok to go back to the main console.

Then go to Configuration Baselines and right click and click Import Configuration Data.

Add the Autodesk Serial Numbers Configuration Baseline.cab and import using the same process as above.

You can then deploy this baseline to a collection of your choice (I have personally distributed this to All Systems to collect data from all my client machines)

Once this is complete, you then can create the reports to display this gathered information.

To do this go into Report Builder 3.0 on your SQL Server.

Click New Report and then Table or Matrix Wizard


Click Create a dataset and click Next


Keep the default dataset that appears and click Next

If prompted for a username and password, ensure that you use an SQL administrator account

Click Edit as text:


In the text box, copy and paste the code from the file AutoDeskCustomReport.txt that you downloaded within the package earlier, then click Next.

Then you need to build the layout and data of the report, take Computer_name, AutoCAD_version, AutoCAD_rel and drag them into Row Groups

Then drag AutoCAD_Serial_Number into Values as below and then click Next



On the layout, make sure you untick Show subtotals and grand totals and also untick Expand/Collapse Groups then click Next

Then select a colour scheme of your choice and click Finish

You then need to save this report to your Configuration Manager 2012 server by clicking the save icon at the top left and then save it wherever you save your custom reports.

If you then run the saved report, you should start to see the information that you require.

A big note for the end of this guide is that this information relies on getting into the Configuration Manager 2012 database by using DCM and hardware inventory. This means it is at the mercy of your scheduled run times for both DCM and hardware – the default in Configuration Manager 2012 is 3 days for each one, so if you have not changed this information then it could take up to a week to see any data in the report – you can always change your DCM schedules and hardware scan schedules (I’ve changed both mine to 3 hours just to get some data into the database) but this choice is yours.

Please leave comments on this post if you have any questions or if you have used this successfully as it would be nice to hear back if this has worked for others.

Labels: , ,

Step by step guide to creating a custom SCCM 2007 report to retrieve Autodesk & AutoCAD serial licence numbers
UPDATE: Please note that we do now recommend a new way of collecting Autodesk serial number information. So please click the link below to our up to date post about this topic:

Autodesk Serial Number Collection using SCCM

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.

To do this, we will be using DCM vbscripts to run on the clients and then using a custom script to create the report to produce the serial number information we want.

First of all, let me just make it clear that this is information I have gathered from much internet searching and I am not the one who has written the DCM VBscript to populate the database with the decrypted serial information - so I cannot take the praise for that! But I have collated all this information and written the custom script reports to help others with a full step by step guide which hopefully will help others.

You will need to download the below zip file which contains all the scripts that we are going to use in this guide:


DOWNLOAD

Download Autodesk Scripts

Then you need to create the DCM part. So login to your server and into the console and do the following:

1. Go to DCM and then to the Configuration Items

2. Create a new General Configuration Item and name it AutoCAD Serial Numbers and then click Next
3. You do not need any objects so just click Next
4. Highlight Settings then click New and then Script
5. For the Display Name type in AutoCAD Serial Numbers
6. Make sure the script language is set to VBScript
7. Then copy and paste the downloaded “AutoDeskDCMScript.txt” script into the script box
8. Click the Validation tab and change the Severity to “Information – no Windows Event Message”
9. Click OK and then select All Windows Platforms and complete the wizard

You then need to create the Baseline to apply this script to all your clients.


1. Go to DCM and then to the Configuration Baselines

2. Create a new Configuration Baseline
3. Name it Serial Collector
4. Add the Configuration Item to the “These applications and general configuration items are required and must be properly configured” and click Finish
5. Right click the DCM Baseline you have just created and assign it to the All Systems collection and set the schedule

Once this is complete, you then need to edit the MOF file on your Primary server.


1. Go to your Primary server and go to the following location


• C:\Program Files\Microsoft Configuration Manager\inboxes\clifiles.src\hinv\ sms_def.mof

2. Open the file and at the end copy and paste the “AutodeskMOFEdit.txt” contents from the downloaded file, then save the MOF file.

The final part to get this working is to create a custom report.


1. Go to Reporting and then Reports

2. Right click and select New and then Report
3. Name the Report “AutoCAD Serials”
4. Select a Category
5. Click Edit SQL Statement
6. Remove the script that is there and replace it with the contents of “AutoDeskCustomReport.txt”
7. Complete the wizard

You are now ready to have your clients report back to your server and you can then run this custom report and it should give you all the information you require.


COMMENTS

If you have any questions, please comment and please post back your findings using this and obviously feel free to share the link to this site to help others.

Labels: , ,