Testing Windows 10 Assigned Access

Posted on June 28, 2016 Updated on March 12, 2017

Based upon the information in article Set up a kiosk on Windows 10, it is possible to quickly setup a Windows 10 UWP app to run with Assigned Access.  From that article, I’ve outlined (below) the quick-start steps for testing purposes.

1. Login to Windows with an account that has local admin rights.
2. Create a local user account (such as “kiosk”) with a password and do not grant the account local admin privileges.
3. Sign out of Windows.
4. Login to Windows with the kiosk user account so that it builds the profile.
5. If the tablet has physical keyboard capabilities, then change that user to use Tablet Mode and log out.  Otherwise, skip this step.
6. Login to Windows with the local admin account.
7. Edit the registry to enable auto login of the kiosk account.
8. Use the PowerShell script in this article to get the AUMID for the UWP app.
   • If you’re just looking for a quick example, use the MSN News app with ID – Microsoft.BingNews_8wekyb3d8bbwe!AppexNews
9. Based upon the information in the previous step, run a PowerShell command in this article to set the kiosk user to have assigned access to your UWP app.
10. Verify that the user was properly assigned to launch the application by:
    • Start > Settings > User accounts > Family and other users
    • Under the “Other Users” section, select “Set up assigned access”
    • Ensure the user shows the application

Also, to sideload a UWP application, see this information: https://msdn.microsoft.com/en-us/windows/uwp/packaging/packaging-uwp-apps#sideload-your-app-package.

More information on best practices for developing UWP apps for Assigned Access: https://msdn.microsoft.com/en-us/library/windows/hardware/mt633799.aspx