Problem with supsersedence

[superted]

Hi,

I have a problem with supersedence. Client have win 7, office 2010, language pack and proofing tools. We want to upgrade to Office 365. Then we have to uninstall all Office 2010 products, and then install Office 365. I have used supersedence and created a device collection. This is limited to all systems, and membership rules I used direct. I have just added one client to this collection and done the office 365 deployment to this collection. Office 2010 are uninstalled and Office 365 are installed, but the problem are that other client then I have added to the collection got this application package. I don't understand why.

 

Se picture for more information.

 

I have experience the same problem on the Adobe reader 11.0.5 package I have made. This have also a supersedence. When I deploy a new maskin it have adobe reader 11.0.5 installed, but somehow it reinstall after a while. Some client it just uninstall without install again. I have just one deployment on this. It deployed to all system, but with direct rule. And I have just added some client to this collection.

Could it be some problem with the supersedence or problem with device collection?

 

Thanks for feedback

[Peter33]

Let me take a wild guess. Your Office 2010 is part of an optional task sequence (probably OSD). And your Adobe Reader obviously too.

If you superseed an application, which is part of an optional task sequnce, all clients of the task sequence target collection, with the superseed version installed, will get the new Version, no matter to which collection you deploy it.

Makes sense? No .. but it's the sad truth.

I actually had a ticket open with MS Support. They could'nt help us either. The bug seems to have no priority for the developers and might be fixed with a future CU.

 

I am hardly using the supersedence option anymore now, to avoid this bevahior.

[superted]

Thanks for your feedback.