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!
Solved! Go to Solution.
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/
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
@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...
Hello lturnerz: below are very simple steps to manage this through jamf Pro
I don't think you can make Chrome the default system browser within the Chrome update policy. This thread is so confusing, people are talking about two different things here. You should take a look at this bash script I posted earlier. It's still working for me on 12.2 after a Mac reboot.
How does this work in your environment once deployed? From my testing, if a user doesn't already have Chrome set as the default browser in System Preferences>General>Default Web Browser, once a user opens Chrome they are not prompted to select the default browser without first having to click the Set as Default button anyway. Meaning, it's the same as doing nothing at all.
Is this what you are experiencing as well? This is happening on a couple of test machines running Big Sur.
No change after upgrading my M1 Mac to Monterey and testing this. Are you also deploying to M1 Macs or Intel Macs only (wonder if there is something happening there)? You mind pasting your PLIST from your config to compare?
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.
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.
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">
User is prompted to change the default browser to Chrome upon launch.
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?