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.