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

Comments

Please log in to comment

Answers

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
0
There is no best practice, as such. Your clients will probably have a preference and each will be different, of course!
Answered 02/07/2012 by: VBScab
Red Belt

Please log in to comment
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.
Answered 02/07/2012 by: GrGrGr
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity