Windows 10: Windows 10 1809 LTSC Multi-App Kiosk Provisioning Package unexpected context menu

TCG806 · Aug 7, 2019

I have logged a premier support call with Microsoft (2+weeks old now) about this unexpected behaviour but wanted to know if the community have seen this..

Background

I have created an advanced provisioning package via the Image and Configuration Designer tool for a multi app kiosk, built the machine and installed the package via SCCM, and deployed the computers to site. All work great.

The service desk gets a call advising that users cant print on these devices via citrix. I review the logs, find the problem, create a new provisioning package and begin to test deploying it out in my lab vms and physical machines.

This is where the unexpected behaviour begins. When i go and remove the existing prov package and then install the new prov package, i reboot and the kiosk account signs in, the printing problem in citrix is resolved, however i can now right click the start menu and the context menu appears. There are no other problems except for this.

If i build the computer from scratch with this new prov package everything works fine with no context menu.

I need to find a fix so i can reapply provisioning packages without having end users able to have access to the context menu.

:)

Prakhar_Khare · Aug 7, 2019

Provision Package to control Start Menu tiles

Hello Stephen,

Thank you for writing to Microsoft Community Forums.

I suggest you to refer the article on
Building Windows 10 Provisioning packages.

However, the issue you posted is related to Provisioning packages with Windows 10 and would be better suited in the TechNet community. Please post your question in the
TechNet forum.

Hope it helps.

Let us know if you got the help you needed by clicking ‘Yes’ or ‘No’.

Regards,

Prakhar Khare

Microsoft Community – Moderator

Ericdukece · Aug 7, 2019

Kiosk mode error when using rs5:AutoLaunch="true"

Windows 10 Build 1809 LTSC. Building a kiosk system to run a desktop application.

I setup a provisioning package using WCD and included an exported a start menu layout.

When I put rs5:AutoLaunch="true" in the xml to auto launch the app The following happens.

The custom layout menu briefly displays then I get this error.

"unhandled unknown exception; terminating the application"

I click ok to that error, then click on the desktop, the custom menu shows up. I can click on my icon and the application runs fine.

No errors in the AssignedAccess log (admin or operational and I enabled operational).

No errors in AppxLocker.

Don't know where to go from here.

Brink · Aug 7, 2019

Simplifying kiosk management for IT with Windows 10

This post outlines the investments Microsoft is making to simplify the configuration and management of kiosk devices, improving Windows 10 as a kiosk platform for IT organizations. Our investments in kiosk and Firstline Worker scenarios are part of a bigger mission to simplify IT in the modern workplace.

You see kiosks everywhere you go: in airports, supermarkets, movie theaters, restaurants, banks, and many other places. Kiosks have many forms and functions. What most people don’t realize is that many of them are powered by Windows.

Windows has long been the platform of choice for kiosk devices because of its security capabilities, the availability of applications, enterprise software assurance support, and a broad ecosystem of device and peripheral partners. Today we see a growing number of IT organizations developing and deploying their own kiosk solutions using standard hardware and, in some cases, repurposing existing hardware.

We use the term “kiosk” as an umbrella term for a broad category of devices, but it generally boils down to two main scenarios:

Kiosks that are used in the “public” domain and do not require users to login or authenticate.

Kiosks that are shared by Firstline Workers to complete a specific task, which typically requires the user to authenticate before accessing the device.

Both usage scenarios have a few requirements in common:

The need for security, regardless of where the kiosks are deployed.

A consistent experience for each person who uses them, so that no one person can modify the device in a way that impacts the next user.

The need for an intuitive experience that is focused on the task at hand.

In the past year, with every Windows feature update, we’ve introduced significant improvements to our kiosk capabilities:

Assigned access enables you to create not only single app kiosks for customers, but also provides the capability to create a kiosk that runs multiple apps.

Assigned access now works with Windows 10 Pro and higher, including in S Mode.

Windows Configuration Designer includes a wizard for single-app kiosk configuration. Install a provisioning package and your device is ready to go.

Multi-app kiosks now support both Universal Windows Platform (UWP) apps and classic Win32 apps.

You can deploy curated kiosk experiences directly from the cloud using Microsoft Intune.

