SiteRemote will be discontinued on December 31, 2025. Please use the successor product SiteKiosk Online instead.
If you are using your own SiteRemote server and the client is already logged in, the configuration settings for SiteRemote will continue to be displayed. For clients without a valid login, the configuration settings for SiteRemote can be accessed by manually editing the SiteKiosk configuration file. Open the file with an editor and change the line
<plugin name="SiteRemote" shown="false" enabled="true" clsid="2F5B83E1-88BC-44D2-9E5D-B3D621C4A292">
to
<plugin name="SiteRemote" shown="true" enabled="true" clsid="2F5B83E1-88BC-44D2-9E5D-B3D621C4A292">

Monitoring and managing your terminals is a breeze with a SiteRemote stand-alone server version.

SiteRemote allows you to conveniently monitor the status of your terminals from your home office. You can create reports on the usage of the terminals as well as on their sales turnover. SiteRemote also lets you exchange data between your local computer and the clients or change SiteKiosk configuration files.

You can obtain a SiteRemote server license for a one-time license fee, which will allow you to run your own SiteRemote server.

1. General information

1.1 Architecture
The server functions as a communication interface between the administrator (the person remotely maintaining and configuring the clients) and the SiteKiosk client. The kiosk client will report back to the SiteRemote Server at specific intervals (heartbeats) and will complete any new jobs. This architecture's main advantage is to provide maintenance even for clients operating behind a firewall and with a dynamic IP address.

1.2 Functions of the SiteRemote server
You can automatically log on to your SiteRemote team your server using your user name and password. Each team can manage any number of administrators and SiteKiosk clients.

2. Register your client

To register a SiteKiosk client with the SiteRemote server, enter the access information for your SiteRemote team (user name/password). 

2.1 Machine name
The kiosk name you enter here will appear automatically in the tree structure under "new terminals" every time the client logs on.
You can change the kiosk name displayed in SiteRemote here at any time.

2.2 Server name and port
Defines the SiteRemote server's address as well as its port at which the client will log on.

2.3 User name and password
Enter your access information here which you will need to log on to the SiteRemote server..
Since each user name will be assigned by the system only once, you will have to assign the name clearly to one SiteRemote team.

2.4 Mobile number
This setting is optional and should only be used if the terminal is using a special mobile device available from gekartel. The SiteRemote server you are using must also be configured to accept these mobile devices.

2.5 Machine location (optional)
You can use these fields for enter the location address and other information or remarks which will be shown later in the terminal view of SiteRemote.

2.6 Log on client
After entering the correct access information, click on "Login machine." Make sure the client is connected to the Internet.
If login was successful, the appearance of the configuration page will change. You will be shown the status of the client and given the option to log off the client.

Caution: save your siteremote.config/siteremoteclient.local.config
Each client will identify itself with its worldwide unique KIOSK ID and the so-called "registration token." Both information will be saved to the XML file siteremote.config, which you will find in SiteKiosk's installation folder under /SiteRemote for the old SiteRemote client. In the new SiteRemote client version (SiteKiosk 7.5 or higher) the information will be stored in the XML file siteremoteclient.local.config, whose default storage location is in the folder:
"C:\ProgramData\PROVISIO\SiteRemote Client" (Vista/Win7) or
"C:\Documents and Settings\All Users\Application Data\PROVISIO\SiteRemote Client" (XP).
Do not delete this file under any circumstances because otherwise the server will no longer be able to identify the terminal. This would result in the fact that the old data, due to the change in identification, would no longer be linked with one another when the system is logged in again.

Conversely, you can, if necessary, assign your old terminal's ID to a new terminal by transferring the siteremote.config or siteremoteclient.local.config file. Thus, you may want to save the siteremote.config or siteremoteclient.local.config to be able to transfer it to any new or already existing device should this ever become necessary.

Caution: Use care when mirroring your systems (multiple installations)
If you want to mirror your complete systems so that you can conveniently perform multiple installations, please make sure you do not include the siteremote.config or siteremoteclient.local.config and take care that each terminal will be registered again after shipping. If multiple systems with the same ID log on to the server, the system will generate meaningless data.


2.7 Log off machine
Use this function at any time to disable the remote maintenance function for your terminal. Another way to do this is to move a terminal to the trash AND empty the trash on the SiteRemote user interface (will not delete any data).
Please note that all data you gathered about this terminal will be lost.


2.8 Replacing a registered machine
If you want to replace a registered machine, e.g. because of a hardware failure, you can just register the new machine under the same machine name as the old one. You will be asked if you want to replace the existing machine with the new one. This process will keep the data of the old machine and assign it to the new one.


2.9 Automatically register machines
To automatically register machines with a SiteRemote server you can use the Auto Register Tool. The tool can be downloaded under the Extras section of your team. Please follow the instructions provided by the Auto Register Tool to automatically register your machines.