/build/static/layout/Breadcrumb_cap_w.png

MSI/MST Install via MDT/SMS/SCCM

What is the best practice for installation for msi/mst package via MDT/SMS/SCCM.
1. Running the line directely
2. Via a Batch file
3. Via a vbs file.

Is it the same for other installation programme like: setup.exe?

I dodeployment since windows 3.11 for workgroup(with batch file) and was wondering if theres new way to install.

thank you

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 12 years ago
Red Belt
0
There is no best practice, as such. Your clients will probably have a preference and each will be different, of course!
Posted by: GrGrGr 12 years ago
Orange Belt
0
ORIGINAL: lepages

What is the best practice for installation for msi/mst package via MDT/SMS/SCCM.
1. Running the line directely
2. Via a Batch file
3. Via a vbs file.

Is it the same for other installation programme like: setup.exe?

I dodeployment since windows 3.11 for workgroup(with batch file) and was wondering if theres new way to install.

thank you

1. Supports return codes from .msi engine directly. You will know when your install failed.

Other options need custom scripting to handle return codes.

Remember that cmd (unless run via .vbs with a hidden windows parameter) is usually what most users will consider closing, you do not want that.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