Using Browser Detection to Place SiteKiosk Object Model or Kiosk Project Specific Code

When you are doing a kiosk project with SiteKiosk you might plan to use web pages that are utilized for a kiosk browser as well as a normal web browser. In that case you don't want to create and maintain the web pages twice, therefore the kiosk code should be integrated into the normal code. To execute the kiosk specific code only on a kiosk system you need to detect that it is running in SiteKiosk. SiteKiosk provides you with two options for that.

One Option is to use the user agent. SiteKiosk uses the Internet Explorer WebBrowser control, therefore it has a user agent that identifies it as the underlying Internet Explorer. By default SiteKiosk adds SiteKiosk version information to the user agent. Here is an example of that:

Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SiteKiosk 8.8 Build 1650)

The setting for the user agent can be found in the configuration of SiteKiosk under Start Page & Browser -> Advanced Computer Identification. There you will also find an option to add any text you want to the user agent. The following is an example that bases the browser detection on the user agent:

	<title>SiteKiosk User Agent Example</title>
		<span id="SiteKioskOrNot">...</span>
	<script type="text/javascript">
		if (navigator.userAgent.indexOf("SiteKiosk") !== -1){
			document.getElementById("SiteKioskOrNot").innerHTML = "You are using SiteKiosk.";
			//Place code for your kiosk project here.
			document.getElementById("SiteKioskOrNot").innerHTML = "You are not using SiteKiosk.";
			//Place code for normal web browsers here.


The other option is to use try-catch in your code. This option is only suitable when you explicitly want to use the SiteKiosk Object Model as part of your kiosk project code. The try-catch basically tries if the initialization of the SiteKiosk Object Model works or not. Here is the code example for that:

	<title>SiteKiosk Try-Catch Example</title>
		<span id="SiteKioskOrNot">...</span>
	<script type="text/javascript">
			document.getElementById("SiteKioskOrNot").innerHTML = "You are using SiteKiosk.";
			//Place code for your kiosk project here.
			document.getElementById("SiteKioskOrNot").innerHTML = "You are not using SiteKiosk.";
			//Place code for normal web browsers here.

Note that you need to allow script permission for the SiteKiosk Object Model to be executed in SiteKiosk. You can do this in the configuration of SiteKiosk under Access/Security -> URLs with Script Permission. Another example for the try-catch option can be found in the SiteKiosk Object Model documentation at the bottom of this page.

Customizing a SiteKiosk Android Browser Design

Accompanying the release of SiteKiosk Android 2.0 this blog post will show you how you can customize a Browser Design. This way you can make your SiteKiosk Android stand out from the rest, e.g. by creating a browser skin in your corporate design.

The following steps can be performed directly on a tablet, but I would suggest doing it on a PC to ease the editing process. First you need to download the Android installer package for SiteKiosk Android from our website:

The installer package is basically a zipped archive, therefore the next step is to unzip the archive, using your favorite tool for that (e.g. Winzip, Winrar, 7zip, etc.).

In the unzipped archive you will find numerous files and folders. The ones we are interested in are all in the folder named assets. The folders required for our customization are apps, common (if available), external, provisio and siteKiosk. 

For our experiment we concentrate on changing the look of the browser. We therefore change a few subfolders deep in the apps folder. In ..\assets\apps\browser\skins we find all the browser designs (or skins) that are included in the SiteKiosk Android installer. To start creating our own design we make a copy of the folder named metal and rename the copy to MyBrowser (of course you can choose any name you like, but if you do, keep that in mind for the upcoming changes).

Now we step into the MyBrowser folder. In it, we will find the images subfolder. In that subfolder are a number of png files which make up the design of a browser skin. You will notice that all but the toolbar.png file are available in two sizes. This is to cater for different pixel sizes of Android devices. You are free to change the logos and icons to your liking. Just make sure to keep the original image sizes and the placement of icons, so for example do not put the refresh icon in the place that the home icon is currently using otherwise you would mix up the functions of your browser skin. The one image file that is only available in one size is the background of the browser tool bar, again you are free to change this to whatever you like, but please keep the size. The next screen shows my colorful (and possibly eye-hurting) design attempt that will be used to illustrate our little tutorial.

Next we create a logo icon for our browser to show in the configuration when we select the browser design. Go to the ..\assets\apps\config\images folder and create two png files for the icon, e.g. MyBrowser_logo.png and MyBrowser_logo2x.png. Again two version to cater for different pixel sizes. You may use the two sk_android_logo files as a base for your own creation.

Now that we are done with the actual design, we have to edit six files to make our browser design show up the way we want. In the folder ..\assets\apps\browser are two files named browserSettingsDescription.xml and browserSettingsDescriptionStrings.xml. Both have to be opened with an editor, e.g. Notepad, Notepad++, etc.

In the file browserSettingsDescription.xml add a new Option tag. Look for the Option tag with the name metal and add the new entry after that:

        <Option name="Metal" title="$Browser/BrowserSkins/Metal.Title" iconName="application-icons" iconIndex="34"></Option>
	<Option name="MyBrowser" title="$Browser/BrowserSkins/MyBrowser.Title" iconName="MyBrowser-icon" iconIndex="1"></Option>

The referenced iconName will be created later. The iconIndex can be 1 as our own logo picture is not part of a single file with more than one logo.

Next is the file browserSettingsDescriptionStrings.xml. We have to add the title for our browser design, so there is a caption next to the logo in the SiteKiosk configuration. Open the file in an editor and search for Metal.Title. You will find 5 matches. Add a new line after each of the matches with your own browser title.

<String Id='Browser/BrowserSkins/Metal.Title'>Metal</String>
<String Id='Browser/BrowserSkins/MyBrowser.Title'>MyBrowser</String>

Let's step into a new folder. This time it is ..\assets\apps\browser\skins\MyBrowser. You will see three .tmpl files in there. Open all of them with an Editor and change all occurrances of the word metal into MyBrowser.

On to the last file that has to be changed. It is the file icon.js in the folder ..\assets\apps\config\widgets. After you have opened it, a few addImageMap entries have to be added. Look for metal-fullscreen-icon and after that line we add our image maps.

addImageMap({ name: "metal-fullscreen-icon", src: "../skins/metal/images/sk_android_fullscreen_icon.png", width: 42, height: 42 });
addImageMap({ name: "MyBrowser-icon", src: "images/MyBrowser_logo.png", width: 29, height: 36 });
addImageMap({ name: "MyBrowser-browserbar-36-icons", src: "../skins/MyBrowser/images/sk_android_browserbar_36_icons.png", width: 38, height: 38, padding: 0, states: 3, icons: 8 });
addImageMap({ name: "MyBrowser-browserbar-25-icons", src: "../skins/MyBrowser/images/sk_android_browserbar_25_icons.png", width: 27, height: 27, padding: 0, states: 3, icons: 2 });
addImageMap({ name: "MyBrowser-browserbar-logo", src: "../skins/MyBrowser/images/sk_android_browserbar_logo.png", width: 119, height: 37 });
addImageMap({ name: "MyBrowser-fullscreen-icon", src: "../skins/MyBrowser/images/sk_android_fullscreen_icon.png", width: 42, height: 42 });

We are done with our browser design. The next step is to copy the files over to the right location on the Android tablet. Attach the tablet to the PC, usually using a USB cable. Locate the SiteKiosk folder on the tablet. You can find it under [externalStorageDir]/SiteKiosk which usually translates into /mnt/sdcard/SiteKiosk. Using the USB connection from the PC the path is something like ..\Internal Storage\SiteKiosk. Copy all the four subfolders from the assets folder described above into the SiteKiosk folder on the tablet.

/mnt/sdcard/SiteKiosk/common (if available)

Start SiteKiosk and open the configuration. If you are using SiteKiosk 2.6 or higher, go to Security and select the option to allow custom SiteKiosk applications. Go to Application > Browser > Design. You should see the newly added MyBrowser design there. Select it.

Go to Application > Browser > Advanced Settings > Logo and select your logo design there. The path usually would be something like mnt/sdcard/SiteKiosk/apps/browser/skins/MyBrowser/images/sk_android_browserbar_logo.png.

Finally select Start SiteKiosk from the treeview on the left and have a look at your design in the SiteKiosk Android browser.

Please remember we kept things pretty basic for this small tutorial, as this was about showing you the places that need to be edited to have your own SiteKiosk Android browser design and not giving lessons in design. Using your own icon, background and color design you can have a completely unique look.

Display TV content in SiteKiosk (using a Hauppauge TV device)

If necessary you can also display content from a TV device in the SiteKiosk Browser using an ActiveX control.

Some manufacturers already provide an ActiveX control for their TV device (if it works in the Internet Explorer 32 Bit it should also work in the SiteKiosk Browser).

Otherwise you will find the description about how to develop an ActiveX and a basic example about how to use it with SiteKiosk in this article.
Provisio developed a simple ActiveX Control Based on a SDK from Hauppauge that can be used with Hauppauge TV Cards to display TV content in the SiteKiosk Browser.

In the following you will find the description how to install and use it in SiteKiosk.
At the end of this article you will also find the download link to a ZIP that contains the ActiveX source which developers can use to make additional customizations to the ActiveX.
The provided ActiveX can be used with Hauppauge devices that are supported with the actual WinTV 7 software from Hauppauge. It was created with the SDK that Hauppauge provides at request.

A. An actual Windows system (Windows XP / Windows 7 / Windows 8)
B. The WinTV 7 Redistributable SDK software from here:
C. The Microsoft .NET Framework v4.0.30319 has to be installed on the PC too.
D. The ZIP containing the ActiveX and 2 demo HTML files from here:
E. SiteKiosk (for using the ActiveX in the SiteKiosk Browser):

1. The WinTV 7 Redistributable SDK software from Hauppauge has to be installed on the computer where you want to use the ActiveX (the WinTV 7 Software is also included)

2. Start the WinTV 7 Software and configure the WinTV device. The TV channels have to be configured with the WinTV Tool before, so that the ActiveX will find the channels.

3. Unzip the file "" and copy the folder "WinTVCtrl" to "...\SiteKiosk\Html\"

4. Register the ActiveX dll as follows:
- Open the command line (cmd.exe) with "Run as administrator" and enter this command (on x64 Systems use "C:\Program Files (x86)\..."):
"C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe" "C:\Program Files\SiteKiosk\Html\WinTVCtrl\WinTVCtrl.dll" /codebase

For testing/using the ActiveX choose the "test_WinTVCtrl.html" or the "test_WinTVCtrl2.html" at "C:\Program Files\SiteKiosk\Html" (on x64 Systems use "C:\Program Files (x86)\...") in SiteKiosk configured as start page (-->Start Page & Browser).
Then start SiteKiosk in "Run once" mode first for testing.
When opening the web page it may take some seconds until you can watch the TV content because the ActiveX will be initialized.

The "test_WinTVCtrl.html" provides some buttons to control the displayed content (choose a channel and use the watch button to display the TV channel that is chosen)

The "test_WinTVCtrl2.html" will just display the TV content and switch the channels automatically every 30 seconds.

Feel free to customize the HTML files to fit your needs or even create your own HTML file and implement the ActiveX.

In case you want to customize the ActiveX or develop it further you can download the (Visual Studio) source files for the ActiveX Control from here:

Furthermore you would need the full WinTV SDK that Hauppauge provides at request.

Creating a Custom SiteRemote Alert

The SiteRemote server already offers a variety of alerts that help you maintain your kiosk systems. But for specific projects it is helpful to be able to create additional alerts that can trigger an email or sms to notify about a possible problem. Customers running their own SiteRemote server can create their own custom alerts. Creating such an alert requires work on the client side (SiteKiosk) and on the server side (SiteRemote). The following is a short guide to creating a custom alert:


1. SiteKiosk

To create new alerts you first have to write the alert event into the log file of the SiteKiosk client machine. To do this, you can use the SiteKiosk Object Model which can also be accessed from other programming languages. The log entry you create with the SiteKiosk Object Model will be used to trigger SiteRemote alerts.

The Write method of the SiteKiosk Object Model is used to create log entries for custom alerts:

The Write method has the follwing parameters:


Short value that specifies the type.


Short value that specifies the level.


String that specifies the facility.


String that specifies the text to write.


The Type property contains the type of the log file message. Possible types are:

The Level property contains the level of the log file message. Possible levels are:

The Facility property contains the description of the device, plugin or component (

The Text property contains the text of the log file message (

See the LogMessage object for further information about the parameters (


More information about the SiteKiosk Object Model can be found here:


The example code for our custom alert looks like this:

SiteKiosk.Logfile.Write(9999, 40, "CustomFacility", "Custom Text to write");


When adding this to an HTML example page we will get this:

		<title>Write Log</title>
		<SCRIPT TYPE="text/javascript">
		function WriteLog(){
			SiteKiosk.Logfile.Write(9999, 40, "CustomFacility", "Custom text to write");
		<input type="button" value="SiteKiosk Logfile Write Button" onclick="WriteLog()">

Copy & paste the code into an editor (e.g. Notepad) and store the html file (e.g. Alert.html) at the path “…\Sitekiosk\Html”. Configure the html file as the start page and run SiteKiosk to test. The log entry will be created when you click the button.


2. SiteRemote Server

With the example above you will see a log entry like this appearing on the SiteRemote Server:

40 9999 2012-07-17 13:51:22 +0200 [CustomFacility] Custom text to write

In order to get an alert notification from this log entry you created, you will need to edit the Notification settings on the Settings page of the Administration section of your SiteRemote server installation.

To receive an alert email and/or SMS, you need to create the corresponding entries under the “Notification settings”.  Create the entries by adding new strings with the text for the alert message (-->Users-->username-->Alert Notifications-->Notification options for results).

Please follow the next steps to configure your SiteRemote server to show a custom alert:

A. Open the SiteRemote Administration page and go to the “Strings” tab. Select the language and use the “Add new” button to create a new string. The next free ID will be chosen automatically.  Enter your message in the text field.

For our example (ID 3545 CustomEventTitleText / ID 3546 CustomEventBodyText / ID 3547 CustomEventGroupID):

Note that for SiteRemote Server 6 and higher you need to create the strings twice. Once under the Web-Strings tab and once under the Report-Strings tab. Both can be found on the Strings page of the Administration. Use the same IDs under both tabs.

The following variables can be used to get the server name, the alert text and the alert time from the client in your alert notification:

$(Server_name_short) receives the error "$(Alert:LogText)". Error occurred at $(Alert:LogLocalTime) local machine time.

Use the existing entries for “SiteCashError” as a reference:

B. After creating the new strings, open the “Settings” page.

Under “Notification settings” follow the “Edit configuration” link.

Press the “Add New” button at the “LogMessage options” section.

You will see a form like this:

Enter the corresponding values for your log entry with “Fire if message count > 0” and “Period (min): 0”. In this case we chose the event name “CustomEvent”:

Use the Save link to save the new entry.

C. Scroll down to the “Notification Events” and press the “Add New” button.

The “Name” value must be an exact match to the “Event name” that was used under LogMessage options section.

The value for "Bit" is a number to represent the ID of the Event.

Select the next free Bit number or the highest available number.

For the different IDs enter the string number(s) you have created.

- OnlineTitleId: Title text on the web page

- OnlineTextId: Body text on the web page

- MailTitleId: Title text Email

- MailTextId: Body text Email

- SMSTitleId: Title text SMS

- SMSTextId: Body text SMS

For our example this means:

Use the Save link to save the new entry.

D.  Scroll down to “Groups” and press the “Add New” button.

The “Events” value must be an exact match to the “Event name” that was used under the LogMessage options section.

The value for "Bit" is a number to represent the ID of the Event.

Select the next free Bit number or the highest available number.

Enter the string number you created for GroupID in the “TitleID” box.

For our example:

Use the Save link to save the new entry.

Click the OK button at the bottom of the page to save and move on to the next step.


Last, login to your SiteRemote team account and activate the new alert on the settings page (-->Users-->Username-->Alert Notifications-->Notification options for results).

For our example:

Now, when you press the button that was created to write the SiteKiosk log file entry, you will get an alert when logged into your team account and via email and/or SMS (if configured).


Example online text:

Example email text:

When an alert is triggered, it will be displayed in your team account and sent by email if that option is configured. If you do not receive the email even though the alert is displayed, you should check the “Delay” that is configured under “-->Settings-->General-->Alerting Delay” (default 15 minutes).

Tools for Creating an Automated SiteKiosk Installation

Deploying a SiteKiosk rollout on a great number of terminals can become a lot easier using some of the tools provided by PROVISIO. With the help of these tools you can create a standalone installation script that you bundle with the required files or use it to create an installation package with one of the deployment toolkits available on the market or prepare a machine to create an image using an imaging software. One of the deployment toolkits is Microsoft's SCCM, which has been the topic of an FAQ article already.

The following is an overview of the tools and what you can do with them.

The installer of SiteKiosk allows you to conduct a silent installation as part of a script or using a deployment toolkit. To do so you need to start the executable of the installer that can be downloaded from our website with parameters. A basic silent installation of SiteKiosk looks like this:

sitekiosk.exe /S /V"/qn"

A full list of available parameters for the silent installation, including examples, can be found in this FAQ article.

During the installation of SiteKiosk a little tool will be copied to the installation path of SiteKiosk (default path: C:\Program Files\SiteKiosk). The tool ist SKStartup.exe (default path: C:\Program Files\SiteKioskSKStartup.exe). This tool can be used to register SiteKiosk and set the startup options. To register SiteKiosk use the license name and license number you received from PROVISIO or a reseller as parameters for SKStartup.exe:

SKStartup.exe /l "YourComp - 10 License(s)" /s 9QH6H-YWF7V-R2PAR-WT3MT-DX6F6

The parameter /l is followed by the license name and the parameter /s is followed by the license number.

SKStartup.exe can also be used to automatically set the desired start settings for SiteKiosk, e.g. Autostart. For this a bit of extra work is required. First you need to create a SiteKiosk configuration file that fits your kiosk project using the SiteKiosk configuration tool, preferrably safe it to the default location for SiteKiosk configuration files: C:\Program Files\SiteKiosk\config\. Next you start SiteKiosk and from the SiteKiosk Quick Start menu you select Customized. Choose your configuration file and set all the start options as desired, then click on the Export button to export your startup options. This creates a file called startup.xml. This file needs to be part of your installation package. You can copy it to wherever you want, e.g. directly into the SiteKiosk installation path once the installation is done. Now you can use the /i parameter with SKStartup.exe to apply the start settings on any of your SiteKiosk terminals:

SKStartup.exe /i startup.xml

Make sure to also copy the SiteKiosk configuration file you created to the same location you used while creating the startup.xml file on all of your machines.

You can of course register SiteKiosk and set the startup options in just one step:

SKStartup.exe /i startup.xml /l "YourComp - 10 License(s)" /s 9QH6H-YWF7V-R2PAR-WT3MT-DX6F6

Note that in order to use the SKStartup.exe you need to first install SiteKiosk, e.g. using the silent installation and only then register SiteKiosk and set the startup options. The SiteKiosk configuration file and the startup.xml file can be created on any PC you have installed SiteKiosk on, you can even use an unregistered version for it.

The SKStartup.exe is also described on this page of the SiteKiosk help.

An optional step is to automatically register the SiteKiosk terminal with a SiteRemote team. This is obviously only required when you want to use the remote management and digital signage features of SiteRemote. Within a SiteRemote team you can find the Extras button which will bring up the Apps page where you can find the Auto Register Tool. You can install the tool on any PC. It provides a small GUI that lets you select your SiteRemote client type and the data required to register a terminal at a SiteRemote server. Once this data is provided a file will be created with the registration data necessary to register a client. The GUI also provides information where this file needs to be copied on a client to start the registration process, the path depends on the client type. Make the resulting file a part of your installation package and during the installation process, after SiteKiosk has been installed, copy it to the required location. Once the file is at the final location and the terminal is able to reach the SiteRemote server it will be registered.

When creating an image instead of an installation script or package you don't need to use most of the tools as you can do most of the required steps with the normal GUI options of SiteKiosk. Use the imaging software of your choice and make sure to follow its procedures to create a working image. Install the operating system and all required updates and drivers. Also install other software like Flash or Acrobat Reader if desired and apply all available updates to them as well. Make sure everything that requires it is registered.
Now you would install SiteKiosk and prepare the configuration to include all the settings required for the kiosk project. You can also register SiteKiosk, if your license count covers enough machines. You may also configure the desired start settings.
Next you are ready to shutdown the machine and create the image using an imaging software.
An optional step before shutting down the machine to make the image would be to prepare it for use with SiteRemote. An important thing to remember is to not register the machine with SiteRemote before you create the image, otherwise all machines using that image will show up as the same machine under SiteRemote. Instead use the Auto Register Tool described above to create the auto registration file. Before copying the file to the required folder (see the instructions in the GUI of the Auto Register Tool) make sure to disconnect the internet connection to prevent the machine from directly registering itself. Once the file is in place you are ready to start the imaging process.

Whether you prefer a script, a deployment toolkit or an image to deploy a great number of SiteKiosk terminals, the above tools should provide you with the necessary help to make this an easy task.

Verschiedene Lösungen für das Kompatibilitätsproblem von SiteKiosk unter Windows 7 mit Internet Explorer 10

The English version can be found here:

Das Kompatibilitätsproblem, dass die SiteKiosk Versionen 7.1 bis 8.6 unter Windows 7 bei installiertem Internet Explorer 10 betrifft (Windows 8 Systeme sind nicht betroffen), ist ab der SiteKiosk Version 8.7 gelöst worden. Die empfohlene Problemlösung ist daher ein Update auf mindestens SiteKiosk 8.7 durchzuführen. Das Update ist kostenlos für alle Nutzer von vorhergehenden SiteKiosk 8 Versionen und für alle Kunden mit SiteKiosk 7.8, die ihre Lizenz seit August 2011 erworben haben.

Kunden, die kein Update auf mindestens SiteKiosk 8.7 durchführen können oder wollen, stehen die folgenden Lösungen zur Verfügung, um das Problem zu lösen:

  1. 1) Laden Sie diesen kleinen Fix herunter, den wir auf unserer Webseite anbieten und führen Sie die Exe-Datei aus.

    Sie können den Fix auch als Silent-Installation durchführen. Nutzen Sie dafür auf der Kommandozeile den Parameter /s (IE10patch.exe /s).

    HINWEIS: Nutzer mit einer SiteKiosk 7.1 Version auf Windows 7 64Bit Systemen müssen vor der Anwendung der Fix-Datei mindestens auf SiteKiosk 7.5 updaten.

  2. 2) Die zweite Lösung ist für alle Nutzer verfügbar, die für die Fernverwaltung Ihrer Kiosk Terminals nutzen oder einen eigenen SiteRemote Server betreiben.
    Wenn Sie sich in Ihr Team unter einloggen und zum Aufträge-Tab gehen, finden Sie dort eine Auftrags-Vorlage mit dem Namen Windows 7 IE 10 Fix. Weisen Sie diesen Auftrag Ihren Windows 7 Maschinen zu. Lesen Sie bitte zuvor die Ausführungen die in der Auftragsbeschreibung stehen.
    Das Nachfolgende gilt nur für Kunden, die Ihren eigenen SiteRemote Server betreiben. Kunden mit einem eigenen SiteRemote Server können die obige Auftrags-Vorlage selbst erstellen. In einem Team auf Ihrem SiteRemote Server gehen Sie bitte zum Aufträge-Tab und klicken dann unten auf der Seite auf Neue Vorlage. Wählen Sie einen Namen und eine Beschreibung und als Clienttyp SiteKiosk. Wählen Sie dann Datei hochladen als Aktionstyp und klicken Sie auf Hinzufügen. Laden Sie die Datei win7ie10fix.js aus diesem zip-Archiv zum SiteRemote Server hoch und nutzen Sie %SiteKioskPath%\ als Zielpfad. Stellen Sie sicher, dass Sie das Überschreiben von bestehenden Dateien auswählen. Jetzt selektieren Sie bitte Ausführbare Datei starten als Aktionstyp und klicken auf Hinzufügen, um einen zweiten Auftragsschritt zu erstellen. Nutzen Sie wscript.exe "%SiteKioskPath%\win7ie10fix.js" als Befehlszeile. Stellen Sie dann Sichtbare Ausführung mit Benutzerrechten ein. Als optionalen Schritt können Sie noch den Exit-Code auf einen Wert von 0 setzen und dies als erfolgreiche Ausführung markieren. Speichern Sie die neue Vorlage und weisen Sie diese Ihren Windows 7 Maschinen zu.


Falls Ihr Rechner bereits von dem Problem betroffen ist und sich in einer Startschleife befindet, können Sie die in diesem FAQ-Artikel aufgeführten Instruktionen verwenden, um das System zurückzusetzen:

Solutions to Fix the Compatibility Issue with SiteKiosk and IE10 on Windows 7

The compatibility issue that affected SiteKiosk versions 7.1 to 8.6 under Windows 7 systems with Internet Explorer 10 (Windows 8 systems are not affected) has been fixed in SiteKiosk version 8.7 and higher. The recommended solution to the problem is therefore to update SiteKiosk to at least version 8.7. This update is free for all users that already run a previous version 8 of SiteKiosk and for all customers with SiteKiosk 7.8 that have bought their license since August 2011.

Customers who cannot or do not want to update to SiteKiosk 8.7 or higher can use the following solutions to fix the problem:

  1. 1) Download the small fix we provide here on our website and then just run the executable.

    You can also run the fix silently via the command line if you use the /s parameter (IE10patch.exe /s).

    NOTE: User who are running SiteKiosk 7.1 under Windows 7 64Bit systems need to update to at least SiteKiosk 7.5 before applying the fix.

  2. 2) The second solution is available for all users who use to remotely manage their kiosks or use their own SiteRemote server. When you log in to your team on and go to the Jobs tab you will find a new system job template named Windows 7 IE 10 Fix. Apply this job to your Windows 7 terminals, make sure to read the job description first.
    The following only applies to customers who run their own SiteRemote server. Customers with their own SiteRemote server can create the above job template themselves. Under a team on the SiteRemote server go to the Jobs tab and at the bottom of the page click on the New Template button. Use a job name and description as desired and set the client type to SiteKiosk. Select File Upload as action type and click on Add. Upload the win7ie10fix.js from this zip archive and use %SiteKioskPath%\ as destination path. Make sure to select to overwrite existing files. Next select Run Executable as action type and click Add again to create a second job step. Use wscript.exe "%SiteKioskPath%\win7ie10fix.js" as the command line. Select Visible execution with user rights. As an optional step you can select Evaluate the process's exit code, set the value to 0 and use completed successfully. Save the job template and assign it your Windows 7 machines.


People who are already affected and experience a loop during SiteKiosk startup can use the instructions from this FAQ to reset the system:

Compatibility Issue with SiteKiosk and IE10 on Windows 7 Resolved

We just released SiteKiosk 8.7 which fixes a bug that occurs when SiteKiosk is used on a Windows 7 system with Internet Explorer 10. Under the restricted SiteKiosk user the SiteKiosk browser may not be able to start properly because of problems with the new Webcache folder introduced by IE10.

You can download SiteKiosk 8.7 from here.

A list of all new features and bug fixes can be found here.


It is recommended to upgrade to SiteKiosk 8.7. Users who for whatever reason do not want to upgrade should not install Internet Explorer 10 on Windows 7 systems. Microsoft provides a toolkit to prevent systems from automatically receiving the IE10:


People who are already affected and experience a loop during SiteKiosk startup can use the instructions from this FAQ to reset the system:


Please note that Windows 8 with IE10 was not affected.

Compatibility Issue with SiteKiosk and IE10 on Windows 7

We are currently investigating a SiteKiosk startup issue that occurs when SiteKiosk is used on a Windows 7 system with Internet Explorer 10. Under the restricted SiteKiosk user the SiteKiosk browser may not be able to start properly because of problems with the new Webcache folder introduced by IE10.


It is recommended to not upgrade to Internet Explorer 10 on Windows 7 systems. Microsoft provides a toolkit to prevent systems from automatically receiving the IE10:


We are working on this issue and try to resolve it as soon as possible.

People who are already affected and experience a loop during SiteKiosk startup can use the instructions from this FAQ to reset the system:


Please note that Windows 8 with IE10 is not affected.

Changing the User Agent of the SiteKiosk Browser

The user agent string is used to identify the browser with which a client contacts a server. This information can be utilized to decide what kind of content is delivered to the client in return, to make sure the browser receives data that is optimized for exactly that type of browser. 

SiteKiosk uses the public WebBrowser control of the Microsoft Internet Explorer installed on the system. This means that SiteKiosk identifies itself with the same user agent string as the IE. When a standard configuration is used SiteKiosk will add SiteKiosk Version Number at the end of the user agent string, e.g. SiteKiosk 8.6.1251. A full user agent string under SiteKiosk will look like this:

Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SiteKiosk 8.6 Build 1251)

