Hello folks...

May this post find you all well...

Issue: I am installing SQL Server Business Intelligence Developer Studio 2008 R2 via SCCM...I have created two batch files. One installs the other uninstalls. The batch files call two .ini files. Again, one .ini installs and the other uninstalls.

Wrappering is out of the question as the SQL 2008 R2 BIDS is almost 5.5 Gigs and to top it off is a bootstrap. My INIs work and so do the batch files that call them.

The install batch calls the install ini which in turn calls the setup.exe stub. Deploying and installing via a DP is no problem. I just hand them the folder with the batch and ini in it and there should be no problem.

However, what the heck do I do with the uninstall batch and ini? The uninstall batch calls the uninstall ini which in turn calls a setup file which is installed after the whole application is installed...(Hard coded path)

Any takers? How and what command do I give the deployment team if they wish to uninstall via SCCM?
0 Comments   [ + ] Show Comments

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.

Answers

0
I tend to use vb scripts, that way I can uninstall older versions, clean up any registry entries, perform silent install, clean up variables and exit all without the user's knowledge.
Answered 04/12/2011 by: riversidekid
Senior Yellow Belt

Please log in to comment
0
What do you give them to uninstall it? You give them the .INI and the batch file. As long as your batch file works from any folder location that's all they should need. They can even put those two files in the installation source folder and simply create an UNINSTALL program as part of their installation SCCM package...
Answered 04/24/2011 by: Lucid
Purple Belt

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