Re: ADMX files or go home.
1. Firefox is a cross-platform browser.
> Yes indeed but most corporations run Windows clients connected to an AD and it would be nice to have native controls from the actual software vendor
2. It is not a particularly onerous task to integrate policy files with / into your LDAP system, whatever schemata you use.
> It really is. First you have to know which files to target, as FF uses quite the mix to configure your settings. Then you have the massive issue of how do you actually target the correct FF user profile, since when you create a new one, it creates a randomised folder name to drop them it.
3. One gets the impression you are whingeing about something you do not have to pay for and likely were not going to use anyway.
> Well it wasn't me whinging but it's nice to have choice. Not everyone wants to use IE, Edge or Chrome but these are the browsers you are limited to right now if you want to manage via GPO. And trust me - I had to deliver FF into a high secure gov environment last year. It's a PITA
4. https://github.com/n8felton/Firefox-ADMX
> Yep not bad but in some environments such as the one above you have to be able to have full transparency of all software and add-ons. That's being able to trace right back to whom and where they originate from etc and that's not always easy.
Plus you run the risk of a new version of FF breaking third party tools (same as anything).
It was only recently that FF included the ability to utilise the Windows certificate store on a client machine. Before that, you had to package every certificate you wanted into FF (again, CCK2 becomes a godsend here) but then if you change one of them, you had to repackage it and then blow away users' FF profiles...so all their personalisations would be lost.
Ultimately, FF is simply not enterprise ready. Nor would I ever expect it to be.