Application Supersedence

Hi!
I want to test supersedence on one computer and have a question,
I have application10, it will be superseeded by application10.1,
Can I deploy application 10.1 to my test collection that contains 1 computer, to see if it replaces application 10 or will it also upgrade all the application10´s out in production? that would be a nightmare if the supersedence doesnt work
and the production computers end up with damaged installations of the application.
can i add some sort of condition so that it only superseeds on a specific computername?
Do i need a complete test environment for this?
/ Lars

I recently found this to be untrue....Veru funny surprise indeed!
I set our new Office 2013 application to superseede Office 2010, then I deployed it to a small test group.
Imagine my joy when ~200 users got this Upgrade (and it would have been a lot more had I not stopped the deployment)! Not only was it available, but if the user was logged out
it immediately uninstalled Office 2010 and installed Office 2013!
This was a very fun surprise indeed, the helpdesk staff did not like me very much the next few days while they had to assist the poor users for a downgrade :)
It was my first mistake in SCCM, but to be honest it did not feel like a mistake. More like SCCM being strange. Now we have to resort to using registry settings to enable Office 2013 testing (setting the custom registry key as a requirement for the application)

Similar Messages

Application Supersedence not working as I want and expect!

Hello,
I need help to find out how to properly deploy an upgraded application using the SCCM 2012 Application supersedence.
What I have
One application in production with version 1.0. Let us call it APPL-BLUE1.0
New application of the same product with version 2.0. Let us call it APPL-RED2.0
What I want to achieve (the goal)
Users should be notified via the Software Center that a new update is available. The new update should not be installed until the user is ready and manually triggers the installation via the Software Center.
My configuration settings
On application APPL-RED2.0 I have gone to Properties -> Supsersedence and added the APPL-BLUE1.0 to the Supsersdence list. Replacement Deployment Type is configured (set to the Deployment type for the APPL-RED2.0) and
the Uninstall checkbox is checked (to uninstall the APPL-BLUE1.0 deployment type first).
Install behaviour for APPL-RED2.0 is "Install for system" and "Whether or not a user is logged on" with Normal visibility.
Then I create the Deployment which I have tried three different ways.
Action: Install, Purpose: Available, "Automatically upgrade any superseded versions of this application"
unchecked.
Action: Install, Purpose: Available, "Automatically upgrade any superseded versions of this application" checked.
Action: Install, Purpose: Required, "Automatically upgrade any superseded versions of this application" checked (forced, greyed out).
What happens
The application is not automatically made available in the users Software Center at all. No notification is presented and the user has to access the installation by looking in the Application Catalogue
first. Once found in the Application Catalogue the installation runs without problems but this means that the user must somehow know there is a new version available through other means.
The application is automatically installed (without regard to whether or not the application is in use) on the client and a notification is presented on the users machine (Software Center).
Exactly the same result as for #2.
This conflicts with what I want to achieve. I want a notification and that the application is automatically made available for installation in the Software Center but I do not want it to automatically upgrade but rather let the user initiate the installation
whe he or she is ready (i.e. when the application is not in use).
Please point me in the right direction in order to accomplish this.
Thank you.
Sindre

Have you tried changing the application deployment evaluation cycle to increase the speed the update is detected?
also with the notification issue, I have a similar problem and have a script in place. Our business rules are to install the application asap giving the user 6 mins to close it. but this script could easily be changed to allow it to wait non stop.
Or maybe you could set a requirement for the deployment type, a custom script that checks if the application is running, but I am not sure on what cycle the application will evaluate this. or if it will evaluate it then download the application (leaving
a window for the application to be run)
Also in case it is not obvious I have removed functions and keywords. but this should give you an idea of how to achieve your desired results
'Check if current version
if CheckMSIVersion("{removed}","removed") = 1 then
wscript.quit(0)
end if
'sets path of script
strScriptDir = getParentDirectory
intACProcesses = CountACProcesses
'Check if running
if intACProcesses >= 1 then
'runs warning HTA
wshShell.Run ("""" & strScriptDir & "\BeforeInstallAlert.hta """),3,False
'Untill app is closed keep activating alert and checking to see if it is running
const timeout = 360000
const timepoll = 15000
do while intACProcesses >= 1 and i < timeout
intACProcesses = CountACProcesses
if intACProcesses >= 1 Then
wscript.sleep timepoll
end if
i=i+timepoll
wshshell.AppActivate "Appname Upgrade Alert"
Loop
end if
'Kill AC
killProcesses("appname%")
'Kill HTA processes
killProcesses("mshta.exe")
'Install new and record exit code
intExitCode = WshShell.Run("msiexec /i """ & strScriptDir & "\removed.msi"" /qn",0, true)
'if install fails exit with exitcode
if intExitCode <> 0 then
wscript.quit(intExitCode)
end if
'Run New client
WshShell.Run("""" & findACProgramDir & "removed.exe"""),1,false
'Run finished HTA
wshShell.Run ("""" & strScriptDir & "\AfterInstallAlert.hta"""),3,False
'Exit with code
wscript.quit(intExitCode)
Quote by andhey "hmm ill try it later, i accidentally deleted all my tv shows when trying to delete a word document lmao"

