Terminal Pairing: A Comprehensive Guide
Before you start troubleshooting, make sure you're familiar with the concept of pairing.
This guide is designed to help you with that.
Establishing Trust between Terminal and Server - Terminal Pairing
We assume you're running at least server version 20230801.
Quick jump
My Terminal firmware version is:
Terminal with version 20230801 and newer
Pairing Steps
Deployment Scenario | Terminal State | Actions to Take | Notes |
|---|---|---|---|
Scenario A | Previously paired, VPN configured | Set the terminal server's host/IP via advanced admin. Look for error screen with pairing code. | In CAS, approve new pairing request. |
Scenario A | Never paired, No VPN | Create terminal on server, generate VPN config. Set host/IP. | As above. |
Scenario B | Never paired | Create terminal on server, set host/IP. | As above. |
Scenario B | Previously paired | Set host/IP. | As above. |
Unpairing Steps
Deployment Scenario | Terminal State | Actions to Take |
|---|---|---|
Scenario A | Paired and connected | Unpair via terminal list action menu. |
Scenario B | Paired and connected | As above. |
Terminal with a version newer than 20190130 but older than 20230801
Pairing Steps
Upgrade the terminal to version 20230801 first. The good news is that the gate service should handle this automatically.
Deployment Scenario | Terminal State | Actions to Take | Notes |
|---|---|---|---|
Scenario A | Previously paired, VPN configured | Set the terminal server's host/IP via advanced admin. Look for error screen with pairing code. | In CAS, approve new pairing request. |
Scenario A | Never paired, No VPN | Create terminal on server, generate VPN config. Set host/IP. | As above. |
Scenario B | Never paired | Create terminal on server, set host/IP. | As above. |
Scenario B | Previously paired | Set host/IP. | As above. |
Terminal with version 20190130 or older
Pairing Steps
You're working with a pretty old machine here. Upgrade the terminal twice. Again, the gate service should handle this.
Deployment Scenario | Terminal State | Actions to Take | Notes |
|---|---|---|---|
Scenario A | Previously paired, VPN configured | Set the terminal server's host/IP via advanced admin. Look for error screen with pairing code. | In CAS, approve new pairing request. |
Scenario A | Never paired, No VPN | Create terminal on server, generate VPN config. Set host/IP. | As above. |
Scenario B | Never paired | Create terminal on server, set host/IP. | As above. |
Scenario B | Previously paired | Set host/IP. | As above. |
There you go! Clear, simple, and: ready to guide anyone through the labyrinth that can be terminal pairing.