Thanks Todd. Since I shouldn't need any of the older versions once they get updated I think I will retire Version 1, and keep Version 2 and 3 active. Then when version 4 comes out and is installed I'll retire version 2, and so on.
Thanks, Ken ... From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hemsell Sent: Tuesday, January 14, 2014 10:45 AM To: [email protected] Subject: Re: [mssms] Application deployment question - supersedence the answer depends on your environment and needs, not on anything inside of SCCM. You supersede and app so that you can upgrade previous version right? So the question should be, how many of those previous versions are still in the environment, and would you expect any to show up with a previous version? Does anything have a dependency to something that has been superseded? a superseded app can still install from a dependency, but a retired one cannot If you no longer need it, then just delete it. answer why you need it, and you answer your initial question(s) On Tue, Jan 14, 2014 at 12:31 PM, Lutz, Ken <[email protected]<mailto:[email protected]>> wrote: I have just set up an application that is now being superseded by a later version. I have: Version 1 Version 2 - supersedence to Version 1 Version 3 - supersedence to Version 2 My question(s): 1) Should I retire Version 1 and/or Version 2 now that Version 3 has been deployed? 2) Should I reference Version 1 on the supersedence tab for Version 3? Right now it is only referencing Version 2 3) Could I just delete Version 1 now that Version 2 is being superseded by Version 3? Thanks for helping. [cid:[email protected]] Ken Lutz Senior Systems Administrator Information Systems Department Spokane County 815 N. Jefferson Spokane, Washington 99260
<<inline: image001.png>>