Error code 0x645(1605) when using application supersedence

I've created a new version of an application that supersedes the previous version. I'd like the new version to uninstall the previous version, as otherwise it will install alongside it. Each version has a different MSI product code.
I created the application for the new version along with the supersedence rule, setting it to uninstall the previous version. I then set up a test VM with the old application and tried to install the new one via the Application Catalog. However, when the
Software Center begins the installation and tries to remove the old version, it fails with: "The software change returned error code 0x645(1605)"
I verified that the uninstall string for the old version is correct: I can even manually run it on the VM and it begins to uninstall the old version. I thought that 1605 indicated that the product that's trying to be removed is not present, but since the
uninstall string works I'm not certain what exactly is going on.
Any help that can be offered would be most appreciated. Thank you!

Thanks for responding so quickly! I ran it manually and the new version of the program installs ok. I used the same command line that I specified in the MSI deployment type (and there's only the one deployment type). So it seems that the error occurs when
SCCM implements the supersedence rule and tries to uninstall the old version.
I checked Event Viewer and I see two entries for when the program is attempting to uninstall, but they are simply the entries that say "beginning a windows installer transaction" and "ending a windows installer transaction." There's no error in Event Viewer.
The entries feature the MSI product code of the product; if I copy that product code and run msiexec /x with it, it uninstalls.

Application Supersedence - Office 2007MSI Office365C2R

Ok, so. I'm kind of the specialist here on program deployment for our company -
I've got around most of the issues we've seen, but the Application system is
totally new to me (we just upgraded from SCCM 2007, where "applications" don't
exist).
I'm trying to create a deployment for Office365 - I can get it
to install, that's no problem. I used the appV packager part of the setup file,
so it even does the streaming.
The problem I've got is that we're upgrading
to that from Office 2007, which was installed via MSI. I found a page that
describes the steps required to add it into the system (given the setup file is
an exe, and the application system imports from msi). I imported the
ProPlusWW.msi file as recommended, and changed the install/uninstall commands to
use the setup.exe file (setup.exe /uninstall for removal). Now, when I set the
system up for O365 to supersede office 2007, it should remove the old version,
right? I run the application from the software centre, and lo! setup.exe *32
appears, which should be the removal.
It sticks at a low amount of
RAM, confirmed to match the amount used when it's got to the "are you sure you
want to remove this software?" prompt. So, I go and create a new xml file with
"displaylevel="none" in it, and reboot value="NEVER" to get it to remove without
prompt, and without rebooting the PC in the middle of someone working... It
still sticks the process at the low level of RAM use (1740k), and I've
left it for over 30 minutes to make sure - should be more than enough time for
it to do what it needs to do.
Anyone have any ideas? Please ask if you
need any more information to help me.... Being as I can't figure out the issue,
I can't be sure what you might need to know about it.
Thanks.

Naturally, I've been trying to sort this out myself...
I've edited the
uninstall command to just use msiexec /x {product key} /q /norestart.
It launches msiexec, setup.exe and starts uninstalling!.... at that exact
moment, the Office 365 install says "failed", and stops doing anything else...
Office 2007 continues to uninstall, and just sits there doing nothing....

Application used in a TS is installing itself

Hi guys,
if some Kind of strange behavior where I´am not 100% sure what is causing this... So here is the Situation: I´ve created an application "Nvidia Drivers" with 4 deployments types. Each DT uses a global condition as requirement to decide, based on
the Video controller, which DT is used. The application is deployed as available AND I´ve also added the same application to a task sequence. This TS is still the one which was used to install these and most of all our clients. The TS is also deployed as available
to these Clients (PXE and media only). After all that stuff we have seen some unexpected installations in the field, even after removing the deployment. So what is going on here? Is there some sort of "loopback" where the clients geht the application
from the TS where they once installed from? I´ve found some blog and other forum posts
http://blogs.technet.com/b/umairkhan/archive/2014/03/08/configmgr-2012-application-supersedence-behavior-with-task-sequence-deployments.aspx
https://social.technet.microsoft.com/Forums/en-US/935c3556-e8a1-4146-95f2-6e6822dbb2f8/application-dependencies-installing-with-no-deployment-of-parent-application?forum=configmanagerapps#d98eaf8c-df65-403c-9204-713b4a5547a9
https://social.technet.microsoft.com/Forums/en-US/c9cd7953-35a2-46eb-bedc-6427c15e92c4/applications-in-a-task-sequence-reinstall-when-app-changes?forum=configmanagerapps
with similar issues, but always related do supersedence. I don´t have supersedence used here. Can anybody confirm or refute my speculation. I can provide log files shots in about ~8 hours since it is 11pm for me now, but you guys sure have some great ideas
until I´am back in the Office ;)
Thank´s a lot...

