×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

BMC Client Management 20.08 ... Installing Installing BMC Client Management on-premises Installing on-premises on Windows and installation options

Installing silently

The BMC Client Management may also be installed via the command line by using the console.msi executable file. This file is located in the installation or upgrade directory, for example, 

..\BCM_12.8.0_190124r_upgrade_win64\master\master_winx64.zip\upgrade\files.zip\ui\console\ install\x64\MSIConsole_x64.zip\.

Related topics

Launching the console via command line

Prerequisites

  • SQL Server/SQL Server Express version 2014/2016/2019 is installed.
  • The bcmdb database is created with tablespaces.

To install the master via command line

To install the master via the command line, enter the following command and specify the options:

msiexec /i numara-footprints-asset-core-master.msi LICENSETYPE=2 LICENSEPATH="C:\toto.xml" ALLUSERS=1 INSTALLDIR="C:\Program Files\BMC Software\Client Management\Master" PORT=1610 VIRTUALHOSTPORT=1611 SSL=2 SERVERNAME=SRV-DB2 DBNAME=bcmdb SERVERLOGIN=sa SERVERPASSWORD=DbMaster@06 OUTOFBOXLANG=francais SERVICENAME="Client Management" SERVICELOCK=1 UNLOCKPASSWORD="unlockpass" DBDRIVER="Driver={SQL Server};Server=SRV-DB2;Database=bcmdb" /qn /l "C:\Install.log"

To install the console via command line

To install the console via the command line, enter the following command and specify the options:

msiexec /i numara-footprints-asset-core-console.msi INSTALLDIR='<ConsoleInstallationDirectory>' ALLUSERS=2 DESKSHORTCUT=1 SSL=1

The following table explains each command in detail.

CommandDescription
LICENSETYPE This  option determines the Windows license type. The following values are possible:
  • 1: Evaluation license
  • 2: Use a license file. In this case, you must specify the LICENSEPATH command.
LICENSEPATH 

This option defines the path to the license file. Use this command only if you have set the LICENSETYPE value to 2.

ALLUSERS This option defines where the configuration information of the installed console/master is stored. The following values are possible:
  • ALLUSERS='': Determines a per-user installation by using the folders in the user's personal profile. Administrator rights are not required for this option.
  • ALLUSERS=1: Specifies a per-device installation by using the folders in the All Users profile. Administrator rights are required for this option.
  • ALLUSERS=2: Offers two possibilities:
    • Specifies a per-device installation by using the folders in the All Users profile, if the installation is launched by a user with administrator rights.
    • Specifies a per-user installation by using the folders in the user's personal profile, if the installation is launched by a user with only user rights.
INSTALLDIR 

This option defines the installation directory of the console/master. If this optional command is not used, the default directory C:/Program Files/BMC Software/Client Management/console or C:\Program Files\BMC Software\Client Management\Master is used.

DESKSHORTCUT 

This option defines if a shortcut to the console/master is to be created on the desktop. By default, the shortcut is created. If the value is set to 0, no shortcut is created.

SSL 

This option defines if the communication between the console and the master agent is secured. By default, this option is activated (1). The following values are possible:

  • 1: No. The agent accepts both secure and non-secure communication, however it sends only non-secure communications.: No. The agent accepts both secure and non secure communication, however it sends only non-secure communications.
  • 2: Securized Send, Receive Both. The agent accepts both secure and non-secure communication, however it sends only secure communications.
  • 3: Yes. The agent only communicates in secure mode, that is, it only receives and sends secure communication.
  • 4: Yes with mutual authentication. The agents communicate in secure mode and in addition authenticate each other via SSL.
PORT This option defines the port number for the client agent communication.
VIRTUALHOSTPORT This is the HTTP port used by the Java console and the web console. The default value is 1611.
SERVERNAME This option defines the remote server name on which the master is located. 
DBNAME This option defines the name of the database.
SERVERLOGIN This option defines the user name for logging in to the server.
SERVERPASSWORD This option defines the password for logging in to the server.
OUTOFBOXLANG 

This option defines the language of the objects created by the BCM outofbox. The following values are possible:

  • american
  • brasileiro
  • deutsch
  • espanol
  • francais
  • japanese
SERVICENAME This option defines the service name.
SERVICELOCK This option locks the Client Management Agent service.
UNLOCKPASSWORD This option defines the password to be used in order to unlock the service.
DBDRIVER 

This is the driver connection chain used for the database connection.

Examples:

    • Driver={SQL Server};Server=MyServerName;Database=myDatabaseName;Uid=myUsername;Pwd=myPassword
    • Driver={Oracle ODBC Driver};Dbq=myDBName;Uid=myUsername;Pwd=myPassword
Was this page helpful? Yes No Submitting... Thank you
Last modified by Darshana Bhangare on Apr 17, 2020

Comments

Log in or register to comment.

Installing the master and console on different devices
Installing on-premises on Linux and installation options
© Copyright 2013 - 2021 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.