Skip to main content

Hi all!

We are currently testing our implementation of Jamf Pro Cloud. I am trying to set Chrome as the default browser for my organization, but I cannot find the option to do that through Jamf. And anything online about this is over a few years old. I just wanted to check in and see if there has been a change to this, or if anyone has a clever way of getting around it!

Thanks!

Hi Jonna, Would be kind enough to show me the steps that you did on Imazing? Sorry Im new with jamf as well


You can check below link:

https://imazing.com/guides/getting-started-with-imazing-profile-editor


Hello,

Here is the easy and best way to manage Chrome Browser through jamf.

https://support.google.com/chrome/a/answer/9923111?hl=en

 

Regards,

Salim Ukani


@Samstar777 As with other confused people below, I don't understand how this is marked as the solution.

Your link provides instructions for how to manage updates, but I don't see how you would manage the default browser using this method.  These are 2 different things.

Please provide instructions on how you can use the above link to manage the default browser for a user...


For those still wondering, you'll need to use iMazing Profile Editor to create the config profile with the Google Chrome payload which includes the Set Google Chrome as the default web browser option which is all you need and then to sign the profile.

The part where I was having trouble was the importing of this profile into Jamf Pro because in Jamf Pro after importing the signed profile, no payload showed up for this profile in Jamf Pro. I did not realize that this was normal because Jamf Pro has no corresponding Google Chrome payload. But once you deploy it out it should work to prompt the user to choose their default browser when they launch Google Chrome.

TLDR: Sign the iMazing profile before importing it in Jamf Pro or it won't work.


For those still wondering, you'll need to use iMazing Profile Editor to create the config profile with the Google Chrome payload which includes the Set Google Chrome as the default web browser option which is all you need and then to sign the profile.

The part where I was having trouble was the importing of this profile into Jamf Pro because in Jamf Pro after importing the signed profile, no payload showed up for this profile in Jamf Pro. I did not realize that this was normal because Jamf Pro has no corresponding Google Chrome payload. But once you deploy it out it should work to prompt the user to choose their default browser when they launch Google Chrome.

TLDR: Sign the iMazing profile before importing it in Jamf Pro or it won't work.


Doing all that to get a prompt, what's the different from my script above which also prompt user to set Chrome as default? 


Doing all that to get a prompt, what's the different from my script above which also prompt user to set Chrome as default? 


No difference at all. In fact, your script looks to be a better option as it requires much less legwork.


Doing all that to get a prompt, what's the different from my script above which also prompt user to set Chrome as default? 


I think the config profile is better because it’s forced where as the script needs to run at least once.


https://chromeenterprise.google/policies/?policy=DefaultBrowserSettingEnabled here is the syntax for the https://support.google.com/chrome/a/answer/9923111?hl=en workflow. like you would for a plist you enter in the syntax given from the first article in save. scope and test. Although, this is not practical for engineering orgs. As if you set it to true it hardens itself to Chrome. Blank lets the user decide. 


This is all you need, user will get the prompt on launch of Chrome though.



This is all you need, user will get the prompt on launch of Chrome though.


Can you post that plist in text form, so I don't have to manually transcribe what's in the screenshot?


Can you post that plist in text form, so I don't have to manually transcribe what's in the screenshot?


Here's an example of how the .plist key value pairs should be set to enable Google Chrome as the default browser:

 

<?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>DefaultBrowserSettingEnabled</key>
<true/>
</dict>
</plist>

 

User is prompted to change the default browser to Chrome upon launch.


Hi guys,

I actually have the same setting working for some time already, and I am currently increasing the scope.
All smooth, but when on ADE devices, the 1st time Google Chrome is launched I get 2 prompts of this type.

When I exclude the devices recently built/enrolled into JAMF, the config does not take action and no prompt appears...
I was expecting Google Chrome would always prompt on the 1st run but I still can't understand what I'm missing here.

Did anyone experience something similar before?

Best regards!


I'm using this this script after Chrome installation. You need to fill parameter 4 with com.google.Chrome. Works after a computer restart.


Thanks I just took out the parts about Apple Mail and confirmed this worked on a machine after a reboot! Maybe I will just add a reboot in the script to make sure it happens.


There has not been a change afaik due to it being a user based setting. You can always try 

open -a "Google Chrome" --args --make-default-browser

 

and see if that works. I think it would need to be a script run in a policy once per user / per computer. May also need to run it as the user by following this: https://scriptingosx.com/2020/02/getting-the-current-user-in-macos-update/


I think this one is the real correct answer. There doesnt seem to be a way to script it without adding a 3rd party app to do it and I needed it to automatically set rather than give users the choice so I added another message to the script to make sure users know what they should do:

/usr/local/bin/jamf displayMessage -message "Please set Google Chrome as the default browser" open -a "Google Chrome" --args --make-default-browser

 


This is what I use. We let users pick

 

#!/bin/bash osascript <<EOD set result to button returned of (display dialog "Set default browser to Chrome") if result = "OK" then do shell script ("open -a 'Google Chrome' --args --make-default-browser") else display dialog "No change in the default web browser" end if EOD

 

 


Do you think this script could be use to just force users to have Chrome as their default browser, without any interaction?
Do you know how to push the script after Chrome is already installed on the device?
Thank you!


Do you think this script could be use to just force users to have Chrome as their default browser, without any interaction?
Do you know how to push the script after Chrome is already installed on the device?
Thank you!


if the script works then you could run via a policy scoped to a Smart group to check if Chrome is installed but from my tests Apple still will show a box confirming you want Chrome to be default.


if the script works then you could run via a policy scoped to a Smart group to check if Chrome is installed but from my tests Apple still will show a box confirming you want Chrome to be default.


Have you been testing with the script above?
It's ok for me even if the apple popup shows up asking you to make it the default browser