Important

   

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

Setting PATROL Agent configuration variables

This section explains how to assign values to the PATROL Agent configuration variables that will allow a DCOM client to communicate with the agent.

  1. Launch wpconfig for the PATROL Agent you are configuring.
  2. Assign values to the PATROL Agent Setup variables described in the following table.



    PATROL Agent COM variables

    Variable

    Values

    Description

    comSecurityLevel

    W (default), N, R, F

    Controls the level of information provided by the PATROL Agent to the DCOM client.

    W — DCOM client can receive and change data on the agent
    N — No DCOM interface allowed
    R — DCOM client can receive data from the agent.
    F — DCOM client can receive, change, and use PslExecute() to run OS commands.

    comUserAllowed

    Empty String (default), Group Names, User Names

    Controls who can access the PATROL Agent DCOM server. Listed users, members of groups, and the user who started the agent may access the agent DCOM server. Separate multiple values with the "|" character (no spaces).

    This variable, supported only by Windows NT 4.0 and later, takes precedence over any security set by the Microsoft DCOM Configuration Utility (see Configuring DCOM on BMC PATROL Agents). If you set comUserAllowed to the empty string, security is determined by the DCOM Configuration Utility.

    Note: When entering a user name that is a member of an NT domain, separate the domain name and the user name with two backslashes.

  3. If you changed the comUserAllowed variable, restart the PATROL Agent.
Was this page helpful? Yes No Submitting... Thank you

Comments