I guess have to do the same, although not sure what the purpose of the "new version" collection is?
IMO is sufficient that old is upgraded. You're using "whether or not a user is logged on", system install with just one deployment type? Wondering what happens if both policies get active the same time? Upgrade through computer and with supersedence. Obviously not the best solution. I think supersedence should always allow to upgrade if the settings of the App/DT allow it. -R From: [email protected] [mailto:[email protected]] On Behalf Of Matt Wilkinson Sent: Montag, 12. Januar 2015 13:21 To: [email protected] Subject: RE: [mssms] Upgrade (supersedence) user based deployment I've tried to accomplish the same thing. In the end I have create 2 computer collections. 1 is based on the installed application with the old version installed. 1 is based on the application with the new version installed. So as long as your hardware inventory is regularly (daily). Then you can deploy the updated application to the computer collection. The computers should move from one collection to another. I did need to put the supercedance in place. An additional user deployment to a user collection is in place for when a user installs the application from the software catalog. So the user doesn't need to be logged in for the deployment to take place. I also noticed in the appdiscovery.log that the application targeted at the user didn't appeared to be discovered. From: Roland Janus [mailto:[email protected]] Sent: 09 January 2015 16:24 To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] Upgrade (supersedence) user based deployment Bump? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Mittwoch, 7. Januar 2015 14:22 To: [email protected] <mailto:[email protected]> Subject: [mssms] Upgrade (supersedence) user based deployment Not sure if I'm thinking about this right. I want all applications basically targeted to "all users" as available to shop. The user installs the application. Now a new version is created and superseded. If the deployment is "available" it would upgrade all clients where it is installed if the user is logged on. But what if I want all clients having the old version be upgraded, regardless if someone is logged on? Obviously "required" on "all users" isn't a choice. Can I only do that through device targeting (inventory with old version) or is there a choice to make this required for the users having this application? CM seems to know about those, but I have no idea if a user based collection can have the same data: The right number is "users with application" Can a user collection have that data? I didn't notice anything obvious in the query editor. -Roland _____________________________________________________________________ This email has been scanned by the MessageLabs Email Security System on behalf of Leeds College of Building. For more information please visit http://www.symanteccloud.com _____________________________________________________________________ _____________________________________________________________________ This email has been scanned by the MessageLabs Email Security System on behalf of Leeds College of Building. For more information please visit http://www.symanteccloud.com _____________________________________________________________________
