From dd4ba615f1b0f08de489c4078e03824f7ef64b25 Mon Sep 17 00:00:00 2001 From: Jeanie Decker Date: Thu, 7 Mar 2019 08:53:19 -0800 Subject: [PATCH] xml samples --- windows/configuration/kiosk-shelllauncher.md | 25 +++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/windows/configuration/kiosk-shelllauncher.md b/windows/configuration/kiosk-shelllauncher.md index 86e3db1569..b74f4a828a 100644 --- a/windows/configuration/kiosk-shelllauncher.md +++ b/windows/configuration/kiosk-shelllauncher.md @@ -84,6 +84,24 @@ You can use XML and a [custom OMA-URI setting](#custom-oma-uri-setting) to confi ### XML for Shell Launcher configuration +The following XML sample works for Shell Launcher v1: + +``` + + + + + + + + + + + + + +``` + For Shell Launcher v2, you will use a different schema reference and a different app type for `Shell`, as shown in the following example. ``` @@ -101,10 +119,15 @@ xmlns:v2="http://schemas.microsoft.com/ShellLauncher/2019/Configuration"> ``` +[Get XML examples for different Shell Launcher v2 configurations.](https://github.com/Microsoft/Windows-iotcore-samples/tree/develop/Samples/ShellLauncherV2) + ### Custom OMA-URI setting -[custom OMA-URI setting](https://docs.microsoft.com/intune/custom-settings-windows-10) +In your MDM service, you can create a [custom OMA-URI setting](https://docs.microsoft.com/intune/custom-settings-windows-10) to configure Shell Launcher v1 or v2. (The XML that you use for your setting will determine whether you apply Shell Launcher v1 or v2.) +The OMA-URI path is `./Device/Vendor/MSFT/AssignedAccess/ShellLauncher`. + +For the value, you can select data type `String` and paste the desired configuration file content into the value box. If you wish to upload the xml instead of pasting the content, choose data type `String (XML file)` instead. ## Configure a custom shell using PowerShell