badmvp.blogg.se - Google chrome homepage settings

The first OMA-URI to create is to ingest the ADMX file downloaded earlier along with Google Chrome bundle, once extracted, you should see a chrome.admx file, keep this to one side for the moment.

Download the Google Chrome Enterprise 圆4 bundle here.

Test account with a valid Intune license assigned.

Test Windows 10 device enrolled into the MEM service.

Administrative permissions within MEM Portal.

We won’t go into a deep dive on how OMA-URI’s work, but you can find out more information about ADMX backed OMA-URI’s here.

Hide the app’s icon in the bookmark barīecause we’re deploying 3rd party application policies, the functionality to manage Google Chrome isn’t available out of the box via MEM, to get around this we’ll deploy a custom profile utilising OMA-URI’s (Open Mobile Alliance Uniform Resource Identifier), these settings are typically used by mobile device manufacturers to control features on a device, the purpose of custom OMA-URI’s is to deploy ADMX backed profiles that aren’t natively built into MEM.

Force the Windows 10 accounts and Windows Windows Defender Browser Protection extensions.

As part of this post, I will demonstrate how to deploy the following Google Chrome policies: