After installation, the EdgeGO server must be paired with the installed agent through an onboarding process.

Onboarding Process Overview

The onboarding process consists of two stages:

• Stage 1: The agent searches for the server location and requests pairing.
• Stage 2: The server receives the request, and the administrator accepts the pairing request.

Agent Request Pairing

The execution process varies based on the operating system:

• Windows:

1. Open File Explorer.
2. Navigate to: C:\Program Files (x86)\EdgeGO\edgegoagent\cmd
3. Right-click on devicego.exe and select Run as administrator.

• Linux:

  cd /opt/edgego/agent/cmd
  sudo ./devicego
  

  The process is successful when the screen displays: “Proceed to the ‘Devices Page’…”

If the local EdgeGO server cannot be found within the Local Area Network (LAN), you will be prompted to specify a remote IP address. To prevent connection issues, avoid launching multiple EdgeGO servers within the same LAN after pairing with a remote one. For additional guidance, refer to the online FAQ.

Server Accept Pairing Request

Once the agent has sent a pairing request, follow these steps on the EdgeGO Server:

1. Log in to the EdgeGO Server.
2. Click Refresh; the status should show as PENDING.
3. Click on Operation, then select Onboard Device.
4. Choose the Device Group name and assign the device to the group.

Please note that the assigned device group cannot be changed in the current version. This limitation will be addressed in the next release. For now, if you need to move a device to a different group after onboarding, you must first offboard the device and then onboard it again to the desired device group.

5. Click Refresh again to update the Device list and confirm that the pairing was successful.

Once the onboarding process is complete, the device status will be displayed as ONLINE. You can start your next journey from Device Management.

Troubleshooting: If the device status remains OFFLINE after the onboarding process:

• Ensure the agent service is still running.
• Verify that the date and time settings match between the server and agent devices.