RE: Uninstalling a non-ALLUSERS GPO installed package, the non-GPO way

If it was me, I'd produce a manifest from the original MSI, then build a
script to remove the files, registry entries and so on in that manifest, then
delete the 'Installer\Managed\Products\[ProductCode] registry stuff.


"Jacob Saaby Nielsen" wrote:

> Hey all,
>
> I'm looking for some advice here.
>
> Situation is this:
>
> One of my predecessors distributed, via GPO, a repackaged package of Python
> 2.2.3. This package when installing, seems to not
> install as allusers, but rather as a user unmanaged package. At least that's
> what I get listed when I use PowerShell with MS Installer
> extensions to list what products are available on my machine.
>
> And it makes sense too, that it's true, cause when I use my VBscript wrapper
> to uninstall the package, it doesn't detect that product
> being installed.
>
> Right, so that's that.
>
> Due to this package being integrated with the WinCVS client and some custom
> macros for WinCVS, I can't just yank the Python
> package via GPO. That would leave the WinCVS client and our custom macros
> unusable for a good amount of time.
>
> So I have to sort of kill it all in one go. The old macros package. The old
> WinCVS client. The old Python client. Via SMS 2003.
>
> So I created the packages, wrapped them in my uninstall vbscript. Then I
> find out that the Python package gets left on the PC.
>
> So my question is.
>
> A package, with the ALLUSERS property not set. It's installed via GPO. I
> want to uninstall it via a script via SMS 2003, so I'm able
> to time the uninstall of all the packages.
>
> How do I uninstall that one package which isn't advertised to the user I'm
> using to uninstall ?
>
> Any inputs and ideas are more than welcome
>
> --
> Best Regards,
> Jacob Saaby Nielsen
>
> http://www.ijacob.info
> gmail: jacob DOT saaby
> hotmail (IM/LinkedIN/Facebook): same as gmail
>
>
>