I have quick question about the MSI. why do we need to make msi for sms 2003 ... being reading on the web .. that setup.exe, vbs, batch files will all work in SMS 2003. why do we need to convert them in MSI, other then custom install don't see any point... can anyone help me understanding this ? Thanks
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Answered 04/28/2006 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Short and sweet: MSI's are easily managed as each workstation's installation of Windows Installer runs MSI set ups and when it's time for the workstation to lose that piece of software it just runs (a cached copy) the MSI again, kind of in reverse, removing everything that was added by the original install (basically). Batches and legacy setups are not manageable by GPO or by SMS - sure you can push em' but when it comes time to pull em' that's a different story. The main driving reason everyone tries to go with MSIs is their manageability.
Answered 05/01/2006 by: fosteky
Purple Belt

Please log in to comment