SOLVED SCCM Application Model

[JM143]

Hi,
I am looking for a document/site that is explaining the mechanics of the Application model (vs packages). My questions are mainly:
1) You associate a collection with an application. Once you have completed the deployment, is it better to empty the collection or is it better to leave the collection filled with the computers/users for resiliency to be maintained?
2) In case of a supersede, is it better to manage the supersede via SCCM, within the MSI itself or both?
Any link to websites or documentations on these matters would be much appreciated.

 

[Garth]

1, it depend on what you want to do 3 months from now.
2. There is no direct link between MSI and CM supersede. Therefore if you add the ability to remove older version within the MSI this SHOULD work with CM. But you should test it.

 

[JM143]

Hi Garth,
The way I see it is that let's suppose you have ApplicationA 1.00. You create an ApplicationA collection that you populate with either machines, users or subcollections. You then create a deployment to deploy the ApplicationA.
A couple of months after, there is an ApplicationA 2.00 to deploy. You remove the V1.00 deployment and you deploy ApplicationA 2.00 to the ApplicationA collection that already contains the users and subcollections of the application.
If you empty the ApplicationA collection after the first deployment, how will you populate the collection to use the V2.00 collection?
I personnaly would leave the ApplicationA collection intact at any time instead of emptying it.
Thanks

 

[Garth]

Why create a new collection in the first place? Why not reuse the same collection?

 

[JM143]

Hi,
This is exactly my point. When you add an application in SCCM and create the collection that goes with it, my comprehension of the application model is that the collection lives as long as the application lives in SCCM and the collection should never be emptied. The collection should also be used if ever you deploy a new version of that application.
I have a client who empty the collection associated with an application once a deployment is completed. I rather think that the collections members should stay there as long as the application exist in SCCM. That way, the collection members is always equal to the number of users that have the application installed.

 

[Garth]

ok, so you are good then?

 

[JM143]

Hi Garth,
If you return to my original email, I am not stuck in any way but I am looking for best practice with the Application model and how to handle the collections.

 

[Garth]

There is no such thing as best practice, only what works for you and your company. So....