mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
timestamps
This commit is contained in:
Paolo Matarazzo
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Create a Shell Launcher configuration file
|
||||
description: Learn how to create an XML file to configure a device with Shell Launcher.
|
||||
ms.date: 02/27/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure Shell Launcher with the WMI provider
|
||||
description: Learn how to configure a Windows kiosk using the WMI provider for Shell Launcher.
|
||||
ms.date: 02/27/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure Shell Launcher
|
||||
description: Learn how to configure Shell Launcher.
|
||||
ms.date: 02/27/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
@ -84,16 +84,17 @@ For more information, see [WESL_UserSetting](wesl-usersetting.md).
|
||||
|
||||
## Launch different shells for different user accounts
|
||||
|
||||
By default, Shell Launcher runs the default shell, which is specified when you create the OS image at design time. The default shell is set to Cmd.exe, but you can specify any executable file to be the default shell.
|
||||
By default, Shell Launcher runs the default shell, which is specified when you create the OS image at design time. The default shell is set to the Windows Command Processor (`Cmd.exe`), but you can specify any executable file to be the default shell.
|
||||
|
||||
You can configure Shell Launcher to launch a different shell for specific users or groups if you don't want to run the default shell. For example, you might configure a device to run a custom application shell for guest accounts, but run the standard Windows Explorer shell for administrator accounts in order to service the device.
|
||||
|
||||
If you use the WMI providers to configure Shell Launcher for a user or group at run time, you must use the security identifier (SID) for that user or group; you can't use the user name or group name.
|
||||
|
||||
For more information about common security identifiers, see [Well-known SIDs](/windows/win32/secauthz/well-known-sids).
|
||||
You can also configure Shell Launcher to launch a different shell for specific users or groups if you don't want to run the default shell. For example, you might configure a device to launch a custom application shell for guest accounts, but run the standard Windows Explorer shell for administrator accounts for servicing the device.
|
||||
|
||||
When the current signed in account belongs to two or more groups that have different configurations defined for each group, Shell Launcher uses the first configuration it finds. The search order isn't defined, so we recommend that you avoid assigning a user to multiple groups with different Shell Launcher configurations.
|
||||
|
||||
> [!NOTE]
|
||||
> If you use the WMI provider to configure Shell Launcher for a user or group at run time, you must use the security identifier (SID) for that security principal. You can't use the user name or group name.
|
||||
>
|
||||
> For more information about common security identifiers, see [Well-known SIDs](/windows/win32/secauthz/well-known-sids).
|
||||
|
||||
## Shell Launcher startup and exit behavior
|
||||
|
||||
Shell Launcher processes the `Run` and `RunOnce` registry keys before starting the custom shell, so your custom shell doesn't need to handle the automatic startup of other applications and services.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 10/31/2024
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 10/31/2024
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 10/31/2024
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Shell Launcher Overview
|
||||
description: Learn how to configure devices with Shell Launcher.
|
||||
ms.date: 02/27/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: overview
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: "Quickstart: configure a single-app kiosk with Shell Launcher"
|
||||
description: Learn how to configure a signle-app kiosk experience with Shell Launcher, using the Assigned Access configuration service provider (CSP), Microsoft Intune, PowerShell, or group policy (GPO).
|
||||
ms.topic: quickstart
|
||||
ms.date: 02/27/2025
|
||||
ms.date: 3/7/2025
|
||||
---
|
||||
|
||||
# Quickstart: configure a kiosk with Shell Launcher
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting
|
||||
description: WESL_UserSetting
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.GetCustomShell
|
||||
description: WESL_UserSetting.GetCustomShell
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.GetDefaultShell
|
||||
description: WESL_UserSetting.GetDefaultShell
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.IsEnabled
|
||||
description: WESL_UserSetting.IsEnabled
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.RemoveCustomShell
|
||||
description: WESL_UserSetting.RemoveCustomShell
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetCustomShell
|
||||
description: WESL_UserSetting.SetCustomShell
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetDefaultShell
|
||||
description: WESL_UserSetting.SetDefaultShell
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetEnabled
|
||||
description: WESL_UserSetting.SetEnabled
|
||||
ms.date: 02/25/2025
|
||||
ms.date: 3/7/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Shell Launcher XML Schema Definition (XSD)
|
||||
description: Shell Launcher XSD reference article.
|
||||
ms.topic: reference
|
||||
ms.date: 02/27/2025
|
||||
ms.date: 3/7/2025
|
||||
---
|
||||
|
||||
# Shell Launcher XML Schema Definition (XSD)
|
||||
|
||||
Reference in New Issue
Block a user