Remote Management Server Settings

Settings

Advanced Settings

Common Questions


Enable

Kiosk Pro's Remote Management Server allows you to fully monitor and administer your iPad kiosks in the field through a simple web-based interface. This interface allows you to monitor the device through regular heartbeats and device health reports, upload new content to Kiosk Pro, and monitor kiosk usage from session length to the content and URL's your visitors are accessing.

Default: Off

Site Name

The site name is preconfigured in the Server's web interface under Site Management > Site Management > Site Settings > Site Name.

This setting, once configured, will apply to all your kiosks and cannot be changed in the future without updating each individual kiosk.


Kiosk Name

The kiosk name is the primary identifier of your kiosk. Each kiosk name must be unique to that iPad kiosk to identify it to the server.  

The kiosk name is required.  It must be composed of standard alphanumeric characters and cannot include any special characters, including periods, hyphens or underscores. 


Unit Name

The unit name acts as a secondary identifier, which can be either unique or non-unique, depending on your preference.  While it does not have to be unique, the unit name is required.  It must be composed of standard alphanumeric characters and cannot include any special characters, including periods, hyphens or underscores. 


Heartbeat Interval

The heartbeat interval determines how frequently Kiosk Pro checks in with the Remote Management Server and provides a device health report.

Options:

  • Disabled
  • 10 min
  • 30 min (default)
  • 1 hour
  • 2 hours

Send Visitor Session & Navigation Data

Added in 8.1

This setting allows you to control sending usage statistics to the Remote Management Server. Choosing to turn off this setting may be a good choice for users who are on a limited data plan, or who don't want visitor sessions to be tracked for privacy.

Default: On

XML Filename for Remote Settings Control

This setting allows you to configure a specific filename that will be used to initiate remote settings update through the Remote Management Server interface.

Default: settings.xml

To update the app’s settings through the remote management server, you’ll first need to create an .xml file with the preferred app settings (either manually using the templates on our site or automatically by exporting settings from a configured device).

Once you have that file, upload it through the Site File Manager in the server console and set up a content update including that file. More information on setting up content updates  is available here.

During any content update, the app will check to see if any files downloaded match the filename configured in this setting and if there is a match, the settings defined in the file will be applied and an event log confirming the update will be posted.

Using Multiple XML files
You can use multiple XML files in this setting by separating the filenames with a comma (for example: "texas.xml,store3.xml"). This is helpful if you need one configuration for multiple kiosks, and a different configuration for a specific kiosk. The XML files will be applied in the order they are listed.


Notification Events

These settings allow you to configure which events trigger certain types of event logs in the Remote Management Server. These types of event logs (info, warning, and error) can be configured in the server to change the overall status of your kiosk and to trigger email notifications.

  • None – no event log is sent to the Remote Management Server when this occurs, essentially turning off this monitoring function.
  • Info – the event log is generated and sent to the server as an information log. Generally, these logs are not used to change the status of the kiosk, but instead serve as markers.
  • Warning – the event log is generated and sent to the server as a warning log. Warning logs can be used to change the status of the kiosk and generally signify a minor malfunction.
  • Error – the event log is generated and sent to the server as an error log. Error logs can be used to change the status of the kiosk and generally signify a major malfunction.

Still stuck? How can we help? How can we help?