Dynamis_dk
New Member
- Messages
- 2
- Reaction score
- 0
- Points
- 1
In an attempt to ease Service Desk workload and to breed a more 'self service' mentality in users, the way we deploy application via SCCM is using AD groups for 'App Install Groups' and 'App Removal Groups' then any requests for new software and our Service Desk just add in new usernames as required and the customer installs in their own time. We have one install group per App title, so say 'VLC_Player_Install' as an example. Overall it works pretty well but its come to the time where I need to better understand how the supersedence bit works for users with existing apps.
So in my example, we have 'Group A' which contains 10 users, 5 of which have 'App Version 1' installed and the last 5 haven't installed it yet.
When I create 'App Version 2' and set its supersedence to replace 'App Version 1', anyone in the AD group who hasn't installed it yet would just get 'App Version 2' in Software Center and everything should go smoothly. What happens to the users who already have 'App Version 1' installed when 'App Version 2' supersedence's it? Does SCCM know to automatically update the existing installations based on the action defined in the supersedance options? or do I need to find a way to upgrade the existing installs?
Is there a recommended 'path' to updating existing app installs in this scenario? I was thinking I could create a device collection which says 'if app version is less than 'App Ver 2' then do required installation of 'App Ver 2'' - but this would mean a lot of new collections as we have maybe 75+ apps being deployed via Software Centre.
So in my example, we have 'Group A' which contains 10 users, 5 of which have 'App Version 1' installed and the last 5 haven't installed it yet.
When I create 'App Version 2' and set its supersedence to replace 'App Version 1', anyone in the AD group who hasn't installed it yet would just get 'App Version 2' in Software Center and everything should go smoothly. What happens to the users who already have 'App Version 1' installed when 'App Version 2' supersedence's it? Does SCCM know to automatically update the existing installations based on the action defined in the supersedance options? or do I need to find a way to upgrade the existing installs?
Is there a recommended 'path' to updating existing app installs in this scenario? I was thinking I could create a device collection which says 'if app version is less than 'App Ver 2' then do required installation of 'App Ver 2'' - but this would mean a lot of new collections as we have maybe 75+ apps being deployed via Software Centre.
