[Jaruzel]

Key point (for Windows) on that page is:

  ADM/ADMX templates with 300+ user and device policies

ADM/ADMXs are a list of settable policies (rules) that Chrome will read from the Windows Registry on startup[1]. I'm going to make a huge assumption that the Chrome.exe for Enterprise users is no different to the Chrome.exe that everyone else uses, and it switches into 'Enterprise' mode if it sees certain key policy entries in the Registry[2].

These polices are typically set on a Windows Domain Controller and are pushed to Domain member machines (and users) on the network on a regular basis.

However end-users can simulate the policies by setting these Registry entries manually (There are about 4 places in the Registry where they live). Depending on where Chrome looks, the user may need local admin privileges to do this.

So, what we really need is a 'Chrome Enterprise Enabler' tool, that does this automatically for non-technical users. They would run this tool, the required Registry keys would be enabled, and WebRequest API based Ad-blocking would continue to work.

Unfortunately, none of this helps Linux users as I don't see a Linux Enterprise Chrome package.

---

[1] I've got 25+ years of Windows domain administration under my belt, this stuff used to be my bread-and-butter.

[2] Even if not, extracting just the Chrome MSI installer from the Enterprise bundle is trivial.

[discreditable]

Chrome MSI and chrome EXE installers work a little differently. The MSI installer by default installs to the program files directory. I've seen the EXE installer often installed to the local user profile. to convert a regular install to Enterprise you would probably have to uninstall the local version and then install the MSI.

ADM templates are something Firefox is sorely lacking at the moment. I remember reading that it is on the road map but that does not help out much. Nevertheless, I installed both chrome and Firefox and my organization. I like Firefox and use it myself, but sadly it's just not as easy to administer as chrome.

[amaccuish]

So two things. The MSI installer will convert a local (EXE) installation to a global install (updating shortcuts and removing the local profile install whilst preserving the chrome profile).

Second, Firefox does have ADMX policies (ADMX being used primarily after Vista): https://github.com/mozilla/policy-templates. I believe it took them so long because they were initially reluctant, user freedom etc. But I guess Chrome's success in enterprise made them reconsider. Honestly I never considered Firefox for our Windows Domain because of the lack of Group Policy support. Now I deploy both and users have options :)

[jchw]

FWIW it Is supported under Linux I believe, but unfortunately the documentation is lacking. If I recall correctly, you have to drop JSON files in the right places.

[rando444]

These are just features and settings, there's no requirement to use them.

The main point isn't listed on the page.

The Enterprise installer installs Chrome to the operating system.

Regular chrome installs in your user profile.

[Jaruzel]

> These are just features and settings, there's no requirement to use them.

I think you missed my point. Google say that the Enterprise version will continue to support WebRequest API. If the Enterprise version is the same codebase as the normal version, then it's a good educated guess that the Policy keys are whats controlling that.