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

Update kiosk configuration documentation

Browse Source
This commit is contained in:
Paolo Matarazzo 2024-02-29 13:27:00 -05:00
parent bd6bee01af
commit e626ddb69a
3 changed files with 3 additions and 11 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

@ -7,9 +7,7 @@ ms.date: 02/05/2024
# Quickstart: Configure a kiosk with Assigned Access # Quickstart: Configure a kiosk with Assigned Access
When you configure Windows as a *kiosk* with Assigned Access, you configure a single application to run above the Windows lock screen. This is useful for public-facing scenarios, such as a digital sign or a public browser. This quickstart provides practical examples of how to configure a *kiosk experience* on Windows with Assigne Access. The examples describe the steps using the Settings app, a mobile device management solution (MDM) like Microsoft Intune, provisioning packages (PPKG), and PowerShell. While different solutions are used, the configuration settings and results are the same.
This quickstart provides practical examples of how to configure a kiosk experience on Windows with Assigne Access. The examples describe the steps using the Settings app, a mobile device management solution (MDM) like Microsoft Intune, provisioning packages (PPKG), and PowerShell. While different solutions are used, the configuration settings and results are the same.
The examples can be modified to fit your specific requirements. For example, you can change the app used, the URL specified when opening Microsoft Edge, or change the name of the user that automatically signs in to Windows. The examples can be modified to fit your specific requirements. For example, you can change the app used, the URL specified when opening Microsoft Edge, or change the name of the user that automatically signs in to Windows.
@ -102,7 +100,5 @@ After the settings are applied, reboot the device. A local user account is autom
> >
> [Assigned Access overview](overview.md) > [Assigned Access overview](overview.md)
[WIN-3]: /windows/client-management/mdm/assignedaccess-csp [WIN-3]: /windows/client-management/mdm/assignedaccess-csp
[MEM-1]: /mem/intune/configuration/custom-settings-windows-10 [MEM-1]: /mem/intune/configuration/custom-settings-windows-10

4
windows/configuration/assigned-access/quickstart-restricted-user-experience.md
View File

@ -9,9 +9,7 @@ zone_pivot_groups: windows-versions-11-10
# Quickstart: Configure a restricted user experience with Assigned Access # Quickstart: Configure a restricted user experience with Assigned Access
With a *restricted user experience*, you can configure Windows to run a limited set of applications in a locked down desktop. This is useful for scenarios where you want to provide a limited set of apps to a user, such as a library catalog, a school device, or a museum guide. This quickstart provides practical examples of how to configure a *restricted user experience* on Windows. The examples describe the steps using a mobile device management solution (MDM) like Microsoft Intune, provisioning packages (PPKG), and PowerShell. While different solutions are used, the configuration settings and results are the same.
This quickstart provides practical examples of how to configure a restricted user experience on Windows. The examples describe the steps using a mobile device management solution (MDM) like Microsoft Intune, provisioning packages (PPKG), and PowerShell. While different solutions are used, the configuration settings and results are the same.
The examples can be modified to fit your specific requirements. For example, you can add or remove applications from the list of allowed apps, or change the name of the user that automatically signs in to Windows. The examples can be modified to fit your specific requirements. For example, you can add or remove applications from the list of allowed apps, or change the name of the user that automatically signs in to Windows.

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

@ -7,9 +7,7 @@ ms.date: 02/05/2024
# Quickstart: configure a kiosk experience with Shell Launcher # Quickstart: configure a kiosk experience with Shell Launcher
When you configure Windows as a *kiosk* with Shell Launcher, you configure an application to replace the default shell (`explorer.exe`). This is useful for public-facing scenarios, such as a point of sale or a business critical application. This quickstart provides practical examples of how to configure a *kiosk experience* on Windows with Shell Launcher. The examples describe the steps using a mobile device management solution (MDM) like Microsoft Intune, and PowerShell. While different solutions are used, the configuration settings and results are the same.
This quickstart provides practical examples of how to configure a kiosk experience on Windows with Shell Launcher. The examples describe the steps using a mobile device management solution (MDM) like Microsoft Intune, and PowerShell. While different solutions are used, the configuration settings and results are the same.
The examples can be modified to fit your specific requirements. For example, you can change the app used, the URL specified when opening Microsoft Edge, or change the name of the user that automatically signs in to Windows. The examples can be modified to fit your specific requirements. For example, you can change the app used, the URL specified when opening Microsoft Edge, or change the name of the user that automatically signs in to Windows.