Downloading and installing a rollout from a server

Rollout packages are available on the rollout server web page i.e. https://<ip rollout server>:<port>/rollout/

From this page you can download the required package and once downloaded, launch this executable file to proceed. This page makes all rollout packages on the server available for download by clients that cannot be accessed directly by the rollout.

This BMC Client Management video (2 mins 27 secs) describes how to download the rollout package.

icon_play.png https://youtu.be/5XdFungwwNU

Related topics

Agent-rollout-configuration

First-agent-rollout

Getting-started-with-agent-rollout

Scheduling-a-rollout

Rolling-out-client-agents-via-alternate-methods

Uninstalling-the-client-agent-via-rollout

Rollout-targets

Automatically-rolling-out-agent-using-a-wizard

To download and install, proceed as follows:

  1. To download a package, right-click its name and save it on the local client, or launch it directly for installation by double-clicking.
  2. Before the actual download or installation process starts, provide the password for the download a second time.

Managing the secured executable

For enhanced security, you get an option to set an execution password for building an encrypted installer. The encrypted installer cannot be executed directly. You need to enter the -p <password> parameter to decrypt the installer so it can be executed. If this parameter is provided for a non-encrypted installer, it will be ignored. Notice that a rollout configuration with password can still be sent to a rollout server which has older version (12.9 and earlier). In this case, the password is ignored and a standard (non-encrypted) installer is generated. 

The password must be provided on the command line which may cause some unexpected behavior. For instance, if the password includes a whitespace character, it may not be extracted as expected. In this case, the password must be enclosed with double quotes (").

For the remote control on request session on a macOS device, the end user downloads a folder and not a binary file. So providing a password on the command line at the folder level may not be possible. In this case, the end user must open the folder from a terminal and call the embedded binary manually.

 

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