Debugging Webpages in the SiteKiosk Android Browser

SiteKiosk Android allows you to debug webpages that are running in the SiteKiosk Android browser.

To activate this option you have to go into the settings of SiteKiosk Android, then you have to switch into the extended configuration mode. The extended configuration mode will show some options that are otherwise hidden. These are either experimental options or options useful to developers.

To enable the extended configuration mode, you need to tab seven times into the upper left corner of the configuration, right on the SiteKiosk Android logo. Please note the waring dialog, that tells you about the experimental status of the settings that are now unhidden.

In the extended configuration mode, you should go to the System page and tick the option Enable web debugging.

This is the only thing specific to SiteKiosk you need to do. The rest of the debugging process is described in detail on the Google Developers pages.

After you are done with the debugging please do not forget to disable the web debugging option of SiteKiosk again.

Using the SiteKiosk Object Model for Automated Website Logins

In case you want SiteKiosk to automatically login to a website with a specific user and you can't use cookies for that, because you need to delete them regularly for security reasons, you can use the SiteKiosk Object Model to help you with the task. The SiteKiosk Object Model enables you to edit the Document Object Model (DOM) of the page, to automatically fill in the required user data and start the login process.

The example will use PROVISIO's own remote monitoring page to demonstrate the automated login.

Unless you are already familiar with the code of the page you want to use you can utilize the developer tools of any modern browser (e.g. Chrome, Firefox or IE) to view the code of the webpage and find out about the fields for user name, password and the way how to submit that data. Using the developer tools on the SiteRemote login page ( shows us that the id of the user field is UserNameEdt, the id of the password field is PasswordEdt. There are different methods the login can be coded on a webpage, here it is a div with the id LoginBtn2 that does a callback, so we just use the Javascript click method to simulate a click on that div. If your login page uses a form element, you can usually call the submit method of that form instead of using the click method, that we use in our example.

Now that we got the required information about the DOM elements of the page we want to login to, we can create our script.

//Flag used to prevent numerous login attempts, you may reset the flag using an event like OnScreenSaverBegin
var loginattempt = false;

//Message event used to detect navigation to login page
SiteKiosk.Logfile.OnMessage = OnMessage;
function OnMessage(seq, time, utcoff, awtype, awlevel, facility, text)
	//Check the SiteKiosk logs if the login page has been called and then call the function to attempt the automated login
    if(text.indexOf("Navigation:") !== -1 
	&& text.indexOf("") !== -1 
	&& loginattempt === false){
        //Delays the automatic login to give the page time to load
		evtid = SiteKiosk.Scheduler.AddDelayedEvent(1500, AutomaticLogin);
		loginattempt = true;
function AutomaticLogin()
	//Go through the open windows to find the browser window with the login page
    for (var i=1;i<=SiteKiosk.WindowList.Windows.Count;i++)
			//Make sure the window is a SiteKiosk browser window and it displays the login page
            if((SiteKiosk.WindowList.Windows(i).WindowType === 1 || SiteKiosk.WindowList.Windows(i).WindowType === 2)
			&& SiteKiosk.WindowList.Windows(i).SiteKioskWindow.SiteKioskWebBrowser.WebBrowser.LocationURL.indexOf("") !== -1)
                SiteKiosk.WindowList.Windows(i).SiteKioskWindow.SiteKioskWebBrowser.WebBrowser.Document.getElementById('UserNameEdt').value = "username";
                SiteKiosk.WindowList.Windows(i).SiteKioskWindow.SiteKioskWebBrowser.WebBrowser.Document.getElementById('PasswordEdt').value = "password";
            SiteKiosk.Logfile.Notification("Automated login failed for window: " + SiteKiosk.WindowList.Windows(i).ItemText);

The script uses a variable (loginattempt) as a flag to prevent more than one login attempt. You may use a SiteKiosk Object Model event like OnScreenSaverBegin or OnSessionEnd to reset the flag to allow for new login attempts.

The OnMessage event helps to detect that the login page has been visited in the SiteKiosk browser. Using the AddDelayedEvent method to give the page time to load, we call the AutomaticLogin method of the script to start the login process.

Within the AutomaticLogin method we use the WindowList object's Windows collection Count property to go through all open windows to identify all open SiteKiosk browser windows (WindowType 1 or 2) to find the one, which displays the SiteRemote login page ( Then we edit the DOM of the page and fill the user name and password fields with the required values and click the login button.

Save the above example as a .js file in the ..\SiteKiosk\html folder. Open the configuration, go to Start Page & Browser, select the Internet Explorer engine and use for example the Metro IE Skin. On the same configuration page click on Advanced and then add the .js file you created as an external script.

Start the SiteKiosk browser and go to An automatic login attempt by the script will occur. If you provided valid credentials as username and password, you will login automatically to your SiteRemote team, otherwise you will recieve an error message about invalid credentials.

For obvious reasons the code to identify the URL and the code to edit the required DOM elements will vary depending on the URL and code of the login page you need to use, please change these code parts accordingly.

Starting External Applications from Web Pages

Here are two examples that show how you can start external applications from a web site in the SiteKiosk browser. One example is for the Internet Explorer engine of SiteKiosk, the other for the Chrome engine.

The first example is a simple HTML page with two buttons for the IE engine of SiteKiosk. The first button just starts the Notepad application of Windows. The second button starts Notepad with a parameter that includes the full path to a file that should be displayed in Notepad.

<!DOCTYPE html>

<html lang="en" xmlns="">
    <meta charset="utf-8" />
    <title>App Start with the SiteKiosk Object Model (IE Engine)</title>

        //Initializing the SiteKiosk Object Model for IE engine

        //Running the external application using a universal method for optional parameter usage
        function runExtApp(extapppath, extappparameter) {
            var completepath = extapppath;

            //Check if parameter is not empty and adding parameter to path
            if (extappparameter !== "")
                completepath += " " + extappparameter;

            SiteKiosk.ExternalApps.Run(completepath, false);
<body style="margin-left:auto;margin-right:auto;margin-top:50px;text-align:center;">
    <input type="button" value="Start Notepad without parameter" onclick="runExtApp('c:/windows/notepad.exe','');"/><!--You can either use single forward slashes in the path-->
    <input type="button" value="Start Notepad with parameter" onclick="runExtApp('c:\\windows\\notepad.exe', 'C:\\Program Files (x86)\\SiteKiosk\\Html\\extapptest.txt');"/><!--Or you can use double backward slashes in the path-->

Embedded in the normal HTML and Javascript code is the SiteKiosk Object Model. The Run method of the ExternalApps object is used to start an external application.

SiteKiosk.ExternalApps.Run(completepath, false);

You can learn more about the Run method here.

For security reasons you need to specifically allow pages you are using the SiteKiosk Object Model on in the SiteKiosk configuration.

To test the above example code you can either put it on your web server but you can also save it locally as an html file in the ..\SiteKiosk\html folder of your SiteKiosk installation. The test code also assumes that there is a local text file available in ..\SiteKiosk\html named extapptest.txt for the parameter variant.

The result will look like this:

The second example is a slight variation from the first and demonstrates the same behaviour in SiteKiosk when using the Chrome engine. The SiteKiosk Object Model for the Chrome engine differs from the one for the Internet Explorer engine. The HTML and Javascript parts are identical but note the different way to initialize the Object Model.

<!DOCTYPE html>

<html lang="en" xmlns="">
    <meta charset="utf-8" />
    <title>App Start with the SiteKiosk Object Model (Chrome Engine)</title>

    <!--Initializing the SiteKiosk Object Model for Chrome engine-->
    <script type="text/javascript" src="file://C:/Program Files (x86)/SiteKiosk/SiteKioskNG/assets/siteKiosk/sitekiosk.js"></script>

        //Running the external application using a universal method for optional parameter usage
        function runExtApp(extapppath, extappparameter) {
            var completepath = extapppath;

            //Check if parameter is not empty and adding parameter to path
            if (extappparameter !== "")
                completepath += " " + extappparameter;

  , false);
<body style="margin-left:auto;margin-right:auto;margin-top:50px;text-align:center;">
    <input type="button" value="Start Notepad without parameter" onclick="runExtApp('c:/windows/notepad.exe', '');"/><!--You can either use single forward slashes in the path-->
    <input type="button" value="Start Notepad with parameter" onclick="runExtApp('c:\\windows\\notepad.exe', 'C:\\Program Files (x86)\\SiteKiosk\\Html\\extapptest.txt');"/><!--Or you can use double backward slashes in the path-->

The line that actually starts the external application is also specifically suited for the Chrome engine:, false);

The functionality and accepted parameters of the run method are the same as for the IE version. Currently there is no detailed documenation available for the SiteKiosk Object Model for Chrome-based browsers in SiteKiosk Windows and SiteKiosk Android, please contact our support to receive a basic documentation.

Using the Chrome example in one of the Chrome browser versions of SiteKiosk will look like this:

When working with external applications please note the information from the SiteKiosk documentation.

Allowing Android System Dialogs to set SiteKiosk Android as Default Browser for another App

As a secure kiosk solution SiteKiosk Android blocks Android system dialogs by default. Depending on the requirements of your kiosk project you might want to allow other apps to be started from within the SiteKiosk browser, for example the Android payment solution Adyen (Note: all of what is described here applies to apps that are called through specific links in the SiteKiosk browser, not to apps you are starting as an external app in SiteKiosk Android). If you need one of these apps to use SiteKiosk Android as the browser of choice to process the response of the app this selection needs to be done trough a system dialog that is called by your app while SiteKiosk is running. The aforementioned secure default behaviour of SiteKiosk Android will block this dialog. To be able to make your choice you need to temporarily allow Android system dialogs while SiteKiosk Android is running.

In order to allow another app to use SiteKiosk Android as its browser of choice you first need to open your SiteKiosk configuration editor, go to Security -> Allow assigned apps and add your app there.

The actual change required to allow Android system dialogs must be done by manually editing the SiteKiosk Android configuration. There are two ways you can do this.

If your Android device is registered with SiteRemote, you can log in to your SiteRemote team and go to SiteKiosk -> Configuration to import the existing configuration from the device, edit the configuration and publish it to one or more terminals.

If your Android device is not using SiteRemote, you can open the SiteKiosk configuration editor, go to System and select Export configuration from SD card. Now either edit the configuration locally on the Android device or copy it to computer to make the necessary change with an editor like Notepad. Afterwards copy it back to the SiteKiosk/config folder on your Android device and use the Import configuration from SD card option to activate the changed configuration.

Before editing your configuration you should make a backup, then you can skip reverting the following change that is only temporarily needed.

When you edit your SiteKiosk Android configuration look for:


Right before that section you need to add:

<App-android enabled="true"/>

The result should look like this:

<App-android enabled="true"/></Apps></AllowedApps>

Once you use your edited SiteKiosk configuration on your Android device, start your app from within the SiteKiosk Android browser and trigger the system dialog that lets you choose SiteKiosk Android as the default browser for that app. Select SiteKiosk Android in the dialog and make sure to use the option in the dialog to make this a permanent decision.

Now that you don't need to use the system dialog anymore you can switch to your configuration backup from before the change or remove the added XML tag from your configuration. For security reasons you should not permanently run SiteKiosk Android with system dialogs being allowed.

Using Self-signed Certificates in a SiteKiosk Chrome Browser Skin

Note: The following is no longer required when using SiteKiosk 9.5.4033 or higher.

In case your kiosk deployment is depending on self-signed certificates here are a few usesful hints in handling those for the Chrome engine version of SiteKiosk.

The certificate store for the Chrome Browser variants of SiteKiosk is generated from the Windows certificate store. This means that you can easily install self-signed certificates into your Windows certificate store, e.g. into the Trusted Root Certification Authorities. Make sure that you install the certificate into the right store, either for a user or the computer, based on your needs.

On the first start of one of the Chrome Browser skins of SiteKiosk under a user SiteKiosk will generate its own certificate list from the Windows store. The file is named SiteKioskNGCef-CA.perm and placed in the Temp folder of the user SiteKiosk is running under (%tmp%\SiteKioskNGCef-CA.pem). In case you make changes to the certificates you need to delete this file in order for SiteKiosk to regenerate the list.

Depending on your needs the file can be deleted in many different ways to force SiteKiosk to generate a new version. For example you can delete it periodically by using a batch file and the Windows Task Scheduler. You can also use the SiteRemote job system to create a two step job that deletes the file and then restarts SiteKiosk.

Distributing the SiteKiosk Windows Start Screen with SiteRemote

The SiteKiosk Windows Start Screen is a powerful and easy to use tool to create a customized kiosk terminal experience. If you want to use the same Start Screen setup, either newly created or changed, on more than one kiosk system, you can distribute the required files using different methods. In case your environment only includes a handful of PCs at the same location you may just use a USB stick, otherwise the more comfortable method is to use SiteRemote.

For our test scenario we create a very simple Start Screen using Template 3, that only includes a monochrome background and a text. Note that the complexity of the Start Screen you create does not alter the described scenario in any way. This is what our starting design will look like:

Once you are done creating or changing your Start Screen you need to save it by clicking on the corresponding icon in the Start Screen Editor. Once this is done you are presented with a dialog that tells you where all the files associated with the Start Screen are located. It will be the same location on all your SiteKiosk Windows installations (C:\Users\Public\SiteKiosk\content):

You will get this information dialog whenever you make any changes. This is a reminder that you now may need to distribute the changed files to all your PCs. You can now copy the content folder onto a USB stick and then copy the folder to the exact same location on all your machines, overwriting the previous version or use SiteRemote to achieve this. How to use SiteRemote for this purpose is what we want to look at in a little more detail.

First we create a new simple Start Screen design that will look different than the original design to symbolize the changes:

Again the changes need to be saved when leaving the Start Screen Editor. Once this has been successfully done, we open the Windows Explorer and browser to the content folder at C:\Users\Public\SiteKiosk. If you right click the content folder you can select Send to and then choose Compressed (zipped) folder. This results in a file at this very location:

Now we need a small tool that will unzip the folder once we have distributed it through SiteRemote. You can for example use the command line version of 7-Zip. The application is called 7za.exe and is available here in the 7-Zip Extra package.

Next just login to your SiteRemote team, go to the SiteKiosk tab and select Jobs from the submenu. Create a new job (you may save it as a job template if you like):

Set Job Name and Description to your liking and select SiteKiosk Windows as the Client Type. Now you need to add three job steps. The first one will be a File Upload that will place the 7za.exe file in the C:\Users\Public\ folder. Make sure to use the slash at the end of the file path. Also choose Overwrite to make sure any existing version at that location is overwritten:

The second step will again be a File Upload and upload the file with the complete Start Screen content. Use the same settings as with the first step:

The third and last step will be of the Run Executable type. If will use the following command line to run 7za.exe and unzip the content of the archive to its final destination:

"C:\Users\Public\7za.exe" x "C:\Users\Public\" -aoa -oC:\Users\Public\SiteKiosk

Leave the other options as they are, especially leave Invisible execution with administrative rights selected:

Finally assign the jobs to the desired machines and wait for it to complete. Note that the changes will only come into play once the Start Screen is refreshed, to speed things up you can send another SiteRemote job that restarts SiteKiosk.

Using Adobe Flash with Chrome Browser Skins of SiteKiosk 8.91-9.1

Please note that the description below, describing how to manually make changes to the configuration of SiteKiosk to enable Flash, will no longer be required with the release of SiteKiosk 9.2. In SiteKiosk 9.2 you can enable Flash support in the configuration under Start Page & Browser -> Chrome Browser -> Customize -> Settings.

For security reasons using Adobe Flash with the Chrome Browser skins (“Chrome Browser” skin and “Chrome Fullscreen Browser” skin) is not supported by default in SiteKiosk 8.91-9.1.

If Adobe Flash is required you will normally need to switch to an Internet Explorer skin where Adobe Flash is supported with the corresponding Adobe Flash Plug-in for IE (for historical reasons).

If you require using Adobe Flash with the Chrome Browser skins you can proceed as follows:
1. First you need to download and install the 32-bit Adobe Flash Player “for Opera and Chromium – PPAPI” on your Windows operating system:

2. Next step is to add the Adobe Flash PPAPI Plug-In to SiteKiosk’s Chromium Engine.
To do this you need to edit the SiteKiosk configuration file (…\SiteKiosk\Config\YourConfig.skcfg).

- Open the SiteKiosk configuration file you want to use with an editor like Notepad or Notepad++.
- Search for the line
"showTaskBar": true,
- Then add these lines right before:

"browserEngine": {
        "commandLineArguments": {
            "set": ["ppapi-flash-path=C:\\Windows\\SysWOW64\\Macromed\\Flash\\pepflashplayer32_20_0_0_267.dll","ppapi-flash-version="],
            "remove": []

It should look like this:

"system": {
    "password": {
      "enabled": false
    "browserEngine": {
        "commandLineArguments": {
            "set": ["ppapi-flash-path=C:\\Windows\\SysWOW64\\Macromed\\Flash\\pepflashplayer32_20_0_0_267.dll","ppapi-flash-version="],
            "remove": []
    "showTaskBar": true,
    "userAgent": {

"ppapi-flash-path" gives the information where to find the PPAPI Flash Plug-In
"ppapi-flash-version" reports the given version for the PPAPI Flash Plug-In

In this example we have installed the Adobe Flash PPAPI version to the default path (32 Bit) "C:\Windows\SysWOW64\Macromed\Flash\pepflashplayer32_20_0_0_267.dll".

When installing other (newer) Adobe Flash versions you need to adjust these entries.

3. Finally save the changes and start SiteKiosk.
When you start SiteKiosk and e.g. go to you will see the Adobe Plug-In is activated:

Automatic Video Playback under SiteKiosk Android

In a few days 2015 will come to an end, therefore PROVISIO wants to wish you all the best for 2016 and we want to keep the last post for 2015 short. In the past we had a few support requests asking about automated video playback on an Android device. If you are not using the Digital Signage feature of SiteKiosk Android, with which you can create a campaign to automatically playback and even loop a video by using the Digital Signage editor of SiteRemote, there are some limitations you need to be aware of.

Automated video playback is limited in Android. This is not special to SiteKiosk Android but a general behaviour of the operating system. That feature is meant to save bandwidth and battery power. It has been added to the Android operating system on purpose and affects browsers running on Android. This means it also affects the browser part of SiteKiosk Android.

There are code examples floating around the web that can work around this behaviour to a certain degree. One of these examples can be found on github, the  code to autoplay a video is available here (

If you not only want to use autoplay but also would like to loop the video, you can find an example here (

At the time of this writing the above examples have been tested with SiteKiosk Android 2.4 on different Android 4.x versions and was working.

Accessing 64-Bit System Folders and Registry Paths from the SiteRemote Job System

The SiteRemote component on the Windows client side is a 32-bit application. This means that the SiteRemote jobs you are running on the client are executed within a 32-bit context. This is relevant when your are using a 64-bit system and you for example want to access the SOFTWARE folder in the Windows registry. By default you will then target the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node path instead of HKEY_LOCAL_MACHINE\SOFTWARE. The same applies to applications from the System32 folder, by default a 32-bit application will be redirected to C:\Windows\SysWOW64 instead of using C:\Windows\System32.

What to do, when you explicitly need to access the 64-bit part of the registry or start a 64-bit system application? Microsoft offers solutions that you can use in your SiteRemote jobs to mitigate the behaviour described above.

First let's look at the Windows registry. To for example set registry values for a 64-bit application by using a SiteRemote job you can create a job with the action type Run Ececutable and use the following command line:

reg import C:\Windows\Temp\test.reg /reg:64

This calls the reg.exe application with the parameter import that specifies the path to .reg file that includes the registry data you want to write to the registry (for this example we assume that there is already a test.reg file in c:\Windows\Temp). After that you use the /reg:64 switch to specify that you want to import the data from the .reg file to the 64-bit part of the registry. For the purpose of this test the content of the .reg file will look like this:

Windows Registry Editor Version 5.00

"TEST"="Test Value"

A SiteRemote job step that includes the above will look like this:

A successful execution will show this result:

When not applying what has been described above the test value would have been written to the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node path.

Next we will look at starting a 64-bit application. For this demonstration we will use the 64-bit version of notepad.exe located in C:\Windows\System32 on a 64-bit Windows system. In order to be able to start this application from the 32-bit environment of the SiteRemote client we need to use a batch file that makes use of the Sysnative folder redirection of Windows. Using Sysnative as the folder name will redirect any request, even those from a 32-bit application, to the native system folder of 64-bit Windows system it is used on. Our batch will look like this:

start %windir%\Sysnative\notepad.exe

For this demonstration we will place it in C:\Windows\Temp as test.bat. Of course you could also create another SiteRemote job step that uploads the file to the client. Next we create the job step that executes the batch file. The command line looks like this:

c:\windows\syswow64\cmd.exe /c "start c:\windows\temp\test.bat"

For the path to the cmd.exe we could actually also use c:\windows\system32\cmd.exe. This will automatically be translated to the SysWOW64 folder on a 64-bit system.

Our job will look like this:

For the purpose of this demonstration we will choose the option Visible execution with user rights to make notepad.exe show up. Executing the job on the target system will give us this result:

Note that the task manager shows that this is actually the 64-bit version of notepad.exe (visible from the missing 32 bit appendix).

Using Input Devices in the SiteKiosk Start Screen

The Start Screen start page of SiteKiosk is Chrome-based and allows you to freely configure a start page for SiteKiosk that matches your requirements. It also supports the SiteKiosk Object Model to further increase the customization options. Because the design is Chrome-based it uses the new SiteKiosk Object Model for the Chrome-based part of SiteKiosk. This Object Model is still in the making so the most current state of the preliminary documentation can be obtained through our support department. Interested developers can just send us a short email.

The following demonstration shows you how to use the SiteKiosk Object Model in the Start Screen (there is also one other example usage documented here). We will use the new SiteKiosk 9 feature to read input from any USB input device that uses keyboard emulation as an example how to achieve this goal.

First create a new configuration for SiteKiosk and select the Start Screen on the Start Page & Browser page. Click the customize button and for the purpose of this demonstration pick Template 3. Create a new HTML widget and edit it to add the code that contains the SiteKiosk Object Model.

The code to add is loosely based on the general Chrome-based example described in more detail in the SiteKiosk help. The code we will use for the Start Screen looks like this:

	var callbackFunc = function (data, deviceName) {"TEST",0,deviceName + " registered the following data: " + data);

	function registerDevice() {
		var deviceName = document.getElementById("devicename").value;

		if(deviceName == "")"TEST",0,"No input device found!");

		var device = parent.siteKiosk.devices.getByName(deviceName);

		if(device == null)"TEST",0,"No input device found!");

		device.valueChanged(callbackFunc);"TEST",0,"Registered input device: " + JSON.stringify(device));
<div style="background:white;padding:10px;">
	Test page for reading the input of keyboard emulation 
	devices configured in the configuration of SiteKiosk 
and writing the received data into the SiteKiosk log.<p />
		Listen to input from this device that has been 
		configured in SiteKiosk: 
		<input id="devicename" tpye="text" /> (state the device name) <button onclick="registerDevice()">Register the listener</button>

The most significant changes to the original code example are that you leave out the line that initializes the external script for the Object Model:

<script>(new Function(_siteKiosk.getSiteKioskObjectModelCode()))();</script>

This is because the Object Model is already initialized in the parent of the HTML widget, therefore you can access all objects, methods, etc. of the Chrome-based SiteKiosk Object Model by adding parent when you use it in the Start Screen:"TEST",0,deviceName + " registered the following data: " + data);

After you copied the code to the HTML widget you can save the changes to the Start Screen and go to the configuration page for Input Devices. Add an input device. For testing you may just attach an additional keyboard to your computer, but do not use the one attached to your computer already or a keyboard that is exactly the same model, as the device will be exclusively used for the input device feature and therefore does not accept keystrokes for normal usage, e.g. hitting Escape to close SiteKiosk, once you start SiteKiosk. Choose a display name for your device, this will be necessary to identify the device in the script, as it is used to register the device listener:

For this example you should also enable the debug output window under Logfiles in the configuration of SiteKiosk. Then save the configuration and start SiteKiosk in Run Once mode. Type the device name you used in the SiteKiosk configuration into the input field and click on the button to register the device listener. If the registration succeeded you will see a log entry. The same applies if you now create input from the attached device: