Say I have an application labeled A & B.

I want to supersede A with B, and notify users that there is an update and for them to go into Software Center and upgrade.

1. What option provides the notification option? Is it after adding the supersede, that SCCM knows automatically?

2. Do I retire application A now that it is being superseded?

3. Do superseded applications still need to belong in the catalog for the supersede to work?
3a. for example now I have application A, B, and C. A is superseded by B, and now B is superseded by C. Should I be keeping A around so that people can jump to C?

Hi,

1. you must deploy the new application which superseeds the old one to the client machine.

2. Yes, you can retire it, retire an application does not mean that it will not install existing deployments of the application is still active. You need to ensure that the client getting the new application isn't targeted by a deployment of the old application becuase otherwise the old application will install again.

3. I would switch the dployment and make version C available instead, if there are no application specific requirements that the old application versions need to be installed before version C can be installed but then it should be a dependency and not a Superseed.

Regards,
Jrgen

Hi,

1. you must deploy the new application which superseeds the old one to the client machine.

2. Yes, you can retire it, retire an application does not mean that it will not install existing deployments of the application is still active. You need to ensure that the client getting the new application isn't targeted by a deployment of the old application becuase otherwise the old application will install again.

3. I would switch the dployment and make version C available instead, if there are no application specific requirements that the old application versions need to be installed before version C can be installed but then it should be a dependency and not a Superseed.

Regards,
J