Articles in this section

Urgent: End of support for Windows Server 2012 R2 with Celigo on-prem agent

The Celigo on-premise agent doesn't support Windows Server 2012 R2, in line with Microsoft's end of support for that operating system. To keep integrations running and stay compatible with current Celigo features, upgrade your Windows server. If you must keep Windows Server 2012 R2, install agent version 4.3.0 using the steps in this article. Version 4.3.0 doesn't update automatically, so it stays compatible with Windows Server 2012 R2.

Important: An agent on version 4.3.0 can't join an agent group, because agent groups require version 6.0 or later. To use agent groups, upgrade the server and install the current agent.

Before you begin

  1. Identify all flows that use the agent, and note any that use agent-based webhook connections.

    For each webhook connection, check whether the webhook provider retries failed deliveries. If it doesn't, turn off the webhooks at the provider until the update is done.

    Warning: While the agent is being replaced:

    • Some events can be delayed.
    • integrator.io responds with status code 403 while the flow is disabled.
    • You might need to trigger missed events from the provider manually.
  2. Disable all flows that use the agent disable_flow_icon.png.
  3. Make sure you have administrator access to the server.
  4. download.svg​​ Download on-premise agent version 4.3.0.

Tip: Schedule the update during a low-traffic period to minimize delayed or missed events.

Uninstall the existing agent

  1. Sign in to the server with an account that has administrator privileges.
  2. Stop the agent.
  3. Open Control Panel, and then select Programs > Programs and Features.
  4. Find the agent in the list. It's named Agent, so it's usually near the top.

    Control_panel_programs_and_features_list.png
  5. Right-click the agent, and then select Uninstall.
  6. Follow the on-screen instructions to finish.

    Agent_uninstall_wizard.png

Install agent version 4.3.0

  1. Open Agent Setup 4.3.0.exe on the server. If you downloaded it on another computer, copy it to the server first.
  2. Complete the setup as described in Install and configure the Windows on-premise agent, starting with the choice of who can run the agent. If you install it for all users, add administrator privileges as that article describes.

When setup finishes, the agent opens and asks for your integrator.io token.

Enter your existing agent token

Reuse the token of the agent you uninstalled, so your connections keep working.

  1. In integrator.io, go to Resources, and then select On-premise agents.
  2. Find the agent, and then select Show token.
  3. Select Copy (copy.svg​​) next to the access token.

    360061142811-agent-2.png
  4. Paste the token into the agent. The agent starts communicating with integrator.io.

    360061148171-agent-4.png

Refresh the On-premise agents page to confirm that the agent is online.

On-premise agents list showing the agent online

If your token is compromised, generate a new one as described in Install and configure the Windows on-premise agent.

Validate the update

  1. Turn the webhooks back on at the provider, if you turned any off.
  2. Enable the flows that use the agent.
  3. Confirm that the flows run, and that webhooks are received, if you use them.
  4. Monitor for errors in the first few hours after the update.

If you see errors, retry the affected flows. If the errors continue, contact Celigo Support.

Revert to version 3.4.0

If agent version 4.3.0 doesn't run or flows fail with it, install version 3.4.0 as a temporary fix.