Merged PR 13728: revised kiosk troubleshooting + how to connect to kiosk in VM

This commit is contained in:
Jeanie Decker
2019-01-10 20:52:23 +00:00
parent 47eabcd921
commit 49e946a503
8 changed files with 44 additions and 10 deletions

View File

@ -31,7 +31,7 @@
#### [Use AppLocker to create a Windows 10 kiosk](lock-down-windows-10-applocker.md)
#### [Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md)
#### [Use MDM Bridge WMI Provider to create a Windows 10 kiosk](kiosk-mdm-bridge.md)
#### [Troubleshoot multi-app kiosk](multi-app-kiosk-troubleshoot.md)
#### [Troubleshoot kiosk mode issues](kiosk-troubleshoot.md)
## [Configure Windows Spotlight on the lock screen](windows-spotlight.md)
## [Manage Windows 10 and Microsoft Store tips, "fun facts", and suggestions](manage-tips-and-suggestions.md)
## [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)

View File

@ -17,7 +17,13 @@ ms.date: 11/07/2018
This topic lists new and updated topics in the [Configure Windows 10](index.md) documentation for Windows 10 and Windows 10 Mobile.
## Novermber 2018
## January 2019
New or changed topic | Description
--- | ---
[Prepare a device for kiosk configuration](kiosk-prepare.md) | Added how to connect to a single-app kiosk in a virtual machine (VM) for testing.
## November 2018
New or changed topic | Description
--- | ---

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

View File

@ -31,7 +31,7 @@ Topic | Description
[Use AppLocker to create a Windows 10 kiosk](lock-down-windows-10-applocker.md) | Learn how to use AppLocker to configure a kiosk device running Windows 10 Enterprise or Windows 10 Education, version 1703 and earlier, so that users can only run a few specific apps.
[Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md) | Using Shell Launcher, you can configure a kiosk device that runs a Windows desktop application as the user interface.
[Use MDM Bridge WMI Provider to create a Windows 10 kiosk](kiosk-mdm-bridge.md) | Environments that use Windows Management Instrumentation (WMI) can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
[Troubleshoot multi-app kiosk](multi-app-kiosk-troubleshoot.md) | Tips for troubleshooting multi-app kiosk configuration.
[Troubleshoot kiosk mode issues](kiosk-troubleshoot.md) | Tips for troubleshooting multi-app kiosk configuration.

View File

@ -237,5 +237,17 @@ The following table describes some features that have interoperability issues we
<span id="test-vm" />
## Testing your kiosk in a virtual machine (VM)
Customers sometimes use virtual machines (VMs) to test configurations before deploying those configurations to physical devices. If you use a VM to test your single-app kiosk configuration, you need to know how to connect to the VM properly.
A single-app kiosk kiosk configuration runs an app above the lockscreen. It doesn't work when it's accessed remotely, which includes *enhanced* sessions in Hyper-V.
When you connect to a VM configured as a single-app kiosk, you need a *basic* session rather than an enhanced session. In the following image, notice that **Enhanced session** is not selected in the **View** menu; that means it's a basic session.
![VM windows, View menu, Extended session is not selected](images/vm-kiosk.png)
To connect to a VM in a basic session, do not select **Connect** in the connection dialog, as shown in the following image, but instead, select the **X** button in the upper-right corner to cancel the dialog.
![Do not select connect button, use close X in corner](images/vm-kiosk-connect.png)

View File

@ -1,5 +1,5 @@
---
title: Troubleshoot multi-app kiosk (Windows 10)
title: Troubleshoot kiosk mode issues (Windows 10)
description: Tips for troubleshooting multi-app kiosk configuration.
ms.assetid: 14DDDC96-88C7-4181-8415-B371F25726C8
keywords: ["lockdown", "app restrictions"]
@ -13,19 +13,30 @@ ms.author: jdecker
ms.topic: article
---
# Troubleshoot multi-app kiosk
# Troubleshoot kiosk mode issues
**Applies to**
- Windows 10
## Sign-in issues
## Single-app kiosk issues
>[!TIP]
>We recommend that you [enable logging for kiosk issues](kiosk-prepare.md#enable-logging). For some failures, events are only captured once. If you enable logging after an issue occurs with your kiosk, the logs may not capture those one-time events. In that case, prepare a new kiosk environment (such as a [virtual machine (VM)](kiosk-prepare.md#test-vm)), set up your kiosk account and configuration, and try to reproduce the problem.
### Sign-in issues
1. Verify that User Account Control (UAC) is turned on.
2. Check the Event Viewer logs for sign-in issues under **Applications and Services Logs\Microsoft\Windows\Authentication User Interface\Operational**.
## Unexpected results
### Automatic logon issues
Check the Event Viewer logs for auto logon issues under **Applications and Services Logs\Microsoft\Windows\Authentication User Interface\Operational**.
## Multi-app kiosk issues
### Unexpected results
For example:
- Start is not launched in full-screen
@ -43,17 +54,17 @@ For example:
![Event Viewer, right-click Operational, select enable log](images/enable-assigned-access-log.png)
## Automatic logon issues
### Automatic logon issues
Check the Event Viewer logs for auto logon issues under **Applications and Services Logs\Microsoft\Windows\Authentication User Interface\Operational**.
## Apps configured in AllowedList are blocked
### Apps configured in AllowedList are blocked
1. Ensure the account is mapped to the correct profile and that the apps are specific for that profile.
2. Check the EventViewer logs for Applocker and AppxDeployment (under **Application and Services Logs\Microsoft\Windows**).
## Start layout not as expected
### Start layout not as expected
- Make sure the Start layout is authored correctly. Ensure that the attributes **Size**, **Row**, and **Column** are specified for each application and are valid.
- Check if the apps included in the Start layout are installed for the assigned access user.