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
you should post in the SCCM forum, you'll have a better chance to have an answer.

sccm forum
Answered 04/11/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
kardock, my question relates more to batch file placement rather than deployment, don't you think?At the risk of duping, I will also post it there...Thanks...
Answered 04/11/2011 by: Repackman
Purple Belt

Please log in to comment
0
1) I do not recommend using batch files for deployment unless you develop a specific way to return an exit code of the setup through them. Plus - they're annoying. The user can just close your batch command for some odd-reason only he knows about.
2) What are you trying to call on uninstall? Are you having issues finding where the setup is located after installation?
Answered 04/11/2011 by: GrGrGr
Orange Belt

Please log in to comment
0
GrGrGr, I agree...I am not a big fan the batch files either...But in this case I have to resort to them...The user can close them...I don't care...It's only kicking off the setup after which the user can't do jack...
2) I have found the setup file after install...I am just trying to see what I would give to the SCCM team for an uninstall...I was thinking maybe a command line uninstall but that's a little messy...It has too many components for me to list every uninstall string...So I thought why not a batch file?
Answered 04/11/2011 by: Repackman
Purple Belt

Please log in to comment
0
Screw it...I am passing the ini properties through the command line...

Thanks all...
Answered 04/11/2011 by: Repackman
Purple Belt

Please log in to comment
0
ORIGINAL: Repackman

GrGrGr, I agree...I am not a big fan the batch files either...But in this case I have to resort to them...The user can close them...I don't care...It's only kicking off the setup after which the user can't do jack...
2) I have found the setup file after install...I am just trying to see what I would give to the SCCM team for an uninstall...I was thinking maybe a command line uninstall but that's a little messy...It has too many components for me to list every uninstall string...So I thought why not a batch file?



Why not use chained un-installation advertisements? "run another program first".

It's just the matter of getting all the product codes for the components.
Answered 04/11/2011 by: GrGrGr
Orange Belt

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