top of page

Automate Abaqus Installation with Silent Mode

  • Aug 8
  • 3 min read

Updated: Sep 25

IT professional running a silent command-line installation process on a desktop computer in a modern office environment.
Automating the Abaqus installation using command line.

Installing Abaqus manually on multiple systems is time-consuming and inconsistent. Whether you're setting up lab environments, refreshing engineering workstations, or managing HPC clusters, silent installation allows you to automate the process with zero user interaction, ensuring repeatability and control. 



Download the Correct Release and Hot Fix

Before you begin, make sure you’re using the exact version of Abaqus that you plan to install silently. 

  • Visit https://software.3ds.com and log in with your 3DS Passport. 

  • Go to SIMULIA → SIMULIA Abaqus, Isight, fe-safe, Tosca. 

  • Download the relevant GA (General Availability) or FD (Fix Pack) version. 

 

The release version must match the one used to create your response file. Some Fix Packs are delivered as complete rebuilt installers. In those cases, you’ll need to generate a new response file based on that updated installer package. 



Generate a Response File 

To run a silent installation, you first need to create a response file that captures your preferred installation configuration. This is done by running a normal Abaqus installation (using the GUI or TUI interface) and completing all setup steps manually. Your inputs, including install paths, selected products, license type, and feature options, will be saved automatically. 


After installation, the response file is usually located in: 

InstallDirectory/InstallData/UserIntentions_CODE.xml 


Keep in mind that this file is version-specific, operating system–specific, and tied to the type of installation media used. Important note, this method applies to SIMULIA Established Products (Abaqus, Isight, Tosca, fe-safe). It does not apply to 3DEXPERIENCE installations managed through Compass or Platform Manager. 



Know Which Response File Applies to Your Setup 

Different Abaqus media types generate different response files. Here’s how they’re typically named and where they’re stored: 

  • Assembly or Suite media: These create files like “UserIntentions_AM_SIM_Abaqus_Extend...” and store them in the temp folder, on Windows that’s usually under AppData\Local\Temp; on Linux, it's /tmp. 

  • CODE media: The response file is named “UserIntentions_CODE.xml” and saved in the InstallData directory of your installation folder. 

  • CAA media: These files are named either “UserIntentions_CAA.xml” or “UserIntentions_CAA_Additional.xml” and are also stored in InstallData. 

  • Hot Fix installations: The files are version-specific, e.g., “UserIntentions_CODE_422.4.xml” or “UserIntentions_CAA_422.4.xml,” and stored in the same InstallData folder. 


Important: Hot Fix response files are not saved in the temp folder. They're written directly to the installation directory. 



Run the Silent Installer 

Once you have the correct response file, you can trigger the silent installation via command line. 


For Windows, use: StartTUI.exe -silent UserIntentions_CODE.xml 

For Linux, use: StartTUI.sh -silent UserIntentions_CODE.xml 


Make sure you're using the appropriate StartTUI executable from the same media that generated the response file. For example, if your response file came from the Suite installer, use the Suite’s StartTUI file. On newer systems like Windows 11 or RHEL 9, certain security or system policies (e.g. UAC, SELinux) can interfere with the installer. Always test your setup on a reference machine before scaling up deployment. 



Check Your Installation Log 

After the silent install runs, verify that the process completed successfully. The installation logs are saved in the folder: InstallDirectory/InstallData/log/. If the installation fails or is interrupted, this folder will contain error messages and detailed status reports that can help with troubleshooting. 



Why Silent Installation is Worth Using 

This method saves time, reduces manual errors, and ensures consistency across systems. It’s especially effective in the following scenarios: 

  • Rolling out Abaqus across company-wide engineering desktops 

  • Preparing university lab computers with identical setups 

  • Installing multiple SIMULIA products in one go using Suite media 

  • Automating updates or refreshes in HPC environments 

 

This guide is based on Dassault Systèmes Knowledge Base article QA00000051236. 

 


Need Help with Silent Installations?

If you're a 4RealSim customer and experiencing issues with silent mode installations, response file creation, or identifying the correct installer media, we're here to assist. Whether you’re managing company-wide rollouts or HPC environments, our team can help streamline the process. You can contact us by filling out the contact form or by emailing us directly at sales@4realsim.com for tailored support and expert advice.

Comments


bottom of page