The end of the "Easy" way of CCK2 is forcing a couple of clients of mine to migrate to Google Chrome.

@RobertHammen I had a meeting yesterday and we came to the conclusion to drop support for Firefox. It will be an optional download in Self Service, but it won't be updated often unless Mozzila changes their mind.

Edit: With the recent changes in Chrome, we might have to roll back that decision.

@RobertHammen it'll be interesting to see how the loss of NPAPI plug ins plays out for Chrome. I've never seen a chromium thread go on and on like this one

oops posted wrong link earlier Correct Chromium NPAPI link

@daz_dar Do you happen to know if there is a JSS recipe for that? I'd like to use it, but I know how annoying it'll be to have a different process for one and only one package everytime Firefox updates. It'd be great if I can get it into the same kind of workflow I have for every other package made by AutoPkgr.

Hi @McAwesome

There's not a JSS recipe but there is a .pkg one by @gregneagle that works awesomely. It'll spit out a standard pkg with the version number already part of the name. It's not too much work to upload this and modify your smart groups and / or policies.

However if you're running the newer versions of AutoPKG (the exact version escapes me) you can use the 'autopkg search' command to look for Firefox recipes and see what it has.

Last option is to have a crack at a .jss recipe that'll take the output from greg's one and import it into your JSS?

Time permitting I may even get a chance to have a go!

Darren

Has anyone gotten this to work for Firefox 38.2 ESR? Using CCK 2.1.1 and the Distribution folder no longer exists. It also looks like the location of the files has changed as well. Thanks.

Perhaps your version of CCK ... try to find v2.1.1.6

Always a moving target. As mentioned a bunch earlier in thread, Greg Neagle has a autopkg recipe that (with some overrides) will help automate. He has an article in a recent MacTech (#350) that is a good history lesson/overview.

edit: still seems to work with Firefox ESR 38.2.0 and AutoPkg(r) recipes ... our CCK customization needs are modest though.

Get autopkg(r) installed with repos containing Firefox and FirefoxAutoconfig recipes. (make-override)s of aforementioned recipes. I recall just editing the Firefox.pkg.recipe override and changing the release key string to "latest-esr" ... then make sure your CCK-generated "autoconfig.zip" is in the directory of your recipe overrides.

IS anyone having issues with ESR 38.3? My process that was working fine through ESR 38.2.1 causes ESR 38.3.0 to not boot. Were there changes in 38.3.0 that my googlefu is not finding?

Still working/launching for me with 38.3.0, but our changes are modest (setting default home page, setting a few bookmarks and changing to Google search). autoconfig.zip was built using CCK2 - v2.1.1.6 and 38.2.0, but still seems to work fine against 38.3.0. At some point I'll try updating to CCK2 - V2.1.1.7 (latest CCK2 release I think and rebuild with 38.3.x), but so far so good.

I am only setting the home page and inserting our proxy certificate.

I put cck2.cfg at /Firefox.app/Contents/Resources
I put autoconfig.js at Firefox.app/Contents/Resources/defaults/pref
I put cck2 distribution bundle at /Firefox.app/Contents/Resources/distribution

Is there something you think I am missing? This was built with CCK2 2.1.1.7.

I am such dumb and put the bundle at /Firefox.app/Contents/Resources/distribution not /Firefox.app/Contents/Resources/distribution/bundles

Looks like this Spring will be a good time to put Firefox ESR to rest.

https://t.co/uEAPSADiTk

Don't know if I'm too late to the Firefox party, but today I tried to install our custom distribution using cck2, but when finish and at the autoconfig.zip file, when I unzip it it only has the following folders:

As you can see, I have no distribution folder. I've tried to follow the initial instructions from the Amsys blog here and the addendum blog here, so I'm not sure why I don't have this folder.

Any ideas?

Apparently this is a known thing - Since Firefox 40 it appears the distribution bundles are gone. Got these links from Kaply support in just a few minutes after posting a ticket.

https://mike.kaply.com/2015/05/19/distributionbundles-directory-gone-in-firefox-40/
https://mike.kaply.com/2015/06/16/cck2-2-1-is-officially-available/

Thought I'd respond here with a screen shot of how the new CCK2 deploys now that dist. bundles are gone.

Tested with Firefox 43.0.3

From the autoconfig output, you will get a folder with the following folder/files:

browser (folder)
cck2 (folder)
cck2.cfg (file)
defaults (folder)

1.) Inside the browser folder, you will have a file named "override.ini". Move this file into /Applications/Firefox.app/Contents/Resources/browser
2.) Move the entire cck2 folder into /Applications/Firefox.app/Contents/Resources
3.) Move the cck2.cfg file into /Applications/Firefox.app/Contents/Resources
4.) Inside the defaults folder you will see another folder named pref and inside that folder you'll have a file named "autoconfig.js". Move this file into /Applications/Firefox.app/Contents/Resources/defaults/pref

You could most likely take all the files/folders listed above and drag and drop. I just wanted to make sure I wasn't overwriting anything that I hadn't looked at first. Screenshot below.

Thanks for posting this info - This is what I have been doing as well.

You could most likely take all the files/folders listed above and drag and drop

Bad idea - as Macs overwrite on a copy, you'd be erasing data. You need to do a 'merge' copy. The 'browser' directory and defaults/prefs directory have data in them you'd be erasing with a drag-n-drop copy.

In version 45 (using CCK2), a "browser" folder is no longer generated.

In version 45 (using CCK2), a "browser" folder is no longer generated.

Anyone here that got it to work with FF 50.1 and CCK 2.2.1?

I've been trying to chuck the files into the FF folder like @dilan suggested, but I keep getting errors saying that it's damaged when I try to start the application.

EDIT: Tried the ESR release instead, worked fine then. I should be using ESR anyway so disregard this post.

I was able to use CCK 2.2.2 to lock down extensions/add-ons from being added on 50.1.0 (non-ESR), however existing ones are still present and functional. Any ideas on how to handle those?