Agents deployed via BigFix revert to Agent‑Initiated mode when Server‑Initiated communication is expected in the SolarWinds Platform

Environment

• Product: SolarWinds Observability Self‑Hosted / SWOES – Network Performance Monitor 2025.2

• Agent: SolarWinds Platform Agent (Windows)

• Deployment tool: IBM BigFix

• Desired mode: Server‑initiated communication (passive) on TCP 17790

Problem / Symptoms

• Agents deployed via BigFix using MSI + MST configured for Server‑initiated appeared on the nodes as Agent‑initiated.

• The agents refused connections from the polling engine on the expected 17790/TCP passive port.

• Manual workaround (changing mode in Control Panel per node) worked for a few servers, but was not scalable for large BigFix deployments.

After deployment via BigFix, the agent configuration reverted to the default “Agent‑initiated communication” even though the MST was generated in Server‑initiated mode. The BigFix command does not reliably enforce the required MSI properties for passive/server‑initiated operation at scale.

Step A – Generate MSI/MST for server‑initiated agents

1. In the SolarWinds Platform Web Console, go to:
   Settings → All Settings → Manage Agents → Download Agent Software.

2. Select:

   • Windows

   • Mass Deploy to Multiple Machines.

3. Under Agent communication mode, choose Server‑initiated communication.

4. Set Agent communication port:

   • Port: 17790 (default).

5. Download:

   • SolarWinds-Agent.msi

   • SolarWinds-Agent.mst (contains server‑initiated settings and poller information).

Copy these to a local folder on the endpoint (for example C:\Temp) as part of the BigFix package.

Step B – BigFix deployment command / MSI properties

Use the following as the core install command in your BigFix action (wait or waithidden):

msiexec /i "C:\Temp\SolarWinds-Agent.msi" ^
  TRANSFORMS="C:\Temp\SolarWinds-Agent.mst" ^
  SERVERINITIATED=True ^
  SERVER=<POLLING_ENGINE_IP_OR_FQDN> ^
  PORT=17790 ^
  /qn /L*V "C:\Temp\SWAgentInstall.log"

Key points:

1. SERVERINITIATED=True must be present

   • Do not rely solely on the MST; explicitly pass this MSI property so the agent comes up in Server‑initiated mode.

2. SERVER=<POLLING_ENGINE_IP_OR_FQDN>

   • Use a poller address that is reachable from the agent node (Main Poller or APE).

3. PORT=17790 (or your custom port)

   • Must match the port you configured when generating the MST and what you will use later when connecting the passive agent.

4. File paths must be valid

   • Ensure BigFix actually copies both SolarWinds-Agent.msi and SolarWinds-Agent.mst to the path referenced in the command (C:\Temp in the example).

5. /L*V "C:\Temp\SWAgentInstall.log"

   • Produces a verbose MSI log to validate that properties were applied and to troubleshoot any “connection refused” behavior if needed.

Step C – Post‑install verification

On one test endpoint after BigFix runs:

1. Verify agent mode on the node

1. Open Control Panel → Orion Agent Settings.

2. Confirm:

   • Mode = SolarWinds Platform server Initiated Communication.

   • Port = 17790.

   • Shared secret (if used) is set and does not contain double quotes.

2. Connect the passive agent in the web console

1. In the Web Console, go to:
   Settings → All Settings → Node & Group Management → Manage Agents.

2. Click:
   Add Agent → Connect to a previously installed agent → Next.

3. Enter:

   • Agent Name

   • IP/Hostname of the target

   • Server‑initiated communication

   • Port: 17790

   • Shared Secret (if configured)

4. Click Submit.

Expected result in Manage Agents:

• Mode: Server‑initiated

• Connection Status: Connected/OK