This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Scenario:
What is the expected install behavior for new devices that come online before the start date of Application B? Will Application A continue to install as new devices come online up until the install start date\time of Application B?
Or do all new installs of Application A get ignored?
Business use case is that we might have a critical security application that goes to all devices. We are trying to schedule in advance and with change controls a new update that will happen in the future. What appears to be happening is that new installs of Application A are not occurring at all if we schedule Application B in the future, leading to a gap in the installations and functions of critical software.
I cannot seem to find documentation verifying what the expected behavior is.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 28.000000000000004%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECK%3C/text%3E%3C/svg%3E)
Hi Rick Smith,
Is there a supersedence relationship conflict? (Please share any error if any on the instalation if required app?) If this is the case, then this may be expected behavior:
Note: If there is a conflict between supersedence and dependency intent, the Intune Management Extension (IME) will enforce the supersedence intent, if possible. Some intent may be blocked due to conflicts.
According to this : - https://techcommunity.microsoft.com/blog/intunecustomersuccess/upcoming-improvements-to-win32-app-supersedence/3713026
@Catherine Kyalo no, there are no conflicts.
If we set Application B to install right away, it will trigger the upgrade\replacement just fine. But in several apps we have seen the behavior that application B is set for a future date (let's say 2 weeks from today) and the result seems to be that no new installations of Application A are performed.
If we remove application B install targets with the future dates, application A begins to install as expected.
My assumption would be that Application A would install until Application B's start date. But I cannot find documentation that defines exactly what should occur in that scenario.