Remove Force-Installed Extension

[Arthur]

Hi there,

According to the Chromium Policy List, I should be able to remove a force-installed extension by sending a new ExtensionInstallForceList that doesn't include that extension. For some reason, this isn't working for me. I'm using MCX in Mac OS X, and finding that the new extensions from the list get installed, but the old ones don't go away. To be more specific, if I run:

> dscl . mcxset /Users/username com.google.Chrome ExtensionInstallForcelist always '("<extension_1_id>;https://clients2.google.com/service/update2/crx")'

Extension 1 will get installed. If I then run:

> dscl . mcxset /Users/<username> com.google.Chrome ExtensionInstallForcelist always '("<extension_2_id>;https://clients2.google.com/service/update2/crx")'

and verify that the ExtensionInstallForceList property has, in fact, been overwritten:

> dscl . mcxread /Users/<username> com.google.Chrome

# Output:

# Key: ExtensionInstallForcelist

# State: always

# Value: (

#    "<extension_2_id>;https://clients2.google.com/service/update2/crx"

# )

Extension 2 gets installed as expected, but Extension 1 doesn't get removed.

Any ideas what I might be doing wrong? Does Google Chrome work differently from Chromium in this way?

Thanks,

Arthur

[Eric Landrum]

Ensure you aren't pushing the extension from the Cloud Policy in Google Apps.

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[Arthur Lewis]

Thanks Eric. We don’t have users logging into Chrome with their Google Apps credentials. (I wish we did; it would certainly make this easier.) But now I’m wondering whether the syncing of my test machine with Chrome on another machine (through a personal Gmail login) might be causing confusion. I’ll do some more testing around that and report back.

[Arthur Lewis]

Ah, it turns out it was just that one machine / Chrome setup. Seems to be working properly on every other machine I run it on. Thanks for the help!