Update Endpoint Privilege Management for Unix and Linux with the Linux Package Installer

The Endpoint Privilege Management for Unix and Linux Linux package installer can be used to upgrade an existing Endpoint Privilege Management for Unix and Linux installation to a new version. The existing Endpoint Privilege Management for Unix and Linux version should have been installed with the Endpoint Privilege Management for Unix and Linux package installer.

It is possible to use the Linux package installer to install Endpoint Privilege Management for Unix and Linux over an existing version that was installed with pbinstall. However, we do not recommended doing so because it can result in unused files from the existing version remaining in the file system.

Package Upgrade Considerations

Installing an upgrade with the Linux package installer is similar to using the Linux package installer to install Endpoint Privilege Management for Unix and Linux for the first time. Keep these considerations in mind when you prepare to upgrade:

Technically, the Endpoint Privilege Management for Unix and Linux Linux packages are upgrade packages, as opposed to update packages. An upgrade package installs the new files before removing the existing files and registering the new version number in the RPM database.
an Endpoint Privilege Management for Unix and Linux Linux upgrade package contains a complete Endpoint Privilege Management for Unix and Linux installation, rather than simply the files that have changed since the previous release.
If you have more than one Endpoint Privilege Management for Unix and Linux package on a computer, upgrade all packages on that computer.
A newer release can introduce features that use new settings or configurations. In which case, an upgrade of the configuration package of Endpoint Privilege Management for Unix and Linux is also needed.
Unlike Endpoint Privilege Management for Unix and Linux patches that are installed with pbpatchinstall, upgrade packages cannot be rolled back to a previous release. However, you can install an older package over a newer one, effectively rolling back to the older release.

For more information, see Revert to a Previous Version.

Package Upgrade Procedure

Follow this procedure to upgrade your installation of Endpoint Privilege Management for Unix and Linux using the Linux package installer:

Obtain the tarball file for the Linux upgrade packages that are appropriate for your hardware. The tarball file name has the format pmul_<flavor>-v.v.r-bb-pn_pkg.tar.Z.
- <flavor> indicates the operating system and hardware architecture.
- v.v.r is the major and minor version number and the release number.
- bb is the build number.
- n is the update number.
Extract the package tarball files into the /unzip-dir/ directory by executing the following command:
```
tar xvfz pmul_<flavor_version>_pkg.tar.Z
```
Navigate to the /unzip-dir/powerbroker/v<version>/<flavor>/install/ directory
Create the settings_files directory and change directory to that location.
To retain or correctly update the settings of the current installation, copy the following files from the target installation host into the settings_files directory you created in step 4:
- /etc/pb.settings
- /etc/pb.cfg
- encryption keys defined in pb.settings for networkencryption, eventlogencryption, iologencryption, reportencryption, policyencryption, and restkeyencryption settings (if enabled)

In a default installation, there are typically 2 key files created: pb.key and pb.rest.key.

policy file defined in policyfile setting in pb.settings (if the target installation is a Policy Server)

In a default installation, the policy file is located in /opt/pbul/policies/pb.conf.

For Cached Policy clients: policypubcertfile (default=/etc/pbpolicypubcert.pem)

Execute the following command and verify the installation settings:
```
./pbinstall -z
```
Create the upgrade configuration package by running the pbcreatelincfgpkg utility:
```
pbcreatelincfgpkg -p suffix
```
Use the current suffix of the installation to be upgraded. Use the suffix you provided during the initial package installation in step 9 of the Installation Procedure.
Another way to find the suffix is to run the following command on the target installation host to get the list of packages installed:
```
rpm -qa |grep powerbroker
```
Identify the suffix of the Endpoint Privilege Management for Unix and Linux configuration package using this format:
```
powerbroker-config<suffix>-<version>.noarch
```
Navigate to the /unzip-dir/powerbroker/v<version>/<flavor>/package/ directory.
Use the Linux rpm utility to upgrade the component packages by typing:
```
rpm -Uv package-file-1 package-file-2...
```
package-file-n is the name of a component package (.rpm) file.

rpm  -Uv  powerbroker-submithost-9.4.1.03-1.p2-1.x86_64.rpm  powerbroker-runhost-9.4.1.03-1.p2-1.x86_64.rpm

Navigate to the /unzip-dir/powerbroker/<version>/<flavor>/install/ directory.
Run the Linux rpm utility to install the Endpoint Privilege Management for Unix and Linux configuration package by typing:
```
rpm -Uv package-file
```
package-file is the name of the configuration package (.rpm) file created in step 7.
Verify the installation of the packages by typing:
```
rpm -qa| grep powerbroker
```

Revert to a Previous Version

Unlike Endpoint Privilege Management for Unix and Linux patches that are installed with pbpatchinstall, upgrade packages cannot be rolled back to a previous release. However, you can install an older package over a newer one, effectively rolling back to the older release. To install older packages over newer ones, use the following command:

rpm -Uv --oldpackage package-file-1 package file-2...

This command restores the previous release. Repeat the command to restore earlier releases. To restore a single package per rpm command, add the --replacepkgs option.

Upgrade the Configuration Package

When upgrading the configuration package (cfg pkg), some settings that are part of the package might need settings and configuration files copied from the existing installation to the staging host.

Files included in the cfg package:

pb.settings: Hardcoded target location /etc/pb.settings.
pb.cfg: Hardcoded target location /etc/pb.cfg.
All the encryption key files defined for networkencryption, eventlogencryption, iologencryption, reportencryption, policyencryption, and restkeyencryption. By default, two key files are typically created:
- pb.key
- pb.rest.key
The sysadmin can define encryption with different key files in locations other than /etc. Therefore, when upgrading, and to retain what is installed on the target machine, look at all the encryption settings in /etc/pb.settings. Copy the settings to the settings_files directory before running pbinstall -z and pbcreate*cfgpkg.
Policy file if the target is a policy server.