When we set up Recast Server Manger we left the setting for Supersedence method to “Active previous versions” this does all active previous versions that arent retired . Is there any mileage on changing this to “All previous versions” ?
Any thoughts?
I got a reply from the PM for Patching. He is watching this thread soooo… If we can get him working here, he might reply, later….
It will generate more load for ConfigMgr clients to evaluate all superseded applications. If there is a lot of supersedence relations, for example you have ten Mozilla Firefox versions and all versions have supersedence to all previous versions (9+8+7+6+5+4+3+2+1 = total of 45 supersedences to evaluate only for single app), it will generate quite a lot of load for ConfigMgr clients to evaluate all the information.So it depends on how many applications and different versions you have targeting the devices and how many devices you have in your environment. We have seen issues with too many supersedences that have led to generate heavy load on client side for larger environments. But can’t really say any boundaries when it starts to be a problem because it’s combination of nbr. of apps and app versions.
Makes sense. Shame it is a global setting. Would be good if it could be applied per app. We are having a major headache trying to align Chrome to same version. That aside App Man now Patching is working well for us
If you separate the app(s) to own deployment process, then you can override the global environment supersedence setting on the deployment process level.
Thanks @JuhaH, and I’m glad we got you working.