sccm: quicktime multiple versions appear installed simultaneously

I'm using SCCM to deploy updates/patches for QuickTime.  In some cases, I now have machines that show multiple versions of Quicktime in add/remove programs, such as 7.6.2 AND 7.6.9 both simultaneously.  attempts to remove 7.6.2 on these machines fail, code 1605 (basically the wrong version).  How can I kill older versions while installing current version? Or some other solution?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joseph DalyCommented:
Are you able to remove the older versions manully through add remove programs?
garrywebbAuthor Commented:
RDP blocked, so not sure.  let me try to replicate the problem on a machine I can get to, then I can test. back in 1 hour.
Joseph DalyCommented:
Ok what im thinking is if you can uninstall the software from add remove programs you should be able to just run a script via sccm to uninstall it.

If that uninstall doesnt work you may need to get the source files for the original install and make a package that has a program advertised that contains the uninstall switches.
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

garrywebbAuthor Commented:
no idea.  the 800 out of 10,000 machines with duplicate quicktime are in other buildings and not accessible except via SCCM. I can't replicate the problem on a test box; the 7.6.9 won't leave older versions behind on testboxes.  Can't RDP, locked down for security by a different network team.  Indirectly, I'm going to guess that I could uninstall them, given that I can manually uninstall JAVA where I have multiple versions in a similar situation.
garrywebbAuthor Commented:
such a script would look like...?
I'm afraid I'm a bit of a vbscript novice, and temp assigned to manage 10,000 machines via SCCM, which I'm decent at, but still somewhat new.
garrywebbAuthor Commented:
I have the source files for the original install(s) and made a package that has a program advertised that contains the uninstall switches. the program results in 1605 because the machine somehow sees it is running a newer version than the uninstall (something.msi /x) is calling for.  Would love to try a script, if you have one or similar or template to try.  Need script.
Joseph DalyCommented:
Its kinda tough to say without knowing exactly why they failed or if a manual removal would be possible. But assuming that a manual removal through add/remove programs does work I would use a script similar to below.

WMIC product where name="ProductName" call uninstall

This uses WMI procedures to uninstall the software. You would need to replace the ProductName with the actual product name EXACTLY as it appears in Add/remove programs. You could either run this locally or you could save as a bat file and advertise through SCCM to the affected machines.

I have written an article here that goes into more detail about the WMI software uninstallation.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Joseph DalyCommented:
Hmmm for some reason the pictures disappeared from my article on EE. Here is a mirro of it on my personal blog.
garrywebbAuthor Commented:
looks very promising, will require some hours to test and tweak; back soon.
Joseph DalyCommented:
Good luck. I know on "normal" installations the WMIC uninstall works very well. Where I dont know the condition of the machines you are having problems on its questionable as to wether or not this will work properly.

Either way let me know how you make out.
garrywebbAuthor Commented:
okay!  wmic is bloody brilliant, by the way. solves 90% of life's problems.
Here's the deal:
wmic sees only quicktime769 on these machines.  However, add/remove programs says quicktime762 AND 769 both.  wmic can uninstall Quicktime, which leaves zero "quicktime" instances detectable with "wmic program get name", but leaves 762 showing under add/remove programs.  basically, there isn't enough 762 there to uninstall, but enough there to get an entry in add/remove programs.  For software scanning purposes, I need the bogus 762 entry to go away.  How do I kill an add/remove programs entry that I cannot uninstall and isn't really there?
Joseph DalyCommented:
For that youd have to go to the registry and remove the entry.

MS used to have a tool that would let you script this out it was part of the windows installer cleanup utility and it was called MSIzap. However MS discontinued support for it.
garrywebbAuthor Commented:
thank you xxdcmast!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Scripting Languages

From novice to tech pro — start learning today.