<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Ok, I get the idea of using the old folder during an upgrade (I
don't like it, because it breaks rule of 32bit in
%ProgramFiles(x86)%, but ok.</p>
<p>Here's what I'm doing to make sure I get a clean install (and am
using the proper folders).</p>
<p>1)Uninstall the current copy.<br>
2)Delete the C:\Program Files (x86)\Mozilla Firefox folder (or
C:\Program Files\Mozilla Firefox)<br>
3)Set MOZ_LEGACY_PROFILES=1<br>
4)Reinstall Firefox in the C:\Program Files (x86)\Mozilla Firefox
(most machines are now 64bit).<br>
5)Make the %ProgramFiles%\Mozilla Firefox\distribution folder<br>
6)Copy the policies.json to %ProgramFiles%\Mozilla
Firefox\distribution<br>
7)Start Firefox with the -setDefaultBrowser to set it as default
browser<br>
</p>
<p>What generally happens is that:</p>
<p>1)I get a new profile<br>
2)Even if I don't get a new profile, the old profile ignores at
least some of the policies.json settings<br>
2)Firefox sets itself as default browser about 80% of the time.</p>
<p>Even when I'm installing on a brand new install, the
policies.json settings fail at least 20% of the time.<br>
</p>
<p>So my automation fails completely.</p>
<p>What am I doing wrong?<br>
</p>
<div class="moz-signature">Thane K. Sherrington<br>
<br>
Computer Connection, Ltd. ...taking the mystery out of computers
since 1982.<br>
Winner of the 2012 Ian Spencer - Excellence in Business Award<br>
<b>Thanks for making us the Reader's Choice Best Computer Store in
2016, 2017, and 2018!</b><br>
95 College St., Antigonish, <br>
NS B2G 1X6<br>
902-863-3361 (phone)<br>
902-863-2580 (fax)<br>
<a class="moz-txt-link-abbreviated" href="mailto:thane@computerconnectionltd.com">thane@computerconnectionltd.com</a></div>
<div class="moz-cite-prefix">On 10/10/2019 7:26 p.m., Mike Kaply
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHueOzAS71ST6AjtPt0Ru3jnXg9eQvZZZAg8d6QVL=wKUK4Yyg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>That's correct, this is an old issue, and the profile per
channel situation made it more interesting.</div>
<div><br>
</div>
<div>So just summarize how things are going to be:</div>
<div><br>
</div>
<div>If you have Firefox installed (32 or 64), and you upgrade
to a different version using our install, it will overwrite
the existing install. This will prevent you from getting
separate profiles fro 32 and 64 bit (it was the only way to
solve this problem for most users.)</div>
<div><br>
</div>
<div>Note that we had always upgraded 32 to 64 in the same
directory in place. This new change is if you explicitly use
an installer and already have Firefox installed, it will
overwrite it in place (which is the logical thing to do).<br>
</div>
<div><br>
</div>
<div>separately, I have added a Windows GPO only policy to turn
off the profile per installation. It will be in the Firefox
and ESR that release on October 22.</div>
<div><br>
</div>
<div>Any other platforms should use the environment variable
(MOZ_LEGACY_PROFILES)<br>
</div>
<div><br>
</div>
<div><a
href="https://github.com/mozilla/policy-templates/blob/master/README.md#legacyprofiles"
moz-do-not-send="true">https://github.com/mozilla/policy-templates/blob/master/README.md#legacyprofiles</a></div>
<div><br>
</div>
<div>Mike<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 8, 2019 at 6:25 AM
Andrew C Aitchison <<a href="mailto:andrew@aitchison.me.uk"
moz-do-not-send="true">andrew@aitchison.me.uk</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
Wed, 2 Oct 2019, Klaus Hartnegg wrote:<br>
<br>
> Am 01.10.2019 um 23:00 schrieb Mike Kaply:<br>
>> We're also making a change so 64 bit Firefox installs
in the same<br>
>> directory as 32 bit (which is causing the new
profiles).<br>
><br>
> Oh, no!<br>
><br>
> You just learned the hard way that not following rules
causes problems.<br>
> Now instead of fixing the underlying bug you want to
break another rule.<br>
> Guess what? That will cause more problems.<br>
><br>
> Every deployment solution, every inventory tool, and
Windows itself<br>
> assumes everywhere that 64-bit programs are installed in
C:\Program Files.<br>
><br>
> How about this:<br>
> When Firefox is installed in its default directory, it
uses the default<br>
> name for the profile directory.<br>
> Only if somebody installs it in a non-standard directory,
it uses a<br>
> non-standard name for its profile.<br>
><br>
> Then all users who use defaults will get what they
expect, and those who<br>
> do not use defaults will get what they deserve: a
surprise.<br>
<br>
Mike will know better than me, but my recollection is that
this issue is <br>
not new but goes back to around ff56.<br>
<br>
At that point 64bit firefox became the default and many users
were <br>
upgraded automatically. Since this would have meant profiles
moving from<br>
%ProgramFiles(x86)% to %ProgramFiles% (have I got that the
right way <br>
around?) both versions were installed in the 32bit location,
so that the <br>
profiles did not move.<br>
<br>
Now that the chaos has been seen, they wish to scratch another
itch<br>
(requests to be able to run multiple versions of firefox) and
tackle<br>
two problems at once.<br>
<br>
-- <br>
Andrew C. Aitchison
Kendal, UK<br>
<a
href="mailto:andrew@aitchison.me.uk" target="_blank"
moz-do-not-send="true">andrew@aitchison.me.uk</a><br>
_______________________________________________<br>
Enterprise mailing list<br>
<a href="mailto:Enterprise@mozilla.org" target="_blank"
moz-do-not-send="true">Enterprise@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/enterprise"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mail.mozilla.org/listinfo/enterprise</a><br>
<br>
To unsubscribe from this list, please visit <a
href="https://mail.mozilla.org/listinfo/enterprise"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mail.mozilla.org/listinfo/enterprise</a>
or send an email to <a
href="mailto:enterprise-request@mozilla.org" target="_blank"
moz-do-not-send="true">enterprise-request@mozilla.org</a>
with a subject of "unsubscribe"<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Enterprise mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Enterprise@mozilla.org">Enterprise@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/enterprise">https://mail.mozilla.org/listinfo/enterprise</a>
To unsubscribe from this list, please visit <a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/enterprise">https://mail.mozilla.org/listinfo/enterprise</a> or send an email to <a class="moz-txt-link-abbreviated" href="mailto:enterprise-request@mozilla.org">enterprise-request@mozilla.org</a> with a subject of "unsubscribe"
</pre>
</blockquote>
</body>
</html>