flowerskvm.blogg.se

Be careful when copying and pasting the "Value" data above in respect of the speech marks ("") as if they are wrong, you'll get a remediation error within Intune. Double-click each item and in the General tab under Startup Type, select Disabled from the dropdown menu and click OK. Scroll down to Google Update Service (update). Once it opens, type services.msc and hit Enter. Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~NativeMessaging/NativeMessagingWhitelist You can do this by using the keyboard shortcut Win + R or searching for Run using Cortana. Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~NativeMessaging/NativeMessagingBlacklist

To use the legacy policies, add the following Blacklist and Whitelist in: Once this policy was updated to the new version or a whitelist entry added for the extension for the older policy version, it worked.ĮDIT: Please note that the above NativeMessagingBlocklist and NativeMessagingAllowlist are only supported in Chrome 86 and onwards. Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~NativeMessaging/NativeMessagingBlacklist This was the original problem setting within Intune in the custom OMA-URI format with no whitelist set: You can either add in NativeMessagingWhitelist with your exceptions or use the newer Chrome policy of NativeMessagingBlocklist.

One of those policies (which is now deprecated by Google) - NativeMessagingBlacklist with a wildcard (*) blocks access to the Native Messaging API's. We use Chrome CIS Level 1 security benchmarks that use ADMX ingestion (Chrome ADMX). I did try older versions of Windows 10 (1903 etc.) and this wasn't the issue. Hi and McAninch, I managed after some lengthy testing, to get to the bottom of the problem for us.