|
How do I register my machines (kiosks) with the SiteRemote server?
|
|
First, you will need to open a SiteRemote user account. To do so, sign up with SiteRemote server for free. After registering, you will receive a no-obligation 30-day test license allowing you to register up to 50 kiosks.
To register a machine (client) at the server, you have to perform one of the following steps, depending on your client application:
SiteKiosk: | launch SiteKiosk's Configuration Wizard on the machine you want to register, select "Remote Monitoring" and click on the "Register" button. |
SiteKiosk Android:
|
launch SiteKiosk Android's Configuration Wizard on the tablet you want to register,
select "Remote Monitoring" then "Register/unregister device with SiteRemote Server" and click on the "Register machine" button.
|
You will be prompted to enter your SiteRemote user name and password to assign the machine to a team on the server.
If you are using the latest client version you can also register a replacement machine with the same name. This will overwrite the existing machine with the new one. The process will keep the old data.
To automatically register a client you can use the Auto Register Tool. It can be downloaded under Extras in your team.
To register UMTS-capable mobile devices, log on to SiteRemote and go to the page under "Settings" -> "Mobile Devices" (optional, not active on all SiteRemote servers).
|
|
How am I charged for using SiteRemote?
|
|
Using SiteRemote is charged according to the number of registered machines as well as the data transfer volume. One SiteRemote license allows you to use a certain number of machines for a specific period of time and allows you to transfer a certain volume of data (traffic). Although the default traffic volume will usually be sufficient, you can always acquire more traffic packages to transfer larger data volumes.
|
|
How do I obtain a license for using SiteRemote?
|
|
Our online store allows you to obtain SiteRemote licenses 24 hours a day/7 days a week. The licenses you obtained will be sent to you by email. To activate your license key from within the Web application, click the tab "Settings" and select "Licenses" from the tab in the right menu. Follow the instructions you will see after clicking this item.
|
|
Can I manage machines belonging to different groups?
|
|
You can create folders, subfolders and tags to group your machines (e.g. according to location or responsibility). To create a folder, simply click the button "Create Group". You can also select "Create" from a folder's context menu by right-clicking one of the existing folders. Note: You will not be able to create new folders from within the recycle bin.
|
|
How do I move a machine from one folder to another?
|
|
Just like in any other Windows application, you can drag&drop machines to another folder inside the tree view (by clicking and holding the left mouse button while moving the mouse).
|
|
What do I have to keep in mind when replacing or mirroring a machine?
|
|
Every machine communicating with the SiteRemote server has an identity (unique ID) which is stored in the file "SiteRemote.config" (old SiteRemote client) or "SiteRemoteClient.Local.config" (new SiteRemote client) on the machine’s hard drive. The default location of this file is "C:\Program Files\SiteKiosk\SiteRemote\" (old SiteRemote client) or "C:\ProgramData\PROVISIO\SiteRemote Client" (Vista/Win7)/"C:\Documents and Settings\All Users\Application Data\PROVISIO\SiteRemote Client" (XP) (new SiteRemote client).
It is important that only one machine with the same identity contact the server as you may otherwise experience irradic and unpredictable behavior as well as erroneous indications. When mirroring hard drives, please ensure, therefore, that registration will not take place until AFTER SiteRemote the mirroring process as this process will assign each machine its unique ID.
In case you want to transfer the identity of an existing machine, e. g. after suffering a hardware defect, you can copy the file "SiteRemote.config" or "SiteRemoteClient.Local.config" from the old to the new machine. However, while this process is in progress, the SiteKiosk terminal service (SKTsvc.exe, old SiteRemote client) or the SiteRemote client service (SiteRemoteClientService.exe, new SiteRemote client) must be stopped.
If you are using the new client version you can also register a replacement machine with the same name the usual way. This will overwrite the existing machine with the new one. The process will keep the old data.
|
|
Does SiteRemote work behind a NAT firewall or with a dial-up connections (modem/ISDN/DSL) with dynamic IP addresses?
|
|
Yes, connections to the SiteRemote server are always initiated by a machine (client) and are only kept alive for the duration of the data transfer. You can set different reporting intervals for machines using dial-up connections and machines using a permanent Internet connection to save costs. Thanks to its use of communication based on reporting intervals (heartbeats), SiteRemote will not cause the machines to process any commands until they have established their next contact.
|
|
Will I have to make special adjustments to my Windows firewall?
|
|
Usually you won’t, as the communication between the machine and the SiteRemote server is encrypted via port 8086 and established by means of TCP. Unless special restrictions for outgoing connections (outbound traffic) apply, you will not have to make any adjustments. To actually manage and monitor your kiosks, you will only need a computer with Internet access and Microsoft's Internet Explorer, Google's Chrome or Mozilla's Firefox to establish a connection to SiteRemote's Web application via the standard protocols HTTP (port 80) and HTTPS (port 443).
An optional VNC connection to the Clients can be established via the SiteRemote server at the expense of your team traffic volume (Repeater) or by directly connecting the client (Teredo). The repeater version requires TCP 5500 (out), UDP 55901 (out) and UDP 55900 (in). The Teredo version requires at least UDP 3544 (out), which will enable you to connect to clients within the same network, for machines outside the same network all outbound UDP traffic must be allowed.
The UVNC Client (Viewer) requires TCP 5901 (out) to reach the SiteRemote server.
The synchronization feature of the file manager and DigitalSignage requires at least 52138 TCP (outbound) to reach the server. Direct peer to peer connections use 59577 TCP (outbound) and the above Teredo ports. Alternatively you can configure the feature to use http/https for the file download on the team settings page.
By default Android clients use port 5222 to connect to the SiteRemote server.
|
|
How does PROVISIO protect my sensitive data (usage/sales) from unauthorized access?
|
|
There are both physical and personal restrictions preventing access to the SiteRemote server and its databases. PROVISIO warrants that your master (email addresses, contact data) and usage data (e.g. terminal log files, turnover) will never be made accessible to any other company or third party. For the purpose of protecting your user accounts, your passwords are stored as hash code only and are not saved to the database in an unencrypted or directly traceable form. To help prevent brute force attacks, the server will only allow three incorrect password entries before shutting down the user account for a certain period of time.
|
|
Is the data transfer between each machine and the server encrypted?
|
|
Yes, it is, provided no cryptography restrictions apply in your country (some language versions of Microsoft Windows can only use a restricted version of the Crypto API, e.g. France). Usually, SiteRemote employs a combination of RSA for the key exchange and AES (Rijndael) for the symmetrical encryption. In addition, SiteRemote uses signatures to verify the identity of both client machine and server.
|
|
How can I exchange files between my local hard drive and my remote machines?
|
|
There are four different options to achieve this purpose:
-
You can use a file upload task as part of a job to transfer files to a multitude of machines at the same time.
To create a new job, please select the "Jobs" tab and click on "New task." The job editor will come up and allow you to add “Upload file“ tasks and specify which machines are supposed to execute the job using the checkboxes next to the folders and machines in the tree view.
-
VNC (can be downloaded under Tools) lets you establish a direct data connection to an individual machine and use this connection to exchange files and perform general file operations (delete, rename, copy, and move). When a VNC connection is established, the client desktop will be locked by default, but can also be unlocked.
-
You can use Terminal Commander (can be downloaded under Tools) to perform file operations on a remote computer. In contrast to a VNC connection, all of these operations will be performed in the background.
-
The file manager incorporated into the Web interface of SiteRemote makes it possible to automatically sync certain directories on the client machines.
The synchronization can be performed once or continuously.
|
|
How long will my files be stored on the SiteRemote server?
|
|
The SiteRemote server will check once a day if uploaded files are still referenced by any machine or job. If this is not the case, they will be deleted automatically. The same holds true for the log files of permanently deleted kiosks (not as long as they are stored in the recycle bin). By creating job templates, which contain steps for uploading file, you can store files on the server almost indefinitely (i.e. until your license runs out) to be able to later perform a particular job on another machine.
|
|
Which restrictions apply when uploading files to machines?
|
|
You can only use SiteRemote's Web application to upload files with a maximum size of 12MB and to assign them to different terminals by an upload job. It is, however, also possible to use the integrated file manager, Terminal Commander or VNC to transfer larger files to or from a specific terminal. Furthermore, the solutions allow you to perform basic file management operations on the client machines including rename, copy, move, etc.
|
|