Upgrade or update applications in sccm? + application naming
Hi,
I have a few applications that I would like to add in my sccm 2012. I am wondering the best way to name and add these applications/deployments so when a newer version of the software is released I can easily manage the deployment of it.
Eg.
I have some software called Paint.Net 3.0.0, Paint.Net 4.0.0 and Paint.Net 4.0.5. Each one of them has the same file name of PaintNet.msi.
Would I require each added as a separate application (named uniquely by adding the version number to the end of the application name) then set the latest to supersede and uninstall the older deployment type?
Or, would I replace the deployment type in the application with the newer version. Or instead of replacing it move it to a higher priority?
Or is there a better method to these?
Many thanks.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Maidens
7 years ago
For sure its good practise having a naming convention for SCCM applications/packages. I use the following method -
<Vendor_Name_Application_Name_Version_Number_Release_Number>
eg - Adobe_Reader_11.0.0.6_R01
(Release number is the application packagers release no.)
Are all three versions of the Paint.Net getting deployed so your managing multiple versions for a period of time? Creating individual applications would give you the ability to use superseedance for uninstalling/upgrading to the newer versions at any point in time. Superseedance is my preferred upgrade method providing you have an existing SCCM application to superseed.
