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

Update kiosk configuration files

Browse Source
This commit is contained in:
Paolo Matarazzo 2024-02-29 13:23:40 -05:00
parent 2c2c7d6d64
commit bd6bee01af
3 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
windows/configuration/assigned-access/quickstart-kiosk.md
View File

@ -61,8 +61,6 @@ Here are the steps to configure a kiosk using the Settings app:
[!INCLUDE [quickstart-kiosk-intune](includes/quickstart-kiosk-intune.md)]
[!INCLUDE [intune-custom-settings-2](../../../includes/configure/intune-custom-settings-2.md)]
Alternatively, you can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].
- **Setting:** `./Vendor/MSFT/AssignedAccess/Configuration`
@ -70,6 +68,8 @@ Alternatively, you can configure devices using a [custom policy][MEM-1] with the
[!INCLUDE [quickstart-kiosk-xml](includes/quickstart-kiosk-xml.md)]
Assign the policy to a group that contains as members the devices that you want to configure.
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
[!INCLUDE [provisioning-package-1](../../../includes/configure/provisioning-package-1.md)]
@ -102,7 +102,7 @@ After the settings are applied, reboot the device. A local user account is autom
>
> [Assigned Access overview](overview.md)
<!--links-->
[WIN-3]: /windows/client-management/mdm/assignedaccess-csp
[MEM-1]: /mem/intune/configuration/custom-settings-windows-10

8
windows/configuration/assigned-access/shell-launcher/index.md
View File

@ -53,6 +53,8 @@ You can configure devices using a [custom policy][MEM-1] with the [AssignedAcces
- **Setting:** `./Vendor/MSFT/AssignedAccess/ShellLauncher`
- **Value:** content of the XML configuration file
Assign the policy to a group that contains as members the devices that you want to configure.
#### [:::image type="icon" source="../../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
[!INCLUDE [provisioning-package-1](../../../../includes/configure/provisioning-package-1.md)]
@ -93,6 +95,10 @@ Depending on your configuration, you can have a user to automatically sign in to
## Next steps
> [!div class="nextstepaction"]
> To learn how to configure the Shell Launcher XML file:
> Learn how to configure the Shell Launcher XML file:
>
> [Create a Shell Launcher configuration file](configuration-file.md)
<!--links-->
[MEM-1]: /mem/intune/configuration/custom-settings-windows-10

2
windows/configuration/assigned-access/shell-launcher/quickstart-kiosk.md
View File

@ -35,7 +35,7 @@ The examples can be modified to fit your specific requirements. For example, you
[!INCLUDE [quickstart-intune](includes/quickstart-intune.md)]
[!INCLUDE [intune-custom-settings-2](../../../../includes/configure/intune-custom-settings-2.md)]
Assign the policy to a group that contains as members the devices that you want to configure.
Alternatively, you can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].