Without knowing what and how it is being packaged it is hard to say. However, you can just run the MSI. Just remember when you setup the MSI distribution package do NOT use any command line switches for UI display (/qn). LANDesk handles this. Also here is a Macrovision doc on silent installations and uninstalls that may help.
My understaning (limited - LOL) is that the setup is basically checking for prereqs (proper MSI version etc...). So just try running the MSI. ALso if you tell us what you are trying to accomplish, there may be a better way to handle it without "heavy packaging". Are you just trying to turn off auto update?
have you tried taking the space out from between v/ and /qn? V passes the command to the MSI and when i have used this switch before it usually works if you do /s /V/qn
I am just trying to disable the Auto-Update for Flash. To do this, an mms.cfg file needs to be installed to C:\WINNT\System32\Macromed\Flash\.
The configuration files works and the only way i can think of rolling this out (apart from batch files, which id rather not use) is to package the install.
I will give this a go and let you know how it turns out. If it simply is a case of not having a space between /V and /qn then it would have been nice for /? to explain that... but i guess Macrovision expect you to know this automatically.
Have tested it as /S /V/QN instead of /S /V /QN and it is now working perfectly!
Just so everyone knows, when using the /v switch, it is used to pass parameters to the MSI.
It should usually be used with quotes so you can pass as many parameters as you want to the MSI file:
The quotes are good to use because you may need multiple parameters for example:
/v"/qn allusers=2 TRANFORMS=tranform.mst ServerName=MyServer"
this is our installation string in LANDesk Package Builder package without any questions to the user:
RUNATMIDDLE: "msiexec.exe", para="/i $WINTEMPDIR$\Flash\install_flash_player_active_x.msi /qb- Reboot=ReallySuppress"
I think you can copy your config file after installing too.
You can find some hints here:. Appdeploy - Flash Player 9.x
It sounds like an after the fact fix - What I call an oops. Sounds like the flash is already out there and they just want to update mms.cfg - but I could be wrong. What I was trying to get at in my post there are a lot of different ways just to update the file using "lighter" methods
BTW Appdeploy rocks!
Oops, you're right...
ZMan is right.
We already have Flash distributed to all of our users and we just needed to get the 1kb mms.cfg onto all the machines to prevent the updater from running every 30 days.
After testing SteveG's method i think we will go with that.
LOL - The reason I know - I oops a lot Glad everthing is working.