Skip to main content

Hi Guys,

 

working on a project where i need to force install certain extensions in Edge. They Keys are there and I have tried configuring using profile creator, JAMF JSON and BIll's JSON. No luck. Edge sees that its managed and allowed extensions install no problem. Blocked extensions are blocked, but those that should be force installed are not working. reaching out asking am I missing a recent change and if anyone has these working?

 

TIA

We are using a custom plist to force install edge extensions 

<key>ExtensionSettings</key>
<dict>
<key> enter the extension</key>
<dict>
<key>installation_mode</key>
<string>force_installed</string>
<key>update_url</key>
<string>Enter the Url</string>
</dict>
</dict>
 
For more details please check the Microsoft documentation 

@vinu_thankachan  can you post a sanitized version of what you are doing.

Example 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ExtensionSettings</key>
<dict>
<key>rgaejpfbsdjmgheoingdqhokbbgrdlpi</key>
<dict>
<key>installation_mode</key>
<string>force_installed</string>
<key>update_url</key>
<string>https://clients2.google.com/service/update2/crx</string>
</dict>
</dict>
</dict>
</plist>

@vinu_thankachan  thanks, still not working for . extension not being force installed. Going to put this down for a while. Thanks for assistance.

Did you ever make anything of this? I recently had a need to update my list of extensions I force-insall and found that they install in a very hit or miss fashion.  Even on my personal test computers they are sometimes there, sometimes not, and randomly disappear at times.

@easyedcstill saw issues with those, but nextthink worked as expected. maybe vendor related?

I think I found my cause - my predecessor had created a stand-alone profile deploying settings for a single extension. I took that and included it into my single profile managing Edge and it worked.

I think I found my cause - my predecessor had created a stand-alone profile deploying settings for a single extension. I took that and included it into my single profile managing Edge and it worked.


The following worked for me. Bill's Solution and adding the following for chrome extensions to use in Edge:

https://clients2.google.com/service/update2/crx. works 100% of the time. This was also mentioned by @vinu_thankachan 

Reply


Terms & ConditionsCookie settings