If we use Zapp-Launcher.exe as a custom shell like it is designed in Windows 10, it comes into foreground every 5 minutes and disturbs the user experience.
This is, because you kill, for whatever reason, every 5 minutes the zapp-launcher.exe file.
Here are some details, we use:
A single-use device is easy to set up in Windows 10 for desktop editions (Pro, Enterprise, and Education). There are a few different methods you can choose from to set up single-function kiosk devices, such as restaurant menus or displays at trade shows:
1. Use the Windows Configuration Designer method to configure a kiosk device running either a single Universal Windows app (Windows 10 Enterprise, Education, and Pro) or a single Classic Windows application (Windows 10 Enterprise or Education only).
2. In Windows 10, version 1709, you can also use the Provision kiosk devices wizard in Windows Configuration Designer to configure a kiosk that runs multiple applications.
3. For a kiosk device to run a single Universal Windows Platform (UWP) app, use the Assigned access method.
4. For a kiosk device (Windows 10 Enterprise or Education) to run a single Classic Windows application, use the Shell Launcher method to set a custom user interface as the shell.
Source: https://docs.microsoft.com/en-us/windows-hardware/customize/enterprise/create-a-kiosk-image#shell-launcher
by: Peter R. | over a year ago | Application Mgmt
Comments
This issue should not occur if you follow this.....
(Yes, Odd Place to document configuring ZAPP as Shell)
https://www.novell.com/documentation/zenworks-2017-update-1/zen_cm_software_distribution/data/bundles_ways_to_access.html#bjpksh1
Thanks Craig. Because this is an idea portal, we would love Micro Focus development to implement this new feature as well. The old method is well since ~20 years and this seems to be the next evolution step for this.