no RDP for kiosk; UAC must be on

This commit is contained in:
Jeanie Decker
2019-01-08 12:57:02 -08:00
parent 8c282a4ba0
commit 26af952087
4 changed files with 19 additions and 3 deletions

View File

@ -7,7 +7,7 @@ ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
author: jdeckerms
ms.date: 07/30/2018
ms.date: 01/08/2019
---
# Configure kiosks and digital signs on Windows desktop editions
@ -30,6 +30,8 @@ There are several kiosk configuration methods that you can choose from, dependin
![icon that represents Windows](images/windows.png) | **Which edition of Windows 10 will the kiosk run?** All of the configuration methods work for Windows 10 Enterprise and Education; some of the methods work for Windows 10 Pro. Kiosk mode is not available on Windows 10 Home.
![icon that represents a user account](images/user.png) | **Which type of user account will be the kiosk account?** The kiosk account can be a local standard user account, a local administrator account, a domain account, or an Azure Active Directory (Azure AD) account, depending on the method that you use to configure the kiosk. If you want people to sign in and authenticate on the device, you should use a multi-app kiosk configuration. The single-app kiosk configuration doesn't require people to sign in to the device, although they can sign in to the kiosk app if you select an app that has a sign-in method.
>[!IMPORTANT]
>Kiosk mode is not supported over a remote desktop connection. Your kiosk users must sign in on the physical device that is set up as a kiosk.
<span id="uwp" />
## Methods for a single-app kiosk running a UWP app