We have issues with superceding dependent applications, put it differently can somebody maybe explain best way for doing this. Setup: Main app: "B1 -- v1.0 SCV1" this has dependency app "A1 -- V1.0 SCV1". When we deploy B1 as available application to test collection it does show up in Software Center and when you install it both B1 and A1 are installed, so far all good.
I try to supersede "A1 -- v1.0 SCV1" with "A1 -- v1.0 SCV2", and this is failing, I've tried various scenario's but they don't succeed. When I remove the dependency and install A1 SCV1 and apply supersedence then it does work without any issues.
Following scenario's I've tested
- add the updated version to the dependency as "OR" so both SCV1&SCV2 would be dependent. For new install only SCV2 would be installed (that makes sense)
- deploy the dependency apps as available to same collection
Questions:
- does anyone have best practice on how to update "Dependent application"?
I have SCCM 2012 R2 environment.
I would like to get some feedback on this, if necessary will open case with Microsoft and see if this is expected behavior or possible bug?