mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
updates
This commit is contained in:
Paolo Matarazzo
parent
406b3d0d58
commit
228d1e7f4c
@ -141,4 +141,3 @@ $ShellLauncherClass.SetEnabled($FALSE)
|
||||
$IsShellLauncherEnabled = $ShellLauncherClass.IsEnabled()
|
||||
"`nEnabled is set to " + $IsShellLauncherEnabled.Enabled
|
||||
```
|
||||
|
||||
|
||||
@ -22,6 +22,79 @@ You can configure the following options for Shell Launcher:
|
||||
|
||||
Any changes don't take effect until a user signs in.
|
||||
|
||||
## Enable Shell Launcher
|
||||
|
||||
Shell Launcher is an optional component in Windows that is not enabled by default. To configure it, you must first enable it. You can enable and configure Shell Launcher in a customized Windows image, or you can enable it before applying a provisioning package to configure it.
|
||||
|
||||
> [!NOTE]
|
||||
> When you configure Shell Launcher with the Assigned Access Configuration Service Provider (CSP), Shell Launcher is automatically enabled, if the device supports it. There's no need to enable Shell Launcher separately when you configure it using Assigned Access CSP.
|
||||
|
||||
There are multiple ways to enable Shell Launcher, select the method that best fits your needs to learn more.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/control-panel.svg"::: **Control Panel**](#tab/control-panel)
|
||||
|
||||
To enable Shell Launcher using Control Panel, follow these steps:
|
||||
|
||||
1. Open **Control Panel** > **Programs** > **Turn Windows features on or off** or use the command `optionalfeatures.exe`
|
||||
1. Expand **Device Lockdown** and select **Shell Launcher**
|
||||
1. Select **OK** to enable Shell Launcher
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/powershell.svg"::: **PowerShell**](#tab/powershell)
|
||||
|
||||
To enable Shell Launcher using PowerShell, follow these steps:
|
||||
|
||||
1. Open a PowerShell window with administrator privileges
|
||||
1. Run the following command:
|
||||
|
||||
```powershell
|
||||
Enable-WindowsOptionalFeature -FeatureName Client-DeviceLockdown,Client-EmbeddedShellLauncher -Online
|
||||
```
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
|
||||
|
||||
[!INCLUDE [provisioning-package-1](../../../includes/configure/provisioning-package-1.md)]
|
||||
|
||||
- **Path:** `SMISettings/ShellLauncher/Enable`
|
||||
- **Value:** ENABLE
|
||||
|
||||
[!INCLUDE [provisioning-package-2](../../../includes/configure/provisioning-package-2.md)]
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You can configure Shell Launcher by creating a provisioning package and then applying the provisioning package during image deployment time or at runtime. If you're creating an installation media with settings for Shell Launcher included in the image, or you're applying a provisioning package during setup, you must enable Shell Launcher on the installation media with DISM for a provisioning package to successfully apply.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/settings.svg"::: **DISM**](#tab/dism)
|
||||
|
||||
The following example uses a Windows image called `install.wim`, but you can use the same procedure to apply a provisioning package.
|
||||
|
||||
1. Open a command prompt with administrator privileges.
|
||||
1. Copy install.wim to a temporary folder on hard drive (in the following steps, we assume it's called `C:\wim`)
|
||||
1. Modify the following script to match your environment:
|
||||
|
||||
```cmd
|
||||
@echo off
|
||||
REM Create a new directory
|
||||
md c:\wim
|
||||
|
||||
REM Mount the image
|
||||
dism /mount-wim /wimfile:c:\bootmedia\sources\install.wim /index:1 /MountDir:c:\wim
|
||||
|
||||
REM Enable the feature
|
||||
dism /image:c:\wim /enable-feature /all /featureName:Client-EmbeddedShellLauncher
|
||||
|
||||
REM Commit the change
|
||||
dism /unmount-wim /MountDir:c:\wim /Commit
|
||||
```
|
||||
|
||||
For more information on DISM, see [What Is Deployment Image Servicing and Management](/windows-hardware/manufacture/desktop/what-is-dism).
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/dev.svg"::: **WMI**](#tab/wmi)
|
||||
|
||||
You can enable or disable Shell Launcher by calling the `SetEnabled` function in the Windows Management Instrumentation (WMI) class `WESL_UserSetting`.
|
||||
|
||||
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.
|
||||
|
||||
@ -1,79 +0,0 @@
|
||||
---
|
||||
title: Enable Shell Launcher
|
||||
description: Learn how to enable the Shell Launcher feature.
|
||||
ms.date: 02/27/2025
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
# Enable Shell Launcher
|
||||
|
||||
Shell Launcher is an optional component in Windows that is not enabled by default. To configure it, you must first enable it. You can enable and configure Shell Launcher in a customized Windows image, or you can enable it before applying a provisioning package to configure it.
|
||||
|
||||
> [!NOTE]
|
||||
> When you configure Shell Launcher with the Assigned Access Configuration Service Provider (CSP), Shell Launcher is automatically enabled, if the device supports it. There's no need to enable Shell Launcher separately when you configure it using Assigned Access CSP.
|
||||
|
||||
There are multiple ways to enable Shell Launcher, select the method that best fits your needs to learn more.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/control-panel.svg"::: **Control Panel**](#tab/control-panel)
|
||||
|
||||
To enable Shell Launcher using Control Panel, follow these steps:
|
||||
|
||||
1. Open **Control Panel** > **Programs** > **Turn Windows features on or off** or use the command `optionalfeatures.exe`
|
||||
1. Expand **Device Lockdown** and select **Shell Launcher**
|
||||
1. Select **OK** to enable Shell Launcher
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/powershell.svg"::: **PowerShell**](#tab/powershell)
|
||||
|
||||
To enable Shell Launcher using PowerShell, follow these steps:
|
||||
|
||||
1. Open a PowerShell window with administrator privileges
|
||||
1. Run the following command:
|
||||
|
||||
```powershell
|
||||
Enable-WindowsOptionalFeature -FeatureName Client-DeviceLockdown,Client-EmbeddedShellLauncher -Online
|
||||
```
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
|
||||
|
||||
[!INCLUDE [provisioning-package-1](../../../includes/configure/provisioning-package-1.md)]
|
||||
|
||||
- **Path:** `SMISettings/ShellLauncher/Enable`
|
||||
- **Value:** ENABLE
|
||||
|
||||
[!INCLUDE [provisioning-package-2](../../../includes/configure/provisioning-package-2.md)]
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You can configure Shell Launcher by creating a provisioning package and then applying the provisioning package during image deployment time or at runtime. If you're creating an installation media with settings for Shell Launcher included in the image, or you're applying a provisioning package during setup, you must enable Shell Launcher on the installation media with DISM for a provisioning package to successfully apply.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/settings.svg"::: **DISM**](#tab/dism)
|
||||
|
||||
The following example uses a Windows image called `install.wim`, but you can use the same procedure to apply a provisioning package.
|
||||
|
||||
1. Open a command prompt with administrator privileges.
|
||||
1. Copy install.wim to a temporary folder on hard drive (in the following steps, we assume it's called `C:\wim`)
|
||||
1. Modify the following script to match your environment:
|
||||
|
||||
```cmd
|
||||
@echo off
|
||||
REM Create a new directory
|
||||
md c:\wim
|
||||
|
||||
REM Mount the image
|
||||
dism /mount-wim /wimfile:c:\bootmedia\sources\install.wim /index:1 /MountDir:c:\wim
|
||||
|
||||
REM Enable the feature
|
||||
dism /image:c:\wim /enable-feature /all /featureName:Client-EmbeddedShellLauncher
|
||||
|
||||
REM Commit the change
|
||||
dism /unmount-wim /MountDir:c:\wim /Commit
|
||||
```
|
||||
|
||||
For more information on DISM, see [What Is Deployment Image Servicing and Management](/windows-hardware/manufacture/desktop/what-is-dism).
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/dev.svg"::: **WMI**](#tab/wmi)
|
||||
|
||||
You can enable or disable Shell Launcher by calling the `SetEnabled` function in the Windows Management Instrumentation (WMI) class `WESL_UserSetting`.
|
||||
|
||||
For more information, see [WESL_UserSetting](wesl-usersetting.md).
|
||||
|
||||
---
|
||||
@ -35,8 +35,6 @@ Methods of controlling access to other desktop applications and system component
|
||||
|
||||
For sample XML configurations for the different app combinations, see [Samples for Shell Launcher v2](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/ShellLauncher/ShellLauncherV2).
|
||||
|
||||
|
||||
|
||||
## FROM COPILOT
|
||||
|
||||
Shell Launcher is a feature in Windows that allows administrators to replace the default Windows Explorer shell with a custom shell for specialized devices or environments. Over time, Shell Launcher has evolved to meet the needs of modern deployments, leading to the introduction of Shell Launcher v2.
|
||||
|
||||
@ -3,8 +3,6 @@ items:
|
||||
href: index.md
|
||||
- name: 🟡 Old content
|
||||
href: index_old.md
|
||||
- name: 🟡 Enable Shell Launcher
|
||||
href: enable.md
|
||||
- name: Configure Shell Launcher
|
||||
href: configure.md
|
||||
- name: "Quickstart: Configure a kiosk"
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user