Hello,

I have run into some complications with Supersedence within SCCM. These are the issues I have had:

• All systems updating to a newer version of software even if the application is deployed as available. My understanding is superseding an application makes it required IF the old application is installed.
• Doesn't comply with Maintenance Windows, meaning all systems are updating when it is available, unless I am not understanding this correctly. If I am not understanding this please let me know. What I want to avoid is 4000 clients hitting the DPs all at once. This generates a ton of traffic.

I tried finding papers to explain this but the only thing I was able to find from M$ is how to create the superseding applications, but nothing about the details on how the process actually works, so I am looking for clarification.

Thanks

Not an answer to your actual question but.....4000 computers getting content at the same time shouldn't be an issue at all assuming the DP's are placed properly and we're not talking about some HUGE package.

The DPs are setup intelligently with IP boundaries to limit the amount of WAN traffic. The largest application we have is nearly 5 gigs, which could get ugly, but a concern that I missed was we work in a clinical environment. If I am locking up these computers by removing/installing software on all at once - my head is going to roll.

I posted your questions to the other MVP's and product team and I was told:

 Theres an option to set a deadline when you deploy a superseding app, that deadline is meant for available installs of the superseded apps. In other words if you have the old app installed it will be auto-upgraded. But as stated, the use of that feature is optional

I got an initial reply to your second question as well however I've held off on posting that one until I get confirmation. I'll let you know what I find.

Great. Thanks for checking with other sources.