This sounds like a classic supersedence scenario.
Create a new Application in SCCM for the updated software, then add a
supersedence rule that says the old Application is superseded. When you set up
the supersedence, there will an "Uninstall" box you can check. This signals
SCCM to run the uninstall command from the old Application before running the
install command from the new Application.
Delete the deployment for the old application and deploy the new application to
the same collection. You do not need to do an uninstall deployment of the old
application, but you do need to keep the old application around in the console
and on the DP because SCCM will run the uninstall command from the old
application.
William
-----
We are running a single server SCCM 2012 R2 setup. I have an Application
deployed via SCCM (MSI file), and the vendor released an update that requires
removing the existing install prior to installing the new MSI package. I’m
still fairly new to SCCM so this is the first uninstall request I’ve
encountered from software I deployed with SCCM. I read online about going
through the Application Deployment Wizard and selecting ‘Uninstall’, but I
just wanted see about the consensus on “Best Practice”. If I have the original
Application in SCCM, I cannot deploy it again with the ‘Uninstall’ to the same
collection. SCCM tells me the Application has already been deployed to that
collection (even though the action will be an uninstall versus install). Is
this to avoid a logic loop of installs/uninstalls? Should I delete the original
deployment to the collection and redeploy with ‘Uninstall’ set? Or is it best
to import the original MSI a second time and deploy with the uninstall flag?
The other option I saw was using msiexec with the uninstall string. Since this
is my first go at this, I was hoping others could offer some insight on how
they handle uninstalling MSI packages in SCCM.
Some things that may factor in:
1) We are not using the software center for installing/uninstalling
applications. Still learning SCCM, so have been tackling it in pieces.
2) The original Application deployment setting was “Install for system”.
3) The original Application Deployment Type has the uninstall string in the
‘Programs’ tab (“msiexec /x {GUID} /q”)
Thank you very much for your time.
-Geoff
Confidentiality Notice: This is a transmission from Community Hospital of the
Monterey Peninsula. This message and any attached documents may be confidential
and contain information protected by state and federal medical privacy
statutes. They are intended only for the use of the addressee. If you are not
the intended recipient, any disclosure, copying, or distribution of this
information is strictly prohibited. If you received this transmission in error,
please accept our apologies and notify the sender. Thank you.
