Silently upgrading Windows agents

You can upgrade the RSCD agent silently. To silently upgrade one or more RSCD agents on Windows systems, use a TrueSight Server Automation File Deploy Job to deploy the RSCD agent installation program for the version to which you want to upgrade. 

The deployment copies the installation program to any target servers you specify and then silently executes the program using the existing installation settings.

Notes

  • If you previously installed a 32-bit Windows agent on a 64-bit platform, you cannot simply upgrade to a 64-bit Windows agent. You must first uninstall the old 32-bit version of the agent before you can successfully install the new 64-bit version.
  • Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. See Upgrading-custom-configuration-objects.
  • If the Application Server and the RSCD agent are on the same machine, they must be at the same version. If you upgrade one component, you must upgrade the other to the same version. Perform the upgrade steps in this order:
    1. Shut down the Application Server.
    2. Upgrade the RSCD agent.
    3. Verify the agent is running and has been upgraded. To do so, run the following command: agentinfo <serverName>
    4. Upgrade the Application Server.

To silently upgrade the RSCD agent

  1. Log in to the system where you want to upgrade the Agent.
  2. Copy the installation file (RSCD<version-platform>.msi) to a directory on the Windows system.
  3. Change to the directory that contains the installation file.
  4. At the command prompt, enter the command:
    msiexec /I RSCD<version-platform>.msi /QN <PROPERTY=value> <PROPERTY=value>
    where:
    • RSCD<version-platform>.msi is the name of the agent installer.
    • /QN — Sets the user interface level to no UI. Optionally, you can use /QB to display a progress bar for the installation.
    • (Optional)/L*V <logLocation> — Logs information about the installation to the file you specify.

    • <PROPERTY=value>— Specifies a property that overrides the default installation settings. You can specify one or more of the following properties:

      Property
      Description
      REBOOT
      The REBOOT property, set to the ReallySuppress value, is necessary to ensure that you are not prompted to reboot the host computer towards the end of the silent installation.
      INSTALLDIR
      The target location for the RSCD installation. The default is: C:\Program Files\BMC Software\BladeLogic\RSCD. Enclose the path in double quotation marks (" ").
      EXPORTSFILE
      Specifies the location of a file to use as the exports file for the RSCD agent. The installation renames the specified file to exports and puts it in the RSCD agent configuration file directory. The installation does not overwrite an existing file, if found. In addition, you cannot edit the specified file in the installation program GUI. For details about the exports configuration file, see Configuring-the-exports-file.Specify the full path to a file. The file name can contain Windows path variables (for example, %temp%); however, the file must reside on the local file system of the computer on which you are installing the agent.
      KEYLOGS
      Enables or disables use of keystroke logs for nexec commands. Keystroke logs capture log information from remote commands run on the agent using nexec. The logs are also periodically rolled and digitally signed as they are rolled.Values: 1 (enable) or 0 (disable). The default is 1.
      LOGFILEDIR
      Location of agent log files. The default is: C:\Program Files\BMC Software\BladeLogic\RSCD.
      MAPUSER
      The account of a local user. If you specify a value for this property, the exports file is modified to force the agent to impersonate the specified user for all activities. By default, the property is not set and no user mapping is created.
      RSCDPORT
      Sets the RSCD port number in rscd entry of the agent's secure file. The default port is 4750.
      SECUREFILE
      Specifies the location of a file to use as the secure file for the RSCD agent. The installation renames the specified file to secure and puts it in the RSCD agent configuration file directory. The installation does not overwrite an existing file, if found. In addition, you cannot edit the specified file in the installation program GUI. For details about the secure file, see Configuring-the-secure-file.Specify the full path to a file. The file name can contain Windows path variables (for example, %temp%); however, the file must reside on the local file system of the computer on which you are installing the agent.
      SECURELOGS
      Enables or disables use of secure (digitally signed) logs for the RSCD agent. Secure agent logs have message authentication codes and sequence numbers assigned to the current log and digitally signed rolled logs.Values: 1 (enable) or 0 (disable). The default is 1.
      USERSLOCALFILE
      Specifies the location of a file to use as the users.local file for the RSCD agent. The installation renames the specified file to users.local and puts it in the RSCD agent configuration file directory. The installation does not overwrite an existing file, if found. In addition, you cannot edit the specified file in the installation program GUI. For details about the users.local configuration file, see Configuring-the-users-or-users-local-files.Specify the full path to a file. The file name can contain Windows path variables (for example, %temp%); however, the file must reside on the local file system of the computer on which you are installing the agent.
      EXPORTSFILETEXT
      Set this parameter to modify the exports file content. For example, to allow access only from appserver1 and appserver2 hosts, use this value: "appserver1,appserver2 rw" For more information about configuring the Exports file, see Configuring-the-exports-file.
      BLADELOGICDCUSERPASSWORD(Mandatory when installing the RSCD agent on a domain controller)
      Set the password for the BladeLogicRSCDDC user.You can change the password later by using the chapw command or the agentctl utility. For more information, see Changing-the-BladeLogicRSCDDC-account-password-on-domain-controllers.
      BLADELOGICUSERPASSWORD
      Set the password for the BladeLogicRSCD user. If you don't set the password, a random password is generated. You can change the password later by using the chapw command or the agentctl utility. For more information, see Changing-the-BladeLogicRSCD-account-password.
      NEW IN 23.4 MAP_TO_SYSTEM_USER_ONLY
      Enables or disables the exclusive mapping of all roles/users to the SYSTEM user on the server. For more information, see Impersonation-and-privilege-mapping.Values: 1 (enable) or 0 (disable). The default is 0.

      Configure the following properties to use the Smart Agent capabilities. 

      Example of configured Smart Agent properties
      AUTOSTART_AGENT=1
      EXPORTSFILETEXT="*rw,user=root"
      SMARTHUB_HOSTNAME="abc.bmc.com"
      SMARTHUB_PORT=10443
      ENROLL_INTERVAL_MIN=1
      ENROLL_AS="<HOSTNAME>.bmc.com<UPPER>"
      HEARTBEAT_INTERVAL_MIN=5
      SMARTAGENT_SERVICE=1
      ACCESS_KEY="azywdWJsaWNfa2V5IjoiLS0tLS1CRUdJTiBQVUJMSUMgS0VZ
      LS0tLS1cclxuTUlJQklqQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FROEFNSUlCQ
      2dLQ0FRRUExSDc5THdmcG5DNm5ZVTNHVTRFb1xyXG5qdERzQjczdzF3dEE4VmV
      CR1FZd1o0NVloK3FrRiszYmN0RDVabGQxdVA2cWRWZWppTzRXMXRTWmxRTXBLb
      tttXHJcbnJIMGdyc3dXNG91S1E2azFTdzY2SWZWTU5BKzI5Qk5oFdZYy9xbzk3
      eW5HSzJLNm41a2tzc2dCM0RONGRcclxuN1FJREFRQUJcclxuLS0tLS1FTkQgUF
      VCTElDIEtFWS0tLS0tXHJcbiIsImluZnJhX2lkIjoiQjgzMzNFQUIwQjUzM0RDR=="
      SERVER_PROP_LIST="CLOUD_PROVIDER, CLOUD_ACCOUNT, CLOUD_REGION,
      CLOUD_RESOURCE_ID, CLOUD_RESOURCE_NAME, CLOUD_VPC"
      CLOUD_PROVIDER="AWS"
      CLOUD_REGION="MUMBAI"
      CLOUD_RESOURCE_ID="123"
      CLOUD_ACCOUNT="BMC-TEST"
      CLOUD_RESOURCE_NAME=""
      CLOUD_VPC="VPC0"
      TUNNEL_ENABLE="true"

To silently upgrade RSCD agents using the File Deploy job

  1. Copy the RSCD installation program (RSCD<version>-<platform>.msi) to the server on which you plan to create the File Deploy Job. Put the file in the <WINDIR>\Temp directory, where <WINDIR> is typically C:\winnt or C:\Windows.
  2. In the TrueSight Server Automation Console, select the installation file for the version of the agent to which you want to upgrade. Then right-click, and choose Deploy Files from the pop-up menu:
    RSCD<version>-<platform>.msi
    The File Deploy Job wizard opens.
  3. For Name, assign a name to this File Deploy Job. For Save in, specify the job group where you want to store this job.
  4. For Destination, enter /c/tmp or a directory with no spaces in its path, and then click Next.
  5. Select the servers being upgraded, and then click Next two times to display the Advanced Options panel.
  6. For Post-command, enter the following command:
    msiexec /I "C:\tmp\RSCD<version>-<platform>.msi" /qn REBOOT=ReallySuppress
    If necessary, replace C:\tmp with the destination directory that you used for the installer.
  7. Click Finish.

The file is deployed to the target servers and the installation runs silently on each machine.

Note

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. For steps on upgrading custom configuration objects, see Upgrading-custom-configuration-objects.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*