MSI with a MST?

Content Authoring
1

(imported topic written by johnism91)

do you see anything worn with this …

wait {pathname of system folder}\msiexec.exe /i “{(pathname of client folder of current site) & “__Download\STD11.MSI” transforms= __Download\officestd.mst}” /qb-!

the MST is in the root with the MSI so I figured the path would be _ Download \Officestd.mst

but ti fials or say succesful and is actully not installed ???

Thanks for the help ,

John

2

(imported comment written by JackCoates91)

they should still be there in the __Download folder to check on… are you using the Software Distribution dashboard to generate this?

3

(imported comment written by johnism91)

I used the wiazrd …here is the full code .

download http://BLA.BLA.COM:52311/Uploads/949abba51619533ddc4601dc4d6f049d189a0889/MicrosoftOffice2003STD.tmp

continue if {(size of it = 233673937 AND sha1 of it = “949abba51619533ddc4601dc4d6f049d189a0889”) of file “MicrosoftOffice2003STD.tmp” of folder “__Download”}

extract MicrosoftOffice2003STD.tmp

wait {pathname of system folder}\msiexec.exe /i {pathname of client folder of current site} & “__Download\STD11.MSI” transforms= __Download\officestd.mst /qb-!

4

(imported comment written by JackCoates91)

ah, try this:

wait {pathname of system folder}\msiexec.exe /i {pathname of client folder of current site} & “__Download\STD11.MSI” transforms= & {pathname of client folder of current site} & __Download\officestd.mst /qb-!

Not sure about those quotes, but generally your problem is that CWD is {pathname of client folder of current site}, and it really should be {pathname of client folder of current site} & __Download. In the current Software Distribution site we handle this automatically by creating a .BAT file and cd’ing into the proper root directory.

5

(imported comment written by johnism91)

hmm somthing seesm to be off …msiexec.exe is displaing the “help” dialog box ?

6

(imported comment written by JackCoates91)

probably bad quoting – your besclient log file should show what the command resolved to.

7

(imported comment written by johnism91)

JackCoates

probably bad quoting – your besclient log file should show what the command resolved to.

how do I see these?

8

(imported comment written by johnism91)

this is what I got in Fixlet Debugger

STATUS: Running action…

Command failed (Relevance substitution failed) wait {(pathname of system folder)&"\msiexec.exe"} /i {(pathname of client folder of current site)& “__Download\STD11.MSI”} transforms= & {(pathname of client folder of current site) & “__Download\officestd.mst /qb-!”}

Command failed (This expression contained a character which is not allowed.) wait {(pathname of system folder)&"\msiexec.exe"} /i {(pathname of client folder of current site)& “__Download\STD11.MSI”} transforms= & {(pathname of client folder of current site) & “__Download\officestd.mst /qb-!”}

  • Result —

Evaluation failed!

9

(imported comment written by JackCoates91)

client logs are in C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Logs – and yes, the quotes are definitely off. Also it’s got to be escaped since it’s in the action… try this.

wait {{pathname of system folder}\msiexec.exe /i {{pathname of client folder of current site}& “__Download\STD11.MSI” /transforms=&{{pathname of client folder of current site}&"__Download\officestd.mst" /qb-!