Форум поддержки Корпоративный Firefox

We're exploring the possibility of implementing a mass update for Firefox through backend management, leveraging PowerShell scripts or any applicable method that can streamline the update process for our users.

Additionally, we've encountered instances where users have installed Firefox via local profiles, posing challenges for centralized updates. I'd appreciate any insights or guidance on how we can address this issue effectively to ensure these installations align with our centralized management approach.

We are currently attempting to automate our Firefox update processes. Currently we use robocopy to push out new versions on release, but ideally we'd like to use the background updater instead. We are currently on 64-bit 119.0.1, on Windows 10 Pro 22H2. We'd prefer not to switch over to ESR if at all possible. I've already reactivated the AppAutoUpdate and BackgroundAppUpdate policies, and DisableAppUpdate is disabled, but I'm still being hit with a UAC Admin prompt when I try to launch Firefox. I tried to bypass it through the registry at [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers], with "C:\Program Files\Mozilla Firefox\firefox.exe" = "RUNASINVOKER", but that also doesn't seem to have done anything. Any and all assistance would be appreciated