deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 10:23:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update CSP documentation to use refreshed Assigned Access reference docs.

Browse Source
This commit is contained in:
Paolo Matarazzo
2024-02-29 16:05:22 -05:00
parent e626ddb69a
commit 8690f4a539
4 changed files with 30 additions and 797 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
windows/configuration/assigned-access/index.md
View File

@ -110,4 +110,19 @@ These locations contain the latest "evaluated" configuration for each sign-in us
"HKCU\SOFTWARE\Microsoft\Windows\AssignedAccessConfiguration" (If it doesn't exist, it means no Assigned Access to be enforced for this user.)
> [!WARNING]
> You can only assign one single app kiosk profile to an individual user account on a device. The single app profile does not support domain groups.
> [!NOTE]
> If the application calls `KeyCredentialManager.IsSupportedAsync` when it is running in assigned access mode and it returns false on the first run, invoke the settings screen and select an appropriate PIN to use with Windows Hello. This is the settings screen that is hidden by the application running in assigned access mode. You can only use Windows Hello if you first leave assigned access mode, select your convenience pin, and then go back into assigned access mode again.
> [!NOTE]
> Deleting the multi-app configuration will remove the assigned access lockdown profiles associated with the users, but it can't revert all the enforced policies (for example, Start Layout).
> [!IMPORTANT]
> - You can't set both KioskModeApp and ShellLauncher at the same time on the device.
> [!NOTE]
> To authorize a compatible configuration XML that includes 1809 or prerelease elements and attributes, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the auto-launch feature that was added in the 1809 release, use the below sample. Notice an alias `r1809` is given to the 201810 namespace for the 1809 release, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
-->

8
windows/configuration/assigned-access/overview.md
View File

@ -18,8 +18,8 @@ Assigned Access is a Windows feature that you can use to configure a device as a
A single UWP application or Microsoft Edge is executed in full screen, above the lock screen. Users can only use that application. If the kiosk app is closed, it will automatically restart. Practical examples include:
- Digital signs
- Public web browsing kiosks
- Public browsing
- Interactive digital signage
This experience is sometimes referred to as *single-app kiosk*.
:::column-end:::
@ -30,13 +30,15 @@ Assigned Access is a Windows feature that you can use to configure a device as a
:::column-end:::
:::column span="3":::
#### Restricted user experience
Users can execute a defined list of applications, with a custom and locked down Start menu and Taskbar. Practical examples include:
Users can execute a defined list of applications, with a custom Start menu and Taskbar. Practical examples include:
- Frontline worker devices
- Student devices
- Lab devices
:::column-end:::
:::row-end:::
When applying an Assigned Access configuration to a device, different policy settings are enforced, creating a locked down experience to the users.
Assigned Access profiles only apply to non-admin accounts. When an administrator signs in, the Assigned Access restrictions don't apply.
## Configure a kiosk

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

@ -36,7 +36,7 @@ Here are some limitations to consider when using Shell Launcher:
## Configure a device with Shell Launcher
To configure Shell Launcher, you must use the [Assigned Access CSP](/windows/client-management/mdm/assignedaccess-csp#shelllauncher). The configuration of Shell Launcher is done using an XML file. The XML file is then applied to the device via the Assigned Access CSP, using one of the following options:
The configuration of Shell Launcher is done using an XML file. The XML file is applied to the device via the [Assigned Access CSP](/windows/client-management/mdm/assignedaccess-csp#shelllauncher), using one of the following options:
- A Mobile Device Management (MDM) solution, like Microsoft Intune
- Provisioning packages