mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
Merge remote-tracking branch 'refs/remotes/origin/rs4' into jdrs4
# Conflicts: # windows/configuration/setup-kiosk-digital-signage.md
This commit is contained in:
@ -7,7 +7,7 @@ ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jdecker
|
||||
ms.date: 09/06/2017
|
||||
ms.date: 03/30/2018
|
||||
---
|
||||
|
||||
# SMISettings (Windows Configuration Designer reference)
|
||||
@ -94,6 +94,9 @@ When you **enable** KeyboardFilter, a number of other settings become available
|
||||
|
||||
Use ShellLauncher to specify the application or executable to use as the default custom shell. One use of ShellLauncher is to [create a kiosk (fixed-purpose) device running a Classic Windows application](https://docs.microsoft.com/windows/configuration/set-up-a-kiosk-for-windows-10-for-desktop-editions#shell-launcher-for-classic-windows-applications).
|
||||
|
||||
>[!WARNING]
|
||||
>Windows 10 doesn’t support setting a custom shell prior to OOBE. If you do, you won’t be able to deploy the resulting image.
|
||||
|
||||
You can also configure ShellLauncher to launch different shell applications for different users or user groups.
|
||||
|
||||
>[!IMPORTANT]
|
||||
|
Reference in New Issue
Block a user