Create a Classic App Kiosk using Configuration Designer

Question

I'm trying to set up a simple kiosk configuration to run a single classic app, but I cannot get it right. I'm doing this steps: 1) install Windows 10 Enterprise 20H2 2) rename the PC and join to the domain 3) install the application manually 4) apply the package created with The Configuration Designer in simple mode. The only settings I configured are: a) the local user to create with it's password and the autologin on b) the username (same as point 4a) for the fullscreen app and the path to the exe file enclosed in quotes (there are spaces in the path) After reboot, the client opens a command prompt. I can press ctrl-alt-del and open the task manager (I shouldn't according to the standard policies of the kiosk mode, right? https://learn.microsoft.com/en-us/windows/configuration/kiosk-policies) and launch explorer etc. etc. While trying at some point the PC started to autostart the desktop app instead of the command prompt, but I didn't understand what I touched... still I can open the task manager and all. Also, I wasn't able to avoid creating the local user and set up the single app mode for a domain user (it's required by the application) because the designer complains about a non valid value, not following the model ^[^\\]+$ Need some help, dind't think a simple task like this one would be so difficult to achieve. I didn't even try to distribute the app (or join the domain) with the package... bye, Dario

Answer 1

Since this is a classic application and not a UWP application, try using Shell Launcher v1 to launch the application as the shell to the system rather than using KIOSK mode. It is a more straight forward solution.

Shell Launcher V1: https://learn.microsoft.com/en-us/windows-hardware/customize/enterprise/shell-launcher
Here are some free utilities that work with Shell Launcher V1: https://annabooks.com/SW_SLUtility.html

There is also Shell Launcher V2, which can launch classic apps as well as UWP: https://learn.microsoft.com/en-us/windows/configuration/kiosk-shelllauncher#:~:text=Using%20Shell%20Launcher,%20you%20can%20configure%20a%20device,a%20Windows%20desktop%20application%20as%20the%20replacement%20shell.

Answer 2

Ok, sorted out the domain user part (needs advanced configuration mode on the Designer), still I don't see applied all the policies from the documentation. And even worse, the applied ones are affecting also administrators (a domain account mapped to the local Administrators group and the local Administrator user).

What am I doing wrong?

bye, Dario

Answer 3

I'm doing exaclty that, with Configuration Designer. I'll check the gui tool you seggested, thanks.

bye, Dario

Answer 4

Hi,

Could you please check whether the VM is connected properly?
Testing your kiosk in a virtual machine (VM)

A single-app kiosk configuration runs an app above the lock screen. It doesn't work when it's accessed remotely, which includes enhanced sessions in Hyper-V.

notice that Enhanced session is not selected in the View menu

To connect to a VM in a basic session, do not select Connect in the connection dialog

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.