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.

      NEW IN 20.02EXPORTSFILETEXTSet 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.

      Configure the following properties to use the Smart Agent capabilities. 

      Property

      Description

      SMARTHUB_HOSTNAMESpecify the host name of the system where the Smart Hub is installed. For example, "smarthubprod1.bmc.com"
      SMARTHUB_PORTSpecify the listener port of the Smart Hub. The default port is 443.
      ENROLL_INTERVAL_MINSpecify the interval for enrolling the agent. The default interval is 15 minutes. The interval range can be 1 - 360 minutes.
      ENROLL_AS
      Shows the predefined identifier that is used for enrolling the server. Specify one of the following identifiers to be used for the enrollment:
      • "<HOSTNAME>": Indicates the server host name. This is the default identifier.
      • "<SMARTHUB_PEER_IP>": Indicates the IP address of the server.
      • "<SMARTHUB_PEER_FQDN>": Indicates the fully qualified domain name of the Smart Hub IP address.
      • NEW IN 20.02.01 <UUID>: Indicates the UUID value that is generated for the server.
        Note: Use this identifier for enrolling servers in the public cloud, such as AWS.

      Also, you can specify a combination of "<HOSTNAME>.domain" or free text, such as "smartagent.domain."

      NEW IN 20.02.01 Conversion operators

      You can use the following conversion operators with any of the predefined identifiers to change their casing:

      • <UPPER>: Changes to upper case characters.
      • <LOWER>: Changes to lower case characters.

      You can also use any free text along with the identifiers.

      Examples:

      IdentifierSample enrolled value
      <HOST_NAME>oracle_prod2
      <SMARTHUB_PEER_FQDN>oracle_prod2.bmc.com
      <HOSTNAME><UPPER>ORACLE_PROD2
      <HOSTNAME>.dev.bmc.com<UPPER>ORACLE_PROD2.DEV.BMC.COM
      <UPPER><SMARTHUB_PEER_FQDN>ORACLE_PROD2.BMC.COM
      RHEL-db-prod1.prod.bmc.com<UPPER>RHEL-DB-PROD1.PROD.BMC.COM
      <LOWER>RHEL-db-prod1.prod.bmc.comrhel-db-prod1.prod.bmc.com
      <UPPER>Error msg : Unable to set enroll_as value from : <UPPER>
      <UPPER><HOSTNAME><LOWER>ORACLE_PROD2

      Note: If both the operators are provided, <UPPER> will have precedence over <LOWER>.

      HEARTBEAT_INTERVAL_MINSpecify the interval at which the Smart Agent sends heartbeats to the Smart Hub for status updates. The default interval is five minutes. The interval range can be 1 - 360 minutes.
      SMARTAGENT_SERVICEIndicates whether the Smart Agent service is enabled. When the service is enabled, the Smart Agent is started automatically after installation.
      • For new installation, the default value is set to 1, which indicates that the Smart Agent service is enabled.
      • For upgrade, the default value is set to 0, which indicates that the Smart Agent service is disabled. The Agent is not started automatically after the upgrade.

      To change the default settings, you can change the property value as required.

      ACCESS_KEYSpecify the access key that is generated after registering the Smart Hub in the Application Server. For more information, see Configuring the Smart Hub and Smart Hub Gateway.

      SERVER_PROP_STR DEPRECATED IN 21.02

      Comma-separated list of server properties of type String. This property is deprecated in version 21.02. Use the SERVER_PROP_LIST property instead. Note: For 21.02.01 and earlier versions, enter the property names and their value in upper case characters only.

      SERVER_PROP_INT DEPRECATED IN 21.02

      Comma-separated list of server properties of type Integer. This property is deprecated in version 21.02. Use the SERVER_PROP_LIST property instead. Note: For 21.02.01 and earlier versions, enter the property names and their values in upper case characters only.

      SERVER_PROP_BOOL DEPRECATED IN 21.02

      Comma-separated list of server properties of type Boolean. This property is deprecated in version 21.02. Use the SERVER_PROP_LIST property instead. Note: For 21.02.01 and earlier versions, enter the property names and their values in upper case characters only.

      SERVER_PROP_LIST

      NEW IN 21.02
      The list of server properties that you want to configure. For 21.02.01 and earlier versions, enter the property names and their values in upper case characters only.

      WM_INTERVAL_SEC NEW IN 20.02.01

      Specify the interval (in seconds) at which the Smart Hub is polled for work requests. The default is 300 seconds.

      TUNNEL_ENABLE NEW IN 20.02.01

      A Boolean value that indicates whether the tunnel feature is enabled. By default, it is disabled.

      TUNNEL_IDLE_TIMEOUT_MIN NEW IN 20.02.01

      The idle connection timeout in minutes. The default is 720 minutes.
      CLOUD_ACCOUNTSpecify the cloud account to which the server belongs.
      CLOUD_REGIONSpecify the cloud region where the server is located.
      CLOUD_RESOURCE_NAMESpecify the cloud resource name for the server.
      CLOUD_RESOURCE_IDSpecify the cloud resource identifier for the server.
      CLOUD_VPCSpecify the cloud VPC where the cloud is located.



      AUTO_USP_ENABLED NEW IN 21.02

      A Boolean value (true or false) that indicates whether the Auto USP feature is enabled. By default, it is enabled. If you want to disable this feature, add this property and specify its value as false.

      AUTO_USP_INTERVAL_H NEW IN 21.02

      The interval (in hours) at which the server properties are validated to detect a change. The default interval is two hours.

      CONFIG_POLICY_ENABLEDNEW IN 21.02

      A Boolean value (true or false) that indicates whether the Configuration Policy feature is enabled. By default, it is enabled. If you want to disable this feature, add this property and specify its value as false.
      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.

Was this page helpful? Yes No Submitting... Thank you

Comments