23.3 enhancements and patches
23.3.00.01
PATROL Agent for BMC Helix Operations Management 23.3.00.01 resolves the issues reported in the earlier versions.
For the list of issues resolved in this release, see Known-and-corrected-issues.
23.3.00
Automatically downloading configuration files from BMC Helix Operations Management
Provide configuration file details while creating a monitor policy for a PATROL Agent in BMC Helix Operations Management. You no longer have to manually copy, deploy, or create configuration files for each PATROL Agent that is applicable to the selection criteria in the monitor policy.
For more information, see the following topics:
See Defining monitor policies for more details about uploading configuration files.
See Configuring and maintaining monitor policy configurations to know how to upload configuration files.
Installing PATROL Agent and knowledge modules by using the Microsoft Software Installer (MSI) package
Use the Setup.msi file to install the PATROL Agent and knowledge modules on Windows. The MSI package file provides a more reliable and resilient installation. The Microsoft Installer service uses the information that is contained within the MSI package file to install the PATROL Agent and knowledge modules.
For more information, see Installing-PATROL-Agents.
Improve the infrastructure performance with multiple forward proxy servers
Use multiple proxy servers to improve infrastructure performance by providing high availability and adding an additional security layer between PATROL Agent and BMC Helix Operations Management.
For more information, see Configuring-PATROL-Agents-to-support-multiple-forward-proxy-servers.
Accessing PATROL Agent with and without credentials
- If you access the PATROL Agent locally, no credentials are required by default.
For example, pconfig +get -p <portnum>.
You can override this behavior by setting up the configuration variable /AgentSetup/pconfigRequiresAuthentication = { REPLACE="true"} or setting up requiresconfigauthentication = true in the patrol.conf file.
For example, pconfig +get -p <portnum> -U <username> -W <password>. - If you access the PATROL Agent remotely, the credentials are required by default.
For example, pconfig +get -host <patrol agent host name> -p <portnum> -U <username> -W <password>.
You can override this behavior by setting up the configuration variable /AgentSetup/pconfigRequiresRemoteAuthentication = { REPLACE="false"}.
For example, pconfig +get -host <patrol agent host name> -p <portnum>. - You can access PATROL Agent on PatrolCli by using the default account credentials only.
Accessing PATROL Agent by unprivileged users
You can access PATROL Agent by using the default account credentials only. If you are an unprivileged user and want to access PATROL Agent, set up the pconfig variable, /AgentSetup/accessControlList.
The following options are available during a package creation:
- Restricted Access Control (default)
- Full Access Control
The Restricted Access Control option is selected by default and is applicable for the default account only. You can modify the access control list to give PATROL Agent access to specific users by setting up the pconfig variable, /AgentSetup/accessControlList.
If you select the Full Access Control option, all the users get access to PATROL Agent from pconfig and PatrolCli.