Agent Outbound Communication: Setting Agent Outbound Per Agent
    • Dark
      Light
    • PDF

    Agent Outbound Communication: Setting Agent Outbound Per Agent

    • Dark
      Light
    • PDF

    Article summary

    From ControlUp Version 9.0, we provide flexibility to enable agent outbound communication per agent via the Real-Time Console.

    Note

    This new change is not relevant for MSI-based agent installations.

    Upgrade Instructions

    1. Extract ControlUpConsole_Secure_SIGN.zip and open the ControlUpConsole.exe. Make sure that no other ControlUp users in the same organization have an older Real-Time Console version open on their machines.

    2. Upgrade your monitor machines to 9.0.0.1546. Note that upgrading the monitors will automatically install the agent on the monitor machines.

    3. Once the agent is installed, the monitor will establish an inbound connection to this agent.
      SetAgentInbound

    4. In the console, right-click an agent and select Set Outbound Connection.
      SetOutboundCon1

      A new wizard opens in which you see whether the agent was successfully registered as outbound. If the registration succeeds, you see status Success.
      SetAgentInboundSuccess

    5. In the Monitor Settings, verify that the agent appears as Outbound.
      AgentConnectOut

    6. Perform this action on all agents you want to move to outbound.

    Note

    After upgrading an agent to version 9.0.0.1546, an ERROR event appears in the log, displaying the message: “Neither registration key nor PAT are configured”.

    This error message is recorded only once and signifies that either the Registration Key or the Personal Access Token (PAT) has not been set up, preventing the agent from communicating outbound. However, you do not need to take any action in response to this message. You can go ahead and assign your agents as outbound if you choose.


    Was this article helpful?