Enabling Agent Connectivity in ControlUp Products

A user asked about enabling agent connectivity from Windows 10 operating systems that are not domain connected and have no open inbound ports – with the existence of an option to open outbound traffic. They also asked if the agent is capable of initiating communication once installed. The response was that starting from version 9, both EdgeDX and RealtimeDX agents can connect using an outbound SSL 443 connection, and domain membership is not a requirement.

Read the entire ‘Enabling Agent Connectivity in ControlUp Products’ thread below:

I have a customer with a couple of Windows 10 OS behind a bridged network – is there a guide for enabling the agent connectivity from these two machines,

• Not domain connected

• No ports open inbound but option to open out bound traffic is there

I get the standalone agent deployment but does (can) the agent initiate the comms once installed – I want to be lead to believe that it will

Noting they will both flag under same IP address as they are using different ones internally

Hey Ian,

Which ControlUp product are you asking about? EdgeDX is primarily focused on physical devices.

RealtimeDX is primarily focused on virtual devices.

Depending on which product you’re asking about will change the answer a bit

Indeed. But the good news are that as of v9, both Edge and RTDX agents can connect using an outbound SSL 443 connection, and domain membership is not required

Continue reading and comment on the thread ‘Enabling Agent Connectivity in ControlUp Products’.  Not a member? Join Here!