Jump to content


SSGIT

SCCM 2012 SP1 Supercedence seemingly doesn't work when uninstall required.

Recommended Posts

Does anyone else distribute applications where an uninstall of the previous version is required for the new version to be installed? We have a couple of these products. Unfortunately, this software isn't designed that well. Each update uses the same MSI (so same unique installer code), but they change the content. Their EXE installer manually uninstalls the old and installs the new. I found a reg key that changes with each install, so I'm using that as my detection method. Which seemingly works, because if I deploy to a collection and a couple of the PCs had the update already, they show as "already compliant."


I'm trying to set up supercedence to uninstall the old deployment type and install the new, but it doesn't want to work. When I deploy, I check the event log; the MSI transaction begins the install procedure and fails. Assuming this because I never see the uninstall action start in the log(s).

Anyone have a similar issue and, if so, how did you get around it?


Share this post


Link to post
Share on other sites

Hi Jörgen, thanks for the reply!

I've checked the appdiscovery.log file and it actually *does* detect the previous installation.

 

<![LOG[ ActionType - Uninstall will use Content Id: Content_c812fa32-ad88-4d85-b6e2-4ab7dbbf18c9 + Content Version: 1 for AppDT "Checkpoint Tools for PPC - 2.2.20" [scopeId_9EA1F6D7-1D7B-4ED9-A402-AAE8DD39A13C/DeploymentType_c9c1ff61-738c-45c0-8a1e-825a1832cec5], Revision - 9]LOG]!><time="19:21:48.734+300" date="03-04-2014" component="AppDiscovery" context="" type="1" thread="3540" file="appprovider.cpp:1486">
<![LOG[ ActionType - Install will use Content Id: Content_be4e7066-16e6-45a2-b5a9-71b66fa544b2 + Content Version: 1 for AppDT "Checkpoint Tools for PPC - 2.3.21" [scopeId_9EA1F6D7-1D7B-4ED9-A402-AAE8DD39A13C/DeploymentType_3f82c6a8-eb81-4401-8e39-00b4eea427ef], Revision - 12]LOG]!><time="19:21:49.389+300" date="03-04-2014" component="AppDiscovery" context="" type="1" thread="3540" file="appprovider.cpp:1486">

Share this post


Link to post
Share on other sites

How does your uninstall command look like? Are you using the same exe there? Try to uninstall with 'msiexec /x {productcode} /L*v c:\winodws\temp\myuninstall.log /norestart /q'.

So if that fails you have at least a logfile which tells you whats going on.

Share this post


Link to post
Share on other sites

How does your uninstall command look like? Are you using the same exe there? Try to uninstall with 'msiexec /x {productcode} /L*v c:\winodws\temp\myuninstall.log /norestart /q'.

So if that fails you have at least a logfile which tells you whats going on.

I was hoping to avoid removal using the product code as the new install has the same product code. I can try reverting back, though...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.