Microsoft Deployment Toolkit (MDT) 2010 is a FREE product that is aimed at helping System Administrators prepare and deploy custom operating system installations (images). I’m not going to explain MDT, WAIK or WDS here. There are too many other sites, books, and videos that do a great job of that. I don’t need to add any more noise there.
If you have network license AutoCAD clients and a network deployment share, you already know how that can save time doing repeated installations. You may also know how much it helps when pushing installations via SCCM 2007 (or similar products). Maybe you’ve tried bundling AutoCAD into your operating system image process but are using Ghost or some other snapshot process and find it less than ideal. Well, MDT not only provides an easier option, it eliminates much of the headache incurred with push installations.
For starters, MDT uses a sequential process to perform tasks (hence “task sequences”). Rather than running entirely under an unattended SYSTEM context with no UI, it runs under a user context (typically), so most of the prerequisite tasks of the deployment work just fine (unlike trying to push with SCCM, where the .NET Framework 4, and DirectX component steps fail). So you can run the default installation and simply add the "/W" parameter to use it with MDT 2010.
You may have better luck than I’ve had with using a “thin” image process and trying to install .NET Framework 4 as a task sequence package instead of going with a “thick” or “hybrid” client build*. In my experience, the .NET 4 installation via MDT task sequence never works. But you may be blessed. My approach is to include .NET components in the base image via a reference capture. It is crucial to have .NET 4 installed before attempting to install AutoCAD 2012 via an automated/unattended process or it will fail.
I only use network license deployments of AutoCAD when installing via SCCM or MDT. I do not ever recommend installing standalone/individual licenses
Build your AutoCAD 2012 deployment share ON the server where the MDT package will refer clients to (this works much better than building it elsewhere and then moving it and editing the deployment configuration INI files)
Configure permissions on the deployment share to suit the user context of the MDT installation (if needed)
Right-click the AutoCAD 2012 installation shortcut in the UNC folder (e.g. Acad2012.lnk), select Properties
Copy the “Target” string contents
Click Cancel to close the properties dialog form
Open the MDT Workbench, expand the Deployment share, select Applications
Add a new Application to the MDT workbench deployment group
Option: Application without source files or elsewhere on the network
Right-click the Deployment Share in MDT Workbench and select “Update Deployment Share”
Assuming the rest of your MDT deployment share is configured, and you've already generated a suitable Boot WIM and Boot ISO file set, you should now be ready to start deploying AutoCAD 2012 with your images.
1.If you discover (like I have) that you also need to install the DirectX components ahead of the AutoCAD deployment installation, you can add the Acad2012DX.msi package I’ve posted and set a Dependency within the AutoCAD 2012 application entry so it runs the DirectX installer first. If you do this, click “Hide this application in the Deployment Wizard” from within the MDT application properties for the Acad2012DX application item.
2.A return code of 259 from the AutoCAD installation can be ignored. I have not seen, heard or experienced any detrimental effects after that has occurred.
3.Because there is NO OPTION to disable desktop shortcuts for Design Review 2012 or Inventor Fusion 2012 via the Deployment Wizard configuration, you will have to resort to some trickery if you are required to keep shortcuts OFF of the standard desktop. My trickery is to add DEL commands to a script that wraps the main installation.
4.If you choose to enable the network log option, keep these points in mind:
a.The UNC path to the logs needs to have appropriate ACL and Share permissions granted to allow the remote installation context to make updates to the folder contents (log file)
b.It tracks the entire deployment bundle, but won’t be updated on the network share until the end of the installation process.
c. If the connection fails before the installation completes, the only trace of a partial installation will be in the client logs.
d. The network log is cummulative. It grows with each client installation. You may want to back it up, rename or delete it occassionally to recover space.
5.Why does Design Review 2012 get a “Autodesk” prefix, while Inventor Fusion 2012 does not? Consistency is important.
*terms borrowed from Johan Arwidmark and Mikael Nystrom of TrueSec (www.truesec.com) - geniuses on the topic of Windows deployment automation
·MDT 2010 Update 1 with WAIK 7
·32-bit Windows 7 client Deployment Image with .NET 4 included (sysprep’d from ref computer)
·New install (not a refresh, upgrade or replacement)
Paste the following code into Notepad…
TITLE Installing AutoCAD 2012
echo installing AutoCAD 2012...
echo %DATE% %TIME% installing autocad 2012 from network deployment >%XLOG%
rem beware of word-wrapping below. should be on one line...