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:
      Excerpt named agent_silent_properties was not found in document xwiki:Automation-DevSecOps.Server-Automation.TrueSight-Server-Automation.Installing.Installing-components-silently.Using-silent-mode-to-install-an-RSCD-agent-Windows.WebHome.

      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*