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

Deploying Firefox ESR in sccm with the /INI switch

  • 4 replies
  • 1 has this problem
  • 20 views
  • Last reply by Mike Kaply

more options

I've been deploying Firefox with the /S switch in SCCM (1802) for a while without issue, but I'm excited to use the new /INI= option, how ever I can't for the life of me to get it to work.

I've been trying: "Firefox Setup 60.0.2esr.exe" /INI=Install.ini "Firefox Setup 60.0.2esr.exe" /INI=%CD%\Install.ini "Firefox Setup 60.0.2esr.exe" /INI=%~dp0\Install.ini

Any help would be appreciated.

I've been deploying Firefox with the /S switch in SCCM (1802) for a while without issue, but I'm excited to use the new /INI= option, how ever I can't for the life of me to get it to work. I've been trying: "Firefox Setup 60.0.2esr.exe" /INI=Install.ini "Firefox Setup 60.0.2esr.exe" /INI=%CD%\Install.ini "Firefox Setup 60.0.2esr.exe" /INI=%~dp0\Install.ini Any help would be appreciated.

All Replies (4)

more options

The self-extractor should pass the parameters through. The issue here might be the path to the .ini not getting through correctly; what ends up on the command line really needs to be a fully resolved absolute path.

more options

I sure that is exactly what is happening, the problem is I will never know the absolute path because SCCM downloads it to C:\Windows\CCMcache\[**random folder name**].

Hence my problem. I realize I could write a script, but also it seems like if the ini file is in the same folder as the executable... then maybe I shouldn't have to give it an absolute path... many programs work this way. Also if an absolute path is absolutely needed... then I can't simply deploy with SCCM with out scripting.

more options

I'll open a bug and see if we can get this fixed.

more options

Side note - we're going to be allowing all these options via flags soon so you won't need the INI file.