I was hoping to get peoples input on supersedence in SCCM 2012.
In my view it seems rather backwards with how it is configured. Here is my example as to why. Very interested to see if anyone agrees or suggestions on what others are doing.
There is an application lets call it "Program A". I input a version for it in the main Application screen. I create a Deployment type and deploy it. All works well.
I now have a new version of this program. Now this is where I feel it goes backwards. In order to now deploy this update common sense to me says I should simply create a new deployment type and tell it within that that this is the updated version. I update the version number in the main application window and off I go. SCCM Automatically updates the distribution points with the new version, removing the old one and "re advertises" the current deployment to link to the new version.
However as I understand it this is what needs to happen:
- Create a completely a "New" Application. "Program A v2" (What is the point of a version number if you need it in the name of it to ensure its unique)
- Create a completely new deployment type.
- Tell this new application that it supersedes the old application.
(I now have 2 applications called the same thing with a version number in the name as you cant have duplicates.)
- Create a new deployment for "Program A v2"
- Remove the deployment for "Program A"
I now have 2 applications for the same program.
I struggle understanding the point of this. Why even both creating a relationship between the 2 programs? Adding in the supersedence relationship actually makes the take longer.