This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Azure Virtual Desktop

  • 2 fhreagra
  • 0 leis an bhfadhb seo
  • 4 views
  • Freagra is déanaí ó Mike Kaply

more options

Hello,

We have a client using Azure Virtual Desktops. Most of the users prefer to use Firefox. We are having an issue that anytime we update Firefox and reimage the virtual hosts. When the users login they get a new Firefox profile. We have to remote in and copy their old profile data to the new profile.

Is there a better way for us to handle Firefox and profiling in and Azure Virtual Desktop deployment?

Hello, We have a client using Azure Virtual Desktops. Most of the users prefer to use Firefox. We are having an issue that anytime we update Firefox and reimage the virtual hosts. When the users login they get a new Firefox profile. We have to remote in and copy their old profile data to the new profile. Is there a better way for us to handle Firefox and profiling in and Azure Virtual Desktop deployment?

All Replies (2)

more options

As you probably discovered by now, there are two .ini files that point Firefox to the latest profile:

  • %APPDATA%\Mozilla\Firefox\installs.ini
  • %APPDATA%\Mozilla\Firefox\profiles.ini
  • %APPDATA%\Mozilla\Firefox\Profiles\ (default location for profile folders)

Can you spare those files/folders when you reimage, or automate restoration of it?

Meanwhile, if it makes sense, should we flag this thread to move over to Firefox for Enterprise?

more options

You might try setting the LegacyProfiles policy

https://mozilla.github.io/policy-templates/#legacyprofiles

It sounds like the install directory of Firefox might be changing so it's creating a new profile.