Adding SiteKiosk to the user agent can be used for example to let a server deliver SiteKiosk Object Model code to a client. You can deactivate this behaviour in the SiteKiosk configuration and you can also add your own identifiers. You can find more information on this topic here:

Ideally the above means that your client browser receives the content it is supposed to display in the most suitable form. If a kiosk project is created from scratch, the content can be optimized to fit the kiosk. Even in projects where content has already been created, it will usually run without modifications on the kiosk, because the content has already been designed for usage in a standard browser like IE.

In some cases though, it might come in handy if your browser could pose as something completely different, for example in a kiosk project where touchscreens should be used. The web pages that should be displayed are already existing in a version for normal browsers and in a version for mobile phones. The mobile phone version would fit perfectly but the server dynamically delivers its content based on the user agent. This means on a normal Windows system you would get the version for standard desktop browsers and not the version for mobile phones. The solution is to completely change the user agent string to one of a mobile phone.

Microsoft already provides this option by means of editing the Windows registry using the registry editor (regedit.exe). Note that changing the registry is always done at your own risk. Making the browser pose as another may also cause script errors or corrupted page layouts. You should carefully experiment with the values described next before applying it to live systems.

The registry key we will have a look at is for the Internet Explorer, but as SiteKiosk is based on the Internet Explorer it also uses it. That means changing the key will change the behaviour for IE and SiteKiosk. A detailed article on the topic of the user agent string on Windows systems can be found here: The registry key can be found at two different locations in the Windows registry.

One location is under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent

Note: on a 64-Bit system the location is slightly different

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent

Editing that key changes the behaviour for all users on the system.

The other location is under

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent

Editing that key only changes the behaviour for the current user. This means to edit this key you must be logged in with the user you want to change the behaviour for.

On most systems the above key only contains the default value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Default). For the desired effect we need to add two additional string values (unless they are already there). One is called Platform and the other Version. As an example we will add the following data to Platform (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Platform)

Linux; U; Android 4.0.4;

and the following data to Version (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Version)

AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30

These are values an Android smartphone uses. When the changes are done, we can see the effect by opening the SiteKiosk browser (or IE, as both are using that registry key) and going to With the changes we will be directly transferred to the mobile version of the page. The SiteKiosk user string now looks like this:

Mozilla/5.0 (compatible; AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30; Linux; U; Android 4.0.4;; Trident/5.0; SiteKiosk 8.6 Build 1251)

If the above workaround is suitable for your project and you want to spare yourself the hassle of manually editing the registry on all your kiosk systems, you can use the SiteKiosk ProgramPatcher tool to automatically apply the registry changes.