Was wondring what is the best way to deploy Microsoft SQL Managment Studio?

I have read and understood both here on the forum and on MSDN that it can be done several ways...

1. Either by creating a configuration file
2. By adding what features you want after setup.exe.......
3. By installing the product once and read the logfile which components are being installing. Then deploying the installation by adding the components(msi'S)
according to the log file.

The reason why im asking this is that i have tried to make a configuration file, and adding the feature by running setup.exe.... But it dosent work all the time.
Sometimes the installation just quits before its finished.

Have anyone experienced something like this and also what installation method do you think is the best?

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


My guess is that the install is ending prematurely because one or more pre-requisites aren't present. The most likely candidate is MSXML6 SP2.
Answered 01/24/2011 by: VBScab
Red Belt

Please log in to comment