Company Christmas Holidays
North American Headquarters in Miami, USA: Dec 25, 2015, Jan 1st 2016
European Headquarters in Muenster, Germany: Dec 21, 2015 until Jan 03rd 2016
Limited support is available during this period.
We at PROVISIO wish you Merry Christmas and a Happy New Year!

 

Support Request: SiteKiosk not implemented correctly

Description

It does not seem that SiteKiosk Config Editor is listening to us. We use SiteKiosk to allow only one application, and one application only. We have set this application on autostart and works correctly. The problem is the Watchdog is active on the other monitor. When you click on the watchdog the application is minimized and the unwanted SiteKiosk desktop is shown. This consists of a Power Off and SiteKiosk Web Browser applications that we do not want. The ideal setting is no watchdog on the other monitor and no SiteKiosk desktop.

We have told the SiteKiosk Config Editor NOT to display the desktop/two icons but it simply does not accept the configuration items we are passing it.

Answer: (5)

Re: SiteKiosk not implemented correctly 3/21/2019 1:24 PM
Hello,

The watchdog is aways displayed in the background when SiteKiosk is running to protect the Widows desktop and on the second monitor it is displayed permamently when the option “Activate second monitor” is disabled.

If using an IE based skin you may enable the checkbox “Keep SiteKiosk main window in the background (not TopMost)” at “Start Page & Browser-->Advanced” to make sure the SiteKiosk Browser window never gets in front of the external applicaition window.

If the application minimizes you can maximize / focus the application again by clicking on the correspondign program element at the taskbar (not enable the option “Hide taskbar in fullscreen mode” at “Start Page & Browser-->Fullscreen” and not disable the option “Display Taskbar” at “Start Page & Browser-->Advanced” to make sure the taskbar is displayed)

Otherwise you may check this developer blog article that diescribes how to keep an external application running and maximized:
http://devblog.provisio.com/post/2017/12/18/How-to-Build-an-Extended-Script-Watchdog-for-External-Applications.aspx


Regards,
Michael Olbrich
Re: SiteKiosk not implemented correctly 3/22/2019 9:22 AM
Hi Michael,

When I enable “Activate second monitor” it is not possible to have simply a plain background, with no MS Windows GUI - I have only managed to configure the SiteKiosk to display a black image which is constantly set to the upper-most window, which hides all of the elements of our main application. This is not suitable.

We are also required that there are no taskbars/switching as this is handled within our application. Is it possible to achieve the above?

Kind regards,

Dave L
Re: SiteKiosk not implemented correctly 3/22/2019 9:44 AM
Hello,

You should not enable the option “Activate second monitor” if you want to display another application (or anything else) on the second monitor
Otherwise the external application is overlapped by “SiteCaster”, “SiteKiosk Player” or a Windows Screensaver (e.g. Blank).

Furthermore you should disable the option “Restrict mouse pointer to first monitor browser area”.



For allowing an external application on second monitor you need to adjust the Windows & Dialogs Management at “-->Access/Security-->Block system critical windows & dialog boxes -->Settings” and add a new entry where you allow the application window to be moved to second monitor (Disable the option “Restrict the window to the main screen“).
http://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?handling_of_windows.htm
--> 1.3 Explicitly allow the display of this window

Example:
Use the “Add” button to create a new entry.
At the top enable the option “Explicitly allow the display of this window” but disable the sub option “Restrict the window to the main screen ”.
At “Window title” add the title of the application window
For Notepad it would e.g. be *Notepad



You can automatically start an external application after the start of the SiteKiosk browser by adding it to the SiteKiosk configuration (-->Applications) and enabling the checkbox at “Run program automatically“. But note that this option will also close and restart the program when the screensaver comes on and turns off, while closing and restarting it when a session ends and is resumed before and after a logout, respectively:
https://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?applications.htm

Otherwise you may check this developer blog article that describes how to keep an external application running and maximized:
http://devblog.provisio.com/post/2017/12/18/How-to-Build-an-Extended-Script-Watchdog-for-External-Applications.aspx

Regards,
Michael Olbrich
Re: SiteKiosk not implemented correctly 3/22/2019 1:26 PM
Hello,

I have done that and the behaviour observed is the Watchdog on the second monitor - the mouse cursor is seen with "loading" swirl whilst hovering over the SiteKiosk wallpaper. The "loading" cursor is not seen whilst hovering over the application.

Also, our application calls a number of child widgets. The dialog boxes have lost the formatting. Is there any way to restore the original formatting?

Thanks,

Dave L
Re: SiteKiosk not implemented correctly 3/22/2019 2:06 PM
Hello,

SiteKiosk cannot change the formatting of the window from an external application.
Maybe this is a user dependent issue and you first check in “Run once” mode?
If that works you can verify if the application is running correctly in the SiteKiosk user account without SiteKiosk started.
Here is the information on how to get access: https://www.provisio.com/en-US/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=5826


Generally SiteKiosk has no direct influence to external applications but 2 settings that restrict the execution:
1. Windows & Dialogs Management:
SiteKiosk can block certain dialogs with using the Windows & Dialogs Management.
If you want / need to allow a specific Dialog that is blocked by default you can create a new entry with corresponding title at “-->Access/Security-->Block system critical windows & dialog boxes-->Settings” (or even delete the corresponding entry that blocks the window)

When SiteKiosk blocks a certain window you will find a notification in the SiteKiosk log (…\SiteKiosk\Logfiles).
Example:
[SiteKiosk] Notification: According to the windows monitoring rule(Title:'xxxxxx' Class:'xxxx') the window (Title:'xxxxxxxx' Class:'xxxxxxxxx') will be closed

Further information here:
http://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?windows___dialoge.htm
http://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?handling_of_windows.htm
https://www.provisio.com/en-GB/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=5676

2. User access rights of the SiteKiosk user:
In “Auto Start” mode the SiteKiosk Browser will be started within the restricted local SiteKiosk user account.
This also applies to access rights to the folders (read only, read & execute, blocked….) and blocking certain EXE programs.

To change user rights for the SiteKiosk user you can use the System-Security-Manager (e.g. providing full access to the folder where the EXE you want to start is stored to).
Further information here:
https://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?step_2_-_security_manager.htm
https://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?advanced.htm
https://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?access_rights1.htm


You may also check this troubleshooting guidelines for using external applications:
http://devblog.provisio.com/post/2015/05/15/Troubleshooting-Guidelines-for-Using-External-Applications-with-SiteKiosk.aspx


Regards,
Michael Olbrich