IBM Support

How to install (deploy) the Controller client silently (without user input)

How To


Customer's I.T. department would like to install the Controller client on an end user's PC/laptop.

They would like to automate this process as much as possible, by pre-configuring the installation parameters.
- In other words, there would be no 'install wizard' during which the user is prompted for choices (such as the name of the Controller application server).

How can this be achieved?


The standard Controller client installation instructions are explained inside separate IBM Technote #1965917.
  • In those instructions, the users will have to manually type in values such as WSS URL:
However, customer wants to deploy the Controller client (to and end user's PC/laptop) without the need for the user to go through an 'install wizard' where they choose configurable options (such as the name of the Controller application server's website).
  • In other words, the customer is looking for a method to automatically pass the above parameters into the installation routine.


These instructions are based on Controller 10.4.0.
  • The instructions may need to be amended for different versions of Controller.


Trigger the installation routine using a command similar to:
msiexec.exe /i CCRLocalClient64.msi WSSURL="http://myserver/ibmcognos/controllerserver" /q

    Additional Information

    More Information on installation parameters:
    • CCRLocalClient64.msi - Almost all customers should use this installation file.
      • The alternative file ("CCRLocalClient32.msi") is only to be used for 32-bit Windows operating systems (extremely rare)
      • The file can be located on the Controller application server in a location similar to: C:\Program Files\IBM\cognos\ccr_64\webcontent\ccr
    • WSSURL - Configure this for your Controller application server's name
    • /q - This causes the installation to be 'quiet'
    Advanced example
    The following script is a real-life example where the customer wanted to achieve some extra changes (in addition to installing the Controller client):
    • Force .NET applications (like Controller client) to use TLS 1.2
    • Import a self-certified SSL certificate into the Controller client's JAVA store.
    @echo off
    cd "C:\temp"
    msiexec /i ccrlocalclient64.msi /passive WSSURL=""
    REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1
    REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1
    cd "C:\Program Files\IBM\IBM Cognos Controller Local Client\Integration\jre\bin"
    keytool -import -trustcacerts -storepass changeit -noprompt -alias CognosController -file "C:\temp\Java Cert\mycertificate.cer" -keystore "C:\Program Files\IBM\IBM Cognos Controller Local Client\Integration\jre\lib\security\cacerts"

    Document Location


    [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9S6B","label":"IBM Cognos Controller"},"Component":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"10.4.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

    Document Information

    Modified date:
    02 July 2019