Unsubscribe
Le 30 mai 2019 14:00, [email protected] a écrit :
To unsubscribe via the web interface, visit
https://mail.mozilla.org/listinfo/enterprise
or, via email, send a message with a subject or body of 'unsubscribe'
to
[email protected]
Send Enterprise mailing list submissions to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Enterprise digest..."
Today's Topics:
1. Re: upcoming ESR 68 / Impact of "Dedicated profiles per
Firefox installation" (Dave Townsend)
2. Re: upcoming ESR 68 / Impact of "Dedicated profiles per
Firefox installation" (wolf)
3. Re: upcoming ESR 68 / Impact of "Dedicated profiles per
Firefox installation" (Dave Townsend)
4. Re: upcoming ESR 68 / Impact of "Dedicated profiles per
Firefox installation" (James Pearson)
----------------------------------------------------------------------
Message: 1
Date: Wed, 29 May 2019 12:15:37 -0700
From: Dave Townsend <[email protected]>
To: [email protected]
Subject: Re: [Mozilla Enterprise] upcoming ESR 68 / Impact of
"Dedicated profiles per Firefox installation"
Message-ID:
<CAPMxTNpo-sNGL2Uun3nPmY1vGAd==cbus9mk0oaijmkzqbu...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
(sorry if this doesn't thread right, I only just joined this list)
Regarding how the dedicated profiles per install feature works, there is
currently no difference between how it works on normal Firefox builds and
ESR.
New versions of Firefox are not new installations. The installation is
defined by the installation directory.
As long as you are upgrading the Firefox version by putting the new version
into the same directory that the old version was in then users would
continue to use the same profile. We are currently seeing an edge case
where that is breaking right now on Windows but I'm expecting to have that
fixed before Firefox 68 ships.
There is currently no policy setting to disable this feature, there is
currently an environment variable that can be set (though it's targeted at
a different use case right now, so if important I'd like to use a different
name for it) but it applies to any version and channel of Firefox.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.mozilla.org/pipermail/enterprise/attachments/20190529/98f7b297/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 29 May 2019 21:54:23 +0000
From: "wolf" <[email protected]>
To: "Dave Townsend"
<[email protected]>,[email protected]<[email protected]>
Subject: Re: [Mozilla Enterprise] upcoming ESR 68 / Impact of
"Dedicated profiles per Firefox installation"
Message-ID: <kcis.A8D4D34471DB46E8B77ADB8022313D20@groupware>
Content-Type: text/plain; charset="utf-8"
thanks for your answer.
As I metioned before,
"We deploy firefox on windows clients by removing/purgings old versions und
redeploy firefox by choosing x86/x64 / language / Version (esr or standard, at
the moment 60.7.0 or 67.0)"
In more detail:
Usually the new firefox version is the in the same place, but upgrading from
66.0.5 to 67.0 led to a new
installs.ini which points to a new default profile (therefore users thoud they
lost their bookmarks)
So we mad an ugly workaround? after installing firefox in opsi-script patching
existing profiles:
...
??????? If ( $usededicatedprofilesperfirefoxinstallation$ = "false")
??????????????? Set $profile.ini.profile.0.path$ =
GetValueFromInifile($akt_profile_ini$,"Profile0","path","")
??????????????? if ( $profile.ini.profile.0.path$ = "" )
??????????????????????? Logwarning " do nothing "
??????????????? else???
??????????????????????? if NOT(FileExists($akt_profile_installs_ini$))
??????????????????????????????? Files_copy_installs_ini_template
??????????????????????? endif
??????????????????????? if ( $architecturesuffix$ = "" )
??????????????????????????????????????? ; patches 32 installs.ini part
??????????????????????????????????????? Patches_install.ini
$akt_profile_installs_ini$
??????????????????????????????????????? if
LineContaining_ExistsIn("InstallE7CF176E110C211B",$akt_profile_ini$)
???????????????????????????????????????????????
PatchTextFile_usededicatedprofilesperfirefoxinstallation $akt_profile_ini$
??????????????????????????????????????? endif
??????????????????????????????????????? Patches_profile.ini $akt_profile_ini$
??????????????????????? else
??????????????????????????????????????? ; patches 64 installs.ini part
??????????????????????????????????????? Patches_install64.ini
$akt_profile_installs_ini$
??????????????????????????????????????? if
LineContaining_ExistsIn("Install308046B0AF4A39CB",$akt_profile_ini$)
???????????????????????????????????????????????
PatchTextFile_usededicatedprofilesperfirefoxinstallation64 $akt_profile_ini$
??????????????????????????????????????? endif
??????????????????????????????????????? Patches_profile64.ini $akt_profile_ini$
??????????????????????? endif??????????????????????????????????
??????????????? endif
??????? endif
...
[PatchTextFile_usededicatedprofilesperfirefoxinstallation]
GoToTop
InsertLine "InstallE7CF176E110C211B"
[PatchTextFile_usededicatedprofilesperfirefoxinstallation64]
GoToTop
InsertLine "Install308046B0AF4A39CB"
[Files_copy_installs_ini_template]
copy "%SCRIPTPATH%\opsi\$architecturesuffix$\installs.ini" "$akt_profile_dir$"
???????????????????????
[Patches_install.ini]
;E7CF176E110C211B
set [InstallE7CF176E110C211B] Default=$profile.ini.profile.0.path$
[Patches_install64.ini]
;308046B0AF4A39CB
set [Install308046B0AF4A39CB] Default=$profile.ini.profile.0.path$
[Patches_profile64.ini]
set [Install308046B0AF4A39CB] Default=$profile.ini.profile.0.path$
set [Install308046B0AF4A39CB] Locked=1
set [Profile0] Default=$profile.ini.profile.0.path$
set [General] StartWithLastProfile=1
set [General] Version=2
[Patches_profile.ini]
set [InstallE7CF176E110C211B] Default=$profile.ini.profile.0.path$
set [InstallE7CF176E110C211B] Locked=1
set [Profile0] Default=$profile.ini.profile.0.path$
set [General] StartWithLastProfile=1
...
With this workaround firefox 67.0 dont point to the wrong default profile but a
better solution would appreciated.
kind regards,
Bardo Wolf
--
opsi - Open PC-Server-Integration
Wondering who's using opsi? Have a look at the opsi map:
http://opsi.org/opsi-map/. <http://opsi.org/opsi-map/>
--
------------------------------------
Bardo Wolf
eMail: [email protected] <mailto:[email protected]>
uib gmbh
Firmensitz / Anschrift:
Bonifaziusplatz 1B
55118 Mainz
internet: www.uib.de <http://www.uib.de>
Gesch?ftsf?hrer: dr. detlef oertel + erol ?l?kmen
Handelsregister: Amtsgericht Mainz HRB 6942
-----Urspr?ngliche Nachricht-----
Von: Dave Townsend?<[email protected]>
Gesendet: Mittwoch 29 Mai 2019 21:16
An: [email protected]
Betreff: Re: [Mozilla Enterprise] upcoming ESR 68 / Impact of "Dedicated
profiles per Firefox installation"
(sorry if this doesn't thread right, I only just joined this list)
Regarding how the dedicated profiles per install feature works, there is
currently no difference between how it works on normal Firefox builds and ESR.
New versions of Firefox are not new installations. The installation is defined
by the installation directory.
As long as you are upgrading the Firefox version by putting the new version
into the same directory that the old version was in then users would continue
to use the same profile. We are currently seeing an edge case where that is
breaking right now on Windows but I'm expecting to have that fixed before
Firefox 68 ships.
There is currently no policy setting to disable this feature, there is
currently an environment variable that can be set (though it's targeted at a
different use case right now, so if important I'd like to use a different name
for it) but it applies to any version and channel of Firefox.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.mozilla.org/pipermail/enterprise/attachments/20190529/edb7f1ac/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 29 May 2019 19:34:41 -0700
From: Dave Townsend <[email protected]>
To: wolf <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [Mozilla Enterprise] upcoming ESR 68 / Impact of
"Dedicated profiles per Firefox installation"
Message-ID:
<capmxtnrwopgiercr5pvgetjpez5hikiv8z0tfe2pkibotom...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
It's odd that Firefox 67 installed into a different location from Firefox
66.0.5. I don't know why that would have happened. As far as I know there
aren't any installer changes that would have caused that, it may be a bug.
If that were fixed you shouldn't need your patch.
On Wed, May 29, 2019 at 2:54 PM wolf <[email protected]> wrote:
> thanks for your answer.
>
>
> As I metioned before,
>
>
> "We deploy firefox on windows clients by removing/purgings old versions
> und redeploy firefox by choosing x86/x64 / language / Version (esr or
> standard, at the moment 60.7.0 or 67.0)"
>
>
> In more detail:
>
>
> Usually the new firefox version is the in the same place, but upgrading
> from 66.0.5 to 67.0 led to a new
>
>
> installs.ini which points to a new default profile (therefore users thoud
> they lost their bookmarks)
>
>
>
>
> So we mad an ugly workaround after installing firefox in opsi-script
> patching existing profiles:
>
> ...
>
> If ( $usededicatedprofilesperfirefoxinstallation$ = "false")
> Set $profile.ini.profile.0.path$ =
> GetValueFromInifile($akt_profile_ini$,"Profile0","path","")
> if ( $profile.ini.profile.0.path$ = "" )
> Logwarning " do nothing "
> else
> if NOT(FileExists($akt_profile_installs_ini$))
> Files_copy_installs_ini_template
> endif
> if ( $architecturesuffix$ = "" )
> ; patches 32 installs.ini part
> Patches_install.ini
> $akt_profile_installs_ini$
> if
> LineContaining_ExistsIn("InstallE7CF176E110C211B",$akt_profile_ini$)
>
> PatchTextFile_usededicatedprofilesperfirefoxinstallation $akt_profile_ini$
> endif
> Patches_profile.ini
> $akt_profile_ini$
> else
> ; patches 64 installs.ini part
> Patches_install64.ini
> $akt_profile_installs_ini$
> if
> LineContaining_ExistsIn("Install308046B0AF4A39CB",$akt_profile_ini$)
>
> PatchTextFile_usededicatedprofilesperfirefoxinstallation64 $akt_profile_ini$
> endif
> Patches_profile64.ini
> $akt_profile_ini$
> endif
> endif
> endif
>
> ...
>
>
> [PatchTextFile_usededicatedprofilesperfirefoxinstallation]
> GoToTop
> InsertLine "InstallE7CF176E110C211B"
>
> [PatchTextFile_usededicatedprofilesperfirefoxinstallation64]
> GoToTop
> InsertLine "Install308046B0AF4A39CB"
>
> [Files_copy_installs_ini_template]
> copy "%SCRIPTPATH%\opsi\$architecturesuffix$\installs.ini"
> "$akt_profile_dir$"
>
> [Patches_install.ini]
> ;E7CF176E110C211B
> set [InstallE7CF176E110C211B] Default=$profile.ini.profile.0.path$
>
> [Patches_install64.ini]
> ;308046B0AF4A39CB
> set [Install308046B0AF4A39CB] Default=$profile.ini.profile.0.path$
>
> [Patches_profile64.ini]
> set [Install308046B0AF4A39CB] Default=$profile.ini.profile.0.path$
> set [Install308046B0AF4A39CB] Locked=1
> set [Profile0] Default=$profile.ini.profile.0.path$
> set [General] StartWithLastProfile=1
> set [General] Version=2
>
> [Patches_profile.ini]
> set [InstallE7CF176E110C211B] Default=$profile.ini.profile.0.path$
> set [InstallE7CF176E110C211B] Locked=1
> set [Profile0] Default=$profile.ini.profile.0.path$
> set [General] StartWithLastProfile=1
>
>
> ...
>
>
> With this workaround firefox 67.0 dont point to the wrong default profile
> but a better solution would appreciated.
>
> kind regards,
>
> Bardo Wolf
>
>
> --
> opsi - Open PC-Server-Integration
>
> Wondering who's using opsi? Have a look at the opsi
> map:http://opsi.org/opsi-map/. <http://opsi.org/opsi-map/>
> --
> ------------------------------------
>
> Bardo Wolf
>
> eMail: [email protected]
>
> uib gmbh
>
> Firmensitz / Anschrift:
> Bonifaziusplatz 1B
> 55118 Mainz
>
> internet: www.uib.de
>
> Gesch?ftsf?hrer: dr. detlef oertel + erol ?l?kmen
> Handelsregister: Amtsgericht Mainz HRB 6942
>
>
>
>
> -----Urspr?ngliche Nachricht-----
> *Von:* Dave Townsend <[email protected]>
> *Gesendet:* Mittwoch 29 Mai 2019 21:16
> *An:* [email protected]
> *Betreff:* Re: [Mozilla Enterprise] upcoming ESR 68 / Impact of
> "Dedicated profiles per Firefox installation"
>
> (sorry if this doesn't thread right, I only just joined this list)
>
> Regarding how the dedicated profiles per install feature works, there is
> currently no difference between how it works on normal Firefox builds and
> ESR.
>
> New versions of Firefox are not new installations. The installation is
> defined by the installation directory.
>
> As long as you are upgrading the Firefox version by putting the new
> version into the same directory that the old version was in then users
> would continue to use the same profile. We are currently seeing an edge
> case where that is breaking right now on Windows but I'm expecting to have
> that fixed before Firefox 68 ships.
>
> There is currently no policy setting to disable this feature, there is
> currently an environment variable that can be set (though it's targeted at
> a different use case right now, so if important I'd like to use a different
> name for it) but it applies to any version and channel of Firefox.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.mozilla.org/pipermail/enterprise/attachments/20190529/b1f53744/attachment-0001.html>
------------------------------
Message: 4
Date: Thu, 30 May 2019 10:49:58 +0000
From: James Pearson <[email protected]>
To: Dave Townsend <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [Mozilla Enterprise] upcoming ESR 68 / Impact of
"Dedicated profiles per Firefox installation"
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Dave Townsend wrote:
>
> (sorry if this doesn't thread right, I only just joined this list)
>
> Regarding how the dedicated profiles per install feature works, there
> is currently no difference between how it works on normal Firefox
> builds and ESR.
>
> New versions of Firefox are not new installations. The installation
> is defined by the installation directory.
>
> As long as you are upgrading the Firefox version by putting the new
> version into the same directory that the old version was in then
> users would continue to use the same profile. We are currently seeing
> an edge case where that is breaking right now on Windows but I'm
> expecting to have that fixed before Firefox 68 ships.
>
> There is currently no policy setting to disable this feature, there
> is currently an environment variable that can be set (though it's
> targeted at a different use case right now, so if important I'd like
> to use a different name for it) but it applies to any version and
> channel of Firefox.
What is the environment variable and what does it need to be set to for
disabling dedicated profiles ?
Thanks
James Pearson
------------------------------
Subject: Digest Footer
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
[email protected] with a subject of "unsubscribe"
------------------------------
End of Enterprise Digest, Vol 95, Issue 19
******************************************
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
[email protected] with a subject of "unsubscribe"
