So I need help\clarification with understanding supersedence and deployments. Scenario 1I have Application A which was installed via SCCM, I now have Application B, I set App B to supersede App A, the application will remove any previous version automatically, so I did not select for SCCM to uninstall App A. When I deploy App B with to Install and Require, (The "Automatically upgrade any superseded versions of this application" is Checked and grayed out) I have set a Deadline a week from the start of deployment, with a mandatory reboot. When the test clients started receiving it it was automatically installing upgrade B, those that did not have App A had till the deadline to install App B. >From what I understanding this is the expected behavior of this particular >application model, is this correct? Is there a way around this, without >creating 2 deployments, one for upgrades and making the deployment available, >and one for new installs with it being required. Scenario 2 (A bit more convoluted)I have a Set of Apps 1 (App A1 with dependence of App B1), I deployed App A1 to devices to install both applications. This needs upgraded with an additional install, set of Apps 2 ( App C1 with a dependence of App A2 which has a dependence of B2) Apps A2 and B2 supersede Apps A1 and B2 respectively, with SCCM performing the uninstall. When I deployed C1 to devices users had to the deadline before SCCM would force the install. I'm assuming that because I deployed C1(which had no applications to supersede) it would not care about any of its dependencies and whether they had any superseded applications, until the user or SCCM initiated the install. However I am running into an oddity. I now need to install App C2 which will supersedes C1, but still depends on A2 and B2. I have deployed C2 to several small test groups with different experiences despite the deployment options remaining the same. The first 2 deployments, did not automatically install C2 despite them having C1 it allows the users to initiate the install manually till the deadline was reached. However on my third deployment it is automatically removing C1 with C2, obviously A2 and B2 are already installed. I would have assumed that it would have reacted the same way as Scenario1 and just perform the upgrade, but that has only happened with the third deployment. Is there something I'm missing? (or just going insane) Mark.
