Silent Installation

Overview

Applies to releases on or after 2025.06.30 (Fathom 14, Arrow 11, Impulse 11, xStream 4).

Silent installation refers to the capability of Systems Admins to push installations and updates to end-user machines without any user input. Silent installation happens in the background on the PC without any GUI or interface pop-ups. It is useful for mass-deployment of software versions in enterprise environments with hundreds or thousands of engineers who need the software installed. Silent installation commands can be useful for tools such as company software centers, Microsoft Intune, SCCM, RMM tools, Windows Command Prompt, batch files (*.bat), PowerShell scripts, etc. Silent installation involves passing parameters into an *.msi Windows installer file that is embedded within our *.exe installer.

Note: Fathom, Arrow, Impulse, and xStream can be installed on an unlimited number of user machines, but the number of concurrent users is dictated by the number of seats which were purchased on the license.

Full installation setup consists of the following steps:

  1. Ensure the requirements listed below are met

  2. Create your silent install command following our template

  3. Activating the eLicense

 

Requirements

  • License Number - This is a 9 or 10-digit number provided on the receipt of purchase in the format of XXXXX-XXXXX (the hyphen is part of the license number). Note: The License Numbers are product-specific and version-specific. For example, a Fathom 14 installer will reject a Fathom 13 License Number. Make sure you have the correct License Number from the software purchase receipt that applies to the product and version that is being installed.

  • Registration.txt File - This is a text file containing the required 32-digit eLicense Activation Code, and it is provided with the receipt of purchase.

  • Internet Connection - The PC must have access to https://my.nalpeiron.com (IP address 20.237.110.18, on port 443). Ensure it is not blocked by company firewalls.

  • Administrator Privileges - The application installation will require admin rights on the PC. Scripts must be executed as admin or by the SYSTEM account.

 

Template Command

FthFull.exe /S /v/qn /v"AGREETOLICENSE=yes" /v"USERNAME=MyUser" /v"COMPANYNAME=MyCompany" /v"SERIALNUM=XXXXX-XXXXX"

The above command is a basic template where certain parameters should be replaced with relevant information for your company. The command can be customized using the info below:

  • FthFull.exe - This is the name of the installer *.exe and should be replaced with the relevant product being installed. For example, the Arrow product would have a different file name such as AroFull.exe. If you renamed the installer then be sure to use the appropriate file name.

  • /S - This parameter tells the command to install "silently", meaning no GUI or pop-ups will be present.

  • /v/qn - This parameter tells the *.exe installer to pass the silent installation option into the embedded *.msi.

  • /v"PARAMETER" - Defines various custom parameters that are passed into the embedded *.msi.

Required Parameters

  • v/"AGREETOLICENSE=yes" - Can be yes or no, and corresponds to the GUI screen where you accept the License Agreement. By setting this parameter to "yes" you are agreeing to the Terms & Conditions in our License Agreement. If "no" is entered, then the product will not be installed.

  • v/"USERNAME=MyUser" - Replace "MyUser" with the desired user name (no space characters), typically the First & Last name of the engineer. In mass-deployment, you can simply enter the same value as the Company Name below.

  • v/"COMPANYNAME=MyCompany" - Replace "MyCompany" with the desired company name (no space characters).

  • v/"SERIALNUM=XXXXX-XXXXX" - Replace "XXXXX-XXXXX" with the nine or ten digit license number for the product being installed. Note: The License Numbers are product-specific and version-specific. For example, a Fathom 14 installer will reject a Fathom 13 License Number. Make sure you have the correct License Number from the software purchase receipt that applies to the product and version that is being installed.

Optional Parameters

  • v/"INSTALLDIR=C:\Program Files (x86)\Datacor\[PRODUCT NAME AND VERSION]" - The path in which the product will be installed. Default paths for the products are located in the Program Files (x86)\Datacor directory since the apps are 32-bit.

  • v/"SETUP_TYPE=Typical" - Represents the installation type. "Typical" represents the normal local install. "Network" represents the advanced server install where further setup will be required on the client machines.

 

Activating the eLicense

The eLicense is set up through a separate file called Registration.txt that is external from the installer. For completeness, you will need to create this file and script the placement in the correct directory. If you don't place this file on each user machine then the users will be prompted with an activation window where they can paste the 32-digit code themselves. For a truly seamless end-user experience you can set up this file ahead of time.

  1. Create a new text file named 'Registration.txt'. If the file is misspelled it won't work.

  2. Paste the 32-digit eLicense Activation Code inside on line 1 and save. This code can be found on the software purchase receipt.

  3. Script the placement of the Registration.txt file into C:\ProgramData\Datacor\Licensing for each machine that needs access. The ProgramData\Datacor directory will exists from running the installer, but the "Licensing" folder will need to be created.

Note: In order to use the ProgramData\Datacor\Licensing folder, you must be using 2025.08.29 releases or later. Prior releases will not recognize this folder.

Note: The actual end destination of the Registration.txt file is C:\Users\username\AppData\Roaming\Datacor\Licensing because the file can have user-specific settings that require write permission. Our applications will automatically copy the file from C:\ProgramData\Datacor\Licensing to user appdata if it sees that it doesn't exist there. This is to reduce the amount of manual scripting that would be required by IT Admins to disseminate this file to all user folders. Furthermore, in the case of shared lab computers with multiple logins, the initial placement in ProgramData is sufficient for all users as our apps will automatically copy it to each user appdata. For legacy support, our applications will also search and attempt to copy the Registration.txt from C:\ProgramData\Applied Flow Technology or the application installation folder (C:\Program Files (x86)\Datacor\Fathom 14) if it is not present in either the appdata or ProgramData\Datacor\Licensing folder.