1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
|
---
title: エンタープライズ環境におけるFirefoxのデプロイ(Firefox 60 ESR 以前)
slug: Mozilla/Firefox/Enterprise_deployment_before_60
tags:
- Firefox
- エンタープライズ
- デプロイ
- 管理者向け
translation_of: Mozilla/Firefox/Enterprise_deployment_before_60
---
<div>{{FirefoxSidebar}}</div>
<p>このページでは、Mozilla Firefox を Windows および macOS コンピュータ上でエンタープライズ設定で管理するプロセスを、最初から最後までドキュメント化しようとしています。 ご不明な点がございましたら、エンタープライズワーキンググループメーリングリスト（<a href="https://mail.mozilla.org/listinfo/enterprise">enterprise@mozilla.org</a>）にメールをお送りください。 さらに、<a href="https://mail.mozilla.org/listinfo/enterprise">リストに登録</a>し、進行中のディスカッションに参加してください。</p>
<div class="note"><strong>注</strong>：この記事では、Firefox 60 ESR 以前の Firefox のバージョンについて説明します。 Firefox 60以降でエンタープライズ環境用にデプロイするには、<a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Enterprise_deployment">エンタープライズ環境での Firefox のデプロイ</a>を参照してください。</div>
<h2 id="さまざまな_Firefox_を選択する">さまざまな Firefox を選択する</h2>
<h3 id="Rapid_Release_(RR)">Rapid Release (RR)</h3>
<p>Mozilla publishes a new version with incremented main version number, new features, and bug fixes every six weeks (and, as needed, additional security releases in between). On the day a major version is released, in most cases (see below for an exception) Mozilla stops providing bug fixes for the previous one.</p>
<p>For the planned dates for upcoming releases, see the column 'release date' in the <a href="https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates">Future branch dates</a> table in the Mozilla wiki.</p>
<h3 id="Extended_Support_Release_(ESR)">Extended Support Release (ESR)</h3>
<p>Every seventh major version of Firefox is declared an Extended Support Release. These versions get serious bugs fixed in minor versions, for 54 weeks (nine of the six-week release cycles). There is an overlap of 12 weeks (two release cycles) between two successive ESR releases, during which both ESR releases get bug fixes.</p>
<p>The major ESR releases so far have been versions 10, 17, 24, 31, 38, 45 and 52. This cadence will be proken according to information in Devember 2017, and <code>60</code> will be the next ESR</p>
<p>Many enterprises and other organizations with centrally-managed computing environments prefer to use the ESR rather than the RR versions, because then they need to test for compatibility only every 42 weeks instead of every 6 weeks. Also if there are any issues, they have 12 weeks additional time (the overlap between two ESR releases) to find a solution (in addition to the 6 weeks that they can get by testing the beta version).</p>
<p>Note that there can be undesired side effects if you switch from a RR version to an earlier ESR version, for example from version 26-RR back to 24.2-ESR, even if they were published on the same day. The reason for this is that often new features are built into the RR versions for test purposes before they are finished, but disabled by preference settings. Eventually Mozilla decides to toggle the feature on in a certain version. If you then downgrade to a previous version, all users keep their latest settings in their profile directories. Thus the option is now switched on, although the feature does not yet fully work in that version. If you want to switch from RR to ESR, you should do so when a new ESR release comes out.</p>
<h2 id="インストール">インストール</h2>
<ol>
<li>Get the full, redistributable installer from<br>
<a href="http://www.mozilla.org/firefox/all/">http://www.mozilla.org/firefox/all/</a> (RR)<br>
or<br>
<a href="https://www.mozilla.org/firefox/organizations/all.html">https://www.mozilla.org/firefox/organizations/all.html</a> (ESR)<br>
rather than the "stub" or "downloader" that you get by clicking the "Download" button.</li>
<li>Install using the software distribution method of your choice.<br>
The command line option for a silent install is <code>-ms</code>. </li>
<li>Optionally you can specify an INI file, for example to disable the placement of shortcuts and the installation of the MaintenanceService; see <a href="https://wiki.mozilla.org/Installer:Command_Line_Arguments">Installer Command Line Arguments</a>.</li>
</ol>
<h2 id="構成・設定">構成・設定</h2>
<ol>
<li>Find the Firefox <strong>program directory</strong> where the Firefox executable is located.<br>
For example:
<ul>
<li>on <strong>Windows</strong> this is typically either:
<ul>
<li><code>C:\Program Files\Mozilla Firefox </code></li>
<li><strong>or</strong> <code>C:\Program Files (x86)\Mozilla Firefox</code></li>
</ul>
</li>
<li>on <strong>macOS</strong> it is typically:
<ul>
<li><code>/Applications/Firefox.app/Contents/MacOS</code></li>
</ul>
</li>
</ul>
If you are specifying a configuration INI file and have set <strong>InstallDirectoryName</strong> or <strong>InstallDirectoryPath</strong>, then use that path.<br>
Subfolders mentioned below are relative to this program directory.</li>
<li>Create a JavaScript file that instructs to use a administrative <strong>config file</strong> at startup.<br>
For best results, the filename should be early in the alphabet, for example; <strong><code style="white-space: nowrap;">00_admin-prefs.js</code></strong><br>
By convention this file is named <strong><code>autoconfig.js</code></strong>, but other filenames will work.<br>
This file should be put inside: <small>(see <a href="#Changes_Over_Time">Changes Over Time</a>)</small>
<ul>
<li>on <strong>Windows</strong>:
<ul>
<li><code>defaults\pref</code></li>
</ul>
</li>
<li>on <strong>Mac</strong>:
<ul>
<li><code>Firefox.app/Contents/Resources/defaults/pref</code></li>
</ul>
</li>
<li>on <strong>Linux</strong>:
<ol>
<li>Formerly:
<ul>
<li><code>defaults/pref</code><br>
<small>(Still working in Firefox 60.0a1)</small></li>
</ul>
</li>
<li>Presently:
<ul>
<li><code>browser/defaults/preferences</code></li>
</ul>
</li>
</ol>
</li>
</ul>
<p>This <code><strong>autoconfig.js</strong></code> file <strong>must</strong> set these preferences:</p>
<pre class="brush: js">// Any comment. You <strong>must</strong> start the file with a single-line comment!
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);</pre>
<div class="warning">
<p>The first line of the <code><strong>autoconfig.js</strong></code> and <code><strong>mozilla.cfg</strong></code> is ignored. The line shouldn't contain any configuration, nor multiline comment (<code>/*...*/</code>) without closing "<code>*/</code>".</p>
</div>
</li>
<li>Create a <code>.cfg</code> file in the Firefox program directory. By convention, <strong><code>mozilla.cfg</code></strong><code>,</code> but it can be any file name really. It just <strong>has to match</strong> what is specified in <strong><code>general.config.filename</code></strong> preference above. <strong>Skip or comment out the first line</strong>, then start setting your preferences. To learn what preferences to set, go to about:config on a copy of Firefox that you have configured correctly and look for preferences that are "user set", or see the example below. Any preference that appears in about:config (and a few that don't) can be set using one of the following functions:
<dl>
<dt><strong>pref </strong></dt>
<dd>sets the preference as if a user had set it, every time you start the browser. So users can make changes, but they will be erased on restart. If you set a particular preference this way, it shows up in about:config as "user set". </dd>
<dt><strong>defaultPref</strong></dt>
<dd>is used to alter the default value, though users can set it normally and their changes will be saved between sessions. If preferences are reset to default through the GUI or some other method, this is what they will go back to. Appears in about:config as "default". </dd>
<dt><strong>lockPref</strong></dt>
<dd>is used to lock preferences so they cannot be changed through the GUI or about:config. In many cases the GUI will change to reflect this, graying out or removing options. Appears in about:config as "locked". <span class="author-g-fer323ku83ypu55t">Some config items require <strong>lockPref</strong> to be set, such as <strong>app.update.enabled</strong>. It will not work if it set with just <strong>pref</strong>.</span></dd>
<dt><span class="author-g-fer323ku83ypu55t">clearPref</span></dt>
<dd><span class="author-g-fer323ku83ypu55t">can be used to "blank" certain preferences. This can be useful e.g. to disable functions that rely on comparing version numbers. </span></dd>
</dl>
<div class="warning">
<p>The first line of the <code><strong>autoconfig.js</strong></code> and <code><strong>mozilla.cfg</strong></code> is ignored. The line shouldn't contain any configuration, nor multiline comment (<code>/*...*/</code>) without closing "<code>*/</code>".</p>
</div>
</li>
</ol>
<p>See <a href="http://mike.kaply.com/2012/03/16/customizing-firefox-autoconfig-files/">Customizing Firefox autoconfig files</a> and <a href="http://mike.kaply.com/2012/03/20/customizing-firefox-autoconfig-files-continued/">Customizing Firefox autoconfig files continued</a> for more detail. For fancier stuff like disabling UI elements, you may want to use the <a href="http://mike.kaply.com/cck2/">CCK2</a> extension.</p>
<h3 id="Example_configuration_file">Example configuration file</h3>
<p>You may see references to "complex preferences" that need to be specified in a different way; the default homepage is one, as in the example below. For more info on individual preferences, search the <a href="http://kb.mozillazine.org/Knowledge_Base">Knowledgebase</a>.</p>
<pre class="brush: js">// Any comment. You <strong>must</strong> start the file with a comment!
<span class="brush: js">// Disable updater
lockPref("app.update.enabled", false);
// make absolutely sure it is really off
lockPref("app.update.auto", false);
lockPref("app.update.mode", 0);
lockPref("app.update.service.enabled", false);
// Disable Add-ons compatibility checking
clearPref("extensions.lastAppVersion");
// Don't show 'know your rights' on first run
pref("browser.rights.3.shown", true);
// Don't show WhatsNew on first run after every update
pref("browser.startup.homepage_override.mstone","ignore");
// Set default homepage - users can change
// Requires a complex preference
</span>defaultPref("browser.startup.homepage","data:text/plain,browser.startup.homepage=http://home.example.com");
<span class="brush: js">
// Disable the internal PDF viewer
pref("pdfjs.disabled", true);
// Disable the flash to javascript converter
pref("shumway.disabled", true);
// Don't ask to install the Flash plugin
pref("plugins.notifyMissingFlash", false);
//Disable plugin checking
lockPref("plugins.hide_infobar_for_outdated_plugin", true);
clearPref("plugins.update.url");
// Disable health reporter
lockPref("datareporting.healthreport.service.enabled", false);
// Disable all data upload (Telemetry and FHR)
lockPref("</span>datareporting.policy.dataSubmissionEnabled<span class="brush: js">", false);
// Disable crash reporter
lockPref("toolkit.crashreporter.enabled", false);
Components.classes["@mozilla.org/toolkit/crash-reporter;1"].getService(Components.interfaces.nsICrashReporter).submitReports = false;</span><em> </em>
</pre>
<h2 id="拡張機能のパッケージング">拡張機能のパッケージング</h2>
<ol>
<li>Install the extension on a test machine. Look in <code>about:support</code> under Extensions to find the GUID. This is absent in: FF 52.5.1 ESR</li>
<li>Look in the <a href="https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data">Profile directory</a> (ex: <code>%APPDATA%\Mozilla\Firefox\Profiles</code> on Win7; to find it, click <strong>Show Folder</strong> in <code>about:support</code>), then under "extensions" for the add-on you want. Note whether it is a single .xpi file (basically a zip file) or extracted to a folder with multiple files.</li>
<li>Decide how you want to deploy it. The simplest method is to drop the .xpi or folder into the <strong>program directory</strong><code>/distribution/extensions</code>, but this only works for profiles created after the extension is installed. Also, if you manually update firefox by re-installing it, this directory will be deleted, so make sure you re-install the extensions as well. See <a href="http://mike.kaply.com/2012/02/09/integrating-add-ons-into-firefox/">Integrating add-ons into Firefox/</a> for alternative methods.</li>
</ol>
<p>Also keep in mind: <a href="http://mike.kaply.com/2013/05/03/add-on-scopes-redux/">Add-on scopes redux</a></p>
<h2 id="Changes_Over_Time">Changes Over Time</h2>
<h3 id="Changes_in_Directory_Structure">Changes in Directory Structure</h3>
<p>The directory structure within the program directory has changed twice. When you read descriptions that were written before version 21 came out, you must take these changes into account:</p>
<ul>
<li>In version 14 some of the pref settings stopped working when they were in a file in directory <code>defaults/pref</code>. The fix was to create a directory <code>defaults/preferences</code> and put them there.</li>
<li>In version 21 the new directory named <code>browser</code> was created. The file <code>override.ini</code> and the directories <code>defaults/preferences</code>, <code>defaults/profile</code>, <code>extensions</code>, <code>plugins</code>, and <code>searchplugins</code> were moved there. Plug-ins in the directory <code>plugins</code> can be reactivated by setting the preference <code>plugins.load_appdir_plugins</code> to <strong>true</strong>.</li>
</ul>
<p>Custom settings in <code>defaults/pref</code> that worked in a version of Firefox before 21 may fail in a current or future version. If this happens, copy or move your customized files into the corresponding directories in <code>browser/defaults/preferences</code> and redeploy.</p>
<h3 id="Mac_Directory_Change">Mac Directory Change</h3>
<p>Due to Apple's stricter approach to software signing, as of about version 35 or so configuration files should now be placed relative to <code>/Applications/Firefox.app/Contents/Resources </code>(so <code>mozilla.cfg</code> should go there, and <code>autoconfig.js </code>under <code>/Applications/Firefox.app/Contents/Resources/defaults/pref</code>.)</p>
<h3 id="Changes_in_ESR_24_and_newer_with_Adobe_PDF_Files">Changes in ESR 24 and newer with Adobe PDF Files</h3>
<p>Firefox RR 19.x changed the default viewer for Adobe PDF files to use the internal Firefox viewer. This change is now in the ESR version as of 24.x, and the setting (on Windows) is changed to use the internal Firefox viewer when upgrading from 17.x, <em>even if an external viewer had already been configured</em>. The name of the Content Type is also changed from <strong>Adobe Acrobat Document</strong> to <strong>Portable Document Format (PDF)</strong>, which makes it difficult to locate via the Tools, Options, Applications tab. To disable this, set <code>pdfjs.disabled</code> to true as in the example file above.</p>
|
