[Mozilla Enterprise] Stop Firefox from creating a new profile on upgrade

[Andrew C Aitchison]

On Wed, 2 Oct 2019, Klaus Hartnegg wrote:

> Am 01.10.2019 um 23:00 schrieb Mike Kaply:
>> We're also making a change so 64 bit Firefox installs in the same
>> directory as 32 bit (which is causing the new profiles).
>
> Oh, no!
>
> You just learned the hard way that not following rules causes problems.
> Now instead of fixing the underlying bug you want to break another rule.
> Guess what? That will cause more problems.
>
> Every deployment solution, every inventory tool, and Windows itself
> assumes everywhere that 64-bit programs are installed in C:\Program Files.
>
> How about this:
> When Firefox is installed in its default directory, it uses the default
> name for the profile directory.
> Only if somebody installs it in a non-standard directory, it uses a
> non-standard name for its profile.
>
> Then all users who use defaults will get what they expect, and those who
> do not use defaults will get what they deserve: a surprise.

Mike will know better than me, but my recollection is that this issue is 
not new but goes back to around ff56.

At that point 64bit firefox became the default and many users were 
upgraded automatically. Since this would have meant profiles moving from
%ProgramFiles(x86)% to %ProgramFiles% (have I got that the right way 
around?) both versions were installed in the 32bit location, so that the 
profiles did not move.

Now that the chaos has been seen, they wish to scratch another itch
(requests to be able to run multiple versions of firefox) and tackle
two problems at once.

-- 
Andrew C. Aitchison					Kendal, UK
 			andrew at aitchison.me.uk