Problems with profile management
We are currently rolling out a profile management solution based on Ivanti User Environment Manager. In order to configure file includes and excludes in the profile manag… (gụkwuo)
We are currently rolling out a profile management solution based on Ivanti User Environment Manager. In order to configure file includes and excludes in the profile management tool, we have to “standardize” the Firefox profile path in the filesystem. We have implemented a PowerShell script, which reads the currently used profile from %appdata%\Mozilla\Firefox\install.ini, renames the appropriate profile subfolder to “firefox.default-esr” and replaces the entries in installs.ini and profiles.ini.
The script seems to be reliable. However, for around 10% of the users, we are seeing issues when the user launches Firefox after the “firefox profile migration” happened. Firefox opens but none of the GUI controls is accessible. Firefox is completely unusable. See screenshot attached.
We do have workarounds to resolve this issue, such as completely wiping the %appdata%\Mozilla\Firefox folder and let Firefox re-build everything from scratch. But we are still trying to find the root cause the issue, because our customers have more than 100k clients, what will be a big impact and hard to handle for the helpdesk.
We are currently unable to reproduce the issue on test clients. Even copied Firefox profile folders form affected clients don’t show the issue on other clients.
Therefore we want to find out and ask for your help:
- Is there a supported way to “standardize” the filesystem folder name of the Mozilla Firefox (ESR) profile of a user? - What are the files within a Firefox profile that are required for the profile and the application itself to properly start? - Do you have any idea which files in a Firefox profile (in a corrupted state) could cause our issue?