Trying to add our custom .MST for adobe reader, and I am able to add the .MST file into "Custom pre/post update installation scripts" this gets the file to download into the ccmcache directory on the client. I then in modify command line added TRANSFORMS=Reader.mst.
This successfully runs the correct install command line, however the install fails with 1624 which is a failure to apply a transform file. In troubleshooting I modified the package.xml file on my test client to change the command line from
<CommandLine>/MainFile=AcroRdrDC2000620034_en_US.exeÿ"/MainArg=/sALL /rs /MSI /qn /norestart ALLUSERS=1 EULA_ACCEPT=YES DISABLE_ARM_SERVICE=1 UPDATE_MODE=0"ÿ/AdditionalArg=TRANSFORMS=Reader.mst</CommandLine>
<CommandLine>/MainFile=AcroRdrDC2000620034_en_US.exeÿ"/MainArg=/sALL /rs /MSI /qn /norestart ALLUSERS=1 EULA_ACCEPT=YES DISABLE_ARM_SERVICE=1 UPDATE_MODE=0"ÿ/AdditionalArg=TRANSFORMS=c:\windows\ccmcache\2e\Reader.mst</CommandLine>
saved the file and retried the installation from software center, and it installed successfully with the transform file applied correctly.
From looking at the PatchMyPC-ScriptRunner.log file i can tell based around Argument #1 is: /MainFile=AcroRdrDC2000620034_en_US.exe that some logic already exists to tell script runner what directory it is in. If this can be extended for modified command line arguments to use the ccmcache directory that the install is running out of it will provide a massive amount of flexibility for admins particularly around the base installation functionality.