Kukhonjiswa imibuzo ethegiwe: Veza yonke imibuzo
  • Okugcinwe kunqolobane

Updated Firefox to version 70, report still shows versions 69 and older installed

We're running reports from our Software deployment tools and after pushing update 70 on Windows 7 machines, version 69.x of Firefox is still reporting as being installed.… (funda kabanzi)

We're running reports from our Software deployment tools and after pushing update 70 on Windows 7 machines, version 69.x of Firefox is still reporting as being installed. When we push an uninstall task for version 69.x, it removes all bookmarks and passwords for users on the PC. Windows 10 does not appear to have this same issue. We believe it may be because version 70 is forcing x64 install and we had x86 69.x installed previously.

Asked by DCarney 1 unyaka odlule

Last reply by Mike Kaply 1 unyaka odlule

  • Okugcinwe kunqolobane

Unable to use client authentication certificates from Keychain or Windows user store.

We use user certificates as a second authentication factor, these are stored in the My Certificates (Key Chain) on OSX and under Windows Personal Certificates on Windows… (funda kabanzi)

We use user certificates as a second authentication factor, these are stored in the My Certificates (Key Chain) on OSX and under Windows Personal Certificates on Windows. These certificates are pushed via MDM and are not exportable. We have configured the Firefox setting the key "about:config", "security.enterprise_roots.enabled" to TRUE, but this only works for "System" not User based.

Asked by paul.hoff 1 unyaka odlule

Last reply by cor-el 1 unyaka odlule

  • Okugcinwe kunqolobane

Profile can't be used in 'older version' of Firefox

Okay, the problem we experience is almost exactly like the one that's described here: https://support.mozilla.org/en-US/questions/1264949 , but in our case this happens o… (funda kabanzi)

Okay, the problem we experience is almost exactly like the one that's described here: https://support.mozilla.org/en-US/questions/1264949 , but in our case this happens on a Remote Desktop environment and we know why it happens.

So we have this Remote Desktop Environment for a client of ours. When a user signs in to their online workplace, he or she will be signed on to one of the RD servers. Their profiles are stored on a user profile disk (UPD), which connects to their session upon logon. (I think the same issue will happen when roaming profiles or folder redirection is used.) We use Ninite Pro to install 3rd party updates on all of our servers. Ninite will only update Firefox when it's not in use so I think this is the reason why the Firefox versions become out of sync between the servers. When a user uses Firefox on server 1, which has version 69.0.2 installed and gets signed on to the other server the next time they log on, where version 69.0.1 is installed, they receive the warning: "You've launched an older version of Firefox". The only option there is to exit or create a new profile. Since they use certificates for their medcial administration software, this is a huge inconvenience.

Using firefox.exe -allow-downgrade solves the problem for now, but I understand that's not the best solution.

I will disable the Ninite updates for now and update Firefox to the latest version when everybody signed off. I've also explained the situation to Ninite support and suggested an option to 'bind' servers to update when all servers are ready to update. I would like suggest Mozilla to loosen the version check a little. I mean, there can't be a huge difference between 0.0.1 right?

Thanks for reading!

Asked by Bryan 1 unyaka odlule

Last reply by Mike Kaply 1 unyaka odlule

  • Okugcinwe kunqolobane

Priority of Firefox definition file - autoconfig.js and prefs.js

I would like to know whether definitions in prefs.js supercedes those in autoconfig.cfg and autoconfig.js. Currently we have one Firefox profile and definitions of proxy… (funda kabanzi)

I would like to know whether definitions in prefs.js supercedes those in autoconfig.cfg and autoconfig.js. Currently we have one Firefox profile and definitions of proxy is in autoconfig.cfg. Now we are planning to deploy new Firefox profile that contains new proxy definitions. Customer requirement is to avoid modifying existing autoconfig definitions. I plan to copy existing firefox profile to the new profile, perform about:config to reflect new proxy definition and create new firefox shortcut to use new profile. Can I satisfy the customer requirement?

Asked by morimura-katsumi 1 unyaka odlule

Last reply by Dkiger 1 unyaka odlule

  • Okugcinwe kunqolobane

How can a school block students from using Firefox Private Network VPN?

I'm looking to block it via a corporate firewall, but I cannot find any list of IP networks or DNS names to block as the school uses BYOD for students (K-8). I do see tha… (funda kabanzi)

I'm looking to block it via a corporate firewall, but I cannot find any list of IP networks or DNS names to block as the school uses BYOD for students (K-8). I do see that it uses cloudflare for their DNS servers but blocking cloudflare is not an option (NOTE: I found this out by using dnsleaktest.com while using firefox in Private Network mode). Thanks in advance for your help.

Asked by GotSQL 1 unyaka odlule

Last reply by cor-el 1 unyaka odlule

  • Okugcinwe kunqolobane

Locking in Automatically install updates (recommended)

Would anyone care to share if it is possible to lock the pref "Automatically install updates (recommended)" option. I have found where I can lock in the check for update… (funda kabanzi)

Would anyone care to share if it is possible to lock the pref "Automatically install updates (recommended)" option. I have found where I can lock in the check for updates updates but specifically we are looking to take away the ability for our user to switch it from "Automatically install updates (recommended)" to "Check for updates but let you choose to install them" .

Asked by Dkiger 1 unyaka odlule

Last reply by cor-el 1 unyaka odlule