Jump to content

Uninstalling software prior to installing updated software with SCCM 2012


Recommended Posts

Posted (edited)

Hi

I have installed Schoolcomms 8.1 with SCCM and now we are having to update the software.

On a test rig I have uninstalled the previous install v8.1 using msiexec /x and uninstalled the new version using msiexec.

Uninstallation of the prior version is essential for the new version to work

 

when using SCCM 2012 can I deploy the new software with the msiexec /x ininstallation for the previous version of the software before installation of the newer version?

 

confused on Friday.com :)

Cheers,

D

Edited by dazza007
Posted

I think the easiest way to do this would be as follows.

 

1. Add the new version of the application to SCCM.

 

2. Go to the properties of the new version and click the supersedence tab.

 

3. Click add, then browse, and then find the old version of the application.

 

4. On the drop down for new deployment type select the new version and then click the uninstall checkbox. This will uninstall the old version and then install the new version in its place.

 

Hope this helps.

Posted
I think the easiest way to do this would be as follows.

 

1. Add the new version of the application to SCCM.

 

2. Go to the properties of the new version and click the supersedence tab.

 

3. Click add, then browse, and then find the old version of the application.

 

4. On the drop down for new deployment type select the new version and then click the uninstall checkbox. This will uninstall the old version and then install the new version in its place.

 

Hope this helps.

 

Yep, this is what I do.

 

Another trick is a combo of the first post. Add the old app into SCCM, and publish an uninstall task sequence; or create a task sequence which includes the uninstall with an "allow to fail" in the TS step followed by your new install step. This way, machines without the app to uninstall wont bomb out. I did this with Smart Notebook I remember, where some machines ended up with 2010 version from our previous 2007 SCCM implementation; and refused to come across properly.

  • 1 year later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...