User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729) This is a feature request. I feel it would be tremendously convenient if the Mozilla/Firefox team implemented a command line switch for the main executable that would do the following when run with root/administrator privileges. -Download latest *.mar upgrade/update file from somewhere like http://releases.mozilla.org/pub/mozilla.org/<product>/releases/latest/update (doesn't exist currently) -Install *.mar file Making updates and upgrades scriptable would relieve a lot of headaches for persons with desktop support responsibilities in an environment where users on the network don't have administrative privileges to perform updates/upgrades through the gui. For more information regarding the manual steps for this process see https://wiki.mozilla.org/Software_Update:Manually_Installing_a_MAR_file Reproducible: Always Steps to Reproduce: 1. Install Firefox in a corporate environment on a mix of Windows XP, Vista, and 7 machines. Users in this environment do not have installation privileges. There is no group policy or Active Directory. 2. Try to keep all machine's Firefox installations up to date using a complex scripting process. Actual Results: The script won't run the same way across all platforms due to differences in security, UAC, and system policies. Expected Results: Firefox gets updated to most recent version. Well, it'd be handy to have a command line switch one could add to a startup script (run with administrative privledges). An example of this would be: "firefox -update -upgrade" Running said switches would silently run the program and update/upgrade the software by automatically downloading the updates from the mozilla server/mirrors.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Version: 3.6 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.