deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-21 13:23:36 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update kiosk configuration and shell launcher XML file

Browse Source
This commit is contained in:
Paolo Matarazzo
2024-02-26 09:09:26 -05:00
parent cd8682c256
commit 2ed2b3471a
2 changed files with 67 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
windows/configuration/assigned-access/index.md
View File

@ -1,11 +1,11 @@
--- ---
title: Configure kiosks and digital signs on Windows 10/11 desktop editions title: Configure kiosks and restricted user experiences
description: In this article, learn about the methods for configuring kiosks and digital signs on Windows 10 or Windows 11 desktop editions. description: Learn about the options available in Windows to configure kiosks and restricted user experiences.
ms.topic: article ms.topic: overview
ms.date: 12/31/2017 ms.date: 02/26/2024
--- ---
# Configure kiosks and digital signs on Windows desktop editions # Configure kiosks and restricted user experiences
Organization may want to set up special purpose devices, such as a device in the lobby that customers can use to view product catalogs, or a device displaying visual content as a digital sign. Windows client offers two different locked-down experiences for public or specialized use: Organization may want to set up special purpose devices, such as a device in the lobby that customers can use to view product catalogs, or a device displaying visual content as a digital sign. Windows client offers two different locked-down experiences for public or specialized use:

76
windows/configuration/assigned-access/shell-launcher-configuration-file.md
View File

@ -11,12 +11,71 @@ This article provides practical examples of Shell Launcher XML configuration fil
Let's start by looking at the basic structure of the XML file. Let's start by looking at the basic structure of the XML file.
- A configuration xml can define multiple `profiles`. Each profile has a *profile Id* and defines a set of applications that are allowed to run - A configuration xml can define one or multiple `Profiles`
- A configuration xml can have multiple `configs`. Each config associates a non-admin user account to a default profile Id - Each profile has a unique `Profile Id` and defines a `Shell` elemnt, which is the application that executes when the user signs in
- A profile has no effect if it's not associated to a user account - A profile can define a default action to be taken when the application exits and may define actions to be taken when the application exits with a specific return code
- A profile must be associated to a user account to have an effect
- You can define a `Default profile` that is used when no other profile is associated to a user account
- A configuration xml can define one or multiple `configs`
- Each config associates a user account to a `profile Id`
- A profile has no effect if it's not associated to a user account
You can start your file by pasting the following XML code into a text editor, and saving the file with an xml extension. For example, `kiosk.xml`. You can start your file by pasting the following XML code into a text editor, and saving the file with an xml extension. For example, `kiosk.xml`.
```xml
<?xml version="1.0" encoding="utf-8" ?>
<ShellLauncherConfiguration
xmlns="http://schemas.microsoft.com/ShellLauncher/2018/Configuration"
xmlns:V2="http://schemas.microsoft.com/ShellLauncher/2019/Configuration">
<Profiles>
...
</Profiles>
<Configs>
...
</Configs>
</ShellLauncherConfiguration>
```
## Profiles node
If you want to define a default profile, you can use the `DefaultProfile` element:
```xml
<Profiles>
<DefaultProfile>
...
</DefaultProfile>
</Profiles>
```
Each profile is identified by a unique identifier `Profile Id`, for example:
```xml
<Profiles>
<Profile Id="{EDB3036B-780D-487D-A375-69369D8A8F78}">
...
</Profile>
</Profiles>
```
### Shell node
The `Shell` node defines the application that executes when the user signs in:
- The `Shell` attribute is the path to the application
- The `V2:AppType` attribute defines the type of application
- The `V2:AllAppsFullScreen` attribute is a boolean value that defines if all applications are executed in full screen
```xml
<Shell Shell="" V2:AppType="" V2:AllAppsFullScreen="">
<ReturnCodeActions>
<ReturnCodeAction ReturnCode="" Action=""/>
</ReturnCodeActions>
<DefaultAction Action=""/>
</Shell>
```
```xml ```xml
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<ShellLauncherConfiguration <ShellLauncherConfiguration
@ -44,17 +103,6 @@ You can start your file by pasting the following XML code into a text editor, an
</ShellLauncherConfiguration> </ShellLauncherConfiguration>
``` ```
## Profiles node
An Shell Launcher configuration file can contain one or more profiles. Each profile is identified by a unique identified `Profile Id`, for example:
```xml
<Profiles>
<Profile Id="{EDB3036B-780D-487D-A375-69369D8A8F78}">
...
</Profile>
</Profiles>
```
### AppType ### AppType