Intune - Manage Google Chrome Settings

-
Not so while ago, I covered the management of Edge browser settings in my blog here. To continue blogging on MDM management capabilities using Intune, I wanted to cover the settings for managing Google Chrome as well. 

Managing Google Chrome consists of two parts -

a. Deploying of Chrome ADMX file to the Intune managed device using a custom policy.

b. Deploying the actual set of settings using custom policies.

Let’s begin.

1. Download the Chrome ADMX template in order to ingest in Intune.
2. Sign-in to the https://endpoint.microsoft.com.
3. Browse to Devices – Windows – Configuration profiles
4. Click Create Profile
5. Choose Windows 10 and later as Platform
6. Choose Custom as Profile type
7. Click Create
8. Give a name
9. Add OMA-URI settings as covered below

Name: Chrome ADMX
OMA-URI: ./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Chrome/Policy/ChromeAdmx
Data Type: String
Value: Copy the entire content of the ADMX file.

Name: HomepageLocation
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/HomepageLocation
Data Type: String
Value: <enabled/> <data id="HomepageLocation" value="https://www.google.com"/>

Name: HomepageIsNewTabPage
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/HomepageIsNewTabPage
Data Type: String
Value: <Enabled/>

Name: ShowHomeButton
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/ShowHomeButton
Data Type: String
Value: <enabled/>

Name: RestoreOnStartup
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/RestoreOnStartup
Data Type: String
Value: <enabled/> <data id="RestoreOnStartup" value="4"/>

Name: RestoreOnStartupURLs
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/RestoreOnStartupURLs
Data Type: String
Value: <enabled/> <data id="RestoreOnStartupURLsDesc" value="1&#xF000;www.google.com"/>

Name: ManagedBookmarks
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome/ManagedBookmarks
Data Type: String
Value:<enabled/>
<data id='ManagedBookmarks' value='[{"toplevel_name":"rahuljindalmyit"},{"url":"https://www.yammer.com/rahuljindalmyit.com","name":"Yammer"},{"url":"https://rahuljindalmyit.sharepoint.com","name":"Sharepoint"},{"url":"https://rahuljindalmyit-my.sharepoint.com","name":"Files - OneDrive"}]'/>

Name: AutofillAddressEnabled
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome/AutofillAddressEnabled
Data Type: String
Value: <disabled/>

Name: AutofillCreditCardEnabled
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome/AutofillCreditCardEnabled
Data Type: String
Value: <disabled/>

Name: BookmarkBarEnabled
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome/BookmarkBarEnabled
Data Type: String
Value: <enabled/>

The end result will be something like this –
 
User Experience

You can navigate to chrome://policy and check for the policies.
 

Settings will come into effect as shown below for Homepage, favorites.


References:

Comments

  1. AmirNovember 22, 2021 at 8:32 PM

    Excellent Article

    ReplyDelete
  2. Dslr Camera PriceApril 25, 2022 at 11:59 PM

    Thanks for sharing this information. I really like your blog post very much. You have really shared a informative and interesting blog post . how to dragclick

    ReplyDelete
  3. Dslr Camera PriceApril 25, 2022 at 11:59 PM

    Thanks for sharing this information. I really like your blog post very much. You have really shared a informative and interesting blog post . how to dragclick

    ReplyDelete

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){              ...
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from st...
Read more

Fixing Tamper Protection Blob Error 65000 using Microsoft Intune

-
Image
I recently encountered an issue with enabling Tamper protection as part of the implementation of Defender for Endpoint in one of customer's tenant and considering how unusual the behavior was and how I didn't encounter this before, I decide to blog my experience. If you have been battling with the same issue, then this blog may just help you. There are multiple ways to enable Tamper protection as part of MDE. One can enable at a tenant level using Defender portal or do it using Intune. I normally choose the Intune, especially when dealing with endpoints to maintain uniformity with other Defender policies being managed by Intune. However, in this particular instance, the issue started cropping randomly on some endpoints where tamper protection would not enable and throw an error code 65000, as show below. Additionally, the status in Defender will report as Unknown instead of reporting Active or something else like EDR in block mode to suggest that Defender Antimalware is running...
Read more