I've found myself landed with SCCM and need to uninstall Acrobat Reader, everywhere there is advice about using the msiexec /qb /i {guid} format but no advice about how to successfully run the command. I have tried to run a package with no source files and simply entered the command into the program field and also I have put the command in a batch file, selected the file as the data source and also as the program, neither method has worked. What am I missing?
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
it's msiexec /x {productcode} /qb to uninstall
Answered 08/16/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
I'm no SCCM expert but I have built a script to automate adding MSIs to SCCM. In that script, the flow is:

- Create AD group
- Create package
- Create program (this is where you could put your MSIEXEC... command line)
- Assign Package to Distribution Point
- Create Collection
- Create Advertisement

The first stept isn't strictly necessary, as you can add machines to a collection directly. It does mean, though, that people who would be expected to populate software distribution groups (e.g. Service Desk personnel) won't need to be trained in using SCCM.

Have you followed the other steps?

BTW, there is a dedicated SCCM/SMS forum here on AppDeploy. A moderator may well move the thread there.
Answered 08/16/2010 by: VBScab
Red Belt

Please log in to comment
0
Thanks Timmsie, I made a typo there, too long a day.
VBScab, thanks for the response, the issue I have is not with an install using a package but with an uninstall where there is no package just a command line. What is the best way to run msiexec /x etc on the client machine? Thanks for the tip on the dedicated forum I'll move over there. Cheers.
Answered 08/16/2010 by: maxx8864
Yellow Belt

Please log in to comment
0
You do what Ian said, add the msiexec command to your program. I've not used SCCM but I would imagine it's very similar to sms2003.

Create an uninstall program and add the command line, it's as simple as that. Or am I missing something?
Answered 08/16/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
Yes, SCCM is SMS with bells on. Many of the APIs (and log entries) still use 'SMS' as their prefix.

I recall being confused by the term 'package' at my last client when migrating from GP useage to SCCM, thinking that it meant an MSI/MST bundle. It doesn't.
Answered 08/17/2010 by: VBScab
Red Belt

Please log in to comment
0
Thanks for your help everybody it works now. I had created a second package with no data source files and only msiexec /x etc. in the command line, when I tried to distribute the package it just sat there 'install pending' forever. It worked after creating a second uninstall program for the original install package.

Cheers
Answered 08/17/2010 by: maxx8864
Yellow Belt

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