Create setup that runs another MSI with parameters

[jadedesigns]

Hello,

This may seem ridiculous, but I have an MSI that was developed by someone else. I need to make it for a client that wants to deploy applications through Windows Group Policy. I need to create a new setup that basically runs the MSI with some parameters. I'm not allowed to recreate the original package or I'd simply do that.

The Installaware one should also run silently as they want it as transparent as possible. How would I accomplish this?

Thanks!

[MichaelNesmith]

Passing parameters to the MSI is a standard feature set of Group Policy. So you don't need to create a new wrapper for the setup. If you still want to create a wrapper, you can use the (Un)Install MSI Setup in your InstallAware setup, and run the foreign MSI file.

[DexterSinister]

Passing parameters to the MSI is a standard feature set of Group Policy.

Really ... ?

I'd love to know how ...

Can you provide a link to some documentation which details this ... ?

-dmm

[jadedesigns]

<<Passing parameters to the MSI is a standard feature set of Group Policy. So you don't need to create a new wrapper for the setup. If you still want to create a wrapper, you can use the (Un)Install MSI Setup in your InstallAware setup, and run the foreign MSI file.>>

GP will not let us use the parameters with this MSI. We've tried everything we can think of and it still doesn't work. Can you elaborate How would I create the wrapper please?

Thanks!

[MichaelNesmith]

Set the public MSI property CMDLINE to whichever value you wish to pass to the inner EXE file.

[DexterSinister]

Set the public MSI property CMDLINE to whichever value you wish to pass to the inner EXE file.

And just where would I create that command line ... ?

As far as I know, the only thing you can do with an MSI package from inside any of the MMC dialogs relating to software deployment is to specify the name of the MSI package and its location ...

To the best of my knowledge, the only way to provide that kind of input to an MSI package being deployed via Group Policy is to use transforms ... which are their own headache.

Perhaps you're thinking about deployment via SMS [or Tivoli or Altiris or some other tool of similar nature], but when using Group Policy and an MSI package, there's no way I know of to do what you're suggesting.

A kludge [and it would be a fairly horrid one] might be to use a ZAP file to provide this information ... but that would defeat the purpose of building a nice, clean MSI package ... and by doing your deployment with a ZAP file, you lose most [if not all] of the benefit(s) you would have gained by using Group Policy in the first place.

Again, if you'd be so kind as to point me to some documentation [preferably from Microsoft] on how to do what you've suggested, I'd be thrilled to see it ...

-dmm

[MichaelNesmith]

Isn't it a standard part of the Group Policy interface to set public MSI properties?

You can send me a screenshot of the deployment interface and I'll try to highlight the correct field.

[DexterSinister]

Isn't it a standard part of the Group Policy interface to set public MSI properties?

No, in fact, it is not ...

As I stated in my last message, the only way is to use transforms ... and the only additional control that an administrator has is order in which the transforms are applied.

At the risk of sounding cranky, I'd ask if you'd ever actually done any automated deployments using Group Policies ... but that would be rude.

I'll just ask that you not blithely answer serious questions when you don't really know what the correct answer is.

-dmm

[MichaelNesmith]

You do realize your post is already rude, right?

Send me a screenshot of the GP deployment interface, and I'll try to help you out.

If you're dissatisfied with the "seriousness" of the support you are getting at these forums, please order a support ticket. These community forums do not come with any service level guarantees, and while we do our best to help you out, this kind of hostility is not welcome (and will lead to immediate banning if continued).

[DexterSinister]

You do realize your post is already rude, right?

It was borderline, but it's your party ... so I'll stipulate to being overly cranky and we can both just leave it at that.

Send me a screenshot of the GP deployment interface, and I'll try to help you out.

While I appreciate your willingness to help, you still seem to have missed the point that what you're asking for doesn't exist in the way you think it does.

If you're dissatisfied with the "seriousness" of the support you are getting at these forums, please order a support ticket. These community forums do not come with any service level guarantees, and while we do our best to help you out, this kind of hostility is not welcome (and will lead to immediate banning if continued).

I'm not dissatisfied. I'm also not an InstallAware customer ...

I am, however, evaluating InstallAware and WiXAware as potential additions to the tools used by one of my clients to develop their installation packages.

My recommendation is not yet finalized ...

Thanks for your assistance,

-dmm