From 7fe684527a3da1711af876a31d68e4f819f5cc1f Mon Sep 17 00:00:00 2001 From: Ed Gallagher Date: Sun, 30 Sep 2018 21:19:43 -0500 Subject: [PATCH] Update kiosk-shelllauncher.md Added information into the note about limitations of using this method. Suggested by user jrshoare --- windows/configuration/kiosk-shelllauncher.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/windows/configuration/kiosk-shelllauncher.md b/windows/configuration/kiosk-shelllauncher.md index 30bb50f7de..fef3c07020 100644 --- a/windows/configuration/kiosk-shelllauncher.md +++ b/windows/configuration/kiosk-shelllauncher.md @@ -25,6 +25,12 @@ ms.date: 07/30/2018 Using Shell Launcher, you can configure a kiosk device that runs a Windows desktop application as the user interface. The application that you specify replaces the default shell (explorer.exe) that usually runs when a user logs on. >[!NOTE] +>Using the Shell Launcher controls what application the user has as the shell experience after login. It does not prevent the user from accessing other desktop applications and system components. +>Methods of controling access to other desktop applications and system components can be used in addition to using the Shell Launcher. These methods include, but are not limited to: +>[Group policy](https://www.microsoft.com/download/details.aspx?id=25250) - example: Prevent access to registry editing tools +>[AppLocker](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-overview) - Application control policies +>[Mobile Device Management](https://docs.microsoft.com/windows/client-management/mdm) - Enterprise management of device security policies) +> >You can also configure a kiosk device that runs a Windows desktop application by using the [Provision kiosk devices wizard](#wizard). >[!WARNING]