Software distribution

(imported topic written by jdamico102291)

Ok I am ready to throw this dam server through a wall!! I’m trying to deploy visio 2002 silently on the network. I have an admin point created. It works just fine when I run the .msi /qn through the run command a client computer. But when I create the fixlet through the software distribution wizard and I run it…it says everything is completed. But nothing happens at all on the client side. Any details would be appreciated before I have a heart attack!!

download http://bes.nycecorp.net:52311/Uploads/d4f05fa2ab39a4b320fb26cfa012a4090ae71f4e/bigC1.tmp

continue if { (size of it = 621750 and sha1 of it = “d4f05fa2ab39a4b320fb26cfa012a4090ae71f4e”) of file “bigC1.tmp” of folder “__Download”}

extract bigC1.tmp

wait “{pathname of system folder & “\msiexec”}” /i “{(pathname of client folder of current site) & “__Download\visio.msi”}” /qn /norestart

Action Script Execution Detail

Completed

download http://bes.nycecorp.net:52311/Uploads/d4f05fa2ab39a4b320fb26cfa012a4090ae71f4e/bigC1.tmp

Completed

continue if { (size of it = 621750 and sha1 of it = “d4f05fa2ab39a4b320fb26cfa012a4090ae71f4e”) of file “bigC1.tmp” of folder “__Download”}

Completed

extract bigC1.tmp

Completed

wait “{pathname of system folder & “\msiexec”}” /i “{(pathname of client folder of current site) & “__Download\visio.msi”}” /qn /norestart

(imported comment written by BenKus)

Hey jdamico,

I bet this MSI doesn’t work well using the SYSTEM account for some reason… You can try testing this using info at:

http://forum.bigfix.com/viewtopic.php?id=1098

If you can verify the problem, I think you can modify the MSI to work by adding a property “ALLUSERS=1”.

Ben

(imported comment written by dgibson91)

jdamico,

Have you tried checking the event log for errors, or checking the MSI log?

If adding ALLUSERS=1 to the command line doesn’t work, then try logging the installation:

wait “{pathname of system folder & “\msiexec”}” /i “{(pathname of client folder of current site) & “__Download\visio.msi”}” /qn /L c:\visio.log /norestart

Should give you a general idea of what is happening.

Also, if the problem is that it was installed under the system account using ALLUSERS=0 then you will need to uninstall it as the system account before installing it with ALLUSERS=1.

If this is the case, then uninstall it using :

wait “{pathname of system folder & “\msiexec”}” /X “{(pathname of client folder of current site) & “__Download\visio.msi”}” /qn /norestart

(imported comment written by jdamico102291)

Hey ben –

I followed “option 1” from the link you sent me. I ran a custom action that said “run cmd.exe” and it worked. I’m not too sure I understand what that proves though.

It’s wierd because when I take the switch /qn /nonrestart out of the equation, it works fine. It will launch the installation. That’s what is so confusing to me. I need it to launch silently though, so that doesn’t help me much.

(imported comment written by BenKus)

Hey jdamico,

If you can run the install successfully through cmd.exe that runs as the SYSTEM account, then it indicates it is not a SYSTEM account problem… Perhaps dgibson’s idea could help in this particular case?

Ben

(imported comment written by jdamico102291)

Ok. It is not a system account issue. I can run cmd.exe through the system account no problem. On a side note…I can run the installation without /qn through bigfix. Once I put the switch in…it doesn’t work. Any ideas?

(imported comment written by sthull)

Are you sure /norestart is a valid switch? We typically use:

msiexec /i package.msi /qn REBOOT=REALLYSUPPRESS

Regards,

Steve