Sorry it should be: How can we prevent that the settings in the GPO influence the Specialized version?

Usually when the workd Group Policies that is more related to Windows O/S itself. Are you sure it's not Windows related?

We are looked all the Windows GPO options ( Enterprise Envionment with 30000 Workstations), none of the Windows GPO options does solve this issue.

I would say to also contact a Windows forum group as well. In my understanding of Group Policies they are a O/S controlled feature done by Admin.

Portable Firefox is a 3rd party application and not created by or released by Mozilla. Portable Apps is only able to use the Mozilla trademarks for Firefox by virtue of their long relationship with Mozilla; they are grandfathered, so to speak.

There is a separate support forum for Portable Apps over here. http://portableapps.com/forums/support/firefox_portable

That said, Portable Firefox doesn't write to disk and doesn't interact with the Windows Operating System. I don't see how the Windows GPO could interact with Portable Firefox.

I think that best would be to use a policies.json file (or an autoconfig file) to deploy Firefox if you have to differentiate. Keep in mind that policies.json is disabled when GPO is active, so it is either use the same GPO for all Firefox versions or use a policies.json file for each Firefox installation.

• https://support.mozilla.org/en-US/kb/customizing-firefox-using-group-policy
• https://support.mozilla.org/en-US/kb/customizing-firefox-using-policiesjson
• https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig
• https://github.com/mozilla/policy-templates/blob/master/README.md

the-edmeister said

Portable Firefox is a 3rd party application and not created by or released by Mozilla.

The portable Firefox is a repackaged version of Mozilla Firefox from Mozilla with a custom launcher so it is not really a third-party build much like PaleMoon or WaterFox etc are actual third-party builds.