Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Moving Profile Issue

  • 1 wotmołwa
  • 3 maja tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot the-edmeister

BigL
BigL
more options

Hi we have roaming profiles in our environment. Whenever a client installs firefox we need to move the profile to a local volume or else it will put the users roaming profile over its limit. I always do this by creating a new folder on the local volume > cut the contents of the profile from %appdata%/roaming and paste it to the new profile location > then i simply update the profile.ini with the new profile path. I never have a problem doing this, but with this one client I am experiencing after moving the profile to the local volume the next time firefox is launched it recreates a new profile folder on %appdata% and points the profile path to it.

My client did have mozilla installed on multiple machines so i uninstalled it from all machines, deleted all mozilla folders from every machine and started it from scratch, but I am still running into this issue when moving the profile

I am wondering if the users roaming profile is causing this issue and it perhaps needs to be recreated? I am trying to avoid that step.

Hi we have roaming profiles in our environment. Whenever a client installs firefox we need to move the profile to a local volume or else it will put the users roaming profile over its limit. I always do this by creating a new folder on the local volume > cut the contents of the profile from %appdata%/roaming and paste it to the new profile location > then i simply update the profile.ini with the new profile path. I never have a problem doing this, but with this one client I am experiencing after moving the profile to the local volume the next time firefox is launched it recreates a new profile folder on %appdata% and points the profile path to it. My client did have mozilla installed on multiple machines so i uninstalled it from all machines, deleted all mozilla folders from every machine and started it from scratch, but I am still running into this issue when moving the profile I am wondering if the users roaming profile is causing this issue and it perhaps needs to be recreated? I am trying to avoid that step.

Wšě wotmołwy (1)

the-edmeister
the-edmeister
  • Moderator
more options

This situation is really beyond the intent of this forum, which is for end-user support. https://support.mozilla.org/en-US/kb/where-go-developer-support

As far as Firefox automatically creating a new local disk Profile, how are you handling profiles.ini?

Firefox looks to the profiles.ini file upon launch and if Firefox can't 'find' the Default=1 Profile where it expects to find that Profile, Firefox will go ahead and create a new Profile in the default location.

IMO as someone who has worked extensively with "Profiles", but never with server based "roaming" Profiles, it seems that might be related to your problem.