Download and install files from a filepath batch - consider
The sample batch files in this topic can be used as templates for installing Autodesk products in typical configurations for stand-alone or network licensed versions. Just copy the sample batch file and replace variables with the data values for the product being installed.
Note: Batch file examples are shown in multiple lines for easier reading, but in practice, each file should be written as a single line of instructions.
Batch File Placeholder Terms
The following placeholder terms are used in the example batch files. When creating your batch file, these terms should be replaced with the appropriate information as described below.
- <mediaDriveLetter> is the drive letter where the media is mounted or the setup.exe file is stored
- Install options used here include /t (setup is executed by script) and /qb (display a basic user interface). Others such as /w (log nonfatal warnings) are defined for Microsoft Msiexec command line, and documented on the MS TechNet website.
- <Product ID> is the abbreviated name of the product being installed, such as ACM_MAIN for AutoCAD Mechanical, MAX for 3ds Max, or INVENTOR. This name can be found inside square brackets in the Product section of the Setup.ini file. Example: [ACAD_MAIN] PRODUCT_NAME=Autodesk® AutoCAD® 2016
- INSTALLDIR=“%programFiles%\Autodesk\” is an optional parameter, and its use is not recommended; it specifies a different installation directory from the default location, and this can cause problems for product operations.
- <Product Name> is the name of the product installation directory, such as Inventor 2016.
- <SerialPrefix> is the first 3 digits of the serial number
- <SerialPostfix> is the last 8 digits of the serial number
- <ProdKey> is the Product Key
- <lang> is the IETF language tag, for example en-US for English-United States
- <eula_lang> is the ISO 3166–1 alpha–2 standard for the country for example US = United States
- ACADSTANDALONENETWORKTYPE identifies the type of license being installed. It has three possible values: 0 for both network and stand-alone, 1 for stand-alone, and 3 for network.
Return to Top
Stand-Alone License Example
Return to Top
Single Server Network License Example
Note: <FlexLicenseServer> is the network license server.
Return to Top
Distributed Server Network License Example
Note: <server1> thru <serverN> are valid network license servers.
Return to Top\\
Redundant Server Network License Example
Note: <server1> thru <server3> are valid network license servers with redundant licenses.
Return to Top
Suite Installation Example
A separate code block is required in the batch file for each product being installed. Each block includes the Product ID for one of the products being installed, but the same suite serial number and product key are used for all products. The following sample represents the batch file for stand-alone installation of three products.
Return to Top
-