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

updates

Browse Source
This commit is contained in:
Paolo Matarazzo 2025-02-28 13:49:43 -05:00
parent 5bdb0e4c20
commit 214b137d8e
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/configuration/assigned-access/toc.yml
View File

@ -9,6 +9,8 @@ items:
href: configure-multi-app-kiosk.md href: configure-multi-app-kiosk.md
- name: 🔴 Multi-app kiosk (merged ↖️) - name: 🔴 Multi-app kiosk (merged ↖️)
href: multi-app-kiosk.md href: multi-app-kiosk.md
- name: Recommendations
href: recommendations.md
- name: Create a configuration file - name: Create a configuration file
href: configuration-file.md href: configuration-file.md
- name: Quickstarts - name: Quickstarts
@ -17,8 +19,6 @@ items:
href: quickstart-kiosk.md href: quickstart-kiosk.md
- name: Configure a multi-app kiosk - name: Configure a multi-app kiosk
href: quickstart-restricted-user-experience.md href: quickstart-restricted-user-experience.md
- name: Recommendations
href: recommendations.md
- name: Reference - name: Reference
items: items:
- name: Assigned Access XSD - name: Assigned Access XSD

6
windows/configuration/shell-launcher/enable.md
View File

@ -8,9 +8,9 @@ ms.topic: how-to
# Enable Shell Launcher # Enable Shell Launcher
> [!NOTE] > [!NOTE]
> Configuring Shell Launcher using Assigned Access CSP, automatically enables Shell Launcher on the device, if the device supports it. There's no need to enable Shell Launcher separately if you configure it using Assigned Access CSP. > 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.
Shell Launcher is an optional component and isn't turned on by default in Windows. It must be turned on prior to configuring. You can turn on and configure Shell Launcher in a customized Windows 10 image (.wim) if Microsoft Windows hasn't been installed. If Windows has already been installed, you must turn on Shell Launcher before applying a provisioning package to configure Shell Launcher. Shell Launcher is an optional component and isn't turned on by default in Windows. It must be turned on before configuring it. You can turn on and configure Shell Launcher in a customized Windows image, or you must turn on Shell Launcher before applying a provisioning package to configure Shell Launcher.
## Enable Shell Launcher using Control Panel ## Enable Shell Launcher using Control Panel
@ -21,7 +21,7 @@ Shell Launcher is an optional component and isn't turned on by default in Window
1. Select **Close** to close the **Windows Features** window. 1. Select **Close** to close the **Windows Features** window.
> [!NOTE] > [!NOTE]
> Turning on Shell Launcher does not require a device restart. > Turning on Shell Launcher doesn't require a device restart.
## Enable Shell Launcher by calling WESL_UserSetting ## Enable Shell Launcher by calling WESL_UserSetting

2
windows/configuration/shell-launcher/toc.yml
View File

@ -13,7 +13,7 @@ items:
items: items:
- name: Shell Launcher XSD - name: Shell Launcher XSD
href: xsd.md href: xsd.md
- name: Enable Shell Launcher - name: 🟡 Enable Shell Launcher
href: enable.md href: enable.md
- name: WMI Provider - name: WMI Provider
items: items: