Application of the Week – AutoCAD 2020 (Part 2)

Application of the week > Application of the Week – AutoCAD 2020 (Part 2)

In ‘Application of the Week – AutoCAD 2020 (Part 1)‘ I’ve described the preparation of an Administrative Image for AutoCAD 2020. How to create a Package to install AutoCAD 2020 using this Deployment Image and how to use Credential Store credentials to access the network share when the setup is run in the ‘Device’ context.

In this blog I will share a few tips and tricks to further customize the deployment using the AutoCAD2020.ini file which is used by the /I switch in our AutoCAD package in Liquit Workspace:

This AutoCAD2020.ini is located in the \Img directory of our Deployment Image.

LOG=%tmp%\Autodesk AutoCAD 2020 Setup.log

If you want to configure logging differently, configure LOG, NETWORK_LOGPATH and NETWORK_LOGGING.
If you want to skip the desktop shortcut creation, in order to provide a Liquit Workspace’ intelligent icon, set CREATE_DESKTOP_SHORTCUT to NO.
If you want to change the licensing, update SERIALNUMBER= and PRODKEY= accordingly.


If there’s anything you need to change in the acad.msi, use the transform file configured for CONFIG_TRANSFORM= where ‘acad-AutoCAD2020.mst’ is the transform file provided by default. You can load this transform in your favorite MSI editor and then apply additional changes:

LOG=%tmp%\Autodesk AutoCAD 2020 PSPack Install.log
LAUNCH_SHORTCUT=AutoCAD 2020 - English\AutoCAD 2020 - English.lnk

PREREQUISITE has a value which lists are prerequisites being installed. You can remove components accordingy, when you already have Managed Packages for and deployed these prerequisites. Prerequisites like Microsoft Visual C++ Runtime 2012, 2017 or .NET Framework 4.

This will prevent the AutoCAD setup from running the setups for these prerequisites, which could downgrade or break current installations.


In AutoCAD2020.ini you will find many sections like this one:

LOG=%tmp%\Autodesk AutoCAD 2020 Private Install.log

to change the location and names of different logfiles.

In part 3 of this blog I will describe how to create a package in Liquit Workspace to launch AutoCAD after it has been deployed.

About the author