Silent Installation

This topic contains information relating to installing or uninstalling CM4D without the installer user interface via command line, referred to as a 'silent' or 'quiet' installation. This installation option is compatible with CM4D v24 and up.

Some recommendations:

  • Make sure all the data has been processed and nothing is waiting in any queue
  • Stop all CM4D services
  • Backup Settings files and INI file

Download Create Machine ID powershell script

Installation Commands

Option Description Command
Disable Reboot Prevents the automatic reboot that is triggered when the installation is finished. A manual system reboot is highly recommended.

/norestart

Logging Generates an installation log file.
Relative Path The log file is created wherever the installer is located.

/L*V "example.log"

Absolute Path The log file is created in the location specified by the path.

/L*V "C:\installs\example.log"

Service User Set the type and credentials of the user that will be configured to run the CM4D Services, such as Scheduler or Results.
Local System Installs the CM4D services with the default 'Local System' user. This is equivalent to the 'Quick Install' method during manual installation.

QUICK_INSTALL_OR_INVALIDUSER="1"

Domain User Install the CM4D services with a Domain user account by providing a user and password, with the user name including the domain name.

CM4D_SERVICE_USER="domain\username" CM4D_SERVICE_USER_PASS="password"

Windows User Install the CM4D services with a local Windows user account by providing a user and password.

If the user does not exist at the time the silent installation is executed, the services will not install correctly.

CM4D_SERVICE_USER=".\cm4dservice" CM4D_SERVICE_USER_PASS="password"

User Interface Runs as a silent installation with no user interface (GUI).

/qn

Explanation:

QUICK_INSTALL_OR_INVALIDUSER="1"   - needs to be set to 1 to tell installer to install services with Default user which is Local System

/qn    -  Quite no interface

/norestart – with GUI we force Restart by pop up Window at the end of installation to make sure that all gets installed correctly with /qn it does reboot without warning and we found this annoying while testing. So it is still recommended to do a reboot after installation but SCCM might have less painful way to ask for a reboot than what it does if you do not use /norestart

/L*V “example.log” – will generate install log next to the executable you can use absolute path if you want it somewhere else

Option 2:

In this option you can set the Services user during the installation by parameters :

For domain user:

CM4D_SERVICE_USER="ats-global\asleis" CM4D_SERVICE_USER_PASS="password" .

For local user

CM4D_SERVICE_USER=".\asleis" CM4D_SERVICE_USER_PASS="password"

The user must exist before the installation is executed.

/x  – means uninstallation

// tells exe bootstrapper to call the MSI inside it

Install Example 1 - Default User

"ATS CM4D Server 64 Bit v24.x.xxxxx.x.exe" QUICK_INSTALL_OR_INVALIDUSER="1"  /qn /norestart /L*V "example.log"

Install Example 2 - Domain User

"ATS CM4D Server 64 Bit v24.x.xxxxx.x.exe" CM4D_SERVICE_USER="ats-global\hmiyazaki" CM4D_SERVICE_USER_PASS="password" /qn /norestart /L*V "example.log"

Uninstallation Commands

Option Description Command
Disable Reboot Prevents the automatic reboot that is triggered when the uninstall is finished. A manual system reboot is highly recommended.

/norestart

Logging Generates a log file with information relating to the uninstallation.
Relative Path The log file is created wherever the installer is located.

/L*V "example.log"

Absolute Path The log file is created in the location specified by the path.

/L*V "C:\installs\example.log"

Uninstall Executes a silent uninstall.

/x

Uninstall Instructs the bootstrapper to call the MSI inside the EXE to initiate the uninstall protocol.

//

User Interface Runs as a silent uninstallation with no user interface (GUI).

/qn

Uninstall Example 1

"ATS CM4D Server 64 Bit v24.x.xxxxx.x.exe" /x // /qn /norestart /l*v “install.log”

Explanation:

/x – means uninstallation

// tells exe bootstrapper to call the MSI inside it

/qn – quiet no GUI

/L*V “example.log” – will generate install log next to the executable you can use absolute path if you want it somewhere else

Example Powershell Script

 


Can we improve this topic?