<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-forward-container">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Hey,<br>
to block firefox or thunderbird updates for all users you have to
do the following:<br>
<br>
create two files with following data:<br>
<br>
1. settings.js:<br>
pref("general.config.obscure_value", 0);<br>
pref("general.config.filename", "mozilla.cfg");<br>
<br>
2. mozilla.cfg:<br>
//<br>
// Disable automatic updates<br>
lockPref("app.update.enabled", false);<br>
lockPref("app.update.auto", false);<br>
<br>
The "mozilla.cfg" file needs to be placed in the ff/tb root
directory ("c:\Program Files (x86)\Mozilla Firefox\) and the
"settings.js" file needs to be placed in:<br>
%FF/TB-Root%\defaults\pref\<br>
<br>
<br>
So to deploy these settings with wpkg you just have to add the 2
files to a directory on your server and add something like this to
your ff/tb package file:<br>
<install cmd='%COMSPEC% /c copy /y
"%SOFTWARE%\firefox\settings.js" "%FIREFOX-ROOT%\defaults\pref\"'
/><br>
<install cmd='%COMSPEC% /c copy /y
"%SOFTWARE%\firefox\mozilla.cfg" "%FIREFOX-ROOT%\"' /><br>
<br>
Hope this helps.<br>
<br>
PS: <br>
You can use the same settings files for both thunderbird and
firefox.<br>
<br>
Greetings,<br>
Nils<br>
<br>
<div class="moz-cite-prefix">Am 07.10.2015 um 09:57 schrieb Holger
Kröber:<br>
</div>
<blockquote cite="mid:5614D075.8050807@biom.uni-freiburg.de"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi,<br>
<br>
when a new version of firefox/thunderbird (ff/tb) is released,
the users will be notified<br>
very soon. Often there is not enough time to test and deploy the
new version before the<br>
users get the update notification. Since most users don´t have
admin rights, this results in help desk calls.<br>
How do you manage this in your environment? Do you use WPGK to
copy a preconfigured<br>
user.js or do you inject the settings directly into the
prefs.js? Or do you use Group Policy Preferences?<br>
I guess WPKG is designed for running in the security context of
the computer (at startup), but in this case the user context
would be preferable.<br>
I would like to do the following:<br>
<ul>
<li>running wpkg at logon (not startup)</li>
<li>pick the correct path to the ff/tb profile folder<br>
how? there might be one ore more profiles...maybe with a
script: for each subfolder in rootfolder do...or by reading
the profiles.ini...</li>
<li>disable auto updates via user.js or prefs.js (but only for
non-admin users)<br>
</li>
<li>be happy ;)</li>
</ul>
<p>Regards,<br>
Holger<br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">-------------------------------------------------------------------------
SSLrack - get your cheap cheap SSL certificates (standard, wildcard, EV)
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.sslrack.com/">http://www.sslrack.com/</a>
-------------------------------------------------------------------------
wpkg-users mailing list archives >> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.wpkg.org/pipermail/wpkg-users/">http://lists.wpkg.org/pipermail/wpkg-users/</a>
_______________________________________________
wpkg-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wpkg-users@lists.wpkg.org">wpkg-users@lists.wpkg.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.wpkg.org/mailman/listinfo/wpkg-users">https://lists.wpkg.org/mailman/listinfo/wpkg-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
IT-Support - Fachbereich 09 Kulturgeschichte und Kulturkunde
Universität Hamburg
Flügelbau West, R. 204
Edmund-Siemers-Allee 1
D-20146 Hamburg
Tel.: +49-40-42838-3024
Email: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:it.service.kultur@uni-hamburg.de">it.service.kultur@uni-hamburg.de</a></pre>
<br>
</div>
<br>
</body>
</html>