I'm currently working on a new book as a follow-up on the previous edition called "The AutoCAD Network Administrator's Bible, 2012 Edition" to focus on changes provided in AutoCAD 2012. This is an excerpt.
Because Autodesk is still ignoring me (story of my life), the situation with regard to using SCCM to install a network deployment package of AutoCAD 2012 is still hampered by DirectX and also .NET 4.0. That's life. There are ways around these road bumps. First, I will run through packaging the custom DirectX bundle. .NET 4.0 is easy to push with SCCM, but it has to be done before you deploy the AutoCAD 2012 deployment package. Otherwise it will crash and burn but still report back "Success!" and laugh at you.
To compile the DirectX component installer package for AutoCAD 2012 using Wise Package Studio version 8.0. WPS 7.0 is pretty much the same (8.0 is essentially 7.0 SP4 anyway), and these idiotic instructions should work the same. The process for InstallShield / AdminStudio is roughly the same (you bundle up the files, drop them on the client and run the install with /SILENT and tell it to ignore the exit code). Ok, that was the spoiler, so you can skip the rest and do it yourself, but if you want more detail, keep reading...
- Copy the “DirectX” folder from the AutoCAD 2012 installation source (it can be found under “\3rdParty\DirectX”) and place the copy somewhere like C:\Acad2012DX. The files that are included are:
Create a Wise Project
1. Open Wise Package Studio
2. Click File / New Project
3. Fill-out the Project information and Save it
4. In the left-hand panel, under the “Projects” tab, select “Run” beside “Create Package”
5. If you have a Wise Share Point server environment, select the top “Change” button and select “Use configuration file on share point”, click OK
6. Click “Next”
7. Select “Snapshot”, click “Next”
8. If prompted to choose “Use initial scan” or “Rerun the initial scan” choose the latter, click “Next”
9. Click “Next” to begin the snapshot scan
10. On the “Execute Installation” page, leave all entries blank and click “Next”
11. Click “Next” again to end the snapshot scan
12. On the “Inclusions” page, make sure nothing is included (Files, Registry, INI, Shortcuts). If any items are captured, select them and click “Exclude” to remove them. Click “Next”
13. On the “Exclusions” page, click “Next”
14. On the “Finish” page, confirm the package information and click “Finish”
After the base project package is created it will return to the Project menu. Click “Run” next to “Edit package”
- When the “Windows Installer Editor” window appears, click “Files” under “Feature Details”
- In the lower left-hand panel, under “Destination Computer”, expand to select \Windows\Temp (highlight the folder)
- In the upper panel, expand the drive to access the folder where you placed a copy of the DirectX files (e.g. “C:\Acad2012DX”) and select that folder (highlight it)
- Click the “Add Contents” button, confirm and click OK
- Save the Project (press CTRL+S)
- Click the “MSI Script” tab (at bottom)
- Select the “Execute Deferred” tab (bottom right)
- Scroll to the bottom of the script editor and click (once) on the “InstallFinalize” line
- In the left-hand “Actions” panel, double-click “Execute Program From Installed Files”
- Set the Custom Action Properties:
- Custom Action Name: “InstallDirectX”
- Executable File: (select DXSETUP.EXE)
- Command Line Arguments: /SILENT
- Click the “Properties” tab
- Set Processing to “Synchronous, Ignore exit code”
- Click OK
- The new line should read “Execute Installed Program DXSETUP.exe Command Line /SILENT (InstallDirectx)” and appear just above the “InstallFinalize” line. If you insert it in the wrong place, use CTRL+UP or CTRL+DOWN to move the line up or down in the editor.
- Save the Project
- Compile the Package (press F7)
Deploying it with SCCM
You have two options, maybe more (but it's Friday and I'm too lazy to think of more than two, so, that's pretty much the deal for now):
- Grab the .MSI file and stuff it into SCCM as a new package and advertise it at the Collection which contains the computers that will later on receive AutoCAD 2012 - OR...
- Make a .CMD script to run your new DirectX .MSI package and then run the AutoCAD 2012 deployment installation.
As for .NET 4.0
Copy the folder from the AutoCAD 2012 installation media that contains the .NET 4.0 installer files. This resides under "\3rdParty\NET\4\wcu\dotNetFramework" and paste it into a folder on your SCCM package source share folder structure
Create a new SCCM package that points to that new folder.
Create a new program within that package for x86 and another for x64 (if needed) using one of the commands below (depending on 32 or 64 bit)
- dotNetFx40_Full_setup.exe /q /x86 /norestart /lang:ENU
- dotNetFx40_Full_setup.exe /q /x64 /norestart /lang:ENU
Set the program to suppress notifications (advanced tab) and run "whether or not user is logged on" (environment tab)
Advertise it to the same collection (ahead of the AutoCAD 2012 deployment) - OR - drop this into a script and make it all a single SCCM package along with the DirectX installer. You might want to add a line of code to check if .NET 4.0 is already installed and skip the installation of .NET unless it hasn't been installed. A pretty good way to check for .NET 4.0 is
if exist "%windir%\Microsoft.NET\Framework\v40.30319" (
echo dotnet 4.0 is installed
echo dotnet 4.0 is installed
) else (
echo dotnet 4.0 is not installed