Have a look at AppDiscovery and AppEnforce.log to see what's really happening.
I'm not surprised though. Even though the TS is only available to media and PXE, the applications used in the TS will be evaluated by the clients. (I know a few that don't use applications in OS task sequences for the same reason. Including
myself. The behavior is just weird.)
Martin Bengtsson | www.imab.dk

Query for applications that have been superseded.

I need to return a list of applications that have not been superseded in a report. I can do this very easily in the console, but I can't seem to find any views that show any information about application supersedence.
While we are at it, has anyone spotted a diagram showing the relationships for Applications in the views for SCCM 2012? Unfortunately looking through the existing reports doesn't help all that much because the way the queries are structured is very
confusing. Which also may explain why the application reports frequently have conflicting numbers in the same report. By this I mean that these multi-part reports that show a bunch of different graphics, often have numbers for the same application
that don't match up.
My customer has basically decided to ignore just about all the application reports that come in SCCM since they so frequently don't agree with themselves or the SCCM console. That's why I'm trying to understand the model so I can try and give them
some better reports.
Bob

You can get a Excel list of SQL views here:
http://gallery.technet.microsoft.com/SCCM-Configmgr-2012-R2-SQL-5fefdd3b

Superseding Application Installed when NOT deployed and NOT set to Automatically Upgrade

SCCM 2012 SP1
I have an application of Adobe Reader X which is deployed as "available" to the "All Workstations" collection. (It is also installed as part of our OSD task sequence for all workstations, if that matters.)
Some months ago I packaged Adobe Reader XI and did NOT set it to supersede Adobe Reader X. It was deployed as available to a small user collection.
Flash forward to yesterday. I wanted Reader XI to be available to all IS staff, but not to automatically install for any of them or to automatically replace existing Reader X installs for anyone. I went into my existing Adobe Reader XI application
and set it to supersede the Adobe Reader X deployment type. I then deployed Adobe Reader XI as "Available" to my "IS Staff" user collection and did NOT select the "Automatically upgrade any superseded versions of this application."
Overnight, all existing installs of Adobe Reader X were replaced by Adobe Reader XI on all workstations that were powered on during the maintenance window. I was understandably surprised and double-checked my deployment settings. It *is* deployed
as "available" to all IS staff and to the pre-existing user collection. and verified that I do not have Adobe Reader XI deployed to ANY other collections other than the original small user collection and now to my IS Staff collection, both
as "Available".
I checked APPINTENTEVAL.log on some of the affected workstations and noted that once I had created the supersedence relationship, all workstations that I've checked started logging as "Applicability = Applicable" and as soon as the maintenance window
started, they installed.
I'm very confused. I've used Application Supersedence many times, and it has never applied to a collection to which the superseding application was not deployed. Can anyone suggest a mechanism I might have missed that made this app evaluate as
applicable on every workstation that had Reader X deployed to it? I'm confident that it should have have.

Is Reader XI used in a (OSD) task sequence?
Torsten Meringer | http://www.mssccmfaq.de

Re-calculate when VIEW changes

I am trying to perform a calculation for a specific VIEW, i.e., ?PERIODIC;? this means calculate for the current period, do not roll forward, the problem is when I change the VIEW to, i.e., ?YTD? and want to roll forward, I am unable to re-calculate, the new values. I am very new to the HFM environment so any suggestions would be appreciated.email=[email protected], Donald

Hi,
Are you sure that those machines are not targeted by an available Task Sequence? becuase then it will happen, it is described here:
http://blogs.technet.com/b/umairkhan/archive/2014/03/08/configmgr-2012-application-supersedence-behavior-with-task-sequence-deployments.aspx
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Removing old EMET trouble

