Important This documentation space contains information about PATROL Agents when deployed in a BMC Helix Operations Management environment. If you are a TrueSight Operations Management user, see PATROL Agent 24.1

24.1 enhancements and patches

Review the PATROL Agent 24.1 enhancements for features that will benefit your organization and to understand changes that might impact your users.

BMC applies upgrades as described in the BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows..

Related topics

Known-and-corrected-issues

Release-notes-and-notices


Enhanced PATROL Agent installation with sudo user support

The PATROL Agent 24.1.00 release, along with the Common Installer 20.02.05 release, introduces an enhanced feature for the PATROL Agent installation process. This feature offers improved flexibility by incorporating support for sudo users. Traditionally, installing the PATROL Agent required the inclusion of the root account in the package, presenting challenges for users without access to root credentials. 

  • Users can now input sudo user credentials directly on the "Root Login Name" screen as part of the installation process.
  • Users with access to the root account still have the option to provide root credentials during installation.
  • The new functionality allows users to leverage a sudo user within the installation package, eliminating the previous requirement for a root user during installation on Unix platforms. Prior to this update, attempting to specify a sudo user during package creation resulted in errors, as the installation process expected a root user. This constraint has been addressed, providing users with increased flexibility and a more streamlined installation experience.

Prerequisites

Before utilizing this feature, administrators must complete the following prerequisites:

  • Configure sudo user in /etc/sudoers
  • Ensure that the /tmp folder is available.
  • The root user must add one of the entries below to the /etc/sudoers file for sudo users, depending on the use case:
    • Specifying a group name:
      %<groupname> ALL=/tmp/install_script.sh
    • Specifying a user name:
      <sudousername> ALL=/tmp/install_script.sh

    • Specifying a specific hostname:
      <sudouser> <hostname>=/tmp/install_script.shIf you are using Solaris, add the below entry to the /etc/sudoers file for sudo users:

      ALL=/tmp/install_script.sh, /bin/cp, /usr/bin/cp, /bin/ln


 

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