Forum Widgets
Latest Discussions
Chrome extension managed storage policy
Hi there, I've developed a chrome extension and now we want to deploy it using Intune. Force install of extension works great but I can't pass managed data to the extension. Here is the scheme: { "type": "object", "properties": { "apiKey": { "title": "API Key", "description": "An API key to communicate with server.", "type": "string" } } } This is the policy that I created in Intune: OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~3rdparty~extensions~eagefwefpbjpewefliifpgfgoewfknnmk~policy Data type: String Value: {"apiKey":"mykey123"} But it doesn't appear in chrome://policy and when I get policies in my code with: const result = await chrome.storage.managed.get(null); The result is empty! What is the problem here? And how to fix it?
Edge for Android top bar after update to 121.0.2277.105 version
On a work fully managed Android device, after the Edge for Android app was updated to 121.0.2277.105 version when I open the Edge app on top of the screen I get a bar named "Edge" that will take from the screen and is very annoying. I noticed that this is happening only if I am not prompted to enter the device PIN when I open the app, if I am prompted to type the PIN then the content is rendered properly. A workaround that I find was to change the device theme but this will be only a temporary fix as next time if I will open the app and I am not asked to type the PIN the top bar will reoccur. The application protection policy is enforced via Intune, and for inactivity we have 10 minutes set up for recheck the access. Anyone come across with this issue? Thanks. Mario
BrowsingDataLifetime crashes Edge
Edge 120 (stable, beta and dev) all seem to be crashing on launch when the BrowsingDataLifetime is set. I've cleared all other policies to rule out any conflicts and set the policy to the example in the policy reference. We only had the policy in test, so there's no impact to us, but it is still concerning.
Edge Dev > Enterprise State Roaming / Sync Broke
I noted in Edge DEV my profile stopped syncing even though its set by policy to be on the journey took me to edge://settings/profiles/sync where turn on sync is presented - so i turn it on a confirm and cancel button appear as well as the expected other areas (but showing as off by policy???) hitting confirm just makes confirm and cancel disappear with no changes these are not new? what gives or is changing? is sync just broke in dev for now? Edge Beta and Stable are not impacted.
Microsoft Edge Group Policies for lists like Pop-ups do NOT combine -they replace unlike IE?
We have 86,000 health computers we are migrating to Microsoft Edge from IE 11. In Group Policy for IE if you add "pop-up allow list" at a root group policy, and then another lower group policy the pop-up lists MERGE. So pop-ups allowed in the root policy and pop-ups allowed in the lower policies BOTH get added to the computer. This goes for all the other IE GPO settings. However, for Microsoft Edge it is a REPLACE in policy and registry which is really, really bad for Enterprise. If we allow 20 sites to not block popups then those 20 sites should remain EVEN if a subset of the organization wants to add their own sites to the list. The same seems to go for all these "list" type Edge policies. Anything that has a list if it is set again, the list gets replaced instead of appended. There is absolutely no reason why it is not working. Group Policies have always been set to COMBINE and in the case of the Edge Policies they also should combine" not replace. Note the registry keys get replaced too.
Starting Edge as a process immediately fires exited event
Hi! Recently I have encountered a rather annoying bug on Windows 11 IoT LTSC where I launch an edge as a process from my .net 9.0 C# code. I need to track Edge and if it exits for some reason I have to relaunch it. I'm tracking whether it has exited by subscribing to the Process.Exited event, but on the beforementioned operating system this event immediately fires even though the Edge itself visibly does not close and stays functional without any problem. This results in infinite edge processes getting launched, since every new instance also exits. Interestingly this issue does not occur when tested with other browsers nor it occurs on Windows 11 Pro, everything works completely fine in these two scenarios. I'm guessing IoT version has some kind of different power plan to reduce battery drainage and CPU usage if possible. My other assumption is that the msedge.exe available with default windows is just a parent process on the IoT version, and it just starts the actual processes needed to present the content of my web app. It'd be great if you could check this and come back to me. Thank you! Kind regards, Gallusz.Tell me about Password Protection...
I'm going through the available policy settings for edge, getting a policy ready ahead of the upcoming release, and saw these settings related to password protection. https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#passwordprotectionwarningtrigger https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#passwordprotectionloginurls https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#passwordprotectionchangepasswordurl I understand that this will trigger warnings if the user enters their "Protected Password" on a site other than those listed in the policy, but I don't see anything explaining what makes something a "protected password". Is it their AD/AAD password? Or can they specify passwords to be protected? Or...? Other than the description of the policy setting itself, I can't find any information on this password protection feature of Edge. Is there any documentation out there explaining more about it, or can anyone in the know share info on it?
