Virtualising Firefox? Don’t forget to disable Updates

If you are virtualising Mozilla Firefox, you should probably consider disabling the update functionality within the browser, to ensure consistency of the virtual package. There are several items that need to be configured or removed:

  • The automatic updates functionality
  • Help / Check for Updates… menu item
  • The Firefox check-box in the Option / Advanced / Updates dialog box

Fortunately doing so is fairly straight-forward:

Disable Automatic Updates

Updates are disabled in the Options / Advanced / Updates dialog box (under Windows), which you can do when running Firefox during the sequencing/capture process – untick the Firefox check box and change When updates to Firefox are found to Ask me what to do.

Alternatively set app.update.auto and app.update.enabled to false in about:config or directly in %APPDATA%\Mozilla\Firefox\Profiles\<profile>.default\prefs.js.

Leave Add-ons and Search Engines enabled as these are stored within the user profile and can be updated when running under application virtualisation.

Disable the Updates UI

Disabling the user interface elements to these update preferences and launch points is also important. To hide UI elements in Firefox, create UserChrome.css in %APPDATA%\Mozilla\Firefox\Profiles\<profile>.default\chrome. This file does not exist by default, although you will find an example file in the chrome folder. Create the file and add the following lines to hide the updates menu item and the Firefox check-box in the Updates dialog box.

/* remove the Check for Updates menu item */
#updateSeparator, #checkForUpdates { display: none !important; }
/* remove the Updates / Firefox checkbox */
#enableAppUpdate { display: none !important; }

If it is working correctly, you should see something like this (before and after):

FirefoxOptions

This method is not completely fool-proof (the modified files all exist in the user profile and are thus writeable) but it should stop users from unwittingly attempting to update Firefox and allow you to control when updates are deployed.

This entry was posted in Virtualisation and tagged , . Bookmark the permalink.
  • http://www.viridisit.com Nicke

    Great writing :)

    Nice touch with disabling the UI aswell :)

  • http://blog.stealthpuppy.com Aaron Parker

    Thanks Nicke

  • Vindictive

    How do you handle the plug-ins when sequencing? For instance Flashplayer, and Quicktime. Thanks.

    • http://blog.stealthpuppy.com Aaron Parker

      I can't say that I've gone as far as including those plug-ins in Firefox myself, but I don't see why you couldn't use DSC for both Flash or QuickTime

      • Joost

        Depending on your needs you could either use DSC, incorporate plugins inside your package or sequence Firefox so all users can install the plugins they like, as with a normal installation of Firefox. I chose for the last option. Plugins are stored in the user's .pkg file, including username and password.

  • Cenzo

    Vindictive, are you having an issue where the Adobe plugin does not exist on the build and is required when you launch Firefox in the bubble.? Thats my problem today.. DSC wont help here. Have you had any joy since..?
    I am thinking that with so many other Browser App plugin's theres not a slick answer to sequencing Firefox

  • Cenzo

    Vindictive, I found this link which helped me out. I took the files and virtualised them, All is happy. I guess if you know whats on your build and stick to it their is some control over what you can virtualise and DSC. Good Luck.
    http://www.varesano.net/blog/fabio/installing+fla

  • Vindictive

    I actually got Quicktime to work using DSC as Aaron recommend. As far as Flashplayer. When I sequenced Firefox I installed flashplayer along with it and it seems to work now. Thanks Aaron!

  • Vindictive

    Next is trying to sequence Flashplayer along with all the java runtime with IE. Any suggestions?

  • Vindictive

    Thanks Cenzo! Has anyone have any experience with using the locally installed IE along with flashplayer, and older versions of Java. What do you think about having all of the plugins virtualized and using the local installation of IE?

  • Marko

    How can you remove add-ons and search engines too?