We continue to add more policies that enable IT to tailor the experience for end users. To name a few: power settings to enable any device to run 24/7, touch keyboard configuration policies, locked down Start screen, and more.

For more information, see Set up a kiosk or digital signage on Windows 10. You can also watch a quick demo on setting up a kiosk using Microsoft Intune or using a provisioning package.

With the upcoming release of Windows 10, version 1803, we are taking the next steps in our efforts to make kiosks even more capable – and easier to deploy and configure. Some key assigned access enhancements include:

Support for multiple screens for digital signage use cases.

The ability to ensure all MDM configurations are enforced on the device prior to entering assigned access using the Enrollment Status page.

The ability to configure and run Shell Launcher in addition to existing UWP Store apps.

A simplified process for creating and configuring an auto-logon kiosk account so that a public kiosk automatically enters a desired state after a reboot, a critical security requirement for public-facing use cases.

For multi-user Firstline Worker kiosk devices, instead of specifying every user, it’s now possible to assign different assigned access configurations to Azure AD groups or Active Directory groups.

To help with troubleshooting, you can now view error reports generated if an assigned access-configured app has issues.

Kiosk Browser

We are excited to complete the circle of support for classic Windows desktop apps and UWP Store Apps with a new Kiosk Browser app. The Kiosk Browser app is built on Microsoft Edge and can be used to create a tailored browsing experience. Kiosk Browser is great for presenting interactive web apps and digital signage content. Kiosk Browser can be configured to navigate to a default URL without showing any UI. When used with other types of kiosks, it can be configured with a list of allowed URLs and the UI elements that should be presented (e.g. navigation buttons). It can also be configured to automatically clear user data between sessions.

To ensure IT has control, Kiosk Browser can only be configured through provisioning or an MDM provider such as Intune. Please refer to our documentation for more information on how to deploy and configure Kiosk Browser.

The Kiosk Browser is available in the Microsoft Store for Business for you to try out yourself.

Looking forward

This post would not be complete without sharing some of our future plans. We will continue to make it easier for IT departments to manage, configure, and deploy Windows 10 kiosks for customers and Firstline Workers, and plan to include the following capabilities in a future Windows 10 feature update:

Deploy a kiosk device with minimal user interaction, thanks to Windows AutoPilot and device management support. Simply unbox the device, start it up, and the device is ready to go. Stay tuned; this will be available to Windows Insiders in preview soon.

Enabling device management to remotely trigger a Windows AutoPilot Reset to bring a kiosk back to a pristine state for a reliable kiosk experience.

Integration of the Kiosk Browser’s functionality directly into Microsoft Edge to support a larger scope of web scenarios.

To learn more about Windows kiosks, check out our Windows kiosk documentation. I encourage you to try out the capabilities and leave a comment below if there are other enhancements and scenarios you would like from the platform.
Click to expand...

Source: Simplifying kiosk management for IT with Windows 10 - Microsoft Tech Community - 187691

Tip How to Setup Assigned Access (Kiosk Mode) in Windows 10

Windows 10: Windows 10 1809 LTSC Multi-App Kiosk Provisioning Package unexpected context menu

Windows 10 1809 LTSC Multi-App Kiosk Provisioning Package unexpected context menu

Windows 10 1809 LTSC Multi-App Kiosk Provisioning Package unexpected context menu

Windows 10 1809 LTSC Multi-App Kiosk Provisioning Package unexpected context menu

Windows 10 1809 LTSC Multi-App Kiosk Provisioning Package unexpected context menu - Similar Threads - 1809 LTSC Multi

Install .exe app with Provision package

Windows 10 multi-app kiosk - apps not available

Setting up Windows 10 Pro as multi-app kiosk

Why is Win10 1809 removing WLAN's installed by provisioning packages?

Provision Package to control Start Menu tiles

Provisioning Package issues

Using Provisioning Packages

Create Provisioning Package in Windows 10

Windows 10 Kiosk mode not applying provisions

Users found this page by searching for:

windows10 ltsc 2019 chrome assigned-access

windows 10 1809 LTSC kiosk mode

which is better for configuring Kiosk in windows 10 provisioning package or microsoft intune