Hi!

When i creating application for MSIs i set the command line to "Msiexec /i <MSIfile.msi> /q" but when i look in AppEnforce.log i see that SCCM add another /qn to the command line.

I suspect that it's the "Installation Program Visibility" property in the User Experience tab that does this.

So to my question, is this by design and should i omit /q to the command line and let SCCM add it after?

All my MSI applications looks like this.

Yes, you should omit the /q and let CM12 handle it.

Yes, this is by design.

Ok, thanks for the info.

Changing program visibility still adds /qn. What if I have to have a user input specific information to the installer? I have them launch the MSI from the App Catalog but it allways appends /qn? It has always been this way but then doesn't that mean the program visibility option actually does nothing? It should not force /qn and that's what that drop down should allow you to change.

Changing program visibility still adds /qn. What if I have to have a user input specific information to the installer? I have them launch the MSI from the App Catalog but it allways appends /qn? It has always been this way but then doesn't that mean the program visibility option actually does nothing? It should not force /qn and that's what that drop down should allow you to change.

For Installation Behavior, did you use "Install for User" or "Install for Device"?

This is just one more reason SCCM sucks! Altiris and LanDesk learned a long time ago to no mess with the command lines that people enter. Some day maybe the guys at Microsoft will learn this too. I will agree that 99% of the time this is desirable but not every time.