Dell OMCI.MSI Deployment through Group Policy
Greetings!
I have been attempting to distribute the Dell OpenManage Client Instrumentation to our client PC's through Group Policy; however, in order to perform a "silent" install a few command-line switches need to be included as part of the package.
I can't seem to figure out how to add command-line switches to a package when I am creating it in Group Policy. I tried to use a .CMD file, but when adding it in GP, it doesn't like it...Is there a way to include the necessary command-line switches in GP? If so, how?? I also took a look at some other posts in the message board about modifying the .msi package with WinInstall LE. I have d/l'd this program and opened the package up with it, but don't really understand what I'm doing and haven't had any luck with it.
Your help would be appreciated.
Thank you,
Robert Spangler
I have been attempting to distribute the Dell OpenManage Client Instrumentation to our client PC's through Group Policy; however, in order to perform a "silent" install a few command-line switches need to be included as part of the package.
I can't seem to figure out how to add command-line switches to a package when I am creating it in Group Policy. I tried to use a .CMD file, but when adding it in GP, it doesn't like it...Is there a way to include the necessary command-line switches in GP? If so, how?? I also took a look at some other posts in the message board about modifying the .msi package with WinInstall LE. I have d/l'd this program and opened the package up with it, but don't really understand what I'm doing and haven't had any luck with it.
Your help would be appreciated.
Thank you,
Robert Spangler
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
AngelD
16 years ago
command-line switches are often used as public properties meaning, all characters in uppercases.
Create a transform and then add those or change existing public properties with appropriate values.
Example of one public property often used is the ALLUSERS property defining if the package will be installs as per-user or per-machine. However if you're deploying the package through Group Policy this property will automatically be set with a value of 1 (per-machine) or 2 (per-user) if you define the package under the machine or user group policy.
Create a transform and then add those or change existing public properties with appropriate values.
Example of one public property often used is the ALLUSERS property defining if the package will be installs as per-user or per-machine. However if you're deploying the package through Group Policy this property will automatically be set with a value of 1 (per-machine) or 2 (per-user) if you define the package under the machine or user group policy.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
