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.

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.

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

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