does firefox run on terminal server ms windows 2003 or 2008 or both
before i install firefox on terminalserver w2003 i would like to know if any one has expierienced any trouble doing so , or had any problems after installing firefox
== did not start at all
Additional System Details
- -Shockwave Flash 10.1 r53
- Adobe Shockwave for Director Netscape plug-in, version 11.5
- Office Authorization plug-in for NPAPI browsers
- The plug-in allows you to open and edit files using Microsoft Office applications
- RealPlayer(tm) LiveConnect-Enabled Plug-In
- RealJukebox Netscape Plugin
- RealPlayer(tm) HTML5VideoShim Plug-In
- Google Update
- User Agent: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b2) Gecko/20100720 Firefox/4.0b2 ( )
not an issue jet i very much would like to know if any one had any trouble in stalling the fox on terminal server
Have done this and it works fine. Only issue I encountered involved locking down the installation so that it would not prompt users about updates and extensions or allowing them to change critical settings. It did take me a bit of time to lock down the installation and I found that most of the sites discussing this have older information that does not work for the latest version of Firefox or is conflicting. For the most part the older sites do have most of the details needed but I found one critical piece missing.
I had to complete the following steps to lock down the update and a few other options on a terminal server installation of Firefox 3.6.9:
1. Create a file in “C:\Program Files\Mozilla Firefox\” titled mozilla.txt
2. Then edit the file adding the following lines to the newly created file and save it:
lockPref("privacy.sanitize.sanitizeOnShutdown", true); // Always clear private data when exiting
lockPref("privacy.sanitize.timeSpan", 0); // 0 = Clears everything, every time
- (The first line of "//" is essential and each line starts with "lockPref" Apologies for the formatting here as this is the only way it would allow me to post it.)
3. Next create a new file called localsettings.js and put it in either “C:\Program Files\Mozilla Firefox\greprefs” or “C:\Program Files\Mozilla Firefox\defaults\pref”. I created “C:\Program Files\Mozilla Firefox\greprefs\ localsettings.js”.
4. Add the following line to this file and save: pref("general.config.filename", "mozilla.cfg");
5. Now you must encode (byte shift 13) your Mozilla.txt file to create a Mozilla.cfg file. This new file will reside in the same directory “C:\Program Files\Mozilla Firefox\”. This file can be created online using the following link:
(Browse to the Mozilla.txt file, open, and then click the “Convert” button saving the new file to the “C:\Program Files\Mozilla Firefox\” directory)
6. That is it. To test your settings start up Firefox and load “about:config” then filter to any of the items you included in your Mozilla.txt file and it should show it’s status as locked. The entire line for this entry and any locked preferences will be italicized. If the entry is not then you know your preferences have not been loaded. See attached screenshot.
Notes: The file created during steps 3 & 4 is critical. For me nothing else worked. Many sites instructed me to modify the all.js file located in “C:\Program Files\Mozilla Firefox\greprefs” with the following lines:
This did not work for me. The first line is supposed to allow you to modify and use your Mozilla.txt file without having to encode it, just renaming it Mozilla.cfg. The second line you will recognize as what we added to the localsettings.js file.
You can set any preference found in the “about:config” using this method. I browsed though and found the ones I wanted to lock and did so. A fairly complete list of “about:config” entries with a description of their functions can be found here: http://kb.mozillazine.org/About:config_entries
This process took me about fours hours of trial and error with many false starts and a bit of conflicting information.
I hope this helps.
This all seems to work well with 5.0.1. The only possible exception is the "import settings" dialogue.
But that really is the least problematic in my scenario. Other values check out and seem to work for me.