Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Silently upgrading Windows agents

To silently upgrade one or more RSCD agents on Windows, use a BMC 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 RSCD agents

  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 BMC 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*