We need to install the new EMET on est 500 end workstations. They already have version 3.0 installed. The problem – EMET 3 is still remaining there after I done installed the new version 4.1 update or 5. I tried it manual install and also from SCCM. How
do I rid of version 3.0 completely using SCCM?
It is looking bad that two EMETs are showing in the add/remove programs area. Sometimes two sys trays show up at the notification area too.
I tried with both application and package options using the msi uninstall string with version number as the detection.
Please help as soon as you can!!!
Thanks

Hello Mecoy,
If you are using the SCCM 2012, you can use ofr your applications, not packages, the option Application Supersedence.
With this option you can see in the image above, the new application can supercede the olt one, and you can have the option to uninstall the old one, remember, this option only applies to Application, and not packages.
More information about Software Supercedence here:
How to Use Application Supersedence in Configuration Manager
http://technet.microsoft.com/en-us/library/gg682071.aspx
I hope it can help!
Best Regards!
Renato S. Pacheco

Detection of batch file

I have a batch file that uninstalls all previous Java versions that I want. I want to set this up as an application to be ran as a dependence for the current Java version that we are running.
As with all applications, it needs a "detection" to know that it is there or ran properly.
Can someone provide some guidance as to what to use. I don't see how a registry or msi value would fit in this.
Thanks in advance!

The correct way to do it would be that you do applications of all the Java versions and then you configure your new Java version to supersede the old ones.
This seems logical.
This is the way it was designed to work. You have to do a little bit work though, you have to create a new application of every Java version you have and specify the detection methods and uninstall commands for all of them. Since they are
.MSI packages, you don't necessarily need to use content for these old versions at all, simply use msiexec /x {PRODUCTCODE} for the uninstallation and the same {PRODUCTCODE} for the detection method for existence of the version in case. When you've created
the old versions, you configure the newest one to supersede all the previous versions.
More info on supersedence here:
http://setupconfigmgr.com/application-supersedence-in-configuration-manager/

Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence. I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml. The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="Never" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ProductFiles" State="Local" Children="force" />
</Configuration>
The detection method is the folder path to see that office 14 exists. When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue.
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall. The application is in the supersedence tab for Office 365 2013. This never installs. If I create a softare distribution and deploy it on its own it uninstalls without issue.
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this. The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool. I can install this with the application I created using the appv5 package created with the click to run tool. The issue is we need Office 2010 and Lync 2010 uninstalled first.
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013.
I have looked at many articles and so far it is not working for us. Any help appreciated to get us to the cloud.
Thanks,
Brit

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do. The detection method seems to be hanging things up. On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com

Deploying a batch file via Application Manager

Hi there,
I have a batch file to remove an application that has several subcomponents that have their own installers and remove their registry keys as well. It works well when deployed as a package but I want to deploy it with the application manager to utilise the
detection methods and content management available there.
The problem is that when I deploy the package, nothing is downloaded to ccmcache, so the batch file doesn't run, although the Software Centre shows that is installed and the compliance on the collection is at 100 percent. Where is my batch file going?

Actually, there is no utility in the Package Manager that I can see for advertising software in the application Catalog, replacing or upgrading deployed applications with supersedence rules, detecting existing installations on client machines, limiting deployment
of applications to clients with requirement rules or managing the dependencies when deploying packages. Is there something missing from my installation?
Correct, none of those exist in the package feature set and there's nothing missing from your installation (there's nothing called "Package Manager" though so not sure what you are talking about there -- are you using a third party tool perhaps?) but do
you need any of those things to run a simple uninstall?
My statement was targeted at this statement of yours: "with the application manager to utilise the ... content management available there". As mentioned, there is no difference as far as content management is concerned between apps and packages. All
of the things you mentioned in the latest post have nothing to do with content management.
Mind you, I'm not saying whether you should or shouldn't necessarily use applications as apps have clear advantages, I just want to make sure the info given is correct and that you base your decisions based on that correct info.
Jason | http://blog.configmgrftw.com

Application Deployed to User Collection...Excluded Collection sees Deployment

