User Profile
Raj_GS
MicrosoftJoined May 15, 2019
User Widgets
Recent Discussions
- 4.6KViews0likes0Comments
Re: GPO Force InPrivate browsing setting breaks webview2 client.
artroy , A few questions/suggestions: You mentioned "multi app use": Is this referring to the multi-app kiosk mode in Windows? If not, have you tried evaluating this mode for your needs? Set up a multi-app kiosk on Windows 10 - Configure Windows | Microsoft Docs This mode locks Windows down to only the allowed apps and prevents the regular taskbar and "normal" start menu from showing up. Here's an example solution post that maybe of relevance to your needs: Setup an Edge Chromium based Kiosk device with Microsoft Intune | (inthecloud247.com) You mentioned trying out Edge kiosk as an attempt to migrate from WebView2, though, "After making that change all webview2 clients threw an error upon launch" indicates the apps are still using WebView2. Is this still a requirement? Instead of forcing InPrivate mode, have you tried other policies to prevent users from modifying settings? Here are some suggestions: AddressBarEditingEnabled - though this would mean users CANNOT modify the address bar contents at all URLBlocklist and/or URLAllowlist Let us know how this goes 🙂4KViews1like2CommentsRe: Edge - On-Screen Keyboard - Not Working
frustin , Sorry to hear that! How have you configured Edge kiosk? Is it via the Settings UI workflow to setup a kiosk (or maybe Intune, Powershell, etc) or are you just running Edge in kiosk mode as a normal user via the documented command-line args? Is this public browsing or digital/interactive signage?12KViews0likes1CommentRe: Windows 10 Kiosk with Edge Chromium
ggbnz2230 , Thanks! The new Edge is Win32-based and so, Set-AssignedAccess cannot be used to configure it as kiosk app, as that command only works with UWP apps. To configure Edge as single app kiosk with Assigned Access, you'll have to use WMI Bridge solution: https://docs.microsoft.com/en-us/windows/configuration/kiosk-mdm-bridge. Look for the Powershell samples linked from that page too. Cc: @edgebrk3.5KViews0likes1CommentRe: Windows 10 Kiosk with Edge Chromium
ggbnz2230 I have not tried this option myself, so would relay this back to some experts who may know better. But in the meantime, some dumb questions: 1. I hope you are trying "-AppUserModelId" as in the docs and not "-AUMID" as you mentioned in the post? 2. Are you also supplying the user name/SID via the options mentioned in the docs when using the "Set-AssignedAccess" command line? This is the doc I'm referring to in the above: https://docs.microsoft.com/en-us/windows/configuration/kiosk-single-app#powershell3.5KViews0likes3CommentsRe: Windows 10 Kiosk with Edge Chromium
jsundelius Glad you were able to figure out the cause! 🙂 Yep, the new Edge has a separate entry and the "old" Edge is now shown as the "Edge Legacy" entry in InTune and this change was recently rolled out in InTune. Multi-app has supported the new Edge ever since new Edge was released - as multi-app supported Win32 apps too.4KViews0likes0CommentsRe: Issues with Kiosk Mode Refresh
Zoltan_GYORGY , Its great to hear that you'll be able to use the new Edge kiosk with Shell Launcher or Assigned Access for your needs! 🙂 To try the new Edge kiosk with Assigned Access: Use a Windows 10 (Pro, Enterprise, and Education according to the documentation here: https://docs.microsoft.com/en-us/windows/configuration/kiosk-single-app) build with the latest updates. Install the new Edge Stable, Beta or Dev channel (these should install by default at system level) Then follow the instructions here: https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-configure-kiosk-mode#configure-using-windows-settings With Shell Launcher, Edge GPOs should work (true for Assigned Access too). I believe Windows GPOs may work for Shell Launcher (have not tried this though)16KViews0likes0CommentsRe: Issues with Kiosk Mode Refresh
Zoltan_GYORGY , Our kiosk documentation is still a work in progress. The "reset" part, as you observed, only closes out the current kiosk session and does not relaunch Edge kiosk with the designated page. This is because Edge kiosk is typically meant to be setup in combination with Windows features like Assigned Access (https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-configure-kiosk-mode#single-app-kiosk) or Shell Launcher (https://docs.microsoft.com/en-us/windows/iot/iot-enterprise/kiosk-mode/shell-launcher) for a complete kiosk experience - these Windows features take the responsibility of relaunching the configured app. Hope you are able to leverage any of these Windows features to fit your scenario for Edge kiosk!17KViews0likes2CommentsRe: Microsoft Edge hanging in Kiosk Mode (Reproduceable)
The_Naval_Museum , Thanks for the update! Glad to know that you have a way to simply lock down Windows to your needs - I'm guessing it is using many of the Windows lockdowns, like Applocker, Keyboard filters etc , but yes, it is convenient to just have some simple config tool especially when your needs are simple and maybe required just for 1 to a few devices 🙂 We do lock down a bunch of things as part of our "single app" restriction in Windows Assigned Access - so it is highly likely that something there is causing this issue too. I'll pass this info on to the team that is best equipped to look at your issue (along with your feedback hub report regarding the virtual keyboard).3.9KViews0likes0CommentsRe: Microsoft Edge hanging in Kiosk Mode (Reproduceable)
The_Naval_Museum , First off, I'm really excited each time I see real customers trying the features that our teams worked on and the videos just amped that feeling up. So I'd really love to see this succeed! 🙂 Thanks for posting this as a separate thread based on my request! The videos and the code chunk were useful in furthering my understanding of your setup. I believe you already sort of answered your query - you have a server on the same device that you're trying to access its contents too. Based on my (limited) understanding, here are a few things happening: 1. Edge kiosk is able to see the html file, as it loads the .gif. But it does not load your expected webpage. 2. FYI, the "Kiosk" user that you'd setup is a local account with regular user privileges. The web server has most likely been configured via the admin user and the web server/sql backend service may all be set to start when that admin user logs in. 3. The problem "goes away", if you login as the admin and log back in as the Kiosk user. Given the above, it seems the act of logging in as the admin user starts the webserver and the sql backend, thereby making your local site fully available/ready to be served. When you log back in as the Kiosk user, Edge kiosk is now able to navigate to your pages. In the normal flow though, Kiosk user auto logs on upon the device boot up and hence, the web server and sql backend may not start running at all. Would it be possible to configure the web server and sql backend to start when the system boots up (or when ANY user logs in)? Even in this case, you will most likely run into hiccups - Assuming Windows allows such startup requests for the Kiosk user, Windows Assigned Access will launch Edge kiosk (the designated app) soon as the Kiosk user logs in. Even if you configure the web server and sql backend to start for all users, Edge kiosk may have trouble loading the site depending on the order in which these things finish. Is a non-local site an option at all? If so, that will be your best and safest bet. If not, here are a couple of things to try: 1. Configure your web server and sql backend to start at system boot up or when ANY user logs in. 2. Assuming step 1 works for the Kiosk user, have a static landing page that kicks off a delay timer for 'N' seconds (you might need to play with this to figure out the best value for 'N' - make sure to add some buffer to it) and then tries loading your site. Let me know how this goes!3.9KViews0likes2CommentsRe: Edge - On-Screen Keyboard - Not Working
The_Naval_Museum , do you mind starting a new thread for this? Having separate threads for issues would help with discoverability of the new issue and will also keep the original thread's intent intact. Also, for the original issue, do you mind submitting a feedback via Feedback Hub (the admin or some other normal user) under the category "Security and Privacy" > "Assigned Access"? This will collect additional logs relevant to the category, which might help the dev team debug the issue better13KViews0likes4CommentsRe: Hide address bar by policy request
Jeffrey_Fronius , Unlike Legacy Edge, the new Edge can be configured to run in kiosk mode as a normal user too - you just need to use the right command-line args when launching Edge to have it run in kiosk mode (you could update the shortcuts too). Since you'll be running this as a normal user, they have access to the whole desktop environment. When Edge runs in kiosk mode, you have access to the KioskAddressBarEditingEnabled policy, which can be used to make the address bar read-only. While this does not hide the address bar, you can at least prevent your users from editing it. FYI, the new Edge supports an "app" mode too.5.8KViews0likes0CommentsRe: Microsoft Edge Kiosk Mode New Tab/New Window Shortcuts
Jeffrey_Fronius , Not sure if you had a chance to review the doc links that Kelly provided. Similar to the Legacy Edge's kiosk offering, Windows Assigned Access feature now supports the new Edge in single app kiosk mode (in Insider builds for a few weeks now) - via Settings UI, Intune, Powershell scripting, etc. When you configure Edge kiosk using Assigned Access's single app mode, you'll notice that we lockdown Ctrl+N. Ctrl+T is not blocked though. In case you had a chance to try this out, let us know what you think!8.1KViews0likes0CommentsRe: Issues with Kiosk Mode Refresh
KrysKy , The --kiosk-idle-timeout-minutes option is only available with the --edge-kiosk-type=public-browsing (5 minutes timeout default if --kiosk-idle-timeout-minutes is not specified) and --edge-kiosk-type=fullscreen offerings (defaults to no timeout). Could you please try the timeout with this additional command line arg/value combo and get back to us in case you still have issues?16KViews0likes0CommentsRe: Edge - On-Screen Keyboard - Not Working
The_Naval_Museum, thanks for the ping! I'm assuming you're referring to the new Edge's kioks mode? Keith should have setup kiosk with the new Edge EITHER in a normal user setup (with/without ShellLauncher configured to launch Edge in kiosk mode) OR using the Windows Assigned Access multi-app kiosk mode - both of which were supporting the new Edge ever since it released to Stable a couple of years ago. 1. Are you using the Settings UI's "Setup a kiosk (assigned access)" option (which started supporting the new Edge in Insider builds very recently)? If not, could you please let me know how you are setting up the kiosk experience? 2. What version of Windows (as seen when you run 'winver') and what version of Edge (and what channel of Edge) are you using to setup the kiosk? The above info will help root cause the issue on our end.13KViews0likes8Comments
Recent Blog Articles
No content to show