搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

How can I define a default firefox profile name for multiple users so we can make Ivanti Environment Manager work?

  • 2 个回答
  • 1 人有此问题
  • 84 次查看
  • 最后回复者为 EkilErif

more options

Our company offers users the choice of Internet Explorer, Microsoft Edge or Mozilla Firefox (60.3 ESR) for web browsing. Our users make use of non-persistent Virtual Desktop Infrastructure which means that each day they get a new desktop. We use a product called Ivanti Environment Manager to retain personal settings across sessions so that things like bookmarks, etc. to persist across sessions.

This product stores settings within a Microsoft SQL database and recommendation from the vendor of that application is only to keep what is necessary across sessions. This is great, we have a list of files and folders within the Firefox profile that we want to roam and some we don't.

Unfortunately this product cannot support wildcards in a folder path so users Firefox profiles are proving to cause a few issues. For example, my profile is C:\Users\Richard\AppData\Roaming\Mozilla\Firefox\i99zcqad.default. What we are looking to do is to have everyone's profile called something like Firefox.default so that we can configure exclusions knowing the profile name will be consistent.

Is there a method anywhere within Firefox where we could do this? Our current solution is a messy one to use a powershell script to find the profile name, rename it and then update the profiles.ini file with the new name but my worry is that some of the underlying sqllite files may face issues as a result of this.

Any suggestions are highly appreciated?

Thanks, Richard

Our company offers users the choice of Internet Explorer, Microsoft Edge or Mozilla Firefox (60.3 ESR) for web browsing. Our users make use of non-persistent Virtual Desktop Infrastructure which means that each day they get a new desktop. We use a product called Ivanti Environment Manager to retain personal settings across sessions so that things like bookmarks, etc. to persist across sessions. This product stores settings within a Microsoft SQL database and recommendation from the vendor of that application is only to keep what is necessary across sessions. This is great, we have a list of files and folders within the Firefox profile that we want to roam and some we don't. Unfortunately this product cannot support wildcards in a folder path so users Firefox profiles are proving to cause a few issues. For example, my profile is C:\Users\Richard\AppData\Roaming\Mozilla\Firefox\i99zcqad.default. What we are looking to do is to have everyone's profile called something like Firefox.default so that we can configure exclusions knowing the profile name will be consistent. Is there a method anywhere within Firefox where we could do this? Our current solution is a messy one to use a powershell script to find the profile name, rename it and then update the profiles.ini file with the new name but my worry is that some of the underlying sqllite files may face issues as a result of this. Any suggestions are highly appreciated? Thanks, Richard

由Roland Tanglao于修改

被采纳的解决方案

Your modification of the profile path should have no adverse effects.

Another option (for a new user) is to use the command:

firefox -CreateProfile "JoelUser c:\internet\joelusers-moz-profile"

And then when you subsequently start Firefox, it will use that profile.

See:

https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#-CreateProfile_.22profile_name_profile_dir.22

定位到答案原位置 👍 2

所有回复 (2)

more options

选择的解决方案

Your modification of the profile path should have no adverse effects.

Another option (for a new user) is to use the command:

firefox -CreateProfile "JoelUser c:\internet\joelusers-moz-profile"

And then when you subsequently start Firefox, it will use that profile.

See:

https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#-CreateProfile_.22profile_name_profile_dir.22

more options

Thanks Mike.

I will add a configuration into my environment to use -createprofile for new users and then use the path modification for existing users. Should cover both scenarios off there.