Info |
---|
Make sure you understand what pairing before continuing troubleshooting by reading this article. |
This article contains list of recommended steps to pair a terminal.
Recommended steps differ based on different state the terminal is in and a different version it has installed on it.
This guide assumes you have sever version at least 20230801.
Jump here to right section that applies to your case:
Table of Contents |
---|
...
Understanding 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. We assume you're running at least server version 20230801.
Navigate to the Right Section
Terminal with version 20230801 and higher
Pairing
...
Steps
Deployment Scenario | Terminal |
---|
State | Actions to |
---|
Take | Notes |
---|
Scenario A |
Terminal was paired in past to this server and has VPN configuration already generated.
Previously paired, VPN configured | Set the terminal server's host/IP via advanced admin. Look for error screen with pairing code |
. |
In CAS |
Approve the pairing request.
Terminal will pair and connect to master service via VPN channel.
If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.
Terminal operates in Deployment Scenario A
, approve new pairing request. | ||
Scenario A | Never paired, No VPN | Create terminal on server |
Set on terminal server’s host/ip via advanced administration. Terminal should show error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service via VPN channel.
If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.
Terminal operates in Deployment Scenario B
This case applies for example to new terminals that has been purchased.
Create terminal on server.
Set on terminal server’s host/ip via advanced administration. Terminal should show error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service.
Terminal operates in Deployment Scenario B
Terminal was paired in past to this server.
Set on terminal server’s host/ip via advanced administration. Terminal should show error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service.
Unpairing steps
Note |
---|
Unparing should not be used unless necessary. |
Deployment Scenario | Terminal state | Actions to take |
---|---|---|
Terminal operates in Deployment Scenario A | Terminal is paired and connected to VPN and master service |
|
Terminal operates in Deployment Scenario B | Terminal is paired and connected to master service |
|
My terminal has a newer version than 20190130 but has older version then 20230801
Pairing steps
...
, 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 |
---|
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed automatically.
Scenario A |
Terminal was paired in past to this server and has VPN configuration already generated.
Previously paired, VPN configured | Set the terminal server's host/IP via advanced admin. Look for error screen with pairing code |
. |
In CAS |
Approve the pairing request.
Terminal will pair and connect to master service via VPN channel.
If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.
Terminal operates in Deployment Scenario A
, approve new pairing request. | ||
Scenario A | Never paired, No VPN | Create terminal on server |
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed automatically.
Terminal should after a while start showing error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service via VPN channel.
If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.
Terminal operates in Deployment Scenario B
This case applies for example to new terminals that has been purchased.
Create terminal on server.
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed automatically.
Terminal should after a while start showing error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service.
Terminal operates in Deployment Scenario B
Terminal was paired in past to this server.
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed automatically.
Terminal should after a while start showing error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service.
My terminal is version 20190130 and older
Pairing steps
Terminal with this version is an archaic piece of machine.
Machine needs to undergo two subsequent terminal upgrades. Good news is that gate service should take care of it automatically.
Deployment Scenario
Terminal state
Actions to take
Notes
Terminal operates in Deployment Scenario A
Terminal was paired in past to this server and has VPN configuration already generated.
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed twice automatically.
Terminal should after a while start showing error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service via VPN channel.
If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.
Terminal operates in Deployment Scenario A
This case applies for example to new terminals that has been purchased.
Create terminal on server.
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed twice automatically.
Terminal should after a while start showing error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service via VPN channel.
If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.
Terminal operates in Deployment Scenario B
This case applies for example to new terminals that has been purchased.
Create terminal on server.
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed twice automatically.
Terminal should after a while start showing error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
Terminal will pair and connect to master service.
Terminal operates in Deployment Scenario B
Terminal was paired in past to this server.
Set on terminal server’s host/ip via advanced administration.
Terminal contacts server and displays following Error: Terminal unpaired
After a while gate service automatically upgrades terminal to a newer version. This step will be performed twice automatically.
Terminal should after a while start showing error screen with pairing code displayed.
On server in CAS new pairing request will appear on terminal list page.
Approve the pairing request.
, 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.