We have 2 versions of an application that need to be deployed. The newer version (6.0) is deployed to a collection that includes All Users, but excludes an exception collection. The users that are in the exception collection do not show in this application
collection.
We then deployed the older version (5.0) to the exception collection.
The issue is that the users in the exception collection can install both 5.0 and 6.0 from the Application Catalog. They should be excluded from the 6.0 deployment since they aren't in the collection, but they are still seeing it as available.
I thought maybe SCCM would recognize that they are not supposed to get the deployment when the user tried to install, but that wasn't the case...they could still follow through with either install.
We use this same process for machine-based deployments and it works fine. I am wondering if I am missing something, or if user deployments don't work quite the same as machine deployments...in this type of scenario.
Thanks for your help!

If the clients had originally downloaded the policy that told them that it was a superseded relationship, then that should correct itself in the next polling cycle when it detects the supersedence is no longer valid.
If that hasn't happened, you could delete one of the apps, and then recreate it.
Wally Mead

Superseding an application which is installed via OS task sequence

Hi I am using SCCM 2012 SP1 and want to update AppA_version_1 to the AppA_version_2. At the moment AppA_version_1 is a core application and is installed to all machines via OSD when the machines are built. For this reason we don't have any
collections for AppA_version_1.
I have now created a new application for AppA_version_2 and want to test the deployment to a group of machines. As part of the test deployment I want to supersede the AppA_version_1 which we currently have installed.
In the past I have tested supreseding business applications (which are not part of the task sequence and deployed to users not machines) by first creating a test collection, setting the supersedence options and then deploying the superseding (latest) application
to the test collection. When I am happy it works OK I deploy the superseding application to the main collection for that application.
I have not had to supersede an application which is part of the task sequence before but I presume I do it in just the same way ? At the moment I don't want to touch the task sequence. I want to test the deployment of AppA_version_2, then
release it to all production machines, then update the task sequence so it includes AppA_version_2. What I don't want is to deploy it to the test group but have it automatically update on all production machines.
The reason I ask is that I have read that if you update the Task Sequence with the latest version of your software and this supersedes a previous version, then all of your machines in production will receive the latest version even though it has not been
specifically deployed to them.
http://www.windows-noob.com/forums/index.php?/topic/8952-possible-bug-in-sp1-cu1-client-applications-that-supersede-others-may-rollout-unexpectedly/
Even though I am not going to update the task sequence with AppA_version_2 just yet, it has got me questioning the testing of the superseded application.
Am I OK to superseded AppA_version_1 with AppA_version_2 and deploy to a test collection (without it updating all machines in the organisation) even though AppA_version_1 is installed as part of the OSD Task Sequence.
Hope this makes sense
Thanks
G

Thanks Jorgen
What happens if I select the option : automatically upgrade any superseded versions of this application
? Would this ignore the fact that I was deploying to a test collection and automatically update all production machines where the software is installed ?
I haven't actually come across this option before, but I think that is because I usually create my deployments prior to setting the supersedence rules.
Thanks
G

Two step application install with reboot in between

I have run into a interesting situation.
1. Deploying upgrade of IBM I Access from v5 to v7. V5 was installed before SCCM was deployed.
Requirement
* I have to uninstall v5 (script done to do this), reboot, then install v71 all in one step.
* I have to publish this to the application catalog as a single step process.
The obvious way would be to use a Task sequence to accomplish this, however; we can't put Task Sequences in the application catalog.
Building a application just to "Uninstall" the previous version and reboot would not work either due to detection requirements and the reboot between.
How can I run these 3 steps as one application in the application catalog? Any ideas?
Thanks
Andrew

hmmm... V5 was installed before SCCM was deployed. I have not tried this, but could I build v5 now and just use the Supersedence portion so the uninstall of V5 would be used?
Would inventory detection tie the v5 application to each machine as detecting an installed app?
Thanks so much!
I "think" supersedence only works with apps that were installed from CM. Not sure though.
John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/
It doesn't matter was it installed through CM or not, it's all about detection methods. Here's what happens if supersedence is configured for the new app (v7)
Because v7 supersedes v5, it will first check is v5 found based on the detection method of v5 that you've configured
v5 is found and because v7 supersedes it and you've configured to uninstall v5 first, it will do it, after v5 is uninstalled, v7 will be installed
You'll have to carefully test this, you could configure v5 to make mandatory restart by ConfigMgr client from the settings, it should do it it then. Also, I'm not 100% sure how the supersedence works if the deployment is made as an available to users (refering
to Application Catalog you mentioned) instead of devices. If this was an available deployment to devices, ConfigMgr client would automatically uninstall v5 on the machines it's found and then install v7, no user action needed even though the deployment is
available, this is by design of the supersedence function.

Application Supersedence

Similar Messages

Maybe you are looking for