Uninstall dependency on application

Question

_{Wednesday, February 26, 2014 3:38 PM}

Hey,

I am having the following situation.
I try to deploy application A. Application A requires application B to be uninstalled (B is already installed - available in sccm with install and uninstall routine as application - not package).

I tried to create a collection that has install deployment for A and uninstall deployment for B (both as required).
Unfortunately application A tries to install first and fails, while uninstalling application B is running as second. :(

I tried with TaskSequence - but uninstalling an application is not possible during tasksequence. :(

I tried with "supersedence" but this replaces all deployments for application B - I just want to uninstall B where A is required.

I tried with a query that requests for applications registered in "add or remove programs" - but this only updates once a day or less often - what is too slowly :(

How do you handle requirements like this?

Unfortunately I already have distributed all applications to all our severs - if I hadn't I would have crated this application as package with program.

Thank you for help in advance

kind Regards

mk_maddin

All replies (7)

_{Wednesday, February 26, 2014 6:40 PM ✅Answered}

Configure application A to supersede application B. This can be done from the application A's properties. After this is configured, deploy application A. It should now update the application B so that it uninstalls B first (if found in the systems of the collection you deployed it) and after that it installs application A.

_{Wednesday, February 26, 2014 3:48 PM}

A requires B and you want to install A and uninstall B? Chicken, egg, eh? Deploy the A first, configure dependencies for B and after the deployment is compliant, remove the A deployment and deploy uninstall for B.

_{Wednesday, February 26, 2014 4:00 PM}

Sorry my mistake - first sentence was wrong.
I corrected :)

_{Wednesday, February 26, 2014 6:58 PM}

Hey
thank you for your help :)

Are you sure this only applies to the collection/deployment the new application is deployed?

To make understanding more easy:

Application B is deployed to collection C1 and C2

Now I want to have for collection C1 application B uninstalled and application A installed. (in this order)
If I specify supersedence and deploy application A to C1 (of course removing the old installation deployment for B)  it will uninstall B for collection C1 and install A for the same collection, but not for collection C2?

Thank you for explanation.
mk-maddin

_{Wednesday, February 26, 2014 7:11 PM}

You have to remove the deployment of application B from the C1 as you stated. Then you deploy A to C1 and it will uninstall the B and install A.

You can still deploy B to C2, it will install there, A will not be installed. Beware that when you deploy A to those machines in C2, it will remove the B again.

_{Wednesday, February 26, 2014 7:18 PM}

Thank you - I will try this :)
hopefully it is like you described and this will not replace all existing deployments / installations for application B.
Only for the ones in Collection C1

_{Wednesday, February 26, 2014 7:22 PM}

Make sure there aren't same systems on C1 and C2.