On Fri, Feb 25, 2011 at 11:59 AM, Matthew W. Ross <[email protected]> wrote: > I know of only a few ways to deploy software that is packaged in an MSI: > > (1) Launching the MSI at the console. > (2) Using PSTool's PSExec to run it remotely from the command line. > (3) Using Group Policy.
Really, they all come down to "Group Policy or MSIEXEC". Whether you double-click an MSI file icon in Explorer, or type at the command line, or use a script, or link from a web page, or email a file attachment, all of those are ultimately just calling MSIEXEC with some combination of options. PSEXEC is just running MSIEXEC remotely; it's fundamentally no different. (Group Policy might actually result in MSIEXEC being invoked at some point, come to think of it, but there's other magic involved with checking to see if it's already installed, and handling upgrades, so it's fundamentally different from what us mere mortals do with MSIEXEC.) > (3) seems a bit heavy handed in this case What's the objection? You create a GPO, drop the MSI in it, computers get it at next reboot. Doesn't seem heavy-handed to me. Explain what you are trying to do. <-- This is important. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
